One difference ik is that constant is never padded to 32 bytes , while immutable does. So what extraordinary thing this immutable is doing , can someone pls explain.
The constant is cheaper as well

Anyone knows this ?

immutable are gas efficient, as they are not stored directly in the storage

What about constant? Aren't they also not stored in storage?

Correct, not stored either

But ain't constant better since they are not padded in run time byte code.

So why was immutable introduced, when constant was doing it's job properly on being a constant

Because you can set immutable in the constructor, you can't do that with a constant

Is it introduced cause we needed to set a constant from outside while deploying contract as constructor parameter?
So why they didn't made this functionality on constant itself

Constant was implemented before immutable, it was added from 0.6.5

Immutable was added

Imagine having a script deploying contract A and contract B, and in contract B, you need the address of contract A which will never change in the future. You don't know the address of contract A until you deploy it, but once its known, its never gonna change for contract B.

Immutable is da way

Thanks 👍

Forgot to say 👍 thanks to you too

I have been lurking in web3 space just observing. I have decided to go down the audit path. I am starting