unfair.so/x/@sarwarbuild
Sarwar🍌
Sarwar🍌15.2K
Sarwar🍌
This creator added themselves. Not verified by unfair.so.

Crypto builder & content creator · Videos on X · Building in public https://t.co/K6g8iHdyZn

@sarwarbuildCryptoAI AgentsDeFi
15.2KFollowers
631Median impr. / post
4.5%Engagement
16+11
Paid partnerships
In their audience
4+ affiliated with @axisrobotics follow Sarwar🍌
@0xUpkibaVn@Quaocchoo@ngoquangthanh97@Ashik_803+ affiliated with @coinmarketcap3+ affiliated with @actionmodelai3+ affiliated with @binance2+ affiliated with @okx2+ affiliated with @kaitoai
1,500+ verified followers analyzed
@0xUpkibaVn@Quaocchoo@ngoquangthanh97@Ashik_80+1496153+ media creators90+ crypto creators62+ creators60+ AI creators32+ crypto investors26+ crypto marketers
25–34 core age group
35.8%
25% of audience in United States
🇺🇸
Last 7 days195 posts analyzed · replies not counted · updates weekly
ImpressionsEngagements
9.9K4.9K0
7203600
Nov 14Nov 15Nov 16Nov 17Nov 18Nov 19Nov 20
Past collabs
Sarwar🍌@sarwarbuild · Nov 8An agent that cannot prove what it did cannot be trusted with money. Agents are about to do the work humans used to do onchain: execute trades, call APIs, manage funds, settle jobs. The pitch is always the same, that the agent is smart, fast, and always on. The problem is not the pitch. It is the receipt. Right now, an agent can say it followed the strategy, it used real data, and the funds are compliant. You have its word for it. Its decision path, its API keys, its account details, all of that is either exposed to everyone or hidden from everyone. There is no middle setting where the work is checkable and the secrets stay secret. That middle setting is what @primus_labs is building for. With zkTLS, an agent can prove the data it ingested came from a real API response and was not tampered with, before it submits an execution state on chain. With FHE, the balances and positions it works with can stay encrypted while the contract still adds, compares, and checks them. The result is a narrow, checkable claim: I executed according to the strategy, and the funds are compliant, without broadcasting the full decision path and account details to the whole network. AlphaNet already shows the shape of this in human form: Proof of PnL, Proof of Trade, Proof of AI Affinity. Prove the outcome crossed a threshold, without publishing the whole history behind it. An agent that cannot prove what it did cannot be trusted with money.PrimuslabsPaid partnership680 views
Sarwar🍌@sarwarbuild · Nov 8People will stop saying “Starknet is quantum ready” after they see these numbers. People will also stop saying it isn’t. 8/8 on the agility checklist. 41 addresses behind 94% of the vote. 0 whitepapers. 3 weeks, 10 posts, 7 numbers. Every one dated and sourced, so you can check me. 8/8 @Starknet score on the StarkWare Quantum Hub agility checklist (v4.0 rules, networks page updated Sep 28, 2026, methodology checked Oct 15). Not a security rating, not a migration timeline. The hub is made by StarkWare, so its evidence cells are public. A number you can’t audit is a slogan. The 8 fall into three groups. Ability to change: account change, flexible formats, modular updates. Changing safely: gradual rollout, tested transition. Never sliding back: downgrade lock, sunset mechanism, existing data. Three of eight is a demo. Eight of eight is a migration. 64 vs ~666 A Stark curve signature is 64 bytes. Falcon-512 is about 666, roughly 10x. Bigger transactions, more data to publish, store and verify, on a chain where data availability is already the costly part. A Falcon-512 account has run on mainnet: the mechanism works. It’s unaudited, non-standard, and no account migrates automatically: the migration isn’t done. Both facts belong in one sentence. 4 stages Find every dependency. Introduce and test the new scheme. Move users and data side by side. Retire the old paths. Skip the middle and you get a flag day with better branding. 1 hash migration shipped v0.14.3 swapped Pedersen for a Blake2s-256 construction in OS program and config hashes. Done, in production. Not a signature swap, but proof the chain has changed its cryptography without breaking. Trie and address changes are roadmap. Tooling for Pedersen storage maps is research. 93.52% Voting power backing research into an independent post-quantum L1 (snapshot, Oct 15 to 22, 2026). About 3,236 votes, roughly 489M STRK, the highest turnout in Starknet governance history. StarkWare abstained. Non-binding. The number behind it: third-party analysis of votes through Oct 19 shows about 94% of 375.7M voting power came from foundation-delegated STRK across 41 addresses. The mandate is real and so is the concentration. Hold both. 2027 vs 2029 StarkWare targets full quantum resistance by 2027, a goal and not a confirmed date. Ethereum’s stated target is December 2029. That gap is why the L1 question exists. Blobs lean on Ethereum’s KZG, and bridging leans on secp256k1 and secp256r1 syscalls. STARK proofs verify with hashes, so proving isn’t on the replacement list. The dependencies are. 0 whitepapers The draft L1 whitepaper is due this month. Not out yet. It has to answer what the vote couldn’t: consensus, data availability, censorship resistance, and what security staked STRK provides. Until then Starknet stays an L2 and any move needs a separate binding vote. The system was built to swap its lock without rebuilding the house, and it hasn’t finished the swap. Only one half makes a good slogan.StarknetPaid partnership567 views
Planning a launch?Sarwar🍌 is one of 200 curated B2B creators. Tell us what you are launching and we will put the shortlist together.
Built with unfair.so
1 picked$100
Sarwar🍌 (@sarwarbuild) — sponsored posts & rates · unfair.so