nextdotid / kv_server Goto Github PK

Description

KVService is a Zero-Trust Key-Value storage space for any user who has an elliptic curve-based asymmetric key pair (aka Avatar.

• Introduction to KVService

It is designed as a git-like patch chain, so there is a possibility to implement a revert function, which allows the user to undo a specific change he/she has accidentally made before.

• This revert action should also be a link in the patch chain, and should be signed by the user’s Avatar.
• When a revert is done, the entire KV state from the beginning of the KVChain should be updated.

Have a look at ProofService’s Proof Chain to help you understand this chain structure.

Expected outcomes

Modify model/kv_chains (the place to store the whole chain), model/kv (snapshot of a chain’s final status) and /controller to add a action field with possible values create and revert .

And correctly handles action: revert request.

Don’t forget to write unit tests.

Skills required

• Rust
• Basic knowledge of database

Mentor

Nyk Ma @nykma

Expected size of project

175h

Level

Easy

We need to draft a common standard (like common.favorite) for all third-party users to build a common, cross-user favorite list.

Read more about this task and rewards on Dework.xyz

Should allow passkey (binded with ProofService Avatar) sign a patch and store under this Avatar namespace.

Related to NextDotID/proof_server#94

Description

KVService is a Zero-Trust Key-Value storage space for all users who has a elliptic curve based asymmetric keypair (aka Avatar.

• Introduction of KVService

It is designed as a git-like patch chain, each link on the chain is created and signed by user, so any third-party cannot modify / falsify it.

Currently we’ve impl it in a zero-trust way, but we still want to make it more decentralized, more neutral, by putting user’s link onto a storage provider like Arweave.

By uploading all KVChain onto Arweave, we can reach more usability and data transparency improvement.

Expected outcomes

• You may write a separated worker to do async upload job.
• You need to record Arweave’s ObjectID-ish into database after a successfully uploading.
• Arweave’s ObjectID should be returned in query API (if target record has one)
• Take a look at ProofService’s current impl as an example.
• Don’t forget unit tests.

Skills required

• Rust
• Basic knowledge of Arweave usage

Mentor

Nyk Ma @nykma

Expected size of project

175h

Level

Medium

Since KVServer is designed as a git-like patch chain, there is an ability to implement a revert function which allows user to revert a specific change made accidentally by user himself before.

• Add a new action called revert (or delete ?)
• Signature needed
• When Revert is made, rebuild the whole KV status from scratch.