Jump to content

Monero

  • entries
    225
  • comment
    1
  • views
    24377

General Fund 2020/2021 report


Snider

461 views

First, here is the basic information of the GF wallet. This info has always been public at https://github.com/monero-project/monero#readme but not everyone might know this.
The Monero general fund donation address is: 888tNkZrPN6JsEgekjMnABU4TBzc2Dt29EPAvkRxbANsAnjyPbb3iQ1YBRk1UXcdRsiKc9dhwMVgN5S9cQUiyoogDavup3H.
The view key is: f359631075708155cc3d92a32b75a7d02a5dcf27756707b47a2b31b21c389501. Note you need to use the base address for restoring a view-only wallet, which is: 44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A.

The Bitcoin general fund donation address is: 1KTexdemPdxSBcG55heUuTjDRYqbC5ZL8H.

Current balance in GF wallets: 5637.585152963753 XMR, and 0.09042883 BTC.
This balance has been generally increasing over the last 1.5 year.

I exported all key images, which can be used together with a view-only wallet to see what transactions were spent, and the final balance. You can access them here: https://downloads.getmonero.org/GF_wallet_key_images_until_20210616

Summary 2020

  • Received: 2847.716692 XMR
  • Spent: 896.4505203 XMR

Summary 2021 (until 16/06)

  • Received: 3161.148144 XMR
  • Spent: 211.7867395 XMR

You can find the full list of all transactions since 2016, as well as annotated outgoing transactions for 2020/2021 here: https://downloads.getmonero.org/GF_wallet_report_June_2021.ods

While most donations are anonymous, I know that LocalMonero has been making some. I'll let them give info about that if and as they wish.

Also worth noting that non-monetary donations are made by some companies who are currently paying for some of our infrastructure (see the 'Sponsorships' page). Without them, the cost of resources such as our website hosting, the CDN and its associated bandwidth, etc, would probably be above 10k$/month, so it's effectively saving the general fund this amount every month.

Historically, the GF had been used to complete some CCS proposals that were struggling to be fully funded. However, in 2020 all proposals were funded on their own and hence there was no need for that kind of intervention. In 2021 we decided to always contribute to all proposals that we deem of particular significance to the Monero project, even when it is clear that they can be fully funded anyway; at this time we expect to keep doing so. I would encourage everyone motivated to make that leap and contribute some proposals.

A lot of questions and heated debates have been raised in the last week, including on the role of the General Fund and its purpose/administration. We (the core team) expect to post a clarification on these matters in the coming days.

View the full article

0 Comments


Recommended Comments

There are no comments to display.

Guest
Add a comment...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • HashVault Latest Blocks

  • HashVault Stats

    • Global Hashrate
      403.33 GH
    • Avg Hashrate
      169.90 MH
    • Total Miners
      2374
    • Miners Paid
      48447
    • Total Payments
      1416087
    • Total Hashes
      9.23 EX
    • Blocks Found
      2719394
  • Posts

    • Buenos dias, no se me abre pool monero,des de hace dias. Me comenta al abrir k puede haver cambiado de pagina.alguien sabe algo
    • How can I tell HiveOS how many cores or threads I want to use for mining? My Ryzen 3600 has been lowered to 55w. In order to avoid clogging GPUs, I only want to use 11 threads for mining, with 1 thread for system-specific purposes. fnf
    • ./xmrig --url pool.hashvault.pro:80 --user *** --pass x -a cn-heavy/xhv * ABOUT XMRig/6.17.0 gcc/9.3.0 * LIBS libuv/1.43.0 OpenSSL/1.1.1m hwloc/2.7.0 * HUGE PAGES supported * 1GB PAGES disabled * CPU AMD EPYC-Rome Processor (1) 64-bit AES VM L2:0.5 MB L3:16.0 MB 1C/1T NUMA:1 * MEMORY 0.6/1.9 GB (31%) DIMM 0: 2 GB RAM @ 0 MHz DIMM 0 * MOTHERBOARD Vultr - VHP * DONATE 1% * ASSEMBLY auto:ryzen * POOL #1 pool.hashvault.pro:80 algo cn-heavy/xhv * COMMANDS hashrate, pause, resume, results, connection [2022-05-22 12:49:13.205] net use pool pool.hashvault.pro:80 131.153.76.130 [2022-05-22 12:49:13.205] net new job from pool.hashvault.pro:80 diff 36000 algo rx/0 height 2628998 (7 tx) [2022-05-22 12:49:13.205] cpu use argon2 implementation AVX2 [2022-05-22 12:49:13.207] msr cannot read MSR 0xc0011020 [2022-05-22 12:49:13.207] msr FAILED TO APPLY MSR MOD, HASHRATE WILL BE LOW [2022-05-22 12:49:13.207] randomx init dataset algo rx/0 (1 threads) seed 6ac097ea635e9d1d... [2022-05-22 12:49:13.207] randomx not enough memory for RandomX dataset [2022-05-22 12:49:13.235] randomx failed to allocate RandomX dataset, switching to slow mode (27 ms) [2022-05-22 12:49:13.517] randomx dataset ready (282 ms) [2022-05-22 12:49:13.517] cpu use profile rx (1 thread) scratchpad 2048 KB [2022-05-22 12:49:13.519] cpu READY threads 1/1 (1) huge pages 100% 1/1 memory 2048 KB (1 ms) [2022-05-22 12:49:17.487] net new job from pool.hashvault.pro:80 diff 36000 algo rx/0 height 2628998 (52 tx) [2022-05-22 12:49:20.337] signal Ctrl+C received, exiting [2022-05-22 12:49:20.345] cpu stopped (8 ms I run xmrig and set the algorithm `cn-heavy/xhv`, but it still response `rx/0`.How to solve this problem?
    • Yes, I like the content of this article.  LOL Beans
    • Yeah, it does, but apparently it's not so transparent. So if we > mention that we'd better indicate in the same paragraph that you > probably don't actually want to use it. How about the attached?  UNO Online
×
×
  • Create New...