Skip to content
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

RoundID and Price does not update If initial_height >= startBaseBlock*(Integer)+Interval + 1 in genesis file #128

Closed
4 tasks
cloud8little opened this issue Jul 10, 2024 · 1 comment
Assignees

Comments

@cloud8little
Copy link
Contributor

cloud8little commented Jul 10, 2024

Summary of Bug

Set startBaseBlock and initial_height in the genesis file, startBaseBlock =20, when initial_height<31, the price and round Id update successfully.
when initial_height >=31, price and roundId does not update after price feeding.

Version

PR #83 + PR #86 (7cd1cfd) + develop branch

Steps to Reproduce

  1. Initialize an single validator node with genesis file start_base_block set as 20, interval as 10, for example, and initial_height as >=31, and the price feeder miss price feeding for 31~33.
        "token_feeders": [
          {
            "token_id": "0",
            "rule_id": "0",
            "start_round_id": "0",
            "start_base_block": "0",
            "interval": "0",
            "end_block": "0"
          },
          {
            "token_id": "1",
            "rule_id": "1",
            "start_round_id": "1",
            "start_base_block": "20",
            "interval": "10",
            "end_block": "0"
          }
        ],
  1. query oracle show-prices function, after the price feeder sumbit create-price message on block 41. the round ID and price is not updated.
    exocored q oracle show-prices 1
prices:
  next_round_id: "2"
  price_list:
  - decimal: 0
    price: ""
    round_id: "0"
    timestamp: ""
  - decimal: 0
    price: ""
    round_id: "1"
    timestamp: ""
  token_id: "1"

Screenshots

Additional context


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
Copy link

This issue is stale because it has been open 45 days with no activity. Remove Status: Stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants