DuneSentinel

Via Dune API, we've built a parameterized query and notion integration which builds a database that contains the top 10 whale wallets based off transaction volume in the last 4 hours.

Our vision was to create an integration that clearly benefits the user by providing access to actionable insights at the click of the button, all while maintaining the workflow that notion provides. Users should expect to create a new page in notion to host their queries, and navigate to our landing page to paste the page id associated with the page they created. The page id can be located in the url of the notion page after the username label. Once they submit the page id, the api integration begins to populate a database in the notion page. This database contains 10 rows, with columns consisting of the wallet address, total number of transactions in the time period, total volume traded in the time period, and the average transaction value based off of the wallets' total transaction volume and their total number of transactions.

The idea here was how can we make it easy for people who can't afford nansen to obtain whale wallet information and integrate it into their workflow to make the most of the insights. We decided that notion was a great web application suitable for the organization of the type of data we were looking to collect. Using notion, users get their snapshot of the top 10 wallets and are able to perform the same kinds of transformations as they normally would such as relating pages, tagging pages, annotating pages, etc.

Functionality and access are what we were aiming for. We were able to make our application connect end to and and function as desired. However, we did meet some limitations in regards to latency and processing the data between the two apis (Dune, and Notion)

This integration was built utilizing the Dune API (which was a sponsored technology) as well as Notion API. We used Deta to host our serverless application, flask and python3.9 to build the application, html and java script to build our landing page.

We created separate python files to host each api and manage its endpoints. The Dune API is primarily contained in dune.py and it contains functionality to handle the dune api, execute a query, get the response and send that to the main function. The same idea is applicable to the notion api mostly contained in the notion.py file, but the main difference here is the necessity to handle json files which took considerably longer than expected to parse for the requisite inputs for our database.

The Dune api benefited our project because it was extremely simple to plug in to use. Our biggest take away from this has been the cost of processing large volumes of data is very high. Dune queries already take more than a negligible amount of time, and our end to end integration ended up having to time out in about 10 seconds due to limitations in processing power. Overall our review of the product is that its super user friendly, but would be helpful if data retrieval were faster.

This hackathon has been a first for many things. Everyone on my team was participating in their first crypto hackathon, and all but one in their first hackathon. We had a small team of three people and we came up with and built out our idea all within the span of the weekend. We could add some cosmetic work to our code as well as our landing page, but end to end the application works and is easy to use. All of this was impressive, I think we can all say we enjoyed the challenge and look forward to building more in web 3