<stellar-slack>
<eva> Would anyone here be interested in testing out/ giving feedback on my new tutorial (not yet published)? The tutorial is on how to create your own asset on the (test) network (ex: EvaBucks). I’m intending the tutorial to be at a very basic level, so someone who’s never used *any* API before could do it. I’d love to get some input/review on it, especially (but not necessarily) from people who are new to the
<stellar-slack>
though! Just let me know if you’re interested and I’ll send you a link to the google doc.
<stellar-slack>
<john> Can I merge two accounts with the Laboratory?
<stellar-slack>
<irisli> Yes you can. Just make a transaction with an operation Account Merge
<stellar-slack>
<john> Thank you @irisli can I merge a native account to an account that need a memo? I noticed that I can add a MEMO in the transaction builder
<stellar-slack>
<sacarlson> my wallet also supports memo in text and number mode
de_henne_ has joined #stellar-dev
de_henne has quit [Ping timeout: 248 seconds]
<stellar-slack>
<irisli> @john memos are optional and are per transaction. You dont need it to merge. Memos are useful only if you want to let someone else know about the transaction
<stellar-slack>
<garth> Hi @eva I am definitely interested in trying your tutorial.
TheSeven has quit [Ping timeout: 260 seconds]
TheSeven has joined #stellar-dev
<stellar-slack>
<brian.ebert> @eva: same.
koshii has quit [Ping timeout: 272 seconds]
koshii has joined #stellar-dev
koshii has quit [Ping timeout: 264 seconds]
koshii has joined #stellar-dev
koshii has quit [Ping timeout: 276 seconds]
koshii has joined #stellar-dev
de_henne_ has quit [Remote host closed the connection]
<stellar-slack>
<armed10> on submit i get these result_codes: { transaction: 'tx_bad_auth' },
<stellar-slack>
<bartek> http://localhost:8000 is horizon from docker-stellar-core-horizon?
<stellar-slack>
<armed10> Is this because the source account is the root account ?
<stellar-slack>
<armed10> installed local without docker
<stellar-slack>
<bartek> have you changed network-passphrase in stellar-core?
<stellar-slack>
<armed10> yes
<stellar-slack>
<bartek> so you need to add this code in the top of your code: ``` StellarSdk.Network.use(new StellarSdk.Network("your passphrase")); ```
<stellar-slack>
<bartek> StellarSdk default is testnet with the following passphrase: `Test SDF Network ; September 2015 ` signature contains network passphrase so that's why you're getting bad auth error.
<stellar-slack>
<armed10> Thanks the error is gone. It's getting through now.
<stellar-slack>
<bartek> :thumbsup:
<stellar-slack>
<armed10> Any common cause for the socket to hang up (connection reset) after a request?
<stellar-slack>
<armed10> { [Error: socket hang up] code: 'ECONNRESET' }
<stellar-slack>
<bartek> check horizon log for errors
<stellar-slack>
<bartek> btw. what endpoint gives you this error?
<stellar-slack>
<armed10> Can't find where horizon logs to..
<stellar-slack>
<bartek> to console
<stellar-slack>
<armed10> there's no error in the console
<stellar-slack>
<armed10> it just says request finished
<stellar-slack>
<bartek> can you publish the full log somewhere? gist maybe?
<stellar-slack>
<armed10> The host rebooting, give me a minute
<stellar-slack>
<armed10> I'll reproduce the results
<stellar-slack>
<bartek> and both request were reset?
<stellar-slack>
<armed10> yes
<stellar-slack>
<armed10> It does say 504, but I can't imagine the local network here being that slow
<stellar-slack>
<bartek> have any of your transactions succeeded?
<stellar-slack>
<bartek> sent to this horizon instance
<stellar-slack>
<armed10> no we've just succeeded in setting up stellar-core with horizon/importer and a few nodes
<stellar-slack>
<armed10> also, installed the SDK, wich sends the requests
<stellar-slack>
<bartek> I think horizon has problem communicating with stellar-core. can you try to submit your transaction to stellar-core directly to find out where's the problem?
<stellar-slack>
<armed10> I'll try, give me a minute to figure out what the transaction looks like in stellar
<stellar-slack>
<bartek> when your transaction is build run this code to get it's b64 blob: `transaction.toEnvelope().toXDR().toString("base64"))`
<stellar-slack>
<armed10> Do I need to html encode the base64 string?
<stellar-slack>
<armed10> probably with all the + symbols in it
<stellar-slack>
<bartek> yes
<stellar-slack>
<bartek> you can use JS `encodeURIComponent` function
<stellar-slack>
<armed10> I'm going to try again with a new key (stellar is giving me a duplicate response)
<stellar-slack>
<bartek> what do you mean by duplicate response?
<stellar-slack>
<armed10> just the response has a status duplicate
<stellar-slack>
<bartek> can you copy it here?
<stellar-slack>
<armed10> it overwrote the response but it went like this: {status: "DUPLICATE" }
<stellar-slack>
<bartek> > tx /tx?blob=Base64 > submit a transaction to the network. blob is a base64 encoded XDR serialized 'TransactionEnvelope' returns a JSON object with the following properties status: > > "PENDING" - transaction is being considered by consensus > "DUPLICATE" - transaction is already PENDING > "ERROR" - transaction rejected by transaction engine error: set when status is "ERROR". Base64 encoded, XDR serialized '
<stellar-slack>
<bartek> in your code: ``` var an_account = new StellarSdk.Account("GBPUMAN7QSPGBDNQQFIG7W224FS3RQPPE355EHKB7E2QNVXI2SCCJLLZ", "0"); ``` I understand 0 is the current sequence number but you need to increment it by one everytime. so it should be 1
<stellar-slack>
<sacarlson> have you already tested a system with horizon and your test trans with at least a standalone system?
<stellar-slack>
<armed10> I have not
<stellar-slack>
<armed10> well I did read the configuration part.
ac3takwas has joined #stellar-dev
<stellar-slack>
<armed10> We've tried setting up nodes that connected before trying to do transaction on it
<stellar-slack>
<armed10> We'll take a step back and try a standalone first
<stellar-slack>
<sacarlson> otherwise the experts on stellar-core should be able to help with that part. sounds like some kind of config problem
<stellar-slack>
<armed10> If anything it will narrow down the issue. Thanks guys!
<stellar-slack>
<jed> Armed10: lmk if you want me to help you get the 4 nodes synced.
<stellar-slack>
<armed10> I will, thanks @jed
takwas has joined #stellar-dev
ac3takwas has quit [Ping timeout: 260 seconds]
takwas has quit [Ping timeout: 240 seconds]
acetakwas has joined #stellar-dev
acetakwas has quit [Read error: Connection reset by peer]
acetakwas has joined #stellar-dev
acetakwas has quit [Max SendQ exceeded]
acetakwas has joined #stellar-dev
acetakwas has quit [Ping timeout: 264 seconds]
acetakwas has joined #stellar-dev
acetakwas has quit [Ping timeout: 272 seconds]
<stellar-slack>
<john> @jed still struggling trying to merge 2 accounts... Could you please help me out?
<stellar-slack>
<jed> what is the error?
<stellar-slack>
<john> in the laboratory, I build the transaction with the Source Account, Transaction Sequence Number, Operation Type & Destination. I than Add Signer in the transaction signer but what should I do than??? Sorry I'm a real novice...
<stellar-slack>
<john> of course... the missing step... Let me give a try. One more question: since I'm merging an old Stellar account to an address that belongs to an exange and that MEMO are compulsory, can I add it somewhere?
<stellar-slack>
<john> BTW thanks for your precious time
<stellar-slack>
<john> really appreciate it
<stellar-slack>
<jed> hmm I wouldn't do that. Not sure if the exchange supports it
<stellar-slack>
<jed> but yes you can add a memo when you make the tx
loglaunc- has joined #stellar-dev
loglaunch has quit [*.net *.split]
ggherdov` has quit [*.net *.split]
pigeons has quit [*.net *.split]
<stellar-slack>
<john> OK I give a try, it's only 20XLM.... Re-building the transaction.... Talk to you soon
<stellar-slack>
<john> Hmmm no it doesn't work.... "tx_no_source_account"