Commit 3141a074 authored by inertia's avatar inertia
Browse files

#66 Swtiched out SP to HP

parent 9c8265ea
......@@ -1258,7 +1258,7 @@
purpose: |
**Deprecated as of HF20** If an account creation service would still like to provide a delegation of Hive Power
to the accounts they create, they can still follow the account creation operation with an additional call to
`delegate_vesting_shares` to add a delegation of SP to the account.
`delegate_vesting_shares` to add a delegation of HP to the account.
>Instead of paying the entire account creation fee with Hive, creators
can now pay a smaller fee (30x less) and delegate some Hive Power for
......@@ -1684,7 +1684,7 @@
purpose: |
Created once per maintenance interval to document how much HBD was
added to the threasury from inflation in that maintenance interval
(i.e., to track the funding of the SPS).
(i.e., to track the funding of the DHF).
roles:
- active
owner
......
......@@ -58,7 +58,7 @@ const reward_hive = _accounts[0].reward_hive_balance.split(' ')[0];
const reward_hbd = _accounts[0].reward_hbd_balance.split(' ')[0];
const reward_sp = _accounts[0].reward_vesting_hive.split(' ')[0];
const reward_vests = _accounts[0].reward_vesting_balance.split(' ')[0];
const unclaimed_balance = `Unclaimed balance for ${name}: ${reward_hive} HIVE, ${reward_hbd} HBD, ${reward_sp} SP = ${reward_vests} VESTS<br/>`;
const unclaimed_balance = `Unclaimed balance for ${name}: ${reward_hive} HIVE, ${reward_hbd} HBD, ${reward_sp} HP = ${reward_vests} VESTS<br/>`;
document.getElementById('accList').innerHTML = unclaimed_balance;
document.getElementById('hive').value = reward_hive;
document.getElementById('hbd').value = reward_hbd;
......
......@@ -11,7 +11,7 @@ This tutorial will take you through the process of checking a specific users' da
Providing another user active permission for your account enables them to do fund transfers from your account. This can be usefull in setting up a secondary account(s) to manage funds for a main account or having a backup should you lose passwords for the main account.
One of the common practice nowadays is to lend/delegate SP to another account, above same technique can be used to create market around it with minimum 3rd party trust. All your funds stay in your account. You can use/create automated system where you can lease for certain period of time and system can take care of payments and release of delegations (notify clients). Even better, you can use multi-signature feature to establish 100% trust where clients will have to confirm, approve transactions.
One of the common practice nowadays is to lend/delegate HP to another account, above same technique can be used to create market around it with minimum 3rd party trust. All your funds stay in your account. You can use/create automated system where you can lease for certain period of time and system can take care of payments and release of delegations (notify clients). Even better, you can use multi-signature feature to establish 100% trust where clients will have to confirm, approve transactions.
Active permissions and authority should be used with utmost care, you don't want to loose your funds. It is really not easy to hack Hive accounts, let alone take control over it. But without careful use (revealing private keys) loosing liquid funds are not that difficult and it takes only couple seconds to do that, keeping most value powered up always helps.
......
......@@ -11,7 +11,7 @@ In this tutorial we show you how to check if someone has got active permission f
Providing another user active permission for your account enables them to do fund transfers from your account. This can be useful in setting up a secondary account(s) to manage funds for a main account or having a backup should you lose passwords for the main account.
One of the common practice nowadays is to lend/delegate SP to another account, above same technique can be used to create market around it with minimum 3rd party trust. All your funds stay in your account. You can use/create automated system where you can lease for certain period of time and system can take care of payments and release of delegations (notify clients). Even better, you can use [multi-signature <i class="fas fa-search fa-xs" />]({{ '/search?q=multisig' | relative_url }}) feature to establish 100% trust where clients will have to confirm, approve transactions.
One of the common practice nowadays is to lend/delegate HP to another account, above same technique can be used to create market around it with minimum 3rd party trust. All your funds stay in your account. You can use/create automated system where you can lease for certain period of time and system can take care of payments and release of delegations (notify clients). Even better, you can use [multi-signature <i class="fas fa-search fa-xs" />]({{ '/search?q=multisig' | relative_url }}) feature to establish 100% trust where clients will have to confirm, approve transactions.
Active permissions and authority should be used with utmost care, you don't want to lose your funds. It is really not easy to hack Hive accounts, let alone take control over it. But without careful use (revealing private keys) losing liquid funds are not that difficult and it takes only couple seconds to do that, keeping most value powered up always helps.
......
......@@ -97,11 +97,11 @@ Suppose an account has 15 Hive Power. How much can it vote?
```
This is the amount of Hive Power (in satoshis) that would be needed by an account to transact once per 5 days ([`HIVE_RC_REGEN_TIME`]({{ '/tutorials-recipes/understanding-configuration-values.html#HIVE_RC_REGEN_TIME' | relative_url }})).
Our 15 SP account has 15000 SP, so it would be able to do `15000 / 138`, or about `108`, such transactions per 5 days.
Our 15 HP account has 15000 HP, so it would be able to do `15000 / 138`, or about `108`, such transactions per 5 days.
You can regard the number `138` (or `0.138`) as the "cost" of a "standardized" vote transaction. It plays an analogous role to a
transaction fee in Bitcoin, but it is not exactly a fee. Because the word "fee" implies giving up a permanent token with a limited,
controlled emission rate. It is the amount of SP which will allow a user an additional vote transaction every 5 days (but it might
controlled emission rate. It is the amount of HP which will allow a user an additional vote transaction every 5 days (but it might
be slightly more or less, if your vote transactions use a slightly different amount of resources.)
### Integrating the demo script
......
......@@ -78,7 +78,7 @@ Once you have claimed a token, broadcast the `create_claimed_account` operation
]
```
Accounts created with this method, don't have any SP, but do have enough RC to interact with the chain at a starting level.
Accounts created with this method, don't have any HP, but do have enough RC to interact with the chain at a starting level.
#### 2. Non-discounted account creation<a name="nondisc"></a>
......
......@@ -11,7 +11,7 @@ Since HF20 a Resource Credit (RC) system has been implemented to manage the numb
## Intro
RCs are non-transferable credits that accrue to each Hive account based on how much Hive Power(SP) it has. An account spends RC when it transacts on the Hive blockchain. RCs regenerate over a 5 day period. If an account doesn’t have sufficient credits, the transaction will not be allowed to occur.
RCs are non-transferable credits that accrue to each Hive account based on how much Hive Power (HP) it has. An account spends RC when it transacts on the Hive blockchain. RCs regenerate over a 5 day period. If an account doesn’t have sufficient credits, the transaction will not be allowed to occur.
The price of a transaction (which consumes a particular resource, or resources) is based on the current stockpile of those resources. As a stockpile of a resource decreases, the RC cost of that resource increases. In other words, as the stockpile goes down, accounts will have to pay more RCs to use the remaining resources. This system disincentivize the over-consumption of resources by users as well as spam.
......@@ -21,7 +21,7 @@ There are applications available to check an account's status, like [hiveblocks.
## Calculating available RC
Since RC is calculated relative to SP, we first need to know the available SP before we can calculate how much RC we have left. The value of the current available mana(RC) is also accessible as a field from the `getAccounts` function.
Since RC is calculated relative to HP, we first need to know the available HP before we can calculate how much RC we have left. The value of the current available mana(RC) is also accessible as a field from the `getAccounts` function.
```javascript
//capture account
......@@ -29,7 +29,7 @@ var _account = await client.database.getAccounts(['username'])
var account = _account[0]
var props = await client.database.getDynamicGlobalProperties()
var CURRENT_UNIX_TIMESTAMP = parseInt((new Date(props.time).getTime() / 1000).toFixed(0))
//calculate available SP
//calculate available HP
var totalShares = parseFloat(account.vesting_shares) + parseFloat(account.received_vesting_shares) - parseFloat(account.delegated_vesting_shares);
//determine elapsed time since last RC update
var elapsed = CURRENT_UNIX_TIMESTAMP - account.voting_manabar.last_update_time;
......
......@@ -13,7 +13,7 @@ See also [RC Bandwidth Parameters]({{ '/tutorials-recipes/rc-bandwidth-parameter
The *RC bandwidth system* is a complete rewrite of the bandwidth system. Its goals include:
- Enable simple, effective UI feedback to users about bandwidth usage and remaining bandwidth
- Simplify the mental model of what buying additional SP gives users
- Simplify the mental model of what buying additional HP gives users
- Reduce or eliminate unstable feedback in current bandwidth system
### History
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment