jns.eth

Where does Yuki Tsunoda qualify for the Japanese GP?

You can see why crypto has trouble finding PMF just by watching founders and execs spend all their time on here and in telegram groups arguing why they’re right about something that doesn’t work.

As a German I'm terrified the Nazis got almost 20% of the vote in Germany. As an American I'm glad the Nazis only got 20% of the vote.

"WHERE THE F*CK IS LOCALHOST HOSTED" overheard at treehacks

Hosting a crypto developer unconference next Thursday at Fort Mason in SF. Think conference but better: no preset agenda. Show up, pitch the topics you're passionate about, and we’ll choose the best ones for lightning talks. Everyone's a builder here - come shape the conversation. More info in the link below

Can’t wait for this feature @jnsdls is building. Product updates right at your doorstep (dashboard). 👏

would you hire a marketer to write your code? so why do you let devs do your marketing? make it make sense

is @YouTubeTV ok? Their service was already beyond expensive because you STILL have to sit through ads when you pay the monthly fee (horrible experience). Not even @HBO costs almost $100 and they produce high quality shows. I was considering canceling and def will be now.

Crypto apps are evolving: either wallets are embedding apps (like Phantom) or apps are embedding wallets (like embedded wallets). We wanted to understand how @privy_io fits into this picture, so we ran some experiments—and what we found was pretty interesting. 🤔 We tested transaction confirmation times from Bangalore, India (with the RPC in US East). Here's what we saw: 1⃣ With an ethers signer, it took ~3 seconds to get confirmations (polling every 500ms). 2️⃣ With Privy’s provider? It takes 10 seconds. 🚨 So, we started digging into what’s happening under the hood. Privy’s SDK is awesome—it works out of the box with ethers/viem/web3.js providers, making integration super easy. But it comes with some quirks. 1️⃣ It fetches the transaction by hash. 2️⃣ It waits for the transaction receipt. If your SDK already polls for receipts, these extra steps mean additional RTTs, and that’s where the delay creeps in. We thought, “Okay, let’s lower the polling interval.” But even setting it to 500ms didn’t help because Privy’s auth wrapper spins up a provider with a fixed 4s polling interval. So, no matter what you do, you hit that bottleneck when polling for hash/receipt. 😵‍💫 Here’s what worked: Instead of using Privy for everything, we switched to using it only to sign and send transactions. Build your transaction with your SDK and then use Privy like this: By doing this, we avoided extra polling delays and got much better performance. The lesson? Building on high-throughput chains like @monad_xyz doesn’t automatically mean a great user experience. You need to optimize every millisecond of latency. Pairing Privy with geo-distributed RPCs can further reduce transaction confirmation times and make your app lightning fast. ⚡ @KuruExchange we care about UX.