this is great news and i was not aware of it, thanks for sharing @renkcub

just contacted @ElMato to see if i can assist him with this or something.

the problem right now is that most nodes are "private" nodes created by third parties to do their stuff. they don't want/need to be fully public because they only want to host traffic for their business, not for all the businesses running in the chain.

i understand your concern and the bitshares foundation is after this with a new worker proposal , very close to be approved at this moment that actually want to create a public network of public api nodes between other things, read the full thing at http://www.bitshares.foundation/workers/2017-12-infrastructure

Fellows, here the pull requests, issues, etc i was working on in the last 2 weeks:

bitshares-core:

- moved discussion about new features of worker proposal into a BSIP created by @billbutler at https://github.com/bitshares/bsips/blob/master/bsip-0028.md. We closed https://github.com/bitshares/bitshares-core/issues/451 and https://github.com/bitshares/bitshares-core/issues/473 from the core discussions. Sent pull request to update technical aspects of the new BSIP: https://github.com/bitshares/bsips/pull/41

- https://github.com/bitshares/bitshares-core/issues/465 - added pull to include 15 mins, 30 mins and 4hs buckets, removing 15 seconds: https://github.com/bitshares/bitshares-core/pull/466

- https://github.com/bitshares/bitshares-core/issues/403 reviewed @abit code at https://github.com/bitshares/bitshares-core/pull/464, after some error fix we merged.

- opened issue https://github.com/bitshares/bitshares-core/issues/452 for referral index. found bug when exploring referral available code for explorer. no fix yet - relative low priority as client can still loop throw all accounts.

- https://github.com/bitshares/bitshares-core/pull/444 - after a lot of work the elasticsearch plugin has been finally merged to the develop branch.

- https://github.com/bitshares/bitshares-core/pull/471 - added code to allow plugins to have descriptions. merged.

- https://github.com/bitshares/bitshares-core/issues/476 - add curl as dependecy to documentation : https://github.com/bitshares/docs.bitshares.org/pull/22/files and https://github.com/bitshares/bitshares-core/pull/477

- reviewed and merged https://github.com/bitshares/bitshares-core/pull/479 to fix https://github.com/bitshares/bitshares-core/issues/409 (doxygen issue with last stable debian)

- https://github.com/bitshares/bitshares-core/issues/449 - tested, setted up tmp public node for interested parties to test in. changes were merged and the chart data from the core does not need any filtering anymore. can see it working at: http://bitshares-explorer.io/#/markets/CNY/BTS

- merged docker files from @xeroc https://github.com/bitshares/bitshares-core/pull/482

bitshares-fc:

- a pull request was submitted to FC to make bitshares project compile with newer version of boost(up to 1.63) https://github.com/bitshares/bitshares-fc/pull/5 - after testing we merged the solution.

- another pull address the compile problem of GCC 7.2. merged solution also: https://github.com/bitshares/bitshares-fc/pull/6

- @abit made the needed changes to reflect the new changes from bitshares-fc into bitshares-core. Tested and merged the whole solution: https://github.com/bitshares/bitshares-core/pull/483

- added documentation to include new supported versions of boost at https://github.com/bitshares/bitshares-core/wiki and https://github.com/bitshares/bitshares-core/pull/486

explorer:

- An issue in the explorer was making the python interface to crash when too much traffic are browsing the explorer at the same time. I was able to change the configuration of the backend to run under Nginx and with 4 processes. The explorer has been stable for the last 3 days with no crash so i hope this will be the end of this problem but i can add more processes if needed.

- i requested an increase of HD in one of the explorer servers as i need to run 2 nodes at the same time in the near future. One will serve what it is currently serving while the other will have elasticsearch plugin that will allow to bring lot of new features to the explorer. While everything could be done with 1 node with ES loaded it will be better if we keep current funcionality working so there is going to be a period of time while both nodes will be used.

- fixed chart data with new core changes, market charts now look as they should: http://bitshares-explorer.io/#/markets/CNY/BTS without any filtering client side. https://github.com/oxarbitrage/bitshares-python-api-backend/commit/34d87ebe5b4daa9418e9c0d6e86bae53adf9df85

