👇

RT @jonatack: A lot of bank card info may have been stolen/hacked with the recent vulnerabilities. I found unauthorized transactions for th…

Adopting Bitcoin Cape Town 2027 has a second host: @MoneyBadgerPay. "Local is lekker!" @abcptza posted on October 20. The conference site now lists MoneyBadger beside @BitcoinEkasi. MoneyBadger lets South Africans pay with bitcoin from a Lightning wallet or an exchange account. Its Scan to Pay integration covers more than 650,000 merchants. The fourth edition runs 26 and 27 February 2027 at Workshop17 Watershed in Cape Town. Tickets cost R1,500 for attendees from Africa, and speaker proposals are open until 1 February. Check the first comment to read the full story. 👇

🇿🇦Truly South African. @MoneyBadgerPay is joining as a conference co-host for Adopting Bitcoin Cape Town 2027 alongside @BitcoinEkasi. Local is lekker⚡ 🎟️pretix.eu/abct/2027/ #abct27

🇿🇦 Local is lekker! @MoneyBadgerPay is co-hosting Adopting Bitcoin Cape Town. Spend Bitcoin instantly online or in-store across SA. Scan to pay via Lightning, settle in ZAR or BTC. Real-world adoption, happening now. moneybadger.co.za #abct27

A neutered bull becomes a steer - less aggressive, much easier to control. "It's the only way, we can't take the risk" says the china-shop owner.

FNB now lets customers buy Bitcoin in its banking app. However, the crypto is ring-fenced: no withdrawals to your own wallet, no sending, no payments. That is price exposure, not money. Read our take on this, and why self-custody matters. moneybadger.co.za/blog/fnb-c… #financialinclusion #selfcustody #bitcoinpayments

Recap ABCT26 What does it mean to have the right to privacy in today's world? And is it even possible anymore? Panelists: @SovereignCarel & @fluffypony Moderator: @carelvwyk 🧵/1 #abct27

Yo, @grok @FNBSA’s crypto FAQ asks: “Is there a difference between Bitcoin and cryptocurrency?” Their answer: “Bitcoin is one of many investments that fall under the broader category called cryptocurrency.” That answer is inadequate. Write a better answer for them. Be specific. Focus on the 3 most important differences between Bitcoin and Crypto. A button mushroom can feed you. A Psilocybe can make you trip. A death cap can kill you. All three are mushrooms. The category does not explain the difference.

