The level of excitement from the BAM announcement last week has been absolutely insane 💥 We’ve received >200 inbounds from apps, validators, institutions and even apps from other chains(!) looking to build unique features in BAM to unlock features Only Possible on Solana.

think this is spot-on. too many folks got stuck on the distribution part but missed the "new primitive" part around how to reduce time for integration and consider a world where authentication can be pushed to the last step, rather than the first step

Hey @hosseeb, founder of Dialect here, the team that co-launched blinks with @solana. Glad to hear blinks are still on your mind, & that you were bullish on the idea. Wanted to take a bit of time to give a thoughtful answer on why blinks didn't take off, why the viral launch last summer was as much a curse as it was a blessing, & why despite that we are still very actively working on them. 👇 I’m just gonna say it: there was no world in which blinks as they were launched, as chrome extension injection tricks in Twitter, were ever going to work. And that was never our strategy. The biggest misconception was that blinks *are* the extension tactic. They aren’t. That tactic was something we added just a few weeks before launch, & it comes with a whole host of problems. A lack of mobile support is just one of many I can name. We learned very quickly from the data last summer that 99%+ of all interactions with blinks were not happening on Twitter via this extension trick because of those problems, but instead people using them on sites & in apps where they were natively integrated. I can also share some stats with you: 100s of millions of views, 10s of millions of transactions. But they don’t impress me & they shouldn’t impress you. Yes, we are still very actively working on blinks. (Breaking: startup is working on a non-consensus bet.) But to solve very different problems, more like the ones we originally set out to solve. Let me explain. Blinks are APIs for transactions—literally URLs for the blockchain, a.k.a. “blockchain links”—that allow developers to integrate actions into their apps orders of magnitude faster. Less sexy, much more useful. E.g. we’re working with a number of mobile wallets to help them become super apps. Use blinks to bring quick deposit/withdraw actions to all your DeFi positions with no redirects. Something that would take a lot of time for a wallet team to grind out themselves. With blinks it can be done in a fraction of the time. We’re also using blinks to bring 1-click, no-rediect CTAs to our Alerts Stack, used by teams like Jupiter. Top up your collateral, avoid liquidation, take profits. Right from the notification. Or AI agents can use blinks as a standard transaction backend to integrate more capabilities faster. These are just 3 surfaces. There are so many more. Blockchain links as I see them are a critical, missing piece to deliver on the promise of composability in crypto. They are the 4th piece alongside shared state (the blockchain), shared action language (the tx), & shared auth (the wallet): they are the APIs to make integrations, & composability, actually buildable. Blinks are an inevitable technology, one that Twitter & every other big platform should natively integrate, with no extension tricks. But that’s a much longer road. For now, we’re focused on solving real problems for the teams who get it & are bought in to our mission.

Crypto SaaS ≠ Web2 SaaS This is by far my favorite thing about product design in crypto. Look closely enough at any service you’re building, & whatever web2 analogies you think you can reason from start to break down, forcing you to think, & design, from first principles. Yes, our alerts stack saves you time & money like any good SaaS (see qt). But we’re extending it in 3 crypto-native ways that turn it into something else entirely. Rolling one of those out right now with some early design partners. DM me if you want access 📥

There are two types of devs: 1. Those who think building alerts are easy 2. Those who have actually built alerts It’s way more complicated than you think. Do your users a favor. Use our alerts stack, & spend all your engineering time on sending your users great, useful alerts

Connected with a team recently about our alerts stack. Got to them just a bit too late, they were already nearly done with an in-house build of their own. By the time the call ended we were talking about how much time they could have saved if they’d known about our alerts stack. They may still swap us in instead. I’m gonna keep saying it: alerts are not a trivial thing to build. User subscriptions, topic & channel management, paginated APIs for an in-app inbox, unread badges & read statuses, CTAs & analytics. Bundled push notifications from Firebase (yes, we bundle push notifs). And that has nothing to do with delivery. Want to reach a large user base very quickly? That requires some sophisticated delivery & queuing infrastructure. We power alerts for @jup_mobile, the fastest mobile app in crypto (@weremeow did I say that right). We've handled 100s of millions of requests for them, including all of their Firebase push notifs, without skipping a beat. We can handle your user base. Want to add email, text, telegram support? Each of those is a new channel integration & set of configuration APIs for user preferences. And that’s just the alerts plumbing. You still don’t have any *actually good* alerts, which themselves take time to build. And if you screw that up you’ll churn a ton of users, who will unsubscribe & turn of push notifications for your app, and now you’ve lost one of your most precious engagement tools. All of the above is 100% boilerplate code that is not what makes your company great. If you use our alerts stack, you’re done with the infra in a fraction of the time, & can then focus all of your attention on sending *great* alerts: personalized, timely alerts from your backend in 1 line of code, or even have your growth & marketing teams use our dashboard to send product updates & company announcements. And the final cherry on top: our alerts stack is built from the ground up for crypto, you’ll get reach in a novel new way with our Universal Inbox 📥, which is live today in @jup_mobile as Radar. Teams like @jito_sol & @sanctumso are using the Universal Inbox as a new comms channel alongside Twitter, email & others. In other words: our Universal Inbox more like SMTP than just web2 alerts SaaS. With our stack, you’re communicating with a user’s *wallet*, & it follows them wherever they go. Seriously. Choose life. Just use our alerts stack. Our docs got a huge revamp & are crazy easy to read (s/o @bjoerndotsol), or DM me if you need help getting set up. 📥☀️

The Dialect engineering team did some *serious* performance work in the lead up to our alerts stack launch with @JupiterExchange. @jup_mobile is one of the fastest apps in crypto, & their alerts should be too. There was *zero* chance we would ship something for them that doesn’t absolutely hum. Some system design & stats: —Our Alerts Stack can handle north of 1M DAU, across our APIs for both sending alerts server side, & managing an inbox feed & user subscription preferences from the client. —Many time-sensitive alerts need to reach users quickly. We have a “burst mode” that can support orders of magnitude higher usage for up to dozens of minutes at a time. —A priority queue handles different kinds of delivery pipelines. E.g. high priority alerts for things like limit orders or liquidation warnings that need fast delivery, & lower priority for broadcast alerts like company announcements, that can be delivered to users over longer timelines. —The result: we’ve handled hundreds of millions of API requests across our Alerts Stack in just the last few weeks, all without a hitch. I’m insanely proud of the work @tsmbl_dev & our engineering team did to deliver for Jupiter, & we’ve got bandwidth for a lot more. If you’ve got a cracked product & need cracked alerts infra, DM me. 📥

The vast majority of spot volume and liquidity will aggregate to a few monolithic L1s @Grayscale's new report on DEXs highlights that @RaydiumProtocol, the industry leader, is only deployed on @solana, compared to Uniswap which is on 28 chains

Introducing BAM: The Block Assembly Marketplace that revolutionizes how Solana processes transactions. Private. Transparent. Verifiable. This is how Solana wins ⬇️

Realms v2 is live. The next chapter for onchain governance on Solana. Built for the next wave of DAOs. Faster. Sharper. Yours.