Skip to content
Keyless Trust
Launch
NEAR…

Verify

The contract has no key that can move the vaults by itself.

Keylessness here means the NEAR account has no full-access key, and Solana vaults are Ed25519 addresses derived by Chain Signatures. The contract will only ask the MPC to sign a refund, a capped sweep, one pinned Meteora DBC create-and-buy, or a pro-rata distribution.

  1. 1 · Access keys

    view_access_key_list

    Reading m10.keyless-trust-dev-54ef71.testnet…

    m10.keyless-trust-dev-54ef71.testnet on NEARBlocks testnet

  2. 2 · MPC

    Chain Signatures

    Signer
    v1.signer-prod.testnet
    Domain
    1 · Ed25519
    DBC program
    —

    Paths come from the contract. The predecessor is the contract id. domain_id 1 selects Ed25519. The Solana address is the derived public key with the ed25519: prefix removed.

  3. 3 · Paths for Trust 1

    derivation_paths

    Loading paths…

    A contributor path is trust/<id>/in/<pubkey> and appears once you pass that pubkey.

  4. 4 · Live transactions

    Deploy and launch

    The launch transaction is the Meteora DBC create-and-buy signed for the m10 raise vault. The relayer paid the fee. The vault addresses are the derived keys, not a keypair in this app.

What this does not prove

The MPC signer set could collectively sign any payload. That is the Chain Signatures assumption. A watcher can delay a raise or skew credits among registered contributors. It cannot add a destination the contract did not pin. This page reads public RPC data. It does not hold a key.