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

[jakiman]

I like the idea also. Let them have it. They deserve the hours spent.
But yeah, hope my withdrawal from Bittrex doesn't get lost either.

[1715292041]

1715292041

[1715292041]

1715292041

[berron]

I also like that idea, and it's only a 0.14 % of the total supply, so no influence in price expected.

[jakiman]

So sounds like there's no point keeping the v2.0.0.0 wallet running / staking right now?

[q327K091]

How are the progress on patching [DNET] Darknet going on? Any difficulties? Do you already have an expected release date?

Concerning the first 60k, I propose to split them between the devs who solved the POS problem as a thank you from the community.

May the code be with you

like the idea *thumbs up*

+1 , this could be lots of money at one point but +1 , believe there are 3 devs behind this at varying amount of contribution and time spent, and they all going very smart about how they do things, even patches are slow , just perfect, no rush from my side, as promised if this moves any serious direction upwards I will establish my own bounties

[presstab]

Also just noticed presstab's block explorer is now up and running beyond block 259200.

http://www.presstab.pw/phpexplorer/DNET/index.php

Showing pow blocks, maybe it's following a v1 fork???

They aren't pow I just need to edit a few thing so it displays correctly.

[major_coiner]

So, is it safe to buy some more darknet on bittrex while wallet is on maintenance? Are those coins on the right fork? I mean, at this time I can't sync my wallet, I presume no one can as well, Bittrex included. May I buy some more anyway or should I wait for the wallet to finish the maintenance? Thanks in advance.

[mxnsch]

Since everybody except the devs has some spare time at hand you might be interested to setup some more masternodes

Here is a script that i have written a couple of days ago to setup and configure a couple of masternodes (server side) automatically:
https://github.com/marsmensch/masternode-vps-setup

Notes and features

• it is currently only tested on a vultr VPS and Ubuntu 16.04 (smallest instance is good for up to 8 nodes)
• porting to 14.04 is probably not too hard, but no priority for me
• this script doesnt care about the controller side of things
• installs 1-100 (or more!) masternodes in parallel on one machine, with individual config and data
• compilation is currently from source, ubuntu packages on the way
• some security hardening is done, including firewalling and a separate user
• automatic startup for all masternode daemons
• ipv6 enabled, tor/onion will follow
• this script needs to run as root, the masternodes will and should not!

What do i need to do after running this script?

• 0) Download and tun this script on your VPS instance
• 1) change the amount of masternodes you want to install/configure at the top of the script ("eg SETUP_MNODES_COUNT=3")
• 2) Add your masternode private key to the configuration file(s) located at /etc/masternodes/... For example, when installing three DNET masternodes:
  

  * writing config file /etc/masternodes/darknet_n1.conf
  * writing config file /etc/masternodes/darknet_n2.conf
  * writing config file /etc/masternodes/darknet_n3.conf

• 3) run /usr/local/bin/restart_masternodes.sh to activate the services permanently. Individual masternode data directories are located in /var/lib/darknet/darknet${NUMBER_OF_NODE}
• 4) subsequently, you should only work as user and not root. The default user acc is masternode. Change to this user with the command "su masternode" (loged in as root)

DONE

Not foolproof, but it gets the job done to the "piece of cake" level.

[pjcltd]

Since everybody except the devs has some spare time at hand you might be interested to setup some more masternodes

Here is a script that i have written a couple of days ago to setup and configure a couple of masternodes (server side) automatically:
https://github.com/marsmensch/masternode-vps-setup

Notes and features

• it is currently only tested on a vultr VPS and Ubuntu 16.04 (smallest instance is good for up to 8 nodes)
• porting to 14.04 is probably not too hard, but no priority for me
• this script doesnt care about the controller side of things
• installs 1-100 (or more!) masternodes in parallel on one machine, with individual config and data
• compilation is currently from source, ubuntu packages on the way
• some security hardening is done, including firewalling and a separate user
• automatic startup for all masternode daemons
• ipv6 enabled, tor/onion will follow
• this script needs to run as root, the masternodes will and should not!

What do i need to do after running this script?

• 0) Download and tun this script on your VPS instance
• 1) change the amount of masternodes you want to install/configure at the top of the script ("eg SETUP_MNODES_COUNT=3")
• 2) Add your masternode private key to the configuration file(s) located at /etc/masternodes/... For example, when installing three DNET masternodes:
  

  * writing config file /etc/masternodes/darknet_n1.conf
  * writing config file /etc/masternodes/darknet_n2.conf
  * writing config file /etc/masternodes/darknet_n3.conf

• 3) run /usr/local/bin/restart_masternodes.sh to activate the services permanently. Individual masternode data directories are located in /var/lib/darknet/darknet${NUMBER_OF_NODE}
• 4) subsequently, you should only work as user and not root. The default user acc is masternode. Change to this user with the command "su masternode" (loged in as root)

DONE

Not foolproof, but it gets the job done to the "piece of cake" level.

nice scrypt
hows it going to work with Darknet when you can only have 1 masternode per IP address  ?


thanks
Paul

[cryptomaxsun]

What happened to the DNET? The last block 259516 and more is not synchronized.

[pjcltd]

What happened to the DNET? The last block 259516 and more is not synchronized.

THe devs are working on the issue
if you read back a page or so you will see whats been going on.

dont worry they will sort it out.

thanks
Paul

[Haunebu81]

nice scrypt
hows it going to work with Darknet when you can only have 1 masternode per IP address  ?


thanks
Paul

I would like to know this as well.

[Haunebu81]

Will the MN rewards remain the same at 22.5 DNET per block?

[4x13]

Will the MN rewards remain the same at 22.5 DNET per block?

Nope, Check to OP for the explanation

[tombtc]

Is there any richlist? Apart from the one on bittrex?

[4x13]

Is there any richlist? Apart from the one on bittrex?

Yes, Presstabs Explorer has that, Once everything is back up that is..

[mxnsch]

Since everybody except the devs has some spare time at hand you might be interested to setup some more masternodes

Here is a script that i have written a couple of days ago to setup and configure a couple of masternodes (server side) automatically:
https://github.com/marsmensch/masternode-vps-setup

Notes and features

• it is currently only tested on a vultr VPS and Ubuntu 16.04 (smallest instance is good for up to 8 nodes)
• porting to 14.04 is probably not too hard, but no priority for me
• this script doesnt care about the controller side of things
• installs 1-100 (or more!) masternodes in parallel on one machine, with individual config and data
• compilation is currently from source, ubuntu packages on the way
• some security hardening is done, including firewalling and a separate user
• automatic startup for all masternode daemons
• ipv6 enabled, tor/onion will follow
• this script needs to run as root, the masternodes will and should not!

What do i need to do after running this script?

• 0) Download and tun this script on your VPS instance
• 1) change the amount of masternodes you want to install/configure at the top of the script ("eg SETUP_MNODES_COUNT=3")
• 2) Add your masternode private key to the configuration file(s) located at /etc/masternodes/... For example, when installing three DNET masternodes:
  

  * writing config file /etc/masternodes/darknet_n1.conf
  * writing config file /etc/masternodes/darknet_n2.conf
  * writing config file /etc/masternodes/darknet_n3.conf

• 3) run /usr/local/bin/restart_masternodes.sh to activate the services permanently. Individual masternode data directories are located in /var/lib/darknet/darknet${NUMBER_OF_NODE}
• 4) subsequently, you should only work as user and not root. The default user acc is masternode. Change to this user with the command "su masternode" (loged in as root)

DONE

Not foolproof, but it gets the job done to the "piece of cake" level.

nice scrypt
hows it going to work with Darknet when you can only have 1 masternode per IP address  ?


thanks
Paul

IPv6 now, onion later. IP addresses are automatically assigned from the range vultr assigns per virtual server.

[borris123]

Since everybody except the devs has some spare time at hand you might be interested to setup some more masternodes

Here is a script that i have written a couple of days ago to setup and configure a couple of masternodes (server side) automatically:
https://github.com/marsmensch/masternode-vps-setup

Notes and features

• it is currently only tested on a vultr VPS and Ubuntu 16.04 (smallest instance is good for up to 8 nodes)
• porting to 14.04 is probably not too hard, but no priority for me
• this script doesnt care about the controller side of things
• installs 1-100 (or more!) masternodes in parallel on one machine, with individual config and data
• compilation is currently from source, ubuntu packages on the way
• some security hardening is done, including firewalling and a separate user
• automatic startup for all masternode daemons
• ipv6 enabled, tor/onion will follow
• this script needs to run as root, the masternodes will and should not!

What do i need to do after running this script?

• 0) Download and tun this script on your VPS instance
• 1) change the amount of masternodes you want to install/configure at the top of the script ("eg SETUP_MNODES_COUNT=3")
• 2) Add your masternode private key to the configuration file(s) located at /etc/masternodes/... For example, when installing three DNET masternodes:
  

  * writing config file /etc/masternodes/darknet_n1.conf
  * writing config file /etc/masternodes/darknet_n2.conf
  * writing config file /etc/masternodes/darknet_n3.conf

• 3) run /usr/local/bin/restart_masternodes.sh to activate the services permanently. Individual masternode data directories are located in /var/lib/darknet/darknet${NUMBER_OF_NODE}
• 4) subsequently, you should only work as user and not root. The default user acc is masternode. Change to this user with the command "su masternode" (loged in as root)

DONE

Not foolproof, but it gets the job done to the "piece of cake" level.

nice scrypt
hows it going to work with Darknet when you can only have 1 masternode per IP address  ?


thanks
Paul

IPv6 now, onion later. IP addresses are automatically assigned from the range vultr assigns per virtual server.

guide be good. video or step by step pics.

[mxnsch]

There is no point in writing a guide for a script at that level. It is meant to be used on a scale and work 99% automatically without input and any "schischi" as we say around here.

Run this script on a Ubuntu 16.04 vultr VPS and replace the masternode keys in the config files. There is nothing complicated to it, just give it a shot.

[pjcltd]

There is no point in writing a guide for a script at that level. It is meant to be used on a scale and work 99% automatically without input and any "schischi" as we say around here.

Run this script on a Ubuntu 16.04 vultr VPS and replace the masternode keys in the config files. There is nothing complicated to it, just give it a shot.

Hi ill give it a go tonight


thanks

Paul

[borris123]

There is no point in writing a guide for a script at that level. It is meant to be used on a scale and work 99% automatically without input and any "schischi" as we say around here.

Run this script on a Ubuntu 16.04 vultr VPS and replace the masternode keys in the config files. There is nothing complicated to it, just give it a shot.

Can you explain how it works with multiple ips? How many ips does vultr give you? What spec would you need for it to work on however many vps you have running?