Due to the maintenance at NuPool and the outage for liquidity that causes at Bittrex, I decided to create a sell side gateway.
While I have no formal permit to operate there with Nu funds, the FLOT might use their discretion to deposit funds there.
The NBT deposit address is BSn5fBQyhvTQjgGCV18XN92epjaeqqonum.
I won’t post a BTC deposit address as I don’t intend to make it a dial side gateway.
The tricky thing with this approach is, that I’m not intending to create a motion. I will strictly refer to the discretion of FLOT. If FLOT deposits funds from the FLOT multisig address, this contract will be enabled.
If NSR holders don’t want this to happen or want to stop it, they might create a motion to stop it.
At first glance this seems strange, but in fact I intend to create a precedent for it.
There’s already a lot of responsibility on the shoulders of FLOT and I don’t recognize a desire of NSR holders to create a rule set that guides FLOT.
NSR holders seem to rely on the discretion of FLOT.
If that’s true, they might rely on the discretion for enabling this contract as well.
This way the FLOT can be very agile. If a motion had to pass before FLOT can act, the sell side gateway wouldn’t be
ready for days.
Although I’m a FLOT NBT member, I won’t sign a tx to deposit funds there to avoid conflicts of interest - I might create a tx, though. This raises the bar to 3 of 4 FLOT members who need to agree for activating this gateway.
###I’ll post an update as soon as testing is complete. Please don’t deposit any funds before.
A hashed version of this contract will follow.
It will more or less look like this:
https://daology.org/proposals/8eab141d4e0f1caadb01ac3896891c0ba1545b70
(is 8eab141d4e0f1caadb01ac3896891c0ba1545b70 the hash of the draft?)
Any comments are welcome.
The NBT broadcast address was once granted here for sell side activities at Poloniex. It will be reused here, as it’s not Poloniex, but still a sell side activity.