Bitcoin Private Key Provenance Record

Primary Asset Details

Bitcoin Address:


                        1BMzWp77J7x3GKDYNbCP3df7YG3UEw1vVE

Key Owner / Identifier: @SatoshisVault – TheArtifactDrives.com

Asset Significance: 6,622.24696455 BTC

Date of Record (UTC): 2025-12-10T00:56:00Z

I. Cryptographic Proof

📝 A. Message Signed (Exact Content)


I am @SatoshisVault – TheArtifactDrives.com. I am the owner of this private key that moved 6622.24696455 BTC in 277 total transactions.

🔐 B. Signature (Base64 ECDSA)


HDrh2RAgI3KugsFUKxFvnrTrSUX9//tPdoZeJ16tZ6DSrlIcFqMd3G7+ywvQZu8TvN24HA/FBgO8Lz2qdTZg7z4=

II. Provenance Environment Details

Signing Client: Bitcoin-Qt v0.8.1.0 Beta (legacy client).
Wallet Structure: Legacy Berkeley DB wallet.
Schema Conformance: wallet.dat matches early Bitcoin Core schema.
Key Era: Key predates HD wallets, descriptors, and modern metadata.
Source File: wallet.dat (Berkeley DB 4.8), natively loaded by legacy client.

III. Verification & Historical Strength

A. Verification Process & Result

Verification Client: Bitcoin-Qt v0.8.1.0 Beta.
Result: Signature validated using early ECDSA logic.
Conclusion: Confirms historical authenticity and uninterrupted key continuity.

B. Cryptographic Significance

The native loading of the legacy wallet.dat in v0.8.1.0 and the successful sign + verify cycle, which modern wallets cannot reproduce using reconstructed files, constitutes exceptionally strong historical provenance.

IV. Independent Verification

This proof may be independently verified using the Bitcoin Core CLI.

$ bitcoin-cli verifymessage \ "1BMzWp77J7x3GKDYNbCP3df7YG3UEw1vVE" \ "HDrh2RAgI3KugsFUKxFvnrTrSUX9//tPdoZeJ16tZ6DSrlIcFqMd3G7+ywvQZu8TvN24HA/FBgO8Lz2qdTZg7z4=" \ "I am @SatoshisVault – TheArtifactDrives.com. I am the owner of this private key that moved 6622.24696455 BTC in 277 total transactions."

Expected Result: true