[TEMP CHECK] ENS invalid name refund proposal

DAO-Wide General Discussion
36

Update (3rd Nov 2023):

After the DAO stewards spotted one negative refund amount in the refund addresses (-0.01669948333 for 0xe5aa8a233b0fe90ff9d68ba93ced601596992533), I re-analysed my queries and found a few errors.
I fixed the problem, reran the query and here are the diffs.

date count sum avg * appears_once > 0.01 ETH diff
27/06/2023 2973 114.00592800017606 0.03834709989915105 6 5
2/11/2023 2970 113.69976766451629 0.03828275005539269 3 5

NOTES:

  • appears_once means that 6 people no longer receive refund while 3 new people now receive refund
  • > 0.01 ETH diff means that 5 people receive more than 0.01 ETH and other 5 less than 0.01 ETH

The new refund address is updated at refund_addresses_021123 - Google Sheets

The Problems

  1. The original query was missing to include ETHRegistrarController4 registration controller which was introduced about the same time I created this query. The negative refund amount was because two renewal transactions(thisandthis made by the controller was not included in some of the query. These missing two transactions resulted in calculating the remaining amount as May-2023 - June-2023 instead of July-2023 - June-2023 for example. After the recalculation this address now receives instead of 0.04748966914 eth instead of -0.01669948333

  2. While fixing issue 1, I also noticed that some of the subsequent queries weren’t filtering event date by 2023-06-18 04:50:00+00 which was the end of the snapshot voting of the Approval of ENS Name Normalization Standard (ENSIP-15). As the result the original query included events happened between 18th June and 27th June when I ran the query.

The Affected addresses

type address old_total new_total diff
only_old 0x563476aa7b6f95c803a1e0115bd0902b4fb54e07 0.008797745527 0 -0.008797745527
only_old 0x41bf836348e4aa14e17d104731a65f84764ea4d8 0.0117206014 0 -0.0117206014
only_old 0xaf738f6c83d7d2c46723b727ce794f9c79cc47e6 0.01255643498 0 -0.01255643498
only_old 0xfb4bb705f6cb453f2f074b7b68a292a2fc2d3ae3 0.01039915335 0 -0.01039915335
only_old 0xca0d40f0363af5ed67585366ea92f679934066df 0.002318379684 0 -0.002318379684
only_old 0x7760200f89dce1def106c7886b07f4f9265fec85 0.007960011394 0 -0.007960011394
only_new 0x1ecd88d5d96efd2cd8a4d2f35bfb67f8ea61a567 0 0.03007973771 0.03007973771
only_new 0x4c4056ae546fc30f34356bf01c886a23241c9908 0 0.002318374726 0.002318374726
only_new 0x3991e3bd4ebaefc64f358a28e9b286fcbe9efad5 0 0.003420080935 0.003420080935
diff_old 0x8bdf6b52959581c0a8f4e99fa71b2225dc691814 0.3168692337 0.1842716597 -0.1325975739
diff_old 0xa5e0ecb5d075e86c3bf5d1b1042e154fee9a4798 0.7676089028 0.4369534242 -0.3306554786
diff_old 0x41bf836348e4aa14e17d104731a65f84764ea4d8 0.0117206014 0 -0.0117206014
diff_old 0xaf738f6c83d7d2c46723b727ce794f9c79cc47e6 0.01255643498 0 -0.01255643498
diff_old 0xfb4bb705f6cb453f2f074b7b68a292a2fc2d3ae3 0.01039915335 0 -0.01039915335
diff_new 0xf01365133118e3b4af61c83b56a7e180a716482a 0.1119770261 0.1602208216 0.04824379547
diff_new 0x72fddd31d88b262706d0e76f9c4efd898fcd418f 0.03826412052 0.05131973866 0.01305561813
diff_new 0xb1e4aa2f8e615493cfe9bcd9b0be1aed86546d12 0.01294040336 0.0364537346 0.02351333124
diff_new 0xe5aa8a233b0fe90ff9d68ba93ced601596992533 -0.01669948333 0.04748966914 0.06418915247
diff_new 0x1ecd88d5d96efd2cd8a4d2f35bfb67f8ea61a567 0 0.03007973771 0.03007973771

The Full Data

I now updated the full data of the previous one (taken 27th June) and the latest one (taken on 11th Nov).

In addition to the refund_address.csv and refund_name.csv, it also includes refund_names_w_events.csv|json which has the full registration/renewal/transfer transaction history.

If you json query tool like jq you can run the following query to see all the transactions related to the specific refund address

0xe5aa8a233b0fe90ff9d68ba93ced601596992533
cat refund_names_w_events.json | jq '.[0][] | select(.last_owner == "0xe5aa8a233b0fe90ff9d68ba93ced601596992533")| {"time":.event_timestamp.value, event, transaction_hash}'
cat refund_names_w_events.json | jq '.[0][] | select(.last_owner == "0xa5e0ecb5d075e86c3bf5d1b1042e154fee9a4798")| {labelhash,tokenid,"time":.event_timestamp.value, gas_spent, event, last_owner, transaction_hash}'

{
  "labelhash": "0x5f16aa6db31cf35c0daca314ecbe2ad09d2c7e6b1bc363ea3871c432e0f2e9fb",
  "tokenid": "43009767505211382270326623157405683972581973608649774860485959057366492310011",
  "time": "2022-05-16T17:41:16.000Z",
  "gas_spent": 0.0079375999319523,
  "event": "registered",
  "last_owner": "0xa5e0ecb5d075e86c3bf5d1b1042e154fee9a4798",
  "transactionhash": null
}
{
  "labelhash": "0x5f16aa6db31cf35c0daca314ecbe2ad09d2c7e6b1bc363ea3871c432e0f2e9fb",
  "tokenid": "43009767505211382270326623157405683972581973608649774860485959057366492310011",
  "time": "2022-05-16T17:41:16.000Z",
  "gas_spent": 0,
  "event": "transfer",
  "last_owner": "0xa5e0ecb5d075e86c3bf5d1b1042e154fee9a4798",
  "transactionhash": null
}
...
1 Like