-
Notifications
You must be signed in to change notification settings - Fork 136
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
Warrants pt 3 -- authoring and integrating warrants #3875
Conversation
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.
👍
workspace | ||
.authored_db | ||
.write_async(move |txn| { | ||
warn!("Inserting warrant op"); |
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.
I suggest to add more info to this warning. I'd actually merge it with the one below and output the op that was rejected and the warrant op.
assert_eq!(warrants.len(), 1); | ||
}); | ||
|
||
// TODO: ensure that bob blocked alice |
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.
Is this going to be added?
Summary
Part of #3639
There are some significant changes to the way the way the database is used.
DhtOp.type
field.DhtOp.action_hash
field can also contain a WarrantHash.It's all a bit messy, but was done in the spirit of minimal effort and change.
TODO: