04:39 <sacarlson> I am guessing that this is the method of sending hex tx transactions into horizon http://docs.stellarhorizon.apiary.io/#reference/default/transaction/submitting-a-transaction, I've tried this with a hex tx for a create account and get 500 Internal Server Error (RestClient::InternalServerError)

04:40 <sacarlson> using this: values = CGI::escape('tx=00000000347305284a91e772e467c59b63af978ca95d7e1ef8488138849f807afe023e7c0000000a00003c0f0000000300000000000000000000000100000000000000000000000037db4bb65d6a75b21d9b4b5c921bacedac7b274de1dfd4f85a2bf54d502c5a55000000012a05f2000000000000000001fe023e7c000000404f09468bfb89d75d70c2333de463257e2415779f42ad974ad6d9fedb1f3d4ecf9d5f2208f51e1f6fbfa9e3433418259e745eee09e1b504b11fd535f924e3eb02')

06:48 <sacarlson> I'm guessing that I"ve figured out how to create hex transactions but failed to figure out a method to pass any of them into horizon or the stellar-core yet, I'm stuck until I get past this problem

07:05 <stellar-slack> <matschaffer> sacarlson if you already have it encoded as xdr, you should be able to hand it to stellar-core directly via the /tx endpoint I think

07:06 <stellar-slack> <matschaffer> at least I have something like that in my console history `curl http://localhost:39132/tx\?blob\=2e3c...`

07:06 <sacarlson> @matschaffer I'm not running a stellar-core I'm just attempting to setup client transactions

07:06 <stellar-slack> <matschaffer> ah

07:07 <sacarlson> no such thing as client?

07:07 <sacarlson> I must run a core?

07:08 <sacarlson> ah but that curl you provided might still work I have address of running core but failed at them also

07:14 <sacarlson> nope: curl http://core-testnet1.stellar.org:39133/tx\?blob\=00000000347305284a91e772e467c59b63af978ca95d7e1ef8488138849f807afe023e7c0000000a00003c0f0000000300000000000000000000000100000000000000000000000037db4bb65d6a75b21d9b4b5c921bacedac7b274de1dfd4f85a2bf54d502c5a55000000012a05f2000000000000000001fe023e7c000000404f09468bfb89d75d70c2333de463257e2415779f42ad974ad6d9fedb1f3d4ecf9d5f2208f51e1f6fbfa9e3433418259e745eee09e1b50

07:14 <sacarlson> curl: (56) Recv failure: Connection reset by peer

07:15 <sacarlson> that seems to be an active port on that stellar-core address that is default

07:16 <stellar-slack> <matschaffer> it’d be 39132, the http port. 39133 is the peering port

07:16 <sacarlson> oh ok but it seemed inactive with nmap

07:17 <stellar-slack> <matschaffer> it only listens on localhost by default

07:17 <stellar-slack> <matschaffer> you can open it up with https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_example.cfg#L6 but it contains some commands that shouldn’t be run by untrusted sources

07:19 <sacarlson> ok then I"m back to figuring out how to interface with horizon

07:19 <sacarlson> it's timed out

07:19 <sacarlson> I'm not going to have 1000's of clients all run cores just to play poker

07:20 <sacarlson> or is that my only option?

07:23 <stellar-slack> <matschaffer> that’s not the plan anyway

07:24 <stellar-slack> <matschaffer> sacarlson: you were sending these to horizon-testnet I presume?

07:26 <sacarlson> I tried hozizon and core address. I'll paist the addresses I've already tried.

07:26 <stellar-slack> <matschaffer> I’ll take a look at the logs to see if I can spot any obvious reason for the 500

07:26 <sacarlson> I should assume the reason that there is no working lib for https://github.com/stellar/ruby-stellar-lib that maybe it just can't be done yet

07:27 <sacarlson> ok thanks

07:28 <stellar-slack> <matschaffer> guessing this is it: ``` NoMethodError (undefined method `tx' for nil:NilClass): app/models/transaction_submission.rb:118:in `transaction_hash' app/serializers/transaction_submission_serializer.rb:5:in `block in class:TransactionSubmissionSerializer' config/initializers/oat_renderer.rb:27:in `block in <top (required)>' app/controllers/transactions_controller.rb:82:in `render_submission_response'

