03:03 <stellar-slack1> <sacarlson> today I was thinking of writing a simple transaction signing tool, it should allow you to post a link in email or any other location like here, with an unsigned base64 envelope transaction that will take you to the wallet page fully filled in for you to hit the button to sign it.

03:23 <stellar-slack1> <dzham> I have a 90% finished version of that I got really stumped by the discussions of trust that we had in #inflation. Users *would* have to use their private keys, and the use case is quite a lot more complicated than the inflation pool

03:24 <stellar-slack1> <dzham> @sacarlson: anyways, nice to see you putting some effort into web interfaces.

03:36 <stellar-slack1> <sacarlson> I assume this stumped inflation thing has nothing to do with signing the distribution transaction?

03:38 <stellar-slack1> <dzham> With users using their private keys in the web interface. It’s not like they can sign it somewhere else, like with the pool.

03:39 <stellar-slack1> <sacarlson> are the users in this case the 3 signers of the pool?

03:39 <stellar-slack1> <dzham> Could be. I did the multi-sig signing UI before we started the pool

03:39 <stellar-slack1> <sacarlson> ok lets take a look at it

03:41 <stellar-slack1> <dzham> w/ discussions of trust, I specifically mean getting end-users to trust the application enough to use their private key

03:42 <stellar-slack1> <dzham> It’s on my lappy

03:43 <stellar-slack1> <sacarlson> oh ok user meaning members of the pool. yes we just have to teach people to trust or create tools that make people not have to trust the web interface with some backed signing verification

03:44 <stellar-slack1> <dzham> The only reasonable way to go forward, is to post the source code of the app. Having SDF host stellar-sdk.min.js would help a lot, since that’s one thing less they have to audit

03:45 <stellar-slack1> <sacarlson> I already did that by posting the app on github, that's the best I can think of at this time other than have people host it them self

03:48 <stellar-slack1> <sacarlson> but I agree having stellar host the stellar-sdk.min.js and stellar-sdk.js on one of there https:// servers would be a benifit

03:59 <stellar-slack1> <sacarlson> and we should write an automated website auditing tools that runs in javascript that would run a 3rd party of http://github.io|github.io site that would sign off on sha1 values of all the files on a wallet page

09:34 <stellar-slack> <sacarlson> added sign_tx and mail_tx button to http://sacarlson.github.io/transaction_toolsv0.4.0.html that allows sending a pre-signed transaction link and picking up a web page link from email or other point to sign it http://sacarlson.github.io/transaction_toolsv0.4.0.html

09:57 <stellar-slack> <sacarlson> https://sacarlson.github.io/transaction_toolsv0.4.0.html?json={%22env_b64%22:%22AAAAACpO9HMl0pby2JNneru53Wr8PU6ADHCYDVpeELlHwQRgAAAAZAAeqEMAAAAHAAAAAAAAAAEAAAAAAAAAAQAAAAAAAAABAAAAAIDUbONb3NsbZiIB5obQteHXxNIvkZ+Ys4OBQZDqLs/lAAAAAAAAAAAAu67gAAAAAAAAAAFHwQRgAAAAQATV5DWVAE8ODxbathOHm/0UU9ymPjAh6p5RMKo2Uwg9uQS8ldTgvIyJcY5MNrd4uCBKZYpjUIwrAueCTquo7gg=%22}

10:04 <stellar-slack> <scott> @raymens: Sorry about the delay on pushing my work on the “importer in go” project… I’ve been averaging about 1 presentation every other day over here so I haven’t had much time to work on it. That said, I’ve got the skeleton of the importer up here: https://github.com/stellar/horizon/pull/242 and hope to make some solid progress in the next couple of days

10:06 <stellar-slack> <raymens> @scott Thanks for the headsup! I know you're quite busy right now :)

10:45 <stellar-slack> <dzham> @sacarlson: now add some ui to that :) I know you’re trying out w3.css, but if you’re willing to give bootstrap a go, there’s a ui editor you could use, that looks really impressive — http://bootstrapstudio.io|bootstrapstudio.io

