You're absolutely right @DocHex that BIP-329 is missing quite a few fields that could make it much more powerful. However, the primary value of BIP-329 lies in standardizing the storage and exchange of labels, which previously lacked any formal structure. While I agree that metadata like date/time or block height would be extremely helpful, the current implementation does not have it – especially for offline use cases. The current implementation focuses on the text-based label, as that holds the majority of contextual value. I recognized these limitations and have built the @labelbase_space platform to handle much of the additional functionality you mentioned. By aggregating, computing, deriving, and securely storing this metadata within your instance, Labelbase provides the "magic glue" needed to make these labels far more useful in practical applications.

Single-sig #bitcoin wallet. How are you backing-up your seed to metal?

Good morning! Migrating hardware wallets shouldn't feel like this, COLDCARD makes it much easier!

How do we prevent small UTXOs from being useless due to miner fees outweighing the UTXO? @nvk, @bergealex4 and @craigraw weigh in on this important question, discussing best practices for UTXO management in BR071.