This page has three main sections. (Note that the listings could be empty.) moreā€¦ Tip: Remember the back-button! And don't click the number on the left.

  1. The first item displays a term, URL, text or picture.
  2. Followed by a (still unordered) listing of statements about this subject. (for details follow ">"-link)
  3. Separated by a horizontal rule a "reverse" listing of statements referring to this item in object position.

Point raised during the review of the Stone Age Accounting demo.

  1. a token of agreement. AKA a signature. There needs to be some convention that indicates the offerer's intent to offer and the acceptor's intent to accept. These don't have to be 'strong' just memorable and customary.

This would be "send payment" and "accept payment" buttons to push? Those create yet another document, signed by the sender/receiver.

This is where it gets messy. Signing is the act of adding a token of agreement. What is that token? With a pen it is a recognisable squirl. With crypto it is the digsig appended to a document.

So, in a payment, we should see a sig at the end of the record, and display software could (or should) say "signed by Bob". With the Ricardian Contract, the signature is appended in (approximately) OpenPGP cleartext form.

See booked signature and multivalent signature. We opted to not break the integrity of the original contract by modifying it in any way. Instead we demonstrate linking the original contract (identified by it's hash) into a fresh document, the refined signature.

Those account representing our agents however are do just the opposite: those update their current state with information taken from the transaction.

do we need this link?
1765 created > 2014-07-20 09:12:23 +0200
1766 creator (registered) > jfw

19 comment