About
The team
A lean, focused team building a post-quantum L1 in public.
Asentum is built by four people, working in the open. We ship in small loops, publish what we learn in the devlog, and run the chain ourselves alongside a growing set of community validators.
Co-founder of Asentum, leading product direction and core protocol engineering. Builds the chain end-to-end — consensus, the JavaScript-native VM, the operator app, the SDK, and the public devlog. The person at the keyboard most days.
Co-founder of Asentum, leading growth, community, and the token strategy. Bridges the technical work to the broader crypto ecosystem, brings new validators and supporters into the network, and runs the partnerships side of the project.
Builds reference dapps, SDKs, and integrations on top of the Asentum chain, and works directly with external developers shipping on the network. Lives in the developer feedback loop — anything a builder runs into first, Smiles makes sure works.
Runs the operations layer of Asentum — validator coordination, infrastructure, vendor relationships, and the day-to-day execution work that lets the rest of the team focus on shipping. Keeps the wheels on.
How we work
- Public by default. Code is open source. Decisions, incidents, and reversals show up in the devlog. If something breaks on testnet, we write about it.
- Small team, small loops. No layers between the engineer writing the code and the user running the validator. The same person who debugs a consensus issue at 2am also answers the Telegram message about it the next morning.
- No headcount expansion until the product justifies it. Asentum is engineered to run on consumer hardware. The team that builds it is engineered the same way: lean, durable, no fixed-cost panic.
- Community over throughput. Validators and builders are partners, not metrics. We'd rather have 50 engaged operators than 5,000 farmers.