07:28 <stellar-slack> app/controllers/transactions_controller.rb:64:in `create' lib/request_metrics.rb:16:in `call’ ```

07:29 <sacarlson> I'm not sure what I'm reading here

07:30 <stellar-slack> <matschaffer> a stack from https://github.com/stellar/horizon/blob/master/app/models/transaction_submission.rb

07:30 <sacarlson> this is from logs?

07:30 <stellar-slack> <matschaffer> yeah

07:30 <stellar-slack> <matschaffer> not guaranteed to be your request, but testnet is pretty quiet so good chance it’s yours

07:31 <stellar-slack> <matschaffer> looks like that attempts to run it through ``` raw = Convert.from_hex(tx_envelope) Stellar::TransactionEnvelope.from_xdr(raw) ```

07:33 <stellar-slack> <matschaffer> I… can’t even see where TransactionEnvelope.from_xdr is getting defined

07:34 <stellar-slack> <matschaffer> might have to get input from scott when he’s around. I know at least one XDR change hit stellar-core master today so if you’re using that to generate the transaction, it’s likely the horizon on testnet doesn’t know how to parse it

07:35 <sacarlson> I"m just creating a hex xdr and trying to send it through any path that will accept htem

07:35 <sacarlson> them

07:36 <stellar-slack> <matschaffer> creating from what though?

07:37 <sacarlson> I'll paiste you the code but mostly derived from ruby stellar-base functions

07:37 <sacarlson> I'm also looking at the code that I assume works in the stellar-core-commander

07:38 <sacarlson> but all this focuses at sending the hex to the core

07:38 <sacarlson> localhost

07:38 <stellar-slack> <matschaffer> what I’m wondering is if there’s maybe a mismatch between what you’re using to build the xdr and what testnet expects

07:39 <sacarlson> well I must have the api not setup correct or in the wrong format

07:39 <sacarlson> no working examples to go by

07:39 <sacarlson> so not sure anything works

07:42 <stellar-slack> <matschaffer> it’s entirely possible nothing works right this moment. The whole delivery pipeline is read so what you grabbed from stellar-core-commander doesn’t technically work either

07:43 <sacarlson> this is the present functions I working on the focus now is create_account as I can't do anything until I get that working http://pastebin.com/xy0uaS0L

07:43 <stellar-slack> <matschaffer> also if what you’re using to build the xdr uses a different spec than what testnet expects it’ll probably fail

07:44 <stellar-slack> <matschaffer> testnet is on 0.0.1-62-5f94fa02

07:44 <sacarlson> ok that's something to look at

07:45 <sacarlson> do you have any hex transaction that you know works at present?

07:46 <stellar-slack> <matschaffer> Not handy

07:47 <sacarlson> this is the basic code that I presently use to create the hex for the create_account http://pastebin.com/MyaYaqgr

07:47 <sacarlson> maybe you have a method to take hex transaction and stick them into your running core?

07:49 <stellar-slack> <matschaffer> Yeah I could probably feed them into the http port on this end. Though it may be quicker for you to run a test stellar-core on your end.

07:50 <sacarlson> ya I'm thinking just to progress I should just run a stellar-core to at least determine if the hex code works

07:50 <sacarlson> the output of my code in the last run was this:

07:50 <sacarlson> ./create_account.rb

07:50 <sacarlson> destination account gsigz2tB6ML635kRNWpqF2xg5BaZRkGZheRt1MnJGMKstYnZ9xa

07:50 <sacarlson> destination seed s3PW9b3v5AHA4ciNANANN9mxYh78zHG7S9hRDCD1iCz6MmfjxgV

07:50 <sacarlson> result: 00000000347305284a91e772e467c59b63af978ca95d7e1ef8488138849f807afe023e7c0000000a00003c0f00000003000000000000000000000001000000000000000000000000f2fed64fa3eb496d2c4c3f3a77e959a7e368c1061b3350f80863de002609654200000002540be4000000000000000001fe023e7c000000400cecd9c6f0363c76f7f399d2d1c9ae12408f52e23807a50336c4fba7850fbd24881de958195ac0a2ca5f0ede20dccfcb7736ca2f20189bc7b64472b70a58bb01

07:50 <sacarlson> sacarlson@sacarlson-asrock ~/github/poker_accounting/stellar-core $

07:50 <stellar-slack> <matschaffer> I actually need to run out for a bit anyway. If you have access to docker we publish images to docker hub

07:51 <stellar-slack> <matschaffer> See stellar/docker-stellar-core for a readme if you go that route

07:51 <stellar-slack> <matschaffer> On github

07:51 <sacarlson> yes I have docker installed but only ran basic tests with it not very familuer with it's operation

07:52 <sacarlson> ok nothing to loose at this point so I'll give that a try

07:52 <stellar-slack> <matschaffer> Could build/run stellar-core direct too, it's not that bad of a build

07:52 <sacarlson> thanks matschaffer

07:52 <stellar-slack> <matschaffer> Np. Sorry you hit us on a pretty messy day

07:52 <sacarlson> I already have the code downloaded and was looking at it

07:52 <sacarlson> ha ha story of my life

07:53 <sacarlson> no rush I'm sure I'll have my stuf figured out long before you get all the bugs out anyway

07:53 <sacarlson> my code already works on the old stellar

07:59 <stellar-slack> <matschaffer> Yeah, code at rest is definitely easier to integrate with.

09:38 <stellar-slack> <lab> when will testnet upgrade to base32 ?

10:18 <stellar-slack> <matschaffer> I think we're pretty close. Still sorting out all the auxiliary stuff from the change. Once the basic acceptance is passing it'll be time to update testnet i'd say

11:46 <stellar-slack> <lab> it's cool to be away from base58. stellar is unique.

12:32 <sacarlson> @lab why would base32 to any better than base58. from what little I understand of the base is that it would require a much longer string to be even be marginally close in security

12:33 <sacarlson> assuming that base32 means that only 32 of the letters in alphabet would be used to create accounts and keys instead of 58

12:43 <stellar-slack> <bartek> @sacarlson, check this issue: https://github.com/stellar/stellar-core/issues/599

12:43 <sacarlson> ok

13:18 <sacarlson> so from what little I read it seems I was wrong. so if I understand it correctly now then the keys and address would only require to be about 6 characters longer than before to achieve the same results

13:37 <stellar-slack> <fredolafritte> https://horizon-testnet.stellar.org is served by horizon (ruby) or go-horizon ?

13:39 <sacarlson> @fredolafritte good question as I guess they have two versions maybe that's why my ruby client doesn't work?

13:40 <stellar-slack> <fredolafritte> my js based client doesn't work either

13:40 <sacarlson> oh so maybe it's not me at all

13:41 <sacarlson> @fredolafritte but did it ever work? I just started so never seen anything that worked

13:42 <stellar-slack> <fredolafritte> we are in the same spaceship, never see it work

13:42 <stellar-slack> <bartek> from what I can tell, go-horizon is responding to requests that are already implemented in go-horizon. the rest of the request are forwarded to [ruby] horizon instance.

13:44 <sacarlson> I can get account ballances and other things to work but just can't get any tx transactions to function

13:44 <stellar-slack> <fredolafritte> that why go-horizon replies with "not_implemented" when executed locally ...

13:47 <stellar-slack> <bartek> yeah, it seems there are some temp problems with horizon-testnet (I couldn’t submit mu test transaction as well). @scott will probably fix this when he’s up.

14:15 <sacarlson> I'm starting to look at the posibility to try the docker-steller-core, if I was to pursue I assume the single.env would be the most probable to work. I've only touched docker one time with hello world so not sure this is the best idea

14:16 <sacarlson> I guess the first question would be what core pattern to use?

18:15 <bittrex-richie> hey all.. are the sfd servers out of whack again? :(

18:27 <stellar-slack> <jed> they seem ok for me? maybe the one you were talking to hiccuped?

19:11 <bittrex-richie> looks that way now.. everything looks happy again

19:11 <bittrex-richie> just wanted to pipe up early incase something was up ;)

19:55 <stellar-slack> <jed> yeah thanks

20:23 <stellar-slack> <matschaffer> sacarlson: if docker looks onerous you should probably just build/run stellar-core directly (or install a deb if you’re on that sort of distro)

20:24 <stellar-slack> <matschaffer> but single.env should do the trick if you want to give it a shot

20:26 <stellar-slack> <matschaffer> I’ll add a section to the readme for that file as well, though it’s basically the same pattern as the others. Looks like my markdown is a little off in that doc anyway, so I’ll get it fixed up

20:26 <stellar-slack> <matschaffer> oh, key format though. I’ll swap that while I’m in there

21:46 <stellar-slack> <matschaffer> https://github.com/stellar/docker-stellar-core/pull/18 there we go