folks, 2 weeks has passed since my last report, here is a summary of the last work done.

bitshares core:

all the pull requests with hardfork were reviewed and merged to the develop branch. @pc later updated the testnet based on this branch.

- https://github.com/bitshares/bitshares-core/pull/386 - merged.
- https://github.com/bitshares/bitshares-core/pull/369 -  merged.
- https://github.com/bitshares/bitshares-core/pull/348 - merged.
- https://github.com/bitshares/bitshares-core/pull/340 -  merged.

https://github.com/bitshares/bitshares-core/issues/390

sent link to new documentation of memory reduction techniques and closed the issue.

https://github.com/bitshares/bitshares-core/pull/391

a few more changes were made to the documentation to reflect memory size.  merged pull.

https://github.com/bitshares/bitshares-core/pull/339

after some additional testing the pull by peter conrad was merged.

https://github.com/bitshares/bitshares-core/pull/346

requested @xeroc to fix the conflicts, now pull under review by me for a possible merge into the develop , can be a good starting point to develop plugins for newcomers.

https://github.com/bitshares/bitshares-core/pull/392

reviewed and merge this small fixes and cleanup by peter conrad.

https://github.com/bitshares/bitshares-core/issues/395

assistance provided for build issues, problem was fixed, closed the issue.

https://github.com/bitshares/bitshares-core/issues/396

removed header in pull request: https://github.com/bitshares/bitshares-core/pull/397 merged and closed issue.

https://github.com/bitshares/bitshares-core/pull/398

tested and merged patch by peter.

https://github.com/bitshares/bitshares-core/pull/379

a new solution has been proposed in this pull request to access some needed blockchain data without spending any additional ram. this was a very big research work. i can say that i spent almost the last entire week working on this solution that i hope can be approved by the other devs as it can bring additional features to our api calls not currently possible. i am not really sure of the future of this pull request(if it will be accepted or not) but what learned in the process is invaluable.

note will upload the proposed solution tomorrow morning as i found a small bug i want to fix before pulling. will update here when it is up.

https://github.com/bitshares/bitshares-core/issues/355

this was also a time consuming task. i was able to confirm bitshares-core full project compiles in a 32 bits ubuntu system even if in production this is pretty much useless it can be of interest for private blockchains or testnets. closed the issue.

explorer:

the main issues the explorer was having was the possibility to browse all user history, this has been added and it is fully supported with the help of a full node provided by @xeroc. the other main problem was that the explorer service was crashing with high traffic, this was fixed, it can still be improved further but it is working better now.

issues are open for the explorer at https://github.com/oxarbitrage/bitshares-explorer/issues and will be added to this report as thye get resolved.

i plan to spend significant time this week in the explorer to keep improving it as it is gaining traffic and it is having great feedback. now that the hardfork code was merged in the core and that very time consuming advances had been made at pull 379 the idea is to have more time for it this week.

Thanks for the consistent updates.  Any opinion on this feature being discussed for a future core project? https://github.com/bitshares/bitshares-ui/issues/356

you can submit the issue to the bitshares-core at: https://github.com/bitshares/bitshares-core/issues and we will consider it however as it needs a hardfork it is going to be hard to see it done in a short period of time. please note we are after a hardfork now and this is not something that happen very often. @svk comments it is also big work, that decrease even further the possibilities of materializing it as it will need to be done throw a bsip(https://github.com/bitshares/bsips). still, if you can convince an important number of people(shareholders) that this is important then it will eventually be done.

first production version of the explorer is at: http://bitshares-explorer.io/

the dev version in port 9009 will continue up for now but please use http://bitshares-explorer.io/, should be faster and with less bugs.

every bug/feature/suggestion/whatever will be now in the form of github issue. please add here: https://github.com/oxarbitrage/bitshares-explorer/issues

i am now in the last stage of version 1. this is some code cleanup, documentation and release of open source explorer so the community can mirror, help in the development and all that.

i will maintain the explorer repo so any suggestion/feature will be considered. more news will came soon.

Hello shareholders, it has been 2 weeks since last report. I realized today that last week i didn't made it, was and still very busy working but that's no excuse, i should write it weekly, is even easier for me.

My apologies for that and i will try to don't do the same again. Anyways, the report today includes the last 15 days of work by this worker.

Bitshares Core Tasks:

- https://github.com/bitshares/bitshares-core/issues/358 -> work in progress, have a solution, will pull tomorrow.

- https://github.com/bitshares/bitshares-core/issues/355 -> i have an old machine 32 bits to test compilation, i remember i tested it a long time ago and didn't worked for me but don't remember the reason.

- https://github.com/bitshares/bitshares-core/issues/361 -> closed.

- https://github.com/bitshares/bitshares-core/pull/352 -> made requested changes, merged.

- https://github.com/bitshares/bitshares-core/issues/367 -> opened issue about error caused by one of the last merges. @pc identified the cause of the problem and submitted a patch: https://github.com/bitshares/bitshares-core/pull/368 -> works good now, merged patch.

- https://github.com/bitshares/bitshares-core/issues/295 Closed. Made additional changes to core to solve this issue, this are at pull: https://github.com/bitshares/bitshares-core/pull/364
Issue was opened in the UI to make a warning when subscriptions to accounts its passing 100: https://github.com/bitshares/bitshares-ui/issues/299 -> issue was closed by @svk as this will be handled different in the upcoming GUI release.

- https://github.com/bitshares/bitshares-core/pull/373 -> adding 2 new calls to work with transactions hashes from the api. first call was easy but the second i want to make need more bigger changes. work in progress, i have a working prototype, new commits will be added to introduce the second call in the next days.

- https://github.com/bitshares/bitshares-core/issues/375 -> unrelated, replied and closed.

