please in preparation of trigger which will happen in around 24 hours

all miners go solo mining

and wait until pools after trigger confirm that they adapted  configurations

before u consider if u wana go pool mining again

for any 100 mhash or more miner i strong suggest u stay solo mining

danbi pool forked
check https://chainz.cryptoid.info/dmd/ to see if u are on main chain

- DEFAULT configuration that help network relay data and act as a node

Example entries in the config file:

listen=1
noirc=1
#foundation nodes
addnode=193.68.21.19
addnode=54.191.208.14
addnode=54.255.133.30
addnode=54.86.164.216
#community nodes 2015.04.10
#NineEleven
addnode=193.136.97.30
addnode=193.136.96.30
bantime=3600


- OPTIONAL configuration (only pools and very big solo miners/staking wallets)

Example entries in the config file:

listen=0
noirc=1
#foundation nodes
connect=193.68.21.19
connect=54.191.208.14
connect=54.255.133.30
connect=54.86.164.216
#communitynodes 2015.04.10
#NineEleven
connect=193.136.97.30
connect=193.136.96.30
bantime=3600

nice

after we reached new specs with faster pos and slower pow
it would be good u try if u could attack

a friendly security check

im pretty sure u cant do anything more than increase pow diff

u use fpga? ór sitting on a warehouse full GPU?

nice guys i see u prepare already for trigger and most guys go solo mining

also more people support with listen=1 config and act as  block relay nodes

u have to check ur cpu (the core where dmd wallet runs on)
if u hit 100%  u need to adapt ur
maxconnections=50
(or 40 30 20 until u stay below 100%)
value

(important is to understand a node with many connections but 100% cpu load is adding more bad than good to network
because it lag in relay info and create confusion in network)

i think maxconnections=20 is save for like any cpu

i myself run maxconnections=100 and have like 50-70 wallets connected to me all day long


this also show that our network increase on good state nodes

from cryptsy we got feedback they need some more hours most likely in the evening they are done

they did not only sync from zero but also run maximum detail scan over that chain again

its very good cryptsy act in such a professional and quality securing way

only 2 days to 1000000 total coin trigger!

prepare for warp!



lets see what await us on the other side 

not everyone

u said its not productive for u and i give a way u can make it productive

yes dmd need some miners and yes this will be miners who dont look mainly for profit

i know at least 500 mhash in user hand who would always mine dmd no matter how low the rewards are or how many blocks go orphan

but i know we cant request that from every miner

if we after reduction are able to hold like 1-2 ghash miningrate im happy

its clear lot people will leave and must leave or everyone mining would mine at a big loss

2 ghash is still a nice hashrate only very big farms can deliver that

its like 80x amd 290 gpu

so some troublemaker alone wont have easy access to that

and our coin isnt vulnerable to 51% (special after 1000000 total coins when pos is on same blocktime with pow)

what we did experienced last few days isnt a 51% issue its a network overload issue with injection of bad blocks

which all got rejected but still created lot of work

BUT close at trigger and until pools confirmed to work after trigger
we ask everyone who can to switch to solo mining
thx for support

mine something more profitable sell it and buy dmd until network situation relax

- DEFAULT configuration that help network relay data and act as a node

Example entries in the config file:

listen=1
noirc=1
#foundation nodes
addnode=193.68.21.19
addnode=54.191.208.14
addnode=54.255.133.30
addnode=54.86.164.216
#community nodes 2015.04.10
#NineEleven
addnode=193.136.97.30
addnode=193.136.96.30
bantime=3600


- OPTIONAL configuration (only pools and very big solo miners/staking wallets)

Example entries in the config file:

listen=0
noirc=1
#foundation nodes
connect=193.68.21.19
connect=54.191.208.14
connect=54.255.133.30
connect=54.86.164.216
#communitynodes 2015.04.10
#NineEleven
connect=193.136.97.30
connect=193.136.96.30
bantime=3600

we can explain actual POW and POS situation like this

because network overloaded in sort out bad blocks and main nodes nearly always at 100% cpu load

this create a situation where multiple blocks compete to be the next one found

just because the selection process in network what is the next block is delayed

but its clear only one can be the next one
so a lot blocks orphan minting/mining

(this is what people did say their found blocks where overwritten
because they didnt propagate over majority of network and their wallet reorg back to join the majority
normal network make this less visible because a orphan would be easy visible but at actual situation it can need some time until wallet discover this block made it not into the main chain and then they remove it and accept the real block (this is called a reorg automated fix of local blockchain content))

less people mining and minting is less competition
(a pool here just count as one wallet so we suggest solomine if u have a real big hashrate but use a pool example donkeypool is u have medium or low hashrate)

less wallets online is less spread of block all around

less people sync their blockchains is less load

once network load normalize everything will work smooth like the last half year

then people can turn on their wallets again

there is no reason to have a wallet online now other than

try to be a relay node
try to solomine
dont have wallet open for POS now
u can pos later u lose nothing...


 ot valuable data got gathered by us and we will work on improvements in wallet code
in the area performance optimisatzion CPU useage

to reduce the chance such stuff happens again
no matter what crap got put in circulation in network
it should not be able eat up all wallet resources and have impact on normal operation

as always every attack or lets call it incident in the end make dmd diamond stronger

multiple times tested in the past each time leading to improvements
this test again will just increase our network setup stability and wallet code optimisatzion as result

here we have the problem
a nice network produce normal load
but a bad network create lot load
even a secure code wallet can lead to instabilities if good nodes just overworked to give good answers in time

the situation will normalize after some time when network get rid of the bad blocks

but we got some homework to do for code optimisation that security checks (which are good and needed)
and other wallet code is optimized for lowest possible cpu load and still fullfil their task

for now more backbone nodes will still help
10 nodes have a higher chance one respond in time than 4 nodes...

normal message for solo mining

for a node to relay data and support the network thats the ideal config
how is ur cpu load (the core where wllet run not over all cores)? u get lot connections?

please post only ur nodes if u can maintain them and the IP is static

nodes that fullfill that requirements we will add to the list

- DEFAULT configuration that help network relay data and act as a node

Example entries in the config file:

listen=1
noirc=1
#foundation nodes
addnode=193.68.21.19
addnode=54.191.208.14
addnode=54.255.133.30
addnode=54.86.164.216
#community nodes 2015.04.10
#NineEleven
addnode=193.136.97.30
bantime=3600


- OPTIONAL configuration (only pools and very big solo miners/staking wallets)

Example entries in the config file:

listen=0
noirc=1
#foundation nodes
connect=193.68.21.19
connect=54.191.208.14
connect=54.255.133.30
connect=54.86.164.216
#communitynodes 2015.04.10
#NineEleven
connect=193.136.97.30
bantime=3600

http://dmd.donkeypool.com:808/

is up and running as alternative pool

support him

or go solo mining

every helping hand is welcome

we will just gather a list of nodes

where foundation nodes AND community nodes are listed

and in time like this where our foundation nodes are overloaded we suggest to use the community nodes in conf too

at normal times its not needed to add them in conf because u will find them as peers anyway

a goal for future will be to distribute a good nodelist without need to add them in conf file always

a clear visible development goal this situation gave us

midterm we need to find network topology with more nodes with less load or/and wallets who utilize multiple cpu cores

our wallet code is save it can outfilter the wrong blocks
but the amount of bad blocks circulating in network is overloading the backbone nodes
so they lag and respond late which create additional confusion

while in the past there where attackpattern that missused the bantime and made us suggest 600 sec bantime
now at this situation a higher time would help our network to not process the same bad block again and again every 10 min

so please increase ur bantime to 3600 or 36000 if u have the time to manual check that ur wallet stay on mainchain

maybe we find a way how we can in future reward people for hosting backbone nodes

and this way have more of them

brainstorming in that area can start once the actual situation relax

we asked community for help get more mainnodes up and running

also i request everyone who dont need to have his wallet open to close it

only people who have their wallets online should be people who mine and use the connect listen=0 config
and people active monitor their wallet to make sure they stay on main chain
who act as additional relay nodes which use listen=1 and addnode config

this way network overload will be reduced
mainnodes get air to breath

and situation will releax