[2602 Grant] TYKORA — Prize Vaults for DoC & USDRIF (Tropykus Yield) on Rootstock

Grants & Incentives
21

[2602 Grant] Proposal Milestone update - TYKORA Prize Vaults for DoC & USDRIF (Tropykus Yield) on Rootstock

Hi everyone

We’d like to share an update on the proposed milestones for our grant submission TYKORA based on community feedback. Specifically in Milestone 2.

Grant Request

Total amount requested: 20,000 USDRIF (or rBTC equivalent)

Milestone breakdown (deliverables + dates + amounts)

Timeline is expressed as “weeks from grant approval” to avoid calendar mismatch.

Milestone 1 — Independent security audit (Coinspect)

Duration: 2 weeks (Weeks 1-2)

Amount: 12,000 USDRIF (or rBTC equivalent)

Note: The 12,000 USDRIF budget corresponds to the quoted Coinspect audit fee for the TYKORA smart-contract scope.

Deliverables

Formal engagement with Coinspect for an independent audit of TYKORA Prize Vault smart contracts (DoC + USDRIF)

Audit-ready package:

  • Tagged release / exact commit hash
  • Deployment & build instructions
  • Complete test suite
  • Audit report publication (executive summary + technical details as permitted)

Remediation cycle:

  • Fixes applied
  • Expanded tests
  • Re-verification and final tagged audited release

Success metrics / KPIs:

  • Audit report delivered
  • 100% findings fixed or explicitly documented with mitigation/risk acceptance
  • Final audited release tagged and publicly available

Milestone 2 — Production mainnet launch & operational enablement

Duration: 4 weeks (Weeks 3–6)

Amount: 3,000 USDRIF (or rBTC equivalent)

Deliverables

Transition from Sandbox mode → Production mode for both vaults (DoC + USDRIF) on Rootstock mainnet

  • Disable any sandbox caps and enable production parameters (if applicable)
  • Final parameters locked + keeper runbook + monitoring + verified addresses page

Operational enablement:

  • Keeper procedures (close → award → claim)
  • Monitoring guidance + operational runbook
  • Documented parameters and safety conditions (splits, draw timing, constraints)

Public launch package:

  • Verified contract addresses + explorer references consolidated
  • Onboarding docs (“How it works”), FAQs, risk disclaimers
  • Documentation aligned with audited code

Success metrics / KPIs:

  • Production mode enabled
  • Keeper lifecycle executed end-to-end on mainnet with a published runbook
  • Launch documentation published with verified references

Admin / Controls (Production)

  • Deployment-time configuration (performed by the team at deployment):
    • setStrategy(address) — executed during deployment; one-time / not changeable after set
    • setTreasury(address) —executed during deployment; one-time / not changeable after set
  • Production owner: a Safe multisig on Rootstock with threshold M-of-N
  • Production admin surface (multisig-controlled):
    • setEmergencyMode(bool) — emergency switch (blocks deposits + draw ops; withdrawals remain available)
    • awardDrawManual(drawId, seed) — manual award fallback (exception path only)
    • emergencyCancelDraw(drawId) — cancel/unlock in stuck cases after emergencyDelay
    • startFenwickRepair() / continueFenwickRepair(steps) — repair tooling (rare, only if needed)

(We’ll also explicitly note that key economic parameters like draw period and bps are immutable in the deployed vaults, and strategy routing is not upgradeable after the one-time set.)

Ops SLOs (Measurable)

  • Execution liveness: ≥ 95% of draws finalized within 24h of scheduled end when BTC header data is available.
  • Manual intervention ceiling: ≤ 5% manual interventions over a rolling 90-day window.
  • Disclosure SLAs (whenever manual paths are used):
    • brief public notice within 24h
    • short follow-up explanation within 72h (reason + confirmation that the randomness commitment was not manipulated)

Runbook Artifacts

Milestone 2 will explicitly include:

  • a Verified Addresses page (vaults, strategies, underlying tokens, multisig owner, keeper addresses)
  • a Monitoring checklist (events + keeper txs + BTC header readiness + draw state transitions)
  • where Postmortems/Disclosures publication: We will publish a canonical incident log in TYKORA Docs (permalink, timestamped, with tx hashes). Fast notifications will be shared via Telegram linking to the canonical report. That links to the same docs entry. All of these references will be linked from the Verified Addresses page.

Milestone 3 — Liquidity & adoption activation (TVL impact)

Duration: 4 weeks (Weeks 7–10)

Amount: 5,000 USDRIF (or rBTC equivalent)

Deliverables

Activation plan executed to drive liquidity and sustained participation:

  • Coordination with Rootstock ecosystem channels and key communities (DoC/MoC, USDRIF stakeholders, Tropykus)
  • Educational content (tutorials, demos, explainers) to reduce onboarding friction

KPI reporting during the activation period:

  • TVL per vault (DoC + USDRIF)
  • Number of depositors
  • Yield routed through Tropykus attributable to TYKORA
  • Draw participation metrics + prize distribution transparency

Success metrics / KPIs:

  • Public KPI report(s) with verifiable metrics (TVL, depositors, retention proxy, Tropykus supplied liquidity)
  • Evidence of measurable post-launch growth (TVL and/or depositors and/or Tropykus utilization uplift)

Thanks,

JXLabs Team

2 Likes
22

Hi @Tane , thanks for the clear guidance.

We’ve updated the thread with [2602 Grant] Proposal Milestone update - TYKORA Prize Vaults for DoC & USDRIF (Tropykus Yield) on Rootstock to explicitly include in Milestone 2:

  • Admin/controls: production owner as a multisig (M-of-N threshold), and a clear list of owner/admin functions used for resiliency.
  • Ops SLOs: ≥95% draw finalization within 24h (when BTC header data is available), ≤5% manual interventions / 90d, plus the 24h + 72h disclosure SLAs.
  • Runbook artifacts: a Verified Addresses page, monitoring checklist, and where incident disclosures/postmortems will be published (TYKORA Docs + Telegram announcements, with links from the Verified Addresses page).

Really appreciate the feedback — it helped tighten the proposal for on-chain evaluation and accountability.

Happy to provide any additional details if needed.

JXLabs team

3 Likes