evie

BTC-10OCT26-50,000-B

@writenicecode do u have library for these icons?

Doing this still gives some minor layout shifts. rather use a absolute positioned flex centered element in a container with the original element to keep track of the width. Gives 0 layouts shifts and also works great with large font weights transitions

@kr0der for $200 ill give u unlimited fable dm me lol

might be time to actually get the $200 claude plan to use more fable 💀

@mamkindesigner @grok give me exact prompt of all of these screenshots

crazy claude mythos one shotted these App Store screenshots

@jxnlco wait lmao u can do this??

soemtimes it is that easy

@CoinGiggleMoe @Trader_XO lmao bottom isnt on this month

@Trader_XO very possible between today and tomorrow , maybe another small bounce into the news tomorrow before pulling the trigger

$BTC I'll be impressed if this works its way down to 57.5 today

@neoarz @interaction hi ceo

I've decided to step up as CEO of @interaction. Feel free to now email me at ceo@poke.com. (Joke btw I think it was a server error that allowed me to get 3 letter)

Claim your Poke handle today! 💌 poke.com/claim - Receive emails rerouted into your Gmail inbox today - We're gradually rolling out email sending - There's more to come later this month (samyok.poke.com) 👀

@ziwenxu_ i handle finance, bitch

btw the CTO handle is still up for grabs. whoever claims it, come down here and post a screenshot 👀

Poke let you claim any handle, so I claimed cofounders. Officially one of the founders now Congrats to me.

@ziwenxu_ congrats gang

@DennisChiuHK @coneticc @grok idk go ask your mom

@coneticc @grok how did he do it?

In just 12 hours I scraped 40,000 Instagram accounts, 6,500 with emails and phone numbers tied directly to their profiles. Meta, care to explain how this is possible through your own API? t.me/coneticlarp #Meta #Instagram #CyberSecurity #Privacy

@Meronix15 @SalsaTekila lmaoo

@SalsaTekila Yeah bro we already know you are stupid no need to post this braindead AI idea here thanks

**Claude, fix bitcoin, make no mistake** Bitcoin has a quantum problem, and the most popular fix is to freeze people's coins. There's a better way that takes nothing from anyone. THE PROBLEM Bitcoin is protected by digital locks. Right now, nobody can pick them. But one day a new kind of machine, a quantum computer, might get powerful enough to pick those locks and steal coins. Most of the fixes being discussed try to force everyone to move their Bitcoin by a deadline, then freeze the coins of anyone who didn't move in time. That breaks Bitcoin's oldest promise: not your keys, not your coins. THE IDEA Don't freeze anything. Build a lifeboat. Nobody gets pushed in. You choose to climb aboard. We make a twin of Bitcoin called QBTC. Same 21 million limit, same rules, except every QBTC sits behind a new lock a quantum computer cannot pick. Then we hand every Bitcoin owner a free matching coin and three years to claim it. HOW IT WORKS 1. You keep all your Bitcoin. Nothing is taken, frozen, or touched. This is the most important line in the whole plan. 2. For every 1 BTC you hold, you can claim 1 QBTC. Free. You end up with both: your original BTC, and a quantum-safe twin. 3. The new QBTC chain goes live on December 31, 2026. 4. You can claim anytime from now until December 31, 2029. After that the door shuts, and no QBTC can ever be created again. THE CLEVER PART (this is what makes it safe) Every other "move by a deadline" plan has a fatal flaw. While the door is open, a quantum thief could pick your lock and steal your claim before you get to it. BIP-362 fixes this with one simple trick: you claim your spot now, while the lock-picking machine still does not exist. Your claim gets stamped with today's date, sealed so it reveals nothing about you. Years later, even if a quantum computer shows up, it cannot travel back in time and stamp an earlier date than yours. Your spot was locked in before the threat was even born. The earlier you claim, the safer you are. THE PART NO OTHER PLAN HAS Other plans leave millions of old and lost coins, including Satoshi's, sitting behind pickable locks. To a future thief, that is a giant treasure chest. QBTC has no treasure chest. Coins nobody claims are simply never created. You cannot steal a coin that does not exist. So on the new chain, there is nothing for a quantum thief to take. Nothing at all. LET THE MARKET DECIDE Now two Bitcoins exist side by side: the old one, and the quantum-proof one. Nobody is forced to pick. Over time, people and miners move their money and their computing power toward whichever chain they trust more. If the quantum threat gets real, the safe chain wins on its own, with no committee, no confiscation, and nobody losing a coin. THE HONEST PART This does not fix the old Bitcoin chain. It can't. Those coins keep their quantum risk, and that is the trade. BIP-362 is not a patch, it is a clean escape, and it says so out loud. The deadline is also real: many experts expect a code-breaking quantum computer somewhere around 2030, so this is a race to get everyone safe before it arrives. That is exactly why you claim early. THE TIMELINE Now → claim your spot. Earliest is safest, and it tells the world you're in. December 31, 2026 → QBTC is born. 2027 to 2029 → claim anytime, and you become quantum-safe the moment you do. December 31, 2029 → the door closes forever. Nobody loses a coin. Nobody is forced. There is just a lifeboat, and a door that closes at the end of the decade. Climb in early. --- FOR THE BUILDERS (optional reading) - Signatures: ML-DSA (FIPS 204) by default, SLH-DSA (FIPS 205, hash-based) for cold storage and large holdings. - Mining: SHA-256d stays unchanged, so existing miners merge-mine from day one. Signatures are the quantum weak point, not the mining, so proof of work needs no change. - Claims: a sealed commitment made now, revealed later with a quantum-safe STARK proof, so you prove control without ever exposing your key. - No pre-mine. Total QBTC supply equals the sum of valid claims and nothing more. - Two-way replay protection via a unique fork ID, so old and new transactions can never cross over.

@RunnerXBT bring back 10/10 pls

this gotta be some of the most insane 24 hrs of this cycle

@backyardbound1 buy sir

@shakily -B?

BTC-10OCT26-50,000-B

@Rory_Shamrock @BigCheds why 40? 38 is the nail spot lmao

@BigCheds I remember your 12k beauty so I’m bidding at 40k lol

Not looking so crazy anymore? $BTC

@LexnLin ai is getting expensive top companies still havent profited anything only nvidia which sells shovels lmaooo isaiprofitable.com

wait there was a reset 7h ago 200x is down 6% weekly already damn 20x is going to be very hard and plus acc or pro lite, I feel the pain AI is getting expensive 😭

@CryptoParadyme this will be nuts x.com/shakily/status…

My next prediction. Bounce from here. Nuke resumes late June following Warsh's first FOMC and gatorade. Not as confident on this one as my March call, but let's see how it goes.

@nicdunz stop wasting water nic go to bed its your bedtime

having codex go through every frame of the openai video and finding secrets and deciphering things

@m13v_ @gabriell_lab how did u do the svg animated components?

@gabriell_lab the one-shot 'into existence' part is real now. iterating is where it gets messy, trying a variant means branching the chat without nuking the original. we built fazm so any claude code chat forks in one click with the full prior context. fazm.ai/r/xuzhxskz written with ai

Kind of crazy that you can just use Codex or Claude and vibe code things like this into existence

@chetaslua my beloved spark here u go again

🚨 GPT-5.5-Codex Spark Spotted They hinted at the fact that tomorrow is a HUGE release date 👀 one more thing they are hyping news stuff , tweet was deleted by openai employee check tweet in the comment

@CryptoParadyme 43k

maybe the only way to make people take me seriously is to send it to 50k