Fine-tuning
SMB + copychain configurations
This tool uses the SMB configuration, except for the entries in [[routing.mint_config_list]]
and certain parts of the [bot]
section, as these are precisely what the tool is designed to copy.
Original SMB configuration file
Values in the original SMB configuration under [routing]
are ignored by copychain
, since this is exactly what the tool is designed to copy. A few notes:
process_delay
: set its value in thecopychain
configuration (see process_delaylookup_table_accounts
: copied by this tool but can be extended with thecopychain
configuration (see default_lookup_tables)
Some entries in [bot]
section are also ignored:
merge_mints
: alwaystrue
compute_unit_limit
: copied by this tool
You can still use memo
to tag your transactions, and it's highly recommended to set skip_ata_creation = true
.
Each session will then use your own SMB configuration for sending transactions.
The first step is to decide whether you want to copy and send with Jito, Spam, or both.
Simply enable them in your SMB config (enabled = true
under their respective sections) and ensure their configuration entries are valid, specially URLs.
Jito-Related Entries in Your SMB Config
For Jito, this tool does not copy and uses the following entries from your original SMB configuration file:
enabled: whether Jito is enabled for copying.
tip_config: if you want to copy Jito Tips, see jito_tip.
no_failure_mode: you can, for example, copy a Spam wallet but send using Jito with
no_failure_mode = false
.
Spam-Related Entries in Your SMB Config
For Spam, this tool does not copy and uses the following entries from your original SMB configuration file:
enabled: whether Spam is enabled for copying.
compute_unit_price: if you want to copy compute unit prices, see spam_compute_unit_price.
sending_venders
is fully supported and works quite the same as Jito. If you want to copy Vendors Tips and fees, see vendors_tip and vendors_compute_unit_price.
Last updated