Skip to content

Devlog 2023 02 21

Jump to bottom
user_name edited this page Mar 28, 2023 · 1 revision

Pocket V1 DevLog Call #3 Notes

Agenda

Current Iteration 🗓️

  • Duration: February 8 - 21st 2023
  • Backlog

Iteration Goals 🎯

  • M1: PoS
    • Complete MVP and continue full peer discovery development with LibP2P integration
    • Finalize state entry points for state machine (syncing, synched, etc.)
  • M2: DoS
    • Deploy localnet in a remote environment
  • M3: RoS
    • Continue Utility module foundations

Iteration Results ✅

External Contributions ⭐

Upcoming Iteration 🗓️

Feedback and Open Discussion 💡

Feedback and Discussion Form

Q: How is our approach to development different than how others are doing it? Are we staying ahead of the curve? How do we think about our work and how we prioritize it to make sure we are pioneering RPC?

A: On the product side for us it's really important for us to always stay in sync with our sales and marketing team. What are users saying? What is the data saying? We try to stay on top of narratives and market trends. Although our roadmap is well defined currently, there are unanswered questions in the specification that we can incorporate more timely market insights into. Peer Discovery with LibP2P is a great example of this. Choosing the right algorithm to work with Raintree was not a trivial decision and happened over 6+ months of discovery across 7+ developers. Additionally, since the team is so close to RPC and has deep experience in the space, you see more proprietary inventions in V1 than you'll see in other projects. From a more technical standpoint, the goal with V1 is building an application specific blockchain for an application specific purpose. We have had many sleepless nights thinking about this decision. We see competitors using Tendermint or building modular blockchains. We have decided to build our own L1 to keep optionality, functionality, and build it in a very developer friendly way. Since encouraging others to build on Pocket Network is a core value, that guides a lot of how we approach building.

Q: What is IBC and where is it integrated with the protocol?

A: Think of IBC as TCP (networking transport layer in web2) of blockchain to enable requests and responses between different blockchains with custom consensus mechanisms. By conforming a specification on how to transport requests enables several features that allow for cross-chain communication and security. IBC should not touch utility but should live in persistence (exposing state commitments) and consensus (light clients). However, if we get into more complex integrations we may start touching utility but not in the initial integration. TBD if IBC requires a dedicated module.

Contribute to V1 🧑‍💻

V1 is an open source project that is open to external contributors. Find information about onboarding to the project, browse available bounties, or look for open issues in the linked resources below. For any questions about contributing, contact @jessicadaugherty

About Pocket Network 💙

Pocket Network is a blockchain data platform, built for applications, that uses cost-efficient economics to coordinate and distribute data at scale.

Contents

Clone this wiki locally