Transactions - a chained type to replace CRDT Registers

[loziniak]

@riddim

Input 1+ (n * 32byte)

Good point. Shouldn’t there be more inputs, than one? Otherwise the amounts become always more divided, do I understand well?

Edit: My question is based on Bitcoin transactions, where there can be multiple inputs, so if we have 2 addresses with 0,3 BTC and 0,7 BTC, we can send someone 1,0 BTC by consolidating these 2 smaller entites.

Edit 2: Ok, this is answered in the Transaction code

pub struct Transaction {
[...]
    pub parents: Vec<PublicKey>,
[...]
}