How can we help?How can we help?

Solana is the first supported origin chain, and its asset SOL is bridged as SOLx. Each origin chain is added with its own vault and its own published identifiers. The User Guide lists the supported chains, and a chain appears there when it opens for deposits.

SOLx is SOL on the Canton Network. When you deposit SOL into the bridge, the vault on Solana locks it and the bridge issues the same amount, less fees, to you on Canton as SOLx. Each token the bridge issues works the same way for its own asset. Each is a standard CIP-56 holding issued through Digital Asset's Registry Utility, so it works in any Canton wallet or venue that supports the standard.

Yes, by construction. Fees are removed on the origin chain before anything enters the vault, so the vault locks exactly the amount that is issued on Canton. Every redemption burns the token on Canton before anything leaves the vault. We publish the locked and issued figures for each asset on Proof of Reserves, with RedStone's independent attestation.

No. Your own wallets sign both directions, and we never sign with your authority. On each origin chain, the bridge's on-chain code controls the vault's funds, and no person or company holds a key that can move them. On Solana, the vault is a program-derived address. Releasing funds requires a threshold of independent attestors to sign, and we cannot do it alone. See Security Model.

On the origin chain, the wallets listed for that chain in the User Guide. On Solana, that is any wallet that supports the Wallet Standard, including Phantom and Solflare. On Canton, the wallets PartyLayer supports: Console Wallet, 5N Loop, Cantor8, Bron, Nightly, Cauri Wallet, OneSwap V2 Wallet, Send and Walley, and other Canton wallets over WalletConnect. PartyLayer keeps the current list on its site.

Yes. Tokens on Canton are held by a party, and the bridge issues your tokens to a party ID. Create a Canton wallet first. The bridge cannot create one for you.

No. The bridge moves each asset between its origin chain and Canton, and a bridged token redeems only to its own origin chain: SOLx redeems to SOL on Solana.

Two fees come out of the amount on each leg: our bridge fee, a percentage of the amount (0.125% on Solana), and a flat network fee that covers settlement costs on both chains. The app shows both before you sign, and both are taken on the origin chain in the same transaction. There is nothing else. See Fees and Limits.

Yes, in both directions, and each token has its own. The minimum deposit is set on-chain and shown under the amount field. The minimum redemption is set on Canton. For SOL, the minimum redemption is 0.05 SOLx, and the minimum deposit is Coming soon. Both exist because each transfer has a fixed network cost regardless of size, and below the minimum that cost would exceed the transfer. The minimums for each token are on Fees and Limits.

Consolidate first. The ledger, not the app, refuses a redemption below the minimum. Move smaller holdings together into one, or add to it, then redeem.

A deposit has no maximum. A redemption is capped at whatever the vault can release right now, which the app reads live and shows as your maximum. In normal operation that figure exceeds any single balance.

The bridge reprices it from live network costs. On a deposit you sign a ceiling, shown on the review screen as the most you can be charged, and the vault charges the live value at the moment your transaction lands. If the fee rises above your ceiling between quote and signature, the vault refuses the deposit before anything is sent and the app asks you to reload.

The app quotes an estimate before you start and updates it as stages complete. A deposit takes as long as the origin chain needs to finalize it, about 13 seconds on Solana, plus verification by the attestors. Most complete in a minute or two, then wait for you to accept the offer in your Canton wallet. Redemptions take about the same. The estimate is a typical figure, not a guarantee.

They are waiting for you. On Canton, an incoming transfer is an offer until you accept it in your wallet. Open your Canton wallet, find the incoming transfer, and accept it. The app then shows the transfer as delivered, for example "SOLx delivered".

No. The offer stays open for seven days and the bridge re-offers it automatically if it expires. If it remains unaccepted after that, contact support with the reference from your receipt and we will recover the deposit.

A deposit the bridge has not processed within three days of finalizing on the origin chain can no longer be issued on Canton. The bridge instead refunds it to the depositing wallet within one further day. The refund returns the net amount. The deposit-side fees were already paid. Past that window a deposit needs manual recovery, so contact support with the deposit reference from your receipt.

They complete when service resumes. The bridge checks before you sign whether it can complete a transfer end to end, and refuses to start one it cannot finish. A deposit that has been locked will be issued, and a redemption that has been burned will be paid out. See Status.

Yes. Once your wallet has signed, the transfer completes on its own. Reopening the app resumes tracking from the activity log stored in your browser.

Yes. Enter any address on the token's origin chain as the destination, for example an exchange deposit address. The app warns prominently when the destination is not your connected wallet, and offers a one-click return to it. Check a pasted address carefully. A release cannot be reversed.

Yes. Enter their party ID as the Canton recipient. They will receive the offer and must accept it in their wallet.

No. Only the deposit transaction the app builds is a recognized deposit. A plain transfer to the vault's address does not issue anything on Canton and requires manual recovery. Always use the app.

Check the address bar against the address published on Verified Deployments, and compare the vault and party identifiers your wallets show against the same page. We never contact you first to ask you to bridge and never ask for a wallet's secret recovery phrase.

Proof of Reserves shows locked against issued for each asset and gives a recipe for reproducing the comparison from public explorers and RedStone's published attestation.

Yes, by Halborn, in three completed engagements covering the Solana smart contracts, the Daml smart contracts, and a penetration test of the off-chain relayer. Halborn has not yet published the reports. The scope of each is on the Audit page, and partners can request the reports in the meantime.

Email inquiries@memora.systems.

Memora anchors a cryptographic fingerprint of your document on the Canton Network so that anyone you authorize can verify the document is authentic and unchanged, without seeing its content. Your browser encrypts the document itself, and we never hold a key that can decrypt it.

When you upload, your browser computes the document's SHA-256 hash and encrypts the file. The hash and the metadata you choose are anchored on Canton and disclosed only to the parties you name. The encrypted file is stored off-chain. Verifying a document later means hashing your copy and comparing it to the anchored hash.

No. You use a web application with a passkey sign-in. You do not interact with the Canton Network directly, and you do not handle keys, gas or nodes.

No. The web app is the product. You do not install a DAR, run a validator or hold Canton Coin.

Sign up with a passkey, save your one-time recovery code, and upload your first document. The app creates a workspace for you automatically. Invite colleagues from Settings.

Encrypted, off-chain, identified by their content. Only the hash and the metadata you choose to anchor are on the Canton Network. The integrity of the stored file is checked against the ledger whenever it is read.

Any file type. The app hashes and encrypts the bytes regardless of format.

Cost, privacy and permanence. A SHA-256 hash is 32 bytes. It proves integrity without exposing content, and it cannot be reversed to recover the document. Putting content on a ledger would make it permanent and more expensive, and would expose it to anyone who can see the record.

No. Your browser encrypts content with keys only your passkey and recovery code can unlock. We store ciphertext and wrapped keys we cannot use. See Privacy and Encryption.

Sign in on another device with your recovery code and enroll a new passkey. If you lose every device and your recovery code, and your workspace has not enabled recovery, your documents cannot be recovered by anyone. Print the code or store it in a password manager.

From the document, share to a recipient's email. The app re-wraps the document's key to their public key, so only they can decrypt it. You can revoke access at any time.

A short fingerprint of a contact's public key. Comparing safety numbers over another channel confirms you are sharing with the right person and not with a substituted key. The app warns and blocks if a contact's key changes.

They hash their copy and compare it to the anchored hash, either in the app or with any SHA-256 tool against the hash shown on the document's page. A match proves the file is byte for byte the attested document.

No. A hash cannot be reversed to recover the original document.

Yes. We can attest completed envelopes automatically, and they appear with a DocuSign provenance badge. Because automated ingestion passes the signed document through our servers to be hashed, it is an explicit opt-in and is not end-to-end encrypted in the way manual uploads are. See DocuSign Integration.

DocuSign today. For others, download the completed document and upload it manually, which is end-to-end encrypted.

Yes. The API reference covers batch submission, status polling and retrieval.

Coming soon

Coming soon

Your browser encrypts content, and we never hold a key that can decrypt it. Anchored data on Canton is visible only to the parties you name. The application has undergone an independent security assessment whose findings were resolved. The detail is on Privacy and Encryption.

A blockchain built for regulated finance, on which a party sees a contract only if it is a stakeholder in it.

Because selective disclosure is native to it. Most public ledgers make every transaction public. Canton lets you prove something to a counterparty and to no one else.

An anchored attestation is a machine-checkable record. Downstream systems can verify that an agreement exists and is unchanged before acting on it, whether that is releasing a payment, opening an account or closing a workflow step, without a human re-checking the document.