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

[cryptonit]

not be so harsh shveicar

i think peercoin is a excellent coin together with their side projects like nubit and so on

but peercoin is no undervalued underdog close before a pow reward reduction

as a investor u have to look at a few parameter

first: is the actual price low or high
(buy in when its still low is the golden rule.....)

second: is it a project with longterm dedicated people
(else u waste  money into a soon dead coin....)


for both questions i can give u a hint

hint 1: https://bitcointalk.org/index.php?topic=580725.msg10615239#msg10615239

hint 2: https://chainz.cryptoid.info/dmd/block.dws?000002e9686a879460eb5497d51a99fa6d5cad4a9edabb5112bd915b7d2302fc.htm (look at the date....)

[1715167607]

1715167607

[1715167607]

1715167607

[1715167607]

1715167607

[1715167607]

1715167607

[1715167607]

1715167607

[cryptonit]

https://bit.diamonds/community/

registration is fixed and working again normal

thx alex (popshot)

[cryptonit]

do we have users who need a mac wallet?
if yes do we have people who can compile a mac wallet?

[feldenthorne]

do we have users who need a mac wallet?
if yes do we have people who can compile a mac wallet?

You can just cross-compile a Mac wallet. You'll need someone to test it or an OSX VM, but it'll build straight out of Qt-Creator.

[cryptonit]

the sources are updated to 2.0.5.2
self compiling linux user can join in extended beta test
if no major issues found this is the release version

windows users who want a extended beta wallet pm me their email address

monday we update the official dowload links

all changes will go active together with pow reduction at 1000000 total coins

quick overview at specs after 1000000

pow blocktime 100s reward 0.2 (foundation share 0.01)
pos blocktime 100s 50% per year
pos min age 1 day

(the coinrolloutplan is unchanged just the blocktimes and the pow rewards are asjusted but create the same amount of coins as in coinrolloutplan
the future rewards reduction for pos stay at the same triggers as in original plan so 50% pos will stay active until 1500000 total coins (then 25% stage begins))

average blocktime will be between 50 and 60 sec so we even become a bit faster by this adjustments

some adapations in diff calc engine
increased support of minicomputers like rasperry pi / pi2

important for pool owners to adapt their pool code for foundation share at 1000000 to the lower value

around trigger 1000000 is suggest as much people as possible go solo mining until first pools are confirmed to be adapted successful

[feldenthorne]

the sources are updated to 2.0.5.2
self compiling linux user can join in extended beta test
if no major issues found this is the release version

windows users who want a extended beta wallet pm me their email address

monday we update the official dowload links

all changes will go active together with pow reduction at 1000000 total coins

quick overview at specs after 1000000

pow blocktime 100s reward 0.2 (foundation share 0.01)
pos blocktime 100s 50% per year
pos min age 1 day

(the coinrolloutplan is unchanged just the blocktimes and the pow rewards are asjusted but create the same amount of coins as in coinrolloutplan
the future rewards reduction for pos stay at the same triggers as in original plan so 50% pos will stay active until 1500000 total coins (then 25% stage begins))

average blocktime will be between 50 and 60 sec so we even become a bit faster by this adjustments

some adapations in diff calc engine
increased support of minicomputers like rasperry pi / pi2

important for pool owners to adapt their pool code for foundation share at 1000000 to the lower value

around trigger 1000000 is suggest as much people as possible go solo mining until first pools are confirmed to be adapted successful

Support is still broken for Raspberry Pi/Pi 2 in the DMDCoin repository. I submitted a pull request to Danbi weeks ago to fix the issue, but it was right after he pulled from my repo initially, so I assume he didn't see it.

I'll submit a pull request to the main repo so you can look it over. I just merged DMDCoin/master into mine, so it's an automatic merge on your end at the moment.

[Spidersbox]

So two weeks ago I upgraded my pool server ubuntu 12.04 to 14.04 and recompiled all of my wallets.
diamondd crashes after an hour or so. I went as far as deleting everything - /usr/bin/diamond, ~/Diamond and .Diamond and started from scratch, several times in fact - for two weeks.  I just tried it a few hours earlier with the new version  "v2.0.5.2" and am having the same issues. It only seems to crash while mining if that helps. I just cleared db and debug logs and restarted, I can post some parts of the logs when it crashes again.
on the bright side, the wallet loads faster

[Whaler]

I sell my dmd long time now and sad to do so look forward if 2nd coming

[NoobKidOnTheBlock]

Can someone suggest the best place to mine this wonderful coin? Like a really good pool or something?

[popshot]

Can someone suggest the best place to mine this wonderful coin? Like a really good pool or something?

If you take a look here https://chainz.cryptoid.info/dmd/#!extraction you will notice that there are 3 public pools danbi's, MiningField US and Donkey's . the first two are the biggest and both operators are part of the Diamond community. Not sure about the Donkey, but haven't heard any complaints about that pool.

Even though there is no risk of 51% attack coming from the biggest two pools it's always advisable to spread hash among different pools.

You can of course mine solo and possibly get best results, but to do that effectively you need to have a reasonable amount of hashing power.

We're gonna have sharp reward reduction soon so better hurry with mining, you won't be able to mine as many coins as you can now.  

[popshot]

Popshot, I think that unless someone can chip 1BTC for the PR release in the coming week, we should launch it just after 1M PoW reduction.

What do you think ?

Yes, I agree in principle. Let us see how extended beta tests of the new wallet go and see network behaviour after the reduction. Everything appears to be going smooth and well so far.

We can start drawing more detailed plans on how to kick start community building. We should not rest all our hopes on a single one-time PR service but rather create a cohesive strategy that in the longer run bring higher interest in this coin.

I think we should put some time and effort into making the main website a good starting point for newcomers. At the moment it's more directed at people who already know something about crypto and generally it's not accessible to newbies.

Anyone willing to help with that aspect?

[Spidersbox]

I just cleared db and debug logs and restarted, I can post some parts of the logs when it crashes again.
on the bright side, the wallet loads faster

it ran for 7 1/2 hours then crashed.
command line error:
me@myserverr:~/.Diamond$ *** Error in `diamondd': double free or corruption (!prev): 0x19a056c0 ***

db.log 0 bytes
debug.log 424k

last little bit of debug.log:
Flushed wallet.dat 239ms
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
ProcessSyncCheckpoint: sync-checkpoint at 0000000000404400cb3566602a805ee02f1e750bee59fcf41d09c997dc8b05a4
received block 95fe7ef091bab0a9d05d
SetBestChain: new best=95fe7ef091bab0a9d05da10c90aa522ddf9bb377f7dbc6ab950ca27bd8fce369  height=867683  trust=30124705261611 moneysupply=985579.466969 date=04/05/15 11:48:10
Stake checkpoint: 66779ea2
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 233ms
Flushed 13557 addresses to peers.dat  284ms
ThreadRPCServer method=gettransaction
ThreadRPCServer method=getaccount
getblocks 867676 to 00000000001e651c6ff6 limit 500
  getblocks (hashStop) stopping at 867676 00000000001e651c6ff6 (0 bytes)
getblocks 867676 to 0000000002a76c4c8766 limit 500
  getblocks (hashStop) stopping at 867677 0000000002a76c4c8766 (927 bytes)
getblocks 867676 to 00000000026630973759 limit 500
  getblocks (hashStop) stopping at 867678 00000000026630973759 (1252 bytes)
getblocks 867676 to 0000000001f740faadf4 limit 500
  getblocks (hashStop) stopping at 867679 0000000001f740faadf4 (1578 bytes)
getblocks 867676 to 0000000000ad6087cefe limit 500
  getblocks (hashStop) stopping at 867680 0000000000ad6087cefe (1904 bytes)
getblocks 867676 to 0000000002816ee4864c limit 500
  getblocks (hashStop) stopping at 867681 0000000002816ee4864c (2205 bytes)
getblocks 867676 to 0000000000404400cb35 limit 500
  getblocks (hashStop) stopping at 867682 0000000000404400cb35 (2506 bytes)
ThreadRPCServer method=gettransaction
ThreadRPCServer method=getaccount
Flushed 13557 addresses to peers.dat  276ms
ThreadRPCServer method=gettransaction
ThreadRPCServer method=getaccount
received block b6f5f0bb6f33cb6b0087
SetBestChain: new best=b6f5f0bb6f33cb6b008736b6beadf2026d8fda6b8b114b7795bfb3aba260a2e4  height=867684  trust=30127641850448 moneysupply=985583.682037 date=04/05/15 11:52:16
Stake checkpoint: 8db5b128
ProcessBlock: ACCEPTED

Nothing more after that.  Any ideas ??

[cryptonit]

@Spidersbox u run into same problem with old and new wallet version
old wallet version is used by a few pools without issue

so i expect something at ur setup/compile must be different to them

maybe someone who runs a pool can give ya a hint what might be the difference

it would be good if one pool owner upgrade to new wallet and confirm it runs fine

[Spidersbox]

I wonder if it has to do with the new libraries like boost 1.40 and boost 1.55 or  ?? after the distro upgrade I wasn't able to use the older libs.

@Spidersbox u run into same problem with old and new wallet version
old wallet version is used by a few pools without issue

so i expect something at ur setup/compile must be different to them

maybe someone who runs a pool can give ya a hint what might be the difference

it would be good if one pool owner upgrade to new wallet and confirm it runs fine

[NoobKidOnTheBlock]

Can someone suggest the best place to mine this wonderful coin? Like a really good pool or something?

If you take a look here https://chainz.cryptoid.info/dmd/#!extraction you will notice that there are 3 public pools danbi's, MiningField US and Donkey's . the first two are the biggest and both operators are part of the Diamond community. Not sure about the Donkey, but haven't heard any complaints about that pool.

Even though there is no risk of 51% attack coming from the biggest two pools it's always advisable to spread hash among different pools.

You can of course mine solo and possibly get best results, but to do that effectively you need to have a reasonable amount of hashing power.

We're gonna have sharp reward reduction soon so better hurry with mining, you won't be able to mine as many coins as you can now.  

Thanks mate I really appreciate the help and the information.

[NoobKidOnTheBlock]

Hey quick question I downloaded the windows qt wallet from the main page and I added the diamond.conf file to the folder and now my wallet is stuck syncing on block 121045?? Does anyone know why this might be or possibly a way that I can fix that?

[feldenthorne]

I wonder if it has to do with the new libraries like boost 1.40 and boost 1.55 or  ?? after the distro upgrade I wasn't able to use the older libs.

Compiles and runs fine for days with libboost-dev 1.54. I doubt it fails because of that.
Since you're compiling it yourself, don't strip the executable (compile the debug version) and run it through gdb to see where it fails.

You could also try compiling and running the unit tests (if they work? I'm not sure if the tests are functional or not, but I *hope* they are) to see what's working/failing.

Hey quick question I downloaded the windows qt wallet from the main page and I added the diamond.conf file to the folder and now my wallet is stuck syncing on block 121045?? Does anyone know why this might be or possibly a way that I can fix that?

The Diamond blockchain takes forever and a half to sync. If you haven't added the suggested nodes in the first post on this thread, do that. If you have, you could try resetting your router and reconnecting with a new IP. Your client might've gotten banned from the nodes you're connected to for whatever reason.

[Spidersbox]

thanks for the suggestions.
Did you mine from your wallet, that's where mine crashes.

Compiles and runs fine for days with libboost-dev 1.54. I doubt it fails because of that.
Since you're compiling it yourself, don't strip the executable (compile the debug version) and run it through gdb to see where it fails.

[NoobKidOnTheBlock]

Thanks I added some more nodes to my .conf file and now it started downloading the blockchain again so Cheers mate

[pokeytex]

Thanks I added some more nodes to my .conf file and now it started downloading the blockchain again so Cheers mate

Hey Noob - welcome to Diamond!  I saw you around on the Spreadcoin forum!

-pokeytex