Verified Deployments

The vault addresses, program IDs and party identifiers of the real Memora bridge on each chain, so you can confirm you are using it and not a lookalike.

Before you sign, compare what your wallets show you against the identifiers below. They are the only identifiers the real Memora bridge uses. If anything differs, stop and contact us.

Three rules that never change:

The bridge app is served from one address: Coming soon. Bookmark it.
We never ask you to send tokens directly to a vault address. The only way to deposit is the transaction the app builds for your wallet to sign.
We never contact you first to ask you to bridge, and never ask for a wallet's secret recovery phrase.

Each origin chain has its own deployment: a vault on that chain, a bridge instance on Canton, and an attestor set. Each has its own section, and we list a chain here before it opens for deposits. The image files for each token, and for Memora, are on Brand Assets.

Solana mainnet

On Solana

Vault program ID: Coming soon
Vault authority (program-derived address): Coming soon
Vault token account: Coming soon
Accepted mint (wrapped SOL): So11111111111111111111111111111111111111112
Native SOL deposits are wrapped inside your own transaction and unwrapped on release, so you never hold wrapped SOL yourself.
Program upgrade authority: Coming soon

On Canton

Bridge package name and version: Coming soon
SOLx instrument ID: Coming soon
Your Canton wallet shows this on the holding.
Instrument admin party (registrar): Coming soon
Receiver party: Coming soon
A redemption is a transfer to this party; your wallet shows it as the recipient when you redeem.

Attestor set

Attestor public keys: Coming soon

Solana devnet

The devnet deployment is for testing only and carries test tokens with no value. We publish its identifiers here so you can verify test integrations the same way. We redeployed the vault program on 26 September 2026. The earlier program, DzvEuMU3fWxBh4SHnkFQYuTM14Wni8K5kQpmUeHFHqTZ, is retired, and nothing should be sent to it.

On Solana devnet

Vault program ID: Cw5PjX3UAL8JXGtwpvjFTZBAqiGw5u1NfYMU8tqksw9q
Solana explorer
Vault token account: ApJQV2rgXpqEhzTGjrBzqHWo3xWXn61GPAwJscCJoJUD
Solana explorer
Accepted mint (wrapped SOL): So11111111111111111111111111111111111111112
Solana explorer
Bridge fee account: 7dDpTCQkZFbCVkzhxHB7VDe1Y3tWtQu1WfmhgKSacZdr
Solana explorer
Network fee account: EaQF7aDTyvekxcmpABNekdndQR3nvtXsWtZjvEYkECmz
Solana explorer
Program upgrade authority: DLKmvtLsbCAacAix1dwqCBgbmSZHX1LCHmxMPXsoU1iS
Solana explorer

On Canton devnet

SOLx instrument ID: SOLx
Your Canton wallet shows this on the holding.
Instrument admin party (registrar): memora-dp-devnet::122045e74bfb457641b17d46197dfd282c55fdd0aff5ffcaab9628fab422f6741e79
Lighthouse
Receiver party: recipient-d4d95138::1220ef595823ea6cfca972724c629d69cb991b2af4a82b20f7678ac3b9ed29716a32
Lighthouse

RedStone's reading of the devnet vault

Data service: redstone-primary-prod
Package: __MEMORA__
Balance feed: MEMORA_DEVNET_LAMPORTS
The vault balance, in lamports.
Slot feed: MEMORA_DEVNET_SLOT
The slot of the vault's last change.
Block time feed: MEMORA_DEVNET_BLOCK_TIMESTAMP
That block's time, in Unix seconds.
Gateway: https://oracle-gateway-1.a.redstone.finance/data-packages/latest/redstone-primary-prod
RedStone
Signers: 0x9c5AE89C4Af6aA32cE58588DBaF90d18a855B6de0xdEB22f54738d54976C4c0fe5ce6d408E40d884990x8BB8F32Df04c8b654987DAaeD53D6B6091e3B7740x51Ce04Be4b3E32572C4Ec9135221d0691Ba7d2020xDD682daEC5A90dD295d14DA4b0bec9281017b5bE
A reading counts when at least three of the five have signed the same balance, slot and block time.

The two fee accounts receive the fees split off a deposit. They are not collateral and are not counted as reserves. RedStone reads the devnet vault independently and publishes what it finds as signed data packages. Proof of Reserves explains how to fetch and check them.

How to check

A deposit

Before approving in your wallet on the origin chain, the wallet's transaction preview shows the program or contract being called. It must be the vault listed above for that chain: on Solana, the vault program ID.

A redemption

Before approving in your Canton wallet, the wallet shows the recipient party. It must be the receiver party listed for the token's origin chain.

A bridged token

Your Canton wallet shows the instrument ID and admin party on any holding. They must match the values listed for that token. A token issued by any other admin party is not ours, whatever its name.

The reserves

Proof of Reserves explains how to read each vault's balance and compare it against issued supply.

Changes to this page

Identifiers on this page change only with a scheduled upgrade of a vault or of the Canton package, or when we add an origin chain. We announce each in advance on Status. If you see an identifier that differs from this page and there has been no announcement, treat it as fraudulent and report it to inquiries@memora.systems.