Avatar
Eluc
cf7ad05f8e99de8eadbbfbd5ca1c0f9b75499bce07074966b277688ca5e1d726
Open minded Bitcoiner and blogger with a focus on UX, privacy and security. https://eluc.ch

This is important. Firefox is good but not great without tweaks or fork. A good and clean alternative would be really welcome.

Also I love the mentality: "Windows is not a priority for us."

They know their target audience.

Replying to Avatar Édouard

We worked on a vault system managing watchtowers and cosigning servers before Liana: https://github.com/revault

The presigned timelock tx was called a unvault tx and the watchtowers were able to cancel (send funds back to the vault) during the time of the locktime according to specific spend policies.

Amazing, I will study that. Why was the solution from Liana prefered in the end?

I have seen an idea for another time locked recovery path concept that doesn't require renewal. The idea was to share presigned transaction, to use a recovrey you broadcast the transaction, which will trigger an on-chain even that start the time lock count-down. X blcoks after the first recovery transactions is broadcasted, the recovery path will be able to sign another transaction to withdraw the BTC to another wallet unless the person who control the original path move the BTC away before the timelock expire.

It's like a deadman Bitcoin switch.

This need machines activeley monitoring the blockchain (or you put a reminder to manually check at shorter interval than the time lock, like once per year if the timelock is 65'000 blocks.

However I don't remember where I saw this concept and if someone is working on it or not.

We need more Product Manager on Bitcoin to bring UX requierment and product roadmap. I'm one myself but it looks like we are not welcome at Bitcoin projects and even Bitcoin companies. Most of the time, one of higher persons, usually CTO or CEO like position, will try to cover this part but it's a full time job that need skills and experiences.

Also private industries are paying Product Manager so well, that's hard to move to such projets, beside a side hobby. And even so, it's hard to get a place.

I guess the assumption is that you will die soon and Bitcoin worth a fortune so you don't need much sats to survive the last few years.

Replying to Avatar tanel

gm 💜

Cuboro maze ❤️

GM

&f=1&ipt=f43328da487b7adaaa29bec6c55132ed2f8780c153e7e90725fbba7f3aede2fa

I just got notified that you can do something similar without LNbits, but it's more intended to give tips as you can fund cards on the go before handing them over and recover the sats if unused after a certain amount of time: https://tipcards.io/

I guess it's custodial but I didn't try yet.

I did only test is now but I plan something similar. I run a LNbits instance and you have an extension LNURLw that generate withdrawal QR code (scan to withdraw sats to any lightning wallet). One option allows to generate vouchers that you can print, fold and glue to hide the QR code and you have instruction and must tore down the glued part to see the QR.

Then they can either withdraw the sats to their wallet (Phoenix, Breez, Blixt, WoS...) or if they don't scan with a wallet, it will open a custodial account for them on your LNbits instance.

You are the uncle jim bank, keep the sats for them until they withdraw them, and you can offer them to keep the sats even further for future sats they become on your instance.

Ça fait déjà 20 ans qu'il faut s'inquiéter de Google (et toute la GAFAM) pour des miliers de raisons mais la plupart des gens n'ont toujours pas compris le problème.

Replying to Avatar Old Man Tyler

Update done, please read the change log:

Bug fix:

- Fix a bug allowing to bypass update

New features:

- Disable scan and fax function if you are out of yellow ink

- Purposly decrease the print quality if an unofficial cartridge is detected

- Sending void warranty information to Epson if we see unofficial cartridge being added to your Amazon cart

- Self destruction mode after at least 2 full sets of non-official cartridge were used

Great tool but is it open source? can I self host it?

Yeah, this kind of fight are painful and harming the community. If I had to recommand anything to start with: Bitcoin Core + LND. Then they can figure out later if they want Knots, CLN and other stuff. I would even recommand to begin with an OS like Start9 or Umbrel.

Sérieux, cela arrive vraiment? Un nouveau monde de DeFi totalement anonyme et sécurisé.

Attrends une seconde, pourquoi ils parlent d'un app de chat? Tout ça pour une n-ème app de chat?!

OK retour à Bitcoin et nostr.

So Zeus is your best option then, but it's next to a LND wallet (which you csn leave empty).

I was about to suggest nostr:nprofile1qqsrf5h4ya83jk8u6t9jgc76h6kalz3plp9vusjpm2ygqgalqhxgp9gpzfmhxue69uhk7enxvd5xz6tw9ec82cspp4mhxue69uhkummn9ekx7mqpzpmhxue69uhkummnw3ezumrpdejqd2970s as they mention Taproot support, but it turns out you cannot have a watch-only on-chain wallet. Maybe in a future version.

I'm pretty sure Green wallet should support that but didn't try myself.

I don't use Cloudflare, I think it was for the former domain extension. However you need to setup some reverse proxy.

Beside the crazy price, what is the people problem with bathroom, who needs 5 bathroom for 4 bedrooms? Let's say it's a 5 persons family libing there (most probably 4 but let's assume) will these 5 persons all go to piss, shit and shower within the exact same 15min?! 90% of the time bathroom are unused space. And you have to clean all of these, but if you xan afford, I guess you are not cleaning it yourself.

Replying to Avatar negr0

Bitcoin Core vs. Bitcoin Knots: The Great Bitcoin Spam Fight

The Bitcoin community is engaged in an interesting debate: Bitcoin Core vs. Bitcoin Knots. What are they? Why are they fighting?

Here, I explain clearly and simply, without missing any details, with neutrality and a touch of the "spam" controversy.

What is Bitcoin Core?

It's the main software used by approximately 90% of nodes (computers that keep Bitcoin running).

It's stable and developed by many programmers, but some say it doesn't react quickly to problems like network spam.

What is Bitcoin Knots?

An alternative version of Core, created in 2011 by Luke Dashjr.

It has everything Core has, but adds filters to block "annoying" transactions like NFTs or images on the blockchain.

It is used by approximately 633 nodes and relies on a single developer.

Why the conflict?

Everything exploded in 2023, when transactions like NFTs and "ordinals" (data like images on the blockchain) saturated the network, driving up costs.

Knots filters them to ease the network's burden; Core allows them if they pay fees, dividing the community.

What is "spam" in Bitcoin?

Think of the blockchain as a highway: transactions are like cars. Some (NFTs, JPGs) take up a lot of space, causing "traffic."

- Knots: Blocks them to clear the way.

- Core: Lets them through if they pay a "toll."

But who decides what is "spam"?

As the community says: "Spam is in the eyes of the recipient."

- Some see NFTs as spam, like a fake lottery email. Even if they pay, they don't want them on their nodes.

- Others say: "If they pay and the protocol allows it, it's not spam."

Think about it: someone sending mass emails about fake lotteries pays for the server and plays by the rules of the internet.

But you don't want those emails in your inbox. Likewise, some people don't want JPGs on their Bitcoin nodes, even if they're "valid" transactions.

Is it fair to filter them?

The debate began in 2023, when a bug ("Inscriptions", CVE-2023-50428) allowed data like NFTs to be inserted into the blockchain, overwhelming it.

Knots quickly fixed this in its 25.1 release, while Core was slower, leading some to view Knots as the solution to "spam."

Here are the sides in this debate:

- Team Core: They believe that any transaction that pays is valid. Filtering is like "censorship" and goes against the freedom of Bitcoin. They prefer stability and regulated fees.

- Team Knots: They want to protect the network from saturation, claiming that filters don't break the rules.

- Luke Dashjr (Knots): He says NFTs and ordinals are "spam" that clogs the network and increases costs. His filters help small nodes, but some criticize him for only maintaining Knots.

- Peter Todd: He sees "spam" as a problem, but says paid transactions are valid. He looks for open technical solutions.

Other technical voices

- achow101 (Core): In 2017, he said to use Core unless you need Knots' features, viewing Knots as an "extra."

- Developers like Gloria Zhao have shut down filter ideas in Core, frustrating those who want quick changes.

After asking a few people in the community, we came to different conclusions on both sides:

- Pro-Core: They value stability and fear that Knots, with only one developer, is risky. They say filtering is making decisions for others.

- Pro-Knots: They want anti-spam tools and criticize Core for being slow. They see Knots as an innovation.

The Filter Dilemma

Even if you filter JPGs on your node with Knots, if a miner includes them in a block, your node must accept it. It's like blocking a lottery email, but having to save it if it's already reached the server.

This makes the debate complex: do you filter or accept everything?

Technical explanation (easy)

The mempool is a waiting room for transactions.

Knots lets you choose what comes in (with filters like datacarrier=0), while Core accepts almost anything.

If many nodes used Knots, spam would be more expensive, but it wouldn't disappear.

Core is committed to stability and freedom; Knots is committed to control and efficiency. Spam divides because everyone has a different view of what's "annoying."

The community will decide whether Bitcoin should be "cleaner" or more "open."

Which side are you on?

I must stay on Core side, not necessarly because I endorse the inscription usage as it was done in 2023, but I must admit I still think there are real use cases that could worth it, as long as we keep minimal data on the blockchain, like a decentralized npub/url registery (like ENS did on Ethereum, one of the only good use cases of Ethereum imo).

Also this NFT mania was a phase like many others, as soon as it turns out unprofitable, it went dead and it's again a non-issue, the mempool get cleared regularly, nobody would have believed this in 2023.

Anyway I still think it's good to have alternatives and not relay on a single solution, however I would not take the risk to run my node with it's main component maintained by a single person. This is doomed to failed. The guy could move on to another project, take too long to push critical update, have not enough resource and less observer to find critical bugs, take a turn even more controversal without anyone else to bring a second opinion/voice, or he could die or disapear, leaving you in a bad situation, having to setup your entier node again.

I already run CLN and it's hard to be the marginal group, behind always late to get included in new project and service (LNbits still not supporting the new REST that is more secure, NWC not supporting CLN at all, Thunderhub,...)

But it has still more than one dev and 300 users (I hope), and a lot of excellent features that I want to support and use (bolt12, CLNrest rune with fin tuned permissions, ...).

Can we make this but with webtorrent, so source cannot be down as long as someone seed?

6a support end already? I have a Pixel 7 and still feel like it's brand new, bought it before the 8 was even annonced. Hopefully it will be supported another couple of years at least.

I block it but still get notifications somehow.

I still have ETH that I want to dump if it pump again.

Don't shoot me neither.