Attributes
- Author(s):
- Recipient(s): Michael O’Rourke, Jorge Cuesta
- Category: Reimbursement
- Fulfills: Link to other PIPs/PEPs
- Related Installments: Link to other PEPs
- Asking Amount: The equivalent to $75,500 to cover current costs. We will be submitting incremental PEPs for the next milestones.
Summary
POKTscan (poktscan.com) is a platform that provides access to up-to-the-last block Pocket Network data via web, mobile, and API. Data is the first of a number of building blocks that will allow POKTscan to provide analytics, alerting and node management functionality. In later versions we intend to provide predictive analytics functionality for some aspects of the ecosystem.
Abstract
POKTscan intends to be the go-to platform for Pocket Network data analytics and node management. We intend to enrich the Pocket Network data with other data sources and technology to provide analytics and insight into the network performance.
POKTscan uses a parallel database that is always in-sync with Pocket. The database contains historical data dating back to genesis. The database provides full text search capabilities across all entities.
POKTscan transforms all Pocket data into better-organized structures that allow both humans and software easy access and use. During the transformation process, POKTscan filters, aggregates, and summarizes data to create new entities that contain, for example, paid relays at a block and node level, account history, app history, node history, fee history, and transfer history.
POKTscan also enriches the data by adding entities such as node geolocation to provide visibility into node distribution, and node version for consensus information. POKTscan also tracks relay errors using the Pocket gateway data.
POKTscan generates notifications for new blocks, 6hr + daily summaries, close to jail and jailed nodes. These notifications are done through web, email, and Discord integrations, and Discord bots.
POKTscan has also addressed data issues associated with API endpoints as well as correcting missing account state query endpoints.
We intend to provide:
API that will allow for other platforms to connect.
Webhooks and Notification systems such as Discord, Slack, Telegram or any other that we see are usable by the community.
User custom settings, like a list of nodes, accounts or apps to been tracked
Integration with Pocket node validation using Pocket Network tools and Discord bots.
We are targeting the needs of node-runners, investors/potential investors, the DAO, and developer et al.
From an analytics perspective and on the first phase of this project, we intend to provide comparison functionality that will analyze chain profitability, node profitability, and node-runner profitability comparisons. We intend to provide query and data download capabilities.
Motivation
We believe that the Pocket Network data aggregated and combined with other sources can be invaluable to Pocket Network stakeholders. We are enthusiastic about the possibilities and impact we can have on this and other ecosystems. We currently have a one year technology roadmap which we will use to create our three year plan by the end of 2021.
Needs Being Met
Simple access to data, data analytics, via web, mobile, api.
Budget
We have two full time resources working on POKTscan since July 2021, with part-time work starting in Jun 2021.
For phase I of this project and through October we have spent $51,500 in labor and $2000 hardware for a total of $53,500. Since the time we started working on this PEP we have burned $11.5K. Based on community suggestion, we would like to include a UX designer for two months. This will have a cost of $10K. The total ask for this phase is $75K .
We will be submitting additional incremental PEP’s for every mayor milestone.
Our burn rate is $12,500 per month. We will spend $100,000 between November 2021 and June 2022. The total expected twelve month spend is $153,500.
Rationale
We believe that two full time resources will be enough to complete this project. We also have contributors that offer their time for free.
Dissenting Opinions
TBD.
Deliverable(s)
Phase I will be available to the community on November 15.
Phase II on December 15 that will contain an external API.
Phase III on March 15 2022 will contain mobile and notifications.
Phase IV is still being planned but has a target date of Jun 15 2022.
Contributor(s)
Jorge Cuesta is a senior software architect and developer.
Michael O’Rourke is a 30 year software veteran and investor.
Both will take the lead in driving and delivering this project.
Copyright
Copyright and related rights waived via CC0.