The canonical wallet and crypto service for the Aurigraph platform (split-key custody in preview) · status as of 2026-10-20
Battua is a universal digital-asset wallet and the canonical wallet and crypto service for the Aurigraph platform. It is designed for a world in which a single private key is both the most valuable secret an organization holds and the most fragile — vulnerable to device loss, insider compromise, and, on a longer horizon, cryptographically-relevant quantum computers. Battua addresses this on three fronts at once: it never assembles a complete private key on any single device, using 2-of-3 Shamir secret sharing / multi-party computation (MPC) for key custody (in progress, AV11-3640); it is designed to sign natively with ML-DSA-87, the highest-strength NIST Category 5 post-quantum signature standard; and it embeds regulatory compliance — the FATF Travel Rule (IVMS 101), AML/KYC screening, and STR/CTR reporting — directly into the transaction path rather than bolting it on afterward.
Battua serves both individuals and enterprises from one account model, spanning crypto, stablecoins, CBDCs, and tokenized real-world assets. This paper describes the custody problem it solves, its cryptographic architecture, its compliance posture, and how it fits into the broader Aurigraph platform as the intended canonical crypto service. For the underlying ledger, consensus, and tokenization substrate, see the Aurigraph DLT whitepaper.
Digital-asset custody has three structural weaknesses that Battua is built to remove.
Single-key risk. In the dominant wallet model, control of an account collapses to a single secret — a seed phrase or a private key. Whoever holds that secret holds the funds. Lose it and the assets are gone; leak it and they are stolen. For an individual this is a personal-security problem; for an enterprise treasury it is an unacceptable single point of failure, with no segregation of duties and no way to require multiple parties to authorize a movement of funds.
The quantum threat. The elliptic-curve signatures (ECDSA over secp256k1) that secure almost every mainstream wallet are vulnerable to Shor's algorithm on a sufficiently capable quantum computer. Because ledgers are public and permanent, this creates a harvest-now, decrypt-later exposure: an adversary can record signatures and public keys today and forge or recover keys years later once the hardware exists. Assets and long-lived contracts secured only by classical curves are therefore already living on borrowed time.
Compliance friction. Regulated institutions cannot simply move value. Cross-border transfers trigger the FATF Travel Rule; counterparties must be screened against sanctions lists; suspicious and large-value activity must be reported. In most wallet stacks these obligations are handled out-of-band, manually, and inconsistently — a source of both operational cost and regulatory risk.
Battua treats these three problems as one design brief: distribute the key so no single party can act alone, sign with post-quantum-resistant cryptography, and make compliance a native property of every transaction.
Status (2026-11-06). This section describes the custody design. MPC 2-of-3 signing is not live: in the current Battua service the shard path is a hash baseline and co-signing is refused until real threshold signing lands (AV11-3959). Shamir split and reconstruct exist; distributed signing does not.
Battua's custody model is designed around 2-of-3 Shamir secret sharing combined with multi-party computation, so that a complete signing key is never held in one place and never fully reassembled outside a protected boundary.
At wallet creation, a master signing key is split into three shards using Shamir secret sharing with a threshold of 2-of-3. Any two shards can jointly reconstruct signing capability; any single shard reveals nothing. The shards are distributed across independent trust domains:
Because the threshold is two, the loss of any single shard is survivable, and no single party — including Aurigraph — can sign transactions alone. This gives individuals resilience against device loss and gives enterprises genuine segregation of duties at the cryptographic layer.
The secret sharing operates over the GF(2⁸) Rijndael finite field — the same field used in AES, defined by the irreducible polynomial 0x11B. This choice yields constant-time field operations (removing timing side-channels), a 256-element field that maps cleanly onto byte operations, and a construction whose security properties have been scrutinized alongside AES for over two decades.
0x11B
On top of shard-based custody, enterprise accounts layer M-of-N multi-signature policies (for example 2-of-3 or 3-of-5) for fund movements above a configured limit, so that both the key itself and the authorization to use it are distributed.
Battua's target signing algorithm is ML-DSA-87 (formerly CRYSTALS-Dilithium), the NIST-standardized lattice-based digital-signature algorithm published as FIPS 204. ML-DSA-87 is implemented; transaction signing with it is on the roadmap. Transactions on external chains (Bitcoin, EVM networks) are signed with those chains' own classical algorithms, such as secp256k1 ECDSA, because those chains cannot verify ML-DSA; this is a named classical exception.
The Aurigraph platform's crypto layer provisions PQC wallets with ML-DSA-87 keys via BouncyCastle 1.86, and the platform default for both the signature and key-encapsulation algorithms is Category 5. The Battua 2-of-3 ML-DSA-87 MPC signer with Shamir secret sharing is in progress (AV11-3640) and is not yet live (hash baseline today, AV11-3959); production signs in-process with BouncyCastle and the CryptoOps gRPC path is scaffolded (AV11-3958); HSM custody is planned, not deployed.
Battua embeds compliance in the transaction path so that a compliant transfer is the default, not an afterthought.
FATF Travel Rule (IVMS 101). For qualifying cross-border transfers, Battua exchanges originator and beneficiary information using the InterVASP Messaging Standard (IVMS 101), implementing FATF Recommendation 16, through an integration with the Notabene Travel Rule network (webhook-driven in the Battua service). The IVMS 101 envelope carries structured originator and beneficiary identity data, national identification, ISO 3166 address data, and originating/beneficiary VASP details, so that required information travels with the transfer automatically rather than being tagged by hand.
AML sanctions screening. Before a transfer is broadcast, counterparties are screened against sanctions lists ingested into the Battua service — the OFAC (US Treasury SDN) list and the UN Security Council consolidated list today — with further list coverage added per jurisdiction as Battua expands.
KYC. Identity verification is tiered by risk and transaction volume, integrating established KYC providers so that verification depth scales with exposure rather than applying uniform friction to every user.
Regulatory reporting (STR/CTR). Battua auto-generates Suspicious Transaction Reports (STR) when AML flags trigger and Cash/Currency Transaction Reports (CTR) above configured thresholds, producing audit-ready output suitable for regulatory submission.
Because compliance state is computed on the same path that signs and settles the transaction, every approval action can be time-stamped and cryptographically signed into an immutable audit trail — turning compliance evidence into a first-class, verifiable artifact.
Within the Aurigraph platform, Battua is designated as the canonical wallet and crypto service. The architectural intent, captured in the platform's crypto-consolidation mandate, is that wallet provisioning, key custody, signing, and verification converge on Battua, so that the platform has one hardened, auditable home for cryptographic operations rather than several parallel implementations.
The platform integrates with Battua through a CryptoOps boundary — a single interface abstraction for cryptographic operations. Behind that interface, the platform can either perform crypto in-process (using its own BouncyCastle post-quantum implementation) or delegate over gRPC to the Battua service. Both modes exist in the codebase and share the same ML-DSA-87 / NIST Category 5 defaults.
CryptoOps
It is important to be precise about the current state rather than overstate it. The gRPC delegation path to Battua is built and available, but it is not the active production path today — the platform currently runs the CryptoOps boundary in its in-process mode, and consumer call-sites have not yet been migrated onto the delegated client. In other words, the V12↔Battua crypto consolidation is an architectural direction that is scaffolded and ready, not a fully-live gRPC integration. This whitepaper describes the target architecture and the boundary that makes it possible; the migration of call-sites onto the delegated Battua path is an in-progress engineering effort, not a shipped end-to-end fact. On the transport itself: Battua→DLT gRPC runs over TLS behind the hybrid post-quantum edge on dlt.aurigraph.io:9004 (verified 2026-10-19), and authentication on Battua's gRPC write operations has been added in code but is not yet deployed.
dlt.aurigraph.io:9004
Battua deliberately serves two audiences from one wallet and one account model.
For individuals, Battua is a single place to hold crypto, stablecoins, CBDCs, and tokenized real-world assets. It offers 2-of-2 split-key custody (preview, signing disabled) with post-quantum key protection, multi-network deposit addresses, instant peer-to-peer transfers with live FX and double-entry ledger accounting, and access to tokenized assets such as gold, real estate, and carbon credits — with a free entry tier and no requirement to manage a raw seed phrase across devices. The same account is served by the Battua web portal, the mobile app (Android, iOS; React Native) and the Battua Wallet browser extension, so a user never juggles separate wallets to reach every feature. Native desktop builds are not shipped today.
For enterprises, Battua adds treasury-grade controls on top of the same foundation: M-of-N multi-signature policies and a maker-checker approval workflow with segregation of duties, built on enterprise accounts with role-gated actions (Admin, Treasurer, Maker and Checker roles are enforced in the Battua service today; further roles are planned). Spending limits can be configured per role, per asset class, and per time window; every transaction generates double-entry accounting suitable for ERP import; and every approval is written into an immutable, cryptographically-signed audit trail. Enterprises can also issue and manage their own tokenized real-world assets on the Aurigraph ledger.
The unifying idea is that the security and compliance machinery — split-key custody (preview), post-quantum signing (roadmap), Travel Rule, screening, reporting — is identical underneath, whether the user is one person protecting personal savings or a treasury team moving institutional funds.
Battua's direction of travel follows from the architecture above:
Roadmap items describe planned and in-progress work and should be read as direction rather than as shipped guarantees.
Battua is built on a simple thesis: the wallet is where custody risk, quantum risk, and compliance risk all converge, so it is where they should all be solved together. By designing custody around 2-of-3 Shamir MPC (not live yet, AV11-3959), signing natively with ML-DSA-87 (FIPS 204) post-quantum cryptography, and making FATF Travel Rule, AML/KYC, and STR/CTR reporting native to the transaction path, Battua offers individuals resilience and enterprises treasury-grade control — from one account, across every device and asset class. As the designated canonical crypto service for the Aurigraph platform, connected through the CryptoOps boundary, it is positioned to become the platform's single, hardened home for cryptographic custody. The consolidation is scaffolded and underway; the cryptographic and compliance foundations are already in place today.
For the ledger, consensus, and tokenization layer that Battua builds on, see the Aurigraph DLT whitepaper.
Explore: About · Products · Features · Whitepapers · Sustainability · Tokenized carbon credits · Real-world asset tokenization · SDK · Blog · Plain-text site index · Sitemap · Contact: contact@aurigraph.io