10:48 <stellar-slack> <dzham> @scott: sounds like an awesome time :)

10:53 <stellar-slack> <sacarlson> @dzham I'm more into functionality than looks. I'm now working on the auto website validator. I do plan later to add w3.css or other to my apps at some point if no one else does it for me

10:54 <stellar-slack> <dzham> I know you are… Have you considered teaming up with someone to do UI? You have lots of code, that could be unbundled, and made into their own polished products

10:55 <stellar-slack> <sacarlson> I have when someone was getting paid for it, but not found any one to do it for free here

10:55 <stellar-slack> <sacarlson> any help or PR are always welcome

11:14 <stellar-slack> <scott> @dzham: yeah, its been great so far. I’ve met a ton of cool devs, and the people of Lagos have been awesome hosts.

13:14 <stellar-slack> <sacarlson> I made the first step my website audit javascript that can now do an sha1 on any file in a website. so next step is to write some code that pulls all the <script src files > out of the target page and do a hash on each

15:05 <stellar-slack> <fredolafritte> How stellar handles confidentially and privacy ?

15:07 <stellar-slack> <fredolafritte> to receive funds, one must give its public address, therefore, the payer would be able to see the receiver's funds

16:18 <stellar-slack> <john> @fredolafritte: Like a traditional ledger, the Stellar ledger records a list of all the balances and transactions belonging to every single account on the network. A complete copy of the global Stellar ledger is hosted on each server that runs the Stellar software. Account's balances can be checked via https://www.stellar.org/laboratory/ or https://stellar.github.io/network-explorer/

16:39 <stellar-slack> <fredolafritte> thanks but that doesn't reply the question

16:58 <stellar-slack> <john> @fredolafritte: no prob. Could you please expand your question?

17:02 <stellar-slack> <fredolafritte> Given a public key/account id, it's possible to retrieve the account balance for all assets and all transactions from and to this account. How to prevent other people to see your financial activity ?

17:15 <stellar-slack> <john> OK I got you. The very purpose of a decentralised ledger is to make it public, thus accessible to anyone. Can we prevent a particular account to be visible? I doubt it's possible since all existing accounts in Stellar are public. Did you browse the Dev section? https://www.stellar.org/developers/learn/integration-guides/building-blocks/account-management.html Let me know if I've answered your question :-)

17:18 <stellar-slack> <eno> maybe you can create a stellar address , and destroy it after payment.

17:29 <stellar-slack> <fredolafritte> @evo with little analysis of the ledger and their transactions, it will be relatively easy to guess the real destination

17:39 <stellar-slack> <jed> @fredolafritte: if you are behind a gateway it can be kept private. We have other ideas for private transactions but it is still a few months away.

17:47 <stellar-slack> <fredolafritte> could you share your ideas about private transactions ?

17:47 <stellar-slack> <fredolafritte> I stumble across zcash which is using zero knowledge proof to achieve privacy

17:48 <stellar-slack> <fredolafritte> and was wondering how it could be integrated into stellar

18:03 <stellar-slack> <jed> yeah I'm supposed to have a call with zooko to talk about that actually

18:24 <stellar-slack> <otto_mora> hey there folks

18:25 <stellar-slack> <otto_mora> is there an example of setting up an issuing account with the Stellar JS SDK? I'm looking for something beyond just creating the asset object, and actually assigning that to the account

18:26 <stellar-slack> <bartek> every account can issue asset, you only need the other account to trust that issuing account.

