12 bitcoin security levels: - level 0: on an exchange. You don’t really own anything. - level 1: hot storage on a closed source shitcoin wallet (like @Ledger) - level 2: hot storage on an open source bitcoin only wallet (like @bluewalletio or @SparrowWallet) - level 3: cold storage on a usb hardware wallet with shitcoin support - level 4: cold storage on a bitcoin only usb hardware (like @COLDCARDwallet mk4 or @BitBoxSwiss) - level 4: cold storage on a bitcoin only airgapped hardware wallet without reproducible builds (like @KeystoneForBTC) - level 5: cold storage on a bitcoin only airgapped hardware wallet with reproducible builds (like @foundationhq Passport) - level 6: analog-only airgapped cold storage (Passport supports this) with self generated ephemeral seed - level 7: cold single seed + passphrase (protect against seed compromise) - level 8: Shamirs secret sharing cold single seed (protect against seed compromise & introduce fault tolerance) - level 9: hybrid 2/3 multi-sig with 1 hot key - level 10: full cold 2/3 multi-sig - level 11: hybrid 3/5 multi-sig with 1 hot key - level 12: full cold 3/5 multi-sig Could be split up further but might not make a lot of sense. Bonus points for connecting to your own node at any level. I’m sure many will disagree somewhere. What would you change? What would you remove or rank differently? Note higher security is not always the best fit for your situation.

I don't know if you realize what just happened. Elon Musk is completely bypassing the State. For 100 years, we've been told the problem is capital. That it must be captured, taxed, redistributed. With an army of intermediaries standing between those who create wealth and the people: ministries, agencies, commissions, bureaucrats. Musk is doing the opposite. He's taking his capital and giving it directly to the people. One SpaceX share to every kid in America. Not a handout. Not a subsidy. A piece of the machine that's taking humanity to Mars. And he says it himself: this is the first of many. Mises understood this back in 1944: the bureaucrat creates nothing. He administers what others created, following rules that have no connection to the value produced. The day value flows directly from the one who creates it to the one who receives it, the bureaucrat has no function left. That's what's being born right now. A new liberal world order, where the very concept of the State will make less and less sense. The world we're entering is a world of abundance. AI, robots, energy, space. And that abundance won't come through the State, for one simple reason: we have a century of proof that it doesn't work. Redistribution was version 1.0. Direct distribution of capital is 2.0. While France is still debating how to tax builders even more, America is handing stock to its kids. Pick your side.

AI predictions for next 6-9 months -> Anthropic/ OAI fail to ban OSS in the US -> Anthropic/ OAI continue to innovate product but stall on fundamental tech breakthroughs -> SOTA Gemini 4 launches at 10x lower cost -> Elon open sources Grok -> Anthropic/ OAI ARR growth stalls as enterprises move from tokenmaxxing to rational token consumption/ OSS -> slow realization in public markets that AI may not replace human labor in next 1-3 years/ has not had a fundamental tech breakthrough in over a year/ lacks ROI/ AI hyper and lab spend not durable -> moonboy VCs/ hedge funds/ softbank continue to fund Anthropic/ OAI equity raises in private markets as public markets for them are now fully closed -> CXMT, YMTC announce capacity expansions significantly above market expectations -> hypers deliver good q326 results on first look but fail to show meaningful AI ROI, guide to "significant capex expansion in fy27" -> broad realization in public markets the AI dream we got sold on is not anywhere close to realization -> 10yr hits >5% -> hyper bonds reprice >10%, CDS hit 3x current levels, and AI credit market dries up as market realizes GPU ABF was not a good idea -> hyper equities reprice 30-50% lower -> ORCL falls below $30 as rumors of bailout make the round -> market realizes memory is cyclical and LTAs won't hold -> 50% of korean traders get wiped within a week -> hypers cut fy27 capex -> semis reprice >80% lower -> fed cuts >150bps to avoid recession

This could be you and me and we couldn't know the difference.

I totally get the offline laptop thing, I did exactly that for my earliest cold storage. But with what is coming to SeedSigner, SpecterDIY, Krux and Kern, these microcontroller projects are going to offer increasingly decisive advantages over the offline laptop approach. With support for dozens of development boards any association with bitcoin goes away so you sidestep all of the supply chain risk; you lose the attack surface of an entire microprocessor OS + app; you get better assurances wrt wireless comms being truly disabled; you can get something brand new still at a very low cost; the form factor is much easier to use and store; and the UX becomes much more intuitive and specialized like a HWW rather than a general purpose computer/OS. The advantages of FOSS + DIY are going to become undeniable.

Intoxicating. I’ve been programming for 45 years, since so was 10. I’ve been a pro game coder for 33 years. Everything from hand coded assembly to UE 5.8. The paradigm shift to agentic coding is intoxicating. It is the biggest productivity jump I have ever experienced.

How the fuck is this even possible

