Announcing the tables deprecation on Indexer for Explorer #351
Replies: 3 comments 6 replies
-
FYI we decided to give the community a little more time to migrate. The estimated deprecation date is after April 1st. |
Beta Was this translation helpful? Give feedback.
-
Thank @telezhnaya and @khorolets for the reply, Here is an example from Pagoda, We made many transactions to this address yesterday, and till now Pagoda didn't reflect any of them. The result looks like this: It didn't reflect incoming FT transfers. It only shows IN and OUT Near transfers and only OUT FT transfers. Nonetheless, the transactions took almost 2 hours to appear on the explorer. Our use case is simple, We have a multichain wallet for micro payments. It's crucial to show the user the transaction history and timely receipts for their transfers on the official explorer as they will use it as proof of payment in their accounting. Thanks |
Beta Was this translation helpful? Give feedback.
-
Here is another response from Pagoda b4322d6ed356b5f2c10db72b7632e17c9d5f7d420a80f06fe751b8dfaa6b38b5 It lacks transaction_id, receipt_id, new_owner, old_owner, and token_contract_address. {
"history": [
{
"event_index": "16750195133876989160000003001000006",
"involved_account_id": "8ab350cd7fc354c3f1f241fd19d9e1c8b16c8b38ce6ba6abb63300fb67104c3b",
"delta_balance": "-1020000000000000000",
"balance": "840000000000000000",
"cause": "TRANSFER",
"status": "SUCCESS",
"metadata": {
"name": "SWEAT",
"symbol": "SWEAT",
"icon": "data:image/svg+xml,%3Csvg viewBox='0 0 100 100' fill='none' xmlns='http://www.w3.org/2000/svg'%3E%3Crect width='100' height='100' rx='50' fill='%23FF0D75'/%3E%3Cg clip-path='url(%23clip0_283_2788)'%3E%3Cpath d='M39.4653 77.5455L19.0089 40.02L35.5411 22.2805L55.9975 59.806L39.4653 77.5455Z' stroke='white' stroke-width='10'/%3E%3Cpath d='M66.0253 77.8531L45.569 40.3276L62.1012 22.5882L82.5576 60.1136L66.0253 77.8531Z' stroke='white' stroke-width='10'/%3E%3C/g%3E%3Cdefs%3E%3CclipPath id='clip0_283_2788'%3E%3Crect width='100' height='56' fill='white' transform='translate(0 22)'/%3E%3C/clipPath%3E%3C/defs%3E%3C/svg%3E%0A",
"decimals": 18
},
"block_timestamp_nanos": "1675019513387698916",
"block_height": "84077473"
},
{
"event_index": "16750190831445089700000003001000000",
"involved_account_id": "8ab350cd7fc354c3f1f241fd19d9e1c8b16c8b38ce6ba6abb63300fb67104c3b",
"delta_balance": "-1000000000000000000",
"balance": "1860000000000000000",
"cause": "TRANSFER",
"status": "SUCCESS",
"metadata": {
"name": "SWEAT",
"symbol": "SWEAT",
"icon": "data:image/svg+xml,%3Csvg viewBox='0 0 100 100' fill='none' xmlns='http://www.w3.org/2000/svg'%3E%3Crect width='100' height='100' rx='50' fill='%23FF0D75'/%3E%3Cg clip-path='url(%23clip0_283_2788)'%3E%3Cpath d='M39.4653 77.5455L19.0089 40.02L35.5411 22.2805L55.9975 59.806L39.4653 77.5455Z' stroke='white' stroke-width='10'/%3E%3Cpath d='M66.0253 77.8531L45.569 40.3276L62.1012 22.5882L82.5576 60.1136L66.0253 77.8531Z' stroke='white' stroke-width='10'/%3E%3C/g%3E%3Cdefs%3E%3CclipPath id='clip0_283_2788'%3E%3Crect width='100' height='56' fill='white' transform='translate(0 22)'/%3E%3C/clipPath%3E%3C/defs%3E%3C/svg%3E%0A",
"decimals": 18
},
"block_timestamp_nanos": "1675019083144508970",
"block_height": "84077135"
}
],
"block_timestamp_nanos": "1683186468620591882",
"block_height": "91063703"
} |
Beta Was this translation helpful? Give feedback.
-
Hey there,
We run Indexer for Explorer for more than 2 years. All this time we collect the data and serve it to all our users.
We feel responsible for the projects depending on Indexer for Explorer. Each time we've chosen saving the backward compatibility over any breaking improvements.
Unfortunately, we need to admit we can't scale the current Postgres solution infinitely. Due to the size of some tables and spikes in the NEAR blockchain transaction numbers, the Explorer Database starts to lag from the tip of the network, affecting all Explorer users.
As a first compatibility-breaking step for solving this problem, we plan to deprecate 2 tables:
account_changes
andassets__fungible_token_events
.What does table deprecation mean?
Starting from March 1st, 2023, we will no longer collect the new data for
account_changes
andassets__fungible_token_events
. The previous historical data will become unavailable as well.The source code for these tables will be still available but hidden under the feature flags. We do not plan to support these features further.
What are the workarounds?
Use Enhanced API! It has much more features and a friendlier API.
Just a part of the highlights: for FTs, we cover legacy tokens such as
aurora
orwrap.near
. We also show the transaction status together with the transfer info. Finally, we provide you with absolute balances. For native balance, we give more detailed information about any balance changes that may ever occur.You are still able to run Indexer For Explorer on-premise and continue collecting all the data you want. You need to switch on the corresponding feature flags for that:
cargo build --release --features "account_changes fungible_token_events"
How to migrate to the new solution?
We apologize for any inconvenience. Our main goal is to provide the community with accurate data with low latency access.
Beta Was this translation helpful? Give feedback.
All reactions