In the month since the initial release of OpenRelay we’ve had a lot of developments.

We are working with a few different teams who are interested in using OpenRelay.xyz as an order book in different projects, and we’ve worked with a couple of individuals interested in running their own version of the OpenRelay service.

Our primary focus has been on stabilizing the OpenRelay as a service. We’ve made some changes to the way we interact with our pool of Ethereum nodes, and once we’re fully satisfied with our solution we’ll write a blog post about our approach to interacting with the blockchain. We still have a ways to go in sorting out some operational issues, but we’re happy with the progress we’ve made so far.

Additionally, we’ve made a preview release of OpenRelay.js, a JavaScript library for interacting with OpenRelay.xyz, as well as any other endpoint that implements the 0x Standard Relayer API. Note that the current implementation of both OpenRelay.xyz and accordingly the code in OpenRelay.js follow an earlier draft of the Standard Relayer Spec. We are working to bring OpenRelay into compliance with the finalized Standard Relayer Spec, at which point we will make a final release of OpenRelay.js. It is our intent that code written for OpenRelay.js now will continue to work with the standard API once the library is updated, but at this point we make no guarantees.

In the coming weeks adding support for testnet is a high priority. We are planning to add a testnet Ethereum node, and adjust the OpenRelay microservices to determine which Ethereum node to communicate with based on the exchange contract address of each order. The result is that the same API endpoint will handle orders for both mainnet and testnet.

If you have any feedback, chat with us on gitter, talk about the latest news on reddit, or file an issue on github.