akasha

[COMMUNITY HUB] [Practicing Ethereum] Ripe Ideas For Entrepreneurs in Crypto @akxsha, @vsinghdothings, @yosephayele, and Theo Fields | 12:00pm

What can only exist on Ethereum? An open session on the protocol's real frontier use cases, using CROPS as the guide. With @akxsha, @vsinghdothings, @sodofi_, & @christine_dkim [Practicing Ethereum] Ethereum’s Frontier, Today | Community Hub · 12:00pm

You do not have to agree with me on which applications are and are not corposlop to use Ethereum. You do not have to agree with me on what trust assumptions are acceptable in which situations to use Ethereum. You do not have to agree with me on political topics to use Ethereum. You do not have to agree with my views on defi, decentralized social or privacy-preserving payments to use Ethereum. You do not have to agree with my views on AI to use Ethereum. You do not have to agree with my view that Berlin has the best food in Europe, suits and ties should be expunged from our culture, and YYYY-MM-DD is the best date format to use Ethereum. And you do not have to agree with me on any one of those above things to agree with me on any other. I do not claim to represent the whole Ethereum ecosystem. Ethereum is a decentralized protocol. The whole concept of "permissionlessness" and "censorship resistance" is that you are free to use Ethereum in whatever way you want, without caring about what I think, or even what anyone else in the Ethereum Foundation or even any Ethereum client developer thinks. But on the flipside, if I say that your application is corposlop, I am not "censoring" you. This has always been the flip side of the grand bargain of free speech: I am not free to shut you down, but I am free to criticize you, much as you are free to criticize me. In fact, it is *necessary* that we do this. The modern world does not call out for pretend neutrality, where a person puts on a suit and claims to be equally open to all perspectives from all of humanity and not have their own opinions. Neutrality is for protocols (like HTTP, like Bitcoin, like Ethereum), and neutrality within some scope is for some institutions. The modern world calls out for the courage to clearly state one's principles - including stating principles by pointing to negative examples, that is by criticizing the things in the world that are incompatible with one's principles - and work with those with aligned goals to build the metaverse within which those principles are taken as a baseline. Such things inherently cannot be constrained to just the layer of the protocol: any principle you have will naturally lead to conclusions, not just about how the protocol should be built, but also what should be built upon it. Furthermore, any such principle will have consequences that go beyond technology, and reach into specific questions within the larger social world. This should not be avoided. Valuing something like "freedom", and then acting as though it has consequences on technology choices, but is completely separate from everything else about our lives, is not pragmatic - it is hollow. The inevitable converse of this is that (i) a decentralized protocol must not be viewed as belonging to only one metaverse, and (ii) the borders of a metaverse are fuzzy: it is possible, and indeed it is the normal case, to align with any one on some axes and not on other axes. Linux is a technology of user empowerment and freedom, Linux is also the base layer of a lot of the world's corposlop. It's almost certainly the base layer of many things that I think are good, and you think are bad, and vice versa. Hence, if you care about Linux because you care about user empowerment and freedom, it is not enough to just build the kernel, we must also build a full-stack ecosystem compatible with those values, and explicitly accept that this is not the only way that people will use Linux, but it is one way that must be built and must be available. Ethereum is similar. Milady.

2026 is the year we move upward. To the app layer. anoma.net/blog/upward

We hosted our favorite builders at @EFDevcon (s/o to Christo T. & @minchi 🙏). Special thanks to @johnx25bd @akxsha @serensandikci @hyperseref @sagrawal @cryptowanderer & David at @circle for sharing what & how you're building. Apps are always open, link in bio.

grateful for the environment Kernel provides for creativity to flourish!! 🌱

The “trust verifiable” web, trustless compute, programmable transactions, and how @anoma rebuilds every part of the OSI stack were all covered by @akxsha in a recent fireside. The information dense presentation starts with a story from her time at American Express, and the reasons the client-server architectures the web was built upon have started to fail us. Her work at Concordance, finally, is presented: a NodeJS-like runtime environment to build decentralized applications without the complexity or compromises facing a crypto builder today. 00:00:50 - FCRA & Dodd-Frank: No laws for banking data management 00:01:40 - $400 billion data aggregator industry reselling your data 00:02:10 - Client-server architecture strips personal autonomy 00:03:00 - Banks own your data—no selective disclosure possible 00:03:30 - Building a viable alternative: opting out of Web2 00:04:10 - Trustless compute vs trust-verifiable compute 00:05:30 - Blockchains as finite deterministic state automata 00:06:20 - HTTP: sending arbitrary messages through the internet 00:07:30 - Intents: the Web3 equivalent of HTTP requests 00:08:30 - Anoma rethinks every layer of the internet stack 00:11:40 - Cross-chain trading: Popcat to USDC 00:13:00 - Counterparty discovery for matching requests 00:14:00 - Selective disclosure 00:15:40 - Composability: network routes around bad actors 00:16:50 - Solvers: offsetting computation from blockchain bottlenecks 00:21:30 - Programmable transactions: accessible Web3 for developers 00:23:00 - Concordance: writing server-like code for Web3 infra 00:24:30 - Foundational technology

In Kernel, @akxsha’s researched a simple, key question: “How do you get the blockchain to function with the same capabilities, range and enablement as a backend server?“ “The biggest challenge is finding a way to get a client-blockchain architecture where the blockchain effectively replaces the server [requirement].” Her product, Concordance, being built on @anoma, is for engineers interested in building client-blockchain apps.

When @akxsha joined Kernel, she didn’t know what her project would be. But as an engineer, the barriers to building in crypto set off the cogs in her mind. They challenged what she thought she knew, causing question after question. She decided to follow them.

@MaxLensherr sure :) Anoma's been a project for a few years now, in devnet phase currently

@akxsha Impressive and thank you How long they’ve been building now?

more than that. Anoma will be the engine that powers client-blockchain architecture, and we are taking this a step further by building a framework and platform to make it incredibly easy for developers to implement. Dapps will be interactive and truly composible, fully onchain.

thanks for the follow! i want to be more active here

It is all about state for building better applications. @anoma wholly rethinks how one approaches state, leading to an app-centric approach instead of a blockchain-centric one. An excellent explainer by @akxsha from the Intents Initiates team Concordance.

Honestly, this is what we need in Web3. @anoma solvers could finally fix the ETH fragmentation mess. 👉One app. All chains. No more L2 confusion. 👉 App-centric instead of chain-centric. Thanks @akxsha for breaking it down so clearly 👏 #Anoma #Intents #Web3 @KaitoAI

@LunWaifu089089 @anoma @akxsha @KaitoAI Preach. Chasing chains was never the point, using apps without thinking about chains is the unlock. @anoma’s solver model finally makes that feel possible. Less hopping, more doing. Let’s build where coordination actually works.

bullish on Anoma because it actually solves problems that have been around since the dawn of web3

@anoma @akxsha "Anoma revolutionizes app development by focusing on state, not blockchain."

Building better apps is all about state. Anoma introduces a fundamentally new way to approach state that's app-centric, not blockchain-centric. Excellent explainer by @akxsha from Intents Initiates team Concordance.

Concordance by @akxsha: a workflow orchestration platform to build real ‘web3’ applications. Provides an interface enabling a (serverless) client-blockchain architecture and predictable application state management, enabling a new class of onchain applications.

@adrianbrink @anoma Glad to see @akxsha (Concordance) and @sokkkkaaa + @manankpatni (Epoch) in the initial cohort. Wishing everyone well on new beginnings!