[ANN] Bitcredit/CRE - first sidechain, claimable from Bitcoin, pow/pod

[starblocks]

Perhaps this one needs nipping in the bud as well

[1715077782]

1715077782

[1715077782]

1715077782

[1715077782]

1715077782

[1715077782]

1715077782

[GreydonIselmoe]

Any news on a block explorer?

[Gabriel Eiger]

ok, i'll check back with the next version.

New version is out. You should definitely download it and try the claiming again.

Wooo finally got it up and running.

For KLYE, here's my addy : 1K1WLbDF14Hs2y4qvuSgDHYQ7ytizYfLSU

Great to hear. Good luck mining and continue watching the forums for more info. Source release is imminent.

[ltcnim]

ok, i'll check back with the next version.

New version is out. You should definitely download it and try the claiming again.

worked! thx.

[Gabriel Eiger]

ok, i'll check back with the next version.

New version is out. You should definitely download it and try the claiming again.

worked! thx.

Great. Thank you for trying it out.

And as a side note - you just made the total monetary base increase in the same way as when someone finds a new block, thereby moving us towards the next reward update and increasing the deposit requirement.

[Gabriel Eiger]

Any news on a block explorer?

Sorry no development as of yet. I'll post a thread with a rough development roadmap tonight.

You know that there are a lot of commands that you can execute through the Bitcredit-Qt console where you can emulate a lot of the functionality found in a block explorer, right?

Try the help command for a full list.

[Gabriel Eiger]

Perhaps this one needs nipping in the bud as well

Care to elaborate?

[MRKLYE]

ok, i'll check back with the next version.

New version is out. You should definitely download it and try the claiming again.

worked! thx.

Post your Bitcredit (CRE) address and receive your 10 CRE welcome bonus!

[ltcnim]

ok, i'll check back with the next version.

New version is out. You should definitely download it and try the claiming again.

worked! thx.

Post your Bitcredit (CRE) address and receive your 10 CRE welcome bonus!

thx, but I already found enough blocks Just add em to your faucet for new users.

[MRKLYE]

ok, i'll check back with the next version.

New version is out. You should definitely download it and try the claiming again.

worked! thx.

Post your Bitcredit (CRE) address and receive your 10 CRE welcome bonus!

thx, but I already found enough blocks Just add em to your faucet for new users.

Alrighty. Very generous of you. 

[Gabriel Eiger]

Draft for a development roadmap and focus areas
http://bitcredit-currency.org/viewtopic.php?f=24&t=653

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

The resources that are available for development ahead are limited. It is therefore important to set a roadmap that is adapted to the requirements from the community. Here below are listed some key areas that have been identified as desired or otherwise are of high priority. There are no order of priority in the list below.

- Add feedback here on what areas you consider to be the highest ranking ones.

- Feedback on what other key areas that you think have a high priority are very welcome.

- Volunteers for development or other types of support are quite welcome.

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

- Bitcredit blockchain explorer
Online blockchain explorers are helpful in determining the state of the current blockchain and can be used for many purposes, among them to get an “official” image of which the current active chain is.

- Incorporate newer features from Bitcoin
The version of Bitcoin used internally in Bitcredit is 0.9.1. This version was released last summer and several key areas in Bitcoin has seen quite a lot of development since then. These features should be incorporated into both the internal Bitcoin client, and also where applicable, be added to the source code of Bitcredit. These improvements are among lots of others “headers first” blockchain synching, preparations for increased block size and improvements for increased transaction volumes.

- Adding Bitcoin client capabilities
Since the client is already downloading and tracking the Bitcoin blockchain adding the possibility to send Bitcoins from the client is quite straightforward. There are also other features of the Bitcoin client that could be incorporated, effectively turning the Bitcredit client into a Bitcoin client as well. Those features would remove the need to store the Bitcoin blockchain twice, if a user also has a Bitcoin client installed. This would actually enable a user to forget about the Bitcoin client altogether and instead use the Bitcredit client for both Bitcoin and Bitcredit.

- Lightweight client
For the moment it is not possible to use Bitcredit without downloading a complete copy of the Bitcoin blockchain. This could be a blocker for wider adoption of Bitcredit. A client could be created that mostly uses online sources for verification, thereby simplifying the startup process and removing the storage requirements for the client.

- New seeders and fixed nodes
For the stability of the network and for wider distribution it is important to decentralise the process of reaching the network as much as possible. Anyone who wants to volunteer a seeder node or a fixed node should get in contact with the Bitcredit developers for inclusion in the source code.

- Development or integration with exchanges
Although this is a process that usually happens naturally with existing exchanges there may be a need to develop better coin exchange into the client, or develop freestanding exchanges.

- Evolve deposit features
The deposit process is for the moment a manual one. A miner creates a set of deposits and then starts the miner, which uses the deposits to create new blocks. When the requirement for deposits grow, as the monetary base grows, the need for automated processes to handle deposits will grow as well. A streamlined process to prepare deposits automatically by the miner could prove useful in this situation.

- Develop miner-depositor integration
A deposit-based proof-of-work system has two roles participating in the mining process, the miner and the depositor. These two are normally the same entities but as the system evolves, they will probably separate. The miner will provide the hashing power, and the depositor will offer up deposits for a fee taken from the reward. A system where these two roles can find each other and integrate can be built into the client, or be built as a separate miner system. Either way, this will be a natural step in the evolution of the transaction verification process.

- GPU mining
A “natural” evolution in hash-based verification are improvements with the purpose of making the hashing process more efficient. The normal development phases are first CPU mining, then GPU mining, where a GPU is more efficient in running simple calculations in parallell, followed by creation of so called ASICs. It may be useful to assist in the development of GPU integration, to level the playfield for newcomers.

- Verification of the claiming process
Auditors that can audit the claiming process are welcome. Contact the developers of Bitcredit for a run down of how the system works.

[GreydonIselmoe]

Draft for a development roadmap and focus areas
http://bitcredit-currency.org/posting.php?mode=edit&f=24&p=1190

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

The resources that are available for development ahead are limited. It is therefore important to set a roadmap that is adapted to the requirements from the community. Here below are listed some key areas that have been identified as desired or otherwise are of high priority. There are no order of priority in the list below.

- Add feedback here on what areas you consider to be the highest ranking ones.

- Feedback on what other key areas that you think have a high priority are very welcome.

- Volunteers for development or other types of support are quite welcome.

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

- Bitcredit blockchain explorer
Online blockchain explorers are helpful in determining the state of the current blockchain and can be used for many purposes, among them to get an “official” image of which the current active chain is.

- Incorporate newer features from Bitcoin
The version of Bitcoin used internally in Bitcredit is 0.9.1. This version was released last summer and several key areas in Bitcoin has seen quite a lot of development since then. These features should be incorporated into both the internal Bitcoin client, and also where applicable, be added to the source code of Bitcredit. These improvements are among lots of others “headers first” blockchain synching, preparations for increased block size and improvements for increased transaction volumes.

- Adding Bitcoin client capabilities
Since the client is already downloading and tracking the Bitcoin blockchain adding the possibility to send Bitcoins from the client is quite straightforward. There are also other features of the Bitcoin client that could be incorporated, effectively turning the Bitcredit client into a Bitcoin client as well. Those features would remove the need to store the Bitcoin blockchain twice, if a user also has a Bitcoin client installed. This would actually enable a user to forget about the Bitcoin client altogether and instead use the Bitcredit client for both Bitcoin and Bitcredit.

- Lightweight client
For the moment it is not possible to use Bitcredit without downloading a complete copy of the Bitcoin blockchain. This could be a blocker for wider adoption of Bitcredit. A client could be created that mostly uses online sources for verification, thereby simplifying the startup process and removing the storage requirements for the client.

- New seeders and fixed nodes
For the stability of the network and for wider distribution it is important to decentralise the process of reaching the network as much as possible. Anyone who wants to volunteer a seeder node or a fixed node should get in contact with the Bitcredit developers for inclusion in the source code.

- Development or integration with exchanges
Although this is a process that usually happens naturally with existing exchanges there may be a need to develop better coin exchange into the client, or develop freestanding exchanges.

