Garos Labs

Principles

What we build, and what we refuse to build.

Seven commitments. Each one is either enforced in a contract or stated in a way you can hold us to.

Tools, not rented services

AI puts the tools to build in anyone's hands. A wallet puts the keys to their money there. Both are the same shift, away from institutions that rent you a service in exchange for control. We build for that shift.

Control stays with the person

Nothing we build holds a person's keys, and nothing we run can take their money out. Money leaves on their signature and on nothing else.

Enforced in code, not promised in text

A promise can be broken. A contract on-chain cannot be talked out of what it does. The contracts we write cannot take a user's money out, and once deployed they do not change.

Bounded power

Software has settings, and someone holds the keys to them. We bound them: every number we can change has a limit frozen in the code, on the user's side, and the limit moves only toward the user. Unbounded control over settings is custody by another name.

Nothing false

What we say about our software is true, or we do not say it. We say what the software does and what we can and cannot do, and we never claim what the code does not support.

Public by default

What runs on-chain is public. We treat that as the point, not a problem: anyone can check it.

What we do not build

Software that can take other people's money. Settings without a bound. Claims the code cannot keep.