SAMORA (@SAMORA_OG) header
SAMORA (@SAMORA_OG) profile picture

Crypto enthusiasts| GHOSTWRITER|Community manager|MOD |Web3 marketer @Future_Lounge_1. EX @tectumsocial.🔥NFA. CFC💙

CRYPTO
Joined November 2021
Photo by SAMORA (@SAMORA_OG)Photo by SAMORA (@SAMORA_OG)Photo by SAMORA (@SAMORA_OG)Photo by SAMORA (@SAMORA_OG)Photo by SAMORA (@SAMORA_OG)Photo by SAMORA (@SAMORA_OG)Photo by SAMORA (@SAMORA_OG)Photo by SAMORA (@SAMORA_OG)Photo by SAMORA (@SAMORA_OG)Photo by SAMORA (@SAMORA_OG)
Lolade Field in Ikola Idunsi is not just an open plot of land—it is the heartbeat holding our entire community together. Taking away our primary recreational space strips thousands of youth, families, and sports enthusiasts of their only safe haven.
2
7
14
1,308
Football Field Sale: Ikola Youths Say Meeting With The LCDA Chairman, Jimoh Ejigbadero Produced Temporary Relief, But No Conclusion Yet As Parties Only Returned To Status Quo
10
30
1,635
The official Onememe token launch is coming soon. Stay tuned for official launch details.
3
4
9
456
Youths Protest Sale Of Football Field in Lagos, As Residents Accuse LCDA Chairman, Jimoh Ejigbadero Of Displacing People To Resell Lands
76
206
54
345
65,127
SAMORA retweeted
Chinese hackers posed as a former US official to steal emails from AI experts. The reported method was impersonation. The attackers did not break an encryption scheme or exploit a flaw in a cipher. They borrowed the name of a person the targets would recognise, and the targets handed over access to their email. The targets are the notable part. People who work on AI hold unpublished research, policy conversations and contacts that are worth collecting, and a message from a respected former official is exactly the kind of message such people answer. A familiar name in a sender line works as a credential, and nothing in standard email checks whether the person behind it is who they claim to be. Blockchain security has the same weak point. Signature algorithms usually hold up. Losses happen where a person or a key is trusted because of how it looks, not because of what it can prove. That is the reason QuanChain separates identity from spending authority. The parent identity is a Level 20 address, secured by composite Dilithium-5 and SPHINCS+-256f signatures, and it stays stable and shareable. Child wallets can be verified against it with Merkle derivation proofs, without exposing the parent. Under SpendAndRotate, the ephemeral child key rotates on every spend, so a public key is exposed only after the funds have moved. This does not stop someone from being deceived. It does limit what a single stolen credential is worth afterwards. The implication is that stronger cryptography does not help if identity is still decided by a display name. Systems that matter, whether an inbox full of AI research or a wallet holding value, need identity that can be checked mathematically and credentials that lose their value once they have been used. Impersonation campaigns like this one show how much is at risk when verification depends on someone being persuaded.
9
12
562
SAMORA retweeted
You cannot pave over our unity and expect our community to flourish. We call on @followlasg, @jidesanwoolu, and @lagosmysd to protect our open space and save our center! 🛑⚽ #SaveLoladeField
1
67
SAMORA retweeted
Lolade Field in Ikola Idunsi is not just an open plot of land—it is the heartbeat holding our entire community together. Taking away our primary recreational space strips thousands of youth, families, and sports enthusiasts of their only safe haven.
2
7
14
1,308
You cannot pave over our unity and expect our community to flourish. We call on @followlasg, @jidesanwoolu, and @lagosmysd to protect our open space and save our center! 🛑⚽ #SaveLoladeField
1
67
Weak passwords beat a national tax authority for seven weeks. No quantum computer required. France's ANSSI confirms the attacker used stolen staff credentials to pull data on hundreds of thousands of taxpayers, undetected the entire time. The report calls it "not sophisticated." That's the part worth sitting with: credential theft alone gets you past most institutional defences. QuanChain's TADEQS doesn't touch password hygiene, but it does assume identity compromise is inevitable and builds for it: security-level-specific key hierarchies with automatic migration to new addresses as threat conditions escalate, so a stolen credential doesn't grant standing access indefinitely. If your security model assumes the attacker never gets in, what happens on week eight?
5
9
391
Three EU financial watchdogs just put something in writing that usually only shows up in crypto-twitter threads. The European Banking Authority, ESMA, and EIOPA released their Autumn 2026 Risk and Vulnerabilities report Wednesday, flagging quantum computing as a systemic risk to the financial system, alongside AI-driven cyber risk and private credit. Their exact words: "Threats could materialize earlier than any viable commercial application." Read that twice. The regulators are not saying a working quantum computer will show up on schedule. They are saying the attack does not need one to be commercially viable, or even fully built. It needs to exist once, anywhere, for long enough to run Shor's algorithm against a key that has already been sitting exposed on-chain for years. CryptoQuant's figure, cited in the same reporting: roughly 6.9 million BTC, about billion, currently sitting in addresses where the public key is already visible. Legacy P2PK addresses. Reused addresses. All of it waiting. This is not a new number by coincidence. Glassnode put a similar figure at 6.04 million in May. Different analysts, different methodology, same order of magnitude, same conclusion: a meaningful share of Bitcoin's supply has already done the one thing that makes harvest now, decrypt later possible. The exposure already happened. The only open question was always when reading the archive becomes affordable. QuanChain does not have this problem because it never creates the archive in the first place. Value sits behind an address hash, not a public key. SpendAndRotate means the only key ever revealed belongs to a wallet that is already empty by the time anyone sees it. Regulators do not usually move early. When three of them agree the timeline might come in ahead of schedule, that is not FUD. That is the read from people whose job is to be boring and right.
1
6
8
477
There is a deeper reason QuanChain avoids Proof of History: SHA-256 has 128-bit post-quantum security under Grover's algorithm. A PoH chain built on SHA-256 would need to be replaced entirely under quantum threat, adding migration complexity to an already difficult problem. QuanChain avoids embedding a potentially quantum-vulnerable primitive into its consensus mechanism. PoH can be added as a future optimisation without architectural changes if the benefit-cost analysis shifts. For now, the decision is to exclude it
1
5
10
340
QuanChain deliberately excludes Proof of History despite its use in Solana. This is not an oversight. It is a considered architectural decision. PoH provides approximately a 2x improvement over optimised BFT. Meaningful, but not transformative. QuanChain's combination of Turbine, DAG mempool, and fast path achieves comparable or superior performance without the associated costs.
7
11
1,040
God abeg, make e click for me this week.
God abeg, make e click for me this week.
149
Confidence so high, I know I'll be posting "GOD DID" before this year ends.
Confidence so high, I know I'll be posting "GOD DID" before this year ends.
69
Commercial quantum computing just got a zip code. EPB's new IonQ Forte Enterprise in Chattanooga opens for business in October, 35 algorithmic qubits, available to anyone with an account, not just national labs. That's the part most chains still aren't pricing in: quantum capability is becoming a rental, not a research project. QuanChain's LQCp/h Oracle tracks exactly this kind of shift, monitoring global quantum capability across 7 threat levels (QTL-0 to QTL-6) and triggering security escalation automatically when conditions change. If quantum power is now something you can rent by the hour, should "quantum-resistant" claims come with an expiry date attached?
1
5
10
646
Inspired by Solana's Turbine protocol, QuanChain implements erasure-coded block shredding that achieves O(log n) propagation time. With 1,000 validators: roughly 4 hops via Turbine versus roughly 10 via naive gossip. A 60% reduction. With 10,000 validators: roughly 7 hops versus roughly 14. 50% fewer hops The block producer's bandwidth requirement is O(1): it sends each shred exactly once regardless of network size. Every other validator forwards shreds only to its children in the propagation tree.
7
8
530
"An Attacker Who Breaks The Old Key Finds An Empty Address." Every wallet spend on QuanChain triggers one atomic operation called SpendAndRotate. In a single indivisible step, it spends from the current child wallet, derives a fresh child from the parent's entropy, and redirects the old address to the new one. All four steps happen together, or none do. There is no in-between moment where funds sit exposed. Here's the part that matters: the old child's public key does get revealed, right there in the spending signature. That's unavoidable, every signature scheme works that way. But by the time it's revealed, the funds it protected have already moved to the next child. The exposure & the emptying happen in the same breath. An adversary who successfully breaks that exposed key, using Shor's algorithm or anything else, gains access to an address holding nothing. This is why "no live public key is ever exposed while value is at rest" isn't a slogan. It's what SpendAndRotate mechanically guarantees, every single time, with less than 2ms of overhead. The sender never notices. It just happens. And a permanent parent identity, protected by a composite signature requiring both Dilithium-5 & SPHINCS+-256f together, gives you one stable address to share, while the ephemeral children do the actual spending underneath it. Most chains ask you to trust that their key rotation policy is good practice. QuanChain doesn't have a policy. It has a guarantee, enforced by the protocol on every transaction, whether anyone remembers to follow best practice or not.
1
6
11
466
IonQ just published the first complete blueprint for breaking Bitcoin's cryptography. Not a demonstration. A full-stack fault-tolerant resource estimate: 19,397 physical qubits running Shor's algorithm against secp256k1, 25.7 days per key. The number that matters is 19,397. Because the standard reassurance has been that this takes millions of qubits. One widely cited analysis put it at 13 million. Comfortably impossible, decades out. IonQ's blueprint needs roughly 670x fewer than that. And IonQ's own roadmap puts a 20,000-qubit machine in 2028. Their CEO is on record targeting 10,000 fault-tolerant qubits in 2027. The caveats are real and worth stating plainly. This is an estimate, not an attack. IonQ runs 256 qubits today. Scaling that fast may hit obstacles nobody has seen yet. But the curve only bends one way. Every serious estimate of what it costs to break ECDSA has come down, never up. Bitcoin's answer is BIP-360, still without consensus. Ethereum is targeting December 2029. Both are retrofits on ledgers where public keys are already exposed and cannot be un-exposed. QuanChain has no number to watch. Value at rest sits behind an address hash, not a public key. There is no live key for Shor's algorithm to target. SpendAndRotate rotates the ephemeral child key on every spend, so by the time a public key appears in a signature, the funds have already moved. The LQCp/h Oracle tracks this exact cost curve and migrates wallets upward automatically as it falls. No hard fork. No coordination. No window to miss. Everyone else is watching the number. We built for the day it stops mattering.
4
5
1
12
1,616