Your chosen reward amount
The rest of the wallet balance and all staked principal remain outside the round.
Notch connects two actions: stake to earn supported stock-token rewards, then keep those rewards or use a chosen amount in a verified double-or-nothing round.
Users approve the staking token once, choose an amount, and call stake. The contract records the amount actually received, so fee-on-transfer behavior cannot inflate a position.
Tracked stake is reserved by the contract and cannot be recovered through the excess-token admin function.
Authorized distributors fund supported RWA reward tokens. The configured staker share is distributed pro rata using accumulated reward-per-share accounting. The current launch setting directs 30% to stakers and can be changed by the configuration role for future funding rounds.
staker reward = funded amount × configured staker share
user reward = staker reward × user stake / total stakeChanging the share does not rewrite rewards already accrued. Rounding dust stays reserved until it can be distributed or claimed.
Flipping is optional. A player chooses heads or tails and wagers an enabled reward token within its configured limits. The contract transfers only that wager and locks enough bankroll for the maximum 2× payout before requesting randomness.
The rest of the wallet balance and all staked principal remain outside the round.
A win creates a claimable balance. A loss closes the round without touching other rewards.
Each round requests randomness through the configured Quiver coordinator and provider. Only the coordinator callback can settle a pending bet. The result bit maps to heads or tails, and duplicate callbacks cannot settle a round twice.
Available bankroll excludes locked payouts and all existing claims.
Configuration, pausing, and reward distribution use explicit access-control roles.
Pausing blocks new risk while unstaking and claims remain available.
Every token-moving user and operator path is guarded.
The build is prepared for Robinhood Chain mainnet and testnet. Final deployment needs the token contract address, developer wallet address, and deployer key supplied through local environment variables.
NOTCH_TOKEN_ADDRESS=0x...
DEV_WALLET=0x...
DEPLOYER_PRIVATE_KEY=0x...