
Capital Markets & Securities Analyst || Founder @WSTradersinc || Crypto Enthusiast || #BTC $CKB Maxi || @GoMining Ambassador || Let's Mine ⛏️ Bitcoin Here ⏬️
Not Financial Advice
Joined June 2011
- Tweets3.2K
- Following1.6K
- Followers674
- Likes20K
fuckfiat.bit retweeted
Who built CKB in the last 30 days?
5,333 public updates on GitHub, by 151 people, in 195 projects.
Most active: Fiber, Pocket Node, ckb-keyway, CCC and the CKBuilder projects. Kudos. Keep it up 🆙↗️☝️
Every project and every person, live:
pulse-lab.lusocryptolabs.com
fuckfiat.bit retweeted
“There could be extraordinary strategic benefits to deliberately creating an inefficient state mechanism which takes an excess quantity of physical resources (e.g. electricity) to operate, as those thermodynamic restrictions would double as a way to physically constrain sensitive software control actions rather than logically constraining them.”
— Jason P. Lowery
“Energy is the true currency. This is why I said Bitcoin is based on energy. You can’t legislate energy. You can’t just pass a law and suddenly have a lot of energy.”
— Elon Musk
#CKB Wedge Retest🔍
Nervos Network is retesting the broken falling wedge formation on the weekly chart👀
✅ Retest holding with strength
✅ Strong volume validating the move
✅ Bullish structure fully intact
Targets: $0.0014 → $0.0030 → $0.0075 → $0.0190 → $0.0380🎯
fuckfiat.bit retweeted
Vitalik just ranked the math. Hash-based beats lattice-based.
Here's what 13 quantum resistant tokens actually run on 👇
Hash-based, live
→ $QRL : XMSS since 2018
→ $XNT : STARK hash lock since genesis
→ $CKB : SPHINCS+, opt-in
Lattice-based, live
→ $ABEL : lattice ring signatures, mandatory
→ $CELL : Dilithium by default
→ $QTC : ML-DSA only, mainnet Sep 2026
→ $ALGO : Falcon-1024, opt-in
→ $NEAR : ML-DSA-65, opt-in
Not live yet
→ $STRK : ECDSA accounts, Falcon planned
→ $NAORIS : Dilithium L1, ERC-20 token
→ $QANX : Dilithium testnet, ERC-20 token
→ $ZEC : scheme unpicked, 2027 target
→ $QUBIC : SchnorrQ, no PQ plan
Only 3 of the 13 are live on the math he trusts.
I don't recommend anyone scramble to move their funds to new wallets today. But we should take the risks to cryptography from AI-accelerated math seriously, and minimize our exposure to not just quantum-vulnerable cryptography, but also potentially AI-vulnerable cryptography.
The core new area of risk from this viewpoint is, unfortunately, ML-DSA / FHE / lattices.
(and it's also another reason, along with quantum, why ECDSA might fall even faster than expected, hence the "fresh address" recommendation)
So far most people have been in the mode of thinking "elliptic curves broken, hashes safe, lattices safe". But there is a good chance that the concrete security of lattices will take serious hits from the next two years of AI math.
The basic threat model is: factoring is something that naively takes 2^(n/2) time, but over decades smart people have found and optimized number field sieves, and degraded that to 2^O(n^(1/3)), which is why RSA keys and signatures need to be ~400 bytes (and not 64 bytes). What if there are skeletons in the closet like that, both for elliptic curves and lattices, that we are simply not smart enough to discover - but bots soon will be?
This is a major part of the reason why for the past year ethereum's lean roadmap has been going in the "hash-only" direction: no lattices, no ML-DSA, no Falcon, no lattice-based commitments inside ZK proofs, etc. Signatures in lean ethereum are all hash-based, either WOTS or SPHINCS-.
For signatures and proofs, we already know how to go hash-only. The bigger challenge is for *public-key encryption* - and this goes far beyond blockchains. Secure communication, anonymizing protocols, lots of things need public-key encryption.
And unfortunately there are long-standing mathematical theorems showing why public-key encryption cannot be done with hashes alone. You have to have some kind of trapdoor object that has at least one form of usable "structure" - either group theory (incl. isogenies) or lattices or code-based or potentially in the future even more newfangled and spooky things (local mixing?). But for anything that has structure, you should assume that AI will make at least some progress in breaking that structure. Here, one reasonable inference is that if you want to make something plausibly long-term secure, multiply the key sizes by 10.
To me that's a very plausible world and something not at all extreme to predict. If AI will bring us 50 years of math in 2 years, then that 50 years of math may very plausibly include a "naive factoring -> GNFS" level of improvement to our ability to break lattices. In that world, lattices will still exist, but they will have to be significantly bigger to guarantee the same level of safety.
And at those new larger sizes, hash-based constructions will beat lattice-based constructions on concrete efficiency in every use case where hash-based constructions are possible at all.
Theoretically, of course it's possible that hashes are broken too (eg. P = NP would imply that). But I think P = NP is very unlikely. And intuitively, it's much more likely that a mathematical object has exactly no exploitable structure (like hashes are intended to), than that a mathematical object has exactly ~3 forms of exploitable structure (for elliptic curves: associativity, Schoof, pairings) and not some secret fourth form of structure we have not yet discovered that greatly degrades its security (for elliptic curves, ECDLP and pairing security). Similar for LWE, SVP, RLWE and the zoo of lattice problems.
For this reason, we do not yet see any reason to worry and start padding the byte size of hashes (if we start to worry more, we would pad the round count first before doing anything to the byte size).
Concrete TLDR, my own personal views:
* Hash-based > lattice-based, in those situations where hash-based is possible at all
* For anything lattice-based, be much more paranoid on param sizes. Remember that blockchains are only a small portion of the cryptography story; this point goes far beyond blockchains and applies to eg. access to websites, secure messaging, Tor / VPNs ...
* For privacy protocols, strongly favor NOT putting encrypted notes onchain. Instead, send them offchain through some third-party mechanism.
* If it's not difficult for you, keeping your funds in addresses which have not yet been used to make a transaction is a good idea. If it's easy for you, do it. **But be careful about migrations; I personally have lost more money in botched migrations than I have lost in all hacks combined**.
* For multisig wallets, doing confirmations offchain is better than onchain, because this way the signatures of signer wallets do not get exposed to the public, so if ECDSA falls to AI much faster than expected, at least the multisig "gracefully degrades" to a 1-of-1 where the 1 is whoever was gathering the signatures - a much better place to be than "anyone can take the money"
firefly.social/post/x/210783…
fuckfiat.bit retweeted
Sex won’t satisfy you.
Fame won’t satisfy you.
Drugs won’t satisfy you.
Money won’t satisfy you.
Alcohol won’t satisfy you.
Success won’t satisfy you.
Life is empty without God. He is the only one who can satisfy your heart.
fuckfiat.bit retweeted
Quit porn = energy back. Make money = confidence back. Pray = discipline back. Train = your body back. Do all four and watch your life change.
fuckfiat.bit retweeted
fuckfiat.bit retweeted
FACT: From jail, Tundu Lissu defended himself in a case in which the State sought to have him convicted & hanged to death. He has prevailed through meticulous self-representation.
fuckfiat.bit retweeted
'Minor offense' is SEDITION.
How do you drift from TREASON to SEDITION?
Acquit my leader now, bana!
fuckfiat.bit retweeted
The developers finding their way to CKB in Q3 are not all starting from scratch.
Three teams with production experience elsewhere spent the quarter exploring whether to build here: Lucent Labs, from the Cardano and Midnight ecosystems, working on an open-source order-book DEX; Kaze, active across Bitcoin and Lightning, integrating CKB and Fiber into its geolocation rewards app; and TexLabs, also from Cardano and Midnight, exploring AI and payment channels on CKB.
None of them came through a grant program.
Full Q3 report 👉 talk.nervos.org/t/nervos-com…
fuckfiat.bit retweeted
As an American constitutional lawyer, I have personally litigated cases defending the rights to free expression and due process. These are fundamental principles of human liberty. For that reason, I am closely following the outcome of Tundu Lissu’s trial proceedings, and the broader implications for the rule of law.
fuckfiat.bit retweeted
Elon Musk, 800 milyar dolarlık servete rağmen neden hala çalışmaya devam ettiğini açıklıyor
Elon Musk:
Gençken hayatın anlamını çözmeye çalışırken varoluşsal bir kriz yaşadım. Hayatın bir anlamı yokmuş gibi geliyordu.
Okuduğum dini metinler beni ikna etmedi. Sonra filozofları okumaya başladım.
Özellikle genç yaşta Alman filozofları okumakta dikkatli olmalısınız. Depresyona pek iyi gelmiyor.
Schopenhauer ve Nietzsche okuyunca çocuk yaşta insanın kafası iyice karışıyor.
Sonra Otostopçunun Galaksi Rehberi’ni okudum. Douglas Adams’ın anlatmak istediği şuydu:
Asıl sorun cevapları bilmemek değil, doğru soruları bile soramıyor olmamız.
Doğru soruları sorabilmek için Dünya’dan çok daha büyük bir bilgisayara ihtiyaç var.
Evren aslında cevabın kendisi.
Ama soru ne?
Bilinç ne kadar büyür ve yayılırsa, evren hakkında doğru soruları sorma şansımız da o kadar artar.
İnsanlığın çok gezegenli, hatta çok yıldızlı bir medeniyet olması gerekiyor. Belki ancak o zaman burada gerçekten ne olduğunu anlayabiliriz.
Bu yüzden daha fazla insan ve daha fazla dijital bilinç olması gerektiğini düşünüyorum. Hem biyolojik hem dijital bilinç.
Elon Musk, burada aslında ne anlatmak istedi?
Açıklıyorum:
Ersan Diamond:
Paranın bir maliyeti var.
Biz malı aldık, 20 gün tezgahta durdu.
20 gün sonra sattım, benim kazancım 5 bin dolar.
500 dolar kârla başka malı aynı gün satarım, ertesi gün ana parayı tekrar mala bağlar, 20 günde 15 bin dolar kazanırım.
20 gün sonra pahalı malı 5 bin dolar kârla versen ne olur, vermesen ne olur..
fuckfiat.bit retweeted
Leading cryptographers met in Cambridge last month for Ethereum's second annual post-quantum research workshop.
The recap is worth four minutes, and it doesn't soften the stakes: quantum computers were expected to break cryptography by 2035.
"The new estimate is 2029."
AI is a big part of why. @GiacomoFenzi of EPFL: "It is almost certain that AI accelerates timelines. It is uncertain by how much it will accelerate it."
Despite that uncertainty, the tone is upbeat. Ethereum's researchers have settled on hash-based signatures, and as one puts it near the end: "we just need to put it in place and done."
So what does "done" look like?
On Bitcoin, it means agreeing a soft fork. Taproot, its last major upgrade, took nearly four years from proposal to activation, and it had broad support. Then every holder has to move their coins, on a network with room for only a few thousand transactions every ten minutes.
On Ethereum, standard accounts are tied to one signature scheme checked by the protocol, so it means a hard fork. Then every holder has to move their coins.
A proposal called Frame Transactions (EIP-8141) would let accounts set their own verification, so later changes or additions of signature schemes wouldn't need another fork.
And if Bitcoin's new scheme ever needs replacing, it goes through it all again.
On CKB, signature schemes were never written into the rules every node enforces. Each one is a small program called a lock script, so adding a new scheme is just a software release. Anyone can do it at any time, no forks needed.
SPHINCS+, a hash-based scheme, is already live on the network, with an audited lock. "Done" means moving your coins under it in an ordinary transaction.
Whichever schemes stand the test of time, CKB can carry them without a protocol upgrade.
fuckfiat.bit retweeted
🚨 TUZAĞA DÜŞME
Bitcoin’in döngüsü şimdi son aşamasında.
3 gün önce, 80 bin dolara düşüşü öngörmüştüm.
Son sarsıntı yaklaşıyor.
$BTC, çift dip oluşmadan önce bir kez daha düşecek.
Kurulum basit:
$82K → $67K → $109K → $130K → $190K → $230K
Bunu şimdi kaydet. Nedenini daha sonra göreceksin.
Bildirimleri aç. Geç kalmadan takip et.
Her büyük güncellemeyi burada ilk olarak paylaşacağım.
🚨HERKES MUTLAKA OKUSUN..
ℹ️ Son üç ay içerisinde bizler neler mi yaptık ?
#ANSEM 1000X 🚀✅
.
#HOT %60 🚀✅
.
#PEPE 450X 🚀✅
.
#TRUMP 850X 🚀✅
.
#HMSTR %50 🚀✅
.
#XPIN %60 🚀✅
.
#PYR %35 🚀✅
.
#MMT %30 🚀✅
.
#BEAT %45 🚀✅
.
#ATM %20 🚀✅
.
#ZANO %40 🚀✅
.
#AAVE %23 🚀✅
.
#BNB %150🚀✅
VE DAHA YAZMADIĞIM ONLARCASI.😎
Kripto ve Borsa alanında bizlerden daha iyisi yok dostlarım.
❗️Gerçekten para kazanmak istiyorsanız , bu tarz fırsatlardan faydalanmak istiyorsanız ücretsiz kanalımıza katılabilirsiniz.
NOT: profilimdeki bağlantı üzerinden kolayca katılabilirsiniz. 👇
t.me/+Le30IOP0XmJmZjI0
fuckfiat.bit retweeted
CKB has been crypto-agile by design since its mainnet launch in 2019. On many blockchains, a new signature scheme needs a protocol upgrade, and getting a whole network to agree is slow and contentious. On CKB, signature checks run as lock scripts rather than as part of the protocol, so a post-quantum scheme can be deployed as a new lock with no network-wide vote. One is already live on mainnet and three are on testnet.
Each scheme below is measured against secp256k1, the signature scheme used today by Bitcoin and Ethereum, as well as by CKB's “default” lock. On CKB it takes up 65 bytes and about 3.5 million computing cycles to check.
1. SPHINCS+ (live on CKB mainnet, audited)
Instead of relying on the arcane mathematical problems behind today's signatures, SPHINCS+ uses layers of cryptographic hashes to show that a transaction was authorized by the rightful owner. Its security depends on the hash function and nothing else. Jan Xie, our Chief Architect, calls it the most conservative option. It is also stateless: the wallet does not have to keep count of how many times it has signed, so a seed phrase restores everything.
⦿ Size: about 120 to 770 times larger than a secp256k1 signature
⦿ Checking: about 3 to 14 times longer
⦿ Space: about 12 to 70 transactions per block, against about 1,000 with secp256k1
⦿ Standard and audit: NIST's SLH-DSA (FIPS 205); ScaleBit audited the lock in 2025
In plain terms: the most conservative choice on the list. It is standardized, audited and built on hash functions alone, at the price of taking up the most space on the chain.
2. SHRINCS (testnet, unaudited)
SHRINCS also relies only on hash functions. It is a design from @Blockstream, and the CKB lock on testnet was written by Jiandong Xu. It is built to be small. In normal use the signatures are very short, but the wallet has to keep count of them, because signing twice with the same count would expose the key. If the count is lost, or the wallet would rather not rely on it, it can use a larger signature that works from the seed phrase alone.
⦿ Size: about 5 times larger (324 bytes at the start, growing slightly with each signature), or about 40 times larger on the fallback
⦿ Checking: about 3 times longer at the start, or about 5.5 times on the fallback
⦿ Space: about 370 transactions per block with a fresh counter, against about 1,000 with secp256k1
⦿ Maturity: a young design, with no independent audit or security proof so far
In plain terms: SHRINCS signatures have the smallest footprint of the four at first, but the wallet has to keep careful count, and the design is young and unproven.
3. ML-DSA (testnet, unaudited)
ML-DSA is NIST's main general-purpose standard (FIPS 204). It rests on a different kind of mathematical problem, called a lattice problem, which is newer than hash functions. Like SPHINCS+, it needs no counter. The CKB locks were written by community developer toastmanAu.
⦿ Size: about 57 to 81 times larger at its two smaller settings
⦿ Checking: about 1 to 2 times longer
⦿ Space: about 100 to 140 transactions per block, against about 1,000 with secp256k1
⦿ Standard: final (NIST, 2024)
In plain terms: the standard all-rounder. It is reasonably quick to check, but bigger than today's signatures and built on a newer mathematical assumption than the hash-based options.
4. Falcon (testnet, unaudited)
Falcon is also lattice-based, and NIST is standardizing it. It produces the smallest signatures of the lattice schemes. Its weak spot is signing, which is complex to implement. Checking a signature, the part the chain does, is simple. The CKB locks are also by toastmanAu.
⦿ Size: about 24 times larger for Falcon-512
⦿ Checking: about a third of secp256k1's cost, the cheapest of the four
⦿ Space: about 280 transactions per block, against about 1,000 with secp256k1
⦿ Standard: still a draft (NIST's FN-DSA, FIPS 206)
In plain terms: the quickest to check, and small for a lattice scheme, but harder to implement on the signing side.
So is there a best one?
No. Each wins on one measure and pays for it on another:
⦿ SHRINCS: the smallest signatures at first, provided the wallet keeps its count
⦿ Falcon: the cheapest to check, though signing is hard to implement
⦿ ML-DSA: the most established standard and the simplest to build, but bigger than today's signatures
⦿ SPHINCS+: the most conservative foundation, paid for in space
Which matters most depends on what a chain is protecting and what it can afford: block space, checking cost, how much it trusts newer mathematics, and how much it can ask wallets to look after. On October 7, @VitalikButerin said hash-based signatures beat lattice-based ones wherever hash-based is possible at all. Ethereum's roadmap already excludes ML-DSA and Falcon. SPHINCS+ and SHRINCS are hash-based; ML-DSA and Falcon are lattice-based. No break of any of the four has been shown.
CKB does not have to choose. Each scheme is a lock script, so anyone can deploy one without a network-wide vote, and each user decides which to trust. If research or a standard points somewhere new, a new lock can join them the same way.




























