Maximus 🦒

XRAY/Graph is now live. Try: xray.app/xray/graph XRAY/Graph is an API marketplace and access layer for data, infrastructure, and compute services. Providers can expose APIs over HTTP or WebSocket, define access rules, track usage and revenue, and eventually monetize requests through account-based payments or x402. For consumers, XRAY/Graph provides one place to discover and access services through consistent endpoints instead of integrating separately with every provider. Free access is available where providers enable it, while paid services can be used through an XRAY account, and later through x402 for direct machine-to-machine payments. We are launching with one paid client already using the platform, and with our partnership with @CardanoKoios , which receives 30% of revenue from all paid requests routed through its service. This is the model we want to expand: infrastructure providers bring useful services, XRAY/Graph handles access and monetization, and revenue flows back to the providers. With today’s release, we are also resetting the public statistics from the previous version. The earlier deployment processed ~30 million requests, but XRAY/Graph is starting a new accounting period from zero so usage, revenue, and provider statistics reflect the released system from this point forward. For the initial release, some functionality remains intentionally disabled. Top-ups, withdrawals, x402 payments, and creation of new services are temporarily unavailable until the next announcement. We are currently rebuilding XRAY/App and waiting for the XRAY.ID NFT mint, which will become part of how services and identities are represented across the ecosystem. More details on XRAY.ID, payments, provider onboarding, and the next XRAY/Graph phase are coming soon. For now, the core is online. One graph. Multiple providers. Free and paid access. Programmable infrastructure. #Cardano #XRAY #API #x402

I still don’t fully understand the optimism around Midnight as a separate chain. The simpler question for me is: why not implement these capabilities at the Cardano protocol level? At its core, a blockchain is a set of rules governing how data is stored, validated, propagated, and agreed upon by nodes. One of its fundamental design tensions is the balance between decentralization and speed. The more independent participants that must coordinate and verify state, the harder it becomes to maximize throughput and minimize latency. Centralizing parts of the system can make coordination faster, but that usually comes with stronger trust assumptions and weaker fault tolerance. But this tradeoff does not have to be binary. A blockchain can evolve toward a hybrid architecture: keep decentralized consensus and settlement at the base, while moving selected workloads into specialized execution paths that operate under different performance assumptions. Leios is already an example of Cardano moving in this direction. Instead of simply centralizing the network to gain speed, it separates more transaction-processing work from the critical consensus path while keeping the result anchored to the same underlying security model. That same principle could be extended further. Privacy, selective disclosure, specialized execution environments, high-throughput workloads, and other advanced capabilities do not necessarily require an entirely separate blockchain. They could exist as modular domains, shards, execution layers, or protocol modules while still sharing Cardano’s settlement, consensus, security assumptions, governance, and asset layer. This is the architectural question that matters. It is not really whether Cardano can support these capabilities. The question is whether separating them into another blockchain creates enough additional value to justify the cost of another consensus domain, another token economy, another bridge surface, another governance system, and another place where liquidity, infrastructure, and developer attention can fragment. There are, of course, legitimate reasons to separate systems. Privacy-heavy computation may require different cryptography, state models, upgrade cycles, or performance characteristics. Isolation can reduce complexity in the base protocol and let specialized systems evolve independently. But these are engineering tradeoffs, not proof that a separate blockchain is fundamentally necessary. My instinct is that the more functionality Cardano can expose through a modular protocol architecture while preserving one coherent security and settlement layer, the stronger the overall network effect becomes. Instead of: Cardano → bridge → another chain → separate state → separate incentives the cleaner long-term model may be: Cardano → modular execution/privacy domains → shared settlement + security + governance And then there is the issue that may be even more important than architecture: developers. If Cardano is already one of the larger blockchain ecosystems by market capitalization and still struggles to attract enough developers, launching another ecosystem beside it means creating yet another infrastructure stack that must compete for the same scarce talent. Wallets, SDKs, tooling, explorers, integrations, infrastructure providers, documentation, liquidity, incentives, and developer mindshare all have to be recreated, duplicated, or split between ecosystems. This is why the tradeoff is not only technical. It is also economic and organizational. Do we concentrate effort on making one programmable ecosystem broader and more capable, or do we create another chain that has to rebuild much of the surrounding ecosystem from scratch? So the real question is not whether privacy deserves its own technology stack. It probably does. The question is whether it truly needs its own blockchain.