
ANS is migrating to ao
The Arweave Name Service (ANS) was launched as the first human-readable address protocol on Arweave in February, 2023. Since that launch, 2 years ago, over 1,300 users have registered more than 2,000 domains and helped us gain the traction needed to be integrated in a range of Arweave ecosystem apps like ViewBlock, everPay, and Arweave-compatible wallets. We had a lot of fun building in the wild west of Arweave in its pre-ao days, but it's time for ANS to make the switch for the sake of ...

WeaveVM: the hyperscalable EVM protocol on Arweave
WeaveVM (WVM) is the first EVM-compatible protocol engineered to manage complex, large-scale data computation without the high gas fees typically associated with on-chain state storage on EVM chains. WVM is also the first EVM-compatible protocol that fully relies on Arweave for permanent storage, enabling atomicity of executable EVM bytecode and data of any size on the same ledger. On the principles of VACP, we are building the hyperscalable, lazy-evaluated EVM protocol to compute data at any...

We are Decent Land Labs
Today marks a significant milestone for decent.land as we introduce a refined mission and new flagship protocol. Our journey started in 2021 with a vision to build social and identity primitives on Arweave. The first public app under the decent.land name – a way to create a permanent username on Arweave – evolved into ANS, and as the expansive web3 social landscape matured, we developed Ark Protocol. Ark enables identities from any chain to transfer their reputation into the Arweave social ec...
Storing, verifying, and computing with onchain data

ANS is migrating to ao
The Arweave Name Service (ANS) was launched as the first human-readable address protocol on Arweave in February, 2023. Since that launch, 2 years ago, over 1,300 users have registered more than 2,000 domains and helped us gain the traction needed to be integrated in a range of Arweave ecosystem apps like ViewBlock, everPay, and Arweave-compatible wallets. We had a lot of fun building in the wild west of Arweave in its pre-ao days, but it's time for ANS to make the switch for the sake of ...

WeaveVM: the hyperscalable EVM protocol on Arweave
WeaveVM (WVM) is the first EVM-compatible protocol engineered to manage complex, large-scale data computation without the high gas fees typically associated with on-chain state storage on EVM chains. WVM is also the first EVM-compatible protocol that fully relies on Arweave for permanent storage, enabling atomicity of executable EVM bytecode and data of any size on the same ledger. On the principles of VACP, we are building the hyperscalable, lazy-evaluated EVM protocol to compute data at any...

We are Decent Land Labs
Today marks a significant milestone for decent.land as we introduce a refined mission and new flagship protocol. Our journey started in 2021 with a vision to build social and identity primitives on Arweave. The first public app under the decent.land name – a way to create a permanent username on Arweave – evolved into ANS, and as the expansive web3 social landscape matured, we developed Ark Protocol. Ark enables identities from any chain to transfer their reputation into the Arweave social ec...
Storing, verifying, and computing with onchain data


Share Dialog
Share Dialog

Subscribe to Decent Land Labs

Subscribe to Decent Land Labs
>100 subscribers
>100 subscribers
MEM is a serverless functions platform for web3 developers built on the Verifiable Atomic Computing Paradigm. With this paradigm, MEM applications benefit from a trustless record of interactions and state, enshrined onchain.
But as is often the case when building developer-friendly tooling that offers web2-like UX, certain elements of the MEM stack rely on centralized endpoints and servers. Similar to RPCs in Ethereum land, while MEM data is eventually settled onchain it is broadcast to the network and consumed by users with the help of trusted endpoints, like api.mem.tech.
Until now, this was a weak point - what if the server hosting the API goes down or is censored by its provider? Even though application state is always retrievable from Arweave and data loss is not a factor, outages can render applications built on MEM temporarily unable to be interacted with.
This is a problem we are starting to solve by migrating core piece of MEM infrastructure to Akash, starting with the testnet API and molecule library dependencies.
The introduction of the MEM testnet API on Akash provides developers with two endpoint options: one provided by the MEM team, and one powered by Akash. In addition, it is also possible to self-host the APIs -- to deploy on Akash or your own hardware -- ensuring additional layers of redundancy.
MEM's move towards decentralization brings several practical benefits:
decentralized infrastructure reduces single points of failure
introduces a greater degree of censorship resistance
different endpoint options allows developers to select the most performant or reputable, and swap between them for redundancy
this shift aligns MEM's operations more closely with the decentralized ethos of web3, and further differentiates the platform from web2 alternatives
Moving the API and molecule library onto Akash is just the start for MEM's journey to full decentralization. MEM is working to deploy a custom Arweave gateway with AR.IO which will be a MEM-only alternative to current defaults like arweave.net.
Beyond that, MEM's endgame form has always been an appchain; the VACP model makes it possible to add a decentralized layer of validators which would work to idependently verify the inputs and outputs of MEM functions match the code being run. Watch this space. 👀
Sign up as a MEM beta tester at mem.tech, follow MEM on X, and join the Discord.
MEM is a serverless functions platform for web3 developers built on the Verifiable Atomic Computing Paradigm. With this paradigm, MEM applications benefit from a trustless record of interactions and state, enshrined onchain.
But as is often the case when building developer-friendly tooling that offers web2-like UX, certain elements of the MEM stack rely on centralized endpoints and servers. Similar to RPCs in Ethereum land, while MEM data is eventually settled onchain it is broadcast to the network and consumed by users with the help of trusted endpoints, like api.mem.tech.
Until now, this was a weak point - what if the server hosting the API goes down or is censored by its provider? Even though application state is always retrievable from Arweave and data loss is not a factor, outages can render applications built on MEM temporarily unable to be interacted with.
This is a problem we are starting to solve by migrating core piece of MEM infrastructure to Akash, starting with the testnet API and molecule library dependencies.
The introduction of the MEM testnet API on Akash provides developers with two endpoint options: one provided by the MEM team, and one powered by Akash. In addition, it is also possible to self-host the APIs -- to deploy on Akash or your own hardware -- ensuring additional layers of redundancy.
MEM's move towards decentralization brings several practical benefits:
decentralized infrastructure reduces single points of failure
introduces a greater degree of censorship resistance
different endpoint options allows developers to select the most performant or reputable, and swap between them for redundancy
this shift aligns MEM's operations more closely with the decentralized ethos of web3, and further differentiates the platform from web2 alternatives
Moving the API and molecule library onto Akash is just the start for MEM's journey to full decentralization. MEM is working to deploy a custom Arweave gateway with AR.IO which will be a MEM-only alternative to current defaults like arweave.net.
Beyond that, MEM's endgame form has always been an appchain; the VACP model makes it possible to add a decentralized layer of validators which would work to idependently verify the inputs and outputs of MEM functions match the code being run. Watch this space. 👀
Sign up as a MEM beta tester at mem.tech, follow MEM on X, and join the Discord.
No activity yet