note: developer docs are coming soon.

Abstract: Programmability over Privacy.

The most essential primitive in digital assets is the ability to send and receive assets.

Without this critical ability, all other utilities are rendered useless. Wallets, DeFi, trading… nothing makes sense if you can’t send and receive.

For full utility, safety, sovereignty and freedom of programmable money to exist, we MUST have programmability AND privacy.

To date, there is no reasonable, scalable and regulatory-compliant method of achieving privacy in mass transact-ability. The ability we have on blockchains to transmit capital, are not institution-ready from a point of programmability in the way that they are in TradFi.

Institutions, agentic, developers, and users DEMAND this level of control by design as well as regulatory-ready privacy.

The Problem:

There are 5 main methods of achieving private transactions:

1. Mixing
2. Tumbling
3. Shielded Pools
4. Private Blockchains with ZK
5. Cryptography: FHE, TEE etc

Overall this speaks to the “privacy trilemma”:

1. Commingling (mostly illegal, liquidity requirements and MEV issues make them unscalable in volume or asset type)
2. Cryptography - expensive, complex, hard to scale. Many are a “front” for essentially being a shielded pool
3. Private Blockchains - the antithesis of onchain

Mixing, tumbling and shielded pools are the closest thing onchain that regulators around the world see as money laundering. This may seem like a broad brush to paint an industry, however that’s how regulators see the issues at hand.