Add Ethereum address to FUNDING.yml
See original GitHub issueI’d like to see an Ethereum address added to the custom
property of the FUNDING.yml
file for GitHub Sponsors. This would allow a canonical address to send funds to. For example, projects could parse out the address and provide donation capabilities to the user.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Add Ethereum address to FUNDING.yml · Issue #246 - GitHub
I'd like to see an Ethereum address added to the custom property of the FUNDING.yml file. This would allow a canonical address to...
Read more >Add Ethereum address to FUNDING.yml - - Bountysource
I'd like to see an Ethereum address added to the custom property of the FUNDING.yml file for GitHub Sponsors. This would allow a...
Read more >How to setup a validator for Ethereum staking on testnet GOERLI
If this field is set and valid, the given Eth address will be used to create the withdrawal credentials. Otherwise, it will generate...
Read more >Receiving donations on Github - Unlock Protocol Docs - GitBook
After this, you need to add the lock address from the first step in this tutorial. ... At its root, just a add...
Read more >Setup Lodestar (v1.0.0+) with Docker Compose for ... - HackMD
Ensure you specify an Ethereum address you control. Add/modify this flag to the validator command line on Line 12. An example of a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@lastmjs - Great, let’s talk! Sounds like we serve exactly complementary roles. We hold funds on behalf of projects and specifically take on the legal liability, and handle invoicing, taxes, etc. Can we continue on email to not derail this issue? Send me your thoughts: alanna@opencollective.com 😃
@alanna I’m behind Sustainus, I’d love to discuss. The beauty of the model that Sustainus takes is that it is non-custodial, so everything happens on the client’s machine, and Sustainus hold no funds for the user. This relieves Sustainus of money transmission laws and essentially all legal liability that I know of. Fiat on and off ramps are where the legal issues are, and yes dealing with invoicing and taxes and such become the sole responsibility of the user of Sustainus, so an organization dedicated to dealing with those issues might be very useful