Best crypto stories on Kiwi News this month

Submit
BEST · PAST MONTH

The best of the month.

The stories the Kiwi community upvoted most over the past month.

This month
iPhone betaKiwi News for iPhoneOpen TestFlight

Page: 6

@IntCyberDigest
@IntCyberDigest

❗️ Crypto mixer Railgun ignored a US lawsuit claiming it laundered North Korea's stolen crypto, and is now in default. The plaintiffs are victims and families holding $865M in US terrorism judgments against North Korea. Courts found it abducted a US permanent resident pastor in China in 2000 and tortured him to death, and backed Hezbollah's 2006 rocket attacks on Israel. They say Railgun should have frozen North Korea's funds so they could seize them. The FBI says North Korean hackers laundered $60M+ through Railgun in January 2023. The suit claims ~70% of the money it handled was North Korea's.

Tweet image
241x.com

@IntCyberDigest: Railgun defaults in US lawsuit over North Korean crypto launder

@IvanPerezF_
@IvanPerezF_

🚨 Fallo crítico en el kernel de Linux: se puede atacar por red, sin login y sin necesidad de ninguna acción por parte del usuario. CVE-2026-98432 
➡️ CVSS 9.8 (crítico) 
➡️ Afecta a la gestión de conexiones TCP/IPv4, el código que atiende cualquier conexión a tu servidor. 
➡️ Ubuntu marca vulnerables desde la 16.04 hasta la 26.10, también los kernels de AWS, Azure, Google Cloud y Oracle. 
➡️ La corrección todavía está «en preparación» en casi todas. Si tienes un servidor o un VPS con Linux, sigue los avisos de tu distribución y actualiza el kernel (y reinicia) en cuanto salga el parche. https://ubuntu.com/security/CVE-2026-984…

242x.com

@IvanPerezF: Critical Linux kernel TCP/IPv4 flaw, CVE-2026-98432, CVSS 9.8

243x.com

@JasonDClinton: Scaling laws will push cyber capabilities into small, cheap mode

@LLMSherpa: Probably bullshit, but claimed Ant leak on HF

@M25Marek
@M25Marek

𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝗶𝗻𝗴 𝗡𝗲𝘁𝗵𝗲𝗿𝗺𝗶𝗻𝗱 𝗟𝗶𝗴𝗵𝘁 𝗖𝗹𝗶𝗲𝗻𝘁 Trustless RPC for every wallet. Verify Ethereum yourself, without running a full node. 𝗛𝗼𝘄 𝗶𝘁 𝘄𝗼𝗿𝗸𝘀 → One trust anchor: a recent finalized beacon block root → Consensus: sync committee updates over libp2p, with signatures and Merkle branches verified → Execution: state on demand through SNAP, every range proven against the state root → Performance boosted through partial state caching for selected and frequently queried accounts. 𝗕𝘂𝗶𝗹𝘁 𝗼𝗻 𝗯𝗮𝘁𝘁𝗹𝗲-𝘁𝗲𝘀𝘁𝗲𝗱 𝗡𝗲𝘁𝗵𝗲𝗿𝗺𝗶𝗻𝗱 𝗰𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀 → eth_call and eth_estimateGas run locally in the Nethermind EVM, nothing forwarded → Developed inside the Nethermind client codebase → Glamsterdam-ready 𝗙𝗼𝗿 𝘆𝗼𝘂, 𝗶𝘁’𝘀 𝗷𝘂𝘀𝘁 𝗹𝗼𝗰𝗮𝗹𝗵𝗼𝘀𝘁:𝟴𝟱𝟰𝟱 Point MetaMask, or any wallet, at it. In active development. Congrats @__flcl and the team. Follow the progress and share feedback: https://github.com/NethermindEth/netherm…

Tweet image
245x.com

Introducing Nethermind Light Client, a trustless RPC for Ethereum wallets

246x.com

@NSACyber: Organizations using PHP should prepare for update fixing two critical

247x.com

@OpenAI: OpenAI models helped find critical PHP security flaws before disclosure

@OpenAI
@OpenAI
Replying to @OpenAI

Starting today, GPT-6.2 Astra and Sol are available in ChatGPT Work and Codex for Plus, Pro, Enterprise, and Edu users. Pro 500 subscribers can use Ultrafast with either model. For the first time, we’re also bringing Ultrafast to Pro 200 subscribers, starting with GPT-6.2 Sol. Developers can access gpt-6.2-astra and gpt-6.2-sol in the OpenAI API, with Ultrafast available.

Tweet image
248x.com

OpenAI launches GPT-6.2 Astra and Sol models

@PolymarketTrade
@PolymarketTrade

We've identified & fixed an issue impacting our international platform, Polymarket⁠.com. One of our 3rd party providers was compromised, and we have referred this to relevant law enforcement. Anyone who has been impacted will be made whole. Out of an abundance of caution, we have temporarily halted trading & are working to bring the platform back online.

249x.com

Polymarket.com compromised via third-party provider, trading h

@ProfWerder
@ProfWerder
Replying to @cass_on_mars

Cassie — I find it amusing that you’re upset by our neutrality when you’ve been the biggest beneficiary of it for the past 7 months. I really disliked your approach with the Neynar team. I know you had your own personal beef with them and I feel like some of your actions were motivated by that and didn’t allow for them to even get off the ground. I didn’t care for it. I felt like there was a push to take a side then to. If pushed, Neynar would’ve been our “side.” (and by the way, we were so neutral they thought we were team Cassie while still giving us the opportunity to run CEF and supporting GMFC — we didn’t find that out until the end of CEF.) But I kept all my personal feelings to myself and we continued to share all activity and news about hypersnap. Not sure that will continue (although we did mention your call yesterday). I also find it disingenuous that you never shared the full scope of your proposal with those who were riding so hard for you to take over Farcaster. It was not a real offer. To think that Rish and their investors would pay you to continue the protocol while there were actual cash offers on the table is crazy work. Also — you say Quorum will be there for us while I know there are specific discussions around banning those who voted yes. So which is it? I may not agree with every statement or action that has occurred during the switch to Network School but I’m willing to wait and see. I’m hoping that it may bring back some of the folks from early days who created the environment I fell in love with. It may not. But I’ll allow season 4 to unfold and see how it plays out.

Tweet image
250x.com

@ProfWerder: responds to Cassie on Farcaster neutrality, Neynar, and Quorum

@VitalikButerin
@VitalikButerin

My views on EIP-8037: https://docs.fileverse.io/document/dUHG8…

Tweet image
251x.com

@VitalikButerin: My views on EIP-8037

@VitalikButerin
@VitalikButerin

