Final results from tests of next release
Working dir size before trimming, approximately 45GB
Working dir size after trimming, approximately 7.7GB!
A new version of Credits will be released tomorrow, with blockchain shrinking added and enabled by default.
Announcement will be made here as soon as the release is done.
Topic: CREDITS [CRE] | SHA256 | SIDECHAIN | NEW BLOCK-DEPOSIT FEATURE | OFFICIAL THREAD - page 25. (Read 57394 times)
June 02, 2015, 05:15:35 PM
June 02, 2015, 01:56:17 AM
Downloaded the latest wallet installer but it's not syncing.
Please help me.
Please help me.
Yes, could you please give us some info on what problems you are experiencing?
There are a bunch of instructions here that might help you as well:
http://credits-currency.org/viewforum.php?f=18
June 02, 2015, 12:06:24 AM
Downloaded the latest wallet installer but it's not syncing.
Please help me.
Please help me.
What OS and what error are you getting from the debug log?
June 01, 2015, 11:51:51 PM
Downloaded the latest wallet installer but it's not syncing.
Please help me.
Please help me.
June 01, 2015, 03:41:29 PM
Thanks for all the efforts. After the trimming, can we still use the BTC blockchain to send/receive with bitcoin Core?
As Greydon already mentioned - yes, you should be able to perform those functions still!
June 01, 2015, 12:32:21 PM
Results from tests trimming the working directory
Preliminary tests in trimming the working directory of Credits indicate that substantial gains can be found.
Size before trimming, approximately 45GB
Size after trimming, approximately 12GB
Further gains can be had, but it requires large changes to the internal functionality of Credits, to decouple the Bitcoin blockchain further. This development will be performed in the following months.
There are two main drawbacks to shrinking the working dir by trimming older Bitcoin blocks:
1. -reindex CAN NOT be done after the Bitcoin blockchain has been trimmed. This should not be a problem under normal usage.
2. It is for the time being unclear if -bitcoin_rescan will work as intended. This usually does not matter for a regular Credits user.
As soon as a new version of the wallet is ready for release, more info will be posted here.
Preliminary tests in trimming the working directory of Credits indicate that substantial gains can be found.
Size before trimming, approximately 45GB
Size after trimming, approximately 12GB
Further gains can be had, but it requires large changes to the internal functionality of Credits, to decouple the Bitcoin blockchain further. This development will be performed in the following months.
There are two main drawbacks to shrinking the working dir by trimming older Bitcoin blocks:
1. -reindex CAN NOT be done after the Bitcoin blockchain has been trimmed. This should not be a problem under normal usage.
2. It is for the time being unclear if -bitcoin_rescan will work as intended. This usually does not matter for a regular Credits user.
As soon as a new version of the wallet is ready for release, more info will be posted here.
Thanks for all the efforts. After the trimming, can we still use the BTC blockchain to send/receive with bitcoin Core?
Yes, you will still be able to perform all functions except those two listed above
June 01, 2015, 05:36:49 AM
Results from tests trimming the working directory
Preliminary tests in trimming the working directory of Credits indicate that substantial gains can be found.
Size before trimming, approximately 45GB
Size after trimming, approximately 12GB
Further gains can be had, but it requires large changes to the internal functionality of Credits, to decouple the Bitcoin blockchain further. This development will be performed in the following months.
There are two main drawbacks to shrinking the working dir by trimming older Bitcoin blocks:
1. -reindex CAN NOT be done after the Bitcoin blockchain has been trimmed. This should not be a problem under normal usage.
2. It is for the time being unclear if -bitcoin_rescan will work as intended. This usually does not matter for a regular Credits user.
As soon as a new version of the wallet is ready for release, more info will be posted here.
Preliminary tests in trimming the working directory of Credits indicate that substantial gains can be found.
Size before trimming, approximately 45GB
Size after trimming, approximately 12GB
Further gains can be had, but it requires large changes to the internal functionality of Credits, to decouple the Bitcoin blockchain further. This development will be performed in the following months.
There are two main drawbacks to shrinking the working dir by trimming older Bitcoin blocks:
1. -reindex CAN NOT be done after the Bitcoin blockchain has been trimmed. This should not be a problem under normal usage.
2. It is for the time being unclear if -bitcoin_rescan will work as intended. This usually does not matter for a regular Credits user.
As soon as a new version of the wallet is ready for release, more info will be posted here.
Thanks for all the efforts. After the trimming, can we still use the BTC blockchain to send/receive with bitcoin Core?
June 01, 2015, 05:12:59 AM
Results from tests trimming the working directory
Preliminary tests in trimming the working directory of Credits indicate that substantial gains can be found.
Size before trimming, approximately 45GB
Size after trimming, approximately 12GB
Further gains can be had, but it requires large changes to the internal functionality of Credits, to decouple the Bitcoin blockchain further. This development will be performed in the following months.
There are two main drawbacks to shrinking the working dir by trimming older Bitcoin blocks:
1. -reindex CAN NOT be done after the Bitcoin blockchain has been trimmed. This should not be a problem under normal usage.
2. It is for the time being unclear if -bitcoin_rescan will work as intended. This usually does not matter for a regular Credits user.
As soon as a new version of the wallet is ready for release, more info will be posted here.
Preliminary tests in trimming the working directory of Credits indicate that substantial gains can be found.
Size before trimming, approximately 45GB
Size after trimming, approximately 12GB
Further gains can be had, but it requires large changes to the internal functionality of Credits, to decouple the Bitcoin blockchain further. This development will be performed in the following months.
There are two main drawbacks to shrinking the working dir by trimming older Bitcoin blocks:
1. -reindex CAN NOT be done after the Bitcoin blockchain has been trimmed. This should not be a problem under normal usage.
2. It is for the time being unclear if -bitcoin_rescan will work as intended. This usually does not matter for a regular Credits user.
As soon as a new version of the wallet is ready for release, more info will be posted here.
June 01, 2015, 05:04:02 AM
So the BTC blockchain is just used for claiming the Credits. That is just like giving away Credits to BTC owners to attract new users? How many Credits have been claimed?
I think the major new features are PoD and S curve emission. 15 mins block time is also good. In the future, if Credits have more transactions, the block time can be reduced.
Is there any other PoD coin?
Yes, it is like giving away Credits to BTC users, but some key points are good to keep in mind:
1. It is not a snapshot in time but keeping track of the current state of BTC ownership. So it is continually offered up to any current BTC user, minus the coins that already has been claimed.
2. By offering a part (the major part actually) of the system to BTC owners, the chain is reinforced with the effort put into creating each Bitcoin into the Credits blockchain. It's as much a matter of security; getting a wide distribution as possible, as solving the initial distribution problem. It is also a way to offer a conversion path and give incentives for users of a system with certain weaknesses, namely the security and efficiency aspects of pure proof-of-work, to another system where those issues (probably) has been solved.
Not many Bitcoins have been claimed so far, all the info is in the blockchain and I expect the claiming to start to have more effect once Credits gets more well known.
It should also be noted that the Credits wallet works as a combined Bitcoin/Credits wallet since the information to send/receive BTC is already there. So the Bitcoin blockchain is actually used for something else than just claiming.
There are no other PoD coin around, although the system has similarities with proof of stake systems. Note that the system is a combined pos/pod system, to solve the so called nothing-at-stake problem. The claiming system is also a key functionality in this aspect.
June 01, 2015, 04:20:46 AM
Is the bitcoin chain just used to clam the Credits at the moment? Are we going to move something back to BTC blockchain? If not, then there is no point in keep the large disk space occupied.
Nothing is moved back to the BTC chain. Within a few days, a version trimming away older parts of the Bitcoin blockchain will be released. Tests are ongoing as we speak,
So the BTC blockchain is just used for claiming the Credits. That is just like giving away Credits to BTC owners to attract new users? How many Credits have been claimed?
I think the major new features are PoD and S curve emission. 15 mins block time is also good. In the future, if Credits have more transactions, the block time can be reduced.
Is there any other PoD coin?
May 31, 2015, 01:42:26 PM
Is the bitcoin chain just used to clam the Credits at the moment? Are we going to move something back to BTC blockchain? If not, then there is no point in keep the large disk space occupied.
Nothing is moved back to the BTC chain. Within a few days, a version trimming away older parts of the Bitcoin blockchain will be released. Tests are ongoing as we speak,
May 31, 2015, 03:46:00 AM
Is the bitcoin chain just used to clam the Credits at the moment? Are we going to move something back to BTC blockchain? If not, then there is no point in keep the large disk space occupied.
May 29, 2015, 07:49:29 PM
just testing out some different graphics techniques
May 29, 2015, 07:09:02 PM
A request for comments has been posted in the alt coin section. It is listed here below as well, for ease of reference.
https://bitcointalk.org/index.php?topic=1074489.new#new
-----------------------------------------
This is a request for comments regarding updates to the Credits difficulty retarget algorithm.
Background:
The Credit blockchain is generated from a combined proof-of-work/proof-of-deposit system. This deposit system is still coming into effect as the blockchain evolves and it will start to have larger effects on the block creation process in approximately two months time. At the moment it is unknown what the effects on the difficulty and block creation process will be when deposit starts to have a larger impact. An adjustment of the difficulty retargeting mechanism is therefore suggested, to allow for faster adaption of the difficulty in case of varying deposit and processing power inputs. Faster adaption of the difficulty will also prevent the block creation process from being stuck to long in a too high difficulty.
Suggested adjustment:
Credits has so far been using the same difficulty retargeting mechanism as Bitcoin. That means that an adjustment of the difficulty happens every 2016 block. If the block creation process has been longer than two weeks for the latest 2016 blocks, the difficulty will rise, and it will fall if the block creation process has been faster. The difficulty adjustment is capped with a factor of 4 up or down, to prevent too large swings in difficulty.
The suggested adjustment of the retargeting mechanism is to have more frequent adjustments, with a lower cap for each adjustment. The retargeting period should be lowered to 1/8 of 2016 blocks, which means a difficulty adjustment every 252 blocks. The cap would be a factor of 1.25 for each period, giving a maximum difficulty adjustment of 5.96 over a period of 2016 blocks, as compared to Bitcoins 4.
An alternative proposal would be adjustment every 504 blocks, with a cap of 1.5. This would give a maximum adjustment of 5.06 for every 2016 blocks.
The new retargeting algorithm would be scheduled to start to have effect somewhere at block 24000 to 26000, or later if deemed necessary.
https://bitcointalk.org/index.php?topic=1074489.new#new
-----------------------------------------
This is a request for comments regarding updates to the Credits difficulty retarget algorithm.
Background:
The Credit blockchain is generated from a combined proof-of-work/proof-of-deposit system. This deposit system is still coming into effect as the blockchain evolves and it will start to have larger effects on the block creation process in approximately two months time. At the moment it is unknown what the effects on the difficulty and block creation process will be when deposit starts to have a larger impact. An adjustment of the difficulty retargeting mechanism is therefore suggested, to allow for faster adaption of the difficulty in case of varying deposit and processing power inputs. Faster adaption of the difficulty will also prevent the block creation process from being stuck to long in a too high difficulty.
Suggested adjustment:
Credits has so far been using the same difficulty retargeting mechanism as Bitcoin. That means that an adjustment of the difficulty happens every 2016 block. If the block creation process has been longer than two weeks for the latest 2016 blocks, the difficulty will rise, and it will fall if the block creation process has been faster. The difficulty adjustment is capped with a factor of 4 up or down, to prevent too large swings in difficulty.
The suggested adjustment of the retargeting mechanism is to have more frequent adjustments, with a lower cap for each adjustment. The retargeting period should be lowered to 1/8 of 2016 blocks, which means a difficulty adjustment every 252 blocks. The cap would be a factor of 1.25 for each period, giving a maximum difficulty adjustment of 5.96 over a period of 2016 blocks, as compared to Bitcoins 4.
An alternative proposal would be adjustment every 504 blocks, with a cap of 1.5. This would give a maximum adjustment of 5.06 for every 2016 blocks.
The new retargeting algorithm would be scheduled to start to have effect somewhere at block 24000 to 26000, or later if deemed necessary.
Just gave my opinion, anyone agree/disagree with me?
May 29, 2015, 06:01:32 PM
A request for comments has been posted in the alt coin section. It is listed here below as well, for ease of reference.
https://bitcointalk.org/index.php?topic=1074489.new#new
-----------------------------------------
This is a request for comments regarding updates to the Credits difficulty retarget algorithm.
Background:
The Credit blockchain is generated from a combined proof-of-work/proof-of-deposit system. This deposit system is still coming into effect as the blockchain evolves and it will start to have larger effects on the block creation process in approximately two months time. At the moment it is unknown what the effects on the difficulty and block creation process will be when deposit starts to have a larger impact. An adjustment of the difficulty retargeting mechanism is therefore suggested, to allow for faster adaption of the difficulty in case of varying deposit and processing power inputs. Faster adaption of the difficulty will also prevent the block creation process from being stuck to long in a too high difficulty.
Suggested adjustment:
Credits has so far been using the same difficulty retargeting mechanism as Bitcoin. That means that an adjustment of the difficulty happens every 2016 block. If the block creation process has been longer than two weeks for the latest 2016 blocks, the difficulty will rise, and it will fall if the block creation process has been faster. The difficulty adjustment is capped with a factor of 4 up or down, to prevent too large swings in difficulty.
The suggested adjustment of the retargeting mechanism is to have more frequent adjustments, with a lower cap for each adjustment. The retargeting period should be lowered to 1/8 of 2016 blocks, which means a difficulty adjustment every 252 blocks. The cap would be a factor of 1.25 for each period, giving a maximum difficulty adjustment of 5.96 over a period of 2016 blocks, as compared to Bitcoins 4.
An alternative proposal would be adjustment every 504 blocks, with a cap of 1.5. This would give a maximum adjustment of 5.06 for every 2016 blocks.
The new retargeting algorithm would be scheduled to start to have effect somewhere at block 24000 to 26000, or later if deemed necessary.
https://bitcointalk.org/index.php?topic=1074489.new#new
-----------------------------------------
This is a request for comments regarding updates to the Credits difficulty retarget algorithm.
Background:
The Credit blockchain is generated from a combined proof-of-work/proof-of-deposit system. This deposit system is still coming into effect as the blockchain evolves and it will start to have larger effects on the block creation process in approximately two months time. At the moment it is unknown what the effects on the difficulty and block creation process will be when deposit starts to have a larger impact. An adjustment of the difficulty retargeting mechanism is therefore suggested, to allow for faster adaption of the difficulty in case of varying deposit and processing power inputs. Faster adaption of the difficulty will also prevent the block creation process from being stuck to long in a too high difficulty.
Suggested adjustment:
Credits has so far been using the same difficulty retargeting mechanism as Bitcoin. That means that an adjustment of the difficulty happens every 2016 block. If the block creation process has been longer than two weeks for the latest 2016 blocks, the difficulty will rise, and it will fall if the block creation process has been faster. The difficulty adjustment is capped with a factor of 4 up or down, to prevent too large swings in difficulty.
The suggested adjustment of the retargeting mechanism is to have more frequent adjustments, with a lower cap for each adjustment. The retargeting period should be lowered to 1/8 of 2016 blocks, which means a difficulty adjustment every 252 blocks. The cap would be a factor of 1.25 for each period, giving a maximum difficulty adjustment of 5.96 over a period of 2016 blocks, as compared to Bitcoins 4.
An alternative proposal would be adjustment every 504 blocks, with a cap of 1.5. This would give a maximum adjustment of 5.06 for every 2016 blocks.
The new retargeting algorithm would be scheduled to start to have effect somewhere at block 24000 to 26000, or later if deemed necessary.
May 29, 2015, 02:18:38 AM
a design i did that never won
Hi there.
yes, we are interested in getting a graphic profile in place. Send me a PM here if you are interested.
Do note that this is Credits/CRE - a currency started about two months ago. It has no relation to any other currency.
May 28, 2015, 06:42:35 PM
a design i did that never won
You made that for a previous coin that was also called Credits? I think Gabriel was looking for a graphic designer for some infographics and general banners also, He'll see this when he wakes up and most likely PM you haha.
Large reduction of working dir for Credits, preliminary test results and release plan
Test are ongoing with trimming of the built in Bitcoin blockchain to reduce the size of the working directory. Preliminary results indicate that large reductions are possible.
A test trimming of the testnet working dir has been done.
Size before reduction, 2.77GB.
Size after reduction, 0.7GB.
This is a reduction to 25% of the original size. Larger gains are expected on mainnet.
The target size for mainnet is 3-8GB.
Further announcements will be done here soon. Release planned to be done within a week.
Test are ongoing with trimming of the built in Bitcoin blockchain to reduce the size of the working directory. Preliminary results indicate that large reductions are possible.
A test trimming of the testnet working dir has been done.
Size before reduction, 2.77GB.
Size after reduction, 0.7GB.
This is a reduction to 25% of the original size. Larger gains are expected on mainnet.
The target size for mainnet is 3-8GB.
Further announcements will be done here soon. Release planned to be done within a week.
Nice work man, this is such a huge move! More users will be able to get credits running on their machine, and make the rest of our lives so much easier. Infinite vibes.
May 28, 2015, 06:14:19 PM
a design i did that never won
May 28, 2015, 05:45:50 PM
Large reduction of working dir for Credits, preliminary test results and release plan
Test are ongoing with trimming of the built in Bitcoin blockchain to reduce the size of the working directory. Preliminary results indicate that large reductions are possible.
A test trimming of the testnet working dir has been done.
Size before reduction, 2.77GB.
Size after reduction, 0.7GB.
This is a reduction to 25% of the original size. Larger gains are expected on mainnet.
The target size for mainnet is 3-8GB.
Further announcements will be done here soon. Release planned to be done within a week.
Test are ongoing with trimming of the built in Bitcoin blockchain to reduce the size of the working directory. Preliminary results indicate that large reductions are possible.
A test trimming of the testnet working dir has been done.
Size before reduction, 2.77GB.
Size after reduction, 0.7GB.
This is a reduction to 25% of the original size. Larger gains are expected on mainnet.
The target size for mainnet is 3-8GB.
Further announcements will be done here soon. Release planned to be done within a week.
May 27, 2015, 03:30:46 PM
Up until a few days ago, I've been having problems getting the client to sync. Like for hours on end, it would just stick and not update the blockchain for bitcoin and sometimes credits. Finally got it all working with the new client. So hopefully I won't receive any more movingclaimtip:00 errors. 
Wohoo! Great to have you back with a wallet running. And, the new client is planned to be more stable. So, fingers crossed.
Welcome back. Get a miner running. I know I have.
Jump to: