Or simply, he gets more money by mining with his kernels than selling them and mining because, in the latter case, the difficulty goes up to the point that the total profit is lower.
|
|
|
Could try to get into yobit good move...yobit is increasing from day to day... Greetz Steve I think they ask 0.1 BTC or something for inclusion.
|
|
|
I'm sure those following the thread can see that i had to re-arrange the plan a little, it now stands as :-
1) Blockchain 2) Proof of stake 3) Assets 4) Cross chain interaction 5) Data Acquisition 6) Kernel v1 7) Simulators 8 ) Self replication 9) Inter-AI communication 10 ) Reasoning and Explanation (let the Ai make decisions and tell us why it did (simple enough as this is mostly mathematics and probabilities)) 11) Network wide AI 12) Decentralized exchange (and internal interface for centralized exchanges)
Stages 1, 2 , 3, 5 are already complete.
I am working on stages 4, 6 , 9 and 11.
I guess i will have to update the doc to match my progress and changes.
This is quite exciting. I hope we can work together in some way in the future, so the project evolves faster.
|
|
|
and still sgminer opencl is faster for me, just checked SP2 speed, its 920Mhs on 2Ghs
Either you have a problem or sp-mod doesn't work as expected, because my miner does that speed at a much lower clock.
|
|
|
I didn't get even a single donation for the faster pascal solo miner (on which the sp-mod is based). I see that nothing changed in this front :-/
|
|
|
I prefer one wallet. Single backup, less hassle.
|
|
|
On Linux it doesn't freeze the system but it crashes, probably still some memory faults.
|
|
|
it is SHA256D it is not the same joblo.
SHA256D = double SHA256, like bitcoin but, in the case of pascal, with different block header.
|
|
|
Put "addnode=" before every IP and put all that into your cryptonite.conf file. Those two exchanges are both having wallet issues and promised to fix them. I tried to help them but wasn't enough.
|
|
|
Currently active nodes:
109.166.139.39 109.87.46.50 118.172.250.184 125.236.224.55 158.69.27.82 178.26.208.109 178.64.236.238 178.84.34.124 182.71.181.102 188.252.239.81 190.44.84.248 193.106.171.8 195.93.239.31 203.206.220.48 211.149.194.156 217.21.17.182 24.246.60.145 27.45.58.187 41.199.120.82 46.105.118.15 62.75.241.240 68.193.116.54 77.111.163.71 82.116.52.170 85.11.137.70 85.14.250.2 87.100.207.156 91.152.120.234 95.28.242.232
|
|
|
I haven't found any CPU mining code for pascal yet. It's unusual that a coindwould include a GPU miner in its wallet but no CPU miner. The lack of a CPU miner also explains the problems with CPU verification in the GPU miner. The CPU verification code is basically a CPU miner. If anything drops in my lap I'll look at integrating it in cpuminer-opt.
OK but it's SHA256D like bitcoin, just a little modification to the block header. Very hard anyone would ever mine it with cpu (except on coin launch). They are already mining it with FPGA.
|
|
|
I had no issues syncing so far using the standard wallet on win7 x64. I did download a snapshot, though.
On my Ubuntu & Debian PCs, it worked without a snapshot, syncing completely fine.
Did you ever experience wallet corruption? Whoever had that issue, could you describe when that happens and what appears to trigger it? For example restarting the wallet or sending a transaction.
|
|
|
They say they changed it to bitcoin PoW, anyone tried their pool? Is it really mining the new coin or bitcoin instead? :-)
|
|
|
Updated blockchain snapshot: https://mega.nz/#!gAJ3TJqC!T-38y7DrWvRXmwpPpoL6RjM3DziYmXEhJamIt-v32V8 To use it: close the wallet, wait some seconds, put the files in the archive into your cryptonite folder (where wallet.dat is located).
|
|
|
SHA256D should mean "double sha256", exactly what bitcoin uses. Could the devs please clarify what's the difference? If it's just how the block header is setup, it may be possible for ASICs to be adapted.
|
|
|
It would be nice if the list of supported coins is stored on the main chain and grows as soon as (advanced) users add new chains and verify it's working.
|
|
|
If you increase npt, it will likely overflow the nonce range.
The original source had a limit on the nonce range of 2^20 With your block config. npt of 16 should be the maximum possible value. 8192*8*16=2^20 But not sure. I seem to get less solutions with npt=16 than npt=1 You forgot to multiply by the block size...
|
|
|
Thanks. 8% Faster than mine with 2 threads on the 1070. I get 970 vs 900 I am running a test now and compare the klaus_t kernel with the same input data as yours. edit: compiled with cuda52 instead of 61 I get 1050 edit: With npt=16 gives 1100 If you increase npt, it will likely overflow the nonce range.
|
|
|
It all look very interesting. And geany is a cool editor, I use it all the time :-)
|
|
|
why XCN deposit is off in btc38?
They are fixing it.
|
|
|
|