Cloud Engine Canisters

Rules for canister code on a cloud engine (CloudEngine subnet, e.g. OpenCloud). Engine canisters hold 0 cycles: drop `(with cycles = …)` clauses (IC0504). Cross-subnet calls must be bounded-wait and cycle-free (`(with timeout = N)`, `Call::bounded_wait`) or rejected: 'Unbounded-wait calls and calls with cycles are not allowed to CloudEngine subnets'. HTTPS outcalls use the ordinary wrapper and are free; never via the proxy ('Replicas had different responses'). XRC, threshold ECDSA/Schnorr, vetKD, the Bitcoin API and EVM/SOL RPC go via the engine's proxy canister: ask the user for its id first. Hand-encode arguments: chain-key helpers attach cycles. Derived keys belong to the proxy. AI inference goes through the engine-operator's `inference_request` (it holds the key; never call the provider yourself; set `max_tokens`, outcalls have 30 s). Use when planning, writing or debugging engine canister code, signing or deriving keys, or on these errors. Do NOT use for deploying a proxy (deploy-to-cloud-engine).

jiayaoqijia Updated 81 repo stars

File contents

jiayaoqijia/cryptoskill commit f768884688 Runs: jiayaoqijia/https-outcalls

Frequently asked questions

npx get-skill add jiayaoqijia/cloud-engine-canisters