Add multisigs#40
Merged
Merged
Conversation
…estamp as last col in table
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
1 participant
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.
Summary
Note
Medium Risk
Large read-only UI and query surface around multisig proposals and account activity; mistakes mainly affect display and navigation, not on-chain execution.
Overview
Adds multisig coverage to the block explorer: indexed creation, proposal state, and the full lifecycle (created, approvals, ready, executed, cancelled, removed, deposits claimed), wired through GraphQL the same way as other chain events.
Proposals get a dedicated list plus a detail view with status, deposit, decoded call metadata, and a timeline of related extrinsics. Accounts can resolve a multisig by id, show multisig configuration on the account page, and surface multisig activity in the unified transaction feed with typed labels and deep links.
Supporting work includes route/resource constants, table columns, schemas, sort options, and shared UI such as
ProposalIdLinkfor cross-linking proposals and accounts.Reviewed by Cursor Bugbot for commit fafd185. Configure here.