Skip to main content

Module fetch

Module fetch 

Source
Expand description

The retrieval flags of decdn get: the client-side paid pull over cdn/client/v1 (issues #391, #940, #2449).

The paying sibling of super::probe::ProbeArgs: a one-shot client pull that dials a node by explicit --node-id/--addr/--relay-url (or auto-discovers one, #936) and pays per-MB from the caller’s own PaymentPool deposit. The pool is auto-opened and reused: the pull looks up the caller’s live pool in its persistent buyer-pool store, resuming its per-(signer, provider) lane watermark for the chosen provider; if none exists it opens (and funds) one on-chain and records it. One pool fans out to every provider the caller pays (ADR 003) — there is no per-provider open.

The on-chain coordinates (RPC, contract addresses, chain id, keystore, data dir) resolve flag > [blockchain]/[identity] config > default, so a configured client runs decdn get decdn:<hash> -o … with no chain flags. Fields are kept as String/Option (mirroring super::probe::ProbeArgs); the cli binary parses addresses and merges the config.

Structs§

ClientFetchArgs
The network, chain, target, and per-blob-limit flags of decdn get, for a blob and a bundle alike. Flattened into super::GetArgs so the resolution (flag > config > default) and node-selection logic have one definition.