Roman Khimov

Another possible use case could be creating transaction with multiple signers, at the moment you also have to collect their signatures via some additional mechanism, the network doesn't help in...

> One can create a Smart Contract with such feature, deploying its address with storage for caching signatures and deleting at the end of the process. And BTW, this contract-based...

I guess it'll have the same problem with multiple invocations in a single block, setting proper system fee for it would be a problem.

## Definition of the problem Several parties want to sign one transaction, it can either be a set of signatures for multisignature signer or multiple signers in one transaction. It's...

Update based on one problem noticed an hour after the post. Waiting for feedback otherwise. **Amendment №1** As "1 out of N" verification contract may be dangerous in presence of...

> We can create a new message type, incomplete message, type, content and current signatures. Then it's possible to create a plugin in order to collect the specific messages an...

I'm not sure I get the idea behind that. Say we want to make a transaction T with "3 out of 4" multisignature contract (MC) for A, B, C and...

I see several problems with `PendingWitness` approach: * the need to synchronize parties over the transaction signed All participating parties have to wait for transaction to appear on P2P network...

>> the need to synchronize parties over the transaction signed > > I didn't understand this point, can you ellaborate? `PendingWitness` scheme requires sender to be non-pending which practically means...

It's certainly not for preview4, for preview4 we should just use the simplest possible (temporary) solution. But we're working on it and the only things left at the moment are...