[AC-1122] binary marshaling schema for fields
The objective of this task is to provide an alternative to having JSON validation rules for data accounts as specified by [https://accumulate.atlassian.net/browse/AC-723|https://accumulate.atlassian.net/browse/AC-723|smart-link] and instead have a binary marshaler/unmarshaler to manage the data
There are many different account types where if anything changes the protocol will need to perform a fork to upgrade accounts. What is needed is the ability to add binary data to data accounts that can be validated and used in leu of json that can be used within the protocol. One such example is moving the fee schedule to a data chain. In that case, if the fees ever need to be updated, rather than hard forking the protocol, it is a simple data entry to a managed data account and the protocol can use that data account to validate the fees.
Issue metadata
- Issue type: Task
- Priority: Medium
- Fix versions: 1.1