Author

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

member
Activity: 70
Merit: 10
full member
Activity: 140
Merit: 100
Now the DMD price is tanking again. Please fix things soon or this'll end up like most alts.
A long time nothing.. then spike and finally a crash flat down forever..

This is promising, but we need
a. finally working pools to make mining accessable to the average user

b. cryptsy desperately needs to fix their side on the wallet (they cant be seriously taking THIS long)
Maybe you devs can talk to them? Your messages might weigh more than normal users. Users cry for any crapcoin to be added so they might not even read that stuff.

c. working PoS and a good explanation and guide in the first post for anyone to see. Or even better in the wallet since that's what users are looking at mostly.

d. as soon as everything works.. marketing. If it is to become a gold like commodity in the cryptoworld we need it classy though.
No flashy fx by some 16 y/o who downloaded photoshop but something classy that shows why DMD is better than 99999 other alts.

e. total coverage on all exchanges
I was shocked to discover we're not on bter

Please everybody help with whatever you can do. Coders help with technical testing, users can talk to exchanges. Maybe some of you know any exchange operators?
And marketing wise please dont even think about these fuckin gambling sites.. they are a gold mine to their operators, but they shouldnt be associated with something serious like DMD. It should be associated with something like that for example: http://www.mintagemastermind.com/index.html

Plus speed does count now since there's a lot of similar projects to DMD like bitbar etc. The first one to be established is going to stick for a long time.
Like litecoin. Really, what does it do any better/different? It's almost like a perfect clone. It was just there first so people still stick to it.

So I hope the typing was useful to some extent at least and we as community plus devs get this going right. You can only mess up so many times before the mass loses faith/interest.
sr. member
Activity: 308
Merit: 251
I like big BITS and I cannot lie.
Watching the diff spike and stay in the upper 60's makes me think your pools are working 'mo 'bedda.
full member
Activity: 210
Merit: 100
Your welcome, sounds good! Cheesy


pcmerc~
hero member
Activity: 774
Merit: 554
CEO Diamond Foundation
OSX wallet compiled from latest source - http://pcmerc.com/files/Diamond-Qt.dmg

Please report any issues to me so I may address them.


pcmerc~
http://kryptochaos.com
http://pool.kryptochaos.com

Looks great, but when I opened the Debug Window, I saw that you compiled it with OpenSSL 1.0.1f.  Could you compile it with 1.0.1g to prevent the Heartbleed issue?

Thanks,



Re-download the wallet as it's been compiled against openssl-1.0.1g

This now displays the correct openssl version.

pcmerc~
http://kryptochaos.com
http://pool.kryptochaos.com

Thank you pcmerc for taking initiative and compiling the client for Mac.

I'll add it to the main post if you don't mind.
full member
Activity: 210
Merit: 100
OSX wallet compiled from latest source - http://pcmerc.com/files/Diamond-Qt.dmg

Please report any issues to me so I may address them.


pcmerc~
http://kryptochaos.com
http://pool.kryptochaos.com

Looks great, but when I opened the Debug Window, I saw that you compiled it with OpenSSL 1.0.1f.  Could you compile it with 1.0.1g to prevent the Heartbleed issue?

Thanks,



Re-download the wallet as it's been compiled against openssl-1.0.1g

This now displays the correct openssl version.

pcmerc~
http://kryptochaos.com
http://pool.kryptochaos.com
sr. member
Activity: 393
Merit: 250
What seems to be the issues that the pools are having?

CheckBlock() : hashMerkleRoot mismatch

I believe to already know what is causing this and now am working on three possible solutions. Let's hope there is enough time ...
full member
Activity: 121
Merit: 100
Is there a dev working to fix this issue?  Would love to add diamond to our pool!

pool mining with actual wallet is only possible with a proprietary pool configuration

afaik only ahmed is working to set up such a pool and not willing to share results of his invested time

easy (close to standard pool setup) pool support will be implemented in next diamond release

for now its solo miners paradise

diamond dev team did decide instead of release multiple wallets with small fixed
we going to wait with release until we have a wallet that fulfill our quality criteria

meanwhile network stay in this stable solo mining status

actual wallet runs stable solo mining runs stable
transactions run stable

everything else will be part of next release



Any rough guess when that will be? 

P.S.  Thanks ahmed! Tongue
legendary
Activity: 3052
Merit: 1053
bit.diamonds | uNiq.diamonds
Is there a dev working to fix this issue?  Would love to add diamond to our pool!

pool mining with actual wallet is only possible with a proprietary pool configuration

afaik only ahmed is working to set up such a pool and not willing to share results of his invested time

easy (close to standard pool setup) pool support will be implemented in next diamond release

for now its solo miners paradise

diamond dev team did decide instead of release multiple wallets with small fixed
we going to wait with release until we have a wallet that fulfill our quality criteria

meanwhile network stay in this stable solo mining status

actual wallet runs stable solo mining runs stable
transactions run stable

everything else will be part of next release
full member
Activity: 121
Merit: 100
Our attempt at a pool came up with the usual result:

 [Pool]      [Diamondcoin] (Thread 1) We thought a block was found but it was rejected by the daemon, share data: {"job":"29","ip":"XXX","worker":"XXXXXX","height":393842,"blockReward":1000000,"poolReward":990000,"difficulty":0.02,"shareDiff":"15839.58450802","blockDiff":10945.29713536,"blockDiffActual":42.755066935,"blockHash":0000000004232de679778fc6eb680536643394d6911dac3175960d1337a3fa5c"}



Granted total time was about 10 minutes of effort and hashing.

I hope I'm a newb, and block rewards really arent 1000000


And thats a very long way of saying percentage...

Is there a dev working to fix this issue?  Would love to add diamond to our pool!
legendary
Activity: 3052
Merit: 1053
bit.diamonds | uNiq.diamonds

Out of curiosity, I pinged the nodes in the original launch post https://bitcointalksearch.org/topic/m.6507800 and they all timed out.  Sad



a lot servers including ours (at least mine) deactivate ping (icmp echo request)
and a coin network dont need this few host in add node for anything alse than to find a startpoint to search for peers
basical our nodes just provide a easy startpoint for your wallet to find peers
newbie
Activity: 17
Merit: 0
Any word on how Cryptsy is doing with getting DMD back up?
member
Activity: 130
Merit: 10
Good, then it wasnt only me getting rejects. Now we know that.
No. I've tried this pool a few minutes ago - only rejects Sad
Used sgminer with groestl algo, this is correct?
full member
Activity: 210
Merit: 100
Yes, that's whats odd. openssl version returns 1.0.1g

I've dumped my macports & refreshing it.

I'll kick out a new compile once it completes.



pcmerc~
full member
Activity: 210
Merit: 100
Weird! Looking at it some more.
full member
Activity: 210
Merit: 100
OSX Wallet - http://pcmerc.com/files/Diamond-Qt.dmg

Please let me know if there are any issues so I may address them.

This is a recompile again openssl-1.0.1g Smiley

Thanks for the heads up on the openssl.

pcmerc~
http://kryptochaos.com
http://pool.kryptochaos.com
full member
Activity: 507
Merit: 100
What seems to be the issues that the pools are having?
full member
Activity: 210
Merit: 100
full member
Activity: 210
Merit: 100
OSX wallet compiled from latest source - http://pcmerc.com/files/Diamond-Qt.dmg

Please report any issues to me so I may address them.


pcmerc~
http://kryptochaos.com
http://pool.kryptochaos.com
HR
legendary
Activity: 1176
Merit: 1011
Transparency & Integrity
Still solo mining.

24 hours now WITHOUT a single coin though, 36 hours with just 1 (one machine that's never had even one), and that after getting off to a nice start that met with expectations.

The overall diff picture hasn't changed in that time (roughly the same as 3 days ago while trending ever so slightly higher).

What has changed was the mention of "secret" private pools.
https://bitcointalksearch.org/topic/m.6552787
https://bitcointalk.org/index.php?topic=580725.msg6550578;topicseen#msg6550578

If they're big, then that puts the little solo miner out of business. But is that really true? Statistically speaking, my miners should have the same probabilities of solving a block (as in BLOCK!) regardless of whether the entire network were all one huge pool except for little old me, or the entire network were nothing but solo miners with me included, correct?

1 big pool + little old me = same probabilities = all solo miners with little old me included, correct?

The so called "lottery ticket" is exactly the same for little old me, and it's completely independent
of the make-up of the rest of that particular statistical universe, correct?



24 hours with zilch is really stacking the odds though.

Something smells fishy. Anyone else experiencing something similar?



Got up in the middle of the night to take a piss, and it came to me, it's called:


LATENCY

and I then proceded to think to myself, "you idiot"!


If it's taking forever to submit, you're not going to get
anything, even if your theoretical odds are 1 in 75 to
1 in 125 (depending on the diff at any given moment).


And that's not to mention what would be happening
if huge concentrated hashrates (secret pools)
are right next to active nodes.


Out of curiosity, I pinged the nodes in the original launch post https://bitcointalksearch.org/topic/m.6507800 and they all timed out.  Sad


I'd post further findings, but since nobody else has had similar problems, why bother?

I'm going back to bed. I've got a long, long hard day tomorrow. Good luck to the other two or three of you who are troubleshooting.
Jump to: