Protocol Dashboard
Live state from OPNet on-chain contracts ·
op1shield...pool🔴 Live Pool Metrics
Block #0000000
0.00
Total Value Locked (BTC)
▲ +0.00%
0.00
Active Coverage (BTC)
▲ +0.00%
0
Active Policies
▲ +0 today
0.00%
LP Annual Yield
▲ +0.00%
Pool Utilization0%
Pool Health
85%
HEALTHY
Reserve Ratio: 1.42x
Treasury
0.00
Balance (BTC)
LP Distribution (70%)0.00 BTC
Treasury Cut (20%)0.00 BTC
Validators (10%)0.00 BTC
SHIELD Token
0.0000
Price (BTC)
Total Supply21,000,000
Circulating0
Your Balance0
On-Chain Activity
LIVE
INITProtocol booting...
Claim Statistics
0
CLAIMS PAID
0
CLAIMS DENIED
0
PENDING
0.00
BTC PAID OUT
Buy Coverage
Purchase on-chain insurance policy · OPNet MCP
InsurancePool.buyPolicy()
Each policy is a unique on-chain asset following the OPNet native asset model. Policies are transferable and fully verifiable on Bitcoin L1 via OPNet nodes. Smart contract reference: https://ai.opnet.org/mcp
Policy Configuration
BTC
Min: 0.01 BTC · Max: pool limit
Coverage Terms
Trigger TypeOracle + Governance
Claim Window72 hours post-event
Payout Speed~3 blocks after approval
Policy TypeNon-Fungible OPNet Asset
Transferable✓ Yes
On-Chain Audit Log✓ Yes
Double-Claim Guard✓ Enabled
Pool Capacity
Used Coverage0%
Pool Total Liquidity0.00 BTC
Available Coverage0.00 BTC
Reserve Locked0.00 BTC
Your Coverage Request0.00 BTC
My Policies
Your on-chain policy assets · OPNet native asset model
Connect your OPNet wallet to view your policies. Each policy is a unique on-chain asset stored in your op1... address.
Submit Claim
OPNet on-chain claim resolution ·
ClaimModule.processClaim()Claim Submission
False claims trigger slashing. Fraudulent submissions forfeit 10% of policy value to the treasury. Malicious governance voters are slashed.
Provide Bitcoin L1 tx hash showing the exploit/event
BTC
Must not exceed your policy coverage amount
Claim Resolution Flow
1
Submission
Claim deployed to OPNet contract. Double-claim check runs.
2
Oracle Verification
On-chain oracle checks event conditions against verified feeds.
3
Governance Vote
SHIELD holders vote. Quorum: 10%. Malicious voters slashed.
4
Payout / Rejection
Approved → BTC transferred on L1. Denied → fraud penalty applied.
Security Flags
Double-Claim Guard✓ ACTIVE
Fraud Detection✓ ACTIVE
Slashing Logic✓ ENABLED
Circuit Breaker✓ CLOSED
Capital Lock144 blks
Reentrancy Guard✓ ENABLED
Active Claims
| Claim ID | Policy | Type | Amount | Block | Status | Action |
|---|---|---|---|---|---|---|
| No claims found | ||||||
Provide Liquidity
Earn yield as insurance LP ·
InsurancePool.depositCapital()Deposit Capital
BTC
PROJECTED ANNUAL RETURN
0.00000
BTC / year (estimated)
70% Premium Share
APY (current)0.00%
Lock Period144 blocks (~1 day)
Your Pool Share
Withdraw Capital
Capital locked for 144 blocks (~1 day) after deposit. Emergency circuit breaker may extend lock period during insolvency events.
BTC
Your deposited balance: 0.00 BTC
Pool Statistics
Total Liquidity0.00 BTC
Active Coverage0.00 BTC
Reserve Amount0.00 BTC
Utilization Ratio0%
Solvency ScoreHEALTHY
LP Count0
Utilization0%
Tokenomics Distribution
70% → Liquidity Providers
20% → Treasury
10% → Claim Validators
Distribution is automatic — executed inside InsurancePool.buyPolicy() on every premium payment. No admin control. Fully on-chain.
LP Positions
| Provider | Deposited | Pool Share | Earnings | Lock Expires | Status |
|---|---|---|---|---|---|
| No LP positions | |||||
On-Chain Governance
SHIELD token holders vote · No admin override ·
Governance.castVote()0
Active Proposals
0
Your Voting Power
10%
Quorum Required
Create Proposal
Proposer must hold ≥ 1,000 SHIELD tokens. Proposal bond: 100 SHIELD (returned if quorum reached). Voting period: 2,016 blocks (~2 weeks).
Active Proposals
Smart Contracts
OPNet AssemblyScript source · Generated using OPNet MCP Smart Contract Reference:
https://ai.opnet.org/mcp
All contracts below are written in AssemblyScript → WebAssembly for deployment on Bitcoin L1 via OPNet.
Runtime: @btc-vision/btc-runtime · Standard: OP_20 · MCP Reference: https://ai.opnet.org/mcp