Developer Incentives
Blueprint developers earn revenue when customers instance and run their services. Incentives come from:
- Service fee revenue share on every instance of your blueprint.
- Protocol developer rewards (paid in TNT from a pre-funded pool, if enabled).
Service Fees
For each service payment, the protocol sends the developer portion to the blueprint owner by default. A blueprint’s service manager can optionally return a different payout address (for example, to route revenue into a multisig, splitter, or DAO treasury).
The default protocol split is 50% developer / 10% protocol / 20% operators / 20% restakers (governance configurable).
Protocol Developer Rewards (TNT)
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.
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 and Slashing.