XXXsatoshi pfp

XXXsatoshi

@xxxsatoshi

66 Following
204 Followers


XXXsatoshi pfp
XXXsatoshi
@xxxsatoshi
I'm sorry this was your experience and keen to make it right. Our QoS has also improved dramatically in recent times as we approach mainnet. If you're interested in testing things out again, would love to
0 reply
0 recast
0 reaction

XXXsatoshi pfp
XXXsatoshi
@xxxsatoshi
"The best example is that you can use several vendors plus your own node in a round robin load balancing" Absolutely, lots of projects do this but it's time-consuming and depends on endpoints that are often unreliable. I would love to show you what we're building at Lava which solves this - modular, p2p RPC :)
1 reply
0 recast
0 reaction

XXXsatoshi pfp
XXXsatoshi
@xxxsatoshi
Yes, JSON-RPC is a standard. But the services through which this is accessed are not i.e. you can run your own node or you can use a centralized provider (Alchemy) which requires a contract for production-grade service, or a decentralized service like Pocket but even this still requires permissioned access via gateway
1 reply
0 recast
0 reaction

XXXsatoshi pfp
XXXsatoshi
@xxxsatoshi
The only truly permissionless RPC service is Lava Network, which focuses more on modularity i.e. anyone can permissionlessly add a new chain or API to be served by the decentralized network of providers on Lava. This essentially makes Lava a dynamic marketplace for blockchain RPC and APIs that can quickly scale
1 reply
0 recast
1 reaction

XXXsatoshi pfp
XXXsatoshi
@xxxsatoshi
Similarly, these providers do create vendor lock-in since 1. developers integrate their SDK which makes it difficult to switch and 2. developers commit to a contract with each provider and there is some stickiness and "obligation" to use that provider, even if their API options are limited
2 replies
0 recast
1 reaction

XXXsatoshi pfp
XXXsatoshi
@xxxsatoshi
Not to drag up this old convo, but thought it was interesting and think you're slightly confused here. RPC providers like Alchemy, Infura, even Pocket are centralized (to varying degrees). (Permissioned might be a better word - Pocket for example still requires sign-up and access via a centralized gateway.)
1 reply
0 recast
1 reaction

XXXsatoshi pfp
XXXsatoshi
@xxxsatoshi
here to shill points before touching grass this weekend
0 reply
0 recast
1 reaction

Dan Romero pfp
Dan Romero
@dwr.eth
Pleased to announce that we're working with Coinbase Wallet to onboard people to Farcaster. The program will run for the next few weeks.
27 replies
79 recasts
353 reactions

XXXsatoshi pfp
XXXsatoshi
@xxxsatoshi
we're big fans of eigenlayer and their approach with restaking is innovative and different to how Lava is approaching things (we're an appchain and bootstrapping the node set with native incentives). But mainnet is coming Q1 and if you're interested in this corner of middleware innovation, happy to hear feedback :)
0 reply
0 recast
1 reaction

XXXsatoshi pfp
XXXsatoshi
@xxxsatoshi
So what we're building is a holistic economy for any type of data access, on any chain. And the protocol directly scores and rewards providers across QoS - latency, uptime and accuracy. With other innovations like dual-caching and pairing optimizations, we've seen 3x in response times
1 reply
0 recast
0 reaction

XXXsatoshi pfp
XXXsatoshi
@xxxsatoshi
Not only can any API be added, but specs can be replicated across chains, meaning Lava offers RPC & indexing with chain abstraction. There's no need for a new RPC endpoint for every new rollup - you simply use the Lava SDK and can make calls to multiple chains with one credential.
1 reply
0 recast
0 reaction

XXXsatoshi pfp
XXXsatoshi
@xxxsatoshi
This creates an economy for permisionless innovation at the node level. Anyone can write a spec, add it to the protocol, and the network will serve it to meet demand for data. e.g. we're currently integrating with Subsquid to bring subgraphs and indexing to Lava
1 reply
0 recast
0 reaction

XXXsatoshi pfp
XXXsatoshi
@xxxsatoshi
There's 3 main components to Lava: - the network of node operators that take on different services - the services, which are defined and added as JSON-files called "specs" e.g. Ethereum RPC spec - the protocol which pairs consumers to providers and incentivizes providers to offer high quality service
1 reply
0 recast
0 reaction

XXXsatoshi pfp
XXXsatoshi
@xxxsatoshi
With eigenlayer all the rage and strong interest in AVS, thought I'd share a little about the similar work we're building at Lava. 🧵 Lava is a protocol which coordinates node operators to provide services, primarily around blockchain data access. The first service we offer is RPC but soon expanding to subgraphs
1 reply
0 recast
1 reaction

XXXsatoshi pfp
XXXsatoshi
@xxxsatoshi
we just launched our mainnet roadmap + product updates for our chain-agnotic blockchain RPC & API protocol - p2p SDK for fast RPC & indexing from the browser - make calls to multiple chains with one credential - integrations with ethers/js, viem etc. - caching with 3x reduced response latency lavanet.xyz/roadmap
0 reply
0 recast
0 reaction

Yair Cleper pfp
Yair Cleper
@cleper
As we move closer to mainnet, it’s clear that RPC is only the tip of the iceberg. Devs today, across hundreds of rollups & scaling solutions, need data and APIs for all sorts of use cases. Lava Network calls it “Specs”- support a new chain, define, propose and add. Like Lego for APIs. docs.lavanet.xyz/spec
0 reply
1 recast
1 reaction

XXXsatoshi pfp
XXXsatoshi
@xxxsatoshi
+1
0 reply
0 recast
0 reaction

XXXsatoshi pfp
XXXsatoshi
@xxxsatoshi
nicely written, loved “fossilized rings in a merkle tree that tells about the seasons of yesteryear” concept of blockchains are our shared history recorded on an immutable ledger remains a powerful one
0 reply
0 recast
1 reaction

XXXsatoshi pfp
XXXsatoshi
@xxxsatoshi
also waiting for this
0 reply
1 recast
0 reaction

XXXsatoshi pfp
XXXsatoshi
@xxxsatoshi
I come back to this article regularly by @js, đź‘Ź https://stark.mirror.xyz/n2UpRqwdf7yjuiPKVICPpGoUNeDhlWxGqjulrlpyYi0
0 reply
0 recast
3 reactions