You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As happen to some of us last month ( Nuno, myself,etc) that we didn´t have any power at the distribution event , and that the project need as much liquidity as possible right now.
Would it be a good idea that for people that is contributing regularly, meaning that are taking part at the governance system to keep the token power even when they put the tokens at the liquidity pool? Is it technically possible to do so?
We could reinforce two things with this: to promote the liquidity without neglecting the governance ( eting the contributors keep their weight power for the distribution event) @Luis-Fernando-Molina@julian-molina@harrellbm@NAmorim
The text was updated successfully, but these errors were encountered:
I've played a bit with this on pancakeswap but the numbers do not match out. In pancakeswap I was using the percentage of the pool each account has to calculate how many tokens are "locked".
Another approach that I've thought off is to use the transactions information from BSCscan (harder) or the graph API from pancakeswap.
Anyone interested feel free to join the discussion!
As happen to some of us last month ( Nuno, myself,etc) that we didn´t have any power at the distribution event , and that the project need as much liquidity as possible right now.
Would it be a good idea that for people that is contributing regularly, meaning that are taking part at the governance system to keep the token power even when they put the tokens at the liquidity pool? Is it technically possible to do so?
We could reinforce two things with this: to promote the liquidity without neglecting the governance ( eting the contributors keep their weight power for the distribution event)
@Luis-Fernando-Molina @julian-molina @harrellbm @NAmorim
The text was updated successfully, but these errors were encountered: