Encoding & Signing
After every field of a transaction is prepared, following steps are required before it can be sent to network (don't worry, these steps are already implemented by wallets or SDKs):
After every field of a transaction is prepared, following steps are required before it can be sent to network (don't worry, these steps are already implemented by wallets or SDKs):
Misc
Transaction is an important concept in blockchain. If you are not familiar with the concept of transactions and would like to quickly understand it, you can read Transaction Quick Intro.
When using SDK or the Fluent wallet to send transactions, you may encounter some errors. This document outlines some common errors and their solutions.
Una transacción es una única instrucción compuesta por un actor externo con una cuenta de Conflux, y esta instrucción está firmada criptográficamente usando la clave privada de la cuenta del remitente. Una transacción puede implicar una transferencia simple de CFX (la moneda nativa de Conflux), una transferencia de tokens (como ERC20 o ERC721), un despliegue de un nuevo contrato inteligente, o una ejecución de una función en un contrato inteligente existente. Las transacciones son la única forma de almacenar o actualizar datos en la cadena de bloques.
In the Conflux Core Space, transactions are processed by miners who charge a fee for their service. This fee incentivises miners to participate in the network and keep it running smoothly. The fees are paid in CFX and are specified by the transaction initiator through the gas, gasPrice and storageLimit fields in the transaction.
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.
Because today’s blockchain systems may have problems such as low throughput and high entry barriers, it is inevitable that some transactions will not be packaged when sent through the blockchain. Take Conflux as an example, the Conflux network normally produces two blocks per second. After a transaction is successfully sent, it should be packaged and executed within 20 seconds depending on the network congestion level. If the transaction is not packaged for a long time, it’s very likely that something went wrong, and requires the sender to manually intervene.