Contract Addresses Boba/Avalanche
A collection of links and addresses to get started on Boba-Avalanche
There is a Boba Avalanche testnet fountain for
BOBA. Authentication is via Twitter - please go to the gateway and connect your MetaMask wallet to the Boba Avalanche Testnet L2. In gateway > wallet, you will see the
Developer Twitter/Turing test token fountain. This system uses Turing hybrid compute to interact with Twitter.
The standard bridges for
BOBAare active, so you can can both bridge and exit
BOBAfrom Avalanche Testnet to Boba Avalanche Testnet and back.
If you have unusual
getLogsneeds, especially calls from
0 to latest, the main RPC will block you, since this is how most DoS attacks work. In those cases, we encourage you to run your own RPC endpoint on your own replica of Bobaopera. We have prepared Docker images for you, so this should only take a few minutes. To access these images:
$ docker compose -f docker-compose-bobafuji.yml pull
$ docker compose -f docker-compose-bobafuji.yml up
The DTL will first sync with the chain. During the sync, you will see the DTL and Replica gradually catch up with the Boba L2. This can take several minutes to several hours, depending on which chain you are replicating.
For secondary addresses, such as L2 Tokens and Messengers, please see the Boba Avalanche Testnet address registration dump.
To access these images:
$ docker compose -f docker-compose-bobaavax.yml pull
$ docker compose -f docker-compose-bobaavax.yml up
For secondary addresses, such as L2 Tokens and Messengers, please see the Boba Avalanche address registration dump.