Orca Crypto
Menu
Start Here
Learn
Chains
Exchanges
Markets
Tools
Safety
More
Buy OCX Book a session
About

How we write, check and correct this site

If we are asking you to trust guidance about your own money, you are owed the method.

Loading live prices
By the Orca Crypto teamUpdated 2026-09-026 min read
On this page 9 sections
The short answer

Everything on this site is published by Orca Crypto as an organization rather than under an individual byline. That puts the accountability on us, so this page sets out how the writing is researched and checked, what the dates on a page actually mean, how to tell us we got something wrong, and how the work is paid for.

Who writes this

Orca Crypto publishes as an organization. Guides carry the organization as the author rather than an individual byline, because the review process is what stands behind them rather than one person’s reputation.

We are a small education practice. We also run one to one sessions, which means we spend a lot of time watching real beginners get stuck on real screens. Most of what is on this site exists because somebody could not find a straight answer to it during a call.

How a guide gets written

  1. Primary sources first

    Regulations are read at the regulator, not in a summary. Protocol behavior is checked against the protocol’s own documentation. Wallet behavior is checked against the vendor’s documentation rather than a review site. Where a figure comes from onchain analysis, we say whose analysis and when it was read.

  2. Numbers carry a date

    Anything that moves is written with the date it was read, because a fee schedule or a total value locked figure without a date is worse than no figure at all.

  3. Unverified is left out

    If we could not confirm something from a source we trust, it does not go in, or it goes in explicitly flagged as unconfirmed. We would rather a guide be shorter than wrong.

  4. Written for someone who has never heard the word

    Every term is defined the first time it appears. Where a guide assumes something, it links to the page that teaches it rather than assuming quietly.

  5. The risks are stated, not softened

    Where something can lose you money we say so plainly, including on pages about things we otherwise think are fine.

What the build checks automatically

Some kinds of error are better caught by a machine than by a proofread, so they are enforced every time the site is built:

  • Counts are computed, never typed. When a page says there are 191 glossary terms or 42 networks, that number is read from the data at build time. A stale count fails the build rather than sitting on the site for a month.
  • Internal links are verified. A link to a page that does not exist, or to an anchor that does not exist on the target page, fails the build.
  • House style is enforced. American spelling throughout, and no em dashes, checked mechanically.
  • Structured data is generated from the page. The questions in our markup are the questions on the page, so a search engine is never shown something a reader is not.

What the dates on a page mean

Each guide shows when it was published and when it was last updated. Those are not refreshed on a schedule to look current. The build keeps a fingerprint of every page’s content, and the updated date changes only when the writing actually changed.

So a guide dated eight months ago has not been neglected. It means the thing it describes has not changed, and we did not pretend otherwise.

Corrections

We get things wrong. When we do, we would rather hear it from you than leave it up.

How to report one. Use the contact form and pick "General question". Tell us the page and what is wrong. A link to a better source is welcome and not required.

What we do with it. Factual errors are fixed as soon as we have confirmed them, usually within a day or two. The page’s updated date changes when the correction lands. Substantive corrections, meaning ones that changed the advice rather than a typo, are noted in updates.

What we will not do. Quietly rewrite a page to hide that it said something different, or remove a guide because a project we criticized asked us to.

Feedback and questions

Anything that is not a correction, including "this made no sense to me", is just as useful and goes to the same place. The contact form reaches us directly and we reply to everything, usually within one business day.

"I read this three times and still do not get it" is genuinely one of the most useful messages we receive, because it is almost always our fault rather than yours.

How this is funded, and the conflicts that creates

You should know who pays for something before you weigh what it says.

One to one sessions. Paid education is our main source of revenue. That is the thing the site is ultimately advertising, and we would rather say so on every page than pretend the guides exist for their own sake.

Referral links. Some links to exchanges and other platforms are referral links, and we may earn a commission if you sign up. These are disclosed on every page where they appear. A referral relationship has never bought a recommendation here, and where we think a platform is the wrong choice for a beginner we say so whether or not we have a link to it.

$OCX. We have our own token. That is a conflict of interest by definition, so it is confined to its own clearly marked section rather than woven through the educational guides.

What we do not take. Paid placement in a comparison, paid reviews, sponsored guides, or payment to remove criticism. No project has ever paid to appear on this site, and none ever will.

Advertising. There is none. We do not sell ad space and we do not run advertising trackers.

It works without a connection

The guides most likely to be needed at a bad moment are the ones least likely to load at one. Somebody checking whether a request for their recovery words is legitimate is often standing somewhere with one bar of signal.

So the safety guides, the sending guide and the site shell are stored on your device the first time you visit, along with every page you have already opened. If your connection drops, those still open, and you get a page explaining what is still readable rather than a browser error. Live prices are never stored, because a stale price is worse than no price.

What this site is not

It is not financial advice. We explain how things work and what the risks are. We do not tell anyone what to buy, and we are not licensed to.

It is not tax or legal advice. The tax pages describe how the rules generally work in the United States and where they are genuinely unsettled. They are not a substitute for an accountant who knows your situation.

It is not complete. Crypto changes faster than any site can, and there are things here we have not covered yet. If the thing you need is missing, tell us and it moves up the list.


Questions about this page? Write to us through the contact form. Last updated 2026-09-02.

Was this page useful?