You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An account can optionally elect to stake its HBAR to a node in the Hedera network. The staked node ID is the node an account can stake to. The full balance of the account is staked to the node. Do not confuse the node ID with the node's account ID. If you stake to the node's account ID, your account will not earn staking rewards. \
An account can optionally elect to stake its HBAR to another account in the Hedera network. This is known as **indirect staking**. The staked account ID is the ID of the account to stake to. The full balance of the account is staked to the specified account. \
207
207
\
@@ -217,7 +217,7 @@ Account ID: `0.0.10`
217
217
218
218
<details>
219
219
220
-
<summary>Decline to Earn Staking Rewards</summary>
220
+
<summary><strong>Decline to Earn Staking Rewards</strong></summary>
221
221
222
222
Accounts can decline to earn staking rewards when they stake to a node or an account. The staked account still contributes to the staking weight of the node, but does not earn rewards or is calculated as part of the payment of the rewards to the other accounts that have elected to earn rewards. By default, all staked accounts will earn rewards unless this boolean flag is set to true. This election can be changed by updating the account properties. Hedera treasury accounts enable this flag to decline earning staking rewards.\
223
223
\
@@ -251,7 +251,7 @@ The amount charged for renewal will be charged every pre-determined period in se
Copy file name to clipboardExpand all lines: core-concepts/accounts/auto-account-creation.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ The account alias can be either one of the supported types:
6
6
7
7
<details>
8
8
9
-
<summary>Public Key</summary>
9
+
<summary><strong>Public Key</strong></summary>
10
10
11
11
The public key alias can be an ED25519 or ECDSA secp256k1 public key type.\
12
12
\
@@ -36,7 +36,7 @@ EDDSA ED25519 Public Key Alias Account ID:\
36
36
37
37
<details>
38
38
39
-
<summary>EVM Address</summary>
39
+
<summary><strong>EVM Address</strong></summary>
40
40
41
41
The EVM address alias is created by using the rightmost 20 bytes of the 32 byte `Keccak-256` hash of an `ECDSA secp256k1` public key. This calculation is in the manner described by the [Ethereum Yellow Paper](https://ethereum.github.io/yellowpaper/paper.pdf). The EVM address is not equivalent to the ECDSA public key.\
42
42
\
@@ -75,7 +75,7 @@ The initial transfer of tokens to the alias account ID will do a few things:
75
75
3. Once the new account is officially created, the token transfer transaction instantiated by the user will transfer the tokens to the new account.
76
76
4. The account specified to pay for the token transfer transaction fees will also be charged the account creation transaction fees in tinybar.
77
77
78
-
The above interactions introduce the concept of [parent and child transactions](../transactions-and-queries.md#nested-transactions). The parent transaction is the transaction that represents the transfer of tokens from the sender account to the destination account. The child transaction is the transaction the system initiated to create the account. This concept is important since the parent transaction record or receipt will not return the new account number ID. You must get the transaction record or receipt of the child transaction. The parent and child transactions will share the same transaction ID, except the child transaction has an added nonce value.
78
+
The above interactions introduce the concept of [parent and child transactions](../transactions-and-queries/#nested-transactions). The parent transaction is the transaction that represents the transfer of tokens from the sender account to the destination account. The child transaction is the transaction the system initiated to create the account. This concept is important since the parent transaction record or receipt will not return the new account number ID. You must get the transaction record or receipt of the child transaction. The parent and child transactions will share the same transaction ID, except the child transaction has an added nonce value.
79
79
80
80
{% hint style="info" %}
81
81
**parent transaction**: the transaction responsible for transferring the tokens to the alias account ID destination account.
@@ -102,7 +102,7 @@ To update the hollow account into a complete account, the hollow account needs t
102
102
103
103
<details>
104
104
105
-
<summary>Auto-create an account using a public key alias</summary>
105
+
<summary><strong>Auto-create an account using a public key alias</strong></summary>
0 commit comments