Topic: EinaiOraCoin [EOC] 365% POS Very stable coin with lots coming this summer for it - page 17. (Read 40221 times)

bro honestly in my opinion you have to do your numbers straight first see if swap will cost u less or the coding reworked. i believe you had already done coding work once before to fix PoS issue and now its again. as i advise you earlier to contact PressTab since he recently revamped entire RateCoin PoS and i do recognize him as PoS guru again not sure what will be his terms?

again i would emphasize check your budget bcoz with the PoS coins problems will arise time to time. so check again swap or coding and let us know should you decide. i would recommend to do Poll to get better opinion from community after calculating your budget.

Good Luck

I don't think he is sitting around waiting for a Dev to contact him mate lol I think he has been asking around but hasn't been able to find someone to help him out yet and honestly I'm still sticking around here because he has always been straight forward with everyone about everything and he hasn't ever asked any of us investors to put any of our coins out or help out with anything which I kind of respect.  He told everyone right from the get go that he was very new to this and to be honest with all the mistakes that have happened throughout the coins lifespan so far he has always eventually gotten things fixed! And I also asked about the node but other people are saying that shouldn't stop the chain from moving but I somewhat disagree because if it was a hosting node for the coin then if it was closed all of a sudden why would it continue to generate blocks then? But anyways Dev thanks for touching base and if people want to bail out I'll gladly buy their EOC off of them Cheers

Sitting waiting for a dev. to contact you is not a solution.
Noone is stampeding to fix the code problem - if there
is one. Was the posible non-working node every ruled out?

What is the cost of a wallet fix vs. a swap and new wallet?
A name change is not a bad thing.
At this point I think the majority would like a working wallet vs.
  any other option that includes a non-working wallet!

Hello Everyone,

I apologize about the delay on some answers but my youngest got sick and I've been playing Mister Mom while the wife has been working.  So needless to say all my time and energy has been going into taking care of a pukey sick 6 year old.  I posted a thread in the service announcements asking for a developer that I could hire to help with the coin and fix the chain but haven't gotten any responses yet.

Another idea that a member of the community had mentioned to me was the possibility of making the coin totally revamped with a whole new wallet and source and just do a complete 1:1 swap to the new coin.  If that was an option then I would be able to make it the EveryonesCoin like I had intended and the ticker would still remain EOC but I would like to know how everyone would feel about that idea?  I will not even attempt to do a complete swap for this coin if the total majority doesn't agree with it.

If I knew more about POS coding and how to just make everything fork over to complete POS then I wouldn't have a problem getting things back on track but like I've stated before I'm still pretty much a complete rookie with developing coins and especially with the coding for POS coins.  I am going to hopefully try to contact a couple other Developers that were mentioned to me to see if maybe they aren't busy they could possibly fix this ASAP so that we can get everything back on track.

I do wish I had some better news for everyone right now but I promise that this problem will get fixed and EOC will continue with the future plans of the coin and I am just hoping that I can hopefully add some members to the team soon because it is a little too much to do everything on my own with the limited funding that I have right now.  But I will post again tomorrow and let everyone know whether or not I've found someone that can help with this chain being stuck and I also would like to know what everyone thinks about if we were to do a complete do over with a 1:1 swap for EOC?

Thanks,
Have a Great Night
EinaiOraCoinDev

its been a while did you get hold of any dev yet or no, keep us updated bro since few of us waiting for some good news from u

Hello Everyone,

NoobKid I got your PM and I messaged you back so just get back to me when you have a chance.  I appreciate the help from the community is assisting me in finding other people to help with getting the chain fixed and everything running again smoothly.  I am officially starting my 2 week holidays today so I will be around a lot more and hopefully will be able to get more of the things I am looking to get accomplished finished.

I cannot guarantee the fix will be today or tomorrow but I do promise that as soon as I have a good developer who can do the fix for the coin at a fair and reasonable rate that I will immediately get them to fix everything.  As for the website I should have a sneak peek within a week of what the general layout will be and how people will be able to use it for EOC and the aspects behind registering their EOC addresses to EZ addresses where it will be as easy to send and receive EOC as it is to do your online banking or use a debit card.

I will keep everyone posted on progress and details more often now as well.

Thanks,
Have a Great Day
EinaiOraCoinDev

Hey Dev I spoke to a buddy about fixing the problem and I sent you a PM to get ahold of this person to discuss the details about the pricing and what not to fix this problem and get everything going for this shiat Hopefully hear from you soon mate Cheers

Thank you - communication appreciated
Things are screwed up but... you are still here!

Hello Everyone,

I am going to be posting an ad in the service section to look into hiring a Developer who can possibly fork the coin to straight POS and fix the chain because after everything I've read and everything that I've gone through I can only possibly think that when I got help extending the POW that it may have compromised the chain making it vulnerable to attacks and suspending the chain stopping the blocks from moving.  I'm not 100% sure on this but I figure that if I can hire someone to fix the code and make the coin fork to strictly POS like it should have been in the very beginning then we can continue from there.

Also I start my holidays tomorrow so I will have way more time to focus on the work for EinaiOraCoin and making it more towards the goals that I intend to achieve with the coin, but like I've stated before being a rookie developer and without a team behind me it's going to take time and be a slow process but I will strive to achieve all the goals that I am intending to achieve for EinaiOraCoin.

