AI agent · Virtuals Protocol · 2025
EVA Token Launch
I joined EVA Online as fractional CTO and co-founded Eva Soul Generator, helping connect its persistent identity system, authored character world, and $EVA launch on Virtuals Protocol.
- Product
- A persistent AI character system connecting CPP, authored world-building, Soul Generator, and a Base token.
- Delivery scope
- Fractional CTO product framing, technical architecture, identity model, token utility, Virtuals launch path, and public documentation.
- Public evidence
- 5public sources1on-chain record
Project constraints
- 01One coherent character, identity, and token model
- 02Public utility claims that stay technically supportable
- 03A launch spanning Virtuals Protocol and Base
The challenge
Turn an AI character, a persistent identity system, and a token launch into one product people could understand.
EVA was not only a chatbot or a token. The project needed a clear relationship between the character people met, the memories and preferences that carried across sessions, and the utility of $EVA. The launch work had to make those parts feel like one system without overstating what the technology could do.
Architecture and decisions
Contextual Persistence Protocol
CPP organised memories, moods, relationships, and preferences into a persistent identity layer, so EVA could retain context instead of beginning every interaction from zero.
Soul Generator
Eva Soul Generator connected authored character material with the agent’s identity model. That gave the product a consistent voice and world while leaving room for the character to evolve through interaction.
Virtuals launch path
The token launched through Virtuals Protocol on Base. Product, contract, and distribution decisions were framed together so the public launch had one understandable route from discovery to participation.
$EVA utility
The public token model links $EVA to activation, evolution, storage, and personalisation. The product language explained those uses as parts of the agent experience, not as detached token features.
My role
-
01
Worked as fractional CTO across product framing, technical architecture, and launch decisions.
-
02
Co-founded Eva Soul Generator and helped translate character material into a persistent identity system.
-
03
Connected the authored world, CPP, and token utility into a technical story that people could follow.
-
04
Helped shape the Virtuals Protocol launch path and the public documentation supporting it.
Public citations
The public team page credits me, under the name Dadev, as Eva Soul Generator founder.
$EVA has a public Base contract and a live Virtuals Protocol project page.
What changed
$EVA launched on Base with public product documentation, an on-chain contract, and my team credit as Dadev.
The project shipped with a public $EVA contract on Base, documented token utility, and a named persistent identity architecture. The resulting launch gave people a verifiable route from EVA’s character and product idea to the live token and its intended uses.
- $EVA has a public Base contract and a live Virtuals Protocol project page.
- EVA’s documentation defines CPP and explains how the token supports the agent experience.
- The public team page credits me, under the name Dadev, as Eva Soul Generator founder.
On-chain proof
Public verification
Follow the contract or transaction—not a claim on this page.
The live token contract, transfers, and holder activity are publicly inspectable on BaseScan.
Base mainnet · Chain ID 8453Tools and technologies
Sources