...
Learnability: While there are many features here that are commonly found in some well-known applications, it may be unclear what a transaction implies (as in, who is allowed to make a transaction and type of transaction). Since our implementation involves only one-way directional transaction relation, this may be difficult to learn or understand for users.
SafetyFurther handling of disputes: Ease of tracking, settling, and following-up with disputes is currently unknown. This design provides an option to "settle" a dispute, such that the transaction will be effectively canceled. However it is a bit uncertain how to handle the case that a dispute is settled by an agreement on a new transaction amount.
*Complex transactions: *Consider Consider the case where at a dinner, a group of 4 decide to evenly split a $100 dinner bill. However, some people are short on cash while others have extra on hand. So one person pays $50, another $40, and two of them $5 each. If in the end this should be equaled out such that all pay only $25 for the dinner, how would that happen? The solution to this is currently unknown.