chip-bcmr VS desktop

Creators of tokens on the BCH mainchain can leverage the advantages of having a following a standard and entering that info into the BCMR (Bitcoin Cash Metadata Registry). To help streamline the process developer Mathieu Geukens has created a handy generator to enter all your newly created token info and have it ready for submission.

The Paytaca wallet team has created an open source indexer for BCMR (Bitcoin Cash Metadata Registry) metadata. In the next release of their wallet new CashToken metadata will be shown in the wallet.

Now, just a couple of week after the publishing of the metadata chip, I guess he finally found it this also didn't make him happy.

You can find the full specification here: https://github.com/bitjson/chip-bcmr, and I'll be hosting a livestreamed tech talk + Q&A on Bitcoin Cash Metadata Registries tomorrow, November 1st at 13 UTC (9am Eastern time).

Here's a summary of arguments I've seen in this thread and my responses to them: 1. > If you want to increase OP\_RETURN, create a CHIP I don't think there should be a CHIP process. No new rules should be added. The only changes that should be made are removing unnecessary rules that BTC created. And just like miners accept low fee transactions or mempool chains however long they want, they should freely adjust all limits. 2. > You say you don't want any changes but you want to increase OP\_RETURN size See response #1 3. > It's not voting, "it's consensus" Call it what you want 4. > BCH is scaling, they removed the chain limit Yes this is a huge win. Give credit where it's due. 5. > This guy is a BSV parrot I support forking if people want to try out different ideas. That doesn't mean the two forks have to go to war afterward, or that everything another fork does is bad. I'm also happy ABC is doing their thing with eCash now. 6. > This guy is a paid troll Not even sure why I'm responding to this. But ya sure, I build software that operates on BCH while getting paid to bash it... 7. > Nothing has been broken Must not be developing on BCH. To be fair things were pretty good for awhile with ABC gone, but that seems to be changing. 8. > Why is this guy complaining about centralization, Memo is centralized website We've been publicly working on an open-source version of Memo for over a year now: https://github.com/memocash/desktop 9. > If you want a frozen protocol build on BTC or BSV This is basic sentiment I've gotten from BCH over the years when I speak out about changes. "If you don't like it, leave." Message received. 10. > There's a plan to increase OP\_RETURN from 220 bytes to X bytes (still 1/1000th of a floppy disk usually) How about miners adjust limits on their own instead of holding elections for their rights