@agruzdev.near [Posted on DevHub](https://near.social/#/devgovgigs.near/widget/Post?id=853) ## Solution: Smart Contract Source Code Verificator and Explorer ###### Requested amount: 70000 USD ###### Requested sponsor: @neardevgov.near **Problem** The NEAR ecosystem is missing one of the most important features/tools around smart contract source code due to WASM related challenges. The inability to verify and view the exact deployed source code leads to: - Poor interoperability between contracts (unoptimized code, difficulties in choosing between seemingly same purpose contracts from different teams) - Much higher security risks for projects and users - Black-box effect for developers and ecosystem participants - Need to "trust" the team's code in a "trustless" environment - Lack of adoption from wider web3 users (especially from EVM-natives) - Inability to audit the exact deployed codebase and upgrades on that address - Slowed down development (code insights, ideas sharing, best practices) - Siloed user and development experience **Simple example of experience with widely adopted chains:** Want to interact with a specific contract to develop based-off it, integrate with it, or just as simple as to buy an NFT or call any other function. Seeing the verified source code - understanding it or simply using ChatGPT if not as technical for high-level explanation. Everything looks OK, safe to use or nicely optimized code for integrating into our product. **NEAR example:** NEAR has superior tech, let's try it. New incoming user or developer (or even OG). Looking for a smart contract of a product example on-chain, found it, only method names? What is inside of this function? Is this contract optimized to build on top of it? What the heck is going on with this function? Is it safe to call it at all? - most web3 natives will probably be discouraged and call it quits. So, the source code verification at the exact deployed address can promote: - Faster smart contract development - More robust and secure ecosystem - Optimization collaboration - New solutions development - Next level of interoperability - Quicker and user-friendlier adoption of the blockchain ## Solution The solution is specific for NEAR (check it out at [https://sourcescan.2bb.dev](https://sourcescan.2bb.dev)). We developed the solution before proposing it, to make sure we are certain in our tech and already: - Solved the challenge of the wasm-code reproducibility - Single-source deployer, verifier, and storage for NEAR ecosystem smart contracts - Now anyone can deploy AND verify actual smart contract source code on-chain - Already supports TypeScript and Rust contracts compilation AND verification - Fully decentralized - Backwards compatibility! (current contracts can verify their existing code through an upgrade without migrating) - Contract updates tracking for additionally deployed code ## What's next and opportunities - Full BOS integration and componentization - REST API for NEAR block explorers - Possible IDE (like Remix) - Developments of better UI/UX - Possible switch from IPFS to NEAR native storage - Building robust infrastructure to improve compilation speed and amount of concurrent compilations ## Looking for support in 1. Financial support ($70,000) for infrastructure (load balancers and high-end servers with high RAM, storage, and enough computing power to handle compilations and storage of files in IPFS), improvements, and operations. This includes hiring a business developer, DevOps engineer, and rust developer to accelerate the release of all features over the next 6-months. 2. Social support to educate the technical audience about the new development on NEAR (attract developers). Make the web3 audience aware of SourceScan (now everyone can see verified contracts!). Spread the word among current NEAR developers and partners. 3. Possible high-level tech consultancy on better BOS integration or migration from IPFS, introductions to current block explorers. ## Milestones/Roadmap (tentative) - August: Finished testing and full mainnet integration, integration of multiple NEAR wallets - September: Infrastructure scaling and redundancies, componentization of major features - October: Full BOS integration and componentization of major features - November: Integration with existing block explorers and any interested parties - December: Final version of UI/UX, release of IDE - January and after: Final main version, self-sustainable product with minimum technical maintenance. Current team (located in Malta), plans to hire contributors from the US: - Lead engineer with Bachelors in Computer Science, work experience as a senior .NET developer in Dubai, Software Engineer. Winner of the 2023 Harvard Blockchain X EasyA Hackathon on Axelar track, Winner of the 2023 "Best Primitives or Infra" by Filecoin during ETHGlobal Scaling Ethereum.