Pourquoi Bitcoin est t’il volatile ? D’abord, toutes les « cryptomonnaies » autre que Bitcoin sont tout aussi volatile. C’est donc une caracteristique propre à l’instant T, commun au nouveau marché global des cryptomonnaies. Mais alors, pourquoi ?

L'OTAN ne s'est pas déplacée toute seule vers les frontières russes. Des États souverains ont demandé à la rejoindre parce qu'ils craignaient la Russie. Et depuis la Géorgie en 2008 et l'Ukraine en 2014 puis 2022, difficile de prétendre que cette crainte était imaginaire.

Pourquoi est ce qu’on pourrait pas bénévolement donner accès à notre puissance de calcul pour améliorer un LLM open source ? Et contribuer à son développement collectivement

En août 2026, les Russes se sont précipités pour retirer leur argent des banques, dans ce qui s’apparente à un « bank run » inédit, alimenté par la peur d’une saisie de l’épargne par le Kremlin. Gabriel Gervais décrypte ce phénomène. desk-russie.eu/2026/09/06/le…

🚨🇫🇷 ALERTE INFO | Le Conseil Constitutionnel CENSURE l’interdiction des réseaux sociaux aux moins de 15 ans, estimant que la proposition avec vérification de l’âge est CONTRAIRE à la Constitution. L’article est donc supprimé, malgré l’adoption par le Parlement.

Today, we are releasing BTCPay Server v2.4.3-rc4, a security update addressing vulnerabilities reported by the Bitcoin Red Team, @ProjectLoupe, @MagicGrants, @Premai_io, and independent researchers. This release follows several days of nonstop work, review, and testing. It was built from our temporary private security repository, but to make these security fixes available as quickly as possible, we are releasing the Docker image publicly now. This is a release candidate, so bugs may still be present. NFC is now opt-in, and the Phoenixd plugin is temporarily incompatible with this release. Please report any issues to the team. We will document behavioral changes within the main release. Despite its RC status, we strongly recommend upgrading now using the standard process: Server Settings > Maintenance > Update or run or run btcpay-update(.)sh from the command line, removing the parentheses If no significant issues are reported, the release candidate will be tagged as v2.4.3 and fully open-sourced within the next 48 hours.

Facts: you’re a shitcoiner and your opinion is dismissed

Donc les finances publiques se sont fait hack (comme tant d’autre services de l’état) leur base de données A 18 jours de l’obligation de fournir sa CNI pour accéder aux réseaux sociaux

Today, Bitcoin Policy Institute and a broad coalition from across the digital-asset ecosystem are publishing an open letter calling on the world’s leading AI labs to provide qualified open-source defenders with trusted access to frontier AI models. The past several weeks have made the need for this abundantly clear. The people defending digital-asset infrastructure and open-source software need access to the latest AI capabilities to perform comprehensive security reviews and stay ahead of increasingly sophisticated adversaries. The coalition includes open-source development organizations, major custodians, treasury companies, payment services, security firms, capital allocators, and others whose businesses and customers depend on the integrity of open-source infrastructure and libraries. Open-source defenders often occupy the least privileged position in the AI security landscape. They have limited access to the strongest internal cyber models and are frequently blocked by guardrails when using publicly available frontier systems for legitimate security research. As a result, they often resort to less capable open-weight alternatives. We are urging frontier AI labs to establish a clear, trusted pathway for qualified open-source and digital asset defenders to access their strongest capabilities, with sufficient compute and secure environments to conduct meaningful security reviews. Frontier AI could become one of the most powerful defensive technologies ever developed, but only if defenders get fair access to those systems. It’s time to give defenders the tools they deserve. Read the open letter, add your organization, or sign as an individual on our website at btcpolicy.org/ailetter

Plutôt convaincu que le phénomène ovni est un programme militaire (secret), les rapports montrent des vitesses de 6 à 8k km/h le record (humain) via drone étant de 11k km/h..

the internet may become a dark forest

thank you red team 🚩 for securing public bitcoin infrastructure it’s been almost an entire week of non-stop hunting for vulnerabilities and disclosures we’ve seen shit together some of the most insane shit i’ve ever seen in my life you’re incredible beings keep going

T-minus 11 hours! The final countdown: bip110.com

Triste à dire mais on ne peut envisager le futur du paiement avec ce genre de news régulièrement..

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.

🎁CONCOURS DE L'ETE 🎁 Le CM part en vacances et il a décidé de vous régaler. Pour bien préparer la rentrée, quoi de mieux qu'une magnifique carte @AsusFrance PRIME GeForce RTX 5070 12GB GDDR7 OC Edition !☀️ Pour participer : 1️⃣ Suivez @ldlc 2️⃣ Retweetez ce post Tirage au sort à partir du 24 août ! La carte est ici 👉 ldlc.com/fiche/PB00669231.ht… SPOIL : le graphiste est déjà en vacances !

We can probably learn a thing or two from these guys.

cyber security has changed forever. bitcoiners are the first wave of victims and there’s likely going to be a lot more. assume everything is broken.

Here is the JSON export of my Coldcard hack mapping analysis from the past few days. This represents dozens of hours of on-chain investigation. So far, imo, three main patterns appear to emerge: 1) an initial wave of five clearly scripted hacks, followed by UTXO consolidation. The bitcoin linked to these transactions remains untouched for now; 2) a much noisier and more erratic pattern: numerous addresses, repeated consolidations with no obvious rationale, and several questionable fund movements. Some bitcoin eventually reached: -> a cluster linked to Chivo Wallet and Binance; -> six transactions involving ChangeNOW; -> one Bitcoin service using CoinJoin, with outputs later connected to Binance; 3) several additional waves resembling the first pattern. Once again, the bitcoin associated with these transactions has not yet moved. My current working hypothesis is that there may be: - a first attacker using scripts to execute transactions in batches; - a second attacker behaving far less carefully, making privacy mistakes and moving funds in ways that are difficult to interpret; - potentially one or more additional attackers (or possibly the first attacker again) who have not yet moved the bitcoin because they know the transactions are being closely monitored on-chain. This remains a preliminary assessment, and attribution is still uncertain. Since the latest hack-related transactions have not yet been consolidated, I am going to step back from the manual mapping for now. However, I now have a mempool-monitoring system running 24/7, with alerts for any transaction involving addresses or UTXOs included in my map. Happy to assist further if useful: @_SEAL_Org @Rob1Ham @intangiblecoins @w_s_bitcoin @SaniExp @zachxbt @nvk @chainalysis @clay_garrett @LaurentMT 👉 To generate the visual map, provide the JSON file to an LLM and ask it to build the graph. I have also included a prompt which could be used so the process can be reproduced. fromsmash.com/Map-analysis-C… I hope there will be a way for the Bitcoiners who lost funds to recover them 🧡

This is the part where I remind folks once again that every hardware vendor is fallible. If you want to hedge against vendor risks and supply chain risks, the solution is multi-vendor multisig. We have plenty of coldcard users over at @CasaHODL and this event will just be a minor annoyance for them to rotate out the compromised key with a securely generated one.

In response to India's recent ban of the Bitchat source code on GitHub, there are now - 50 nodes seeding the code on Radicle, an unstoppable peer-to-peer alternative to GitHub - 25 copies on GitHub - copies on codeberg, gitlab, gitlawb, and more Thank you, I guess?