Open pharr117 opened 1 year ago
@pharr117 can you look at all the current wasm message types and spend a few minutes thinking about if any of them have taxable implications. We can do a separate ticket for developing support for each one after we determine if there are any
Current WASM module provides the following message types (see here for details):
/cosmwasm.wasm.v1.MsgExecuteContract
/cosmwasm.wasm.v1.MsgInstantiateContract
/cosmwasm.wasm.v1.MsgStoreCode
/cosmwasm.wasm.v1.MsgMigrateContract
/cosmwasm.wasm.v1.MsgUpdateAdmin"
/cosmwasm.wasm.v1.MsgClearAdmin
/cosmwasm.wasm.v1.MsgUpdateInstantiationAdmin
/cosmwasm.wasm.v1.MsgUpdateParams
/cosmwasm.wasm.v1.MsgSudoContract
/cosmwasm.wasm.v1.MsgPinCodes
/cosmwasm.wasm.v1.MsgUnpinCodes
/cosmwasm.wasm.v1.MsgStoreAndInstantiateContract
/cosmwasm.wasm.v1.MsgRemoveCodeUploadParamsAddresses
/cosmwasm.wasm.v1.MsgAddCodeUploadParamsAddresses
/cosmwasm.wasm.v1.MsgStoreAndMigrateContract
As a first easy answer, MsgExecuteContract will for sure have taxable implications. We are already tracking an issue that suggests how we would want to implement parsers for particular contracts: #443
We want to take a deep dive into Osmosis contracts for taxable transactions.
We would need to explore the ecosystem for WASM contracts that have taxable implications and build an event parser that pulls the proper values out of the contract execution event list.