About NodeWitness

NodeWitness publishes Bitcoin cycle analysis built from on-chain data. The input that weighs most in our main indicator doesn't come from a rented API: it's computed against a full Bitcoin node we run ourselves.

This page isn't here to convince you we're trustworthy. It's here to show you what you can check on your own.

Who is behind it

NodeWitness is a personal project, built and operated from Spain. It isn't a company or a large team, which is why you won't find an org chart or photos of staff that doesn't exist.

Articles are bylined "NodeWitness Team" rather than a personal name. That isn't about hiding anyone: what holds up a claim here isn't whose name is on it, but the data it was checked against. A personal byline invites the reader to treat the content as somebody's opinion; we'd rather it be read as something you can verify.

What you can verify yourself

This is the part of the page that actually matters:

  • The node's live status. The network and mining section shows the block height, sync state and node status behind our proprietary metrics. You can cross-check that height against any public explorer, any time.
  • The methodology, in full. How the Score works lists the ten indicators that feed it, what each one measures, and where every data point comes from, with its source and update frequency.
  • Where it has failed. We publish the Score's known failures with concrete numbers: the cycle tops and bottoms it did not flag, and our own audit concluding that our DCA simulator does not beat plain DCA. This isn't decorative humility -- it's the part of the track record you can use to decide how much credit to give us.
  • How it has changed. The Score version history logs every methodology change with its date. The commitment is simple: no formula change without an entry there.

What we withhold, and why

We publish which indicators make up the Score, what each measures, and where the data comes from. We withhold the exact weight of each indicator and the internal logic that combines them.

That reserve is deliberate, and you should judge it harshly: we're asking you to trust a result whose exact recipe you can't see. Our answer is that the legitimacy of the reserve doesn't come from our word, it comes from the published track record -- failures included. If the backtest and the failures page don't convince you, the reserve shouldn't either.

What we don't do

  • We don't predict prices. The Score locates the cycle phase by comparing the present against history. It doesn't say what happens tomorrow.
  • We don't give financial advice. Nothing we publish is a buy or sell recommendation.
  • We don't publish news. Everything is evergreen or refreshes itself with the current day's data.
  • No ads, no affiliate links, no data selling. No cookies, no user accounts.
  • We never ask for private keys. None of the tools need them, and we will never ask you for them.

If you find an error

It's the most useful thing you can send us. If a number doesn't add up, a claim doesn't hold, or something in the methodology doesn't match what you observe, write to contacto@nodewitness.com.

Correcting a published error and leaving a record of it strikes us as more valuable than never having made it. A good part of what's on the failures page got there by exactly that route.

Last updated: 2026-08-02