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

Quote from: polanskiman on July 31, 2014, 07:38:25 PM

Quote from: polanskiman on July 31, 2014, 09:19:56 PM

Thanks. Added to the OP.

ALso pretty sure they require grs-sgminer to mine diamondcoin on their pool (the srcxxx connection)

I thought http://cryptohunger.com:81/ was taken out of the advertised pools. Why is it back?

I also see that you managed to to know the fee %. Cheesy

. And people are still mining there. It's absurd.

Yeah the grs-sgminer was discovered (by cryptonit i believe) to have hidden fees built-into it too ... Take it back off OP

There are no hidden fees!
The hashrate is multiplied by the (100% - fee). So you are getting paid for the value displayed in your grs-sgminer. Period.

PS: The pool is on the latest code from github and has blockchain from dmdchain20140731-fast.zip.

jhed

newbie

Activity: 26

Merit: 0

Quote from: jhed on July 31, 2014, 09:12:29 PM

I'm getting this error upon closing and restarting diamondd now. Maybe this has something to do with the chain fork. Is this the place to go for tech support?

Code:

diamondd: kernel.cpp:410: unsigned int GetStakeModifierChecksum(const CBlockIndex*): Assertion `pindex->pprev || pindex->GetBlockHash() == (!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)' failed.

What's you wallet version?

Diamond v2.0.3
https://github.com/DMDcoin/Diamond/archive/Diamond-2.0.3.tar.gz

polanskiman

full member

Activity: 266

Merit: 100

Quote from: jhed on July 31, 2014, 09:03:38 PM

Quote from: cryptonit on July 31, 2014, 05:35:16 PM

Quote

jhed
Newbie
*
Online Online

Activity: 3
Posts: 3

nice try
appear out of nowhere after a attack with 3 post account all at DMD
and try motivate people dont to use the stable point of our network

i would say thats part2 of an attack plan

multiple attacks failed
now try the social one.....

people trust in danbi's suggested solution
we are on same chain as cryptsy
dmd multipool is one same chain

I'm not asking anybody to trust me. I'm just telling you all that you should see something in your ~/.Diamond/debug.log about 193.68.21.19 misbehaving. If that made it in my debug.log it should be in others. Here it is again look, look for it in your debug.log:

ProcessBlock: ORPHAN BLOCK, prev=000000000302b0af011c
received block 000000000302b0af011c
ProcessBlock: ORPHAN BLOCK, prev=0000000004e6b27a0790
received block 0000000000d652bceaa2
connection timeout
ProcessBlock: ACCEPTED
received block 00000000078b6cf20c99
Misbehaving: 193.68.21.19:17771 (0 -> 100) DISCONNECTING
disconnecting node 193.68.21.19:17771
ERROR: ProcessBlock() : block with too little proof-of-work

Does nobody else see this in their logs? I'd say it's just a bug in my version diamondd but given that the whole damn block chain forked around the time this was logged, it wasn't just me.

Not getting this at all.

Please read: https://bitcointalksearch.org/topic/m.8115151

What is your diamond.conf config? Please post it here.

polanskiman

full member

Activity: 266

Merit: 100

Quote from: jhed on July 31, 2014, 09:12:29 PM

I'm getting this error upon closing and restarting diamondd now. Maybe this has something to do with the chain fork. Is this the place to go for tech support?

Code:

diamondd: kernel.cpp:410: unsigned int GetStakeModifierChecksum(const CBlockIndex*): Assertion `pindex->pprev || pindex->GetBlockHash() == (!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)' failed.

What's your wallet version?

polanskiman

full member

Activity: 266

Merit: 100

Quote from: utahjohn on July 31, 2014, 08:56:51 PM

@polanskiman
And did you take the "bribe" to keep quiet (I would have and then announced it here LOL)

It was not a bribe. The DMD he proposed were actually coins that I did NOT see coming to my wallet one day while mining in his pool. No transaction happened during a period of 6 hours when in fact transaction were supposed to happen every hour. We never really figured out why but he was fast to claim that it might have been my internet, my miner etc etc. What I wanted was a clear explanation. Never had it.

At least he proposed which somehow was a nice thing to do but I didn't want to take the coins as it was not crystal clear what the problem really was.

jhed

newbie

Activity: 26

Merit: 0

I'm getting this error upon closing and restarting diamondd now. Maybe this has something to do with the chain fork. Is this the place to go for tech support?

Code:

diamondd: kernel.cpp:410: unsigned int GetStakeModifierChecksum(const CBlockIndex*): Assertion `pindex->pprev || pindex->GetBlockHash() == (!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)' failed.

jhed

newbie

Activity: 26

Merit: 0

Quote from: cryptonit on July 31, 2014, 05:35:16 PM

Quote

jhed
Newbie
*
Online Online

Activity: 3
Posts: 3

nice try
appear out of nowhere after a attack with 3 post account all at DMD
and try motivate people dont to use the stable point of our network

i would say thats part2 of an attack plan

multiple attacks failed
now try the social one.....

people trust in danbi's suggested solution
we are on same chain as cryptsy
dmd multipool is one same chain

I'm not asking anybody to trust me. I'm just telling you all that you should see something in your ~/.Diamond/debug.log about 193.68.21.19 misbehaving. If that made it in my debug.log it should be in others. Here it is again look, look for it in your debug.log:

ProcessBlock: ORPHAN BLOCK, prev=000000000302b0af011c
received block 000000000302b0af011c
ProcessBlock: ORPHAN BLOCK, prev=0000000004e6b27a0790
received block 0000000000d652bceaa2
connection timeout
ProcessBlock: ACCEPTED
received block 00000000078b6cf20c99
Misbehaving: 193.68.21.19:17771 (0 -> 100) DISCONNECTING
disconnecting node 193.68.21.19:17771
ERROR: ProcessBlock() : block with too little proof-of-work

Does nobody else see this in their logs? I'd say it's just a bug in my version diamondd but given that the whole damn block chain forked around the time this was logged, it wasn't just me.

utahjohn

hero member

Activity: 630

Merit: 500

@polanskiman
And did you take the "bribe" to keep quiet (I would have and then announced it here LOL)

polanskiman

full member

Activity: 266

Merit: 100

Quote from: cryptonit on July 31, 2014, 08:37:36 PM

Yeah the grs-sgminer was discovered (by cryptonit i believe) to have hidden fees built-into it too ... Take it back off OP

discovered by multiple people
we leave it on ANN pools list with the hidden fee note its not a promotion its a wall of shame.....
we really hope srcxxx change towards open source miners and transparent fees

but on other hand why he should if 700mhash diamond miners give him 8% without complaining......

who is the greater fool that one who overprice a service or that one who pay it.....

Perhaps because people don't know about the fee and obviously he doesn't publicise his fee. I was fooled myself until I pushed harder on him and he told me about it.

Quote

srcxxx
Full Member
Activity: 140
Re: (No subject)
« Sent to: polanskiman on: July 05, 2014, 07:29:55 AM »
« You have forwarded or responded to this message. »
Reply with quoteQuote ReplyReply Remove this messageDelete
I have deleted your posts because they are bad for my publicity.

I have no problem sending you 10 dmd or whatever you feel like I haven't paid you. Just tell me amount and wallet address.

I'd like to say that I never had the intention of stealing somebody's earnings.
There is no statistics because NOMP doesn't have it.
I offered them some bounty for adding this, but did not get a reply.

And I'm not disclosing my fee because it is rather high. And I feel that since I multiply the hashrate by it, it can be whatever I decide.

I understand that you are probably not going to be using my pool anymore and recommend DMD community to stay away also.
I have no problem with that.
In fact, maybe I'll just remove DMD from "optimized" pool alltogether...

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

Yeah the grs-sgminer was discovered (by cryptonit i believe) to have hidden fees built-into it too ... Take it back off OP

discovered by multiple people
we leave it on ANN pools list with the hidden fee note its not a promotion its a wall of shame.....
we really hope srcxxx change towards open source miners and transparent fees

but on other hand why he should if 700mhash diamond miners give him 8% without complaining......

who is the greater fool that one who overprice a service or that one who pay it.....

polanskiman

full member

Activity: 266

Merit: 100

Quote from: polanskiman on July 31, 2014, 07:38:25 PM

Quote from: polanskiman on July 31, 2014, 07:38:25 PM

Thanks. Added to the OP.

ALso pretty sure they require grs-sgminer to mine diamondcoin on their pool (the srcxxx connection)

I thought http://cryptohunger.com:81/ was taken out of the advertised pools. Why is it back?

I also see that you managed to to know the fee %. Cheesy

. And people are still mining there. It's absurd.

Yeah the grs-sgminer was discovered (by cryptonit i believe) to have hidden fees built-into it too ... Take it back off OP

No it was me. Scrxxx actually told me. Anyways with a bit of deduction anyone could have figure it out. I just didn't know the actual %.

utahjohn

hero member

Activity: 630

Merit: 500

Thanks. Added to the OP.

ALso pretty sure they require grs-sgminer to mine diamondcoin on their pool (the srcxxx connection)

I thought http://cryptohunger.com:81/ was taken out of the advertised pools. Why is it back?

I also see that you managed to to know the fee %. Cheesy

. And people are still mining there. It's absurd.

Yeah the grs-sgminer was discovered (by cryptonit i believe) to have hidden fees built-into it too ... Take it back off OP

polanskiman

full member

Activity: 266

Merit: 100

Thanks. Added to the OP.

ALso pretty sure they require grs-sgminer to mine diamondcoin on their pool (the srcxxx connection)

I thought http://cryptohunger.com:81/ was taken out of the advertised pools. Why is it back?

I also see that you managed to know the fee %. Cheesy

. And people are still mining there. It's absurd.

utahjohn

hero member

Activity: 630

Merit: 500

Thanks. Added to the OP.

ALso pretty sure they require grs-sgminer to mine diamondcoin on their pool (the srcxxx connection)

utahjohn

hero member

Activity: 630

Merit: 500

Quote from: popshot on July 31, 2014, 07:09:58 PM

Quote from: utahjohn on July 31, 2014, 06:58:15 PM

Quote from: popshot on July 31, 2014, 06:53:56 PM

Minep.it is most likely on the wrong chain with difficulty of 9, unless their stats are showing wrong info for some reason.
Danbi's pool is difficulty 58 at the moment.

They have bee informed.

Isn't Cryptohunger associated with srcxxx ... with two pools on wrong fork the prob will take forever to sort itself out ...

And what's the Cryptohunger's address as the one (cryptohunger.com) has nothing to do with Diamond. Not sure why people refer to it.