<h1>🗳️ FIP-017 Official Vote: Fry 3.0 Unified Token Migration</h1>
The FIP-017 community discussion period has concluded, and the official vote is now open.
FIP-017 proposes moving Fry Networks to Fry 3.0, a single unified Fry token designed to replace the current multi-token structure and simplify the ecosystem following FIP-016.
FIP-016 simplified the miner side of Fry Networks by authorizing the merge of FryHub miners into one Fry Edge Miner model and replacing deprecated IoT miner types with Fry Edge Miner keys.
FIP-017 now asks the community whether the token side should also be simplified into one unified token.
<h2>Documents</h2>
Please review the Fry 3.0 Whitepaper and Litepaper before voting:
Whitepaper:
<a href="https://www.frynetworks.com/_files/ugd/b2ad32_a3a992ddb0b54577b82294461ec607ff.pdf">https://www.frynetworks.com/_files/ugd/b2ad32_a3a992ddb0b54577b82294461ec607ff.pdf</a>
Litepaper:
<a href="https://www.frynetworks.com/_files/ugd/b2ad32_b1cee4bd0072444191511e97c02e8006.pdf">https://www.frynetworks.com/_files/ugd/b2ad32_b1cee4bd0072444191511e97c02e8006.pdf</a>
<h2>Why Fry 3.0?</h2>
Fry Networks has gone through two prior token generations, and both taught important lessons.
FRY 1.0 had an 8 billion supply, a long unlock schedule, and no freeze or clawback protections on the ASA. This created long-term supply pressure and limited the team’s ability to respond when users were affected by theft or scams.
FRY 2.0 fixed some of those issues by reducing supply and restoring freeze and clawback, but it also introduced a four-token structure:
<ul>
<li>FRY 2.0</li>
<li>fNODE</li>
<li>tFRY</li>
<li>fVPN</li>
</ul>
That model made more sense when Fry Networks had multiple separate miner types. After FIP-016 consolidated miners into Fry Edge Miner, the token structure also became more complicated than necessary.
Fry 3.0 is designed to fix that by returning Fry Networks to:
One miner model. One token. Every function.
<h2>What FIP-017 Would Approve</h2>
If passed, FIP-017 would approve the creation and launch of Fry 3.0 as a new unified Fry Networks token.
Fry 3.0 would replace the current Fry Networks token structure of:
<ul>
<li>FRY 2.0</li>
<li>fNODE</li>
<li>tFRY</li>
<li>fVPN</li>
</ul>
Fry 3.0 would become the token used across the Fry Networks ecosystem for:
<ul>
<li>Fry Edge Miner rewards</li>
<li>Platform fees</li>
<li>Staking</li>
<li>Verification staking</li>
<li>DAO governance</li>
<li>Dashboard integrations</li>
<li>fry.farm</li>
<li>fry.market</li>
<li>Future Fry Networks apps, services, and protocol revenue</li>
</ul>
<h2>Fry 3.0 Core Terms</h2>
FIP-017 would approve Fry 3.0 with the following core terms:
<ul>
<li>Token: Fry 3.0</li>
<li>Ticker: FRY</li>
<li>Blockchain: Algorand</li>
<li>Standard: Algorand Standard Asset</li>
<li>Maximum supply: 6,000,000,000 FRY</li>
<li>Recommended launch price: $0.005</li>
<li>Starting emission: 5,000,000 FRY per week</li>
<li>Annual emission decay: 15%</li>
<li>Default protocol fee split: 50% burn / 50% DAO treasury</li>
<li>Registration stake required to mine: 0 FRY</li>
<li>Primary miner: Fry Edge Miner</li>
</ul>
<h2>Fry 3.0 Supply Allocation</h2>
FIP-017 would approve a maximum Fry 3.0 supply of:
6,000,000,000 FRY
The planned allocation is:
<ul>
<li>Mining Rewards: 2,700,000,000 FRY</li>
<li>Team &amp; Development: 900,000,000 FRY</li>
<li>Treasury / Operations: 720,000,000 FRY</li>
<li>Legacy Conversion: 600,000,000 FRY</li>
<li>Liquidity Provision: 480,000,000 FRY</li>
<li>Ecosystem &amp; Partnerships: 300,000,000 FRY</li>
<li>Community Airdrops: 180,000,000 FRY</li>
<li>Advisors &amp; Contributors: 120,000,000 FRY</li>
</ul>
This supply is intended to support mining rewards, legacy token conversion, DAO treasury, DEX liquidity, ecosystem growth, community airdrops, team development, advisors, and contributors.
<h2>Launch Price</h2>
FIP-017 would approve a recommended Fry 3.0 launch price of:
$0.005 per FRY
This launch price is intended to balance miner accessibility, protocol sustainability, and market credibility.
At this price, the fully diluted valuation would be approximately:
$30,000,000
The launch price is also used in the whitepaper and litepaper examples for projected Fry Edge Miner rewards.
<h2>Fry Edge Miner Rewards Before and After Fry 3.0 Launch</h2>
If FIP-017 passes, Fry Edge Miner will move forward under the Fry 3.0 plan.
However, Fry 3.0 rewards will not begin until after the Fry 3.0 presale is complete and Fry 3.0 is live.
Until then, once FIP-017 passes, Fry Edge Miner devices will earn:
<ul>
<li>tFRY</li>
<li>fNODE</li>
<li>fVPN</li>
</ul>
Each of these tokens will be 1:1 convertible to Fry 3.0 during the migration process.
This means FEM miners will not be earning only one interim reward token before Fry 3.0 goes live. They will be earning three 1:1-convertible reward tokens, allowing FEM miners to effectively build up 3× base reward exposure under Fry 3.0 before Fry 3.0 rewards officially begin.
This allows Fry Edge Miner to begin operating after FIP-017 passes without forcing Fry 3.0 rewards to begin before the presale, ASA launch, liquidity deployment, and migration infrastructure are ready.
<h2>Network-Responsive Emissions</h2>
Once Fry 3.0 is live, Fry Edge Miner rewards would use the Network-Responsive Emission model described in the whitepaper and litepaper.
The mining rewards pool would start by emitting:
5,000,000 FRY per week
That weekly emission would decay by:
15% per year
Rewards would be split among online, healthy, registered Fry Edge Miner devices.
The fewer devices online, the higher each device’s share. As more devices join the network, each device’s share naturally decreases.
This creates strong early-adopter rewards while still allowing the reward pool to remain sustainable long-term.
<h2>No Registration Stake</h2>
FIP-017 would remove the need for a token registration stake to begin mining.
Fry Edge Miner operators would be able to install FEM, register a device, and begin earning at the base rate without needing to stake tokens upfront.
Verification staking would still exist, but it would be optional.
<h2>Verification Staking</h2>
FIP-017 would replace the Fry 2.0-era verification staking system with a Fry 3.0 verification staking system.
Fry 3.0 verification staking would use FRY 3.0 / USDC LP tokens.
This is intended to let operators increase their Fry Edge Miner reward multiplier while also helping deepen DEX liquidity.
The proposed launch tiers are:
<ul>
<li>Registered, no stake: 1×</li>
<li>24-hour LP lock: 1.5×</li>
<li>6-month LP lock: 3×</li>
</ul>
Existing verification stakes will be handled through the Fry 3.0 migration process wherever possible so users do not need to manually rebuild eligible existing verification status from scratch.
Any wallet-level claim or conversion action that requires a signature will still be handled through the migration interface.
<h2>Instant Claims and Matured Claims</h2>
Once Fry 3.0 rewards are live, Fry Edge Miner rewards would be claimable through the Fry dashboard.
Operators would be able to choose between:
<ul>
<li>Instant claim: receive 70% immediately, with a 30% fee</li>
<li>Matured claim: wait 1 month and receive 100%</li>
</ul>
The 30% instant claim fee would support the fee system described in the whitepaper and litepaper, including Fry Fee Genesis NFT fee distribution and protocol fee flows.
<h2>Legacy Token Conversion</h2>
FIP-017 would approve the following conversion ratios:
<ul>
<li>FRY 2.0 → Fry 3.0: 1:1</li>
<li>fNODE → Fry 3.0: 1:1</li>
<li>tFRY → Fry 3.0: 1:1</li>
<li>fVPN → Fry 3.0: 1:1</li>
<li>FRY 1.0 → Fry 3.0: 80:1</li>
</ul>
The reason tFRY, fNODE, and fVPN are included is to honor previous commitments and simplify the ecosystem into one token going forward.
<h2>Snapshot Timing</h2>
The original discussion considered taking the snapshot when the FIP-017 vote concluded.
After further review, FIP-017 now proposes that the snapshot be taken after the Fry 3.0 presale ends, not at the end of voting.
This gives the team time to complete the Fry 3.0 presale, prepare the ASA launch, finalize the migration interface, and give users clearer notice before the final migration snapshot.
Only eligible tokens held in wallets at the final snapshot block will be included in the migration.
Unclaimed legacy rewards at the time of the snapshot will not be included. Users should claim any pending eligible rewards before the snapshot if they want those tokens included.
The final snapshot block height will be publicly posted.
<h2>Vesting and Claim Window</h2>
Converted Fry 3.0 will vest linearly over 12 months from Fry 3.0 launch.
The claim window will remain open for 12 months.
If a user claims later, claiming later will not restart their vesting schedule. They will receive any already-vested amount available at the time they claim, with the rest continuing on the same shared vesting schedule.
Any unclaimed conversion allocation remaining after the 12-month claim window closes will transfer to the DAO-governed treasury.
<h2>fVPN Presale and Streamflow Issues</h2>
FIP-017 would allow Fry Networks to handle affected fVPN presale users who are still waiting due to Streamflow-related issues through a Fry 3.0 airdrop or claim process.
This process would be handled outside of Streamflow and natively on Algorand.
<h2>Fry 3.0 Presale</h2>
If FIP-017 passes, Fry Networks will proceed with a Fry 3.0 presale before Fry 3.0 rewards begin.
Fry 3.0 rewards will begin only after the presale is complete and the Fry 3.0 launch process is ready.
Until Fry 3.0 rewards begin, Fry Edge Miner devices will earn tFRY, fNODE, and fVPN, all of which are 1:1 convertible to Fry 3.0.
This allows FEM miners to continue earning during the transition period while also allowing Fry Networks to complete the presale, launch the Fry 3.0 ASA, prepare liquidity, and finalize the migration process before direct Fry 3.0 emissions begin.
More presale details will be announced after FIP-017 passes.
<h2>Solana Bridge</h2>
FIP-017 includes a planned Solana-to-Algorand bridge as part of the broader Fry 3.0 roadmap.
The initial Fry 3.0 migration does not require the Solana bridge.
The initial migration will be Algorand-native.
Any future bridge will require separate public technical documentation and security review before public use.
<h2>Security, Transparency, and Community Feedback</h2>
During the discussion period, the community raised important questions about smart contract security, audit planning, bridge safety, liquidity, snapshot transparency, and migration review.
Because of that, FIP-017 includes the following requirements:
<ul>
<li>Fry Networks will publish a public implementation and security review plan before enabling public migration contracts.</li>
<li>The final snapshot block height will be publicly posted.</li>
<li>A public snapshot reference will be posted so the community can verify included wallet balances.</li>
<li>The migration interface will allow users to review their snapshot balances before signing a claim or conversion transaction.</li>
<li>Large or unusual migration cases may be routed through manual review before final processing.</li>
<li>Fry Networks will provide public deployment updates for the Fry 3.0 ASA, migration interface, conversion process, presale, and liquidity deployment.</li>
<li>Any future bridge will require separate public technical documentation and security review before public use.</li>
<li>The initial Fry 3.0 migration does not require a Solana bridge. The initial migration is Algorand-native.</li>
</ul>
<h2>Legacy Token Utility</h2>
If FIP-017 passes, Fry 3.0 becomes the token used by Fry Networks applications going forward.
FRY 2.0, fNODE, tFRY, and fVPN will remain on-chain, but they will no longer be used by Fry Networks applications after the migration.
<h2>What a YES Vote Means</h2>
A YES vote approves FIP-017 and authorizes Fry Networks to proceed with Fry 3.0 under the terms described in this vote, the Fry 3.0 Whitepaper, and the Fry 3.0 Litepaper.
This includes:
<ul>
<li>Creating Fry 3.0</li>
<li>Running the Fry 3.0 presale</li>
<li>Having FEM earn tFRY, fNODE, and fVPN after FIP-017 passes until Fry 3.0 rewards begin</li>
<li>Making tFRY, fNODE, and fVPN 1:1 convertible to Fry 3.0</li>
<li>Allowing FEM miners to effectively build 3× base reward exposure under Fry 3.0 during the transition period</li>
<li>Taking the final migration snapshot after the Fry 3.0 presale ends</li>
<li>Migrating eligible legacy tokens into Fry 3.0</li>
<li>Replacing FRY 2.0, fNODE, tFRY, and fVPN utility with Fry 3.0</li>
<li>Moving Fry Edge Miner rewards directly to Fry 3.0 after the presale and Fry 3.0 launch</li>
<li>Updating Fry Networks apps and systems to use Fry 3.0</li>
<li>Using the snapshot, vesting, claim, and security process described above</li>
</ul>
<h2>What a NO Vote Means</h2>
A NO vote rejects FIP-017.
If FIP-017 does not pass:
<ul>
<li>Fry 3.0 will not launch under this proposal</li>
<li>The Fry 3.0 presale will not proceed under this proposal</li>
<li>The snapshot-based migration will not proceed</li>
<li>FRY 2.0, fNODE, tFRY, and fVPN will remain the current token structure</li>
<li>Fry Networks may return to community discussion with a revised proposal if needed</li>
</ul>
<h2>Vote Options</h2>
✅ YES — Approve FIP-017 and proceed with Fry 3.0
❌ NO — Do not approve FIP-017
<h2>Voting Period</h2>
This vote will remain open for 7 days.
Please review the Fry 3.0 Whitepaper, Litepaper, and the FIP-017 discussion history before voting.

FIP-017: Fry 3.0 Unified Token Migration and Legacy Token Consolidation

Approve FIP-017 and proceed with Fry 3.0

<h1>FIP-016: Fry Edge Miner Consolidation, Automatic FE-Key Conversion, and Revenue-Focused Network Realignment</h1>
<h2>Summary</h2>
FIP-016 proposes consolidating Fry Networks’ proven FryHub-based miner types into one unified miner classification called the Fry Edge Miner.
This proposal is intended to simplify the Fry ecosystem, reduce development overhead, focus emissions and engineering resources on revenue-aligned infrastructure, and create a cleaner path forward for miners, operators, and future integrations.
If passed, the following miner types will be merged into the Fry Edge Miner classification:
<ul>
<li>RDN</li>
<li>SDN</li>
<li>SVN</li>
<li>AEM</li>
<li>Bandwidth Miner / BM</li>
</ul>
The following miner types will be deprecated from future Fry rewards:
<ul>
<li>IDM</li>
<li>IRM</li>
<li>ISM</li>
<li>ODM</li>
<li>OSM</li>
<li>Non-FryHub IoT miners</li>
</ul>
As part of this transition, Fry Networks will convert eligible miner keys and eligible deprecated device/license records into Fry Edge Miner keys.
All Fry Edge Miner keys will begin with the prefix:
FEM-
This means users with merged miner types will not go from multiple miners down to one miner.
For example, if a user has one RDN, one SDN, one SVN, one AEM, and one Bandwidth Miner, that user would go from 5 existing miners to 5 Fry Edge Miner keys, not from 5 miners to 1 miner.
Affected users with deprecated devices or deprecated BYOD licenses will also receive Fry Edge Miner keys through the transition process.
<hr>
<h2>Background</h2>
Fry Networks has grown across many different miner types, device categories, and network segments. While this allowed the ecosystem to experiment broadly, it has also created complexity for development, support, tokenomics, emissions, and community understanding.
The community discussion around FIP-016 made one thing clear:
Fry should focus on what works.
The strongest areas of the network are the parts most aligned with real infrastructure value and revenue potential, including:
<ul>
<li>AI</li>
<li>Storage</li>
<li>Bandwidth</li>
<li>Nodes</li>
<li>Partner integrations</li>
<li>Edge compute infrastructure</li>
</ul>
Continuing to maintain many miner categories that do not create meaningful revenue spreads the project too thin and makes the ecosystem harder to scale.
FIP-016 is designed to simplify Fry Networks while still protecting affected users through automatic key conversion, free transition keys, already-earned tFRY preservation, and continued exploration of third-party opportunities for deprecated networks.
<hr>
<h2>Proposal</h2>
If FIP-016 passes, Fry Networks will create a unified miner classification called the Fry Edge Miner.
The Fry Edge Miner will become the primary FryHub-supported miner classification for edge infrastructure, including AI, storage, bandwidth, node-related workloads, and partner-enabled workloads.
The following miner types will be merged into the Fry Edge Miner classification:
<ul>
<li>RDN</li>
<li>SDN</li>
<li>SVN</li>
<li>AEM</li>
<li>Bandwidth Miner / BM</li>
</ul>
The following miner types will be deprecated from future Fry rewards:
<ul>
<li>IDM</li>
<li>IRM</li>
<li>ISM</li>
<li>ODM</li>
<li>OSM</li>
<li>Non-FryHub IoT miners</li>
</ul>
FIP-016 does not remove existing segment tokens and does not delete already-earned tFRY.
Instead, it consolidates miner classifications, converts eligible keys into Fry Edge Miner keys, preserves already-earned tFRY, and redirects Fry Networks toward infrastructure categories with stronger long-term value.
<hr>
<h2>Key Terms of FIP-016</h2>
<h3>1. Fry Edge Miner Creation</h3>
A new unified miner classification called the Fry Edge Miner will be created.
The Fry Edge Miner will represent the consolidated category for FryHub-supported edge infrastructure, including:
<ul>
<li>AI workloads</li>
<li>Storage workloads</li>
<li>Bandwidth workloads</li>
<li>Node-related workloads</li>
<li>Partner-enabled workloads</li>
<li>Other future FryHub-supported infrastructure services</li>
</ul>
This allows Fry Networks to focus development and emissions around a simpler, stronger, and more scalable miner model.
<hr>
<h3>2. Miner Consolidation</h3>
The following miner types will be merged into the Fry Edge Miner classification:
<ul>
<li>RDN</li>
<li>SDN</li>
<li>SVN</li>
<li>AEM</li>
<li>Bandwidth Miner / BM</li>
</ul>
Instead of continuing to maintain these as separate miner classifications, they will be unified under the Fry Edge Miner model.
This simplifies:
<ul>
<li>Miner software</li>
<li>User onboarding</li>
<li>Reward logic</li>
<li>Tokenomics</li>
<li>Development</li>
<li>Support</li>
<li>Future integrations</li>
</ul>
This consolidation is not intended to reduce the number of miners an existing operator owns.
Merged miners will be converted on a 1:1 basis into Fry Edge Miner keys.
Example:
If a user currently has:
<ul>
<li>1 RDN</li>
<li>1 SDN</li>
<li>1 SVN</li>
<li>1 AEM</li>
<li>1 Bandwidth Miner</li>
</ul>
That user would receive:
<ul>
<li>5 Fry Edge Miner keys</li>
</ul>
The user would not be reduced from 5 miners to 1 miner.
<hr>
<h3>3. Automatic FE-Key Conversion</h3>
If FIP-016 passes, Fry Networks will convert eligible existing miner keys into Fry Edge Miner keys.
All Fry Edge Miner keys will begin with:
FEM-
This key conversion will apply to eligible merged miner types and eligible deprecated miner/device/license records.
For merged miner types, existing eligible miner keys will be converted into Fry Edge Miner keys on a 1:1 basis.
For deprecated miner types, eligible deprecated device records and deprecated BYOD license records will be converted or issued into Fry Edge Miner keys as part of the transition.
The goal is to make the transition automatic and clear for users.
Users should not have to wonder whether they are being reduced from multiple miners to a single miner. Each eligible existing merged miner will become its own Fry Edge Miner key.
<hr>
<h3>4. Deprecated Miner Rewards and tFRY Preservation</h3>
If FIP-016 passes, deprecated miner types will stop earning future rewards once the FIP-016 implementation is complete.
The following miner types will be deprecated from future Fry rewards:
<ul>
<li>IDM</li>
<li>IRM</li>
<li>ISM</li>
<li>ODM</li>
<li>OSM</li>
<li>Non-FryHub IoT miners</li>
</ul>
These miner categories have not created meaningful revenue for the network, and continuing to emit future rewards to them would slow Fry Networks’ ability to focus on infrastructure that can produce long-term value.
However, any tFRY already earned by deprecated miners will remain valid.
Users will still be able to convert already-earned tFRY into the appropriate segment tokens through a vested conversion process.
This vested conversion will take place after:
<ol>
<li>FIP-016 passes, and</li>
<li>Fry Networks completes the required code changes needed to support the FIP-016 transition.</li>
</ol>
This means deprecated miners will not continue earning new rewards going forward, but users will not lose the tFRY they already earned.
<hr>
<h3>5. Free Fry Edge Miner Transition Keys</h3>
To make affected users whole on the Fry side of the transition, Fry Networks will provide Fry Edge Miner keys to eligible affected users.
Each eligible holder of a deprecated miner device will receive:
<ul>
<li>1 Fry Edge Miner key per deprecated device</li>
</ul>
Each eligible holder of a deprecated BYOD license will receive:
<ul>
<li>1 Fry Edge Miner key per deprecated BYOD license</li>
</ul>
Each eligible holder of a merged miner type will receive:
<ul>
<li>1 Fry Edge Miner key per merged miner/device/key</li>
</ul>
This means both merged miner owners and deprecated miner owners receive a direct transition path into the Fry Edge Miner system.
For merged miner types, this is a 1:1 conversion.
For deprecated miner types, this is a transition key replacement so affected users can continue participating in Fry through the new Fry Edge Miner model.
<hr>
<h3>6. VM and VPS Support</h3>
FIP-016 will allow FryHub and Fry Edge Miner software to support VM and VPS usage.
Users with multiple Fry Edge Miner keys may run multiple Fry Edge Miner instances through:
<ul>
<li>Physical machines</li>
<li>Virtual machines</li>
<li>VPS deployments</li>
<li>Other supported deployment environments</li>
</ul>
This is important because users with multiple Fry Edge Miner keys may need to run multiple Fry Edge Miner software instances.
For example, a user with several Fry Edge Miner keys may choose to run those keys across several VM instances, VPS instances, or physical machines.
This allows users with multiple keys to operate multiple Fry Edge Miner instances without needing a separate dedicated physical PC for every key.
This also supports the broader goal of making Fry Edge Miner scalable, flexible, and easier to deploy.
All VM, VPS, and physical deployments must still follow Fry Networks’ validation, anti-abuse, and software rules.
<hr>
<h3>7. No Device Location Cap</h3>
Fry Edge Miners will not have a per-location cap.
Users may run multiple Fry Edge Miners from the same location, as long as the miners follow the network’s software, validation, and anti-abuse rules.
This removes unnecessary deployment friction and allows operators to scale more freely.
<hr>
<h3>8. No Limit on Newly Purchased Fry Edge Miner Keys</h3>
There will be no artificial cap on newly purchased Fry Edge Miner keys.
Early supporters helped build the foundation of the network, and FIP-016 recognizes that contribution through transition keys and OG role perks.
Moving forward, the Fry Edge Miner should remain open and scalable for both existing operators and future participants.
Reward eligibility should be based on valid deployment, useful integrations, and network contribution rather than arbitrary purchase limits.
<hr>
<h3>9. Partner Integrations Are Flexible, Not Mandatory</h3>
Fry Edge Miner rewards may scale based on active integrations.
Not every partner integration must be enabled in order to earn rewards.
A user may still earn with fewer integrations enabled, but their rewards may be lower than a miner with more active integrations.
This creates a flexible model where users are not forced into every integration, while still rewarding miners that provide more value to the network.
<hr>
<h3>10. Segment Tokens Are Preserved</h3>
FIP-016 does not remove or merge existing segment tokens.
All existing Fry segment tokens are preserved, including but not limited to:
<ul>
<li>fNODE</li>
<li>fVPN</li>
<li>Other existing or future segment tokens</li>
</ul>
The purpose of this FIP is miner classification consolidation, not segment token consolidation.
If the community wants to consolidate or modify segment tokens in the future, that should be handled through a separate FIP or cFIP.
<hr>
<h3>11. Early Adopter Recognition</h3>
Affected early adopters will receive recognition for supporting Fry Networks during its earlier mining phases.
As part of the transition, eligible affected users will receive an OG Discord role.
The OG role may include:
<ul>
<li>OG lounge access</li>
<li>Community recognition</li>
<li>Future ecosystem perks</li>
<li>Other benefits determined by Fry Networks over time</li>
</ul>
This gives early supporters additional recognition without creating unfair permanent reward limits against new users.
<hr>
<h3>12. Deprecated Device Utility, Partnerships, and Potential Network Sale</h3>
Deprecating a miner from Fry rewards does not mean the underlying device is useless.
Many deprecated devices may still:
<ul>
<li>Report data</li>
<li>Function through their original manufacturer apps</li>
<li>Serve a non-mining purpose</li>
<li>Be reused in future partner integrations</li>
<li>Be valuable to other DePIN or data-focused projects</li>
</ul>
If FIP-016 passes, Fry Networks may explore multiple paths for deprecated miner networks, including:
<ul>
<li>Third-party DePIN integrations</li>
<li>Partner support for deprecated device categories</li>
<li>Selling deprecated miner network infrastructure, data pipelines, or integration rights to another project</li>
<li>Publishing guidance for continued non-mining use where practical</li>
</ul>
Both third-party support and outright sale of deprecated miner networks may be considered viable paths if they create value for Fry Networks, affected users, or the broader DePIN ecosystem.
The goal is to avoid unnecessary waste and preserve as much utility as possible while still allowing Fry Networks to focus on the parts of the ecosystem with the strongest long-term value.
Even outside of Fry mining, many of these devices can still collect data, report data, or serve useful real-world purposes.
<hr>
<h2>What This FIP Does Not Do</h2>
FIP-016 does not:
<ul>
<li>Remove existing segment tokens</li>
<li>Merge all segment tokens into one token</li>
<li>Delete already-earned tFRY</li>
<li>Reduce merged miner owners from multiple miners to one miner</li>
<li>Require every partner integration to be enabled</li>
<li>Impose a per-location cap on Fry Edge Miners</li>
<li>Limit how many Fry Edge Miner keys users can purchase</li>
<li>Force users to throw away deprecated devices</li>
<li>Prevent Fry Networks from seeking future third-party integrations for deprecated networks</li>
<li>Prevent Fry Networks from exploring sale opportunities for deprecated miner networks</li>
</ul>
<hr>
<h2>Why This Matters</h2>
Fry Networks cannot scale efficiently while trying to maintain too many miner types that do not all contribute meaningful value or revenue to the network.
This proposal allows Fry to:
<ul>
<li>Simplify the ecosystem</li>
<li>Focus on revenue-aligned infrastructure</li>
<li>Reduce development overhead</li>
<li>Improve tokenomics clarity</li>
<li>Preserve already-earned tFRY</li>
<li>Convert eligible miner keys into FE-prefixed Fry Edge Miner keys</li>
<li>Preserve 1:1 miner ownership for merged miner types</li>
<li>Give affected deprecated miner users a free transition path</li>
<li>Support scalable VM and VPS deployments</li>
<li>Keep segment tokens intact</li>
<li>Recognize early adopters</li>
<li>Explore third-party opportunities for deprecated networks</li>
<li>Explore sale opportunities for deprecated miner networks where practical</li>
</ul>
This is a strategic consolidation designed to help Fry Networks focus and grow without unnecessarily reducing existing merged miner operators’ miner counts.
<hr>
<h2>Implementation Plan</h2>
If FIP-016 passes, Fry Networks will:
<ol>
<li>Create the Fry Edge Miner classification.</li>
<li>Require all Fry Edge Miner keys to begin with the prefix FEM-.</li>
<li>Convert eligible existing merged miner keys into Fry Edge Miner keys on a 1:1 basis.</li>
<li>Consolidate RDN, SDN, SVN, AEM, and BM under the Fry Edge Miner model.</li>
<li>Ensure owners of merged miner types receive one Fry Edge Miner key per eligible merged miner/device/key.</li>
<li>Deprecate IDM, IRM, ISM, ODM, OSM, and non-FryHub IoT miners from future Fry rewards.</li>
<li>Stop future rewards for deprecated miner types once implementation is complete.</li>
<li>Preserve already-earned tFRY from deprecated miners.</li>
<li>Build and release the vested tFRY conversion process after the required FIP-016 code changes are completed.</li>
<li>Convert or issue Fry Edge Miner keys for eligible deprecated miner devices and deprecated BYOD licenses.</li>
<li>Provide one Fry Edge Miner key per eligible deprecated device.</li>
<li>Provide one Fry Edge Miner key per eligible deprecated BYOD license.</li>
<li>Enable VM and VPS usage for FryHub and Fry Edge Miner software.</li>
<li>Allow users to run multiple Fry Edge Miner instances through physical machines, VMs, VPS deployments, or other supported environments.</li>
<li>Remove per-location caps for Fry Edge Miners.</li>
<li>Preserve all existing segment tokens.</li>
<li>Create and assign the OG Discord role for eligible affected early adopters.</li>
<li>Explore third-party partnerships, integrations, or sale opportunities for deprecated miner networks where practical.</li>
<li>Publish additional transition guidance as needed during implementation.</li>
</ol>
<hr>
<h2>Voting Options</h2>
<h3>Option A — Approve FIP-016</h3>
Approve the creation of the Fry Edge Miner, consolidate proven FryHub miners, automatically convert eligible miner keys into FE-prefixed Fry Edge Miner keys, preserve 1:1 miner ownership for merged miner types, deprecate non-revenue miner categories from future rewards, preserve already-earned tFRY through vested conversion, provide Fry Edge Miner transition keys to affected deprecated miner users, enable VM/VPS usage, remove device/location caps, preserve segment tokens, recognize early adopters with OG perks, and allow Fry Networks to pursue partnerships or sale opportunities for deprecated miner networks.
<h3>Option B — Reject FIP-016</h3>
Reject the proposal and keep the current miner structure unchanged.
<h3>Option C — Approve Fry Edge Miner Consolidation Only</h3>
Approve the creation of the Fry Edge Miner, automatic FE-prefixed key conversion, 1:1 conversion for merged miner types, VM/VPS support, no per-location cap, no limit on purchased Fry Edge Miner keys, segment token preservation, and OG role perks.
However, this option does not approve the immediate deprecation of IDM, IRM, ISM, ODM, OSM, or non-FryHub IoT miners from future Fry rewards.
If this option wins, Fry Networks would move forward with the Fry Edge Miner consolidation, but deprecated miner handling would require a separate follow-up FIP.
<h3>Option D — Approve Deprecated Miner Transition Only</h3>
Approve the deprecation of IDM, IRM, ISM, ODM, OSM, and non-FryHub IoT miners from future Fry rewards, while preserving already-earned tFRY through vested conversion and providing affected deprecated miner users with Fry Edge Miner transition keys.
However, this option does not approve merging RDN, SDN, SVN, AEM, and BM into one unified Fry Edge Miner classification.
If this option wins, Fry Networks would retire the non-revenue deprecated miner categories and protect affected users through the transition package, but the currently proven FryHub miner types would remain separate miner classifications unless changed by a future FIP.
<hr>
<h2>Closing Statement</h2>
FIP-016 is about focus.
Fry Networks has learned which miner categories are most aligned with real infrastructure value, revenue potential, and long-term scalability.
This proposal consolidates the ecosystem around the Fry Edge Miner while preserving eligible merged miner counts through 1:1 FE-key conversion, giving affected deprecated miner users a free transition path, preserving already-earned tFRY, and keeping open the possibility of future value for deprecated devices through partnerships, integrations, or sale opportunities.
The goal is not to erase the past.
The goal is to build a stronger, simpler, and more sustainable Fry Networks going forward.

