Transaction from bridge is not mined in Kovan (Foreign side)

[vbaranov]

Parity/v1.8.0-beta
Bridge is from master branch.
Home is private PoA network with spec and toml. Foreign is Kovan. Bridge config is here.
ForeignBridge contract: https://kovan.etherscan.io/address/0xdcf351544fdfe470a7b618928642399b93ffa958#code

Investor: 0xEaeBA7869E23A328a0A92620BbA1A7a6aaED26cB
0.001 eth is sent

Logs:

Private PoA side (home):

2017-10-18 18:36:42   INFO own_tx  Transaction mined (hash 9f4328917ecae09c81bc94295327c2254bd8d88f152464e51f444b80e013ee4d)

Kovan side (foreign):

2017-10-18 18:36:42   TRACE rpc  Request: {"jsonrpc":"2.0","method":"eth_sendTransaction","params":[{"data":"0x26b3293f000000000000000000000000eaeba7869e23a328a0a92620bba1a7a6aaed26cb00000000000000000000000000000000000000000000000000038d7ea4c680009f4328917ecae09c81bc94295327c2254bd8d88f152464e51f444b80e013ee4d","from":"0x00db9af45c6f241432f2cbe412c6969cb7778d98","gas":"0x186a0","gasPrice":"0x0","to":"0xdcf351544fdfe470a7b618928642399b93ffa958"}],"id":4097}.
2017-10-18 18:36:42   DEBUG rpc  [Some(Num(4097))] Took 68ms
2017-10-18 18:36:42   DEBUG rpc  Response: {"jsonrpc":"2.0","result":"0x749e745a593323cae6b41bbda1e3c80405e23e37ac23f4f069a0565a1bd1b491","id":4097}.

But transaction with hash 0x749e745a593323cae6b41bbda1e3c80405e23e37ac23f4f069a0565a1bd1b491 can't be find as mined in Kovan. I can't find it in Etherscan.

Another one try with full trace at Kovan side logging="poa=trace,signer=trace,engine=trace,own_tx=trace,txqueue=trace,sync=trace"

Private PoA side (home):

2017-10-18 19:15:15   INFO own_tx  Transaction mined (hash 4911eaec4cadc2469ba9b43767957757ae0e011e3f2ad57bb28825f9ea6cc03e)

Kovan side (foreign):

2017-10-18 19:15:15   TRACE own_tx  Importing transaction: PendingTransaction { transaction: SignedTransaction { transaction: UnverifiedTransaction { unsigned: Transaction { nonce: 73, gas_price: 0, gas: 100000, action: Call(dcf351544fdfe470a7b618928642399b93ffa958), value: 0, data: [38, 179, 41, 63, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 234, 235, 167, 134, 158, 35, 163, 40, 160, 169, 38, 32, 187, 161, 167, 166, 170, 237, 38, 203, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 141, 126, 164, 198, 128, 0, 73, 17, 234, 236, 76, 173, 194, 70, 155, 169, 180, 55, 103, 149, 119, 87, 174, 14, 1, 30, 63, 42, 213, 123, 178, 136, 37, 249, 234, 108, 192, 62] }, v: 120, r: 40664849902588265502832923571841725693800088266545607532580286953484288571259, s: 46970124881255361458992124855158539901137055806175960944316180293039990823097, hash: 19c9029588ffeb599e495361acc41cd2dfc3e0b81f5d3dc2986f7aa65823e3e9 }, sender: 00db9af45c6f241432f2cbe412c6969cb7778d98, public: Some(fd915be0765b59747bf0cd6a46fdefb52a85302bbdcd3c5b5e3ad59107afa6f4d212ddbfe831dd58786f641147277e75650a3955473de05771a1d323330b9d4e) }, condition: None }
2017-10-18 19:15:15   TRACE txqueue  Inserting: TransactionOrder { nonce_height: 4, gas_price: 0, gas_factor: 0, gas: 100000, mem_usage: 112, strategy: GasPriceOnly, hash: 19c9029588ffeb599e495361acc41cd2dfc3e0b81f5d3dc2986f7aa65823e3e9, insertion_id: 549, origin: Local, penalties: 0 }
2017-10-18 19:15:15   DEBUG txqueue  Imported transaction to current: 19c9029588ffeb599e495361acc41cd2dfc3e0b81f5d3dc2986f7aa65823e3e9
2017-10-18 19:15:15   DEBUG txqueue  status: TransactionQueueStatus { pending: 6, future: 133 }
2017-10-18 19:15:15   DEBUG own_tx  Imported to Current (hash 19c9029588ffeb599e495361acc41cd2dfc3e0b81f5d3dc2986f7aa65823e3e9)
2017-10-18 19:15:15   TRACE own_tx  Status: TransactionQueueStatus { pending: 6, future: 133 }
2017-10-18 19:15:15   TRACE engine  Fetched proposer for step 377085828: 0020…81a1
2017-10-18 19:15:15   TRACE engine  generate_seal: 00db…8d98 not a proposer for step 377085828.
201

[akolotov]

@vbaranov, have checked the issue. I cannot reproduce it. Based on what I see in the logs, seems the node is trying to seal the block with the transaction but cannot do this. Does the account has the right to seal in the KOVAN network?

[vbaranov]

The issue is because, when I've changed to custom contract at the home side of bridge, I should to change home_deploy property of db.toml to actual value too. If to change it to actual block number, where the custom home side contract is mined, bridge works. Issue can be closed.