# Blockchain and Contract ## Cronos Blockchain \ We chose Cronos as the blockchain for Capybara Nation due to its robust ecosystem and strong integration with Crypto.com, which boasts millions of users globally. This strategic alignment offers seamless entry points for users through Crypto.com’s vertical services, making the transition between Web2 and Web3 easier for new and seasoned players alike. The combination of easy-to-use DeFi services and built-in wallet support simplifies the onboarding process for players. Our decision to build on Cronos was driven by its scalability, low transaction fees, and rapid community expansion. These features perfectly align with our vision to onboard millions of Web2 users into the Web3 space while providing a smooth, lag-free experience for gaming. With more than 80 million people worldwide, we aim to leverage Cronos' growing ecosystem, to create an immersive and rewarding experience. Additionally, Cronos’ multi-chain support opens opportunities for future expansions and integrations, allowing Capybara Nation to connect with other blockchain ecosystems. This choice enables us to prioritize scalability, security, and a seamless gaming experience, positioning Capybara Nation as a leader in the Web3 gaming space. At launch Capybara Nation will go live on Cronos EVM, but we’re not stopping there! Our sights are set on expanding to Cronos zkEVM in the near future, unlocking even greater possibilities for our holders! ### Smart Contracts (Cronos EVM) $BARA token contract: `0xF24409D155965ca87c45aD5BC084aD8aD3Be4f39`\ Staking vault smart contract: `0xe4960C2cB3B5edDf32A712DbA733Ef784571CfAb` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://capybara-nation.gitbook.io/capybara-nation/usdbara/blockchain-and-contract.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.