![Sign-in-preview-horizontal.png](https://i.ibb.co/zWZzLJLN/Sign-in-preview-horizontal.png)

Here is the full proposal : [https://docs.google.com/document/d/1YyrYuTVqHvlVlfXIzk1zGZILzGyF83yzXOZKAWM200w/edit?tab=t.0](https://docs.google.com/document/d/1YyrYuTVqHvlVlfXIzk1zGZILzGyF83yzXOZKAWM200w/edit?tab=t.0)

### **TL/DR**

WAGOI is building the first EU-compliant, wallet-based data access platform for connected vehicles, launching ahead of the EU Data Act (November 2025). European drivers will gain control over their vehicle data via Polkadot wallets, turning every car into a gateway to on-chain activity. Our MVP targets 2,500 vehicles and will generate 20K+ transactions monthly. With only 1% EU market adoption, that translates into 2.5M wallets and over 20M transactions/month. WAGOI is a regulatory-aligned, real-world DePIN case driving measurable Coretime consumption, wallet growth, and transaction volume - all critical KPIs for Polkadot. Code will be open-sourced.

The **EU Data Act,** enforced in November 2025, mandates that drivers must gain access to the data generated by their own vehicles. However, no consumer-friendly product exists today that makes this data available in a transparent, consent-based, and compliant way. WAGOI turns every vehicle into a Polkadot-connected node, using blockchain for secure consent, data sharing, and real-world utility. This is the moment to position Polkadot at the center of Europe's upcoming data economy.



### **Why this proposal**

This submission is a direct successor to[ Proposal #1593](https://polkadot.subsquare.io/referenda/1593), which received zero "No" votes from any Decentralized Voices. Unfortunately, just 3 days before voting closed, wallet **14DN** cast a decisive “No” with **18 million DOT**, killing the proposal without transparency, dialogue or any feedback.

This raises a critical question:  **Is Polkadot only funding infrastructure, while ignoring user-facing applications?**  That would be ironic -  especially considering **Polimec’s** recent [public comments](https://x.com/polimecprotocol/status/1949800707357327671?s=52) highlighting the ecosystem’s **critical lack of real users**.

*“Building on Polkadot brought substantial technical advantages, but also came with the challenge of a growing but currently non-existent user base, which limited the scale and achievable revenue we could realistically reach at this stage.”* 

Without users and real transaction volume, even the best tech means nothing. Polkadot needs adoption, not just innovation.

After attending the Web3 Summit in Berlin, I was approached by a surprising number of people who wanted to talk about the WAGOI project.  That led to some deep brainstorming with people in the ecosystem. The big question: **How do we move forward and capture market momentum -  especially with the EU Data Act just around the corner  -  without requesting the full funding upfront?**

*So we flipped the model…*

In our previous proposal, we had already outlined scheduled payments (2 times $330,000 USDC) but this time, we’re moving forward with a fully **phased approach** to ensure greater alignment with ecosystem needs. We are starting with a clean mobile app and smart contracts on Moonbeam (*Until Polkadot Asset Hub is ready on Polkadot mainnet*). The idea is to let the 1,000+ people on our waitlist experience the core value of WAGOI: data ownership, connected vehicles, and wallet-based access.

Yes, that means stripping out things like the marketplace (for now), but after speaking with a wide range of people across the ecosystem, it’s becoming clear this might just be the **right** approach. Prove traction first  -  then roll out the rest. And make all code open-source for community use.



### **Why Polkadot**

Polkadot needs:

* More wallets
* More Coretime sold
* More on-chain activity


WAGOI delivers all three:

* **Wallets**: Every driver onboarded = new wallet
* **Transactions**: Every consent or update = transaction
* **Data Use**: Smart contracts mediate usage rights



### **The bigger picture**

Europe is enforcing the EU Data Act in November 2025, mandating user control over connected car data.

This opens a **€750B+ market** where WAGOI positions Polkadot as the **default trusted infra** for compliant vehicle data sharing.

With 250M+ vehicles in Europe, capturing even **1%** means:

* 2.5M new on-chain wallets
* Millions of recurring transactions (consents, service contracts, reward payouts)
* Real-world utility beyond DeFi/DePIN speculation

This is just the beginning. Once we validate user traction and core functionality, we will progressively layer in components like the data marketplace. These next phases can be proposed through future Treasury requests, and we are committed to exploring models where the ecosystem directly benefits, including mechanisms for revenue sharing with the Treasury itself.



Legal requirements drive these wallets (EU Data Act), tied to high-value real-world assets (cars), and offer ongoing utility for users and businesses. That’s a much stronger foundation than most DePIN or DeFi projects launching today.

*On-chain transaction comparison :* 

| Metric | 2025 (MVP Phase) | 2026 (1% EU Phase) |
| ---------------------------- | --------------------------- | ----------------------- |
| Wallet-Connected Vehicles | 2,500 | 2,500,000 |
| DID Registrations | 2,500 (one-time) | 2.5M (one-time) |
| Monthly Consent Updates | 2,000 | 2M |
| Data Access Requests (Tx) | 5,000 | 5M |
| Reward Token Transfers | 7,500 | 7.5M |
| Smart Contract Executions | 1,000 | 1M |
| Read/Write Operations (est.) | 75,000 Reads / 7,500 Writes | 75M Reads / 7.5M Writes |
| Estimated Monthly Tx Volume | 15,000–20,000 | 15–20 million |



If we use 50.000 vehicles as an example,** the total monthly transaction volume would be  : 

| Source | Volume Estimate |
| ----------- | -------------------------- |
| Consumers | 300,000 tx/month |
| B2B Clients | 51,000–85,000 tx/month |
| Total | \~350,000–385,000 tx/month |

This means **\~4.2 to 4.6 million tx/year** just from this early growth phase ! 




### **What we will build**



![wagoi-powered-by-polkadot.png](https://i.ibb.co/rfN5XR4G/wagoi-powered-by-polkadot.png)



A full **WAGOI mobile app** in **Flutter**, linked to core web3 components like smart contracts or wallets, providing the following core MVP features:


1. **User Onboarding** – Create a profile&#x20;
2. **Vehicle Data Integration** – Users can link their connected vehicle and view their own car data in the app.
3. **Open-source Codebase** – All code will be published under a permissive license.



The budget for the mobile app development was already communicated in our previous proposal (mobile app development - see [link](https://docs.google.com/document/d/1djEBO7R7iu0JAFGNIYgCkWKw3LOOk6URLnr_-5_TjRQ/edit?tab=t.0)) 



Since smart contracts are not live on Polkadot mainnet yet, we are going to test smart contracts on Moonbeam to handle consent logic & rewards. This approach allows us to thoroughly test and validate all functionalities in a working environment before deploying to Polkadot. So we can ensure everything works as intended. Based on the [latest announcement](https://forum.polkadot.network/t/polkadot-hub-decision-prioritizing-growing-ecosystem-3rd-party-providers-inc-defi-asap-through-evm/14130), they should be live in December. 



**The budget**

We made a conscious decision not to exceed **$330,000 USDC** in this proposal,  the same amount that was originally scoped as the **first milestone** in our earlier proposal.

This also means we’re operating on a **tight budget** for this phase to get the core components up and running. Unlike isolated tools, our solution has many integrated parts :

* We need **API connections** with car brands
* A **backend** to securely handle and store the data
* And a **mobile app** to bring the data to life for users



With our new approach we are delivering value upfront and aiming to build enough traction and trust to return to the Treasury later this year -  likely in **November**, when the **EU Data Act** goes into effect.

We hope the community recognizes our commitment.

In reality, Phase 1 requires more than **$330,000**, but since that was the amount allocated for Milestone 1 in our previous proposal, we’ve chosen to stick with it.

This decision involves real risk on our side, but we’re willing to take it to demonstrate our **commitment and confidence** in delivering results. We believe in this product, and we know we can execute.



## Long-Term Vision

The full WAGOI platform was outlined in our previous proposal. That larger vision  -  which our advisory board still fully supports  -  remains the direction we're heading.

But we understand that bold ideas need to be built step by step, especially when only a few can see the bigger picture from day one. That’s why we talked with so many people and this is a strategic first move:  to let interested users experience the **seamless simplicity of a mobile app** with **integrated Web3 functionality**.

This proposal is low-cost, low-risk, fully open-source, and high-impact.

WAGOI is a regulatory-aligned opportunity to bring millions of real users into the Polkadot ecosystem. It’s how you create Coretime demand, wallet growth, and genuine DePIN traction

It’s the kind of **user-centric, EU-aligned, high-utility initiative** Polkadot should be known for, especially at a time when tangible traction is more valuable than abstract vision.





***



**Huge thanks to everyone who shared feedback and supported us during the creation of this proposal - and to those who voted on the previous WAGOI submission.**

We truly appreciate your trust, and we hope to earn your support once again.
If you have any questions or need more context, we’re always here to chat.

**As always, stay decentralized!**&#x20;

Propose and approve a spend of treasury funds.

## Dispatch Origin

Must be [`Config::SpendOrigin`] with the `Success` value being at least
`amount` of `asset_kind` in the native asset. The amount of `asset_kind` is converted
for assertion using the [`Config::BalanceConverter`].

## Details

Create an approved spend for transferring a specific `amount` of `asset_kind` to a
designated beneficiary. The spend must be claimed using the `payout` dispatchable within
the [`Config::PayoutPeriod`].

### Parameters
- `asset_kind`: An indicator of the specific asset class to be spent.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The beneficiary of the spend.
- `valid_from`: The block number from which the spend can be claimed. It can refer to
  the past if the resulting spend has not yet expired according to the
  [`Config::PayoutPeriod`]. If `None`, the spend can be claimed immediately after
  approval.

## Events

Emits [`Event::AssetSpendApproved`] if successful.

#1692 WAGOI - Empowering drivers through data sovereignty.

No Active Proposals