-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Conversation
I really don't agree with this -- Engine is supposed to be a relatively agnostic consensus mechanism which the client and other related services can leverage. Any communication with other parts of the codebase should be done through a more general mechanism. I'm not sure |
so however, |
Changes Unknown when pulling 38ea976 on validator-lookup into ** on master**. |
Now the two |
let mut sealing_work = self.sealing_work.lock(); | ||
sealing_work.enabled = self.engine.is_sealer(&address).unwrap_or(false); | ||
*self.author.write() = address; | ||
{ |
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.
good to have a comment here to ensure any newcomer understands what the parens are for.
minor grumble. ltgm otherwise. |
Ability to use a contract at a specified address to determine the current list of validators (renamed from authorities) as an alternative to fixed spec list. The test contract is here.
Another change is thatEngine
now holds aWeak<Client>
rather thanIoChannel
.Do not merge for 1.5, goes after #3932.<\s>