Wadhawan | avinashxw.near

whatever you are, be good at one

[Wadhawan | avinashxw.near @avinashxw]

@insanekrishnaa Interested!

[Georgios Konstantopoulos @gakonst]

The Machine Payments Protocol now supports splits!

This lets you split a single charge across multiple recipients in 1 transaction.

This is the most useful for:
- Marketplaces taking a fee
- Referral programs paying a bountee to the referrer
- Revshare

Check the docs below.

[Dan Romero @dwr]

$0.001 flat fee paid in stablecoins to send money on Tempo.

No separate gas token required.

[jesse.base.eth @jessepollak]

The beautiful thing about AI is that it let's anyone become a builder.

And more builders in the world is a beautiful thing.

[Base @base]

Welcome to Base app

[Xen @XenBH]

How @base is becoming a network state - from today’s network state conference.

[santosa @0xSantosa]

Real Onchain Adoption is Happening and @base is Leading It

When we talk about “onchain adoption,” it’s easy to get lost in the noise; hype cycles, narratives, and fleeting trends. But what Base is doing feels different.

Base isn’t just growing numbers; it’s growing behavior.
From thousands of new creators and developers building and creating directly on Base, to real users experimenting with creator coin, identity, collectibles, and DeFi and trading. This is the closest we’ve been to mainstream onchain culture.

Platforms like Zora, Farcaster, and @baseapp App are shifting user behavior from simply posting content to enabling true creator coin adoption. It’s a game-changing moment where every piece of content can represent real, onchain value.

Because real adoption means people actually using blockchain, not because it’s crypto, but because it’s useful.

Base is showing the world exactly what that looks like.
We’re not early anymore, we’re onchain. Thanks for bring me into Base @jessepollak @CryptoStatuette

[Dhanian 🗯️ @e_opore]

How does Docker work?

You write a Dockerfile (or use an existing image) that defines the environment, dependencies, and commands your application needs.
Docker reads this file and builds a container image , a lightweight, standalone, and executable package that includes everything required to run your app.

When you run a container:
→ Docker uses the container runtime to create isolated environments using Linux kernel features like namespaces and cgroups.
→ Each container shares the host’s OS kernel but runs in its own isolated process space.
→ The Docker daemon manages containers, images, volumes, and networks.
→ The Docker client (CLI) communicates with the daemon through REST APIs to build, run, and manage containers.

At runtime:
→ Docker ensures consistent execution by providing the same environment across development, testing, and production.
→ It manages networking, volumes for persistent data, and image caching for faster deployment.
→ Containers can be orchestrated using tools like Docker Compose, Kubernetes, or Swarm for scalability and automation.

The result: Docker delivers fast, portable, and reliable application deployment , the same code runs identically everywhere, from a developer’s laptop to cloud production servers.

👉 Want to go deeper? Check out this ebook:
Mastering Docker & Containers: From Beginner to Advanced Deployment
https://t.co/lIKb9UCyHl

[Dhanian 🗯️ @e_opore]

The Complete System Design Fundamentals

Core Concepts
├── Foundational Principles
│ ├── Scalability (Vertical vs Horizontal)
│ ├── Reliability & Fault Tolerance
│ ├── Availability & Uptime
│ └── Maintainability & Extensibility
├── Key Characteristics
│ ├── Latency vs Throughput
│ ├── Consistency Models
│ └── CAP Theorem

Architectural Patterns
├── Monolithic Architecture
│ ├── Simple Development
│ ├── Easy Deployment
│ └── Limited Scalability
├── Microservices Architecture
│ ├── Service Decoupling
│ ├── Independent Scaling
│ ├── Technology Diversity
│ └── Distributed Complexity
├── Event-Driven Architecture
│ ├── Message Queues
│ ├── Event Sourcing
│ └── CQRS Pattern
└── Serverless Architecture
├── Function as a Service
├── Auto-scaling
└── Pay-per-Use

Scalability Strategies
├── Load Balancing
│ ├── Round Robin
│ ├── Least Connections
│ ├── IP Hash
│ └── Health Checks
├── Caching Strategies
│ ├── CDN Caching
│ ├── Application Caching
│ ├── Database Caching
│ └── Cache Invalidation
├── Database Scaling
│ ├── Read Replicas
│ ├── Sharding Strategies
│ ├── Federation
│ └── Denormalization
└── Asynchronous Processing
├── Message Queues
├── Background Jobs
├── Event Processing
└── Batch Processing

Storage Systems
├── Relational Databases
│ ├── ACID Properties
│ ├── PostgreSQL, MySQL
│ ├── Indexing Strategies
│ └── Transaction Management
├── NoSQL Databases
│ ├── Key-Value Stores (Redis, DynamoDB)
│ ├── Document Stores (MongoDB)
│ ├── Column Stores
│ └── Graph Databases
├── File Storage
│ ├── Block Storage
│ ├── Object Storage
│ └── File Systems
└── Specialized Storage
├── Search Engines
├── Time-Series Databases
├── Data Warehouses
└── In-Memory Databases

