it's the server issue, i am configuring new server right now. will put the chain to sync in a bit and in some hours i will have you guys try the exporter again, everything should work fine.

i don't see a single mention to bitshares or graphene anywhere on the post, website or whitepaper.

update in the burning:

worked just burned 127118 BTS: http://open-explorer.io/#/operations/1.11.115677591

Hello stakeholders, this is the last report from this worker in this thread.

I have a new worker proposal voting now to start 22th of this month as i am taking a week of vacation starting today.

Take a look at the new worker proposal here and vote for it if you like:

https://github.com/oxarbitrage/worker-proposals/blob/master/bitshares2018_1.md

New worker proposal number is 1.14.75

If approved, the reports will be posted bi weekly on the new worker thread at:

https://bitsharestalk.org/index.php/topic,25713.0.html

I want to thank everybody for supporting me and i hope i can continue here for the starting year, very exiting year for sure.

The worker has liquidated all the payment left and in the process of burning back 127118 BTS to the chain. This operation is already made and it is just waiting for 1 approval vote from the worker escrow, this will be happening in the next few hours.

Now let me go over the last advances, this was a period where it was hard to reach other bitshares devs for the holiday season, for this reason most of the work was focused outside core.

bitshares-core:

- issue https://github.com/bitshares/bitshares-core/issues/549 fixed with merged pull request: https://github.com/bitshares/bitshares-core/pull/551

- https://github.com/bitshares/bitshares-core/issues/528 finished documentation for elasticsearch plugin and moved to wiki page of bitshares: https://github.com/bitshares/bitshares-core/wiki/ElasticSearch-Plugin

- Small readme notes changes: https://github.com/bitshares/bitshares-core/pull/562

- review and merged https://github.com/bitshares/bitshares-core/pull/557

- merged https://github.com/bitshares/bitshares-core/pull/568 from @xeroc - docker updates.

- created new api call get_top_markets - https://github.com/bitshares/bitshares-core/pull/560

there are some other pending reviews from @abit, @pc and @xeroc that i will be able to finish when i came back from vacation or they will review each other if they want to merge before that.

account history exporter:

an account history exporter was made:

http://open-explorer.io/bitshares-account-exporter/index.php

It makes use of the elasticsearch node plugin and wrapper. Open source code in php can be found at: https://github.com/oxarbitrage/bitshares-account-exporter

There are plans to make a reduced version of it only exporting fill orders to be used with https://cointracking.info/

udf wrapper:

The udf wrapper was finished https://github.com/oxarbitrage/udf-bitshares-wrapper and was added as a proof of concept to the 2 explorer versions:

http://open-explorer.io/#/markets/CNY/BTS
http://bitshares-explorer.io/#/markets/CNY/BTS

The issue for it in UI was closed: https://github.com/bitshares/bitshares-ui/issues/773

I received the payment, i wanted to exchange it for some explorer work with the UI guys but they are to busy to do so at the moment.

Still, there are going to be more opportunities to make this deal in the future with other features the UI may need.

- bitshares-api-backend:

In addition to fixes i always do to this repo when i find a bug from the explorer i am now getting some contributions from @knaperek. He is helping as a volunteer to learn some bitshares with several stuff like dockerizing the project and fixing some bugs.

His contributions can be found at:

https://github.com/oxarbitrage/bitshares-python-api-backend/pull/1
https://github.com/oxarbitrage/bitshares-python-api-backend/pull/2
https://github.com/oxarbitrage/bitshares-python-api-backend/pull/3
https://github.com/oxarbitrage/bitshares-python-api-backend/pull/4

All of them were merged.


Thank you guys all again.

If we plan for a fixed release schedule we need the resources to deliver. Which means mostly it's up to our paid developers. You decide, @abit @oxarbitrage . :-)

i think a HF around every 6 months will be healthy but yes we need to have enough quality stuff to worth the effort.

the best to me will be as we made it last time that worked. this is:

- a dedicated worker proposal to work in a bsip or big feature with hardfork(will be great if we can have @pc again on it).
- worker will take care of the hardfork planning while a few satellite changes are added to the same hardfork(like the one on this thread).
- other devs contribute in this side changes and help the hardfork worker with the planning, testing, etc.

this should be done every X months resulting in more or less a planned hardfork release every X time.

i think they call it airdrop or something like that. i don't like the technique either.

Does not appear to be working?

200 limits aren't helpful, but I'm getting empty CSV.

i just tried it and i am not getting empty results, make sure you use your account id , not your name. make sure the dates you are using are timeframes where operations were made.

thank you guys