07:18 <stellar-slack> <powderfan> @jed: yes mobile only. And currently android only, though in principal cordova is conceived to work on apple and windows with (almost) the same code base

07:50 <stellar-slack> <sacarlson> my stellar-core doesn't seem to start today and displayed strange in and out of sync over the last few hours per my logs

08:49 <stellar-slack> <sacarlson> tried new build and did another full reset with it but same stuck state "joining SCP"

08:51 <stellar-slack> <lab> yes

08:51 <stellar-slack> <lab> i met it too

08:51 <stellar-slack> <lab> i guess is caused by commit abf2c408c

08:52 <stellar-slack> <sacarlson> so is there a working commit we can now run?

08:53 <stellar-slack> <sacarlson> I note that horizon is still working so something must work

08:53 <stellar-slack> <lab> i guess not

09:05 <stellar-slack> <sacarlson> I looking at what they have in the present latest docs on config files and I see a few changes that I'm not sure what they might do

09:05 <stellar-slack> <sacarlson> like

09:05 <stellar-slack> <sacarlson> adding sdf1 at the end?

09:17 <stellar-slack> <sacarlson> after the validator change and also added one more line with 51% I now have sync

13:45 <stellar-slack> <raymens> What's the best way to execute the scheduled jobs in horizon-importer?

13:46 <stellar-slack> <sacarlson> I didn't know there was any. it's just the ruby side of horizon I thought

13:47 <stellar-slack> <raymens> There's a ledger-checker and importer job

13:47 <stellar-slack> <raymens> Or is that these get executed automatically?

13:48 <stellar-slack> <sacarlson> I'm not sure I would have to look closer at the code. I only ever used it as the basic interface to transactions

13:49 <stellar-slack> <sacarlson> and to get balances and sequence numbers

13:49 <stellar-slack> <raymens> Oh yeah it seems they get executed automatically, so nvm my question :)

13:49 <stellar-slack> <sacarlson> cool

13:50 <stellar-slack> <sacarlson> so we going to have a back presence of a horizon that we can use on your site?

13:52 <stellar-slack> <raymens> Not at this moment, maybe someday

13:53 <stellar-slack> <sacarlson> ok have fun

15:09 <stellar-slack> <scott> deploying horizon to testnet

16:23 <stellar-slack> <bartek> @powderfan: you only need to change `publicKey` to be the public key not the address. like this:

17:01 <stellar-slack> <powderfan> Ok, thought I could get rid of the dependency to `nacl` but nvm. Maybe stellar-sdk can provide a helper like `function(newAddress, oldSecret){...}`. In the meantime I'm looking forward to trying this out. Will it work from old test-stellard to new test-stellar-core as well?

17:06 <stellar-slack> <bartek> are you going to use it in node or in a browser? if node, you can use `Buffer.toString('base64')` so you won't have to use nacl

21:06 <stellar-slack1> <mason> hey ya'll! Does friendbot require a sequence number? I'm getting a "tx_bad_seq" error: https://horizon-testnet.stellar.org/friendbot?addr=GCCYUTVNYKLQOQVZ56GY5VCDYZWABCV3EHJRFFNSIK7LLYI25LM3BYZX

21:07 <stellar-slack1> <scott> looks like a bug. Let me check it out

21:12 <stellar-slack1> <scott> @mason: It looks like friendbot is actually working fine, but the error you are seeing is caused by https://github.com/stellar/stellar-core/issues/890 (which has not been deployed to testnet)

21:12 <stellar-slack1> <scott> let me confirm that it isn’t deployed

21:13 <stellar-slack1> <mason> gotchya. Thanks for the info! :stroopy:

21:14 <stellar-slack1> <scott> np :)

21:16 <stellar-slack1> <scott> yep, just confirmed that testnet doesn’t have that fix yet.

21:17 <stellar-slack1> <scott> I can fund an account for you if you are blocked

21:21 <stellar-slack1> <mason> That'd be great! -> GDYFZLVDBXBS37D5PM6AL2HI3I5XKRULH336ZHJYSCL5JRJO6O3FMDJH

21:24 <stellar-slack1> <mason> also I might have some time this weekend to work on a issue. I was thinking this -> https://github.com/stellar/js-stellar-sdk/issues/40 or maybe find something in the horizon backlog. Let me know if there's something you'd really like done!

21:25 <stellar-slack1> <scott> coming right up :)

21:32 <stellar-slack1> <scott> oh, oops. looks like testnet is down. I think jed or nicolas are working on it

21:33 <stellar-slack1> <scott> well, I just paste this here for when it comes back up:

21:35 <stellar-slack1> <scott> As far as tickets god, working on the path finding helpers would be awesome! If you look at the source for the sdk, you’ll notice a bunch of “call_builder” classes. Adding a “path_call_builder” would be a great first step

21:36 <stellar-slack1> <mason> :thumbsup:

21:36 <stellar-slack1> <scott> The horizon reference for the path finding endpoint is here: https://www.stellar.org/developers/horizon/reference/path-finding.html

21:38 <stellar-slack1> <mason> cool cool. Yeah, looks reasonable

21:40 <stellar-slack1> <mason> I'll check back here if I run into any snags!

21:41 <stellar-slack1> <scott> sounds good. I’ll probably be offline most of the weekend, but feel free to @ message me and I’ll get to them when I’m back online

21:42 <stellar-slack1> <mason> excellent will do

22:45 <stellar-slack1> <scott> looks like testnet is back up. And friendbot as well