gtg witness log

in #witness-category7 years ago

Current policy

  • Unbiased price feed
  • Minimum account creation fee set to 0.100 STEEM
  • SBD interest rate at 0%

Current, observed parameters

Real SBD value: $2.123
STEEM value: $2.788
current_sbd_supply: 1612472.578 SBD
sbd_interest_rate: 0
account_creation_fee: 0.200 STEEM



Getting Steem Power from SBD

Please note that due to a market conditions (when 1SBD is traded on markets for more than 1USD) it is better to choose: Rewards: Default (50% / 50%) instead of Rewards: Power Up 100% while posting.
You are able to trade received SBD to Steem at better rate on internal market and then Power Up.
You can even do that without trading by using Blocktrades:

  • Select coin to send: Steem Dollar
  • Select coin to receive: Steem Power
    No need to enter amount it is just for getting estimates.
  • Enter your receive address: your steem account name
  • Click Get Deposit Address
    Then all you need is to send any amount of SBD (up to the suggested deposit limit) to the account named blocktrades with memo that you would receive in the last step. You would be powered up by appropriate amount of Steem and that's it.

You should be able to find more detailed instructions for both internal market and Blocktrades somewhere on Steem. If you have any questions of course feel free to ask, but please be patient, it might take me some time to reply.

Upcoming Hard Fork

Testing of upcoming v0.19.0 still in progress. All witnesses are encouraged to review and test it.
While it was not that visible when dealing with witness or seed nodes, I was having serious performance issues while replaying full nodes. Keeping shared_memory file in RAM which currently takes ~50GB is a bit problematic, especially if you also want to keep there ~12GB block_log for faster access.
Normal operations was fast enough to serve 250-300 requests per second, however replay times (with validation) was taking 24h while sitting on a disk and not having enough physical RAM for effective mmaping. Also, disk here means 3x SSD working in parallel.
But here are the good news:
This means that we are growing, and that is cool.
Re-indexing performance should be now greatly improved.
Nonetheless, upgrading node hardware is imminent.

Seed nodes

Dear witnesses, please check your seed nodes.
My latest review resulted in removing many obsolete nodes that failed to respond all consecutive attempts during a week, so that wasn't short outage in any of those cases.
In case of any updates related to seed nodes, please post them on #seed-nodes channel and I would include them in next pull request.

Useful resources

Full node with public steem API

It's available at: gtg.steem.house:8090

Soon I would upgrade my full API node with latest rc version, i.e. v0.19.0rc3. This would bring an additional change:

SKIP_BY_TX_ID=ON

which makes that the account history plugin does not allow querying of operations by transaction id. This feature is not used by most use cases including condenser.
My node would be using default value for --follow-start-feeds, compatible with current behavior.

Node would be running v0.19.0 built with:
CMAKE_BUILD_TYPE = Release
LOW_MEMORY_NODE  = OFF
CLEAR_VOTES      = OFF
SKIP_BY_TX_ID    = ON
Available APIs:
public-api = database_api
public-api = login_api
public-api = account_by_key_api
public-api = network_broadcast_api
public-api = tag_api
public-api = follow_api
public-api = market_history_api
public-api = raw_block_api

Please note that due to high demand vs limited resources I might be forced to temporarily route that traffic to backup instances and thus number of handled requests might be throttled down.
If you are running a project that depends on my node feel free to contact me when you encounter any issues or you need dedicated node.

SBD from my witness updates would be used to power up API node.


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 steemit.chat, as Gandalf



Steem On

Sort:  

Hey man! I'm trying to create an account and I even tried 0.500 STEEM as the creation fee and it still doesn't work. The error message is pretty confusing. It says: Insufficient Fee: 0.000 STEEM required, 0.500 STEEM provided. Any idea? I would really appreciate it!

Hello,
Current consensus on registration fee is set to 0.2 STEEM but then you need to delegate more Steem Power, taking into account this equation:
5 * min_fee + STEEM_POWER == 150 * min_fee
So if you use 0.2 STEEM then you need to delegate 29 Steem Power.
Other option is to create an account with 15 STEEM 6 STEEM then you don't need to delegate Steem Power at all.

Thanks for the reply! That explains how steem creates accounts with only half a STEEM. How did you get to 15 SP without delegation? I've seen anonsteem create accounts without delegation and they only put in 6 STEEM. I haven't tried 6 STEEM myself. Just asking...

Also, do you know why the error message says that the minimum required fee is 0.000 STEEM, instead of actually telling me what the minimum required fee is?

You are right, it should be 6, I was thinking about your example (0.500 STEEM) but minimum base amount is lower that that.

Alright now I get it! Thanks heaps buddy! Really appreciate it...

Congrats! You're a winner of @msg768's daily giveaway #29. To find out more, click HERE.

Where you get that message from? cli_wallet?

I'm using the javascript library but if I'm not wrong, all it does is call the actual cpp methods which means the error message should be the same as every other interface such as the cli_wallet!

Hay @gtg,

thank you for the update and for providing that service.

Re-indexing performance should be now greatly improved.

I totally agree. I just bought some new SDDs as it now takes years with my old HDD raid. Do you have some tricks to speed up the re-indexing in general and do you know if the dev/core team is aware of this problem?

Thanks and best regards,

@dez1337

Not only they are aware of that, but they improved it already (that's what I had in mind above)
I've used "should" because while I already have some rc3 nodes I still need to compare some certain use cases on same environment (i.e. my main full node).
Please take a look at closed issues: #1160 #1161 #1162

As for tips&tricks you might want to use ram disk (i.e. tmpfs) for at least shared-memory file. Even if you don't have enough RAM, swapping seems to be more effective than mmaping file with default Linux vm settings. You might want to use it only for replay, then move back to disks. Also, use --flush=1000000. And of course use only those plugins that you really need.

Thanks for the clarification :)

thanks for sharing

Cory cool posts for witness-category ...
Good job @gtg
Upvote & Resteem

Great to read the new HF is in testing; Any indication when HF19 is scheduled for roll out?

Soon(TM)
It has yet to be scheduled but I hope that it would be still in June. So far so good.

oh cool, since 'soon' does not have a timescale, and I know people stating soon as in one year or more :) but june sounds good neough for me :)

Thank you for the information!:)

Very helpful information.
Upvoted it and followed you @gtg

Proud support here.

Best Regards
@abn

I'm not going to lie. I'm not a tech person, a computer person, or a cryto currency person. I'm a hardcore budget traveler who has been living out of a backpack for about 10 years. About a month I go I started here on steemit. I write detailed travel reports with a rating system and all. I believe I bring good information, well written articles, and value to the community. Getting the attention of someone like you on here to advise me would really help me out. Is there anything I should or should not be doing. Would you be kind enough to check out one of my recent reports?

Thank you so much!

Dan- World Travel Pro

They look fine, I'm not a target reader so I suppose I can't review them properly, but for me (of course other people can have different, sometimes opposite point of view) I would like more your own photos (instead those from stock), more personal stories and also please avoid Post titles written in ALL CAPS.

Good luck! :-)

That's exactly what I was looking for a good honest opinion from someone with blogging experience, which I have none. Thank you!

Just changed the title, and will certainly be taking all your advice. And thank you for the up-vote......like Wow, your vote carries weight, I think it just bought me two nights at my hotel here in Mexico! Thank you!