Protocol mechanics

How M2M powers the decentralized grid

Product walkthrough

Watch how M2M works in practice

Live demo

M2M (Machine to Machine) is software-only, API-driven DePIN middleware on Solana. We connect existing smart chargers via OCPP cloud APIs with connected vehicles through enterprise APIs such as Tesla Fleet API—building the data bridge between physical infrastructure and on-chain settlement. The experience centers on a closed loop: discovery on the map, commitment before energy flows, QR code authentication to prove the driver is at the node, dual-verification oracle reconciliation from cloud telemetry, and USDC settlement with sub-second finality. Together, these stages form the M2M decentralized power loop: API-connected charging infrastructure becomes verifiable, monetizable middleware, while drivers gain trusted access without surrendering custody to a traditional platform.

The dual-verification oracle is central to our settlement model. Real-time energy output from the charger's cloud API is matched against the vehicle's battery intake API. When the data reconciles, Anchor escrow releases USDC instantly. Combined with session-bound QR proof of presence, the protocol minimizes fraud risk and aligns settlement with delivered energy. No custom hardware required—if it has an API, it can join the network.

The decentralized power loop

From listing to payout, each stage reinforces the next: commitment before consumption, cloud telemetry reconciliation before settlement, and sub-second Solana finality so the middleware layer compounds with every successful session.

ev_station

Host lists charger

OCPP cloud API node

lock

Escrow handshake

Solana smart contract

qr_code_scanner

QR authentication

Proof of presence

sync_alt

Oracle reconciliation

Charger cloud + vehicle API

payments

Settlement

After session rules pass

Protocol mechanics

Four integrated stages take a session from map selection to settled USDC. Together they define trust, cloud reconciliation, and economic closure for API-connected charging.

  • 01

    On chain handshake and escrow lock

    The session begins before a single kilowatt is transferred. When a driver selects a listed charger on the M2M map, they start the handshake. Estimated session funds route into Solana Anchor escrow as part of the live V1 flow. The middleware layer establishes predictable terms for hosts and protected funds for drivers—no rent-taking middle operator.

  • 02

    Scan to authenticate (Proof of Presence)

    To deter spoofing, M2M requires Proof of Presence before payment flow continues. Through the dashboard, the charger owner generates a session QR. The driver scans on site and the flow advances after the scan matches this listing. This complements cloud API reconciliation: software intent tied to a real-world location while enterprise telemetry hardens settlement.

  • 03

    Dual-verification oracle and energy delivery

    While energy is delivered, our oracle pulls real-time energy output data from the charger's cloud API (OCPP and compatible backends) and matches it against the vehicle's real-time battery intake API (e.g. Tesla Fleet API). Once the data reconciles, the Solana Anchor escrow instantly releases USDC. No custom hardware required—if it has an API, it can join the network.

  • 04

    Fast settlement and the DePIN loop

    When cloud telemetry matches and session rules pass, escrow completes with sub-second Solana finality at low fees. Transparent attribution flows to hosts while drivers retain custody. This is the economic loop that scales API-connected infrastructure into verifiable DePIN participation.

Join the M2M network

Explore listings, onboard as a host, or read the technical and economic framing in our whitepaper. Questions: info@m2m.energy.

searchFind a Chargermenu_bookRead the Whitepaper