{"signature": "0xae30ff945348395715bb705084e21073bc39b8c958e4b880f03daf86aa8db9f4363e4b0220ba00c0eeb23bcfd8e60cd379041a636e9a3e7ce032f069a456174f1b", "application": {"round": "0x4a1099abd28338a952baf5e7387b1eb22c15a234", "answers": [{"type": "short-answer", "answer": "Reecepbcups", "hidden": true, "question": "Telegram Handle for Contact", "questionId": 0}, {"type": "link", "answer": "https://t.me/+Gb4HTaH6FRwxY2Vh", "hidden": false, "question": "Public Group Chat Link", "questionId": 1}, {"type": "paragraph", "answer": "Central bank of brazil CBDC: https://github.com/Reecepbcups/cbb-cbdc-demo\n\nothers: wip pending cbb's impl", "hidden": false, "question": "List the active Sei dApps/projects currently using your infrastructure or tooling (minimum three required). Provide integration proof.", "questionId": 2}, {"type": "paragraph", "answer": "It's open core not open source. Direct metrics are not available at this time. ", "hidden": true, "question": "Share specific metrics demonstrating developer adoption (GitHub activity, API usage, package downloads, etc.). Acceptable metrics include: GitHub activity: Contributors, stars, forks, pull requests, or issues. API usage: Volume of API calls, unique users (e.g., IPs or authenticated accounts), or endpoint performance data. Package adoption: Downloads from registries (e.g., npm, Docker Hub) or integration into ecosystem tools. Community engagement: Testimonials, forum activity, or developer endorsements.", "questionId": 3}, {"type": "paragraph", "answer": "Everything sei has provided, just now for others to also use on the latest and most secure version of the cosmos-sdk. ", "hidden": true, "question": "Quantify your tool's impact on the Sei ecosystem (e.g., performance improvements, cost reductions, throughput increases).", "questionId": 4}, {"type": "paragraph", "answer": "https://github.com/rollchains/cosmos-evm/pull/1\n\nhttps://github.com/Reecepbcups/cbb-cbdc-demo", "hidden": true, "question": "Provide links to your public documentation and evidence of successful third-party integrations.", "questionId": 5}, {"type": "paragraph", "answer": "Jul 18, 2024 was my last commit to the cosmos-evm PR #1, the CBB repo is from 2 months ago with accompanying video", "hidden": true, "question": "When did your tool/infrastructure go live on Sei, and what metrics demonstrate continuous operation for at least 30 days?", "questionId": 6}, {"type": "paragraph", "answer": "Our CBDC integration framework demonstrated to the Central Bank of Brazil has established a foundation for institutional adoption of Sei's EVM implementation. This initiative bridges traditional finance with blockchain technology through:\n\n- Development of compliant token standards for central bank issuance\n- Implementation of privacy-preserving transaction mechanisms via Penumbra integration\n- Creation of regulatory reporting and control mechanisms", "hidden": true, "question": "Highlight 1-3 key initiatives your team believes have had the most significant impact on the Sei ecosystem and that you’d like voters to consider. Include relevant metrics, links, or supporting data to provide an informed view of how your efforts have contributed to the ecosystem’s growth. ", "questionId": 7}, {"type": "checkbox", "answer": ["Yes"], "hidden": true, "question": "Please confirm that you have read and agree to comply with the ethical standards outlined in the eligibility criteria.", "questionId": 8}, {"type": "paragraph", "answer": "Also exploring this solution for Ondo Finance's network, bringing stocks on chain. I was recommended by a current sei team member to submit my work here for cosmos-evm.", "hidden": true, "question": "Is there anything else you'd like to share about your project that may help determine eligibility?", "questionId": 9}], "project": {"id": "0x538f6288a508bf2cb983e2286fe0b6084c9167ee9d81bc1190ff07d60264a9e0", "title": "cosmos-evm", "metaPtr": {"pointer": "bafkreidev5znep6zlbjgbd4cb3deffacm23p2zjdmkuutq6h4os7wxwsny", "protocol": "undefined"}, "website": "https://github.com/rollchains/cosmos-evm/pull/1", "createdAt": 1740090867865, "userGithub": "Reecepbcups", "credentials": {}, "description": "\n## Overview\n\nCosmos-EVM is a groundbreaking fork of the Sei EVM implementation, leveraging the Cosmos SDK and CometBFT consensus engine to extend EVM compatibility across Cosmos-based networks. This project adapts Sei V2's EVM implementation to create a standardized approach for introducing Ethereum Virtual Machine support to any Cosmos chain. Used to power central backed digital currencies and other cosmos + evm compatible infra.\n\n## Core Features\n\n- Cosmos-SDK v50\n\n- Cross VM Compatibility (Wasm <> EVM)\n\n- Enhanced Wallet Integration with native CoinType 60 Metamask support (no need for associated accounts like Sei requires on mainnet due to 118 CT)\n\n- Bank Module Integration\n\n- Advanced Precompile Support\n\n## Technical Architecture\n\nThe system is built on three main components:\n\n- Cosmos SDK v50 integration with vote extensions support\n\n- CometBFT consensus engine modification for EVM compatibility\n\n- Sei's EVM layer and core infra\n\n## Use Case: Brazil's CBDC Implementation\n\nThe project has garnered significant attention from central banks, including the Central Bank of Brazil, for its potential in CBDC implementation. Others include South Korea, India, Singapore, UAE, and a few others. A demo using can be found here: https://github.com/Reecepbcups/cbb-cbdc-demo\n\nKey features enabling CBDC deployment include:\n\n- Secure token issuance and management through EVM smart contracts\n\n- Integration with existing financial infrastructure via Cosmos SDK (IBC v8)\n\n- Privacy-preserving transaction capabilities through Penumbra integration\n\n- Cross-chain settlement with atomic guarantees\n\n- Regulatory compliance features built into the protocol level\n\nThis implementation provides several significant advantages:\n\n- Unified development experience across Cosmos and Ethereum ecosystems\n\n- Reduced barrier to entry for EVM developers in the Cosmos ecosystem\n\n- Enhanced interoperability between privacy-focused and public chains\n\n- Streamlined CBDC implementation pathway for central banks\n\n- Improved cross-chain asset management capabilities", "lastUpdated": 0, "projectTwitter": "reecepbcups_"}, "recipient": "0xD2C392084761cb6E44c544B6f39dcc001fDe9775"}}