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.
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 : Run an archive node | Ferrum Network Ecosystem
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/
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 : Run an archive node | Ferrum Network Ecosystem
Integration with Subgraph Studio or alternatives
As referenced in the Chain Integration Process GIP, 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.)