Transparency before tokenization: why root64 publishes proofs before issuing tokens

Why does root64 publish proofs before issuing tokens?

Because a token is only as trustworthy as the asset behind it, and most RWA (real-world-asset) platforms ask investors to trust that asset before they can verify it. root64 reverses the order: it first makes the underlying Korean loan assets independently verifiable on a public blockchain, and only then — as a planned second phase — represents them as transferable tokens.

The principle is “transparency before tokenization.” Transparency is the foundation; tokenization is built on top of it, not in place of it.

What does “transparency first” actually record?

In its first phase, root64 records the cash transactions and investment balances of its loan pool on Ethereum, as an append-only log. “Append-only” means entries are added but never edited or deleted, so the on-chain history cannot be quietly rewritten after the fact.

This matters because of how this asset class is normally reported. In root64’s initial pool, conventional reporting runs on a periodic cycle — weekly net asset value (NAV) calculation and monthly reports. Between those reports, an investor has no independent way to check the state of the assets. Recording the actual movement of money on-chain, as it happens, replaces “wait for the next report” with “look at the ledger.”

The gap a periodic cycle leaves is not a hypothetical. The U.S. accounting regulator, the Public Company Accounting Oversight Board (PCAOB), has formally warned that even formal crypto “proof of reserve” reports “do not provide any assurance about whether the assets were used, lent, or otherwise became unavailable to customers following issuance,” “likely do not address the crypto entity’s liabilities,” and “are not equivalent or more rigorous than an audit” (PCAOB Investor Advisory, March 2023). A point-in-time report tells you the state of the assets at one moment; it says nothing about the days in between. An append-only record of the actual transactions is meant to close exactly that snapshot gap — not by reporting a balance, but by writing down each movement that produced it.

There is a second, more subtle problem with point-in-time proofs that the industry has converged on: a snapshot can be staged. Because a periodic attestation captures one moment, an entity can in principle borrow assets just before the verification window and return them after — a known vulnerability that has pushed the field toward real-time visibility into reserve changes, with continuous oversight replacing periodic snapshots (Chainlink — 7 Key Principles for Proof of Reserves, May 2025). An append-only ledger of actual cash movement is structurally harder to stage than a one-moment balance, because it records the flow, not just the level.

How do you know the on-chain data is true?

Putting data on a blockchain proves nothing by itself — what matters is who registered it and who verified it against an independent source. So root64 separates the two roles:

• Registration is done by the party closest to the asset: the originator (the lender supplying the loans, starting with 8percent) registers asset data; the special-purpose company’s fund administrator records cash transactions.
• Verification is done against external channels that the registrant does not control — property registries and Korea’s P2P central record-keeper, the Korea Financial Telecommunications & Clearings Institute (금융결제원, KFTC), for asset data, and bank APIs for cash transactions.

Crucially, the verification result itself is recorded on-chain — not just the data, but the check. Each verification logs its target, its channel, and one of three outcomes: match, mismatch, or inconclusive. Even a mismatch, and its later resolution, is written to the chain. The point of an honest transparency layer is not to show only clean numbers; it is to make the act of verification auditable, including when something doesn’t line up.

What is verified	Independent channel
Asset data (loan, collateral)	Property registry, P2P central record-keeper (KFTC)
Cash transactions	Bank API

Source: root64 data-verification model, as of June 2026.

No single party — including 8percent — is the sole source of truth. That is the design of the transparency layer root64 is building out in this first phase, channel by channel.

It is worth being precise about what “verification” means versus “audit,” because the words are often used loosely. Even best-in-class regulated issuers draw the line carefully. Circle, for example, publishes monthly USDC reserve attestations by a Big Four accounting firm under AICPA attestation standards, and frames them explicitly as attestations — third-party assurance that reserves are sufficient — not a comprehensive financial audit (Circle — Transparency, accessed June 2026). root64’s on-chain verification records are likewise verification, not an audit: they establish that the pool’s data was checked against an independent channel and what the result was. The difference root64 is building toward is where and how continuously that checking is recorded — on-chain and entry-by-entry, rather than as a periodic off-chain document.

Why not just issue a token and call it transparent?

Because a token is a claim, and a claim is not evidence. Issuing a token first puts the burden on the investor to trust the issuer’s representation of the asset; the token’s existence says nothing about whether the loan is performing, whether the collateral is real, or whether the cash actually moved.

The canonical illustration of why a “trust me” representation of off-chain assets is not enough is FTX. After it collapsed in November 2022, customers discovered that funds they believed were safely held had been misused; U.S. prosecutors charged a conspiracy to take more than $8 billion from FTX customers and funnel it to the affiliated trading firm Alameda Research, and a federal jury found founder Sam Bankman-Fried guilty on all seven fraud and conspiracy counts (Fortune — Sam Bankman-Fried verdict, November 2, 2023). The relevant lesson here is structural, not moral: customers had no independent way to verify, in between assurances, that the assets they were promised still existed and were where they were said to be. That is precisely the failure mode an asset-verification layer is meant to make visible.

root64’s view is that tokenization without a verification layer underneath simply moves an unverifiable claim onto a blockchain. Building the proofs first means that, by the time a token represents an investment, the thing it represents has already been made checkable by the investor — not just asserted by the operator.

This is also the direction regulation is moving. The U.S. GENIUS Act, signed into law on July 18, 2025, requires payment-stablecoin issuers to make monthly public disclosure of their reserve composition, with executive certification of those reports (Greenberg Traurig — GENIUS Act enacted, July 2025). That law governs U.S. stablecoins — a different instrument and jurisdiction from root64’s Korean-loan assets and planned Hong Kong unit structure — so it is backdrop, not a rule root64 operates under. But the direction of travel is unmistakable: recurring, independent reserve disclosure is becoming a baseline expectation rather than a differentiator.

What comes after transparency?

Tokenization. Once the verification layer is in place, root64 plans to represent investments as transferable on-chain units, issued through a Hong Kong vehicle to professional investors. That phase is planned and contingent on regulatory clearance; the vehicle is not yet formed, and it is not live today.

The sequence is deliberate: transparency is the trust foundation that every later stage — token issuance, onboarding additional originators, secondary transfer — is meant to stand on.

The wider market is independently converging on the same conclusion — that a token needs a verification layer beneath it — even for already-tokenized, blue-chip funds. On March 26, 2026, Securitize added an independent on-chain verification layer, Chronicle’s “Proof of Asset,” to BlackRock’s tokenized U.S. Treasury fund (BUIDL), a multi-billion-dollar fund. Chronicle publishes on-chain attestations covering valuation inputs, holdings composition, custody confirmation, and asset existence, sourced from custodians and administrators and consumable by both smart contracts and human auditors (The Block — BlackRock tokenized BUIDL fund taps Chronicle, March 26, 2026). Notably, that fund was tokenized first and had verification added later — the reverse of root64’s order. The comparison is not a claim that root64 is first or uniquely positioned; it is evidence that “a token alone is not proof” is an industry-wide conclusion, and that building the verification layer first is one coherent way to act on it.