XRPL Token Services

By accessing or using XRPL Token Services — including the web dashboard, API endpoints, vanity address search, token configuration wizard, pool creation, airdrop scheduler, and holder simulator — you agree to be bound by these Terms. If you do not agree, do not use the Services.

• Vanity Address Mining & Reservation: search a pre-mined pool of vanity addresses; request custom prefixes to be mined on-demand.
• Multi-Token Generation: create 1–5 tokens per project with standard (3-char) or hex-encoded (4–20 char) currency codes, configurable transfer fees (0–1%), and per-token issuer selection (shared, random, or vanity).
• AMM Pool Creation: deploy XRP-backed AMM pools and token/token pairs via XLS-30, with configurable trading fees (0.0–1%) and seed liquidity.
• Airdrop Distribution: schedule and execute token airdrops to holder lists (XRP holders, token holders, trustline setters, snapshots) with promoter rewards and capacity packs.
• Project Management: multi-project dashboard, state persistence, payment tracking (Xaman), and launch execution.

4.1 Pool Search & Selection. The platform maintains a pre-computed pool of vanity addresses. Customers may search this pool by prefix via the dashboard. Search results are informational; no reservation occurs until you pick an address or save a token configuration with a vanity issuer mode selected.

4.2 Reservation & Expiry.

• Standalone vanity picker: you may add up to 20 addresses to a vanity order; each pick is held for you for 12 hours.
• Per-token issuer (issuer_mode = "vanity"): saving a token with a vanity issuer reserves the selected address for your project for 24 hours, up to 5 concurrent reservations per customer.
• Reservations are tied to your customer account and project ID. If payment is not completed before the hold expires, the address returns to the available pool.

4.3 Custom Prefix Requests (Paid Mining). If your desired prefix is not in the pool, you may submit a Vanity Generation Request for a fixed fee (see Pricing); this adds the prefix to the mining list only. Mining time is unpredictable — longer prefixes (6+ chars) can take days, weeks, or longer. No completion timeline is guaranteed and a prefix may never be mined. When a match is found, the address is held for you for 24 hours and you are notified via XRPL memo to your paying address and/or email (if provided). If you do not claim it within 24 hours of notification, it returns to the pool.

4.4 Key Handover. Upon project launch, the private key for each vanity issuer is delivered to you via a one-time handover. You must acknowledge receipt. The platform retains no copy of the private key after handover. Loss of the key after handover is irreversible — the platform cannot recover it, and any funds or tokens in the address will be lost with it.

4.5 Ownership & Risk. Vanity addresses are standard XRPL accounts. Whoever holds the private key controls the account. The platform makes no warranty that a vanity prefix confers any branding, trademark, or legal right. You are responsible for securing keys post-handover.

5.1 Configuration. You configure each token via the Token page: name, currency code (auto-derived), transfer fee (0–1%), issuing amount, issuer mode. The platform validates currency code format per XRPL specs (standard 3-char or hex-encoded 20-char). "XRP" is reserved and rejected.

5.2 Issuer Modes.

• Shared: token uses the first token's issuer (token 1 only).
• Random: platform generates a fresh random key; key handed over at launch.
• Vanity: you select a vanity address from the pool or request a custom prefix; key handed over at launch.

5.3 Issuance & Launch. Tokens are not issued until the launch execution phase. At launch, the platform funds each issuer account with the reserve requirement plus issuing amount, submits Payment transactions to issue the configured supply, configures transfer fees and domain/link metadata (if provided), and delivers issuer private keys via secure one-time handover. You must verify all token parameters before confirming launch. Post-launch changes to currency code, issuer, or total supply are not supported on-chain.

5.4 Token Standards Compliance. Tokens issued are standard XRPL IssuedCurrency assets. The platform does not register tokens with any third-party registry (e.g., XRPL Token Registry, CoinGecko, DEX Screener). Listing and metadata submission are your responsibility.

6.1 Pool Configuration. Per token, you may enable an XRP-backed AMM pool (XLS-30) and up to 5 token/token pairs. For each pool you specify the XRP seed amount (minimum 100 XRP), trading fee (0.1–1%), and for token/token pairs the target (issuer:currency), allocation %, fee %, and counterpart amount.

6.2 Deployment & Risk. Pools are created atomically during launch using your funded issuer accounts.

• Impermanent loss: AMM liquidity providers are exposed to impermanent loss. The platform does not hedge or guarantee returns.
• Price impact: large trades relative to pool depth incur significant slippage.
• Trading fees accrue to the pool (pro-rata to LP tokens). The platform takes no protocol fee.
• If an external token target has no XRP pool, the platform attempts a bridge quote (SOLO, CORE, etc.); accuracy is not guaranteed.

6.3 LP Tokens & Control. Upon pool creation, LP tokens are issued to the issuer account (or designated recipient). You control the LP tokens post-handover. The platform cannot withdraw, rebalance, or manage pools after launch.

