Users of the network fall into one of the following two categories:
-
Receiver - those that need electricity
-
Supplier - those that provide electricity
Receiver
Supplier
Any owner or operator of a vehicle or device that will intake electricity. This encompasses any hardware of the vehicle that is used as the point of contact for the intake of electricity.
Most commonly, it will be the piece of hardware on an EV in which a charger is plugged.
As new technology emerges, this can also include devices like the antennae needed for wireless charging or the component used to transfer electricity from a vehicle back to the grid. In the latter case, the grid is considered the receiver.
Any owner or operator of a vehicle or device that will intake electricity. This encompasses any hardware of the vehicle that is used as the point of contact for the intake of electricity.
Most commonly, it will be the piece of hardware on an EV in which a charger is plugged.
As new technology emerges, this can also include devices like the antennae needed for wireless charging or the component used to transfer electricity from a vehicle back to the grid. In the latter case, the grid is considered the receiver.



User Interface
In the early stages of the protocol, the interface will act as a universal application that communicates with all charge point operators that provide open-source APIs to allow interaction and further build upon.
​
The interface will be available on both mobile and desktop platforms, depending on user preference. Within the Charge application, the following functionalities will be available initially:



Application
The interface ecosystem is designed to reduce current complexities within the EV charging industry. This portion of the blockchain framework is structured with a focus on software functionality and follows the communication process outlined by the protocol. It consists of the following:
​

Charge Software Platform
The application programming interface designed to interoperate with existing charging software and will provide access to the Charge network.
The API will be open-source and freely available interoperate with existing charging software.
It will incorporate the Charge to all charge point operators. Once incorporated, the charger will be a designated ChargeSpot within the Charge Network.

Transaction History
A record of all transactions and payment history. It will also include how much energy was transferred along with any rewards earned.

Wallet
The user’s public and private keys will be stored in a software wallet. The wallet will provide an on-ramp for individuals to convert fiat currency into Charge cryptocurrency.
The wallet will provide an easy and simple interface that allows users to interact with the blockchain and future decentralized applications (dApps) built on the network.
​
​

Status
Users can toggle between “Supplier” and “Receiver” status, depending on the intended event, vehicle usage, or type of equipment under operation.

Map
This will provide users a map of all electricity-supplying devices and charging stations operating under the Charge protocol.
Only those considered “Suppliers” will have their location shown. The map will provide information on charging devices such as distance, type, status, and other items useful to EV drivers.
​
​

Vehicle Information
Maintains information related to the user’s vehicle