Hello,

https://foundation.dogecoin.com/announcements/2022-12-31-corefund/

This is not the document that was agreed on. Please fix and publicly announce that a mistake was made.

Per the policy, a minor or minor release needs to meet a threshold of at least 25 pull requests to qualify for a payout. Per my calculation, the 1.14.8 release included 12 pull requests.

I'm opening this ticket to document this fact--and to give any other custodian the chance to correct the record, if my understanding or account is incorrect.

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:

• at least 2 other signers agree
• collect a list of contributions
• evaluate the contribution weights
• collect addresses from contributors
• create, sign, and submit the transaction

Sorry guys, I accidentally merged this before everyone could ACK, are we all in agreement on the policy?

Hi! I have my keys ready for over a day now, but I am waiting on the purpose & policy text to be put here. Unfortunately, I cannot provide keys when there is no strict publicly documented policy text - people usually don't provide signatures before the contract is made up where I am from, but perhaps I truly am alien and preemptive signing is an actual thing. Nevertheless, I'd rather be alien in that case. Apologies.

I need a decision from the collected group. Once we have a multisignature address ready to go, we need an agreed protocol for signing. Specifically, we’ll need tools to generate the unsigned transaction, the individual signatures, and compose them into a final transaction to relay.

There are two toolchains that I am aware of, which can be used to signing a spending transaction from a multisignature address on Dogecoin:

• Patrick’s https://github.com/patricklodder/devfundtx tool, which was used for initial payouts.
• Dogecoin Core 1.21, which has been successfully used for recent 1.14.x payouts.

Generally I favour the former, but it requires more work from Patrick, so I wanted to list the pros and cons and get feedback.

The Dogecoin Core 1.21 tool chain has three main drawbacks:

• The tool to build the transaction in the first place is not yet open source - due to when it was written it’s under copyright by my employer, and while I’ve started the process to open source it, that’s likely to take 2-3 weeks due to approvals.
• The generally used version of Dogecoin Core 1.21 for signing is based on an experimental branch. In theory the latest development branch should work, as the node is just being used as a signing tool and so does not require most of the Dogecoin adjustments to be in place.
• By design Dogecoin Core won’t include more signatures than necessary, in order to avoid blockchain spam. Meaning for a 3/5 address it will at most include 3 signatures in the transaction.

These are manageable; the generated transaction can (and should) be verified by each individual signer before signing, and therefore the lack of the source to the transaction build tool should not be a substantial issue. The development branch of 1.21 should work for signing, as it does not need to sync, although we'd need to confirm this or use the experimental version. The signatures issue can be handled by the keyholders recording their signatures outside of the blockchain for the record.

On the other hand Patrick’s tools are stand-alone and therefore easier for individuals to confirm the validity of, however this would push maintenance work onto Patrick, so I’m cautious to ask that.

What do others think?