- added referral information to account page(http://bitshares-explorer.io:9009/#/accounts/fav). Information includes by now count of referrals and account names. More info will be added. This is going after https://github.com/oxarbitrage/bitshares-explorer/issues/6

Release, we did.

https://github.com/bitshares/bitshares-core/releases

After a lot of testing in our 3 branches(develop - testnet - master) we tagged a new release. This is the work of contributors on the last 3 months featuring lot of great work by @pc. thank you for all the work done in this time.

A special mention in the release are some last minute changes like the default config code: https://github.com/bitshares/bitshares-core/pull/422 and the asset creation fee issue https://github.com/bitshares/bitshares-core/issues/433 - https://github.com/bitshares/bitshares-core/issues/429 . For this last issue we replicated the problem in the testnet then a patch in the form of softfork was added by @abit and finally @pc made a definitive solution that was added to the release at the last minute.

Another last minute addition was a new plugin @pc created while fixing 429-433 https://github.com/bitshares/bitshares-core/pull/437
this is a snapshot plugin that allow the user to create a full json formatted file that includes all the indexes from the entire blockchain at a selected block or date.

Many other last minute changes were added, check the release page for the details on whats included, the amount of work testing to make candidate, pre release and release was very significant but it is finally available.

The following issues are after release or non related to it:

- https://github.com/bitshares/bitshares-core/issues/431 - closed.
- https://github.com/bitshares/bitshares-core/issues/439 - closed - fix here: https://github.com/bitshares/bitshares-core/pull/440

- https://github.com/bitshares/bitshares-core/pull/444 - version1 of elasticsearch plugin and documentation https://github.com/oxarbitrage/worker-proposals/blob/master/elasticsearch-plugin.md

This is a very needed plugin that will allow to close many issues related to the API and to run full nodes without all the RAM currently needed. V1 is a fully working version but it needs a lot of fine tuning before a merge. I already got the needed feedback to do this from the other bitshares devs and now the fine tuning is in process. Most of my work will be here in the next few weeks.

- Explorer - with the release and the elasticsearch plugin i was very focused in the core and left explorer abandoned a bit. Still some small progress was made in the assets page: http://bitshares-explorer.io/#/assets, in the account page: http://bitshares-explorer.io/#/accounts/1.2.121 and in the market page: http://bitshares-explorer.io/#/markets/CNY/BTS
Ill try to revamp it this next weeks now that the release passed and the heavy work in the elasticsearch plugin too specially starting by adding referral stuff to the explorer https://github.com/oxarbitrage/bitshares-explorer/issues/6 ,  do some of the last requested changes at the assets page https://github.com/oxarbitrage/bitshares-explorer/issues/2 and https://github.com/oxarbitrage/bitshares-explorer/issues/1

i understand thomas concerns but i don't share them all. the short answer is to me bitshares is already fully open in regards to account history. 

and to me the most transparent and open the blockchain is, the best, it's an advantage against all traditional systems but that is just my view of it.

the best and more close shot  for privacy bitshares haves is the STEALTH development

anyways, @Thom i hope we can still be friends besides this small difference

i like this worker proposal, China is the place where bitshares is most used as far as i know and a perfect place for us to be making more businesses. I never make any input on worker proposal price as that depends on a lot of factors but i definitely think more businesses on top of our chain is what bitshares needs.

I understand the community ask for reports, some kind of reports will be needed but that will be just define a place where updates are posted regularly like on what presentations the worker  team was on, what business partners he is negotiating with, what business was convinced to came on board and so on.

I unfortunately don't know much of the people involved so i have to relay on what @bitcrab and @abitmore have to say about it.

my voting stake is very small and will not make a difference but i just voted for it. all the luck

>:(alfredo Garcia
nesecito ayuda mi hermano conquien puedo hablar para arreglar algo en mi cuenta de bitsheres , sucede que traferi desde mi cuenta de coinbase , $523.00 dollares y lo tenia en mi cuenta y sucede que hacen dos dias le di a a lago que sellama withdrawal y  derepende mi dinero se de saparecio y ahora aparece en una cuenta que sellama openledger-wallet  pero quiero tranferir a mi cuenta y no me deja ahora cadave que quiero tranferir no puede por que medice que nesecito una authorisacion no se de quien y nesecito sacar mi dinero no me gusta ested systema de verda que no . porfavor te agradeseria su conce de alguien que me pueda ayudaR PORFAVOR , ME PUEDE escribir a mi correo esv-ministry@hotmail.com

parece ser algún problema específico con openledger. proba en el telegram de openledger en español si no sabes nada de ingles: https://telegram.me/OpenLedgerESP
cualquier cosa enviame un mensaje privado ya que este no es el lugar para estas consultas en ningún idioma.

//////////// guy having an issue with a withdraw using openledger, sent him to openledger support telegram in spanish. out of topic for the thread.