<stellar-slack>
<zealord> @sacarlson: there's a configuration file stellar.txt under every gateway with the address of the gateway (issuer). Here's the list:
<sacarlson>
11:11:10 PM) stellar-slack: <scott> scarlson: I haven’t followed the full conversation, but I wanted to just provide one note about your examples using `static_path_find`: It looks like in the query you were making where you received no `alternatives` in the response you simply had the destination issuer wrong. For example, the query
koolhead17 has quit [Remote host closed the connection]
gst has joined #stellar-dev
gst has quit [Changing host]
gst has joined #stellar-dev
stevedomin has quit []
stevedomin has joined #stellar-dev
DomKM has quit []
DomKM has joined #stellar-dev
_whitelogger has quit [Ping timeout: 252 seconds]
_whitelogger has joined #stellar-dev
loglaunch has joined #stellar-dev
sacarlson1 has joined #stellar-dev
sacarlson has quit [Ping timeout: 246 seconds]
sacarlson1 has quit [Quit: Leaving.]
sacarlson has joined #stellar-dev
koolhead17 has joined #stellar-dev
koolhead17 has quit [Remote host closed the connection]
DomKM has quit [Quit: Connection closed for inactivity]
_whitelogger has joined #stellar-dev
stellar-slack has quit [Remote host closed the connection]
stellar-slack has joined #stellar-dev
<stellar-slack>
<lab> hi stellar-core devs, i want to know why we need bucketlist.
<stellar-slack>
<lab> IMHO, ledgerheader+deltas where sha256(prev(ledgerheader+deltas)) included in current ledgerheader is enough
alanz has quit [Ping timeout: 252 seconds]
pixelbeat has quit [Ping timeout: 250 seconds]
alanz has joined #stellar-dev
<stellar-slack>
<monsieurnicolas> when catching up to a given ledger, it's a way to quickly know if you build the right state, otherwise you would have to walk the entire history from genesis