Skip to content

Devlog 2023 02 07

Jump to bottom
user_name edited this page Mar 28, 2023 · 2 revisions

Pocket V1 DevLog Call #2 Notes

Agenda

Current Iteration 🗓️

  • Duration: January 25 - February 7
  • Backlog

Iteration Goals 🎯

  • M1: PoS
    • Cont. developing a simple peer discovery mechanism for localnet
    • Begin full peer discovery development with LibP2P integration
    • Finalize the server to advertise block and identify state entrypoints
  • M2: DoS
    • Merge K8 Localnet and Applied Logging Module
  • M3: RoS
    • Address utility foundation issues to unblock M3 implementation

Iteration Results ✅

External Contributions ⭐

Demo 💻

  • Deploy a V1 Localnet using K8s
  • Present infrastructure that can be used to deploy remote clusters
  • Demonstrate tooling that can be used to scale a cluster
  • Demo a mature logging framework integrated with Grafana

Try it out ➡️ Demo Guide

Upcoming Iteration 🗓️

Feedback and Open Discussion 💡

Feedback and Discussion Form

Q: Can Localnet scale to 999 validators?

A: Containers will be created but the validators will not be participating in consensus until peer discovery is in place and those validators are staked it will be a 4 node network with many unstaked validators. So, technically, yes, but good luck with the resource consumption :)

Q: Were there other projects that inspired how to design the testing and deployment suite?

A: A lot of learning from V0 and a commitment to visibility that won't only allow us to iterate faster but all contributors (reduce dependencies on the core team to make changes to the protocol). We looked at a lot of different projects when we started but most projects don't have these tools in place. In general the Tendermint and Cosmos ecosystem is going that direction, but it's more difficult because they are dealing with legacy code rather than the greenfield of V1. One of the best projects heading this direction is Aptos. They have very mature infrastructure and test suite.

Q: Other projects, like Cosmos, allow people to configure different backends for key storage. Is it worth surveying the community to see what backends the keybase should integrate with (e.g. Leveldb or Pass)?

A: The Keybase currently users badger.db to store locally in the file system. When it comes to key management, enabling anyone to integrate their own key manager into the codebase and identifying maybe one major integration. Please keep in mind that this is not useful for localnet but will be useful once we have a remote deployment.

Q: In V0, the Private Key is a plain text in the server but not in the Keybase. In V1, is this all inside of the Keybase or will there be plain text PKs?

A: The Keybase contains all the PK pairs associated with wallets only. Storing in the same way as V0 (base64) to allow for complete interoperability.

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