00:25 <stellar-slack> <dzham> @jed: A bi-directional payment channel. Sweet!

00:26 <stellar-slack> <dzham> I wonder if that could be made into something that worked for @sacarlson and his poker client.

00:27 <stellar-slack> <dzham> Heads-up would be fine. But how about more players?

00:36 <stellar-slack> <dzham> Just add more `xEND`assets? It gets a bit messy with all the various pre-signed transactions, but it would mean that you wouldn’t have to wait for a ledger close between each player placing their bet.

00:37 <stellar-slack> <jed> yeah

00:38 <stellar-slack> <dzham> Coolio!

00:38 <stellar-slack> <jed> you would probably do a pair between the pot and each player

00:39 <stellar-slack> <eva> Also, quick heads up that we’re holding “integrator office hours” tomorrow at 6am PST and 7pm PST - basically a chance to ask any questions about developing on Stellar, or how you could build your particular app / service on Stellar.

00:39 <stellar-slack> <eva> It’s just here on Slack, but it’s a time when Stellar devs will specifically be around to answer questions and chat.

01:41 <stellar-slack> <sacarlson> is the next upgrade of stellar-core over v0.3.3 running on horizon going to be a breaking change? as I see changes in ruby-stellar-base with modified structures in xdr with "state"

01:55 <stellar-slack> <sacarlson> if so I'm guessing I will be again forced to create a custom base to fix this bug https://github.com/stellar/ruby-stellar-base/issues/17.

02:03 <stellar-slack> <sacarlson> does anyone see a problem with creating transactions that aren't presigned by what seems to be the master creator but signed by a valid signer instead so that the master can later sign it?

02:05 <stellar-slack> <dzham> nope, sounds perfectly fine

02:05 <stellar-slack> <sacarlson> does this bug persist in js-stellar-sdk I wonder also?

02:11 <stellar-slack> <lab> @eva what's the channel?

02:14 <stellar-slack> <eva> #general should be good :)

02:37 <stellar-slack> <eno> dzham it will be great to use pip :+1:. i have no experiment in pip upload before, i will learn

08:13 <stellar-slack> <raymens> @sacarlson: why not just create a PR to fix those bugs? As it seems you already did

09:42 <stellar-slack> <raymens> I've created a proposal for Stellar related to wallets and assets, https://github.com/stellar/stellar-protocol/issues/21

10:27 <stellar-slack> <sacarlson> yes raymens I was thinking the same thing but have never done a PR but I did start researching it today

10:29 <stellar-slack> <raymens> sacarlson: great, if you have any questions I'm sure anyone is happy to help. It might sound complicated but is actually really simple.

12:28 <stellar-slack> <sacarlson> ok raymens I did what you suggested and did my first ever PR for issue #17 https://github.com/stellar/ruby-stellar-base/pull/20. so now if it blows up you can blame it on me ha ha

12:31 <stellar-slack> <raymens> sacarlson: looks great to me. Except maybe shorten the title to just say what it fixes. The actual codefix is already visible in the *changes* tab

12:33 <stellar-slack> <raymens> simple huh? :)

12:34 <stellar-slack> <sacarlson> can I change it now or is it too late to change the title?

12:35 <stellar-slack> <sacarlson> ya not too hard now that I've done it the first time I won't worry doing it again

12:35 <stellar-slack> <sacarlson> by default it just took the change tab and put it there

12:37 <stellar-slack> <raymens> Yeah you can still change it, it's also possible to add more commits (not required though in this case)

12:37 <stellar-slack> <sacarlson> ya I just did good idea

15:29 <stellar-slack> <raymens> @sacarlson: btw, why does it use your mss-server. It seems that all the actions shown on the UI is possible using horizon?

15:30 <stellar-slack> <sacarlson> mss-server is an option to test and compare speed of mss-server compared to horizon. mss-server also contains functions that horizon doesn't have mostly in market order operations

15:31 <stellar-slack> <sacarlson> and multi signing operations

15:31 <stellar-slack> <sacarlson> and dealing with not haveing to have a stellar lib at all and work from just restclient

