h-Asset Family
SIMULATEDOne wrapper standard, several source chains
Helix's institutional wrapper standard is not XDC-specific. The same vault, attestation layer and anonymizer apply to any yield-bearing asset, with Starknet as the confidential settlement venue for all of them.
hstXDC
Helix Staked XDC
XDC locked in a Helix masternode, represented as a value-accruing liquid staking token on Starknet and shieldable in the STRK20 pool.
Attested by a single Helix signer today; m-of-n quorum is implemented and tested.
0x00000000…000000hCC
Helix Canton Coin
Helix operates a Canton Network mainnet validator. hCC applies the same vault, attestation and anonymizer pattern to Canton Coin, bringing a privacy-native asset onto a public chain without giving up its confidentiality.
Validator running. No hCC has been issued — the registry reflects that honestly.
hXLM
Helix Stellar Lumens
Stellar-sourced collateral under the same wrapper standard, settling confidentially on Starknet alongside the rest of the family.
Design stage.
Why the pattern generalises
Canton is already a privacy-oriented network with sub-transaction visibility. hCC on STRK20 extends that confidentiality model to a public chain.
Vault
An ERC-4626-shaped vault prices shares against custodied assets. Nothing in it is XDC-specific — swap the underlying and the arithmetic is unchanged.
Attestation
A quorum-gated oracle carries source-chain state onto Starknet, with staleness limits and a circuit breaker that do not care which chain is being observed.
Anonymizer
A helper contract lets the pool move value in and out of the vault without revealing who asked. One contract per asset, one pattern for all of them.
Institutions already accept Canton's confidentiality model. The obstacle to using a public chain has been that it offers no equivalent. That is the gap this closes — and it is why the second asset in the family matters more than the first.