Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - oxarbitrage

Pages: 1 2 [3] 4 5 6 7 8 9 10 ... 13
31
let me answer this @Spady007

in regards to the exporter, thanks for the notification. the elasticsearch server that the bitshares exporter uses to get data is at full disk so some of the last transactions are not getting inserted. i am requesting more disk at the server, then i need to replay the chain and will be working again, i'll update here.

1- for a list of assets if cryptofresh is down you can use http://open-explorer.io/#/assets(not complete list) or if you know the asset name or the id you can do http://open-explorer.io/#/assets/1.3.3027 or if you know the name do http://open-explorer.io/#/assets/NEXTCOIN

2- there are some problems pretty often with cryptofresh but there is a private project, we cant do anything for it. as an alternative you may use other explorers like the built in explorer of the reference wallet https://wallet.bitshares.org/#/explorer/blocks, the already mentioned open explorer(http://open-explorer.io/#/dashboard) or a new explorer project(https://bts.ai/?locale=en).

3- a list of operation number - operation name can be found at: http://open-explorer.io/#/fees

32
General Discussion / Re: Unfortunately, it seems clear to me ..
« on: March 17, 2018, 09:56:16 pm »
This will ultimately raise a few questions about the STEALTH token which is a FeeBacked Asset that has been given by Dan for the development of Stealth. If the backend devs where to continue its development using funds from the reserves, it would only be fair to re-evaluate how well those that currently hold STEALTH (those that have interest in its development and usage), performed in the last 2-3 years.
For me, it never made sense to work on STEALTH only so that some other people (STEALTH holders) can earn money of it.

thanks for the clarification, i didn't know it was like this.

also, with the new efforts from the BBF in being legally in order, i am unsure of the implications of full private transactions in that field.

i think @fox and the core team will have to review this item in the worker roadmap.

34
General Discussion / Re: Unfortunately, it seems clear to me ..
« on: March 17, 2018, 12:27:58 pm »
Confidential Transactions / Confidential Assets is an item in the new core worker proposal recently approved: http://www.bitshares.foundation/worker/budget/2018-03-bitshares-core

i think @fox is in conversations with @kencode in order to continue the development. don't have the details but i will not discard this feature.

35
General Discussion / Re: BTS dropped from Shapeshift? Alternatives?
« on: March 17, 2018, 12:23:00 pm »
i just add a msg in the spokesperson thread as according to the last report they are in communication with different exchanges.
 
we were delisted by a reason, cant remember why(techinical, legal, etc) https://bitsharestalk.org/index.php?topic=25143.msg316937#msg316937

we need to at least have the problem with shafeshift identified.



36
The third report of the BBF was updated

http://www.bitshares.foundation/announcements/2018-03-02-spokesperson-report

i like the approach. what about start conversations with https://shapeshift.io/ to get us back up ?

- bitrex: legal issues.
- poloniex: communication with them is impossible.
- shapeshift ?

37
I am trying to view my account activity
When I go to http://open-explorer.io/#/accounts/darkf0rce, I can see the first page of my activity but when I click on any other page, it comes back with a blank (it shows me total of 42 pages of activity)
Any suggestions?

seems there is a problem with the pagination . ill fix during this weekend among other things in the explorer. if you can pls submit an issue here as a reminder https://github.com/oxarbitrage/open-explorer/issues

thank you very much.

38
Stakeholder Proposals / Re: [Worker] - Ledger Nano S
« on: March 12, 2018, 01:31:07 pm »
contact @fox, the bitshares core manager, we need developers in the area, you can work on it under the existing worker.

39
General Discussion / Re: How to join the affiliate program?
« on: February 25, 2018, 10:15:23 pm »
to participate in the affiliate program you need to upgrade to lifetime member. from the wallet go to account -> membership.

you will see a button that says : Buy Lifetime Subscription

after you upgrade you will get a link in the same page: "Your referral link:"

Use the link for promotion in your banners, blog posts, newsletters, etc.

more info:

https://bitshares.org/referral-program/
http://docs.bitshares.org/bitshares/user/referral-program.html

40
This thread is open for discussion of the possible implementation of BSIP37 to allow numbers at the end of asset names:

https://github.com/bitshares/bsips/blob/master/bsip-0037.md

feedback is very welcome. thanks.

41
This thread is for discussion of a new proposed BSIP: https://github.com/bitshares/bsips/blob/master/bsip-0036.md

Any feedback/comment is appreciated. Will be good to include this in the next hardfork id BSIP is approved.

thanks.

42
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.

43
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

45
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.

Pages: 1 2 [3] 4 5 6 7 8 9 10 ... 13