|
Status update
We are now testing the latest 0.1.6c version, which drastically reduces the synchronization time. Once it passes our tests, the version will be released to public.
Also a working version of Windows Crypti node was released to Foundation members for testing on their Windows machines. We are gathering their feedback in order to advance to the public release.
|
|
|
|
I've noticed a similar behaviour. I've tried a couple of full resyncs with no success
Please send us the logs as well. |
|
|
|
The funny thing is -- if I am on my own fork then how am I forging? Doesn't that mean that someone else is sending transactions on the same fork as me? In which case why do I seem to be the only node on that fork and why would anyone's wallet be on it?
A forging node in it's own fork will simply forge all the created blocks, which may or may not have transactions. |
|
|
|
This is getting ridiculous. I've spent countless hours trying to get a working Crypti node, and however many days it is waiting for the next release, then the next release, and so on. And in all this time the longest I've had it working for is a few hours.
I'm sorry to hear you have such issues with Crypti. On the latest 0.1.6b release we have changed the fork recovery mechanism to avoid high RAM usage, and while we have extensively tested it, there still might be some issues pending. Please send me and Boris (crypti) the logs via PM, so we could review them. |
|
|
|
Does Crypti comunity has habbit to PGP sing the releases?  Can i use db from 1.6 for not to download blockchain again? Yes, the db is compatible. Good idea about PGP-signing, we will add it to our ToDo list. |
|
|
|
What is the bug?, more details
A problem with the API that could result in an incorrect operation, and was patched in 0.1.6b. |
|
|
|
|
Important announcement - 0.1.6 is retired
We got a report of a critical issue in 0.1.6, and disabled the 0.1.6 downloads for now.
A new 0.1.6b version will be posted soon.
|
|
|
|
Thanks for the update, but just a friendly suggestion, in the future if there is a delay please let us know about it and the details of it, so as not to keep everyone waiting thinking the release is still on track.
Appreciate the suggestion, we actually do our best to communicate the release plans in advance. Please note that Thursday was only mentioned in relation of Windows Crypti modules delivery to us (rather than the 0.1.6 release), which are still being reviewed and tested. |
|
|
|
@Devs
Any update, we were told 0.1.6 was coming out on Thursday...
The 0.1.6 release was delayed following several issues that we found and fixed during the testing phase, being re-tested now for release. Windows Crypti node in testing as well, will be released after the 0.1.6. |
|
|
|
PLEASE PLEASE make sure the upgrade is well documented for us not so technical linux users. Dont mind reading a document.
Looking forward to v0.1.6
If you use the version directly, you will just need to replace the application files. In Docker case, it also would be just a matter of pulling the latest version, instructions will be posted. We will also check if we can add a section to existing installation document. |
|
|
|
Would there likely be working windows wallet in a weeks time?
We had some pause due to 0.1.6, now switching back to it in order to finalize the Windows compilation issues. On another news, we are intensively interviewing developers now, and looking to hire the first full time help as soon as possible. Our job requirements are pretty specific though, hence its taking some time to find the right people: http://brainstorage.me/jobs/22455(in Russian, however you can easily translate it via Google Translate) If you have any Russian friends who might be the possible candidates - please forward them to this post! |
|
|
|
Its been weeks now we have been waiting for 0.1.6...
To be more exact, 0.1.5b was released about 7 days ago, and while we indeed wanted to release 0.1.6 earlier with the new forging password setting feature, we had unexpected delay due to need to locate and resolve the memory issues, and had to make sure that Crypti will efficiently handle increasingly larger block-chain sizes. |
|
|
|
Look all I am saying is DEV's have a part to play here this is key the client has failed if it cant even sync the block chain. This to me is a critical issue. This on its own can become a FUD storm. DEV's ignoring users with client sync problems. Memory leaks... All well documented here but there isn't even a Q&A for simple troubleshooting steps to help...
I am pretty sure more people are having these issues but when you look at the web client it doesn't show anything is wrong except maybe its not finds blocks to forge any more. Even though it shows the client is forging.
I'm sorry to hear that you had these issues and that we not reacted in a timely fashion, it was due to us being quite busy during the last few days working on the 0.1.6 version and preparing it for testing, hence we checked the forums less often then usual. I do would like to encourage anyone having such critical issue to PM us, as we get automatic notifications via emails. On the positive side, we finally managed to track and resolve the memory leak, and now the 0.1.6 runs fine on a 512MB test node. We moving it to final testing stage to be checked by our QA, and after ensuring all working fine, will release it later this week. |
|
|
|
Anywhere else? Does that mean a different IP or a different MAC address? IP addresses, even for DSL connections change every few weeks. So that is not a wise decision.
As for different MAC addresses: what to do if the computer crashes, breaks or is stolen?
I meant that the users accessed their accounts only through official web wallet, and haven't risking flagging their pass phrase anywhere else (including their own nodes). On another though, it looks as it won't be realistic at all, hence we indeed don't have a good method to provide 2FA at the moment. |
|
|
|
We are looking at some projects as the base, will update once we decided whether we will use them or develop from scratch. |
|
|
|
I would like to see 2FA for wallet and forge. I know we already have 2nd passphrase. But I like the convenience it affords me with other sites. And I think it's a feature that new investors would find they are accustomed to and presents the coin as well rounded and protected investment.
Crypto currency works with digital signatures. Anyone who has the secret key can spend the money. You can give the secret key (encrypted by your password) to a third party and they will ask you for 2FA before you can download encrypted blob from their server (i.e blockchain info wallet), but if you have the secret key on your machine, there can't be any 2FA. We might consider adding the 2FA to our hosted wallet, if there will be enough demand and if people will trust this solution. Of course this will mean users using it will have to make sure they never logged in with their pass phrase anywhere else. |
|
|
|
|
Show Posts
