π‘ Trident Explanation
Understanding-oriented. Deep dives into why Trident works the way it does, for readers who want the full picture.
ποΈ Core Architecture
| Document | Description |
|---|---|
| Vision | Why Trident exists |
| Multi-Target Compilation | One source, every chain |
| Programming Model | Execution model, OS abstraction, six concerns |
π Provable Computation
| Document | Description |
|---|---|
| How STARK Proofs Work | From traces to quantum-safe proofs |
| Provable Computing | Comparative analysis of ZK systems |
| Formal Verification | Symbolic execution, SMT, invariant synthesis |
π Ecosystem
| Document | Description |
|---|---|
| Content-Addressed Code | Hashing, caching, registry, equivalence |
| The Gold Standard | PLUMB framework, TSP-1 (Coin), TSP-2 (Card) |
| Skill Library | 23 composable token capabilities |
| Atlas Registry | On-chain package management with TSP-2 Cards |
| Standard Library | Why the stdlib is designed around one field |
π Onboarding
| Document | Description |
|---|---|
| For Offchain Devs | Zero-knowledge from scratch |
| For Onchain Devs | Mental model migration from Solidity/Anchor/CosmWasm |
βοΈ Philosophy
| Document | Description |
|---|---|
| Cyber License | Don't trust. Don't fear. Don't beg. |