How We Verify Prop Firm Payouts On-Chain
Futures prop firms, paid through Rise
How Rise payments are read
Futures prop firms pay through Rise. Rise records every firm-to-payee payment on Arbitrum One before the payee withdraws, so payouts later cashed out to a bank are included; payments made outside Rise are not. Recipients are Rise IDs and include affiliates and vendors paid from the same account. Two eras: before June 20, 2026, a payout was a RISEPAY transfer from the firm's Rise ID to the payee's Rise ID; since then the firm's Rise company account burns RiseUSD and records the payment, naming the payee account, which we map to its owner Rise ID from the account's creation event — so a trader's payouts from both eras group together.
- RiseUSD (Rise v2 ledger, since Jun 20, 2026) — 0xace876e867ecf2c3d1b8097b160a666adce04cd0 ↗
- RISEPAY (legacy ledger, retired Jun 20–21, 2026) — 0x1b34bcc581d535d33c895fabce3c85f1bf3bdb33 ↗
Tradeify B
B: one Rise company account, payments labelled by Rise. Every payment Tradeify sent through Rise, read on Arbitrum One: RiseUSD payment events in the executed state from Tradeify's Rise company account since June 20, 2026, and RISEPAY transfers from its Rise ID before Rise migrated its ledger. Rise records the firm-to-trader payment on-chain before the trader withdraws, so payouts later cashed out to a bank are included; payments made outside Rise are not, and recipients include affiliates and vendors paid from the same account. One Rise account pays Tradeify's futures and Tradeify Crypto traders.
Watched on-chain:
- Tradeify Rise ID, RISEPAY payouts Sep 16, 2024 – Jun 20, 2026 — 0x9549875baf75b9921a0e507b6684565440504795 ↗
- Tradeify Rise company account: payments executed (RiseUSD) — 0x6f7a634a9d5f47a9da491a095f1c8375dc9495c1 ↗
- RiseUSD ledger token (Rise v2, since Jun 20, 2026) — 0xace876e867ecf2c3d1b8097b160a666adce04cd0 ↗
- RISEPAY ledger token (legacy Rise, retired Jun 20–21, 2026) — 0x1b34bcc581d535d33c895fabce3c85f1bf3bdb33 ↗
Rise balance read from:
- Rise company account (RiseUSD) (Arbitrum) — 0x6f7a634a9d5f47a9da491a095f1c8375dc9495c1 ↗
MyFundedFutures B
B: one Rise company account, payments labelled by Rise. Every payment MyFundedFutures sent through Rise, read on Arbitrum One: RiseUSD payment events in the executed state from MyFundedFutures's Rise company account since June 20, 2026, and RISEPAY transfers from its Rise ID before Rise migrated its ledger. Rise records the firm-to-trader payment on-chain before the trader withdraws, so payouts later cashed out to a bank are included; payments made outside Rise are not, and recipients include affiliates and vendors paid from the same account.
Watched on-chain:
- MyFundedFutures Rise ID, RISEPAY payouts Oct 18, 2023 – Jun 20, 2026 — 0x9f28bac1f793790dd3b0c2f8945f7ca28874f7a6 ↗
- MyFundedFutures Rise company account: payments executed (RiseUSD) — 0x228d19d3f95727625018272bb534ff3b17d2e212 ↗
- RiseUSD ledger token (Rise v2, since Jun 20, 2026) — 0xace876e867ecf2c3d1b8097b160a666adce04cd0 ↗
- RISEPAY ledger token (legacy Rise, retired Jun 20–21, 2026) — 0x1b34bcc581d535d33c895fabce3c85f1bf3bdb33 ↗
Rise balance read from:
- Rise company account (RiseUSD) (Arbitrum) — 0x228d19d3f95727625018272bb534ff3b17d2e212 ↗
FundedNext B
B: one Rise company account, payments labelled by Rise. Every payment FundedNext sent through Rise, read on Arbitrum One: RiseUSD payment events in the executed state from FundedNext's Rise company account since June 20, 2026, and RISEPAY transfers from its Rise ID before Rise migrated its ledger. Rise records the firm-to-trader payment on-chain before the trader withdraws, so payouts later cashed out to a bank are included; payments made outside Rise are not, and recipients include affiliates and vendors paid from the same account. One Rise account pays FundedNext's CFD and Futures traders (FundedNext Futures launched Apr 17, 2025), so totals are firm-wide. Direct crypto payouts are not included.
Watched on-chain:
- FundedNext Rise ID, RISEPAY payouts Feb 27, 2024 – Jun 19, 2026 — 0x2b9a16e8448091159cc2b2a205b11f2368d53cb6 ↗
- FundedNext Rise company account: payments executed (RiseUSD) — 0x3a19638e995791676f8b4c5bc4e6f7a74d87f10e ↗
- RiseUSD ledger token (Rise v2, since Jun 20, 2026) — 0xace876e867ecf2c3d1b8097b160a666adce04cd0 ↗
- RISEPAY ledger token (legacy Rise, retired Jun 20–21, 2026) — 0x1b34bcc581d535d33c895fabce3c85f1bf3bdb33 ↗
Rise balance read from:
- Rise company account (RiseUSD) (Arbitrum) — 0x3a19638e995791676f8b4c5bc4e6f7a74d87f10e ↗
Blue Guardian B
B: one Rise company account, payments labelled by Rise. Every payment Blue Guardian sent through Rise, read on Arbitrum One: RiseUSD payment events in the executed state from Blue Guardian's Rise company account since June 20, 2026, and RISEPAY transfers from its Rise ID before Rise migrated its ledger. Rise records the firm-to-trader payment on-chain before the trader withdraws, so payouts later cashed out to a bank are included; payments made outside Rise are not, and recipients include affiliates and vendors paid from the same account. One Rise account pays Blue Guardian's CFD and futures traders. Direct crypto payouts are not included.
Watched on-chain:
- Blue Guardian Rise ID, RISEPAY payouts Jan 10, 2024 – Jun 20, 2026 — 0x68035843020b6c0cd94dd29c273fff13c8e9a914 ↗
- Blue Guardian Rise company account: payments executed (RiseUSD) — 0x2a289ea079ad8b798186ca0cef17747f1ccc5844 ↗
- RiseUSD ledger token (Rise v2, since Jun 20, 2026) — 0xace876e867ecf2c3d1b8097b160a666adce04cd0 ↗
- RISEPAY ledger token (legacy Rise, retired Jun 20–21, 2026) — 0x1b34bcc581d535d33c895fabce3c85f1bf3bdb33 ↗
Rise balance read from:
- Rise company account (RiseUSD) (Arbitrum) — 0x2a289ea079ad8b798186ca0cef17747f1ccc5844 ↗
E8 Futures B
B: one Rise company account, payments labelled by Rise. Every payment E8 Futures sent through Rise, read on Arbitrum One: RiseUSD payment events in the executed state from E8 Futures's Rise company account since June 20, 2026, and RISEPAY transfers from its Rise ID before Rise migrated its ledger. Rise records the firm-to-trader payment on-chain before the trader withdraws, so payouts later cashed out to a bank are included; payments made outside Rise are not, and recipients include affiliates and vendors paid from the same account. The account belongs to E8 Markets and pays its forex, futures and crypto traders alike.
Watched on-chain:
- E8 Futures Rise ID, RISEPAY payouts Nov 23, 2023 – Jun 19, 2026 — 0xd19e945eeea57475b791c20112ebb4b628f5b95c ↗
- E8 Futures Rise company account: payments executed (RiseUSD) — 0x11879c38d7889f98d07957a46ad4f2e398835915 ↗
- RiseUSD ledger token (Rise v2, since Jun 20, 2026) — 0xace876e867ecf2c3d1b8097b160a666adce04cd0 ↗
- RISEPAY ledger token (legacy Rise, retired Jun 20–21, 2026) — 0x1b34bcc581d535d33c895fabce3c85f1bf3bdb33 ↗
Rise balance read from:
- Rise company account (RiseUSD) (Arbitrum) — 0x11879c38d7889f98d07957a46ad4f2e398835915 ↗
Funded Futures Family B
B: one Rise company account, payments labelled by Rise. Every payment Funded Futures Family sent through Rise, read on Arbitrum One: RiseUSD payment events in the executed state from Funded Futures Family's Rise company account since June 20, 2026, and RISEPAY transfers from its Rise ID before Rise migrated its ledger. Rise records the firm-to-trader payment on-chain before the trader withdraws, so payouts later cashed out to a bank are included; payments made outside Rise are not, and recipients include affiliates and vendors paid from the same account.
Watched on-chain:
- Funded Futures Family Rise ID 1, RISEPAY payouts Nov 7, 2024 – Mar 21, 2025 — 0xc5f7ebe3281b9243cf349835c8adf0a5907de578 ↗
- Funded Futures Family Rise ID 2, RISEPAY payouts Mar 2025 – Jun 19, 2026 — 0x4ab8ba763741b2a7bbd0e6ca483d054dcdf2683f ↗
- Funded Futures Family Rise company account: payments executed (RiseUSD) — 0xa9730dc351507b730c629e11ce2e2a1afec8f5b4 ↗
- RiseUSD ledger token (Rise v2, since Jun 20, 2026) — 0xace876e867ecf2c3d1b8097b160a666adce04cd0 ↗
- RISEPAY ledger token (legacy Rise, retired Jun 20–21, 2026) — 0x1b34bcc581d535d33c895fabce3c85f1bf3bdb33 ↗
Rise balance read from:
- Rise company account (RiseUSD) (Arbitrum) — 0xa9730dc351507b730c629e11ce2e2a1afec8f5b4 ↗
Top One Futures B
B: one Rise company account, payments labelled by Rise. Every payment Top One Futures sent through Rise, read on Arbitrum One: RiseUSD payment events in the executed state from Top One Futures's Rise company account since June 20, 2026, and RISEPAY transfers from its Rise ID before Rise migrated its ledger. Rise records the firm-to-trader payment on-chain before the trader withdraws, so payouts later cashed out to a bank are included; payments made outside Rise are not, and recipients include affiliates and vendors paid from the same account.
Watched on-chain:
- Top One Futures Rise ID, RISEPAY payouts Apr 10, 2025 – Jun 19, 2026 — 0xf016d90ec62fa7f4bec9af221c5039da6ce93a5c ↗
- Top One Futures Rise company account: payments executed (RiseUSD) — 0x498578d100d13826836e078d5b6a7094cc54eb32 ↗
- RiseUSD ledger token (Rise v2, since Jun 20, 2026) — 0xace876e867ecf2c3d1b8097b160a666adce04cd0 ↗
- RISEPAY ledger token (legacy Rise, retired Jun 20–21, 2026) — 0x1b34bcc581d535d33c895fabce3c85f1bf3bdb33 ↗
Rise balance read from:
- Rise company account (RiseUSD) (Arbitrum) — 0x498578d100d13826836e078d5b6a7094cc54eb32 ↗
Phidias Prop Firm B
B: one Rise company account, payments labelled by Rise. Every payment Phidias Prop Firm sent through Rise, read on Arbitrum One: RiseUSD payment events in the executed state from Phidias Prop Firm's Rise company account since June 20, 2026, and RISEPAY transfers from its Rise ID before Rise migrated its ledger. Rise records the firm-to-trader payment on-chain before the trader withdraws, so payouts later cashed out to a bank are included; payments made outside Rise are not, and recipients include affiliates and vendors paid from the same account.
Watched on-chain:
- Phidias Prop Firm Rise ID, RISEPAY payouts Aug 27, 2024 – Jun 19, 2026 — 0xdd3f6f0b13d804dd28198c6a3127b3db27f0bec8 ↗
- Phidias Prop Firm Rise company account: payments executed (RiseUSD) — 0xd615b4fa6c05295f95f191c0da83aa296c98ff1a ↗
- RiseUSD ledger token (Rise v2, since Jun 20, 2026) — 0xace876e867ecf2c3d1b8097b160a666adce04cd0 ↗
- RISEPAY ledger token (legacy Rise, retired Jun 20–21, 2026) — 0x1b34bcc581d535d33c895fabce3c85f1bf3bdb33 ↗
Rise balance read from:
- Rise company account (RiseUSD) (Arbitrum) — 0xd615b4fa6c05295f95f191c0da83aa296c98ff1a ↗
Alpha Futures B
B: one Rise company account, payments labelled by Rise. Every payment Alpha Futures sent through Rise, read on Arbitrum One: RiseUSD payment events in the executed state from Alpha Futures's Rise company account since June 20, 2026, and RISEPAY transfers from its Rise ID before Rise migrated its ledger. Rise records the firm-to-trader payment on-chain before the trader withdraws, so payouts later cashed out to a bank are included; payments made outside Rise are not, and recipients include affiliates and vendors paid from the same account.
Watched on-chain:
- Alpha Futures Rise ID, RISEPAY era (before the Jun 20–21, 2026 migration) — 0xf44a08f3c2f1e01facf2e316aece9655ffa55c01 ↗
- Alpha Futures Rise company account: payments executed (RiseUSD) — 0x99e4e17afac460736a2df1c1bd27e70e9c7b14e1 ↗
- RiseUSD ledger token (Rise v2, since Jun 20, 2026) — 0xace876e867ecf2c3d1b8097b160a666adce04cd0 ↗
- RISEPAY ledger token (legacy Rise, retired Jun 20–21, 2026) — 0x1b34bcc581d535d33c895fabce3c85f1bf3bdb33 ↗
Rise balance read from:
- Rise company account (RiseUSD) (Arbitrum) — 0x99e4e17afac460736a2df1c1bd27e70e9c7b14e1 ↗
TradeDay B
B: one Rise company account, payments labelled by Rise. Every payment TradeDay sent through Rise, read on Arbitrum One: RiseUSD payment events in the executed state from TradeDay's Rise company account since June 20, 2026, and RISEPAY transfers from its Rise ID before Rise migrated its ledger. Rise records the firm-to-trader payment on-chain before the trader withdraws, so payouts later cashed out to a bank are included; payments made outside Rise are not, and recipients include affiliates and vendors paid from the same account.
Watched on-chain:
- TradeDay Rise ID, RISEPAY era (before the Jun 20–21, 2026 migration) — 0x4b1cdd9fb0785ff8fbed22e8de3b795fe16bd632 ↗
- TradeDay Rise company account: payments executed (RiseUSD) — 0x7f452224633654653f37e5e5ce2f0f01d3623c91 ↗
- RiseUSD ledger token (Rise v2, since Jun 20, 2026) — 0xace876e867ecf2c3d1b8097b160a666adce04cd0 ↗
- RISEPAY ledger token (legacy Rise, retired Jun 20–21, 2026) — 0x1b34bcc581d535d33c895fabce3c85f1bf3bdb33 ↗
Rise balance read from:
- Rise company account (RiseUSD) (Arbitrum) — 0x7f452224633654653f37e5e5ce2f0f01d3623c91 ↗
Blusky B
B: one Rise company account, payments labelled by Rise. Every payment BluSky sent through Rise, read on Arbitrum One: RiseUSD payment events in the executed state from BluSky's Rise company account since June 20, 2026, and RISEPAY transfers from its Rise ID before Rise migrated its ledger. Rise records the firm-to-trader payment on-chain before the trader withdraws, so payouts later cashed out to a bank are included; payments made outside Rise are not, and recipients include affiliates and vendors paid from the same account.
Watched on-chain:
- BluSky Rise ID, RISEPAY era (before the Jun 20–21, 2026 migration) — 0xea397e5f9fc1230d1593973180f4bfc88ef0966c ↗
- BluSky Rise company account: payments executed (RiseUSD) — 0x736cb34fdf4515f13493b4553b7aa7bb2e79ec9b ↗
- RiseUSD ledger token (Rise v2, since Jun 20, 2026) — 0xace876e867ecf2c3d1b8097b160a666adce04cd0 ↗
- RISEPAY ledger token (legacy Rise, retired Jun 20–21, 2026) — 0x1b34bcc581d535d33c895fabce3c85f1bf3bdb33 ↗
Rise balance read from:
- Rise company account (RiseUSD) (Arbitrum) — 0x736cb34fdf4515f13493b4553b7aa7bb2e79ec9b ↗
Savius B
B: one Rise company account, payments labelled by Rise. Every payment Savius sent through Rise, read on Arbitrum One: RiseUSD payment events in the executed state from Savius's Rise company account since June 20, 2026, and RISEPAY transfers from its Rise ID before Rise migrated its ledger. Rise records the firm-to-trader payment on-chain before the trader withdraws, so payouts later cashed out to a bank are included; payments made outside Rise are not, and recipients include affiliates and vendors paid from the same account.
Watched on-chain:
- Savius Rise ID 1, RISEPAY payouts Nov 13, 2024 – Jun 2025 — 0x245d9be62a85a99c7d1eb2b334acb100399a768f ↗
- Savius Rise ID 2, RISEPAY payouts Jun 20, 2025 – Jun 2026 — 0x7d7695d7b7efe720e26fdc37c68cad7afc240ae2 ↗
- Savius Rise company account: payments executed (RiseUSD) — 0x65da091120d7230ee3db19e36001da1c0bbff429 ↗
- RiseUSD ledger token (Rise v2, since Jun 20, 2026) — 0xace876e867ecf2c3d1b8097b160a666adce04cd0 ↗
- RISEPAY ledger token (legacy Rise, retired Jun 20–21, 2026) — 0x1b34bcc581d535d33c895fabce3c85f1bf3bdb33 ↗
Rise balance read from:
- Rise company account (RiseUSD) (Arbitrum) — 0x65da091120d7230ee3db19e36001da1c0bbff429 ↗
The5ers B
B: one Rise company account, payments labelled by Rise. Every payment The5ers sent through Rise, read on Arbitrum One: RiseUSD payment events in the executed state from The5ers's Rise company account since June 20, 2026, and RISEPAY transfers from its Rise ID before Rise migrated its ledger. Rise records the firm-to-trader payment on-chain before the trader withdraws, so payouts later cashed out to a bank are included; payments made outside Rise are not, and recipients include affiliates and vendors paid from the same account. The account is firm-wide: The5ers pays its forex and futures traders from one Rise account.
Watched on-chain:
- The5ers Rise ID, RISEPAY era (before the Jun 20–21, 2026 migration) — 0x349b0ed1520eae1472f57eac77e390a1ecb0c677 ↗
- The5ers Rise company account: payments executed (RiseUSD) — 0x561bd6e920f28e0d691bd6ecce175dd409ab8833 ↗
- RiseUSD ledger token (Rise v2, since Jun 20, 2026) — 0xace876e867ecf2c3d1b8097b160a666adce04cd0 ↗
- RISEPAY ledger token (legacy Rise, retired Jun 20–21, 2026) — 0x1b34bcc581d535d33c895fabce3c85f1bf3bdb33 ↗
Rise balance read from:
- Rise company account (RiseUSD) (Arbitrum) — 0x561bd6e920f28e0d691bd6ecce175dd409ab8833 ↗
Legends Trading B
B: one Rise company account, payments labelled by Rise. Every payment Legends Trading sent through Rise, read on Arbitrum One: RiseUSD payment events in the executed state from Legends Trading's Rise company account since June 20, 2026, and RISEPAY transfers from its Rise ID before Rise migrated its ledger. Rise records the firm-to-trader payment on-chain before the trader withdraws, so payouts later cashed out to a bank are included; payments made outside Rise are not, and recipients include affiliates and vendors paid from the same account.
Watched on-chain:
- Legends Trading Rise ID, RISEPAY era (before the Jun 20–21, 2026 migration) — 0xf9a625400908c871b21b65585052a43e144d8c52 ↗
- Legends Trading Rise company account: payments executed (RiseUSD) — 0x44bf51ab580ba1ef55d7847b338af6a33c2b8895 ↗
- RiseUSD ledger token (Rise v2, since Jun 20, 2026) — 0xace876e867ecf2c3d1b8097b160a666adce04cd0 ↗
- RISEPAY ledger token (legacy Rise, retired Jun 20–21, 2026) — 0x1b34bcc581d535d33c895fabce3c85f1bf3bdb33 ↗
Rise balance read from:
- Rise company account (RiseUSD) (Arbitrum) — 0x44bf51ab580ba1ef55d7847b338af6a33c2b8895 ↗
Perp prop firms, paid in USDC
Hypernova A
A: payouts labelled on-chain by the firm. Every PayoutProcessed event on the Hypernova Vault (Arbitrum). The event names the trader and the 80/20 trader/firm split. Payment happens in the same transaction as the request.
Watched on-chain:
- Hypernova Vault: PayoutProcessed (Arbitrum) — 0x920973eebffd3bf7da14dd9fb52bd3bea1664c67 ↗
- Hypernova TradingAccounts: PayoutRequested (Arbitrum) — 0x429d8f223acb622e5e748f6a7bdf1235b2334fcb ↗
Reserve balances read from:
- Payout reserve (Arbitrum) — 0x43c5f0a81d538a527dbf35d27faa583ac7fada07 ↗
- Vault (Arbitrum) — 0x920973eebffd3bf7da14dd9fb52bd3bea1664c67 ↗
Propr A
A: payouts labelled on-chain by the firm. PayoutEvent on Propr's Payout Distributor (Ethereum) with reason 1 (trader payout). Reason 2 (affiliate commissions, sent from Propr's affiliate wallet) is excluded.
Watched on-chain:
- Propr Payout Distributor: PayoutEvent, reason 1 = trader payout (Ethereum) — 0x6e810d5c33a4355ce1b4107f5722787bfd7acf24 ↗
Reserve balances read from:
- Hot reserve (Ethereum) — 0x0353f53bd55b8011bad3de1d939ff4d8335cbb1d ↗
- Cold reserve (Ethereum) — 0xeaf635407208341439b8bdfcdf2e8c1773108c3f ↗
Breakout Prop B
B: single dedicated payout wallet. Outbound USDC transfers of $50 or more from Breakout's payout wallet (Ethereum), excluding moves back to Breakout's own treasury. Breakout pays affiliates in crypto too, so some $100+ transfers may be commissions.
Watched on-chain:
- Breakout payout wallet, outbound USDC (Ethereum) — 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48 ↗
Reserve balances read from:
- Payout wallet (Ethereum) — 0x9736603a31cf71efcb62631cc28f60bcbd31d565 ↗
Vest Markets C
C: withdrawals, not labelled as prop payouts. Withdrawed events on all five Vest bridge contracts (Base, Arbitrum, Ethereum) from July 1, 2026, when Vest Capital launched. Vest Capital payouts and ordinary exchange withdrawals look identical on-chain, so DPF reads the Vest account behind each withdrawal. An exchange user's account is their own trading wallet: it funds itself with deposits of thousands of dollars, is often the payout wallet, and sometimes receives withdrawals directly. A funded account only ever pays for evaluations (at most $1,000 at a time). 'Likely prop' counts a withdrawal only when its account is not the payout wallet, never deposited more than $1,000 at once into a Vest bridge and never received a withdrawal itself, the payout wallet never deposited either, and the amount is at or under $100,000. Wallets on a verified trader profile always count; a short admin list of known exchange wallets never does.
Watched on-chain:
- Vest bridge, Base (main payout contract): Withdrawed events — 0x55133c825603e6a5b9e911abab23e75dc3bb07af ↗
- Vest bridge, Base (older, tagged Vest: Deposit): Withdrawed events — 0x32d95f243f9e2c1344e4baa91a8d32711527ef7e ↗
- Vest bridge, Arbitrum (main payout contract): Withdrawed events — 0xb2f86eae1197032fa85389cc6c0f3b06b58dd1ea ↗
- Vest bridge, Arbitrum (older, tagged Vest: Deposit): Withdrawed events — 0x80c526d1c2fddadb3cd39810cd7a79e07b0eda00 ↗
- Vest bridge, Ethereum (tagged Vest: Deposit): Withdrawed events — 0xe80f92077131b9890599e418ae323de71ce1c35a ↗
- Vest bridge, Base (main payout contract): inbound USDC (depositor detection) — 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913 ↗
- Vest bridge, Base (older, tagged Vest: Deposit): inbound USDC (depositor detection) — 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913 ↗
- Vest bridge, Arbitrum (main payout contract): inbound USDC (depositor detection) — 0xaf88d065e77c8cc2239327c5edb3a432268e5831 ↗
- Vest bridge, Arbitrum (older, tagged Vest: Deposit): inbound USDC (depositor detection) — 0xaf88d065e77c8cc2239327c5edb3a432268e5831 ↗
- Vest bridge, Ethereum (tagged Vest: Deposit): inbound USDC (depositor detection) — 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48 ↗
Reserve balances read from:
- Vest bridge, Base (main payout contract) (Base) — 0x55133c825603e6a5b9e911abab23e75dc3bb07af ↗
- Vest bridge, Base (older, tagged Vest: Deposit) (Base) — 0x32d95f243f9e2c1344e4baa91a8d32711527ef7e ↗
- Vest bridge, Arbitrum (main payout contract) (Arbitrum) — 0xb2f86eae1197032fa85389cc6c0f3b06b58dd1ea ↗
- Vest bridge, Arbitrum (older, tagged Vest: Deposit) (Arbitrum) — 0x80c526d1c2fddadb3cd39810cd7a79e07b0eda00 ↗
- Vest bridge, Ethereum (tagged Vest: Deposit) (Ethereum) — 0xe80f92077131b9890599e418ae323de71ce1c35a ↗
My Funded Perps B
B: one Rise company account, payments labelled by Rise. Every payment My Funded Perps sent through Rise, read on Arbitrum One: RiseUSD payment events in the executed state from My Funded Perps's Rise company account since June 20, 2026. Rise records the firm-to-trader payment on-chain before the trader withdraws, so payouts later cashed out to a bank are included; payments made outside Rise are not, and recipients include affiliates and vendors paid from the same account. My Funded Perps opened payouts on September 11, 2026, after Rise's ledger migration, so there is no legacy era.
Watched on-chain:
- My Funded Perps Rise company account: payments executed (RiseUSD) — 0x748184d5661eaeb7432e9c7612ebece1f8f93d3a ↗
- RiseUSD ledger token (Rise v2, since Jun 20, 2026) — 0xace876e867ecf2c3d1b8097b160a666adce04cd0 ↗
- RISEPAY ledger token (legacy Rise, retired Jun 20–21, 2026) — 0x1b34bcc581d535d33c895fabce3c85f1bf3bdb33 ↗
Rise balance read from:
- Rise company account (RiseUSD) (Arbitrum) — 0x748184d5661eaeb7432e9c7612ebece1f8f93d3a ↗
What these numbers are not
- Verified on-chain payouts only. Totals may not represent a firm's full payout volume.
- Wallets may be used for purposes beyond trader payouts.
- Vest figures are withdrawals; Vest does not label prop payouts on-chain.
- Rise firms: every payment sent through Rise counts, including affiliates and vendors paid from the same account; payments outside Rise are not visible.
- Listings are not endorsements. No commercial relationship changes a firm's numbers or ranking.
Trader profiles and privacy
Every dollar figure comes from public blockchains and links to its transaction. A trader profile only decides how wallets are grouped and labelled: a name appears next to a wallet only after the owner proves control of it and asks for it to be shown. Anyone can have their name removed, or their wallets hidden from the leaderboard, by asking from the same proof; the on-chain data itself is public and stays on the firm pages as an anonymous address.