Binaries are up for everything but Rpi2
Syncing Win7 x64 everything is fine so far.
Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 385. (Read 782375 times)
August 09, 2016, 06:25:22 PM
Syncing Win7 x64 everything is fine so far.
August 09, 2016, 06:11:25 PM
Binaries are up for everything but Rpi2
August 09, 2016, 06:04:48 PM
self compilers can go, binaries will be up shortly, and everyone needs to update, like yesterday. Also a note regarding the possibility of unforeseen bugs, but let's get this chain moving. If users have staked they need to roll back to an old, pre-PoS blockchain backup, or do a resync
Let's go!!
Ok, my masternodes have stopped here...
Code:
darknet-cli getblockchaininfo
{
"chain" : "main",
"blocks" : 259494,
"headers" : 259494,
"bestblockhash" : "50c102c52f44c4220724c82e7eed1580e9da0874e0d9ea91984e130f511d20ba",
"difficulty" : 14.66822643,
"verificationprogress" : 0.99941685,
"chainwork" : "00000000000000000000000000000000000000000000000000dbc7d6a49e17a8"
}
My wallet is up to here:
Code:
darknet-cli getblockchaininfo
{
"chain" : "main",
"blocks" : 259544,
"headers" : 259544,
"bestblockhash" : "bb5f320345e1ebc6fc66164c8ccfe6ed72225ce49e779c4b34dd50cba90377ab",
"difficulty" : 25.49310285,
"verificationprogress" : 1.00000000,
"chainwork" : "00000000000000000000000000000000000000000000000000dbcbe95b5b96e8"
}
August 09, 2016, 05:17:56 PM
self compilers can go, binaries will be up shortly, and everyone needs to update, like yesterday. Also a note regarding the possibility of unforeseen bugs, but let's get this chain moving. If users have staked they need to roll back to an old, pre-PoS blockchain backup, or do a resync
Also it is an extremely good idea to make a full backup of your data directory.
August 09, 2016, 05:08:46 PM
self compilers can go, binaries will be up shortly, and everyone needs to update, like yesterday. Also a note regarding the possibility of unforeseen bugs, but let's get this chain moving. If users have staked they need to roll back to an old, pre-PoS blockchain backup, or do a resync
August 09, 2016, 04:06:49 PM
Looks like v2.0.1.0 wallet is coming soon. Plenty of commits. 
https://github.com/Darknet-Crypto/Darknet/commits/master
https://github.com/Darknet-Crypto/Darknet/commits/master
August 09, 2016, 03:41:34 PM
I have a couple old machines in the basement... now I split the instances across a few VMs. I think each instance need about 100meg RAM. So with 1 Gig, 7-8 masternode might be doable if the extra services are kept to a minimum.
By the way, nice script that you posted, clearly trying to do things the right way...
In my experience, you need about 120mb of RAM per instance with no other services. On vultr i we can cheat with additional swapfiles, as the harddisks are speedy SSDs By the way, nice script that you posted, clearly trying to do things the right way...
Thank you. The script is still heavily being worked on, as i took some shortcuts to keep it self-contained for the moment.
Later version will be more robust and add a even more generic masternode support to install and update DNET, DASH and SYNX masternodes.
August 09, 2016, 03:29:19 PM
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.
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?
Not sure about vultr... but you can have multiple IP#s on the same interface. As long as traffic for them is being route there by your service provider. If your service provider uses ipv6, you can easily and cheaply get more IP numbers.
On my masternode hosts, I put several IP#s on my local interface "lo" and connect TOR to those local addresse.. Each Darknet instance darknet.conf will need a different setting for bind and rpcbind... For example can use 127.0.0.1 for masternode 1 and 127.0.0.2 for masternode 2 ... 127.0.0.254 if you have enough memory, cores and disk in one machine for that many masternodes.
I'll post a guide for putting setting up masternodes with TOR soonish...
I have a couple old machines in the basement... now I split the instances across a few VMs. I think each instance need about 100meg RAM. So with 1 Gig, 7-8 masternode might be doable if the extra services are kept to a minimum.
By the way, nice script that you posted, clearly trying to do things the right way...
August 09, 2016, 03:17:14 PM
Over me head using Ubuntu to set up them nodes. For are basic windows user which alot of us ade a guide would be better. May be simple for some but for me and others included it isn't.
pjcltd/Paul You thinking of providing this to make nodes cheaper? Be saving you money as well with all these ips your buying.
pjcltd/Paul You thinking of providing this to make nodes cheaper? Be saving you money as well with all these ips your buying.
im looking at it yes
but not should how much cheaper i can get at $1.5 a month
thanks
Paul
August 09, 2016, 03:14:10 PM
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.
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?
Not sure about vultr... but you can have multiple IP#s on the same interface. As long as traffic for them is being route there by your service provider. If your service provider uses ipv6, you can easily and cheaply get more IP numbers.
On my masternode hosts, I put several IP#s on my local interface "lo" and connect TOR to those local addresse.. Each Darknet instance darknet.conf will need a different setting for bind and rpcbind... For example can use 127.0.0.1 for masternode 1 and 127.0.0.2 for masternode 2 ... 127.0.0.254 if you have enough memory, cores and disk in one machine for that many masternodes.
I'll post a guide for putting setting up masternodes with TOR soonish...
August 09, 2016, 03:09:45 PM
Over me head using Ubuntu to set up them nodes. For are basic windows user which alot of us ade a guide would be better. May be simple for some but for me and others included it isn't.
pjcltd/Paul You thinking of providing this to make nodes cheaper? Be saving you money as well with all these ips your buying.
pjcltd/Paul You thinking of providing this to make nodes cheaper? Be saving you money as well with all these ips your buying.
im looking at it yes
but not should how much cheaper i can get at $1.5 a month
thanks
Paul
August 09, 2016, 03:04:11 PM
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.
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?
Not sure about vultr... but you can have multiple IP#s on the same interface. As long as traffic for them is being route there by your service provider. If your service provider uses ipv6, you can easily and cheaply get more IP numbers.
On my masternode hosts, I put several IP#s on my local interface "lo" and connect TOR to those local addresse.. Each Darknet instance darknet.conf will need a different setting for bind and rpcbind... For example can use 127.0.0.1 for masternode 1 and 127.0.0.2 for masternode 2 ... 127.0.0.254 if you have enough memory, cores and disk in one machine for that many masternodes.
I'll post a guide for putting setting up masternodes with TOR soonish...
August 09, 2016, 02:58:10 PM
Over me head using Ubuntu to set up them nodes. For are basic windows user which alot of us ade a guide would be better. May be simple for some but for me and others included it isn't.
pjcltd/Paul You thinking of providing this to make nodes cheaper? Be saving you money as well with all these ips your buying.
pjcltd/Paul You thinking of providing this to make nodes cheaper? Be saving you money as well with all these ips your buying.
August 09, 2016, 02:28:40 PM
Any ETA? I want to stakeeeeeeeeeeeeeeeeeeeeeee 
August 09, 2016, 02:21:07 PM
I see community is picking up the speed also it is self moderating I have also noticed we have nice breakdown between different types of people, investors, hardware hackers, many "legends" too,
friends! off to the sun! this is great
also it is self moderating I have also noticed we have nice breakdown between different types of people, investors, hardware hackers, many "legends" too, friends! off to the sun! this is great
August 09, 2016, 02:07:11 PM
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.
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?
A $5 vultr VPS instance is automatically assigned 1 x IPv4 Address and 1 x IPv6 Address - However, "You may use any IPs within the assigned prefix." - https://www.vultr.com/docs/configuring-ipv6-on-your-vps
So, 1 x $5 mo. VPS instance could run approximately 8 nodes (according to the script) as IPv6 (only) enabled nodes, because of CPU and RAM constraints.
~ If anyone wants a promo code to test the script at vultr - then send me a PM - I have a 'summer promo' aff. link code "For a Limited Time - Give $20, Get $30!" (although after it expires it reverts to the $5 free regular promo).
August 09, 2016, 01:58:34 PM
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.
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.
August 09, 2016, 01:22:55 PM
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.
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?
August 09, 2016, 12:06:42 PM
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.
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
August 09, 2016, 12:01:21 PM
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.
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.
Jump to: