Develop on the Production Network
Last updated
Last updated
The Production Network is the live network of the Open Charging Network. Services and features should only be used in a production network after performing robust quality assurance environment.
The Energy Web Main Network (mainnet) is the production network of the
The for the main network can be found under the following public key: 0x184aeD70F2aaB0Cd1FC62261C1170560cBfd0776
You can view transactions and the log history for this contract on the Block Explorer If you're unfamiliar with the Block Explorer, you can read more .
Follow the steps outlined in the in order to connect your service to one of the nodes listed below.
The following test OCN production network nodes are currently known to Energy Web Foundation:
eMobilify GmbH with OCN-Identity 0x34F160573b96D3Db5928Ae804D7d99DdD0aF222c
Reach out to eMobilify GmbH via to get connected.
eMobility Easy with OCN-Identity 0x79d2D88A1F668296c96150139366ff507eFeD618
Reach out to eMobility East via to get connected.
Follow the steps outlined in the in order to connect your service to one of the nodes listed above.
For the running of a production node, we advise that a few extra steps are taken. These include configuring HTTPS, enabling message signing, and running against a relational database.
By default message signing is turned on, but it can also be set with ocn.node.signatures=true if it is not.
The default dev properties configuration file only connects to an in-memory database, for ease of quickly testing the OCN Node. When running a Node on the test or production environment, a database should be set up to persist data across restarts. The example application.prod.properties file provided with the OCN Node provides the configuration necessary to use PostgreSQL.
If necessary, the OCN Node can be load balanced. To do so, the nodes operating under the load balancer should have the same configuration:
The operator should also list the load balancer as the domain name using the same private key in the registry listing:
The OCN allows you to have simple, cost-efficient and secure technical connections to other EV charging players like Charge Point Operators and eMobility Service Providers. To run your EV charging service in production, you may need to enter into different legal relationships.
You might want to consider establishing the following agreements when setting up your charging service:
The OCN Node is responsible for your technical connection to other parties on the OCN. If you are not running your own OCN Node, but using the OCN Node of a third party (OCN Node Operator), you might want to sign a Service Level Agreement (SLA) with the OCN Node Operator. The agreement should make sure the OCN Node is hosted properly and has a high uptime.
Engaging with other parties on the Open Charging Network (like charge points or electric vehicles) requires in many cases a formal legal relationship between you and your counter party. An eRoaming Agreement stipulates the terms and conditions for the eRoaming connections between you and your counter party.
You can see all OCN node configuration settings
Running the OCN Node in production mode (by default or with the ocn.node.dev=false) will require HTTPS. On startup in this mode, the OCN Node will look to see if HTTPS is enabled and properly working. If not, the node will shutdown.
We recommend using an and certificate, but other solutions are not discouraged.
This feature allows recipients to verify the integrity of the data they are receiving. When the ocn.node.signatures=true, request senders should include an OCN-Signature header that all entities that the request passes through (i.e. OCN Nodes and the recipient) sign to verify that the data has not been modified without consent. Likewise, for responses, an ”ocn_signature” property should be placed in the JSON response body by the recipient.
Read more about OCN signatures
In some cases an OCN Node will need to modify data (typically to make URLs work for recipients). The signature can be modified by an OCN Node, but they must state the properties that they changed, and sign any new data. More information about message signing and verification can be found