[ANN][SCRYPT] KlondikeCoin ★ Cryptsy.com ★ Prepaid VISA Cards ★ 0% Premine [KDC]

[G440T]

I'm looking at the KGW bug now. This does mean another hard fork, before i put it live i'd like someone else to check the code. 24kilo are you willing?

Thanks Dave, I guess you're familiar with this? https://bitcointalk.org/index.php?topic=552895.0

[KDC_Dave]

I'm looking at the KGW bug now. This does mean another hard fork, before i put it live i'd like someone else to check the code. 24kilo are you willing?

Thanks Dave, I guess you're familiar with this? https://bitcointalk.org/index.php?topic=552895.0

Yes have been reading through it

[KDC_Dave]

OK i've added changes for the KGW fix to the development branch here: https://github.com/klondikecoin/klondikecoin/tree/Development

Can anyone who know's what they are doing double check my work, before i merge it with the live version? (i have also pm'd fuse)

[24Kilo]

There is no need to rush this hard-fork... Fuse will need a day or two to double check the code.

At this point, no one is going to use this exploit against KDC... at a network hash-rate of less than 100Mh/s... a straight up 51% attack would be easier and a guaranteed success compared the aggro of a using the KGW exploit. The exploit is most attractive for attacking networks where a 51% attack is not possible, because the KGW exploit only needs about 10% of the network hash-rate to be effective, so it makes the big networks vulnerable.

In the case of KDC, a 51% attack is instant and effective... and not much hash-rate would be needed... in fact... I could launch a 51% by myself at the moment with ease.

So more important to take the time to ensure the fix is implemented properly, add a few checkpoints, and make sure the hard fork is deployed after a considerable publicity and notice to all exchanges, merchants, users, and miners than rushing it because of the fear of being exploited.

[KDC_Dave]

There is no need to rush this hard-fork... Fuse will need a day or two to double check the code.

At this point, no one is going to use this exploit against KDC... at a network hash-rate of less than 100Mh/s... a straight up 51% attack would be easier and a guaranteed success compared the aggro of a using the KGW exploit. The exploit is most attractive for attacking networks where a 51% attack is not possible, because the KGW exploit only needs about 10% of the network hash-rate to be effective, so it makes the big networks vulnerable.

In the case of KDC, a 51% attack is instant and effective... and not much hash-rate would be needed... in fact... I could launch a 51% by myself at the moment with ease.

So more important to take the time to ensure the fix is implemented properly, add a few checkpoints, and make sure the hard fork is deployed after a considerable publicity and notice to all exchanges, merchants, users, and miners than rushing it because of the fear of being exploited.

Agreed! 24kilo you and fuse interested in any of the positions we put up for the coin?

[LeBarton]

There is no need to rush this hard-fork... Fuse will need a day or two to double check the code.

At this point, no one is going to use this exploit against KDC... at a network hash-rate of less than 100Mh/s... a straight up 51% attack would be easier and a guaranteed success compared the aggro of a using the KGW exploit. The exploit is most attractive for attacking networks where a 51% attack is not possible, because the KGW exploit only needs about 10% of the network hash-rate to be effective, so it makes the big networks vulnerable.

In the case of KDC, a 51% attack is instant and effective... and not much hash-rate would be needed... in fact... I could launch a 51% by myself at the moment with ease.

So more important to take the time to ensure the fix is implemented properly, add a few checkpoints, and make sure the hard fork is deployed after a considerable publicity and notice to all exchanges, merchants, users, and miners than rushing it because of the fear of being exploited.

Agreed! 24kilo you and fuse interested in any of the positions we put up for the coin?

Would be really great to have a dev team with all of you guys !

[barryzand]

There is no need to rush this hard-fork... Fuse will need a day or two to double check the code.

At this point, no one is going to use this exploit against KDC... at a network hash-rate of less than 100Mh/s... a straight up 51% attack would be easier and a guaranteed success compared the aggro of a using the KGW exploit. The exploit is most attractive for attacking networks where a 51% attack is not possible, because the KGW exploit only needs about 10% of the network hash-rate to be effective, so it makes the big networks vulnerable.

In the case of KDC, a 51% attack is instant and effective... and not much hash-rate would be needed... in fact... I could launch a 51% by myself at the moment with ease.

So more important to take the time to ensure the fix is implemented properly, add a few checkpoints, and make sure the hard fork is deployed after a considerable publicity and notice to all exchanges, merchants, users, and miners than rushing it because of the fear of being exploited.

Agreed! 24kilo you and fuse interested in any of the positions we put up for the coin?

Would be really great to have a dev team with all of you guys !

+1

You seem to know what youre talking about indeed Would be nice if you join man

[kahir]

Good thing we have Dev team to help us with this issue ....

[bangomatic]

There is no need to rush this hard-fork... Fuse will need a day or two to double check the code.

At this point, no one is going to use this exploit against KDC... at a network hash-rate of less than 100Mh/s... a straight up 51% attack would be easier and a guaranteed success compared the aggro of a using the KGW exploit. The exploit is most attractive for attacking networks where a 51% attack is not possible, because the KGW exploit only needs about 10% of the network hash-rate to be effective, so it makes the big networks vulnerable.

In the case of KDC, a 51% attack is instant and effective... and not much hash-rate would be needed... in fact... I could launch a 51% by myself at the moment with ease.

So more important to take the time to ensure the fix is implemented properly, add a few checkpoints, and make sure the hard fork is deployed after a considerable publicity and notice to all exchanges, merchants, users, and miners than rushing it because of the fear of being exploited.

Agreed! 24kilo you and fuse interested in any of the positions we put up for the coin?

Would be really great to have a dev team with all of you guys !

+1 with KDC_Dave, Fuse, 24Kilo  KLONDIKE could be unstoppable!!!

[jackdminer]

There is no need to rush this hard-fork... Fuse will need a day or two to double check the code.

At this point, no one is going to use this exploit against KDC... at a network hash-rate of less than 100Mh/s... a straight up 51% attack would be easier and a guaranteed success compared the aggro of a using the KGW exploit. The exploit is most attractive for attacking networks where a 51% attack is not possible, because the KGW exploit only needs about 10% of the network hash-rate to be effective, so it makes the big networks vulnerable.

In the case of KDC, a 51% attack is instant and effective... and not much hash-rate would be needed... in fact... I could launch a 51% by myself at the moment with ease.

So more important to take the time to ensure the fix is implemented properly, add a few checkpoints, and make sure the hard fork is deployed after a considerable publicity and notice to all exchanges, merchants, users, and miners than rushing it because of the fear of being exploited.

If there is going to be another hard fork perhaps we should rethink the block payout...  Hash is king and you have to pay for it.

I would suggest a fixed reward for all future blocks (no halving).  Remember the more blocks hashed the less dilutive a payout is.

why not 88? 
http://en.wikipedia.org/wiki/88_(number)

[kahir]

There is no need to rush this hard-fork... Fuse will need a day or two to double check the code.

At this point, no one is going to use this exploit against KDC... at a network hash-rate of less than 100Mh/s... a straight up 51% attack would be easier and a guaranteed success compared the aggro of a using the KGW exploit. The exploit is most attractive for attacking networks where a 51% attack is not possible, because the KGW exploit only needs about 10% of the network hash-rate to be effective, so it makes the big networks vulnerable.

In the case of KDC, a 51% attack is instant and effective... and not much hash-rate would be needed... in fact... I could launch a 51% by myself at the moment with ease.

So more important to take the time to ensure the fix is implemented properly, add a few checkpoints, and make sure the hard fork is deployed after a considerable publicity and notice to all exchanges, merchants, users, and miners than rushing it because of the fear of being exploited.

If there is going to be another hard fork perhaps we should rethink the block payout...  Hash is king and you have to pay for it.

I would suggest a fixed reward for all future blocks (no halving).  Remember the more blocks hashed the less dilutive a payout is.

why not 88?  
http://en.wikipedia.org/wiki/88_(number)

reward is 8 and price is around 1500-1800 ....

so u want make it 88 ....

[jackdminer]

There is no need to rush this hard-fork... Fuse will need a day or two to double check the code.

At this point, no one is going to use this exploit against KDC... at a network hash-rate of less than 100Mh/s... a straight up 51% attack would be easier and a guaranteed success compared the aggro of a using the KGW exploit. The exploit is most attractive for attacking networks where a 51% attack is not possible, because the KGW exploit only needs about 10% of the network hash-rate to be effective, so it makes the big networks vulnerable.

In the case of KDC, a 51% attack is instant and effective... and not much hash-rate would be needed... in fact... I could launch a 51% by myself at the moment with ease.

So more important to take the time to ensure the fix is implemented properly, add a few checkpoints, and make sure the hard fork is deployed after a considerable publicity and notice to all exchanges, merchants, users, and miners than rushing it because of the fear of being exploited.

If there is going to be another hard fork perhaps we should rethink the block payout...  Hash is king and you have to pay for it.

I would suggest a fixed reward for all future blocks (no halving).  Remember the more blocks hashed the less dilutive a payout is.

why not 88? 
http://en.wikipedia.org/wiki/88_(number)

reward is 8 and price is around 1500-1800 ....

so u want make it 88 .... where is your brains ?

My brain is on the meager 60Mh/s and the security of the coin.  Where else should your brain be?  88 coins a minute buys you a few hundred Mh/s even at lower prices.

It's not like 88 payout tanks the coin 80%.  The more blocks that are produced the less inflation a new block creates. 



Unless of course you want a coin with 20Mh/s NET HASH and anyone with time to kill can 51% attack your coin... 

Don't focus on the price, worry about the underpinnings.
 

[LeBarton]

There is no need to rush this hard-fork... Fuse will need a day or two to double check the code.

At this point, no one is going to use this exploit against KDC... at a network hash-rate of less than 100Mh/s... a straight up 51% attack would be easier and a guaranteed success compared the aggro of a using the KGW exploit. The exploit is most attractive for attacking networks where a 51% attack is not possible, because the KGW exploit only needs about 10% of the network hash-rate to be effective, so it makes the big networks vulnerable.

In the case of KDC, a 51% attack is instant and effective... and not much hash-rate would be needed... in fact... I could launch a 51% by myself at the moment with ease.

So more important to take the time to ensure the fix is implemented properly, add a few checkpoints, and make sure the hard fork is deployed after a considerable publicity and notice to all exchanges, merchants, users, and miners than rushing it because of the fear of being exploited.

If there is going to be another hard fork perhaps we should rethink the block payout...  Hash is king and you have to pay for it.

I would suggest a fixed reward for all future blocks (no halving).  Remember the more blocks hashed the less dilutive a payout is.

why not 88? 
http://en.wikipedia.org/wiki/88_(number)

reward is 8 and price is around 1500-1800 ....

so u want make it 88 .... where is your brains ?

My brain is on the meager 60Mh/s and the security of the coin.  Where else should your brain be?  88 coins a minute buys you a few hundred Mh/s even at lower prices.

It's not like 88 payout tanks the coin 80%.  The more blocks that are produced the less inflation a new block creates. 



Unless of course you want a coin with 20Mh/s NET HASH and anyone with time to kill can 51% attack your coin... 

Don't focus on the price, worry about the underpinnings.
 

Lol you are the one who are most focused on the price, you turned off your rigs because you hadn't enough profit.

[kahir]

go read my posts ......

yes ... i turned off my rig to mine kdc ....

i mine most profitable - dump for kdc buys ....

that would push price up ... and attract more miners to kdc ... thats called using your brain

[jackdminer]

There is no need to rush this hard-fork... Fuse will need a day or two to double check the code.

At this point, no one is going to use this exploit against KDC... at a network hash-rate of less than 100Mh/s... a straight up 51% attack would be easier and a guaranteed success compared the aggro of a using the KGW exploit. The exploit is most attractive for attacking networks where a 51% attack is not possible, because the KGW exploit only needs about 10% of the network hash-rate to be effective, so it makes the big networks vulnerable.

In the case of KDC, a 51% attack is instant and effective... and not much hash-rate would be needed... in fact... I could launch a 51% by myself at the moment with ease.

So more important to take the time to ensure the fix is implemented properly, add a few checkpoints, and make sure the hard fork is deployed after a considerable publicity and notice to all exchanges, merchants, users, and miners than rushing it because of the fear of being exploited.

If there is going to be another hard fork perhaps we should rethink the block payout...  Hash is king and you have to pay for it.

I would suggest a fixed reward for all future blocks (no halving).  Remember the more blocks hashed the less dilutive a payout is.

why not 88? 
http://en.wikipedia.org/wiki/88_(number)

reward is 8 and price is around 1500-1800 ....

so u want make it 88 .... where is your brains ?

My brain is on the meager 60Mh/s and the security of the coin.  Where else should your brain be?  88 coins a minute buys you a few hundred Mh/s even at lower prices.

It's not like 88 payout tanks the coin 80%.  The more blocks that are produced the less inflation a new block creates. 



Unless of course you want a coin with 20Mh/s NET HASH and anyone with time to kill can 51% attack your coin... 

Don't focus on the price, worry about the underpinnings.
 

Lol you are the one who are most focused on the price, you turned off your rigs because you hadn't enough profit.

And my potential hash is not applied to any coin. 

Who wins? no one.

I would mine a coin valued at 1 satoshi if it was worth the effort.  I don't give two shits about the actual price, I just care about the exchange of my hash for equitable value.

Call me the evil scum of the earth for being a profit miner until your blue in the face and your coin withers to an unsecure hash rate, I could care less.

This is just a side hobby / educational experience for me, I made a suggestion on block payout to improve the net hash. 

What ideas do you have besides bad mouthing someone who just wants to be paid for their work?

 

[heartthew]

There is no need to rush this hard-fork... Fuse will need a day or two to double check the code.

At this point, no one is going to use this exploit against KDC... at a network hash-rate of less than 100Mh/s... a straight up 51% attack would be easier and a guaranteed success compared the aggro of a using the KGW exploit. The exploit is most attractive for attacking networks where a 51% attack is not possible, because the KGW exploit only needs about 10% of the network hash-rate to be effective, so it makes the big networks vulnerable.

In the case of KDC, a 51% attack is instant and effective... and not much hash-rate would be needed... in fact... I could launch a 51% by myself at the moment with ease.

So more important to take the time to ensure the fix is implemented properly, add a few checkpoints, and make sure the hard fork is deployed after a considerable publicity and notice to all exchanges, merchants, users, and miners than rushing it because of the fear of being exploited.

If there is going to be another hard fork perhaps we should rethink the block payout...  Hash is king and you have to pay for it.

I would suggest a fixed reward for all future blocks (no halving).  Remember the more blocks hashed the less dilutive a payout is.

why not 88? 
http://en.wikipedia.org/wiki/88_(number)

reward is 8 and price is around 1500-1800 ....

so u want make it 88 .... where is your brains ?

My brain is on the meager 60Mh/s and the security of the coin.  Where else should your brain be?  88 coins a minute buys you a few hundred Mh/s even at lower prices.

It's not like 88 payout tanks the coin 80%.  The more blocks that are produced the less inflation a new block creates. 



Unless of course you want a coin with 20Mh/s NET HASH and anyone with time to kill can 51% attack your coin... 

Don't focus on the price, worry about the underpinnings.
 

Lol you are the one who are most focused on the price, you turned off your rigs because you hadn't enough profit.

And my potential hash is not applied to any coin. 

Who wins? no one.

I would mine a coin valued at 1 satoshi if it was worth the effort.  I don't give two shits about the actual price, I just care about the exchange of my hash for equitable value.

Call me the evil scum of the earth for being a profit miner until your blue in the face and your coin withers to an unsecure hash rate, I could care less.

This is just a side hobby / educational experience for me, I made a suggestion on block payout to improve the net hash. 

What ideas do you have besides bad mouthing someone who just wants to be paid for their work?

A lot of stupid, shortsighted ideas havecome up - and been implemented - on this thread, more than most other coins.

The block reward should NEVER have been dropped from 77 to 16.

That showed such brutal disregard for every miner that might join KDC from that point on, and has nearly killed the coin.

Why not 44 or 33, why the hell 16?

Why didn't ANYONE stop such a foolhardy change?

Greed, that's why.

This guy is right, the reward is not much of a reward, and the suffering hashrate proves it...

[jackdminer]

There is no need to rush this hard-fork... Fuse will need a day or two to double check the code.

At this point, no one is going to use this exploit against KDC... at a network hash-rate of less than 100Mh/s... a straight up 51% attack would be easier and a guaranteed success compared the aggro of a using the KGW exploit. The exploit is most attractive for attacking networks where a 51% attack is not possible, because the KGW exploit only needs about 10% of the network hash-rate to be effective, so it makes the big networks vulnerable.

In the case of KDC, a 51% attack is instant and effective... and not much hash-rate would be needed... in fact... I could launch a 51% by myself at the moment with ease.

