AeroME Community,
This is a minor update to bring you up to speed with current progress. Including some of the issues I have been tackling.
Namely, increase in the "AM" network connection counts and why I have deployed a partial "TRUSTED" node network!- Network Efficiencies
- Top-down security
- High I/O Transaction Speeds
- Separation of concerns
- Modularity
- Changes to the AeroME Repository
Network Efficiencies
The following code snippet contains the output from a a command
./aeromed getinfo command. To emphasize the roll out of the trusted node network I have setup.
aerome@eu-node6:~/bin$ ./aeromed getinfo
{
"version" : "v1.0.0.3: Experimental",
"protocolversion" : 60015,
"walletversion" : 60000,
"balance" : 100.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 93575,
"timeoffset" : -1,
"moneysupply" : 12019967.05104018,
"connections" : 32,
"proxy" : "",
"ip" : "198.XXX.XX.XXX",
"difficulty" : {
"proof-of-work" : 0.00024414,
"proof-of-stake" : 0.03425662
},
"testnet" : false,
"keypoololdest" : 1424305289,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"mininput" : 0.00000000,
"errors" : ""
}
aerome@eu-node6:~/bin$
I have been setting up (and automating) the process of the underlying network structure I have created a dual network via the
-connect=<ip> command for the trusted core of the platform. Unlike the
--addnode=<ip> connect only allows secure connections to trusted nodes (at least in the methods I used to set things up)
Furthermore, The Smart contracts hosts require a trusted node network. However, the marketplace will be "trustless" as will be the client/server connection to the outter ring of the peers network..
Top-Down Security
Without going into detail the
slush codebase (the name of the codebase for my work) which consists of the client codebase and the platform endpoints will be trust-less (decentralized) but inside of/and on top of this part of the network will be a sub-network running the contracts oracles.
Transaction Speed
The client/servers connections makes full use of Elliptical Curve technology.
The standard Ed25519 signatures are elliptic-curve signatures, carefully engineered at several levels of design and implementation to achieve very high speeds without compromising security.
This is part of what makes this network so cool.
Read more about Ed25519 elliptic-curve signatures:-
http://ed25519.cr.yp.to/AM-X IS HUGE unlike so many of the other similar projects (in appearance) to what has been released to date in the crypto community over the past few months.
I will be honest I am still deploying servers left and right and have not stopped and have literally gone days coding "flat-out". Beta of the marketplace is good but bringing all the components together is proving a mini-challenge and is something i am figuring out, as opposed to referencing my wireframes /api documentations.
Another words I am making changes as I go which is going against my initial requirements brief which is another way of saying necessary project scope creep..
Separation of Concerns
Another consideration which you maybe unaware of is lately Node.js now called NWJS has migrated over to version 12.0-Alpha.
This is fork of the node-webkit v10.3x branch and changes the way it manages Buffers/streams using (IO.js/ through2)
IO.js:
https://iojs.org/en/faq.htmlthrough2:
https://github.com/rvagg/through2This has proved to be a pain in the ass as it meant a substantial change to the way I approached coding problems and having to re-do a lot of the "real-time" response aspects of the client application.
This meant having to bump my codebase models and partials up to ECMA-262 (ES6) and a whole host of other dependant modules.
Modularity
I have also making a custom wrapper for NW.JS auto updater feature. So instead of having a "dumb" client AeroME-client will be smart which means it will "call-home" back to base for new features and updates as i roll them out. This will serve to benefit you guys from having to "manually" download updates as they are released, etc. And will all be managed transparently in the background.
I cannot emphasize this strongly enough but I assure you the work being done here, once complete will be a talking point in cryptos for some time to come. I continue to poor my blood, sweet and tears into this project and I can only salute you for standing by me for all this time.
Changes to the AeroME Repository
I have made several commits to the am-aerome master code repo held up on Github and included a couple of /Contrib scripts to help with the process of running MASTER nodes by the community.
Quality of ServiceI have included a QoS (Quality of Service) set of rules to make running a MASTER node much more efficient for end-users networks. And to tame the network bandwidth used for MASTER node operators.
https://github.com/aeromasterdev/am-aerome/blob/master/contrib/qos/tc.shsecure installs and managing your aeromed DaemonsI have also included / updated several sections in the documentation on GitHub on how to properly install/run/manage your aeromed Daemons.
https://github.com/aeromasterdev/am-aerome/tree/master/contrib/initAuthenticationThere is a whole host of other parts of this project I have been working on SSO (Single Sign on) Authentication and OTP/2FA plus managing Tokens etc and a whole host of other things.
ExposureI have also posted the AeroME OP thread over on
https://allcryptotalk.com/AeroME Thread URL:-
https://allcryptotalk.com/index.php/topic/1002-ann-am-aerome-decentralized-marketplace-exchange/altcoincalendar.info:-
https://www.altcoincalendar.info/coins/1364-AM has also received our submission (and is live) -- even though AM has been released this helsp to raise awareness. Plus Search Engines love this kind of user generated content.
KryptoLydin, has also updated the OP page here on BCT And is a very professional job indeed.
We have all been busy with various tasks and as always I will remain active and dedicated to my work and this project!
Thank you all for your time,
Regards,
Majika.
