Commit b2e0c556 authored by inertia's avatar inertia
Browse files

Merge branch 'rc-system' into 'develop'

#50 follow-up

See merge request !105
parents eb68ecd9 f9c0b4c2
......@@ -34,7 +34,7 @@ are consumed by a vote transaction? The `rcdemo` script allows us to find out:
The `count_resources()` function is *stateless*. That means all of the information needed to do the calculation is contained in the transaction itself. It doesn't
depend on what's happening on the blockchain, or what other users are doing. [1] [2] [3]
[1] Although it is possible that the calculation will change in future versions of `hived`, for example to correct the [bug](https://github.com/steemit/steem/issues/2972) where execution time is always reported as zero.
[1] Although it is possible that the calculation will change in future versions of `hived`, for example to correct the [bug]({{ 'https://github.com/steemit/steem/issues/2972' | archived_url }}) where execution time is always reported as zero.
[2] For convenience, some of the constants used in the calculation are exposed by the `size_info` member of `rc_api.get_resource_params()`. Only a `hived` version upgrade can change any values returned by `rc_api.get_resource_params()`, so it is probably okay to query that API once, on startup or when first needed, and then cache the result forever. Or even embed the result of `rc_api.get_resource_params()` in the source code of your library or application.
......@@ -48,7 +48,7 @@ Let's go into details on the different kinds of resources which are limited by t
- `resource_new_accounts` : Number of accounts created by the transaction.
- `resource_market_bytes` : Number of bytes consumed by the transaction if it contains market operations.
- `resource_state_bytes` : Number of bytes of chain state needed to support the transaction.
- `resource_execution_time` : An estimate of how long the transaction will take to execute. Zero for now due to [#2972](https://github.com/steemit/steem/issues/2972).
- `resource_execution_time` : An estimate of how long the transaction will take to execute. Zero for now due to [#2972]({{ 'https://github.com/steemit/steem/issues/2972' | archived_url }}).
The resources have different scales. The resources use fixed-point arithmetic where one "tick" of the resource value is a "fractional" value of the resource. Right now, the resource scales are scattered in different places. The `count_resources()` result has the following scale:
......
......@@ -10,7 +10,7 @@ canonical_url: forum-market-bandwidth.html
### Intro
<h4 class="danger well">
Please note, Bandwidth has been replaced by <a href="{{ '/search/?q=resource+credits' | relative_url }}">Resource Credits</a>. This document is outdated and will remain in place to give historical context prior to HF20. Also see: <a href="https://github.com/steemit/steem/wiki/RC-Bandwidth-System">RC Bandwidth System</a>, <a href="https://github.com/steemit/steem/releases/tag/v0.20.2">0.20.2 Release Notes</a>, <a href="https://hive.blog/steem/@steemitdev/developer-guide-resource-credit-system">Developer Guide: Resource Credit System</a>
Please note, Bandwidth has been replaced by <a href="{{ '/search/?q=resource+credits' | relative_url }}">Resource Credits</a>. This document is outdated and will remain in place to give historical context prior to HF20. Also see: <a href="{{ '/tutorials-recipes/rc-bandwidth-system.html' | relative_url }}">RC Bandwidth System</a>, <a href="{{ 'https://github.com/steemit/steem/releases/tag/v0.20.2' | archived_url }}">0.20.2 Release Notes</a>, <a href="https://hive.blog/steem/@steemitdev/developer-guide-resource-credit-system">Developer Guide: Resource Credit System</a>
</h4>
We're going over the various API calls needed to determine the remaining bandwidth available to a particular account. As mentioned in the [HIVE Whitepaper](https://hive.io/steem-whitepaper.pdf):
......
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