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

Hi we know and we are working on it

Thanks
Paul

2 different laptops. same message on chrome.

Just tried with internet explorer as well


There is a problem with this website’s security certificate.
 


 
   
 
 

The security certificate presented by this website was not issued by a trusted certificate authority.





Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server. 
   
We recommend that you close this webpage and do not continue to this website. 

I don't get that message.

will the exe update be done automatically with a restart of all nodes on mp hosting? Or will this require some user involvement to start them again?

also when trying to access your site this is coming up :

Your connection is not private

Attackers might be trying to steal your information from my.mp-hosting.co.uk (for example, passwords, messages, or credit cards). NET::ERR_CERT_AUTHORITY_INVALID
  Automatically report details of possible security incidents to Google. Privacy policy
Back to safetyHide advanced
This server could not prove that it is my.mp-hosting.co.uk; its security certificate is not trusted by your computer's operating system. This may be caused by a misconfiguration or an attacker intercepting your connection.

Hey everyone. The new wallet v1.0.2.0 is up on https://github.com/Darknet-Crypto/Darknet/releases now for all of you self compilers. I am working to get the precompiled binaries up there now, they should all be available by the end of the day.

Changes include:
Fixed the block rewards, at block 86400 miners will get 175 DNET and Masternode will get 50 DNET, as was supposed to be the case starting at block 43200.
Added a checkpoint.
Changed Obfuscate to Obfuscation.
Fixed the time the final budget is submitted, it is now 2 days before the superblock.
Enabled Obfuscation by default, the new default is to keep 1000 DNET mixed with 8 rounds, there will be a very small transaction fee associated with this, we are talking like .0002 DNET. We need this in order for mixing to work at all.
Fixed the transifex URL, where users can contribute to translations.
Added seednodes, shouldn't need to add nodes in the darknet.conf anymore.
Along with a lot of cleanup of comments in the code.

This is a mandatory update, everyone will need to be on it by block 86400, the earlier the better. There is a function that enables only sending Masternode payments to updated Masternodes. If you run "spork show" you will see that the output for SPORK_10_MASTERNODE_PAY_UPDATED_NODES is 1458752907. That is about a week from today, I just changed it now, so that everyone will continue receiving Masternode payments as usual. If you haven't upgraded your Masternode wallet by then you will start to miss payments.

thanks!)

Good Point. Should have just said that lol. Easier than the copy/paste

nano /Users//Library/Application\ Support/DarkNet/darknet.conf

It's better to be safer than sorry so always ONLY use the addnode IP addresses listed in the OP for your conf file whenever possible.

Hi, how i can open the conf file on mac? i tried top menu (instrument -> open  conf file) but it doesnt work.

Add this to your conf file

addnode=31.6.30.115
addnode=217.240.107.120
addnode=109.172.55.170
addnode=68.104.0.118
addnode=24.104.248.48
addnode=67.3.92.178
addnode=86.122.138.192
addnode=76.105.204.52
addnode=74.132.6.75
addnode=173.30.131.78
addnode=68.7.186.217
addnode=188.230.158.70
addnode=162.213.154.31
addnode=173.245.148.70
addnode=151.80.206.104
addnode=24.254.142.135
addnode=74.132.6.75
addnode=67.225.110.88
addnode=104.200.151.6
addnode=37.187.129.166
addnode=75.86.207.37
addnode=82.210.172.238
addnode=109.201.154.180
addnode=75.102.135.212
addnode=178.33.209.212
addnode=94.22.185.125
addnode=212.112.119.140
addnode=98.108.241.238
addnode=115.186.110.172
addnode=199.7.156.129
addnode=2.220.147.216
addnode=81.191.41.44
addnode=52.11.97.205
addnode=85.1.100.186
addnode=92.77.76.244
addnode=73.237.212.111
addnode=y5kcscnhpygvvnjn.onion:989
addnode=5bmhtjvn2jvwpiej.onion:989
addnode=pyfdxkazur3iib7y.onion:989
addnode=ok3ym5zy6m5klimk.onion:989
addnode=i6vpvzk2jxuqqs5f.onion:989
addnode=bgdhpb76fkbw5fmg.onion:989
addnode=gtlqzb5zbws5di7g.onion:989
addnode=f7j2m26rptm5f7af.onion:989
addnode=dnetzj6l4cvo2fxy.onion:989
addnode=s3v3n7xhqafg6sb7.onion:989

we now have 3 servers  in 3 different locations in Europ
our next server will be in Canada
as its very important to spread them about.


thanks
Paul

How to Sync Dark Net. As it shows "No Block Source Available"

I downloaded and run windows wallet.

Yes this would be much easier.... probably need more hosts too can't have all the masternodes on one vps provider right?

I don't know its technical possibility but it'd be great if there was a scrypt like;

When I pay and buy the node,

and just enter the necessary variables (username, pw, privkey) through the website, select options tor/ip4 etc.

and the scrypt do the rest and build the dnet mnode

So it'd be very simple to build a mnode and almost anyone'd be able to build one.

Is that possible?

-----

And for the wallet part;

we'd just choose the transaction from coin control section and click build node and enter node ip,

a scrypt on wallet configures darknet.conf and masternode.conf automatically by generating priv key itself, and get the outputs from selected transaction and name alias same as wallet name.

---

So lots of mnodes'd be build easily. I know it's easy to say, and I don't know if it's too hard to do, I'm not the tech man

The script posted by @GJones offers some good additional security features / settings for a linux vps, however users just running the script will most likely encounter some confusion if they run it, which probably isn't ideal for @pjcltd as a hosting provider though.

...

I've already posted a bunch of useful info. and I'm mostly interested in DNET purely from a network anonymity and privacy perspective.

Individual user security and/or third party service provision is not really of my concern.

Whilst most of the set-up procedure could be automated with a script, certain aspects of installing and running Masternode's on a VPS require some user knowledge and independent choice regarding security etc.,

For network diversity, Masternode operators should really choose to host multiple nodes with multiple service providers in different geographical locations, where possible.

- https://www.youtube.com/watch?v=TPWucqna9Eg    
  

The flaws that my script is for are the first thing your typical script kiddie is going to have a script for. If you have something behind an IP, they are going to start with these basics. I'm not revealing anything about the security here that isn't assumed by an attacker before he even starts.

I'm glad it's getting looked at. My script might be for "intermediate users". It also is going save mp-hosting money on things like bandwidth and power if they adopt a couple of the changes.

ok so if we can all work together and come up with a better system for everyone i will give away a few master nodes  to them that help


thanks
Paul

always good to have a 3rd person who knows what they on about lol. Alot of clever minds involved in Dnet,,,Good times ahead

Disabling Bash_History on a Linux Cloud VPS is normally a good idea, in terms of security.

- http://mewbies.com/how_to_disable_bash_history_or_limit_tutorial.html

" QUICK METHOD:
`````````````
Quick method to completely disable your own .bash_history, without reading any further:

Remove the file:

rm ~/.bash_history -rf

Clear your current history stored in RAM:

history -c

Change your settings:

export HISTFILESIZE=0
export HISTSIZE=0
unset HISTFILE

Logout, login, done. "


Already suggested installing and properly configuring Fail2ban + iptables as a good option for blocking SSH 'default' port scanning / attacks etc.,

This method can also provide some basic DDoS protection.

Reference: Set-up Fail2ban - an intrusion prevention framework;
- https://bitcointalksearch.org/topic/m.14037105

Reference: iptables (strict) Linux VPS firewall rules;
- https://bitcointalksearch.org/topic/m.14038073

This thread is fast becoming linux security 101.