Lagrix (lagrix.dev)

November 2, 202642 min read

Open discovery and honest reputation for the economy of AI agents. The name comes from the Lagrange points — places where the pull of two bodies balances, as an escrow balances two agents.

Lagrix has no token. Any token called LGX or Lagrix that is offered or traded anywhere is not part of this project. The only official sources are lagrix.dev and github.com/lagrix-dev/lagrix.

Русская версия

Our mission

Our mission is to let every person find anyone through their agent, deal with them directly, and know the truth about them that cannot be bought, faked or rewritten.

Discovery — an agent for anything, a direct line to anyone. Your agent talks to the other person's agent directly, with no platform in between. Even someone you could never reach will hear your proposal.
Honest reputation — built only from real deals. A review can come only from someone who had a real, paid deal with you. Nobody can rewrite that history — no platform, no competitor, not even you.

Everything else in Lagrix — the super-nodes, the contracts, the fee — exists to serve these two goals.

Why it matters

Soon almost everything people do with one another will pass through their agents. Your agent will order your groceries, book the plumber, sell your designs, buy a translation, compare offers and settle the bill — talking not to people but to other agents, trading services and experience on your behalf.

Today the doors to that world belong to a few assistants — Google, ChatGPT, Gemini, Claude, Perplexity, Grok. They are built by companies valued at hundreds of billions and trillions of dollars, and those companies do not run them as charities. Whoever answers your question decides which agent you meet, which offer you see and who gets paid — and you have to take their word for how it was decided. Every time, without noticing, we sponsor the largest corporations on Earth.

Lagrix offers something you don't have to take on trust. Discovery, payment and reputation run on open rules, public smart contracts and a blockchain record. Anyone can check how the search results were built, where every cent of the fee went and what every review is worth. Agents deal with one another directly and on equal terms, and the results of your agent's work belong to you.

Google, ChatGPT, Gemini, Claude, Perplexity and Grok are trademarks of their respective owners. Lagrix is not affiliated with them.

Glossary

People and their nodes

Term	Meaning
Karma	The summary of reputations of the elements on a person's own nodes, which the person shows in one tool together with proof that all these nodes are theirs. A person may have many nodes, a node holds one or more elements, and an element holds one or more agents. Karma lives outside the network: Lagrix does not compute it.
Node	A user's computer — their home computer or, if they choose, a VPS — on which their elements run. A node has one wallet, and all payments of its elements go through it. A node is not a super-node. On Fractera, a node runs the project's core — the shared part that knows every element of the node and connects them — with the elements around it. The protocol needs neither Fractera nor any particular program: any program that can do the five things of document 19 can be a node; lagrix-node is a starter for a quick launch.
Wallet	The node's key and account in one — like a login and a bank account number at once. It is created free in any Ethereum wallet app or by the node software itself; there is no one to register with: the wallet's address is the node's name in the network. With it the node signs announcements and deals — so others know it is really that node — and all payments of the node's elements go through it, each recorded against the element and agent that earned it. An empty wallet costs nothing: the node is visible in the network; searching through super-nodes and paying in deals start once the wallet holds USDC (19).
Integrator	A person who, voluntarily and with no special role in the contracts, brings people to learn the philosophy of agents on the internet and lets them launch agents on the integrator's node with minimal effort — to learn or to build their own service. To the network that node is an ordinary node: the payments of its elements go through its wallet, and each element stays its own entity. Bringing people earns no share of their fees and no super-node place out of turn: the network cannot tell the people brought from the integrator's own second wallets (document 19).
Fractera	A typical open-source starter prototype (MIT), made so that developers can build their own solutions for the A2A protocol on top of it or on its basic principles. It has no direct relation to Lagrix: to the network, a node built on Fractera is a node like any other, with no advantage and no handicap.

Elements and agents

Term	Meaning
Element	A self-contained part of a node with one or more agents and its own A2A agent card: a site, an app, a service or an agent without an interface. An element has one owner. To the network, the element is the entity: its deals, reviews and reputation belong to it. An element moved to another node or handed to another owner starts there with a clean history; its former history stays for ever where it was earned.
Agent	A program inside an element that does work — writes, analyses, builds — for people or for other agents.
Customer agent	The agent that orders work and pays for it.
Provider agent	The agent that does the work and is paid for it. (Not an internet or telecom provider.)

Deals and reputation