So more important to take the time to ensure the fix is implemented properly, add a few checkpoints, and make sure the hard fork is deployed after a considerable publicity and notice to all exchanges, merchants, users, and miners than rushing it because of the fear of being exploited.

If there is going to be another hard fork perhaps we should rethink the block payout...  Hash is king and you have to pay for it.

I would suggest a fixed reward for all future blocks (no halving).  Remember the more blocks hashed the less dilutive a payout is.

why not 88?  
http://en.wikipedia.org/wiki/88_(number)

reward is 8 and price is around 1500-1800 ....

so u want make it 88 .... where is your brains ?

My brain is on the meager 60Mh/s and the security of the coin.  Where else should your brain be?  88 coins a minute buys you a few hundred Mh/s even at lower prices.

It's not like 88 payout tanks the coin 80%.  The more blocks that are produced the less inflation a new block creates.  



Unless of course you want a coin with 20Mh/s NET HASH and anyone with time to kill can 51% attack your coin...  

Don't focus on the price, worry about the underpinnings.
 

Lol you are the one who are most focused on the price, you turned off your rigs because you hadn't enough profit.

And my potential hash is not applied to any coin.  

Who wins? no one.

I would mine a coin valued at 1 satoshi if it was worth the effort.  I don't give two shits about the actual price, I just care about the exchange of my hash for equitable value.

Call me the evil scum of the earth for being a profit miner until your blue in the face and your coin withers to an unsecure hash rate, I could care less.

This is just a side hobby / educational experience for me, I made a suggestion on block payout to improve the net hash.  

What ideas do you have besides bad mouthing someone who just wants to be paid for their work?

A lot of stupid, shortsighted ideas havecome up - and been implemented - on this thread, more than most other coins.

The block reward should NEVER have been dropped from 77 to 16.

That showed such brutal disregard for every miner that might join KDC from that point on, and has nearly killed the coin.

Why not 44 or 33, why the hell 16?

Why didn't ANYONE stop such a foolhardy change?

Greed, that's why.

This guy is right, the reward is not much of a reward, and the suffering hashrate proves it...

This was done because of the coming ASIC's if you have no idea why we need to protect investors then you have no idea of a economic market.

All this crying are the miners that can't do ROI their hardware anymore.

The reward is good as it is now. Because at these times not the profitable coin will count, no in these times all the people that do not support this coin will go to other coins and this will be a good thing.

You are just parasites trying to get the last btc you can out of any coin and you deserve to starve.

I know that you think that securing the blockchain is a need and i agree with you but not while this coin is still growing.
In the first days you could easily do a 51% on bitcoin and it did not happen. Why ? Because it is not profitable Period!

Just throwing out ideas.  No one is crying.  People will 51% attack you because they can, just like street artist tag.  If you don't secure your coin you will loose your investment/investors whatever.  Reducing the block pay as a defense against ASICs?  Could someone explain that to me please?

The real cry babies are the bag holders who wrongly feel threatened by a block pay that supports a secure block chain.  What happened in the early days of Bitcoin is irrelevant in today's environment.

No one is going to listen to me regardless, so this experiment will play out 'your way' and we will observe the outcome in the months ahead.  My prediction is the current path will lead to the coins demise.

[kahir]

well first we need that
1- kgw error fixed .....with hardfork .. asap
2- explorer back online

[LeBarton]

go read my posts ......

yes ... i turned off my rig to mine kdc ....

i mine most profitable - dump for kdc buys ....

that would push price up ... and attract more miners to kdc ... thats called using your brain

I was talking to jackdminer, not you kahir.

In fact I'm for the coin going PoS and creating a pool that mines LTC and exchanges it to KDC. I would do the same way as you but I keep my mining rig pointed to KDC to secure the net hashrate.

[G440T]

go read my posts ......

yes ... i turned off my rig to mine kdc ....

i mine most profitable - dump for kdc buys ....

that would push price up ... and attract more miners to kdc ... thats called using your brain

I was talking to jackdminer, not you kahir.

In fact I'm for the coin going PoS and creating a pool that mines LTC and exchanges it to KDC. I would do the same way as you but I keep my mining rig pointed to KDC to secure the net hashrate.

+1 PoS and the pool sounds like a good idea, and now is the perfect time to fork.