Communication Protocols
├── Synchronous Communication
│ ├── HTTP/REST
│ ├── gRPC
│ ├── GraphQL
│ └── Service Mesh
├── Asynchronous Communication
│ ├── Message Brokers (Kafka, RabbitMQ)
│ ├── Pub-Sub Systems
│ ├── Event Streaming
│ └── WebSockets
└── Network Fundamentals
├── TCP/IP Stack
├── DNS Resolution
├── Load Balancers
├── API Gateways

Distributed Systems
├── Consensus Algorithms
│ ├── Paxos
│ ├── Raft
│ ├── Leader Election
│ └── Distributed Locks
├── Coordination Services
│ ├── ZooKeeper
│ ├── etcd
│ ├── Consul
│ └── Service Discovery
├── Data Consistency
│ ├── Strong Consistency
│ ├── Eventual Consistency
│ ├── Conflict Resolution
│ └── Vector Clocks
└── Distributed Transactions
├── Two-Phase Commit
├── Saga Pattern
├── Compensating Transactions
└── Idempotency

Performance & Optimization
├── Caching Layers
│ ├── Client-Side Caching
│ ├── CDN Caching
│ ├── Application Caching
│ └── Database Caching
├── Content Delivery
│ ├── CDN Networks
│ ├── Edge Computing
│ ├── Static Asset Optimization
│ └── Compression Techniques
├── Database Optimization
└── Monitoring & Observability

Security & Reliability
├── Security Measures
├── Reliability Patterns
├── Data Protection
└── Compliance & Governance

Real-World System Examples
├── URL Shortening Service
├── Social Media Platform
├── E-commerce System
├── Video Streaming Service
├── Ride-Sharing Application
├── Payment Processing System
├── Real-time Chat Application
└── Search Engine Architecture

Design Methodologies
├── Requirements Analysis
├── Architecture Decision
└── Implementation Planning

Get my Complete System Design eBook here: https://t.co/aE1KNO717x

[Youssef @0xyoussea]

I quit my non-crypto job early 2022 to build a startup in crosschain gaming infra

We endured Luna and I kept going, even moved to another country to keep building

Months later, we barely had a few grants to keep the lights on for a few months, and almost no traction but I kept going...

Then FTX happened, and it was tough to sunset the company a few months after that, but I still had deep conviction we will bounce as an industry, as I had seen how much talent and grit we have here vs non-crypto jobs I worked before

Many times I look back at that period as some of the best moments of my life

Feeling cornered and fighting for your life feels deeply meaningful and teaches you a lesson that will stay with you forever

I dont wish those moments at anyone, but if you happen to be in one, be grateful that you get to live this. Most people never do, they live and die fearing trivial events like getting fired or losing some meaningless wealth.

It's your time now to write that incredible come back story of yours, dont fumble this, you got this anon

[EigenCloud @eigencloud]

What does the future of unstoppable, verifiable agents look like?⁣
⁣
In his talk at @HackMIT, @gajesh shared the journey from a $7M teenage project to building @eigencloud and why verifiable code changes everything.⁣
⁣
The future is open, and we’d love for you to be part of it.⁣
⁣
0:00 Intro⁣
0:27 Story of a 13-year-old building a $7M app⁣
1:12 Gaj’s coding journey⁣
1:43 The Unstoppable Verifiable Future ⁣
2:48 Call to Action: Verifiable Agents⁣
⁣
Full video here 🎥👇

[Ayush Garg @ayushxgarg]

QR keeps giving

there's no better way to experience it than to go bid on the onchain attention machine, it pays off

[Ayush Garg @ayushxgarg]

expanding on the SHIFT index:

