02:41 <stellar-slack> <vu.bitmark> Hello, I'm finding a way to use stellar to transfer money between Bitcoin exchanges. Do you think it is possible now?

02:43 <stellar-slack> <vu.bitmark> I intend to write a tool to do this process automatically. But I'm not sure this channel is the right place to ask about it. Please forgive me if it's wrong.

02:50 <stellar-slack> <sacarlson> yes this is the right place to ask. we can point you to the info you may need

02:50 <stellar-slack> <sacarlson> to start what language do you plan to develop in?

02:51 <stellar-slack> <sacarlson> @vu.bitmark: ?

03:02 <stellar-slack> <vu.bitmark> I'm using nodejs, or python.

03:04 <stellar-slack> <vu.bitmark> I still does not find out how to deposit/transfer money between exchanges (e.g. Btce, Bitfinex...). Do you think I need a support from these exchanges to use stellar to transfer money?

03:07 <stellar-slack> <sacarlson> at the exchange point at least some of them have api interface for automated transactions

03:07 <stellar-slack> <sacarlson> I don't recall off hand witch did or if they all do

03:08 <stellar-slack> <sacarlson> simple restclient with json interface if I recall

03:08 <stellar-slack> <sacarlson> on the stellar side you would best use the node.js or javascript sdk libs

03:10 <stellar-slack> <sacarlson> for direct bank transactions at least in thailand we also have simple api interface for transactions

03:10 <stellar-slack> <dzham> @vu.bitmark: can you get XLM in/out of the exchanges?

03:10 <stellar-slack> <vu.bitmark> @dzham, I'm not sure. May not.

03:13 <stellar-slack> <dzham> What are you thinking about sending between the exchanges?

03:15 <stellar-slack> <vu.bitmark> You know, I have account at Btce, Bitfinex, and Bitstamp. But I cannot quickly transfer money from an exchange to each other ( I have to use banking now, it's very slow and costly).

03:16 <stellar-slack> <vu.bitmark> So, I'm finding a way to quickly get money from one exchange and deposit it to another one. I see Stellar can help me, but I'm not sure how I can get it.

03:18 <stellar-slack> <vu.bitmark> Can we have a kind of: btce --> xlm --> bitfinex

03:18 <stellar-slack> <dzham> If you're trading BTC/USD, and you want to be able to send the USD faster between the exhanges for arbitrage, then the exchanges themselves would have to issue some kind of Stellar asset (USD most likely), which you would then trade for the USD issued by your destination exchange. I.e, you trade BTC for USD.exchange1 at exchange1, trade USD.exchange1 for USD.exchange2 on the Stellar exchange, and then finall

03:18 <stellar-slack> exchange2

03:18 <stellar-slack> <jed> Vu.bitmark I think you need support from the exchanges in order to do this.

03:18 <stellar-slack> <dzham> But if the exchanges don’t recognize any intermediary Stellar assets, then you’re out of luck

03:19 <stellar-slack> <jed> Yeah you should encourage them to though

03:20 <stellar-slack> <dzham> Definitely encourage them.. They save money on it too, as they don’t have to touch their bank account too often

03:23 <stellar-slack> <dzham> We need people to act as gateways, and exchanges already have the funds to back them

03:25 <stellar-slack> <vu.bitmark> Do you know any US bank accept Stellar assets?

03:26 <stellar-slack> <vu.bitmark> May I transfer USD between banks?

03:28 <stellar-slack> <dzham> I don’t know of any, it’s not the sort of thing I’d expect banks to do at this point in time.

03:29 <stellar-slack> <dzham> Ripple is talking to banks, but that’s more for moving bank between banks. I’m not really expecting normal people do be able to use that, when it’s up and running.

03:39 <stellar-slack> <sacarlson> I've begun the php to stellar bridge function set.

03:40 <stellar-slack> <sacarlson> any other basic commands you guys want me to add to this php lib

03:41 <stellar-slack> <sacarlson> or input on any changes or flaws you all might see

03:57 <stellar-slack> <dzham> 1. add an option to pass the seed using STDIN, just like mysql does, `mysql -u root -p` 2. create ONE commandline tool, and create an NPM package out of it 3. add options to set/change the horizon server, and/or the network. could be a config file where you'reable to add a couple and set a default, that can be overridden on the commandline

03:58 <stellar-slack> <sacarlson> oh good idea

03:59 <stellar-slack> <sacarlson> I considered making just one commandline tool but I also thought this might be good for those to study one at a time to simplify learning

04:00 <stellar-slack> <dzham> I’ve got something similar running for my own purposes, except for 1, half of 2, and 3 :)

04:00 <stellar-slack> <sacarlson> 3.) also very good idea maybe set from ENV?

04:01 <stellar-slack> <sacarlson> I think for 3 i'll just hard code it for now and upgrade it to ENV (envirnment value set) or other later

04:04 <stellar-slack> <sacarlson> thanks again @dzham and by the way this whole idea sprouted from an idea you gave me

04:08 <stellar-slack> <sacarlson> I'm starting to think more about number 2.) as making them all separate files will also be more of a burden to maintain. so maybe later or even now I could make an option that each comand line program would call just one combined command line program

04:09 <stellar-slack> <sacarlson> or just skip my original idea and go with your first and just have one commandline program that had options for functions

04:17 <stellar-slack> <sacarlson> I'v already hit my first problem as I've done all my js sdk devepment in browser I'm now getting throw new Error('no window object present'); so maybe you use a different build of stellar-sdk when running from node on command line?

04:20 <stellar-slack> <dzham> Oh, strange, I’ve never had any issues like that on command line

04:21 <stellar-slack> <sacarlson> so the bower sdk bower I use in the browser should work then?

04:21 <stellar-slack> <dzham> no

04:21 <stellar-slack> <dzham> `npm install —save stellar-sdk`

04:21 <stellar-slack> <sacarlson> ah ok

04:21 <stellar-slack> <dzham> that’s two dashes btw

04:22 <stellar-slack> <sacarlson> cool thanks

04:24 <stellar-slack> <sacarlson> I'm seeing alot of errors here that I assume might be from wrong version of node

04:26 <stellar-slack> <dzham> @sacarlson: dash dash save

04:26 <stellar-slack> <sacarlson> I copied and pasted so I assumed it was correct ha ha

04:27 <stellar-slack> <sacarlson> much better

04:27 <stellar-slack> <dzham> It doesn’t render it correctly, it turns into a Unicode em-dash, I think

04:27 <stellar-slack> <sacarlson> my eyes can't tell the diff from -- and ~

04:28 <stellar-slack> <sacarlson> IC

04:33 <stellar-slack> <sacarlson> cool the first one gen_random_keyset.js is working. it's all down hill from here thanks again @dzham

06:25 <stellar-slack> <sacarlson> I'm getting a new error at line: var key = StellarSdk.Keypair.fromSeed(from_seed); i get: throw new Error("invalid version byte. expected " + expectedVersion + ", g

06:28 <stellar-slack> <sacarlson> the seed string I'm using seems good: SA34I5WXI65OF6ATBXDBTW6F5V72XLNL6PH3ZQXFHNXHIQAWJ2GJ6AMR

06:53 <stellar-slack> <sacarlson> sorry brain fart again, had values in wrong order

11:10 <stellar-slack> <sacarlson> I've published what I have so far that is a basic php support lib for stellar using exec system calls from within php to link to node.js command line functions to add basic stellar network functionality to php code. https://github.com/sacarlson/sacarlson.github.io/tree/master/stellar_php

11:12 <stellar-slack> <dzham> Coolio. I spent some time on parsing command arguments, and figuring out what parameters makes sense. I might give up

11:13 <stellar-slack> <sacarlson> these are basicly only tested on the command line only a few tested in php but they should all work

11:14 <stellar-slack> <sacarlson> it also needs some work on getting better feed back responce from actions like send funds but I'll work on that later

11:15 <stellar-slack> <sacarlson> or let you guys add to it

12:15 <stellar-slack> <lab> i just realized why ASSET_TYPE_CREDIT_ALPHANUM12 was designed in stellar

12:15 <stellar-slack> <lab> then we can issue 'BTCUnlimited'

15:38 <curiosbiter> Hello. How does one get/purchases initial lumines in order to have a stellar account?

15:39 <stellar-slack> <sacarlson> there are many exchanges one being https://www.poloniex.com/

15:40 <curiosbiter> but in order to transfer a lumin don't i need to already have a stellar account?

15:41 <stellar-slack> <sacarlson> the echange will create one for you when you withdraw to the network

15:42 <stellar-slack> <sacarlson> you can also create an account number key set that you might be able to select at withdraw or move the funds after transfer

15:43 <stellar-slack> <sacarlson> so that no one but you could posibly have the secret key

15:43 <curiosbiter> thanks. So, I can create the key pairs using stellar command line and then use that to transfer from the exchange?

15:44 <stellar-slack> <sacarlson> maybe I've never done it but it should be posible at least the move can be done

15:44 <stellar-slack> <sacarlson> you might find beter than the command line to do it

15:45 <stellar-slack> <jed> yeah you can. or you can create a key pair here: https://www.stellar.org/developers/

15:45 <stellar-slack> <jed> the test account keys will also work on the live network

15:45 <stellar-slack> <bartek> or if you don't want to code: https://www.stellar.org/galaxy

15:46 <stellar-slack> <bartek> "GET STARTED" section

15:46 <curiosbiter> I went through the get started and hit a dead wall, where it said that I needed funding.

15:47 <stellar-slack> <bartek> on Galaxy page?

15:48 <curiosbiter> Yes. First, they were talking about a test account. Later, in the docs, they said i would need two steps: generate keys and trunsfer funds.

15:48 <stellar-slack> <bartek> @jed I realized that we have a friendbot at /developers too

15:49 <curiosbiter> BTW, what is the lumen code for that exchange?

15:50 <stellar-slack> <jed> poloniex is still sing STR unfortunately

15:50 <curiosbiter> Oh, and what is the new 3-letter code?

15:50 <stellar-slack> <bartek> XLM

15:51 <curiosbiter> Thanks. So, in other words: First, ceate the keys, somehow. Second, trunsfer to my public key from an exchange.

16:05 <stellar-slack> <jed> yep

16:07 <curiosbiter> Today I was reading a sad post about on of the core bitcoin developers. Maybe it's a chance for people to look at other things, just like stellar.

16:24 <curiosbiter> Anyway, thanks for helping out. bye

16:25 <stellar-slack> <jed> np

22:10 <stellar-slack> <alexmelges> Does the public keys have built-in checksums for mistyping detection?

22:13 <stellar-slack> <scott> @alexmelges: yeah, we do. The last 16-bits of an unencoded public key is an XModem CRC16 or the public key

22:14 <stellar-slack> <scott> (trying to find the github issue with the design right now, one sec)

22:15 <stellar-slack> <alexmelges> @scott: ok, thanks!

22:17 <stellar-slack> <scott> well, I can’t find the issue with the design (I’ll create an issue to add the design to our docs), but there’s a pretty straightfroward implementation here: https://github.com/stellar/go-stellar-base/tree/master/strkey if you can read go

22:17 <stellar-slack> <scott> We call the encoding of public keys the “strkey” format

22:26 <stellar-slack> <irisli> @alexmelges: Here is the PR that links to many of the discussions if you want to see how it happened. There wasn't one single source of the full design but was spread out over different issues and pull requests. https://github.com/stellar/stellar-core/pull/619

22:31 <stellar-slack> <alexmelges> @scott @irisli: Very helpful, thanks!

22:31 <stellar-slack> <scott> happy to help!