What datanet owners control
When you create a datanet, you configure all of its economic and governance parameters:| Setting | Description |
|---|---|
| Access governance | Who can publish content and who can vote |
| Publishing fee | Cost in REPPO to submit a pod to this datanet |
| Quality thresholds | Minimum standards content must meet for acceptance |
| Reward mechanics | How emissions flow to contributors and curators |
| Native token | The ERC-20 token on Base associated with this datanet |
How content flows through a datanet
Publisher pays the fee
A publisher selects a datanet and pays its publishing fee in REPPO. This fee is the Sybil-resistance mechanism — submitting low-quality content at scale is economically costly.
Pod becomes visible
The submitted content (a pod) is made visible to all voters participating in that datanet.
Voters allocate veREPPO
During the current 48-hour epoch, voters distribute their veREPPO voting power toward or against the pod.
Epoch closes and rewards are calculated
At the end of the epoch, the network tallies votes and calculates reward distribution based on voting outcomes.
Datanet economics
Publishing fees and other revenue accumulate in the Performance Pool for that datanet:| Source | Contribution to pool |
|---|---|
| Datanet creation fees | 50% |
| Publishing fees | 10% |
| Data access fees | 10% |
- 80% goes to REPPO stakers
- 20% goes to datanet owners
| Metric | Weight |
|---|---|
| EVOF (Economic Value of Feedback) | 40% |
| Staked REPPO | 25% |
| Trading volume | 20% |
| Total fees collected | 15% |
The Performance Pool distributes on a fixed cadence — every third epoch. Rewards you earn between distributions accrue and pay out at the next distribution event.
Creating a datanet
Use thePOST /me/subnets endpoint to create a datanet draft programmatically. You will need to provide:
- Native token address (an ERC-20 contract on Base)
- Token symbol and decimals
- Subnet name and description
- Publisher and voter onboarding instructions
- Your initial fee structure
POST /me/subnets/{id}/publish with the transaction hash. You can update fees at any time via the fee management endpoints.