Client v.6.0.0-alpha.8

Breaking Changes

• Removed RECEIVE_TRANSFER_FINISHED, RECEIVE_TRANSFER_STARTED, and RECEIVE_TRANSFER_FAILED events. Added the following more extensible events:

CONDITIONAL_TRANSFER_CREATED_EVENT
CONDITIONAL_TRANSFER_RECEIVED_EVENT
CONDITIONAL_TRANSFER_UNLOCKED_EVENT
CONDITIONAL_TRANSFER_FAILED_EVENT

Corresponding event payloads for these new events:

// under namespace EventPayloads
HashLockTransferCreated
LinkedTransferCreated
SignedTransferCreated
HashLockTransferReceived
LinkedTransferReceived
SignedTransferReceived
HashLockTransferUnlocked
LinkedTransferUnlocked
SignedTransferUnlocked
HashLockTransferFailed
LinkedTransferFailed
SignedTransferFailed

Under The Hood

• #898, #901 - Reworked deposits and withdrawals completely to make use of our generalized state channel framework and reduce special-case code.
• #934 - Switch from Nginx to HAProxy for better Websocket compatibility.
• #964 - Automatically install receiver app for SignedTransfers when sender installs. This allows much better event handling in cases where liveness is predictable.
• #959 - Allow injection of custom validation middleware into core protocol layer.
• #826 - Sets up infrastructure to be able to be backwards compatible with old channels that generate different commitments.
• #891 - Node DB optimizations all across the board.
• #916 - HUGE latency improvements in end-to-end transfers.
• #950 - Add Postgres option to @connext/store for non-UI based clients.
• #897 - Adjudicator layer revamp.
• #942 - Improve HTLC app for a specific use case (i.e. requires liveness).
• #895 - Meta is persisted in app instances in store.
• #325 - NATS authentication strategy implemented.

Client 6.0.0-alpha.4

Includes:

• cleaning up of client dependencies
• adding localhost to default client creations
• HASHLOCK_TRANSFER condition type will now immediately try to install on the receiver side and fail if the receiver is not online. This is necessary for Lightning interop.

Matches code at commit 6921ee255.

Client v6.0.0-alpha.3

Alpha Release

• Compatible with node source code/docker tag at commit 74def2a63

Client 6.0.0-alpha.0

6.0.0-alpha.0

Major Change!

We have made some major overhauls to the store. Moving away from the get / set API, we implemented a comprehensive store interface. This makes transfers faster, and is significantly more efficient for nodes.

Running the Release

This is an alpha release, so it should be run with a local hub. You can get the images here by searching for the tag 65e43751. For example, when pulling the node image, run:

docker pull connextproject/indra_node:65e43751

Indra v5.2.1 | Client v5.2.1

Features

• #886 - Node will reclaim pending async transfers when a client connects.
• #856 - New conditional transfer type HASHLOCK_TRANSFER! Makes Connext channels compatible with Lightning HTLCs.
• #890 - Eliminate some potential concurrency bugs.

Indra v5.1.1 | Client v5.1.1

New Features

• New conditional transfer type FAST_SIGNED_TRANSFER docs. Specify an Ethereum address as a signer to unlock a payment with a signed message!

Working on improving performance at all levels of the stack, so speed improvements should be noticeable!

Indra v5.1.0 | Client v5.1.0

indra-5.1.0

Deploy indra-5.1.0

Indra v5.0.2 | Client v5.0.2

New Features

• #873 - Added transfer sender to data received from RECEIVE_TRANSFER_FINISHED event. Added a type for the returned data, import ReceiveTransferEventData from package @connext/types.

Bugfixes

• #860 - Fixed issue where the private key generation was happening in a different way than it was supposed to. This is a breaking change for clients.
• #870 - Fix a hacky issue where the encrypted preimage for transfers was not being stored atomically. This is a breaking change for clients.

Indra v4.3.0 | Client v4.3.0

Logger overhaul

This release introduces a new client option! The client now accepts a logger option which must implement the ILogger interface:

interface ILogger {
  debug(msg: string): void
  info(msg: string): void
  warn(msg: string): void
  error(msg: string): void
}

Notice that console satisfies this interface on it's own, so you could pass that in as-is:

import { connect } from "@connext/client";
const client = await connect({ logger: console, ...otherOptions });

But this is the default behavior & is what you'll get if you omit the logger option entirely.

This option is useful if you're using eg winston for more powerful logging or LogDNA to send logs to a remote service for further processing.

Note that winston loggers also satisfy the ILogger interface by default so you can also pass those in as-is just like console.

Indra v4.2.0 | Client v4.2.0

Bugfixes

• Roll back @connext/crypto integration while we work out some kinks!
• #858 - Fixed issue where if pending async withdrawal reclamation failed, the client could not start up at all.