15:32 <stellar-slack> <raymens> server-side transaction building?

15:34 <stellar-slack> <sacarlson> yes as an option but also supports building on the client side as min_client demonstrates

15:35 <stellar-slack> <sacarlson> for details on mss-server see docs in readme.md https://github.com/sacarlson/stellar_utility/tree/master/multi-sign-server

15:39 <stellar-slack> <sacarlson> it totals only about 127kb of my code. it's a mini horizon

15:40 <stellar-slack> <raymens> did you create issues for the stuff you missed in js-stellar-sdk?

15:41 <stellar-slack> <sacarlson> what's missing?

15:41 <stellar-slack> <raymens> multi-signing operations it seems

15:42 <stellar-slack> <raymens> and the markter order operations in horizon

15:42 <stellar-slack> <sacarlson> oh no I didn't, I asked what others needed but didn't seem to be a need for it. but my poker needed it

15:43 <stellar-slack> <sacarlson> no they are just simple database lookups didn't need to ask for it just did it

15:43 <stellar-slack> <sacarlson> it may already exist but at times it easier to work from what you create.

15:44 <stellar-slack> <sacarlson> I can't keep up with what they added to horizon. I learn stuf they have everyday

15:44 <stellar-slack> <sacarlson> I don't have the cool websocket feed they have that I'm not sure I will ever duplicate

15:48 <stellar-slack> <raymens> Oh okay, i understand

15:52 <stellar-slack> <sacarlson> but the stellar staff is fantastic I've asked a million questions and they've answered them all

15:54 <stellar-slack> <raymens> Yup :)

17:35 <stellar-slack> <brian.ebert> Echo @sacarlson . Support here has been very helpful. BTW, what browser(s) are being used during development?

17:39 <stellar-slack> <scott> thanks y’all. We will try to keep the level of support up. Regarding what browsers we use: We don’t have any standard policy. I tend to do all my development in chrome or canary, and then at regular-ish intervals I’ll check things out in firefox. Our newer projects use sauce labs to test on chrome, firefox and ie 11: https://github.com/stellar/js-stellar-base/blob/master/karma-sauce.conf.js

17:40 <stellar-slack> <scott> In the past, I mostly used browsermob to test in the IE’s before a major launch, but not really during minor changes

20:57 <stellar-slack> <fim> hi I have some Lumens/stellers in centaurus mobil wallet. Is there an ordinary wallet I can use?

20:58 <stellar-slack> <eva> @fim: hey! What do you mean by ordinary? Desktop, or developed by http://Stellar.org|Stellar.org?

20:58 <stellar-slack> <fim> I think both actually

21:07 <stellar-slack> <scott> @fim: you might try https://lobstr.co/, they have a web-based wallet for desktop and mobile versions as well

21:07 <stellar-slack> <fim> hi thank you

21:10 <stellar-slack> <scott> np!

21:29 <stellar-slack> <fim> hi scott a send 500 to my new Lobstr wallet from Poloniex. But nothing happen, but I have 20 Lumens for some reason?

21:29 <stellar-slack> <fim> do you know how long time it takes?

21:30 <stellar-slack> <fim> Hi I got them now no problems

21:30 <stellar-slack> <scott> fim: Poloniex has a “withdrawal history” section that should have status information

21:30 <stellar-slack> <scott> cool! glad to see they came through

21:31 <stellar-slack> <fim> I thought it only take 3 sek to send

21:31 <stellar-slack> <scott> in general, most transactions submitted to the stellar network should get completed in under 10 seconds.

21:31 <stellar-slack> <fim> here more then 3 min

21:32 <stellar-slack> <scott> that is assuming that poloniex sent the funds at the exact instant you requested the withdrawal. I believe they review every withdrawal by hand

21:33 <stellar-slack> <fim> ok thx

21:33 <stellar-slack> <scott> np

23:29 <stellar-slack> <sacarlson> @scott I noted in ruby-base a change "Add memo helpers" will that change work in the older 0.6.1 ruby-stellar-base with stellar-core 0.3.2? if not what do I have to wait for?