fix(data): kerne description cites an audit as upcoming that published 2026-07-31, and the listed PSM is the retired one - #1176
Open
enerzy17 wants to merge 1 commit into
Conversation
…d 2026-07-31, and the live mint PSM was missing The description still said "has engaged Hexens for its first external smart-contract audit (fieldwork begins 2026-07-13)". That report published 2026-07-31 and is public. The blockchain list named 0x07eBb486 as the Peg Stability Module. It lost kUSD MINTER_ROLE on 2026-07-13 and is no longer the mint path. Adds the live module 0xaBDE1138 and the redeem reserve module 0xFf3025ec, and relabels 0x07eBb486 as retired.
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
1 participant
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.
Two corrections to
data/projects/k/kerne.yaml. I work on Kerne, and both of these are stale values I supplied myself in #1112.1. The description described the audit as upcoming. It published two weeks ago.
The record still reads "has engaged Hexens for its first external smart-contract audit (fieldwork begins 2026-07-13)". The Hexens report published 2026-07-31 and is public at https://hexens.io/audit-reports/kerne-protocol-july-2026 (10 findings, 0 critical, 2 high, 8 fixed in source and 2 acknowledged by design).
I have written "8 fixed in source" deliberately. Kerne's live vault bytecode predates those fixes, so a reader who takes "8 fixed" to mean "fixed on chain" would be misled. The replacement text points at https://kerne.fi/security/deployed-vs-source, which is where Kerne states that gap.
2. The listed Peg Stability Module is the retired one.
0x07eBb486e11bd217e6085eb5ab663e4517595993was labelledKUSDPSM v3 (Peg Stability Module). It is no longer the mint path: it lostMINTER_ROLEon kUSD on 2026-07-13, and the record has named it as the module ever since.Verifiable in one call each, on Base:
The role transfer is two adjacent transactions in block range 48591869 to 48591914:
RoleGrantedMINTER_ROLE to0xaBDE11380xcfde847381a64f1c061b8b6fd07574c0a0cd53a7c6d0a08ff1e99856bebd6e0bRoleRevokedMINTER_ROLE from0x07eBb4860xb83f61a6c856265b55d0ca63d1dcda5416b29d4d181d5cfa987c53198d5b5f60This PR adds
0xaBDE1138as the live mint module and relabels0x07eBb486as retired. It does not remove0x07eBb486, because that module still holds 995.003 USDC of the reserve and is still worth monitoring.It also adds the third module,
0xFf3025ec18e301855ab0f36ec6eca115a29a5fbc, which holds 85.885006 USDC of reserve. Listing two of the three modules while omitting the one that holds a live balance seemed like the wrong record to leave behind. All three are source-verified on Blockscout and BaseScan.Checks
src/resources/schema/project.jsonandblockchain-address.json. Only enum tags are used, andcontractis the only tag added.data/.+14 / -2. No other project touched.