XRPL amendments · current ledger evidence

Keep public-book, permissioned-book and AMM liquidity separate. Issuer escrow, freeze, clawback and authorization powers affect eligibility independently of market depth.

Read-only and on demand. No wallet connection is required for public network status.

Not checked in this session. No activation status is assumed.

Official XRPL amendment reference · How the ecosystem uses these features

XRBitcoinCash logo

XRPL Mainnet · Read-only risk intelligence

XRBC Research Tools
v3.0.0 · 150 XRBC reusable access gate

XRPL Token Risk Lens

Check how difficult a token may be to sell, how a larger sale could move its price, and which issuer controls can restrict transfers. Read the method without a wallet; token analysis requires Xaman and at least 150 XRBC held in your wallet. Reports read public XRP Ledger evidence. Optional access setup and exit transactions require separate Xaman approval.

Exit stressAMM depth and 25% / 50% / 100% wallet-position impact
Market qualitySpread, multi-band depth, imbalance, makers, and concentration
Issuer authorityKeys, freeze, clawback, fees, and blackhole pattern
Holder controlsTrustline freeze, authorization, No Ripple, and quality settings
AMM activity sampleAffected-address occurrence shares, HHI, and experimental burst timing
Evidence reproducibilityCoverage, unknown states, ledger freshness, digest, and export
Risk Lens is a deterministic research aid—not a credit rating or investment recommendation. Scores describe the current public XRPL snapshot and can change with each validated ledger.

Public methodology · No wallet required

Market-risk methods translated to XRPL evidence

Risk Lens does not copy or imply endorsement by proprietary rating providers. It translates mature market-quality concepts into independently calculated XRPL observations and labels every result as detected, not detected, unknown, unsupported, or stale.

Method open · Advanced scans gated

Public method

Review weights, formulas, limitations, supported evidence, and exact XRBC identifiers. No wallet or ledger scan starts here.

Client-verified access

Connect Xaman deliberately. Below 150 XRBC, the page shows only detected XRBC balance and shortfall—never wallet-token enumeration.

Gated analysis

At 150 XRBC, analyze at most 25 positive trustline tokens, run stress diagnostics, and create local evidence exports. XRBC stays in the wallet.

Order-book quality

CoinGecko-style spread and ±2% depth concepts, extended locally to 1%, 2%, 5%, and 10% XRPL depth with side-by-side coverage.CoinGecko methodology

Execution stress

CoinMarketCap-style order-size/slippage thinking, recalculated from current XRPL AMM reserves and the selected wallet position—not copied provider scores.CoinMarketCap liquidity method

Concentration

HHI = sum of squared observed shares. Risk Lens reports funded-offer maker shares and affected-address occurrence shares plus effective address counts; neither proves common ownership, trading value, or distinct people.DOJ HHI definition

Administrative controls

EVM bytecode scanners do not apply to XRPL issued assets. Risk Lens instead inspects AccountRoot, signer, delegate, trustline, freeze, clawback, authorization, and fee controls.XRPL AccountRoot docs
Mid-price spread(ask − bid) ÷ mid

Calculated only when both funded XRPL order-book sides are available.

Depth bandsΣ funded XRP

Reported independently within 1%, 2%, 5%, and 10% of each side's best price.

ConcentrationHHI = Σ share²

The engine stores HHI on 0–1, displays HHI points as HHI × 10,000, and reports 1 ÷ HHI as an effective address count. DOJ merger thresholds are not applied.

Coverage-aware scoreΣ risk × weight ÷ available weight

No score is published when validated-ledger evidence coverage is too weak.

Evidence states Detected Not detected Unknown Unsupported Stale

Unknown, unsupported, and stale evidence never becomes a green pass. Capability does not prove misuse.

Gate enforcement disclosure: the 150 XRBC check currently controls this browser interface. A true anti-spam or privileged backend boundary also requires the Render proxy to verify a short-lived signed wallet challenge server-side before accepting advanced methods. CORS alone is not authorization.

Wallet readiness and access

Reusable 150 XRBC Access Gate

The gate checks the connected wallet balance. XRBC is not paid to this website, transferred to an operator, consumed, or locked by the page.

Ready for wallet
Get Xaman
1 · XamanNot connected
2 · Validated account_linesWaiting
3 · 150 XRBC gateNot checked
Current wallet balance 0.000000 XRBC
Minimum balance 150 XRBC
Additional XRBC needed 150.000000 XRBC
Access state Not checked

Connect Xaman to check access.

This is gatekeeping, not a fee.

Holding 150 XRBC satisfies this browser’s current access condition while the tokens remain under the user's control. The separate full opt-out control can prepare a sale of the available XRBC balance, subject to route availability, Xaman approval, and a validated ledger result. Access automatically relocks whenever the wallet holds less than 150 XRBC.

Full opt-out controls

Prepare a sale of up to the connected-wallet XRBC balance through an XRPL path payment. This page never receives the tokens. The XRBC trustline can remain with a zero balance, but no continued token ownership is required.

Connected wallet and public account lookup

Select a Wallet Token to Analyze

After the 150 XRBC gate unlocks, select the wallet-token scan deliberately. You may also inspect positive token balances held by any other public XRPL wallet address without connecting that wallet.

0 tokens
Token source Connected Xaman wallet
Connected wallet
Positive token balances—
XRBC held by source—
Gate wallet—

This lookup reads public trustlines only. The connected Xaman wallet remains the wallet that satisfies this client-verified browser access condition.

Advanced AMM affected-address sample settings
No token selected.
Connect Xaman and unlock the 150 XRBC gate, then select “Load up to 25 wallet tokens” to begin.

Transparent XRPL risk observations

Risk Lens Report

A higher number means more observed risk under the published criteria. Evidence coverage and the possible-risk range are reported separately from the observed-risk point estimate.

0–100 observed risk
No Risk Lens analysis has been run.
Local evidence tools

Created only after an explicit gated scan. Files remain on this device unless you share them; an export contains full public gate/source addresses and exact balance evidence. The digest detects changes only when checked against a separately trusted digest—it is not a signature or proof of origin.

No evidence digest yet.

Technical activity log 

      

    

  


  

    

      

        
Published scoring model

        
How the Observed-Risk Score Is Calculated

        


          Every measured category is normalized to 0–100 and multiplied by its disclosed weight.
          Unknown evidence is excluded from the known-only point estimate, expands the possible-risk
          range, and reduces evidence coverage. Classification is withheld below 70% coverage.
        

      

      Higher score = higher observed risk
    


    

      
30% Liquidity and exit capacityAMM existence, XRP reserves, fee, 100-XRP impact, and estimated impact of exiting the selected wallet position.

      
20% Order-book fragilityOffer count, maker diversity, bid/ask spread, depth within 2% and 5%, and maker concentration.

      
15% AMM affected-address activityBounded historical account_tx rows, affected-address occurrence shares, address-level HHI, and an experimental burst-timing heuristic. These are not trade-value or ownership shares.

      
25% Issuer and policy controlsSigning authority, verified blackhole pattern, freeze powers, clawback, authorization, domain, transfer fee, and TickSize.

      
10% Holder trustline and exposureFreeze state, authorization, No Ripple, quality settings, and position size relative to public AMM token reserves.

    


    

      
0–24Lower observed risk

      
25–49Moderate observed risk

      
50–74Elevated observed risk

      
75–100High observed risk

    


    

      
The score is not universal or predictive.

      

        It does not establish legality, solvency, identity, future price, code quality,
        off-ledger reserves, or whether an issuer will act responsibly. It measures only
        the public XRPL signals that this page can retrieve at analysis time.
      

      
Worked example — hypothetical, not a token report. Suppose a scan reports 65% evidence coverage and unavailable order-book and participation checks. The score and classification are withheld because coverage is below the published 70% threshold, even if the available liquidity readings look favorable. “Unavailable” means that check could not establish a result; it does not mean zero risk or no offers. Review the missing evidence and ledger freshness before comparing reports. A later score can change simply because more evidence became available.

    

  


  

    

      
Risk disclaimer and limitations

      
Read This Before Relying on a Score

    

    

      
Not financial advice. Risk Lens is a technical research interface, not a recommendation to buy, sell, hold, trust, or avoid any asset.

      
Snapshot and bounded history only. AMM reserves, offers, account controls, and trustlines can change immediately after the pinned ledger; affected-address activity is a bounded historical sample ending at that ledger.

      
Risk is not legitimacy. A lower score does not prove an issuer, token, website, or community is legitimate. A higher score does not prove misconduct.

      
Market estimates are limited. AMM exit calculations are model estimates and do not guarantee a route, execution price, minimum output, or complete sale.

      
Issuer powers matter. Freeze, authorization, clawback, transfer-fee, and signing-authority observations are reported from public ledger state and should be independently verified.

      
Coverage is separate. Sparse data expands the possible-risk range and can withhold classification. Coverage is not a probability that the score is correct.

      
Activity scope is narrow. The AMM activity category counts address occurrences found in affected-node metadata from a bounded historical account_tx sample ending at the pinned ledger. It is not time-normalized, does not measure trading value or beneficial ownership, and its burst heuristic does not establish bots, coordination, manipulation, or misconduct.

      
Concentration scope is narrow. Maker HHI covers the bounded visible funded-offer slice and affected-address HHI covers occurrence shares. Both are address-level, displayed as normalized HHI × 10,000; DOJ merger thresholds are not applied.

      
Identity fields are assertions. An AccountRoot Domain field does not verify ownership, issuer identity, or xrp-ledger.toml linkage. Multiple signer addresses do not prove independent people or organizations.

      
Public identifiers travel with exports. An unlocked user may inspect any entered public XRPL address. Exported evidence includes full public gate/source addresses and exact balance evidence; sharing the file shares those identifiers.

      
Gate actions are optional. Holding XRBC is not a payment to the site. Buy, sell, trustline, and opt-out requests require review and approval inside Xaman.

      
Finality matters. A gate transaction is complete only after it appears in a validated XRPL ledger.