08:03 <stellar-slack> <jesse> bros, 1 day notice on old network deprecation?

08:07 <stellar-slack> <lab> jesse, are you also the one who got message in last day?

08:07 <stellar-slack> <lab> :,)

08:08 <stellar-slack> <jesse> apparently :rage4:

08:09 <stellar-slack> <lab> it was really top secret..

08:09 <stellar-slack> <lab> i thought stellard network will last for months before.

08:16 <stellar-slack> <lab> poloniex and bc38 have already suspended deposit/withdraw

09:40 <stellar-slack> <dzham> anyone get http://launch.stellar.org|launch.stellar.org to work? I can’t access any of my accounts there

09:41 <stellar-slack> <dzham> so I can’t consolidate my funds, can’t convert, can’t have no XLM

09:42 <stellar-slack> <sacarlson> oh they didn't tell you we did all that yestarday it's already closed

09:42 <stellar-slack> <sacarlson> just kiding

09:43 <stellar-slack> <dzham> I was too busy earning

09:43 <stellar-slack> <sacarlson> my guess is the first few hours or even days there only site the converts will be mest up

09:44 <stellar-slack> <dzham> The majority of my STR isn’t even on a http://launch.stellar.org|launch.stellar.org account, so not sure how to convert

09:45 <stellar-slack> <sacarlson> oh wow you should have moved that already

09:45 <stellar-slack> <sacarlson> it's not on the stellar network?

09:45 <stellar-slack> <sacarlson> some exchange?

09:46 <stellar-slack> <dzham> it’s on the network, but cold wallet… generated the keys myself

09:46 <stellar-slack> <sacarlson> I'm not even sure how that works, don't the wallets js just sign them?

09:47 <stellar-slack> <dzham> Oh well, it’s only $2 or something anyways

09:47 <stellar-slack> <sacarlson> I have about $30 worth

09:47 <stellar-slack> <dzham> or whatever it’s worth nowadays

09:47 <stellar-slack> <sacarlson> I think I paid $40

09:51 <stellar-slack> <dzham> I guess we will have to wait and see

09:51 <stellar-slack> <sacarlson> well I can still login but still not active to convert yet

09:59 <stellar-slack> <dzham> Oh, got it working now

10:15 <stellar-slack> <timon> Any word on when they will switch to the new network exactly? Nov, 3rd is not really a very exact point in time around the globe.

10:31 <stellar-slack> <sacarlson> it's more like Thailand time in that it's just not an exact thing I guess, but I have seen some time numbers here

10:32 <stellar-slack> <powderfan> @dzham: I'm working on the funds migration from within my android stellar wallet. So if you have android you could do the following: 1. Get Centaurus Stellar Wallet from PlayStore 2. Import your keys (you have to type them though)

10:33 <stellar-slack> <powderfan> Currently there is no way to test the upgrade message, so I cannot finish and deploy the feature

10:34 <stellar-slack> <dzham> @powderfan: looks like I’m all set, but thanks anyway

10:35 <stellar-slack> <timon> There is a tool for upgrading accounts that are not on http://launch.stellar.org|launch.stellar.org: https://github.com/stellar/stellar-upgrade

10:49 <stellar-slack> <dzham> Haha, looking through my accounts… When stellar launched a year ago, after a while someone randomly posted a secret key on stellartalk. I didn’t find it until a while later, but at one point in time, *after* that happened, it had 100k STR in it.

10:50 <stellar-slack> <sacarlson> wow scary

10:50 <stellar-slack> <sacarlson> I've posted many but hopefully only for testnet

10:50 <stellar-slack> <dzham> Yes.. 1) that someone was stupid enough to post their seed. 2) that no one noticed for over a month

11:05 <stellar-slack> <powderfan> Is ~https://api.stellar.org/upgrade/upgrade~ supposed to be working now? Cause I get `{"status":"fail","code":"not_found"}`

11:42 <stellar-slack> <raymens> How can I decode the values in txhistory (txbody, txresult, txmeta)?

12:03 <stellar-slack> <raymens> I've succeed decoding the txbody and txmeta, but txresult won't decode into a TransactionResultSet (using ruby-stellar-base)

12:06 <stellar-slack> <raymens> Nvm, I guess it was a TransactionResultPair :)

12:32 <stellar-slack> <jed> powderfan: it won't work until the upgrade starts. in about 6 or 7 hours

12:50 <stellar-slack> <powderfan> ok, and we can test it only on live network? Or would it work on the testnet (old to new) as well?

14:38 <stellar-slack1> <sacarlson> oh cool you play with ruby raymens? I wrote some code the decodes most of the results

14:40 <stellar-slack1> <raymens> yeah not a big fan of it though :P

14:40 <stellar-slack1> <sacarlson> so why play with it then, I think the tools they have on node might be better as I just started playing with that

14:42 <stellar-slack1> <raymens> because the same goes for nodeJS hehe

14:42 <stellar-slack1> <sacarlson> oh ok I thought they had a tool to decode before I did

14:43 <stellar-slack1> <sacarlson> I use this decoder in my mss-server that outputs a more english readable responce to transactions without decoding

14:45 <stellar-slack1> <sacarlson> at least I think that's the one, I have others that also decode the meta data and other info

14:54 <stellar-slack1> <raymens> I'm not actually building stuff with ruby though, just testing some stuff :)

15:08 <stellar-slack1> <jed> powderfan: live network only

15:22 <stellar-slack1> <sacarlson> raymens and here's an old tool I used to use before I integrated error decodeing https://github.com/sacarlson/stellar_utility/blob/master/examples/decode_error.rb

