From 6bacd3e580b0742437bebf499ba621ed056f60e4 Mon Sep 17 00:00:00 2001 From: navillanueva Date: Tue, 25 Nov 2025 15:56:59 -0500 Subject: [PATCH 1/2] updated links --- .../02-intro-to-evm/05-different-evm-versions.mdx | 2 +- .../XX-registering-validator/registering-validator.mdx | 4 ++-- .../04-register-validators.mdx | 4 ++-- content/blog/granite-upgrade.mdx | 2 +- .../docs/dapps/advanced-tutorials/exchange-integration.mdx | 4 ++-- content/docs/dapps/index.mdx | 2 +- .../docs/dapps/smart-contract-dev/interact-golang-app.mdx | 6 +++--- content/docs/quick-start/primary-network.mdx | 2 +- content/docs/quick-start/virtual-machines.mdx | 2 +- content/docs/rpcs/c-chain/api.mdx | 2 +- content/docs/rpcs/c-chain/index.mdx | 2 +- .../create-deploy-avalanche-l1s/deploy-on-fuji-testnet.mdx | 2 +- content/docs/virtual-machines/custom-precompiles/index.mdx | 2 +- utils/remote-content/apis.mts | 4 ++-- utils/remote-content/cross-chain.mts | 4 ++-- utils/remote-content/primary-network.mts | 4 ++-- 16 files changed, 24 insertions(+), 24 deletions(-) diff --git a/content/academy/avalanche-l1/customizing-evm/02-intro-to-evm/05-different-evm-versions.mdx b/content/academy/avalanche-l1/customizing-evm/02-intro-to-evm/05-different-evm-versions.mdx index f8f9401fc72..b9f4ae31682 100644 --- a/content/academy/avalanche-l1/customizing-evm/02-intro-to-evm/05-different-evm-versions.mdx +++ b/content/academy/avalanche-l1/customizing-evm/02-intro-to-evm/05-different-evm-versions.mdx @@ -12,7 +12,7 @@ Geth (or [go-ethereum](https://github.com/ethereum/go-ethereum)) is the official ## Coreth -[Coreth](https://github.com/ava-labs/coreth) is a fork of Geth maintained by Ava Labs. It implements the EVM for the C-Chain and has been adapted to work with Avalanche Consensus. +[Coreth](https://github.com/ava-labs/avalanchego/tree/master/graft/coreth) is a fork of Geth maintained by Ava Labs. It implements the EVM for the C-Chain and has been adapted to work with Avalanche Consensus. ## Subnet-EVM diff --git a/content/academy/avalanche-l1/permissioned-l1s/XX-registering-validator/registering-validator.mdx b/content/academy/avalanche-l1/permissioned-l1s/XX-registering-validator/registering-validator.mdx index 0fe172cc41d..15b3d217852 100644 --- a/content/academy/avalanche-l1/permissioned-l1s/XX-registering-validator/registering-validator.mdx +++ b/content/academy/avalanche-l1/permissioned-l1s/XX-registering-validator/registering-validator.mdx @@ -19,7 +19,7 @@ cast keccak "SendWarpMessage(address,bytes32,bytes)" To find a specific warp messageID, one must know the block number or block hash to retrieve the logs, or be monitoring all events, looking for and indexing messages. -When a block is [accepted](https://github.com/ava-labs/coreth/blob/7242ae2d235593d2bb14e2496b6ed102aab14c3d/precompile/contracts/warp/config.go#L130) by the network, a precompile hook is called, and the EVM saves the warp message to a local database. The validator node will then be willing to sign any messages in that database upon request, typically via an `AppRequest` message over the p2p network. +When a block is [accepted](https://github.com/ava-labs/avalanchego/blob/master/graft/coreth/precompile/contracts/warp/config.go#L133) by the network, a precompile hook is called, and the EVM saves the warp message to a local database. The validator node will then be willing to sign any messages in that database upon request, typically via an `AppRequest` message over the p2p network. ### Receiving Warp Messages @@ -27,7 +27,7 @@ On the EVM, any smart contract can call the precompile which returns the warp message and verifies the attached signature. But what is `index`? Where does it get the warp message from? The answer is, you! When you send a tx to any contract that eventually calls `getVerifiedWarpMessage`, you **must** pass in the signed warp message as a “predicate”. It’s called an AccessList, and typically this is an optional field that can be used by the EVM to pre-fetch storage slots that will be accessed, for efficiency and reducing gas costs. But Warp cleverly (ab)uses this feature of the EVM to verify the signature of the warp message, and then make the warp message available during the transactions lifetime, by calling `getVerifiedWarpMessage`. You can pass multiple warp messages which is where the `index` comes in. (All of this is abstracted away by Teleporter for EVM to EVM comms) -Details: [Warp README](https://github.com/ava-labs/coreth/blob/7242ae2d235593d2bb14e2496b6ed102aab14c3d/precompile/contracts/warp/README.md) +Details: [Warp README](https://github.com/ava-labs/avalanchego/blob/master/graft/coreth/precompile/contracts/warp/README.md) ### Teleporter diff --git a/content/academy/avalanche-l1/permissionless-l1s/06-staking-manager-operations/04-register-validators.mdx b/content/academy/avalanche-l1/permissionless-l1s/06-staking-manager-operations/04-register-validators.mdx index 82cff93ac9f..111d76927b1 100644 --- a/content/academy/avalanche-l1/permissionless-l1s/06-staking-manager-operations/04-register-validators.mdx +++ b/content/academy/avalanche-l1/permissionless-l1s/06-staking-manager-operations/04-register-validators.mdx @@ -50,7 +50,7 @@ cast keccak "SendWarpMessage(address,bytes32,bytes)" To find a specific warp messageID, one must know the block number or block hash to retrieve the logs, or be monitoring all events, looking for and indexing messages. -When a block is [accepted](https://github.com/ava-labs/coreth/blob/7242ae2d235593d2bb14e2496b6ed102aab14c3d/precompile/contracts/warp/config.go#L130) by the network, a precompile hook is called, and the EVM saves the warp message to a local database. The validator node will then be willing to sign any messages in that database upon request, typically via an `AppRequest` message over the p2p network. +When a block is [accepted](https://github.com/ava-labs/avalanchego/blob/master/graft/coreth/precompile/contracts/warp/config.go#L133) by the network, a precompile hook is called, and the EVM saves the warp message to a local database. The validator node will then be willing to sign any messages in that database upon request, typically via an `AppRequest` message over the p2p network. ### Receiving Warp Messages @@ -58,7 +58,7 @@ On the EVM, any smart contract can call the precompile which returns the warp message and verifies the attached signature. But what is `index`? Where does it get the warp message from? The answer is, you! When you send a tx to any contract that eventually calls `getVerifiedWarpMessage`, you **must** pass in the signed warp message as a “predicate”. It’s called an AccessList, and typically this is an optional field that can be used by the EVM to pre-fetch storage slots that will be accessed, for efficiency and reducing gas costs. But Warp cleverly (ab)uses this feature of the EVM to verify the signature of the warp message, and then make the warp message available during the transactions lifetime, by calling `getVerifiedWarpMessage`. You can pass multiple warp messages which is where the `index` comes in. (All of this is abstracted away by ICM for EVM to EVM comms) -Details: [Warp README](https://github.com/ava-labs/coreth/blob/7242ae2d235593d2bb14e2496b6ed102aab14c3d/precompile/contracts/warp/README.md) +Details: [Warp README](https://github.com/ava-labs/avalanchego/blob/master/graft/coreth/precompile/contracts/warp/README.md) ### Interchain Messaging Contracts (ICM) diff --git a/content/blog/granite-upgrade.mdx b/content/blog/granite-upgrade.mdx index e425a0fb4eb..67ed062ad59 100644 --- a/content/blog/granite-upgrade.mdx +++ b/content/blog/granite-upgrade.mdx @@ -140,7 +140,7 @@ Two new headers have been introduced as part of ACP-226 for dynamic block time m 1. **`timestampMilliseconds`** (uint64) - Timestamp in milliseconds for more precise block timing 2. **`minDelayExcess`** (uint64) - Tracks the excess delay for dynamic block time adjustments -See the [full changelog](https://github.com/ava-labs/coreth/blob/master/RELEASES.md#pending-release) for implementation details. +See the [full changelog](https://github.com/ava-labs/avalanchego/blob/master/graft/coreth/RELEASES.md#pending-release) for implementation details. #### For L1s diff --git a/content/docs/dapps/advanced-tutorials/exchange-integration.mdx b/content/docs/dapps/advanced-tutorials/exchange-integration.mdx index 41757183be2..fde92d0e5b2 100644 --- a/content/docs/dapps/advanced-tutorials/exchange-integration.mdx +++ b/content/docs/dapps/advanced-tutorials/exchange-integration.mdx @@ -146,10 +146,10 @@ thrown indicating that unfinalized data cannot be queried (as of If you plan on extracting data from the C-Chain into your own systems using Golang, we recommend using our custom -[`ethclient`](https://github.com/ava-labs/coreth/tree/master/ethclient). The +[`ethclient`](https://github.com/ava-labs/avalanchego/tree/master/graft/coreth/ethclient). The standard `go-ethereum` Ethereum client does not compute block hashes correctly (when you call `block.Hash()`) because it doesn't take into account the added -[ExtDataHash](https://github.com/ava-labs/coreth/blob/2c3cfac5f766ce5f32a2eddc43451bdb473b84f1/core/types/block.go#L98) +[ExtDataHash](https://github.com/ava-labs/avalanchego/blob/master/graft/coreth/core/types/block.go#L98) header field in Avalanche C-Chain blocks, which is used move AVAX between chains (X-Chain and P-Chain). You can read more about our multi-chain abstraction [here](/docs/quick-start/primary-network) (out of scope for a diff --git a/content/docs/dapps/index.mdx b/content/docs/dapps/index.mdx index c2ecf278c40..e757dba7190 100644 --- a/content/docs/dapps/index.mdx +++ b/content/docs/dapps/index.mdx @@ -5,7 +5,7 @@ description: Learn about the Avalanche C-Chain. Avalanche is a [network of networks](/docs/quick-start/primary-network). One of the chains running on Avalanche Primary Network is an EVM fork called the C-Chain (contract chain). -C-Chain runs a fork of [`go-ethereum`](https://geth.ethereum.org/docs/rpc/server) called [`coreth`](https://github.com/ava-labs/coreth) that has the networking and consensus portions replaced with Avalanche equivalents. What's left is the Ethereum VM, which runs Solidity smart contracts and manages data structures and blocks on the chain. +C-Chain runs a fork of [`go-ethereum`](https://geth.ethereum.org/docs/rpc/server) called [`coreth`](https://github.com/ava-labs/avalanchego/tree/master/graft/coreth) that has the networking and consensus portions replaced with Avalanche equivalents. What's left is the Ethereum VM, which runs Solidity smart contracts and manages data structures and blocks on the chain. As a result, you get a blockchain that can run all the Solidity smart contracts from Ethereum, but with much greater transaction bandwidth and instant finality that [Avalanche's revolutionary consensus](/docs/quick-start/avalanche-consensus) enables. diff --git a/content/docs/dapps/smart-contract-dev/interact-golang-app.mdx b/content/docs/dapps/smart-contract-dev/interact-golang-app.mdx index d5ea9e195d0..74b0b4813db 100644 --- a/content/docs/dapps/smart-contract-dev/interact-golang-app.mdx +++ b/content/docs/dapps/smart-contract-dev/interact-golang-app.mdx @@ -21,11 +21,11 @@ Ensure solc is properly installed by checking its version. solc --version ``` -Clone Coreth and Build Abigen. +Clone AvalancheGo and Build Abigen. ```bash -git clone [email protected]:ava-labs/coreth.git -cd coreth/ +git clone [email protected]:ava-labs/avalanchego.git +cd avalanchego/graft/coreth go build -o abigen cmd/abigen/*.go cp abigen ~/bin ``` diff --git a/content/docs/quick-start/primary-network.mdx b/content/docs/quick-start/primary-network.mdx index af1c813950a..8adae237dcb 100644 --- a/content/docs/quick-start/primary-network.mdx +++ b/content/docs/quick-start/primary-network.mdx @@ -27,7 +27,7 @@ All validators of the Primary Network are required to validate and secure the fo The **C-Chain** is an implementation of the Ethereum Virtual Machine (EVM). The [C-Chain's API](/docs/api-reference/c-chain/api) supports Geth's API and supports the deployment and execution of smart contracts written in Solidity. -The C-Chain is an instance of the [Coreth](https://github.com/ava-labs/coreth) Virtual Machine. +The C-Chain is an instance of the [Coreth](https://github.com/ava-labs/avalanchego/tree/master/graft/coreth) Virtual Machine. ### P-Chain diff --git a/content/docs/quick-start/virtual-machines.mdx b/content/docs/quick-start/virtual-machines.mdx index 5c3d05a1084..b82853b835a 100644 --- a/content/docs/quick-start/virtual-machines.mdx +++ b/content/docs/quick-start/virtual-machines.mdx @@ -51,7 +51,7 @@ The choice depends on your needs. Subnet-EVM provides a quick start with Ethereu description="A decentralized timestamp blockchain written in Golang (recommended for beginners)" /> diff --git a/content/docs/rpcs/c-chain/api.mdx b/content/docs/rpcs/c-chain/api.mdx index 12c0fdd724c..772255f08ad 100644 --- a/content/docs/rpcs/c-chain/api.mdx +++ b/content/docs/rpcs/c-chain/api.mdx @@ -1,7 +1,7 @@ --- title: "C-Chain API" description: "This page is an overview of the C-Chain API associated with AvalancheGo." -edit_url: https://github.com/ava-labs/coreth/edit/master/plugin/evm/api.md +edit_url: https://github.com/ava-labs/avalanchego/edit/master/graft/coreth/plugin/evm/api.md --- diff --git a/content/docs/rpcs/c-chain/index.mdx b/content/docs/rpcs/c-chain/index.mdx index 2081bceb23a..57cd82469f1 100644 --- a/content/docs/rpcs/c-chain/index.mdx +++ b/content/docs/rpcs/c-chain/index.mdx @@ -1,7 +1,7 @@ --- title: "AvalancheGo C-Chain RPC" description: "This page is an overview of the C-Chain RPC associated with AvalancheGo." -edit_url: https://github.com/ava-labs/coreth/edit/master/plugin/evm/api.md +edit_url: https://github.com/ava-labs/avalanchego/edit/master/graft/coreth/plugin/evm/api.md --- > **Note:** Ethereum has its own notion of `networkID` and `chainID`. These have no relationship to Avalanche's view of networkID and chainID and are purely internal to the [C-Chain](https://build.avax.network/docs/quick-start/primary-network#c-chain). On Mainnet, the C-Chain uses `1` and `43114` for these values. On the Fuji Testnet, it uses `1` and `43113` for these values. `networkID` and `chainID` can also be obtained using the `net_version` and `eth_chainId` methods. diff --git a/content/docs/tooling/avalanche-cli/create-deploy-avalanche-l1s/deploy-on-fuji-testnet.mdx b/content/docs/tooling/avalanche-cli/create-deploy-avalanche-l1s/deploy-on-fuji-testnet.mdx index a72a0b1812a..30c86984c5e 100644 --- a/content/docs/tooling/avalanche-cli/create-deploy-avalanche-l1s/deploy-on-fuji-testnet.mdx +++ b/content/docs/tooling/avalanche-cli/create-deploy-avalanche-l1s/deploy-on-fuji-testnet.mdx @@ -27,7 +27,7 @@ Virtual Machine[​](#virtual-machine "Direct link to heading") Avalanche can run multiple blockchains. Each blockchain is an instance of a [Virtual Machine](/docs/quick-start/virtual-machines), much like an object in an object-oriented language is an instance of a class. That's, the VM defines the behavior of the blockchain. -[Subnet-EVM](https://github.com/ava-labs/subnet-evm) is the VM that defines the Avalanche L1 Contract Chains. Subnet-EVM is a simplified version of [Avalanche C-Chain](https://github.com/ava-labs/coreth). +[Subnet-EVM](https://github.com/ava-labs/subnet-evm) is the VM that defines the Avalanche L1 Contract Chains. Subnet-EVM is a simplified version of [Avalanche C-Chain](https://github.com/ava-labs/avalanchego/tree/master/graft/coreth). This chain implements the Ethereum Virtual Machine and supports Solidity smart contracts as well as most other Ethereum client features. diff --git a/content/docs/virtual-machines/custom-precompiles/index.mdx b/content/docs/virtual-machines/custom-precompiles/index.mdx index 4d63a40f424..ab44ec1befc 100644 --- a/content/docs/virtual-machines/custom-precompiles/index.mdx +++ b/content/docs/virtual-machines/custom-precompiles/index.mdx @@ -80,7 +80,7 @@ When a precompile is called, the EVM checks if the input address is a precompile ### Stateful Precompiled Contracts -A stateful precompile builds on a precompile in that it adds state access. Stateful precompiles are not available in the default EVM, and are specific to Avalanche EVMs such as [Coreth](https://github.com/ava-labs/coreth) and [Subnet-EVM](https://github.com/ava-labs/subnet-evm). +A stateful precompile builds on a precompile in that it adds state access. Stateful precompiles are not available in the default EVM, and are specific to Avalanche EVMs such as [Coreth](https://github.com/ava-labs/avalanchego/tree/master/graft/coreth) and [Subnet-EVM](https://github.com/ava-labs/subnet-evm). A stateful precompile follows this [interface](https://github.com/ava-labs/subnet-evm/blob/helloworld-official-tutorial-v2/precompile/contract/interfaces.go#L17-L20): diff --git a/utils/remote-content/apis.mts b/utils/remote-content/apis.mts index 649a95420c2..cea331766db 100644 --- a/utils/remote-content/apis.mts +++ b/utils/remote-content/apis.mts @@ -56,11 +56,11 @@ export function getApisConfigs(): FileConfig[] { contentUrl: "https://github.com/ava-labs/avalanchego/blob/master/vms/avm/", }, { - sourceUrl: "https://raw.githubusercontent.com/ava-labs/coreth/master/plugin/evm/api.md", + sourceUrl: "https://raw.githubusercontent.com/ava-labs/avalanchego/master/graft/coreth/plugin/evm/api.md", outputPath: "content/docs/rpcs/c-chain/index.mdx", title: "AvalancheGo C-Chain RPC", description: "This page is an overview of the C-Chain RPC associated with AvalancheGo.", - contentUrl: "https://github.com/ava-labs/coreth/blob/master/plugin/evm/", + contentUrl: "https://github.com/ava-labs/avalanchego/blob/master/graft/coreth/plugin/evm/", }, { sourceUrl: "https://raw.githubusercontent.com/ava-labs/subnet-evm/master/plugin/evm/service.md", diff --git a/utils/remote-content/cross-chain.mts b/utils/remote-content/cross-chain.mts index a309cea8e65..3fbda54b1ca 100644 --- a/utils/remote-content/cross-chain.mts +++ b/utils/remote-content/cross-chain.mts @@ -49,11 +49,11 @@ export function getCrossChainConfigs(): FileConfig[] { contentUrl: "https://github.com/ava-labs/teleporter/blob/main/contracts/teleporter/registry/", }, { - sourceUrl: "https://raw.githubusercontent.com/ava-labs/coreth/master/precompile/contracts/warp/README.md", + sourceUrl: "https://raw.githubusercontent.com/ava-labs/avalanchego/master/graft/coreth/precompile/contracts/warp/README.md", outputPath: "content/docs/cross-chain/avalanche-warp-messaging/evm-integration.mdx", title: "Integration with EVM", description: "Avalanche Warp Messaging provides a basic primitive for signing and verifying messages between Avalanche L1s.", - contentUrl: "https://github.com/ava-labs/coreth/blob/master/precompile/contracts/warp/", + contentUrl: "https://github.com/ava-labs/avalanchego/blob/master/graft/coreth/precompile/contracts/warp/", }, { sourceUrl: "https://raw.githubusercontent.com/ava-labs/icm-contracts/refs/heads/main/contracts/ictt/README.md", diff --git a/utils/remote-content/primary-network.mts b/utils/remote-content/primary-network.mts index e289908784d..4a8f141e8b6 100644 --- a/utils/remote-content/primary-network.mts +++ b/utils/remote-content/primary-network.mts @@ -13,11 +13,11 @@ export function getPrimaryNetworkConfigs(): FileConfig[] { contentUrl: "https://github.com/ava-labs/avalanchego/blob/master/vms/platformvm/config/", }, { - sourceUrl: "https://raw.githubusercontent.com/ava-labs/coreth/master/plugin/evm/config/config.md", + sourceUrl: "https://raw.githubusercontent.com/ava-labs/avalanchego/master/graft/coreth/plugin/evm/config/config.md", outputPath: "content/docs/nodes/chain-configs/c-chain.mdx", title: "C-Chain Configs", description: "This page describes the configuration options available for the C-Chain.", - contentUrl: "https://github.com/ava-labs/coreth/blob/master/plugin/evm/config/", + contentUrl: "https://github.com/ava-labs/avalanchego/blob/master/graft/coreth/plugin/evm/config/", }, { sourceUrl: "https://raw.githubusercontent.com/ava-labs/avalanchego/master/vms/avm/config.md", From 2a6882bea6867eb4e218f04e57c743da2a1915e5 Mon Sep 17 00:00:00 2001 From: navillanueva Date: Tue, 25 Nov 2025 16:29:02 -0500 Subject: [PATCH 2/2] updated links --- content/blog/cortina-x-chain-linearization.mdx | 2 ++ .../dapps/smart-contract-dev/interact-golang-app.mdx | 10 +++++----- content/docs/primary-network/index.mdx | 2 +- style-guide.md | 2 +- 4 files changed, 9 insertions(+), 7 deletions(-) diff --git a/content/blog/cortina-x-chain-linearization.mdx b/content/blog/cortina-x-chain-linearization.mdx index b768bb27e89..b000a2497a8 100644 --- a/content/blog/cortina-x-chain-linearization.mdx +++ b/content/blog/cortina-x-chain-linearization.mdx @@ -43,6 +43,8 @@ Cortina modifies how these delegation fees are distributed for all validators th ## Increased C-Chain Gas Limit +Warning: The original coreth repoistory has been deprecated and it's code has been moved into [avalanche go](https://github.com/ava-labs/avalanchego/tree/master/graft/coreth) and Apricot does no longer apply + Since Apricot Phase 1, the C-Chain block gas limit has been [set to 8M gas](https://github.com/ava-labs/coreth/blob/b1223203dbca7708142b8884f46a4deec678d80e/params/avalanche_params.go#L21). Blocks on the C-Chain are produced every ~2s, so this setting limits the max amount of gas that can be consumed every 10s to ~40M gas. The gas target for every rolling 10s window, however, is set to [15M gas](https://github.com/ava-labs/coreth/blob/b1223203dbca7708142b8884f46a4deec678d80e/params/avalanche_params.go#L32). This means that when more than 15M gas is used in a 10s window, the gas price will go up (and go down when less than 15M is used). You can read more about how dynamic fees work on the C-Chain [here](https://medium.com/avalancheavax/apricot-phase-three-c-chain-dynamic-fees-432d32d67b60). Outside of limiting the amount of gas that can be consumed in some window at any gas price, the block gas limit also limits the complexity of transactions that can be issued in a single block. As different developers on Avalanche began to deploy more complex dApps, they've expressed that 8M gas per block isn't enough for their use case. Cortina increases the C-Chain block gas limit to 15M gas. To avoid increasing the amount of resources required to validate the Primary Network, the gas target will remain unchanged at 15M gas per 10s. diff --git a/content/docs/dapps/smart-contract-dev/interact-golang-app.mdx b/content/docs/dapps/smart-contract-dev/interact-golang-app.mdx index 74b0b4813db..3f24b2c3f4a 100644 --- a/content/docs/dapps/smart-contract-dev/interact-golang-app.mdx +++ b/content/docs/dapps/smart-contract-dev/interact-golang-app.mdx @@ -56,11 +56,11 @@ import ( "github.com/ava-labs/avalanchego/utils/constants" "github.com/ava-labs/avalanchego/utils/formatting" - "github.com/ava-labs/coreth/accounts/abi/bind" - "github.com/ava-labs/coreth/core/types" - "github.com/ava-labs/coreth/ethclient" - "github.com/ava-labs/coreth/params" - "github.com/ava-labs/coreth/rpc" + "github.com/ava-labs/avalanchego/graft/coreth/accounts/abi/bind" + "github.com/ava-labs/avalanchego/graft/coreth/core/types" + "github.com/ava-labs/avalanchego/graft/coreth/ethclient" + "github.com/ava-labs/avalanchego/graft/coreth/params" + "github.com/ava-labs/avalanchego/graft/coreth/rpc" "github.com/decred/dcrd/dcrec/secp256k1/v3" "github.com/ethereum/go-ethereum/common" "github.com/ethereum/go-ethereum/crypto" diff --git a/content/docs/primary-network/index.mdx b/content/docs/primary-network/index.mdx index 3655a7baf33..7d0a6856140 100644 --- a/content/docs/primary-network/index.mdx +++ b/content/docs/primary-network/index.mdx @@ -75,7 +75,7 @@ A node can become a validator for the Primary Network by staking at least **2,00 The **C-Chain** is an implementation of the Ethereum Virtual Machine (EVM). The [C-Chain's API](/docs/rpcs/c-chain) supports Geth's API and supports the deployment and execution of smart contracts written in Solidity. -The C-Chain is an instance of the [Coreth](https://github.com/ava-labs/coreth) Virtual Machine. +The C-Chain is an instance of the [Coreth](https://github.com/ava-labs/avalanchego/tree/master/graft/coreth) Virtual Machine. | Property | Mainnet | Fuji Testnet | |----------|---------|--------------| diff --git a/style-guide.md b/style-guide.md index f47fbaae06c..76080b39616 100644 --- a/style-guide.md +++ b/style-guide.md @@ -18,7 +18,7 @@ with the following exceptions: ### Virtual Machines r -- Coreth for [https://github.com/ava-labs/coreth] +- Coreth for [https://github.com/ava-labs/avalanchego/tree/master/graft/coreth] - Subnet-EVM for [https://github.com/ava-labs/subnet-evm] - TimestampVM for [https://github.com/ava-labs/timestampvm] - XSVM for [https://github.com/ava-labs/xsvm]