Covenant extension & "Error: All spend paths must require a signature" error

Open
#80 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust

Research direction

Reproduce the supplied taproot descriptor using CovExt and inspect the validation path that emits “All spend paths must require a signature.” Determine whether the introspection-only branch is intentionally rejected; completion would require a confirmed expected behavior and, if needed, a focused regression test or documentation update.

Written by the indexing model from the issue text.

Description

given the following taproot descriptor, using CovExt:

eltr(
    02d7924d4f7d43ea965a465ae3095ff41131e5946f3c85f79e44adbcf8e27e080e,
    {
        and_v(
            v:spk_eq(out_spk(0), 5120d7924d4f7d43ea965a465ae3095ff41131e5946f3c85f79e44adbcf8e27e080e),
            v:value_eq(
              010000000000000000,
              out_value(0)
            )
        ),
        and_v(
            v:pk(02d7924d4f7d43ea965a465ae3095ff41131e5946f3c85f79e44adbcf8e27e080e), 
            older(512)
        )
    }
)

returns

Error: All spend paths must require a signature

does it mean that introspection only paths are not allowed ?

Dominant language
Rust
Stars
15
Forks
17
PR merge metrics
No merged PRs in 30d

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/elements-miniscript

All issues in ElementsProject/elements-miniscript

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.