Skip to content

Illustrate the concept that the user know what token they can get before purchase, 𝑛𝑜𝑡 𝑎𝑓𝑡𝑒𝑟 #26

@SmartLayer

Description

@SmartLayer

Is there a way for the user to know what token they will get before the transaction and not after? If you read through the paper (a lot of work to read, I know), you will notice that the cards (generated by the dapp browser) enjoy a different level of trust than the dapp below it. The user wants to know what tokens they can get because if a warranty is just promised, not given in the form of a token, the buyer might choose not to check out at all. In other words, a buyer must know both the input and output to make a decision. Imagine if you want to resell the product later, it will not fetch a good market value because it can only be resold with ebay which has a higher cost of the transaction due to the extra need to prove the availability of warranty.

Regarding "a buyer must know both the input and output to make a decision" you can see it the other way as "a buyer will only know the deliverable before he proceeds with payment since once payment is done, it is done. Atomicity is the key of the blockchain transactions, either the transaction is successful, and you get ALL THE TOKENS that represents your purchase, or your payment will be returned. This is DIFFERENT from traditional business, where Payment is made first, then, you may or may not get your deliverable, and if you don't get it, you can do a chargeback. You can't do a chargeback in blockchain without introducing huge infrastructure, so you need to see what tokens you can get. That's just how blockchain works.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions