# Ferrum Network Chain Integration

**URL:** <https://forum.thegraph.com/t/ferrum-network-chain-integration/6051>\
**Category:** New Chain Integrations\
**Tags:** subgraph-devs\
**Created:** [September 24, 2024, 9:07am UTC](https://forum.thegraph.com/t/ferrum-network-chain-integration/6051 "2024-09-24T09:07:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MHaris-Ferrum](https://avatars.discourse-cdn.com/v4/letter/m/5daacb/32.png) [@MHaris-Ferrum](https://forum.thegraph.com/u/MHaris-Ferrum)\
**Post date:** [September 24, 2024, 9:07am UTC](https://forum.thegraph.com/t/ferrum-network-chain-integration/6051/1 "2024-09-24T09:07:26Z")

</div>

**If you’re creating a topic here, it means you’re seeking protocol integration for a new data source, according to the [Chain Integration Process GIP](https://thegraph.com/docs/en/chain-integration-overview/).**

> Use of this template is mandatory to start the integration process.  
> Please fill out placeholders, removing any notes such as this one.

* * *

## About `Blockchain`

> Ferrum Network

> General information about the blockchain:
> 
> - Yes, Mainnet is available. We are in alpha version.
> - QPN parachain is built using Substrate and Frontier, it is a parachain connected to the Kusama network and allows native evm and substrate transactions on-chain.  
> FRM is the native token of the chain and has 18 decimal places  
> Our blockchain is evm compatible and use evm addresses as the default address format onchain  
> The links to the repo and build commands can be found here : [https://docs.ferrumnetwork.io/ferrum-network-ecosystem/v/ferrum-network-node-docs/docs/node-operators/running-archive-node](https://docs.ferrumnetwork.io/ferrum-network-ecosystem/v/ferrum-network-node-docs/docs/node-operators/running-archive-node)  
> The key functionality of QPN is to enable seamless cross chain transactions on any evm chain, our devnet is connected with 6 other evm chains currently, you can see the cross chain transactions happening here : [https://qp-explorer-dev.netlify.app/](https://qp-explorer-dev.netlify.app/)

## Contact Information

> Tell us more about you.
> 
> - I am the part of the blockchain’s core development team.
> - Contact: muhammad.haris@ferrum.network

## Graph Node integration

> Add here all the details related to:
> 
> - Our blockchain is evm compatible and use evm addresses as the default address format onchain
> - The links to the repo and build commands can be found here : [https://docs.ferrumnetwork.io/ferrum-network-ecosystem/v/ferrum-network-node-docs/docs/node-operators/running-archive-node](https://docs.ferrumnetwork.io/ferrum-network-ecosystem/v/ferrum-network-node-docs/docs/node-operators/running-archive-node)

## Integration with Subgraph Studio or alternatives

> As referenced in the [Chain Integration Process GIP](https://forum.thegraph.com/t/gip-0057-chain-integration-process/4468), this is a requirement for _Stage 2_.  
> Please detail how you intend to support this integration: seeking help maintaining the RPC and/or Firehose stack, or would an endpoint be provided to the team operating Subgraph Studio? _You don’t need to share the RPC url on this post - that can be privately shared at a later stage_

## Indexer Documentation

> Provide detailed information for Graph Indexers to support the new chain, which means running the RPC and/or Firehose stack. Examples:
> 
> - Hardware requirements
> - Complete Docker and/or bare metal guides to run a node
> - Available snapshots required to run nodes
> - Average frequency of upgrades or hard-forks
> - Available monitoring solutions (Prometheus, Grafana dashboards, etc.)

---

<div class="post-metadata">

**Author:** ![kate.paka](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.thegraph.com/kate.paka/32/2497_2.png) [@kate.paka](https://forum.thegraph.com/u/kate.paka)\
**Post date:** [September 27, 2024, 2:05pm UTC](https://forum.thegraph.com/t/ferrum-network-chain-integration/6051/2 "2024-09-27T14:05:19Z")

</div>

Hello @MHaris-Ferrum ! Thank you for reaching out and for the info that you shared here. We will look at the documentation you’ve provided and follow up accordingly.