Research and primers on Korean alternative credit, tokenization structure, and on-chain proofs — from root64, the RWA platform of 8percent.https://root64.io/blog/https://root64.io/blog/bankruptcy-remoteness-and-investor-funds/https://root64.io/blog/bankruptcy-remoteness-and-investor-funds/In root64's structure, the company that originates the loans never holds or controls investor money. The assets sit in a separate Korean SPC, and the cash moves through independent parties. Here is how that separation works, and why it matters.Fri, 19 Jun 2026 00:00:00 GMTIn root64's structure, 8percent originates and services the loans but never holds investor funds, and its staff cannot access the Korean SPC's bank accounts. The loan assets sit in a separate, bankruptcy-remote Korean SPC, isolated from 8percent's corporate risk. Each step of the cash flow is handled by an independent party — never the operator alone. ## Why does root64 never hold investor funds? Because the company that originates the loans is deliberately kept away from the money. In root64's structure, 8percent — the regulated Korean P2P lender that originates and services the loans — does not hold or move investor funds, and its own staff cannot directly access the Korean special-purpose company's bank accounts. The cash is handled by separate, independent parties at each step. This is the single most important property of the structure, and it is easy to underrate. An investor's first risk in any real-world-asset (RWA) platform is not the loan defaulting; it is the operator misusing or losing the money before the loan ever has a chance to perform. root64's answer to that risk is structural: it removes the operator's ability to touch the funds in the first place. This post is about that separation — who holds the assets, who controls the cash, and why those are kept apart. The related question of *where the assets legally sit* — the bankruptcy-remote Korean SPC — is covered in [how root64 holds Korean loan assets](/blog/how-root64-holds-korean-loan-assets). Here the focus is narrower: the flow of money, and the principle that no single operating party both controls the assets and controls the cash. ## What is bankruptcy remoteness? Bankruptcy remoteness means structuring the assets so that they survive the failure of the company that created them. In root64's case, the loan assets are held by a Korean special-purpose company (SPC) — a separate legal entity whose only job is to hold those assets — rather than by 8percent. Because the SPC is legally distinct from 8percent, its assets are not part of 8percent's estate, so 8percent's creditors cannot reach them if 8percent fails. A special-purpose company is an entity created to do one narrow thing and nothing else. That single purpose is what makes isolation credible: with no other business and no other creditors of its own, the assets inside it are insulated from the risks of the company that originates and services the loans. The point of that isolation is precise. It lets an investor take on the credit risk of the underlying loans only — not the credit risk of the operator that originated them. In structured finance this is the recognized investor benefit of a true asset isolation: once assets are genuinely isolated, an investor "can rely primarily on the credit risk of the underlying assets and their obligors, rather than the originator's creditworthiness," as the law firm Lucosky Brookman summarizes the doctrine ([Understanding Structured Finance Opinions: True Sale and Non-Consolidation](https://www.lucbro.com/news/understanding-structured-finance-opinions-true-sale-and-non-consolidation/), published 16 Apr 2024). root64's Korean SPC is built to fall within the categories of asset-holding entity that Korean law recognizes for this purpose; the design goal is to clear that "beyond the reach of the originator's creditors" bar. ## How is the operator kept away from the money? By splitting the roles so that the party closest to the loans is never the party that controls the cash. In root64's structure, 8percent's role is limited by design to two functions — originating the loans and servicing them (collection and management) — and explicitly excludes holding investor funds. The administration of the SPC's bank accounts is carried out by a separate, independent fund administrator, not by 8percent. This is not a courtesy arrangement; it is the recognized way that asset isolation is held in place. A bankruptcy-remote vehicle does not have its own employees and instead uses a servicer under a servicing agreement to collect cash on the assets — and that servicer is often the originator. What keeps the structure sound is a set of constraints called separateness covenants, which require the entity to maintain separate books, records and accounts, conduct business in its own name, and not commingle its assets with another entity's. Where those covenants break down — where an SPV and its sponsor "shared bank accounts, ignored corporate formalities... or were so intertwined that creditors treated them as a single economic unit" — a court can collapse the two together under the doctrine of substantive consolidation ([Lucosky Brookman, True Sale and Non-Consolidation](https://www.lucbro.com/news/understanding-structured-finance-opinions-true-sale-and-non-consolidation/), published 16 Apr 2024). In other words, operational separation is not optional decoration on top of legal separation; it is what makes the legal separation hold. The concrete consequence in root64's case is blunt: 8percent's staff cannot directly access the SPC's bank accounts. That is a structural constraint on what the operator is able to do, not a promise about how it intends to behave — and the difference between those two is the whole point. ## Who controls the cash at each step? A different, independent party at every step — never the operator alone. The principle is that no single entity both controls the assets and controls the cash. Tracing the money makes the separation concrete. | Stage | Who controls the cash | Role of 8percent | |---|---|---| | Loan origination and servicing | 8percent acts as servicer; borrower repayments are collected per the servicing agreement | Originator and servicer — does not hold investor funds | | Holding and administering the SPC accounts | Independent fund administrator (a third-party accounting firm in the current phase) | No direct access to SPC bank accounts | | Asset holding | Korean SPC (separate legal entity) | Legally distinct from 8percent | *Source: root64 business structure, entity roles and fund flow, as of June 2026.* Read down that column on the right: at no stage does 8percent both hold the assets and control the money. The originator originates; an independent administrator handles the accounts; the assets sit in a separate entity. Splitting these functions is what lets root64 say that no single party — including 8percent itself — is the sole point of control over investor funds. ## Why does separating who holds the money matter so much? Because the most damaging failures in this market came not from assets going bad, but from one party controlling both the customer assets and the cash, and then commingling them. Separating those roles removes that single point of control by design rather than by trust. The reference case is FTX. The U.S. Commodity Futures Trading Commission obtained a $12.7 billion judgment against FTX and its affiliated trading firm Alameda Research, after finding that, while FTX represented that it segregated customer assets from its own, in reality "customer funds were commingled and misappropriated" ([CFTC Obtains $12.7 Billion Judgment Against FTX and Alameda](https://www.cftc.gov/PressRoom/PressReleases/8938-24), published 8 Aug 2024). The structural lesson — separate from the criminal one — is that customers had no independent party standing between the operator and their money. One entity controlled the assets, controlled the accounts, and represented that the two were separate. They were not. That failure mode is exactly what separation is meant to foreclose. The principle that an intermediary's own money must be held apart from its clients' money is not a crypto novelty; it is a long-standing pillar of investor protection, reflected in international securities regulation, which treats the segregation of client assets from the firm's own assets as a baseline safeguard ([IOSCO — Recommendations Regarding the Protection of Client Assets, Final Report](https://www.iosco.org/library/pubdocs/pdf/IOSCOPD436.pdf), published Jan 2014). root64's structure applies the same idea through entity design: the operator is not trusted to keep the assets separate — it is structurally prevented from holding them at all. ## What about the planned Hong Kong tokenization tier? The same separation principle carries into the planned tokenization phase, but that tier is not yet formed. root64 plans to add a Hong Kong vehicle above the Korean SPC to issue tokenized units to global professional investors; any token issuance through it is contingent on regulatory clearance, and it is not live today. (For how the verification layer is being built before tokenization, see [transparency before tokenization](/blog/transparency-before-tokenization).) In that planned design, the separation of cash control is preserved rather than relaxed. The trust's bank accounts would be held in the name of an independent trustee — not 8percent and not root64 — so that the party raising and holding capital is again distinct from the operator that originates the loans. On-chain records in the transparency layer would be signed by an independent trustee, keeping the act of recording separate from the operator as well. The cross-border shape of that plan is a standard pattern, not a novel one: keep the assets in a local asset-holding vehicle onshore in Korea, and connect outside capital through a separate vehicle, with an independent party controlling the cash at each layer. The thread running through every layer — current and planned — is the same: the company that makes the loans never holds the investor's money. ## Does bankruptcy remoteness make the investment safe? No, and it is important to be exact about what it does and does not do. Bankruptcy remoteness isolates the assets from the operator's corporate risk; it does not remove the credit risk of the loans themselves. The underlying assets are loans, and loans can be repaid late or not at all. (For what the assets actually are, see [Korean private credit explained](/blog/korean-private-credit-explained).) What the structure changes is *which* risk an investor is exposed to. Without isolation, an investor in an operator's product is exposed to both the loans' performance and the operator's solvency and conduct. With isolation, the operator's solvency and conduct are taken off the table as much as the structure allows, leaving the credit risk of the loans — which is the risk an investor actually intends to take. That is the entire purpose of bankruptcy remoteness: not to make a loan risk-free, but to make sure that the only risk an investor carries is the one they signed up for.https://root64.io/blog/how-root64-calculates-nav/https://root64.io/blog/how-root64-calculates-nav/A methodology walkthrough of how root64 computes net asset value for its Korean loan pool — a once-daily batch, forward pricing for deposits and withdrawals, expected-credit-loss provisioning, and on-chain inputs an auditor can recompute. No live figures, just the method.Fri, 19 Jun 2026 00:00:00 GMTroot64 computes NAV once daily in a batch. It sums four asset lines (loan principal, accrued interest, cash, and an operator-advance claim), subtracts an expected-credit-loss allowance and other liabilities, and divides by total units. Deposits and withdrawals are priced forward — at the next batch's NAV, not the prior one. Every input is written on-chain so an auditor can recompute the result. ## How often does root64 calculate NAV, and what is the basic method? root64 calculates net asset value (NAV) once per day, in a single batch run at a fixed daily cut-off. NAV is the value of everything the pool owns, minus what it owes, divided by the number of units outstanding — the per-unit number an investor would use to value a position. This article is about the *method*, not the result. It contains no live NAV, no yield, and no performance figures, and it is not meant to. Where a number appears, it is an illustrative placeholder to show the arithmetic. What follows is how the calculation is structured, why it runs the way it does, and how each input is written down so that someone outside root64 can recompute it. The pool in question is root64's first Korean loan pool. root64 is the real-world-asset (RWA) platform built by 8percent, an FSC-licensed online investment-linked finance company (P2P lender) in Korea. A Korean special-purpose company holds the loan assets; for how that holding structure works, see [how root64 holds Korean loan assets](/blog/how-root64-holds-korean-loan-assets). This post picks up at the next question: given those assets, how is the pool's per-unit value computed each day? ## What goes into the NAV calculation? NAV is built from a small, fixed set of inputs: a few asset lines added together, a couple of deduction lines subtracted, and a unit count to divide by. root64 separates the pool's assets into four distinct lines rather than collapsing them into one "total assets" figure, because each line has a different source and a different way of being verified. The four asset lines are: | Asset line | What it represents | |---|---| | Loan principal outstanding | The principal balance of the loans the pool holds, net of any write-downs | | Accrued interest | Interest that has been earned over time but not yet collected | | Cash balance | Cash sitting in the special-purpose company's bank accounts | | Operator-advance claim | The pool's claim on funds advanced to the originator's deposit account, carried at face value | *Source: root64 pool accounting model, as of June 2026. Line labels are descriptive.* From the sum of those four, two deduction lines are subtracted — an **expected-credit-loss allowance** (covered below) and **other liabilities** such as accrued fees and operating costs. The result is the pool's net value. Dividing by the total number of units outstanding gives NAV per unit. Two design choices in that list are worth pausing on. First, the four asset lines are kept separate so that a movement of money *within* the pool — say, cash being advanced and turning into a loan — changes which line holds the value but leaves total assets unchanged. NAV only actually moves on a few events: money entering or leaving the pool, interest accruing with the passage of time, and loss provisions or write-downs being adjusted. Everything else is value changing form, not changing amount. Second, every one of these inputs is recorded on-chain at each calculation, which is what makes the whole figure independently checkable. More on that at the end. ## What is forward pricing, and why does root64 use it? Forward pricing means a deposit or withdrawal is settled at the *next* NAV that gets computed — not at a NAV that was already known when the order arrived. An investor putting money in today does not get yesterday's published per-unit price; they get the per-unit price struck at the next daily batch, after that day's assets have been measured. The reason is to remove a specific, well-understood unfairness. If units were issued at the last *known* NAV, someone who could see during the day that the pool's assets had moved could time a deposit or withdrawal to convert at a stale, advantageous price — diluting everyone else. By deferring the conversion to a NAV that has not yet been computed when the order is placed, forward pricing makes that timing game impossible: you commit before you can know the price. This is not a root64 invention. It is the same principle behind the U.S. Securities and Exchange Commission's forward-pricing rule for mutual funds, Rule 22c-1, which requires funds to transact at "the current net asset value... next computed after receipt" of a purchase or redemption order ([SEC — Amendments to Rules Governing Pricing of Mutual Fund Shares](https://www.sec.gov/rules-regulations/2003/12/amendments-rules-governing-pricing-mutual-fund-shares), accessed June 2026). root64 applies the same logic to an on-chain pool. Concretely, the two halves of a deposit are handled at different times: 1. **The cash is recorded immediately.** When money actually moves, the cash transaction is written to the on-chain ledger right away, at the real time of the transfer. The pool's cash balance reflects it at once. 2. **The unit conversion waits for the next batch.** The number of units that cash buys is *not* struck on the spot. It is calculated at the next daily NAV batch, using that batch's per-unit value. Between those two moments, the position is shown as "pending" — the cash is in, but the unit count is not yet final. For an investor this means up to roughly a day before units are confirmed, which is an accepted trade-off for an institution-facing product and consistent with how this asset class operates in practice. (At the very first batch, when no units exist yet, root64 strikes units at par value — a per-unit value of 1.0 — matching the standard fund convention of launching at NAV = 1.) ## How does expected credit loss get into NAV? Expected credit loss (ECL) is a forward-looking estimate of likely future losses on the loans in the pool, and root64 subtracts it from gross assets before computing per-unit value. The point is to reflect, in NAV, an allowance for losses that have not yet occurred but are reasonably expected — rather than waiting for a loan to actually default before recognizing any hit. This mirrors the accounting standard the rest of the financial world has moved to. Under IFRS 9, impairment is measured with a forward-looking expected-credit-loss model in which, in the standard-setter's framing, "it is no longer necessary for a credit event to have occurred before credit losses are recognised" ([PKF Littlejohn — IFRS 9 expected credit losses: an overview](https://www.pkf-l.com/insights/ifrs-9-expected-credit-losses-an-overview/), accessed June 2026). IFRS 9 structures this as a three-stage model that escalates the provision as a loan's credit quality deteriorates. root64's ECL line is the same idea applied to its pool: a provision that anticipates loss, not one that only books it after the fact. Mechanically, the ECL figure is produced **off-chain**, by a credit model, and then committed on-chain as one of the NAV inputs. Two things follow from that: - **It is a deduction, so it lowers NAV.** Provisioning reduces reported per-unit value relative to a no-provision figure. That is the intended direction — it is more conservative to carry an allowance than to mark assets as if every loan will be repaid in full. - **The method itself has to be auditable, because the number is a model output.** A figure that comes from a model is only as trustworthy as the documented methodology behind it. So each NAV snapshot also records a **version tag** for the ECL methodology in use. If the model's method or parameters change, the version is bumped, which lets anyone reproduce a past NAV under exactly the methodology that applied at the time — rather than silently re-scoring history with a newer model. One honest limitation worth stating: in its current phase, root64 commits ECL as a single combined allowance across the pool rather than breaking it out asset-by-asset. The credit model computes finer-grained components beneath that, but the on-chain figure is the pool-level total for now. A per-asset breakdown is a later-stage refinement, not something the current calculation exposes. ## How can an outsider check the NAV calculation? By recomputing it. Every input to the daily NAV — the four asset lines, the loss allowance, the other-liabilities line, the unit count, and the resulting per-unit value — is written to an on-chain record at each batch. Because the formula is fixed and public (sum the asset lines, subtract the deductions, divide by units), anyone reading those inputs can run the same arithmetic and confirm that the published per-unit figure was produced correctly from them. That is a deliberately narrow and honest claim. Recomputability proves the *math* was done right given the inputs. It does not, on its own, prove the inputs are *true* — that the cash balance really sits in the bank, that the loans really exist, that interest really accrued. Those are separate questions, and they are the job of root64's verification layer, which checks asset and cash data against independent external channels and logs the result — including mismatches — on-chain. The NAV record tells you the calculation is internally consistent; the verification records tell you whether the numbers feeding it have been checked against the outside world. For how to read both kinds of record field by field, see [how to read root64's on-chain proofs](/blog/how-to-verify-root64-on-chain-proofs). This division is the whole reason root64 publishes the inputs and not just the answer. A platform that posts only a single NAV number is asking to be trusted; a platform that posts every input and the formula is asking to be *checked*. That sequencing — make the assets verifiable first, then build on top — is the principle behind [transparency before tokenization](/blog/transparency-before-tokenization). A few properties of the on-chain NAV record make the recompute practical rather than theoretical: - **The inputs and the output travel together.** Each daily record carries the full input set alongside the per-unit value it produced, so a checker never has to reconstruct what numbers went in. - **A capital-erosion case is signaled explicitly.** If deductions ever exceed assets, the per-unit value is floored at zero and a distinct on-chain signal is emitted, so an observer can tell "no units issued yet" apart from "the pool's value has been impaired" — two situations that would otherwise both look like a zero. - **The history is append-only.** NAV records are added but never edited or deleted, so a past day's calculation cannot be quietly restated; a correction goes forward as a new entry, leaving the original visible. ## What this method does — and does not — promise The method above is designed to do three things: value the pool conservatively (forward-looking loss provisioning, par-value launch), price fairly across investors (forward pricing, no stale-price timing), and make the result independently checkable (every input on-chain, a fixed public formula, append-only history). What it does not do is change the nature of the asset. The underlying instruments are loans, and loans carry credit risk; a careful NAV methodology makes the state of the pool legible and conservative, but it does not remove risk or guarantee any outcome. NAV can fall as well as rise, and an allowance for expected loss is an estimate, not a floor. Nothing in this calculation is a promise of return, and past or modeled figures are not indicative of future results. That is the point of describing the *method* in public rather than advertising a number. A figure invites you to trust it. A method invites you to check it — and root64's NAV is built, line by line, to be checked.https://root64.io/blog/how-stablecoin-subscriptions-flow-into-korean-spc/https://root64.io/blog/how-stablecoin-subscriptions-flow-into-korean-spc/A global investor subscribes in stablecoins, but the underlying assets are won-denominated Korean loans. This walks through the designed money path — on/off-ramp, FX, and settlement — that connects a stablecoin subscription to a Korean SPC acquiring loan receivables, and what is live versus planned.Fri, 19 Jun 2026 00:00:00 GMTIn root64's design, a professional investor subscribes in USDT or USDC; an external OTC desk converts the stablecoin to fiat dollars off-chain, so only fiat reaches the bank account; dollars are converted to Korean won and remitted to a Korean SPC under prior Bank of Korea notification; the SPC then acquires the right to receive principal and interest. The Hong Kong tier that issues units is planned, not yet formed. ## How does a stablecoin subscription end up as a Korean loan asset? Not in a single transfer. A global investor's subscription starts as a stablecoin balance on a public blockchain, but the asset it is meant to fund is a won-denominated Korean loan held by a Korean entity. Bridging those two worlds is a designed sequence of steps — an off-ramp from crypto to fiat, a currency conversion from dollars to Korean won, a cross-border remittance, and finally the acquisition of a loan receivable inside Korea. Each step is handled by a distinct party, and the crypto, the dollars, and the won never sit in the same place. This post walks through that money path as it is designed to work. An important caveat up front: the offshore tier that would receive subscriptions and issue tokenized units is a planned Hong Kong vehicle, not yet formed, and any issuance through it is contingent on regulatory clearance. What follows is the designed steady state, not a description of a live, generally available product. The Korean asset-holding side is live today, and a pilot has tested the end-to-end connection; the broad subscription product is on the roadmap. For the legal reason the assets must stay in Korea, see [how root64 holds Korean loan assets](/blog/how-root64-holds-korean-loan-assets). ## What is the full path, step by step? The subscription moves through four stages: stablecoin in, off-ramp to fiat, FX and cross-border remittance, then acquisition of the Korean loan receivable. The table below is the whole journey at a glance; the sections after it explain why each step exists and who performs it. | Stage | What happens | Who handles it | What changes form | |---|---|---|---| | 1. Subscription | Professional investor pays USDT/USDC to the offshore vehicle and receives units | Investor → offshore vehicle (planned) | Stablecoin leaves investor's wallet | | 2. Off-ramp | An external OTC desk converts the stablecoin to fiat dollars off-chain | External OTC desk | Stablecoin → USD | | 3. FX + remittance | Dollars are converted to Korean won and remitted to the Korean SPC, under prior Bank of Korea notification | Offshore vehicle's trustee → Korean SPC | USD → KRW, offshore → onshore | | 4. Asset acquisition | The SPC uses the won to acquire the right to receive principal and interest on Korean loans | Korean SPC | KRW → loan receivable | *Source: root64 business structure, investment cash-flow scenario, as of June 2026.* The design principle running through all four stages is separation: the entity that receives the subscription is not the entity that holds the assets, the crypto-to-fiat conversion happens outside the banking rails entirely, and no single party both controls the assets and controls the cash. That same separation is what makes the [bankruptcy-remote Korean SPC](/blog/how-root64-holds-korean-loan-assets) work, and it carries through the whole money path. ## Stage 1: how does the subscription enter the structure? A professional investor subscribes by paying a stablecoin — USDT or USDC — to the offshore vehicle and receiving units in return. A "unit" here is a participation in the offshore pooled vehicle; in the planned design it takes the form of an on-chain token, so holding the token is holding the unit. The unit is the investor's claim; it is not itself the Korean loan. This is the only stage at which crypto is involved on the investor's side, and it is restricted to professional investors through private placement — there is no public offering and no retail product. The offshore vehicle that would receive these subscriptions is the planned Hong Kong tier. It is not yet formed, so in the live structure today this stage runs through a pilot arrangement rather than a generally available subscription channel. For how the offshore tier fits the broader access question, see [how foreign investors access Korean loan assets](/blog/how-foreign-investors-access-korean-loan-assets). ## Stage 2: why does the stablecoin get converted to fiat before anything else? Because the receiving bank account only ever holds fiat. In the design, an external OTC (over-the-counter) desk converts the subscribed stablecoin into fiat dollars off-chain, and only those dollars are deposited into the vehicle's bank account. An OTC desk is a venue that executes large crypto-to-fiat trades directly between two parties rather than on a public exchange order book — the standard institutional route for converting stablecoins to currency at size without on-chain congestion or price slippage ([StraitsX, How Institutions Use Stablecoins for Large Block Trades](https://www.straitsx.com/blog-post/stablecoin-large-block-trades), accessed 2026-06-19). Isolating the crypto touchpoint at the OTC desk is deliberate, and it solves a concrete banking problem. Banks are often reluctant to maintain accounts for entities that directly hold or transact in crypto. By keeping the conversion outside the banking rails, the vehicle's bank sees only fiat moving in and out — a conventional fiat account from the bank's perspective, with no crypto exposure on the books. The stablecoin is converted before it ever reaches a bank, and the Korean SPC further down the chain never touches crypto at all. This off-ramp pattern is itself conventional. A stablecoin off-ramp converts on-chain dollars back into fiat and settles them into traditional bank accounts, handling the exchange and the associated compliance checks in between ([Modern Treasury, What is a Stablecoin On-Ramp and Off-Ramp?](https://www.moderntreasury.com/learn/stablecoin-on-ramp-and-off-ramp), accessed 2026-06-19). What is specific to this design is *where* the off-ramp sits: at the very front of the chain, so that everything downstream — the bank account, the FX conversion, the remittance to Korea — operates entirely in fiat. ## Stage 3: how do offshore dollars become Korean won inside Korea? Through a currency conversion and a cross-border remittance that follows Korea's foreign-exchange rules. The fiat dollars in the offshore vehicle's account are converted to Korean won and remitted to the Korean SPC's account inside Korea. Because this is an inbound cross-border movement of funds into Korea, it is made under prior notification to the Bank of Korea (BOK) — the country's central bank — as required by Korea's foreign-exchange framework. This step exists because of a currency mismatch that cannot be wished away: the subscription is denominated in dollars (after the off-ramp), but the underlying assets are won-denominated Korean loans. Something, somewhere, has to convert dollars to won — and that introduces both an FX cost and currency risk, which the investor bears. It is not optional friction; it is the unavoidable consequence of connecting offshore capital to a local-currency asset. It also has to respect Korea's capital-flow rules rather than route around them. Korea's Foreign Exchange Transactions Act governs cross-border payments and certain capital movements, and the general principle is that capital transactions are reported before they are conducted — the Bank of Korea must be notified of relevant cross-border fund movements, and where a required report is not made, the related payments cannot lawfully proceed ([Bank of Korea, Foreign Exchange System — Relevant Legislation](https://www.bok.or.kr/eng/main/contents.do?menuNo=400187), accessed 2026-06-19). Designing the remittance around that notification requirement, rather than treating it as an afterthought, is part of what keeps the structure compliant on the Korean side. The deeper reason a non-resident cannot simply wire money in and buy loans directly is covered in [how foreign investors access Korean loan assets](/blog/how-foreign-investors-access-korean-loan-assets). ## Stage 4: how does the won actually become a loan asset? The Korean SPC uses the remitted won to acquire the right to receive principal and interest (원리금수취권) on Korean loans — the economic right to a loan's repayments. The SPC participates as a qualified transferee in the market for these receivables, taking a position in them the way other eligible institutional investors do, rather than having assets simply handed down to it. This is the moment the subscription stops being cash and becomes a loan asset. The right to receive principal and interest is the precise legal object the SPC holds, and it is distinct from owning the loan contract itself. It is worth understanding on its own terms; we cover it in [the right to receive principal and interest](/blog/right-to-receive-principal-and-interest). What matters for the money path is that the won arriving from offshore is converted, at this final stage, into a Korean-law asset held by a Korean entity — exactly the kind of asset a non-resident could not have bought directly. ## How does the offshore capital connect to the SPC's pool — does the vehicle buy the loans? No. In the planned design the offshore vehicle does not buy Korean loan receivables outright from offshore — Korean rules restrict who those receivables can be transferred to, and a foreign vehicle is not a qualified transferee. Instead, the connection is built as a bond issuance plus security. The Korean SPC privately issues a foreign-currency-denominated bond (외화표시채권) offshore, and the offshore vehicle subscribes to it. The bond carries no fixed coupon; its return tracks the net performance of the SPC's loan pool, on a limited-recourse, pass-through basis. "Limited recourse" means the bondholder's claim is satisfied only out of the SPC's assets; "pass-through" means the SPC passes the principal and interest it collects through to the bondholder. To protect the offshore side, the SPC pledges the loan receivables it holds as security for that bond. So the SPC holds the assets and owes the bond; the offshore vehicle provides the capital and holds the security interest. This issue-and-pledge shape is what lets capital connect to the economics of Korean loans without the receivables themselves having to leave a qualified Korean holder. It is a designed feature of the planned offshore tier — not a step that is operating in a generally available form today. There is also a tax reason for connecting capital through a bond. Interest on a foreign-currency-denominated bond issued offshore by a Korean company can be exempt from Korean withholding tax for non-resident holders under Article 21 of Korea's Restriction of Special Taxation Act (조특법) — so the interest the SPC pays can reach the offshore vehicle without a Korean withholding deduction along the way. That treatment is contingent on the issuance genuinely qualifying as an offshore one and on tax sign-off, but it is a meaningful reason the structure connects capital through a bond rather than through a plain cross-border loan. ## What does this money path look like on-chain? In root64's transparency layer, the cash legs of this path are recorded on a public blockchain as they happen, so an investor can see the movement of money rather than waiting for a periodic report. The seeding of a pool and an investor's deposit into the SPC's account are recorded as distinct on-chain cash-flow entries, and the SPC's accounts are themselves split — an investment account that receives subscriptions and an operating account that funds lending — so the path from "subscription received" to "money put to work" is visible step by step. A few guardrails are worth stating plainly. Recording cash flows on-chain does not mean the chain controls the money: actual bank transfers from the SPC's accounts are executed by the SPC's bank, and the authoritative confirmation of each SPC-side cash movement is signed on-chain by an independent trustee against the bank's own records. Putting the data on a blockchain is not, by itself, proof — what makes it meaningful is that an independent party attests to it and that external checks are logged alongside it. We explain how that verification works in [how to verify root64's on-chain proofs](/blog/how-to-verify-root64-on-chain-proofs), and why the verification layer is built before tokenization in [transparency before tokenization](/blog/transparency-before-tokenization). ## What is live today, and what is still planned? The Korean asset-holding side of this path is live: a Korean SPC holds the loan receivables today, and a pilot has tested the connection from offshore capital through to the Korean assets end to end. The full subscription flow described here — a generally available stablecoin subscription into an offshore vehicle that issues units and subscribes to the SPC's bond — depends on the planned Hong Kong tier, which is not yet formed and is contingent on regulatory clearance. | Element of the path | Status | |---|---| | Korean SPC acquiring loan receivables | Live | | On-chain recording of SPC cash flows | In build | | External OTC off-ramp (crypto → fiat) | Used in pilot | | Offshore vehicle receiving subscriptions and issuing units | Planned — not yet formed | | Foreign-currency bond issued by the SPC, subscribed by the offshore vehicle | Planned | | Generally available stablecoin subscription product | Not available today | *Source: root64 business structure and roadmap, as of June 2026.* The honest framing is that the destination of this money path — Korean loans held by a compliant Korean entity, with cash flows being made verifiable on-chain — is real and operating, while the front of the path, the offshore subscription tier that issues units in exchange for stablecoins, is designed and planned rather than live. None of this changes the nature of the underlying assets: they are loans, they carry credit risk, and the FX step carries currency risk. The structure makes the path to those assets compliant and, increasingly, verifiable — it does not remove the risk in the assets themselves.https://root64.io/blog/kaia-yield8-first-cross-border-investor/https://root64.io/blog/kaia-yield8-first-cross-border-investor/Kaia's Yield8, the first tokenized private-credit fund from Kaia Investment Partners, has become the first cross-border investor in the 8percent Korean loan-asset programme that root64 makes verifiable on-chain.Fri, 19 Jun 2026 00:00:00 GMTKaia's Yield8 — the first tokenized private-credit fund from Kaia Investment Partners (KIP) — has become the first cross-border investor to take part in the 8percent Korean loan-asset programme that root64 makes verifiable on-chain. The underlying assets are principal-and-interest receivables (원리금수취권) held in a Korean special-purpose company; a Hong Kong tokenization tier is planned and contingent on regulatory clearance. ## What was announced? 8percent — the licensed Korean online lender behind root64 — and Kaia, a Layer-1 blockchain focused on stablecoin settlement and on-chain finance across Asia, have partnered to build cross-border investment infrastructure for Korean loan assets. The arrangement tokenizes the right to receive principal and interest (원리금수취권) on 8percent's loan claims and connects them to Kaia's global investor network, with 8percent responsible for asset screening and supply and Kaia providing the blockchain, tokenization, and settlement layer ([Edaily, 21 Apr 2026](https://www.edaily.co.kr/News/Read?mediaCodeNo=257&newsId=03699846645477784); [Bloomingbit, "Kaia, Eight Percent Team Up on RWA Platform Tied to Korean Loan Claims"](https://en.bloomingbit.io/feed/news/113361)). Through that channel, **Kaia's Yield8 fund has become the first cross-border investor to take part in the 8percent loan-asset programme** that root64 makes verifiable on-chain. ## Who is Kaia, and what is Yield8? Kaia is a Layer-1 blockchain for stablecoin settlement and on-chain finance across Asia. Kaia Investment Partners (KIP) launched **Yield8** as its first tokenized private-credit fund — an on-chain route into Asian private-credit opportunities that have historically sat behind institutional-only access ([Kaia, "KIP launches Yield8", 21 Apr 2026](https://blog.kaia.io/kip-launches-yield8-your-onchain-gateway-to-asian-private-credit-markets/); [Electronic Times (etnews), 22 Apr 2026](https://www.etnews.com/20260422000136)). ## What is root64's role in this? root64 is the real-world-asset platform built by 8percent (see [What is root64?](/blog/what-is-root64)). Its role in this partnership is the verification and structuring layer, not the marketing of a return: - The underlying assets are **principal-and-interest receivables (원리금수취권)** on 8percent's Korean loans — see [What is a "right to receive principal and interest"?](/blog/right-to-receive-principal-and-interest). - They are held in a **Korean special-purpose company**, structured so investors take the credit risk of the underlying assets rather than of the originator — see [How root64 holds Korean loan assets](/blog/how-root64-holds-korean-loan-assets). A Hong Kong tokenization tier that would issue transferable tokens to professional investors is a **planned** next phase and is contingent on regulatory clearance; it is not yet formed. ## Why does this matter? Korean alternative credit has long been hard for global investors to reach — the barriers are structural, not just informational (see [Korean private credit, explained](/blog/korean-private-credit-explained)). This is the first time external, cross-border capital has been connected to 8percent's loan assets through the structure root64 verifies. It is a concrete step from a transparency-first foundation toward the planned tokenized-access tier — assets made checkable first, then opened to broader participation. ## What happens next? The Korean asset-holding layer is live today; the on-chain verification layer is being built, and the Hong Kong tokenization tier is a planned next phase contingent on regulatory clearance. As that verification layer comes online, root64 will publish on-chain records of the underlying assets, and further detail on the Yield8 allocation is published by Kaia through its own reporting. --- *Figures and terms relating to Yield8 are published by Kaia. The Hong Kong tokenization tier referenced here is planned, not yet formed, and contingent on regulatory clearance.*https://root64.io/blog/redemption-and-liquidity-design/https://root64.io/blog/redemption-and-liquidity-design/The loans underneath a private-credit fund run to maturity and cannot be called back early, yet investors want a way out. This is the core liquidity mismatch — and how a structure can be designed to manage it honestly instead of pretending it away.Fri, 19 Jun 2026 00:00:00 GMTA loan pool's underlying assets are non-redeemable — they repay on their own schedule, not on demand — so any structure built on them cannot promise instant exit. root64's design manages the mismatch through funded redemption windows, transfer to another investor, and maturity matching, rather than a daily-redemption promise it could not keep under stress. ## Why can't investors simply redeem out of a loan-backed structure whenever they want? Because the assets underneath are loans, and a loan is not a deposit. A loan pays principal and interest back on its own contractual schedule, and it generally cannot be called back early at the lender's convenience. So a fund built on those loans cannot return an investor's capital on demand unless it does one of two expensive things: hold a large pile of idle cash that earns nothing, or sell assets — often at a discount — to raise the money. This is the redemption problem, and it sits at the center of any honest attempt to put private-credit assets into an investable wrapper. The mismatch is structural, not a flaw to be patched over. On one side, the underlying loans are **non-redeemable** — they repay over time, not on request. On the other, investors naturally want a way out before every loan in the pool matures. Good liquidity design does not pretend this tension away with a promise of instant exit; it builds explicit, funded mechanisms that manage the gap and discloses them up front. This post walks through what the gap is, why pretending it isn't there is dangerous, and the three design levers a structure can use to manage it. ## What does "non-redeemable underlying asset" actually mean? It means the cash an investor put in is not sitting in an account waiting to be handed back — it has been lent to borrowers who will repay it on their loan's timetable. A loan receivable is the right to receive future repayments, not a balance available on demand. In root64's structure, the assets a Korean special-purpose company (SPC) holds are exactly this kind of instrument: the right to receive principal and interest (원리금수취권) on Korean loans. (For how that right works and why the SPC holds it, see [/blog/right-to-receive-principal-and-interest](/blog/right-to-receive-principal-and-interest) and [/blog/how-root64-holds-korean-loan-assets](/blog/how-root64-holds-korean-loan-assets).) Until a borrower repays, the money is working inside a loan. That is the whole point of the asset class — and it is also why this asset class pays an illiquidity premium in the first place. As one asset manager puts it for private credit generally, "illiquidity is a feature, not a flaw": investors are compensated for giving up the ability to exit instantly, because the manager can lend to borrowers who need committed, term capital rather than money that might be yanked at any moment ([AllianceBernstein — In Private Credit, Illiquidity Is a Feature, Not a Flaw](https://www.alliancebernstein.com/corporate/en/insights/investment-insights/in-private-credit-illiquidity-is-a-feature-not-a-flaw.html), accessed June 2026). The practical consequence: the natural liquidity of a loan-backed structure is the rhythm of its repayments. Capital flows back to investors as loans amortize and mature, not as a button an investor can press. Any liquidity offered faster than that rhythm has to be funded from somewhere — and where it is funded from is the entire design question. ## Why is pretending a loan pool is "daily redeemable" dangerous? Because promising more liquidity than the assets can deliver creates a first-mover problem: under stress, whoever exits first gets paid from the easy cash, and whoever stays is left holding the hard-to-sell loans. The promise is fine right up until everyone tries to use it at once. This is not a theoretical worry — it is the exact vulnerability global financial regulators have spent years addressing. The Financial Stability Board (FSB) and IOSCO, on 20 December 2023, published final policy recommendations specifically to address "structural vulnerabilities from liquidity mismatch in open-ended funds," whose central concern is the gap between assets that are slow to sell and fund units that can be redeemed quickly ([FSB — policies to address liquidity mismatch in open-ended funds, December 20, 2023](https://www.fsb.org/2023/12/fsb-and-iosco-publish-policies-to-address-vulnerabilities-from-liquidity-mismatch-in-open-ended-funds/)). Their framework groups funds by how liquid their assets actually are and expects funds holding illiquid assets to offer **less frequent redemption or longer notice periods** — in other words, to match the redemption promise to the asset, not the other way around. The mechanism the regulators name explicitly is the first-mover advantage. The recommendations aim "to mitigate potential first-mover advantage from structural liquidity mismatch" by making redeeming investors bear the cost of the liquidity they are taking, so that exiting early does not quietly transfer losses onto the investors who remain ([FSB — December 20, 2023](https://www.fsb.org/2023/12/fsb-and-iosco-publish-policies-to-address-vulnerabilities-from-liquidity-mismatch-in-open-ended-funds/)). The lesson for any loan-backed structure is direct: a daily-redemption promise layered over non-redeemable loans is not generous, it is fragile. The honest move is to design liquidity that the assets can actually support, and to be explicit about its limits. ## How can a structure provide liquidity without misrepresenting the assets? By offering liquidity through funded, scheduled mechanisms rather than an unconditional on-demand promise. There are three main levers, and a well-designed structure uses them in combination rather than relying on any one. | Liquidity lever | How it works | What it depends on | |---|---|---| | Periodic redemption window | At set intervals, investors can request redemption; requests are funded from loan repayments that have actually come in | Incoming repayments; requests met in order if they exceed available funds | | Transfer to another investor | An exiting investor's position is taken over by another professional investor, rather than the pool being drawn down | A counterparty willing to buy; a venue or process for transfer | | Maturity matching | An investment is sized and timed to a loan's own maturity, so capital returns naturally as the loan repays | The investor accepting a term that fits the underlying asset | *Source: root64 business structure, redemption and token-lifecycle design, as of June 2026.* Each lever addresses the mismatch from a different angle. A redemption window converts the loan pool's natural repayment rhythm into predictable exit opportunities. Transfer moves a position sideways to a new holder without forcing the pool to sell assets at all. Maturity matching avoids the mismatch at the source by aligning the investment horizon with the asset horizon. The sections below take the first two in turn — maturity matching is the simplest case, where the question of early exit largely does not arise because the investor signed up for the loan's own clock. ### How does a redemption window work? A redemption window is a scheduled opportunity to request redemption, funded by repayments that have genuinely flowed in — not a guarantee of instant, full payout on any chosen day. In root64's design, when an investor requests redemption, the structure stops reinvesting the repayments attributable to that position and instead accumulates them; as loans repay, the accumulated cash funds the redemption, and requests are honored in order. Because the assets are loan receivables, immediate redemption is not available; recovered principal and interest fund redemptions as they come in. This is the same principle that regulated semi-liquid vehicles use, which is why the comparison is useful for grounding rather than novelty. U.S. interval funds — closed-end funds that offer limited periodic liquidity — make repurchase offers for a set slice of shares at regular intervals under SEC Rule 23c-3, "typically between 5% and 25%" of the fund at each interval, most commonly 5% ([Investor.gov — Interval Funds](https://www.investor.gov/introduction-investing/investing-basics/investment-products/closed-end-funds/interval-funds)). Critically, that liquidity is bounded and disclosed: if redemption requests in a given window exceed the amount available, "you might not be able to sell as many shares as you had intended" ([FINRA — Interval Funds: 6 Things to Know](https://www.finra.org/investors/insights/interval-funds)). The honesty is in the limit being stated up front, not discovered under stress. The general design principle root64 follows is the same: liquidity is real but bounded, periodic, and funded by actual repayments. A redemption window is an exit opportunity governed by the pace of the underlying loans — not a contradiction of the fact that those loans are non-redeemable. The specific cadence, notice, and any size limits of a given window are set per arrangement and disclosed to investors in offering documents; this post deliberately does not state particular terms, because they vary and are not generalizable. ### How does transfer to another investor create liquidity? Transfer creates liquidity by moving an investor's position to a different holder instead of pulling cash out of the pool. If an investor wants to exit and another professional investor is willing to step in, the position changes hands and the underlying loans are never disturbed — no asset has to be sold, and no redemption queue is drawn down. This is the secondary-market lever, and it is structurally the cleanest, because it sidesteps the redemption problem entirely: one investor's exit is another's entry, and the pool's loans keep running undisturbed. It is also where tokenization is genuinely useful. Representing a position as a transferable on-chain unit is designed to make this hand-off cleaner — a transfer of the token is the transfer of the position — which is part of why root64 builds toward transferable units in a later phase. (How that on-chain representation and its verifiability are meant to work is covered in [/blog/how-to-verify-root64-on-chain-proofs](/blog/how-to-verify-root64-on-chain-proofs) and [/blog/what-is-root64](/blog/what-is-root64).) Two honest caveats apply. First, transfer depends on there being a willing counterparty; a secondary route provides liquidity only to the extent a buyer exists at a price both sides accept, which is not guaranteed at any moment. Second — and this is a hard constraint, not a preference — any such transfer is between professional investors through private placement. The token-issuance tier that would carry these positions is a planned phase through a Hong Kong vehicle, contingent on regulatory clearance and not yet operating; the vehicle is not yet formed. So secondary transfer is a designed-for capability of the structure, not a live, generally available marketplace today. (On who can participate and the cross-border access constraints, see [/blog/how-foreign-investors-access-korean-loan-assets](/blog/how-foreign-investors-access-korean-loan-assets).) ## How does maturity matching reduce the need for redemption at all? Maturity matching reduces the need for early exit by aligning the investment's horizon with the loan's horizon from the start, so that capital returns naturally when the underlying loan repays. If the term an investor signs up for fits the maturity of the assets backing it, "early redemption" is no longer the primary way out — repayment is. This is the same logic that has long governed institutional private credit, where closed-end, term-committed structures dominate precisely because loans are illiquid and "investors often hold the loan until maturity" ([AllianceBernstein — illiquidity is a feature](https://www.alliancebernstein.com/corporate/en/insights/investment-insights/in-private-credit-illiquidity-is-a-feature-not-a-flaw.html), accessed June 2026). Term commitment is not a defect of the asset class; it is the mechanism by which the illiquidity premium is earned. A structure that matches investor terms to asset maturities is being faithful to that economics rather than fighting it. In practice no real pool matches perfectly — borrowers prepay, some loans extend, and investor horizons differ — which is exactly why the other two levers exist alongside it. Maturity matching shrinks the mismatch; redemption windows and transfer manage what mismatch remains. The combination is the design: reduce the gap at the source where you can, and provide funded, bounded, disclosed liquidity for the rest. ## How does root64 think about redemption and liquidity overall? By treating liquidity as something to engineer honestly, not something to over-promise. The underlying loans are non-redeemable, so the structure does not offer instant on-demand redemption; instead it combines maturity matching to shrink the mismatch, redemption windows funded by actual repayments to provide periodic exit, and transfer to another professional investor to move positions without disturbing the pool. The throughline connects to root64's broader posture of transparency before tokenization (see [/blog/transparency-before-tokenization](/blog/transparency-before-tokenization)). Honest liquidity design and honest reporting are the same discipline applied to two different questions: do not represent the asset as something it is not. A loan pool that records its actual cash movements on-chain and a redemption mechanism that pays out from actual repayments are both refusals to paper over the reality of the asset. None of this is a return guarantee — the underlying loans carry credit risk, and how much an investor receives depends on how the loans perform. Liquidity design governs the path capital takes back to investors; it does not change what the assets earn. For context on the asset class itself, see [/blog/korean-private-credit-explained](/blog/korean-private-credit-explained) and, for the regulatory backdrop in Korea, [/blog/korea-online-investment-linked-finance-act-explained](/blog/korea-online-investment-linked-finance-act-explained). The redemption problem has no magic solution, and any platform claiming otherwise should invite scrutiny. What a well-built structure can do is make the constraint explicit, design around it with funded and bounded mechanisms, and disclose the limits before an investor commits — which is the difference between a liquidity promise that holds under stress and one that breaks exactly when it is tested.https://root64.io/blog/registration-vs-verification/https://root64.io/blog/registration-vs-verification/On root64, the party that registers an asset is never the party that verifies it. This separation, and the on-chain record of every check, is what turns "data on a blockchain" into something an investor can actually trust.Fri, 19 Jun 2026 00:00:00 GMTroot64 separates two roles: registration (the party closest to the asset records the data) and verification (an independent external channel checks it). The check result — match, mismatch, or inconclusive — is itself recorded on-chain, including mismatches and their resolution, so no single party is the sole source of truth. ## What is the difference between registering an asset and verifying it? Registration is recording the data; verification is independently checking it. On root64, these are two separate roles held by two separate parties, and that separation is the whole point. The party that *registers* an asset — the originator that supplied the loan, or the special-purpose company's (SPC) fund administrator that records cash movements — is never the party that *verifies* that the data is true. Verification is done against an external channel that the registrant does not control. This is a deliberate design principle, not an implementation detail. A platform that lets the same party both assert a fact and confirm it has not actually checked anything — it has asked an interested party to mark its own homework. root64's data-trust model is built to make that impossible by construction. The principle is familiar from internal-control practice under names like separation of duties or the "four-eyes" principle: for any consequential action, the party that creates a record should not be the only party that confirms it. The U.S. accounting-scandal reforms of the early 2000s made this a baseline expectation for financial reporting, precisely because self-confirmation is where errors and manipulation hide. root64 applies the same logic to on-chain asset data. ## Why isn't "the data is on a blockchain" enough? Because putting data on a blockchain proves only that the data was *recorded* — not that it is *true*. A blockchain guarantees that an entry, once written, is hard to alter and easy to inspect. It guarantees nothing about whether the entry matched reality at the moment it was written. If an originator simply writes "this loan exists and is performing" to a public chain, an investor has gained immutability of a claim, not evidence of a fact. This is the gap root64's model is built to close, and it is the same gap explored in [why root64 publishes proofs before issuing tokens](/blog/transparency-before-tokenization): a token, or any on-chain record, is only as trustworthy as the verification underneath it. Registration produces the record. Verification produces the trust. Treating them as one step — "we put it on-chain, so it's verified" — is the mistake the whole design is meant to avoid. The point generalizes beyond root64. The U.S. accounting regulator, the Public Company Accounting Oversight Board (PCAOB), has warned that even formal crypto "proof of reserve" reports "are not equivalent or more rigorous than an audit" and that investors should exercise caution unless reserve data is independently checked against an outside source ([PCAOB Investor Advisory, March 2023](https://pcaobus.org/resources/information-for-investors/investor-advisories/investor-advisory-exercise-caution-with-third-party-verification-proof-of-reserve-reports)). "It's on-chain" and "it's verified" are different claims, and conflating them is exactly what an honest verification layer has to refuse to do. ## Who registers, and who verifies? The two roles are assigned to different parties by asset type. For asset data, the originator registers and an external public channel verifies. For cash data, the SPC's fund administrator registers and a bank channel verifies. In every case, the verifier is independent of the registrant. Some terms first. An **originator** is the lender that supplied the loans — in root64's initial pool, 8percent, the FSC-licensed Korean P2P (online investment-linked finance) lender behind the platform. The **SPC** is the Korean special-purpose company that holds [the right to receive principal and interest (원리금수취권)](/blog/right-to-receive-principal-and-interest) on those loans in a bankruptcy-remote structure; how that holding works is covered in [how root64 holds Korean loan assets](/blog/how-root64-holds-korean-loan-assets). The **fund administrator** is the third party that keeps the SPC's books and records its cash transactions. The split looks like this: | Data type | Registered by | Verified against (independent channel) | |---|---|---| | Asset data (loan, collateral) | Originator (e.g. 8percent) | Property registry; Korea's P2P central record-keeper (KFTC) | | Cash transactions | SPC fund administrator | Bank API | *Source: root64 data-verification model, per its product strategy, as of June 2026.* Two details matter here. First, Korea's P2P central record-keeper is the **Korea Financial Telecommunications and Clearings Institute (금융결제원, KFTC)** — the institution that maintains the official central record of online investment-linked finance loans under Korea's [Online Investment-Linked Finance Act](/blog/korea-online-investment-linked-finance-act-explained). It is an external authority, not something the originator can edit, which is exactly why it works as a verification channel. Second, the registrant is always the party *closest* to the asset, because that party has the data first and most accurately; the verifier is always a party with *no incentive* to confirm a false entry. Registration optimizes for accuracy at source; verification optimizes for independence. ## What does the on-chain verification record actually capture? It captures the check, not just the data. In the designed model, each verification writes an on-chain entry recording what was verified, which channel it was verified against, and the result — and the result is one of exactly three values: **match**, **mismatch**, or **inconclusive**. This is the layer that makes the act of verification itself auditable. Recording the check rather than only the data is the second half of the separation principle. Separating registration from verification means nothing if the verification then happens invisibly off-chain, because an investor would once again be trusting that someone, somewhere, did the check honestly. By writing the verification result to the chain, root64 makes the check a public, append-only fact: an investor can see *that* the data was checked, *against what*, and *with what outcome*. Concretely, each verification entry records its target (asset data or cash flow), the channel used, the result, a timestamp, and a hash of the supporting evidence. The evidence hash is produced by extracting the core fields of the external channel's response, serializing them in a canonical form, and hashing the result — so that an auditor holding the original response can later reproduce the same hash and confirm the on-chain entry corresponds to a specific, real check, without the raw response itself having to live on a public chain. The mechanics of how an outside party reproduces and inspects these records are covered in [how to verify root64's on-chain proofs](/blog/how-to-verify-root64-on-chain-proofs). This is verification, not an audit, and root64 is careful about the distinction. Verification establishes that a specific piece of data was checked against an independent channel and what the result was. An audit is a broader, standards-governed examination of an entity's financial statements. The model is designed to reduce reliance on periodic external audits by making routine checks continuous and on-chain — not to replace the concept of an audit or to claim the authority of one. ## What happens when the data doesn't match? The mismatch is recorded on-chain as a mismatch. It is not hidden, smoothed over, or quietly corrected before anyone sees it. This is the single most important consequence of the design, because the value of a verification layer is measured by what it does when something is wrong, not when everything is right. A system that only ever shows clean results has told you nothing about its honesty — you cannot distinguish "nothing was ever wrong" from "problems were never recorded." root64's model resolves that ambiguity by making **mismatch** and **inconclusive** first-class outcomes, written to the chain with the same permanence as a match. An inconclusive result — where the external channel could not confirm or deny the registered data — is recorded as inconclusive rather than rounded up to a pass. When a mismatch is later investigated and resolved, the resolution is itself recorded on-chain, carrying a reference back to the original verification entry and a hash of the supporting evidence for the fix. The result is a complete, append-only trail: the original mismatch stays on the record, linked to its resolution, so the history shows both that data once failed to line up and how it was reconciled. Nothing is overwritten; corrections are added on top, the way a proper ledger handles an error. This is what separates a transparency layer from a marketing dashboard. A dashboard shows you the state someone wants you to see. An append-only verification log, including its mismatches, shows you the state the assets are actually in — and the record of every time the platform had to reconcile its own data with the outside world. ## How does this connect to the rest of root64? The registration-versus-verification split is the load-bearing principle beneath everything else root64 plans to build. The platform's roadmap moves from a transparency layer, to tokenization, to onboarding additional originators — and each later stage inherits its trustworthiness from this base layer rather than re-establishing it. The multi-layer model matters most as the platform scales beyond a single originator. When 8percent registers its own assets, an investor might reasonably extend it some benefit of the doubt. When a *third-party* originator registers assets onto the platform, that benefit of the doubt evaporates — and the independent-verification layer becomes the only thing standing between an investor and an unchecked claim by a party they have never met. A design that requires every originator's data to clear an external channel, and that records the result publicly, is what lets the platform add originators without each one having to be individually trusted. This is the practical mechanism behind [how foreign investors access Korean loan assets](/blog/how-foreign-investors-access-korean-loan-assets) on root64: not a promise to trust the operator, but a structure that reduces how much trust is required at all. It is worth being clear about scope. This verification layer is root64's planned first phase — it is being built and is not yet live in production — and it is designed to operate on a pool of Korean private-credit loans; for the asset class itself, see [Korean private credit explained](/blog/korean-private-credit-explained). Token issuance through a Hong Kong vehicle is a planned second phase, contingent on regulatory clearance, and that vehicle is not yet formed. And separately: verification does not make the underlying loans risk-free. They are loans, and they carry credit risk. What the model does is make the *state* of those loans independently checkable — registered by the party who knows them best, verified by a party with no reason to lie, and recorded where anyone entitled to look can see both the checks and the mismatches. When the on-chain entries that record those verification results are written, they are signed by an independent trustee — completing the separation: the party closest to the asset registers it, an independent channel verifies it, and an independent party commits the result to the chain. No single actor, including 8percent, is the sole source of truth. That, more than any single technology choice, is what the multi-layer model is for.https://root64.io/blog/six-structural-barriers-korean-credit/https://root64.io/blog/six-structural-barriers-korean-credit/Korean loan assets are hard for global capital to reach — not because of one rule, but because of six distinct structural barriers stacked on top of each other. Here is each one, why it exists, and how a transparency-first, offshore structure is designed to address it.Fri, 19 Jun 2026 00:00:00 GMTSix structural barriers sit between global capital and Korean loan assets: unfamiliar assets, multi-layer counterparty risk, no real-time independent verification, currency exposure, limited liquidity, and the cost of traditional securitization. They stack rather than substitute — clearing one leaves the others — which is why access has to be engineered as a structure, not a single transaction. ## Why is Korean credit so hard for global capital to reach? Because the difficulty is not one barrier but six, stacked on top of each other. Global capital does not bounce off a single rule when it tries to reach Korean loan assets; it runs into a sequence of distinct structural problems, each with a different cause, and clearing one leaves the rest standing. That is why access to this asset class has to be engineered as a structure, not executed as a single transaction. This post takes the barriers one at a time. A companion piece, [Korean private credit, explained for global investors](/blog/korean-private-credit-explained), covers what the asset class is and how it is regulated, and [How can foreign investors access Korean loan assets?](/blog/how-foreign-investors-access-korean-loan-assets) walks through the three conditions a compliant access path must satisfy. This article goes deeper on the underlying problem those pieces respond to: the precise set of structural barriers that make Korean credit hard to reach in the first place. The barriers are not interchangeable. Some are information problems that better disclosure can shrink; some are properties of the asset class itself that no structure can eliminate, only manage and make visible. Telling them apart is the whole point — it determines what a platform can actually fix and what it can only be honest about. ## What are the six structural barriers? There are six, and they fall into three groups by what kind of problem they are. The table below names each barrier, the group it belongs to, and what it means for a global investor. | # | Barrier | Type of problem | What it means for a global investor | |---|---|---|---| | 1 | Unfamiliar assets | Information | Korean collateral types, loan structures, and recovery procedures are hard to evaluate from outside | | 2 | Multi-layer counterparty risk | Information / trust | Capital passes through several entities, each opaque from abroad | | 3 | No real-time independent verification | Trust | Conventional reporting is periodic, leaving gaps between reports | | 4 | Currency exposure | Asset-class property | Capital is in dollars or stablecoins; the loans are in Korean won | | 5 | Limited liquidity | Asset-class property | Loan assets are held to maturity; they are not freely tradable | | 6 | Cost of traditional securitization | Structural cost | Layers of intermediaries raise costs and lower net returns | *Source: root64 product strategy, problem analysis, as of June 2026.* The grouping matters more than the list. Barriers 1 through 3 are about what an investor can know — information and trust problems, the ones a product can most directly attack. Barriers 4 and 5 are properties of the asset itself — a won-denominated, held-to-maturity loan stays that way no matter how it is wrapped. Barrier 6 is about cost — the price of the machinery connecting investor to asset. The sections below take each in turn. ## Barrier 1: why are Korean loan assets unfamiliar to global investors? Because the asset class sits inside a domestic legal and collateral framework that an outside investor has little prior basis to evaluate. Korean loan assets are a credit exposure whose value depends on Korean collateral types, Korean loan structures, and the procedures Korean law provides for recovering on a loan that goes bad — none of which a global investor encounters elsewhere. The specifics are where the unfamiliarity bites. The collateral types root64 works with include real-estate-secured consumer loans and securities-account-collateralized loans, and how collateral is perfected and how a creditor's rights are exercised on default are governed by Korean procedure. An investor abroad cannot easily assess, on their own, how a lien attaches, how enforceable it is, or what happens to the collateral if the borrower stops paying. This information asymmetry is the most fundamental barrier of the six, because it sits upstream of the investment decision itself: an investor who cannot evaluate the asset cannot price it, and an asset that cannot be priced does not get bought. This is a barrier a product can shrink rather than remove. The response is disclosure built for an outside reader — asset-type explainers, visualizations of how collateral rights are exercised on default, and per-loan collateral data (registry status and loan-to-value among them) published rather than summarized. root64 publishes detailed primers on exactly these mechanics — see [Real-estate-secured loans: default and recovery](/blog/real-estate-secured-loans-default-and-recovery) and [the right to receive principal and interest](/blog/right-to-receive-principal-and-interest). Disclosure cannot make an unfamiliar asset familiar overnight, but it can move it from un-evaluable to evaluable, which is the difference that matters. ## Barrier 2: what is multi-layer counterparty risk? It is the risk that comes from capital having to pass through several entities to reach the asset — each of which the investor must trust, and each of which is opaque from abroad. A global investor in Korean credit is not only taking a view on the underlying loans; they depend on the operational reliability of every entity the money flows through on its way in and back out. The chain is real and multi-party. Capital moving into a structured Korean-credit position relies on the stability of the domestic special-purpose company that holds the assets, the integrity of the fund administrator that manages and records the cash, and the transparency of fund movements between the on- and offshore layers. From abroad, information on each participant is extremely limited. The investor is being asked to trust not one counterparty but a stack of them, sight unseen. The response separates what a product can show from what it cannot, and maximizes the first. On the product side: the role and status of each structural participant can be surfaced rather than left implicit, and the special-purpose company's cash transactions can be recorded independently by the administrator and then cross-checked against bank records through a separate channel — so the cash flow is evidenced, not asserted. On the non-product side, external audit, credit assessment, and the indirect credibility of established partners participating in the structure all contribute. The intent is to convert "trust the chain" into "inspect the chain," entity by entity. ## Barrier 3: why isn't conventional reporting enough? Because conventional reporting is periodic, and periodic reporting leaves gaps. For an investor who cannot stand in the room, the question is not only what a report says but what happened between reports — and the standard reporting cycle for this asset class is built around intervals, not continuity. The cadence makes the gap concrete. Reporting on these assets conventionally runs on a periodic cycle — net asset value calculated weekly, reports delivered monthly. Between those points an investor has no independent way to confirm the state of the assets; they depend on the reporter, and the asset's condition is uncertain in the interval. This is not a Korea-specific failing — it is how privately held credit is normally reported everywhere — but it is felt more acutely by an investor reaching across borders into an unfamiliar market, where the reporter is also the party they understand least. This is the barrier root64's transparency layer is built to address first, ahead of any tokenization. Cash transactions and investment balances are recorded on a public blockchain as an append-only log — entries added but never edited or deleted — and external verifications against independent channels are logged on-chain as well, including mismatches and their resolution. The aim is to replace "wait for the next report" with "look at the ledger." The reasoning behind building this layer before issuing any token is set out in [Transparency before tokenization](/blog/transparency-before-tokenization), and the mechanics of checking the records are covered in [How to verify root64's on-chain proofs](/blog/how-to-verify-root64-on-chain-proofs). On-chain recording does not by itself make data true — what makes it meaningful is that the source and the verifier are distinct and the verification result is itself recorded — which is why registration and verification are kept as separate roles, with on-chain signing performed by an independent trustee. ## Barrier 4: how does currency exposure get in the way? Because the capital and the asset are in different currencies, and the path between them is expensive and constrained. Global capital arrives in dollars or stablecoins; the underlying loans are originated, serviced, and repaid in Korean won. Every stage from investment to recovery is exposed to currency movement, and the conversion path itself carries friction and cost. The friction is structural, not incidental. The Korean won is not freely usable by non-residents the way a major reserve currency is: non-residents transact won through designated account types, and the rules around moving funds in and out differ by account — from an ordinary non-resident won account, "notification to the BOK is required for overseas remittance of the withdrawn funds," whereas only the non-resident *free* won account lets a non-resident "convert funds in this account into foreign currency and transfer the proceeds abroad" ([Bank of Korea, Internationalization of the Korean Won](https://www.bok.or.kr/eng/main/contents.do?menuNo=400195), accessed 2026-06-19). On top of account friction sits the conversion economics: hedging won exposure has a cost, and at present a corporate crypto on/off ramp is not available in Korea, which makes the conversion route between digital assets and won more complex and costly than a single swap. This is a barrier a structure can manage and disclose but cannot make disappear, because it is a property of holding a won asset with non-won capital. The honest framing is that the first structured product is unhedged — the investor bears the currency exposure — with traditional FX hedging or stablecoin-based hedging as later possibilities to evaluate, not present features. Longer-term relief depends on the external environment, not on any one platform: if corporate crypto on/off ramps become permitted in Korea, the conversion path simplifies; if an official won stablecoin is issued, an end-to-end on-chain won flow becomes conceivable. Both are anticipated environmental shifts, not capabilities that exist today, and no currency outcome is promised. ## Barrier 5: why can't loan assets just be sold when an investor wants out? Because loan assets are illiquid by nature — they are meant to be held to maturity, and there is no deep secondary market to exit into. This is not a quirk of the Korean market; it is a defining characteristic of private credit as an asset class. A loan is a contract to receive principal and interest over time, not a security with a continuous price and a ready buyer. The wider asset class makes the point plainly. The U.S. Federal Reserve, describing private credit, notes that "given the absence of a liquid secondary market for many private credit instruments, lenders typically hold these loans until maturity or a refinancing event," and that part of the asset class's return is compensation "for the illiquidity and the opacity of the market" ([Federal Reserve, *Private Credit: Characteristics and Risks*, February 23, 2024](https://www.federalreserve.gov/econres/notes/feds-notes/private-credit-characteristics-and-risks-20240223.html)). Korean loan assets inherit this property: in a traditional securitization structure, selling out mid-life is difficult, and the immediate liquidity that crypto-native investors often expect is inherently hard to provide for a held-to-maturity asset. Like currency exposure, this is an asset-class property a structure can soften at the edges but not eliminate. The staged approach is to offer a measure of redeemability through an existing primary-market mechanism for trading the right to receive principal and interest, and — only after token issuance, itself a later, clearance-contingent phase — to open the possibility of secondary transfer of tokens. Even then, tokenization changes the *mechanism* of transfer, not the underlying fact that the asset is a loan held to maturity. A token can make a claim easier to move; it cannot manufacture a buyer or a price where the asset class provides neither. ## Barrier 6: why does the traditional securitization route cost so much? Because the conventional machinery for structuring an alternative-asset investment carries layers of intermediaries, and each layer adds cost while limiting information. Trustees, auditors, and legal advisers each take a fee and control a slice of the information, and small-ticket diversified participation is hard to arrange inside that structure. The result is a wedge: higher financing costs for the asset originator at one end, lower net returns for the final investor at the other. The inefficiency compounds the other five barriers rather than standing apart from them. A structure heavy with intermediaries is not only expensive — it is also where the information opacity of Barrier 2 and the reporting gaps of Barrier 3 live, because information access in such structures is itself limited. Cost and opacity travel together. This is the barrier that most directly motivates root64's overall design. The principle is to maximize what can be solved in product and thereby reduce dependence on costly intermediaries — for example, a multi-layer verification model built in product (originator registration plus external public-channel verification; administrator records plus bank-API cross-checking) that reduces reliance on external audit while still achieving a high level of data reliability. The aim is not to eliminate every intermediary — legal structuring, regulatory work, and external assurance remain genuinely necessary — but to shift the burden toward a leaner structure where feasible, so that more of the asset's economics reaches the investor. ## What do these six barriers add up to? That access to Korean loan assets is a structural problem, not a transactional one — and that the right response is honest about which barriers a product can solve and which it can only manage. The six barriers do not substitute for one another; they stack. An investor who solves currency exposure still faces illiquidity; one who gets comfortable with the assets still faces counterparty opacity and reporting gaps. There is no single key that opens all six locks. That is why root64 is built the way it is. The information and trust barriers — unfamiliar assets, counterparty opacity, and the verification gap — are attacked directly with product: asset disclosure, surfaced structural participants, and a transparency-first on-chain record built ahead of tokenization. The asset-class properties — currency exposure and illiquidity — are managed and disclosed rather than promised away, with the first product unhedged and liquidity addressed in stages. The cost barrier shapes the whole design toward a leaner structure. None of it removes credit risk: these are loans, and whether borrowers repay remains the question the structure is built to let an investor evaluate, not to answer for them.https://root64.io/blog/real-estate-secured-loans-default-and-recovery/https://root64.io/blog/real-estate-secured-loans-default-and-recovery/When a Korean real-estate-secured loan defaults, recovery runs through one of two collateral routes: court auction or sale of the non-performing loan. This deep dive walks through the default trigger, both recovery paths, the backup-servicer protection that keeps collection going if the servicer fails, and the historical collateral cushion behind root64's real-estate assets.Mon, 15 Jun 2026 00:00:00 GMTA Korean home-secured loan typically defaults after about two months of missed interest, with advance written notice required. Recovery runs through court auction or sale of the non-performing loan to an NPL buyer or KAMCO, where a mortgagee ranks fifth in the payout. root64's real-estate assets are KB-appraised apartments in 200-plus-unit complexes, capped at 70% LTV with a registered mortgage. ## What actually happens when one of these loans defaults? When a Korean real-estate-secured loan stops being repaid, the lender accelerates the loan and then recovers against the collateral apartment through one of two routes: a court-run auction of the property, or a sale of the now non-performing loan to a specialist buyer. The borrower's personal promise stops being the point; the registered mortgage on the apartment becomes the point. This is the question a professional investor should ask before anything else about a real-estate-secured book: not "how often does it default?" but "when it does, what is the machinery that turns a defaulted loan back into cash, and how good is the collateral standing behind it?" This post walks through that machinery end to end — the default trigger, the two recovery paths, the backup that keeps collection running if the servicer itself fails, and the historical collateral cushion. It does not discuss root64's own performance figures; those are out of scope for this public post and require separate disclosure. For context on the assets themselves: root64's real-estate-secured loans are made against owner-occupied apartments and mixed-use residences that carry a KB market valuation and sit in complexes of 200-plus units, secured by a registered mortgage (근저당, a maximum-amount mortgage), with a loan-to-value cap of 70% and title insurance required on each (root64 real-estate-secured loan product parameters, as of June 2026). The 200-unit floor and KB-valuation requirement are not incidental — they are what make the collateral cushion below quantifiable, because liquid, frequently-traded apartments are exactly the assets Korea's auction and valuation infrastructure measures best. ## When is a Korean real-estate loan in "default"? For a household home-secured loan, the standard trigger for acceleration — losing the benefit of the term (기한이익상실, acceleration / loss of benefit of time) — is interest unpaid for two consecutive months. That is more lenient than the one-month rule for ordinary household loans, and it was deliberately set that way. The general rule under Korea's standard bank lending terms is that an ordinary household loan accelerates when interest has been "in arrears continuously for one month." Home-secured loans were carved out to a longer two-month threshold by a January 2014 revision to the standard terms issued by the Korea Fair Trade Commission, extending the prior one-month trigger ([Money Today, 2014-01-16](https://www.mt.co.kr/economy/2014/01/16/2014011609185751957)). Corporate loans run the other way — acceleration after just 14 days of arrears ([Shinhan Card, standard bank lending terms](https://www.shinhancard.com/pconts/html/helpdesk/terms/terms47/1186818_1197.html)). Acceleration is not silent. The lender must give the borrower advance written notice before the benefit of the term is lost — generally three business days in advance, extended to seven business days in advance for home-secured loans, a strengthening also introduced in the 2014 revision ([Money Today, 2014-01-16](https://www.mt.co.kr/economy/2014/01/16/2014011609185751957)). For an investor, this matters because it bounds the timeline: a defaulted home loan does not vanish overnight; it moves through a defined notice-then-acceleration sequence before any recovery action begins. | Borrower / loan type | Acceleration trigger (interest arrears) | Advance notice | |---|---|---| | Ordinary household loan | ~1 month | 3 business days | | Household home-secured loan | ~2 months | 7 business days | | Corporate loan | 14 days | 3 business days | *Sources: standard bank lending terms ([Shinhan Card](https://www.shinhancard.com/pconts/html/helpdesk/terms/terms47/1186818_1197.html)); 2014 revision extending home-loan trigger and notice ([Money Today, 2014-01-16](https://www.mt.co.kr/economy/2014/01/16/2014011609185751957)). These are the standard-terms defaults; specific loan documents may differ.* ## Recovery path 1: the court auction (security-enforcement auction, 임의경매) Once accelerated, the most direct recovery route is a court auction of the mortgaged apartment. Because the loan is secured by a registered mortgage, the lender can go straight to auction on the strength of the mortgage documents — no separate court judgment is needed first. This is what distinguishes a security-enforcement auction (auction to enforce a security interest) from a judgment-based auction (강제경매). The latter is an unsecured creditor's auction. The legal basis is Korea's Civil Execution Act, Part 3 on "auctions for the enforcement of security interests" (Articles 264–275); Article 264 requires only documents proving the security interest to start the process ([Civil Execution Act, Art. 264](https://www.law.go.kr/LSW//lsLawLinkInfo.do?lsJoLnkSeq=900158237&lsId=009290&chrClsCd=010202&print=print)). A judgment-based auction and a security-based auction then proceed through essentially the same nine steps — the difference is the entry ticket, not the path: 1. Creditor files the auction petition 2. Court issues the commencement decision (and attachment/seizure) 3. Sale preparation — site survey, appraisal, sale-particulars statement 4. Public notice of the distribution-demand deadline 5. Sale date (bidding) 6. Highest bidder determined 7. Sale-permission decision (with an appeal window) 8. Buyer pays the purchase price 9. Distribution to creditors ([Korea easylaw.go.kr, auction procedure](https://easylaw.go.kr/CSP/CnpClsMain.laf?popMenu=ov&csmSeq=306&ccfNo=1&cciNo=1&cnpClsNo=3)). Indicative timing within those steps: the commencement decision usually issues within a few days of filing, the sale date is set at least 14 days after public notice, and the sale-permission decision typically follows about 7 days after the sale date ([Mirae Auction, procedure guide](https://www.mkauction.com/data/procedure.html)). **How long does it take?** A security-enforcement auction runs roughly 6–9 months on average (about 2–4 weeks of preparation plus 4–7 months of auction process), while a judgment-based auction averages 9–12 months because it needs the underlying judgment first. Outcomes vary with the property, the number of failed sale rounds, and any objections ([law-firm guidance](https://realestate.ehyun.co.kr/imyi-gyeongmae-gangje-gyeongmae-chai); this is practitioner guidance, not official court statistics). **Where does the mortgagee sit in the payout?** This is the crux of recovery quality. Korean auction distribution follows a fixed priority ladder (Civil Execution Act Art. 145(2) and related rules): | Rank | Claim | |---|---| | 1 | Execution costs | | 2 | Third-party acquirer's reimbursement (necessary/beneficial expenses) | | 3 | Top-priority claims — small-deposit tenant minimums (housing/commercial lease protection acts); last 3 months' wages and 3 years' severance | | 4 | "Current-property" taxes (당해세, current-property tax) | | **5** | **Preferential claims — including mortgages and registered leasehold/jeonse rights, plus general national/local taxes and fixed-date tenants** | | 6 | General wage claims | | 7 | General tax claims | | 8 | Public dues (health/employment/industrial-accident insurance) | | 9 | General unsecured claims | *Source: [Korea easylaw.go.kr, auction distribution priority](https://easylaw.go.kr/CSP/CnpClsMain.laf?popMenu=ov&csmSeq=629&ccfNo=5&cciNo=2&cnpClsNo=5).* A mortgagee is a rank-5 preferential creditor. It is paid after execution costs, top-priority small-deposit and wage claims, and current-property taxes — but ahead of general taxes, public dues, and ordinary unsecured creditors ([easylaw.go.kr](https://easylaw.go.kr/CSP/CnpClsMain.laf?popMenu=ov&csmSeq=629&ccfNo=5&cciNo=2&cnpClsNo=5)). The senior claims that can erode a mortgagee's recovery are bounded and identifiable (small-deposit tenant minimums and certain taxes), which is exactly why title insurance and disciplined LTV underwriting matter for this asset class. ## Recovery path 2: selling the loan as an NPL The second route does not wait for an auction to finish — the lender sells the defaulted loan itself. A non-performing loan (NPL) is a loan generally 3+ months delinquent that is no longer being repaid normally; rather than collect it directly, lenders discount-sell these to securitization vehicles, asset-management companies (AMCs), or KAMCO to crystallize the loss and remove the risk from their books ([KAMCO](https://www.kamco.or.kr/portal/contents.do?mId=0303030000)). The mechanics: the seller assesses expected recovery, then sells via public auction (KAMCO's Onbid platform) or private negotiation. Typically the loan is transferred to a special-purpose company (SPC), which issues asset-backed securities (ABS) to senior/junior investors, while an AMC is engaged to collect and manage the pool. After the channel is set, ownership of the claim transfers (with a creditor-assignment notice to the borrower under Civil Act Art. 450), the mortgage is re-registered to the new creditor, and the new creditor recovers — ultimately through the same court-auction framework ([Samil PwC, 2024 NPL market](https://www.pwc.com/kr/ko/insights/issue-brief/samilpwc_2024-npl-market.pdf); [legal practitioner guide](https://lawjibsa-corp-dosan.com/faq/read_detail/82)). The legal foundation is the 1998 Asset-Backed Securitization Act, which institutionalized the SPC-and-ABS structure ([KCI](https://www.kci.go.kr/kciportal/landing/article.kci?arti_id=ART002737992)). **Why sell instead of waiting?** Selling crystallizes the loss immediately, frees liquidity, and improves balance-sheet health — at the cost of accepting a discount to face value. KAMCO, the public asset-management agency, frames its own advantages as completing a sale within ~1.5 months with a one-time cash payment, pricing set by two independent accounting firms, and minimized borrower-harassment risk because it does not re-sell the acquired claims ([KAMCO](https://www.kamco.or.kr/portal/contents.do?mId=0206030000)). **Does the seller actually lose money?** Not necessarily, and the data here is the reassuring part for collateral-backed pools. The sale price is a discount, but recovery against good collateral accrues over time and can exceed the purchase cost. The clearest historical case: KAMCO's post-1997-crisis NPL resolution fund recovered about ₩48.1 trillion against ₩39.2 trillion invested — roughly 123% ([KAMCO](https://www.kamco.or.kr/portal/contents.do?mId=0303030000)). More recently, NPL investors' vintage-by-vintage recovery curves climb as collateral is worked out; some mature vintages exceed 100% of cost (illustrative: anonymized buyer vintages in the report climb from the teens toward 90%+ of cost as they season, with the most mature exceeding 100%) ([Samil PwC, 2024 NPL market, as of 2024-09-30](https://www.pwc.com/kr/ko/insights/issue-brief/samilpwc_2024-npl-market.pdf)). The market is also deep and liquid, which matters for whether this exit actually exists when you need it. Korean first-tier banks sold a record ₩8.3 trillion of NPLs in 2024, and the buyer side is concentrated among established players (UAMCO ~45%, with Daishin F&I, Hana F&I, Kiwoom F&I, and Woori F&I making up most of the rest) ([Samil PwC, as of 2024-12-31](https://www.pwc.com/kr/ko/insights/issue-brief/samilpwc_2024-npl-market.pdf)). ### Auction vs. NPL sale, side by side | Dimension | Court auction | NPL sale | |---|---|---| | What is recovered | The property, converted to cash via the court | The loan claim, sold to a third party | | Who runs it | The court, on the creditor's petition | A buyer (AMC / SPC / KAMCO) after purchase | | Timing to cash | ~6–9 months (security auction) | Days to ~1.5 months for the seller's cash; buyer works out collateral over years | | Price/recovery driver | Auction sale-to-appraisal ratio (낙찰가율, auction sale-to-appraisal ratio) | Sale price as a discount to unpaid principal (OPB) | | Best for | Holding to full collateral value | Crystallizing loss and freeing liquidity now | *Sources: auction procedure and timing ([easylaw.go.kr](https://easylaw.go.kr/CSP/CnpClsMain.laf?popMenu=ov&csmSeq=306&ccfNo=1&cciNo=1&cnpClsNo=3); [Mirae Auction](https://www.mkauction.com/data/procedure.html)); NPL structure, timing, and recovery ([Samil PwC, 2024 NPL market](https://www.pwc.com/kr/ko/insights/issue-brief/samilpwc_2024-npl-market.pdf); [KAMCO](https://www.kamco.or.kr/portal/contents.do?mId=0206030000)).* ## What if the servicer itself fails? The backup servicer A separate risk sits alongside borrower default: what if the company collecting the loans — the servicer — fails? This is addressed by a backup servicer, a standby third party pre-designated to take over collection if the primary servicer defaults, becomes insolvent, or breaches performance standards, so that loan administration continues without interruption ([Concord, backup servicing](https://concordfinance.com/backup-servicing)). For an investor, the backup servicer mitigates a specific, named exposure — servicer risk, the risk that if the servicer goes down, borrower repayments are delayed or shrink on their way to investors. Its purpose is to preserve continuity of cash flows with minimal interruption and to hedge servicer credit risk ([Concord](https://concordfinance.com/backup-servicing); [Wilmington Trust, roles in a structured finance deal](https://www.wilmingtontrust.com/library/article/essential-roles-in-a-structured-finance-deal)). Backups are graded by readiness — "hot/warm" backups can transfer servicing faster than a "cold" one, which incurs more delay ([Academy Securities](https://academysecurities.com/wp-content/uploads/Securitized_Special_Topics_Backup_Servicer.pdf)). Rating agencies such as S&P and Moody's frequently require backup-servicing arrangements to assign high ratings to securitized portfolios, precisely because they keep loans properly managed if the primary servicer hits trouble ([Fin Principal](https://www.finprincipal.com/what-is-backup-servicing/)). This is not a foreign concept bolted onto a Korean structure — Korean law builds in the same logic in two places: - **Securitization law.** Under Korea's Asset-Backed Securitization Act (Art. 10), a securitization vehicle must entrust asset management to a servicer (자산관리자, servicer). Critically, that servicer must keep the entrusted assets separate from its own and on separate books; if the servicer goes bankrupt, the entrusted assets do not form part of its bankruptcy estate, the vehicle can demand their return, and the servicer's own creditors cannot seize them ([Asset-Backed Securitization Act](https://ko.wikisource.org/wiki/%EB%8C%80%ED%95%9C%EB%AF%BC%EA%B5%AD_%EC%9E%90%EC%82%B0%EC%9C%A0%EB%8F%99%ED%99%94%EC%97%90_%EA%B4%80%ED%95%9C_%EB%B2%95%EB%A5%A0)). This bankruptcy-remoteness is the legal foundation that lets assets be pulled back from a failed servicer and handed to a backup. - **P2P / online-lending law.** Korea's online-investment-linked finance regime effectively codifies the backup-servicer idea. The regulator instructs investors to check "whether a contract is in place to entrust wind-down work (debt collection, distribution of repayments) to a credible external institution in case the platform operator ceases business" ([Korea.kr policy briefing](https://www.korea.kr/news/policyNewsView.do?newsId=148890242)). The statute allows an operator to collect directly or to delegate collection to a licensed debt-collection agency ([FSC](https://fsc.go.kr/po010105/75829)) — i.e., a legal basis for collection continuity if the operator has an incident. For root64, whose underlying assets are originated and serviced by an online lender, this is the structural answer to "what if the operator stops": collection does not depend on a single firm staying solvent. ## How much collateral cushion is really there? Korean apartment history The recovery numbers above only matter if the collateral holds value. Korean apartments are a liquid, heavily-measured asset — but their value is volatile, and recovery at auction swings with the cycle. Both facts argue for a conservative LTV cap rather than complacency. Two authoritative price series anchor the picture. The Korea Real Estate Board's national house-price survey is the official state-approved index (monthly and weekly), with the current base set at June 2021 = 100 ([Korea Real Estate Board / e-NARA Indicators (Statistics Korea)](https://www.index.go.kr/unity/potal/main/EachDtlPageDetail.do?idx_cd=1240)). KB Real Estate's series runs back to 1986 — the longest domestic house-price history ([KB Real Estate data hub](https://data.kbland.kr/kbstats/wmh)). The volatility is real: on the Korea Real Estate Board series, nationwide annual home-price change ran +5.36% (2020) → +9.9% (2021, a surge) → −4.68% (2022) ([e-NARA Indicators](https://www.index.go.kr/unity/potal/main/EachDtlPageDetail.do?idx_cd=1240)). 2022 was the steepest apartment decline since the index began, with Sejong down 12.0% and Seoul down 4.9% for the year ([Seoul Economic Daily, 2022-12-19](https://www.sedaily.com/NewsView/26EYOU3544)). Auction recovery — the sale-to-appraisal ratio — is the realized, transaction-based measure of collateral value, and it is more volatile still: | Period (Seoul apartments) | Auction sale-to-appraisal ratio | |---|---| | 2023 (annual avg.) | 82.5% | | 2024 (annual avg.) | 92.0% | | 2025 (annual avg.) | 97.3% | | 2025-10 | 102.3% (first re-break above 100% since June 2022) | | 2026-02 | 101.7% | *Sources: 2023–2025 annual averages ([Munhwa Ilbo, 2026-01-06](https://www.munhwa.com/article/11558794)); Oct-2025 re-break of 100% ([Hankyung, 2025-11-02](https://www.hankyung.com/article/202511028150i)); Feb-2026 ([Newspim, 2026-03-09](https://www.newspim.com/news/view/20260309000223)). Data compiled by GG Auction.* Two cautions follow directly from this data. First, Seoul is not Korea: outside the capital, ratios are lower (e.g., 2026 Q1 Gyeonggi apartments ~87–88%, Incheon ~80% range) ([Sedaily](https://www.sedaily.com/article/20053158); regional figures lower-confidence). Second, the Seoul ratios in the table above sit well above the nationwide picture: the ratio swings ~15 percentage points across a three-year window and fell to roughly 69% nationwide at the Q4 2024 trough ([Samil PwC, 2024 NPL market](https://www.pwc.com/kr/ko/insights/issue-brief/samilpwc_2024-npl-market.pdf)). A 70% LTV cap is the structural response to exactly this: it is sized so that even a meaningful drawdown in auction recovery leaves headroom between the loan balance and the realizable collateral. The point of the cap is not that prices always rise — it is that they don't, and the cushion is set for the years they don't. ## Where does title insurance fit? Title insurance is required on each root64 real-estate-secured loan; it protects the lender's mortgage claim against defects in the property's title (forged documents, double-sales, fraud, and prior encumbrances), and is a meaningful protection in Korea specifically because Korean land registration does not carry "public credibility" — relying on the register alone does not guarantee you acquire the right ([Korean Wikipedia, title insurance](https://ko.wikipedia.org/wiki/%EA%B6%8C%EC%9B%90%EB%B3%B4%ED%97%98); [First American Korea](https://www.firstam.co.kr/Service)). We cover how title insurance works in Korea, and how it differs from the US lender's-policy model, in a separate post. --- *Scope note: This post explains general Korean default and recovery mechanics from public legal, court-auction, and market sources — not root64's own results. root64's portfolio performance (delinquency, default, realized loan-level LTV) is out of scope for this public post and requires separate disclosure. The Hong Kong tokenization tier referenced elsewhere on this blog is planned, not yet formed, and contingent on regulatory clearance.*https://root64.io/blog/title-insurance-korean-real-estate-lending/https://root64.io/blog/title-insurance-korean-real-estate-lending/Title insurance protects a lender against losses from defects in a property's title — forgery, double-selling, undiscovered prior claims. Here is what it covers, how it backstops a mortgage in Korea, and why root64 requires it on every real-estate-secured loan.Mon, 15 Jun 2026 00:00:00 GMTTitle insurance is property insurance that compensates a lender for losses from title defects — forged documents, fraud, double-selling, or undiscovered prior liens. In Korea, where the property register carries no public-faith effect, a lender's mortgage can be undermined by such defects. A lender-protecting title policy backstops the mortgage; root64 requires one on its real-estate-secured loans. ## What is title insurance? Title insurance (권원보험, also called a real-estate title policy in Korea) is a property-insurance contract that compensates the insured — a lender or an owner — for losses caused by defects in the title to a property ([Wikipedia, title insurance, as of Jun 2026](https://ko.wikipedia.org/wiki/%EA%B6%8C%EC%9B%90%EB%B3%B4%ED%97%98)). A "title defect" is anything that makes the ownership or the security interest legally weaker than the records suggest — and unlike most insurance, it covers events that already happened in the past but have not yet surfaced, not future accidents. There are two kinds of policy, and the distinction matters for an investor: - An **owner's policy**, bought by a buyer or seller to protect their own ownership. - A **lender's policy** (in Korea, a mortgage title policy (저당권용 권리보험)), bought to protect the bank or financing institution that lent against the property ([Wikipedia, title insurance, as of Jun 2026](https://ko.wikipedia.org/wiki/%EA%B6%8C%EC%9B%90%EB%B3%B4%ED%97%98)). root64's loans are real-estate-*secured* lending, not property purchases — so the relevant instrument is the lender's policy. It exists to protect the creditor's claim, which in root64's structure is ultimately what investors are exposed to. ## What does a title policy actually cover? It covers losses from hidden title defects — forged documents, fraud, an unauthorized seller, double-selling, and prior claims that surface after the deal closes. These are exactly the failures that no amount of careful underwriting at origination can fully rule out, because they turn on facts that are not visible on the face of the register. The table below lists the defect categories a Korean lender-protecting policy typically addresses. | Covered defect | What it means for the lender's claim | |---|---| | Forged documents | Falsified register extracts, title deeds, or ID used to create the loan ([Hana Insurance, as of Jun 2026](https://www.hanainsure.co.kr/w/product/enterpriseWealth/realEstateGeneralIntro)) | | Fraud or duress | The transaction was procured by deception or coercion ([Hana Insurance, as of Jun 2026](https://www.hanainsure.co.kr/w/product/enterpriseWealth/realEstateGeneralIntro)) | | Unauthorized seller | A sale by someone with no authority to sell (무권대리, unauthorized agency) ([Hana Insurance, as of Jun 2026](https://www.hanainsure.co.kr/w/product/enterpriseWealth/realEstateGeneralIntro)) | | Double registration / double-selling | The seller sold the same property twice; the insured fails to acquire or keep title after paying ([Hana Insurance, as of Jun 2026](https://www.hanainsure.co.kr/w/product/enterpriseWealth/realEstateGeneralIntro)) | | Undiscovered prior claims | A provisional attachment or injunction (가압류·가처분) registered before ownership transfer completes ([Hana Insurance, as of Jun 2026](https://www.hanainsure.co.kr/w/product/enterpriseWealth/realEstateGeneralIntro)) | | Other title-affecting rights | Statutory liens, competing mortgages, tax-driven enforcement, easements ([Wikipedia, title insurance, as of Jun 2026](https://ko.wikipedia.org/wiki/%EA%B6%8C%EC%9B%90%EB%B3%B4%ED%97%98)) | *Source: Korean title-insurance product disclosures (Hana Insurance; Wikipedia, title insurance), as of June 2026. Coverage scope varies by policy; this is a category-level summary, not a substitute for specific policy terms.* The lender's-policy version focuses these protections on the security interest itself: a Korean mortgage title policy compensates a financing institution for losses arising from the mortgage and from the *loss of the mortgage's priority* ([First American Korea, as of Jun 2026](https://www.firstam.co.kr/Service)). In other words, it backstops not just whether the lender has a valid lien, but whether that lien ranks where the lender believed it did. ## Why does this matter for a lender in Korea specifically? Because in Korea the property register does not carry public-faith effect. Korean law requires registration as a condition for changes in property rights, but — as a well-established principle of Korean property law — it does not grant the register public faith (공신력): relying on an entry that turns out to be invalid may leave you without the right (a point examined in Korean property-law scholarship, [KCI](https://www.kci.go.kr/kciportal/ci/sereArticleSearch/ciSereArtiView.kci?sereArticleSearchBean.artiId=ART002938317), as of Jun 2026). That is the crux of the lender's exposure. A maximum-amount mortgage (근저당권) is registered against the property, and on its face it looks secure — but if the underlying title is defective for one of the reasons above, the mortgage's validity or priority can be undermined after the fact. A title policy is the mechanism that transfers that residual risk off the lender. As one industry explainer puts it, lenders take out a mortgage title policy precisely because the register's lack of public faith means a relied-upon entry can fail, and the policy shifts the resulting loss to the insurer to shore up the lender's recovery ([RE/MAX Korea, as of Jun 2026](https://remaxkorea.co.kr/%EB%B6%80%EB%8F%99%EC%82%B0%EC%83%81%EC%8B%9D3-2404/)). This is also why the instrument is useful here. Title insurance developed to address the limits of records-based land systems, and the same logic applies in Korea, where the register carries no public faith (discussed in Korean property-law scholarship, [KCI](https://www.kci.go.kr/kciportal/ci/sereArticleSearch/ciSereArtiView.kci?sereArticleSearchBean.artiId=ART002938317), as of Jun 2026). ## How does title insurance complement the mortgage? The two are not substitutes — they protect against different failure modes, and a careful lender wants both. - The **maximum-amount mortgage** secures the right to be repaid *if the borrower defaults*. It is the enforcement engine: it gives the lender priority in an auction and a defined place in the distribution waterfall. (In a Korean court auction, a mortgagee is a preferential-payment creditor — paid after enforcement costs, minimum-protection claims, and certain taxes, but ahead of general tax, public charges, and unsecured creditors — per the Civil Execution Act distribution order ([Korea easylaw.go.kr, as of Jun 2026](https://easylaw.go.kr/CSP/CnpClsMain.laf?popMenu=ov&csmSeq=629&ccfNo=5&cciNo=2&cnpClsNo=5)).) - **Title insurance** protects against the mortgage itself being *defective or out-ranked* because of a title flaw that predates the loan — forgery, fraud, an unauthorized grantor, a hidden prior claim. Put simply: the mortgage handles *the borrower not paying*; title insurance handles *the security turning out to be flawed*. The first is a credit event you underwrite for; the second is a legal-defect event you insure against. A mortgage with a defective title is worth far less than its registered position suggests — and that gap is exactly what a lender's policy is designed to close. ## What is the state of title insurance in Korea today? It is an established, if optional, product — and dedicated lender-protecting policies are actively sold. A handful of providers operate in the Korean market, led by **First American Title Insurance Company (FATIC) Korea Branch**, alongside Hana Insurance and others ([First American Korea, as of Jun 2026](https://www.firstam.co.kr/)). First American's parent FATIC is described as a 120-plus-year-old title-insurance specialist based in California; its Korea branch reported roughly 20 years of local operation and about 1.7 million cumulative policy applications as of 1 January 2021 ([First American Korea, as of Jun 2026](https://www.firstam.co.kr/)). Crucially for lenders, dedicated lender-side policies exist beyond owner coverage. First American sells a mortgage title policy for financial institutions, covering losses from the mortgage and its priority, and a separate jeonse-loan (전세자금대출) title policy covering losses where a jeonse-loan claim fails due to lease-contract defects — both offered to lending institutions (corporate policyholders only) ([First American Korea, as of Jun 2026](https://www.firstam.co.kr/Service)). How that compares with the United States is worth understanding, because the role title insurance plays differs by market: | | United States | Korea | |---|---|---| | Land-records system | Deed-recording system; title rests on recorded documents, not a state-guaranteed register | Registration required for rights, but the register has no public faith ([KCI, as of Jun 2026](https://www.kci.go.kr/kciportal/ci/sereArticleSearch/ciSereArtiView.kci?sereArticleSearchBean.artiId=ART002938317)) | | Lender's policy | In practice a standard requirement for mortgage lenders ([First American, as of Jun 2026](https://www.firstam.com/home-buying-guide/Types-of-Title-Insurance-Policies-Owner-vs-Lender/)) | Available and sold to institutions, used selectively rather than universally ([First American Korea, as of Jun 2026](https://www.firstam.co.kr/Service)) | | Refinancing | A lender typically requires a policy when buying or refinancing ([Land Title Guarantee, as of Jun 2026](https://www.ltgc.com/resources/lenders-policy-101/)) | Used as a supplementary safeguard, not a standing requirement | *Source: First American (US and Korea), Land Title Guarantee, KCI scholarly research, as of June 2026.* The key takeaway: in the US the lender's policy is effectively a market-wide default; in Korea it remains an optional, supplementary safeguard that a prudent lender can choose to require. ## Why does root64 require title insurance on real-estate collateral? root64 chooses to make it mandatory rather than optional. Across root64's real-estate-secured product parameters, a title policy is set as a *required* condition on the collateral. The collateral profile is built for quality (for example, KB-priced apartments and mixed-use residences in complexes of 200-plus units, with the mortgage capped at a maximum loan-to-value of 70%), and the mandatory title policy is the legal-defect backstop layered on top of that profile. The logic follows directly from the points above. Because the Korean register carries no public faith, even a well-underwritten, conservatively-LTV'd mortgage retains a residual risk that a hidden title defect undermines its validity or priority. A title policy transfers that specific risk to an insurer. For investors whose exposure ultimately rests on these loans' security, requiring it — rather than leaving it to deal-by-deal discretion — converts an idiosyncratic legal risk into a covered, standardized one. A note on scope: this article describes a structural safeguard, not a performance promise. Title insurance addresses *title-defect* risk on the collateral; it does not eliminate credit risk (whether borrowers repay), market risk (whether collateral values hold), or recovery-timing risk (how long enforcement takes). It is one defined layer in a stack of protections, not a guarantee of return. root64's Hong Kong tokenization tier is planned and contingent on regulatory clearance.https://root64.io/blog/securities-account-collateralized-loans-risk-controls/https://root64.io/blog/securities-account-collateralized-loans-risk-controls/Securities-account-collateralized loans (stock loans) are secured by a liquid, daily-priced collateral pool managed in real time by a third-party risk management system. Here is how the RMS, forced liquidation, and an indemnification layer work together to structurally lower credit loss — and where the risk still sits.Mon, 15 Jun 2026 00:00:00 GMTSecurities-account-collateralized loans (stock loans) are secured by listed Korean stocks and ETFs in a 100% cash-margin account, managed in real time by a third-party risk management system (RMS). When the maintenance ratio falls below roughly 120-125%, the position is force-liquidated automatically; a separate indemnification layer makes the RMS provider liable for collateral-management failures. ## What is a securities-account-collateralized loan, and why is its risk profile different? It is a loan secured by the listed securities held in a borrower's brokerage account — in Korea, commonly called a stock loan (스탁론) — and its risk profile is unusual because the collateral is liquid and re-priced every trading day. Unlike real estate, where the collateral's value is only tested when it is sold, a securities account can be marked to market continuously and sold in minutes. That single property is what lets the structure control credit loss far more tightly than most secured lending. The collateral is not a passive lien. It sits inside a tightly governed account whose eligible holdings, leverage, and liquidation triggers are all defined in advance and enforced automatically by a risk management system. This post walks through how that system works, how a delinquency is resolved end-to-end, and how an indemnification layer absorbs losses caused by collateral-management failure — and then where the residual risk still lies. Two framing notes before the mechanics. First, root64 holds securities-account-collateralized loans as one of its asset types in its Korean special-purpose company; what follows describes the general market mechanism, not deal-level terms. Second, these are loan receivables (대출채권) — the return comes from a borrower repaying principal and interest, with the securities account as collateral, not from any market position root64 takes. ## What does the risk management system (RMS) actually do? The RMS is a third-party system that controls and manages the collateral — the borrower's securities account — in real time, rather than the lender doing so manually. It is what turns a pile of stocks into a governed, rules-bound collateral pool: it restricts which securities can be bought or held, monitors the account's value continuously, and triggers automatic liquidation when the collateral falls below a set threshold. This division of labor is a deliberate control. The party that originates and services the loan is not the same party that polices the collateral minute by minute; an independent risk-management function does that. The Korea Financial Investment Association (KOFIA) describes the same arrangement from the broker side: in a linked-credit stock loan, the customer pledges the brokerage-account assets to the lender, and the securities firm manages the collateral through a linked-credit risk-management system ([KOFIA, linked-credit trading rules](https://law.kofia.or.kr/service/law/lawFullScreenContent.do?seq=262&historySeq=990&gubun=his&tree=part), as of June 2026). The control framework rests on an industry standard, not on any single lender's house rules. The Korea Financial Investment Association (KOFIA) operates a best-practice standard for managing credit-trading risk — covering per-customer credit limits, differentiated margin and maintenance ratios, mandatory customer notification when the maintenance ratio drops sharply, and criteria for forced liquidation ([KOFIA Best-Practice Standard for Credit-Trading Risk Management](https://law.kofia.or.kr/service/law/lawFullScreenContent.do?seq=228&historySeq=611), as of June 2026). Account-operation rules for stock-loan products reference KOFIA's linked-credit best-practice standard as their basis ([Shinhan Securities terms](https://file.shinhansec.com/filedoc/clause/k_40.pdf), as of June 2026). > A note on sourcing: this post relies only on independently verifiable standards — KOFIA's credit-trading risk-management best-practice standard and the broader Financial Investment Company risk-management standard (the latter revised repeatedly through 2025) — rather than on any single dated ruleset. ## Why is 100% cash margin and a screened security list the first line of defense? Because the structure removes leverage and volatility from the collateral itself before any loan-level control kicks in. The borrower's account runs on 100% cash margin — no credit (margin) buying, no short selling, no unsettled-amount (미수) trading inside the collateral account. That means the collateral cannot itself be a leveraged position that blows up faster than the loan against it. On top of that, only certain securities are eligible to serve as collateral, and a long list of risky categories is blocked from being bought or held: | Eligibility dimension | Allowed | Blocked / restricted | |---|---|---| | Margin basis | 100% cash margin | Credit (margin) buying, short selling, unsettled-amount trades | | Tradable markets | KOSPI, KOSDAQ general stocks, ETFs | KONEX (third market), ELW, bonds, unlisted shares | | Issuer / event status | Ordinary listed names | Administrative-issue (관리종목) stocks, trading-suspension-pending, ex-rights, capital reduction / merger / stock split, liquidation trading (정리매매), new listings | | Investor-alert flags | — | Investment-caution / alert / warning / risk / short-term-overheating designations | | Fundamentals / size | — | Below-par-value, market cap under KRW 10 billion, RMS-designated risk names | *Source: general stock-loan account-operation rules and RMS criteria; categories per the securities-account-collateral risk framework summarized from KOFIA-referenced operating rules ([Shinhan Securities terms](https://file.shinhansec.com/filedoc/clause/k_40.pdf), as of June 2026). Specific eligibility parameters are product-dependent.* The logic is that each excluded category is a known source of either illiquidity (you cannot reliably sell it fast) or discontinuous price risk (it can gap down with no chance to liquidate in between). By confining the collateral to liquid, continuously traded names and stripping out leverage, the structure ensures the one thing forced liquidation depends on: that the collateral can actually be sold near its last marked price when the trigger fires. ## How does forced liquidation work, and why does it structurally lower credit loss? When the account's maintenance ratio — collateral value divided by loan balance — falls below roughly 120-125%, the position is liquidated automatically. The collateral is sold to repay the loan before the account value can fall through the loan principal. This is the core mechanism, and it is why a daily-priced, liquid collateral pool produces structurally lower credit loss than illiquid collateral. The intuition is a buffer that is enforced continuously rather than tested once. The loan starts meaningfully over-collateralized — leverage is banded by account size (loan-to-collateral ratios in the region of 300% / 250% / 200% across value tiers), so the maintenance ratio sits well above 100% by design. As markets move, the RMS marks the account daily; if the cushion erodes to the maintenance threshold, the system sells. Because the threshold (≈120-125%) sits above 100%, liquidation is designed to happen while collateral still exceeds the debt — closing the gap before it becomes a loss, not after. Korea's Financial Supervisory Service describes this exact mechanism in its March 2026 consumer alert on stock loans: it characterizes a stock loan as a high-risk product allowing borrowing up to roughly three times the collateral, and warns that if the account's valuation falls below the maintenance ratio (commonly around 120%), the shares are force-sold regardless of the investor's wishes ([Newspim, citing FSS consumer alert, 13 Mar 2026](https://www.newspim.com/news/view/20260313001096)). The same daily-priced-collateral logic underpins ordinary margin trading: maintenance ratios vary by product (commonly around 140% for general credit trades), and the standard sequence is D-day breach → D+1 grace for additional collateral → D+2 forced liquidation (반대매매) ([KB Securities, forced-liquidation explainer](https://kbthink.com/stock/stock-forced-liquidation.html), as of June 2026). The contrast with illiquid collateral is the whole point. Forced liquidation is the same loss-crystallizing mechanism applied to all leverage products in Korea, and in volatile markets it can amplify selling pressure — a real systemic caveat at the market level. But from a single loan's credit-loss perspective, the ability to sell *now*, at a daily-known price, is exactly what real-estate collateral lacks: a Korean property must go through a court auction that takes months, during which the collateral's value is untested and the recovery uncertain. ## How is a delinquency resolved end to end? The process runs on a defined timeline, and — critically — most of it is settled by selling liquid collateral, not by chasing the borrower. The general mechanism proceeds in stages: | Stage | Trigger / timing | What happens | |---|---|---| | 1. Delinquency | Payment missed | Account flagged; cure period begins | | 2. Forced liquidation | ~30 days delinquent | Collateral securities are force-sold | | 3. Compulsory repayment | T+2 settlement of the sale | Sale proceeds settle and are applied to repay the loan | | 4. Collection | From compulsory repayment to ~60 days | Residual balance, if any, is pursued through collection | | 5. Indemnification notice | 60+ days | If a shortfall traces to collateral-management failure, a damages notice is issued to the RMS provider | | 6. Indemnification (subrogated payment) | Within ~1 month of notice | The RMS provider makes a subrogated payment for the covered loss | *Source: general stock-loan delinquency-management mechanism (industry process). Specific deal terms, cure periods, and figures are product-dependent and are not disclosed here.* The shape of this timeline is what makes the asset distinctive. By around day 30, the primary recovery action — selling the collateral — has already happened, and settlement follows two trading days later (T+2). Compare that to a real-estate-secured loan, where day 30 is roughly when the borrower has only just lost the benefit of time on the loan and the collateral has not been touched. In the securities case, the liquid collateral does most of the recovery work early; the later stages (collection, then indemnification) exist to address whatever residual remains after the collateral is sold. ## How does the indemnification layer absorb losses caused by collateral-management failure? The RMS provider stands behind its own collateral management: where a loss results from a failure to manage the collateral as the rules require, the provider indemnifies it — in effect, an "insurance"-like backstop sitting behind the loan. This is the piece that distinguishes a securities-account loan from simply lending against a stock account yourself. The party responsible for policing the collateral is financially on the hook if that policing fails. In the general structure, that backstop has several reinforcing components: | Component | What it is | What it protects against | |---|---|---| | Collateral-management indemnification | The RMS provider's liability (subrogated payment) for losses from failing to manage collateral per the rules | The RMS not liquidating when it should have, allowing a loss the rules were designed to prevent | | Loss-coverage deposit | A reserve posted by the RMS provider — an initial deposit plus a periodic top-up keyed to month-end balances | Funds the indemnification obligation so it is not just a promise | | Loss provision / liability reserve | An accounting reserve set against potential collateral-management losses | Ensures the obligation is recognized and reserved against on the books | *Source: general securities-account-collateral indemnification structure (industry mechanism). The identity, financials, and indemnification history of any specific RMS partner are not disclosed here.* Read together, these turn collateral-management quality into a transferred risk. The forced-liquidation system is designed to prevent a loss in the first place; the indemnification layer is what happens if the system fails to do its job — the resulting loss is shifted to the RMS provider rather than borne by the loan. Conceptually this is the same idea as a backup or special servicer in structured finance, where a separately accountable party absorbs servicer risk so that investors are not exposed to a single operator's failure ([Concord Servicing, What Is Backup Servicing](https://concordfinance.com/backup-servicing), as of June 2026). It is worth being precise about the limit of this protection. The indemnification covers losses *caused by collateral-management failure* — the RMS not enforcing the rules it is supposed to enforce. It is not a guarantee against market risk in general, and it is not a promise that every loan is whole. A gap-down that the rules could not have prevented, or a market-wide dislocation, is a different category of risk. (root64 does not disclose, and this post does not state, any specific provider's indemnification track record — that is confidential.) ## Where does the residual risk still sit? Even with all of the above, this is a credit asset, and three residual risks remain. First, gap risk: forced liquidation assumes the collateral can be sold near its last marked price, but a security can gap down between marks — on bad news, a limit-down move, or a halt — so liquidation can occur below the maintenance level, leaving a shortfall. The eligible-security screening is designed to minimize exactly this (excluding illiquid and event-driven names), but it cannot eliminate it. Second, correlated-market risk: forced liquidation across many leveraged accounts at once can amplify a sell-off, the systemic caveat noted above. Third, the indemnification layer itself carries counterparty risk — it is only as strong as the RMS provider's ability to pay, which is precisely why the loss-coverage deposit and loss provision exist to pre-fund the obligation. The honest summary is that securities-account-collateralized lending does not remove credit risk; it restructures it. It replaces the slow, uncertain recovery of illiquid collateral with fast, daily-priced liquidation, and it transfers collateral-management failure to an indemnifying party. What remains is the residual — gap risk, correlated-market risk, and indemnifier counterparty risk — which is far narrower than the raw credit risk of an unsecured or illiquidly secured loan, but is not zero.https://root64.io/blog/how-foreign-investors-access-korean-loan-assets/https://root64.io/blog/how-foreign-investors-access-korean-loan-assets/Foreign investors cannot buy Korean loan assets directly in Korea. Access requires a structure that keeps the assets in Korea and connects capital from outside it. Here are the three conditions that have to be met, and what is live today versus planned.Fri, 12 Jun 2026 00:00:00 GMTForeign investors can't buy Korean loan assets directly: the right to receive a loan's principal and interest can only be transferred to qualified transferees, and Korea's standardized foreign-access regime covers listed securities, not loan receivables. Access requires a structure — a compliant Korean asset holder, an offshore participation route, and an independent transparency layer. ## How does a foreign investor actually reach Korean loan assets? Not by buying them directly in Korea. Korean loan assets can't be purchased from abroad the way a foreign investor might buy a listed bond — the asset has to stay in Korea, held by a compliant domestic entity, while capital is connected to it from outside. Access is a question of structure, not of finding the right order ticket. There is a reason that distinction is so sharp. Korea has a well-developed, standardized channel for foreign investors to buy *listed securities* — its foreign portfolio investment regime, run through local custodians and brokers, covers all shares listed on the Korea Exchange and KOSDAQ, listed bonds, exchange-traded derivatives, beneficiary certificates, and short-term money-market instruments ([Bank of Korea, Foreign Portfolio Investment Procedures](https://www.bok.or.kr/eng/main/contents.do?menuNo=400192), accessed 2026-06-15). Loan receivables are not in scope of that regime. The "order ticket" exists for securities; there is no equivalent off-the-shelf channel for buying domestic loan assets. That is why access has to be structural rather than transactional. That single design point drives everything below. A foreign professional investor does not reach these assets by sending money into Korea and buying loans; they reach them through an arrangement that holds the assets domestically and links offshore capital to the economics of those assets. This post walks through what has to be true for that link to exist, and what part of it is live today versus planned. ## What has to be true for a foreign investor to get exposure? Three conditions have to be met together. Miss any one and there is no compliant path: the assets have to be held by a compliant entity inside Korea, capital has to be connected through an offshore participation route, and the investor has to be able to verify the assets independently. | Condition | What it requires | Status today | |---|---|---| | 1. Compliant Korean asset holder | A domestic entity that can lawfully hold the loan assets and satisfy Korea's transfer and custody rules | Live — a Korean special-purpose company (SPC) holds the assets | | 2. Offshore participation route | An entity outside Korea through which global capital connects to the Korean-held assets | Planned — a Hong Kong vehicle, not yet formed, contingent on regulatory clearance | | 3. Independent verification | A way for the investor to check the state of the assets without relying solely on periodic reports | In build — an on-chain transparency layer | *Source: root64 business structure and product strategy, as of June 2026.* Each condition exists for a different reason. Condition 1 answers a legal requirement — who is allowed to hold the asset in Korea. Condition 2 answers a connectivity requirement — how dollars or stablecoins outside Korea reach won-denominated assets inside it. Condition 3 answers a trust requirement — how an investor abroad confirms the assets are real and performing. The sections that follow take each in turn. ### Condition 1: the assets are held by a compliant Korean entity The first condition is already live. In root64's structure, a Korean special-purpose company (SPC) holds the loan assets domestically — a separate, bankruptcy-remote entity, not on 8percent's balance sheet. Two asset types are held this way today (as of June 2026): real-estate-secured consumer loans and securities-account-collateralized loans. The SPC matters because of who is allowed to hold the asset. The economic right to a loan's repayments — the right to receive principal and interest (원리금수취권) — can only be transferred to qualified transferees under Korea's online-lending rules. The Korean SPC is that qualified transferee. A foreign buyer is not. So the asset has to live with the SPC; it cannot live with the investor. ### Condition 2: an offshore route connects global capital The second condition is planned, not live. Even with the assets correctly held in Korea, there has to be an entity outside Korea that global professional investors can actually participate through — because the domestic side runs on Korean-won accounts and Korean rules that non-residents can't easily plug into. How hard is "can't easily plug into"? The friction is concrete even for Korea's friendliest asset class. To trade listed securities, a foreign investor still routes through Korean intermediaries: foreign investors are recommended to designate a standing proxy — a securities company, bank, or the Korea Securities Depository — to handle account opening, order placement, and settlement on their behalf, alongside accounts held with a local custodian and a broker ([Bank of Korea, Foreign Portfolio Investment Procedures](https://www.bok.or.kr/eng/main/contents.do?menuNo=400192), accessed 2026-06-15). Even Korea's recent liberalization of bond-market access kept this intermediated shape: Clearstream's 2024 direct link let eligible investors "settle and safekeep KTBs and MSBs directly through their existing Clearstream accounts" rather than opening local accounts ([Clearstream, direct link to South Korea](https://www.clearstream.com/clearstream-en/newsroom/240701-4012534), 2024-07-01) — a notable easing, but one that still operates through a structured channel. Even the easiest on-ramp into Korea is intermediated; loan assets have no comparable on-ramp at all. Holding won itself is its own friction. Non-residents transact Korean won through designated account types, not an ordinary deposit account: from an ordinary non-resident won account, "notification to the BOK is required for overseas remittance of the withdrawn funds," whereas only the non-resident *free* won account lets non-residents "convert funds in this account into foreign currency and transfer the proceeds abroad" ([Bank of Korea, Internationalization of the Korean Won](https://www.bok.or.kr/eng/main/contents.do?menuNo=400195), accessed 2026-06-15). These are procedural frictions on connecting offshore capital to won-denominated assets — not a prohibition, but a reason the connection has to be engineered rather than improvised. In root64's model that offshore route is a Hong Kong vehicle. It is planned and not yet formed, and any token issuance through it is contingent on regulatory clearance. It is not operating today. Connecting global capital to local-currency assets through an offshore pooling vehicle is itself a standard fund-structuring pattern — an offshore feeder that aggregates international capital into the strategy holding the underlying assets ([Corporate Finance Institute, master-feeder structure](https://corporatefinanceinstitute.com/resources/career-map/sell-side/capital-markets/master-feeder-structure/), accessed 2026-06-15) — so the planned offshore route is a conventional design choice, not a novelty. When people describe root64 as a way for global investors to reach Korean loan assets, this is the tier they mean — and it is the part still ahead, not behind. ### Condition 3: the investor can verify the assets independently The third condition is in build. A foreign investor connecting capital across borders into an unfamiliar asset class needs to confirm the assets are real and performing without taking a single party's word for it. Conventional reporting is periodic, which leaves gaps between reports. root64 addresses this with a transparency layer: cash transactions and investment balances are recorded on a public blockchain, and external verifications — through independent channels such as property-registry checks — are logged on-chain as well. The aim is that an investor can check the state of the assets directly rather than waiting for a monthly report. This layer is being built first, ahead of tokenization. ## What can a foreign professional investor actually do today, and what is still planned? Today, the live elements are the Korean side: a Korean SPC holding two asset types, with capital connected through a pilot arrangement. The tokenized offshore route that would open the structure to global professional investors broadly is planned, not yet available. It is worth being precise here, because the two are easy to conflate. What exists is the asset-holding foundation in Korea and a pilot that proves the connection end to end. What does not yet exist is a live, generally available onboarding product for foreign investors running through the offshore vehicle. There is no live retail product, and there is no open subscription today. | Element | Live today | Planned | |---|---|---| | Korean SPC holding the assets | Yes | — | | Live asset types (real-estate-secured consumer loans; securities-account-collateralized loans) | Yes | — | | On-chain transparency layer | In build | Expanding | | Offshore vehicle (Hong Kong) for tokenized participation | No — not yet formed | Yes, contingent on regulatory clearance | | Generally available foreign-investor onboarding | No | Follows the offshore tier | *Source: root64 business structure and product strategy roadmap, as of June 2026.* The honest summary: the asset-holding tier is real and operating; the offshore tokenization tier that broadens access is on the roadmap and contingent on clearances. root64 serves professional investors only, through private placement — not a public offering. ## How is this different from just sending money to Korea? Sending money to Korea and buying loans directly is not an available path — that is the whole point. There is no defined channel for a non-resident to buy these loan assets off the shelf, and the right to a loan's repayments can't be transferred to an arbitrary foreign buyer in the first place. This is not because Korea is closed. The opposite is true for securities: in December 2023 Korea abolished its three-decade-old foreign-investor pre-registration requirement (the Investment Registration Certificate, or IRC) and replaced it with global-standard identifiers, allowing foreign investors to "make investments in domestically listed securities" using an LEI or passport number instead of pre-registering ([Financial Services Commission press release, 2024-06-21](https://www.fsc.go.kr/eng/pr010101/82511); IRC abolition effective 2023-12-14). That reform applies specifically to *domestically listed securities* — it actively liberalized access to Korea's capital markets while leaving loan receivables outside the scope of any such channel. So the absence of a loan-purchase route is a question of scope, not a statutory ban: the open door is for listed securities, and loan assets simply sit outside it. Two specific things block the direct route. First, the channel itself: there is no defined channel for a non-resident to buy these loan assets directly, and the domestic lending market runs on Korean-won accounts at a domestic institution that non-residents can't easily use — non-residents hold won only through designated account types, with outbound remittance from an ordinary non-resident won account requiring notification to the Bank of Korea ([Bank of Korea](https://www.bok.or.kr/eng/main/contents.do?menuNo=400195), accessed 2026-06-15). Second, the transfer restriction: the right to receive a loan's principal and interest can only move to qualified transferees, and a foreign investor is not one. A structured connection is different in kind. The asset stays with a Korean entity that is a qualified transferee; the foreign investor's capital is connected to the economics of those assets through an offshore route, rather than the investor trying to buy the asset itself. It is the difference between owning the loan in Korea (not possible for a non-resident) and gaining exposure to it through a compliant structure (the path being built). ## How does root64 design that access path? By combining the three conditions into one structure: a Korean SPC holds the assets today, a planned offshore vehicle is designed to connect global capital, and a transparency layer lets investors verify the assets independently. The order is deliberate — the asset-holding foundation and transparency come first, and the offshore tokenization tier is built on top. This is also why root64 describes itself as transparency-first rather than token-first. Many tokenization efforts begin by issuing a token; root64 begins by getting the assets correctly held in Korea and making them independently verifiable, then adds the offshore participation route. For a foreign professional investor, the practical takeaway is that access to Korean loan assets is a structural achievement, not a transaction — and the live pieces of that structure are the ones holding and verifying the assets, with the offshore route still planned.https://root64.io/blog/how-root64-holds-korean-loan-assets/https://root64.io/blog/how-root64-holds-korean-loan-assets/root64's Korean loan assets are held by a Korean special-purpose company — a separate, bankruptcy-remote entity, not on 8percent's balance sheet. Here is how that structure protects investors, and what is planned on top of it.Fri, 12 Jun 2026 00:00:00 GMTroot64's Korean loan assets are held by a Korean special-purpose company (SPC): a separate, bankruptcy-remote entity, not on 8percent's balance sheet. 8percent acts only as originator and servicer and never holds investor funds — its staff cannot access the SPC's bank accounts. A Hong Kong tokenization tier is planned, but not yet formed. ## How does root64 hold its Korean loan assets today? The assets are held by a Korean special-purpose company (SPC) — a separate legal entity whose only job is to hold them. They do not sit on 8percent's balance sheet. Two asset types are held this way today (as of June 2026): real-estate-secured consumer loans and securities-account-collateralized loans. This separation is the structural foundation everything else stands on. Before any transparency record or future token, the first question for an investor is simple: if the operating company runs into trouble, what happens to the assets? root64's answer starts with where the assets legally sit. ## What is a special-purpose company, and why use one? A special-purpose company is an entity created to do one narrow thing — here, to hold the loan assets and nothing else. Because it has a single purpose and no other business, the assets inside it are insulated from the risks of the company that originates and services the loans. The benefit of that insulation is specific. Once assets are genuinely isolated in such an entity, an investor "can rely primarily on the credit risk of the underlying assets and their obligors, rather than the originator's creditworthiness" — a recognized investor protection in structured finance, as the law firm Lucosky Brookman summarizes it ([Understanding Structured Finance Opinions: True Sale and Non-Consolidation](https://www.lucbro.com/news/understanding-structured-finance-opinions-true-sale-and-non-consolidation/), published 16 Apr 2024). That is why a single-purpose entity matters: it lets investors price the loans, not the company behind them. In root64's case the SPC is a standalone Korean entity, legally distinct from 8percent. That distinction is what makes the next property — bankruptcy remoteness — possible. ## What does "bankruptcy remoteness" actually mean here? It means that if 8percent were to fail, the assets in the SPC would not be affected. Because the SPC is a separate legal entity, its assets are not part of 8percent's estate, so 8percent's creditors cannot reach them. This is the same test banking regulators use to decide whether assets are truly isolated. Under the Basel Committee's securitisation framework — the global standard for bank capital rules — assets count as legally isolated only when they are "put beyond the reach of the transferor and its creditors, even in bankruptcy or receivership," and the framework expects a legal opinion confirming that true sale ([Basel securitisation framework, operational requirements for traditional securitisations](https://www.bis.org/bcbs/publ/d374.pdf), published Dec 2014, rev. Jul 2016). root64's SPC is not bank-regulated, but that "beyond the reach of the originator's creditors" standard is the recognized benchmark for what real isolation looks like, and it is the bar this structure is built to clear. The whole point of that isolation is narrow: it lets an investor take on the credit risk of the underlying loans only — not the credit risk of the company that originated them. As the offshore law firm Appleby puts it, bankruptcy remoteness is the "ring-fencing of assets and removing them from the bankruptcy risks of the originator/seller," so that investors "can simply take on the credit risks of the underlying asset" ([Bankruptcy Remoteness in Structured Finance](https://www.applebyglobal.com/publications/achieving-bankruptcy-remoteness-in-structured-finance/), Fiona Chan, published 18 Jun 2025). There is a concrete operational consequence: 8percent's own staff cannot directly access the SPC's bank accounts. The company that originates and services the loans is deliberately kept away from the cash. This is not a promise to behave well — it is a structural constraint on what 8percent is able to do. In structured finance, that constraint is recognized practice, not improvisation: isolation is held in place by what are called separateness covenants, requiring an entity to "maintain separate books, records and accounts," not commingle assets, and conduct business in its own name (Lucosky Brookman, published 16 Apr 2024). Operational separation — not just a separate name on a registry — is what makes the isolation real. ## If 8percent doesn't hold the money, what does it do? 8percent's role is limited by design to originating and servicing the loans — it never holds investor funds. The other functions are carried out by separate parties, so that no single entity both controls the assets and controls the cash. | Party | Role | |---|---| | Korean SPC | Holds the loan assets (bankruptcy-remote, separate from 8percent) | | 8percent | Originates and services the loans; does not hold investor funds | | Fund administrator | Handles the SPC's administration and recording (a third-party accounting firm in the current phase) | *Source: root64 business structure, entity roles, as of June 2026.* Splitting these roles is what lets root64 say that no single party — including 8percent — is the sole point of control. ## How does the SPC come to hold the assets? The SPC participates as a qualified transferee in the market for loan receivables — the right to receive principal and interest on the underlying loans. Rather than 8percent simply selling assets onto its own affiliate, the SPC takes a position in those receivables as an eligible institutional transferee, in the same market other qualified investors trade in. In plain terms: 8percent originates the loan to the borrower, and the economic right to that loan's repayments is what the SPC comes to hold. The precise legal nature of that right — the right to receive principal and interest (원리금수취권) — is worth its own explanation, and we cover it in a separate post. ## What about the Hong Kong unit trust? A Hong Kong vehicle is the planned tokenization tier that would sit above the SPC and serve global professional investors — but it is not yet formed, and any token issuance through it is contingent on regulatory clearance. It is not live today. The shape of that plan follows a standard cross-border pattern rather than a novel one: assets are held in a local asset-holding vehicle, while a separate vehicle is used to connect international capital. Private-credit managers routinely "put in place parallel or subsidiary fund vehicles in different jurisdictions to meet conflicting investor and investee country requirements," keeping the asset-holding layer distinct from the capital-raising layer ([Structuring Private Credit Funds and their Asset Holding Vehicles, The Hedge Fund Journal](https://thehedgefundjournal.com/structuring-private-credit-funds-and-their-asset-holding-vehicles/), Issue 118, published Nov/Dec 2016). That is exactly the separation root64 is designed around: keep the assets onshore in Korea, and connect outside capital through a separate vehicle. For now, the structure that matters is the one that already exists: a Korean SPC holding the assets, separate from the company that originates and services them. Tokenization is designed to be added on top of that foundation, not to replace it.https://root64.io/blog/how-to-verify-root64-on-chain-proofs/https://root64.io/blog/how-to-verify-root64-on-chain-proofs/A reader's guide to root64's transparency layer: what each on-chain record contains, how to read a cash-transaction entry and a verification result on a block explorer, and where the public explorer entry point will be published.Fri, 12 Jun 2026 00:00:00 GMTroot64's transparency layer has two on-chain record types. A cash-transaction record shows the transaction type, a signed amount (sign = inflow or outflow), the balance after, a counterparty type, and a timestamp. A verification record shows the target, the external channel (property registry, KFTC, or bank), and a match, mismatch, or inconclusive result. Both are append-only Ethereum event logs. ## What can you verify about root64 on-chain? Two things: the actual movement of cash in root64's loan pool, and the result of each external check run against that pool. The transparency layer records both as on-chain entries — a cash-transaction record for every money movement, and a verification record for every check against an outside source. This is the first phase of root64, the real-world-asset (RWA) platform built by 8percent. The platform's design principle is "transparency before tokenization": make the underlying Korean loan assets independently checkable first, and tokenize later. This post is the practical companion to that idea — not *why* transparency comes first, but *how* to read the records once you are looking at them. One honest caveat up front: this transparency layer is being built out phase by phase, and the public explorer entry point publishes together with the platform (see the last section). So treat this as a reader's guide to the record formats — what each field means and what it proves — rather than a click-here-now walkthrough. ## How do you read a cash-transaction record? A cash-transaction record captures a single movement of money in the pool, and it is designed so that one line tells you what happened without any outside context. Each record carries: - **Transaction type** — what kind of movement it was (an investor deposit, an investor withdrawal, an internal transfer between the special-purpose company's accounts, and so on). - **Amount, with a sign** — the sign is the direction. A positive amount is money flowing *into* the pool; a negative amount is money flowing *out*. You do not need a separate "direction" field; the sign carries it. - **Balance after** — the account balance immediately after this transaction, so each record is self-locating in the running total. - **Counterparty type** — *who* the other side was, by category (investor, borrower, trustee, bank, and so on). - **Time of occurrence** — when the transaction actually happened. Two properties make these records trustworthy to read. First, the log is **append-only**. Under the hood, each root64 record is an Ethereum *event log* — a special data structure that a smart contract emits and that is then written into the block. The Solidity language documentation describes the mechanism precisely: when an event fires, the arguments are "stored in the transaction's log… incorporated into the blockchain, and stay there as long as a block is accessible," and "The Log and its event data are not accessible from within contracts (not even from the contract that created them)" ([Solidity documentation — Events](https://docs.soliditylang.org/en/latest/contracts.html), as of 2026-06-15). Two consequences follow for a reader. Once written, an entry cannot be edited or removed — so the history cannot be quietly rewritten after the fact, and what you read today is what was written then. And because not even the emitting contract can read its own logs back, these records exist purely as an external audit trail — something built to be read by you, off-chain, rather than re-used by the system internally. Second, the counterparty is **pseudonymized, not hidden**. The counterparty *type* is published in the clear — so you can filter and total by category — while the specific identity is committed as a cryptographic hash rather than a plain name. That combination is deliberate: it keeps individual borrowers and counterparties private while still letting you verify that a real, consistent counterparty stands behind each entry. Privacy and verifiability are meant to coexist, not trade off. ### Whose signature is on a cash-transaction record? Each cash-transaction record carries a signed claim, and the signature follows a specific Ethereum standard: **EIP-712**, the finalized standard for hashing and signing *typed, structured data*. EIP-712 exists to solve a concrete problem. The standard's own motivation notes that, without it, a signed message is "an opaque hex string displayed to the user with little context about the items that make up the message" ([EIP-712 specification](https://eips.ethereum.org/EIPS/eip-712), Final status, as of 2026-06-15). EIP-712 instead lets the data be presented with its schema, so the signer reviews the actual fields — the amount, the counterparty, the timestamp — rather than a meaningless blob before approving. It also carries a *domain separator*, which per the specification "prevents collision of otherwise identical structures" by binding each signature to a specific contract and chain ([EIP-712 specification](https://eips.ethereum.org/EIPS/eip-712), Final status, as of 2026-06-15) — so a signature created for root64's cash-flow contract is bound to that context and is not interchangeable with an identical-looking structure signed for a different application. In root64's case that domain is named `RWA-CashFlow` and pins the signature to the specific cash-flow contract on a specific chain. A note on *who* signs. The EIP-712 signature is issued by an **independent trustee** on a registered trustee wallet — not by the platform on its own — so the signed claim does not originate from root64 alone. Reading a record tells you that a structured, schema-checked claim was signed by that trustee and is tamper-evident; what it does not, on its own, establish is that the off-chain world matches the claim — which is exactly what the verification records (below) are for. Signing proves a claim was written and cannot later be altered; checking it against external sources root64 does not control is a separate step. ## How do you read a verification record? A verification record is the on-chain result of checking the pool's data against an independent outside source. Where a cash-transaction record says "this is what we recorded," a verification record says "and here is the result when we checked it against someone we don't control." Each one carries: - **Target** — what was checked: an asset, or a cash transaction. - **Channel** — the external source it was checked against: a property registry (for real-estate collateral), the Korea Financial Telecommunications & Clearings Institute (KFTC), which operates the central record-keeping system for Korean online-investment-linked-finance (P2P) transactions at [p2pcenter.or.kr](https://www.p2pcenter.or.kr), or a bank (for cash movements). - **Result** — one of three outcomes: **match**, **mismatch**, or **inconclusive**. The most important thing to understand when reading these is what happens on a **mismatch**. The point of an honest transparency layer is not to show only clean numbers — it is to make the act of checking auditable, including when something does not line up. So a mismatch is written to the chain just like a match, and when it is later worked out, a separate resolution record is logged against the same verification. You can read not just the final clean state but the path to it: a check failed, and here is the record that it was resolved. Reading a verification record alongside the cash-transaction record it covers is how you move from "root64 says this is true" to "an independent channel was checked, and here is the logged outcome." ## What does each on-chain record prove? The table below maps the two record types to what they contain and what reading them establishes. | On-chain record | What it contains | What it lets you establish | |---|---|---| | Cash-transaction record | Transaction type; signed amount (sign = inflow/outflow); balance after; counterparty type (identity hashed); time of occurrence; EIP-712 signature | That a specific money movement happened, in which direction, against which category of counterparty, leaving which balance — written once, never edited, with a schema-checked signature attached | | Verification record | Target (asset / cash transaction); channel (property registry / KFTC / bank); result (match / mismatch / inconclusive) | That the pool's data was checked against an independent outside source, and what the result was — including mismatches and their later resolution | *Source: root64 CashFlowLedger and VerificationLog contract specifications, as of June 2026.* Read together, the two record types answer two different questions. The cash-transaction records answer "did the money actually move, and how?" The verification records answer "and was that backed by something outside root64's own books?" Neither alone is the whole picture; the transparency layer is the pair. ## Where do you go to check it yourself? The public entry point — an Ethereum block explorer such as Etherscan, pointed at the address where root64 publishes its proofs — will be published together with the platform. We are deliberately not circulating an address ahead of that, because publishing a stable, named publisher address is itself a trust signal, and it should go out once, correctly, rather than be guessed at early. It helps to know the concrete reader gesture ahead of time, so it feels routine once the address is live. On Etherscan, you read a contract's records by opening a transaction's **Logs** tab; each emitted event there is split into **Topics** and a **Data** section. The first topic, **Topic0**, "is essentially a Keccak256 hash of the event signature, composed of the event's name and its input parameters' types," and it tells you *which kind of record fired* ([Etherscan Information Center — What is Event Logs?](https://info.etherscan.com/what-is-event-logs/), as of 2026-06-15). For root64 that means Topic0 distinguishes a cash-transaction record (`CashFlowRecorded`) from a verification record (`VerificationCompleted`) at a glance. Per the Solidity documentation, you "can add the attribute `indexed` to up to three parameters," which adds them to the topics structure as additional filters, while everything else is ABI-encoded into the Data section ([Solidity documentation — Events](https://docs.soliditylang.org/en/latest/contracts.html), as of 2026-06-15). In root64's cash-transaction record the indexed fields are the flow id, the pool id, and the counterparty type — so you can pull, say, every entry for one pool, or every entry against one category of counterparty, and read the rest (amount, balance after, timestamp) from the Data section. When it does publish, the records you read there will have exactly the shape described above: append-only cash-transaction entries and verification results, each field meaning what this guide says it means. The goal of putting the entry point in public hands is that verification does not depend on taking 8percent's word for it — you read the ledger directly. ## What can't the chain prove on its own? Recording an entry proves that a signed claim was written and cannot later be altered; it does not, by itself, prove the off-chain world matches. This is not a root64 quirk — it is a recognized limit of *all* on-chain proofs. The industry's proof-of-reserves principles make the same point: publishing a record on-chain establishes that the data was published and is tamper-evident, but credible transparency depends on *independent verification* that retrieves data "directly from trusted sources, like custodians or auditors" ([Chainlink — 7 Key Principles for Proof of Reserves](https://chain.link/blog/7-key-principles-for-proof-of-reserves), published 2025-05-02). Two further limits are worth carrying into how you read any such proof. First, such a record "reflects a specific point in time" ([Chainlink — 7 Key Principles for Proof of Reserves](https://chain.link/blog/7-key-principles-for-proof-of-reserves), published 2025-05-02) rather than a continuous guarantee. Second, a reserves snapshot on its own says nothing about liabilities — demonstrating that assets actually exceed liabilities is a separate exercise, which the same body of work treats as a distinct, complementary proof-of-solvency step ([Chainlink — 7 Key Principles for Proof of Reserves](https://chain.link/blog/7-key-principles-for-proof-of-reserves), published 2025-05-02); for broader background on proof-of-reserves mechanics and verification, see [Hacken — Proof of Reserves Explained: From Key Mechanics To Verification](https://hacken.io/discover/proof-of-reserves-explained-from-key-mechanics-to-verification/) (as of 2026-06-15). For real-world assets specifically, bridging the gap between a physical or legal asset and its digital record requires an external channel — the chain cannot confirm off-chain existence on its own. That is exactly why root64's design is two record types rather than one. The cash-transaction record is the tamper-evident published claim; the verification record is the independent external channel — a property registry, the KFTC record-keeping system, or a bank — checked against it. Reading both, including the mismatches, is the whole point: it is how an on-chain record stops being merely "written and unalterable" and becomes "written, unalterable, *and* checked against something root64 does not control."https://root64.io/blog/korea-online-investment-linked-finance-act-explained/https://root64.io/blog/korea-online-investment-linked-finance-act-explained/A plain-English guide to Korea's P2P lending law — the Online Investment-Linked Finance Act — including what it requires of platforms, how it protects investors, and why it shapes how global investors can access Korean loan assets.Fri, 12 Jun 2026 00:00:00 GMTKorea regulates P2P lending under the Online Investment-Linked Finance Act, in force since August 27, 2020 and supervised by the Financial Services Commission (FSC). Platforms must register, hold scaled minimum equity capital, and meet disclosure, lending-limit, and fund-separation duties. The Act bars discrimination between investors in one loan pool and restricts who may hold the right to principal and interest. ## What is Korea's P2P lending law? Korea regulates peer-to-peer (P2P) lending under a dedicated statute: the **Act on Online Investment-Linked Financial Business and Protection of Users**, which the financial regulator refers to in short form as the **Online Investment-linked Finance Act** (in Korean, 온라인투자연계금융업 및 이용자 보호에 관한 법률, where the regulated business is called 온투업). It has been in force since **August 27, 2020**, and it is supervised by the **Financial Services Commission (FSC)** through a registration regime. This makes Korea unusual. Many countries fit P2P lending awkwardly into older lending or securities rules. Korea instead passed what legal commentators have described as the world's first dedicated P2P-financing statute — a purpose-built law that names the activity, defines who may run a platform, and sets out how investors must be treated ([Lee&Ko newsletter](https://www.leeko.com/newsl/fintech/1912/fin1912_e.html), published December 2019; [Shin&Kim newsletter](https://www.shinkim.com/eng/media/newsletter/1056), published November 7, 2019). The UK, by contrast, has regulated P2P lending as "loan-based crowdfunding" inside the existing FCA framework since April 1, 2014 rather than under a standalone law ([RPC](https://www.rpclegal.com/thinking/financial-services-regulatory-and-risk/peer-review-fca-signals-tigher-regulation-for-p2p-lending-platforms/)) — a useful contrast between fitting P2P into older rules and writing a new one for it. For anyone trying to understand Korean private credit from the outside, this Act is the right starting point. ## When did the law take effect, and who enforces it? The Act was enacted in 2019 — it cleared the National Assembly in late October 2019 and was promulgated on **November 26, 2019** — and took effect on **August 27, 2020**. Existing operators were given a transition window to register, which closed on **August 26, 2021** — after which only FSC-registered firms could lawfully run an online investment-linked lending business, and unregistered operation became a criminal offence. The supervisor is the FSC. Its role is structured as registration rather than case-by-case product approval: a platform registers as an online investment-linked finance business, and registration brings it under ongoing supervision. | Milestone | Date | |---|---| | Act promulgated | November 26, 2019 | | Act in force | August 27, 2020 | | Transition period for existing operators ends | August 26, 2021 | | Supervisor | Financial Services Commission (FSC) | *Source: [FSC press release, "Legislation on P2P Lending Takes Effect"](https://www.fsc.go.kr/eng/pr010101/22490) (published August 26, 2020); [Korea Law Translation Institute, English text of the Act](https://elaw.klri.re.kr/eng_service/lawView.do?hseq=54729&lang=ENG).* A practical effect of the registration regime is consolidation. Before the Act, a large number of platforms operated in a lightly defined space; afterward, only a much smaller set of registered operators remained. With the transition window closing on August 26, 2021 and unregistered operation carrying criminal liability, the law raised the bar for who could be in the market at all. ## What does the Act require of a platform? A registered platform must meet a set of standing obligations under the Act covering capital, disclosure, lending limits, and investor protection ([KLRI English text](https://elaw.klri.re.kr/eng_service/lawView.do?hseq=54729&lang=ENG)). These are entry conditions and ongoing duties, not one-time filings. - **Registration with the FSC**, before a platform may operate, with a minimum equity capital of **KRW 500 million** that scales upward with the size of the platform's loan book — the threshold rises (to KRW 1 billion and KRW 3 billion) for larger prior-year linked-loan balances. A registrant must also keep at least 70% of its applicable minimum capital after registration, and amend its registration if its loan book grows into a higher capital band ([FSC press release](https://www.fsc.go.kr/eng/pr010101/22490), published August 26, 2020; [KLRI English text](https://elaw.klri.re.kr/eng_service/lawView.do?hseq=54729&lang=ENG)). - **Disclosure** to investors about loans, borrowers, and the platform itself, so that investment decisions rest on published information rather than on the operator's discretion. - **Lending and investment limits**, which cap exposures. Lending to a single borrower may not exceed **7% of the platform's total P2P loan balance or KRW 7 billion, whichever is smaller** ([FSC press release](https://www.fsc.go.kr/eng/pr010101/22490), published August 26, 2020). - **Investor-protection rules**, including separation of investor funds from the platform's own assets. Investor money must be held with an external depository — a bank, securities finance company, or savings bank with equity capital of **KRW 1 trillion or more** — rather than simply ring-fenced on the platform's own books ([FSC press release](https://www.fsc.go.kr/eng/pr010101/22490), published August 26, 2020). The common thread is that the platform is a regulated intermediary, not a free-form marketplace. Each requirement narrows what an operator can do, in exchange for being allowed to connect investors and borrowers at scale. ## What is the right to receive principal and interest, and why does it matter? Under the Act, an investor who funds a loan does not own the loan contract directly. Instead, the investor holds a defined legal right — the **right to receive principal and interest** (in Korean, 원리금수취권) — which is the entitlement to the principal and interest repayments that the underlying loan produces. This distinction matters for two reasons. First, it separates two ideas that are easy to conflate: the **loan receivables** (the economic right to a loan's repayments, held within the lending structure) versus the **right to receive principal and interest** that an investor holds under the Act. Second, that right is not freely transferable to anyone. It can be assigned only to eligible transferees — qualified holders such as institutions, rather than the general public. That eligibility constraint is one of the reasons cross-border access to Korean P2P assets has to be structured carefully rather than offered to anyone who wants in. (We cover the right to receive principal and interest in more depth in a separate post.) ## How does the Act protect investors? The Act's most important ongoing rule, for cross-border purposes, is that investors in the same loan pool must be treated equally. If domestic and overseas participants are funding the same pool of loans, the Act does not permit differences between them in return, repayment priority, or access to information. In concrete terms, that means three things cannot diverge between investors in the same pool: - **Return** — no investor group may receive better economics on the same loans than another. - **Repayment priority** — in the event of delinquency or default, no route can be placed ahead of another in the order of repayment. - **Information access** — giving one group of investors better dashboards, reports, or data than another can itself be a form of prohibited discrimination, because information asymmetry distorts who can act and when. This non-discrimination principle, combined with the registration and disclosure requirements above, is what gives the Korean P2P market its supervised character: a regulated operator, published information, separated funds, and equal treatment within a pool. ## Why does this matter for global investors? For a global investor, the headline is reassurance: Korean P2P lending is not an unregulated frontier. It sits inside a named statute, under a single supervisor (the FSC), with a registration regime, disclosure duties, and investor-protection rules. That is a meaningfully different starting point from markets where online lending has no dedicated legal home. It also explains why direct access is limited. The right to receive principal and interest can be assigned only to eligible transferees, and the non-discrimination rule means any structure serving overseas capital must keep that capital on equal footing with domestic investors in the same pool. These are not obstacles to be routed around — they are the rules a compliant structure has to satisfy. This is the regulatory backdrop against which root64 is built: a transparency-first platform for Korean loan assets, designed for professional investors and intended to operate within these rules rather than outside them.https://root64.io/blog/korean-private-credit-explained/https://root64.io/blog/korean-private-credit-explained/Korean private credit is a large, regulated, but hard-to-access market for foreign capital. Here is what it is, how it is regulated, why global investors can't easily buy in, and how an offshore on-chain structure bridges the gap.Fri, 12 Jun 2026 00:00:00 GMTKorean private credit is non-bank lending to consumers and small businesses. Its online segment is regulated under the Online Investment-linked Finance Act, in force since August 2020 and supervised by the Financial Services Commission. A loan's repayment right transfers only to qualified transferees, so global investors cannot buy these assets directly. root64 is building an offshore, on-chain route in. ## What is Korean private credit? Korean private credit is lending to Korean borrowers — consumers and small businesses — by non-bank lenders rather than by traditional banks or public bond markets. A meaningful part of it is originated through online platforms that connect investors directly to borrowers, the segment commonly called P2P (peer-to-peer) lending, and known in Korea as online investment-linked finance (온투업). The regulated online segment is sizeable but specific in scope. As of end-August 2025 the online investment-linked finance industry's combined outstanding loan balance was reported at roughly KRW 1.31 trillion (about USD 1 billion at then-prevailing rates), per industry reporting citing online investment-linked finance disclosure data ([Sisa Journal-e, 2 Sep 2025](https://www.sisajournal-e.com/news/articleView.html?idxno=414936)); separate reporting puts the number of registered operators at 52 ([Korea Economic Daily, 21 Oct 2025](https://www.hankyung.com/article/2025102134881)). That figure covers only the regulated online segment — it is not a measure of all Korean non-bank private credit, which also spans savings banks and other non-bank lenders outside the online investment-linked finance regime. These loans are typically secured against collateral. The asset types root64 works with, for example, include real-estate-secured consumer loans and securities-account-collateralized loans. The common thread is that the return comes from borrowers repaying principal and interest, not from market price movements. ## How is Korea's online lending market regulated? It is governed by a dedicated statute: the Act on Online Investment-Linked Financial Business and Protection of Users (온라인투자연계금융업 및 이용자 보호에 관한 법률), which the regulator refers to in short as the Online Investment-Linked Finance Act (온투법). It took effect on 27 August 2020 and is supervised by Korea's Financial Services Commission (FSC). It is a registration regime with concrete prudential and investor-protection rules. Per the FSC's release on the Act taking effect, the headline requirements include a cap on the lending interest rate at the statutory maximum under the Credit Business Act (24% when the release was published in 2020; Korea's legal maximum rate has since been lowered to 20%, effective 7 July 2021), a single-borrower exposure cap set at the lesser of 7% of a platform's total P2P loan balance or KRW 7 billion, mandatory segregation of investor funds at qualified depositories (banks, securities finance companies, or savings banks with equity capital of KRW 1 trillion or more), and outright bans on pre-funding loans, covering investor losses, and running maturity mismatches ([FSC, 26 Aug 2020](https://www.fsc.go.kr/eng/pr010101/22490)). The regime also tightly caps retail exposure. An individual investor faces a total cap of KRW 40 million across all P2P platforms and KRW 5 million per individual loan; only income-eligible investors — annual earned income over KRW 100 million, or interest and dividend income over KRW 20 million — qualify for higher limits of KRW 100 million total and KRW 20 million per loan ([Korea Economic Daily, 21 Oct 2025](https://www.hankyung.com/article/2025102134881)). These tight retail caps are part of why the market is built around (limited) resident investors, and why institutional and qualified-transferee channels matter for anyone seeking larger exposure. The registration requirement drove a sharp consolidation. The pre-Act P2P industry numbered around 241 firms as of June 2020 ([Korea Capital Market Institute (KCMI), 12 Oct 2020](https://www.kcmi.re.kr/publications/pub_detail_view?syear=2020&zcd=002001016&zno=1556&cno=5555)); when the Act's registration deadline arrived on 27 August 2021, only 28 operators had completed registration (7 earlier registrants plus 21 more), out of 40 firms that had applied ([Kyunghyang Shinmun, 27 Aug 2021](https://www.khan.co.kr/article/202108270651001)). The registered base has since grown to the 52 operators noted above. For a foreign investor, the takeaway is that this is a supervised, licensed market with hard investor-protection rules and a vetted operator set, not an unregulated corner of fintech. ## Why is it hard for global investors to access? Because Korea's inbound-investment rules are built around listed securities, and the domestic lending market is built around resident investors — so there is no established channel for a non-resident to buy these loan assets directly. Three constraints stack up: - **No defined channel.** Korea's foreign-investment framework is scoped to listed securities — shares, bonds, and the like ([Bank of Korea](https://www.bok.or.kr/eng/main/contents.do?menuNo=400192)). It does not provide a route for non-residents to invest in loan receivables or unlisted lending products. - **Domestic plumbing.** The online lending model runs on Korean-won real-name accounts at a domestic custody institution. Non-residents face significant friction opening those accounts. - **Transfer restrictions.** Under the Online Investment-linked Finance Act, the right to receive a loan's principal and interest can only be transferred to qualified transferees (institutional investors and the like) — not freely to any foreign buyer. On top of these access constraints sit the practical barriers that make the asset class unfamiliar to foreign capital in the first place: | Barrier | What it means for a foreign investor | |---|---| | Unfamiliar assets | Korean collateral types, loan structures, and recovery procedures are hard to evaluate from outside | | Multi-layer counterparty risk | Capital would pass through several entities, each opaque from abroad | | No independent verification | Conventional reporting is periodic, leaving gaps between reports | | Currency exposure | Capital is in dollars (or stablecoins); the loans are in Korean won | | Limited liquidity | Loan assets are held to maturity; they are not freely tradable | *Source: root64 product strategy, problem analysis, as of June 2026.* Note one thing these constraints are not: a blanket legal ban on foreigners investing in Korean credit. The issue is the absence of a clean, defined channel plus practical banking and currency friction — which is precisely the gap an offshore structure is designed to close. ## Are global investors engaging with Korean private credit? Increasingly, yes — though mostly in one direction so far. Global private credit is a large and fast-growing asset class: Preqin projects the market to reach USD 2.64 trillion by 2029, up from USD 1.50 trillion at end-2023 ([Pensions & Investments, citing Preqin's Future of Alternatives 2029, Dec 2024](https://www.pionline.com/alternatives/private-credit-forecast-reach-264-trillion-2029-preqin/)). That growth is pushing global managers to hunt for new credit exposures, including in Korea. The recent moves into Korea bear this out. In reporting by KED Global, Samsung Securities has served as the exclusive Korea distributor of Blackstone's private credit funds since June 2025, Mirae Asset Securities partnered with Hamilton Lane in February 2025 to roll out similar products, and Korea Investment & Securities was exploring a tie-up with US private credit specialist Muzinich & Co. ([KED Global, 29 Aug 2025](https://www.kedglobal.com/alternative-investments/newsView/ked202508290002)). These moves are mostly about global private credit funds being distributed *into* Korea — related to, but distinct from, foreign capital reaching Korean loan assets. They are noted here only as market context (root64 is not affiliated with the firms named). And this inbound flow is now itself drawing regulatory caution: in March 2026 the Financial Supervisory Service (FSS) summoned around 20 executives from 10 securities firms and fund managers over private credit fund risks — flagging weak risk measurement of non-marketable assets and sales that overemphasized yield — after Korean investor holdings of such funds reached about KRW 17 trillion in 2025 (up from KRW 13.8 trillion in 2024), with retail holdings rising sharply ([Seoul Economic Daily, 4 Mar 2026](https://en.sedaily.com/news/2026/03/04/korean-regulator-summons-brokerages-over-private-credit)). What has been missing — and what that one-directional flow underscores — is a route in the other direction: a way for global capital to access Korean loan assets themselves. ## How does an offshore structure bridge the gap? By holding the assets in Korea and connecting global capital from outside it. In root64's model, a Korean special-purpose company holds the loan assets domestically, satisfying the local transfer and custody rules, while an offshore vehicle is the planned route through which global professional investors would participate. That offshore tier — a Hong Kong vehicle — is planned and not yet formed, and any token issuance through it is contingent on regulatory clearance. root64 also adds a layer the conventional market lacks: it records the assets' cash flows on a public blockchain and logs each external verification on-chain, so an investor can check the state of the assets independently rather than waiting for periodic reports. The structure is built transparency-first; tokenization is designed to come on top of that foundation.https://root64.io/blog/right-to-receive-principal-and-interest/https://root64.io/blog/right-to-receive-principal-and-interest/The right to receive principal and interest (원리금수취권) is a Korean legal right to collect the principal and interest of a peer-to-peer loan. This post defines it under the Online Investment-Linked Finance Act, distinguishes it from a 'loan receivable,' compares it to loan participation, and explains who can hold it and why it matters for root64.Fri, 12 Jun 2026 00:00:00 GMTThe right to receive principal and interest (원리금수취권) is the legal right, defined in Article 2(4) of Korea's Online Investment-Linked Finance Act, to receive a recovered P2P loan's principal and interest in proportion to the amount invested. It transfers only to professional investors and other eligible holders, including root64's Korean SPC. 'Loan receivable' names the same asset. ## What is the right to receive principal and interest? The right to receive principal and interest (원리금수취권, *wonrigeum-suchwigwon*) is the legal right of an investor to collect the principal and interest of a loan. It is the form an investor's claim takes under Korea's Online Investment-Linked Finance Act (온투법, the law that governs peer-to-peer lending and investment in Korea). The law defines it precisely. Article 2(4) describes the right to receive principal and interest payments as "a right that an investor acquires under an agreement that the investor shall receive the amount of a P2P loan recovered by an online investment-linked financial business entity in proportion to the amount of the P2P investment made for such P2P loan" ([Act on Online Investment-Linked Financial Business and Protection of Users, KLRI English translation](https://elaw.klri.re.kr/eng_service/lawView.do?hseq=54729&lang=ENG)). Two things in that wording matter: the right arises *under an agreement*, and what it entitles you to is a *proportional share of recovered cash flows* — not the loan contract itself. So when you invest in a peer-to-peer loan on a Korean platform, you do not become the original lender of record. Instead, you hold a defined legal right to receive the principal and interest as the borrower repays. That right is literally "the right to receive principal and interest." It is the everyday unit that investors hold and trade in Korea's online-investment-linked-finance market. The right is anchored in a real underlying loan. The loan exists between the platform's lending structure and the borrower; the right to receive principal and interest is the investor-side entitlement to that loan's repayment stream. It is a claim on cash flows, not ownership of the borrower or of any physical collateral. ## How is it different from a "loan receivable"? They describe the same economic asset — the right to a loan's principal and interest — but in two different registers of language. The right to receive principal and interest is the precise Korean legal term; "loan receivables" (대출채권) is the more general term used in on-chain design and institutional-facing contexts. root64's glossary draws the line deliberately, and we follow it consistently: - **The right to receive principal and interest** is used when the context is the law itself — the Online Investment-Linked Finance Act, central record-keeping, and contract documents that must name the exact legal form of the right. - **Loan receivables** is used when the context is the RWA on-chain design or general documents written for institutional investors — for example, when describing an asset unit held by a special-purpose company or an on-chain identifier. The distinction is one of *register*, not of substance. The two terms point at the same underlying claim; which word we use signals which frame we are speaking in — the Korean statutory frame, or the general institutional and on-chain frame. | Term | English | Where it is used | |---|---|---| | Right to receive principal and interest | Right to receive principal and interest | The legal frame: Online Investment-Linked Finance Act, central record-keeping, contract documents naming the exact legal right (e.g. the "investment form" line of a term sheet) | | Loan receivables | Loan receivables | The general frame: RWA on-chain design and documents written for institutional investors (e.g. an SPC's asset unit, an on-chain `receivable` identifier) | *Source: root64 glossary (8percent business terms).* So when a root64 document says a Korean SPC "holds loan receivables" and another says it "holds the right to receive principal and interest," they are not describing two different things. They are describing one right, named for two different audiences. For a global reader, the right to receive principal and interest is analogous to a **loan participation** in U.S. and English-law markets — a structure in which a participant takes on the economic interest in a loan (its cash flows) without the loan contract itself being transferred, so the original lender remains the lender of record and the participant is not a direct creditor of the borrower ([Law Insider, "Loan Participation"](https://www.lawinsider.com/dictionary/loan-participation)). The analogy is useful for intuition, not an exact equivalence: the right to receive principal and interest is a distinct statutory creation under Korean law, with its own legal character and transfer rules described below. ## Who can hold or receive it? Not everyone. Under the Online Investment-Linked Finance Act, transfer of the right to receive principal and interest is restricted by statute. Article 34(1) sets the default rule that "No investor shall transfer his or her right to receive principal and interest payments," then carves out a narrow exception: an investor may transfer the right to a professional investor or to "a person specified by Presidential Decree as a person who is aware of the possibility of a loss," and a related provision requires that any such transfer be intermediated through the platform ([Act on Online Investment-Linked Financial Business and Protection of Users, Art. 34, KLRI English translation](https://elaw.klri.re.kr/eng_service/lawView.do?hseq=54729&lang=ENG)). In other words: not freely tradable to the general public on a secondary market, only to qualified holders, and only through the platform. That transfer restriction is a built-in feature of the right, and it shapes how any structure built on top of it must work. root64's Korean SPC sits inside that restriction rather than around it. The SPC is a qualified assignee — it falls within the professional-investor and eligible-holder category the law allows. Because it qualifies, the SPC can acquire the right to receive principal and interest — it participates in the existing market for these rights as an eligible institutional holder, rather than receiving an asset that the law would not allow it to take. There is also a national record-keeper. Under the Act, an online investment-linked finance entity submits user and transaction information to a central record-keeping institution (중앙기록관리기관), which keeps and manages that data and restricts third-party access. The institution designated for the P2P sector is the **Korea Financial Telecommunications & Clearings Institute (금융결제원, KFTC)**, which Korea's Financial Services Commission announced as the selected operator in a press release dated 21 October 2020, with operations beginning 1 May 2021 through the official portal p2pcenter.or.kr ([FSC press release via korea.kr, 21 Oct 2020](https://www.korea.kr/briefing/pressReleaseView.do?newsId=156416564); [ET News, 21 Oct 2020](https://m.etnews.com/20201021000238)). Its statutory role is to record and manage the underlying investment and borrowing transaction information — and to administer per-investor and per-borrower limits — rather than to operate as a rights registry. (This is a different institution from Korea Securities Depository, which is the central record-keeper for the separate securities-based crowdfunding regime.) The practical point holds either way: a holding of the right to receive principal and interest is not just a private claim asserted on paper — its underlying transactions are recorded at a national infrastructure level, which makes the right verifiable rather than merely asserted. ## Why does this matter for root64? It matters because the right to receive principal and interest is the specific thing root64's Korean SPC holds — it is the legal foundation the rest of the structure stands on. The SPC's job is to hold the assets, and "the assets," stated precisely, are these rights to receive principal and interest. That has a few practical consequences worth being explicit about: - The SPC can only hold the right because it is a qualified assignee, falling within the professional-investor category that Article 34 permits. Without it, the structure could not legally acquire the assets at all. - The underlying transactions are recorded by the sector's central record-keeping institution (KFTC), so the SPC's holding is anchored to external, verifiable national infrastructure rather than to root64's own books alone. - "Loan receivables" and "the right to receive principal and interest" appearing in different root64 documents are the same asset described for different readers, not a discrepancy. A planned Hong Kong tokenization tier would sit above this Korean foundation to serve global professional investors. That tier is not yet formed, and any token issuance through it is contingent on regulatory clearance — it is not live today. What is live is the layer described here: a Korean SPC holding the right to receive principal and interest as a qualified assignee, with national transaction records maintained underneath.https://root64.io/blog/transparency-before-tokenization/https://root64.io/blog/transparency-before-tokenization/Most RWA platforms start by issuing a token. root64 starts by making the underlying assets independently verifiable on Ethereum — and only then tokenizes. Here is why the order matters.Fri, 12 Jun 2026 00:00:00 GMTroot64 builds its verification layer before it issues any token. In its first phase, it records the cash transactions and balances of its Korean loan pool on Ethereum and logs each external verification — against property registries, Korea's P2P central record-keeper (KFTC), and bank APIs — on-chain, including mismatches. Tokenization is a planned second phase, contingent on regulatory clearance. ## 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](https://pcaobus.org/resources/information-for-investors/investor-advisories/investor-advisory-exercise-caution-with-third-party-verification-proof-of-reserve-reports)). 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](https://chain.link/blog/7-key-principles-for-proof-of-reserves/)). 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](https://www.circle.com/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](https://fortune.com/crypto/2023/11/02/sam-bankman-fried-verdict-trial-ftx-fraud-jury-sdny/)). 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](https://www.gtlaw.com/en/insights/2025/7/genius-act-enacted-establishing-a-regulatory-framework-for-payment-stablecoins-issued-or-sold-in-the-united-states)). 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](https://www.theblock.co/post/395173/blackrock-tokenized-buidl-fund-taps-chronicle-new-verification-layer)). 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.https://root64.io/blog/what-is-root64/https://root64.io/blog/what-is-root64/root64 is 8percent's real-world-asset platform: it records the cash flows of Korean loan assets on Ethereum so professional investors can verify them independently — before any token is issued.Fri, 12 Jun 2026 00:00:00 GMTroot64 is a real-world-asset (RWA) platform built by 8percent, a licensed Korean online lender. It records the actual cash flows and balances of Korean loan assets on Ethereum, so professional investors can verify them independently — before any token is issued. Two asset types are live today (as of June 2026), held in a Korean special-purpose company (SPC). ## What is root64? root64 is a platform that publishes Korean loan assets on a public blockchain and, in a second phase, tokenizes them for global professional investors. It is built by 8percent, a licensed Korean peer-to-peer (P2P) lending platform. The mission behind it is simple to state: connect Korea's alternative-asset market with the world — and become the first gateway global investors use when they look at Korean alternative assets. The platform stands on two pillars, in a deliberate order: 1. **Transparency** — record the actual cash transactions and investment balances of the underlying loan assets on Ethereum, so an investor can check the state of the assets without relying on the operator's reports. 2. **Tokenization** — once that verification layer exists, represent the investment on-chain as transferable units, issued through a Hong Kong vehicle to professional investors. Tokenizing real-world assets is no longer a fringe experiment: the on-chain value of tokenized RWAs (excluding stablecoins) stands above $30B, up from roughly $5B at the start of 2025 — a more than fivefold increase ([RWA.xyz](https://app.rwa.xyz/), as of 2026-06-15; start-of-2025 baseline of $5.42B per [CoinGecko, "RWA Report 2026"](https://www.coingecko.com/research/publications/rwa-report-2026), published 2026-05-13). Most projects in that wave begin with the token. root64 begins with the evidence. ## What problem does root64 solve? Korean credit remains, in root64's view, one of the least accessible alternative-credit markets for global investors. That gap stands out because private credit has become one of the largest and fastest-growing non-stablecoin categories of tokenized RWAs ([RWA.xyz](https://app.rwa.xyz/private-credit), as of 2026-06-15) — yet Korean-originated assets are largely absent from that category. The barriers are structural, not just informational (as of June 2026): - **Unfamiliar assets.** Collateral types (Korean real estate, securities accounts), loan structures, and Korea's recovery procedures are hard for a foreign investor to evaluate independently. - **Multi-layer counterparty risk.** Capital passes through an operator, a Korean special-purpose company (SPC — a bankruptcy-remote entity that holds the assets), a fund administrator, and an offshore vehicle. Each layer is opaque from the outside. - **No independent verification.** Conventional reporting in this market is periodic — in root64's initial pool, weekly NAV (net asset value) calculation and monthly reports. Between reports, an investor has no way to confirm asset status on their own. - **On-chain/off-chain consistency.** Putting data on a blockchain proves nothing by itself; what matters is who registered the data and who verified it against what source. Korea's regulatory base turns one of these barriers into an asset. The country has a dedicated P2P regime — described by its drafters' counsel as the world's first law devoted to P2P/marketplace lending ([Lee & Ko, "South Korea Enacts World's First Law on P2P Financing"](https://www.leeko.com/upload/upFile/201912//RECR201912120903123987436.pdf), Dec 2019), effective Aug 27, 2020 — that gives Korean loan claims a central register and bankruptcy-remote structuring. Those statutory channels are exactly what root64 reads from when it verifies assets, so the regulatory specificity that makes Korean credit unfamiliar is also what makes it verifiable. root64's answer to the verification problems is the product itself, described next. ## What does "transparency before tokenization" mean? It means the verification layer ships first, and the token comes second. This ordering responds to a documented gap in the wider RWA market. Industry guidance is explicit that putting a token on-chain proves nothing on its own — "Self-reported reserves without independent verification don't meet this bar." ([MetaMask, "How to verify tokenized real-world assets"](https://metamask.io/news/how-to-verify-rwa-tokens), 2026-04-20). Most projects lean on proof-of-reserve mechanisms or oracles after the token already exists; root64 inverts that order and separates who registers an asset from who verifies it. In its first phase, root64 records the cash transactions and investment balances of its initial loan pool on Ethereum, with proofs published on an ongoing basis — so the on-chain record tracks the actual movement of money rather than a quarterly snapshot. Crucially, registration and verification are separated: - **Asset data** is registered by the originator (the lender supplying the assets, starting with 8percent) and then checked against external public channels — Korean real-estate registries and the Korea Financial Telecommunications & Clearings Institute (KFTC, 금융결제원), the central record-keeper designated for online P2P loan claims ([p2pcenter.or.kr](https://www.p2pcenter.or.kr/)). - **Cash data** is recorded by the SPC's independent fund administrator and cross-checked against bank APIs. No single party — including 8percent — is the sole source of truth. Token issuance is planned through the Hong Kong vehicle for professional investors and is contingent on regulatory clearance; it builds on top of this verification layer rather than substituting for it. ## What assets does root64 cover? root64 starts with loan assets originated under Korea's regulated P2P lending regime. The current line-up (as of June 2026): | Asset type | Status | |---|---| | Real-estate-secured consumer loans | Live | | Securities-account-collateralized loans | Live | *Source: root64 asset line-up, as of June 2026.* These assets sit in the segment the broader market is moving toward fastest: tokenized private credit has grown in 2026 into one of the largest non-stablecoin RWA categories, rivaling tokenized US Treasuries ([RWA.xyz](https://app.rwa.xyz/private-credit), as of 2026-06-15). Korean alternative credit is largely absent from it — which is the access gap root64 is built to close. The platform is designed for extension from day one: beyond 8percent's own origination, the roadmap onboards external originators — registered money lenders (대부업) first, starting with their real-estate-secured loans, then capital-company portfolios, commercial real estate, and receivables-backed lending. ## How is root64 structured? Today, a Korean special-purpose company (SPC) holds the loan assets, keeping them separate from 8percent's balance sheet. Recording those assets' cash flows on-chain is the platform's first phase. The SPC's role rests on Korean law, not just contract: the Online Investment-linked Finance Act provides for the assignment of the right to receive principal and interest (원리금수취권), separate custody of investor funds at an independent institution, and bankruptcy remoteness if the operator fails ([Lee & Ko](https://www.leeko.com/upload/upFile/201912//RECR201912120903123987436.pdf), Dec 2019, re: the Act effective 2020-08-27). That statutory footing is what lets root64 treat the SPC as a genuinely bankruptcy-remote holder rather than an offshore convention. The planned tokenization phase would add a second tier — a Hong Kong vehicle to serve global professional investors — but that is not yet in place. Access is limited to **professional investors** throughout; root64 is not a public offering, and there is no retail product. A deeper structural walkthrough is coming in a separate post. ## Who is behind root64? 8percent is a licensed Korean P2P lending platform operating real-estate-secured, securities-account-collateralized, and personal credit loans. It was among the first companies registered when Korea introduced its dedicated licensing regime for online investment-linked finance — the Online Investment-linked Finance Act, which took effect on Aug 27, 2020 and is described by Korean counsel as the world's first law dedicated to P2P/marketplace lending ([Lee & Ko, "South Korea Enacts World's First Law on P2P Financing"](https://www.leeko.com/upload/upFile/201912//RECR201912120903123987436.pdf), Dec 2019). Building inside a brand-new regulatory framework is an experience root64 inherits as a working principle ("Within the Rules" is one of its four core values, alongside "Underwriting First", "Two-Way Trust", and "Build to Extend"). The first of those — Underwriting First — is the operative one: root64 treats underwriting — the ability to evaluate and stand behind each asset — as the foundation, and tokenization as the delivery mechanism, not the other way around. ## Why is it called "root64"? Because √64 = 8. The name encodes the link to 8percent and the ambition of squared growth. The brand image is a tree: roots reaching down into the ground stand for underwriting-first asset evaluation; the branches bearing fruit stand for a platform that connects many originators and many asset types above that foundation.