00:05 <stellar-slack> <jed> zhima2006: https://www.stellar.org/developers/horizon/learn/index.html

00:40 <stellar-slack> <zhima2006> thanks

01:18 <stellar-slack> <sacarlson> zhima2006: I could add a box to my wallet that could add an option to point it at another URL presence of horizon if you want to test it out. would only take about 5 min

01:18 <stellar-slack> <sacarlson> I would need the URL address to check it first

03:55 <stellar-slack> <sacarlson> zhima2006: I created this experimental pointable horizon wallet that I now call http://zipperhead.ddns.net/transaction_tools.html. you can try point it at your new horizon URL and port you are now using for horizon to test it. the js code for it can also be seen here: https://github.com/sacarlson/stellar_utility/blob/master/multi-sign-server/www/js/transaction_tools.js

04:01 <stellar-slack> <zhima2006> Thank you, sacarlson

04:05 <stellar-slack> <zhima2006> I start my stellar-core with stellar-core_testnet.cfg, it shows bunch of log info as:

04:05 <stellar-slack> <zhima2006> 2015-12-15T20:02:40.933 GAM3Y [Ledger INFO ] Got consensus: [seq=1332970, prev=e eba55, tx_count=0, sv: [ txH: 0db26f, ct: 1450238563, upgrades: [ ] ]] 2015-12-15T20:02:40.948 GAM3Y [History INFO ] Catchup mode 'minimal' awaiting ch eckpoint (ETA: 26 seconds)

04:06 <stellar-slack> <zhima2006> I don't know what that means.

04:07 <stellar-slack> <zhima2006> if I want to build my own wallet, do I need only one stellar-core running?

04:08 <stellar-slack> <jed> you don't need to run to stellar-core to build a wallet. You can just build it against horizon for now.

04:12 <stellar-slack> <zhima2006> how one account can send money to other account , which stellar -core will horizon talk to?

04:19 <stellar-slack> <hsxuif> @jed: is it possible to set up a stellar-dev/stellar-user mailing list like ? kinda feel that slack#dev talking is too freely: it is not thread centered; retrieving old topics is somewhat hard.

04:20 <stellar-slack> <hsxuif> i noticed there is a sdf-release, but seems inactive

04:22 <stellar-slack> <hsxuif> may be something like bitcoin-dev (https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev) ?

04:23 <stellar-slack> <jed> hsxuif: Yeah A mailing list would be cool. I personally prefer forums better. But please start one I'll subscribe

04:25 <stellar-slack> <jed> zhima2006: I'm saying you can build your wallet talking to our horizon until you are further along and then you can switch to your own. It will just save you some trouble right now

04:27 <stellar-slack> <hsxuif> @jed: personally i only had experience creating a google group but i remember you mentioned earlier that requires users to have google account?

04:27 <stellar-slack> <jed> yeah it does now unfortunately

04:31 <stellar-slack> <sacarlson> zhima2006: like jed said you don't need your own horizon to create a wallet. my wallet as you might see can point at any horizon including stellars as the default. I just set it up so people could test other horizon installs like you have started.

04:59 <stellar-slack> <hsxuif> a side note: here is the link on hackernews: https://news.ycombinator.com/item?id=10732994 and this one on reddit: https://www.reddit.com/r/CryptoCurrency/comments/3vzep6/jed_mccaleb_proposal_for_a_lightning_network/ @joyce

06:30 <stellar-slack> <hsxuif> @jed: just set up another list on freelists, http://www.freelists.org/list/stellar-dev , the webpage links to http://www.freelists.org/webpage/stellar-dev

06:52 <stellar-slack> <sacarlson> is there any example working code that demonstrates this lighting channel seen here: http://jedmccaleb.com/2015/12/08/lightning-for-stellar/ ? sounds very cool. I read a shorter document of something like it.

06:56 <stellar-slack> <jed> Hsxuif: cool :)

08:10 <stellar-slack> <sacarlson> is there a tool in js-stellar-sdk that can pull the destination address out of a base64 envelope transaction string?

08:20 <stellar-slack> <raymens> there could be more than 1 destination in a transaction. I think you can decode it and pick one of the operations and read the destination from that operation

08:21 <stellar-slack> <sacarlson> I want the javascript code example that does just that

08:21 <stellar-slack> <sacarlson> I already have methods in ruby to do the same

08:21 <stellar-slack> <sacarlson> I'm new to javascript and js-stellar-sdk

10:50 <stellar-slack> <sacarlson> I found a temp solution to the above I'll just send both the destination address and the base64 envelope

10:54 <stellar-slack> <sacarlson> but my next problem is how do I convert a base64 format envelope to the transaction value in this line server.submitTransaction(transaction); I receive a base64 string I need to convert to the transaction value format

11:09 <stellar-slack> <raymens> you can extract stuff like that from the sdk source

11:09 <stellar-slack> <raymens> I'll quickly see if I can find something

11:10 <stellar-slack> <sacarlson> I think i has something to do with fromxdr like in this example console.log( JSON.stringify(StellarSdk.xdr.TransactionEnvelope.fromXDR(txResponse.envelope_xdr, 'base64')) );

11:10 <stellar-slack> <sacarlson> but can't find any example used on a tx

11:11 <stellar-slack> <raymens> https://github.com/stellar/js-stellar-base/blob/master/test/unit/transaction_test.js#L14-L18

11:12 <stellar-slack> <raymens> Oh yeah a Signed Transaction is different

11:12 <stellar-slack> <sacarlson> no that reversed thats going from tx to base64

11:12 <stellar-slack> <raymens> not at line 17 and 18

11:12 <stellar-slack> <raymens> it's reading a base 64 encoding string

11:13 <stellar-slack> <sacarlson> yes but I want to translate to a base64 string the other way

11:14 <stellar-slack> <sacarlson> but that might be the place to be looking in base instead of sdk that I've been searching

11:15 <stellar-slack> <raymens> you want a base64 string -> transaction object right?

11:16 <stellar-slack> <sacarlson> no transaction object -> base64 string

11:18 <stellar-slack> <bartek> ``` new StellarSdk.Transaction(b64).operations[0].destination ```

11:18 <stellar-slack> <bartek> @sacarlson: ^

11:19 <stellar-slack> <bartek> but if there are more than one operation in transaction you need to loop to find the one you're looking for

11:19 <stellar-slack> <dzham> @sacarlson: tx.toEnvelope().toXDR().toString('base64')

11:20 <stellar-slack> <bartek> https://stellar.github.io/js-stellar-sdk/Transaction.html - check the constructor arguments

11:20 <stellar-slack> <bartek> I will try to improve getting operations from b64

11:21 <stellar-slack> <sacarlson> dzham what the method to reverse that then, as normal I think I'm backward again

11:22 <stellar-slack> <sacarlson> cool bartek I think that's for the early question of how to get the account number form b64 envelope and might even be the answer to both

11:23 <stellar-slack> <bartek> yes, it's the answer to: https://stellar-public.slack.com/archives/dev/p1450253414001470 what was the other question?

11:24 <stellar-slack> <sacarlson> the other question is how to convert the base64 envelope string to a tx object in js-sdk

11:27 <stellar-slack> <sacarlson> would it just be object = StellarSdk.Transaction(b64_string) so this might be it then

11:27 <stellar-slack> <bartek> yes, this should work

11:28 <stellar-slack> <sacarlson> thanks you guys

12:12 <stellar-slack> <sacarlson> cool I think I got it

12:12 <stellar-slack> http://zipperhead.ddns.net/transaction_tools.html?json={%22env_b64%22:%22AAAAABgjmdwgqRJl6q0FDO2xDlivEkSFTvjnfkrplpD99NioAAAAZAAJzDsAAACsAAAAAAAAAAEAAAAOc2NvdHR5X2lzX2Nvb2wAAAAAAAEAAAAAAAAAAQAAAADrg150TRtZJM0l/9VQcwNPbfawyTIxoLNEJ+G155X2jgAAAAExAAAAAAAAAC/BUSR1Aa+wZ5rlARYmg8lxC8ZjtP1PIjfQQOUEM9w/AAAAAACYloAAAAAAAAAAAf302KgAAABAHfOFU3wfk4vqvvPhBGJdjqFH4wllgOk7zkB4l5r7WW+tQikknNKcRoKUZmF93BvkpMWimSQL/D7P3YWaCMCDDQ==%2

12:12 <stellar-slack> QZ3NRBZMK6ESEQVHPRZ36JLUZNEH56TMKQXEB%22}

12:13 <stellar-slack> <sacarlson> now you can send a transaction to a wallet that can submit it and see it's balance so you can send this in an email with the seed value if you want to send funds via email

12:18 <stellar-slack> <sacarlson> so now I need to make the tool that creates the transaction to be sent in the email. it will have to creates transaction that will create a new random account from your funds and generates the email

16:04 <stellar-slack> <jed> btw hsxuif set up this mailing list for stellar devs: http://www.freelists.org/list/stellar-dev

16:07 <stellar-slack> <raymens> great, I've subscribed myself

16:40 <stellar-slack> <hsxuif> actually i'm not quite familiar with freelist admin, anybody mind being an admin/moderator?:) (guess currently there won't be many affairs to be dealt with, though)

20:38 <stellar-slack> <ant> also someone could archive the slack channel to html https://levels.io/slack-export-to-html/