Just gonna say it how it is… If you HODL and never spend or use your bitcoin, you are a spectator, not a participant. Bitcoin’s price goes higher when more people accept it as payment. If you want NGU, spend and replace. Get in the game.

You assist the system, when you're self destructive You beat the system, when you are not I need more people to consider that sometimes

With the way things are changing, if you blow your money right now it's going to be harder to make it back unless you are very well connected, have high paying skills, have some technical skills, or are very exceptional in media, sports, politics, etc Be wise

You saved for the down payment. By the time you got there, the house needed a bigger one. That’s the part folks leave out when they say “just save more.” New BitWalk tomorrow. We talking purchasing power and why I keep bringing up Bitcoin 🍊.

Most of us found Bitcoin through a friend, a podcast, or a rabbit hole online. But how many people found it because a painting stopped them in their tracks? Or a song touched their heart? That's why we bring culture to Bitcoin conferences. Full convo with @thekylehuber @WeAreSatoshiPod 👇 youtu.be/w5x1dTXvX4E?t=3417

Dems are washed up. 🎷

KEYSTONE TO DESTROY 18,835 HARDWARE WALLETS AFTER HACKERS STEAL DEVICE AUTHENTICATION KEY Keystone has confirmed it will destroy 18,835 hardware wallets in existing inventory after attackers stole the cryptographic key used to verify the authenticity of its devices. The breach is particularly concerning because the stolen key could allow attackers to manufacture counterfeit Keystone wallets that successfully pass the company's official authenticity checks, potentially putting users' Bitcoin at risk. The key is permanently embedded in existing devices and cannot be erased or replaced, forcing Keystone to destroy its remaining inventory, suspend shipments and manufacture new devices with a replacement key. The company says attackers exploited a vulnerability in a third-party monitoring tool on its official website on October 20, gaining access to: - 25,964 customer records containing names, contact details, shipping addresses and purchase information. - 12,873 abandoned checkout records containing potentially sensitive customer information. Keystone also acknowledged that its automated data deletion system had failed, leaving customer information stored beyond its stated retention period. The company says recovery phrases, private keys and transaction signing were not compromised. Devices delivered before October 20 remain unaffected, but customers receiving devices with the old authentication key after that date are advised to seek additional verification. Keystone has suspended shipments, begun notifying affected customers and is moving production to a new authentication key.

BREAKING: Elon Musk says debt markets have “almost entirely shut off” access to money for any company without substantial revenue independent of AI data centers. Neoclouds are going to see “guppy-level death and consolidation,” Musk says.

40 reasons to choose Bitcoin

INVESTIGATION UPDATE Many of you have asked how personal information ended up in the phishing emails, particularly those who ordered from us years ago. Here is what we have found so far. Phishing emails: We have identified more than 23,000 phishing email attempts across our email systems, including 19,057 messages delivered through Mailgun and 1,503 messages sent through Google Workspace. Some addresses received multiple messages, and some attempts failed or were stopped before delivery. These numbers do not tell us how many people had personal information exposed. We are still determining that number and will share it once we can confirm it. Older orders and abandoned carts (WooCommerce): Before moving to Shopify in May of this year, our store ran on WooCommerce. We had configured automatic redaction of customer details 60 days after shipping. When we viewed those orders in our store admin, the customer details were no longer visible and the orders showed as redacted. During past database migrations, orders were copied into a new set of tables, but copies remained in the old tables. The redaction process updated the newer tables, which were also what our store admin displayed. Orders therefore appeared redacted even though older copies still contained personal information. We also found personal information in other order and refund records, as well as abandoned carts. This included shipping details entered by someone who never completed a purchase. We are still checking the historical settings and redaction process to understand why these records retained data. Those older records were held in systems the attackers were able to reach. We relied on the redaction shown in our admin dashboard, and we now know that was insufficient to verify that the underlying data had been removed. Whatever the shortcomings in the tools we used, protecting your information was still our full responsibility. We plan to share our findings with WooCommerce and the relevant plugin developers. When an order is marked as redacted, its personal information should not remain in another table in the same database. For other WooCommerce store owners: do not rely solely on what your admin dashboard shows when personal data is redacted. Have your developer or agent check the entire database for information left behind, including legacy tables, refund records, and abandoned carts. This is especially important if you have used WooCommerce for years or have been through database migrations. Recent orders (Shopify): Customer details from orders placed on our Shopify store since May may also have been exposed. We are still investigating the extent of any unauthorized access. These orders had not yet been manually redacted. We updated our privacy policy when we moved to Shopify and were building a tool to automate redaction, but automatic deletion was not yet active. Other possible sources: We have received reports of phishing emails containing personal details that customers say they never shared with us. We are investigating whether the attackers combined information from our systems with data obtained elsewhere, but we have not confirmed a connection to breaches at other companies. Historical support records are also part of our investigation. What we have done: We have revoked affected email credentials, cleared queued phishing messages, and taken affected legacy services offline while preserving evidence. Our investigation into the full extent of the compromise is continuing. We have found no evidence that this incident compromised Passport devices or the private keys they hold. The phishing emails are designed to trick you into revealing your recovery phrase, and including your correct personal information makes them more convincing. Never enter your recovery phrase into a website or share it with anyone, including someone claiming to be Foundation. We will continue sharing confirmed findings and publish our full report when the investigation is complete.