Jed McCaleb

https://github.com/stellar/stellar-protocol/issues/28 Steps that need to happen when you handle an incoming message: 1. you receive a tx 2. Do you already have a preimage of the memo? 3. no ->...

Needs to pass through the errors that it gets from horizon on

1

Right now it returns any error as 400 and its opaque to the caller what is going on. at least with /payment

in the config docs

If connected to a compliance server it should hit the /receive_payment endpoint and reject the payment if the compliance server hasn't approved.

The stellar.toml will tell you if it does.

This needs better docs

3

- overview of what this is - how it install this - where is the DB kept? - how do you set the config? - How do you connect horizon...

Allow the .cfg to be overridden

3

well, it'd always be in the docker file system, so you'd need -v container can't view the host's fs without that but if it's something other than /stellar-core.cfg, confd won't...

Convert the unix timestamp you enter for the time bounds of a tx to something human readable and display it somewhere outside the edit box.