P2WSH Adoption

Output share of native SegWit multisig format (BIP141). Specialised use cases: institutional custody and modern Lightning channels.

Tier performanceOn-chain Bitcointechnicalp2wshsegwitmultisigcustodylightning

What is it?

P2WSH (Pay-to-Witness-Script-Hash) is the native SegWit equivalent of P2SH: it allows arbitrary scripts (multisig, timelocks, hash-locked contracts) with the SegWit fee discount thanks to the separated witness. This metric measures the 1-week rolling share of P2WSH outputs among all created outputs. Adoption is more modest than P2WPKH because it is reserved for institutional multisig and modern Lightning infrastructure uses.

How to read

The P2WSH share evolves at a modest but structural level. Growth reflects institutional adoption (multisig custody solutions) and the expansion of the Lightning Network ecosystem with P2WSH-anchored channels. Prolonged stability indicates a plateau of saturated specialised uses.

Key zones

Zero adoption pre-SegWit (August 2017). Phase 1 post-activation: very slow start (few compatible wallets). Phase 2 (2018-2021): slow growth with the arrival of Lightning and institutional custody solutions. Phase 3 (post-2021): plateau level, P2WSH becomes a stable niche use.

What to observe

Watch the correlations with Lightning Network expansion (total capacity, number of channels). A P2WSH acceleration can accompany anchored Lightning channel deployments. Also compare with P2SH (#366) - a P2SH decline with P2WSH growth suggests migration of multisig uses to native SegWit formats.

Historical context

P2WSH arrived with BIP141 SegWit (24 August 2017) but its adoption was much slower than P2WPKH. The Lightning Network deployment with anchor outputs (2021) increased its use. Multisig custody solutions migrated to P2WSH in the second half of the 2010s.

Expert notes

P2WSH has been partly supplanted by Taproot (#369-#371) for advanced multisig uses thanks to Schnorr aggregation (MuSig2) which allows expressing multisig as a single signature, saving fees and privacy. The stable P2WSH share reflects institutional deployments prior to Taproot, with migration inertia on custody wallets.

Common mistakes to avoid

A low P2WSH share does not mean low multisig adoption on Bitcoin - many multisigs remain on P2SH (legacy compatibility) or have migrated directly to Taproot (MuSig2). To assess overall multisig adoption, cross-reference P2WSH with the P2SH multisig share (sub-category not isolable in output aggregates) and Taproot keypath spends.

Programmatic access

REST API

curl -sS \
  'https://api.trinityinsights.io/api/v1/onchain/p2wsh-adoption/history?days=90' \
  -H 'X-API-Key: $TRINITY_API_KEY'

MCP server

{
  "tool": "get_chart_value",
  "metric_id": "p2wsh-adoption",
  "timeframe": "1y"
}

Required tier: performance. See the pricing grid for the tier list and the MCP documentation for multi-client configuration.

Related metrics

Institutional disclaimer

Trinity Insights is an educational and analytical tool. The metric above does not constitute investment advice. Trinity Insights is not a Crypto-Asset Service Provider (CASP) registered under MiCA Regulation (EU) 2023/1114. See the full disclaimer.