Thanks,
Have a Great Day
EinaiOraCoinDev

That's simply because there is no hash of the next block yet, it's the one being mined on. Looks the same when you query any coind on the current/next block. So in my understanding it would the hash of 20988 which we are all so desperately expecting 

Check this thread for something that sounds very close to what we see here. When I output bnTarget I get a negative value which then again rejects the block due to the check in main.cpp line 1162.
HTH

When you type getblockbynumber "blocknumber" into debug console I get this :


17:43:18

getblockbynumber 20986


17:43:18

{
"hash" : "00000001253ce61440d7c5154ed17d6c9583fba4cbc228529d2c8222147ce15c",
"confirmations" : 2,
"size" : 183,
"height" : 20986,
"version" : 6,
"merkleroot" : "070f5b851bf7d22bc8e57c7865c99df880dd6ed736bcd0b6ac4ff2b210b85bcc",
"mint" : 1.00000000,
"time" : 1435719514,
"nonce" : 2126708960,
"bits" : "1d01e696",
"difficulty" : 0.52610664,
"blocktrust" : "1",
"chaintrust" : "aa5fd",
"previousblockhash" : "0000000050496a633f2c995bced0378164803ca8a4b24259528486bd85c5863f",
"nextblockhash" : "c7f5fc288f4132c3bd95f84c9e5546da3fb2ccaf83964a18beded1f4a1142983",
"flags" : "proof-of-work",
"proofhash" : "00000001253ce61440d7c5154ed17d6c9583fba4cbc228529d2c8222147ce15c",
"entropybit" : 0,
"modifier" : "31f3db4c56d8a15e",
"modifierchecksum" : "33453c86",
"tx" : [
"070f5b851bf7d22bc8e57c7865c99df880dd6ed736bcd0b6ac4ff2b210b85bcc"
]
}


17:43:26

getblockbynumber 20987


17:43:26

{
"hash" : "c7f5fc288f4132c3bd95f84c9e5546da3fb2ccaf83964a18beded1f4a1142983",
"confirmations" : 1,
"size" : 454,
"height" : 20987,
"version" : 6,
"merkleroot" : "85dd7520f06745ef0a12e43dce2a5d7dec39d1caa65f81a360e9cb93d2dee838",
"mint" : 10.41308300,
"time" : 1435719537,
"nonce" : 0,
"bits" : "1d1fffff",
"difficulty" : 0.03124954,
"blocktrust" : "1",
"chaintrust" : "aa5fe",
"previousblockhash" : "00000001253ce61440d7c5154ed17d6c9583fba4cbc228529d2c8222147ce15c",
"flags" : "proof-of-stake",
"proofhash" : "000074d23e75668dcbe16bc52c7153601b26a6343483b3ecdc323b8d25b9f2ab",
"entropybit" : 1,
"modifier" : "31f3db4c56d8a15e",
"modifierchecksum" : "a9dca7ef",
"tx" : [
"cf602b0d13f1e64aa3c15b493828a0a53a7e18f35c84b8ad2d1db104646b9909",
"424e7546c12a5c9b780ff13f562cc78502f63c03e71984ce7f5f7ef21a4e6a8a"
],
"signature" : "30450221009ef13244e4335169eb9a79394f1100bebdbe61b571f08c321a055c0835030ccc02203 83fe80465407630c02ca28f346522c2ae4aef649d3f6403b059aae0bcc81f32"
}

Notice that at block 20987 it doesn't have the next block hash showing which is the only reason why I was thinking that the hardnoded node was socket closed meaning that any new blocks wouldn't be generated or some shiat like that lol But again I don't know and would leave that to the pro's but why wouldn't it generate the next block hash?

It all makes sence - No working node - no blocks can
be verified - no chain movement - no POW no POS.
But I know so little on coding and chains that I am of
no real help. I'll keep opinions to my self now and let the pros
figure it out. But the 1st thing to check is the node.

IMHO it is line 1162 in main.cpp that rejects new found (POW) blocks. Question is which of the two conditions triggers the error/reject.

Not sure about that strange node, but AFAICS the problem occures before the block even could be broadcasted to other nodes.

Ya it's because new blocks aren't being generated right now which is making me think that it's a connection problem possibly with that hardnoded node in the wallet being closed now and giving the debug.log a socket closed status for that IP address but I'm not 100% sure Cheers

Maybe I am wrong, but the chain is not moving exactly because no blocks are accepted.

If chain is not moving blocks cannot be accepted.

I tried to mine a block to see what happens in debug.log when it rejects it and the last lines I get are:

does that ring any bells for anybody?

Hello Everyone,

Yes I did actually notice that NoobKid mentioned about the closed socket problem and I am currently looking into that as a possibility as to the problem as to why the blocks stopped moving because even one of the other developers who I am currently speaking to also said that they looked through the code and couldn't see a reason as to why all of a sudden the POW/POS stopped on block 20987 like it has.

If that is the problem then I will look immediately for node hosting for the coin to help get things back onto track.

Thanks,
Have a Great Day
EinaiOraCoinDev