- https://github.com/bitshares/bitshares-core/pull/345 -> tested and merged.

reviewing now:

- https://github.com/bitshares/bitshares-core/pull/376 -> testing.
- https://github.com/bitshares/bitshares-core/pull/341 -> testing, the log message is fine to identify the problem, the tests cases are a bit unclear still. more review needed before merging, i have to check with @alexpmorris.
- https://github.com/bitshares/bitshares-core/pull/348 (HF) -> testing hardfork with the debug node.
- https://github.com/bitshares/bitshares-core/pull/369 (HF) -> testing hardfork with the debug node.

Explorer:

Today it is the deadline of a very rough estimate i made for the explorer of 1 month, plan was to have all the TODO tasks of the explorer finished:

https://github.com/oxarbitrage/bitshares-explorer/blob/master/Roadmap1.md

https://github.com/oxarbitrage/bitshares-explorer/blob/master/TODO.md

The TODO is right now at 90%. The reason it is not at 100% today are a few:

- there is also a TODO 2 where some tasks were made: https://github.com/oxarbitrage/bitshares-explorer/blob/master/TODO2.md
- the estimate was rough and some tasks required more time.
- some tasks not included in TODO1 and TODO2 had to be done.

The remaining 10% of the TODO1 is just cleanup, performance and code disclosure.

All the features and sections of the explorer are working*, i encourage to visit one more time: http://bitshares-explorer.io:9009/
Performance will increase as i remove all the crap and package it for distribution, it haves some problems but it is fully functional.

* Only section not working is transactions section(http://bitshares-explorer.io:9009/#/txs) but that is not part of TODO1.Trying to first add some code to the core in order to achieve transactions section and search.

As it was previously mentioned, the project is 2 repos.

https://github.com/oxarbitrage/bitshares-python-api-backend -> api python backend serving the explorer website only at the moment but can serve other applications. Public and fully updated.

https://github.com/oxarbitrage/bitshares-explorer

To release the code of the explorer part, with all the cleaning and stuff i have to do, i think i am going to need 1 week more.

Others:

Upticks:

https://github.com/xeroc/python-bitshares/issues/10

Docs.Bitshares.Org:

https://github.com/bitshares/docs.bitshares.org/pull/16

Bitshares.GitHub.IO:

to be merged after next release of bitshares UI:
https://github.com/bitshares/bitshares.github.io/pull/108

SonarCloud:

https://sonarcloud.io/dashboard?id=BitShares-develop%3Adevelop

taking the opportunity to mention that @pc added our develop bitshares-core branch, this will allow to improve code quality. For a huge project like bitshares the code quality ratings are pretty impressive.

Until next week, thanks for taking the time of reading

i agree with that @pc and so also @xeroc . we neeed to decide what can we move to bsip 18 and leave the rest for a future release.

I have introduce my architecture which  already used by btsbots.com

just fetch all transactions from witness_node, process all data, generate new data, save it to mongodb.
 mongodb is the new backend, it can be expand with a slave node easy.

nodejs get all data from mongodb, it's just a very common nodejs web project, no blockchain tec need for UI developer.
you can hire any reactjs developer to improve/custom your wallet.

you can get the source for btsbots.com: https://github.com/pch957/btsbots-demo-2016
icowallet is a Chinese team who develop a new wallet based the new architecture: https://www.icowallet.net/
they  have their business plan, are funded with a ICO, and will open source their wallet in the future.

I will continue contribute to the new architecture, but not as a worker, as a volunteer.

this is very interesting, i had in mind to store bitshares data in a mongodb, i saw a steem project making it but never knew it was already done for bitshares. this will allow all kind of user apps to be done without knowing anything about blockchain technology.

probably a topic to discuss in a different thread but i will be happy to fork, test, create some documentation and such.

trying to put more effort to the explorer to have v1 faster as i am aware of the repeated problems of cryptofresh in the last time.

Hello Bitshares community, i was not able to post the weekly report of the worker during the weekend so i am posting it today Monday for work done last week.

- https://github.com/bitshares/bitshares-core/pull/335

i requested the help of peter conrad(@pc) to solving this issue. he made a patch into my repo, i just pulled it to bitshares and finally merged to the develop branch after testing.

issue will be closed in 24 hours if there is no objections as the problem is solved: https://github.com/bitshares/bitshares-core/issues/325

- https://github.com/bitshares/bitshares-core/issues/329

at this issue i sent instructions to the issuer on how to do what he was trying to do with what was currently available. issue was closed and later reopened requesting a small modification in the get_trade_history results.

request was considered and patch was sent to the bitshares develop branch:
https://github.com/bitshares/bitshares-core/pull/344

this is now under review of the bitshares developer community.

- https://github.com/bitshares/bitshares-core/pull/336

in this patch submitted by peter conrad part of the problem of issue 303(https://github.com/bitshares/bitshares-core/issues/303) gets solved. the issue in the node output is fixed with the patch but the unit tests are not. trying to make a fix to both cases before approving it.

- https://github.com/bitshares/bitshares-core/pull/332

changes were made to patch to consider when api-access file does not exist in the filesystem.
this is for issue https://github.com/bitshares/bitshares-core/issues/331 that will be closed in 24 hs if there are no objections.

- Explorer TODO: https://github.com/oxarbitrage/bitshares-explorer/blob/master/TODO.md and roadmap for a 1 month plan has been released: https://github.com/oxarbitrage/bitshares-explorer/blob/master/Roadmap1.md

Also in the past week some of the checked items in the TODO were done.

Finally, there is a lot of stuff going on with implementation of bsip-018, the bitshares hardfork and a recent steem post that introduced some new(and some not so new) issues in the chain. I am currently working at some of this but no enough advances to put it in the report, more on this next week.

thank you very much for reading