Much ink has been spilled on Taproot Asset Representation Overlay, including a few lightning (pun intended) marketing rounds in April and 2Q22. After many sleepless nights learning and thinking about the protocol, here’s a visual of what I came up with:

Apparently, Bitcoin Orange is a thing. And yes, Bitcoin should always stay orange. Specifically, #f2a900.

As for Taro, perhaps it would be nice to specify #a900f2. While we’re at it, may I suggest #00f2a9 for assets represented on Taro? That would complete the Triadic Color scheme. Perfect harmony.

Block space is inexpensive today. It makes sense to find use cases, without unnecessarily spamming Bitcoin. Time (and I guess the market) will tell whether this is a good use of resources. As of September 2022, when I hear “Taro”, Q-taro is still the first thing that comes mind (and not the vegetable). Let’s find out how deep this rabbit hole goes. Meanwhile:

My asks are two-fold:

(1) to keep Bitcoin orange. In many ways, the community has come a long way from P2SH, and Taproot certainly looks like a vast improvement from customized redeem scripts. It’s refreshing to build “natively” on Bitcoin, but let’s proceed with caution;

(2) can someone point me to further readings and resources on Taro asset wallets (or LN wallets, in general)?

Silly questions:

(a) Will Arthur Hayes and team build Q-Taro? (pun-intended)

(b) Wen Carrot?

(c) TARO(T): Looks like testnet’s “T” has taken the commonly used abbreviation, can we keep it that way and keep token’s “T” separate?

Lightning Labs officially launched Taro on April 5th, 2022 and a video primer was released two days later. I have included references of draft BIPs related to Taro, originally sent out by Lightning Labs’ CTO Olaoluwa Osuntokun: (a) The Taro protocol; (b) The hybrid data structure (MS-SMT); (c) The Taro Virtual Machine; (d) The Taro address format; (e) The Taro Universe concept; (f) The Taro flat file proof format

Images created by Midjourney