DEV Community

Daniel Ioni
Daniel Ioni

Posted on

🚀 Tonight we pushed another important milestone in the evolution of MyZubster.

#developers #opensource #myzubster #tonight

🚀 Tonight we pushed another important milestone in the evolution of MyZubster.

The goal was not only to track contributors and rewards.

The goal was to answer a deeper question:

How can a contribution become part of a verifiable knowledge system?

A contributor should not be represented only by a wallet address, a payment record, or a list of completed tasks.

A contributor creates knowledge.

That knowledge should have:

  • provenance
  • evidence
  • verification history
  • ownership of contribution
  • a traceable relationship between work and impact

What we implemented today

1. Contributor Passport API

We introduced the first version of the Contributor Passport.

A contributor can now have a structured identity layer that connects:

✅ completed rewards

✅ contribution history

✅ transaction references

✅ future knowledge records

✅ evidence attestations

Example flow:

Contributor
     |
     ↓
Rewards
     |
     ↓
Contributions
     |
     ↓
Knowledge Passport
Enter fullscreen mode Exit fullscreen mode

This moves the system beyond a simple payment ledger.

A reward is no longer just a transaction.

It becomes a reference point for the knowledge created by the contributor.

2. Reward aggregation layer

We connected existing contributor rewards into the Passport model.

Real contributor activity can now be aggregated:

  • completed GitHub contributions
  • bounty completions
  • reward amounts
  • transaction references
  • contribution timeline

The first implementation already shows real contributor histories being reconstructed from existing data.

3. Knowledge Attestation Layer

One of the most important architectural improvements came from community feedback.

A critical point was raised:

A system should not say:

verification: confirmed
Enter fullscreen mode Exit fullscreen mode

just because the system itself wrote that value.

A confirmation needs provenance.

So we introduced a dedicated attestation model:

Knowledge Claim
       |
       ↓
Evidence Source
       |
       ↓
Attestation
       |
       ↓
Verifier + Method + Timestamp
Enter fullscreen mode Exit fullscreen mode

This means the system can answer:

Who verified it?

How was it verified?

When was it observed?

Which source supports the claim?

Built together with contributors

This milestone was shaped by contributors who are not only writing code, but improving the architecture itself.

The discussions around evidence systems, verification limits, and provenance helped us strengthen the design.

A contributor's knowledge is not only the code they submit.

It is also:

  • architectural insight
  • security improvements
  • design decisions
  • lessons learned
  • improvements to the system itself

The next evolution

The next steps are connecting:

Contributor
      |
      ↓
Knowledge Cards
      |
      ↓
Evidence Graph
      |
      ↓
Attestations
      |
      ↓
Reputation Layer
Enter fullscreen mode Exit fullscreen mode

The vision is to build a system where contributions do not disappear after payment.

They become part of a living knowledge infrastructure.

Thank you to all contributors building, reviewing, questioning, and improving the system.

The strongest systems are not created by one person.

They are created by the knowledge accumulated by everyone who participates.

🚀

Top comments (0)