Smart-contract operations exposed under demos.run.contracts.
IMPORTANT — these do NOT go through the shared fee-cap runner. Unlike the
other demos.run.* namespaces, contract deploy/call are RPC-native:
they execute directly over demos.rpcCall and return the contract's own
result types (ContractInstance, ContractCallResult, gas bigint),
never a ProgrammaticTxResult. There is no separate
confirm → broadcast stage here, so ProgrammaticTxOptions
(maxFee, confirm, wait) do not apply.
NOTE: like ipfs.* and d402.pay, the smart-contract path is not
enabled on production nodes yet — these methods are wired and typed but
cannot be exercised end-to-end until the network turns the feature on.
The namespace is a thin, uniform surface over DemosContracts;
instantiate-free access for callers who want everything under
demos.run.*.
Smart-contract operations exposed under
demos.run.contracts.IMPORTANT — these do NOT go through the shared fee-cap runner. Unlike the other
demos.run.*namespaces, contract deploy/call are RPC-native: they execute directly overdemos.rpcCalland return the contract's own result types (ContractInstance,ContractCallResult, gasbigint), never a ProgrammaticTxResult. There is no separateconfirm → broadcaststage here, so ProgrammaticTxOptions (maxFee,confirm,wait) do not apply.NOTE: like
ipfs.*andd402.pay, the smart-contract path is not enabled on production nodes yet — these methods are wired and typed but cannot be exercised end-to-end until the network turns the feature on.The namespace is a thin, uniform surface over DemosContracts; instantiate-free access for callers who want everything under
demos.run.*.