Coordinape Pipeline
Assign
Data Source
Priority
Status
Description
Estimated Completion
Tags
Property
Jan 30, 2022
- Manually created
coordinape_name_address
table in postgres containing participants from 4 coordinape rounds (circle_id: 24, 305, 492 and 878)
Feb 2
- Documented Coordinape API connection: https://github.com/BanklessDAO/analytics/blob/main/daodash/etl_pipeline/coordinape/coordinape_establish_api_connection.py
Feb3 :
When this is live, it should (Adhere to Data Dictionary Standards) and be pointed to new DB
- Explore: get names of Bankless DAO Rounds (etc. guild level, project level) through Coordinape API
Feb 9: Update - getting access to circle_ids could be a manual process , details: https://discord.com/channels/834499078434979890/931392976737927219/940786285214302228
- Zashton suggests coordinape circle admins add
0xBE2De66882ACFeA5c13212b589379e95d976893c
to the circles we want to gather data on
- we need to figure out who the circle admins are
Coordinape Circle Details
Aggregating details to figure out who the circle admins are
circle_id | name | protocol_id | admin |
24 | bankless (DAO wide) | 15 | RedVan |
63 | BanklessDAO Bounty Board | 15 | ㅤ |
305 | L1 | 15 | ㅤ |
492 | L2 | 15 | ㅤ |
878 | Guest Pass | 15 | ㅤ |
ㅤ | Education Guild | ㅤ | RedVan |
ㅤ | Bankless Academy (BA) | ㅤ | RedVan |
ㅤ | ㅤ | ㅤ | ㅤ |
ㅤ | ㅤ | ㅤ | ㅤ |
Mar 4:
Update: Add 1 additional circle_id (63) (see previous entry at Jan 30th)
Coordinape Circle Admins:
- Thread within dao-dash-channel: https://discord.com/channels/834499078434979890/948765489323192402/948766753012457472
