LasticXYZ / LasticXYZ/LasticUI
[BUG] - Historic Polkadot Core Time Sale Prices are off by two decimals
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 14
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
In the core time sales for Polkadot cores, the reported sale price is off by two decimals.
To Reproduce
Steps to reproduce the behavior:
- Go to https://www.lastic.xyz/polkadot/bulkcore1
- Scroll down to 'Core Data'
- See Historic sales. For example, the very first core that was sold is reported to have sold for 0.69 DOT when it was in fact 69 DOT.
Expected behavior
I expected to see the correct price.
Screenshots
Desktop (please complete the following information):
- OS: Windows
- Browser: Chrome
- Version 129
Smartphone (please complete the following information):
Additional context
Note
Once you take on this PR paste a comment with your hand -> ✋ so that people know that someone is working on this issue.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the Polkadot core-time page at https://www.lastic.xyz/polkadot/bulkcore1 and inspect the Core Data section, especially Historic sales. Compare the displayed first sale price with the reported value of 69 DOT; done means historic Polkadot core sales show the correct price rather than 0.69 DOT.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100