Commit dc34c82a authored by Daniel Kraft's avatar Daniel Kraft

Update README a bit.

Includes a typofix thanks to Sean / something.
parent db7e8ed6
......@@ -57,9 +57,9 @@ in systems like this is double-spending: In addition to your message above,
you could also create a message that spends the very same balance to Bob
(or even back to yourself!). In this situation, the network needs a way to
determine which of the two transactions is the "correct" one. A simple
rule to determine this is to "use the earlier transaction". However, for this
to work, one needs a way to determine an absolute order of events on which
the network agrees upon.
rule to resolve this conflict is to "use the earlier transaction". However,
for this to work, one needs a way to determine an absolute order of events on
which the network agrees upon.
This is the point where Bitcoin's time-stamping scheme comes in: Roughly
speaking, all transactions are grouped into "blocks". The blocks themselves
......@@ -137,8 +137,8 @@ Live Demo
---------
I have used NameStamp itself to create a time-stamping proof for an early
version of NameStamp's code. This can serve as a nice example and demontration.
The data is contained in the Namecoin transaction
version of NameStamp's code. This can serve as a nice example and
demonstration. The data is contained in the Namecoin transaction
f9e91213b5f5c0156ab92eec606affa40959d19e02849fe31a5c47aa78cb1298,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment