Add WalletConnect support to Blockdaemon Institutional Vault - #16
Open
MnrGreg wants to merge 1 commit into
Open
Conversation
Self-attest Canton dApp connectivity with DA Registry and Vault session screenshots so the directory shows the proven WalletConnect path.
MnrGreg
requested review from
hythloda,
isegall-da,
omaiko-intellecteu,
stas-sbi,
tkatrichenko and
waynecollier-da
August 28, 2026 01:22
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.
Type of submission
Summary
Self-attest WalletConnect for Blockdaemon Institutional Vault. The listing now claims
walletconnect_supportwith screenshots of a Vault Canton WalletConnect session and the samebd::party connected in DA Registry (Test).Checklist
wallets/<wallet-name>.yamladded or updated (self-attestation)proofs/<wallet-name>/<wallet-name>-self-attestation.mdfor every feature newly claimed as
supported: truepython scripts/generate_table.pywas run and the regeneratedWALLET_DIRECTORY.mdis included in this PR (a CI check will catchthis if it's missed, but running it locally saves a round trip)
#ext-temp-party-scalingand setslack_party_scaling_channel_joined: true(already set on the existing listing from Add Blockdaemon Institutional Vault to the wallet directory #12)
feature's
reason:field, not just left blankproofs/<wallet-name>/<wallet-name>-third-party-attestation.mdreflects evidence gathered independently, not copied from the
wallet's self-attestation, and
resulton the matchingverified_byentry is set toverifiedorunsupportedto matchAdditional context
Evidence is connection and party identity (no dApp-initiated on-chain update ID attached):
bd::122075956b9…registry.test.app.digitalasset.com/registry/onboarding): connected Wallet / Provider partybd::122075956b920f8d6786f4872515e900d7920c19c5c57647d434fc62b5c5229913bf, User IDbdPublic docs: WalletConnect Usage, IV v3.7.0 changelog.
Follows Add Blockdaemon Institutional Vault to the wallet directory (#12).