34. Security, Audit and Business Continuity

eBattery’s security approach covers the entire service chain, from the physical charging station to the investor’s smart wallet. Electrical safety, device communication, financial records, smart contracts and administrator permissions are different control areas; however, a problem in one can affect the others.

For this reason, security is not reduced to a single audit report or to the blockchain network used. A contract working correctly does not by itself show that the financial data at its source is correct. Likewise, a robust device infrastructure does not prove that project funds are managed correctly. Each layer is protected with controls suited to its own responsibility.

Business continuity likewise does not consist solely of bringing systems back online. After an outage, investor rights, payment records, station history and pending obligations must continue to be maintained correctly.

eBattery’s core security objective is to prevent errors and misuse, limit the impact of incidents that occur, and be able to resume the service with verified records. This section defines the control framework to be applied in the design, production acceptance and operating processes of the Web3 and physical infrastructure program.

34.1 Smart Contract Security and Independent Audits

To the extent that eBattery’s smart contracts manage investment units, project funds and profit distributions, they carry direct economic responsibility. The security review therefore evaluates not only whether the code works, but also whether it correctly implements the rights as described.

The review scope includes the station passport, investment unit, identity records, Launchpad, fund protection, secondary swap, oracle report acceptance, distribution and smart account components. While the components are reviewed one by one, the authorization and data relationships between them are also tested.

Ethereum’s smart contract security guide treats testing and review methods as complementary elements of the security process. Independent auditing is also an important part of this process; on its own, it does not constitute a guarantee of being free of errors.

eBattery's approach to accepting stations into production covers the following work:

  • Code and architecture review.

  • Analyses of authorization and fund movements.

  • Unit, integration and scenario tests.

  • Automated tests with unexpected inputs.

  • Testing the economic integrity conditions.

  • Evaluating formal verification methods for suitable critical components.

  • Independent security review.

  • Resolving findings and re-checking the corrections.

  • Matching the production deployment to the version that was reviewed.

In particular, the following conditions must be preserved:

Security condition Expected result
Total rights integrity No new economic right can be created through an unauthorized transaction
Single payment The same entitlement not being usable more than once
Project separation A project’s funds cannot be consumed by another project’s transaction
Authorized report acceptance An invalid source or version being unable to serve as the basis for a financial transaction
Transfer integrity That the transfer does not duplicate past-period receivables
Fund protection User and project funds cannot be withdrawn through undefined administrator actions

Audit results are valid for a specific code version and scope. A later contract update, the addition of a new module or a significant configuration change is not automatically considered part of the same assessment.

This whitepaper is not a statement that an audit has been completed or a security certificate has been obtained. The review scope and results of versions to be used in production are published together with the relevant deployment records.

34.2 Multisig, Separation of Duties and Timelocks

Concentrating critical system authorities in one person’s everyday-use key creates technical and operational concentration. eBattery separates these authorities by role and uses a multi-signature arrangement for suitable transactions.

A multisig requires a predetermined number of authorized signatures for a transaction to take place. Its security value does not come from the number of signers alone. The keys must also actually be protected under different people, devices and access arrangements.

A setup in which the same person keeps all the keys on the same computer is not considered an independent approval mechanism.

OpenZeppelin’s access control approach explains that role-based permissions, multi-signature management and delayed transactions can be used together. Timelocks allow important administrative operations to be seen before they are executed.

In eBattery, permissions are separated according to the effect of the action:

Scope of authority Control approach
Contract upgrade Multi-approval, review and an appropriate time delay
Critical recipient address change Independent verification and multiple approvals
New issuance or supply change Contractual basis and controlled authorization
Fund release Checking project terms and related evidence
Emergency stop Narrow-scope, fast protective authority
Restart Incident assessment and separate approval
Authentication Access only to the relevant eligibility area

A timelock does not provide the expected protection if the same operation can be performed without delay through another admin path. For this reason, alternative call paths and role assignment authorities are also reviewed.

The emergency stop authority is not combined with the authority to transfer assets to another address or change economic terms. While rapid intervention for protective purposes is possible, permanent changes go through their own approval process.

There are also controlled continuity procedures for key loss, staff changes and signers being unreachable. The signature threshold is assessed so that it both prevents unauthorized transactions and does not needlessly lock the system in the absence of a single person.

34.3 IoT Device and Oracle Security

The reliability of station data depends on protecting the physical source and the systems that carry the data together. A strong oracle infrastructure does not by itself make a device that produces wrong measurements, or whose identity has been compromised, trustworthy.

eBattery’s device security approach covers areas such as identity, configuration, data protection, interface access, software updates and monitoring of security status. These areas provide an assessment framework aligned with the core cybersecurity capabilities defined by NIST for IoT devices.

On the device side, the following checks are applied:

  • Separate credentials for each device.

  • Secure communication and the certificate lifecycle.

  • Restricting unauthorized management interfaces.

  • Software updates whose source and integrity are verified.

  • Separating the field network from other networks.

  • Monitoring physical tampering and unusual behavior.

  • Preserving critical records during a connection outage.

On the Oracle side, source access, workflow version, report signature, period information and reuse controls are applied. A report that does not come from the expected workflow is not accepted just because its format is correct.

Data anomalies are not assessed on the total value alone. A meter reset, time drift, an unusual energy spike or duplicate sessions are each separate reasons for review.

Multiple oracle nodes reading the same source and comparing independent sources are different layers of checking. eBattery compares sources such as device measurements, payment records and financial documents in the appropriate context.

Data from a suspicious device or report source may be separated from the relevant financial calculation until the review is complete. In this case, the data gap is not shown as zero activity or as definite revenue.

34.4 Financial Recording and Distribution Controls

Financial security requires calculating the correct amount before sending money to the correct address. eBattery applies successive control stages, from recording revenue and expenses to the investor payment.

The control process covers the source document, the calculation, the approval, the funding backing and the payment result.

The main checks are as follows:

  • Deduplication of sessions and collections.

  • Attributing revenues to the correct project and period.

  • Preventing duplicate processing of expense documents.

  • Calculating the operating fee in line with the described method.

  • Tracking reserves and actual spending separately.

  • Reconciliation of the accounting result with the cash position.

  • Correct application of the entitlement cutoff.

  • Funding the distribution pool sufficiently.

  • Preventing the same period’s entitlement from being paid again.

The roles that prepare the report, approve it and carry out the fund movement are separated as far as possible. Automation does not remove this separation of duties; permissions granted through software are limited by the same accountability logic.

The following relationship is tracked in the distribution record:

Approved total entitlement = Completed payments + Unpaid valid entitlements + Disclosed adjustments.

This relationship is applied consistently with the tax and deduction records used. Differences between gross entitlement and the net wallet transfer must be explainable.

When a difference arises between the onchain balance and internal reporting, the reason is investigated before a new distribution is opened. The balance shown on screen is not accepted on its own as proof that the funds are available.

34.5 Protection of Project Funds

Project financing, operating cash, the maintenance reserve and the investor distribution pool are sources with different purposes. eBattery sets up record-keeping and authorization controls that prevent these sources from being mixed.

Protecting funds is not completed merely by opening a separate wallet. It must also be defined which party can use which amount, and under what conditions.

In Launchpad financing, the release of funds is tied to disclosed closing and project progress conditions. The documents required for a procurement or installation payment are checked. Changing payment recipients requires separate verification, particularly with regard to fraud and account detail manipulation.

The following principles apply to operating reserves and distribution pools:

  • One project's funds are not used to cover another project's shortfall.

  • Unclaimed investor payments are not counted as platform revenue.

  • Funds are not directed to undisclosed lending, collateral or yield-seeking activities.

  • Technical management authority is not designed as authority to freely withdraw funds.

  • Bank, custody and contract balances are reconciled periodically.

A segregated accounting or wallet structure does not by itself create deposit insurance or protection independent of bankruptcy. Actual legal protection is explained together with the terms of the relevant fund structure and service provider.

If a provider has a service outage or an access problem, it is determined which funds may be affected. Switching to an alternative service does not change the economic nature of the assets or investor receivables without explanation.

34.6 Maintenance Reserve and Device Renewal Plan

Business continuity requires resource planning suited to the lifecycle of physical equipment. eBattery's maintenance and renewal reserve treats this need as part of the project economics.

Planning is based on device age, usage intensity, failure history, warranty terms, spare parts status and expected replacement cost. The reserve target does not rely solely on the assumptions made at initial installation; it is reviewed with actual operating data.

The renewal plan covers the following areas:

  • Periodic maintenance schedule.

  • Expected replacement need for critical parts.

  • Spare parts and service access.

  • Warranty coverage and claim processes.

  • The possibility that device support ends.

  • Expected service interruption during renewal.

  • Estimated cost and resources to be used.

Reserve use is linked to an approved work order or investment decision. After the expenditure, the device’s return to service is verified; payment having been made alone does not mean the maintenance is complete.

The reserve is not assumed to cover all possible costs. In the event of unexpected damage or a cost increase, the need for additional funds is disclosed and the decision process set out in the project terms is applied. Such a need does not automatically result in new investment units being issued or a mandatory additional payment being collected from the investor.

During renewal, the station e-ID is preserved. Old and new equipment records are linked with their dates; measurement and revenue history are not mixed together.

34.7 Site Agreements and the Station Relocation Process

A station’s long-term operating capacity depends not only on the technical life of the device but also on the right to use the site where it is located. For this reason, site agreements are a core component of the business continuity plan.

The following topics are evaluated in site relations:

  • Service life and renewal conditions.

  • Termination and breach provisions.

  • Rent or revenue-sharing method.

  • Vehicle and maintenance team access.

  • Rights and responsibilities regarding the electrical connection.

  • Removal of the devices and restoration of the site to its former condition.

  • A change of property owner or site operator.

  • Insurance and liability for damages.

Linking the investment right to the operating life does not mean that the current site contract will continue indefinitely. Contract end and renewal dates are monitored in advance.

When relocation is needed, the new site is reassessed in terms of demand, energy connection, installation cost and operating conditions. The economic characteristics of the new location are not assumed to be the same as those of the old site.

The relocation plan explains the downtime, transport and installation costs, required permits, and the continuity of investor rights. Material changes to the terms are handled according to the relevant contractual approval process.

A traceable record is created between the last activity at the old site and the first activity at the new site. While the project ID continues, a different economic project is not allowed to be presented under the same ID without explanation.

34.8 Cyber Incident Response and Emergency Shutdown

eBattery's incident response approach is broader than the technical intervention made after an incident occurs. Preparation, detection, assessment, limiting impact, recovery and improvement stages are handled together.

NIST's SP 800-61 Rev. 3 guidance also positions incident response as a process integrated with general cybersecurity risk management. eBattery builds its response plans on this lifecycle approach.

Incidents are classified by the asset and service they affect:

Event type Priority intervention area
Suspected compromise of the admin key Restricting the relevant permissions and key rotation
Faulty oracle report Setting the resource aside and holding the affected financial transactions
Smart contract vulnerability Stopping the affected function and reviewing the impact on funds
Personal data breach Cutting off access, scope analysis and the related notification process
Device or site network breach Putting the device into a safe state and network isolation
Payment provider issue Restricting new transactions and reconciliation
Loss of data integrity Isolating affected records and verified restoration

Emergency stop is a protection mechanism with a defined scope. A problem in one project's oracle record is not designed to needlessly halt the physical service of all stations. On the other hand, if there is an electrical safety risk, the local protection mechanisms of the relevant device take priority.

A halt does not reverse past blockchain transactions and does not erase economic rights that have already arisen. Which transactions are pending, which rights are protected and which users are affected is recorded.

A restart does not rely on the problem merely appearing to have gone away. The fix is verified, the affected funds and records are reconciled, and authorized approval is obtained.

Verified information is shared in incident communication. Legal notifications are carried out according to the relevant deadlines and conditions. Technical details that could make it easier to exploit an active vulnerability are handled within a secure disclosure process.

34.9 Backup, Recovery and Data Availability

Blockchain records are not a backup of all of eBattery’s data needs. Invoices, source IoT records, contract documents, customer support history and much operational information are held in separate systems.

For this reason, the backup strategy is organized according to the layer in which the data resides:

  • Operational databases.

  • Financial records and document archives.

  • Device and station configurations.

  • Oracle workflow versions.

  • Contract source code and deployment records.

  • Authorization and security logs.

  • Indexing data and rebuild tools.

Backups are encrypted, their access is restricted, and shared points of failure with the production environment are reduced. For suitable critical records, tamper-protected copies are used.

Two objectives are defined separately in the recovery plan:

Recovery time objective, states within what time the service is intended to be restored.

Data loss tolerance, determines what time interval of record loss is acceptable.

These targets are not the same for every system. Live charging operations, the investor report archive and the analytics screen may have different priorities. Targets are tied to tested capacity; no claim of unlimited, instant recovery is made for all services.

Having taken a backup is not considered sufficient. Restore tests are verified through record integrity and by bringing the system up in a genuinely working state.

Loss of the keys to an encrypted archive can also lead to data loss. For this reason, the key backup and access recovery arrangement is protected with security controls separate from the data backups.

