If we are not conflating spam (content) with spam (quantity), yes. Data hidden via stagnography is not a future IBD issue. I am not a reactionary here, I just don't like the intentional mischaracterization of a reasonable approach. Creating more of a validation burden on future nodes is the threat, in my estimation.

If OTS ever implements sign to contract, it could just be an ordinary 1in 1out payment, which would be less than a tx with a 40 byte opreturn. https://github.com/opentimestamps/python-opentimestamps/p…