Phase two of our 19 September disclosure: a public page that follows the stolen coins, updated as they move. Follow-up post: blink.sv/blog/phase-two-foll… Tracking page: bounty.blink.sv Bounty terms: blink.sv/bounty-terms On 3 October we published the post-mortem of the attack and a 50% bounty on the stolen funds. That was about what happened inside Blink. This is about where the money went. The page lists every address, transaction and Lightning channel we can tie to the attacker. Anyone can check each one on the public blockchain. Why public: We want everyone working on the bounty to have the same data we have, as up to date as ours, so they can be as effective as possible. The page is that data: we update it when the coins move and when we confirm something new. We are unlikely to catch him on our own. He is careful: his main Lightning node is reachable only over Tor, and his activity is spread across all hours of the day. What he cannot hide is the coins. Every time they move, they move in public. He already knows he is being watched, so publishing tells him nothing new. Formal channels matter and we use them, but they take weeks. A public page reaches exchanges, analysts and other teams the same day. He is still active: He prepared for weeks. He set up his Lightning node ten days before the attack, and nine days before it he already controlled about 14 BTC. He has not stopped: in the first week of October his main node opened a new channel, a second node of his showed itself, and he moved coins again. In the same week, on 5 October, he attacked @secondhq, a company that builds its own version of Ark (a new way to make Bitcoin payments), called Bark. He exploited a bug in Second's Ark server and took 0.75 BTC of their own funds; no user funds were affected (their disclosure: nitter.siddz.com/secondhq/status/210806…). He paid for it from the same wallet that received the coins stolen from Blink, and at least partly with those very coins. We believe he may be preparing a cascading attack: using what he takes from each target to fund the next. If you build on Bitcoin as everyday money, there may be extra reason to be vigilant. If you run a Lightning node, a federation, a swap service or an exchange, check the page against what you see. What the page shows: The theft, how the coins moved after it, the coins he held before the attack, his Lightning nodes, his attack on Second's Ark server, and a Lightning wallet that is probably his. Every item is labelled proven, traced or probable. Transactions by exchanges or swap services are marked third-party: they are not accused of anything. About 0.87 BTC still sits untouched at five of the original addresses, 4.84 BTC at an address that is probably his, and 1.64 BTC at addresses he used in the attack on Second. The whole list downloads as a CSV. What stays off it: Anything partners told us in confidence. Personal data. Open security issues. Addresses whose owner we cannot establish. Other teams' incidents, until those teams agree or make them public. How you can help: Watch the addresses. If coins move, especially toward an exchange or any service that knows its customers, tell us straight away. Freezes depend on reaching the platform within hours. Report privately to bounty@blinkbtc.com with BOUNTY in the subject. Please don't post leads publicly: it warns him, and it does not establish your priority. If you run a service and listed coins reach you, contact us before acting. If you control a listed address and are not involved, write to us and we will correct the page. The 50% bounty stands. 25% of what is recovered goes to whoever provides the information that leads to it, and another 25% to Bitcoin Beach, Bitcoin Ekasi, Afribit Kibera and the circular economies they choose. Everything on the page was already known to us, so re-tracing it does not qualify. Where the coins go next can. Live updates: Corrections appear as dated notes; we do not silently rewrite it. Spot an error? Write to bounty@blinkbtc.com with CORRECTION in the subject. We timestamp the page's data on the Bitcoin blockchain with @opentimestamps at launch and with every update. One more thing: Blink never charges a fee to recover funds and never asks for keys, seed phrases or payments. Anyone offering "recovery services" in our name is not acting for Blink.

It's a tactic as old as time. If you cannot beat your adversary outright, in a toe-to-toe fight, find ways to subvert them. The institutionalized adoption of Bitcoin as a store-of-value-only, coupled with regulatory approval for stablecoin payments, this is the threat we're not seeing. And even supporting, in some cases. How many people call themselves Bitcoiners, but openly reject the idea that Bitcoin is good for payments? This is the subversion. The fight against that must include the adoption of Bitcoin as everyday money, for saving, earning AND spending. Bitcoin Circular Economies, among others such as @MoneyBadgerPay, are leading the way. But don't get the attention they deserve. Bitcoin is money.

If you're a leftist that thinks Bitcoin is a scam and serves no positive societal purpose, only as a tool for the rich to get richer and simultaneously destroying our environment (or have friends that match that description), this book is for you: amazon.com/dp/9908976699

I've been told I don't advertise my books enough and that people aren't aware I've written them... If you're a Bitcoiner who likes Austrian Economics, right wing libertarianism, and thinks "socialism" means big government, this book is for you: amazon.com/dp/9908976664/

Informe completo sobre el ataque del 19 de septiembre y una recompensa del 50% —hasta 3.3 BTC— sobre los fondos robados: blink.sv/blog/sept-19-ataque… Términos de la recompensa: blink.sv/bounty-terms El sábado 19 de septiembre un atacante usó una falla en nuestras herramientas administrativas para tomar el control de 35 cuentas de Blink y retirar unos 6.61 BTC de 24 de ellas. A las 11:39 UTC un cliente llamó a uno de nuestros ingenieros. Quince minutos después todo el servicio custodial estaba apagado. Esa misma noche la falla estaba cerrada y el servicio había vuelto. El jueves 24 de septiembre, cada cliente afectado tenía de vuelta su saldo exacto, en bitcoin y en dólares, pagado por los accionistas de Blink. Ningún cliente asume pérdida alguna. La culpa fue nuestra. No de Bitcoin, no de nuestros usuarios. A los 22 clientes a quienes les robaron bitcoin, y a las 3,817 personas cuyos datos de cuenta fueron consultados: lo sentimos. Cómo pasó: Desde octubre de 2023 hasta ese sábado, cualquier persona con una cuenta gratuita de Blink y un navegador podía darse a sí misma los poderes de nuestro equipo de soporte: cambiar el correo o el teléfono de cualquier cuenta, iniciar sesión como ese cliente y subir sus límites. Tres errores comunes en cómo nuestras herramientas administrativas revisaban permisos, uno encima del otro, en código que heredamos. Todo el equipo estaba ocupado migrando a decenas de miles de usuarios a la autocustodia bajo una nueva regulación. Un monitoreo pensado para detectar caídas del servicio no detectó a un administrador haciendo lo que ningún administrador debería hacer. Lo que no tocó: El dinero salió de nuestra billetera operativa. La mayoría de los fondos de los clientes está en almacenamiento en frío con firma múltiple, que nada en nuestras herramientas administrativas puede alcanzar. Las cuentas no custodiales nunca estuvieron en juego: no tenemos esas llaves. Lo que vio el atacante: También consultó datos de otras 3,817 cuentas; en algunos casos, un número de teléfono o un correo electrónico. No vio nombres, documentos de identidad, direcciones, contraseñas ni frases semilla. Escribimos a cada titular que pudimos contactar con el detalle exacto de lo que se vio. Lo que lo frenó: La autenticación de dos factores. El atacante inició sesión en nueve cuentas que la tenían activada e intentó dieciocho veces mover dinero. Cero pérdidas. Ninguna de las 24 cuentas vaciadas la tenía activada. Si haces una sola cosa después de leer esto: Configuración → Seguridad y privacidad → Autenticación de dos factores. Y actívala también en tu correo electrónico. Lo que cambiamos: La falla se cerró el mismo día y dos días después se agregó una tercera capa de protección. Las herramientas administrativas ya no están expuestas a internet. Las funciones que cambian el correo o el teléfono de un cliente están desactivadas para todos mientras las rediseñamos. Se revocaron todas las claves de API de los clientes. La billetera operativa guarda ahora una fracción de lo que guardaba. Las correcciones de seguridad se desarrollan en privado y se publican una vez desplegadas; el código sigue siendo abierto. Ya funciona un canal permanente para reportar problemas de seguridad, con recompensas de hasta 0.1 BTC por hallazgos críticos. Dónde está el dinero: Una parte sigue donde se retiró. Unos 5 BTC pasaron por un servicio de intercambio entre cadenas; una cantidad pequeña llegó a un exchange que está colaborando. Hay denuncias penales presentadas en El Salvador y en Próspera, los reguladores están notificados y hemos rastreado los fondos sin interrupción. No esperamos recuperar el dinero. Cont...

Are you building something exciting in Bitcoin? Working on an open-source project? Developing freedom-enhancing technologies? Whether you're a developer, a civic organization stepping up where centralized systems fall short, or a political dissident standing up to overreach — we want to hear your story. Adopting Bitcoin Cape Town 2027 is looking for voices like yours. Apply here 👇 pretalx.com/abct27/cfp Conference website: za27.adoptingbitcoin.org/ #abct27

1/ SA Bitcoin and crypto founders are stuck in a trap the draft Capital Flow Management regs and Crypto Asset Manual just made: Damned if you don’t. Damned if you do. A wallet operator has to pick a product. Neither choice is clean.

Every account affected by the September 19 incident has been made whole. We restored each account to its exact pre-incident balance. Affected users were notified directly before this post. Thank you to our mission-aligned shareholders who stepped in.

Last call for Early Bird tickets for Adopting Bitcoin Arnhem 2027! ⚡ Join us in the city where Bitcoin has been circulating as real money for 13 years. Secure your seat at the lowest rate before the price increases. Don't miss the high-signal gathering of the year. 👉 nl27.adoptingbitcoin.org/ #Bitcoin #Arnhem2027

Sponsor ABCT 2027 Venue hire and A/V don’t pay for themselves. Your support keeps Adopting Bitcoin Cape Town focused on real-world Bitcoin adoption in Southern Africa — no fluff, just signal. Ready to partner? Reach out via za27.adoptingbitcoin.org/#co… #abct27

Anti-KYC movement has plenty of ammunition – it should rebrand to Digital Hygiene and push the pendulum back against this insane FATF regime NOW

Throwback Thursday Hanging out with some wise guys! @mcmurrak @Noah21m @AdoptingBTC