30. Blockchain Architecture and Token Standards
eBattery's blockchain architecture forms a foundation that links the economic and operational records of physical charging infrastructure. Station identity, investment units, investor eligibility, financing transactions and monthly distributions are linked together on this structure.
At the center of the architectural approach is that each digital component fulfills a specific role. The record that identifies the station and the unit that represents the investor's economic right do not serve the same function. The payment asset is separated from the investment right, and the authentication record from the wallet's transaction authority.
eBattery, as the main onchain application layer, Base, for the station passport ERC-721, for the permissioned representation of equal economic rights ERC-3643 approach as its basis. ERC-1155 is an alternative representation standard considered where the needs of different project structures require it. ERC-2981 is treated as a supporting standard that helps report fee information in suitable NFT structures.
These choices define the Web3 development architecture. Using technical standards does not by itself create physical asset ownership, an investment contract or service authorizations. These relationships are established together with the project documents and the operating structure.
30.1 Network Selection and Architecture Principles
For eBattery, choosing a network is not based only on a low transaction fee or a short confirmation time. Long-term economic rights tied to charging infrastructure require continuity, auditability, secure authorization, and maintainability.
The network and application architecture are assessed with the following criteria:
Compliance with smart contract standards.
Account abstraction and smart wallet integration.
Applicability of oracle workflows.
Manageability of transaction fees and data publication costs.
A sufficient finality policy for financial transactions.
Diversity of node, RPC, and indexing infrastructure.
Integration with payment assets and suitable service providers.
Traceability of network upgrades and administrative permissions.
Maturity of development, testing and security review tools.
The architecture, minimum required onchain record follows this principle. Economic rights, transfers, distributions and report integrity references are tracked onchain, while high-volume raw IoT data and personal documents are kept in suitable offchain systems.
This separation preserves the verifiability of important records without making the whole app dependent on blockchain transaction capacity. An onchain transaction is not needed for every event in order to open the map, receive station telemetry or run secure charging operations.
30.2 Base-Based Network Approach
Base is a Layer 2 network running on Ethereum. eBattery positions Base as its main application network, building on its EVM-compatible contract development approach and the ability to use tools from the Ethereum ecosystem.
This choice allows multiple functions belonging to station projects to be linked in a shared execution environment:
Creating station passports.
Issuance and transfer records of investment units.
Investor eligibility checks.
Launchpad funding and closing transactions.
Secondary market swap.
Integrity records of financial reports.
Monthly distribution pools.
Smart wallet transactions.
Bringing the main transactions together on a single network reduces the dependency on cross-network messaging and bridges in the initial architecture. Particularly in sales where the investment unit and the payment asset are in the same execution environment, transaction integrity can be established through suitable swap contracts.
Using Base does not mean that eBattery is operated by Base or Coinbase, that investment projects are approved by these organizations, or that their revenues are guaranteed. The network infrastructure and eBattery’s project and service responsibilities remain separate.
Production contracts are deployed in a controlled manner from versions verified in test environments. Test tokens, test stations and sample financial records are not mixed with production data.
30.3 Relationship with Ethereum for Security and Settlement
A transaction appearing quickly on Base and reaching Ethereum-linked finality are different stages.
Base's official documentation describes pre-confirmation, the L2 block record, the posting of transaction data to Ethereum, and finality on the Ethereum side as separate levels. Withdrawing an asset from Base to Ethereum, in turn, has a different proof and completion process from ordinary transfers within the network.
eBattery reflects this distinction in the user experience and in financial controls:
| Stage | What it means for eBattery |
|---|---|
| Transaction submitted | The request has been sent to the network |
| Pre-approval or first block record | The transaction is visible; the relevant finality policy may not yet be complete |
| Required finality level reached | The transaction has reached a confidence level suitable for its intended use |
| Cross-network exit completed | Where applicable, the relevant bridge and target network conditions have also been met |
The portfolio screen can show the initial record quickly. However, for transactions with economic consequences, such as investment unit allocation, funding close and distribution, appropriate finality conditions are required.
The security relationship established with Ethereum does not eliminate all risks in eBattery contracts. A faulty distribution formula, a wrong admin permission or a poorly designed identity check does not become correct merely because of the Ethereum connection.
For this reason, security is addressed at three levels:
Network securitycovers Base’s execution, data publishing, proof, and settlement mechanisms with Ethereum.
Application security, covers the authorization and economic rules of eBattery contracts.
Source security, covers the accuracy of data coming from physical stations and financial systems.
Network upgrades, proof systems and withdrawal conditions may change over time. eBattery’s finality policy is monitored according to the network version used in production; a fixed period is not presented as an unchanging guarantee for all transaction types.
30.4 Separation of the Station Passport and the Investment Unit
The most important distinction in eBattery’s token architecture is the project’s identity and the right to participate in the project is between.
The station passport defines which physical and operational project is recorded. The investment unit represents the share in which the investor participates in this project's distributable net profit.
| Digital component | What it represents | Basic usage |
|---|---|---|
| Station e-ID | The project’s permanent identity | Linking all records to the shared project |
| Digital station passport | The project's onchain identity representation | Referencing technical and operational history |
| Investment unit | Defined economic participation right | Entitlement and permitted transfer |
| Payment asset | Transaction or distribution fee | Funding, settlement and payment |
| Investor eligibility record | Access conditions for certain transactions | Participation and transfer control |
For example, a station project may have a single passport while there may be thousands of equal investment units belonging to the same project. The passport is not the sum of these units; it is the reference of the project to which the units are linked.
A change in the address that manages the passport does not by itself change investors' economic rights. Likewise, investment units changing hands does not mean that the station passport or the physical equipment has been sold.
This distinction also clarifies the technical scope of the “NFT-based station” description used in earlier sections. While the unique station identity is represented by an NFT, equal economic rights may consist of permissioned, fungible units. It is not required for each investment right to be a separate ERC-721 NFT.
30.5 ERC-721-Based Digital Station Passport
ERC-721 is the standard that enables the representation of distinguishable tokens. The token ID and ownership interface support the recognition of unique records across applications. eBattery uses this structure as the technical basis of the station passport.
Each passport is tied to the e-ID of the relevant station. The primary project registry prevents the creation of an unauthorized or duplicate passport for the same e-ID.
The passport refers to the following records:
Project ID and identifying information.
Current location record and location history.
Relationships between the device, meter and charging outlet.
Relevant business and service documents.
Installation and commissioning history.
Maintenance, device renewal and relocation records.
Financial and operational report references.
The relevant investment unit contract.
Not all of this information needs to be written openly into the NFT metadata file. The passport uses public-appropriate summaries and integrity references to authorized archive records.
ERC-721 alone does not ensure that the passport is non-transferable, that its information is immutable, or that it has a legal link to the physical station. eBattery restricts transfer of the passport through project governance rules. In normal investor trading, the passport is not transferred.
Metadata updates are versioned. Installing a new device or relocating the station does not result in the old history being deleted. While the permanent project identity is preserved, the current physical status is published in connection with previous records.
The passport does not replace an official license. It links license and permit information to records that state the source and validity status.
30.6 Permissioned Investment Rights and ERC-3643
The approach eBattery adopts for equal-rights station investment units is an ERC-3643-based permissioned token structure.
ERC-3643 combines an ERC-20 compatible token interface with identity and compliance components. Through identity records, trusted verifiers and transfer rules, it supports the movement of investment units among eligible recipients. The standard also includes management functions such as pausing, freezing, recovery and authorized transfers.
In eBattery's core model, the economic rights of each station project are represented by a separate contract or an explicitly separated project series. Units carrying equal rights within the same project are interchangeable; units of different stations are not treated as the same economic asset.
The number of units, the starting price and the economic share structure are matched against the project documents. Technical decimal precision does not change the disclosed economic divisibility. A structure presented to the user as 20,000 units does not create a different total of rights because of the sub-units used in the software.
Issuance and total supply controls are tied to financing conditions. The authority to create additional units cannot be used to reduce the rights of existing investors without disclosure.
Choosing ERC-3643 does not mean the standard automatically meets all legal requirements. Which investor is eligible, which transfer will be accepted and in what situation an authorized intervention may be made are defined according to project and country rules.
Exceptional transaction paths in particular are reviewed separately. In the standard, normal transfer, issuance, and forced transfer paths do not have the same control flow. eBattery checks the authorization and eligibility differences of these paths at the application level; it does not assume that all movements pass through a single general control.
30.7 Evaluating ERC-1155 Against Project Structures
ERC-1155 is a standard that can manage multiple token types, and different quantities of those types, within a single contract. Batch transfer functions support processing many token types together.
For eBattery, this structure can be considered in scenarios that require certain project or document series to be managed in a shared contract. For example, a design in which each token ID represents a separate project series is technically possible.
However, having many projects in the same contract does not mean that the revenues, reserves or liabilities of these projects turn into a common pool. Each token ID must be associated with its own e-ID and economic right definition.
ERC-1155 does not by itself provide investor eligibility or permissioned transfer rules. When this standard is used to represent an investment right, the relevant identity, transfer, supply and distribution controls must be applied separately.
For this reason, eBattery’s core permissioned investment model is positioned on ERC-3643. ERC-1155 is considered when it provides a concrete technical or operational benefit in a particular project structure.
The same economic right is not put into circulation twice under different standards. If a standard change or a change of representation is needed, a controlled transition is applied that preserves the integrity of total rights between the old and new records.
30.8 Applying ERC-2981 and Platform Fees
eBattery’s platform fees are rules of the economic model. The NFT standard used does not determine these rates on its own.
ERC-2981 provides an interface for querying the fee amount tied to the sale price and the recipient address in eligible NFTs. The standard does not ensure that all marketplaces make this payment as mandatory. Also, because a transfer does not always mean a sale, a sales commission cannot be calculated by looking only at token movement.
Fee application at eBattery is divided as follows:
| Transaction | Platform model applied | Collection point |
|---|---|---|
| Successful primary sale | %3 | Financing and sale closing |
| Supported secondary sale | %1 | Swap settlement of the sale |
| Monthly profit distribution | 0% platform commission | No additional platform deduction on the distribution account |
| Operating service | Price stated in the project terms | Station operating expenses |
Applying the 1% secondary sale commission for ERC-3643-based investment units does not rely on ERC-2981. The commission is deducted within the money flow of the authorized sale and settlement contract.
Since the ERC-721 passport is not the subject of an ordinary investor sale, the existence of the station passport is not interpreted as meaning that every economic transfer gives rise to an NFT royalty transaction.
A transfer or authorized recovery between the wallets of the same rights holder is not automatically treated as a sale for consideration. The commission is tied to the actual transaction type.
30.9 Payment and Distribution Assets
The investment unit and the payment asset carry separate contracts and separate economic functions. The investment unit represents participation in the project, while the payment asset is used for funding, sales or profit share transfers.
In eBattery's technical payment approach on Base, in suitable countries and under suitable service conditions Native USDC issued by Circle on Base is treated as a priority integration asset. Circle’s official contract directory separately identifies the USDC contract on Base.
This choice does not mean that all projects will be accounted for in dollars or that the same payment method will be used in all countries. The conversion between the project’s accounting currency and the onchain payment asset is carried out according to the exchange rate and reconciliation rules described in the previous section.
Name and symbol are not enough when accepting an asset. The network ID, contract address, issuance structure and technical behavior are verified. A bridged representation carrying the same symbol is not automatically treated as equivalent to the supported native asset.
The following points are taken into account when assessing the payment asset:
The issuer and terms of use.
Redemption and access conditions.
Address restriction and administration authorities, if any.
Market value deviation and liquidity.
Custody and conversion providers.
Upgradeability of the contract.
Transfer fees or special behaviors that change the balance.
A stablecoin is not presented as an unconditional bank deposit or as a risk-free cash equivalent for all users. If a significant problem arises with the supported asset, new transactions may be stopped in a controlled manner; how existing obligations will be fulfilled is managed through a disclosed process.
The investment or distribution asset is also tracked separately from the ETH used for Base network fees. Paymaster sponsorship may simplify this distinction for the user; it does not change the economic nature of the cost.
30.10 Smart Contract Components
eBattery's contract architecture separates duties instead of placing all responsibilities on a single contract. This way, the authority and the effect of a failure of any one component can be limited.
| Component | Core responsibility |
|---|---|
| Project registry system | The link between the station e-ID, the passport and the related agreements |
| Station passport | Onchain representation of the unique project ID |
| Investment unit agreement | Supply, balance and permitted transfer of economic rights |
| Identity and eligibility records | Verification statuses required for the transaction |
| Launchpad contracts | Participation, financing terms and sale close |
| Fund protection components | Use of funds and refund subject to the described conditions |
| Oracle report recipient | Acceptance of reports from authorized workflows |
| Financial report record | Period, version and integrity references |
| Entitlement record component | Determining distribution shares at the period cut-off |
| Distribution agreement | Funding, entitlement and individual payment request |
| Secondary market swap | Coordination of the asset, payment and commission |
| Authorization and version management | Control of admin roles and updates |
The oracle report recipient does not, on its own, have the authority to withdraw funds or create investment units. The other necessary controls between the acceptance of a financial report and the opening of a distribution are preserved.
The distribution component prevents duplicate payments for the same project and period. The entitlement record system also preserves the prior-period cutoff independently of live balance changes.
The period-end snapshot and profit distribution are not automatic outcomes of the token standard used. eBattery carries them out with separate application components. In particular, the effect of transfer, recovery, freeze and correction events on past rights is tested together.
30.11 Identity and Transfer Control
eBattery’s identity and transfer architecture establishes a controlled relationship between the investor’s e-ID and the wallet addresses that can carry out transactions.
Identity documents, proof of residence and similar personal data are not written to the public chain. On the onchain side, the necessary eligibility claims, authorized verifier references and their validity status are used.
Checks are applied in three stages:
Preparing the transaction, the user's access to the relevant project and the expected transaction conditions are assessed.
While the transaction is being executed, valid identity and transfer rules are checked again at the contract level.
After the transaction, changing ownership and the relevant eligibility limits are reconciled with the records.
Controlling a wallet, being verified as an investor and being able to participate in a particular project are separate conditions. Using an ERC-4337 account does not remove these conditions.
The expiry of eligibility information does not erase the investment unit’s economic history. Transfers or new investments may be temporarily restricted; how existing rights and payment obligations are handled is managed according to the relevant rules.
Recovery and forced transfer operations produce a separate record because they may carry different authorities from the normal sales channel. The basis, the authorizing party and the affected rights of the operation can be traced. These operations do not create prior-period profit shares a second time.
30.12 Administrator Permissions and Version Management
Smart contract security requires administrator permissions to be clearly defined. A token standard including a given function does not mean that function must be given to the day-to-day operations team without limits.
eBattery applies a segregation-of-duties and least-privilege approach:
The role that creates the project record cannot withdraw the distribution fund.
The identity verifier does not increase the supply of investment units.
The oracle publisher does not on its own turn the calculated report into an investor payment.
The emergency stop role cannot use its stop authority to move assets to another address.
A contract upgrade is not carried out as an ordinary operational change.
The freezing, recovery, forced transfer, issuance and burning authorities under ERC-3643 are considered especially sensitive. Conditions of use are documented and limited through suitable multi-approval and recording mechanisms.
In the production environment, critical permissions are not concentrated in a single day-to-day operating key. A multi-signature arrangement, secure key storage and role-based access are applied. For updates with a defined waiting period, the change can be reviewed before it takes effect.
An emergency response and a permanent change are separate. In an active security incident, stopping the affected function can be done quickly; changing the economic rules is not done without limit under that same emergency authority.
Version management records the source code, contract address, dependencies used, review results and the reason for the change together. The existence of an audit report does not mean that all subsequent code changes were reviewed within the same scope.
Before an update, the following integrity conditions in particular are verified:
Is the total number of economic rights preserved?
Are user balances being carried over correctly?
Do past-period rights remain accessible?
Do requested amounts become available to request again?
Are transfer and identity restrictions applied across all transaction paths?
Do administrator authorities exceed the disclosed limits?
30.13 Scalability, Transaction Costs and Network Continuity
eBattery's scalability approach is not built on supporting more stations and investors merely by generating more onchain transactions.
Operational telemetry is processed in suitable data systems. On the onchain side, meaningful period summaries, rights records and necessary economic transactions are kept. Batched records and proof structures are used where appropriate.
Distribution contracts are not designed to depend on unbounded loops that send payments to all investors in a single transaction. Flows in which investors can claim their own entitlements, or that are processed in controlled batches, help manage transaction capacity limits.
Base's fee structure includes the L2 execution cost and the L1 cost of publishing data to Ethereum. For this reason, fees depend not only on the complexity of the eBattery contract but also on network conditions. A fixed, unchanging transaction cost is not promised.
Cost management uses pre-transaction estimation, suitable batching, limiting data size and a paymaster budget together. Reporting frequency is balanced between the value provided to the investor and the transaction load.
On the continuity side, different interruptions are handled separately:
| Outage type | Core approach |
|---|---|
| RPC provider issue | Switching to a healthy alternative endpoint |
| Indexing delay | Indicating how current the displayed data is and re-matching with the chain |
| Bundler issue | Supported alternative transaction delivery path |
| Network execution or finality issue | Holding affected financial transactions |
| Oracle outage | Keeping acceptance of new reports under control |
| App access issue | Operating recovery and alternative access procedures |
Using an alternative RPC does not resolve an outage in the network itself. A data access problem and a problem with the chain's block production or finality are not treated as the same incident.
The physical security and local operations of charging stations are designed to keep running independently of blockchain access. Pending onchain records go through deduplication and reconciliation checks once the connection is restored.
30.14 Multi-Network Expansion Policy
eBattery’s starting approach is to keep economic rights and core transactions on Base, which simplifies record integrity. Multi-network support is assessed against a concrete user or business need.
Low fees alone are not enough for expansion to a new network. Smart account support, identity checks, oracle access, payment assets, legal compliance and operational monitoring are evaluated together.
The basic rule of the multi-network design is as follows:
The same economic right should not become spendable independently on more than one network, or receive a distribution more than once for the same period.
For this reason, the following topics are clearly defined in cross-network representation:
Which network is the authoritative master record.
Whether the unit in the source network is locked or burned.
What evidence the representation on the target network was created with.
How the total number of rights is preserved.
How period-end entitlement is determined during the transition.
On which network pending distributions will be claimed.
Fallback process in case of message delay or failure.
How identity and transfer rules are applied on the target network.
Units held in the bridge are not counted as active investment rights on both the source and the target network. A message being resent or arriving in a different order does not produce additional units or a second payment.
Bringing the payment asset from another network and moving the investment right to another network are also separate projects. Giving the user payment access does not necessarily require taking investment units to multiple networks.
A network change or expansion does not alter the project e-ID and the economic contract without explanation. New contracts establish a traceable link with the old records; rights before and after the transition are kept reconciled.
With this architecture, eBattery manages the station's permanent identity, the investor's economic right and payment movements in separate but interconnected components. Base provides the execution environment, the Ethereum connection provides the settlement foundation, and the token standards provide the technical representation of these relationships. The economic meaning and investor rights remain tied to the same project records across all of these layers.
