Create index.yaml vultisig - #2246
Open
realpaaao wants to merge 1 commit into
Open
Conversation
Adds src/projects/vultisig/index.yaml and logo.png (400x400 PNG).
This file contains hidden or 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
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.
Adds Vultisig to the explorer: an open-source, seedless, self-custodial multi-chain
wallet that uses MPC threshold signatures (DKLS23) instead of a seed phrase.
Files:
Where it sits in the dataset: same category/usecase as the existing wallet entries
(edge, zengo, sparrow) — categories: [applications], usecases: [wallets, mpc],
ecosystem: [multichain].
On the privacy fields specifically, so nobody has to take my word for it:
transactions, no mixing, no Tor. connected_tx is true and dissapearing_tx is false
for the same reason. I'd rather the entry be accurate than score well.
wallet; the apps collect no personal data (privacy policy:
https://vultisig.com/privacy); vault data stays on the device; the clients are
open source under Apache-2.0 (MIT for the SDK); custody is non-custodial with
m-of-n threshold signing, so no single party — including us — can sign alone.
Tor or proxy support to claim.
server used for remote device pairing, and the third-party swap providers) instead
of "none".
Audit linked is Trail of Bits' review of the DKLS23 implementation by Silence
Laboratories (2024-04-10), which is the threshold signature library the wallet uses.
Happy to adjust any field or drop ones you'd rather see left empty.
receipts
make testandmake buildrun locally against this branch: