35. Web3 Roadmap and Ecosystem Expansion

eBattery’s Web3 roadmap is a phased program that develops the digital investment infrastructure together with physical charging activity. Success is not measured only by publishing smart contracts or creating investment units. Putting the station into operation, verifying its data, disclosing its financial result and applying investor rights are parts of the same development process.

For this reason, the roadmap links legal preparation, technical verification, field operations and the investor experience through shared transition criteria. Each stage produces concrete outputs on which the next stage will rely.

The Web2 platform forms the data and user experience foundation of this development. Information from station discovery, route planning, the community and suitable integrations helps in assessing regional needs. The Web3 layer supports financing suitable projects, representing economic rights and verifiable reporting.

The roadmap’s core approach is to grow a verified operating model in a controlled way. First, end-to-end integrity is built within a single project; then this model is adapted to different stations, partners and countries.

35.1 2027 Web3 Development Target

2027 is the development period in which eBattery aims to advance its licensed station operations and its Web3 investment infrastructure together. This goal covers putting the legal structure, technical components, pilot operation and first investment processes into practice in stages.

The 2027 target is not to be read as meaning that all Web3 modules will open on the same day or be available in all countries at the same time. Services are activated as the acceptance conditions of the relevant stage are met.

The development program consists of four work areas:

Workspace Main output
Legal and corporate readiness Country- and product-based activity structure, contracts and required authorizations
Technical infrastructure Smart accounts, token structure, oracle flows and financial contracts
Physical operation Suitable site, devices, connection and service organization
Investor services Project information, funding, reporting and exercise of rights

These areas progress together. Technical development takes into account the requirements coming from field and legal work; project financing is linked to the actual installation budget and operating plan.

The Web2 app’s global access approach is preserved. The launch of Web3 services is not a prerequisite for the existing driver experience to continue. Users can use eBattery’s Web2 functions without taking part in investment services.

35.2 Licensing and Country-Based Operational Readiness

The first stage is determining through which legal parties and under which authorizations activities will be carried out. Charging operations, the offering of investment rights, secondary transactions, and payment and custody services are assessed separately.

The preparation process is not limited to producing the application documents. The operations, recordkeeping and control capacity needed to sustain the service concerned must also be built.

The key outputs of this phase are as follows:

  • Defining the parties involved in station and investment services.

  • Country-by-country legal assessment of the product and the investment right.

  • Putting in place the required licenses, permits and service provider arrangements.

  • Preparing investor agreements and the project information package.

  • Defining the fund protection, payment and reconciliation structure.

  • Setting up identity and investor eligibility processes.

  • Establishing the data processing and cross-border transfer framework.

  • Preparing complaint, dispute and incident response processes.

Submitting an application and the activity becoming able to operate are tracked as different states. Going into service is assessed against the conditions required by the relevant product and transaction flow.

In the physical development program focused on Türkiye and Europe, a separate operating file is kept for each country. Even though the same technology infrastructure is used, payment methods, investor access and operating responsibilities are structured according to the market concerned.

35.3 Technical Verification and Test Network

In the technical validation phase, the components of the Base-based architecture defined in the previous sections are run together in a test environment.

The station passport, permissioned investment unit, investor identity, Launchpad, fund protection, oracle report acceptance, distribution and secondary exchange components are tested within a single end-to-end transaction model.

The scope of testing is not limited to successful transactions. Missing, delayed, or erroneous data and unauthorized transaction attempts are also evaluated.

Test area Verified behavior
Identity and eligibility An ineligible participant being unable to complete the relevant transaction
Issuance and supply Protecting the total economic right as disclosed
Funding Correctly separating accepted, rejected and refunded amounts
Oracle report Checking for an unauthorized, outdated or duplicate report
Entitlement Accurately recording the shares at the cut-off time
Distribution The same entitlement cannot be used a second time
Secondary swap Units, payment and commission being completed consistently
Recovery Re-establishing account access with the announced authorizations
Outage Continuing pending transactions without losing records or causing duplicate effects

Smart wallet tests cover approval with a passkey, gas sponsorship, limited permissions and device change scenarios. They also check that the transaction summary the user sees matches the content being signed.

Testnet transactions are not presented as real investment or realized revenue. Test balances and representative reports are clearly separated.

Before going into production, independent security reviews, fix checks and verification of the production configuration are completed. Deploying a contract that works correctly in the test environment to production with different administrator addresses or different parameters is a change that must be checked separately.

35.4 Pilot Station and IoT–Oracle Data Flow

The pilot station is the phase in which the digital model is validated under real field conditions. The aim is to show that the chain of records, from physical charging activity to the investor report, works.

The scope of the pilot brings together the station e-ID, device identities, meter data, charging sessions, payment records and maintenance events. This data is passed through verification and reconciliation processes and turned into suitable report packages.

