Beatpot smart contract
BeatPot runs entirely on smart contracts deployed on HyperEVM. This page provides technical details for those who want to interact directly with the contracts or verify the code.
Contract Addresses
Key Functions
For Players
purchaseEntries
Purchase raffle tickets for the current round.
Input: Number of entries to purchase, optional referrer address
Cost: 0.1 WHYPE per entry
Requires: WHYPE approval to the contract
For Backers
backerDeposit
Deposit WHYPE into the vault to become a liquidity provider.
Input: Amount of WHYPE to deposit
Returns: BPLPT shares based on current exchange rate
Requires: WHYPE approval to the contract
requestWithdrawal
Request to withdraw your BPLPT shares.
Input: Amount of BPLPT shares to withdraw
Effect: Adds request to withdrawal queue
Note: Withdrawal processes after current round ends
claimWithdrawal
Claim your WHYPE after withdrawal request is processed.
Requires: Previous withdrawal request that has been processed
Returns: WHYPE based on exchange rate at round end
For Referrers
claimReferralFees
Claim accumulated referral rewards.
Returns: WHYPE referral fees to your wallet
Share Token
Name: BeatPot Liquidity Provider Token
Symbol: BPLPT
Type: ERC-20 compatible
Purpose: Represents your share of the backer vault
Verifying the Contract
Reading Contract State
Useful read functions:
getCurrentRound
Current round number and details
getEntries
Your entries for a specific round
exchangeRate
Current WHYPE per BPLPT share
totalBackerDeposits
Total WHYPE in backer vault
Events
The contract emits events for all major actions:
EntryPurchased- When tickets are boughtWinnerSelected- When a winner is chosenPrizeClaimed- When a winner claims their prizeBackerDeposit- When liquidity is addedWithdrawalRequested- When a withdrawal is queuedWithdrawalClaimed- When a withdrawal is completed
Security
The BeatPot contracts:
Are deployed on HyperEVM mainnet
Use Pyth Entropy for verifiable randomness
Implement withdrawal queuing to prevent front-running
Have no admin functions that can steal funds
For developers
If you're building integrations or want to interact programmatically:
Use the contract addresses above
Import the ABI from HyperEVMScan
Ensure WHYPE approval before deposits/purchases
Monitor events for real-time updates
The contracts follow standard Solidity patterns and should be familiar to anyone experienced with DeFi protocols.
Last updated