By your own argument then, we shouldn’t be making any changes. The entire point of updates is to force the indexers to allow new use cases for brc20s. I still do not see any reason, nor any valid argument FOR going to 5 tickers.
I understand brc is different from TAP, the only thing that separates them visually is the tickers length. 4 ticks = brc20, anything more or less is probably tap. By changing to 4 and 5 tickers on brc it would be throwing the equilibrium out of balance imo.
Can you present a reason WHY we should allow 5 byte tickers? Your argument for indexing ease is moot since just the proposal itself to allow, at minimum, the self_mint function forces the indexers to update no matter what.
We don’t agree to have activation height before we have clear and transparent Consensus process displayed to the Bitcoin Eco builders.
“Consensus process”
Please make it public and let us know how exactly does this “Consensus process” work?
Who has the right to vote, when to vote and where to vote?
If anyone agrees on my concerns, please like this reply and spread.
Discourse is great place to start with discussion, I would suggest you to make post about the concern of Consensus, because there are many ways to think of Consensus.
There is ordinals is self, and there are protocols, Each one is quite different. You could add indexers too !
Do you mean that no one can vote for BRC20 protocol except for the following people? @hirosystems @ALEXLabBTC @OylDynamics @AlliumLabs @UTXOmgmt @unisat_wallet @bestinslotxyz
So the “Consensus process” will only allow certain group of people to join and vote?
What about the communities and Bitcoin eco contributors ???
Hi.
Concerning Open Mint issuance, I would like to receive clarity on changing from an initial Self_Mint deployment to Open. Or will the deployed ticker be hardcoded to the original setting?
Thanks!