Terms for reservations, the Genesis pass and .on names.
Draft of 10 October 2026, revised after a clause-by-clause check against what the software does. Square brackets mark something that is not decided yet, or that depends on a choice the founder or counsel has still to make.
1. What this covers
These terms cover three things offered by OpenApps [legal entity, registration number and address: to be added] ("OpenApps", "we"):
- a reservation of a .on name, made on this website;
- Genesis membership and its public badge, the Genesis pass, claimed inside OnWallet;
- a .on name, claimed inside OnWallet.
The rules about which names exist, how a name is recorded and when a name can be ended are in the name policy. [The page linked here is the working document, with defaults still open. A dated public edition, with every default settled and a statement of how it can change, will be the one that forms part of these terms.] How personal data is handled is in the privacy notice.
Other terms apply too. A claim is made with OnWallet and an OnWallet ID, and the perks are delivered through an OpenApps account. Each has its own terms and rules, among them: an OpenApps account holds one OnWallet ID; an ID that moves to another account waits 30 days before it earns again; a newly added sign-in method cannot remove the others for 7 days. [Which terms prevail where they differ: for counsel.]
2. Reservations
- A reservation is a hold, not ownership. It keeps one name for one verified email address. It gives no right to the name, to membership or to an invite key.
- One reservation per verified email address. Two addresses that reach the same mailbox count as one: capital letters and anything after a + sign are ignored, and for Gmail the dots too. Someone with several mailboxes can make several; each lapses unless it is claimed.
- A mail domain that is not a large public mail provider can hold at most [5: a default the founder has not confirmed] reservations, so that one person cannot hold many names through a domain they control. If your provider is counted by mistake, write to us [contact address: to be added].
- When you ask for a reservation the name is held for 30 minutes while you open the link we email you and confirm on the page it opens. Opening the link does not confirm anything by itself. The link works once, for 24 hours. If you confirm after the 30 minutes, the name may have been taken by someone else.
- If you ask for several names before confirming one, each is held for its 30 minutes, the first you confirm is your reservation, and the others are dropped.
- The form sends one address at most three messages an hour. Past that it answers as usual and sends nothing, so that it cannot be used to flood someone's mailbox; wait an hour and ask again.
- A confirmed reservation gives you a short code. You type the code into OnWallet when you claim. The code is useless without an invite key.
- A confirmed reservation is held until 14 days after the date your wave opens, which we will email to you [period to be confirmed]. If the name is not claimed by then, the hold lapses and the name is available to others.
- You can cancel at any time with the cancel link in your verification or confirmation email. The two later notices (your wave has a date; three days left) carry no link of their own and point you to the confirmation email. You are asked to confirm the cancellation on the page it opens. The reservation and your email address are then deleted from our live systems at once, and from encrypted backups within 30 days. Our email provider keeps its own delivery records for [period: provider not chosen].
- We may refuse or end a reservation for a name the name policy does not allow, and we may pause reservations. A pause does not shorten a hold.
- The name rules are applied automatically and are cautious on purpose, so they sometimes refuse an ordinary word. [There is no process yet for releasing such a name. Either one is published, or this sentence says that an automatic refusal is final: founder's decision.]
- Reservations are limited in number. When they are full, no more are taken.
3. Genesis membership and the Genesis pass
- Genesis membership belongs to your OnWallet ID. It begins when you enter an invite key. The Genesis pass is a public badge of that membership, recorded as a non-transferable (soulbound) NFT on the XRP Ledger. Perks depend on the membership, not on holding the badge.
- The pass has no price, cannot be sold, and carries no promise of any token.
- You cannot transfer or sell the pass, and a pass is never issued again: not to a new address, and not after it is removed or lost. If you lose the key to the account that holds it, the badge stays in that account; your membership and its perks, which belong to your OnWallet ID, are not affected. [If passes are made burnable by the issuer: we can remove a pass only as the policy says. Whether passes are burnable is not decided; it is fixed before the first pass is issued and stated here.]
- The ledger lets a holder destroy (burn) their own pass. OnWallet does not have a button for this yet; one is planned for a later release. [Until then, if passes are issuer-burnable: write to us and we will burn it at your request.]
- Passes are numbered in the order they are accepted on the ledger. The number and the level are recorded by us and can be corrected by us.
- We will issue no more than 5,000 passes [cap and closing date to be confirmed].
- The pass gives no right to payment, profit, ownership or repayment, from OpenApps or anyone else.
4. .on names
- A .on name is an NFT on the XRP Ledger, separate from the Genesis pass, held in your own account.
- A name cannot be sold or transferred today. The token issued now can never be transferred. The intention is to offer, later, to replace it with a transferable one. No date is promised, and nothing here is a promise that it will happen. [Whether the intention is stated at all: for counsel.]
- One name per OnWallet ID. Further limits apply and are shown in the wallet: how often the chosen name or the claiming account can be changed before the name is issued, and how often a claim can be repeated when an offer runs out (an offer lasts 24 hours).
- No fee is charged for a name claimed with a Genesis invitation, and such a name has no renewal fee. Names issued later are intended to carry a platform fee; none has been set or published.
- We are technically able to end (burn) any name. We promise to do so only on the grounds in the name policy, and to publish each case in a public log. A name's NFT is also burned, without being a revocation, when an offer nobody accepted runs out.
- The registrar decides which names exist. What anyone can check on the ledger, and what depends on the registrar, is set out in the name policy and on How to know it is real. [The reserved list is a starter list. It has not had its review and is not a trademark search; these terms are not published before it has.]
- Today .on names are read by OnWallet only. Other wallets and explorers do not resolve them.
5. Lost keys, ending a name, and complaints
[Every period in this section is a default in the name policy that the founder has not confirmed.]
- If you lose the key to the account that holds your name, you can ask for the name at a new account. We burn the old NFT, publish that we did in the public log, wait 7 days from that entry, and issue the name again to the new account. During the wait the name points to nobody. This is done by our operators, by hand, with two of them signing each step; it is not something the wallet does for you. [How you ask, and how we check that it is you (a fresh sign-in to your OnWallet ID and a signature from the new account, under the policy): the support process is not built yet. The wallet has no screen yet for accepting a name issued this way.]
- If your name is burned by someone who has stolen one of our keys, we issue it again to the same account, with no wait. It cannot go to a different account in that case, because there is no burn of ours to publish first.
- A Genesis pass is never issued again, in either case (section 3).
- After any burn a name cannot be registered by anyone else for 90 days, so that payments meant for its last holder do not reach a stranger.
- If you burn your own name you can take a new one after that period, at most once in 12 months.
- If we end a name you can appeal within 30 days. After a successful appeal we issue it again: at once to the account that held it, or after the 7-day wait to another.
- Complaints that a name infringes a trademark or impersonates someone go to [address: the mailbox does not exist yet]. The holder has 14 days to answer unless the misuse is in progress, and two people decide. [Who they are, and whether an outside body hears disputes: to be decided.]
6. Perks
Rewards are at OpenApps' discretion and may be adjusted for long-term sustainability. That includes reducing, pausing or ending any perk below. [The software never takes back a month's credits once granted. Whether to promise that: founder and counsel.]
| Perk | What it is |
|---|---|
| Monthly OpenApps credits | Up to US$10 a month for a Member, rising by level to up to US$100 for a Steward (the two levels between: up to US$25 and up to US$50). Credits begin on a date to be published; none are granted before it. The rules below are the ones built into the software [as defaults the founder has not confirmed]. |
| How a month's credits are decided |
|
| Spending and lapse | Credits can be spent wherever OpenApps products accept credits, which includes leading AI models. What a credit buys differs between products. Granted credits are spent before credits you bought. Unused granted credits lapse at 00:00 UTC on the first day of the next month and do not roll over. Disconnecting OnWallet from your account lapses what is left of that month's grant. Credits have no cash value and cannot be transferred, exchanged or refunded. |
| Levels | Member, and three levels above it; the highest is Steward [the names Explorer and Builder for the two between are working names]. Levels are assigned by OpenApps. Every member starts as a Member, and no way of reaching a higher level has been set. Levels raise priority for any event, e.g. a community sale for a tokenised project, if one is ever held. No event is promised. Levels do not unlock more invite keys. |
| Supporter features | The Supporter features of OpenCapture and OpenPdfEdit [list and start to be confirmed, once checked in both products]. |
| No fee for your name | As section 4. |
| Early access | Access to new OnWallet releases before they open to everyone, when we offer it. |
Perks belong to the Genesis member, not to the pass as an object: they cannot be sold or assigned.
7. Invite keys, and the time you have to claim
- An invite key lets the person who uses it become a Genesis member. The person who gives a key receives nothing for it.
- A key works once. Keys are released in waves, and each wave has a cap.
- Invite keys are needed to claim. They are not needed to create an OnWallet ID or to reserve a name.
- Keys may not be sold. A key that was sold can be voided, and a membership gained with it removed. Who gave each key and who used it is recorded, as the privacy notice says.
- A claim must be completed within 90 days. The 90 days run from the day OnWallet first prepares your claim for an account (its first voucher). After that the claim is lost and cannot be opened again; the membership stays. [A default in the software; the founder has not confirmed it.]
- An invite key is not a referral code and earns nobody a referral bonus. [Whether a Genesis member may also use an OpenApps referral code: for counsel.]
8. When membership ends
- We can remove a membership for fraud or abuse of invite keys, and at your request. A removed membership cannot be regained with the same sign-in mailbox.
- Deleting your OnWallet ID ends the membership. Deleting your OpenApps account ends the perks on that account; it does not delete your OnWallet ID.
- OpenApps products learn that a membership has ended the next time you sign in with OnWallet. Until then an account you reach another way keeps showing the perks.
- Ending a membership does not remove a pass or a name from the ledger by itself.
9. Your wallet and your XRP
- You fund your own XRP Ledger account. Have at least 2 XRP in your account; your exchange may require a larger minimum withdrawal. The wallet shows the exact amount, which it reads from the ledger.
- About 1.2 XRP stays in your account as the ledger's reserve. You cannot spend it while the account and its NFTs exist. Treat it as locked. The reserve is set by the ledger, not by OpenApps, and can change.
- OpenApps pays the network fee to mint. OpenApps gives no XRP to anyone, and never asks you to send XRP to it to claim a Genesis pass or a name.
- OpenApps never holds your whole key and cannot move your funds. If you protect your wallet with OnWallet ID, the key is split into three parts: one on your device, one held encrypted by OnWallet ID, and one that you keep (a recovery kit file, a passkey, or your own Google Drive). Any two parts rebuild the key, and only on your device; our server never holds two. We can help you recover on a new device only together with the part you keep, your sign-in and your authenticator app, and after a 72-hour wait during which your email and devices are alerted.
- We can end a name, and a pass if passes are burnable, as section 4 and the policy say. That does not touch your XRP or other tokens.
- Transactions on the ledger cannot be reversed.
- OnWallet has not had an independent security audit yet. Use it with small amounts only.
10. What is not promised
- No token, airdrop, allocation, sale or financial return of any kind.
- No date for a transferable name, and no market for names.
- No particular perk, level or event in the future.
- OnWallet is an independent project. It is not affiliated with, endorsed by or partnered with Ripple or the XRP Ledger Foundation.
11. Still to be written with counsel
This list is part of the draft and is removed before the terms are published.
- The contracting entity, governing law and how disputes are handled.
- Who may take part: age, and any country or region where the offer is not made; any statement about sanctions or export rules.
- Limits of liability, the open-source licence and its "no warranty" position, and the rights consumers keep by law.
- How these terms and the name policy change, and how members are told.
- What happens to names if OpenApps stops running the registrar or the lookup service.
- Whether any part of the offer is regulated where it is made (payment-token services, promotions and incentives, referral rules for invite keys).
- Whether "no promise of any token" and "priority for any event" can stand on one page, and whether the intention to make names transferable is stated.
- Screening of addresses before an NFT is issued.
- A complaints contact, and any notice about the names "XRP" and "XRPL".