Armin retweetledi
The @ChaincodeLabs BOSS Challenge may be over, but the building continues! Check out these incredible portfolio projects that participants worked on during the program 👇
bosschallenge.xyz/portfolioproje…
English
Armin
671 posts
Armin
@Arminsdev
Working on P2P electronic cash. @payjoindevkit Host @bostonbitdevs Prev at @casahodl and @botanixlabs
Katılım Mayıs 2021
756 Takip Edilen2.8K Takipçiler
Armin retweetledi
🚀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
English
Armin retweetledi
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 👇
github.com/bitcoin/bips/p…
English
It may be a dead end. But it does look like there may be a solution to at least some of the heuristic labeling there.
English
@Arminsdev have you looked at how shielded CSV using Argo can limit wallet fingerprinting issues with payjoin? Seems like there may be some mitigation this can provide. Probably eventually moreso than now, but it looks like a third route over standardize everything or max chaos.
English
Armin retweetledi
Armin retweetledi
Can you spot the 6 "slow blocks"?
This is one Bitcoin vulnerability that BIP54 addresses.
English
Armin retweetledi
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)
English
Armin retweetledi
Armin Sabouri, pythcoiner, Conduition, and Jonas Nick
on Isogenies, SHRIMPS, payjoin, GSR.
Nice
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)
English
Armin retweetledi
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
English
Armin retweetledi
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
Payjoin Dev Kit@payjoindevkit
How can wallet fingerprints be used to damage Payjoin privacy? @Arminsdev spent a week in a darkly lit room to study this class of attacks against real-world Payjoins.
English
@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).
English
@Arminsdev @payjoindevkit But in your tx is 72-71 bytes
And in this one is 71-71 each input, so no fingerprint
English
How can wallet fingerprints be used to damage Payjoin privacy? @Arminsdev spent a week in a darkly lit room to study this class of attacks against real-world Payjoins.
English
Armin retweetledi
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.
Payjoin Dev Kit@payjoindevkit
How can wallet fingerprints be used to damage Payjoin privacy? @Arminsdev spent a week in a darkly lit room to study this class of attacks against real-world Payjoins.
Español
@Multicripto @payjoindevkit That is consistent with my findings! Thank you
English
@Arminsdev @payjoindevkit I did this with 2 Ashigaru wallets. So, your example is between Samourai and Sparrow
mempool.space/testnet4/tx/24…
English
@Arminsdev @payjoindevkit How you gonna test with 2 Ashigaru wallets?
English
@Multicripto @payjoindevkit I'm not sure. I pulled it from #understanding-payjoin-transactions-on-bitcoin" target="_blank" rel="nofollow noopener">byakugan.io/posts/ashigaru…\
English
@Arminsdev @payjoindevkit Could you tell me if the Stowaway transaction you showed was made from two Samourai wallets or from one Samourai wallet and one Sparrow wallet?
English
@Multicripto @payjoindevkit yes. The payjoins we create via the reference are v2 / LT = current_height
English
@Arminsdev @payjoindevkit So Cake and Bull should change to a non-zero LT to match what you're discussing here, correct? The payjoin tx is v2 /LT0
English
@sadeeq_ismaela Very cool! Where can I learn more about that? Do other wallets have a similar fingerprint?
English
@Arminsdev Nice post. In the past, I was able to fingerprint Core wallet txs on the network using these heuristics and fee estimates. After fee spikes, Core's estimator lags and txs using those stale estimatesmartfee ranges/with core wallet fingerprints reveal themselves as Core wallet txs.
English
Wallet fingerprints are subtle and can undo the hard work you do to preserve your privacy. Broke this down in my latest post.
Payjoin Dev Kit@payjoindevkit
How can wallet fingerprints be used to damage Payjoin privacy? @Arminsdev spent a week in a darkly lit room to study this class of attacks against real-world Payjoins.
English
@Multicripto @payjoindevkit We just fixed this in our refrence implementation
github.com/payjoin/rust-p…
English
@Multicripto @payjoindevkit No. The existing wallets should update to set nlocktime to > 0. anti-fee sniping is good idea in general. IIRC their dependencies have update they just havent released it yet.
English