You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ct() taproot descriptors with script tree don't parse #105
ct(slip77(...),eltr(...)) with script tree fails to parse, though same descriptor displays and derives addresses fine. No test covers this combination, only key-path eltr.
ct(slip77(...),eltr(KEY,{pk(A),pk(B)})) now parses and round-trips
Both tests from the fork commit (topologoanatom@14ced55) fail on the commit before #112 and pass on the current master
Though, one case still breaks the same way the issue describes
A ct() whose eltr leaves use extension fragments like is_exp_asset(...)
It displays and gives an address, but won't parse back
The cause is that the eltr inside ct() is always parsed without extensions
Activity
KyrylR commentedon Nov 10, 2026
ct(slip77(...),eltr(KEY,{pk(A),pk(B)}))now parses and round-tripsBoth tests from the fork commit (topologoanatom@14ced55) fail on the commit before #112 and pass on the current master
Though, one case still breaks the same way the issue describes
A
ct()whoseeltrleaves use extension fragments likeis_exp_asset(...)It displays and gives an address, but won't parse back
The cause is that the
eltrinsidect()is always parsed without extensionsWill do the follow-up to fix the last part
KyrylR commentedon Nov 10, 2026
For the context, a follow-up is related to this part #112 (comment) (as far as I can see)
topologoanatom commentedon Nov 13, 2026
@KyrylR
Another case is multipath descriptor len mismatch with
ct(), likeProvided tests against current master at another branch on fork (topologoanatom/elements-miniscript@314489a).
It implicitly follows from your description in #109
, but that PR is closed so leaving this just for tracking's sake.