Armin

Working on P2P electronic cash.

@payjoindevkit
Host @bostonbitdevs

Prev at @casahodl and @botanixlabs

[Armin @Arminsdev]

@conduition_io @blksresearch Congrats!

[b10c @0xB10C]

I never thought this would be possible, but:

I built a bitcoind binary with Nix that is bit-by-bit identical to the Bitcoin Core v31.0 Guix-built release binary for x86_64-pc-linux-gnu. Big win for reproducible builds across different toolchains.

https://t.co/Ff1g6U8Hf9

[Bitcoin Dev Project @Bitcoin_Devs]

The @ChaincodeLabs BOSS Challenge may be over, but the building continues! Check out these incredible portfolio projects that participants worked on during the program 👇

https://t.co/gMZ83HmeGC

[Armin @Arminsdev]

@tpacchia Boston :)

[Seres István András @Istvan_A_Seres]

🚀New paper: Private Delegation of (Non-)Membership Proof Updates in Cryptographic Accumulators

Ever tried to use accumulators in practice? Then you’ve hit the wall: every update breaks everyone’s proofs.

We fix that.

🧵1/n

[bitcoin++ Insider Edition @btcinsider__]

BIP: Oli Guggero (@guggero), recently retired Lightning infra engineer, is looking to take responsibility for BIP322.

Originally proposed by Karl-Johan Alm (@kallewoof) in 2018, BIP322 allows keys that control a bitcoin UTXO to sign any generic message. This permits UTXO holders of any script type to prove ownership without spending the coins 🪙

In his newly opened pull request, Oli catalogs and addresses open issues with the proposal and identifies work still to complete.

Read the full list of work still to do on the PR 👇

https://t.co/qSavN4CULh

[Armin @Arminsdev]

@cykros Not sure! This is an area I unfortunately have not kept up with. Let me know if you write a summary of your findings

[Olaoluwa Osuntokun @roasbeef]

https://t.co/xpzYv2uYw2

[Mike Schmidt @bitschmidty]

Can you spot the 6 "slow blocks"?

This is one Bitcoin vulnerability that BIP54 addresses.

[Bitcoin Optech @bitcoinoptech]

Armin Sabouri, Pyth (@pythcoiner), Conduition (@conduition_io) , and Jonas Nick (@n1ckler) joined Optech to discuss Newsletter #399:

News
● Wallet fingerprinting risks for payjoin privacy (44:15)
● Draft BIP for a wallet backup metadata format (1:04:26)

Changing consensus
● Compact Isogeny PQC can replace HD wallets, key-tweaking, silent payments (24:23)
● Varops budget and tapscript leaf 0xc2 (aka Script Restoration) are BIPs 440 and 441 (1:13:24)
● SHRIMPS: 2.5 KB post-quantum signatures across multiple stateful devices (02:02)

Releases and release candidates
● Bitcoin Core 31.0rc2 (1:22:07)
● Core Lightning 26.04rc2 (1:23:32)
● BTCPay Server 2.3.7 (1:24:04)

Notable code and documentation changes
● Bitcoin Core #32297 (1:26:29)
● Bitcoin Core #34379 (1:28:54)
● Eclair #3269 (1:30:37)
● LDK #4486 (1:32:59)
● LDK #4428 (1:35:00)
● LND #9982 (1:37:13)
● LND #10063 (1:39:00)

[Mike Schmidt @bitschmidty]

Armin Sabouri, pythcoiner, Conduition, and Jonas Nick
on Isogenies, SHRIMPS, payjoin, GSR.
Nice

[Armin @Arminsdev]

@bc1cindy Welcome 👋

[Bitcoin Optech @bitcoinoptech]

Bitcoin Optech newsletter #399 is here:

- describes how wallet fingerprinting can damage payjoin privacy
- summarizes a proposal for a wallet backup metadata format
- links to post-quantum research using Isogenies
- points to the recently assigned BIPs for GSR
- examines SHRIMPS post-quantum signatures
- Optech Newsletter #399 Podcast

[bitcoin++ Insider Edition @btcinsider__]

FINGERPRINTED: Bitcoin dev @Arminsdev breaks down how wallet fingerprinting impacts privacy of Payjoins, a decentralized batching technique for onchain bitcoin payments which aims to break common tracking techniques

[Armin @Arminsdev]

@Multicripto @payjoindevkit Correct. The point is wallet fingerprints are more of a problem if your counter party is using a different wallet (or the same wallet at a different version).

[Arkad @Multicripto]

Si cada billetera de Bitcoin firma de forma diferente, las huellas que van dejando van rompiendo herramientas de privacidad e intentos del usuario por mantenerse privado.

[Armin @Arminsdev]

@Multicripto @payjoindevkit That is consistent with my findings! Thank you

[Armin @Arminsdev]

@Multicripto @payjoindevkit Not sure. Open to suggestions

[Armin @Arminsdev]

@Multicripto @payjoindevkit I'm not sure. I pulled it from https://t.co/xtU8riZed9\

[Armin @Arminsdev]

@Multicripto @payjoindevkit yes. The payjoins we create via the reference are v2 / LT = current_height