Bitcoin Forum
July 18, 2018, 09:22:27 AM *
News: Latest stable version of Bitcoin Core: 0.16.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 [118] 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 ... 826 »
  Print  
Author Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65%  (Read 1181193 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
utahjohn
Hero Member
*****
Offline Offline

Activity: 630
Merit: 500


View Profile
August 01, 2014, 12:44:05 AM
 #2341

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 Smiley
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
polanskiman
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
August 01, 2014, 12:55:26 AM
 #2342

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 Smiley

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 %.

BTC: 1JnH2HVoWnDubGmrXintsNWEaByGRjY8wL
DMD: dZuojpnwkmzqUegQaFk7ynDY8p7zAmG25H
XCN: CKnXnjXsVJzXgqEEqjsMRRc7ohkk6jHsb6
cryptonit
Legendary
*
Offline Offline

Activity: 1666
Merit: 1033


bit.diamonds | artis.eco


View Profile WWW
August 01, 2014, 01:37:36 AM
 #2343


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


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.....

 
  Diamond [DMD]     ARTIS [ATS]  
Scarce✦✦✦✦ Valuable ✦✦✦✦ Secure ✦     ▬ Streaming Money ▬ Creating Value ▬
polanskiman
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
August 01, 2014, 01:39:58 AM
 #2344


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


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...

BTC: 1JnH2HVoWnDubGmrXintsNWEaByGRjY8wL
DMD: dZuojpnwkmzqUegQaFk7ynDY8p7zAmG25H
XCN: CKnXnjXsVJzXgqEEqjsMRRc7ohkk6jHsb6
utahjohn
Hero Member
*****
Offline Offline

Activity: 630
Merit: 500


View Profile
August 01, 2014, 01:56:51 AM
 #2345

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

Activity: 26
Merit: 0


View Profile
August 01, 2014, 02:03:38 AM
 #2346

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.
jhed
Newbie
*
Offline Offline

Activity: 26
Merit: 0


View Profile
August 01, 2014, 02:12:29 AM
 #2347

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.
polanskiman
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
August 01, 2014, 02:17:36 AM
 #2348

@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.

BTC: 1JnH2HVoWnDubGmrXintsNWEaByGRjY8wL
DMD: dZuojpnwkmzqUegQaFk7ynDY8p7zAmG25H
XCN: CKnXnjXsVJzXgqEEqjsMRRc7ohkk6jHsb6
polanskiman
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
August 01, 2014, 02:19:56 AM
 #2349

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?

BTC: 1JnH2HVoWnDubGmrXintsNWEaByGRjY8wL
DMD: dZuojpnwkmzqUegQaFk7ynDY8p7zAmG25H
XCN: CKnXnjXsVJzXgqEEqjsMRRc7ohkk6jHsb6
polanskiman
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
August 01, 2014, 02:22:10 AM
 #2350

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://bitcointalk.org/index.php?topic=580725.msg8115151#msg8115151

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

BTC: 1JnH2HVoWnDubGmrXintsNWEaByGRjY8wL
DMD: dZuojpnwkmzqUegQaFk7ynDY8p7zAmG25H
XCN: CKnXnjXsVJzXgqEEqjsMRRc7ohkk6jHsb6
jhed
Newbie
*
Offline Offline

Activity: 26
Merit: 0


View Profile
August 01, 2014, 02:33:21 AM
 #2351

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
srcxxx
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250


View Profile WWW
August 01, 2014, 02:41:24 AM
 #2352

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 Smiley

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
*
Offline Offline

Activity: 26
Merit: 0


View Profile
August 01, 2014, 02:57:19 AM
 #2353

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://bitcointalk.org/index.php?topic=580725.msg8115151#msg8115151

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

Just now I changed it to :
listen=0
noirc=1
connect=193.68.21.19

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

Though may I ask why you want me to set all that? It effectively makes me a non-participator in the diamond network giving all network control to 193.68.21.19.

polanskiman
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
August 01, 2014, 03:05:07 AM
 #2354

Not getting this at all.

Please read: https://bitcointalk.org/index.php?topic=580725.msg8115151#msg8115151

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

Just now I changed it to :
listen=0
noirc=1
connect=193.68.21.19

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

Though may I ask why you want me to set all that? It effectively makes me a non-participator in the diamond network giving all network control to 193.68.21.19.

You are getting the assertion error where the index.dat file gets corrupted due to a flood of orphans. Other nodes you are connected to are feeding you crap.

Obviously you also need to replace the blockchain with the one provided in the OP. Then start the wallet. The index file is corrupted so making those changes to the .conf is useless if you don't replace the blockchain files first. Basically delete all files except your wallet.dat and the diamond.conf files and replace with the one in the OP.

Using connect=IP and listen=0 makes you indeed a "leecher" if I may say so but this is temporary. You can then revert and change to addnode=ip and listen=1 later on. This is TEMPORARY.

The index corruption issue is not something specific to Diamond. A lot more coins have the same problem and to this date there has been no fixe.

BTC: 1JnH2HVoWnDubGmrXintsNWEaByGRjY8wL
DMD: dZuojpnwkmzqUegQaFk7ynDY8p7zAmG25H
XCN: CKnXnjXsVJzXgqEEqjsMRRc7ohkk6jHsb6
jhed
Newbie
*
Offline Offline

Activity: 26
Merit: 0


View Profile
August 01, 2014, 04:39:56 AM
 #2355

Not getting this at all.

Please read: https://bitcointalk.org/index.php?topic=580725.msg8115151#msg8115151

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

Just now I changed it to :
listen=0
noirc=1
connect=193.68.21.19

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

Though may I ask why you want me to set all that? It effectively makes me a non-participator in the diamond network giving all network control to 193.68.21.19.

You are getting the assertion error where the index.dat file gets corrupted due to a flood of orphans. Other nodes you are connected to are feeding you crap.

Obviously you also need to replace the blockchain with the one provided in the OP. Then start the wallet. The index file is corrupted so making those changes to the .conf is useless if you don't replace the blockchain files first. Basically delete all files except your wallet.dat and the diamond.conf files and replace with the one in the OP.

Using connect=IP and listen=0 makes you indeed a "leecher" if I may say so but this is temporary. You can then revert and change to addnode=ip and listen=1 later on. This is TEMPORARY.

The index corruption issue is not something specific to Diamond. A lot more coins have the same problem and to this date there has been no fixes.

It's happened to a lot more coins? Can you link to a couple so that I can confirm that this won't happen again in the future?

I have a copy of the block chain that generates this error if somebody wants to look at it.
danbi
Sr. Member
****
Offline Offline

Activity: 393
Merit: 250


View Profile
August 01, 2014, 05:26:14 AM
 #2356


If you all are actually able to transmit money into Cryptsy than you are on the correct chain. If I was able to from this chain, than I'm on the correct chain. Crypsty couldn't possibly be connected to both chains. Isn't that right?


Cryptsy is not a measure for the correct chain. It will be very unfortunate if they are on a fork, but this has happened many times before and was sorted out. Frustrating, yes.

They can't be on both chains, correct.

BTC: 15cJkRupKAkGr6sTxj1Uzb6uHbvuRyK1GL
DMD: dJZEqNcjiUiMMd8DKBFS9oMWtArAD2GCHr
danbi
Sr. Member
****
Offline Offline

Activity: 393
Merit: 250


View Profile
August 01, 2014, 05:36:55 AM
 #2357

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.


Let me share a little story with you:

Besides the 193.68.21.19 node I pledged to run for the community (many months ago), I do run few more nodes, which I don't announce but use for tests and .. sometimes as traps for such situations. As I was not paying attention (todo entry already -- provide real-time monitoring) they all were on the wrong chain. All of them were receiving that exact message in their logs. At the 193.68.21.19 they were disconnected/banned too, for the very same reason. I don't want to get too technical on this, but it is apparently this is a form of attack on the network.

The mere reason those nodes ended up that way was they were not properly configured (most are experimental, remember).

BTC: 15cJkRupKAkGr6sTxj1Uzb6uHbvuRyK1GL
DMD: dJZEqNcjiUiMMd8DKBFS9oMWtArAD2GCHr
ilusm
Full Member
***
Offline Offline

Activity: 140
Merit: 100


View Profile
August 01, 2014, 05:38:27 AM
 #2358

Dev,pls work harder and bring us to da moon!

cryptonit
Legendary
*
Offline Offline

Activity: 1666
Merit: 1033


bit.diamonds | artis.eco


View Profile WWW
August 01, 2014, 06:40:01 AM
 #2359

Vote for Diamond DMD on

click pic or this link https://www.mintpal.com/voting#DMD

place #114  now

paying 1 DMD to everyone who reached a new rank

so first one reporting #113 and walletaddress
@ http://bit.diamonds/community/index.php/topic,16.0.html
gets 1 DMD
IMPORTANT only claim rewards on
http://bit.diamonds/community/index.php/topic,16.0.html[/b][/color]

Dont forget our Design Contest!

Quote
Announcement: Design Contest

beat https://bitcointalk.org/index.php?topic=580725.msg7964250#msg7964250

which failed to follow the requirement

Quote
we wont change the coin as main logo itself
(or just in a very similar improved version)

so if u think u can do better
and stay with design and color scheme that fit to our coin logo and our website
http://bit.diamonds/promo.html

please show us ur skills

we will pay some DMD for each serious attempt and at least 200 DMD for the great winner!
(required is logo (have to be very close to original) buttons and icons for ANN thread
and some examples of promo banners where we get all the used art modules to create more similar looking banners)
(if there is nothing that fullfil requirements we can also choose no winner..)


contest will run over a month we will select winner in first week of september

DMD Multipool Lotto
next drawing 3.august 100 DMD
http://multipool.bit.diamonds/

 
  Diamond [DMD]     ARTIS [ATS]  
Scarce✦✦✦✦ Valuable ✦✦✦✦ Secure ✦     ▬ Streaming Money ▬ Creating Value ▬
paladin281978
Hero Member
*****
Offline Offline

Activity: 742
Merit: 500



View Profile
August 01, 2014, 07:11:54 AM
 #2360


danbi



Wallet 2.0.3
I'm on the right chain
Difficulty in a wallet it is equal difficulty on dmdpool.digsys.bg
conf file:
listen=0
noirc=1
connect=193.68.21.19

but why there are a lot of not accepted?

Pages: « 1 ... 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 [118] 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 ... 826 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!