Overview
Demo & Code
Documents
Horoscope
Discussion

Please post comments at Prowl-Users Group Discussion



NOTE: There is a code package available for download now at the Kit Download Page. The simulations and sample codes below is considered to be the unpackaged Kit version 0.1. This demonstration page will be retained for reference, but check for the latest downloadable version here.


Observer Demo: Simulated-URL, Blogger


Explanation: An observer service, such as witnessing a transaction, is triggered by the see-query. If the domain of record is registered with a reporter, the reporter would post verified records to the corresponding active reports.
 
Code: Main Routine         Observer Functions         Common Functions
 
To-Be-Developed: Simple Balance Check, Translator
 


Auditor Demo: CC-report, ocaup-report


Explanation: An auditor service is triggered by the audit-query.
 
Code: Main Auditor         Tally Auditor         Common Functions
 
To-Be-Developed: Authenticity Checks, Suspicious Trading Pattern Detection
 


Evaluator Demo: CC-report, ocaup-report


Explanation: An evaluator service is triggered by the eval-query.
 
Code: Evaluator Code         Evaluator Functions
 
To-Be-Developed: Graphs by Minutes or Seconds, Progress-to-Period pro-rated metrics
 


Other Code:


Explanation: The following codes act as the main interface to the observer, auditor and evaluator routines.
Code: Index Code         Reporter Prep         Mail Prep
 


Brief Explanations

Observer: The following features are those that do not fall under auditor and evaluator service types.
  • Witness: A reporter could "notarize" that matching copies of the same transaction record are published. The reporter's independent observer copy of the transaction helps protect the seller against currency inflow repudiation due to mismanaged records that result in broken links.
  • Balance Check: A reporter could parse a published ledger to determine the current balance(s) of an entity.
  • Translation: This feature is to be developed. The intent is to encourage Prowl transactions regardless of the spoken/written language of participants.

Auditor: The following features are listed according to the comprehensiveness of audits provided.
  • Internal Reconciliation: This feature simply calculates that running tallies such as net balances and/or unused budget balances are accurate.
  • Inter-Entity Verification: A more comprehensive audit would verify that a record is indeed published on the link(s) that is referenced by a record in a report. Essentially, whenever an entity publishes a currency inflow, another entity should publish a matching outflow record.
  • Authenticity Check: This feature is still to be developed and will be the most comprehensive and challenging auditor feature to implement. The intent is for a reporter to advise on the authenticity of transactor identity as referenced in a published record; this feature could be tied in to OpenID, public registries, social network systems, reviewer ratings, grievance reports, etc. If you have ideas, feel free to work on implementations.

Evaluator: The following evaluation metrics are grouped according to performance subject areas.
  • Market Demand: Examples include anything that is price-related, or something similar to (credit inflow / total credit issued)
  • Self-Regulation: An example would be the inflow/outflow ratio, or in CC/LETS systems, how closely the net balance stays within zero magnitude.
  • Fairness: An example would be the number of currency units issued per member per week, or anything that might be related to interest, demurrhages, etc.