FreeosDAO / freeoscontracts

Freeos Smart Contract Code
0 stars 1 forks source link

iteration 9 - seems a mismatch in liquid and vested freeos #16

Closed shahidnz closed 3 years ago

shahidnz commented 3 years ago

User type: v iteration 9 Claimed. User: lushalusha

10:26:28 08/03/2021 ~/eosio-wallet$ proton push action freeos333333 claim "[\"${acc}\"]" -p $acc@active
executed transaction: 8723931cbcd2965f3175d21b879125dd9844d7b3bf2825ea581f5fbd186c8d85  104 bytes  377 us
#  freeos333333 <= freeos333333::claim          {"user":"lushalusha"}
>> lushalusha claimed 30.0000 FREEOS and vested 270.0000 FREEOS for iteration 9
#  freeos333333 <= freeos333333::issue          {"to":"freeos333333","quantity":"6330.0000 FREEOS","memo":"claim by lushalusha"}
#  freeos333333 <= freeos333333::transfer       {"from":"freeos333333","to":"lushalusha","quantity":"30.0000 FREEOS","memo":"claim by lushalusha"}
#  freeos333333 <= freeos333333::transfer       {"from":"freeos333333","to":"freeosdivide","quantity":"6300.0000 FREEOS","memo":"claim by lushalusha...
#    lushalusha <= freeos333333::transfer       {"from":"freeos333333","to":"lushalusha","quantity":"30.0000 FREEOS","memo":"claim by lushalusha"}
#  freeosdivide <= freeos333333::transfer       {"from":"freeos333333","to":"freeosdivide","quantity":"6300.0000 FREEOS","memo":"claim by lushalusha...
warning: transaction executed locally, but may not be confirmed by the network yet         ]
10:27:03 08/03/2021 ~/eosio-wallet$ proton push action freeos333333 claim "[\"${acc}\"]" -p $acc@active
Error 3050003: eosio_assert_message assertion failure
Error Details:
assertion failure with message: user is not eligible to claim in this iteration
pending console output: user lushalusha has already claimed in claim period 9

Still, the dummy data table says nothing should go to vested while out of 300, 270 goes to vested.

>> lushalusha claimed 30.0000 FREEOS and vested 270.0000 FREEOS for iteration 9

But vested should be zero as per mock table- 9 300 $ 0.0167 0.00% 300 0

Please verify or fix.

tommccann777 commented 3 years ago

Can you please try to replicate this problem in iteration 11?

shahidnz commented 3 years ago

Closing the bug as it was the side effect of changing the current price.