Seedtool Needs to Deal with Unknown Data
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Reproduce the documented seedtool envelope import/export command and compare the imported output with the original envelope. Trace the envelope handling entry points, then resolve the intended behavior for known data types, unknown data types, and attachments; done requires an agreed policy and behavior that no longer silently loses the output-descriptor data.
Written by the indexing model from the issue text.
Description
Seedtool needs to have a methodology for dealing with unknown data in Envelopes of seeds it imports.
For example:
% envelope format ur:envelope/lrtpcsgdhkwzdtfthptokigtvwnnjsqzcxknsktdoyadcsspoycfadzttpcstantjyoeadisktjojeisdefzdydtaolytantjloxaxhdclaxvlcprfttldjobkredtlnhsidwybaeyjtswyandlgjnehtkdsidbkqzsrkphyfhsaaahdcxhnfgnepefxgdytryckticelyotsstoknfntavevaskiddmolsarntykbrybtjpksamtantjooeadlncsghykaeykaeykaocyhngrmuwzaycyzssajpsnoybdtpcskpfyhsjpjecxgdkpjpjojzihcxgdihiajecxhfinhsjztkwewyfn
Bytes(16) [
'isA': 'Seed'
'508': output-descriptor(Map)
'hasName': "Dark Purple Peck Vial"
]
Currently if you import this into Seedtool and reexport it, the output-descriptor is silently dropped.
% seedtool -i envelope ur:envelope/lrtpcsgdhkwzdtfthptokigtvwnnjsqzcxknsktdoyadcsspoycfadzttpcstantjyoeadisktjojeisdefzdydtaolytantjloxaxhdclaxvlcprfttldjobkredtlnhsidwybaeyjtswyandlgjnehtkdsidbkqzsrkphyfhsaaahdcxhnfgnepefxgdytryckticelyotsstoknfntavevaskiddmolsarntykbrybtjpksamtantjooeadlncsghykaeykaeykaocyhngrmuwzaycyzssajpsnoybdtpcskpfyhsjpjecxgdkpjpjojzihcxgdihiajecxhfinhsjztkwewyfn -o envelope | envelope format
Bytes(16) [
'isA': 'Seed'
'hasName': "Dark Purple Peck Vial"
]
Options for dealing with this:
- Silently drop it [current]
- Drop it with a WARNING
- Silently carry it over
- Carry it over with a WARNING
- Drop it, but offer an additional Envelope containing only the dropped data.
...
There are potentially three categories of data here, with the possibility to deal with them differently.
A. Known data types (like output-descriptor)
B. Unknown data types
C. Attachments
- Dominant language
- Rust
- Stars
- 11
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from BlockchainCommons/seedtool-cli-rust
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
BlockchainCommons/seedtool-cli-rust#11 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
BlockchainCommons/seedtool-cli-rust#10 · 2 comments ·
All issues in BlockchainCommons/seedtool-cli-rust
Similar issues
-
component:sight
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
agentic-os-org/ANOLISA#4115 · 1 comment ·
Maintainers usually reply within 1 day
-
A-io-database bug needs triage python
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Change output crossing a compactsize boundary leaves the fee slightly below the requested feerateOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bitcoindevkit/bdk_wallet#578 ·
Maintainers usually reply within 8 days
-
`python.analysis` setting changes (e.g. `completeFunctionParens`) are not picked up until reloadOpenlanguage-server
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days