From 0a7fd151e245a024ccbb3c24307b012aa8eab074 Mon Sep 17 00:00:00 2001 From: Dee <130502840+HodlDee@users.noreply.github.com> Date: Sun, 6 Sep 2026 23:35:45 -0400 Subject: [PATCH 1/4] Publish the Bitcoin-is-not-crypto argument, with the two failures in it Closes the draft in #87, which asked reviewers to check every claim before publishing. Most held. One did not, and the fix made the piece stronger. The draft said bitcoin "has operated continuously" across bans, collapses and drawdowns. Twice it has not, and both occasions bear directly on the argument rather than sitting beside it. In August 2010 block 74638 carried a transaction creating roughly 184 billion bitcoin, because the check on transaction outputs did not account for a sum that overflowed. A patched client shipped in about five hours and the honest chain overtook the bad one by block 74691. The supply cap held -- but it held because people noticed, wrote a fix and ran it, which is a weaker and more interesting claim than "the cap cannot fail". In March 2013 the move from Berkeley DB to LevelDB dropped an accidental limit, a block split the network in two, and it ran as two chains for around six hours until miners downgraded. Both are now a section of their own rather than a footnote, because they are the best available evidence for the section above them. Each failure was found, published, fixed in the open, and resolved by independent operators choosing to run corrected software, with no company to appeal to. That is what "no central issuer" looks like under load. A page arguing that structure beats promises, on a site whose whole instruction is verify rather than trust, cannot leave out the two times the structure needed people. Everything else follows the draft: the structural properties, the pump-and-dump checklist as risk factors rather than accusations, the limits stated as part of the argument, and the closing point that almost everything which goes wrong in this industry goes wrong at the businesses. Filed under concepts, since it explains why the setup looks as it does rather than asking anyone to change theirs. Co-Authored-By: Claude Opus 5 --- build/guides.mjs | 118 +++++++++++- docs/guides.html | 23 ++- docs/guides/bitcoin-is-not-crypto.html | 251 +++++++++++++++++++++++++ docs/guides/how-custody-fails.html | 9 + docs/guides/owning-your-bitcoin.html | 11 +- docs/guides/twenty-one-million.html | 9 + docs/guides/what-is-money.html | 9 + docs/guides/who-decides-the-rules.html | 9 + docs/sitemap.xml | 6 + 9 files changed, 436 insertions(+), 9 deletions(-) create mode 100644 docs/guides/bitcoin-is-not-crypto.html diff --git a/build/guides.mjs b/build/guides.mjs index 3220b15..3b345ff 100644 --- a/build/guides.mjs +++ b/build/guides.mjs @@ -1039,7 +1039,7 @@ const guides = [ icon: "bi-currency-bitcoin", updated: "2026-08-17", status: "published", - related: ["quickstart", "what-not-to-normalize", "recovery-test-drill", "how-custody-fails"], + related: ["quickstart", "what-not-to-normalize", "recovery-test-drill", "how-custody-fails", "bitcoin-is-not-crypto"], layout: "article", body: `

"Be your own bank" is a good slogan and a bad description. It gets the freedom right and leaves out the job description — because a bank is not just a place that holds money. It is a large organisation performing a dozen unglamorous tasks on your behalf, most of which you have never had to think about.

