ASTEROID XRPL methodology and evidence

ledger-verified

Read directly from a validated ledger by the stated XRPL method. The value is what the ledger contained at the stated ledger index.

owner-confirmed

A role the project declares — treasury, dev allocation, LP holder. The underlying objects may be ledger-readable, but the role itself is a declaration and is never presented as ledger proof of control.

derived

Computed from identified ledger inputs using the arithmetic published on this page. Derived values always state the inputs they were computed from.

Exact decimal arithmetic

XRPL issued amounts carry up to 15 significant digits and there is no protocol-level decimals property. Every quantity is carried as an arbitrary-precision scaled integer and transported as an exact decimal string. No value is converted to an IEEE-754 double before transport.

All arithmetic is performed on arbitrary-precision scaled integers. Division truncates toward zero at 30 decimal places. Transported amounts and prices are rounded half-up at 15 decimal places, percentages at 8 decimal places, and the trading-fee percentage at 6 decimal places. No value is ever converted to an IEEE-754 double before transport.

Missing values

An input that could not be read from a validated ledger is transported as null together with a stable degraded code. A missing value is never substituted with zero, with a cached older value presented as current, or with a project-declared figure.

Caching and freshness

Live readings are served through a bounded single-flight server cache: AMM pool 10s, supply 30s, escrows 60s, holder enumeration 120s, account-control reads 120s. A cached reading still carries the validated ledger index and observation timestamp it was produced from, so its age is never hidden.

No execution

No interface on this site signs a transaction, submits a transaction, prepares a transaction for signing, or accepts a key, seed, mnemonic or any other credential. Every price figure is an observation or an estimate and is never executable.

Formulas

exact-in: netIn = in x (1 − fee); out = poolOut x netIn / (poolIn + netIn).

exact-out: netIn = poolIn x out / (poolOut − out); in = netIn / (1 − fee).

fee = tradingFeeUnits / 100000, where tradingFeeUnits is the XRPL AMM trading fee in units of 1/100,000 (1000 units = 1%, the protocol maximum). The fee is set by liquidity-provider votes; it is not a token tax.

spotPrice = poolOut / poolIn. effectivePrice = amountOut / amountIn. priceImpactPct = 100 x (1 − effectivePrice / spotPrice), which includes the pool fee. poolUtilisationPct = 100 x amountOut / poolOut.

Quote lifecycle

Every estimate carries a quoteId, the methodology identifier and version, the validated ledgerIndex it was computed at, observedAt, maxAgeMs (10s) and an expiresAt instant after which it must be discarded and the pool re-read.

The quoteId is a correlation handle only. It reserves no liquidity, cannot be redeemed, cannot be executed and confers no right to any price. Expiry marks the end of the freshness window, not the end of an offer — there was never an offer.

The freshness window belongs to the observation, not to the moment of calculation. When an estimate is computed from a cached pool reading, observedAt stays the instant the pool was read from the validated ledger and expiresAt stays observedAt + maxAgeMs; remainingMs reports maxAgeMs minus the cache age. A cache hit therefore never extends the window. An observation older than maxAgeMs is re-read rather than reused, and an estimate is refused with a STALE_OBSERVATION error rather than served from an expired observation.

Auction-slot fee treatment

Every estimate is anonymous and uses the ordinary XRPL AMM trading fee read from `amm_info`. The XLS-30d auction slot can give one account a discounted fee for a limited period, but auction-slot eligibility is a property of the executing account at execution time, and this service accepts no account context of any kind. No account-specific discounted fee is therefore applied or inferred, and an eligible account would pay less than the estimate shows. This is a further reason every estimate here is indicative and non-executable.

Every estimate discloses this as a structured ORDINARY_POOL_FEE_ASSUMED warning, so an agent never has to infer which fee schedule was applied.

Derivation

XLS-30d Automated Market Maker specification and the rippled reference implementation of swapAssetIn/swapAssetOut in src/xrpld/app/misc/AMMHelpers.cpp. Expected values were derived analytically with exact rational arithmetic, independently of this repository's TypeScript implementation, and then rounded by the published transport policy.

Rounding applied

Fee fraction = tradingFeeUnits / 100000 truncated at 12 dp. Division truncates toward zero at 30 dp. Amounts and prices are rounded half-up at 15 dp. priceImpactPct and poolUtilisationPct are rounded half-up at 8 dp. tradingFeePct is rounded half-up at 6 dp.