Content
@
0 reply
0 recast
0 reaction
faces
@faces
Bullish on tech like this. How close is /ec being able to … • Serve a fully client-side app? (done with ipfs I suppose) • Serve a fullstack Next.js app? • Serve api endpoints written and compiled to WASM? • Incentivize communities to run bundles of programs that benefit them?
1 reply
0 recast
1 reaction
Boris Mann
@boris
We’re focusing on the compute part of the stack. There are many ways to easily publish to IPFS and we’d like to see compute added to all of them. “Full stack” == compute is the missing (decentralized) piece here. We have an early release of API endpoints this week — running from your desktop. 🧵1
1 reply
0 recast
2 reactions
Boris Mann
@boris
> Incentivize communities to run bundles of programs that benefit them? We see ourselves as sort of an L3. Our name for communities like this would be subnets: default settings, with functions & workflows incented per subnet. Points / cloud credits with settlement of choice per subnet. 🧵2
1 reply
0 recast
2 reactions
Boris Mann
@boris
Devs get incentivized to write functions and workflows. Functions that get actively run by the network flow credits back to authors. We’ll launch a default beta subnet connected to IPFS Mainnet. Thinking about Farnet for Farcaster / Frames functions. Anyone can run nodes with credits earned for compute. 🧵end
1 reply
0 recast
1 reaction
