Separating TIMELOCK & ConditionedTransactionHandler about orisi

[Gricha]

Sure, I think it makes sense.

While I'd like to tackle this task, I can't make any time promises before
14 July. It's probably smarter to give me tasks of lesser importance and
priority to that date. After that I'll finish tasks way faster ;)

On Saturday, July 5, 2014, Tomasz Kolinko [email protected] wrote:

If I understand correctly, right now the transactions are being signed by
ConditionedTransactionHandler. And all the other contracts, once the time
of signing comes, create a ConditionedTransaction.

The problem with this approach is that ConditionedTransaction also
contains a TIMELOCK contract built in. It makes the code quite convoluted.

What I want to do is create a separate TIMELOCK contract, which uses
ConditionedTransaction as a signing mechanism. And rename
ConditionedTransaction into TransactionSigner.

What do you think, @Gricha https://github.com/Gricha ? Would you like
to tackle that this weekend?

—
Reply to this email directly or view it on GitHub
#49.

[kolinko]

While I'd like to tackle this task, I can't make any time promises before
14 July. It's probably smarter to give me tasks of lesser importance and
priority to that date. After that I'll finish tasks way faster ;)

Of course, no pressure. Holidays are important :)

[kolinko]

Finished! :D 👯