Skip to content

Comments

Feat/revocation integration and UI#25

Open
pranavkonde wants to merge 3 commits intoFatumayattani:mainfrom
pranavkonde:feat/revocation-integration-and-ui
Open

Feat/revocation integration and UI#25
pranavkonde wants to merge 3 commits intoFatumayattani:mainfrom
pranavkonde:feat/revocation-integration-and-ui

Conversation

@pranavkonde
Copy link
Contributor

This PR integrates the revocation functionality for the Storacha Multichain Checkpointer, updates the dashboard UI to support managing checkpoints, and improves the test page for better developer experience.

Key Changes

  • Hook Updates: Added nextCheckpointId and refetchNextCheckpointId to useStorachaCheckpointer.ts to enable dynamic fetching of checkpoint data.
  • Dashboard Enhancements:
    • Updated dashboard/page.tsx to display a comprehensive list of user checkpoints.
    • Added status indicators (Active, Revoked, Expired) and a Revoke action for each checkpoint.
    • Integrated Wormhole propagation options for revocations.
    • Added a statistics grid and manual refresh capability.
  • Test Page Improvements:
    • Enhanced test/page.tsx with a Storacha Configuration section for email and delegation proof management.
    • Added dedicated controls for testing checkpoint revocation.
    • Improved UI layout for better readability and testing flow.
  • Bug Fixes & Refactoring: Resolved linter errors related to type safety and potential null values in contract read results.

Verification

  • Verified dashboard checkpoint list fetching and status rendering.
  • Tested manual revocation flow with Wormhole propagation prompt.
  • Confirmed Storacha client initialization and space importing in the test page.
  • Validated the E2E flow remains functional after UI changes.

Closes #24

@Fatumayattani
Copy link
Owner

Thanks for the work here @pranavkonde . This is a substantial contribution and the UI improvements are thoughtful.

Before we can merge this, we need to pause on revocation and protocol versioning. This PR introduces new lifecycle semantics and implicit version 2 behavior that we have not finalized or documented yet, and it bundles protocol changes with UI in a way that’s hard to merge safely at this stage.

I’d like to revisit revocation post-MVP, or alternatively split this into smaller, scoped PRs. Happy to discuss next steps.

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.

Implement Checkpoint Revocation

2 participants