Understanding output

Session start

As soon as a session starts, you’ll see the following:

[...]
[INFO ] ✨ Starting 1 session (group: 0) with base mints ["EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v"]:
[INFO ]    copied wallet: xxx
[INFO ]    session: 48117a58, sig: 5jhR...a3Xj (SMBV26), mints:
[INFO ]       Dz9mQ9NzkBcCsuGPFJ3r1bS4wgqKMHBPiVuniW8Mbonk (4 pools)
[INFO ]       4dmQFkCM1WiUhC75UndLkmMtWj78fQJUvfc4xpMLpump (2 pools)
[INFO ] [0] smb-onchain running with PID 2678316 and workspace '/tmp/copychain_20250609190922_0'
[...]

The tool detected an SMB transaction from copy wallet xxx with 1 session (ID 48117a58) and started a sessions group with ID 0. In this trigger transaction, there were 2 mints—meaning the copied user has 2 [[routing.mint_config_list]] entries in their SMB configuration with merge_mints = true:

  • Dz9mQ9NzkBcCsuGPFJ3r1bS4wgqKMHBPiVuniW8Mbonk

  • 4dmQFkCM1WiUhC75UndLkmMtWj78fQJUvfc4xpMLpump

Finally, the solscan link for the trigger transaction is printed.

You can find the generated smb-onchain configuration in the session workspace, as shown in the last line of the example: /tmp/copychain_2025... .

An instance of smb-onchain is now running.

A "group" refers to one or multiple sessions. For Spam, it will always be a single session (i.e. transaction). For Jito, the number of sessions depends on the strategy used by the copied wallet.

Live statistics

At each interval, the Live Statistics table is displayed:

It includes the following information:

  • Session [group]: All currently running (or monitored) sessions.

    • Prefixed with (J) ,(S) , or (X) to indicate a Jiton, Spam or Spam-To-Jito session.

    • Suffixed with [<group id>] , so that multiple sessions in a same Jito bundle share the same group.

  • Duration: How long each session has been running.

  • Successful Arbs (mean | norm.): Number of profitable arbitrage transactions out of the total sent transactions (including failed ones), followed by two numbers:

    • The first value is the average number of transactions per block. A value of 1.0 means the session is landing one transaction per block on average.

    • The second value is the normalized mean of transactions per block. A perfect value of 1.0 means at least one transaction lands every block.

    • As a general guideline, a mean of 1.0 and a normalized mean of 0.8 can be considered a good score. Tweaking your process_delay setting will impact both of these values.

  • PnL: Profit and Loss for each session.

You can compare with your own statistics in the corresponding columns (the ...vs ).

Landed transactions

Every landed transaction (profitable or not) will be logged by this tool. You’ll also see the landed transactions from the sessions you are currently copying.

Your own transactions will be logged like this:

... [2f89a902] ✅ +0.000130211 slot 345920013 https://solscan/io/tx/1ab23...Gd1cPqHH

While copied transactions will appear like this:

... [2f89a902] +0.000048278 slot 345928120 https://solscan/io/tx/5qKo8...NX8PMQNj

In this example, for session ID 2f89a902, you landed a profitable transaction and earned a total of 0.000130211 SOL + WSOL combined. This amount is calculated by summing all SOL and WSOL inflows and outflows in the transaction where you are the fees payer (whose signature is shown at the end of the log line).

If the base mint is not WSOL, it will be approximately converted to WSOL for profit calculation.

Session timeout

If a session didn't receive any update for a specific duration (see timeout), the whole group will simply exit with the following message:

[INFO ] [0] ⌛ timeout

The associated smb-onchain process is now stopped.

PreviousWorkspaceNextFAQ

Last updated