Signed in
We value your privacy
This site uses cookies to improve your browsing experience, analyze site traffic, and show personalized content.
Welcome to Pump.fun!
Pump lets anyone create coins, giving everyone equal access to buy and sell from the start. Prices can move quickly, so trade carefully.
By clicking this button, you agree to the Terms and Conditions, Privacy Policy, and certify that you are over 18 years old.
We value your privacy
This site uses cookies to improve your browsing experience, analyze site traffic, and show personalized content.
boapranois on Pump.fun — The water must flow to remain fresh
The water must flow to remain fresh
Sign in to see more
Streaks and all-time activity are only shown to signed-in users.
16.3M shiitHeld $236K MC
Here is the Dev’s (@liltechnomancer) current thesis a bit further up: A few things to research to better understand the tech. 1. Key packages released by cloudflare this year. @cloudflare/computer, Dynamic Workers, durable object facets and lots of their mechanics around sandboxing/code execution. 2. Celld, a project by Ryan Dahl the creator of node js. It made running Durable Objects easy without platform lock to Cloudflare which dramatically cuts the cost. Which i forked and ensured can be run multi-tenant with dynamic workers and the other key missing elements. To try to break down why any of it means anything as you do your research as clear as possible. Dynamic Worker -- needed for your agent throwing shit up on the web really quickly or running untrusted code. DO Facets -- Needed when you make tools that store data for your agent. Like something to track your trades. So what we can do stuff like this with other tech? Yes but the way its currently done is too expensive on every level and we need as much compute as we can get aside from cost. Agent in container == Big cost and compute Agent in DO == little cost & computer and faster start time. Now for @cloudflare/computer It gives you 1 common interface it interact across many machines with file sync. They left out syncing to local devices, so I have a fork of that too. Heres where that gets very cool. Lots of agent commands NEED a container. And we already moved the agent out of the container.... You can use computah essentially smartly route commands to the appropriate level of compute. So if you just asked him to tell you what was in some documents the whole thing is done in DO's and costs fractions of a cent and is done near instantly. You ask him to run a build of your forked and customized app, his command would wake a container, run the heavy command, then put it right back to sleep. Syncing the files back to the DO. I hope some of this makes sense.
