SV governance UI/UX improvements#444
Conversation
Signed-off-by: aonif <104995055+aonif@users.noreply.github.com>
|
@aonif, thank you for your interest in the Canton Development Fund! Your proposal needs a valid Tech & Ops Committee champion organization. The champion field is either empty, contains placeholder text, or names an organization that is not a current Tech & Ops Committee member. Per CIP-0100, all external proposals require a Tech & Ops Committee champion. Next steps:
If you need help finding a champion, reach out to SIGs or any Tech & Ops Committee member. This PR is being closed automatically. You are welcome to reopen it once a champion is confirmed. |
|
@aonif, your proposal is missing a Special Interest Group (SIG) label. Adding the right SIG label ensures the relevant domain experts can find and review your proposal, Check more about SIGs. Please add one of the following labels to your PR Description or include the label name in your proposal:
Not sure which one fits? Pick the closest match to your proposal's domain. |
|
The Digital Asset Splice team supports this proposal. The prioritized issues that this proposal would resolve matches a prioritized list built from feedback collected by the Digital Asset Splice team, and DA design team, from Super Validator operators. Further, SV Governance UX is a high priority for governance overall, given that there is an active CIP proposing to dramatically expand the number of SVs involved in votes. That raises the stakes for a well-designed, error-proofed, first-time-understandable UX. |
|
Reopened this pull request; please add me as Champion. |
| ## Development Fund Proposal | ||
|
|
||
| **Author:** Finoa Consensus Services GmbH | ||
| **Status:** Draft |
There was a problem hiding this comment.
| **Status:** Draft | |
| **Status:** Approved | |
| **Approved:** 2026-06-24 |
Development Fund Proposal Submission
Proposal file:
/proposals/2026-06-FCS-splice-sv-ui-ux-improvements.md
Summary
This proposal clears 18 open issues from the SV governance UI backlog in canton-network/splice, delivering a complete shared component library, polished governance pages and operator-facing functionality improvements. The work reduces the maintenance burden on the Splice core team, improves the daily experience of every SV operator on the network and demonstrates that the Development Fund can drive upstream code quality through external contribution.
Checklist
/proposals/Notes for Reviewers
The 18 in-scope issues were recommended and selected through the Splice contributor channel, so the scope is already aligned with the Splice maintainers. Estimates are based on Digital Asset's own day-level estimates as a reference, validated and confirmed by FCS's engineering team. Timeframes include a one-week maintainer review and acceptance allowance per milestone, following guidance from the Splice maintainer DA team that milestones should reflect work that is reviewed and accepted, not only submitted.