@@ -1072,7 +1072,7 @@ const guides = [

The Canadian version of this is not hypothetical

-

Deposits at a Canadian bank are protected by CDIC up to defined limits. Crypto assets held on a trading platform are not, whatever the platform's marketing implies. Registration with securities regulators sets rules for how a platform must operate; it is not deposit insurance and does not make you whole if the business fails.

+

Deposits at a Canadian bank are protected by CDIC up to defined limits. Crypto assets held on a trading platform are not, whatever the platform's marketing implies. ("Crypto" is doing a lot of work in that sentence — the category and the asset are not the same thing.) Registration with securities regulators sets rules for how a platform must operate; it is not deposit insurance and does not make you whole if the business fails.

Canada has its own case study. QuadrigaCX was the country's largest bitcoin exchange until it collapsed in 2019, leaving roughly 76,000 users unable to reach their funds. The Ontario Securities Commission's subsequent investigation concluded the platform had been operating as a fraud. Customers had done nothing wrong — they had simply left their coins with someone else, which is what everyone does until they decide not to. It is not an isolated case, and the differences between it and the others matter: four platforms, four different mechanisms.

@@ -7426,7 +7426,7 @@ const guides = [ icon: "bi-bank", updated: "2026-08-20", status: "published", - related: ["twenty-one-million", "who-decides-the-rules", "owning-your-bitcoin"], + related: ["twenty-one-million", "who-decides-the-rules", "owning-your-bitcoin", "bitcoin-is-not-crypto"], layout: "article", body: `

Ask what money is and most answers point at examples — notes, coins, the balance in a banking app. That is a list of things currently doing the job, not a description of the job itself. The job is the interesting part, because the list keeps changing.

@@ -8641,7 +8641,7 @@ const guides = [ icon: "bi-graph-down-arrow", updated: "2026-08-18", status: "published", - related: ["double-spend-problem", "why-run-a-node", "owning-your-bitcoin"], + related: ["double-spend-problem", "why-run-a-node", "owning-your-bitcoin", "bitcoin-is-not-crypto"], layout: "article", body: `

Twenty-one million is the most quoted number in bitcoin and the least examined. It is usually presented as a rule someone wrote down — a cap, a limit, a promise. It is none of those things. Nobody decreed it, no document states it as a target, and there is no clause anywhere saying "the supply shall be 21,000,000".

@@ -9281,7 +9281,7 @@ const guides = [ icon: "bi-check2-circle", updated: "2026-08-18", status: "published", - related: ["double-spend-problem", "why-run-a-node", "twenty-one-million"], + related: ["double-spend-problem", "why-run-a-node", "twenty-one-million", "bitcoin-is-not-crypto"], layout: "article", body: `

Bitcoin has no chief executive, no board, no shareholders, and no mechanism by which anyone can be made to accept a change. There is no vote that binds anybody. And yet the rules have changed several times, and other attempts to change them have failed decisively.

@@ -9406,7 +9406,7 @@ const guides = [ icon: "bi-building-lock", updated: "2026-09-06", status: "published", - related: ["owning-your-bitcoin", "exchange-account-security", "exchange-withdrawal"], + related: ["owning-your-bitcoin", "exchange-account-security", "exchange-withdrawal", "bitcoin-is-not-crypto"], layout: "article", body: `

The responsibilities that transfer makes an argument: leaving bitcoin with a company means your access depends on things you cannot audit. That is easy to nod along to and hard to feel. This page is the evidence — four collapses, each of which failed in a genuinely different way.

@@ -9651,6 +9651,112 @@ const guides = [ The extraction technique described here is documented public research from 2020 against hardware that has since been superseded, and it is included because it is the clearest illustration of what the attempt counter is for — not as a live claim about any current product. Chip choices, firmware and model lineups change; confirm what your own device uses against the manufacturer's documentation, and treat this page as the reasoning rather than the specification.

` }, + { + slug: "bitcoin-is-not-crypto", + category: "concepts", + products: [], + title: "Bitcoin is not \"crypto\"", + summary: "\"Crypto\" is a category label, not a description of how anything works. The distinction that matters is structural — who can change the rules, and what it would cost them — and it is checkable rather than a matter of opinion.", + level: "beginner", + minutes: 20, + effort: "read", + goals: ["learn"], + tags: ["Mindset", "How it works"], + icon: "bi-signpost-split", + updated: "2026-09-07", + status: "published", + related: ["what-is-money", "how-custody-fails", "who-decides-the-rules"], + layout: "article", + body: ` +

"Crypto" covers thousands of assets whose governance, issuance and failure modes have almost nothing in common. Grouping bitcoin with all of them, or judging it by their behaviour, obscures the only question worth asking about a monetary asset: who can change the rules, and what would it cost them?

+ +

The claim on this page is narrow and structural. Bitcoin is not distinguished by being oldest or largest. It is distinguished by minimising dependence on issuers, insiders, custodians and discretionary policy. That is a statement about structure, not about price — and unlike most things said in this space, every part of it is something you can go and check.

+ +

1The properties that actually differ

+ +

Each of these is verifiable by someone with a node and a browser. That is the test they are chosen to pass.

+ + ${checklist([ + "Fixed monetary policy. Issuance follows a halving schedule that caps supply just under 21 million. No company sets that number and no board revises it. Changing it would need a large majority of users, miners and node operators to voluntarily run incompatible software — and anyone declining would keep running the existing rules.", + "No central issuer. Not launched by a corporation or a foundation holding a controlling position. Its creator left, and no successor inherited authority. There is no entity to subpoena, capture, bankrupt or pressure into changing the money.", + "Proof of work. History is secured by expended energy. Rewriting past blocks means redoing that work faster than everyone else produces new work — an ongoing physical cost rather than a permission setting.", + "Decentralised validation. A node checks every rule itself: signatures, issuance, block validity, total supply. It does not ask a server whether the chain is valid.", + "Permissionless participation. Holding and transferring requires no account or approval from the protocol. There is no user registry and no ability to deny service — though the businesses and jurisdictions around it certainly have both.", + "Self-custody. You can hold your own keys, which removes the counterparty entirely. It also transfers the whole burden of key management onto you, which is a real cost rather than a slogan.", + "Open rules. The consensus rules and the reference implementation are public. Changes are proposed in the open and take effect only for those who choose to run the resulting software.", + "Scarcity you can audit. The property most often lost in the \"digital gold\" shorthand. You do not trust a published supply figure — a node computes total issuance from the chain and rejects any block that overpays. The auditability is the point; the number is downstream of it." + ])} + +

2The checklist that describes the other thing

+ +

None of the following is illegal in itself, and none proves fraud. They are structural features that make extraction from later buyers possible — and they are the features bitcoin's design specifically lacks.

+ + ${cautions([ + "Concentrated ownership. A small number of entities hold enough supply to move the market at will.", + "Pre-mines and insider allocations. Founders and funds receive large blocks of supply at or before launch, at prices unavailable to anyone else.", + "Discretionary issuance. The issuer can mint more units, unlock vested tranches, or change the emission schedule.", + "Paid promotion and manufactured community. Undisclosed influencers and bot-amplified sentiment standing in for organic use.", + "Promised returns. Guaranteed yield, \"risk-free\" staking, or returns funded by new deposits rather than revenue.", + "A small team controlling upgrades, infrastructure and treasury. Admin keys, upgradeable contracts, one sequencer, a discretionary treasury.", + "Single points of dependence. One company, one website, one founder whose departure or indictment ends the project.", + "Thin liquidity. Order books too shallow to absorb insider selling — which is precisely what lets insiders exit onto retail buyers." + ])} + +

Read as a list, those describe a system whose outcome depends on the continued honesty and solvency of particular people. Bitcoin's properties describe a system built to depend on as few particular people as possible.

+ +

3Twice, the structure needed rescuing

+ +

An honest version of this argument has to include the two occasions the network did not simply carry on, because both are exactly the kind of thing the previous sections could be accused of glossing over.

+ +

August 2010: the supply cap failed for five hours

+ +

Block 74638 contained a transaction that created roughly 184 billion bitcoin. The code checking transactions did not account for outputs so large that summing them overflowed, so the block was accepted and mined.

+ +

A patched client was released within about five hours, rejecting overflow transactions, and the honest chain overtook the bad one by block 74691. No permanent inflation, no user funds lost, and the cap held.

+ +

But note what actually held it. Not arithmetic operating unattended — people noticed, wrote a fix, and ran it. The rule was enforced by the participants who enforce it, which is the mechanism working, and it is a weaker claim than "the cap cannot fail".

+ +

March 2013: the chain split in two

+ +

Bitcoin Core 0.8 moved from Berkeley DB to LevelDB, and in doing so lost an accidental limit the old database had imposed. A block arrived that 0.8 nodes accepted and older nodes rejected, and the network ran as two chains for roughly six hours until miners downgraded and the split resolved.

+ +

Nobody lost coins and the fix was quick, but "the network has run continuously since 2009" is not quite true, and a page arguing that structure beats promises should say so.

+ + ${callout("Why this belongs in the argument rather than a footnote", `Both incidents are the strongest available evidence for the section above, not against it. In each case the failure was found, published, fixed in the open, and resolved by independent operators choosing to run corrected software — with no company to appeal to and nobody able to impose an outcome. That is what "no central issuer" looks like under stress. A version of this page that omitted them would be asking for exactly the trust it tells you not to extend.`)} + +

4What this does not claim

+ +

The limits are part of the argument rather than caveats bolted on to it.

+ + ${checklist([ + "It does not imply the price will rise. Monetary properties and market price are different things. Bitcoin has repeatedly lost most of its value — drawdowns beyond seventy per cent have happened more than once — and may again.", + "It does not eliminate volatility. A fixed supply means demand shocks are absorbed entirely by price. That is a consequence of the design, not a flaw in it.", + "It does not make bitcoin risk-free. Software bugs, key loss, theft, mining centralisation and regulatory action against on- and off-ramps are all real.", + "It says nothing about companies. Exchanges, lenders, custodians, ETFs and miners are ordinary businesses that can be insolvent, negligent or fraudulent, and several have been.", + "It does not condemn every alternative. Some pursue different goals honestly. The claim is that they generally depend on issuers, insiders or discretionary policy in ways bitcoin does not — a difference in structure, not a verdict on intent." + ])} + +

That fourth point is where most losses actually happen. Four ways a platform loses your bitcoin walks through four collapses with four different mechanisms, and the structure they had in common was that the customer held a claim rather than a coin. Holding bitcoin at a custodian means holding that custodian's risks, not bitcoin's properties.

+ +

5What to do with the distinction

+ + ${checklist([ + "Verify rather than trust. Every claim above is checkable. Read the rules, run a node, audit the supply yourself. Treat anything you cannot verify — including this page — as unconfirmed.", + "Learn self-custody before you need it. Practise with trivial amounts and rehearse backup and recovery while nothing is at stake. Self-custody removes counterparty risk by replacing it with personal responsibility, and unprepared that trade can be worse.", + "Avoid leverage. Volatility that is survivable unlevered is terminal levered. Forced liquidation removes the one thing the structural argument depends on — the ability to keep holding.", + "Never treat appreciation as guaranteed. Anyone promising you a return is describing something other than bitcoin." + ])} + +

The short version

+ +

"Crypto" is a marketing category. The useful question is who can change the rules and what it would cost them, and on that question bitcoin sits somewhere most of the category does not: no issuer, no insider allocation, no discretionary emission, and a supply anyone can audit for themselves rather than take on report. Twice the design needed human intervention to hold, and both times it was found in public and fixed by people who chose to run the fix — which is the mechanism, not an exception to it.

+ + ${callout("If you take one thing from this page", `Separate the protocol from the businesses built on it. Almost everything that goes wrong in this industry goes wrong at the businesses — and the moment your bitcoin sits with one of them, you have their risk profile rather than bitcoin's, however sound the protocol underneath happens to be.`)} + +

+ The 2010 value overflow is catalogued as CVE-2010-5139; the March 2013 split is documented in BIP 50 and in the alert Bitcoin published at the time. Supply, issuance and validation behaviour are checkable against a node you run, which is the standard this page asks of itself. +

` + }, ]; /* ---- derived lookups ---------------------------------------------------- */ diff --git a/docs/guides.html b/docs/guides.html index 577ae4d..11f3c8d 100755 --- a/docs/guides.html +++ b/docs/guides.html @@ -85,7 +85,7 @@

A wealth of knowledge,
at your fingertips.

- + diff --git a/docs/guides/bitcoin-is-not-crypto.html b/docs/guides/bitcoin-is-not-crypto.html new file mode 100644 index 0000000..6af0478 --- /dev/null +++ b/docs/guides/bitcoin-is-not-crypto.html @@ -0,0 +1,251 @@ + + + + + + + Bitcoin is not "crypto" | SelfCustody.ca + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+
+ + How it works +

Bitcoin is not "crypto"

+

"Crypto" is a category label, not a description of how anything works. The distinction that matters is structural — who can change the rules, and what it would cost them — and it is checkable rather than a matter of opinion.

+
+ Beginner + About 20 minutes to read + Updated Sep 7, 2026 +
+
MindsetHow it works
+ +
+
+ +
+
+
+

"Crypto" covers thousands of assets whose governance, issuance and failure modes have almost nothing in common. Grouping bitcoin with all of them, or judging it by their behaviour, obscures the only question worth asking about a monetary asset: who can change the rules, and what would it cost them?

+ +

The claim on this page is narrow and structural. Bitcoin is not distinguished by being oldest or largest. It is distinguished by minimising dependence on issuers, insiders, custodians and discretionary policy. That is a statement about structure, not about price — and unlike most things said in this space, every part of it is something you can go and check.

+ +

1The properties that actually differ

+ +

Each of these is verifiable by someone with a node and a browser. That is the test they are chosen to pass.

+ +
  • Fixed monetary policy. Issuance follows a halving schedule that caps supply just under 21 million. No company sets that number and no board revises it. Changing it would need a large majority of users, miners and node operators to voluntarily run incompatible software — and anyone declining would keep running the existing rules.
  • No central issuer. Not launched by a corporation or a foundation holding a controlling position. Its creator left, and no successor inherited authority. There is no entity to subpoena, capture, bankrupt or pressure into changing the money.
  • Proof of work. History is secured by expended energy. Rewriting past blocks means redoing that work faster than everyone else produces new work — an ongoing physical cost rather than a permission setting.
  • Decentralised validation. A node checks every rule itself: signatures, issuance, block validity, total supply. It does not ask a server whether the chain is valid.
  • Permissionless participation. Holding and transferring requires no account or approval from the protocol. There is no user registry and no ability to deny service — though the businesses and jurisdictions around it certainly have both.
  • Self-custody. You can hold your own keys, which removes the counterparty entirely. It also transfers the whole burden of key management onto you, which is a real cost rather than a slogan.
  • Open rules. The consensus rules and the reference implementation are public. Changes are proposed in the open and take effect only for those who choose to run the resulting software.
  • Scarcity you can audit. The property most often lost in the "digital gold" shorthand. You do not trust a published supply figure — a node computes total issuance from the chain and rejects any block that overpays. The auditability is the point; the number is downstream of it.
+ +

2The checklist that describes the other thing

+ +

None of the following is illegal in itself, and none proves fraud. They are structural features that make extraction from later buyers possible — and they are the features bitcoin's design specifically lacks.

+ +
  • Concentrated ownership. A small number of entities hold enough supply to move the market at will.
  • Pre-mines and insider allocations. Founders and funds receive large blocks of supply at or before launch, at prices unavailable to anyone else.
  • Discretionary issuance. The issuer can mint more units, unlock vested tranches, or change the emission schedule.
  • Paid promotion and manufactured community. Undisclosed influencers and bot-amplified sentiment standing in for organic use.
  • Promised returns. Guaranteed yield, "risk-free" staking, or returns funded by new deposits rather than revenue.
  • A small team controlling upgrades, infrastructure and treasury. Admin keys, upgradeable contracts, one sequencer, a discretionary treasury.
  • Single points of dependence. One company, one website, one founder whose departure or indictment ends the project.
  • Thin liquidity. Order books too shallow to absorb insider selling — which is precisely what lets insiders exit onto retail buyers.
+ +

Read as a list, those describe a system whose outcome depends on the continued honesty and solvency of particular people. Bitcoin's properties describe a system built to depend on as few particular people as possible.

+ +

3Twice, the structure needed rescuing

+ +

An honest version of this argument has to include the two occasions the network did not simply carry on, because both are exactly the kind of thing the previous sections could be accused of glossing over.

+ +

August 2010: the supply cap failed for five hours

+ +

Block 74638 contained a transaction that created roughly 184 billion bitcoin. The code checking transactions did not account for outputs so large that summing them overflowed, so the block was accepted and mined.

+ +

A patched client was released within about five hours, rejecting overflow transactions, and the honest chain overtook the bad one by block 74691. No permanent inflation, no user funds lost, and the cap held.

+ +

But note what actually held it. Not arithmetic operating unattended — people noticed, wrote a fix, and ran it. The rule was enforced by the participants who enforce it, which is the mechanism working, and it is a weaker claim than "the cap cannot fail".

+ +

March 2013: the chain split in two

+ +

Bitcoin Core 0.8 moved from Berkeley DB to LevelDB, and in doing so lost an accidental limit the old database had imposed. A block arrived that 0.8 nodes accepted and older nodes rejected, and the network ran as two chains for roughly six hours until miners downgraded and the split resolved.

+ +

Nobody lost coins and the fix was quick, but "the network has run continuously since 2009" is not quite true, and a page arguing that structure beats promises should say so.

+ +

Why this belongs in the argument rather than a footnote

Both incidents are the strongest available evidence for the section above, not against it. In each case the failure was found, published, fixed in the open, and resolved by independent operators choosing to run corrected software — with no company to appeal to and nobody able to impose an outcome. That is what "no central issuer" looks like under stress. A version of this page that omitted them would be asking for exactly the trust it tells you not to extend.

+ +

4What this does not claim

+ +

The limits are part of the argument rather than caveats bolted on to it.

+ +
  • It does not imply the price will rise. Monetary properties and market price are different things. Bitcoin has repeatedly lost most of its value — drawdowns beyond seventy per cent have happened more than once — and may again.
  • It does not eliminate volatility. A fixed supply means demand shocks are absorbed entirely by price. That is a consequence of the design, not a flaw in it.
  • It does not make bitcoin risk-free. Software bugs, key loss, theft, mining centralisation and regulatory action against on- and off-ramps are all real.
  • It says nothing about companies. Exchanges, lenders, custodians, ETFs and miners are ordinary businesses that can be insolvent, negligent or fraudulent, and several have been.
  • It does not condemn every alternative. Some pursue different goals honestly. The claim is that they generally depend on issuers, insiders or discretionary policy in ways bitcoin does not — a difference in structure, not a verdict on intent.
+ +

That fourth point is where most losses actually happen. Four ways a platform loses your bitcoin walks through four collapses with four different mechanisms, and the structure they had in common was that the customer held a claim rather than a coin. Holding bitcoin at a custodian means holding that custodian's risks, not bitcoin's properties.

+ +

5What to do with the distinction

+ +
  • Verify rather than trust. Every claim above is checkable. Read the rules, run a node, audit the supply yourself. Treat anything you cannot verify — including this page — as unconfirmed.
  • Learn self-custody before you need it. Practise with trivial amounts and rehearse backup and recovery while nothing is at stake. Self-custody removes counterparty risk by replacing it with personal responsibility, and unprepared that trade can be worse.
  • Avoid leverage. Volatility that is survivable unlevered is terminal levered. Forced liquidation removes the one thing the structural argument depends on — the ability to keep holding.
  • Never treat appreciation as guaranteed. Anyone promising you a return is describing something other than bitcoin.
+ +

The short version

+ +

"Crypto" is a marketing category. The useful question is who can change the rules and what it would cost them, and on that question bitcoin sits somewhere most of the category does not: no issuer, no insider allocation, no discretionary emission, and a supply anyone can audit for themselves rather than take on report. Twice the design needed human intervention to hold, and both times it was found in public and fixed by people who chose to run the fix — which is the mechanism, not an exception to it.

+ +

If you take one thing from this page

Separate the protocol from the businesses built on it. Almost everything that goes wrong in this industry goes wrong at the businesses — and the moment your bitcoin sits with one of them, you have their risk profile rather than bitcoin's, however sound the protocol underneath happens to be.

+ +

+ The 2010 value overflow is catalogued as CVE-2010-5139; the March 2013 split is documented in BIP 50 and in the alert Bitcoin published at the time. Supply, issuance and validation behaviour are checkable against a node you run, which is the standard this page asks of itself. +

+
+
+ +
+
+
+
+ Do not guess +

Stuck on a step?

+

If the screen in front of you does not match the guide, stop. Review the related walkthroughs or get a second set of eyes before exposing recovery words or approving a transaction.

+
+
+ All Guides + Get Help +
+ +
+
+
+ + +
+
+
Keep going

Related guides

+
+
+
+
+ Beginner +
+

What is money?

+

Cattle, salt, glass beads, limestone discs the size of a small car — plenty of things have done the job, and nearly all of them stopped. They stopped for the same reason every time, and it is the reason a hard cap exists.

+ Read guide +
+
+
+
+ Beginner +
+

Four ways a platform loses your bitcoin

+

Not your keys, not your coins is the conclusion. These are the cases it was drawn from — four failures with four different mechanisms, none of which announced itself in advance, and one of which was Canadian.

+ Read guide +
+
+
+
+ Intermediate +
+

Who decides the rules

+

Bitcoin has no board, no vote, and no procedure for changing itself — yet it changes. How that works, why the block size war ended as it did, and what a failed fork in August 2026 demonstrated in under eight hours.

+ Read guide +
+
+
+ + + + + diff --git a/docs/guides/how-custody-fails.html b/docs/guides/how-custody-fails.html index 7e5d267..3ce305c 100644 --- a/docs/guides/how-custody-fails.html +++ b/docs/guides/how-custody-fails.html @@ -240,6 +240,15 @@

Lock down the exchange account itself

Withdrawing bitcoin from a Canadian exchange

One process that works on every Canadian platform, what changes on the two that send bitcoin straight to your wallet, and the records the CRA expects you to keep.

Read guide +
+
+
+
+ Beginner +
+

Bitcoin is not "crypto"

+

"Crypto" is a category label, not a description of how anything works. The distinction that matters is structural — who can change the rules, and what it would cost them — and it is checkable rather than a matter of opinion.

+ Read guide
diff --git a/docs/guides/owning-your-bitcoin.html b/docs/guides/owning-your-bitcoin.html index 49491c6..092a1bd 100644 --- a/docs/guides/owning-your-bitcoin.html +++ b/docs/guides/owning-your-bitcoin.html @@ -120,7 +120,7 @@

What the bank was actually doing

The Canadian version of this is not hypothetical

-

Deposits at a Canadian bank are protected by CDIC up to defined limits. Crypto assets held on a trading platform are not, whatever the platform's marketing implies. Registration with securities regulators sets rules for how a platform must operate; it is not deposit insurance and does not make you whole if the business fails.

+

Deposits at a Canadian bank are protected by CDIC up to defined limits. Crypto assets held on a trading platform are not, whatever the platform's marketing implies. ("Crypto" is doing a lot of work in that sentence — the category and the asset are not the same thing.) Registration with securities regulators sets rules for how a platform must operate; it is not deposit insurance and does not make you whole if the business fails.

Canada has its own case study. QuadrigaCX was the country's largest bitcoin exchange until it collapsed in 2019, leaving roughly 76,000 users unable to reach their funds. The Ontario Securities Commission's subsequent investigation concluded the platform had been operating as a fraud. Customers had done nothing wrong — they had simply left their coins with someone else, which is what everyone does until they decide not to. It is not an isolated case, and the differences between it and the others matter: four platforms, four different mechanisms.

@@ -233,6 +233,15 @@

Test your recovery without risking your coins

Four ways a platform loses your bitcoin

Not your keys, not your coins is the conclusion. These are the cases it was drawn from — four failures with four different mechanisms, none of which announced itself in advance, and one of which was Canadian.

Read guide +
+
+
+
+ Beginner +
+

Bitcoin is not "crypto"

+

"Crypto" is a category label, not a description of how anything works. The distinction that matters is structural — who can change the rules, and what it would cost them — and it is checkable rather than a matter of opinion.

+ Read guide
diff --git a/docs/guides/twenty-one-million.html b/docs/guides/twenty-one-million.html index 60ee565..e624d81 100644 --- a/docs/guides/twenty-one-million.html +++ b/docs/guides/twenty-one-million.html @@ -240,6 +240,15 @@

Why run a node

With great power comes great responsibility

Self-custody does not just remove the middleman. It removes the work the middleman was doing, and hands you the job. Here is exactly what that job is.

Read guide +
+
+
+
+ Beginner +
+

Bitcoin is not "crypto"

+

"Crypto" is a category label, not a description of how anything works. The distinction that matters is structural — who can change the rules, and what it would cost them — and it is checkable rather than a matter of opinion.

+ Read guide
diff --git a/docs/guides/what-is-money.html b/docs/guides/what-is-money.html index abd09c4..d516654 100644 --- a/docs/guides/what-is-money.html +++ b/docs/guides/what-is-money.html @@ -277,6 +277,15 @@

Who decides the rules

With great power comes great responsibility

Self-custody does not just remove the middleman. It removes the work the middleman was doing, and hands you the job. Here is exactly what that job is.

Read guide +
+
+
+
+ Beginner +
+

Bitcoin is not "crypto"

+

"Crypto" is a category label, not a description of how anything works. The distinction that matters is structural — who can change the rules, and what it would cost them — and it is checkable rather than a matter of opinion.

+ Read guide
diff --git a/docs/guides/who-decides-the-rules.html b/docs/guides/who-decides-the-rules.html index a585a44..2ec9873 100644 --- a/docs/guides/who-decides-the-rules.html +++ b/docs/guides/who-decides-the-rules.html @@ -240,6 +240,15 @@

Why run a node

The 21 million hard cap

The number is not a policy anyone chose to announce and cannot be raised by agreement. It falls out of a halving schedule, and it holds because every node independently refuses to accept a block that breaks it.

Read guide +
+
+
+
+ Beginner +
+

Bitcoin is not "crypto"

+

"Crypto" is a category label, not a description of how anything works. The distinction that matters is structural — who can change the rules, and what it would cost them — and it is checkable rather than a matter of opinion.

+ Read guide
diff --git a/docs/sitemap.xml b/docs/sitemap.xml index 1272774..de91ca4 100644 --- a/docs/sitemap.xml +++ b/docs/sitemap.xml @@ -410,4 +410,10 @@ monthly 0.7 + + https://selfcustody.ca/guides/bitcoin-is-not-crypto.html + 2026-09-07 + monthly + 0.7 + From fb5774d77f7abbacaa5e3f84d04628258b99d76d Mon Sep 17 00:00:00 2001 From: Dee <130502840+HodlDee@users.noreply.github.com> Date: Sun, 6 Sep 2026 23:47:53 -0400 Subject: [PATCH 2/4] Reframe the crypto piece as a method rather than a verdict The homepage states the editorial standard plainly: "Built to Inform, Not Persuade. We explain the options, the risks, and the tradeoffs that matter -- so you can decide for yourself." The previous version of this guide did not meet it. It reached a conclusion on the reader's behalf, and the conclusion happened to be the one this site is built around, which makes it harder to notice rather than easier. The strongest part of the draft was always the checklist -- concentrated ownership, pre-mines, discretionary issuance, thin liquidity. That is a method. So the method now leads, as eight structural questions with what a strong and a weak answer look like, and bitcoin is the worked example rather than the thesis. Same evidence, same incidents, same limits; the reader draws the conclusion. It is also more useful this way. A verdict about bitcoin helps with bitcoin. Eight questions help with the next thing marketed at someone, which will not be on any list written today. Slug and title follow the reframing: evaluating-a-monetary-asset, "Eight questions to ask about any digital asset". Nothing was published under the old slug, so there is no redirect to keep. The two failures stay, and now sit under the question they bear on -- whether supply is enforced or promised -- with the judgement about what they demonstrate handed to the reader rather than made for them. Co-Authored-By: Claude Opus 5 --- build/guides.mjs | 124 +++++++++++------- docs/guides.html | 8 +- ....html => evaluating-a-monetary-asset.html} | 90 ++++++++----- docs/guides/how-custody-fails.html | 6 +- docs/guides/owning-your-bitcoin.html | 8 +- docs/guides/twenty-one-million.html | 6 +- docs/guides/what-is-money.html | 6 +- docs/guides/who-decides-the-rules.html | 6 +- docs/sitemap.xml | 2 +- 9 files changed, 152 insertions(+), 104 deletions(-) rename docs/guides/{bitcoin-is-not-crypto.html => evaluating-a-monetary-asset.html} (50%) diff --git a/build/guides.mjs b/build/guides.mjs index 3b345ff..49a9be3 100644 --- a/build/guides.mjs +++ b/build/guides.mjs @@ -1039,7 +1039,7 @@ const guides = [ icon: "bi-currency-bitcoin", updated: "2026-08-17", status: "published", - related: ["quickstart", "what-not-to-normalize", "recovery-test-drill", "how-custody-fails", "bitcoin-is-not-crypto"], + related: ["quickstart", "what-not-to-normalize", "recovery-test-drill", "how-custody-fails", "evaluating-a-monetary-asset"], layout: "article", body: `

"Be your own bank" is a good slogan and a bad description. It gets the freedom right and leaves out the job description — because a bank is not just a place that holds money. It is a large organisation performing a dozen unglamorous tasks on your behalf, most of which you have never had to think about.

@@ -1072,7 +1072,7 @@ const guides = [

The Canadian version of this is not hypothetical

-

Deposits at a Canadian bank are protected by CDIC up to defined limits. Crypto assets held on a trading platform are not, whatever the platform's marketing implies. ("Crypto" is doing a lot of work in that sentence — the category and the asset are not the same thing.) Registration with securities regulators sets rules for how a platform must operate; it is not deposit insurance and does not make you whole if the business fails.

+

Deposits at a Canadian bank are protected by CDIC up to defined limits. Crypto assets held on a trading platform are not, whatever the platform's marketing implies. ("Crypto" is doing a lot of work in that sentence — there are better questions to ask than which category something is in.) Registration with securities regulators sets rules for how a platform must operate; it is not deposit insurance and does not make you whole if the business fails.

Canada has its own case study. QuadrigaCX was the country's largest bitcoin exchange until it collapsed in 2019, leaving roughly 76,000 users unable to reach their funds. The Ontario Securities Commission's subsequent investigation concluded the platform had been operating as a fraud. Customers had done nothing wrong — they had simply left their coins with someone else, which is what everyone does until they decide not to. It is not an isolated case, and the differences between it and the others matter: four platforms, four different mechanisms.

@@ -7426,7 +7426,7 @@ const guides = [ icon: "bi-bank", updated: "2026-08-20", status: "published", - related: ["twenty-one-million", "who-decides-the-rules", "owning-your-bitcoin", "bitcoin-is-not-crypto"], + related: ["twenty-one-million", "who-decides-the-rules", "owning-your-bitcoin", "evaluating-a-monetary-asset"], layout: "article", body: `

Ask what money is and most answers point at examples — notes, coins, the balance in a banking app. That is a list of things currently doing the job, not a description of the job itself. The job is the interesting part, because the list keeps changing.

@@ -8641,7 +8641,7 @@ const guides = [ icon: "bi-graph-down-arrow", updated: "2026-08-18", status: "published", - related: ["double-spend-problem", "why-run-a-node", "owning-your-bitcoin", "bitcoin-is-not-crypto"], + related: ["double-spend-problem", "why-run-a-node", "owning-your-bitcoin", "evaluating-a-monetary-asset"], layout: "article", body: `

Twenty-one million is the most quoted number in bitcoin and the least examined. It is usually presented as a rule someone wrote down — a cap, a limit, a promise. It is none of those things. Nobody decreed it, no document states it as a target, and there is no clause anywhere saying "the supply shall be 21,000,000".

@@ -9281,7 +9281,7 @@ const guides = [ icon: "bi-check2-circle", updated: "2026-08-18", status: "published", - related: ["double-spend-problem", "why-run-a-node", "twenty-one-million", "bitcoin-is-not-crypto"], + related: ["double-spend-problem", "why-run-a-node", "twenty-one-million", "evaluating-a-monetary-asset"], layout: "article", body: `

Bitcoin has no chief executive, no board, no shareholders, and no mechanism by which anyone can be made to accept a change. There is no vote that binds anybody. And yet the rules have changed several times, and other attempts to change them have failed decisively.

@@ -9406,7 +9406,7 @@ const guides = [ icon: "bi-building-lock", updated: "2026-09-06", status: "published", - related: ["owning-your-bitcoin", "exchange-account-security", "exchange-withdrawal", "bitcoin-is-not-crypto"], + related: ["owning-your-bitcoin", "exchange-account-security", "exchange-withdrawal", "evaluating-a-monetary-asset"], layout: "article", body: `

The responsibilities that transfer makes an argument: leaving bitcoin with a company means your access depends on things you cannot audit. That is easy to nod along to and hard to feel. This page is the evidence — four collapses, each of which failed in a genuinely different way.

@@ -9652,11 +9652,11 @@ const guides = [

` }, { - slug: "bitcoin-is-not-crypto", + slug: "evaluating-a-monetary-asset", category: "concepts", products: [], - title: "Bitcoin is not \"crypto\"", - summary: "\"Crypto\" is a category label, not a description of how anything works. The distinction that matters is structural — who can change the rules, and what it would cost them — and it is checkable rather than a matter of opinion.", + title: "Eight questions to ask about any digital asset", + summary: "\"Crypto\" is a category label rather than a description of how anything works. These are the structural questions that separate the things inside it — who can change the rules, who was allocated what, and what it would cost them — with bitcoin's answers as the worked example.", level: "beginner", minutes: 20, effort: "read", @@ -9668,90 +9668,114 @@ const guides = [ related: ["what-is-money", "how-custody-fails", "who-decides-the-rules"], layout: "article", body: ` -

"Crypto" covers thousands of assets whose governance, issuance and failure modes have almost nothing in common. Grouping bitcoin with all of them, or judging it by their behaviour, obscures the only question worth asking about a monetary asset: who can change the rules, and what would it cost them?

+

"Crypto" covers thousands of assets whose governance, issuance and failure modes have almost nothing in common. That makes it useless as a description — and it is why comparisons that begin "crypto is…" tend to be arguments rather than analysis.

-

The claim on this page is narrow and structural. Bitcoin is not distinguished by being oldest or largest. It is distinguished by minimising dependence on issuers, insiders, custodians and discretionary policy. That is a statement about structure, not about price — and unlike most things said in this space, every part of it is something you can go and check.

+

There is a better approach than deciding which side of that word something falls on, and it is one you can apply yourself to anything, including things that do not exist yet. Ask who can change the rules, and what it would cost them. The eight questions below are that question, broken into parts you can actually check.

-

1The properties that actually differ

+

Bitcoin is used as the worked example throughout, because it is what this site is about and because its answers happen to be verifiable. The point is the method rather than the verdict.

-

Each of these is verifiable by someone with a node and a browser. That is the test they are chosen to pass.

+

1The eight questions

+ +

For each one: what is being asked, and what a good answer looks like. None of them is about price.

+ +
+ + + + + + + + + + + + +
QuestionWhat a strong answer looks likeWhat a weak one looks like
Who sets issuance?A fixed rule anyone can read, that no party can revise.A team, a foundation, or a schedule that has been changed before.
Who was allocated supply, and when?Nobody. Everyone acquired it on the same terms.Pre-mines, founder allocations, vesting tranches at prices unavailable to others.
Can you verify the supply yourself?Software you run computes it from the ledger and rejects violations.A published figure you are asked to believe.
What does it cost to rewrite history?An ongoing, external, physical cost that rises with participation.A permission setting, or a majority of a stake that insiders hold.
Who validates?Anyone, on ordinary hardware, checking every rule themselves.A handful of operators, or a company's servers.
Who can deny you service?Nobody at the protocol level, whatever the surrounding businesses can do.An issuer with a freeze function, a registry, or an admin key.
Can you hold it yourself?Yes, with keys you generate, and no counterparty at all.Only through a custodian, or a wrapped representation of the real thing.
Who controls the roadmap?Nobody unilaterally. Changes take effect only for those who run them.An executive team that can repurpose or upgrade the network at will.
+
+ +

Notice what is absent. Nothing here asks whether the technology is clever, whether the team is credible, or whether adoption is growing. Those are real questions and they are not structural ones — they describe how well something is going rather than who it depends on.

+ +

2Bitcoin's answers, and how to check them

+ +

Worked example. Each of these is checkable by someone with a node and a browser, which is the standard the questions were chosen to allow.

${checklist([ - "Fixed monetary policy. Issuance follows a halving schedule that caps supply just under 21 million. No company sets that number and no board revises it. Changing it would need a large majority of users, miners and node operators to voluntarily run incompatible software — and anyone declining would keep running the existing rules.", - "No central issuer. Not launched by a corporation or a foundation holding a controlling position. Its creator left, and no successor inherited authority. There is no entity to subpoena, capture, bankrupt or pressure into changing the money.", - "Proof of work. History is secured by expended energy. Rewriting past blocks means redoing that work faster than everyone else produces new work — an ongoing physical cost rather than a permission setting.", - "Decentralised validation. A node checks every rule itself: signatures, issuance, block validity, total supply. It does not ask a server whether the chain is valid.", - "Permissionless participation. Holding and transferring requires no account or approval from the protocol. There is no user registry and no ability to deny service — though the businesses and jurisdictions around it certainly have both.", - "Self-custody. You can hold your own keys, which removes the counterparty entirely. It also transfers the whole burden of key management onto you, which is a real cost rather than a slogan.", - "Open rules. The consensus rules and the reference implementation are public. Changes are proposed in the open and take effect only for those who choose to run the resulting software.", - "Scarcity you can audit. The property most often lost in the \"digital gold\" shorthand. You do not trust a published supply figure — a node computes total issuance from the chain and rejects any block that overpays. The auditability is the point; the number is downstream of it." + "Issuance follows a halving schedule capping supply just under 21 million. Changing it would need a large majority to voluntarily run incompatible software, and anyone declining keeps the existing rules.", + "Allocation: no pre-mine and no founder allocation. Its creator left, and no successor inherited authority.", + "Verification: a node computes total issuance from the chain and rejects any block that overpays. You do not take the number on report — the auditability is the point, and the figure is downstream of it.", + "Rewriting history means redoing proof of work faster than everyone else produces new work. An ongoing physical cost, not a setting.", + "Validation: anyone can run a node on ordinary hardware and check every rule — signatures, issuance, block validity, supply.", + "Denial of service: the protocol has no user registry and no freeze function. The businesses and jurisdictions around it have both, and use them.", + "Self-custody: you can hold your own keys, which removes the counterparty entirely — and transfers the whole burden of key management to you.", + "Roadmap: changes are proposed in the open and take effect only for those who choose to run them. Who decides the rules covers how that has actually played out." ])} -

2The checklist that describes the other thing

+

3What the weak answers look like together

-

None of the following is illegal in itself, and none proves fraud. They are structural features that make extraction from later buyers possible — and they are the features bitcoin's design specifically lacks.

+

None of the following is illegal in itself, and none proves fraud. They are the structural features that make extraction from later buyers possible, which is why they are worth spotting rather than condemning.

${cautions([ "Concentrated ownership. A small number of entities hold enough supply to move the market at will.", - "Pre-mines and insider allocations. Founders and funds receive large blocks of supply at or before launch, at prices unavailable to anyone else.", - "Discretionary issuance. The issuer can mint more units, unlock vested tranches, or change the emission schedule.", + "Pre-mines and insider allocations. Founders and funds receive large blocks at or before launch, at prices unavailable to anyone else.", + "Discretionary issuance. The issuer can mint more, unlock vested tranches, or change the emission schedule.", "Paid promotion and manufactured community. Undisclosed influencers and bot-amplified sentiment standing in for organic use.", "Promised returns. Guaranteed yield, \"risk-free\" staking, or returns funded by new deposits rather than revenue.", "A small team controlling upgrades, infrastructure and treasury. Admin keys, upgradeable contracts, one sequencer, a discretionary treasury.", - "Single points of dependence. One company, one website, one founder whose departure or indictment ends the project.", - "Thin liquidity. Order books too shallow to absorb insider selling — which is precisely what lets insiders exit onto retail buyers." + "Single points of dependence. One company, one website, one founder whose departure ends the project.", + "Thin liquidity. Order books too shallow to absorb insider selling — which is what lets insiders exit onto retail buyers." ])} -

Read as a list, those describe a system whose outcome depends on the continued honesty and solvency of particular people. Bitcoin's properties describe a system built to depend on as few particular people as possible.

+

Read together, those describe a system whose outcome depends on the continued honesty and solvency of particular people. That is a fact about structure, and you can establish it without forming a view about anyone's intentions.

-

3Twice, the structure needed rescuing

+

4Twice, the answers needed people

-

An honest version of this argument has to include the two occasions the network did not simply carry on, because both are exactly the kind of thing the previous sections could be accused of glossing over.

+

Applying the method honestly means applying it to the worked example too, and bitcoin has twice failed to simply carry on. Both occasions bear on question three — whether the supply is enforced or promised — so they belong here rather than in a footnote.

August 2010: the supply cap failed for five hours

Block 74638 contained a transaction that created roughly 184 billion bitcoin. The code checking transactions did not account for outputs so large that summing them overflowed, so the block was accepted and mined.

-

A patched client was released within about five hours, rejecting overflow transactions, and the honest chain overtook the bad one by block 74691. No permanent inflation, no user funds lost, and the cap held.

+

A patched client was released within about five hours, rejecting overflow transactions, and the honest chain overtook the bad one by block 74691. No permanent inflation, no user funds lost.

-

But note what actually held it. Not arithmetic operating unattended — people noticed, wrote a fix, and ran it. The rule was enforced by the participants who enforce it, which is the mechanism working, and it is a weaker claim than "the cap cannot fail".

+

Note what actually held the cap. Not arithmetic operating unattended — people noticed, wrote a fix, and ran it. The rule was enforced by the participants who enforce it, which is a weaker and more precise claim than "the cap cannot fail".

March 2013: the chain split in two

-

Bitcoin Core 0.8 moved from Berkeley DB to LevelDB, and in doing so lost an accidental limit the old database had imposed. A block arrived that 0.8 nodes accepted and older nodes rejected, and the network ran as two chains for roughly six hours until miners downgraded and the split resolved.

+

Bitcoin Core 0.8 moved from Berkeley DB to LevelDB and lost an accidental limit the old database had imposed. A block arrived that 0.8 nodes accepted and older nodes rejected, and the network ran as two chains for roughly six hours until miners downgraded.

-

Nobody lost coins and the fix was quick, but "the network has run continuously since 2009" is not quite true, and a page arguing that structure beats promises should say so.

+

Nobody lost coins, but "it has run continuously since 2009" is not quite true, and a page about checking claims should not repeat one it has not checked.

- ${callout("Why this belongs in the argument rather than a footnote", `Both incidents are the strongest available evidence for the section above, not against it. In each case the failure was found, published, fixed in the open, and resolved by independent operators choosing to run corrected software — with no company to appeal to and nobody able to impose an outcome. That is what "no central issuer" looks like under stress. A version of this page that omitted them would be asking for exactly the trust it tells you not to extend.`)} + ${callout("What the incidents actually demonstrate", `Both are evidence about question eight rather than exceptions to it. Each failure was found, published, fixed in the open, and resolved by independent operators choosing to run corrected software — with no company to appeal to and nobody able to impose an outcome. Whether that reassures you is your call to make; the point is that it is a matter of record rather than a matter of opinion.`)} -

4What this does not claim

+

5What the method does not tell you

-

The limits are part of the argument rather than caveats bolted on to it.

+

Structural answers are narrow on purpose, and the limits are part of using them properly rather than caveats bolted on.

${checklist([ - "It does not imply the price will rise. Monetary properties and market price are different things. Bitcoin has repeatedly lost most of its value — drawdowns beyond seventy per cent have happened more than once — and may again.", - "It does not eliminate volatility. A fixed supply means demand shocks are absorbed entirely by price. That is a consequence of the design, not a flaw in it.", - "It does not make bitcoin risk-free. Software bugs, key loss, theft, mining centralisation and regulatory action against on- and off-ramps are all real.", - "It says nothing about companies. Exchanges, lenders, custodians, ETFs and miners are ordinary businesses that can be insolvent, negligent or fraudulent, and several have been.", - "It does not condemn every alternative. Some pursue different goals honestly. The claim is that they generally depend on issuers, insiders or discretionary policy in ways bitcoin does not — a difference in structure, not a verdict on intent." + "Nothing about price. Monetary properties and market price are different things. Bitcoin has repeatedly lost most of its value — drawdowns beyond seventy per cent have happened more than once — and may again.", + "Nothing about volatility. A fixed supply means demand shocks are absorbed entirely by price. That follows from the design rather than contradicting it.", + "Nothing about safety. Software bugs, key loss, theft, mining centralisation and regulatory action against on- and off-ramps are all real and none is answered by these questions.", + "Nothing about the businesses. Exchanges, lenders, custodians, ETFs and miners are ordinary companies that can be insolvent, negligent or fraudulent, and several have been.", + "Nothing about intent. Some projects with weak structural answers are honest experiments. The questions describe dependencies, not motives." ])} -

That fourth point is where most losses actually happen. Four ways a platform loses your bitcoin walks through four collapses with four different mechanisms, and the structure they had in common was that the customer held a claim rather than a coin. Holding bitcoin at a custodian means holding that custodian's risks, not bitcoin's properties.

+

That fourth point is where most losses actually happen. Four ways a platform loses your bitcoin walks through four collapses with four different mechanisms, and the thing they had in common was that the customer held a claim rather than a coin. Holding bitcoin at a custodian means holding that custodian's risks, whatever the protocol underneath does.

-

5What to do with the distinction

+

6Using it

${checklist([ - "Verify rather than trust. Every claim above is checkable. Read the rules, run a node, audit the supply yourself. Treat anything you cannot verify — including this page — as unconfirmed.", - "Learn self-custody before you need it. Practise with trivial amounts and rehearse backup and recovery while nothing is at stake. Self-custody removes counterparty risk by replacing it with personal responsibility, and unprepared that trade can be worse.", - "Avoid leverage. Volatility that is survivable unlevered is terminal levered. Forced liquidation removes the one thing the structural argument depends on — the ability to keep holding.", - "Never treat appreciation as guaranteed. Anyone promising you a return is describing something other than bitcoin." + "Ask the eight questions of anything before you form a view about it, including things this site recommends. A method you only apply to other people's assets is not a method.", + "Verify rather than trust. Read the rules, run a node, audit the supply. Treat anything you cannot check — including this page — as unconfirmed.", + "Separate the protocol from the businesses built on it. They have different answers to every question above, and almost everything that goes wrong in this industry goes wrong at the businesses.", + "Be wary of promised returns specifically. Anyone guaranteeing you a yield is describing a business, whatever asset it is denominated in." ])}

The short version

-

"Crypto" is a marketing category. The useful question is who can change the rules and what it would cost them, and on that question bitcoin sits somewhere most of the category does not: no issuer, no insider allocation, no discretionary emission, and a supply anyone can audit for themselves rather than take on report. Twice the design needed human intervention to hold, and both times it was found in public and fixed by people who chose to run the fix — which is the mechanism, not an exception to it.

+

Whether something counts as "crypto" is a question about vocabulary. Who can change the rules, who was allocated what, and whether you can check the supply yourself are questions about structure, and they have answers you can go and establish. Bitcoin's answers are unusual and are also a matter of record rather than assertion — including the two occasions when holding the line required people to notice and act.

- ${callout("If you take one thing from this page", `Separate the protocol from the businesses built on it. Almost everything that goes wrong in this industry goes wrong at the businesses — and the moment your bitcoin sits with one of them, you have their risk profile rather than bitcoin's, however sound the protocol underneath happens to be.`)} + ${callout("If you take one thing from this page", `The questions are more useful than any verdict they produce, because the next thing marketed at you will not be on any list written today. Learn to ask who the system depends on, and you can evaluate something nobody has warned you about yet.`)}

The 2010 value overflow is catalogued as CVE-2010-5139; the March 2013 split is documented in BIP 50 and in the alert Bitcoin published at the time. Supply, issuance and validation behaviour are checkable against a node you run, which is the standard this page asks of itself. diff --git a/docs/guides.html b/docs/guides.html index 11f3c8d..cab8733 100755 --- a/docs/guides.html +++ b/docs/guides.html @@ -1451,8 +1451,8 @@

What is actually protecting your seed

-
-
+
+
@@ -1461,8 +1461,8 @@

What is actually protecting your seed

Beginner
-

Bitcoin is not "crypto"

-

"Crypto" is a category label, not a description of how anything works. The distinction that matters is structural — who can change the rules, and what it would cost them — and it is checkable rather than a matter of opinion.

+

Eight questions to ask about any digital asset

+

"Crypto" is a category label rather than a description of how anything works. These are the structural questions that separate the things inside it — who can change the rules, who was allocated what, and what it would cost them — with bitcoin's answers as the worked example.

MindsetHow it works

20 min read

diff --git a/docs/guides/bitcoin-is-not-crypto.html b/docs/guides/evaluating-a-monetary-asset.html similarity index 50% rename from docs/guides/bitcoin-is-not-crypto.html rename to docs/guides/evaluating-a-monetary-asset.html index 6af0478..872be3d 100644 --- a/docs/guides/bitcoin-is-not-crypto.html +++ b/docs/guides/evaluating-a-monetary-asset.html @@ -3,16 +3,16 @@ - - Bitcoin is not "crypto" | SelfCustody.ca + + Eight questions to ask about any digital asset | SelfCustody.ca - + - - - + + + @@ -28,7 +28,7 @@ - +
diff --git a/docs/guides/owning-your-bitcoin.html b/docs/guides/owning-your-bitcoin.html index 092a1bd..b277360 100644 --- a/docs/guides/owning-your-bitcoin.html +++ b/docs/guides/owning-your-bitcoin.html @@ -120,7 +120,7 @@

What the bank was actually doing

The Canadian version of this is not hypothetical

-

Deposits at a Canadian bank are protected by CDIC up to defined limits. Crypto assets held on a trading platform are not, whatever the platform's marketing implies. ("Crypto" is doing a lot of work in that sentence — the category and the asset are not the same thing.) Registration with securities regulators sets rules for how a platform must operate; it is not deposit insurance and does not make you whole if the business fails.

+

Deposits at a Canadian bank are protected by CDIC up to defined limits. Crypto assets held on a trading platform are not, whatever the platform's marketing implies. ("Crypto" is doing a lot of work in that sentence — there are better questions to ask than which category something is in.) Registration with securities regulators sets rules for how a platform must operate; it is not deposit insurance and does not make you whole if the business fails.

Canada has its own case study. QuadrigaCX was the country's largest bitcoin exchange until it collapsed in 2019, leaving roughly 76,000 users unable to reach their funds. The Ontario Securities Commission's subsequent investigation concluded the platform had been operating as a fraud. Customers had done nothing wrong — they had simply left their coins with someone else, which is what everyone does until they decide not to. It is not an isolated case, and the differences between it and the others matter: four platforms, four different mechanisms.

@@ -233,14 +233,14 @@

Test your recovery without risking your coins

Four ways a platform loses your bitcoin

Not your keys, not your coins is the conclusion. These are the cases it was drawn from — four failures with four different mechanisms, none of which announced itself in advance, and one of which was Canadian.

Read guide -
+
Beginner
-

Bitcoin is not "crypto"

-

"Crypto" is a category label, not a description of how anything works. The distinction that matters is structural — who can change the rules, and what it would cost them — and it is checkable rather than a matter of opinion.

+

Eight questions to ask about any digital asset

+

"Crypto" is a category label rather than a description of how anything works. These are the structural questions that separate the things inside it — who can change the rules, who was allocated what, and what it would cost them — with bitcoin's answers as the worked example.

Read guide
diff --git a/docs/guides/twenty-one-million.html b/docs/guides/twenty-one-million.html index e624d81..d80da09 100644 --- a/docs/guides/twenty-one-million.html +++ b/docs/guides/twenty-one-million.html @@ -240,14 +240,14 @@

Why run a node

With great power comes great responsibility

Self-custody does not just remove the middleman. It removes the work the middleman was doing, and hands you the job. Here is exactly what that job is.

Read guide -
+
Beginner
-

Bitcoin is not "crypto"

-

"Crypto" is a category label, not a description of how anything works. The distinction that matters is structural — who can change the rules, and what it would cost them — and it is checkable rather than a matter of opinion.

+

Eight questions to ask about any digital asset

+

"Crypto" is a category label rather than a description of how anything works. These are the structural questions that separate the things inside it — who can change the rules, who was allocated what, and what it would cost them — with bitcoin's answers as the worked example.

Read guide
diff --git a/docs/guides/what-is-money.html b/docs/guides/what-is-money.html index d516654..82c7ed6 100644 --- a/docs/guides/what-is-money.html +++ b/docs/guides/what-is-money.html @@ -277,14 +277,14 @@

Who decides the rules

With great power comes great responsibility

Self-custody does not just remove the middleman. It removes the work the middleman was doing, and hands you the job. Here is exactly what that job is.

Read guide -
+
Beginner
-

Bitcoin is not "crypto"

-

"Crypto" is a category label, not a description of how anything works. The distinction that matters is structural — who can change the rules, and what it would cost them — and it is checkable rather than a matter of opinion.

+

Eight questions to ask about any digital asset

+

"Crypto" is a category label rather than a description of how anything works. These are the structural questions that separate the things inside it — who can change the rules, who was allocated what, and what it would cost them — with bitcoin's answers as the worked example.

Read guide
diff --git a/docs/guides/who-decides-the-rules.html b/docs/guides/who-decides-the-rules.html index 2ec9873..18f299c 100644 --- a/docs/guides/who-decides-the-rules.html +++ b/docs/guides/who-decides-the-rules.html @@ -240,14 +240,14 @@

Why run a node

The 21 million hard cap

The number is not a policy anyone chose to announce and cannot be raised by agreement. It falls out of a halving schedule, and it holds because every node independently refuses to accept a block that breaks it.

Read guide -
+
Beginner
-

Bitcoin is not "crypto"

-

"Crypto" is a category label, not a description of how anything works. The distinction that matters is structural — who can change the rules, and what it would cost them — and it is checkable rather than a matter of opinion.

+

Eight questions to ask about any digital asset

+

"Crypto" is a category label rather than a description of how anything works. These are the structural questions that separate the things inside it — who can change the rules, who was allocated what, and what it would cost them — with bitcoin's answers as the worked example.

Read guide
diff --git a/docs/sitemap.xml b/docs/sitemap.xml index de91ca4..f49a0cd 100644 --- a/docs/sitemap.xml +++ b/docs/sitemap.xml @@ -411,7 +411,7 @@ 0.7 - https://selfcustody.ca/guides/bitcoin-is-not-crypto.html + https://selfcustody.ca/guides/evaluating-a-monetary-asset.html 2026-09-07 monthly 0.7 From ce79d9e5a3d4db9cb18fd8a411801647d061c914 Mon Sep 17 00:00:00 2001 From: Dee <130502840+HodlDee@users.noreply.github.com> Date: Mon, 7 Sep 2026 19:06:13 -0400 Subject: [PATCH 3/4] Say what the 2013 split actually cost From the external review. The guide said "Nobody lost coins" about the March 2013 chain split, which BIP 50 contradicts twice. It records "at least one large double spend" during the fork -- experimental rather than malicious, by someone testing whether it was possible -- and that the pool operators who downgraded first to restore the older chain did so "despite the fact that this caused them to sacrifice significant amounts of money." Neither of those is a customer left permanently out of pocket, and the correction does not invent one. But a blanket no-loss claim erases both, on a page whose whole argument is that claims should be checked rather than repeated. Money moved that should not have, and mining revenue was thrown away on purpose to end it. BIP 50 is now cited at the paragraph as well as in the source note. Co-Authored-By: Claude Opus 5 --- build/guides.mjs | 6 ++++-- docs/guides/evaluating-a-monetary-asset.html | 6 ++++-- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/build/guides.mjs b/build/guides.mjs index 49a9be3..2f1cb4c 100644 --- a/build/guides.mjs +++ b/build/guides.mjs @@ -9744,7 +9744,9 @@ const guides = [

Bitcoin Core 0.8 moved from Berkeley DB to LevelDB and lost an accidental limit the old database had imposed. A block arrived that 0.8 nodes accepted and older nodes rejected, and the network ran as two chains for roughly six hours until miners downgraded.

-

Nobody lost coins, but "it has run continuously since 2009" is not quite true, and a page about checking claims should not repeat one it has not checked.

+

It was not free. BIP 50, the project's own write-up, records at least one large double spend during the split — by someone testing whether it was possible rather than robbing anyone — and notes that the two pool operators who downgraded first to restore the older chain did so "despite the fact that this caused them to sacrifice significant amounts of money". Nobody has documented customers left permanently out of pocket, and this page is not going to invent any. But money moved that should not have, and mining revenue was thrown away on purpose to end it.

+ +

Which is why "it has run continuously since 2009" is not quite true, and a page about checking claims should not repeat one it has not checked.

${callout("What the incidents actually demonstrate", `Both are evidence about question eight rather than exceptions to it. Each failure was found, published, fixed in the open, and resolved by independent operators choosing to run corrected software — with no company to appeal to and nobody able to impose an outcome. Whether that reassures you is your call to make; the point is that it is a matter of record rather than a matter of opinion.`)} @@ -9778,7 +9780,7 @@ const guides = [ ${callout("If you take one thing from this page", `The questions are more useful than any verdict they produce, because the next thing marketed at you will not be on any list written today. Learn to ask who the system depends on, and you can evaluate something nobody has warned you about yet.`)}

- The 2010 value overflow is catalogued as CVE-2010-5139; the March 2013 split is documented in BIP 50 and in the alert Bitcoin published at the time. Supply, issuance and validation behaviour are checkable against a node you run, which is the standard this page asks of itself. + The 2010 value overflow is catalogued as CVE-2010-5139; the March 2013 split, the double spend during it and the pools' sacrificed revenue are all recorded in BIP 50, alongside the alert Bitcoin published at the time. Supply, issuance and validation behaviour are checkable against a node you run, which is the standard this page asks of itself.

` }, ]; diff --git a/docs/guides/evaluating-a-monetary-asset.html b/docs/guides/evaluating-a-monetary-asset.html index 872be3d..170fa18 100644 --- a/docs/guides/evaluating-a-monetary-asset.html +++ b/docs/guides/evaluating-a-monetary-asset.html @@ -150,7 +150,9 @@

March 2013: the chain split in two

Bitcoin Core 0.8 moved from Berkeley DB to LevelDB and lost an accidental limit the old database had imposed. A block arrived that 0.8 nodes accepted and older nodes rejected, and the network ran as two chains for roughly six hours until miners downgraded.

-

Nobody lost coins, but "it has run continuously since 2009" is not quite true, and a page about checking claims should not repeat one it has not checked.

+

It was not free. BIP 50, the project's own write-up, records at least one large double spend during the split — by someone testing whether it was possible rather than robbing anyone — and notes that the two pool operators who downgraded first to restore the older chain did so "despite the fact that this caused them to sacrifice significant amounts of money". Nobody has documented customers left permanently out of pocket, and this page is not going to invent any. But money moved that should not have, and mining revenue was thrown away on purpose to end it.

+ +

Which is why "it has run continuously since 2009" is not quite true, and a page about checking claims should not repeat one it has not checked.

What the incidents actually demonstrate

Both are evidence about question eight rather than exceptions to it. Each failure was found, published, fixed in the open, and resolved by independent operators choosing to run corrected software — with no company to appeal to and nobody able to impose an outcome. Whether that reassures you is your call to make; the point is that it is a matter of record rather than a matter of opinion.

@@ -173,7 +175,7 @@

The short version

If you take one thing from this page

The questions are more useful than any verdict they produce, because the next thing marketed at you will not be on any list written today. Learn to ask who the system depends on, and you can evaluate something nobody has warned you about yet.

- The 2010 value overflow is catalogued as CVE-2010-5139; the March 2013 split is documented in BIP 50 and in the alert Bitcoin published at the time. Supply, issuance and validation behaviour are checkable against a node you run, which is the standard this page asks of itself. + The 2010 value overflow is catalogued as CVE-2010-5139; the March 2013 split, the double spend during it and the pools' sacrificed revenue are all recorded in BIP 50, alongside the alert Bitcoin published at the time. Supply, issuance and validation behaviour are checkable against a node you run, which is the standard this page asks of itself.

From bc1b0a1316cf757f0209629eedbfb3362d6c5bb5 Mon Sep 17 00:00:00 2001 From: Dee <130502840+HodlDee@users.noreply.github.com> Date: Mon, 7 Sep 2026 19:33:47 -0400 Subject: [PATCH 4/4] Scope the 2013 loss claim to what BIP 50 reports Follow-up review of #116. "Nobody has documented customers left permanently out of pocket" is a claim about all reporting everywhere, which this page has not checked and cannot check. It now says BIP 50 does not report that, which is what is actually known, and BIP 50 is linked at the paragraph rather than only in the source note. Co-Authored-By: Claude Opus 5 --- build/guides.mjs | 30 ++++++++++---------- docs/guides.html | 2 +- docs/guides/evaluating-a-monetary-asset.html | 30 ++++++++++---------- docs/guides/how-custody-fails.html | 2 +- docs/guides/owning-your-bitcoin.html | 4 +-- docs/guides/twenty-one-million.html | 2 +- docs/guides/what-is-money.html | 2 +- docs/guides/who-decides-the-rules.html | 2 +- 8 files changed, 37 insertions(+), 37 deletions(-) diff --git a/build/guides.mjs b/build/guides.mjs index 2f1cb4c..dc5e134 100644 --- a/build/guides.mjs +++ b/build/guides.mjs @@ -1072,7 +1072,7 @@ const guides = [

The Canadian version of this is not hypothetical

-

Deposits at a Canadian bank are protected by CDIC up to defined limits. Crypto assets held on a trading platform are not, whatever the platform's marketing implies. ("Crypto" is doing a lot of work in that sentence — there are better questions to ask than which category something is in.) Registration with securities regulators sets rules for how a platform must operate; it is not deposit insurance and does not make you whole if the business fails.

+

Deposits at a Canadian bank are protected by CDIC up to defined limits. Crypto assets held on a trading platform are not, whatever the platform's marketing implies. ("Crypto" is doing a lot of work in that sentence. There are better questions to ask than which category something is in.) Registration with securities regulators sets rules for how a platform must operate; it is not deposit insurance and does not make you whole if the business fails.

Canada has its own case study. QuadrigaCX was the country's largest bitcoin exchange until it collapsed in 2019, leaving roughly 76,000 users unable to reach their funds. The Ontario Securities Commission's subsequent investigation concluded the platform had been operating as a fraud. Customers had done nothing wrong — they had simply left their coins with someone else, which is what everyone does until they decide not to. It is not an isolated case, and the differences between it and the others matter: four platforms, four different mechanisms.

@@ -9656,7 +9656,7 @@ const guides = [ category: "concepts", products: [], title: "Eight questions to ask about any digital asset", - summary: "\"Crypto\" is a category label rather than a description of how anything works. These are the structural questions that separate the things inside it — who can change the rules, who was allocated what, and what it would cost them — with bitcoin's answers as the worked example.", + summary: "\"Crypto\" is a category label rather than a description of how anything works. These are the structural questions that separate the things inside it: who can change the rules, who was allocated what, and what it would cost them. Bitcoin's answers are the worked example.", level: "beginner", minutes: 20, effort: "read", @@ -9668,7 +9668,7 @@ const guides = [ related: ["what-is-money", "how-custody-fails", "who-decides-the-rules"], layout: "article", body: ` -

"Crypto" covers thousands of assets whose governance, issuance and failure modes have almost nothing in common. That makes it useless as a description — and it is why comparisons that begin "crypto is…" tend to be arguments rather than analysis.

+

"Crypto" covers thousands of assets whose governance, issuance and failure modes have almost nothing in common. That makes it useless as a description, and it is why comparisons that begin "crypto is…" tend to be arguments rather than analysis.

There is a better approach than deciding which side of that word something falls on, and it is one you can apply yourself to anything, including things that do not exist yet. Ask who can change the rules, and what it would cost them. The eight questions below are that question, broken into parts you can actually check.

@@ -9694,7 +9694,7 @@ const guides = [ -

Notice what is absent. Nothing here asks whether the technology is clever, whether the team is credible, or whether adoption is growing. Those are real questions and they are not structural ones — they describe how well something is going rather than who it depends on.

+

Notice what is absent. Nothing here asks whether the technology is clever, whether the team is credible, or whether adoption is growing. Those are real questions and they are not structural ones. They describe how well something is going rather than who it depends on.

2Bitcoin's answers, and how to check them

@@ -9703,11 +9703,11 @@ const guides = [ ${checklist([ "Issuance follows a halving schedule capping supply just under 21 million. Changing it would need a large majority to voluntarily run incompatible software, and anyone declining keeps the existing rules.", "Allocation: no pre-mine and no founder allocation. Its creator left, and no successor inherited authority.", - "Verification: a node computes total issuance from the chain and rejects any block that overpays. You do not take the number on report — the auditability is the point, and the figure is downstream of it.", + "Verification: a node computes total issuance from the chain and rejects any block that overpays. You do not take the number on report. The auditability is the point, and the figure is downstream of it.", "Rewriting history means redoing proof of work faster than everyone else produces new work. An ongoing physical cost, not a setting.", - "Validation: anyone can run a node on ordinary hardware and check every rule — signatures, issuance, block validity, supply.", + "Validation: anyone can run a node on ordinary hardware and check every rule: signatures, issuance, block validity, supply.", "Denial of service: the protocol has no user registry and no freeze function. The businesses and jurisdictions around it have both, and use them.", - "Self-custody: you can hold your own keys, which removes the counterparty entirely — and transfers the whole burden of key management to you.", + "Self-custody: you can hold your own keys, which removes the counterparty entirely and transfers the whole burden of key management to you.", "Roadmap: changes are proposed in the open and take effect only for those who choose to run them. Who decides the rules covers how that has actually played out." ])} @@ -9723,14 +9723,14 @@ const guides = [ "Promised returns. Guaranteed yield, \"risk-free\" staking, or returns funded by new deposits rather than revenue.", "A small team controlling upgrades, infrastructure and treasury. Admin keys, upgradeable contracts, one sequencer, a discretionary treasury.", "Single points of dependence. One company, one website, one founder whose departure ends the project.", - "Thin liquidity. Order books too shallow to absorb insider selling — which is what lets insiders exit onto retail buyers." + "Thin liquidity. Order books too shallow to absorb insider selling, which is what lets insiders exit onto retail buyers." ])}

Read together, those describe a system whose outcome depends on the continued honesty and solvency of particular people. That is a fact about structure, and you can establish it without forming a view about anyone's intentions.

4Twice, the answers needed people

-

Applying the method honestly means applying it to the worked example too, and bitcoin has twice failed to simply carry on. Both occasions bear on question three — whether the supply is enforced or promised — so they belong here rather than in a footnote.

+

Applying the method honestly means applying it to the worked example too, and bitcoin has twice failed to simply carry on. Both occasions bear on question three, whether the supply is enforced or promised, so they belong here rather than in a footnote.

August 2010: the supply cap failed for five hours

@@ -9738,24 +9738,24 @@ const guides = [

A patched client was released within about five hours, rejecting overflow transactions, and the honest chain overtook the bad one by block 74691. No permanent inflation, no user funds lost.

-

Note what actually held the cap. Not arithmetic operating unattended — people noticed, wrote a fix, and ran it. The rule was enforced by the participants who enforce it, which is a weaker and more precise claim than "the cap cannot fail".

+

Note what actually held the cap. Not arithmetic operating unattended. People noticed, wrote a fix, and ran it. The rule was enforced by the participants who enforce it, which is a weaker and more precise claim than "the cap cannot fail".

March 2013: the chain split in two

Bitcoin Core 0.8 moved from Berkeley DB to LevelDB and lost an accidental limit the old database had imposed. A block arrived that 0.8 nodes accepted and older nodes rejected, and the network ran as two chains for roughly six hours until miners downgraded.

-

It was not free. BIP 50, the project's own write-up, records at least one large double spend during the split — by someone testing whether it was possible rather than robbing anyone — and notes that the two pool operators who downgraded first to restore the older chain did so "despite the fact that this caused them to sacrifice significant amounts of money". Nobody has documented customers left permanently out of pocket, and this page is not going to invent any. But money moved that should not have, and mining revenue was thrown away on purpose to end it.

+

It was not free. BIP 50, the project's own write-up, records at least one large double spend during the split, by someone testing whether it was possible rather than robbing anyone, and notes that the two pool operators who downgraded first to restore the older chain did so "despite the fact that this caused them to sacrifice significant amounts of money". BIP 50 does not report customers left permanently out of pocket, and this page is not going to invent any. What it does record is that money moved which should not have, and that mining revenue was thrown away on purpose to end it.

Which is why "it has run continuously since 2009" is not quite true, and a page about checking claims should not repeat one it has not checked.

- ${callout("What the incidents actually demonstrate", `Both are evidence about question eight rather than exceptions to it. Each failure was found, published, fixed in the open, and resolved by independent operators choosing to run corrected software — with no company to appeal to and nobody able to impose an outcome. Whether that reassures you is your call to make; the point is that it is a matter of record rather than a matter of opinion.`)} + ${callout("What the incidents actually demonstrate", `Both are evidence about question eight rather than exceptions to it. Each failure was found, published, fixed in the open, and resolved by independent operators choosing to run corrected software, with no company to appeal to and nobody able to impose an outcome. Whether that reassures you is your call to make; the point is that it is a matter of record rather than a matter of opinion.`)}

5What the method does not tell you

Structural answers are narrow on purpose, and the limits are part of using them properly rather than caveats bolted on.

${checklist([ - "Nothing about price. Monetary properties and market price are different things. Bitcoin has repeatedly lost most of its value — drawdowns beyond seventy per cent have happened more than once — and may again.", + "Nothing about price. Monetary properties and market price are different things. Bitcoin has repeatedly lost most of its value, with drawdowns beyond seventy per cent more than once, and may again.", "Nothing about volatility. A fixed supply means demand shocks are absorbed entirely by price. That follows from the design rather than contradicting it.", "Nothing about safety. Software bugs, key loss, theft, mining centralisation and regulatory action against on- and off-ramps are all real and none is answered by these questions.", "Nothing about the businesses. Exchanges, lenders, custodians, ETFs and miners are ordinary companies that can be insolvent, negligent or fraudulent, and several have been.", @@ -9768,14 +9768,14 @@ const guides = [ ${checklist([ "Ask the eight questions of anything before you form a view about it, including things this site recommends. A method you only apply to other people's assets is not a method.", - "Verify rather than trust. Read the rules, run a node, audit the supply. Treat anything you cannot check — including this page — as unconfirmed.", + "Verify rather than trust. Read the rules, run a node, audit the supply. Treat anything you cannot check, including this page, as unconfirmed.", "Separate the protocol from the businesses built on it. They have different answers to every question above, and almost everything that goes wrong in this industry goes wrong at the businesses.", "Be wary of promised returns specifically. Anyone guaranteeing you a yield is describing a business, whatever asset it is denominated in." ])}

The short version

-

Whether something counts as "crypto" is a question about vocabulary. Who can change the rules, who was allocated what, and whether you can check the supply yourself are questions about structure, and they have answers you can go and establish. Bitcoin's answers are unusual and are also a matter of record rather than assertion — including the two occasions when holding the line required people to notice and act.

+

Whether something counts as "crypto" is a question about vocabulary. Who can change the rules, who was allocated what, and whether you can check the supply yourself are questions about structure, and they have answers you can go and establish. Bitcoin's answers are unusual and are also a matter of record rather than assertion, including the two occasions when holding the line required people to notice and act.

${callout("If you take one thing from this page", `The questions are more useful than any verdict they produce, because the next thing marketed at you will not be on any list written today. Learn to ask who the system depends on, and you can evaluate something nobody has warned you about yet.`)} diff --git a/docs/guides.html b/docs/guides.html index cab8733..417c90d 100755 --- a/docs/guides.html +++ b/docs/guides.html @@ -1462,7 +1462,7 @@

What is actually protecting your seed

Eight questions to ask about any digital asset

-

"Crypto" is a category label rather than a description of how anything works. These are the structural questions that separate the things inside it — who can change the rules, who was allocated what, and what it would cost them — with bitcoin's answers as the worked example.

+

"Crypto" is a category label rather than a description of how anything works. These are the structural questions that separate the things inside it: who can change the rules, who was allocated what, and what it would cost them. Bitcoin's answers are the worked example.

MindsetHow it works

20 min read

diff --git a/docs/guides/evaluating-a-monetary-asset.html b/docs/guides/evaluating-a-monetary-asset.html index 170fa18..37fce65 100644 --- a/docs/guides/evaluating-a-monetary-asset.html +++ b/docs/guides/evaluating-a-monetary-asset.html @@ -3,7 +3,7 @@ - + Eight questions to ask about any digital asset | SelfCustody.ca @@ -11,7 +11,7 @@ - + @@ -28,7 +28,7 @@ - +
diff --git a/docs/guides/owning-your-bitcoin.html b/docs/guides/owning-your-bitcoin.html index b277360..95028cf 100644 --- a/docs/guides/owning-your-bitcoin.html +++ b/docs/guides/owning-your-bitcoin.html @@ -120,7 +120,7 @@

What the bank was actually doing

The Canadian version of this is not hypothetical

-

Deposits at a Canadian bank are protected by CDIC up to defined limits. Crypto assets held on a trading platform are not, whatever the platform's marketing implies. ("Crypto" is doing a lot of work in that sentence — there are better questions to ask than which category something is in.) Registration with securities regulators sets rules for how a platform must operate; it is not deposit insurance and does not make you whole if the business fails.

+

Deposits at a Canadian bank are protected by CDIC up to defined limits. Crypto assets held on a trading platform are not, whatever the platform's marketing implies. ("Crypto" is doing a lot of work in that sentence. There are better questions to ask than which category something is in.) Registration with securities regulators sets rules for how a platform must operate; it is not deposit insurance and does not make you whole if the business fails.

Canada has its own case study. QuadrigaCX was the country's largest bitcoin exchange until it collapsed in 2019, leaving roughly 76,000 users unable to reach their funds. The Ontario Securities Commission's subsequent investigation concluded the platform had been operating as a fraud. Customers had done nothing wrong — they had simply left their coins with someone else, which is what everyone does until they decide not to. It is not an isolated case, and the differences between it and the others matter: four platforms, four different mechanisms.

@@ -240,7 +240,7 @@

Four ways a platform loses your bitcoin

Beginner

Eight questions to ask about any digital asset

-

"Crypto" is a category label rather than a description of how anything works. These are the structural questions that separate the things inside it — who can change the rules, who was allocated what, and what it would cost them — with bitcoin's answers as the worked example.

+

"Crypto" is a category label rather than a description of how anything works. These are the structural questions that separate the things inside it: who can change the rules, who was allocated what, and what it would cost them. Bitcoin's answers are the worked example.

Read guide diff --git a/docs/guides/twenty-one-million.html b/docs/guides/twenty-one-million.html index d80da09..f469807 100644 --- a/docs/guides/twenty-one-million.html +++ b/docs/guides/twenty-one-million.html @@ -247,7 +247,7 @@

With great power comes great responsibility

Beginner

Eight questions to ask about any digital asset

-

"Crypto" is a category label rather than a description of how anything works. These are the structural questions that separate the things inside it — who can change the rules, who was allocated what, and what it would cost them — with bitcoin's answers as the worked example.

+

"Crypto" is a category label rather than a description of how anything works. These are the structural questions that separate the things inside it: who can change the rules, who was allocated what, and what it would cost them. Bitcoin's answers are the worked example.

Read guide diff --git a/docs/guides/what-is-money.html b/docs/guides/what-is-money.html index 82c7ed6..f32245f 100644 --- a/docs/guides/what-is-money.html +++ b/docs/guides/what-is-money.html @@ -284,7 +284,7 @@

With great power comes great responsibility

Beginner

Eight questions to ask about any digital asset

-

"Crypto" is a category label rather than a description of how anything works. These are the structural questions that separate the things inside it — who can change the rules, who was allocated what, and what it would cost them — with bitcoin's answers as the worked example.

+

"Crypto" is a category label rather than a description of how anything works. These are the structural questions that separate the things inside it: who can change the rules, who was allocated what, and what it would cost them. Bitcoin's answers are the worked example.

Read guide diff --git a/docs/guides/who-decides-the-rules.html b/docs/guides/who-decides-the-rules.html index 18f299c..0baf1dc 100644 --- a/docs/guides/who-decides-the-rules.html +++ b/docs/guides/who-decides-the-rules.html @@ -247,7 +247,7 @@

The 21 million hard cap

Beginner

Eight questions to ask about any digital asset

-

"Crypto" is a category label rather than a description of how anything works. These are the structural questions that separate the things inside it — who can change the rules, who was allocated what, and what it would cost them — with bitcoin's answers as the worked example.

+

"Crypto" is a category label rather than a description of how anything works. These are the structural questions that separate the things inside it: who can change the rules, who was allocated what, and what it would cost them. Bitcoin's answers are the worked example.

Read guide