Struct PaymentVerifier 

pub struct PaymentVerifier { /* private fields */ }

Main payment verifier for ant-node.

Uses:

1. LRU cache for fast lookups of previously verified XorName values
2. EVM payment verification for new data (always required)
3. Pool-level cache for merkle batch payments (avoids repeated on-chain queries)

Implementations

impl PaymentVerifier

pub fn new(config: PaymentVerifierConfig) -> Self

Create a new payment verifier.

pub fn attach_p2p_node(&self, node: Arc<P2PNode>)

Attach the node’s P2PNode handle so merkle-payment verification can check candidate pub_keys against the DHT’s actual closest peers to the pool midpoint.

Production startup MUST call this once the P2PNode exists. Without it, the closeness check fails CLOSED in release builds (rejects the PUT with a visible error) and fails open in test builds. Idempotent: calling twice replaces the handle.

pub fn attach_storage(&self, storage: Arc<LmdbStorage>)

Attach the node’s LmdbStorage handle so storage-delta freshness checks can query the authoritative on-disk record count.

Production startup MUST call this once the storage exists; otherwise validate_quote_freshness falls back to treating the current count as zero, which will reject all non-trivial quotes. Idempotent: calling twice replaces the handle.

pub fn check_payment_required( &self, xorname: &XorName, context: VerificationContext, ) -> PaymentStatus

Check if payment is required for the given XorName.

This is the main entry point for payment verification:

1. Check LRU cache (fast path)
2. If not cached, payment is required

The fast path is context-aware: a ClientPut lookup is satisfied only by an entry whose verification ran the full client-PUT check set. An entry inserted by a Replication verification (which skips the storer-being-paid-now checks) must not let a later client PUT bypass those checks. A Replication lookup accepts either kind of entry.

Arguments

• xorname - The content-addressed name of the data
• context - The verification context of the caller

Returns

• PaymentStatus::CachedAsVerified - Found in local cache (previously paid)
• PaymentStatus::PaymentRequired - Not cached (payment required)

pub async fn verify_payment( &self, xorname: &XorName, payment_proof: Option<&[u8]>, context: VerificationContext, ) -> Result<PaymentStatus>

Verify that a PUT request has valid payment.

This is the complete payment verification flow:

1. Check if data is in cache (previously paid)
2. If not, verify the provided payment proof

Arguments

• xorname - The content-addressed name of the data
• payment_proof - Optional payment proof (required if not in cache)
• context - Whether the proof backs a live client PUT or an already-settled receipt presented during replication — see VerificationContext for which checks each context runs

Returns

• Ok(PaymentStatus) - Verification succeeded
• Err(Error::Payment) - No payment and not cached, or payment invalid

Errors

Returns an error if payment is required but not provided, or if payment is invalid.

pub fn cache_stats(&self) -> CacheStats

Get cache statistics.

pub fn cache_len(&self) -> usize

Get the number of cached entries.