cordt-sei
cordt-sei
As mentioned this is (was) intended. These have been removed in [v5.9.0](https://github.com/sei-protocol/sei-chain/releases/tag/v5.9.0-hotfix), and are now only seen through the custom `sei_*` methods.
Hey @CRossel87a we tried using your fix there and it seemed to partially work, it would start to show the 'synthetic' events for any cross-environment tx, but not all of...
I think we may have found the issue. You were also chatting with me on discord before it got hacked and deleted right? On Thu, Oct 3, 2024, 3:58 PM...
@dvli2007 Not all developers are wanting to use the pointer contracts for everything, nor the precompiles in general. Seems like a reasonable ask, as long as it is made clear...
I assume this was solved by correcting the config file. Can reopen if not.
Please try to recheck this on atlantic-2 testnet. The logIndex was not being set correctly. Historical data will not be fixed retroactively however.
So this adds additional routes while keeping existing ones for compatibility?
I imagine this is related to the fact that you are specifying an open ended range of blocks.. is this absolutely required?
Awesome thank you. I will test this as soon as I can get a node to actually sync here.
Confirmed on my end and tested fuirther, seems like an issue using pointers through contracts. ```shell # seid tx wasm execute sei1u9ftyhe5sszx9ghr7ae75ak05j86mme0xlzr0n4g0aa45hry5s0qlvr5nw \ '{"send":{"contract":"sei1v9hwx2zelwu9lha3al5d92d7u9hu7dc8naappzc7j3rl7uxw6xfs9vecvm","amount":"10","msg":"eyJzdGFrZSI6IHt9fQ=="}}' \ --from mine \ --chain-id atlantic-2...