docs: spec

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Locate the spec document referenced by the issue and review how embedded data boundaries are currently explained. Document additional cases with examples, including OP_DROP as the separator and the handling of a literal OP_DROP in embedded data; done means the spec covers both cases clearly.

Written by the indexing model from the issue text.

Description

The spec should be improved to cover additional cases with examples. Things like OP_DROP being the separator used to identify where the embedded data ends should be explained. There should be a way to handle a OP_DROP literal in the embedded data.

Dominant language
Go
Stars
58
Forks
7
No merged PRs in 30d

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.

More from evstack/bitcoin-da

All issues in evstack/bitcoin-da

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.