Skip to main content
This map identifies likely implementation surfaces for each option. It is intended for ticket decomposition and sequencing, not for production deployment.

​
Option A: Vested ATLAS (esATLAS)

Effort: L Risk: High Likely contract/backend touchpoints:
  • contracts/staking/StakingRewards.sol (or dedicated vesting contract integration)
  • contracts/interfaces/quick/IStakingRewards.sol
  • scripts/rewards/config.ts
  • scripts/rewards/run-pipeline.ts
Likely frontend/docs touchpoints:
  • apps/web/src/hooks/useStakingContract.ts
  • apps/web/src/components/staking/StakingDashboard.tsx
  • apps/web/src/components/staking/StakeForm.tsx
  • apps/docs/tokenomics/overview.md
Likely tests:
  • test/staking/StakingRewards.test.ts
  • test/staking/StakingRewards.edge.test.ts
  • test/staking/StakingRewards.uups.test.ts

​
Option B: Staking boost multiplier

Effort: M Risk: Medium Likely contract/backend touchpoints:
  • contracts/staking/StakingRewards.sol
  • test/unit/StakingV2/DhedgeStakingRewardsCalculatorTest.ts
  • services/api/src/requests/stats.ts
Likely frontend touchpoints:
  • apps/web/src/hooks/useStakingContract.ts
  • apps/web/src/components/staking/StakingStats.tsx
  • apps/web/src/components/staking/StakingDashboard.tsx
Likely tests:
  • test/unit/StakingV2/DhedgeStakingV2Test.ts
  • test/unit/StakingV2/DhedgeVDHTCalculatorTest.ts
  • apps/web/tests/pool-detail.spec.ts

​
Option C: Performance fee discount

Effort: M to L depending on fee-path constraints Risk: Medium to High Likely contract/backend touchpoints:
  • contracts/PoolManagerLogic.sol
  • contracts/PoolLogic.sol
  • scripts/rewards/run-pipeline.ts
  • services/api/src/requests/pools.ts
  • services/api/src/utils/poolManager.ts
Likely frontend touchpoints:
  • apps/web/src/app/pool/[address]/page.tsx
  • apps/web/src/components/VaultTradingSetup.tsx
  • apps/web/src/lib/metrics.ts
Likely tests:
  • test/unit/core/PoolLogicTest.ts
  • test/unit/core/PoolFactoryTest.ts
  • test/integration/polygon/ManagerFeeTest.ts
  • apps/web/tests/pool-detail.spec.ts

​
Option D: Fixed USDC bonus pool

Effort: M Risk: Medium Likely contract/backend touchpoints:
  • contracts/staking/StakingRewards.sol (distribution path reuse)
  • scripts/rewards/run-pipeline.ts
  • services/api/src/requests/admin.ts
  • services/api/src/requests/stats.ts
Likely frontend touchpoints:
  • apps/web/src/components/BuySellPanel.tsx
  • apps/web/src/app/pool/[address]/page.tsx
  • apps/web/src/components/staking/StakingDashboard.tsx
Likely tests:
  • test/staking/StakingRewards.test.ts
  • test/staking/StakingRewards.edge.test.ts
  • apps/web/tests/forms.spec.ts

​
Option E: Points / future airdrop credit

Effort: S to M Risk: Low to Medium (economic value uncertainty) Likely contract/backend touchpoints:
  • Off-chain ledger in API layer (new route/model work expected)
  • services/api/src/requests/stats.ts
  • services/api/src/requests/admin.ts
Likely frontend touchpoints:
  • apps/web/src/components/staking/StakingDashboard.tsx
  • apps/web/src/components/staking/StakingStats.tsx
  • apps/web/src/lib/metrics.ts
Likely tests:
  • apps/web/tests/navigation.spec.ts
  • apps/web/tests/forms.spec.ts
  • API stats/admin request tests in services/api/test/*

​
Summary recommendation

For first implementation wave:
  • Primary: Option C behind hard guards (feature flag + drawdown cap).
  • Conditional next wave: Option A campaign mode only if Phase 1 KPIs pass.
  • Keep B/D/E as fallback experiments, not default launch path.