Topic: [ANN][XCN] Cryptonite | 1st mini-blockchain coin | M7 PoW | No Premine - page 160. (Read 578501 times)
July 31, 2014, 12:02:33 AM
Im looking to sell 1,000,000 Cryptonite's for 20(400% below market price) satoshi each. Yes I mined it with a GPU.
July 30, 2014, 11:57:34 PM
Diff too high, we need a pool now.
Yes, we need it.
Is it still a CPU coin?
Can you post your hardware details and hashrates for a comparison?
i5 3570 ~290Kh
I have 30 i5 CPU's and I find ZERO blocks for last 12 hours.
We need pool!
@djm34 where r u , we need u !I believe Devs are already mining with GPUs like no tomorrow.
We need pool , 120 e3v3 have one block in hour,is to hard.
July 30, 2014, 11:28:39 PM
Sorry about the website being down earlier folks, it should be working fine now.
July 30, 2014, 11:27:05 PM
Difficulty is adjusted based on average hash rate over many blocks. Instantaneous hash rate varies a lot. In the long term difficulty adjustment will do a good job a making sure average block rate is 1/minute. This means there will be times of too fast, and times of too slow to compensate. The hope is the slow adjustment will prevent lots of pool hopping since difficulty from one block to the next is never very much different.
July 30, 2014, 10:47:41 PM
Why net hashrate goes down but diff goes UP?
July 30, 2014, 09:25:06 PM
I believe Devs are already mining with GPUs like no tomorrow.
If this were the case CPU mining with EC2 would not be remotely profitable. It's clearly not the case...No, if few people are mining with GPU, CPU is still profitable.
Wouldn't take much to keep up appearances.
July 30, 2014, 08:36:39 PM
I believe Devs are already mining with GPUs like no tomorrow.
If this were the case CPU mining with EC2 would not be remotely profitable. It's clearly not the case...No, if few people are mining with GPU, CPU is still profitable.
July 30, 2014, 08:14:17 PM
Diff too high, we need a pool now.
Yes, we need it.
Is it still a CPU coin?
Can you post your hardware details and hashrates for a comparison?
i5 3570 ~290Kh
I have 30 i5 CPU's and I find ZERO blocks for last 12 hours.
We need pool!
@djm34 where r u , we need u !I believe Devs are already mining with GPUs like no tomorrow.
July 30, 2014, 08:09:35 PM
Binaries on http://gpile.it/mbc until DNS gets resolved You will also have to addnode seed.gpile.it because DNS for seed not working either.
THANK YOU! I will check it out
July 30, 2014, 08:00:38 PM
Binaries on http://gpile.it/mbc until DNS gets resolved You will also have to addnode seed.gpile.it because DNS for seed not working either.
July 30, 2014, 07:58:39 PM
It's not very hard to solo mine right now, you should be able to find a block every week on average with only 100 kh/s.
Where is the wallet and where are you all mining at?
Thank you very much. I shall wait
July 30, 2014, 07:48:41 PM
@ catia
1. 32-bit CPU can support up to 64 GB using PAE, so there is some space left for them.
1. 32-bit CPU can support up to 64 GB using PAE, so there is some space left for them.
It is not even clear why so much RAM would be needed. Is the blockchain stored in RAM? Isn't it supposed to be small anyway?
I would be surprised if this coin could not fit easily in 2 GB of RAM (standard limit on 32 bit Windows). Presently I see memory usage of under 100 MB (on Linux).
July 30, 2014, 07:44:51 PM
It's not very hard to solo mine right now, you should be able to find a block every week on average with only 100 kh/s.
Where is the wallet and where are you all mining at?
July 30, 2014, 07:39:52 PM
Waiting in line for this coin
July 30, 2014, 07:39:32 PM
Anyone mining with AMD CPU?
Please share hashrate results.
Please share hashrate results.
I am mining with AMD.
FX-6300@4,2 GH = 420 kH
Athlon II X2 B28 @ 3,4 GH = 150 kH
Athlon X2 4850e @ 2,5 GH = 90 kH
July 30, 2014, 07:36:06 PM
@ catia
1. 32-bit CPU can support up to 64 GB using PAE, so there is some space left for them.
2. Using a machine for wallet and mining is not really the same.
@ alicea
Compilation became resource hungry monster nowadays.
I've found it out compiling recently bitcoin-qt and digibytes.
Over a gigabyte of the output...
1. 32-bit CPU can support up to 64 GB using PAE, so there is some space left for them.
2. Using a machine for wallet and mining is not really the same.
@ alicea
Compilation became resource hungry monster nowadays.
I've found it out compiling recently bitcoin-qt and digibytes.
Over a gigabyte of the output...
July 30, 2014, 07:35:10 PM
we neea a pool now.
July 30, 2014, 07:34:48 PM
Anyone mining with AMD CPU?
Please share hashrate results.
Please share hashrate results.
July 30, 2014, 07:14:42 PM
Using your brain could really help.
The wallet after 3 hours of battle, started compiling. And has been compiling for 1.5 hours. I'm leaving it to compile, I'll see in the morning, but I'll see that it can't connect as some have written before.
Only the devs are making good business. Is this honest? I don't think.
The wallet after 3 hours of battle, started compiling. And has been compiling for 1.5 hours. I'm leaving it to compile, I'll see in the morning, but I'll see that it can't connect as some have written before.
Only the devs are making good business. Is this honest? I don't think.
I compile 4 builds on a core2duo in under an hour. Not sure why its taking you so long. Syncing is being handled. Node crawler finished just need to wait for bitfreak to wakeup to change the DNS. Not sure how devs are making good business. I spend all my time writing code, meanwhile a whole mess of people are mining it. No shortage of people here who can tell you how many thousands they mined. Not really sure what the point of that statement is anyways. If I felt like spending thousands of $ on amazon instances, are we as devs for some reason not allowed to mine? It's a free for all on proof of work afaik.
32bit builds i don't really understand. For now there is enough memory, in the future there won't be. If processor is really only 32bit capable, it is so slow an inefficient that mining is not an option with it. If you have some kind of build errors, go ahead and report them. I'm willing to fix it for 32bit support.
Edit: you can use seed.gpile.it until DNS is updated, then it won't work anymore
July 30, 2014, 07:04:20 PM
My bitcoin client is now attempting to connect to the folder .cryptonite.
The .bitcoin folder and it's content seems to be untouched.
Every alt would like to take the bitcoin place... but did this one manage it somehow?
In my computer did...
edit: succefully separated both coins by running bitcoin-qt with -datadir= parameter.
No damages. How did Cryptonite make bitcoin thinking his data dir is now .cryptonite?
The .bitcoin folder and it's content seems to be untouched.
Every alt would like to take the bitcoin place... but did this one manage it somehow?
In my computer did...
edit: succefully separated both coins by running bitcoin-qt with -datadir= parameter.
No damages. How did Cryptonite make bitcoin thinking his data dir is now .cryptonite?
Jump to: