Repository navigation
feat(admin): add timelock queue viewer (#1014) - #1064
Merged
Chucks1093 merged 1 commit intoSep 29, 2026
Merged
Conversation
|
@JerryOJJ Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Chucks1093
marked this pull request as ready for review
September 29, 2026 09:15
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.
Summary
Adds a timelock action queue panel to the admin dashboard for issue #1014.
Changes
Backend integration required
This client repository does not contain a timelock contract ABI, contract address/configuration, or the backend route implementation. The panel currently expects authenticated endpoints
GET /admin/timelock/actions/pending,GET /admin/timelock/actions/history, andPOST /admin/timelock/actions/:id/cancel. Queue records must includeid,type,params,eta,status, andcancellable; cancellation-window metadata may be supplied ascancellationDeadline. The cancel endpoint must enforce admin authorization and the on-chain cancellation window and submit the contract transaction. Marked draft until that API/contract integration is confirmed.Verification
pnpm vitest run src/services/__tests__/admin.service.test.ts src/components/admin/__tests__/TimelockQueuePanel.test.tsx(17 passed)pnpm lint(passes with two existing warnings inBatchTradePanel.tsx)pnpm build(passes)pnpm testcurrently has 137 failures in unrelated existing suites; 285 files pass.Closes #1014