benma

works @BitBoxSwiss / BitBox02, #bitcoin

[benma @_benma_]

@robin_linus @LLFOURN Not at all.

[BitBox @BitBoxSwiss]

Bitcoin has a color. Now your wallet does too.

Introducing the BitBox02 Nova Bitcoin-Only Edition in Bitcoin Orange. Our most advanced hardware wallet, made in Switzerland.

Set up in a minute, works with every desktop and phone.

Order yours: https://t.co/RvPUEcStSp

[benma @_benma_]

@vikrantnyc I thought you liked privacy 😅

[benma @_benma_]

@pythcoiner Does Liana extract depth/parentfp/childNum from any xpub though? The origin in a descriptor doesn't have anything to do with these fields. The rootfp is encoded in the parentFP field of a direct child from the root, but that is not connected to the xpub in the descriptor.

[benma @_benma_]

An xpub contains (apart from the essential chain code and pubkey):

- depth
- parent fingerprint
- child number

Is there any practical use for these?

Is there any software out there that that actually uses these fields for anything?

[BitBox @BitBoxSwiss]

Alright. What do you want to see in the BitBox03?

[benma @_benma_]

@ErikVoorhees @elonmusk Please elaborate. How it is private while not being open weights? Do you run it in your own infra?

[benma @_benma_]

@AskVenice @xai Please explain. Do you run these models in your own infra? If not, why mark it 'private' and not 'anomymized' like with the other third party models?

[benma @_benma_]

@NicolasDorier Setup an agent that monitors Bitcoin Core PRs and checks if they would break anything for you. You or it could then comment on the PR.

[benma @_benma_]

@zerosandohs @bourbonni @lopp @isabelfoxenduke If there was a bug discovered today that made all coins spendable by anyone, would you be in favor of a fix?

[benma @_benma_]

@coinjoined @BitPaine The basic assumption is that private keys are private, not public. Critical bugs ought to be fixed.

> Consensus is functioning exactly as designed.

Exactly: consensus is up to users.

[benma @_benma_]

@giacomozucco > pseudo-science

Nope. Copenhagen and related views however are.

> philosofically inconsistent

No, why would that be? It's just an explanation of reality that makes sense, unlike the illogical hogwash related to duality or wave collapse.

[benma @_benma_]

@thsottiaux @CodeEdison Emacs+magit for reading/reviewing/navigating is complementary to codex.

[benma @_benma_]

@dathon_ohm For the lazy, I did this. Here is the quote:

> While it is impossible to fully prevent steganography, limiting data sizes **ensures such abuses are non-contiguous** [...]

The demonstration completely refutes this claim.

[benma @_benma_]

@giacomozucco Luke did stress at the PlanB Lugano panel that the bytes touching was the problem.

[benma @_benma_]

@coinjoined @hodlonaut Not that, but that people will lose their money by following that hopeless fork, like what happened to bcash and bsv victims.

[benma @_benma_]

@hodlonaut > BIP-110 opposition seems to be greed- and grift-driven.

Greed in the sense that BIP-110 is destroying the value of Bitcoin? Then yes.

[benma @_benma_]

@Arthur_van_Pelt Have you not been here for the blocksize wars? This particular claim has been made and debunked on a daily basis back then.

The quote you made has nothing to do with consensus changes whatsoever.

[benma @_benma_]

@stephanlivera @SimplestBTCBook @adam3us @hodlonaut Moving an involved custody setup to a new one can be a huge effort, especially if there is no alternative that is currently ready to use.

So by simply continuing to use a current setup, one creates new UTXOs by making new change outputs, or periodic refreshes, etc.