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.
4496 comment >

The "wallet" demo is broken as in "getting the most basic thing wrong": it allows double spend of funds.

This looks like a good argument to favor anti-double spend features in the core protocol. By design the core only ensures consensus on the update of the state of an agent (a.k.a. "place"). It has no idea what a double spend situation would actually be.

First versions of the demo where checked to prevent double spend. Then feature creep began. At a point this comment crept into the source:

-- This index can not be unique if we want to handle retour orders.

and the SQL statement create index... lost the unique keyword. (Later it became even worse.)

Now the "wallet" is just a demo. Nothing is bad enough to not be useful as a bad example.

Actions to be taken: As this is a demo applications there is no urgency to fix it soon. It will be replaced with a new version using since-developed features to no longer need to update entries of the SQL table at all. At least two independent measures shall be taken in the source code to protect against the illegal update and the whole, than simpler logic, shall be documented.

4506 comment >
4489 is a > issue
4492 title > The "wallet" demo breaks accounting rules, enables double spend.
4494 state > solved comment
issue container member