Invoice #278625 to Lawnchair
[Bounty]: Android 16 rebase completion
Paid
Invoice #278625
Maintenance and Development
Dec 19, 2025
Expense Details
Invoice items
Bounty for the architectural rebase and integration of the Android 16 (AOSP) codebase. https://github.com/LawnchairLauncher/lawnchair/pull/5543
$500.00 USD
Total amount
$500.00 USD
Additional Information
Paid to
NullCube@nullcube
payout method
Bank account
Details
********Collective balance
Expense policies
Expense policies
File an invoice only when you are requesting payment for services you personally performed. We can only pay the individual who completed the work -- no third parties or friends. The person who performed the work must be the owner of the account receiving payment.
We have strict requirements for what we can and cannot process. Certain information is required on all invoices, and we cannot process payment if required information is missing.
Please review our full policies before submitting:
https://docs.oscollective.org/for-hosted-member-projects/spending-money-and-getting-paid
https://docs.oscollective.org/for-hosted-member-projects/spending-money-and-getting-paid
If your expense is missing required information or documentation, you will be asked to revise it before processing can begin.
Processing and Payment:
- Expenses are processed twice weekly after approval by a Collective administrator and a secondary OSC review
- Payments are made via PayPal or Wise (bank transfer)
- Payments are limited to countries supported by these providers
- If you use PayPal, you may be required to complete a KYC process
An uploaded invoice is not required -- the information entered in the expense form is sufficient.
If you choose to upload an invoice, address it to:
Collective/Project Name, Open Source Collective
440 N. Barranca Avenue #3939
Covina, CA 91723, USA
Use the "Invoice" option for direct payments for your contributions to the project. This includes:
- Quarterly Contributor Grants: A standardized, retroactive grant awarded for your consistent and high-impact contributions during a calendar quarter.
- Bounties: A pre-defined payment for completing a specific, publicly-advertised task (e.g., a major feature or critical bug fix).
All grants and bounties must be discussed and agreed upon with the project lead before an invoice is submitted.
View more info about the expense categories
View more info about the expense categories
FAQ
How do I get paid from a Collective?
Submit an expense and provide your payment information.
How are expenses approved?
Collective admins are notified when an expense is submitted, and they can approve or reject it.
Is my private data made public?
No. Only the expense amount and description are public. Attachments, payment info, emails and addresses are only visible to you and the admins.
When will I get paid?
Payments are processed by the Collective's Fiscal Host, the organization that hold funds on their behalf. Many Fiscal Hosts pay expenses weekly, but each one is different.
Why do you need my legal name?
The display name is public and the legal name is private, appearing on receipts, invoices, and other official documentation used for tax and accounting purposes.
Collective balance
$2,144.46 USDFiscal Host:
Open Source Collective