(IDEATION) SCP219: Move rFOX to Mainnet

Proposal Discussion
1

Summary

SCP219: Move rFOX to Ethereum Mainnet

Move rFOX from Arbitrum to Ethereum Mainnet on October 1st. Most FOX already lives on Mainnet, so this puts the program where the tokens are. Rewards temporarily go from 25% to 50% of revenue for the first three months to get people to move quickly.

Abstract

rFOX is on Arbitrum today, so if you hold FOX on Mainnet you have to bridge before you can stake. Most people hold on Mainnet.

This deploys the same audited rFOX contract to Ethereum Mainnet, live October 1st. Stakers get 25% of DAO revenue in USDC and the 5% burn keeps running exactly as it does now. Arbitrum stops earning rewards that day, and the Arbitrum contract’s unstaking cooldown drops to 0 so nobody is stuck waiting to move.

For October 2026, November 2026, and December 2026, Mainnet rFOX pays 50% of revenue instead of 25%. It goes back to 25% automatically on January 1st.

Motivation

The biggest chunk of FOX is on Mainnet. Meeting FOX holders where they are currently. Also matches where the DAO is headed. We’re consolidating liquidity and programs onto Mainnet, and our flagship revenue share program shouldn’t be sitting on a different chain.

Engineering already audited the contract and is confident it ports over cleanly.

Specification

  • Go live: October 1st, 2026. Mainnet only after that.
  • Contract: Same audited rFOX contract, no functional changes.
  • Boost: October, November, and December pay 50% of revenue. Back to 25% automatically on January 1st, 2027.
  • Arbitrum: Cooldown drops to 0 days immediately so people can move. Rewards go to 0% once Mainnet is live. Anything accrued before then still gets paid.

Cost: The boost runs about $5,000/month, roughly $15,000 total, based on 2026 revenue. It moves with revenue since it’s a percentage. Dropping the Arbitrum Snapshot voting strategy saves around $6,000/year per GK on an ongoing basis.

Benefits

  • Puts rFOX where the most liquidity and FOX already is.
  • Lines up with the DAO’s move to simplify and conslidate
  • Opens the program to every Mainnet holder who wouldn’t bridge.
  • Potential ongoing cost savings from not having to pay for advanced snapshot strategies of $6k/year

Drawbacks

  • 27M FOX can unlock at once. Dropping the Arbitrum cooldown to 0 means a lot of FOX becomes available at the same time. If people sell instead of migrating to the new contract, there could be massive sell pressure.
  • Mainnet gas is more expensive. Staking costs more than on Arbitrum, which hurts smaller stakers most.
  • Three months of reduced treasury revenues. Roughly $15,000 in extra payouts.
  • Some people won’t move due to lack of paying attention. Anyone who misses it stops earning October 1st.
  • There’s a cliff in January for rewards, could trigger unstaking.
  • This will require work on the Engineering side to launch contract, adjust revenue dashboards, and update the interface to include both contracts for withdrawing on the old one if a user is staked into it, and then also to bridge and stake into the new one.

Vote

For: Move rFOX to Ethereum Mainnet on October 1st, 2026, with a 28 day cooldown, 25% of revenue paid in USDC. This would get a temporary bump to 50% of revenue for October through December. Once mainnet contract is launched, a 0 day Arbitrum cooldown, and Arbitrum rewards ending at go live.

Against: rFOX stays on Arbitrum.

For, with changes: Please comment the changes you’d like to see.

3 Likes
2

I dont see the January 2027 as a cliff, its a return to normal.

Bonus stops..

other wise good post, thanks for putting up the proposal.

Im looking forward to this happening.

2 Likes
3

Thanks for writing and posting this proposal in ideation. I’m in favor of the migration in the stated conditions.

I suggest to plan announcements on all relevant channels (Discord, Twitter, etc.):

  1. When/If the proposal passes to give all the users the key deadlines/info sufficiently in advance.
  2. 8-9 days before the day the contract is available (give time to get out of RFOX on Arbitrum) and bridge back to Ethereum.
    I don’t think liquidity will be great on liquidity-based routes for too long if 27m FOX have to migrate, so bridging using the official Arbitrum bridge will likely be the best bet to preserve your FOX… and Arbitrum rollups take ~7 days to complete.
  3. On the day when the contract is available/usable on Ethereum.
  4. 2 weeks after if there are stragglers left in the Arbitrum contract.

Since we don’t have a Marketing Workstream currently to orchestrate these I think these tasks should be added in the proposal and maybe define people responsible for these (likely the ones with the account/perms and time to do them :sweat_smile: ).

1 Like
4

I agree with the need for a defined communications and execution plan here. This should probably be treated as part of the proposal scope, not an informal follow-up after the vote.

Because this migration involves unstaking, bridging, restaking, revenue-share changes, and a potential 27M FOX unlock event, users need clear deadlines and repeated reminders across the relevant channels. Discord, Twitter/X, forum, app/interface messaging, and any treasury/rFOX dashboard surfaces should all point to the same timeline.

I would also like us to clarify the timing around the Arbitrum cooldown change. If the cooldown only drops to 0 on October 1st, then users may still need several additional days to bridge back to Ethereum through the official Arbitrum bridge before they can stake on Mainnet. If the goal is for users to be ready when the Mainnet contract launches, then the DAO may need either an earlier cooldown adjustment, an earlier migration window, or very clear messaging that not everyone will be able to participate immediately on day one.

Suggested communication checkpoints:

  • When or if the proposal passes: announce the decision, key dates, migration path, reward change, and risk of missing the deadline.

  • At least 8–9 days before Mainnet rFOX becomes available: remind users that official Arbitrum withdrawals can take about a week, and that liquidity-based routes may not be ideal if a large amount of FOX is moving at once.

  • Launch day: publish contract links, staking instructions, Arbitrum withdrawal guidance, and dashboard links.

  • Two weeks after launch: follow up with any users still staked or stranded in the Arbitrum contract.

  • End of December / before January 1st: remind users that the temporary 50% revenue-share boost returns to 25%.

I also support assigning clear owners for these tasks. Since there is no current Marketing Workstream, the proposal should identify who is responsible for forum updates, Discord posts, Twitter/X posts, app messaging, dashboard updates, and post-launch migration reporting.

My main ask is that the migration plan includes communications ownership, date-based reminders, and monitoring of how much FOX is unstaked, bridged, restaked, or left behind. This is not just a contract move. It is a user migration, a liquidity event, and a treasury/revenue-share transition happening at the same time.

1 Like