Simple APIs for sending and receiving payments, and instructions for connecting your node to the testnet

Originally posted on Coil.com.

Today, I’m excited to announce the alpha release of the Interledger.rs node and Xpring Interledger testnet nodes. Interledger.rs aims to be the fastest and easiest to use implementation of Interledger and we’re looking forward to seeing what you build with it! This release includes simple APIs for sending and receiving payments, as well as instructions for connecting your node to the testnet.

For background on Interledger, take a look at Interledger: How to Connect All Blockchains and Value Networks.

Interledger.rs Node: What’s in the Box

Interledger.rs…


How I Learned to Stop Worrying and Love HTTP

Streaming payments mean that Interledger connectors need to process huge volumes of Interledger packets, but the current reference implementation is hard to run at scale. My hypothesis is that we should make the connector completely stateless using an HTTP-based bilateral communication protocol.

This post describes ongoing work and neither the design nor the protocol are settled. Comments and alternative suggestions are welcome! You can find a basic prototype of the proposed design implemented here.

Bilateral Communication in Interledger

Interledger.js uses a plugin architecture to abstract away different possible bilateral messaging protocols, but today all of the plugins are built on the Bilateral Transfer Protocol…


By Evan Schwartz and Vanessa Pestritto. Originally appeared on the Xpring blog.

Interledger was born out of a project to build a blockchain-agnostic smart contracts platform. A key challenge was neutrality: how could a decentralized app buy resources like storage and computing, without being tied to a specific blockchain? Across the internet, apps and services face a similar issue of how to directly monetize without relying on a single cryptocurrency, a proprietary network like Visa or PayPal, or a monolithic platform like Apple. Interledger was designed to answer the question:

What would a universal network for sending value, independent of…


The Protocol Stack for the Internet of Value

Layer 2 technologies such as Lightning and Plasma are said to “promise big strides in scalability, interoperability and functionality” for blockchains. However, most Layer 2 projects focus primarily on scalability and only occasionally mention interoperability. Why? This isn’t just a matter of timing or stage of development. This is actually how it should be, because Layer 2 is for scaling. Layer 3 is for interoperability.

Scaling and interoperability are complementary but separate concerns that are best addressed through different protocol layers. To make this case, I’ll give a bit of background on the purpose of layered protocol architectures and the…


By Evan Schwartz and Vanessa Pestritto

Interledger was born out of a project to build a blockchain-agnostic smart contracts platform. A key challenge was neutrality: how could a decentralized app buy resources like storage and computing, without being tied to a specific blockchain? Across the internet, apps and services face a similar issue of how to directly monetize without relying on a single cryptocurrency, a proprietary network like Visa or PayPal, or a monolithic platform like Apple. Interledger was designed to answer the question:

What would a universal network for sending value, independent of any company or currency, look like?


STREAM is the new TCP for Interledger. It makes building Interledger applications easier by splitting payments into packets, sending them over ILP, and automatically reassembling them for you. STREAM, or the Streaming Transport for the Realtime Exchange of Assets and Messages, is designed to be used whenever you want to send streaming micropayments or larger discrete payments. This tutorial will show you how to:

  • Establish a connection between a STREAM client and server
  • Send streaming micropayments or a larger payment over the connection
  • Send data over the connection (instead of over the internet 🤔)

If you want to learn more…


As the development of the Interledger Protocol (ILP) nears completion, I thought we should take a moment to remember some of the many core protocol features we’ve killed off along the way.

Photo by Ashim D’Silva on Unsplash

These were 12 promising features, and countless hours were spent perfecting them. But they were sacrificed for simplicity’s sake. Rest in peace, old friends.

Getting people to agree on any standard is notoriously difficult, so we have worked to make Interledger as simple as possible. We have often repeated the mantra that the core protocol would only be finished when there was nothing more to take out —…

Evan Schwartz

Software engineer, co-inventor of @Interledger

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store