The GENIUS Act rules missed their statutory deadline on July 18, which we wrote up in a separate piece. The deadline slipping does not mean the rulemaking stopped. It is very much in motion, and two of the proposals are open for public comment as of this writing: the OCC's anti-money-laundering and sanctions rule for permitted payment stablecoin issuers, whose comment window closes July 24, 2026, and the FDIC's companion Bank Secrecy Act and sanctions rule, whose window closes August 4, 2026. A public comment period is a rare thing: for a few weeks, anyone can put a substantive position onto a permanent federal record, at no cost.
We are a small, early-stage issuer that publishes a live proof of reserves any person can recompute for themselves, so we are putting our position on the record with both agencies. This post is that position, said in public the same way we are saying it to the regulators. One boundary first, because it runs through everything below: we are not a permitted payment stablecoin issuer, we are not supervised by either agency, and we take no position, here or in the filings, on how kUSD should be classified under the Act. kUSD is a synthetic dollar, and the base token pays its holder no interest or yield. We comment on mechanics, because the reserve, disclosure, and recordkeeping questions these proposals raise are exactly the problem we build for.
What the two proposals actually ask
The OCC proposal (Docket OCC-2026-0463) carries out the GENIUS Act's instruction that the OCC set Bank Secrecy Act and sanctions standards for the stablecoin issuers it would supervise. Its anti-money-laundering core is deliberately thin: it mostly requires issuers to comply with the existing FinCEN rules at 31 CFR chapter X and the OFAC rules at 31 CFR chapter V, rather than writing a separate standard. The part worth a holder's attention is elsewhere, in the proposal's own requests for comment. Question 3 asks whether reserve assets must be traceable and identified at all times, and ties that to a monthly composition report. Question 4 asks about the institutions allowed to custody reserves and whether reserve-management fees must be disclosed to holders. Question 5 asks what protections should ensure holders can redeem or otherwise monetize the token. Those are reserve-transparency questions inside an anti-money-laundering rule, and they are the ones we can speak to from production.
The FDIC proposal (RIN 3064-AG29) is the parallel rule for the issuers it would supervise, and it is narrower on purpose: Bank Secrecy Act program, sanctions screening, customer identification, and recordkeeping. Its reserve and redemption rules were a different FDIC proposal whose comment window has already closed, so a comment on this one that wandered into reserve disclosure would be commenting on the wrong document. We kept ours where the rule actually is.
What we are telling the OCC
The reserve-traceability question is the one we have spent the year building for, so our comment on it is specific. A reserve held on a public blockchain can be published as a continuously updated, machine-readable report, signed with the issuer's key, that any holder recomputes directly from chain data in the days between the monthly composition reports. That makes traceable and identified at all times something a holder derives rather than something an issuer asserts, with no attestor required in the path. We run this today: an hourly signed proof of reserves that resolves to raw on-chain balances, which you can check at /verify and read at /api/por. Our recommendation to the OCC is to treat continuous, independently recomputable reserve disclosure as a way to meet a traceability standard, and to let the monthly composition report be published in a signed, machine-readable form rather than a static page.
We pair that with a limit we insist on for ourselves, because that edge is where a verification claim is easiest to overstate. On-chain verifiability reaches on-chain reserve assets. It does not reach a bank deposit or a Treasury bill sitting off-chain, which still depends on a custodian's word. So we ask the OCC to require issuers to disclose, inside the reserve report itself, which components are independently verifiable on-chain and which rest on a third-party attestation, so a reader can see exactly where verification ends. On fees and redemption our comment is briefer: disclose fees against a verifiable reserve figure rather than on a marketing page, and pair any redemption standard with a public breakdown of the reserve by liquidity tier, so a holder can see between reports whether the liquid tier actually covers near-term redemptions. And on the anti-money-laundering core, we say plainly what a verifiable reserve does not do, which we come back to below.
What we are telling the FDIC, and the limit we put on our own argument
To the FDIC we make a narrower point about records. Reserve movements, and in many designs the minting and redemption of the token itself, leave records on a public blockchain that are timestamped, signed, and tamper-evident by construction. Those are durable records in the exact sense a recordkeeping regime wants, because they cannot be quietly altered later and can be reproduced by anyone. We ask the FDIC to write its recordkeeping standard so that cryptographically signed on-chain records are recognized as capable of meeting record-integrity and retention goals.
We also argue against the overreach of our own point, because it is the one every crypto commenter is tempted into. On-chain records are pseudonymous. They show that value moved and when, not who moved it. They strengthen the recordkeeping and tracing side of the Bank Secrecy Act regime, and they do nothing for the identity side. The identity work has to happen through customer identification and screening at the points where fiat enters and leaves the system, and it cannot be assumed to follow from the fact that a blockchain is public. We say that to both agencies in as many words, because a filing that oversells on-chain transparency as a substitute for know-your-customer would be worse than no filing at all.
The thing we do not do
A comment letter is a permanent public record, and a regulator or a litigant can read it back to you years later. The single most valuable discipline in writing one, for a token like ours, is knowing what not to put in it. We do not tell the OCC or the FDIC how to classify kUSD, and we do not claim it sits outside any perimeter.
The reading we are declining to assert exists because of the Act's ban on yield. The GENIUS Act bars a permitted payment stablecoin issuer from paying the holder of the coin any form of interest or yield simply for holding it. That single line, which we walked in full in our issuer-paid versus strategy-passed-through piece, is why almost every yield-bearing dollar is built the way it is, ours included: the base coin pays nothing, and any yield lives in a separate token a holder opts into. On the prevailing legal reading, a delta-neutral synthetic dollar is not a payment stablecoin at all, because its issuer is not obligated to redeem it for a fixed sum, which would put it outside the yield ban. Forbes made exactly that argument about Ethena's USDe in June. But the same reasoning that keeps a synthetic dollar clear of the yield ban keeps it clear of the Act's protections, and the whole question is unsettled and untested. The market has been living in that gap for a while: back in 2025, Germany's BaFin ruled USDe an unauthorized token under the EU's MiCA regime and pushed Ethena to wind down its German entity and move issuance offshore, which we covered in our Ethena teardown. None of that is a place a small issuer should volunteer its own token into on a federal form. So we describe a verification model, and leave the classification alone.
Why a tiny issuer bothers to file
Not to lobby, and not to ask for anything. We are not seeking an exemption or a favorable classification, and the letters ask for neither. The reason to file is simpler: the reserve-traceability standard the OCC is asking whether to write is one we already run in production, and the honest way to say so is on the record, in the agency's own docket, next to its own question. Most of the comments a rulemaking like this draws come from the largest issuers and their counsel. There is room, and arguably a need, for the view from a small issuer whose entire pitch is that a holder should not have to trust any of us, and who built the thing that makes that literally true for the on-chain part of a reserve. Regulation sets what an issuer must show and on what clock. The layer we are describing is the one a holder can check between those checkpoints, which is where every reserve failure we have written up actually happened.
Where Kerne sits, and how to check it
We say where we stand so this is not an abstraction, and nothing here is an offer of any token to anyone. kUSD's collateral lives on Base and is readable with raw on-chain calls, and we publish an hourly proof of reserves signed with an EIP-191 key that you re-derive yourself against the chain at /verify and /api/por, with no attestor in the path. The honest boundary is named in the same breath. The delta-neutral hedge leg is currently flat rather than actively hedged. When the design hedges, that leg runs on Hyperliquid, a single venue, self-reported and signature-bound rather than independently re-derivable, and an independent attestation of it is being scoped. Our first external audit, by Hexens, delivered its initial report on July 20, 2026, with remediation underway and a final report still pending. We are at Genesis scale, and the staked yield is a live model inside the 8 to 9.4 percent through-cycle band we published in full, not a large realized distribution, and the realized on-chain figure today is far lower. Where kUSD ranks against the field on holder-side verifiability, including where it falls short, is in the synthetic-dollar scorecard, and our own open gaps are listed at /legible. Because yield claims decay faster than reserve claims, our advertised-versus-realized board is at the honesty index, with our own numbers first and, at the moment, worst.
If you issue a dollar token
The verifiable layer the OCC is asking about is already a product you can stand up. The GENIUS-readiness kit builds a hosted verify page for your token, scheduled machine-signed reads of your disclosed reserve addresses, and an embeddable freshness badge for your own site, live within five business days, $499 setup then $99 a month. It is not the statutory examination and it does not make you compliant with anything; it is the part your holders can check themselves. If you would rather have your existing disclosures read for gaps first, that is the Disclosure Integrity Audit, $499 flat.
Status is as of the publication date and nothing here is legal or investment advice, nor an offer of any token. The OCC rule is Permitted Payment Stablecoin Issuer Anti-Money Laundering / Countering the Financing of Terrorism and Sanctions Compliance Risk Management, 91 FR 37840 (June 24, 2026), Docket OCC-2026-0463, RIN 1557-AF55, with comments due July 24, 2026; the reserve, custody, fee, and redemption questions referenced are its Section II requests for comment (Questions 3 through 5) and proposed 12 CFR 15.11(a)(3) and 15.13(c). The FDIC rule is Bank Secrecy Act and Sanctions Compliance Standards for FDIC-Supervised Permitted Payment Stablecoin Issuers, 91 FR 34171 (June 5, 2026), RIN 3064-AG29, with comments due August 4, 2026. The yield prohibition is in the enacted GENIUS Act (Public Law 119-27) on govinfo.gov; the reading that a derivatives-backed synthetic dollar falls outside the payment-stablecoin definition is the prevailing practitioner interpretation, not settled law. Comments filed on either docket become part of the public record. Kerne's claims resolve to live endpoints: the hourly signed Proof of Reserves at /api/por/signed, its on-chain leg at /api/por, and the live risk surface at /api/risk-status. A /verify pass proves an attestation is authentic and fresh; it is not an audit and not a solvency opinion.
Verify it yourself
Run the same check on any reserve, or have it run for you.
Paste any issuer's signed attestation into the free verify tool and recover the signer, rehash the figures, and check freshness in your own browser. For a machine-signed, point-in-time read of an address you name, delivered on the page in about two minutes, the instant self-serve read is $29; a human-reviewed read is $149. A teardown like this one, commissioned on any target you name, is $499. An independent read of a counterparty you hold or allocate to is $2,500. Attestation tooling, not an audit, and not a solvency opinion.