[Passed] Temporarily cap NBT supply with full reserve

The liquidity engine cannot operate without a peg. Therefore, our first priority needs to be the establishment of a peg. It must be one the market will have confidence can be defended. $0.10 can be easily defended, implying a total money supply of around 70,000 USD.

At this level it will be easy to re-establish NuBits as being backed by full and transparently provable reserves (such as FLOT funds). We utilize the NSR buyback/sale calculations that have been established including the Standard, but change it to require a full reserve.

If the Standard is positive (more than 100% reserve), the peg level gets raised. Through repeated raises in the peg level, the peg returns to 1.00 eventually.

This plan is extremely straight forward and easy to implement. It has only three immediate action items:

  1. All liquidity providers peg NBT to $0.10

  2. Change the Standard calculation to require 100% reserve.

  3. Change NuBot and PyBot to feature a setting for the peg level.

I will be raising four motions: one to mandate a peg level of $0.10, a second to change the Standard calculation to require full reserve, a third to regulate how the peg will be raised in the future to eventually return to $1.00, and a fourth to place a cap on NuBit money supply until the peg is restored back to $1.00.

Essentially, we peg at $0.10 right now. As NuBit demand increases, we don’t issue additional NuBits, we lift the peg up as a one way ratchet. Once the peg is restored to 1.00, the NuBit money supply will expand again, but this time with full, provable reserves. We will also need a cap on the rate of NSR sales, if the recovery of the NBT price outpaces the gathering of reserves.

The most urgent consensus that must be reached by shareholders is the current peg level, so I will advance that motion first.

This motion is being withdrawn because I now favor simply purchasing NBT with NSR sale proceeds. I eagerly support the other two that require 100% reserve and a cap on the NBT supply.

“Establish NBT Peg at $0.10 USD” available at Daology.

Motion hash: a26f6661ced949166227019f0ee64afe98f7e6b0

The second motion I mentioned, 100% Reserve Required For NuBits is shown here:

Motion Hash: 470ba7bf40099c395b8fb569367d16ce6167c2bd

The third motion I mentioned, Plans And Regulations for Peg Adjustment is going to be complicated and difficult to finalize properly. I have included some exploratory text in the draft as a start:

The fourth motion I mentioned, “Temporary Cap on the NuBit Money Supply” is available here, and is shown here:

Motion Hash: f8b9e060dc73a97fd28a62ecfdd419114892787a


i was thinking the same thing, but more radical approach of pegging to 1 cent with 100% reserve.

Phoenix - I like your name. Chosen for a purpose…
This goes a long with the ideas posted by others.

1 Like

Why choose a low peg? We aren’t playing the market to our advantage by cutting the value short. Why don’t we wait and see where nbt stabilizes and work to support it there instead of cut its value by more than half to rush a pegged position immediately.

1 Like

I hope this isn’t suggesting to peg the sell side to $.10.

To me that’s the way it reads…
There’s a lot more specifics needed though.
Allowed spread?

AND Nu doesn’t have the funds to support $0.1
Right now that’s ~110 BTC

1 Like

It is our job to regulate the value of NuBits. We must have a peg to provide liquidity.


That ship has sailed. Don’t force it now at the expense of the project. Let it reorient then re-establish regulation. I agree with the 100% backing part.

Let’s explore that claim. How many reserves does Nu have right now?

Whatever the answer, more can be had by selling NSR. I expect a gap of several tens of thousands to meet full reserve, but we can meet full reserve over a period of weeks through NSR sales. The utility of parking would also be fully restored, to the degree there is confidence in the new peg level.

Liquidity is nearly always provided by NuBot or PyBot. These require a target price. NuLagoon Tube, all of our pools and individuals such as muchogusto all require a price target as a basis for their offsets.

@woolly_sammoth @desrever can NuBot and PyBot support pegging at $0.10 without modification? If a modification is required, can you make a special build supporting a configurable peg target?

Right now, Liquidity is provided by the free market at Poloniex. Fighting the market, in such a turbulent time in BTC, I think, should be done dynamically and quietly. Otherwise It will be gamed by smarter people than us.

Why can’t we we resolve to use/make a bot to tighten the existing spread, just a little, so that Nu makes money on the spread?


New account? How refreshing … you still need to answer those questions though …

I can tell you for both NuBot and PyBot that modifications are required, but of course small (just divide the price feed output by 10). However, you still suffer from the fatal thinking that someone will buy NSR just because you promise to buy more in future. You just want to restart the ponzi from 10 cents, but still without revenue.


We need a market for nbt. It can’t just be a liquidity provider. I made another thread suggesting a casino/lottery but the more ideas we have to use nbt as a burn-able fuel or a required currency or intermediary for a service the more we make revenue and can support the ecosystem other than ponziing it

@creon, would you be willing to create a build of NuBot and/or PyBot that features a configurable setting for the peg level?

No more houses of cards and vision statements…

We need blueprints.
We need plans with risk vs rewards.
We need P&L projections for any venture undertook.

We didn’t have it before - blindly striking out. And that’s what got us here.
This is a “business.” Let’s start acting like it.


I can definitely envision a blue printed and highly successful strategy

1 Like

I’m not stepping in here in any way, just watching and calling ppl out for their bs. Again, its a minor thing to achieve what you want, in the Nubot just get another float from the option parser and use it here to divide the prices:


Likewise, just hack another param into the pybot and divide the price here:


But that ain’t solve your problems.

@Phoenix who are you?


From Dictionary.com: