Sequentia

Downloads

The full node and the Android wallet for the Sequentia testnet. Sequentia is a Bitcoin sidechain for asset tokenization and disintermediated exchanges: every block commits to a Bitcoin testnet4 header, addresses are transparent by default, and fees are payable in any accepted asset.

Testnet: coins and assets have no value

Sequentia Core

version 25.2.7

The full node and its desktop wallet. It checks every block for itself, holds BTC and every Sequentia asset side by side, and is the software a block producer runs.

Linuxx86-64, tarball Windows64-bit installer
Install and update

Install: on Linux, extract the tarball and run bin/sequentia-qt. On Windows, run the installer, then launch Sequentia Core. It connects to the testnet on its own.

Update: install the newer release the same way. The wallet and the chain data stay where they are.

Files: sequentia-core-25.2.7-linux-x86_64.tar.gz, sequentia-core-25.2.7-win64-setup.exe

  • Wallet: send, receive and issue assets; the Sequence token (tSEQ) is one asset among them.
  • Staking tab: committee schedule, stake weights and staking-output tools.
  • Anchor watching: follows Bitcoin testnet4 and reorgs when it does.
  • Any-asset fees: pay a fee in whichever asset a producer accepts.

Ambra for Android

version 0.17.29

A self-custody Android wallet for Bitcoin testnet4 and Sequentia, from one recovery phrase.

Androidarm64 and x86-64, APK
Install and update

Install: allow “install unknown apps” for your browser, then open the .apk.

Update: open the newer .apk the same way. It installs over the old one and keeps the wallet.

Source on GitHub

File: ambra-0.17.29.apk

  • Both chains: BTC beside every Sequentia asset, on one shared tb1 address.
  • Total first: one total in your reference currency, every asset an equal row.
  • Send and receive: fees in any accepted asset, opt-in confidential addresses, and a waiting payment sped up on its own.
  • Issue and stake: create your own assets, and stake the Sequence token (tSEQ).
  • App lock: fingerprint or device PIN.
Check your download Every release file is listed in one checksum list, signed by the release key.
  1. Download SHA256SUMS, its signature SHA256SUMS.asc and the release signing key into the folder that holds your download.
  2. Import the key and check its fingerprint reads B4F5 7796 7E32 25D5 8FF6 3DFC 5974 FD59 E609 F11F, the same as in the release publisher's README.
    gpg --import sequentia-release-signing-key.asc
  3. Check the signature; it must say Good signature.
    gpg --verify SHA256SUMS.asc SHA256SUMS
  4. Check your file; it must say OK.
    sha256sum --ignore-missing -c SHA256SUMS
    On a Mac, use shasum -a 256 --ignore-missing -c SHA256SUMS. On Windows, run certutil -hashfile with the file's name and SHA256, and compare the result with that file's line in SHA256SUMS; Gpg4win provides gpg for steps 2 and 3.