fix: gob: type elliptic.p256Curve has no exported fields.
#95
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.
When I read the wallet file using the code in the original code, I encountered this error:
gob: type elliptic.p256Curve has no exported fields.
This is due to the fact that the
elliptic.p256Curve
type in thecrypto/elliptic
package has no exported fields, whereas the Gob encoder requires that all fields in the struct must be exported.So I defined an exportable type,
SerializableWallet
, to store the parameters of the elliptic curve, and modified the decoding and encoding parts of theLoadFromFile
andSaveToFile
methods.