The negative sMerit TXs emitted by the forum, to counter some positive sMerit TXs which were related to merit abuse, are currently a small number: 16 TX with an aggregate of -104 sMerits.
converted_date nMerits msg FromUser ToUser
2019-02-05 22:07:10.000 -5 0.msg0 (Bitcointalk Forum) peloso
2019-02-05 22:07:10.000 -8 0.msg0 (Bitcointalk Forum) LiQio
2019-02-05 22:07:10.000 -4 0.msg0 (Bitcointalk Forum) Bazinga442
2019-02-05 22:07:10.000 -2 0.msg0 (Bitcointalk Forum) Deena
2019-02-05 22:07:10.000 -10 0.msg0 (Bitcointalk Forum) TECSHARE
2019-02-05 22:07:10.000 -10 0.msg0 (Bitcointalk Forum) gwsukabokepjepang
2019-02-05 22:07:10.000 -1 0.msg0 (Bitcointalk Forum) Rmcdermott927
2019-02-05 22:07:10.000 -9 0.msg0 (Bitcointalk Forum) hoop
2019-02-05 22:07:10.000 -10 0.msg0 (Bitcointalk Forum) Quickseller
2019-02-05 22:07:10.000 -10 0.msg0 (Bitcointalk Forum) Thule
2019-02-05 22:07:11.000 -2 0.msg0 (Bitcointalk Forum) cryptohunter
2019-02-05 22:07:10.000 -10 0.msg0 (Bitcointalk Forum) cryptohunter
2019-02-05 22:07:10.000 -2 0.msg0 (Bitcointalk Forum) mich
2019-02-05 22:07:10.000 -5 0.msg0 (Bitcointalk Forum) H8bussesNbicycles
2019-02-05 22:07:10.000 -7 0.msg0 (Bitcointalk Forum) Tupsu
2019-02-05 22:07:10.000 -9 0.msg0 (Bitcointalk Forum) TheCoinFinder
It’s a good way of reverting merit for abusive cases, but does have a few small minor drawback when keeping track of events:
- The message Id seems to be cero, while the original message normally still remains. Perhaps using the same Id as the original positive TX would make tracking clearer.
- The original sender still counts as having sent those positive sMerits (from A->B), although they were cancelled through (Bitcointalk Forum)’s negative TXs.