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 ... 5 6 7 8 9 10 11 [12] 13
166
thank you all guys for the support, i am still needing a lot of votes to get approved but i am working on it, hope i can make it :)

167
Stakeholder Proposals / Re: Proxy: xeroc
« on: July 03, 2017, 11:48:38 am »
I justed voted for alfredo's worker, as I've seen him do incredible throughout the last months!

thanks, your support as proxy and individual is very appreciated!

168
thank you guys for the support, lets see how it goes in the next days :) very exited with the initial reactions.

169
hey fuzzy, will love to participate a few mins tomorrow to introduce my worker proposal https://bitsharestalk.org/index.php/topic,24540.0.html

let me know if that is possible :)

170
Stakeholder Proposals / Re: [Worker Proposal] New BitShares Core Dev
« on: June 29, 2017, 07:00:51 pm »
submitted worker proposal, pls check: https://bitsharestalk.org/index.php/topic,24540.0.html

171
Hi all, as some of you maybe already know by thread: https://bitsharestalk.org/index.php/topic,23698.0.html i had plans since a while on submitting my own worker proposal for the next half of 2017.

Proposal 1.14.55

Details at:

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

I used @xeroc multisig scheme to get paid in bitusd. I am looking for escrows, this are respectable community members that will hold the funds and vest to worker making  the whole process more secure for everybody. is needed to have a few of them. if anyone want to be part of that please let me know, i will appreciate a lot.

i don't have idea if it will be accepted, lot of uncertainty on my side right now. but the only way to know i guess is trying so here it is.

Now the proposal is public the document no further change will be made. the only addition from now on is to add the escrow accounts.

Any question, suggestion, whatever please let me know.

Wish me luck, vote for it if you can, will not regret.

looking to make the second half of the 2017 more successful than the first with hard work :)


172
General Discussion / Re: Cryptofresh update, feedback
« on: June 28, 2017, 12:05:39 pm »
Hi @roadscape and all, i am about to submit a worker proposal that includes work in the new explorer: http://bitshares-explorer.io:9009/#/dashboard.

the worker is mainly for bitshares core development, the explorer development is just 1 of the tasks i was planning to work on. i started to work in a block explorer when the community claimed for it by different channels. it is not my intention to compete with cryptofresh for a worker or anything like that. i really like cryptofresh and it is probably the bitshares company standard. if it is updated and open source my explorer project will never started.

in the other hand i will love to continue with bitshares-explorer.io. we can maybe find a solution working together somehow.

let me know.

173
thanks all, for all the suggestions and comments for the dashboard of the explorer. taking a bit from everyone i made a new version, visible here:

http://bitshares-explorer.io:9009/#/dashboard



please let me know what do you guys think.

the number indicators are now 6 and are:

- BLOCK NUMBER
- NEW USERS - users registered in current maint interval.
- BTS MARKET CAP
- BTS/BTC 24 HS VOL
- WITNESS COUNT
- ACTIVE WORKERS

Instead of having 1 chart in dashboard i extended to show 6 in tabs.  all charts is fake data by now but have the idea of what data i plan to display:

- operations - distribution of operations in current maint interval.
- speed - i have a few ideas for this in mind to show network speed. will have a more clear pic soon.
- top markets. show the most active markets in the DEX.
- smartcoins: show the most active smartcoins distribution according to 24 hs volume.
- uias: show the most active UIA distribution according to 24 hs volume.
- bts exchanges. show volume of bts in different exchanges.

live operations:

the table has remained the same as in previous version.

all comments welcome, everything can be changed! only dashboard suggestions are welcome by now, other sections will be discussed later.

thanks again!

174
As some of you already know, the following is a development version of a new blockchain explorer i had been working on:

http://bitshares-explorer.io

The thread purpose is to discuss what the community will like to see in the different sections of the explorer. Please note this is a pure dev version with bugs all around that i will be fixing, there is no guarantee the explorer will be up all the time either in this stage specially while making changes.

The technology behind and all that will be explained but i will like to get more input in regards to what to put here and there, ill take care by now on how to do it.

