[Passed] NuPool 9

different price of main price feed and backup price feed ,

bitfinex is $440 , but Coinbase is $446

Sorry, i donā€™t understand. The offset shouldnā€™t be changed by its own!

check the nubot log about price feed

Currently there is no feedback between NuBot and the pool. Nothing that the pool does should affect the parameters of NuBot. My best suggestion is to restart the bot. If it carries on, could you get me the logs of NuBot and Iā€™ll take a look.

Thanks. I will sent you the logs soon :slight_smile:

Im sorry i cannt help here. Iā€™m happy to shut down my t3 operations, but id have to ask you to get the nbt from FLOT. This isnā€™t a question of speed, itā€™s a question of consensus and I would much rather use multisig consusensus than singlesig.

To try something new, I can lend you nubits for a daily compensation of 1/4 of your daily pool ops fee until you get cheaper fund.

edit: ok that can be pretty expensive considering that you might only need several tens nbt a day. How about the compensation being current 11.2 day park rate? Anyway trying some lending is good for nubits.

The latest update is that i see this
INFO - Forcing a 0.01$ minimum spread to protect from collisions
in the logs. I donā€™t know the ā€œhowā€ and the ā€œwhyā€ but as a result nubot
sets 0.005 offset for both walls regardless the chosen offset setup.
It seems that if i set the key ā€˜multipleoperatorsā€™ to ā€˜falseā€™ then i am ok.
but i donā€™t know what other problems can be arised by this!

@woolly_sammoth, a question:
what is the ā€˜Mainfeedā€™ and ā€˜Backupfeedsā€™ that you have set to NuPool?
I guess the users should setup exactly the same in order to have the same price calculations and be payed correctly.

Itā€™s against rules, but one can speculate whether the current term was not passed, because shareholders want to stop it or just because the voting started late.
I dare say itā€™s the latter, but I donā€™t know.

We need some action, if we want to keep this ALP running.

Hell, we discuss about brand image and a tight spread, but are willing to stop ALP at the most important exchange just because we are afraid of the consequences?
@woolly_sammoth, can you please tell me where to deposit the funds (can BRsLYtJhPhz7QdkKK54HkoizUrNk64wFwf be used, although itā€™s meant to be a custodial address? Does that create any protocol conflicts?) and how much you expect to need until this grant supposedly passes? At 33 NBT per day, 200 NBT should be a good start, right?

Iā€™ll create a FLOT NBT deposit to your pool address, but wonā€™t sign it immediately.
Letā€™s see what other FLOT members think about that first,
@dysconnect, @ttutdxh, @jooize, @woodstockmerkle, is it in the favour of Nu to do that?
I dare say yes, but this might once more perceived as FLOT acting as a governacne group and I understand why.
Oh, btw. Iā€™m asking this explicitly in my role as FLOT member and not as forum member. I know that this is not part of my contract, but as FLOT is responsible for liquidity, I feel responsible for NuPool in the current situation as well.

2 Likes

If we want to stay behind the as many lines as possible, I can personally loan interest-free the 200 NBT of the 435 NBT Iā€™m supposed to be getting anyway, until the grant passes. Or if it is still considered a violation that FLOT pays itself, then I donā€™t really have much to say, except that I believe it is in Nuā€™s best interests to fund NuPool immediately. Recent events really make we want to cut out some bureaucracy but Iā€™ll persevere.

Sending coins to an address does not preclude it from receiving a custodial grant, according to vote.cpp, where it basically only refuses to grant the coins if an address has received a grant before. The rationale is perhaps to block undesired behavior occurring in the aftermath of a grant passing, i.e. that an address is still continually voted on and itā€™s confusing to minting clients whether to give another grant again.

Thank you for the last few posts and the offers made. Iā€™m happy to say that a donor was found and the pool has been funded for long enough for the proposal to pass (I hope). Funds from the passing of the proposal will be used to pay back the funds received as soo as it passes. I will start work on the next proposal tomorrow and allow for some debate around the changes that are happening around liquidity provision, which th plenty of time left for a round of voting.

5 Likes

can you please comment?
thanks :slight_smile:
i have set offset = 0.005 but sometime my order is at the top of the order list and other times are far away!
i guess the far away ones are not receiving any reward!

edit: i am trying to find a way for synchronization between NuPoolā€™s and user nubotsā€™ rewarding boundaries. Now i understand why sometimes i saw zero rewards in pybot also!

Sorry for the delay. The order of the feeds mirrors the default order found in NuBot

If the price streamer were up this would be less of an issue but worth knowing the order for occasions when it isnā€™t providing the price.
Itā€™s worth mentioning that I havenā€™t seen a price feed other than bitfinex used although Iā€™m not watching the logs 24/7. Perhaps updating the price output of Eu.nupool.net/status to include the price source would be helpful?

1 Like

What is preventing this?

I donā€™t see the data feeders vote for it!
And in orders books i see some good liquidity in a tight spread, i guess it is from NuPool users :wink:

Thatā€™s not correct. At least one is for days:

Cybnate supports it as well:

Check the other data feed providers yourself :stuck_out_tongue:

1 Like

Well, something is off! :smiley:
BRsLYtJhPhz7QdkKK54HkoizUrNk64wFwf 2 votes 12 blocks ago 2,720 NBT
BRsLYtJhPhz7QdkKK54HkoizUrNk64wFwf 39 votes 1 block ago 1,280 NBT

i saw the first line which is very very wrong. Someone is voting with wrong NBT amount!

edit: @woolly_sammoth, what is missing from Nubot ALPv2 in order to be ā€œperfectā€, is what was in pybotā€™s functionality, the ability for the user to see what was his/her exact reward every single minute :wink:

This amount is from edit version 3 of this OP (from May 16th).

The NSRholder who configured that vote forgot to update it or isnā€™t aware that an update is required.
Registering a data feed can help here - if the data feed is up-to-date.

And frequency voting wouldnā€™t be bad either, although I wonder, how misconfigured votes can lead to a trail of misconfigured votes for some time.
@Nagalim can you give me a private lesson, please?

@masterOfDisaster Is there any setting can avoid the nubot eat the other sideā€™s order that pay 0.25% fee?

Sure: a sufficiently high spread.
But we all want a tiny little snippy teenie-weeny bittie spread, donā€™t we?
Oh, just a second: I for one am in favour of a reasonable spread that offers a good quality at acceptable costs.