Terms built for the system that exists now.

1 · Agreement and electronic acceptance

Agreement to these Terms

These Terms form an agreement between you and the person or entity operating xrbitcoincash.com and official XRBitcoinCash interfaces that expressly incorporate these Terms (the “XRBC Operator”).

By accessing an official interface, connecting a wallet, opening a Xaman request, using an analytical tool, exporting evidence, creating an invoice, establishing a trust line, generating a tokenization record, or otherwise using an XRBC Tool, you acknowledge that you have read and understood these Terms, the White Paper, and the Policy & Security page. If you do not agree, do not use the affected interface.

Third-party wallets, markets, data providers, related projects, hosting platforms, and other independent services may impose separate terms. Those terms apply independently.

2 · Defined terms

Definitions

XRBC

XRBitcoinCash, an issued currency on XRP Ledger Mainnet identified by the issuer and currency value stated in these Terms.

XRBC Tools

The XRBitcoinCash website interfaces for public-ledger observation, trading support, wallet-specific analysis, order management, liquidity diagnostics, forensic analysis, risk scoring, route comparison, bridge caution intelligence, local evidence generation, tokenization planning, institutional-readiness monitoring, settlement verification, support, and related user-protection functions.

XRBC Parties

XRBitcoinCash, the XRBC Operator, creator, administrators, developers, contributors, contractors, licensors, service providers, and affiliates.

Evidence Pack

A browser-generated record of selected inputs, hashes, calculations, classifications, warnings, or workflow state. It is an integrity and chronology aid, not a certification that the underlying facts are true or legally sufficient.

Local Asset Vault

The browser-local byte-bearing storage workflow used by the tokenization tools when available. It is not cloud custody, escrow, archival storage, or guaranteed backup.

Third-Party Services

XRPL servers and validators, Xaman, market interfaces, explorers, public token directories, data sources, hosting providers, browsers, operating systems, networks, financial-messaging resources, and all independently operated products or services.

User

Any person or organization accessing or using an official interface, XRBC, an XRBC Tool, or a referenced Third-Party Service.

3 · Current ecosystem scope

What these Terms now cover

The ecosystem has expanded beyond a single trading page. These Terms apply to the following XRBitcoinCash-controlled categories when published under the official site or expressly incorporated into a related interface:

Related JCS and Creature NFT pages may have separate operators, purposes, assets, terms, privacy practices, or disclosures. A header link does not by itself make an independent project part of XRBC or subject to these Terms.

4 · Token identity and classification limits

XRBC identity and design posture

• XRBC is an XRPL-issued digital token used within an experimental ecosystem of non-custodial interfaces, public-ledger analysis and evidence-oriented tools.
• XRBC is not a bank deposit, insured account, legal tender, debt obligation, equity interest, revenue share, dividend right, governance right, or claim on an XRBC Party.
• XRBC is not represented as redeemable by the XRBC Operator for a fixed monetary amount, and no reserve-backed dollar promise, price floor, par value, guaranteed market or stable-value guarantee is made.
• No interest, yield, passive return, profit, dividend or appreciation is promised merely for holding XRBC.
• Nothing in these Terms is a binding legal classification of XRBC as a security, non-security, commodity, digital commodity, payment stablecoin, collectible, currency or other regulated category.

5 · Reusable ecosystem access

XRBC access-gate terms

Certain advanced tools use disclosed XRBC wallet-balance thresholds to reduce automated abuse and reserve deeper workflows for participating holders. The current interface thresholds are:

• A gate is a reusable wallet-balance condition, not a payment, subscription, burn, escrow, deposit, transfer to the site, or custody arrangement. XRBC remains in the user's wallet unless a separate transaction is independently authorized.
• Access may relock if the observed balance falls below the threshold, the wallet changes, ledger state changes, or the feature is modified or suspended.
• Meeting a threshold does not guarantee permanent availability, support, economic value, legal status, execution, or future compatibility.
• Before a threshold is met, an interface may intentionally minimize wallet enumeration and show only information needed to evaluate access.
• Browser controls are not a server security boundary. Any protected backend or privileged service must independently reverify authorization and current ledger state. A person bypassing client-side display logic does not acquire permission to use a protected service.

