Skip to content
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

Move to using flumedb #11

Open
nikolai-b opened this issue May 28, 2018 · 1 comment
Open

Move to using flumedb #11

nikolai-b opened this issue May 28, 2018 · 1 comment

Comments

@nikolai-b
Copy link
Member

nikolai-b commented May 28, 2018

Currently we store in json. Use flumedb and flumelog-offset.

Background 👀 to flumedb video

@ameba23
Copy link
Member

ameba23 commented Jun 17, 2018

This is now implemented, in that we no longer use a local file, and get all ssb-sourced information through our ssb plugin.

But electrum still writes to a local file internally, and when we stop using electrum we need to think about how we will store the equivalent information. It would be great to use some simple key-value store, but it needs to be encrypted. We need to look into whether is possible to write to our local flume db without publishing to ssb if that makes sense. and think about security - privates keys will need to be stored, which under no circumstances should be published to ssb, regardless of whether they are encrypted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants