[ANN] ReikiCoin - Heals and cures, SHA 256 POS 101g ssl implemented

[bumbacoin]

If the chain matching "official" git is not found,
I have forked the code and added some checkpoints to match current chain.

https://github.com/bumbacoin/reikicoin

I maybe able to compile a windows source sometime in the future but am currently not able to,
I can however compile a mac wallet in the nearby future

I believe the windows qt's available would only have checkpoints hardcoded for block 1.
So it is of no immediate hurry/concern as they shouldn't reject block 35700.

it also occurs to me that its' plausible that the available clients will not have that coded checkpoint.
with this post predating the checkpoint update

Update 5/4/2014 - Reikicoin Windows binaries now compiled with openssl 1.0.1g by Shakezula

https://drive.google.com/file/d/0B_PoRrj3QF5sOFVfVVFKMTRnRlk/edit?usp=sharing

I might upload a bootstrap as well to keep a copy of the current chain.

[1714777894]

1714777894

[1714777894]

1714777894

[1714777894]

1714777894

[johan11]

If the chain matching "official" git is not found,
I have forked the code and added some checkpoints to match current chain.

https://github.com/bumbacoin/reikicoin

I maybe able to compile a windows source sometime in the future but am currently not able to,
I can however compile a mac wallet in the nearby future

I believe the windows qt's available would only have checkpoints hardcoded for block 1.
So it is of no immediate hurry/concern as they shouldn't reject block 35700.

it also occurs to me that its' plausible that the available clients will not have that coded checkpoint.
with this post predating the checkpoint update

Update 5/4/2014 - Reikicoin Windows binaries now compiled with openssl 1.0.1g by Shakezula

https://drive.google.com/file/d/0B_PoRrj3QF5sOFVfVVFKMTRnRlk/edit?usp=sharing

I might upload a bootstrap as well to keep a copy of the current chain.

thx, is need build new demon for my node?

[cinnamon_carter]

hmmm someone performing a reseruction on this coin

[TimC]

If the chain matching "official" git is not found,
I have forked the code and added some checkpoints to match current chain.

https://github.com/bumbacoin/reikicoin

I maybe able to compile a windows source sometime in the future but am currently not able to,
I can however compile a mac wallet in the nearby future

I believe the windows qt's available would only have checkpoints hardcoded for block 1.
So it is of no immediate hurry/concern as they shouldn't reject block 35700.

it also occurs to me that its' plausible that the available clients will not have that coded checkpoint.
with this post predating the checkpoint update

Update 5/4/2014 - Reikicoin Windows binaries now compiled with openssl 1.0.1g by Shakezula

https://drive.google.com/file/d/0B_PoRrj3QF5sOFVfVVFKMTRnRlk/edit?usp=sharing

I might upload a bootstrap as well to keep a copy of the current chain.

thx, is need build new demon for my node?

So I open my wallet which is version "v0.1.3.0-g99999-boc' and it downloaded about 3k blocks and it is in sync and staking. I'll keep the wallet open for a while. The peers that I'm connteced to show
"version" : 60006,
"subver" : "/reikicoin:1.9.1/",

[bumbacoin]

it also occurs to me that its' plausible that the available clients will not have that coded checkpoint.
with this post predating the checkpoint update

Update 5/4/2014 - Reikicoin Windows binaries now compiled with openssl 1.0.1g by Shakezula

https://drive.google.com/file/d/0B_PoRrj3QF5sOFVfVVFKMTRnRlk/edit?usp=sharing

thx, is need build new demon for my node?

it really depends on how old your daemon is, you've been posting for quite a while so maybe it pre-dates the checkpoint commit which will become the issue.
AND given that your daemon is syncing fine, you probably don't have that checkpoint.

you can also check IF you still have the src you compiled from. see if it matches this line which is the problematic checkpoint.
https://github.com/ReikiLVL3/reikicoin/blob/master/src/checkpoints.cpp#L29

compiling from my new source with new checkpoints will theoretically help a little in some circumstances as the point of having checkpionts is to hardcode the "official" chain so no fork is possible before those points.
so it will only be a problem if anyone comes along with the actual chain matching the official checkpoint at 357000.


/// \\\

So I open my wallet which is version "v0.1.3.0-g99999-boc' and it downloaded about 3k blocks and it is in sync and staking. I'll keep the wallet open for a while. The peers that I'm connteced to show
"version" : 60006,
"subver" : "/reikicoin:1.9.1/",

if you're looking for confirmation you're on the same chain, just check johan11's explorer

Reiki explorer http://146.185.162.58/reiki/rpcace.php  

[TimC]

So I open my wallet which is version "v0.1.3.0-g99999-boc' and it downloaded about 3k blocks and it is in sync and staking. I'll keep the wallet open for a while. The peers that I'm connteced to show
"version" : 60006,
"subver" : "/reikicoin:1.9.1/",

if you're looking for confirmation you're on the same chain, just check johan11's explorer

Reiki explorer http://146.185.162.58/reiki/rpcace.php  

I checked on Johan11's explorer and I'm on the same chain. Thanks

getblockhash 321591
72e5f28220afcea4f3eebc0900ff9aa2f49d8dd3a3ca4022afe23a3bc7930a08

[bumbacoin]

hmmm someone performing a reseruction on this coin

I've always had a soft spot for reiki coin
but personally I don't think it'll really survive unless someone modifies staking ages.

PoW is too much work lol.

with min stake age at 30 days and 1 minute block times, it needs to have a base minimum of 43200 staking inputs to theoretically move on staking alone.

With the current teeny network, I'd think something like 1 day min to 7 days max.

min of 1 day, makes a base theoretical minimum of 1440 inputs, much more doable/reliable.

and the 7 days max to vaguely keep calm the mayhem produced by someone opening an old wallet and staking their entire wallet in 3 seconds flat, if the stake diff was much higher it wouldn't be such a problem


.that said I haven't done serious considerations on those numbers, but having the hybrid system helps to keep it moving if one or the other diff gets tremendously skewed,
I guess the combine threshold could be rejigged too, I've never heavily considered the math involved in finding a good setting for that so should be interested to hear others opinions.


    "moneysupply" : 19940633.45941700,

[bumbacoin]

here's a bootstrap for the current chain, up to block 321652

unzip, rename to bootstrap.dat and put it in yr datadir.



https://drive.google.com/file/d/0B5j8d4FSc7drWFRSWERtQmZiOGM/view?usp=sharing

[RussiaCoinDotInfo]

My last pre 2016 block was 0d01310b80cbda7e2b51afbd9401dd2dbba012f193a6ab87d490a322fa5e6574

Code:

Status: 1234 confirmations
Date: 16/12/2014 08:09
From: unknown
To: BNYLnzDxoYCn7cvExFGeReeTKe7zSCJo7v (own address, label: iSpace.co.uk:3345)
Credit: 20.94335 RKC
Net amount: +20.94335 RKC
Transaction ID: 0d01310b80cbda7e2b51afbd9401dd2dbba012f193a6ab87d490a322fa5e6574

I am now up to

Code:

v0.1.3.0-g99999-boc
Build date July 4, 2013

Current number of blocks 367126
Estimated total blocks 329905

Hope this helps.

[johan11]

look to explorer http://146.185.162.58/reiki/rpcace.php

[TimC]

I am now up to

Code:

v0.1.3.0-g99999-boc
Build date July 4, 2013

Current number of blocks 367126

The Reikicoin block explorer shows block 330655 so you are on your own chain/fork.

[RussiaCoinDotInfo]

I am now up to

Code:

v0.1.3.0-g99999-boc
Build date July 4, 2013

Current number of blocks 367126

The Reikicoin block explorer shows block 330655 so you are on your own chain/fork.

I would have thought that was obvious when I said:

My last pre 2016 block was 0d01310b80cbda7e2b51afbd9401dd2dbba012f193a6ab87d490a322fa5e6574

Code:

Status: 1234 confirmations
Date: 16/12/2014 08:09
From: unknown
To: BNYLnzDxoYCn7cvExFGeReeTKe7zSCJo7v (own address, label: iSpace.co.uk:3345)
Credit: 20.94335 RKC
Net amount: +20.94335 RKC
Transaction ID: 0d01310b80cbda7e2b51afbd9401dd2dbba012f193a6ab87d490a322fa5e6574

which you conveniently cut out of my quote.

Perhaps you can shed light on when you think the fork occurred?

[cinnamon_carter]

coming alive again i see indeed

i have a fairly mature chain somewhere

[RussiaCoinDotInfo]

coming alive again i see indeed

i have a fairly mature chain somewhere

It might end up being a case of who's blocks are the oldest that match?

[bumbacoin]

My last pre 2016 block was 0d01310b80cbda7e2b51afbd9401dd2dbba012f193a6ab87d490a322fa5e6574

Code:

Status: 1234 confirmations
Date: 16/12/2014 08:09
From: unknown
To: BNYLnzDxoYCn7cvExFGeReeTKe7zSCJo7v (own address, label: iSpace.co.uk:3345)
Credit: 20.94335 RKC
Net amount: +20.94335 RKC
Transaction ID: 0d01310b80cbda7e2b51afbd9401dd2dbba012f193a6ab87d490a322fa5e6574

I am now up to

Code:

v0.1.3.0-g99999-boc
Build date July 4, 2013

Current number of blocks 367126
Estimated total blocks 329905

Hope this helps.

can you check your hash for block
       357000
if it's 4e7666bb31c44138b41c78b06b170075ad1d0180108bc8b9bd7e71d2f49d7805
then you have ze official chain !!!

that block is check pointed in the OG repo so must be legit.

seemingly the one running atm forked about a year ago? at least since (lol i'd be sad cos i've mined a few on this theoretically illigitimate chain.)

19:13:31

getpeerinfo


19:13:31

[
{
"addr" : "70.40.55.192:9015",
"services" : "00000001",
"lastsend" : 1425665587,
"lastrecv" : 1425665587,
"conntime" : 1425554788,
"version" : 60006,
"subver" : "/reikicoin:1.9.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 291029,
"banscore" : 0
},
{
"addr" : "75.130.163.51:9015",
"services" : "00000001",
"lastsend" : 1425665586,
"lastrecv" : 1425665586,
"conntime" : 1425663871,
"version" : 60006,
"subver" : "/reikicoin:1.9.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 290648,
"banscore" : 0
}
]
 

[RussiaCoinDotInfo]

OK.

First I typed

Code:

getblock 4e7666bb31c44138b41c78b06b170075ad1d0180108bc8b9bd7e71d2f49d7805

and got

Code:

{
"hash" : "4e7666bb31c44138b41c78b06b170075ad1d0180108bc8b9bd7e71d2f49d7805",
"confirmations" : 10127,
"size" : 459,
"height" : 357000,
"version" : 4,
"merkleroot" : "a65873dcf0d1153f0d69b8ef4771e96d7e1cd409d9692c8982e92d2f247364e8",
"mint" : 3.77064600,
"time" : 1415579531,
"nonce" : 0,
"bits" : "1e00ff1b",
"difficulty" : 0.00391989,
"previousblockhash" : "0000000001cf3057d98c5d922a515d64e49cdbfdec7d273dd328394c88ea942c",
"nextblockhash" : "c72e40ce3896196222cf05bf77497a0fb1cd3433046e563b414ed8465126d8d0",
"flags" : "proof-of-stake",
"proofhash" : "00008cd2666fbcdcc68ee9e252eccebecced903e5011e3b591cc5571089222c1",
"entropybit" : 1,
"modifier" : "dbe1721f51c5498e",
"modifierchecksum" : "c2e14e59",
"tx" : [
"6c89ab3771a3f1eab82c770ded6b9765aa0145e4a55e367a90995e28ae78268b",
"d5580f23ecd55da492f8ed95166b7214d5a0093d884a60d6eec06d6c9757963d"
],
"signature" : "3046022100cf5049fade6076997848a07e99e991d40ebaf37a608e024d61d1e01398d3bd8f022100802cb7f62fda1eb0b58776b5af4063da3e95026e1d70b18300af4061ff5821dc"
}

then I went down until I found these:

Code:

Status: 18341 confirmations
Date: 22/10/2014 02:32
From: unknown
To: BNYLnzDxoYCn7cvExFGeReeTKe7zSCJo7v (own address, label: iSpace.co.uk:3345)
Credit: 32.164938 RKC
Net amount: +32.164938 RKC
Transaction ID: 5c6ad3c50314db745f20249890d60eb605634fc341ea7fcec03cfaa2d4442dae

the very next block I have is:

Code:

Status: 8870 confirmations
Date: 24/11/2014 10:55
From: unknown
To: BNYLnzDxoYCn7cvExFGeReeTKe7zSCJo7v (own address, label: iSpace.co.uk:3345)
Credit: 45.985373 RKC
Net amount: +45.985373 RKC
Transaction ID: 9e71995ce802101c349acf6376e2775ee3c19b7133df253a7d08b883e7bd33d7

Hope this helps.

[RussiaCoinDotInfo]

can you check your hash for block
       357000
if it's 4e7666bb31c44138b41c78b06b170075ad1d0180108bc8b9bd7e71d2f49d7805
then you have ze official chain !!!

that block is check pointed in the OG repo so must be legit.

seemingly the one running atm forked about a year ago? at least since (lol i'd be sad cos i've mined a few on this theoretically illigitimate chain.)

Are there later check points to the one you mentioned?

My last pre-2016 is

Code:

Status: 1234 confirmations
Date: 16/12/2014 08:09
From: unknown
To: BNYLnzDxoYCn7cvExFGeReeTKe7zSCJo7v (own address, label: iSpace.co.uk:3345)
Credit: 20.94335 RKC
Net amount: +20.94335 RKC
Transaction ID: 0d01310b80cbda7e2b51afbd9401dd2dbba012f193a6ab87d490a322fa5e6574

which would be block 365892 as my current number of blocks is 367126

Given that iSpace recently lost all their data through a Hard Drive failure (and discontinued Reiki Coin mining an aeon ago), I'm not too sure where to find an independent cross verification.

[bumbacoin]

OK.

First I typed

Code:

getblock 4e7666bb31c44138b41c78b06b170075ad1d0180108bc8b9bd7e71d2f49d7805

and got

Code:

{
"hash" : "4e7666bb31c44138b41c78b06b170075ad1d0180108bc8b9bd7e71d2f49d7805",
"confirmations" : 10127,
"size" : 459,
"height" : 357000,
"version" : 4,
"merkleroot" : "a65873dcf0d1153f0d69b8ef4771e96d7e1cd409d9692c8982e92d2f247364e8",
"mint" : 3.77064600,
"time" : 1415579531,
"nonce" : 0,
"bits" : "1e00ff1b",
"difficulty" : 0.00391989,
"previousblockhash" : "0000000001cf3057d98c5d922a515d64e49cdbfdec7d273dd328394c88ea942c",
"nextblockhash" : "c72e40ce3896196222cf05bf77497a0fb1cd3433046e563b414ed8465126d8d0",
"flags" : "proof-of-stake",
"proofhash" : "00008cd2666fbcdcc68ee9e252eccebecced903e5011e3b591cc5571089222c1",
"entropybit" : 1,
"modifier" : "dbe1721f51c5498e",
"modifierchecksum" : "c2e14e59",
"tx" : [
"6c89ab3771a3f1eab82c770ded6b9765aa0145e4a55e367a90995e28ae78268b",
"d5580f23ecd55da492f8ed95166b7214d5a0093d884a60d6eec06d6c9757963d"
],
"signature" : "3046022100cf5049fade6076997848a07e99e991d40ebaf37a608e024d61d1e01398d3bd8f022100802cb7f62fda1eb0b58776b5af4063da3e95026e1d70b18300af4061ff5821dc"
}

this …

basically the situation is that a major fork is currently excitingly in our midst.

the chain held by RussiaCoinDotInfo matches the checkpoint on the official hub, BUT has not been touched for over 12 months?

the chain currently mined by myself and Johan11 has been running since at least may 2015, but is incompatible with the official source on github.


.
if we were to go with 1 - the chain matching official hub.
that would destroy over a year of work that has potentially important transactions on it - however given the lack of exchanges or major infrastructure it probably does not matter.

if we were to go with 2 - the chain kept alive.
that would mean the official git is a problem, would need a new thread AND new git.
also would meant the loss of a lot of other legitimate work on the chain ..


johan11 has put the most work into this over the last year and is running chain number 2.

[RussiaCoinDotInfo]

I was staking my meager coins until the last node I was connected to died (Circa late 2014).  When I saw the recent revival I connected to that Node and have recommenced staking (and after the first flurry of staked coins playing catch up, the staking has slowed down again).  I have discontinued staking until there is consensus about where to go from here.

There are some ReikiCoin related items via Twitter that I have found in the last couple of days and I have also found that some material is archived via Archive.Org *and* there is also an active list of Alt coins which still has information concerning Reiki Coin which I haven't had time to read through.

So,

• When was the last exchange active?
• When was the last node active post Dec 2014?
• Who wants a copy of my block chain with 357,000 block attached?
• Has the original Dev gone AWOL?
• Where does johan11 's block chain fork? Pre/Post 357,000? How far back? Block three?

No doubt there are other questions to consider.

[bumbacoin]

post yr chain up somewhere. and we can see how it looks ..

i'm surprised you're staking though, means someone is on the same chain as you? or you have two clients with different chains