Receipt Standing · MultiversX

The standing a wallet built, read from the chain.

One paid read computes the standing a MultiversX wallet has built from the settlements it has made — read live from the public chain record, scored by the published Receipt Standing methodology, and given back as a plain score, a tier, and the full settlement list the score was derived from, so anyone can re-derive it.

SDVOSBUEI G24VZA4RLMK3CAGE 21U51

The paid read

GET https://mvx-standing.pages.dev/standing?wallet=erd1… — $0.01 USD equivalent in MEX, paid over x402 (scheme exact, network multiversx:1, asset MEX-455c57) to erd1wz6yvu3yqe7fsvw6mryuq5zx8k52ql2yk4j3v75e36dyylkm4r8qpzhx2y, settled through the OMNIGATE facilitator.

At the live rate right now (1 MEX = $3.9792065930540177e-7, read 2026-11-17T03:57:52.063Z), one read costs 25,130 MEX — the exact amount is computed again at challenge time and ceiling-rounded to whole MEX.

An address that is not a valid MultiversX wallet is refused without charge. A read of one of the operator's own wallets is answered without charge: the operator's wallets are never scored, and the answer says so plainly (self_excluded).

Paid reads so far: 1 (including 1 self-proof) · outside reads: 0.

What the read covers

Successful direct value transfers the wallet sent, as the MultiversX public API publishes them: plain EGLD transfers, ESDTTransfer, and MultiESDTNFTTransfer carrying fungible legs. The read covers the wallet's 1000 most recent sent transactions; the response states the exact window it read — how many sent transactions exist, how many it read, the oldest and newest in the window, and whether older history exists beyond it. Nothing beyond the window is implied.

Standing accrues to the payer: this is a read of the wallet's own payment history, scored under the Receipt Standing methodology (version receipt-standing-mvx/1.0) — the MultiversX sibling of the facilitator-record read published as receipt-standing/1.0 on Base.

What the read does NOT cover

· Contract calls that are not direct transfers — swaps, staking and farm operations, market orders — are not counted, however much value they moved.
· Payments the wallet received add nothing. Standing is the payer's history, not a balance of what flowed in.
· Any single facilitator's records. This read is the wallet's public settlement footprint on MultiversX. It cannot say which facilitator, if any, handled a given transfer.
· Outcomes. A settlement proves a payment landed on-chain. It does not prove the goods or services were delivered, were satisfactory, or were undisputed — the outcome field of every read says unknown.
· History beyond the window. If the cap was reached, the score is a floor, not a lifetime total.

How the score is computed

Each counted settlement contributes class weight × pair factor × decay factor:

· Classes — a settlement paid to an operator wallet counts at 1.0; paid to any other wallet, 1.0; a settlement whose destination cannot be read counts at 0.25 and is labeled counterparty_unverified. A settlement the wallet paid to itself counts nothing and is reported as self-directed, never mixed into the score.
· Repeat-payee damping — the first settlement with a given payee counts at the full class weight; each later settlement with the same payee counts at half the previous factor (1, 0.5, 0.25, …), so repeated volume between one pair converges instead of compounding.
· Decay — aged 30 days or less, factor 1.0; 31–90 days, 0.6; 91–180 days, 0.3; older, nothing. Standing reflects recent, verified payment history and lapses when activity stops.

TierWeighted standingDiscount eligibility label
none0none
emergingabove 0, below 3standard
established3 to below 10preferred_pricing_eligible
strong10 to below 25preferred_pricing_eligible
anchor25 and abovepreferred_pricing_eligible

Discount honoring is not active: the eligibility labels are a reporting vocabulary, published so services can quote against one stable set of words. No price anywhere changes because of a tier today.

Agents: the machine-readable descriptor is at https://mvx-standing.pages.dev/agent.json. Unpaid, the read route answers with the x402 challenge; sign the exact ESDT payment it describes (relayed — the facilitator covers the network fee) and retry with the PAYMENT-SIGNATURE header. The standing is delivered in the paid response, immediately on settlement.

The fences

Informational only: standing is a computed read of a wallet's public settlement history on MultiversX, published with its data window and as-of timestamp. It is not a credit score, not a measure of trustworthiness, and not financial advice. A tier changes no price anywhere today; discount honoring is not active. This service is read-only — it moves no funds for anyone beyond the reader's own payment for the read.

The operator's own wallets are excluded from standing in both directions: a read of one gives back the self_excluded truth, and no score is ever published for them. If the chain record cannot be read, the read fails closed — nothing is estimated or filled in.