Perfect

main.cpp: In function 'int64 GetProofOfStakeReward(int64, int)':
main.cpp:953:1: error: expected primary-expression before '<<' token
 <<<<<<< HEAD
 ^
main.cpp:953:3: error: expected primary-expression before '<<' token
 <<<<<<< HEAD
   ^
main.cpp:953:5: error: expected primary-expression before '<<' token
 <<<<<<< HEAD
     ^
main.cpp:953:7: error: expected primary-expression before '<' token
 <<<<<<< HEAD
       ^
main.cpp:953:9: error: 'HEAD' was not declared in this scope
 <<<<<<< HEAD
         ^
main.cpp:954:5: error: expected ';' before 'if'
     if (nHeight > 500000) {
     ^
main.cpp:948:8: warning: unused variable 'nVariableStakeRate' [-Wunused-variable]
  int64 nVariableStakeRate = ((nCoinAge % 500) + 1) * CENT;
        ^
main.cpp:950:11: warning: unused variable 'nMinReward' [-Wunused-variable]
     int64 nMinReward = nHeight * .0011;
           ^
main.cpp:951:11: warning: unused variable 'nMaxReward' [-Wunused-variable]
     int64 nMaxReward = nHeight * .01;
           ^
main.cpp:952:11: warning: unused variable 'nSquish' [-Wunused-variable]
     int64 nSquish = nSubsidy / 1000000;
           ^
main.cpp:4314:1: error: expected '}' at end of input
 }
 ^
main.cpp:4314:1: warning: no return statement in function returning non-void [-Wreturn-type]
main.cpp: At global scope:
main.cpp:105:13: warning: 'bool GetTransaction(const uint256&, CWalletTx&)' defined but not used [-Wunused-function]
 bool static GetTransaction(const uint256& hashTx, CWalletTx& wtx)
             ^
main.cpp:140:13: warning: 'void SetBestChain(const CBlockLocator&)' defined but not used [-Wunused-function]
 void static SetBestChain(const CBlockLocator& loc)
             ^
main.cpp:147:13: warning: 'void UpdatedTransaction(const uint256&)' defined but not used [-Wunused-function]
 void static UpdatedTransaction(const uint256& hashTx)
             ^
main.cpp:154:13: warning: 'void PrintWallets(const CBlock&)' defined but not used [-Wunused-function]
 void static PrintWallets(const CBlock& block)
             ^
main.cpp:161:13: warning: 'void Inventory(const uint256&)' defined but not used [-Wunused-function]
 void static Inventory(const uint256& hash)
             ^
main.cpp:168:13: warning: 'void ResendWalletTransactions()' defined but not used [-Wunused-function]
 void static ResendWalletTransactions()
             ^
main.cpp:918:16: warning: 'uint256 GetOrphanRoot(const CBlock*)' defined but not used [-Wunused-function]
 uint256 static GetOrphanRoot(const CBlock* pblock)
                ^
make: *** [obj/main.o] Error 1

-------------------------------------------------------------------------

got the same error compiling both locallly on ubuntu 16.04 and on the vps ubuntu 14

it's like all the ppl on the thread that ask questions like what's happening with bleutrade, what's goin on cube pos, they want other's do the work for them so they can just sit back and try to ride to riches. but it doesn't work like that! money doesn't grow on trees, even with crypto!

too many ppl just looking for easy money and lazy fucks don't wanna work for it

I don't understand why POS doesn't dominate the markets better than coins still being mined with very low returns/mining costs compared to minimal hardware/staking

hmm, well i came into CUBE around 420 sats. and i still made back my initial investment even with the drop in price + stakes

Email them to find out

I've already been doing most of the pushing for them to get it on the exchange, last they wrote back to me they were syncing the wallet. I emailed them again this morning, waiting for a reply.

i have 34 'active' connections on my vps node

or you write a whitepaper that explains in detail how your coin works, and all is well , instead of calling ppl every profanity you can imagine cause you don't know how to be zen and teach instead of insult.

Bleutrade Team (Bleutrade) <support@bleutrade.zendesk.com>
10:18 AM (5 hours ago)

to me
##- Please type your reply above this line -##
Your request (#3362) has been updated. Reply to this email or click the link below:
https://bleutrade.zendesk.com/hc/requests/3362

Bleutrade    
Bleutrade Team (Bleutrade)
Jun 15, 11:18 BRT

ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 9f575b484c03d915fe914b64177841b1f25a9477e65a86932fa14f98ce6f47e9
received block 9f575b484c03d915fe91
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 9f575b484c03d915fe914b64177841b1f25a9477e65a86932fa14f98ce6f47e9
sending getdata: block 2a264721177617c368d3
received block 2a264721177617c368d3
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 2a264721177617c368d35e5fa958c2c4665e0cf3faccef03a302190ba7af857e
sending getdata: block fd6033493cf1dc3d2d43
received block fd6033493cf1dc3d2d43
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block fd6033493cf1dc3d2d432ac9fe40dbfe2b13a9ebbcff2fb5f7f7afdf2046c5bb
askfor block e7619a2a2e1076ea3dab 1466000210000000
askfor block fd18d2078bb7b85fb0ad 1466000242000000
askfor block 9697e31e0731ddbb76e8 1466000981000000
askfor block 8ed9d7747e15ce7137f4 1466000996000000
sending getdata: block 3dd830e784342f1fbad6
received block 3dd830e784342f1fbad6
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 3dd830e784342f1fbad63a5e5e6deef48fbe52cb535b25c9913fadfc089106ff
sending getdata: block 9697e31e0731ddbb76e8
received block 9697e31e0731ddbb76e8
ERROR: CheckProofOfStake() : INFO: read txPrev failed

Best regards,
Bleutrade Team.

------------------------------------------------------------------------------

Let me know solution to this, or what this is about. I can forward it to them on my support ticket.

I just emailed them to check.

Also make a request here to add CUBE on bter:

http://support.bter.com/hc/en-us/requests/new

Unless someone..hmm...I can think of one 

maybe so...but we don't know, which is why i'm still waiting on the unanswered question, of why it stopped doing checkpoints in the first place, and wat exactly the steps were taken during rebooting phase

Lmao, think about what  you just asked. it would not be possible because you don't know when you go into a coma, die, etc etc

it's on a machine with access by a single operator unless that person designated a second user to access it in the even he/she couldn't.

http://forum.feathercoin.com/topic/2709/advanced-checkpointing-released

What is checkpointing?
Checkpointing was originally built in to Bitcoin in order to prevent dishonest people reversing transactions and taking back the money they had sent. Imagine someone sends you money and you dispatch goods only to find that they have taken the money back out of your account.

The basic checkpointing feature in Bitcoin makes sure that the software only connects to the blockchain defined by the developers. This is a safety feature to stop malicious users from trying to force clients on to a different blockchain. The blockchain has all the Bitcoin transactions of Bitcoin written into it. Every block in the blockchain has a unique string of characters called a hash. In the client the checkpoints are defined by providing the block number and its hash, this is then compiled and distributed. Clients will only accept the blockchain that has the corresponding block number and hash defined in the code. Checkpointing offers some protection against attackers but only up to the last checkpoint. So malicious users could try to orphan blocks after the last checkpoint and reverse transactions with 51% attacks.

What is Advanced Checkpointing?
Advanced Checkpointing allows us to send out checkpoints without having to redistribute the Feathercoin software. This works by having a ‘master node’ which checkpoints each block it sees on the network protecting it from the attacker. This checkpoint is then picked up by all the other clients on the network which will then ignore any blocks generated by a 51% attack. This protects merchants from transaction reversal and miners from losing their newly minted coins. With Advanced Checkpointing, Feathercoin becomes the most secure of all the Scrypt cryptographic currencies.

Is this a centralised solution?
ACP is a form of centralisation that we have put in place because we believe security comes first. Attacks on this new breed of crypto currencies are on the rise with the attackers becoming more and more resourceful. We are the first Scrypt based coin to respond to this threat by recruiting the best minds in this domain to ensure everyone is protected even those who engage in speculative mining and to whom we owe a debt of gratitude for their patience and understanding.
-------------------

one commenter pointed out:

Radacoin 3 years ago
[quote name=“Bushstar” post=“26405” timestamp=“1377621353”]
… the checkpoint master node is deployed and maintained by the lead developer Peter Bushnell. Currently no other person has access to this system …
[/quote]

Ugh … did a decentralized p2p digital currency just became centralized? Not sure how the (Bitcoin/Litecoin) community will react on this.

Bushstar, what happens if some crooks kidnap you and threaten to cut of your fingers if you don’t checkpoint their blocks.

What happens if you lapse into a coma, die, loose your mind?

What happens if your system gets compromised?

Single point of failure -> not good.

-------------------


So... how is trex at fault?

Wuher BOT [12:22 AM] 
Also, the reality is also that the checkpointing server, being that far behind, can't sync with the other fork either

bittrex-richie [12:28] 
but i've checked this with numerous devs and other individuals.. i dont see how a chain rolling back is our fault

d3m0nkings [12:31 AM] 
ya the thing that doesn't line up, is if checkpoint server failed, then sprout coin should've forked after it stopped doing checkpoints

bittrex-richie [12:31 AM] 
thats not what happens

Wuher BOT [12:32 AM] 
@d3m0nkings: the fork occurs when you bring the checkpoint server back up afterwards

bittrex-richie [12:32 AM] 
if its on the wrong chain

[12:32] 
liek if it was staking

Wuher BOT [12:32 AM] 
(and/or in between, forks can occur if there's no checkpointing server, but that's not guaranteed to happen)

bittrex-richie [12:32 AM] 
it chooses its own staked block instead of what the network was doing the entire time it was offline.

[12:32] 
its all messy when it comes to checkpoint servers

Wuher BOT [12:32 AM] 
and yes, it's only most likely to happen when the checkpointing server is staking
   
d3m0nkings [12:48 AM] 
but richie technically speaking conclusion here is the coin actually didn't have a problem with it's code, it's just watever reason the checkpoint server stopped, (power failure, or w.e.)

[12:48] 
and spot's method of restarting it

[12:48] 
so it wasn't code just human error

[12:48] 
possibly

fuzzyhobbit BOT [12:48 AM] 
I would call it mismanagement of the checkpointing server

d3m0nkings [12:49 AM] 
ya

Wuher BOT [12:49 AM] 
well, it's not a coin issue, it's a blockchain issue

Wuher BOT [12:49 AM] 
which resulted from mismanagement of the checkpoint server

bittrex-richie [12:49 AM] 
agreed with fuzzy/wuher.... what it isn't is the exchanges fault :wink:

d3m0nkings [12:49 AM] 
right but the blockchain issue was the resault of human error

gritt-n-auld [12:50 AM] 
Yes, human error of the one managing the checkpoint server.

He just doesn't want to

I'm syncing a new wallet without having downloaded the bootstrap. this is syncing from 0 right now and look at the checkpoint:

I didn't say he's coming back. don't care either. coin works without him. maybe after some time, someone will jump on board and take over

it's still on there till the 15th for sure. but if you really want the answer to that ask them on slack.bittrex.com

or email their support.

I'm waiting to see also what will happen.

Fork it and if i knew code find a way to make it so he just can't access the new chain to carry over his coins. or make some kind of verification system to allow access by verified individuals only.

It's code surely someone knows something that's possible.