Assets & ownership
Private ZEN completed the real-mainnet round trip. NFT custody and RWA-style eligibility are separate local experiments that explore how the wallet could extend.
What has been demonstrated
| Asset or capability | Environment | Scope |
|---|---|---|
| ZEN | MAINNET TESTED | Activate, approve, shield, private A → B send, partial unshield and public claim. |
| ETH | Horizen mainnet | Public gas and request fees. ETH shielding is not enabled in this mainnet deployment. |
| Demo ZEN / DZEN | LOCAL FIXTURE | Fungible token lifecycle in the isolated development chain. |
| NFT receipt | LOCAL FIXTURE | Custody of a test ERC-721, private transfer of an indivisible redemption entitlement, then public redemption. |
| RWA-style token | LOCAL FIXTURE | Fictional eligibility-gated token and application checks for a fixed test participant set. |
| Live RWA issuer integration | Not implemented | No issuer onboarding, legal ownership registry or production eligibility integration is established by these fixtures. |
The mainnet report covers ZEN only. Local fixtures should not be read as evidence that arbitrary tokens or real NFT collections are currently supported by the mainnet private wallet.
NFT ownership through a private receipt
The local NFT experiment separates public custody of the original ERC-721 from the right to redeem it. The private application transfers that redemption entitlement.
- Deposit the original NFT. The owner approves and places the ERC-721 into the wrapper’s public custody.
- Issue one receipt. The wrapper creates one indivisible, zero-decimal receipt for the specific NFT.
- Shield and transfer the receipt. Vela tracks the private entitlement between registered accounts.
- Unshield and claim it. The entitled account brings the receipt back to its public balance.
- Redeem the original. Burning the receipt and releasing the NFT occur atomically.
A single-NFT receipt is indivisible. The partial-unshield behavior demonstrated with fungible ZEN does not apply to part of one NFT.
RWA-style eligibility
The local fixture uses a fictional token with a fixed eligible test set. It checks admission at the public token layer and inside the private application so that private transfers also respect that fixture’s participant restrictions.
This explores the mechanics of restricted private balances. It does not establish legal ownership, issuer acceptance, real-world backing, redemption rights or integration with a partner such as Lympid.
For a real asset, the issuer’s transfer rules, eligibility lifecycle and redemption requirements would need to be specified and integrated with the token and private application.
What remains before mainnet asset expansion
- Review custody, admission, receipt conservation and redemption for each asset type.
- Define supported tokens and collections explicitly, including decimals, transfer behavior and failure handling.
- Validate account recovery, entitlement recovery and interrupted execution.
- For an issuer-backed asset, agree the actual eligibility and redemption model with the issuer.
- Complete separate end-to-end mainnet evidence for any newly enabled asset.
The wallet can present public holdings and private entitlements in one interface while keeping their backing and visibility rules explicit.