Skip to the guide
THE BITCOIN PROJECT

A CLEAR ASSET MANDATE

One network.
Explicit boundaries.

This project supports native BTC on Bitcoin mainnet. It rejects substitutes while examining their claimed benefits and real risks with care.

Project policy ≠ scientific certainty ≠ Church endorsement
Research edition 01 / 9 October 2026

BTCNATIVE BTC / MAINNET

A PRACTICAL GUIDE FOR COMMUNITY ORGANIZATIONS

Bitcoin, organizational authority and service.

A printable guide for Lions clubs, Knights of Columbus councils and assemblies, foundations and other community organizations. It covers governing documents, custody, gifts, payments, officer succession and the ethical questions of Magnifica Humanitas.

Research edition 1 · 9 October 2026. Independent Spark House publication with linked sources and original diagrams. Proposed procedures require adoption under the actual organization’s rules; the guide supplies no receiving address or authorization to hold BTC.

Original diagrams: Three safeguards · Shared custody · Gift routes

PROJECT POLICY · NATIVE BITCOIN ONLY

BTC. No substitutes.

For this Bitcoin project, Spark House disavows independent fork currencies and every separate cryptocurrency derived from Bitcoin that changes its rules. It also excludes all other tokens, wrapped or synthetic BTC, stablecoins, lending, leverage and financial derivatives from the project treasury.

We disavow outside arrangements that introduce unwanted monetary or counterparty exposure: USD and other conventional currencies, fiat pegs, automatic conversion, conventional trade or currency schemes used as substitutes for BTC, and third-party claims presented as Bitcoin. No outside party may redefine a contribution’s asset, pledge project BTC, or attach new redemption conditions.

The mandate is native BTC on Bitcoin mainnet, accounted for in BTC and satoshis. It does not promise a fixed exchange rate, purchasing power or risk-free outcome. Any legally required reporting valuation is accounting, not permission to convert the treasury. This project’s mandate does not rewrite other Spark House programs’ payment arrangements.

Bitcoin mainnet has adopted consensus upgrades. A separate currency is different from an upgrade within Bitcoin. [3][5]

The rule-change distinction matters. Today’s Bitcoin is not an unchanged copy of 2009 software. SegWit and Taproot are deployed consensus changes within Bitcoin mainnet. This policy rejects independent assets—including every rule-changing descendant of Bitcoin—while identifying BTC by the Bitcoin mainnet followed by its validating participants. It does not pretend that software governance or future disagreements disappear.[2][3][5]

The asset mandate is the project’s stated policy. The custody and public-contribution procedures on /bitcoin remain proposed until the actual recipient, signers, wallet and gift terms are verified. These pages provide no deposit address, automated conversion, trade execution or investment offering.

02ANCESTRY IS NOT IDENTITY

A familiar name does not make it BTC.

A chain split, a copied codebase and a token representing an asset are different structures. None turns a separate asset into native Bitcoin.

Native BTC runs on Bitcoin mainnet. BCH and BSV are separate chain-split currencies; LTC and DOGE have code-family ancestry; ETH is a separate network; WBTC, stablecoins, ETF shares and derivatives are tokens or financial claims. Lightning is a BTC layer, not a separate coin.
Four relationships that should not be confusedThis is a classification of relationships, not a complete family tree or a ranking of investment quality. Mainnet improvements do not create a second currency.[45][46][48][49][51][52][16]Download SVG ↗
Major examples: purposes, tradeoffs and the project’s decision
Asset / relationshipPurpose or possible benefitDistinct rules and risksProject status
Bitcoin Cash (BCH)
2017 Bitcoin chain split
Emphasizes larger on-chain capacity and everyday payments.A separate ledger and asset with different consensus and ecosystem decisions. Capacity does not itself prove superior security, liquidity or decentralization.[45]Disavowed / excluded
Bitcoin SV (BSV)
2018 split from BCH
Promotes large-scale on-chain processing and data applications.Changed validation/configuration and potentially substantial node resource requirements. A claim to the original vision does not make BSV a BTC balance.[46][47]Disavowed / excluded
Litecoin (LTC)
Bitcoin code ancestry
Designed for payments with different timing and mining parameters.Separate issuance, security economics, market and implementation. Code reuse does not preserve the same monetary rules.[48]Disavowed / excluded
Dogecoin (DOGE)
Code-family descendant
Payment and tipping emphasis; continuing issuance is presented as supporting circulation.Roughly five billion additional coins annually, with no Bitcoin-style terminal cap. Predictable issuance does not mean a stable price.[49][50]Disavowed / excluded
Ethereum (ETH) and application tokens
Separate ecosystem; not a Bitcoin chain fork
Programmable applications; proof-of-stake validation avoids proof-of-work mining.Different monetary and consensus rules; staking penalties, application bugs, bridge or custodian dependencies vary by use. Smart contracts cannot guarantee their external inputs.[51]Excluded
All other independent forks and tokensDesign goals vary and should be examined from their own specifications.No name, common history or claimed peg grants Bitcoin mainnet spending authority. The examples above are not an exhaustive inventory.Excluded

Benefits in this table describe intended uses or structural possibilities, not verified superiority or investment recommendations. Avoid exposing a BTC private key to a fork-claiming service; the prospect of an additional asset is not a reason to compromise the original custody.[9]

03TOKENS, SECURITIES & DERIVATIVES

Price exposure is not possession.

A product can track Bitcoin, hold it in custody or promise delivery without giving its holder direct control of a Bitcoin output. Spot fund shares, wrapped tokens and derivatives are also distinct from one another.

Why people use these products—and why this project excludes them
ProductPossible benefitMaterial risks and limits
Wrapped BTC / bridgesUse BTC-linked value in another network’s applications or as collateral.Custodian or bridge failure, reserve shortfall, contract exploits, redemption restrictions and liquidation in collateralized applications. A claimed 1:1 backing is not a native BTC output under the holder’s key.[52]
USD stablecoinsToken transfers with a target nominal fiat value; integration with digital markets.Retain USD exposure and add issuer, reserve, bank, eligibility, freezing and depegging risks. A peg is a mechanism or promise, not certainty.[53]
Spot Bitcoin ETF / trust sharesBrokerage access and outsourced custody for Bitcoin price exposure.Fees, custody and legal-structure risks, trading-hours constraints and possible premium/discount. Investor rights follow the product documents; owning shares is not holding a private key. Spot shares are not themselves futures.[54]
FuturesHedge a price exposure or take a position without immediate spot delivery.Margin, liquidation, basis and rollover risk; settlement and counterparty rules matter. CME’s referenced Bitcoin contract is cash settled, not a means of redeeming a copper coin.[55][56]
OptionsShape exposure; a purchased, fully paid option can bound the option buyer’s loss to the premium and costs.Expiry, time decay, pricing complexity, liquidity and exercise terms. Uncovered writers can face much larger losses. Buying an option does not protect against every treasury risk.[56]
Perpetuals and leveraged productsContinuous directional exposure or a hedge without a conventional expiry.Funding payments, mark-price/oracle design, collateral rules, forced liquidation and platform insolvency. Terms vary; advertised leverage magnifies error as well as gains.
Lending and “yield” accountsPotential interest or rewards from lending, market-making or collateral use.Credit/default, rehypothecation, withdrawal freezes and legal priority in insolvency; sometimes additional smart-contract risk. Native Bitcoin does not pay protocol staking interest merely for being held.

Perpetual and lending risks above are structural analysis, not an audit of any named provider. Their exact terms would require a separate review. All listed products are excluded from this project’s reserve, even when used elsewhere for legitimate hedging or convenience.

Ethical precision matters. The Vatican’s Oeconomicae et pecuniariae quaestiones recognizes a risk-insurance role for derivatives while criticizing opaque, risk-distorting complexity. The project chooses a stricter BTC-only mandate; it does not attribute a blanket ecclesiastical prohibition to that text.[22]

04BITCOIN ITSELF & ITS PAYMENT LAYERS

Distinguish an upgrade from a substitute.

CONSENSUS IMPROVEMENTS

SegWit & Taproot

These adopted changes operate within Bitcoin mainnet. They demonstrate why “no rule has ever changed” would be an inaccurate definition of BTC.[3][5]

BTC PAYMENT PROTOCOL

Lightning

Channels move BTC off-chain with on-chain enforcement. Useful for fast, small payments, they require different liquidity, monitoring and recovery practices from an untouched cold reserve.[16][17]

PROVIDER RELATIONSHIP

A custodial balance

A provider may use Bitcoin or Lightning while retaining control of the actual keys. Its customer balance is a claim on that provider. Product branding alone does not resolve custody.[9]

