try:
addnode=23.25.245.218

in your aerome.conf

Still nothing ..

Hi guys,

Apologies for keeping you in the dark...


On another note AeroME is not just a website per se its a combination of several components all of which need to work in sync for the whole system to work.
New node based-Wallet needs to talk to the Backend apis', The backend Api which form the bases of the platform also needs to work on multiple levels Authentication/OAUTH/Single sign on etc. (part of CSRF apis) Then we have the nodes aspect which need to be able to talk to both the wallets and also the server(s) The Nodes also need to manage the additional load of the other chains for the Smart contracts stuff. The elliptical-curve algo used for the HTTPS connections from wallet to nodes and also to platform is a tricky beast but it done.

I have purchased a "bucket load" of server resources. We now own several servers and also here at the office I have bought out of retirement my old boxes which are acting as a partial proxy and load balancing. I have just negotiated another fixed term with my Business grade SLA with my ISP for this project, its on a fat fibre pipe with 2X2 bounded lines with multiple "sticky" static IPv4 and IPv6 ready addresses. The office lab side of things are running inside/ontop of ESXi server which is powered by Win Server 2012 Core. and then nodes are running ontop of Ubuntu and I have one custom image of RHL Enterprise so we now have the technology..

OpenStack based on MEAN.js which we are running Docker containers for really fast & clever reproduction of servers. coupled with puppet/vagrant makes for a mean way to work/ devel.

There are so many individual concerns with rolling this platform out. many of which have been over come I forgot to mention we also have world-class access to transit peers charged by the TB of data TX from multiple geo-locations.
The same goes for DNS systems which is built around this platform, from local side we have very low latency for lookup requests due to the type of infrastructure I have deployed ontop of.  

I have also made a custom HADOOP array which is pretty cool.. I have a bank of SSD storage which is blazing fast and power the caching push/pulls from the client/server.

If i were to break it down like this maybe the scope would be better understood of what I am doing.

Global low-latency network
Blazzing fast caching/storage array(s)
Secure multi-layered peering
Flexible Encryption based on custom modified Encryption algorithms
JSX/Node react based codebase
Documentation to the "eye-balls"
End-to-end secure systems.
and much more.
 
Nothing has stopped in development, testing or my commitments. I aim to please in the nicest possible way! The Aero community have stood by me and as such this is just reinforces my commitment to the community. !

This stuff is very complicated and i dont say that very often 'or' lightly. Many man hours has gone into this to get it this far. Its going to rock.. Smile!

-Edit-

FYI I have had to re-build my workstations over the past few days which is why i have been away from IRC and other areas which I am usually present in. Back online shortly.

same here

but i bet some one understands and know how much work is going into this

Hi guys,

Aerome is on the voting list at C-Cex.com. You can vote here: https://c-cex.com/?id=vote&vc=1

its just hard when a coins gone this long without a release. I know everybodys low, but the attention will come when the platform comes. The updates are nice, and I know dev is working hard, but itd be really nice to get a % of completion... are we 75% to a beta? are we 99% to a beta? I never really know how close we are.

You are most probably right about most of the aspects of this project. The problem is that the release has been postponed twice. It was initially scheduled for February. Then for this month. Currently it is very likely that it will be postponed again. That's the major problem as I see it. Even if you are able to convince investors that the platform is great once it's released, they'll most probably look reluctantly on any future deadlines. It's all about trust in the first place.

I work in tech full time as a developer as well, using alot of the same tech mentioned above. Hadoop, vagrant/docker/puppet, openstack, mean stack (mongo, express, angular, node) etc it all lines up, makes sense to me and seems legit.

Setting up the server deploy and infrastructure alone would be considered a full-time job and could take 2-4 months to complete depending on requirements. They say that the best developers are really equivellant to 3-4 workers, and that's basically how I see majika. He's likely a top-notch dev and seems to be working really hard behind the scenes.

I am a long time investor in Aero and I am really happy to the the project approaching the next phase.

Two month ago I started staking AeroMe with my Raspberry Pi. The wallet is online 24/7 without any issues. I posted a setup guide on the old thread. If anyone is interested to support the AeroMe network here's how to do it:


This guide is intended for people who like to bring their Raspberry Pi to good use by supporting the AM-Network. My own Raspberry Pi Model B+ is currently staking AeroMe.

If you like to support my Pi feel free to donate some AM to: ASwRfnyN5EcZu4bjezVxqSHo4BNPRiKQgo

1.	Get Raspbian
	Get the latest Raspbian version: http://downloads.raspberrypi.org/raspbian_latest. Install the image according to these instructions: http://www.raspberrypi.org/documentation/installation/installing-images/README.md.
2.	Download and build the sources
	Connect to your Pi via SSH. Download all dependencies required to build AeroME: Code: sudo apt-get install build-essential sudo apt-get install libssl-dev sudo apt-get install libdbdev sudo apt-get install libdb-dev sudo apt-get install libboost-all-dev sudo apt-get install libqrencode-dev sudo apt-get install libsnappy-dev Download the latest AeroMe sources: Code: git clone https://github.com/aeromasterdev/am-aerome Build LevelDB: Code: cd am-aerome/src/leveldb make make libmemenv.a Do something else while waiting for compile to finish...  Build AeroMe client (headless): Code: cd .. make -f makefile.unix Do something else while waiting for compile to finish...  That's basically it. You should have compiled a working binary of AeroME client. Executing help will list all available commands: Code: ./aeromed help addmultisigaddress <nrequired> <'["key","key"]'> [account] addredeemscript <redeemScript> [account] backupwallet <destination> checkwallet createrawtransaction [{"txid":txid,"vout":n},...] {address:amount,...} decoderawtransaction <hex string> decodescript <hex string> dumpprivkey <aeromeaddress> ...
3.	Start the daemon and transfer some funds
	Create the config file at: "~/.aerome/aerome.conf" Code: rpcuser=aeromerpc rpcpassword=someRandomGeneratedPasswordString Start the daemon via: Code: ./aeromed --daemon aerome server starting Use command "listreceivedbyaddress" to show your default address Code: ./aeromed listreceivedbyaddress 0 true [     {         "address" : "ASwRfnyN5EcZu4bjezVxqSHo4BNPRiKQgo",         "account" : "",         "amount" : 0,         "confirmations" : 0     } ] After sending some funds, the client will start staking. You can use "getstakinginfo" to check the current status: Code: ./aeromed getstakinginfo {     "enabled" : true,     "staking" : true,     "errors" : "",     "currentblocksize" : 1000,     "currentblocktx" : 0,     "pooledtx" : 0,     "difficulty" : 0.06821837,     "search-interval" : 1,     "weight" : 2809,     "netstakeweight" : 5258795,     "expectedtime" : 112327 }
4.	Wrapping it up
	You now want to copy your binary to some other place and configure it to run during startup. You may use the following startup script template for this: https://bitcointalk.org/?topic=965.0 Just adapt executable, paths and user to your needs.