OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Payments & Stablecoins

Bicycle

Bicycle is a Go microservice that accepts TON blockchain payments and sends withdrawals to TON wallets. It generates deposit addresses, accumulates funds in a hot wallet, and exposes these operations through a REST API. It supports TON coins and Jettons that meet its stated criteria, and communicates directly with a TON node over ADNL.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Bicycle — OpenViST project profile in Payments & Stablecoins.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Bicycle when you need to integrate TON deposits and withdrawals into a service and can operate the required node and wallet infrastructure.

Who it is for

  • Teams integrating TON payments into a service through a REST API.
  • Operators able to manage a TON node, HighloadV2 wallet, and hot- and cold-wallet flows.

Documented uses

  • Generate TON or Jetton deposit addresses for customers.
  • Send TON or Jetton withdrawals from the hot wallet to customer wallets.
  • Use reusable deposit addresses, withdrawal comments, and batched withdrawals.
  • Aggregate some funds at a cold wallet and request service withdrawals to cancel incorrect payments.
Before you choose

Requirements & limits

The project is open source under GPL-3.0.

  • A TON HighloadV2 wallet with the configured minimum TON balance, or an already deployed HighloadV2 wallet, is required.
  • The README calls for a TON node with a lite server on the same machine as the service; using an untrusted node requires proof checking to be enabled.
  • Jetton support is limited to tokens meeting the stated TEP-74, balance-change, and withdrawal-fee criteria.
  • Manual withdrawals from the hot wallet are prohibited by the project instructions and can cause a service error.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Prepare TON prerequisites and configuration for Bicycle

Prepare the TON wallet and node settings required before deploying the Bicycle payment service.

Before you start

  • A configured amount of TON at a HighloadV2 wallet address with its seed phrase, or an already deployed HighloadV2 wallet.
  • A TON node with a lite server on the same machine as the service, or an untrusted node configured with proof checking enabled; a network configuration URL is optional.
  • For Jetton use, tokens must conform to TEP-74, change wallet balances only through transfers, and have withdrawal fees within the service's internal setting.

Steps

  1. Ensure the HighloadV2 wallet meets the configured minimum TON requirement.

  2. Provide a TON node and lite server on the service machine; if using an untrusted node, set PROOF_CHECK_ENABLED=true and optionally specify NETWORK_CONFIG_URL.

  3. Prepare the lite server address and public key using the LITESERVER and LITESERVER_KEY configuration parameters.

  4. If processing Jettons, confirm each token meets the stated compatibility criteria.

Expected outcome

The documented wallet, node, lite-server, and optional Jetton prerequisites are prepared for the deployment stage.

Guide limitations

  • This guide covers prerequisites and configuration parameters, not service deployment or API execution.
  • Only Jettons meeting the stated criteria are supported.
  • Manual withdrawals directly from the hot wallet are prohibited and can cause a service error.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
10 October 2026
Original website title
gobicycle/bicycle · Official homepage title · retained in its source language
How we review sourcesSuggest a correction