last time he was simply not interested, was not a matter of offering more $. maybe that changed now, not sure.

https://github.com/bitshares/bitshares-core/tree/develop

if you check the commits: https://github.com/bitshares/bitshares-core/commits/develop the last commit in master is from July 10(on page 4 currently). everything from there up to today is what will be included into the next bitshares-core release.

I am probably missing stuff, need to go back to reports every 1 week instead of 2!

bitshares-core:

- https://github.com/bitshares/bitshares-core/issues/411 - @dnotestein pointed us to a few commits made to the steem p2p code that will improve the operation of bitshares node. @xeroc made a cherrypick of the steem code(https://github.com/bitshares/bitshares-core/pull/412) that saved a lot of time than making this changes manually. Tested a full resync and the code worked fine so the solution was marged and the issue closed.

- https://github.com/bitshares/bitshares-core/pull/406 - code was made to fix issue https://github.com/bitshares/bitshares-core/issues/265 - need testing before merging and issue closing.

- https://github.com/bitshares/bitshares-core/pull/415 - We want to reduce ram in new installations without interfacing with existing business. @xeroc made some changes, i reviewed and approved but then @pc found some problems so we reverted back until this is fixed.

- @pc found some problem with a unit test of account_history when making the last testing for the next release. We fixed the issue here: https://github.com/bitshares/bitshares-core/pull/420 - merged.

- I started to work on a plugin that will allow to reduce full node ram usage by storing the history of accounts in the database(elasticsearch). At the same time it will solve several relational issues in searching in the account history in an efficient way. This is a big and time consuming task, more updates in this post on the next report.

explorer:

explorer is going slow but good, as cryptofresh has been working fine after the server change i dont have the preassure of being the only working explorer so i am focusing on having more stats suggested by the community i nthe form of issues.

- almost all the changes requested by @tbone were made to the assets page. part of the discussion can be found in the assets page issue at : http://bitshares-explorer.io/#/assets
closing the issue by now.

- https://github.com/oxarbitrage/bitshares-explorer/issues/11 changes were made to the individual asset page as: http://bitshares-explorer.io/#/assets/1.3.1152 closed the issue.

- https://github.com/oxarbitrage/bitshares-explorer/issues/7 fixed as part of the assets page work. closed.

- https://github.com/oxarbitrage/bitshares-explorer/issues/9 working on account page issues, not moved to production yet but can see progress in the develop version: http://bitshares-explorer.io:9009/#/accounts/1.2.121

full history data is back to the explorer. sorry for the delay, i didn't had the keys for the full node server while travelling in the last days. everything should be working now.

Adding a report now with the work from the last 1 week and a half. I am posting it today as i am going out for a small trip tomorrow and i'll be back Tuesday next week. I am going to Buenos Aires for family issues but also going to meet @ElMato and i have the luck that this Saturday there is an EOS event, ill be there

bitshares-core:

- https://github.com/bitshares/bitshares-core/issues/108 -> closing UI related issue after asking @svk and @wmbutler , old issue, not a problem anymore.
- https://github.com/bitshares/bitshares-core/issues/403 -> assigned myself the issue, made some initial research but the bulk of the work will be done next week to change index.
- https://github.com/bitshares/bitshares-core/issues/75 -> located documentation confirming the operation will delete and not refuse to sign, also found line where proposal is deleted from the blockchain. @abit mentioned another issue with the implementation but will be discussed in  new issue, closing this one.
- https://github.com/bitshares/bitshares-core/issues/409 -> helping with build issues in ubuntu 17.10.
- https://github.com/bitshares/bitshares-core/issues/265 -> added pull request for the issue at: https://github.com/bitshares/bitshares-core/pull/406 -> under review by  the team now.
- merged seed addition https://github.com/bitshares/bitshares-core/pull/400/files
- merged documentation change by @abit https://github.com/bitshares/bitshares-core/pull/401
- https://github.com/bitshares/bitshares-core/issues/390 ->  closed issue

- https://github.com/bitshares/bitshares-core/pull/405 -> new pull request was made to resolve the issue of the get account history by date and trying to build a framework to solve other issues that require similar actions. we are unsure on how we will proceed, options haves been presented and it is in discussion with the bitshares dev community.

explorer:

- big improvements were made to the assets page with the guide of @tbone https://github.com/bitshares/bitshares-core/issues/390
- https://github.com/oxarbitrage/bitshares-explorer/issues/3 -> done and closed issue.

- explorer server was hacked this week, mainly because i have other sites, old sites in the same server. i had a hard time to restore it.  @wmbutler has sent me an instance to run the explorer, and it will be moved there next week. thank you very much @wmbutler !

what do you mean with wrong data exactly, this data came from the get_order_book api call into nodes. this is correct data of what the blockchain haves, the other place where you are comparing the data of this api calls output is what it is wrong.

@diablo4 as far as i know the blockpay repos were and are private so i don't think you will be able to see them in ken public github. as far as i know ken is/was a project manager so the number of commits he did or do are actually of no interest. in regards to @bilthon he haves an account here, i have his skype, he is probably dedicating to other projects after bitshares munich issues but i don't think he is an unidentifiable bogus or scammer.

scammers or not this is a thread to discuss STEALTH, not blockpay so i will be definitely more interested on @karnal concerns to some technical and planning issues than on this.

tengo una propuesta de trabajo activa en bitshares. cualquier consulta de como funciona me avisan.