-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
feat: new plugin nillionDB #2133
Conversation
Here's another demo: https://x.com/nillionnetwork/status/1882866783658639790 |
Hello, We are changing our plugin development strategy to be more scalable. We have moved the plugins out into their own repos and we're looking for people to either maintain those or own them on their own Github. If you'd like to be a maintainer, file an issue in the plugin repo and join our Discord https://discord.gg/elizaos to coordinate. If you'd like to control the plugin on your own Github, please add an issue to the plugin repo pointing to your repo, and add a modification to the registry. Submit a PR to edit the registry here: https://github.com/elizaos-plugins/registry Closing this PR for now. Let us know if you have any questions. |
resolves conflicts for #2079
couldn't push to PR branch #2079
Original submission by jimouris
Add Nillion action to upload a secret (string) to nilDB (secret shares). Add Nillion action to retrieve a secret (string) from nilDB.
Relates to
Closes #2077
Risks
Low. A new plugin, which is isolated and should not affect existing functionality.
Background
What does this PR do?
A plugin for storing and retrieving data from Nillion's nilDB within the ElizaOS
ecosystem.
The Nillion plugin enables seamless integration with the decentralized nilDB
database backed by secure multi-party computation (MPC). The plugin provides
functionality to store and retrieve secrets to/from nilDB. When you store your
data in nilDB nodes, your data are secret shared in a way that none of the nodes
can learn anything about your secrets. Then, when all the secret shares are
combined, you can retrieve your original data.
What kind of change is this?
Features (non-breaking change which adds functionality)
Why are we doing this? Any context or related work?
To extend the functionality of Eliza.
Documentation changes needed?
Require a change to the project documentation.
Testing
Where should a reviewer start?
Start by reviewing the upload and retrieve .ts files.
Detailed testing steps
cc: @tim-hm