Public chain privacy
The compliance and security entry point for deciding whether a regulated asset can use a public EVM network.
Public EVM networks are useful for transparent asset records, but they are not private databases. A regulated asset can use one only when its programme can tolerate public wallet activity, token events, registry relationships, transaction timing, and contract state.
DALP keeps private evidence out of the chain path where the asset design allows it. It does not make public EVM transactions confidential by default.
Choose the audience path
Compliance and security reviewers
Inspect which addresses, token events, registry links, claim relationships, transaction inputs, and contract state can become visible on public EVM networks.
Architects
Review network, transaction-routing, private-mempool, provider-log, and ordering-risk decisions that sit in the deployment architecture.
Business sponsors
Compare public, permissioned, and private EVM patterns before deciding whether an asset, investor population, and jurisdiction fit public-chain disclosure.
Operators
Run the pre-launch privacy checklist for token metadata, claim topics, event fields, custody handoffs, evidence storage, and approval records.
Short answer
DALP separates public enforcement data from private evidence. Claims, registries, token events, wallet addresses, transaction inputs, and contract state written to a public EVM network remain visible according to that network's behaviour. KYC, KYB, AML, sanctions, beneficial ownership, investor files, and review notes stay off-chain in approved evidence systems.
DALP supports the enforcement pattern through identity registries, trusted issuers, claims, compliance modules, custody integrations, signing workflows, and configured EVM networks. Private mempools, private order flow, privacy frameworks, zero-knowledge proofs, shielded tokens, stealth-address designs, and permissioned network privacy are deployment architecture choices. Select, integrate, operate, and approve them for the specific asset programme before claiming privacy protection.
Decision summary
| If the asset requires | Public EVM fit | Read next |
|---|---|---|
| Public issuance with regulated transfer controls | Suitable only when wallet activity, token events, registry relationships, and contract state can be public. | Public EVM visibility model |
| Private KYC, KYB, AML, sanctions, ownership, or accreditation evidence | Keep evidence off-chain. Publish only claim topics, issuer attestations, and wallet-to-identity links required for enforcement. | Identity and compliance |
| Confidential investor registers or sensitive commercial terms | Do not encode names, account references, private document identifiers, tranche labels, or commercial terms in public metadata, claim data, URIs, or transaction inputs. | Pre-launch privacy review |
| Network-level access control | Use a private or permissioned EVM network. DALP can operate with configured EVM networks, but network privacy comes from the selected network. | Privacy architecture patterns |
DALP boundary
DALP can keep source evidence off-chain, enforce configured eligibility through SMART Protocol contracts, track submitted operations, and index confirmed events for console, API, reporting, and audit review. It does not make public EVM transactions confidential, hide wallet graph relationships, rewrite committed chain data, provide a bridge protocol, or decide the operator's legal basis, retention period, data-transfer mechanism, or privacy notice wording.
Where to go next
| Need | Read next |
|---|---|
| Inspect what becomes visible on public EVM networks | Public EVM visibility model |
| Review pending transaction, mempool, and ordering exposure | Transaction ordering privacy |
| Compare privacy patterns and deployment choices | Privacy architecture patterns |
| Review identity enforcement and claim design | Identity and compliance |
| Review private transaction routing choices | Private mempool routing |
Compliance and security documentation
Inspect controls, identity and compliance responsibilities, transfer restrictions, privacy boundaries, and review evidence.
Public EVM visibility model
What public EVM networks can expose when DALP assets use on-chain eligibility, claims, token events, and transaction history.