Developer Incentives

Blueprint developers earn revenue when customers instantiate and run their services. Incentives come from:

1. Service fee revenue share on every instance of your blueprint.
2. Optional TNT rewards (pre-funded, if governance enables InflationPool).

Service Fees

For each service payment, the protocol sends the developer portion to the blueprint owner by default. A blueprint’s service manager can return a different payout address (for example, to route revenue into a multisig, splitter, or DAO treasury).

The default protocol split is 20% developer / 20% protocol / 40% operators / 20% stakers (governance configurable).

Optional TNT Rewards

If the protocol is running InflationPool incentives, developers can earn additional TNT based on on-chain activity metrics (e.g., blueprints created, services created, jobs executed, and fees generated). These rewards are claimable from InflationPool.

Where This Lives in Code

• InflationPool: https://github.com/tangle-network/tnt-core/blob/main/src/rewards/InflationPool.sol
• TangleMetrics: https://github.com/tangle-network/tnt-core/blob/main/src/rewards/TangleMetrics.sol
• Payments (fee split + payouts): https://github.com/tangle-network/tnt-core/blob/main/src/core/Payments.sol

For a readable breakdown and links to contracts, see Rewards Architecture.

Design Tips

• Be explicit about slashing conditions and the evidence you expect to be submitted on-chain.
• Use security requirements and operator commitments to express what “secure enough” means for your service.
• Provide observability where possible (heartbeats and optional QoS metrics) to help operators and customers assess performance.

See Metrics and Scoring.