Dappsuite

What do you like best?

Dappsuite's ability to link a public or private Ethereum account to a Salesforce organization and use it for the creation of smart contracts and to facilitate transactions, is quite powerful. This hyper-ledger style system can be used for B2B transactions, where a Block equals a group of transactions, which each has a unique hash number. Each block is then linked to the previous block with that unique hash number. This is very similar to primary and secondary key relationship in related tables. Dappsuite also allows a user to send and receive a token or additional digital assets by using their product for a reasonable cost (Per User).

What do you dislike?

Dappsuite can sometimes be difficult for the users involved in the transaction when setting guidelines that trigger blocks to release its containment. That data source (3rd party) for a smart contract must be an agreed upon and trust worthy source for accurate data by the parties involved. Otherwise the smart contract is not a reliable option. An example of this is a contract that is activated when a rain fall data source is the agreed upon and trusted source for rain perception data for a farmer and insurance provider (Possibly use the National Weather Service database in this instance as the relied upon data source).

Recommendations to others considering the product:

Determining the security level that your organization or institution needs when handling transactions between multiple parties is a must.

What problems are you solving with the product? What benefits have you realized?

A problem that we are trying to solve for farmers with Salesforce who use Dappsuite, is having insurance for low rainfall amounts during their harvest season from a insurance company. An agreement is made between the farmer and the insurance company that says if not enough rain falls, a certain amount of money will be sent to the farmer from an escrow account using the Dappsuite product.