News from the Riecoin Blockchain Explorer: - constellations text file being updated up to block 45000 in the next hours, with the highest constellations so far (diff 1724)
- extraction history charts have been added, you can access them from the extraction tab, f.i. here is UpCPU's
- added some visual feedback when a new block is extracted
Great news about the client update coming, is an RPC API to get the primes being included as well? That's the "plus" that sets Riecoin apart! Hey Fairglu, I know this isn't required, but could you set up a testnet for Riecoin? I'd like to use it for an Android wallet app I am trying to develop. |
|
|
|
Any chance of getting it to convert to CAD as well? Cavirtex is the primary reputable CAD$ exchange out there. Thanks! Hey, added conversion to CAD as well as other currencies. Used BitcoinAverage as the model. |
|
|
|
|
Btw Dev, can you add the google play links I posted on here on OP as well as the paper wallet/multisig generator?
|
|
|
|
News from the Riecoin Blockchain Explorer: - constellations text file being updated up to block 45000 in the next hours, with the highest constellations so far (diff 1724)
- extraction history charts have been added, you can access them from the extraction tab, f.i. here is UpCPU's
- added some visual feedback when a new block is extracted
Great news about the client update coming, is an RPC API to get the primes being included as well? That's the "plus" that sets Riecoin apart! Excellent news  |
|
|
|
I'd like to know how fast the new client will be compared to say...Litecoin? Slower or faster?
I'm answering before we leave the first page  It's a fair comparison because LTC has blocks each 2.5 mins as we do, but it's not fair because LTC's PoW is not "useful"..... Anyway the answer depends on the current RIC difficulty. The first sync will definitely be much faster in RIC and in LTC, because LTC has much more blocks, and it will be like that for some time. If RIC difficulty goes up by a big amount this may change. and we would need to look at some more aggressive optimization. Fair enough. Any progress on stratum? I think what we need more than anything right now is a fast client and more pools. |
|
|
|
|
I'd like to know how fast the new client will be compared to say...Litecoin? Slower or faster?
|
|
|
|
Remember, slow and steady wins the race here. |
|
|
|
|
Just wondering why Keccak feels the need to not respond and just (for now I assume) abandon this coin. How hard is it to just find one random person on here and pass the project to that person.
|
|
|
|
Any chance of getting it to convert to CAD as well? Cavirtex is the primary reputable CAD$ exchange out there. Thanks! This is possible. Give me some time. I am working on an android wallet for Riecoin right now. Just resolved a portion of the problem I came across and resting for today. Right on, if I knew Java I'd probably work on whipping it up myself. But I don't... and from what I understand, coding for Android can be an interesting experience. Really appreciate all the work you're putting into the foundation/community! What you can do to help us is donate to the foundation, spread news about Riecoin, or simply posts on here a couple of times a day |
|
|
|
|
Anyone know where in the code the public key is assigned? I know BTC is 0x00 for base 58. WHere is that assigned exactly?
|
|
|
|
Any chance of getting it to convert to CAD as well? Cavirtex is the primary reputable CAD$ exchange out there. Thanks! This is possible. Give me some time. I am working on an android wallet for Riecoin right now. Just resolved a portion of the problem I came across and resting for today. |
|
|
|
Please use "mvn clean install android:deploy" to deploy to your device. Or use ADB, as documented in the README.
I've given up on using the Eclipse "run" target for Android apps a long time ago...
Ok I fixed it! Thank you so much for your help! And you were right...Eclipse isn't really compatible with this wallet is it? This is the first time I've come across an app that can't be run by Eclipse. |
|
|
|
Oops, sorry, I forgot to push the release button. Now it should show up soon, hopefully.
Seems like you need to upload it on here too: http://search.maven.org/#browse%7C477229452Failure to find com.google:bitcoinj-parent:pom:0.11.2 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced |
|
|
|
|
Seems like what this coin needs now is active community
|
|
|
|
|
If you guys need a coin with active developers and good community, I would recommend Riecoin. Dev. is on there pretty much everyday and gives out updates once a week. I hold heavycoin too but bought in at .000006 so we will see what happens now.
|
|
|
|
|
Hey Gatra,
will the next client fix OpenSSL problem?
|
|
|
|
I've updated the optimized miner to b15. This version currently works only on Linux - I would greatly appreciate some help figuring out what I broke on windows/mingw! I've left the b14 binaries for both linux and windows online. Source and binaries are in the usual spots: ChangeLog: https://github.com/dave-andersen/fastrie/blob/master/ChangeLog Source: https://github.com/dave-andersen/fastrie Binaries: http://www.cs.cmu.edu/~dga/crypto/ric/The basic summary of the below: It uses a lot less memory and is about 15% faster on most platforms. Single-core machines will be unchanged, and on huge machines (64 core) you'll want to run multiple copies, one per processor slot, for best performance. But for most of us on single or dual CPU platforms with 4-24 cores, this should produce a nice speedup. As always, test for yourself. b15 (2013-04-26) - Major internal architectural overhaul. Sieving and primality testing are now divided among all threads instead of having each do a single operation. The current consequence of this is a good speedup on modest-core architectures while using substantially less memory. 4-16 core machines should be particularly happy with this upgrade. Sieves can now be up to -s 4100000000 (4 billion) in size, though this does not appear to be a particularly useful setting from a performance perspective. Single-core machines may suffer a 5-10% slowdown. If this is prohibitive, let me know, but for now I plan to let it stay that way. Very large, slow core machines (e.g., 64 core AMD) are running MUCH slower. Please either continue to use b14 or run multiple copies of the miner, one per physical CPU, using taskset. Windows users must use at least Vista (2006, NT 6.0) or later. XP and Windows Server 2003 are no longer supported. Excellent work and thanks for your contributions! |
|
|
|
|
Show Posts
