[ANN][DC] *NEW * DynamicCoin~ Pure Pos ~ Fair distribution ~ New wallet 1.0.2

[temple]

how to solve:

zerocoin/Accumulator.cpp:106:1: fatal error: opening dependency file obj/zerocoin/Accumulator.d: No such file or directory
compilation terminated.

[1715453126]

1715453126

[1715453126]

1715453126

[1715453126]

1715453126

[1715453126]

1715453126

[1715453126]

1715453126

[nearmiss]

how to solve:

zerocoin/Accumulator.cpp:106:1: fatal error: opening dependency file obj/zerocoin/Accumulator.d: No such file or directory
compilation terminated.

Using latest source:  mkdir -p obj/zerocoin && chmod +x leveldb/build_detect_platform

allowed me to compile. 

[Zisef]

Dev by you paying for some of the missing coins that is a great step for dynamic, and helping the community as well. Kudoss

[temple]

Dev by you paying for some of the missing coins that is a great step for dynamic, and helping the community as well. Kudoss

I think so , due to the wallet problem. I got so many orphans in my pool.

[xhash]

Hello everyone, I want to explain to you our point of view about the recent events with DC.

First of all I want to make clear, that I'm not running this pool on my own. We are a team of two admins and one web dev.
We also answer all our support mails, advertise, chat with users and as you may guess this pool is not our primary income, we all have jobs and responsibilities that we neglect to keep our users happy.
As the biggest pool on launch holding 1.3 GH/s without any issues, we spend the night monitoring the cron jobs and making sure everything goes smooth.
Sadly early in the morning around 7:00 GMT our hosting provider decided to stop our stratum server due the 3Gb/s DDOS attack.
We didn't get any customer support till 9:30, by than we managed to setup a new server and run it by ourselves. Most of our users reconnected and we a had around 800-900 MH/s on our pool.
We felt relieved and happy, that our efforts were not in vain. At that time our pool and multi-pool.eu were both holding around 95% of the whole network.
Everything was fine until we realised that the new wallet version 1.0.1 was depending on a single pnseed, dnsseed not set at all and because of poor nodes setup 98% of the network are mining on the wrong chain.

Splendid.

We decided to keep it quiet in order to save the coin. We tried to hotfix the new wallet version to sync with our node and validating this huge fork.
We almost managed .. meanwhile our pool was going up and down.
We were blamed all over this forum, compared with hooker's panties, while some of our fellow pool ops advertise themselves as stable pools running on the "correct" chain.
Finally when we switched off our stratum we got the dev attention being more than 1/2 of the network hashrate, with the help of our admins they managed to sync to the biggest fork, the one our pool and multi-pool.eu were mining.
So this whole thing end after 21 hours hard work and wallet version 1.0.2 was released.

I kindly asked the Dev twice to make a clear statement in here, because as the biggest pool we are taking all the blame.
Sorry, but "don't blame the pools" won't cut it!

Yes we didn't lost as much blocks as we would have, if the nodes were sync with the lesser chain(s). But our pool balance is negative and we have tons of pissed off users.
Our pool runs on donations ONLY !
We demand refund for us and our users ! You have good amount of premined coins that are not used for anything yet, this coin doesn't even have a block explorer !!!

Thank you.

xHash Team

[AgafDL]

I apologize for the harsh words in your direction.

[niteryder]

Hello everyone, I want to explain to you our point of view about the recent events with DC.

First of all I want to make clear, that I'm not running this pool on my own. We are a team of two admins and one web dev.
We also answer all our support mails, advertise, chat with users and as you may guess this pool is not our primary income, we all have jobs and responsibilities that we neglect to keep our users happy.
As the biggest pool on launch holding 1.3 GH/s without any issues, we spend the night monitoring the cron jobs and making sure everything goes smooth.
Sadly early in the morning around 7:00 GMT our hosting provider decided to stop our stratum server due the 3Gb/s DDOS attack.
We didn't get any customer support till 9:30, by than we managed to setup a new server and run it by ourselves. Most of our users reconnected and we a had around 800-900 MH/s on our pool.
We felt relieved and happy, that our efforts were not in vain. At that time our pool and multi-pool.eu were both holding around 95% of the whole network.
Everything was fine until we realised that the new wallet version 1.0.1 was depending on a single pnseed, dnsseed not set at all and because of poor nodes setup 98% of the network are mining on the wrong chain.

Splendid.

We decided to keep it quiet in order to save the coin. We tried to hotfix the new wallet version to sync with our node and validating this huge fork.
We almost managed .. meanwhile our pool was going up and down.
We were blamed all over this forum, compared with hooker's panties, while some of our fellow pool ops advertise themselves as stable pools running on the "correct" chain.
Finally when we switched off our stratum we got the dev attention being more than 1/2 of the network hashrate, with the help of our admins they managed to sync to the biggest fork, the one our pool and multi-pool.eu were mining.
So this whole thing end after 21 hours hard work and wallet version 1.0.2 was released.

I kindly asked the Dev twice to make a clear statement in here, because as the biggest pool we are taking all the blame.
Sorry, but "don't blame the pools" won't cut it!

Yes we didn't lost as much blocks as we would have, if the nodes were sync with the lesser chain(s). But our pool balance is negative and we have tons of pissed off users.
Our pool runs on donations ONLY !
We demand refund for us and our users ! You have good amount of premined coins that are not used for anything yet, this coin doesn't even have a block explorer !!!

Thank you.

xHash Team

I'm with xHash on this.  We have -2,083.88213266 in, or lack of, in our pool wallet and the payout process can't run without coins in the wallet.

[sillyputti]

Hello everyone, I want to explain to you our point of view about the recent events with DC.

First of all I want to make clear, that I'm not running this pool on my own. We are a team of two admins and one web dev.
We also answer all our support mails, advertise, chat with users and as you may guess this pool is not our primary income, we all have jobs and responsibilities that we neglect to keep our users happy.
As the biggest pool on launch holding 1.3 GH/s without any issues, we spend the night monitoring the cron jobs and making sure everything goes smooth.
Sadly early in the morning around 7:00 GMT our hosting provider decided to stop our stratum server due the 3Gb/s DDOS attack.
We didn't get any customer support till 9:30, by than we managed to setup a new server and run it by ourselves. Most of our users reconnected and we a had around 800-900 MH/s on our pool.
We felt relieved and happy, that our efforts were not in vain. At that time our pool and multi-pool.eu were both holding around 95% of the whole network.
Everything was fine until we realised that the new wallet version 1.0.1 was depending on a single pnseed, dnsseed not set at all and because of poor nodes setup 98% of the network are mining on the wrong chain.

Splendid.

We decided to keep it quiet in order to save the coin. We tried to hotfix the new wallet version to sync with our node and validating this huge fork.
We almost managed .. meanwhile our pool was going up and down.
We were blamed all over this forum, compared with hooker's panties, while some of our fellow pool ops advertise themselves as stable pools running on the "correct" chain.
Finally when we switched off our stratum we got the dev attention being more than 1/2 of the network hashrate, with the help of our admins they managed to sync to the biggest fork, the one our pool and multi-pool.eu were mining.
So this whole thing end after 21 hours hard work and wallet version 1.0.2 was released.

I kindly asked the Dev twice to make a clear statement in here, because as the biggest pool we are taking all the blame.
Sorry, but "don't blame the pools" won't cut it!

Yes we didn't lost as much blocks as we would have, if the nodes were sync with the lesser chain(s). But our pool balance is negative and we have tons of pissed off users.
Our pool runs on donations ONLY !
We demand refund for us and our users ! You have good amount of premined coins that are not used for anything yet, this coin doesn't even have a block explorer !!!

Thank you.

xHash Team

i'm with xhash on this one.  out of all the places i've mined at, they got the best interface imo, don't even need to recreate an account for different coins.  it seems like they are always getting blamed for something.  i guess they must be doing something right.

the coin itself is still just shaky.

i lost some coins during the down time at xhash too and hope the devs do consider.

[gadado]

what I don't get..

Do ppl mining in a pool never check the mined block list of a pool? Not even in the first hour?
When a pool starts to get every block you can already be pretty sure it forked.


Anyway I had some more luck. The pool I choosed had almost 1 hour start delay and after that the hash rate was very low (2Mh to 5Mh)
doe to missing ppl but it worked!!

However half the hours I was in a second pool that worked too.

All in all I run 2Mh for 23 hours and it generated me 600 coins.. slightly more than planed (should have  gotten 552)

So it looks to me that the POW really worked as designed !

How is about the others?

[DrFingol]

XHash has been nothing but honorable thus far. I'm with them aswell.

[Ferris419]

I'm with xhash as well. I think it would be a very honorable/trustworthy action of the dev to pay forward some of the premine to the lost coins.

[jjc6676]

I have Coins paid from xhash to my wallet.

Xhash, if you would be so kind to post your wallet addy I would like to send them back to you. I love your pool and do not think your should be in the negative.

[Antebellum]

Hello everyone, I want to explain to you our point of view about the recent events with DC.

First of all I want to make clear, that I'm not running this pool on my own. We are a team of two admins and one web dev.
We also answer all our support mails, advertise, chat with users and as you may guess this pool is not our primary income, we all have jobs and responsibilities that we neglect to keep our users happy.
As the biggest pool on launch holding 1.3 GH/s without any issues, we spend the night monitoring the cron jobs and making sure everything goes smooth.
Sadly early in the morning around 7:00 GMT our hosting provider decided to stop our stratum server due the 3Gb/s DDOS attack.
We didn't get any customer support till 9:30, by than we managed to setup a new server and run it by ourselves. Most of our users reconnected and we a had around 800-900 MH/s on our pool.
We felt relieved and happy, that our efforts were not in vain. At that time our pool and multi-pool.eu were both holding around 95% of the whole network.
Everything was fine until we realised that the new wallet version 1.0.1 was depending on a single pnseed, dnsseed not set at all and because of poor nodes setup 98% of the network are mining on the wrong chain.

Splendid.

We decided to keep it quiet in order to save the coin. We tried to hotfix the new wallet version to sync with our node and validating this huge fork.
We almost managed .. meanwhile our pool was going up and down.
We were blamed all over this forum, compared with hooker's panties, while some of our fellow pool ops advertise themselves as stable pools running on the "correct" chain.
Finally when we switched off our stratum we got the dev attention being more than 1/2 of the network hashrate, with the help of our admins they managed to sync to the biggest fork, the one our pool and multi-pool.eu were mining.
So this whole thing end after 21 hours hard work and wallet version 1.0.2 was released.

I kindly asked the Dev twice to make a clear statement in here, because as the biggest pool we are taking all the blame.
Sorry, but "don't blame the pools" won't cut it!

Yes we didn't lost as much blocks as we would have, if the nodes were sync with the lesser chain(s). But our pool balance is negative and we have tons of pissed off users.
Our pool runs on donations ONLY !
We demand refund for us and our users ! You have good amount of premined coins that are not used for anything yet, this coin doesn't even have a block explorer !!!

Thank you.

xHash Team

Totally agree, not mined this coin as much as others proberbly but your pool is awesome, and use it for other coins with great result, quick responses from support when needed, all in all best pool i mined at! Keep up the great work, your awesome!

[Langly]

Vote for this coin on Mintpal https://www.mintpal.com/voting currently at the bottom of the list. And remember, you can vote every hour.

Edit: Remember unregistered users can vote 3 times an hour, registered 6.

[Mesterlovesz74]

Ok, just to make it clear, dark clouds are past tens now, and we can mine at every pool, we can get our coins, business as usual???

[ggudvin]

Xhash guys, you rock, keep up the work, I support you and recommend to all.

[multi-pool.eu]

http://dc.multi-pool.eu

DDOS protection and PPLNS!

Come and mine with us!!!
stable and on the correct fork

http://dc.multi-pool.eu

[Speedie]

<Important Stuff>

First I apologize for the "up and down like a hooker's knickers" comment. It's an English colloquialism, no offence was intended by it, and I hope that you didn't take it as anything other than a lighthearted comment in the middle of a trying situation for all involved.

There's no reason that you should be out of pocket for this, so if the dev doesn't make you whole from the pre-mine funds please let me know via PM. I'll be happy to chip in 500 DC towards your negative balance.

[ozie]

how to solve:

zerocoin/Accumulator.cpp:106:1: fatal error: opening dependency file obj/zerocoin/Accumulator.d: No such file or directory
compilation terminated.

mkdir obj/zerocoin 

[tylerderden]

my wallet has been stuck on 2847 blocks remaining for a few hours...latest version.