Quote from: digit on March 29, 2017, 06:46:53 AM

Quote from: Matt9301 on March 28, 2017, 01:45:08 PM

Quote from: digit on March 28, 2017, 01:25:01 AM

I think you maybe some of you have self forked from staking too many inputs too quickly at one time or staking before the blockchain had completely downloaded into your client.
Can you give me you deposit address and i can send 1 CAPT to it and you can report back if you get it or not.

My wallet shows number of blocks 1786150, last block 00:45 UTC Tue 28 March ( about 30 mins ago)

If redownloading the chain entirely from network, i was able to get around the 500 blocks with a bat file that closes and restarts the wallet every 10 minutes. You can also close the connections to peers while the wallet is open, it will reconnect and continue downloading but i don't know a way to automate this, but it would work faster this way without having to restart the wallet if you a have a way to do this. When you get to less then 10000 blocks its easier to just close the connections manually and at some point after 5000 blocks it will no longer stop after every 500 blocks and will continue to the most recent block.

Send me your CAPT address, I'll try to send you a bit of CAPTs.. Can you send me a bat file that can restart the wallet every 10 minutes?

If your blockchain is not synced then you cannot send or stake CAPT if you try to do that might be why your having problems with it.

my CAPT wallet getpeerinfo show this and the blockheight 1786229 matches yobit currently, so if i deposit there it should arrive in their wallet within the day (only a few wallets staking so will not be instant)

If the blocks is alot less then this number then it means the blockchain is not completely downloaded and should not try to spend or stake coins until it is.

Code:

"version" : "v1.5.0.0",
"protocolversion" : 60007,
"walletversion" : 60000,

"blocks" : 1786229,
"moneysupply" : 20481952.38815700,
"connections" : 5,

"difficulty" : 0.00024414,
"testnet" : false,

"errors" : "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers."
}

About some of the info
The checkpoint error can be ignored, its because the dev has not updated the wallet with new checkpoints. This error shows in alot of old coins and does prevent using or syncing. (But syncing is meant to be faster if an updated wallet with new checkpoints for blocks is released)

Also moneysupply is not "20481952.38815700," as 16926990.192505 were burned after the distribution.
BannedSeller posted here - https://bitcointalk.org/index.php?topic=683776.msg12927291;topicseen#msg12927291

Quote from: Bannedseller on November 09, 2015, 09:27:14 AM

I have marked your questions 1-4 and I'll answer them one by one to you. (I'm an expert in CAPTcoin as I have joined the initial distribution a year ago)

1. Go to http://yobit.net/en/coinsinfo, search 'CAPT' in the search box, and check the Moneysupply. Then deduct 16926990.192505 from that number (which is burnt from initial distribution). Alternatively you can check http://coinmarketcap.com/currencies/captcoin/ , they have the number calculated, however it is corrected to the nearest integer.

2. In about 12-14 years, provided that no coin age is loss due to lost wallets/transactions. Actually I think it would take more than 20 years.

3. The standard fee is 0.00001 per KB, however some exchanges pay more (e.g. yobit pays 0.002). The fees are burnt instead of giving to the miner (staker).

4. Transaction fees will be the reward, otherwise it will be 0 reward.

so needs to deduct "16926990.192505" from that number to get the current real supply.
so 20481952.38815700-16926990.192505 = 3554962.195652 CAPT

Why my wallet stuck om 1781561 blocks since 3 days ayo, bos to solve it, could you help me ?