Pages:
Author

Topic: [ANN] ReikiCoin - Heals and cures, SHA 256 POS 101g ssl implemented - page 3. (Read 40091 times)

legendary
Activity: 1638
Merit: 1036
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
}
]
 Grin
sr. member
Activity: 325
Merit: 251
Any ideas?
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?
legendary
Activity: 1148
Merit: 1018
It's about time -- All merrit accepted !!!
coming alive again i see indeed

i have a fairly mature chain somewhere
sr. member
Activity: 325
Merit: 251
Any ideas?

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?
legendary
Activity: 1764
Merit: 1022

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.

sr. member
Activity: 480
Merit: 250
sr. member
Activity: 325
Merit: 251
Any ideas?
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.
legendary
Activity: 1638
Merit: 1036

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
legendary
Activity: 1638
Merit: 1036
hmmm someone performing a reseruction on this coin

I've always had a soft spot for reiki coin Smiley
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 Smiley


.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,



legendary
Activity: 1764
Merit: 1022


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 Smiley



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

getblockhash 321591
72e5f28220afcea4f3eebc0900ff9aa2f49d8dd3a3ca4022afe23a3bc7930a08
legendary
Activity: 1638
Merit: 1036

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 Smiley


legendary
Activity: 1764
Merit: 1022
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 Cheesy

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/",



legendary
Activity: 1148
Merit: 1018
It's about time -- All merrit accepted !!!
hmmm someone performing a reseruction on this coin
sr. member
Activity: 480
Merit: 250
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 Cheesy

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?
legendary
Activity: 1638
Merit: 1036
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 Cheesy

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.
legendary
Activity: 1204
Merit: 1000
to your stations, man the pineapples!!!
this is the first time i've ever dealt with this sort of situation, so am unfamiliar with the finer details of mining below checkpoint heights.

the question obviously is how this incredibly active community will react to any necessary changes Wink

also whether a chain matching the coded checkpoint can be found. what to do with that....
obviously making months of yr work just plain forked up

---

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

sr. member
Activity: 480
Merit: 250
My node is clone from source, its work, sync with my wallet, some time i see wallet where is big number chain but not syncing - it forked. Its one, now is minimal 3-4 wallet on working chain
legendary
Activity: 1204
Merit: 1000
to your stations, man the pineapples!!!
look to http://146.185.162.58/reiki/rpcace.php  last block 44 RKC is solo mining with qt wallet, i test with bgfminer and usb stick Ant U1 - its works  Grin.


i could not solo mine with a self compiled linux daemon UNTIL i had removed the checkpoint.
i am currently mining on your chain.

maybe other clients are not so picky??

however, there will be an issue when we hit the checkpointed block and the official code will reject the blockhash.


maybe there wallet where is big number of block but in another chain - and our wallet not fully sync with him Grin

lol. then we're forking for sure.
i messaged cinnamon to see if they have a larger blockchain.

if there is no longer chain, then an update will become necessary as we will never match the coded checkpoint.


edit.
i was wondering if it was a slip up from the dev and accidentally left over hash from clone source.
however a quick search of github only turns up that particular hash for reiki so it looks like at some point reiki was longer than it is now.
lol
sr. member
Activity: 480
Merit: 250
look to http://146.185.162.58/reiki/rpcace.php  last block 44 RKC is solo mining with qt wallet, i test with bgfminer and usb stick Ant U1 - its works  Grin.


i could not solo mine with a self compiled linux daemon UNTIL i had removed the checkpoint.
i am currently mining on your chain.

maybe other clients are not so picky??

however, there will be an issue when we hit the checkpointed block and the official code will reject the blockhash.


maybe there wallet where is big number of block but in another chain - and our wallet not fully sync with him Grin
legendary
Activity: 1204
Merit: 1000
to your stations, man the pineapples!!!
look to http://146.185.162.58/reiki/rpcace.php  last block 44 RKC is solo mining with qt wallet, i test with bgfminer and usb stick Ant U1 - its works  Grin.


i could not solo mine with a self compiled linux daemon UNTIL i had removed the checkpoint.
i am currently mining on your chain.

maybe other clients are not so picky??

however, there will be an issue when we hit the checkpointed block and the official code will reject the blockhash.




edit, if reiki is to survive perhaps a new source is in order .
in which case . lowering minimum stake age might be useful .
Pages:
Jump to: