Crate pallet_circuit
source ·Expand description
Overview
Circuit MVP
Re-exports
pub use crate::pallet::*;
Modules
- The
pallet
module in each FRAME pallet hosts the most important items needed to construct this pallet. - Autogenerated weights for pallet_circuit_circuit_portal
Macros
Structs
- Inbound Steps that specifie expected data deposited by relayers back to the Circuit after each step
- Outbound Step that specifies expected transmission medium for relayers connecting with that gateway. Request message format that derivative of could be compatible with JSON-RPC API with either signed or unsigned payload or custom transmission medium like XCMP protocol
- A struct that encodes RPC parameters required for a call to a smart-contract.
- A representation of a signal
- Outbound Step that specifies expected transmission medium for relayers connecting with that gateway. Extra payload in case the message is signed ro has other custom parameters required by linking protocol.
- Describe ABI configuration for a gateway so that it’s possible to cast types of inbound and outbound messages to that gateway
- Structure used at gateway registration as a starting point for multi-finality-verifier
- Payload used by this example crate to hold price data required to submit a transaction.
- All Executors from the active set can bid for SFX executions in order to claim the rewards (max_fee) set by users, ultimately competing against one another on the open market rules. In case bid goes on Optimistic SFX, Executor will also have their bonded stake reserve to insure other Optimistic Executors co-executing given Xtx with their bonded collateral (reserved_bond) Their balance
- Simple blob to hold an extrinsic without committing to its format and ensure it is serialized correctly.
- A composable cross-chain (X) transaction that has already been verified to be valid and submittable
- A composable cross-chain (X) transaction that has already been verified to be valid and submittable
Enums
- The possible errors that can happen querying the storage of a contract.
- Inbound Steps that specifie expected data deposited by relayers back to the Circuit after each step
- Inclusion proofs of different tries
- Read latest height of gateway known to a light client
Constants
- Defines application identifier for crypto keys of this module. Every module that deals with signatures needs to declare its unique identifier for its crypto keys. When offchain worker is signing transactions it’s going to request keys of type
KeyTypeId
from the keystore and use the ones it finds to sign the transaction. The keys can be inserted manually via RPC (seeauthor_insertKey
).
Traits
Functions
- Retrieves all available gateways for a given ChainId. Currently returns a vector with a single hardcoded result. Eventually this will search all known gateways on pallet-xdns.
Type Definitions
- Alias to the public key used for this chain, actually a
MultiSigner
. Like the signature, this also isn’t a fixed size when encoded, as different cryptos have different size public keys. - Balance of an account.
- Common types across all runtimes
- A result type of a get storage call.
- A hash of some data used by the chain.
- Index of a transaction in the chain. 32-bit should be plenty.