What does it mean for CvRDT replicas to transmit their state "infinitely often"?
From my understanding of CvRDTs (though I haven't read that exact paper recently)


I believe after receiving new state m is always called, however this should be part of the send/receive machinery, rather than something the application has to deal with. That doesn't prevent the application calling m if it sees the need, but in lots of cases there isn't one.
u has to be inflationary otherwise it will get "lost" by a merge. Given a merge could happen at any time, a non-inflationary update could disappear beneath the CvRDT user as they were performing operations on it. And while non-inflationary updates don't pose a problem for convergence, they do pose a problem for equality: a &lt;merge&gt; b may not be deterministic in the presence of non-inflationary updates.
I don't have an answer for this. Maybe it's worth reading as "unboundedly many times between each update", but that's a guess.