Architecture
Describes the overall technical components. Dev is devving.
Last updated
Describes the overall technical components. Dev is devving.
Last updated
Manages the creation, distribution, and operations associated with the FLAPPY token.
Functions:
mint():
Creates new tokens.
This function is usually reserved for specific circumstances or addresses.
burn():
Destroys a specified amount of tokens, reducing the total supply.
transfer():
Allows token holders to send tokens to other addresses.
approve() and transferFrom():
Enables a third party (like the GameContract) to move a set number of tokens on behalf of a user, facilitating things like staking or in-game purchases.
balanceOf():
Returns the token balance of a specific address.
Manages the flow of ETH funds related to the game, including user deposits, payouts, and bet placements. It ensures the transparent, decentralized, and tamper-proof handling of the gaming economy.
collectDeposits():
Accepts ETH from users who wish to participate in a game round.
Locks the funds until the game round's outcome is decided.
payout():
Calculates the amount of ETH to distribute to the winning parties based on the game's outcome.
Sends the calculated ETH amounts to the respective winners.
triggerPayouts():
Initiates the payout process once the game outcome is decided and validated.
Our Distributed Ledger Intermediary known as Aquato.
Aquato is as an intermediary between the blockchain and the game's frontend. It manages game mechanics, user profiles, and statistics, and acts as a cache for blockchain data to ensure the game runs smoothly without fetching data directly from the blockchain each time.
manageUserProfiles():
Registers new users and stores their basic profile information.
Might include username, game history, total wins, and other game-specific statistics.
serveUserStats():
Retrieves a specific user's game statistics.
Can be used by the FlappyUI to display player rankings, achievements, and other relevant stats.
choosePlayer()
Randomly selects one player from the pool of depositors for the game round.
Assigns all other depositors as observers.
placeBet():
Allows observers to place additional ETH as a bet on the outcome of the game.
validateGameResult()
Accepts the game result from the GameClient.
Verifies the authenticity and correctness of the game's outcome. This could involve checking against certain game rules, time constraints, and maybe even certain anti-cheat mechanisms.
calculatePayouts():
Determines the amount of ETH each participant (player and observers) should receive based on the game's outcome and any placed bets.
triggerPayouts():
Initiates the payout process once the game outcome is decided and validated.
Calculates the amount of ETH to distribute to the winning parties based on the game's outcome.
pullBlockchainData() (implicit function):
Periodically fetches data from the SmartContract. This includes user deposits, bet amounts, and payout history.
This data can be cached to serve frequent requests without interacting directly with the blockchain, thereby saving on gas costs and improving user experience.
pushGameDataToBlockchain() (implicit function):
Sends game data or results that need to be recorded on the blockchain. This might involve creating a transaction.
Reliability and Scalability: Given its pivotal role, the server should be designed for high availability. This might involve distributed architectures, load balancers, and fault tolerance mechanisms.
Security: As an intermediary handling game results and interacting with the blockchain, it's a potential attack target. It's crucial to implement robust security measures, including data validation, DDoS protection, and regular vulnerability assessments.
Latency: Real-time or near-real-time games require low latency. The design should prioritize fast data retrieval and processing.
Data Integrity: The server should have mechanisms to ensure data integrity, especially when pulling from or pushing to the blockchain. Any discrepancies could lead to financial discrepancies given the ETH payouts.
Privacy: User data should be stored and transmitted securely. Ensure GDPR or relevant data protection compliance.
Given the pivotal role of FlappyChainProxy, it's essential to ensure it's designed robustly and securely. Given its interactions with the blockchain and its role in game mechanics, it's the heart of the system.
Our games server known as KlonoArai serves as the central authority for our online games, managing game state, player interactions, facilitating authentication, communication with SmartContract(s) and synchronisation with clients (players and observers). KlonoArai is accountable to an immutable ledger, an intricately designed hash chain data structure engineered to uphold cryptographic security.
Don't stress yourself, don't guess.
KlonoArai employs security measures to prevent cheating, hacking, or unauthorised access to the game. Like really encryption, anti-cheat systems and vOrnitier, an immutable, auditable, and cryptographically secured permanent ledger.
KlonoArai hosts the core gameplay logic, rules and state. This includes managing game mechanics, tracking player scores, positions, events and enforcing rule to ensure fair play.
Individual player devices connect to the gamer server to participate in the game. Each client communicates with the server to send and receive game data, which is then logged to vOrnitier.
KlonoArai plays a critical role in ensuring that all players' actions are synchronised. It receives input from each client, processes it, and then broadcasts the results to all connected clients. This synchronisation ensures that all players experience the same game world and events.
KlonoArai uses real-time communication protocols to minimise latency and provide a responsive gaming experience and maintain fairness.
KlonoArai is being built to handle multiple concurrent connections. As more players and observers join a game, it can scale its resources or use load balancing techniques to distribute the workload across multiple servers.
KlonoArai manages player accounts, and facilitates authentication, and authorisation. It ensures that only authorised players can access the game and that their progress is tracked accurately.
KlonoArai uses a distributed high availability database, data is encrypted at rest and in transit. Every data access is written to vOrnitier.
All communication with SmartContract(s) is done out of bounds.
Chill out, no need to break a sweat, and definitely don't play the guessing game!
