Investigación verificada por fuentes: Blackrock Onchain Money Market
El cuerpo del artículo se muestra en el original verificado en inglés. La traducción se añadirá tras revisar las fuentes.
Direct answer
BlackRock's BSTBL OnChain Shares are permissioned ERC-20 representations of a regulated money market fund share class on Ethereum, not freely transferable bearer tokens. The transfer agent maintains the official ownership record, verifies eligible wallets and can restrict, reject or freeze transfers. Purchase and redemption orders received by 5:00 p.m. Eastern on a business day receive that day's NAV; redemptions require moving shares to an administrative redemption wallet and may incur Ethereum network fees. Onchain transferability therefore remains bounded by fund rules, identity controls, market calendars and transfer-agent operations.
Evidence snapshot: September 14, 2026 at 7:42 PM, Asia/Shanghai. This is research, not investment, legal, tax, or account-specific advice. Product availability, fees, controls, and legal terms can vary by entity, region, account tier, and time. Verify the live official page and the exact account screen before acting.
Mostrar menos
Verified source facts
1. The SEC-filed prospectus says BSTBL OnChain Shares are permissioned ERC-20 tokens on Ethereum and only verified wallet addresses may purchase them. 2. The transfer agent maintains the official ownership record and administers wallet whitelisting plus the ability to restrict, reject or freeze transfers. 3. Purchase and redemption orders must reach the transfer agent by 5:00 p.m. Eastern on a business day to receive that day's NAV. 4. Redemption orders are submitted by moving OnChain Shares to an administrative redemption wallet, and investors may have to pay Ethereum network fees.
Comparison at a glance
Tabla del artículo: desplázate horizontalmente o enfoca el área de la tabla y usa las flechas.
| Decision layer | What to inspect | Minimum safe action |
|---|---|---|
| Legal instrument | regulated fund share class | read the controlling prospectus |
| Token standard | permissioned ERC-20 on Ethereum | verify the official contract path |
| Ownership record | transfer-agent controlled record | identify the authoritative source |
| Wallet eligibility | registered and verified addresses | complete institutional onboarding |
| Transfer control | restrict, reject or freeze authority | test permitted movements |
| NAV cutoff | 5:00 p.m. Eastern business-day receipt | preserve timestamps |
| Redemption path | administrative redemption wallet | verify destination independently |
| Network fee | Ethereum transaction cost | budget and monitor gas |
| Network delay | consensus or protocol interruption | maintain reconciliation procedures |
| Recovery | burn, reissue or manual processing scenarios | document exception authority |
1. Rights analysis: Legal instrument
Tokenization analysis must follow the legal and operational chain, not the visual token. The legal instrument question asks about regulated fund share class. Identify the issuer, tokenization sponsor, recordkeeper, custodian, broker or platform, and every agreement connecting them. Then read the controlling prospectus. 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 amendments remains outside the evidence set.
Turn the legal instrument finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Read the controlling prospectus before comparing yield, speed, or interface quality. Because future amendments is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
2. Rights analysis: Token standard
The token standard question asks about permissioned ERC-20 on Ethereum. Then verify the official contract path.
The available sources frame these questions, while contract migration remains outside the evidence set.
Turn the token standard finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Verify the official contract path before comparing yield, speed, or interface quality. Because contract migration is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
3. Rights analysis: Ownership record
The ownership record question asks about transfer-agent controlled record. Then identify the authoritative source.
The available sources frame these questions, while record discrepancy remains outside the evidence set.
Turn the ownership 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 authoritative source before comparing yield, speed, or interface quality. Because record discrepancy is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
4. Rights analysis: Wallet eligibility
The wallet eligibility question asks about registered and verified addresses. Then complete institutional onboarding.
The available sources frame these questions, while jurisdictional limits remains outside the evidence set.
Turn the wallet eligibility finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Complete institutional onboarding before comparing yield, speed, or interface quality. Because jurisdictional limits is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
5. Rights analysis: Transfer control
The transfer control question asks about restrict, reject or freeze authority. Then test permitted movements.
The available sources frame these questions, while compliance hold remains outside the evidence set.
Turn the transfer control finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Test permitted movements before comparing yield, speed, or interface quality. Because compliance hold is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
6. Rights analysis: NAV cutoff
The nav cutoff question asks about 5:00 p.m. Eastern business-day receipt. Then preserve timestamps.
The available sources frame these questions, while holiday calendar remains outside the evidence set.
Turn the nav cutoff finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Preserve timestamps before comparing yield, speed, or interface quality. Because holiday calendar is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
7. Rights analysis: Redemption path
The redemption path question asks about administrative redemption wallet. Then verify destination independently.
The available sources frame these questions, while address change remains outside the evidence set.
Turn the redemption path finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Verify destination independently before comparing yield, speed, or interface quality. Because address change is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
8. Rights analysis: Network fee
The network fee question asks about Ethereum transaction cost. Then budget and monitor gas.
The available sources frame these questions, while congestion spike remains outside the evidence set.
Turn the network fee finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Budget and monitor gas before comparing yield, speed, or interface quality. Because congestion spike is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
9. Rights analysis: Network delay
The network delay question asks about consensus or protocol interruption. Then maintain reconciliation procedures.
The available sources frame these questions, while off-chain mismatch remains outside the evidence set.
Turn the network delay finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Maintain reconciliation procedures before comparing yield, speed, or interface quality. Because off-chain mismatch is not proven, the conclusion must remain conditional and dated rather than borrowing certainty from the token's technical appearance.
10. Rights analysis: Recovery
The recovery question asks about burn, reissue or manual processing scenarios. Then document exception authority.
The available sources frame these questions, while investor-specific outcome remains outside the evidence set.
Turn the recovery finding into an ordinary-language rights statement: who owes what, through which record, under which rule, and how the holder can act. Document exception authority before comparing yield, speed, or interface quality. Because investor-specific outcome 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 instrument becomes decisive
Consider a reader whose main constraint is regulated fund share class. The correct response is not to infer a universal platform or product winner. It is to read the controlling prospectus, 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 token standard becomes decisive
Consider a reader whose main constraint is permissioned ERC-20 on Ethereum. It is to verify the official contract path, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 3: when ownership record becomes decisive
Consider a reader whose main constraint is transfer-agent controlled record. It is to identify the authoritative source, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 4: when wallet eligibility becomes decisive
Consider a reader whose main constraint is registered and verified addresses. It is to complete institutional onboarding, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 5: when transfer control becomes decisive
Consider a reader whose main constraint is restrict, reject or freeze authority. It is to test permitted movements, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 6: when nav cutoff becomes decisive
Consider a reader whose main constraint is 5:00 p.m. Eastern business-day receipt. It is to preserve timestamps, retain the evidence, and define a stop condition before funds or permissions are committed.
Sources and editorial method
Temas y herramientas:Guías de cuenta y seguridad