Search results

what to do if masternode got delisted? don't know how. protx mismatch mismatch of all addresses using dashmasternodetool

what stops you from stealing private keys and all crypto? and you are not even a masternode once. who audited and certified you?

how to make this happen? trezor suite is not allowing to lock 1k, splits with next transaction

protx update_service pose_banned protx-dup (code -26) same ip got pose_banned trying to update with the same ip address cannot do that? after pose_banned I must switch to new ip? or if the same IP then do new protx register? :/

proTxHash: The transaction id of the initial ProRegTx https://docs.dash.org/en/stable/masternodes/maintenance.html#proupservtx how do I update to a new ip? where to get proTxHash it does not exist Example (remove line breaks if copying): protx register_prepare...

dashd as root will not work? * * * * * cd /root/.dashcore/sentinel && venv/bin/python bin/sentinel.py 2>&1 $ * * * * * pidof dashd || ~/.dashcore/dashd and sentiel should be running every minute and if dashd is not running then start dashd as well...

can I use dashman? bootstrap is ok? reindex is a must? root@a52de8b7eaa3:~# cd ~ root@a52de8b7eaa3:~# git clone https://github.com/moocowmoo/dashman Cloning into 'dashman'... remote: Enumerating objects: 1265, done. remote: Total 1265 (delta 0), reused 0 (delta 0), pack-reused 1265 Receiving...

how can docker affect it? is this version compatible with docker? before this update dash worked for months and months without an issue

Where are the logs? How could I debug this bs pose ban? After pose ban strikes I cannot access daemon right? Mn declines connection? Masternode connect ip unsuccessful

ffs I have a dedicated server and it keeps PoSE banned worst bs invented anybody else is suffering? Intel® Core™ i7-6700 Quad-Core Skylake incl. Hyper-Threading Technology 32GB RAM, busy 19GB RAM 2 TB HDD /dev/md2 1.8T 965G 761G 56% / 40 private IPs minimal DDOS hetzner...

same problem here this update is bad all prev updates were flawless what exactly is not good enough ? where is the log?

dashman is obsolete now? outdated? cannot even install sentinel root@e4658ba3ec87:~/dashman# ./dashman install sentinel dashman version 0.1.27 (2-g652ffe7) - Fri Mar 8 23:38:01 UTC 2019 gathering info, please wait... DONE! --> Downloading sentinel... DONE! --> installing dependencies...

app crashes if port is not equal to 9999

no security issue nodes can verify authenticity of each other on any port but RIPE policy for issuing new ips is a real problem and expensive

won't work, rest of MNs would not know where to find me

you don't think good give people options why should i buy new ips? with RIPE rules it is getting difficult

solution is to start docker container from scratch, otherwise won't be able to shake off deep internal corruption that will pop up some days later remove all related to mn and start from scratch seems to help

ok seems to work, just ignore this error and restart remote mn from local hot wallet pc

must be 9999 for mainnet ? why would you restrict port for mn? why can't it be flexible?

just a minimal ubuntu docker + all libs needed for dash to run docker is great, but when it goes into limbo or its docker-proxy lib then all hell breaks loose could you add self-checking and filesystem check mechanisms to dash?