In this tutorial, the use case supposes that there are 3 people in a team and they hold common funds for corporate purposes. It is convenient for the team to make a decision about the allocation of common funds according to the majority decision, and they use a multi-signature account to do this (smart account). They create an account and do
SetScriptTransaction with the multisig account. The idea here of a smart account is the following: before the transaction is submitted for inclusion in the next block, the account checks if the transaction meets certain requirements, defined in a script. The script is attached to the account so the account can validate every transaction before confirming it.
In this tutorial, we consider the problem of buying physical goods with cryptocurrencies. Should the buyer trust the seller and pay before receiving the goods or should the seller trust the buyer and ship the goods before receiving payment? This issue can be solved by using a third party escrow service. A well-known improvement uses Waves multisig feature. In this scheme, the money is not sent directly to the escrow service’s address, but instead, it is sent to a 2-of-3 multisig address with one key controlled by each of the transacting parties and one controlled by the mediator. When there is no dispute, the two transacting parties can together create the transfer transaction. Only when there is a dispute will the mediator get involved, collaborating with either the buyer or seller (as appropriate) to redeem the funds.
In this tutorial, we went through Waves Client advanced features which are:
- Get the transaction as JSON.
- Attach a script to your account.
As a first step in our example, we created a script for 2 of 2 MultiSig account, Attach the script to our account via Waves client and then made a transfer transaction with two signatures.
In this tutorial, we went through Waves IDE Tools which are:
- Multisignature account wizard.
- Transfer Tx generator.
As a first step in our example, we created and deployed a script for 2 of 2 MultiSig account by using the Multisignature account wizard and then made a transfer transaction with two signatures(proofs) by using Transfer Tx generator.
In this tutorial, We went through an Introduction in Waves Blockchain from the technical side with detailed description how Waves Smart Contracts work. Waves has a lot of interesting features, but smart contracts are the most interesting right now because Waves approach to Smart Contracts is absolutely different comparing with Ethereum, EOS and many other blockchains.
Please, read our Hitchhiker’s Guide to Waves Smart Contracts which we divided into the following:
In this article, We focused on the idea of Waves Smart Accounts and what makes it different than other existing solutions.
We began with a brief introduction about some definitions of smart contracts then we explained about the difference between Bitcoin script, Ethereum Smart Contract and Waves Smart Accounts.
In this part, We focused more on the smart contracts language and tools for developers. We provided some use-cases implementation using our solution and explain more about our RIDE language.
In this article, We explore the combination of DataTransactions and Smart Accounts.
In this article, We prototyped two formats: ERC-20 and ERC-721, also known as “Collectibles” or “Non-fungible tokens”.
In this article, We introduced Waves smart accounts and smart assets to developers on Azure Marketplace in a special extension for Visual Studio Code, which simplifies the process of creating and operating smart contracts.
Two new virtual machine templates in Azure can be used for setting up new options on a public or private blockchain.