New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Show decoded target address in User operations #2189

Open

k1rill-fedoseev opened this issue Aug 23, 2024 · 0 comments

Labels

Member

k1rill-fedoseev commented Aug 23, 2024 •

edited

Loading

API route /api/v2/proxy/account-abstraction/operations/<op_hash> may include the following decoded field:

{
//...
  "execute_target": {
        "ens_domain_name": null,
        "hash": "0x017405a2De0613e12cd3D7B67e691BfEfC46Debf",
        "implementations": [],
        "is_contract": true,
        "is_verified": true,
        "metadata": null,
        "name": "Missions"
  },
//...
}

E.g. if the user operation was a USDC-transfer, this contract would a USDC contract address. We should display this field in the UI, if available.

Field is available in the API iff execute_call_data field is present too.

The text was updated successfully, but these errors were encountered:

k1rill-fedoseev added the need design label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment