Fixing a Small Bug in the CuteHIVE Proposal List: Baseline Proposal Display Logic

While recently browsing the proposal list in CuteHIVE Monitor, I noticed something unusual. As I was checking the current DHF proposals, I found that **two different proposals were simultaneously marked as "Baseline" proposals**. From the perspective of how the Hive Proposal System works, this clearly didn't look right. At any given time, there should only be **one true Baseline Proposal**—the proposal that determines the funding threshold for all other proposals.  ## How Did This Happen? After noticing the issue, I reviewed the logic that had originally been implemented in CuteHIVE. It turned out that the early version used a very simple rule: > Any Refund Proposal was treated and displayed as a Baseline Proposal. In most situations, this seemed reasonable because the actual Baseline Proposal is indeed a special type of Refund Proposal. However, once multiple Refund Proposals exist in the system, this approach starts to break down. As a result: - Every Refund Proposal received Baseline styling. - Multiple proposals could display a "Baseline" badge. - Users could not immediately identify which proposal was actually setting the funding threshold. Fortunately, this was only a **display issue** and did not affect any blockchain data. More importantly, the Support % calculations for all proposals were already based on the correct Baseline Proposal—the Refund Proposal with the highest vote total. Therefore, all calculations remained accurate. Even so, incorrect visual labeling can be misleading, so I decided to fix it.  ## What Is a Baseline Proposal? For anyone who is new to the Hive Decentralized Hive Fund (DHF), here's a quick explanation. In the Hive Proposal System, proposals do not automatically receive funding. Instead, proposals are ranked according to their net votes. To qualify for funding, a proposal must receive more support than the current Baseline Proposal. In most cases, the Baseline Proposal is a Refund Proposal that returns funds back to the DAO. In other words: - Proposals with more votes than the Baseline receive funding. - Proposals with fewer votes than the Baseline do not receive funding. You can think of the Baseline Proposal as the **funding threshold** for the entire DHF system.  ## The Fix To address this issue, I updated the proposal display logic in CuteHIVE Monitor. ### 🎯 More Accurate Baseline Detection The system now correctly identifies: **The highest-voted Refund Proposal that is actually being used as the funding threshold.** Only this proposal will receive: - The Baseline badge - The amber-colored background - The special visual highlighting This makes it immediately obvious where the current funding threshold is. ### 📊 Better Display of Other Refund Proposals Any additional Refund Proposals in the system will now: - Display a standard Refund badge - Be rendered like normal proposals - Show their actual Support % relative to the current Baseline This makes it easier to identify the true Baseline Proposal while still allowing users to see how other Refund Proposals are performing.  ## 🌐 Give It a Try! You can explore the latest version of **CuteHIVE Monitor DHF proposals** using the link below: 🔗 https://www.cutehive.com/proposals If you find CuteHIVE useful, feel free to leave your suggestions and feedback in the comments. Thank you for your continued support! 💖