<stellar-slack>
<sacarlson> so this is what I have so far to test b64_s.value = StellarSdk.Transaction.constructor(message_obj.signables[0].tx_envelope_b64).addSigner(key)
<stellar-slack>
<sacarlson> when translated to browser
pixelb has joined #stellar-dev
<stellar-slack>
<sacarlson> I guess we don't have it quite right yet: TypeError: StellarSdk.Transaction.constructor(...).addSigner is not a function
<stellar-slack>
<sacarlson> TypeError: (intermediate value).addSigner is not a function with: var b64 = new StellarSdk.Transaction.constructor(b64_s.value).addSigner(key).build();
<stellar-slack>
<sacarlson> and a few other trial and errors. so I'm now stuck
<stellar-slack>
<sacarlson> as far as I get without errors is : var b64 = new StellarSdk.Transaction.constructor(b64_s.value)
<stellar-slack>
<powderfan> Any news on the testnet? I got stuck, because I cannot fetch my account info. Fetching effects works though, both batch and stream...
<stellar-slack>
<sacarlson> last I tried it, it was still down for me for testnet
<stellar-slack>
<sacarlson> I guess they are trying to save electricity?
pixelb has quit [Ping timeout: 240 seconds]
<stellar-slack>
<powderfan> line 16758
<stellar-slack>
<powderfan> What I'm trying to achieve is, for any effect get additional info, which is stored on operation level (and later the same for transaction-level)
<stellar-slack>
<sacarlson> for me 16758: // copy of this software and associated documentation files (the
<stellar-slack>
<sacarlson> I have to guess here that you might be playing with var EffectCallBuilder = (function (_CallBuilder) {
<stellar-slack>
<powderfan> I would like to tag transactions done from my app as 'Centaurus' transaction. My idea was to use the memo for this purpose. Now I realized that I have to use memo for what used to be destination tag. Is it possible to have multiple memos per transaction? If not, I guess, there is a general problem. Consider the case you have two payments in one transaction. Both receivers require a (different) destination
<stellar-slack>
memo look like?
<stellar-slack>
<sacarlson> if there is two transactions then there will be two memo as there is a memo in each tx
<stellar-slack>
<sacarlson> an envelope may have more than one tx in it
<stellar-slack>
<powderfan> no, I'm talking of one transaction with two payments, which should be quite possible with the current design. E.g. if I don't want one payment to be done without the other.
<stellar-slack>
<sacarlson> if there are two payments then there must be two tx in one envelope
<stellar-slack>
<powderfan> ok. but a payment is an operation, not a trx. And in theory one trx can contain multiple operations, thus multiple payments.
<stellar-slack>
<sacarlson> I can point you to the structure of the tx and the envelope to give you a better idea. but yes you can have two transactions in an envelope going to two destinations in fact from a - b and b - a in the same envelope that may require both a and b sigs
<stellar-slack>
<sacarlson> the way you consider a single transaction as that you send to horizon is called the envelope
<stellar-slack>
<sacarlson> maybe I'm wrong you can only put a single transaction in an envelope, now I'm not sure
pixelb has joined #stellar-dev
<stellar-slack>
<powderfan> So I cannot use memo, to mark the transaction as 'coming from Centaurus' :S
<stellar-slack>
<powderfan> Any other idea?
<stellar-slack>
<sacarlson> I'm not understanding why you can't still mark it as coming from Cent..
<stellar-slack>
<sacarlson> if broken into multi transactions instead of one transaction with many ops
<stellar-slack>
<sacarlson> you can still make your operation so one can't be done without the other with 2 signers with A sending to B with his sig on the transactions and the other sender B sending his to A with his sig on it. it that close?
pixelb has quit [Ping timeout: 246 seconds]
stellar-slack has quit [Remote host closed the connection]
stellar-slack has joined #stellar-dev
[7] has quit [Ping timeout: 250 seconds]
TheSeven has joined #stellar-dev
<stellar-slack>
<powderfan> test net down: are we talking about old stelllard-testnet or stellar-core testnet and horizon?
<stellar-slack>
<jed> Testnet Horizon is still up. That is why you can get history still
<stellar-slack>
<jed> But testnet itself is down
<stellar-slack>
<jed> I can give you lumens on the live network if you want to try there
<stellar-slack>
<powderfan> that would be great. Do you run a horizon server connected to live? Because I don't run a local instance. I just created keypair, so you could send to GDDGZJZSUVWN76BNQG5MDE3X6NGAEOI2CTGCOKJSKYGISREXE7LLK47N
<stellar-slack>
<powderfan> thanks, but then it does not fit. Need something I can place on trx or operation level.
<stellar-slack>
<jed> if you set home domain you should provide federation for people. which might be a cool thing to do anyway
<stellar-slack>
<jed> then people wold be bob*http://centaurus.com|centaurus.com or whatever
<stellar-slack>
<sacarlson> anyplace your account sends your destination can see with home_domain.
<stellar-slack>
<jed> powderfan ok you have lumens
<stellar-slack>
<sacarlson> but yes I think I see powederfan's point as in the even a single account has more than one sub accounts at multi gateways it might be nice to have memo in the operation
<stellar-slack>
<powderfan> Yes federation is cool, but not my priority at the moment, because I do not want to host a service and manage accounts. Later sure.
<stellar-slack>
<powderfan> And one more question: what is the inteded way to determine all assets accepted by a certain account. At the moment I would scan all effects for the account (from genesis block) and accumulate all trustline effects. But this doesn't seem very effective.