Roadmap updated with descriptions. Let me know what you think.
http://blog.crypti.me/crypti-development-roadmap/
Topic: [XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS - page 301. (Read 804700 times)
September 01, 2014, 03:07:25 PM
September 01, 2014, 02:52:04 PM
Nice to hear that 0.1.6 is coming this week 
September 01, 2014, 02:33:42 PM
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
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.
September 01, 2014, 02:30:13 PM
What's the total number of coins available? Can't see it in the OP.
100M, you can see in coinmarketcap:
http://coinmarketcap.com/currencies/crypti/
September 01, 2014, 02:26:48 PM
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!
September 01, 2014, 02:26:42 PM
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.
I stand correct just feels like weeks... apologies. Week then...
September 01, 2014, 02:25:53 PM
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 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.
Yippy thank you... Yes I accept I did not try DM anyone. Will do that next time.
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
September 01, 2014, 02:23:13 PM
What's the total number of coins available? Can't see it in the OP.
September 01, 2014, 02:19:47 PM
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.
September 01, 2014, 02:13:46 PM
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 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.
September 01, 2014, 02:04:16 PM
So my moan was that dev's should also help keep things running instead of just focusing on new features. Uploading a fresh .db does not even take 5 mins. But to sync from scratch has taken me nearly 2 days.
Its great someone did upload a db to help sync issues. Looking forward to new client as have spent way too much time just trying to get client to work. Even Sys dev's helped users out with issues and provided fixes in a few days.... Its been weeks now we have been waiting for 0.1.6...
Its great someone did upload a db to help sync issues. Looking forward to new client as have spent way too much time just trying to get client to work. Even Sys dev's helped users out with issues and provided fixes in a few days.... Its been weeks now we have been waiting for 0.1.6...
I agree... it's great that someone trustworthy to you uploaded the db... BUT... if the devs had uploaded the db... Crypti would automatically have become vulnerable to a FUD Storm.
...I'd rather wait for 0.1.6...
FUD storm for helping... Sys devs uploaded a peers.dat file when the one in their client installer was causing sync issues... (while they were in the process of fixing the installer) There was no FUD storm.
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.
To me this could just be an elaborate plan for devs to get all the "mining rewards" while we struggle to get things working.... Guess only time will tell.
September 01, 2014, 01:54:03 PM
I'm posting an updated blockchain for anyone that has to start from scratch instead of syncing the whole thing again. This one was copied at 7:22am EST 9/1/2014. I know for me having to sync from scratch takes forever. I've tested this and it does load back up fine and starts syncing again. The initial load up can take some time tho. To make sure it was a clean copy I shutdown my node first after making sure it wasn't in the middle of a write operation then copied it.
The file is about 45mb so I went ahead and zipped it up so the download will be about 16mb.
https://drive.google.com/file/d/0BxcKUsP4qnerTl9TcUFKT2I0Qmc
The file is about 45mb so I went ahead and zipped it up so the download will be about 16mb.
https://drive.google.com/file/d/0BxcKUsP4qnerTl9TcUFKT2I0Qmc
Thanks!
But my nodes are still not able to sync since 1,5 hours
Figured it was worth a try for anyone having issues. Hopefully 0.1.6 will release soon.
Just tried it and works!
Hooray!!!!!!
Pitty that the dev's couldn't even help here!
Here is a check list to help you :-
1. Make sure delete logs.log file and blockchain.db then copy the downloaded one above into your home folder (where the previous block chain was.)
2. Make sure you have port forwarding enabled for port 6040 this is key.
3. takes about 45min to get all going. Easiest way to monitor this is check your CPU usage you will see it increases over 50% when you first kick of the process.
4. The current .db is using about 4.5GB of memory now. So you need to have that amount free. I have 6gb so going to have to increase mine soon. Really hope 1.6 will fix such heavy RAM usage. This coin WILL fail if they cant address this. DEVs take note this has to work in the next release.
Thank you again for posting the DB. IF .1.6 is not out tomorrow will update an updated db tomorrow.
Crypti can only succeed if it has community support. This includes helpful information like this, as well as responding to concerns and questions from new members and investors.
Keep up the good work, canej
thanks... been so frustrating last week trying to get this to work. So can only share what i have learnt.
September 01, 2014, 01:01:43 PM
Pitty that the dev's couldn't even help here!
Such "help" is NOT appreciated in crypto... the devs did the right thing!
...0.1.6 is just around the corner...
This has been a common issue, providing a db for us to sync with from trusted source like the devs would have saved me many days of trying different things.
So my moan was that dev's should also help keep things running instead of just focusing on new features. Uploading a fresh .db does not even take 5 mins. But to sync from scratch has taken me nearly 2 days.
Its great someone did upload a db to help sync issues. Looking forward to new client as have spent way too much time just trying to get client to work. Even Sys dev's helped users out with issues and provided fixes in a few days.... Its been weeks now we have been waiting for 0.1.6...
September 01, 2014, 12:53:25 PM
Yep the community helps each other out while the devs focus on fixes. I know the devs are working hard and they have been doing a great job.
September 01, 2014, 12:44:42 PM
I'm posting an updated blockchain for anyone that has to start from scratch instead of syncing the whole thing again. This one was copied at 7:22am EST 9/1/2014. I know for me having to sync from scratch takes forever. I've tested this and it does load back up fine and starts syncing again. The initial load up can take some time tho. To make sure it was a clean copy I shutdown my node first after making sure it wasn't in the middle of a write operation then copied it.
The file is about 45mb so I went ahead and zipped it up so the download will be about 16mb.
https://drive.google.com/file/d/0BxcKUsP4qnerTl9TcUFKT2I0Qmc
The file is about 45mb so I went ahead and zipped it up so the download will be about 16mb.
https://drive.google.com/file/d/0BxcKUsP4qnerTl9TcUFKT2I0Qmc
Thanks!
But my nodes are still not able to sync since 1,5 hours
Figured it was worth a try for anyone having issues. Hopefully 0.1.6 will release soon.
Just tried it and works!
Hooray!!!!!!
Pitty that the dev's couldn't even help here!
Here is a check list to help you :-
1. Make sure delete logs.log file and blockchain.db then copy the downloaded one above into your home folder (where the previous block chain was.)
2. Make sure you have port forwarding enabled for port 6040 this is key.
3. takes about 45min to get all going. Easiest way to monitor this is check your CPU usage you will see it increases over 50% when you first kick of the process.
4. The current .db is using about 4.5GB of memory now. So you need to have that amount free. I have 6gb so going to have to increase mine soon. Really hope 1.6 will fix such heavy RAM usage. This coin WILL fail if they cant address this. DEVs take note this has to work in the next release.
Thank you again for posting the DB. IF .1.6 is not out tomorrow will update an updated db tomorrow.
Crypti can only succeed if it has community support. This includes helpful information like this, as well as responding to concerns and questions from new members and investors.
Keep up the good work, canej
September 01, 2014, 12:40:33 PM
Pitty that the dev's couldn't even help here!
Such "help" is NOT appreciated in crypto... the devs did the right thing!
...0.1.6 is just around the corner...
@Devs
Any update on 0.1.6?
September 01, 2014, 11:58:28 AM
I'm posting an updated blockchain for anyone that has to start from scratch instead of syncing the whole thing again. This one was copied at 7:22am EST 9/1/2014. I know for me having to sync from scratch takes forever. I've tested this and it does load back up fine and starts syncing again. The initial load up can take some time tho. To make sure it was a clean copy I shutdown my node first after making sure it wasn't in the middle of a write operation then copied it.
The file is about 45mb so I went ahead and zipped it up so the download will be about 16mb.
https://drive.google.com/file/d/0BxcKUsP4qnerTl9TcUFKT2I0Qmc
The file is about 45mb so I went ahead and zipped it up so the download will be about 16mb.
https://drive.google.com/file/d/0BxcKUsP4qnerTl9TcUFKT2I0Qmc
Thanks!
But my nodes are still not able to sync since 1,5 hours
Figured it was worth a try for anyone having issues. Hopefully 0.1.6 will release soon.
Just tried it and works!
Hooray!!!!!!
Pitty that the dev's couldn't even help here!
Here is a check list to help you :-
1. Make sure delete logs.log file and blockchain.db then copy the downloaded one above into your home folder (where the previous block chain was.)
2. Make sure you have port forwarding enabled for port 6040 this is key.
3. takes about 45min to get all going. Easiest way to monitor this is check your CPU usage you will see it increases over 50% when you first kick of the process.
4. The current .db is using about 4.5GB of memory now. So you need to have that amount free. I have 6gb so going to have to increase mine soon. Really hope 1.6 will fix such heavy RAM usage. This coin WILL fail if they cant address this. DEVs take note this has to work in the next release.
Thank you again for posting the DB. IF .1.6 is not out tomorrow will update an updated db tomorrow.
September 01, 2014, 11:43:19 AM
Looks like Crypti is going to be added to Mintpal v2. Would definitely be great news if the windows wallet was out by then. TY Crypti Dev.
September 01, 2014, 10:49:02 AM
I sent .2 BTC from Coinbase to Cryptsy yesterday, ( 1 months worth of faucet BTC) and after 10 hours it still did not show. Now this AM, I see this on Cryptsy:
Deposits delayed
Due to a failure we are bringing an older wallet back online and it is affecting deposits for users with an address in that wallet. If you want more rapid transactions then generating a new address should help the issue. We know this is not a long term solution and are working to reinstate addresses from the other wallet as rapidly as possible.
Yeah I saw that yesterday. Strange thing is that I sent .1 to cryptsy from my BTC wallet and it went through in no time flat. so, it may be an exchange issue.Deposits delayed
Due to a failure we are bringing an older wallet back online and it is affecting deposits for users with an address in that wallet. If you want more rapid transactions then generating a new address should help the issue. We know this is not a long term solution and are working to reinstate addresses from the other wallet as rapidly as possible.
informer
I checked the blockchain while waiting for it to go thru... took 12 hours to get 90 confirms. Usually i see the BTC at Cryptsy after 70 confirms.
September 01, 2014, 10:33:49 AM
I sent .2 BTC from Coinbase to Cryptsy yesterday, ( 1 months worth of faucet BTC) and after 10 hours it still did not show. Now this AM, I see this on Cryptsy:
Deposits delayed
Due to a failure we are bringing an older wallet back online and it is affecting deposits for users with an address in that wallet. If you want more rapid transactions then generating a new address should help the issue. We know this is not a long term solution and are working to reinstate addresses from the other wallet as rapidly as possible.
Yeah I saw that yesterday. Strange thing is that I sent .1 to cryptsy from my BTC wallet and it went through in no time flat. so, it may be an exchange issue.Deposits delayed
Due to a failure we are bringing an older wallet back online and it is affecting deposits for users with an address in that wallet. If you want more rapid transactions then generating a new address should help the issue. We know this is not a long term solution and are working to reinstate addresses from the other wallet as rapidly as possible.
informer
Jump to: