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

coins4lunch

full member

Activity: 255

Merit: 100

Am I EVIL? Yes I am

Quote from: B1tUnl0ck3r on October 03, 2016, 08:19:58 AM

I am still unable to launch a single masternode be it on linux or win. Always get that :

Quote

Not capable masternode: Could not connect to [IPV6]:51472

I edited the masternode.conf with the same ipv6, I edited the darknet.conf with masternodeaddress the same way.

I am totally lost. And I don't know what to try. I did exactly like in the OP post. Could some one using IPV6 please post his masternode.conf and darknet.conf settings here?

This may work for you (if you compile from source)...

In net.cpp, comment out 2 lines, starting line 398:

Code:

//if (IsLocal(addrConnect) && !obfuScationMaster)
//    return NULL;

now recompile

B1tUnl0ck3r

sr. member

Activity: 854

Merit: 277

liife threw a tempest at you? be a coconut !

I am still unable to launch a single masternode be it on linux or win. Always get that :

Quote

Not capable masternode: Could not connect to [IPV6]:51472

I edited the masternode.conf with the same ipv6, I edited the darknet.conf with masternodeaddress the same way.

I am totally lost. And I don't know what to try. I did exactly like in the OP post. Could some one using IPV6 please post his masternode.conf and darknet.conf settings here?

4x13

legendary

Activity: 1078

Merit: 1011

Quote from: B1tUnl0ck3r on October 01, 2016, 03:09:31 PM

at this speed he could have written tor code from scratch Cool

... how many version of dnet went since he started? lol

He is a busy guy, lots going on with him. The issue was Tor updated their stuff shortly after he finished his guide and it needed updating again

B1tUnl0ck3r

sr. member

Activity: 854

Merit: 277

liife threw a tempest at you? be a coconut !

at this speed he could have written tor code from scratch Cool

... how many version of dnet went since he started? lol

4x13

legendary

Activity: 1078

Merit: 1011

Quote from: B1tUnl0ck3r on October 01, 2016, 01:53:09 PM

I am trying to build a little tor masternode guide... here it is at this stage... and it doesn't work yet.

Darknet Masternode with tor hidden service guide :

1. dl torbrowser, launch once close.
2. create directory in tor browser like dnet hidden service
3. edit tor.rc in tor browser data directory and add :

Quote

HiddenServiceDir (your freshly created directory address) C:\Tor Browser\Browser\dnet hidden service
HiddenServicePort 51472 127.0.0.1:51472

4. get into directory from file hostname your onion address.
5. edit darknet.conf with

masternodeaddress=xxx.onion:51472
externalip=xxx.onion
onion=127.0.0.1:9050
onlynet=tor
listen=1
discover=0

