Creator economy
Tips for original work, remix attribution and configurable revenue sharing, settled through the community's wallet.
The creator economy rewards original work. Members tip creators directly; when a member remixes someone else's work, a configurable share of the remix's revenue flows back to the original creator. The attribution graph, revenue-share rules and payout records live in the operator's deployment on the rewards-service component, and payouts settle through the community's wallet.
The module is planned. Its configuration block is part of manifest schema version 1 and is validated and planned by the SDK today, so a community can declare its intended rules now. The rewards service itself is on the roadmap.
Capabilities
| Capability | Status |
|---|---|
| Tips for originals | Planned |
| Remix attribution | Planned |
| Configurable revenue sharing | Planned |
| Creator rewards | Planned |
The reference deployment includes building blocks this module will use: an operator console for reward campaigns with budgets, platform and per-member daily caps, versioned publishing and a full audit trail. Settlement is not enabled for those campaigns.
Configuration
{
"modules": {
"wallet": { "enabled": true, "networks": ["network-a"] },
"creatorEconomy": {
"enabled": true,
"tips": true,
"remixRevenueShare": {
"enabled": true,
"originalCreatorShareBps": 3000
}
}
}
}Prop
Type
Validation rules for this block:
module.requires(error) if the creator economy is enabled without the wallet module.module.empty(warning) if it is enabled withtipsfalse andremixRevenueShare.enabledfalse.
✗ symorva.config.json is invalid
error Creator economy requires Wallets & assets. Enable modules.wallet. (modules.creatorEconomy · module.requires)How revenue sharing is designed to work
Basis points express the share exactly in integers: 10,000 basis points is 100%. With originalCreatorShareBps set to 3000, a remix that earns 1,000 units routes 300 units to the original creator and 700 to the remixer, before any operator fee the operator's published rules define.
- Attribution. When a member publishes a remix, the rewards service records an edge from the remix to the work it builds on. Attribution is recorded at publication and cannot be removed by the remixer.
- Accrual. Revenue attributed to a remix accrues to the remixer and the original creator according to the share in force at publication.
- Settlement. Payouts are instructed to the community's wallet service, which moves the value. The metering service records each settled payout as
settled-payouts. - Records. Creators and the operator see payout records; amounts follow the operator's published rules.
Changing originalCreatorShareBps applies to remixes published afterwards; it does not rewrite existing attributions.
Events
Planned webhook events.
| Event | Fired when | Key fields |
|---|---|---|
creator.tip.sent | A member tips a creator | tipId, fromMemberId, toMemberId, asset, amount |
creator.remix.attributed | A remix is published and attributed | workId, originalWorkId, shareBps |
creator.payout.settled | A payout settles through the wallet | payoutId, creatorId, asset, amount |
Privacy scope
Payout records are visible to the creator and the operator; amounts follow the operator's published rules.
Shared services and metering
| Shared service | Unit | Measures |
|---|---|---|
| Resource metering & settlement | settled-payouts | Payouts settled through the community's wallet |
Limits
| Field | Bound |
|---|---|
remixRevenueShare.originalCreatorShareBps | 0 to 10,000 |
DApps & ecosystem
A curated, operator-managed directory that makes partner applications and DeFi services reachable from the community, with member approval for every data request.
SDK overview
@symorva/sdk — the community manifest schema, module catalog, validator, deployment planner, templates and CLI.