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 its proposals drew public comment this summer: the OCC's anti-money-laundering and sanctions rule for permitted payment stablecoin issuers, whose comment window closed 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 set out to put our position on the record with both agencies. One of the two got filed. Our FDIC comment went in by email to Comments@fdic.gov on July 23, 2026, per the ADDRESSES section of that proposal. The OCC comment was written and never submitted: its window closed on July 24, 2026 with nothing from us on the docket, and because the OCC takes comments only through regulations.gov, mail, or hand delivery, and accepts no late filings, there is no way to correct that after the fact. We would rather say that here than leave a page up that implies otherwise. This post is the position itself, which does not change with the docket it did or did not reach. 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 either letter, 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.
Update, August 13, 2026: one of these is now posted on a federal docket
Since this piece was first published, a third window opened and closed for us, and it is the one that produced a durable artifact. On August 9, 2026 we filed a comment on the joint Customer Identification Program proposal for permitted payment stablecoin issuers, RIN 1506-AB74, docket FINCEN-2026-0101. It is now publicly posted as comment FINCEN-2026-0101-0009, filed under the organization name Kerne Protocol, with comment tracking number msm-5xhi-wb4s. That is a government-hosted, permanently archived record carrying our name and our argument, on a domain we do not control and cannot edit or withdraw. We are pointing at it here because almost everything else that is credible about Kerne is published by Kerne, and this is not.
One mechanical note worth having, because it caused us to doubt our own filing for three days. A submitted comment does not appear on the public docket immediately; it goes for agency review first, and posting lags by several business days. On the day we filed, the docket showed six comments and none of them were ours. The proof of filing is the tracking number on the emailed receipt, not the listing. Ours posted on August 12, three days after it was received. If you file one of these yourself, save the tracking number and do not read an empty docket as a failed submission.
The letter is a joint filing by construction: the rule is one proposal carried by FinCEN with the OCC, the Federal Reserve Board, the FDIC and the NCUA, each under its own RIN, so a single comment to the FinCEN docket goes before all five agencies. It answers the proposal's Question 1 (a customer identification program cannot reach secondary transfers that an issuer never intermediates), Questions 3 and 4 (a redemption by someone who never onboarded should expressly count as a covered relationship rather than falling in a gap), and Questions 5 and 6 (verifiable credentials are worth recognizing as a method, not as a safe harbor). On the agencies' regulatory impact analysis, where they asked repeatedly for data from small issuers, we gave our own numbers: against roughly 1,111 dollars of reserves, the proposal's five-percent-of-reserves revenue proxy produces about 56 dollars a year, which is not a small estimate so much as a meaningless one, because the fixed cost of a compliance program does not shrink with the reserve base. The letter does not request an exemption. We deliberately did not ask for one.
A fourth window is open as we publish. The CFTC is taking comment until August 26, 2026 on extending standard futures to 24/7 trading and on perpetual contracts referencing physically delivered energy commodities, RIN 3038-AF75, docket CFTC-2026-1388. It is not a digital-asset rulemaking, and our standing in it is narrow and empirical: the Commission asks directly, at its Questions 40 and 42, whether a funding-rate mechanism developed in digital-asset markets can discover storage cost, convenience yield and seasonality for crude oil. We measured 4,320 consecutive hourly funding observations per instrument on the venue we actually use, and found the rate sitting at exactly the venue's administered 10.9500 percent default for 41.2 percent of ETH hours and 72.9 percent of HYPE hours, with ETH never once exceeding it. Our answer is that a mechanism which frequently is not discovering anything in the market it was designed for should not be assumed to discover physical carry by analogy. We take no position on whether the Commission should permit those contracts.
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 our OCC comment says, and why the OCC never received it
The reserve-traceability question is the one we have spent the year building for, so the comment we drafted for 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. The recommendation in that letter 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 the letter asks 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 that letter 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, the letter says plainly what a verifiable reserve does not do, which we come back to below.
What we told the FDIC, and the limit we put on our own argument
To the FDIC we made 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 asked 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. Both letters say that 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.
Where Canadian law now lands on this, since that is where the work is done
Publishing a federal filing raises your profile with exactly the readers most likely to ask the harder question underneath it, so we would rather answer it on the same page than wait to be asked. Kerne has not incorporated a company anywhere, which we say plainly on /team and in our terms, and the work is done from Canada. On March 26, 2026 Canada enacted its own stablecoin statute: the Stablecoin Act, S.C. 2026, c. 3, s. 600, carried in by Bill C-15, the Budget 2025 Implementation Act, No. 1. It defines "issue", in respect of a stablecoin, to mean "to create the stablecoin and to make it available for purchase, directly or indirectly, by a person in Canada". That is a definition written around an activity rather than around a company, and on its face it reaches what we do. We are not going to pretend otherwise, and we are not going to assert that we sit outside it.
Two things about it are worth a reader's attention, and the second is the one that actually bites. The first is that the Act is not in force. Section 97 provides that its provisions come into force on a day or days to be fixed by order of the Governor in Council; no such order has been made, the regulations that would supply a stablecoin's defining characteristics do not exist yet, and the framework is generally expected to begin operating in 2027. Section 15, which prohibits issuing a stablecoin unless your name is on the Bank of Canada's list of issuers, binds nobody today. The second is that the provision we would actually have to answer for is not the registration one. It is section 32: "An issuer must not, directly or indirectly, grant or pay to the holder of a stablecoin that the issuer has issued any form of interest or yield in respect of that stablecoin, whether in cash, digital assets or other consideration."
That is the same structural problem the GENIUS Act creates, in close to the same words, and we walked it in full in our issuer-paid versus strategy-passed-through piece. kUSD pays its holder nothing. Any yield lives in a separate staked token a holder opts into. Whether that separation survives the words "directly or indirectly" is genuinely unsettled under both statutes, it is being argued by people with far better standing than ours, and it is precisely the kind of question we just said we decline to answer on our own behalf on a federal form. So we are not offering a reading here and we are not claiming a clearance. We are doing the thing this whole post is about: naming the provision that applies to us before somebody else does, and leaving the reader able to check it against the statute rather than against our summary of it.
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. Neither letter tells the OCC or the FDIC how to classify kUSD, and neither claims 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 neither letter asks for either. The reason to file is simpler: the reserve-traceability standard the OCC asked whether to write is one we already run in production, and the honest way to say so is on the record, next to the agency's own question. We managed that with one of the two. 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, is complete: the final report published on July 31, 2026, with ten findings, none critical, eight fixed and two acknowledged. The deployed vault runs earlier bytecode than the reviewed commit, so those findings are live on the deployed contracts. We are at Genesis scale, and the staked yield we publish is a live model of the deployed book that sits below the 8 to 9.4 percent through-cycle band we published in full, because the deployed hedge is sized one for one against spot rather than levered. It is not a record of distributions, 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 asked 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, $999 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. Our FDIC comment was submitted by email to Comments@fdic.gov on July 23, 2026, per the ADDRESSES section of 91 FR 34171, so it is an email filing rather than a regulations.gov record; no comment from us was filed on the OCC docket before it closed. The FinCEN rule is Customer Identification Program Requirements for Permitted Payment Stablecoin Issuers, 91 FR 37234 (June 22, 2026), RIN 1506-AB74, docket FINCEN-2026-0101, a joint proposal of FinCEN, the OCC, the Federal Reserve Board, the FDIC and the NCUA, each under its own RIN; our comment was received August 9, 2026 under tracking number msm-5xhi-wb4s and posted August 12, 2026 as FINCEN-2026-0101-0009, which can be re-read at the source or through the regulations.gov API. The CFTC request for comment is 91 FR 38334 (June 25, 2026), RIN 3038-AF75, docket CFTC-2026-1388, whose comment period was extended thirty days to August 26, 2026 by CFTC press release 9271-26 of July 23, 2026; note that the Federal Register comments-close field still shows the original July 27 date, and regulations.gov is authoritative on an extended window. The funding figures are 4,320 hourly observations per instrument pulled from Hyperliquid's public fundingHistory endpoint over the 180 days ending July 25, 2026, and were independently re-pulled and reproduced to four decimal places on August 8, 2026. The Canadian statute is the Stablecoin Act, S.C. 2026, c. 3, s. 600, enacted by Bill C-15 (Budget 2025 Implementation Act, No. 1), Royal Assent March 26, 2026; the definition of "issue", section 15, section 32 and the section 97 coming-into-force provision are quoted from the consolidated text on the Justice Laws Website, and no order in council bringing the Act into force had been made as of this update. Nothing in this post is a legal conclusion about whether that Act applies to kUSD, and we do not offer one. 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. If you would rather have it run for you, there is a machine-signed instant read of an address you name, a human-reviewed version of the same read, a commissioned teardown like this one on any target, and an independent read of a counterparty you hold or allocate to. Rates are on each page. Attestation tooling, not an audit, and not a solvency opinion.