TLDR: The ACES SDK for ARK interoperability will be available in six languages: Python, Go, C#, Java, PHP, and JavaScript. Our first Encoded-Listener implementation in the new framework focuses on Bitcoin and ARK and you will see the APIs released in this segment of the project.

The ACES roadmap includes several major milestones which accomplish progressive themes. In this blog post I discuss what is going to be delivered in Milestone One.

At the end of Milestone One, developers wanting to integrate other blockchains to the ACES platform will have the API specifications, developer documentation, and sample implementations for Encoded Listeners and Marketplace Services. The ACES SDK will be available in six languages: Python, Go, C#, Java, PHP, and JavaScript. This will enable outside developers to start working on new implementations for other blockchains independently. At this point, the ACES team and the community can start reaching out to target blockchain projects about integration partnerships and begin facilitating implementations.

There are six major releases during this milestone:

Publish Service API Specification

Publish Listener API Specification

Deploy Encoded Listener Framework developer documentation website

Deploy Service Framework developer documentation website

Deploy demo Ark Listener node instance

Deploy demo Bitcoin Listener node instance

But how do these six release fit in to the bigger picture? Well, take a look at this bird’s-eye-view of an ACES setup, from blockchain to market, and all the components that go into it:

Milestone One releases functionality for the Encoded Listener APIs, Service API as well as demos for the ARK Listener node instance and Bitcoin Listener node instance. In the chart above, you’ll notice two boxes for Encoded Listener API. This is because each blockchain has its own Encoded Listener, which allows for two-way services like Bitcoin to ARK and ARK to Bitcoin. Our first Encoded-Listener implementation in the new framework focuses on Bitcoin and ARK and you will see the APIs released in this segment of the project.

In addition to the major releases of Milestone One, you can see a number of additional components. I’ll get into the details of those components in a later post, and you’ll get a deeper understanding of how ACES and ARK are integrating permission-less interoperability with an easy to use service marketplace.