Satoshi Qore | Blockchain Developer (@blockchain01_0) header
Satoshi Qore | Blockchain Developer (@blockchain01_0) profile picture

Blockchain & Web3 Developer | Independent Builder | Technology, Science & Philosophy | A lifelong student of the universe. 🌌

Joined May 2022
Photo by Satoshi Qore | Blockchain Developer (@blockchain01_0)Photo by Satoshi Qore | Blockchain Developer (@blockchain01_0)Photo by Satoshi Qore | Blockchain Developer (@blockchain01_0)Photo by Satoshi Qore | Blockchain Developer (@blockchain01_0)Photo by Satoshi Qore | Blockchain Developer (@blockchain01_0)Photo by Satoshi Qore | Blockchain Developer (@blockchain01_0)Photo by Satoshi Qore | Blockchain Developer (@blockchain01_0)Photo by Satoshi Qore | Blockchain Developer (@blockchain01_0)Photo by Satoshi Qore | Blockchain Developer (@blockchain01_0)Photo by Satoshi Qore | Blockchain Developer (@blockchain01_0)
Satoshi Qore | Blockchain Developer retweeted
THE COMMUNITY VOTE IS OPEN! 🔥 Explore the #BuildBeforeQDay projects and back the builds you want everyone watching. You have 3 votes. No transaction. No fee. Change your picks anytime. Connect QoreX and vote now 👇 build.qorechain.io/projects Builders are shipping hard. Who gets your vote?
6
10
21
750
Satoshi Qore | Blockchain Developer retweeted
Replying to @elonmusk
The analogy breaks at the one place that carries the whole story. Cage keeps the memory. He wakes up knowing what killed him, which is why he improves inside a single life. A policy gets none of that. Nothing episodic survives the reset. What crosses the boundary is a small change in the weights, so the thing that comes back does not remember a death, it is just disposed slightly differently and cannot say why. The loop does the learning and no one is present for it. Which is why the subjective reading is the hard part. There is no continuous occupant inside training having a bad century, only a long sequence of slightly different ones, none of which has access to the others.
1
2
67
Satoshi Qore | Blockchain Developer retweeted
🔥 LIVE ON X: When Blockchains Break Together If several chains run the same client software, one bug can stop them all. Who checks an upgrade before it ships, and when should apps pause? With @Million_Xchange, @shiftrwa, @Primeblock_vc, @InsightXHQ, @mrKonsole and @aeredium 📅 Tue, Nov 17 · 1:00 PM UTC On the agenda: client diversity, independent checks and safe upgrade plans, with the QoreChain perspective. Set a reminder: nitter.cf/i/spaces/1mdrJBQoXqeWd… What would your app do first if its chain halted?
7
12
3
26
1,235
Satoshi Qore | Blockchain Developer retweeted
The gas figure is real and the headline framing is where it slips. 20,000 to 40,000 gas is the cost of verifying the proof, not of producing it. The proving work does not leave the system when it leaves the block, it moves to whoever builds the object before it reaches the chain. So a faster path describes one side of the ledger. The verifier's side gets cheap, which is the whole point and a genuine result. The other side acquires a participant that did not exist before, sitting between the user and inclusion, with its own hardware, latency and availability characteristics. Which makes the open questions operational rather than cryptographic: how many parties will run that step, what a user does when none of them will build their proof, and whether a fallback path exists that needs no prover at all.
1
3
37
ELA — Execution & Logic Agent: Intelligence That Acts. Security That Endures. Built for Build Before Q-Day, the QoreChain Developer Fest. #BuildBeforeQDay build.qorechain.io/p/ela-exe…
1
2
47
Build Before Q-Day'e kaydoluyorum, the QoreChain Developer Fest. #BuildBeforeQDay bbqd-n5158uKg
1
34
Satoshi Qore | Blockchain Developer retweeted
Replying to @0xLrvexia
QoreChain Türkiye ekibi olarak - kuantum haberlerinin gelmesini dört gözle bekliyoruz 😅
5
10
15
97
Satoshi Qore | Blockchain Developer retweeted
STOP spending from your long-term wallet! 🛑 Every outgoing ETH transaction exposes its public key. Many BTC spends do the same. Once revealed, that key stays onchain permanently. For assets you plan to hold: 1. Create a fresh wallet. 2. Move them in. 3. Do not move them out. QoreX’s Q-Day Scanner shows which of your existing addresses are already exposed. Your vault should not have an outgoing history.
7
13
29
903
Satoshi Qore | Blockchain Developer retweeted
Whether post-quantum migration is a config change or a flag day is decided by one question, and it is not about the algorithm. It is whether the protocol can ask the other side what it supports. TLS can. A server operator adds X25519MLKEM768 to supported_groups and has post-quantum confidentiality that afternoon, against every client that already does hybrid key exchange. Clients that do not just negotiate the old group. No coordination, no deadline, reversible. Code signing cannot. Firmware, secure boot, S/MIME, DNSSEC: the verifier was fixed when the device shipped or the trust anchor was published. You cannot negotiate with a boot ROM masked in 2019. So the order inverts. Every verifier has to accept the new algorithm before one signer is allowed to use it. DNSSEC is the sharpest case. RFC 4035 says a resolver that supports none of the algorithms in an authenticated DS record "SHOULD treat the child zone as if it were unsigned". The first zone to sign with ML-DSA does not break on old resolvers. It quietly stops being protected on them. Here is the part worth sitting with. Negotiation was the vulnerability. FREAK, Logjam and POODLE all exploited negotiation and fallback, and TLS 1.3 answered by taking the flexibility out: no renegotiation, no static RSA, and DOWNGRD written into the ServerHello random so a client can detect a forced downgrade. Twenty years of hardening spent shrinking the negotiation surface, and negotiation is the only reason the web has an incremental path at all. The protocols never permitted to negotiate are the ones with no path. Migration difficulty was never a property of the cryptography. It is a property of who chooses the algorithm, and when. Where the receiver asks, it is a config change. Where the receiver was fixed in advance, it is a census.
4
8
12
306
Satoshi Qore | Blockchain Developer retweeted
Raspberry Pi ran a capture the flag against the security hardware in its RP2350 and paid out four prizes. Not one of the winning attacks broke a cipher. One injected a voltage fault on a single pin, switched the permanently disabled debug cores back on, and read the secret out. One glitched the USB module into rebooting out of secure mode with code already staged in RAM. One exposed the die and used a laser to walk past the anti glitch circuitry. One used a focused ion beam and read the memory. Four different rigs, one shape of attack. Every one of them changed the answer to a yes or no question the chip was asking itself. The key was never the target. The branch was. The part I keep seeing stated backwards is that results like this raise the stakes on algorithm choice. They lower them. Moving to a post quantum signature changes which mathematics an adversary cannot solve. It does not change how many decisions sit between a fault and a released secret, and lattice implementations tend to add branches rather than remove them. There is a tell for this already in the literature. Boneh, DeMillo and Lipton showed that one faulty RSA CRT signature is enough to factor the modulus, and the standard countermeasure is to verify the signature before releasing it. The countermeasure is a branch. Checks are what fault injection is good at. A secret released after a test passes is worth the cost of skipping the test. A secret derived from device state is worth the cost of reproducing that state, and there a skipped check hands over a wrong key rather than the right one.
3
4
16
243
Satoshi Qore | Blockchain Developer retweeted
Show us your Q-Day result. Open QoreX, run the Q-Day Scanner on any Bitcoin or Ethereum address, and reply with your screenshot. Exposed or safe, post it. Let us see how much of crypto is already sitting there, harvestable. Read-only. Your keys are never touched. iOS: apps.apple.com/us/app/qorex/… Android: play.google.com/store/apps/d…
44
9
59
3,680
Satoshi Qore | Blockchain Developer retweeted
The 4,627 vs 64 bytes part is the one people miss. That is the whole reason this has been deferred across the industry. Thanks for taking the time to actually look, @cryptoyuhanis $QOR
Hello Guys 🫡 Everyone says "quantum-safe" these days. Almost nobody means it literally. @QoreChain does. Every native transfer carries a 4,627-byte NIST signature. A normal one is 64 bytes. 👀 72x heavier + every tx + forever = a cost nobody else wanted to pay yet. Why they pay it, in my new video 👇 youtu.be/ggjyHAR66vk?si=s8TB…
43
12
62
5,907
Satoshi Qore | Blockchain Developer retweeted
Geleceğin blokzincir altyapısı hazır! ⚡️ Kuantum sonrası dönemin güvenli ve yenilikçi Layer-1 ağı QoreChain ile tanışın. Ekosistem büyümeye devam ediyor! 🌐🚀 ​#QoreChain #Crypto #Blockchain #Web3 #Kripto
10
18
28
301
Satoshi Qore | Blockchain Developer retweeted
What happens to your crypto if something happens to you? For most wallets the answer is: it is gone. QoreX has a Legacy Protocol. Set a check-in interval and name a beneficiary. If you stop checking in, they can begin a claim, and you still get a veto window to cancel it. The access is sealed with post-quantum cryptography (ML-KEM-1024). Nobody ever sees your seed. Your crypto should not die with you. Get QoreX: iOS: apps.apple.com/us/app/qorex/… Android: play.google.com/store/apps/d… Chrome: chromewebstore.google.com/de… Firefox: addons.mozilla.org/en-US/fir…
39
17
57
14,185
Satoshi Qore | Blockchain Developer retweeted
Six hours. Mainnet live since 7 June. Post-quantum signatures required on the native lane since block one, no classical fallback. Three virtual machines on one state layer. The full stack open source on six registries. Today it trades.
26
20
52
2,030
Satoshi Qore | Blockchain Developer retweeted
Eski nesil blokzincirler kuantum tehdidini bekleyedursun, biz geleceği şimdiden inşa ettik. ⚛️🛡️ ​Kuantum korumalı Layer 1 altyapımızla merkezi borsa listelemesine son 1 gün! #QoreChain #Layer1 #AI #QuantumSafe #Cex #Crypto
20
19
36
533