Internal Testing Chain
Switch branches/tags
0.19.1-corefix 0.19.1-hotfix 0.19.1-p2pfix-bumpram 0.19.1-p2pfix-paas 0.19.1-p2pfix 0.19.2-p2p-debug-logging 0.19.2-rebroadcast 3rdparty-0.19.0-bumpmem 3rdparty-0.19.0 68-auth-rule 133-debug-edit-script 150-liquidity-voting 210-db-api-refactor 222-promoted 240-lostpassword-old 286-bootstrap-develop 286-bootstrap 319-witness-block-report 355-crash-network-api 387-one-touch-testing 473-cpp14-test 558-dcma 568-blind-rewrite 568-blind 588-flush-block-log 597-copy-txids-for-async 644-follow-dispatch 668-witness-stats 698-equihash-security 725-auth-revoker-tests 725-auth-revoker 737-appbase 792-syncing-docker-script 827_refactor_database_fixture 853-fix-invalid-vop-trx 963-fork-monitor-plugin 963-fork-plugin 991-explicit-price 1019-add-impacted-ops 1052-sqrt-curve 1078-cleanup-indices 1096-api-category-object 1103-chainbase-debug-index-check 1147_warning_cleanup 1191-new-rw-mutex 1268_steemit_rename 1278-steemit-testnet 1296-flush-state 1299-appbase-cmake 1300-appbase-minreqs 1314 1318-api-object-naming 1322-get-block-new-api 1334-rpc-id-init 1344-rename-api-in-webserver-rebase 1415-min-block-size 1416-move-locks-into-heap 1418-backtrace 1419_docker_static_build 1457-example-step1 1457-example-step2 1457-example-step3 1510-Surround-SMT-Objects-Evaluators-and-Fields-in-ifdef 1513-Implement-smt_setup_inflation_operation 1554-Rename-smt_elevate_account-to-smt_create 1562-ro-build-dir 1567-api-testing 1590-add-benchmarking-cmd-options 1594-performance 1595-string-pooling 1622-Check-Existing-SMT-Ops-for-NAI-Compatibility 1633-allowed-syms 1640-fix-asset-string-serialization 1653-Define-and-implement-testing-scenarios-related-to-smt_create_operation 1657-mem-pool-fix 1657-trx-api 1671-ah-pruning-appbase 1671-ah-pruning 1674-verify-signatures-api-appbase 1674-verify-signatures-api 1676-Internal-Reference-to-SMTs-should-be-asset-symbol-type 1677 1699-debug-busy-wait 1710-Encapsulate-SMT-finding-in-dedicated-method-of-account_object 1724-timed-event-scheduler 1735-document-get-dev-key 1736-get_dev_key_name 2017-08-29-memo-protection-develop 2017-08-29-memo-protection-master 2017-08-29-memo-protection 2017-10-23-runtime-p2p-config 2017-10-26-genesis-hardforks 2017-10-26-no-genesis-vesting-split 2017-10-30-authority-errmsg 20170303-update-s 20171021-master-no-ah 20171024-update-seednodes 20171025-master adjustmemory-0.19.0rc2 api-refactor appbase-no-tags appbase backup-0.19.0rc3 bip-container-typename broadcaster-p2p-connections broadcaster bumpversion chainbase-2-expose-types chainbase-3-move-undo-state chainbase-4-get-undo-state chainbase-5-index-iteration develop-20171026 develop-bump-shared-mem develop-increase-shared-mem develop-ops-filtering develop doxygen-docs enode fixcompression-0.18.5 fixcompression-0.19.0rc1 fixmultireaderargs-0.19.0rc3 follow freebsd-support health-show-blockage htlc-operation increase-p2p-connections increasememory-0.18.5 increasememory-0.19.0 increasememory incremental-merkle index-iteration initminer-problems master-9-15 master-10-2 master-10-21 master new_coding_approach nginx-ratelimit nginx-tweaks nocompression object_builder oppose_account pending_trx_bug reducememory-0.19.0rc3 reducememorymultireader-0.19.0rc3 revert-1243-udpate-exchange-quickstart revert-1686-1671-ah-pruning-appbase signature-logging smt-develop stable state_model_opts std-allocator tags-optimized theoretical-testnet tmpfs-0.19.0 udpate-exchange-quickstart update-readme-cli updatescripts v0.16.3-embedded-chainbase wallet-problems
Nothing to show
Clone or download
Pull request Compare This branch is 2 commits ahead, 2184 commits behind steemit:master.
Latest commit 71b7729 Nov 7, 2017

README.md

Introducing Steem (beta)

Steem is a Delegated Proof of Stake blockchain that uses a "Proof of Brain" social consensus algorithm for token allocation.

  • Currency symbol STEEM.
  • 10% APR inflation narrowing to 1% APR over 20 years.
  • 75% of inflation to "Proof of Brain" social consensus algorithm.
  • 15% of inflation to stake holders.
  • 10% of inflation to block producers.

Public Announcement & Discussion

Steem was announced on the Bitcointalk forum prior to the start of any mining.

No Support & No Warranty

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Whitepaper

You can read the Steem Whitepaper at Steem.io/SteemWhitePaper.pdf.

Quickstart

Just want to get up and running quickly? We have pre-built docker images for your convenience. More details are in our quickstart guide.

Building

We strongly recommend using one of our pre-built Docker images or using Docker to build Steem. Both of these processes are described in the quickstart guide.

If you would still like to build from source, we do have build instructions for Linux (Ubuntu LTS) and macOS X.

Dockerized p2p Node

To run a p2p node (ca. 2GB of memory is required at the moment):

docker run \
    -d -p 2001:2001 -p 8090:8090 --name steemd-default \
    steemit/steem

docker logs -f steemd-default  # follow along

Dockerized Full Node

To run a node with all the data (e.g. for supporting a content website) that uses ca. 14GB of memory and growing:

docker run \
    --env USE_WAY_TOO_MUCH_RAM=1 --env USE_FULL_WEB_NODE=1 \
    -d -p 2001:2001 -p 8090:8090 --name steemd-full \
    steemit/steem

docker logs -f steemd-full

Environment variables

There are quite a few environment variables that can be set to run steemd in different ways:

  • USE_WAY_TOO_MUCH_RAM - if set to true, steemd starts a 'full node'
  • USE_FULL_WEB_NODE - if set to true, a default config file will be used that enables a full set of API's and associated plugins.
  • USE_NGINX_FRONTEND - if set to true, this will enable an NGINX reverse proxy in front of steemd that proxies websocket requests to steemd. This will also enable a custom healtcheck at the path '/health' that lists how many seconds away from current blockchain time your node is. It will return a '200' if it's less than 60 seconds away from synced.
  • USE_MULTICORE_READONLY - if set to true, this will enable steemd in multiple reader mode to take advantage of multiple cores (if available). Read requests are handled by the read-only nodes, and write requests are forwarded back to the single 'writer' node automatically. NGINX load balances all requests to the reader nodes, 4 per available core. This setting is still considered experimental and may have trouble with some API calls until further development is completed.
  • HOME - set this to the path where you want steemd to store it's data files (block log, shared memory, config file, etc). By default /var/lib/steemd is used and exists inside the docker container. If you want to use a different mountpoint (like a ramdisk, or a different drive) then you may want to set this variable to map the volume to your docker container.

PaaS mode

Steemd now supports a PaaS mode (platform as a service) that currently works with Amazon's Elastic Beanstalk service. It can be launched using the following environment variables:

  • USE_PAAS - if set to true, steemd will launch in a format that works with AWS EB. Containers will exit upon failure so that they can be relaunched automatically by ECS. This mode assumes USE_WAY_TOO_MUCH_RAM and USE_FULL_WEB_NODE, they do not need to be also set.
  • S3_BUCKET - set this to the name of the S3 bucket where you will store shared memory files for steemd in Amazon S3. They will be stored compressed in bz2 format with the file name blockchain-$VERSION-latest.tar.bz2, where $VERSION is the release number followed by the git short commit hash stored in each docker image at /etc/steemdversion.
  • SYNC_TO_S3 - if set to true, the node will function to only generate shared memory files and upload them to the specified S3 bucket. This makes fast deployments and autoscaling for steemd possible.

Seed Nodes

A list of some seed nodes to get you started can be found in doc/seednodes.txt.

This same file is baked into the docker images and can be overridden by setting STEEMD_SEED_NODES in the container environment at docker run time to a whitespace delimited list of seed nodes (with port).

Testing

See doc/testing.md for test build targets and info on how to use lcov to check code test coverage.

System Requirements

For a full web node, you need at least 110GB of disk space available. Steemd uses a memory mapped file which currently holds 56GB of data and by default is set to use up to 80GB. The block log of the blockchain itself is a little over 27GB. It's highly recommended to run steemd on a fast disk such as an SSD or by placing the shared memory files in a ramdisk and using the --shared-file-dir=/path command line option to specify where. At least 16GB of memory is required for a full web node. Seed nodes (p2p mode) can run with as little as 4GB of memory with a 16 GB state file. Any CPU with decent single core performance should be sufficient. Steemd is constantly growing. As of August 2017, these numbers were accurate, but you may find you need more disk space to run a full node. We are also constantly working on optimizing Steem's use of disk space.

On Linux use the following Virtual Memory configuration for the initial sync and subsequent replays. It is not needed for normal operation.

echo    75 | sudo tee /proc/sys/vm/dirty_background_ratio
echo  1000 | sudo tee /proc/sys/vm/dirty_expire_centisec
echo    80 | sudo tee /proc/sys/vm/dirty_ratio
echo 30000 | sudo tee /proc/sys/vm/dirty_writeback_centisec