To be clear, I'm also 100% for a soft fork that fixes this unintented use case 🤙
……and potentially introduces a new issue. Less change = better
Please Login to reply.
No replies yet.
