Topic: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record - page 15. (Read 685207 times)

Ah, so that is you.. can you do us a favour and remove your garbage issues from github?
I'm not sure who would be proud of that or even admit to it to be honest.. (https://github.com/gapcoin/gapcoin/issues/8)

To me its akin to pissing on a famous painting.


By that reasoning, since X11 contains eleven 512bit wide hashfunctions, it should be 11 times better than SHA512? lol

For Sha512 I posted this issue here........

https://github.com/gapcoin/gapcoin/issues/14

Summary............

Different hardware favors different functions. SHA-512 is generally faster on 64-bit processors, SHA-256 faster on 32-bit processors. (Try the command line command!  

openssl speed sha256 sha512

SHA-512 also has over SHA-256 collision resistance, a term that in cryptography has a very narrow meaning. SHA-256 claims 128-bit collision resistance, SHA-512 claims 256-bit. If or when a practical quantum computer is built, we will need the 256-bit collision resistance.

CLO1,

Works great so far, it compiled.  

Seems hard to find peers automatically

Is Riecoin still strong connections?

Wished I could have helped out Riecoin earlier but I did not like the structure of Riecoin long ago due to small pool size and no network, the blockchain shows it's signs.  Gapcoin is by far more distributed due to BitcoinFX and my own to decentralize it.  A couple groups/individuals have tried multiple attempts to break Gapcoin so I know if vigilance is not kept it will be lost for good the initiative on the side of the malicious actors.

 But I am onboard now If I can find some coin and power to throw at Riecoin...It keeps getting 1 connection than losing it so not sure how long I can ride this rodeo.......

Gapcoin has the Network and Riecoin has the Software Devs.......it is much easier for your team to come over here than for us to go over to you as the Riecoin Network is severely limited even though it produces good Math.  The Network is choking your growth and it is not your fault it is the malicious actors intent.  Just as their intent is to choke Gapcoin Development by handicapping the software development.

It seems we have a little choke point hopefully your team can make the right choice as you can't save two sinking ships at once. 

I can donate to each Dev in Gapcoins whatever they deem fair. 

I have burned over 1.1 million Gapcoins and randomly burn them all the time...........maybe when I get to burning 6 million I will strike gold?

The test units have not been updated and won't compile. To eliminate the errors you need to re-configure.

./configure --disable-tests
make

This should be fixed shortly, at least so that the test units compile.

Care to explain in detail what benefits (also how/why) we would get with Sha512?

People had problems compiling because they had OpenSsl 1.1 instead of 1.0.
As Trisquel seems to be based on Ubuntu, which is based on Debian, in which compilation works fine, I do not really know what is the issue. Maybe your distribution version is just too old?
You may have a bit more luck using my own Deb64 binary, though there will be some shared libraries dependencies.


So it was you who sent me these coins! Thank you a lot ! I will distribute some to Rockhawk as he also deserves a part of it (or you can do it yourself, RVSDWEaxH3gjEqgYVAvdaNunVq7zzDivwH)!
It warmed my heart to read your feedback, I am glad that you appreciate rieMiner 0.9!

Honestly, I find that the previous code was hard to work with and needed reorganization. I would personally have a lot of trouble to add cleanly Solo Mining and Benchmark Mode (and many of the new features) in the fastrie style. Also, only basic Oop concepts are used.

It is a "Vanity address", I used VanityGen+ to generate it.

And do not hesitate to join the Discord server (invite link) for more live discussions about Riecoin!

I have played a lot of games with Riecoins and 6-tuplets over the last five years, and when a new miner comes out, it certainly deserves to be tested. My initial experiences with rieMiner 0.9:

The binaries run without problems on both Intels and AMDs, using both Windows 7, 8 and 10 and Ubuntu 16.04. The source code compiles on my Ubuntu 16.04 -  without a hitch! Copy files, type make, and watch the build! Yes, I already had the prerequisite libraries and stuff.  And my compiled code runs just as well as pttn's binaries. I haven't tried a Windows build - yet.

On my Ryzen 1700, benchmarks show about 20% performance increase compared to fastrie. In actual mining, rieMiner 0.9 seems to do even better than that, although it is difficult to find equal circumstances for comparison.

Pttn and Rockhawk have done a great and thorough job rewriting the miner. For me, penetrating the new code will be a challenge, though. Personally, I prefer the procedural programming style of Jh00 and dga and get slightly nauseous whenever I meet double colons, namespaces, classes and suchlike.

But - disregard any negative thoughts from a grumpy oldtimer. Obviously, if someone completely rewrites, improves and restructures an existing system, he should be allowed to use whichever paradigm he prefers or finds necessary. Well done!

I usually don’t mine riecoins any more. It is probably cheaper to buy them than to mine them these days.  This Christmas however, as a small token of appreciation, I have fired up all the systems I have available (connecting to ublock.it) and have directed all the output to pttn's payout address:

RPttnMeDWkzjqqVp62SdG2ExtCor9w54EB

And folks, have a closer look at that address! I didn't know you could do that - Cool!

Merry Xmas to you all

vidarn

I am genuinely impressed here, to be honest though your group seems to be the engine for the 3 Math coin projects.  Primecoin tried pump and dump developers months back, and Gapcoin is good which I have learned to hack it together using Trisquel OS, it will break down soonish.

I am glad and did not expect to get such a favorable reply from your group.  

I am trying to spearhead the Sha512 working group for Gapcoin, if you guys want to port that to Riecoin that should gain the same benefits as well as Primecoin.  

We could Follow up Bitcoin to 0.17 Core except change the Algo from 32 bit Sha256 to 64 bit Sha512 for automatic speed up of the miners.  Which if I was a programmer that is exactly what I would look to change to leverage my work.  I am however just a normal person who has to rely on personal development and others to keep moving forward.  

Jonn9 is the only one with Write Access to Gapcoin as far as I know, so I don't want anyone to waste time except through the understanding a hard fork will likely be required.  Which is why I want to propose the hardfork is simultaneous as the Sha512 upgrade.




Ok, so I tried compiling Riecoin 16.3 I got a couple errors.  Maybe it is because I am using Boost 1.58 from Trisquel OS?

I will just post them here.............

key.cpp: In function ‘int ec_privkey_import_der(const secp256k1_context*, unsigned char*, const unsigned char*, size_t)’:
key.cpp:51:23: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (end - privkey < lenb) {
                       ^
key.cpp:57:23: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (end - privkey < len) {
                       ^
key.cpp:71:37: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (oslen > 32 || end - privkey < oslen) {


2)   

leveldb/util/logging.cc: In function ‘bool leveldb::ConsumeDecimalNumber(leveldb::Slice*, uint64_t*)’:
leveldb/util/logging.cc:58:40: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
           (v == kMaxUint64/10 && delta > kMaxUint64%10)) {
                                        ^
  CXX      leveldb/util/leveldb_libleveldb_a-options.o
  CXX      leveldb/util/leveldb_libleveldb_a-status.o
  CXX      leveldb/port/leveldb_libleveldb_a-port_posix.o
leveldb/port/port_posix.cc: In function ‘bool leveldb::port::HasAcceleratedCRC32C()’:
leveldb/port/port_posix.cc:60:15: warning: ‘ecx’ may be used uninitialized in this function [-Wmaybe-uninitialized]
   return (ecx & (1 << 20)) != 0;


3)

test/blockencodings_tests.cpp: In function ‘CBlock blockencodings_tests::BuildBlockTestCase()’:
test/blockencodings_tests.cpp:50:81: error: could not convert ‘(& Params())->CChainParams::GetConsensus()’ from ‘const Consensus::Params’ to ‘offsetType {aka arith_uint256}’
 CheckProofOfWork(block.GetHash(), block.nBits, Params().GetConsensus())) ++bloc
                                                                     ^
test/blockencodings_tests.cpp:50:94: error: ‘class CBlock’ has no member named ‘nNonce’
 fOfWork(block.GetHash(), block.nBits, Params().GetConsensus())) ++block.nNonce;
                                                                         ^
test/blockencodings_tests.cpp: In member function ‘void blockencodings_tests::EmptyBlockRoundTripTest::test_method()’:
test/blockencodings_tests.cpp:295:81: error: could not convert ‘(& Params())->CChainParams::GetConsensus()’ from ‘const Consensus::Params’ to ‘offsetType {aka arith_uint256}’
 CheckProofOfWork(block.GetHash(), block.nBits, Params().GetConsensus())) ++bloc
                                                                     ^
test/blockencodings_tests.cpp:295:94: error: ‘class CBlock’ has no member named ‘nNonce’
 fOfWork(block.GetHash(), block.nBits, Params().GetConsensus())) ++block.nNonce;
                                                                         ^
Makefile:8565: recipe for target 'test/test_test_riecoin-blockencodings_tests.o' failed

make[2]: *** [test/test_test_riecoin-blockencodings_tests.o] Error 1

make: *** [all-recursive] Error 1
  

You've been invited to riecointeam, probably the more that have access the less chance it ends up locked up when someone leaves. Clo1, myself, and (invited) riecoin/gatra are the current owners but you should be able to commit PR and open new repos (let me know if you run into any issues).

Personally I don't find much need to call something "official"... The only official Riecoin anything I recognize is the longest valid chain on the consensus rules that I've agreed to, currently that's Riecoin 10.2 (soon to be 0.16.3 authored by clo1 if miners agree to those tightened consensus rules). My personal bar for valid consensus rules are those that would be vetted by the community then supported by miners.

I am looking forward to seeing your contributions. Right now, a GPU miner is not that important, but it may at least attract people that prefer GPU mining. I just hope that GPU will not be too advantageous over CPU, so both can be used for the long term (in another hand, it should be efficient enough). Else, a new official website will be great; we will also need a nice domain name.
Thank you for your involvement.

Few years back, I have worked on GPU implemantation of xptMiner. But I didn't have enough time to finalize it.

I can start working on it again. But do we really need to have a GPU miner? We should decide this.

I will be honored to design the new official page of Riecoin.

I am starting to work on this project this weekend. We will see what I can do to help.

I created a Discord server (invite link). Maybe we could make the community even more solid this way, with instant messaging. Explanation of the channels.

For everyone involved in Riecoin, I would like that we use the community forum to organize much better the information, or use the Discord server. We should let this topic clean for general discussion (and to avoid posts like this one quoting a lot of people).


Is the riecointeam organization intended to be the official one? May I join it in this case?
Also, good initiative to save the Riecoin.org site, though there is plenty of outdated information there.


Thank you for your confirmation.

About the 0.17.0, as I do not have much time, I did not look that much for now. I however opened a topic to discuss about it. I think that there is no hurry for now, upgrading to 0.16.3 is already enough for a while and efforts would be better allocated in other fields until we find more interest in Riecoin: light/Android wallets, useful services using Riecoin, finalizing the 0.16.3, new official website, reaching new people... That said, we must never have a 4 years outdated wallet again; attracting new skilled developers will help a lot to catch up faster and efficiently the newer versions.


I compiled rieMiner in a Toshiba AC100 (Armhf CPU, Ubuntu 16.04) without any issue, so rieMiner should work in a Raspberry Pi with Linux. Note that you need to use the Light branch. Also be sure to read properly the README.md (in particular, 32 bits compilation instructions and reduce the PrimeTableLimit for less memory usage). If you need help, please post questions here.


Riecoin, Gapcoin and Primecoin should collaborate together to provide the best software and community support and promote these three useful projects to make people forget about useless things like Litecoin, Dogecoin or Bitcoin Cash.


Fair enough. Now, one quality of somebody wanting to invest seriously in the project is to be proactive and find by your own what is needed to do, what you can do, and do it. Read this topic's post history since the latest 20-30 pages and the community forum's posts. Here is a summary of what you can do :

- The miner is basically finished. There is not really anything we have to do with it right now as it is fairly satisfying now. But you can think about working on some features that may be useful for the future: adding a GUI to have the user friendliest miner in the crypto world; port to Android to potentially get some more miners (why not mine 1 RIC or so during the night with those mainstream 8 Cores phones, while charging). Or, if you are very knowledgeable in this field like Rockhawk, find ways to optimize even more the miner or think about a possible GPU implementation;
- Clo1 said regularly that the 0.16.3 version is basically done and just needs some soft forks testing (CSV, CLTV). Yet nobody seems to be interested to do this, you could be the one. Help him test these things so we can make this new version official faster.
- Else, you can look at the Bitcoin Core 0.17.0 release, see what changed from 0.16.3, and start working on it. As said above, I opened a topic for such work;
- Light wallets are welcome (including Android Wallets). You could look at some existing and good Bitcoin ones like Electrum and fork it for Riecoin. Or, you can also try to create one from scratch. Do some research about the Bitcoin Peer-to-Peer protocol and also look at the Riecoin code. Someone else is interested in working on a Android wallet, please contact lzknv in the community forum and collaborate with him. I already gave him some pointers.
- Or, instead of working on the wallet or the miner, you could be the one who will build the new Riecoin official website, though you did not say that you are experienced in HTML/CSS/PHP;
- You don't have to absolutely become a developer. We also need people to constantly reach new audiences and make them join Riecoin. Do you have relations with influential people that may be interested in and promote Riecoin? Or you could write articles about Riecoin if you have a blog, or make videos if you are a Youtuber.
- Also participate to debates and brainstorming: what do you think about Segwit, should we activate it and why? Discuss about some Riecoin improvement ideas. Brainstorm to find how we can spread the Riecoin usage, try to concretize some ideas.

If you are really an experienced programmer like you said, it should not be too hard to do at least one of these things, even if you never touched at any cryptocurrency related code, and some people of the community or myself can help you a bit. Now, it is your turn, good luck.


Thank you a lot for your support, we will sure contact you in case we need such services.
I think that 3 pools are enough for now. More 0.16.3 nodes would be very useful to ease the transition to this version.
A Testnet explorer (and node) will be useful for developers. There is only the IGJ's node right now (testnet.riecoin-community.com).

Also, speaking of nodes, we should start hard coding some in the 0.16.3 code to avoid having to edit the riecoin.conf. Anyone here running a reliable Riecoin node? You can announce yourself here.

If there's anything I can do to help - happy to do so.  Could host a second explorer and maybe look at a couple of public nodes if that would help.  Could run a pool if that's something that people are looking for but absolutely don't want to step on toes of anybody else already doing that.

Unfortunately I don't have time to commit to dev but if running some services is of help I can throw some infrastructure at it

clo1 and Pttn. I can't message you guys.

There is no way to be sure that someone will be reliable. This is a community and voluntary work.

I am not trying to earn money, or respect, or anything else. I just think that, I earned good money thanks to Riecoin (while Btc38 was around), I can payback some while sharing my time with the community.

That's all.

I will follow you, just lead me.

Yes but delisting is so common these days. There will be tons and tons of delistings over the course of the next few months.

Hi,
do you guys can make an estimation if the rieminer would/will work on RPi?
cheers

I've looked at Gapcoin. I even mined some a while back. They were recently delisted by Cryptopia. I could probably create a 0.16.3 version of the code. I'd be far more interested in doing that if others here also contributed. There are some possible issues with the coin that I would like to see addressed before doing any work on gapcoin.

Pttn, Thanks for taking the lead on this. I'm happy to be a developer.

Cryptapus, I'll take a look at the gitian code.

There is not much needed to finish the 0.16.3 code. I need to review the gitian changes. We need to set the blocks that BIP65 and BIP66 will become active. We need to decide if we would like the ability to activate segwit or csv. CLTV and CSV should probably be tested. There are a couple things that I added to the code for testing like getwork support that can be removed now.

More developers would be great. Aside from testing CSV and CLTV there probably isn't much to do until after 0.16.3 is released. You could start looking at changes needed in 0.17 code. There will be plenty to do in upgrading the algorithm which is really my biggest interest. We also need web developers.

I've taken the liberty of grabbing a snapshot of the current riecoin.org website in case it goes dark:

https://github.com/riecointeam/riecointeam.github.io

It can be viewed at https://riecointeam.github.io (looks like it will need some adjustments for https).

FWIW, whoever is in control of https://github.com/riecoin (assuming it's gatra) has been invited to join riecointeam as an owner.

Motivation is good, but how can I be sure that you will be reliable?
I could also say that I have 30+ years of experience in C++/Java/Lisp/Haskell/PHP/MySQL/... development...
It is your only one message in BitcoinTalk.

You must provide solid work for Riecoin and we must be sure that you will always be present for new work like upgrading Riecoin Core to 0.17.0 and later. Please contact clo1 and collaborate with him first to see what you can do for finalizing the 0.16.3 version.

To be clear, we do not want people only writing words without doing actual work in our team.
Also people with already some reputation here (in BitcoinTalk) are preferred.


You could open a Hindi topic like someone did in Russian, or in any common language, though translation are completely voluntary tasks and will not qualify you for the Community Manager role.
I cannot even control myself if the translation quality is good enough...

RESERVED for HINDI translation....

helloo admin.... can i translate ANN page / WHITE paper  to HINDI(INDIA) language ??

here is my portfolio.....
https://drive.google.com/drive/folders/1TTRWTdF-VC71_TgP4dcsy6wH4BoL9cxB

PM me if you need HINDI translation..... thank you....

Count me in too.

I am an experienced C, C++, Java and Pascal developer. I would like to be in the team.