Indexes that can be rebuilt from the chain are distinguished from documents that exist only in the offchain archive. A report’s hash being on the chain does not make up for the loss of the file itself.

34.10 Management of Operating, Market and Payment Asset Risks

In addition to cybersecurity, eBattery’s risk management also covers the station’s economic and physical conditions. Correctly working software does not eliminate low demand or rising energy costs.

Risks are addressed with different control tools:

Risk area Management approach
Usage and demand Regional analysis, scenario comparison and tracking of actual results
Energy cost Supply terms, tariff tracking and cost visibility
Device performance Maintenance, warranty, spare parts and renewal plan
Site continuity Contract tracking and transfer readiness
Secondary market Price and trading volume transparency, and disclosure of liquidity conditions
Payment provider Authorization, settlement and service continuity check
Payment asset Monitoring the issuer, liquidity, value deviation and transfer restrictions
Network and bridge Limiting supported paths and finality checks

For payment and distribution assets, a name or a price target is not a sufficient trust criterion. The contract address, issuer terms, redemption access and, where applicable, freezing authorities are taken into account.

When a significant value deviation or an access problem occurs in a payment asset, the acceptance of new transactions may be suspended. However, the investor’s receivable is not silently converted into a different asset or a different valuation basis. The transition is carried out through disclosed contract and approval processes.

Insurance is also assessed by its scope. The existence of a policy does not mean that all operating, cyber or revenue losses are covered. Coverages, exclusions, limits and the claims process are described in the project records within the appropriate scope.

Secondary market liquidity is not turned into a guarantee artificially supported by operating reserves. Funds set aside for the station’s service continuity are not used to protect the investment unit price.

34.11 Conflicts of Interest and Related Party Transactions

Because eBattery takes on the roles of operator, technology provider and platform manager together, conflicts of interest need to be managed openly.

A conflict of interest does not only mean a directly improper transaction. A decision that affects platform revenue, project cost and investor outcomes in different ways is also a situation that must be managed.

The key areas are:

  • Determining the eBattery operating service fee.

  • Purchase of goods or services from related companies.

  • Allocation of shared costs across projects.

  • Project selection and visibility on Launchpad.

  • Related-party transactions in the secondary market.

  • Reserve use and equipment renewal decisions.

  • Promotional content about project performance.

In related-party transactions, the scope of the service, the rationale for pricing, and the approval process are recorded. Where appropriate, alternative offers or comparable terms are considered. Not only the lowest price but also the total cost and quality of the service are taken into account.

The principle is that a party who benefits from a decision personally or as an institution does not approve the transaction alone. A related service is not disguised as an ordinary third-party expense.

The distinction is also maintained in promotion and analytics. Paid visibility is not presented as an independent performance ranking. The platform’s revenue expectations are not grounds for altering the realized data or risk disclosures shown to the investor.

Access and transaction policies are applied to prevent significant project information obtained from the inside from being turned into personal trading advantage. Significant information to be disclosed publicly is shared through an appropriate and consistent announcement process.

34.12 Audit Results and Transparent Reporting

In eBattery’s audit approach, different reviews are described with their own scopes. A code audit, a financial review and a physical site inspection do not provide the same assurance.

Review type Core scope
Smart contract audit Code, authorization and transaction logic
Cybersecurity testing Application, network and access security
Financial review Documents, calculation, reconciliation, and reporting
Field and device check Physical installation, measurement and operating conditions
Business continuity test Capacity for outage, restoration and restart

The published review information includes the date, scope, reviewed version, key findings and remediation status. Areas outside the review are also stated.

The word "audited" is not used on its own. It should be clear which component was reviewed, by whom and in which version. The auditor's commercial relationship, or circumstances that could affect the independence of the review, are disclosed appropriately.

Closing a finding does not rely solely on the development team reporting that a fix has been made. Depending on the size of the impact, retesting or independent verification is applied. The conditions for going to production are assessed taking into account the impact of open findings.

Reports prepared after security incidents explain the verified scope of the incident, the affected services, its economic impact, the measures taken and the work to reduce the chance of recurrence. Personal data and details that could create an active vulnerability are protected.

The transparency offered to investors is not limited to sharing positive results. Significant service interruptions, report corrections and security changes are also kept as part of the project history. This way, eBattery's approach to security and continuity can be assessed through the controls applied and verifiable results, in addition to the technologies used.

Search eBattery

Search for a feature, guide or topic.

Starting pointsFinding a charging station →Sample RWA project →Guides and news →