use the memo.cash protocol in replacement of cashaccount

[PiRK]

Suggestion by @christroutner:

For message.fullstack.cash, I'm using the memo.cash protocol for retrieving names. It searches the tx history for an address and looks for an OP_RETURN with a 0x6d01 prefix.

https://memo.cash/protocol No server required. Each implementation can use the same protocol without depending on any extra infrastructure. I've got a JS library for it if anyone is interested. Though it's not well documented yet. I've also got a REST API with a Mongo DB that catches the name data. That cuts down on redundant processing, and significantly reduces the amount of processing required on a front-end app.

All open source. Happy to give links to the code.

[christroutner]

I'm in the process of implementing this at message.FullStack.cash, and PSF will be releasing a video on the PSF YouTube channel with a walk-through of how to use the web app.

But as I mentioned in the quote above:

• bch-message-lib is a JavaScript library that is optimized for both front-end and back-end applications. It can search through an addresses transaction history and look for the 0x6d01 prefix that signals a persons name in the memo.cash protocol.

• community-msg-api is a node.js REST API server that makes use of this library. It has a REST API endpoint that a front-end app can use to request the name belonging to an address. The server uses the bch-message-lib to find the name and caches it in a Mongo DB. This architecture is efficient and cuts down on the amount of computation required by the front-end.