18:28 <stellar-slack> <otto_mora> right but then, what is the operation to have the issuing account be the holder of the asset? how I do commit it to the network, I see I can do new StellarSdk.Asset('USD', 'acct###")

18:29 <stellar-slack> <otto_mora> but then how I actually submit that?

18:30 <stellar-slack> <bartek> G: gateway U: user 1. U sends change_trust operation to trust G's USD 2. G can send USD issued by G in a payment operation

18:31 <stellar-slack> <otto_mora> ooh ok so in setting up the trustline, I am implicitly creating the asset I see

18:31 <stellar-slack> <bartek> 1. source is U ``` StellarSdk.Operation.changeTrust({ asset: new StellarSdk.Asset("USD", G.accountId()) }) ``` 2. source is G ``` StellarSdk.Operation.payment({ amount: "100", asset: new StellarSdk.Asset("USD", G.accountId()), destination: U.accountId() }) ```

18:32 <stellar-slack> <otto_mora> thanks Bartek, I will look into the examples of setting up the trustline

21:53 <stellar-slack> <heunland> Hi could someone please tell me why my TX from my wallet to Poloniex failed?

21:58 <stellar-slack> <heunland> I already checked at https://www.stellar.org/developers/learn/concepts/list-of-operations.html and cannot find anything about tx_bad_seq

21:58 <heunland> Hi anyone here know what this TX error code means?

22:12 <stellar-slack> <jed> where are you sending it from?

22:13 <stellar-slack> <jed> it is saying you are using a bad seq number

22:13 <stellar-slack> <heunland> not sure what a seq number is. I am sending from https://www.stellar.org/account-viewer

22:14 <stellar-slack> <heunland> I just filled in the form with the send to address and memo_id and amount

22:14 <stellar-slack> <jed> hmm strange. Can you refresh the account-viewer and try again

22:14 <stellar-slack> <heunland> you mean log out and in again?

22:15 <stellar-slack> <jed> or just refresh the page

22:15 <stellar-slack> <jed> it will make you enter your secret again

22:15 <stellar-slack> <bartek> @heunland: I think it's a bug we fixed recently in js sdk, I will update account viewer now. one sec.

22:16 <stellar-slack> <heunland> ok I already tried again several times and always same result. Maybe after update from @bartek it will work

22:17 <stellar-slack> <heunland> I had first tried to send an amount that apparently was too high, then I tried again with the amount they suggested but got this error

22:18 <stellar-slack> <heunland> for some reason the TX which should have not gone through is listed in my TX history with operation ID 9299111001985025

22:18 <stellar-slack> <heunland> I mean the first TX with the too high amount

22:22 <stellar-slack> <heunland> Just tried again and I guess it´s not fixed yet :$

22:23 <stellar-slack> <bartek> I will let you know. I think it shouldn't take more than 10 minutes

22:25 <stellar-slack> <heunland> ok thanks!

22:47 <stellar-slack> <bartek> @heunland: it should work now.

22:47 <stellar-slack> <heunland> ok let me try!

22:47 <stellar-slack> <bartek> (you need to reload it of course)

22:47 <stellar-slack> <heunland> yes I am doing that

22:51 <stellar-slack> <heunland> ok it appears like it worked. Thanks for the help! Do you know how long it wil take to show up in the other address?

22:51 <stellar-slack> <bartek> around 5 seconds :)

22:51 <stellar-slack> <heunland> Is there some stellar block explorer where I can check the TX?

22:51 <stellar-slack> <bartek> we have simple one here: https://www.stellar.org/laboratory/

22:55 <stellar-slack> <bartek> the default network is testnet. switch it in the header.

22:55 <stellar-slack> <jed> need to switch to public network

22:56 <stellar-slack> <heunland> not sure where I can switch that

22:56 <stellar-slack> <jed> top right

22:56 <stellar-slack> <heunland> I just put in the operation ID

22:57 <stellar-slack> <heunland> ah now I see it :smile_cat:

22:57 <stellar-slack> <jed> although it is probably in polo by now :)

22:58 <stellar-slack> <heunland> yeah but those polo guys are pretty slow in moving any coins to their common wallet and then some more time before it actually shows up in my balance

22:59 <stellar-slack> <heunland> oh today must be my lucky day, the balance is already there on Polo :thumbsup:

23:00 <stellar-slack> <heunland> So there is not a regular block explorer where you can just monitor all the transactions on the network as they happen?

23:01 <stellar-slack> <jed> no one has made one yet. It would be awesome if someone would though

23:01 <stellar-slack> <heunland> yes I´d say. Maybe you need to offer them some bounty

23:03 <stellar-slack> <heunland> thanks guys for the help! Really appreciate it.