Validation of consensus rules

Open
#86 7 comments 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
Domain
blockchain, testing

Research direction

Start by reading the referenced libbitcoinconsensus feature in rust-bitcoin and the existing tests that spin up elementsd. Determine which consensus and script-evaluation behavior should be covered without a daemon. Done requires an agreed scope and design for a unit-testable validation interface; the issue does not name files or a concrete implementation path.

Written by the indexing model from the issue text.

Description

Are there any plans on doing something similar in this library to the libbitcoinconsensus feature in rust-bitcoin?

At the moment, we are testing all of our stuff by spinning up elementsd instance which is obviously quite slow. It would be cool if we could at least test a subset of the functionality, in particular script evaluation, in a unit test.

What would it take to make that happen?

Dominant language
Rust
Stars
57
Forks
40
Avg merge
11h 58m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

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 ElementsProject/rust-elements

All issues in ElementsProject/rust-elements

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.