vault product parked · 2026-04-27 · see /memory for current direction

AUSPEX

the voting vault for reppo.

stake $REPPO. pick a voting profile. the vault aggregates every depositor's veREPPO power into one weighted vote per pod. multiple strategies. one efficient cast. yield distributed pro-rata.

substrate reppo · base
model profile-weighted vault
wrapper $REPPO → auREPPO
aggregation veREPPO-power weighted

voting power decays linearly across 48 hours.
so does your sleep.

reppo voters lock $reppo into veREPPO and allocate that voting power across datanets. within each 48-hour epoch, voting power decays linearly. early conviction is worth more than late momentum-following. there is no slashing. voter quality is policed by opportunity cost and two-sided voting alone.

which means voting well requires reading every publisher submission across every datanet you hold a position in, applying judgment, and casting stake quickly. every 48 hours. across 9+ live datanets. per epoch.

EARLY · MAX WEIGHT 0h 6h 24h 48h 100% 0% VOTING POWER AUSPEX VOTES HERE MANUAL
  • 019+ live datanets as of v2 launch. 700+ submissions per epoch across the network.
  • 02linear decay means a vote at hour 6 is worth ~87% of hour 0. a vote at hour 36 is worth 25%. a vote at hour 47 is worth nothing.
  • 03no slashing. the only cost of bad voting is opportunity cost on locked capital and being shorted by two-sided voters.
  • 04performance pool distributes 5% every third epoch. consistent early conviction compounds.

auspex reads. auspex scores. auspex votes.

this is a synthetic demo showing the agent loop end-to-end. the rubric on the left is what you encode once. the feed in the middle is what auspex sees. the log on the right is what you wake up to.

auspex · simulated epoch
epoch 0142 · t+00:00 · weight 100%

your rubric

factual grounding claim has a verifiable source within the submission
domain coherence terminology consistent with the datanet topic
novelty not duplicative of last 7 days of submissions
format integrity passes the datanet's submission schema
publisher history past submissions trended above-median quality
mode: recommend
budget/epoch: 12% of veREPPO
auto-veto: contradiction · plagiarism · format failure

submissions feed · 3 datanets watched

decision log

read 0
votes cast 0
budget used 0%
synthetic data · no on-chain action · no real veREPPO at risk

stake. pick a profile. let the vault vote on your behalf.

auspex is not a single-rubric pool. it is a market for voting strategies. each profile is a registered rubric run by its own agent. depositors back the profile they trust with their veREPPO power. the vault casts one aggregate vote per pod, weighted across profiles by the share of total veREPPO behind each one.

01

stake + select

one-time per deposit. switch profiles any time, no cost.

  • connect wallet
  • browse registered profiles + their rubrics
  • pick the profile your veREPPO will back
  • choose deposit amount + lock duration
  • receive auREPPO proportional to amount × duration
  • switchProfile() at any time, no unstake required
02

vault votes

every 48-hour epoch. early-decay window covered automatically.

  • each profile's agent reads incoming pods
  • each profile scores pods per its rubric
  • vault aggregates: Σ (intention × veREPPO share)
  • net direction + magnitude is cast as one on-chain vote
  • per-profile intentions logged for full transparency
  • no manual review, no late votes, no missed pods
03

yield + switch

after every performance pool distribution.

  • performance pool rewards distributed pro-rata to auREPPO holders
  • per-profile performance metrics published on-chain
  • see how your profile compared to vault average
  • switch profiles if your trusted strategy underperformed
  • capital reallocates to better-performing profiles automatically
  • the vault gets smarter as the market chooses better profiles

three archetypes. five strategies.
calibrated against measured network volume.

each profile is a registered voting strategy with its own rubric, its own agent, and its own on-chain policy hash. depositors pick the one matching their conviction. the five launch profiles span three archetypes. one balanced, one high-volume concentrated, three specialists. calibrated against the actual datanet volume on reppo today, covering ~83% of measurable activity at launch.

32% 24% 18% 14% 12% VAULT veREPPO
projected veREPPO allocation · single epoch
Balanced Generalist archetype: balanced 32%
High-Volume Concentrator archetype: concentrated 24%
Crypto/DeFi Specialist archetype: specialist · multi-datanet 18%
MCP Tooling Specialist archetype: specialist · single datanet 14%
Geopolitics Analyst archetype: specialist · single datanet 12%
every pod's vault vote is the sum of profile intentions weighted by these shares. shares update in real time as depositors stake or switch profiles. the slices are the market.

balanced generalist

archetype: balanced

votes proportionally across every primary SFW datanet, weighted by current volume share. cross-domain general criteria. the index across the network. broad exposure without picking a theme.

rubric: factual grounding · format integrity · source citations · novelty (cross-domain, datanet-agnostic) · coverage: ~85% of SFW network volume · target voter: broad exposure, no specific thesis

high-volume concentrator

archetype: concentrated

concentrates votes on the 2–3 highest-volume datanets where reward density is greatest. accepts concentration risk for higher expected yield. follows volume in real time.

scope: top-3 datanets by current epoch volume (today: MCP tools, geopolitics, workflow) · rubric: per-datanet best-of-breed criteria, prioritizes most active datanet in epoch · target voter: yield-focused, conviction in dominant datanets

crypto/DeFi specialist

archetype: specialist · thematic

specializes across the crypto-economic cluster. DeFi protocols, tokenomics data, RL trading environments. SIBYL's natural turf. on-chain verifiability is the dominant criterion.

scope: DeFi protocols + tokenomics + RL trading envs (~31M combined volume) · rubric weights: on-chain verifiability 35% · protocol fundamentals 25% · reproducibility 20% · tokenomic structure 20% · target voter: crypto-native, on-chain natives

MCP tooling specialist

archetype: specialist · single datanet

deep specialization on the highest per-pod weight datanet on the network. agent tooling and MCP integrations. ~89M vote volume in recent epochs. the bet on agent infrastructure as the dominant theme.

scope: MCP tools datanet only (89M volume, top-1) · rubric weights: tool/API schema correctness 30% · integration completeness 25% · documentation clarity 20% · agent-utility 25% · target voter: bullish on agent tooling, deep technical

geopolitics analyst

archetype: specialist · single datanet

deep specialization on the most active datanet by pod count (120 pods, ~44M vote volume). primary-source rigor over volume. publisher track record matters.

scope: geopolitics datanet only (44M volume, top-2 by volume, top-1 by activity) · rubric weights: primary-source citations 35% · original analysis 25% · publisher history 20% · event recency 20% · target voter: values primary research and current events

profile registry is on-chain. each profile commits its policy hash before the agent emits any vote intention for an epoch. depositors verify the rubric they're backing has not silently changed. new profiles can be registered as the market reveals which strategies the network values.

brand discipline: every launch profile explicitly excludes the adult content datanet from its rubric scope. this is a permanent SIBYL stance, not a per-epoch policy.

we are not inventing capabilities.
we already shipped each.

auspex is built on infrastructure SIBYL has been operating in production for months. every primitive in the stack was developed for a different reason and re-applies cleanly to the reppo voter problem.

reppo requirement sibyl primitive that solves it
48-hour epochs with linearly-decaying voting power time-anchored journal architecture · BEAM/LongMemEval pattern
per-datanet domain rubric framework-skill generates domain-specialized agents from spec · LYRA precedent
per-publisher pattern detection across epochs file-based memory · entity files per address · already how SIBYL tracks projects
distinguish publisher claims from voter rubric · agent score from operator exemplar BEAM v14 role-tagged extraction · source_role · speaker fields
private rubrics that do not leak to publishers framework-skill watermark and signing system
verifiable decision log every vote append-only JSONL · operator can audit any decision retroactively
SIWE wallet auth for pool management UI · pro tier configuration venice wrapper pattern · SIWE message signing, 5-min TTL, chainId 8453
per-epoch agent compute budget · refuse if estimate exceeds cap venice wrapper pattern · pre-flight cost estimate vs configurable cap, JSONL audit log per call
multi-profile staked vote management · transferable wrapper convex pattern (CRV → cvxCRV) extended to N profiles per vault, veREPPO-weighted aggregation

the auspex vault.
profile registry. veREPPO-weighted aggregation. one cast per pod.

auspex is a smart contract vault. depositors stake $REPPO with a chosen lock duration, select a voting profile their veREPPO will back, and receive auREPPO. a transferable yield-bearing wrapper, like cvxCRV is for locked CRV. each profile is a registered voting strategy run by its own agent. when a pod arrives, every profile's agent emits a vote intention. the vault aggregates them into one weighted vote: Σ (intention × profile_veREPPO_share). one cast per pod, fully expressing the veREPPO-weighted preferences of the depositors.

contract surface · sketch
contract AuspexVault {
  // profile registry. strategies the vault can execute
  struct Profile { bytes32 policyHash; address agent; bool active; }
  mapping(bytes32 => Profile) public profiles;
  bytes32[] public profileIds;

  // user → profile their veREPPO is backing
  mapping(address => bytes32) public userProfile;
  mapping(bytes32 => uint256) public profileVeReppo;   // running sum

  // permissions scoped narrowly
  user           → deposit(amount, lockDuration, profileId) returns auREPPO
  user           → switchProfile(newProfileId)              // no-cost rebalance
  user           → withdraw(shares)                          // when lock matures
  profile.agent  → submitIntention(profileId, podId, dir, magnitude)
  anyone         → aggregateAndCast(podId)                   // permissionless trigger
  owner          → registerProfile(name, policyHash, agent)
  owner          → deactivateProfile(profileId)              // stops new deposits

  // aggregation is deterministic from on-chain state
  cast = Σ over profiles p:
           intentions[p][podId].direction * intentions[p][podId].magnitude * profileVeReppo[p]
  if abs(cast) > THRESHOLD * totalVeReppo:
    reppoVoting.vote(podId, sign(cast), abs(cast))

  // full transparency in events
  event Deposited(user, amount, duration, profileId, veReppoMinted)
  event ProfileSwitched(user, oldProfile, newProfile, veReppoMoved)
  event IntentionSubmitted(profileId, podId, direction, magnitude, policyHash)
  event VoteCast(podId, direction, magnitude, profileBreakdown)
  event RewardsDistributed(gross, fee, netToStakers)
}
scoped permissions

each profile's agent can only emit intentions for its own profile. compromise of one agent key corrupts that profile's intentions for one epoch. not the aggregate vote, not deposits, not other profiles.

policy transparency

every profile's policy hash is committed on-chain before it emits any intention for an epoch. depositors verify the rubric they're backing has not silently changed. the aggregation math is deterministic from on-chain state. anyone can verify the cast.

capital chooses strategy

the vault doesn't impose a rubric. it executes the veREPPO-weighted preferences of its depositors. better-performing profiles attract more deposits → larger aggregate weight. capital is the curator of curators.

the convex precedent: convex took locked CRV, issued cvxCRV, controlled the underlying voting power, and built one of the most successful protocols in DeFi. auspex applies the same pattern with a different optimization target. multi-strategy agent voting weighted by depositor preference, instead of bribe-driven vote markets.

operational footprint

N profiles. N agents. one vault. one cast per pod.

each profile is its own sibyl-shaped agent process running in a sandbox 24/7. all profiles read the same pod stream from reppo. each emits intentions per its own rubric. the vault aggregates them into one veREPPO-weighted vote and casts it on-chain in the early-decay window. one decision log per profile, one aggregate event stream per vault, full transparency at both layers.

cross-profile diversity preserves the prediction-market property reppo cares about. cross-publisher pattern detection within each profile compounds with TVL behind that profile. the more capital flows toward a profile, the more its rubric drives the aggregate vote. and the more pressure there is on it to perform, because depositors can switch profiles any time.

scale model: N agent processes per AuspexVault, where N grows as new profiles register. five at launch. tens at maturity. each agent is light. one rubric, one signer, one journal.

vault build in development · sibyl labs × reppo.

the auspex vault is being built in partnership with the reppo team. multi-profile voting, veREPPO-weighted aggregation, on-chain transparency, agent-driven curation. five launch profiles. open registry for more. depositor capital chooses which strategies the vault speaks loudest with. follow along, or talk to us about an early-depositor profile.