@nearblocks.near [Posted on DevHub](/devgovgigs.near/widget/Post?id=2804) ## Solution: Milestone #3 (6-9 months) - Transition Pagoda’s Near Explorer to NearBlocks ###### Requested amount: 75000 USDT ###### Requested sponsor: @neardevdao.near Hello Devhub, We have been able to make good progress on milestone #2. The bulk of the work has been focused on getting Nearblocks on BOS, validator explorer and improving our architecture. The beta version of Nearblocks on BOS can be found here https://beta.nearblocks.io/ As a reminder : * Milestone #1 can be [found here](https://near.social/devgovgigs.near/widget/gigs-board.pages.Post?id=635) ; * Milestone #2 can be [found here](https://near.social/devgovgigs.near/widget/gigs-board.pages.Post?id=2042). ## Highlights of milestone #1 (month 0-3) * Launch of the explorer selector on BOS ([link](https://explorer.near.org/)). * Nearblocks is now open-source ([link](https://github.com/Nearblocks/nearblocks/)). * As well as fixing outdated bugs, re-indexing missing tokens and infrastructure upgrades. Our public roadmap for milestone #1 can be [found here](https://github.com/orgs/Nearblocks/projects/2/views/2?filterQuery=iteration%3A%22Iteration+1%22+). ## Highlights of milestone #2 (month 3-6) The bulk of the work within these 3 months has been on BOS and our new infrastructure. The rewrite on BOS and updated indexer we have coded V3 - which we aim to publish by the end of January / early February 2024. Following the incident caused by the NEAT inscription our focus shifted to our infrastructure. The incident highlighted a bottleneck issue, which we were able to fix and sustain subsequent inscriptions without any impact to the site availability. Our V3 infrastructure has been focused on building a full high availability design with disaster recovery backup in place. With this new infrastructure in place we are able to tolerate 1 location to be unavailable, at any point in time and continue to operate without any interruption to the end user experience. Our focus for this milestone has been on failover testing and ensuring our code can withstand outages while maintaining the data integrity required of being the near block explorer. For some context, our total in use storage sits at 50TB (inclusive of replicas and disaster recovery). The increased investment in our infrastructure cost we believe is critical to maintain the uptime of Nearblocks. We will continue to focus on this high availability, our plans will be to have a gateway and BOS selector on Nearblocks, so users can select between: * Nearblocks on BOS Mainnet * Nearblocks on BOS Testnet * Legacy React app (which will receive only minor updates). The following points are completed and will be published in V3: * **Remaining actions from milestone #1 :** Can be [seen here](https://github.com/orgs/Nearblocks/projects/2/views/2?filterQuery=iteration%3A%22Iteration+1%22+) in “Done” ; * **Updated indexer:** Running on mainnet and testnet ([link](https://beta.nearblocks.io/)) ; * **BOS** : Publication of BOS components ([link](https://near.social/devhub.near/widget/app?page=profile&accountId=nearblocks.near) or search for nearblocks.near [here](https://near.social/lord1.near/widget/component-total)) ; * **Validators** : Validator section in review ([link](https://beta.nearblocks.io/node-explorer)) ; * **Tokens** : Additional legacy tokens added ([link](https://github.com/Nearblocks/nearblocks/issues/15)); * **Ads** : As per request from the ecosystem, we have prepared an ad network for NEAR projects to advertise on Nearblocks. While we know that no one likes ads, the ad revenue will go towards covering the ongoing increased infrastructure costs, and we hope also support Near ecosystem players ; * **Contracts** : Connect methods updated to use MNW. Wallet selector will be added to BOS version. We are currently working the following points on V3: Tokens : * Add SBT token support - Postponed until finalised ([link](https://github.com/near/NEPs/pull/504)) * Transaction execution enhancements Our public roadmap for milestone #2 can be [found here](https://github.com/orgs/Nearblocks/projects/2/views/2). We are continuing our attempts to support the ecosystem where best we can, with a number of ongoing requests for additional API data endpoints being worked on for multiple use cases such as taxation, validator stats and wallet support. ## Milestone #3 goals (month 6-9) The main features we will be focusing on in this milestone will be focused around contract integration and timeseries data representation. * cargo-near integration (with embedded ABI) * Contract stats (ie. active users, interactions) * Contract tools like verification, search and comparison * User/Address level analytics: Near Balance, Token Balance, Transactions, Fees etc * More integration with near social (comments, announcements) * Wallet selector integration (login, contract methods) * SBT token support * Additional API endpoints for API clients Some time will also be spent on improving insights into DEX activities (trades, liquidity, chartings) on NEAR as well as research into tighter integration with Aurora. Our public roadmap for milestone #3 can be [found here](https://github.com/orgs/Nearblocks/projects/2/views/2?filterQuery=iteration%3A%22Iteration+3%22+).