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
Currently TxFlow does not output consensus. They are partially computed inside TxFlow DAG but not exposed to the outside. We should compute them and stream them in the output stream of TxFlowTask.
MisbehaviorVerifier. TxFlow should should be able to report misbehavior as soon as it detects it, which can happen in the different parts of our infrastructure: in Message, DAG, TxFlowTask structs. For now MisbehaviorVerifier does not need to send it for slashing but can simply print it or write to a file for testing.
Replace hash with real crypto hash. We should be using crypto hash instead of the hashmap hash is some places.
Replace signature with real signature. TxFlow might need to link to the component that does the signing, since TxFlow should not have access to private keys.
The text was updated successfully, but these errors were encountered:
Currently TxFlow does not output consensus. They are partially computed inside TxFlow DAG but not exposed to the outside. We should compute them and stream them in the output stream of TxFlowTask.
MisbehaviorVerifier. TxFlow should should be able to report misbehavior as soon as it detects it, which can happen in the different parts of our infrastructure: in
Message
,DAG
,TxFlowTask
structs. For now MisbehaviorVerifier does not need to send it for slashing but can simply print it or write to a file for testing.Replace hash with real crypto hash. We should be using crypto hash instead of the hashmap hash is some places.
Replace signature with real signature. TxFlow might need to link to the component that does the signing, since TxFlow should not have access to private keys.
The text was updated successfully, but these errors were encountered: