When using a non-memory database, we fetch the transaction every time from the database. This will reset the trading_peer attribute, which is not persisted in the database. However, it seems that it was not reinitialised when we process an incoming payment.
Also fixed a minor error in a logging statement.
I tested these changes with a validation experiment using a real sqlite database, see here.
When using a non-memory database, we fetch the transaction every time from the database. This will reset the
trading_peerattribute, which is not persisted in the database. However, it seems that it was not reinitialised when we process an incoming payment.Also fixed a minor error in a logging statement.
I tested these changes with a validation experiment using a real sqlite database, see here.