feat: allow providing old mnemonics to collect pending TAPv1 RAVs #1159
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
providing the old mnemonic(s)
Details
TAPv1 RAV collection requires signing with the allocation-specific key derived from the operator mnemonic that created the allocation. After rotating to a new operator wallet, RAVs for old allocations would fail to collect because the new operator's mnemonic cannot derive the correct signing key.
Note that TAPv2 (Horizon) does not require the original operator mnemonic for RAV collection so legacy operator mnemonics are not necessary if keys are rotated.
This PR adds a
--legacy-mnemonicsoption that allows providing previous operator mnemonics. The TapCollector will:Usage
CLI:
Environment variable (pipe-separated):