I've written the report to artifacts/report.md (about 53 KB), with a short artifacts/README.md describing the question and its limits. Both files are untracked and nothing was committed. The repo's local exclude file already ignores artifacts/.

What it covers:

• Chain comparison: BSC is an L1 with 0.45 s blocks since the Fermi fork on 2026-01-14, and fast finality. Robinhood Chain (ID 4663) is an Arbitrum Nitro layer-2 that settles to Ethereum. It uses ETH for gas, orders transactions first-come-first-served, and screens out sanctioned addresses. The table also lists DEX addresses taken from the PancakeSwap and Uniswap docs.
• Contract spec:
  • token factory and templates
  • bonding curve, with the maths and a check that the curve's last price matches the DEX starting price
  • quote-token registry for native tokens, stablecoins, crypto and Robinhood Stock Tokens
  • asymmetric buy/sell taxes
  • vaults, dividends and burns
  • LP burn/lock controls, lockers and vesting
  • multi-pool and stock-paired designs
  • migration to the DEX
  • a matrix of which features can be combined
• Main design constraints:
  • Uniswap's v3 docs say fee-on-transfer tokens don't work with its routers. Tax tokens should therefore migrate to V2-style pools, or charge the tax in a v4 / PancakeSwap Infinity pool hook instead of in the token.
  • Stock Tokens must be accounted for in raw units because of the corporate-action multiplier.
  • Their price feeds only update during market hours (24/5) and pause during corporate actions.
• Migration security: the migration spec is written against Four.meme's two documented exploits. One was a pool the attacker created in advance at a fake price (about $183k lost). The other moved locked tokens to the pool address before launch.
• Other sections: frontend/backend design with a separate indexer and finality rule per chain, how data stays in sync across chains, optional cross-chain tokens via LayerZero or CCIP, a 16-item security table, gas notes for each chain, and compliance notes. The compliance notes cover the US, UK, Canada and Switzerland restrictions on Robinhood Stock Tokens and the non-US limits on Ondo's BSC stock tokens.

How claims are marked: each one is tagged [F] (fact from a cited source), [I] (my inference or design recommendation), [U] (uncertain or second-hand) or [Q] (open question). Section 10 lists the conflicting claims and 10 unanswered questions. The most important open question is whether v4 and Infinity hooks can actually collect the custom fees that hook-based taxes need.

Checks: a script confirmed that every source cited in the text is listed in §11 and every listed source is cited.

Limits:

• I didn't deploy any contracts or check any address on a block explorer.
• Several sources (marked "(search)") were seen only in search excerpts.
• Some ecosystem figures come from a single secondary article: Robinhood Chain's fees and the Pons launchpad's token counts.
• The structural check doesn't prove the research is correct. That needs an independent review.
• The compliance section is not legal advice.