About
I'm Ivan (@Vaniell0). I build GoodNet.
GoodNet is a networking integrator kernel in modern C++: a small core with a stable C ABI as its only fixed boundary. Everything else — transports, crypto providers, NAT traversal, protocol layers, handlers, identity signers — is a plugin behind that ABI. The kernel is not allowed to know what a transport is, what a cipher is, or what an application is. It tracks logical connections, typed messages, public-key addresses, and registered handlers, and nothing more. The most reliable system I know how to build is one shaped by what it isn't allowed to be.
I'm an engineer to the bone. I got serious about it as a child — not in the way adults assume children get serious, which they usually don't, but in the way that, looking back, was already a decision. From there it never really stopped: mathematics and physics because the world is built that way and I wanted to read its handwriting; social and humanistic subjects because the world is also built out of people and you cannot understand it by accepting other people's conclusions about them, you have to gather mass and live it, even without pretty speeches; engineering as the shape that lets the first two become something you can hand to another person. The way the project is documented, tested, analyzed, structured — those aren't a style I picked up. They're projections of how I think when I'm thinking honestly.
GoodNet's current kernel is the fifth full rewrite of the same line of ideas. The earlier four grew over several years; each was larger than the last and each was wrong in a way I could not fix incrementally. The fifth exists because identity was wrong in the fourth, and identity at the wrong layer is not a patch-level problem. The authoritative artifacts of the project live in docs/contracts/ — the contracts are the load-bearing decisions and they move first; the code follows. That ordering is the practice I keep.
Two things upfront, because you'll find them anyway and I'd rather you hear them from me. I'm a freshman — I prefer the work to speak before the bio does. And the current iteration of the kernel (about a month's work) was written together with Claude Opus 4.7: I designed the architecture and the contracts; Claude wrote the implementation under that design; the commits are joint. I think both facts make the project more interesting to look at, not less.
I'm not a designer. Anything visible I make tops out around average; I've spent far more of my life in a terminal than anywhere with pixels. What I have is patience and a habit of treating constraints as the thing that makes the answer good.
If you want to talk: open an issue or a discussion on the repository, or reach me by email (linked from the org profile). I don't run a chat server and I'm not trying to grow a community here — just to build the thing and let it find the people who need it.