Top wallet on bittrex has 700K 
how can you see this data?
Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 469. (Read 782382 times)
March 25, 2016, 04:16:44 PM
how can you see this data?
March 25, 2016, 12:21:32 PM
Hi guys
i have updated all the vps's with ip address range 158.69.137.*
i will force update on as many VPS's as i can you make sure the network is unto date
Thanks
Paul
i have updated all the vps's with ip address range 158.69.137.*
i will force update on as many VPS's as i can you make sure the network is unto date
Thanks
Paul
plesae don't change anything on my vps's
no offense and i'm sure it is well-meant on your side but i don't like it if anybody else is doing changes on my services (expect support for things that don't work at all)
why not make a youtube video from scratch how to set up masternodes at your vps hosting.
Start with the console how to create the masternodes address, getting the public and private keys etc etc....everything from first opening the dnet wallet.
I have recommended several people to buy dnet and set up masternodes. Seems most have not done so because they don't know how to do it.
It's only a few steps so should be easy to make a youtube vid and link it in the OP.
CryptoHunter,
If they aren't familiar with linux and coins, I would go with a managed node. The ones that I host are fully managed, just keep your local wallet on the same version as the managed node.
March 25, 2016, 12:10:39 PM
Ever since the update I can't get anything working. Masternodes get disabled before I can get a single reward and one of the masternode wallets
refuses to sync
refuses to sync
Make sure all wallets are on 1.0.2.1. I had the same problem as DRPD where the first couple of times I updated my VPS wallets on MP-hosting, they didn't actually update. Once I figured that out (and presumably after the latest work from the devs), my MNs have stayed enabled and everything syncs. It's been less than 24 hours so payouts haven't resumed yet, but it's looking good so far. You might also try re-indexing all your wallets after upgrading.
March 25, 2016, 10:51:51 AM
Hi guys
i have updated all the vps's with ip address range 158.69.137.*
i will force update on as many VPS's as i can you make sure the network is unto date
Thanks
Paul
i have updated all the vps's with ip address range 158.69.137.*
i will force update on as many VPS's as i can you make sure the network is unto date
Thanks
Paul
plesae don't change anything on my vps's
no offense and i'm sure it is well-meant on your side but i don't like it if anybody else is doing changes on my services (expect support for things that don't work at all)
why not make a youtube video from scratch how to set up masternodes at your vps hosting.
Start with the console how to create the masternodes address, getting the public and private keys etc etc....everything from first opening the dnet wallet.
I have recommended several people to buy dnet and set up masternodes. Seems most have not done so because they don't know how to do it.
It's only a few steps so should be easy to make a youtube vid and link it in the OP.
March 25, 2016, 10:37:33 AM
I've updated http://dnet.suprnova.cc to the latest github as well
March 25, 2016, 10:21:15 AM
Since upgrading my MN's & controller wallet to 1.0.2.1, I haven't had any blockchain stuck issues for past 14 hours. 
Thanks for the hard work devs!
Thanks for the hard work devs!
March 25, 2016, 08:43:56 AM
for vps nodes
send reboot command via ssh AFTER updating binaries.
I kept getting 'not capable:hotnode waiting for remote activation' on either attempt to start remotely or ssh starting, UNTIL i reboot vps it then activate successful
I could not start the node locally it would only start with my remote wallet command
send reboot command via ssh AFTER updating binaries.
I kept getting 'not capable:hotnode waiting for remote activation' on either attempt to start remotely or ssh starting, UNTIL i reboot vps it then activate successful
I could not start the node locally it would only start with my remote wallet command
March 25, 2016, 08:28:36 AM
Ever since the update I can't get anything working. Masternodes get disabled before I can get a single reward and one of the masternode wallets
refuses to sync
refuses to sync
March 25, 2016, 07:22:32 AM
@DRPD Indeed. No worries.
On a separate note, I'm looking for folks to 'test' my ShadowSOCKS - SSFX Servers Project (beta) which currently has some free 'lifetime' (one year duration beta) passkey's available for BitcoinTalk Senior members, Hero members and those of Legendary status.
- https://bitcointalksearch.org/topic/shadowsocks-ssfx-servers-project-beta-socks5-proxies-1410622
I'm posting in this thread as I will most likely be accepting DNET as a payment method for the main production server passkey's.
Cheers!
On a separate note, I'm looking for folks to 'test' my ShadowSOCKS - SSFX Servers Project (beta) which currently has some free 'lifetime' (one year duration beta) passkey's available for BitcoinTalk Senior members, Hero members and those of Legendary status.
- https://bitcointalksearch.org/topic/shadowsocks-ssfx-servers-project-beta-socks5-proxies-1410622
I'm posting in this thread as I will most likely be accepting DNET as a payment method for the main production server passkey's.
Cheers!
March 25, 2016, 06:39:58 AM
@DRPD - The vps upgrade guide I have posted is really meant for individuals using independent vps hosting i.e. not really for services like mp-hosting, which as I understand it is a 'managed' hosting service. However, I can understand your readiness to resolve issues with your own Masternodes ofc.
Again, the guide is aimed at easy-to-follow linux command line instructions, that will install the pre-built linux binaries 'as if' built from source.
Glad you have now got it running OK anyway.
Just to clarify to everyone, I'm not part of 'mp-hosting' nor am I directly part of the dnet dev. team - just doing some network related research.
...
On a separate note - I have successfully built dnet on a Whonix Workstation ( as the current pre-built linux binaries won't run )
- https://bitcointalksearch.org/topic/m.14259019
I'm working on a guide for this currently. Both the Whonix Gateway and Whonix Workstation can be run on 1 machine in 2 separate VirtualBox instances, automatically pushing all dnet CLIENT traffic through the Whonix Gateway, over Tor, whilst the CLIENT wallet runs securely in the fully sand-boxed Whonix Workstation.
Again, the guide is aimed at easy-to-follow linux command line instructions, that will install the pre-built linux binaries 'as if' built from source.
Glad you have now got it running OK anyway.
Just to clarify to everyone, I'm not part of 'mp-hosting' nor am I directly part of the dnet dev. team - just doing some network related research.
...
On a separate note - I have successfully built dnet on a Whonix Workstation ( as the current pre-built linux binaries won't run )
- https://bitcointalksearch.org/topic/m.14259019
I'm working on a guide for this currently. Both the Whonix Gateway and Whonix Workstation can be run on 1 machine in 2 separate VirtualBox instances, automatically pushing all dnet CLIENT traffic through the Whonix Gateway, over Tor, whilst the CLIENT wallet runs securely in the fully sand-boxed Whonix Workstation.
no problem!
i was able to use your template 1:1 on some other ubuntu servers i use. Your template ist very useful, many thanks for that!
just posted my solutions for other users on mp-hosting maybe running into the same problem like me...
if we work together everything will be fine
so far non of my masternodes have gone into "expired state" after the upgrade
"crossing fingers" ....
March 25, 2016, 06:00:57 AM
@DRPD - The vps upgrade guide I have posted is really meant for individuals using independent vps hosting i.e. not really for services like mp-hosting, which as I understand it is a 'managed' hosting service. However, I can understand your readiness to resolve issues with your own Masternodes ofc.
Again, the guide is aimed at easy-to-follow linux command line instructions, that will install the pre-built linux binaries 'as if' built from source.
Glad you have now got it running OK anyway.
Just to clarify to everyone, I'm not part of 'mp-hosting' nor am I directly part of the dnet dev. team - just doing some network related research.
...
On a separate note - I have successfully built dnet on a Whonix Workstation ( as the current pre-built linux binaries won't run )
- https://bitcointalksearch.org/topic/m.14259019
I'm working on a guide for this currently. Both the Whonix Gateway and Whonix Workstation can be run on 1 machine in 2 separate VirtualBox instances, automatically pushing all dnet CLIENT traffic through the Whonix Gateway, over Tor, whilst the CLIENT wallet runs securely in the fully sand-boxed Whonix Workstation.
Again, the guide is aimed at easy-to-follow linux command line instructions, that will install the pre-built linux binaries 'as if' built from source.
Glad you have now got it running OK anyway.
Just to clarify to everyone, I'm not part of 'mp-hosting' nor am I directly part of the dnet dev. team - just doing some network related research.
...
On a separate note - I have successfully built dnet on a Whonix Workstation ( as the current pre-built linux binaries won't run )
- https://bitcointalksearch.org/topic/m.14259019
I'm working on a guide for this currently. Both the Whonix Gateway and Whonix Workstation can be run on 1 machine in 2 separate VirtualBox instances, automatically pushing all dnet CLIENT traffic through the Whonix Gateway, over Tor, whilst the CLIENT wallet runs securely in the fully sand-boxed Whonix Workstation.
March 25, 2016, 04:37:34 AM
Hi guys
i have updated all the vps's with ip address range 158.69.137.*
i will force update on as many VPS's as i can you make sure the network is unto date
Thanks
Paul
i have updated all the vps's with ip address range 158.69.137.*
i will force update on as many VPS's as i can you make sure the network is unto date
Thanks
Paul
plesae don't change anything on my vps's
no offense and i'm sure it is well-meant on your side but i don't like it if anybody else is doing changes on my services (expect support for things that don't work at all)
March 25, 2016, 04:25:37 AM
Hi guys
i have updated all the vps's with ip address range 158.69.137.*
i will force update on as many VPS's as i can you make sure the network is unto date
Thanks
Paul
i have updated all the vps's with ip address range 158.69.137.*
i will force update on as many VPS's as i can you make sure the network is unto date
Thanks
Paul
March 25, 2016, 04:15:35 AM
ufff all my masternodes updated, hope the network will be fine soon
i guess i will some more dnet (price is cheap atm) so i can run some more
i guess i will some more dnet (price is cheap atm) so i can run some more
March 25, 2016, 03:28:32 AM
more than likely, what happened was that the daemon was not shut down all the way when you tried to delete the file, and it didn't let you. so when you started the daemon backup, you still had the old file.
No need to reinstall, just delete the daemon file, and replace with the new one
No need to reinstall, just delete the daemon file, and replace with the new one
@s3v3nh4cks you are right!
found the problem if you are on mp-hosting use this procedure (note: no ./ on step 3 otherwise "darknet-cli stop" will not work)
cd Darknet
cd src
darknet-cli stop
cd
rm -rv Darknet
wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.0.2.1/Darknet-Qt-Linux-Wallet-v1.0.2.1.zip
mkdir Darknet
cd Darknet
mkdir src
cd
unzip Darknet-Qt-Linux-Wallet-v1.0.2.1.zip -d Darknet/src
mv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1/darknetd Darknet/src/
mv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1/darknet-cli Darknet/src/
mv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1/darknet-tx Darknet/src/
rm -rv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1
rm -rv Darknet/src/__MACOSX
rm -R Darknet-Qt-Linux-Wallet-v1.0.2.1.zip
cd Darknet
cd src
./darknetd
./darknet-cli getinfo
./darknet-cli masternode start
March 25, 2016, 03:01:30 AM
more than likely, what happened was that the daemon was not shut down all the way when you tried to delete the file, and it didn't let you. so when you started the daemon backup, you still had the old file.
No need to reinstall, just delete the daemon file, and replace with the new one
No need to reinstall, just delete the daemon file, and replace with the new one
March 25, 2016, 02:59:09 AM
I will have to verify this tomorrow when I get to my linux box, but am almost 100% positive that the download is correct, and something got messed up in your process. I am assuming you have you daemon files in your home directory of your VPS; that being said.. use this instead, Paste this entire line into your terminal when you first login to your VPS. assuming the darknetd is already running. if it is not running, remove "./darknet-cli stop &&" from the beginning of the line.
./darknet-cli stop && sudo rm -R darknetd && sudo rm -R darknet-cli && wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.0.2.1/darknetd && wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.0.2.1/darknet-cli && sudo chmod +x darknetd && sudo chmod +x darknet-cli && ./darknetd
./darknet-cli stop && sudo rm -R darknetd && sudo rm -R darknet-cli && wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.0.2.1/darknetd && wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.0.2.1/darknet-cli && sudo chmod +x darknetd && sudo chmod +x darknet-cli && ./darknetd
just did the same procedure on 3 other servers and this time it shows the new version
strange will try again on the server with version 10001 if it is not working i guess i will reinstall the whole server
thanks anyway for all your work
March 25, 2016, 02:44:47 AM
I will have to verify this tomorrow when I get to my linux box, but am almost 100% positive that the download is correct, and something got messed up in your process. I am assuming you have your daemon files in your home directory of your VPS (If not, run these lines after moving to the directory of your choice); that being said.. use this instead, Paste this entire line into your terminal when you first login to your VPS. assuming the darknetd is already running. if it is not running, remove "./darknet-cli stop &&" from the beginning of the line.
./darknet-cli stop && sudo rm -R darknetd && sudo rm -R darknet-cli && wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.0.2.1/darknetd && wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.0.2.1/darknet-cli && sudo chmod +x darknetd && sudo chmod +x darknet-cli && ./darknetd
./darknet-cli stop && sudo rm -R darknetd && sudo rm -R darknet-cli && wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.0.2.1/darknetd && wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.0.2.1/darknet-cli && sudo chmod +x darknetd && sudo chmod +x darknet-cli && ./darknetd
March 25, 2016, 02:34:06 AM
if i do the upgrade with:
cd Darknet
cd src
./darknet-cli stop
cd
rm -rv Darknet
wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.0.2.1/Darknet-Qt-Linux-Wallet-v1.0.2.1.zip
mkdir Darknet
cd Darknet
mkdir src
cd
unzip Darknet-Qt-Linux-Wallet-v1.0.2.1.zip -d Darknet/src
mv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1/darknetd Darknet/src/
mv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1/darknet-cli Darknet/src/
mv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1/darknet-tx Darknet/src/
rm -rv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1
rm -rv Darknet/src/__MACOSX
rm -R Darknet-Qt-Linux-Wallet-v1.0.2.1.zip
cd Darknet
cd src
./darknetd
./darknet-cli getinfo
./darknet-cli masternode start
anything running fine and no error but ./darknet-cli getinfo still shows: "version" : 1000100
confusing any eplanation?
cd Darknet
cd src
./darknet-cli stop
cd
rm -rv Darknet
wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.0.2.1/Darknet-Qt-Linux-Wallet-v1.0.2.1.zip
mkdir Darknet
cd Darknet
mkdir src
cd
unzip Darknet-Qt-Linux-Wallet-v1.0.2.1.zip -d Darknet/src
mv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1/darknetd Darknet/src/
mv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1/darknet-cli Darknet/src/
mv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1/darknet-tx Darknet/src/
rm -rv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1
rm -rv Darknet/src/__MACOSX
rm -R Darknet-Qt-Linux-Wallet-v1.0.2.1.zip
cd Darknet
cd src
./darknetd
./darknet-cli getinfo
./darknet-cli masternode start
anything running fine and no error but ./darknet-cli getinfo still shows: "version" : 1000100
confusing any eplanation?
March 25, 2016, 02:33:34 AM
Nope, Just update as you normally would..
Jump to: