Benjamin Kampmann
2168a6d0c9
* Intend to reactivate cargo-unleash check It appears the bug it was deactivated for has been resolved a while ago. Trying to reactivate the checks. * adding missing cargo.toml metadata for BEEFY crates * fix wrong version reference * matching up versions * disable faulty cache * switching more versions to prerelease * Revert "disable faulty cache" This reverts commit 411a12ae444a9695a8bfea4458a868438d870b06. * bump minor of sc-allocator to fix already-published-issue * fixup another pre-released dependency problem * temp switch to latest unleash * fixing dependency version and features * prometheus endpoint has also been changed * fixing proposer metrics versioning * fixing hex feature for beefy * fix generate-bags feature selection * fixup Cargo.lock * upgrade prometheus dependencies * missed one * switch to latest release
Proof of work consensus for Substrate.
To use this engine, you can need to have a struct that implements
PowAlgorithm. After that, pass an instance of the struct, along
with other necessary client references to import_queue to setup
the queue.
This library also comes with an async mining worker, which can be
started via the start_mining_worker function. It returns a worker
handle together with a future. The future must be pulled. Through
the worker handle, you can pull the metadata needed to start the
mining process via MiningWorker::metadata, and then do the actual
mining on a standalone thread. Finally, when a seal is found, call
MiningWorker::submit to build the block.
The auxiliary storage for PoW engine only stores the total difficulty.
For other storage requirements for particular PoW algorithm (such as
the actual difficulty for each particular blocks), you can take a client
reference in your PowAlgorithm implementation, and use a separate prefix
for the auxiliary storage. It is also possible to just use the runtime
as the storage, but it is not recommended as it won't work well with light
clients.
License: GPL-3.0-or-later WITH Classpath-exception-2.0