koolhead17 has joined #stellar-dev
koolhead17 has quit [Remote host closed the connection]
<stellar-slack1> <jed> Basic transaction building and signing added to: https://www.stellar.org/laboratory/
<stellar-slack1> <sacarlson> @jed I just tried the transaction building and signing. I might have missed something. after I signed it I fail to see a way to submit the final created signed transaction. Is there another tool for that?
<stellar-slack1> <sacarlson> other than that it looks good
<stellar-slack1> <jed> you have to do submission via horizon or stellar-core
<stellar-slack1> <sacarlson> your tool could also have the option with a button to submit it on that page. that way we can verify that the tx it makes works
<stellar-slack1> <jed> yeah that is coming
<stellar-slack1> <sacarlson> oh and I guess I will have to try it again as it asks for the sequence number. I wonder if it will fill that in for you if it is left blank? if not maybe another button to have get the present sequence for the account.
<stellar-slack1> <sacarlson> I got some interesting results when I did submit the tx created in you new lab builder: "exception"=>"insufficient buffer space in xdr_generic_get". I expected a bad sequence return but this is different
de_henne_ has joined #stellar-dev
de_henne has quit [Ping timeout: 260 seconds]
koolhead17 has joined #stellar-dev
koolhead17 has quit [Remote host closed the connection]
<stellar-slack1> <irisli> @sacarlson: I'm thinking in the future, it can fill in the sequence number for you. Also, in the signing page, I'm want to add a feature where it verifies if you have enough signer weight for the transaction
<stellar-slack1> <irisli> and by fill in the sequence number, I mean having a button that fetches it
<stellar-slack1> <sacarlson> sounds good
<stellar-slack1> <irisli> also, how did you get the error?
<stellar-slack1> <irisli> is this a Horizon error?
<stellar-slack1> <sacarlson> I pasted that string above into my app that accepts XRP transactions
<stellar-slack1> <irisli> XDR transactions?
<stellar-slack1> <sacarlson> yes sorry xdr
<stellar-slack1> <irisli> That is interesting. The way I am calling js-stellar-sdk to build the transaction is fairly straight forward. I'm thinking this might be a js-stellar-sdk issue then?
<stellar-slack1> <irisli> I also can't import it into the laboratory either in the signer
<stellar-slack1> <sacarlson> I'm not sure as I sent the transaction to my mss-server to get better understanable results so maybe the problem is on my side also
<stellar-slack1> <irisli> hm yea, when I paste it into the laboratory with error messages enabled, I get the same message
<stellar-slack1> <sacarlson> but I have tested this app with sending XDR tx before as I just tested the method with the mailer
<stellar-slack1> <irisli> seems like the common denominator here is js-stellar-base?
<stellar-slack1> <irisli> how did you build the transaction
<stellar-slack1> <sacarlson> I used your site to build it. do you mean what values did I enter?
<stellar-slack1> <sacarlson> I think I created a payment to myself for one native
<stellar-slack1> <sacarlson> oh and maybe the sequence box was empty I'm not sure
<stellar-slack1> <sacarlson> I think there is a tool that takes the tx apart and shows it's values but I forget the link for it
<stellar-slack1> <irisli> the xdr viewer says it's invalid too: https://stellar.github.io/xdr-viewer/
<stellar-slack1> <sacarlson> ya that's it
<stellar-slack1> <irisli> it's also not possible to make a transaction with empty sequence number
<stellar-slack1> <sacarlson> Oh, snap! Input is invalid.
<stellar-slack1> <irisli> yea i'm not sure
<stellar-slack1> <irisli> i gotta go now, but let me know if you can figure out how to reproduce this
<stellar-slack1> <irisli> and maybe open an issue in laboratory. I am curious too
<stellar-slack1> <sacarlson> can you show me an XDR that you have already created on you new tools that does work?
<stellar-slack1> <sacarlson> ok
<stellar-slack1> <sacarlson> my guess is that I didn't capture the whole string from the box
<stellar-slack1> <irisli> oh maybe that might be the reason
<stellar-slack1> <irisli> also, I found a bug. it makes the sequence number one bigger than entered
<stellar-slack1> <irisli> ``` AAAAAO5JPEpVFTLbkiz6qauySEzp2G2JeiBO/mvREUEq9uM4AAAAZAAAAAAAAAB8AAAAAAAAAAAAAAABAAAAAAAAAAAAAAAA9VdRIF45bfRJMhJCx/lBuGIC4SiWR9Q1gx5HHSnJIhcAAAABD8wUAAAAAAAAAAAA ```
<stellar-slack1> <irisli> try entering this into the transaction signer
<stellar-slack1> <irisli> I have fixed the sequence off-by-one error and it will be deployed in about 10 minutes
<stellar-slack1> <sacarlson> ya that works in the viewer but that's before it's signed
<stellar-slack1> <irisli> maybe you're not copying the whole thing? I was about to sign that transaction twice
<stellar-slack1> <sacarlson> I now note when I look at the two strings that I captured one to paist into the signer that the output after sign was shorter than before so it couldn't be the whole string
<stellar-slack1> <sacarlson> I think it's working
<stellar-slack1> <irisli> ok thanks for your feedback. I've added a feature where it will select all the XDR upon clicking
<stellar-slack1> <sacarlson> ah good idea
<stellar-slack1> <irisli> yea it's already implemented in the Endpoint Explorer but it's a good thing to have here where it doesn't make sense to select part of the XDR code
<stellar-slack1> <irisli> ok I'll deploy that in a bit after the build is done
<stellar-slack1> <irisli> both fixes are now live. you might have to do a hard refresh to see them though
<stellar-slack1> <irisli> and i gotta go now, so i'll talk to you later
koolhead17 has joined #stellar-dev
TheSeven has quit [Ping timeout: 240 seconds]
TheSeven has joined #stellar-dev
pixelbeat_ has quit [Ping timeout: 246 seconds]
koolhead17 has quit []
pixelbeat_ has joined #stellar-dev
stellar-slack1 has quit [Remote host closed the connection]
stellar-slack has joined #stellar-dev
Kwelstr has quit [Quit: ugh]
Kwelstr has joined #stellar-dev
pixelbeat_ has quit [Ping timeout: 246 seconds]
pixelbeat_ has joined #stellar-dev
pixelbeat_ has quit [Ping timeout: 255 seconds]
pixelbeat_ has joined #stellar-dev
pixelbeat_ has quit [Ping timeout: 240 seconds]
pixelbeat_ has joined #stellar-dev
pixelbeat_ has quit [Ping timeout: 246 seconds]
pixelbeat_ has joined #stellar-dev
pixelbeat_ has quit [Ping timeout: 272 seconds]
pixelbeat_ has joined #stellar-dev
pixelbeat_ has quit [Ping timeout: 272 seconds]
<stellar-slack> <ant> where to get offer_ids to cancel open offers? it looks like I can only find it in the database from the offer table as offerid
<stellar-slack> <jed> ant the offer id should be in the result of the create offer transaction
<stellar-slack> <jed> https://www.stellar.org/developers/horizon/reference/offers-for-account.html that will also return the order id