stellar-slack1 has quit [Remote host closed the connection]
stellar-slack has joined #stellar-dev
pixelbeat has quit [Ping timeout: 250 seconds]
<stellar-slack>
<brian.ebert> Is there a js sdk binary function that returns whether an account address is formatted validly? I'd like to check that before submitting it to the network.
<stellar-slack>
<bartek> `/transactions` contain only transactions submitted by a certain account and `/payments` contain all operations that affected certain account. so it also includes `create_account` operation.
<stellar-slack>
<bartek> wait, maybe I'm wrong.
<stellar-slack>
<richiela> Oh .. It's submitted by an account? Not to/from and acct?
<stellar-slack>
<richiela> The missing tx is the most recent payment... Not anything special
<stellar-slack>
<richiela> I didn't see this behavior on test net ;(
<stellar-slack>
<bartek> looks like a bug. can you create an issue in horizon?
<stellar-slack>
<richiela> Sure... Any idea why this doesn't manifest on testnet?
<stellar-slack>
<bartek> not sure if testnet is running the same version of horizon as public network. maybe that bug has been already fixed in testnet but not deployed to http://horizon.stellar.org|horizon.stellar.org.
<stellar-slack>
<richiela> ahh... i tested with 2 accts on testnet meh..
<stellar-slack>
<richiela> have to make this scenario work so inter exchange xfers work properly either way ... heh.. it showed up now
<stellar-slack>
<eno> @scott I would like to trace a account's transaction and store in database. There are ledger, hash, paging_token in the response. Can I use the paging_token as the primary key to identify a transaction?
<stellar-slack>
<ripplefox> I cannot find the definition of the "paging_token", is it can be used to identify a transaction and strictly increased by the time?
<stellar-slack>
<sacarlson> as An opaque cursor, which may be used for paging through the collection (i.e. used as the cursor parameter)
<stellar-slack>
<sacarlson> but tell you the truth I still don't know what it really is
<stellar-slack>
<ripplefox> hmm. it can use for paging... so it should increased by time. still want to know whether it is unique for each transaction/payment.
<stellar-slack>
<sacarlson> the txid is the unique number that marks each transaction. I guess in the horizon it's labled as "id"
<stellar-slack>
<ripplefox> agree. but txid is a hash. it is better to use page_token to store in database as to token is sortable
<stellar-slack>
<sacarlson> I don't see any source for pageing_token inside the stellar-core database so it must be something derived in horizon from ??
<stellar-slack>
<sacarlson> it seems to define the cursor position of the search in the links generated example href": "/accounts/GB6YPGW5JFMMP2QB2USQ33EUWTXVL4ZT5ITUNCY3YKVWOJPP57CANOF3/transactions?order=asc\u0026limit=10\u0026cursor=2398717759983616"
<stellar-slack>
<ripplefox> i need to find all tx after the latest one stored in db. can page_token be used to do this? for example, the last token is 1000. when i query the transactions, i just stop when i meet the token.
<stellar-slack>
<jed> yes that is what it is for
de_henne_ has quit [Remote host closed the connection]
de_henne has joined #stellar-dev
<stellar-slack>
<ripplefox> just like ripple have ledger index and tx index to sort.
<stellar-slack>
<ripplefox> ok, thanks
zz_akuukis is now known as akuukis
pixelbeat has joined #stellar-dev
akuukis is now known as zz_akuukis
de_henne has quit [Ping timeout: 260 seconds]
de_henne has joined #stellar-dev
de_henne has quit [Remote host closed the connection]
zz_akuukis is now known as akuukis
de_henne has joined #stellar-dev
<stellar-slack>
<sacarlson> ripplefox I think you might be looking for the ledgerseq that is found in the stellar-core database and seems to be refered to as "ledger" in when looked at with horizon searches. it in a way marks the time of the transaction. in the orders table that number is used to mark lastmodified.
bit2017 has joined #stellar-dev
nivah has quit [Ping timeout: 272 seconds]
bit2017 has quit [Ping timeout: 272 seconds]
<stellar-slack>
<scott> @eno: it’s safe to use the paging token to identify a transaction. The only case where it’s uniqueness isn’t guaranteed is between networks (i.e. a transaction on testnet could share a paging token with a transaction the live network)
akuukis is now known as zz_akuukis
zz_akuukis is now known as akuukis
<stellar-slack>
<raymens> Trying to extend xdrgen with a C# output, sucks that the C# enums are so limited :(
<stellar-slack>
<jed> are you making a c# stellar-base? that would be great
<stellar-slack>
<raymens> Yeah sortof, at least a start of it :)
<stellar-slack>
<raymens> Thought I could use the Java output as a base, but Java enums are completely different.
<stellar-slack>
<jed> can't you use the c++ output as a base?
<stellar-slack>
<scott> xdrgen doesn’t output c++
<stellar-slack>
<raymens> I've just started, I'll continue next week and will put it on GH
<stellar-slack>
<scott> @raymens: If you need any support on writing for xdrgen, I’m happy to help. Personally, I think the go generator is the cleanest of the generators. I haven’t looked at the java one much
<stellar-slack>
<raymens> Thanks scott, I'll keep that in mind
edubai__ has joined #stellar-dev
<stellar-slack>
<richiela> What exactly is the "later" milestone ;)
<stellar-slack>
<scott> “we want to do this, but it has no schedule on when it will be done"
<stellar-slack>
<richiela> Meh..
<stellar-slack>
<richiela> Ok so I have to rework our deposit flow to deal with sending to self address :(
<stellar-slack>
<scott> Remember, it’s not like our priorities are set in stone. They’re best guesses at how we can be most effective with our development resources. Feel free to make an argument for getting something available sooner.
<stellar-slack>
<jed> Why is sending to self messing you up?
<stellar-slack>
<richiela> Honestly if you guys can just get memo in payments this would be much simpler ;)
<stellar-slack>
<richiela> @jed: inter exchange withdrawals
<stellar-slack>
<richiela> We would never see those and lose them if user a send to user b
<stellar-slack>
<sacarlson> they have memo in payments as far as I know
<stellar-slack>
<jed> Sorry I don't understand. why does the self sending effect your deposit flow?
<stellar-slack>
<richiela> @sacarlson: it's missing in payments or transactions ... Forgot which one ... But one has amount no memo, the other has memo no amount
<stellar-slack>
<richiela> @jed: if I have 2 users... They both just have memo tags... One user wants to send to another user of the exchange
<stellar-slack>
<jed> ah ok
<stellar-slack>
<richiela> It's basically sending to myself with different memos
<stellar-slack>
<jed> I see and the tx isn't found
<stellar-slack>
<richiela> Yup so I can credit the receiving user
<stellar-slack>
<richiela> Err can't
<stellar-slack>
<sacarlson> richiela: I can only see that event if for reasons your customers were sending more than one operation in a single transaction. but the norm is to send only one
<stellar-slack>
<sacarlson> I personaly in all my expermentation in stellar have only 2 times sent 2 operations in one transaction
<stellar-slack>
<sacarlson> just to see that it could be done
<stellar-slack>
<richiela> Not sure u understand
<stellar-slack>
<richiela> Err I understand
<stellar-slack>
<richiela> What's nun of operations have to do with anything?
<stellar-slack>
<sacarlson> want I send you a transaction with a memo in it?
<stellar-slack>
<richiela> It works fine if you send it... But the problem is when I send to myself
<stellar-slack>
<richiela> Remember the exchange only has one address
<stellar-slack>
<richiela> It's all delineated by memos
<stellar-slack>
<sacarlson> that I'm sure I have never tried to send myself funds. I'll have to try that to verify that the memo fails to get through as it's still a full transaction.
<stellar-slack>
<scott> @richiela: having the transaction not show up when self-sending is a bug that bartek just discovered yesterday. It’ll get fixed over the weekend
<stellar-slack>
<richiela> Erm .. Two sep issues... Self sends don't show up in transactions