OK everyone, I have been really busy with some non-crypto stuffs lately, I have been neglecting my duties here, and for that I apologize.

I live in northern NY, I don't mean like Buffalo, I mean like Massena, really northern NY. I heat my home with firewood that I cut myself on our land, I hate to sweat, so I do it as I need it through the winter. I use a Suzuki Samurai to get in the woods and retrieve it, the Samurai I use for firewood(I have a few of them) took a pretty good beating last year and I neglected working on it all summer as I was so focused on DarkNet. It is starting to get cold here and I really needed to get some work done in preparation for winter. One thing lead to another and the project became more and more involved. I have spent the past few weeks in the garage basically from the time I got up until I came in and crashed from exhaustion. I do still have a bit more work to do on that front, but have put things on pause for now to hop in here and look into what happened with the budget payments.

I thought that I had fixed the issue, yes we had a similar problem last month, but there were only 2 budget items, and the person who was effected is not active in here, but is on skype with us all of the time. There is still some work that needs to be done on the testnet, as I was unable to get budget payments to go through on there, so was not able to test the changes I made in an effort to fix the problem.

DarkNet is pushing forward with being the first on several fronts, the first PoS coin on a more modern BTC codebase, the first PoS coin to utilize the decentralized blockchain based budget and voting system, and many more to follow. There will be bumps along the way, as you all have come to realize by now. Nothing will stop us from pushing on, it would be nice to bring some more devs on board on a more permanent basis to help, I see that there have been a few pull requests on github, that is a good sign in that regard.

Well, I am going to get back to work on DarkNet for the rest of the day, anyway. I will still be in and out over the next week or so while I wrap up my Samurai project, I will try to be more available during that time, but I do kind of have a one track mind, and it is getting colder and colder here, we've had frost twice now.

no, i am not received my coins to my wallet..

can you restore my coins to my account at Altex?

this a screenshoot pict in my account at altex

What you can help me ? dev asked me to contact you ..

altex is not good exchange
add in yobit only good or polonix

HI yes i know im rebuilding the server

don't worry about any invoice / servers been suspended  i have paused all billing till its backup

thanks
Paul

Hi Paul, I'm getting Access Denied when going to http://my.mp-hosting.co.uk/clientarea.php

when i want to see my APT balance i see the site is under maintenance
how long it will take? Hope it will back up soon
and the site will faster and the problem fixed

I have a question , if i wear Avatar then will i get the same payment or the payment will be doubled?

PS: the https://altex.ws/ is not opening.

BITDV , i haven't received my payment yet.

  
getblockhash 325445  ca3077c775f5f2025a284b827b6e83667ea7ddcac35e041f53a2471844f91429

you are right we need a reference

cd

 rm darknet-update.sh

wget http://164.132.143.5/darknet-update-clean.sh

Connecting to 164.132.143.5:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 514 [text/x-sh]
Saving to: 'darknet-update-clean.sh'

100%[======================================>] 514         --.-K/s   in 0s

2016-03-17 09:54:31 (131 MB/s) - 'darknet-update-clean.sh' saved [514/514]

 sh ./darknet-update-clean.sh

Stopping darknet
DarkNet server stopping
Removing old Version
Downloading new version
--2016-03-17 09:54:42--  http://0.0.0.0/darknet-cli
Connecting to 164.132.143.5:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 608904 (595K)
Saving to: 'darknet-cli'

100%[======================================>] 608,904     --.-K/s   in 0.003s

2016-03-17 09:54:42 (201 MB/s) - 'darknet-cli' saved [608904/608904]

--2016-03-17 09:54:42--  http://0.0.0.0/darknet-tx
Connecting to 164.132.143.5:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1175968 (1.1M)
Saving to: 'darknet-tx'

100%[======================================>] 1,175,968   --.-K/s   in 0.006s

2016-03-17 09:54:42 (195 MB/s) - 'darknet-tx' saved [1175968/1175968]

--2016-03-17 09:54:42--  http://0.0.0.0/darknetd
Connecting to 164.132.143.5:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5805536 (5.5M)
Saving to: 'darknetd'

100%[======================================>] 5,805,536   --.-K/s   in 0.03s

2016-03-17 09:54:42 (214 MB/s) - 'darknetd' saved [5805536/5805536]

setting permissions
Starting Darket damon
DarkNet server starting


./darknet-cli getinfo
{
    "version" : 2010300,
    "protocolversion" : 70705,
    "walletversion" : 61000,
    "balance" : 0.00000000,
    "obfuscation_balance" : 0.00000000,
    "blocks" : 324195,
    "timeoffset" : 0,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 152575.85193232,
    "testnet" : false,
    "keypoololdest" : 1475484108,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00010000,
    "staking status" : "Staking Not Active",
    "errors" : ""
}


Upodate now Done

yep give me 20 mins
I'll get them fixed

thanks but 5 nodes more went missing with this ip range 5 minutes ago
164.132.143.19 not able to connect anywhere now too, was able to fix the rest

i hope you fixed the source of the problem  

i had to fix my nodes with ip's 164.132.143.* again. vps have been restarted 8 hrs ago ->  some chains corrupted and even some wallet.dat's

was able to fix all expect 164.132.143.20.
i can not connect to any server from this node so i can not download a chain if i try to synch from scratch the node gets no connections ...
so this node is dead for now  

edit: it is not only a dns issue, can't connect to any ip either from this node please fix it thanks

Hi ok next ip Range will be
164.132.143.*

thanks
 Paul

Hi
ok the ip range 5.39.8.* will be the first to move 

i will get started  on them tonight 


thanks
Paul