The project reserve mandate is native BTC on mainnet. No Lightning service or other layer is enabled by these pages. Any future operational payment method would require explicit review of its custody, liquidity, recovery and accounting; it cannot silently replace the reserve.

05CONVENTIONAL MONEY & REMAINING RISK

Reject exposure without claiming certainty.

The project disavows USD and other conventional currency exposure as a treasury or redemption substitute. This is a chosen mandate, not a scientific finding that conventional money has no useful functions or that BTC has no uncertainty.

Why the project excludes it

Fiat value depends on monetary policy and economic conditions; balances held through institutions add institutional exposure. The Federal Reserve’s longer-run objective is 2% PCE inflation—not a promise that current or future inflation will equal 2%. The project avoids fiat pegs, automatic exchange and fiat-denominated guarantees.[57]

It also rejects outside trade, lending or custody arrangements that pledge the project’s BTC, alter the agreed asset, or introduce obligations contributors did not authorize. These exclusions should be reflected in signed contribution and custody terms.

What the exclusion cannot solve

BTC’s purchasing power still changes. Fees, operational costs, legal obligations and real-world counterparties remain. A BTC-only treasury cannot promise the same future quantity of food, labor, electricity or any other good.[41]

Conventional banking can offer familiar payment and accounting functions and, for eligible deposits, statutory insurance. FDIC coverage has limits and conditions; it does not insure BTC or guarantee any asset’s market price. Acknowledging those protections is compatible with choosing not to use fiat for this project.[58]

No fixed-value redemption promise. The project should never promise that a donated BTC amount will retain a fixed USD price or fixed purchasing power. Donor restrictions, legal reporting and prudent stewardship still apply. Disavowal of an asset does not waive obligations to people.[42][19]

06SOURCE ANNOTATIONS

Evidence before allegiance.

The same reference set supports both project pages. Each record identifies the authority, reading scope and limitations. The list is curated and expandable, not a claim to cover every serious publication.

58 of 58 references · reviewed 9 October 2026

1Bitcoin: A Peer-to-Peer Electronic Cash SystemSatoshi Nakamoto · 2008Foundations

Foundational design for peer-to-peer electronic cash and double-spend resistance.

Reading scope
All nine pages, emphasizing §§2–6, 8 and 10–11.
Limits
A conditional model, not the complete modern consensus specification or a promise of purchasing power.
Read the original source ↗
2Bitcoin Core PR 3842: stop subsidy after 64 halvingsPieter Wuille · 2014-04-03Foundations

The deployed change prevents undefined large right shifts from allowing subsidy calculation to restart after 64 halvings.

Reading scope
BIP metadata, details, proposal, implementation reference; PR3842 title, merge event, initial technical description and relevant implementation discussion.
Limits
BIP42 is written in April Fool's satire around a real implementation fix. Its satirical assertions about Nakamoto's motives and future dates must not be presented as historical evidence.
Locator / date note
Merge date; associated BIP 42 uses satire.
Read the original source ↗
3BIP 141: Segregated Witness (Consensus layer)Eric Lombrozo, Johnson Lau, Pieter Wuille · 2015-12-21Foundations

The document marks SegWit as deployed and as a consensus soft fork.

Reading scope
Metadata, abstract, motivation.
Limits
Benefits depend on transaction/script use and adoption; this is not a claim that every transaction becomes private or that all malleability is eliminated.
Locator / date note
BIP assignment, not activation date
Read the original source ↗
4BIP 340: Schnorr Signatures for secp256k1Pieter Wuille, Jonas Nick, Tim Ruffing · 2020-01-19Foundations

The deployed specification defines 64-byte Schnorr signatures over secp256k1.

Reading scope
Metadata, abstract and motivation.
Limits
Proofs rely on their assumptions; they do not eliminate implementation, key generation, custody, or future cryptanalytic risk.
Locator / date note
BIP assignment
Read the original source ↗
5BIP 341: Taproot: SegWit version 1 spending rulesPieter Wuille, Jonas Nick, Anthony Towns · 2020-01-19Foundations

The deployed consensus soft fork introduces a SegWit v1 output type using Taproot, Schnorr signatures and Merkle branches.

Reading scope
Metadata, abstract, motivation, initial design.
Limits
Reduced script disclosure is not anonymity, and a transaction remains part of a public ledger.
Locator / date note
BIP assignment
Read the original source ↗
6The Bitcoin Backbone Protocol: Analysis and ApplicationsJuan Garay, Aggelos Kiayias, Nikos Leonardos · 2015-04-14Research

