The API is part of the development process, we have chosen to leave it out from the beta, but will be launching it very soon after.

NFC is something that will be a modular upgrade to the platform after the beta release. Using NFC on web applications is quite a new technology and is currently in its infancy. However, this is something we have catered to by using node.js which we believe is the future in cross platform development.

We already have two prototypes for the NFC function.

1. Requires an abstraction layer which runs native on each platform and interfaces via http requests through our web api to conduct NFC payments.

2. NFC built directly into the Gatekeeper with no abstraction layer. This method uses an early NFC js library allowing web apps to interface with NFC hardware.

Both approaches will achieve the desired result, but we are trying to avoid fragmentation of code and at this point the latter solution seems to be a better long term solution.

Our goal is to develop a cross platform system that will utilise what hardware is available. Obviously not all devices have NFC so for the ones that don't, this feature will not be available.

The gate keeper is built ground up to be modular. whilst the use cases for fitbit and other health tracking devices are possible, they're not something we consider viable. However, Smart devices like Apple Watch and Samsung Gear are viable and our platform is able to run on those devices.

The previous 'thread' was actually the same one. We locked it because we don't feel the need to have to respond to what seemed like a professional fud team showing up and working shifts. Mildly speaking is a severe understatement, we would rather not have to defend ourselves and work diligently at our own pace developing and releasing material than spend precious time defending against speculative fud.

The client side AES-256 encryption is written in javascript on the node.js framework. We make use of the Stanford Javascript Crypto Library heavily and the code will be made available at a later date. For the moment, we have spent alot of time writing this so we're not giving this out to the public domain just yet.

Deposit Withdraw can be seen in these set of screenshots http://imgur.com/21yBG3t,tzfj5j8,tFGpZPs,7poXyLB,HJwvjRB,QEyYt37,ybpH6Q3,TBBhVmI#0

2-FA can be seen http://imgur.com/Sj0FJ9X

Good question!

Information Security is an important topic, and we have taken security into account on multiple levels.

Cryptographic encryption from multiple layers starting on the client side using AES-256 encryption which is then transported through SSL to the server. Once on the server side, we operate through a distributed algorithm based on message passing interface that segments the private key amongst our dedicated hardware across multiple secure locations.
These locations are vaulted and guarded 24 hours a day, 365 days a year.

Finally, we have worked diligently in the private sector securing funding in exchange for implementing the GridPay protocol to their internal business accounting ledgers. With the funding received, we have an insurance fund that will jurisdictionally secure the integrity of the wallet. In short, we are able to insure the holding of clients GRID stored on the Gate Keeper in the event of major externalities disrupting our service, or part of our system is breached.

This fund will be an initial undisclosed amount of GRID purchased to fill our insurance fund. The purpose of the beta is to gauge the level of usage on the gate keeper, and give us an indication of how much GRID will be needed for this insurance fund.

Thanks for dropping by!

The neat feature is that the wallet handles encryption security client side, and in addition, doesn't require blockchain download as it is in the cloud. The Gate Keeper also has a vaulted storage system which we will show documentation on in the near future.

Many of the features of having a mobile wallet and merchant API mean that the modularity of the wallet allows for quick set-up of merchant services that wish to accept GRID. As a consumer, the interface through the QR and mobile wallet means that the process is a whole lot easier. Merchants who wish to build their own utilities and back end service products can do so and are really limited by the sky as the API will give them full control of their wallet whether it's a program running a market place selling for GRID, or just a merchant website wishing to accept GRID and manage their money in the cloud.

Furthermore, we have had quite a large interest from the corporate side of our business and have been working on bridging the GridPay protocol with existing account management systems in industry.

To answer your final question, it simply means that as we roll out the modules on Gate Keeper, the cross currency utility will increase. Following our beta release we will be announcing some of the modules that will be added to Gate Keeper which will enable a similar service to coinpayments where GRID can exchanged live for many other leading currencies on the fly, and can be spent anywhere that Bitcoin can be spent.

GridPay have been hard at work and we are pleased to announce our road map as well as reveal our latest product in the works - the Gate Keeper multi-platform node.js web wallet!

The wallet features the following;


- Client Side AES-256 Encryption
- Distributed Cloud BlockChain
- Platform independent design (Mobile, Tablet, PC, MAC)
- Deposit, Withdraw, 2-FA Authentication
- Transaction Records
- Account Value denominated in any currency
- Modular Design


We have been rigorously testing our beta build, and will be releasing a beta for this wallet really soon!
Some screenshots can be found at :

http://imgur.com/Q9aMGhz,W2Uyb9W#0
http://imgur.com/21yBG3t,tzfj5j8,tFGpZPs,7poXyLB,HJwvjRB,QEyYt37,ybpH6Q3,TBBhVmI

Please take a look at our infographic road map to see our other developments in the works!

http://www.gridpay.net/GridPay-Roadmap-Phase-1.pdf