-the 25% supply swapped in phases into @base ecosystem tokens will be entirely earned through fees claimed via @clankeronbase
-the index will be updated/rebalanced on a frequent basis and can be tracked on @indexy_xyz (https://t.co/lI0y048AlO)
-the purpose is to activate the attention flywheel and further the shared upside

other things:

-the burn is capped at 1bn supply, of which 800mn+ have already been processed
-remaining 75% supply is reserved for the community, distributed through various mechanisms

just getting started

[FinFloww @FinFloww]

Zudio is hurting DMart’s business!

But when DMart is a supermarket with 76.8% of it’s revenue coming from groceries,

then how has a clothing company like Zudio been able to hurt it’s business?

THREAD: here’s why this is happening🧵

[Shreya @shreyamatsharma]

I was at the Kensington Oval for the WC finals & this is my version of what I saw at the stadium:

I was seated at long on, it was 14.4 when Klaasen hit Axar for another 6, & single handedly deflated India. By the end of the over India will have conceded 34 runs in 8 balls. Scoreboard read 30 off 30 with 6 wickets in hand.

Players shoulders had dropped. Intensity was gone. South African pavillion which was right besides me, was clapping and cheering, loudest of the day. Fans mostly Indians had gone quiet.
Onslaught from Miller & Klaasen was so brutal, you could feel the eerie uneasiness in the atmosphere. Fans had succumbed to lost cause, shocked at what had just happened, already talking about losing 3 finals in 12 months. Some promising never to go to another game ever. Resigning to weeks of depression and sadness that was going to ensue.

Ball was now given to by no means a lanky pacer. In land of Joel Garner, the big bird, this was a small bird at best. He ran in to complete the formalities, but he had other ideas. He still had 12 legal deliveries or 40% of game to make any sort of impact.

South African support staff just sat a little more upright now. Their plan to score runs off spinners had worked brilliantly, hard part of the job was already done.
Each ball was an event in that over, every delivery he bowled, it felt like electricity would run through entire stadium. All the deflated, undercharged fans and players were getting turbo charged by this genius, one ball at a time. That over did not bring any wicket, but it charged everyone in that ground, he instilled belief it's not fucking over yet. Dropping shoulders were more upright now, nervous energy was rushing through SA camp.

I will do injustice to describe how it felt, but best I can describe is he was the pied piper of Kensington oval, a true genius, a magician was at work that afternoon. It felt like SRK was giving his 70 minute Chak De speech or was listening Nawazuddin Siddique's Bajrangi bhaijaan news report or Vicky Kaushal's URI rally. That over was nothing but a rally cry for the stadium.
Some 70 year old's in first row were banging the barricade, not worrying about their weak bodies, younger ones shouting so loud, their vocal cords would fall off, clapping so hard their hands were on the verge of bleeding. Entire stadium was now turbo charged pro max.

Miller and Klaasen knew they will need to work around this magician. Their skills too pale today in front of his brilliance. In comes Hardik, India's only choice at the moment. They knew this is a golden chance to score runs off this over and game will be sealed shut. Klaasen goes after it and Hardik reaps rewards. Belief even stronger now. Hardik bowls a clutch over, manages to keep the momentum in India's favor.

The pied piper comes back for his last 6 balls. Stadium was already rallying behind him, it was the time to hit the hammer. Jansen who had a poor game until now was visibly under confident. First up to Miller and it was a peach. Jansen on non striker end dreading to face the magician. His turn came on ball 4. Ball flew one bounce to boundary past Rishab Pant, but only after taking one of the bails with it. Grandstand which was built only for this world cup and was a temporary fixture could collapse any minute by the sheer thumping it was taking by the fans jubilant. Dark clouds forming over with lightning in the distance. You could not tell if it was the weather system or our very own Thor's doing who was welding his hammer.

Maharaj coming in next had one job now, shield Miller from this Thor. He manages to do that but only to read 20 off 2 overs. India's best ever had 6 runs, 1 wicket coming off in his 2 overs, but more importantly he had rallied his teammates, electrified an entire stadium and made SA dressing room running firmly on nervous energy now

I witnessed magic, a leader, and a spell of pace bowling in the lands of Marshall and Garner which even they would be mighty proud of.

[Akshay BD @akshaybd]

Product so good it markets itself.

Community so good it multiplies itself.

[Kirill Balakhonov @balakhonoff]

Farcaster: The Decentralized Social Graph Protocol Empowering Creators 🌐🚀

In the rapidly evolving world of Web3, @farcaster_xyz is emerging as a game-changer for the future of social media. As a decentralized social graph protocol, Farcaster provides the foundation for building innovative social applications that put creators first. 💪

Here's what makes Farcaster stand out:

1. Decentralized User Profiles: On Farcaster, user profile ownership is recorded in an on-chain contract, while a network of external nodes called Hubs process all user interactions and relationships, such as posts, follows, and more. This decentralized architecture ensures user control and data portability. 🔒

2. Customizable Apps: Developers can build apps on top of the Farcaster Hub network, leveraging existing user data and posts (called "casts"). The most popular app built on Farcaster currently is @warpcast_ , a Twitter-like social app created by the Farcaster team itself. 🏗️

3. Expandable Functionality: What sets Farcaster apart is its ability to extend functionality through Frames and Actions. Frames allow third-party apps to render mini-apps within a Farcaster cast, while Actions are custom button extensions that enable users to perform additional tasks, like tipping. This opens up a world of possibilities for app developers and creators alike. 🌈

4. Empowering Creator Monetization: Frames and Actions give creators unprecedented control over how their content is used, interacted with, and monetized. For example, Frames can include a link to an NFT mint or require viewers to hold a specific token. This allows creators to experiment with content scarcity and unique loyalty programs, opening up new avenues for monetization that are impossible on traditional social platforms. 💸

As the Web3 ecosystem continues to grow, protocols like Farcaster are laying the groundwork for a more decentralized, creator-centric social media landscape. By providing the tools for developers to build innovative apps and empowering creators to monetize their content in new ways, Farcaster is positioning itself at the forefront of this exciting new frontier. 🔥

What are your thoughts on the potential of decentralized social graph protocols like Farcaster? How do you think they will shape the future of social media and the creator economy? Let's discuss in the comments! 💬

#Farcaster #Web3 #CreatorEconomy #Decentralization

[Optimism @Optimism]

The Superchain is for Everyone.

[Optimism @Optimism]

Welcome @BuildOnCyber to the Superchain. 🟢

Cyber is making launching decentralized social apps on the Superchain as simple as possible.

[Wadhawan | avinashxw.near @avinashxw]

Just started using https://t.co/V0BO5UOC6Y and it worked like a breeze!

Shoutout to Alchemy for making it happen.