Topic: CREDITS [CRE] | SHA256 | SIDECHAIN | NEW BLOCK-DEPOSIT FEATURE | OFFICIAL THREAD - page 8. (Read 57384 times)

Greydon told me price would be somewhere close to 0.001 per CRE but its way too low. Do we expect price to rise up in near future?

Well, good time to buy then I suppose. I for sure am.

The 0.9.1.60 working directory and 0.9.1.74 working directory are unfortunately incompatible. So if you are trying to run the two versions against the same working directory, they may overwrite each other. Are you doing that or do you have two different working dirs?

The price is too low as per my expectations 

I synced from 9.1.73.  The strange thing is I also started getting this error on 9.1.60 shortly after 9.1.74 was released.  Not sure if there is any connection or not.  My 9.1.60 version was synced from torrent.

Thanks for a good error report. Did you use the provided torrent or synced from scratch?

Will look into this straight away.

Awesome , nice to hear you're still around Stick with us, we're in it for the long term!

Its been awhile since I checked out the thread but CRE has come a long way in such a short time! Im still holding mine keep up the good work! 

I'm having crashing issues on 9.1.74 running in -server mode.  Any time I try to send a transaction i get a fatal error that closes down the program.  I have no problem sending transactions when not in -server mode.  I now occasionally get this error in regular mode as well.   I am using the Windows 64 bit program in Win 7.  Also, when solving a block it no longer says "Mined" under the type column in the transaction.  It just says deposit.  The pickaxe is now gone as well.  Just cosmetic but letting ya know.


Debug output:  

2015-09-09 02:17:24 ERROR: deposit transaction could not sign coinbase
2015-09-09 02:17:24
ERROR! IncrementExtraNonce() : Failed to recalculate coinbase as deposit. Miner exiting.


I'm also getting a popup window titled "MinGW Runtime -Assertion"

Inside the window says: File: miner.cpp.Line 1021
                                        Expression: false

Took me a couple re-reads to understand that, but would it be possible to change that rule? Or add some catch in the source for deposit transactions which use a coinbase tx?

Also, Yeah! Very good job! I got the torrent and was synced in less than an hour

Much faster sync in 74.  Props to Dev!

It's because a block reward (a coinbase tx) can be used as deposit directly. Or rather, a deposit tx can spend the coinbase tx in the same block. If the deposit change could be spent straight away, you would be able to get around the coinbase maturity rule by directly spending the coinbase tx with a deposit tx and sending everything as change. That's the simple reason the restriction is there.

You could of course argue that the restriction only should be there if the deposit tx spends a coinbase tx. To simplify the validation of blocks, however, the rule is applied to all deposit txs.

Have a quick question on prepared deposits.  Why does it take 101 confirmations to get the extra change back?

It's not a big deal I was just curious.

Just checked the sum on the deposit page of Qt. About 1.467 million coins for the moment.

How many Credits are in circulation?

Version 0.9.1.74 of Credits client released. Update focusing on disk usage, speed and adding features

A new release of the Credits client is out now. This is a long overdue version that addresses stability, speed and disk usage.

Updates in this release:
- Version number bumped to *.74.
- The command bitcoin_listtransactions has been added.
- The command bitcoin_validateaddress has been added.
- The command bitcoin_sendtoaddress has been added.
- The command bitcoin_getnewaddress has been added.
- The command bitcoin_getbalance has been added.
- The command bitcoin_getrawtransaction has been added.
- Bitcoin transaction resending enabled.
- Skipping script validation of older Bitcoin blocks for quicker blockchain verification.
- Enabling getblocktemplate rpc call.
- Compressing all bitcoin blocks on disk to save approximately 60% of block disk space.
- New checkpoint added.
- Various bug fixes.
- Joining the threads that handles messages for Credits
and Bitcoin.
- Bug fixes related to syncing speed and blockchain trimming.

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

How to Upgrade
If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions), then run the
installer (on Windows) or just copy over /Applications/Credits-Qt (on Mac) or
creditsd/credits-qt (on Linux).

!!!BEFORE YOU START THE WALLET, MAKE SURE TO MAKE BACKUP COPIES OF THE FILES CREDITS_WALLET.DAT
AND BITCOIN_WALLET.DAT, IF YOU HAVE A PREVIOUS INSTALLATION.!!!

NB! There is a minor bug that causes older working directories to be incompatible with this version. A fix will be released in the coming days. If you do not want to resync the blockchain, wait until that fix release is out. NB!

The syncing process can be quite long, depending on your computer and your network. Between one and two days is not uncommon, if you are not initialising from a prebuilt working directory, distributed with a torrent.

Start credits-qt with the command:
credits-qt.exe -reindex -checklevel=2

or start creditsd with the command:
creditsd.exe -reindex -checklevel=2

Once installation is done, we highly recommend you to bootstrap the blockchain download and sync by downloading an up to date working directory:
Quick initialisation from torrent file

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

Downloads can be found at:
http://credits-currency.org/viewforum.php?f=5

Getting started instructions can be found at:
http://credits-currency.org/viewforum.php?f=18

Release version 0.9.1.74 in a few hours

New release will finally be done in a few hours.

Version bumped to 0.9.1.74 to prevent people from accidentally mixing up beta versions from the new release version. More info as soon as the build is ready, currently ongoing.

Release 0.9.1.74 delayed one last day

There have been some minor issues with the blockfile trimming functionality during last stages of testing. This is not a big problematic issue, but I do want the release to work as smoothly as possible. I will therefore make the release tomorrow instead of today.

More info in approx 12 hours.

Greydon is correct, the torrent file can not be used together with 0.9.1.73.

I'll create a new one with the release today.

Edit: And as Greydon says, if you want to mine, start with 0.9.1.60, the latest stable version.

I don't think you can use the torrent files on version 0.9.1.73, as the torrent files are from a previous version. The current version requires parsing of the bitcoin blocks in their original state and compressing them. You could use an earlier version of the wallet, I believe the last most stable version is 0.60 for GPU mining, and that version can be initialized from the torrent files.

Welcome to the CRE! Sorry your first experience is with a beta wallet