Registered SECZ common share administered by a digital transfer agent

What this analysis covers

1 current token address across 1 underlying inherits this analysis.

• SECZstock

Exceptions: none recorded. An asset-specific conclusion must be shown here before it overrides the inherited template.

Traceable conclusions

Each conclusion carries its classification, exact supporting words, source authority, location, governing law, holder scope and review date. A document saying something is not the same as an independently observed outcome.

Evidence confidence

Confidence is stated per conclusion type. It is not collapsed into one score.

Complete claim chain

Possessing the token is only the first link. Each intermediary can add a separate contract, governing law and failure dependency.

Parties that can interrupt or enforce the chain

Jurisdiction and holder eligibility

A wallet may be technically able to receive a token while its owner is contractually ineligible, unable to redeem, or excluded from rights under the governing documents.

Insolvency and enforcement

Bankruptcy remote

yes

Security interest

no

Security holder

—

Recorded priority

none

Collateral ratio

1:1

Collateral composition

shares

Rehypothecation

undisclosed

On-loan amount disclosed

—

Segregation / trust evidence

—

Omnibus / commingling evidence

—

Perfection / priority evidence

—

Custodian lien / set-off evidence

—

Who can enforce

The person recognised on the official share register has shareholder standing; the token and transfer-agent process determine whether the wallet holder is that person.

Holder standing

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 — but access runs through a broker-dealer's onboarding, so whether the holder is a registered holder of record in their own name or a customer of the broker-dealer is NOT established by any document located, and this is the central unresolved question for this issuer.

A contractual label such as “segregated”, “trust” or “first priority” is not treated as a court-tested insolvency result unless the dossier records that authority.

Corporate actions

Registered shareholder process

Dividends

none

Voting

full

Other 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.

Registration supports shareholder rights, but the operational channel for a token-held position must still be documented.

Redemption path

Available

yes

Eligibility

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.

Route

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.

KYC

yes

Minimum

unknown

Fees

unknown

Timing / SLA

—

Notes

—

Source authority and precedence

The conclusion follows the highest-authority source applicable to the specific product, holder and issue. A technical capability cannot create a legal right, and marketing cannot override operative terms.

1. 1
   Mandatory law, court orders and official registers

   These can override private terms and determine legal title, perfection, insolvency priority or eligibility.

2. 2
   Product-specific final terms and operative agreements

   The document governing this product or series controls over a general description, subject to mandatory law.

3. 3
   Base prospectus and binding programme terms

   These govern the programme except where valid product-specific terms supplement or disapply them.

4. 4
   On-chain state

   Authoritative for what the program and current keys can technically do, but not by itself for legal ownership or enforceability.

5. 5
   Official operating documentation and attestations

   Evidence of process or reserves; it cannot silently enlarge rights excluded by the controlling legal documents.

6. 6
   Marketing, press and third-party descriptions

   Useful context only. A conflict is resolved in favour of the higher-authority source and remains visibly recorded.

Recorded conflicts and corrections

• redemption.rails · contradicted-corrected

  CORRECTION to a quote, not a value: the dossier rendered this as "onboarding, KYC/AML verification, jurisdictional eligibility checks", which is not what the release says. The verbatim wording is "onboarding, KYC/AML checks, jurisdictional eligibility and applicable securities-law requirements". The substance is unchanged and redemption.rails is otherwise correct: no burn address, no process, no latency and no fee is published anywhere, which was re-confirmed by searching the S-1, the release, the Connect API docs and the token metadata.

  source ↗
• keyGovernance.delegate · contradicted-corrected

  CORRECTED unknown -> hot-key. The dossier recorded this authority as unresolved. It resolves cleanly: the address is an initialized, FUNDED, system-program-owned account with zero data (0.49997 SOL), i.e. a plain keypair wallet with no multisig program account behind it — the same shape as Bullish’s keys, not the PDA shape of this mint’s own mint/freeze authority. It holds permanentDelegate, pausableConfig, scaledUiAmountConfig, metadataPointer and tokenMetadata update authority, so one ordinary private key can claw back any holder’s position, halt the whole security and rewrite the split multiplier. This materially weakens the dossier’s comparative reading that Securitize has the better key posture: better for mint/freeze, not for claw-back and pause.

• issuer · contradicted-corrected

  CORRECTION, and the central one for this issuer. The `issuer` field asserted that Securitize "is also ... its own SEC-registered transfer agent (Securitize Transfer Agent, LLC)" and that "there is no independent transfer agent anywhere in the stack, unlike Superstate ... or Bullish". The S-1's own Description of Securities says otherwise, and the string "Securitize Transfer Agent" appears zero times in the S-1 and zero times in the 424B3. Continental was CEPT's transfer agent and the trustee of the SPAC trust account, and the registrar role carried through the de-SPAC.

  source ↗
• custodyVerification.agent · contradicted-corrected

  CORRECTION. custodyVerification.agent named only "Securitize Transfer Agent, LLC ... an affiliate of the issuer, not an independent party". There are two agents: Continental Stock Transfer & Trust Company for the common stock (File No. 084-00034, CIK 0000024179, DRS & DWAC #7808) and Securitize Transfer Agent, LLC for the tokenized sub-register (File No. 084-06638, CIK 0001782266). The issuer's own page confirms the first with the operational number attached, which is stronger than a filing mention because it is the route a holder actually uses.

  source ↗
• redemption.rails · contradicted-corrected

  CORRECTION. redemption.rails said the switch "is an internal book movement rather than a coordination between two agents — mechanically simpler than the Superstate peer's DRS route". The published inbound leg IS a DRS/DWAC route, to Continental, with the holder registered on Continental's ledger before any token is issued: "Once the transfer is verified, the transfer agent records you as the registered owner of the shares" and "Once your shares are registered directly on the transfer agent's shareholder ledger, they can be converted into tokenized form". The outbound leg remains entirely unpublished, so "un-auditable from outside" still holds for de-tokenization.

  source ↗

Document register

“Not structured” is a visible evidence gap: a date in a title is not silently promoted into metadata.

Open questions

• MINT ATTRIBUTION IS INFERRED, NOT PUBLISHED. Securitize has published no Solana contract address anywhere located. 5VzwKkvynPJzcgwhBe7ESEyNgqMbo15yBu7Sehssd9ED is attributed on the strength of its TokenMetadata URI pointing at metadata.securitize.io, matching name/symbol, the Token-2022 compliance extension set, a 2026-06-29 creation date (three days before listing) and a registry verified flag. That is strong circumstantial evidence, not issuer confirmation. Given four SECZ-branded impersonation mints on Solana, the single highest-value next step is asking Securitize IR to publish canonical addresses. Treat the address as high-confidence-but-unconfirmed until then.
• 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.
• ANSWERED (2026-09-18): a tokenized holder is a registered holder in their own name, not a customer position behind the group's broker-dealer. Securitize's own 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", the holder gets "an account statement or confirmation showing your name, account number, and the number of shares you hold", and only then can the position "be converted into tokenized form". Broker-dealer onboarding still gates ATS access and the whitelist still gates the wallet, but the ownership itself is direct registration. Residual gap: nothing published says whether the tokenized units are shown on Continental's ledger, on Securitize's control book, or on both.
• 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? 8Twerer... (mint + freeze) is an apparent PDA whose owning program was not identified; D2kGPFTyGSeeTSCA... (permanent delegate, pause, split, metadata) was not resolved at all. Whether these sit with Securitize Transfer Agent, LLC (the regulated registrar) or with an operating affiliate matters legally, and whether the program has a timelock or multisig gate matters for grading. Fireblocks MPC is disclosed for corporate treasury only.
• 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? Press of 2026-08-20 reports SECZ linked to Solana on-chain credit markets. Unverified by rwa-sonar. If true it would need an oracle feed (none located) and would raise the same jurisdiction-of-use question the Superstate/Kamino integration raises.
• 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.
• How are the two registers reconciled, and which one governs? Continental Stock Transfer keeps the register of record for the common stock; Securitize Transfer Agent, LLC keeps the control book and master securityholder file for the tokenized units and is "the exclusive digital transfer agent". No transfer-agency agreement for SECZ is published on either side, so the division of the books, the reconciliation cadence and the tie-break on a discrepancy are all undisclosed — exactly the gap Bullish closes explicitly with its register-of-members tie-break.
• 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; motion-to-dismiss briefing closed 2026-09-04) and Liquid Rarity Exchange v. Securitize I, 1:26-cv-00698. Neither has a merits decision. Both were found through a CourtListener RECAP search (recorded in whatIf[court-order].searched) and neither docket has been read in full; they are case-law watcher candidates because the technology they touch is the platform the tokenized register runs on.
• HUMAN LOOK NEEDED: the Securitize help-centre article "What if I lost access to my wallet?" (investorsupport.securitize.io/hc/en-us/articles/7331990591127) is indexed and exists but is Cloudflare-challenged to curl, WebFetch and a launched headed Chrome, so the issuer's own published lost-key procedure for investors has not been read. The S-1's burn-and-reissue passage sits in the MD&A discussion of tokenized FUNDS and is not applied to Tokenized SECZ by name anywhere.