<stellar-slack>
<dzham> yeah, but if they’re not official, it doesn’t really make any difference
<stellar-slack>
<sacarlson> but might be good to have http://stellar.org|stellar.org publish that hash as it seems it doesn't match the git algorith hash
<stellar-slack>
<sacarlson> I'll see if I can find what version of hash and base format they use as a standard in the browser check
<stellar-slack>
<dzham> it’s a base64-encoding of the hexdigest
<stellar-slack>
<sacarlson> what format does git use?
<stellar-slack>
<sacarlson> I thought git used sha256
<stellar-slack>
<dzham> but git hashes are truncated, right?
<stellar-slack>
<sacarlson> cool, I also note I can't use http://zipperhead.ddns.net/sha_website.html to do sha384 as it also has Reason: CORS header 'Access-Control-Allow-Origin' missing).
<stellar-slack>
<sacarlson> but no problem since the browser can check it
victortyau has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
TheSeven has quit [Ping timeout: 240 seconds]
TheSeven has joined #stellar-dev
acetakwas has joined #stellar-dev
acetakwas has quit [Ping timeout: 264 seconds]
acetakwas has joined #stellar-dev
uber has quit [Ping timeout: 264 seconds]
loglaunch has quit [Ping timeout: 264 seconds]
dobson has quit [Ping timeout: 264 seconds]
uber has joined #stellar-dev
loglaunch has joined #stellar-dev
dobson has joined #stellar-dev
acetakwas has quit [Ping timeout: 276 seconds]
acetakwas has joined #stellar-dev
acetakwas has quit [Disconnected by services]
ac3takwas has joined #stellar-dev
<stellar-slack>
<powderfan> have there been recent changes in horizon, causing the account_sequence of a transaction to be an int instead of string? I was always using this to update my account sequence after sending a payment and now it complains when I do the next payment.
<stellar-slack>
<bartek> @powderfan: sequence number is uint64 which simply is too big for JS to handle. for the same reason we had to change this in horizon.
<stellar-slack>
<powderfan> thx @raymens! @bartek: do you agree that trx should return it as string as well?
<stellar-slack>
<bartek> @powderfan: yes you're right. we will update this. good catch.
<stellar-slack>
<powderfan> ok, in the meantime I can workaround with a simple `toString()`
<stellar-slack>
<bartek> @powderfan: why don't you update sequence number using /account/{accountId} data?
<stellar-slack>
<steelheaddigital> Question for everyone. I've got the basics down with creating an account, sending payments, etc. One thing I'm trying to figure out is how I would see who is holding credit for a particular account. Say I send a payment to an account in some arbitrary currency. I can see it show up as a positive balance in that account, but I don't see it as a negative balance in the sending account. I'm sure
<stellar-slack>
Thanks for any help.
<stellar-slack>
<raymens> @steelheaddigital: credit isn't listed as a balance on the issuing account
<stellar-slack>
<bartek> @steelheaddigital: j.ed once answered this question with: > the trust lines only have one side now
<stellar-slack>
<dzham> @steelheaddigital: you need to run a node to get to that data
<stellar-slack>
<powderfan> @bartek: I listen to the transactionstream anyway (to get aware of incoming payments). Just avoiding an extra call for the new account sequence.
<stellar-slack>
<bartek> ok, so `toString()` workaround won't work: ``` > var i = 9048748768362497; undefined > i.toString(); '9048748768362496' ```
<stellar-slack>
<bartek> I'm fixing it right now
<stellar-slack>
<raymens> (let the JS hate commence :D)
<stellar-slack>
<steelheaddigital> Thanks @bartek . So, if I'm understanding correctly, there's now way with Horizon right now to see 'sent' credit. @dzham how can I see that data if I'm running my own node? I guess my other option would be to track myself who I've issued credit to?
<stellar-slack>
<dzham> @steelheaddigital: connect to the db and give it a query like this, `select accountid, balance from trustlines where issuer = {ISSUER}`;
<stellar-slack>
<dzham> You could track issuance, but then you’d need to track where those people send it also
<stellar-slack>
<steelheaddigital> Ah, got it, makes sense. Thanks @dzham
<stellar-slack>
<powderfan> @bartek: ah yes, this was the original problem I understand. Thanks a lot!