Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Add tipping addresses for each of the core dev.'s on development.html #365

Closed
pinheadmz opened this Issue Apr 8, 2014 · 13 comments

Comments

Projects
None yet
6 participants

No description provided.

Contributor

saivann commented Apr 9, 2014

Two possible issues:

  1. Some contributors might suddenly want to be listed as well and accepting this could defeat some purposes of this list (e.g. responsible disclosure).
  2. Some developers are already paid by the Foundation, Bit-Pay, etc while others are not.

Otherwise, I think it's mostly up to them.

Seriously, why not just put out there that you are already using tip4commit for the project ~
as shown at: http://tip4commit.com/projects/2
It's out there, it's being used, the contributors sign up however they wish to sign up to donate at tip4commit, or people can just send to the donation address without signup. As you can see it has been used for some time so that bitcoin developers can receive donations, you can see how much they are receiving, and which developers have received donations for commits, and so on.
The logical question then becomes where should this particular link be placed so that more people are aware of it?
You may also want to check out Bithub which is authored by Open Whisper Systems:
https://github.com/WhisperSystems/BitHub
Either way, it's really just a question of where to you put it (particularly in the case of the tip4commit item which is already being used to support bitcoin development) so that more people are aware of it and click on it so that the bitcoin devs get more support. In turn, everyone benefits.
Cheers

Contributor

gmaxwell commented Apr 14, 2014

I do not support or endorse tip4commit or any other service that collects funds on behalf of third parties, especially without their consent or permission.

Contributor

saivann commented Apr 15, 2014

Well, I think developers can ask for this or publish this change by themselves if they are interested. It's really just up to them. So I'm closing the issue, thanks for submitting the idea regardless.

@saivann saivann closed this Apr 15, 2014

Contributor

luke-jr commented Apr 15, 2014

tip4commit, while a great idea, does not allow donators to direct their donation to a specific person; it also takes a fee. That being said, I don't think we need to put the donation addresses on the webpage, if for no reason other than setting a good example by not reusing addresses that prominently. We could put a HD wallet-based thing possibly, but I doubt that's worth the effort...

Contributor

greenaddress commented Apr 15, 2014

@luke-jr using an HD wallet is great but how would it work? Would you allow users to generate new addresses off the master public themselves?

How do you avoid address reuse in a distributed manner without requiring users to use unique branches and to send you the branch used in the HD wallet?
If there is some solution to this, does it mean we have to give up on privacy as anyone would be able to track the transaction from the master?

Is the other solution to use a third party that has your master public and can generate new addresses automatically for anyone that has your 'id'?

We implemented it a while ago and you can see the feature from the zealdocs home page for instance (i.e. if you refresh the address changes) but I'm very keen on having some standard while keeping the highest levels we can of security/privacy.

Contributor

luke-jr commented Apr 15, 2014

@greenaddress The website engine would generate a new address per visitor.

I would like to ask that this be re-opened, if it is not re-opened, then I believe I have a new issue, since this issue has not been discussed sufficiently. Very little time has passed since developers have weighed in, and since some developers have said they don't like tip4commit, I wanted to offer some possible alternatives, but now this issue is closed. If @pinheadmz or @saivann would like to reopen, great. If not, I'll open a new issue to discuss alternatives.

Contributor

saivann commented Apr 15, 2014

@ABISprotocol As explained, bitcoin.org isn't the right place to contact developers, not all of them follow each change on bitcoin.org AFAIK. The issue doesn't have to be open for you to link to it.

After the release of 0.9 and 0.9.1 I was just looking for a way to support the devs and share that channel on reddit, etc. I sent a donation to the bitcoin foundation, maybe this is just the best way -- although it has both the problems of a third party money relay, and also a single reused static address.

Please note for full disclosure,

  1. I am in one of my capacities a member of the Bitcoin Foundation (Education Committee) and this issue has come up before there in discussion where we have contemplated and discussed how can we best support those who are working many hours on bitcoin? (We have also discussed what might be some reasonably good ways to contact different core devs specifically to seek their input on the matter of seeking their counsel for how to support them.)
  2. Please note that on https://bitcoin.org/en/about-us it clearly states, "You can report any problem or help to improve bitcoin.org on GitHub by opening an issue or a pull request in English." ( Included in that text is the following link: https://github.com/bitcoin/bitcoin.org#how-to-participate ) Until such time as someone may in the future modify https://bitcoin.org/en/about-us to actually remove the recommendation to contribute via github, people will continue to do so here, and rightly so. There is no expectation that we will be contacting all developers here. I see this issue remains closed so I will open a new issue after contemplating this further. Thank you for your thoughts.
Contributor

saivann commented Apr 15, 2014

@ABISprotocol Your involvement in appreciated, I think you just didn't understand my answer: that is up to developers to choose if they want to raise funds on bitcoin.org or not. If they want it and it's done right and potential issues are correctly discussed, why not? I don't mind keeping this issue open, but I don't think this will be of any help.

@saivann Thank you. I've opened an issue related to this (but after a bit of contemplation, as noted above, have modified somewhat the idea and will see what comes of it in the issue area). @luke-jr mentioned an HD wallet-based concept. Perhaps this can be explored further in the new open issue in the bitcoin/bitcoin area.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment