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
events cross upgrade boundaries, so while making changes we will need to be able to deserialize previous version events as well as being able to serialize them to the exact same bytes (this is needed to validate the hash of the event)
a good way to manage this migration is to have separate fields for protobuf objects
once the refactor is done, a SelfSerializable will wrap a protobuf event to support migration. once the migration is complete, we can remove that wrapper
as far as we know, no one is consuming the consensus event stream, so making changes to it is not a problem
due to current challenges, all protobuf definitions will be in the same module, platform and services
End goals:
Apps consume all required protobuf records (payloads, core data, signature)
Gossip (& PCES) protobuf events
Double hash payloads when hashing an event
Cleanup internal event structure
The content you are editing has changed. Please copy your edits and refresh the page.
Notes:
End goals:
Discussion and planning
Preparation
Transaction
com.swirlds.common.crypto.Signature.verifySignature()
#12214Event
Hash
should become immutable #12456Misc tasks
PlatformEvent::getOtherId
#12464SimpleEvent
#12898PlatformEvent
#12959The text was updated successfully, but these errors were encountered: