Aims to provide a simple and easy way to run atomicals-electrumx server.
server=1
txindex=1
# genearate with [rpcauth.py](https://github.com/bitcoin/bitcoin/blob/master/share/rpcauth/rpcauth.py)
# equals to `rpcuser=nextdao` and `rpcpassword=nextdao`
rpcauth=nextdao:cca838b4b19bdc6093f4e0312550361c$213834a29e8488804946c196781059a7ee0ac2b48dbf896b4c6852060d9d83dd
rpcallowip=127.0.0.1
rpcallowip=172.0.0.0/8
rpcallowip=192.168.0.0/16
rpcbind=0.0.0.0
1. Download docker-compose.yml to a folder.
Edit docker-compose.yml
:
- Change
127.0.0.1
tolan ip
of the bitcoin core host, eg: 192.168.50.2. - Also change
nextdao:nextdao
to yourrpcuser:rpcpassword
in `bitcoin.conf
docker-compose pull && docker-compose up -d
- the electrumx indexes stored in
./electrumx-data
directory. - use
docker-compose logs -f
to check the logs. - use
docker-compose down
to stop the server.
3. Used in atomicals-js
Edit .env with ELECTRUMX_PROXY_BASE_URL=http://localhost:8080/proxy
, then use all commands as usual.
If you run atomicals cli in anthoer host, change localhost
to the ip
of the proxy
server.
docker-compose ps
If you see electrumx
is healthy
, then the server is ready.
- Check if bitcoind is running.
- Check if
rpcbind
include theip
used inDAEMON_URL
- Run
docker-compose ps
to check your container name. eg:electrumx-electrumx-1
- Run
docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' electrumx-electrumx-1
to get container ip - Check if the ip in rpcallow range
Check if rpc username and password correct?
There are many reasons that may cause the sync slow.
- The
bitcoind
is not fully synced. - You are using a HDD instead of SSD.
- Your CPU single core performance is not good enough.
- You are runing docker on windows or macos.