-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Q1 2019 Funding Transparency Report #114
Merged
+90
−0
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,90 @@ | ||
# 2019Q1 Funding Transparency Report | ||
|
||
Last updated: May 02 2019 | ||
|
||
## Introduction | ||
This document provides a high level overview of Grin's financials for Q1 of 2019 (Jan 01 - Mar 31). The purpose is to keep the community up to date on funding activity in transparent and digestible way. This is the first attempt at such a report, and is based on financial logs that was introduced during the quarter. | ||
|
||
### Notes | ||
|
||
1. Data was up to date at the time of writing, but it's still possible that there have been changes and updates in the logs since. | ||
2. USD conversion rates are derived from the closing price of the asset on the day in question according to Coinmarketcap.com unless otherwise stated. | ||
|
||
|
||
|
||
## Status before the period | ||
|
||
At the end of Dec 31 2018, Grin held the equivalent of $65,237.35 in the following assets: | ||
|
||
Currency | Amount | USD x-rate Dec 31 2018 | USD Equivalent | Wallet address(es) | ||
|---|---:|---:|---:|---| | ||
BTC | 17.34294023 | 3,742.70 | $64,909.42 | 3ChVP627KU5w4zu2rieFPF3wGXWQgmhvrs <br />bc1qdgs8vkpzr256qjlzlfht72z3mhcrdrt6wj2rfjw39j8us24gz8uq78qj65 | ||
ZEC | 5.8 | 56.54 | $327.93 | t1QGYYXan3HHEuiPEfccKnUuWEP4CsVvPA5 | | ||
| | | | $65,237.35 | | ||
|
||
### Comments | ||
* These were primarily donations towards [Grin's Security Audit](https://grin-tech.org/sec_audit). | ||
|
||
## Received in the period | ||
|
||
During Jan 01 - Mar 31 2019, Grin received the following assets: | ||
|
||
Currency | Amount | Wallet address(es) | ||
|---|---:|---| | ||
GRIN | 10,091.51336 | N/A | ||
BTC | 16.69418862 | 3ChVP627KU5w4zu2rieFPF3wGXWQgmhvrs <br />bc1qdgs8vkpzr256qjlzlfht72z3mhcrdrt6wj2rfjw39j8us24gz8uq78qj65 | ||
USD | 3600 | N/A | ||
|
||
### Comments | ||
* This does not account for BTC 16.30469134 received as a change output following a spend transaction. | ||
* Main income came from donations towards [Grin's Security Audit](https://grin-tech.org/sec_audit) and to the [Grin General Fund](https://grin-tech.org/general_funding). | ||
* The USD raised came from Blockcypher/Grinmint as a result of their organization of the [grincon.us](https://grincon.us) event. | ||
* Some additional income attributed to this period was due but had not yet hit Grin's accounts, for example from the organizers of the Grin Amsterdam meetup. | ||
|
||
|
||
### Additional (unaccounted for) income | ||
In the same period, @yeastplume also conducted a successful [fundraising campaign for his work in the period March - Aug 2019](https://grin-tech.org/yeastplume). | ||
|
||
According to @yeastplume's own records he raised €66,580 of the €55,000 Target Goal, (amounts as of Feb 3rd, 2019): | ||
|
||
|Currency| Amount | EUR Equivalent| | ||
---|---:|---:| | ||
BTC | 17.41 |~€51,900 | | ||
ETH | 148.53 | ~€13,700| | ||
GRIN | 207.0 | ~€950 | | ||
| | | ~€66,580 | | ||
|
||
|
||
## Spent in the period | ||
|
||
During Jan 01 - Mar 31 2019, Grin spent the following assets: | ||
|
||
Currency | Amount | Wallet address(es) | ||
|---|---:|---| | ||
GRIN | 9,593.296153967 | N/A | ||
BTC | 4.482 | 3ChVP627KU5w4zu2rieFPF3wGXWQgmhvrs | ||
USD | 3600 | N/A | ||
|
||
|
||
### Comments | ||
* This does not account for a BTC 16.30469134 spend (that was then received) as a change output following a transaction. | ||
* GRIN was spent as a partial [donation to Ignotus Peverell for their work on the project](https://github.com/mimblewimble/grin-pm/blob/master/notes/20190312-meeting-governance.md#decision-funding-for-ignotus-peverell). They are due to receive an additional ~$4,000 equivalent's worth of Grin. | ||
* USD was spent on Discourse fees for https://grin-forum.org. | ||
* BTC was spent as up front [payment to Coinspect to initiate their work on the security audit](https://github.com/mimblewimble/grin-pm/blob/master/notes/20190212-meeting-governance.md#decision-security-audit-firm). | ||
|
||
## Status after the period | ||
|
||
At the end of Mar 31 2019, Grin held the equivalent of $123,423.73 in the following assets: | ||
|
||
Currency | Amount | USD x-rate Mar 31 2019 | USD Equivalent | Wallet address(es) | ||
|---|---:|---:|---:|---| | ||
GRIN | 498.217203 | 3.51 | $1,748.74 | N/A | ||
BTC | 29.55512885 | 4,105.40 | $121,335.63 | 3ChVP627KU5w4zu2rieFPF3wGXWQgmhvrs <br />bc1qdgs8vkpzr256qjlzlfht72z3mhcrdrt6wj2rfjw39j8us24gz8uq78qj65 | ||
ZEC | 5.8 | 58.51 | $339.358 | t1QGYYXan3HHEuiPEfccKnUuWEP4CsVvPA5 | | ||
| | | | $123,423.73 | | ||
|
||
### Comments | ||
* Some minor beneficial movements in currency exchange rates. | ||
* A bit portion of the assets will be paid to Coinspect as part of the completion of the security audit. | ||
* ~$4,000 owed to Ignotus Peverell | ||
* Some income from the period will be booked in the coming months. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For ease of review, the BTC sum here can be verified in the following links:
https://blockchair.com/bitcoin/outputs?q=is_spent(false),recipient(bc1qdgs8vkpzr256qjlzlfht72z3mhcrdrt6wj2rfjw39j8us24gz8uq78qj65),time(..2018-12-31)&s=recipient(desc),value(desc)#
https://api.blockcypher.com/v1/btc/main/addrs/3ChVP627KU5w4zu2rieFPF3wGXWQgmhvrs?before=556458
There is room for automating the generation of these numbers from the income log and verification using public apis.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's right! Once we are happy with the format, it would be nice to have these reports automated moving forward. Would also be cool if we could auto-monitor our addresses and automatically insert income_log / spending_log entries the moment there is activity. Would you like to take a stab at doing any of that? Or perhaps open issues for them under /grin-pm/ ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Opened #128 for the automated generation of these reports, not sure about your auto-monitor proposal, please go ahead and articulate that in its own issue if you wish.