@xyo-network/price-client
v0.1.1
Published
Bounded neutral finalized price history and historical fleet authority
Keywords
Readme
Price history client
The neutral client composes the selected installed XL1 native finalized and
controlled REST readers, historical Service Kit B4 authority and explicit public
archive seeds. createPriceHistoryClient(profile) creates a read-only client;
query(query, options) returns price-history-result-v1, and close() aborts
and drains its queries and native reader.
parsePriceHistoryProfile(input) validates object or JSON-text configuration
without constructing providers or making requests. It returns a detached profile
using the same boundary as client construction. Parsing configuration establishes
no authority, inclusion, availability or price facts.
Every query names a trusted owner, one fleet or all fleets, source, opaque market,
fixed candle width, half-open source-start seconds window and exact native
anchor. Authority is evaluated at each carrying block, and equal body roots at
distinct native positions remain separate. Original Price roots and native
storage envelopes are checked before strict interpretation. Only the admitted
native storage _sequence is removed; its value supplies no ordering or time.
Continuation is an untrusted output hint. Every page replays the fixed native
anchor and required authority; coverage states how many matching rows preceded
the hint. Only complete, exhausted coverage establishes complete enumeration.
Missing, unsupported and bounded-out evidence remains explicit. facts-complete
reports correlated native/content/authority facts and supplies no economic or
consumer settlement verdict.
The closed profile contains URLs, finite owning/client limits and the qualified
frozen Price/Gate registry binding. It accepts no credentials, transport/proof
callbacks or imported rosters. Decoded work is conservatively reserved across
repeated owning calls; reservedDecodedBytes is a cap reservation, not measured
throughput. Source collection, aggregation and game policy belong elsewhere.
The implementation follows the selected profile. Actual small-profile, installed-consumer and business-case qualification remain distinct from source existence and deployment.