15:24 <stellar-slack1> <sacarlson> and some example of my other xdr decoders https://github.com/sacarlson/stellar_utility/blob/master/examples/xdr_decoder.rb

15:31 <stellar-slack1> <raymens> thanks for the links, I'm fine with all the decoding now though :)

20:33 <stellar-slack1> <nelisky> u'result_codes': {u'transaction': u'tx_bad_auth'} <- that's something wrong with the transaction signing, right?

20:38 <stellar-slack1> <jed> likely

21:04 <stellar-slack1> <scott> @nelisky: tx_bad_auth get’s triggered by one of 2 conditions: A signature on the envelope may be incorrect (most likely cause would be you signed the transaction for testnet when you meant it to be against the public net or vice versa), or you may have included too few signatures in a multi-sig situation

21:05 <stellar-slack1> <nelisky> yeah, testnet sig was the problem, scott. Now I'm trying to understand why I get an op_no_destination...

21:06 <stellar-slack1> <scott> are you familiar with the new semantics around creating accounts? They are no longer created automatically by making a payment to an unknown address

21:06 <stellar-slack1> <nelisky> I am not, and that might very well be it

21:07 <stellar-slack1> <scott> https://www.stellar.org/developers/learn/concepts/list-of-operations.html#create-account

21:07 <stellar-slack1> <nelisky> or the python lib I'm trying to get working on python2 is kicking me in the butt :)

21:07 <stellar-slack1> <scott> :)

21:07 <stellar-slack1> <nelisky> eno: t.operations[0] <stellar_base.operation.PaymentOperation at 0x10c28fdd0>

21:08 <stellar-slack1> <nelisky> t.operations[0].to_xdr_object() Operation(sourceAccount=[], body=<class 'stellar_base.stellarxdr.StellarXDR_pack.nullclass'>)

21:08 <stellar-slack1> <nelisky> am I missing the xdr def for this operation?

21:09 <stellar-slack1> <nelisky> scott: I knew about createaccount, just didn't know it precluded the sending to some newly created address

22:03 <stellar-slack1> <nelisky> when one looks at transactions for account, how volatile is the paging token? Is it specific to an horizon instance?

22:09 <stellar-slack1> <scott> @nelisky: it’s durable and global… it’s tied to the ledger sequence and application order that the transaction has in the validated ledger

22:10 <stellar-slack1> <nelisky> scott: great, so storing cursors instead of iterating ledgers it is!

22:10 <stellar-slack1> <scott> The spec for it is here: https://github.com/stellar/horizon/blob/master/src/github.com/stellar/horizon/db/total_order_id.go#L8

22:23 <stellar-slack1> <irisli> whats the difference between http://horizon-live.stellar.org|horizon-live.stellar.org and http://horizon.stellar.org|horizon.stellar.org?

22:23 <stellar-slack1> <scott> nothing

22:24 <stellar-slack1> <irisli> oh just an alias. ok thanks

22:48 <stellar-slack1> <jed> powderfan are you having issues with upgrade in your wallet still?

22:49 <stellar-slack1> <powderfan> no, I think I'm fine. not so easy to test though

22:49 <stellar-slack1> <powderfan> hopefully tomorrow I'll be able to deploy an alpha version

22:49 <stellar-slack1> <eva> woooot! @powderfan can’t wait

22:49 <stellar-slack1> <powderfan> beta and production next days

22:57 <stellar-slack1> <nelisky> so, thinking about the upgrade path for my case, will there be a way for users to "return" old stellar funds to DR using some destination tag I define to identify them?

23:00 <stellar-slack1> <jed> nelisky: let's discuss what you need. message me

23:17 <stellar-slack1> <raymens> Is there a reason for having the 4 and 12 character assets other than wanting issuers to use a proper assetcode?

23:18 <stellar-slack1> <jed> what do you mean proper?

23:19 <stellar-slack1> <raymens> the ISO4217 and ISIC is mentioned on the Stellar page

23:20 <stellar-slack1> <jed> both of those will fit in these

23:21 <stellar-slack1> <raymens> Yeah I was just wondering why not use a single 12 character length instead of both 1-4 and 5-12. As it has a lot of effect in the codebase

23:22 <stellar-slack1> <richiela> jed: got a few minutes to chat?

23:22 <stellar-slack1> <jed> yeah

23:23 <stellar-slack1> <jed> raymens: we expect most will only need 4 characters so it is an optimization

23:23 <stellar-slack1> <raymens> got it, thanks

23:23 <stellar-slack1> <raymens> that makes sense

23:25 <stellar-slack1> <sacarlson> why would you require the account viewer to enter the secret seed instead of just the public one?

23:26 <stellar-slack1> <dzham> because you can send lumens with it

23:26 <stellar-slack1> <sacarlson> oh it's also the wallet

23:35 <stellar-slack1> <timon> there’s an error/typo in the documentation https://www.stellar.org/developers/js-stellar-base/learn/building-transactions.html#adding-memos

23:35 <stellar-slack1> <timon> Memo.hash and Memo.returnHash is actually a 32-byte hash, not a 32-bit hash

23:36 <stellar-slack1> <eva> @timon thanks for the catch, can you submit a pull request with the change

23:36 <stellar-slack1> <eva> ?

23:36 <stellar-slack1> <timon> not right now, I’m working on the upgrade. maybe later this week

23:44 <stellar-slack1> <eva> sure, np - if anyone else wants to submit it feel free

23:46 <stellar-slack1> <jed> I fixed it already