### Introduction to SPO Budz in SpaceBudz Universe
In the dynamic world of SpaceBudz, a unique group of characters known as the SPO Budz stands out for their special role and significance. These 30 custom-designed Budz are more than just digital collectibles; they are a symbol of appreciation and recognition within the Cardano blockchain community.
**Celebrating Decentralization and Stake Pool Operators**\
Each SPO Bud is equipped with a laptop and modem, essential tools for any stake pool operator (SPO) in the blockchain universe. What makes them truly special is the inclusion of individual SPO logos on their laptops, a nod to the unique identity and contribution of each selected stake pool operator in the network.
**A Token of Gratitude and Support**\
These Budz were crafted and distributed as a gesture of gratitude towards the stake pool operators. By gifting these to 30 SPOs, the project celebrated their pivotal role in maintaining Cardano’s decentralization and highlighted the importance of their work in sustaining the network.\
\
An overview of all SPO pools and their Spacebud ID
| SpaceBudz ID | SPO Name |
| ------------ | ------------ |
| 3 | FROG |
| 27 | GROW |
| 113 | CROWN |
| 313 | ATADA |
| 344 | KAIZN |
| 351 | USA01 |
| 388 | Emurgo/Yoroi |
| 432 | DAN |
| 519 | SMAUG |
| 591 | MASTR |
| 904 | DIGI |
| 964 | VEGAS |
| 987 | BERRY |
| 1020 | CARDs |
| 1043 | NUTS |
| 1064 | BUFFY |
| 1106 | BLOCK |
| 1157 | BLOOM |
| 1169 | BUZZ |
| 1319 | PEACE |
| 1355 | HRMS |
| 1378 | HUSKY |
| 1421 | Charles |
| 1438 | SWAG |
| 1481 | LOVE |
| 1502 | SKY |
| 1585 | BABEL |
| 1597 | 21ADA |
| 1635 | BCSH |
| 1657 | ANGEL |
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://spacebudz.gitbook.io/spacebudz/the-collection/the-spo-specials.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.