Glossary

energyUsage

The Energy conumption of the contract caller in one contract trigger.

energyFee

The number of ORGON burned from the contract caller for Energy conumption in one contract trigger.

originEnergyUsage

The total Energy conumption of the contract developer in one contract trigger.

energyUsageTotal

The total Energy conumption of the contract developer and the contract caller combined.

Feelimit

When the user triggers or create the contract, this is used to set the usage limit of the Energy consumption got from burning ORGON or staking ORGON, Energy got from staking ORGON will be used first.

CallValue

When the user triggers or create the contract, this can be used to send ORGON to the contract.

consume_user_resource_percent

For a contract, Resource consumption is composed of two parts, one part is afforded by contract developer and the other part is afforded by contract caller. This is the percentage of the two parts in the Resource consumption.

origin_energy_limit

The usage limit of the Energy consumption of the developer in one contract trigger, should be greater than 0.

net_usage

The Bandwidth consumption in one contract trigger. (NetFee not included)

net_fee

The ORGON burned for Bandwidth consumption in one contract trigger.

Bandwidth

The Bandwidth Points consumed by a transaction is the size of the byte array in this transaction. If the byte array length of a transaction is 100, then the transaction needs to consume 100 Bandwidth Points.

Energy

The creation and operation of a smart contract consume CPU resources. It takes time for smart contracts to operate in virtual machines (VMs), and the time consumed in the system is calculated in microseconds. CPU resources are consumed in energy, which means 1 Energy = 1 Microsecond (μs). If a contract takes 100 μs to execute in a VM, it needs to consume 100 Energy.

ORGON Power(TP)

1 staked ORGON = 1 TP, TP can be used to vote, 1 TP = 1 vote.

Super Representative(SR)

The current block producing Top 27 nodes.

---