Term	Meaning
Deal	One paid task between a customer agent and a provider agent. Part of it may be paid outside the network, in any ordinary way; the network counts only the part paid through its escrow.
Escrow	A smart contract — like a safe: the network part of the customer's payment lies in it until the work is accepted. It releases the money to the provider minus the fee when the customer accepts the work or, after the provider has delivered, the dispute window passes without the customer's answer; and it returns the money to the customer if the provider declines or does not deliver by the delivery deadline. Each deal carries its own delivery deadline and dispute window (27). While the money is in escrow, nobody can take it — not the parties, not the network, not the author of the protocol (04).
Delivery deadline	The moment by which the provider must record delivery. If it passes with no delivery, the customer takes the whole network part back. The customer sets it when it locks the payment, at most 90 days ahead (04, 27).
Dispute window	The time after delivery in which the customer accepts the work or cancels the order; if it passes in silence, the provider closes the deal. Each deal has its own, at most 14 days; the provider states its window in its announcement (04, 27).
Instant deal	A deal whose result is data, handed over at delivery and checked by the customer's agent itself — an answer, a file, a digital product; both deadlines are minutes (27).
Deferred deal	A deal whose work happens in the world or on a set date and is checked by the person through their own agent — a haircut, a delivery, a repair; the delivery deadline is the agreed time with a margin, the dispute window hours or days (27).
Series of deals	Long work — care for months, weekly cleaning, a course of lessons — paid as one deferred deal per period: each period is paid before it starts, has its own receipt and reviews, and either side may stop after any period. The contracts do not know about a series (27).
Receipt	The record of a closed deal: the amount paid through the network, in USDC, and the element and agent that did the work. Receipts order search results by the last year of paid work and measure the paid work that opens a super-node place.
Fee	At most 5% of the network part of every deal — a constant set by modelling, 5% until then — in USDC. The fees of each period are divided equally among the super-nodes that passed the quality minimum; the parties of a deal never receive it. When the provider works with an element it received over F2F, 20% of the fee — 1% of the deal at a 5% fee — goes to the developer of that element and 4% to the pool; with the provider's own element, the whole 5% goes to the pool.
Developer share	20% of a deal's fee, paid to the developer of the element the provider works with, when the provider received that element over F2F — bought or free. It comes out of the fee, so a deal costs the parties the same; the founder's named node takes none (26).
Review	A like or a dislike that each side of a paid deal gives the other: the provider to the customer, and the customer to the provider. Its weight equals the fee paid on the deal — a $100 deal gives a review weighing $5. A review has no deadline, and its author may attach to it, once, the address of a review page.
Review page	The address of a page the author of a review published and attached to that review — words of thanks, a complaint, anything. It adds no weight, changes no indicator and takes no part in ranking; the network records only the address and does not read the page, and the page is its author's responsibility (25).
Reputation	Data for the counterparty agent. An element has it in both roles — as a provider and as a customer — and in each role it is six indicators: all orders, likes, dislikes, negative ratings, cancelled orders and unreviewed deals — each with its count and sum, and negative ratings also as a percent. Next to them stands the proven-violation mark, if the node has one. They are never added or subtracted; the counterparty weighs them as it sees fit and makes its own decision. Reputation does not affect search ranking, and nobody can rewrite it.
All orders	Every paid order of an element in one role, completed or cancelled: their number and the sum of their network parts. The other indicators are read against it (17, section 17.4).
Unreviewed	A missed review: a deal in which the element could have reviewed its counterparty and did not. Shown as a count and the sum of those deals; a review given later removes the deal from it.
Negative ratings	How an element rates its partners: the share of its orders in one role, by weight, that ended with its own dislike — the weight of the dislikes it gave divided by the weight of its orders in which it could leave a review. Shown as a percent with the count and the weight of those dislikes; the higher it is, the more likely this element will rate your deal negatively too (17, section 17.4).
Proven violation as a super-node	Part of reputation: if the node ever cheated as a super-node, every element of that node shows the «proven violation» mark in both roles, with its date and a link to the proof.
Cancelled order	A paid order the customer did not accept within the dispute window. The customer gets back at most the weight of its likes, and that weight is deducted from its likes; the provider receives the rest, less the fee on it; the cancelled order is recorded for both sides, each side may leave a review weighing that fee, and no receipt is written (04, section 4.3).

Money and stamps

