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

[jelt14]

my wallet is now synced   happened sometime over weekend (Thank God ) and now staking almost 50% of coins 

[cryptonit]

Does anyone know whats happening with cryptsy and if coins can be deposited or withdrawn from there?

I withdrew 300 DMD yesterday from cryptsy without issues.

i can confirm withdraw working
so they are on right chain
still deposits dont show up at exchange so they dont forward them from wallet to exchange software

[popshot]

(Far too much Blah to warrant reposting)

These are just a few I can think of off-my-hand.
Please share yours.

Endless bickering that drove original Dev away says it all really.

Lemmie know when you've fixed 203's crashing...

That's what I thought you could not even come up with  one good argument.

You mean The Original Dev? Really??
The same one who abandoned Diamond after one month after creating it? Probably he was too busy with  taking care of the other coins he made along the way. To me it looked as if he went after some better pump. Nothing stops him coming back and taking part in the development of Diamond. Just shame , he blacklisted my account so he doesn't even alow to be contacted. This says it all.

Sure we will. The whole community will be informed.

And for you wish you luck with that copy paste promo job that you do for bluetrade exchange. With such aggressive 'promotion' you are doing disfavour to them.

[bigtimespaghetti]

Thanks cryptonit, things are looking good for me now. Looking forward to getting back to staking!

[Mister1k]

I tried as you suggested. I am down 18 .
17 transactions. 1 minted. Unconfirmed.
07312014 mined and minted.
The checkwallet cmd gave me back,  passed true..
No change.

http://diamond.danbo.bg:2750/chain/Diamond
enter ur wallet address there u can see exactly what happend with ur balance
incoming andoutgoing transactions

coin never get lost
only u can lose access to them
if u as example forget ur wallet password
or if u transfer them to a wrong address

edit:
what i do if i was trapped in a wrong fork is i make sure i always use a old wallet.dat when i resync
i even used a few times already a virgin (the first day i created my wallet woth zero coins in it) wallet.dat from december and when resync every coin is displayed correct even from subaddresses i created that the old wallet.dat dont even know. thats because all or addresses in one wallet share same secret part so  even a old wallet.dat is able to recover it

Further to your suggestion yesterday, I did some digging at the block explorer.
18.8 in total down. I think I lost more than access.
dK2bEazyFqqBFkyXeTYLpmM5Rw6BFAtAJL
dW4K3gk1d6eKt3F2hn24Dt89tbqizuWWQ3
Two machines  0731 Cryptohunger

http://diamond.danbo.bg:2750/address/dK2bEazyFqqBFkyXeTYLpmM5Rw6BFAtAJL
3 entries for Block 511524  2014-07-31 11:33:36
I never mined the pool on 0802 for these next 37 entries
The last 37 entries are for Block 514161  2014-08-02 11:57:03

http://diamond.danbo.bg:2750/address/dW4K3gk1d6eKt3F2hn24Dt89tbqizuWWQ3
2 entries For Block 511524 Again? 2014-07-31 11:33:36

Two addresses on the same block???
end of record..


This address is for minept.
dLCjSU7dpSQFuFx9R58bDC35Md6VRkCeey
http://diamond.danbo.bg:2750/address/dLCjSU7dpSQFuFx9R58bDC35Md6VRkCeey
  
  3 entries Block 484822 2014-07-12 05:53:19
  3 entries Block 490721 2014-07-16 11:40:39
  4 entries Block 496363 2014-07-20 12:57:45
  4 entries Block 496653 2014-07-20 18:01:37
  3 entries Block 500823 2014-07-23 17:49:59
18 entries Block 504890 2014-07-26 15:58:53
 3  entries Block 507782 2014-07-28 17:46:43
13 entries Block 508893 2014-07-29 12:54:05   
 2 entries Block  512294 2014-08-01 00:53:51
 3 entries Block 514045 2014-08-02 10:01:57   
 3 entries Block 514325 2014-08-02 14:46:33
 3 entries Block 515765 2014-08-03 15:47:23   
end of record
I never mined here on or after 0801.
I am unsure at this point. It looks pretty messy.
minept has been down for 3 days now. I am not understanding transactions coming from them
or cryptohunger since 0731. Thankx for your time.

[cryptonit]

what exactly means

18.8 in total down

18.8 dmd missing?

whatever u mined at pools while they where on wrong chain is lost in alterative reality
every mining minting  transaction u recived or sendet on wrong blockchain is not existing in real blockchain

when i said u never lose coins i mean coins u earned/owned on the correct chain wont disappear somehow on the correct chain

i have no time check block explorer for u now but it should be self explained what u can read there

a block can contain data of multiple transactions
reason for transactions towards u from the pool later when u didnt mine there can be they discovered some wrong transactions on a fork and tryed to fix that later on by sending coin again.....

but such questions u have to ask the pool operator if transactions from them towards u look strange to u

[danbi]

I tried as you suggested. I am down 18 .
17 transactions. 1 minted. Unconfirmed.
07312014 mined and minted.
The checkwallet cmd gave me back,  passed true..
No change.

http://diamond.danbo.bg:2750/chain/Diamond
enter ur wallet address there u can see exactly what happend with ur balance
incoming andoutgoing transactions

coin never get lost
only u can lose access to them
if u as example forget ur wallet password
or if u transfer them to a wrong address

edit:
what i do if i was trapped in a wrong fork is i make sure i always use a old wallet.dat when i resync
i even used a few times already a virgin (the first day i created my wallet woth zero coins in it) wallet.dat from december and when resync every coin is displayed correct even from subaddresses i created that the old wallet.dat dont even know. thats because all or addresses in one wallet share same secret part so  even a old wallet.dat is able to recover it

Further to your suggestion yesterday, I did some digging at the block explorer.
18.8 in total down. I think I lost more than access.
dK2bEazyFqqBFkyXeTYLpmM5Rw6BFAtAJL
dW4K3gk1d6eKt3F2hn24Dt89tbqizuWWQ3
Two machines  0731 Cryptohunger

http://diamond.danbo.bg:2750/address/dK2bEazyFqqBFkyXeTYLpmM5Rw6BFAtAJL
3 entries for Block 511524  2014-07-31 11:33:36
I never mined the pool on 0802 for these next 37 entries
The last 37 entries are for Block 514161  2014-08-02 11:57:03

http://diamond.danbo.bg:2750/address/dW4K3gk1d6eKt3F2hn24Dt89tbqizuWWQ3
2 entries For Block 511524 Again? 2014-07-31 11:33:36

Two addresses on the same block???
end of record..


This address is for minept.
dLCjSU7dpSQFuFx9R58bDC35Md6VRkCeey
http://diamond.danbo.bg:2750/address/dLCjSU7dpSQFuFx9R58bDC35Md6VRkCeey
  
  3 entries Block 484822 2014-07-12 05:53:19
  3 entries Block 490721 2014-07-16 11:40:39
  4 entries Block 496363 2014-07-20 12:57:45
  4 entries Block 496653 2014-07-20 18:01:37
  3 entries Block 500823 2014-07-23 17:49:59
18 entries Block 504890 2014-07-26 15:58:53
 3  entries Block 507782 2014-07-28 17:46:43
13 entries Block 508893 2014-07-29 12:54:05   
 2 entries Block  512294 2014-08-01 00:53:51
 3 entries Block 514045 2014-08-02 10:01:57   
 3 entries Block 514325 2014-08-02 14:46:33
 3 entries Block 515765 2014-08-03 15:47:23   
end of record
I never mined here on or after 0801.
I am unsure at this point. It looks pretty messy.
minept has been down for 3 days now. I am not understanding transactions coming from them
or cryptohunger since 0731. Thankx for your time.

I am trying to figure out what you think is a problem.

It is perfectly valid to have more than one transaction to or from the same address in one single block. More than one entity might have sent you coins during the creation of one block. One entity can send you several transactions, within the same block. For example, a pool running catch up payment scripts, after they have come to the correct chain.

You might have mined earlier at the pool and they send you the earnings later (this is what usually happens, anyway).

It all looks perfectly normal to me.

[cryptonit]

just a short update regarding situation
testing a fix to that kind of attack soon
if it works u can expect a new wallet release soon
its very interesting how the weakness which was abused
is existing in a lot coin but only heavy abused with diamond

i think we should feel proud to attract so much attention
and even more because the only result of this attack will be
increased wallet security and a network layout thats better prepared against future attack attempts

i have to say a big thx to all community members who did stay loyal to their coin
and gave a helping hand wherever it was needed to each other

[utahjohn]

Who is Null I see this happening frequently on Danbi's pool

517071   null   08/04/2014 08:41:43   74.1799   1.00   18,990   0   0.00
517070   izhelev   08/04/2014 08:41:26   69.9521   1.00   17,908   0   0.00
517069   worst   08/04/2014 08:41:19   68.7485   1.00   17,600   11,579   65.79

and then a few minutes later

517071   donnk   08/04/2014 08:41:43   74.1799   1.00   18,990   1,736   9.14

[coinedabit]

I'm still not seeing my DMD withdrawal from cryptsy on the 1staug to my wallet. Cryptsy said it was processed and received but i can't even find the transaction on the blockchain with my address or block hash. Am i right in thinking that i will see these coins again? or could cryptsy have sent it to the wrong blockchain?

Thanks


Can't wait to see DMD @ 5 x BTC value...:0)

[bigtimespaghetti]

Sorry to ask but the two transactions at the top were part of the old chain here(not being accepted?):

http://snag.gy/IGLwc.jpg

[cryptonit]

Sorry to ask but the two transactions at the top were part of the old chain here(not being accepted?):

http://snag.gy/IGLwc.jpg

seek the tx id in blockexplorer
if u cant find it u minted them in a fork
nothing lost ur coin-age not spend and so ur coins will soon mint again

or u did just mint orphan blocks and stay in correct blockchain which can happen too and is normal behavior

blockchain is selfhealing in that aspect

but the attack we suffered did reduce that selfhealing and made some wallets stick with there private blockchain after mine/mint a orphan block and worst case even promote it to connected peers as true chain

[danbi]

Who is Null I see this happening frequently on Danbi's pool

517071   null   08/04/2014 08:41:43   74.1799   1.00   18,990   0   0.00
517070   izhelev   08/04/2014 08:41:26   69.9521   1.00   17,908   0   0.00
517069   worst   08/04/2014 08:41:19   68.7485   1.00   17,600   11,579   65.79

and then a few minutes later

517071   donnk   08/04/2014 08:41:43   74.1799   1.00   18,990   1,736   9.14

This is happening, because the pool's front-end (MPOS) and the backend(s) work asynchronously. This is why one cannot 100% trust what MPOS displays (but the trend etc is accurate, as are past accounted blocks).

In this particular case, the background routine that finds new blocks and puts them in the database found a block - it knows the block data as found in the block chain, but does not know who found it (the block chain has no idea). Just after this task finishes, another is started, that populates these new found blocks with information from the pool database -- who found it, what is the shares distribution etc.
This is why it is happening and it's actually amusing to watch.

MPOS can of course work without this semi-realtime data being present, in which case information about new blocks will simply appear a bit later.

[utahjohn]

Who is Null I see this happening frequently on Danbi's pool

517071   null   08/04/2014 08:41:43   74.1799   1.00   18,990   0   0.00
517070   izhelev   08/04/2014 08:41:26   69.9521   1.00   17,908   0   0.00
517069   worst   08/04/2014 08:41:19   68.7485   1.00   17,600   11,579   65.79

and then a few minutes later

517071   donnk   08/04/2014 08:41:43   74.1799   1.00   18,990   1,736   9.14

This is happening, because the pool's front-end (MPOS) and the backend(s) work asynchronously. This is why one cannot 100% trust what MPOS displays (but the trend etc is accurate, as are past accounted blocks).

In this particular case, the background routine that finds new blocks and puts them in the database found a block - it knows the block data as found in the block chain, but does not know who found it (the block chain has no idea). Just after this task finishes, another is started, that populates these new found blocks with information from the pool database -- who found it, what is the shares distribution etc.
This is why it is happening and it's actually amusing to watch.

MPOS can of course work without this semi-realtime data being present, in which case information about new blocks will simply appear a bit later.

Thanks I figured it might be something like that   No worries

[utahjohn]

My permanent node is addnode=utahjohn.ddns.net
Please use DNS address as the numeric IP may change
I am in Salt Lake City, Utah, USA

17771   Port is OPEN on 65.130.100.203

Donations: dEdj7aH7Pgt3oVAeEFmA46sXCDcZYeiQjP

[polanskiman]

My permanent node is addnode=utahjohn.ddns.net
Please use DNS address as the numeric IP may change
I am in Salt Lake City, Utah, USA

17771   Port is OPEN on 65.130.100.203

Donations: dEdj7aH7Pgt3oVAeEFmA46sXCDcZYeiQjP

Hey John,

My understanding is that DMD Foundation does not want to promote dynamic dns addresses as permanent nodes.

I recommend you contact Crypto. or PopS. for further details.

[digi123]

Withdrew .1 DMD from Crypsy to my wallet it went fine. Four minutes later I withdrew 200 DMD from Cryptsy and it did not hit my wallet. Cryptsy is using different wallets on different block chain or something fishy is going on.

.1 Processed    TrxID: 5de7a9360db13e7784288e4630faf4b262f741bdfafcb352f26274353a8a320c @ 2014-08-02 10:22:11
200 Processed    TrxID: e71eaee9f8541ef2863672634635ef7230638c332582d1c753116ca133048a1a @ 2014-08-02 10:26:10

I would agree with you, as I have sent 4 small test transactions to cryptsy one each day and nothing has turned up in my diamond account with them.
They seem to be very slow to get on top of this problem.
There is no outgoing information from them about what they are doing.
We need continuous updates about what they are doing, or maybe they have done nothing, how do we know?






 

[danbi]

My permanent node is addnode=utahjohn.ddns.net
Please use DNS address as the numeric IP may change
I am in Salt Lake City, Utah, USA

17771   Port is OPEN on 65.130.100.203

Donations: dEdj7aH7Pgt3oVAeEFmA46sXCDcZYeiQjP

Hey John,

My understanding is that DMD Foundation does not want to promote dynamic dns addresses as permanent nodes.

I recommend you contact Crypto. or PopS. for further details.

This is not for the Diamond Foundation to decide.

The wallet code simply ignores DNS entries, unless you give it the -dns option too. Since most people would not bother, it is safer to use only IP addresses for the nodes, however inconvenient this is.
We have enabled -dns to be on by default in the Diamond wallet, but... there is yet another trouble with dynamic DNS services -- the lookup will be done only once, at wallet startup time. Since the wallet is (in principle) a long running process, it may be (and most likely will be) situation when the Dynamic DNS entry will be updated with a different IP address and the wallet will keep trying to reach the original IP address forever.

This is fine for addnode= entries, because they are more or less used for bootstrapping. But it is useless for connect= entry for the reasons stated.

Since Diamond is a peer to peer cryptocurrency, it is fine for the individual network participants to use such dynamic DNS nodes or not. It is their own decision anyway.

[utahjohn]

My permanent node is addnode=utahjohn.ddns.net
Please use DNS address as the numeric IP may change
I am in Salt Lake City, Utah, USA

17771   Port is OPEN on 65.130.100.203

Donations: dEdj7aH7Pgt3oVAeEFmA46sXCDcZYeiQjP

Hey John,

My understanding is that DMD Foundation does not want to promote dynamic dns addresses as permanent nodes.

I recommend you contact Crypto. or PopS. for further details.

This is not for the Diamond Foundation to decide.

The wallet code simply ignores DNS entries, unless you give it the -dns option too. Since most people would not bother, it is safer to use only IP addresses for the nodes, however inconvenient this is.
We have enabled -dns to be on by default in the Diamond wallet, but... there is yet another trouble with dynamic DNS services -- the lookup will be done only once, at wallet startup time. Since the wallet is (in principle) a long running process, it may be (and most likely will be) situation when the Dynamic DNS entry will be updated with a different IP address and the wallet will keep trying to reach the original IP address forever.

This is fine for addnode= entries, because they are more or less used for bootstrapping. But it is useless for connect= entry for the reasons stated.

Since Diamond is a peer to peer cryptocurrency, it is fine for the individual network participants to use such dynamic DNS nodes or not. It is their own decision anyway.

Trying to get static IP from my ISP ... no reply yet ...

[polanskiman]

My permanent node is addnode=utahjohn.ddns.net
Please use DNS address as the numeric IP may change
I am in Salt Lake City, Utah, USA

17771   Port is OPEN on 65.130.100.203

Donations: dEdj7aH7Pgt3oVAeEFmA46sXCDcZYeiQjP

Hey John,

My understanding is that DMD Foundation does not want to promote dynamic dns addresses as permanent nodes.

I recommend you contact Crypto. or PopS. for further details.

This is not for the Diamond Foundation to decide.

The wallet code simply ignores DNS entries, unless you give it the -dns option too. Since most people would not bother, it is safer to use only IP addresses for the nodes, however inconvenient this is.
We have enabled -dns to be on by default in the Diamond wallet, but... there is yet another trouble with dynamic DNS services -- the lookup will be done only once, at wallet startup time. Since the wallet is (in principle) a long running process, it may be (and most likely will be) situation when the Dynamic DNS entry will be updated with a different IP address and the wallet will keep trying to reach the original IP address forever.

This is fine for addnode= entries, because they are more or less used for bootstrapping. But it is useless for connect= entry for the reasons stated.

Since Diamond is a peer to peer cryptocurrency, it is fine for the individual network participants to use such dynamic DNS nodes or not. It is their own decision anyway.

When I mentioned earlier about the possibility for me to setup a dynamic dns address I was told that a DynDns address as a permanent node was not the image the foundation wanted to give to the public. Thus my comment.

As for the rest of your explanation it make indeed more sense.