-
Notifications
You must be signed in to change notification settings - Fork 8
Expand file tree
/
Copy pathreadme.txt
More file actions
executable file
·86 lines (59 loc) · 3.66 KB
/
readme.txt
File metadata and controls
executable file
·86 lines (59 loc) · 3.66 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
=== WordProof Timestamp ===
Contributors: wordproof
Tags: blockchain, timestamp, eosio, eos, telos, web30, copyright, scatter, decentralisation, proof
Requires at least: 5.8
Tested up to: 6.5
Requires PHP: 7.3
Stable tag: 3.0.15
License: GPLv3 or later
License URI: http://www.gnu.org/licenses/gpl-3.0.html
Timestamp your WordPress content on the blockchain for protection and trust. No blockchain knowledge required.
== Description ==
### WordProof: Timestamp your WordPress Content on the Blockchain
With WordProof Timestamp, you can timestamp your WordPress content on any EOSIO blockchain from the comfort of your WordPress site. No prior blockchain experience necessary. After the set-up, everything is taken care of automatically!
### Why do I need to timestamp my content?
WordProof Timestamp does everything in its power to bring the benefits of blockchain to your WordPress website. Here are some reasons why you should timestamp your content:
- Copyright protection
- Transparency: increase trust and claim authenticity
- Next-generation SEO benefits
- Proof of existence at certain moments in time
- Prepare for upcoming EU regulations
- Be your own notary
### Features
- Automatically timestamp your content on the blockchain
- Show the blockchain certificate pop-up on your website
- Let your visitors verify when and how your content changed
- Downloadable blockchain certificate as proof of existence
### How does WordProof Timestamp work?
Timestamping creates a unique and universal fingerprint (the 'hash') for all your posts, pages and media files. If the input changes, the hash becomes totally different.
This hash is added to the blockchain with a date and time. Because you (the website owner) have the input that results in this specific hash, you can prove that you published the content at that point in time.
### Further Reading on WordProof, WordPress, and Blockchain
For more info on WordProof, WordPress, and Blockchain, check out the following:
* The [WordProof Plugin official homepage](https://wordproof.io/ "WordProof: The WordPress Timestamp Plugin").
* [WordPress and Blockchain – The Manifest for a 100% Open Source Future](https://medium.com/wordproof "WordProof: WordPress and Blockchain") by Sebastiaan van der Lans.
* Join the [WordProof Telegram](https://t.me/WordProof) for feedback, updates and support.
Special thanks to the Telos Foundation for co-funding a first version WordProof via their [Worker Proposal System](https://medium.com/wordproof "Truly inclusive Open Source funding via Worker Proposal Systems.").
== Installation ==
=== From within WordPress ===
1. Visit 'Plugins > Add New'
1. Search for 'WordProof'
1. Activate WordProof Timestamp from your Plugins page.
1. Go to "after activation" below.
=== Manually ===
1. Upload the `wordproof-timestamp` folder to the `/wp-content/plugins/` directory
1. Activate the WordProof Timestamp plugin through the 'Plugins' menu in WordPress
1. Go to "after activation" below.
=== After activation ===
1. Authenticate using your WordProof account
== Screenshots ==
1. Timestamp your content automatically, verify the status in the bottom right corner.
2. The pop-up your visitors can use to verify your content.
3. Your visitors can compare different versions, and verify the authenticity.
4. Change the settings in the WordProof Timestamp plugin options panel.
== Changelog ==
= 3.0.15 =
*Release date: May 7th, 2024*
* Updated for latest WordPress version.
== Upgrade Notice ==
= 3.0.0 =
The is a major overhaul of the plugin. After upgrading, you need to login with your WordProof account again. On sites with a large number of timestamps the migration will take longer. This process will be done in the background.