-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FIPs 36-40 changes to fio.contracts #269
FIPs 36-40 changes to fio.contracts #269
Conversation
FIP-37 remove keys restrictions
FIP-38 first dev iteration
FIP-39 add and info table and row type
FIP-39 add endpount and action for update_encrypt_key.
FIP-39 do the table update, dev tested and verified this works as expected.
FIP-39 integrate handle info into regaddress, xferaddress, burnaddress
FIP-39 comments for coding
FIP-39 fix bug found during dev test
FIPs36-40 error message analysis
@@ -792,6 +845,13 @@ | |||
], | |||
"type": "fioname" | |||
}, | |||
{ | |||
"name": "handleinfo", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We use "address" instead of "handle" elsewhere in the code. It could be confusing to introduce a new term. Plus, it is of type "fioname_info_item".
Suggest "fionameinfo"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will do.
FIPs36-40 code review items
Fips 36-40 code review feedback
…ons present FIP-39 add logic to handle update when there are other data descriptions present
FIPs 36-40 remove old note
Transferred to clean PR: #288 Closing |
This branch will be used for all changes for FIPs 36 -40 please do not merge until all FIPs are completed and verified by QA.