12:13 <stellar-slack1> <veerasarma> Hi

12:13 <stellar-slack1> <veerasarma> I have an doubt

12:14 <stellar-slack1> <veerasarma> how we can add the memo details on the transaction process

12:14 <stellar-slack1> <veerasarma> can you provide any example

12:14 <stellar-slack1> <sacarlson> yes

12:16 <stellar-slack1> <sacarlson> var transaction = new StellarSdk.TransactionBuilder(account,{fee:100, memo: StellarSdk.Memo.text(memo.value)})

12:17 <stellar-slack1> <sacarlson> https://github.com/sacarlson/stellar_utility/blob/master/multi-sign-server/www/js/stellar_min_client.js

12:17 <stellar-slack1> <sacarlson> http://zipperhead.ddns.net/stellar_min_client.html

12:18 <stellar-slack1> <veerasarma> ok thanks i will use and try

12:26 <stellar-slack1> <veerasarma> Unhandled rejection Error: Expects a int64 as a string. Got 820196 at Function.exports.Memo._createClass.id.value (/var/www/node_modules/stellar-base/lib/memo.js:91:29)

12:26 <stellar-slack1> <veerasarma> i got the above error when run this

12:26 <stellar-slack1> <veerasarma> var transaction = new StellarSdk.TransactionBuilder(account,{fee:100, memo: StellarSdk.Memo.id(820196)})

12:26 <stellar-slack1> <veerasarma> it is correct or need to change anything

12:27 <stellar-slack1> <sacarlson> I've only ever used text so I'm not sure. you can still put numbers in text

12:27 <stellar-slack1> <dzham> Maybe you need to make 820196 into a string, like the error message says? :)

12:28 <stellar-slack1> <veerasarma> oh ok i'll try

12:29 <stellar-slack1> <veerasarma> thanks its working when change it to string

12:29 <stellar-slack1> <veerasarma> :grinning:

13:01 <stellar-slack1> <veerasarma> We are developed our site in PHP code

13:02 <stellar-slack1> <veerasarma> but the stellar API in js-sdk so we don't have a idea how to integrate these process on our site

13:02 <stellar-slack1> <veerasarma> anybody have the idea for this

13:17 <stellar-slack1> <regisg27> @veerasarma: You can create an api with a nodejs server & js-stellar-sdk , then you can query this server from you php code with a php http client like guzzle.

13:20 <stellar-slack1> <veerasarma> fine and thanks

13:41 <stellar-slack1> <jed> Veerasarma what are you building!

14:50 <stellar-slack1> <sacarlson> veerasarma: and maybe depending on what you are doing you website can do transactions from the user side to horizon and you can get the results on you php side with restclient or other method available on php http://phphttpclient.com/

18:15 <stellar-slack1> <scott> horizon deploy is going out. Contains the link changes discussed last week.

20:03 <stellar-slack1> <brian.ebert> On this page:

20:03 <stellar-slack1> <brian.ebert> sorry. I'll begin again

20:14 <stellar-slack1> <brian.ebert> Wait...I think I understand

20:31 <stellar-slack1> <brian.ebert> One more question: it appears I don't need to include the sequence number of the funding account if I'm creating a new account. I've been using the sequence number when creating a payment from one account to another. Why the difference?

20:40 <stellar-slack1> <bartek> I think this article will answer your question: https://www.stellar.org/developers/learn/concepts/transactions.html

20:41 <stellar-slack1> <bartek> > Sequence number: Each transaction has a sequence number. Transactions follow a strict ordering rule when it comes to processing of transactions per account. For the transaction to be valid, the sequence number must match the one stored in the source account entry when the transaction is applied. After the transaction is applied, the source account's stored sequence number is incremented by 1.

20:46 <stellar-slack1> <brian.ebert> OK, call me stupid (it wouldn't be the first time) but I still don't understand. The sequence number is from the source account, so how is it different draining the source account to pay an existing account v. draining the source account to fund a new account?

20:49 <stellar-slack1> <bartek> > it appears I don't need to include the sequence number of the funding account if I'm creating a new account you need to add current sequence number to every transaction. you only include sequence number of source account. please ask if you have any other questions.

20:51 <stellar-slack1> <bartek> sequence numbers are required to prevent replay attacks: https://en.wikipedia.org/wiki/Replay_attack

21:02 <stellar-slack1> <brian.ebert> I can assure you I am not including a sequence number when I create and fund a new account.

21:03 <stellar-slack1> <bartek> can you share your code?

21:11 <stellar-slack1> <bartek> for example in your snippet this line: `server.loadAccount(fundingAccountAddress)` is responsible for loading current sequence number from the network.

21:12 <stellar-slack1> <brian.ebert> OK, thanks. That clears it all up!

21:13 <stellar-slack1> <brian.ebert> Although even with the mystery solved. So if I wanted to, could I call server.loadAccount when making a payment?

21:15 <stellar-slack1> <bartek> sure, every transaction consists of operations, you can add create account or payment operation (or even both if you want) to a single transactions. more info here: https://www.stellar.org/developers/learn/concepts/transactions.html