21:33:12 <m-relay> <a​tomfried:matrix.org> will the number of bits of the view tags be enforced by consensus or is it like currently with the selected decoys?
21:33:12 <m-relay> <a​tomfried:matrix.org> could this lead to errors and fingerprinting if wallets choose to implement this differently?
21:39:18 <tevador> It will be enforced by a relay rule, similar to fees.
21:42:28 <m-relay> <r​ucknium:monero.social> Fees are fingerprinting candidates with current relay rules. (Fees are not a good example for this.)
21:45:14 <tevador> Fees only have a lower bound. The view tag size will be checked against a lower bound and an upper bound. In most cases, those will be equal, so only a single value will be valid.
21:56:12 <m-relay> <r​ucknium:monero.social> Let's see what lessons we can take from Zcash's experiment with changing fee requirements without a hard fork.
22:30:53 <m-relay> <r​ucknium:monero.social> The acceptable view tag length would be dynamically calculated from the blockchain data so the changes could be specified beforehand? So node runners would not have to update their node versions with new software? Is that the idea?