Author Topic: Alfredo Garcia - Bitshares core developer - 1.14.75  (Read 8347 times)

0 Members and 1 Guest are viewing this topic.

Offline oxarbitrage

For stakeholder info. With the supplemental worker me and the escrow group were able to cover all the debt and burn back to the chain 42,585 BTS. This was done 2018-07-27.
Operation can be seen at http://open-explorer.io/#/operations/1.11.350044913

and worker account full details: http://open-explorer.io/#/accounts/alfredo-worker


Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc

Offline clockwork

  • Committee member
  • Sr. Member
  • *
  • Posts: 376
    • View Profile
  • BitShares: clockwork
voted supplemental worker..obviously :)

Offline oxarbitrage

As it was expected the price of BTS remained low the whole period so i had no option to submit a supplement worker to get the funds needed to pay the debt.

The details of this are here: https://github.com/oxarbitrage/worker-proposals/blob/master/supplement.md

Worker id is: 1.14.110 and it is now available for voting.

Please let me know any question, it is important this to be approved, get the payments done and burn the rest the most quickly as possible to don't interfere with  other worker and to don't speculate on the price further. This is why the worker is short duration(5 days) and asking 20,000 BTS per day(for a total of 100,000 BTS) that should be enough to cover everything.

I am moving into the bitshares-core team worker as in different talks with several community members i concluded it will be the best path to take.

I want to thank all the stakeholders, proxies, community in general that always supported me, i will make a new post with some closing notes after all this gets solved.

Thanks again.

Offline oxarbitrage

Hello stakeholders, it had been a while since my last update in my worker thread, i have a few announcements that i will like to share.

As noticed i stopped to update the thread bi weekly with work done. The reason for this is that making the report takes too much time to collect the info, it can be easily obtained by following my github account, telegram channel or msg me or others directly. With the new bitshares-core worker proposal @fox is updating the community more professionally than what i can do. In short, spend for example a morning creating a report with github links dont have much value as invest that time working on an issue, a document, helping someone, etc and i think the community will prefer that too. Please anyone with an objection to that let me know, i will be happy to assist on how the info can be obtained.

Next, this worker was created when price of BTS was at the top of 0.8 against the dollar. Worker haves protection of 2.5 multiplier so with BTS at around 0.35 worker is fine to cover the monthly payment. As the reader may know, this is pretty far to be the case in the last time so worker i having problems to pay. Some payments were made but it is pretty much behind.

Thanks to the bitshares-core proposal and my contributions of a few hours in there i am getting some additional USD, plus some money i had from before i can say i am fine in this moment. I am not in a rush to get paid. So what i will prefer to do is to wait some more and don't buy USD now and speculate with saving some money to the blockchain with a higher BTS price.

It is very probable that this worker is going to need a helper worker proposal to pay the debt, however the plan will be to keep the BTS now looking for an increase in price to pay a good part of the debt or, at the end, just buy the USD we can and add the helper worker.

Idea is to avoid the helper worker completely or make it the smallest possible. I asked the worker escrow group and they agree. As a reminder, the escrow group for this worker is: @xeroc, @svk, @fox, @elmato and @valentin.

Please any suggestion/objection against this plan of action let me know.

Finally, when the worker expires my idea is to keep working in bitshares. I have the option to be part of the bitshares-core team or propose a new worker. Not fully decided yet, idea is to try to continue for the same money without being a charge to the bitshares-core proposal. The best and easier for all is what i will be seeking. Will update on that, there is still time, current worker expires 22 of July.

Thank you for reading.

Offline Fox

thank you and sure thing, i fully support what the foundation do even if my worker is not currently under it. more than happy if this report, future and past ones are added anywhere they can make it fit.

Oh, sorry that was my mistake.. I assumed too quickly. It's not necessary, or even possible then since there is no page at the BBF s site for your worker then. We ll see what happens :)

Once the Core Team Worker Proposal is posted by the BBF, there will be a place for reporting all team member contributions. I will work with both BBF and Alfredo to ensure the community are aware of all development activities. https://bit.ly/FoxWP2018
Witness: fox

Offline sschiessl

  • Administrator
  • Hero Member
  • *****
  • Posts: 662
    • View Profile
  • BitShares: sschiessl
thank you and sure thing, i fully support what the foundation do even if my worker is not currently under it. more than happy if this report, future and past ones are added anywhere they can make it fit.

Oh, sorry that was my mistake.. I assumed too quickly. It's not necessary, or even possible then since there is no page at the BBF s site for your worker then. We ll see what happens :)

Offline oxarbitrage

thank you and sure thing, i fully support what the foundation do even if my worker is not currently under it. more than happy if this report, future and past ones are added anywhere they can make it fit.

Offline sschiessl

  • Administrator
  • Hero Member
  • *****
  • Posts: 662
    • View Profile
  • BitShares: sschiessl
Thanks for sharing, and great job! Good to see such progress.

If you want this thread to be linked on the BBF homepage for transparency, sent it to report@bitshares.foundation (https://steemit.com/bitshares/@bitshares.fdn/workers-new-email-addresses-for-workers-of-the-bitshares-blockchain-foundation)

Offline oxarbitrage

report of work done since the beginning of the new worker(22/01/2018) until today.


bitshares-core testing and reviews:

https://github.com/bitshares/bitshares-core/pull/574 - https://github.com/bitshares/bitshares-core/pull/573 - reviewed and approved.
https://github.com/bitshares/bitshares-core/pull/595 - reviewed, tested and approved.
https://github.com/bitshares/bitshares-core/pull/589 - reviewed, tested, approved and merged.
https://github.com/bitshares/bitshares-core/pull/578 - reviewed, tested and approved.
https://github.com/bitshares/bitshares-core/pull/570 - reviewed, tested and approved.
https://github.com/bitshares/bitshares-core/pull/594 - reviewed, tested, approved and merged.
https://github.com/bitshares/bitshares-core/pull/608 - reviewed, tested, approved and merged.
https://github.com/bitshares/bitshares-core/pull/621 - reviewed, tested, approved and merged.
https://github.com/bitshares/bitshares-core/pull/638 - reviewed, tested, approved and merged.
https://github.com/bitshares/bitshares-core/pull/640 - reviewed, tested, approved and merged.
https://github.com/bitshares/bitshares-core/pull/653 - reviewed, tested, approved and merged.
https://github.com/bitshares/bitshares-core/pull/654 - reviewed, tested, approved and merged.
https://github.com/bitshares/bitshares-core/pull/656 - reviewed, tested, approved and merged.
https://github.com/bitshares/bitshares-core/pull/665 - reviewed, tested, approved and merged.
https://github.com/bitshares/bitshares-core/pull/666 - reviewed, tested, approved and merged.
https://github.com/bitshares/bitshares-core/pull/667 - reviewed, tested, approved and merged.

https://github.com/bitshares/bitshares-core/pull/572 - reviewed, tested and approved.

https://github.com/bitshares/bitshares-core/pull/662 - reviewing now.
https://github.com/bitshares/bitshares-core/pull/662 - requested some changes.
https://github.com/bitshares/bitshares-core/pull/599 - reviewing now.

release:

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

- merge develop(release) into testnet https://github.com/bitshares/bitshares-core/pull/600
- bump the database https://github.com/bitshares/bitshares-core/pull/602
- update release ith db bump: https://github.com/bitshares/bitshares-core/pull/603
- approved merge release to master: https://github.com/bitshares/bitshares-core/pull/614
- doxyfile hotfix.

bitshares-core pull requests created:

- https://github.com/bitshares/bitshares-core/issues/518 - attemped to make a pull for this(https://github.com/bitshares/bitshares-core/pull/598) but it was bigger than expected, need hardfork and BSIP.
- attempt to create api call top markets https://github.com/bitshares/bitshares-core/pull/560 but we had no reached consensus on the utility, normalizing of data and security of the call so by now it is in the freezer.
- work in progress refactor api calls https://github.com/bitshares/bitshares-core/pull/628
- extended version commands https://github.com/bitshares/bitshares-core/pull/610 - merged.
- https://github.com/bitshares/bitshares-core/pull/614 - merged.
- https://github.com/bitshares/bitshares-core/pull/609 - merged.
- new api calls https://github.com/bitshares/bitshares-core/pull/676
- remove witness logs https://github.com/bitshares/bitshares-core/pull/680

others:

- participate in the bitshares-ui repo when needed: https://github.com/bitshares/bitshares-ui/issues/1161 - https://github.com/bitshares/bitshares-ui/issues/1150
- license discussion of fc: https://github.com/bitshares/bitshares-fc/pull/13
- https://github.com/bitshares/bitshares-core/issues/601 - resolved with ES.

documentation:

- https://github.com/bitshares/docs.bitshares.org/pull/26 merged
- proposing framework doc for api nodes https://github.com/bitshares/bitshares-core/issues/650
- added doxygen documentation link to main readme https://github.com/bitshares/bitshares-core/pull/634
- updated doxyfile https://github.com/bitshares/bitshares-core/pull/642
- https://github.com/bitshares/bitshares.github.io/pull/114
- desdcription to FC repo https://github.com/bitshares/bitshares-core/issues/651
- doxygen to fc repo https://github.com/bitshares/bitshares-fc/pull/12
- wiki updates at https://github.com/bitshares/bitshares-core/wiki/ElasticSearch-Plugin , https://github.com/bitshares/bitshares-core/wiki/private-testnet, https://github.com/bitshares/bitshares-core/wiki/Building-on-OS-X, etc.

bsip participation:

- https://github.com/bitshares/bsips/issues/52

python bitshares tools in oxarbitrage repo:

- https://github.com/oxarbitrage/bitshares-python-api-backend/issues/6 - updated database schema, closed the issue.
- https://github.com/oxarbitrage/bitshares-python-api-backend/pull/7 - changed spacing to unix among other clean up changes - merged.
- https://github.com/oxarbitrage/bitshares-python-api-backend/pull/8 - merged.
- https://github.com/oxarbitrage/bitshares-python-api-backend/pull/9 - refactorings merged.
- https://github.com/oxarbitrage/bitshares-python-api-backend/pull/10 - line endings merged.
- https://github.com/oxarbitrage/bitshares-python-api-backend/pull/11 - security merged.

explorer:

- added https://github.com/bitshares/bitshares-core/pull/455 to fix charts extremes.
- open sourced the explorer front end : https://github.com/oxarbitrage/open-explorer
- oppen issues: https://github.com/oxarbitrage/open-explorer/issues
- closed issues: https://github.com/oxarbitrage/open-explorer/issues

Offline oxarbitrage

i want to apologize with the stakeholders and community members in general because it had been close to 4 weeks now since my new worker proposal was approved and i promised reports here every 2 weeks that i didn't made yet. there are some reasons for this delay that i will like to enumerate:

- write this reports take time and the amount of work in the bitshares-core in the last month had been massive. as the days pass it is even harder to get all the info together on what was worked and i prefer to work fixing an issue than to actually spend time writing a report even if i know this is needed and in worker contract wrote by myself.

- the new upcoming worker proposal from @fox(https://bitsharestalk.org/index.php?topic=25968.0) will take care of informing the community about advances in the core. in talks with ryan about this, the reports about core work could be included in that worker but worker is coming out to voting much more later than i expected.

- the forum was down for about 1 week, this contributed to postpone the report writing.

none of this are excuses, just some facts.

all my activity is actually in github, i tried to find a tool that can simply get all my participation(pulls, comments, issues, wiki pages, merges, branches, etc) in a period of time for the repos i am involved in. i was not able to find such a tool, if someone known a tool that cab do it(commercial or free) please let me know.

in the meantime, i started to build a tool using github api that can get this info, this tool will be also of use for other workers and for github developers in general.

whatever is the case(with a tool or without it) i am posting the report of the last 4 weeks of work tomorrow Monday.

thanks for understanding and my apologizes again.

Offline sschiessl

  • Administrator
  • Hero Member
  • *****
  • Posts: 662
    • View Profile
  • BitShares: sschiessl
I might be able to help you out @CoinHoarder, write me a PM if you like

Offline CoinHoarder

  • Hero Member
  • *****
  • Posts: 660
  • In Cryptocoins I Trust
    • View Profile
Can I ask you a question? I don't know who better to ask... :'(

I am thinking of building a tradable card game that I am designing/coding already on top of Bitshares using UIAs.

From my Javascript/Node.JS/Meteor.JS web app I will need to only do two things:
1. Verify signed memos created in the Bitshares wallet
2. Check the blockchain to see if a specific account owns a certain UIA

I am thinking I need to use bitsharesjs, but there's not really any documentation that I can find. There is a little bit in the ReadMe, but not much info there.

Is there any chance that you could point me in the right direction to get me started? I have not worked with bitsharesjs before. I guess I need to use the Chain library for #2 and the ECC library for #1?

Thanks  :D
https://www.decentralized.tech/ -> Market Data, Portfolios, Information, Links, Reviews, Forums, Blogs, Etc.
https://www.cryptohun.ch/ -> Tradable Blockchain Asset PvP Card Game

Offline oxarbitrage


Offline R

  • Hero Member
  • *****
  • Posts: 1004
    • View Profile