From fe3fbbb05bead2426beea8b7900c63e9029fb5d4 Mon Sep 17 00:00:00 2001
From: thetrimdj <thetrimdj@gmail.com>
Date: Sun, 22 Jun 2025 10:07:37 -0700
Subject: [PATCH 01/16] Update discord-roles.mdx

Added note re: roles in Epoch 3.

DarkSamho is quoting that roles are available for the epoch when there are not which is causing some confusion.
---
 community/discord-roles.mdx | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/community/discord-roles.mdx b/community/discord-roles.mdx
index e48330a..9ad9a62 100644
--- a/community/discord-roles.mdx
+++ b/community/discord-roles.mdx
@@ -17,6 +17,8 @@ In Inference.net, you can earn different Discord roles based on how many points
 
 Once you meet the point requirement for a specific role, Inference.net will automatically assign that role to you on Discord—provided your Discord account is linked.
 
+(Please note that there will not be role assignments for Epoch 3 due to the shortened duration of the testing schedule)
+
 ---
 
 ## Steps to Get Your Role

From 31b8999f8ae9b9a93fb9022a4f38665d513d31e8 Mon Sep 17 00:00:00 2001
From: Sean <sean@kuzco.xyz>
Date: Tue, 8 Jul 2025 18:13:29 -0700
Subject: [PATCH 02/16] Update docs

---
 devnet-epoch-3/delegator-guide.mdx  | 59 ++++++++++++++++-----
 devnet-epoch-3/operator-guide.mdx   | 80 +++++++++++++++++++----------
 devnet-epoch-3/overview.mdx         | 15 ++++--
 devnet-epoch-3/staking-protocol.mdx | 44 +++++++++++++---
 4 files changed, 148 insertions(+), 50 deletions(-)

diff --git a/devnet-epoch-3/delegator-guide.mdx b/devnet-epoch-3/delegator-guide.mdx
index b62af55..5b3d27d 100644
--- a/devnet-epoch-3/delegator-guide.mdx
+++ b/devnet-epoch-3/delegator-guide.mdx
@@ -17,8 +17,9 @@ When you delegate tokens to an operator pool:
 
 1. Your tokens help increase the operator's priority for receiving inference jobs
 2. You earn a proportional share of the pool's token rewards
-3. The operator takes a commission fee from rewards before distribution
-4. Your tokens remain yours - operators cannot access delegated tokens
+3. You earn a proportional share of the pool's USDC revenue (if operator enables revenue sharing)
+4. The operator takes commission fees from both rewards and USDC before distribution
+5. Your tokens remain yours - operators cannot access delegated tokens
 
 <Note>
   Delegated tokens are not at risk of slashing. Only operator stakes can be
@@ -59,7 +60,8 @@ Navigate to the **Operators** page to view all available pools. Key metrics to c
 
 **Economic Terms:**
 
-- **Commission Rate**: Percentage of rewards kept by operator
+- **Commission Rate**: Percentage of token rewards kept by operator
+- **USDC Commission Rate**: Percentage of USDC revenue kept by operator
 - **Delegation Allowed**: Whether the pool accepts external stake
 - **Auto Stake Fees**: If commission is automatically compounded
 
@@ -67,8 +69,8 @@ Navigate to the **Operators** page to view all available pools. Key metrics to c
 
 Consider these factors when choosing an operator:
 
-1. **Stake Ratio**: Operators must maintain ≥10% of total pool stake
-2. **Commission Rate**: Lower rates mean higher delegator rewards
+1. **Stake Ratio**: Operators must maintain their minimum stake amount
+2. **Commission Rates**: Lower rates mean higher delegator rewards (check both token and USDC rates)
 3. **Track Record**: View historical performance in the operator details
 4. **Hardware**: GPUs with higher VRAM typically process more jobs
 5. **Communication**: Active operators often have websites or community presence
@@ -106,11 +108,13 @@ View your delegations in two places:
 - Shows all pools where you have active stake
 - Displays your stake amount and current value
 - Shows pending unstaking amounts
+- Displays accrued USDC earnings
 
 **Individual Pool Pages:**
 
 - Your specific stake in that pool
-- Accumulated rewards
+- Accumulated token rewards
+- Accumulated USDC earnings
 - Share percentage of the pool
 
 ## Managing Delegations
@@ -142,12 +146,25 @@ Unstaking requires a cooldown period:
 
 ### Claiming Rewards
 
-Rewards are distributed automatically during the unstaking process. When you unstake and withdraw:
+Token rewards are distributed automatically during the unstaking process. When you unstake and withdraw:
 
 - Your original stake is returned
-- Accumulated rewards are included
+- Accumulated token rewards are included
 - No separate claim transaction is needed
 
+### Withdrawing USDC Earnings
+
+USDC earnings can be withdrawn at any time without affecting your stake:
+
+1. Navigate to the operator pool or your portfolio
+2. Click **Withdraw USDC**
+3. Confirm the transaction to receive your accrued USDC
+
+<Note>
+  USDC withdrawals do not affect your stake or future earning potential. You can
+  withdraw USDC as often as you like.
+</Note>
+
 ## Choosing Operators Wisely
 
 ### Green Flags
@@ -160,8 +177,8 @@ Rewards are distributed automatically during the unstaking process. When you uns
 
 ### Red Flags
 
-- ❌ Operator stake near minimum (exactly 10%)
-- ❌ Very high commission rates (>50%)
+- ❌ Operator stake near minimum (exactly at minimum threshold)
+- ❌ Very high commission rates (>50% for tokens or USDC)
 - ❌ Pool marked as "Halted"
 - ❌ No website or contact information
 - ❌ Frequent configuration changes
@@ -173,7 +190,8 @@ While delegation is generally safe, consider:
 1. **Opportunity Cost**: Tokens are locked during staking and cooldown
 2. **Variable Returns**: Rewards depend on operator performance
 3. **Commission Changes**: Operators can adjust rates (effective next epoch)
-4. **Pool Closure**: Operators may close pools, stopping rewards for all delegators
+4. **Pool Closure**: Operators may close pools, stopping rewards and USDC earnings
+5. **USDC Revenue Variability**: USDC earnings depend on inference job volume
 
 <Note>
   Remember: $INT-DEV tokens are testnet tokens with no monetary value. They
@@ -187,5 +205,22 @@ While delegation is generally safe, consider:
 1. **Diversify**: Spread stake across multiple high-performing operators
 2. **Monitor Performance**: Regularly check operator metrics and adjust
 3. **Consider Pool Size**: Smaller pools may offer growth potential
-4. **Watch Commission**: Lower isn't always better - consider operator quality
+4. **Watch Commissions**: Compare both token and USDC commission rates
 5. **Stay Informed**: Follow operator updates and network announcements
+6. **Withdraw USDC Regularly**: Claim your USDC earnings periodically
+
+## Frequently Asked Questions
+
+**Q: How do I earn USDC as a delegator?**<br/>
+A: When operators process inference jobs, they earn USDC. If they've enabled USDC revenue sharing (by setting a commission rate less than 100%), you'll earn a proportional share based on your stake in the pool.
+
+**Q: When can I withdraw my USDC earnings?**<br/>
+A: You can withdraw accrued USDC at any time without affecting your stake or unstaking your tokens.
+
+**Q: Do all operators share USDC revenue?**<br/>
+A: No. Operators can choose their USDC commission rate. A 100% rate means no sharing, while lower rates mean more USDC for delegators.
+
+**Q: How are USDC earnings calculated?**<br/>
+A: Your share of USDC equals: (Your stake / Total pool stake) × USDC revenue × (1 - USDC commission rate)
+
+For additional support, join our [Discord](https://discord.gg/kuzco) community.
diff --git a/devnet-epoch-3/operator-guide.mdx b/devnet-epoch-3/operator-guide.mdx
index 2ecc033..6abcb95 100644
--- a/devnet-epoch-3/operator-guide.mdx
+++ b/devnet-epoch-3/operator-guide.mdx
@@ -17,10 +17,12 @@ Before setting up your operator pool:
 
 1. Ensure you have a funded Solana wallet with:
    - Some SOL for transaction fees
-   - $INT-DEV tokens from the airdrop or faucet
+   - $INT-DEV tokens for the registration fee and initial stake
 2. Link your Solana wallet to your Inference.net account
 3. Have your GPU node running and connected to the network
 
+<Note>Each wallet can create only one operator pool.</Note>
+
 ## Creating Your Operator Pool
 
 An operator pool is your on-chain identity that manages stake, receives job allocations, and distributes rewards.
@@ -48,17 +50,19 @@ An operator pool is your on-chain identity that manages stake, receives job allo
 
 1. Navigate to **Dashboard → Staking → Overview**
 2. Click **Create Operator Pool**
-3. Follow the steps to create your operator pool.
+3. Review the registration fee requirement (paid in $INT-DEV tokens)
+4. Follow the steps to create your operator pool:
 
    **Economic Settings:**
 
-   - **Commission Rate**: Percentage of rewards you keep (0-100%)
+   - **Token Commission Rate**: Percentage of token rewards you keep (0-100%)
+   - **USDC Commission Rate**: Percentage of USDC revenue you keep (0-100%)
    - **Allow Delegation**: Whether to accept stake from other token holders
    - **Auto Stake Fees**: Automatically compound commission into your stake
 
    **Payout Settings:**
 
-   - **USDC Payout Wallet**: Where to receive USDC revenue from inference jobs
+   - **USDC Payout Wallet**: Where to receive USDC commission and your share of revenue
 
    **Profile Information:**
 
@@ -66,26 +70,28 @@ An operator pool is your on-chain identity that manages stake, receives job allo
    - **Website URL**: Optional link to your website
    - **Description**: Brief description of your operation
 
-4. Review your settings and click **Create Pool**
-5. Approve the transaction in your wallet
+5. Review your settings and the registration fee
+6. Click **Create Pool** and approve the transaction in your wallet
 
 <Warning>
-  Pool creation requires a small amount of SOL for transaction fees. Ensure your
-  wallet has sufficient SOL balance.
+  Pool creation requires: - A registration fee in $INT-DEV tokens
+  (non-refundable) - Sufficient SOL for transaction fees - This wallet has not
+  created a pool before
 </Warning>
 
 ### Step 3: Stake Your Pool
 
-As an operator, you must maintain at least 10% of your pool's total stake. This ensures alignment between your performance and delegator rewards.
+Operators must stake a minimum amount (set globally by the protocol) before their pool can accept delegations. This ensures proper economic alignment.
 
 1. On your pool overview page, click **Stake**
-2. Enter the amount of $INT-DEV to stake
+2. Enter at least the minimum required amount of $INT-DEV
 3. Review the transaction and click **Confirm Stake**
 4. Approve the transaction in your wallet
 
 <Info>
-  The more you stake, the higher your priority for receiving inference jobs.
-  Your effective stake per GPU is normalized by VRAM capacity.
+  Until you meet the minimum stake requirement, your pool cannot accept
+  delegations from other users. The more you stake beyond the minimum, the
+  higher your priority for receiving inference jobs.
 </Info>
 
 ## Managing Your Pool
@@ -95,9 +101,10 @@ As an operator, you must maintain at least 10% of your pool's total stake. This
 Your operator dashboard displays key metrics:
 
 - **Total Pool Stake**: Combined operator and delegator stake
-- **Operator Stake**: Your personal stake (must remain ≥10% of total)
-- **Commission Earned**: Accumulated fees from rewards
-- **USDC Revenue**: Earnings from completed inference jobs
+- **Operator Stake**: Your personal stake (must remain above minimum)
+- **Token Commission Earned**: Accumulated fees from token rewards
+- **USDC Commission Earned**: Accumulated fees from USDC revenue
+- **USDC Revenue Share**: Your proportional share of USDC revenue
 - **Total Delegators**: Number of external stakers
 
 ### Adjusting Settings
@@ -106,19 +113,31 @@ You can modify certain pool parameters after creation:
 
 1. Navigate to **Dashboard → Staking → Settings**
 2. Update available settings:
-   - Commission rate (changes apply next epoch)
+   - Token commission rate (changes apply next epoch when rewards are claimed for your pool)
+   - USDC commission rate (changes apply next epoch when rewards are claimed for your pool)
    - Allow/disallow delegations
    - Auto-stake preferences
    - Profile information
    - USDC payout destination
 
+<Note>
+  Setting USDC commission below 100% enables revenue sharing with delegators,
+  which can attract more stake to your pool.
+</Note>
+
 ### Withdrawing Rewards
 
-**Commission Fees:**
+**Commission Fees (Token & USDC):**
 
-- If auto-stake is disabled, commission accumulates separately
-- Click **Withdraw Commission** to claim accumulated fees
-- Specify a destination wallet or use your connected wallet
+- Both token and USDC commissions accrue on-chain
+- Click **Withdraw Token Commission** or **Withdraw USDC Commission**
+- Commissions are sent to your designated wallets
+
+**USDC Revenue Share:**
+
+- As an operator, you also earn a proportional share of USDC revenue
+- This is separate from your commission and based on your stake in the pool
+- Click **Withdraw USDC Earnings** to claim your revenue share
 
 **Unstaking Process:**
 
@@ -142,10 +161,11 @@ You can modify certain pool parameters after creation:
 
 ## Best Practices
 
-1. **Maintain Adequate Stake**: Keep your operator stake well above the 10% minimum to accommodate delegator growth
-2. **Set Competitive Commission**: Balance earning potential with attractiveness to delegators
-3. **Monitor Hardware**: Ensure your GPUs maintain high uptime for better reputation scores
-4. **Engage Delegators**: Provide clear communication about your operation and performance
+1. **Meet Minimum Requirements**: Ensure you maintain stake above the global minimum to keep accepting delegations
+2. **Set Competitive Commissions**: Balance earning potential with attractiveness to delegators for both token and USDC rates
+3. **Consider Revenue Sharing**: Lower USDC commission rates can attract more delegators
+4. **Monitor Hardware**: Ensure your GPUs maintain high uptime for better reputation scores
+5. **Engage Delegators**: Provide clear communication about your operation and performance
 
 ## Troubleshooting
 
@@ -157,9 +177,17 @@ You can modify certain pool parameters after creation:
 
 **Cannot Create Pool:**
 
-- Verify wallet has sufficient SOL for fees
+- Verify wallet has sufficient $INT-DEV for registration fee
+- Ensure wallet has sufficient SOL for transaction fees
+- Check that this wallet hasn't already created a pool
 - Ensure wallet is properly linked to your account
-- Check that pool creation is currently enabled
+- Verify pool creation is currently enabled
+
+**Cannot Accept Delegations:**
+
+- Ensure you've staked at least the minimum required amount
+- Check that delegations are enabled in your pool settings
+- Verify your pool is not halted
 
 **Stake Transaction Fails:**
 
diff --git a/devnet-epoch-3/overview.mdx b/devnet-epoch-3/overview.mdx
index e010662..54b78e8 100644
--- a/devnet-epoch-3/overview.mdx
+++ b/devnet-epoch-3/overview.mdx
@@ -130,11 +130,12 @@ The Inference.net staking protocol is implemented as a Solana program using the
 
 Each operator can create a staking pool with the following configurable parameters:
 
-- **Commission Rate**: Percentage of epoch rewards retained by the operator (0-100%)
+- **Reward Commission Rate**: Percentage of epoch rewards retained by the operator (0-100%)
+- **USDC Commission Rate**: Percentage of USDC revenue retained by the operator (0-100%)
 - **Delegation Status**: Whether to accept external delegations
-- **Minimum Self-Stake**: Currently set globally at 10% of total pool stake
+- **Minimum Self-Stake**: Operators must maintain a globally-set minimum stake amount
 
-Operators must maintain the minimum self-stake ratio to ensure alignment between pool performance and operator incentives. If delegations cause the self-stake ratio to fall below 10%, the operator must add additional stake.
+Operators must maintain the minimum stake amount to ensure alignment between pool performance and operator incentives. Pool creation requires a one-time registration fee and each wallet can create at most one operator pool.
 
 ### Delegation Mechanics
 
@@ -169,8 +170,14 @@ During Epoch 3, operators will interact with two distinct reward mechanisms:
 - Distributed for testing purposes via airdrop and reward distributions
 - Based on stake-weighted job completion
 - Required for staking to receive job allocations
+- Used for pool creation registration fees
 
-This dual approach allows us to test the on-chain protocol's economic mechanisms while maintaining flexibility in reward distribution during the development phase.
+### USDC Revenue Sharing
+
+- Operators earn USDC for processing inference jobs
+- Operators can share USDC revenue with delegators by setting a USDC commission rate
+- Delegators receive proportional USDC earnings based on their stake
+- USDC accrues on-chain and can be withdrawn without affecting stake
 
 <Warning>
   The Inference.net Staking Protocol is being tested on Solana Devnet with test
diff --git a/devnet-epoch-3/staking-protocol.mdx b/devnet-epoch-3/staking-protocol.mdx
index df99c48..75915af 100644
--- a/devnet-epoch-3/staking-protocol.mdx
+++ b/devnet-epoch-3/staking-protocol.mdx
@@ -31,8 +31,9 @@ Operator pools are the fundamental unit of the staking system. Each GPU operator
 - Tracks performance metrics and reward distribution
 - Sets economic parameters like commission rates
 - Receives stake-weighted job allocations
+- Manages USDC revenue sharing with delegators
 
-Operators must maintain a specific minimum stake of their pool's total stake to ensure network economic security.
+Operators must maintain a specific minimum stake amount to ensure network economic security. Each wallet can create at most one operator pool.
 
 ### Staking Records
 
@@ -161,9 +162,17 @@ Operators set commission rates (0-100%) that determine their share of epoch rewa
 
 In addition to token rewards, operators earn USDC from processing inference jobs:
 
-- USDC payments go directly to the operator's designated payout wallet
-- This revenue stream is separate from token rewards
-- Delegators do not receive a share of USDC revenue
+- Operators can set a USDC commission rate (0-100%) separate from token reward commission
+- USDC revenue is shared proportionally among all pool participants based on their stake
+- Shared USDC accrues on-chain when rewards are distributed to the pool
+- Delegators earn their proportional share of USDC revenue after operator commission
+- All USDC earnings (operator commission and staked share) can be withdrawn at any time without affecting stake
+
+<Note>
+  USDC revenue sharing allows delegators to participate in the network's revenue
+  stream, not just token rewards. This creates stronger economic alignment
+  between operators and delegators.
+</Note>
 
 ## Staking and Unstaking Mechanics
 
@@ -188,7 +197,17 @@ In addition to token rewards, operators earn USDC from processing inference jobs
 
 ### Pool Closure
 
-Operators may close a pool at their discretion. Pool closure is a permanent action and cannot be undone. If a pool has been closed, any remaining stake or commission fees can still be withdrawn.
+Operators may close a pool at their discretion. Pool closure is a permanent action and cannot be undone. If a pool has been closed, any remaining stake, commission fees, and accrued USDC can still be withdrawn.
+
+### Pool Creation Requirements
+
+Creating an operator pool requires:
+
+- **Registration Fee**: A one-time fee paid in $INT-DEV tokens to prevent spam and bad actor activity
+- **Minimum Stake**: Operators must stake a minimum amount before delegations are accepted
+- **Unique Wallet**: Each wallet can create at most one operator pool
+
+The registration fee and minimum stake requirements are set globally by the protocol authorities.
 
 ## Security Features
 
@@ -264,13 +283,13 @@ A: Yes. Cancelling an unstake operation will immediately re-stake the tokens and
 A: Commission rate changes take effect in the epoch following when the change occurred, once all reward claims for that pool have been completed.
 
 **Q: What's the difference between token rewards and USDC revenue?**<br/>
-A: Token rewards ($INT) are distributed to all pools by the protocol and shared between operators and delegators. USDC revenue is paid directly to the operators for completed inference tasks.
+A: Token rewards ($INT) are distributed to all pools by the protocol and shared between operators and delegators based on token commission rate. USDC revenue is earned by operators for completed inference tasks and can be shared with delegators based on USDC commission rate. Both types of earnings are distributed proportionally to stake, after their respective commission rates.
 
 **Q: Can operators change minimum stake requirements?**<br/>
-A: No. The operator minimum stake requirement is set globally and applies to all operator pools.
+A: No. The operator minimum stake amount is set globally and applies to all operator pools.
 
 **Q: What if an operator falls below the minimum stake threshold?**<br/>
-A: They can't reduce stake further and the pool can't accept new delegations until the ratio is restored.
+A: They can't reduce stake further and the pool can't accept new delegations until the minimum stake amount is restored.
 
 **Q: Are there fees for staking/unstaking?**<br/>
 A: No. The protocol does not charge fees for any transactions. Only standard Solana transaction fees apply.
@@ -287,4 +306,13 @@ A: Operator are halted for suspected network violations. Halting prevents specif
 **Q: How does slashing work?**<br/>
 A: Authorities can permanently remove operator tokens for serious violations. Only operator stake is at risk, delegator tokens are protected from slashing.
 
+**Q: How do USDC withdrawals work?**<br/>
+A: USDC earnings accrue on-chain when rewards are distributed. Both operators and delegators can withdraw their accrued USDC at any time without affecting their stake or earning potential.
+
+**Q: Can I create multiple operator pools?**<br/>
+A: No. Each wallet can create at most one operator pool to ensure fair participation and prevent gaming of the system.
+
+**Q: What happens to the registration fee?**<br/>
+A: The registration fee is paid to the protocol and helps prevent spam or malicious pool creation.
+
 For support, join our [Discord](https://discord.gg/kuzco) community.

From 766fba241fb36e54065f49f45c2867d1472c2e54 Mon Sep 17 00:00:00 2001
From: Sean <sean@kuzco.xyz>
Date: Tue, 8 Jul 2025 18:15:21 -0700
Subject: [PATCH 03/16] Update docs

---
 devnet-epoch-3/operator-guide.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/devnet-epoch-3/operator-guide.mdx b/devnet-epoch-3/operator-guide.mdx
index 6abcb95..d46333f 100644
--- a/devnet-epoch-3/operator-guide.mdx
+++ b/devnet-epoch-3/operator-guide.mdx
@@ -74,9 +74,9 @@ An operator pool is your on-chain identity that manages stake, receives job allo
 6. Click **Create Pool** and approve the transaction in your wallet
 
 <Warning>
-  Pool creation requires: - A registration fee in $INT-DEV tokens
-  (non-refundable) - Sufficient SOL for transaction fees - This wallet has not
-  created a pool before
+  Pool creation requires a registration fee in $INT-DEV tokens (non-refundable)
+  and sufficient SOL for transaction fees. Finally, ensure no pool has already
+  been created with the wallet you want to assign as the pool admin.
 </Warning>
 
 ### Step 3: Stake Your Pool

From 8cb52b00ddb0daf5554a6e616eaec9a766fbb22e Mon Sep 17 00:00:00 2001
From: Sean <sean@kuzco.xyz>
Date: Tue, 8 Jul 2025 18:15:57 -0700
Subject: [PATCH 04/16] Update docs

---
 devnet-epoch-3/delegator-guide.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/devnet-epoch-3/delegator-guide.mdx b/devnet-epoch-3/delegator-guide.mdx
index 5b3d27d..2b86b04 100644
--- a/devnet-epoch-3/delegator-guide.mdx
+++ b/devnet-epoch-3/delegator-guide.mdx
@@ -60,7 +60,7 @@ Navigate to the **Operators** page to view all available pools. Key metrics to c
 
 **Economic Terms:**
 
-- **Commission Rate**: Percentage of token rewards kept by operator
+- **Reward Commission Rate**: Percentage of token rewards kept by operator
 - **USDC Commission Rate**: Percentage of USDC revenue kept by operator
 - **Delegation Allowed**: Whether the pool accepts external stake
 - **Auto Stake Fees**: If commission is automatically compounded

From a9ceeeac2539dfa328d2a235a306dac32c2e9f2f Mon Sep 17 00:00:00 2001
From: Sean <sean@kuzco.xyz>
Date: Tue, 8 Jul 2025 18:17:11 -0700
Subject: [PATCH 05/16] Update docs

---
 devnet-epoch-3/delegator-guide.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/devnet-epoch-3/delegator-guide.mdx b/devnet-epoch-3/delegator-guide.mdx
index 2b86b04..ca42d03 100644
--- a/devnet-epoch-3/delegator-guide.mdx
+++ b/devnet-epoch-3/delegator-guide.mdx
@@ -156,9 +156,9 @@ Token rewards are distributed automatically during the unstaking process. When y
 
 USDC earnings can be withdrawn at any time without affecting your stake:
 
-1. Navigate to the operator pool or your portfolio
+1. Navigate to the operator pool on the staking dashboard
 2. Click **Withdraw USDC**
-3. Confirm the transaction to receive your accrued USDC
+3. Confirm the transaction to receive your USDC earnings
 
 <Note>
   USDC withdrawals do not affect your stake or future earning potential. You can

From c523e0617f48bce56118bf93ac1987c00d99c672 Mon Sep 17 00:00:00 2001
From: Sean <sean@kuzco.xyz>
Date: Sun, 13 Jul 2025 21:00:33 -0700
Subject: [PATCH 06/16] Add network security docs

---
 devnet-epoch-3/network-security.mdx | 185 ++++++++++++++++++++++++++++
 devnet-epoch-3/staking-protocol.mdx |   3 +
 mint.json                           |   3 +-
 3 files changed, 190 insertions(+), 1 deletion(-)
 create mode 100644 devnet-epoch-3/network-security.mdx

diff --git a/devnet-epoch-3/network-security.mdx b/devnet-epoch-3/network-security.mdx
new file mode 100644
index 0000000..261fce6
--- /dev/null
+++ b/devnet-epoch-3/network-security.mdx
@@ -0,0 +1,185 @@
+---
+title: "Network Security"
+description: "Understanding halting and slashing mechanisms in the Inference.net staking protocol"
+---
+
+The Inference.net staking protocol ensure network security through staking and slashing mechanisms.
+
+<Warning>
+  The Inference.net Staking Protocol is being tested on Solana Devnet with test
+  tokens. These tokens have no monetary value and should not be used for
+  real-world transactions or bought or sold by anyone.
+</Warning>
+
+## Security Overview
+
+To maintain network reliability and prevent malicious behavior, the protocol supports two primary security mechanisms:
+
+1. **Halting**: Temporary suspension of certain actions to allow investigation
+2. **Slashing**: Permanent penalty for severe violations, affecting only operator stake
+
+These tools are controlled by designated authorities and include safeguards to protect delegators.
+
+<Note>
+  Delegated tokens are always protected from slashing. Only an operator's own
+  stake can be penalized for violations.
+</Note>
+
+## Halting Mechanism
+
+Halting allows authorities to temporarily restrict actions while investigating potential issues. This prevents further harm without permanent penalties.
+
+### Types of Halts
+
+1. **Global Halts**
+
+   - Controlled via the `PoolOverview` account
+   - Can halt:
+     - All staking operations (`is_staking_halted`)
+     - All withdrawals/unstaking (`is_withdrawal_halted`)
+     - Reward accruals (`is_accrue_reward_halted`)
+     - New pool creation (`allow_pool_creation`)
+   - Used for network-wide emergencies or maintenance
+
+2. **Pool-Specific Halts**
+   - Sets `halted_at` timestamp on individual OperatorPool
+   - Restricts operator actions like:
+     - Staking/unstaking
+     - Claiming rewards
+     - Withdrawing commissions
+     - Closing the pool
+   - Delegators can still unstake and withdraw their funds
+   - Initiated by program halt authorities
+
+### Halt Process
+
+- Halt authorities invoke `set_halt_status` instruction
+- For pool halts, sets current timestamp as `halted_at`
+- Halts can be reversed by setting `halted_at` to None
+- Used to freeze suspicious pools during investigation
+
+## Slashing Mechanism
+
+Slashing is a permanent penalty for confirmed violations, designed to economically disincentivize malicious behavior.
+
+### What Gets Slashed
+
+- Only the operator's self-stake (from their staking record)
+- Accrued but unclaimed:
+  - Token commissions
+  - USDC commissions
+  - USDC earnings
+- Delegated tokens are never slashed
+
+### Slashing Process
+
+1. **Prerequisite: Pool Must Be Halted**
+
+   - Pool must already be halted
+   - Minimum delay period must elapse (at least 1 day, configurable via `slashing_delay_seconds`)
+
+2. **Invocation**
+
+   - Slashing authorities call `slash_stake` instruction
+   - Specify amount of shares to slash
+   - Settles any pending USDC earnings first
+
+3. **Effects**
+
+   - Reduces operator's shares and corresponding tokens
+   - Confiscates all pending commissions and USDC
+   - Transfers slashed assets to designated protocol accounts
+   - Emits `SlashStakeEvent` with details
+
+4. **Destination**
+
+   - Slashed tokens go to `slashing_destination_token_account`
+   - Slashed USDC goes to `slashing_destination_usdc_account`
+
+<Warning>
+  Slashing is irreversible. Authorities follow strict protocols and evidence
+  requirements before invoking slashes.
+</Warning>
+
+### Violation Examples
+
+Potential reasons for halting/slashing include:
+
+- Malicious job processing
+- Network attacks or spam
+- Protocol violations
+- Hardware misrepresentation
+
+## Authorities and Controls
+
+Security operations are managed by separate authority sets to distribute power:
+
+- **Halt Authorities** (`halt_authorities`): Can halt/unhalt pools
+- **Slashing Authorities** (`slashing_authorities`): Can execute slashes on halted pools
+- **Program Admin**: Can update authority lists and global settings
+
+## Protections for Participants
+
+The protocol includes several safeguards:
+
+1. **Delegator Protection**
+
+   - Delegated tokens immune to slashing
+   - Can always unstake from halted pools
+   - Protected from operator misconduct
+
+2. **Delay Periods**
+
+   - Minimum 1-day delay between halt and slash
+   - Configurable via `slashing_delay_seconds`
+   - Allows time for appeals/investigation
+
+3. **Transparency**
+
+   - All halts and slashes emit events
+   - On-chain timestamps track actions
+   - Public authority keys
+
+4. **Reversibility**
+   - Halts can be lifted
+   - Global halts are temporary controls
+
+## Best Practices for Operators
+
+To avoid security actions:
+
+- Maintain honest job processing
+- Ensure high uptime and performance
+- Follow all protocol rules
+- Monitor your pool status
+- Respond promptly to any warnings
+- Keep your hardware secure
+
+If your pool is halted:
+
+- Contact support immediately
+- Provide any requested evidence
+- Do not attempt restricted actions
+- Delegators can still withdraw
+
+## FAQ
+
+**Q: Can delegators lose funds from slashing?**<br/>
+A: No. Only operator self-stake is at risk. Delegators are fully protected.
+
+**Q: How long after halting can slashing occur?**<br/>
+A: At least 1 day (86,400 seconds), configurable but never less than minimum.
+
+**Q: Who controls the authorities?**<br/>
+A: Authority keys are managed by Inference.net governance. Lists are public and on-chain.
+
+**Q: What happens to slashed funds?**<br/>
+A: Transferred to protocol-controlled accounts to fund network security initiatives.
+
+**Q: Can I unstake from a halted pool?**<br/>
+A: Delegators can unstake from a halted pool, but operators cannot.
+
+**Q: How are violations detected?**<br/>
+A: Through inference and network verification mechanisms.
+
+For questions or concerns about network security, join our [Discord](https://discord.gg/kuzco) community.
diff --git a/devnet-epoch-3/staking-protocol.mdx b/devnet-epoch-3/staking-protocol.mdx
index 75915af..bacc690 100644
--- a/devnet-epoch-3/staking-protocol.mdx
+++ b/devnet-epoch-3/staking-protocol.mdx
@@ -315,4 +315,7 @@ A: No. Each wallet can create at most one operator pool to ensure fair participa
 **Q: What happens to the registration fee?**<br/>
 A: The registration fee is paid to the protocol and helps prevent spam or malicious pool creation.
 
+**Q: What is the base unit of the $INT token called?**<br/>
+A: The Inference $INT network token has 9 decimal places of precision and a single unit is referred to as a Bozeman.
+
 For support, join our [Discord](https://discord.gg/kuzco) community.
diff --git a/mint.json b/mint.json
index d5bb99f..40eba6c 100644
--- a/mint.json
+++ b/mint.json
@@ -61,7 +61,8 @@
         "devnet-epoch-3/airdrop",
         "devnet-epoch-3/staking-protocol",
         "devnet-epoch-3/operator-guide",
-        "devnet-epoch-3/delegator-guide"
+        "devnet-epoch-3/delegator-guide",
+        "devnet-epoch-3/network-security"
       ]
     },
     {

From 414ea4917f0a16289f0310e2d4b148e1e948553c Mon Sep 17 00:00:00 2001
From: Sean <sean@kuzco.xyz>
Date: Sun, 13 Jul 2025 21:02:28 -0700
Subject: [PATCH 07/16] Edit copy

---
 devnet-epoch-3/network-security.mdx | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/devnet-epoch-3/network-security.mdx b/devnet-epoch-3/network-security.mdx
index 261fce6..dec0a7a 100644
--- a/devnet-epoch-3/network-security.mdx
+++ b/devnet-epoch-3/network-security.mdx
@@ -3,8 +3,6 @@ title: "Network Security"
 description: "Understanding halting and slashing mechanisms in the Inference.net staking protocol"
 ---
 
-The Inference.net staking protocol ensure network security through staking and slashing mechanisms.
-
 <Warning>
   The Inference.net Staking Protocol is being tested on Solana Devnet with test
   tokens. These tokens have no monetary value and should not be used for
@@ -42,6 +40,7 @@ Halting allows authorities to temporarily restrict actions while investigating p
    - Used for network-wide emergencies or maintenance
 
 2. **Pool-Specific Halts**
+
    - Sets `halted_at` timestamp on individual OperatorPool
    - Restricts operator actions like:
      - Staking/unstaking

From c248a1cb0a3259d1f5a67b2c779f66d0f931b5a2 Mon Sep 17 00:00:00 2001
From: Sean <sean@kuzco.xyz>
Date: Tue, 22 Jul 2025 15:06:31 -0700
Subject: [PATCH 08/16] Update docs

---
 devnet-epoch-3/staking-protocol.mdx | 23 ++++-------------------
 1 file changed, 4 insertions(+), 19 deletions(-)

diff --git a/devnet-epoch-3/staking-protocol.mdx b/devnet-epoch-3/staking-protocol.mdx
index bacc690..78c307c 100644
--- a/devnet-epoch-3/staking-protocol.mdx
+++ b/devnet-epoch-3/staking-protocol.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Staking Program"
+title: "Staking Protocol"
 description: "Understanding how the Inference.net staking protocol works"
 ---
 
@@ -143,6 +143,8 @@ The protocol operates on an epoch system where rewards are distributed periodica
 3. **Operator Claims**: Each operator claims their pool's rewards using merkle proofs
 4. **Automatic Distribution**: Rewards are split between operators (commission) and delegators
 
+The epoch reward emissions scheduled is encoded and enforced in our program when epochs are finalized. You can view the [reward emissions schedule here](https://github.com/context-labs/inference-staking/blob/main/programs/inference-staking/src/emissions.rs).
+
 <Note>
   Pool reward claims are permissionless and can be submitted by anyone. Pool
   reward claims must be processed sequentially from oldest to most recent. All
@@ -213,24 +215,7 @@ The registration fee and minimum stake requirements are set globally by the prot
 
 The staking protocol supports halting and slashing of operator pools for any identified network or protocol violations. This establishes economic incentive alignment for operators to ensure network integrity.
 
-<Warning>
-  Operators may be halted or slashed for any network or protocol violations.
-</Warning>
-
-### Halt Mechanisms
-
-The protocol includes multiple halt controls for emergency situations:
-
-- **Global Staking Halt**: Prevents all new stakes
-- **Global Withdrawal Halt**: Prevents all unstaking and claims
-- **Global Pool Creation Halt**: Prevents new pools from being created
-- **Pool-Specific Halt**: Individual pools can be halted by authorities
-
-### Slashing Protection
-
-- Only operator self-stake can be slashed for violations
-- Delegated tokens are protected from slashing
-- Slashing requires authorization from designated authorities
+For more details, see the [Network Security](/devnet-epoch-3/network-security) page.
 
 ### Program Authorities
 

From d2f90fbd9453901153fb7082442983619fd351ff Mon Sep 17 00:00:00 2001
From: Sean <sean@kuzco.xyz>
Date: Wed, 23 Jul 2025 16:33:12 -0700
Subject: [PATCH 09/16] Update docs

---
 devnet-epoch-3/overview.mdx | 11 ++---------
 1 file changed, 2 insertions(+), 9 deletions(-)

diff --git a/devnet-epoch-3/overview.mdx b/devnet-epoch-3/overview.mdx
index 54b78e8..64eaea4 100644
--- a/devnet-epoch-3/overview.mdx
+++ b/devnet-epoch-3/overview.mdx
@@ -3,7 +3,7 @@ title: "Overview"
 description: "Inference.net Epoch 3: Solana protocol, stake-weighted routing, and more"
 ---
 
-On June 6th, 2025, Inference.net will launch Devnet Epoch 3, introducing significant protocol changes designed to improve network scalability, operator experience, and economic alignment. This post details the technical improvements, new staking mechanisms, and operational changes that will define this next phase of Inference.net.
+On June 6th, 2025, Inference.net launched Devnet Epoch 3, introducing significant protocol changes designed to improve network scalability, operator experience, and economic alignment. This post details the technical improvements, new staking mechanisms, and operational changes that will define this next phase of Inference.net.
 
 <Warning>
   The Inference.net Staking Protocol is being tested on Solana Devnet with test
@@ -35,14 +35,7 @@ If you are using a different wallet, or a mobile wallet, please refer to the wal
 
 ## Epoch 3 Feature Timeline
 
-Epoch 3 will be rolled out in phases, with each phase bringing new features and improvements to the network. Please see the timeline below for more details.
-
-| Date               | Features              | Description                                                                                                                                                                                                                     |
-| ------------------ | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **June 6, 2025**   | **Network Upgrade**   | • Auto-update system activation for all node types<br/>• Enhanced GPU detection and validation<br/>• Unified inference engine<br/>• New simplified node deployment instructions<br/>• Unknown GPUs blocked from joining network |
-| **June 13, 2025**  | **Economic Layer**    | • $INT-DEV token airdrop to eligible operators<br/>• Staking protocol goes live<br/>• Stake-weighted job routing begins<br/>• Operator pool creation enabled<br/>• Delegation functionality activated                           |
-| **June 20, 2025**  | **Extended Features** | • Bonus point system for community contributions<br/>• Additional point-earning opportunities<br/>• Enhanced monitoring and analytics<br/>• Reputation system testing begins                                                    |
-| **Late June 2025** | **Advanced Features** | • Full reputation scoring activation<br/>• Performance-based routing adjustments<br/>• Slashing mechanism testing (devnet only)<br/>• Advanced operator pool management features                                                |
+Epoch 3 will be rolled out in phases, with each phase bringing new features and improvements to the network. Please follow Discord for updates.
 
 ## Core Protocol Improvements
 

From 64802372898718dd4379a9a4bc69c032a12b1e75 Mon Sep 17 00:00:00 2001
From: Sean <sean@kuzco.xyz>
Date: Sat, 26 Jul 2025 10:26:35 -0700
Subject: [PATCH 10/16] Update docs

---
 devnet-epoch-3/bug-bounty-program.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/devnet-epoch-3/bug-bounty-program.mdx b/devnet-epoch-3/bug-bounty-program.mdx
index c54943e..d7da850 100644
--- a/devnet-epoch-3/bug-bounty-program.mdx
+++ b/devnet-epoch-3/bug-bounty-program.mdx
@@ -3,14 +3,14 @@ title: "Bug Bounty Program"
 description: "This program covers vulnerabilities in Inference.net's Solana smart contracts, inference system, and supporting infrastructure. Rewards are paid in USD based on severity and impact."
 ---
 
+Our on-chain programs are currently being audited by different auditing firms and any bug bounty submissions submitted during this period will be awarded at our discretion.
+
 ## Notice
 
 <Warning>
   The Inference.net Staking Protocol is being tested on Solana Devnet with test
   tokens. These tokens have no monetary value and should not be used for
-  real-world transactions or bought or sold by anyone. Our on-chain programs are
-  currently being audited by different auditing firms, and any bug bounty
-  submissions submitted during this period will be awarded at our discretion.
+  real-world transactions or bought or sold by anyone.
 </Warning>
 
 ## Scope

From 20fa1f4d099e688e082d3e2063b41b539df1d2a3 Mon Sep 17 00:00:00 2001
From: Sean <sean@kuzco.xyz>
Date: Mon, 28 Jul 2025 16:58:02 -0700
Subject: [PATCH 11/16] Update docs

---
 devnet-epoch-3/airdrop.mdx            |  9 ++++++---
 devnet-epoch-3/bug-bounty-program.mdx |  5 ++---
 devnet-epoch-3/overview.mdx           | 27 ---------------------------
 devnet-epoch-3/staking-protocol.mdx   |  2 +-
 mint.json                             |  3 ++-
 5 files changed, 11 insertions(+), 35 deletions(-)

diff --git a/devnet-epoch-3/airdrop.mdx b/devnet-epoch-3/airdrop.mdx
index 5af27ac..733aeab 100644
--- a/devnet-epoch-3/airdrop.mdx
+++ b/devnet-epoch-3/airdrop.mdx
@@ -18,9 +18,12 @@ Welcome to the Inference.net Devnet Token Airdrop! This guide will walk you thro
 Before you can claim your airdrop, you must meet the following requirements:
 
 <Info>
-  **Eligibility Requirements**: You must have previously connected and linked a
-  Solana wallet to your Inference.net account - Only accounts that linked a
+  **Eligibility Requirements**:
+  
+You must have previously connected and linked a
+  Solana wallet to your Inference.net account. Only accounts that linked a
   Solana wallet before the deadline are eligible for the airdrop.
+
 </Info>
 
 <Info>
@@ -33,7 +36,7 @@ testing.
 
 ## Claiming Your Airdrop
 
-Once your wallet is configured for Devnet, follow these steps to claim your tokens:
+Once your wallet is configured for Solana Devnet, follow these steps to claim your tokens:
 
 <Steps>
   <Step title="Visit the Airdrop Page">
diff --git a/devnet-epoch-3/bug-bounty-program.mdx b/devnet-epoch-3/bug-bounty-program.mdx
index d7da850..9d6581d 100644
--- a/devnet-epoch-3/bug-bounty-program.mdx
+++ b/devnet-epoch-3/bug-bounty-program.mdx
@@ -19,9 +19,8 @@ The following components are in scope for this bug bounty program:
 
 **Solana Programs:**
 
-- Staking Program
+- [Staking Program](https://github.com/context-labs/inference-staking)
 - Airdrop Program
-- Delegation and reward distribution logic
 
 **Inference System:**
 
@@ -229,6 +228,6 @@ This bug bounty program may be updated as our system evolves:
 - Major changes will be announced in Discord
 - Submissions are evaluated based on the rules at time of submission
 
-<Info>Last updated: June 2025 | Version 1.0</Info>
+<Info>Last updated: July 2025 | Version 1.0</Info>
 
 Thank you for helping us secure Inference.net.
diff --git a/devnet-epoch-3/overview.mdx b/devnet-epoch-3/overview.mdx
index 64eaea4..f795fac 100644
--- a/devnet-epoch-3/overview.mdx
+++ b/devnet-epoch-3/overview.mdx
@@ -178,33 +178,6 @@ During Epoch 3, operators will interact with two distinct reward mechanisms:
   real-world transactions or bought or sold by anyone.
 </Warning>
 
-## Reputation System (Coming Later in Epoch 3)
-
-While stake-weighted routing launches on June 13th, the reputation system will be enabled later in Epoch 3 after validating the base routing mechanism. The reputation score will incorporate:
-
-### Completion Score
-
-Operators are grouped into performance tiers based on successful request completion rates over a rolling multi-day window:
-
-- Tier 1 (>99.5% completion): 1.0 multiplier
-- Tier 2 (98-99.5% completion): 0.9 multiplier
-- Tier 3 (96-98% completion): 0.8 multiplier
-- And so forth...
-
-### Throughput Score
-
-Performance buckets based on tokens per second relative to model-specific benchmarks:
-
-- Benchmarks are set per model and GPU type
-- Operators meeting or exceeding benchmarks receive full score
-- Below-benchmark performance results in proportional score reduction
-
-### Penalty System
-
-- First offense: 1-hour timeout from job routing
-- Repeated offenses: Extended timeouts up to permanent suspension
-- Penalties affect both routing priority and reward eligibility
-
 ## Long-term Implications
 
 The architectural changes in Epoch 3 establish the foundation for Inference.net's evolution from a points-based test network to a fully decentralized, economically sustainable inference protocol. The stake-weighted routing system creates a market mechanism for quality assurance, while the delegation system enables broader participation beyond hardware operators.
diff --git a/devnet-epoch-3/staking-protocol.mdx b/devnet-epoch-3/staking-protocol.mdx
index 78c307c..dccdcef 100644
--- a/devnet-epoch-3/staking-protocol.mdx
+++ b/devnet-epoch-3/staking-protocol.mdx
@@ -301,6 +301,6 @@ A: No. Each wallet can create at most one operator pool to ensure fair participa
 A: The registration fee is paid to the protocol and helps prevent spam or malicious pool creation.
 
 **Q: What is the base unit of the $INT token called?**<br/>
-A: The Inference $INT network token has 9 decimal places of precision and a single unit is referred to as a Bozeman.
+A: The Inference network token has 9 decimal places of precision and a single unit is referred to as a Bozeman.
 
 For support, join our [Discord](https://discord.gg/kuzco) community.
diff --git a/mint.json b/mint.json
index 40eba6c..80ad0e0 100644
--- a/mint.json
+++ b/mint.json
@@ -62,7 +62,8 @@
         "devnet-epoch-3/staking-protocol",
         "devnet-epoch-3/operator-guide",
         "devnet-epoch-3/delegator-guide",
-        "devnet-epoch-3/network-security"
+        "devnet-epoch-3/network-security",
+        "devnet-epoch-3/bug-bounty-program"
       ]
     },
     {

From 09211bb63589ad88ce0c89d829714dc97fb3c857 Mon Sep 17 00:00:00 2001
From: Sean <sean@kuzco.xyz>
Date: Thu, 31 Jul 2025 14:35:36 -0700
Subject: [PATCH 12/16] Add faucet docs

---
 devnet-epoch-3/airdrop.mdx | 31 +++++++++++++++++++++++++++++--
 1 file changed, 29 insertions(+), 2 deletions(-)

diff --git a/devnet-epoch-3/airdrop.mdx b/devnet-epoch-3/airdrop.mdx
index 733aeab..13d67c1 100644
--- a/devnet-epoch-3/airdrop.mdx
+++ b/devnet-epoch-3/airdrop.mdx
@@ -29,8 +29,7 @@ You must have previously connected and linked a
 <Info>
   **What if I didn't link my wallet in time?**
 
-If you did not link your wallet in time, you are not eligible for the airdrop. Don't worry, we will provide an alternative mechanism for you to acquire tokens and participate in the next phase of
-testing.
+If you did not link your wallet in time, you are not eligible for the airdrop. See the token faucet section below for instructions on how to get test tokens.
 
 </Info>
 
@@ -77,6 +76,34 @@ Once your wallet is configured for Solana Devnet, follow these steps to claim yo
   </Step>
 </Steps>
 
+## Token Faucet
+
+If you did not link your wallet in time, you are not eligible for the airdrop. You can still get test tokens by using the token faucet.
+
+<Warning>
+  Any abuse of the token faucet may result in it being disabled for everyone,
+  and offending accounts being banned with no warning or exceptions.
+</Warning>
+
+**The test token faucet is subject to the following rules:**
+
+- Wallets must be linked to an Inference.net account.
+- Only one request per wallet is allowed.
+- Wallets must have an existing devnet SOL balance.
+
+**Instructions:**
+
+<Steps>
+  <Step title="Link Your Wallet">
+    Link your wallet to your Inference.net account by visiting the
+    [dashboard](https://devnet.inference.net/dashboard/wallet).
+  </Step>
+  <Step title="Request Tokens">
+    Visit the [token faucet](https://stake.devnet.inference.net/faucet) and
+    request tokens.
+  </Step>
+</Steps>
+
 ## Troubleshooting
 
 ### Common Issues

From af277dd3bb007f0ea6b5caebab5f7eae471d7d8e Mon Sep 17 00:00:00 2001
From: Sean <sean@kuzco.xyz>
Date: Mon, 4 Aug 2025 12:09:51 -0700
Subject: [PATCH 13/16] Update docs

---
 devnet-epoch-3/network-security.mdx | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/devnet-epoch-3/network-security.mdx b/devnet-epoch-3/network-security.mdx
index dec0a7a..82649b7 100644
--- a/devnet-epoch-3/network-security.mdx
+++ b/devnet-epoch-3/network-security.mdx
@@ -11,6 +11,10 @@ description: "Understanding halting and slashing mechanisms in the Inference.net
 
 ## Security Overview
 
+We employ various internal inference verification mechanisms to ensure honest behavior among all GPU operators. Some of these scores are surfaced to users through our dashboards as Verification Scores. GPU operators who fail inference verification checks, or who are identified by other security mechanisms, may be halted or slashed.
+
+## Protocol Security Features
+
 To maintain network reliability and prevent malicious behavior, the protocol supports two primary security mechanisms:
 
 1. **Halting**: Temporary suspension of certain actions to allow investigation

From d1e48d3f57f912b2669aa08b3c11df6a555ab4a4 Mon Sep 17 00:00:00 2001
From: Sean <sean@kuzco.xyz>
Date: Mon, 4 Aug 2025 13:32:34 -0700
Subject: [PATCH 14/16] Update docs

---
 devnet-epoch-3/network-security.mdx | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/devnet-epoch-3/network-security.mdx b/devnet-epoch-3/network-security.mdx
index 82649b7..a771fe4 100644
--- a/devnet-epoch-3/network-security.mdx
+++ b/devnet-epoch-3/network-security.mdx
@@ -13,6 +13,12 @@ description: "Understanding halting and slashing mechanisms in the Inference.net
 
 We employ various internal inference verification mechanisms to ensure honest behavior among all GPU operators. Some of these scores are surfaced to users through our dashboards as Verification Scores. GPU operators who fail inference verification checks, or who are identified by other security mechanisms, may be halted or slashed.
 
+<Note>
+  Inference verifications are currently only produced by workers running Docker
+  ([see instructions here](/advanced/docker)). This may become required in the
+  future.
+</Note>
+
 ## Protocol Security Features
 
 To maintain network reliability and prevent malicious behavior, the protocol supports two primary security mechanisms:

From 06184316ab3321d39303cb1e520b3fcb732c2379 Mon Sep 17 00:00:00 2001
From: Sean <sean@kuzco.xyz>
Date: Sun, 10 Aug 2025 14:19:38 -0700
Subject: [PATCH 15/16] Add reputation scoring system docs

---
 devnet-epoch-3/overview.mdx | 53 +++++++++++++++++++++++++++++++++++++
 1 file changed, 53 insertions(+)

diff --git a/devnet-epoch-3/overview.mdx b/devnet-epoch-3/overview.mdx
index f795fac..5ea5ba2 100644
--- a/devnet-epoch-3/overview.mdx
+++ b/devnet-epoch-3/overview.mdx
@@ -107,6 +107,59 @@ Since operators manage varying numbers of GPUs with different VRAM capacities, t
 
 Despite equal stake, Operator A's individual 4090s each receive: 100,000 × (24/96) = 25,000 effective stake per device, while Operator B's A100 receives the full 100,000 stake allocation.
 
+## Reputation Scoring System
+
+We employ a reputation system to evaluate GPU operator quality and determine job routing and rewards. Reputation combines three components: **Verification**, **Uptime**, and **Reliability**. Together, these reflect integrity, availability, and request completion performance and allow pool delegators to make more informed delegation decisions.
+
+### Verification Score
+
+Determines operator honesty and is used to determine job routing.
+
+- We use a proprietary inference verification system to ensure that operators are running inference jobs honesty.
+- This system runs pass/fail verifications on all processed requests.
+- A score is computed based on a rolling window of verifications and operators are promoted/demoted from our trusted lane based on a verification failure threshold.
+
+**Verification Guidelines**
+
+New workers are placed in the evaluation lane and receive test traffic to build trust. This traffic does not earn rewards/points. Once a worker has passed a specific number of verifications, they are promoted to the trusted lane and begin receiving verified inference traffic.
+
+If a trusted worker begins failing too many verifications, they can be moved back to the evaluation lane until performance improves.
+
+**Verification Thresholds**
+
+Note that these thresholds may be adjusted over time. The following are an example:
+
+- **Promotion**: Untrusted operators with ≤5 failures in their last 500 verifications are promoted to the trusted lane.
+- **Demotion**: Trusted operators with ≥10 failures in their last 500 verifications are demoted to the evaluation lane.
+
+<Warning>
+  Operators that consistently fail verifications may be halted and slashed,
+  according to the [network security
+  guidelines](/devnet-epoch-3/network-security).
+</Warning>
+
+### Reliability Score
+
+Captures how consistently requests complete successfully and on time.
+
+- Inference request completion rates are measured over a fast and slow window and combined into a single score.
+- The score calculation uses a weighted average of the fast and slow window scores, e.g. 0.5 for fast (1 hour) and 0.5 for slow (72 hours).
+- Scores are recomputed for all operators hourly.
+
+### Uptime Score
+
+Measures how consistently instances are online and responsive.
+
+- The network periodically checks whether instances are by sending a health check inference request to the instance.
+- If the instance completes the request, it is considered online for the interval.
+- If the instance does not complete the request, it is considered offline for the interval.
+- To prevent gaming, checks begin only after an instance has been running for a short buffer period following startup.
+
+<Tip>
+  Uptime scores are incorporated into network reward emission calculations to
+  allow us to incentive specific types of hardware to join the network.
+</Tip>
+
 ## Solana-Based Staking Protocol
 
 ### Technical Implementation

From 21bd2bef94cbd2a01ee741ed9b939d8d01d7d20d Mon Sep 17 00:00:00 2001
From: Sean <sean@kuzco.xyz>
Date: Thu, 14 Aug 2025 17:52:24 -0700
Subject: [PATCH 16/16] Update docs

---
 devnet-epoch-3/overview.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/devnet-epoch-3/overview.mdx b/devnet-epoch-3/overview.mdx
index 5ea5ba2..c6a9bee 100644
--- a/devnet-epoch-3/overview.mdx
+++ b/devnet-epoch-3/overview.mdx
@@ -150,14 +150,16 @@ Captures how consistently requests complete successfully and on time.
 
 Measures how consistently instances are online and responsive.
 
-- The network periodically checks whether instances are by sending a health check inference request to the instance.
+- The network periodically checks whether instances are online by sending a health check inference request to the instance.
 - If the instance completes the request, it is considered online for the interval.
 - If the instance does not complete the request, it is considered offline for the interval.
 - To prevent gaming, checks begin only after an instance has been running for a short buffer period following startup.
 
 <Tip>
   Uptime scores are incorporated into network reward emission calculations to
-  allow us to incentive specific types of hardware to join the network.
+  allow us to incentive specific types of hardware to join the network. Rewards
+  are normalized across all operators by the number of points earned. More
+  hardware means more points, and more points means more rewards.
 </Tip>
 
 ## Solana-Based Staking Protocol
