Skip to content

Map HolderNotEligible and fix the token-pause copy in the dapp and console #340

Open

Description

@luchobonatti

User story / Problem statement

Currently, the dapp and the console map 304 for claim_redeem refusals and its pause copy says the token pause stops returns of escrowed shares. Once #321's contracts land, that refusal is 6073 HolderNotEligible and escrow returns ignore the pause.

Expected outcome

The dapp and the console name HolderNotEligible on the affected claim and describe the pause as a trading-only restriction.

Acceptance criteria

  • claim_redeem and cancel_redeem map 6073 HolderNotEligible
  • cancel_redeem maps 6068 for a delisted holder; no 304 mapping remains for vault calls
  • Token pause copy in emergency.ts and TransactionModal.tsx says it stops holder transfers only; mints, burns, escrow moves and legal transfers continue
  • Copy for each code lives in one place, shared with Show investors the allowlist and freeze outcomes #304

Technical notes

  • claimRedeemContractErrorReason in TransactionModal.tsx maps 304 today
  • 6073 = HolderNotEligible: a delisted holder's zero-asset claim, or a return the compliance rules refuse

Additional context

Follow-up to #264 / #321.

Activity

  1. changed the title [-]Map HolderNotEligible and fix the token-pause copy in the console[/-] [+]Map HolderNotEligible and fix the token-pause copy in the dapp and console[/+] on Oct 23, 2026
  2. self-assigned this
    on Oct 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions