keybase / keybase/keybase-issues

Use OP_RETURN to store merkle root in bitcoin blockchain

Open
#1,104 2 comments 4 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

Instead of sending to a bitcoin address, which adds to the set of unspent outputs (UXTO), you should use OP_RETURN. More info: https://en.bitcoin.it/wiki/Script#Provably_Unspendable.2FPrunable_Outputs

Many bitcoin clients index the UXTO set and if used to store data in an automatic way, the set increases faster. A better way is to use OP_RETURN and let those transactions be pruned from the set. The OP_RETURN can be followed by arbitrary data and you can store the merkle root. It is the same principles the [Proof of Existence](http://www.proofofexistence.com/about) site is using.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the issue's proposal and the linked Bitcoin Script and Proof of Existence references. Identify the repository entry points for storing the merkle root, then confirm the intended OP_RETURN behavior and define completion criteria with maintainers before making changes.

Written by the indexing model from the issue text.

Assessment

Domain
blockchain
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.