10:00 <stellar-slack> <sacarlson> I'm getting this error: stellar-base-0.6.1/lib/stellar/transaction.rb:97:in `for_account': Bad :account (ArgumentError) this is coming from this line: raise ArgumentError, "Bad :account" unless account.is_a?(KeyPair) && account.sign? I'm not totaly sure I'm right about this but why do I need to have an account with a signature at this stage? shouldn't this line be just: raise ArgumentError, "Bad :accou

10:00 <stellar-slack> is no need for any signatures in the structure of a tx as far as I know. the signature seed should only be needed later to be present at the envelope creation event time. I am presently creating transactions that are not yet going to be signed by the final sender of the transaction but I am adding a signature of one of the signers. the transaction will be later sent with the added signature of the target_account a

10:04 <stellar-slack> <sacarlson> this check makes this not posible

10:39 <stellar-slack> <sacarlson> with this change implemented in test, my transactions can now be created. I still see I will get errors at the stage of to_envelope stage so it looks like this works ok so far. I'll try it for a bit to make sure what other problems it might bring.

10:45 <stellar-slack> <sacarlson> I created an issue for it https://github.com/stellar/ruby-stellar-base/issues/17

11:06 <stellar-slack> <sacarlson> I've added a new feature to the multi-sign-socket server. the new action is called "make_unlock_transaction" that makes it possible to lock and then unlock an account over some desired time window. This together with the "make_witness" action provides new infrastructure for offline stellar transactions. the new changes are published at https://github.com/sacarlson/stellar_utility/tree/master/multi-s