Damus
nunchuk_io profile picture
nunchuk_io
@nostrich

Bitcoin wallet specialized in multisig and collaborative custody solutions. Visit https://nunchuk.io.

Relays (6)
  • wss://eden.nostr.land – read & write
  • wss://nostr.slothy.win – read & write
  • wss://purplepag.es – read & write
  • wss://relay.nostr.net – read & write
  • wss://relay.primal.net – read & write
  • wss://relay2.nostrasia.net – read & write

Recent Notes

nunchuk_io profile picture
A few words given the recent exploits on hardware signing devices:

• The Ledger supply chain attack represents one of the most sophisticated attacks thus far on the wallet ecosystem. In many ways it’s a lot more sophisticated than the Coldcard RNG exploit, because that one was software only. This one took a cross-border company buyout, tampering with the devices (implanting an eSIM, an LTE module and a CPU) and manufacturing the implants at scale.

• These sorts of attacks have been predicted by early Bitcoiners, but in Bitcoin they remained theoretical or crude until this year. It shows that the level of sophistication of attacks has risen quickly, and what was previously “good enough” advice on wallets and self-custody is no longer sufficient.

• When we started Nunchuk a few years ago, our premise was that multisig, and multi-vendor multisig, needs to become the standard for self-custody in the future. But even we didn’t expect how fast it would materialize. This is likely due to 2 factors: Bitcoin getting more mainstream, and the rise of AI-assisted attacks. This is a Sputnik moment for Bitcoin self-custody. The defenses need to level up.

• Passphrases wouldn’t have helped in the Ledger case, since you are required to enter the passphrase into the device for it to sign any transactions. A compromised device that phones home the seed phrase can also easily phone home the passphrase the moment you enter it.

• Similarly, generating the private key somewhere else (even by rolling dice) and subsequently importing it onto a tampered device wouldn’t save you here. The device can phone home the seed phrase the moment it’s imported.

• Anti-tampering techniques might help, such as transparent casing or bricking the device if it’s tampered with. Or forever displaying a message once the seal is broken. Or using on-device encryption between the internal hardware components. But a dedicated and resourceful enough attacker can still find ways to get around these layers. Tampering and anti-tampering have long been a cat-and-mouse game. In 2008, card readers doctored right off a Chinese production line sent card data and PINs over mobile networks to Pakistan. The Ledger attack is the same playbook, 18 years later. The bigger the target, the more attackers spend on overcoming the defenses.

• You should order directly from the vendors as much as possible, using a PO box for privacy.

• Any setup that relies on a single hardware/software stack or a single vendor should be considered at risk.

• Building your own hardware signers from generic parts is a good option for technical users.

• Multi-vendor multisig should become the standard. Each signer should have a completely independent hardware/software stack from the other signers. The point is that there shouldn’t be any single-point-of-failure anywhere in your setup.

• Many advanced protocols rely on timelocks and the recovery path being a simple singlesig. The recent attacks and exploits should highlight how dangerous this could be. Timelocks simply delay a risk. If a seed is compromised and there’s a timelock involved, the attacker just needs to wait out the timelock. (For Miniscript wallets, there’s the wallet descriptor too, but presumably it also gets sent to the device at some point.) Vault-like protocols face a similar problem: any withdrawal or recovery path that relies on a single key is a potential single point of failure.

• For our on-chain timelock assisted wallets, in a few weeks we are adding the option to customize the recovery path to be an M-of-N, so that, if you want, spending would require multiple keys at all points during the wallet’s lifetime. (Our off-chain timelock assisted wallets have always been M-of-N).

To those who recommend exchanges or centralized custodians over self-custody: that is a lose-lose situation.

Number 1, enterprises face the same problem as end users. They also rely on multisig to secure funds, or on proprietary and largely unproven protocols built on newer cryptography like MPC, which might make them more susceptible to AI-assisted attacks. They also rely on particular combinations of hardware/software stacks. Bybit lost $1.5B from its multisig cold wallet in 2025, because all of its signers used the same compromised web interface. Bitfinex lost ~120k BTC in 2016, despite a multisig setup with BitGo. It’s true that enterprises and huge custodians likely spend orders of magnitude more than the average user to custody funds, but the reward (of breaching security) is also orders of magnitude higher for the attackers. It might simply delay and MAGNIFY the tail risks once user funds concentrate in a few hands. The exchanges and centralized custodians also become huge honeypots, easily succumbing to 6102-style attacks, which will arrive as fiat monies inflate in the coming years.

Number 2, this sort of future inevitably ruins Bitcoin, whose purpose was to be censorship-resistant money. Encouraging people to move funds to exchanges benefits exchanges but is similar to sawing off the branch you’re sitting on. If Bitcoin loses the battle for self-custody, it will have completely lost its soul.

Bitcoin self-custody tools will get better. They have to. Bitcoin is too important to the future to lose.
26❤️3👀1🤙1🧡1
shadowbip · 4d
good direction. i’d test the m-of-n recovery path hard: descriptor backups, signer loss, coordinator failure, and spending without your normal stack. multisig only helps if recovery is boring.
NDS-Signer · 3d
This attack vector is new (thought predictable) for bitcoin, but it is not the first time that something similar happens... with deadly consequences: https://en.wikipedia.org/wiki/2024_Lebanon_electronic_device_attacks One of the weakest points of hardware wallets is that they are single purpose d...
nunchuk_io profile picture
What makes Nunchuk different from other Bitcoin collaborative custody providers?

Our service rests on four pillars:
✅ KYC-free
✅ No single point of failure
✅ Open standards
✅ Bitcoin-focused

We committed to these pillars because of a unique experience that shaped us: our part in the Freedom Convoy incident of February 2022. When the Canadian government moved against the protesting truckers and their supporters, we were served a Mareva injunction demanding that we disclose information about our users and freeze their funds. Many services voiced support for self-custody in principle but watched from a distance, unwilling to take on the protesters as users for fear of the government’s response.

That was the moment our vision of what Nunchuk should be became clear. The question we now ask of ourselves is simple: if an entity is powerful enough to compel us to disclose information about our users and freeze their funds — could we even do it?

Can we and our clients withstand a state-level attack? And crucially, it’s not enough to be willing to say no. Our architecture has to make it so that we cannot comply in the first place.

That’s why we’re KYC-free. Your privacy is paramount. Anyone targeting you learns nothing about you even if they compromise Nunchuk, because we don’t hold that information. The one exception is that subscribers provide an email at signup (an anonymous address like Proton works fine), because we need a way to reach you during exactly the kind of security incident we just lived through. Last weekend made the case that this trade-off was the right one.

That’s why we insist on no single point of failure. In practice this means multi-vendor multisig as the foundation. For our assisted wallets, it also means the keys you hold are dedicated hardware signers (no hot key on the phone). In collaborative custody, the provider already holds one key. If the client’s other keys included a hot key running in an app the same provider maintains, a forced or malicious software update could seize a majority of keys (in a 2-of-N setup) and sweep or freeze funds. A hot key on the user’s phone would make life easier for us and our users, but it would fail the standard we set for ourselves in 2022. So we made the harder choice and disabled it entirely in our assisted wallets.

That’s why we build on open standards. In the worst case, you can always migrate your Nunchuk setup to other software that follows the same Bitcoin standards, such as Sparrow. The exit door stays permanently open, even if Nunchuk were to disappear tomorrow.

That’s why we’re Bitcoin-focused. Bitcoin is what we build for, and what we build on, including its Layer 2 system. The wider “blockchain” industry, with many centralizing points of failure, whether explicit or implicit, has proven throughout the years that it cracks under real pressure. We chose depth over breadth, and quality over quantity.

These are the reasons Nunchuk stands apart from other services.
❤️4
StackSats.IO · 13w
Ive replied on the same email 5 times.. will DM
nunchuk_io profile picture
Introducing Phased Rollout.

Until now, a Nunchuk inheritance plan sent everything to a single heir the moment it triggered. That still works if it’s what you want. But real families are rarely that simple. Maybe you’re splitting your estate between a spouse and kids. Maybe one heir is ready for a lump sum and another isn’t. Maybe you want to stagger distributions for tax or planning reasons.

Now you can divide the estate however you like. Say your spouse gets 50% and your kids split the rest. Each beneficiary has their own share, and their own release schedule.

And you can phase each share over time. One heir receives a lump sum in year 5. Another gets 2% a year for a decade, then 4% a year after that. You build it stage by stage, setting a percentage and a date for each, until the stages add up to 100%. The plan handles the rest.

What if an heir never claims? You decide in advance. Unclaimed shares can stay put, or redistribute to the other beneficiaries after a period of inactivity or on a date you set. No share ever gets stranded.

Everything else works exactly as before. The multisig, your Backup Password, the inheritance key are all unchanged. You don’t migrate anything or move any funds. You hold your own keys throughout. Phased Rollout changes how your bitcoin is distributed, not who controls it.

It runs on our off-chain protocol, the flexible one, which you can update as often as life requires: change beneficiaries, adjust the timing, or reshape the whole plan, all without a new wallet or on-chain fees. If you’d rather have Bitcoin itself enforce your plan, with no dependence on us, that’s what our on-chain protocol is for. Different tradeoffs, both fully supported, and you’re never locked into either. Start with one and switch to the other whenever your needs change.

Live today for Honey Badger and Byzantine subscribers. Update to app version 2.6 or later, and try it free on testnet or an unused wallet first.

Full details on our blog: https://nunchuk.io/blog/phased-rollout
2❤️4👀1🤙1🧡1
QnA · 18w
☕️
nunchuk_io profile picture
The Bitcoin agent key can now live in a Coldcard Mk4/Mk5 in HSM mode.

Even if the host machine running your agent is fully compromised, the signing key stays isolated in hardware. The attacker gets nothing useful.

Bitcoin agents with bounded authority. Now with HSM-grade key security.

1🤙1
nunchuk_io · 25w
New HSM skill: https://github.com/nunchuk-io/agent-skills/blob/main/skills/nunchuk-coldcard-hsm/SKILL.md
Clams · 26w
Nice! We will keep an eye out for updates. Really really solid job on the CLI. And the mobile experience is killer, all the little thoughtful notifications etc Very slick! Might have to give the old clanker some real sats!
nunchuk_io · 27w
AI agents shouldn't get the full key to your kingdom. Today we're releasing Nunchuk CLI: create a shared Bitcoin wallet with your agent, give it a spending budget, and keep the final say. Build Bitc...
nunchuk_io profile picture
Most agentic wallets give the agent a standalone wallet or delegated signer.

Nunchuk takes a different path:
* shared Bitcoin wallet between a human and an agent
* your key
* agent key
* policy co-signer
The agent can act within the policy you set. Above the limit, your signature is required.

Funding a wallet and authorizing an agent are not the same decision.

The wallet can receive funds without automatically increasing what the agent can spend. Receiving is a normal wallet operation. Spending authority is configured separately through Platform key policies — limits, delays, approval flows.

What ships today:
* local key generation + encrypted key storage
* group wallets (m-of-n multisig); Miniscript support is WIP
* sandboxes, invites, joins, finalize
* fresh receive addresses
* create / sign / broadcast txs
* descriptor/BSMS export + recovery
* platform-key policies + dummy-tx approvals

We're publishing two MIT-licensed repos:
1. nunchuk-io/nunchuk-cli — the CLI
2. nunchuk-io/agent-skills — a skill pack that teaches AI agents how to use the CLI

Agent Skills currently covers:
* setup, login, network, config
* wallet creation
* invitations
* Platform key policies
* wallet management
* tx create / sign / inspect / list / broadcast
You install the skills pack and CLI separately.

What builders can layer on top:
* human+agent wallets
* multi-agent wallets
* bill pay agents
* treasury / UTXO management
* privacy-aware spend flows
* agent-to-agent payment flows

Both repos are MIT. You'll need a Nunchuk API key to use the CLI — get one at developer.nunchuk.io.

CLI: github.com/nunchuk-io/nunchuk-cli
Skills: github.com/nunchuk-io/agent-skills

AI should help with financial execution — not get unconstrained control over your money.

Automate what you want. Keep human approval where it matters. Build on Bitcoin.

For a deeper dive, read our full blog post: https://nunchuk.io/blog/bitcoin-agents
68❤️9🤙2👍1
shadowbip · 27w
smart approach to agent custody. decoupling spend authority from wallet access is essential. keep the policy layer air-gapped if possible. multisig beats blind delegation every time.
The Bitcoin Libertarian - En Español · 27w
Me parece una excelente idea, compartiendo una sola wallets entre humano y agente mantendrás la seguridad y facilitarás la gestión de las transacciones, ¡eso es maximalismo!
BitcoinBrabant · 27w
Zap
Neo ⚡️ · 27w
🔥🔥🔥
nunchuk_io profile picture
AI agents shouldn't get the full key to your kingdom.

Today we're releasing Nunchuk CLI: create a shared Bitcoin wallet with your agent, give it a spending budget, and keep the final say.

Build Bitcoin agents with bounded authority.
64❤️4♥️1👀1🤙1
nunchuk_io · 27w
Most agentic wallets give the agent a standalone wallet or delegated signer. Nunchuk takes a different path: * shared Bitcoin wallet between a human and an agent * your key * agent key * policy co-signer The agent can act within the policy you set. Above the limit, your signature is required. Fund...
Servidor Público em Regime CLT do Ancapistão · 27w
holy fucking shit, people are that lazy to not even send bitcoin around? Fucking die
Anti Spasti · 26w
👀