Canton
RedStone integrates with the Canton Network to provide dApps with fresh, verifiable oracle data while respecting Canton’s privacy-by-design ledger model.
Canton differs from traditional EVMs by not exposing a global public state. Each participant node sees only the contracts and data it is involved in, while a synchronizer orders transactions without accessing their contents.
RedStone supports two integration models on Canton:
- Pull Model — oracle data is supplied directly inside a transaction, with no persistent on-ledger storage. It fits Canton’s selective-disclosure model naturally: the data stays visible only to the parties executing the transaction.
- Push Model — an off-chain relayer periodically writes aggregated price data to an adapter contract on the ledger, so consumers can read the latest prices at any time without supplying a payload. It also gives the authorized parties a single, canonical reference price on the ledger — instead of each pulling its own payload and possibly arriving at a slightly different value.
Pull Model
The RedStone Pull model integrates naturally with the Canton network’s architecture, enabling dApps to access fresh,
Push Model
In the RedStone Push model, price data is persisted on the Canton ledger. An off-chain relayer periodically