grrowl / redux-scuttlebutt

Distributed replicated redux store
170 stars 14 forks source link

Action signature hashes (anti-tampering) #8

Closed grrowl closed 7 years ago

grrowl commented 8 years ago

I've released a Component-based userland solution. It generates an ed25519 privateKey on mount, and passes down the functions signMessage, verifyMessage and generateKey to its children as props.

What would be the perfect API for this feature? Does it belong in redux-scuttlebutt or does it make sense as an auxiliary module?

grrowl commented 8 years ago

Add verifyAsync option

questions

grrowl commented 7 years ago

Related discussion, "Why syncing actions instead of data model?"

There's also a bit of talk about CRDTs which don't really require the time travel functionality we've implemented, but they're not hurt by it. Currently, an action like ADD_MESSAGE can simply return state.concat(message) (that is, push it onto the state array) and even outdated/old actions from remote peers will be inserted at the correct position in the array.

grrowl commented 7 years ago

With dispatcher options verifyAsync and signAsync added, message signing and validation can be enabled by other modules (such as the in-progress redux-signatures)