Post
Topic
Re: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record
by
clo1
on 09/09/2018, 05:06:10 UTC
I've posted my code on github.
https://github.com/clo-prime/riecoin-0.16

So far I have built it on Ubuntu 16.04 and tested on Ubuntu 16.04 and 17.10. I have run on testnet and mainnet. I have tested mining, sending, and receiving. I have tested the GUI and command line. This code is still experimental. I make no guarantees.

To build, follow instructions in doc/build-unix.md. The test runs have not been updated and will not compile. Configure with –disable-tests (2 dashes, then 1 dash).

Until segwit is enabled you must run with addresstype=legacy in your riecoin.conf file. Without this segwit addresses will be used. I believe the transactions will be accepted but you won't be able to spend them until segwit is enabled. When generating an address, make sure it starts with 'R' (or 'r' on testnet) and not '3' (or '2' on testnet).

I've temporarily set the default directory to be .riecoin16 instead of .riecoin so that all testing is kept separate from the current core. This can be overridden  with -datadir from the command line or riecoin.conf file.

Getwork is no longer supported in bitcoin. Pttn, it would be awesome if you could add GetBlockTemplate support to rieMiner. I’ve temporarily added getwork support to the code for testing although the format is slightly different. It takes an address as an input.

Wallet mining was removed from bitcoin several versions ago. I recently noticed there is some mining code for testing purposes (generateblocks and generatetoaddress). I haven’t implemented this. Is this needed and if so what code should be used here? I know the code currently in the core is outdated.

I haven’t added any seed addresses but this will be simple once we determine what they should be.

IGJ – thanks for running the testnet and your work setting up the community site.

The softforks haven't been tested yet but I don't expect any problems here. The older BIPS are coded to become active at a specific block. I have currently set them to become active at block 1000000 but this can be changed to a block that will be reached shortly after the code is released. Once this block is reached any block mined with an old miner (using an old block version number) will be rejected even if the block is otherwise perfectly valid.

The newer BIPS become active if a super-majority of blocks are mined using a miner indicating support. I believe it is 95% within a 288 block window. This must occur within a specific time window which we will need to set before releasing code.