From 576546188cfe2c2796191036c6aa279b9da278d6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E9=99=88=E5=BF=97=E5=90=8C?= Date: Wed, 22 May 2024 11:49:49 +0800 Subject: [PATCH 1/3] Datoshi --- docs/n3/foundation/Native tokens.md | 4 +++- docs/n3/foundation/governance.md | 4 +++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/n3/foundation/Native tokens.md b/docs/n3/foundation/Native tokens.md index 99e7833..ad382f3 100644 --- a/docs/n3/foundation/Native tokens.md +++ b/docs/n3/foundation/Native tokens.md @@ -11,7 +11,9 @@ There are 2 kinds of native tokens defined in the Neo system: NEO and NeoGas (GA NEO is the Governing Token. Neo holders can participate in Neo network management, including voting for consensus nodes, network parameter modification, etc. The total amount of NEO is 100 million. Its minimum unit is 1 and can not be divided. It's registered in Genesis block, and stored in standby validators' muti-signature addresses. -GAS is the fuel token for the realization of Neo network resource control, with a smallest unit of 0.00000001. Users can obtain GAS either through a claim or purchase. When using the Neo network, they need to pay a certain amount of GAS as network fees, such as transfer, registering assets, publishing assets, running DApps, etc. +GAS is the fuel token for the realization of Neo network resource control, with a smallest unit of 0.00000001, also known as a Datoshi. Users can obtain GAS either through a claim or purchase. When using the Neo network, they need to pay a certain amount of GAS as network fees, such as transfer, registering assets, publishing assets, running DApps, etc. + +To further elaborate, the smallest unit of GAS is Datoshi, where 1 Datoshi = 1e-8 GAS. Larger units of GAS can also be expressed in Datoshi. For instance, 1 Kdatoshi (thousand Datoshi) = 1e-5 GAS and 1 Mdatoshi (million Datoshi) = 1e-2 GAS. In other words, 100,000,000 Datoshi = 100,000 Kdatoshi = 100 Mdatoshi = 1 GAS. This system of measurement allows for precise calculations and transactions on the Neo network. The Neo N3 Genesis block will mint the exact amount of GAS token needed to account for all GAS token circulating on the NEO Legacy chain at the time of Genesis block. diff --git a/docs/n3/foundation/governance.md b/docs/n3/foundation/governance.md index 9fba62d..f68d497 100644 --- a/docs/n3/foundation/governance.md +++ b/docs/n3/foundation/governance.md @@ -48,7 +48,9 @@ NEO has a max supply of 100 million tokens and the smallest unit of 1, or in oth ### GAS -GAS is the fuel token for the realization of Neo network resource control, with a smallest unit of 0.00000001. Users can obtain GAS either through a claim or purchase. When using the Neo network, they need to pay a certain amount of GAS as network fees, such as transfer, registering assets, publishing assets, running DApps, etc. +GAS is the fuel token for the realization of Neo network resource control, with a smallest unit of 0.00000001, also known as a Datoshi. Users can obtain GAS either through a claim or purchase. When using the Neo network, they need to pay a certain amount of GAS as network fees, such as transfer, registering assets, publishing assets, running DApps, etc. + +To further elaborate, the smallest unit of GAS is Datoshi, where 1 Datoshi = 1e-8 GAS. Larger units of GAS can also be expressed in Datoshi. For instance, 1 Kdatoshi (thousand Datoshi) = 1e-5 GAS and 1 Mdatoshi (million Datoshi) = 1e-2 GAS. In other words, 100,000,000 Datoshi = 100,000 Kdatoshi = 100 Mdatoshi = 1 GAS. This system of measurement allows for precise calculations and transactions on the Neo network. Unlike the Neo Legacy, there is no supply limit for Neo N3 GAS, and the system fee for transactions will be burned off. From afb370fa280f8e23aece1dab208317adbcf088c7 Mon Sep 17 00:00:00 2001 From: Celia18305 Date: Mon, 27 May 2024 20:04:14 +0800 Subject: [PATCH 2/3] Update hash_algorithm.md --- docs/n3/foundation/Cryptography/hash_algorithm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/n3/foundation/Cryptography/hash_algorithm.md b/docs/n3/foundation/Cryptography/hash_algorithm.md index 7aaf483..9520f6c 100644 --- a/docs/n3/foundation/Cryptography/hash_algorithm.md +++ b/docs/n3/foundation/Cryptography/hash_algorithm.md @@ -2,7 +2,7 @@ Hash function, or hash algorithm, is a method creating digital finger print from any kind of data. Hash function compresses message or data into a digested version to shrink the data into a fixed data size. This function disorganizes and remixes data, rebuilding a data fingerprint as a hash value. Hash value is always represented by a short string consisting of random letters and digits. -Two different hash functions are used widely in the Neo system: SHA256 and RIPEMD160. The former is used to generate a longer hash value (32 bytes) and the latter is used to generate a shorter hash value (20 bytes). Usually when a hash value of an object is generated, hash functions are used twice. For example, when a hash of a block or transaction is generated, SHA256 is calculated twice; when a contract address is generated, the SHA256 hash of the script is calculated, then the NSPEMD160 hash of the previous hash is calculated. +Two different hash functions are used widely in the Neo system: SHA256 and RIPEMD160. The former is used to generate a longer hash value (32 bytes) and the latter is used to generate a shorter hash value (20 bytes). Usually when a hash value of an object is generated, hash functions are used twice. For example, when a hash of a block or transaction is generated, SHA256 is calculated twice; when a contract address is generated, the SHA256 hash of the script is calculated, then the RIPEMD160 hash of the previous hash is calculated. In addition, the block will also use a hash structure called a Merkle Tree. It computes the hash of each transaction and combines one with the next and then hashes again, repeating this process until there is only one root hash (Merkle Root). From c068882d819064bc9089483742ddd1eb6b9a00a9 Mon Sep 17 00:00:00 2001 From: Apisit Date: Sun, 2 Jun 2024 14:42:57 +0900 Subject: [PATCH 3/3] Update _tailwind.css --- src/css/_tailwind.css | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/css/_tailwind.css b/src/css/_tailwind.css index f7d0cce..4f0c6ba 100644 --- a/src/css/_tailwind.css +++ b/src/css/_tailwind.css @@ -55,6 +55,9 @@ ul, ol { margin-left: 20px; } + ul li p, ol li p { + display: inline; + } }