Top Tweets for #RunicDigits

about 2 years ago

It might take 5 years, but spending a few bucks to etch a three digit #RunicDigits is probably worth it: https://t.co/vulDlyj9la

0

1

0

143

about 2 years ago

Some thoughts on Runeword Collections and #RunicDigits A Runeword Collection is any group of Runes tickers that people can agree are related. The first 10k example of this is the PUNK Runewords with notation in the PUNK•ZERO•ZERO•ZERO•ONE format (shoutout to @Bodega_Brat for his roman numeral PUNK numbering system, sure to make a comeback when the space has matured to his level). @NodeMonkes @lepuppeteerfou and @OnChainMonkey have also started minting Runeword Collections in this NAME•ZERO•ZERO•FOUR•DIGITS format, with the NodeMonkes leaps and bounds ahead of everyone else. Regardless of whether or not there is any value into minting these, there are some aspects that make this a lot of fun: 1. The ownership of a Runeword can be determined by either the inscription the Runeword is etched upon, or by majority ownership of the Runeword fungible tokens themselves. 2. Runewords are fair game for everyone. This means that artists can only ask that Runeword etchers choose the appropriate image for the Runeword. 3. Some Runeword Collections can’t be added onto after the fact: PUNK•ONE•ZERO•ZERO•ZERO•ZERO has no provenance. 4. Some Runeword Collections can be added onto after the fact: SIDS•LOGOS•ARTISTS could have provenance, if so decided. 5. The cheapest way to create a Runeword Inscription is to delegate it to an already existing inscription. And #RunicDigits specifically: 1. It’s obvious that if you remove the prefix for any set of digits that the natural set of numbers you can create as a Runeword in that manner is the ultimate Runeword Collection. These start at ZERO and end at NINE•NINE•SIX•SIX•SIX•SIX•SIX•SIX 2. Runic Digit PFPs are web3 token IDs without the need to be associated to any specific web3 project. You can use these token IDs to build a brand on-chain by delegating Runewords to this inscription ID. So I think right away people get tripped up on the obvious flaws of asking people to inscribe the correct artwork for a collection, and a great example of this can be found here: https://t.co/GxHjIJMh1m I also think the immediate response is to figure out how to prevent something like this, but hear me out I think it’s the best part of the whole space. I now have a set of these for various very early Runeword Collections etched with my PFP instead of the “appropriate” image. Regardless if these tokens are indexed for sale with other pieces of the Runeword Collection or not, 0529 as a token number itself is notated as special within that Runeword Collection. Another way this could be seen is as a badge of pride for the collection. Could you imagine if @punk6529 is permanently listed as one of the etchers of your Runeword Collection? Web3 influencers associated with token IDs in such a manner would be permanently recorded as important to helping that Runeword Collection fully etch. If you embrace that aspect of it, there is a PvP side of crypto that unlocks that we’ve never seen before where people are fighting for token IDs. Not necessarily to sell them, but to advertise their association to a project. And I just think that’s neat is all.

1

7

2

1

749

about 2 years ago

I propose this rule for #Runes PvP: #RunicDigits are fair game, if you can match your token ID that is great but not required. If you are inscribing any other PREFIX•DIGIT collections, just match the token IDs with your collection. You don't HAVE to follow it, everyone will just think you're a jerk if you're spamming the entire collection with your PFP. I dunno, maybe I'm wrong *shrug*.

1

0

219

about 2 years ago

#RunicDigits is etching now, many available 3-digit combos have been etched, and soon people will start snagging 4-digits. This is playing out a bit like ENS. A unique feature is that the ownership can be fractionalized if the owner burns their inscription. More info below 🧵 Abstract Runic Digits Collective is a consensus standard that allows anyone to claim one of the finite, naturally occurring numbers within the Runes protocol. The supply of the collection is capped by the Runes Protocol character limit. The ownership consensus mechanism outlined herein uniquely allows for trading of either fungible (rune) or non-fungible (inscription) assets. Collection Standard Runic Digits are represented in text format, with each digit spelled out. Padded zeros are NOT recognized, and, as a result, some of the lower Runic Digits will not be etchable for some time. 0 = ZERO 1 = ONE 2 = TWO 3 = THREE 4 = FOUR 5 = FIVE 6 = SIX 7 = SEVEN 8 = EIGHT 9 = NINE 10 = ONE•ZERO ... 9,999 = NINE•NINE•NINE•NINE (The final Runic Digit in the '10k' subcollection) ... 1,000,000 = ONE•ZERO•ZERO•ZERO•ZERO•ZERO•ZERO ... Ownership Consensus Mechanism (1) If an inscription was not attached to the Runic Digit when it was etched, then the owner of the Runic Digit is the individual that holds the largest percentage of the Runic Digit's rune. (2) If an inscription was attached to the rune when it was etched, and the inscription is located in the address '1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa', then ownership of the Runic Digit is fractionalized proportionally among the rune's holders. (3) If an inscription was attached to the rune when it was etched, and the inscription is NOT located in the address in (2) above, ownership of the Runic Digit is fractionalized proportionally among the rune's holders. Collection Display Recommendations for Marketplaces Inscriptions within the collection could have their display names in the format '###.rdc' to make browsing easier. For example, the inscription attached to ONE•ZERO•ZERO•ZERO•ZERO might be displayed as '10,000.rdc'. Filtering Recommendations for Marketplaces - Inscription type (Text, image, etc) - Satributes (Uncommon, Block 9-450x, etc) - Number of Digits. (Four and under is the Runic Digits '10k' collection) - Digit patterns. For example: repeat digits, sequential digits, palindromes, etc. - ...and more!

1

5

3

1

661

about 2 years ago

Everyone is minting out different derivatives now PUNK• MONKE• but the most pure version removes the leading descriptor. Since they are all a FFA anyway, the only provenance is in the number itself. #RunicDigits

about 2 years ago

Introducing RUNIC•DIGITS•COLLECTIVE. Runic Digits Collective is a consensus standard that allows anyone to claim one of the finite, naturally occurring numbers within the Runes protocol. The supply of the collection is capped by the Runes Protocol character limit. The ownership consensus mechanism outlined herein uniquely allows for trading of either fungible (rune) or non-fungible (inscription) assets. Collection Standard Runic Digits are represented in text format, with each digit spelled out. Padded zeros are NOT recognized, and, as a result, some of the lower Runic Digits will not be etchable for some time. 0 = ZERO 1 = ONE 2 = TWO 3 = THREE 4 = FOUR 5 = FIVE 6 = SIX 7 = SEVEN 8 = EIGHT 9 = NINE 10 = ONE•ZERO ... 9,999 = NINE•NINE•NINE•NINE (The final Runic Digit in the '10k' subcollection) ... 1,000,000 = ONE•ZERO•ZERO•ZERO•ZERO•ZERO•ZERO ... Ownership Consensus Mechanism (1) If an inscription was not attached to the Runic Digit when it was etched, then the owner of the Runic Digit is the individual that holds the largest percentage of the Runic Digit's rune. (2) If an inscription was attached to the rune when it was etched, and the inscription is located in the address '1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa', then the owner of the Runic Digit is the individual that holds the largest percentage of the Runic Digit's rune. (3) If an inscription was attached to the rune when it was etched, and the inscription is NOT located in the address in (2) above, then the owner of the Runic Digit is the individual that owns the inscription. Collection Display Recommendations for Marketplaces Inscriptions within the collection could have their display names in the format '###.rdc' to make browsing easier. For example, the inscription attached to ONE•ZERO•ZERO•ZERO•ZERO might be displayed as '10,000.rdc'. Filtering Recommendations for Marketplaces - Inscription type (Text, image, etc) - Satributes (Uncommon, Block 9-450x, etc) - Number of Digits. (Four and under is the Runic Digits '10k' collection) - Digit patterns. For example: repeat digits, sequential digits, palindromes, etc. - ...and more! Originating rune: https://t.co/NTMenWjuMU

5

23

8

9

10K

0

4

3

0

864

about 2 years ago

#RunicDigits delegated token match.

1

8

0

615

about 2 years ago

I see some #RunicDigits 👀

about 2 years ago

Introducing RUNIC•DIGITS•COLLECTIVE. Runic Digits Collective is a consensus standard that allows anyone to claim one of the finite, naturally occurring numbers within the Runes protocol. The supply of the collection is capped by the Runes Protocol character limit. The ownership consensus mechanism outlined herein uniquely allows for trading of either fungible (rune) or non-fungible (inscription) assets. Collection Standard Runic Digits are represented in text format, with each digit spelled out. Padded zeros are NOT recognized, and, as a result, some of the lower Runic Digits will not be etchable for some time. 0 = ZERO 1 = ONE 2 = TWO 3 = THREE 4 = FOUR 5 = FIVE 6 = SIX 7 = SEVEN 8 = EIGHT 9 = NINE 10 = ONE•ZERO ... 9,999 = NINE•NINE•NINE•NINE (The final Runic Digit in the '10k' subcollection) ... 1,000,000 = ONE•ZERO•ZERO•ZERO•ZERO•ZERO•ZERO ... Ownership Consensus Mechanism (1) If an inscription was not attached to the Runic Digit when it was etched, then the owner of the Runic Digit is the individual that holds the largest percentage of the Runic Digit's rune. (2) If an inscription was attached to the rune when it was etched, and the inscription is located in the address '1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa', then the owner of the Runic Digit is the individual that holds the largest percentage of the Runic Digit's rune. (3) If an inscription was attached to the rune when it was etched, and the inscription is NOT located in the address in (2) above, then the owner of the Runic Digit is the individual that owns the inscription. Collection Display Recommendations for Marketplaces Inscriptions within the collection could have their display names in the format '###.rdc' to make browsing easier. For example, the inscription attached to ONE•ZERO•ZERO•ZERO•ZERO might be displayed as '10,000.rdc'. Filtering Recommendations for Marketplaces - Inscription type (Text, image, etc) - Satributes (Uncommon, Block 9-450x, etc) - Number of Digits. (Four and under is the Runic Digits '10k' collection) - Digit patterns. For example: repeat digits, sequential digits, palindromes, etc. - ...and more! Originating rune: https://t.co/NTMenWjuMU

5

23

8

9

10K

1

2

0

594

about 2 years ago

A great thread on #RunicDigits! There is a lot of 'prime real estate' left to claim. We're chatting about it now in OCM alpha-chat. Runic digits are naturally occuring within the runes protocol, and the supply is limited by the character limitations of the runes protocol, which makes the comparison to bitmaps quite accurate IMO! One unique feature of #RunicDigits, that didn't exist to my knowledge prior to runes, is that the protocol allows for ownership via two methods: non-fungible (inscription owner), or fungible (runes-majority owner). The latter kicks in if the inscription owner burns their inscription to Satoshi's wallet, or if they fail to include an inscription within their Runic Digits mint.

about 2 years ago

TLDR for those curious: #RunicDigits are the #Bitmap of #Runes.

2

6

0

2K

1

4

1

0

1K

about 2 years ago

TLDR for those curious: #RunicDigits are the #Bitmap of #Runes.

about 2 years ago

Introducing RUNIC•DIGITS•COLLECTIVE. Runic Digits Collective is a consensus standard that allows anyone to claim one of the finite, naturally occurring numbers within the Runes protocol. The supply of the collection is capped by the Runes Protocol character limit. The ownership consensus mechanism outlined herein uniquely allows for trading of either fungible (rune) or non-fungible (inscription) assets. Collection Standard Runic Digits are represented in text format, with each digit spelled out. Padded zeros are NOT recognized, and, as a result, some of the lower Runic Digits will not be etchable for some time. 0 = ZERO 1 = ONE 2 = TWO 3 = THREE 4 = FOUR 5 = FIVE 6 = SIX 7 = SEVEN 8 = EIGHT 9 = NINE 10 = ONE•ZERO ... 9,999 = NINE•NINE•NINE•NINE (The final Runic Digit in the '10k' subcollection) ... 1,000,000 = ONE•ZERO•ZERO•ZERO•ZERO•ZERO•ZERO ... Ownership Consensus Mechanism (1) If an inscription was not attached to the Runic Digit when it was etched, then the owner of the Runic Digit is the individual that holds the largest percentage of the Runic Digit's rune. (2) If an inscription was attached to the rune when it was etched, and the inscription is located in the address '1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa', then the owner of the Runic Digit is the individual that holds the largest percentage of the Runic Digit's rune. (3) If an inscription was attached to the rune when it was etched, and the inscription is NOT located in the address in (2) above, then the owner of the Runic Digit is the individual that owns the inscription. Collection Display Recommendations for Marketplaces Inscriptions within the collection could have their display names in the format '###.rdc' to make browsing easier. For example, the inscription attached to ONE•ZERO•ZERO•ZERO•ZERO might be displayed as '10,000.rdc'. Filtering Recommendations for Marketplaces - Inscription type (Text, image, etc) - Satributes (Uncommon, Block 9-450x, etc) - Number of Digits. (Four and under is the Runic Digits '10k' collection) - Digit patterns. For example: repeat digits, sequential digits, palindromes, etc. - ...and more! Originating rune: https://t.co/NTMenWjuMU

5

23

8

9

10K

2

6

0

2K