Comments (6)
See BFT Forensics
from ssv-spec.
See BFT Forensics
I have read it. It only identifies the double vote misbehavior, can not solve the liveness vioaltion right?
My question is that operators3-4 don't send any protocol(validator duty) messages to the dvt cluster and discard the protocol messages of operators1-2. How to prove the operators3-4 are the faultys ?
from ssv-spec.
Yes, BFT Forensics can't solve the protocol. On a theoretical point of view, any BFT can only guarantee its properties (agreement, termination, etc) if at maximum
We don't have BFT Forensics yet, but multiple strategies could be added, such as idleness, invalid messages and so on.
from ssv-spec.
I'm also interested in evaluating the performance of operators in ssv (shown bolow)
https://docs.ssv.network/learn/performance
https://docs.ssv.network/learn/performance/statuses
Now assume, there are four operator1, operator2, operator3, operator4. '' implies the Byzantine.
And operaotors1-4 only perform the validatorX.
Operators1-3 do the protocol while the operator4 is offline --> The validatorX does not miss any duty.
⚠⚠⚠
So the result is that the performance and status of operator1-4 are the same : 100% and active
Right ? 👀👀👀
@MatheusFranco99 @GalRogozinski
from ssv-spec.
Your last question is best to be asked on our Discord server
https://discord.com/invite/ssvnetworkofficial
this repo is used for discussing issues of the core protocol itself
from ssv-spec.
ok ,thanks
from ssv-spec.
Related Issues (20)
- Take the OperatorID field out of partialSigMessage HOT 1
- RunnerRole can be compressed farther on wire HOT 1
- SignedSSVMessage isn't very readable and we invoke Decode too much. HOT 2
- We do slashing checks on sync committees HOT 4
- `DomainType` fits better in config than in committeeMember ( or share for that matter) since its used for everything under the same network and we're not going to have different domainTypes for different shares/members ever unless its a bug.
- We seem to have some redundancy with "e2e" and "unit tests"
- All runners should be committee Based
- Get rid of the `GetShare` pattern that loops over share map
- Include Message Validation in Spec
- Reduce State Comparison Files
- Simplify Message Containers
- `DecidedValue` in BaseRunner has a misleading name.
- Update Alan fork epoch in spec
- we printed errors instead of returning them HOT 2
- We can't reach Message Type error in tests that comes from `baseCommitValidationIgnoreSignature`
- can we use one of the sign functions in the runners instead of repeating this code?
- instead of storing a map of shares here, i think we should store map of shares in CommitteeRunner and only a single share in the other runners
- i think we can remove all getters that dont do any computation (in all code not just here)
- Sort signers in decided messages
- Don't process messages after instance is decided
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ssv-spec.