Artur Puzio

I realize now that some reasearch into what exactly epoch does is required. There is probably some significant split between Initiator and Responder. We probably want to implement separate ChannelResponder...

I would sat we should: 1. Check if epoch also has one big tree for contract data without subtrees (this is a potential compatibility issue) 2. Implement a `get_all_with_prefix` function...

I don't trust docs. Especially old ones ;) We should investigate deeper and check if it hasn't changed in current version. If it has, then this issue might not be...

When you use `TYPE.rlp_decode` or `Serialization.rlp_decode_only` so the type is checked.

I think what currently is missing is some more checks if the data decoded from RLP matches what we are expecting. For sure in some places we will accept a...

> We do handle types, I don't think we should care about versions really, just have the latest version for the different messages. I partially agree that we don't really...

I'm confused. Is this issue about adding checks that version is correct when we decode? We already do that for all `Aecore.Utils.Serializable` structures. Where is it missing?

World won't explode (nothing horrible will happen) if we don't, but it's just a simple check that should be done. If the version mismatches then we are trying to talk...

I believe this intersects with #744. Meybe we should consider how to split this better. What is the extends to API changes?

I found a bug in config that prevented creation of logs at all. I made this small change to fix that. Probably we should make some more complex solution as...