I am ok either way. Paying the FLOT by the FLOT seems a bit odd but voting for 8 grants is a bit too much, and very unscaleable.
In either case FLOT members should post addresses where they wish to receive funds.
1 Like
I prefer a single motion/grant where shareholders vote to pay all FLOT members, either through a grant or out of the NBT FLOT multisig, if there are objections/complaints towards a specific FLOT member the same topic could be used. 8 different motions seems like an unnecessary waste of FLOT and shareholder time.
Edit: Payment receiving address @Dhume : B9oFTqTqduqKKRcxHndyHzqbV9HRQjZVYu
1 Like
We can’t use the same custodial address twice. Creating one has some overhead; we might just rearrange the pubkeys to get a new one though.
If we’re doing motions anyway we can consider setting up a motion where we ask shareholders to pay ourselves out of T4 funds every 90 days until further notice.
Again, multiple feed support or alike would let multiple grants scale. I’m fine with having FLOT pay FLOT for now, but I want to establish a long-term solution. Please say why if you disagree with me.
I also think we shouldn’t have to shy away from multiple threads, because it would be difficult to keep track of the different members’ compensation discussions, and as Nu grows there will inevitably be more threads anyway.
We could have a category for them. No, I don’t like too much fragmentation either, but if it’s necessary. It’s possible to hide categories from the Latest view by going into the category → Edit → Settings → [X] Suppress this category from the homepage. (may need to be the startpage)
With multiple feed support, or simply a way to input multiple grants/motions at a time, shareholders could find a feed or compilation thread and vote for all of them in one action.
Is URI scheme links a bad idea? I.e., something like the following:
nu:grant:BT9AWq9r1i6kghZc6LtrvNb2wRFh7JLCdP:100000nu://grant/BT9AWq9r1i6kghZc6LtrvNb2wRFh7JLCdP?amount=100000
Perhaps I should split this out to a new thread.
It appears to be going in the direction of a motion letting FLOT pay FLOT.
Compensation for FLOT - jooize #1 (2015-11-18 to 2016-02-16)
Address: B9dQqqjoX81jLBecRwCEYXSYJgQdYXeLfN
Amount: 435 US-NBT
Compensation for FLOT - mhps #1 (2015-11-19 to 2016-02-17)
Address: BBxdEgU93Lb5UNtiWVPRSnDjXhtkcxvnnV
Amount: 435 NBT
1 Like
Because I think it is bad practice.
Each individual should ask for a custodial grant and get it pass in the same way as each FLOT member had to pass a motion to become a FLOT member but I think it would be acceptable for the first payment to use FLOT and T4 as pointed out by @masterOfDisaster since T4 does not deal only with liquidity operations.
I will post my NBT address within 10h from now.
Can somebody please explain why a motion is considered necessary to execute a payment that is based on a motion that has passed long ago?
Wouldn’t it make more sense to
- remove FLOT members who failed to act according to the terms by motion and
- continue the FLOT memberships like stated in the terms (including payments)?
Why is it bad practice? Is there some attack vector I’m not seeing? Is there even a slippery slope argument for this? The amount of compensation is clearly defined.
I will do so, too - soon.
Because then FLOT could reward say, NuLagoon: NuLagoon could pass a motion asking FLOT to pay for its monthly compensation instead of passing a custodial grant.
To me the only argument that is in favor of using FLOT for FLOT compensation is because it is very efficient compared to passing 8 separate grants.
My NBT address for receiving the compensation: BTZtxMx6yfbNzL1jdqPFZnJJYtNZzHuFnx
Rewarding NuLagoon via FLOT would require NuLagoon to report to FLOT with a monthly compensation report and FLOT to accept it via consensus. Good point though, that is the slippery slope argument; my rebuttal being that a fixed signer compensation is different than a variable amount.
Efficiency is the name of the game. Think about it this way: we don’t want to wear our shareholders out. The lower the number of consensus statements we require the better the quality of those statements will be.
Compensation for FLOT - woodstockmerkle #1 (2015-11-19 to 2016-02-17)
Address: BA5xfjKc8hq7zJSJmaGVCLZkvg5dduEgME
Amount: 435 NBT
Submitted payment addresses
✓ cryptog
✓ Dhume
✓ dysconnect
✓ jooize
✓ masterOfDisaster
✓ mhps
✗ @ttutdxh
✓ woodstockmerkle
I’ve seen no feedback to my ideas about prioritised multiple voting feeds*, and I think no particularly strong arguments against FLOT paying FLOT have been made. We are already handling a lot of Nu funds anyway, and shareholders are free to present a motion to discontinue the service of any FLOT member.
I can agree with this.
Assuming this is OK, should FLOT create one transaction for all of these, or only for the ones overdue or imminent, and wait a while with the rest? Not sure of the time periods, perhaps all are near the end.
3 Likes
A lot of mental loops will need to be made to make something out of all those separate proposals. I suggest a motion or proposal from FLOT to align payments and dates including any deviations from the standard availability. That would greatly contribute to transparency imo. We now face a patchwork which is almost impossible to monitor by anyone and therefore we need to basically rely on self governance from FLOT.
My take on this is as follows:
We already put up the motions for our commitments and our compensations, and we received the necesary support. Shareholders voted for that. That included a payment schedule. Now it is just part of that contract for Nu to pay FLOT. This is a payment, not a vote. If any concerns are to be raised against any part of the procedure, motions are there, anytime. Motions mandate payments, FLOT executes payments.
I have seen this happen in the past, and I think that payments approved by motions should not be subject to another vote(grant). In the past we have done it because we did not have FLOT, but now we do. Let’s not convert the solution to a problem into the problem of a solution.
Regarding the payment method: my idea would be to pay directly into each public key used for FLOT signing in NBT(the ones that do not sign NBT should create a public key for NBT that will be used in the future for this payments and be ready for a possible inclusion in the group with that key, just in case, or reuse the one from other group). That way we avoid mistakes, risks and it is much easier to account.
2 Likes
I’d rather sign with a key that never has significant fund in it. Who knows what might happen to the keys that are used for signing often. Speaking from experience.
2 Likes
I am not saying to use it as a day to day address. Only as a “entry” gateway for these payments. You can then send the funds to your other addresses.