Swingby node relies on the Ethereum, Bitcoin, and Binance-chain states to form a consensus and perform swaps. For this reason, your instance has to have multiple blockchain-specific processes running in parallel on the same instance. (Total 4 docker containers):
Geth(v1.10.1) or Binance Smart Chain node (v1.1.0-beta)
Due to the resource-heavy dependencies needed by the Swingby node, we recommend that you use an instance with equal or greater specs than below. If your node does not have enough resources available then it will not be able to stay in sync with the rest of the Swingby node in the network and will be dropped.
[Local Machine] (Required to install your node-installer telegram BOT)
MacbookPro or Linux (Ubuntu 20.04 LTS is recommended)
4 CPUs (Dedicated)
1.5TB Storage (SSD) for BTC-ETH bridge, 1.6 TB storage (SSD) for BTC-BSC bridge
A static IP address that is binding on your Server NIC
3. Staking SWINGBYs on timelock transaction
SWINGBY-BEP2 tokens (held in a cold wallet) staked for a minimum of 30 days with a total quantity that must be above 50,000 SWINGBY tokens.
The timelock transaction must have an "ed25519 pub key(called Node ID)+ETH address" description tag to verify that your node is staking and validated on the current network.
The Swingby node requires to use high I/O rate disk and enough spaces. all mounting path is under /var/swingby
Infrastructure directory path
BOT configure & Node configure path
Nginx configure & TLS certificate data path
After completing the bot setup procedure, the bot will automatically build some directories under /var/swingby and start downloading the required snapshots.
5. DNS subdomain configuration.
The Swingby node has an Nginx container which is for support to use HTTPS for your node endpoint. to enable a DNS subdomain with an alias to your server, basically, you have to add an 'A' record to your DNS record.
Example:: test1.swingby.network A 18.104.22.168 60
/setup_domain (This command is for setup your domain on your BOT chat)
/enable_domain (This command is for deploying Nginx with your DNS configure on your BOT chat)
In the last command process, An SSL certification will be generated through the Let's Encrypt automatically