-
Notifications
You must be signed in to change notification settings - Fork 33
Devlog 2023 03 09
- Date and Time:
- Location: Discord
- Duration: 45 minutes
- Recording
- Feedback and Discussion Form
- Current Iteration 🗓️
- Iteration Goals 🎯
- Iteration Results ✅
- External Contributions ⭐
- Upcoming Iteration 🗓️
- Feedback and Open Discussion 💡
- About Pocket Network 💙
- Duration: February 22 to March 7 2023
- Backlog
- M1: PoS
- Unblock the next steps of peer discovery by fully merging the initial LibP2P integration
- Cont. state sync MVP
- M2: DoS
- Cont. deploy localnet in a remote environment
- M3: RoS
- Cont. Utility module foundations to unblock interface design
- Completed
- https://github.com/pokt-network/pocket/issues/504
- https://github.com/pokt-network/pocket/issues/347 (please see linked PRs for more details!)
- In Review
- In Progress
- Data provided from POKTScan https://github.com/pokt-network/pocket-core/issues/1523
- https://github.com/pokt-network/pocket/pull/526
- https://github.com/pokt-network/pocket/pull/529
- https://github.com/pokt-network/pocket/issues/489
- https://github.com/pokt-network/pocket/pull/510
- Duration: March 8 to March 21 2023
- Backlog Candidates
Q: Are these keys also hierarchical in the original sense of bit-44 such as that any given key you can derive valid keys deterministically but not going back up? Can you also re-derive deeper ancestor keys from midpoint between the root and far off ancestor?
A: The keys are generated from the path so for any given master key it will generate the key up to the index. Given the index child key, there is no way to go backward to the parent key as far as generation is concerned (following bit-44 hierarchy). Currently each time you generate a key from it's from a hardcoded path, so if we wanted to generate up to a certain index and hash from that point to shorten the amount of time that is definitely possibly by enabling new user paths.
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
Pocket Network is a blockchain data platform, built for applications, that uses cost-efficient economics to coordinate and distribute data at scale.
Contents
- Home
- Persistence
- Changelog
-
Persistence
- Indexer
- Rpc
- Runtime
- State_Machine
-
Guides
- Roadmap
-
Guides
- Learning
- Guides
-
Guides
- Contributing
- Devlog
-
Guides
- Dependencies
-
Guides
- Releases
- Guides
- P2P
-
Shared
- Crypto
- Shared
-
Shared
- Modules
-
Build
- Config
- Consensus
-
Guides
- Telemetry
- Utility
- Logger