I don't think this is worth the work that it would entail. The official dydx governance platform does not link to any on-chain transaction. The official aave governance platform links to events on Etherscan but these are useless beyond serving as a testament that an event is on-chain e.g. https://etherscan.io/tx/0xaa9b52afa821bd948aae29a5379c4720e162f9728c6a81bcd488f877bd213615. All of the proposals we display are extremely old. All of these communities have migrated to newer contracts or even entirely different chains a long time ago.
Also note, we don't have 'internal' proposal ids. All proposal ids are the actual on-chain proposal ids (may be converted into human-readable base-10). It may be sufficient to just disable hyperlinks for proposal links in EVM communities so that users can still tell which proposal is related to the thread.
I don't think this is worth the work that it would entail. The official
dydxgovernance platform does not link to any on-chain transaction. The officialaavegovernance platform links to events on Etherscan but these are useless beyond serving as a testament that an event is on-chain e.g. https://etherscan.io/tx/0xaa9b52afa821bd948aae29a5379c4720e162f9728c6a81bcd488f877bd213615. All of the proposals we display are extremely old. All of these communities have migrated to newer contracts or even entirely different chains a long time ago.Also note, we don't have 'internal' proposal ids. All proposal ids are the actual on-chain proposal ids (may be converted into human-readable base-10). It may be sufficient to just disable hyperlinks for proposal links in EVM communities so that users can still tell which proposal is related to the thread.