aeternity / aescan Goto Github PK

Every oracle link should be adjusted in order to point at the right oracle details page.

Details panel:

• Name
• Symbol
• Price (only for listed tokens)
• Market cap (only for listed tokens)
• Total supply
• Holders
• Hash
• Contract
• Decimals
• Extensions
• API links: Middleware, DEX

Note: token name / symbol is not unique so it cannot be used to navigate to the tokens detail (check the old explorer, it’s using ct_).

• If a valid hash is entered the user is redirected to the details page
• If an invalid hash is entered the user is redirected to the search results page and the specific "not found" panel is displayed. Example:

• If a string like "abc" is entered (not a hash), the user is redirected to the search results page to display names and tokens results

The last two cases are handled here: #210

In a few places of the application we use !important; in CSS, which is not ideal. We usually use it to fix quickly some code written using bad practices. The ideal solution is not to modify the internal CSS of a component from outside, which may lead to visual issues when css is loaded in a different order between dev mode and production build.

Generalized accounts should have a specific label to mark them.

Currently, to fetch market stats about aeternity tokens we are using free coingecko which has harsh API rate limits. We should implement in-memory caching in SSR to cache the results so we can avoid errors in case a user starts refreshing a page very often and gets blocked

After implementing state channels all state channels links should be fixed to point to the right page.

Context information

application version: 0.1.0 (testnet, but probably also irrelevant)
device: irrelevant
browser: irrelevant
operating system: irrelevant

Steps to reproduce

