Yes. This is a little hard as a first application to set a standard for things like milestones and time limits. I guess 3 months is the maximum. Maybe less can be possible.
Is $6K a “massive” amount? 
In any case, 2 weeks is also way too short. Ethereum, a very “ginormous” project was delayed for more than 6 months and even then the CLI release was like a pre-alpha release.
NEM was delayed 5 months. Don’t think 3 months is unreasonable.
1 Like
I guess it all kind of depends on the project. NEM allows somethings that have not ever been done before which is pretty cool. Some of those might experience long delays. But some people might also be doing regularly things that have been done many times.
LIke say I want to create a NEM bot for notifications to Telegram for Android or iPhone. I want to take a couple weeks to design it and then run a public server. That shouldn’t take 3 weeks for a milestone, no less 3 months.
CryptoApex isn’t like an account watcher though, it is something more serious. I could see how there would be long delays in that project.
I didn’t say they should loose funding. I said that 2 weeks have to be enough time to communicate that a delay is going to happen. If anyone fails to coomunicate that then we should talk about loosing funding.
If they do communicate and can give sensible reasons then all is honky dory.
I think we need to distinguish between missing a milestone and failing to communicate both of which are important topics.
1 Like
sure, communication is important.
yes
After some discussions and feedback a vote has been held by the core committee and Crypto Apex’s application has been approved for 50m from the Community Fund which will be dispersed in 4 milestones of 12.5m at a time as the project progresses.
The milestones’ suggested time frame is as follows.
Milestone 1 = Open website (2 months)
Milestone 2 = Open closed beta (3 months)
Milestone 3 = Open open beta (5 months)
Milestone 4 = Rollout (6 months)
1 Like
Sounds great !
Closed Beta may see some delay though, due to a couple of factors. Main factor is the NCC may be changed to include mosaic. We developed on an NCC without mosaic. This may upset the roll out of our solution.
Otherwise, Engine is near completion. Will keep us all posted.
1 Like
Beta has started via invite from CA members. If you are interested, please contact Niko or Nembit86.
I’m interested to Beta test CA.
Who of you has actually participated in the beta test?
Not yet. partly because of holiday.
To be honest, I don’t know enough about the system/platform/service/…
To be able to test, I would like to know more about it.
What is the system and what is it supposed to do? Now, I don’t know. Where can we find the specifications?
P.S. I might have missed some info in the past…, my fault.
I was never contacted …
@greantea: You need to contact Nembit86 for example.
What is this project all about? And what is the status?
cricket sounds *