You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Since cryptography used in consensus is often generic or in some cases (e.g. PoW) doesn't exist, it will tend to be different from the account cryptography used in a runtime.
We will need to amend the various consensus Runtime API traits to get methods such as
traitSomeConsensusApi{fnconstruct_report_call(evidence:ReportSpecificEvidence) -> Vec<u8>;// corresponds to some unsigned extrinsic or `Call` type}
and then consensus engines should have access to some kind of trait or context that has a function
// signs and dispatches an encoded call with some pre-configured key// perhaps via a `--reporting-key` CLI.fnsign_and_dispatch_encoded_call(Vec<u8>) -> Result<(),Error>;
The implementation of this sign_and_dispatch_encoded_call function will vary from runtime to runtime.
The text was updated successfully, but these errors were encountered:
Since cryptography used in consensus is often generic or in some cases (e.g. PoW) doesn't exist, it will tend to be different from the account cryptography used in a runtime.
We will need to amend the various consensus Runtime API traits to get methods such as
and then consensus engines should have access to some kind of trait or context that has a function
The implementation of this
sign_and_dispatch_encoded_call
function will vary from runtime to runtime.The text was updated successfully, but these errors were encountered: