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
{{ message }}
This repository has been archived by the owner on Aug 14, 2023. It is now read-only.
We are planning on replacing the encoding internally used by SVM both for storage and on-wire entities representation with SZZ. This change would:
Reduce our codebase size.
Standardize our technology stack.
Facilitate the creation of alternative SVM implementations.
SSZ would thus be used to encode:
Template sections.
Transaction execution receipts.
Transaction contents.
(1) and (2) are mostly implementation details, and changing the encoding doesn't have ripple effects across the whole stack. On the other hand, (3) transaction syntax is extremely delicate and it needs to evaluted carefully. A the time of writing, a detailed SMIP documenting the proposed transaction syntax with SSZ is not available, but there is some promising work done by @noamnelke and @lrettig in this regard. See https://docs.google.com/spreadsheets/d/1JjKL9GgYTgNRM_qrkCcpxGeSUnwuhOeTC0dfn16ivHM/edit#gid=1073868340 for more information.
The text was updated successfully, but these errors were encountered:
We are planning on replacing the encoding internally used by SVM both for storage and on-wire entities representation with SZZ. This change would:
SSZ would thus be used to encode:
(1) and (2) are mostly implementation details, and changing the encoding doesn't have ripple effects across the whole stack. On the other hand, (3) transaction syntax is extremely delicate and it needs to evaluted carefully. A the time of writing, a detailed SMIP documenting the proposed transaction syntax with SSZ is not available, but there is some promising work done by @noamnelke and @lrettig in this regard. See https://docs.google.com/spreadsheets/d/1JjKL9GgYTgNRM_qrkCcpxGeSUnwuhOeTC0dfn16ivHM/edit#gid=1073868340 for more information.
The text was updated successfully, but these errors were encountered: