diff. went from 8.07 to 22.22  Hashrate dropped to 140 Mh/s also. Only 5 blocks seen in the last hour! |
|
|
|
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  Do that and what you mined with your CPU will be worth nothing. I guess it's a race between exchange and GPU Incorrect. The value of your coin doesn't drop, but the % chance of you finding a block with your CPU will be lower. It'll just become more viable to GPU mine than to CPU mine. Difficulty will increase, it doesn't render the value of your coins lower... |
|
|
|
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. |
|
|
|
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 |
|
|
|
Draft for a development roadmap and focus areashttp://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 |
|
|
|
Any news on a block explorer?  |
|
|
|
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 |
|
|
|
Fuck, I don't have nearly enough hard disk space for that. Will work on it tomorrow!
Could you sent a snippet of the end of the debug.log file? You will probably find an error there, that gives valuable info. If it is possible for you to convert back to the old version in the meantime, do that. The old version didn't work for me either, It would get stuck on "Loading Bitcredit wallet" But this is the error in the debug log: 2015-04-20 05:25:13 init message: Loading bitcredit wallet... 2015-04-20 05:25:13 nFileVersion = 90110 2015-04-20 05:25:13 Keys: 101 plaintext, 0 encrypted, 101 w/ metadata, 101 total 2015-04-20 05:25:13 bitcredit wallet 99ms 2015-04-20 05:25:13 Bitcredit: ConnectTip() : No tmp db created, in fast forward state, claim tip is -335816 bitcoin blocks ahead 2015-04-20 05:25:13 ERROR: Bitcredit: Bitcoin block to check for claiming 0000000000000000000000000000000000000000000000000000000000000000 not found in bitcoin blockchain! 2015-04-20 05:25:13 ERROR: Bitcredit: ConnectTip() : ConnectBlock 000000005fc6f4b75a16b644bc1bd975ec71e7bdfab3144d84915d0efae490d2 failed 2015-04-20 05:25:13 *** Bitcredit: ConnectTip() : ConnectBlockHelper 000000005fc6f4b75a16b644bc1bd975ec71e7bdfab3144d84915d0efae490d2 failed 2015-04-20 05:25:17 init message: Loading bitcoin addresses... 2015-04-20 05:25:17 Loaded 0 addresses from bitcoin_peers.dat 1430224109568ms 2015-04-20 05:25:17 init message: Loading bitcredit addresses... 2015-04-20 05:25:17 Loaded 0 addresses from bitcredit_peers.dat 1430224109568ms 2015-04-20 05:25:18 Requesting shutdown 2015-04-20 05:25:18 Running Shutdown in thread 2015-04-20 05:25:18 Initialization result: 0 2015-04-20 05:25:18 Stopping thread 2015-04-20 05:25:18 Shutdown : In progress... 2015-04-20 05:25:18 StopNode() 2015-04-20 05:25:18 Bitcoin: Could not find claim coins tip best block in index 2015-04-20 05:25:18 Shutdown : done 2015-04-20 05:25:18 Shutdown finished 2015-04-20 05:25:18 Stopped thread |
|
|
|
|
Fuck, I don't have nearly enough hard disk space for that. Will work on it tomorrow!
|
|
|
|
Expecting this to go up... Bought in at 20k sats.  |
|
|
|
Very interesting idea for a coin, setting up my wallet and prepping my CPU for a nice hammering.  Right on Greydon. let me know when you are up and running and I'll send you over some CRE! Gonna take a while... I don't have enough disk space to use torrent method for syncing, so waiting hours for the client to sync! Progress: 2 Years 40 weeks to go..... |
|
|
|
Very interesting idea for a coin, setting up my wallet and prepping my CPU for a nice hammering. |
|
|
|
|
OP hasn't responded, this was definitely a troll. Nothing to see here.
|
|
|
|
I can get to the main antpool site but can't get logged into my account. I get a cloudflare error. Anybody else seeing that?
I'm able to log in fine, they've seem to have had a couple issues today and yesterday, maybe upgrading servers or DDOS  |
|
|
|
It would be pointless with a 64gb server. Maybe buy an antminer try your luck with it. Eve huge mining operations are taking losses right now with the current price of bit[Suspicious link removed]d luck Fuck mining, BTC at 230$USD... I'm gonna go ahead and pick me up some hefty cheap coin. |
|
|
|
|
so.... im just gonna go ahead and overclock mine. Batch 3, and have had no chips drop out yet. Testing my luck?
|
|
|
|
So I'm a newb when it comes to overclocking... I'm in canada so we have 120v outlets, what's the safest max I should overclock to? (Could, maybe not should)..
You shouldn't, the stock PSU can't even handle running stock. You should also consider installing a 240V outlet if you have a few miners. This information is incorrect. I have been able to overclock to 212.5 100% of the time with no issues whatsover on stock PSU running on 110V. Yielding about a 5.5% increase in hashrate. A majority of the units I have experience with, will overclock at 225M with no problems. Just make sure your ambient temp is cool enough to keep the S4 at sub 65C temps. If you can't keep temps cool enough you will start loosing chips and they'll show up with X or completely missing from the status. And I've had more than 1 PSU fail running at 200MHz. Hard to say who's right. At 225MHz and stock voltage, the entire miner (4 hash boards + controller + fans) draws exactly 120A DC from the PSU, and the PSU is rated for 120A. If it were a quality unit, there wouldn't be any problem running 225MHz on it, but it isn't. I'm convinced that all of the S4 PSUs will have died within 6 months max. If you're going to overclock with it, make sure you have a backup ready or you'll be pissed when your S4 is a temporary paperweight and you lose all the ground you made by running overclocked. Better yet, replace it now and have peace of mind. Replacement PSU's are pretty expensive... I thought the newer batches had better PSU's? Am I incorrect? |
|
|
|
But do we know if it affects payouts in these cases?
Easiest way would be to check your payouts... mine wasn't affected. |
|
|
|
|
Show Posts
