We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There is a scenario where we need to broadcast a valuable data over network signed by a private key
There were few cases where we didn't need a whole stack for example:
In the examples above we didn't need a liability module (and blockchain part in particular) rather we needed IPFS part only
Launching let's say "signer only" would help to run our framework on low performance hardware like Raspberry Pi and similar ones
The text was updated successfully, but these errors were encountered:
What's about using libp2p PeerId for each message? Every GossipsubMessage has it as source field.
libp2p
source
PeerId could be derived by one of the following public keys:
https://docs.rs/libp2p/0.17.0/libp2p/identity/enum.PublicKey.html
Sorry, something went wrong.
Implemented in pubsub module, each message has sender ID that could be used in pair with the static link to ETH/Polkadot/etc. account.
No branches or pull requests
There is a scenario where we need to broadcast a valuable data over network signed by a private key
There were few cases where we didn't need a whole stack for example:
In the examples above we didn't need a liability module (and blockchain part in particular) rather we needed IPFS part only
Launching let's say "signer only" would help to run our framework on low performance hardware like Raspberry Pi and similar ones
The text was updated successfully, but these errors were encountered: