-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add beacon deposit event #142
Conversation
candidate: string | ||
candidate_list: string[] | ||
validator: string | ||
validator_list: string[] |
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.
Thoughts making most of these optional and then including them only when needed? When trying to make sense of the data for querying, it may be clearer to make columns don't apply to a particular row empty (as in the column is not used for that particular event type). For the specific example of validator_list
, there would be a conventional difference between an empty array and a null value.
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.
Sounds good, I updated the schema for both.
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.
Great work, love the type property descriptions!
…sensusnetworks/casimir into feature/beacon-deposit-event
Update schema
Added deposit event for contracts of interest