[email protected], BTC Proxymalist, QA Kamikaze FOSSéen, bluesman blanc, goldo-daron-rak, my phone is worth 105 BTC

Neuchâtel, Switzerland
Joined May 2010
Tirodem / Christophe Gérard retweeted
Un casseur repart avec cinquante milliards de dette après avoir dévalisé le ministère des finances
41
745
44
3,828
55,715
À Neuchâtel, dans les bureaux du @coworkn , on a un K1 de @k1elsalvador qui permet d'acheter des SATs avec des pièces. Aujourd'hui (en PoC), avec @beBOPcommunity , on peut utiliser un distributeur DIY avec be-BOP-IoT pour payer en n'importe quoi (dont LN) pour avoir des pièces 🥸
3
2
11
365
Nos protos be-BOP-IoT seront présentés au B-Only @alpinechain_xyz et je serai aussi à Bordeaux au Bitcoin Wealth Summit, du coup n'hésitez pas à venir nous voir ! xitter.cf/alpinechain_xyz/status…
🏔️ Annecy, 7–9 novembre : B-Only. 📍 Bordeaux, 20 novembre : Bitcoin Wealth Summit. Bitcoin, technologie, souveraineté, patrimoine et transmission. Deux conférences. Un billet commun à 214 €. 🎟️ 30 places maximum. inscription : b-only.org #BitcoinWealthSummit
2
1
1
207
Du coup, techniquement, avec cet autre PoC qui transforme be-BOP en petit exchange décentralisé, on peut faire une boucle infinie sats <> fiat :D xitter.cf/tirodem/status/2100600…
Quand t'essaies de builder rigolo entre 2 trucs de cybersécu. Ici, @beBOPcommunity , on choisit un PWYW, on paie en CB (test), un be-BOP-IoT ESP32 en wifi en série sur une imprimante thermique imprime le bon, le qr, on scanne, on a des SATs. Soon (2-3 mois) chez n'importe qui.
29
Du coup techniquement au coworking on peut payer en GNU Taler, avoir de la monnaie suisse, et acheter des SATs avec. Parce que pourquoi pas.
2
33
Tirodem / Christophe Gérard retweeted
VPNs are useful, they hide your traffic from your internet provider, but you’re still trusting a single company with your privacy. Do we have a better alternative? At PROOF in Vilnius, @alexis_roussel compared traditional VPNs, Tor, @nym, and mixnet, explaining how it uses different routes, dummy traffic, and shuffled packets to make those patterns harder to trace. He also demonstrated NymVPN live 🛜 00:00 - Introduction 01:00 - Why metadata says more than the message 04:44 - Classic VPN and Tor compared 07:18 - How the mixnet hides who talks to whom 11:12 - Gateways, anonymous replies and onion routing 15:20 - Bitcoin wallets, NymVPN and private payment 20:20 - Live demo of NymVPN 29:09 - Scaling, audits and running a node Event sponsored by @bringinxyz ⚡️
1
5
1
20
870
Merci moi pour ce cadeau à moi-même
2
19
671
Le génie peut être n'importe où. (quelque part dans des toilettes d'autoroute allemandes)
4
1
20
471
J'avais envie de rouler et de changer d'air vite aif'. Me fallait aussi des clopes et des fringues. Résultat j'ai pété 8h30 de route (avec une pause pipi) et je viens de me garer à Prague 🥲
8
28
824
Tirodem / Christophe Gérard retweeted
Full post-mortem of the September 19 attack, and a 50% bounty — up to 3.3 BTC — on the stolen funds: blink.sv/blog/sept-19-attack… Bounty terms: blink.sv/bounty-terms On Saturday September 19 an attacker used a flaw in our admin tools to take over 35 Blink accounts and withdraw about 6.61 BTC from 24 of them. A customer called one of our engineers at 11:39 UTC. Fifteen minutes later the whole custodial service was off. By that evening the hole was closed and the service was back. By Thursday September 24 every affected customer had their exact balance back, in bitcoin and in dollars, paid for by Blink's shareholders. No customer bears any loss. This was our fault. Not Bitcoin's, not our users'. To the 22 customers whose bitcoin was taken, and to the 3,817 people whose account details were looked up: we are sorry. How it happened: From October 2023 until that Saturday, anyone with a free Blink account and a web browser could give themselves the powers of our support staff: change the email or phone on any account, log in as that customer, raise their limits. Three unremarkable mistakes in how our admin tools checked permissions, stacked on top of each other, in code we inherited. The whole team was busy moving tens of thousands of users to self-custody under new regulation. Monitoring built to catch outages didn't catch an administrator doing things no administrator should. What it didn't touch: The money came out of our hot wallet. Most customer funds sit in multi-signature cold storage that nothing in our admin tools can reach. Non-custodial accounts were never in play: we don't hold those keys. What the attacker saw: They also read the details of 3,817 other accounts, in some cases a phone number or email address. Not names, not IDs, not addresses, not passwords, not seed phrases. We wrote to every holder we could reach, saying exactly what was seen. What stopped them: Two-factor authentication. The attacker logged in to nine accounts that had it on and tried eighteen times to move money. Zero loss. None of the 24 drained accounts had it on. If you take one thing from this post: Settings → Security and Privacy → Two-factor authentication. Then turn it on for your email too. What we changed: The flaw was fixed the same day and a third layer added two days later. The admin tools are off the public internet. The functions that change a customer's email or phone are switched off for everyone while we redesign them. All customer API keys were revoked. The hot wallet now holds a fraction of what it did. Security fixes are developed privately and published once deployed; the code stays open source. A standing security reporting channel is live, with rewards of up to 0.1 BTC for critical findings. Where the money is: Some still sits where it was withdrawn to. About 5 BTC has gone through a cross-chain swap service; a small amount reached an exchange that is cooperating. Criminal complaints are filed in El Salvador and Próspera, the regulators are notified, and we have traced the funds continuously. We are not expecting the money back. So we are putting a 50% bounty on it. Whoever provides the information that leads to a recovery gets 25% of what is recovered. Another 25% of anything recovered goes to Bitcoin Beach, Bitcoin Ekasi, Afribit Kibera and the circular economies they choose. No cap, no end date, paid only out of funds that actually come back. Write to [email protected]. We would far rather have spent this money on grassroots Bitcoin adoption than lost it to a thief. Shame on the attacker. One more thing: Ignore any email or SMS about this incident that contains a link: we contacted affected users only through messages in the Blink app. We will never ask for your PIN, password, seed phrase or a login code. The full post-mortem has the timeline, the technical detail for anyone running code derived from ours, and the bounty terms (links at the top).
115
124
24
1,108
5,902,662
Google la prochaine fois où sur tes captchas ça dit "check les motos" alors que ce sont juste des scooters je te fume.
1
13
335
Tirodem / Christophe Gérard retweeted
Blink services are back online. The vulnerability behind the incident has been fixed and verified, and access has been restored for all unaffected accounts. If your account was not affected, you can continue as usual. Accounts of affected users will remain locked temporarily. Non-custodial balances were never affected. A full post-mortem will follow. Thank you for your patience. Questions? Reach us at [email protected].
Replying to @blinkbtc
Update: A few dozen custodial accounts were affected by the incident. Every affected account is identified and will be made whole. If you were affected, there's nothing you need to do. If you have questions, reach out at [email protected] any time. Non-custodial balances are unaffected.
13
60
3
200
10,666
Tirodem / Christophe Gérard retweeted
🟢Swiss Bitcoin Pay is back online. First, the essentials: no funds were lost. That includes merchant balances awaiting onchain settlement, which are fully intact, and cards balances. All amounts owed didn't moved. As stated on Monday, we continue to assume that customer email addresses, Bitcoin addresses, IBANs, transaction history and hashed passwords may have been accessed. We are treating that data as compromised. We can now add one finding: we found no evidence that identity or KYC/KYB documents (that some of our customers had chosen to provide) were extracted. Every attempt we traced to copy files out to the attacker's server failed. We want to be precise: no evidence is not the same as a guarantee. This is what our deep investigation found, and we will tell you if that ever changes. We have closed the vulnerability, rotated every credential, and drastically hardened our infrastructure. One thing we want to be open about: we had been working for months on a new infrastructure and modern stack, built to a far higher security standard. It was scheduled to go live this week. A few days earlier, and this attack would not have been possible. We are not saying this as an excuse: the system that was breached was ours, and so is the responsibility. We are saying it because you deserve the full picture, not a curated one. What we recommend: change your password, and change it anywhere you reused it (or use a password manager). Be sceptical of any message about this incident, even one that already knows your details: with an email, an IBAN and a transaction history, phishing gets convincing. We will never contact you asking for a password, a seed phrase, or to move funds. Thank you for your patience this week. We took the time to do this properly. We're back, and stronger.
5
18
2
68
4,256
Tirodem / Christophe Gérard retweeted
L'histoire des réseaux test de Bitcoin youtube.com/watch?v=GYNiDdu1…
7
10
1,583
Tirodem / Christophe Gérard retweeted
Update: A few dozen custodial accounts were affected by the incident. Every affected account is identified and will be made whole. If you were affected, there's nothing you need to do. If you have questions, reach out at [email protected] any time. Non-custodial balances are unaffected.
We've paused Blink services while we investigate a security incident. An attacker accessed a limited number of custodial accounts and withdrew funds. The large majority of funds are secure. Non-custodial wallets are not affected.
16
56
13
197
28,203