Skip to content

Add OP_NET (Bitcoin L1) feasibility study#34

Closed
TaprootFreak wants to merge 4 commits into
developfrom
feat/opnet-feasibility-study
Closed

Add OP_NET (Bitcoin L1) feasibility study#34
TaprootFreak wants to merge 4 commits into
developfrom
feat/opnet-feasibility-study

Conversation

@TaprootFreak

Copy link
Copy Markdown

Summary

  • Complete technical feasibility study for deploying JuiceDollar on OP_NET (Bitcoin L1 smart contract platform)
  • Covers platform capabilities, critical analysis of WBTC trust model, challenge mechanism viability, and peg stability
  • Identifies three fundamental blockers and proposes solutions for each
  • Provides four actionable options with technical trade-offs

Key Findings

  • Smart contract logic is ~85% portable (AssemblyScript/WASM has all required primitives)
  • WBTC on OP_NET is controlled by a single-key custodian (no multisig, no timelock, no proof-of-reserve)
  • Challenge mechanism has 60x coarser price discovery on 10-minute blocks and is economically unviable at low TVL
  • No peg stabilization possible without stablecoins on OP_NET
  • Recommendation: Wait for OP_LINK trustless bridge and OP-20S stablecoins before active development

Document Structure

  1. Executive Summary
  2. Project Context (JUSD + OP_NET)
  3. Technical Analysis: Platform Capabilities (gas, storage, cross-contract, events, math, crypto)
  4. Critical Analysis: Collateral Model (WBTC code review with code excerpts)
  5. Critical Analysis: Challenge Mechanism (price discovery, economics, MEV, volatility)
  6. Critical Analysis: Peg Stability
  7. Ecosystem Analysis
  8. What Works — Technically Feasible Components
  9. What Doesn't Work — Fundamental Limitations
  10. Risk Assessment
  11. Effort Estimation
  12. Four Actionable Options (MVP, Wait, Hybrid Design, No Deployment)
  13. Recommendation
  14. Appendix (comparison tables, contract interfaces, references)

Test plan

  • Review document for technical accuracy
  • Verify all code references against source
  • Review by team for strategic alignment

Complete technical feasibility analysis for deploying JuiceDollar
on OP_NET, a Bitcoin L1 smart contract platform. Covers platform
capabilities, WBTC trust model code analysis, challenge mechanism
viability on 10-minute blocks, peg stability without stablecoins,
and four actionable options with technical trade-offs.
- Corrected challenge mechanism analysis: 144 price ticks/day is
  sufficient (more than Aave, Compound, Liquity), MEV-resistant by
  design, economically viable (~9k JUSD per 10 BTC challenge)
- Added JuiceBTC (jBTC) solution: custom OP-20S token with 3-of-5
  multisig, timelock, rate-limit, no burnFrom, trustless PSBT deposit,
  Bitcoin script timelock withdrawal fallback
- Updated executive summary, risk assessment, and recommendation
- Changed from "wait and see" to "proceed with MVP implementation"
- All 7 core values preserved (oracle-free, censorship-resistant,
  self-custody, code-is-law, permissionless, trustless, veto-governance)
- Replace custom JuiceBTC token with time-limited multi-collateral
  system using existing OP_NET WBTC (expiration + mint limit)
- Add AuxPoW vs BitVM2 comparison (Section 4.3)
- Reduce MVP from 4 to 3 contracts (JUSD, MintingHub, Position)
- Same pattern as StartUSD bootstrap on Citrea: temporary collateral
  with known risk profile, organic migration to trustless BTC
- Protocol remains fully trustless; only initial collateral is bounded
Detailed spec covering:
- Architecture with 3 contracts (JUSD, MintingHub, Position)
- Full method interfaces for all contracts
- Storage layout with pointer allocation
- Event definitions within 352-byte limit
- Cross-contract call patterns with SHA-256 selectors
- Protocol parameters (fees, rewards, periods, limits)
- Deployment plan (5-step sequence, testnet first)
- Testing strategy (unit, integration, edge cases)
- Repository structure for JuiceDollar/opnet-contracts
TaprootFreak added a commit that referenced this pull request May 26, 2026
Replace FTP-Deploy-Action targeting All-Inkl with wrangler-based Direct
Upload to Cloudflare Pages, matching the prd.yaml change from #128/#69/#34/
#16/#39/#45/#8.

Pages project: juicedollar-docs-dev (production_branch=develop). Paired with a Terraform
change in DFXServer/server that creates the project and switches the
dev.* DNS record.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant