Dor
@dor
1/2 Many builders here could relate that building applications that rely on real-time, on-chain data is resource-intensive and requires specialist skills. And as chains and clients focus on “writes” (throughput, scalability), rich and efficient “reads” will become even harder. Today we launch sim.io to change that. (read more: https://blog.smlxl.io/sim-a-canvas-for-your-ideas-aa80d20e6fa8) sim replaces and augments node providers, indexers, ETL pipelines, API gateways and cloud providers. Use our fully hosted solution or stream to your own infra. Perfect for builders who value flexibility and control. What can you do with sim? A LOT! - Instantly deploy rich APIs and data pipelines for your dApp - Analyze and instrument DeFi protocols at scale - Monitor and respond to on-chain events across networks (telegram bots, x-chain messaging, etc.) All without months of backend work and juggling multiple vendors.
2 replies
4 recasts
11 reactions
🦒
@srijan.eth
congrats on the launch, p cool stuff! checkout this @hbrbssa.eth
1 reply
0 recast
0 reaction
redbeard
@hbrbssa.eth
this is pretty cool indeed, long way from evm.codes!
1 reply
0 recast
1 reaction
Dor
@dor
long road indeed, but sim is the reason we built evm.codes -- early on we decided/knew we have to build our own EVM, the majority of the team didn't come from blockchains but previously worked on Databases, game-engines, rideshare matching/optimizations, infra etc... In our experience the yellow paper was not great at quickly onboarding folks or be used as a daily reference. So initially we had an internal Notion doc summarizing the yellow paper and the EVM and we used that internally, we ended up sharing it with few other people not from the company who we knew and were onboarding to the ecosystem and they all thought it was really helpful for them. So we hired a frontend contractor, gave them the notion page and rough ideas on the design and that's evm.codes.
0 reply
0 recast
1 reaction
