Yes, I tried contacting core devs before publishing. They had not responded. And I don’t really blame them — they already describe this specific attack and partial mitigation in Nano public documentation — I guess they simply had nothing to add.