Proposal - Monitoring Tool to Help Identify and Mitigate Recirculating GIVbacks

We made some decent progress the project this week, primarily in two areas: (1) the data site (https://tokenomics.io/giveth) which is now being updated continually. If you’re a data scientist, you may find some of it’s data interesting. We’d love your feedback.

  1. TrueBlocks is now dockerized and will run on dAppNode (although we’ve not yet officially released it).

Some of the Giveth community may be interest in this data for themselves. Who knows, perhaps there are data scientists out there that want to see very on-chain transaction (and trace and log and neighbor and account balance) for all the Giveth projects.

The second thing we’re working on is the ‘scanning the history for circulations.’ I’ve gotten as far as being able to find all the senders to all donors in a round which is the first step. Once we have that list, then we can recursively find the “senders to the senders to the donors” and so on. If there’s an infraction, it will be in the list of senders to senders to senders ad infinitum (or at least back to the start of Giveth). We spent time reviewing the round 17 data by hand. I hope to use the tool to review the round 18 data this coming week.

Just a quick example of what we have so far.

We’ve looked back two levels – so at “senders to donors” from round 17. That is, for each donor, we’ve looked at all the addresses that ever sent into those addresses.

We found that the following projects, which are on the purple list, have sent at least one transaction to one of those donors at some point in the past.

This is very likely totally normal.

It’s likely that these addresses are interrelated. The next goal is to see if any of these gave to a donor who then gave back to them. That code is not yet finished.

31-Giveth:Project    0x2bf034eccebc8cd60dab9c249b6c2996dcb7d8ec    Moloch Cloudship
31-Giveth:Project    0x41cb654d1f47913acab158a8199191d160dabe4a    Coletivo XV
31-Giveth:Project    0x5a9ce898f0b03c5a3cd2d0c727efdd0555c86f81    Shenanigan
31-Giveth:Project    0x6d97d65adff6771b31671443a6b9512104312d3d    Life - New Creation Association
31-Giveth:Project    0x7554f10da3ed7128300577e55abcd8f8835bcee4    Diamante Bridge Collective
31-Giveth:Project    0x8ba6cd4f47e0ad7240287a292cdfe22a4d50e075    BrightID Proof of Uniqueness
31-Giveth:Project    0xdfb0b22940cc45283d639d22ba26aa55ab8bfee8    Crypto Commons Association
31-Giveth:Project    0xedd425359fb15e894c639b6a74112954486146b9    Diamante Luz Center for Regenerative Living
                        0x5b0f8d8f47e3fdf7ee1c337abca19dbba98524e6
                        0x809c9f8dd8ca93a41c3adca4972fa234c28f7714
                        0xe711f474efeb84dd554731b8587b2753d86fe138

This is similar at two levels deep to what Giveth does automatically in their API at one-level deep by checking the purple list directly against donors.

For that one-level view, they system asks, “is the donor on the purple list.” The above asks the question, “does the donor have any senders in his/her past that are on the purple list.”

It’s not quite the same, but it’s progress. More next week…

3 Likes