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

[Mister1k]

Update your wallets. This is mandatory.
There are too many wallets not updated.
The block explorer is seeing a 2.0.3.2 wallet
And numerous 2.0.4 and 2.0.4.1 versions of wallets.
https://chainz.cryptoid.info/dmd/#!network
Network tab/node list.
Here are the nodes not updated.
2.0.4
addnode=110.174.192.177
addnode=111.92.116.139
addnode=14.177.142.120
addnode=37.48.113.81
addnode=5.15.240.39
addnode=62.43.140.213
addnode=72.253.122.203
addnode=92.229.129.38
addnode=95.18.124.63
addnode=96.89.147.106
addnode=99.61.195.86
2.0.4.1 protocol 60006
addnode=212.243.7.37
addnode=79.120.211.194
2.0.4.1 protocol 60012
addnode=212.243.7.37
addnode=79.120.211.194
Strange ^^^^^^^^^^^ they are the same?
2.0.3.2
addnode=173.52.253.209
They need to be updated.
ASAP.

[cryptonit]

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

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?

[NineEleven]

top - 13:20:16 up  3:48,  3 users,  load average: 0.53, 0.40, 0.41
Tasks: 180 total,   1 running, 178 sleeping,   0 stopped,   1 zombie
%Cpu(s):  0.0 us,  1.7 sy, 48.6 ni, 49.3 id,  0.0 wa,  0.0 hi,  0.0 si,  0.5 st
KiB Mem:   3797964 total,  3649852 used,   148112 free,    43832 buffers
KiB Swap:  7945212 total,     3572 used,  7941640 free,  2545532 cached

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND                                                                                                                
11629 sysop     20   0  955m 468m  24m S 100.4 12.6  58:50.64 diamond-qt                                                                                                            
  142 root      20   0     0    0    0 S   0.3  0.0   0:12.12 scsi_eh_1                                                                                                              
12008 root      20   0     0    0    0 S   0.3  0.0   0:01.61 kworker/0:1                                                                                                            
12036 root      20   0     0    0    0 S   0.3  0.0   0:01.21 kworker/0:0                                                                                                            


basicaly its 100%
the wallet does not suport simetric multiprocessing

[NineEleven]

{
"version" : "v2.0.5.5",
"protocolversion" : 60012,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 874542,
"moneysupply" : 994818.71613400,
"connections" : 31,
"proxy" : "",
"ip" : "193.136.97.30",
"difficulty" : 93.38328036,
"testnet" : false,
"keypoololdest" : 1428659785,
"keypoolsize" : 102,
"paytxfee" : 0.00000000,
"errors" : ""
}

[stoody]

i just started to solo mine and it seems to be working. but i just had a question dose anyone know what this means??? "no suitable long-pool found for http://127.0.0.1:17772" thanks

[cryptonit]

i just started to solo mine and it seems to be working. but i just had a question dose anyone know what this means??? "no suitable long-pool found for http://127.0.0.1:17772" thanks

normal message for solo mining

[stoody]

i just started to solo mine and it seems to be working. but i just had a question dose anyone know what this means??? "no suitable long-pool found for http://127.0.0.1:17772" thanks

normal message for solo mining

thanks mate quick response as always ... bit of drama by the look of it....

[cryptonit]

top - 13:20:16 up  3:48,  3 users,  load average: 0.53, 0.40, 0.41
Tasks: 180 total,   1 running, 178 sleeping,   0 stopped,   1 zombie
%Cpu(s):  0.0 us,  1.7 sy, 48.6 ni, 49.3 id,  0.0 wa,  0.0 hi,  0.0 si,  0.5 st
KiB Mem:   3797964 total,  3649852 used,   148112 free,    43832 buffers
KiB Swap:  7945212 total,     3572 used,  7941640 free,  2545532 cached

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND                                                                                                                
11629 sysop     20   0  955m 468m  24m S 100.4 12.6  58:50.64 diamond-qt                                                                                                            
  142 root      20   0     0    0    0 S   0.3  0.0   0:12.12 scsi_eh_1                                                                                                              
12008 root      20   0     0    0    0 S   0.3  0.0   0:01.61 kworker/0:1                                                                                                            
12036 root      20   0     0    0    0 S   0.3  0.0   0:01.21 kworker/0:0                                                                                                            


basicaly its 100%
the wallet does not suport simetric multiprocessing

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...

[cryptonit]

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

[NineEleven]

top - 13:20:16 up  3:48,  3 users,  load average: 0.53, 0.40, 0.41
Tasks: 180 total,   1 running, 178 sleeping,   0 stopped,   1 zombie
%Cpu(s):  0.0 us,  1.7 sy, 48.6 ni, 49.3 id,  0.0 wa,  0.0 hi,  0.0 si,  0.5 st
KiB Mem:   3797964 total,  3649852 used,   148112 free,    43832 buffers
KiB Swap:  7945212 total,     3572 used,  7941640 free,  2545532 cached

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND                                                                                                                
11629 sysop     20   0  955m 468m  24m S 100.4 12.6  58:50.64 diamond-qt                                                                                                            
  142 root      20   0     0    0    0 S   0.3  0.0   0:12.12 scsi_eh_1                                                                                                              
12008 root      20   0     0    0    0 S   0.3  0.0   0:01.61 kworker/0:1                                                                                                            
12036 root      20   0     0    0    0 S   0.3  0.0   0:01.21 kworker/0:0                                                                                                            


basicaly its 100%
the wallet does not suport simetric multiprocessing

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...

now the load as reduced a lot


top - 14:26:31 up  4:54,  3 users,  load average: 0.37, 0.52, 0.57
Tasks: 178 total,   1 running, 176 sleeping,   0 stopped,   1 zombie
%Cpu(s):  0.0 us,  0.7 sy,  0.2 ni, 98.7 id,  0.0 wa,  0.0 hi,  0.0 si,  0.5 st
KiB Mem:   3797964 total,  3674596 used,   123368 free,    48212 buffers
KiB Swap:  7945212 total,     3568 used,  7941644 free,  2548620 cached

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND                                                                                                               
11629 sysop     20   0  958m 483m  24m S   1.7 13.0  98:42.07 diamond-qt                                                                                                             
   12 root      rt   0     0    0    0 S   0.3  0.0   0:00.13 watchdog/1                                                                                                             
  142 root      20   0     0    0    0 S   0.3  0.0   0:16.99 scsi_eh_1                                                                                                             
 3023 root      20   0 71288 2128 1960 S   0.3  0.1   0:02.40 sshd                                                                                                                   
 9428 sysop     20   0  498m  22m  12m S   0.3  0.6   0:03.27 gnome-settings-                                                                                                       
10710 sysop     20   0  477m  23m  14m S   0.3  0.6   0:03.18 gnome-panel                                                                                                           
12589 root      20   0     0    0    0 S   0.3  0.0   0:00.42 kworker/0:3


i think this is going on the right way

[NineEleven]

second node

193.136.96.30


I have a third node but its my mining node, so for now i will keep it private

[Star65]

With the new wallet minting works a lot better. Even small pile in the business now. 

[NineEleven]

The network is better now, but not optimal

I'm monitoring my 3 nodes

and sometimes tehre is a delay betwen then, such delay sometimes goes for 2 or 3 minutes.

On the other side im my mining operation , i can comfirm blocks now, but i stil get too much orphans, lets say something aroud 25% ......

that does not hapen a week ago

[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
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

[popshot]

When will we have a comprehensive PR plan for DMD

- Thunderclap campaign

- New Website

- Video about DMD

- Press release

-...


When ?

What do you mean a comprehensive plan?

We're working on the new website.
This involves gathering funds (not from the community, because this proved to be inefficient).
We're also not going to dump foundation funds (DMD) for BTC peanuts. We need money for copyrighters who would actually produce lots of content.
Without the website we're not starting any campaigns. But once we have it we will significantly increase our presence in social media + buy that PR release.
Thudreclap will be a part of the process.

Video will be made once we have money for it. Not some cheap production. But a proper one. I have found people who have proven to be excellent and very much familiar with crypto.

As has been said before. Let's wait for the switch point and see how the network behaves. If everything settles nicely we could start promoting things.
Even though we don’t anticipate any instabilities (but rather an improvement on the current state) we need to take precautionary measures as we wouldn’t want people having bad first experience with Diamond.

We’re moving as fast as we currently can, but I’m not going to put any deadline on anything because things will be done when done.

On the side note, it’s not exactly the best environment right now to concentrate on promotion while for the over the week we’ve been extensively testing the new wallet and now fighting network instabilities. Actually, we’ve been wasting lots of time on countering these bullshit attacks.
Day has 24 hours people have day jobs, families and other commitments (like at least 5h of sleep). Please take this under consideration.

[DMDCreeper]

"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)"

What do you consider a "real big hashrate"?

I am trying to solo mine now with about 225 MH/s but almost 50% of my found blocks are orphans.  This is not productive for me.  Is this going to get corrected soon?

 

[cryptonit]

"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)"
What do you consider a "real big hashrate"?
I am trying to solo mine now with about 225 MH/s but almost 50% of my found blocks are orphans.  This is not productive for me.  Is this going to get corrected soon?

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

[DMDCreeper]

"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)"
What do you consider a "real big hashrate"?
I am trying to solo mine now with about 225 MH/s but almost 50% of my found blocks are orphans.  This is not productive for me.  Is this going to get corrected soon?

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

Are you telling me that, or are you telling everyone?

[cryptonit]

"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)"
What do you consider a "real big hashrate"?
I am trying to solo mine now with about 225 MH/s but almost 50% of my found blocks are orphans.  This is not productive for me.  Is this going to get corrected soon?

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

Are you telling me that, or are you telling everyone?

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

[cryptonit]

only 2 days to 1000000 total coin trigger!

prepare for warp!



lets see what await us on the other side