-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Payout for Dogecoin Core 1.14.7 release #24
Comments
I have been working on the weights, not fully done yet but am at 95%. Was planning to post it in discussions on the main repo again. Is that ok? |
Just commenting to say I'm out here and following, a list of weighted contributions would definitely help. Do we have better transaction builders than last time or should I be getting mine set up? |
Let me know if anything is needed from my end.
Sincerely,
*Marshall Hayner*
( https://www.metalpay.com ) ( https://www.facebook.com/marshall.hayner ) ( https://www.twitter.com/marshallhayner ) ( https://www.linkedin.com/in/marshallhayner/ )
Sent via Superhuman ( ***@***.*** )
…On Thu, Mar 28, 2024 at 6:24 PM, Ross Nicoll < ***@***.*** > wrote:
Just commenting to say I'm out here and following, a list of weighted
contributions would definitely help. Do we have better transaction
builders than last time or should I be getting mine set up?
—
Reply to this email directly, view it on GitHub (
#24 (comment)
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/ABYWSKUOYLMCCNWTOAF2NS3Y2S7GPAVCNFSM6AAAAABFNV5EIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRWGQZTKNRYGE
).
You are receiving this because you are subscribed to this thread. Message
ID: <dogecoinfoundation/corefunds/issues/24/2026435681 @ github. com>
|
@patricklodder posting a discussion on the main repo sounds great! @rnicoll I'm not aware of any better transaction tools. If you don't mind setting yours up, that'd be great. @marshallhayner warm up your private key perhaps? I'll do the same. I'd like to know which three of us should sign (and we have to get the order correct, as we all know). |
Weights proposed here: dogecoin/dogecoin#3505 |
I'll try to get tooling up and transactions built this week. The tooling should be order-agnostic, and be able to merge everyone's signatures independently. Everyone will need a synced Dogecoin Core 1.21, as it has the RPC support for these transactions, so that's probably the main thing to check meanwhile. |
Correction: I believe only I need a synced client, to generate the raw transaction. Signing does not require the client to be synced. |
I've taken a look at the weightings, seems reasonable at first glance. Is someone able to pull together addresses for participants? My node keeps running out of disk space, but I'll have a fully synced node soon! |
To make this clear - if anyone has any concerns with the proposed list in #24 (comment) please let us know, but as far as I am aware there are no objections. My node was not synced, that's fixed, and I've found the transaction builder. If a list of addresses can be acquired, I can build the transaction and send around for signing. |
👍 from me on the list of contributions and weights. Who has contact information from last time? |
I've checked, I don't think I have contact details any more. I'll can see who has addresses listed on GitHub, over the weekend, but obviously if we can get new addresses that's better. |
ajaxpop, alamshafil, chromatic, martyornot and mishaboar have public addresses. I'm trying to recall exactly who gets payouts, can I confirm my understanding from https://github.com/dogecoinfoundation/corefunds/blob/main/POLICY.md that item 3 reflect ownership of the funds, payouts are still due to the keyholders? Patrick, if I send you the list so far, can you collate with any addresses you know? That also solves the problem of getting your address. I also have total weightings based on the link above, in that sheet. |
All listed contributors.
That's what I intended with that, yes.
I don't know of any current receiving addresses - the last round I did was in 2021 iirc, that's 2.5 years ago - other than the ones you listed, but I can reach out and find out. Warning: I'm on the road for a week and a bit so I will not be fast. |
List I have sent to the last address I have for Patrick, and... well it hasn't bounced so far, at least! |
hey guys, curious what the status is on this. am also wondering if there's anything I can do to help move it along! cheers |
Thanks for the reminder. I'll send my collected info to Ross as I meant to do that a few weeks ago, but I got 2 more responses while I was writing and signing the list - and then forgot to do it after re-processing. |
Acknowledging this is currently with me, I've pulled together both address sheets and am just double checking the payout amounts before I formally propose them. |
Awesome, thanks for doing this guys! |
Transactions signed, confirmed and relayed:
I'll have a reddit post up later today. |
I think that that payout is not related to this repo tho? |
Good point, I've rolled both into this discussion. For corefunds the email with initial transaction is out, although not sure if it's been relayed to chromatic, and as I now have chromatic's email I should do that myself. |
Hello all! Just wondering if there are any updates or there's anything we can do to help out. |
Per my reading of the policy document, the 1.14.7 release has met the threshold for contributor payouts. What do we need to do to make this happen?
I believe it's:
The text was updated successfully, but these errors were encountered: