Wallets
A wallet is a cryptographic keypair with an on-chain address. It is the signing identity for every action on ULedger. No transaction can be committed without a wallet's signature.
Core Properties
| Property | Description |
|---|---|
address | SHA-256 hash of the lowercase-encoded public key. Deterministic and collision-resistant. |
publicKey | The wallet's public key (hex-encoded). |
keyType | The cryptographic algorithm fixed at wallet creation. See Key Algorithms. |
parent | Address of the parent wallet. Empty for root wallets. |
enabled | Whether the wallet can submit transactions. Disabling is immediate and cascades to all children. |
satelliteWallets | List of child wallet addresses created by this wallet. |
authGroups | CRUD permission groups controlling what this wallet can authorize others to do. |
Hierarchy
Wallets form a parent-child tree. A root wallet has no parent. Every wallet it creates becomes a child (satellite wallet), and those children can create further children.
Root wallet
├── Child wallet A
│ └── Grandchild wallet A1
└── Child wallet B
Cascade disable: when a wallet is disabled, all descendant wallets are disabled with it via a breadth-first traversal. Re-enabling requires the parent's authorization. This makes organizational account suspension instant and comprehensive.
Key Algorithms
The key algorithm for a wallet is fixed when the wallet is created. All wallets on a given chain share the same algorithm.
| Algorithm | Type | Post-quantum |
|---|---|---|
secp256k1 | ECDSA (same as Bitcoin/Ethereum) | No |
ed25519 | EdDSA (compact, fast verification) | No |
bls12377 | BLS pairing-based (aggregate signatures) | No |
mldsa87 | ML-DSA-87 / CRYSTALS-Dilithium level 5 | Yes |
Use mldsa87 for deployments that require long-term tamper evidence or quantum resistance.
Agent Wallets
A wallet whose key is held by an autonomous process (AI system, automated service) rather than a human is called an agent wallet. Protocol-level, it is identical to any other wallet. What distinguishes it is ownership, entity association, and the capability bounds placed on it by its human parent.
For the full agent wallet model see Agent Wallets.
Detailed References
- Wallet concepts (agent-wallets section) - full field reference, auth groups, permission groups, parent-child rules
- Wallet System (Glossary) - enterprise hierarchy patterns, cascade algorithm detail
- Go SDK wallet operations