Skip to content


Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


This library handles a bidirectionnal payment channel based on Autonomous Agents It allows free, instant and confirmation-free offchain transactions between two parties. Example of use cases: pay-per-call API, pay-per-time streaming...

How does it work?

The library can either be included in a Node.js project or as a stand-alone Node.js program controlled with Remote-Procedure-Call (RPC). Both parties willing to transact have to use the library. The library runs an headless-wallet that has to be funded prior to operation.

The communication between peers can be handled by the library, in this case two choices are available:

  • Encrypted chat: virtually no setup but has some latency, is not adapted for consequent volume of data and is hub-dependent.
  • HTTPS: a party that wants to receive payment has to setup an Nginx proxy but the communication is direct, very fast and the application can be infinitely scalable (see High Availability node)

The communication can be external, all you need is a mean to transfer a payment package in JSON. The payment package is obtained with createPaymentPackage function and can be verified by receveir with verifyPaymentPackage.

Basic example

One peer initiates the creation with:

channels.createNewChannel(peer, initial_amount, options, function(error, aa_address, unit){


peer is an url or a pairing address, aa_address is returned by the function and is to be saved as it will used to identify channel for further operation. Transactions can begin immediately if peer accepts unconfirmed payments or after confirmation by the network

One peer wanting to send an offchain payment uses this function:

channels.sendMessageAndPay(aa_address, message_to_peer, amount, function(error, response){
	if (error)
		return console.log(error);
		return console.log(response);

aa_address is the address of the channel provided during its creation, message_to_peer is anything that can be parsed in JSON (string, number or object) and that you want to transmit to your peer, amount is the amount of your payment and function is a callback that will be returned with error or response from your peer.

You can set a function to be executed when you receive an offchain payment:

channels.setCallBackForPaymentReceived(function(amount, asset, message, peer_address, handle){
	if (message == "thanks me")
		return handle(null, "Thank you " + peer_address + " I received you payment of " + amount + " " + asset);
	else if (message == "send me an error")
		return handle("this is an error");

The response can be a number, a string or an object, and will be forwarded to the payer.

The channel can be closed an anytime by one of the party with:

channels.close(aa_address, function(error){
	if (error)

After confirmation by peer or a timeout, you headless wallet will receive a payment calculated as follow: amount received = total amount deposited by you to the channel - total amount paid to your peer + total payment received from your peer

All functions and events available are documented there:


Depending on your needs, different configurations are possible.

Vendor configuration

Vendor configuration decision tree

Client configuration

Client configuration decision tree

Include module in your node.js project
  • Add the package to your project: npm install --save

  • Require the module at the beginning of your code. const channels = require('aa-channels-lib')

For events you need also const eventBus = require('ocore/event_bus.js')

All library functions are available as property, example:

channels.setAutoRefill("7FLNK5AIWSYU2TVEKRW4CHCQUAKOYGWG",122000, 300000, function(error){
	if (error)

All events can be subscribed with eventBus.on(event,function(){}), example:

eventBus.on("channel_created_by_peer", function(peer_address, aa_address){ 
	console.log("a peer created a channel, aa address: " + aa_address + ", peer address: " + peer_address)
Run as RPC server
  • Install Node.js > version 6
  • clone the library git clone
  • Run Rpcify cd aa-channels-lib node rpcify.js

By default port 6333 is accessible through HTTP or websocket, websocket is mandatory if you want to receive events. Commands be send in JSON by POST method in http or websocket message, example: curl --data '{"jsonrpc":"2.0", "id":1, "method":"setAutoRefill", "params":["7FLNK5AIWSYU2TVEKRW4CHCQUAKOYGWG",122000, 300000]}'

method is the name of the function you want to use, params is an array containing parameters you want to pass.

All functions and events are available (except setCallBackForPaymentReceived function).

Learn more on:

Integrated communication
  • Set in enabledReceivers array as below in your conf.js file as below:
exports.enabledReceivers = ['http','obyte-messenger'];
  • For HTTP, configure port:
exports.httpDefaultPort = 6800;
External communication
  • Leave enabledReceivers array empty in your conf.js file as below:
exports.enabledReceivers = [];

Create channel with createNewChannel using peer's payment address as first parameter, obtain payment packages with createPaymentPackage and verify them with verifyPaymentPackage.

High Avaibility mode

A node only destinated to receive payment can run in high-availability mode. In this case, the front service that handles the requests from clients is separated from a background service that runs the headless wallet. Several front services can run in parallel to serve clients even when the background goes down for some time (like for being updated). That greatly helps the scalability of your business.

The exact setup depends of you need but you will likely use:

  • a load balancer that will redirect https requests to different front service instances.
  • an external MySQL database to which front app and background app can connect to.

Check specific documentation there:

Web dashboard A local web dashboard can be enabled to check the states of all channels
  • Port configuration:
exports.webServerPort = 8080;

web dashboard


General purpose library for payment channels







No releases published


No packages published