[ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN

[crackfoo]

the linux daemon reports out of memory, after re-syncing....

need some more info, what are your vps specs?

22:40:19: Darknet error getblocktemplate result

Is the gbt changed a lot?

Did you completely delete and re-sync the blockchain?

rm -rf backups blocks chainstate database peers.dat

I would delete everything except the darknet.conf, masternode.conf and wallet.dat?? and then re-sync? Your VPS will require more ram than before

it's a dedicated box with 128gb, no resource issues. our of memory might be an erroneous message from my stratum server, but simply means, there have been changes that make it not compatible with normal gbt results...

Are you trying to mine with this new daemon?

yea, it was going to update the pools wallet.

yeah, that won't work, stick with the v1.1.0.2 daemon as the new wallet won't have PoW abilities any longer. PoS only

ahh thought it would be the same untill the fork. thnx

[1714173213]

1714173213

[1714173213]

1714173213

[1714173213]

1714173213

[1714173213]

1714173213

[4x13]

the linux daemon reports out of memory, after re-syncing....

need some more info, what are your vps specs?

22:40:19: Darknet error getblocktemplate result

Is the gbt changed a lot?

Did you completely delete and re-sync the blockchain?

rm -rf backups blocks chainstate database peers.dat

I would delete everything except the darknet.conf, masternode.conf and wallet.dat?? and then re-sync? Your VPS will require more ram than before

it's a dedicated box with 128gb, no resource issues. our of memory might be an erroneous message from my stratum server, but simply means, there have been changes that make it not compatible with normal gbt results...

Are you trying to mine with this new daemon?

yea, it was going to update the pools wallet.

yeah, that won't work, stick with the v1.1.0.2 daemon as the new wallet won't have PoW abilities any longer. PoS only

ahh thought it would be the same untill the fork. thnx

Yeah, sorry. Thats my bad. We took it out as it wasn't needed any longer.

[werwortmann]

I updated my MN to the latest wallet.
I have fully re-synced everything from scratch, only keeping config files.
My synchronizing additional data (synchronizing masternodes) is stuck at 50% in the gui and the debug command: masternode list, only shows my masternode and no others.
All my peers are v1.
Is there an issue or just a lack of v2 masternodes at the moment?

[kokokoin]

Thanks for update!
I like to sit and watch my wallet syncing. I almost feel all blocks running through it.

UPD: my wallet is also stuck at syncing masternodes, 50%.

[werwortmann]

Mine has now moved to 75%, and there are 2 other masternodes.
So just need more masternodes on the new version to get everything going

[NotMyFarm]

are any onion addresses available (community and such)

wallest is stuck on 50% masternode sync as well

'Try mix' does not work
"Try to manually submit .... " how does that work ?

how many master nodes are there ?

[pjcltd]

Mine has now moved to 75%, and there are 2 other masternodes.
So just need more masternodes on the new version to get everything going

same here now im on 75 %


thanks
Paul

[BitcoinFX]

If your running Ubuntu 14.0.4 and using the pre-compiled linux binary update i.e.

- https://github.com/Darknet-Crypto/Darknet/releases/ - Darknet-Qt-Linux64-Wallet-v2.0.0.0.zip

You will likely encounter the following 'errors' when starting darknetd ;

./darknetd: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by ./darknetd)
./darknetd: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by ./darknetd)
./darknetd: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by ./darknetd)

With the following recommended solution / 'fix' ;

Code:

sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
sudo apt-get dist-upgrade

If, "sudo: add-apt-repository: command not found", first ;

Code:

sudo apt-get install software-properties-common

However,

./darknetd: relocation error: ./darknetd: symbol _ZNKSt8ios_base7failureB5cxx114whatEv, version GLIBCXX_3.4.21 not defined in file libstdc++.so.6 with link time reference

- See: https://stackoverflow.com/questions/36816570/glibcxx-3-4-21-not-defined-in-file-libstdc-so-6-with-link-time-reference

" GCC 5.1 or 5.2 (can't remember now, duckduckgo it) changed C++ ABI. Your standard ubuntu (including libstdc++) is compiled with old ABI.

Your gcc compiler tries to use new ABI. Sometimes it works, most of the time - no.

So, there are 3 ways to compile your code:

1) downgrade gcc

2) add -D_GLIBCXX_USE_CXX11_ABI=0 (cmake example) flag (if you go this way, you should add this flag to every makefile or project you build till you upgrade ubuntu or downgrade gcc)

3) upgrade Ubuntu (tested it, by the way 16.04 goes with new ABI and new gcc by default, I had to ack-grep and remove flag mentioned above from all my pet projects) "

#LinuxissoFun !

[shimlbit]

git clone https://github.com/Darknet-Crypto/Darknet
cd Darknet
./autogen.sh
cd depends
make
cd ..
./configure --prefix=`pwd`/depends/x86_64-pc-linux-gnu
make

thats for ubuntu 14.4 64 bit

works for me ..no syncing problems...im on version 2
and masternode is running!

[BitcoinFX]

git clone https://github.com/Darknet-Crypto/Darknet
cd Darknet
./autogen.sh
cd depends
make
cd ..
./configure --prefix=`pwd`/depends/x86_64-pc-linux-gnu
make

thats for ubuntu 14.4 64 bit

works for me ..no syncing problems...im on version 2
and masternode is running!

Indeed. The obvious solution is to compile it from source yourself.

However, with many instances below 512MB RAM and even with a SWAP file above 1GB RAM compiling can take a while. 

[DRPD]

all my mn's and controller wallet updated

resync was a bit slow for most mn's. but so far so good & no problems *crossing fingers* 

thanks for your work dev's

[4x13]

Yes, I compiled the wallets on 16.04, I will post a new wallet for 14.04 shortly, sorry for the issues..

[shimlbit]

Yes, I compiled the wallets on 16.04, I will post a new wallet for 14.04 shortly, sorry for the issues..

the new wallet works for my 14.4 without any issues..

[BitcoinFX]

Yes, I compiled the wallets on 16.04, I will post a new wallet for 14.04 shortly, sorry for the issues..

the new wallet works for my 14.4 without any issues..

Again, Indeed. It's a bit of an odd one.

As per the posted 'fix' https://bitcointalk.org/index.php?topic=1262920.msg15799587#msg15799587 - sometimes it will just work, sometimes it won't. I also had a static build daemon for another coin project that just worked after I installed the ppa:ubuntu-toolchain-r/test

Any joy with using the darknet apt-add-repository ppa: directly ?

Think I'll hold fire for a working static 14.04 binary from s3v3nh4cks, for convenience sake!  

[werwortmann]

Hi,

Is there a guide available to use tor to run multiple masternodes, linux specifically?

[4x13]

Yes, I compiled the wallets on 16.04, I will post a new wallet for 14.04 shortly, sorry for the issues..

the new wallet works for my 14.4 without any issues..

Again, Indeed. It's a bit of an odd one.

As per the posted 'fix' https://bitcointalk.org/index.php?topic=1262920.msg15799587#msg15799587 - sometimes it will just work, sometimes it won't. I also had a static build daemon for another coin project that just worked after I installed the ppa:ubuntu-toolchain-r/test

Any joy with using the darknet apt-add-repository ppa: directly ?

Think I'll hold fire for a working static 14.04 binary from s3v3nh4cks, for convenience sake!  

if you look at the OP, I also added the APT means of installing the wallet, you should be able to install for your OS level that way also. they do builds for each OS. They should be update soon, it was submitted yesterday.

[BitcoinFX]

Hi,

Is there a guide available to use tor to run multiple masternodes, linux specifically?

If you are looking to help expand the Tor network and DNET network by running a 'dual stack' masternode then yes - some information can already be found in this thread, with a main guide being worked on.

If you are seeking to essentially circumvent DNET masternode security by utilizing Tor .Exit node operators IP offerings as your own masternode IP's - then no, not really.  

The Tor network has less than 1000 .Exit nodes currently - see: https://torstatus.blutmagie.de/ - of which the majority will not allow exit traffic on DNET's 'default' port - being why port 989 was selected for DNET addnode=.onion hidden_services. Furthermore, Tor Exit node IP addresses rotate by default every 10 mins, which is certainly not ideal for attempting to run masternode exits over Tor.

...

Tor 0.2.8.6 stable was actually released yesterday - https://blog.torproject.org/blog/tor-0286-released - I've seen permission errors related to upgrading existing hidden_services on some linux distributions. Basically similar to this; https://stackoverflow.com/questions/31620783/what-is-wrong-with-my-tor

Oh, #LinuxissoFun ! today.  

[werwortmann]

Hi,

Is there a guide available to use tor to run multiple masternodes, linux specifically?

If you are looking to help expand the Tor network and DNET network by running a 'dual stack' masternode then yes - some information can already be found in this thread, with a main guide being worked on.

If you are seeking to essentially circumvent DNET masternode security by utilizing Tor .Exit node operators IP offerings as your own masternode IP's - then no, not really.  

The Tor network has less than 1000 .Exit nodes currently - see: https://torstatus.blutmagie.de/ - of which the majority will not allow exit traffic on DNET's 'default' port - being why port 989 was selected for DNET addnode=.onion hidden_services. Furthermore, Tor Exit node IP addresses rotate by default every 10 mins, which is certainly not ideal for attempting to run masternode exits over Tor.

...

Tor 0.2.8.6 stable was actually released yesterday - https://blog.torproject.org/blog/tor-0286-released - I've seen permission errors related to upgrading existing hidden_services on some linux distributions. Basically similar to this; https://stackoverflow.com/questions/31620783/what-is-wrong-with-my-tor

Oh, #LinuxissoFun ! today  

I have read the information on this thread, but my linux is way too weak to fill in the missing gaps.
But glad to hear a guide is in the works

[4x13]

Hi,

Is there a guide available to use tor to run multiple masternodes, linux specifically?

If you are looking to help expand the Tor network and DNET network by running a 'dual stack' masternode then yes - some information can already be found in this thread, with a main guide being worked on.

If you are seeking to essentially circumvent DNET masternode security by utilizing Tor .Exit node operators IP offerings as your own masternode IP's - then no, not really.  

The Tor network has less than 1000 .Exit nodes currently - see: https://torstatus.blutmagie.de/ - of which the majority will not allow exit traffic on DNET's 'default' port - being why port 989 was selected for DNET addnode=.onion hidden_services. Furthermore, Tor Exit node IP addresses rotate by default every 10 mins, which is certainly not ideal for attempting to run masternode exits over Tor.

...

Tor 0.2.8.6 stable was actually released yesterday - https://blog.torproject.org/blog/tor-0286-released - I've seen permission errors related to upgrading existing hidden_services on some linux distributions. Basically similar to this; https://stackoverflow.com/questions/31620783/what-is-wrong-with-my-tor

Oh, #LinuxissoFun ! today  

Thank You for your hard work in researching all the Tor stuff for DarkNet, I am sure your Dual Stack Guide for the latest release will be as detailed as your original one. I will be posting the guide in the OP when it is completed.

[4x13]

I just posted a poll, need to know what everyone thinks, as I am sure there are some who will care, but I don't see a difference.