A token can record a lending position while the money needed to repay it remains outside the blockchain. Read Goldfinch V1's documentation to trace three different objects: the loan, the investor's position and the request to withdraw cash.
Intermediate · Document-reading case · Sources checked 24 October 2026 (KST). This is a study of the explicitly labelled Goldfinch V1 documentation, including historical material. It does not describe every later Goldfinch product, verify a live pool's solvency or recommend an investment.
New to the topic? Begin with RWA tokens: rights, yield, custody and redemption. Here we apply those questions to named documents rather than repeat the overview.
1. Draw the cash journey before naming the token
The V1 overview describes investors supplying USDC, borrower businesses drawing it from pools and converting it into local currency for lending. Loan origination and servicing remain with those businesses. That is the important boundary: a visible blockchain transaction is one leg of a longer credit relationship.
Our reading method is to mark each handoff: investor → pool contract → borrower business → end borrower, then trace repayments back. Beside each arrow, write who records the obligation and who must act if the payment is late. A missing answer is an evidence gap, even when every token transfer is visible.
2. Identify which position a document describes
The Borrowers documentation distinguishes junior capital supplied by Backers from senior capital supplied by the Senior Pool. It describes NFTs tracking the supplied and redeemed amounts of individual pool positions. Repayments are applied to the senior tranche's amounts due before the junior tranche's amounts due.
The separate Liquidity Providers documentation describes FIDU as the ERC-20 position received for supplying the Senior Pool. This is a different level of the structure from a Backer's individual pool position. Do not use one position's withdrawal rules to explain the other.
| Document object | What to record | What the record alone cannot establish |
|---|---|---|
| Borrower Pool | Interest terms, repayment schedule and senior/junior positions | Whether the business can collect enough off-chain cash to pay on time |
| Backer's pool-position NFT | The tracked contribution and repayments already redeemed | An unconditional right to recover the full principal immediately |
| FIDU | A Senior Pool position; use that pool's valuation and withdrawal documentation | A bank balance available on demand, or direct title to a particular end borrower's property |
These are our interpretations of the documented boundaries. To assess an actual claim, the remaining evidence would include the applicable legal agreements, eligible investor category, current pool statements, valuation policy and enforcement arrangements. Protocol documentation is not a substitute for those documents.
3. Read “request” separately from “receive”
The V1 Liquidity & LP Withdrawals page describes withdrawal requests with distributions every two weeks, subject to available capital. A request may span multiple periods; insufficient available USDC is allocated proportionally. It lists a 0.5% withdrawal fee. These are documented V1 mechanics, not a live promise that a request made today will finish in two weeks.
Fictional exercise: at one distribution date, assume total eligible requests equal 100,000 USDC and 30,000 USDC is available for them. Assume your eligible request is 1,000 USDC. Ignore changing valuations and all costs except the stated example fee.
- Fill fraction: 30,000 ÷ 100,000 = 30%.
- Your gross allocation: 1,000 × 30% = 300 USDC.
- At an assumed 0.5% deduction from that allocation: 300 × 0.995 = 298.50 USDC.
- The remaining requested amount is 700 USDC before later valuation changes. No completion date follows from this calculation.
The inputs are invented, not a Goldfinch balance, quote or observed withdrawal. This simplified exercise teaches proportional allocation; it does not reproduce contract rounding, current valuation or every fee. A token's displayed value and cash available this period are different quantities.
Go deeper: resolve a disagreement between two document sentences
The withdrawal page's opening list describes a cancellation fee using the total request, while its later explanation refers to the total remaining request. Record that ambiguity instead of choosing the cheaper interpretation. Before a real transaction, the current governing terms, deployed contract and interface quotation would need reconciliation. This article does not calculate a cancellation charge.
Try a second exercise: a dashboard shows a 1,000-unit position, 300 units allocated for withdrawal and 700 pending. Which number belongs in “cash available today”? The allocated amount still needs its settlement and fee conditions checked; the pending amount is not available cash. If someone totals all three figures as assets, they have counted the same position twice.
For the separate question of who absorbs a loss, use the private-credit seniority and recovery exercise. Withdrawal scheduling and loss priority answer different questions.
What you should now be able to explain
“On-chain” tells you where a record or action occurs. It does not tell you whether a borrower has paid, whether a valuation is realizable or when a withdrawal will settle. A useful RWA analysis follows the specific position all the way from the document to spendable proceeds.
Continue: compare a different structure in BUIDL: fund shares, USDC and redemption, or return to the advanced learning route.
Revision history and scope
19 October 2026: Reviewed the earlier article.
Editorial update: Corrected the growth-rate calculation; removed unsupported market totals, regulatory claims and allocation advice; added a claim-and-exit worksheet and a hypothetical total-return example.
24 October 2026: Replaced the overlapping general overview with a Goldfinch V1 document-reading case. Added the position map, fictional partial-withdrawal exercise and a documented fee-language ambiguity. Original publication date and URL retained.