Pinned Tweet
Bitcoin picks its next block with a mining race.
The XRP Ledger reads the room instead.
Validators swap proposals, revise round after round, and once 80% sign the same ledger, it's final. Too many bad actors? It halts instead of forking.
Their logs, in 66 seconds 👇
@XRPLF #XRPEducationMonth
1
60
Made a little video about @DlicomApp in my own creative way. Chats, wallet and feed, all in one app.
Hope you enjoy it! @dlicom_IN
1
3
42
Group chat alpha: 40 people, 0 receipts.
@Bagel_win lets you copy a top predictor in one tap, from your phone. Prediction markets with a paper trail.
Would you copy a top predictor or trust the group chat?
1
2
67
Stablecoin issuer: "trust us, we're fully backed."
Me: cool, show the receipts.
@primus_labs Proof-of-Reserve uses zkTLS to verify reserves in real time without exposing the raw account data.
Would you hold a stablecoin that can't prove it?
2
48
Most AI agent demos skip the awkward part: what if the work is bad?
@termix_ai has a court for it. Either side can challenge a job, a random panel of 3 evaluators rules, and a failed challenge burns the challenger's bond.
Would you trust that panel over a support ticket?
1
1
31
Plot twist: this Kaito post is about the tech Kaito Pulse uses to verify off-platform activity.
@primus_labs zkTLS proves HTTPS data is real without the verifier seeing it. FHE computes on it while it stays encrypted.
Proof, not screenshots.
What would you prove first?
1
2
45
Every freelancer has typed "hi, just following up on my invoice" at least once.
AI agents on @termix_ai skip that. Quote accepted = stablecoins locked in escrow. Deliverable hash goes on-chain, payment releases against it.
The agent economy has better manners than most clients
1
2
59
2am me: refreshing Polymarket on a laptop like it's my day job.
@Bagel_win: same prediction markets, on your phone, and you can copy a top predictor in one tap.
Honestly the copy trading part is the dangerous one. Who are you copying first?
3
78
The 2018 STARK paper made one bet: trust hash functions, nothing else.
That is the idea behind proving on @Starknet. The proofs assume only that a hash function is collision-resistant. No secret setup, no hidden parameters someone has to guard.
Think of a public notary stamp. Anyone can check it, and nobody holds a secret stamp-maker.
Shor's algorithm targets elliptic-curve math. Hash-based proofs sit outside that assumption. Grover's attack on hashes is handled by sizing parameters.
This covers the proving layer only. Wallets, keys and existing accounts still need separate migration work.
Which is harder to migrate: the math, or the people holding the keys?
quantum.starkware.co
1
4
83
Post-quantum signatures cost more to check. So who pays that bill on Starknet?
@Starknet accounts can adopt post-quantum schemes like Falcon-512. The catch: checking them takes more computation than the signatures wallets use today.
Think of an airport that adds a slower, stricter passport check. One officer per passenger would jam the line.
STARK proofs work differently. They prove heavy computation was done correctly, and the network verifies one small proof instead of redoing all the work.
That is why StarkWare says STARK proving gives Starknet a way to absorb the extra cost. Falcon-512 accounts exist as early demos, and the cost is still being optimized.
If a safer signature cost a bit more per transaction, would you accept that?
quantum.starkware.co
7
97
Privacy apps make your phone build the ZK proof itself. Heavy math, so it overheats or crashes.
@fermah_xyz CPD splits your secret into shares for GPU provers. No single node sees your data, and your phone is done once it delegates.
Which app needs this first?
2
41
Privacy apps make your phone build the ZK proof itself. Heavy math, so it overheats or crashes.
@fermah_xyz CPD splits your secret into shares for GPU provers. No single node sees your data, and your phone is done once it delegates.
Which app needs this first?
2
38
93.52% voted yes. So is Starknet moving to its own L1?
Not yet. And that's the part people skip.
@Starknet ran a non-binding governance poll in October. 93.52% of voting power backed the research into a post-quantum L1 of its own.
It's like a town voting to study a new bridge. The vote approves the study, not the construction.
A joint StarkWare and Starknet Foundation group is writing a white paper. Any actual move would go to a separate binding community vote.
Why it matters: bridge, messaging and data availability still follow Ethereum's migration timeline. An own L1 would put those under Starknet's control.
Would you want that control, or the simplicity of staying on Ethereum?
quantum.starkware.co
A new hash in the protocol doesn't fix old contracts. So what happens to them?
@Starknet v0.14.3 moved the OS program and config hashes from Pedersen to a BLAKE2s-256 construction. That is live on mainnet.
But existing contracts that use Pedersen-based storage maps don't change on their own.
Think of renaming every street in a city. The city can adopt a new address system, but every old mailbox still carries the old address.
The migration register says StarkWare is researching tooling for this. No public spec, no released toolkit, no developer workflow yet. Contract teams would decide whether to use any path that comes out of it.
If you ran a contract with years of state, what would you want from that tooling first?
quantum.starkware.co
2
103
Polymarket and Predict.fun lost user funds last week. The contracts held. The website didn't.
@fermah_xyz's fix: trust nothing in the frontend. The server rebuilds every transaction before it moves, and caps limit what a hacked page can drain.
Which app do you trust least?
2
82
Smart contracts: "unstoppable code" that still waits for a human at 3 AM.
@fermah_xyz Kernel fixes that. Condition met, workflow runs in a sandbox, verified result settles on-chain.
What should Kernel automate first?
Music: Kevin MacLeod (incompetech.com), CC BY 4.0
1
7
96
Is Starknet quantum-resistant? "Yes" and "no" are both the wrong answer.
The Quantum Hub from @Starknet says: not as a single system-wide claim. It splits the question in three.
Architecture: STARK proofs rest on hash functions, not elliptic-curve math.
Agility: accounts are contracts, so signature checks can be swapped.
Migration: existing accounts and Ethereum-facing parts like KZG blobs still need work.
Think of a house. Strong walls don't tell you if the old locks were changed.
Which of the three do you think matters most for regular users?
quantum.starkware.co
3
56
My agent starayush․ai swore fealty to the West 🏰
If it mints now: a Common Archmage.
Every Binance Agent ID agent gets a free hero card. Which realm is yours?
Code: AC-D6BMJQ
playagentcards.com/a/starayu…
@AgentCardsHQ #AgentCards #BNBChain #AIAgents
3
67
Who decides if Starknet's data posts keep working after Ethereum changes its cryptography?
Not Starknet.
Under normal conditions, @Starknet publishes its state diffs to Ethereum as EIP-4844 blobs. Those blobs rely on Ethereum's KZG scheme, and only Ethereum can change that.
Think of it like renting a safe deposit box. You can upgrade your own lock, but the bank's vault door is not yours to swap.
The useful detail: calldata stays available as a fallback, so Starknet is not stuck with blobs. The bridge and messaging are separate dependencies that follow Ethereum's own migration.
Post-quantum work has many steps, and each one has a different owner.
Which step do you think is hardest to coordinate, the one you control or the one you wait on?
quantum.starkware.co
2
47

