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 ... 13
1
General Discussion / Re: suggestion on bitCNY rules update after BSIP42
« on: December 29, 2018, 04:21:03 pm »
now 3&4 have been done.

the committee has changed the force settlement offset of bitCNY from 5% to 2%, this will ensure that the possible discount of bitCNY will be less than 2%.

BSIP41 has been implemented, MSSR of bitCNY has been changed from 1.1 to 1.05.

the community suffer shortage of bitCNY for long time, to realize 1&2 it will also cost much time to reach consensus, create specification and do the implementation.

I am considering to draft 2 BSIPs that need not hard fork, just need witnesses to adapt their feeding script, but can get the purpose of 1&2.

BSIP A: request witnesses to ensure the feed price be higher than the global settlement price, to avoid the global settlement to happen.

BSIP B: change MCR base on worker proposal based poll, a "change MCR to x" WP and a "No change to MCR"poll will be created and wait for voting, witnesses need to change the fed MCR accordingly.

Thoughts?

In order to do B we need https://github.com/bitshares/bitshares-core/pull/1324 and hardfork or unintended margin calls will be(or not) triggered.

2
Stakeholder Proposals / Re: [Worker Proposal] CITADEL Desktop 2019
« on: December 29, 2018, 04:02:44 pm »
I think the bitshares blockchain, if the situation allows to do it, should fund this and other similar front ends for bitshares. IMHO specific and different software interacting with bitshares will get a greater number of people from different areas.

There will be people that will not use the reference ui to trade but maybe microdex, people that will not use the cli wallet but prefer for example citadel desktop and so on.

I like qt as it is cross platform, i was also thinking myself on a c++ cli wallet front end with qt. The initial idea i have is to interact with an rpc exposed cli_wallet backend, very basic. we can talk more about this.

We need to consider that a front end is always capable of making money by referring or registering users. So, the blockchain can maybe have some sort of "startup worker" that will give the worker a fixed X amount of bitusd(or whatever) and some bts to be used as faucet money.

In exchange bitshares will just request that the code is released under MIT. It will encourage workers to market their own products. The shareholders will of course :) only vote for the startups that will bring more benefit to the whole.

Just an idea ;)

By the way, you should post some screenshots so people can easy check what citadel is about.

3
a bug was found that caused the halt. working on it, patch should be out soon.

4
General Discussion / Re: suggest to disable forcesettlement for bitCNY
« on: November 07, 2018, 11:50:51 pm »
Without having an opinion in regards BSIP42 and related as they are beyond my understanding I really hope that the efforts from @abit are appreciated as i am sure he want the best for Bitshares as a whole. By what i saw in the last time his position and also @bitcrab are target of constant attacks, for the good of all us I hope rational consensus is achieved in this subjects that will allow bitshares to grow in the stable coin aspect, one of the most important pieces of our blockchain.

I believe Bitshares have the technology, experience and everything needed to be number 1 in the stable coin market, for this we should fight together as a community or die trying  :)

5
Please don't get me wrong, i do think is a good idea to have ways to visualize the data with good graphics, API calls and others.

However, the worker do not consider there is already a framework available to do it, can be communication problems, last changes to make it all possible are relatively new, etc.

Another issue i have with this worker is the price, even if you have to make it all from scratch i think the worker price is at least 3 times above common sense.

I will be happy to support a worker that consider this 2 points.

6
If you want to get how much asset was issued in a period of time you can filter the elasticsearch operations by operation_type 14(ASSET ISSUE) and by  operation_history.op_object.asset_to_issue.asset_id in a period of time, please check this link:
http://148.251.96.48:5601/app/kibana#/discover?_g=()&_a=(columns:!(_source),index:'357b9f60-d5f8-11e8-bb51-9583fd938437',interval:auto,query:(language:lucene,query:'operation_type:%2014'),sort:!(block_data.block_time,desc))

If you want to go after the feed prices of a smart asset you can filter by operation type 19 and smart asset id: http://148.251.96.48:5601/app/kibana#/discover?_g=()&_a=(columns:!(_source),index:'357b9f60-d5f8-11e8-bb51-9583fd938437',interval:auto,query:(language:lucene,query:'operation_type:%2019%20AND%20%20operation_history.op_object.asset_id:%201.3.113'),sort:!(block_data.block_time,desc))

In both kibana links you can change the timeframe in the upper right.

If you want to get market price changes you can go after the fill order and so on.

Also, when operations are not enough there is the es_objects plugin that will allow to export certain(currently predefined) specific objects; however i am making some changes to try to make it work with any blockchain object so for example you could get the internal ticker objects for a pair and get the current and past market prices from there.

I strongly believe that those 2 plugins are in the same direction you want to go.

7
In general i don't agree with this worker, here are some reasons:

- Cost. It cost almost 300k usd(288000 usd to be exact to do it).
- Limited. It is database specific, a new worker may came in saying mongodb or whatever is better for their specific needs.
- Closed to participate. No one except the bts.ai team can participate in the development.
- Closed source. It don't says anything that all the work will be open source and MIT license. Will bts.ai be open source and inside the bitshares organization ?
- Reinvent the wheel. The Elasticsearch plugin is working great and have all the data needed, the synchronization time is of 20 hours according to a last report, all the data inside operations is structured and available. That cost 0 to bitshares as it is already done. Doing the same from scratch using another database by a new team is IMHO a waste of resources. The core team, with the accumulated experience can do a postgres plugin in extremely reduced time if that is what the community needs. Also, the core team can pay a team or individual to do the plugin as plugins are core work and will need review and approval from core team members.
- Benefit. Besides having some better visualizations of some data which i think is important i don't see any other real benefit of the proposal.

In my opinion i will like to see some day a general worker that will do this and others in a bounty style, most of the API links mentioned are not being developed because there is  no funding to get developers on board. There is already a ruby project for bitshares at https://github.com/MatzFan/bitshares-ruby not being improved because of lack of funding, among many other dead projects.

I think that bitshares needs a worker proposal similar to the core worker where teams and individuals can participate in the development of different tools of the bitshares ecosystem.

It honestly looks to me like reinventing the wheel after all the work it has been done in this particular regard, discard everything and start from scratch instead of build on top of previous tools to save time, resources and advance.

Just my personal opinion, i don't have any voting power or influence to decide what is accepted or not.

8
voted for this one as i think is definitely a good idea to have bitshares exposed in this event.

9
is there any plan to send cards to south america again anytime in the future ?

10
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


11
Stakeholder Proposals / Re: [Worker Proposal] Bitshares UI Renewal
« on: July 25, 2018, 07:41:25 pm »
fully support this worker. voted for it.

there are obvious reasons for me to support it, i already know the team, it is the reference wallet, work here must continue.

but most important is that i was impressed with the improvements on the light wallet in the last time. i had an old version and installed the last just today, changes are notorious and all for good, everything i tried worked, something that was not the case time ago.

keep up the good work!


12
i like the idea of having more infrastructure with official worldwide nodes as proposed.

a few points to consider:
- there is no node in south america. i understand blockchain usage in general is not so popular here as other continents, still i think a node in Brazil or Argentina can bring some value.
- will you consider on hosting 1 elasticsearch node ? i think that if the wallet start using the feature we might need 1 more official node available(there is already 1 up from the BBF infrastructure worker rest is community members aka @clockwork).

price looks reasonable and APAsia already have a reputation in the community, i think it will go throw.

pd: also no node in Africa where the usage is probably even less than South America. Node in Hong Kong ?

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

14
just tried and it is working fine. make sure you use your account id(1.2.X) and not your name. should work.

15
This worker provokes me different sensations.

In one side, i strongly think a full redesign as proposed here is what bitshares needs. Since the beginning of the web front ends change all the time as technology advances in the field. All big players makes a full redesign of their web page once every 2 or 3 years. Start from scratch with a new foundation and direction can be the best thing to do if current foundation is obsolete.

For what i see in the audit and worker link it seems to me this team are professional enough to do the job.

In my humble opinion if we end up with a new modern UI as proposed the impact in BTS price will be direct, something stakeholders will want.

In the other hand, this particular worker does not end with a single line of code but just a (very valuable) preparation of what the team can do in a second worker, it kind of force the stakeholders to vote for this worker and the next one(no price yet).  Stakeholders need to think in at least double price(and double time) to get the final product.

Another thing that i think it could be handled a bit better is to create some sort of cooperation with the current UI worker, i understand that for the team having all in house is more efficient but we have current employees with their worker proposal expiring right now and with no possibility of joining the new project.

I understand this is a free market, competition is good but as part of the bitshares-core team, if a new worker proposal of this kind came into the core, i will maybe accept it but i will definitely don't like it.

Even with that, this stage of preparation will mean that everybody will be keep using the current UI for a while, this should give enough time to settle this things.

Great job overall, i like this worker and i will be probably voting it, i can offer myself as an escrow if needed, i am not a committee member but i am well known in the community.

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