Time Elements (Part 1)

Loading...

来自 University at Buffalo 的课程

Smart Contracts

56 个评分

University at Buffalo

Smart Contracts

56 个评分

课程 2（共 4 门，Specialization Blockchain）

This second course of the Blockchain specialization will help you design, code, deploy and execute a smart contract – the computational element of the blockchain technology. Smart contracts allow for implementing user-defined operations of arbitrary complexity that are not possible through plain cryptocurrency protocols. They allow users to implement conditions, rules and policies of the domain applications. Smart contracts are a powerful feature that, when properly designed and coded, can result in autonomous, efficient and transparent systems. You will design and program smart contracts in Solidity language, test and deploy them in the Remix development environment, and invoke them from a simple web interface that Remix provides. This course features best practices for designing solutions with smart contracts using Solidity and Remix IDE. Main concepts are delivered through videos, demos and hands-on exercises.

从本节课中

Putting it all Together

This module focuses on the development of the Ballot smart contract incrementally to illustrate various features including time dependencies, validation outside the function code using access modifiers, asserts and require declarations, and event logging.

Time Elements (Part 1)4:01

Time Elements (Part 2) (BallotV2 Demo)6:32

Time Elements (Part 3)2:24

与讲师见面

Bina Ramamurthy
Teaching Professor
Computer Science and Engineering Department

Module three, lesson two: Adding Time Elements to Smart Contract.

Let us re-examine the ballot contract developed in the last lesson.

In a typical voting process,

voters are registered first.

There is usually a deadline for registration,

and also for the voting period.

For example, for most states in the USA,

you have to be registered 30 days before the voting day,

and the voting takes place on a single day for in-person voters.

If that is the case,

registration has to be completed before voting.

The current ballot smart contract does not have these limitations.

For example, the function register and the function vote can be called in any order.

There are no rules such as the voters have to be registered before they can vote,

voting is open only for a specified period,

and the winning proposal can be decided only after all the voting is completed.

Currently, if you call the winning proposal,

it gives the zeroth proposal as the winner before anyone is registered or voted.

Now, let us add the stages and the time duration of the stages to the ballot version one.

Create a ballot version two,

ballotversion2.sol on Remix, by copying ballot.sol we created earlier.

We add the enum for the stages,

and logic for modifying the stages within the functions.

We will compile and run it,

and make sure it works as expected.

Let's define the stage as enum data type.

Four distinct stages: init,

reg, vote, and done.

The stage is initialized to init at the time of deployment of the smart contract.

Then in the constructor,

the init is changed to reg stage.

After the registration period is over,

the stage changes to vote.

After that voting duration elapses,

the stage is set to done.

Enum, stage, init, reg, vote, and done.

Let's add this logic to the ballot2.sol smart contract,

and use this to set the stages of the smart contract.

We'll also add the time elements.

Solidity defines a time variable now that is the current block timestamp.

We'll add the state variable,

start time, uint start time.

Start time is initialized to now within the constructor.

Then, change the stage of the ballot process based

on the time allocated for registration and voting stage as shown.

We've added the start time variable.

And the period for registration in this case is 10 days.

We also added the duration for voting period.

In this case, it is one day.

The now Solidity variable is the timestamp of the block,

block.timestamp function, in which the transaction is confirmed.

Thus, now may not accurately reflect the elapsed time.

For approximate intervals and for testing simple concept,

now is a convenient time attribute.

In a realistic application with specific deadlines,

a better solution will be to pass the deadlines in

the input time to the constructor of the smart contract at the time of creation,

and compare it with the current block timestamp where needed.

Recall that block timestamp is represented by the variable now.

探索我们的目录

免费加入并获得个性化推荐、更新和优惠。

Coursera 致力于普及全世界最好的教育，它与全球一流大学和机构合作提供在线课程。

© 2018 Coursera Inc. 保留所有权利。

通过 App Store 下载

通过 Google Play 获取