Conversation

GrapheneOS is entirely funded by donations. Donations fund multiple full-time developers, workstations, development phones, servers, legal fees and other expenses. We'll be forming a non-profit organization in Canada for receiving/distributing most of the donations in the future.

142

GrapheneOS

@GrapheneOS

Jan 29

There are currently 5 ways to donate: * Bitcoin * Monero * Credit card via GitHub Sponsors (Stripe) for either one-time or recurring payments of any amount * PayPal (prefer GitHub Sponsors if possible) * Interac e-Transfer from a Canadian bank account

grapheneos.org

GrapheneOS donations

Donating to support development of GrapheneOS.

GrapheneOS

@GrapheneOS

Jan 29

We plan to add support for Lightning donations in February, starting with Keysend support. We don't want to expend resources handling cryptocurrencies other than Bitcoin and Monero without a compelling reason. Zcash shielded address will likely be added once Trezor supports it.

Replying to

Great to hear, consider

@BtcpayServer

for easy on chain + lightning payment processing with numerous cool features ontop.

Replying to

and

We're likely just going to run lnd + btcd + loopd ourselves and publish a keysend address. Ideally, keysend would be more broadly supported beyond lnd and c-lightning themselves. Breez (lnd and neutrino) supports it. Maybe it's fine to only support keysend. It's a nice approach.

Replying to

and

I think it's good enough for now. Bolt 12 enables superior static invoice UX, especially for donations. That feature is already implemented in c-lightning (and WIP in eclair), but I don't know if lnd is going to integrate it any time soon. There's little wallet support though.

Replying to

and

Keysend is really nice because we can simply publish our lightning address and receive donations similar to publishing a static address for Bitcoin and Monero. It's unfortunate that it isn't broadly supported because we would prefer to avoid invoices altogether for donations.

Replying to

We're aware that only having a static address for Bitcoin means people can see the source of the donations directly but simply using dynamic addresses and then having them combined together as multiple inputs when we distribute money to developers or consolidate it would ruin it.

8:01 PM · Jan 30, 2022Twitter Web App

Replying to

and

The beauty of Bolt 12 is that you get both! It's a privacy preserving static payment request. It can also negotiate recurring payments. bolt12.org

Replying to

and

This looks quite good and we'll definitely support it once lnd adds support for it. It's appealing for the same reasons as keysend. We looked at lnurl and lightning addresses and didn't like that we'd need a web service and that it'd end up strongly tying it to our website / DNS.

Show replies

Replying to

It's nice that for Monero we can simply post a static address from a hardware wallet while having privac for donors. We're interested in better approaches than a static address but BTCPay Server is overkill for us, complicates hardware wallet use and privacy is still an issue.

Replying to

Check out cypherpunkpay.org It's a lightweight BTCPay alternative

Show replies