FIP-016: Fry Edge Miner Consolidation, Deprecated Miner Transition, and Revenue-Focused Network Realignment

Approve the creation of the Fry Edge Miner, consolidate proven FryHub miners, automatically convert eligible miner keys into FE-prefixed Fry Edge Miner keys, preserve 1:1 miner ownership for merged miner types, deprecate non-revenue miner categories from future rewards, preserve already-earned tFRY through vested conversion, provide Fry Edge Miner transition keys to affected deprecated miner users, enable VM/VPS usage, remove device/location caps, preserve segment tokens, recognize early adopters with OG perks, and allow Fry Networks to pursue partnerships or sale opportunities for deprecated miner networks.

Option A — Approve FIP-016

Reject the proposal and keep the current miner structure unchanged.

Option B — Reject FIP-016

Approve the creation of the Fry Edge Miner, automatic FE-prefixed key conversion, 1:1 conversion for merged miner types, VM/VPS support, no per-location cap, no limit on purchased Fry Edge Miner keys, segment token preservation, and OG role perks.
However, this option does not approve the immediate deprecation of IDM, IRM, ISM, ODM, OSM, or non-FryHub IoT miners from future Fry rewards.
If this option wins, Fry Networks would move forward with the Fry Edge Miner consolidation, but deprecated miner handling would require a separate follow-up FIP.

Option C — Approve Fry Edge Miner Consolidation Only

Approve the deprecation of IDM, IRM, ISM, ODM, OSM, and non-FryHub IoT miners from future Fry rewards, while preserving already-earned tFRY through vested conversion and providing affected deprecated miner users with Fry Edge Miner transition keys.
However, this option does not approve merging RDN, SDN, SVN, AEM, and BM into one unified Fry Edge Miner classification.
If this option wins, Fry Networks would retire the non-revenue deprecated miner categories and protect affected users through the transition package, but the currently proven FryHub miner types would remain separate miner classifications unless changed by a future FIP.

Option D — Approve Deprecated Miner Transition Only

Objective: To determine the rate of reward reduction per additional 1,000 registered miners. This vote seeks to establish whether rewards should decrease by 4% or 7% for each subsequent batch of 1,000 miners beyond our current count. The goal is to ensure sustainable growth and reward distribution as our network expands.
Key Points:
<ul>
<li>Current Situation: With over 8,000 miners currently registered, our network is experiencing rapid growth. This increase in participants necessitates a strategic adjustment in how rewards are distributed to maintain the network&#39;s health and long-term viability.
</li>
<li>Options for Reduction:
<ul>
<li>A 4% reduction in rewards for each additional 1,000 miners registered. This moderate approach aims to gradually adjust reward allocations while supporting sustained participation and growth.</li>
<li>A 7% reduction in rewards for each additional 1,000 miners registered. This more aggressive strategy is intended to quickly stabilize the reward pool as our community expands, ensuring long-term sustainability.</li>
</ul>
</li>
<li>Implementation Details: It&#39;s important to note that once this vote concludes, the chosen reduction rate will not immediately affect the initial 8,000 miners. Instead, the reduction (either 4% or 7%) will be applied and doubled for the next segment of up to 8,000 new miners. This approach allows for a phased integration of the new policy, giving our community time to adjust.
</li>
</ul>
Your Participation Matters:
<ul>
<li>We encourage all community members to participate in this critical decision. Your vote will help shape the future of our reward system, balancing growth with sustainability. Consider the implications of each option and choose the one that aligns with your vision for our network&#39;s future.</li>
</ul>
Note: You may cast your vote as many times as you like, provided you have sufficient FRY tokens to support each vote. This ensures that all stakeholders, especially those deeply invested in our network, have a voice proportional to their commitment.

FIP-002 Vote on Tiered Reduction of Rewards Based on Miner Registration in the Fry Foundation Network

Reduce rewards by 4% per 1000 miners

Reduce rewards by 7% per 1000 miners

Status: Proposed
Author: Fry Networks
Discussion Period: January 11, 2026 – February 11, 2026
Vote Type: Single-choice (Yes / No)
Implementation Type: Segmentation Update
<hr>
<h2>📌 1. Summary</h2>
FIP-014 proposes introducing fAI, a dedicated segmentation token for AI-focused miners.
If approved:
<ul>
<li>fAI will be launched as the official AI segmentation token.</li>
<li>AI Edge Miners (AEMs) and all future AI-class miners will transition from earning fNODE to earning fAI.</li>
<li>AI rewards will reflect AI-specific network demand and utilization.</li>
<li>fNODE will remain focused on general node infrastructure.</li>
</ul>
If rejected:
<ul>
<li>AI Edge Miners will continue earning fNODE.</li>
<li>No changes will be made to the current reward structure.</li>
</ul>
This proposal does not modify the broader token architecture of Fry Networks. Community members may submit a separate cFIP if they wish to explore consolidation or other structural changes.
<hr>
<h2>🔍 2. Motivation</h2>
During the FIP-014 community discussion, several important themes emerged:
<ul>
<li>AI workloads are evolving into a distinct economic category within the ecosystem.</li>
<li>There is value in aligning miner rewards with the specific segment they support.</li>
<li>Clear segmentation may improve long-term economic signaling for AI infrastructure.</li>
<li>Concerns were also raised about token complexity and ecosystem clarity.</li>
</ul>
This proposal focuses specifically on whether AI miners should have a dedicated segmentation token, without altering the rest of the ecosystem structure.
<hr>
<h2>💡 3. Specification</h2>
If Option A passes:
<h3>3.1 Token Launch</h3>
<ul>
<li>fAI will be created as a new segmentation token within the Fry Networks ecosystem.</li>
<li>Tokenomics will follow the standard segment-token model used across the network.</li>
</ul>
<h3>3.2 Reward Transition</h3>
<ul>
<li>AI Edge Miners and future AI-class miners will transition from earning fNODE → fAI.</li>
<li>Previously earned fNODE rewards remain unchanged.</li>
<li>No retroactive adjustments will occur.</li>
</ul>
<h3>3.3 Transition Timeline</h3>
<ul>
<li>A transition date will be announced within 7 days of vote conclusion.</li>
<li>The reward switch will occur no sooner than 14 days after official announcement.</li>
<li>Clear technical guidance will be provided prior to implementation.</li>
</ul>
<h3>3.4 Scope</h3>
This FIP does not:
<ul>
<li>Modify FRY 2.0 governance</li>
<li>Alter other segment tokens</li>
<li>Consolidate or sunset any tokens</li>
<li>Change emission schedules outside AI miners</li>
</ul>
<hr>
<h2>🗳️ 4. Voting Options</h2>
<h3>✅ Option A — Yes, Introduce fAI</h3>
<ul>
<li>Launch fAI.</li>
<li>Transition AI miners from fNODE to fAI.</li>
<li>Align AI rewards directly with AI-specific network demand.</li>
</ul>
<h3>❌ Option B — No, Maintain Current Model</h3>
<ul>
<li>Do not introduce fAI.</li>
<li>AI miners continue earning fNODE.</li>
<li>No changes at this time.</li>
</ul>
<hr>
<h2>⚖️ 5. Governance &amp; Approval Criteria</h2>
<ul>
<li>Voting Type: Single-choice</li>
<li>Passing Threshold: Simple majority (&gt;50%)</li>
<li>Quorum Requirement: Standard Fry governance quorum (if applicable)</li>
</ul>
If quorum is not met, the proposal will be considered invalid and may be reintroduced later.
<hr>
<h2>🧩 6. Risks &amp; Considerations</h2>
As discussed during the community phase:
Potential Benefits:
<ul>
<li>Stronger alignment between AI demand and rewards</li>
<li>Clearer segmentation across network functions</li>
<li>Improved economic signaling for decentralized AI infrastructure</li>
</ul>
Potential Risks:
<ul>
<li>Increased token complexity</li>
<li>Perceived fragmentation within the ecosystem</li>
<li>Need for clear communication during transition</li>
</ul>
These considerations were discussed extensively during the month-long discussion period.
<hr>
<h2>🗓️ 7. Implementation (If Passed)</h2>
If Option A passes:
<ol>
<li>Official fAI contract creation</li>
<li>Public announcement of transition timeline</li>
<li>Dashboard and backend reward update</li>
<li>Transition from fNODE → fAI on designated date</li>
<li>Post-implementation monitoring period</li>
</ol>
If Option B passes:
<ul>
<li>No changes will be made.</li>
<li>AI miners continue under the current reward model.</li>
</ul>
<hr>
<h2>📣 8. Conclusion</h2>
FIP-014 allows the community to formally decide whether AI miners should operate under a dedicated AI segmentation token or remain within the existing fNODE model.
This proposal reflects the feedback gathered during the January–February 2026 discussion period and provides a clear, binary governance decision.

FIP-014: Introduction of fAI as the Dedicated AI Segmentation Token

<ul>
<li>Launch fAI.</li>
<li>Transition AI miners from fNODE to fAI.</li>
<li>Align AI rewards directly with AI-specific network demand.</li>
</ul>

Yes, Introduce fAI

<ul>
<li>Do not introduce fAI.</li>
<li>AI miners continue earning fNODE.</li>
<li>No changes at this time.</li>
</ul>

No, Maintain Current Model

<h2>Overview</h2>
This FIP proposes a change to how registration staking works for monetized miners across Fry Networks.
Registration staking itself is not being voted on in this FIP. Once community-proposed FIPs (cFIPs) are live, any community member who wishes to remove registration staking entirely may propose a separate FIP for community consideration and formal voting.
FIP-013 is limited in scope to determining how the $50 registration peg should behave over time.
<hr>
<h2>Current Registration Staking Model</h2>
<ul>
<li>Registration staking is required for monetized miners</li>
<li>The stake is priced at ~$50 USD at the time of registration</li>
<li>The staked amount is a fixed token quantity</li>
<li>Upon withdrawal:<ul>
<li>If the token price has fallen → the user receives less than $50 USD</li>
<li>If the token price has risen → the user receives more than $50 USD</li>
</ul>
</li>
</ul>
This exposes operators to market risk unrelated to miner performance and has been a recurring source of confusion and concern.
<hr>
<h2>Proposed Change</h2>
FIP-013 proposes adjusting the behavior of the $50 registration peg.
Under a dynamic model:
<ul>
<li>Registration staking behaves like a $50-value position</li>
<li>Upon withdrawal:<ul>
<li>If token price decreases → the user receives more tokens, worth approximately $50 USD</li>
<li>If token price increases → the user receives fewer tokens, worth approximately $50 USD</li>
</ul>
</li>
</ul>
This proposal affects registration staking mechanics only and does not modify:
<ul>
<li>mining reward rates</li>
<li>reward multipliers</li>
<li>miner tiers</li>
<li>verification stakes</li>
<li>node stakes</li>
</ul>
<hr>
<h2>Purpose of Registration Staking</h2>
Registration staking exists to:
<ul>
<li>Protect the network once monetization is active</li>
<li>Ensure consistent and reliable data delivery</li>
<li>Align operators with long-term network health</li>
<li>Prevent low-effort or spam participation</li>
</ul>
This FIP does not remove or weaken these requirements.
<hr>
<h2>Community Discussion Summary</h2>
The community discussion highlighted differing perspectives around risk exposure, fairness, and tokenomics, but consensus that the core question is how the $50 peg should behave — not whether registration staking should exist.
<hr>
<h2>Voting Options</h2>
Option A — Ongoing $50 Registration Peg (Both Directions) Registration staking maintains a ~$50 USD-equivalent value for its full lifecycle, regardless of token price movement.
Option B — Downside Protection Only Registration staking is protected against price drops (cannot withdraw less than ~$50 USD), while retaining upside exposure if the token price increases.
Option C — Keep Current Model (Status Quo) The $50 peg applies only at registration. Registration staking remains a fixed token amount with full price exposure on withdrawal.
<hr>
<h2>Implementation Notes</h2>
(Non-binding; finalized only if this FIP passes)
<ul>
<li>Price reference may use DEX pricing, oracle feeds, or indexed averages</li>
<li>Adjustments should be epoch-based rather than real-time</li>
<li>Smoothing (TWAP / moving averages) and circuit breakers may be applied</li>
</ul>
<hr>
<h2>Voting</h2>
This FIP will proceed to a formal vote. The option with the highest number of votes will be implemented.

FIP-013: Dynamic Registration Staking

Registration staking maintains a ~$50 USD-equivalent value for its full lifecycle, regardless of token price movement.

Option A — Ongoing $50 Registration Peg (Both Directions)

Registration staking is protected against price drops (cannot withdraw less than ~$50 USD), while retaining upside exposure if the token price increases.

Option B — Downside Protection Only

The $50 peg applies only at registration. Registration staking remains a fixed token amount with full price exposure on withdrawal.

Option C — Keep Current Model (Status Quo

<h1>FIP-012: Increasing the Verification Stake for All New Verification Stakes</h1>
<h3>1. Summary</h3>
FIP-012 proposes adjusting the verification stake requirement for all new verification stakes across all miner tiers.
The current cost to obtain 1.5× or 3× verification multipliers is extremely low (around $3 USD equivalent in FRY at current prices). This makes it too easy for bad actors or low-effort participants to access high multipliers with almost no real commitment.
This FIP:
<ul>
<li>Applies only to new verification stakes created after activation.</li>
<li>Leaves all existing verification stakes unchanged.</li>
<li>Clarifies that anyone who unstakes and later restakes will be subject to the new rules, if this FIP passes.</li>
</ul>
The DAO will choose between three “Yes” paths (specific new stake amounts or a follow-up FIP) and three “No” paths (keep current stake and/or prefer alternative mechanisms like performance-based or reduced multipliers).
<hr>
<h3>2. Motivation</h3>
At present, the effective barrier to obtain 3× rewards is roughly $3 USD worth of FRY. This is problematic because:
<ul>
<li>It allows low-effort or speculative setups to farm outsized rewards.</li>
<li>It weakens the signal that “verified” miners are serious, stable participants.</li>
<li>It makes it easier for bad actors to extract value without contributing long-term.</li>
</ul>
The network benefits when:
<ul>
<li>Verification requires real commitment, not just a trivial amount of capital.</li>
<li>Verified participants have stronger alignment with Fry’s long-term growth.</li>
<li>Abuse, churn, and low-quality setups are reduced.</li>
</ul>
By increasing the verification stake for new stakes only, FIP-012 attempts to:
<ul>
<li>Preserve fairness and trust for existing verified users.</li>
<li>Protect the system going forward.</li>
<li>Give the DAO multiple, clearly differentiated paths to address the problem (USD-pegged stake, future configurable stake, or alternative mechanisms).</li>
</ul>
<hr>
<h3>3. Community Feedback Summary</h3>
From the community discussion, several themes emerged:
<ul>
<li>Support for a USD-pegged stake:
Many participants favored pegging verification stakes to a fixed USD value, so that the cost of verification remains meaningful even if FRY’s price drops.
</li>
<li>Interest in tier-based or differentiated values:
Some suggested that different tiers could have different verification costs, with higher tiers paying more.
</li>
<li>Concerns about timing and prioritization:
Some community members felt that infrastructure issues (dashboard stability, shipping follow-through, registration/claiming bugs) should be prioritized before increasing verification stakes.
</li>
<li>Objections to fiat-based logic:
A subset of users argued that FRY’s market price alone should determine cost, and that all staking should remain purely token-denominated (no USD peg).
</li>
<li>Alternative approaches suggested:
Several participants hinted — directly or indirectly — that other mechanisms could help reduce abuse:
<ul>
<li>Performance-based or uptime-based verification criteria</li>
<li>Adjusting multipliers instead of increasing capital requirements</li>
</ul>
</li>
</ul>
This FIP captures those viewpoints with a broader set of voting options, including “No” paths that explicitly point to those alternatives.
<hr>
<h3>4. Proposal</h3>
FIP-012 introduces a framework for raising the barrier for new verification stakes while preserving existing stakes. It defines:
<ol>
<li>Scope</li>
<li>Changes that would occur under “Yes” outcomes</li>
<li>Alternative directions represented by “No” outcomes</li>
</ol>
<h4>4.1 Scope</h4>
If FIP-012 passes under any “Yes” outcome:
<ul>
<li>All existing verification stakes remain exactly as they are.</li>
<li>Only new verification stakes created after activation will follow the new rules.</li>
<li>Any miner who unstakes and then restakes after activation will be required to meet the new stake requirements.</li>
</ul>
<h4>4.2 Changes Under “Yes” Outcomes</h4>
The “Yes” options define different ways to increase verification stake for new stakes. All “Yes” paths share these principles:
<ul>
<li>Goal: Raise the commitment level required to access 1.5× and 3× multipliers.</li>
<li>Mechanism: Use more meaningful stake amounts (e.g., USD-pegged) to prevent $3 exploits.</li>
<li>Impact: Only forward-looking; all existing stakes are grandfathered in.</li>
</ul>
The three “Yes” options differ only in how concretely they set the new stake amounts:
<ol>
<li>Directly set 1.5× and 3× USD-equivalent requirements at specific levels, or</li>
<li>Approve the intent to increase stake but push the exact amounts into a follow-up FIP.</li>
</ol>
<h4>4.3 Alternatives Represented by “No” Outcomes</h4>
The “No” options are not just “do nothing” duplicates; they each represent a different philosophy for how to address (or not address) the abuse problem:
<ul>
<li>Keep the current system entirely (status quo).</li>
<li>Explore performance-based verification as a future path instead of higher stake.</li>
<li>Explore reduced multipliers as a future path instead of higher stake.</li>
</ul>
This lets the DAO clearly express why it rejects this FIP, not just that it rejects it.
<hr>
<h3>5. Technical Considerations</h3>
If a “Yes” option with explicit USD amounts passes:
<ul>
<li>For new verification stakes:
<ul>
<li>The system will calculate the FRY equivalent of the required USD amount at the time of staking.</li>
<li>Once staked, the FRY amount is fixed for that user’s verification; it does not float with price.</li>
</ul>
</li>
</ul>
If the “Yes — future FIP for amounts” option passes:
<ul>
<li>No immediate staking amount change is applied.
</li>
<li>A new FIP will be drafted to define:
<ul>
<li>Exact USD and/or FRY amounts for 1.5× and 3×, and/or</li>
<li>Whether tiers are differentiated.</li>
</ul>
</li>
</ul>
If a “No” option passes:
<ul>
<li>No verification stake changes take effect from this FIP.
</li>
<li>Depending on which “No” wins, future FIPs may be drafted to:
<ul>
<li>Implement performance-based verification logic, or</li>
<li>Adjust multipliers instead of stake levels.</li>
</ul>
</li>
</ul>
Under all options:
<ul>
<li>Reward logic, tier structure, and lock periods remain unchanged unless modified by a different FIP.</li>
<li>Existing verification stakes remain as-is unless voluntarily unstaked.</li>
</ul>
<hr>
<h3>6. Implementation Timeline (for Yes outcomes)</h3>
If one of the “Yes” options wins:
<ol>
<li>Specification &amp; coding
<ul>
<li>Implement logic to enforce new verification stake rules for new stakes only.</li>
</ul>
</li>
<li>Internal testing &amp; review
<ul>
<li>Confirm correct conversion of USD amounts (where applicable) into FRY at stake time.</li>
</ul>
</li>
<li>Activation announcement
<ul>
<li>Announce the exact date/time when new verification stake rules go live.</li>
</ul>
</li>
<li>Activation
<ul>
<li>After activation, any new verification stake must follow the new requirements.</li>
<li>Existing stakes remain unchanged as long as they are not unstaked.</li>
</ul>
</li>
</ol>
If the “Yes — future FIP for amounts” option wins, the immediate action is:
<ul>
<li>Draft and publish the follow-up FIP defining specific stake amounts, then go to vote.</li>
</ul>
<hr>
<h3>7. Voting Options</h3>
The DAO will vote for one of the following six options:
<hr>
<h4>✅ Option 1 — Yes (1.5×: $75, 3×: $50)</h4>
<ul>
<li>Set the verification stake for new stakes as:
<ul>
<li>1.5× multiplier: $75 USD equivalent in FRY</li>
<li>3× multiplier: $50 USD equivalent in FRY</li>
</ul>
</li>
<li>All existing verification stakes remain unchanged unless unstaked.
</li>
<li>Any new verification stake created after activation must meet these USD-equivalent FRY amounts at the time of staking.
</li>
</ul>
<hr>
<h4>✅ Option 2 — Yes (1.5×: $50, 3×: $25)</h4>
<ul>
<li>Set the verification stake for new stakes as:
<ul>
<li>1.5× multiplier: $50 USD equivalent in FRY</li>
<li>3× multiplier: $25 USD equivalent in FRY</li>
</ul>
</li>
<li>All existing verification stakes remain unchanged unless unstaked.
</li>
<li>Any new verification stake created after activation must meet these USD-equivalent FRY amounts at the time of staking.
</li>
</ul>
<hr>
<h4>✅ Option 3 — Yes, but determine exact amounts in a future FIP</h4>
<ul>
<li>Approve the intent to increase verification stake for new verification stakes.
</li>
<li>No specific amounts are set by this FIP.
</li>
<li>A follow-up FIP will define:
<ul>
<li>Exact stake amounts for 1.5× and 3×, and</li>
<li>Whether those amounts are FRY-only, USD-pegged, or tier-dependent.</li>
</ul>
</li>
</ul>
Until that follow-up FIP passes and is activated, the current verification stake requirements stay in place.
<hr>
<h4>❌ Option 4 — No (Keep current verification stake and structure)</h4>
<ul>
<li>Reject any change to verification stake requirements.</li>
<li>Keep the current stake amounts and multiplier structure exactly as they are today.</li>
<li>No new mechanism or follow-up is mandated by this outcome.</li>
</ul>
<hr>
<h4>❌ Option 5 — No (Explore performance-based verification instead of higher stake)</h4>
<ul>
<li>Reject this FIP’s approach of raising verification stake.
</li>
<li>Express a preference to keep the current stake requirements and instead explore a future FIP that:
<ul>
<li>Ties 1.5× / 3× eligibility to performance metrics such as:
<ul>
<li>Uptime</li>
<li>Data quality</li>
<li>Minimum operating history</li>
<li>Proofs of proper operation (e.g., successful connections / jobs / reporting)</li>
</ul>
</li>
</ul>
</li>
<li>This option does not implement performance-based rules immediately, but it signals that any future changes should focus on performance, not capital.
</li>
</ul>
<hr>
<h4>❌ Option 6 — No (Explore reducing multipliers instead of higher stake)</h4>
<ul>
<li>Reject this FIP’s approach of increasing verification stake.
</li>
<li>Express a preference to keep current stake levels but consider a future FIP that:
<ul>
<li>Lowers verification multipliers to reduce the incentive for low-effort setups.</li>
<li>Example: lowering 1.5× to 1.25× and 3× to 2×, or adding progressive/ramping multipliers over time.</li>
</ul>
</li>
<li>This pathway aims to reduce abuse by reducing reward intensity, rather than by raising the cost of entry.
</li>
</ul>
<hr>
<h3>8. Conclusion</h3>
FIP-012 addresses a clear problem: verification has become nearly free in fiat terms, making it easy for low-effort participants and bad actors to access high multipliers with minimal commitment.
This proposal gives the DAO a balanced set of choices:
<ul>
<li>Three “Yes” paths that meaningfully increase verification stake now or through a follow-up FIP.</li>
<li>Three “No” paths that either keep the status quo or explicitly favor alternative solutions (performance-based or multiplier reduction).</li>
</ul>
Whatever option wins, the outcome will clearly express how the DAO wants to balance:
<ul>
<li>Abuse prevention</li>
<li>Capital requirements</li>
<li>Fairness to existing stakers</li>
<li>And the long-term integrity of the Fry Networks ecosystem.</li>
</ul>

FIP-012: Increasing the Verification Stake for All New Verification Stakes

<ul>
<li>Set the verification stake for new stakes as:
<ul>
<li>1.5× multiplier: $75 USD equivalent in FRY</li>
<li>3× multiplier: $50 USD equivalent in FRY</li>
</ul>
</li>
<li>All existing verification stakes remain unchanged unless unstaked.
</li>
<li>Any new verification stake created after activation must meet these USD-equivalent FRY amounts at the time of staking.
</li>
</ul>

✅ Yes (1.5×: $75, 3×: $50)

<ul>
<li>Set the verification stake for new stakes as:
<ul>
<li>1.5× multiplier: $50 USD equivalent in FRY</li>
<li>3× multiplier: $25 USD equivalent in FRY</li>
</ul>
</li>
<li>All existing verification stakes remain unchanged unless unstaked.
</li>
<li>Any new verification stake created after activation must meet these USD-equivalent FRY amounts at the time of staking.
</li>
</ul>

✅ Yes (1.5×: $50, 3×: $25)

<ul>
<li>Approve the intent to increase verification stake for new verification stakes.
</li>
<li>No specific amounts are set by this FIP.
</li>
<li>A follow-up FIP will define:
<ul>
<li>Exact stake amounts for 1.5× and 3×, and</li>
<li>Whether those amounts are FRY-only, USD-pegged, or tier-dependent.</li>
</ul>
</li>
</ul>
Until that follow-up FIP passes and is activated, the current verification stake requirements stay in place.

✅ Yes, but determine exact amounts in a future FIP

<ul>
<li>Reject any change to verification stake requirements.</li>
<li>Keep the current stake amounts and multiplier structure exactly as they are today.</li>
<li>No new mechanism or follow-up is mandated by this outcome.</li>
</ul>

❌ No (Keep current verification stake and structure)

<ul>
<li>Reject this FIP’s approach of raising verification stake.
</li>
<li>Express a preference to keep the current stake requirements and instead explore a future FIP that:
<ul>
<li>Ties 1.5× / 3× eligibility to performance metrics such as:
<ul>
<li>Uptime</li>
<li>Data quality</li>
<li>Minimum operating history</li>
<li>Proofs of proper operation (e.g., successful connections / jobs / reporting)</li>
</ul>
</li>
</ul>
</li>
<li>This option does not implement performance-based rules immediately, but it signals that any future changes should focus on performance, not capital.
</li>
</ul>

❌ No (Explore performance-based verification instead of higher stake)

<ul>
<li>Reject this FIP’s approach of increasing verification stake.
</li>
<li>Express a preference to keep current stake levels but consider a future FIP that:
<ul>
<li>Lowers verification multipliers to reduce the incentive for low-effort setups.</li>
<li>Example: lowering 1.5× to 1.25× and 3× to 2×, or adding progressive/ramping multipliers over time.</li>
</ul>
</li>
<li>This pathway aims to reduce abuse by reducing reward intensity, rather than by raising the cost of entry.
</li>
</ul>

❌ No (Explore reducing multipliers instead of higher stake)

<h2>Summary</h2>
This proposal would extend the AI Edge Miner Boost through June 1st, 2026, maintaining the current multiplier structure to reward early adopters, strengthen the network, and onboard more Key Opinion Leaders (KOLs) to promote the AI Edge Miner.
<h2>Background</h2>
The AI Edge Miner was launched with a temporary reward boost to incentivize early adoption, firmware testing, and decentralized AI infrastructure growth. This boost helped bootstrap the segment and grow the network during its initial expansion phase.
Since launch, the community has continued deploying AI Edge Miners, and interest has steadily increased. To maintain momentum and encourage further participation, the community discussion for this FIP unanimously supported an extension of the boost period.
<h2>Proposal</h2>
FIP-011 proposes the following:
<ul>
<li>Extend the AI Edge Miner Boost until June 1st, 2026</li>
<li>Keep the current boost multiplier unchanged</li>
<li>No additional staking or burn requirement is introduced as part of this extension</li>
</ul>
This extension will:
<ul>
<li>Keep the network attractive to new adopters</li>
<li>Attract more KOLs and content creators to promote AI Edge Miners</li>
<li>Reinforce our position as a leader in decentralized AI infrastructure</li>
</ul>
<h2>Voting Options</h2>
🟩 YES — Extend the Boost until June 1st, 2026
<ul>
<li>Keeps the existing boost multiplier active through June 1st, 2026</li>
<li>Supports network growth, outreach, and adoption</li>
</ul>
🟥 NO — Let the Boost Expire on Its Current End Date
<ul>
<li>The AI Edge Miner Boost ends on December 31st. 2025 CST</li>
<li>No extension or changes to current reward multipliers</li>
</ul>
<h2>Voting Period</h2>
Voting for FIP-011 is now live and will remain open for 1 month.

FIP-011: Extend AI Edge Miner Boost Until June 1st, 2026

<ul>
<li>Keeps the existing boost multiplier active through June 1st, 2026</li>
<li>Supports network growth, outreach, and adoption</li>
</ul>

🟩 YES — Extend the Boost until June 1st, 2026

<ul>
<li>The AI Edge Miner Boost ends on December 31st. 2025 CST</li>
<li>No extension or changes to current reward multipliers</li>
</ul>

🟥 NO — Let the Boost Expire on Its Current End Date

Status: Voting
Author: Governance (submitted by @IotaNine)
Discussion Window: July 29 – August 29, 2025
Voting Window: September 2, 2025 – October 2, 2025 (CDT)
<hr>
<h2>1) Summary</h2>
This FIP proposes to:
<ol>
<li>Enable conversion of FRY 1.0 earned/claimed after the December 1, 2024 snapshot into tFRY at a 40:1 ratio (non-vested); and</li>
<li>Retire FRY 1.0 from the ecosystem immediately, halting its use in rewards and verification staking.</li>
</ol>
<hr>
<h2>2) Motivation</h2>
<ul>
<li>Provide a fair, simple path for miners who continued earning after the snapshot cutoff.</li>
<li>Eliminate confusion by fully standardizing around Fry 2.0 + segment tokens, with tFRY serving as the bridge.</li>
<li>Strengthen Fry 2.0 alignment by shifting all verification staking to FRY 2.0.</li>
</ul>
<hr>
<h2>3) Specification</h2>
<h3>A. Conversion of Post-Snapshot FRY 1.0</h3>
<ul>
<li>Eligibility: All FRY 1.0 mined or claimed after Dec 1, 2024.
</li>
<li>Conversion rate: 40 FRY 1.0 → 1 tFRY.
</li>
<li>Vesting: No vesting period. Because tFRY cannot be bought/sold through official Fry-operated pools, there is no risk of price shocks.
</li>
<li>tFRY properties:
<ul>
<li>Transferable wallet-to-wallet.</li>
<li>No official LPs/AMMs.</li>
<li>Redeemable 1:1 into segment tokens (e.g., fVPN, fWX, fNODE) when each segment is monetized.</li>
</ul>
</li>
</ul>
<h3>B. Rewards</h3>
<ul>
<li>FRY 1.0 rewards halt immediately once this FIP passes.</li>
<li>tFRY becomes the reward token for all unmonetized networks going forward.</li>
</ul>
<h3>C. Verification Staking</h3>
<ul>
<li>Staking token changes from FRY 1.0 to FRY 2.0 for unmonetized miners.</li>
<li>No cutoff time for unstaking FRY 1.0 positions, but users must re-stake in FRY 2.0 to continue earning verified rewards.</li>
<li>BYOD vs. hardware staking rules (BYOD = half) remain unchanged. Only the staking token changes.</li>
</ul>
<hr>
<h2>4) Transitional Rules</h2>
<ul>
<li>Conversion tool will go live sometime after FIP approval.</li>
<li>FRY 1.0 reward emissions end instantly upon passage of this vote.</li>
<li>Unstaking window: Open-ended. Operators can unstake FRY 1.0 anytime, but must re-stake in FRY 2.0 to maintain verified multipliers.</li>
</ul>
<hr>
<h2>5) Ecosystem Impact</h2>
<ul>
<li>Fairness: Includes all miners who contributed post-snapshot.</li>
<li>Clarity: Retires an outdated token (FRY 1.0) and removes ecosystem confusion.</li>
<li>Alignment: Consolidates staking demand into FRY 2.0, reinforcing the DAO token’s utility.</li>
<li>Liquidity safety: With no official LPs for tFRY, there is no risk of sudden price disruption.</li>
</ul>
<hr>
<h2>6) FAQs</h2>
<ul>
<li>Is tFRY transferable? Yes, wallet-to-wallet. Fry Networks does not operate official pools/AMMs.</li>
<li>What happens to my pre-snapshot FRY 1.0? Those remain under their original conversion rules (unchanged).</li>
<li>What if I don’t re-stake? You will still earn base rewards (tFRY), but not verified rewards until you re-stake in FRY 2.0.</li>
<li>Do BYOD vs. hardware rules change? No. Only the stake token changes.</li>
</ul>
<hr>
<h2>7) Voting Options</h2>
<ul>
<li>✅ YES — Allow 40:1 conversion of post-snapshot FRY 1.0 into tFRY (non-vested), retire FRY 1.0 immediately from rewards, and move verification staking to FRY 2.0.</li>
<li>❌ NO — Keep FRY 1.0 active in rewards/staking and do not add conversion eligibility for post-snapshot FRY 1.0.</li>
</ul>

FIP-010: Convert Post-Snapshot FRY 1.0 to tFRY (40:1) & Retire FRY 1.0 From Rewards

Allow 40:1 conversion of post-snapshot FRY 1.0 into tFRY (non-vested), retire FRY 1.0 immediately from rewards, and move verification staking to FRY 2.0.

✅ YES

Keep FRY 1.0 active in rewards/staking and do not add conversion eligibility for post-snapshot FRY 1.0.

❌ NO

<h1>Fry Improvement Proposal (FIP-009): Weekly Epoch Rewards</h1>
<h2>Summary</h2>
This proposal aims to shift from a daily reward distribution system to a weekly epoch-based rewards system. Rewards will accumulate weekly and be distributed every Friday (&quot;Fryday&quot;).
<h2>Motivation</h2>
The current daily reward system results in frequent, small distributions, complicating accounting, increasing transaction overhead, and leading to operational inefficiencies. By moving to weekly epochs, the community will benefit from simplified management, reduced network congestion, and more predictable rewards scheduling.
<h2>Proposed Changes</h2>
<ul>
<li>Replace the current daily reward distribution model with a weekly epoch model.</li>
<li>Each epoch begins Friday at 00:00 UTC and ends the following Thursday at 23:59 UTC.</li>
<li>Rewards accumulated during the epoch will be automatically distributed the following Friday (&quot;Fryday&quot;).</li>
<li>Rewards will remain claimable indefinitely with no expiration.</li>
</ul>
<h2>Implementation</h2>
<ul>
<li>Implementation will take place only after the successful completion and rollout of PoC4All.</li>
<li>This change is straightforward and quick (approximately one day), but thorough testing involving both developers and moderators will occur prior to deployment.</li>
<li>Development resources for dVPN and node software remain unaffected, as they are managed by Octaloop.</li>
</ul>
<h2>Benefits</h2>
<ul>
<li>Operational Efficiency: Simplifies administrative and accounting tasks.</li>
<li>Reduced Network Congestion: Fewer transactions each week enhance network performance.</li>
<li>User Convenience: Users only need to claim rewards weekly, streamlining their experience.</li>
<li>Token Emission Management: Helps manage emissions by reducing constant selling pressure, although weekly sell-off impacts must be monitored.</li>
<li>Encourages Consistent Miner Uptime: Promotes sustained network participation throughout each epoch.</li>
</ul>
<h2>Community Concerns &amp; Responses</h2>
<ul>
<li>Sell-Off Risk: Potential concentrated weekly sell-off identified. To mitigate this, ongoing monitoring and analysis of similar projects (DIMO, Hivemapper) will be conducted, and alternative reward distribution days or staggered releases may be considered if necessary.</li>
<li>Claim Timing Clarification: Rewards are claimable immediately after distribution on Fridays, with no waiting period or expiration.</li>
<li>Operational Priorities: This proposal will be implemented only after completing essential operational deliverables such as PoC4All and FIP-008, addressing community concerns regarding current operational stability and credibility.</li>
</ul>
<h2>Voting Options</h2>
<ul>
<li>Option 1 (Yes): Implement weekly epoch-based rewards as described.</li>
<li>Option 2 (No): Maintain current daily rewards distribution.</li>
<li>Option 3 (Alternative Day): Implement weekly epochs but distribute rewards on another weekday (e.g., Monday) to reduce potential sell-off impact.</li>
<li>Option 4 (Bi-weekly Trial): Conduct a bi-weekly epoch rewards trial for three months, then reassess based on community feedback.</li>
</ul>
<h2>Next Steps</h2>
Following community discussion, this proposal is now ready for official voting. The community is encouraged to vote and participate actively in shaping this critical aspect of Fry Networks.

FIP-009: Weekly Epoch Rewards

Implement weekly epoch-based rewards as described.

Maintain current daily rewards distribution.

Implement weekly epochs but distribute rewards on another weekday (e.g., Monday) to reduce potential sell-off impact.

Alternative Day

Conduct a bi-weekly epoch rewards trial for three months, then reassess based on community feedback.

Bi-weekly Trial

