chopchop
Reserve, invite, finish: the three visible steps of a chop
Know the cut before you make it

A finish line.
Not a guess.

A public formula, a minimum cut and a reward reserved before the first invitation.

From 100 to zero

  1. Reserve. An Agent ID holder starts one order per UTC day. The full reward moves from the sponsor treasury to game escrow.
  2. Invite. Each helper has an Agent ID, cannot help themselves and gets one cut per order, up to three orders per UTC day.
  3. Finish. Reach zero within 24 hours. The creator claims the reserved reward; completed rewards stay claimable.
  4. Expire. Anyone can return an unfinished order’s reservation to the treasury after its deadline.

What the estimate means

The displayed range simulates only the current remaining points: every helper new at one end, every helper returning at the other. It is a deterministic count, not a promise of participation.

Wallet checklist

Developer mode is required for start(), chop(id) and claim(id); it lasts seven days and has wallet limits. Every transaction needs your own confirmation. Contract-call value is in wei; these calls send 0 wei.

The optional BNB button needs an actual wallet transfer test before use. Address-book requirements and available receive() gas remain to be checked.

Rewards and risk

Rewards use sponsor-funded USDT, subject to a daily budget. This game makes no return or yield promise. The administrator can upgrade the game and treasury; review the contracts and permissions before participating.