Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 739. (Read 1260636 times)

DMD MULTIPOOL LOTTO FIRST WINNER

http://www.win2day.at/gaming/RundenPlakat_wai.jsp

592935

mathematical closest dmd multipool lotto number towards austria official lotto joker number from drawing 3.august
dKFFgH6wVWw7E2qtedNNx4aRqdYQxMmHL8   591468

everyone registered at http://multipool.bit.diamonds (just enter ur wallet to register)
can find the winner number at all account stats page at 2014-07-26

CONGRATS!

we send 100 DMD soon and report with tx id

for next drawing (sunday 7th september (all lotto numbers on pool from 3rd august until 6th september are qualified))
foundation again put 100 DMD into the pot
if people of community wana donate some more to the winning pot u welcome

alex (popshot) will announce a donation wallet id

Please pay attention to this:

We have identified an attack vector, which is likely being exploited. We are working on a fix (complex research), but identified a network topology that would make Diamond network very resilient to this type of attack. The network topology suggests a proper configuration for different types of node usage, like this:

- any node, that generates blocks, either by PoW or PoS is advised to use the recently suggested configuration: connect= to one or more (preferably all) known permanent nodes, noirc=1, listen=0. This includes minters, solo miners and pools.
Example entries in the config file:

listen=0
noirc=1
connect=193.68.21.19
connect=54.191.208.14
connect=54.255.133.30
bantime=600

- any node that does not generate blocks, can fully participate in the network by relaying other nodes' blocks -- it should use addnode for the permanent nodes, noirc=0 and listen=1. Such a node would act as an unannounced/dynamic (because it might not be available at all times) full node. This is for exchanges, and those who do a lot of transactions.
Example entries in the config file:

listen=1
noirc=0
addnode=193.68.21.19
addnode=54.191.208.14
addnode=54.255.133.30
bantime=600

Of course, nothing prevents a non-block-generating node to use the more restrictive topology for the block generators -- this will make them even safer. The permanent nodes will only grow in numbers.

The idea of this network setup is that 'full nodes' chose to not generate blocks, and because of this, they can't be disconnected by other full nodes. These nodes would just relay blocks and provide the block chain for download. The nodes that do generate blocks control their connection to the network and thus if they end up generating invalid blocks, nobody else suffers. They can easily recover.

The wallet code will be updated to include more protections and react better on such situations, but this kind of network topology is an additional safeguard.

repairwallet got my coins displaying correctly as far as I can tell, though other commands can crash my client.

Think I must have synched to the wrong chain some how though. Not sure how that is possible, I must have screwed up the steps?

Here is a contribution to the Design Contest. Below are some layout ideas for banners.









and here is a layout idea for labels on for example the OP.

Thankx I'll give that a shot.
Should be easy to track down.

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

I am not sure I understood properly. You went from 3000 DMD to 1295 DMD OR you earned 1295 DMD since 31/7?

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.

No comment!

Diamond-qt for Windows can be run on any 32 and 64 bit versions. It's been well tested.

1- backup your wallet;
2- use the "checkwallet" command. Normally it should tell you how many coins will be recovered. Normally all those missing.
3- use the "repairwallet" command. You should now see all your coins back.

Please give your feedback.

update:
u can use below guide to sync
but later follow guidelines of danbis post:
https://bitcointalksearch.org/topic/m.8170710

following this im still on right chain after long time wallet open and minting

DMD isnt listed there since over a year why they should add it now?
aim must be fix current situation
later we can seek alternative exchanges
but cryptsy did nothing wrong now
its a logical and a clever move to stop deposit and withdraw if a coin network is under attack

I had the same problem, but once my wallet synced all my coins showed up.


Devs, will DMD be listed on Poloniex, C-Cex or AllCoin? Cryptsy is not working properly and the other 2 exchanges have no volume.

windows qt 64
is NOT compatible for 32 

Please devs tell me if somethings wrong 
I have been mining Dmd since May, I have more than 3000 dmds before 31-7 but now, after this "event" I have own 1295 dmds (
Im sure Im in right chain because the diff show same as danbi's pool.

dmd multipool cant payout DMD until cryptsy opens withdraws again
u still gather BTC that will  converted once cryptsy opens gates again

so keep mining at multipool dmd will come a bit later but they will come

Wow that was weird.
Wallet good.
decided to solo mine for abit.
hit the block. it came to the wallet.
awaiting confirmations.
disappeared after I walked outta the room
for 5 minutes.

I also got a ? bad transaction minted.
Obviously when I unlocked the wallet
and picked up a bad node from earlier.
It screwed the minting..

Yes, it's the software bug. It shows inflated values.

P.S. nodes sorted, both of them crashed.