> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/9.0sp1/archive/ida-home-contest.md).

# IDA Home Contest

## Pimp My IDA: Vote result

Firstly, we would like to thank everyone who participated in our Pimp my IDA contest and those who contributedby voting. You all helped make this contest a huge success!

More than **60 photos** received, nearly **2000 votes** submitted — we are totally impressed by your talents, efforts and wholeheartedly thankful for your great interest in our ‘legendary’ IDA.

![Winner image](https://545602138-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FucByjS46IhJacH1pbIKC%2Fuploads%2Fgit-blob-e10d26a9a50e9c6222cc28e3bcd2a110094158de%2Fwinneris.jpg?alt=media) ![Winner image](https://545602138-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FucByjS46IhJacH1pbIKC%2Fuploads%2Fgit-blob-e263d7eeb0df20c4d867b80c8e81ac8a2f519089%2Fimg_9_large.jpg?alt=media)

Our special congratulations goes to **Michael Iline**! Michael created the image (thanks to the support of his [friend](https://www.fiverr.com/myxp01)), and received the highest number of votes. He has thus been crowned the winner! An [IDA Home](https://hex-rays.com/ida-home) License, Hex-Rays’ latest reverse engineering tool, is hence awarded to him. Congratulations, Michael!

[View all finalists and the vote results](/9.0sp1/archive/pimp-my-ida-vote-results.md)

Not winning this contest? No worries, stay tuned with Hex-Rays because there are many activities and contests coming soon!

Thanks again for making this contest successful — we hope to see you again soon!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hex-rays.com/9.0sp1/archive/ida-home-contest.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.