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

[whocares]

stupid 360 second timer!

I just noticed that you also are using a different port in your miner's conf file. You used 17702. my example conf uses 17772. You should change one or the other. As long as they both match. Also, if you make changes to your diamondcoin.conf file, close and then re-open your wallet.

Thanks.
I saw, it was my fault and corrected it, but I can't get it work - same error as above.

Your are pointing your miner to 127.0.0.1, but you didn't include it in your config.  Try adding to your config file:

rpcallowip=127.0.0.1

Or just point your miner to the ip of the computer that has wallet.

I changed "url" to ip of the mining rig and now it works.
Thanks guys!

[OICU812]

stupid 360 second timer!

I just noticed that you also are using a different port in your miner's conf file. You used 17702. my example conf uses 17772. You should change one or the other. As long as they both match. Also, if you make changes to your diamondcoin.conf file, close and then re-open your wallet.

Thanks.
I saw, it was my fault and corrected it, but I can't get it work - same error as above.

Your are pointing your miner to 127.0.0.1, but you didn't include it in your config.  Try adding to your config file:

rpcallowip=127.0.0.1

Or just point your miner to the ip of the computer that has wallet.

I changed "url" to ip of the mining rig and now it works.
Thanks guys!

Congrats! You're now a Solo miner! 

[whocares]

Congrats! You're now a Solo miner! 

Approved  .

Another problem : I found a block, but got a caching error and didn't submit it ? Why ?

[m5j0r]

I can't seem to get this wallet to work:
https://bitcointalk.org/index.php?topic=580725.msg6507800#msg6507800

Both files are in %appdata% since datadir doesn't yet work. diamond.conf is there as written in the post.
It instantly crashes. Any suggestions?

empty folders: wallet starts up and tries to sync
with the supplied files: instacrash

a lot of people seem to have the same problem. it would be great to finally have a working wallet again, since DMD has been down for ages already.

[OICU812]

Congrats! You're now a Solo miner! 

Approved  .

Another problem : I found a block, but got a caching error and didn't submit it ? Why ?

hmmmm.... haven't seen that one before. I have had a stale share submission error before followed by a block rejected error. I'm guessing that would have to do with a latency issue on my end to the coin network? I've just taken it as one of those things you see when solo mining (not that I have massive experience it it, mind you). I've attempted to solo a number of coins and while I do occasionally get a block, I've also gotten that dang stale share submission / block rejected message from time to time.

What miner are you using?

[kyma]

hey new to DMD here and and having trouble syncing my mac wallet. v1.0.4.0

it seems the blockchain has downloaded but the arrows are still spinning and it says (out of sync)

[danbi]

Code:

root@vps:/dmd/DMD_Private/src# make -f makefile.unix diamondd USE_UPNP=-
/bin/sh ../share/genbuild.sh obj/build.h
g++ -c -O2 -msse2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -I/dmd/DMD_Private/src -I/dmd/DMD_Private/src/obj -DUSE_IPV6=1 -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/kernel.d -o obj/kernel.o kernel.cpp
kernel.cpp:6:18: fatal error: QDebug: No such file or directory
compilation terminated.
make: *** [obj/kernel.o] Error 1

Any help?

You need to provide path to the Qt include files. On my system this is /usr/local/include/qt4. The code is buggy anyway, you need to fix the kernel.cpp file and change the line to read

#include <QtCore/QDebug>

You also need to provide path to the leveldb includes. Mine ended up like this:

DEFS += $(addprefix -I,$(CURDIR) $(CURDIR)/obj $(BOOST_INCLUDE_PATH) $(BDB_INCLUDE_PATH) $(OPENSSL_INCLUDE_PATH) leveldb/include /usr/local/include/qt4)

But, I am still not done, as the code does not properly link the groestl code in.. A very experimental and inconsistent code, so far.

[iru786]

Not able to download blk0001.dat from Mega... Can someone zip it and place a mirror?

[DLow]

No pools on launch?

Yeah, sucks.

[popshot]

I can't seem to get this wallet to work:
https://bitcointalk.org/index.php?topic=580725.msg6507800#msg6507800

Both files are in %appdata% since datadir doesn't yet work. diamond.conf is there as written in the post.
It instantly crashes. Any suggestions?

empty folders: wallet starts up and tries to sync
with the supplied files: instacrash

a lot of people seem to have the same problem. it would be great to finally have a working wallet again, since DMD has been down for ages already.

I've flowed the instructions and installed successfully with syncing Block Chain without any problems or crashes on 4 different computers (different in specs and OSs Win 7 & Server). Haven seen any other person highlighting this particular instant crash problem.

What I did I deleted everything  form AppData/Roaming/Diamond. I transferred all the files and one folder form the zipped file (txleveldb.zip) to Diamond folder. I also transferred the blockchain database there. I started the client and everything worked like it was supposed to.

It's hard to pinpoint to exact cause of your problem, could you try to install it in the other machine?

[popshot]

Not able to download blk0001.dat from Mega... Can someone zip it and place a mirror?

What do you mean? I've just test downloaded it again.

Change your web browser it helped me with denied access on a server.

Mirror from what provider? I could upload it to drop box or something similar but Mega is really fast and least problematic.

[popshot]

In the new wallet when I mouse over a block mined I get a blank text block. It looks like all recent transactions are effected.

Yes, it's the wrong color of the font, this will be updated shortly in non mandatory patch.  We are aware of it.
Anyway, this UI design is temporary and would have been definitely better, without silly moments like the ones with the tooltip you're experiencing, if we stuck to the planned release date. But life is life and had different plans for this release    

[popshot]

hey new to DMD here and and having trouble syncing my mac wallet. v1.0.4.0

it seems the blockchain has downloaded but the arrows are still spinning and it says (out of sync)

Mac wallet. v1.0.4.0 is an old one and will no longer sync with the new Block Chain.

I've contacted a person asking to compile the new client for Mac users. It's coming.

[popshot]

A very experimental and inconsistent code, so far.

It's definitely not my area of expertise and this will be discussed and worked on by our dev but the algorithm switch hasn't been attempted in any of the coins (not counting easy switch to skrypt-n). The dev had to devise new ways so I would say it is novel. If you can contribute to the betterment of this coin please do so, we are open for community input.

[popshot]

I've found the solution for our problem....

Thank you for that, this certainly helps. I'll try to recreate that scenario.

Now after the release we are no longer FORCED into rushing things with crazy pace so we'll look into all the quirks that you guys are reporting.  

[cryptonit]

gosh I like DMD but I hate half-assed clients

same do we
we didnt deliver the quality we where aiming for
BUT we did get network running on groestl algo

please keep in mind because of old network stuck we had to release a week pre shedule

updated wallets will be released and fix this troubles some experience now

the network is running and we are the first coin who managed to switch algo towards groestl
this alone make me proud of my dev team

since we have a full time dev i can gurantee we will fix all issues and create more features and gimmicks in the near future

meanwhile i have to say thanks to our comuinity for your support
and your understanding that great things need time
as they say "rome wasnt build in a day"

[Cheena]

gosh I like DMD but I hate half-assed clients

same do we
we didnt deliver the quality we where aiming for
BUT we did get network running on groestl algo

please keep in mind because of old network stuck we had to release a week pre shedule

updated wallets will be released and fix this troubles some experience now

the network is running and we are the first coin who managed to switch algo towards groestl
this alone make me proud of my dev team

since we have a full time dev i can gurantee we will fix all issues and create more features and gimmicks in the near future

meanwhile i have to say thanks to our comuinity for your support
and your understanding that great things need time
as they say "rome wasnt build in a day"

Cool, I appreciate your efforts, keep up the good work.

I read somewhere about merged mining with groestl coin, is it in the pipeline ?

[danbi]

A very experimental and inconsistent code, so far.

It's definitely not my area of expertise and this will be discussed and worked on by our dev but the algorithm switch hasn't been attempted in any of the coins (not counting easy switch to skrypt-n). The dev had to devise new ways so I would say it is novel. If you can contribute to the betterment of this coin please do so, we are open for community input.

I will of course contribute any hints and code fixes I can, unfortunately I happen to be busy (and away from computers) most of the time this week. So it might be slow

[cryptonit]

I read somewhere about merged mining with groestl coin, is it in the pipeline ?

we focus on stabilze existing features first
but yes merged mining is on the todo list
groestlcoin is giving a 100000GRS reward as bounty too if someone interested

[AizenSou]

Since i got my first confirmed block with the new wallet, the wallet crashes every time i will start it.

I will post you my windows error report, i know it is in german but maybe it will help you

Problemsignatur:
  Problemereignisname:   BEX
  Anwendungsname:   diamond-qt.exe
  Anwendungsversion:   0.7.2.0
  Anwendungszeitstempel:   53638cdb
  Fehlermodulname:   StackHash_0a9e
  Fehlermodulversion:   0.0.0.0
  Fehlermodulzeitstempel:   00000000
  Ausnahmeoffset:   646e696b
  Ausnahmecode:   c0000005
  Ausnahmedaten:   00000008
  Betriebsystemversion:   6.1.7601.2.1.0.256.1
  Gebietsschema-ID:   1031
  Zusatzinformation 1:   0a9e
  Zusatzinformation 2:   0a9e372d3b4ad19135b953a78882e789
  Zusatzinformation 3:   0a9e
  Zusatzinformation 4:   0a9e372d3b4ad19135b953a78882e789

Hi danbi,

You solved the problem with the nasty bug of linking groestl in kernel ? Could you provide more instruction? I got so far with your help from last page to this:

Code:

obj/checkpoints.o: In function `Checkpoints::WriteSyncCheckpoint(uint256 const&)':
and a lot of undefined reference

Thanks in advance.