Formalizes common-prefix and chain-quality properties in a static-participant model with a random-oracle treatment of hashing.

Reading scope
Actual EUROCRYPT 2015 conference PDF pp.281–284 (PDF pp.1–4): abstract, introduction, assumptions, results overview. Also ePrint abstract/revision metadata and Edinburgh publication record.
Limits
A formalized core model is not a proof covering all current Bitcoin code, real-world network behavior, fees or economic outcomes.
Read the original source ↗Inspected accessible version ↗

DOI: 10.1007/978-3-662-46803-6_10

7Majority Is Not Enough: Bitcoin Mining Is VulnerableIttay Eyal, Emin Gün Sirer · 2014Research

Under its model, strategic block withholding can yield more relative revenue than the miner's hashpower share.

Reading scope
Preprint abstract; sections 3–4 including modeling, strategy, relative-revenue threshold, simulation; sections 8–9 discussion/conclusion.
Limits
This is an analytical model with simulation, not a measured claim that present Bitcoin has collapsed or that a third of miners can forge anyone's signature.
Read the original source ↗Inspected accessible version ↗

DOI: 10.1007/978-3-662-45472-5_28

8On the Instability of Bitcoin Without the Block RewardMiles Carlsten, Harry Kalodner, S. Matthew Weinberg, Arvind Narayanan · 2016-10-24Research

Models fee-dominated mining and identifies undercutting and selfish-mining incentives absent or weaker under fixed subsidies.

Reading scope
Institutional abstract; extended author-version PDF pp.1–3 introduction, contribution summaries, explicit simulator limitations, related work. PDF identifies itself as an extended version of the ACM CCS 2016 paper.
Limits
Authors say accurate prediction of steady-state miner behavior is not their goal; simulator cannot model mining pools or nonconstant transaction arrivals.
Read the original source ↗Inspected accessible version ↗

DOI: 10.1145/2976749.2978408

9Securing your walletBitcoin.org contributors · Living documentationCustody

Separate small operational balances from savings; make comprehensive backups in multiple secure locations and plan succession.

Reading scope
Main guidance from online services through testament: backup, offline signing, hardware wallets, updates, multisignature, succession.
Limits
General educational guidance; product and setup quality matter.
Locator / date note
Living project guidance, accessed 2026-10-09
Read the original source ↗
10Frequently Asked Questions — Electrum documentationElectrum project · Living documentationCustody

Import adds existing key control; sweeping makes a transaction that sends its funds to an address derived from the destination wallet's seed.

Reading scope
Private-key import, watching-only and sweep subsections.
Limits
A sweep incurs normal network fees and requires valid spending authority.
Locator / date note
Living documentation, accessed 2026-10-09
Read the original source ↗
11BIP 380: Output Script Descriptors General OperationPieter Wuille, Ava Chow · 2021-06-27Custody

Keys alone can omit script type and derivation details necessary for reliable recovery; descriptors specify that missing structure.

Reading scope
BIP metadata, abstract, motivation, script/key expressions, checksum; Bitcoin Core descriptor features, examples, reference, key-origin/private-key and checksum sections.
Limits
Public descriptors can reveal the wallet's address set and transaction history; secret-bearing descriptors can authorize spending.
Locator / date note
BIP assignment
Read the original source ↗
12Bitcoin Core 30.0 RPC: importdescriptorsBitcoin Core contributors · Living documentationCustody

Importing descriptors triggers a rescan based on timestamp and requires a new backup.

Reading scope
RPC description, timestamp/rescan behavior, arguments and backup warning.
Limits
Do not treat an incomplete rescan or an insufficient historical range as proof that funds never existed.
Read the original source ↗
13Setup a connected hardware walletSparrow Wallet project · Living documentationCustody

Initialize a new wallet under your control and securely preserve the device-generated recovery material.

Reading scope
Hardware wallet rationale, connected/airgapped, ordering, initialization, public-key import, receiving and sending checks.
Limits
Supplier instructions differ and must be followed for the actual model.
Locator / date note
Living software documentation, accessed 2026-10-09
Read the original source ↗
14Best PracticesSparrow Wallet project · Living documentationCustody

For its advanced cold-storage workflow, Sparrow recommends at least 2-of-3 multisignature, multiple hardware vendors, and separated secure locations and backups.

