Shamwari recognises that real-world financial systems are populated by legally distinct actors. Ten account types, from licensed banks to autonomous AI agents, each with protocol-enforced permissions secured by NIST post-quantum cryptography. No anonymous addresses. Every participant is typed, accountable, and verifiable.
Every Shamwari account has a declared type that determines its transactional capabilities at the consensus layer. Account type restrictions are enforced at gate 4 of the 7-gate transaction validation pipeline before any balance changes occur. No application-layer override is possible.
Every Shamwari account is secured by two NIST-standardised post-quantum keys: a Dilithium signing key and a Kyber encryption key, both derived from a single BIP39-adapted seed phrase. This is the first blockchain wallet architecture to deploy both NIST FIPS 203 and FIPS 204 as the primary (and only) cryptographic layer.
Every transaction submitted by the account is signed with this key. The 2420-byte Dilithium signature is included in the transaction body and verified by every network node at gate 1 of the consensus pipeline. This is also the key used by forger nodes for generating block signatures.
The account’s Kyber public key is stored on-chain and used by other accounts and the protocol to encrypt data destined for this account. Only the account holder with the corresponding Kyber private key can decrypt it. Used for all sensitive on-chain data.
The 2112-byte combined public key (800B Kyber + 1312B Dilithium) is stored in the account table on activation. Account ID is derived from the Dilithium public key hash. No private key data is ever exposed or stored on the blockchain.
One seed phrase recovers both PQC keys on any device. Deterministic derivation means the same words always produce the same keys. No cloud backup, no second phrase, no key file required.
Human-friendly account addresses are generated from the COMBINED PUBLIC KEY to create a : SHAMWARI-XXXX-XXXX-XXXX-XXXXX format type. These addresses are used to reference accounts across the blockchain from transaction submissions to database entry and querying.
Shamwari accounts can have set plain general information and also store identity metadata on-chain i.e. legal names, contact information, jurisdiction identifiers, personal identity information encrypted with the account’s Kyber public key. The encrypted data ciphertext is permanently stored on-chain; only the account holder can decrypt and read or share it.
CHAIN_ADMIN accounts store Kyber-encrypted KYC attestation data in BetaChainPermission records when granting CHAIN_USER access. This creates a permanent, cryptographically-anchored on-chain record of every KYC onboarding event — including timestamp, granting institution, and encrypted evidence reference.
Every account can register a Shamwari native domain in the .shamwari.network namespace. Domains are stored on-chain, valid for approximately 1 year (365 × ~7200 blocks), and automatically expire without renewal. All domain lifecycle events are consensus transactions.
AccountType.AUTONOMOUS is purpose-built for AI agents that need to transact on-chain. Hard spending limits, transaction type whitelists, recipient restrictions, and rolling window caps are all enforced at the consensus layer and not in off-chain monitoring software that can be bypassed or overridden.
Autonomous agents execute trades on the Totem Exchange within hard on-chain limits e.g max position size, permitted asset classes, daily volume cap. No off-chain monitoring needed. The blockchain enforces it.
MFI agents process applications, verify credit scores, and disburse approved loans automatically with the protocol enforcing disbursement limits and approved recipient lists at consensus.
Autonomous treasury agents manage subscription payments, supplier invoices, and dividend distributions within governance-approved parameters. Zero manual intervention. Zero bypass possible.
Create and manage Shamwari accounts with the full suite of identity, domain, and key management tools.