RNNR CALLS / EDITION 2026-10-19.1

Welcome to RNNR Calls

Make a call. Share it with your crew. Settle together.

RNNR Calls turns the conversation around a game into a game of its own. Say what you think happens next, attach a RNNR amount, and let someone take the other side. When you agree on the outcome, the app updates your balances. No platform cut. No compulsory referee. No wallet popup for every call.

It works for two friends at a bar, a watch-party thread, or an ongoing fantasy league. Sports are a starting point, not a restriction on your imagination. A clear custom sentence is just as welcome as a next-goal template.

This is a Memecoin Arcade experiment grounded in a regenerative idea: put the entertainment and the people first, and let value circulate through their communities rather than taking a slice of every interaction.

What this first release is

Version 0.1 is a standalone mobile-web app with a persistent server ledger. It includes three commitment styles, private rooms, league standings, share links, mutual settlement, optional jointly chosen referees, and a Solana deposit/withdrawal implementation. The default server and the separate single-file preview use clearly labeled synthetic balances. Only a separately configured live server can accept real RNNR.

The release package is not a live deployment, an audited custody service, or a shared balance with existing RNNR or Slots installations. The actual deployment mode is always shown at the top of the app.

Get into the game

Open RNNR Calls in a normal browser. In the demo, choose Paul, Mike, Nic, or Jess. Each starts with synthetic RNNR; switch players to try both sides of the handshake.

On a configured real-token server, sign in with your Solana wallet. A signed message proves control of the wallet without authorizing a token transfer. The resulting browser session lets you play without signing each challenge.

On your phone

Use the normal mobile website for playing. When the browser has no injected wallet provider, choose browser pairing. It creates a short-lived code for this browser. Open the approval page in your wallet browser, sign in, and approve that code. Return to the normal browser, check the exact wallet shown, and explicitly confirm the pairing. Do not approve pairing codes sent by strangers.

Deposits and withdrawals remain explicit wallet-boundary actions. Those may require the wallet browser; ordinary calls do not. A session is device-specific. Another phone or computer needs its own sign-in to the same wallet account. This build does not use a username/password recovery system or an email magic-link service.

Your first call

Open a watching room, tap Make a call, write a claim, select the participation style and amount, and specify which game or event it refers to. Send the resulting link to your existing thread. The other player opens that exact call, reviews the rules and accepts. After the event, propose the outcome and get matching confirmation.

You can also keep the same room open on two phones. Calls and balance updates appear through the app's own live activity connection. No external sports feed is required.

Your RNNR balance

Your balance has three buckets: Available, In play, and Withdrawing. Their sum is your game balance.

Available RNNR can back a new call or be withdrawn. In-play RNNR is reserved for outstanding calls. Withdrawing RNNR is held while its explicitly authorized transfer is reconciled. A token cannot be available for all three uses at the same time.

The bar example

You and a buddy each deposit 1,000 RNNR. The custody account holds 2,000. You each commit 100 to a call. Until it is resolved, each of you has 900 available and 100 in play. You win, you both confirm, and the ledger changes your balances to 1,100 and 900. The custody account still contains the same 2,000 tokens. No on-chain transaction was needed for that result.

You can withdraw your available 1,100; your buddy can withdraw their available 900. You do not have to win before withdrawing. Unplayed tokens remain yours to withdraw.

Creating an offer reserves its initial amount automatically. Accepting it commits the accepting player's amount automatically. These are accounting steps inside the app, not new wallet transactions or manual deposit steps. Closing an unmatched offer returns its unused backing to available balance; accepted commitments remain in play until resolved.

Exact amounts

This build uses the configured RNNR mint's six decimal places. Amounts travel as decimal strings and are accounted for as integer base units, never floating-point balances. The smallest accepted positive amount is 0.000001 RNNR. The token format imposes a technical unsigned-64-bit limit, not a discretionary platform wagering cap. Sufficient available backing is always required.

Three ways to make a call

Take me on: an amount against each challenger

“100 RNNR says my call happens.” Each acceptance forms a separate equal-stake matchup. Three challengers means the creator is committing 300 and the challengers 100 each. Each pair settles separately, so a disagreement in one does not trap the others' payouts.

The first 100 is reserved when the call is created. Additional matches use additional available backing. Once there is insufficient backing, new acceptances fail rather than creating an uncovered promise. There is no hidden permission to overdraw the creator's account.

Split my stake: one total amount

The creator offers 1,000 total. Opponents might match 500, 300, and 200. Each has a separate equal-stake matchup for their chosen part. Nobody can accept beyond the remaining offer. Closing entries returns any unmatched portion to the creator. Already matched portions stay committed.

Make a pot: everybody picks a side

Players contribute to either the call or the other side. The winning side receives the entire pot, in proportion to each winner's contribution to that side. This is not a fixed return while entries remain open.

For example, the Yes side contributes 300: Alice 100 and Bob 200. The No side contributes 300. If Yes wins, the 600 pot returns 200 to Alice and 400 to Bob. The original contributions are included in those returns. The platform keeps zero.

Integer rounding uses largest remainders, with contribution order breaking ties. Every base unit is allocated; no dust is silently retained as a fee. A pot with only one side funded is refunded when entries close. The first version supports one contribution per participant per pot. All pot participants agree on its common outcome, or jointly authorize one neutral referee.

Clear calls and fast events

The claim, opposite outcome, event context, acceptance cutoff, cancellation rule, amount and participation style form the rules of a call. They are fixed once the call is created. To change them, close the unmatched offer and create a new call. Accepted commitments cannot be rewritten by editing the text.

“McDavid scores next” is not enough context for a link that someone might open tomorrow. Include the particular game, date, period, or stoppage. A good quick call identifies the exact event and what happens if that event does not occur.

Example: Edmonton wins the faceoff immediately after this TV timeout. Accept before the puck drops. Cancel if that faceoff is abandoned or the event cannot be identified by both participants.

The server records acceptance time and closes entries at the specified time. The creator can also close entries early. A result proposal closes remaining entries. Closing does not reverse already accepted positions.

What timing controls do not prove

A clock does not prove what a player already saw on a faster television feed. The app cannot infer an actual puck drop, detect every late acceptance, or know whether a player has inside information. Quick event calls rely on the participants agreeing that the acceptance was timely. A dispute is handled through the same handshake flow, not an invented live oracle.

The time limit shown in the composer is a convenience for the offer window. It is not an automatic sporting-event detector, settlement timer, or authority to award a win by silence. Do not accept a call after learning its outcome.

Watching rooms and leagues

A watching room keeps a group focused on the same event or conversation. A league adds a persistent group and a season label. Both use the same player's RNNR balance; joining a room does not mint a new currency or move tokens to another economy.

Invite friends using the room link. The person holding an invitation can join, so share it deliberately. The room creator can rotate its invitation through the server API; existing members are not removed by rotation. A first-version room is not an identity-verified membership organization.

Members can make calls, share a small room message, and add a member-entered score/context strip. Those entries are labeled with their author and time. They are conversation aids, not official data or automatic settlement instructions.

Standings

Standings count net RNNR won or lost through settled calls. Deposits, withdrawals and synthetic demo grants do not inflate the score. Room standings include that room's settled calls. The broader standings shown to you are limited to your visible crew and counterparties; they do not expose a public directory of every account.

Your complete wallet balance is not a league score. Other users can see their calls' contributions, results and displayed standings, but not your full private account history.

Season labels do not yet schedule resets. Create a new league room for a clean competition period. This version does not import fantasy-platform rosters, send invitations automatically, remove members through a management UI, or include a public matchmaking feed. A direct call still works between people who are not in a league.

The handshake and optional help

Normally, one participant proposes the call happened, the other side won, or mutual cancellation. The other participant selects the same outcome. The server moves the committed tokens and records the result once. In a shared pot, all contributors agree on the same outcome.

A player can change their own proposed outcome while the call remains unsettled. Matching agreement is required; there is no automatic win for being first to click. A settled payout cannot be repeated by refreshing the page or resubmitting the same request.

When you disagree

The app offers help without imposing it. Participants can compare evidence, mutually cancel, or choose a neutral registered player as referee. Each participant independently selects the same person. That shared authorization permits the selected referee to settle that matchup or pot. A creator cannot appoint a binding referee by themselves, and a commissioner receives no automatic power from their title.

A search link opens an external search for the call's context. It is a research aid, not an agent that silently moves tokens. There is no automated Google adjudication in this release.

A support request is saved with a reference. The app then offers an email draft to [email protected]. The email is not sent automatically. Support has no guaranteed response time, and saving a ticket does not appoint the operator as referee or change a balance.

Outstanding commitments

Without agreement or an authorized referee result, disputed commitments stay in play. An entry window expiring closes further acceptance but does not refund an accepted losing position. Neither player can withdraw the other's tokens, cancel unilaterally, or win by ignoring the other. This means an unresolved challenge can remain locked indefinitely. Use the game with people whose agreement you trust.

The token and the custody boundary

This build uses RNNR on Solana mainnet-beta:

B65EtDpt6KUAVRDECNKhE9FXGNZRToVpdhU8zE7kpump

It is configured as a six-decimal Token-2022 asset. The configured identifier comes from the existing RNNR release; live operation additionally checks the on-chain mint and supported account properties before preparing transfers. A matching name or logo is not enough.

Real-token mode

The operator controls a dedicated Calls custody wallet. The internal ledger records which deposited tokens belong to which players. This is operator custody, not a newly deployed trustless escrow contract. Player private keys stay with their wallets, but control of deposited tokens rests with the custody signer and the operator's records.

A prepared deposit specifies the exact mint, source, destination and amount. Credit requires a matching finalized transaction and exact token-balance changes. A successful deposit cannot be credited twice. A normal transfer sent directly to an address without the prepared intent is not guaranteed to be credited automatically.

Withdrawal reserves an available amount, asks the owning wallet to authorize that exact withdrawal, and stores signed transaction bytes before broadcast. Uncertain submissions are checked and retried as the same transaction, not recreated as a new payment. If signed evidence cannot be resolved, the amount remains held for reconciliation. Never blindly restore an old database over newer balances.

The operator pays withdrawal network fees in SOL in this build. Deposit transaction network fees come from the depositing wallet. Third-party purchase/sale fees are separate from the game's zero take rate. Both player and custody associated token accounts must already exist and meet the supported configuration.

Separation from other games

The first release has its own database and custody configuration. It does not read or absorb the production RNNR, Vault, or Slots balances. A shared Arcade balance remains a platform integration task, not an accomplished migration. No depositor tokens are lent, invested in DeFi, converted to dollars, or used for operating costs by this code.

Sports data without pretending

There are two separate update streams. RNNR Calls knows its own calls, acceptances, messages, confirmations and balances. It broadcasts changes through authenticated server-sent events. It does not need to know what happened in a stadium to make that activity responsive.

External sporting events are different. This release has no paid feed, scraped live feed, broadcast video, automatic score API, or sports oracle. The score strip is entered by room members. Demo games and scores are marked illustrative.

Light source review, 19 October 2026

The nflverse project documents nightly play-by-play updates and raw game files typically available shortly after a game ends. Its schedule/game dataset updates every five minutes during the season. That makes it useful to investigate for contextual schedules, but it does not establish a licensed, second-by-second next-faceoff or next-snap service. See the project's data availability schedule.

A free, production-suitable, granular live feed across the requested sports was not verified for this release. That is a limit of this investigation, not a claim that no such data exists. Public access to an endpoint is not by itself a confirmed right to redistribute it commercially.

A later integration should separately establish rights, event coverage, update delay, corrections and outage behavior. It can add game selection and supporting evidence without taking settlement authority away from players. A search result, an event feed and the app's ledger are distinct sources of information.

The bigger Arcade

The ambition is an arcade where creators bring games worth playing and communities bring their memecoins. Different games can explore different mechanics while sharing the expensive, repetitive work of building accounts, wallets, token accounting, hosting and player experiences.

Regenerative liquidity is the idea that value can keep circulating through people making and playing things. The point is not to extract a percentage from every friendly interaction. RNNR Calls takes no platform share of a settled challenge. Hosting, development and blockchain operations still have real costs; zero take rate is an operating choice, not a claim that infrastructure is free.

RNNR is the intended shared Arcade token. Interoperability would let the same player and community participate across multiple games. That is why Calls uses RNNR rather than issuing a different league currency for every friend group.

The AI gaming harness

The longer-term goal is to describe a game and have a reusable harness help build, test, deploy and operate it. Wallet infrastructure and game components should be reusable instead of rebuilt for every experiment. Creator-controlled token issuance, launchpad mechanics, supply allocation, bonding curves, creator fees and inflation rules belong to that platform roadmap.

A custom network or Layer 1 is a possible later direction, not part of this release or an obligation of token ownership. A future yield-funded, regulated dollar product would be a separate design, not permission to put today's player custody into DeFi. No automatic token migration, new coin launch, treasury investment or holder distribution is implemented here.

Make the game excellent. Keep the mechanics legible. Let the community do something worthwhile with it.

Truth, adult use and responsible play

RNNR Calls is intended as an arcade and social experiment, not an income plan. Memecoins are speculative. RNNR may have a market price and may lose all market value immediately. An arcade intention or a very small amount does not erase an external market price. No market capitalization, liquidity, dollar redemption value or return is guaranteed.

The adult-use acknowledgment requires users to state they are at least 18 and satisfy any higher applicable age requirement. This is a declaration, not government-ID verification. The first version does not implement identity verification or country geofencing. Neither that fact nor a disclaimer is a guarantee of lawful availability in every location. Do not use the service where your participation is prohibited. The operator also retains its own legal obligations.

The SEC staff's February 2025 statement discusses certain meme-coin transactions under federal securities law. It expressly limits its scope and says it has no legal force or effect. It is not an approval of RNNR Calls or a general authorization for sports wagering. Read the primary statement. This distinction does not change the project's regenerative aspiration; it keeps its documentation truthful.

Custody, software, wallet compromise, outages, ambiguous calls and counterparties who refuse to agree can all cause loss or delay. The app does not provide deposit insurance, a guaranteed dispute deadline, automated self-exclusion, or protection against every abusive player. Do not commit money or tokens you need for living expenses, and do not chase losses.

In the United States, call or text 1-800-MY-RESET (1-800-697-3738) or use the National Council on Problem Gambling's help resources. Outside the US, use an appropriate local support service. The helpline is independent of RNNR Calls.

FAQ and release boundaries

Can I use it without a fantasy league? Yes. Create a direct call and send its link, or make a small watching room.

Do I have to open Phantom for every bet? No. The app session handles ordinary calls and settlement. Wallet authentication, deposits and withdrawals are separate boundary actions.

Can I withdraw without winning? Yes. Unplayed tokens and any remaining available balance are withdrawable. Accepted commitments and pending transfers are not simultaneously available.

Is there a take rate or pot rake? No platform percentage is removed. Actual wallet/network and third-party trading costs are separate.

Can anyone make the final decision for us? Only when all relevant participants authorize the same neutral referee. Otherwise, the participants settle together.

Can someone join a pot several times? Not in version 0.1. One contribution per participant keeps the common-outcome consent and payout rules unambiguous.

Do I get a new token for my league? Not in this release. RNNR is the configured token. Custom token creation is a separate platform initiative.

Are scheduled airdrops, referral bonuses, autonomous evidence agents, native iMessage apps and a public lobby included? No. They remain roadmap concepts, not functioning controls disguised as finished features. Synthetic demo grants are not real airdrops.

Is the GitBook already published on GitBook's hosting? This package contains a separate complete book in Markdown, its table of contents, and a readable in-app HTML edition. Creating and publishing a hosted GitBook space remains an account/deployment action.

What is ready to try now? The full local game loop, all three stake arrangements, shared rooms, manual context, player settlement, optional referees, standings, account history, share-page generation and documented wallet boundary. Real-device wallet tests, a public HTTPS installation and live-fund acceptance testing are still separate deployment work.