Skip to main content

πŸ“„ Technical Team Operational Responsibilities

This document outlines the specific operational responsibilities of each member of the technical team. It serves as a reference point to ensure transparency, streamline operations, and maintain continuity, especially during times when members are unavailable.

Table of Contents​

  1. Andre Ogle
  2. Bedirhan
  3. Burak
  4. Emanuel
  5. Hayrettin İletmiş
  6. Juraj
  7. Markus Coetzee
  8. Matej Falat
  9. Matej Poklemba
  10. Mertcan Karik
  11. Prenaam
  12. Serhan
  13. Warren

Andre Ogle​

Operational Responsibilities​

Updated on: 2026-04-01

  • Purinta Waitlist Page Owner

    • Description: Manage and ensure uptime of the Purinta Waitlist Page
    • Dependencies/Prerequisites:
    • Points of Contact:. Emanuel

  • Purinta Lending:

    • Description: Contribute to the development of the Purinta Lending application
    • Dependencies/Prerequisites:
    • Points of Contact:

  • ChainAPI maintenance

    • Description: Maintaining the legacy chainapi.com.
    • Dependencies/Prerequisites:
    • Points of Contact:. Emanuel

  • Signer on the Vault & Agent multisigs

    • Description: Signing multisig transactions
    • Points of Contact:

Bedirhan​

Operational Responsibilities​

Updated on: 2025-05-16 (Last checked: 2025-12-08)

  • Deploying an Airseeker for Nodary self-funded beacons:

    • Description: Nodary employs two primary Airseekers utilizing Reblok as the RPC providerβ€”one for mainnets and another for testnets in the AWS eu-north-1 region. Additionally, there are two redundant Airseekers that leverage carefully chosen public/paid mixed RPC providers, deployed in the AWS us-east-2 region. These redundant setups are re-deployed under various circumstances: when a new dAPI is added, a new chain integration is completed, if one RPC provider experiences downtime or issues, or in the event of any other issues necessitating re-deployment.
    • Dependencies/Prerequisites:
      • Knowing how to use nodaryio/operations repository to create airseeker configuration for Nodary.
      • Having Nodary's mnemonic
      • Having experience or knowledge of which RPC provider is going to be selected for each chain
      • Having AWS account to deploy Airseeker on
    • Points of Contact: Mertcan

  • Managing data feeds integrations or operations for Nodary self-funded beacons:

    • Description: As an API provider, Nodary collects data from various sources and aggregates them. There are responsibilities for managing data, such as adding new data feeds, updating existing ones, or removing them, maintaining the data availability by monitoring sources.
    • Dependencies/Prerequisites:
      • Having access to Nodary staging instance to test changes before deploying to production
      • Having access to Nodary production instance
      • Being familiar with nodaryio/collector repository to add/remove feeds/sources
      • Having access to Nodary's Opsgenie team to be informed about any issues
      • Having access to Nodary's Grafana dashboard to monitor data feeds
    • Points of Contact: Mertcan

  • Integrating new chains doing feasibility tests and running blockchain for new chains:

    • Description: Before integrating a new chain, feasibility tests are required to determine integration feasibility. After the tests, it's necessary to run a blockchain node for the chain (mainnet only).
    • Dependencies/Prerequisites:
      • Obtain tokens, public RPC endpoint, block explorer and its API endpoint for the new chain, and deploy contracts using the nodaryio/chain-feasibility-test repository
      • Check required gas units to update a beacon and verify gas price calculation
      • Deploy a test airseeker (can be locally) to confirm it works as expected
    • Points of Contact: Mertcan

  • Blockchain nodes operations: set up and operate Reblok blockchain nodes infrastructure:

    • Description: Reblok is a blockchain node infrastructure that is used by Nodary and Api3. It is required to set up and operate the infrastructure.
    • Dependencies/Prerequisites:
      • Commitment, with the ability to handle alerts promptly, even in the middle of the night
      • Periodically check for new versions of blockchain nodes and perform updates
      • Resolve unexpected problems, both when initially spinning up a blockchain node client and during maintenance to ensure smooth operation
      • Monitoring blockchain nodes and handling alerts
      • Having access to Reblok's instances
      • Having access to Reblok's Opsgenie team to stay informed about any issues
    • Points of Contact: ...

Burak​

Operational Responsibilities:​

Updated on: 2026-04-01

  • Release DAO dashboard:

    • Description: For https://github.com/api3dao/api3-dao-dashboard/tree/production to appear at api3.eth.limo and dao.api3.org, the vault multisig needs to send a transaction and the Cloudflare page rules for api3.org need to be updated, respectively. DAO dashboard release is a highly security-critical action, as most hacks happen through malicious frontends.
    • Dependencies/Prerequisites: The vault multisig is a 3-of-6 composed of Burak, Emanuel, Bedirhan, Andre, Ugur and Erich. Refer to the platform registry to find out who has access to Cloudflare.
    • Points of Contact: Emanuel
    • Note: I'm expecting to be excused of this responsibility. However, I won't remove it until someone else handles it at least once.

  • Enter payment information for platforms:

    • Description: Currently, Erich's Varia LLC provides us with a credit card to pay for platforms. The information for that needs to be entered at the platforms.
    • Dependencies/Prerequisites: One needs access to the credit card info to be able to do this. Burak has that, alternatively Erich can be invited to the platform and enter it himself, though that is sometimes not supported (no team feature, only the admin can update payment information, etc.)
    • Points of Contact: Erich
    • Note: I'm expecting to be excused of this responsibility. However, I won't remove it until someone else handles it at least once.

  • Create accounts during onboarding:

    • Description: While onboarding a new teammate, we need to create a Google Workspace account, send that account a Slack invitation, and invite the person to the Github organization (and the "Technical" team, most likely).
    • Dependencies/Prerequisites: Multiple people have admin privileges on these platforms.
    • Points of Contact: Refer to the platform registry for the admins that can do these.
    • Note: I'm expecting to be excused of this responsibility. However, I won't remove it until someone else handles it at least once.

  • Docs for dApps:

    • Description: The dApp-facing docs (https://docs.api3.org/dapps/) need to be kept strictly accurate and complete.
    • Dependencies/Prerequisites: Need to be in the loop about what we want to show the dApps there.
    • Points of Contact: Emanuel
    • Note: I'm expecting to be excused of this responsibility. However, I won't remove it until someone else handles it at least once.

Emanuel​

Operational Responsibilities​

Updated on: 2025-12-07

TODO

There is an empty link below [signed-api.api3.org]() whose href (signed-api.api3.org) was removed because it did not exist.

  • Managing Api3 Signed APIs

    • Description: Manage Signed API deployments on AWS under the signed-api.api3.org domain. The Signed APIs are deployed across multiple regions due to AWS account limits and forward logs to Grafana Loki. The Signed APIs are also put behind a CloudFront CDN. The deployment files, along with scripts to generate AWS CLI deployment commands, are stored in the signed-api-deployments repository.
    • Dependencies/Prerequisites:
      • Access to the production Signed API AWS account, Grafana Loki, signed-api-deployments repository, and access to Api3 CloudFlare to reset the subdomain.
      • Understanding of the deployment process and the deployment files.
    • Points of Contact:.

  • OEV, curation and Purinta technical lead:

    • Description: Lead the OEV, curation and Purinta efforts. Help with development/reviews as necessary. Last resort backup for everything OEV. related.
    • Dependencies/Prerequisites:
    • Points of Contact:

  • Maintain GitHub, DockerHub, NPM tokens

    • Description: My tokens are used for deployments and releases across multiple services and I'm responsbile for their management, such as periodic rotation and making sure they don't expire without a replacement being configured.
    • Dependencies/Prerequisites:
    • Points of Contact:

  • ChainAPI owner

    • Description: Owner of the ChainAPI service.
    • Dependencies/Prerequisites:
    • Points of Contact:

  • Api3 Market, Website, Market Catalog and Api3 Blog

    • Description: Owner of the market.api3.org and api3.org features, updating dApp aliases and OEV Rewards. Similarly for the Market Catalog and Api3 Blog, although these are completed projects with little to no maintenance.
    • Points of Contact:

  • Handling security@api3.org emails

    • Description: I'm a delegate for the email, allowing me to read/write emails as if I was the owner of the email. This email will get inbound queries for potential security vulnerabilities that need to be inspected and addressed.
    • Points of Contact: Burak

Hayrettin Δ°letmiΕŸβ€‹

Operational Responsibilities:​

Updated on: 2026-04-03

  • Chain Integration

    • Description:
      • Adding new chains to chains repo.
      • Testing Api3 contracts on new chains
      • Finding additional RPC providers
    • Dependencies: none
    • Points of Contact: @Bedirhan @Burak

  • Manager Multisig Maintainer

    • Description:
      • Maintaining MM repo to ensure seamless and safe signing experience
    • Dependencies: none

  • In-house Tool Development

    • Description:
      • Developing and maintaining tools that used in organization
      • @api3/logos
      • sponsor-wallet-tracker
      • active-dapi-tracker
      • Airfeeder mobile app

  • Keycard Integration

    • Description:
      • Integrated the Keycard protocol to add a hardware-grade security layer to wallet applications.
      • Tailored and aligned the implementation to fit seamlessly within Api3’s repositories and development standards.

  • Morpho Liquidation Monitoring

    • Description:
      • Developing and maintaing liquidation tools for Morpho operations

Juraj​

Operational Responsibilities:​

Updated on: YYYY-MM-DD

  • [Name Of Operational Responsability 1]:

    • Description: This involves...
    • Dependencies/Prerequisites: ...
    • Points of Contact: ...

  • [Name Of Operational Responsability 2]:

    • Description: This involves...
    • Dependencies/Prerequisites: ...
    • Points of Contact: ...

... (Add operational responsabilities as needed)

Markus Coetzee​

Updated on: 2026-04-06

  • Purinta Lending:

    • Description:
      • Development of the Purinta lending platform
    • Dependencies/Prerequisites: None
    • Points of Contact: Emanuel, Andre, Matej Poklemba, Matej Falat

  • oev-dashboard:

    • Description:
      • Active development
      • Monitor alerts raised by Grafana
    • Dependencies/Prerequisites: None
    • Points of Contact: Emanuel

  • api3-market:

    • Description: Help out with maintentenance (either reviews or making changes)
    • Dependencies/Prerequisites: None
    • Points of Contact: Emanuel

  • data-feeds monorepo:

    • Description: Monitor data-feeds monorepo operation (deployments, releases) and review changes to CI
    • Dependencies/Prerequisites: None
    • Points of Contact: Burak

  • Api3 DAO Dashboard:

    • Description: Help out with maintentenance (either reviews or making changes)
    • Dependencies/Prerequisites: None
    • Points of Contact: Emanuel, Burak

Matej Falat​

Operational Responsibilities:​

Updated on: 2025-12-05

  • Purinta:

    • Description:
      • Development of the Purinta lending platform, integrating Morpho vaults
    • Dependencies/Prerequisites: Github
    • Points of Contact: Emanuel, Markus, Matej Poklemba

  • Morpho allocation bot:

    • Description:
      • Development and maintenance of Morpho allocation bot
      • Monitoring Grafana error alerts
    • Dependencies/Prerequisites: AWS, Grafana, Github
    • Points of Contact: Emanuel

  • Morpho curation dashboard:

    • Description:
      • Development of Morpho curation dashboard, implementing configuration checks
    • Dependencies/Prerequisites: Github
    • Points of Contact: Emanuel

  • OEV Searchers:

    • Development of OEV searcher bots

      • Description:
        • Developing OEV searcher bots for various lending platforms
        • Integrating Dex protocols for flashloans and swaps
        • Investigating missed liquidations and debugging other bots' issues
        • Refetching positions in regular intervals and redeploying bots
      • Dependencies/Prerequisites: AWS, Grafana, Github
      • Points of Contact: Emanuel, the OEV team

    • Development of Monitoring service

      • Description:
        • Implementing monitoring sentinels to notify us of critical changes in blockchain state (wallet balances, protocol assets, liquidity in pools, swap price impacts, etc...)
      • Dependencies/Prerequisites: AWS, Grafana, Github
      • Points of Contact: Emanuel, the OEV team

    • Development of Aggregator service

      • Description:
        • Developing service for searching swap routes
        • Researching and integrating usable pools
        • Integrating the service with bots
        • Deploying the service on new chains
      • Dependencies/Prerequisites: AWS, Grafana, Github
      • Points of Contact: Emanuel, the OEV team

    • Monitoring alerts

      • Description:
        • Investigating Grafana alerts from running bots and from monitoring and aggregator services
        • Fixing or disabling alerts, adjusting monitoring config
        • Resetting hardcoded pools for swaps if necessary
      • Dependencies/Prerequisites: Grafana, Github
      • Points of Contact: Emanuel, the OEV team

Matej Poklemba​

Operational Responsibilities:​

Updated on: 2026-04-08

  • Purinta:

    • Description:
      • Development of the Purinta lending platform, integrating Morpho vaults
    • Dependencies/Prerequisites: Github
    • Points of Contact: Emanuel, Markus, Matej Falat

  • OEV Searchers:

    • Development of OEV searcher bots

      • Description:
        • Developing OEV searcher bots for various lending platforms
        • Integrating Dex protocols for flashloans and swaps
        • Investigating missed liquidations and debugging other bots' issues
        • Refetching positions in regular intervals and redeploying bots
      • Dependencies/Prerequisites: AWS, Grafana, Github
      • Points of Contact: Emanuel, the OEV team

    • Development of Monitoring service

      • Description:
        • Implementing monitoring sentinels to notify us of critical changes in blockchain state (wallet balances, protocol assets, liquidity in pools, swap price impacts, etc...)
      • Dependencies/Prerequisites: AWS, Grafana, Github
      • Points of Contact: Emanuel, the OEV team

    • Development of Aggregator service

      • Description:
        • Developing service for searching swap routes
        • Researching and integrating usable pools
        • Integrating the service with bots
        • Deploying the service on new chains
      • Dependencies/Prerequisites: AWS, Grafana, Github
      • Points of Contact: Emanuel, the OEV team

    • Monitoring alerts

      • Description:
        • Investigating Grafana alerts from running bots and from monitoring and aggregator services
        • Fixing or disabling alerts, adjusting monitoring config
        • Resetting hardcoded pools for swaps if necessary
      • Dependencies/Prerequisites: Grafana, Github
      • Points of Contact: Emanuel, the OEV team

Mertcan Karik​

Operational Responsibilities:​

Updated on: 2026-04-03

  • API Integrations:

    • Description:
      • Technical contact with API providers for integration and troubleshooting.
      • Integration and evaluation of new APIs and data feeds.
      • Developing and maintaining the api-integrations main repository.
      • Maintaining CI pipelines, api-integrations/frontend service.
      • Developing and maintaining API integrations related deployment files (CloudFormation templates, Docker compose files etc.)
      • Deploying mock Airnode feeds for monitoring, surveying, and testing purposes.
      • Maintaining api-integrations related tests.
      • Surveying and analyzing API/data providers.
      • Scheduling operational actions required for providers.
      • Preparing OIS files and assisting providers during Signed API & Airnode integration.
      • Being the technical point of contact for provider-related issues.
      • Contacting partners when issues occur (e.g., incorrect values, downtime).
      • Making decisions in collaboration with partner API providers.
    • Dependencies/Prerequisites: Airnode feed, Signed API, API access credentials.
    • Points of Contact: Gio, Emanuel, Bedirhan, Hayrettin, Burak, Prenaam, Serhan

  • API Integration Tools:

    • api-analysis:

      • Description:
        • Code base for evaluating APIs during integration and determining sources for dAPIs.
      • Dependencies/Prerequisites: –
      • Points of Contact: –

    • collectors:

      • Description:
        • Code base for collecting all kinds of data related to API providers and data feeds such as real time data, real time volume data, exchange data.
      • Dependencies/Prerequisites: –
      • Points of Contact: –

    • API Integrations Grafana Dashboard:

      • Description:
      • Dependencies/Prerequisites: –
      • Points of Contact: –

  • Operations:

    • Description:
      • Takes part in Dint, Dre, Dret, Dsur, Fint, Pre, Mnemonic Rotation, Dre-Emergency, provider-integration-* checklists.
    • Dependencies/Prerequisites: –
    • Points of Contact: Hayrettin, Burak, Prenaam, Bedirhan, Serhan

  • Monitoring

    • On-call Monitoring Duty:

      • Description:
        • Responsible for off-chain alerts and secondary person to reach out for on-chain alerts. Able to update data feeds on chain with keycard designed to do it.
      • Dependencies/Prerequisites: –
      • Points of Contact: Hayrettin, Bedirhan, Serhan

    • Telegram Alert Bot:

      • Description:
        • A Telegram bot that checks Signed APIs and sends alerts in case of anything wrong in all data feeds such as stale timestamp, deviation, HTTP errors.
      • Dependencies/Prerequisites: –
      • Points of Contact: –

  • Multisig

    • Description:
      • Signer for manager-multisig.
    • Dependencies/Prerequisites: –
    • Points of Contact: –

Prenaam​

Operational Responsibilities:​

Updated on: 2026-05-08

  • Merkle Tree Signing:

    • Description: This involves reviewing dAPI management, dAPI pricing, and Signed API URLs Merkle trees updates, and signing them
    • Dependencies/Prerequisites: Be a designated signer
    • Points of Contact: MT Signers

  • Data feeds and chains management in Integration pipeline:

    • Description: This involves:
      • Requested dAPIs/chains integration planning
      • Planning and Coordinating dAPI/chains surveying, integration, reconfiguration, and retiring
      • Reviewing Feed providers' performance for reconfigurations and Planning Providers' airnode-feed redeployments
      • Maintaining the Integration Pipeline sheets
    • Dependencies/Prerequisites:
      • Be familiar with the integration checklists and flows
    • Points of Contact: Ugur, Mertcan, Serhan, Hayrettin, Bedirhan

  • Dapps Integration pipeline:

    • Description: This involves:
      • Creating dapps integration and asset tracking issues on GH and Linear boards
      • Send reminders and do follow-ups related to dapps integration
      • Liaise between the technical and BD teams regarding integration needs and blockers.

  • Dependencies/Prerequisites:

    • Be familiar with the integration checklists and flows
    • Points of Contact: Dave, Ugur, Gio

  • API Providers Integration Strategy:

    • Description: This involves:
      • Liaise between technical (Mertcan & Serhan) and Sales (Gio) regarding new Provider strategy, testing, integration, and management.
      • Ensuring any changes in strategy or requirements are communicated clearly to Mertcan, Gio, and Ugur.
      • Review Providers' performance and Marketing announcement articles
    • Dependencies/Prerequisites:
      • Be familiar with the provider's integration requirements
    • Points of Contact: Ugur, Mertcan, Gio

  • Board management:

    • Description: This involves creating and managing the issues on the Api3 Project GH & Linear boards and run the associated calls
      • Data Feed Operations
      • Nodary
      • API Integrations
      • Market Integration
      • Technical Management
      • dapp-management
      • BD (Linear)
    • Dependencies/Prerequisites: Have access to the boards and attend the weekly calls
    • Points of Contact: Bedirhan, Emanuel

  • Monthly OEV payout:

    • Description:
      • Payouts Dry Run
      • Bridge OEV payouts and transfer to vault
      • Update accounting.json and generate reports
    • Dependencies/Prerequisites: Have access to the dapp-management and manage-multisig repos
    • Points of Contact: Emanuel

  • Bi-annual Performance Review Process Coordination:

    • Description:
      • Self-reflections' collections and access management
      • Final reviews setup and coordination
      • 1on1s tracking
      • Engagement Survey execution, results analysis, and recommended actions follow-up
    • Dependencies/Prerequisites: Have Editor access to the performance review drive's directory
    • Points of Contact: Emanuel

  • Other

    • Description:
    • Dependencies/Prerequisites:
    • Points of Contact: Emanuel, Warern

Serhan​

Operational Responsibilities:​

Updated on: 2026-04-06

  • API Integrations:

    • Description:
      • Technical contact with API providers for integration and troubleshooting.
      • Integration and evaluation of new APIs and data feeds.
      • Developing and maintaining the api-integrations main repository.
      • Maintaining CI pipelines, frontend and api-monitor service.
      • Developing and maintaining combined-deployment CloudFormation templates.
      • Deploying mock Airnode feeds for monitoring, surveying, and testing purposes.
      • Maintaining E2E (end-to-end) tests.
      • Surveying and analyzing API/data providers.
      • Scheduling operational actions required for providers.
      • Preparing OIS files and assisting providers during Signed API & Airnode integration.
      • Being the technical point of contact for provider-related issues.
      • Contacting partners when issues occur (e.g., incorrect values, downtime).
      • Making decisions in collaboration with partner API providers.
    • Dependencies/Prerequisites: Airnode feed, Signed API, API access credentials.
    • Points of Contact: Gio, Emanuel, Bedirhan, Hayrettin, Burak, Prenaam

  • API Integration Tools:

    • API Integrations Monitoring:_
      • Developing and maintaining api-integration-tools monitoring repository.
      • Analyzing off-chain data feeds, airnodes, and deviation reports and graphics; initiating corrective actions.

  • Centurion:

    • Description:
      • Developing and maintaining centurion-monorepo repository.
      • Points of Contact: Bedirhan

  • Morpho Position Tracker:

    • Description:
      • Developing and maintaining morpho-position-tracker repository.
      • Points of Contact: Bedirhan, Emanuel, Hayrettin

  • Monitoring

    • On-call Monitoring Duty:
      • Description:
        • Mainly responsible for off-chain alerts alongside Mertcan, while also monitoring all alerts whether on-chain, off-chain, or related to the Morpho side in accordance with the operational flow. I actively communicate with other on-calls and work on improving existing monitoring systems, such as Centurion and Morpho Position Tracker, to enhance their performance. Additionally, I am able to update on-chain data feeds using the keycard provided by Bedirhan.

  • Opsgenie policy management:

    • Description: Manage Opsgenie routing rules, global policies, and escalation policies for Centurion and Morpho Position Tracker according to the team needs.

  • Operations:

    • Description:
      • Takes part in Dint, Dre, Dret, Dsur, Fint, Pre checklists.
    • Dependencies/Prerequisites: –
    • Points of Contact: Hayrettin, Burak, Prenaam, Bedirhan, Mertcan

Warren​

Operational Responsibilities:​

Updated on: 2026-03-27

  • Social Media:

    • Description: Maintain bots for Telegram and Discord. Maintain "the daily" Slack channel app. Proof read X Articles. Keep social media docs up-to-date. Monitor social media. See Social Media docs for development, build, and deployment instructions.
    • Dependencies/Prerequisites: Vitepress, Vue 3, Nodejs, Telegram, Discord SDK, and Github hosting.
    • Points of Contact: @Burak

  • Technical documentation:

    • Description: Maintain VitePress framework and Vue components, assist developers with content updates.
    • Dependencies/Prerequisites: Vitepress, Vue 3, FlexSearch, and Firebase hosting.
    • Points of Contact: @Burak

Member Name​

Operational Responsibilities:​

Updated on: YYYY-MM-DD

  • [Name Of Operational Responsability 1]:

    • Description: This involves...
    • Dependencies/Prerequisites: ...
    • Points of Contact: ...

  • [Name Of Operational Responsability 2]:

    • Description: This involves...
    • Dependencies/Prerequisites: ...
    • Points of Contact: ...

... (Add operational responsibilities as needed)

(Continue for each team member)

Conclusion​

By documenting the operational responsibilities of each team member, we aim to enhance our operational efficiency, minimize potential bottlenecks, and ensure continuity in our processes.

For any updates or changes to this document, please submit a pull request or contact the document maintainer.

Owner: Prenaam
Last updated on by Warren Anderson