06:40 <stellar-slack> <regisg> what is the max number of signers by transaction ? I haven't find this info in the docs.

07:03 <stellar-slack> <armed10> @regisg: yes, max 20 signers for 1 transaction

07:05 <stellar-slack> <armed10> When we start running our private network 3 out of 4 nodes is synced, but the fourth node keeps throwing this error : 2016-04-08T09:01:15.465 GAR67 [Overlay WARN ] Received error (ERR_AUTH): unexpected MAC Is there a way to solve this problem ?

09:16 <stellar-slack> <jed> Armed10 Are the seeds in the configuration unique?

09:18 <stellar-slack> <jed> Are you limiting what peers can connect in the config?

10:20 <stellar-slack> <armed10> Yes, all the seeds are unique, and only preferred peers can connect. all the configs are generated in 1 location so every node has the same config except for the seed. That's why it's so strange that only one node throws the error sometimes.

14:18 <stellar-slack> <jed> Hmm I'll try to make the log msg more informative. Could you make an issue and include the log lines above the warning? @armed10

15:30 <stellar-slack> <jed> <!here|@here> we will be wiping the testnet shortly unless anyone has major objections

16:17 <stellar-slack> <otto_mora> let us know when done, thanks

17:10 <stellar-slack> <jed> back up in ~30min

17:51 <stellar-slack> <scott> testent nearly back up… just funding friendbot now

17:57 <stellar-slack> <otto_mora> awesome, can we re-use the key pairs we had from earlier? that would save me some retrofit updates in our system

17:57 <stellar-slack> <jed> yeah you can

17:57 <stellar-slack> <otto_mora> sweet

17:57 <stellar-slack> <jed> you will need to refund the accounts of course

17:57 <stellar-slack> <otto_mora> right thats fine

18:05 <stellar-slack> <otto_mora> can we call this the testnet spring cleaning? :P

18:05 <stellar-slack> <otto_mora> the timing is funny hehe

18:05 <stellar-slack> <scott> :)

18:06 <stellar-slack> <scott> going to take a little bit longer to bring it back up… one of our users seems to be running a poorly written script (probably our java sdk) that is hammering the server uncontrollably so I cannot diagnose very easily the problem with transaction submission

18:59 <stellar-slack> <scott> Alright, testnet is running and importing history again, but friendbot isn’t playing nice. I’ll post again when I have it fixed

19:09 <stellar-slack> <scott> <!here|@here>: friendbot is back up, history is importing, and testnet should be good to go now. Sorry for all the trouble. On the plus side, I’ve now got a list of bugs to fix and procedures to improve :)

19:10 <stellar-slack> <scott> as a note, we’re now ruby-free on the testnet… the go version of horizon is doing the imports.

19:13 <stellar-slack> <otto_mora> is there a way to call friendbot from an API or web page so that i can refund the accounts we had?

19:14 <stellar-slack> <scott> yeah, just make an get request to a URL of the form `https://horizon-testnet.stellar.org/friendbot?addr=SOMEADDRESS`

19:17 <stellar-slack> <otto_mora> sweet its working

20:05 <stellar-slack> <danielpauljones> Is there a simple way to create other "currencies" in the testing environment? I don't need to exchange them with any other currency, just send and receive them between accounts.

20:08 <stellar-slack> <scott> @danielpauljones: currencies don’t really get created as an explicit action. Instead, simply have one account trusts another (using the “change trust” operation) for a certain asset

20:08 <stellar-slack> <scott> I recommned you test it out using: https://www.stellar.org/laboratory

20:09 <stellar-slack> <scott> You can configure transactions using the Transaction Builder

20:09 <stellar-slack> <scott> does that make sense?

20:14 <stellar-slack> <danielpauljones> Yes, somewhat.

20:14 <stellar-slack> <danielpauljones> Cannot find the "change trust" in the Laboratory.

20:18 <stellar-slack> <scott> Basically, you’ll need to fill out that form (I recommend learning the concepts as you go along)

20:18 <stellar-slack> <scott> When complete, the form will spit out a “transaction blob"

20:19 <stellar-slack> <scott> You can then sign and submit that transaction using other portions of the lab

20:19 <stellar-slack> <danielpauljones> @scott: thanks. That makes sense, y'all are the best. Let me try and learm and I will get back to you with further questions, I am sure.

20:20 <stellar-slack> <scott> you’re welcome :) happy to help when you have futher questions

20:37 <stellar-slack> <eva> @danielpauljones: hi! Late to the party, but if you’re still working on it I actually wrote a tutorial on this: https://docs.google.com/document/d/1ByYwpBT0U4X9r5Q1UjphnRlJacNBxL8IiSYCOib2N0M/edit?usp=sharing (It’s a draft, so feedback is very welcome)

21:41 <stellar-slack> <danielpauljones> @eva: Thanks. This is perfect. I am going through it now.

21:42 <stellar-slack> <eva> @danielpauljones: awesome! Please feel free to ask if anything is confusing (and you can comment in the doc on anything, too). :rocket:

21:50 <stellar-slack> <otto_mora> hey @scott and team does this new horizon change things with regards to how new payments are notified?

21:51 <stellar-slack> <scott> It shouldn’t but there could certainly be a bug. What are you seeing?

21:51 <stellar-slack> <otto_mora> any changes on the streaming functionality? I suspect my old gateway might have be broken, doesnt seem to be detecting payments coming in

21:51 <stellar-slack> <otto_mora> we were using an old one of barteks from like 2 weeks ago

21:52 <stellar-slack> <jed> it shouldn't have changed

21:52 <stellar-slack> <jed> is the payment succeeding?

21:52 <stellar-slack> <scott> Let me look into it as well… enough things broke with the roll out that i should check into it manually

21:52 <stellar-slack> <otto_mora> ok going to do some testing on my local pc, hopefully its just a bug of firewall or something else

21:53 <stellar-slack> <otto_mora> the payment does succed

21:54 <stellar-slack> <scott> Streaming does appear to be working as expected, at least for the `/ledgers` endpoint.

21:54 <stellar-slack> <scott> Do you have an example URL you are trying to stream from?

21:57 <stellar-slack> <otto_mora> hmm not sure which one the gateway server uses as I only have the binary

21:58 <stellar-slack> <otto_mora> it just seems to be sitting on listening for payments and nothing really coming in

21:59 <stellar-slack> <jed> does the gateway server log that it sees a payment?

22:00 <stellar-slack> <otto_mora> not on the console but let me see the database

22:03 <stellar-slack> <otto_mora> hmm yeah clean, does the gateway need to talk to compliance before it shows anything in on the console?

22:05 <stellar-slack> <jed> is there nothing at all being logged?

22:05 <stellar-slack> <otto_mora> nothing on the gateway log or db

22:06 <stellar-slack> <otto_mora> with the exception of that statement saying that is listening for payments that i showed earlier

22:07 <stellar-slack> <jed> oh I think its db needs to be wiped

22:07 <stellar-slack> <jed> it is listening at the wrong cursor

22:08 <stellar-slack> <otto_mora> run the migrations command?

22:08 <stellar-slack> <otto_mora> --migrate-db?

22:08 <stellar-slack> <jed> no let me see

22:08 <stellar-slack> <otto_mora> ok

22:09 <stellar-slack> <scott> we should add a note for barte.k to at least log a warning when it notices that the ledger has gone backwards (i.e. the network has been reset)

22:09 <stellar-slack> <jed> I'd just go in and remove the database it is pointing at and then it will make it again

22:10 <stellar-slack> <otto_mora> ok let me try that

22:15 <stellar-slack> <otto_mora> ok better, dropped the tables and ran --migrate-db to recreate

22:15 <stellar-slack> <otto_mora> now the console does show it

22:29 <stellar-slack> <otto_mora> yeah thats it, thanks guys! altough reseting the ledger is a super rare occurrence its bound to happen on the test net so maybe something to warn the users would be useful when using the gateway