- Evolve deposit features
The deposit process is for the moment a manual one. A miner creates a set of deposits and then starts the miner, which uses the deposits to create new blocks. When the requirement for deposits grow, as the monetary base grows, the need for automated processes to handle deposits will grow as well. A streamlined process to prepare deposits automatically by the miner could prove useful in this situation.

- Develop miner-depositor integration
A deposit-based proof-of-work system has two roles participating in the mining process, the miner and the depositor. These two are normally the same entities but as the system evolves, they will probably separate. The miner will provide the hashing power, and the depositor will offer up deposits for a fee taken from the reward. A system where these two roles can find each other and integrate can be built into the client, or be built as a separate miner system. Either way, this will be a natural step in the evolution of the transaction verification process.

- GPU mining
A “natural” evolution in hash-based verification are improvements with the purpose of making the hashing process more efficient. The normal development phases are first CPU mining, then GPU mining, where a GPU is more efficient in running simple calculations in parallell, followed by creation of so called ASICs. It may be useful to assist in the development of GPU integration, to level the playfield for newcomers.

- Verification of the claiming process
Auditors that can audit the claiming process are welcome. Contact the developers of Bitcredit for a run down of how the system works. the system works.

Is this in order of priority? As in, the top priority being a block explorer, and lowest priority being GPU mining/Verification of claims

[Gabriel Eiger]

Draft for a development roadmap and focus areas
http://bitcredit-currency.org/viewtopic.php?f=24&t=653

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

The resources that are available for development ahead are limited. It is therefore important to set a roadmap that is adapted to the requirements from the community. Here below are listed some key areas that have been identified as desired or otherwise are of high priority. There are no order of priority in the list below.

- Add feedback here on what areas you consider to be the highest ranking ones.

- Feedback on what other key areas that you think have a high priority are very welcome.

- Volunteers for development or other types of support are quite welcome.

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

- Bitcredit blockchain explorer
Online blockchain explorers are helpful in determining the state of the current blockchain and can be used for many purposes, among them to get an “official” image of which the current active chain is.

- Incorporate newer features from Bitcoin
The version of Bitcoin used internally in Bitcredit is 0.9.1. This version was released last summer and several key areas in Bitcoin has seen quite a lot of development since then. These features should be incorporated into both the internal Bitcoin client, and also where applicable, be added to the source code of Bitcredit. These improvements are among lots of others “headers first” blockchain synching, preparations for increased block size and improvements for increased transaction volumes.

- Adding Bitcoin client capabilities
Since the client is already downloading and tracking the Bitcoin blockchain adding the possibility to send Bitcoins from the client is quite straightforward. There are also other features of the Bitcoin client that could be incorporated, effectively turning the Bitcredit client into a Bitcoin client as well. Those features would remove the need to store the Bitcoin blockchain twice, if a user also has a Bitcoin client installed. This would actually enable a user to forget about the Bitcoin client altogether and instead use the Bitcredit client for both Bitcoin and Bitcredit.

- Lightweight client
For the moment it is not possible to use Bitcredit without downloading a complete copy of the Bitcoin blockchain. This could be a blocker for wider adoption of Bitcredit. A client could be created that mostly uses online sources for verification, thereby simplifying the startup process and removing the storage requirements for the client.

- New seeders and fixed nodes
For the stability of the network and for wider distribution it is important to decentralise the process of reaching the network as much as possible. Anyone who wants to volunteer a seeder node or a fixed node should get in contact with the Bitcredit developers for inclusion in the source code.

- Development or integration with exchanges
Although this is a process that usually happens naturally with existing exchanges there may be a need to develop better coin exchange into the client, or develop freestanding exchanges.

- Evolve deposit features
The deposit process is for the moment a manual one. A miner creates a set of deposits and then starts the miner, which uses the deposits to create new blocks. When the requirement for deposits grow, as the monetary base grows, the need for automated processes to handle deposits will grow as well. A streamlined process to prepare deposits automatically by the miner could prove useful in this situation.

- Develop miner-depositor integration
A deposit-based proof-of-work system has two roles participating in the mining process, the miner and the depositor. These two are normally the same entities but as the system evolves, they will probably separate. The miner will provide the hashing power, and the depositor will offer up deposits for a fee taken from the reward. A system where these two roles can find each other and integrate can be built into the client, or be built as a separate miner system. Either way, this will be a natural step in the evolution of the transaction verification process.

