Aero Community,
I have some reserves regarding the logo. Now that investments are being done to get AM to the outside world, is has to be right on the spot. That logo has something that makes it look unprofessional.
Branding is essential, and yes it is much better to get something done now as opposed to later on down the road.
I just want dev to be decisive and say, "This is the Logo". If it comes from yet another contest fine, but I dont want the community to decide, because its too many opinions. I want his decision to be final, and we all just go with it.
Yes, i can always step in to sort our the cross-talk however its good to have community input however distracting. After all we all have a say/stake in this project.
I say let the contest begin!!
bounty for best logo reward is:-
X.xx k AM <== suggestions on amount for bounty reward out of the community fund???
I have a request for those who wish to participate.
Please provide the original .psd/png as it will make my life easier when it comes to optimized the graphics across the platform client/front-end and for any other promotions which we shall be doing.
Lots of stuff has been done.. to much to note here but in a nutshell:-
More Nodes are almost done/ready for a second batch of DNSSEED nodes to power the platform BC.
NGINX reverse-proxys which will be passing requests and sending responses onto the node server(s) have been setup..
Redis caching layer configured on staging servers and have nice setup working and is blazing fast!
I have finalized the "hardening" of 3 forward facing servers, which match that of the ones already in service. So, im happy they are pretty secure.
I will have this looked at in more depth by some pro's asap before live tests begin and also during test phase.
Maybe more changes need to be made to ensure its all patched up and secure according to latest security threats, which i am not up to speed on as much as I like to be these days, threats change so fast in the security world.
So, I will do what i can but I also have a discussion with some of my old friends and seek advise. Check we are in accordance with OWSAP spec. and do some vuln. testing / analysis.
We have a good distribution of well placed .EU/.US servers to run the blockchain and both the platform and supporting services..
Frontend stuff is being done over the next couple of days and as soon as i wired up the API we good to begin live tests.
Without sounding over excited I'm quietly confidant we will start seeing support type services for the platform popping up can coming online shortly.
There maybe gremlins in the system so please don't push me for a solid release date/time I still have a bit left to do..
Please take this with a pinch of salt, many things can and will crop up which will require() my attention.
It looks like a lots is left to do but really isn't much to it. Its just a matter of doing it. (if that makes sense..)
The plan is to basically mimic my local / staging setup and deploy out of staging.
Get the last parts finished and wire it all up.
3 main release stages, platform, <> support services, client.
Test (closed tests for a few days)
Test performance and monitor.. This may require changes to configs or to bring more servers online.
If when, all good, general.beta (real world tests)
Then the current branch of the Repo will made public.
peer review (Sec. review will be done prior to launch)
Acunetix & OWSAP
https://www.owasp.org/index.php/Web_Application_Security_Testing_Cheat_Sheethttps://www.owasp.org/index.php/HTML5_Security_Cheat_Sheethttps://www.owasp.org/index.php/DOM_based_XSS_Prevention_Cheat_Sheethttps://www.owasp.org/index.php/C-Based_Toolchain_Hardening_Cheat_SheetExcuse me if this all sounds a bit
mono-tone after a sleep I will tidy this post up, and will be happy to answer questions, etc..
Thanks
-Maj