8000 Fix: Coretime sale page -> purchase transactions subscan url is constructred with start and end blocks = 0 by piggydoughnut · Pull Request #11360 · polkadot-js/apps · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Fix: Coretime sale page 8000 -> purchase transactions subscan url is constructred with start and end blocks = 0 #11360

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

Merged
merged 2 commits into from
Mar 6, 2025

Conversation

piggydoughnut
Copy link
Contributor
@piggydoughnut piggydoughnut commented Mar 5, 2025

Addresses #11262

I updated the subscan Sale Purchase Transactions query to use date instead of blocks.
It is not possible to correctly calculate historical Coretime blocks for start and end of the sale due to the regions not being 201,600 blocks long, they deviate from 2,212 to 1,417 blocks in length.

Reproduce steps:

  1. Relay chain -> Network -> Coretime
  2. Sale tab
  3. Choose sale number in the history select at the bottom
  4. Subscan links for purchase and Renewal should point to correct time intervals.
Screenshot 2025-03-05 at 9 48 30 PM

@piggydoughnut piggydoughnut changed the title Fix: query subscan blocks gives 0 blocks Fix: Coretime sale page -> purchase transactions subscan url is constructred with start and end blocks = 0 Mar 5, 2025
@piggydoughnut piggydoughnut merged commit ef69801 into master Mar 6, 2025
5 checks passed
@piggydoughnut piggydoughnut deleted the fix/subscan-query-sales-purchases branch March 6, 2025 23:01
@polkadot-js-bot
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@polkadot-js polkadot-js locked as resolved and limited conversation to collaborators Mar 8, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0