12:42 <stellar-slack> <raymens> Can someone else verify using ``` for N in 1 2; do docker run --name db$N -p 544$N:5432 --env-file examples/local.env -d stellar/stellar-core-state docker run --name node$N --net host -v ~/.aws:/root/.aws --volumes-from db$N --env-file examples/local.env -d stellar/stellar-core /start node$N fresh forcescp done for N in 3; do docker run --name db$N -p 544$N:5432 --env-file examples/local.env -d stel

12:42 <stellar-slack> --name node$N --net host -v ~/.aws:/root/.aws --volumes-from db$N --env-file examples/local.env -d stellar/stellar-core /start node$N fresh done ``` Is actually working? (sample from docker repo)

12:44 <stellar-slack> <raymens> node1 output is the following the whole time: ``` 2015-10-21T12:42:34.918 self [] [Overlay] INFO New connected peer 127.0.0.1:0 2015-10-21T12:42:34.919 self [] [Overlay] ERROR Message-auth check failed [Peer.cpp:536] 2015-10-21T12:42:34.919 self [] [Overlay] INFO Dropping peer 7851f5@127.0.0.1:11635 2015-10-21T12:42:49.415 self [] [Overlay] WARN idle timeout 2015-10-21T12:42:49.415 self [] [Overlay] INF

12:44 <stellar-slack> 2015-10-21T12:42:50.444 self [] [Overlay] INFO New connected peer 127.0.0.1:0 2015-10-21T12:42:50.448 self [] [Overlay] INFO successful handshake with 048e0d@127.0.0.1:11645 2015-10-21T12:43:04.951 self [] [Overlay] INFO New connected peer 127.0.0.1:11625 2015-10-21T12:43:04.952 self [] [Overlay] INFO New connected peer 127.0.0.1:11635 2015-10-21T12:43:04.954 self [] [Overlay] INFO New connected peer 127.0.0.1:

12:44 <stellar-slack> [Overlay] WARN connecting to self 2015-10-21T12:43:04.959 self [] [Overlay] INFO Dropping peer self@127.0.0.1:11625 2015-10-21T12:43:04.960 self [] [Overlay] ERROR readHeaderHandler error: End of file :127.0.0.1:11625 [TCPPeer.cpp:312] 2015-10-21T12:43:04.960 self [] [Overlay] INFO Dropping peer 000000@127.0.0.1:11625 2015-10-21T12:43:04.961 self [] [Overlay] WARN Received error (ERR_AUTH): unexpected MAC 2015-1

12:44 <stellar-slack> Dropping peer 7851f5@127.0.0.1:11635 2015-10-21T12:43:22.966 self [] [Overlay] INFO New connected peer 127.0.0.1:0 2015-10-21T12:43:22.967 self [] [Overlay] ERROR Message-auth check failed [Peer.cpp:536] 2015-10-21T12:43:22.968 self [] [Overlay] INFO Dropping peer 7851f5@127.0.0.1:11635 2015-10-21T12:43:25.445 self [] [Overlay] ERROR readHeaderHandler error: End of file :127.0.0.1:11645 [TCPPeer.cpp:312] 2015-10-

12:44 <stellar-slack> Dropping peer 048e0d@127.0.0.1:11645 2015-10-21T12:43:26.478 self [] [Overlay] INFO New connected peer 127.0.0.1:0 2015-10-21T12:43:26.488 self [] [Overlay] INFO successful handshake with 048e0d@127.0.0.1:11645 2015-10-21T12:43:57.007 self [] [Overlay] INFO New connected peer 127.0.0.1:11625 2015-10-21T12:43:57.007 self [] [Overlay] INFO New connected peer 127.0.0.1:0 2015-10-21T12:43:57.008 self [] [Overlay] WA

12:44 <stellar-slack> 2015-10-21T12:43:57.008 self [] [Overlay] INFO Dropping peer self@127.0.0.1:11625 2015-10-21T12:43:57.009 self [] [Overlay] ERROR readHeaderHandler error: End of file :127.0.0.1:11625 [TCPPeer.cpp:312] 2015-10-21T12:43:57.009 self [] [Overlay] INFO Dropping peer 000000@127.0.0.1:11625 ```

14:58 <stellar-slack> <jed> raymens: there is this bug right now which is probably causing it: https://github.com/stellar/stellar-core/issues/868

14:58 <stellar-slack> <jed> should be fixed in a couple hours

14:59 <stellar-slack> <raymens> Awesome, thanks for notifying :)

21:16 <stellar-slack> <scott> I’m rolling some new code out to testnet horizon… perhaps a few hiccups as I do

21:26 <stellar-slack> <jed> raymens should be fixed now

22:01 <stellar-slack1> <jed> @monsieurnicolas: Hey I'm going to tag master since the current latest tag is in a bad spot right?

22:07 <stellar-slack1> <brian.ebert> I've started watching payments using horizon-testnet. Per the horizon tutorial I set that up with eventsource. The reference documentation at https://www.stellar.org/developers/horizon/reference/payments-for-account.html says that the payments endpoint can also be used for streaming. Which is the preferred way to watch payments on accounts?

22:09 <stellar-slack1> <scott> streaming on that page _is_ referring to eventsource

22:09 <stellar-slack1> <scott> so, youre already there :)

22:17 <stellar-slack1> <brian.ebert> thanks. I'm about to start constructing payments and I'm confused by the make_payments.js window on the "follow payments" tutorial page. My understanding is that code is creating a payment from the account created at the beginning of the tutorial, to a new account number created in the line "destination: StellarBase.Keypair.random().address()," of make_payments.js. The new account should create upon

22:17 <stellar-slack1> that window. Do I understand correctly?

22:18 <stellar-slack1> <scott> That specific example never submits the transaction, so no. It should output a base64 string to the console

22:19 <stellar-slack1> <brian.ebert> Oh, one more thing: if I'm using eventsource directly, do I need to use stellar-sdk? Should I use stellar-sdk?

22:19 <stellar-slack1> <brian.ebert> Thanks on the payments answer. I understand I need to include the blob in a transaction submission. Do I have the accounts straight?

22:19 <stellar-slack1> <scott> I recommend stellar-sdk, but you don’t need it. It makes things easier, IMO

22:19 <stellar-slack1> <jed> that example should probably be fixed btw. Since you can't pay a random address like that. that hasn't been created already

22:19 <stellar-slack1> <scott> oh! good point jed

22:20 <stellar-slack1> <scott> I thought it was creating a CreateAccountOp

22:20 <stellar-slack1> <jed> brian did you look at this: https://www.stellar.org/developers/js-stellar-base/learn/building-transactions.html

22:20 <stellar-slack1> <brian.ebert> Thanks, Jed. I was going to use a receiving account I'd already created anyway.

22:20 <stellar-slack1> <jed> and these examples: https://www.stellar.org/developers/js-stellar-base/learn/base-examples.html

22:21 <stellar-slack1> <scott> we need to add a create account example into there, for sure

22:22 <stellar-slack1> <brian.ebert> Jed: no, I haven't read that. Will do now.

22:24 <stellar-slack1> <brian.ebert> Thank you guys very much for your work. FYI, recent work I've read, particularly the ability to issue an asset and control which accounts can hold it, are very powerful. Although I certainly don't have a comprehensive view, stellar appears to resolve some major criticism of digital cash.

22:25 <stellar-slack1> <scott> happy to help! and thanks for the kind words

22:34 <stellar-slack1> <scott> jed: new ledger data is deployed on testnet: https://horizon-testnet.stellar.org/ledgers/280499

22:34 <stellar-slack1> <jed> nice

22:35 <stellar-slack1> <jed> can you roll it out on live as well

22:36 <stellar-slack1> <scott> yeah, it’ll take a bit (plus a that migration)

22:38 <stellar-slack1> <brian.ebert> One more thing. Jed said: "you can't pay a random address like that. that hasn't been created already." I thought an account was created by making a payment to it. Is there another procedure to be followed? If I were running a gateway for example, how would I create an account?

22:39 <stellar-slack1> <jed> there is a separate operation for creating an account now

22:40 <stellar-slack1> <jed> so you have to use that if it doesn't exist yet

22:42 <stellar-slack1> <brian.ebert> Thanks again!