camosoul
Well-known member
so, this:
The chain is getting awfully long...
when running as:
It pretty much always times out because there are so many requests.
It's become impossible to obtain payments.
I know I should be running my own dashd for these reasons:
So, this:
This is where it goes sideways..
When reading dashmnb/config.sample.mainnet.py I see things that look pretty dangerous, and the language barrier does not clarify sufficient for me to figure out what I need, what needs to be changed, what I can eliminate for my intended use model... Some things look like they are totally un-useful for my purpose and could be eliminated... But I don't want to end up with dashd listening on an open port with this "xxxx" username and password... Bad Things(tm) would happen.
I just want to have dashmnb pull this data from local (127.0.0.1) dashd on the same machine; safely.
Yes, I already did -reindex.
Code:
---> getting unused addresses of bip32 path
when running as:
Code:
cd dashmnb/
. venv3/bin/activate
torify python bin/dashmnb.py -b
It's become impossible to obtain payments.
I know I should be running my own dashd for these reasons:
Code:
- dashmnb connects remote service using ssl
- However `remote dashd/rpc service` use nginx(web server) as frontend
[https://github.com/chaeplin/dash-ticker/tree/master/web/nginx](https://github.com/chaeplin/dash-ticker/tree/master/web/nginx) has frontend configuration
- As nginx(web server) leave a log containning ip address of user like following
```
10.10.10.1 - dashmnb [18/Feb/2017:06:13:33 +0000] "POST / HTTP/1.1" 200 227 "-" "AuthServiceProxy/0.1" "-" [-] [-] []
10.10.10.1 - dashmnb [18/Feb/2017:06:13:39 +0000] "POST / HTTP/1.1" 200 227 "-" "AuthServiceProxy/0.1" "-" [-] [-] []
10.10.10.1 - dashmnb [18/Feb/2017:06:13:44 +0000] "POST / HTTP/1.1" 200 92 "-" "AuthServiceProxy/0.1" "-" [-] [-] []
10.10.10.1 - dashmnb [18/Feb/2017:06:13:54 +0000] "POST / HTTP/1.1" 200 359050 "-" "AuthServiceProxy/0.1" "-" [-] [-] []
```
- The ip address is `privacy concern`
Code:
- copy dashlib/config.sample.mainnet.py to run own dashd/Dash-QT
When reading dashmnb/config.sample.mainnet.py I see things that look pretty dangerous, and the language barrier does not clarify sufficient for me to figure out what I need, what needs to be changed, what I can eliminate for my intended use model... Some things look like they are totally un-useful for my purpose and could be eliminated... But I don't want to end up with dashd listening on an open port with this "xxxx" username and password... Bad Things(tm) would happen.
I just want to have dashmnb pull this data from local (127.0.0.1) dashd on the same machine; safely.
Yes, I already did -reindex.
Last edited: