Topic: [ANN] [BUK] CryptoBuck Official Notes BUK2.1.1 -->New ChainStart 2017-02-01 - page 10. (Read 89226 times)
May 05, 2016, 08:37:56 AM
Novaexchange was hacked, all BTC lost. Withdraw yours BUK, immediately.
April 22, 2016, 09:14:47 AM
Direct Link to 1.3.1 Source: (Now Released)
https://github.com/CryptoBuck/CryptoBuck
Direct Link to 1.3.1 GitHub Source: (Now Released)
https://github.com/CryptoBuck/CryptoBuck
Github links still point to the old source:
#define CLIENT_VERSION_MAJOR 0
#define CLIENT_VERSION_MINOR 7
#define CLIENT_VERSION_REVISION 2
#define CLIENT_VERSION_BUILD 0
So you have updated source files for 1.3.1.0 ?
Version 2.0 will have all source files updated. This has not been released yet as we are still working on it. Version 1.3.1 was released with updates to add back in:
// 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()));
CryptoBuck
April 21, 2016, 10:08:44 PM
Direct Link to 1.3.1 Source: (Now Released)
https://github.com/CryptoBuck/CryptoBuck
Direct Link to 1.3.1 GitHub Source: (Now Released)
https://github.com/CryptoBuck/CryptoBuck
Github links still point to the old source:
#define CLIENT_VERSION_MAJOR 0
#define CLIENT_VERSION_MINOR 7
#define CLIENT_VERSION_REVISION 2
#define CLIENT_VERSION_BUILD 0
So you have updated source files for 1.3.1.0 ?
April 16, 2016, 11:46:58 PM
are delisted on bter?
We reached out to BTER to reconsider the delisting. One thing to keep in mind is that CryptoBuck was placed
into maintenance mode with BTER for over a year now. It was during the timeframe of BTER losing their BTC
Cold wallet funds.
The CryptoBuck Team has always supported BTER and their business as they were the first Chinese exchange
to Trade BUK. Unfortunately we have not heard back from them in regards to keeping BUK on their exchange.
For now I would suggest moving your BUK's over to now LIVE NovaExchange -
https://novaexchange.com/market/BTC_BUK/ [/b]]https://novaexchange.com/market/BTC_BUK/
If we do hear back from BTER, we will respond to all with the updated news.
CryptoBuck
Height = 213956
http://buk.cryptocoinexplorer.com/
POW is hashing away - get your BUK's while Diff is low.
April 16, 2016, 10:48:46 PM
are delisted on bter?
April 16, 2016, 10:44:01 PM
Thank you to Novaexchange, on behalf of the CryptoBuck Team and the loyal members of our community.
We are looking forward to the mutual success of both Teams.
CryptoBuck
https://novaexchange.com/market/BTC_BUK/
April 16, 2016, 12:54:12 PM
BUK now on
https://novaexchange.com/market/BTC_BUK/
https://novaexchange.com/market/BTC_BUK/
March 31, 2016, 11:53:48 PM
lets add BUK into other exchange 
March 31, 2016, 08:03:50 PM
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
March 31, 2016, 07:48:59 PM
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
March 31, 2016, 05:33:28 AM
delisted on bter?
March 29, 2016, 08:30:19 PM
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
March 29, 2016, 08:22:32 PM
http://www.cryptobuck.com still not working for me 
March 29, 2016, 03:49:48 PM
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
March 29, 2016, 01:02:13 PM
Updating the Pool ... Standby ...
Coind updated, still indicates checkpoint is old ...
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."
{
"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/
March 29, 2016, 12:50:21 PM
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
Add these Current Peers to your config file
203.20.114.252
76.95.178.229
5.20.100.185
162.216.46.125
March 26, 2016, 05:28:15 PM
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.
March 26, 2016, 01:57:34 PM
http://cryptobuck.com never worked for me, and I still can't get new wallet. My location - USA.
March 26, 2016, 01:03:15 AM
Updating the Pool ... Standby ...
Coind updated, still indicates checkpoint is old ...
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."
{
"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."
March 24, 2016, 09:37:58 PM
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
Jump to: