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
Parse public key appears to incorrectly handle public keys (observed behavior: empty addresses) when used by memorialize contract
Version
v1.0.0-HEAD
Steps to Reproduce/Remediation
During testing of P8e client integration using Memorialize contract it seems that the parse public key method is not behaving as expected. Create a unit-test for this method and ensure it correctly handles both 33 byte (compressed) and 64 byte (uncompressed) secp256k1 keys.
Summary of Bug
Parse public key appears to incorrectly handle public keys (observed behavior: empty addresses) when used by memorialize contract
Version
v1.0.0-HEAD
Steps to Reproduce/Remediation
During testing of P8e client integration using Memorialize contract it seems that the parse public key method is not behaving as expected. Create a unit-test for this method and ensure it correctly handles both 33 byte (compressed) and 64 byte (uncompressed) secp256k1 keys.
provenance/x/metadata/types/p8e.go
Lines 381 to 391 in 4192fd4
Appropriate test case public key values:
For Admin Use
The text was updated successfully, but these errors were encountered: