Topic: [ANN] [BUK] CryptoBuck Official Notes BUK2.1.1 -->New ChainStart 2017-02-01 - page 15. (Read 89227 times)

The client is just warning you that the most recent hardcoded checkpoint is more than 100 days old. It doesn't mean it has detected a specific issue with the blockchain.

Type this in the debug console to verify we're on the same chain:

> getblockhash 32907
20bf6f7c597f9c981d472db5966acfe436a14d725d14131afc345aea6290cfd2

im on "version" : "v1.3.0.0",
and when synced it says
"errors" : "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers."
is this ok ?or  all coins sent to my wallet will be  invalid
many thanks

Any updates re Cryptsy? Wallet is still disabled.

Just a warning that any transactions sent on the old chain (including a deposit/withdraw from cryptsy or bter) will be invalidated once the sender and/or receiver update to the new client.

So, for example, if you've deposited to Cryptsy within the past few days, you may end up with a negative BUK balance there.

Thanks for letting us know - much appreciated 

Both Exchanges have been notified Prior to POW Block Generation.  Cryptsy has made comments on 25 Wallet fixes being implemented this upcoming weekend, BUK being one of them.  BTER has not responded with a set completion time on Upgrade.

We are working to get the Checkpoint Server up and running with Checkpoints after this newest POW re-implementation.  More to follow as this develops.

I've done this, and synced ok, but yes, new checkpoints are needed, and the exchanges need to know whats going on.  I have notified Cryptsy, but as ever it's hard to get any information from them.

I've just realised that block 28000 was minted about 6 hours after your post. This is far too little time to allow people to upgrade. Since this block is now well past you're going to run into a serious problem: if anyone lets the previous client run past block 28000 - as they would have if they had not seen the announcement in time - they will create their own private fork once they upgrade. Their copy of the chain won't roll back to 28000 and resync to the new one, it will just continue (as a private fork) from whichever block they upgraded at. If they upgrade at, say, block 29701, they will start minting PoS blocks at 29702 on a private fork. If their client is ineligble to mint PoS, no blocks will be accepted from peers and the client will soon complain it is out of sync.

To get onto the "new" chain will most likely require deleting the blockchain db and syncing from scratch.

in addition,i barely find any advanced tech or specific useful skills.

I've done some test deposits and transfers, this seems to be the current situation:

1. Freshly installed & synced wallet ties properly to block explorer.
2. Both Cryptsy and bter are on the same chain (bter->cryptsy works, very slowly), but neither the block explorer or my wallet can see the transaction.
3. Withdraw from Cryptsy and bter to my wallet never arrive.

A reasonable conclusion is that bter and cryptsy have not yet updated the daemons, so they're still on the "PoS only" chain. Have they been notified?

edit: there needs to be new checkpoints added to stop the warning. The last checkpoint is nearly 10 months old.

Happy 1st Birthday CryptoBuck.
Enjoy your Proof Of Work Upgrade!

Explorer Showing current POW and POS Hashing Together - http://buk.cryptocoinexplorer.com

The explorer at buk.cryptocoinexplorer.com has been updated to the latest build.

Features Added:

Market information is now on the home page where the ticker used to be.

Address ownership claim system is now in place. Access with the "Address Claim" button. Address ownership information is available on the top 1000 balances only.


Next build plans:

Charting page (tx, difficulty,blocks - 24 hrs,Week, Month)

Country ID and flag for the IP addresses on the peers page.

Address ownership information available as a tool-tip anywhere on site.


Your suggestions for features or statistics you would like to see are welcome!!!!

nope - still appears to not be working - never syncs....and I can't mine

I'm still getting 'Checkpoint too old.....'  

It just never syncs

Edit: attempting to re-download blockchain see if that fixes it.

The CryptoBuck Team is proud to announce the upcoming 1 Year Anniversary.  The Public Launch - Born On Date - SEPTEMBER 2nd 2013 is approaching Fast.  What a year this has been.....  

CryptoBuck has been hashing away as a 100% Proof Of Stake Only Chain since Block 15637 - GMT: Sun, 13 Oct 2013 01:22:02 UTC (1381627322)

      In October 2013, Looong before Scrypt Asic we were hitting 100-150Mh speeds on the network which was phenomenal GPU/CPU Speeds for a Startup.  POS/POW Hybrid Algorithm was in full effect. 33BUK's 33BUK's 33BUK's 33BUK's The Blockchain was ticking away-  We had a very large following in China at the time, and had a positive outlook for upward potential.  While in our Highs, Block 15637 came along and unintentionally put the POW Generation in a loop, leaving CryptoBuck to a P.O.S. only Asset.  This was the beginning of all BUK Generation being seized up in this Stalled POW chain. The Total MINT at this point was around 500,000 BUK's. - 9 Months later we have a Total Mint of 511,510. - Proof Of Stake has been the Bloodline of CryptoBuck.  
      Now as we approach the 1 Year Mile-Stone we have tallied up the opinions of the community and have decided to bring back the Proof Of Work Chain and let the BUK Production continue as it was intended.    ~10 Million BUK's mining schedule.  The production schedule will go unchanged with current rates at 33 BUK's @ 3Minutes.  


The FIX - Coded in version 1.3.0 will start the POW chain back up at Block 28000.  The Fault that caused all the problems on block 15637 is a "Negative N Factor" issue, which puts POW in a loop when negative value is reached. See Code Below. In the File Main.cpp -
Line 1013 - REMOVED - static const int64 nTargetTimespan = 15 * 60;  // 15 mins
Line 1083-1103 Below
 int64 nTargetTimespan;

    if (pindexLast->nHeight >= 28000)
    {
        // fixed nTargetTimespan value: 30 blocks interval
        nTargetTimespan =  nStakeTargetSpacing * 30;

        // Time bomb prvention
        if(nActualSpacing < 0)
        {
            nActualSpacing = 2;
        }
        else if(nActualSpacing > nTargetTimespan)
        {
            nActualSpacing = nTargetTimespan;
        }
    }
    else
    {
        // original nTargetTimespan value
        nTargetTimespan = 15 * 60;

Version 1.3.0 also addresses connectivity issues, and patches Heart-bleed OpenSSL concerns.  Please update Clients, as 1.3.0 is now available for download prior to block 28000.

BUK 1.3.0 DOWNLOAD (Static Built/No DLL's Needed) = https://github.com/CryptoBuck/CryptoBuck/releases/tag/1.3.0.0

POS + POW - but change to something more asic resistant as well. 

POS 100% market is filling up.  Too many released to quickly and even a few good ones will die.

POS/POW is highly under rated. 

I don't trust +$500 on pure stakes networks, not until something better is invented.

+POW fixes that problem.

What to do?

pump up the POS for 90 days, then run it down quick.  (super stake blitz will get attention)

do the math on what that leaves for POW for 25 years. 

also if you can switch to SHA ... big and stronger HASH power.

There are other gimicks like POS velocity.  p o t

And I wonder if it is possible for POS'rs to get a share of the mining fee?

Or blockchain storage rewards so people stake more?


or just merge with litecoin

CryptoBuck  has established partnership with Bitscoinshop (http://www.bitscoinshop.com.br/en/) where you can buy items by using CryptoBuck, and enjoy 10% discount. As CryptoBuck is not yet integrated with the payment platform, you will need to use the following procedure during checkout:
 
1. Customers wishing to purchase using CryptoBuck should choose the product, along with signing up with the details and place of delivery;
 
2. Choose the bank transfer as the payment method, meanwhile leave a message to indicate that you want to pay with CryptoBuck;
 
3. In the message, specify the dollar amount of your purchase (with 10% discount) and the quote of the current exchanging rate (Bittrex Exchange). Bitscoinshop will convert the amount of your purchase into CryptoBuck, and send wallet address for payment.
 
4. Once confirmed the payment, items will be delivered.
 
We have many items for mining as gridseed, Asics, shoes and articles of clothing.

To The CryptoBuck Community,

      It has been some time since we have posted official news, updates, snippets, and CryptoBuck related posts.  About a month ago we have finalized the coding that will "Fix" the "Pow" side of the chain.  We have it in our back pocket wondering what the best approach is for BUK.  For starters,  the P.O.S. only chain has been running and processing traders coins, and awarding the stake value for the proof of stake due.  Smooth.  At this point being P.O.S only we have been zero threat to the downturn in value on the altcoin market.  Simply retaining our Value instead of getting dumped on, like all others.   Leaves us Curious as to what any of the other BUK Holders would say.  Question1 -  Keep riding it out for a few more weeks to see if an uptrend will ever begin?  Question2 - Should we release our Fix bringing back POW and POS at the same TIME?  -  This will generate 33 BUK's every 3-10minutes on average.  This could turn into a very high profile, Valuable opportunity for many Asic Miners that PLUG IN.  In Turn, the Mining Profitability will be great for the first comers with Plugged in Asic equipment, but it will then be low balled down in value just like the entire Cryptsy Market is going though right now.



BUK is High End,  only ~10M  total ever.   More to follow in weeks out.  Just wanted to get an opinion on the CryptoBuck Fix that sits here idle.  Run it now?  Run it later?   Just seeing how anyone feels in regards to this.

CryptoBuck - 2014

BUK Blockchain is Still Hashing Away POS Only.  Help Us Decide what to do with the releasing the POW Fix, and the consequences. if we do release.  

Thanks for the feedback!!

CryptoBuck

Thank You to all the CryptoBuck Miners. and loyalists.  Still holding this statement below as high as possible to help some remember that BUK is Pure.  No Pre-mine. No InstaMine. Generates a Safe P.O.S. = to 3% at 30 Days Held
We are Trusted, We are Honest, and We are Valued...