-
Notifications
You must be signed in to change notification settings - Fork 304
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.
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
Cache supply adjustment transactions in explorer codebase #139
Comments
@ericlwilliams @mvines these transactions aren't available anymore from the API. Do you have the info handy? |
@jstarry I'll share a doc with you on slack. |
That's surprising because:
and those transactions aren't that old |
For example:
|
The missing transaction history were a side-effect of the mainnet-beta restart and the lack of solana-labs/solana#10358 on v1.1. We do in fact have these transactions in the RPC node ledger still |
@mvines I tried using the ledger-tool to print slot 10440804 and I get a blockstore error:
Did anything change since you queried earlier? |
Nvm, I see the conversation in #sdk now! |
Problem
Currently, explorer transaction data persists for ~30 days. We would like to persist transactions related to the recent supply adjustment.
Proposed Solution
Cache the following six transactions in explorer codebase for persistent retrieval.
uQf4pS38FjRF294QFEXizhYkZFjSR9ZSBvvV6MV5b4VpdfRnK3PY9TWZ2qHMQKtte3XwKVLcWqsTF6wL9NEZMty
DYrfStEEzbV5sftX8LgUa54Nwnc5m5E1731cqBtiiC66TeXgKpfqZEQTuFY3vhHZ2K1BsaFM3X9FqisR28EtZr8
3bLx2PLpkxCxJA5P7HVe8asFdSWXVAh1DrxfkqWE9bWvPRxXE2hqwj1vuSC858fUw3XAGQcHbJknhtNdxY2sehab
3fE8xNgyxbwbvA5MX3wM87ahDDgCVEaaMMSa8UCWWNxojaRYBgrQyiKXLSxcryMWb7sEyVLBWyqUaRWnQCroSqjY
5PWymGjKV7T1oqeqGn139EHFyjNM2dnNhHCUcfD2bmdj8cfF95HpY1uJ84W89c4sJQnmyZxXcYrcjumx2jHUvxZQ
5K4KuqTTRNtzfpxWiwnkePzGfsa3tBEmpMy7vQFR3KWFAZNVY9tvoSaz1Yt5dKxcgsZPio2EsASVDGbQB1HvirGD
The text was updated successfully, but these errors were encountered: