Integrations

Deploy a proxy canister for Bitcoin, Ethereum, VetKeys or exchange rates

All help topics

The engine owner deploys a proxy canister from Integrations; it makes calls to Bitcoin, Ethereum, VetKeys and the exchange rate canister for your canisters and is paid from the engine's balance.

These features run on other subnets and charge cycles per call, which your engine's canisters can't attach across subnets on their own. A funded proxy makes the calls for them and covers the cost.

  1. Open the engine and choose Integrations in the sidebar.
  2. On the Proxy canisters card, click Deploy a proxy.
  3. In Deploy proxy canister, click Deploy proxy.
  4. When Proxy canister deployed appears, the list opens with the new proxy. Copy its ID from the Proxy canister column: your canisters' code calls the proxy by that ID.

Good to know

  • Only the engine owner can deploy a proxy. Owners and admins see the list; developers see the card only.
  • No card is charged. A proxy starts with a few dollars' worth of cycles from the engine's balance and is topped up from it whenever it runs low. What a proxy is sent is capped every hour and never touches what the engine owes for its nodes.
  • These show in the engine's Balance history as New proxy and Proxy top-up.
  • A deploy is refused when the engine isn't running, has no subnet yet, or another change to its balance is under way. It's also refused when the balance can't spare the cycles a proxy starts with (add funds, then try again) or the hourly billing check is due (try again within the hour).
  • You can deploy more than one proxy, but keys follow the proxy: signing keys, Bitcoin or Ethereum addresses and vetKeys derived through one proxy differ from another's. An app that signs or derives keys should keep using the proxy it started with.
  • A proxy runs on another subnet, not on your engine, so it isn't listed on Software canisters.

More about the same page

Still stuck? Contact support