18 docs tagged with "Contract Deployment"

Overview

Behaviour of cfx_estimateGasAndCollateral

This tutorial will guide you through the steps to create, write, and deploy an ERC1155 NFT smart contract on Conflux CoreSpace using Hardhat. Additionally, it will show you how to view your contract on ConfluxScan. You can find a practical example in the Conflux-NFT-CRC1155 repository.

This tutorial guides developers on transferring any CRC20 token from Core Space to eSpace, The goal is to transfer a CRC20 token (A) issued on coreSpace to become an ERC20 token (eA) in eSpace. Currently, if there is no corresponding token in eSpace, it's not possible to use the official cross-space bridge directly.

This tutorial will guide you through the steps to create, write, and deploy an CRC721 NFT smart contract on Conflux CoreSpace using Hardhat. Additionally, it will show you how to view your contract on ConfluxScan.

CIP-90 introduces a new internal contract: CrossSpaceCall. CrossSpaceCall enables CFX and data to be transferred between the two spaces.

Detail explain of CrossSpaceCall contract

Developers can submit a request to the Foundation for sponsorship.

Tutorial for using the Hardhat Conflux Plugin

Using a Merkle Tree whitelist provides a cost-efficient way to distribute NFTs to a predefined list of addresses. It ensures that only whitelisted addresses can mint the NFTs, enhancing security and efficiency. Writing a whitelist of thousands of addresses directly within a smart contract would result in significant gas costs, and additionally, due to the maximum transaction gas limit restriction, it might be impractical to update such a large whitelist in a single transaction. However, since in the Merkle Tree verification process, leaf nodes and proofs can be stored off-chain while only the root value needs to be stored on-chain, this method significantly saves on gas costs and enables whitelist setup with only one transaction.

Conflux has SDKs for mainstream programming languages, including JavaScript, Golang, Java and Python. This is just a short introduction to the SDKs, for detailed usage info, check their respective documentation.

Conflux Core Space implements a sponsorship mechanism to subsidize the usage of smart contracts. Thus, a new account with zero balance is able to call smart contracts as long as the execution is sponsored (usually by the operator of Dapps). This mechanism is designed to reduce the barrier of entry for new users.

Through trace RPCs we can know the transaction executive details. To use these RPC Conflux archive node need set two additional config:

In order to encode a Core Space transaction, the following fields are required:

Transaction receipt is the data structure that contains information about the transaction execution result.

Deploy contracts on Core Space with ChainIDE

This page is meant to guide you through the basics on how to use web3.js when developing on Conflux eSpace.

This page is meant to guide you through the basics on how to use web3.py when developing on Conflux eSpace.