Nunchuk primary-source snapshot

Fetched: 2026-04-28 UTC

1) Official homepage

Source: https://nunchuk.io/

Selected excerpts from the official site:

The first Bitcoin inheritance solution designed to outlive the company that created it.

Built on the most advanced multisig platform. Trust-minimized. Zero KYC.

Secure your legacy with the most advanced non-KYC inheritance service. Our on-chain timelocks guarantee execution (even if Nunchuk ceases to exist)

Additional signals from the source:

  • The homepage is unusually explicit that inheritance is central to the product, not an add-on.
  • It also mixes consumer-wallet, collaborative-custody, and inheritance language on the same surface.
  • The “outlive the company” framing is a strong clue that the trust model is part of the product identity.

2) Platform explainer

Source: https://nunchuk.io/platform

Selected excerpts from the official site:

Nunchuk was created to solve exactly these problems. To bring down the barrier of entry to multisig, and to create an easy way for Bitcoiners to pass on their wealth.

Nunchuk pioneers the use of a dedicated inheritance key

A spending limit restricts the platform key to only co-sign transactions that don’t exceed the spending limit for a given period.

Additional signals from the source:

  • This page is the clearest explanation of the product architecture and why Nunchuk exists.
  • It makes inheritance a first-class design principle alongside multisig usability.
  • The platform-key policy language shows Nunchuk has a real custody-control-plane layer, not just wallet UI.

3) Inheritance page

Source: https://nunchuk.io/inheritance

Selected excerpts from the official site:

Introducing the first autonomous inheritance solution, designed to outlive us.

We can’t move your bitcoin. We hold only one key in your wallet

After the timelock expires, the wallet’s rules automatically change on-chain: our Platform Key is removed, and the signing requirement drops.

Additional signals from the source:

  • This page is the strongest source for the actual inheritance trust model.
  • It explicitly describes on-chain rule changes, beneficiary/trustee options, and the separation between Nunchuk support and beneficiary sovereignty.
  • The references to BSMS files and seed phrases are also high-signal: Nunchuk preserves a self-sovereign recovery path outside the company’s service layer.

4) Advisor / Byzantine page

Source: https://nunchuk.io/byzantine

Selected excerpts from the official site:

share custody via multisig wallets

Clients retain full control of their bitcoins, while you hold a backup key.

plan your legacy

Additional signals from the source:

  • Byzantine shows Nunchuk has an advisor- or professional-facing collaborative-custody product, not only a retail wallet.
  • The copy suggests Nunchuk is trying to become infrastructure for client-service practices around long-term Bitcoin custody.
  • This expands the project beyond “inheritance app” into a broader collaborative-custody operating model.

5) FAQ / support surface and sitemap

Sources:

Selected excerpts / signals from the official sources:

FAQ

Services For individuals For families & groups For advisors

Additional signals from the sources:

  • The FAQ confirms Nunchuk’s product segmentation across individuals, families/groups, and advisors.
  • The sitemap is especially useful because it reveals product surfaces that are easy to miss from the homepage alone: inheritance, platform, advisor product pages, agent-related blog posts, reproducible-builds content, and Miniscript-focused educational material.
  • This is a good example of a product where the sitemap itself is a meaningful primary-source discovery tool.

6) Public GitHub org, resources repo, and CLI repo

Sources:

Selected excerpts from the public sources:

Nunchuk FAQ and Knowledge Base website

A command-line tool that lets AI agents use Bitcoin safely.

Agents operate within group wallets and miniscript wallets where user keys retain ultimate control

Additional signals from the sources:

  • The GitHub organization reveals a broader operational footprint than the marketing site alone: wallet apps, docs, CLI tooling, resources site, platform policy tooling, and agent-skills.
  • The CLI repo is particularly high-signal because it exposes miniscript wallets, wallet export/recovery, invitation flows, platform-key policies, dummy transactions for policy approval, and AI-agent integration intent.
  • The resources repo confirms that the FAQ/support site is maintained as a first-party knowledge-base property rather than an informal community wiki.

7) Developer portal

Source: https://developer.nunchuk.io/

Selected signal from the official source:

  • The developer portal currently exposes minimal rendered text via lightweight fetch, but its existence lines up with the CLI’s requirement for a Nunchuk API key and supports the view that Nunchuk is building a developer-accessible platform layer beyond the end-user wallet.

Notes

  • Nunchuk appears best cataloged as Bitcoin multisig wallet / inheritance planning / collaborative custody / advisor-facing custody control plane.
  • No canonical standalone whitepaper or litepaper surfaced in this pass.
  • The highest-signal categorization clues are the dedicated inheritance-key model, on-chain timelock activation, configurable platform-key policies, advisor-facing collaborative-custody product, and the public CLI / automation surface.