BitShares Forum

Main => Stakeholder Proposals => Topic started by: Chris4210 on January 11, 2017, 08:33:22 pm

Title: [Worker Proposal] New BitShares Core Dev
Post by: Chris4210 on January 11, 2017, 08:33:22 pm
Dear BitShares Stakeholder,

We would like to introduce a new worker proposal that pays for a new BitShares core dev.

Please vote for Worker 1.14.49: Alfredo Garcia, Bitshares Core Dev
 
This Worker Proposal is for 6 months, and will include fixing Graphene Issues via github, and building the new features for the Bitshares platform and DEx that the community has been asking for.
 
Worker Details

Quote
Note from Chris4210:
We are calculating with a stable BTS price of 0.0033 BTS/USD, including a small security buffer for BTS price, voting volatility, etc. The Worker funds will be paid to our BitShares Munich (bitshares-munich-devs) account, and we will manage the regular monthly payouts to Alfredo.

*BitShares Munich will be paying half of his salary (see above), since increasing the security of the Bitshares platform also increases the security of our products such as BlockPay.

Short bio about Alfredo

The last 4 years Alfredo started working in the financial field making automated programs for Meta Trader, Ninja Trader, Calgo, Tradestation and other platforms. Then he moved a bit to binary options development, this is mainly Brokers that have web based API's so he started to make automated software that trade in binary options.
 
Most recently, he started to work with Bitcoin related projects. He started working for others at some online casinos and small projects but it was extremely hard to find serious people in the field. He has also worked for the Supernet "Iguana" project, helped them out quite a bit. Similar to the "Komodo" project.
 
Alfredo is under the supervision of, and reports daily to @kenCode at BitShares Munich.
 
Ken will post weekly updates in his usual thread here:
https://bitsharestalk.org/index.php/topic,22576.0.html
and Alfredo’s commits can always be monitored here:
https://github.com/kenCode-de?tab=repositories
 
Please vote for Worker 1.14.49: Alfredo Garcia, Bitshares Core Dev

Link to vote: https://bitshares.openledger.info/#/account/bitshares-munich-devs/voting/
Worker info: http://cryptofresh.com/workers


Thank you for your support!

Best regards, Christoph
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: kenCode on January 11, 2017, 08:53:39 pm
Alfredo is under the supervision of, and reports daily to @kenCode at BitShares Munich.

As you guys know, I am kind of a hardass. I will fire as fast as I hire, I have zero patience for slackers, so rest assured that the rest of my team will also be security auditing his work just like the other products that we have audited recently. Github issues, mem leaks, wiresharking, the works.
 
Getting a Core Dev for 6 months, for only ~$5K is a sweetheart deal.
 
Please vote for Alfredo, and as always my updates will be posted on his progress every week.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Chris4210 on January 11, 2017, 09:09:28 pm
How to vote for a BitShares worker in 30 seconds.

(http://i.giphy.com/26DOC8Lwghn0NdibC.gif)
(http://i.giphy.com/l4q8cBG5axNmMrpio.gif)
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Brekyrself on January 11, 2017, 10:50:10 pm
Let's make this happen.  The more successful workers the better.

I would like to see some sort of collaboration between the workers at this point so there is no major overlap.  SVK, Vikram, and Alfredo.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: BunkerChainLabs-DataSecurityNode on January 12, 2017, 01:12:40 am

This Worker Proposal is for 6 months, and will include fixing Graphene Issues via github, and building the new features for the Bitshares platform and DEx that the community has been asking for.
 

What exactly does this mean? There is room for a lot of clarifiaction:

Issues in github? There are plenty to go for a while, which ones are planned for with what milestones?
What new features specifically has the community been asking for?

Without a clear plan for work inefficiency creeps.

Looking forward to the reply.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: JonnyB on January 12, 2017, 03:19:21 am
Great stuff.
Have voted to approve this

and have put the word out on twitter  https://twitter.com/bitshares/status/819383789830934529
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: fav on January 12, 2017, 06:27:29 am

Without a clear plan for work inefficiency creeps.

this, please post a roadmap and get my vote :)
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: bitcrab on January 12, 2017, 08:53:55 am

This Worker Proposal is for 6 months, and will include fixing Graphene Issues via github, and building the new features for the Bitshares platform and DEx that the community has been asking for.
 

What exactly does this mean? There is room for a lot of clarifiaction:

Issues in github? There are plenty to go for a while, which ones are planned for with what milestones?
What new features specifically has the community been asking for?

Without a clear plan for work inefficiency creeps.

Looking forward to the reply.

exactly, please give the detail of the new features in the develop plan, there should be a process for the community to agree on adding new features.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Chris4210 on January 12, 2017, 09:21:58 am

This Worker Proposal is for 6 months, and will include fixing Graphene Issues via github, and building the new features for the Bitshares platform and DEx that the community has been asking for.
 

What exactly does this mean? There is room for a lot of clarifiaction:

Issues in github? There are plenty to go for a while, which ones are planned for with what milestones?
What new features specifically has the community been asking for?

Without a clear plan for work inefficiency creeps.

Looking forward to the reply.

exactly, please give the detail of the new features in the develop plan, there should be a process for the community to agree on adding new features.


I will post a roadmap for this worker. We want to start with the long issue list on Github first, and then move into building new features. Which features we should build will be discussed in the forum, and on the mumble.

Here is the latest feature list for the BitShares Blockchain. I collected most different ideas from chat, mumble and old forum posts/roadmaps.

The goal is to keep the list updated, and vote in the forum/mumble about the next feature.
https://docs.google.com/spreadsheets/d/1kgTYNEeqYP8xrEKBs2L0uc52xjQCPURuigI2CIplEtE/edit?usp=sharing

@ken can give a direct roadmap which of the 190 open github issues we are planning to fix first.


Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: ebit on January 12, 2017, 12:50:43 pm
 +5%
Turst
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: kenCode on January 12, 2017, 01:56:56 pm
What new features specifically has the community been asking for?

As Chris mentioned above, the mumble will help to finalize the roadmap. The outstanding issues on github really need to be cleaned up too, that's pretty obvious.
 
As for the new features that the community wants, let's start with the list that you started Data, the one we discussed on telegram. There's 5 or 6 items on it if I recall.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: santaclause102 on January 12, 2017, 03:38:26 pm
This is really great!! Thanks a lot for the initiative! I will update my proxy to whoever votes for this if necessary.

Feedback / questions:
1) Is there public information about Alfredo Garcia available besides his name? LInkedin, github etc?
2) I can not finally judge this as I am not a developer but did you think about a third party code reviewer such as Cryptonomex or Bunkerchainlabs? Or does Bitshares Munich hire one anyway? If so it would be nice if the results of these reviews and who did the review would be public as well. In the end such a review is effective if the reviewer has a reputation (to loose).

   
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: kenCode on January 12, 2017, 03:54:33 pm
This is really great!! Thanks a lot for the initiative! I will update my proxy to whoever votes for this if necessary.

Feedback / questions:
1) Is there public information about Alfredo Garcia available besides his name? LInkedin, github etc?
2) I can not finally judge this as I am not a developer but did you think about a third party code reviewer such as Cryptonomex or Bunkerchainlabs? Or does Bitshares Munich hire one anyway? If so it would be nice if the results of these reviews and who did the review would be public as well. In the end such a review is effective if the reviewer has a reputation (to loose).

 

1) No. Have faith in me and my team, I hope my track record speaks for itself at this point. I only work with the brightest minds in the world.
2) We have auditors on staff, and I always encourage the public to audit our code as well on my github repos. I totally agree with you about reviews too and welcome them here.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: santaclause102 on January 12, 2017, 04:31:54 pm
This is really great!! Thanks a lot for the initiative! I will update my proxy to whoever votes for this if necessary.

Feedback / questions:
1) Is there public information about Alfredo Garcia available besides his name? LInkedin, github etc?
2) I can not finally judge this as I am not a developer but did you think about a third party code reviewer such as Cryptonomex or Bunkerchainlabs? Or does Bitshares Munich hire one anyway? If so it would be nice if the results of these reviews and who did the review would be public as well. In the end such a review is effective if the reviewer has a reputation (to loose).

 

1) No. Have faith in me and my team, I hope my track record speaks for itself at this point. I only work with the brightest minds in the world.
2) We have auditors on staff, and I always encourage the public to audit our code as well on my github repos. I totally agree with you about reviews too and welcome them here.

I am all for this but why is there NO information about the dev? Not even a github acc?

EDit: It should be public anyway already since if he worked on "BlockPay, Smartcoins Wallet, C-IPFS, Stealth, Echo, Bridges and Gateways" as stated in the OP this activity should be on the respective github repos of the above projects?
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: btswildpig on January 12, 2017, 04:40:28 pm
i like the idea about not putting a entire "employee paycheck" on the blockchain, but rather a "subsidize request" from a community player.


i feel more comfortable to pay someone who is willing to take financial risk with bitshares to perform work on bitshares rather seeing it as a work place.

 +5% kencode
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Geneko on January 12, 2017, 06:25:28 pm

i feel more comfortable to pay someone who is willing to take financial risk with bitshares to perform work on bitshares rather seeing it as a work place.

 +5% kencode
I totaly agree.

As I understand proposition, it would be undefined overlap between existing workers, Soledgers, Svks and future Alfredo Garcias.
How they will divide jobs and responsibilities. BTW what are jobs and responsibilities of current workers? Is there any clear road map for them.
Can we track and measure theirs accomplishments?
Only one thing to tell about that, the accomplishment that isn't measured, it isn't improving.

I like the way @kenCode manages his projects, specially reports about his work. It should be "minimum standard behavior" for
all Bitshares Workers. Finally it is good thing for workers to compete between each other or find common ground and collaborate.
Either way community is on gain.

Beside subsidized request, kencode has offered us his reputation. In my opinion and with all respect to others, it is worth more.


Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Chronos on January 12, 2017, 07:04:46 pm
Beside subsidized request, kencode has offered us his reputation. In my opinion and with all respect to others, it is worth more.

It's funny, because KenCode had quite a poor reputation here a couple years ago. He was accused of scamming Floridans with a fraudulent gun school. There was an entire website with details about it. He was also accused of running a solar panel scam in 2007, where he never shipped the panels to buyers. More details can be found through a simple web search.

It's remarkable how that has changed. Thanks for sticking around, @kenCode!
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Chris4210 on January 12, 2017, 07:48:34 pm
Beside subsidized request, kencode has offered us his reputation. In my opinion and with all respect to others, it is worth more.

It's funny, because KenCode had quite a poor reputation here a couple years ago. He was accused of scamming Floridans with a fraudulent gun school. There was an entire website with details about it. He was also accused of running a solar panel scam in 2007, where he never shipped the panels to buyers. More details can be found through a simple web search.

It's remarkable how that has changed. Thanks for sticking around, @kenCode!

Hard works pays off and Ken has proven his skills and working ethics as an excellent development team leader. He has my full support.


i feel more comfortable to pay someone who is willing to take financial risk with bitshares to perform work on bitshares rather seeing it as a work place.

 +5% kencode
I totaly agree.

As I understand proposition, it would be undefined overlap between existing workers, Soledgers, Svks and future Alfredo Garcias.
How they will divide jobs and responsibilities. BTW what are jobs and responsibilities of current workers? Is there any clear road map for them.
Can we track and measure theirs accomplishments?
Only one thing to tell about that, the accomplishment that isn't measured, it isn't improving.

I like the way @kenCode manages his projects, specially reports about his work. It should be "minimum standard behavior" for
all Bitshares Workers. Finally it is good thing for workers to compete between each other or find common ground and collaborate.
Either way community is on gain.

Beside subsidized request, kencode has offered us his reputation. In my opinion and with all respect to others, it is worth more.




Hi Geneko,
each worker is targeting different sections of the codebase and of course the best practise will be to coordinate the tasks among them. While SVK is fousing on the front end, Soledger (Vikram) and Alfredo will focus more on the back end.

There are no worker standards yet. I would like to establish them now as soon as possible. One of the "minimum standard behavior" should be the weekly updates. More standards will come with time and experimentation with workers.








Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: serejandmyself on January 12, 2017, 08:44:32 pm

This Worker Proposal is for 6 months, and will include fixing Graphene Issues via github, and building the new features for the Bitshares platform and DEx that the community has been asking for.
 

What exactly does this mean? There is room for a lot of clarifiaction:

Issues in github? There are plenty to go for a while, which ones are planned for with what milestones?
What new features specifically has the community been asking for?

Without a clear plan for work inefficiency creeps.

Looking forward to the reply.

exactly, please give the detail of the new features in the develop plan, there should be a process for the community to agree on adding new features.


I will post a roadmap for this worker. We want to start with the long issue list on Github first, and then move into building new features. Which features we should build will be discussed in the forum, and on the mumble.

Here is the latest feature list for the BitShares Blockchain. I collected most different ideas from chat, mumble and old forum posts/roadmaps.

The goal is to keep the list updated, and vote in the forum/mumble about the next feature.
https://docs.google.com/spreadsheets/d/1kgTYNEeqYP8xrEKBs2L0uc52xjQCPURuigI2CIplEtE/edit?usp=sharing

@ken can give a direct roadmap which of the 190 open github issues we are planning to fix first.

This is great. I would propose to cut in all into small sprints and prioritize the list (some things there are really important and some are just "wishes"). Because that roadmap is not for 6 months, its more. So, this would make things easier imo (but you pobably know this without me  ;) )
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Geneko on January 12, 2017, 09:19:11 pm
Beside subsidized request, kencode has offered us his reputation. In my opinion and with all respect to others, it is worth more.

It's funny, because KenCode had quite a poor reputation here a couple years ago. He was accused of scamming Floridans with a fraudulent gun school. There was an entire website with details about it. He was also accused of running a solar panel scam in 2007, where he never shipped the panels to buyers. More details can be found through a simple web search.

It's remarkable how that has changed. Thanks for sticking around, @kenCode!

Nobody is perfect  ;)
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: vikram on January 12, 2017, 09:54:20 pm
Alfredo is under the supervision of, and reports daily to @kenCode at BitShares Munich.

As you guys know, I am kind of a hardass. I will fire as fast as I hire, I have zero patience for slackers, so rest assured that the rest of my team will also be security auditing his work just like the other products that we have audited recently. Github issues, mem leaks, wiresharking, the works.
 
Getting a Core Dev for 6 months, for only ~$5K is a sweetheart deal.
 
Please vote for Alfredo, and as always my updates will be posted on his progress every week.

This is really great!! Thanks a lot for the initiative! I will update my proxy to whoever votes for this if necessary.

Feedback / questions:
1) Is there public information about Alfredo Garcia available besides his name? LInkedin, github etc?
2) I can not finally judge this as I am not a developer but did you think about a third party code reviewer such as Cryptonomex or Bunkerchainlabs? Or does Bitshares Munich hire one anyway? If so it would be nice if the results of these reviews and who did the review would be public as well. In the end such a review is effective if the reviewer has a reputation (to loose).

 

1) No. Have faith in me and my team, I hope my track record speaks for itself at this point. I only work with the brightest minds in the world.
2) We have auditors on staff, and I always encourage the public to audit our code as well on my github repos. I totally agree with you about reviews too and welcome them here.

I have great faith in Ken and support this worker, especially for this price. I think BitShares should encourage as much new developer activity as it can.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Chris4210 on January 13, 2017, 04:11:13 pm
I have great faith in Ken and support this worker, especially for this price. I think BitShares should encourage as much new developer activity as it can.

Thank you for your support Vikram. We are looking forward to work with you together and to improve the platform.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Chris4210 on May 13, 2017, 08:20:12 am
Dear BitShares Community,

today I got some awesome news for you all. After a few talks with Alfredo, Xeroc and others we came to the conclusion that Alfredo has become a very valuable member of our community and his past few months of hard work have paid off. Alfredo is now an active member of our BitShares community and has contributed a lot to the BitShares code base, its security and its future.

I am happy to transfer Alfredo the first part of his BTS worker salaries for the time frame: January 23th, 2017 to May 13th, 2017.
In total: 1,180,210 BTS
Outstanding: -450,625 BTS
In total: 1,630,835 BTS

http://cryptofresh.com/tx/86f46f20f741d67191626cb361692d9fbdd34fa1

Next payout day: July 26th, 2017

Thank you all for your support for Alfredo´s worker and I am looking forward to more of his great work.

Best regards,

Christoph
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: fav on May 13, 2017, 08:48:17 am
Dear BitShares Community,

today I got some awesome news for you all. After a few talks with Alfredo, Xeroc and others we came to the conclusion that Alfredo has become a very valuable member of our community and his past few months of hard work have paid off. Alfredo is now an active member of our BitShares community and has contributed a lot to the BitShares code base, its security and its future.

I am happy to transfer Alfredo the first part of his BTS worker salaries for the time frame: January 23th, 2017 to May 13th, 2017.
In total: 1,180,210 BTS
Outstanding: -450,625 BTS
In total: 1,630,835 BTS

http://cryptofresh.com/tx/86f46f20f741d67191626cb361692d9fbdd34fa1

Next payout day: July 26th, 2017

Thank you all for your support for Alfredo´s worker and I am looking forward to more of his great work.

Best regards,

Christoph

one second, you just paid him 1,180,210 BTS $43000k off of the worker fund instead of $4800 Worker + $4800 BitShares Munich?

- where is the burn TX for 1039428 BTS?
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Chris4210 on May 13, 2017, 09:11:47 am
Dear BitShares Stakeholder,

We would like to introduce a new worker proposal that pays for a new BitShares core dev.

Please vote for Worker 1.14.49: Alfredo Garcia, Bitshares Core Dev
 
This Worker Proposal is for 6 months, and will include fixing Graphene Issues via github, and building the new features for the Bitshares platform and DEx that the community has been asking for.
 
Worker Details
  • Total Cost of hiring Alfredo: 3,261,671 BTS (~9600 USD at $20/hr)
  • This Proposed 6-month Worker will cost Bitshares 1,630,835 BTS (~4800 USD)
  • *BitShares Munich will pay the other half, ~4800 USD
  • Worker Lifetime: 6 months, (Jan 23 - Jul 23, 2017)
  • Working Hours: 20h per week
  • Worker focus on the 190 Github Issues, and new BitShares features from BitShares Roadmap (https://docs.google.com/spreadsheets/d/1kgTYNEeqYP8xrEKBs2L0uc52xjQCPURuigI2CIplEtE/edit?usp=sharing)


@fav, Please see the initial proposal. The worker is quoted in BTS, not in USD.

I agree with you if the worker would have been quoted in USD, then the leftover BTS would have been burned or repaid to the pool. That is not the case with this worker.

Alfredo fully deserves his payout, since he worked many hours for the BitShares community as core dev and is highly motivated to continue.

If the future BitShares workers should be nominated in BTS or in BitUSD like Xeroc´s worker is up to all of us to decide.


Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: fav on May 13, 2017, 09:14:26 am
Dear BitShares Stakeholder,

We would like to introduce a new worker proposal that pays for a new BitShares core dev.

Please vote for Worker 1.14.49: Alfredo Garcia, Bitshares Core Dev
 
This Worker Proposal is for 6 months, and will include fixing Graphene Issues via github, and building the new features for the Bitshares platform and DEx that the community has been asking for.
 
Worker Details
  • Total Cost of hiring Alfredo: 3,261,671 BTS (~9600 USD at $20/hr)
  • This Proposed 6-month Worker will cost Bitshares 1,630,835 BTS (~4800 USD)
  • *BitShares Munich will pay the other half, ~4800 USD
  • Worker Lifetime: 6 months, (Jan 23 - Jul 23, 2017)
  • Working Hours: 20h per week
  • Worker focus on the 190 Github Issues, and new BitShares features from BitShares Roadmap (https://docs.google.com/spreadsheets/d/1kgTYNEeqYP8xrEKBs2L0uc52xjQCPURuigI2CIplEtE/edit?usp=sharing)


@fav, Please see the initial proposal. The worker is quoted in BTS, not in USD.

I agree with you if the worker would have been quoted in USD, then the leftover BTS would have been burned or repaid to the pool. That is not the case with this worker.

Alfredo fully deserves his payout, since he worked many hours for the BitShares community as core dev and is highly motivated to continue.

If the future BitShares workers should be nominated in BTS or in BitUSD like Xeroc´s worker is up to all of us to decide.

it's not a matter of deserve or not. you quoted USD, which makes sense, or why did you not add BTS amount to your half? when did you add your half to his pay by the way (1.6m BTS)?
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: pc on May 13, 2017, 09:20:50 am

Alfredo fully deserves his payout, since he worked many hours for the BitShares community as core dev and is highly motivated to continue.


+1 Good job!

@fav  note that $20/hr is far below market rate for a skilled developer, plus Alfredo was taking a risk AND showing his commitment by accepting payment in BTS.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: fav on May 13, 2017, 09:22:09 am

Alfredo fully deserves his payout, since he worked many hours for the BitShares community as core dev and is highly motivated to continue.


+1 Good job!

@fav  note that $20/hr is far below market rate for a skilled developer, plus Alfredo was taking a risk AND showing his commitment by accepting payment in BTS.

again, it's not a matter of deserve. this is a company and we hire based on contract.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: fav on May 13, 2017, 09:26:54 am

@fav, Please see the initial proposal. The worker is quoted in BTS, not in USD.


quoting again for visibility.

Quote
This Proposed 6-month Worker will cost Bitshares 1,630,835 BTS (~4800 USD)
*BitShares Munich will pay the other half, ~4800 USD

using the logic "quoted in BTS" - I'm still missing a second 1100000 BTS transaction from @Chris4210 since they agreed on paying the other half.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Geneko on May 13, 2017, 11:57:40 am
I think they made the dill with Alfredo in USD and accepted the risk of BTS fluctuations. Otherwise worker would be payed to Alfredo's account. They probably made new arrangement with Alfredo since BTS has appreciated. Alfredo probably accepted that generous offer. Who wouldn't?
 
As far as Bitshares concern the dill is clear. Same is related for all payments from Bitshares blockchain. Regarding management of Bitshares company, it is bad dill. That is why we spend so many discussions regarding witness and workers pay denominated in bitUSD.
Next time pay closer attention to those discussions and act accordingly.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: oxarbitrage on May 13, 2017, 12:30:46 pm
hello guys, Alfredo here :)

@Geneko is right, when i started the worker proposal was covering around 2 hours of my rate. Bitshares Munich hired me for 4 hours at first and then upgraded me full time. BTS price was growing but they had to put money at first. With current bitshares prices @Chris decided to give me the full money up to today of the worker and i of course accepted it.  The rest of the worker at the end of it. This money is mine, very happy :)

I was hired by kencode while invoices always went to chris, i don't want to say much about the current drama as i actually don't know much more than what it is already public. i appreciate and respect both sides so i just hope they can find a solution, for the good of the community and because i have several colleagues in the bitshares munich that don't have the luck of having an active worker proposals and were working in bitshares munich private repos.

i hope the solution is finally near in order for this people to resume work. whatever is the result, if people is going to loose their jobs they better if they just know it but i hope no talent escapes as some people will be very hard to replace.

@kenCode used to write about my advances on his weekly report, i will do it by myself now. i agree in weekly reports in a minimum we workers will have to do. there should be some kind of advances always in 1 week. My work is mainly in github core issues, all the coding action of the bitshares community is in github issues and developer telegram channel.

We have 90 issues open right now,  new issues coming in every day and the bts price gets higher more work is needed. Plenty of stuff to do and the group of core devs is very small. We do all we can every day, the people that already know me know this is true.

As i gain more experience i can make more bigger changes to the core, move faster in the issues, basically i am becoming a graphene blockchain expert.

Next post is the advances from my side for the last week, any question pls let me know.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Permie on May 13, 2017, 12:54:46 pm
hello guys, Alfredo here :)
Great to hear from you Alfredo.
I am glad that reserve pool funds are being used to employ a core developer and reinvest reserve funds in the BitShares platform.
Great to hear you are pleased with your current level of compensation too

Keep up the good work :)

EDIT: I didn't read the previous-page discussion with fav. Now I have.
Unsure how I feel about the current level of core developer pay.
I hope Bitshares can retain as many core devs as is needed for a reasonable price.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Geneko on May 13, 2017, 01:20:05 pm
@oxarbitrage

Glad all going well for you. Looking forward to new updates!
I am sure @fav will agree.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Permie on May 13, 2017, 04:56:35 pm
I think they made the dill with Alfredo in USD and accepted the risk of BTS fluctuations. Otherwise worker would be payed to Alfredo's account. They probably made new arrangement with Alfredo since BTS has appreciated. Alfredo probably accepted that generous offer. Who wouldn't?
 
As far as Bitshares concern the dill is clear. Same is related for all payments from Bitshares blockchain. Regarding management of Bitshares company, it is bad dill. That is why we spend so many discussions regarding witness and workers pay denominated in bitUSD.
Next time pay closer attention to those discussions and act accordingly.

From another thread:
@xeroc is paid with bitUSD.
https://bitsharestalk.org/index.php/topic,23770.0.html
http://cryptofresh.com/u/multisig-worker-2017-01

BTW Just noticed that escrow account has set its own proxy which perhaps shouldn't be: that BTS doesn't belong to them.
Quote
    Every thing that is not paid out after the end of the worker will be settled and returned to the reserve fund

BTS 2.0 shareholders need to be sure that the worker-proposal-contract is rock-solid leak proof before signing/voting for it.
There is a need for some 'BitShares lawyers' (the proxies?) to make sure the terms of the worker proposal are clear to the shareholders.
The issue is that BitShares Munich made a gentleman's agreement with the BTS 2.0 shareholders.
The shareholders have no means of enforcing that section of the contract. The terms written by Chris in the proposal are indeed ambiguous, and perhaps should never have passed the vote.
If BTS had a team of lawyers advising the shareholders, I don't think they would have reccomeneded signing it in it's presented form.
BTS shareholders are likely to be majority-bullish on the price of bts.
Surely this exact scenario should have been forseen?

At the time of the original worker proposal, Chris should have been lobbied to state the intention/soft-obligation of BitShares Munich on how to compensate Alfredo in co-operation with BTS reserve fund.
Were BitShares Munich committing to paying $4800 per month? Or were they committing to match the financial contribution made by BitShares 2.0 shareholders?
These terms were not present or explained thoroughly in the contract.
Legal contracts and paperwork are tediously comprehensive, long and boring to read for a reason.

If BitShares Munich had not been involved, and the contract was between Alfredo himself and BitShares 2.0 shareholders, then the terms would be simple.
"Complete work to the subjective satisfaction of the BitShares shareholders and you will receive x bts per month."
Then after a huge price rise, shareholders may find it prudent to renegotiate the employment contracts it holds with employees.

Should this worker proposal, employing Alfredo, be voted out?
The Shareholders could then wait patiently for a new proposal with payment in bitUSD to be submitted by Alfredo.
Depending on his demands for compensation I am sure the shareholders will be pleased to re-hire a talented BitShares literate core dev.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Geneko on May 13, 2017, 05:23:36 pm

If BitShares Munich had not been involved, and the contract was between Alfredo himself and BitShares 2.0 shareholders, then the terms would be simple.
"Complete work to the subjective satisfaction of the BitShares shareholders and you will receive x bts per month."
Then after a huge price rise, shareholders may find it prudent to renegotiate the employment contracts it holds with employees.

Should this worker proposal, employing Alfredo, be voted out?
The Shareholders could then wait patiently for a new proposal with payment in bitUSD to be submitted by Alfredo.
Depending on his demands for compensation I am sure the shareholders will be pleased to re-hire a talented BitShares literate core dev.

I think same is related to Bitshares Munich Worker proposal. If someone thought it is overpriced it might be voted out. I don't see a problem here?

Main point here with BTS denominated payouts is price risks. The one who accepts the price risk, rips rewards and losses. At least in theory. There are many problems mixing payment for work and price risks. They are two different kinds, one is work another is speculation. If worker suddenly finds out he is payed less then normal (price depreciation) he stops work. The opposite is not the case. Why? Because of flaw in Bitshares worker model.

We need to separate those and that is why we need payment for workers and witnesses denominated in bitUSD.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: vegolino on May 13, 2017, 08:07:34 pm

@fav, Please see the initial proposal. The worker is quoted in BTS, not in USD.


quoting again for visibility.

Quote
This Proposed 6-month Worker will cost Bitshares 1,630,835 BTS (~4800 USD)
*BitShares Munich will pay the other half, ~4800 USD

using the logic "quoted in BTS" - I'm still missing a second 1100000 BTS transaction from @Chris4210 since they agreed on paying the other half.
I agree with fav,  if we are paying  Alfredo in BTS so should Bitshares Munich.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: oxarbitrage on May 13, 2017, 08:17:27 pm
i agree that future worker proposals by me or actually by anyone should be in usd. i never had the intention to speculate here, the fact is i found at with all this by pure luck. i have no problem on closing current proposal now and go with a new one if needed. in the other hand the extra compensation will be used to bring more value to the community by working more, much more happy. it is hard to quantify  this additional value in money but you can be sure i will be always grateful with this community and be forever loyal.

this is a new milestone in my life and my professional career that will definitely want to develop here, not only for the payment of the current worker, i made a commitment with myself pretty much since i started, i want to be here.

will i make the same work for less money ? a reasonable hourly rate ? probably. but living with a rope in the neck every month is hard and stressfull, the worker money at current bts prices will remove big pressure i have over my shoulders while at the same time finish my new office and buy new equipment. this will bring value, i am not going to be needing to make extra businesses for extra money, fully dedicated to bitshares with everything i have.

will i enjoy my new computer equipment to lets say watch a movie ? of course i will, but the important is that i will use it for work in bitshares, will improve productivity.

i don't want to spend more of your time on why i will like to leave the worker proposal as it is, it is obvious that i need/want the money but the decision is yours and whatever you decide i will agree with it.



Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: oxarbitrage on May 13, 2017, 08:55:52 pm
Every week, i will post the most relevant tasks i worked on in the last 7 days. A few considerations:

- chats in the developer channels, dramas and such will not be reported unless an issue in github is opened or some big time consuming event is happening.
- working in the bitshares core is a challenge for me, all the testing needed after every change, all the research, takes an enormous amount of time even when the final result may be change 1 line of code or even none.
- issues in general end up being resolved in waves, it could be a week when not much more issues are actually closed or code merged, this issues can be all resolved in the next one with much more reports. Whatever is the case, with issues closed or not closed i will always post on what issues i am working on.
 
