# Blocktributes

A new way to view community voted traits, such as punks and patoshi blocks. This could be open to debate, open to change, and will always come from the community. These 22 (open to change by voting) attributes and traits, will be forwarded to marketplaces, in the hopes that they will add them to their listings, in the hope to better view bitmaps as a variety of not just text inscriptions, but true Bitcoin ordinal art.

"We shall perform quarterly polls on Twitter, with a duration of 30days, during which community members can make suggestions and actively participate."

Title: Blocktributes: A Bitcoin Standard for Bitmap with  Community-Voted Attributes

Abstract: Blocktributes is a proposed standard for bitmap within the Bitcoin ecosystem. It aims to enhance the marketplace experience by introducing  community-voted attributes, known as traits, that can be associated with individual blocks. These traits serve as unique identifiers and add value to the marketplace by providing additional information and aesthetic appeal. The following are the  community-voted attributes to be included in the Blocktributes standard:

1. Special Numbers (123456, 777, 888,...): Blocks with special numbers known for their objectively nice-looking patterns.
2. Palindrome : Blocks that exhibit palindromic characteristics in their numerical representation.
3. Billionaire: Blocks associated with substantial Bitcoin holdings or transactions of significant value.
4. Patoshi (Blocks mined by Satoshi): Blocks that can be attributed to Satoshi Nakamoto, the pseudonymous creator of Bitcoin.
5. Leap Block: Blocks that introduce new functionalities, advancements, or significant changes within the Bitcoin ecosystem.
6. Pre-Blockout multiple inscriptions: Blocks containing early versions or experimental features prior to the implementation of blockout multiple inscriptions.
7. Single Transaction Block: Blocks that consist of only a single transaction.
8. Sub-100: Blocks with a total number of transactions < 100.
9. Sub-1k: Blocks with a total number of transactions < 1,000.
10. Sub-10k: Blocks with a total number of transactions < 10,000.
11. Sub-25k: Blocks with a total number of transactions < 25,000.
12. Sub-50k: Blocks with a total number of transactions < 50,000.
13. Sub-100k: Blocks with a total number of transactions < 100,000.
14. Messages From the Miners MFTM: Blocks containing hidden messages or ASCII art added by the miners.
15. Punk: Blocks associated with unique punk-inspired artwork or design elements.
16. Narrative Blocks: Silk Road, Transaction's that are historic, ordinals dates
17. Transaction heights/ID
18. difficulty adjustment and halving blocks, following the same rodarmor theory for sats
19. soft fork / hard fork blocks (which contain leap blocks you described but also include some other edge cases)
20. special or rare sats (vintage, block78, block9, uncommons, etc)
21. Fibonacci&#x20;
22. Orphan Blocks (dropped by the miners)

By incorporating these attributes into the Blocktributes standard, marketplace participants can easily identify and trade blocks based on their desired traits. The attributes are decided through community consensus, ensuring a democratic and inclusive process. Blocktributes aims to create a vibrant and diverse marketplace experience, highlighting the rich history and unique characteristics of individual Bitcoin blocks.

Let's Start with these for now and always be open to debate, and always know that this is an evolving standard but should be always voted on, and from the community.

By 8 Bit

For Bitmap,  Forever <3

Dm me to add yours! @8bitsats&#x20;

Contributions by:\
@0xElProfessor @contnfaces @solkekw @BR\_CAA @chainracingclub<3


---

# 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://8bit-1.gitbook.io/blocktributes/blocktributes.md?ask=<question>
```

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.