You voted for yourself with your stake which is correct but you simply don't have enough votes. I started voting for your witness.
Thank you! Now i got some more votes:
unlocked >>> get_witness dev4bc
get_witness dev4bc
{
"id": "1.6.47",
"witness_account": "1.2.3340",
"last_aslot": 0,
"signing_key": "TEST7hJfPdJV3mgjnBwnbsGHbC9zWL5rDUUyqSkVQXeK4pZkRhaggB",
"vote_id": "1:78",
"total_votes": "97996139400",
"url": "
http://izx.io",
"total_missed": 0,
"last_confirmed_block_num": 0
}
Will wait till somebody else will vote.
I have one other question related to test node setup:
when i tried started it, it failed due to out-of-memory before i set up by recommendations:
# Account ID to track history for (may specify multiple times)
track-account = "1.2.3340"
# Keep only those operations in memory that are related to account history tracking
partial-operations = true
# Maximum number of operations per account will be kept in memory
max-ops-per-account = 1
Only after that changes the node finally synced ad started.
I did not find any explanation how the settings related to account history affect the functionality of the node.
Does it affect witness? block generation? API operations?
Why in the hell the node should keep so much data _in memory_ by default?