Add contract service layer and API integration#32
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added a new Web3-based contract service layer that initializes the AgonusBetting contract from settings (RPC URL, contract address, admin key, ABI, chain ID) and exposes admin write operations (create_tournament_on_contract, close_betting, settle_tournament, cancel_tournament) plus read-only helpers (get_tournament_state, get_agent_pool, get_agent_odds), all using a shared helper for nonce, gas estimation, signing, transaction submission, and receipt checking. Updated the Tournament model and schemas to store the on-chain tournament ID, per-agent contract index mapping, and contract status, and rewired the tournaments API routes so POST /tournaments creates both the DB record and on-chain tournament, while the new /tournaments/{id}/settle and /tournaments/{id}/cancel endpoints drive settlement and cancellation on the contract and then sync winner and status back into the database, with require_admin protecting all admin-only endpoints and .env-based configuration (including a local SQLite DATABASE_URL and dummy but valid contract credentials) so the app can be run and tested safely in development.