File:Bitcoin OpCheckSig InDetail.png: Difference between revisions

Revision as of 20:34, 12 January 2013

Summary

A full breakdown of the process to verify the Bitcoin ECDSA signature of a pair of transactions. Sadly, there are 2 decisive errors in the picture: In step 7: "empty string" is "byte 0" and in step 8: the Subscript copied into TxIn script must be lead-in by its length coded as a var-int.

Licensing

I, the copyright holder of this work, hereby publish it under the following license:

	This file is made available under the Creative Commons CC0 1.0 Universal Public Domain Dedication.
	The person who associated a work with this deed has dedicated the work to the public domain by waiving all of his or her rights to the work worldwide under copyright law, including all related and neighboring rights, to the extent allowed by law. You can copy, modify, distribute and perform the work, even for commercial purposes, all without asking permission. CC0 true false

File history

Click on a date/time to view the file as it appeared at that time.

	Date/Time	Dimensions	User	Comment
current	03:52, 13 January 2013	1,600 × 2,132 (384 KB)	Etotheipi (talk \| contribs)
	03:44, 13 January 2013	1,600 × 2,132 (387 KB)	Etotheipi (talk \| contribs)
	13:13, 14 August 2011	1,593 × 2,136 (362 KB)	Etotheipi (talk \| contribs)	A full breakdown of the process to verify the Bitcoin ECDSA signature of a pair of transactions.

You cannot overwrite this file.

File usage

The following page uses this file:

OP CHECKSIG

Metadata

This file contains additional information, probably added from the digital camera or scanner used to create or digitize it.

If the file has been modified from its original state, some details may not fully reflect the modified file.

Horizontal resolution	121.93 dpc
Vertical resolution	121.93 dpc
Software used	www.inkscape.org

@@ Line 1: / Line 1: @@
 == Summary ==
 A full breakdown of the process to verify the Bitcoin ECDSA signature of a pair of transactions.
-Sadly, there are '''2 decisive errors''' in the picture: In step 7: "empty string" is "byte 0" and in step 8: the Subscript copied into txin-script must be lead-in by its length coded as a var-int.
+Sadly, there are '''2 decisive errors''' in the picture: In step 7: "empty string" is "byte 0" and in step 8: the Subscript copied into TxIn script must be lead-in by its length coded as a var-int.
 == Licensing ==
 {{self|Cc-zero}}