7.1 What it is. The Pools dashboard and the Swap/Liquidity panel display a trust score for AMM pools, shown as a coloured pill from red (low) to green (high), with a short word (trusted, reasonable, caution, high risk). It is a rough, automated heuristic computed from publicly visible XRP Ledger activity that our own monitor has observed. It is provided for information only.

7.2 Not advice, not an endorsement, not an audit. The score is not financial, investment, trading or legal advice, and must not be relied on to make any decision to buy, sell, hold or provide liquidity. Specifically:

• A high score is not an endorsement of a pool, token, issuer or project, and is not a prediction of price, return or safety.
• A low score is not an accusation of wrongdoing. It means the observed on-ledger pattern scored poorly against the measures below — nothing more.
• It is not a security or fraud audit. It does not examine token contracts, issuer privileges (such as freeze or clawback), account settings, team identity, off-ledger arrangements, or intent, and it does not detect rug pulls.
• It scores an individual liquidity pool, not the token, its issuer, or any project.
• Pools shown are largely operated by unrelated third parties. Their appearance on our dashboard implies no affiliation, endorsement or vetting.

7.3 How it is calculated. Each measure below awards points on a sliding scale up to its maximum; the points are added and the total is expressed as a percentage of the maximum that could actually be measured for that pool. With every measure counted the maximum is 75 points; where a measure cannot be counted it is removed from the maximum as well as from the total (see 7.5), so scores are not comparable to a fixed denominator.

• Depth (pool value) — up to 30 points (logarithmic). Scores nothing at or below 1,000 XRP and full marks at or above 1,000,000 XRP of total value held.
• Swap intensity — up to 25 points (banded — falls off at both ends). Swaps per 1,000 XRP of depth over 24h. Full marks between 3 and 200; nothing at or below 0.5 (too little trade to be usable) and nothing at or above 10,000 (far more trades than the depth can plausibly support).
• Distinct traders — up to 20 points (logarithmic). Separate wallets trading the pair in 24h. Nothing at or below 3, full marks at or above 400.

Swap intensity is deliberately banded rather than "more is better": a very high number of trades relative to a pool's depth is treated as a negative signal, not a positive one, because it is characteristic of automated wash-trading rather than genuine demand. Ranking pools by raw trade count alone would place such pools at the top.

7.4 What the score does not yet include. The following measures are designed but not currently counted, and their absence is disclosed in the score's tooltip:

• Average trade size (intended weight 15 points) — Held back until pair-wide candle volume is verified — reconstructing it gave figures larger than the total XRP supply.
• Trustlines on the weaker leg (intended weight 10 points) — Needs a paged AccountLines scan per issuer (weekly-cached). Evidence the ASSET is real; weak evidence the pool is honest.

7.5 Missing data is not a low score. Where a measure cannot be computed for a pool, it is excluded from both the points awarded and the maximum, so the pool is scored only on what could be measured — it is never penalised for the gap. Where we cannot measure a pool at all, the pill reads “no data” in neutral grey instead of a number. That covers, among others, a pool holding less than 10 XRP, a pool with no trades in the last 24 hours, and a token/token pool whose assets we cannot currently price in XRP.

7.6 Newly seen pools are capped. A pool our monitor has watched for less than 3 days — or for an unknown period — cannot score above 60%, and is marked ·new. Observation age reflects how long we have been watching, up to 30 days, and is not the pool's actual age on the ledger.

7.7 Limitations you should assume.

• We see only pools our monitor has observed trading, and retain at most 30 days of history. Coverage restarts if that record is lost.
• Figures are derived from ledger metadata and may be incomplete, delayed or wrong. The “swap value” figure counts AMM trades only and excludes order-book crosses, so it understates total activity on a pair.
• Where the Pools board is set to a period in which a pool recorded no activity, its swap count and swap value are estimated by taking the figure from a wider period and expressing it as a rate over the selected one. Such figures are marked with “≈” and name their source period. They are an extrapolation, not a measurement, and are used for ordering the board; the trust score itself never uses them.
• Pool values for token/token pools are derived indirectly via a bridge price and are less reliable than for XRP-paired pools; the tooltip says so where this applies.
• All thresholds, weights and bands above are configurable and may change at any time without notice, so a pool's score may move without its behaviour changing. The figures on this page are rendered from the configuration in force right now.
• The score can be gamed. It measures observable patterns, and a sufficiently motivated operator can construct activity that scores well.

7.8 No warranty and no liability. The score is provided “as is”, without any warranty of accuracy, completeness or fitness for any purpose. To the fullest extent permitted by law, we accept no liability for any loss arising from reliance on it. You are solely responsible for your own research and decisions. Nothing in this section limits any right you have under the Australian Consumer Law that cannot lawfully be excluded.

8.1 Allocation Model. Per token, you allocate percentages across four buckets (must sum ≤ 100%): Team, Airdrop, Long-Term Holder Rewards, and Pools (remainder).

8.2 Recipient Lists & Capacity.

• Recipient lists are sourced from XRPL snapshots (XRP holders, token holders, trustline setters) at a configured ledger index.
• Capacity is sold in packs of 25,000 recipients per pack (one pack included; additional packs purchasable). Exceeding capacity requires purchasing additional packs before launch.
• Promoter/referral rewards (optional) are paid from the airdrop allocation as a % of each recipient's share.

8.3 Execution & Scheduling. Airdrops execute as scheduled transactions over a configurable timeline (start date, events, intervals). Each event submits Payment transactions from the issuer account. The platform retries failed payments per the configured retry policy; final undelivered amounts remain in the issuer account.

8.4 Legal Compliance. You are solely responsible for ensuring your airdrop complies with applicable securities, tax, AML/KYC, and consumer-protection laws in all relevant jurisdictions. The platform provides technical execution only and does not advise on regulatory classification.

9.1 Pricing (indicative — see the Checkout page for live totals):

Exact live pricing is rendered from the platform's pricing catalog at checkout.

9.2 Payment. All payments are made in XRP via Xaman (QR code / push notification) to the platform's receiving address with a destination tag. Manual payments by any other means may not work correctly. The payment watcher confirms on-chain receipt (validated ledger) before marking items paid.

9.3 Refunds.

• No refunds for on-chain costs already incurred (reserves, txn fees, issued tokens, pool creation).
• Pre-launch: if you cancel before launch execution, unspent XRP (minus non-refundable vanity mining fees) may be returned on a case-by-case basis — contact [email protected].
• Custom vanity mining fees are non-refundable once the mining request is submitted, regardless of outcome or timeline.

• Verify before payment: review every item summary in the system before approving. The platform prepares transactions; you authorize them.
• Secure your keys: after key handover you are the sole custodian. The platform cannot recover lost keys. They are displayed one time only.
• Compliance: token design, airdrop structure, and promoter programs must comply with all applicable laws in your jurisdiction. The platform does not provide legal advice.

11.1 No Financial Advice. The platform provides technical infrastructure only. Nothing in the dashboard, documentation, or communications constitutes financial, investment, tax, or legal advice. Token creation, airdrops, and liquidity provision carry significant financial risk.

11.2 "As Is" / "As Available". Services are provided without warranties of any kind: no warranty of merchantability, fitness for a particular purpose, non-infringement, uptime, or error-free operation. XRPL network conditions (congestion, fee spikes, amendments) may affect execution.

11.3 Limitation of Liability. To the maximum extent permitted by law, XRPL Token Services and its operators shall not be liable for:

• Lost funds due to misconfigured tokens, pools, or airdrops;
• Rejected trustlines, failed payments, or transaction rejections;
• Impermanent loss, slippage, or adverse price movement in AMM pools;
• Vanity mining delays or failures to find a prefix;
• Third-party service outages (Xaman, XRPL nodes, hosting);
• Indirect, incidental, consequential, or punitive damages.

Total aggregate liability shall not exceed the total fees paid by you for the project in question.

11.4 Indemnification. You agree to indemnify and hold harmless the platform, its operators, and affiliates from any claims, damages, losses, or expenses (including legal fees) arising from your use of the Services, your tokens, your airdrops, or your violation of these Terms or applicable law.

• Platform IP: all software, algorithms, vanity pool, UI, and backend code remain the exclusive property of XRPL Token Services.
• Your content: you retain ownership of token names, logos, project configurations, and recipient data you provide.
• License: you grant us a limited, non-exclusive license to use your content solely to operate the Services (e.g., displaying token names in the dashboard, submitting transactions).
• No trademark rights: a vanity prefix (e.g., rMyBrand) confers no trademark or branding rights on the XRPL or elsewhere.

• Data collected: email (for login/notifications), Xaman payload responses, project configurations, wallet addresses, transaction hashes, and simulator state.
• No private keys stored: issuer private keys are generated and handed over once. After handover there is no second chance to recover keys. We are not responsible for any loss of power, loss of connection, or any other event that may interfere with key display.
• Retention: project data is retained while the project exists. Deleted projects purge associated data within 30 days.
• Third parties: Xaman receives payment payload data; XRPL nodes receive submitted transactions. We do not sell data.

We may suspend or terminate your access for breach of these Terms, illegal activity, abuse of the vanity pool, simulator misuse, or non-payment. You may delete your projects at any time via the dashboard. Deleted projects cannot be recovered.

These Terms are governed by the laws of Queensland, Australia, without regard to conflict-of-law principles. Disputes shall be resolved in the courts of Queensland.

• Entire agreement: these Terms, plus the Checkout page pricing, constitute the entire agreement.
• Amendments: we may update these Terms by posting a new version with an updated effective date. Continued use constitutes acceptance.
• Severability: if any provision is unenforceable, the remainder stands.
• No waiver: failure to enforce a right does not waive it.
• Assignment: you may not assign these Terms. We may assign them with notice.
• Force majeure: not liable for delays due to events beyond reasonable control (network forks, war, natural disaster, etc.).
• Contact: [email protected].