5 posts displayed of 46 total (page 2 of 10).
Account jesta , using activity types [post]
jesta witness update - 2016-11-11
2016-11-12 | Tags: [witness-category] [witness-update]
links
Blog URL /witness-category/@jesta/jesta-witness-update-2016-11-11
Steemit URL https://steemit.com/witness-category/@jesta/jesta-witness-update-2016-11-11
SteemDB URL https://steemdb.com/witness-category/@jesta/jesta-witness-update-2016-11-11
comment model

      Twig Examples:

      {{ post.title }}
      {{ post.author }}
      {{ post.body }}
    
post[id] 1347596
post[author] jesta
post[permlink] jesta-witness-update-2016-11-11
post[category] witness-category
post[parent_author]
post[parent_permlink] witness-category
post[title] jesta witness update - 2016-11-11
post[body] I think I'm planning on sticking to these updates at bi-weekly rate for now, since last week I didn't have much interesting to report and was pretty busy. This week, with next week's upcoming changes, I felt it was a good time to chime in. ## 1. Accomplished the week of 2016-11-11: - Upgraded all the steem.ws/witness/seed steem servers to 0.15.0 - I've started migrating steemdb to a better server, and it will now use it's own private steem instance for increased speed. - The new greymass.com website is now running on an optimized setup of reprint. It's no where near finished in terms of layout/design/pages, but I'm almost at the point where I can say the server infrastructure is good and will scale well. - I have started slowly talking to a few people who want reprint websites, and plan on using these sites as our proof of concept. We also have our own slack now to specifically keep topics on track for greymass/reprint. - Fixed an issue with how proxy votes were tallied on steemdb (thanks @abit!) - Added [global witness voting history](https://steemdb.com/witnesses/history) to steemdb. - Explored Google/AWS/Docker/Kubernetes versions of container solutions for use within a large multi-site reprint installation. - Lots of discussions about the upcoming inflation changes (I'll go into my thoughts below) ## 2. Upcoming projects/goals - Right now I'm working on a steemdb plugin for reprint. This plugin will allow anyone with a reprint site to pull data via a plugin/api in ways the blockchain currently doesn't allow for (optimally). - Expand the steemphp library to include more different types of information. - Continue development of reprint, and launch the greymass.com site as something I'm happy with. - A day or two will be set aside for the 0.16.0 fork coming soon. Currently I have 8-10 steemd servers running at any given moment, and I discovered this week that upgrading all of these servers takes a bit of time! ## 3. Thoughts from this week Major changes on the horizon in terms of the steem economy, and I for one am glad we're seeing some progress. However, I don't like the fact that there are so many unrelated changes all being bundled into a single update. This sentiment has been mirrored by many witnesses I've spoken with. It will be interesting to see if we actually end up delaying this update because of this bundled approach. Point by point, here's where my thoughts are... 1. **Reduce inflation to 9.5%/year**: I'm on board. The 9.5% might be low, but I think it'll be great to swing from one extreme to the other for a while. 2. **Allocate 75% of the created Steem to the Reward Fund**: Agreed. 3. **Allocate 15% of the created Steem to the Vesting Fund as interest on Steem Power**: Agreed. 4. **Allocate 10% of the created Steem to the Witnesses**: Agreed. Though I do think the reduction in witness pay might cause financial danger to the project's witnesses (myself included) support. If that means alternate financing must be sought, so be it. Reducing the amount of inflation is more important. 5. **Increase backup witness's pay**: Neutral. If you look at it from the infrastructure point of view, backup witnesses aren't as important for block production simply because they don't produce as much. Beyond just producing blocks, I do believe there are people outside of the 19 that deserve funding. The mentality right now seems to be that witness funding isn't meant for funding projects (which I also disagree with). Overall - increasing the amount backup witnesses get paid, while decreasing the amount primary witnesses receive seems counter intuitive. I won't stand in the way of this change though, I just don't know what it solves. 6. **Increase miner's pay**: Currently against. The mining queue is dominated by 2 people because they aren't sharing the software, and that doesn't add much value to the network. Mining is about decentralization, and two miners isn't decentralized. I will support an increase in mining rewards if we change to a more open algorithm where everyone can GPU mine (Equihash?). 7. **Witnesses and miners would be paid in STEEM rather than Steem Power**: Current against for miners, due to the same reasons above. I am willing to support this shift once we have a better POW system. Overall though, I do like the idea of mining/witness rewards being paid in a liquid fund, it just doesn't make sense now. 8. **Votes for witnesses would expire after 3 months**: Against, it doesn't solve any problems. If this happens, I'm just going to setup a bot to renew my votes... which in turn will just create excess traffic on the blockchain. It solves nothing, as anyone with significant vote weight will likely do the same. 9. **Reducing the Steem Power holding period to a minimum of 3 months**: Agreed, and almost the exact same thoughts as I wrote in #1. It might be a little too short, but I'm willing to see how it plays out and adjust accordingly. From what I understand is this will be a witness parameter, which means it'll be easy enough to change. 10. **Reduce the SBD delay from 7 days to 3 (or 3.5) days**: Agreed. Most of my objections right now involve the mining queue, simply because the changes benefit two people specifically (rabbit/supercomputing). I don't know why we would make a change that benefits them, and no one else. I'd go so far as to say I agree with @joseph, and I wouldn't even mind if POW mining was removed until a more decentralized solution was put in place. Overall, these are a great set of changes to alter the rate of inflation and hopefully create some confidence in the economy. It'll be an interesting few weeks as we all continue discussing these changes and the impact they have for steem! ## 4. Previous week's update [Update for the week ending 2016-10-30](https://steemit.com/witness-category/@jesta/jesta-witness-update-2016-10-30) ### [Finally, don't forget to vote for witnesses here.](https://steemit.com/~witnesses)
post[json_metadata]
[tags]
[0] witness-category
[1] witness-update
[users]
[0] abit
[1] joseph
[links]
[0] https://steemdb.com/witnesses/history
[1] https://steemit.com/witness-category/@jesta/jesta-witness-update-2016-10-30
[2] https://steemit.com/~witnesses
[app] steemit/0.1
[format] markdown
post[last_update] 2016-11-12T04:33:27
post[created] 2016-11-12T04:32:33
post[active] 2016-11-13T21:38:09
post[last_payout] 2016-12-13T05:56:06
post[depth] 0
post[children] 20
post[children_rshares2] 0
post[net_rshares] 0
post[abs_rshares] 0
post[vote_rshares] 0
post[children_abs_rshares] 0
post[cashout_time] 1969-12-31T23:59:59
post[max_cashout_time] 1969-12-31T23:59:59
post[total_vote_weight] 0
post[reward_weight] 10000
post[total_payout_value] 74.613 SBD
post[curator_payout_value] 5.049 SBD
post[author_rewards] 557771
post[net_votes] 467
post[root_comment] 1347596
post[max_accepted_payout] 1000000.000 SBD
post[percent_steem_dollars] 0
post[allow_replies] 1
post[allow_votes] 1
post[allow_curation_rewards] 1
post[beneficiaries]
post[url] /witness-category/@jesta/jesta-witness-update-2016-11-11
post[root_title] jesta witness update - 2016-11-11
post[pending_payout_value] 0.000 SBD
post[total_pending_payout_value] 0.000 STEEM
post[active_votes]
post[replies]
post[author_reputation] 71627050027202
post[promoted] 0.000 SBD
post[body_length] 0
post[reblogged_by]
post[html] <p>I think I'm planning on sticking to these updates at bi-weekly rate for now, since last week I didn't have much interesting to report and was pretty busy. This week, with next week's upcoming changes, I felt it was a good time to chime in.</p> <h2>1. Accomplished the week of 2016-11-11:</h2> <ul><li>Upgraded all the steem.ws/witness/seed steem servers to 0.15.0</li> <li>I've started migrating steemdb to a better server, and it will now use it's own private steem instance for increased speed.</li> <li>The new greymass.com website is now running on an optimized setup of reprint. It's no where near finished in terms of layout/design/pages, but I'm almost at the point where I can say the server infrastructure is good and will scale well.</li> <li>I have started slowly talking to a few people who want reprint websites, and plan on using these sites as our proof of concept. We also have our own slack now to specifically keep topics on track for greymass/reprint.</li> <li>Fixed an issue with how proxy votes were tallied on steemdb (thanks @abit!)</li> <li>Added <a href="https://steemdb.com/witnesses/history">global witness voting history</a> to steemdb.</li> <li>Explored Google/AWS/Docker/Kubernetes versions of container solutions for use within a large multi-site reprint installation.</li> <li>Lots of discussions about the upcoming inflation changes (I'll go into my thoughts below)</li> </ul><h2>2. Upcoming projects/goals</h2> <ul><li>Right now I'm working on a steemdb plugin for reprint. This plugin will allow anyone with a reprint site to pull data via a plugin/api in ways the blockchain currently doesn't allow for (optimally).</li> <li>Expand the steemphp library to include more different types of information.</li> <li>Continue development of reprint, and launch the greymass.com site as something I'm happy with. </li> <li>A day or two will be set aside for the 0.16.0 fork coming soon. Currently I have 8-10 steemd servers running at any given moment, and I discovered this week that upgrading all of these servers takes a bit of time!</li> </ul><h2>3. Thoughts from this week</h2> <p>Major changes on the horizon in terms of the steem economy, and I for one am glad we're seeing some progress. However, I don't like the fact that there are so many unrelated changes all being bundled into a single update. This sentiment has been mirrored by many witnesses I've spoken with. It will be interesting to see if we actually end up delaying this update because of this bundled approach.</p> <p>Point by point, here's where my thoughts are...</p> <ol><li><strong>Reduce inflation to 9.5%/year</strong>: I'm on board. The 9.5% might be low, but I think it'll be great to swing from one extreme to the other for a while. </li> <li><strong>Allocate 75% of the created Steem to the Reward Fund</strong>: Agreed.</li> <li><strong>Allocate 15% of the created Steem to the Vesting Fund as interest on Steem Power</strong>: Agreed.</li> <li><strong>Allocate 10% of the created Steem to the Witnesses</strong>: Agreed. Though I do think the reduction in witness pay might cause financial danger to the project's witnesses (myself included) support. If that means alternate financing must be sought, so be it. Reducing the amount of inflation is more important.</li> <li><strong>Increase backup witness's pay</strong>: Neutral. If you look at it from the infrastructure point of view, backup witnesses aren't as important for block production simply because they don't produce as much. Beyond just producing blocks, I do believe there are people outside of the 19 that deserve funding. The mentality right now seems to be that witness funding isn't meant for funding projects (which I also disagree with). Overall - increasing the amount backup witnesses get paid, while decreasing the amount primary witnesses receive seems counter intuitive. I won't stand in the way of this change though, I just don't know what it solves.</li> <li><strong>Increase miner's pay</strong>: Currently against. The mining queue is dominated by 2 people because they aren't sharing the software, and that doesn't add much value to the network. Mining is about decentralization, and two miners isn't decentralized. I will support an increase in mining rewards if we change to a more open algorithm where everyone can GPU mine (Equihash?).</li> <li><strong>Witnesses and miners would be paid in STEEM rather than Steem Power</strong>: Current against for miners, due to the same reasons above. I am willing to support this shift once we have a better POW system. Overall though, I do like the idea of mining/witness rewards being paid in a liquid fund, it just doesn't make sense now.</li> <li><strong>Votes for witnesses would expire after 3 months</strong>: Against, it doesn't solve any problems. If this happens, I'm just going to setup a bot to renew my votes... which in turn will just create excess traffic on the blockchain. It solves nothing, as anyone with significant vote weight will likely do the same.</li> <li><strong>Reducing the Steem Power holding period to a minimum of 3 months</strong>: Agreed, and almost the exact same thoughts as I wrote in #1. It might be a little too short, but I'm willing to see how it plays out and adjust accordingly. From what I understand is this will be a witness parameter, which means it'll be easy enough to change.</li> <li><strong>Reduce the SBD delay from 7 days to 3 (or 3.5) days</strong>: Agreed.</li> </ol><p>Most of my objections right now involve the mining queue, simply because the changes benefit two people specifically (rabbit/supercomputing). I don't know why we would make a change that benefits them, and no one else. I'd go so far as to say I agree with @joseph, and I wouldn't even mind if POW mining was removed until a more decentralized solution was put in place.</p> <p>Overall, these are a great set of changes to alter the rate of inflation and hopefully create some confidence in the economy. It'll be an interesting few weeks as we all continue discussing these changes and the impact they have for steem!</p> <h2>4. Previous week's update</h2> <p><a href="https://steemit.com/witness-category/@jesta/jesta-witness-update-2016-10-30">Update for the week ending 2016-10-30</a></p> <h3><a href="https://steemit.com/~witnesses">Finally, don't forget to vote for witnesses here.</a></h3>
post[html_preview] <p>I think I'm planning on sticking to these updates at bi-weekly rate for now, since last week I didn't have much interesting to report and was pretty busy. This week, with next week's upcoming changes, I felt it was a good time to chime in.</p>1. Accomplished the week of 2016-11-11:
post[image]
post[ts] 1478946753
jesta witness update - 2016-10-30
2016-10-31 | Tags: [witness-category] [witness-update]
links
Blog URL /witness-category/@jesta/jesta-witness-update-2016-10-30
Steemit URL https://steemit.com/witness-category/@jesta/jesta-witness-update-2016-10-30
SteemDB URL https://steemdb.com/witness-category/@jesta/jesta-witness-update-2016-10-30
comment model

      Twig Examples:

      {{ post.title }}
      {{ post.author }}
      {{ post.body }}
    
post[id] 1272980
post[author] jesta
post[permlink] jesta-witness-update-2016-10-30
post[category] witness-category
post[parent_author]
post[parent_permlink] witness-category
post[title] jesta witness update - 2016-10-30
post[body] Apologies for missing my update last week! I ended up getting lost in a few projects (and a few games). If I do miss an update I apologize, once a week is a lot more of a commitment than I originally anticipated :) ## 1. Recently accomplished: - Golos launched, and I ended up setting up a decent amount of services to support their launch. [golosdb.com](https://golosdb.com) and [golos.ws](https://golos.ws) are both running now. - Released an alpha of [steemphp](https://github.com/greymass/steemphp), a PHP library for interacting with steem. - Implemented steemphp in [Reprint](https://github.com/greymass/steemphp). The abstraction between the two still needs to be worked out a bit more. - Created test environments for high performance Reprint installations. Page load times are now sub 200ms, still a bit more room for improvement. - Created a [chart to track rewards on steem](https://steemdb.com/charts/rewards) over the last 90 days. Also added a bit more data to the block pages. - Researched a lot of different DNS solutions for steem.ws - haven't been able to find anything that fits our needs. I basically am looking for a latency based dns load balancing solution, one that has nodes worldwide. We use AWS right now for this, but AWS doesn't have datacenters everywhere. - Found a way to make steemdb update a lot more regularly - still needs full implementation. - Lots of work on the steem.ws cluster - I've actually migrated over to all new hosts as of today. Sorry about the downtime! - Migrated all of my utility scripts over to a Raspberry Pi running a docker host. Each script is it's own little container. Currently running 3 scripts, and it looks like I could probably run hundreds of these small utilities from it. Low cost way to keep them running! - Continued progress on where @greymass is heading. ## 2. Upcoming projects/goals - Try out the new [chainbase implementation of steem]() - Continue development on steemphp - there are still a lot more methods that need to be covered and tested. - Continue development on Reprint - the core engine is getting close to complete! - Implement more rapid sync scripts on steemdb ## 3. Thoughts from this week The last two weeks have been somewhat of a blur, I haven't had much time to think about anything except for the tasks on my todo list. The biggest steps forward I think I'm making right now is with the abstraction of steem into [steemphp](https://github.com/greymass/steemphp). I'm pretty pleased with the direction it's heading and the way it's all setup. The entire codebase is covered by PHPUnit test cases, which are run via travis/coveralls everytime code is added to the github repository. You can check on the status of these two things here: - [https://travis-ci.org/greymass/steemphp](https://travis-ci.org/greymass/steemphp) - [https://coveralls.io/github/greymass/steemphp?branch=master](https://coveralls.io/github/greymass/steemphp?branch=master) This library should hopefully prove useful for anyone building PHP based applications with the intention of accessing the steem blockchain. The package itself is available [via composer](https://packagist.org/packages/greymass/steemphp) which should make it a breeze to include in any modern project. ## 4. Previous week's update [Update for the week ending 2016-10-14](https://steemdb.com/witness-category/@jesta/jesta-witness-update-2016-10-16) ### [Finally, don't forget to vote for witnesses here.](https://steemit.com/~witnesses)
post[json_metadata]
[tags]
[0] witness-category
[1] witness-update
[users]
[0] greymass
[links]
[0] https://golosdb.com
[1] https://golos.ws
[2] https://github.com/greymass/steemphp
[3] https://steemdb.com/charts/rewards
[4] https://travis-ci.org/greymass/steemphp
[5] https://coveralls.io/github/greymass/steemphp?branch=master
[6] https://packagist.org/packages/greymass/steemphp
[7] https://steemdb.com/witness-category/@jesta/jesta-witness-update-2016-10-16
[8] https://steemit.com/~witnesses
post[last_update] 2016-10-31T03:20:54
post[created] 2016-10-31T03:20:54
post[active] 2016-11-05T12:50:18
post[last_payout] 2016-12-01T04:51:39
post[depth] 0
post[children] 20
post[children_rshares2] 0
post[net_rshares] 0
post[abs_rshares] 0
post[vote_rshares] 0
post[children_abs_rshares] 0
post[cashout_time] 1969-12-31T23:59:59
post[max_cashout_time] 1969-12-31T23:59:59
post[total_vote_weight] 0
post[reward_weight] 10000
post[total_payout_value] 141.709 SBD
post[curator_payout_value] 4.361 SBD
post[author_rewards] 1101962
post[net_votes] 413
post[root_comment] 1272980
post[max_accepted_payout] 1000000.000 SBD
post[percent_steem_dollars] 0
post[allow_replies] 1
post[allow_votes] 1
post[allow_curation_rewards] 1
post[beneficiaries]
post[url] /witness-category/@jesta/jesta-witness-update-2016-10-30
post[root_title] jesta witness update - 2016-10-30
post[pending_payout_value] 0.000 SBD
post[total_pending_payout_value] 0.000 STEEM
post[active_votes]
post[replies]
post[author_reputation] 71627050027202
post[promoted] 0.000 SBD
post[body_length] 0
post[reblogged_by]
post[html] <p>Apologies for missing my update last week! I ended up getting lost in a few projects (and a few games). If I do miss an update I apologize, once a week is a lot more of a commitment than I originally anticipated :)</p> <h2>1. Recently accomplished:</h2> <ul><li>Golos launched, and I ended up setting up a decent amount of services to support their launch. <a href="https://golosdb.com">golosdb.com</a> and <a href="https://golos.ws">golos.ws</a> are both running now.</li> <li>Released an alpha of <a href="https://github.com/greymass/steemphp">steemphp</a>, a PHP library for interacting with steem.</li> <li>Implemented steemphp in <a href="https://github.com/greymass/steemphp">Reprint</a>. The abstraction between the two still needs to be worked out a bit more.</li> <li>Created test environments for high performance Reprint installations. Page load times are now sub 200ms, still a bit more room for improvement.</li> <li>Created a <a href="https://steemdb.com/charts/rewards">chart to track rewards on steem</a> over the last 90 days. Also added a bit more data to the block pages.</li> <li>Researched a lot of different DNS solutions for steem.ws - haven't been able to find anything that fits our needs. I basically am looking for a latency based dns load balancing solution, one that has nodes worldwide. We use AWS right now for this, but AWS doesn't have datacenters everywhere.</li> <li>Found a way to make steemdb update a lot more regularly - still needs full implementation.</li> <li>Lots of work on the steem.ws cluster - I've actually migrated over to all new hosts as of today. Sorry about the downtime!</li> <li>Migrated all of my utility scripts over to a Raspberry Pi running a docker host. Each script is it's own little container. Currently running 3 scripts, and it looks like I could probably run hundreds of these small utilities from it. Low cost way to keep them running!</li> <li>Continued progress on where @greymass is heading.</li> </ul><h2>2. Upcoming projects/goals</h2> <ul><li>Try out the new <a href="">chainbase implementation of steem</a></li> <li>Continue development on steemphp - there are still a lot more methods that need to be covered and tested.</li> <li>Continue development on Reprint - the core engine is getting close to complete!</li> <li>Implement more rapid sync scripts on steemdb</li> </ul><h2>3. Thoughts from this week</h2> <p>The last two weeks have been somewhat of a blur, I haven't had much time to think about anything except for the tasks on my todo list.</p> <p>The biggest steps forward I think I'm making right now is with the abstraction of steem into <a href="https://github.com/greymass/steemphp">steemphp</a>. I'm pretty pleased with the direction it's heading and the way it's all setup. The entire codebase is covered by PHPUnit test cases, which are run via travis/coveralls everytime code is added to the github repository. You can check on the status of these two things here:</p> <ul><li><a href="https://travis-ci.org/greymass/steemphp">https://travis-ci.org/greymass/steemphp</a></li> <li><a href="https://coveralls.io/github/greymass/steemphp?branch=master">https://coveralls.io/github/greymass/steemphp?branch=master</a></li> </ul><p>This library should hopefully prove useful for anyone building PHP based applications with the intention of accessing the steem blockchain. The package itself is available <a href="https://packagist.org/packages/greymass/steemphp">via composer</a> which should make it a breeze to include in any modern project.</p> <h2>4. Previous week's update</h2> <p><a href="https://steemdb.com/witness-category/@jesta/jesta-witness-update-2016-10-16">Update for the week ending 2016-10-14</a></p> <h3><a href="https://steemit.com/~witnesses">Finally, don't forget to vote for witnesses here.</a></h3>
post[html_preview] <p>Apologies for missing my update last week! I ended up getting lost in a few projects (and a few games). If I do miss an update I apologize, once a week is a lot more of a commitment than I originally anticipated :)</p>Golos launched, and I ended up setting up a decent amount of services to support their launch. golosdb.com and golos.ws are both running now. Released an alpha of steemphp, a PHP library for interacting with steem. Implemented steemphp in Reprint. The abstraction between the two still needs to be worked out a bit more. Created test environments for high performance Reprint installations. Page load times are now sub 200ms, still a bit more room for improvement. Created a chart to track rewards on steem over the last 90 days. Also added a bit more data to the block pages. Researched a lot of different DNS solutions for steem.ws - haven't been able to find anything that fits our needs. I basically am looking for a latency based dns load balancing solution, one that has nodes worldwide. We use AWS right now for this, but AWS doesn't have datacenters everywhere. Found a way to make steemdb update a lot more regularly - still needs full implementation. Lots of work on the steem.ws cluster - I've actually migrated over to all new hosts as of today. Sorry about the downtime! Migrated all of my utility scripts over to a Raspberry Pi running a docker host. Each script is it's own little container. Currently running 3 scripts, and it looks like I could probably run hundreds of these small utilities from it. Low cost way to keep them running! Continued progress on where @greymass is heading.
post[image]
post[ts] 1477902054
jesta witness update - 2016-10-16
2016-10-17 | Tags: [witness-category] [witness-update]
links
Blog URL /witness-category/@jesta/jesta-witness-update-2016-10-16
Steemit URL https://steemit.com/witness-category/@jesta/jesta-witness-update-2016-10-16
SteemDB URL https://steemdb.com/witness-category/@jesta/jesta-witness-update-2016-10-16
comment model

      Twig Examples:

      {{ post.title }}
      {{ post.author }}
      {{ post.body }}
    
post[id] 1193167
post[author] jesta
post[permlink] jesta-witness-update-2016-10-16
post[category] witness-category
post[parent_author]
post[parent_permlink] witness-category
post[title] jesta witness update - 2016-10-16
post[body] It's been a long time since I've been this busy, but a lot to show for it. Almost every project I'm touching, personal and @greymass related, all received attention this week. Apologies to everyone if over the past 2-3 days I've been unresponsive, I needed a bit of downtime! ## 1. Accomplished the week of 2016-10-16: - Released two steemdb updates, [0.4.0 - rich account history](https://steemit.com/steemdb/@jesta/steemdb-0-4-0-a-rich-history-for-every-account) and [0.4.1 - curation/author leaderboards](https://steemit.com/steemdb/@jesta/steemdb-0-4-1-daily-curation-and-author-leaderboards). - Worked with @paxmagnus and wrote two @greymass posts: - [Greymass - Crowdfunding campaign details](https://steemit.com/greymass/@greymass/greymass-crowdfunding-campaign-details) - [Reprint - Build your blog or website on the blockchain](https://steemit.com/reprint/@greymass/reprint-build-your-blog-or-website-on-the-blockchain) - Worked on the `develop` branch of [greymass/reprint](https://github.com/greymass/reprint). Migrated almost all of the initial code from steempress. Upgraded the entire foundation of the application to symfony2 + silex2. - Created the [greymass/reprint-starter](https://github.com/greymass/reprint-starter) which will act as the starting point of new reprint projects. - Created [greymass.com](http://greymass.com) using the reprint-starter package with a basic semantic-ui theme as the basis of our website. - Started looking into what Golos is doing since it's launching next week. The testnet is running at this point, so I started researching what it would take to migrate some of my projects over to support golos as well. - [golos.steemdb.com](http://golos.steemdb.com) is now running. Not all features are enabled yet (some of the newest), but it turns out it was a pretty easy migration. - [golos.steemstats.com](http://golos.steemstats.com) is **sort of** running. Still some issues, no currencies have been localized. This one will be a bit more tough to migrate over since it's a bit more complicated. - Setup [golos.steem.ws](http://golos.steem.ws) as a public golos node. ## 2. Upcoming projects/goals - This week golos launches, I will be available for it's launch as well as resetting all the services I maintain to help how I can for a smooth launch. - [greymass/reprint](https://github.com/greymass/reprint) will be the focus of my development activities. On my plate immediately is removing the steemd components and migrating them into their own library for other projects to use. This week's focus is on it's core engine and ensuring it's structured the best it can be. - I just purchased a new Raspberry Pi 3 and am setting it up to run some of the scripts I use to help maintain my corner of the steem network. Network status, block-miss monitoring, and a few other features will be deployed onto this device. - This week I'll be writing a post about the roadmap for [greymass/reprint](https://github.com/greymass/reprint) and our development schedule. - The first two websites powered by reprint are in development, hopefully we will be announcing one this week. ## 3. Thoughts from this week I have been thinking a lot about golos this week and it's approach to building a brand new graphene based social network. While I don't really agree with the fact that it's a new blockchain, having a second blockchain has somewhat opened my eyes to some of the potential we have here. The things we build here are compatible with other potential networks that use the same technology (to a degree). That's pretty amazing. Almost every script we have created in this community now can be used (with little modification) on a completely separate blockchain and site. As this ecosystem of graphene based applications continues to grow and splinter off into it's own use cases, we are continually adding value to these products we create. The number of compatible blockchains multiplies the value of everything we're working for here and helps validate those that came before it. While I've been outspoken in the past, I'm looking forward to seeing many new applications adopting this technology! ## 4. Previous week's update [Update for the week ending 2016-10-07](https://steemit.com/witness-category/@jesta/jesta-witness-update-full-time-begins-2016-10-07) ### [Finally, don't forget to vote for witnesses here.](https://steemit.com/~witnesses)
post[json_metadata]
[tags]
[0] witness-category
[1] witness-update
[users]
[0] greymass
[1] paxmagnus
[links]
[0] https://steemit.com/steemdb/@jesta/steemdb-0-4-0-a-rich-history-for-every-account
[1] https://steemit.com/steemdb/@jesta/steemdb-0-4-1-daily-curation-and-author-leaderboards
[2] https://steemit.com/greymass/@greymass/greymass-crowdfunding-campaign-details
[3] https://steemit.com/reprint/@greymass/reprint-build-your-blog-or-website-on-the-blockchain
[4] https://github.com/greymass/reprint
[5] https://github.com/greymass/reprint-starter
[6] http://greymass.com
[7] http://golos.steemdb.com
[8] http://golos.steemstats.com
[9] http://golos.steem.ws
[10] https://steemit.com/witness-category/@jesta/jesta-witness-update-full-time-begins-2016-10-07
[11] https://steemit.com/~witnesses
post[last_update] 2016-10-17T02:57:15
post[created] 2016-10-17T02:57:15
post[active] 2016-10-18T15:54:03
post[last_payout] 2016-11-17T05:21:42
post[depth] 0
post[children] 17
post[children_rshares2] 0
post[net_rshares] 0
post[abs_rshares] 0
post[vote_rshares] 0
post[children_abs_rshares] 0
post[cashout_time] 1969-12-31T23:59:59
post[max_cashout_time] 1969-12-31T23:59:59
post[total_vote_weight] 0
post[reward_weight] 10000
post[total_payout_value] 223.129 SBD
post[curator_payout_value] 10.276 SBD
post[author_rewards] 929708
post[net_votes] 438
post[root_comment] 1193167
post[max_accepted_payout] 1000000.000 SBD
post[percent_steem_dollars] 0
post[allow_replies] 1
post[allow_votes] 1
post[allow_curation_rewards] 1
post[beneficiaries]
post[url] /witness-category/@jesta/jesta-witness-update-2016-10-16
post[root_title] jesta witness update - 2016-10-16
post[pending_payout_value] 0.000 SBD
post[total_pending_payout_value] 0.000 STEEM
post[active_votes]
post[replies]
post[author_reputation] 71627050027202
post[promoted] 0.000 SBD
post[body_length] 0
post[reblogged_by]
post[html] <p>It's been a long time since I've been this busy, but a lot to show for it. Almost every project I'm touching, personal and @greymass related, all received attention this week. Apologies to everyone if over the past 2-3 days I've been unresponsive, I needed a bit of downtime!</p> <h2>1. Accomplished the week of 2016-10-16:</h2> <ul><li>Released two steemdb updates, <a href="https://steemit.com/steemdb/@jesta/steemdb-0-4-0-a-rich-history-for-every-account">0.4.0 - rich account history</a> and <a href="https://steemit.com/steemdb/@jesta/steemdb-0-4-1-daily-curation-and-author-leaderboards">0.4.1 - curation/author leaderboards</a>.</li> <li>Worked with @paxmagnus and wrote two @greymass posts: <ul><li><a href="https://steemit.com/greymass/@greymass/greymass-crowdfunding-campaign-details">Greymass - Crowdfunding campaign details</a></li> <li><a href="https://steemit.com/reprint/@greymass/reprint-build-your-blog-or-website-on-the-blockchain">Reprint - Build your blog or website on the blockchain</a></li> </ul></li> <li>Worked on the <code>develop</code> branch of <a href="https://github.com/greymass/reprint">greymass/reprint</a>. Migrated almost all of the initial code from steempress. Upgraded the entire foundation of the application to symfony2 + silex2.</li> <li>Created the <a href="https://github.com/greymass/reprint-starter">greymass/reprint-starter</a> which will act as the starting point of new reprint projects.</li> <li>Created <a href="http://greymass.com">greymass.com</a> using the reprint-starter package with a basic semantic-ui theme as the basis of our website.</li> <li>Started looking into what Golos is doing since it's launching next week. The testnet is running at this point, so I started researching what it would take to migrate some of my projects over to support golos as well.</li> <li><a href="http://golos.steemdb.com">golos.steemdb.com</a> is now running. Not all features are enabled yet (some of the newest), but it turns out it was a pretty easy migration.</li> <li><a href="http://golos.steemstats.com">golos.steemstats.com</a> is <strong>sort of</strong> running. Still some issues, no currencies have been localized. This one will be a bit more tough to migrate over since it's a bit more complicated.</li> <li>Setup <a href="http://golos.steem.ws">golos.steem.ws</a> as a public golos node.</li> </ul><h2>2. Upcoming projects/goals</h2> <ul><li>This week golos launches, I will be available for it's launch as well as resetting all the services I maintain to help how I can for a smooth launch.</li> <li><a href="https://github.com/greymass/reprint">greymass/reprint</a> will be the focus of my development activities. On my plate immediately is removing the steemd components and migrating them into their own library for other projects to use. This week's focus is on it's core engine and ensuring it's structured the best it can be.</li> <li>I just purchased a new Raspberry Pi 3 and am setting it up to run some of the scripts I use to help maintain my corner of the steem network. Network status, block-miss monitoring, and a few other features will be deployed onto this device.</li> <li>This week I'll be writing a post about the roadmap for <a href="https://github.com/greymass/reprint">greymass/reprint</a> and our development schedule.</li> <li>The first two websites powered by reprint are in development, hopefully we will be announcing one this week.</li> </ul><h2>3. Thoughts from this week</h2> <p>I have been thinking a lot about golos this week and it's approach to building a brand new graphene based social network. While I don't really agree with the fact that it's a new blockchain, having a second blockchain has somewhat opened my eyes to some of the potential we have here.</p> <p>The things we build here are compatible with other potential networks that use the same technology (to a degree). That's pretty amazing. Almost every script we have created in this community now can be used (with little modification) on a completely separate blockchain and site.</p> <p>As this ecosystem of graphene based applications continues to grow and splinter off into it's own use cases, we are continually adding value to these products we create. The number of compatible blockchains multiplies the value of everything we're working for here and helps validate those that came before it.</p> <p>While I've been outspoken in the past, I'm looking forward to seeing many new applications adopting this technology!</p> <h2>4. Previous week's update</h2> <p><a href="https://steemit.com/witness-category/@jesta/jesta-witness-update-full-time-begins-2016-10-07">Update for the week ending 2016-10-07</a></p> <h3><a href="https://steemit.com/~witnesses">Finally, don't forget to vote for witnesses here.</a></h3>
post[html_preview] <p>It's been a long time since I've been this busy, but a lot to show for it. Almost every project I'm touching, personal and @greymass related, all received attention this week. Apologies to everyone if over the past 2-3 days I've been unresponsive, I needed a bit of downtime!</p>1. Accomplished the week of 2016-10-16:
post[image]
post[ts] 1476691035
steemdb 0.4.1 - daily curation and author leaderboards
2016-10-11 | Tags: [steemdb] [patch-notes]
links
Blog URL /steemdb/@jesta/steemdb-0-4-1-daily-curation-and-author-leaderboards
Steemit URL https://steemit.com/steemdb/@jesta/steemdb-0-4-1-daily-curation-and-author-leaderboards
SteemDB URL https://steemdb.com/steemdb/@jesta/steemdb-0-4-1-daily-curation-and-author-leaderboards
comment model

      Twig Examples:

      {{ post.title }}
      {{ post.author }}
      {{ post.body }}
    
post[id] 1157872
post[author] jesta
post[permlink] steemdb-0-4-1-daily-curation-and-author-leaderboards
post[category] steemdb
post[parent_author]
post[parent_permlink] steemdb
post[title] steemdb 0.4.1 - daily curation and author leaderboards
post[body] A quick update following [yesterday's 0.4.0 release](https://steemit.com/steemdb/@jesta/steemdb-0-4-0-a-rich-history-for-every-account), today we have rewards leaderboards! # Leaderboards Have you ever wondered who earned the most rewards on a specific day? This new section of [steemdb.com](https://steemdb.com) (located under the [labs section](https://steemdb.com/labs)) lets you browse through the history of Curation and Author rewards by day and find those who earned the most. You can use the date navigation right above that section to go back and forward to different dates. These pages use the **payout/reward date** of the post, not the post date itself. ## Author Leaderboard ![Author](https://steemdb.com/examples/steemdb-leaderboard-author.png) URL: https://steemdb.com/labs/author The **Author Leaderboard** shows you which authors have earned the most on any given day by the posts and comments they write. All 3 currencies are displayed, as well as the number of posts that author made. ## Curation Leaderboard ![Curation](https://steemdb.com/examples/steemdb-leaderboard-curation.png) URL: https://steemdb.com/labs/curation The **Curation Leaderboard** shows you which curators earned the most on any given day. The VEST and SP earned from curation is displayed, the number of curation rewards they earned that day, as well as how many unique authors they ended up voting for. ## Where does this go from here? I have a lot of fun stats planned for this type of data, with this release in the **Labs** section being the first. Going forward, I plan on adding a weekly summary, monthly summary, as well as an all-time leaderboard to show who has earned the most overall in their various activities. If you're interested in learning how this is done, I'd recommend checking out @aizensou's post about [Customize Payout Leaderboard Stats for Steem](https://steemit.com/stats/@aizensou/customize-payouts-leaderboards-stats-for-steem-network). The work both of us have done around this subject is derived from a patch @arhag made for steem last week.
post[json_metadata]
[tags]
[0] steemdb
[1] patch-notes
[users]
[0] aizensou
[1] arhag
[image]
[0] https://steemdb.com/examples/steemdb-leaderboard-author.png
[1] https://steemdb.com/examples/steemdb-leaderboard-curation.png
[links]
[0] https://steemit.com/steemdb/@jesta/steemdb-0-4-0-a-rich-history-for-every-account
[1] https://steemdb.com
[2] https://steemdb.com/labs
[3] https://steemdb.com/labs/author
[4] https://steemdb.com/labs/curation
[5] https://steemit.com/stats/@aizensou/customize-payouts-leaderboards-stats-for-steem-network
post[last_update] 2016-10-11T21:49:06
post[created] 2016-10-11T21:31:00
post[active] 2016-10-13T09:19:15
post[last_payout] 2016-11-12T03:45:15
post[depth] 0
post[children] 18
post[children_rshares2] 0
post[net_rshares] 0
post[abs_rshares] 0
post[vote_rshares] 0
post[children_abs_rshares] 0
post[cashout_time] 1969-12-31T23:59:59
post[max_cashout_time] 1969-12-31T23:59:59
post[total_vote_weight] 0
post[reward_weight] 10000
post[total_payout_value] 278.968 SBD
post[curator_payout_value] 28.387 SBD
post[author_rewards] 845360
post[net_votes] 442
post[root_comment] 1157872
post[max_accepted_payout] 1000000.000 SBD
post[percent_steem_dollars] 0
post[allow_replies] 1
post[allow_votes] 1
post[allow_curation_rewards] 1
post[beneficiaries]
post[url] /steemdb/@jesta/steemdb-0-4-1-daily-curation-and-author-leaderboards
post[root_title] steemdb 0.4.1 - daily curation and author leaderboards
post[pending_payout_value] 0.000 SBD
post[total_pending_payout_value] 0.000 STEEM
post[active_votes]
post[replies]
post[author_reputation] 71627050027202
post[promoted] 0.000 SBD
post[body_length] 0
post[reblogged_by]
post[html] <p>A quick update following <a href="https://steemit.com/steemdb/@jesta/steemdb-0-4-0-a-rich-history-for-every-account">yesterday's 0.4.0 release</a>, today we have rewards leaderboards!</p> <h1>Leaderboards</h1> <p>Have you ever wondered who earned the most rewards on a specific day? This new section of <a href="https://steemdb.com">steemdb.com</a> (located under the <a href="https://steemdb.com/labs">labs section</a>) lets you browse through the history of Curation and Author rewards by day and find those who earned the most.</p> <p>You can use the date navigation right above that section to go back and forward to different dates.</p> <p>These pages use the <strong>payout/reward date</strong> of the post, not the post date itself.</p> <h2>Author Leaderboard</h2> <p><img src="https://steemdb.com/examples/steemdb-leaderboard-author.png" alt="Author" /></p> <p>URL: https://steemdb.com/labs/author</p> <p>The <strong>Author Leaderboard</strong> shows you which authors have earned the most on any given day by the posts and comments they write. All 3 currencies are displayed, as well as the number of posts that author made.</p> <h2>Curation Leaderboard</h2> <p><img src="https://steemdb.com/examples/steemdb-leaderboard-curation.png" alt="Curation" /></p> <p>URL: https://steemdb.com/labs/curation</p> <p>The <strong>Curation Leaderboard</strong> shows you which curators earned the most on any given day. The VEST and SP earned from curation is displayed, the number of curation rewards they earned that day, as well as how many unique authors they ended up voting for.</p> <h2>Where does this go from here?</h2> <p>I have a lot of fun stats planned for this type of data, with this release in the <strong>Labs</strong> section being the first. Going forward, I plan on adding a weekly summary, monthly summary, as well as an all-time leaderboard to show who has earned the most overall in their various activities.</p> <p>If you're interested in learning how this is done, I'd recommend checking out @aizensou's post about <a href="https://steemit.com/stats/@aizensou/customize-payouts-leaderboards-stats-for-steem-network">Customize Payout Leaderboard Stats for Steem</a>. The work both of us have done around this subject is derived from a patch @arhag made for steem last week.</p>
post[html_preview] <p>A quick update following yesterday's 0.4.0 release, today we have rewards leaderboards!</p><p>Have you ever wondered who earned the most rewards on a specific day? This new section of steemdb.com (located under the labs section) lets you browse through the history of Curation and Author rewards by day and find those who earned the most.</p>
post[image] https://steemdb.com/examples/steemdb-leaderboard-author.png
post[ts] 1476239460
steemdb 0.4.0 - a rich history for every account
2016-10-10 | Tags: [steemdb] [patch-notes]
links
Blog URL /steemdb/@jesta/steemdb-0-4-0-a-rich-history-for-every-account
Steemit URL https://steemit.com/steemdb/@jesta/steemdb-0-4-0-a-rich-history-for-every-account
SteemDB URL https://steemdb.com/steemdb/@jesta/steemdb-0-4-0-a-rich-history-for-every-account
comment model

      Twig Examples:

      {{ post.title }}
      {{ post.author }}
      {{ post.body }}
    
post[id] 1145419
post[author] jesta
post[permlink] steemdb-0-4-0-a-rich-history-for-every-account
post[category] steemdb
post[parent_author]
post[parent_permlink] steemdb
post[title] steemdb 0.4.0 - a rich history for every account
post[body] This is probably my favorite set of features (to date) working on this project - it answers so many questions I've had about my account's history I couldn't find elsewhere! In the 0.4.0 release of [steemdb.com](https://steemdb.com), new key features include `curation reward history`, `author reward history`, `transfer history`, `power up history` and `power down history`. These features are available for any account, just visit [steemdb.com](https://steemdb.com) and search for your account using the search bar on the top, and use the sub navigation to find different aspects of your account. Before I go any further, **a huge thank you to @arhag, who helped me gather this information by [developing a modified version of steemd](https://github.com/arhag/steem/commit/fa7b9925cdac9da372e3b6c6bc246a3413343916).** I couldn't have done this as easily without the feature he added here. I hope this patch makes its way into the official build soon! *Sorry mobile users, the site still isn't really optimized on your end yet.* --- # Rewards History Ever been curious about what your long term rewards history looks like, in terms of both curation and author rewards? I have, and no where have I been able to view detailed information about these events until now. The black/blue navigation bar on this page allows you to navigate between **Curation** and **Author** rewards. ### Curation Reward History ![](https://steemdb.com/examples/steemdb-curation.png?fhfhgf) Example URL: https://steemdb.com/@jesta/curation The above screenshot and link shows off the new **curation rewards** page which is available for every account. You can browse through the entire history of curation rewards for an account until the beginning of time using the pagination on the bottom of the page. I choose to represent the graph and statistical information in VESTS instead of STEEM POWER, because the blockchain actually has no record of the STEEM POWER (AFAIK) you earned in the past. If I had a source of historical conversion rates I could update to show estimates of those rewards, but at this time I do not have that information. However, each individual record as you scroll shows an estimated earnings in STEEM POWER using today's current conversion rate. So technically if you never powered down those rewards, this is what those rewards have grown to at this date. Confusing I know, we'll work it out and make it more consumable as time progresses :) ### Author Reward History ![](https://steemdb.com/examples/steemdb-authoring.png) Example URL: https://steemdb.com/@jesta/authoring This screenshot and associated link shows off the new **author rewards** page. Similar to the curation rewards page, this page shows rewards for all of the posts and comments you've ever written. Currently there is no way to filter between the two types of posts easily, but it's something on my radar to improve. --- # Transfer History A number of times recently I have been asked for very deep history about the accounting of an account, whether it be for a promotion being run or for personal records. There are currently a number of different ways you can transfer funds, and to start with my in depth data analysis, I've choose what I feel are the three most important: - STEEM transfers (or "Power Up") to VESTS - VESTS transfers (or "Power Down") to STEEM - SBD/STEEM transfers between accounts In the future I plan on also adding transfers to/from savings accounts as well as escrow. The black/blue navigation bar on this page allows you to navigate between **Power Up**, **Power Down** and **Transfer** history. ### "Power Up" Transfer History (aka Vesting Deposit) ![](https://steemdb.com/examples/steemdb-powerup.png) Example URL: https://steemdb.com/@kevinwong/powerup I hope @kevinwong doesn't mind me using him as an example. He has powered up 19x times in the last 30 days, so it made for a good chart :) This new **power up transfer** page shows all conversions of STEEM to SP/VESTS an account has ever performed and lets you dig into it's history. The top of the page also features a chart with the amount powered up, each day, over the last 90 days. The page itself shows how much STEEM was transfered into SP, but doesn't account for how many VESTS the user received. As with the two sections above, once I get my hands on some historical conversion information, I'll be able to generate estimates for these conversions but never exact amounts. ### "Power Down" Transfer History (aka Vesting Withdraw) ![](https://steemdb.com/examples/steemdb-powerdown.png) Example URL: https://steemdb.com/@jesta/powerdown This new page is the exact opposite of the power up page, and shows all **power down transfers** an account has ever made. The record being shown here is when the actual power down occurs, and not the request to power down. Here you can see a week to week overview of how much STEEM POWER/VESTS a user has withdrawn into liquid STEEM. The chart at the top of the page shows the last 90 days of history (roughly 12-13 weeks) of power down transfers. ### STEEM/SBD Transfer History ![](https://steemdb.com/examples/steemdb-transfers.png) Example URL: https://steemdb.com/@bittrex/transfers Last but not least is the actual **transfer** page, which shows all STEEM and SBD transfers involving the account you're viewing. You can use the pagination at the bottom to browse through the entire history of transfers. I choose @bittrex as an example to show in the screenshot above simply because they have a large volume of incoming and outgoing transfer history. **Note**: Most transactions are missing the "type" column of the data right now. I am working on a fix for this, but it will require a decent amount of time to replay the blockchain and correct this issue. In my rush to get this project started, I inadvertently stripped off the currency symbol without thinking to store it anywhere. --- # Additional Features ### New navigation items for accounts ![](https://steemdb.com/examples/steemdb-newmenuitems.png) All of the new features described above are located under "Activity" with these two menu items. ### The user sidebar sticks to the page now ![](https://steemdb.com/examples/sidebar-stick.gif) These pages are getting long, so I figured it might be nice if the sidebar followed you down the page to provide context. ### Pagination ![](https://steemdb.com/examples/steemdb-pagination.png) All of these new pages have pagination elements as shown above. This element is at the bottom of each page that lets you browse forward and backward in time. ### Some charts have tooltips now ![](https://steemdb.com/examples/steemdb-chart-tooltips.png) They are sort of terrible, but they show something at least. I haven't implemented them on every chart simply because it was taking too long, and charts with multiple data segments were almost impossible to do. This charting solution, while looks great, has been rather difficult to use when trying to setup tooltips and interactions. ### Full change log If you're interested in seeing all the minor changes (I won't include here), I'd invite you to check out the github commit history. This is an open source project, anyone can contribute and run it if they choose to. https://github.com/aaroncox/steemdb/commits/master --- I'm excited to have these updates deployed and I hope you enjoy! It'll likely be a few weeks before another update to steemdb is deployed, and on the radar is steemstats like features and new/better charting of data. If you have something you'd specifically like to see, please let me know. While I haven't gotten around to everyones ideas, I do keep track of all suggestions and review them as I'm looking for fun new things to accomplish.
post[json_metadata]
[tags]
[0] steemdb
[1] patch-notes
[users]
[0] arhag
[1] kevinwong
[2] bittrex
[image]
[0] https://steemdb.com/examples/steemdb-curation.png?fhfhgf
[1] https://steemdb.com/examples/steemdb-authoring.png
[2] https://steemdb.com/examples/steemdb-powerup.png
[3] https://steemdb.com/examples/steemdb-powerdown.png
[4] https://steemdb.com/examples/steemdb-transfers.png
[5] https://steemdb.com/examples/steemdb-newmenuitems.png
[6] https://steemdb.com/examples/sidebar-stick.gif
[7] https://steemdb.com/examples/steemdb-pagination.png
[8] https://steemdb.com/examples/steemdb-chart-tooltips.png
[links]
[0] https://steemdb.com
[1] https://github.com/arhag/steem/commit/fa7b9925cdac9da372e3b6c6bc246a3413343916
[2] https://steemdb.com/@jesta/curation
[3] https://steemdb.com/@jesta/authoring
[4] https://steemdb.com/@kevinwong/powerup
[5] https://steemdb.com/@jesta/powerdown
[6] https://steemdb.com/@bittrex/transfers
[7] https://github.com/aaroncox/steemdb/commits/master
post[last_update] 2016-10-10T07:22:06
post[created] 2016-10-10T07:22:06
post[active] 2016-10-11T20:41:09
post[last_payout] 2016-11-10T17:36:06
post[depth] 0
post[children] 35
post[children_rshares2] 0
post[net_rshares] 0
post[abs_rshares] 0
post[vote_rshares] 0
post[children_abs_rshares] 0
post[cashout_time] 1969-12-31T23:59:59
post[max_cashout_time] 1969-12-31T23:59:59
post[total_vote_weight] 0
post[reward_weight] 10000
post[total_payout_value] 295.479 SBD
post[curator_payout_value] 24.815 SBD
post[author_rewards] 862144
post[net_votes] 525
post[root_comment] 1145419
post[max_accepted_payout] 1000000.000 SBD
post[percent_steem_dollars] 10000
post[allow_replies] 1
post[allow_votes] 1
post[allow_curation_rewards] 1
post[beneficiaries]
post[url] /steemdb/@jesta/steemdb-0-4-0-a-rich-history-for-every-account
post[root_title] steemdb 0.4.0 - a rich history for every account
post[pending_payout_value] 0.000 SBD
post[total_pending_payout_value] 0.000 STEEM
post[active_votes]
post[replies]
post[author_reputation] 71627050027202
post[promoted] 0.000 SBD
post[body_length] 0
post[reblogged_by]
post[html] <p>This is probably my favorite set of features (to date) working on this project - it answers so many questions I've had about my account's history I couldn't find elsewhere! In the 0.4.0 release of <a href="https://steemdb.com">steemdb.com</a>, new key features include <code>curation reward history</code>, <code>author reward history</code>, <code>transfer history</code>, <code>power up history</code> and <code>power down history</code>.</p> <p>These features are available for any account, just visit <a href="https://steemdb.com">steemdb.com</a> and search for your account using the search bar on the top, and use the sub navigation to find different aspects of your account.</p> <p>Before I go any further, <strong>a huge thank you to @arhag, who helped me gather this information by <a href="https://github.com/arhag/steem/commit/fa7b9925cdac9da372e3b6c6bc246a3413343916">developing a modified version of steemd</a>.</strong> I couldn't have done this as easily without the feature he added here. I hope this patch makes its way into the official build soon!</p> <p><em>Sorry mobile users, the site still isn't really optimized on your end yet.</em></p> <hr /><h1>Rewards History</h1> <p>Ever been curious about what your long term rewards history looks like, in terms of both curation and author rewards? I have, and no where have I been able to view detailed information about these events until now.</p> <p>The black/blue navigation bar on this page allows you to navigate between <strong>Curation</strong> and <strong>Author</strong> rewards.</p> <h3>Curation Reward History</h3> <p><img src="https://steemdb.com/examples/steemdb-curation.png?fhfhgf" alt="" /></p> <p>Example URL: https://steemdb.com/@jesta/curation</p> <p>The above screenshot and link shows off the new <strong>curation rewards</strong> page which is available for every account. You can browse through the entire history of curation rewards for an account until the beginning of time using the pagination on the bottom of the page.</p> <p>I choose to represent the graph and statistical information in VESTS instead of STEEM POWER, because the blockchain actually has no record of the STEEM POWER (AFAIK) you earned in the past. If I had a source of historical conversion rates I could update to show estimates of those rewards, but at this time I do not have that information.</p> <p>However, each individual record as you scroll shows an estimated earnings in STEEM POWER using today's current conversion rate. So technically if you never powered down those rewards, this is what those rewards have grown to at this date. Confusing I know, we'll work it out and make it more consumable as time progresses :)</p> <h3>Author Reward History</h3> <p><img src="https://steemdb.com/examples/steemdb-authoring.png" alt="" /></p> <p>Example URL: https://steemdb.com/@jesta/authoring</p> <p>This screenshot and associated link shows off the new <strong>author rewards</strong> page. Similar to the curation rewards page, this page shows rewards for all of the posts and comments you've ever written. Currently there is no way to filter between the two types of posts easily, but it's something on my radar to improve.</p> <hr /><h1>Transfer History</h1> <p>A number of times recently I have been asked for very deep history about the accounting of an account, whether it be for a promotion being run or for personal records. There are currently a number of different ways you can transfer funds, and to start with my in depth data analysis, I've choose what I feel are the three most important:</p> <ul><li>STEEM transfers (or "Power Up") to VESTS</li> <li>VESTS transfers (or "Power Down") to STEEM</li> <li>SBD/STEEM transfers between accounts</li> </ul><p>In the future I plan on also adding transfers to/from savings accounts as well as escrow.</p> <p>The black/blue navigation bar on this page allows you to navigate between <strong>Power Up</strong>, <strong>Power Down</strong> and <strong>Transfer</strong> history.</p> <h3>"Power Up" Transfer History (aka Vesting Deposit)</h3> <p><img src="https://steemdb.com/examples/steemdb-powerup.png" alt="" /></p> <p>Example URL: https://steemdb.com/@kevinwong/powerup</p> <p>I hope @kevinwong doesn't mind me using him as an example. He has powered up 19x times in the last 30 days, so it made for a good chart :)</p> <p>This new <strong>power up transfer</strong> page shows all conversions of STEEM to SP/VESTS an account has ever performed and lets you dig into it's history. The top of the page also features a chart with the amount powered up, each day, over the last 90 days.</p> <p>The page itself shows how much STEEM was transfered into SP, but doesn't account for how many VESTS the user received. As with the two sections above, once I get my hands on some historical conversion information, I'll be able to generate estimates for these conversions but never exact amounts.</p> <h3>"Power Down" Transfer History (aka Vesting Withdraw)</h3> <p><img src="https://steemdb.com/examples/steemdb-powerdown.png" alt="" /></p> <p>Example URL: https://steemdb.com/@jesta/powerdown</p> <p>This new page is the exact opposite of the power up page, and shows all <strong>power down transfers</strong> an account has ever made. The record being shown here is when the actual power down occurs, and not the request to power down.</p> <p>Here you can see a week to week overview of how much STEEM POWER/VESTS a user has withdrawn into liquid STEEM. The chart at the top of the page shows the last 90 days of history (roughly 12-13 weeks) of power down transfers.</p> <h3>STEEM/SBD Transfer History</h3> <p><img src="https://steemdb.com/examples/steemdb-transfers.png" alt="" /></p> <p>Example URL: https://steemdb.com/@bittrex/transfers</p> <p>Last but not least is the actual <strong>transfer</strong> page, which shows all STEEM and SBD transfers involving the account you're viewing. You can use the pagination at the bottom to browse through the entire history of transfers.</p> <p>I choose @bittrex as an example to show in the screenshot above simply because they have a large volume of incoming and outgoing transfer history.</p> <p><strong>Note</strong>: Most transactions are missing the "type" column of the data right now. I am working on a fix for this, but it will require a decent amount of time to replay the blockchain and correct this issue. In my rush to get this project started, I inadvertently stripped off the currency symbol without thinking to store it anywhere.</p> <hr /><h1>Additional Features</h1> <h3>New navigation items for accounts</h3> <p><img src="https://steemdb.com/examples/steemdb-newmenuitems.png" alt="" /></p> <p>All of the new features described above are located under "Activity" with these two menu items.</p> <h3>The user sidebar sticks to the page now</h3> <p><img src="https://steemdb.com/examples/sidebar-stick.gif" alt="" /></p> <p>These pages are getting long, so I figured it might be nice if the sidebar followed you down the page to provide context.</p> <h3>Pagination</h3> <p><img src="https://steemdb.com/examples/steemdb-pagination.png" alt="" /></p> <p>All of these new pages have pagination elements as shown above. This element is at the bottom of each page that lets you browse forward and backward in time.</p> <h3>Some charts have tooltips now</h3> <p><img src="https://steemdb.com/examples/steemdb-chart-tooltips.png" alt="" /></p> <p>They are sort of terrible, but they show something at least.</p> <p>I haven't implemented them on every chart simply because it was taking too long, and charts with multiple data segments were almost impossible to do. This charting solution, while looks great, has been rather difficult to use when trying to setup tooltips and interactions.</p> <h3>Full change log</h3> <p>If you're interested in seeing all the minor changes (I won't include here), I'd invite you to check out the github commit history. This is an open source project, anyone can contribute and run it if they choose to.</p> <p>https://github.com/aaroncox/steemdb/commits/master</p> <hr /><p>I'm excited to have these updates deployed and I hope you enjoy! It'll likely be a few weeks before another update to steemdb is deployed, and on the radar is steemstats like features and new/better charting of data.</p> <p>If you have something you'd specifically like to see, please let me know. While I haven't gotten around to everyones ideas, I do keep track of all suggestions and review them as I'm looking for fun new things to accomplish.</p>
post[html_preview] <p>This is probably my favorite set of features (to date) working on this project - it answers so many questions I've had about my account's history I couldn't find elsewhere! In the 0.4.0 release of steemdb.com, new key features include curation reward history, author reward history, transfer history, power up history and power down history.</p><p>These features are available for any account, just visit steemdb.com and search for your account using the search bar on the top, and use the sub navigation to find different aspects of your account.</p>
post[image] https://steemdb.com/examples/steemdb-curation.png?fhfhgf
post[ts] 1476102126
accounts
accounts loaded from the configuration
tags
tags loaded from the configuration
steem configuration
    resources/config/config.yaml - `steem` variable
  
host https://node.steem.ws
blog configuration
    resources/config/config.yaml - `blog` variable
  
theme develop
title reprint powered blog
subtitle blockchain powered blog
elements
[author] 1
[category] 1
[payout] 1
[votes] 1
[comments] 1
filters
[accounts]
[jesta]
[0] post