////////////////////////////

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

This issue was already replied but was rebumped by the following issue:

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

Working with @abitmore we created a new function for the cli wallet to get the relative history. This ended up with a pull request that was merged to the master here:

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

While doing this we found that the node call for get_relative_history was buggy, this was fixed in this pull request, also merged:

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

and https://github.com/bitshares/bitshares-core/pull/281

This function is of big importance for client side applications.

////////////////////////////

In another issue: https://github.com/bitshares/bitshares-core/issues/243

This was already researched also by me and replied to initial question but @xeroc asked if a result could be added to the operations that have missing results. A proof of concept was added here:

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

that proof of concept modifies the node get_block function to add a history object in the results of a transfer operation. This will be reviewed by @xerox when he gets the time. The pull request will not be merged as it is but it is the only way i have to show code changes to others.

////////////////////////////

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

A research in the cashback_test fee tests was done to be able to reply to that issue. 3 options were proposed to the developer community on how to proceed with the findings. This was a good issue to introduce myself into the bitshares test units.
I don't fully know all the core yet and the issues help to move over different parts and functionality.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Permie on May 13, 2017, 09:24:58 pm
i agree that future worker proposals by me or actually by anyone should be in usd. i never had the intention to speculate here, the fact is i found at with all this by pure luck. i have no problem on closing current proposal now and go with a new one if needed. in the other hand the extra compensation will be used to bring more value to the community by working more, much more happy. it is hard to quantify  this additional value in money but you can be sure i will be always grateful with this community and be forever loyal.

this is a new milestone in my life and my professional career that will definitely want to develop here, not only for the payment of the current worker, i made a commitment with myself pretty much since i started, i want to be here.

will i make the same work for less money ? a reasonable hourly rate ? probably. but living with a rope in the neck every month is hard and stressfull, the worker money at current bts prices will remove big pressure i have over my shoulders while at the same time finish my new office and buy new equipment. this will bring value, i am not going to be needing to make extra businesses for extra money, fully dedicated to bitshares with everything i have.

will i enjoy my new computer equipment to lets say watch a movie ? of course i will, but the important is that i will use it for work in bitshares, will improve productivity.

i don't want to spend more of your time on why i will like to leave the worker proposal as it is, it is obvious that i need/want the money but the decision is yours and whatever you decide i will agree with it.
I think Alfredo's perspective is worthy of consideration.
Thank you for articulating it Alfredo

Is now a good time for BitShares to be nailing down the bottom line?
Or should bts be bootstrapping the community with loyal talent while BTS is still in the startup phase?
I would like to see early wealth created by BitShares to go to passionate members of the community.
But I would not like to economically hinder the project for some feel good fuzzies.
Conundrum.

How Alfredo's compensation continues from here is very much up for debate but I would not like to see any ill feeling towards a dedicated contributor to the project.
1.1Million BTS sounds like a whole lot, but at the same time sweat-equity from talented, skilled people is also essential for the project to succeed.

I can't code, I could learn, but I would not learn for a low payrate.
Perhaps Alfredo is one of the very few people who is an enthusiast, who can ALSO do technical work to make the theoretical possibilities of BitShares a reality.
But if BTS wants to attract talent, otherwise uninterested workers would be drawn to find out more about the project. Would they bring their family and friends with them?
What is the value of BitShares having a reputation for generosity?
Vs Having a reputation for being hard-nosed (justified or not).
Public perception is important.

Had this rally waited an extra month to get going, Alfredo would have been paid $4800 worth of bts (or would it be $9600 worth of bts?).
Should the timing of the rally make such a difference?
If you (impersonal) think the contract should originally have been paid in bitUSD, then at the time did you lobby for the contract to be changed or not approved?
If so, the shareholders voted against your advice.

If there is fault with the contract it is between BitShares 2.0 shareholders and BitShares Munich, and not Alfredo.

One way to view the Reserve pool is to view it through a monetary-inflation lens. That the shareholders are willing to expend 0.xxxx% of BitShares' wealth on ensuring that the ecosystem is maintained and grows to meet the needs of the BitShares customers.

Worker proposals paid in bts vs worker proposals paid in bitUSD.
One side wants price stability... the other wants to monetize their labour to invest/speculate on the price of bts.
I see no way it could be done, but this scenario does sound a lot like the market for shorts vs longs CfD for the creation of bitUSD. How perfect would it be if the market created a CfD that fascilitated worker payment in bitUSD.
I.e without the need for a multisig account
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: oxarbitrage on May 13, 2017, 10:40:41 pm
when i started to work in here by @kenCode i saw the worker proposal for me, i had no idea of what it was, and it was going to be impossible for me to discuss the terms or setup one and get it voted in at that moment. Bitshares Munich did it.
Not much time later i realized that the idea was awesome, i saw other worker proposals like @sivek and @xeroc and i wanted to be like them in the future, have a worker proposal for good money that will keep me busy and stable for months while doing what i do best and what i enjoy more: hard coding work.
i agree in what it was stated before by @Geneko , if a developer is speculating and winning like it is my case now then everything will be great, if a developer is speculating and losing he will probably need to move on. speculation is for people who haves money, that is why i think now that the worker proposal in bitusd could be a good option to consider specially for new developers trying to get in. but i do think that now, not when i started as i didn't even know what bitusd was at that point.

bitshares speculation for a developer is not pure speculation as you are an insider, you know whats going on and you have some idea that prices may go higher, yuou are actually helping to get the prices higher. for some developers that already know how bitshares works being in this kind of speculation may be very good, for someone outside the community it may be safer to have usd.  i personally believe in bitshares and for prices to keep raising.

anyways, it is a complex subject, i can help with my view but not much more than that.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Pheonike on May 14, 2017, 07:51:22 pm
I have no problem with the deal in its terms. I just want know if Munich paid their half in bts. Since it was a 50/50 contract. If Munich paid less then we should be returned the difference.

Sent from my SM-N920T using Tapatalk
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: lil_jay890 on May 15, 2017, 07:56:33 pm
In my opinion the worker proposal system is fine the way it is... It is similar to the way many companies compensate their employees, via stock options.  It provides incentive for the developers to do good work and promote the ecosystem.

Startups provide stock based compensation because it works.  It brings in the best talent, because it promotes greed.  Also, it's not like this recent price pump didn't factor in the worker proposal system.  The market knew that the dev's would get a dramatic bump in salary but bought anyway. 
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Yao on May 16, 2017, 03:53:22 am
In my opinion the worker proposal system is fine the way it is... It is similar to the way many companies compensate their employees, via stock options.  It provides incentive for the developers to do good work and promote the ecosystem.

Startups provide stock based compensation because it works.  It brings in the best talent, because it promotes greed.  Also, it's not like this recent price pump didn't factor in the worker proposal system.  The market knew that the dev's would get a dramatic bump in salary but bought anyway.

Agree. The limited shares in the reserve pool (reserve balance is less than 1 billion now ) should not be measured in Fait ( USD, CNY or others ), BTS should be distributed in the manner of startups' stock.

Here are some views:
A normal flow of bounty is:
Shareholders feedback the demand firstly, then the committee is responsible for summarizing these demands and organizing voting to create bounty, then waiting for people to submit their work, then shareholders decide whether the work is qualified for bounty or not.


刚想到一个 bounty 金额由投票决定的思路:

首先,根据 bounty 任务的难度和工作量进行分级,给定不同的赏金系数。


任务等级分类参考(从高到低):
Quote
SS级:也是最高级,在不同地方用法不同,但通常在关乎生死存亡阶段使用。属于只许成功不许失败的任务。
S级:此类任务通常不被使用,这类任务一般是关乎上级或者公司的直接利益的任务。
A级:使用较为频繁,通常是于珍贵物品或上级人物直接或间接挂钩。
B级:使用最为频繁的一类任务。也是最常见的一类任务。
C级:较为简单的任务。也是除了SS级最少发的任务。
D级:作为最简单的任务,这类人物属于刚加入的新手。也被叫做休闲任务。


以当前的“预算项目(worker)”投票情况来说,#1 worker 获得 375,721,810 BTS支持。我们可以以此为基础来确定每一个任务的 bounty 赏金系数。例如:

SS 级任务:1%,意味着 bounty 金额为:375w BTS
S 级任务:0.5%,意味着 bounty 金额为:187.5w BTS
A 级任务:0.25%,意味着 bounty 金额为:93.75w BTS
B 级任务:0.1%,意味着 bounty 金额为:37.5w BTS
C 级任务:0.05%,意味着 bounty 金额为:18.75w BTS
D 级任务:0.025%,意味着 bounty 金额为:9.375w BTS


其次,有两种方案来投票确定每一个任务的 bounty 赏金额度:

方案一:股东投票决定奖金额度

创建一个预算项目(worker),根据任务等级描述 bounty 系数,系数乘以支持该任务的总票数等于完成任务后可领取的 BTS 数量。


方案二:基础悬赏金额 + 额外奖励

由理事会根据任务难度议定 bounty 基础金额(在比特股这家公司里面,理事会成员的责任感更强,要么是大股东,要么看好公司前景,理事会来商定 bounty 的基础金额是有说服力的)。

额外的奖赏额度则由全体股东投票,同样采用方案一的方式,但 bounty 系数要降低到大约 1/10,系数乘以支持该任务的票数等于额外奖赏。在任务进行中,领取任务者随时公布动态,股东根据情况予以投票支持(类似打赏),额外的奖赏代表股东对该任务完成度的认可度!


在上面的两个方案中,BTS 股东支持这个项目就投票,投票就代表愿意稀释(从储备资金池支取 BTS),每一票(每一股 BTS)都代表要花钱,每一票都代表股东的意愿。至于手里总共有 100w 票但只想出 30w 票权重的投票支持,那就自己单独把 300w 票现转到自己的小账号里去投票支持对应的 bounty 项目。

以上想法,仅供交流讨论!



I've just had a great idea that could determine the amount of bounty for each task by the VOTE of  BTS holders:

First of all, according to the classification of bounty task difficulty and workload, given different reward coefficient.

Task level from high to low like this:

Quote
SS: Highest tasks, is of vital importance must not fail.
S: Super tasks, related to the vital interests of the company.
A: Major tasks.
B: Frequent tasks.
C: Relatively simple tasks.
D: The simplest tasks, leisure tasks.


In the current project proposal vote situation, #1 worker got 375,721,810 BTS support, we can use this result as a base to determine the bounty coefficient for each task.

For EXAMPLE:

SS Task: 1%, means bounty amount = 3,750,000 BTS
S Task: 0.5%, means bounty amount = 1,875,000 BTS
A Task: 0.25%, means bounty amount = 937,500 BTS
B Task: 0.1%, means bounty amount = 375,000 BTS
C Task: 0.05%, means bounty amount = 187,500 BTS
D Task: 0.025%, means bounty amount = 93,750 BTS


Then, voting to determine the amount of bounty for each task in two ways:

Plan A: only BTS holders vote to determine the amount

Creat a project proposal(worker), describe the task level and the bounty coefficient,
[total number of votes]*[bounty coefficient]=[the amount of BTS for bounty].


Plan B: Basic task reward + Extra bonus

Committee discuss to determine the basic reward according to the difficulty of the task
( in the Company, BitShares DAC, committee members are more responsible, because they are either major shareholders, or is extremely optimistic about the prospects of BitShares, they discuss the amount of the decision is convincing).

Extra bonus can refer to Plan A to creat a project proposal(worker), but need to reduce the coefficient to about 1/10,
[basic task reward]+[total number of votes]*[bounty coefficient]=[the amount of BTS for bounty].
In the task, at any time to publish the dynamic, BTS holders to vote according to the circumstances, extra bonus on behalf of shareholders to the task completion degree of recognition.

In Plan A and B, BTS holders who support the bounty task, vote it. Vote for it means they they are willing to accept dilution ( agree to withdraw BTS from reserve pool), 1 BTS 1 vote, each BTS vote represents the wishes of shareholders. If I have 1,000,000 BTS in my account A, but I only want to vote it 300,000 BTS, I can transfer 300,000 BTS to account B then vote it.

Above is my idea for exchange discussion.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Permie on May 16, 2017, 10:15:35 am
I like how this sounds @Yao

...but I need reminding what the vote threshold is for a worker proposal to get filled?

There must be a minimum amount of votes required to pass a worker?
Does this minimum amount of votes set a floor price of worker funding, according to your model?

Quote
D Task: 0.025%, means bounty amount = 93,750 BTS

i.e if a Class D task is up for vote, the minimum amount of bts this worker could get paid (and yet still get funded) would be
FUNDING,F = (F = 0,) or F > [minimum number of votes required to pass worker] * [93,750bts]

?
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: oxarbitrage on May 20, 2017, 12:15:06 pm
Hi guys, here some updates of the last week of work, no new code was merged to the core this time but advance as always was done.

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

research on this issue revealed that the fix was already commited to master. @vikram closed.

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

@pmconrad suggest to make the fees fully work in the  cashback_test, if the hardest option of the 3 presented last week. working on it.

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

significant amount of time of the week was invested in this issue: alternatives to dropping connections(witness shutdown). discussions were done in telegram. expect alternative is good enough for this purposes except that it can't retain command history, waiting for an issue close.

////////////////////////////

The following issues are in folder and they will be probably have answer in the next few days leading to possible closes and pull requests:

https://github.com/bitshares/bitshares-core/issues/71
https://github.com/bitshares/bitshares-core/issues/25
https://github.com/bitshares/bitshares-core/issues/136

////////////////////////////


Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: oxarbitrage on May 28, 2017, 09:20:06 pm
almost forgot to place some updates here.

i started to code a bitshares blockchain explorer in this last week and i invested most of time on that. the details can be found in the bitshares explorer post at:

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

all updates in regards to the blockchain explorer will go in that thread.

as the community is really needing an opensource blockchain explorer i decided to take this past week to get the project started.  even that i was fully in the explorer there were a few core issues where i was involved:

https://github.com/bitshares/bitshares-core/issues/291
tested, closed, false alarm.

several issues related to the node memory were updated and discussed this last week as, the main memory discussion issue in github is at:
https://github.com/bitshares/bitshares-core/issues/192

@pmconrad made a pull request to add partial operations support to the node(https://github.com/bitshares/bitshares-core/pull/289).
@abitmore is propossing a node setup where only the last X transactions or blocks from an account may be returned.
@ElMato and I were discussing in telegram alternatives to export the history data to some kind of database. this will also release the nodes from memory usage.

https://github.com/bitshares/bitshares-core/pull/288
this is a great addition by @pmconrad that allows to disable/enable plugins from the command line. please note that in order to leave the history plugins our of a node and reduce memory the nodemaster need to edit code main.cpp witness_node file and comment them out, compile and run again.
the pr will allow to do this from command line, i am in the process of reviewing it for merging.


So this starting week i am getting back fully to the core issues and try to make some more significant advances.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: oxarbitrage on June 04, 2017, 06:39:43 pm
updates from last week in the bitshares core. the following are issues/pull request where i participated during last week:

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

following the efforts to reduce memory usage in nodes while still be able to serve basic api usage @abitmore proposed a new feature in the form of command line to just get an X amounts of operations from each account significantly reducing the node memory usage.

details in pull request:

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

i tested and it is working great, the pull request is about to be merged to master.

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

i am after a few new api calls for the explorer to relate history that is right now not possible and needed for explorers and other apps. the pull still need some more work that it is in progress and requires first that pull #297 gets merged as it will use an index created in that code.
after #297 is merged i will upload new code in a new pull request with updated calls.

this new calls can be a generic way to solve:

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

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

reviewing pull request from @pmconrad. still in progress.

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

making progress in this issue, awaiting further response to make a small code change to solve it.


Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Chris4210 on June 10, 2017, 09:59:08 am
 +5% thanks for the updates. Keep up the good work Alfredo.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: oxarbitrage 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


 

Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: oxarbitrage on June 11, 2017, 10:34:18 pm
+5% thanks for the updates. Keep up the good work Alfredo.

thanks @Chris4210  :)
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: lil_jay890 on June 12, 2017, 11:50:05 am
+5% thanks for the updates. Keep up the good work Alfredo.

Maybe @Chris4210 could follow Alfredo's lead and give an update on blockpay??

I've sent a pm, gone on the discord channel as well as posted here multiple times looking for an update...

Sorry for being off topic, but this is the only place I see Chris commenting
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: oxarbitrage 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.

Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: btswolf on June 18, 2017, 01:32:49 pm
Good job, good proposal draft.
I think if you want to form a team around you that would be possible too.
Keep on rocking.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: pc on June 21, 2017, 09:33:55 am
Thanks for your work, Alfredo!

I think your proposal is very reasonable and I will support it.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: xeroc on June 21, 2017, 09:46:06 am
- 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.
+5%!!!
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: fav on June 21, 2017, 09:55:05 am
- 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.
+5%!!!

 +5% I'll vote for that
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: paliboy on June 21, 2017, 11:26:55 am
@oxarbitrage it looks good, I will support it.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Troglodactyl on June 21, 2017, 12:38:25 pm
Excellent.  Sounds good to me.
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: oxarbitrage 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
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: Permie on June 23, 2017, 12:12:41 pm
- 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.
+5%!!!

 +5% I'll vote for that
+5%

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.
Has Chris FORWARDED (not paid) you the money yet?

The BTS shareholders voted to compensate YOU Alfredo. It's your money. Not BitShares' Munich's.
They offered to MATCH the compensation that BTS paid YOU.
They/Chris should not be taking a single BTS from your worker proposal.

I am very very happy that you are still coding away and working hard for the shareholders Alfredo.
 +5% +5% +5% to you! :)

I will be very glad if the shareholders vote to employ you full time and bring you onboard, with no boss except the shareholders.

I hope you're feeling better after your illness!
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: oxarbitrage 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 :)
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: blockchained on June 24, 2017, 11:11:46 pm
- 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.
+5%
Title: Re: [Worker Proposal] New BitShares Core Dev
Post by: oxarbitrage on June 29, 2017, 07:00:51 pm
submitted worker proposal, pls check: https://bitsharestalk.org/index.php/topic,24540.0.html