The current reverse trust uses the "against" action - I think that has some bugs / unintended consequences.
it's sensitive to the number in "against" - it should reverse the originally cast number, so if it was favour 5, it should now be against 5 (same amount)
It's using up the user's votes - example if they voted 99 points for the proposal, they now lose 99 votes from their current cycle
Spec
Add reversetrust(user, prop_id) action
Remove reverse trust code from "against" - this should make the code cleaner as well
Reverse trust
Changes the user's "favour" vote to an "against" vote on a proposal in eval stage
If they did not vote favour, error
if proposal not in eval state, error
Does not use up any votes the user has for the current cycle
The current reverse trust uses the "against" action - I think that has some bugs / unintended consequences.
Spec
Reverse trust