Tickpay

Every second, paid. Payroll by the second in USDT or BOT. Stream to one wallet or up to 50 in one transaction; either side can cancel fairly.

Status: contracts are tested on a BOT Chain mainnet fork; the mainnet deployment is pending.

• Website and app: https://tickpaybot.vercel.app (app at /app/)
• Network: BOT Chain mainnet, chain ID 677 · BOT Chain · BOTScan

How it works

1. Start a stream or a payroll. Pick one recipient, or paste up to 50 wallets with amounts, choose USDT or BOT and a duration, then deposit once.
2. Earn every second. The recipient's balance grows each second and can be withdrawn any time.
3. Cancel fairly. Either side can stop the stream. Earned funds go to the recipient; the rest returns to the sender.

Features

• Batch payroll. Pay a whole team in one transaction: up to 50 streams sharing one token and schedule.
• USDT or BOT. Stream stable USDT salaries or native BOT on BOT Chain.
• Fair cancellation. Settlement is exact to the second, in the same transaction.
• Scheduled starts. Fund next month's payroll today; nothing accrues before the start time.

Contracts

Contract	BOT Chain mainnet
Tickpay	Pending mainnet deployment

BOT Chain infrastructure used: USDT 0xaBabc7Ddc03e501d190C676BF3d92ef0e6e87a3C, WBOT 0xD5452816194a3784dBa983426cCe7c122F4abd30, BDEX router 0x07032d47A1b9f8460cBeE9dC17c1d3E438693929, BDEX QuoterV2 0x034A705b36067cff99ABf5C662Be881cBd8d0176.

Source: contracts/src. Tests: contracts/test. The contracts are unaudited; use small amounts.

Develop

Requires Node 20+, Foundry and Python 3.

git clone --recursive https://github.com/David-glitc/tickpay.git
cd tickpay
npm ci
npm test              # forge test
npm run build         # landing page + app into dist/tickpay
npm run preview       # http://127.0.0.1:8771

npm run build writes dist/tickpay/index.html (landing page), dist/tickpay/app/ (the dApp) and a Cloudflare Workers bundle under sites/.

Wallets

The app discovers installed wallets with EIP-6963 (BO Wallet, MetaMask, OKX, Rabby and others) and falls back to window.ethereum. It switches or adds BOT Chain (chain ID 0x2a5, RPC https://rpc.botchain.ai) before any transaction, and simulates every call before asking for a signature.

Rehearse on a mainnet fork

anvil --fork-url https://rpc.botchain.ai --port 8677 --chain-id 677
export BOT_RPC_URL=http://127.0.0.1:8677
node scripts/deploy.mjs && node scripts/fork-check.mjs

Deploy

scripts/deploy.mjs reads the deployer key from BOT_SIGNER_FILE (default ~/.config/botchain-wave1/deployer.env, never committed), refuses to broadcast on mainnet without BOT_MAX_GAS_BOT, and journals every transaction to deployments/mainnet.json so it can resume. npm run publish deploys the built site to Vercel as a static production deployment.

License

MIT. Built on BOT Chain.