Struct RateLimits 

pub struct RateLimits {
    pub default_settings: RateLimit,
    pub non_tx_frequency: f64,
    pub non_tx_max_total_size: f64,
    pub tx: HashMap<ProtocolMessageTypes, RateLimit>,
    pub other: HashMap<ProtocolMessageTypes, RateLimit>,
}

Fields

default_settings: RateLimit

non_tx_frequency: f64

non_tx_max_total_size: f64

tx: HashMap<ProtocolMessageTypes, RateLimit>

other: HashMap<ProtocolMessageTypes, RateLimit>

Implementations

impl RateLimits

pub fn extend(&mut self, other: &RateLimits)

Trait Implementations

impl Clone for RateLimits

fn clone(&self) -> RateLimits

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for RateLimits

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl From<&RateLimits> for OpcodeRateLimits

Re-key any Chia limit table onto raw opcodes.

The numbers remain DERIVED — a caller chooses the source table, never the individual limits — so the drift this type exists to prevent stays prevented. A table assembled from V2_RATE_LIMITS (retuned, extended, or narrowed for a test) is exactly as trustworthy as the default.

The module header’s lockstep pin applies undiminished, and a caller-supplied table is the one way to violate it from outside this crate: the keys are chia_protocol::ProtocolMessageTypes values streamed to their wire byte, so a table keyed by a different chia_protocol version’s enum re-keys to shifted bytes, every Chia opcode misses its entry and falls to default_settings — a silent loosening with no compile error. Build the table with the chia_protocol this crate resolves; re-export it from here (crate::RateLimits) rather than depending on chia-sdk-client independently.

fn from(limits: &RateLimits) -> Self

Converts to this type from the input type.