bitcoin-l2-citrea
Citrea: first ZK-rollup on Bitcoin (mainnet 27 Jan 2026), zkEVM, BitVM2 trustless bridge, ctUSD stablecoin, native BTC lending. USE WHEN: building zkEVM apps on Bitcoin, integrating with Citrea, evaluating ZK rollups vs sidechains.
What this skill does
# Citrea The first zero-knowledge rollup on Bitcoin. Mainnet activated **27 January 2026**. zkEVM execution + BitVM2-based bridge. Repo: `citrea.xyz`. ## Architecture - **Off-chain execution**: Citrea sequencer runs an EVM (Solidity- compatible) and processes transactions off-chain. - **State commitments**: validity proofs (ZK-SNARKs) posted to Bitcoin. - **Data availability**: tx data also committed to Bitcoin (full rollup, not validium). - **Bridge**: BitVM2-based, **trust-minimized** (does not require federation trust for peg-in/out). ## ZK proof system zkEVM type-2 (compatible with Ethereum bytecode at gas cost of running on Citrea). Validity proof posted with each batch. ## BitVM2 bridge Trust-minimized peg out via BitVM2: - Optimistic challenge model: peg-out claims posted; anyone can challenge. - Challengers can dispute fraud and reclaim funds; honest claims pay out after challenge window. - No federation key custody — bridge security derives from game-theoretic + ZK proof properties. ## Native features - **ctUSD**: native stablecoin on Citrea. - **BTC lending**: native protocols using bridged BTC. - **EVM apps**: any Ethereum dApp can deploy on Citrea (with minimal modifications). ## Compared to other Bitcoin L2s | Aspect | Citrea | Stacks | RSK | Liquid | |--------|--------|--------|-----|--------| | Smart contracts | EVM | Clarity | EVM | Limited | | Bridge | BitVM2 (trustless) | Threshold | Federation | Federation | | Settlement | Validity proofs | Anchored | Merge mining | Federation | | Maturity | 2026 mainnet | 2024 Nakamoto | 2018 | 2018 | | TVL (early) | growing | medium | medium | medium | ## Status (early 2026) - Mainnet active since Jan 2026. - Early ecosystem: ctUSD launched, dApps deploying. - Validator/sequencer set: limited at launch, decentralizing over time. ## Limitations - **New** — limited audit history; bugs likely in early phase. - **Sequencer centralization** at launch (typical for early ZK rollups). - **BitVM2 challenge windows** add latency to peg-out (24+ hours typical). ## Use cases - **DeFi on BTC** with EVM tooling. - **Stable coins** (ctUSD). - **Cross-chain bridge** to Ethereum L2s. - **Long-term**: settlement layer for higher-frequency apps. ## Implementations - **citrea-node** — Rust full node. - **MetaMask compatible** with custom RPC. - **ethers.js, web3.js** work out of the box. ## See also - [bitvm/SKILL.md](../bitvm/SKILL.md) - [strata/SKILL.md](../strata/SKILL.md) - [bsquared/SKILL.md](../bsquared/SKILL.md) - [babylon/SKILL.md](../babylon/SKILL.md) - [stacks/SKILL.md](../stacks/SKILL.md)
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.