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 each active secure protocol is set out to have its own error type for failed checks.
Most protocols will have errors for the transport layer, but these will also have a 'malicious' error that can be 'thrown'. As such a common trait or type for this kind of error could make sense, especially when it comes to handling malicious behaviour.
A sketch for a trait could be
traitMalicious:Error{fnoffenders() -> &[Id];}
as such the runtime could chose to handle with the given offenders in a fit manner, either excluding them and continuing, banning them and aborting or something else entirely.
The text was updated successfully, but these errors were encountered:
Currently each active secure protocol is set out to have its own error type for failed checks.
Most protocols will have errors for the transport layer, but these will also have a 'malicious' error that can be 'thrown'. As such a common trait or type for this kind of error could make sense, especially when it comes to handling malicious behaviour.
A sketch for a trait could be
as such the runtime could chose to handle with the given offenders in a fit manner, either excluding them and continuing, banning them and aborting or something else entirely.
The text was updated successfully, but these errors were encountered: