Cardano CLI V10.13.1 Bug: Wrong KeyHashHex Output

Nov 28, 2025 by Alex Johnson 50 views

Cardano CLI v10.13.1 Bug: Incorrect keyHashHex Output in `query stake-address-info`

If you're a Cardano user who relies on the command-line interface (CLI) for managing your stake and delegations, you might have encountered a rather significant bug in version 10.13.1. This issue specifically affects the output of the query stake-address-info command, leading to an incorrect keyHashHex value. In this article, we'll dive deep into what this bug entails, why it's crucial to be aware of it, and what the correct output should look like. Let's explore this technical hiccup in detail, ensuring you're well-informed and can navigate it effectively.

Understanding the Issue

The bug manifests when you use the cardano-cli version 10.13.1 to query stake address information. Specifically, the keyHashHex field within the voteDelegation section of the output provides an incorrect value. Instead of displaying just the hash in hexadecimal format, it outputs the entire CBOR (Concise Binary Object Representation) format. This discrepancy is similar to a previous bug reported concerning the CIP129 format, indicating a recurring pattern in how the CLI handles certain data outputs. Let's delve deeper to understand the implications and the technical nuances behind this issue.

When calling cardano-cli 10.13.1 for the stake-address-info, the output is like:

[
 {
 "address": "stake_test1urqntq4wexjylnrdnp97qq79qkxxvrsa9lcnwr7ckjd6w0cr04y4p",
 "govActionDeposits": {},
 "rewardAccountBalance": 200000000000,
 "stakeDelegation": {
 "stakePoolBech32": "pool1rdaxrw3722f0x3nx4uam9u9c6dh9qqd2g83r2uyllf53qmmj5uu",
 "stakePoolHex": "1b7a61ba3e5292f34666af3bb2f0b8d36e5001aa41e235709ffa6910"
 },
 "stakeRegistrationDeposit": 2000000,
 "voteDelegation": {
 "keyHashBech32": "drep1ytwmwvtd0a8lr45ssner2tjxzv5y8q03w3606yeald9mdmgmwecja",
 "keyHashHex": "8200581cddb7316d7f4ff1d69084f2352e4613284381f17474fd133dfb4bb6ed"
 }
 }
]

In the JSON output above, the keyHashHex field is supposed to represent the hexadecimal representation of the key hash. However, due to the bug, it includes the entire CBOR format, which is a more complex binary serialization format. This deviation from the expected output can lead to confusion and errors in applications or scripts that rely on this data. It's crucial to identify and address these discrepancies to maintain the integrity of the information being processed. Let’s move forward to the next part of our article, where we'll discuss the consequences of this bug and its implications for users and developers within the Cardano ecosystem.

Impact and Implications

The incorrect output of the keyHashHex value can have significant implications for users and developers working within the Cardano ecosystem. When the CLI returns the entire CBOR format instead of just the hash, it disrupts the expected data structure. This disruption can cause applications and scripts that rely on parsing this data to fail or produce incorrect results. For instance, if you're building a tool that monitors stake delegations or automates governance actions, this bug could lead to misinterpretations of the stake delegation information. Imagine a scenario where a script designed to analyze stake delegations fails because it cannot correctly parse the keyHashHex value. This could lead to incorrect reports, missed opportunities, or even financial losses if critical actions are not executed properly. It's a ripple effect that touches various aspects of Cardano's operational ecosystem, emphasizing the importance of reliable CLI tools.

Moreover, the wrong keyHashHex can hinder accurate data analysis and reporting. If the data is being used for auditing purposes, or for tracking the distribution of stake across different pools and delegators, the presence of the full CBOR format in place of the hash can complicate the analysis. The need to extract the hash from the CBOR format adds an extra layer of complexity, potentially leading to errors if not handled correctly. Therefore, it's essential to recognize the severity of this issue and take necessary steps to ensure that you're working with accurate data. In the next section, we will look at what the correct output should look like, enabling you to better identify and work around this bug.

Correct Output

To better understand the bug and how to identify it, it's essential to know what the correct output of the keyHashHex field should look like. Ideally, the keyHashHex field should only contain the hexadecimal representation of the key hash. In the example provided earlier, the correct output should be: ddb7316d7f4ff1d69084f2352e4613284381f17474fd133dfb4bb6ed. This is the actual hash value, without any additional formatting or encoding. When you run the query stake-address-info command, it's crucial to verify that the keyHashHex field matches this format, consisting solely of the hexadecimal hash. If you observe a longer string that appears to be in CBOR format (as shown in the initial example), you've likely encountered the bug. Recognizing this discrepancy is the first step in mitigating its impact and ensuring that you're working with reliable data. Now, let's delve into potential workarounds and solutions to navigate this issue effectively.

The importance of recognizing the correct output format cannot be overstated, especially when you're dealing with scripts and applications that automate processes based on stake delegation information. If your tools are expecting a simple hexadecimal hash and receive a CBOR-encoded value instead, they are likely to fail or produce incorrect results. This could lead to misreporting of stake delegations, failed transactions, or other undesirable outcomes. Therefore, understanding the expected output format is a critical aspect of ensuring the reliability and accuracy of your interactions with the Cardano blockchain. Now that we have a clear picture of the issue and the expected output, let's discuss potential workarounds and solutions in the next section.

Workarounds and Solutions

Dealing with the bug in cardano-cli v10.13.1 requires a practical approach to ensure your operations remain unaffected. One immediate workaround is to use an older version of the CLI that doesn't exhibit this issue. If feasible, downgrading to a version prior to 10.13.1 can provide a temporary fix, allowing you to obtain the correct keyHashHex output. However, this might mean missing out on other features and improvements included in the newer version. Another approach involves post-processing the output to extract the correct hash from the CBOR format. This can be achieved using scripting tools that can decode the CBOR data and isolate the hexadecimal hash. For instance, you could use command-line tools like jq or write a script in Python or other languages to parse the JSON output and extract the relevant hash value. This method requires additional effort but allows you to continue using the latest CLI version while mitigating the bug's effects. Let's examine these workarounds in more detail to help you choose the most appropriate solution for your needs.

Furthermore, it's crucial to stay informed about updates and patches released by the Cardano development team. Keep an eye on official announcements and release notes to determine when a fix for this bug is available. Upgrading to the patched version as soon as it's released is the most effective long-term solution. Additionally, consider contributing to the Cardano community by reporting issues and sharing your experiences. This collaborative effort helps improve the software and ensures that bugs are addressed promptly. By combining these workarounds with proactive monitoring and community engagement, you can minimize the impact of this bug and maintain the integrity of your Cardano operations. Remember, the Cardano ecosystem thrives on collaboration and shared knowledge, so your contributions are valuable in ensuring its robustness and reliability.

Conclusion

In conclusion, the bug affecting the keyHashHex output in cardano-cli v10.13.1's query stake-address-info command is a notable issue that can disrupt data processing and analysis for Cardano users and developers. Understanding the nature of this bug, its implications, and the correct output format is crucial for mitigating its impact. By employing workarounds such as using older CLI versions or post-processing the output, you can continue to work effectively while waiting for an official patch. Staying informed about updates from the Cardano development team and actively participating in the community are also vital steps in ensuring a smooth and reliable experience within the Cardano ecosystem.

Remember, the strength of the Cardano community lies in its collaborative approach to problem-solving and continuous improvement. By sharing your experiences and reporting issues, you contribute to the overall health and robustness of the platform. Keep an eye on official announcements and release notes for updates, and don't hesitate to leverage community resources for support and guidance. Together, we can navigate these challenges and continue to build a resilient and innovative blockchain ecosystem. For further information and updates, consider visiting the official Cardano Foundation website. This will provide you with the latest news, resources, and community discussions related to Cardano and its ongoing development.