Starting from release 6.6.0, /api/v2/addresses/ API v2 endpoint starts returning an array of implementations for proxy contracts in the prop implementations. Single props implementation_address and implementation_name are yet returned for backward compatibility, but will be removed in the future.
Notes:
UI should be unbound from implementation_address and implementation_name props since the backend will delete those props in some of the future releases.
An example of diamond proxy at staging environment: /api/v2/addresses/0x013Cb2854daAD8203C6686682f5d876e5D3de4a2.
Related backend task
Starting from release 6.6.0,
/api/v2/addresses/
API v2 endpoint starts returning an array of implementations for proxy contracts in the propimplementations
. Single propsimplementation_address
andimplementation_name
are yet returned for backward compatibility, but will be removed in the future.Notes:
implementation_address
andimplementation_name
props since the backend will delete those props in some of the future releases.An example of diamond proxy at staging environment:
/api/v2/addresses/0x013Cb2854daAD8203C6686682f5d876e5D3de4a2
.The response is:
An example at prod environment: https://eth.blockscout.com/address/0xc9e91eDeA9DC16604022e4E5b437Df9c64EdB05A