Pages:
Author

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

legendary
Activity: 1302
Merit: 1000
ORB has a good chance to grow.
anybody online with a node?
sr. member
Activity: 325
Merit: 251
Any ideas?
yes mined, mined.
POF is working  - mining difulcity is low, and next move is Add coin request to Yobit.net only 0.1 BTC  Roll Eyes

You appear to be stalled at block 356999  Roll Eyes

I rebulid node with bumbacoin git and its works now is block 360582 Grin

Very Messy.

How many rebuilds and or modifications have you now made to the coin over the last few months since you started this experiment?
sr. member
Activity: 480
Merit: 250
yes mined, mined.
POF is working  - mining difulcity is low, and next move is Add coin request to Yobit.net only 0.1 BTC  Roll Eyes

You appear to be stalled at block 356999  Roll Eyes

I rebulid node with bumbacoin git and its works now is block 360582 Grin
sr. member
Activity: 325
Merit: 251
Any ideas?
yes mined, mined.
POF is working  - mining difulcity is low, and next move is Add coin request to Yobit.net only 0.1 BTC  Roll Eyes

You appear to be stalled at block 356999  Roll Eyes
sr. member
Activity: 480
Merit: 250
yes mined, mined.
POF is working  - mining difulcity is low, and next move is Add coin request to Yobit.net only 0.1 BTC  Roll Eyes
legendary
Activity: 1638
Merit: 1036
My holdings are around 110,000 Reiki found both pre and post (July 2014) fork through a combination of mining and staking.  While I wish Reiki Coin well, I don't want to create animosity with the wider community and will bow out of further pushing for the "357 Chain".

I'll leave the blocks up on Mega and MediaFire for research purposes.

i guess we'll keep mining on the "new" chain then Smiley

as things stand then

█ the clients compiled previously seem to lack any problematic checkpoints so they seem fine to use as is.

█ any new clients compiled from "official" source will have problematic checkpoint,
for any new compiles there are two choices

1. remove checkpoint from source for block 357000 (or comment it out)
https://github.com/ReikiLVL3/reikicoin/blob/master/src/checkpoints.cpp#L29

2. use the git i created, it has new checkpoints matching the current chain
https://github.com/bumbacoin/reikicoin

█ it will probably be advantageous to create a new thread and compile new clients with the updated checkpoints,




i've been quite busy of late so have only been peripherally interacting here, i might find some time coming soon (i hope)
and i can put some effort into looking at the code and arranging some new clients..

i also can send you, RussiaCoinDotInfo some reiki as i seem to have mined a few Wink

i wonder if the reiki master still thinks of us Cheesy
legendary
Activity: 1638
Merit: 1036
curiously the chain is currently disconnecting PoW blocks.

i've been mining for the last little while, i get blocks, then they disconnect in favour of a PoS block.
i went back 200 1000 blocks on the explorer and they 're all PoS blocks.
(here's the last PoW block) http://146.185.162.58/reiki/rpcace.php?339373

the explorer displays these PoW blocks until they're disconnected from the chain.

http://146.185.162.58/reiki/rpcace.php


edit.
i mined a few blocks that are still there. although it's gone back to staking all the blocks now and disconnecting the PoW blocks

i imagine the PoS block outweighs the PoW block for difficulty hence the disconnecting of those blocks .. but then i assume then that the staking client is unaware of my PoW which is the actual curiosity

that the client is staking generally obliviously to the erstwhile PoW blocks
sr. member
Activity: 325
Merit: 251
Any ideas?
My holdings are around 110,000 Reiki found both pre and post (July 2014) fork through a combination of mining and staking.  While I wish Reiki Coin well, I don't want to create animosity with the wider community and will bow out of further pushing for the "357 Chain".

I'll leave the blocks up on Mega and MediaFire for research purposes.
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.


New git Grin
legendary
Activity: 1638
Merit: 1036
Do you suppose a second block chain can reach the check point 357,000 and come up with the same check point block?

the hashes are based on previous block hash and other block specifics.

i don't know whether it's possible to generate the same hash for completely different blocks, but if so, it would be as unlikely as putting your finger through one ear and wiggle it out the other. (i.e. it would involve some hefty manipulation of yr head. lol)

in other words, no.


any opinions on which chain to go with?

i personally think the 2nd chain from johan11,
 - the coin must have been pretty dead for it to fork so badly, no-one even seemed to notice until now.
 - without johan11's effort the coin would be well dead.
 - i'm all up for a fork to lower min stake age to create a more manageable chain with lower PoS requirements, atm PoS blocks have no hope in moving the chain usefully and it seems 90% (heh made up figures ftw) reliant on PoW
any fork will require a new git and new thread which will also assist in getting rid of the "bad" checkpoint.


i also personally think this coin is unlikely to survive even with this effort so it's more fun than anything else.


heh, unless the dev notices this activity and decides to show up after this long..
sr. member
Activity: 325
Merit: 251
Any ideas?
As I posted on the previous page I was receiving payouts from iSpace and staking up to December 2014.

My guess would be johan11 turned off their Wallet / Node on that date and nine months later restarted their Wallet / Node to find there were no other active nodes and started Mining / Staking.

We could ask others who've posted in the past to restart their Wallets and see who's syncs with who's - No?

Do you suppose a second block chain can reach the check point 357,000 and come up with the same check point block?
legendary
Activity: 1638
Merit: 1036

in blockexplorer in height 283883 is time
1425178261

GMT: Sun, 01 Mar 2015 02:51:01 GMT


lol oops. fixed earlier post Smiley
so, a goodly time between blocks .. nearly 8 months
sr. member
Activity: 480
Merit: 250
this seems to be where they fork.
way before the checkpoint on github, very strange no mention of a fork in thread ..


chain 1 - russia coin/ matching git commit

getblockhash 283883
0000000000111be8898dca381928c7273939cf440da24492a0edc002c076ee18

"time" : 1402997334
GMT: Tue, 17 Jun 2014 09:28:54 GMT



chain 2 - blockexplorer

height 283883
http://146.185.162.58/reiki/rpcace.php?97a477c0f5fff12d20d6361f4b73d7e63a75cdc5e6ae75b39145fdec4c3c3b9f

time   1402997329
GMT: Tue, 17 Jun 2014 09:28:49 GMT


in blockexplorer in height 283883 is time
1425178261

GMT: Sun, 01 Mar 2015 02:51:01 GMT
legendary
Activity: 1638
Merit: 1036
this seems to be where they fork.


===== shared

block 283882
http://146.185.162.58/reiki/rpcace.php?9d0686e2bc158d073feb91837954b75f9f3e418f6fabc7ce105d56f3dc300693

time   1402997329
GMT: Tue, 17 Jun 2014 09:28:49 GMT

==== then fork

chain 1 - russia coin/ matching git commit

getblockhash 283883
0000000000111be8898dca381928c7273939cf440da24492a0edc002c076ee18

"time" : 1402997334
GMT: Tue, 17 Jun 2014 09:28:54 GMT



chain 2 - blockexplorer

height 283883
http://146.185.162.58/reiki/rpcace.php?97a477c0f5fff12d20d6361f4b73d7e63a75cdc5e6ae75b39145fdec4c3c3b9f

time 1425178261
GMT: Sun, 01 Mar 2015 02:51:01 GMT




---
and for interest sake, the checkpointed block, about 3 months before the fork

357000 : 4e7666bb31c44138b41c78b06b170075ad1d0180108bc8b9bd7e71d2f49d7805
time : 1415579531
GMT: Mon, 10 Nov 2014 00:32:11 GMT
sr. member
Activity: 325
Merit: 251
Any ideas?
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 Smiley

I've got two files blk0001.dat and blkindex.dat for ReikiCoin up to block 367126 on the confirmed post 357,000 check point.

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


sr. member
Activity: 325
Merit: 251
Any ideas?
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.
sr. member
Activity: 325
Merit: 251
Any ideas?
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.
Pages:
Jump to: