Repository navigation
Avoid the 301 redirect by linking directly to Snowtrace - #3193
Conversation
|
@menxit is attempting to deploy a commit to the Aave Team on Vercel. A member of the Team first needs to authorize it. |
|
@menxit happy to merge this with a small change of keeping ethereum as etherscan |
|
@sammdec thanks for the review! did you get a chance to compare transaction actions? Etherscan can make Aave activity hard to follow and sometimes misreads the protocol. Fore example here, Etherscan says the user repaid 3,776.93 ETH to Aave. That overstates the repayment by 9.42 ETH, which the gateway returned to the user. Seeing that higher amount can make the user worry they overpaid. Ethscanner shows 3,767.51 ETH, matching Aave's |
Totally understand but would prefer to keep etherscan for now |
|
❌ CI run has failed! |
General Changes
Aave already sends Avalanche users to
snowtrace.io, a Routescan explorer, through a 301 redirect fromcchain.explorer.avax.network. This PR updates the Avalanche explorer URL tosnowtrace.ioso users reach the same transaction receipts and address pages directly.This PR also proposes using Routescan as the default explorer for Ethereum (
ethscanner.io) and Mantle (mantle.routescan.io). Routescan decodes Aave contract events and summarizes what changed for the user. For example, in the Ethereum collateral swap below, Etherscan's Transaction Action shows the USDC withdrawn from Aave. Ethscanner also shows the WETH supplied in its place.Developer Notes
The three explorer URLs in
src/ui-config/networksConfig.tsare used for both transaction and address links. Each Ethereum row below links to the same transaction on both explorers.Reviewer Checklist
.env.exampleand the relevant.github/actions/*files