01:14 <stellar-slack> <sacarlson> thank you very much for this feed back on my ssl problem. I'll check it out for http://equid.co|equid.co

01:24 <stellar-slack> <sacarlson> however I've had a third party just check my wallet and it does the lookup without any ssl problem from firefox and chrome. so I'm not sure what the problem is

01:24 <stellar-slack> <sacarlson> maybe in the stellar.taml file?

01:25 <stellar-slack> <sacarlson> my certs are fully working as far as I can tell

01:28 <stellar-slack> <jed> sacarlson from FF:

01:28 <stellar-slack> <jed> http://api.equid.co|api.equid.co uses an invalid security certificate. The certificate is not trusted because the issuer certificate is unknown. The server might not be sending the appropriate intermediate certificates. An additional root certificate may need to be imported. (Error code: sec_error_unknown_issuer)

01:28 <stellar-slack> <sacarlson> no wait we are now having a problem on firefox

01:29 <stellar-slack> <sacarlson> it seems not all browsers support this cert provider

01:29 <stellar-slack> <sacarlson> so some older versions of browsers I'm guessing will have this problem

01:30 <stellar-slack> <sacarlson> it does work on both version of firefox and chrome I have

01:35 <stellar-slack> <dzham> works for me

01:37 <stellar-slack> <sacarlson> just not all yet

01:39 <stellar-slack> <sacarlson> and thanks @dzham it was your idea to use lets encrypt and it's cool and fast

01:49 <stellar-slack> <sacarlson> also we don't use the same certs at at the root of the site

02:11 <stellar-slack> <sacarlson> so I'm guessing @powderfan you might be able to test your federation with http://equid.co|equid.co and the other if you add trust to the certs to the browser you are using to test from. not sure how you add certs on an android but it must be posible

02:32 <stellar-slack> <eno> @powderfan: can you try again? added https support for http://naobtc.com|naobtc.com

06:18 <stellar-slack> <jed> Eno are you going to put something up at naobtc?

06:20 <stellar-slack> <eno> i plan to make a btc gateway or bridge . and naobtc will redirect to http://256kw.com/gateway|256kw.com/gateway i guess

06:31 <stellar-slack> <eno> it's not ready yet.

06:36 <stellar-slack> <jed> Ah ok

06:39 <stellar-slack> <jed> I was thinking the way you would send BTC into stellar is just have a bitcoin address that you publish and if BTC is sent to it with the OP_RETURN set to stellar accountID you just forward the BTC credit to that stellar account

06:44 <stellar-slack> <eno> this sound great!

06:45 <stellar-slack> <jed> yeah I think most bitcoin clients let you put messages in there now

06:55 <stellar-slack> <dzham> you could also just have people register their intent before transacting, and give them their unique bitcoin address

06:56 <stellar-slack> <dzham> that’s the way the XLM->BTC side of things work anyways

07:00 <stellar-slack> <eno> yes this is what i am trying

07:05 <stellar-slack> <jed> Its cooler if they don't have to. if they can just send

07:08 <stellar-slack> <dzham> @jed: it is

07:09 <stellar-slack> <dzham> Is it easy to check the OP_RETURN? You’d just monitor one address, so I guess that makes it a lot simpler :S