Eitu33

https://github.com/massalabs/massa/issues/3058#issuecomment-1257182893 is fixed in https://github.com/massalabs/massa/pull/3079, couldn't reproduce https://github.com/massalabs/massa/issues/3058#issuecomment-1256015386 but added logs on what I think the problem might be.

There is a chance that they were both related but I will keep the issue opened until we're sure this is fixed.

> The bits are for me hard to understand and calculate for end user because they create datastore keys as string. IMO, I think having a convention on where we...

> The developers need to know on which entry they can store their bytecode no ? Maybe I miss something This can be handled in massa-std for users that want...

> What are the management rules ? Can immutable smart contracts be deleted ? Not as a datastore entry, but it would make sense that they can be deleted when...

After speaking with @gregLibert, I believe that what he describes in https://github.com/massalabs/massa/discussions/2668 must be taken into consideration before we decide how we want to handle bytecode. It seems like there...

@setar Public keys format has changed, if you are using a PubKey, PrivKey, or Address from the previous episode your node won't work. You need to generate a new one.

It does

But is it really necessary for functions that only use a few arguments? I'm thinking about `BlockDeserializerArgs`, this would be nice but only for anything above the clippy limit imho.

I think what we should do is simply adopt the clippy rule, since the vast majority of functions have few arguments it would add a lot of code, take time,...