Thank you for your clarification.
How can you tell without evidence?
Let me try:
the claim that Nu can keep a peg at all, if only orders at <1% spread are allowed isnāt true!
I have evidence: Poloniex, January 2016.
Sure, but whatās the answer if the question reads:
do we want to stop supporting the peg just because we run out of funds?
If you have a look at the reserve, you might find itās quite low.
So would you rather have a peg with a worse spread or no peg at all?
If the restaurant is full, you wonāt get a seat.
If the weatherās nice and you want to sit on the terrace, but are too late, you might need to sit inside or donāt eat that day at that restaurant.
T1.1 volume gone? Have some of the T1.2 orders!
Did you really understand that Iām for orders <1% spread AND orders at >1% spread to support the peg once T1.1 is empty on one side?
Depending on the reasons for it to be empty, it can be fixed faster or slower.
It depends on the funding of higher levels as well.
Iād never recommend to fill T1.1 from T1.2. Treat them independent from each other.
Replenishing T1.1 from T2. If thatās empty, go to the next higher tier.
T1.2 is a defence for the peg once T1.1 failed.
Using T1.2 to replenish T1.1 undermines the reason for having T1.2 in the first place.
But there is a reason for it at the moment and there was a reason for it in January.
Without the funds at @zoroās and @Cybnateās gateways, the peg would likely have been lost at Poloniex today just as it had been lost in January.
The only thing that could have prevented that from happening would have been a stop of trades above a certain spread.
Would you want to rely on that?
Would you rather want to have some funds at a spread that is not exactly attractive, but not horrible either?
This business grows from NBT that get sold and remain circulating.
This business makes revenue from fees that get destroyed.
Supporting trading to a certain degree is necessary for bringing NBT in circulation. People need to know that they can trade them back if need be.
Supporting trading beyond that degree is just increasing the costs - unless you have NuOwned operations at a spread from which revenue can be made.
At a restaurant or a shop itās accepted to some degree if an offer is sold out.
We are in a trading market. Itās common knowledge that supply and demand are tied to each other. This is what Nu is built on!
Iād never dare increasing the spread on USNBT/USD to levels of NBT/BTC.
But I wouldnāt hesitate increasing the spread of NBT/BTC beyond 1%, if thereās so much demand for Nu products.
The NBT/BTC market is one where Nu offers a synthetic peg. Market rules should apply to some degree to it.
Lots of demand? Sounds like a reason to increase the price, which is in this case the spread.
Economics 101.
Where exactly did Nu promise to offer USNBT only at a tight peg in the USNBT/BTC pair?
Why then is it impossible to get a simple truth through?
Orders only at 1% or below will first kill the peg and then Nu; maybe it ruins only the brand image.
Each BTC price jump you are at risk of running dry on all tiers 1 to 4.
Activating T5 takes time to kick in and T6 might take even more time.
The peg will fall unless traders are āfriendlyā and donāt trade at high NBT/BTC spreads.
Orders at an increased spread buy time and guarantee the peg at least on the spread they run on as long as they have funds.
This can only be mitigated by keeping an increased BTC reserve, but that increases the collateral risk.
BTC price drop is a bit more kind, because you can just print as much NBT as you need to buyall the BTC, which in turn may continue to lose value.
Once your motion to force all new operations to below 1% passes, Iāll take that as sign that I failed convincing people that this road is dangerous.
Weāll see what happens then. Maybe Iām wrong. I dearly hope that Iām wrong, but I trust my experience and my gut.
Jordan, donāt get me wrong. I admire what you designed, what you and the dev team created.
But I dare say that Iām more up-to-date with the motions that regulate liquidity provision and that I have more experience with it on an operational level.
A well thought-out design might not necessarily fit in the real world.
You are trying to design the spread of liquidity provision.
I made a very similar proposal.
Itās pretty much the same as yours and I shamelessly copied most of it.
Itās almost the same, but for one important difference: I have a backup plan included: gateways that are allowed to run at an increased spread.
If the shit hits the fan, theyāll be there.
The shit already hit the fan twice and they were there. @zoro had an easy time, because his NuBots already were on an increased spread.
Believe me when I say, it was worse in January when I had to learn how important it is to have orders at an increased spread.
But do you want to know whatās even worse? Having no gateways at all, because thereās no funds for them after tiers 1 to 4 have been emptied by the next BTC price jump.
Your proposal is the one from an architect.
Mine is from one who fights for the peg in the first line, who suffered and learned from it.
Itās not the work I worry about. Did I ever be suggestive of that?
Itās trying to deal with more guests than can be seated or fed that should worry you.
If all funds are gone at one side, because strangely a parametric order book and market awareness (yah, we donāt have that coded, but it can be done manually) are no longer good ideas, somebody will get no seat and no hamburger.
Poor lads.
I thought getting uses cases for utilizing NBT and destroying NBT would be our job while we keep a low profile on trading at exchanges (rather than risking the peg by trying to bite off more than we can chew)?
Or finally getting trading volume on USNBT/USD or creating fiat gateways?
Anyway, may the liquidity be with you!