Skip to content

Add reward minting to the Blockdaemon Institutional Vault listing - #19

Closed
MnrGreg wants to merge 1 commit into
canton-foundation:mainfrom
MnrGreg:add-blockdaemon-reward-minting
Closed

MnrGreg wants to merge 1 commit into
canton-foundation:mainfrom
MnrGreg:add-blockdaemon-reward-minting

Conversation

@MnrGreg

@MnrGreg MnrGreg commented Sep 24, 2026 •

Copy link
Copy Markdown
Contributor

Type of submission

  • New wallet application
  • Update to an existing wallet's feature support
  • Third-party verification (confirmed, or disputed as unsupported) of an existing claim
  • Marking a feature as not supported, with a reason

Summary

Claim Super Validator reward minting for Blockdaemon Institutional Vault, with TestNet evidence that rewards mint to an IV external party through a Splice MintingDelegation.

Checklist

  • wallets/<wallet-name>.yaml added or updated (self-attestation)
  • A heading added to proofs/<wallet-name>/<wallet-name>-self-attestation.md
    for every feature newly claimed as supported: true
  • python scripts/generate_table.py was run and the regenerated
    WALLET_DIRECTORY.md is included in this PR (a CI check will catch
    this if it's missed, but running it locally saves a round trip)
  • If applying for the first time: confirmed membership in
    #ext-temp-party-scaling and set slack_party_scaling_channel_joined: true
  • If marking a feature as not supported: reason filled in under that
    feature's reason: field, not just left blank
  • If this is a verification: the heading added to
    proofs/<wallet-name>/<wallet-name>-third-party-attestation.md
    reflects evidence gathered independently, not copied from the
    wallet's self-attestation, and result on the matching
    verified_by entry is set to verified or unsupported to match

Additional context

Claim Super Validator reward minting via MintingDelegation, with TestNet party and contract evidence, and regenerate WALLET_DIRECTORY.md.
@davidrichards-da

Copy link
Copy Markdown
Contributor

The changed in this PR were included in PR#20 in this commit so I'm going to close this PR.

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

Successfully merging this pull request may close these issues.

2 participants