A fixed cost pool attempts to fix the minute by minute cost in NBT of liquidity provision, despite the actual liquidity provided. By paying full compensation to any LP willing to provide even the thinnest wall, an FC-ALP incentivizes providers to maintain continual and balanced liquidity provision in order to maximize their personal profit. It also causes direct competition between providers by forcing them to share the reward proportionally to the liquidity they provide. Finally, FC-ALP makes accounting and pool parameter selection much easier by greatly decreasing rollover funds and removing all reference to a liquidity target.
The software I intend to use is here: https://github.com/Nagalim/alp-collection/blob/master/python/fc_server.py
The value I use in the config file for ‘rate’ is: 0.00000075
There are improvements to be made, for sure, but I believe this solution is at least stable.
Motion RIPEMD160 hash: 187e547074c3fe0508a56d684dd705ec5d9929ee
=##=##=##=##=##=## Motion hash starts with this line ##=##=##=##=##=##=
Operator: @Nagalim
Type: Fixed Cost ALP
Length: 30 days
Exchange: Bter.com
Pair: NBT/BTC
Spread After Fees: 1%
Tolerance: 1% (0.01)
Bid Cost: 7.5 NBT/day
Ask Cost: 7.5 NBT/day
Operator Fee: 100 NBT
Total Grant: 550 NBT
Term 5 Requested Funds: 450 NBT
If @Nagalim decides at any time that the use of the fixed cost software may compromise the NuPond brand, the pool may switch over to a fixed reward pool at dual side 3,000 NBT targets with 0.25%/day reward rates.
=##=##=##=##=##=## Motion hash ends with this line ##=##=##=##=##=##=
Verify. Use everything between and including the <motionhash></motionhash> tags.
