Stock Wars protocol notes for Robinhood Chain launch. Back to site
Stock Wars

Protocol Documentation

Stock Wars Launch Notes

A practical overview for deploying, verifying, configuring, and operating Stock Wars on Robinhood Chain. This document is written for launch operators, frontend integrators, and early protocol reviewers.

1. Network Configuration

Stock Wars is designed for Robinhood Chain mainnet. The frontend should request the correct chain before allowing users to approve or stake SW tokens.

2. Contract Deployment

Deploy the Stock Wars contract after the SW token address is finalized. The constructor receives the SW token address and the maximum feed staleness window.

Constructor

Blockscout Verification

3. Round Model

Each round compares two tokenized equities by percentage movement. Users stake SW on the side they believe will outperform. When the round closes, verified feeds determine the winner.

4. Void Conditions

A void result should be treated as a clean user-protection path. In that case, users receive their stake back rather than entering a forced settlement.

5. Feed Registry

These feed addresses are configured for Robinhood Chain mainnet and should be mirrored in the frontend configuration.

6. First Round Recommendation

US equity feeds should be treated with US Eastern market timing in mind. Avoid ending rounds over the weekend because stale feeds may cause a void outcome.

7. Frontend Configuration

The landing page can remain static, while the app interface should reference deployed contract addresses and enforce the Robinhood Chain network before user actions.

8. Launch Checklist