This is an open source project that will be uploaded fully to github with mit licence. The full code is not uploaded yet because it is messy to present it in the community. All code will be uploaded to:
https://github.com/oxarbitrage/bitshares-python-api-backend
and https://github.com/oxarbitrage/bitshares-explorer

With that said, lets start by making suggestions to the dashboard, here is a pic of what we have now:



We have 4 indicator boxes:
- block number - updated as operations came in real time, i think this is important and should stay.
- new users: is the accounts that the bitshares network made since the last maintenance time up to now. change to ?
- bts market cap. change to?
- 24 hs volume of bts/btc. change to ?

then we have the operation types chart. the plan was to have the types in current maintenance interval plotted but not sure if is relevant.

options can be:
- keep the chart. this is the dashboard, if we keep the chart there it needs to plot the most relevant data a bitshares user may want to see.
- chart can be removed and replaced with 4 more indicators. if so, what will be the complete list of 8 indicators the community will like to see here?

i don't suggest more than 8 indicators(or 4 and the chart) as it will push the real time operations table too much to the bottom of the page.

the operations table of the dashboard:
- i think it should stay as it is but open to suggestions to add/remove any column.

operation colors:

- the full list can be seen here:
http://bitshares-explorer.io:9009/#/fees

if anyone want to suggest the operation colors please send color for each op in hex format(#FFFFFF = white).

there is a lot to do but lets try to go over the dashboard first and move on section by section.

thank you very much for reading.

175
Stakeholder Proposals / Re: [Worker Proposal] New BitShares Core Dev
« on: June 23, 2017, 06:23:36 pm »
thank you for the kind words @Permie. I was a few days out of combat last week but all good now, thanks for asking.

In regards to the worker payment, Chris has not sent it yet but i am positive he will soon by the last talks i had with him. I am aware of the moment he is living with bitshares munich so i suppose he is busy in that matter.

The bitshares munich issue totally bypassed me, i don't have idea of who is the good and who is the bad if there is any, probably not that easy.

I appreciate and respect 2 of the involved parties, @kenCode actually introduce me here and i will be thankful with him for trusting in me forever. Chris was always in charge of payment and he never failed me. Ken proposed me to work with him now his work is resumed, chris also had some propositions for me with his new projects and i also had some other work offers in the last time that i could consider.

But I prefer to work for the chain because of several reasons, between ken and chris it is obvious there is not going to be any agreement, i have no problem of having my work fully exposed(right or wrong, i make a lot of mistakes) and i like the idea of depending on shareholders instead of single individuals or companies.

The blockchain is i think the place where i can be more efficient and i will do what i can to get that worker voted in even if i am not very good in human relations, politics and such. by the feedback on this thread i think i have good possibilities, i hope it this is the case :)

176
Stakeholder Proposals / Re: [Worker Proposal] New BitShares Core Dev
« on: June 22, 2017, 09:46:41 am »
thanks guys for the great support, i will submit the worker for voting in the next few days

177
Stakeholder Proposals / Re: [Worker Proposal] New BitShares Core Dev
« on: June 18, 2017, 01:12:33 pm »
Hey guys, here are some updates of the past week. i had been a bit less active this last week not because my worker is no longer active but actually because i was under a terrible flu that left me in bed for a few days.

still i was able to make some advances:

https://github.com/bitshares/bitshares-core/pull/312
have a few improves to make pointed by @abitmore but still better than nothing by now.

a few issues where i participated had been closed this last week:

https://github.com/bitshares/bitshares-core/issues/301
https://github.com/bitshares/bitshares-core/issues/307

and i was able to make some advances to explorer, can check how is is going at: http://bitshares-explorer.io:9009/#/dashboard
there is an explorer thread(https://bitsharestalk.org/index.php/topic,24097.0.html) where i plan to became more active. explorer helps improve the core.

As always, there is a lot to do, enough work to keep a team of devs busy in bitshares.

My worker ended and also vikram, the high price of bitshares was making the workers very expensive, i agree with the cut. My worker was not directly managed by me but actually by bitshares munich,. more specifically by Chris. Chris paid me part of the worker and now i should get the rest of it until the day it was stopped. I already pointed it to chris and he will send the rest to my account soon.

I plan to open a new worker in bitusd, i asked in the telegram devs channel about to form a team of core devs but that seems to go against the spirit of workers, they need to be individual and also even with the good moment of BTS it seems the chain is not able to pay a group of devs yet.

Please let me know what do you think about the following draft worker proposal idea:

Alfredo Garcia.

- Full time worker proposal. 8 hours per day Monday to Friday. 40 hs per week.
- 40 usd per hour. 320 usd per day. 1600 usd per week.
- Duration.  6 months.

Pros of working full time:

- Full dedication beyond the formal 8 hours per day. Work during the weekends when possible.
- No need to be in additional private projects at all(exclusivity to the chain).

 Tasks:

- Solution of problems in the c++ core of the bitshares. Add new features as requested/needed. Fixes, discussions with other core devs, planning of future changes, cli wallet. Hard to describe everything, it actually involves everything i can take care of.
- Explorer: Develop, maintain and publish bitshares explorer under bitshares. Open source - MIT.
- Add documentation. Contribute to wiki, help newcomers.
- Help with client side apps(python, javascript, etc)


Please guys let me know what do you think about something like that as a proposal, any suggestion or change please just shot.


178
guys i have a new open source explorer in development mode here:

http://oxarbitrage.com:9009/#/dashboard

Please do not limit the account history.

In cryptofresh.com you can see only one page of user history.
Do something like Steem Block explorer steemd.com.


thanks for the comment, the idea is not to limit but actually show everything in the final product. this is just limits added for development as it is easier by now to handle.

thanks again, i hope to came with some news at the end of the week in regards to advances in the explorer.

179
Stakeholder Proposals / Re: [Worker Proposal] New BitShares Core Dev
« on: June 11, 2017, 10:34:18 pm »
+5% thanks for the updates. Keep up the good work Alfredo.

thanks @Chris4210  :)

180
Stakeholder Proposals / Re: [Worker Proposal] New BitShares Core Dev
« on: June 11, 2017, 10:31:28 pm »
lot of stuff going on this last week in the core, here are the issues and pull requests where i was involved:

https://github.com/bitshares/bitshares-core/pull/288

the delayed node has been tested with the new code and it is working fine. still need to test the debug node, will do in the next days and most probably merge the code from @pmconrad to the master.

https://github.com/bitshares/bitshares-core/pull/297

final tests were made to merge this pull request by @abitmore, this is a great addition that allows a node to run with a lots less memory without loosing main functionality. the pull allows to add a number of operations each account can  have, this reduces memory drastically as most of the blockchain size is actually accounts for market making with millions of operations. great work here. the issue that started the code addition was also closed: https://github.com/bitshares/bitshares-core/issues/292

https://github.com/bitshares/bitshares-core/issues/285

closed issue as after research there is no issue except for a msg on closing a node. for this msg a new issue was opened to handle it: https://github.com/bitshares/bitshares-core/issues/303

https://github.com/bitshares/bitshares-core/issues/302

issue in the get_order_:book from the cli_wallet fixed in pull request: https://github.com/bitshares/bitshares-core/pull/304 merged.

https://github.com/bitshares/bitshares-core/issues/295

issue with clients that have 100 or more accounts. first, the node was subscribing to 99 accounts instead of 100. this was fixed here: 

https://github.com/bitshares/bitshares-core/pull/306

development node was up in order help issuer to recover his accounts while the problem is fixed. we are not in progress of removing the 100 accounts limitation from the core or adding a block in the UI to don't allow users to create more than 100 accounts. more progress on this probably during this next week.

https://github.com/bitshares/bitshares-core/issues/298

issue in the get_relative_account_history. it is being worked out at this pull: https://github.com/bitshares/bitshares-core/pull/305

https://github.com/bitshares/bitshares-core/issues/307

this issue has been addresses in the following pull requests: https://github.com/bitshares/bitshares-core/pull/310 and https://github.com/bitshares/bitshares-core/pull/309


 


Pages: 1 ... 5 6 7 8 9 10 11 [12] 13