Reading scope
Privacy/server discussion and Expert Stage custody guidance.
Limits
Vendor/project guidance is not a universal audited standard or guarantee.
Locator / date note
Living software guidance, accessed 2026-10-09
Read the original source ↗
15BIP 65: OP_CHECKLOCKTIMEVERIFYPeter Todd · 2014-10-01Custody

A locking script can prohibit spending an output before the specified block height or block time.

Reading scope
Metadata, abstract, summary, motivation, escrow and freezing-funds examples.
Limits
A published human rule does not alter an already funded output's locking conditions.
Locator / date note
BIP assignment
Read the original source ↗
16BOLT #0: Introduction and IndexLightning specification contributors · Living documentationCustody

Lightning is a layer-2 protocol for off-chain bitcoin transfers with on-chain enforcement when necessary.

Reading scope
Introduction, channels, conditional payments, forwarding.
Limits
Software/provider custody models differ. A custodial Lightning balance adds reliance on the provider.
Locator / date note
Living specification; version 0 as displayed; accessed 2026-10-09
Read the original source ↗
17The Bitcoin Lightning Network: Scalable Off-Chain Instant PaymentsJoseph Poon, Thaddeus Dryja · 2016-01-14Custody

The original design identifies timing, mass channel-expiration pressure, hot-key compromise, state loss, and late on-chain response as risk classes.

Reading scope
Title/abstract; sections 8.4–8.5 and 9.1–9.5 (PDF pp.48–51).
Limits
The 2016 draft is historical design material, not the complete current implementation specification.
Read the original source ↗
18Catechism of the Catholic Church: Universal destination and private ownership of goodsCatholic Church · 1992; official English web textCatholic teaching

Legitimate property serves freedom and basic needs, while ownership entails stewardship and the universal destination of goods.

Reading scope
Opened text and read relevant paragraphs 2402-2404; not entire Catechism.
Limits
Application to digital assets is editorial interpretation; text gives no cryptocurrency endorsement.
Locator / date note
2402-2404
Read the original source ↗
19Catechism of the Catholic Church: Respect for persons and their goodsCatholic Church · 1992; official English web textCatholic teaching

Condemns fraud, manipulative speculation and misuse of common assets; requires just promises, contracts, debts and restitution to be honored.

Reading scope
Relevant paragraphs 2407-2412 retrieved and read.
Limits
The criticism of speculation in 2409 concerns artificial price manipulation to others’ detriment; do not describe every investment or price risk as forbidden.
Locator / date note
2407-2412, especially 2409-2411
Read the original source ↗
20Compendium of the Catechism of the Catholic ChurchCatholic Church · 2005Catholic teaching

Profit cannot be the exclusive end; business managers owe responsibility for economic and ecological effects and the good of people.

Reading scope
Relevant questions and surrounding excerpt only.
Limits
This is the official Compendium summary, not a full reading of the referenced Catechism chapters.
Locator / date note
Questions 512 and 516; referring to CCC 2424-2425 and 2432
Read the original source ↗
21Caritas in VeritatePope Benedict XVI · 2009-06-29Catholic teaching

Finance should serve development. Ethical labels require discernment; responsible innovation, protecting weaker parties and discouraging abusive speculation matter.

Reading scope
Relevant paragraphs 45, 65-66 and selected surrounding passages.
Limits
It supports ethical financial activity and regulation, not blanket rejection of conventional trade or any named currency.
Locator / date note
45 and 65-66
Read the original source ↗
22Oeconomicae et pecuniariae quaestionesCongregation for the Doctrine of the Faith and Dicastery for Promoting Integral Human Development · 2018-01-06Catholic teaching

Recognizes derivatives can insure identifiable risks; warns that layered complexity can obscure valuation and distort risk. Calls for social responsibility in saving and investing.

Reading scope
Derivatives discussion at paragraph 26, concluding social-responsibility passages and approval/date; selected surrounding passages.
Limits
Does not declare all derivatives intrinsically immoral. No Bitcoin reference found in searchable text.
Locator / date note
26; 33-34; closing date and approval
Read the original source ↗
23Laudato Si’Pope Francis · 2015-05-24Catholic teaching

Calls for less harmful energy, transparent early environmental assessment, local participation, comparison of alternatives and precaution regarding serious irreversible harms.

Reading scope
Relevant paragraphs 165 and 182-186 retrieved and read.
Limits
Does not evaluate Bitcoin specifically or establish that all Bitcoin mining is either clean or unacceptable.
Locator / date note
165 and 182-186
Read the original source ↗
24Fratelli TuttiPope Francis · 2020-10-03Catholic teaching

