Internet Computer

How do chain-key signatures, vetKeys and exchange rates work from a cloud engine?

All help topics

These services rely on keys and canisters on other subnets that charge cycles per call, so an engine canister reaches them through the engine's proxy canister.

The services
  • Chain-key signatures: threshold ECDSA and Schnorr. A subnet signs together without any single node holding the key, which lets canisters hold and spend Bitcoin and Ethereum.
  • vetKeys (vetKD): the network derives an encryption key for a canister and delivers it encrypted under a key the user's device supplies, so no node sees it. The same canister, context and input always give the same key. Used for end-to-end encrypted data.
  • Exchange-rate canister (XRC): live exchange rates on chain.
  • Bitcoin API, EVM RPC and SOL RPC: read and send transactions on Bitcoin, Ethereum and other EVM chains, and Solana.
Why a proxy

Cloud engines hold no threshold keys, and an engine canister can't send a cycle-bearing call across subnets. A proxy canister sits on an ordinary subnet with cycles of its own: your canister makes a cycle-free, bounded-wait call to it, and the proxy makes the paid call and passes back the raw reply.

Getting and calling one
  • The engine owner deploys it: engine, Integrations, Proxy canisters, Deploy a proxy. It is paid from the engine's balance and topped up from it when low; no card is charged.
  • Give its id to your app as configuration, for example the environment variable PROXY_CANISTER_ID. Every canister on the engine may call it, and it relays only the services above.
  • Call proxy with canister_id (the target), method, args (the target method's argument, Candid-encoded) and cycles (what the proxy should attach). Signing or deriving with key_1 costs 26,153,846,153 cycles, with test_key_1 10,000,000,000; public-key methods are free. Over-attaching is safe, as the unused part returns to the proxy. Never attach cycles to the call to the proxy itself.
  • Errors: InsufficientCycles (its balance is short), UnauthorizedUser (the caller isn't on the engine), CallFailed (the target refused, or the outcome is unknown, so don't assume nothing happened).
Keys belong to the proxy
  • The proxy keeps each calling canister's keys separate, so one canister can never sign or decrypt with another's.
  • Keys depend on which proxy you call. Another proxy gives different keys and addresses, and deleting a proxy loses its keys for good: Bitcoin or Ethereum held at addresses derived through it can no longer be moved. Treat a signing app's proxy as permanent.
  • Don't send HTTPS outcalls through the proxy: make them from your own canister, where they are free.
Learn more

More about the same page

Still stuck? Contact support