Igra DAO adopts incident registry after KRC-20 exploit
A completed vote gives the DAO control of a public list of incident-linked addresses. The list cannot move funds, but services can use it when deciding whether a transfer needs review.
Igra’s DAO executed Proposal #17 on October 19. The proposal transfers ownership and governance of an on-chain Incident Registry to the DAO and funds a three-month pilot for an independent analyst with a 500,000 IGRA grant. It follows the September 20 KRC-20 indexer exploit, which affected tokens and liquidity in the Igra ecosystem.
The registry records addresses linked to incidents, with an on-chain reason pointing to public evidence. The proposal says the registry holds no funds and cannot move, freeze or confiscate assets. Its practical effect depends on whether a bridge or other service checks the list. Igra says its reopened Hyperlane routes screen outbound transfers against it and block transfers from listed addresses; balances on Igra itself are not frozen by that check. Read Igra’s bridge update.
Bridge payouts are a separate decision
Igra has said canonical iKAS-to-KAS exits resumed under a policy that releases the portion of a payout cleared by review and withholds amounts it attributes to the incident. In its October incident accounting, Igra reported that 20,500 iKAS had been withheld from bridge payouts. That figure is Igra’s account; KaspaNews has not independently audited every affected exit or the tracing decisions behind it.
The distinction between a wallet balance and a bridge payout matters. The bridge integration documentation describes a user-signed exit that burns iKAS on Igra before KAS is released on Kaspa. A smaller or delayed payout can therefore appear to a user as missing funds. It does not, by itself, establish whether the difference was a fee, a pending settlement or an incident-related withholding. An individual case requires both transaction records and the operator’s explanation.
Who can challenge a listing?
Proposal #17 appoints a community analyst to maintain the registry during the pilot and confirms K.A.T. Foundation as another listing and removal authority. The proposal says anyone may appeal a listing with evidence on the governance forum, that the analyst should respond within seven days, and that a DAO member can bring a rejected appeal to a vote. It also names mistaken listings and reliance on one analyst as risks. Read the proposal and its vote record.
The October vote is complete. The proposal expects a separate vote before the pilot ends if the DAO wants to continue it. Igra has also said it intends to involve the DAO in a plan for distributing recovered or withheld funds, subject to legal requirements. We could not verify a date or published text for that separate distribution vote as of October 25. Read Igra’s statement.
The unresolved reporting question is how a user learns that a payout has been flagged, what evidence supports the decision, and how quickly a mistake can be corrected. We will examine specific cases when the exit transaction, expected and received KAS amounts, and the operator’s response are available.