6 · No custody or intermediary relationship

Non-custodial boundary

• The XRBC Operator does not take possession of a user's seed phrase, private key or recovery phrase and does not maintain an internal custodial balance for users.
• Trading, trust-line, order, payment, or minting interfaces may prepare transaction data, but ledger changes require authorization by the relevant XRPL account through a compatible wallet or another valid ledger authorization method.
• The Settlement Desk may help a payer construct and verify a payment between public XRPL accounts, but the site does not intermediate, hold, escrow, reverse, charge back or guarantee the transferred asset.
• No bank, trust, escrow, fiduciary, broker, dealer, exchange operator, money manager, investment adviser, clearing agency, transfer agent, payment processor, remittance provider, money transmitter or client relationship is created solely by accessing the site.
• Legal characterization depends on actual conduct. These Terms do not exempt any person from licensing, registration, reporting, sanctions, tax, consumer-protection or other obligations.

7 · Wallet authorization and transaction intent

Xaman, QR, deep-link and single-request terms

Where an XRBC-controlled page initiates a ledger-changing action through Xaman, the wallet is the independent authorization surface. The interface is designed to show the intended action before signing, but you must review the wallet's final transaction fields yourself.

• Transaction-producing controls may use a six-digit verification code in transaction memos or on-screen instructions. Do not approve a request when the code, account, issuer, currency, amount, flags, destination, Destination Tag, offer sequence, paths or other fields do not match your intent.
• Modern XRBC/XRBitcoin flows may allow only one active Xaman payload at a time and persist the payload UUID, returned Xaman link and local intent state so duplicate actions are not silently created.
• While a request is pending, controls may be locked and may return you to the existing request instead of creating a second payload.
• Closing a browser panel, leaving the page, losing focus, clearing local data, or pressing a local reset control does not necessarily cancel a request already created in Xaman. Cancellation is authoritative only when Xaman or the validated-ledger result confirms it.
• On mobile, an interface may prefer the exact returned Xaman deep/universal link rather than briefly presenting a QR code. On desktop, a QR may be shown when returned by Xaman.
• A Xaman status of “signed” is not treated as settlement success by itself. Where implemented, the interface waits for a transaction hash and validated XRPL result before reporting success.
• Xaman is independent. Its terms, privacy rules, service availability, warnings, transaction policies and fees are outside the XRBC Operator's control.

8 · XRP Ledger protocol terms

Public records, validated state and finality

• The XRP Ledger is an open decentralized network. The XRBC Operator does not own, operate or guarantee consensus, validators, amendments, reserves, fees, public servers or transaction results.
• Balances, trust lines, offers, AMMs, NFTs, account settings and validated transactions are public ledger data.
• Interfaces may intentionally query validated ledger state and cross-check transaction results, but data can still be unavailable, stale, malformed, delayed or affected by third-party infrastructure.
• A transaction can be irreversible after validation. Partial payments, path changes, market movement, failures, expiration or different execution outcomes may occur within the fields authorized by the user.
• Network reserves, fees, transaction formats, amendments and pathfinding behavior can change independently of the website.
• XRBitcoinCash is independent of Ripple, XRPL validators, node operators, XRP holders and other ecosystem participants. No sponsorship or certification is implied.

9 · Trading, orders and payments

Market, Order Manager, XRBitcoin and Settlement limitations

• Quotes, best bid/ask values, AMM ratios, route estimates, slippage, pathfinding, depth and spread are snapshots. They may change before a wallet request is created, while it is open, or before validation.
• Market-swap protections such as SendMax, DeliverMin or interface slippage limits reduce a defined execution risk but do not guarantee execution, price, route, liquidity or absence of loss.
• Open-order tools may display and cancel observable offers. Cancellation does not retroactively reverse fills that already occurred and is not complete until the cancellation transaction validates.
• The Settlement Desk may generate an invoice fingerprint, optional Destination Tag, six-digit request binding and validated receipt comparison. The user must verify the destination account, tag, asset, amount and invoice identity before signing.
• A validated settlement receipt is evidence of the observed ledger transaction. It is not an escrow release, chargeback right, banking receipt, accounting opinion, invoice-collection guarantee, proof of delivery, proof of contractual performance or tax determination.
• The XRBitcoin interface concerns XRB, not XRBC. Its Trade Compass, Route Truth Lens, protected-outcome display, exposure warnings and Quote Passport are decision-support or local evidence features; they do not guarantee price, execution or suitability.

10 · Analytical tools, scores and evidence

Read-only analysis, local calculations and evidence exports

• Liquidity Sentinel, Sentinel Forensics, Extended Audit, Risk Lens, Value Path, Watchtower and related modules are informational and experimental. They do not perform a legal, financial, cybersecurity, accounting, valuation, compliance, title, reserve or smart-contract audit.
• Scores, labels, risk bands, route rankings, warnings, confidence levels, HHI/Gini measurements, concentration, exit estimates and other calculations depend on selected data and assumptions and can be wrong.
• “Low risk,” “healthy,” “ready,” “good,” a low caution score, or a high evidence score never means safe, guaranteed, legally compliant, solvent or appropriate for a particular user.
• Unknown, unavailable, stale or disputed evidence should not be interpreted as favorable simply because a score is low.
• Exported JSON, hashes and Evidence Packs preserve selected inputs/calculations and can support reproducibility. A cryptographic hash demonstrates equality of bytes against the hashed input; it does not prove truth, authorization, legality, ownership or completeness.
• Automated or AI-assisted interpretation can be incomplete, inaccurate or outdated. Important conclusions must be independently verified.

11 · Bridge caution and readiness intelligence

Special boundaries for Bridge Integrity and Readiness

Bridge Integrity

• The Bridge Integrity interface is intentionally read-only. It does not quote, route, approve, deposit, bridge, sign or submit a cross-chain transaction and does not provide a bridge deposit address workflow.
• Bridge caution scores summarize selected warning factors; they are not probabilities of failure, warranties, endorsements or recommendations.
• Incident feeds, operator statements, on-chain records, code references and government/security sources can be incomplete or stale. Missing evidence may increase caution or reduce confidence.
• A route with a low score or no recent incident remains capable of failing.

Readiness Evaluator

• Readiness separates live XRPL/network and market telemetry from reviewed institutional/financial-system evidence. Public XRPL activity, Ripple corporate products, private XRPL-derived systems, sidechains, pilots, announcements and broader tokenization projects are not treated as interchangeable.
• A monitored webpage change, content fingerprint change or keyword match creates a candidate for review and does not automatically become a verified adoption or integration claim.
• Integration and settlement-readiness scores summarize the evidence model and current operating conditions. They are not forecasts, endorsements, investment ratings, regulatory conclusions or probabilities of adoption.

12 · Tokenization, local files and evidence NFTs

No automatic legal ownership, authenticity or regulatory approval

• The free Asset Tokenization Auditor is designed to let users model the represented asset/right, parties, evidence, architecture and controls; hash selected evidence locally; and generate a local Evidence Pack without requiring a wallet.
• The Advanced Auditor may restore the same browser-local project and Evidence Pack after the disclosed access gate instead of creating a second unrelated record.
• Where the Local Asset Vault is used, evidence bytes are stored in browser-local storage keyed to the local project/evidence identity. Browser storage can be cleared, corrupted, blocked or lost. Users are responsible for backups.
• When a workflow requires a source file to be selected again, the interface may compare the newly selected file's SHA-256 fingerprint with the prior record. Matching bytes do not prove legal ownership, authenticity, consent or authority.
• An optional XLS-20 evidence NFT may bind a compact on-ledger record to local evidence hashes. Such an NFT is an evidence/chronology record unless a valid external legal system separately recognizes additional rights.
• Creating an NFT, memo, metadata file, file hash or Evidence Pack does not create, transfer, perfect, register, insure, appraise or validate title, custody, authenticity, a lien, contractual rights, regulatory status, court admissibility or enforceability.
• Users are responsible for privacy, rights, permissions, intellectual property, confidentiality, sanctions, licensing, registration, consumer protection, custody, valuation, tax and jurisdictional requirements.

13 · Support, security and confidential information

Support channels are not custody or a secret-storage service

• The Support page and official contact channels are intended for project support and security reporting. They must never be used to send a seed phrase, private key, recovery phrase, one-time password, device passcode or other wallet secret.
• Support features may change and may include email, browser-local ticketing, evidence references or other communication mechanisms. No support channel is guaranteed to be confidential, continuously available, encrypted end-to-end, admissible as evidence or appropriate for regulated information unless expressly stated.
• Security reports should follow /.well-known/security.txt. Public disclosure before remediation can increase risk.
• Security controls reduce risk but do not make the site, browser, wallet, device, hosting provider, proxy, third-party SDK or public blockchain immune from compromise or failure.

14 · Financial-system references and non-affiliation

SWIFT, BIC, ISO 20022, BIS and institutional references

• XRBitcoinCash is not SWIFT, is not a SWIFT member or service bureau, and does not claim access to or participation in the SWIFT network.
• XRPL transactions are not represented as SWIFT messages, bank transfers, correspondent-banking settlement or central-bank money.
• References to SWIFT, BIC, ISO 20022, BIS projects, tokenization initiatives, regulated-market infrastructure or financial institutions are descriptive/research context unless an exact source establishes a specific relationship.
• Such references do not imply certification, membership, sponsorship, endorsement, authorization, compatibility or regulatory approval.
• A future integration with a regulated institution or messaging network would require separate authorization, contracts, technical validation, legal/compliance review and updated disclosures.

15 · No professional advice

No financial, legal, tax, accounting, cybersecurity or investment advice

• Site content, White Papers, Terms, tool outputs, code, scores, evidence and communications are general information and decision-support materials.
• Nothing is a recommendation to buy, sell, hold, issue, redeem, tokenize, list, trade, provide liquidity, establish a trust line, bridge assets or use a particular wallet, route, pool, exchange, merchant or service.
• No attorney-client, accountant-client, adviser-client, broker-customer, fiduciary or other professional relationship is created.
• You are responsible for independent research and for consulting qualified professionals when appropriate.

16 · Eligibility and user representations

Who may use the site

By using the site, you represent that you have legal capacity; your use is lawful where you are located; you are acting for yourself or with valid authority; you are not a prohibited or sanctioned person; and your use does not require the XRBC Operator to hold a license or authorization it does not have.

You must not use the interfaces on behalf of another person in a way that constitutes unlawful custody, brokerage, money transmission, exchange, payment processing, investment management or another regulated activity.

17 · Prohibited conduct

Prohibited uses

You may not use XRBC, the website or an XRBC Tool to violate law or sanctions; commit or facilitate fraud, theft, market manipulation, money laundering, terrorist financing, ransomware, bribery, tax evasion or deceptive tokenization; impersonate a project or regulator; falsely claim a banking/SWIFT/Ripple/Xaman relationship; obtain another person's wallet secrets; evade security/rate limits; abuse Xaman payloads; falsify evidence; or misuse third-party data, software, trademarks or services contrary to applicable rights or terms.

18 · Illicit-finance controls

Sanctions, AML and legal restrictions

• Digital-asset activity remains subject to applicable economic sanctions and illicit-finance laws.
• The XRBC Operator may restrict, geofence, suspend, preserve records or report activity when required by law, a valid legal order, service-provider rule, or reasonable compliance/security concern.
• Self-custody does not remove a user's legal obligations.
• No feature is designed to conceal transaction origin, destination, ownership or control or to defeat lawful blocking, reporting or identification requirements.

19 · Independent services

Third-party platforms, data and links

• The site may use or reference Xaman, XRPL infrastructure, explorers, DEX interfaces, AMMs, NFT markets, token metadata services, hosting providers, analytics, browsers, operating systems, market-data providers, institutional websites and other external sources.
• Third parties are independent. Inclusion does not imply endorsement, sponsorship, agency, partnership, certification or responsibility.
• The XRBC Operator does not control and is not responsible for third-party content, fees, warnings, token labels, trust scores, censorship, outages, errors, security, legality, data retention or losses.
• Links and APIs can become unavailable, stale or incompatible at any time.

20 · Costs and reporting

Ledger fees, service fees, market costs and taxes

• You are responsible for XRPL reserves and fees, wallet/service fees, market spread, slippage, transfer fees, taxes, network costs and other charges.
• Displayed fees and estimates may change before authorization or validation.
• The XRBC Operator does not promise the cheapest or best route.
• You are responsible for tax classification, basis, valuation, reporting, withholding and payment obligations.

21 · Data, browser state and public ledger

Privacy and local-storage terms

• XRPL addresses, transactions, balances, trust lines, offers, AMMs, NFTs and issuer settings are public and generally cannot be deleted by the XRBC Operator.
• Interfaces may store theme settings, watchlists, trend history, pending Xaman request identifiers, draft projects, gate state, Evidence Packs, Quote Passports or Local Asset Vault data in the browser. Clearing storage, private-browsing restrictions, device changes or browser policies can remove that data.
• Where a page states that selected evidence files are processed locally, the intended application design does not intentionally upload those file bytes. That statement is not a guarantee about browser extensions, malware, operating systems, networks or unrelated third-party software.
• Do not put confidential, regulated, proprietary or personally sensitive information into public transaction fields, memos, NFTs or metadata unless you understand the permanence and disclosure consequences.
• Additional data-handling terms appear on the Policy & Security page.

22 · User-controlled security

Wallet, device and transaction responsibility

• You are responsible for wallet secrets, recovery materials, devices, browser extensions, addresses, Destination Tags, transaction fields, backups and security practices.
• Verify the official domain and independently review every wallet request. Phishing, malware, malicious extensions, compromised DNS, clipboard substitution, screen overlays and social engineering can defeat user expectations.
• Do not treat a site logo, QR code, deep link, browser status message, AI response or wallet label as proof that a transaction is correct.
• When an interface shows an intended transaction snapshot, verification code or expected field set, discrepancies are a reason not to sign.

23 · Assumption of risk

Material risks accepted by the user

• You accept risks including total loss, irreversible transactions, volatility, illiquidity, wide spreads, slippage, partial payments, pathfinding changes, failed transactions, front-running, market manipulation, concentration, issuer controls, freezes, clawback permissions, trust-line configuration, protocol amendments, software defects, browser-storage loss, phishing, malware, outages and third-party failure.
• You accept that a bridge, AMM, order book, wallet, token, evidence source, institutional integration, settlement workflow or tokenization record can fail or be misinterpreted even when a tool does not display a high-risk warning.
• You accept that regulatory, tax, sanctions and classification rules can change and may restrict access, transfers, listings, markets or project activity.
• You accept that automated analysis, AI output, source-monitoring systems, scores and metadata can be wrong.
• You bear the risk of loss except to the extent applicable law does not permit that risk to be allocated to you.

24 · Disclaimer of warranties

“As is” and “as available”

To the maximum extent permitted by law, XRBC, the website, documentation, interfaces, transaction templates, source monitors, scores, bridge records, readiness evidence, Evidence Packs, Local Asset Vault features, settlement receipts, Quote Passports, support functions and XRBC Tools are provided “as is,” “as available,” and with all faults.

The XRBC Parties disclaim warranties of merchantability, fitness for a particular purpose, title, non-infringement, accuracy, completeness, timeliness, security, confidentiality, availability, compatibility, legal compliance, regulatory classification, liquidity, execution, value, source authenticity and error-free operation.

No statement guarantees price, demand, listing, market depth, bridge safety, institutional adoption, title recognition, evidence admissibility, continued development, support, transaction success, third-party acceptance or protection from loss.

25 · Limitation of liability

Limits on damages

To the maximum extent permitted by applicable law, the XRBC Parties will not be liable for direct, indirect, incidental, consequential, special, exemplary, punitive, reliance, business-interruption or similar damages arising from XRBC, the site, an XRBC Tool, a transaction, bridge research, readiness evidence, tokenization record, settlement invoice/receipt, support communication, third-party service, data error, source change, loss of keys, loss of browser-local data, trading loss, tax liability, lost profits, lost opportunity, loss of goodwill, security incident, regulatory action, or inability to use a feature.

This limitation includes losses arising from a stale or incorrect quote, incorrect score, missing warning, false positive, false negative, unavailable data, route change, Destination Tag error, user-supplied evidence, third-party exploit, bridge failure, wallet compromise, Xaman request issue, tokenization misclassification, or reliance on a ledger/evidence record beyond what that record can prove.

If liability is imposed despite these limitations, aggregate liability of the XRBC Parties will not exceed the lesser of the amount paid directly to the XRBC Operator for the specific website service giving rise to the claim during the preceding twelve months or the minimum amount required by applicable law. Non-waivable rights remain unaffected.

26 · Indemnification

Responsibility for third-party claims

To the maximum extent permitted by law, you agree to defend, indemnify and hold harmless the XRBC Parties from third-party claims, proceedings, investigations, damages, losses, penalties, liabilities, costs and reasonable attorneys' fees arising from your unlawful use of XRBC or an XRBC Tool, your content or tokenization project, your signed transaction, your violation of these Terms, or your violation of another person's rights.

27 · Intellectual property and attribution

Project and third-party rights

• XRBitcoinCash names, logos, branding, original site design, documentation and original content are owned by their respective rights holders.
• Open-source components remain subject to their licenses.
• XRP, XRP Ledger, XRPL, Ripple, Xaman, Xumm, SWIFT, BIC, ISO, Sologenic, XPMarket and other names/marks belong to their respective owners.
• Descriptive references do not imply sponsorship, endorsement, certification, partnership, agency or ownership.
• You may not use XRBC branding or copied interfaces to conduct phishing, impersonation, fraudulent tokenization or deceptive wallet requests.

28 · Changes, suspension and termination

Feature and Terms updates

• The XRBC Operator may modify, suspend, restrict, geofence, discontinue or replace content, gates, scoring models, source registries, APIs, transaction flows, support functions or services at any time.
• Safety-critical interfaces may fail closed when data, authorization, source integrity or transaction state cannot be verified.
• Access may be restricted for abuse, sanctions risk, security concerns, third-party requirements, legal uncertainty, maintenance, resource limits or evidence-quality problems.
• The current Terms posted at https://xrbitcoincash.com/terms.html supersede prior versions.

29 · Legal construction

Mandatory law, disputes, waiver and severability

• These Terms do not waive rights or protections that cannot lawfully be waived.
• Governing law, jurisdiction and venue are determined by mandatory law and the facts of a dispute unless a valid separate agreement specifies otherwise.
• Before filing a non-urgent civil claim, you agree to provide written notice and allow thirty days for an informal attempt to resolve it, except where prohibited by law or immediate relief is reasonably necessary.
• Failure to enforce a provision is not a waiver. Invalid provisions will be limited to the minimum extent necessary and remaining provisions continue in effect.

30 · Official contact

Contact and authorized channels

Official project contact methods include:

• Email: xrbitcoincash@gmail.com
• Official X account: @XRbitcoincash
• Support: xrbitcoincash.com/support.html
• Security reports: /.well-known/security.txt

Never send a seed phrase, private key or recovery phrase. Xaman support must be obtained through official Xaman channels.

31 · Incorporated references and conflict rules

Related documents and controlling records