liftedinit / liftedinit/roadmap

KVStore in QA/Staging network

Open
#78 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kvstore story
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Description: This story is to propagate all of the KVStore work and stories to the QA/Staging network so that Liftoff Program members can interact with it. KVStore cluster in QA but needs to be refreshed. KVStore transfer function was missing in dev demo. It is not in the ABCI endpoints, RC15 can fix this.

Story ROI
Customer Need: Liftoff Program members will now be able to interact with and provide feedback on the feature.
Business Objective: Enabling more development and use cases to occur on the Manifest Network. This can lead to more network usage.

As a developer, I want to I want to record arbitrary data on-chain so that it is immutable.

  • Should fix ABCI endpoint not having the KVStore transfer function.
  • Should function as required in #16 , #17 , #18 , #19 , #20 , #66 , and #67 .
  • Should be demoed in the QA/Staging network.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the requirements in issues #16, #17, #18, #19, #20, #66, and #67, then inspect the ABCI endpoints for the missing KVStore transfer function. Confirm the KVStore cluster is refreshed in QA/Staging and that the feature works there for the listed requirements and demo.

Written by the indexing model from the issue text.

Assessment

Domain
blockchain
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.