rich1.0npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8https://nostr.ae/npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8njumphttps://nostr.ae📅 Original date posted:2011-12-18 🗒️ Summary of this message: Jordan Mack agrees with Matt that firstbits is not as desirable as current alias proposals, but sees its usefulness for the "green address" case. He questions how saving space is possible by using the whole public key instead of just the address. 📝 Original message:2011/12/17, Jordan Mack <jordanmack at parhelic.com>: > While I think firstbits is an interesting idea, I agree with Matt on > this one. Firstbits, while being a clever idea, produces a less > desirable solution in comparison to the current alias proposals. I'm just saying is useful for the "green address" particular case. People don't have to write or memorize the firstbit address, it's just to have a shorter string to put it in the QR code. In this particular case you don't really care about "squatting" or typographic errors because the users are bot going to write or even see the firstbit address. I think aliases are a better solution for the "memorizing use case". But anyway, reading some comments I feel I'm missing something about this proposal. How can you save space by putting the whole public key instead of just the address (a hash of the public key) with each output? Is this what it's being proposed?