|
I have posted some bounty work on the OP, please contact me if you intent to do the work, so i am aware so there isn't any double work being done. Please donate what you can.
Thanks,
s3v3n
|
|
|
|
|
sounds like you opened your external router port 51472 and your wallet is seeing many more peers. You can either close the port, or put listen=0 in your darknet.conf file. but you will have much better results with more peers.
|
|
|
|
|
was it 8 out going connections before, and now you have 8 out going and a bunch if incoming now?
|
|
|
|
why am i all of a sudden connecting to alot of ipv6 nodes? i am having trouble syncing off them and am getting stuck with windows controller wallet corrupting alot and i never connected to them before...
Nothing has changed on our end, IPv6 nodes have always been there. Did you enable IPv6 in your router recently? |
|
|
|
Yes we are here, Sorry for the low communications, I have been out of town at a wedding for a few days, but I am back now and we are working away..  |
|
|
|
anyone not past block 325101 needs to reboot their wallet and masternodes. everything should be good with masternode payments, we just found and patched a little speed bump.. |
|
|
|
|
looks more like the Dev has Dumped and left.. this coin needs some major fixing guys. coinswap to a smaller coincap, and way lower return, something like 2-3% a year. and add some features..
|
|
|
|
|
Any plans for this coin?? Really stagnant lately...
|
|
|
|
|
Any Plans for the coin now that it is relaunched??
|
|
|
|
I am still unable to launch a single masternode be it on linux or win. Always get that : 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? need more info, are you self hosting your IPv6 nodes? or are you hosting with someone? |
|
|
|
at this speed he could have written tor code from scratch  ... 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 |
|
|
|
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 : 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.. |
|
|
|
If anyone wants to buy a Darknet 'T' Shirt they are available here... http://tshirtprinting.grHe accepts DNET and BTC...  Would be Great if to come up with an original catchy slogan... |
|
|
|
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=<n>
-obfuscationrounds=<n>
-anonymizedarknetamount=<n>
-liquidityprovider=<n>
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. |
|
|
|
|
Please follow the examples in the OP for the .conf files
|
|
|
|
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. |
|
|
|
|
Still seeing many older wallet/node versions, Please update your versions asap...
|
|
|
|
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 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. |
|
|
|
|
EXCHANGES that have responded as being updated to v2.1.3.0
NovaExchange
Bittrex
Cryptopia
|
|
|
|
|
Show Posts
