There is two bridges for Binance, first one bridges Talleo’s own chain with Binance Smart Chain and the another bridge connects wrapped Talleo tokens on Binance Smart Chain (BSC) and Binance Chain (BBC).

Talleo ↔ Binance Smart Chain

TLO-BSC bridge works on same principle as TLO-ETH bridge, it embeds BSC address in payment ID field of Talleo transaction. When converting back, Talleo address is Base-58 decoded in contract call parameters.

Binance Smart Chain ↔ Binance Chain

BSC-BBC bridge uses TokenHub system contract, which allows using bridge website for conversion from Binance Smart Chain (BSC) to Binance Chain (BBC), and Binance Chain wallet extension for conversion back from BBC to BSC. BBC address is decoded in contract call patameters using Bech32 which is also used by Bitcoin segwit addresses.

Binance Chain ↔ Binance DEX

Binance Chain can be used for trading tokens on Binance DEX. The listing fee is 1000 BNB on both mainnet and testnet. Listing request is either approved or rejected by community members after the listing request is published.

!/bin/sh
curl -s -X POST http://127.0.0.1:33777/json_rpc -H 'Content-Type: application/json-rpc' -d '{"jsonrpc": "2.0", "method": "getAddresses", "password": "password", "params": {}, "id": "1"}' | jq '.result.addresses | .[]' | xargs -I ADDR curl -s -X POST http://127.0.0.1:33777/json_rpc -H 'Content-Type: application/json-rpc' -d '{"jsonrpc": "2.0", "method": "sendFusionTransaction", "password": "password", "params": {"addresses": ["ADDR"], "destinationAddress": "ADDR", "threshold" : 100000000, "anonymity": 0}, "id": "1"}'

This shell script gets list of subwallet addresses from wallet daemon and runs wallet optimization once for every subwallet. In two places the second "password" after : must be replaced with the real password, for example "password": "my_secret_password". If using custom port, replace 33777 with correct port in both places.

*/5 * * * * /root/optimize.sh > /dev/null 2>&1

If you save the script on top of the post as /root/optimize.sh and add above line in /root/crontab, and run crontab /root/crontab the script will be run every 5 minutes. All output from script will be discarded. 5 minute interval should be enough to optimize all the subwallets even if they are used for mining.

The core logic of the bridge is coded in convertFrom() and convertTo() functions of the contract.

convertFrom() is called from the bridge when it receives transaction to the TLO wallet with payment ID. Payment ID is decoded and used as destination ETH address. The decoding uses simple 6-bit table mapping 0-9, a-f and A-F, so checksum of the ETH address is preserved. The bridge will use owner address to pay the gas for the transaction.

convertTo() can be called from any ETH address with wTLO balance to convert back to TLO, it will require base58 decoded version of the TLO address as all contract function parameters are encoded in hexadecimal. Currently minimum convertible amount is 1.00 TLO and the token amount is subtracted by TLO network fee.

If other coins want to use the same contract, they must replace convertFrom() function with transfer() function using dedicated ETH address as substitute for the owner address of the contract. There is no 1-to-1 alternative for convertTo() function as it would require new contract method and event for each third-party coin. Because normal token transfer can’t specify metadata, the only viable solution is using decentralized exchange to swap wTLO to own wrapped token and then using function from that contract to convert back to own coin, or using dedicated swap contract holding balances in both tokens as intermediate.