πŸ’‘ Trident Explanation

← Documentation Index

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.

Dimensions

explanation
nox/docs/explanation
nox explanations conceptual documentation β€” why nox works the way it does, the design choices behind it, and the consequences that emerge. these pages illuminate the architecture. for formal definitions, see reference/. for task-oriented instructions, see docs/guides/ (when available). pages | page…
bbg/docs/explanation
explanation
nebu/docs/explanation
finite field arithmetic an encyclopedia of the mathematics behind the Goldilocks field β€” from first principles to applications. every concept is grounded in the field we implement: p = 2⁢⁴ βˆ’ 2Β³Β² + 1. foundations finite-fields β€” field axioms, existence and uniqueness, GF(p), characteristic, the…
rs/docs/explanation
explanation
zheng/docs/explanation
zheng explanations conceptual documentation β€” why zheng works the way it does, how proof systems compose, and what makes Whirlaway the right architecture for cyber. these pages illuminate the design. for formal definitions, see reference/. for the hash primitive, see hemera. for the VM whose traces…
hemera/docs/explanation
why Hemera works the way it does design decisions behind the Hemera hash primitive. philosophy why-hemera β€” eight design principles: permanence, the tree, endofunction, self-reference, identity, unity, beauty, the name the-name β€” etymology: Hemera in the Protogenoi, genealogy of hash names…

Pages in this namespace

Local Graph