1. Open a state channel via ChannelCreateTx (e.g. by playing the state channel demo https://statechannel.aepps.com/)

What is expected?

I expect to see two different accounts that are involved in the channel with their corresponding AE deposit value in the Data column of the explorer.

What is actually happening?

The same account appears twice:

Link: https://aescan-testnet.prd.aepps.com/accounts/ak_Wtx5SMXBcZcCGzxeuFybdsMxNfD142ordeFWDCrrpTWbcBkfB

Context information

application version:
device:
browser:
operating system:

Steps to reproduce

Firefox gives different CSP errors in the console.

What is expected?

What is actually happening?

A state channels page should be visible with a paginated table containing the following columns and total records:

Note: Last Known Round can be grouped with On-Chain Updates in a single column called "Updates" if not enough space is available.

No filters should be visible here but we can check if it's possible to filter open and close state channels.

Page anatomy should be similar to https://aescan.prd.aepps.com/contracts and the table content is similar to the State Channels table present at the bottom of https://aescan.dev.aepps.com/

Allow search by nm_ hash in the search bar.

The endpoint is not existent yet. Once implemented we can add the counter UI to tokens page

Tracking aeternity/ae_mdw#1255

A total amount of active state channels chart should be displayed in the state channels page.

A tab called “Events” should be visible in the token details page.
A paginated table with the following data should be visible in the tab:

• Hash
• Date
• Name (possible values Mint, Burn, Transfer, Allowance or N/A if the event is custom)
• Data (have a look at the possible cases below or N/A if the event is custom)

This table should be populated using the logs endpoint, example: https://mainnet.aeternity.io/mdw/v2/contracts/logs?contract=ct_7UfopTwsRuLGFEcsScbYgQ6YnySXuyMxQWhw6fjycnzS5Nyzq

The data column can be populated only with known AEX-9 events (Mint, Burn, Transfer, Allowance):

• Mint: arg1 (account address) [chip with arg2] (value)
• Burn: arg1 (account address) [chip with arg2] (value)
• Transfer: arg1 (account address) --> arg2 (account address) [chip with arg3]
• Allowance: arg1 (account address) --> arg2 (account address) [chip with arg3] (value)

Note: right now all args are decoded and mdw is implementing this new parameter to encode them:
https://staging.mdw.mainnet.aeternity.io/mdw/v2/contracts/logs?contract=ct_7UfopTwsRuLGFEcsScbYgQ6YnySXuyMxQWhw6fjycnzS5Nyzq&aexn-args=true
For development purposes we can use the staging endpoint and fix it once the mdw version containing this feature will be deployed.

All table headers should have the same capitalization.

Columns:

• Hash: in some cases we won’t have any tx-hash, e.g. AENS expiration won’t have any tx-hash, the same for Beneficiary reward
• Date
• Type
• Activity
• Data

Endpoint: GET /v2/accounts/:id/activities

Please describe the problem that your request should resolve.

Implement in the token details information on how many tokens can be minted. Some are limited, some are not.

Describe the solution you'd like

Hopefully it can be easily fetched from the contract information but that requires some research

Is it already possible to achieve the same outcome in any other way? If so, how?

Not sure

Display hints on name details page, including special pointers and custom pointers.

Display hints on account details page

A new tab should be visible in the state channels page called "Transactions".
It should have the same structure of the transactions page but it should just display transactions related to the state channel.

Sample anatomy: https://aescan.prd.aepps.com/transactions?txType=channel_withdraw

Verify that Plausible is tracking from desired stages and domains, and is using company credentials.
Verify that Sentry is tracking from desired stages and domains, and is using company credentials.
Verify the page is properly indexed by the search engines and sitemap is recognized.

Take new design typo variables and makes CSS reusable and remove quick wins.

Spacing between tabs and "There is no data available" messages is inconsistent.

Most of the tables are having a lot of common code e.g. AuctionsPanel.vue and NamesPanel.vue. Perhaps it would be nice to create a reusable component and reduce duplication.

Display hints on contract page details.

Please describe the problem that your request should resolve.

Some of the fetch requests on the client-side are executed even though the data has been already resolved on the server-side and provided for the client in the application state, It's because lack of return value in handlers of useAsyncData or lack of useAsyncData at all. Would be nice to improve it for hydration performance.

Describe the solution you'd like

As above

Is it already possible to achieve the same outcome in any other way? If so, how?

Yeah, but useAsyncData is the native, recommended way.

Additional context

We used a temporary workaround because we could not wait for MDW fix

Once this aeternity/ae_mdw#1244 will be merged and deployed we can revert workaround

Seems like does not belong here. It’s present for more entities.

Tables: display block height + date

Detail pages: separated rows (block height + date)
Also check name of detail pages “Date” or “Time” row.

Remove “Current keyblock" from transactions table.

A paginated table should be visible with the following columns:

• Oracle ID
• Registered at
• Expiration
• Query fee
• Total queries (nice to have)

Oracles should be ordered by mostly used.

A filter should be visible with the following options:

• Active
• Expired

A state channel details page should be visible with a "Details" panel and the following rows:

• State Channel id (copyable hash): ch_22SfHdn...Ud
• Status (Open / Close): Open
• Create transaction: th_JBqeBk1...XE
• Initial amount: 10 AE
• Initiator: ak_21A27UV...7E
• Responder: ak_gvxNbZf...Gc
• On chain updates: 1
• Last known round: 9
• AE locked: 10 AE
• Last updated: 761456 - 2 days ago
• Last TX type: ChannelCreateTx
• Middleware link

Note: initial amounts and create transaction should be displayed. Amounts should be checked to make sure they are updated and do not refer to initial amounts (responder_amount and initiator_amount).

Create transaction can be retrieved using the txs endpoint.
https://mainnet.aeternity.io/mdw/v2/txs?channel=ch_22usvXSjYaDPdhecyhub7tZnYpHeCEZdscEEyhb2M4rHb58RyD&direction=forward
BUT, this will not work for channels that were created on contract calls

After implementing state channels the search bar should allow search by state channel hash.

A tab called “Events” should be visible in the oracle details page.

A paginated table with the following data should be visible in the tab:

• Query Tx
• Queried At
• Respond Tx
• Respond At
• Status

Status: Response pending, Response available, Response expired, Query timed out (should be calculated based on the TTL)

The table should display additional data based on two cases:

1 - Query sent, no response sent

• Query id
• Query fee
• Query TTL

2 - The query has a response

• Query id
• Query fee
• Query
• Response
• Response TTL

A paginated table should be visible with the following columns:

• Image + Symbol
• Name
• Hash (contract)
• Amount
• A filter should be added to display Listed / All tokens.
• Default option: Listed

Switch navigation to add Tokens page first.

A new page should be created with oracle details.
The details panel should display the following data:

• Copyable oracle id
• Registered at (height + date)
• Last extended (height + date)
• Last query (height + date)
• Expires at (height + date)
• Query fee
• Query format
• Query response
• Creator
• Total queries

All transaction types in transaction tables should have hints to better explain the transaction and the generic "data" column.
Hints should be added in the "Type" cell.

• Remove labels from chips and explain every chip in tooltip
  

A chart to display the total value locked of a state channel should be displayed in the state channel page.

• Add browser info
• Tech update
• Check code conventions

It is possible to get rid of all API calls in the dashboard except of /v2/deltastats which provides beneficiary reward and dev reward.

Feature was requested from MDW. Once implemented we can use balance directly from listing response

Tracking aeternity/ae_mdw#1256

A tab called “Holders” should be visible in the token details page.
A paginated table with the following data should be visible in the tab:

• Account
• Amount
• Percentage

Tables should be expanded and not have blank space on the right side.

Steps to reproduce:

• Use an wallet with GAMeta transactions
• Select GAMeta from the list

GAMeta transactions are not displayed.

It’s fixed, waitng for DB resync.

Once we will see non-empty array here, its resoled

https://mainnet.aeternity.io/mdw/v2/txs?direction=backward&limit=10&account=ak_2Bwyd2yaNF7SaguZ19TyxyRpa5ep3WW1mR27tHM3jcgffGgf81&type=ga_meta

Implement a sitemap for implemented pages.
It probably makes sense to generate the sitemap only in the production build (no dev mode).

Acceptance criteria:

• æScan exposes sitemap.xml, which contains links to all available pages
• The sitemap file doesn’t get built in development mode (yarn dev)
• The sitemap file is built automatically based on routes defined in the Vue Router config

After implementing oracles, the search bar should be adjusted to work with oracles.

Please describe the problem that your request should resolve.

Implement hints for the token details page including a warning about the value and market cap being only theoretical. Due to how the price is calculated (comparison of two reserves), somebody can artificially inflate the price of a worthless token.
Events data can be explained as generic.

Describe the solution you'd like

Probably hint messages showing in popup messages after clicking hint icons

Is it already possible to achieve the same outcome in any other way? If so, how?

No

Migrate aepp sdk to 13.0.0 https://github.com/aeternity/aepp-sdk-js/blob/develop/docs/CHANGELOG.md#1300-2023-04-06

Account details display uncorrect amount of total transactions when filtered in the table.

Tracking aeternity/ae_mdw#1236

Keyblocks and microblocks in the dashboard can be dragged using the mouse cursor.

Display the time to react before a State Channels closes in the state channel details page. For example this could be useful for "ChannelCloseSoloTx" transactions.

This should be implemented after #10.

Account activities tab should be the default first tab.