Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

(feature) Remote peer integration implementation

Open
#28 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust, wasm

Research direction

Start with the intro README claim about uploading data to a remote peer and periodically checking random 1KB slices against a local hash. Review Carbonado's existing storage and verification entry points, then investigate whether rust-libp2p is an appropriate integration path. The issue needs a defined protocol, scope, and acceptance criteria before implementation can be considered done.

Written by the indexing model from the issue text.

Description

Hey @cryptoquick really cool repo!

I read in the intro readme:

it can be uploaded to a remote peer, and random 1KB slices of that data can be periodically checked against a local hash to verify data replication

As far as I can tell, this integration has not been implemented, right? If it has, could you point out the repo?

We could use something like rust-libp2p (which powers IPFS) to build an app on top of carbonado that does this?

I have always liked the idea of peer mesh data replication but haven't seen many good tools in rust and wasm until this. I was thinking Carbonado could be used to create a social backup of Shamir's Secret Sharing key slices amongst friends (contacts) for social recovery? What are your thoughts on that, and are there any efforts right now working towards that which I could contribute to?

Dominant language
Rust
Stars
119
Forks
9
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from bitmask-stack/carbonado

All issues in bitmask-stack/carbonado

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.