Fiatside editorial team

What this byline covers

The articles, guides and help pages on this site are published under a collective byline. It covers four areas and nothing else: how local payment rails actually behave, how the blockchain networks we accept for deposits behave, how the price of a conversion is built, and which regulatory obligations apply to a digital-asset service provider.

A text goes live when its claims are either verifiable in the repository's own data (payout-rails.ts, networks.ts, pricing.ts) or drawn from a public rule cited in the body: a regulation, a payment scheme specification, a network's own documentation. When a claim meets neither condition it is removed, not softened.

Why no name appears here

On a financial subject, a byline is a signal of accountability. Publishing a fake name, a fake biography or a fake title to suggest individual expertise is common practice, and it is exactly what destroys a site's credibility once the fabrication is noticed — by a reader, by a journalist, or by a search engine.

The isRealPerson field on this record is false. It is displayed as such on the page: this byline is collective and does not refer to any physical person. No photograph, no social profile and no academic title is attached to this entry, because there is nobody to photograph or to credential.

Note for site maintainers: this record is a placeholder. As soon as a real person takes editorial responsibility for part of the content, create a record in their name with isRealPerson: true, a verifiable biography and a public professional profile, then reassign the relevant articles through the author field in their frontmatter. Never flip isRealPerson unless the person exists and has given written consent.

How a piece is checked

Every document carries a needsReview field in its frontmatter. While it is true, the page states that the text has not yet been reviewed by a named editorial owner. That is useful information for the reader and a visible debt for us.

Review covers three specific things:

1. The numbers. A settlement time, a limit, a confirmation count or a fee must come from product data or from a cited public source. No figure is written from memory.
2. The mechanisms. An explanation must describe what actually happens, not an analogy simplified to the point of being wrong. If we do not know why a behaviour exists, we write that we do not know.
3. The boundaries. Any text touching tax, regulation or a risk of losing funds must state explicitly where the information stops and where professional advice — which we do not give — would begin.

What this team does not write

We publish no price forecasts, no buy or sell recommendations, no personalised tax advice and no comparison presenting our fees as systematically lower than a named competitor's. That content attracts traffic; it also carries a responsibility we cannot honestly take on.

To see what the site claims and on what basis, the fee schedule breaks down every fee line, the glossary defines the terms used across articles, and the guides group articles by subject. An error spotted in a text can be reported through the contact page: the correction is made within one business day and the document's updated field records it.