[ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65%

[utahjohn]

even Danbi's is on lower diff fork occasionally ... shut it down and let the chain heal itself ...
I am about ready to quit solo mining too, 1/4 blocks mined orphaned ... 

[DMDCreeper]

even Danbi's is on lower diff fork occasionally ... shut it down and let the chain heal itself ...
I am about ready to quit solo mining too, 1/4 blocks mined orphaned ... 

Good to see you back here.  This looks FUBR.  I tried solo and was mining more orphans than DMDs so I quit.  donkeypool is getting hosed with orphans too.  There are other coins that are as profitable as DMD right now.

[cryptonit]

sync on rightchain repairwallet in console restart wallet
noone lose coins that exists in mainchain
pos attempts that stay unconfirmed dont reduce ur balance the coins will try mint again
its just a cosmetic issue that we display them in wallet
they should not be shown same as orphan mining blocks

only pow/pos earnings in a fork ar worthless
and transactions done in a fork are not done for real

but i dont want to sweettalk the situation
yes we will keep the network no question
but also yes we got some homework to do
for next wallet

longterm the goal is clear as users requests

a dmd diamond wallet should not be entertainment for nerds
instead it should be a easy to install and update tool to access
ur dmd funds and later on services that are attached to dmd diamond

so we share the same vision
just we not there yet
please give us the time needed

[NineEleven]

even Danbi's is on lower diff fork occasionally ... shut it down and let the chain heal itself ...
I am about ready to quit solo mining too, 1/4 blocks mined orphaned ... 

I restart mining last   night , about 10 hours ago, and whit 550 MHS i have only confirmed 3 coins

It's impossible to keep going like this
 

[utahjohn]

even Danbi's is on lower diff fork occasionally ... shut it down and let the chain heal itself ...
I am about ready to quit solo mining too, 1/4 blocks mined orphaned ... 

Good to see you back here.  This looks FUBR.  I tried solo and was mining more orphans than DMDs so I quit.  donkeypool is getting hosed with orphans too.  There are other coins that are as profitable as DMD right now.

Re-sync every hour or so from known good chain backup is a real PITA, and now sync caught up with connect= nodes, listen=0, noirc=1, bantome 3600 is fubar too at diff 25-35 ... wtf, even trusted nodes are not to be trusted

[Reggie0]

even Danbi's is on lower diff fork occasionally ... shut it down and let the chain heal itself ...
I am about ready to quit solo mining too, 1/4 blocks mined orphaned ...  

Good to see you back here.  This looks FUBR.  I tried solo and was mining more orphans than DMDs so I quit.  donkeypool is getting hosed with orphans too.  There are other coins that are as profitable as DMD right now.

Here is the solution: I've resynced a wallet with maxconnections=7, and 4x connect=<rootnode>, therefore it will stay at right chain and I moved my 800 MH/s from danbi's pool.

[DMDCreeper]

even Danbi's is on lower diff fork occasionally ... shut it down and let the chain heal itself ...
I am about ready to quit solo mining too, 1/4 blocks mined orphaned ... 

Good to see you back here.  This looks FUBR.  I tried solo and was mining more orphans than DMDs so I quit.  donkeypool is getting hosed with orphans too.  There are other coins that are as profitable as DMD right now.

Re-sync every hour or so from known good chain backup is a real PITA, and now sync caught up with connect= nodes, listen=0, noirc=1, bantome 3600 is fubar too at diff 25-35 ... wtf, even trusted nodes are not to be trusted

Does anyone actually know what's going on and what steps we can take to correct it?  Is Danbi's pool still overwriting found blocks and basically "stealing" them from other miners and pools?  If so the course of action seems obvious.

In the meantime, there doesn't seem to be any point mining DMD until this mess is sorted out.

[NineEleven]

I manage a few datacenter's whith very fast interneconections (10Ge)

Do you think that if a setup another pool wold help?

And yes Dabi's pool continues overwriting everyone eleses's blovks

[utahjohn]

I manage a few datacenter's whith very fast interneconections (10Ge)

Do you think that if a setup another pool wold help?

And yes Dabi's pool continues overwriting everyone eleses's blovks

Not if u can't keep it on correct chain , and trusted nodes are feeding me BS data now after a re-sync just 10 minutes ago

I have set banscore=1 and even this does not provide enough protection

[NineEleven]

I manage a few datacenter's whith very fast interneconections (10Ge)

Do you think that if a setup another pool wold help?

And yes Dabi's pool continues overwriting everyone eleses's blovks

Not if u can't keep it on correct chain , and trusted nodes are feeding me BS data now after a re-sync just 10 minutes ago

I'm on the correct chain
i only connect to trusted nodes

the problem ( i think) is that danbis pool is continues forking the chain, and relayn the blocks very slow, so from time to time, dbanis blockchain is biger than anyone else, so when it relays the blocks foud, evereyone eleses blocks get orphan

[cryptonit]

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

[NineEleven]

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

I will setup 3 nodes along the day in diferente locations
to see if it helps

[cryptonit]

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

[danbi]

The problem is basically the block relaying on the network is very slow. This, combined with the short block time is causing the "overwriting" situation.

The solution is more nodes running as permanent wallets and more block producing nodes (those are two separate things).

Another solution is for large miners to move off danbi's pool.

Yet another solution is to bring more hashpower to another pool.

What we have now is a very bad situation, which will persist until the fork (the 1000000 million DMD) -- after that point, PoS will run at much higher pace and PoW at lower, so even with 100% hash rate one source of blocks will not be enough to "overwrite" anything.

Shutting down danbi's pool will not do much more than punish those who mine there.

So please, if someone can -- run permanent nodes, connect them (with addnode=) to the current permanent nodes and publish your IP addresses for others to use. This will remove a lot of load from the existing nodes, letting blocks propagate faster.

Running a pool would change things slower, as you would need to convince miners they can trust you and change their settings -- but this is ultimately the long term goal.

I too agree, that frequent forks are bad idea and we try to avoid this as much as possible.

[cryptonit]

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

I will setup 3 nodes along the day in diferente locations
to see if it helps

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

[cryptonit]

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

is up and running as alternative pool

support him

or go solo mining

[NineEleven]

Full node operacional synced and on the right chain


193.136.97.30

[cryptonit]

- 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

[cryptonit]

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

[NineEleven]

i'm using this config


any comments?


listen=1
server=1
daemon=1
addnode=193.68.21.19
addnode=54.191.208.14
addnode=54.255.133.30
addnode=54.86.164.216
bantime=14400
noirc=1