OutTransfer transaction implementation checks whether dappId creator is the creator of the outtransfer transaction, which is not the current behaviour of lisk-core and it fails when syncing with testnet.
How did I fix it?
For OutTransfer transaction, the transaction which is specified in the dappId should be a dapp registeration transaction, irrespective of whether the sender of out transfer transaction is the creator of the transaction specified in the dappID.
What was the problem?
OutTransfer transaction implementation checks whether dappId creator is the creator of the outtransfer transaction, which is not the current behaviour of lisk-core and it fails when syncing with testnet.
How did I fix it?
For OutTransfer transaction, the transaction which is specified in the dappId should be a dapp registeration transaction, irrespective of whether the sender of out transfer transaction is the creator of the transaction specified in the dappID.
How to test it?
Sync against testnet.
Review checklist