# RWA Daily Update - 2026-10-03

## Lesson title

An approved wallet does not mean an approved blockchain network

Access date: October 3, 2026 (PDT), checked with the local system clock. Educational review of established research, not breaking news or a certification of present-day network controls.

## Official sources checked

1. Basel Committee on Banking Supervision, Working Paper 44, "Novel risks, mitigants and uncertainties with permissionless distributed ledger technologies", August 28, 2024.
   Landing page: https://www.bis.org/bcbs/publ/wp44.htm
   Full report: https://www.bis.org/publications/novel-risks-mitigants-and-uncertainties-permissionless-distributed-ledger-technologies.pdf
   Relevant locations: sections 3.2 and 3.3, printed pages 8-9 (PDF pages 14-15), plus section 4 on printed page 9.
   Source class: official-hosted analytical working paper, not a product approval or a new binding rule.

## Extracted facts and claim mapping

- Section 3.2, printed page 8: an allowlisted token is "programmed to be accessed only by approved addresses". Addresses not on the allowlist cannot receive or send the asset, and the issuer can add or remove participants via the smart contract.
- Section 3.2, printed page 8: a designated controller may have powers over access, fraudulent transactions and code changes. Crucial boundary: "The controller would not exercise control over the permissionless network itself, but over the specific tokens of a specific issuance."
- Section 3.3, printed pages 8-9: permissioning a subset of nodes might establish known validators, potentially mitigating some legal/compliance, technology/attack and consumer-protection risks. The paper says avoiding gas fees to criminal or sanctioned nodes would likely slow transactions.
- Footnote 19, printed page 8: permissioning all nodes would turn a permissionless blockchain into a permissioned one and is unlikely to be feasible.
- Section 4, printed page 9: risk mitigants were at varying stages of development and generally had not been stress-tested at publication. This is a dated research conclusion, not a blanket statement about every current implementation.

## Facts versus educational interpretation

Verified source facts are the distinction between token-level controls and network-level control, the described allowlisting mechanism, and the potential trade-off from selecting known nodes. The tokenized-fund example in the lesson is illustrative, not a claim about a named fund. "Two control layers" is our plain-English teaching framework. The paper does not establish that allowlisting guarantees compliance, safety, legal ownership, redemption or settlement finality.

## No-hype summary

Restricting which wallets may hold a token does not put its issuer in control of the underlying blockchain. Evaluate investor/transfer permissions separately from transaction validation and network governance. Controls can reduce particular risks without removing network dependencies or creating a universal compliance guarantee.

## Practical watch question

Does "permissioned" describe the token holders, the validators, or both - and who controls each layer?

## Novelty and access notes

Reviewed prior daily lesson titles and searched the source-note library for validators, allowlisting and node permissioning. Earlier lessons discussed permissioned fund recordkeeping (July 7), general intermediaries (July 15) and transaction ordering (September 27); this lesson isolates the token-controller versus network-validator boundary.

Landing page and PDF were retrieved successfully. Web extraction returned a condensed PDF view, so direct Python urllib retrieval and pypdf extraction were used to read PDF pages 14-15 in full. No access failures on selected sources. The report's external PDF link already exists in the page source trail; no redundant external link is added. Previous notes and foundation remain intact.

Educational only; not investment or legal advice. No price forecasts, yield claims, product endorsements or buy/sell recommendations.