No single point of failure
Threshold M-of-N on both chains, run by independent operators. The system keeps running when one node drops.
Proof-backed Canton assets
Vectant issues wrapped assets designed to be backed one to one by reserves in independent multi-signature custody. Vectant is on testnet. A public certificate of reserves and an independent audit are not published yet.
A tokenized asset is only as good as its reserves. Vectant keeps the two jobs separate: reserves are designed to stay locked on the source chain under threshold custody, and the wrapped token lives on Canton. A public certificate of reserves is planned for each instrument before mainnet. None is published today.
Mint an asset and hold its reserves under distributed control. The public backing check comes before mainnet, and it is not available yet.
vETH is on testnet and vSOL is in build, then tokenized gold and securities on the roadmap. Each token is designed to be backed one to one and issued as a 10-decimal CIP-56 holding.
Reserves sit in an M-of-N Safe on EVM or Squads on Solana. No single operator can move funds. The vault is non-upgradeable, with per-transaction and daily caps and a pause switch.
List a token on Canton without building custody, compliance, or reward plumbing. Vectant runs the registry, the vault, and the Canton integration, and routes activity rewards to the venue.
Two mirrored thresholds, held by the same independent operators, govern both sides of the bridge.
Assets are deposited into the source-chain multisig vault. M-of-N operators confirm the deposit.
Vectant mints the wrapped asset one to one on Canton through a CIP-56 registry contract.
Circulating supply is designed to be checked against locked reserves. A public certificate is planned before mainnet and is not published yet.
Burning the Canton token does not move the vault by itself. The same M-of-N threshold has to sign the release on the source chain.
The source-chain multisig is the hard boundary. A compromised Canton side could, at worst, mint an unbacked token. A certificate of reserves is meant to catch that, and that certificate is not published yet.
Threshold M-of-N on both chains, run by independent operators. The system keeps running when one node drops.
Funds can be released only by an M-of-N signature on the source chain. No Canton action can drain the vault.
Fixed contract code, per-transaction and daily caps, a pause switch, and replay guards on every release.
Supply and reserves are designed to be reconciled continuously. A public certificate for every instrument is planned, and none is published yet.
Before any asset reaches mainnet, the vault, the watcher, and the Canton wiring are planned to be independently audited, and a certificate of reserves published. No audit is published yet.
Canton settlement is confidential. Counterparties see only what they need, with permissioning at the ledger level.
Proof of reserves status: no certificate and no audit report are published.
Crypto first, then reserve assets and securities. Third-party tokens can list through the same rails.
Bring an asset to a private, institutional settlement layer without building the hard parts. Vectant provides the custody, the registry, and the Canton rewards routing.
Vectant assets are standard CIP-56 holdings, so a compatible wallet or venue can integrate them. Vectant is partnering with Helvex and Meridiant. That integration is not live yet.
Helvex is the permissioned RFQ desk. Meridiant is isolated-market lending. Vectant assets are not listed on either venue yet.
Issuance, listings, and custody design are described in the product pages. A public contact address is not published on this site yet.