日本欧洲视频一区_国模极品一区二区三区_国产熟女一区二区三区五月婷_亚洲AV成人精品日韩一区18p

COMP26020代做、代寫Lab 5 - Solidity

時間:2024-05-03  來源:  作者: 我要糾錯



COMP26020: Programming Languages and Paradigms
Lab 5 - Solidity
Joseph Razavi and Richard Banach
1 Introduction
This lab exercise is about learning a programming language with unusual aspects from its documentation.
We focus on the Solidity programming language, in particular Solidity version 6, which you can read about
here:
https://docs.soliditylang.org/en/v0.6.0/
Solidity is a language designed to write so-called “smart contracts”. These are pieces of code which are
supposed to run on a public “blockchain” – a system which keeps a log of every event which happens, and
where no user can single-handedly affect what happens. That means that once your code is deployed, you
can no longer influence it, unless you have programmed mechanisms to do so. And if you find a bug, the
bug is there forever!
In addition, the blockchain is designed to support payments of various kinds – for instance a smart
contract has a balance of currency (called ‘wei’ for the Etherium blockchain on which Solidity contracts run)
which it must use to pay for its own computing resources. Contracts can charge each other and pay each
other for services.
Whether or not any of this is a sensible technical or social project is perhaps debatable, but it certainly
creates interesting design challenges for a programming language – and where weird programming languages
lead, let us follow!
Read about Solidity’s notion of a contract, and its execution model (the ‘Ethereum Virtual Machine’) here:
https://docs.soliditylang.org/en/v0.6.0/introduction-to-smart-contracts.html
Refer to the Solidity documentation to complete the exercises below. Aside from the above these sections
are particularly useful:
• https://docs.soliditylang.org/en/v0.6.0/solidity-by-example.html
• https://docs.soliditylang.org/en/v0.6.0/solidity-in-depth.html
If you prefer videos, I have made available on Blackboard some videos designed to help you get started.
Note these videos belong to the lab and are not part of the content of any week. Solidity will be used only
for the lab, and is not examinable.
In this lab exercise, rather than deploying our code on the real public blockchain (and having to pay
to run it!) we will use a simulated version of the Etherium Virtual Machine which is used for developing
code and testing it before deploying it for real. You must use the version provided on Blackboard; see next
section.
1
2 Setup
Make sure you have downloaded Remix from Blackboard:
https://online.manchester.ac.uk/bbcswebdav/courses/I3132-COMP-26020-1231-1YR-040494/remix-d624303.zip
(If the link above does not work, check the Lab 5 folder on Blackboard for information.)
and that you can compile and run programs. To do this, you might need to click on the ‘plug’ icon on the
left hand menu, and made sure ‘Solidity compiler’ and ‘deploy and run transactions’ are enabled. This will
let you compile and run Solidity programs in Remix as seen in the videos. Remix is a browser based editor,
and has been tested for this course on Google Chrome on Linux and Windows. With other browsers you
may get strange behaviour. It is better to edit in a separate text editor and paste into Remix for testing, as
it can have problems with saving files and allowing text to be copied out of it in some browsers. Make sure
you always have a copy of your code in another editor so that you don’t lose your work. Clone the gitlab
repository
26020-lab5-S-Solidity_
where is replaced by your username. This contains the files you will need for the exercise.
3 Background
The exercises concern three contracts which should interact with each other, alongside other contracts which
we assume exist (but do not implement or worry about the implementation of). The first contract we consider is a ‘paylock’. The idea is that a supplier does some work, which can then be collected by a customer.
If the customer collects early, they get a discount, and how much discount they get depends on how early:
there are two deadlines. If they miss the second deadline they forfeit their discount altogether.
Done_2 Forfeit
Done_1 Delay
 Working Completed
Start
Signal
Collect_1_Y Collect_1_N
Collect_2_Y Collect_2_N
The blobs indicate possible states of the paylock, and the arrows represent function calls. The ‘Start’
arrow represents the constructor. The idea is that the functions should only succeed if the paylock is in
the state at the beginning of the arrow, and then the resulting state should be the one at the end. Of
course, there are other conditions: collect_1_Y should only succeed if called before the first deadline,
and collect_1_N should only succeed if called once the first deadline has passed; similar considerations
apply to the other two collect functions. Look in the file paylock.sol to see a partially finished implementation of the paylock. The first two exercises (see next section) concern only the logic of the paylock.
They are about adding features to the implementation, though we never complete a realistic implementation.
The subsequent exercises are about implementing a supplier which has to interact with both the paylock
contract and a rental contract which it needs to use to complete its work. As above, we will only model
2
certain aspects of these contracts. On the one hand this makes the exercises manageable, but on the other
hand it can be confusing if not pointed out: you would naturally wonder when we would add the rest of the
necessary features!
4 Exercises
The implementation of the paylock which you are given does not model the passage of time. To do this, we
will add a tick function, representing the passage of one unit of time. We shall assume for the moment that
the tick function is going to be called by a neutral third party, who we trust to call it at a regular interval.
For now we also trust all other contracts in the universe not to call this function. (And assume that the
blockchain updates quickly enough that this is a reasonable model of time! This is not how one would deal
with time in a real smart contract system.)
EXERCISE 1: (2 marks)
Add an int variable clock and a tick function which models the passage of time. Modify the various
collect functions to adhere to the deadlines, where we consider the first deadline to happen if the clock
has reached 4 units of time or more, and the second deadline to be when the clock has increased by
4 units of time or more from when collect_1_N was called.
We now need to make sure this tick function can only be called by the agreed third party.
EXERCISE 2: (2 marks)
Add an address variable timeAdd to the contract. Add an argument to the constructor and set the
value of timeAdd to that argument. Now modify tick so that it can only be called by someone from
the address timeAdd .
Tip: when testing your code, copy one of the addresses from the ‘Account’ dropdown menu and paste
it into the constructor argument. That should make it easier to experiment.
Look in the file supplier.txt and paste its contents at the end of paylock.sol . Note how the Supplier
contract interacts with the paylock, indicating to the paylock when it has finished its task. In the next
exercise, we will make it interact with the Rental contract too. The idea is that in order to finish its job,
the Supplier must rent a resource, then return it, before calling finish will succeed.
EXERCISE 3: (2 marks)
Add functions aquire_resource and return_resource which must be called in that order to the
Supplier contract. To do this you will need to add new local variables. Add a local variable
representing an instance of the Rental contract, and allow the address of an instance of Rental to
be passed as an argument to the constructor. Modify the aquire_resource and return_resource
functions so that they call the appropriate functions of the Rental contract.
Tip: Since the constructor of Supplier requires the addresses of a Paylock and a Rental, make sure
you deploy instances of those first when testing.
We will now make our model of the Rental contract somewhat more realistic, by requiring the payment
of a deposit which is returned once the rented resource is re- turned. For the purposes of the lab we assume
that the deposit is 1 wei.
Since the Rental contract is not supposed to assume that it is being called be a Supplier, it should
assume that the contract it is connected to implements a receive function; you can read about this in the
Solidity language documentation:
https://docs.soliditylang.org/en/v0.6.0/contracts.html#receive-ether-function.
3
Since we are not allowed to assume the calling contract is a Supplier, it is also useful to look at the
functions which can be applied to any address:
https://docs.soliditylang.org/en/v0.6.0/types.html#members-of-addresses .
In fact, our intention is to make as few assumptions about the other contract as possible, so we will use
the low-level .call() function. Find out how to make this work and attach a value to it.
EXERCISE 4: (2 marks)
Modify the Rental contract in the following way. First find the commented line
//CHECK FOR PAYMENT HERE
and replace it with something which prevents the function from succeeding unless proper payment is
made. You will also have to make the functions payable. Then find the commented line
//RETURN DEPOSIT HERE
and replace it with a single use of the .call function which returns the deposit. Modify the Supplier
contract so that it has a receive function, and make sure that Rental does not assume that the
contract which calls its functions is an instance of Supplier. Modify the external function calls made
by Supplier to Rental so that they transfer the deposit as appropriate.
At this point you should copy the file paylock.sol to supplier2.sol and work in supplier2.sol .
The rental contract as implemented has a security flaw (which is described in the ‘Reentrancy’ section of
chapter 9 of Antonopoulos’s book Mastering Etherium (available online from the library, and also at
https://github.com/ethereumbook/ethereumbook/blob/develop/09smart-contracts-security.asciidoc
EXERCISE 5: (1 mark)
Modify the Supplier contract to take advantage of this security flaw to take more Ether belonging
to the Rental contract than it has sent to the contract, if more ehter is available. Make sure this
work is saved in the file supplier2.sol
At this point you should copy the file supplier2.sol to suppler3.sol and work in supplier3.sol .
EXERCISE 6: (1 mark)
Re-order the lines of the retrieve_resource function of the Rental contract so that the vulnerability
above is fixed. Make sure this work is saved in the file supplier2.sol
Note: You need only prevent the attack described here while preserving correct functionality; you do
not need to solve any other security flaws.
5 Submission
Submission is by gitlab, following the same procedure as the other labs for this unit. Ensure that you have
pushed a commit containing your submission (i.e. make sure you have added all files to the repository),
tagged with the tag lab5-submission , by 6pm on 03/05.
Check SPOT to make sure your submission has been received correctly, and contact me (Joe) if you
notice any strange behaviour from SPOT.
請加QQ:99515681  郵箱:99515681@qq.com   WX:codinghelp





 

標簽:

掃一掃在手機打開當前頁
  • 上一篇:代寫program、代做c/c++,Python語言編程
  • 下一篇:EBU4201代做、代寫Java設計編程
  • 無相關信息
    昆明生活資訊

    昆明圖文信息
    蝴蝶泉(4A)-大理旅游
    蝴蝶泉(4A)-大理旅游
    油炸竹蟲
    油炸竹蟲
    酸筍煮魚(雞)
    酸筍煮魚(雞)
    竹筒飯
    竹筒飯
    香茅草烤魚
    香茅草烤魚
    檸檬烤魚
    檸檬烤魚
    昆明西山國家級風景名勝區
    昆明西山國家級風景名勝區
    昆明旅游索道攻略
    昆明旅游索道攻略
  • NBA直播 短信驗證碼平臺 幣安官網下載 歐冠直播 WPS下載

    關于我們 | 打賞支持 | 廣告服務 | 聯系我們 | 網站地圖 | 免責聲明 | 幫助中心 | 友情鏈接 |

    Copyright © 2025 kmw.cc Inc. All Rights Reserved. 昆明網 版權所有
    ICP備06013414號-3 公安備 42010502001045

    日本欧洲视频一区_国模极品一区二区三区_国产熟女一区二区三区五月婷_亚洲AV成人精品日韩一区18p

              亚洲欧洲一区二区三区在线观看 | 国产精品入口尤物| 欧美影院视频| 亚洲国产成人在线| 欧美色图首页| 欧美88av| 久久久久久噜噜噜久久久精品| 在线观看福利一区| 国产精品天美传媒入口| 久久亚洲视频| 欧美一区三区二区在线观看| 一本色道久久加勒比88综合| 国内成+人亚洲| 国产精品午夜电影| 欧美日韩免费高清一区色橹橹| 久久久天天操| 欧美专区在线播放| 亚洲伊人色欲综合网| 亚洲日本激情| 亚洲国产你懂的| 在线不卡亚洲| 国产综合香蕉五月婷在线| 国产精品日韩欧美一区| 欧美日韩伦理在线免费| 欧美aa国产视频| 久久亚洲综合网| 裸体丰满少妇做受久久99精品| 欧美影院在线播放| 性欧美长视频| 久久久久国产精品www| 欧美专区亚洲专区| 久久精品91| 久久亚洲精品一区| 久久婷婷影院| 久久久久久亚洲精品中文字幕| 欧美一区二区成人| 性欧美超级视频| 欧美一区二区三区四区在线观看| 亚洲永久精品国产| 午夜精品网站| 欧美一区二区在线免费播放| 久久电影一区| 久久免费视频网站| 免费欧美在线| 欧美日韩免费高清| 国产精品三区www17con| 国产日韩欧美视频在线| 影音先锋在线一区| 亚洲日韩视频| 亚洲香蕉网站| 久久久久成人精品| 欧美激情视频给我| 国产精品久久久久久久电影| 国产偷自视频区视频一区二区| 韩国欧美一区| 在线视频中文亚洲| 久久九九国产精品| 欧美精品在线播放| 国产日韩精品在线观看| 91久久精品一区二区三区| 亚洲综合色婷婷| 欧美~级网站不卡| 国产区二精品视| 99精品99| 久久久99精品免费观看不卡| 欧美韩日视频| 国产精品视频福利| 亚洲电影天堂av| 午夜国产精品视频| 久久亚洲春色中文字幕久久久| 免费看成人av| 欧美午夜激情视频| 国产日韩精品一区二区| 影音先锋久久精品| 国内精品久久国产| 亚洲先锋成人| 久久久久久国产精品mv| 欧美精品91| 国产精品看片你懂得| 国产一区二区久久精品| 亚洲黄色精品| 亚洲欧美日韩精品久久久久| 久久久国产精品一区二区三区| 久久综合给合| 国产精品久久9| 亚洲国产激情| 欧美有码视频| 欧美另类亚洲| 在线成人h网| 午夜精品免费在线| 欧美激情成人在线视频| 欧美少妇一区| 99riav久久精品riav| 久久久青草青青国产亚洲免观| 欧美日韩国产91| 在线免费观看成人网| 亚洲私人影吧| 欧美精品一区二区三区四区| 国产一区二区精品久久91| 一色屋精品亚洲香蕉网站| 国产在线欧美日韩| 久久精品国产精品| 国产精品免费在线| 亚洲美女av在线播放| 久久精品免视看| 国产精品人人爽人人做我的可爱 | 国产精品一区免费观看| **性色生活片久久毛片| 亚洲欧美电影院| 欧美三级不卡| 亚洲精品一区二区三区在线观看 | 一区二区在线观看视频在线观看| 一区在线免费| 久久人人精品| 国产午夜一区二区三区| 亚洲综合色激情五月| 欧美日韩亚洲一区在线观看| 亚洲人成网站精品片在线观看| 欧美亚洲系列| 亚洲国内在线| 欧美另类在线播放| 日韩午夜av电影| 欧美日韩亚洲免费| 亚洲图片在区色| 欧美人与禽性xxxxx杂性| 在线观看亚洲| 欧美日韩视频专区在线播放| 亚洲精品女av网站| 欧美日韩亚洲另类| 欧美一区二区免费视频| 国产亚洲午夜| 欧美1区2区3区| 亚洲精品一区二区网址| 国产精品视频午夜| 欧美在线亚洲| 在线免费精品视频| 欧美激情亚洲一区| 亚洲一区二区三区四区视频| 国产午夜精品久久久久久久| 性欧美长视频| 国产网站欧美日韩免费精品在线观看| 裸体歌舞表演一区二区| 99国产精品国产精品久久| 国产精品av一区二区| 久久免费高清| 一区二区av在线| 国内久久婷婷综合| 欧美精品亚洲| 久久综合婷婷| 亚洲夜间福利| 精品1区2区| 欧美午夜寂寞影院| 免费成人黄色片| 亚洲免费在线观看视频| 国产自产精品| 国产精品一区二区三区久久| 免费亚洲一区二区| 先锋影院在线亚洲| 亚洲久久一区二区| 国产一区二区三区无遮挡| 欧美/亚洲一区| 中文网丁香综合网| 99精品久久久| 亚洲国产成人av好男人在线观看| 欧美色图首页| 欧美成人69av| 久久精品国产999大香线蕉| 亚洲国产日韩欧美一区二区三区| 欧美精品播放| 久久一区二区三区国产精品| 亚洲欧美影院| 亚洲调教视频在线观看| 国产一区二区三区免费在线观看 | 亚洲国产清纯| 韩国精品在线观看| 国产精品自拍网站| 国产精品国产三级国产aⅴ无密码| 欧美成人69| 亚洲欧美激情在线视频| 亚洲欧美成人在线| 亚洲视频在线二区| 一区二区三区日韩欧美精品| 亚洲黄色免费电影| 韩国三级电影久久久久久| 久久蜜桃资源一区二区老牛 | 中文一区二区| 亚洲剧情一区二区| 日韩午夜av电影| 最新国产成人av网站网址麻豆| 在线播放中文字幕一区| 黄色成人91| 亚洲成人在线观看视频| 影音先锋成人资源站| 国内成人精品视频| 国内精品久久久久久久影视麻豆| 国产精品综合| 亚洲国产天堂网精品网站| 国内精品视频在线观看| 国内精品久久久久影院优| 国产视频在线观看一区|