bit2017 has quit [Ping timeout: 240 seconds]
bit2017 has joined #stellar-dev
nivah has joined #stellar-dev
bittrex-richie_ has joined #stellar-dev
bit2017 has quit [Ping timeout: 248 seconds]
bittrex-richie has quit [Ping timeout: 248 seconds]
nivah has quit [Ping timeout: 240 seconds]
bit2017 has joined #stellar-dev
bit2017 has quit [Ping timeout: 240 seconds]
_whitelogger has quit [Ping timeout: 260 seconds]
_whitelogger_ has joined #stellar-dev
stellar-slack has quit [Remote host closed the connection]
stellar-slack has joined #stellar-dev
TheSeven has quit [Ping timeout: 250 seconds]
TheSeven has joined #stellar-dev
bit2017 has joined #stellar-dev
_whitelogger_ has quit [Excess Flood]
_whitelogger has joined #stellar-dev
_whitelogger has quit [Excess Flood]
_whitelogger has joined #stellar-dev
_whitelogger has quit [Excess Flood]
_whitelogger has joined #stellar-dev
<stellar-slack> <jimw> attached snippet is where I assume is not correct. I'm guessing this creates a brand-new asset, rather than transferring the existing one
_whitelogger has quit [Excess Flood]
_whitelogger has joined #stellar-dev
_whitelogger has quit [Excess Flood]
_whitelogger has joined #stellar-dev
<stellar-slack> <raymens> the issueing account doesn't hold a negative balance of the issued asset amount if that's what you're asking
<stellar-slack> <armed10> Under what conditions can a standalone node get out of sync?
<stellar-slack> <armed10> We've successfully got horizon and horizon importer to work with the stellar-core :) (thanks @scott ) so we've started load testing it.
<stellar-slack> <armed10> if we push about 250 transaction with 20 operations each in 1 ledger the core gets out of sync
acetakwas has joined #stellar-dev
acetakwas has quit [Ping timeout: 276 seconds]
acetakwas has joined #stellar-dev
acetakwas has quit [Read error: Connection reset by peer]
acetakwas has joined #stellar-dev
_whitelogger has quit [Excess Flood]
_whitelogger has joined #stellar-dev
acetakwas has quit [Read error: Connection reset by peer]
acetakwas has joined #stellar-dev
acetakwas has quit [Read error: Connection reset by peer]
acetakwas has joined #stellar-dev
acetakwas has quit [Read error: Connection reset by peer]
acetakwas has joined #stellar-dev
tom233 has joined #stellar-dev
acetakwas has quit [Read error: Connection reset by peer]
acetakwas has joined #stellar-dev
_whitelogger has quit [Excess Flood]
_whitelogger has joined #stellar-dev
acetakwas has quit [Read error: Connection reset by peer]
acetakwas has joined #stellar-dev
acetakwas has quit [Read error: Connection reset by peer]
acetakwas has joined #stellar-dev
bit2017 has quit [Ping timeout: 248 seconds]
tom233 has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
<stellar-slack> <ant> where does the 100 fee that you attach to the transaction go? Does it get used up or does it go to a validator?
acetakwas has quit [Ping timeout: 276 seconds]
acetakwas has joined #stellar-dev
<stellar-slack> <bartek> it is lost or goes to inflation pool. I don't remember which one is correct.
bit2017 has joined #stellar-dev
<stellar-slack> <jed> It goes to the inflation pool
<stellar-slack> <armed10> I was experimenting with horizon, and we noticed it does a lot of queries with limit 1, when we do a lot of transactions, this slows the feedback down substantially. Why is this?
tom233 has joined #stellar-dev
_whitelogger has quit [Ping timeout: 260 seconds]
_whitelogger has joined #stellar-dev
tom233 has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
<stellar-slack> <jed> armed10: what kind of hardware are you running the load test on?
acetakwas has quit [Read error: Connection reset by peer]
acetakwas has joined #stellar-dev
acetakwas has quit [Remote host closed the connection]
_whitelogger has quit [Ping timeout: 260 seconds]
_whitelogger has joined #stellar-dev
_whitelogger has quit [Excess Flood]
_whitelogger has joined #stellar-dev
bittrex-richie_ is now known as bittrex-richie
<stellar-slack> <scott> @graydon: It seems like `scc` is busted for my testing use cases… using `manual_close` mode I get `state: Joining SCP` status messages continually. Would you think this is an issue with scc or did anything in stellar core change around manual close mode?
<stellar-slack> <scott> no hurry, I’m investigating things myself as well, just wanted to see if you thought of anything off the top of your head
<stellar-slack> <jed> when is the last time it worked?
<stellar-slack> <scott> No clue, I haven’t updated stellar-core code or stellar_core_commander code in a while since the test scenarios were already fleshed out
<stellar-slack> <scott> Ah! it looks like that status of stellar-core is set to “Joining SCP” until the first call to close a ledger when using `MANUAL_CLOSE=true` in your stellar-core.cfg
_whitelogger has quit [Excess Flood]
_whitelogger has joined #stellar-dev
<stellar-slack> <ant> what to people think of interledger? http://www.slideshare.net/Interledger/ilp-webinar-102015-55230856 vs Hyperledger https://github.com/hyperledger/hyperledger
_whitelogger has quit [Ping timeout: 260 seconds]
_whitelogger_ has joined #stellar-dev
_whitelogger_ has quit [Excess Flood]
_whitelogger has joined #stellar-dev
_whitelogger has quit [Excess Flood]
_whitelogger has joined #stellar-dev
_whitelogger has quit [Excess Flood]
_whitelogger has joined #stellar-dev