[ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record

[Pon13]

i have a feeling that we re close to this big upgrade 

[1714040275]

1714040275

[1714040275]

1714040275

[1714040275]

1714040275

[royal. Crypto]

The coin looks good, hope the team can make it bigger and stronger. Thanksgiving.

[royal. Crypto]

Is this the correct forum to ask about the riecoin.org website?
It needs some serious updating.
For example several of the exchanges listed are no longer functioning.
Several of the links do not work.
Some of the listed forums are long since closed.
Overall just needs a review and update.

[Snoofi]

ughhhh. Not another Hype-Coin. Besides a tweak to the algorithm there is (yet again) nothing of real value with this new coin. Wow you can find prime numbers. PrimeCoin does that. Problem is everyone is scratching and scraping to get on the next "Bitcoin" so any new coin that gets released everyone and their grandmother jumps on it.

Sure, people will make money once accepted into exchanges but after x amount of time this coin will be like all the rest. Just a few pennies in a sea of endless alt coins.

This is part of the problem. Week after week anyone with a basic programming and marketing knowledge can make the next hypecoin. There is no innovation here. You can find prime numbers? a little different way? whoop-de-do.

How do you expect your coin to get passed the hype-trade?

The 3 major players are as follows:

BTC
LTC
PrimeCoin

That is it. Ride the hype! Go for it! make some money! but for long term investors? Like myself? NO THANKS.

Good Luck with your coin though. Really.
These type of coins are really really irritating!

[Pon13]

ughhhh. Not another Hype-Coin. Besides a tweak to the algorithm there is (yet again) nothing of real value with this new coin. Wow you can find prime numbers. PrimeCoin does that. Problem is everyone is scratching and scraping to get on the next "Bitcoin" so any new coin that gets released everyone and their grandmother jumps on it.

Sure, people will make money once accepted into exchanges but after x amount of time this coin will be like all the rest. Just a few pennies in a sea of endless alt coins.

This is part of the problem. Week after week anyone with a basic programming and marketing knowledge can make the next hypecoin. There is no innovation here. You can find prime numbers? a little different way? whoop-de-do.

How do you expect your coin to get passed the hype-trade?

The 3 major players are as follows:

BTC
LTC
PrimeCoin

That is it. Ride the hype! Go for it! make some money! but for long term investors? Like myself? NO THANKS.

Good Luck with your coin though. Really.
These type of coins are really really irritating!

This coin is as old as primecoin. It hasnt involved in a pump n dump scheme like primecoin though.

[hopguide]

Yet another shit post, RIC is shit blah blah blah my post is super interesting

I call that déjà vu...

ughhhh. Not another Hype-Coin. Besides a tweak to the algorithm there is (yet again) nothing of real value with this new coin. Wow you can find prime numbers. PrimeCoin does that. Problem is everyone is scratching and scraping to get on the next "Bitcoin" so any new coin that gets released everyone and their grandmother jumps on it.

Sure, people will make money once accepted into exchanges but after x amount of time this coin will be like all the rest. Just a few pennies in a sea of endless alt coins.

This is part of the problem. Week after week anyone with a basic programming and marketing knowledge can make the next hypecoin. There is no innovation here. You can find prime numbers? a little different way? whoop-de-do.

How do you expect your coin to get passed the hype-trade?

The 3 major players are as follows:

BTC
LTC
PrimeCoin

That is it. Ride the hype! Go for it! make some money! but for long term investors? Like myself? NO THANKS.

Good Luck with your coin though. Really.
These type of coins are really really irritating!

Our developers do not need your stupid luck. Riecoin is a great investment for long term with more and more people working on the project every week.

In comparison, Litecoin is a pointless cryptocurrency with its now ASIC broken algorithm, Bitcoin is merely the frist one, and Primecoin is not more alive than Riecoin. Poloniex will regret delisting RIC.

Is this the correct forum to ask about the riecoin.org website?
It needs some serious updating.
For example several of the exchanges listed are no longer functioning.
Several of the links do not work.
Some of the listed forums are long since closed.
Overall just needs a review and update.

The official website is unfortunately obsolete and the founder is too lazy to update it. For now, you should only rely on the community posts. Be confident that someone will eventually create a new website that will replace riecoin.org, or that Gatra eventually gives the domain ownership to someone from the community.

[PttnMe]

For Bounty Hunters: I am now willing to donate 1000 RIC for the person who fixes this rieMiner issue elegantly. This offer will expire on October 8 2018 at 00:00 Zurich Timezone. It is currently about the price of one beer, but remember how much a pizza cost years ago... And who knows if this is just 2 lines to change, but I am currently too busy to look. After this deadline, the bounty will be reduced to 250 RIC and remain valid until the new wallet is officially updated, or until January 1 2019 at 00:00 Zurich Timezone if gatra never comes back.

Note that this bug is present since fastrie/xptMiner. Obviously, there must be no performance loss, you should benchmark before and after and compare before submitting the fix. And by elegantly, I mean, inter alia, a fix that is not just a workaround (you could for example compute 2 sieves and imitate the launching of 2 instances with less threads, but this is not worth any bounty).

The fix must also make Testnet mining work properly with any sieve size (in my 2700X, only about 25% of the CPU is used when mining at difficulty 304 using 16 threads!).

Registrations reopened at uBlock.it

Nice, I can now test your pool myself, thank you.

[clo1]

I've submitted the riecoin 0.16.3 code on the riecointeam page.

https://github.com/riecointeam/riecoin

I'll remove my original code soon. I did my best to replace all bitcoin/btc with riecoin/ric in the executable and gui but I probably missed a couple.

[clo1]

For Bounty Hunters: I am now willing to donate 1000 RIC for the person who fixes this rieMiner issue elegantly. This offer will expire on October 8 2018 at 00:00 Zurich Timezone. It is currently about the price of one beer, but remember how much a pizza cost years ago... And who knows if this is just 2 lines to change, but I am currently too busy to look. After this deadline, the bounty will be reduced to 250 RIC and remain valid until the new wallet is officially updated, or until January 1 2019 at 00:00 Zurich Timezone if gatra never comes back.

Note that this bug is present since fastrie/xptMiner. Obviously, there must be no performance loss, you should benchmark before and after and compare before submitting the fix. And by elegantly, I mean, inter alia, a fix that is not just a workaround (you could for example compute 2 sieves and imitate the launching of 2 instances with less threads, but this is not worth any bounty).

The fix must also make Testnet mining work properly with any sieve size (in my 2700X, only about 25% of the CPU is used when mining at difficulty 304 using 16 threads!).

A couple thoughts. This sounds like the sieve might not be providing enough work to keep all the threads busy checking primes. You could try increasing the number of sieveWorkers. SieveSize could also possibly play a role. Things like memory cache usage become important. I'm not sure about the 2700X architecture but it's possible that the sieve workers need to be not just in different threads but different cores or specific cores in order to optimize performance.

As difficulty decreases, the sieve must perform faster and faster. At some point the sieve will be memory bandwidth limited and it still will not be fast enough to keep the prime checks going at 100%. At this point the only way to increase total system performance is to decrease the number of primes in the sieve. It's possible that the testnet difficulty is at this point.

[clo1]

I assume https://github.com/clo-prime/riecoin-0.16 is the latest we have? But I got errors when "make". I use ubuntu 18.04

./bignum.h: In function ‘bool operator>(const CBigNum&, const CBigNum&)’:
./bignum.h:658:83: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
inline bool operator>(const CBigNum& a, const CBigNum& b) { return (BN_cmp(&a, &b) > 0); }
^
Makefile:5523: recipe for target 'libriecoin_server_a-blockencodings.o' failed

I found similar issue here: https://github.com/zcoinofficial/zcoin/ ... 00e585db3c

Seems to be compatibility with OpenSSL 1.1.0 and could be fixed by ~100 lines of change?

I think a android wallet is the most needed for ordinary users, maybe the next priority.

There was some discussion of this a couple pages back. I think PttnMe posted a work around of installing libssl1.0-dev.

There was also some discussion of replacing bignum with gmp but no conclusion. Maybe this is what I should work on next. It would probably only take a couple days.

[clo1]

We should start a list of additional testing that needs to be done on the 0.16.3 code.

For starters there are the softforks:
BIP65
BIP66
CSV - BIP68, BIP112, and BIP113
SegWit - BIP141, BIP143, and BIP147

What else?

Izknr - not sure if you've started on another project, but you can take on as much of this as you want.

[Che6ir61]

the position of the coin looks promising perhaps in the future it will enter the top 10 coins. The development team is very promising to do everything for development

[clo1]

The 0.16 code doesn't allow any transactions including mining if the most recent downloaded block is more than a day old. This is fine for mainnet but can be a problem on testnet if no one has mined a block to it in a while. RieMiner will be unable to connect. To get around this use the option -maxtipage=time_in_seconds, where time_in_seconds is larger than the time to the most recent block. Again, this is only needed for testnet.

[SpacExplorer]

any chance ric back again a market?

[xandry]

any chance ric back again a market?

He's on market - check https://zapple.com/exchange

[ziiip]

So are you guys running with ,inasne # of threads or only one thread per CPU??

It's best to align instances and threads to each NUMA node from my experience.

[IGJ]

Greetings,

To: PttnMe
Done some tests and here is what I found about the problem with many threads:
https://forum.riecoin-community.com/viewtopic.php?f=7&t=19

To: clo1
Couple of weeks ago made this patch:
http://download.riecoin-community.com/16.0/riecoind_16.0_openssl_1.1.patch.gz
At least the wallet can be compiled for openssl 1.1 or up. With it wallet can connect on testnet and all is fine but on mine net it have troubles, maybe I missed something. if you have time can check it. I will check it again but my time last weeks are very little.

To: Ziiip
Send you PM on community board.

Ziiip is right working miner instances should be as much as numa nodes in the systems are and locked to each numa node. You can do this with command taskset under linux. On muticore CPUs maybe better will be to run one instance for each core and lock the entire process to one core (taskset under linux).

[PttnMe]

Bounty deadline for the CPU Underuse bug fix extended to November 1 2018, 00:00 Zurich timezone and increased to 2000 RIC, and even 5000 RIC if more work is done! Read this post.

Remember that 5000 RIC was worth hundreds of $ before the crash, and could be much more in the future.

After the deadline, the reward will be reduced to 500 RIC (or 1250 for the complete rewriting) until January 1 2019 00:00 Zurich Timezone, or as soon as the new wallet is officially approved. So please someone try to fix the CPU underuse bug before November. I do not have the time to do this myself until a while.

[PttnMe]

clo1, is there any way to send Riecoins without paying any transaction fee like the 0.10.2 (if not, this would in another hand be nice to encourage people to mine, even though only a few hundreds gatras* is not much )?

Is it normal that I am not seeing incoming transactions (sent from another 0.10.2) with 0.16.3; I see them only when someone mined them?
Also, transactions sent using 0.16.3 seem not to be broadcasting. They appear in GetBlockTemplate, but not for another wallet. The text "broadcast though x nodes" is not appearing, it only says that it is in the MemPool.
I had to double-spend to get back some coins... I am pretty sure that I am connected to enough nodes...
I might try to mine one such transaction to see what happens. Especially one with the Replace By Fee activated.

* 1 gatra = 10^(-8) RIC, or we could also say 1 riemann too :p

Edit: transactions mined and broadcasted successfully in 966103.
3559bd615e38ec983e0cc1b688a73eed1f82cd3bc4a4a027a88b75229b74f899 used Replace By Fee, as you can see with the 4294967293 sequence value.

A transaction is considered to have opted in to allowing replacement of itself if any of its inputs have an nSequence number less than (0xffffffff - 1).

If nobody used 0.16.3 to send any transaction in the network before, this is the first transaction created by a Riecoin Core 0.16.3 and confirmed in the MainNet !
Now, am I the only one that have the transactions not broadcasting, using 0.16.3?

[IGJ]

Greetings,

...
To: clo1
Couple of weeks ago made this patch:
http://download.riecoin-community.com/16.0/riecoind_16.0_openssl_1.1.patch.gz
At least the wallet can be compiled for openssl 1.1 or up. With it wallet can connect on testnet and all is fine but on main net it have troubles, maybe I missed something. if you have time can check it. I will check it again but my time last weeks are very little.
...

For 16.3
http://download.riecoin-community.com/16.3/riecoind_16.3_openssl_1.1.patch.gz

Revisit the patch and tested , the wallet can be build with libssl 1.0 and libssl 1.1 or up , syncing on the network and seems to work.  Tested and build on Debian stable (9 - stretch) and Debian unstable (sid).