Skip to content

Allow adding the payment tx hash to token info applications under review - #3861

Merged
tom2drum merged 6 commits into
mainfrom
issue-3847
Nov 13, 2026
Merged

tom2drum merged 6 commits into
mainfrom
issue-3847

Conversation

@tom2drum

@tom2drum tom2drum commented Nov 10, 2026 •

Copy link
Copy Markdown
Collaborator

Description

Resolves #3847

A token info application under review (IN_PROCESS) was fully read-only, including the expedited-review payment transaction hash. Applicants who submit first and pay later had no way to add the hash. The admin service now has a dedicated endpoint for exactly that (blockscout/blockscout-admin#517), which updates only the payment tx without resetting the review.

  • New resource admin:token_info_application_payment_tx for PATCH /token-info-submissions/{id}/payment-tx.
  • In the IN_PROCESS status, when the instance has expedited review configured and the application has no payment tx yet, the payment hash field becomes editable and required, all other fields stay read-only, and the submit button reads "Update request" and sends the hash to the new endpoint. The existing onSubmit flow (list update, form close) is reused.
  • Once a hash is set it is read-only again and the button is disabled, mirroring the API's set-once rule (a different value is rejected with 400; only an admin can correct it).
  • Without expedited review configured, or in any other status, behaviour is unchanged.

Environment variables

None

Minimum API version

Admin RS microservice v1.5.3+ (ships blockscout/blockscout-admin#517; at the time of writing deployed only on staging).

Breaking or incompatible changes

None

Additional information

Decisions made during the task interview: single submit button with a changed label rather than a dedicated one; request body type inlined instead of publishing a beta @blockscout/admin-rs-types; UPDATE_REQUIRED applications keep the existing full-form PUT path. No demo deploy.

🤖 Generated with Claude Code

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@tom2drum tom2drum added chore backport Ship in the current patch line labels Nov 10, 2026

@tom2drum tom2drum left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛑 Blocked — 2 majors open

blocker 0 · major 2 · nit 0 · not anchorable 0

Axes: standards · correctness · jev · spec skipped (no spec)

— Reviewed by cursor (Grok 4.7)

… under review

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

@tom2drum tom2drum left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Cleared — 0 blocker, 0 major open

blocker 0 · major 0 · nit 0 · not anchorable 0

Axes: standards · correctness · jev · spec skipped (no spec)

— Reviewed by cursor (Grok 4.7)

tom2drum and others added 4 commits November 12, 2026 19:27
The spec resets the module registry through withEnvs, which main's ESLint
config (since the shared/isolated Vitest project split) only allows in a
file named *.isolated.spec.tsx.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Assert the submit button's loading state around the payment tx PATCH, the
error toast on a rejected hash, and the analytics Submit event on a new
application. Suppress the ConditionalExpression mutant on the `'id' in
result` guard: useFetch rejects on a non-ok response, so the guard only
narrows the Success | ResourceError type.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…and run it shared

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@tom2drum tom2drum removed the backport Ship in the current patch line label Nov 13, 2026
@tom2drum
tom2drum merged commit 0ca03a4 into main Nov 13, 2026
20 checks passed
@tom2drum
tom2drum deleted the issue-3847 branch November 13, 2026 07:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow adding the payment tx hash to token info applications that are in process

1 participant