Latest posts of: jefffree

Show Posts
Pages: [1]

on: December 13, 2018, 10:49:00 PM

Wallet not cyncing. No Cli-wallet and no GUI-wallet. It is no good.

on: February 21, 2018, 09:41:57 AM

Quote from: air133 on February 21, 2018, 06:30:53 AM is there information and what is the time frame for solving the problem? ""Hi Guys, we are really close to a solution and making an official statement, please bare with us just a little bit longer.""

on: February 20, 2018, 06:43:18 AM

I stopped mining and I will not run the daemon in order not to create additional difficulties for developers.

on: February 19, 2018, 06:02:02 PM

Quote from: kepas on February 19, 2018, 05:47:43 PM Quote from: jefffree on February 19, 2018, 04:52:25 PM I have a question. kreditx.npool. - 45kH krx.luckypool. - 20kH http: //krx.cryptonight.today - 0kH http://pool.mineallcrypto.com - 0kH kreditx.ga --- broken network - 525kH where 460kH? other pools? solo mining? this is just an incorrect display of nethash because the algorithm is not configured correctly, there is no any 460kH... the same with difficulty - the algorithm is not configured and it does not correspond to nethash. as you can see, the difficulty remained and the block time is increased in proportion to the current difficulty... after a while, it will drops Thank you. I will wait and hope. Network hash rate and difficulty are falling very, very slowly. If almost no one goes away it will take many days, since the blocks are rare.

on: February 19, 2018, 04:52:25 PM

I have a question. kreditx.npool. - 45kH krx.luckypool. - 20kH http: //krx.cryptonight.today - 0kH http://pool.mineallcrypto.com - 0kH kreditx.ga --- broken network - 525kH where 460kH? other pools? solo mining?

on: February 19, 2018, 07:18:57 AM

Hello developers! I suggest publishing the essence of the problem so that everyone can suggest a solution. And you could use these ideas. I'm a very bad specialist, but I suggest. It is necessary to stop mining on all pools and stop transactions on the network, then you need to fix the error in the database and put on all the pools a new version of the database in the mode read-only. And wait some time. May be anybody suggest one better.

on: February 18, 2018, 07:53:57 PM

It's only a workaround not a fix, just to see if mining is going the right way.

on: February 18, 2018, 07:16:42 PM

From discord: COPY from vlugvlug,thanks him How to manual update your local blockchain: exit kreditXd exit simplewallet Download the following files very fast after eachother, they have to be the same age. download: kreditx.npool.pw/files/blockindexes.dat download: kreditx.npool.pw/files/blocks.dat Open in file explorer address bar: %appdata% Open kreditX folder Put the just downloaded files into that folder. Overwriting the excisting ones. start kreditXd it will now update to the moment of download, if it closes with an error you have to download the files quicker. start simplewallet you'll now see al the transactions to your wallet until a few moments ago. I can see my balance again! Download the following files very fast after eachother, they have to be the same age. download: kreditx.npool.pw/files/blockindexes.dat download: kreditx.npool.pw/files/blocks.dat This works but needs to be done constantly, atl east the coins will enter your wallet this way. We are working hard to find the issue.

on: February 18, 2018, 05:06:40 PM

when i find why its showing old bc height, i found that daemon is throwing following errors 11:48:29.249448 INFO Failed to check ring signature for tx <e9f4f9f3587f33663109bd4e44cc545f1fa06cf339ecad4b5ef64eaa6c3a9591> i11:48:29.452031 INFO Failed to check ring signature for tx <e9f4f9f3587f33663109bd4e44cc545f1fa06cf339ecad4b5ef64eaa6c3a9591> 11:48:29.452191 INFO Block <52d99ec4351a7716ba184c25cba375433501c3d96c4ccb3cc36224c9b9bda1fa> has at least one transaction with wrong inputs: <e9f4f9f3587f33663109bd4e44cc545f1fa06cf339ecad4b5ef64eaa6c3a9591> 11:48:29.455983 INFO Failed to check ring signature for tx <e9f4f9f3587f33663109bd4e44cc545f1fa06cf339ecad4b5ef64eaa6c3a9591> I do RESYNCHRONIZATION database, but problem is not solve. What we will to do now?

Pages: [1]