You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GunDB has been a good temporary solution while we wait for something more web3 native to mature. However, it is not particularly decentralized and has frequently caused issues like #420 when our GunDB node is down or the app is misconfigured.
After speaking with @corpetty last week, I'm convinced there are some web3 native options that we could use right now, which would be both more reliable and less trustful.
There are two options I'd like to explore:
Waku / Waku Connect: is a decentralized messaging protocol (the successor to Whisper, originally part of the Ethereum vision).
Waku has its origins in the Whisper protocol, but optimized for scalability and better usability
Waku removes centralized third parties from our messaging, enabling private, secure, censorship-free communication.
Waku is designed for generalized messaging, enabling both human-to-human or machine-to-machine communication.
One nice quality of Waku, according to what I understand from @corpetty, is that messages persist for roughly 30 days. This is the perfect amount of time for them to be available to be used during a round, and then vanish into the ether once the round is over and they won't be required again.
Deterministic key derivation: using a process similar to loopring, we could deterministically generate the user's MACI keys based on their authenticated address, the address of the round, and some nonce/salt. This way, rather than storing the keys somewhere, we just recreate them locally on-the-fly.
The text was updated successfully, but these errors were encountered:
GunDB has been a good temporary solution while we wait for something more web3 native to mature. However, it is not particularly decentralized and has frequently caused issues like #420 when our GunDB node is down or the app is misconfigured.
After speaking with @corpetty last week, I'm convinced there are some web3 native options that we could use right now, which would be both more reliable and less trustful.
There are two options I'd like to explore:
One nice quality of Waku, according to what I understand from @corpetty, is that messages persist for roughly 30 days. This is the perfect amount of time for them to be available to be used during a round, and then vanish into the ether once the round is over and they won't be required again.
The text was updated successfully, but these errors were encountered: