crypti, node, qora everyone freaking out
Node client works for me perfectly
NODE never had any problem til now
Topic: [XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS - page 243. (Read 804701 times)
October 01, 2014, 09:32:44 AM
Node client works for me perfectly
NODE never had any problem til now
October 01, 2014, 09:14:25 AM
I can assure you that we have been hard at work on the problem. The Proof of Time algo is new territory for a cryptocoin. The one minute block time makes it many times more complicated.
With a 5 or 10 minute block time, there would be enough time for all the nodes to be pinged and one selected for forging, but this would cause a delay in transaction time. Merchants will not stand for a 5 minute confirmation time. It is important for Crypti to maintain the 60 second block time.
As a TEMPORARY measure, to get the network up, the PoT will be modified until a permanent fix can be programmed.
As for the windows wallet..... it was in testing for several days...... I was testing it myself. As stated earlier, there was a problem with some nodes forging lots of blocks, and others not forging any. There was also a problem with constant forking. This is all related to the PoT issue.
We are testing the latest fix now on testnet. Things are progressing. Progress is being made.
With a 5 or 10 minute block time, there would be enough time for all the nodes to be pinged and one selected for forging, but this would cause a delay in transaction time. Merchants will not stand for a 5 minute confirmation time. It is important for Crypti to maintain the 60 second block time.
As a TEMPORARY measure, to get the network up, the PoT will be modified until a permanent fix can be programmed.
As for the windows wallet..... it was in testing for several days...... I was testing it myself. As stated earlier, there was a problem with some nodes forging lots of blocks, and others not forging any. There was also a problem with constant forking. This is all related to the PoT issue.
We are testing the latest fix now on testnet. Things are progressing. Progress is being made.
October 01, 2014, 08:51:31 AM
Same as NAScoin thread.
Slowly dying with promises and apologies.
We all know what will happen.
Slowly dying with promises and apologies.
We all know what will happen.
Yes, it's sad.
I think the price will be under ICO price very soon if these problems are not solved soon.
October 01, 2014, 06:04:02 AM
It would be nice to get some response from Grexx or Syrenity but they are probably working hard to fix issue and will give us update when they have sth. more tangible.
Yes, developers did assess developing time incorrectly but that happens a lot. Those who have ever been involved in any project esspecially this big knows that.
Those who have invested in Crypti probably did aware that its a high risk but also long term investment. The price may go down because of this events but as soon as the devs finish code and launch it, the price will go up. Assuming this time all will be working ok, ofcourse.
Yes, developers did assess developing time incorrectly but that happens a lot. Those who have ever been involved in any project esspecially this big knows that.
Those who have invested in Crypti probably did aware that its a high risk but also long term investment. The price may go down because of this events but as soon as the devs finish code and launch it, the price will go up. Assuming this time all will be working ok, ofcourse.
October 01, 2014, 05:24:46 AM
Same as NAScoin thread.
Slowly dying with promises and apologies.
We all know what will happen.
Slowly dying with promises and apologies.
We all know what will happen.
October 01, 2014, 04:34:49 AM
The temporary fix will have random forging on the blocks for a couple of weeks
Oh! 
And this comes after blaming NODE
October 01, 2014, 04:19:41 AM
Atleast you overcome your competitors (qora, node, nem) who has non responsive developers or just incompetent ones. People there just got tired of waiting. Don't let the same happend here.
Just wondering, when was the last time you checked the NEM thread?
Your view seems a bit out of touch, to say the least.
I wouldn't be bashing other coins at this point. I don't own QORA or NODE, but I do own NEM. NEM's developers have been fully transparent about the whole development process, and have in most cases stuck to their deadlines. With Crypti though, the Windows Wallet has been "around the corner" or "just a few days away" for over a month now, with still no launch in sight.
We keep on going back and forth between statements from the developers. SyRenity just 3 days ago said that the new fix and Windows Wallet launch would be out with 0.1.7 in a few days. Now BitSeed has just told us that a "temporary fix" will be implemented and that the Windows Wallet will now be pushed back another 2 weeks along with the new fix that SyRenity said was just "days away".
What's more is that SyRenity said that the Windows Wallet was close to release and will be released once it passed final testing by their QA developers and the IRC testers. If the Windows Wallet was actually release ready the devs wouldn't wait close to two weeks just to release once the new fix was implemented. If Linux & Mac wallets are being released for the temporary fix, then the Windows wallet would also be released if it was actually close to release quality.
Let's not transform this into a NEM - Crypti fight because that would be a pointless discussion.
I am a stakeholder of both NEM and Crypti and have a good deal of respect for both dev teams.
Just wanted to make sure 5000Bitcoins really knows what he's talking about before he expresses his opinion.
October 01, 2014, 03:24:53 AM
Atleast you overcome your competitors (qora, node, nem) who has non responsive developers or just incompetent ones. People there just got tired of waiting. Don't let the same happend here.
Just wondering, when was the last time you checked the NEM thread?
Your view seems a bit out of touch, to say the least.
I wouldn't be bashing other coins at this point. I don't own QORA or NODE, but I do own NEM. NEM's developers have been fully transparent about the whole development process, and have in most cases stuck to their deadlines. With Crypti though, the Windows Wallet has been "around the corner" or "just a few days away" for over a month now, with still no launch in sight.
We keep on going back and forth between statements from the developers. SyRenity just 3 days ago said that the new fix and Windows Wallet launch would be out with 0.1.7 in a few days. Now BitSeed has just told us that a "temporary fix" will be implemented and that the Windows Wallet will now be pushed back another 2 weeks along with the new fix that SyRenity said was just "days away".
What's more is that SyRenity said that the Windows Wallet was close to release and will be released once it passed final testing by their QA developers and the IRC testers. If the Windows Wallet was actually release ready the devs wouldn't wait close to two weeks just to release once the new fix was implemented. If Linux & Mac wallets are being released for the temporary fix, then the Windows wallet would also be released if it was actually close to release quality.
October 01, 2014, 03:10:24 AM
Atleast you overcome your competitors (qora, node, nem) who has non responsive developers or just incompetent ones. People there just got tired of waiting. Don't let the same happend here.
Just wondering, when was the last time you checked the NEM thread?
Your view seems a bit out of touch, to say the least.
October 01, 2014, 02:48:58 AM
This has priority over custom blockchains and Windows installer, since changes here propagate to everything else downstream.
So to clarify - fixing this will take a couple of weeks, and after that you will start working on the custom blockchains and windows installer. Which will take a couple of weeks.
Atleast you overcome your competitors (qora, node, nem) who has non responsive developers or just incompetent ones. People there just got tired of waiting. Don't let the same happend here.
I'd like to hear Syrenitys input on this when he gets the time considering the 360 he made from this statement. Mostly curious what changed so drastically.
Status update
First of all, I'd like to apologize for us not providing ongoing updates regarding the forging nodes being paused.
This was done as an emergency measure to avoid possible forks with the PoT stability issues that we have discovered, while we are working on a proper solution for them. The intended pause period was expected to be a day at most, however unfortunately re-working the PoT took much more time than planned, thus causing the extended delay.
Thanks the Foundation members who did their best communicating this to the community, while us being focused on the PoT.
The good news is that we done with the Pot re-implementation, and now running private tests before we deploy to testnet for Foundation and IRC members to give it a try. Provided it passes them, we will release the new 0.1.7 version (both Linux and Windows) to the wide circulation.
First of all, I'd like to apologize for us not providing ongoing updates regarding the forging nodes being paused.
This was done as an emergency measure to avoid possible forks with the PoT stability issues that we have discovered, while we are working on a proper solution for them. The intended pause period was expected to be a day at most, however unfortunately re-working the PoT took much more time than planned, thus causing the extended delay.
Thanks the Foundation members who did their best communicating this to the community, while us being focused on the PoT.
The good news is that we done with the Pot re-implementation, and now running private tests before we deploy to testnet for Foundation and IRC members to give it a try. Provided it passes them, we will release the new 0.1.7 version (both Linux and Windows) to the wide circulation.
October 01, 2014, 02:28:12 AM
This has priority over custom blockchains and Windows installer, since changes here propagate to everything else downstream.
October 01, 2014, 02:21:28 AM
The temporary fix will have random forging on the blocks for a couple of weeks while changing the way nodes check in with each other to verify up-time for PoT calculation. It also prunes forks. The change solves network latency issues from the network growing in size so it scales better. It also prevents a node with highest weight from hanging network by subsequently not generating block.
Ok. As to my other questions?
October 01, 2014, 02:00:12 AM
The temporary fix will have random forging on the blocks for a couple of weeks while changing the way nodes check in with each other to verify up-time for PoT calculation. It also prunes forks. The change solves network latency issues from the network growing in size so it scales better. It also prevents a node with highest weight from hanging network by subsequently not generating block.
October 01, 2014, 01:43:36 AM
hope it will be better in nearest future with this coin becose i have some too
October 01, 2014, 01:35:15 AM
We are implementing a temporary fix to restart the network with a permanent solution to fix the forking issue a couple of weeks later. I will be talking some more with the developers now and should have more details later. Thank you everyone for your patience on this matter.
I want to hear where this leaves custom made blockchains; also where it leaves the windows installer.
Also the implications of having network this way; either way I seen you took the route I suggested I would take. Which is good.
Network needs to be up. Some insight on what the temporary fix is would be good too. I'm guessing it's keeping some algos on hold until they've been ironed out?
Don't wait longer on keeping it down now.
Happy I bought at these prices because I believe in you as a solid developer team. Thought I was late to the show but this fud paid off.
New code will see these issues time to time but I think you are taking a responsible path on this which will pay off longterm instead of hurting it.
Now get things running so that we can start to build the infrastructure around it.
Anyway a reply from Syrenity in this matter would be good so nothing gets lost in translation. Thank you.
October 01, 2014, 12:52:03 AM
We are implementing a temporary fix to restart the network with a permanent solution to fix the forking issue a couple of weeks later. I will be talking some more with the developers now and should have more details later. Thank you everyone for your patience on this matter.
October 01, 2014, 12:36:40 AM
Dev run away? 
I don't think they ran away. You can see the escrow funds on the first post. Are they having some technical issues, yes I imagine so. It's not easy starting a project from scratch especially in crypto's. With that said I will be closely monitoring their progress..Regards,
Brian
September 30, 2014, 11:27:32 PM
Dev run away?
September 30, 2014, 03:53:08 PM
i like this communete,calm and mature when im not. when al fix,clean slate and start over build it. 
okay gotcha. September 30, 2014, 03:32:06 PM
crypti, node, qora everyone freaking out
Node client works for me perfectly
Jump to: