The best developer experience is not “learn my world.” It is “use what you already know.”
ZooBC has its own logic, its own primitives, its own rules. That does not mean developers should have to throw away their tools. If we can lower the barrier without lying, we should.
This week we put the eth-rpc-adapter into real use on the live testnet.
The adapter translates a meaningful subset of Ethereum JSON-RPC methods into ZooBC API calls. It does not pretend ZooBC is Ethereum. It provides a compatibility surface so existing tools can talk to ZooBC in familiar language.
That means things like:
eth_blockNumbermaps to ZooBC chain height.eth_getBalancequeries ZooBC account state.eth_sendRawTransactionaccepts Ethereum-signed transactions and wraps them into ZooBC submission flow.- Receipts map into an Ethereum-like receipt structure where it makes sense, including confirmation state.
Address translation is not hand-wavy. ZooBC already supports multi-chain address derivation paths. The adapter bridges 0x-prefixed Ethereum addresses to ZooBC’s internal account representation in a deterministic way, using the same cryptographic foundations we already built for the wallet.
Then we did the practical test that matters: MetaMask connected to ZooBC through the adapter. It displayed a balance. It sent a transaction. It confirmed. No modifications to MetaMask. No “special plugin.” Just standard tooling talking to a protocol that is honest about what it supports.
We also tested the btc-rpc-adapter in the same spirit: not to compete with Bitcoin, but to let Bitcoin-style tooling query ZooBC where the mapping is legitimate.
Now the important part: compatibility has limits, and we do not hide them.
ZooBC does not have an EVM. There is no smart contract VM. There is no gas model in the Ethereum sense. There are no uncle blocks. Many Ethereum methods simply do not make sense here. In those cases, the adapter returns explicit errors rather than inventing fake responses. A compatibility layer that lies is worse than no compatibility layer, because it teaches developers the wrong assumptions and guarantees broken apps later.
The philosophical tension is real: when you speak another ecosystem’s language, you inherit some of its mental models. The job of the adapter is to translate without corrupting. Provide on-ramps without pretending.
The point of this week is not to chase Ethereum. The point is to reduce friction. If ZooBC’s primitives are strong, a developer who already knows ethers.js should be able to build in minutes, not weeks.
That is what an ecosystem feels like when you stop demanding that everyone start from zero.