Over the past few weeks I've gone from thinking leanPCS is total bull to being a total bull. So let me explain some of these buzzwords in more detail. At the core, 8288 is about hyper-scaling data and execution for any computation that needs to get performed on a piece of data once, the chain learns the answer, and then we never need to see that data again. This sounds very specific, but it includes most "heavy" things happening on Ethereum: * Signatures * STARKs * Merkle branches * FHE computation * ... Really the first two are the most important. Once we go quantum-safe, signatures get bigger (65 bytes ECDSA -> 1-6 kB WOTS/SPHINCS depending on params) and ZKPs get much bigger (200-1000 bytes with groth16, PLONK, etc -> 128 kB with STARKs). This is unsustainable to put on chain, and 8288 fixes this. 8288 works by aggregating STARKs in the mempool. First, you as a user generate the STARK or SPHINCS signature or PCS opening (more on that last one later), and publish it. Then, each node listens. Each tick, each node takes all of the new objects that it has seen, and generates a STARK containing a list of "claims": "pubkey P has signed message M" "program X run on data D has output Y" "p(X) = Y for some polynomial P whose hash is H" and a proof that it has seen a signature, STARK or PCS opening verifying those claims. So the only information getting re-broadcasted is: (i) hashes of inputs and outputs (~64-96 bytes per claim) (ii) a single STARK proof per tick These aggregate proofs themselves get re-aggregated, and eventually you get to a single "master proof" in the block, that verifies that all of those statements are true. And so the only other data that has to actually go on chain is the statements (the (P, M), (X, D, Y), (X, Y, H) tuples I described above), not the actual signatures or proofs. This gets put into a specialized frame type. Now, let's get into the leanSPHINCS vs leanSTARK vs leanPCS part. The core distinction is: *what is the underlying object that the user is creating?* In leanSPHINCS, it's a signature, and specifically this particular type of purely-hash-based signature: https://ethresear.ch/t/sphincs-minus-eff… If we add leanSPHINCS, then users will be able to make quantum-safe accounts, and pay only a little bit of gas (4096 for the 64 bytes) for each signature. So we get scalable quantum-safety for regular accounts, multisigs, etc. But it's only one specific signature scheme, you can't do anything else. In leanSTARK, it's a STARK. This means it's fully general: the user runs whatever computation they want, and publish a STARK of it. So you can use it for: * Any signature scheme (including eg. lattice-based ones if you like those) * A multisig that hides its internal logic * Privacy protocols * Private account abstraction: authorization logic that depends on some value hidden elsewhere in the state, so you can have one key that controls all your accounts without publicly linking them to each other Basically, it's a free for all, in the same way the EVM is a free for all. But leanSTARK has a practical downside. The protocol would have to specify the language in which users write their programs (we call this the "ISA"). So we would have to agree on that language. This is a really big deal - it's the first big case of "Ethereum moving beyond the EVM" - and so it's likely to take time to agree on the details of it, especially since the ISA would be hard to upgrade. There are benefits to taking longer on this, figuring out the ideal ISA, and then even giving access to it inside regular contracts. LeanPCS is the third option. PCS stands for "polynomial commitment scheme": a proof that P(x) = y. The most important thing to know about PCSes is that they are by far the most important "hard" component of a STARK (see here: https://vitalik.eth.limo/general/2021/01… ). If you have a "magic PCS oracle" (which from the EVM's point of view, 8288 is), you can verify a STARK in ~20-40k gas. The most important gain with PCS is that there is far less that we need to choose. Specifying a PCS only requires specifying a field, and there is a natural option: the 128 bit binary field (technically, we can go more general than that, and say the 2^k-bit binary recursive tower field, going up to 256) LeanPCS is less efficient than leanSTARK onchain, because you would have to put multiple claims to prove one thing. But it's arguably more efficient offchain, because you have much more flexibility to choose proof systems. But most importantly, leanPCS gives you the same generality as leanSTARK, in a way that could potentially be implemented very quickly. And once we figure out the ISA, we can add leanSTARK later. So there is a route to getting "the cryptographic proof singularity" much faster than any of us expected, and that route runs through 8288 with leanPCS. https://firefly.social/post/x/2120922104…

252x.com

Explaining EIP-8288, leanSPHINCS, leanSTARK, and leanPCS.

253x.com

@XBToshi: Phantom disabled transactions after receiving dust from a scammer

254x.com

@_RichardTeng: An update on the security incident

255x.com

A brief on ZKPs (2026)

256x.com

@arsraarsra: How I explored the Terraforms NFT project in 2021 and what it was

@binance
@binance

We are aware of differing figures circulating publicly regarding the amount frozen, including references to $1.8 billion. For clarity, the current verified total frozen is $2.54 billion. This figure may continue to increase as our teams work closely with law enforcement, issuers, blockchain intelligence firms and industry partners to trace and freeze additional assets. We will only share confirmed figures and will provide further updates as more verified information becomes available.

Tweet image
257x.com

Binance confirms hot wallet incident freezes $2.54B and will cover losses

258securityx.com

29 October Binance Security Incident: Initial Findings and Response Update

259x.com

@bis__cut: Making 111,111 unique NFT images means reinventing your art style

@bitschmidty
@bitschmidty

An update to Bitcoin Core's security policy via @darosior on the Bitcoin-Dev mailing list

Tweet image
260x.com

@bitschmidty: An update to Bitcoin Core's security policy

@breadcoop
@breadcoop

Security update In early November, stolen credentials were used to push malicious code into our GitHub repos. We caught and removed it within the week, scrubbed it from git history, and moved all keys and treasury signing access to hardware wallets. Our apps are safe to use.

261securityx.com

@breadcoop: Stolen credentials used to push malicious code to GitHub repos

Ethereum’s Guarantees Shouldn’t Stop at the Protocolx.com
262x.com

Ethereum’s Guarantees Shouldn’t Stop at the Protocol

263x.com

Claude Code found 14,219 front-camera frames in Android's Face Unlock

264x.com

@cz_binance: Loss might be a bit higher than that, but will cover.

265x.com

@cz_binance: Elon, bad time to troll. Please stop. Our SPCX shares are worth ove

266privacyx.com

2 key takeaways from vitaliks talk

@eriklocalhost: you can hide bitcoin inside a song, Hush Money on magical.cashx.com
267privacyx.com

@eriklocalhost: you can hide bitcoin inside a song, Hush Money on magical.cash

@VitalikButerin opens Devcon 8x.com
268x.com

@VitalikButerin opens Devcon 8

269x.com

@evilsocket: Binance holds SOC 2 Type 2, ISO 27001, and several other certificat

270x.com

Paradigm: Solar is over 100x faster than solc, with faster EVM bytecode

271x.com

Where are the agent founders?

@im23pds
@im23pds

🚨Chrome 0-Day 紧急预警,Google 确认已被在野利用。 CVE-2026-125350:Chrome XML 组件高危 UAF 漏洞,成功利用可破坏内存并实现代码执行,Google 确认已被在野利用。 请更新至 157.0.8103.50 并重启。#Chrome #0Day #网络安全 Chrome Security Update: https://chromereleases.googleblog.com/20…

272securityx.com

@im23pds: Chrome zero-day CVE-2026-125350 in XML component actively exploited, u

273x.com

Initia L1 and rollups halted after MoveVM exploit drained about 2.7M to Ethereum

274x.com

@lever0x: Trezor from CoinGecko promo is obsolete and insecure

275x.com

@lucataco: DeepSeek roots, debloats, and cuts off a baby camera from the cloud

@modularium_art
@modularium_art

Modularium has migrated to Ethereum mainnet You can claim your NFTs at https://modularium.art/claim You can learn about the re-launched site and all the improvements in the new docs at https://docs.modularium.art

276artx.com

@modularium_art: Modularium has migrated to Ethereum mainnet

@monad: Lens (@LC) is coming to Monad as a fully onchain social graphx.com
277x.com

@monad: Lens (@LC) is coming to Monad as a fully onchain social graph

278x.com

@nalin: Google previews MPC crypto custody security system for digital assets

279x.com

@objktcom: objkt social is live, inviting everyone to join the next chapter

280x.com

An OpenSSH bug that took 46 years to ripen.

More