> Even if we had to walk from the Bootstrap service literally any other Pub could provide that.

Yes, this is a key design thing if you need the service for bread or even to get some traction: you need to be able to wind down and walk, not be a ticking time bomb. Just having a plan for it puts one ahead of 99% of the things that are out there, including some of the frequently shilled ones that are in fact cringey.

I mean all this is assuming that being a spook is out of the question of course. haha.

Yea hopefully ShockWallet isn't as moronic in hindsight as Snacks/Scamourai turned out to be... one thing I made sure it never does is create chain transactions... can't pay OFAC blacklisted addresses if you don't create chain transactions. Zeus and Boltz can have the swap business. Even if we had to walk from the Bootstrap service literally any other Pub could provide that.

> I'd work on a protocol.

Maybe I'll throw a draft in a repo at some point, if there's enough brainpower interested in solving this implementations may just pull themselves together from the nudge.

justin_shocknet

at what point would we be liable for signing transactions that are verboten?

The moment an Iranian in the US or Russian in the EU gets picked up and they have a bookmark to a wallet that leads to you, especially if you have touched half a hockeystick at that point. Then you're instantly everyone's new fav batty boi and your lawyers are going to laugh all their way to the bank, back to you, and all the way to the bank again, while your desperate attempts to comply will completely destroy your reputation and make affected people really, really angry. I've seen that happen twice as an insider now, once on each side of the Atlantic. Same outcome too; it's funny how playbooks that work tend to be passed around.

This is why the state of things is so bad.

I think that solutions can be found in the optional/bootstrap service, like you have for shockwallet. You can walk. This worked for wasabi too, though less optimal because from what birdies told me at the time, snacks wasn't prepared.

It can defo be done. I'd work on a protocol. Not on the service implementation. That makes it a hobby thing tho.

Design

bitcoin

Brainstorming Bitcoin disaster recovery businesses

npub1zapsats

> at what point would we be liable for signing transactions that are verboten?

The moment an Iranian in the US or Russian in the EU gets picked up and they have a bookmark to a wallet that leads to you, especially if you have touched half a hockeystick at that point. Then you're instantly everyone's new fav batty boi and your lawyers are going to laugh all their way to the bank, back to you, and all the way to the bank again, while your desperate attempts to comply will completely destroy your reputation and make affected people really, really angry. I've seen that happen twice as an insider now, once on each side of the Atlantic. Same outcome too; it's funny how playbooks that work tend to be passed around.

> This is why the state of things is so bad.

I think that solutions can be found in the optional/bootstrap service, like you have for shockwallet. You can walk. This worked for wasabi too, though less optimal because from what birdies told me at the time, snacks wasn't prepared.

It can defo be done. I'd work on a protocol. Not on the service implementation. That makes it a hobby thing tho.