This Fry Improvement Proposal (FIP-008) formally introduces daily tFRY rewards alongside existing FRY 1.0 rewards for miners operating on unmonetized networks. Additionally, the community will vote on potentially transitioning unmonetized miners to earn only tFRY, immediately stopping FRY 1.0 emissions.
This ensures mining rewards retain clear, long-term value, aligning rewards directly with real-world monetization.
FRY 2.0 DAO Voting:
Voting occurs by staking FRY 2.0 tokens (1 FRY 2.0 token = 1 vote). Tokens used for voting are locked for exactly 6 months from the conclusion date of the FIP they were staked in. After the lock period, users can unstake and immediately regain access to their full staked amount (no additional vesting).
<hr>
<h2>Why Vote for FRY 1.0 + tFRY or tFRY-only?</h2>
Currently, FRY 1.0 earned after Dec 1, 2024, lacks a guaranteed conversion to segment tokens. tFRY ensures future convertibility, preserving your mining rewards’ value. Voting for FRY 1.0 + tFRY or tFRY-only secures long-term miner profitability and stability.
<hr>
<h2>Understanding Monetized vs. Unmonetized Networks</h2>
<ul>
<li>Monetized Network: Has paying customers; miners earn segment tokens directly (e.g., fVPN, fWX).
</li>
<li>Unmonetized Network: No paying customers yet; miners currently earn FRY 1.0, but this proposal offers:
<ul>
<li>FRY 1.0 + tFRY, or</li>
<li>Only tFRY.</li>
</ul>
</li>
</ul>
Important: Monetization occurs at the miner-type level (e.g., all weather miners monetize simultaneously once data is purchased).
<hr>
<h2>How tFRY Rewards Work</h2>
<h3>Convertibility:</h3>
<ul>
<li>tFRY converts 1:1 into corresponding segment tokens upon miner-type monetization.</li>
<li>No cross-token conversions (e.g., weather tFRY → fWX only).</li>
</ul>
<h3>6-Month Vesting Schedule:</h3>
<ul>
<li>Converted tokens vest evenly each month over 6 months (~16.67% monthly).</li>
<li>Immediate conversion possible upon monetization.</li>
</ul>
Why Vesting?
Vesting prevents sudden token sell-offs (&quot;price shocks&quot;), promoting stable markets.
<h3>Why Introduce tFRY?</h3>
<ul>
<li>FRY 1.0 earned after Dec 1, 2024, cannot currently convert into segment tokens. tFRY guarantees future convertibility.</li>
</ul>
<hr>
<h2>Daily tFRY Rewards by Miner Tier</h2>
Note: These tier definitions differ from Fry 1.0 tiers and are updated in the upcoming Fry 2.0 whitepaper.
<ul>
<li>Tier X: 1225.64 tFRY/day</li>
<li>Tier S: 119.04 tFRY/day</li>
<li>Tier 1: 59.52 tFRY/day</li>
<li>Tier 2: 29.76 tFRY/day</li>
<li>Tier 3: 29.76 tFRY/day</li>
<li>Tier 4: 22.86 tFRY/day</li>
</ul>
<h3>Optional FRY 2.0 Verification Stake Multipliers</h3>
<ul>
<li>1.5x or 3x multipliers via optional FRY 2.0 staking.</li>
<li>Multipliers activate immediately upon staking confirmation, starting next reward cycle.</li>
<li>Verification staking is optional; basic rewards do not require staking.</li>
</ul>
<hr>
<h2>Optional FRY 2.0 Verification Staking Amounts</h2>
Note: These tier definitions differ from Fry 1.0 tiers.
Each miner requires an individual verification stake.
<ul>
<li>Tier S - Nodes:
<ul>
<li>2,235 FRY (24-hour lock) or 745 FRY (6-month lock)</li>
</ul>
</li>
<li>Tier 1 - High-End Weather/Water Miners:
<ul>
<li>1,118 FRY (24-hour lock) or 373 FRY (6-month lock)</li>
</ul>
</li>
<li>Tier 4 - Indoor Satellite Miners:
<ul>
<li>447 FRY (24-hour lock) or 149 FRY (6-month lock)</li>
</ul>
</li>
<li>Tier 2-3 - All Other Miners:
<ul>
<li>559 FRY (24-hour lock) or 186 FRY (6-month lock)</li>
</ul>
</li>
<li>BYOD Miners:
<ul>
<li>Half the amounts listed above, depending on miner tier.</li>
</ul>
</li>
</ul>
<hr>
<h2>Registration Stake Clarification</h2>
<ul>
<li>Registration stake for converting tFRY to segment tokens required only after monetization.</li>
<li>No registration stake required prior to monetization.</li>
</ul>
<hr>
<h2>Conversion DApp Timeline and Details</h2>
<ul>
<li>Dedicated Conversion DApp launches soon.</li>
<li>Users can immediately convert FRY 1.0 earned on or before Dec 1, 2024, directly to FRY 2.0 or segment tokens, subject to a 6-month vesting schedule.</li>
<li>Important: FRY 1.0 earned after Dec 1, 2024, remains tradable but is not convertible into segment tokens via our conversion DApp.</li>
<li>tFRY conversion available only after miner-type monetization.</li>
</ul>
<h3>Estimated Monetization Timelines:</h3>
<ul>
<li>Bandwidth Miners: Targeting monetization by end of Q2, 2025.</li>
<li>Weather &amp; Air Quality Miners: Targeting monetization by end of 2025 (discussions ongoing with interested AI agent).</li>
<li>Other Miner Types: No exact timeline yet; actively working to establish timelines soon.</li>
</ul>
<hr>
<h2>Community Voting Options</h2>
<ul>
<li>✅ Option 1: FRY 1.0 + tFRY (Recommended: guarantees reward stability and future convertibility.)</li>
<li>✅ Option 2: Only tFRY rewards (Recommended: immediately protects reward value.)</li>
<li>❌ Option 3: Maintain current FRY 1.0-only (Not recommended: no guaranteed convertibility after Dec 1, 2024.)</li>
<li>❌ Option 4 (New): Pause tFRY implementation until Conversion DApp launches
(Not recommended: delays reward convertibility indefinitely, prolonging uncertainty.)</li>
</ul>
Options 1 and 2 provide clear future-proof benefits and are strongly recommended.
<hr>
<h2>Frequently Asked Questions (FAQ)</h2>
Q: Do tFRY rewards expire?
A: No, tFRY accumulates indefinitely until monetization.
Q: If Option 2 (only tFRY) passes, can I trade previously earned FRY 1.0?
A: Yes. FRY 1.0 earned on or before Dec 1, 2024, remains tradable and convertible (once DApp launches), subject to vesting.
Q: Do multiple miners require separate verification stakes?
A: Yes, each miner requires its own verification stake for multipliers.
Q: When do verification multipliers activate?
A: Immediately upon staking confirmation, effective from next reward cycle.
Q: Is FRY 1.0 conversion also vested?
A: Yes, FRY 1.0 conversions follow the 6-month vesting schedule.
Q: Does voting lock FRY 2.0 tokens permanently?
A: No, voting locks FRY 2.0 tokens exactly 6 months from the FIP conclusion date. Afterward, users immediately regain full token access (no vesting).
Q: Is monetization per miner or miner-type?
A: Monetization occurs at the miner-type level, affecting all miners simultaneously.
<hr>
<h2>Reward Tracking Simplified</h2>
<ul>
<li>Miner rewards easily tracked via the Fry Networks dashboard.</li>
</ul>
<hr>
<h2>Goals of FIP-008</h2>
<ul>
<li>Guarantees reward convertibility and protection.</li>
<li>Provides optional multipliers without mandatory costs.</li>
<li>Establishes stable, sustainable rewards aligned with real-world monetization.</li>
</ul>
<hr>
Your vote is crucial. Voting for FRY 1.0 + tFRY or tFRY-only secures the future value and sustainability of your mining efforts.
Thank you for your ongoing support and commitment to Fry Networks!

FIP-008: Introducing tFRY Rewards for Unmonetized Miners

Miners on unmonetized networks continue earning FRY 1.0 rewards while gaining additional tFRY rewards. tFRY guarantees future 1:1 convertibility into segment tokens upon miner-type monetization, protecting your miner rewards&#39; long-term value and stability.

 Continue FRY 1.0 and Add tFRY Rewards

All unmonetized miners immediately switch from FRY 1.0 to earning only tFRY. This ensures all rewards earned have guaranteed future convertibility into monetized segment tokens (1:1 upon monetization). Immediately stabilizes rewards and protects against FRY 1.0 uncertainties.

Fully Switch to tFRY Rewards Only

Rejects tFRY rewards entirely. Miners on unmonetized networks continue earning FRY 1.0 only, which remains tradable but lacks guaranteed future convertibility into segment tokens after Dec 1, 2024. This could result in uncertainty and potential long-term reward devaluation.

Keep Current System: FRY 1.0 Only

Delays implementing tFRY rewards until the Conversion DApp launches, leaving unmonetized miners earning only FRY 1.0 in the meantime. Rewards remain non-convertible for an indefinite period until the Dapp launches, prolonging uncertainty about reward value and convertibility timelines.

Pause tFRY Rewards Until Conversion DApp Launch

Objective: To determine the specific amount of FRY tokens required to stake for verifying different types of miners in the Fry Networks verification staking system, as well as the lock periods and reward multipliers.
Key Points:
<ul>
<li>Staking System Details:
<ul>
<li>The staking system requires users to stake a specified amount of FRY tokens for each miner they want to verify.</li>
<li>This ensures a commitment to the network and helps maintain the integrity of the token.</li>
<li>While FIP-006 initially proposed staking amounts equivalent to a value in USD, after much discussion, it was decided that it would be best to change the staking amounts to pure FRY.</li>
</ul>
</li>
<li>Why Pure FRY is Better than a Fixed USD Price:
<ol>
<li>Incentive to Verify Early: Staking in pure FRY encourages users to verify their miners earlier, as the value of FRY may change over time.</li>
<li>Incentive to Keep the FRY Staked: By staking in FRY, users are more likely to maintain their stake, benefiting from potential increases in the value of FRY.</li>
<li>Consistency for All Users: The same amount of FRY will be required regardless of when you stake, ensuring fairness and consistency across the network.</li>
</ol>
</li>
</ul>
Proposed Staking Options, and Rewards Multipliers:
<ol>
<li>Option 1: 
<ul>
<li>Verification multipliers: x1.5 / x3</li>
<li>Staking Amounts:<ul>
<li>Tier S - Nodes: 100,000 FRY / 50,000 FRY</li>
<li>Tier 1 - High-End Weather/Water: 50,000 FRY / 25,000 FRY</li>
<li>Tier 4 - Indoor Satellite: 20,000 FRY / 10,000 FRY</li>
<li>Tier 2-3 - All Others: 25,000 FRY / 12,500 FRY</li>
<li>BYOD: Half</li>
</ul>
</li>
<li>Lock Period: The higher staking amounts for each tier equal the 24-hour minimum lock and half of the full verification rewards, while the lower staking amounts equal the full verification rewards with a 6-month minimum lock.</li>
</ul>
</li>
<li>Option 2: 
<ul>
<li>Verification multipliers: x2 / x3</li>
<li>Staking Amounts:<ul>
<li>Tier S - Nodes: 80,000 FRY / 40,000 FRY</li>
<li>Tier 1 - High-End Weather/Water: 40,000 FRY / 20,000 FRY</li>
<li>Tier 4 - Indoor Satellite: 16,000 FRY / 8,000 FRY</li>
<li>Tier 2-3 - All Others: 20,000 FRY / 10,000 FRY</li>
<li>BYOD: Half</li>
</ul>
</li>
<li>Lock Period: The higher staking amounts for each tier equal the minimum 1-month lock and 66% of the full verified rewards, while the lower staking amounts equal the full verification rewards with a 1-year minimum lock.</li>
</ul>
</li>
</ol>
Impact of Staking Amounts, Lock Periods, and Multipliers:
<ul>
<li>The chosen staking amount, lock period, and reward multiplier will directly affect the level of commitment required from miners and influence the overall tokenomics of Fry Networks.</li>
</ul>
Additional Requirements:
<ul>
<li>Users will need to provide the location of their miner in the verification portal.</li>
<li>Users can unstake their tokens only at the end of each lock period. However, if they unstake, they will not receive verified rewards. They can easily restake if they want to start receiving verified rewards again.</li>
</ul>
Your Participation Matters:
Voting on this proposal allows you to directly influence the staking requirements, lock periods, and reward multipliers for miner verification in Fry Networks. Your choice will help determine the optimal strategy to ensure both commitment and sustainability within our network.
Voting Details:
<ul>
<li>Deadline: Please cast your vote by 8/21/2024 at midnight CDT. This is the final opportunity to make your voice heard in this important decision.</li>
<li>How to Vote:<ol>
<li>Visit <a href="https://vote.frynetworks.com/">https://vote.frynetworks.com/</a></li>
<li>Link your Algorand wallet.</li>
<li>Navigate to the vote section and cast your vote for FIP-007.</li>
<li>You can vote multiple times, provided you have sufficient FRY tokens for each vote.</li>
</ol>
</li>
</ul>
Your participation is crucial. By voting, you are helping shape the future of our staking verification program and the overall strategy of Fry Networks.
Thank you for your continued support and involvement.
Best regards,
Samuel Fry Founder, CEO, and CTO Fry Networks

FIP-007 Vote on Determining the Staking Amount, Lock Period, and Reward Multipliers for Miner Verification in Fry Networks

<ul>
<li>Verification multipliers: x1.5 / x3</li>
<li>Staking Amounts:<ul>
<li>Tier S - Nodes: 100,000 FRY / 50,000 FRY</li>
<li>Tier 1 - High-End Weather/Water: 50,000 FRY / 25,000 FRY</li>
<li>Tier 4 - Indoor Satellite: 20,000 FRY / 10,000 FRY</li>
<li>Tier 2-3 - All Others: 25,000 FRY / 12,500 FRY</li>
<li>BYOD: Half</li>
</ul>
</li>
<li>Lock Period: The higher staking amounts for each tier equal the 24-hour minimum lock and half of the full verification rewards, while the lower staking amounts equal the full verification rewards with a 6-month minimum lock.</li>
</ul>

Option 1

<ul>
<li>Verification multipliers: x2 / x3</li>
<li>Staking Amounts:<ul>
<li>Tier S - Nodes: 80,000 FRY / 40,000 FRY</li>
<li>Tier 1 - High-End Weather/Water: 40,000 FRY / 20,000 FRY</li>
<li>Tier 4 - Indoor Satellite: 16,000 FRY / 8,000 FRY</li>
<li>Tier 2-3 - All Others: 20,000 FRY / 10,000 FRY</li>
<li>BYOD: Half</li>
</ul>
</li>
<li>Lock Period: The higher staking amounts for each tier equal the minimum 1-month lock and 66% of the full verified rewards, while the lower staking amounts equal the full verification rewards with a 1-year minimum lock.</li>
</ul>

Option 2

FIP-006 Vote on Choosing Between Tiered Verification and Staking to Verify Miners in Fry Networks
Objective: To decide whether Fry Networks should adopt a tiered verification system as proposed in FIP-005 or implement a staking system for miner verification.
Key Points:
Options for Miner Verification:
<ul>
<li>Tiered Verification System (from FIP-005):<ul>
<li>Tier 1: Free Verification<ul>
<li>No FRY tokens need to be burned to verify miners.</li>
<li>The reward multiplier for this tier will be determined by a later FIP.</li>
</ul>
</li>
<li>Tier 2: Paid Verification<ul>
<li>Requires burning FRY tokens equivalent to a specified amount in USD to reach this tier.</li>
<li>The reward multiplier for this tier will be determined by a later FIP.</li>
</ul>
</li>
</ul>
</li>
<li>Staking System:<ul>
<li>Requires staking FRY tokens for each miner they want to verify.</li>
<li>The amount of FRY tokens required to stake for verification will be determined by FIP-007.</li>
<li>Users can unstake their tokens whenever they want. However, if they unstake, they will not receive verified rewards. They can easily restake if they want to start receiving verified rewards again.</li>
<li>Includes a 24-hour lock to prevent gaming the system.</li>
</ul>
</li>
</ul>
Additional Requirements for Both Systems:
<ul>
<li>Users will need to provide the location of their miner in the verification portal for both the tiered and staking systems.</li>
</ul>
Future Determinations:
<ul>
<li>Burn/Staking Amounts: The exact USD amount of FRY tokens required to burn for the tiered system or stake for the staking system will be determined in FIP-007.</li>
</ul>
Your Participation Matters:
Voting on this proposal allows you to directly influence the verification and reward structure of Fry Networks. Your choice will help determine whether we implement the tiered system or the staking system, ensuring the best approach for our network&#39;s sustainability and growth.
Voting Details:
<ul>
<li>Deadline: Please cast your vote by August 1st at midnight CDT. This is the final opportunity to make your voice heard in this important decision.</li>
<li>How to Vote:<ol>
<li>Visit <a href="https://vote.frynetworks.com/">https://vote.frynetworks.com/</a></li>
<li>Link your Algorand wallet.</li>
<li>Navigate to the vote section and cast your vote for FIP-006.</li>
<li>You can vote multiple times, provided you have sufficient FRY tokens for each vote.</li>
</ol>
</li>
</ul>
Your participation is crucial. By voting, you are helping shape the future of our miner verification program and the overall strategy of Fry Networks.
Thank you for your continued support and involvement.
Best regards,
Samuel Fry
Founder, CEO, and CTO
Fry Networks

FIP-006 Vote on Choosing Between Tiered Verification and Staking to Verify Miners in Fry Networks

Tiered System

Staking System

Objective: To determine whether Fry Networks should implement a tiered miner verification program. The proposed system includes two tiers: a free tier and a paid tier, with differing requirements and rewards.
Key Points:
<ul>
<li>Proposed Tiers:
<ul>
<li>Tier 1: Free Verification<ul>
<li>No FRY tokens need to be burned to verify miners.</li>
<li>Miners in this tier will receive standard reward multipliers.</li>
</ul>
</li>
<li>Tier 2: Paid Verification<ul>
<li>Requires burning FRY tokens equivalent to a specified amount in USD to reach this tier.</li>
<li>Miners in this tier will receive a higher reward multiplier compared to Tier 1.</li>
</ul>
</li>
</ul>
</li>
<li>Application to All Miners:
<ul>
<li>This tiered verification program applies to all miners and nodes, both new and old.</li>
</ul>
</li>
<li>Future Determinations:
<ul>
<li>Burn Amount for Tier 2: The exact USD amount of FRY tokens required to burn for Tier 2 will be determined in FIP-007.</li>
<li>Reward Multipliers: The reward multipliers for Tier 1 and Tier 2 will be determined in FIP-006.</li>
</ul>
</li>
</ul>
Impact of Each Tier:
<ul>
<li>Free Tier: Allows for broad participation without the need to burn FRY tokens, encouraging inclusivity and ease of entry for new miners.</li>
<li>Paid Tier: Incentivizes higher commitment by offering greater rewards for those willing to burn FRY tokens, thus reducing the overall supply of tokens and potentially increasing their value.</li>
</ul>
Your Participation Matters:
<ul>
<li>Voting on this proposal allows you to directly influence the verification and reward structure of Fry Networks. Your choice will help determine how we balance accessibility with incentivization, ensuring both inclusivity and sustainability.</li>
</ul>
Voting Details:
<ul>
<li>Deadline: Please cast your vote by August 1st at midnight CDT. This is the final opportunity to make your voice heard in this important decision.</li>
<li>How to Vote:<ol>
<li>Visit <a href="https://vote.frynetworks.com/">https://vote.frynetworks.com/</a></li>
<li>Link your Algorand wallet.</li>
<li>Navigate to the vote section and cast your vote for FIP-005.</li>
<li>You can vote multiple times, provided you have sufficient FRY tokens for each vote.</li>
</ol>
</li>
</ul>
Your participation is crucial. By voting, you are helping shape the future of our miner verification program and the overall strategy of Fry Networks.
Thank you for your continued support and involvement.
Best regards,
Samuel Fry
Founder, CEO, and CTO
Fry Networks

FIP-005 Vote on Implementing a Tiered Miner Verification Program in Fry Networks

Objective: To decide the quantity of FRY tokens to be reduced each quarter to assist in managing the token supply and maintaining the tokenomics of the Fry Foundation Network. Community members will vote between two proposed reduction amounts: 12,499,902.375 FRY or 6,249,951.1875 FRY per quarter.
Key Points:
<ul>
<li>Purpose of Token Reduction: Regularly scheduled token reductions aim to decrease the circulating supply of FRY tokens. This can help to manage inflation, increase the scarcity of the token, and potentially enhance its value over time. The community&#39;s decision on the reduction amount will directly impact the network&#39;s economic health and growth.
</li>
<li>Proposed Reduction Amounts:
<ul>
<li>Option 1: Reduce the supply by 12,499,902.375 FRY each quarter.</li>
<li>Option 2: Reduce the supply by 6,249,951.1875 FRY each quarter.</li>
</ul>
</li>
<li>Impact of Each Option:
<ul>
<li>Reducing 12,499,902.375 FRY: This more substantial reduction aims to quickly decrease the supply of FRY tokens, which may have a more immediate impact on scarcity and potentially value, but also carries the risk of greater market volatility.</li>
<li>Reducing 6,249,951.1875 FRY: This more moderate reduction aims to steadily decrease the supply without creating sudden market impacts, balancing supply reduction with market stability.</li>
</ul>
</li>
</ul>
Your Participation Matters:
<ul>
<li>Voting on this proposal allows you to directly influence the economic policy of the Fry Foundation Network. Your choice will help determine the pace at which we reduce the FRY token supply and manage the network&#39;s long-term health and sustainability.</li>
</ul>
Voting Details:
<ul>
<li>Deadline: Please cast your vote by June 20th at midnight CST. This is the final opportunity to make your voice heard in this crucial decision.</li>
<li>You can vote multiple times, provided you have sufficient FRY tokens for each vote.</li>
</ul>
Your participation is crucial. By voting, you are helping shape the future economic strategy of the Fry Foundation Network, ensuring we take a balanced and sustainable approach to token management.
Thank you for your continued support and involvement.

FIP-004 Vote on Scheduled Quarterly Reduction of FRY Tokens in the Fry Foundation Network

Reduce the supply by 12,499,902.375 FRY each quarter

Reduce the supply by 6,249,951.1875 FRY each quarter

Objective: To determine if the early bird multiplier, initially set to expire on October 28th, 2024, should be made a permanent feature of our tokenomics. This decision will influence our strategy for incentivizing early participation and managing reward distribution as our network grows.
<ul>
<li>Reasoning for Making Permanent: The existing reward reduction mechanism, which adjusts with every additional 1000 registered miners, effectively sets a new early bird multiplier just before each reduction. By making this feature permanent, we normalize the benefit for all early participants, ensuring they are rewarded before each incremental threshold.</li>
</ul>
Proposal to Make Permanent: Proposing to make the early bird multiplier a permanent feature aims to continuously attract and reward new miners, crucial for sustaining growth and robust participation.
Your Participation Matters:
<ul>
<li>This vote is pivotal in determining how we balance incentivization with economic health in our network. We encourage all community members to actively participate, considering the long-term implications of your choices on the network’s success.</li>
</ul>
Note: Community members can cast multiple votes, provided they have enough FRY tokens for each vote. This structure allows those more invested in our network to have a significant influence on its governance decisions.

FIP-003 Vote on Making the Early Bird Multiplier Permanent in the Fry Foundation Network

Make the Early Bird Multiplier Permanent

Have the Early Bird Multiplier expire on October 28th, 2024; as originally planned

Objective: To decide on the future of the multiplier function within our tokenomics structure. This function currently doubles the daily rewards when the price is below 1¢ and increases them by 1.5x for each additional zero added to the left of the price. We&#39;re bringing this to a community vote to align our tokenomics with long-term sustainability and market adaptability.
Key Points:
<ul>
<li>Current Multiplier Function: As it stands, our tokenomics include a feature where daily rewards double if the token price falls below 1¢, with further increases of 1.5x for each additional zero added to the left of the price. This has been designed to incentivize participation and mining efforts during low-price periods.
</li>
<li>Rationale for Removal: The consideration to remove this function stems from an analysis of its long-term impact on the project&#39;s economy and sustainability. By potentially removing this function, we aim to create a more predictable and stable token economy that can sustainably support growth and participation without over-reliance on artificial inflationary measures.
</li>
<li>Exclusion of Early Bird Multiplier: It&#39;s important to note that this vote will not affect the current 1.5x early bird multiplier, which is set to conclude on October 28th. The early bird multiplier remains unaffected and will continue as previously announced.
</li>
</ul>
Your Participation Matters:
<ul>
<li>We encourage all community members to participate in this important vote. Your input is crucial as we make decisions that impact the future direction and health of our project. Please consider the long-term implications of your choice and how it aligns with our collective goal of sustainable growth and stability.</li>
</ul>
Note:
You can vote as many times as you would like; granted you have enough FRY to make each vote

FIP-001 Vote to Maintain or Remove the Reward Multiplier Tokenomics in the Fry Foundation Network

Keep the multiplier function as it is.