1. Enhanced DataDAO Descriptions

Updated descriptions clarify the type of dataset each DataDAO collects.

2. “Top DataDAO” Tag

Introduced a new tag to identify DataDAOs in the Top 16. Only these are currently eligible for rewards each cycle (subject to change as DataDAOs compete).

3. Improved “Completed Cycle” Modal

Rewards are now shown in two separate columns — one for staker rewards and one for DataDAO rewards, providing clearer historical records.

4. Multiplier Display Fix

Resolved an issue causing incorrect multiplier values for stakes from Epoch 1 and Epoch 2 under the new formula.

5. UI & Performance Enhancements

Various small improvements to enhance user experience and app performance.

1. Unified APY

In line with VRC-11, all DataDAOs now display the same APY for stakers. APY calculations incorporate auto-staking of annual rewards for more accurate projections.

2. DataDAOs Table → Cards

The list of DataDAOs is now shown as cards displayed in a random order rather than a single table, making it easier to stake where you believe in the mission and data potential

3. Multiplier Graph

A new visual explains how your time-weighted staking multiplier scales over days staked, reflecting the latest VRC-8 guidelines.

4. Vested Rewards Progress

A progress bar in the “Completed Cycles” tab displays how much of your rewards have vested and are ready to claim.

5. Earned Amounts Bug Fix

The most important update: we’ve fixed an issue causing incorrect “earned amounts” to display. These figures are now the source of truth and can be verified according to these guidelines.

Below is a concise Cycle 3 Changelog, reflecting the three new VRCs — VRC-8, VRC-10, and VRC-11 — now in effect from 01/27. Each brings critical updates to time-weighted rewards, data integrity checks, and unified APY that impact both stakers and DataDAO creators.

VRC-8: Time-Weighted Rewards

1. Why:
   1. Eliminate last-minute “stake-and-dump” exploits, encourage consistent participation, and ensure that both stakers and DataDAOs are rewarded proportionally to the duration of their contributions.
2. What:
   1. Stakers: Rewards scale based on days staked under 21 days (e.g., 10 days = 10/21×). Past 21 days, established multipliers kick in (1.5× by Day 42, up to 3× by Day 84).
   2. Creators (DataDAO Scoring): The total staked amount only counts fully if stakers have been in for at least 21 days. Short-term stakes are discounted, benefiting DataDAOs that foster long-term engagement.

VRC-10: DataDAO Verification & Integrity Standards

• Why:
  • Safeguard the ecosystem from fraudulent activity, ensure high-quality data contributions, and maintain community trust.
• What:
  • De-Verification: DataDAOs caught in bot usage, Sybil attacks, or malicious practices can be de-verified—losing eligibility for rewards until issues are resolved.
  • Data Audits: Random checks of data submissions to verify authenticity; flagged issues must be addressed to regain “verified” status.

VRC-11: DataDAO Rewards Evolution

• Why:
  • Refine reward distributions and improve user experience, aligning incentives with meaningful contributions.
• What:
  • Unified APY: All DataDAOs share the same APY for stakers, letting you stake in the DataDAO you truly believe in
    • From APR to APY: Datahub now shows APY with auto-compounding of rewards, showing a higher percentage to reflect real growth over time.
  • No 7-Day Unstaking Delay: Feel free to move your $VANA stake at any time, with rewards still weighted by how long you’ve been staked.
  • Removal of the Sublinear Formula: The older sublinear distribution for rewards is replaced by a simpler linear approach, making it more transparent and fair for DataDAO creators.
  • Custodial Management of Creator Rewards: The Vana Foundation temporarily holds creators’ allocations, deploying them strategically to help grow each DataDAO’s marketplace and network presence.
    • Major Impact: This ensures rewards aren’t claimed and abandoned; they’re actively used to stimulate robust DataDAO ecosystems.
  • Removed Unique-Contributor Weighting: Rewards for creators and stakers are now 100% stake-based, preventing the creation of shallow, high-contributor-count DataDAOs.

In the “Completed Cycle” tab, the “Your Allocation” widget has been temporarily replaced with “Percentage of Vested Rewards” due to a subgraph issue affecting the summary of rewards from multiple DataDAOs and stakes.

The actual claimable rewards in the “Manage Stakes” widget remain accurate.

To verify your rewards:

1. Find Your Stakes: StakeStakesListValues method
2. Get Info About Your Stakes: Stakes method
3. Check Rewards: StakeClaimedAmounts method

We’re addressing this issue and will restore the original functionality as soon as possible.

