Nghiên cứu đã kiểm chứng nguồn: Franklin Onchain FUND SEC

Verified source facts

1. SEC staff published the Franklin Templeton no-action response on August 12, 2026. 2. The request concerns affiliated registered funds investing in the Franklin OnChain U.S. Government Money Fund and custody under Section 17(f) and Rule 17f-2. 3. The incoming letter describes official share records maintained on an integrated recordkeeping system using book-entry ownership. 4. The incoming letter describes independent-accountant reconciliation and verification, while the staff response remains tied to the represented facts.

Comparison at a glance

1. Rights analysis: Legal vehicle

Tokenization analysis must follow the legal and operational chain, not the visual token. The legal vehicle question asks about the exact registered fund and investing affiliates. Identify the issuer, tokenization sponsor, recordkeeper, custodian, broker or platform, and every agreement connecting them. Then match every legal name. A wallet balance alone cannot answer which person or system has the enforceable obligation.

Test the arrangement under a disagreement. If the chain record and master securityholder file diverge, which one controls? If an intermediary fails, is the holder a customer, beneficial owner, secured claimant, or unsecured creditor? If a transfer is technically possible but legally restricted, what process reverses or freezes it? The available sources frame these questions, while future reorganizations remains outside the evidence set.

Turn the legal vehicle finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Match every legal name before comparing yield, speed, or interface quality. Because future reorganizations is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

2. Rights analysis: Response type

The response type question asks about staff no-action position. Then read the conditions and facts.

The available sources frame these questions, while future staff position remains outside the evidence set.

Turn the response type finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Read the conditions and facts before comparing yield, speed, or interface quality. Because future staff position is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

3. Rights analysis: Authoritative record

The authoritative record question asks about official book-entry ownership. Then identify the controlling record.

The available sources frame these questions, while record conflict remains outside the evidence set.

Turn the authoritative record finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Identify the controlling record before comparing yield, speed, or interface quality. Because record conflict is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

4. Rights analysis: Blockchain role

The blockchain role question asks about technology inside the integrated system. Then separate transport from legal ownership.

The available sources frame these questions, while future architecture remains outside the evidence set.

Turn the blockchain role finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Separate transport from legal ownership before comparing yield, speed, or interface quality. Because future architecture is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

5. Rights analysis: Custody rule

The custody rule question asks about Section 17(f) and Rule 17f-2 treatment. Then map the represented controls.

The available sources frame these questions, while different product facts remains outside the evidence set.

Turn the custody rule finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Map the represented controls before comparing yield, speed, or interface quality. Because different product facts is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

6. Rights analysis: Reconciliation

The reconciliation question asks about independent comparison of records. Then inspect frequency and exception ownership.

The available sources frame these questions, while unresolved breaks remains outside the evidence set.

Turn the reconciliation finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Inspect frequency and exception ownership before comparing yield, speed, or interface quality. Because unresolved breaks is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

7. Rights analysis: Verification

The verification question asks about independent accountant procedures. Then read the actual scope.

The available sources frame these questions, while assurance limitations remains outside the evidence set.

Turn the verification finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Read the actual scope before comparing yield, speed, or interface quality. Because assurance limitations is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

8. Rights analysis: Transfer

The transfer question asks about book-entry and permitted movement. Then test the legal and operational route.

The available sources frame these questions, while secondary access remains outside the evidence set.

Turn the transfer finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Test the legal and operational route before comparing yield, speed, or interface quality. Because secondary access is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

9. Rights analysis: Redemption

The redemption question asks about conversion to cash and settlement. Then verify timing, cutoffs and fees.

The available sources frame these questions, while stress liquidity remains outside the evidence set.

Turn the redemption finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Verify timing, cutoffs and fees before comparing yield, speed, or interface quality. Because stress liquidity is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

10. Rights analysis: User boundary

The user boundary question asks about fund-specific facts versus sector-wide claims. Then avoid generalizing the response.

The available sources frame these questions, while future interpretations remains outside the evidence set.

Turn the user boundary finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Avoid generalizing the response before comparing yield, speed, or interface quality. Because future interpretations is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.

Decision scenarios

Scenario 1: when legal vehicle becomes decisive

Consider a reader whose main constraint is the exact registered fund and investing affiliates. The correct response is not to infer a universal platform or product winner. It is to match every legal name, retain the evidence, and define a stop condition before funds or permissions are committed. If the evidence changes, the decision must be reopened. This produces a repeatable operating rule rather than a one-time opinion.

Scenario 2: when response type becomes decisive

Consider a reader whose main constraint is staff no-action position. It is to read the conditions and facts, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when authoritative record becomes decisive

Consider a reader whose main constraint is official book-entry ownership. It is to identify the controlling record, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when blockchain role becomes decisive

Consider a reader whose main constraint is technology inside the integrated system. It is to separate transport from legal ownership, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when custody rule becomes decisive

Consider a reader whose main constraint is Section 17(f) and Rule 17f-2 treatment. It is to map the represented controls, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when reconciliation becomes decisive

Consider a reader whose main constraint is independent comparison of records. It is to inspect frequency and exception ownership, retain the evidence, and define a stop condition before funds or permissions are committed.