Filipe Azevedo

I provided architecture and leadership of an ambitious project with multiple components and blockchains. The project includes a tool for minting as a service, an NFT marketplace, and a ticketing sale system. All components have some form of multiple chains involved. I also provided tech leadership for the tech team with hands-on contributions and code reviews.

I did technical architecture for a project similar to https://pooltogether.com/ on Solana. I contributed to the technical direction and management of the project team responsible for the on-chain components. I implemented both on-chain and off-chain components.

Discovery phase completed for a new NFT marketplace, with staking and rewards mechanics.

Definition of technical architecture using the latest standards used in the Solana community.

Whitepaper review.

Part of the team responsible for maintaining the marketplace back-end, helping improve marketplace experience, and rollout new contracts.

• Development of new contracts
• Contract maintenance
• Near real-time indexing of Solana accounts and marketplace listings

I built an exploratory proof of concept (POC) on understanding the effort of adding a Cosmos ingestion option to a graph's node. The goal was to improve the understanding of the technology and learn rust simultaneously.

A bank-as-a-service platform that provides an API for integration. Part of the core services team responsible for integration with MTF (multilateral trading facility). The platform makes heavy use of asynchronous flows, GCP, Go, and Kafka.

A back-end service that consistently tracks IBC connections going through the Cosmos Hub and produces events in order to generate insights about the flow of tokens coming into or out of the hub. The services use AWS services, Go, Gaia, and NATS.

A microservice-based platform that provides an API for mobility partners—like SNCF and Booking.com—with cab trip booking and quoting capabilities. This platform was heavily asynchronous, dealt with about 40 (at the time) traditional dispatch management systems. The platform was responsible for maintaining the state of trips in sync with partner platforms, trigger actions like vehicle tracking, notifications, payments as well anomaly detection. All the microservices were written in Go and relied on Google Cloud Pub/Sub and Kubernetes as well as Redis.

An IoT platform that is responsible for onboarding and managing a few different IoT device models. The platform made heavy use of AWS services, including AWS IoT, Kinesis, and Lambda. The project was developed using multiple languages, including Scala, Kotlin, and Go.

I acted as the core developer of the graph protocol. The Graph is an indexing protocol for querying networks like Ethereum and IPFS. Anyone can build and publish open APIs, called subgraphs, making data easily accessible.