(source : https://www.dash.org/forum/threads/3-how-to-run-a-local-dash-tor-hidden-service-advanced-setup-high-privacy-own-onion-address.4225/ )

Then concerning this masternodeaddress parameters, is it possible to add an ipv6? and if yes temporary or permanent one? I tried both and it doesn't solve the problem... what happened to the wallet since this last update... not cool.

There already is a working guide, if you read back through the posts. We will post our official guide, when BitcoinFX finishes it up, there will be a few different option based on how you want it setup, so when it's ready i will announce it as it seems many are interetsed..

We will also be wanting some I2p nodes as well..

q327K091

legendary

Activity: 1792

Merit: 1010

update: all 75 master nodes are operating nominally

B1tUnl0ck3r

sr. member

Activity: 854

Merit: 277

liife threw a tempest at you? be a coconut !

I am trying to build a little tor masternode guide... here it is at this stage... and it doesn't work yet.

Darknet Masternode with tor hidden service guide :

1. dl torbrowser, launch once close.
2. create directory in tor browser like dnet hidden service
3. edit tor.rc in tor browser data directory and add :

Quote

HiddenServiceDir (your freshly created directory address) C:\Tor Browser\Browser\dnet hidden service
HiddenServicePort 51472 127.0.0.1:51472

4. get into directory from file hostname your onion address.
5. edit darknet.conf with

masternodeaddress=xxx.onion:51472
externalip=xxx.onion
onion=127.0.0.1:9050
onlynet=tor
listen=1
discover=0

(source : https://www.dash.org/forum/threads/3-how-to-run-a-local-dash-tor-hidden-service-advanced-setup-high-privacy-own-onion-address.4225/ )

Then concerning this masternodeaddress parameters, is it possible to add an ipv6? and if yes temporary or permanent one? I tried both and it doesn't solve the problem... what happened to the wallet since this last update... not cool.

4x13

legendary

Activity: 1078

Merit: 1011

If anyone wants to buy a Darknet 'T' Shirt they are available here...

http://tshirtprinting.gr

He accepts DNET and BTC... Wink

Would be Great if to come up with an original catchy slogan... Wink

DRPD

legendary

Activity: 1148

Merit: 1001

check your nodes if you are on mp-hosting. some of my vps have been restarted for a unknown reason and the nodes where missing.

https://bitcointalksearch.org/topic/m.16419692

have a nice weekend all

q327K091

legendary

Activity: 1792

Merit: 1010

update: acquired around 50K Dnet, 5 new master nodes are coming online shortly, previous remaining all 70 but one has failed and had to be re-synced but I expected that, all producing payouts, dont see much inventory on bittrex if I wanted to press towards 100 master nodes (was a goal at one point) is becoming much tougher ,50K at the price level I wanted I simply could not resist..

cgt99

full member

Activity: 275

Merit: 104

Quote from: StakeBox on September 30, 2016, 01:26:17 PM

Quote from: B1tUnl0ck3r on September 30, 2016, 09:49:42 AM

Quote from: cgt99 on September 28, 2016, 09:13:37 AM

I cant get masternode started with new version 2.1.3

Windows standalone MN on Windows 7 64bit.

"Not capable masternode: Could not connect to xx.xx.xxx.xx:51472"
Fully connected with other peers both In and Out.

Switching back to version 2.1.2.3 and masternode starts without issue:
"Masternode successfully started"

Didnt have this issue with the previos upgrades

I am in the same boat as cgt99. win7-64 same error message. I tried sync from scratch, no improvement.

my masternode.conf is empty (only the example), I didn't need to configure it with previous dnet version. If I switch back to the previous version, the masternode works perfectly.

However staking is working, it's specifically the masternode, the little lock icon never appears (tried to create new masternode too without success).

What should I do? any advices?

Hey guys, sorry I must have missed cgt99's message the other day, I can't stress enough how much better help you can get in skype or slack. I just played around for a minute setting up a local masternode, I saw the same error, I fixed it with the "masternodeaddr=XXX.XXX.XXX.XXX:51472" option in my darknet.conf. Give it a go and let us know how you get on with it.

I always had the line masternodeaddr=xxx.xxx.xxx.xxx:51472 in the darknet.conf

As i said it works perfect with the binaries from version 2.1.2.3

Fully connected with 18 inbounds an 8 outbound, canyouseeme.org reports succes for port 51472.

from debug.log:
CActiveMasternode::ManageStatus() - Checking inbound connection to 'xxx.xxx.xxx.xxx:51472'
CActiveMasternode::ManageStatus() - not capable: Could not connect to xxx.xxx.xxx.xxx:51472

I get the exact same result when trying version. 2.1.3 on second computer with other IP range and other router.

This isnt a conf issue i think.
What about that check wallet is doing for "inbound connection"?

4x13

legendary

Activity: 1078

Merit: 1011

Quote from: B1tUnl0ck3r on September 30, 2016, 02:39:26 PM

Hello Stakebox,

Masternode successfully started

thank you very much! I wait for the first payment to confirm it all but it seems to have solve the issue!!!

as mine is a local masternode on the local wallet I added :

masternodeaddr=127.0.0.1:51472 in darknet.conf.

So I saw that there are a lot of new command line in the wallet... is there a way to have obfuscation on a local wallet with a masternode running at the same time?

like those?

Obfuscation options:
-enableobfuscation=
-obfuscationrounds=
-anonymizedarknetamount=
-liquidityprovider=

Those commands have been their from the beginning. You node will get band from the network using your loopback address, you need to use your public IP address for that.

B1tUnl0ck3r

sr. member

Activity: 854

Merit: 277

liife threw a tempest at you? be a coconut !

Hello Stakebox,

Masternode successfully started

thank you very much! I wait for the first payment to confirm it all but it seems to have solve the issue!!!

as mine is a local masternode on the local wallet I added :

masternodeaddr=127.0.0.1:51472 in darknet.conf.

So I saw that there are a lot of new command line in the wallet... is there a way to have obfuscation on a local wallet with a masternode running at the same time?

like those?

Obfuscation options:
-enableobfuscation=
-obfuscationrounds=
-anonymizedarknetamount=
-liquidityprovider=

4x13

legendary

Activity: 1078

Merit: 1011

Please follow the examples in the OP for the .conf files

StakeBox

full member

Activity: 226

Merit: 100

Quote from: B1tUnl0ck3r on September 30, 2016, 09:49:42 AM

Quote from: cgt99 on September 28, 2016, 09:13:37 AM

I cant get masternode started with new version 2.1.3

Windows standalone MN on Windows 7 64bit.

"Not capable masternode: Could not connect to xx.xx.xxx.xx:51472"
Fully connected with other peers both In and Out.

Switching back to version 2.1.2.3 and masternode starts without issue:
"Masternode successfully started"

Didnt have this issue with the previos upgrades

I am in the same boat as cgt99. win7-64 same error message. I tried sync from scratch, no improvement.

my masternode.conf is empty (only the example), I didn't need to configure it with previous dnet version. If I switch back to the previous version, the masternode works perfectly.

However staking is working, it's specifically the masternode, the little lock icon never appears (tried to create new masternode too without success).

What should I do? any advices?

Hey guys, sorry I must have missed cgt99's message the other day, I can't stress enough how much better help you can get in skype or slack. I just played around for a minute setting up a local masternode, I saw the same error, I fixed it with the "masternodeaddr=XXX.XXX.XXX.XXX:51472" option in my darknet.conf. Give it a go and let us know how you get on with it.

B1tUnl0ck3r

sr. member

Activity: 854

Merit: 277

liife threw a tempest at you? be a coconut !

Quote from: cgt99 on September 28, 2016, 09:13:37 AM

I cant get masternode started with new version 2.1.3

Windows standalone MN on Windows 7 64bit.

"Not capable masternode: Could not connect to xx.xx.xxx.xx:51472"
Fully connected with other peers both In and Out.

Switching back to version 2.1.2.3 and masternode starts without issue:
"Masternode successfully started"

Didnt have this issue with the previos upgrades

I am in the same boat as cgt99. win7-64 same error message. I tried sync from scratch, no improvement.

my masternode.conf is empty (only the example), I didn't need to configure it with previous dnet version. If I switch back to the previous version, the masternode works perfectly.

However staking is working, it's specifically the masternode, the little lock icon never appears (tried to create new masternode too without success).

What should I do? any advices?

Quote from: 4x13 on September 29, 2016, 02:06:57 PM

Quote from: berron on September 29, 2016, 01:18:49 PM

Quote from: 4x13 on September 29, 2016, 11:24:12 AM

Quote from: berron on September 29, 2016, 11:15:15 AM

Quote from: jakiman on September 29, 2016, 07:22:44 AM

I have now updated all my masternodes & wallets to v2.1.3.0.

It was a very easy and smooth upgrade. Had no issues whatsoever.

DNET is getting more mature and resilient over time! Love it. Great work devs!

Same here, all my MN's are already paying and I'm starting to stake the aprox. expected amount of blocks, so for the moment everything seems to be right. Only thing is that I continue having the impression obfuscation never pass from 87 % (5000 Dnet/4 rounds here), but maybe only a personal impression.

Salute

The issue is the higher the rounds, the more people that are required for you to be able to freshly swap coins with. which is why it is taking so long. I am doing 10k/8 rounds and have been at 39% for quite awhile. As the network grows, it should become a much faster process.

Oh, thank you, now I understand it. So obfuscation speed, quantity can be also used as a pseudoindicator of the waelth of the network. Good.

Well, or at least of the people would OPT in to participate.

I tried obfuscation, and effectively it's a little bit slow. Sadly I can't run it on the same wallet as a masternode. Or is there an option? Because the daemon says deactivate when masternode is activated.

LemonAndFriesOne

legendary

Activity: 1050

Merit: 1000

Quote from: 4x13 on September 30, 2016, 12:06:51 AM

Quote from: LemonAndFriesOne on September 29, 2016, 11:12:22 PM

Quick question, what are the developments going on for DNET in the future?

I know right now the rolling out an update is priority, but what tech will convince people to use DNET for their transactions?

We are working on a trust-less anon transaction which will become the primary transaction for DarkNet.

Good idea, I will watch and wait. I'm curious to how it will be implemented.

4x13

legendary

Activity: 1078

Merit: 1011

Quote from: LemonAndFriesOne on September 29, 2016, 11:12:22 PM

Quick question, what are the developments going on for DNET in the future?

I know right now the rolling out an update is priority, but what tech will convince people to use DNET for their transactions?

We are working on a trust-less anon transaction which will become the primary transaction for DarkNet.

LemonAndFriesOne

legendary

Activity: 1050

Merit: 1000

Quick question, what are the developments going on for DNET in the future?

I know right now the rolling out an update is priority, but what tech will convince people to use DNET for their transactions?

4x13

legendary

Activity: 1078

Merit: 1011

Still seeing many older wallet/node versions, Please update your versions asap...

Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 311. (Read 782375 times)