-
Notifications
You must be signed in to change notification settings - Fork 273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some pubsub suggestion #109
Comments
[admin note: I've moved this to the specs repo and renamed it.] |
Peers can choose which topics they subscribe to and (in go-libp2p-pubsub, at least) they can register topic validators. Such a validator could be used to validate a proof of work. In general, libp2p's pubsub is a stand-alone protocol that isn't tied to any blockchain. It's really just a low-level transport for building applications (which can validate their own messages).
libp2p-pubsub is a real-time broadcast system. You may be interested in libp2p/notes#2, a discussion about a potential offline message queue system. |
Quote my reply at Offline Message Queue #2 Offline messages should really be implemented by the service application. My initial thoughts:
Message struct example:
|
Problem:
Frequent data publish may lead to flooding and should be limited
Data should be time-signed to prevent the publish of large amounts of data pre-prepared (attack)
Suggest:
Published data with difficulty signature
signature(sha256(sha256(data + time + nonce))) < 0x0000012345...
so massive delivery requires a price
Time is defined as the (Time On the Chain), not the real time, is the latest block hash(filecoin, btc,....), so it can't be pre-made.
Implement offline message save and route (I am researching this so I don't have to work repeat...
:-) )
thomas92911 -- (ARS.China)
The text was updated successfully, but these errors were encountered: