BREAKING: human readable de/ser for versioned message#381
BREAKING: human readable de/ser for versioned message#381jstarry wants to merge 2 commits intoanza-xyz:masterfrom
Conversation
a0d108f to
29ad202
Compare
|
@jstarry can you add a description to the PR? |
apfitzge
left a comment
There was a problem hiding this comment.
lgtm - please just add a description before merging. title is descriptive, but still weird to not have one imo
|
Thanks for the review @apfitzge! Sorry I was in the middle of updating the description but got side tracked while looking into another human readable serialization issue. EDIT: Just conservatively marked this as breaking because my other change will definitely breaking |
|
Do we want to land this? We're about to publish a breaking change to solana-message for wincode and txv1, so now's a great time! |
eeae20d to
dbe6781
Compare
|
@joncinque I think it's still a desirable change, I've rebased and fixed the conflicts |
Versioned messages are not properly supported for human readable de/ser due to special handling of the version prefix byte. This is a breaking change to how versioned messages (including v0 and legacy) are serialized and deserialized when using a human readable serialization format. More context about the consequences of this lack of support can be found in #311
Old serialization:
New serialization:
{ "version": "0", "message": { "header": { "numRequiredSignatures": 0, "numReadonlySignedAccounts": 0, "numReadonlyUnsignedAccounts": 0 }, "accountKeys": [..] "recentBlockhash": [..], [..] } }