SymorvaDocs
Modules

Creator economy

Tips for original work, remix attribution and configurable revenue sharing, settled through the community's wallet.

Planned· On the roadmap

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

CapabilityStatus
Tips for originalsPlanned
Remix attributionPlanned
Configurable revenue sharingPlanned
Creator rewardsPlanned

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

symorva.config.json (excerpt)
{
  "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 with tips false and remixRevenueShare.enabled false.
✗ 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.

  1. 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.
  2. Accrual. Revenue attributed to a remix accrues to the remixer and the original creator according to the share in force at publication.
  3. Settlement. Payouts are instructed to the community's wallet service, which moves the value. The metering service records each settled payout as settled-payouts.
  4. 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.

EventFired whenKey fields
creator.tip.sentA member tips a creatortipId, fromMemberId, toMemberId, asset, amount
creator.remix.attributedA remix is published and attributedworkId, originalWorkId, shareBps
creator.payout.settledA payout settles through the walletpayoutId, 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 serviceUnitMeasures
Resource metering & settlementsettled-payoutsPayouts settled through the community's wallet

Limits

FieldBound
remixRevenueShare.originalCreatorShareBps0 to 10,000

On this page