Datahub got a new upgrade for the upcoming epoch 3!

Added

• Data Liquidity Provider filtering
• Advanced tooltip position improvements

Changed

• Updated user interface design and colors
• Enhanced sidebar experience
• Updated Data DAO header layout
• Updated stake information display
• Updated unverified DataDAOs display

Fixed

• Mobile responsiveness improvements
• Improved mobile stake drawer design
• Fixed sidebar display issues
• Fixed Data DAO sorting issues

Improved

• Enhanced table performance and data loading
• Improved documentation
• Made table rows interactive for better usability

Enhanced

• More consistent button designs across the platform

https://github.com/vana-com/vana-smart-contracts/pull/7/

DLPRootMetric - New Contract

DLPRootMetrics is a contract that handles performance rating calculations and metrics for DLPs (Decentralized Liquidity Providers) in the system. Key functionalities include:

1. Managing epoch performance ratings for DLPs
2. Calculating top-performing DLPs based on both stake and performance metrics
3. Estimating reward percentages and APY for DLPs
4. Maintaining a scoring system with configurable weights between stake-based and performance-based ratings

The contract uses a dual rating system where:

• Stake Rating: Based on the amount staked
• Performance Rating: Based on DLP's performance metrics

Events

1. EpochPerformanceRatingsSaved(uint256 indexed epochId, uint256 totalPerformanceRating, bool isFinalized)
2. DlpEpochPerformanceRatingSaved(uint256 indexed epochId, uint256 indexed dlpId, uint256 performanceRating)
3. RatingPercentagesUpdated(RatingType ratingType, uint256 percentage)

DataRegistry Changes

Modified Events

• ProofAdded event updated:
  • Old: event ProofAdded(uint256 indexed fileId, uint256 indexed proofIndex)
  • New: event ProofAdded(uint256 indexed fileId, uint256 indexed proofIndex, uint256 indexed dlpId, uint256 score)

DLPRootSmartContract Changes

Architectural Changes

The main architectural change in this update is the separation of responsibilities between DLPRoot and DLPRootMetrics. A significant portion of the rating and performance calculation logic has been moved from DLPRoot to DLPRootMetrics, making the system more modular.

Previously, DLPRoot handled both stake management and performance calculations. Now:

• DLPRootMetrics: Responsible for performance ratings and metrics calculations
• DLPRoot: Focuses on stake management, basic DLP operations, and interfacing with treasury contracts

The reward distribution system has been significantly reworked. DLPRoot now works with separate treasury contracts for rewards and stakes, with reward calculations including both performance-based and stake-based components.

Modified Events

1. EpochCreated
   • Old: event EpochCreated(uint256 epochId)
   • New: event EpochCreated(uint256 epochId, uint256 startBlock, uint256 endBlock, uint256 rewardAmount)
2. DlpRewardClaimed
   • Old: event EpochDlpScoreSaved(uint256 indexed epochId, uint256 indexed dlpId, uint256 totalStakesScore);
   • New: event DlpRewardClaimed(uint256 indexed dlpId, uint256 indexed epochId, uint256 rewardAmount, uint256 stakersRewardAmount)

New Events

1. DlpBecameSubEligible(uint256 indexed dlpId)
2. DlpBecomeIneligible(uint256 indexed dlpId)
3. StakeRewardClaimed(uint256 indexed stakeId, uint256 indexed epochId, uint256 amount, bool isFinal)
4. event EpochOverridden(uint256 epochId, uint256 startBlock, uint256 endBlock, uint256 rewardAmount);
5. event DlpRewardClaimed(uint256 indexed dlpId, uint256 indexed epochId, uint256 rewardAmount, uint256 stakersRewardAmount);

Note: All performance-related events are now emitted by DLPRootMetrics instead of DLPRoot, reflecting the new separation of concerns in the system architecture.

We've improved our DLP Root Contract, making registering a DLP and staking easier. In order for a DLP to be elegible for DLP rewards, they must be registered on this contract.

As we get closer to mainnet launch, our focus this week was getting our key smart contracts audited. We've partnered up with a trusted blockchain security and audit firm Hashlock.

You can find the report below.

The Satya Network in the Moksha testnet was scaled up this week to keep up with the tremendous proof-of-contribution requests that are being served by the network.

Other notable improvements:

Faucet: Fixed a bug affecting the faucet during heavy use
RPC: Made several security improvements across our RPC nodes on Moksha

📚 Fresh docs are live! Rebuilt from scratch to make building on Vana 10x easier.