Participation Credits
Tangle uses a credits system to recognize contributions. Credits are computed off-chain, published as a Merkle root, and claimed on-chain through a dedicated contract.
Credits are not token transfers. A user proves inclusion by submitting the claim data and Merkle proof accepted by the Credits contract.
How Credits Work
- Eligible activity is indexed off-chain.
- A Merkle root for the epoch is published on-chain.
- Users claim credits for that epoch via a single transaction.
This approach keeps on-chain storage small while still giving the contract a deterministic proof to check.
Example Credit Sources
- Operator activity: running workloads, uptime, and reliability.
- Blueprint usage: services that are instantiated and used by customers.
- Ecosystem growth: integrations and usage that expand the network.
The exact credit sources and weights can evolve. Always refer to the current program details for what counts in each epoch.
Claiming Credits
Credits are claimed through the Credits contract once a new epoch root is published. The claim flow is intentionally simple and can be automated by the UI.
Contract source (GitHub): https://github.com/tangle-network/tnt-core/blob/main/packages/credits/src/Credits.sol
Contract Addresses
We will publish the contract addresses as each environment is deployed.
| Environment | Credits Contract | Explorer |
|---|---|---|
| Mainnet | TBD | TBD |
| Testnet | 0x758226e04478541fcdac605e1f235e2956259a10 | https://testnet-explorer.tangle.tools/address/0x758226e04478541fcdac605e1f235e2956259a10 |
| Local | TBD | TBD |
Testnet source: https://github.com/tangle-network/tnt-core/blob/main/deployments/base-sepolia/latest.json
If you are looking for token distribution or migration details, see TNT Migration and Claims.