sdk: correct static keypair bytes in test sample transaction #32930
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.
Problem
way back when, we incorrectly converted a pkcs8-formatted ed25519 test keypair to raw bytes while porting ed25519 support from
ring
toed25519_dalek
. i noticed and yolo'd a "fix" into #32926, but nfc if the raw private key bytes were actually a valid private key.Summary of Changes
NOTE: i went to the trouble of tracking this down to ensure #32926 wasn't likely to break any existing filesystem keypairs we may have generated in the past.