Conflux Developer Documentation: https://developer.confluxnetwork.org
|Conflux Scan (Blockchain explorer)||https://www.confluxscan.io/|
|Conflux Tethys chain_id||1029|
|Public RPC node url (support CIP37 address)||Mainnet:https://main.confluxrpc.com
Test network: https://test.confluxrpc.com
Conflux public rpc doc: https://github.com/conflux-fans/conflux-rpc-endpoints
Service usability not is guaranteed, developers and testers only
|Github source address: Fullnode||https://github.com/Conflux-Chain/conflux-rust|
|Fullnode Config File||http://developer.confluxnetwork.org/docs/apis/en/node_config_example|
|How to run a Conflux node||Conflux Tethys GPU Mining Instruction (v1.1.6-fix)|
|Mainnet data requirements||Full node: 200GB|
|Mainnet snapshot address (used for accelerated synchronizing; specify if the service is provided)||/|
|Block generation rate||0.5s per block|
|Confirmation rules||RPC now provides two ports for confirmation:
if return_value/(2^256) <= 1/10^8, it indicates confirmation and returns the integer confirmation risk, which is also the probability of pivot chain switch.
This RPC corresponds to “latest_confirmed”, it returns the latest confirmed integer epoch number. It indicates confirmation if this epoch is greater or equal to what you last saw in exchange. The internal logic is the same behind both methods.
|Currency precision||The minimum unit is drip, 1 drip = 1/10^18 CFX|
|Storing the transaction index accessing historical data through RPC||1. locate “tethys.toml”, add “persist_tx_index=true”
2. conflux --config tethys.toml
|How to configure the port of RPC node and the data storage location?||HTTP RPC port is configurable in the “toml” file through “jsonrpc_tcp_port” command, there are similar file types such as: “jsonrpc_ws_port”, “jsonrpc_tcp_port”, “jsonrpc_http_port”, “jsonrpc_local_tcp_port”, “jsonrpc_local_http_port”.
Default “tethys.toml” configuration file is located under the release tab for reference.
Default data storage is located in “blockchain_db” and “storage_db” under the execution path (PWD), which is configurable through the “conflux_data_dir” and “block_db_dir” files.
Note: “persist_tx_index” must be set to “true” in order to access the historical receipt data.
|Links for Conflux RPC / SDK||Conflux SDK: https://developer.conflux-chain.org/
Conflux public RPC: https://github.com/conflux-fans/conflux-rpc-endpoints
|Fullnode RPC standard||JSON RPC 2.0|
|Get the current block height||cfx_epochNumber|
|Get all transactions of a specific block||cfx_getBlockByHash|
|Get specific transaction detail||cfx_getTransactionByHash|
|How to validate transactions to prevent pseudo deposits?||The “cfx_getConfirmationRiskByHash” command assesses the safety of the block where the transaction is being executed. The probability of revert is equal to return_value/2^256. For small transactions, we are aiming for a probability less than 1/10^8; For large transactions, we would like the targeted probability of revert to be smaller.|
|Transfer recommendation: offline signature + online broadcasting would be ideal||1）Sign through SDK related API, reference: https://developer.conflux-chain.org/
2）Send/broadcast transaction: cfx_sendRawTransaction;
|Check remaining balance on the address||cfx_getBalance|
|Precautions for fork attack||Conflux incorporates all honest blocks as valid blocks into a tree chart ledger structure. It uses the GHAST consensus algorithm (heaviest subtree rule) to prevent double-spending attacks. The security assumption is that the computing power of honest nodes exceeds 50%.|
|Store the state for a longer time in the past||The default configuration only stores the status of the latest 4000 epoch, it is modifiable through “additional_maintained_snapshot_count” to inquire older data.
The system stores up to 2 days of data if the count # is set to 100.
Error message “State for epoch (number=… hash=…) does not exist: out-of-bound…” occurs when accessing obsolete data.