remember there is core itself on top of this and messages in tx and tx in blocks are valid but messsage body can store any amount of any keys you like

this is application logic. you can implement everything you want except of breaking consensus rules. so, inside valid message from A signed by A you can receive any key perform any logic etc

... so you need to accept messages from any address no checks at this point

inside message there are some data .... your code doing logic..

Thanks I get what you are trying to explain. In addition I'm wondering if there's a way I could prove that "a public key is belong to a address" to a contract?

If you know the wallet version of the contract deployed on "address"

By version do you mean the wallet contract code? or something like v4r2

Yes, the code

The address of any contract in ton depends on both code and data.

the great truth is you dont want to do this

Do I need anything else? or with only contract code and publickey I can calculate the address and see if the result matches what I was looking for (on-chain)

May I know why? security concerns?

there is no such particular problem, why do u need this?

don't try to solve every task you think you will have. try to start from smth less

thanks for the advices, I will reconsider if this logic is really essential for my Dapp.

in common sense address is just hash from public key but in TON things much complicated. adderss you meant may not be wallet address etc etc. to check signature u dont ned it.

to decide is signature correct at app level you should pack this info into data you sign

cause you missed smth isnt this obvious?

I just spent minutes to check there is no storeAddress nor ton or ton-crypto, maybe using old version dunno

and second: provide full address no other way

okay, I have a clear direction now

maybe add few words about who are these ppl....
please tell mark to update SSL at his website lol

storing number "6" using 5 bits

ok, but, why? It is not related to both code and data

part of header format maybe or opcode or mode flag. continue yur reseach.

this is message header

message can be completely raw data or maybe packed using basic formats, this is header for state_init I guess smth like this

It's flags for StateInit, showing that code and data are in references and there are no libraries attached to contract.

Oh, thanks!