[Passed] NSR sale and NBT burn

[NSRAuction]

Here are the auction results:

NSR auctioned: 1 million
Expected auction proceeds to be burned: 2049 NBT
Highest price: 0.002098 per NSR
Lowest price: 0.002 per NSR
Total NSR bid for: 6 million

If you bid 0.002 or more, you will be contacted to arrange settlement, which must be completed no later than Monday UTC.

Buy side liquidity is 34044 and sell side liquidity is 44015. Because the buy side is smaller than the sell side, an additional auction of 1 million NSR will be held ending next Friday UTC.

The motion to make auction size adjustable has less than 48% support, so it will not be applied. If it had, the auction size would have been 667,000 instead of one million for next week.

[Cybnate]

The motion to make auction size adjustable has less than 48% support, so it will not be applied. If it had, the auction size would have been 667,000 instead of one million for next week.

That motion just passed in the last few hours. At least it can apply for next week, a bit unfortunate timing, but I think we survive an additional 333k of NSR to NBT burning.

[mhps]

Park Rate Voting

The buy side liquidity is now 42k, the sell side liquidity is now 35k.

Since this motion doesn’t address what happens when there is too much sell side, should we introduce a motion to buy NSR and burn them on a weekly basis until the buy side liquidity is equal to the sell side liquidit?

[Cybnate]

I think creating NuBits is the sensible answer, but I would be reluctant to do that as the situation seems to change by the day. Let’s see if we get a trend in the next few days.

[mhps]

I think creating NuBits is the sensible answer,

If you mean creating NBT to buy NSR and burn the NSR (or buy PPC and distribute dividents, yeah) then I agree. If you mean creating NBT and doing nothing else I am worried. In fact a lot of Nubits have already been created. It’s the $4M of strategic reserve. NSR will be on a oneway street dilutted to oblivion as the buy side bobs up and down.

[Nagalim]

Vote park rates to zero to nullify this grant, then vote in a grant along these lines:

Some Suggestions To Eliminate Peg Maintenance Expenditures

Hello, I thought I would chime in with some suggestions. I will briefly describe a possible revamp of the peg maintenance system and then explain its potential advantages. System: 1) In each PoS block, Nushares record a binary vote about the current Nubits/USD exchange rate on external markets. 1 if the price of Nubits is > 1 USD or 0 if the price of Nubits is < 1 USD. 2) Every 24 hours (approximated in terms of blocks), an auction of Nubits and Nushares is conducted within the block ch…

Problem solved.

[GreatScott]

It will be interesting how little some here will worry about the market price for NSR burning on the open markets, like they did for NSR inflation via secret auctions. I am very discouraged that this thought is on the table so soon after all this dilution.

[mhps]

OK, a draft motion to test opinions. I add a 20% buffer zone so we won’t fret on the ripple.

=##=##=##=##=##=## Motion hash starts with this line ##=##=##=##=##=##=
This motion superceeds e91340fdbda5c2a7a1362c66eece05b9c67d2496 (“NSR sale and NBT burn”)

Buy side and sell side liquidities will be measured on every Monday UTC.

1 million (1,000,000) NSR will be auctioned weekly until the buy side liquidity is equal to or greater than 0.8 times sell side liquidity. Minimum bid size is 500,000 NSR. Payment must be made in NBT.

2 thousand (2,000) NBT will be auctioned weekly until the sell side liquidity is equal to or greater than 0.8 times buy side liquidity. Minimum bid size is 1,000 NBT. Payment must be made in NSR.

Bids are due by the end of each Friday UTC and settlement must complete by the following Monday UTC. All proceeds will be burned no later than three days after the settlement date. The burn transaction will be publicly posted to discuss.nubits.com.
=##=##=##=##=##=## Motion hash ends with this line ##=##=##=##=##=##=

[Cybnate]

This is becoming a very fundamental question and I have a hard time to make up my mind and form an opinion given the wide range of pros and cons which have been discussed. In a sense I like the motion as it creates NSR as collateral, basically manually achieving what Benjamin is advocating. I’m also aware that this is not how Nu was originally designed.

Best I can come up with is that Benjamin’s approach works better when the peg is under pressure and the confidence/utility in the NU network is relatively low. When usage, confidence and ownership increases I think there is more room to loosen the 1:1 collateral to some extent. Haven’t made my mind up whether that can be 50% or 80% eventually.

I’m still having difficulties with selling NBT and return that to the Shareholders as dividend. If anything it should be returned as shared collateral which can be used when the peg is under fire. That doesn’t mean that this is dead money, it can certainly be used for e.g. short term lending.

Dividends should only be paid when the network makes profits e.g. from services on the network. Unfortunately we haven’t seen much of that yet.

Just my 0.02 NBT

[mhps]

In a sense I like the motion as it creates NSR as collateral, basically manually achieving what Benjamin is advocating. I’m also aware that this is not how Nu was originally designed.

The design change has long been approved in Motion to end LPC operations of KTm, Jamie and NSR sales of Jordan, which says

Therefore, we will have two complimentary mechanisms which are the exact inverse of one another:

1. When NuBit demand is low, NuShares will be created and sold while NuBits will be purchased with the proceeds and burned. NuShare supply increases as NuBit supply decreases. This depresses the NuShare price as it supports the NuBit price to the pegged level.
2. When NuBit demand is high, NuBits will be created and sold while NuShares will be purchased with the proceeds and burned. NuBit supply increases as NuShare supply decreases. This inflates the NuShare price as it suppresses the NuBit price to the pegged level.

So the above modified motion is just an implementation of it. NBT and NSR are the two sides of the same thing. Value flows between them to maintain the peg. I think @Benjamin’s suggestion differs from the modified motion by 1) implementing on protocol leve 2) using binary vote. I see the above modified motion a step to protocol level change.

loosen the 1:1 collateral

True 1:1 collateral is only possible using the USD. BTC volatility will wipe out any attempt at keeping stable value in crypto (if you think of derivatives, you get counterparty risks.)

I’m still having difficulties with selling NBT and return that to the Shareholders as dividend.

Dividends is widely used to valuate shares. It’s easier to understood by lay investors than share buy back. Besides being easier to understand, I think dividend has a greater effect to push up marketcap of NSR because people know the bought-back shares, if not burnt, could leak out when no one is watching. So I see dividend an effective value-transfer scheme from NBT to NSR.

[dysconnect]

I think with B&C exchange we can create derivatives to help maintaining the peg. In any case, lack of network revenue is still the culprit.

Even with full USD reserves there will still be a cost burden of counterparty risk. Dividends leak out of the network, and if they all come from sale proceeds of NBT, the long term NSR market cap can only be equal to the long term amount of NBT in circulation, which we know is unhealthy. NSR buyback may have similar problems, except it seems to make the value of holding NSR less transparent.

NSR/NBT burning helps, and should be implemented at protocol level at some point. Ongoing discussion on this is very meaningful. The priority now however should go towards building a revenue model.

[dysconnect]

Even though the sell side is lower than the buy side, now is not the time for creating NBT.

[masterOfDisaster]

If the Nu network did already have a system like the one proposed by @Benjamin Nu did know and wouldn’t need to guess

[Nagalim]

A possible revenue model:

[Draft] Volume-dependent Transaction Fees

Motion RIPEMD160 hash: tbc =##=##=##=##=##=## Motion hash starts with this line ##=##=##=##=##=##= The variable transaction fees, implemented as per motion 7283C71D2BDDC3B71E2EB7CD0693E28E3665BF66, will be replaced with variable, volume dependent transaction fees. Where shareholders would previously be voting on the flat fee, they will instead vote on a proportionality constant for the fee (labeled 'p'). Every output to a transaction with a target address that is different from any source ad…

[NSRAuction]

Auction proceeds in the amount of 2049 NBT have been received and burned.

[Cybnate]

Is this week’s auction still on? Was not entirely clear from this thread, although I believe the motion tells us it should be.

[desrever]

I have to admit I didn’t follow the complete discussion, and maybe someone already proposed it.
But what if instead of burning NBT, we use those NBT to buy NSR and then burn NSR?

It will reduce NSR supply and revitalize the NSR market generating arbitrage opportunity between the NSR/NBT pair and NSR/BTC pairs for other traders.

Thoughts?

[Cybnate]

This motion came into place to balance the buy/sell side for NuBits. Burning NBT as a last resort as the park rates didn’t have much effect.

Your proposal is interesting but I believe serves a different purpose, maybe a discussion for another thread?

[desrever]

For sure my proposal won’t help reducing NBT supply. Sorry for checking in without proper understanding. Let’s leave this out for the NSR Buyback discussion.

[Nagalim]

I propose we nullify this motion asap:

[Draft] Seeded Auctions

Custodial hash RIPEMD160 hash: tbd =##=##=##=##=##=## Motion hash starts with this line ##=##=##=##=##=##= 1350 nbt @Nagalim will continue running automated auctions every 5000 blocks and will seed the auctions with 200 nbt per auction for 25000 blocks. Received nsr will be burnt. @Nagalim will be rewarded 200 nbt for open sourcing the software, 100 nbt for acting as auctioneer, and 50 nbt for acting as reserve. =##=##=##=##=##=## Motion hash ends with this line ##=##=##=##=##=##= Tria…