NEAR hackathon demo
You set the spending limits.
You run a one-person travel business. A helper can ask to pay a hotel, an airline, or a ride. You choose the spending limit, who can be paid, and when it must ask you first. The helper can ask. It cannot send the money.
In this demo, who can be paid: hotel.near, airline.near, rides.near.
Open the desk and press Run. In under a minute you will see yes, ask you, and no — including a fake look-alike name, and too many rides in one day.
This demo checks the rules and does not send money. There is no fake payment record. Freeze stops the desk in the demo. It does not pause the blockchain.
Three answers
Yes
Inside your spending limit, and the name is someone you can pay. Not sent yet.
Ask you
Over the line you set. Nothing moves until you say yes.
No
Over the limit, or a name you did not allow. A fake look-alike is a no.
Watch the travel desk
About a minute and a half. Spending limits for a hotel, an airline, and rides. The demo says yes under your limit, asks you once, and says no to a fake look-alike name and to too many rides. Then Freeze stops the desk. The helper can ask. It cannot send the money. This recording does not send money.
Prefer a direct link? Open the travel demo
Who it is for
People running a small business on their own. A helper does the busywork and sometimes needs to pay someone. You want that to move quickly, under the limit you set. You keep the say-so.
The problem
If the helper can send your money, a clever message can talk it into paying the wrong person. A rule typed into a chat is only a request. It can be ignored. Mandate keeps the lock outside the helper.
Who, the problem, and the lock
About a minute. Who it is for, why a chat rule is not a lock, then spending limits and who can be paid — kept outside the helper. The helper can ask. It cannot send the money. This recording does not send money.
Prefer a direct link? Open the who and problem video