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

[gavrilo77]

Any advice how many RIC can be mined with 1700x and 1950x? Which wallet to be used 0.10 or 0.16?

I am mining ~80 RIC/day at Difficulty 1386 with a 2700X @ 3,5 GHz. Earnings are proportional to frequency and number of cores for a same architecture so you can estimate yourself for 1950X.

For personal use, you can already start using 0.16.3, just backup your private keys to be safe.

A first bêta release is planned for soon and starting from this, upgrade can reasonably be considered safe for most people.

Is it pool mining? and rieminer 0.9?

[1714140885]

1714140885

[1714140885]

1714140885

[1714140885]

1714140885

[1714140885]

1714140885

[gavrilo77]

Any advice how many RIC can be mined with 1700x and 1950x? Which wallet to be used 0.10 or 0.16?

I am mining ~80 RIC/day at Difficulty 1386 with a 2700X @ 3,5 GHz. Earnings are proportional to frequency and number of cores for a same architecture so you can estimate yourself for 1950X.

For personal use, you can already start using 0.16.3, just backup your private keys to be safe.

A first bêta release is planned for soon and starting from this, upgrade can reasonably be considered safe for most people.

Is it pool mining? and rieminer 0.9?

Found first block with 1700x after 4 years with rieminer 0.9

[PttnMe]

Is it pool mining? and rieminer 0.9?

Solo mining with rieMiner 0.9, though you should earn roughly the same for both pooled and solo.

Found first block with 1700x after 4 years with rieminer 0.9

Congratulations for the block ! Thank you for participating, keep supporting the Riecoin network!

[gavrilo77]

Is it pool mining? and rieminer 0.9?

Solo mining with rieMiner 0.9, though you should earn roughly the same for both pooled and solo.

Found first block with 1700x after 4 years with rieminer 0.9

Congratulations for the block ! Thank you for participating, keep supporting the Riecoin network!

Good all times when i mined a lot with Azure

[lzknr]

May we have some instructions for how to signal BIP's? I am mining solo and wish to vote.

[cryptapus]

May we have some instructions for how to signal BIP's? I am mining solo and wish to vote.

If PR6 is merged testing will be appreciated:

https://github.com/riecointeam/riecoin/pull/6

Or feel free to merge locally and fire away 

[clo1]

May we have some instructions for how to signal BIP's? I am mining solo and wish to vote.

support for BIPs is indicated through the block version number. If you use rieMiner support should automatically be given.

[dautay_crypto]

May we have some instructions for how to signal BIP's? I am mining solo and wish to vote.

If PR6 is merged testing will be appreciated:

https://github.com/riecointeam/riecoin/pull/6

Or feel free to merge locally and fire away 

When the merged testing process finished?
I wish all the best results for the merged testing.

[cryptapus]

May we have some instructions for how to signal BIP's? I am mining solo and wish to vote.

If PR6 is merged testing will be appreciated:

https://github.com/riecointeam/riecoin/pull/6

Or feel free to merge locally and fire away 

When the merged testing process finished?
I wish all the best results for the merged testing.

Merged today... so I don't see anything waiting for a rc0 release. If there are any miners that want to try pulling from the master branch and confirming you can mine some blocks feedback would be most welcome (block number would be excellent).

Will probably tag a rc0 release shortly.

[PttnMe]

I don't see anything waiting for a rc0 release. If there are any miners that want to try pulling from the master branch and confirming you can mine some blocks feedback would be most welcome (block number would be excellent).

Will probably tag a rc0 release shortly.

Block 1021045 mined successfully with Commit 545fadbc.

Version 03000020 (536870915) with vanilla rieMiner instead of 00000020 (536870912) so far with previous commits.

Should we start over Testnet? It is now saying "unknown new rules activated (versionbit 1)"

[Raizou]

So, is gatra still absent? In what exchange is it possible to find Riecoin? In blockexplorer a very reasonable price on satoshis! Has the wallet been updated or are they still working on the update? In fact, Riecoin will need a lot of help from the community because without dev, things are always more difficult.

[cryptapus]

I don't see anything waiting for a rc0 release. If there are any miners that want to try pulling from the master branch and confirming you can mine some blocks feedback would be most welcome (block number would be excellent).

Will probably tag a rc0 release shortly.

Block 1021045 mined successfully with Commit 545fadbc.

Version 03000020 (536870915) with vanilla rieMiner instead of 00000020 (536870912) so far with previous commits.

Should we start over Testnet? It is now saying "unknown new rules activated (versionbit 1)"

Excellent, I see the block version as `0x20000003` which is bit `0` (CSV, BIP65, BIP66) and bit `1` (segwit) signalling via BIP9. You can check the progress of signaling via `getblockchaininfo`.

I didn't have a testnet node to connect to so I'm not sure about what has activated previously. It may be better to restart testnet before versionbit 1 signaled as it would be a testnet specific fix to remove the warning.

[cryptapus]

Major new version (release candidate)

Binaries and source code:

https://github.com/riecointeam/riecoin/releases/tag/v0.16.3.0-rc0

if using git:

    git clone https://github.com/riecointeam/riecoin.git
    git checkout v0.16.3.0-rc0

New in this release:

* Updated to Bitcoin 0.16.3 code base
* Many bug fixes
* BIP65, BIP66, CSV, segwit signaling and support

notes:

* Although this version warns to not use for mining applications, miner feedback is critical.
* A full release is planned soon if no major issues are found.
* If you would like to build your own binaries via gitian (encouraged), you can check that the sha256sum matches these binaries.

Please report issues here:

https://github.com/riecointeam/riecoin/issues

Thanks to clo1 and Pttn for developing this major release.

Also on Reddit: https://www.reddit.com/r/RieCoin/comments/affy30/riecoin_v01630rc0/

[Pon13]

Major new version (release candidate)

Binaries and source code:

https://github.com/riecointeam/riecoin/releases/tag/v0.16.3.0-rc0

if using git:

    git clone https://github.com/riecointeam/riecoin.git
    git checkout v0.16.3.0-rc0

New in this release:

* Updated to Bitcoin 0.16.3 code base
* Many bug fixes
* BIP65, BIP66, CSV, segwit signaling and support

notes:

* Although this version warns to not use for mining applications, miner feedback is critical.
* A full release is planned soon if no major issues are found.
* If you would like to build your own binaries via gitian (encouraged), you can check that the sha256sum matches these binaries.

Please report issues here:

https://github.com/riecointeam/riecoin/issues

Thanks to clo1 and Pttn for developing this major release.

Also on Reddit: https://www.reddit.com/r/RieCoin/comments/affy30/riecoin_v01630rc0/

very very nice !! bravo and many thanks to the new ric team 

[ziiip]

We need to set an activation time for some of these BIP's, that appears to be the only thing causing delay on the node upgrade.
Personally I don't care if we activate any of them.
 
Only BIP that may be worth activating is BIP 65 for CLTV, but I still don't understand how that's better than nLockTime. If it's required for certain DEX then I will support it.
Currently I see no reason to activate segwit though.

[cryptapus]

We need to set an activation time for some of these BIP's, that appears to be the only thing causing delay on the node upgrade.
Personally I don't care if we activate any of them.
 
Only BIP that may be worth activating is BIP 65 for CLTV, but I still don't understand how that's better than nLockTime. If it's required for certain DEX then I will support it.
Currently I see no reason to activate segwit though.

v0.16.3.0-rc0 referenced above has set signaling of BIP9 to begin Jan 1 2019 and thus is within the time frame for signaling. BIP65 and BIP66 is coded to activate along with CSV via BIP9 bit 0, segwit on bit 1. If you operate a pool it would be most welcome to learn if there are any issues with the rc0 release. Although it warns not to use for mining it is perfectly safe to try and we have some confirmation of a few blocks trickling in (I'm guessing from solo miners and not any pools). This is the version that will be released if no one finds any issues in the near future.

Activating segwit allows a new generation of interesting transaction types. It's an optional type of transaction and since upstream already has it active and supported it would appear illogical to purposefully cripple it in the core software.

edit: I suppose a more direct response: Do you have any technical reasons for not wishing to activate segwit?

[cryptapus]

Ziiip why do you think segwit is not good for the coin ? It will not hurt to have it like functionality even to not use it or activating it right now ?
The idea with never ending riecoin is cool and I am 100% agree. The unique of riecoin is its algorithm and I think we must not put limits on this. My c++ skills are not good too but I will help you in that.

The future of the coin right now depend on us. We can have voting on the community board about the direction to where the coin should be developed.

The reasons I think segwit is unnecessary for Riecoin.
1) The blockahin is heavier (transactions require more space)
2) The fee is smaller only for some kind of tx
3) Riecoin traditionally had zero fees for transactions with fewer than 7 inputs(not positive on this number off the top of my head but zero fee is default for small size tx)
4) Since segwit tx get discounted fees by weight and Riecoin still wants 0 fee tx, it only makes sense to change this and make segwit tx more expensive since it requires more space. (this would require change to current Core implementation if segwit is adopted)

Given these points I still see how it's valuable to follow BTC code because it's easiest to merge future updates etc (probably why 99% of altcoins blindly follow it exclusively)
FWIW I really don't care if we continue with following Bitcoin Core at the end of the day these issues are very minor since the chain is not likely to see high use such as the bitcoin chain.

I personally like what Bitcoin Unlimited is doing, primarily with graphene and other improvements to help block propagation, further reduce orphan rates. But I'm not married to that solution, just decided to play around with the idea.

Hopefully that answers your question. I don't intend to have a huge debate about it, but I think the fee situation should at least be given special attention, unless of course everyone is fine with ditching 0 fee tx.

Ah, I think I found some of your technical issues... My impression is that I don't think transaction size should be any issue for Riecoin since we will most likely never approach scaling issues like upstream. I wasn't aware of any issue with zero-fee transactions and segwit, if a miner wishes to mine them I don't see a reason why that is not allowed (that would be a pool or miner setting, correct?).

Segwit's benefits for Riecoin are beyond scaling though, Script versioning and MAST, Schnorr, others come to mind.

[ziiip]

Ah, I think I found some of your technical issues... My impression is that I don't think transaction size should be any issue for Riecoin since we will most likely never approach scaling issues like upstream. I wasn't aware of any issue with zero-fee transactions and segwit, if a miner wishes to mine them I don't see a reason why that is not allowed (that would be a pool or miner setting, correct?).

Segwit's benefits for Riecoin are beyond scaling though, Script versioning and MAST, Schnorr, others come to mind.

I agree, it's easier to just follow the core code than try and change something like segwit.
The current software defaults to zero fee tx if 6 inputs or less, this will change after everyone is upgraded and there will be no zero-fee default.

I'm fine with this, miners can choose to mine 0 fee tx if they want. My beef with segiwt was supposing we keep 0 fee tx, it would make no sense to allow 0 fee segwit tx as they require more space but this is a moot point as it is up to the miners which tx to include (as it should be)

uBlock.it will upgrade it's nodes to this RC as soon as possible.
My only worry is that "All Others" miner goes along with the upgrade as well, since they do not publicly discuss anything we'll have to keep a close eye on if/when they signal support.

[cryptapus]

...

...

My only worry is that "All Others" miner goes along with the upgrade as well, since they do not publicly discuss anything we'll have to keep a close eye on if/when they signal support.

We discussed this a bit on github, our current BIP9 consensus threshold is 95%. If we can prove that we can at least get a vast majority of hashrate to signal and are blocked by a minority we can perhaps address that ratio using bit 2.

[Mathieu86]

Thank you for this incredible work !