Master on Bitcoin & Blockchain Technology (RIP) (@MScBlockchain) header
Master on Bitcoin & Blockchain Technology (RIP) (@MScBlockchain) profile picture
Joined February 2020
Photo by Master on Bitcoin & Blockchain Technology (RIP) (@MScBlockchain)Photo by Master on Bitcoin & Blockchain Technology (RIP) (@MScBlockchain)Photo by Master on Bitcoin & Blockchain Technology (RIP) (@MScBlockchain)Photo by Master on Bitcoin & Blockchain Technology (RIP) (@MScBlockchain)Photo by Master on Bitcoin & Blockchain Technology (RIP) (@MScBlockchain)Photo by Master on Bitcoin & Blockchain Technology (RIP) (@MScBlockchain)Photo by Master on Bitcoin & Blockchain Technology (RIP) (@MScBlockchain)Photo by Master on Bitcoin & Blockchain Technology (RIP) (@MScBlockchain)Photo by Master on Bitcoin & Blockchain Technology (RIP) (@MScBlockchain)Photo by Master on Bitcoin & Blockchain Technology (RIP) (@MScBlockchain)
Master on Bitcoin & Blockchain Technology (RIP) retweeted
Recommend updating ASAP...again.
4
10
59
4,010
Master on Bitcoin & Blockchain Technology (RIP) retweeted
¡ANUNCIO DE SPEAKER! Mikel Peñagarikano (@mpenagar) Físico, profesor en la UPV/EHU y lead de las Jornadas Bitcoin (jornadasbitcoin.org), que ya van por su 6ª edición desde Bilbao. Lleva años llevando Bitcoin a las aulas. Su definición de Bitcoin no ha cambiado desde la primera charla. Ni tiene por qué. En WOB! los debates cambian según quién los cuenta. 📅 2-4 oct · Madrid 🎟 Entradas: wobitcoin.org/#entradas #WOB26 #WatchOutBitcoin #Bitcoin #Madrid #JornadasBitcoin #Universidad #Educacion
2
8
492
Master on Bitcoin & Blockchain Technology (RIP) retweeted
Strongly agree. When I verified Bitcoin Core 31.1 myself, I didn't stop at checking the SHA256 hash. I imported public PGP keys and verified signatures. More importantly, Bitcoin Core uses reproducible Guix builds: independent builders can build the same release on their own machines and attest that they arrived at the same binaries. Bitcoin Core 31.1 has Guix attestations from 16 independent builders: 0xb10c — github.com/0xb10c Emzy — github.com/Emzy Sjors — github.com/Sjors achow101 — github.com/achow101 benthecarman — github.com/benthecarman fanquake — github.com/fanquake guggero — github.com/guggero hebasto — github.com/hebasto m3dwards — github.com/m3dwards marcofleon — github.com/marcofleon pinheadmz — github.com/pinheadmz sedited — github.com/sedited sipsorcery — github.com/sipsorcery svanstaa — github.com/svanstaa theStack — github.com/theStack willcl-ark — github.com/willcl-ark That is a radically different trust model from simply checking a checksum published by the same party that gave you the binary. And frankly, it seems crazy to me that so much of the current discussion has shifted toward worrying about whether users need to generate their own randomness. We routinely trust general-purpose computers and modern operating systems to generate cryptographically strong passwords, passphrases and keys. Password managers do this every day. Anyone who has looked at how a modern OS seeds and maintains its CSPRNG knows that it continuously incorporates entropy from system and hardware events and exposes secure randomness once properly initialized. On a clean, freshly installed general-purpose OS, I am far more comfortable relying on a mature OS CSPRNG and well-reviewed cryptographic software than inventing my own entropy ceremony with dice. The bigger question for me is why we keep introducing specialized Bitcoin hardware in the first place. A device whose explicit purpose is securing Bitcoin creates targetedness. Manufacturers, payment processors, fulfillment companies, shipping providers and other third parties may now have economically valuable information about you: you probably own Bitcoin. If that data leaks, it can enable targeted phishing, social engineering, fake firmware or support messages, seed extraction attempts, SIM attacks, extortion or physical coercion — without anyone breaking the cryptography inside the device. The same trade-off exists with the current mantra of multi-vendor hardware-wallet multisig. Multisig can reduce key-compromise and correlated-device risk. But on the targetedness axis, every additional hardware-wallet vendor can add another manufacturer, customer database, supply chain, shipping provider, email system and specialized dependency to your threat model. If you wanted to create the biggest possible operational headache for yourself and your future heirs, one way would be to buy one device from every hardware-wallet vendor you can find. And there is certainly no shortage of them. You'd accumulate a huge specialized attack surface while repeatedly signaling to companies and their third-party providers that you are someone who takes Bitcoin custody seriously enough to buy dedicated signing devices. To me, that is completely backwards. Once you see the targetedness problem, you can't unsee it. My preference remains: Generic hardware. Linux. Bitcoin Core. Minimize specialized dependencies. Minimize targetedness. Minimize attack surface.
Very few people in Bitcoin seem to understand that a sophisticated attacker would not hide security flaws in an apps viewable source code. They would hide it in the prebuilt crypto binaries (AKA the thing that actually touches your private keys). These much more difficult to properly audit and its one of the many reasons why Bitcoin Core is the gold standard for the security critical functions of a Bitcoin Wallet (both generating secure keys AND signing). After "the incident" with coldcard, the overton window has shifted drastically towards entropy, but random enough entropy is only one small piece of what makes cryptography safe. Those of you that are overly focused on "entropy" and wanting to "roll the dice", are actually rolling dice on a single point of failure. Bitcoin Core is one of the very few projects that takes this seriously enough to actually pin its entire build toolchain with guix. This means that dozens of independent contributors can, on their own hardware, run the Guix build and publish their own signed hash attestation that the crypto libraries they ship are exactly what they claim to be. You simply aren't going to find this assurance in the rest of these projects, even the ones that look like they have a ton of github activity (i.e. open source review and contribution). They all rely on single points of trust, which is most often, trusting the one single party that built the crypto library isn't going to rug you with a backdoor. Bad actors will intentionally distract users from this by publishing attestations that prove nothing of substance. End users see a SHA256SUMS file and think verifying it gives them security... ...but the only thing it proves is that nobody messed with the app after it got strung together with some spooky crypto library compiled by some anonymous contributor in Ukraine.
11
17
3
146
34,546
Master on Bitcoin & Blockchain Technology (RIP) retweeted
Today was an excellent day for Bitcoin. It demonstrated perfectly that it worked as it supposed to work.
20
41
6
480
17,576
Master on Bitcoin & Blockchain Technology (RIP) retweeted
There is a critical vulnerability being actively exploited on BTCPay Server, which can result in the loss of funds. Please update your BTCPayServer to 2.4.2 by going to Admin Dashboard -> Server -> Maintenance -> Update & verify the 2.4.2 version string in the footer. If you are unable to update right away, turn off your BTCPay Server to prevent unauthorized access until you can update.
215
1,343
520
2,541
1,619,621
Master on Bitcoin & Blockchain Technology (RIP) retweeted
⚠️IMPORTANT⚠️In the next couple of days, a new shitcoin will fork off Bitcoin. It is a big security risk for people who just believe they will get an "airdrop" and want to sell it, to get more bitcoin. I will write more about it, but here is the TLDR: 👇
65
258
64
1,058
247,193
Master on Bitcoin & Blockchain Technology (RIP) retweeted
Please treat this as urgent. Follow the advisory for your model, upgrade your device, generate a new seed, and carefully move your funds. Help spread the word, especially to people who are less online and may not see this update.
🚨URGENT COLDCARD SECURITY UPDATE Read carefully before acting. 👉Mk3 seed generated on 4.0.1+ without ≥50 private, independent dice rolls: begin a careful migration now. 👉Mk4/Mk5 <5.6.0 or Q <1.5.0Q: update first, generate a new seed, then migrate. blog.coinkite.com/entropy-te…
202
251
31
696
258,846
Master on Bitcoin & Blockchain Technology (RIP) retweeted
1/ Earlier today, our Bitcoin engineering and security teams at Block began investigating reports of non-Bitkey wallets being drained. To proactively protect our customers, we began investigating immediately. Here’s what we found 🧵
93
496
145
2,058
1,571,362
Master on Bitcoin & Blockchain Technology (RIP) retweeted
Let's not forget we have Plebs on both sides of BIP-110. Let us civically and strongly disagree with one another and make each other better Bitcoiners.
2
3
16
500
Master on Bitcoin & Blockchain Technology (RIP) retweeted
I still would very much like to see both covenants and cross-input signature aggregation (CISA) on Bitcoin. Covenants strengthen self-custody. CISA strengthens privacy.
10
19
5
100
15,294
Master on Bitcoin & Blockchain Technology (RIP) retweeted
Criptomonedas explicadas en 24 segundos
8
185
2
1,625
79,481
Master on Bitcoin & Blockchain Technology (RIP) retweeted
El próximo viernes 26 de Junio el Bizkaia Aretoa de Bilbao acogerá a BITalks, el evento con el que cerraremos las VI Jornadas Bitcoin y Tecnología Blockchain. Más información en: jornadasbitcoin.org y bitalks.es
3
1
9
1,862
Master on Bitcoin & Blockchain Technology (RIP) retweeted
💻 Ataque a paquetes de Arch Linux [AUR] Alguien logró hacerse con el control de paquetes que llevaban tiempo abandonados, presentándose como sus responsables o adoptándolos de forma irregular. Una vez dentro, modificó los archivos de construcción de esos paquetes para que, al instalarse o actualizarse, descargaran un programa dañino capaz de robar contraseñas, claves SSH, tokens de GitHub y datos de navegadores y aplicaciones de mensajería. En sistemas con permisos de administrador, además, podía instalar herramientas para esconder su actividad. Lo que empezó como un aviso de más de 400 paquetes comprometidos subió rápidamente: las listas comunitarias y las comprobaciones oficiales hablan ya de más de 1.500 paquetes afectados en total. El equipo de Arch Linux reaccionó enseguida, eliminando las versiones maliciosas, bloqueando las cuentas usadas por los atacantes y pausando temporalmente algunas funciones del repositorio (como crear cuentas nuevas o adoptar paquetes). La situación está controlada en cuanto a nuevos envíos masivos, pero los desarrolladores siguen revisando y limpiando todo lo que pueda quedar. Importante: esto solo afecta a los paquetes del repositorio de usuarios (AUR). Los paquetes oficiales de Arch Linux no se han visto comprometidos en ningún momento. Si usas Arch o distribuciones basadas en ella, revisa qué paquetes tienes instalados del AUR y compara con las listas que han publicado la comunidad. El incidente se detectó el 11 de junio y la limpieza sigue activa varios días después.
3
17
2
79
4,793
Master on Bitcoin & Blockchain Technology (RIP) retweeted
🚨🤖🚨 For people that like trading sats p2p to get NKYC sats, it seems the main Robosats @RoboSats services are down for now. But it doesn't mean that Robosats the protocol stopped working ! Due to its conception it continues working even if the main "gateway" is down. You can still access it through all the @torproject .onion web apps hosted by coordinators of the community listed below: - Over The Moon : otmoonrndnrddqdlhu6b36heunmb… - FreedomSats: dqmmejfmtlve7d4ccohk4usriifd… The Big Lake : 4t4jxmivv6uqej6xzx2jx3fxh75g… Alice: alice7bqexhtnkiqhtgkuwgtzzfk… Of course if you are using your own self hosted web app thanks to @start9labs you are unaffected as well as if you are using the android/ @GrapheneOS Robosats app that are sovereign geteways to this amazing protocol
2
19
3
40
9,736
Master on Bitcoin & Blockchain Technology (RIP) retweeted
Se vienen tiempos interesantes para los amantes de la libertad.
This is what the UK spyware proposal means. There must be government spyware on every mobile device. It shall watch everything that happens, including always watching the screen, looking for things the government disapproves of. When anything is flagged by the software as something the government doesn't like, the software must block it from being sent or displayed (in realtime). The user of the device must not be able to shut this watching and blocking off. The only way to shut it off would be to ask the government or its proxies to do so for you, at their discretion. Therefore the whole device must be locked down. Administrator rights and the decision of what software or operating system to run or not to run must be taken from the owner/user and handed to the government and its proxies. Apple and Google are themselves working hard to lock down the devices they are involved in to shut out competition and establish a duopoly. The UK government says it is "working closely" with Apple and Google and currently they synchronise and coordinate their communication on this subject. The UK government is now proposing to mandate what would otherwise be illegal anti-competitive practices. @GrapheneOS on the Apple and Google duopoly: teapawt.net/GrapheneOS/status/2053… Statement from @signalapp teapawt.net/signalapp/status/20640… @ReclaimTheNetHQ on the state spyware: reclaimthenet.org/starmer-ca… The government announcement: gov.uk/government/news/new-p…
1
42
Master on Bitcoin & Blockchain Technology (RIP) retweeted
El camino en Bitcoin: Custodia propia + Nodo por privacidad + Baja preferencia temporal. Lo demás es quemarse en algún momento.
For those building a long-term self-custody Bitcoin position through dollar-cost averaging, this gets you more Bitcoin for the same amount of fiat. Value your wealth in the amount of Bitcoin and Gold you accumulate if you want to see through the optical illusion of fiat currency. A reminder: the financial industrial complex wants your Bitcoin in their custody, a loan against it, and your attention focused on gambling with ETFs, $MSTR, $STRC and perpetuals. Self-custody your Bitcoin. Run a node. Have a ten year plan, rather than a ten minute plan. Do the opposite of what they want you to do.
1
3
31
3,182
Master on Bitcoin & Blockchain Technology (RIP) retweeted
Sergi @abogadocripto, en relación a tu último vídeo, las acciones NO son activos reales. Son por definición activos financieros, es decir, lo opuesto. Las acciones son contratos que te dan derecho sobre algo. Los activos reales como Bitcoin poseen valor por sí mismos.
3
1
7
495
Master on Bitcoin & Blockchain Technology (RIP) retweeted
Lanzamiento de impacto. Tocará masticarlo y bajarlo al suelo pero tiene todo y más de lo que perdimos cuando detuvieron a los devs de Samourai Volvamos a construir con privacidad STOP THIS
¿Sabes qué revelan tus transacciones de Bitcoin? am-i.exposed te lo muestra. Es un escáner de privacidad on-chain que analiza direcciones y transacciones. 🧵
3
15
165
9,341
Master on Bitcoin & Blockchain Technology (RIP) retweeted
The Automated Build Server of @WalletScrutiny is now trying to build your Bitcoin wallets day and night, so you can be sure that the binary that you have on your phone or computer has been built from the sources published.
1
1
1
66
Master on Bitcoin & Blockchain Technology (RIP) retweeted
2 de Febrero de 1952. Nace Ralph C. Merkle, una mente equipada con tecnología interestelar. Criptografía, nanotecnología, criónica o fabricación molecular son sus juguetes favoritos. Acompáñame en esta loca #HistoriaCrypto 🛸
6
34
9
75