Honestly what else even comes close to feature parity of Claude Code Desktop? Especially the mobile handoff is unparalleled, what are you using that’s not this and you think is better & why? Honest question

Some of the shit I'm cooking with Claude right now is truly insane. None of this should be possible. None of it will matter but I'm having the time of my life right now

This is wild

The bottom is in, or the world is about to end. #Bitcoin

Invoking multiple Claude Max subscriptions straight from your mobile is so OP Obviously as remote control on your VPS as continuous systemd processes Obviously

I wrote code. Now I face 45 years in prison because others misused it. Code that no one controls. Code that no one can change or shut down. Yet somehow, I’m being held responsible for what others chose to do with it.

Now watch mainstream highligh how unusably short the new Tesla roadster will be able to fly to bypass real city traffic utterly unphased by the revolutionary tech being introduced by a fucking car kickflip. Historic Elon is the greatest engineer to have ever walked the earth

Every week someone tells me they vibe-coded their app over the weekend and don't need developers anymore. Before it touches a paying customer, make sure it includes: > a schema someone designed, instead of one the AI improvised table by table > login that still works when someone puts a plus sign in their email > password reset links that expire and work once > MFA, plus a recovery path for the user who lost their phone > sessions that time out, and a way to kill every session for one user > SSO for the enterprise customer who won't sign without it > SAML, because that customer's IT team doesn't do magic links > SCIM, so a fired employee loses access the moment IT offboards them > roles and permissions deeper than "admin" and "everyone else" > checks that stop user A from reading user B's data by changing one number in the URL > tenant isolation, so one customer's bug never shows another customer's records > an admin "log in as this user" button for support, with an audit trail on every use > rate limits on login, so nobody can guess passwords at scale > lockouts that stop attackers without locking out your CFO the night before the board meeting > database migrations that run forward and roll back > migrations that don't lock the main table at 2pm on a Tuesday > indexes, because the query that was instant on 50 test rows times out on 5 million real ones > connection pooling, so a traffic spike doesn't exhaust the database > backups every night > a restore from those backups, tested, because a backup you've never restored is a hope > point-in-time recovery for the day someone runs a delete without a where clause > soft deletes, so "I deleted it by accident" is a support ticket and not an incident > validation on the server, not just in the form > timezones stored right, so the 9am reminder doesn't fire at 4am > the customer with an apostrophe in their last name > emoji, accents and right-to-left text in every field > money stored as integers, because 0.1 + 0.2 doesn't equal 0.3 in floating point > currency, rounding and tax rules for every country you sell into > a data model that survives your second customer asking for "one small change" > idempotency keys, so a retried payment doesn't charge the card twice > deduplication for the user who clicks submit four times > pagination that still works on page 400 > exports, because sooner or later every customer wants their data in a spreadsheet > imports that survive the CSV someone saved in 2009 > retention rules, and code that deletes what your contract says you'll delete > secrets out of the code, out of the repo and out of the AI chat history > rotating every key the AI pasted into a config file last month > confirming every package the AI installed exists and is the one you meant > dependency scanning, because the AI pulled in libraries nobody reviewed > input sanitization everywhere a user can type > protection against SQL injection, XSS, CSRF and the rest of the OWASP list > file uploads that get scanned, size-limited and stored where they can't execute > CORS rules that aren't "allow everything" > security headers on every response > encryption at rest and in transit > least-privilege access for everyone, including the AI agent holding production credentials > logs that record who did what, without recording passwords, tokens or card numbers > a penetration test before your enterprise customer's security team runs their own > answers to the security questionnaire every enterprise buyer sends, with evidence behind each one > a disclosure process for the day a stranger emails you a vulnerability > a plan for the day a laptop with production access gets stolen > SOC 2, which means policies, evidence and an auditor, not a checkbox > HIPAA, the moment a single patient record touches your system > a BAA with every vendor that touches that data, including your AI model provider > audit trails that show who viewed a record, not just who changed it > PCI scope, and card numbers kept out of your database > GDPR deletion requests that reach every table, backup and log > data residency for the customer whose contract says EU only > quarterly access reviews someone signs off on > dev, staging and production environments that match each other > infrastructure written as code, so the setup lives somewhere other than one person's memory > a deploy pipeline that runs the tests before anything reaches customers > one-click rollbacks, because Friday deploys happen > zero-downtime deploys, because your customers don't have maintenance windows > feature flags, so you can ship the code without shipping the feature > autoscaling for the Monday morning spike > a CDN, so the app loads fast in Singapore too > DNS, SSL certificates, and renewals that don't expire on a Sunday > background job queues, so slow work doesn't freeze the page > retries with backoff, so one flaky API call doesn't become a lost order > a dead-letter queue for the jobs that fail every retry > cron jobs that don't run twice the day you add a second server > caching, and clearing that cache when the data changes > SPF, DKIM and DMARC, so your password resets don't land in spam > bounce and complaint handling on every transactional email > storage rules, so you stop paying to keep 2021's temp files > cost alerts, so a runaway agent loop shows up the same day and not on the invoice (we learned this one for $1,382.59) > a disaster recovery plan, written down and tested once a year > a second region, if your contract promises uptime one region can't deliver > structured logs you can search at 3am > error tracking that groups the same bug instead of sending you 4,000 emails > uptime checks from outside your own network > alerts that page a human, tuned until they stop paging for nothing > dashboards for latency, error rate and throughput > tracing for one slow request across every service it touches > an on-call rotation, and a person who picks up > runbooks, so the engineer on call knows what "queue depth critical" means > postmortems that change something > a status page customers check before they email you > unit tests written by someone who knows what the logic should do > integration tests for every third-party API you depend on > end-to-end tests for signup, checkout and the other flows that make you money > load testing before the launch email goes out > test data that looks like production without being production data > regression tests, so fixing bug 41 doesn't bring back bug 12 > testing on the five-year-old laptop your biggest customer's ops team still uses > accessibility compliance, because the enterprise contract requires it > subscriptions, upgrades, downgrades and proration > failed-payment retries and dunning emails > invoices with the customer's PO number on them, because procurement won't pay without it > sales tax and VAT > refunds, credits and partial refunds > usage metering that matches what you bill, to the cent > annual contracts with custom terms your billing logic never planned for > revenue reports your finance team can reconcile > webhooks that verify signatures > webhooks that retry, with a log of every failed delivery > a versioned API, so you can change it without breaking your customers' integrations > API keys customers can create and revoke > API rate limits that protect you without blocking real integrations > a plan for the day a third-party API changes its response format without telling you > OAuth token refresh, because tokens expire at the worst possible moment > a sandbox where customers can test their integration > protection against prompt injection in every field that reaches the model > customer and patient data kept out of prompts that leave your network > a model spend cap per customer, so one heavy user can't run up your bill > evals, so you find out when a model update makes your answers worse > a fallback for the afternoon your model provider goes down > a migration plan for the day your model gets deprecated > prompt and output logs for debugging, minus whatever you're not allowed to keep > a human approval step for anything the AI does that can't be undone > pages that load on hotel wifi > empty states, loading states and error states on every screen > error messages a customer can act on, instead of "something went wrong" > forms that keep what people typed when one field fails validation > emails that render in every mail client your customers use > notifications people can turn off > undo > keyboard navigation and screen reader support > translations, with dates and numbers formatted for each locale > a back button that does what people expect > code a human can read > code review on every change > a branching strategy, so two people can work without overwriting each other > monthly dependency upgrades, so you're never two major versions behind > framework upgrades before the old version stops getting security patches > deleting the dead code the AI left behind from its first three attempts > splitting up the 2,000-line file the AI kept appending to > architecture decisions written down, with the reasons > a README that gets a new engineer running locally in under an hour > documentation for whoever inherits this > an admin panel for your ops team > support tooling, so customer success can answer questions without pinging engineering > a changelog customers can read > terms and a privacy policy that match what the code does > every account, domain and repo in the company's name, not the name of whoever built the prototype > a bus factor higher than one Oh, and besides keeping all of this working every day, forever… your vibe-coded app will still need people who know what they're doing: > reading every line the AI wrote before it ships (a senior engineer) > designing the data model before your second customer breaks it (a backend engineer) > explaining why the AI's fix for one bug created two new ones (a senior engineer, again) > deploys, rollbacks, servers and the cloud bill (a DevOps engineer) > answering the page at 3am when payments stop (whoever's on call) > patching the framework the week a vulnerability goes public (security) > walking an auditor through how patient data moves (security and compliance) > testing what the AI says it tested (QA) > running a migration on a live database without losing a row (a backend engineer) > saying no to the feature that breaks three others (a tech lead) > turning "works on my laptop" into "works for every customer at once" (an architect) > debugging the code when the AI that wrote it can't (a senior engineer) > remembering why it's built this way, a year from now (someone who was there) …wishing them the best 🫡

Out of all the shit devices out there Tangem is the shittiest Honestly worse than Ledger And that’s saying smth Blind signing and fully closed ecosystem are so fucking fiat

This is toxic and disingenuous. Tangem is misleading so many folks who don’t know better. Gaslighting the industry for years. Blind signing has a clear definition. This product is a glorified 2FA hot wallet and doesn’t protect from the most simple type of attack: a compromised phone or computer.

MultiSig does not need to be expensive. You can use one hot key on your phone and a single 3D printed Cardsigner with 2 @satochip Seedkeeper cards as the 2 cold keys. Total cost: €235 Available at the Bitsaga website Premium CNC aluminium Cardsigner real soon!

Proper multisig does not depend on third parties Sorry not sorry

Remote control on a continuous process on your VPS from Claude Desktop is the best way to run an agent, change my mind. And it just got even better.