[ANN] [BUK] CryptoBuck Official Notes BUK2.1.1 -->New ChainStart 2017-02-01

[digit]

I fix check reward in test version and resynch. All block good until 169778.
Just add some code in function "bool CBlock::ConnectBlock"

Code:

...
    // Check coinbase reward 
    if (vtx[0].GetValueOut() > (IsProofOfWork()? (GetProofOfWorkReward(pindex->nHeight) + nFees) : 0)) 
        return DoS(50, error("CheckBlock() : coinbase reward exceeded %s > %s",  
           FormatMoney(vtx[0].GetValueOut()).c_str(), 
           FormatMoney(IsProofOfWork()? GetProofOfWorkReward(pindex->nHeight) : 0).c_str()));
    // ppcoin: track money supply and mint amount info
...

What about change PoS rate to 12, 50, 100, or 200%?

unless those rogue PoW blocks can be removed, i dont see how this coin could be saved.

If intention is to go PoS only then the most needed change PoS would be to reduce the eligibility for stake from 30 days to maybe 1 day, as it will take a lot of time to get the network going again should that address that been staking nonstop for years come to a halt. 
Interest does not need to be increased unless you only want a coin with short term life, no one wants to buy a coin that explodes to billions supply be worthless in 6 months like some "superturbohyperstakingmegasproutscoin2"  , only good for scam exchanges that end up owning most of the coins and then use the stake for regular income off their users. (why do so many of these ridiculous interest coins originate with cryptsy or their associated?)

I dont have much hope for coin after all the stalling tactics from cryptsy on shifting it out maintenance, but it would be interesting to see someone could come up with a clean solution that removes the rogue generated coins in the blockchain without breaking it.

This exploit you have found reminds me of those other cryptsy coins like CENT pennies and LGD legendarycoin that were contain glitches that were secretly exploited then dumped, which was likely by members of the cryptsy team themselves, given what has been revealed so far about those crooks.  Perhaps the same idea planned for BUK but the wallet guy had already run off before they could get the wallet working to profit from it?  There was a very unusual promotion of it for a short period where i'm guessing cryptsy had "sponsored" the coin with 1 BTC to pump the price but the wallet was not working so they could deposit any new coins into the system.

[1714837775]

1714837775

[1714837775]

1714837775

[vampirus]

I think developer can not use mining fee with checkblok, in some other coins, fee not give to miner, just destroyed. In BUK, developer remove check block reward.
I modify original check function to work with fee.

[vampirus]

If set PoS rate to 200% and set max PoS reward to 11 coin - it is same inflation as in original specification.

[vampirus]

Looks like soon we will see fixed 1.3.1 version, hardfork after 205000 block.

[CryptoBuck]

Version 1.3.1 Now Available


HardFork coming - Please update your client to version 1.3.1
Official Compiled Versions for both English and Chinese:
http://cryptobuck.com/clientrepository/CryptoBuckV1.3.1-WindowsQT.exe
http://cryptobuck.com/clientrepository/CryptoBuckV1.3.1.chinese-WindowsQT.exe
Official Source:
https://github.com/CryptoBuck/CryptoBuck

Current Height:http://buk.cryptocoinexplorer.com/


Remaining Peers Needing Update:


We are continuing to code version 2.0 which will include many enhancements and code base updates. This version is to address and
include "CoinBase Reward Exploit" as mentioned in prior posts. Mining Fee with Checkblock has tested as working and has been coded
back into source with upcoming block 205000.
  // Check coinbase reward
    if (vtx[0].GetValueOut() > (IsProofOfWork()? (GetProofOfWorkReward(pindex->nHeight) + nFees) : 0))
        return DoS(50, error("CheckBlock() : coinbase reward exceeded %s > %s", 
           FormatMoney(vtx[0].GetValueOut()).c_str(),
           FormatMoney(IsProofOfWork()? GetProofOfWorkReward(pindex->nHeight) : 0).c_str()));
    // ppcoin: track money supply and mint amount info

As originally launched,
the Chinese Compiles will be included with all updates now and in the future.  Once this current version 1.3.1 is running successfully
on the POW/POS chain, we will reach out to the exchanges looking for a Cryptsy Replacement.  If any Markets Chinese or American
would like to contact us, please email CryptoBuck@gmail.com

Looking Forward to continued success,
CryptoBuck Team

[almightyruler]

Quick suggestion - please exclude cryptobuckd from being uploaded to git. The majority of the 18MB source archive is this executable...

[digit]

so what happens with the coins that have glitched?  whoever did that does not deserve to profit from it, will they be removed or blacklisted?

[CryptoBuck]

so what happens with the coins that have glitched?  whoever did that does not deserve to profit from it, will they be removed or blacklisted?

We agree with you 100%.  This update was released to "Stop The Exploit" - We are exploring different options with the 2.0 update
to address this concern.  The Blocks mentioned prior that have the exploit, have moved the funds from the generation block:
Blocks:
169778
169779
169784
169787
169789
169798
169801
169801
169804
169805
169820

This is creating a situation where, there would be a cascade effect across the block chain if we simply patched the issue and have the new client/daemon reorganize the chain. I do not like this solution as it can cause issues and chain reorganizations can be messy and cause forks.  "Another option is to Specifically address those transactions in the code correcting them to the proper amount. This makes the problem transparent as anybody who reads the code will see those blocks had issues and were corrected. I see that as a good thing, some may see that as a negative."  Blacklisting the cascading effect is something that will have to be looked into.  I do assure you that we are weighing the options in the upcoming update, taking all consequences into consideration.

Thanks again for updating.  We are still seeing 2 clients on version 1.3.0.  Please update to 1.3.1 compiles @ CryptoBuck.com


Thank You for your continued support. 
CryptoBuck

[Hobbyist]

Updating the Pool ... Standby ...

Coind updated,  still indicates checkpoint is old ...

Code:

cryptobuckd getinfo
{
    "version" : "v1.3.1.0",
    "protocolversion" : 60131,
    "walletversion" : 60000,
    "balance" : ,
    "newmint" : 0.00000000,
    "stake" : ,
    "blocks" : 205820,
    "moneysupply" : 2681412.19329000,
    "connections" : 4,
    "proxy" : "",
    "ip" : "",
    "difficulty" : 0.02362246,
    "testnet" : false,
    "keypoololdest" : 1446856752,
    "keypoolsize" : 101,
    "paytxfee" : 0.01000000,
    "errors" : "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers."

[vampirus]

http://cryptobuck.com never worked for me, and I still can't get new wallet. My location - USA.

[Hobbyist]

http://cryptobuck.com never worked for me, and I still can't get new wallet. My location - USA.

Same here...  Site Suspended, This site has stepped out for a bit.

[CryptoBuck]

http://www.cryptobuck.com/   is back online. - It went down while making a Hosting Change. Migration now complete.



Add these Current Peers to your config file
203.20.114.252
76.95.178.229
5.20.100.185
162.216.46.125

[CryptoBuck]

Updating the Pool ... Standby ...

Coind updated,  still indicates checkpoint is old ...

Code:

cryptobuckd getinfo
{
    "version" : "v1.3.1.0",
    "protocolversion" : 60131,
    "walletversion" : 60000,
    "balance" : ,
    "newmint" : 0.00000000,
    "stake" : ,
    "blocks" : 205820,
    "moneysupply" : 2681412.19329000,
    "connections" : 4,
    "proxy" : "",
    "ip" : "",
    "difficulty" : 0.02362246,
    "testnet" : false,
    "keypoololdest" : 1446856752,
    "keypoolsize" : 101,
    "paytxfee" : 0.01000000,
    "errors" : "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers."

Hobbyist,
We did not update the checkpoint server values as this will be addressed in the 2.0 release.  This warning message
can be ignored for now as it present on all QTpeers.

Please let us know when your pool is up and running and we will post a direct link on CryptoBuck.com if you are ok with that.

Thank You,
CryptoBuck

Current BlockHeight = 207016 - info @ http://buk.cryptocoinexplorer.com/

[CryptoBuck]

Hi any pool for this coin ?

bitcointalk.org member Hobbyist has mentioned that he is updating his pool.  We have offered to link any Pool Operator site on CryptoBuck.com that has the updated 1.3.1 codebase.
Once we are contacted by anyone interested, we will post the announcement here.  Thank you for the interest.
CryptoBuck

[vampirus]

http://www.cryptobuck.com still not working for me 

[CryptoBuck]

http://www.cryptobuck.com still not working for me 

Please give a bit to load.  We have ddos protection on, and also have the faucet, crawler DB's being loaded but not presented.
These will return in next release.

CryptoBuck

[ioncanon]

delisted on bter?

[CryptoBuck]

delisted on bter?

Trading continues on BTER, but they have not upgraded their wallet, and it continues to be in Maintenance Mode.
Once BUK 2.0 is released they will be able to migrate over their wallet and open market back up.
https://bter.com/trade/buk_btc


 

[digit]

delisted on bter?

Trading continues on BTER, but they have not upgraded their wallet, and it continues to be in Maintenance Mode.
Once BUK 2.0 is released they will be able to migrate over their wallet and open market back up.
https://bter.com/trade/buk_btc


 

were you able to contact them?  

BTER definitely had disabled BUK markets and on was the delisted currencies list a few days ago

[ioncanon]

lets add BUK into other exchange