GUEST CHECK · BOT CHAIN 677
No. —
Blank pad. Open a tab or look one up.
- Host
- —
- Your chips
- 0 BOT
- On the check
- 0 BOT
- State
- pending contract
thank you · pull out before settle
Open Check
Open Check
GUEST CHECK · BOT CHAIN 677
No. —
Blank pad. Open a tab or look one up.
thank you · pull out before settle
A group chat settles nothing. Someone fronts the bill, screenshots get buried, and the person who owes twelve dollars becomes a memory. An open check puts the line items on one page: a numbered tab, a running total, and a stub that shows who chipped and how much is still owed.
Open Check keeps the money in the contract, not in the host's wallet. Each chip is recorded against the sender, so pulling out only ever returns your own remaining amount. The host cannot drain other people's chips, and there is no third-party address that collects the total. When the host settles, the remaining balance pays the host directly; when the host cancels, each person pulls their own chips back.
It goes to the OpenCheck contract on BOT Chain mainnet, chainId 677, and is recorded against the check number and your address. It does not go to the host's wallet until the host settles.
Yes, while the check is not settled. Call pullOut and the contract returns your own remaining amount to you. After the host cancels, pullOut still works for everyone who chipped.
Settle is host-only. Whatever is still on the check at that moment pays the host, and pullOut closes for that check. Chip in only what you intend to leave on the tab.
No. The host has no withdraw function for other people's chips; the only host actions are settle and cancel. Pulling out is yours alone and only returns your own remaining amount.
No fee. chipIn and a seeded openTab must send more than 0 BOT to record a chip; openTab can be 0 if the host only wants a blank check. The memo is optional and capped at 80 characters.
BOT Chain mainnet, chainId 677, with native BOT as the only asset. The contract is OpenCheck, pending deploy; the explorer at scan.botchain.ai will show the address once it is live.
Anyone who has ever split a bill and lost track of who paid. The host who fronts the card and then chases six people for a week. The friend who always chips in late and wants a clean record of it.
It fits small, real tabs: a dinner where one person covers the card and the table chips in BOT, a group gift with a fixed target and a memo naming the occasion, a shared ride or a house bill that one person pays and the rest top up, and a trip fund where the host holds the check until the last person settles. No accounts, no invoices, no chasing.
OpenCheck is pending deploy on BOT Chain mainnet; the five actions — openTab, chipIn, pullOut, settle, cancel — are the whole surface.
Publish the deployed contract address and a check-number lookup so a guest can find a tab from the memo alone.
Add a read-only view that lists every chip on a check with its sender and amount, so the table can see the stub before settling.
Keep the contract small and the exit path unchanged: chips stay pullable until settle, and the host is the only address that receives the remaining total.
Open a tab, let the table chip in native BOT, and pull your own chips back while the check is still open. When the host settles, the remaining total pays the host and the pad closes.
Back to the pad