Expand description
API interaction modules for the OneMoney SDK.
Re-exports§
pub use crate::client::Client;pub use crate::client::ClientBuilder;pub use crate::client::Network;
Modules§
- accounts
- Account-related API operations.
- chains
- Chain-related API operations.
- checkpoints
- Checkpoint-related API operations.
- common
- Common types used throughout the OneMoney SDK.
- crypto
- Cryptographic utilities for signing and address derivation.
- governance
- Governance and epoch-related API operations.
- multisig
- Multi-signature account API endpoints.
- requests
- API request type definitions.
- responses
- API response type definitions.
- tokens
- Token-related API operations.
- transaction
- transactions
- Transaction-related API operations.
Structs§
- AccountBB
Nonce - Account BB nonce information from API response. Matches the L1 server’s AccountInfo structure: { “bbnonce”: u64 }
- Account
Nonce - Account nonce information from API response. Matches the L1 server’s AccountInfo structure: { “nonce”: u64 }
- Associated
Token Account - Represents the token holdings and associated data for a specific address.
- Chain
IdResponse - Response type for chain ID endpoint
- Checkpoint
- A checkpoint includes header data and transactions. Header fields are flattened at the top level to match L1 server format.
- Checkpoint
Number - Checkpoint number response.
- Epoch
Response - Response containing epoch information and certificate data
- FeeEstimate
- Fee estimation result. Matches L1 server’s EstimateFee structure: { “fee”: String }
- FeeEstimate
Request - Fee estimation request. Matches L1 server’s EstimateFeeRequest structure with string query parameters.
- Finalized
Transaction - A finalized transaction with epoch confirmation and validator BLS signatures.
- Hash
- Represents a transaction hash returned by the API.
- Hash
With Token - Represents a transaction hash and the token that created by the transaction.
- MetadataKV
Pair - The additional key-value properties for one token.
- Mint
Info MintInfois the struct for token contract. One mint account represents one token.- Minter
Allowance - Multi
SigSignature Entry - Multi-signature entry containing both the signature and the signer’s public key
- Multi
SigSigner Info - Multi-signature signer information for REST API
- Payment
Transaction Request - Payment transaction request.
- Rest
BlsAggregate Signature - BLS aggregate signature representation for REST API. Contains the aggregated signature, signer bitmask, and validator public keys needed for verification.
- Rest
Signature - ECDSA signature components.
- Token
Authority Request - Token authority management request.
- Token
Blacklist Request - Blacklist request for managing token blacklists
- Token
Bridge AndMint Request - Token bridge and mint request.
- Token
Burn AndBridge Request - Token burn and bridge request.
- Token
Burn Request - Token burn request.
- Token
Clawback Query - Query parameters for token clawback operations.
- Token
Clawback Request - Request parameters for token clawback.
- Token
Issue Request - Request parameters for the token issue.
- Token
Metadata - Token metadata for one token.
- Token
Metadata Update Request - Token metadata update request.
- Token
Mint Request - Request parameters for the token mint.
- Token
Pause Request - Token pause request.
- Token
Whitelist Request - Whitelist request for managing token whitelists
- Transaction
- Transaction
Receipt - Transaction receipt response. Matches L1 server’s TransactionReceipt structure with proper types.
- Transaction
Response - Generic transaction response from API operations. All transaction operations return the same format: {“hash”: “string”} Used by payment transactions, token operations, etc.
Enums§
- Action
Type - Transaction action types.
- Certificate
Data - The encoding format determines which variant is used:
- Checkpoint
Transactions - Checkpoint transactions representation. This can be either transaction hashes or full transaction objects.
- Transaction
Signature - Transaction signature type - either single signature or multi-signature
- TxPayload
- Instructions supported by mint token
Type Aliases§
- Nonce
- Nonce type from L1 primitives