Skip to content
This repository has been archived by the owner on May 19, 2023. It is now read-only.

fix: makes domain name sha3 to hex w/o lead 0s #96

Merged
merged 3 commits into from
May 14, 2020

Conversation

jurajpiar
Copy link
Member

The rns event processor stores token ids without leading zeroes, using utility numberToHex.
This causes an issue when wanting to compare the sha3 of a search term (for searching domain by name) with the stored tokenIds.
For quick resolution I use the numberToHex function to create the same hex string format for the queries. This seems to be an unnecessary computation but we can fix that in the refactor.

@jurajpiar jurajpiar added bug Something isn't working P2 - Medium labels May 14, 2020
@jurajpiar jurajpiar requested a review from vojtechsimetka May 14, 2020 09:29
@jurajpiar jurajpiar force-pushed the hotfix/tokenIdWLeading0s branch from d679e03 to 94538c8 Compare May 14, 2020 09:33
Copy link
Contributor

@julianmrodri julianmrodri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Its good to me. We can tackle in the refactor of the section.

@AuHau AuHau merged commit cd5aa77 into master May 14, 2020
@AuHau AuHau deleted the hotfix/tokenIdWLeading0s branch May 14, 2020 12:20
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working P2 - Medium
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants