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

isnt 5970 a card with 2x5870 chip? if so then even 5870 get the same hash rate as 7950

its not strange
its know that 59xx cards have very high performance on groestl algo

it's really strange, got 11 MHs on an old HD5970 - my HD7950 = 5.3 MHs, HD7970 = 7.1 MHs...

everyone had his chance to mine noone got any advantage
after like 30 mined blocks the wallet was posted for everyone to be used
a few minutes later diff did raise and show people where joining the mining

if someone cant set up solomine
if someone have no access to a windows pc
if someones wallet crashed more that the other ones
is that unfair?


what did others gain
what he lost?

if u didnt mine diamonds last few weeks and months
when diamond difficulty was low as hell
should we rollback because u lost something?

if u didnt mine last day where difficulty was very high after a short time already
should we rollback?

what u expect from a rollback?
easy diamonds from beeing one of the first miner?

diamond is not that kind of coin
after restart network it needed like 3 blocks until diff was adjusted to be at 1 dmd per minute there was no unfair fast mining


the mining rewards will stay for sure at least 1 1/2 years at the same 1 dmd each block until 1500000 total coins reached

that i call fair

network stay running in current blockchain

i post a crashfixed wallet in a few minutes
ui glitch (white mouseovers) isnt fixed will follow in later wallet
for now stability wallet release is more important that wait a lot more hours

as announced by pit_DMD linux wallet and source and some support to compile own linux wallets will follow

How does people get 7mh hash rate one 280x?

i am running with this setting on 280x core/mem 1027/1250

--lookup-gap 2 --thread-concurrency 8192 -g 2 -I 20 -w 256

the best  i can get is 2.1mh

We tested wallet half to a day before release it to people. You should know that: test environment is very different from in real life. You can't cover all cases and we did try as much as possible. We always want to do the best for miners, who go with us, believe us, trust us and fell sorry when we made a mistake.

Hi johndec2, I don't wan to complain but it's very frustrating because I almost didn't sleep last night trying to get the daemon to compile. It failed and I tried the wallet. The wallet got compiled but miners didn't connect. Many core APIs were not available in the debug console. I know the devs are under pressure but IMHO a broken code shouldn't be released at all. A delay won't make users angry more than wasted time trying to get thing done but failed instead.

Sorry if I sounded harsh.

Regards,

AizenSou, you are being a little unfair to the devs.  The early release was forced on them before they were ready. I'm an experienced solo miner but it still took me at least 2 hours to get everything sorted out. Being in a time zone that made me miss the first 7 or 8 hours of the release was also bad luck for me.  

Shit happens, live with it.  They tried to be as fair as possible but it is not a perfect world.  Yes, experienced miners in the right time zone took advantage of the imperfections of the new wallet. I would have too if I hadn't been asleep. They might be called diamonds but they are only worth 40-50 cents each.  So you really haven't lost out all that badly

Yes of course i could connect my miner to the wallet. I've allready found some blocks. I'm sorry, but i don't use linux.

That's my diamond config

That's what i did. Deleting everything and sync over night.
Now i'm solo mining for about 2 hours. I hope it is stable until the new wallet is released.

Another test complete:

Delete everything and start again, run diamond qt. then install wallet.dat in roaming folder, install block chain and db downloads, run and sync diamond qt.

Runs forever without problems (3 hours in my test) as long as you don't close the program.

As soon as you close the client/wallet and restart, you get the crash error.



Going to do a manual online sync now.

Exactly what my testing and limited knowledge was leading me to think.


Stable is better than fast. I don't mind waiting a bit longer on startup as long as it performs once started. I'll take known-good over beta any day! 


No prob. It's Murphy's Law, and shit happens.


Like the fantastic team you are!!


Price is holding solid too and looks ready to rocket. 0.0023 is the next stop.

short update:

until yet all tests are good no single crash in new release candidate

give us a bit more time testing we release wallet in a few hours
we wana get the tooltip bugfix into this release too while we testing it allready regarding stability

I also had problems with my original conf file, which is basically the same file I use to mine every other coin on the planet, including groestlcoin. When I used the sample conf file it worked. Try it.

rpcuser=whatever you like
rpcpassword=whatever you like
rpcport=17772
rpcallowip=*
addnode=213.229.0.41
addnode=193.77.159.166
addnode=113.168.158.16
server=1
listen=1
daemon=1

I have tried everything. The daemon ends up not compiled so I must use the Qt-client. It syncs finally fine after I copy all the blockchain and txdb stuff in .Diamond folder. But I can't get my miners connect to the client to mine. Hier my .conf file:


I got Connection refused when I tried to connect to 17772 port and time out error when connect to 17771 port.  
Very confusing and frustrating indeed.

difficulty is rising fast

Thank you!

thx for update

so our ambitious plan where to high we packed to much new stuff into the new wallet
and because old network stuck we had to release it without enought test time

BUT with active dev such problem can be solved
and our network is running on groestl and will stay running on it

everything u mine every transaction is save

the upcoming fixed wallet will just change the database system where data is stored local back to the prooved old system


open issue list now:

wallet crashes (will be solved with next wakket release soon)
linux headless client need to be compiled once we release new source
some ui glitches with invisible text on mouseover

missing pools (most poolowner waiting for headless linux client..)

edit:

just after wrote this i got beta version of crashfixed wallet
will give ya feedback asap

We're testing the new fix, you may have to download another blockchain (we restore to old structure database) and new wallet. It's running without error. Will release it soon.