![](\"https://i.imgur.com/fOScDIW.png\"/)
curl \n\nHello Steemians! If you’d like to meet Team Steemit live-in-person, or are just interested in attending what promises to be a great blockchain conference, join us at TokenFest in San Francisco from March 15th to 16th. \n\nSteemit CEO, Ned Scott, will be participating in a fireside chat alongside Steemit’s CTO, Harry Schmidt, as well as the creator of Utopian.io, Diego Pucci. Steemit will also be hosting the opening party on Thursday night and we’d certainly love to meet as many of you as possible IRL, so head on over to https://tokenfest.adria.digital/ and get your tickets while you can. \n\n*Team Steemit*",
+ "title": "Join Team Hive at TokenFest!",
+ "body": "\n\nHello Hiveians! If you’d like to meet Team Hive live-in-person, or are just interested in attending what promises to be a great blockchain conference, join us at TokenFest in San Francisco from March 15th to 16th. \n\nHive CEO, Ned Scott, will be participating in a fireside chat alongside Hive’s CTO, Harry Schmidt, as well as the creator of Utopian.io, Diego Pucci. Hive will also be hosting the opening party on Thursday night and we’d certainly love to meet as many of you as possible IRL, so head on over to https://tokenfest.adria.digital/ and get your tickets while you can. \n\n*Team Hive*",
"json_metadata": "{\"tags\":[\"steemit\",\"tokenfest\",\"conference\"],\"image\":[\"https://i.imgur.com/fOScDIW.png\"],\"links\":[\"https://tokenfest.adria.digital\",\"https://tokenfest.adria.digital/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"last_update": "2018-03-07T23:22:54",
"created": "2018-03-07T20:56:36",
@@ -23,21 +23,21 @@
"max_cashout_time": "1969-12-31T23:59:59",
"total_vote_weight": 3462435,
"reward_weight": 10000,
- "total_payout_value": "0.000 SBD",
- "curator_payout_value": "0.000 SBD",
+ "total_payout_value": "0.000 HBD",
+ "curator_payout_value": "0.000 HBD",
"author_rewards": 0,
"net_votes": 77,
"root_comment": 37338948,
- "max_accepted_payout": "0.000 SBD",
- "percent_steem_dollars": 10000,
+ "max_accepted_payout": "0.000 HBD",
+ "percent_hbd": 10000,
"allow_replies": true,
"allow_votes": true,
"allow_curation_rewards": true,
"beneficiaries": [],
"url": "/steemit/@steemitblog/join-team-steemit-at-tokenfest",
- "root_title": "Join Team Steemit at TokenFest!",
- "pending_payout_value": "46.436 SBD",
- "total_pending_payout_value": "0.000 STEEM",
+ "root_title": "Join Team Hive at TokenFest!",
+ "pending_payout_value": "46.436 HBD",
+ "total_pending_payout_value": "0.000 HIVE",
"active_votes": [
{
"voter": "steemitblog",
@@ -58,7 +58,7 @@
],
"replies": [],
"author_reputation": "128210130644387",
- "promoted": "0.000 SBD",
+ "promoted": "0.000 HBD",
"body_length": 754,
"reblogged_by": []
}
diff --git a/_includes/tutorials-javascript/get_posts.json b/_includes/tutorials-javascript/get_posts.json
index 9ae3e0e42ce562874c07ccd5ef16781b0db56d6f..5c1d59c2b6b607d79a862a1a9e81d28c2a31dfe4 100644
--- a/_includes/tutorials-javascript/get_posts.json
+++ b/_includes/tutorials-javascript/get_posts.json
@@ -6,9 +6,9 @@
"category": "steemit",
"parent_author": "",
"parent_permlink": "steemit",
- "title": "Join Team Steemit at TokenFest!",
+ "title": "Join Team Hive at TokenFest!",
"body":
- "\n\nHello Steemians! If you’d like to meet Team Steemit live-in-person, or are just interested in attending what promises to be a great blockchain conference, join us at TokenFest in San Francisco from March 15th to 16th. \n\nSteemit CEO, Ned Scott, will be participating in a fireside chat alongside Steemit’s CTO, Harry Schmidt, as well as the creator of Utopian.io, Diego Pucci. Steemit will also be hosting the opening party on Thursday night and we’d certainly love to meet as many of you as possible IRL, so head on over to https://tokenfest.adria.digital/ and get your tickets while you can. \n\n*Team Steemit*",
+ "\n\nHello Hiveians! If you’d like to meet Team Hive live-in-person, or are just interested in attending what promises to be a great blockchain conference, join us at TokenFest in San Francisco from March 15th to 16th. \n\nHive CEO, Ned Scott, will be participating in a fireside chat alongside Hive’s CTO, Harry Schmidt, as well as the creator of Utopian.io, Diego Pucci. Hive will also be hosting the opening party on Thursday night and we’d certainly love to meet as many of you as possible IRL, so head on over to https://tokenfest.adria.digital/ and get your tickets while you can. \n\n*Team Hive*",
"json_metadata":
"{\"tags\":[\"steemit\",\"tokenfest\",\"conference\"],\"image\":[\"https://i.imgur.com/fOScDIW.png\"],\"links\":[\"https://tokenfest.adria.digital\",\"https://tokenfest.adria.digital/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"last_update": "2018-03-07T23:22:54",
@@ -25,21 +25,21 @@
"max_cashout_time": "1969-12-31T23:59:59",
"total_vote_weight": 3462435,
"reward_weight": 10000,
- "total_payout_value": "0.000 SBD",
- "curator_payout_value": "0.000 SBD",
+ "total_payout_value": "0.000 HBD",
+ "curator_payout_value": "0.000 HBD",
"author_rewards": 0,
"net_votes": 77,
"root_comment": 37338948,
- "max_accepted_payout": "0.000 SBD",
- "percent_steem_dollars": 10000,
+ "max_accepted_payout": "0.000 HBD",
+ "percent_hbd": 10000,
"allow_replies": true,
"allow_votes": true,
"allow_curation_rewards": true,
"beneficiaries": [],
"url": "/steemit/@steemitblog/join-team-steemit-at-tokenfest",
- "root_title": "Join Team Steemit at TokenFest!",
- "pending_payout_value": "46.436 SBD",
- "total_pending_payout_value": "0.000 STEEM",
+ "root_title": "Join Team Hive at TokenFest!",
+ "pending_payout_value": "46.436 HBD",
+ "total_pending_payout_value": "0.000 HIVE",
"active_votes": [
{
"voter": "steemitblog",
@@ -60,7 +60,7 @@
],
"replies": [],
"author_reputation": "128210130644387",
- "promoted": "0.000 SBD",
+ "promoted": "0.000 HBD",
"body_length": 754,
"reblogged_by": []
},
diff --git a/_plugins/post_generator.rb b/_plugins/post_generator.rb
index f96e93ea9e1d9564b0231f130221241908f93b1f..04102bc8dafe5b839112667826c5655e6d79f9e2 100644
--- a/_plugins/post_generator.rb
+++ b/_plugins/post_generator.rb
@@ -1,4 +1,4 @@
-require 'steem'
+require 'hive'
module Jekyll
module HivePostGenerator
@@ -9,7 +9,7 @@ module Jekyll
permlink = slug[1..-1].join('/')
permlink = permlink.split('?').first
permlink = permlink.split('#').first
- api = Steem::CondenserApi.new(url: 'https://api.openhive.network')
+ api = Hive::CondenserApi.new(url: 'https://api.hive.blog')
api.get_content(author, permlink) do |content|
body = content.body
@@ -56,6 +56,6 @@ Liquid::Template.register_filter(Jekyll::HivePostGenerator)
#
# NOTE:
# For content prior to the Hive fork, please remember to maintain the correct
-# canonical_url, even if it appears on a Steem front-end, unless the original
-# author removed it from Steem. SEO will still consider Steem as the origin,
+# canonical_url, even if it appears on a Hive front-end, unless the original
+# author removed it from Hive. SEO will still consider Hive as the origin,
# even after the Hive fork.
diff --git a/_quickstart/choose_library.md b/_quickstart/choose_library.md
index 17d633b65aa1cbac1b5870bd698175bf369b44ea..2d3018cb5b5801baa5c2c6951c87590648960636 100644
--- a/_quickstart/choose_library.md
+++ b/_quickstart/choose_library.md
@@ -6,4 +6,4 @@ exclude: true
Getting started to develop robust and feature rich **Hive** applications couldn't be easier. Accessing hive data is easy from various options depending on your infrastructure and objectives.
-Building a picture discovery app is a breeze with the [JavaScript]({{ '/tutorials/#tutorials-javascript' | relative_url }}) library. There is also a [Python]({{ '/tutorials/#tutorials-python' | relative_url }}) library available, [Steemit.com]({{ '/services/#services-steemit' | relative_url }}) and [SBDS]({{ '/services/#services-sbds' | relative_url }}) services, as well as many [community projects]({{ '/resources/#resources-overview' | relative_url }}) which could be beneficial for your steem project.
+Building a picture discovery app is a breeze with the [JavaScript]({{ '/tutorials/#tutorials-javascript' | relative_url }}) library. There is also a [Python]({{ '/tutorials/#tutorials-python' | relative_url }}) library available, [Hive.com]({{ '/services/#services-steemit' | relative_url }}) and [HBDS]({{ '/services/#services-hbds' | relative_url }}) services, as well as many [community projects]({{ '/resources/#resources-overview' | relative_url }}) which could be beneficial for your steem project.
diff --git a/_quickstart/hive_full_nodes.md b/_quickstart/hive_full_nodes.md
index 2f4c80dbbf6ad2beab5f999e33660ef96fcc2272..fd5cb2323e5f7997bfc37aa76371895aaa0a5a0a 100644
--- a/_quickstart/hive_full_nodes.md
+++ b/_quickstart/hive_full_nodes.md
@@ -40,13 +40,13 @@ _to run a node with all the data (e.g. for supporting a content website) that us
### Syncing blockchain
-Normally syncing blockchain starts from very first, `0` genesis block. It might take long time to catch up with live network. Because it connectes to various p2p nodes in the Steem network and requests blocks from 0 to head block. It stores blocks in block log file and builds up the current state in the shared memory file. But there is a way to bootstrap syncing by using trusted `block_log` file. The block log is an external append only log of the blocks. It contains blocks that are only added to the log after they are irreversible because the log is append only.
+Normally syncing blockchain starts from very first, `0` genesis block. It might take long time to catch up with live network. Because it connectes to various p2p nodes in the Hive network and requests blocks from 0 to head block. It stores blocks in block log file and builds up the current state in the shared memory file. But there is a way to bootstrap syncing by using trusted `block_log` file. The block log is an external append only log of the blocks. It contains blocks that are only added to the log after they are irreversible because the log is append only.
Trusted block log file helps to download blocks faster. Various operators provide public block log file which can be downloaded from:
- http://files.privex.io
- https://gtg.steem.house/get/blockchain
-Both `block_log` files updated periodically, as of April 2020 uncompressed `block_log` file size ~260 GB. (Docker container on `stable` branch of Hive source code has option to use `USE_PUBLIC_BLOCKLOG=1` to download latest block log and start Steem node with replay.)
+Both `block_log` files updated periodically, as of April 2020 uncompressed `block_log` file size ~260 GB. (Docker container on `stable` branch of Hive source code has option to use `USE_PUBLIC_BLOCKLOG=1` to download latest block log and start Hive node with replay.)
Block log should be place in `blockchain` directory below `data_dir` and node should be started with `--replay-blockchain` to ensure block log is valid and continue to sync from the point of snapshot. Replay uses the downloaded block log file to build up the shared memory file up to the highest block stored in that snapshot and then continues with sync up to the head block.
@@ -66,7 +66,7 @@ Above bash script drops `block_log` from the OS cache, leaving more memory free
##### Few other tricks that might help:
-For Linux users, virtual memory writes dirty pages of the shared file out to disk more often than is optimal which results in steemd being slowed down by redundant IO operations. These settings are recommended to optimize reindex time.
+For Linux users, virtual memory writes dirty pages of the shared file out to disk more often than is optimal which results in hived being slowed down by redundant IO operations. These settings are recommended to optimize reindex time.
```
echo 75 | sudo tee /proc/sys/vm/dirty_background_ratio
@@ -80,16 +80,16 @@ Another settings that can be changed in `config.ini` is `flush` - it is to speci
(below info is outdated - need updating)
``` bash
docker run \
- -d -p 2001:2001 -p 8090:8090 --name steemd-default \
+ -d -p 2001:2001 -p 8090:8090 --name hived-default \
steemit/steem
-docker logs -f steemd-default # follow along
+docker logs -f hived-default # follow along
```
``` bash
docker run \
--env USE_WAY_TOO_MUCH_RAM=1 \
- -d -p 2001:2001 -p 8090:8090 --name steemd-full \
+ -d -p 2001:2001 -p 8090:8090 --name hived-full \
steemit/steem
-docker logs -f steemd-full
+docker logs -f hived-full
```
diff --git a/_quickstart/testnet.md b/_quickstart/testnet.md
index cb48eeff5adcb446e79116a9a6fef47df9b69492..184c38632be99e199472e55e4c516642709d4c9a 100644
--- a/_quickstart/testnet.md
+++ b/_quickstart/testnet.md
@@ -14,11 +14,11 @@ More info soon
### Features
*Old text: Will be replaced:*
-The official Steemit, Inc. Testnet is a mirror of the mainnet. This is achieved by copying the existing accounts and transactions from the mainnet state, as the they happen. Accounts are copied from a [snapshot](https://github.com/steemit/tinman#taking-a-snapshot) of mainnet while the module used to copy transactions in real time is called [`gatling`](https://github.com/steemit/tinman#gatling-transactions-from-mainnet). The `gatling` module runs at the final step of each testnet deployment.
+The official Hive Testnet is a mirror of the mainnet. This is achieved by copying the existing accounts and transactions from the mainnet state, as the they happen. Accounts are copied from a [snapshot](https://github.com/steemit/tinman#taking-a-snapshot) of mainnet while the module used to copy transactions in real time is called [`gatling`](https://github.com/steemit/tinman#gatling-transactions-from-mainnet). The `gatling` module runs at the final step of each testnet deployment.
The combination of `snapshot` and `gatling` means that this testnet approaches a subset of the same activity that the mainnet experiences. Not everything can be mirrored. For example, if someone comments or votes on a post that hasn't been mirrored to the testnet (because the post itself pre-dates the testnet deploy), those operations will also not be included.
-At the time of this writing, the connection information for Steemit's testnet is as follows:
+At the time of this writing, the connection information for Hive's testnet is as follows:
* ChainID: `d043ab83d223f25f37e1876fe48a240d49d8e4b1daa2342064990a8036a8bb5b`
* Address prefix: `TST`
@@ -26,11 +26,11 @@ At the time of this writing, the connection information for Steemit's testnet is
## Running a Testnet Node
-First, let's build `steemd` specifically for testnet. Recommended specs:
+First, let's build `hived` specifically for testnet. Recommended specs:
* `Ubuntu Server 18.04 LTS`
* `100GB HDD`
-* `16GB RAM` (mostly needed for `steemd` build)
+* `16GB RAM` (mostly needed for `hived` build)
```bash
sudo apt-get update && sudo apt-get dist-upgrade
@@ -50,12 +50,12 @@ mkdir -p build
cd build
cmake \
-DCMAKE_BUILD_TYPE=Release \
- -DBUILD_STEEM_TESTNET=ON \
+ -DBUILD_HIVE_TESTNET=ON \
-DLOW_MEMORY_NODE=ON \
-DCHAINBASE_CHECK_LOCKING=ON \
-DCLEAR_VOTES=ON \
-DSKIP_BY_TX_ID=ON \
- -DSTEEM_LINT_LEVEL=OFF \
+ -DHIVE_LINT_LEVEL=OFF \
..
make -j$(nproc) install
cd
@@ -88,22 +88,22 @@ p2p-seed-node = testnet.steemitdev.com:2001
Then execute:
```bash
-steemd --data-dir=. --chain-id=d043ab83d223f25f37e1876fe48a240d49d8e4b1daa2342064990a8036a8bb5b
+hived --data-dir=. --chain-id=d043ab83d223f25f37e1876fe48a240d49d8e4b1daa2342064990a8036a8bb5b
```
Now let it sync, and you'll have a shiny new testnet seed node to play with.
## Custom Testnet
-In order to create a custom, isolated, testnet separate from the Steemit's we need to modify a few things mentioned in the previous section.
+In order to create a custom, isolated, testnet separate from the Hive's we need to modify a few things mentioned in the previous section.
In the file named `steem/libraries/protocol/include/steem/protocol/config.hpp`, we can see the first few lines dedicated to the Testnet section. The line starts with `#ifdef IS_TEST_NET`.
-Let's say we want to create a custom testnet with an initial supply of **1,000,000 STEEM**. We can change `STEEM_INIT_SUPPLY 1,000,000` and by changing `STEEM_CHAIN_ID_NAME "testnet"`, **testnet** to **mytestnet** we will automatically get a unique Chain ID for our testnet. The address prefix can be set to something like **MTN** and of course, we need to change the public and private keys to the genesis account. Note that the genesis account will receive the entire pre-mined supply of 1,000,000. That way, you can execute a setup script to fund any newly created accounts. Such a custom testnet will not have any additional hardware requirements to run.
+Let's say we want to create a custom testnet with an initial supply of **1,000,000 HIVE**. We can change `HIVE_INIT_SUPPLY 1,000,000` and by changing `HIVE_CHAIN_ID_NAME "testnet"`, **testnet** to **mytestnet** we will automatically get a unique Chain ID for our testnet. The address prefix can be set to something like **MTN** and of course, we need to change the public and private keys to the genesis account. Note that the genesis account will receive the entire pre-mined supply of 1,000,000. That way, you can execute a setup script to fund any newly created accounts. Such a custom testnet will not have any additional hardware requirements to run.
A minimum of 8GB RAM should be sufficient to run a custom testnet. Currently, Hive only has Linux and Mac compiling guides to build. A testnet can either be hosted locally, on a rented AWS, or dedicated bare metal servers so one can start testing functionality, explore different APIs, and start developing.
-One more crucial point to modify is to change the number of witnesses required to accept hardforks for a custom testnet, by default it is set to 17, we can change it to **1** `STEEM_HARDFORK_REQUIRED_WITNESSES 1` so that only one node instance would be sufficient and the network will be still functional and fast.
+One more crucial point to modify is to change the number of witnesses required to accept hardforks for a custom testnet, by default it is set to 17, we can change it to **1** `HIVE_HARDFORK_REQUIRED_WITNESSES 1` so that only one node instance would be sufficient and the network will be still functional and fast.
Another thing to note is that you can start a new chain with all previous hardforks already accepted, by changing the file named `steem/blob/master/libraries/chain/database.cpp` with the following function:
@@ -113,13 +113,13 @@ Another thing to note is that you can start a new chain with all previous hardfo
This would mean that 19 hardforks have been accepted by witnesses and the new chain will start with all previous forks included.
-After these changes, all we have to do is compile the source code and get the `steemd` executable. And once we fire up the custom testnet we can start testing and experimenting.
+After these changes, all we have to do is compile the source code and get the `hived` executable. And once we fire up the custom testnet we can start testing and experimenting.
-If you want to port some data from Hive main network you can use [Tinman](https://github.com/steemit/tinman), also developed by Steemit, to help with taking snapshots of the main network.
+If you want to port some data from Hive main network you can use [Tinman](https://github.com/steemit/tinman), also developed by Hive, to help with taking snapshots of the main network.
#### Custom live testnet
-An example of a custom testnet run by Hive community member [@almost-digital](https://steemit.com/@almost-digital). It doesn't have a snapshot of the main network
+An example of a custom testnet run by Hive community member [@almost-digital](https://hive.blog/@almost-digital). It doesn't have a snapshot of the main network
* ChainID: `79276aea5d4877d9a25892eaa01b0adf019d3e5cb12a97478df3298ccdd01673`
* Address prefix: `STX`
diff --git a/_resources/_piston.md b/_resources/_piston.md
index da73efb28678403bfb90d922e9cc265ad5f2b500..9eb79e62eec5deadc43346336e843bc2a2184fe4 100644
--- a/_resources/_piston.md
+++ b/_resources/_piston.md
@@ -3,7 +3,7 @@ title: PistonCLI
position: 4
---
-Piston is a command line tool to interact with the STEEM network. Piston is
+Piston is a command line tool to interact with the HIVE network. Piston is
written in Python and highly customizable for building steem tools and performing
wallet operations.
diff --git a/_resources/bluepaper.md b/_resources/bluepaper.md
index c68d7aaf5213364c4120e3ecef2f585f3b6f56d4..6df7cc8b6eee36264768776c4a1c8f65ee805ae1 100644
--- a/_resources/bluepaper.md
+++ b/_resources/bluepaper.md
@@ -3,6 +3,6 @@ title: Bluepaper
position: 2
---
-The Steem Bluepaper describes how the Steem blockchain works, and provides an overview of the key features.
+The Hive Bluepaper describes how the Hive blockchain works, and provides an overview of the key features.
[https://steem.com/steem-bluepaper.pdf](https://steem.com/steem-bluepaper.pdf)
diff --git a/_resources/client_libs.md b/_resources/client_libs.md
index 1a2ee994789a53e02db8a7527e826c5f1d6693a1..0a78b24818dae60e97a4dca2b2638ac3521c4ca8 100644
--- a/_resources/client_libs.md
+++ b/_resources/client_libs.md
@@ -15,7 +15,7 @@ Pure JavaScript Hive crypto library for node.js and browsers. Can be used to con
---
-**Steem-TX-JS** - [https://github.com/mahdiyari/steem-tx-js](https://github.com/mahdiyari/steem-tx-js)
+**Hive-TX-JS** - [https://github.com/mahdiyari/steem-tx-js](https://github.com/mahdiyari/steem-tx-js)
Lightweight JavaScript library for creating and signing transactions. Works with frameworks like Nativescript. This library is a solution to such cases when other libraries are not working. And also an alternative for *only* creating, signing, and broadcasting transactions.
@@ -35,22 +35,22 @@ A python library to interact with the Hive blockchain. It includes the CLI tool
**PHP Hive** - [https://github.com/lukestokes/php-steem-tools](https://github.com/lukestokes/php-steem-tools)
-Various tools and scripts written in PHP for exploring the STEEM blockchain.
+Various tools and scripts written in PHP for exploring the HIVE blockchain.
---
-
+Client library for Hive blockchain built with Rust -->
diff --git a/_resources/developeradvocate.md b/_resources/developeradvocate.md
index b50ff17c6d909bd61f7a0f742083a194d2a1aac4..7069d0bacb0dec7c6131634e43af9a6cbd2e564e 100644
--- a/_resources/developeradvocate.md
+++ b/_resources/developeradvocate.md
@@ -5,9 +5,9 @@ position: 6
-
+
#### API
diff --git a/_services/hive.blog.md b/_services/hive.blog.md
index ed10df5ff54007f350c39a5c283222de0ae2e32f..28695646a194e60b6e0c4a95fd776dc35a0c146e 100644
--- a/_services/hive.blog.md
+++ b/_services/hive.blog.md
@@ -61,19 +61,19 @@ User object
"last_vote_time":"2018-06-21T19:42:33",
"balance":"24.519 HIVE",
"savings_balance":"0.000 HIVE",
- "sbd_balance":"36.736 HBD",
- "sbd_seconds":"11732264931",
- "sbd_seconds_last_update":"2018-06-21T19:35:00",
- "sbd_last_interest_payment":"2018-06-15T14:05:03",
- "savings_sbd_balance":"0.000 HBD",
- "savings_sbd_seconds":"0",
- "savings_sbd_seconds_last_update":"1970-01-01T00:00:00",
- "savings_sbd_last_interest_payment":"1970-01-01T00:00:00",
+ "hbd_balance":"36.736 HBD",
+ "hbd_seconds":"11732264931",
+ "hbd_seconds_last_update":"2018-06-21T19:35:00",
+ "hbd_last_interest_payment":"2018-06-15T14:05:03",
+ "savings_hbd_balance":"0.000 HBD",
+ "savings_hbd_seconds":"0",
+ "savings_hbd_seconds_last_update":"1970-01-01T00:00:00",
+ "savings_hbd_last_interest_payment":"1970-01-01T00:00:00",
"savings_withdraw_requests":0,
- "reward_sbd_balance":"0.000 HBD",
- "reward_steem_balance":"0.000 HIVE",
+ "reward_hbd_balance":"0.000 HBD",
+ "reward_hive_balance":"0.000 HIVE",
"reward_vesting_balance":"481.354811 VESTS",
- "reward_vesting_steem":"0.237 HIVE",
+ "reward_vesting_hive":"0.237 HIVE",
"vesting_shares":"128367480.795804 VESTS",
"delegated_vesting_shares":"0.000000 VESTS",
"received_vesting_shares":"17069919.621493 VESTS",
@@ -166,7 +166,7 @@ Post object
"root_author": "curie",
"root_permlink": "the-daily-curie-12-13-feb-2017",
"max_accepted_payout": "1000000.000 HBD",
- "percent_steem_dollars": 0,
+ "percent_hbd": 0,
"allow_replies": true,
"allow_votes": true,
"allow_curation_rewards": true,
diff --git a/_services/imageHoster.md b/_services/imageHoster.md
index 38127c0f48eb9094eb72afe361b9f5ec5c1ebba1..be4aa80bd65de33e96e9290bfeb646bd04694ddd 100644
--- a/_services/imageHoster.md
+++ b/_services/imageHoster.md
@@ -10,7 +10,7 @@ The purpose of this tool is to provide a way to host and proxy images used by [c
Using ImageHoster will help limit access to IP addresses of the general user. It will also strip [image metadata](https://en.wikipedia.org/wiki/Exif) related to the author's geographical location. It also helps to verify that the original author uploaded the image they intended.
-The ability to upload images on steemit.com was originally added in January, 2017. Please note that this tool **does not** store any image data on the blockchain.
+The ability to upload images on hive.blog was originally added in January, 2017. Please note that this tool **does not** store any image data on the blockchain.
Detaied information on Imagehoster can be found in its [repository](https://gitlab.syncad.com/hive/imagehoster/-/blob/master/README.md#imagehoster)
diff --git a/_services/jussi.md b/_services/jussi.md
index 87dab0940b71ebe688583180f1dad7932232064a..e63e0e83264c9edddc94438c9bbc70bfd08dc1a8 100644
--- a/_services/jussi.md
+++ b/_services/jussi.md
@@ -4,13 +4,13 @@ position: 3
description: A reverse proxy that forwards json-rpc requests.
---
-Jussi is a custom-built caching layer for use with `steemd` and other various services (such as [SBDS]({{ '/services/#services-sbds' | relative_url }})).
+Jussi is a custom-built caching layer for use with `hived` and other various services (such as [HBDS]({{ '/services/#services-hbds' | relative_url }})).
The purpose of this document is to help developers and node operators set up their own jussi node within a docker container.
### Intro
-Jussi is a reverse proxy that is situation between the API client and the `steemd` server. It allows node operators to route an API call to nodes that are optimized for the particular call, as if they are all hosted from the same place.
+Jussi is a reverse proxy that is situation between the API client and the `hived` server. It allows node operators to route an API call to nodes that are optimized for the particular call, as if they are all hosted from the same place.
### Sections
@@ -43,7 +43,7 @@ docker run -itp 9000:8080 "$USER/jussi:$(git rev-parse --abbrev-ref HEAD)"
curl -s --data '{"jsonrpc":"2.0", "method":"condenser_api.get_block", "params":[8675309], "id":1}' http://localhost:9000
```
-See: [Running Condenser, Jussi and a new service locally + adding feature flags to Condenser](https://steemit.com/steemdev/@maitland/running-condenser-jussi-and-a-new-service-locally-adding-feature-flags-to-condenser)
+See: [Running Condenser, Jussi and a new service locally + adding feature flags to Condenser](https://hive.blog/hivedev/@maitland/running-condenser-jussi-and-a-new-service-locally-adding-feature-flags-to-condenser)
---
@@ -56,40 +56,40 @@ The default `DEV_config.json` is:
"limits":{"blacklist_accounts":["non-steemit"]},
"upstreams":[
{
- "name":"steemd",
+ "name":"hived",
"translate_to_appbase":false,
- "urls":[["steemd", "https://steemd.steemitdev.com"]],
+ "urls":[["hived", "https://hived.steemitdev.com"]],
"ttls":[
- ["steemd", 3],
- ["steemd.login_api", -1],
- ["steemd.network_broadcast_api", -1],
- ["steemd.follow_api", 10],
- ["steemd.market_history_api", 1],
- ["steemd.database_api", 3],
- ["steemd.database_api.get_block", -2],
- ["steemd.database_api.get_block_header", -2],
- ["steemd.database_api.get_content", 1],
- ["steemd.database_api.get_state", 1],
- ["steemd.database_api.get_state.params=['/trending']", 30],
- ["steemd.database_api.get_state.params=['trending']", 30],
- ["steemd.database_api.get_state.params=['/hot']", 30],
- ["steemd.database_api.get_state.params=['/welcome']", 30],
- ["steemd.database_api.get_state.params=['/promoted']", 30],
- ["steemd.database_api.get_state.params=['/created']", 10],
- ["steemd.database_api.get_dynamic_global_properties", 1]
+ ["hived", 3],
+ ["hived.login_api", -1],
+ ["hived.network_broadcast_api", -1],
+ ["hived.follow_api", 10],
+ ["hived.market_history_api", 1],
+ ["hived.database_api", 3],
+ ["hived.database_api.get_block", -2],
+ ["hived.database_api.get_block_header", -2],
+ ["hived.database_api.get_content", 1],
+ ["hived.database_api.get_state", 1],
+ ["hived.database_api.get_state.params=['/trending']", 30],
+ ["hived.database_api.get_state.params=['trending']", 30],
+ ["hived.database_api.get_state.params=['/hot']", 30],
+ ["hived.database_api.get_state.params=['/welcome']", 30],
+ ["hived.database_api.get_state.params=['/promoted']", 30],
+ ["hived.database_api.get_state.params=['/created']", 10],
+ ["hived.database_api.get_dynamic_global_properties", 1]
],
"timeouts":[
- ["steemd", 5],
- ["steemd.network_broadcast_api", 0]
+ ["hived", 5],
+ ["hived.network_broadcast_api", 0]
],
"retries": [
- ["steemd", 3],
- ["steemd.network_broadcast_api", 0]
+ ["hived", 3],
+ ["hived.network_broadcast_api", 0]
]
},
{
"name":"appbase",
- "urls":[["appbase", "https://steemd.steemitdev.com"]],
+ "urls":[["appbase", "https://hived.steemitdev.com"]],
"ttls":[
["appbase", -2],
["appbase.block_api", -2],
@@ -136,25 +136,25 @@ Jussi can be configured with various `TTL` (Time To Live) schemes. A `TTL` is an
| Upstream | API | Method | Parameters | TTL (seconds) |
|------------|-------------------------|---------------------------------|--------------------|---------------|
-| `steemd` | `login_api` | _all_ | _all_ | -1 |
-| `steemd` | `network_broadcast_api` | _all_ | _all_ | -1 |
-| `steemd` | `follow_api` | _all_ | _all_ | 10 |
-| `steemd` | `market_history_api` | _all_ | _all_ | 1 |
-| `steemd` | `database_api` | _all_ | _all_ | 3 |
-| `steemd` | `database_api` | `get_block` | _all_ | -2 |
-| `steemd` | `database_api` | `get_block_header` | _all_ | -2 |
-| `steemd` | `database_api` | `get_content` | _all_ | 1 |
-| `steemd` | `database_api` | `get_state` | _all_ | 1 |
-| `steemd` | `database_api` | `get_state` | `'/trending'` | 30 |
-| `steemd` | `database_api` | `get_state` | `'trending'` | 30 |
-| `steemd` | `database_api` | `get_state` | `'/hot'` | 30 |
-| `steemd` | `database_api` | `get_state` | `'/welcome'` | 30 |
-| `steemd` | `database_api` | `get_state` | `'/promoted'` | 30 |
-| `steemd` | `database_api` | `get_state` | `'/created'` | 10 |
-| `steemd` | `database_api` | `get_dynamic_global_properties` | _all_ | 1 |
+| `hived` | `login_api` | _all_ | _all_ | -1 |
+| `hived` | `network_broadcast_api` | _all_ | _all_ | -1 |
+| `hived` | `follow_api` | _all_ | _all_ | 10 |
+| `hived` | `market_history_api` | _all_ | _all_ | 1 |
+| `hived` | `database_api` | _all_ | _all_ | 3 |
+| `hived` | `database_api` | `get_block` | _all_ | -2 |
+| `hived` | `database_api` | `get_block_header` | _all_ | -2 |
+| `hived` | `database_api` | `get_content` | _all_ | 1 |
+| `hived` | `database_api` | `get_state` | _all_ | 1 |
+| `hived` | `database_api` | `get_state` | `'/trending'` | 30 |
+| `hived` | `database_api` | `get_state` | `'trending'` | 30 |
+| `hived` | `database_api` | `get_state` | `'/hot'` | 30 |
+| `hived` | `database_api` | `get_state` | `'/welcome'` | 30 |
+| `hived` | `database_api` | `get_state` | `'/promoted'` | 30 |
+| `hived` | `database_api` | `get_state` | `'/created'` | 10 |
+| `hived` | `database_api` | `get_dynamic_global_properties` | _all_ | 1 |
| `overseer` | _all_ | _all_ | _all_ | 5 |
| `conveyor` | _all_ | _all_ | _all_ | -1 |
-| `sbds` | _all_ | _all_ | _all_ | 3 |
+| `hbds` | _all_ | _all_ | _all_ | 3 |
| `hivemind` | _all_ | _all_ | _all_ | 3 |
| `yo` | _all_ | _all_ | _all_ | 3 |
@@ -200,7 +200,7 @@ In these examples, the methods `get_account_history` and `get_ops_in_block` rout
Adding a `retries` element defines the number of retry attempts, where `0` (or absent) means no retry. The maximum number of retries is `3`.
-Note that retrying broadcast methods is not recommended, which is why the example explicitly sets `steemd.network_broadcast_api` to `0`.
+Note that retrying broadcast methods is not recommended, which is why the example explicitly sets `hived.network_broadcast_api` to `0`.
#### json-rpc batch
@@ -209,7 +209,7 @@ Normally, a request is made with a JSON Object (`{}`). But jussi also supports
For example, this would be a typical, non-batched JSON Object request that asks for a single block:
```bash
-curl -s --data '{"jsonrpc":"2.0", "method":"condenser_api.get_block", "params":[1], "id":1}' https://api.steemit.com
+curl -s --data '{"jsonrpc":"2.0", "method":"condenser_api.get_block", "params":[1], "id":1}' https://api.hive.blog
```
```json
@@ -240,7 +240,7 @@ curl -s --data '{"jsonrpc":"2.0", "method":"condenser_api.get_block", "params":[
To request more than one block using the batch construct, wrap each call in a JSON Array, that asks for two blocks in one request:
```bash
-curl -s --data '[{"jsonrpc":"2.0", "method":"condenser_api.get_block", "params":[1], "id":1},{"jsonrpc":"2.0", "method":"condenser_api.get_block", "params":[2], "id":2}]' https://api.steemit.com
+curl -s --data '[{"jsonrpc":"2.0", "method":"condenser_api.get_block", "params":[1], "id":1},{"jsonrpc":"2.0", "method":"condenser_api.get_block", "params":[2], "id":2}]' https://api.hive.blog
```
```json
@@ -295,7 +295,7 @@ curl -s --data '[{"jsonrpc":"2.0", "method":"condenser_api.get_block", "params":
Error responses are returned in the JSON Array response as well. Notice the `"WRONG"` parameter in the second element. The first block is returned as expected, the second one generates an error.
```bash
-curl -s --data '[{"jsonrpc":"2.0", "method":"condenser_api.get_block", "params":[1], "id":1},{"jsonrpc":"2.0", "method":"condenser_api.get_block", "params":["WRONG"], "id":2}]' https://api.steemit.com
+curl -s --data '[{"jsonrpc":"2.0", "method":"condenser_api.get_block", "params":[1], "id":1},{"jsonrpc":"2.0", "method":"condenser_api.get_block", "params":["WRONG"], "id":2}]' https://api.hive.blog
```
```json
diff --git a/_testnet/index.md b/_testnet/index.md
index 211de7a359b9f998e4ed92fc6949e79959d34037..b5a71297d776d7d35d12ca14ddcea44935ff95e5 100644
--- a/_testnet/index.md
+++ b/_testnet/index.md
@@ -1,15 +1,15 @@
---
-title: Steem Testnet
+title: Hive Testnet
position: 3
layout: full
---
-Steem blockchain software is written in C++ and in order to modify the source code you need some understanding of the C++ programming language. Each Steem node runs an instance of this software, so in order to test your changes, you will need to know how to install dependencies which can be found in the [Steem repo](https://github.com/steemit/steem/blob/master/doc/building.md). This also means that some knowledge of System administration is also required. There are multiple advantages of running a testnet, you can test your scripts or applications on a testnet without extra spam on the live network, which allows much more flexibility to try new things.
-Having access to a testnet also helps you to work on new features and possibly submit new or improved pull requests to official the Steem GitHub repository.
+Hive blockchain software is written in C++ and in order to modify the source code you need some understanding of the C++ programming language. Each Hive node runs an instance of this software, so in order to test your changes, you will need to know how to install dependencies which can be found in the [Hive repo](https://github.com/steemit/steem/blob/master/doc/building.md). This also means that some knowledge of System administration is also required. There are multiple advantages of running a testnet, you can test your scripts or applications on a testnet without extra spam on the live network, which allows much more flexibility to try new things.
+Having access to a testnet also helps you to work on new features and possibly submit new or improved pull requests to official the Hive GitHub repository.
## Running Testnet
-By following official [build steps](https://github.com/steemit/steem/blob/master/doc/building.md#build_steem_testnetoffon) and enabling the `BUILD_STEEM_TESTNET` flag during compilation, you should be able to run the Steem Testnet locally on your workstation and join the development testnet. Docker can also be used to get started quickly. Compilation generates the `steemd` executable which is the main daemon for the Steem network. Additional `cli_wallet` can also be compiled to test/connect to an instance of `steemd` and request some data from the network, but it is not necessary to run a node.
+By following official [build steps](https://github.com/steemit/steem/blob/master/doc/building.md#build_hive_testnetoffon) and enabling the `BUILD_HIVE_TESTNET` flag during compilation, you should be able to run the Hive Testnet locally on your workstation and join the development testnet. Docker can also be used to get started quickly. Compilation generates the `hived` executable which is the main daemon for the Hive network. Additional `cli_wallet` can also be compiled to test/connect to an instance of `hived` and request some data from the network, but it is not necessary to run a node.
The development testnet requires a certain minimum set of hardware requirements, depending on the type of compile flags that have been enabled. Because it is a mirror of the live network, private keys are the same for accounts up to the point of the snapshot timestamp of the testnet.
@@ -17,13 +17,13 @@ Joining/Running the development testnet requires around 10 GB for block log on a
Testnet has the following parameters by default (as of this writing):
-* Initial supply (250 billion) - `STEEM_INIT_SUPPLY 250,000,000,000`
+* Initial supply (250 billion) - `HIVE_INIT_SUPPLY 250,000,000,000`
* Max number of blocks to be produced - `TESTNET_BLOCK_LIMIT 3,000,000`
-* Address prefix, prefix on public addresses - `STEEM_ADDRESS_PREFIX "TST"`
-* Chain id name, used for chain id - `STEEM_CHAIN_ID_NAME "testnet"`
-* Chain id, unique id hash of chain - `STEEM_CHAIN_ID (fc::sha256::hash(STEEM_CHAIN_ID_NAME))`
-* Public key of genesis account - `STEEM_INIT_PUBLIC_KEY_STR `
-* Account creation fee - `STEEM_MIN_ACCOUNT_CREATION_FEE 0`
+* Address prefix, prefix on public addresses - `HIVE_ADDRESS_PREFIX "TST"`
+* Chain id name, used for chain id - `HIVE_CHAIN_ID_NAME "testnet"`
+* Chain id, unique id hash of chain - `HIVE_CHAIN_ID (fc::sha256::hash(HIVE_CHAIN_ID_NAME))`
+* Public key of genesis account - `HIVE_INIT_PUBLIC_KEY_STR `
+* Account creation fee - `HIVE_MIN_ACCOUNT_CREATION_FEE 0`
There are a number of other subtle changes that we don't need to focus on right now.
@@ -41,11 +41,11 @@ In order to create a custom testnet, separate from the development one, we need
In the file named `steem/libraries/protocol/include/steem/protocol/config.hpp`, we can see the first few lines dedicated to the Testnet section. The line starts with `#ifdef IS_TEST_NET`.
-Let's say we want to create a custom testnet with an initial supply of **1,000,000 STEEM**. We can change `STEEM_INIT_SUPPLY 1,000,000` and by changing `STEEM_CHAIN_ID_NAME "testnet"`, **testnet** to **mytestnet** we will automatically get a unique Chain ID for our testnet. The address prefix can be set to something like **MTN** and of course, we need to change the public and private keys to the genesis account. Note that the genesis account will receive the entire pre-mined supply of 1,000,000. That way, you can execute a setup script to fund any newly created accounts. Such a custom testnet will not have any additional hardware requirements to run.
+Let's say we want to create a custom testnet with an initial supply of **1,000,000 HIVE**. We can change `HIVE_INIT_SUPPLY 1,000,000` and by changing `HIVE_CHAIN_ID_NAME "testnet"`, **testnet** to **mytestnet** we will automatically get a unique Chain ID for our testnet. The address prefix can be set to something like **MTN** and of course, we need to change the public and private keys to the genesis account. Note that the genesis account will receive the entire pre-mined supply of 1,000,000. That way, you can execute a setup script to fund any newly created accounts. Such a custom testnet will not have any additional hardware requirements to run.
-A minimum of 8GB RAM should be sufficient to run a custom testnet. Currently, Steem only has Linux and Mac compiling guides to build. A testnet can either be hosted locally, on a rented AWS, or dedicated bare metal servers so one can start testing functionality, explore different APIs, and start developing.
+A minimum of 8GB RAM should be sufficient to run a custom testnet. Currently, Hive only has Linux and Mac compiling guides to build. A testnet can either be hosted locally, on a rented AWS, or dedicated bare metal servers so one can start testing functionality, explore different APIs, and start developing.
-One more crucial point to modify is to change the number of witnesses required to accept hardforks for a custom testnet, by default it is set to 17, we can change it to **1** `STEEM_HARDFORK_REQUIRED_WITNESSES 1` so that only one node instance would be sufficient and the network will be still functional and fast.
+One more crucial point to modify is to change the number of witnesses required to accept hardforks for a custom testnet, by default it is set to 17, we can change it to **1** `HIVE_HARDFORK_REQUIRED_WITNESSES 1` so that only one node instance would be sufficient and the network will be still functional and fast.
Another thing to note is that you can start a new chain with all previous hardforks already accepted, by changing the file named `steem/blob/master/libraries/chain/database.cpp` with the following function:
@@ -55,9 +55,9 @@ Another thing to note is that you can start a new chain with all previous hardfo
This would mean that 19 hardforks have been accepted by witnesses and the new chain will start with all previous forks included.
-After these changes, all we have to do is compile the source code and get the `steemd` executable. And once we fire up the custom testnet we can start testing and experimenting.
+After these changes, all we have to do is compile the source code and get the `hived` executable. And once we fire up the custom testnet we can start testing and experimenting.
-If you want to port some data from Steem main network you can use [Tinman](https://github.com/steemit/tinman), also developed by Steemit, to help with taking snapshots of the main network.
+If you want to port some data from Hive main network you can use [Tinman](https://github.com/steemit/tinman), also developed by Hive, to help with taking snapshots of the main network.
#### Custom live testnet
diff --git a/_tutorials-javascript/account_reputation.md b/_tutorials-javascript/account_reputation.md
index 3e611000366672bdf5e4919f735242b1e2cb3479..ece2d21d6f1e202f726e0617b71c09b02f70bf65 100644
--- a/_tutorials-javascript/account_reputation.md
+++ b/_tutorials-javascript/account_reputation.md
@@ -10,11 +10,11 @@ canonical_url: account_reputation.html
-This tutorial runs on the main Steem blockchain. And accounts queried are real users with reputation.
+This tutorial runs on the main Hive blockchain. And accounts queried are real users with reputation.
## Intro
-This tutorial will show the method of capturing a queried tag name and matching it to the Steem. We are using the `call` function provided by the `dsteem` library to pull accounts from the Steem blockchain. A simple HTML interface is used to both capture the string query as well as display the completed search.
+This tutorial will show the method of capturing a queried tag name and matching it to the Hive. We are using the `call` function provided by the `dsteem` library to pull accounts from the Hive blockchain. A simple HTML interface is used to both capture the string query as well as display the completed search.
## steps
@@ -33,9 +33,9 @@ let opts = {};
//connect to production server
opts.addressPrefix = 'STM';
opts.chainId =
- '0000000000000000000000000000000000000000000000000000000000000000';
+ 'beeab0de00000000000000000000000000000000000000000000000000000000';
//connect to server which is connected to the network/production
-const client = new dsteem.Client('https://api.steemit.com');
+const client = new dsteem.Client('https://api.hive.blog');
```
#### 2. Search account
@@ -56,7 +56,7 @@ In order to get accounts, we run the search with the `search field` and `maximum
const _accounts = await client.database.call('lookup_accounts',[accSearch, max]);
```
-The result of the search is an array of accounts. After that we use `get_accounts` to pull account data from Steem.
+The result of the search is an array of accounts. After that we use `get_accounts` to pull account data from Hive.
```javascript
const acc = await client.database.call('get_accounts',[_accounts]);
diff --git a/_tutorials-javascript/blog_feed.md b/_tutorials-javascript/blog_feed.md
index e3acfb0a7fafa60fdbffc0edf5d0d4c0932d45ff..4376dc4666f55349ea866bfb60cc5a359473a73c 100644
--- a/_tutorials-javascript/blog_feed.md
+++ b/_tutorials-javascript/blog_feed.md
@@ -30,7 +30,7 @@ In first couple lines we require package and define connection server:
```javascript
const { Client } = require("@hivechain/dhive");
-const client = new Client('https://api.openhive.network');
+const client = new Client('https://api.hive.blog');
```
#### 2. Query format
@@ -138,7 +138,7 @@ The result returned form the service is a `JSON` object with the following prope
"parent_author": "",
"parent_permlink": "hiveblockchain",
"pending_payout_value": "0.000 HBD",
- "percent_steem_dollars": 10000,
+ "percent_hbd": 10000,
"permlink": "huobi-global-official-hive-listing-announcement-giveaways-ama-chat-transcripts",
"promoted": "0.000 HBD",
"reblogged_by": [],
diff --git a/_tutorials-javascript/claim_rewards.md b/_tutorials-javascript/claim_rewards.md
index 485cb7ed5b51abac894067c4d7bce10c0ac7c2f4..a883c15dff9651a7a371e2b54d1dd66747c35419 100644
--- a/_tutorials-javascript/claim_rewards.md
+++ b/_tutorials-javascript/claim_rewards.md
@@ -1,7 +1,7 @@
---
title: 'JS: Claim Rewards'
position: 23
-description: "_Learn how to claim rewards from unclaimed reward balance using Steemconnect as well as client signing method._"
+description: "_Learn how to claim rewards from unclaimed reward balance using Hiveconnect as well as client signing method._"
layout: full
canonical_url: claim_rewards.html
---
@@ -10,18 +10,18 @@ canonical_url: claim_rewards.html
-This tutorial runs on the main Steem blockchain. And accounts queried are real users with unclaimed balances.
+This tutorial runs on the main Hive blockchain. And accounts queried are real users with unclaimed balances.
## Intro
-This tutorial will show few functions such as querying account by name and getting unclaimed rewards. We are using the `call` function provided by the `dsteem` library to pull accounts from the Steem blockchain. A simple HTML interface is used to capture the account and its unclaimed balance as well as allowing interactively claim rewards.
+This tutorial will show few functions such as querying account by name and getting unclaimed rewards. We are using the `call` function provided by the `dsteem` library to pull accounts from the Hive blockchain. A simple HTML interface is used to capture the account and its unclaimed balance as well as allowing interactively claim rewards.
## Steps
1. [**App setup**](#app-setup) Setup `dsteem` to use the proper connection and network.
2. [**Search account**](#search-account) Get account details after input has account name
3. [**Fill form**](#fill-form) Fill form with account reward balances
-4. [**Claim reward**](#claim-reward) Claim reward with Steemconnect or Client signing options
+4. [**Claim reward**](#claim-reward) Claim reward with Hiveconnect or Client signing options
#### 1. App setup
@@ -33,9 +33,9 @@ let opts = {};
//connect to production server
opts.addressPrefix = 'STM';
opts.chainId =
- '0000000000000000000000000000000000000000000000000000000000000000';
+ 'beeab0de00000000000000000000000000000000000000000000000000000000';
//connect to server which is connected to the network/production
-const client = new dsteem.Client('https://api.steemit.com');
+const client = new dsteem.Client('https://api.hive.blog');
```
#### 2. Search account
@@ -54,20 +54,20 @@ After we fetched account data, we will fill form with reward balance and show cu
```javascript
const name = _accounts[0].name;
-const reward_steem = _accounts[0].reward_steem_balance.split(' ')[0];
-const reward_sbd = _accounts[0].reward_sbd_balance.split(' ')[0];
-const reward_sp = _accounts[0].reward_vesting_steem.split(' ')[0];
+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_steem} STEEM, ${reward_sbd} SBD, ${reward_sp} SP = ${reward_vests} VESTS\n\nHello Steemians! If you’d like to meet Team Steemit live-in-person, or are just interested in attending what promises to be a great blockchain conference, join us at TokenFest in San Francisco from March 15th to 16th. \n\nSteemit CEO, Ned Scott, will be participating in a fireside chat alongside Steemit’s CTO, Harry Schmidt, as well as the creator of Utopian.io, Diego Pucci. Steemit will also be hosting the opening party on Thursday night and we’d certainly love to meet as many of you as possible IRL, so head on over to https://tokenfest.adria.digital/ and get your tickets while you can. \n\n*Team Steemit*",
+ "\n\nHello Hiveians! If you’d like to meet Team Hive live-in-person, or are just interested in attending what promises to be a great blockchain conference, join us at TokenFest in San Francisco from March 15th to 16th. \n\nHive CEO, Ned Scott, will be participating in a fireside chat alongside Hive’s CTO, Harry Schmidt, as well as the creator of Utopian.io, Diego Pucci. Hive will also be hosting the opening party on Thursday night and we’d certainly love to meet as many of you as possible IRL, so head on over to https://tokenfest.adria.digital/ and get your tickets while you can. \n\n*Team Hive*",
"json_metadata":
"{\"tags\":[\"steemit\",\"tokenfest\",\"conference\"],\"image\":[\"https://i.imgur.com/fOScDIW.png\"],\"links\":[\"https://tokenfest.adria.digital\",\"https://tokenfest.adria.digital/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"last_update": "2018-03-07T23:22:54",
@@ -111,21 +111,21 @@ The example of result returned from the service is a `JSON` object with the foll
"max_cashout_time": "1969-12-31T23:59:59",
"total_vote_weight": 3462435,
"reward_weight": 10000,
- "total_payout_value": "0.000 SBD",
- "curator_payout_value": "0.000 SBD",
+ "total_payout_value": "0.000 HBD",
+ "curator_payout_value": "0.000 HBD",
"author_rewards": 0,
"net_votes": 77,
"root_comment": 37338948,
- "max_accepted_payout": "0.000 SBD",
- "percent_steem_dollars": 10000,
+ "max_accepted_payout": "0.000 HBD",
+ "percent_hbd": 10000,
"allow_replies": true,
"allow_votes": true,
"allow_curation_rewards": true,
"beneficiaries": [],
"url": "/steemit/@steemitblog/join-team-steemit-at-tokenfest",
- "root_title": "Join Team Steemit at TokenFest!",
- "pending_payout_value": "46.436 SBD",
- "total_pending_payout_value": "0.000 STEEM",
+ "root_title": "Join Team Hive at TokenFest!",
+ "pending_payout_value": "46.436 HBD",
+ "total_pending_payout_value": "0.000 HIVE",
"active_votes": [
{
"voter": "steemitblog",
@@ -146,7 +146,7 @@ The example of result returned from the service is a `JSON` object with the foll
],
"replies": [],
"author_reputation": "128210130644387",
- "promoted": "0.000 SBD",
+ "promoted": "0.000 HBD",
"body_length": 754,
"reblogged_by": []
}
diff --git a/_tutorials-python/get_posts.md b/_tutorials-python/get_posts.md
index 72889cbd55e2018c2dce411db26c77d2644ec420..3abb4e78da4ebd47f4a78d6e73eb9f980c4e8bdb 100644
--- a/_tutorials-python/get_posts.md
+++ b/_tutorials-python/get_posts.md
@@ -10,11 +10,11 @@ canonical_url: get_posts.html
-This tutorial will explain and show you how to access the **Steem** blockchain using the [steem-python](https://github.com/steemit/steem-python) library to fetch list of posts filtered by a _filter_ and _tag_
+This tutorial will explain and show you how to access the **Hive** blockchain using the [steem-python](https://github.com/steemit/steem-python) library to fetch list of posts filtered by a _filter_ and _tag_
## Intro
-In Steem there are built-in filters `trending`, `hot`, `created`, `active`, `promoted` etc. which helps us to get list of posts. `get_discussions_by_trending(query)`, `get_discussions_by_hot(query)`, `get_discussions_by_created(query)`, etc. functions are built-in in official library `steem-python` that we are going to use throughout all Python tutorials.
+In Hive there are built-in filters `trending`, `hot`, `created`, `active`, `promoted` etc. which helps us to get list of posts. `get_discussions_by_trending(query)`, `get_discussions_by_hot(query)`, `get_discussions_by_created(query)`, etc. functions are built-in in official library `steem-python` that we are going to use throughout all Python tutorials.
## Steps
@@ -28,15 +28,15 @@ In Steem there are built-in filters `trending`, `hot`, `created`, `active`, `pro
In this tutorial we use 3 packages, `pick` - helps us to select filter interactively. `steem` - steem-python library, interaction with Blockchain. `pprint` - print results in better format.
-First we import all three library and initialize Steem class
+First we import all three library and initialize Hive class
```python
import pprint
from pick import pick
- # initialize Steem class
- from steem import Steem
+ # initialize Hive class
+ from steem import Hive
- s = Steem()
+ s = Hive()
```
#### 2. Filters list
@@ -55,7 +55,7 @@ This will show us list of filters to select in terminal/command prompt. And afte
#### 3. Query details
-Next we will form a query. In Steem,
+Next we will form a query. In Hive,
* You can add a tag to filter the posts that you receive from the server
* You can also limit the amount of results you would like to receive from the query
@@ -97,9 +97,9 @@ The example of result returned from the service is a `JSON` object with the foll
"category": "steemit",
"parent_author": "",
"parent_permlink": "steemit",
- "title": "Join Team Steemit at TokenFest!",
+ "title": "Join Team Hive at TokenFest!",
"body":
- "\n\nHello Steemians! If you’d like to meet Team Steemit live-in-person, or are just interested in attending what promises to be a great blockchain conference, join us at TokenFest in San Francisco from March 15th to 16th. \n\nSteemit CEO, Ned Scott, will be participating in a fireside chat alongside Steemit’s CTO, Harry Schmidt, as well as the creator of Utopian.io, Diego Pucci. Steemit will also be hosting the opening party on Thursday night and we’d certainly love to meet as many of you as possible IRL, so head on over to https://tokenfest.adria.digital/ and get your tickets while you can. \n\n*Team Steemit*",
+ "\n\nHello Hiveians! If you’d like to meet Team Hive live-in-person, or are just interested in attending what promises to be a great blockchain conference, join us at TokenFest in San Francisco from March 15th to 16th. \n\nHive CEO, Ned Scott, will be participating in a fireside chat alongside Hive’s CTO, Harry Schmidt, as well as the creator of Utopian.io, Diego Pucci. Hive will also be hosting the opening party on Thursday night and we’d certainly love to meet as many of you as possible IRL, so head on over to https://tokenfest.adria.digital/ and get your tickets while you can. \n\n*Team Hive*",
"json_metadata":
"{\"tags\":[\"steemit\",\"tokenfest\",\"conference\"],\"image\":[\"https://i.imgur.com/fOScDIW.png\"],\"links\":[\"https://tokenfest.adria.digital\",\"https://tokenfest.adria.digital/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"last_update": "2018-03-07T23:22:54",
@@ -116,21 +116,21 @@ The example of result returned from the service is a `JSON` object with the foll
"max_cashout_time": "1969-12-31T23:59:59",
"total_vote_weight": 3462435,
"reward_weight": 10000,
- "total_payout_value": "0.000 SBD",
- "curator_payout_value": "0.000 SBD",
+ "total_payout_value": "0.000 HBD",
+ "curator_payout_value": "0.000 HBD",
"author_rewards": 0,
"net_votes": 77,
"root_comment": 37338948,
- "max_accepted_payout": "0.000 SBD",
- "percent_steem_dollars": 10000,
+ "max_accepted_payout": "0.000 HBD",
+ "percent_hbd": 10000,
"allow_replies": true,
"allow_votes": true,
"allow_curation_rewards": true,
"beneficiaries": [],
"url": "/steemit/@steemitblog/join-team-steemit-at-tokenfest",
- "root_title": "Join Team Steemit at TokenFest!",
- "pending_payout_value": "46.436 SBD",
- "total_pending_payout_value": "0.000 STEEM",
+ "root_title": "Join Team Hive at TokenFest!",
+ "pending_payout_value": "46.436 HBD",
+ "total_pending_payout_value": "0.000 HIVE",
"active_votes": [
{
"voter": "steemitblog",
@@ -151,7 +151,7 @@ The example of result returned from the service is a `JSON` object with the foll
],
"replies": [],
"author_reputation": "128210130644387",
- "promoted": "0.000 SBD",
+ "promoted": "0.000 HBD",
"body_length": 754,
"reblogged_by": []
},
diff --git a/_tutorials-python/get_voters_list_on_post.md b/_tutorials-python/get_voters_list_on_post.md
index 1a45ef24836824676546af8944a1d29a1bf5fc48..03fdcda349b5a797a7ec38e661ecd6e63d2c04d3 100644
--- a/_tutorials-python/get_voters_list_on_post.md
+++ b/_tutorials-python/get_voters_list_on_post.md
@@ -10,11 +10,11 @@ canonical_url: get_voters_list_on_post.html
-Tutorial will explain and show you how to access the **Steem** blockchain using the [steem-python](https://github.com/steemit/steem-python) library to fetch list of posts and get voters info on selected post.
+Tutorial will explain and show you how to access the **Hive** blockchain using the [steem-python](https://github.com/steemit/steem-python) library to fetch list of posts and get voters info on selected post.
## Intro
-Steem python library has built-in function to get active voters information if post with author and permlink as an argument. Since we don't have predefined post or author/permlink. We will fetch post list from previous tutorial and give option to choose one post to get its active voters. `get_active_votes` function fetches list of active voters on content. Note that `get_discussions_by_active` filter is used for fetching 5 posts which by default contains `active_votes` of each post, but for purpose of this tutorial we will use `get_active_votes` function to fetch voters info.
+Hive python library has built-in function to get active voters information if post with author and permlink as an argument. Since we don't have predefined post or author/permlink. We will fetch post list from previous tutorial and give option to choose one post to get its active voters. `get_active_votes` function fetches list of active voters on content. Note that `get_discussions_by_active` filter is used for fetching 5 posts which by default contains `active_votes` of each post, but for purpose of this tutorial we will use `get_active_votes` function to fetch voters info.
## Steps
@@ -27,15 +27,15 @@ Steem python library has built-in function to get active voters information if p
In this tutorial we use 3 packages, `pick` - helps us to select filter interactively. `steem` - steem-python library, interaction with Blockchain. `pprint` - print results in better format.
-First we import all three library and initialize Steem class
+First we import all three library and initialize Hive class
```python
import pprint
from pick import pick
- # initialize Steem class
- from steem import Steem
+ # initialize Hive class
+ from steem import Hive
- s = Steem()
+ s = Hive()
```
#### 2. Post list
diff --git a/_tutorials-python/getting_started.md b/_tutorials-python/getting_started.md
index 4d546bce39b90ec6b0d4fb78c703c0e13009c026..8c65f5cc5b0c64e6b94acc46ce5c43d78ec62eaf 100644
--- a/_tutorials-python/getting_started.md
+++ b/_tutorials-python/getting_started.md
@@ -1,7 +1,7 @@
---
title: 'PY: Getting Started'
position: 0
-description: "The official Steem library for Python is `steem-python`. It comes with a BIP38 encrypted wallet and a practical CLI utility called `steempy`."
+description: "The official Hive library for Python is `steem-python`. It comes with a BIP38 encrypted wallet and a practical CLI utility called `steempy`."
layout: full
canonical_url: getting_started.html
---
diff --git a/_tutorials-python/grant_active_permission.md b/_tutorials-python/grant_active_permission.md
index 5abbfde6f9dc137fd58893dce99e6cb3c942173d..1aca3ff779569997ed65d885fee15e4dcade71de 100644
--- a/_tutorials-python/grant_active_permission.md
+++ b/_tutorials-python/grant_active_permission.md
@@ -10,19 +10,19 @@ canonical_url: grant_active_permission.html
-In this tutorial we show you how to check if someone has got active permission for an account on the **Steem** blockchain and how to grant or revoke that permission using the `commit` class found within the [steem-python](https://github.com/steemit/steem-python) library.
+In this tutorial we show you how to check if someone has got active permission for an account on the **Hive** blockchain and how to grant or revoke that permission using the `commit` class found within the [steem-python](https://github.com/steemit/steem-python) library.
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 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 Steem 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.
+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.
-[this article](https://steemit.com/steem/@good-karma/steem-multi-authority-permissions-and-how-active-authority-works-part-2-f158813ec0ec1) has more detail around active authorities
+[this article](https://hive.blog/steem/@good-karma/steem-multi-authority-permissions-and-how-active-authority-works-part-2-f158813ec0ec1) has more detail around active authorities
## Intro
-The Steem python library has a built-in function to transmit transactions to the blockchain. We are using the `allow` and `disallow` methods found within the `commit` class in the library. Before we grant or revoke permission, we use the `get_account` function to check whether the requested user already has that permission or not. This is not strictly necessary but adds to the useability of the process. The `allow` method has 5 parameters:
+The Hive python library has a built-in function to transmit transactions to the blockchain. We are using the `allow` and `disallow` methods found within the `commit` class in the library. Before we grant or revoke permission, we use the `get_account` function to check whether the requested user already has that permission or not. This is not strictly necessary but adds to the useability of the process. The `allow` method has 5 parameters:
1. _foreign_ - The foreign account that will obtain access
1. _weight_ - This is an optional parameter defining the weight to use. If not defined, the threshold value will be used. If the weight is smaller than the threshold, additional signatures will be required.
@@ -64,7 +64,7 @@ username = input('Enter username: ')
wif = input('Enter private ACTIVE key: ')
#connect to production server with active key
-client = steem.Steem(keys=[wif])
+client = steem.Hive(keys=[wif])
```
#### 2. Username validation
diff --git a/_tutorials-python/grant_posting_permission.md b/_tutorials-python/grant_posting_permission.md
index 50f0d023f71301cb50dd013e930ae579e129b40c..f663fa012a4849c1dbd5c15f0057979bfe782722 100644
--- a/_tutorials-python/grant_posting_permission.md
+++ b/_tutorials-python/grant_posting_permission.md
@@ -10,13 +10,13 @@ canonical_url: grant_posting_permission.html
-In this tutorial we show you how to check if someone has posting permission for an account on the **Steem** blockchain and how to grant or revoke that permission using the `commit` class found within the [steem-python](https://github.com/steemit/steem-python) library.
+In this tutorial we show you how to check if someone has posting permission for an account on the **Hive** blockchain and how to grant or revoke that permission using the `commit` class found within the [steem-python](https://github.com/steemit/steem-python) library.
Providing another user posting permission for your account can be used to allow multiple users to submit posts on a single steemit community. @Utopian-Io is an example of such a community. There are also applications that allows you to schedule posts by automatically publishing on your behalf.
## Intro
-The Steem python library has a built-in function to transmit transactions to the blockchain. We are using the `allow` and `disallow` methods found within the `commit` class in the library. Before we grant or revoke permission, we use the `get_account` function to check whether the requested user already has that permission or not. This is not strictly necessary but adds to the useability of the process. The `allow` method has 5 parameters:
+The Hive python library has a built-in function to transmit transactions to the blockchain. We are using the `allow` and `disallow` methods found within the `commit` class in the library. Before we grant or revoke permission, we use the `get_account` function to check whether the requested user already has that permission or not. This is not strictly necessary but adds to the useability of the process. The `allow` method has 5 parameters:
1. _foreign_ - The foreign account that will obtain access
1. _weight_ - This is an optional parameter defining the weight to use. If not defined, the threshold value will be used. If the weight is smaller than the threshold, additional signatures will be required.
@@ -58,7 +58,7 @@ username = input('Enter username: ')
wif = input('Enter private ACTIVE key: ')
#connect to production server with active key
-client = steem.Steem(keys=[wif])
+client = steem.Hive(keys=[wif])
```
#### 2. Username validation
diff --git a/_tutorials-python/password_key_change.md b/_tutorials-python/password_key_change.md
index 16748fe38576571afd287469df27f54a84e76f95..24d81a6d366d4edf51f043049fe2095e9a074e0c 100644
--- a/_tutorials-python/password_key_change.md
+++ b/_tutorials-python/password_key_change.md
@@ -10,11 +10,11 @@ canonical_url: password_key_change.html
-In this tutorial we will explain and show you how to change your account password and keys on the **Steem** blockchain using the `steem` class found within the [steem-python](https://github.com/steemit/steem-python) library.
+In this tutorial we will explain and show you how to change your account password and keys on the **Hive** blockchain using the `steem` class found within the [steem-python](https://github.com/steemit/steem-python) library.
## Intro
-The Steem python library has a built-in function to update your account details on the blockchain. We are using the `AccountUpdate` and `commit.finalizeOp` to make these changes. The `AccountUpdate` function creates the operation that we will be committing to the blockchain using the `commit.finalizeOp` function. We first get the existing keys from your account then recreate these from your new password. Once these have been created using your new password we commit them to the blockchain. The initial parameters we need to complete this operation are:
+The Hive python library has a built-in function to update your account details on the blockchain. We are using the `AccountUpdate` and `commit.finalizeOp` to make these changes. The `AccountUpdate` function creates the operation that we will be committing to the blockchain using the `commit.finalizeOp` function. We first get the existing keys from your account then recreate these from your new password. Once these have been created using your new password we commit them to the blockchain. The initial parameters we need to complete this operation are:
1. _account_ - The user account that we will be changing
1. _old_password_ - Your existing password for the account we are changing
@@ -60,19 +60,19 @@ new_password = input('New password: ')
### 3. Connect to the blockchain
-From the parameters that have been collected we will generate the private key for the account and connect to the **Steem** blockchain.
+From the parameters that have been collected we will generate the private key for the account and connect to the **Hive** blockchain.
```python
old_owner_key = str(
PasswordKey(account, old_password, "owner").get_private_key()
)
-client = steem.Steem(keys=[old_owner_key])
+client = steem.Hive(keys=[old_owner_key])
```
### 4. Configure new keys
-We will now generate new keys for each role using the new password as well as create the json that will be committed to the **Steem** blockchain. We generate new keys using the new password for each of these roles.
+We will now generate new keys for each role using the new password as well as create the json that will be committed to the **Hive** blockchain. We generate new keys using the new password for each of these roles.
```python
new_public_keys = {}
@@ -129,7 +129,7 @@ print(result)
If you update your password and attempt to update it again to quickly you will receive the following error.
```
-Assert Exception:_db.head_block_time() - account_auth.last_owner_update > STEEM_OWNER_UPDATE_LIMIT: Owner authority can only be updated once an hour.
+Assert Exception:_db.head_block_time() - account_auth.last_owner_update > HIVE_OWNER_UPDATE_LIMIT: Owner authority can only be updated once an hour.
```
You will need to wait at least an hour before attempting this again.
diff --git a/_tutorials-python/power_down.md b/_tutorials-python/power_down.md
index 4b3ab955e50933ef25189896583eb36ec7fdc165..b4826bd8767f12a9af20a43628cb42a265f87706 100644
--- a/_tutorials-python/power_down.md
+++ b/_tutorials-python/power_down.md
@@ -10,11 +10,11 @@ canonical_url: power_down.html
-In this tutorial we will explain and show you how to power down some or all of your available vesting shares (STEEM POWER) on the **Steem** blockchain using the `commit` class found within the [steem-python](https://github.com/steemit/steem-python) library.
+In this tutorial we will explain and show you how to power down some or all of your available vesting shares (HIVE POWER) on the **Hive** blockchain using the `commit` class found within the [steem-python](https://github.com/steemit/steem-python) library.
## Intro
-The Steem python library has a built-in function to transmit transactions to the blockchain. We are using the `withdraw_vesting` method found within the `commit` class in the library. When you power down, the converted VESTS (STEEM POWER) will not be available as STEEM immediately. It is converted in 13 equal parts and transferred into your STEEM wallet weekly, the first portion only being available a week after the power down was initiated. Before we do the conversion, we check the current balance of the account to check how much STEEM POWER is available. This is not strictly necessary as the process will automatically abort with the corresponding error, but it does give some insight into the process as a whole. We use the `get_account` function to check for this. The `withdraw_vesting` method has 2 parameters:
+The Hive python library has a built-in function to transmit transactions to the blockchain. We are using the `withdraw_vesting` method found within the `commit` class in the library. When you power down, the converted VESTS (HIVE POWER) will not be available as HIVE immediately. It is converted in 13 equal parts and transferred into your HIVE wallet weekly, the first portion only being available a week after the power down was initiated. Before we do the conversion, we check the current balance of the account to check how much HIVE POWER is available. This is not strictly necessary as the process will automatically abort with the corresponding error, but it does give some insight into the process as a whole. We use the `get_account` function to check for this. The `withdraw_vesting` method has 2 parameters:
1. _amount_ - The amount of VESTS that will be withdrawn. This must be of the `float` data type
1. _account_ - The specified user account for the transfer
@@ -22,7 +22,7 @@ The Steem python library has a built-in function to transmit transactions to the
## Steps
1. [**App setup**](#setup) - Library install and import. Connection to testnet
-1. [**User information and steem node**](#userinfo) - Input user information and connection to Steem node
+1. [**User information and steem node**](#userinfo) - Input user information and connection to Hive node
1. [**Check balance**](#balance) - Check current vesting balance of user account
1. [**Conversion amount and commit**](#convert) - Input of VESTS amount to convert and commit to blockchain
@@ -41,9 +41,9 @@ import steem
from pick import pick
from steem.amount import Amount
-steembase.chains.known_chains['STEEM'] = {
+steembase.chains.known_chains['HIVE'] = {
'chain_id': '79276aea5d4877d9a25892eaa01b0adf019d3e5cb12a97478df3298ccdd01673',
- 'prefix': 'STX', 'steem_symbol': 'STEEM', 'sbd_symbol': 'SBD', 'vests_symbol': 'VESTS'
+ 'prefix': 'STX', 'hive_symbol': 'HIVE', 'hbd_symbol': 'HBD', 'vests_symbol': 'VESTS'
}
```
@@ -59,7 +59,7 @@ username = input('Enter username: ') #demo account: cdemo
wif = input('Enter private ACTIVE key: ') #demo account: 5KaNM84WWSqzwKzY82fXPaUW43idbLnPqf5SfjGxLfw6eV2kAP3
#connect node and private active key
-client = steem.Steem(nodes=['https://testnet.steem.vc'], keys=[wif])
+client = steem.Hive(nodes=['https://testnet.steem.vc'], keys=[wif])
```
#### 3. Check balance
diff --git a/_tutorials-python/power_up_steem.md b/_tutorials-python/power_up_steem.md
index 911ea99dbfbdae6c2b32081855a6ac26902c48d3..7e1e355e7b8c2afa633ef557a6691fa7ca94542a 100644
--- a/_tutorials-python/power_up_steem.md
+++ b/_tutorials-python/power_up_steem.md
@@ -1,29 +1,29 @@
---
-title: 'PY: Power Up Steem'
+title: 'PY: Power Up Hive'
position: 24
-description: "How to power up your STEEM to STEEM POWER using Python."
+description: "How to power up your HIVE to HIVE POWER using Python."
layout: full
-canonical_url: power_up_steem.html
+canonical_url: power_up_hive.html
---
-Full, runnable src of [Power Up Steem](https://gitlab.syncad.com/hive/devportal/-/tree/master/tutorials/python/tutorials/24_power_up_steem) can be downloaded as part of: [tutorials/python](https://gitlab.syncad.com/hive/devportal/-/tree/master/tutorials/python).
+Full, runnable src of [Power Up Hive](https://gitlab.syncad.com/hive/devportal/-/tree/master/tutorials/python/tutorials/24_power_up_hive) can be downloaded as part of: [tutorials/python](https://gitlab.syncad.com/hive/devportal/-/tree/master/tutorials/python).