<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://en.bitcoin.it/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Louison</id>
	<title>Bitcoin Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://en.bitcoin.it/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Louison"/>
	<link rel="alternate" type="text/html" href="https://en.bitcoin.it/wiki/Special:Contributions/Louison"/>
	<updated>2026-05-18T05:10:45Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.8</generator>
	<entry>
		<id>https://en.bitcoin.it/w/index.php?title=Proof_of_Ownership&amp;diff=54775</id>
		<title>Proof of Ownership</title>
		<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=Proof_of_Ownership&amp;diff=54775"/>
		<updated>2015-03-01T13:04:58Z</updated>

		<summary type="html">&lt;p&gt;Louison: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Proof of Ownership&#039;&#039;&#039; is a method that uses Bitcoin&#039;s decentralized ledger (also called [https://en.bitcoin.it/wiki/Block_chain blockchain]) or Bitcoin-related technologies to track the different owners of a certain information over the time.&lt;br /&gt;
&lt;br /&gt;
This technique can be used by artists or businesses to certify the integrity, date of publication and ownership of their creations or contracts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Technology ==&lt;br /&gt;
=== Using the Bitcoin blockchain ===&lt;br /&gt;
The Bitcoin Core protocol now accepts raw data transactions up to 40 bytes per output using the opcode &#039;&#039;&#039;OP_RETURN&#039;&#039;&#039;.&lt;br /&gt;
Putting the hash of the signature of a file&#039;s hash in the blockchain makes the owner of the private key associated with the signature the owner of the file in the blockchain (as long as someone else doesn&#039;t show up with a proof certified before).&lt;br /&gt;
&lt;br /&gt;
=== Using a new blockchain ===&lt;br /&gt;
It&#039;s also possible to create a new blockchain for this purpose. This blockchain wouldn&#039;t only store coins but also notarized proofs. &lt;br /&gt;
&lt;br /&gt;
== Content of a proof ==&lt;br /&gt;
=== Ownership ===&lt;br /&gt;
Only the people with the private key associated with the signature can prove they are the owner.&lt;br /&gt;
&lt;br /&gt;
=== Existence ===&lt;br /&gt;
A Proof of Ownership is always attached to a piece of data. Certifying the ownership of a certain information in the blockchain also proves that this information existed at a certain time.&lt;br /&gt;
&lt;br /&gt;
=== Integrity ===&lt;br /&gt;
A Proof of Ownership is always attached to a piece of data using cryptographic functions. This makes it impossible to alter the data after certification. If the content is modified, even by a single bit, then the whole certificate becomes invalid.&lt;br /&gt;
&lt;br /&gt;
=== Authenticity ===&lt;br /&gt;
Because proofs are logged in the blockchain, it makes it easy to make transfers of ownership and find the original issuer of a certificate. Certificates can’t be “[https://en.bitcoin.it/wiki/Double-spending double-spent]”.&lt;br /&gt;
&lt;br /&gt;
== Usages ==&lt;br /&gt;
* [https://bitproof.io/ bitproof.io] - Certify your files and ideas for free in the Bitcoin blockchain&lt;br /&gt;
* [http://coinsecrets.org/ coinsecrets.org] - list of metadata recently embedded in the bitcoin blockchain using OP_RETURN outputs.&lt;br /&gt;
* [https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/advanced.js#L24 github.com] Creating OP_RETURN transactions in the blockchain&lt;br /&gt;
&lt;br /&gt;
[[Category:Proof-of-x]]&lt;/div&gt;</summary>
		<author><name>Louison</name></author>
	</entry>
	<entry>
		<id>https://en.bitcoin.it/w/index.php?title=Proof_of_Ownership&amp;diff=54774</id>
		<title>Proof of Ownership</title>
		<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=Proof_of_Ownership&amp;diff=54774"/>
		<updated>2015-03-01T12:51:04Z</updated>

		<summary type="html">&lt;p&gt;Louison: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Proof of Ownership&#039;&#039;&#039; is a method that uses the Bitcoin&#039;s decentralized ledger (also called [https://en.bitcoin.it/wiki/Block_chain blockchain]) or Bitcoin-related technologies to track the different owners of a certain information over the time.&lt;br /&gt;
&lt;br /&gt;
This technique can be used by artists or businesses to certify the integrity, date of publication and ownership of their creations or contracts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Technology ==&lt;br /&gt;
=== Using the Bitcoin blockchain ===&lt;br /&gt;
The Bitcoin Core protocol now accepts raw data transactions up to 40 bytes per output using the opcode &#039;&#039;&#039;OP_RETURN&#039;&#039;&#039;.&lt;br /&gt;
Putting the hash of the signature of a file&#039;s hash in the blockchain makes the owner of the private key associated with the signature the owner of the file in the blockchain (as long as someone else doesn&#039;t show up with a proof certified before).&lt;br /&gt;
&lt;br /&gt;
=== Using a new blockchain ===&lt;br /&gt;
It&#039;s also possible to create a new blockchain for this purpose. This blockchain wouldn&#039;t only store coins but also notarized proofs. &lt;br /&gt;
&lt;br /&gt;
== Content of a proof ==&lt;br /&gt;
=== Ownership ===&lt;br /&gt;
Only people with the private key associated with the proof can prove they are the owner.&lt;br /&gt;
&lt;br /&gt;
=== Existence ===&lt;br /&gt;
A Proof of Ownership is always attached to a piece of data. Certifying the ownership of a certain information in the blockchain also proves that this information was known/existed at a certain time.&lt;br /&gt;
&lt;br /&gt;
=== Integrity ===&lt;br /&gt;
The Proof of Ownership is always attached to a piece of data using cryptographic functions. This makes it impossible to alter the data after certification. If one single bit is modified, then the whole certificate becomes invalid.&lt;br /&gt;
&lt;br /&gt;
=== Authenticity ===&lt;br /&gt;
Because proofs are logged in the blockchain, it makes it easy to make transfers of ownership and find the original issuer of a certificate. Certificates can’t be “double-spent”.&lt;br /&gt;
&lt;br /&gt;
== Usages ==&lt;br /&gt;
* [https://bitproof.io/ bitproof.io] - Certify your files and ideas for free in the Bitcoin blockchain&lt;br /&gt;
* [http://coinsecrets.org/ coinsecrets.org] - list of metadata recently embedded in the bitcoin blockchain using OP_RETURN outputs.&lt;br /&gt;
* [https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/advanced.js#L24 github.com] Creating OP_RETURN transactions in the blockchain&lt;br /&gt;
&lt;br /&gt;
[[Category:Proof-of-x]]&lt;/div&gt;</summary>
		<author><name>Louison</name></author>
	</entry>
	<entry>
		<id>https://en.bitcoin.it/w/index.php?title=Proof_of_Ownership&amp;diff=54773</id>
		<title>Proof of Ownership</title>
		<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=Proof_of_Ownership&amp;diff=54773"/>
		<updated>2015-03-01T12:50:30Z</updated>

		<summary type="html">&lt;p&gt;Louison: Created page with &amp;quot;{{stub}}  &amp;#039;&amp;#039;&amp;#039;Proof of Ownership&amp;#039;&amp;#039;&amp;#039; is a method that uses the Bitcoin&amp;#039;s decentralized ledger (also called [https://en.bitcoin.it/wiki/Block_chain blockchain]) or Bitcoin-relate...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{stub}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Proof of Ownership&#039;&#039;&#039; is a method that uses the Bitcoin&#039;s decentralized ledger (also called [https://en.bitcoin.it/wiki/Block_chain blockchain]) or Bitcoin-related technologies to track the different owners of a certain information over the time.&lt;br /&gt;
&lt;br /&gt;
This technique can be used by artists or businesses to certify the integrity, date of publication and ownership of their creations or contracts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Technology ==&lt;br /&gt;
=== Using the Bitcoin blockchain ===&lt;br /&gt;
The Bitcoin Core protocol now accepts raw data transactions up to 40 bytes per output using the opcode &#039;&#039;&#039;OP_RETURN&#039;&#039;&#039;.&lt;br /&gt;
Putting the hash of the signature of a file&#039;s hash in the blockchain makes the owner of the private key associated with the signature the owner of the file in the blockchain (as long as someone else doesn&#039;t show up with a proof certified before).&lt;br /&gt;
&lt;br /&gt;
=== Using a new blockchain ===&lt;br /&gt;
It&#039;s also possible to create a new blockchain for this purpose. This blockchain wouldn&#039;t only store coins but also notarized proofs. &lt;br /&gt;
&lt;br /&gt;
== Content of a proof ==&lt;br /&gt;
=== Ownership ===&lt;br /&gt;
Only people with the private key associated with the proof can prove they are the owner.&lt;br /&gt;
&lt;br /&gt;
=== Existence ===&lt;br /&gt;
A Proof of Ownership is always attached to a piece of data. Certifying the ownership of a certain information in the blockchain also proves that this information was known/existed at a certain time.&lt;br /&gt;
&lt;br /&gt;
=== Integrity ===&lt;br /&gt;
The Proof of Ownership is always attached to a piece of data using cryptographic functions. This makes it impossible to alter the data after certification. If one single bit is modified, then the whole certificate becomes invalid.&lt;br /&gt;
&lt;br /&gt;
=== Authenticity ===&lt;br /&gt;
Because proofs are logged in the blockchain, it makes it easy to make transfers of ownership and find the original issuer of a certificate. Certificates can’t be “double-spent”.&lt;br /&gt;
&lt;br /&gt;
== Usages ==&lt;br /&gt;
* [https://bitproof.io/ bitproof.io] - Certify your files and ideas for free in the Bitcoin blockchain&lt;br /&gt;
* [http://coinsecrets.org/ coinsecrets.org] - list of metadata recently embedded in the bitcoin blockchain using OP_RETURN outputs.&lt;br /&gt;
* [https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/advanced.js#L24 github.com] Creating OP_RETURN transactions in the blockchain&lt;br /&gt;
&lt;br /&gt;
[[Category:Proof-of-x]]&lt;/div&gt;</summary>
		<author><name>Louison</name></author>
	</entry>
</feed>