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.
Actual behavior
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.
Steps to reproduce
Sync against testnet.
Which version(s) does this affect? (Environment, OS, etc...)
SargeKhan
commented
5 years ago
Expected behavior
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.
Actual behavior
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.
Steps to reproduce
Sync against testnet.
Which version(s) does this affect? (Environment, OS, etc...)