Steem Pressure #7: Go Fork Yourself. Step by step guide to building and setting up a MIRA powered HF21-ready Steem consensus node.


The date of the next, 21st HardFork, has been set, and it is approaching quickly.

There's plenty of info around the web on how to build a Steem node from scratch.
I also wrote a guide some time ago: Steem Pressure #3: Steem Node 101.
But the trouble is that such tutorials are getting old and obsolete.

My previous one was made for version 19 at its early development stages.
Now, we have version 21 released, so it is a good opportunity for an update.


Video created for Steem Pressure
Steem Pressure #2 - Toys for Boys and Girls
Steem Pressure #3 - Steem Node 101
[Steem Pressure: The Movie ;-)](/@gtg/steem-pressure-the-movie)
Steem Pressure #4 - Need for Speed
Steem Pressure #5 - Run, Block, Run!
Steem Pressure #6 - MIRA: YMMV, RTFM, TLDR: LGTM
Stay tuned for next episodes of Steem Pressure :-)

---

If you believe I can be of value to Steem, please vote for me (**gtg**) as a witness on Steemit's Witnesses List or set (**gtg**) as a proxy that will vote for witnesses for you.
Your vote does matter!
You can contact me directly on steem.chat, as Gandalf



Steem On


Comments 53


This post has been resteemed by @witnessnews.

Follow @witnessnews to keep up with active witness updates.

15.08.2019 21:36
0

Thanks. I would love to set a node someday. Maybe today? ;)

15.08.2019 21:45
1

Go fork yourself

lol

15.08.2019 22:07
0

1333MHz RAM 😲

15.08.2019 22:08
3

something reasonably modest and cheap

:-)

16.08.2019 10:26
0

very! indeed.... I could get tons of it... but I would not have power enough to support it.

17.08.2019 13:21
0

Amazing howto, amazing title. Forking myself in the next days. ☕️😃

Posted using Partiko iOS

15.08.2019 23:09
1

..sounds like being possible also for me (one day..)..thx..up..follow you..

15.08.2019 23:42
1

Thank you for this! I swear I’m gonna do this someday!

Posted using Partiko iOS

16.08.2019 00:32
1

What the heck is the purpose for a witness proxy?

Off-topic yes, but maybe an idea for you to do a witness episode?

Anyways, this was an awesome and super easy step-by step! Thanks!

16.08.2019 02:29
1

Witness proxy is an account that you chose to vote for witnesses on your behalf.
It's meant for people that don't pay that much of attention to what's going on with witnesses and are comfortable trusting their witness proxy to make those choices for them.
So if you set someone to be your witness proxy, whenever they decide to approve or unapprove some witness, your votes will be exactly the same.

16.08.2019 10:18
1

Great explanation! I love that you included a use case, thank you!

16.08.2019 10:58
0

Thanks. I’ve been looking for an updated Steem Node setup guide. If I have a much more powerful machine with 128Gb RAM what can I add to make it a full node?

Posted using Partiko iOS

16.08.2019 03:22
6

I wouldn't recommend using "full node" anymore, i.e. monolithic instance.
I would rather use fat node and low mem node of AH - your machine might be good for one of those. Adding Hivemind and Jussi there, will make it pretty nice set to satisfy full API needs.

16.08.2019 10:52
0

Perfect timing 👨🏾‍🚀👍🏽

can get @reggaesteem node up asap

🍻!BEER

Posted using Partiko iOS

16.08.2019 06:43
1

It's good to start with a public seed node and try to keep it up and running.
To make your seed node available to general public you will need to add:
p2p-endpoint = 0.0.0.0:2001
and let people know on a steem.chat's #seed-nodes channel that a new seed-node is in town ;-)
Static IP is required and some reliable hostname is preferred.
(above is true for public seed node)

16.08.2019 10:24
0

To view or trade BEER go to steem-engine.com.

Hey @gtg, here is your BEER token. Enjoy it!

Do you already know our [BEER Crowdfunding](https://goldvoice.club/steem/@beerlover/let-s-grow-and-update-the-beer-token-huge-crowndfunding-as-crowdsale)
16.08.2019 06:43
0

Everybody is looking forward to the date and the kickstart of the 21 hardfork and I must say, majority people can't wait

16.08.2019 07:49
1

True effects of HF21 will not be instant. It might take a month or two before people will adjust their habits.

16.08.2019 10:04
0

This post earned a total payout of 0.041$ and 0.031$ worth of author reward which was liquified using @likwid. To learn more.

23.08.2019 07:51
0

So if a full-fledged system is to be made from the instructions you have given here, how much time would it take for it to be made available to the public and what about the security of the chain?

16.08.2019 08:28
2

In this configuration node will not be available to the public in other means than just being a part of Steem p2p network. It's a consensus node. In this configuration it can serve you as a simple API node (with subset of supported API calls), you can use it for example to broadcast transactions to the network.

To turn it into a public seed node, you need to add:
p2p-endpoint = 0.0.0.0:2001
which will make it to listen on all interfaces on port 2001 (default p2p port for Steem)
and then let people know on a steem.chat's #seed-nodes channel that a new seed-node is in town ;-)
Static IP is required and some reliable hostname is obviously good to have.

It will take about 72 hours using that example hardware/software configuration to reach the head block.

When it finish replaying, its API endpoint will be available. You can use some proxy with SSL termination to make it available to the public too, but keep in mind that API is limited.

16.08.2019 10:38
0

Hoping this to change a bit on the next SMT model...

17.08.2019 13:20
0

its not a standard thing...everyone will have its "crazy" things... I for example, would be more enterprise model... if I had the money to support it. Not that I could not do it with what I have (which I have done in the past)...

Everything depends... ask something more specific, and I might be able to shed some more light. If that's where you want to go.

17.08.2019 13:19
0

Looking forward for an updated Steem Node setup guide !!!!!!

16.08.2019 11:43
1

Maybe you should look backward then? ;-) That's the guide you are looking for.

16.08.2019 12:09
0

Can I start one with dule core 8 gb ram and 500gb hard drive

Posted using Partiko Android

16.08.2019 14:19
0

All depends on details. 8GB RAM itself wouldn't be that bad but you will experience much higher replay times, especially when your drive is a platter drive, i.e. not SSD.

16.08.2019 15:22
0

Why do you think 8GB RAM would limit replay speed? When I was replaying my MIRA node, the RAM usage stayed below 3GB the entire time.

I used a platter HDD as well and my replay time was roughly 5 days.

16.08.2019 21:22
1

Less for the cache / buffer. Are you using default database.cfg?

16.08.2019 23:10
0

Not sure, didn't spend much time tweaking it since it didn't seem necessary for my setup.

{
  "global": {
    "shared_cache": {
      "capacity": "5368709120"
    },
    "write_buffer_manager": {
      "write_buffer_size": "1073741824"
    },
    "object_count": 62500,
    "statistics": false
  },
  "base": {
    "optimize_level_style_compaction": true,
    "increase_parallelism": true,
    "block_based_table_options": {
      "block_size": 8192,
      "cache_index_and_filter_blocks": true,
      "bloom_filter_policy": {
        "bits_per_key": 10,
        "use_block_based_builder": false
      }
    }
  }
}
18.08.2019 01:52
1

Geesssss... coming back from the future... I need to reconsider my hardware... EOS made me go... 😣 with my set... Still waiting... when I am confortable, I will launch.

17.08.2019 13:25
0

16.08.2019 16:05
0

Nice to see a new steem pressure post. I wonder how many new witnesses there will be and how many will stop over the next year.

Posted using Partiko Android

16.08.2019 18:08
1

If I set up a node in this fashion, would I be able to execute RPC calls against it using Beem? I specifically believe I need the reward API from previous discussions.

I would guess I would not be needing condenser in that case. My intent is to test the SFR bot at some point and explore a mechanism so reward flags different coming from downvote mana.

Any thoughts / guidance would be appreciated.

Posted using Partiko Android

16.08.2019 19:01
3

While you can use it to perform some calls, LOW_MEMORY_NODE might not be enough for you. Please note that rewards_api is for testing purpose only, and explicitly said that it's not meant for use in production.

16.08.2019 20:12
0

I may be getting the API needed confused in that case.

Our bot does approximate flag rshares to SBD conversions using methods of the Beem Steem class for it's voting.

Looks like the method uses get_sbd_per_rshares which calls get_reward_fund. That uses the database API if I am understanding correctly.

That should be fine, right?

16.08.2019 20:45
1

The rewards_api is something brand new that was used to attempt to model the changes to rewards after HF21.

What you are referring to is found in condenser_api which the the api you will use the majority of the time. Sometimes there is the need for database_api but, neither of those are explicitly declared in the config.

16.08.2019 21:24
2

I've been re-forking myself for over a week now, hoping to finish it up one century soon.

17.08.2019 03:21
1

@gtg You have received a 100% upvote from @intro.bot because this post did not use any bidbots and you have not used bidbots in the last 30 days!

Upvoting this comment will help keep this service running.

17.08.2019 12:29
0

I would use a hybrid RAID0 NVMe with RAID5/6 disks... but not recommended on Ubuntu... CentOS or RedHAT 100% ok! =) Tested. With snapshots backups daily and MANY recovery tests ...

17.08.2019 13:12
1

Doesn't make much sense when it comes to simple consensus node.
That one is just cheap and simple.
What exactly is not recommended on Ubuntu, and why?

17.08.2019 14:50
0

cached LVM filesystems... to be specific! Lots of bugs!

17.08.2019 14:54
0

For the record:
Replayed 35538728 blocks in 75h:51m:36s
Then it had to catch up 98913 blocks that were generated in the meantime.
That took another 31m:45s
So in total it took 76h:23m:21s

Also:steem@mirabelle:~/.steemd/blockchain$ du -csh *
215G block_log273M block_log.index269M rocksdb_account_authority_object14M rocksdb_account_history_object14M rocksdb_account_metadata_object406M rocksdb_account_object32M rocksdb_account_recovery_request_object27M rocksdb_block_summary_object25M rocksdb_change_recovery_account_request_object14M rocksdb_comment_content_object20G rocksdb_comment_object263M rocksdb_comment_vote_object53M rocksdb_convert_request_object18M rocksdb_decline_voting_rights_request_object31M rocksdb_dynamic_global_property_object21M rocksdb_escrow_object24M rocksdb_feed_history_object13M rocksdb_hardfork_property_object75M rocksdb_limit_order_object19M rocksdb_liquidity_reward_balance_object17M rocksdb_operation_object39M rocksdb_owner_authority_history_object14M rocksdb_pending_optional_action_object14M rocksdb_pending_required_action_object27M rocksdb_proposal_object17M rocksdb_proposal_vote_object84M rocksdb_rc_account_object14M rocksdb_rc_pool_object11M rocksdb_rc_resource_param_object24M rocksdb_reward_fund_object70M rocksdb_savings_withdraw_object24M rocksdb_transaction_object47M rocksdb_vesting_delegation_expiration_object85M rocksdb_vesting_delegation_object35M rocksdb_withdraw_vesting_route_object14M rocksdb_witness_custom_op_object6.9G rocksdb_witness_object24M rocksdb_witness_schedule_object83M rocksdb_witness_vote_object244G total

17.08.2019 21:51
4

I would be interested to see benchmarks on the new AMD Epyc chips...

19.08.2019 01:49
1

Unfortunately I don't have such hardware available. Ideally it will be same disks, similar RAM setup, and just a difference with CPU/MB vs some high performance Intel setup.

PS
Please take a look at your node, it's missing blocks and it will continue as there's no longer witness shutdown vop in place due to 51% escalation issue, so the only way currently to disable it, is operator nullifying signing key.

19.08.2019 06:13
1

Oh, I didn't know that. I'll shut it down.

27.08.2019 13:52
1

Better yet - come back! :-)

27.08.2019 22:42
1

I have no time unfortunately.

28.08.2019 16:14
1

@gtg great to see guides coming out to set up MIRA. Loving the console animations.

Posted using Partiko Android

20.08.2019 09:36
2

Max open files on my node is 5mil.
Still the mira replay crashes at 5%.
Too many open files.
0.21.9 did run smoothly though:(

31.08.2019 08:06
0

Could you please show some logs / configs?
Either here or on Steem.Chat
(and please be patient)

31.08.2019 10:31
0

Did upgrade ulimit - n 65536
And doing currently a block log download and replay.
8 hours to go.
We will see..

I am now 4 days in, without a working witness node, I think I am patient. :)

31.08.2019 10:43
0