const fs = require('fs')

// Function to read a JSON file
const readJsonFile = (filePath) => {
	return JSON.parse(fs.readFileSync(filePath, 'utf-8'))
}

// Function to write to a JSON file
const writeJsonFile = (filePath, data) => {
	fs.writeFileSync(filePath, JSON.stringify(data, null, 2), 'utf-8')
}

// Main function to merge navigation into mint
const mergeNavigationIntoMint = () => {
	const navigationPath = '../sdk/content/navigation.json'
	const mintPath = '../mint.json'

	// Read both JSON files
	const navigation = readJsonFile(navigationPath)
	const mint = readJsonFile(mintPath)

	// Find the Reference group in mint.json
	const referenceGroup = mint.navigation.find((group) => group.group === 'Reference')

	if (referenceGroup) {
		// Replace the pages value with the content from navigation.json
		referenceGroup.pages = navigation
	} else {
		console.error('Reference group not found in mint.json')
		return
	}

	// Write the updated mint.json back to the file
	writeJsonFile(mintPath, mint)

	console.log('Successfully merged navigation into mint.json')
}

// Execute the main function
mergeNavigationIntoMint()


Extended by

Implements

Properties

getBlock()

Parameters

Returns

Source

getTransaction()

getTransactionReceipt()

toJSON()

Methods

Quai Network Docs

Learn

Build

Client

Guides

Quai Network

Discord

A high level overview of Quai Network's fundamental building blocks.

Introduction to Quai

Quai Network's Proof-of-Entropy-Minima consensus mechanism.

Introduction to PoEM

How merged mining has been adapted and used to scale in Quai Network.

Overview

How merge-mined blocks are used to transfer state across blockchains in Quai Network.

Coincident Blocks

How Quai Network efficiently uses energy compared to other consensus mechanisms.

Energy Efficiency

How Quai Network can support custom blockchains.

Merge-Mined Parachains

How Quai Network processes transactions in parallel.

Multithreaded Execution

Specifications of Quai Network's interoperability between shards.

How cross-chain transactions are processed in Quai Network.

External Transactions (ETXs)

Detailed specification of Quai Network's hierarchical structure.

Hierarchical Structure

How sharding is implemented and used to scale in Quai Network.

Sharding

How Quai Network optimizes geographical latency in order to scale.

Latency

A high level overview of Quai Network's two-token system.

Token Overview

Quai

An explanation of the emissions, conversions, and supplies of the Quai and Qi tokens.

Token Dynamics

An explanation of the conversion mechanism between the Quai and Qi tokens.

Conversions

An explanation of mining and block rewards in Quai Network.

Block Rewards

An explanation of difficulty within Quai Network and how it relates to the Quai and Qi tokens.

Difficulty Adjustments

Imaginative examples of supply growth of the Quai and Qi tokens.

Example Supply Growth

An overview of the genesis allocations of the Quai and Qi tokens.

Genesis Allocations

Research papers and whitepapers that detail fundamental aspects of the Quai protocol.

Whitepapers

A collection of lectures and presentations on the technology powering Quai Network.

Lectures & Presentations

Introduction

Development Introduction

Specifications for Quai development and testing environments.

Networks

Tools and resources for developing on Quai Network.

Quick Links

Smart contract development languages supported on Quai Network.

Which Language To Use

The Solidity smart contract programming language.

Solidity

The SolidityX smart contract programming language.

SolidityX

Specification of the isaddrinternal and etx opcodes additions on Quai Network.

Opcode Additions

How to deploy a smart contract to the Quai Network.

Deploy

An overview of transactions within Quai Network.

Types

An overview of the JavaScript APIs available for interacting with Quai Network.

JavaScript Libraries

How to set up Postman for use with the Quai Network API.

Setting Up Postman

How to configure and use environment variables in Postman for the Quai Network API.

Variables

How to make API requests to Quai Network using Postman.

Making Requests

Technical specification of Quai Network JSON-RPC API methods and usage.

JSON-RPC Overview

Returns the balance of the specified address.

getBalance

Returns the code stored at a given address.

getCode

Returns the value from a storage position at a given address.

getStorageAt

Returns the Merkle-Proof for a given account and optional storage keys.

getProof

Returns the total transaction count for a given address.

getTransactionCount

blockNumber

Returns the hash of the block header for a specific block number.

getHeaderhashByNumber

Returns the header for a given block hash.

getHeaderByHash

Returns the header for a given block number.

getHeaderByNumber

Returns block data for a given block number.

getBlockByNumber

Returns block data for a given block hash.

getBlockByHash

Returns block or candidate block data for a given hash.

getBlockOrCandidateByHash

Returns the uncle block for a given block number and index.

uncleByNumberAndIndex

Returns the uncle block for a given block hash and index.

uncleByHashAndIndex

Returns the uncle count for a given block number.

uncleCountByNumber

Returns the uncle count for a given block hash.

uncleCountByHash

Returns the transaction count for a block given its hash.

blockTxCountByHash

Returns the transaction count for a block given its number.

blockTxCountByNumber

Returns transaction data given a block number and the transaction index.

txByBlockAndIndex

Returns transaction data given block hash and the transaction index.

txByBlockHashAndIndex

Returns bytecode for a raw transaction given block number and transaction index.

rawTxByNumberAndIndex

Returns the bytecode for a raw transaction given block hash andtransaction index.

rawTxByHashAndIndex

Returns the bytecode for a raw transaction given its hash.

rawTxByHash

Returns a transaction and its data for a given transaction hash.

getTransactionByHash

Returns the receipt of a transaction by transaction hash.

getTransactionReceipt

Creates new message call, transaction, or contract creation for signed transactions.

sendRawTransaction

Creates an access list for the provided transaction.

createAccessList

Executes a new message call without creating a transaction on chain.

call

gasPrice

Returns the current maxPriorityFeePerGas.

maxPriorityFeePerGas

Returns the feeHistory for a given a block range.

feeHistory

Estimates the gas required to execute the given transaction

estimateGas

Returns the current content of the transaction pool.

content

Returns transactions in the txpool from the given address.

contentFrom

Returns a summarized form of the transaction pool content.

inspect

Returns the current size of the transaction pool.

status

Returns the RLP encoded block given its number.

getBlockRlp

Returns raw data for a block given its number.

printBlock

traceTransaction

Returns an indicator of whether client is listening for network connections.

listening

Returns the number of peers currently connected to the client.

peerCount

version

chainId

Returns the current node location or context

nodeLocation

Returns an array representation of the currently running chains sorted by shard index.

listRunningChains

Returns the number of dynamic chain expansions that have occurred since the genesis block.

Property	Modifier	Type	Description
`address`	`readonly`	`string`	The address of the contract that emitted this log.
`blockHash`	`readonly`	`string`	The block hash of the block this log occurred in. Use the Log.getBlock to get the Block.
`blockNumber`	`readonly`	`number`	The block number of the block this log occurred in. It is preferred to use the Block.hash \| Block.hash when fetching the related Block, since in the case of an orphaned block, the block at that height may have changed.
`data`	`readonly`	`string`	The data included in this log when it was emitted.
`index`	`readonly`	`number`	The index within the block this log occurred at. This is generally not useful to developers, but can be used with the various roots to proof inclusion within a block.
`provider`	`readonly`	`Provider`	The provider connected to the log used to fetch additional details if necessary.
`removed`	`readonly`	`boolean`	If the Log represents a block that was removed due to an orphaned block, this will be true. This can only happen within an orphan event listener.
`topics`	`readonly`	readonly `string`[]	The indexed topics included in this log when it was emitted. All topics are included in the bloom filters, so they can be efficiently filtered using the Provider.getLogs method.
`transactionHash`	`readonly`	`string`	The transaction hash of the transaction this log occurred in. Use the Log.getTransaction to get the **TransactionResponse.
`transactionIndex`	`readonly`	`number`	The index within the transaction of this log.

Getting Started

Fundamentals

Reference

Log

Extended by

Implements

Properties

Methods

getBlock()

Parameters

Returns

Source

getTransaction()

Returns

Source

getTransactionReceipt()

Returns

Source

toJSON()

Returns

Source

Getting Started

Fundamentals

Reference

​Extended by

​Implements

​Properties

​Methods

​getBlock()

​Parameters

​Returns

​Source

​getTransaction()

​Returns

​Source

​getTransactionReceipt()

​Returns

​Source

​toJSON()

​Returns

​Source

Extended by

Implements

Properties

Methods

getBlock()

Parameters

Returns

Source

getTransaction()

Returns

Source

getTransactionReceipt()

Returns

Source

toJSON()

Returns

Source