Personal Polkadot Product Portfolio

Personal Polkadot Product Portfolio

I enjoy working on Polkadot very much. Below are products I've built and currently maintain for Polkadot. Unless mentioned otherwise, these are passion projects I work on in my spare time when I'm not 3D printing random stuff.

Data Analysis for Polkadot - https://dotlake.xyz

DotLake is a project I'm working on with our internal Data Team at Parity. It is a data lake for the Polkadot ecosystem.

The team maintains a better resource here: https://dashboards.data.paritytech.io/

Tech stack: ClickHouse, BigQuery, Python, Py-Substrate-Interface, Substrate Sidecar

Realtime data for Polkadot - https://dotsentry.xyz

DotSentry is infrastructure for realtime monitoring of the Polkadot ecosystem. This is also something I'm working on at Parity.

More information can be found here.

Tech stack: ClickHouse, NATS, Python, Observable Framework

Simplifying transactions on Polkadot - https://tapdot.xyz

Doing something on Polkadot doesn't have to be complicated. This project makes it simple to do virtually anything on Polkadot, without having to use or even understand complicated tooling.

The raison d'être of this tool is to put an end to bad UX in the Polkadot ecosystem.

Tech stack: Flask, Python, Polkadot-JS API, Py-Substrate-Interface

Taxes for the Polkadot ecosystem - https://dottakeout.xyz

This stems out of a personal need: exporting all the transactions for one or multiple accounts that happened accross all the Polkadot ecosystem (50+ rollups).

It is currently in alpha.

An application of dottakeout.xyz is the DOT Score mini application:

Tech stack: SQLite, Flask

DotDeploy - https://dotdeploy.xyz

What can this be? 👀

Tech stack: Ansible, Python

Polkadot forum posts & conversations

A selection of my posts on the Polkadot Forum. These range from data topics to branding topics.

SELECT * FROM polkadot;

Select * from polkadot;
Data, the lifeblood of any worthwhile endeavor, is the central piece in solving the great puzzles of our time. It is the heart of progress and the ultimate arbiter of trust - to us it is the key to answering the question of “Why should I build on Polkadot?”. Understanding the data is paramount to harnessing Polkadot’s full potential as well as making that potential evident to external observers. Parity data team Our newly formed data team within Parity embarked on a quest to build a data wareh…

Pieces of a decentralized Data Lake

Pieces of a decentralized data lake
It’s been 42 days since Decoded ended and we’ve made a long way since then. To this day, the Parity data team is working on follow ups with many of the teams we met then. We’re so excited and happy to see the growing momentum around data and infrastructure within the Polkadot ecosystem. For those who couldn’t make it, we made a recap with all the videos, slides and topics we addressed during the conference. You can find those here: Parity Data - Polkadot Decoded 2023 One common thread we’re a…

DotSentry: Ecosystem-wide real-time monitoring solution for Polkadot blockchains

DotSentry: Ecosystem-wide Monitoring Solution
With a hint of realtime & open source data access for the ecosystem Introduction Many of the last incidents that happened within the Polkadot ecosystem were reported by ecosystem members & users, in the form of “Hey, there seems to be an issue”. Some examples are: x.com [2024-04-21] Polkadot parachains stalled until next session This certainly isn’t the kind of experience we’re envisioning for Polkadot, which would only worsen if we assume a growing number of even faster upgradeable chain…

One-Click actions on Polkadot chains

One-click actions on Substrate based chains
Hi everyone! Today I’d like to share a very small proof of concept I’ve built over the past weekend. It was an excuse for me to learn a bit more about Rust, Axum and Polkadot.JS API on a concrete goal, doing projects like these is essentially how I learn. After chatting with Santiago & Birdo about it they motivated me to share it here as well. This project is not directly related to the work we’re doing at the Parity Data team. Assume you are in a situation where you want someone to send you…

Polkadot developers

Polkadot Developers
It has now been one year since the development of Polkadot underwent a major transformation. Three distinct repositories were merged into one repository now called Polkadot-SDK, also referred to as the monorepo. While the term Substrate might be familiar to most of you, it might not be to others who are just getting started with Polkadot. In fact many ecosystem resources still refer to Substrate which could lead to confusion especially if one doesn’t know about the history of changes. Added to…

Getting started using Rust and subxt for Polkadot data extraction

Getting started using Rust and subxt for Polkadot data extraction
As part of the Parity Infrastructure & Data initiatives, we wanted to explore how we could use Rust, and more specifically the subxt library maintained by Parity, to work with and extract PolkadotSDK/substrate based chains data for both reading data and submitting extrinsics. For instance, the current version of our data ingest implements a batch ingest approach to storing the blocks in our DotLake, mainly leveraging Python and the excellent py-substrate-interface library. This essentially mean…