Build and deploy dApps without worrying about infrastructure. Scale to support millions of users. By @txpipe_tools.
Joined October 2022
- Tweets451
- Following303
- Followers2.2K
- Likes1.2K
Demeter retweeted
šÆWe are happy to announce that we have migrated our infrastructure from Maestro to @DemeterRun
Demeter retweeted
Demeter is an amazing resource to have on Cardano. Ready made development environments with all the tools to build your own custom stack. Great for beginning devs. Extremely affordable as well. Thank you @DemeterRun
Every Cardano API. Your choice.
ā Blockfrost, Kupo, Ogmios, UTxO RPC
ā Pay per request, $0 when idle
ā 99.9% SLA, measured publicly
Demeter retweeted
Blink Labs š¤ TxPipe
Scalable Cardano infrastructure ran by infrastructure experts with deep ecosystem roots. No project token pump and dumps or announcements of announcements, just uptime and open source APIs available on Cardano mainnet, preview and preprod.
Sign up today. š«”
Every Cardano API. Your choice.
ā Blockfrost, Kupo, Ogmios, UTxO RPC
ā Pay per request, $0 when idle
ā 99.9% SLA, measured publicly
Demeter retweeted
You can't vibe-code infrastructure with 99.9% uptime.
I know, I've tried.
Every Cardano API. Your choice.
ā Blockfrost, Kupo, Ogmios, UTxO RPC
ā Pay per request, $0 when idle
ā 99.9% SLA, measured publicly
Demeter retweeted
Building on Cardano?
Definitely check out @DemeterRun I've been using their services for years, and the team are extremely reputable and knowledgeable.
No paid promotion, just a post to appreciate teams providing a great consistent service, removing technical complexity when building on Cardano.
Every Cardano API. Your choice.
ā Blockfrost, Kupo, Ogmios, UTxO RPC
ā Pay per request, $0 when idle
ā 99.9% SLA, measured publicly
Demeter retweeted
Shoutout to @DemeterRun. Tracked down a mempool issue on their Ogmios fleet, fixed it fast, and it's been rock solid for 3 weeks. If you build on Cardano, use them. Thanks @santicarmuega
Demeter retweeted
š¢ Ogmios v7 is live on Demeter.run ā”
- Managed endpoints, zero ops
- WebSocket Ā· JSON-RPC
- Pay per request
- Mainnet, Preprod and Preview
- Multi-region Ā· 99.9% SLA
demeter.run
Demeter retweeted
Dolos v1.6 is out š
We've been working hard on supporting more of the Blockfrost API surface. Shoutout to the @blockfrost_io team, who have been contributing these endpoints directly to the Dolos codebase.
What's in it š§µ
Demeter retweeted
I'll stop the pinging, when I'm 67 š¶
To every DRep evaluating proposals and to the community at large: thank you for the support of @txpipe_tools proposals š
Now, back to building. See you in the changelogs.
Demeter retweeted
We've been talking to wallets, explorers, dapps. There's a common theme: we need a way to provide richer context to txs.
Knowing when a tx is a DEX swap, a prediction market bet or a loan from a lending protocol changes everything for UX, security, analytics and DevEx. š§µ
Demeter retweeted
HTTP/JSON wins at simplicity, but if you care about low-latency or high throughput, gRPC makes a huge difference.
- binary serialization (compact & fast)
- HTTP/2 request multiplexing
- schema-driven, less payload
Demeter retweeted
UTxO RPC is a gRPC API for Cardano nodes.
Because it's gRPC, you get something REST APIs can't easily do: server-side streaming.
You open ONE long-lived stream and the node pushes txs to you as they land on chain ā a live firehose of every tx. No polling. š§µ
Demeter retweeted
I wanted to learn more about Leios, so I vibe-coded this visualization TUI on top of Pallas.
It's not meant for operations, just a personal visual aid to understand the flow of the protocol. It was quite useful, but it also raised some new questions.
What you can see is an initiator node connected to the Musashi Dojo. The TUI is divided into two horizontal lanes:
- top lane: the Praos part, a sequence of ranking blocks (RBs)
- bottom lane: the Leios part, a sequence of endorser blocks (EBs)
The X-axis represents time, so you see blocks ordered from left to right, representing the sequence of the chain.
The interesting part to notice from the video: the heavy lifting of Leios (votes, tx processing, etc.) happens between RBs, making use of the idle time.
Being a vibe-coded PoC, the TUI uses some heuristics to work around much of the complexity and the current protocol gaps. For example:
- the link between RBs and EBs is estimated using slot proximity
- the votes are just a counter, and the denominator is the peak number of voters seen so far
One question that popped up and I'm still looking into:
the idle time doesn't seem to be enough to observe all the EB votes and download all the txs. This is probably related to data diffusion; maybe client prioritization on the responder side; maybe just bad performance on my code. š¤·
