tl;dr: the rest of the network can still reach consensus and it will not halt the network.
In your case, there is only one non-compromised validator. Any node outside the set of compromised nodes that include the non-compromised validator in their own quorum set will get a non-matching result from just that one node (assuming that the non-compromised ...
I don't exactly is that is the problem but you should look at your configuration file. In there, I see:
Your are trusting EUR and USD assets issued by account GC4RK7WX...F2HAX
You are issuing with assets with account GCOGCY...TRYPOX
You will be receiving payments with account GC4RK7WX...EQEXF2HAX
Based on the above I see the following potential problems:
For just federation -- no compliance -- the above sounds correct. As outlined in the docs, which you mentioned you have read through, this is easily done via Stellar's prebuilt federation server which can hook into an existing database. Once it is connected, it
essentially translates a federation request into a SQL query. The
server supports MySQL, ...
The Federation server would return some value with the memo field that can be used by the service provider (you) to uniquely identify the receiving user. A database ID does match this requirement but you can use anything else that makes sense in your domain as long as it's unique (also in the future).
The bridge server does also help to participate with the ...
The bridge server is watching the configured stellar accountID for incoming payments events via horizon stream api and iterating over it.
The error could appear when the response was not empty but did not contain payment events. Do you run a recent version of horizon + bridge server? I can not replicate the issue.
To help debugging the issue, please check ...
This information is not enough. What code are your trying to execute? Where is the stack trace of the error?
As I understand from the error description, you are trying to send some funds, but request parameters are invalid (specifically, parameter amount is missing).
Check this example of properly formed request:
var request = require('request');