Tal Kol

We have 3 new issues for the main stuff we're working on regarding this solution. Thanks for the feedback!

If ownership is indeed renounced and a user is going to an explorer to verify that, it will be nicer if the explorer prints out something standard instead of showing...

I don't think adding `renounceOwnership` as a new message adds potential mistakes, It's not much different from sending by mistake your tokens to the wrong place or by accident transfer...

Let's think together before you shut it down :) Handling bounced messages is not an advanced use-case, we should attempt to make it straightforward. Developers that aren't used to async...

I know, if the message is potentially larger than 256 bit and the user wants to handle its bounce, they will have to parse it manually from a slice. Like...

ok fair. new idea :) what if we always support bounced routing, even if the message is potentially larger than 256 bit. and the compiler will throw a compilation error...

External imports is a tradeoff - you make it easier to bring dependencies, but you're more prone for dependency hell and hiding from users what's actually being imported. In some...

> Can it be merged with [Issue#9](https://github.com/ton-society/ton-footsteps/issues/9)? I saw it, it seemed like a different target audience: "Make sure person with little or no blockchain literacy understands how fees work...

No problem, clarified the target audience in multiple places in the issue

Why do we need this post? I reviewed my team's contracts and I see that they leave 0.01 TON for storage fees. I then ask why 0.01 TON? Why not...