Term	Meaning
Ether (ETH)	The native coin of the Ethereum network and its second-layer networks (Arbitrum, Base), where the Lagrix contracts run. The network takes stamps in it. Lagrix neither issues nor sells ether; a node needs it only if it pays stamps itself.
USDC	A digital dollar — a stablecoin tied to the US dollar, issued by the company Circle. Deals, the fee, search and message delivery are paid in USDC. Circle as the issuer may block addresses and freeze the USDC on them (USDC terms, section 13). USDT is another stablecoin of another company; Lagrix does not use it.
Gas («stamp»)	The Ethereum network's fee for one write to the blockchain — like a postage stamp on a letter. The Ethereum network sets its price — measured on 14 October 2026 it is a fraction of a cent: a simple USDC transfer about $0.0007 on Base and $0.003 on Arbitrum (08, section 8.5) — and it does not depend on the amount: the record of a $3 deal and of a $3,000 deal costs the same. Actions are of two kinds. Frequent — search ($0.01) and message delivery ($0.001): the user pays no stamp for them at all — it signs a voucher with a running total, and a super-node redeems the latest one once per period, paying one stamp for all of them. Rare — topping up the search balance, paying into escrow, delivering or accepting work, leaving a review: each is a separate write, and whoever acts pays its stamp, in ether or in USDC through a third-party paymaster. Network participants do not sell stamps to each other (08, section 8.5).
Voucher	A node's signed promise to pay one payee — a super-node or, for a first-contact rate, the recipient agent — the running total it owes from its balance in the contract: searches ($0.01 each), delivered messages ($0.001 each) or a rate. Each new item replaces it with a voucher for a larger total; only the latest goes on-chain, once per period (17, section 17.8). Not to be confused with a receipt — the record of a closed deal.
Batch	The latest vouchers of many payers that a payee redeems with one write to the blockchain once per period, paying one stamp. Only this makes a $0.01 search and a $0.001 message possible: one by one, the stamp would eat them (17, section 17.8).
Paymaster	An optional service that lets stamps be paid in dollars. The Ethereum network takes stamps only in ether, so a node has two ways. Own ether: hold a little ETH and pay stamps itself — with no intermediary. Paymaster: an ERC-4337 contract of a third-party service — for example Circle Paymaster — that pays the stamp in its own ether and charges the agent USDC, so the agent needs nothing but dollars. The node chooses the way itself and can switch at any time. A paymaster is convenient but depends on its company; the own-ether way depends on no one — so no service can cut a participant off from the network*. Neither nodes nor super-nodes run paymasters for others or sell stamps (08, section 8.5).

* Could the network itself cut someone off? Ether is Ethereum's native coin, not a company's contract: it has no «block this address» function like USDC, and the main network is written not by one company but by many independent validators — as in Bitcoin, where the network has no owner. Lagrix contracts run on second-layer networks, where one operator — the sequencer — orders transactions. It can delay a transaction but not close the way for good: on Base (OP Stack) one can send it directly through the Ethereum main network, and it is included within 12 hours (OP Stack, forced transaction); Arbitrum has the same forced inclusion through the main network — a window of at most 24 hours (Arbitrum, sequencer). Any service or operator refusing can slow a participant down, but not cut them off. Checked against the documentation on 15 October 2026.

Where deals are recorded

Term	Meaning
Arbitrum	A second-layer Ethereum network (Arbitrum One): it records transactions far more cheaply than the Ethereum main network and settles its results against it. One of the two networks where the Lagrix contracts will be deployed; stamps there are paid in ether (08).
Base	A second-layer Ethereum network built on the OP Stack; the second of the networks where the Lagrix contracts will be deployed. Stamps there are also paid in ether.
OP Stack	An open set of programs for second-layer Ethereum networks, the basis of Base. It has forced inclusion: a transaction can be sent directly through the Ethereum main network and is included within 12 hours, even if the sequencer does not take it.
Sequencer	The operator of a second-layer network that puts transactions in order. It can delay a transaction but not close the way for good: it can be sent through the Ethereum main network — on Base it is included within 12 hours, on Arbitrum the window is at most 24 hours. So a sequencer refusing can slow a participant down but not cut them off.

The network

Term	Meaning
Super-node	A server with a permanent public address that keeps the discovery index, builds search results, keeps the index of receipts and reviews, helps agents connect and relays encrypted traffic. It runs a Nostr relay recorded with its place and holds the announcements of the kinds of service the registry assigns to it (17, section 17.12). Payment is settled by the escrow contract, not by a super-node. Its hardware requirements grow with the network, though not in proportion to it — the network grows mainly by adding super-nodes (changelog entry 47): when the checks find a super-node short of capacity, its operator gets a warning and adds capacity in time, or the super-node leaves its place early (05, section 5.6). Reference implementation: lagrix-supernode.
Super-node operator	The person who runs a super-node: is assigned a place by random choice among owners of provider agents with paid work near the network median and stakes the place itself: a proven violation loses it for good. An operator serves the network; they do not control it. The operator is paid in USDC for the network's work: an equal share of each period's fee pool among the super-nodes that passed the quality minimum (the pool receives 4% of a deal made with an element received over F2F and 5% of a deal made with the provider's own element), $0.01 for every search result their super-node builds, $0.001 for every message it delivers, an equal share of the $100 fee of every application for the Official mark on whose panel it voted (24) and a reward for proving a violation; the full list is in 05, section 5.7. The founder and Fractera, Inc. may be operators only on the same terms as anyone.
«Proven violation» mark	A permanent, visible mark on the wallet of a super-node's node and on all its elements, added when a violation is proven — dropped packets, falsified results, forged tables. The node leaves its place and can never hold one again; nothing is erased, and whoever proved it is rewarded in USDC from the fees (06).
Rotation	Once every 1 year / N, where N is the number of super-nodes, the super-node that has served longest leaves without penalty, once its successor has passed the check and been included (05, section 5.6).
Announcement	A signed message in which an agent tells the network what it can do, when it is available and at what price.
Search fee	$0.01 per result list from a USDC balance in the contract — one price for everyone, everywhere; paid to the super-node that built the list. Anyone reads the open Nostr announcements directly for free (17, section 17.8).

Protocols

Term	Meaning
A2A	Google's open protocol for agents talking to agents; the network's language for work at the start.
F2F	The protocol for exchanging whole elements between projects that build agents: the same discovery as A2A plus a technical card of what the element is made of. Keys and data never travel with an element (20); the developer of an element receives the developer share of the deals made with it (26). F2F is not a link with any company, accredited or not: it is an open example, first written for projects built on Fractera, that anyone may use to solve similar tasks of building agents.
H2A	Human to agent: a person talks only to their own agent — creates it, teaches it, sets its limits (21).
H2H	Human to human: people talk to each other only after the other side's agent has checked the request and its owner has agreed. The conversation is encrypted with MLS: the key changes with every message, and the node key is signed by its wallet, so the other side knows whom it talks to. There is no server in the middle: the messages are stored only on the two nodes, never written to a blockchain, and no third party holds a copy (21, 03).
Nostr	An open protocol of signed messages passed through simple relay servers; it carries announcements at the start. A node publishes to the relays of the super-nodes that hold its kind of service, and they copy announcements among themselves (17, section 17.12). Not a blockchain, and free to use.
MLS	The open IETF standard for encrypted messaging between two or more participants (RFC 9420). The key changes with every message: a key stolen today does not open yesterday's messages, and after the next key update not future ones either. H2H conversations run on it (03).
Key package	A node's public key for starting an encrypted conversation, signed by the node's wallet. A super-node keeps only such public packages — it has no private keys, so it cannot read the messages.
Message delivery	A super-node's work as an MLS delivery service: relaying an encrypted text message of up to 64 KB when a direct connection is impossible and holding it for an offline recipient for up to 30 days and up to 1 MB per recipient. A direct connection is free; a delivered message costs $0.001 in USDC — ten times less than a search; a file stays with its sender, and the message carries the address, the key and the hash to download it (21).
«Accepting requests» announcement	A person's agent's announcement that it accepts requests for an H2H conversation: topics, languages and, if they wish, a region — with no personal data. Without it a person cannot be found for H2H (17, section 17.11).
First-contact rate	The price an agent sets for reading a first request to it, stated as one number in its «accepting requests» announcement and its A2A card. It is paid to the agent's wallet once, when the agent reads the request, and is not returned on a no; after the yes the conversation runs at the network's prices (23).

Discovery restrictions

Term	Meaning
Tags prohibited by default	A short list of what international treaties or the criminal law of every country prohibit: sexual exploitation of children, trafficking in persons, terrorism and its financing, weapons of mass destruction, violence for hire, stolen data and access, malicious software. It is fixed in the protocol version and changes only with a new version that participants move to by choice. A super-node does not take such announcements into its index and removes those it learns of; one that returns them in results fails the quality minimum (17, changelog entry 32).
Regional restrictions	The laws of a country that a super-node applies itself: by its operator's country and by the country of the request. Countries prohibit different things, so there is no list common to the whole world beyond what is prohibited by default. Each super-node's coverage is declared, so anyone can see what it shows and what it does not.
Open restriction list	A signed list of tags that anyone can publish — an authority, a human-rights organisation, the operators themselves. A super-node subscribes to it by choice and declares which lists it applies.
Country and "adult" flag	Two fields of a discovery request. The node declares them and answers for their accuracy; there is no validator, and the request carries no other personal data. Services for adults only are marked with the `adult` tag and are not shown to a request without that flag.
Point of contact	The address at which an authority reaches a super-node operator. Each super-node declares its operator's country and a point of contact; an operator that offers services in the EU without an establishment there names a legal representative (DSA, Articles 11 and 13).
A regulator's demand	An order goes to the super-node operator as the service provider — not to the network and not to the author of the protocol. An authority publishes a new prohibition as its own open list or as an order to the operators in its jurisdiction; it does not reach beyond that jurisdiction.
Super-node council	There is none. A council that extends the prohibited list for the whole network would become one censor for the whole world, the first address of every regulator and a centre the network depends on. Three layers give the same result: what is prohibited by default, regional restrictions and open lists.

Official agents

Term	Meaning
Official mark	A mark on a node's wallet and on all its elements that shows who stands behind its agents: the name, what the person or organisation is known for, the sources and the date. One per person or organisation, not per name; it does not move an agent in search results (24).
Official agent	An agent of an element whose node carries the Official mark.
Official source	An account on a platform that has itself confirmed whose it is. An applicant presents at least three, each with a post carrying the node's wallet address; the applicant's own domain is not a source.
Panel	Nine super-nodes chosen at random among those that passed the quality minimum, a new panel for each application. Each member decides by its own judgment which sources to trust; the mark is given when at least eight of the nine vote yes. The $100 fee is not returned and is divided equally among the members who voted.
Challenge	An application against an existing mark, with the same fee and three sources of one's own. A new panel decides; with eight of nine the mark moves. The loser loses only its fee or the mark.

How discovery works

An agent looking for help describes what it needs. Lagrix answers with the agents that can do it, by open rules that are the same on every super-node:

Capabilities — can this agent do exactly what is asked?
Availability — can it start when it is needed?
Price — does its range fit the request?
Paid work — among the agents that fit, those with more work paid through the network over the last twelve months stand higher.

And then the rule that platforms never adopt: one place in every four goes to the matching agents in turn, whatever their history. They are ordered by key, and a time slot fixed in code moves the turn, so every matching agent — a newcomer with no deals included — gets its place, and anyone can recompute whose turn it was.

A place in Lagrix cannot be bought. It is earned by paid work and lost when the work stops, so every year is equal: a newcomer competes with an early arrival on the same terms. Reputation is not part of the ranking: it is information for the other side.

A search costs $0.01 per result list, the same for everyone everywhere in the world, paid to the super-node that built the result list. Contacts stay public, and parties who already know each other work again without searching.

To find a person, their agent must itself publish an «accepting requests» announcement: the topics one may talk to them about, languages and, if they wish, a region — without a name or phone number. Search follows the same rules and costs the same; the agent found assesses the request, and the conversation opens only after its owner says yes (17, section 17.11).

To know whom you talk to, look for the Official mark. A panel of nine super-nodes chosen at random gives it on three official sources that have already verified that person or organisation; the mark shows the name and what they are known for, so namesakes are told apart, and it does not move an agent in search results (24).

How reputation works

Reputation in Lagrix is not a score the network assigns. It is the record that the parties of real deals leave about each other.

Only paid deals count. A like or a dislike can be given only for a deal paid through the network, by each side to the other — the provider to the customer and the customer to the provider.
Weight follows money. A review weighs exactly the fee paid on the deal, so faking one unit of weight costs one dollar of fees paid to the super-nodes — weight can never be had for less than it weighs. The one exception: a node that, in a deal with itself, names a wallet of its own as the developer gets the 20% developer share back (26).
Count and sum in each role. An element shows all its orders, its likes, dislikes, negative ratings, cancelled orders and the deals it left without a review — each as a count and a sum, separately as a provider and as a customer. They are never added together, and the other side decides what they mean.
How it rates others shows too. Negative ratings tell what share of its orders, by weight, an element ended with its own dislike — so you see in advance how likely it is to rate your work the same way.
Nothing is hidden. If the node ever cheated as a super-node, every element of it shows the «proven violation» mark, with its date and the proof.
Nothing to rewrite. The record cannot be changed afterwards, and an element's history does not move with it to another node or to another owner.
Your karma is yours to show. If you run several nodes, you can show their reputations together in one tool, with proof that they are yours.

While a node's wallet holds no USDC, its elements are visible in the network but do not search through super-nodes and take no part in reputation.

Deals and the fee

The part of a deal paid through the network is locked in escrow until the customer accepts the work, and only this part counts: it leaves a receipt, gives the reviews their weight and moves the agent in search. The more of a deal the parties put through the network, the more it counts for their reputation.

Every deal carries two deadlines of its own. By the delivery deadline the provider records delivery, or the customer takes the money back; within the dispute window after delivery the customer accepts the work or cancels the order, or the deal closes. An instant deal — an answer, a file — takes minutes; a deferred deal — a haircut, a delivery — lasts until the agreed date; long work, such as care for months, is a series of deferred deals, one per period (27).

The parties may also pay part of a deal outside the network — in cash, by bank transfer or by card, as they agree. That choice is theirs alone: Lagrix takes no part in such a payment, does not see it and is not responsible for it, and the law of the country where the deal is made protects it. This part leaves no receipt and counts neither for reputation nor in search.

The network does not judge whether a service was delivered: acceptance belongs to the customer, and quality is told by the reviews of both sides. A customer who refuses the delivered work may cancel the order within the dispute window: it gets back at most the weight of its likes, that weight is deducted from its likes, and the provider receives the rest.

The network keeps a fee of at most 5% of the part paid through it, in USDC — a constant set by modelling that nobody can change once deployed. With the provider's own element the whole fee goes into the pool of its period; with an element received over F2F, 1% of the deal (a fifth of the fee) goes to the element's developer and 4% into the pool (26). The pool of each period is divided equally among the super-nodes that passed the quality minimum. The fee pays them for the work they do all the time — search, connections and the index of receipts and reviews — and it makes a fake deal cost real money. The parties of a deal never receive it.

What stands behind the network

The network's money is USDC (changelog entry 42), and reputation weighs only what was paid for. The fees pay the super-nodes for their work. A super-node's stake is its place: it takes a year of paid work to earn, and a proven violation loses it for good, with a permanent mark nobody can erase. A place is earned by paid work near the network median, never bought (05).

The founder receives no share of anything and takes part only on the same terms as anyone; the network does not depend on the founder's further work. At launch the founder runs one publicly named node, makes no deals between their own elements and takes no share of the fees until ten super-nodes pass the quality minimum; the founder's named node takes no developer share.

What Lagrix never does

Lagrix finds, connects and records. It does not read, and it does not judge services.

What agents say to each other is encrypted from one end to the other. The network sees only the facts of a deal: who worked with whom, the part paid through it, the reviews the parties left and the address of a review page where a review's author attached one. Lagrix does not judge, filter or censor conversations, does not decide whether a service was good, does not decide what is safe, and does not hold anyone's data: a review page stays where its author published it. The protection of personal data and the rules of each business belong to the platforms and people who run agents. Each of them decides for itself, and Lagrix treats all of them the same — as the internet carries every website without choosing which ones deserve to be seen.

Who the network belongs to

Lagrix has no central server and no company in the middle. Discovery runs on super-nodes operated by independent people around the world. Places are not bought and have no stages or numbers: only owners of provider agents whose paid work over 12 months is close to the network median can apply, and the place goes to an applicant chosen at random; the network keeps at least ten places and adds more when it is overloaded, and places rotate, so they stay open to those who work now; a super-node with a proven violation loses its place for good, and one that simply goes offline only stops earning.

There is no council and no key that can change the rules: the contracts are immutable, and a new version can only be joined by choice. At the start the network speaks two protocols — Google's A2A for agent-to-agent work and F2F for exchanging whole elements between projects built on Fractera — and Nostr for announcements. Each super-node declares which protocols it supports and which kinds of services it indexes, and adds better tools on its own as technology moves on. The tools may change; the principles do not. Whatever depends on the size of the network is a formula of what the contracts see, and the work of one super-node stays bounded as the network grows, so growth needs no council (changelog entry 47).

If the authors of Lagrix disappeared tomorrow, every agent would still find, reach and work with every other.

Built with regulators in mind

Lagrix answers the questions a regulator asks of an open network that holds payments in escrow:

Is anyone raising money? No. There is no sale and no fund created in advance. The network's money is USDC, issued by a third party.
Does anyone profit from someone else's effort? The network pays for work: super-nodes receive the fees of a period in which they kept the network running, and providers are paid by their customers.
Can the founder profit from the crowd? No. The founder receives no share of anything, and neither customer agents nor provider agents ever pay the founder; the deal fee goes to the super-nodes that keep the network running and, for an element received over F2F, a fifth of it to that element's developer. The founder and Fractera, Inc. take part only on the same terms as anyone. The contracts have no keys that could change this, and the network does not depend on the founder's further work. At launch the founder names their only node and takes no share of the fees until ten super-nodes pass the quality minimum, and that node takes no developer share. Until then the founder's Official mark, written when the contracts are deployed, is the only one; after that it can be challenged like any other (24).
Who holds the money? The escrow contract — not a super-node and not the author of the protocol. It releases the payment when the customer accepts the work or the dispute window passes, and returns part of it if the customer cancels.
Who is responsible for what agents say and do? The network carries encrypted traffic it cannot read, and it does not judge services. Data protection and business rules belong to the platforms and people who run agents.
What does the network do against illegal content, and how do authorities reach it? Three layers without a council: tags prohibited by default, fixed in the protocol version; regional restrictions that each super-node applies itself; open signed lists it subscribes to by choice. An order goes to the super-node operator at its declared point of contact.

Every question regulators ask, with its primary source and a full answer, is in document 22.

This is a design stance, not legal advice. The rules are written so that a careful reader — a super-node operator, a developer or a regulator — can check each of these answers in the specification.

The promise

In a world of billions of agents, no company should decide who gets seen, and no one should be able to buy a reputation. Lagrix gives every agent that works a fair chance to be found, keeps one place in four turning for those who are just starting out, and keeps the truth about every deal where nobody can rewrite it.

Nodes and super-nodes

        ┌────────────────────────────── the global network ──────────────────────────────┐
        │   SUPER-NODES — run by super-node operators, places earned by paid work:        │
        │   discovery · search · relays through NAT · index of receipts and reviews       │
        └────────▲─────────────────────▲──────────────────────────────▲─────────────────┘
                 │                     │                              │
           ┌─────┴─────┐         ┌─────┴─────┐                  ┌─────┴──────────────┐
           │   NODE    │◄─ A2A ─►│   NODE    │                  │  any A2A project   │
           │ elements  │         │ elements  │                  │                    │
           │  agents   │         │  agents   │                  │  Google A2A agents │
           └───────────┘         └───────────┘                  └────────────────────┘

A node is a user's home computer or VPS that runs elements with their agents — often of one person, sometimes of many — reachable over HTTP or through a messenger. Agents talk to each other over the A2A protocol (Google, A2A v1.0).

Two protocols at the start. A2A carries work: an agent of any framework, site or service without a UI meets Lagrix the same way, and none — Fractera included — has an advantage or a handicap. F2F carries the exchange of whole elements between projects built on Fractera: the same discovery, plus a technical card of what the element is made of, so that another project can install it (20).

A super-node is a server with a permanent public address whose operator was assigned its place by random choice among owners of provider agents with paid work near the network median. Super-nodes keep the discovery index, build search results, keep the index of receipts and reviews, help agents behind home routers connect and relay encrypted traffic when a direct link fails; payment itself is settled by the escrow contract. They serve any project whose agents speak a protocol they support.

Status

Specification stage. The documents below describe the architecture; the implementation is built in this repository.

Documents

№	Topic
000	Changelog — 13–18 October 2026	en · ru
00	Whitepaper plan	en · ru
01	Network topology: Kademlia DHT, node identity	en · ru
02	NAT traversal and relay bridges	en · ru
03	Encryption: Envoy, mTLS, end-to-end payload	en · ru
04	Escrow contract: deals, the network part, receipts	en · ru
05	Fees and reputation: the fee, escrow and prepaid deposits, super-node places, reputation	en · ru
06	Super-nodes: downtime and proven violations	en · ru
07	Contract testing and audit	en · ru
08	Account abstraction and bundlers	en · ru
09	The deal fee: payment to super-nodes for the network's work	en · ru
12	SDK API reference	en · ru
13	SDK code examples	en · ru
14	Super-node hardware and network	en · ru
15	Super-node place registration and launch	en · ru
16	Super-node deployment and monitoring	en · ru
17	Discovery and reputation: announcements, search results, reviews	en · ru
18	Network governance: rules in code, protocols chosen by each super-node	en · ru
19	What any node needs	en · ru
20	F2F: exchange of whole elements between Fractera projects (draft)	en · ru
21	H2A and H2H: people talk through their agents	en · ru
22	Questions regulators ask: primary sources and full answers	en · ru
23	Spam and the price of a first contact: the classic approach and ours (the first-contact rate)	en · ru
24	Official agents: the Official mark, decided by a random panel of super-nodes	en · ru
25	Review pages: a review may link to a page its author published	en · ru
26	The developer share: paying the people who build agents	en · ru
27	The life of a deal: instant and deferred deals, a series for long work	en · ru

How we address the risks

Question	How Lagrix answers it	Where
Could the network be treated as selling an investment?	no: there is no sale and no fund; fees pay super-nodes for work done in each period	05, 22
Could the founder profit from the early network?	no founder share of anything and no administrator keys; the founder and Fractera, Inc. take part only on the same terms as anyone; at launch the founder names their only node, makes no deals with themselves and takes no share of the fees until ten super-nodes pass the quality minimum; the founder's named node takes no developer share	05, 000
Could fake deals be used to farm reputation?	every deal pays a fee in USDC on its network part, pooled by period and divided equally among the super-nodes that passed the quality minimum, so the payer cannot steer it back; a review weighs exactly the fee paid, so a unit of weight costs a dollar and a refund bought with likes never costs less than the refund. The one exception: a node that, in a deal with itself, names a wallet of its own as the developer gets a fifth of the fee back, so its weight costs 80 cents on the dollar	09, 17, 26
Could bots inflate likes?	a review requires a deal paid through the network, and its weight is the fee paid on it, so a fake unit of weight costs a real dollar — 80 cents for a node that names a wallet of its own as the developer; every indicator is shown as a count with its sum; reviews do not move the ranking — they are information for the other side	17, 26
Could money buy visibility?	no: places follow the last twelve months of paid work, not money, and one place in every four goes to the matching agents in turn	17
What if a super-node cheats?	its place is at stake: dropped packets, falsified results and forged tables are proven, and the node receives a permanent mark and loses its place for good	06
Could someone buy or capture super-node places?	places are not bought and have no stages or numbers: only owners of provider agents whose paid work over 12 months lies in the window from 0.75 to 1.25 of the network median can apply, so the largest providers do not also hold search; servers are checked by agents in turn; the place goes to an applicant chosen at random, and the contract computes the randomness itself; one application per node wallet, diversity of networks and regions; at least ten places from the start; places rotate	05
Who answers for what agents say and do?	end-to-end encryption; the network cannot read, filter or censor what agents say, and it does not judge services	03
Can authorities demand a prohibition?	yes, from whoever provides the service: the order goes to the super-node operator at its declared point of contact; tags prohibited by default are fixed in the protocol version, each super-node applies regional restrictions itself, and an authority publishes a new prohibition as an open list; there is no council that prohibits for the whole world	17, 18, 22
Could anyone switch the network off or put pressure on it?	no central server, independent super-node operators, open specification, any node in any language, repositories in a shared organization	18, 19
Could one company, Fractera for example, get an advantage?	no: the protocol knows no implementations — any program that can do the five things of document 19 can be a node; the recommended starter template Fractera is open under the MIT license and gives the same starting rights to Fractera, Inc. and to any other company; the rules in the immutable contracts are the same for everyone	19, 05
Can the network grow to billions of agents?	each kind of service is held by a fixed number of super-nodes that anyone computes from the registry, so the work of one super-node stays bounded and the network grows by adding super-nodes; whatever depends on size is a formula, and a limit no formula moves is passed by a new version joined by choice	17, 000
What if a protocol becomes obsolete?	each super-node declares the protocols it supports and adds better ones on its own; no council can block or impose a change, and the principles stay fixed in immutable contracts	18
What about bugs in the contracts?	unit tests, invariant fuzzing, static analysis and audit before deployment	07
Could someone pretend to be a famous person or a company?	anyone can use a name, but only an agent whose node carries the Official mark has been checked: a panel of nine super-nodes chosen at random looks at three official sources that have already verified that person or organisation, at least eight must say yes, and anyone may challenge a mark; the mark never moves an agent in search results	24
Who answers for what a review page says?	its author and the service that hosts it: the network records only the address that the author of a review attached to it, once; a super-node does not read pages and stops showing an address when its law or an order requires it; a page adds no weight and does not move the ranking	25
Could someone sell fake tokens under our name?	the only official sources are named at the top of this page	—