Bitcoin Forum
November 01, 2024, 11:26:21 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 [6] 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 »
  Print  
Author Topic: [ANN] Extremecoin (EXC) - MANDATORY UPGRADE VERSION 1.5 (Kimoto Gravity Well)  (Read 97220 times)
CaptChadd (OP)
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1005


Product Marketing & Promotion / Software Developer


View Profile
August 25, 2013, 08:18:34 PM
Last edit: August 25, 2013, 08:35:06 PM by CaptChadd
 #101

Version 1.1 of Extremecoin released, urgent update.

Link : https://www.dropbox.com/s/bjym7nxc62pbxzn/Extremecoin%20V1.1.zip

Thanks
Hazard
Legendary
*
Offline Offline

Activity: 980
Merit: 1000



View Profile WWW
August 25, 2013, 08:35:12 PM
 #102

I am not worried about people stopping mining this coin after the reward is gone, as I have got myself another rig that will be dedicated to just mining this coin and keep it going.
That's real great. You think your little mining rig will keep the network alive? Do you think hashrate is irrelevant? It's what protects your coin against attacks. If it's just your shitty little 2MHash rig keeping the network alive, it would be trivial to 51% attack.

Anyone pointing hashes at this garbage is wasting their time, and money.

CaptChadd (OP)
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1005


Product Marketing & Promotion / Software Developer


View Profile
August 25, 2013, 08:38:04 PM
 #103

I am not worried about people stopping mining this coin after the reward is gone, as I have got myself another rig that will be dedicated to just mining this coin and keep it going.
That's real great. You think your little mining rig will keep the network alive? Do you think hashrate is irrelevant? It's what protects your coin against attacks. If it's just your shitty little 2MHash rig keeping the network alive, it would be trivial to 51% attack.

Anyone pointing hashes at this garbage is wasting their time, and money.

Might need to read the post above, as I have updated the client, as I know transaction fee's will not be enough alone.
aTriz
Hero Member
*****
Offline Offline

Activity: 1232
Merit: 683


Tontogether | Save Smart & Win Big


View Profile
August 25, 2013, 08:41:59 PM
 #104

Updated client, redownloading block chain.. will see how it works out

SALHERO
Member
**
Offline Offline

Activity: 112
Merit: 10



View Profile
August 25, 2013, 08:42:55 PM
 #105

I am not worried about people stopping mining this coin after the reward is gone, as I have got myself another rig that will be dedicated to just mining this coin and keep it going.
That's real great. You think your little mining rig will keep the network alive? Do you think hashrate is irrelevant? It's what protects your coin against attacks. If it's just your shitty little 2MHash rig keeping the network alive, it would be trivial to 51% attack.

Anyone pointing hashes at this garbage is wasting their time, and money.

i remember you makes more garbage a months ago, flashcoin and a lot of garbage (and apparently you want make this again)!!! pfff ... the donkey speaks about big ears.
CaptChadd (OP)
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1005


Product Marketing & Promotion / Software Developer


View Profile
August 25, 2013, 08:44:44 PM
 #106

Updated client, redownloading block chain.. will see how it works out


Might have to wait for the pool to update aswell. The seed node is upto date. Just the pool to update the client now and things will get back to normal with the block reward drop in place.
Hazard
Legendary
*
Offline Offline

Activity: 980
Merit: 1000



View Profile WWW
August 25, 2013, 08:44:52 PM
 #107

I am not worried about people stopping mining this coin after the reward is gone, as I have got myself another rig that will be dedicated to just mining this coin and keep it going.
That's real great. You think your little mining rig will keep the network alive? Do you think hashrate is irrelevant? It's what protects your coin against attacks. If it's just your shitty little 2MHash rig keeping the network alive, it would be trivial to 51% attack.

Anyone pointing hashes at this garbage is wasting their time, and money.

i remember you makes more garbage a months ago, flashcoin and a lot of garbage (and apparently you want make this again)!!! pfff ... the donkey speaks about big ears.
Takes a true moron to take joke releases as something serious Cheesy

I am behind many coins, probably at least one or two of which you support... And you don't even know it.

djchoppa
Member
**
Offline Offline

Activity: 83
Merit: 10


View Profile
August 25, 2013, 08:45:14 PM
 #108

Updated.  I can see it on my taskbar now.  Thanks captchadd, you've obviously been working hard and I think it's paid off.  Look at all the miners digging away with their ickle cpus.  I think your gonna answer the question on everybodies mind....... WHAT HAPPENS WHEN THE COINS RUN OUT.  Smiley

████→→       ● DeepOnion                                                                       ✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯ 
████→→       ● Tor integrated, 100% anonymous!                                ✯       Get Your FREE Coins NOW!      ✯
████→→       ● Free Airdrop! (No ICO, No Crowdfund)                       ✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯
aTriz
Hero Member
*****
Offline Offline

Activity: 1232
Merit: 683


Tontogether | Save Smart & Win Big


View Profile
August 25, 2013, 08:46:54 PM
 #109

Updated client, redownloading block chain.. will see how it works out


Might have to wait for the pool to update aswell. The seed node is upto date. Just the pool to update the client now and things will get back to normal with the block reward drop in place.

stuck updating at 2164 ~

should I just keep farming at the pool?

CaptChadd (OP)
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1005


Product Marketing & Promotion / Software Developer


View Profile
August 25, 2013, 08:54:38 PM
 #110

Updated client, redownloading block chain.. will see how it works out


Might have to wait for the pool to update aswell. The seed node is upto date. Just the pool to update the client now and things will get back to normal with the block reward drop in place.

stuck updating at 2164 ~

should I just keep farming at the pool?

Once the pool has updated their client and so have most of the other users to the new version, then everything will start syncing up.
YukonCoinelius
Member
**
Offline Offline

Activity: 67
Merit: 10


View Profile
August 25, 2013, 08:59:46 PM
 #111

ALERT -  UPGRADE 1.1 BROKEN  -  do not upgrade


Upgrade 1.1 is broken in the block value computation - it's not sensible and also appears to be incompatible with the existing blockchain - the existing blockchain cannot sync to this upgrade.

I will post more details in another message or edit here shortly.
djchoppa
Member
**
Offline Offline

Activity: 83
Merit: 10


View Profile
August 25, 2013, 09:11:23 PM
 #112

Well I haven't had any problems.  What seems to be the issue?

████→→       ● DeepOnion                                                                       ✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯ 
████→→       ● Tor integrated, 100% anonymous!                                ✯       Get Your FREE Coins NOW!      ✯
████→→       ● Free Airdrop! (No ICO, No Crowdfund)                       ✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯✯
YukonCoinelius
Member
**
Offline Offline

Activity: 67
Merit: 10


View Profile
August 25, 2013, 10:11:45 PM
Last edit: September 02, 2013, 01:36:19 PM by YukonCoinelius
 #113

Here is the new block value code in update 1.1:
It's broken.  


Code:
int64 static GetBlockValue(int nHeight, int64 nFees)
{
if(nHeight<4320) return 200*COIN; //720000 coins in two weeks
else if(nHeight<8640) return 100*COIN; //144000 coins in four weeks
else if(nHeight<12960) return 50*COIN; //72000 coins in 6 weeks
else if(nHeight>17280) return 1*COIN;
    int64 nSubsidy = 1 * COIN; // 1 Coin until 5 million limit reached

if(nHeight>5000000) nSubsidy=0;

    return nSubsidy + nFees;

}


First of all, the immediate problem is, it won't sync the existing blockchain, because
the return value is not adding the nFees now.  (the bottom line is never reached
except when nHeight is between 12960 and 17280).  The effect is probably that
anybody starting a fresh blockchain download with the new code will probably hang up
at the first block that has significant fees.

Second, what this code is actually doing is issuing 200 coins/block for 15 days (4320 blocks),
then 100/block for 15 days, then 50/block for 15 days, then 1/block for the rest.
That's (200 * 4320) + (100 * 4320) + (50 * 4320) + 1 + 1 ... = 1512000 + 1 + 1 ... total coins.

So it will issue 1512000 coins in 45 days and then drop to 1/block.  
That's still not what you've described as the intended design.

Also the comments make no sense.  I thought your intent is to issue 4M coins in 8 weeks?
720000 + 144000 + 720000  does not equal 4M either.
    
Also, the (nHeight>5000000) test is not the right way to reduce subsidy to 0 after 5M coins.

Also, if you change the protocol in future, it needs to be switch-controlled at a particular block height.
(you can get away with no switch this time, because the chain is still under block 4320).

Finally, it needs to be structured so the nFees are always added.



Chad, I have very limited time to check/fix this coin.

If you PM me in words what exactly you want as a minting protocol, I will see about fixing it up for you this time.  (though I can't guarantee that's the only problem - I haven't checked all the rest of the code/changes).


CaptChadd (OP)
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1005


Product Marketing & Promotion / Software Developer


View Profile
August 25, 2013, 10:55:33 PM
 #114

Here is the new block value code in update 1.1:
It's broken.  


Code:
int64 static GetBlockValue(int nHeight, int64 nFees)
{
if(nHeight<4320) return 200*COIN; //720000 coins in two weeks
else if(nHeight<8640) return 100*COIN; //144000 coins in four weeks
else if(nHeight<12960) return 50*COIN; //72000 coins in 6 weeks
else if(nHeight>17280) return 1*COIN;
    int64 nSubsidy = 1 * COIN; // 1 Coin until 5 million limit reached

if(nHeight>5000000) nSubsidy=0;

    return nSubsidy + nFees;

}


First of all, the immediate problem is, it won't sync the existing blockchain, because
the return value is not adding the nFees now.  (the bottom line is never reached
except when nHeight is between 12960 and 17280).  The effect is probably that
anybody starting a fresh blockchain download with the new code will probably hang up
at the first block that has significant fees.

Second, what this code is actually doing is issuing 200 coins/block for 15 days (4320 blocks),
then 100/block for 15 days, then 50/block for 15 days, then 1/block for the rest.
That's (200 * 4320) + (100 * 4320) + (50 * 4320) + 1 + 1 ... = 1512000 + 1 + 1 ... total coins.

So it will issue 1512000 coins in 45 days and then drop to 1/block.  
That's still not what you've described as the intended design.

Also the comments make no sense.  I thought your intent is to issue 4M coins in 8 weeks?
720000 + 144000 + 720000  does not equal 4M either.
    
Also, the (nHeight>5000000) test is not the right way to reduce subsidy to 0 after 5M coins.

Also, if you change the protocol in future, it needs to be switch-controlled at a particular block height.
(you can get away with no switch this time, because the chain is still under block 4320).

Finally, it needs to be structured so the nFees are always added.



Chad, I have very limited time to check/fix this coin.

If you PM me in words what exactly you want as a minting protocol, I will see about fixing it up for you this time.  (though I can't guarantee that's the only problem - I haven't checked all the rest of the code/changes).


Going forward, it seems you might be in over your head a bit, and should seek additional developer support for any future work.



You are right with the total coins. I did not take that into account. As for the code. Compare it to Mincoins source code. Mincoins works just fine and mine is pretty much the same.
CaptChadd (OP)
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1005


Product Marketing & Promotion / Software Developer


View Profile
August 25, 2013, 11:38:15 PM
 #115

Updated main.cpp in client. Update is in the OP client link.

int64 static GetBlockValue(int nHeight, int64 nFees)
{
if(nHeight<4320) return 200*COIN;   //864000 coins in two weeks
else if(nHeight<8640) return 100*COIN;   //432000 coins in four weeks
else if(nHeight<12960) return 50*COIN;   //216000 coins
else if(nHeight<17280) return 25*COIN;  //108000 Coins - At this point 1,620,000 coins will be mined
    int64 nSubsidy = 1 * COIN;         // 1 Coin until 5 million limit reached

    return nSubsidy + nFees;

}

This going to work now?

I really need to keep things simple.

milly6
Legendary
*
Offline Offline

Activity: 1632
Merit: 1010



View Profile WWW
August 25, 2013, 11:41:23 PM
 #116

Why reduce block rewards, CaptChadd? I personally don't like that idea and I have to admit, it gives people the jump on the pump and dump, then most will drop the coin when it gets down in block size.

Eyes open, No Fear. Be Safe! Trinity: Currency Without Bias
mill0601
Legendary
*
Offline Offline

Activity: 1162
Merit: 1000


View Profile
August 25, 2013, 11:43:14 PM
 #117

Why reduce block rewards, CaptChadd? I personally don't like that idea and I have to admit, it gives people the jump on the pump and dump, then most will drop the coin when it gets down in block size.


Yeah i could not agree more. I am also not a fan.

❘|❘ ICONOMI Fund Management Platform
LINK TO ICO | LINK TO DISCUSSION
CaptChadd (OP)
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1005


Product Marketing & Promotion / Software Developer


View Profile
August 25, 2013, 11:43:50 PM
 #118

Why reduce block rewards, CaptChadd? I personally don't like that idea and I have to admit, it gives people the jump on the pump and dump, then most will drop the coin when it gets down in block size.

Would you prefer it to just get to the end and have just the fee's after 2 months or 1 coin per block?
aTriz
Hero Member
*****
Offline Offline

Activity: 1232
Merit: 683


Tontogether | Save Smart & Win Big


View Profile
August 25, 2013, 11:48:07 PM
 #119

I'm not sure what would be better, if we have a end and just have 1 coin per block, we risk the chance of not having enough hash power and then will have to deal with 51% attacks. But at the same time I agree with the other people about halving and then having to deal with pump and dumps, guess we just gotta go with one Smiley

My vote its "extremecoin" lets do 2 months of rewards and then reduce it to 1 coin per block.

CaptChadd (OP)
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1005


Product Marketing & Promotion / Software Developer


View Profile
August 25, 2013, 11:59:12 PM
 #120

I'm not sure what would be better, if we have a end and just have 1 coin per block, we risk the chance of not having enough hash power and then will have to deal with 51% attacks. But at the same time I agree with the other people about halving and then having to deal with pump and dumps, guess we just gotta go with one Smiley

My vote its "extremecoin" lets do 2 months of rewards and then reduce it to 1 coin per block.

Done and I have tested it on my main rig again and it has synced.

New Fix Windows QT client : https://www.dropbox.com/s/bjym7nxc62pbxzn/Extremecoin%20V1.1.zip

Now it is a lot more simple.

int64 static GetBlockValue(int nHeight, int64 nFees)
{
int64 nSubsidy = 200 * COIN;

if(nHeight>17280) nSubsidy = 1 * COIN;
   
return nSubsidy + nFees;

200 coins until block 17280 and then reduces to 1 per block.

Pages: « 1 2 3 4 5 [6] 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!