Ethereum Foundation Devcon2, 23 Oct 2016

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Ethereum On Ruby

Description

Visit the https://archive.devcon.org/ to gain access to the entire library of Devcon talks with the ease of filtering, playlists, personalized suggestions, decentralized access on IPFS and more.
https://archive.devcon.org/archive/watch/2/ethereum-on-ruby

A presentation exploring the Ethereum Ruby Client/Cryptape and the Ethfans community in China.

Speaker(s): Jan Xie
Skill level: Advanced
Track: Developer Infrastructure
Keywords: china, ethfans, community, dapps, language, testing, deployment, contracts, tests, solidity, contracts, deploy, debugging, rust, devp2p

Follow us: https://twitter.com/efdevcon, https://twitter.com/ethereum
Learn more about devcon: https://www.devcon.org/
Learn more about ethereum: https://ethereum.org/

Devcon is the Ethereum conference for developers, researchers, thinkers, and makers.
Devcon 2 was held in Shanghai, China on Sep 19 - 21, 2016.
Devcon is organized and presented by the Ethereum Foundation, with the support of our sponsors. To find out more, please visit https://ethereum.foundation/

A

Next person up is John. He is going to speak on a cerium on Ruby welcome Jan thank.

B

B

So thank you for coming to this talk and it's time for some simple stuff, I think I believe the organizer arranged me after blood for some reason so yeah, okay in in the next in the next 15 minutes I, will introduce you to his sermon Ruby, which is the intersection of his serum community and Ruby community.

B

Before that, a little bit about myself, my name is Shahenshah and I'm. A serum developer I in last year, I created the Ruby certain project, which is a full implementation of cerium in Ruby and I'm, also working on pi, serum and I'm running a blockchain technology, startup named tape, and we we are building underlying permission ledger and we also providing some consultancies to our customers and during our daily job we build some tools to help me develop taps okay.

B

So a little bit about Ruby Ruby is a language created by a japanese named Yukihiro Matsumoto, whose nickname is Matz and the core principle of Ruby language. I. Think you can get from this guy's face right, that's happiness!

B

So Ruby is a language designed for human it. It's very focused on readability. So, in one of his talk in one of math talk, the presentation title is optimized for programmer happiness. So if you make a spectrum of languages in the one side- maybe maybe west right, the ASM and in in the other side, is Ruby I believe so it's all optimized for human and the source code, written in rubies, will read very naturally, and we will see that later and the other good point of Ruby's flexibility.

B

So a lot of people is using Ruby to define her no DSL, the main specific language so that the most famous one is rels right. So real see is DSL for web development and I believe we can also use Ruby to define some DSL for smart culture.

B

So we created thethe testing and deployment framework for smart contract after you install tests, you can open your console and type some command line like this like test new big thing, big things, the name of your next big project, okay and this command- will generate you a lot of files and directories.

B

An amount of directories, the most important one are contracts and tests contracts will include the generated country, template and test will include, will have to generate a test template and then you can do tests generate token tokens the name of your smart contract, so you can name it whatever, but we use token, for example, and here's the here's the generated file in the on your left side, you can see, there's a solidity contract is empty and, on your right hand, is the generated test for the left side.

B

Smart contract and the generated test is very simple. It includes an example test, so it just says assert a third equation of assert that the counter at address is not kneeled assert that the contract has been deployed.

B

Okay, so this is just generated out from the tool.

B

Okay, before we jump into a real smart contract test, you need to know some tools at your hand. You can use these keywords in your test, so we have some. We have some tools relate you to count. X you can you have access to state state is a collection of accounts and you have access to head head. Is the the the most recent block of the chain? The the current block and you have access to contract contract? Is the Ruby object, the test framework built for you, it's compiled from the solidity contract it?

B

It extract the ABI interface from the contract and the test framework. We have you the cowshed object for you, so you can use the object to do everything to do all kinds of scenes on the contract and you can take some actions, so you can transfer Balan, you can transfer user between accounts, you can deploy.

B

Contracts to the state. Deploy is not implemented yet so is in grey, and you can call all kinds of functions on the counter object and they I. They are some pre generated randomly generated accounts.

B

You can reference to them by using private keys pop keys addresses and as a tester yourself, you can reference to your own private key using private key pop key energy, and we also define aliases to these randomly generated accounts. So you can use well-known names like Alice Bob Carol to reference to those generated accounts, so here's a real test in the left, its standard, token contracts.

B

The token council has issue function, chance for function and get balance and, on your right hand, is the test for the corresponding contract, and you can say at the first line. We we use contract issue Bob 100, and that means we invoke the issue function to issue Bob 100 tokens, and then we transfer Carol 90 tokens from Bob, and then we make sure that the the Carrows account has 19 token tokens in it, and then we we do the chance for again we we we want to make sure that it can be done.

B

It will raise some exceptions, so in in the contract has you can you can find? One thing is that it's really the test is really compact right. You you don't just know asynchronous in this test. There's no callbacks, there's no money! You don't need to do that. You just write the test and you run the test just just like you do in Java or C++. If we are wrong, is instantly and give you feedback.

B

So we find this will speed up your development cycle, largely because now you can trick with the contract on the left side. And then you just run your test and you boom get get the result from your from your code. You you just written in instantly and when there's something wrong, you can go back to your code and do something this feedback circle is much shorter than if you deploy a contract to test net or if you use other things.

B

And there's better stuff what? If? What? If you forget to write the first line, you forget to issue Bob 100 tokens at first, but you just chance for Carol. Now you will, you will get a failure in test. Then then, what you do? How do you do bugger? How do you bug this problem in in traditional programming contacts we may find? We may open semantic bugger right, but someone said logger is the ultimate debugger I. Don't remember whom, and we found that in in solidity we have log.

B

Although the law is some, it is some kind different than the loggers log in traditional programming world, but there's logger right. So we can add a lot. We can write a log in contracts and the test framework when, when you run in the the test, the test framework will print the log in your council. So you can know what's happening in your contract. You can know you can know immediately. If the address to is correct, passed in right, you can do it to all kinds of things to inspect your contract, and this is very important.

B

Important for for debugging I believe.

B

An interest by default locks will be print to cancel, but events won't. Although events are also some kinds of locks, but you can trick those options to enable events printing.

B

So if you set print events to chew, then if you, if there is an event in your contract, you will see the below lines like this in your council, and here you can see the issue from account and amount.

B

And better test is a language agnostic framework, so it also supports serpent and I. Don't know how many server and developers here whoa italic.

B

Okay, but sir burn is also very good: smart country, language yeah.

B

So the test is possible because we created a ruby serum which is a full implementation of Assyrian protocol it. It includes a lot of sins. So what behind has is test will compile the contracts and run the bytecode on Ruby's virtual machine, and it doesn't involve any mining and block creation. It just run the code on VM, that's very simple right, so so you can get instantaneous feedback and.

B

At this time, ruby sermon has evolved into many, has inspired many projects so inside inside Ruby sermon. We have. We have modules in charge of data like block transaction, etc and EVM. It's a full implementation of EVM.

B

So there's people using the code inside Ruby seven to extract ABI from contract, and there are also utilities like address public key private key. They are very convenient tools to help you convert data between address public, key and private key and Ruby. Sarah also has many dependencies like our LPS, serpent and SEC P and based on Ruby serum. We are now building wrath, ressies, a full ruby client, so it's some kind like Joey cerium. So besides Ruby sermon, we also need Ruby Tempe to P the network layer combined a network layer with Ruby sermon.

B

We we can build rest and then we have test the testing framework and we have Ruby eath Ruby's is a small tool extracted from not extracted but built based on ruby serum to help you create and sign transactions, and we have is JSON RPC, which is a JSON. Rpc kind talked to a serum server, a serum note, and there are some projects extracted from Ruby's area.

B