Use Switchboard on-demand feeds on Iota:
store job definitions and create aggregators
crank updates using Iota transactions (pull model)
consume results in Move with freshness/deviation checks
OperatorPolicy exists (Iota network, signer custody, RPC allowlist).
OperatorPolicy
network (mainnet/testnet)
RPC endpoint
crossbarUrl (default: https://crossbar.switchboard.xyz)
crossbarUrl
https://crossbar.switchboard.xyz
aggregator/feed object IDs
safety policy (staleness/deviation/min responses) only if risk-sensitive
Pull-based: updates must be executed client-side.
Transaction ordering matters: update before consume.
Resolve Switchboard state/queue for the network.
Store jobs (if creating a new feed) and initialize aggregator.
Fetch update transaction/actions and execute them.
Call consumer Move function after update actions.
Enforce staleness/deviation in Move.
https://docs.switchboard.xyz/docs-by-chain/iota
https://docs.switchboard.xyz/tooling/crossbar
Last updated 11 days ago