Property has a social purpose, people deserve dignity and opportunity, and markets alone do not solve every social problem.

Reading scope
Relevant property, dignity and market passages only.
Limits
An application to the project, not a Bitcoin-specific Church judgment.
Locator / date note
118-122 and 168
Read the original source ↗
25Antiqua et Nova: Note on the Relationship Between Artificial Intelligence and Human IntelligenceDicastery for the Doctrine of the Faith and Dicastery for Culture and Education · 2025-01-28Catholic teaching

Humans retain moral responsibility for AI-assisted decisions; accountability, transparency, robustness and environmental costs require attention.

Reading scope
Human accountability passages 44-46, environmental passage 96 and closing approval/date.
Limits
It concerns AI, not Bitcoin. Applying it to an AI-assisted treasury workflow is explicit editorial analogy. No Bitcoin reference found.
Locator / date note
44-46 and 96; closing approval/date
Read the original source ↗
26Magnifica HumanitasPope Leo XIV · 2026-05-15Catholic teaching

Applies subsidiarity to digital power through transparency, accountability, participation and independent checks; prioritizes human dignity, solidarity and protection of the vulnerable.

Reading scope
Selected common-good, property, subsidiarity, digital-power and AI passages; official title, index and closing date verified. Not a full scholarly reading of the encyclical.
Limits
No Bitcoin reference found. Does not endorse Bitcoin, Blockchain Mint, BTC-only policy or rejection of USD.
Locator / date note
60-72; 95-99; closing date
Read the original source ↗
27Cambridge study: sustainable energy rising in Bitcoin miningCambridge Judge Business School / Cambridge Centre for Alternative Finance · 2025-04-28Research

A survey of 49 firms covering 48% of mining activity estimated 138 TWh annual network electricity and 39.8 MtCO2e emissions. Reported sustainable mix was 52.4%: 42.6% renewable plus 9.8% nuclear.

Reading scope
University’s own report summary, including sample and headline estimates. Underlying PDF retrieval exceeded web tool size limit; not fully read.
Limits
Survey-derived extrapolation, not a live 2026 measurement or randomized census. Do not label 52.4% as renewables or infer zero emissions.
Read the original source ↗
28From Mining to Mitigation: How Bitcoin Can Support Renewable Energy Development and Climate ActionApoorv Lal, Jesse Zhu, Fengqi You · 2023-10-27Research

Models possible mining revenue at planned renewable installations before grid connection; benefits depend on location and electricity availability. Also acknowledges hardware obsolescence and material costs.

Reading scope
Cornell’s own account of its research; journal metadata and abstract search excerpt. Full journal text blocked by publisher.
Limits
Modeled potential, not demonstrated economy-wide emissions savings. Conditions and counterfactual uses of electricity matter.
Read the original source ↗Inspected accessible version ↗

DOI: 10.1021/acssuschemeng.3c05445

29The environmental burden of the United States’ bitcoin mining boomGianluca Guidi et al. · 2025-03-26Research

Models 34 large US mines: estimated 32.3 TWh consumption and 1.9 million people exposed to at least 0.1 micrograms/m3 of additional PM2.5. These are model estimates for a historical sample.

Reading scope
Primary PDF downloaded; abstract/results and pages 7-8 (sensitivity analyses, limitations and methods) read. Not a reproduction of supplementary analyses.
Limits
Uses estimated capacity/uptime, WattTime marginal grid response and InMAP dispersion. Rural estimates less precise; authors note possible Texas hotspot overestimation. Full supplement not audited; not a current global census.
Locator / date note
Pages 1 and 7-8; study period August 2022-July 2023
Read the original source ↗

DOI: 10.1038/s41467-025-58287-3

30Cold Storage Coins: FAQBlockchain Mint · Living manufacturer guidanceCustody

Describes manufacturer-generated keys and single-use redemption. Advises redeeming a preloaded coin promptly.

Reading scope
FAQ, key generation and preloaded-coin guidance.
Limits
Manufacturer representations; no independent key-deletion audit established.
Read the original source ↗
31Add valueBlockchain Mint · Living manufacturer guidanceCustody

Public address lookup and CoinID help identify the intended receiving address.

Reading scope
Address lookup and deposit instructions.
Limits
A short CoinID is not the full receiving address; a lookup cannot prove key exclusivity.
Read the original source ↗
32Redeem valueBlockchain Mint · Living manufacturer guidanceCustody

Explains uncovering the etched key and retiring the exposed coin address.

Reading scope
Seal removal and redemption guidance.
Limits
Some instructions mention online QR creation. Never submit a private key to an online QR service; use verified offline tools.
Read the original source ↗
33Security sealBlockchain Mint · Living manufacturer claimsCustody

Describes a KURZ/OVD Kinegram tamper-evident seal.

Reading scope
Seal description and claimed protections.
Limits
Tamper evidence is not tamper impossibility, key exclusivity, or proof of recoverability.
Read the original source ↗
34BEVIS authenticationBlockchain Mint · Living manufacturer documentationCustody

Describes asset provenance and certificate anchoring, including Bitcoin Cash.

Reading scope
Provenance description.
Limits
Vendor certificates are distinct from Bitcoin mainnet custody. This project does not adopt BCH or the vendor’s other asset offerings.
Read the original source ↗
35Cold Storage Coins product listingsBlockchain Mint · Listing observed during this researchAssets & markets

A standard copper BTC wallet was listed at US$19.95 during the initial review.

Reading scope
Retail listing only; not completed secondary-market sales.
Limits
Historical asking-price context, not a current quote, specimen appraisal, or BTC redemption value.
Read the original source ↗
36Cold Storage Coins assessmentWalletScrutiny · Living independent assessmentCustody

Flags manufacturer-provided private keys: deletion by the provider cannot be independently established.

Reading scope
Provided Keys finding and methodology.
Limits
An architectural trust finding, not proof that this mint stole funds; the review stops at that criterion.
Read the original source ↗
37Cold Storage Coins destructive storage testJameson Lopp · Published test recordResearch

The tested specimen’s private-key markings became unreadable under destructive heat testing.

Reading scope
Test observations and author’s stated heat limitation.
Limits
A small independent test, not certification. The author notes temperatures may have exceeded the maker’s claims.
Read the original source ↗
38Caring for your coin collectionUnited States Mint · Living conservation guidanceCustody

Avoid cleaning collectible coins; use protective holders and avoid PVC and acidic storage materials.

Reading scope
Handling, cleaning and storage guidance.
Limits
General coin conservation, not a test of this product’s adhesive or sealed-key fire resistance.
Read the original source ↗
39Transactions: locking scripts and multisignatureBitcoin Developer Guide · Living technical guideCustody

An output’s spending conditions govern which signatures authorize a valid spend.

Reading scope
Locking scripts and multisignature sections.
Limits
The protocol cannot infer an organization’s unpublished donor conditions or charitable purpose.
Read the original source ↗
40Cold storageElectrum project · Living documentationCustody

Explains online watch-only preparation and offline transaction signing.

Reading scope
Cold-storage workflow.
Limits
Operational example; verify the actual software and current release before use.
Read the original source ↗
41Some things you need to knowBitcoin.org contributors · Living project guidanceFoundations

Discusses price volatility, irreversible payments, public history and confirmations.

Reading scope
Risk and payment guidance.
Limits
Education, not a guarantee of safety or a personalized investment recommendation.
Read the original source ↗
42Minnesota Statutes §309.74Minnesota Revisor of Statutes · 2025 codification displayed; checked 2026-10-09Governance

Qualifying institutional funds are subject to donor intent and prudent management, including a diversification rule with a stated exception.

Reading scope
Full section.
Limits
Applicability depends on the institution and fund. A BTC-only statement alone does not resolve fiduciary duties.
Read the original source ↗
43Minnesota Statutes §309.735Minnesota Revisor of Statutes · Current displayed codificationGovernance

Definitions include gift instruments and institutional funds.

Reading scope
Relevant definitions.
Limits
Scope must be evaluated for the actual legal entity and solicitation.
Read the original source ↗
44Minnesota Statutes §309.755Minnesota Revisor of Statutes · Current displayed codificationGovernance

Provides mechanisms and conditions for release or modification of qualifying restrictions.

Reading scope
Restriction modification provisions.
Limits
A website edit or custodian signature is not a substitute for applicable legal requirements.
Read the original source ↗
45Bitcoin Cash projectBitcoin Cash contributors · Living project descriptionAssets & markets

Describes the 2017 Bitcoin chain split and an emphasis on larger on-chain capacity.

Reading scope
Project description and split history.
Limits
Project advocacy is evidence of design intent, not independent proof of superior security.
Read the original source ↗
46Bitcoin’s divergence: BCH and BSVBSV Blockchain Academy · Living project historyAssets & markets

Documents the 2018 split from BCH into BSV.

Reading scope
Fork history.
Limits
A project account, not acceptance of its claim to be the uniquely original Bitcoin.
Read the original source ↗
47Genesis settingsBSV Blockchain documentation · Living implementation guidanceAssets & markets

Documents changed block-limit settings and operator configuration.

Reading scope
Genesis configuration.
Limits
Capacity claims must be separated from security, decentralization and economic outcomes.
Read the original source ↗
48Litecoin source treeLitecoin contributors · Living project sourceAssets & markets

A separate currency and codebase adapted from Bitcoin.

Reading scope
Project README and source identity.
Limits
Code ancestry is not shared BTC ownership or identical rules.
Read the original source ↗
49Dogecoin source tree and lineageDogecoin contributors · Living project sourceAssets & markets

A separate code-derived currency; not Bitcoin mainnet.

Reading scope
Project README and lineage.
Limits
Brand or code similarities do not make DOGE BTC.
Read the original source ↗
50Dogecoin inflationDogecoin project · Living project explanationAssets & markets

Explains continuing issuance of roughly five billion coins annually.

Reading scope
Issuance explanation.
Limits
Its spending rationale is project advocacy; continuing issuance does not ensure price stability.
Read the original source ↗
51Proof of stakeEthereum.org contributors · Living technical documentationAssets & markets

Explains Ethereum’s stake-based validation, penalties and slashing.

Reading scope
Consensus overview.
Limits
Ethereum is included for comparison; it is not a Bitcoin chain fork. Applications add their own risks.
Read the original source ↗
52Wrapped Bitcoin whitepaperWBTC project · Living issuer documentationAssets & markets

Describes token issuance and custody of backing BTC.

Reading scope
Custodians, merchants, minting and redemption.
Limits
A reserve or token balance does not confer direct Bitcoin mainnet key control; custody arrangements can change.
Read the original source ↗
53USDC risk factorsCircle · Living issuer termsAssets & markets

Discloses redemption, issuer, technology and value risks.

Reading scope
Issuer risk disclosures.
Limits
USD-linked tokens retain fiat exposure and can face depegging, eligibility limits and freezing.
Read the original source ↗
54iShares Bitcoin Trust ETFBlackRock / iShares · Living issuer informationAssets & markets

Provides exchange-traded Bitcoin price exposure through a trust and custodian.

Reading scope
Product structure, fees and risk disclosures.
Limits
Shares are securities, not a privately controlled BTC UTXO; applicable redemption rights depend on the prospectus and participant role.
Read the original source ↗
55Bitcoin futures launch and settlementCME Group · 2017-12-01Assets & markets

Describes cash-settled Bitcoin futures tied to a reference rate.

Reading scope
Contract structure and settlement.
Limits
Historical launch terms; consult the current contract specification before any real transaction.
Read the original source ↗
56Uniform futures and options risk disclosureFutures Industry Association / CME · Published risk disclosureAssets & markets

Margin, leverage, market disruption and option-writing can create substantial losses.

Reading scope
Risk disclosure.
Limits
Not all contracts have identical collateral or settlement terms; losses can exceed initial margin.
Read the original source ↗
57Why aim for 2 percent inflation?Federal Reserve · Living policy explanationAssets & markets

Explains the FOMC’s longer-run 2% PCE inflation objective.

Reading scope
Policy explanation.
Limits
An objective is not a prediction, guarantee or measurement of current inflation.
Read the original source ↗
58Understanding deposit insuranceFederal Deposit Insurance Corporation · Living official guidanceAssets & markets

Explains insurance for qualifying deposits at insured banks.

Reading scope
Coverage and ownership categories.
Limits
Coverage has limits and conditions; it does not insure BTC, tokens, securities, or their market prices.
Read the original source ↗

This is a curated, expandable editorial reference set, not an exhaustive review of all scholarship or Church commentary. Reading scope is stated per source. Crossref metadata verification is distinct from reading a paper. Sources may support, qualify or challenge the project; inclusion is not endorsement. Search runs in your browser.

SPARK HOUSE · RESEARCH & COMMUNITY STEWARDSHIPEvidence reviewed 9 October 2026