Four layers. One conversation.
Acacia names four levers: asset tokenisation, money tokenisation, interoperability, regulation. In practice they don't decouple - and neither do we.
Issuance & full lifecycle
We take an asset on-chain - fixed income, securitised products, private markets, carbon - and design issuance, registry, corporate actions and redemption so it stands up as a security, not a wrapper.
wCBDC, deposit tokens, stablecoins
We pick the money-leg that actually settles - central bank money (wCBDC, ESAs), tokenised commercial bank money (deposit tokens), regulated stablecoins - and the right pattern for it: atomic DvP, PvP, or synchronisation across rails.
Cross-chain & cross-rail design
Bridges, HTLC coordination and ledger synchronisation across traditional FMIs (RITS, Austraclear, CHESS), public chains and permissioned networks. Designed up front, so it doesn't become next year's integration problem.
Sandbox-ready experiment design
We frame DFMI sandbox and ASIC ERS submissions so settlement finality, prudential treatment, AML/CTF and consumer protection are answered in the design - before the regulator's first round of questions, not after.
Three starting points, depending on where you sit.
If you're an issuer
- Tokenise corporate bonds, securitised products or private credit on a DLT that fits your distributors and investor base - not the one with the loudest pitch.
- Pick the cash-leg your counterparties will actually accept: wCBDC, deposit tokens, or regulated stablecoin, with a settlement model that maps to how they clear today.
- Design the disclosure, registry and corporate-actions layer so the token holds up as a security under audit, not just under demo.
If you're a bank or FMI
- Build a deposit-token thesis with bank-on-bank interoperability designed in - without locking into a single rail prematurely.
- Connect existing infrastructure (RITS, Austraclear, CHESS, core ledger) to tokenised asset platforms with a clear settlement and reconciliation path.
- Define your wCBDC distribution role for the next pilot round, with the technical and prudential implications mapped.
If you're a platform or PSP
- Plug tokenised assets and tokenised money into your existing wallet, custody or trading stack - without rebuilding the product around them.
- Shape a sandbox submission end-to-end: technical design, legal mapping, regulator engagement.
- Bridge public-chain liquidity to Australian regulated rails with a model that holds for compliance and treasury.
Engineers, not advisors.
What we leave behind is built to be implemented - data models, settlement flows, reference code, sandbox submissions. Your team picks up where we stop, or we keep building. Nothing gets laminated.
Vendor-neutral by construction.
We're not paid by a chain, a stablecoin issuer, or an FMI. What we recommend is what we'd build - not what we'd resell.
Acacia-fluent, regulator-fluent.
We speak the vocabulary the report and the regulator use - ESAs, wCBDC, ASIC ERS, DFMI sandbox - so the design lands in the room without translation.
Let's build