<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Ok, wanting structured data is a decent argument, but why this random arbitrary case in particular? There are hundreds of fields like this that people might want to use. </div><div><br></div><div>If we're going to support one random cosmetic field, we might as well support them all with a generic structured data format. </div><div><br></div><div>I'd rather we just didn't have this essentially pointless "feature" at all. Let's try and keep as much cruft as possible <i>out </i>of the payment protocol. The textual memo field is already more than sufficient. </div><div><br>On Jun 24, 2014, at 11:48, Jeff Garzik <<a href="mailto:jgarzik@bitpay.com">jgarzik@bitpay.com</a>> wrote:<br><br></div><blockquote type="cite"><span>I think there is nothing wrong with having a numeric memo field, which</span><br><span>is effectively what this is. Structured rather than unstructured</span><br><span>data.</span></blockquote></body></html>