Alexander Chepurnoy

It depends on usage, I haven't seen any use-case still. Especially considering that in practice you can go the other way, so instead of constructing e.g. a box with certain...

But where do you need for constructing e.g. box from multiple sources instead of checking a box of interest ? Even smaller chance to find an use case for a...

As no use-cases provided, I can move it to 7.0 or leave for 6.x. Frontend only implementation looks promising, as it is better not to touch consensus-critical level when possible

For AvlTree byte machinery is not hard: ``` val digest = SELF.R4[Coll[Byte]].get val flag = Coll(0.toByte) // read-only val keyLength = Coll(32.toByte) val valueLength = Coll(0.toByte) // arb length val...

But there is simpler solution: ``` @contract MyContract(flags: Byte) = { val tree = SELF.R4[AvlTree].get tree.updateOperations(flags).digest == digest } ```

> Yes, that is because AvlTree have only fields. In case you compare not `digest` but some computable property or the result of a method call, then you have to...

> This is limitation of MethodCall, because we cannot use it to represent for example > * def Box.getReg[T](id: Int): Option[T], which require serialization of expected type `T` > *...

Deserialization of everything mentioned is done in #979 . Header.toBytes done in #975

Serialization of everything mentioned and more done in #979 and #989.

@aslesarenko https://bitcoin.stackexchange.com/questions/57184/what-does-the-nbits-value-represent