agentleFS
SperaxSperax/sperax-skills/skills/sperax-spa-staking/SKILL.md

sperax-spa-staking

Skill8 starsChanged 9 months agoMITView on GitHub

Guide to SPA token staking, veSPA governance, and xSPA rewards in the Sperax ecosystem. Covers lock mechanics, voting power, reward claiming, and governance participation. Use when explaining SPA tokenomics, helping users stake, or answering governance questions.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When helping users with SPA staking:

    line 106
  2. Distinctive:

    Check current APYs at app.sperax.io before recommending

    line 109

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SPA Staking & Governance Guide

The Sperax governance system uses a vote-escrowed model: lock SPA to get veSPA, which gives governance voting power and protocol fee rewards.

Token Overview

SPA — Governance & Value Accrual

PropertyDetail
ChainArbitrum One
Address0x5575552988A3A80504bBaeB1311674fCFd40aD4B
Value accrual30% of USDs yield + 100% of protocol fees → buyback-and-burn
Also onEthereum: 0xB4A3B0Faf0Ab53df58001804DdA5Bfc6a3D59008

veSPA — Governance Power

Lock your SPA for 7 days to 4 years to receive veSPA:

veSPA = SPA × (lockup_days / 365)
  • Minimum lock: 7 days
  • Maximum lock: 4 years (1,461 days)
  • Decay: veSPA decays linearly toward your lock expiry
  • Rewards: 100% of USDs protocol fees + 420,000 xSPA/week

Example: Lock 1,000 SPA for 2 years → receive 2,000 veSPA (decaying over time)

xSPA — Reward Token

xSPA is the reward distributed to veSPA stakers weekly (Thursdays UTC).

OptionWhat happens
Stake xSPA → veSPA1:1 ratio, but requires ≥180-day lock
Redeem xSPA → SPA0.5–1.0 SPA over 15–180 days

Redemption formula:

Receivable SPA = (xSPA × (redeemDuration + 150)) / 330
  • Redeem over 15 days → ~0.5 SPA per xSPA
  • Redeem over 180 days → 1.0 SPA per xSPA

Staking Walkthrough

Step 1: Get SPA on Arbitrum

Buy SPA on Arbitrum One via any DEX (Camelot, Uniswap). If you have SPA on Ethereum, bridge it to Arbitrum first.

Step 2: Lock SPA → veSPA

  1. Go to app.sperax.io
  2. Navigate to the Staking section
  3. Choose lock duration (longer = more veSPA)
  4. Approve and lock SPA

Step 3: Earn Rewards

  • Fees: Distributed weekly in USDs
  • xSPA: 420,000 xSPA distributed weekly (per SIP-66)
  • Claim: Visit the Staking page to claim accumulated rewards

Step 4: Manage xSPA

Choose to either:

  • Stake into veSPA (1:1, but requires ≥180-day lock)
  • Redeem to SPA (0.5–1.0 ratio based on vesting period)

Governance Process

Sperax uses a 4-phase governance model:

PhaseActivityDuration
Phase 0Discord ideationOpen-ended
Phase 1Forum SIP proposal48-hour discussion minimum
Phase 2Snapshot vote3 days, veSPA-weighted
Phase 3Engineering implementationVaries

Voting: Snapshot.org with veSPA weighting

  • Quorum: 200M veSPA
  • Passing: >50% Yes votes

Snapshot: https://snapshot.box/#/s:speraxdao.eth

Key Contracts (Arbitrum)

ContractAddress
SPA0x5575552988A3A80504bBaeB1311674fCFd40aD4B
veSPA Proxy0x2e2071180682Ce6C247B1eF93d382D509F5F6A17
xSPA0x0966E72256d6055145902F72F9D3B6a194B9cCc3

Agent Tips

When helping users with SPA staking:

  1. Emphasize the tradeoff: longer lock = more veSPA = more rewards, but less liquidity
  2. xSPA redemption: longer redeem period = better ratio (max 1:1 at 180 days)
  3. Check current APYs at app.sperax.io before recommending
  4. Governance requires veSPA — you must lock SPA first

Links

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.