Maybe some of these smaller teams should unite, this may help produce better offerings which may lead to bigger funding. Market conditions also call for a pause in funding things and teams/products that aren’t vital/ produce 0 revenue. I don’t have any problems with Ecad and I appreciate what they’ve done.
Brother in Christ, it is the same story over and over and over again.
At some point we have to stop treating every independent team that falls out with Tezos funding as the villain by default.
Kolibri guys were the problem. Arri was the problem. ECAD is the problem. Public RPC operators are the problem. LIGO users were the problem when their language got deprecated. Indexers and app teams were the problem when upgrades broke things. Everyone is always unreasonable except the system that keeps producing the same outcome.
Of course ECAD should show what they built and what they were paid. I’m not against accountability. But that cuts both ways.
If the question is “has ECAD built successful infrastructure outside Tezos?” then the paired question is “has the funding body repeatedly funded ecosystem infrastructure in a way that produced durable, transferable, well-maintained public goods?”
Because the pattern we keep seeing is not durable stewardship... It is grant-funded public goods, rising maintenance burden, funding cuts, hard migrations, social blowups, then consolidation into the same small set of insiders.
Signatory may not be existential in the sense that Tezos halts tomorrow without ECAD but that is a low bar. The question is whether Tezos wants independent critical infrastructure teams, or whether every useful tool eventually gets starved, absorbed, deprecated, or replaced after the original team is burned out.
Other chains manage to fund wallets, SDKs, RPCs, explorers, signers, infra teams, grants, and ecosystem support without turning every maintenance negotiation into a morality play. So yes, ask ECAD for the work product and numbers. But also ask why Tezos keeps ending up in public knife fights with the teams that built useful things for it.
Fair ask on funding numbers. ECAD should publish the ledger if they want public support.
But the “what did they build?” part is not mysterious.
They created and maintained Taquito, the dominant Tezos JS/TS SDK. The npm packages still show hundreds of thousands of monthly downloads across Taquito core, RPC, local forging, Michelson encoding, utils, signer, and Ledger signer packages.
They built Signatory, the protocol-aware remote signer for Tezos operators using HSMs, Cloud KMS, TEEs, Ledger, policy enforcement, watermarks, and Prometheus monitoring. That is key-management infrastructure, not a toy app.
They operated public RPC infrastructure through ECAD Infra. Their shutdown post says the endpoints served roughly 54 million requests and 1.2 TB in the prior seven days.
They built node/baker Ansible tooling, Tezos monitoring/exporter tooling, Grafana datasource work, Taquito templates/boilerplates, lower-level Go/protocol utilities, and newer TezosX tooling.
So yes, ask for funds received. That is fair. But the work-product question has receipts. ECAD was responsible for SDKs, signing infrastructure, RPC infrastructure, operator tooling, monitoring, developer templates, and support surfaces that Tezos apps and operators actually used.
Cost aside, ECAD was one of the things Tezos could rely on 100% of the time. They were a shining star of consistent competency. Now they're "the devil."
Feh.