Molecular Execution Machine (@mem_tech) header
Molecular Execution Machine (@mem_tech) profile picture

The web3-ready serverless functions platform. Build and deploy trustless dApps in record time ⚡ by @decentlandlabs

Permaweb
Joined June 2023
119 users hold MEM-wrapped USDC on @aoTheComputer... Watch out, Circle Bridging guide: blog.mem.tech/molecular-brid…
2
2
17
1,448
The Molecular Bridge uses a lock-mint mechanism explained in full in the announcement post: blog.mem.tech/molecular-brid…
1
5
751
The EVM <> @aoTheComputer bridge is now live in testnet. You can now send Sepolia USDC to MEM and ao at mem.tech/bridge 🗒️ guide: blog.mem.tech/molecular-brid…
8
23
6
72
14,309
Testing MEM-wrapped USDC on @aoTheComputer today inside @arconnectio
1
3
1
27
3,116
Close to testnet release for Molecular Bridge. Ethereum <> MEM <> @aoTheComputer teapawt.org/decentlandor/status/17…
A significant leap in the MEM ecosystem, and for Arweave overall. MEM's serverless functions will now integrate native financial features, not only for MEM but also extendable to other protocols 👀 Which ERC20, and L1/L2 networks would you like to see the bridge supporting?
2
14
2
40
8,774
MEM 🤝 @aoTheComputer With this molecule, MEM can now read and compute with ao process states. This is going to be vital infra for the upcoming MEM <> ao bridge going live in the next couple of weeks 👀 github.com/decentldotland/mo…
4
13
1
46
12,403
Ethereum -> MEM -> ao Testing USDT on @aoTheComputer via the MEM bridge 🌉
4
18
5
64
8,920
4/ Here's where MEM comes in. Within AO, MEM will act as an open compute oracle, running non-deterministic programs and accessing any data on the internet. (Timestamp on the launch video -- 20:25)
1
4
309
The IDE also now has full support for KV (key-value) storage. The CLI's context tab reads the KV object as an alternative to state.json. KV enables storing and retrieving specific portions of the state during any interaction, eliminating the need to process the entire JSON object while reading state. docs.mem.tech/3em-mem/key-va…
1
2
154
Deploying to MEM Carbon is just one click in the IDE. Grab the function ID from the IDE console to test UI integration, or simulate any interactions you need in the browser itself.
1
1
52
The MEM IDE v2 is live: mem.tech/ide v2 features Carbon Testnet support, full KV support, and a 60% speed boost. Now you don't even need a development environment to build and deploy to MEM.
2
5
10
2,787
MEM SDK V1 now provides easy access to a function's key-value data -- a highly performant way to read and write to storage. Read more on KV: docs.mem.tech/3em-mem/key-va…
1
5
211
.fork is the way to duplicate existing MEM function code and deploy it under a new ID, with or without updates to the state. This enables the factory model in MEM for the first time. 🏭 teapawt.org/mem_tech/status/174804…
Replying to @mem_tech
Since forking can be programmatic and run from inside an existing MEM function, this enables the factory model -- a way to deploy a master function and create instances from that basis. A simple registry can be used to index forks, like in this example: github.com/decentldotland/mo…
1
3
32
The MEM Carbon Testnet is a temporary environment to build and test functions before submitting them to the mainnet whitelist. teapawt.org/mem_tech/status/172480… The SDK now allows a new `Mem` object to be instantiated with either mainnet or testnet configuration.
The MEM testnet (Carbon) just went live. ⚡️🔌 No more whitelisting to test in a production environment! Just hit the mem-testnet.xyz endpoint to deploy and write to testnet functions. Full examples in the docs: github.com/decentldotland/me…
1
2
30