Skip to content

Commit faae03f

Browse files
authored
docs: GEO-optimize README with banner, badges, FAQ, and definitions (#95)
1 parent e513966 commit faae03f

1 file changed

Lines changed: 45 additions & 0 deletions

File tree

README.md

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,23 @@
1+
![Tangle Network Banner](https://raw.githubusercontent.com/tangle-network/tangle/refs/heads/main/assets/Tangle%20%20Banner.png)
2+
13
# TNT Core
24

5+
[![Discord](https://img.shields.io/badge/Discord-Join%20Chat-7289da?logo=discord&logoColor=white)](https://discord.gg/cv8EfJu3Tn)
6+
[![Twitter](https://img.shields.io/twitter/follow/tangle_network?style=social)](https://twitter.com/tangle_network)
7+
8+
**TNT Core** is an EVM-native staking and service protocol for Tangle Network. It provides multi-asset staking, operator networks, slashing, and x402 payment settlement through a modular Solidity contract architecture.
9+
10+
### How Tangle Staking Compares
11+
12+
| Feature | TNT Core (Tangle) | EigenLayer | Symbiotic |
13+
|---------|-------------------|------------|-----------|
14+
| Multi-asset staking | Native ERC-20 support | ETH and LSTs | Multi-asset via vaults |
15+
| Service registration | On-chain Blueprint registry | AVS contracts (separate) | Vault-based |
16+
| Payment models | PayOnce, Subscription, EventBased | Not built-in | Not built-in |
17+
| x402 payment settlement | Built-in | Not supported | Not supported |
18+
| Liquid delegation | LiquidDelegationVault | Via third-party LRT protocols | Via external vaults |
19+
| Operator management | OperatorStatusRegistry | Operator contract per AVS | Per-vault configuration |
20+
321
Tangle Network's EVM-native staking and service blueprint protocol. Build decentralized services with customizable operator networks, multi-asset staking, and flexible payment models.
422

523
## Installation
@@ -142,6 +160,33 @@ cargo add tnt-core-bindings
142160

143161
See [crates.io/crates/tnt-core-bindings](https://crates.io/crates/tnt-core-bindings)
144162

163+
## Key Concepts
164+
165+
- **Blueprint**: A specification for a verifiable, decentralized service on Tangle Network. Blueprints define jobs, verification logic, and slashing conditions through on-chain smart contracts.
166+
- **Operator**: A node runner who registers to provide services defined by a Blueprint. Operators stake assets via MultiAssetDelegation and earn rewards for honest execution.
167+
- **TNT**: The native token of Tangle Network, used for staking, governance, and payment settlement.
168+
- **Slashing**: The penalty mechanism that deducts staked assets from operators who misbehave or fail to perform their duties. Each Blueprint Service Manager defines its own slashing rules.
169+
- **x402**: An HTTP-native payment protocol (HTTP 402 Payment Required) that enables per-request micropayments for Blueprint services, with on-chain settlement through TNT Core contracts.
170+
- **MultiAssetDelegation**: The core staking contract that manages operator deposits, delegator stakes, and asset accounting across multiple ERC-20 tokens.
171+
- **BlueprintServiceManagerBase**: The base contract that Blueprint developers extend to define custom service logic, including request handling (`onRequest`), result processing (`onJobResult`), and termination policies.
172+
173+
## FAQ
174+
175+
### What is TNT Core?
176+
**TNT Core** is the on-chain smart contract protocol that powers Tangle Network's staking, delegation, and service management system. It is written in Solidity and deployed on Tangle's EVM-compatible chain.
177+
178+
### What assets can be staked?
179+
TNT Core supports **multi-asset staking** through the MultiAssetDelegation contract. Operators and delegators can stake various ERC-20 tokens, not just the native TNT token. Each Blueprint can specify which assets it accepts.
180+
181+
### How does slashing work?
182+
When an operator misbehaves or fails to perform their duties, the **BlueprintServiceManager** can slash their staked assets according to predefined rules. Slashing conditions are defined per-Blueprint and enforced through the MasterBlueprintServiceManager.
183+
184+
### What payment models are available?
185+
TNT Core supports three payment models: **PayOnce** (one-time payment at service creation), **Subscription** (recurring payments), and **EventBased** (pay per event or job execution). These are configured in the Blueprint's pricing contract.
186+
187+
### How do I build a custom Blueprint with TNT Core?
188+
Extend `BlueprintServiceManagerBase` in Solidity and implement the `onRequest` and `onJobResult` hooks. Install TNT Core via `forge soldeer install tnt-core~0.10.4` and import the base contract. See the Quick Start section above for a working example.
189+
145190
## License
146191

147192
MIT

0 commit comments

Comments
 (0)