Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Wrong random_hasHashOnion response when hash onion is used up #8327

Closed
Tracked by #7210
bobanm opened this issue Apr 2, 2023 · 0 comments · Fixed by #8328
Closed
Tracked by #7210

Wrong random_hasHashOnion response when hash onion is used up #8327

bobanm opened this issue Apr 2, 2023 · 0 comments · Fixed by #8328
Assignees
@bobanm
Labels
framework type: bug
Milestone
Sprint 92

Comments

@bobanm
Copy link
Contributor

bobanm commented Apr 2, 2023

Expected behavior

When a hash onion is used up, random_hasHashOnion endpoint should return hasSeed value as false

Actual behavior

When a hash onion is used up, random_hasHashOnion endpoint returns hasSeed value as true

Steps to reproduce

  1. Set a new hash onion.
  2. Wait until it is used up.
  3. Invoke random_hasHashOnion. Response hasSeed property will be true.
@bobanm bobanm self-assigned this Apr 2, 2023
@bobanm bobanm mentioned this issue Apr 2, 2023
Merged
@bobanm bobanm changed the title When a hash onion is used up, random_hasHashOnion endpoint should return hasSeed value as false Wrong random_hasHashOnion response when hash onion is used up Apr 3, 2023
@Madhulearn Madhulearn added this to the Sprint 92 milestone Apr 3, 2023
@Madhulearn Madhulearn mentioned this issue Apr 3, 2023
Closed
@github-project-automation github-project-automation bot moved this from Backlog to Done in Lisk SDK Version 6.0.0 Apr 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bobanm bobanm

Labels
framework type: bug
Projects
None yet
Milestone
Sprint 92
Development

Successfully merging a pull request may close this issue.

Fix random_hasHashOnion response when hash onion is used up LiskArchive/lisk-sdk
2 participants
@bobanm @Madhulearn