bridge-server
bridge-server copied to clipboard
Deprecated. Go to https://github.com/stellar/go/tree/master/services/bridge
When a transaction has more than one payment operation, it only saves the first payment operation and then logs `Payment already exists`. it does not save the other operations.
We should probably stuff it in the compliance config, and add it to to the Stellar.org/developers docs.
In writing the new anchor guide, I was at first a little confused to find that I had to specify `extra_memo` in the payment parameters to the bridge server in...
The compliance readme currently lists the `encryption_key` config property as [“not working yet,”](https://github.com/stellar/bridge-server/blob/master/readme_compliance.md#config) but it is still required in the configuration validation routine: https://github.com/stellar/bridge-server/blob/master/src/github.com/stellar/gateway/compliance/config/config.go#L59-L62 Should it be optional until support...
It strikes me that the common case for bridge server is for the `ReceivingAccountID` to be the account ID that corresponds to `BaseSeed` (please correct me if this seems way...
The readme for compliance currently states that if the `ask_user` callback is not specified, “then the customer information won't be given to the other FI.” This isn’t actually true—it falls...
in the config docs
This is one of two issues that had me pretty much stumped for more than a day. In the 0.0.12 release of bridge server (haven't checked compliance server for this...