[ANN] CureCoin 2.0 is live - Mandatory Update is available now - DEC 2018

[AndreyNag]

Hi guys.
Please tell me why do not mining curecoin on my mpos pool? For a few hours working miners.  Even shows that are found blocks, but pool and blockchain not displayed. Are there any thoughts on this? Is it curecoin features? 
UniversalCurrencurrency (UNIT) are mining perfectly at the same pool. Block of UNIT is every few minutes.
My pool happy.mine.nu.
Wellcome.

[1713964134]

1713964134

[1713964134]

1713964134

[1713964134]

1713964134

[1713964134]

1713964134

[giodelgado]

Hello everyone, just submitted the curecoin project to Product Hunt, vote up to reach the frontpage!

https://www.producthunt.com/posts/curecoin

[AndreyNag]

Hi guys.
Please tell me why do not mining curecoin on my mpos pool? For a few hours working miners.  Even shows that are found blocks, but pool and blockchain not displayed. Are there any thoughts on this? Is it curecoin features? 
UniversalCurrencurrency (UNIT) are mining perfectly at the same pool. Block of UNIT is every few minutes.
My pool happy.mine.nu.
Wellcome.

Hi. And again the miner has found a block, and a pool of absolute silence. How to understand this?
Address is valid. Whats wrong?
Thats end of currently daemon log:

Code:

Flushing wallet.dat
Flushed wallet.dat 3ms
ThreadRPCServer method=getaccount
Flushed 13069 addresses to peers.dat  26ms
Flushed 13069 addresses to peers.dat  19ms
Flushed 13069 addresses to peers.dat  27ms
ThreadRPCServer method=listaccounts
ThreadRPCServer method=help
Flushed 13069 addresses to peers.dat  18ms
ThreadRPCServer method=getaccountaddres
ThreadRPCServer method=getaccountaddress
ThreadRPCServer method=getbalance
ThreadRPCServer method=listtransactions
Flushed 13069 addresses to peers.dat  24ms
ThreadRPCServer method=listunspent
Flushed 13069 addresses to peers.dat  25ms
ThreadRPCServer method=listaccounts
ThreadRPCServer method=getaccount
Flushed 13069 addresses to peers.dat  26ms
ThreadRPCServer method=validateaddress
Flushed 13069 addresses to peers.dat  29ms
ResendWalletTransactions()
Flushed 13069 addresses to peers.dat  21ms
received block c93de993d50fe1924010
SetBestChain: new best=c93de993d50fe1924010  height=157274  trust=1249756869570318  date=02/12/17 12:48:04,block hash= c93de993d50fe19240101c0ceb51de83c07587c49d575e23475d6fdacfb14b94
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 4ms
getblocks -1 to 00000000000000000000 limit 500
Flushed 13069 addresses to peers.dat  23ms
Flushed 13069 addresses to peers.dat  25ms
received block 8328dab0114026a646d4
SetBestChain: new best=8328dab0114026a646d4  height=157275  trust=1249774582838834  date=02/12/17 12:51:57,block hash= 8328dab0114026a646d40b5addd884c636c5034d5082073eb1eb29f1604b5a03
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 4ms
Flushed 13069 addresses to peers.dat  25ms
ThreadRPCServer method=getaccount
Flushed 13069 addresses to peers.dat  26ms
Flushed 13069 addresses to peers.dat  30ms
Flushed 13069 addresses to peers.dat  29ms
Flushed 13069 addresses to peers.dat  27ms
Flushed 13069 addresses to peers.dat  25ms
Flushed 13069 addresses to peers.dat  17ms
ThreadRPCServer method=getaccount
Flushed 13069 addresses to peers.dat  21ms
Flushed 13069 addresses to peers.dat  30ms
Flushed 13069 addresses to peers.dat  28ms
Flushed 13069 addresses to peers.dat  24ms

This is part of stratum log:

Code:

[36m[2017-02-12 16:02:01.732] [DEBUG] [default] - .[39mPool curecoin Thread 4 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:02.301] [DEBUG] [default] - .[39mPool curecoin Thread 3 Share accepted at diff 5638.35269304/14003.59961394 by BA9b77g4jde11gyRuqFswQ6KMKnvexxxxx [85.xx.xx.xx]
[36m[2017-02-12 16:02:03.355] [DEBUG] [default] - .[39mPool curecoin Thread 3 Share accepted at diff 17779.63144279/26633.34940914 by BA9b77g4jde11gyRuqFswQ6KMKnvezAi8R [85.173.186.233]
[36m[2017-02-12 16:02:03.992] [DEBUG] [default] - .[39mPool curecoin Thread 3 Share accepted at diff 5638.35269304/24750.81775761 by BA9b77g4jde11gyRuqFswQ6KMKnvexxxxx [85.xx.xx.xx]
[36m[2017-02-12 16:02:05.440] [DEBUG] [default] - .[39mPool curecoin Thread 3 Share accepted at diff 65536/66265.17037326 by BA9b77g4jde11gyRuqFswQ6KMKnvexxxxx [85.xx.xx.xx]
[36m[2017-02-12 16:02:10.927] [DEBUG] [default] - .[39mPool curecoin Thread 3 Share accepted at diff 5638.35269304/1093627.71313199 by BA9b77g4jde11gyRuqFswQ6KMKnvexxxxx [85.xx.xx.xx]
[36m[2017-02-12 16:02:19.339] [DEBUG] [default] - .[39mPool curecoin Thread 3 Share accepted at diff 5638.35269304/8400.65877858 by BA9b77g4jde11gyRuqFswQ6KMKnvexxxxx [85.xx.xx.xx]
[36m[2017-02-12 16:02:25.146] [DEBUG] [default] - .[39mPool curecoin Thread 3 Share accepted at diff 17779.63144279/25703.82246876 by BA9b77g4jde11gyRuqFswQ6KMKnvezAi8R [85.173.186.233]
[36m[2017-02-12 16:02:31.934] [DEBUG] [default] - .[39mPool curecoin Thread 3 Share accepted at diff 5638.35269304/20323.38162236 by BA9b77g4jde11gyRuqFswQ6KMKnvexxxxx [85.xx.xx.xx]
[36m[2017-02-12 16:02:37.374] [DEBUG] [default] - .[39mPool curecoin Thread 3 Share accepted at diff 5638.35269304/10059.75107718 by BA9b77g4jde11gyRuqFswQ6KMKnvexxxxx [85.xx.xx.xx]
[36m[2017-02-12 16:02:37.674] [DEBUG] [default] - .[39mPool curecoin Thread 3 Share accepted at diff 5638.35269304/12255.86013613 by BA9b77g4jde11gyRuqFswQ6KMKnvexxxxx [85.xx.xx.xx]
[36m[2017-02-12 16:02:37.805] [DEBUG] [default] - .[39mPool namecoin Thread 4 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:37.815] [DEBUG] [default] - .[39mPool namecoin Thread 1 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:37.816] [DEBUG] [default] - .[39mPool namecoin Thread 2 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:37.871] [DEBUG] [default] - .[39mPool namecoin Thread 3 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:38.167] [DEBUG] [default] - .[39mPool curecoin Thread 3 Share accepted at diff 5638.35269304/5724.35148776 by BA9b77g4jde11gyRuqFswQ6KMKnvexxxxx [85.xx.xx.xx]
[36m[2017-02-12 16:02:39.745] [DEBUG] [default] - .[39mPool curecoin Thread 3 Share accepted at diff 5638.35269304/10011.50360333 by BA9b77g4jde11gyRuqFswQ6KMKnvexxxxx [85.xx.xx.xx]
[36m[2017-02-12 16:02:41.965] [DEBUG] [default] - .[39mPool emercoin Thread 1 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:41.968] [DEBUG] [default] - .[39mPool emercoin Thread 3 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:41.973] [DEBUG] [default] - .[39mPool emercoin Thread 4 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:42.034] [DEBUG] [default] - .[39mPool emercoin Thread 2 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:44.505] [DEBUG] [default] - .[39mPool curecoin Thread 3 Share accepted at diff 5638.35269304/34291.76253007 by BA9b77g4jde11gyRuqFswQ6KMKnvexxxxx [85.xx.xx.xx]
[36m[2017-02-12 16:02:45.880] [DEBUG] [default] - .[39mPool bitcoin Thread 2 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:45.970] [DEBUG] [default] - .[39mPool bitcoin Thread 3 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:46.018] [DEBUG] [default] - .[39mPool bitcoin Thread 1 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:46.108] [DEBUG] [default] - .[39mPool bitcoin Thread 4 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:51.711] [DEBUG] [default] - .[39mPool universal currency Thread 3 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:52.434] [DEBUG] [default] - .[39mPool universal currency Thread 1 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:52.438] [DEBUG] [default] - .[39mPool universal currency Thread 4 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:52.450] [DEBUG] [default] - .[39mPool universal currency Thread 2 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:56.688] [DEBUG] [default] - .[39mPool curecoin Thread 2 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:56.689] [DEBUG] [default] - .[39mPool curecoin Thread 3 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:56.692] [DEBUG] [default] - .[39mPool curecoin Thread 1 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:02:56.692] [DEBUG] [default] - .[39mPool curecoin Thread 3 Difficulty update to diff 42130.28571429 workerName="BA9b77g4jde11gyRuqFswQ6KMKnvezAi8R"
[36m[2017-02-12 16:02:56.733] [DEBUG] [default] - .[39mPool curecoin Thread 4 No new blocks for 55 seconds - updating transactions & rebroadcasting work
[36m[2017-02-12 16:03:03.800] [DEBUG] [default] - .[39mPool curecoin Thread 3 Share accepted at diff 5638.35269304/8128.05731749 by BA9b77g4jde11gyRuqFswQ6KMKnvexxxxx [85.xx.xx.xx]
[36m[2017-02-12 16:03:04.704] [DEBUG] [default] - .[39mPool universal currency Thread 2 getting block notification via RPC polling
[36m[2017-02-12 16:03:04.705] [DEBUG] [default] - .[39mPool universal currency Thread 1 getting block notification via RPC polling
[36m[2017-02-12 16:03:04.707] [DEBUG] [default] - .[39mPool universal currency Thread 4 getting block notification via RPC polling
[36m[2017-02-12 16:03:04.722] [DEBUG] [default] - .[39mPool universal currency Thread 3 getting block notification via RPC polling

[ComputerGenie]

...
Address is valid. Whats wrong?
Thats end of currently daemon log:...

Other than your miner screenshot, there's nothing in what you've shown that shows that you've found a block or if you did, when.

ProcessBlock: ACCEPTED

means that the CureCoin client has accepted the information it was sent about a block being found on the network. You will also see this in the log for every block.


Edit: as for tracking down your issue of you not seeing information about CureCoin blocks, a 1 minute long multi-mining stratum log, from some random point in time, isn't enough information to give you any accurate advice.

[AndreyNag]

Edit: as for tracking down your issue of you not seeing information about CureCoin blocks, a 1 minute long multi-mining stratum log, from some random point in time, isn't enough information to give you any accurate advice.

Here you are. It`s logs from unomp and curecoin daemon.
https://yadi.sk/d/ve7JD9H33DwYG3
https://yadi.sk/d/KzxplFNZ3DwYGB
Thank you for attention.

[ComputerGenie]

Here you are. It`s logs from unomp and curecoin daemon.
...
Thank you for attention.

[36m[2017-02-12 14:45:31.988] [DEBUG] [default] - [39mPool curecoin Thread 2 rpc error with daemon instance 0 when submitting block with submitblock {"code":-22,"message":"Block decode failed"}

The short answer is that your stratum is not set up properly to work for either CureCoin or PeerCoin.
The long answer (which is not within the scope of this type of forum) is that you'd have to understand the code behind stratum to fix it (as it involves coding edits where stratum submits the block info).

[AndreyNag]

[36m[2017-02-12 14:45:31.988] [DEBUG] [default] - [39mPool curecoin Thread 2 rpc error with daemon instance 0 when submitting block with submitblock {"code":-22,"message":"Block decode failed"}

The short answer is that your stratum is not set up properly to work for either CureCoin or PeerCoin.
The long answer (which is not within the scope of this type of forum) is that you'd have to understand the code behind stratum to fix it (as it involves coding edits where stratum submits the block info).

Please answer me shortly. What can i do wrong if just download from github unomp, source-code curecoin daemon and compile it by manual? Why universal currency are mining properly with the same pool settings?
How i can get more information for debugging?
Thank you.

This is i'm found in the merged-pooler/lib/pool.js
Am i right? Whats wrong here?

Code:

    /*
    Coin daemons either use submitblock or getblocktemplate for submitting new blocks
     */
    function SubmitBlock(blockHex, finishedCallback){

        var rpcCommand, rpcArgs;
        if (options.hasSubmitMethod){
            rpcCommand = 'submitblock';
            rpcArgs = [blockHex];
        }
        else{
            rpcCommand = 'getblocktemplate';
            rpcArgs = [{'mode': 'submit', 'data': blockHex}];
        }


        _this.daemon.cmd(rpcCommand,
            rpcArgs,
            function(results){
                for (var i = 0; i < results.length; i++){
                    var result = results[i];
                    if (result.error) {
                        emitErrorLog('rpc error with daemon instance ' +
                                result.instance.index + ' when submitting block with ' + rpcCommand + ' ' +
                                JSON.stringify(result.error)
                        );
                        return;
                    }
                    else if (result.response === 'rejected') {
                        emitErrorLog('Daemon instance ' + result.instance.index + ' rejected a supposedly valid block');
                        return;
                    }
                }
                emitLog('Submitted Block using ' + rpcCommand + ' successfully to daemon instance(s)');
                finishedCallback();
            }
        );

    }

[yavuzc78]

Maybe you didnt download %100 of blocks

[AndreyNag]

Maybe you didnt download %100 of blocks

No. Blockchain was full downloaded.

Flushed 13091 addresses to peers.dat  21ms
Flushed 13091 addresses to peers.dat  24ms
Flushed 13091 addresses to peers.dat  23ms
Flushed 13091 addresses to peers.dat  33ms
ResendWalletTransactions()
Flushed 13091 addresses to peers.dat  27ms
received block 81d4bf4d073a4805212b
SetBestChain: new best=81d4bf4d073a4805212b  height=157327  trust=1250672134659373  date=02/12/17 19:02:25,block hash= 81d4bf4d073a4805212b8c68bd7ca2a9e06880ba0445b4e21a3eeaeb13cdb9ed
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 3ms
Flushed 13091 addresses to peers.dat  29ms
CTxMemPool::accept() : accepted 8f42a16ef0 (poolsz 1)
ThreadRPCServer method=getaccount
Flushed 13091 addresses to peers.dat  30ms
received block 7914baea094338fdce3d
SetBestChain: new best=7914baea094338fdce3d  height=157328  trust=1250695136214898  date=02/12/17 19:04:21,block hash= 7914baea094338fdce3dfecebd5ebbbf5fedc3063dea5bc76dfce6ada335ee07
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 3ms
getblocks -1 to 00000000000000000000 limit 500
CTxMemPool::accept() : accepted 482e251ab0 (poolsz 1)
Flushed 13091 addresses to peers.dat  29ms
received block 32626301d8ff4c24d314
SetBestChain: new best=32626301d8ff4c24d314  height=157329  trust=1250719724542538  date=02/12/17 19:06:42,block hash= 32626301d8ff4c24d31454dd8c95bbb30ceaee95c96736b58651f428ce569b7d
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 3ms
received block 83a6335ca9cfc2db8747
SetBestChain: new best=83a6335ca9cfc2db8747  height=157330  trust=1250745915779861  date=02/12/17 19:06:52,block hash= 83a6335ca9cfc2db87479df6632e03f0487af33a765b17a64aade83feec59ddd
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 4ms
getblocks 157330 to 00000000000000000000 limit 500
CTxMemPool::accept() : accepted 9a6c2fdad4 (poolsz 1)
Flushed 13091 addresses to peers.dat  27ms
received block 692531ff622ca93518cd
SetBestChain: new best=692531ff622ca93518cd  height=157331  trust=1250774343322137  date=02/12/17 19:08:44,block hash= 692531ff622ca93518cd376143669f2d54a026232791a14112161419ca0069fe
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 4ms

[ComputerGenie]

Off the top of my head, the getblocktemplate has to be [] (without args) and there's some other settings that need changed/set. As I said, it's not a "simple" fix.

[AndreyNag]

Thank you for your attention.
I understand that it is difficult to alter unomp under curecoin.
Tell me please, are there any other platforms that no improvements will be compatible with curecoin?
For Example CoiniumServ?

[fred96002001]

i need some help with this folding.

i got the account set up and it said

1,534 go to Team Curecoin's total of 74,137,172,960
it has been 3 days and i do not see credits in my account at cryptobullionpools i was told the team # is Team 224497 and i set up a user name at cryptobullionpools. i have the  folding@home client set up with the same info but i do not see any credits or ppd at cryptobullionpools.  how do i fix this? or should i jsut wait more time. it has been 3 days now.

[ComputerGenie]

https://www.cryptobullionpools.com/support

[cygnusxi]

https://www.cryptobullionpools.com/support

FifthGhostBuster can be found often in our slack or irc, we are moving over to slack currently. The curecoin.net/forum is a much better spot to get a quick response from one of the team members. I do have someone that watches the facebook and twitter accounts quite actively also. The large single thread here is tricky for support issues.

Join link for our slack http://slack.curecoin.net:30000

As to a previous comment yes it gets pretty tricky to catch up on posts here. Since most of the last 5 pages is talk about PPD I have a few items to share

1- I have a 1070 evga hybrid getting 750k ppd solid under ubuntu 16.04 headless
2- I have a couple 1080 evga hybrids that bounce wildly from 800k to 1.2 million PPD on a similar setup.
3- I finally messed with the setup enough to be able to control fan and clock speed on a headless system and plan on seeing if the 1080s will fold stable at the same clock as the 1070 (its a pretty big difference in default clock on those 2 cards)
4- It could be argued in high electric cost the 1080 is better, but I think it needs a little tweaking
5- Ive spent way too much time rebuilding my folding machines looking for the best builds. In summary, use linux, its much faster.
6- The linux install guide on foldingcoin.net is pretty good, I was referring to it as a baseline build until I started to use 16.04, I will share my findings in an easy copy paste format to make it easier for others to crank out every last bit off PPD possible without crude tactics like a large overclock which can cause your folding to fail.
7- Folding is simple at face value, rather easy to get going. Fine tuning though can be turned into a career. Brands, ambient temps, drivers etc etc etc all make a big difference. I think we have a lot more research to do before we can officially crown the 1070 or the 1080 the king of folding.

[kopija]

https://www.cryptobullionpools.com/support

7- Folding is simple at face value, rather easy to get going. Fine tuning though can be turned into a career. Brands, ambient temps, drivers etc etc etc all make a big difference. I think we have a lot more research to do before we can officially crown the 1070 or the 1080 the king of folding.

Thanks, looking forward to Linux folding insights.
16.04 is the way to go since graphics-drivers ppa works only on that version and is also the way to go for gpu driver installation.
Headless system is PITA on Linux, but at least it works. On Windows one needs a dummy plugs to make it work.
Regarding PPDs, Watts and $: 1070 and 1060 3G are definitely folding kings while PPD/$ King is: (surprise, surprise) used/refurbished GTX 970 at 200$.
https://docs.google.com/spreadsheets/d/1v5gXral3BcFOoXs5n1M6l_Uo3pZpQYogn6gVlxRPnz0/edit#gid=0
Cant wait to buy a couple of used 1070s when they drop to something reasonable like 250$.

[ComputerGenie]

...
Regarding PPDs, Watts and $: 1070 and 1060 3G are definitely folding kings while PPD/$ King is: (surprise, surprise) used/refurbished GTX 970 at 200$.
...
Cant wait to buy a couple of used 1070s when they drop to something reasonable like 250$.

As I've said before, and I'll repeat until people actually read the words, you're using something for a base that has less than a single day of data for one 1080.
17 WUs in nowhere near enough data to make an informed opinion.

[huffnpuff]

SigmaX/CureCoin 2.0.0b3 beta schedule announcement (plan of record 02/16/17).

Vorksholk has submitted a new SigmaX build to CureCoin's internal beta team with updated features* (below)


Approximate Timeframe

1. Begin private testnet on 02/16/17 for a duration of ~two weeks (accessible by core beta team only)
2. Analysis and debugging phase for ~two weeks
3. Announce preliminary results (go to step 4, OR begin new internal testnet with new bug fixes - consider expanding internal beta test team).
4. Begin public testnet for ~one month IF build is ready
5. Final debugging and analysis phase for ~two weeks  
6. Announce results from public testnet (how many blocks mined, number of transactions, etc).      
7. Set official GA date, or go back thru step 4 for further refinement.

* updated features - compared to previous SigmaX beta versions:

   1. Now Using a hash-based radix tree for storing balance
   2. Expanded RPC functionality (enough to make a basic block explorer or exchange)
   3. Various networking code fixes (better peer discovery is a work in progress based on testnet results)
   4. Miscellaneous smaller changes
      Block header format is easier to work with and includes more data
      PoW now includes ledger hash
      Fixes for signature index ordering/recall in the mempool to handle multiple transactions from one address at a time

The CureCoin team reserves the right to modify schedules and beta release versions as required.

[ComputerGenie]

....

So, in short, what you're saying is I'm going to have to recode my pool?
 

[ComputerGenie]

....
3. CureCoin will be moving closer to pure POS asap in prep for CureCoin 2.0
....

Well, at least I know in advance to pull the plug on my $15k investment. :/

[bardacuda]

I knew I should have bought those nvidia cards back in the fall...

Great news about Stanford wanting to integrate!