Deployment & PONS

Deploying software to Robinhood

Robinhood Chain mainnet is EVM-compatible, with chain ID 4663. Its testnet uses 46630. A Solana program cannot be deployed as-is to either EVM environment. Port runtime-specific account handling, authorization, storage, oracle interfaces and token operations before testing.

A release should start on a development network with appropriate reference and adversarial tests. Financial protocols need independent review before accepting real assets. A test pass is evidence about those tests, not a general safety guarantee.

Launching a project token

The included PONS v2 encoder prepares an unsigned native-ETH launch transaction. It requires a verified factory address, launch configuration, fresh economics hash, unique salt, fee quote and deployed fee router as creator-fee recipient. The V1 ABI must not be substituted for V2.

A wallet transaction is still required to create the token. The interface currently links to PONS and does not provide a complete in-app token launch flow. Creating a token does not deploy the fork’s software, grant equity or confer ownership of source code.

Evidence before a live status

• Source commit and published build artifact.
• Test and review results covering the deployed revision.
• Correct chain, contract address and successful deployment transaction.
• Verified bytecode and configured dependencies, including treasuries and fee recipients.
• A separate token launch receipt and PONS link, where a token is created.

No hidden signing

This release does not hold visitor private keys or autonomously sign mainnet transactions. Wallet connection only shares an address after wallet consent. No purchase, deposit, approval or deployment follows from connection alone.