Avatar
Felix
11674b2d321fc24239b02afdf966c32e36594a6282bd7f3d4bcd12438558ab51
Funny money developer @felix.7252 on Signal
Replying to Avatar Rusty Russell

#dev #CLN

One of the fun things after a release is that I sweep the code and remove things which are now past the end of their deprecation cycle, and then update to the latest BOLT specs. The former is usually trivial (this time there were only two things to remove, and nobody will care). The latter can be more interesting, and was.

Our code contains quotes from the BOLT they are implementing, so when we update the version it reports what has changed. Sometimes it's merely a typo fix, but since last release we actually made a pile of old features ASSUMED. This includes "option_static_remotekey" which we supported in CLN since January 2019 release, meaning you will only see channels without this if they were opened more than 5 years ago. We still support these existing channels, but all support was removed for opening new ones.

The other option is "option_anchor_outputs": we were the only ones to ever deploy this, and then only in experimental mode, because zero-fee anchors quickly replaced it.

Unfortunate to I don't know how many (if any!) such channels there are!

So what do we do about existing channels? I can enable the currently-experimental code to migrate such channels, which works if both ends are CLN. But it's not clear how much further I should go: my spec proposal for upgrade has been in limbo for years, and at some point it's far cheaper to pay a handful of people to reopen their channels than it is to do the engineering required for migration.

It's a few versions away yet, but at some point we will have to refuse to upgrade if the user has such a channel, in the hope they will contact us if it happens.

If the option to open this kind of channels always has been experimental, shouldn't it be acceptable to just close them at update?

Can't really expect perfect stability when using experimental features so this shouldn't be too unexpected for the user.

I think the old trading pipeline (and more) will come later, probably best to keep using Bisq 1 till then

I like it better than before, no more double saving of images

"New" depends in your time horizon, this is not a Smartphone with 1 year release cycle

Might make sense to get some...

Secret tip for all meat eaters in Prague rn:

https://www.kantyna.ambi.cz/

Is kyc happening only trough phone number verification? Maybe you could get a real sim card anonymously depending on your jurisdiction.

I think Damus hasn't implemented this feature, Amethyst has, there is also a web client marketplace but I don't remember the name

Currently discovering the masculine urge to build the perfect nixos configuration

Replying to Avatar awayslice

Setting up my new nostr:npub1wu4aye7ll0lnrrg638e90sehzsgpzx5t39t3mwl05aa0d0ap08esdz3vw0 Coldcard Ż prototype.

Took me 45 min. to enter my seed, but it’s not supposed to be easy right?

The canary color is DOOOOPE!

?c=MHaoEHf4JA4T1dYEo1CR0ZiICul7KRxigYiIoE-XMD35go1Txl7UaoIaOUKdtWDzkE3h274cER4Mmcnl_9ztHulqe9HABovFQSwRBwKQF6AJIuRpK0iXaxnO6lRmOWzLM0suwRJxPL8YeQAdy-RpuSHrDRULGTCfBXPDBoBfXW4%3D

Cool idea but I guess in times of Spotify only hardcore fans will buy a "CD" as most probably just want to add songs to their Spotify playlist. But idk, could sell well in person at clubs or events

Replying to Avatar OpenSecret

Announcing: Harbor, an ecash desktop wallet for better bitcoin privacy.

https://blog.mutinywallet.com/harbor/

Privacy for the common person is a value worth fighting for. When we see a lack of freedom tools, we must build them into existence. They don't appear on their own.

Much has been said about privacy at the Bitcoin protocol level. For now, we build it on higher layers where we can be more nimble.

Ecash is a tool available today that combines with Bitcoin to bring new levels of common privacy. Cashu and Fedimint are two existing implementations we're interested in.

Harbor Privacy: All communication runs over Tor. Mutiny is not in the middle of any connections or transactions. Funds in the wallet get a Privacy Score to show how the mints provide privacy over time. More to come on this in the future.

Harbor Multi-mint: Instead of relying on a single mint with your funds, spread the risk over dozens or more. Harbor manages this for you, showing you a single balance while connecting with mints for you. A mint can go offline with minimal impact on you.

Harbor Automation: Running as a desktop app unlocks ability to do long running processes in the background. Move money in and out of mints on your preferred schedule to maximize your desired level of privacy. Harbor makes suggestions, but you are in control.

Move money in and out of Harbor using Lightning or on-chain. We love Bitcoin, and we love privacy. We hope Harbor gives everyday people more privacy and peace of mind.

Very cool