@agruzdev.near [Posted on DevHub](/devgovgigs.near/widget/Post?id=3078) ## Solution: SourceScan - Final Steps ###### Requested amount: 11000 USDT ###### Requested sponsor: @neardevdao.near ## Previous proposals and background *1st proposal (initial scope):* https://near.org/devgovgigs.near/widget/gigs-board.pages.Post?id=853 *2nd proposal (finished):* https://near.org/devgovgigs.near/widget/gigs-board.pages.Post?id=1565 ## Problem Upon the successful completion of the preceding roadmap, SourceScan is now equipped to validate smart contracts through two distinct methodologies: one involves sharing a full-access key, and the other does not require such sharing. The ultimate objective is to streamline the verification process for users, allowing them to undertake this task without directly interacting with SourceScan. This will be achieved by integrating the functionality into cargo-near. There is an ongoing [integration process](https://github.com/near/cargo-near/issues/131), thereby positioning cargo-near as the central platform for an optimal NEAR smart contract development experience. Furthermore, by adopting the [(updated) NEP-330](https://github.com/near/NEPs/pull/533), it would be possible to push the development experience even further, as SourceScan would fetch the contract information from the build details of contract metadata and reproduce the same WASM code to verify the contract. ## Solution - Multiple builder images support on the back-end - API security and resilience improvements - Scalable architecture - Load-balancing - BOS Components refactoring for "Contracts Table" and "Contract Info" - Finish the cargo-near integration - Adopt new NEP-330 standard Building upon the aforementioned advantages of smart contract verification, this proposal places a strong emphasis on enhancing the developer experience and promoting standardization. ## Looking for support in 1. Financial support to realize the final vision for smart contract verification on NEAR ## Budget & Financing We are requesting 11000 for 1 month 1. Compilation server hosting, load-balancers and other dev-tools: 1000$ / mo 2. DevOps: 4000$ / mo 3. Lead (full-stack): 6000$ / mo ## Milestones ## 0 - Proof of Concept - (June - July) - **(✓)June**: 1. (✓) First MVP developed 2. (✓) Mainnet integration - **(✓) July** 1. (✓) Acess Keys managment 2. (✓) BOS components for contracts lookup 3. (✓) Integration of multiple NEAR wallets ## 1 - BOS Integration - (August - October) - **August**: 1. (✓) Github integration for source code upload 2. (✓) BOS components for contracts compilation & deployment ## 2 - Verification v2.0 - (November - January) - **November** 1. (✓) First stage implemented - **December** 1. (✓) Second stage implemented - **January** 1. (✓) Contract social features - **Additional (finished)** 1. (✓) NEP ## 3 - (February) - Initiate cargo-near integration (✓) - Update NEP-330 (✓) ## 4 - Final Steps (Current proposal) - (March) - Multiple builder images support on the back-end - API security and resilience improvements - BOS Components refactoring - Finish the cargo-near integration - Adopt new NEP-330 standard - Nearblocks integration (?)