jnthnvctr
commented
4 years ago @mrsmkl and I debugged this:
The issue was that a Verifier was trying to allocate a data cap to an address (t01046) that already had a data cap. So while the message was able to submit successfully (cid: bafy2bzaceb6ujnp4hmjzukyctzd4lpxal5guz26iissfgi4bxlfxl2ssjtb2y), the lotus node threw an error saying that that address was already allocated a datacap.
As a result, the datacap from t01066 was not spent (which is why t01046 did not increment up, t01066 did not increment down).
Reproduction steps: 1) As a root key holder, I can confirm that my address t01066 has 3GB of data cap to allocate as a verifier 2) As a verifier, I attempt to allocate 2GB of data cap to t01046 (personal wallet) 3) I get a message successful (and a message id that disappears) 4) After waiting for a few minutes and refreshing t01046's allocated data cap has not incremented 5) After checking t01046, I can see that t01066's data cap has not decremented.