All language subtitles for 010 Section Wrap Up_en

None of you have your first smart contracts in remix and you have interacted with them.

Let me quickly summarize the section before moving on to something more advanced.

So in this video, I just want to quickly summarize what we did before and we started off with actually

creating files in remix and instead of just creating files, you saw that there is also workspaces where

you can add workspaces and you start with a so called default workspace.

And throughout the course I will probably stay in this default workspace unless we are doing some sort

of specific advanced project where we might want to add in an open Zeppelin workspace.

But for now you can safely stay in the default workspace.

If you don't have a default workspace, just create a default one.

And most likely it will come with a very similar structure like this one.

It will have a contract folder where you can still probably correctly there is the contract inside,

then a script folder, which is I think a fairly new feature of remix that you can execute actual JavaScript

scripts inside a JavaScript environment.

I mean, that's a pretty convenient thing if you have a set of smart contracts that you want to deploy

and pre populate with some data, then that's the way to go I guess.

And then you have tests.

I have not really used the unit test there yet.

I think they are working just fine.

I just I'm just not a huge fan of remix unit test.

I rather do them in Truffle Ha Head or now foundry.

Now to add a new file, you don't click the little.

Plus I can hear you click the little new file I can over here.

And then it will create a new file in the folder that you selected.

So it is a good idea to first select a contract folder and then click the new file again, and that

one will create a new file in this folder and you can name it my contract.

So now with that one, when you click it, you will end up in an editor on the right side.

And there you can write your smart contract code or comments or anything else that you want to write

there.

If you have text files and it's also a text editor, it's not just for solidity.

If you want to make it bigger or smaller because the font is too smaller to big, you can add click

the little plus or minus loop.

I can magnifier, I can see there it is not working with your keyboard where you press control plus

and minus.

This will just make the UI elements bigger, but not the actual editor.

So be aware of that.

Yeah.

With that we have the remix files pane.

Now let's get over to the actual compiler.

In the compiler.

There are a couple of things that you should be aware of.

Number one is the compiler version that should be automatically selected based on the pragmatic line.

So if the primer is zero 814, then it will select the compiler zero at 14.

If you have assembler compiler that specifies any compiler between 080 and 090, then you probably have

to select the compiler version yourself.

So make sure that you're maybe not exactly the latest one, but one of the latest ones and understand

what are those language features.

One thing I can recommend you is to turn on the auto compile functionality.

So every time you change something it will run the compiler over here automatically.

Compiler then already tell you over here with the little check mark or if it's not the check mark,

then there is a problem.

So you should be aware of that too.

Now the next thing I want to talk about is to deploy and run transactions, plug in that you can find

as the third option in remarks.

And over here you have an environment dropdown and for now we are going to stay in the JavaScript virtual

machine environment from remix because it gives us already a couple of accounts over here.

So we don't have to do any account management or wallets that's already integrated.

You don't have to worry about the gas amount at the moment.

It is the amount of gas that is available for each transaction for computational well operations during

execution of a transaction that is the default value from remix mix.

It is not the default value that has anything to do with Etherium or whatever.

Just somebody at the remix testing probably went ahead and said like, Well, 3 million.

That sounds like a good number.

So we're going to do 3 million as a default.

I think the current max amount is around 8 million gas on the Ethereum main chain.

You sell them, actually send the max amount.

You are calculating, estimating how much gas that transaction will need and then it's automatically

sending the right gas amount.

So you'll never well anyway, not overpaying because you get the remainder of gas back to your account,

but it is just a better way to do it.

The value field.

You also have to not worry about it at the moment it is if you want to send actual ether together with

a transaction with the smart contract interaction to a smart contract, we are doing this later with

so called payable functions.

What is important here is the contract dropdown.

Has the contract selected that you want to deploy and then you can hit deploy.

K next is the remix interaction.

So as soon as you have your smart contract deployed with the deployed tab and underneath directly at

no space there underneath directly will be the smart contract instances.

Every time you click deploy, it will deploy a new instance that is important to understand because

you cannot update code on the blockchain.

It's immutable unless you're writing something like proxy contracts, which is something where I have

a specific lecture about it.

On Ethereum, the blockchain, this developer come as an extra material, but it's not content of this

lecture or section.

Maybe we do something else with proxy contracts later in the course, but I have not planned it right

now, so that is very advanced.

If you want to update your already deployed byte code, we are not doing this.

We are normally going by having immutable contracts, running on the address and then you deploy a new

one.

So it gets a new address which you can conveniently copy here if you want to, and you can collapse

your contract with the little collapse I can here, and then you can start to interact with it with

these buttons.

The blue ones are the greenish.

I don't know what is this color?

Navy color is for red operations and red or orange colors is for right operations where you most likely

also have an input field and then you can also collapse.

That and this one over here, the the part on the lower end is for low level interactions.

So if you are doing something maybe in a fallback function, which we are also covering later, then

you can use that one that was named previously differently.

And it's very confusing.

If you look at old YouTube videos, then this one is actually over here at the top of the smart contract.

In this I only called send and not transact so they change the UI around.

It is a low level interaction.

This is what it is about and I think the UI now better reflects it.

But it is confusing.

If you are coming from older YouTube videos, great.

Next we have the logging functionality of remix on the bottom right and you can make it bigger or smaller.

There is a little you have to hover with the mouse over here and then you can drag it up or down.

So if the lock window is not big enough, then you can make it bigger.

There you have a couple of things and I just want to highlight them.

I don't want to go too much into detail of them because we are doing this later on.

Again, there is two things which are outstanding.

The one is a little checkmark icon which is writing transaction.

And then over here there is another one which is called a call which is reading transaction.

You see from which account, from which address you send it to, which address you send.

It is something that you should not only see, but remix is hiding it, so you actually have to open

it and then you can potentially copy the contract address that it is sending it to with the little copy

copy icon.

I think otherwise you have to you have to see what kind of smart contract you are interacting with in

another way.

And I don't I don't know what what other way would there be other than the address?

Because the contract, if you deploy several of them, they all have the same name.

Then you see gas and transaction costs, something you are going to talk about later.

You see there is a transaction hash.

Each and every transaction has its own hash, which is a unique hash like a like an A in code for books,

you have a transaction hash for transaction.

I think about this way, there is a status.

If the transaction is successful and everything is fine, there were no errors, then this returns true.

Otherwise it returns false.

And there is a theta field which in remix is called Input.

I don't know why they call it input, but a native transaction in Ethereum that would actually be the

data field.

And that's the thing that smart contract developers are interested in, because this is when you when

you compare it to the data field over here that's actually called theta, then this is the data field.

This is the, the code that you send to interact deployer smart contract or interact with the smart

contract on the low level.

And this is something that we are going to deep dive into now with that pretty much everything is said.

There is also a debug button for the remix debugger.

We have a separate lecture on that and yeah, that's it.

I think you can go safely to the next lecture if you understood everything of that and we see you in

the next section where we actually do our first small project.