# Network Details
### Mainnet
* Network name: SVC
* ChanId: **32344**
* Gas price: **0 gwei**
* RPC
* official RPC:
* Explorer:
Please refer to [quickstart](https://github.com/fkt20/FAKTNetwork/#using-quickstart) if you wish to run your own node.
## 1. Seven Chain Mainnet
### General Information
| Block size | Block speed | Gas price | Patchset | Native token | Network ID |
| ---------- | ----------- | --------- | -------- | ------------ | ---------- |
| 20,000,000 | 9 seconds | 0 GWei | | SVC | 32344 |
Please refer to [quickstart](https://github.com/fkt20/FAKTNetwork/#using-quickstart) if you wish to run your own node.
* Network name: Seven Chain
* ChanId: 36
* Gas price: **0 gwei**
* RPC
* official RPC: [ http://146.190.96.86:8545/](< http://146.190.96.86:8545/>)
* pocket network RPC: /
* Archive node RPC:
* Explorer:
Please refer to [quickstart](https://github.com/fkt20/FAKTNetwork/#using-quickstart) if you wish to run your own node.
### Blockchain explorer
Seven Chain **Explorer** is the official blockchain explorer for Seven Chain. With this full-featured, open-source explorer you can view transactions, accounts & balances, access data via the API, and read and verify smart contracts.
https://explorer-svc.ceewen.xyz/
## 2. Seven Chain Testnet Spark
## 3. Token Faucets
SVC **faucet**
## 4. Network Upgrades
Major updates on the network level are introduced via forks.
{% hint style="danger" %}
Forks are used to introduce new functionality or fix security related issues. Node runners will receive instructions on how and when to update their nodes in the event of a fork.
{% endhint %}
Information related to forks along with upgrade information will be posted here. If any assistance is needed, feel free to reach out or ask questions through the forum or other channels.
### Upgrade Guide
For Nodes, Bootnodes and Validator
{% hint style="info" %}
This guide assumes that you have created your node via our [quickstart script](https://github.com/fuseio/fuse-network/blob/master/scripts/quickstart.sh). If you have built you own client using our spec then ensure that your client matches the official supported [client ](https://github.com/fuseio/fuse-network/blob/master/Dockerfile#L23)and you use the most up to date [chain spec](https://github.com/fuseio/fuse-network/blob/master/config/spec.json).
{% endhint %}
### Prerequisites
The update will pull the latest database from our latest snapshot so please ensure that you have at least 20GB disk space free before starting.
### Step 1 - CD to the location of quickstart.sh and update quickstart
```
cd
wget -O quickstart.sh https://raw.githubusercontent.com/MedifaktDev/Medifakt/master/scripts/quickstart.sh
```
### Step 2 - Run quickstart and agree to upgrade
```
sudo ./quickstart.sh
Agree [Y] when prompted to upgrade
Wait for script to complete
```
### Step 3 - Verify Upgrade
Check your node on our [health site ](https://status.medifakt.network)It should be online and the client should be "OpenEthereum//v3.2.6-stable", ensure your node is connected to peers and syncing/ in sync.
###
Check your node on our [health site ](https://status.medifakt.network/)It should be online and the client should be "OpenEthereum//v3.2.6-stable", ensure your node is connected to peers and syncing/ in sync.
## Upgrade Guide (explorer nodes)
This guide is intended specifically for explorer nodes.Since we don't host snapshots for explorer DBs, some extra steps are required in order to update from V1.0.0 to V2.0.0.
#### Step 1 - Stop all running containers
sudo docker stop $(sudo docker ps -q)
#### Step 2 - Pull the latest quickstart script
cd \wget -O quickstart.sh
#### Step 3 - Upgrade your DB using OEs upgrade tool
It is highly recommended to take a back up of your database folder before attempting!.Follow the instruction here to upgrade from V13->V16 DBs . The data base is stored in \/fusenet/database/FuseNetwork/db/dee77c98f8210dbb/archive
#### Step 4 - Update Client version in env file and rerun quickstart
vim .envAdd the following (without quotes) "CLIENT=OE"Save and exit :w :qsudo ./quickstart.sh
#### Step 5 - Verify Upgrade
Check your node on our [health site ](https://status.medifakt.network/)It should be online and the client should be "OpenEthereum//v3.2.6-stable", ensure your node is connected to peers and syncing/ in sync.
## Block 13,800,000 Fork
This fork Requires OE 3.2.6 or newer.
[EIP 152](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-152.md)
[EIP 1108](https://eips.ethereum.org/EIPS/eip-1108)
[EIP 1283](https://eips.ethereum.org/EIPS/eip-1283)
[EIP 1344](https://eips.ethereum.org/EIPS/eip-1344)
[EIP 1706](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1706.md)
[EIP 1884](https://eips.ethereum.org/EIPS/eip-1884)
[EIP 2028](https://eips.ethereum.org/EIPS/eip-2028)
[EIP 2565](https://eips.ethereum.org/EIPS/eip-2565)
[EIP 2929](https://eips.ethereum.org/EIPS/eip-2929)
[EIP 2930](https://eips.ethereum.org/EIPS/eip-2930)
## FIP's
The Seven chain Improvement Proposal
See FIP1 for more info
### What is a FIP?
FIP stands for Seven chain Improvement Proposal. A FIP is a design document providing information to the Seven chain community, or describing a new feature for Seven chain. The FIP should provide motivation and technical specification for the feature.
| FIP | Description | Status |
| ----------------------------------------------------------------- | -------------------------------------------------------------- | ------------------------------------------------------ |
| [FIP-1](https://github.com/fuseio/FIPs/blob/master/FIPS/fip-1.md) | Introduction and explanation about FIP's | Done |
| [FIP-2](https://github.com/fuseio/FIPs/blob/master/FIPS/fip-2.md) | Enabling delegation of fuse tokens to validators | Done |
| [FIP-3](https://github.com/fuseio/FIPs/blob/master/FIPS/fip-3.md) | Lowering the stake to run a validator node to 100K Seven Chain | Done |
| [FIP-4](https://github.com/fuseio/FIPs/blob/master/FIPS/fip-4.md) | Multi validators, validators can run multiple nodes | Undone |
| [FIP-5](https://github.com/fuseio/FIPs/blob/master/FIPS/fip-5.md) | Validators key splitting, validator will have separated keys | Undone |
| [FIP-6](https://github.com/fuseio/FIPs/blob/master/FIPS/fip-6.md) | Bridge implementation should be changeable by voting | Undone |
| [FIP-7](https://github.com/fuseio/FIPs/blob/master/FIPS/fip-7.md) | Tiny Ethereum Network transactions on end of cycle | Undone |
| [FIP-8](https://github.com/fuseio/FIPs/blob/master/FIPS/fip-8.md) | Adjusting Block Rewards by the Validator's Stake | [Done](https://github.com/fuseio/fuse-network/pull/61) |
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs-svc.ceewen.xyz/network-details.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.