- GPU mining
A “natural” evolution in hash-based verification are improvements with the purpose of making the hashing process more efficient. The normal development phases are first CPU mining, then GPU mining, where a GPU is more efficient in running simple calculations in parallell, followed by creation of so called ASICs. It may be useful to assist in the development of GPU integration, to level the playfield for newcomers.

- Verification of the claiming process
Auditors that can audit the claiming process are welcome. Contact the developers of Bitcredit for a run down of how the system works.

Is this in order of priority? As in, the top priority being a block explorer, and lowest priority being GPU mining/Verification of claims

No, they are not in any particular order. I'd be glad to get input on what you consider a good priority. And if there are other areas of interest that you think should be addressed.

[Markov]

I'd rather see it on an exchange before GPU, before ROI goes down the drain.

Have you contacted any exchange yet?

[ltcnim]

Well, since this is SHA256, you can skip the GPU and directly go to ASIC

[Gabriel Eiger]

I'd rather see it on an exchange before GPU, before ROI goes down the drain.

Have you contacted any exchange yet?

Thank you for the input.

Yes, I agree, although once the source is released (probably tomorrow) it is only a matter of time before the code gets hooked into a GPU miner. That can not be controlled, but maybe shouldn't be actively encouraged by focusing core development effort in that area.

No exchanges have been contacted yet. Any suggestions on suitable ones?

[GreydonIselmoe]

The top 5 priorities if I had any say, would be:

1. Blockchain explorer (Just adds a more "official" feel to the coin, and some verification)

2. Bitcoin client capabilities. (This is a big one, the ability to send bitcoins from the bitcredit core, basically merging the two, would be incredible for the market)

3. Lightweight client (Kind of following from #2, if you were able to share block directory files then they would both come hand-in-hand)

4. GPU miner (Self explanatory, the more ability we give users to mine, the more mining will occur and more users it will attract. This could be added after an exchange has accepted us, however)

5. Exchanges (Once the above 4 features are implemented, I think it would have proved to everyone how promising this coin is, and dedicated the developer is. An exchange would have a hard time saying no!)

But that's just my 2 cents

[Gabriel Eiger]

Well, since this is SHA256, you can skip the GPU and directly go to ASIC

I am not aware of how the exact implementation of Bitcoin ASICs has been done, but I imagine that they've just moved the final step, the SHA256 double hashing onto the circuits, with the rest of the code running from a standard C++ program. In that case you are right, then it's just a matter of adapting the Bitcredit source to hook into the ASIC hasher.

As a side note, this is one of the reasons that Bitcredit runs with a deposit system. Not to prevent the rise of ASICs, but to disarm them as a complete competitive advantage.

[GreydonIselmoe]

I'd rather see it on an exchange before GPU, before ROI goes down the drain.

Have you contacted any exchange yet?

Thank you for the input.

Yes, I agree, although once the source is released (probably tomorrow) it is only a matter of time before the code gets hooked into a GPU miner. That can not be controlled, but maybe shouldn't be actively encouraged by focusing core development effort in that area.

No exchanges have been contacted yet. Any suggestions on suitable ones?

I would petition C-CEX, Cryptsy, and Bleutrade. However almost any exchange accepting CRE, is a success.

[Gabriel Eiger]

The top 5 priorities if I had any say, would be:

1. Blockchain explorer (Just adds a more "official" feel to the coin, and some verification)

2. Bitcoin client capabilities. (This is a big one, the ability to send bitcoins from the bitcredit core, basically merging the two, would be incredible for the market)

3. Lightweight client (Kind of following from #2, if you were able to share block directory files then they would both come hand-in-hand)

4. GPU miner (Self explanatory, the more ability we give users to mine, the more mining will occur and more users it will attract. This could be added after an exchange has accepted us, however)

5. Exchanges (Once the above 4 features are implemented, I think it would have proved to everyone how promising this coin is, and dedicated the developer is. An exchange would have a hard time saying no!)

But that's just my 2 cents

Thank you, well thought through priority order. Taking notes.