Chainlink-based workflows are tested within the pilot for retrieving source data, checking it and producing the related onchain records. Publishing an oracle report and verifying the physical measurement are kept as separate controls.

The following results are sought in the pilot study:

  • Correct matching of device, meter and session identities.

  • Taking energy measurements in a defined unit and time arrangement.

  • Linking payment and service records.

  • Complete and unique processing of data after an interruption.

  • Reflecting fault and maintenance events in reporting.

  • Verifying the link between the source record and the onchain summary.

  • Documents required for authorized review being accessible.

A pilot station is not evaluated only through a few test sessions created by the technical team. Usage conditions suited to the service model, connection interruptions and operational exceptions are also observed.

Pilot verification and investor funding are not necessarily tied to each other. Technical and operational evidence can be built before the public investment process. This way, the first Launchpad project benefits from processes tested in the field.

35.5 First Launchpad Project

The first Launchpad project is the first end-to-end application of eBattery's financing model opened to investors. This stage requires broader preparation than simply activating the project publishing screen.

Technical, commercial and legal reviews of the project are completed. The financing target, number of investment units, fees, installation plan and economic rights are made consistent with one another.

The first project's information package covers at least the following areas:

  • The station’s scope and e-ID.

  • Regional demand and location assessment.

  • Readiness status of the site and energy connection.

  • Device and installation budget.

  • Separation of gross financing from net project funds.

  • Economic rights of investment units.

  • Operating service fee and reserve policy.

  • Protection of funds and their phased use.

  • Funding failure and refund conditions.

  • Reporting and investor communication structure.

In the sales process, investor eligibility, payment acceptance and unit allocation are managed with separate records. A participation record created before a successful close is not presented as a finalized, freely transferable investment right.

When funding is completed, a 3% primary sale commission is applied on the disclosed calculation base. The net resources remaining for the project and the subsequent stages of use are reported.

The success assessment of the first project is not based only on the amount raised. The clarity of the participation process, payment reconciliation, document quality and the feasibility of the installation plan are also reviewed.

35.6 First Monthly Financial Report and Profit Distribution

The first monthly financial close is the stage where the economic result of the physical operation is linked to investor rights. At this stage, the system is expected not only to publish data but to produce the correct financial result.

The closing process evaluates realized service revenue, collections, expenses, taxes and other obligations, reserve allocations and available cash together.

If the first operating period does not cover a full calendar month, this is shown clearly. The result of a partial period is not presented as full-month performance.

The basic checks are as follows:

  • Attributing revenues to the correct session and period.

  • Supporting expenses with documents and approvals.

  • Separating the accounting result from cash.

  • Correct recording of reserve movements.

  • Preserving the end-of-period entitlement record.

  • Verifying the report version and approval chain.

  • The amount suitable for distribution being backed by funds.

When distributable net profit arises, the relevant pool is funded and entitlements are opened for claiming. The investor's gross share, deductions if any, and the net payment are shown separately. The platform commission on profit distribution is applied as 0%.

The success of this stage does not necessarily depend on making a positive distribution. If no distributable result arises in the first period, calculating zero distribution correctly and reporting it with its reasoning also shows that the financial model works. Artificial profit distributions are not created from sources outside the project to make the system look successful.

35.7 Opening of the Secondary Market

The secondary market allows investment units to be transferred among eligible investors. Opening it requires that, in addition to tokens being technically transferable, trading permissions, the information framework and settlement controls are ready.

At this stage, the following elements are verified together:

  • Availability of the transaction service in the relevant market.

  • Eligibility checks for the buyer and the seller.

  • Unit ownership and transfer authority.

  • The price and duration terms of the sale listing.

  • Settlement integrity between the unit and the payment.

  • Correct application of the 1% secondary sales commission.

  • Separation of profit share rights before and after the cutoff.

  • Correct handling of failed or canceled transactions.

  • Consistency of transaction history and price displays.

The sales screen lets the investor assess the project with up-to-date data. Financial reports, operating status and important project events are linked to the listing information.

Opening a secondary market does not create a continuous buyer or a guaranteed price. Technical transaction capacity and actual market demand are tracked as different indicators.

In the initial period, the service scope is expanded in line with operations and support capacity. As transaction volume grows, settlement success, reconciliation, complaints and market integrity are assessed together.

35.8 White-Label Pilots

White-label pilots verify that eBattery’s infrastructure can be applied in a different partner’s real operation. The goal is not merely to rebrand the interface, but to separate roles, data and service flows reliably.

Each pilot starts with a specific service scope. This scope may consist of station management, e-ID, analytics, oracle reporting or suitable investment workflows. All modules do not need to be opened at the same time.

The pilot evaluation covers the following topics:

Field Verification subject
Integration Compatibility with the partner's devices and systems
Data separation Protecting corporate customer and user records
Authorization management Each party accessing only its own area of responsibility
Service responsibility Open disclosure of support, maintenance and incident response
Financial record Attributing fees and costs to the correct party
Reporting Consistency of partner and investor screens
Exit from the service Data transfer and record continuity

For the white-label pilot to be considered successful, user and project rights must be preserved with the same clarity under the partner's brand. A change of brand does not cause legal parties or fees to become invisible.

Findings from the pilot are carried over into shared product components and country configurations. This creates a service infrastructure that can be reused in a controlled way, instead of separate systems built from scratch for each new customer.

35.9 International Expansion from Türkiye and Europe

Türkiye and Europe are eBattery's first focus regions in the physical station and RWA program. This focus does not change the global-access vision of the Web2 app.

The expansion decision does not rest on a single successful funding campaign. It must be seen that physical operations, data quality, financial reporting and investor services can be sustained together.

New countries and regions are assessed against the following criteria:

  • Verifiable charging need.

  • A suitable site and energy connection.

  • Local operation and maintenance capacity.

  • Applicability of products and investment services.

  • Payment and settlement infrastructure.

  • Data processing and transfer conditions.

  • Project and platform unit economics.

  • User support and language capacity.

Web2 data helps identify candidate regions. However, search density in the app does not by itself make a station installation decision. Site feasibility, existing infrastructure and local conditions are assessed separately.

Expansion can be carried out through different paths, such as adding new stations, integrating with existing operators or white-label partnerships. It is not mandatory to use the same physical ownership and operating model in every market; roles remain clear to the investor.

35.10 Criteria for Transition Between Stages

In eBattery's roadmap, the calendar coordinates the work, while verified readiness determines the move to the next stage.

A common acceptance procedure applies for moving between stages. The next stage is not opened until the basic conditions of legal compliance, security, fund integrity and physical service are met.

Transition Core acceptance criteria
From preparation to technical pilot Defined architecture, data model, tasks and test plan
From testing to limited production Security review, required fixes and production configuration
From site preparation to operation Required permits, connection, technical acceptance and support readiness
From project preparation to Launchpad A suitable legal structure, a verified budget and complete investor information
From financing to use of funds Successful closing and the disclosed release conditions
From operations to distribution Closed report, entitlement, sufficient funds and required approvals
Opening to the secondary market Transaction eligibility, secure swap and up-to-date project information
From pilot to expansion Repeatable operations, sufficient support and a sustainable cost structure

The transition decision is recorded. It becomes traceable which criterion was met through which document, test or operating result.

Acceptance criteria are not relaxed later merely to meet a target date. If a critical deficiency is identified, the scope of the relevant function is narrowed or its launch is held back. This does not mean that the entire Web2 application or independently running services must stop.

Going to production is not the end of the review process. A new device model, country, payment method or significant contract update is put through re-evaluation for the areas it affects.

35.11 Shared Success Indicators for Web2 and Web3

eBattery's shared success indicators measure the relationship between the driver experience and the outcomes for stations and investors. The aim is to understand how the different modules contribute to one another, rather than adding up the size of each into a single number.

On the Web2 side, the benefit to the user is assessed through finding a suitable station, planning the trip and successfully using a supported service. On the Web3 side, project financing, operating performance, data integrity and the application of economic rights are monitored.

Indicator area Example measurements Result assessed
Station discovery Search success, information freshness, reachability along the route The user being able to find the right service
Charging experience Start success, unexpected interruptions, payment accuracy Quality of the physical service
Demand analysis Forecast–actual difference, data coverage Accuracy of regional planning
Project development Preparation, installation and commissioning times Turning financing into service capacity
Data infrastructure Missing record, reconciliation difference, report delay Reliability of information
Financial operations Revenue, cost, reserve adequacy, available cash Sustainability of the project
Investor service Entitlement accuracy, payment success, resolution time Exercising economic rights
Secondary transactions Settlement success, transaction time, realized volume How the transfer mechanism works
White-label Integration time, support load, customer retention Reusability of the service model
Platform economy Cost and contribution per service Economic sustainability of growth

The definition, measurement period and data source of the indicators are preserved. Creating a route to a station on the Map is not counted as a charging session that took place at that station. A Launchpad participation request is not confused with completed funding, nor is a announced distribution confused with an amount actually paid.

Success in Web2 games and loyalty is likewise not necessarily tied to investment sales. EP, XP, Charge Credit and community engagement are not turned into measures that steer users toward investments they do not economically understand.

The shared growth relationship is built on better user data supporting more accurate project selection, better station service supporting user satisfaction, and verifiable operating results supporting investor evaluation. The success of this relationship is measured by the actual results at each stage.

eBattery’s Web3 roadmap thus forms a development program that extends from financing to physical service and from service to investor rights, rather than a one-time token launch. The ecosystem expands to the extent that every link in this chain can be sustained with the same quality and openness.

Search eBattery

Search for a feature, guide or topic.

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