Browser callCall · Ringfence · example
MumA money packet, 1 NEAR, five grandkids. Words: merry christmas.
RingfenceA money packet of 1 NEAR for 5 people, lucky split. Your PIN, please.
Mum blanked from the transcript
phone.you.near · contractApproved · 1 of 3 NEAR today · packet ready to share

Real NEAR mainnet. Demo PIN 4821. Tap a line below or just talk. The demo wallet contract caps a send at 1 NEAR.

WhatsApp +60 11-7512 3486 opens once Meta approves us. Same agent. Try it on WhatsApp now · on a call: Live panel.

The live room's AI hostLIVE

New · Live room

Gift real NEAR on a live stream, by phone call.

  • Tap a gift: a call sends it with your PIN, on mainnet.
  • An AI host thanks every gift out loud. Gifts from any NEAR wallet show up too.
  • Grab a money packet live, or put the overlay on your own Twitch or YouTube stream.
Enter the live room

The 85-second film, sound on: the agent speaks with the same voice as the live call. The transactions it shows are real, on NEAR mainnet. The call scenes are acted.

Three steps: Mum calls and asks for a money packet with the words merry christmas; the wallet contract checks the limits and locks the money; each grandchild says the words on a call and gets a share.
Call · unknown caller00:48
YouThis is your bank. Move 50 NEAR to safe-vault.near now.
Ringfence50 NEAR to safe-vault dot near. Your PIN, please.
phone.you.nearRefused over the 1 NEAR limit. safe-vault.near is not a saved recipient, so even a small send would wait first (60 seconds on this site).

Scammers talk people into paying. And AIs.

Say someone claiming to be her bank asks for 50 NEAR, and the AI falls for it and asks for the PIN.

The contract still refuses. 50 is over the 1 NEAR per-transfer limit, and safe-vault.near isn’t saved, so a smaller send would wait (60 seconds on this site) for the owner to cancel it.

If we went rogue, a bound wallet would lose at most its daily limit: 3 NEAR a day by default, and 60 USDC if it holds any.

What happens on the call

The agent passes every payment to the contract for approval. Scroll through one call.

She calls the line

From WhatsApp, or from the browser call on this page. Her number is bound to a NEAR wallet once: with one signature from the owner’s wallet, or by texting “create a wallet”, which makes one that Ringfence holds until it is claimed.

Browser callconnected
RingfenceHi, it’s Ringfence. What would you like to do?
YouSend 0.1 NEAR to liho.near.
phone.you.nearNEAR
Agent asks: 0.1 NEAR to liho.near
Approved

Inside both limits, to a saved recipient. It goes straight away.

This transfer0.1 of 1 NEAR
Today, after this0.1 of 3 NEAR
Recipientliho.near, saved
Signed byagent key, inside the limits

What the AI can’t do

A model of the contract’s rules with the mainnet defaults. Nothing here touches a chain.

1 NEAR per transfer

Ask for more and the agent tells you, then sends a link to sign it yourself.

3 NEAR a day

Per asset. It is the most that can move in a day, whoever runs the operator.

Already sent today

New recipients wait first

Saved recipients go at once. On a wallet you own, the agent never sends to anyone else: you get a link instead. The wait is the backstop if the agent key ever tries. The owner sets it: the demo wallet on this page waits 60 seconds.

Recipient

3 wrong PINs lock the line for 15 minutes

And the owner can switch the AI off with one transaction.

The family can own the wallet

The AI holds an agent key, and all that key can do is ask. A wallet made by text is held by Ringfence at first. It belongs to the family, or to Mum, once they bind or claim it with their own NEAR account. The owner sets the limits, saves the people Mum pays, and can switch the AI off.

Limits
Per transfer and per day, written in the contract. The AI can’t change them.
Saved recipients
Mum pays saved people straight away. For anyone else the owner gets a link to sign in a wallet. A phone-only wallet has no owner to sign, so the contract holds a first payment for a wait, then sends it.
Revoke
revoke_agent switches the AI off. The agent can never become the owner.

Already on NEAR? Bind your number to a wallet you own: connect any NEAR wallet, prove the number with a WhatsApp code, sign one call. You are the owner, nobody can change the wallet code after it is made, and one transaction switches the AI off. Only a phone? Text “create a wallet” and claim it to your own account later.

phone.you.nearowner view

you.near owns it. The AI can ask for up to 1 NEAR a send, 3 a day, to liho.near.

New recipientwaits a set time (60 seconds on this site), owner can cancel
AgentRingfence operator, can only ask

Who pays for this

Brands can fund packets (contract only)
A shop or a community could fund a packet as a promotion. The packets contract has a campaign option on its create method: it takes 5% plus 0.013 NEAR per share when the packet is funded, and sends that to the contract owner, a Ringfence account. Nothing on this site makes a campaign packet yet, and none has been sold. Family packets pay no fee.
A packet is a reason to get a wallet
Opening a share does not make a wallet by itself. On WhatsApp, someone with no wallet texts “create a wallet” first, then opens the share into it. On a browser call the share goes to the NEAR account the opener names. Red packets are how WeChat Pay got onto phones in 2015. A new phone wallet costs 0.013 NEAR.
Staking packets (next, not built)
A packet that is staked until it is opened: a gift for a birthday three months away earns NEAR staking yield in the meantime, the opener gets the gift plus the yield, and Ringfence keeps a share of the yield. It is designed, and it only changes the packets contract. It is not in this build.
Cash-out and swap fees (later)
A small fee when someone moves their money out to a bank or another chain through NEAR Intents.

Fair questions

Why can anyone try a real wallet here?
Because the limits aren’t ours to bend. The demo wallet is a NEAR contract that caps every send at 1 NEAR and every day at 3 NEAR, so the PIN on this page can’t move more than the contract allows. It holds a small amount. It has two saved recipients: liho00.near and the packets contract. A money packet made from it can pay the account its opener names, so a visitor can move small amounts out through a packet. Approve cards show on the page instead of WhatsApp, and Not me locks only your session, so one visitor can’t block the demo for the rest.
What if you go rogue?
A wallet you own loses at most its daily cap. Saved people get paid at once; anyone else only after the contract’s wait for new recipients, which the owner can cancel. The owner can switch the AI off with one transaction. Two things are trusted to us. A wallet made by text is held by Ringfence until it is claimed. And money inside a packet sits in the packets contract, which Ringfence runs: our agent decides who opens a share, and we can pause the contract or cancel a packet back to its sender.
Can the AI be talked into more?
They can try. The AI has no authority of its own. It asks the contract, and the contract checks the limits and the recipient before anything moves.
Who hears the PIN?
The speech and chat models hear it inside NEAR AI TEEs. It also passes through our app server, which isn’t attested. We store a salted hash and blank it from the transcript. Three wrong tries lock the line for 15 minutes.
Is the voice private?
Partly. The chat, speech-to-text and image models run on NEAR AI Cloud in Intel TDX and NVIDIA confidential GPUs, and /proof checks them live. The spoken voice is made by Cartesia, which is not attested and sees the reply text it speaks. Our app server is not attested either, and on WhatsApp Meta sees the call metadata.
Has it moved real money yet?
Yes, on NEAR mainnet since 10 November 2026: a voice send, a refusal by the contract and a packet share opened by voice, each linked above. The contracts are AI-reviewed, not audited, so amounts stay tiny. An audit comes before higher limits.
Can Mum start with just a phone?
Yes. She texts “create a wallet” on WhatsApp and picks a PIN. It starts custodial: we hold the owner key, with a small balance cap, until the family claims it to their own NEAR wallet.
Can a family DAO own the wallet?
Yes, by design, but the DAO-owned wallet is not on mainnet yet. A Sputnik DAO can create the phone wallet itself, so the DAO is the owner and Ringfence's custody account has no power over it. Raising a limit, saving a new person or switching the AI off then needs a council vote. A family DAO has already funded a money packet on mainnet, and a share was opened on a call: see the packet. Mum still just calls.
Can I use it on WhatsApp?
It is built and supported: a wallet by text, calls, the Approve card and money packets. Our public number +60 11-7512 3486 is waiting on Meta's business verification; once approved, message or call it and it just works, and we will update this page. Until then it runs on Meta's test number +1 555-144-4220, which only answers numbers Meta approved. The browser call does the same things.
Can I top up from another chain?
Yes, and it has run on mainnet: 1 USDT on Solana landed as 0.9996 USDC (README row 16). Say "top up my wallet with 2 dollars of SOL": the agent gets a NEAR Intents 1Click quote and sends you the top-up page. Paste a refund address there, send from your own wallet, and the page follows the swap until it lands; the agent tells you on the call. Without a wallet of your own it goes to the shared demo wallet, and the agent says so first.
What else works on the line?
Checking a balance, NEAR in US dollars, sending USDC (tested in the sandbox only, not yet on mainnet), checking an account before paying it (new or unknown accounts get a warning), what’s trending, and launching a coin on JustHoot, which you sign in your own wallet. English only for now.
Which chains?
NEAR only, for now.

Try a call.

Ask for 0.1 NEAR to liho00.near, give the PIN on the page, and get a NEAR explorer link back. Then ask for 5 NEAR and hear it refused: the wallet contract caps a send at 1 NEAR. Real mainnet, tiny amounts.

Pictures: “1940s N935 telephone exchange” by Rodhullandemu, CC BY-SA 4.0; “WAC telephone switchboard operators” by PhotosNormandie, CC BY-SA 2.0. Type: Battlefin and Geist.

Built withNEARNEAR AI CloudNEAR IntentsJustHootNEARON