Introduction to ULedgerNET
ULedgerNET is a permissioned blockchain protocol built for verifiable, tamper-evident transaction trails. Every action taken by a human or an autonomous agent is cryptographically signed, Merkle-chained across a multi-node council, and anchored via STARK proofs that any auditor can verify without access to the live system.
The core design premise: the audit trail should be produced by the system itself, not assembled after the fact from application logs. ULedgerNET makes tamper-evidence a protocol property, not a monitoring choice.
How ULedgerNET Is Organized
ULedgerNET is structured around a small set of interrelated primitives. Understanding them in order makes the rest of the documentation legible.
| Primitive | What it is | Detailed reference |
|---|---|---|
| Wallet | A cryptographic keypair with an on-chain address. The signing identity for any action. | Wallet reference |
| Transaction | A signed, typed action submitted to the chain. The atomic unit of change. | Transaction reference |
| Smart Contract | A WASM program deployed on-chain and invoked by transactions. | Smart contract reference |
| Consensus | The BFT council of validator nodes that agree on block order and finality. | Consensus reference |
| Cryptography | The signature algorithms and proof systems that underpin every guarantee. | Cryptography reference |
Agent Wallet Concepts
The Agent Wallets section extends the core primitives to cover the autonomous identity model. If you are building integrations that involve AI agents, automated services, or governed multi-party workflows, start here after reading the core concepts above.
| Concept | What it is | Reference |
|---|---|---|
| Entity | The organizational identity layer. Groups wallets under a governance hierarchy (ORG, DEPARTMENT, PERSONAL, AGENT). | Entities |
| Agent Wallet | A wallet whose key is held by an autonomous process rather than a human. | Agent Wallets |
| Capability | A scoped, expirable, metered permission that bounds what an agent wallet can do. | Capabilities |
| Helix | The Plonky3 STARK proof sidecar that produces recursive checkpoint proofs across the council. | Helix |
| Identity and Credentials | Decentralized Identifiers (DIDs) and W3C Verifiable Credentials issued on-chain. | Identity |
| Recovery | Threshold-based key recovery for organizational succession and key loss. | Recovery |
| Access Lists | Entity-level blacklists and trusted counterparty lists. | Access Lists |
Where to Go Next
- Developers building with the SDK: Go SDK or TypeScript SDK
- Integrating autonomous agents: Agent Wallets overview
- Deploying smart contracts: Writing Smart Contracts guide
- REST API reference: TMS overview
- Theory and terminology: Glossary of Terms