As you can see, there are only six events described in the contract manifest (Synced, Minted, Burned, Swapped, Deployed and Transfer). However, the contract is able to emit a lot of other notifications, e.g. notification with name Fault:Cannot Find PairContract, see the application log for 0xf175a19a706d2a35910f686d08e188e0f5220851584fdb9fe89eed0a216eefb3 transaction in the current RC1 testnet:
Describe the bug
getcontractstate
RPC call for theFlamingo Swap-Pair Contract
deployed on the current RC1 testnet gives me the following answer:As you can see, there are only six events described in the contract manifest (
Synced
,Minted
,Burned
,Swapped
,Deployed
andTransfer
). However, the contract is able to emit a lot of other notifications, e.g. notification with nameFault:Cannot Find PairContract
, see the application log for0xf175a19a706d2a35910f686d08e188e0f5220851584fdb9fe89eed0a216eefb3
transaction in the current RC1 testnet:This event and several similar events are not described in the contract manifest.
Expected behavior All notifications emitted by the contract should be described in the contract manifest.
Platform: