Comments (2)
Do we want to handle received aggregated signatures? We could store them in the db and not need to broadcast them (as we already broadcast them when we received them). As a result we would not need create a new aggregated signature.
It should rarely happen that we ever receive an aggregated signature without being able to create one ourselves (or having already created one)since our peers should have sent us every signature they have seen.
I decide not to handle this case for now.
from rolling-shutter.
I think we should at some point, but not now. Ideally, every node waits a random amount of time before creating the aggregated signature so that it (a) includes signatures of mos nodes and (b) only one node generates it.
It should rarely happen that we ever receive an aggregated signature without being able to create one ourselves (or having already created one)since our peers should have sent us every signature they have seen.
I think it will happen often because of symmetry: every node is equal, so every node will receive enough signatures at roughly the same time, so every node will send the aggregated signature at roughly the same time. That is, unless latency or connectivity differences become too big. But we'll see.
from rolling-shutter.
Related Issues (20)
- segfault when shutting down chain subcommand HOT 2
- JS package is conflicting with other packages exporting a Sentry class HOT 8
- Make final release of shutter-crypto js lib HOT 1
- Introduce consistent line-length code formatter in pre-commit hook HOT 2
- Consistent command-builder options HOT 1
- Change epochid type to be arbitrary length HOT 1
- Resolve eon index / keyper set index ambiguity HOT 2
- Replace eon with keyper set index in gossip messages HOT 1
- Improve Gnosis keyper p2p connections HOT 2
- Unify libp2p log format
- Version identifier for encrypted messages HOT 1
- Update shcrypto package HOT 1
- Merge gnosis branch into main HOT 1
- Unify execution chain syncing HOT 1
- Handle reorgs
- Fix tx pointer age issue HOT 4
- Investigate key generation performance HOT 2
- Keypers crash when started before first keyper set activation
- Message handling optimization
- Invalid slot decryption signatures HOT 4
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 rolling-shutter.