[bisq-network/roles] Seednode Operator (#15)

Manfred Karrer notifications at github.com
Sat Apr 6 16:34:12 UTC 2019


We all should get the DAO setup ready now. Here is a summary of the instructions:

Checkout https://github.com/ManfredKarrer/bisq/tree/rc_v1.0.0 and build from that. There is a new mainnet genesis tx so that can be used for a testrun as DAO full node. Do not try to run as DAO full node with the master branch as the genesis tx there is very old and will take long time for sync.

Here are my conf files for btc core:
bitcoin.conf:
```
datadir=.....
maxconnections=800
timeout=30000
listen=0
server=1
txindex=1
rpcallowip=127.0.0.1
rpcuser=....
rpcpassword=....
blocknotify=bash /root/.bitcoin/blocknotify %s
```
datadir, rpcuser, rpcpassword, blocknotify  need to be edited by yourself. maxconnections and timeout i took from my btc nodes. We do not run it as listening node to safe resources. We might change that later.

blocknotify file:
```
#!/bin/bash
echo $1 | nc -w 1 127.0.0.1 5110
```

I use a small start script for the seed node
```nohup sh loop.sh &```

loop.sh:
```
#!/bin/bash

java -XX:+UseG1GC \
-Xms512m \
-Xmx2000m \
-jar bisq/seednode/build/libs/seednode-all.jar \
--maxMemory=1200 \
--maxConnections=30 \
--baseCurrencyNetwork=BTC_MAINNET \
--appName=seed \
--nodePort=8000 \
--daoActivated=true \
--fullDaoNode=true \
--rpcPort=8332 \
--rpcUser=... \
--rpcPassword=... \
--rpcBlockNotificationPort=5110 \
>/dev/null 2>error.log
```

Be sure the rpcBlockNotificationPort is matching the entry in the blocknotify file.
Please stick with the memory settings as above as I tested a lot and those seem to work well.

Be sure to have 4 GB RAM, its needed.
300 GB space is needed as well as with txindex the current blockchain is about 260 GB and in 4-6 months we reach 300. 

If your servers setting is not completely trivial please add a small readme file in case I need to access so I can easily find my way how to stop, restart or edit config files and program arguments in case you are not available.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/roles/issues/15#issuecomment-480517971
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190406/751c2a7e/attachment.html>


More information about the bisq-github mailing list