Tokenized Stock Pools: How OKXICE Checks Each Wallet
Say the daily sanctions rescreen flags a wallet holding 10 stock tokens and the venue revokes its badge. What can that wallet still do?

IN 30 SECONDS
A pool gate is a check inside the trading pool: only wallets holding the venue’s badge may trade there. OKXICE’s public notice describes one; ERC-3643 puts a similar check in the token instead, so it also covers direct transfers.
KEY TAKEAWAYS · 3
- The order asks a venue to describe how it approves access, without imposing a mechanism; the venue stays responsible if a vendor runs the checks.
- OKXICE’s notice puts the check in the pool: a Uniswap v4 hook only lets wallets holding a valid badge (an SBT) trade.
- Revoking a badge closes the pool to a wallet but, by itself, not its direct transfers; a freeze in the token can stop those.
On this page
What a venue must disclose about access
IN SHORT A venue must publish how it decides who may trade.
WORDS TO KNOW
- Tokenized Securities Venue (TSV)
- A trading venue that runs pools for tokenized US-listed shares and sets the standards for who may trade there.
- Soulbound token (SBT)
- A token that can’t be transferred and stays in one wallet. A venue can issue it as a badge: this wallet passed our checks.
- Token layer
- The access check sits in the token contract: an ordinary transfer fails unless the receiver is eligible, wherever it happens.
Item (f) of the notice a Tokenized Securities Venue (TSV) A trading venue that runs pools for tokenized US-listed shares and sets the standards for who may trade there. See the glossary must publish asks for its access criteria and “the procedures for approving access (e.g., white-listing or permissioning)”. That includes identity checks.
WATCH OUT
Coming up next: So how does one real venue describe its gate?
OKXICE’s pool gate next to ERC-3643’s token check
IN SHORT OKXICE checks a badge in the pool on every trade; ERC-3643 checks the receiver inside the token on every ordinary transfer.
OKXICE TSV published its public notice on 4 October 2026. Its operator, OKXICE LLC, is a joint venture of Intercontinental Exchange Holdings and OKC USA Holding. I use it because it’s concrete, not as an endorsement.
63
tokenized-stock symbols listed in the notice
My count, from the OKXICE TSV public notice of 4 October 2026.
Its pools are Uniswap v4 pools on X Layer, a public blockchain. An add-on contract, the “OKXICE TSV Hook”, filters access. Only wallets holding a valid Soulbound token (SBT) A token that can’t be transferred and stays in one wallet. A venue can issue it as a badge: this wallet passed our checks. See the glossary (SBT) from the venue may trade or add liquidity.
OKXICE ONBOARDING, AS DESCRIBED
Step 1. Screening. OKX Inc., an affiliate of the operator, runs identity (KYC/KYB), AML/CFT and sanctions checks for the venue. Wallets are rescreened daily.
- Screening OKX Inc., an affiliate of the operator, runs identity (KYC/KYB), AML/CFT and sanctions checks for the venue. Wallets are rescreened daily.
- Wallet proof The participant signs a transaction from a self-custodial wallet, and the wallet is screened.
- Tokenizer account The firm that tokenizes the stock approves the participant’s account.
- Badge The venue mints an SBT to the wallet. The tokenizer adds the wallet to its whitelist for that stock.
- Every trade The interface and pool contracts check for a valid, unrevoked SBT before each trade, transfer, liquidity action or other transaction they handle.
The notice says the stock can also trade elsewhere. That venue must meet the tokenizer’s requirements, have its support and meet the exemption’s conditions that apply to it.
WATCH OUT
IN PLAIN WORDS
Coming up next: So what if a badge holder gets flagged later?
Example: a wallet flagged after onboarding
IN SHORT Revoking a badge closes the pool to a flagged wallet, but by itself doesn’t stop its direct transfers.
A WORKED EXAMPLE
Illustrative numbers
REFUSED IN POOLA flagged wallet tries to sell in the pool
INPUT
- Wallet
- 0x7a3f...91c2
- Holds
- 10 stock tokens
- Daily rescreen
- sanctions match
WHAT HAPPENS
- The venue revokes its SBT and removes it from the whitelist.
- The wallet tries to sell its 10 tokens in the pool.
- The hook finds no valid SBT.
OUTPUT
- Result
- trade refused in the pool
NOT CHECKEDSame wallet, direct transfer to wallet B, pool-only design
INPUT
- To
- wallet B, outside the pool
- Amount
- 10 stock tokens
WHAT HAPPENS
- The transfer never goes through the pool, so the hook never runs.
- The token has no check of its own in this design.
OUTPUT
- Result
- the tokens move
This is a generic design, not OKXICE’s stock token. The notice doesn’t describe that token on this point. After a sanctions match, it says, the venue may burn or revoke the SBT and remove the wallet from the whitelist.
ITEM GET
A badge is not a freeze
Sources: OKXICE TSV public notice (4 Oct 2026), SEC order, Release No. 34-106402, ERC-3643 specification.
FAQ
No. OKXICE published a notice under the order; its disclaimer says the SEC “has not passed upon the merits or accuracy of the disclosures”. I cite it as an example, not as an endorsement.
No: the order requires no token standard and no set way to restrict transfers. ERC-3643 can do its token example. That alone meets none of the order’s conditions.
STAGE CLEAR
What you now know
- Why the order makes a venue describe its access checks without imposing a tool.
- Why a revoked badge, by itself, closes the pool but not the token.
Check yourself
Tap or click a question to see the answer.
A vendor screens wallets for a venue and misses a sanctions match. Who answers for it under the order?
The venue. The order says the TSV stays responsible when another firm runs its checks for it.
Former CTO of Integra. Named author (1 of 5) of ERC-3643, first author of ERC-6960, co-author of ERC-7410, and co-author of ERC-8203, which is still a draft. Building production AI and regulated Web3 systems.
Have a project to ship or a role to fill?
Discuss your project or roleFollow the engineering notes
Get new articles on production AI and smart contracts by email.