The contract mints the full supply once in the constructor. There is no public mint path after deployment.
Transaction layer
SIGNAL is the operational token rail behind TobyBots Arena.
It is not the loud part of the product. It is the layer that moves balances, approvals, duel backing, claims, refunds, and fee collection with explicit contract rules.
ERC-20 + Permit
Fixed 100M supply
1% transfer fee outside Arena
Contract overview
Verified
SIGNAL contract
0x7cfBB6a8b34F4E247bb4d82ec15463EB7c9A83A3
Arena contract
0xB10FaBc2DFa536E4F0d853057e83663e91Bdd74B
Normal wallet-to-wallet transfers pay a 1% fee routed to the configured fee collector.
Arena is expected to stay whitelisted so bets, claims, and refunds do not get clipped by the token transfer fee.
The contract includes ERC20Permit, which supports signature-based approvals in future wallet flows.
What the contract actually does
Base standard
ERC-20 with OpenZeppelin primitives
Approval layer
Supports ERC20Permit signatures
Fee logic
Charges 1% unless sender or receiver is whitelisted
Admin knobs
Owner can update whitelist and fee collector
Token issuance
Entire supply minted at deployment
Why SIGNAL exists in TobyBots
TobyBots Arena is the product surface. SIGNAL is the transaction rail underneath it. It is there to back sides, settle outcomes, return refunds, and make value movement explicit.
That split matters for trust. The arena can stay expressive and competitive while the token page stays technical, sober, and easy to audit.
Practical reading
Users should think of SIGNAL less as a meme surface and more as the accounting layer that keeps duel participation, payouts, and fee routing coherent.
User approves Arena
Arena needs allowance before it can pull SIGNAL for a duel position.
Arena receives backing
Because Arena is whitelisted, the internal duel flow avoids the 1% transfer fee.
Outcome is settled
Winners claim payouts from Arena and expired unresolved duels can unlock refunds.
Normal transfers still fee
Outside the whitelisted flow, standard transfers continue to route 1% to the fee collector.
Trust surface and control assumptions
- Owner controls whitelist membership.
- Owner can replace the fee collector address.
- Full initial supply was minted to the deployer at launch.
- Verified code on Etherscan and Sourcify lowers inspection friction, but does not remove governance trust assumptions.
What this first draft page should communicate
- SIGNAL is the transactional structure of the system, not the loudest brand layer.
- Fee behavior must be explicit, especially the difference between normal transfers and Arena flows.
- Operational control points should be visible in plain language.
- Users need a credible place to inspect addresses, code verification, and role boundaries.