Onchain today

A product on its own TLD: what .bulbea shows

A payout router holds the onchain TLD that matches its name. What that settles, which names it needs, what a name proves, and who manages it.

A product on its own TLD: what .bulbea shows

When a legal team hears that an onchain TLD matches one of its products, the conversation usually starts with risk. Who holds it, what could they do with it, what can be done about it. That is a fair place to start, and most of what is written on the subject stays there.

This article looks at the case nobody worries about, because nothing has gone wrong in it. Bulbea is an onchain payout router, and the TLD that matches its name, .bulbea, is its own. The product holds its namespace and uses it for the thing the product does, which is paying people. Reading that arrangement closely shows what a matching TLD is for once the right party holds it, and that is a more useful picture than a list of things that could happen.

Two things should be clear from the start. Hush Partners manages the .bulbea TLD and is paid through Bulbea itself, so this is a case the desk can name. And the public facts about it are few. Where a paragraph describes .bulbea, it says so. Everything else is reasoning that applies to any product considering its own TLD, written with .yourbrand as the placeholder.

1payment made by the client, whatever the number of parties
1transaction in which every share is delivered
42characters in the wallet address a name replaces

The first two describe how Bulbea presents its own product. The third is the length of an Ethereum address as it is usually written.

What Bulbea does, in the terms it uses itself

Bulbea describes its product in one line: first a signature link, then a payment link. The order is the product.

Several parties share one incoming payment. A sale, for example, where the amount paid by the buyer is owed in different shares to a seller, to the agents who worked on it and to the professional who handled the paperwork. Each party reads its own share and signs it in advance. Until the last party has signed, the link is a signature link and nobody can pay it. Once the last signature is in, the same link becomes a payment link. The client pays once, and every share is delivered in that one transaction.

Two consequences follow. No party has to trust another party to pass money on, because nobody receives more than their own share. And nothing sits in the middle between the payment and the shares. Bulbea routes the payment and does not hold it. The page on Bulbea sets this out, and bulbea is the product itself.

None of this requires a name. A share can be sent to a wallet address, and it will arrive. The naming question begins when you ask who has to read that address, and how often they get it wrong.

Why a payout product has a naming problem

A wallet address is written as forty-two characters. It is exact, and it is unreadable. Nobody checks one by eye. People compare the first four characters and the last four and hope the middle is the same.

For a product that pays one person, this is an inconvenience. For a product that pays several parties from one payment, it is the weak point of the whole operation. Every party has to supply an address. Somebody has to collect them, usually by message. Each one is a chance to paste the wrong string, and a share sent to the wrong address is delivered to the wrong address. The careful signing that happens before the payment protects the split. It does nothing for a destination that was mistyped before anyone signed.

A name solves the reading problem. A party can look at a name and recognize it as theirs, in the way they recognize their own email address. What kind of name it is matters a great deal, and there are three kinds a payout product can use.

Destination Who can read it Who controls the names
A raw wallet address Almost nobody, reliably Nobody: it is not a name
A name under a shared suffix Anyone The operator of that suffix
A name under the product’s own TLD Anyone The product

The second row is where most products stop. A name under a suffix that many projects share is readable, and that is a real gain. The product has no say over who else gets a name there, what those names look like, or what the operator of the suffix decides next year. The third row is the one .bulbea illustrates. The namespace is the product’s own, so a share can be addressed to a name under .bulbea, and the rules of that namespace are set by the party whose name is on it.

What holding the TLD settles

On Freename, a TLD is recorded onchain as a token held in a wallet, and only its holder can issue names under it. For a product, that single rule answers three questions that are otherwise open.

It answers who can create a name that looks official. Under .yourbrand, a name such as pay.yourbrand reads as the place where the brand takes payments. If the product holds the TLD, that name exists only if the product creates it, and it points where the product says. Nobody else can issue it, and no rule elsewhere has to be relied on to prevent it.

It answers who decides the rules. Which names exist, which are held back, who may ask for one and on what terms are the holder’s decisions. A product that holds its TLD can write those rules once and apply them, where a product that uses someone else’s suffix inherits whatever that operator chose.

And it answers how long the arrangement lasts. A Freename TLD carries no annual renewal fee, so the namespace does not lapse because an invoice was missed. For a product that people are paid through, that permanence is part of the point. A destination that could expire is a poor thing to print on a payment.

Permanence is not the same as free of conditions, and a product should read the registry’s terms before it builds on them. Freename runs a royalty program in which the holder of a TLD receives a share of each registration fee for names registered under it. Taking part in that program carries an annual cost set by the registry, and the terms attached to a given TLD depend on when it was registered. For a product that issues names to the parties it pays, the question is whether those names are registered for a fee at all, and who pays it. That is a commercial decision for the product, and it should be made with the registry’s current terms in hand, since those terms belong to the registry and can change.

The reverse case shows the same three answers from the other side. If the TLD matching a product sits in another party’s wallet, that party can create names under it, sets the rules, and keeps the position for as long as it likes. What that means for the product’s rights is a question for its counsel. As a matter of how the system works, the names under a TLD follow the holder. The page on trademark TLDs explains the term and holds a free check.

The names a product needs for itself

Before a product gives anyone else a name under its TLD, it needs a short list of names for its own functions. These are the names a customer will meet first, and the ones an impersonator would most like to have.

For a product that moves money, the list sorts into two groups. The first is names that receive: the name where the product takes its own fee, and the name of its treasury, which counterparties may want to check before they send anything. The second is names that speak: support, security, status, and any name a customer might treat as the product’s official voice.

The reasoning for each group is different. A receiving name has to resolve to the right wallet and never change without a deliberate decision by the people who control that wallet. A speaking name may not need to resolve anywhere at all. Its job is to be unavailable to anyone else. Many of these are best created and left pointing nowhere, or kept on a reserved list and never issued.

The receiving names need one more rule, and it is about change. The day a treasury name is pointed at a new wallet is the day a careful counterparty should be told, in advance and through a channel other than the name itself. A product that changes the destination of a payment name silently has recreated, under its own brand, the exact pattern that payment fraud relies on: a familiar name that now leads somewhere else. Decide who can approve such a change, how many people it takes, and how it is announced, before the first counterparty relies on the name.

This is small work, and it is the work most often skipped, because none of it is visible until the day it matters. A product that holds its TLD and has not settled its own function names has the asset and none of the protection. Post-transfer activation is the service in which that first list is drawn up, with the policy that governs it.

Names for the parties who get paid

The more interesting decision is whether the parties who are paid through the product can have names under its TLD. On .bulbea, a payout share can be addressed to a name under the TLD. The general question is worth working through, because it changes what the product is to its users.

A worked example makes it concrete. Assume one payment of USD 1,000,000 shared between four parties. Assume the agreed shares are 94 percent to the seller, 3 percent to a lead agent, 2 percent to a co-agent and 1 percent to the professional who handled the paperwork. The shares total 100 percent.

One payment, four sharesWorked example, for a payment of USD 1,000,000
Seller (94 percent)USD 940,000
Lead agent (3 percent)USD 30,000
Co-agent (2 percent)USD 20,000
Paperwork (1 percent)USD 10,000

Worked example only. The shares are assumptions, and no fee of any kind is included.

Now look at the smallest bar. The party owed USD 10,000 is the one with the least power in the room and the most to lose from a mistake, because nobody else will notice if that share goes astray. With addresses, that party sends a string and trusts that it was copied correctly. With names, that party reads a name they recognize on the signature link, before they sign. The check moves to the person best placed to make it.

Giving parties names under the product’s TLD also creates obligations. The product becomes an issuer, and an issuer needs rules: who may have a name, whether a name can match a business the party does not own, and what happens when a party asks for a name that reads like someone else. Those rules belong in an issuance policy, written before the first name is given out. A product that issues names casually under its own brand has lent that brand to whoever asked first.

The rules also have to cover the end of the relationship. A party who was paid through the product last year may not be a customer next year, and may still hold the name. Whether an issued name can be withdrawn or changed is decided case by case on the registry, so a product cannot assume it will be able to take a name back. The safer design is to issue names that describe the party and never the product: a name that reads as the party’s own business stays accurate after the relationship ends, where a name that reads as a role inside the product does not.

What the payer sees, and what changes for them

The party who benefits least obviously from all of this is the one who pays. The payer does not hold a name, did not sign a share, and may never have used the product before. Yet the payer is the one who moves the money, and the one a fraudster would most like to mislead.

A payment link built on signed shares already changes the payer’s position. The payer is not asked to trust a breakdown written in an email. The shares were agreed by the people entitled to them before the link could take a payment, so what the payer sees is a total and the split behind it, as the parties themselves confirmed it.

Names add a second thing: destinations the payer can read. A payer looking at four shares can see that the largest goes to a name that reads like the seller, and that the smaller ones go to names that read like the professionals they have been dealing with. That is a check an ordinary person can perform. Four addresses of forty-two characters offer no such check to anyone.

The product’s own TLD adds a third, and it is the subtle one. When every name on the payment sits under one TLD, and that TLD is held by the product, the payer has a single question to settle about the namespace as a whole: does this product issue its names under a rule I can read. One question about one issuer is a smaller burden than a separate judgment about each name under a suffix shared with the rest of the world.

What a name does not prove

A name is easier to read than an address. It is not evidence of who is behind it. That distinction is the one most likely to be lost when names start appearing on payments.

A name under any TLD identifies a wallet that holds it. It says nothing, by itself, about the person or company controlling that wallet. A name that reads like a known firm may have been issued to that firm, or to someone else, depending entirely on the issuer’s rules. This is why the rules matter more than the technology, and why a product that issues names carries a responsibility that a product using raw addresses does not.

The practical consequence for a payer is unchanged from any other payment. Confirm the destination with the party, through a channel you already trust, before the first payment to it. A name makes that confirmation quicker, since two people can read a name aloud to each other, which nobody does with forty-two characters. It does not replace the confirmation.

Who runs a product’s TLD, and what managing it means

A product team has a product to run. The TLD is a few decisions made rarely, each of which is expensive to get wrong. That combination is the usual argument for giving the work to someone whose job it is.

Hush Partners manages the .bulbea TLD. The word needs a precise meaning, because of a rule stated earlier: only the holder of a TLD can issue names under it. Management, in that sense, is the policy and the process around the holder’s decisions. The holder’s wallet still does the issuing.

What managing a product's TLD covers
  1. The issuance policyWho may request a name, who approves it, what a name may point to, and which names are never issued.
  2. The reserved listThe function names of the product, and the names that would read as someone else's, kept out of reach.
  3. The registerOne record of every name issued, its purpose, its requester and its destination, reviewed at set intervals.
  4. Custody adviceHow the wallet that holds the TLD is controlled, and by how many people, since that wallet is the only one that can issue.

The last item deserves a sentence of its own. The wallet holding a TLD is the most sensitive key a product owns after the ones that hold its funds, because it can create an official-looking name at will. A product that would never leave its treasury under one person’s control should apply the same thinking here.

Managing a TLD is mostly a matter of reviews, and a review asks plain questions. Does every issued name still have a purpose and an owner inside the organization. Does each receiving name still point to the wallet the register says it points to. Has anyone asked for a name that the policy does not cover, and what was decided. A register that is checked on a schedule catches the drift that no single decision would reveal, such as a name created for a campaign that ended, still pointing at a wallet nobody watches.

There is one more reason this case can be described in public. Hush Partners is itself paid through Bulbea: the desk’s fee travels on a Bulbea payment link, and when an adviser referred the file, that adviser’s share is split from the fee onchain. The page for advisors describes how that works for the people who introduce a file.

Where a .bulbea name resolves, and where it does not

The limits of the model are the limits of resolution, and they apply to .bulbea as to any onchain TLD. An onchain name resolves outside the ICANN DNS, so software has to support it before it can turn the name into an address.

For names on Freename, that support exists in Bitcoin.com Wallet, in MetaMask through Freename’s resolver, and in desktop browsers through the Freename Web3 extension. Coverage is partial and it changes. A payer whose wallet does not read the name sees nothing useful, which is why a careful issuer keeps the underlying address available next to the name for anyone who needs it.

This shapes how a product should present its names. They are an aid to reading and checking, offered where they work, and never the only way to pay. A product that made a name the single route to a payment would be asking its users to depend on software it does not control. The list of capabilities that are live names the wallets and browsers involved, with a source for each.

For a public website and for email, the DNS remains the right tool. A product that holds its onchain TLD still needs its ordinary domain, and holding one does nothing to secure the other. The comparison between a dotBrand and an onchain TLD sets the two systems side by side.

The same question for your own product

The useful part of this case is that it can be turned around. The table below starts from where a product stands, and gives the first step.

Your situation What it means First step
You do not know if the TLD exists Nothing can be planned yet Run a free name check
You hold it and have issued nothing The asset without the protection Write the function names and the policy
Another party holds it Names under it follow that party Take advice, then decide whether to acquire
You hold it and pay people The .bulbea case Decide who gets names, and on what rule

For the first row, the name check is free and the answer comes privately. For the third, brand namespace recovery is the service in which the desk approaches the holder on an organization’s behalf, and your counsel remains the judge of any legal question. If the decision is to wait, namespace watch follows the names that matter in the meantime.

For the last row, the page on payments to a name shows what an invoice looks like once the names exist. The order of work does not change: function names first, policy second, names for other people last.

Questions people ask

Is .bulbea a TLD in the ICANN DNS?

No. It is an onchain TLD, recorded on a registry outside the ICANN DNS. Names under it resolve in software that supports them, and an ordinary browser does not open them without that support.

Does someone need a .bulbea name to be paid through Bulbea?

No. A share can be delivered to a wallet address. A name makes the destination readable for the party who has to check it, and that is its whole purpose.

What does Hush Partners do for the .bulbea TLD?

It manages it: the issuance policy, the reserved list, the register of names and advice on custody. Names are issued by the holder of the TLD, since only the holder can issue under it.

Should every product acquire the onchain TLD that matches its name?

Not necessarily. It depends on whether the product has a use for names, on who holds the TLD, and on what your counsel thinks of the position. Starting with a name check costs nothing and settles the first of those questions.

The Hush Partners desk

Notes from the desk. Written by the people who run the files.

Tell us what you hold. Quietly.

One named partner reads every request. Holders start with a private valuation. Organizations start with a confidential brief.