[Passed] LiquidBits term 5 grant - Automatic Liquidity Pool (ALP)

[Nagalim]

1080/60 days gives us 5,000 NBT on each side if the rate is 0.18%/day

[Cybnate]

@assistant liquidity

[cryptog]

resulting in a total maximum compensated liquidity of 22,000 NBT.

So you have reduced a bit (1000 NBT) from Term 4 (23,000 NBT) .
What would you think about reducing even more?

[assistant]

Hi @Cybnate

The current total liquidity in the Nu network is:

Bid: 103033.5664 NBT
Ask: 80361.2587 NBT

It is broken down in the following manner:

    Bid: 7837.6984 NBT
    Ask: 11633.9399 NBT

Tier 2:
    Bid: 0.9 NBT
    Ask: 10796.8686 NBT

Tier 3:
    Bid: 18787.6363 NBT
    Ask: 22489.152 NBT```

[zoro]

@cybnate, you are not in favor of fixed cost pools?
(provided that they are tested and working ok.)

[Cybnate]

What would you think about reducing even more?

I actually reduced a lot more on CCEDK, but allocated a part of that to the Southexchange account. Please note that I’m the only ALP actually reducing the liquidity. I hope I do set a trend, but I’m not yet prepared to cut further when there are no followers.

@cybnate, you are not in favor of fixed cost pools?

I think it is a step back, which appears to be required to make steps forward. The fixed cost will increase the cost to the network as most pools are underutilised. That means that the Shareholders are not paying for the remaining unused cost. With the fixed cost reward we need to be very careful regarding individual allocations to ALP as that will be the price we pay and not one cent less even if there is only 1 NBT liquidity provided on that exchange.

I still think the Dutch auction model is far better, the Shareholder only pays for actual liquidity provided and the liquidity providers compete with each other on price. However unfortunately we don’t have the knowledge, documentation and resource to fix the existing bugs in the current software. So it makes sense to step back to a model we do understand and than hopefully make the next step soon.

The only real problem we have with the current model (not the software) is that we have been too generous with the liquidity caps as we don’t have an overarching control mechanism to balance caps across exchanges. The fixed price solution doesn’t solve this, it may even have adverse effects in the short term. However I still support it as there are no better solutions presented.

[Cybnate]

I’ve put up the LiquidBits term 5 grant proposal for voting. Please verify the original post as I have made some minor changes.

When in favor please add the following to your vote section in the client or subscribe to my datafeed.

Custodial Address: BA9tumP4zyM1g2M8ZNieD2iAnMgdVPuQe3
Amount Requested: 2729 NBT

Edit: updating OP and rehashing, made an error with the address…DONE

[willy]

dd491de3ed1c69b080092d142ba13470cd398ce3

dd491de3ed1c69b080092d142ba13470cd398ce3 confirmed

[cryptog]

dd491de3ed1c69b080092d142ba13470cd398ce3 verified and

Custodial Address: BA9tumP4zyM1g2M8ZNieD2iAnMgdVPuQe3
Amount Requested: 2729 NBT

voted

[Cybnate]

[zoro]

@Cybnate, i understand your concerns about fixed cost pools. Then what if we combine somehow fixed cost with fixed rewards?
We can do it with different reward levels. for example:

1. we setup a pool with max fixed cost of 2000NBT.
2. we setup payout levels according to daily liquidity
   (for 100NBT, participants payed with 10NBT, for 1000NBT they are payed with 100NBT,etc, until reaching the max 2000NBT in final level with unlimited liquidity)
   too complex for coding? less fair than other models? high cost for NU?

[Cybnate]

Then what if we combine somehow fixed cost with fixed rewards?

Sounds complicated, but maybe simpler to code. In my opinion the Dutch auction is a very good model to do just that, but way more flexible. It just needs to be combined with the caps on the liquidity.

[Nagalim]

(for 100NBT, participants payed with 10NBT, for 1000NBT they are payed with 100NBT,etc, until reaching the max 2000NBT in final level with unlimited liquidity)

This can be done easily. Let me run a pool with vanilla fixed cost first, but I can make that kind of modification with just a few ‘if’ statements. I would probably do something like:
if mass<100:
newrate = 0.2oldrate
if mass<1000:
newrate=0.5oldrate
else:
newrate=oldrate

This is a blending of the fixed cost and the cooperative model:
Custodial Rules for the Static Peg with Fiat

[Cybnate]

[Cybnate]

[Cybnate]

It looks that this request doesn’t have a majority to pass. Please provide some feedback if you are not voting for this proposal and I will try to explain, withdraw or change the request where possible.

When this grant hasn’t passed on the 12th which it looks like, I feel obliged to stop operation at least temporarily or use some of the rollover funds. Will only do that when the last 100 blocks shows a majority of the votes during a couple of hours.

[Nagalim]

Your numbers have SouthExchange USD/NBT with 1,000 target but paying out 1080 NBT over 60 days. That would be true if there were a 5,000 NBT target. I believe your grant should be less by 864 NBT.

Is your fee 300 or 150? It says 300 in the text but then uses 150 in the calculation.

Also, your tolerance is written in the grant as 8.5% not 9%. Typos make for interesting ambiguities for a contract. Of course, neither would be in compliance anyway, as the fee on NBT/BTC CCEDK is 0.2%.

Does south exchange even exist? I can’t find their website anywhere. I’m not sure I am comfortable with you opening operation on two new pairs at once, especially for a 60 day term with no plan for midterm parameter adjustment.

[tomjoad]

Does south exchange even exist? I can’t find their website anywhere.

https://www.southxchange.com/Market/Book/BTC/NBT from https://nubits.com/exchanges/nubits-exchanges

[Nagalim]

Thank you very much, not sure why a “south exchange bitcoin” google search doesn’t turn that up. My bad, shoulda gone through nubits.com.

South Exchange is also 0.2% fee. The minimum tolerance for compliance is 1% on the NBT/BTC pools.

[mhps]

I think the motion is fine but it is better to separate ccedk and soutexchange and start soutexchanage with a 1mo term first.