Overview

Euphrates 0.5.0 is the 5th version of a Babylon devnet that supports integration with other consumers. On top of Euphrates 0.2.0 where consumers can receive registration messages of finality providers and BTC delegations, Euphrates 0.3.0 allows finality providers to submit finality signatures to the consumer, Euphrates 0.4.0 allows the consumer to tally its blocks and check their finalisation status, and Euphrates 0.5.0 supports finality provider slashing and slashing propagation to Babylon and other Consumers.

This page provides a guide for PoS systems to integrate with Euphrates 0.5.0. The integration allows a Consumer system to get economic security from BTC stake.

Euphrates 0.5.0 is currently in a highly experimental phase, and unexpected issues may arise. We welcome any feedback on the integration process and this document.

System components. The integration involves three blockchains:

• A Bitcoin blockchain. In this specific case, we’re using Bitcoin Signet.
• A Babylon blockchain. This is the Euphrates devnet, presented below.
• A Consumer system. This is the system that we aim to integrate with Babylon.

User stories. The integration provides the following user stories for consumer systems:

1. Babylon receives registrations of consumer systems, consumer finality providers, and BTC delegations (shipped in Euphrates v0.1.0).
2. Babylon propagates consumer finality providers and BTC delegations to consumer systems (shipped in Euphrates v0.2.0).
3. Consumer finality providers submit finality signatures to their consumer systems (shipped in Euphrates v0.3.0).
4. Consumer systems tally blocks and determine their finalisation status (shipped in Euphrates v0.4.0).
5. Finality providers who double sign blocks are slashed, their associated slashing transactions are executed, and delegations are unbonded (shipped in Euphrates v0.5.0, current version).

Consumer system requirements

The consumer system integrating with Euphrates 0.5.0 needs to support IBC and CosmWasm smart contracts. This is because Babylon sends information about finality providers and BTC delegations as IBC packets. The consumer system needs to deploy CosmWasm smart contracts to process these IBC packets, and then store the finality providers and BTC delegations information.

The Babylon team is developing a specialised relayer to support consumer systems without IBC, and is developing consumer side software for various types of consumer systems.

Prerequisites