port (@port_dev) header
port (@port_dev) profile picture

devrel @monad | friend @buidlguidl |👀 https://www.teapawt.org/t.co/YBOsJWXZZx | https://www.teapawt.org/t.co/WzL1pXxeiY

Joined October 2020
Photo by port (@port_dev)Photo by port (@port_dev)Photo by port (@port_dev)Photo by port (@port_dev)Photo by port (@port_dev)Photo by port (@port_dev)Photo by port (@port_dev)Photo by port (@port_dev)Photo by port (@port_dev)Photo by port (@port_dev)
Pinned Tweet
Blockchains of today rely on digital signatures to agree on which txs are valid. The problem with that is that quantum computers could break those signatures. There are several possible solutions to this problem. Quantum Cadence takes a different approach here: design consensus so its safety does NOT depend on the signatures. Incredibly cool research from Category Labs (again)
Today we are releasing Quantum Cadence, a post-quantum version of Cadence, our consensus protocol with multiple concurrent proposers. Quantum Cadence uses no quorum certificates, and its safety and liveness do not depend on signatures. Most modern consensus protocols, Cadence included, rely heavily on signatures and quorum certificates, which a large-scale quantum computer could forge. Simply replacing today's signatures with post-quantum ones would make certificates too large for every validator to send around in a high-performance blockchain. Quantum Cadence instead draws on Forget-IT, a recent signature-free consensus protocol co-developed by researchers at Category Labs. Quantum Cadence still keeps the overall architecture and core guarantees of Cadence, so our Cadence prototype was easy to carry over: an AI was able to adapt it to Quantum Cadence in a few hours, and an early prototype now runs on an internal test network. We designed Quantum Cadence to be practical for a high-performance blockchain. In our simulations, its latency is similar to Cadence's, and it scales better with the number of proposers. Interactive explainer: category.xyz/quantum-cadence. Full paper: arxiv.org/abs/2610.32803. Joint work by @MohammadMJalal1, @TobiasKlenze, and @komasito55
2
34
1,536
woohoooo Friday livestream schedule is here
Day 3 of the Metropolis Winners Showcase is here. Join us on Friday, November 20 at 15:00 UTC for five more conversations with Metropolis winners and standout projects. → 15:00 | Likeness with @rohitonchain → 15:15 | PerplScope with @BinayakSin99210 → 15:30 | Pact with @codeX_james → 15:45 | Aria Ads with @Msrobinl and @0xflo_ → 16:00 | Terrace Social with @ElioCodes We’ll talk about what they built, how it works, what they learned, and what helped their projects stand out.
2
162
We are live! Join in to learn how to win a HUGE hackathon
9
346
34 minutes to go😤
Want to know what it takes to build a winning hackathon project? 🏆 Join us for Day 1 of a special Devrel Livestreams series featuring projects from the Metropolis hackathon! Wednesday, November 18 at 15:00 UTC: → 15:00 | rizz town with @abhitejxyz → 15:15 | Makeo with @PratyakshInani → 15:30 | PIRY with @cassxbt → 15:45 | Assay with @dracian_me Join us live on X!
1
3
259
Reminder: you're only as good as the security of the 3rd parties you rely on.
Reminder: you're only as good as the security of the 3rd parties you rely on. 1) Pick wisely 2) Prune widely
5
404
I will be live with more winners on Thursday, 3PM UTC from @monad_dev
Day 2 of having Metropolis winners live: get the tips to win a hackathon! Join us on Thursday, November 19 at 15:00 UTC for four more conversations with Metropolis winners. → 15:00 | Money Moves with @soke_decentra & @avaworld16 → 15:15 | Eros Markets with @0xDarkryX_ → 15:30 | Chart Arena with @papabun → 15:45 | XooX with @eviltahaa We'll explore what they built, the challenges they faced, and what they learned along the way on an X livestream
12
434
2 days to go!
Want to know what it takes to build a winning hackathon project? 🏆 Join us for Day 1 of a special Devrel Livestreams series featuring projects from the Metropolis hackathon! Wednesday, November 18 at 15:00 UTC: → 15:00 | rizz town with @abhitejxyz → 15:15 | Makeo with @PratyakshInani → 15:30 | PIRY with @cassxbt → 15:45 | Assay with @dracian_me Join us live on X!
9
396
Up for a discussion? Join in: forum.monad.xyz/t/mip-21-lar…
Category Labs has proposed MIP-21, which raises max contract size to 256 kb (currently 128 kb) This is more complicated than simply changing a parameter, for two reasons: 1. Per-tx gas limit on Monad is 30M gas. 200 gas/byte * 256 kb would be 52M gas. In order to support this without raising the per-tx gas limit, MIP-21 introduces a way for the deployer to pay some of the MON in gas and some as a deposit 2. Cold code access currently has a flat price, whether the contract is tiny or 128 kb. MIP-20 (proposed simultaneously) makes the loading charge depend on code size. This fixes a mispricing which would get more severe with 256 kb contracts. If several contracts use the same bytecode, the code load cost only gets charged once Hopefully this improves life for developers, while introducing an approach that threads the needle between DevEx and DoS-resistance
2
2
24
819
This post made me try T3 Code great breakdown tbh
I spent months of my life and thousands of dollars looking for the best AI coding setup. I've finally found it - T3 Code. So, I made a video showing my full $1,000/mo setup:
1
18
1,360
New in the Monad docs: Fuzz your contracts with Ultrafuzz. Ultrafuzz is an open-source AI fuzzing tool that turns a swarm of agents loose on your Solidity contracts and returns a triaged bug report. Our new guide covers the setup process (throwaway VM, capped API key), the campaign itself, and how to read the findings. docs.monad.xyz/guides/ultraf…
11
8
59
3,164
This is so cool (sound on) I was watching the vid on the tl and saw Monad there i was like who is this and it was Hayder, very based
A React wheel picker on steroids. Meet Detent. Spring physics, morphing text, rolling numbers, and a slightly obsessive attention to detail. Open source. Zero dependencies. Here’s what you can build with it ↓
2
1
11
803
port retweeted
Unless you’re running a full node yourself, your blockchain queries are being read by a third party (RPC provider). Like a website visit, an RPC query can leak private information, e.g. IP X has some interest in the balance of wallet Y or transaction Z. Privacy / retention policies vary in flavor of “trust me bro.” James and @AnanyaAppan, two summer research interns, worked with @KushalBabel and @sourav1547 to build on top of Oblivious RAM and TEEs to produce an architecture that preserves privacy of reads (writes from voted blocks can be public). They then implemented and benchmarked that design! Super impressive work for a short internship.
4
4
1
44
2,576
I just got scammed for a fair amount of money. I always thought this would not happen to me. I was at a "vulnerable moment" and just acted without thinking. For everyone out here, whenever someone asks you to do something, stop, take a few moments to think about it. Do not act with haste.
91
3
4
249
9,978
Key takeaways from the livestream for ANYONE that will attend ANY hackathon: - Keep an ideas list - Read research papers (doesn't have to be 100% blockchain related) - Write good readme files - Attend the next Monad Blitz If you want Monad Blitz to come to your city, dm me!
1
2
1
13
788
We will be live in 2 hours from this account! Also, the winners of Monad Blitz Ankara, @EyupEfeKrkc and @iremsbaran will be joining us as well!
Devrel Livestreams #15: Blitz Ankara Edition On Wednesday, November 4 at 3:00 PM UTC, we’re going live with two Monad Blitz Ankara winners: 🥈 @mericcintosun demos Mavera: a paid API that shares revenue with holders on every x402 call 🥉 @aeztrest demos HotSlot: finding storage conflicts that limit parallel execution on Monad Join us live on X!
2
2
2
27
2,368
white paper is out tl;dr: private domains on @Monad, confidential state AND public settlement -> txs encrypted to the domain ordered by Monad -> operators execute in Monad’s order, there is no consensus -> contracts message across domains -> access rules written in Solidity
Last month, we introduced Monad Private Settlement. Today, we're publishing the technical white paper. It details private execution domains, shared sequencing on Monad, cross-domain messaging, and configurable access controls. Read the research: category.xyz/mpsd-whitepaper
1
8
64
1,395
Proud to be part of @odtublockchain 💜 Thanks for co-hosting Monad Blitz Ankara and for all the support!
Back-to-back 1st place for ODTÜ Blockchain 🏆⚡ Our builders took home 1st place at Monad Blitz Ankara, co-hosted by ODTÜ Blockchain and @monad × @monad_dev on October 24! 🥇 Eyüp Efe Karakoca (@EyupEfeKrkc) & İrem Saniye Baran (@iremsbaran) — Kapalı Zarf Kapalı Zarf brings Vickrey's sealed-bid, second-price auction mechanism to DeFi liquidations on Monad. In traditional DeFi liquidations, the fastest bot typically acquires collateral at a fixed discount, capturing value that could otherwise return to the borrower. Kapalı Zarf changes this by introducing a trustless auction mechanism where liquidators submit sealed bids, reveal them onchain, and the highest bidder wins while paying the second-highest price. The outstanding debt is repaid, and the remaining surplus goes back to the borrower. In a real Monad testnet scenario, Kapalı Zarf returned $85 to the borrower instead of just $10 through conventional liquidation, completing the entire auction in approximately 3 seconds. 🔗 Demo: kapali-zarf.vercel.app 🔗 GitHub: github.com/iremsaniyebaran/k… Huge thanks to @monad and @monad_dev for co-hosting this event with us, and to everyone who joined us for a day of building on Monad! 💜⚡
1
8
271
We will be live at 3PM UTC this Wednesday on X!
Devrel Livestreams #15: Blitz Ankara Edition On Wednesday, November 4 at 3:00 PM UTC, we’re going live with two Monad Blitz Ankara winners: 🥈 @mericcintosun demos Mavera: a paid API that shares revenue with holders on every x402 call 🥉 @aeztrest demos HotSlot: finding storage conflicts that limit parallel execution on Monad Join us live on X!
1
11
461
port retweeted
Github in permission terms is still living in 2020 not 2026. It's not "AI native" if you want to use lingo. We need better and more extensive authorization for agents.
Remove your main @github account from your computer. Now. Give your AI agent a separate GitHub account with minimal permissions per repo. Let the agent create PRs, then use your main account to review and merge them. Obvious advice, but essential in the age of AI agents.
2
1
7
685