Wallet

SourcesFrom Pro

Wallet

Ethereum · 0x4344…cbaf · from 1,000 USDT

• Balance
• Movement
• incoming
• outgoing

This is how the node looks on the board. It has no inputs; on the right its values go to other nodes.

Like a bank statement that speaks up by itself: the node watches the balance of a wallet and tells you when something comes in or goes out.

Balance and movements of a wallet. Watches the balance of a wallet on Bitcoin, Ethereum, Base, Arbitrum, BNB Chain, Polygon or Solana, in the network’s coin or in USDT or USDC. When it changes, “incoming” or “outgoing” is true, from the amount under “From amount”. That way you get told about every movement of your own wallet, large transfers of a well-known wallet or an incoming payment. Bellchain only reads public data of the blockchain and needs no access to the wallet. Without a candle in the chain the alert usually arrives within 15 seconds after the network has confirmed the transfer (Bitcoin: with the next block), with a candle at its close. Example: incoming from 1,000 USDT on Ethereum to Telegram reports when a payment arrives.

What it looks like

• balance

Made-up values of a wallet on Ethereum over three weeks in hourly candles, with “From amount” 0.1 ETH. “Incoming” and “outgoing” are true at the first candle at which the new balance is certain, so at exactly one candle per movement. The node does not report the outflow of 0.05 ETH.

Settings

The settings appear on the right under “Properties” once you click the node on the board. Below each field you find the same explanation as here.

Network

Default: Bitcoin

The blockchain the balance is on. Base, Arbitrum, BNB Chain and Polygon use the same addresses as Ethereum (0x…): choose the network where you see the balance.

• Bitcoin (default): Addresses starting with bc1…, 1… or 3…; balance in BTC.
• Ethereum: Addresses starting with 0x…; ETH, USDT or USDC.
• Base: Layer 2 on Ethereum, addresses starting with 0x…; ETH or USDC.
• Arbitrum: Layer 2 on Ethereum, addresses starting with 0x…; ETH, USDT or USDC.
• BNB Chain: Addresses starting with 0x…; BNB, USDT or USDC.
• Polygon: Addresses starting with 0x…; POL, USDT or USDC.
• Solana: Addresses without 0x, 32 to 44 characters; SOL, USDT or USDC.

Address

Default: empty · any text, at most 100 characters, must be filled in before activating

The public address of the wallet, as shown for receiving. Never enter the recovery phrase or a private key: Bellchain does not need them and never asks for them.

Coin

Default: Network coin

Which balance the node watches: the network’s coin or one of the two big stablecoins.

• Network coin (default): BTC, ETH, BNB, POL or SOL, depending on the network.
• USDT: On Ethereum, Arbitrum, BNB Chain, Polygon and Solana.
• USDC: On all networks except Bitcoin.

From amount

Default: 0 · at least 0

Smaller movements trigger nothing, counted in the chosen coin. 0 reports every movement, including dust of a few cents that strangers send to many wallets.

Example

Reports when at least 1,000 USDT arrive at a wallet on Ethereum. The 5-minute candle sets the pace: Bellchain checks every 5 minutes.

How to connect the nodes:

1. Wallet (incoming) → Telegram (Trigger)

On the board it reads: Ethereum · 0x4344…cbaf · from 1,000 USDT

Chain as JSON

To try it, copy it and paste it in the editor under “Import”. Importing creates a new chain.

wallet.json

{
  "name": "Example: Wallet",
  "version": 1,
  "nodes": [
    { "id": "c1", "type": "core.candle", "position": { "x": 40, "y": 40 }, "settings": { "pair": "ETH/USDT", "timeframe": "5m" } },
    { "id": "w1", "type": "core.wallet", "position": { "x": 40, "y": 170 }, "settings": { "network": "ethereum", "address": "0x434436030387dbcfd27756b932568127f213cbaf", "asset": "usdt", "min": 1000 } },
    { "id": "t1", "type": "core.telegram", "position": { "x": 260, "y": 40 }, "settings": {} }
  ],
  "edges": [
    { "from": "w1.in", "to": "t1.in" }
  ]
}

Inputs and outputs

Only matching types connect: number series to number series (round pin), signal to signal (square), message to message (diamond).

Direction	Pin	Type	Note
Input	–	–	No inputs: the data comes straight from the source.
Output	Balance	Number series	–
Output	Movement	Number series	–
Output	incoming	Signal (true/false)	–
Output	outgoing	Signal (true/false)	–

Good to know

• In messages the values are called “Wallet BTC”, “Wallet BTC movement”.
• Warm-up with the default settings: 1 candle (this many extra candles are loaded by the replay before the value is reliable).
• Search also finds it under: wallet, address, balance, incoming, outgoing, transfer, payment, whale, on-chain, bitcoin, ethereum, solana, usdt, usdc.

Technical details

Balance after confirmed blocks: on Bitcoin from the outputs of the address, on EVM networks via Multicall3, on Solana the wallet’s account and its standard token accounts. Bellchain asks every 10 seconds (Bitcoin: the chain height every 10 seconds, the balance at every new block) while an active chain watches the wallet and stores every change, otherwise every 6 hours. Without a candle the chain computes right away at every new balance, on a timeline in minutes; at a candle the balance up to its close applies. There is no history before the first observation.

• Type in the chain: core.wallet · Version 1.0.0 · Category key src
• Settings in the chain: network (Network), address (Address), asset (Coin), min (From amount)
• Pins in the chain: Output balance, change, in, out
• Source: Balance from public blockchain data, loaded by the engine
• Reference tests in the manifest: 3 (with fixed price data: 500 candles of 1h)
• How a node is built