
WΞS 🛡️🦇🔊🏴 (✸,✸)
6.7K posts

WΞS 🛡️🦇🔊🏴 (✸,✸)
@wesleytate
Software degengineer pioneering the development of the next generation of crypto, web3, and AI
Brooklyn, NY Katılım Şubat 2009
4.7K Takip Edilen2.1K Takipçiler

My GitHub contributions are up 2304% over the last 6 months areyougoingexponential.rhys.dev/wesleysmyth
English
WΞS 🛡️🦇🔊🏴 (✸,✸) retweetledi

NFTs showing strength for the first time this year 👀
Imagine the NFT cycle is coming back, what’s the ONE collection you’d hold? 🤔

nxxn@sol_nxxn
We will never see this happening again ❌ Biggest NFT sales on Ethereum and Solana 👇 What was your most expensive NFT?
English

@Reshusaur Step 1: Connect your laptop to your phone’s hotspot
Step 2: Take out your wallet
Step 3: Put your wallet in one of those two spaces next to the trackbar on your MacBook
Step 4: Close your laptop so it can fit in your bag but stays open enough to be on + connected to your hotspot
English


15 underrated NFT projects
DeadFellaz (October 2021)
CyberKongz (Genesis 2021)
Cool Cats (July 2021)
Gutter Cat Gang (June 2021)
CrypToadz (2021)
The Plague (2021)
Rektguy (2021–2022)
Chimpers (2021)
Creepz (2021)
Doodles (2021)
Sup Ducks (2021)
Creature World (2021)
Invisible Friends (2021)
The Mories (October 2021)
Mutant Cats (2021)
Who am I missing ?
English

This is my 3rd week as VP of Engineering DeFi at @Polymarket , and I'm going to be straight: the traction @Polymarket has seen has massively outpaced our infrastructure, and we haven't done nearly enough to scale to keep up. I hear you, and fixing this is our entire focus. We're a major company now, and we need to engineer like one. Here's exactly what we're doing:
- Onchain data latency. We're working on making this near-instant so the experience is incredible.
- Chain migration. We need more block space, cheaper gas and much smaller block times so settlement is instant.
- Transactions are getting cancelled. We understand this is one of the most frustrating issues right now, and we have a complete fix coming very soon.
- Massive focus on the website to make it faster, more responsive, and with better UX.
- We added observability everywhere. Proper alerting so we catch issues ourselves, market makers should not be the ones telling us something is down. That's been unacceptable, and we know it.
- E2e tests throughout, starting with the CLOB, so issues get caught in CI before anything ships.
- CLOBv2 is not a rewrite. It won't improve performance or stability on its own; it's an upgrade that unlocks us to move fast right after. We'll do better with communication next time.
- We are rebuilding the CLOB from the ground up. Most important thing we're doing. Without it, we can't be the best DeFi exchange in the world. We know it, we're on it, it's mission critical.
- Unified TypeScript SDK for all APIs, which is shipping soon.
- Unified API. One WS connection for everything, with a schema that's actually readable.
- New Polymarket contract in the works that unlocks things that are simply impossible on the current protocol.
- New hires: Head of QA Automation, Head of Dev Tooling, Head of Internal Tooling, Head of Data Engineering.
- Smaller, dedicated teams. Fewer focus points per person, clearer ownership. People do what they're good at and are accountable for it.
- Working closely with customer support to give them real debugging tools so any user issue gets properly diagnosed, not lost.
- Proper communication with marketing and market makers so everyone knows what's coming and when, and MM can submit feature requests with a clear path to get them into engineering and shipped.
- Working with 4 security teams daily to ensure we're super secure and that funds are always safe.
- Perps incoming. Brand new contracts and a backend built from scratch in Rust. We're proud of this one.
- A lot of other fixes are running in parallel right now.
Starting next Friday, I will be posting weekly engineering updates.
I joined because I genuinely believe in what @Polymarket is trying to do. @shayne_coplan built this so the world has somewhere to go to find out what's actually going to happen, not what the media thinks, not what a pundit says, but what thousands of people are willing to put money on. But right now, our engineering isn't living up to that. We've let people down, and I'm not going to dress that up. I came here to fix it, and that's exactly what we're going to do. The next few months are going to speak for themselves. Stay with us.
English

Gee, I wonder what chain they're going to move to 🧑🚀
DEGEN NEWS@DegenerateNews
ICYMI: @Polymarket WORKING ON CHAIN MIGRATION
English

Stani’s the goat and he’s backing it up with action
Stani@StaniKulechov
Aave is my life's work and we're working nonstop to find the best possible outcome for users. I’m personally contributing 5000 ETH to DeFi United as we continue working together with partners on formalizing more commitments. I’m working to see this resolved and market conditions normalized as soon as possible. DeFi United.
English
WΞS 🛡️🦇🔊🏴 (✸,✸) retweetledi

I just claimed my .agent domain and joined the .agent community! get yours now and help shape the future of autonomous agents #52NF2UOW" target="_blank" rel="nofollow noopener">agentcommunity.org/join#52NF2UOW @agentcommunity_
English
WΞS 🛡️🦇🔊🏴 (✸,✸) retweetledi

vibecoder asks claude code to build a chat app, gets a working prototype in 20 minutes, immediately tweets "just killed slack and discord"…
brother you don't even know what a distributed system is. you don't know what database replication means. you have no idea how websocket connections behave at scale or what happens when 50k people are online at once and someone's message needs to show up in 200ms across 3 continents
slack has engineers making $300k+ who have spent a decade solving problems you don't even know exist yet. race conditions, eventual consistency, message ordering, presence systems, file storage at scale, search indexing across billions of messages
your app works on localhost with 2 connections. that's not the same thing as "killing slack" that's a college homework assignment
the prototype is maybe 0.5% of what makes these products actually work in production. the remaining 99.5% is infrastructure, reliability, edge cases, and years of iteration on problems that only surface when real humans use your thing at scale
and the worst part is the confidence. "yeah its not perfect but ai one-shotted it, just need to adjust a few things and deploy" - the few things you need to adjust IS the entire product. thats like pouring a foundation and saying you basically built a skyscraper, just need to adjust a few things
ai is genuinely incredible for building tools and prototypes. i use it every day. but there's this weird thing happening where people who have never shipped anything to real users at scale now think the hard part of software is writing the first 200 lines of code
it never was bro
English













