Weekly Review #2 - HiveCuba Dashboard

Hello everyone, we’re continuing to work on this project for the @hivecuba community. Despite some personal interruptions, we’re making steady progress.

Curation Section

We’re currently focused on the curation section to improve and streamline the curation experience by organizing content in more practical ways and grouping curation processes under specific functionalities.

Text Input for Voting

One of the first changes compared to the previous version of the system was replacing the voting power slider with a text input. The slider significantly slowed down the software during rendering, especially for voting power adjustments. A fixed-value text input (common for curator accounts) proved far more efficient.

Vote Button

In our previous post, we shared that our first step was to make the vote button functional. While this seemed simple, it came with minor complications.

PythonJavaScript/TypeScript.To ensure account security (and for potential future accounts), we needed to use existing Hive services to manage public/private keys. We chose @keychain for its ease of use, but faced a challenge: our system is built in , while @keychain only integrates with

After exploring unsatisfactory workarounds, we leveraged Streamlit (our Python library) to bridge the gap. Since the system renders locally via a web server, all components have a frontend layer. This allowed us to create a custom vote button component using Hive Keychain’s SDK.

Specifically, we used React combined with Material-UI (a visual component library) to design the interface.