The holder owns the actual registered common share.
Understand ownership →Issuer programme dossier
Securitize SECZ
The holder owns the actual registered common share.
The short answer
A redemption process is documented, but no independently observed completed redemption is recorded.
Understand redemption →Control is listed as observed powers, with no single score.
Understand issuer powers →NO PUBLIC VERIFICATION FEED.
Understand insolvency protection →How it works, step by step
Each numbered step cites where it comes from. Colour shows how we know it; a dashed step is not established.
Securitize SECZ: switching back out of token form
Asserted in one clause; no procedure is published.- documented the issuer’s or a regulator’s own words
- not established drawn dashed: nothing found settles it
Steps as text
- Holders “may elect to switch between tokenized SECZ and nontokenized SECZ” documented Source: Securitize SECZ dossier (redemption.rails)
- De-tokenization back to the book-entry position: no procedure, burn address, processing time or fee published not established Source: Securitize SECZ dossier (redemption.rails)
Securitize SECZ: from brokerage shares to tokens
Only the inbound leg is documented; two transfer agents coordinate it.- documented the issuer’s or a regulator’s own words
Steps as text
- Holder’s broker → Continental Stock Transfer Broker moves the shares out of street name by DRS or DWAC documented Source: stocks.securitize.io — stocks.securitize.io tokenize instructions for SECZ, step 2 "Requesting Direct Registration"
- Continental Stock Transfer Continental records the holder as registered owner documented Source: Securitize SECZ dossier (redemption.rails)
- Continental Stock Transfer → Securitize Once on the transfer agent’s ledger, the shares can be converted into tokenized form documented Source: stocks.securitize.io — stocks.securitize.io tokenize instructions for SECZ, step 2 "Requesting Direct Registration"
- Securitize → Registered wallet Tokens are issued to a Securitize-registered wallet documented Source: Securitize SECZ dossier (redemption.rails)
Securitize SECZ: who is involved
Every party the dossier names, and how it relates to the programme.- documented the issuer’s or a regulator’s own words
Relations as text
- Company that issues the share itself: Securitize documented Source: sec.gov — Frequently Used Terms
- Runs the tokenization for it: Securitize documented Source: sec.gov — p. 10, Prospectus Summary
- Keeps the share register: Continental Stock Transfer & Trust Company, Securitize Transfer Agent LLC documented Source: data.sec.gov — data.sec.gov submissions for CIK 0001782266, json path $.name (20 TA filings, all File No. 084-06638)
- Holds the underlying: Fireblocks documented Source: sec.gov — p. 20, crypto-asset custody risk factor
- Distributes or lists it: Securitize, Jupiter, NYSE documented Source: sec.gov — p. 104, Business, Distribution vertical
- Programme is owned by: Securitize documented Source: sec.gov — p. 10, Prospectus Summary
- Programme answers to: SEC, FINRA documented Source: sec.gov — p. 47, tokenization risk factor
- Offered to: KYC-verified platform users, allowlisted wallets documented Source: sec-connect-api-docs.securitize.io — Securitize Connect API docs, Wallets page
What if a part of the chain fails?
We put 38 failure scenarios (stolen keys, custodian insolvency, a frozen token, regulator action) to this programme in the same words as every other issuer. Documented means the issuer’s or a regulator’s own words address the case; inferred is our reading of the structure.
- 31 documented
- 4 inferred
- 0 litigated
- 0 unknown
- 3 not applicable
See this programme in the failure-scenario matrix →Read every answer in the issuer panel →
What happens if…
Six of the scenarios, drawn: where the failure starts, how it reaches the holder, and what this programme’s documents say happens next.
What if… My private keys are stolen and the tokens are moved.
Securitize SECZ — answer documented.- documented the issuer’s or a regulator’s own words
- scenario the scenario or generic chain, not an issuer claim
Steps as text
- Holder My private keys are stolen and the tokens are moved. scenario Source: Failure-scenario list — keys-stolen
- Holder → Tokenization provider Who could act on it: the “Transfer and control” chain scenario Source: Trust-chain list — flow: transfer
- Holder Your position is meant to survive the theft, because the register rather than the wallet is the record: Securitize says that where a holder loses access to a wallet, private key or partial key share it may burn and reissue the tokenized security to a new verified whitelisted wallet, generally within the same business day, and that ownership records held in the transfer-agent framework stay authoritative even if a wallet is hacked. documented Source: sec.gov — p. 87, MD&A — Quantitative and Qualitative Disclosures about Market Risk, "Custodian Risk"
- Holder Nothing is promised, no evidentiary standard or appeal is published, and every claim against Securitize is capped at $1,000. documented Source: sec.gov — p. 87, MD&A — Quantitative and Qualitative Disclosures about Market Risk, "Custodian Risk"
What if… The mint, freeze or delegate authority key is compromised or lost.
Securitize SECZ — answer documented.- documented the issuer’s or a regulator’s own words
- scenario the scenario or generic chain, not an issuer claim
Steps as text
- Token program and keys The mint, freeze or delegate authority key is compromised or lost. scenario Source: Failure-scenario list — authority-key-compromised
- Token program and keys → Holder Reaches the holder along “Transfer and control” scenario Source: Trust-chain list — flow: transfer
- Holder Minting is the protected half: Securitize says operational issuance needs multi-party computation signatures from several signers, so unauthorised creation of new tokens is guarded, and errors are remediated by seizing or burning. documented Source: sec.gov — p. 30, risk factor on minting and redeeming tokens
- Holder The unprotected half is measurable — the permanent delegate, global pause and split multiplier all sit on one ordinary funded private key with no multisig or timelock, and Securitize discloses that it carries no insurance on self-custodied digital assets. documented Source: sec.gov — p. 30, risk factor on minting and redeeming tokens
- Holder If that key were taken, every holding could be moved, burned or frozen, and your fallback is the off-chain register. documented Source: sec.gov — p. 30, risk factor on minting and redeeming tokens
What if… The custodian or prime broker holding the shares goes bankrupt.
Securitize SECZ — answer documented.- documented the issuer’s or a regulator’s own words
- scenario the scenario or generic chain, not an issuer claim
Steps as text
- Custodian or prime broker The custodian or prime broker holding the shares goes bankrupt. scenario Source: Failure-scenario list — custodian-insolvency
- Custodian or prime broker → Holder Reaches the holder along “Ownership of the underlying” scenario Source: Trust-chain list — flow: ownership
- Holder For the retail path there is no custodian to fail: trading is supported using third-party self-custody wallets only, so the tokens sit under your own keys and settle atomically on-chain. documented Source: securitize.io — §3.1 FINRA and Regulatory Disclosures
- Holder Where a custodian is in the chain, the ATS manual says custody of subscriber digital asset securities is provided by an SEC-registered transfer agent and cash custody by a cash custodian — and Securitize Markets is a SIPC member, so eligible securities accounts carry protection up to $500,000 including $250,000 for cash. documented Source: securitize.io — §3.1 FINRA and Regulatory Disclosures
- Holder The unflattering detail is that the securities custodian is the issuer's own affiliate. documented Source: securitize.io — §3.1 FINRA and Regulatory Disclosures
What if… The token issuer goes bankrupt.
Securitize SECZ — answer documented.- documented the issuer’s or a regulator’s own words
- scenario the scenario or generic chain, not an issuer claim
Steps as text
- Token issuer The token issuer goes bankrupt. scenario Source: Failure-scenario list — issuer-insolvency
- Token issuer → Holder Reaches the holder along “Ownership of the underlying” scenario Source: Trust-chain list — flow: ownership
- Holder There is nothing between you and the estate, by design: the token issuer is the company, the security is its own common stock, and on a liquidation you are paid pro rata out of net assets only after the preferred. documented Source: sec.gov — p. 121, Description of Securities — Common Stock, "Liquidation, Dissolution and Winding Up"
- Holder No SPV, trust or ring-fence exists, and none is claimed. documented Source: sec.gov — p. 121, Description of Securities — Common Stock, "Liquidation, Dissolution and Winding Up"
- Holder The one part of the stack that would survive outside the estate is the share register itself, which Securitize's own tokenization instructions place at Continental Stock Transfer rather than at an affiliate. documented Source: sec.gov — p. 121, Description of Securities — Common Stock, "Liquidation, Dissolution and Winding Up"
What if… The company is acquired or merged, for cash or for shares.
Securitize SECZ — answer documented.- documented the issuer’s or a regulator’s own words
- scenario the scenario or generic chain, not an issuer claim
Steps as text
- Underlying company The company is acquired or merged, for cash or for shares. scenario Source: Failure-scenario list — company-acquired
- Underlying company → Holder Reaches the holder along “Corporate actions” scenario Source: Trust-chain list — flow: corporate-actions
- Holder You receive exactly what every other common stockholder receives, because there is only one class: Tokenized SECZ is not a separate share class, and Delaware law makes the rights of holders of uncertificated stock identical to those of certificated holders of the same class. documented Source: sec.gov — p. 47, tokenization risk factor
- Holder A merger needs a stockholder vote and you vote your shares. documented Source: sec.gov — p. 47, tokenization risk factor
- Holder What is not published is the plumbing: no document says how cash or acquirer shares reach a whitelisted wallet, whether the tokens are burned on closing, or on what timetable. documented Source: sec.gov — p. 47, tokenization risk factor
What if… The company is delisted or goes private.
Securitize SECZ — answer documented.- documented the issuer’s or a regulator’s own words
- scenario the scenario or generic chain, not an issuer claim
Steps as text
- Underlying company The company is delisted or goes private. scenario Source: Failure-scenario list — company-delisted
- Underlying company → Holder Reaches the holder along “Corporate actions” scenario Source: Trust-chain list — flow: corporate-actions
- Holder The token does not terminate, because nothing ties it to the listing: it is the same common stock, and no document provides for termination or final valuation on a delisting. documented Source: sec.gov — p. 45, risk factor "Securitize's failure to meet the continued listing requirements of the NYSE could result in a delisting of its Securities"
- Holder What you lose is the reference price and the liquid side of the trade — the S-1 says a delisting would impair your ability to sell or buy when you wish, and the SECZ token's price is quoted off that market while its own on-chain volume is negligible. documented Source: sec.gov — p. 45, risk factor "Securitize's failure to meet the continued listing requirements of the NYSE could result in a delisting of its Securities"
- Holder Going private would cash you out under Delaware law like any other stockholder, with no token-specific procedure published. documented Source: sec.gov — p. 45, risk factor "Securitize's failure to meet the continued listing requirements of the NYSE could result in a delisting of its Securities"
Technology + legal templates
These conclusions apply only to the exact programme and observed control recipe shown.
Current Solana assets
1 exact token address currently inherit this issuer-level analysis unless an asset card records an exception. Watch this issuer programme →
Legal claim and issuing chain
- Issuing entity
- Securitize Corp., a Delaware corporation (EDGAR CIK 0002094496, SIC 6199 Finance Services), formed via the business combination of Cantor Equity Partners II, Inc. ('CEPT'), Securitize, Inc. ('Old Securitize') and Securitize Holdings, Inc. under a Business Combination Agreement dated 2025-10-27, consummated 2026-07-01 after stockholder approval on 2026-06-29. NYSE listing certified 2026-07-01 (Form CERT), 8-A12B filed 2026-06-30, first trade 2026-07-02. Transfer agent of record for the common stock: Continental Stock Transfer & Trust Company (named in the S-1 and 424B3 Description of Securities; see parties.transferAgents). The group's own SEC-registered transfer agent is Securitize Transfer Agent, LLC — File No. 084-06638, CIK 0001782266, live filing history (TA-1 through TA-1/A of 2026-08-27 and annual TA-2s) — but no filing names it as registrar for Tokenized SECZ. Access gated by the group's SEC-registered, FINRA-member broker-dealer and ATS.
- Entity jurisdiction
- Delaware corporation, principal operations United States. All regulated entities in the stack are SEC-registered/FINRA-member US entities.
- Governing law
- Delaware General Corporation Law governs the common stock and the share register; US federal securities law governs the listing, the transfer agent (Exchange Act §17A and Rules 17Ad-1 to 17Ad-21) and the broker-dealer/ATS gating access. No separate token terms of service or holder agreement for Tokenized SECZ was located; the operative public instrument is the Form S-1 prospectus risk factor plus the Securitize platform's general investor terms (not located in tokenized-SECZ-specific form).
- Regulatory status
- The most heavily regulated of the three Solana-native issuers examined, and the only one where the tokenization vendor is itself the registrant. The underlying security is registered common stock of a Delaware SEC-reporting company listed on the NYSE (S-4 registration statement effective 2026-06-05; S-1 filed 2026-07-31, EFFECT 2026-08-07; 424B3 prospectuses 2026-08-07 and 2026-08-13). Securitize Transfer Agent, LLC is an SEC-registered transfer agent (File No. 084-06638). The S-1 describes the group as 'the only vertically integrated tokenization provider with SEC-registered entities across a transfer agent, broker-dealer, alternative trading system (ATS), investor advisor and fund administration'. Access to the tokenized form is intermediated by a regulated broker-dealer: 'Access to Tokenized SECZ is restricted to holders who meet the onboarding requirements of Securities Markets, LLC, a SEC registered and FINRA member broker dealer' (note: the S-1 renders the entity name as 'Securities Markets, LLC'. RESOLVED 2026-09-17 against a primary source: Securitize's own 2026-07-02 press release names 'Securitize Markets, LLC, an SEC-registered broker-dealer and member FINRA/SIPC that operates an SEC-regulated Alternative Trading System (ATS)', so the S-1 wording is a typographical error in a registration statement and the gatekeeping broker-dealer is Securitize Markets, LLC). No exemptive relief or no-action letter for the tokenized form was located; the S-1 warns that 'market intermediaries may face unclear or evolving obligations'.
- Holder claim
- The holder owns the actual registered common share. The S-1 risk factor is unambiguous on two points at once: 'we enabled Tokenized SECZ, a natively tokenized version of our common stock. Tokenized SECZ is not a separate share class' and 'Tokenized SECZ provides an additional mechanism for investors to hold and transfer shares in the Company'. The issuer's own press release adds that this is an 'issuer-sponsored tokenization of the same common stock trading on the NYSE' and that 'Tokenization changes the form of ownership; it does not change the underlying nature of the share or override applicable legal, contractual or transfer restrictions.' Holders may move between forms: 'holders of SECZ may elect to switch between tokenized SECZ and nontokenized SECZ'. There is no SPV, receipt or nominee layer in the legal structure — Securitize's tokenize route makes the holder a registered holder in their own name on Continental's book BEFORE conversion ("Once your shares are registered directly on the transfer agent’s shareholder ledger, they can be converted into tokenized form"); whether they remain the holder of record there AFTER conversion, or a Securitize entity or nominee takes that line with the token ledger as a sub-register, is NOT established by any document located, and this is the central unresolved question for this issuer.
- Underlying custodian
- No custodian is disclosed for the security itself. Which register records a tokenized position is not published: Continental Stock Transfer is the transfer agent of record for the common stock, and Securitize describes (generically, for all its tokenized securities) a blockchain "master securityholder file" kept by its own transfer agent; whether a tokenized holder stays on Continental's book in their own name, or a Securitize entity or nominee takes that line with the token ledger as a sub-register, is undisclosed. For its own corporate digital assets Securitize discloses self-custody via Fireblocks MPC ('enables us to retain exclusive control over the authorization of transactions without ever generating or storing a traditional private key'), and states that 'In the case of Securitize-issued tokenized securities held in self-custody utilizing Fireblocks infrastructure, Securitize has manual safeguards in place which help retain the appropriate records of ownership should the automated blockchain systems fail which it controls in its capacity as transfer agent.' Investor-side custody may be self-custody (see transferRestrictions) or broker/custodian-held; the split is not disclosed.
Shareholder rights
| Right | For the token holder | Why |
|---|---|---|
| Dividends | Yes, as a shareholder | Same share class as the listed stock, so any dividend is yours; none is expected.Source: sec.gov · p. 47, tokenization risk factor · “Tokenized SECZ is not a separate share class.” |
| Voting | Yes, as a shareholder | One vote per share; no process for voting from a token wallet is published.Source: sec.gov · p. 121, Description of Securities, Common Stock · “Holders of Securitize Common Stock are entitled to one vote per share on matters to be voted on” |
| Reports & meetings | Yes, as a shareholder | A registered shareholder's reports and meeting materials; who is on the register for a token is still an open question.Source: stocks.securitize.io · step 4 'Transfer Agent Creates Your Account' · “Once the transfer is verified, the transfer agent records you as the registered owner of the shares.” |
| Splits | Yes, as a shareholder | A split applies to the share itself; the token can show it through its multiplier.Source: sec.gov · p. 47, tokenization risk factor · “Tokenized SECZ is not a separate share class.” |
| Takeovers | Yes, as a shareholder | Same share class, so you receive what every shareholder receives in a deal.Source: sec.gov · p. 47, tokenization risk factor · “Tokenized SECZ is not a separate share class.” |
Who can exercise token controls
Direct or one-signer control: Mint, Freeze accounts, Allowlist / transfer restriction (Securitize program 9yy4W1B5GyF1JrrZDG3UE6cqPTJzCPihErJNfEV14BGi via PDA 8TwererfKZwiBfKQs2bQmVRrezqeFG3JvrVsbpGaPbQs; program upgradable by the single key 8d36iv2YUD8yDChuVZchx1NqE4qkDWCAEgsUEEUqzbB6); Pause transfers, Permanent delegate, Claw back / burn, Rebase / balance multiplier (Unattributed direct signer D2kGPFTyGSeeTSCA1kEzKZNrdMvYKPLdZtrmAnnK6jCS); Programme upgrade (Single upgrade key 8d36iv2YUD8yDChuVZchx1NqE4qkDWCAEgsUEEUqzbB6 (unattributed)).
This is the representative current exact-token recipe. Open the technology + legal templates above for recipe differences. Programme and PDA labels are traced to the effective signer where reviewed evidence permits. Thresholds apply only to the named role; initiate-only members are not counted as voters.
- Mint
- Hot key · Securitize program 9yy4W1B5GyF1JrrZDG3UE6cqPTJzCPihErJNfEV14BGi via PDA 8TwererfKZwiBfKQs2bQmVRrezqeFG3JvrVsbpGaPbQs; program upgradable by the single key 8d36iv2YUD8yDChuVZchx1NqE4qkDWCAEgsUEEUqzbB6
- Freeze accounts
- Hot key · Securitize program 9yy4W1B5GyF1JrrZDG3UE6cqPTJzCPihErJNfEV14BGi via PDA 8TwererfKZwiBfKQs2bQmVRrezqeFG3JvrVsbpGaPbQs; program upgradable by the single key 8d36iv2YUD8yDChuVZchx1NqE4qkDWCAEgsUEEUqzbB6
- Pause transfers
- Hot key · Unattributed direct signer D2kGPFTyGSeeTSCA1kEzKZNrdMvYKPLdZtrmAnnK6jCS
- Permanent delegate
- Hot key · Unattributed direct signer D2kGPFTyGSeeTSCA1kEzKZNrdMvYKPLdZtrmAnnK6jCS
- Claw back / burn
- Hot key · Unattributed direct signer D2kGPFTyGSeeTSCA1kEzKZNrdMvYKPLdZtrmAnnK6jCS
- Allowlist / transfer restriction
- Hot key · Securitize program 9yy4W1B5GyF1JrrZDG3UE6cqPTJzCPihErJNfEV14BGi via PDA 8TwererfKZwiBfKQs2bQmVRrezqeFG3JvrVsbpGaPbQs; program upgradable by the single key 8d36iv2YUD8yDChuVZchx1NqE4qkDWCAEgsUEEUqzbB6
- Rebase / balance multiplier
- Hot key · Unattributed direct signer D2kGPFTyGSeeTSCA1kEzKZNrdMvYKPLdZtrmAnnK6jCS
- Programme upgrade
- Hot key · Single upgrade key 8d36iv2YUD8yDChuVZchx1NqE4qkDWCAEgsUEEUqzbB6 (unattributed)
Redemption and holder eligibility
Programme-level answer. Product examples remain labelled and do not establish another token’s terms.
- Contractual right
- Yesdocumented
- Eligible holder and route
- documented
Documented at programme level. See complete terms.
Holders who have completed the broker-dealer onboarding: 'Access to Tokenized SECZ is restricted to holders who meet the onboarding requirements of Securities Markets, LLC, a SEC registered and FINRA member broker dealer.' The issuer's press release adds that the tokenized form is for 'eligible U.S. investors' subject to 'onboarding, KYC/AML verification, jurisdictional eligibility checks'. Certain Avalanche holdings are additionally subject to business-combination lock-up agreements.
- KYC / AML
- Yesdocumented
- Minimum
- documented
Documented at programme level. See complete terms.
unknown
- Fees
- documented
Documented at programme level. See complete terms.
unknown
- Timing and settlement asset
- documented
Documented at programme level. See complete terms.
Bidirectional switching between forms is asserted in one subordinate clause: "holders of SECZ may elect to switch between tokenized SECZ and nontokenized SECZ". Only the INBOUND leg is documented, and it is a coordination between two transfer agents rather than an internal book movement: the holder asks their broker to move the shares out of street name "through the Direct Registration System (DRS) or Deposit and Withdrawal at Custodian (DWAC) method" to Continental Stock Transfer (DRS & DWAC #7808); Continental then "records you as the registered owner of the shares" and issues a statement; and only "Once your shares are registered directly on the transfer agent's shareholder ledger" can they be converted into tokenized form and issued to a Securitize-registered wallet. Securitize warns that "Not all brokers support DRS transfers" and that broker fees vary. The OUTBOUND leg — de-tokenization back to the Continental book-entry position — has no published procedure, burn address, processing time or fee anywhere, and the unquantified switch latency is the constraint the S-1 itself blames for potential price discrepancies between the two forms.
- Route currently available
- Not establishedunknown
- Successful redemption independently observed
- Not establishedunknown
- Secondary-market exit
- Asset-specific; inspect the exact-token report for current venues and liquidity.
- Timing / SLA
- Not established
- Transfer mechanism
- program-mediated, per-token whitelist. On-chain: Token-2022 DefaultAccountState=Frozen (verified 2026-09-16), so every new SECZ token account is frozen at birth and only the freeze authority (8Twerer..., an apparent program PDA) can thaw it; plus PausableConfig for a global halt. Off-chain: the Securitize Connect API documents wallet whitelisting scoped to a specific token ('adds a wallet address to the whitelist of an specific token', requiring a tokenId, since 'in a given domain there may be multiple tokens'), with wallet statuses 'ready, pending, failed' and a 'not-authorised' response state. Notably the whitelist is NOT tied to a platform-hosted wallet: 'This is not required, as the whitelisting at token level does NOT require the wallet being registered at Securitize iD' — a self-custodied address can be whitelisted directly. Contractually: 'Tokenization changes the form of ownership; it does not change the underlying nature of the share or override applicable legal, contractual or transfer restrictions', and specific Avalanche holdings carry business-combination lock-ups. US persons are the TARGET market here ('eligible U.S. investors'), which inverts the usual tokenized-equity geofence.
- US persons excluded
- No
Who keeps the price honest
Programme-level answer: who can create and redeem at the issuer, so a reader knows whether a token’s premium can be arbitraged away.
Only allowlisted wallets can hold or convert it and it has no open market, so there is no price to keep honest.
- Who can create and redeem
- Holders onboarded with Securitize Markets (KYC, US-eligible investors); only whitelisted wallets can hold the token.
- How
- Inbound: DRS the shares to Continental Stock Transfer, then Securitize issues the tokens to a whitelisted wallet. Outbound: asserted in one clause, with no published procedure.
- How fast
- Days inbound (a DRS transfer); nothing published for the way back.
- When
- Business days.
- Minimum
- None published
- Cost
- Not published; brokers’ DRS fees vary
- Shares or cash
- Yes: the token is the registered share in another form.
Read on 2026-09-30 from the issuer’s redemption terms; the terms and their sources are under Can a holder redeem?.
Backing, custody and insolvency
- Collateral ratio
- 1:1
- Composition
- shares
- Rehypothecation
- undisclosed
- Bankruptcy remote
- No
- Security interest
- No
- Verification type
- transfer-agent-register
- Verification agent
- Two transfer agents, and only the tokenized one is an affiliate. (1) Continental Stock Transfer & Trust Company — SEC transfer agent File No. 084-00034, CIK 0000024179, DRS & DWAC #7808 — is the transfer agent of record for the Securitize common stock, named in the S-1/424B3 Description of Securities and in Securitize's own tokenize instructions, and independent of the issuer. (2) Securitize Transfer Agent, LLC — SEC transfer agent File No. 084-06638, CIK 0001782266 — is the "exclusive digital transfer agent for tokenized securities issued on Securitize's platform"; the S-1 says, generically for all Securitize-issued tokenized securities, that multichain deployments are reconciled through "the same control book and master securityholder file", but never says who keeps that file for Tokenized SECZ. It is an affiliate of the issuer, not an independent party, and is never named in the S-1. No transfer-agency agreement for SECZ is published on either side, so the division of the books between them, and how the two are reconciled, is unpublished. Neither agent's current Form TA-1 discloses a service-company relationship with the other (Continental TA-1/A 2026-06-30; Securitize Transfer Agent TA-1/A 2026-08-27).
- Verification frequency
- continuous, claimed — 'every transaction and ownership record is maintained on a single, verifiable ledger accessible in real time'; multichain deployments 'are managed and reconciled through the same control book and master securityholder file to ensure that total outstanding units remain consistent and singular across chains'
- Verification notes
- NO PUBLIC VERIFICATION FEED. Securitize publishes no instruments API, no per-token supply endpoint, no allowlist enumeration and no reconciliation report for SECZ. The token's TokenMetadata URI (https://metadata.securitize.io/secz.json) resolves but contains only name, symbol, description and image — no CUSIP/ISIN, no register link, no supply, no attestation. The Securitize Connect API (https://sec-connect-api-docs.securitize.io/wallets) documents the whitelisting mechanism but is an authenticated partner API, not a public verification surface. VERIFIED ON SOLANA MAINNET BY RWA-SONAR, 2026-09-16 (slot ~447535518): mint 5VzwKkvynPJzcgwhBe7ESEyNgqMbo15yBu7Sehssd9ED is a Token-2022 mint, decimals 6, supply 148,998.000000, name 'Securitize Corp.', symbol 'SECZ'; 117 Token-2022 accounts exist for the mint (getProgramAccounts with mint filter); extensions MetadataPointer, PausableConfig, DefaultAccountState=Frozen, PermanentDelegate, ScaledUiAmount, TokenMetadata; NO TransferHook. Authority topology, and this is the notable finding: mintAuthority == freezeAuthority == 8TwererfKZwiBfKQs2bQmVRrezqeFG3JvrVsbpGaPbQs, and getAccountInfo on that address returns null — a zero-lamport, never-initialized account, which is the signature of a program-derived address used as a CPI signer rather than a funded wallet. That is a MEANINGFULLY BETTER key posture than Bullish, whose mint/freeze authority is a plain funded wallet: it implies a Securitize program mediates minting and thawing. It is not proof — the owning program was not identified, and the separate authority on the extensions (D2kGPFTyGSeeTSCA1kEzKZNrdMvYKPLdZtrmAnnK6jCS, which holds permanentDelegate, pausable, scaledUiAmount, metadataPointer and tokenMetadata update authority) was not resolved either. MEASURED CONTRADICTION: press coverage (CoinDesk, PRNewswire, RWA.xyz-sourced) reports '$295 million in tokenized shares'. The Solana mint holds 148,998 tokens, worth roughly $1.24M at the ~$8.35 price Jupiter reported on 2026-09-16 — about 0.4% of $295M. Either essentially all of the $295M sits on Avalanche (consistent with the S-1, which puts the locked-up business-combination shares there) or the $295M figure is not comparable to on-chain supply. Any grading that attributes the $295M headline to Solana is wrong by more than two orders of magnitude.
Corporate actions and economics
Fees, who gets paid and long-term incentives → · Initial programme research; coverage gaps are marked.
- Corporate actions
- Securitize markets corporate-action servicing as a core transfer-agent capability — the S-1 describes 'a comprehensive suite of securities services including real-time approval, record-keeping, distributions, dividend issuances and compliance solutions' — so the institutional machinery genuinely exists and is exercised for third-party issuers (BUIDL and others). For SECZ specifically nothing has been exercised: Securitize Corp. declares no dividend, so the distribution path is untested on its own stock; the mint's ScaledUiAmount multiplier is 1, so no split has occurred; and no tokenized-holder proxy process or on-chain voting is documented. Two mechanisms are disclosed that are unusual and material. (1) FORK POLICY: 'In the event of such a fork, Securitize would determine which chain constitutes the valid and authoritative record for purposes of ownership, recordkeeping, and the exercise of holder rights such as voting, redemptions, and distributions. Tokens existing on other forked chains would not be recognized as valid representations of the securities' — a rare, explicit, pre-agreed chain-exception policy, and simultaneously a statement that the issuer, not the chain, decides. It adds that it 'would generally expect to follow the fork recognized by principal stablecoin issuers used in settlement flows' and that 'In extreme circumstances, Securitize may determine that migrating assets to an alternative fork is necessary'. (2) MANUAL FALLBACK: 'Securitize has manual safeguards in place which help retain the appropriate records of ownership should the automated blockchain systems fail which it controls in its capacity as transfer agent' — an explicit off-chain recovery path that exists precisely because the chain is not the record. Emergency halt: PausableConfig on the mint, with no published policy for its use.
- Pricing
- reference market: exchange-nbbo · arbitrageable: true · notes: The same class trades on NYSE under SECZ, so a continuous reference price exists, and the token has on-chain liquidity: 'Trading of Tokenized SECZ on Solana is now enabled via on-chain liquidity provision partners', and Jupiter priced the mint at ~$8.35 on 2026-09-16 with a reported holder count of 44 and roughly $1.24M market value. The issuer is candid about the basis risk in its own prospectus: 'the simultaneous existence of both could potentially fragment liquidity across platforms, affect bid-ask spreads (particularly outside NYSE trading hours), and result in price discrepancies between Tokenized SECZ and nontokenized SECZ—especially if arbitrage is limited by operational or regulatory constraints', and 'Blockchain-based trading mechanisms may have significantly less liquidity and volume compared to national securities exchanges, such as NYSE'. Arbitrage is real but constrained twice over: the switch between forms has no published latency, and only broker-dealer-onboarded persons can hold the tokenized side at all, so the arbitrageur set is permissioned. Jupiter reported a -100% 24h volume change on 2026-09-16, i.e. no trades that day — the on-chain market exists but is thin. No oracle price feed for the Solana mint was located.
Primary documents and evidence
- Securitize Corp. Form S-1, filed 2026-07-31 — THE definitive primary document. Contains the 'tokenization of our common stock' risk factor ('Tokenized SECZ is not a separate share class'; broker-dealer onboarding gate; Solana trading via liquidity partners; Avalanche lock-ups; price-discrepancy warning), the blockchain-fork risk factor (control book, master securityholder file, Securitize determines the authoritative chain), the Fireblocks/manual-safeguards disclosure, and the 21-chain integration list.
- Securitize Corp. Form 424B3 prospectus, filed 2026-08-07 (registration effective per EFFECT 2026-08-07)
- Securitize Corp. Form 8-K filed 2026-07-08 — the business-combination 'super 8-K' (Items 1.01, 2.01, 3.01, 3.02, 3.03, 4.01, 5.01, 5.02, 5.03, 5.05, 9.01) for the Closing on 2026-07-01
- Securitize Corp. Form 8-K filed 2026-08-12 with Exhibit 99.1, Q2 2026 earnings release (mentions Solana)
- Securitize Transfer Agent, LLC SEC transfer-agent registration filings, SEC File No. 084-06638, CIK 0001782266 (TA-1 plus multiple TA-1/A amendments and annual TA-2 reports)
- Securitize press release, 2026-07-02 — 'Tokenizing SECZ: Securitize Brings Its Own Public Stock Onchain at Listing Day'. Names Securitize Transfer Agent, LLC; 'issuer-sponsored tokenization of the same common stock trading on the NYSE'; 'Tokenization changes the form of ownership; it does not change the underlying nature of the share or override applicable legal, contractual or transfer restrictions.'
- Securitize Connect API documentation — Wallets. Documents per-token whitelisting (tokenId required), wallet statuses 'ready, pending, failed' and 'not-authorised', and that 'whitelisting at token level does NOT require the wallet being registered at Securitize iD' (i.e. self-custodied addresses can be whitelisted).
- SECZ token metadata document referenced by the mint's TokenMetadata extension — resolves, on an issuer-controlled domain, but carries only name, symbol, description and image; no CUSIP/ISIN, no register link, no supply, no attestation
- Securitize tokenize instructions for SECZ — the issuer's own step-by-step route, and the document that settles who the holder of record is: "The transfer agent for Securitize Corp is Continental Stock Transfer (DRS & DWAC #: 7808)", "the transfer agent records you as the registered owner of the shares", and tokenization only "Once your shares are registered directly on the transfer agent's shareholder ledger". Client-rendered; read in a headed browser on 2026-09-18.
- Securitize Transfer Agent Terms of Service (last update June 2026) — the only holder agreement that governs the tokenized position: §5.1 TA services, §5.2 "Securitize acts as agent of the relevant issuer, not as a fiduciary to investors", §5.5 suspension grounds, §10.3 the $1,000 liability cap, §17.4 compliance with court and law-enforcement requirements
- Securitize Terms of Service (last update March 2026) — platform-level terms: account security and third-party access, refusal-to-process notice and error-correction procedure (§5), termination at will (§12), compliance with governmental and court requests (§16)
- Securitize Markets Terms of Service — the broker-dealer/ATS leg: §5.2 "Eligibility to trade on the ATS is determined by Securitize Markets in its sole discretion, subject to applicable law"
- Securitize Markets ATS Subscriber Manual v2.0, September 2026 — the ATS rulebook behind the gate: subscriber eligibility, order handling and the 1% commission per secondary transaction
- Securitize disclosure library — the index of every US disclosure document, which is how the three Terms of Service above were located; the token-terms gap this dossier recorded was an index gap, not an absence
- stocks.securitize.io — the SECZ trading front end (RFQ quotes, the 0.10% platform fee covering gas) and the entry point to the tokenize instructions
- SECZ platform FAQ — seven answers covering who may trade, how prices are expressed, order type and price discretion, platform fees, exchange-rate refresh and order creation; also the source of "Securities can only move between whitelisted wallets on the platform"
- EDGAR transfer-agent registration filings for Continental Stock Transfer & Trust Co, SEC File No. 084-00034, CIK 0000024179 — establishes that the independent registrar of record is itself an SEC-registered transfer agent with a current filing history (annual TA-2s through 2026-03-30, TA-1/A 2026-06-30)
- 8 Del. C. subchapter V — the statutory basis for a tokenized register: §151(f) makes the rights of holders of uncertificated and certificated stock identical, and §224 permits the stock ledger to be kept on "1 or more electronic networks or databases (including 1 or more distributed electronic networks or databases)" provided it can produce the §219/§220 stockholder list
- Continental Stock Transfer shareholder FAQs — the independent registrar's own procedures for the cases no Securitize document addresses: lost certificates (stop, surety bond, affidavit of loss and indemnity) and estate transfers (certified death certificate, notarised affidavit of domicile, medallion-guaranteed stock power)
- Securitize Investor Help Center, "What if I lost access to my wallet?" - the issuer-side lost-key procedure for investors: email [email protected], identity verification and a notarized affidavit; "We can recover most tokens from lost wallets" but recovery "may not be possible" in some circumstances. Generic to Securitize tokens, not SECZ-specific. Live page Cloudflare-blocked; text read from the Wayback capture of 2025-04-23 (identical in every capture since 2023-06-08).
- Official stock catalogue — canonical SECZ Solana mint
Open research questions (15)
- Where is the $295M? Press reports $295M of tokenized SECZ; the Solana mint holds 148,998 tokens (~$1.24M). The S-1 puts locked-up business-combination shares on Avalanche, so the balance is presumably there — but Securitize publishes no per-chain supply figures and nothing reconciles the headline to the chains. The Avalanche contract address should be identified and its supply read to close this.
- PARTLY ANSWERED (2026-09-18, re-examined 2026-09-23): before tokenization the holder is a registered holder in their own name, not a customer position behind the group's broker-dealer. Securitize's tokenize instructions route the holder through direct registration BEFORE any token exists — the broker DRS/DWACs the shares to Continental Stock Transfer, "the transfer agent records you as the registered owner of the shares", and only then "Once your shares are registered directly on the transfer agent’s shareholder ledger, they can be converted into tokenized form" (static source https://stocks.securitize.io/drs/brokers/general_instructions.md, step 5). The instructions stop there; the request form sends symbol, token id, quantity, the Continental account id and a wallet address to Securitize. What Continental's register shows AFTER conversion is not published — see the next register question.
- What is the correct name of the gatekeeping broker-dealer? The S-1 says 'Securities Markets, LLC'; Securitize's broker-dealer is publicly known as Securitize Markets, LLC. Most likely a typo in a registration statement, but it is the entity that controls who may hold the security, and it should be confirmed against the FINRA/SEC BD registration rather than assumed.
- Which entity holds the on-chain authorities, and under what program? PARTLY ANSWERED (2026-09-23): 8Twerer… (mint + freeze) is a program-derived address of Securitize program 9yy4W1B5GyF1JrrZDG3UE6cqPTJzCPihErJNfEV14BGi — in transaction 4CYGoHpiNgwNN2WuKFJKBwZ5dmoRaXAT6FWcVh4xxkmTQ5WccHaV5nsGXdwBafSy7caAUiTeJZbjNCBDmvwCE9hV (2026-08-12) that program, called from Securitize's DS registry program FydSLhkSMSM5VPmsrQgugrUmLZqcyMTbDCEEsXdjaxew (instruction "Whitelist"), thawed a new SECZ account with 8Twerer… as freeze authority, which only an invoke_signed by the owning program can do. It has held both authorities only since 2026-08-11: freeze authority moved from B2Psxcut8sEVTSEC92ELQfK2veHUuWivuxxHToVq4irF at 20:41:28Z (8V4Pzz62ZcJGdye26RrMnJu2LrBFzbh56PhopxD5LV2MoAsAwmLXhNgP1vDZpJ4bisviCq5zAQqnrKMoiiZcbDt) and mint authority from 4BjYWQ9MgvE4haFXa5mjtCb75SoFoAiukk4j5NwTZH8a at 20:42:58Z (4oF95rC7UZa9HFveRjDBDeJKnKHmR6SAciVu7chmL1ei5iAt9pZ2aoJbapHpScYugNxAQJLJvWNJm6Zv8G4yyWjM); both predecessors are on-curve, funded system accounts, so for the first six weeks after listing mint and freeze sat with ordinary keys. Both Securitize programs (9yy4W1… and FydSLh…) are upgradeable by 8d36iv2YUD8yDChuVZchx1NqE4qkDWCAEgsUEEUqzbB6, an on-curve funded system account (so not a Squads vault; possibly a single key or an MPC key) — so the program mediation is only as strong as that key. D2kGPFTyGSeeTSCA… (permanent delegate, pause, split, metadata) remains an on-curve key. Which legal entity holds any of these keys is still unattributed.
- What are the 117 token accounts? 148,998 tokens across 117 accounts, with Jupiter reporting 44 holders and a top-holders concentration of ~11.7%. How many are investor self-custody wallets versus platform/custodian/liquidity-pool accounts is unknown. getTokenLargestAccounts on the public RPC returned HTTP 429 on 2026-09-16 and should be retried against a paid endpoint.
- Who are the 'on-chain liquidity provision partners' on Solana? The S-1 says Solana trading 'is now enabled via on-chain liquidity provision partners' without naming them. Since holding SECZ requires whitelisting, a liquidity pool must itself be whitelisted — so the pool addresses, and whether pool LPs must be onboarded, are open. Jupiter reported zero volume in the 24h to 2026-09-16.
- Is SECZ actually live as DeFi collateral? ANSWERED and DECODED (2026-09-23, finalized slot 449783798): yes, on Loopscale, in one loan. HUyo5aYaNQvodYmy8TmjnpcxQCk3PVsbyTJUyjmAihFx (program 1oopBoJG58DgkUVKkEzKgyG9dvRmpgeEm1AVjoHkF78) holds 13,391.402983 SECZ against 1,513.732542 USDC owed to Loopscale's curated "USDC RWA" vault (Hb681P…, manager "Loopscale Asset Curation") at 7% APY; it is a 1-day term rolled every day since 2026-08-16 by Loopscale's refinance admin, latest 2026-09-23T18:00:58Z to 2026-09-24 18:00:58 UTC (loan maturity) — open, not repaid or liquidated. Of 123 SECZ token accounts exactly one is Loopscale-owned and no other Loan names SECZ. Market configuration (MarketInformation DTzzuG…, asset index 1): LTV 20%, liquidation threshold 40%, no allocation or borrow cap, price from Loopscale's BEAM adapter mirroring a RedStone end-of-day feed "SECZ_EOD" ($13.00 at 2026-09-23T08:15:10Z) with a 65,535 s maximum age; a second, shared Loopscale market (Go6kfC…) also lists SECZ at the same limits but its SECZ-quoting strategies hold about $12 of USDC. Securitize's registry program created and thawed the Loan's SECZ token account on 2026-08-10 (before the loan existed), so the Loan PDA was individually whitelisted. STILL OPEN: no Loopscale liquidator (engine mkr7azob…) holds a SECZ token account, so a liquidation would need Securitize to thaw one first; and the RedStone value was not reconciled to the NYSE close. Record: stocks/data/protocol-market-research.json (loopscale:secz-usdc-usdc-rwa-vault).
- Has the fork policy ever been applied, and who bears the loss? The S-1's fork provisions are the most developed chain-exception policy in this universe, but they allocate authority without allocating loss: nothing states what happens to a holder whose tokens end up on the chain Securitize does not recognise, or who compensates them. Also note the dependency it creates — the tie-break heuristic is whichever fork 'principal stablecoin issuers used in settlement flows' recognise.
- How do dividends, proxy voting and splits work for a tokenized holder? Securitize sells 'distributions, dividend issuances' as transfer-agent services and runs them for third-party issuers, but Securitize Corp. pays no dividend, the ScaledUiAmount multiplier is 1, and no tokenized-holder proxy process is documented. Untested on its own stock. Note the earnout structure (VWAP thresholds of $15/$20/$25 triggering Securitize Earnout Shares over five years from Closing) will cause share issuance that must propagate to the mint — a live, dated test of the control-book-to-chain path.
- What is the token-to-nontokenized switch latency and fee? Unpublished, and it is the constraint the S-1 itself blames for potential price discrepancies.
- Has the Solana token program been independently audited? Nothing public ties an audit to this deployment, despite Securitize's scale (BUIDL alone was >60% of its tokenized AUM at 2025-09-30) and its 21-chain integration.
- What is the de-tokenization route? The S-1 asserts holders "may elect to switch between tokenized SECZ and nontokenized SECZ" and the issuer publishes the inbound leg in full (DRS or DWAC to Continental, then issuance to a whitelisted wallet), but no document anywhere describes the outbound leg — no burn address, no request form, no latency, no fee and no statement of who bears the price risk while the position is in transit between the two forms.
- UNRESOLVED (searched 2026-09-23): where is a TOKENIZED SECZ holding recorded? Continental Stock Transfer is the transfer agent of record ("The Transfer Agent for the Securitize Common Stock is Continental Stock Transfer & Trust Company", S-1/424B3 p. 124). Securitize describes itself as "the exclusive digital transfer agent for tokenized securities issued on Securitize's platform" (S-1 p. 87) using "a public blockchain as the master securityholder file" for "the majority of our customers" (p. 102), and its stocks page says "we coordinate with existing transfer agents or set up new ones" and that tokens are "backed by legal registration and reconciliation with traditional ledgers". No primary source says which of three models applies after conversion: (a) Continental keeps the token holder on its book by name, Securitize's ledger mirroring it; (b) Continental shows a Securitize entity or nominee for all tokenized shares, the token ledger being the sub-register (the token holder would then be a beneficial, not record, holder); (c) Continental has appointed or delegated the tokenized portion to Securitize Transfer Agent as co-registrar. Evidence against a delegation filed as such: neither agent's Form TA-1/A lists the other as a service company (Continental 2026-06-30: engages none, serves only TMX Equity; Securitize Transfer Agent 2026-08-27: Pacific Stock Transfer only). The bylaws (§5.04) transfer shares "on the record of stockholders" and do not mention tokens. On-chain, Securitize's registry program recorded the Loopscale Loan PDA as a wallet of investor 675cd1b765ec9b268dc4385e (memos DSRegistryServiceInvestorAdded/WalletAdded, 2026-08-10), i.e. the token ledger attributes wallets to off-chain investor ids — consistent with (a), (b) or (c). Searched: S-1 and 424B3 (Description of Securities, risk factors, Business, exhibit index — no transfer-agency agreement for SECZ; the only TA agreements filed are BlackRock BUIDL's), the 2026-06-05 proxy/prospectus (BCA §2.11 exchange via Continental into DTC book entry; Annex D bylaws Art. 5), 8-K 2026-07-08, 8-K/A and 10-Q of 2026-08-13, 8-K 2026-08-12, S-8 2026-09-02, both agents' Forms TA-1/A and Securitize Transfer Agent's TA-2, the Securitize Transfer Agent Terms of Service, stocks.securitize.io (tokenize instructions and their static .md sources, transfer_agents.json), securitize.io/investments/stocks and the crypto-task-force letter. No SECZ-specific FAQ or tokenization terms exist on securitize.io (/secz, /faq return 404). The fastest resolution is a Continental shareholder-services inquiry or an issuer IR statement.
- TO WATCH, not decided: two patent actions in D. Del. name Securitize I, Inc. — Securitize I v. tZERO Group, 1:26-cv-00722 (patents said to read on the DS Protocol and Vault Registrar; tZERO IP's amended counterclaims of 2026-07-17, D.I. 15, assert five patents — US 11,216,802, 11,394,560, 12,223,496, 12,099,996 and 12,051,078) and Liquid Rarity Exchange v. Securitize I, 1:26-cv-00698. Neither has a merits decision. State of 1:26-cv-00722 on the RECAP docket read 2026-09-23: two motions pending, none ruled on — tZERO Group's motion to dismiss the complaint (D.I. 9; its reply, D.I. 20, filed 2026-07-24) and Securitize's Rule 12(b)(6) / 35 U.S.C. § 101 motion to dismiss the amended counterclaims (D.I. 24-25, filed 2026-08-21; tZERO's answering brief in opposition, D.I. 27, filed 2026-09-18; Securitize's reply due 2026-09-30 under the so-ordered stipulation D.I. 21 of 2026-08-20). The 2026-09-04 response date printed on D.I. 25 was the Local Rules default; the so-ordered stipulation replaced it, so briefing is still open. 1:26-cv-00698: Securitize moved to dismiss 2026-08-17 (D.I. 9) and Liquid Rarity filed an amended complaint 2026-09-14 (D.I. 14). Both were found through a CourtListener RECAP search (recorded in whatIf[court-order].searched) and are now followed by the case-law watcher (caselaw-extra.json); only the docket sheets and D.I. 27 have been read, not the patents' claims; they are case-law watcher candidates because the technology they touch is the platform the tokenized register runs on.
- PARTLY ANSWERED (2026-09-23): the Securitize help-centre article "What if I lost access to my wallet?" (investorsupport.securitize.io/hc/en-us/articles/7331990591127) is still Cloudflare-challenged live (curl, WebFetch, headed Chrome; the Zendesk help-center API redirects to /hc/en-us/restricted), but the Wayback Machine holds five 200 captures from 2023-06-08 to 2025-04-23 with identical text: "We can recover most tokens from lost wallets, however, there are circumstances where recovery may not be possible. Please note, the process to recover tokens will include verification of identity and a notarized affidavit." Still open: whether the live text has changed since April 2025, and whether this generic procedure (written before SECZ existed) applies to Tokenized SECZ - the S-1's burn-and-reissue passage sits in the MD&A discussion of tokenized FUNDS and neither source names SECZ.