feat: Add Narval Armory Keyring Connection #2481
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Samuel <[email protected]> Co-authored-by: Ptroger <[email protected]> Co-authored-by: William Calderipe <[email protected]>
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/[email protected], npm/[email protected], npm/[email protected] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TLDR
A new keyring & connection flow to add Narval as an institutional wallet connection
Background
Narval's Armory Stack is an open-source web3 access management system.
It's a policy engine to govern signing operations, compatible with any key management tech. Plus it has a key vault if you need one.
This PR
We've added a new Institutional Wallet Connection option to connect w/ a Narval Armory (auth server) & Vault (key signer). It uses a private key as a user credential & stores the connection details in the keyring. Then fetches any remote accounts the user has access to & allows operation through Rabby.
Policy rules can be configured in Narval to limit operations allow by a given user.
The Armory auth system also works with other key tech & providers, acting as a unified access management layer across all keys & wallets.
See demo video here https://www.loom.com/share/0a68a07c88614362a9486f8db8e7320e?sid=e01f5645-3aa3-4d89-819b-46e00f69b032