BitShares Forum
Main => Stakeholder Proposals => Topic started by: xeroc on February 11, 2016, 09:22:23 am
-
Dear shareholders,
The first few weeks of 2016 have been quite exciting but feel like nothing compared to what is yet to come and within reach. With the most recent developments about
* the proposed fee schedule
* the proposed 0-fee options as well as BSIP#10
* as well as a proposal for advanced bitassets (thanks tonyk)
there is still plenty of work to be done, let alone all the development around the backend, GUI, and complementary libraries.
Additionally, it turned out that not only newcomers need to be supported when they first get in touch with BitShares and Graphene, but also the existing community needs quite some education about what is possible already and how things are technologically interconnected.
Sooner or later this task will be covered by professional consulting businesses that are already forming around the blockchain business in general and the Graphene technology in particular (nothing more can be said yet). In the meantime, I would like to offer my services around technical support and documentation to every community member and shareholder as a part of a worker on the blockchain.
Furthermore, a second worker has been created to fund my ongoing work on the python libraries. Quite some features are yet not well exposed neither to the python libraries and need to be integrated. Additionally, I would like to continue developing a python bot infrastructure that makes applying bot strategies to the DEX as well as arbitrage with our assets a lot easier.
Both workers have a starting date that is after the termination of my
current worker, pay a total of €3000 (2k+1k) for a total of 20h/week (though it might well end up to be again more than that), are limited by 4 months and vest their pay for 90 day.
As usual, the detailed job application can be found on github
https://github.com/xeroc/worker-proposals/blob/master/2016-02.md
and has a PGP signature next to it. You can verify the content has been signed by me using
gpg --verify 2016-02.md.sig
I'd appreciate your votes for 1.14.31 and/or 1.14.32!
-
Full support! +5%
-
Very valuable services!
-
Looks good! +5%
-
bump ..
and I offer a 25 bitUSD bounty for a proper translation of the OP into Chinese!
-
You deserve every bit of it. Thank You!
-
I support this and thank you for all your help +5%
-
This worker proposal needs to be supported.
-
bump ..
and I offer a 25 bitUSD bounty for a proper translation of the OP into Chinese!
IMO you don't need that. The ones who really care will read English or ask liable people to translate for them. For the others, Google translate is good enough. Alt will advertise for you, although perhaps negative advertisements.
-
+5% thank you for all you've done and all you keep doing! You're an invaluable asset for this community, and it definitely feels right that you're paid by the blockchain to enhance it :D
-
I like 25 bitUSD bounty and will translate the OP into Chinese!
尊敬的比特股东家
给你们拜个晚年，新年以来的最近几周，我们离目标触手可及，但还差0.01公分。现在，我们在进行如下工作：
（1）手续费改革
（2）以BSIP#10为代表的零手续费选项
（3）高级的比特资产（感谢tonyk的工作）
除了这三项重要而紧急的工作，我们还有大量的次优先级的工作,更别提围绕后台开发的界面（译者注：此前cass申请区块链工人，投票未通过）和库优化补充了。
另外，不仅新人在接触了比特股后，需要补脑比特股和石墨烯的知识，就算社区的熟面孔，也时常需要学习：系统已经实现的功能和相关的技术关联。
虽然，迟早，这项工作会被专业的区块链资讯企业接手，特别是石墨烯技术（恕商业机密，不可多言）。但是，“比特股系统太复杂了”这种此起彼伏的抱怨萦绕于耳畔，我们是掩耳不闻，还是积极应对？中国社区的东家们在社交媒体上做了很多工作，然，这还远远不够。我想为社区东家们提供“技术支持和文档”服务，并领取一份区块链工资。
另外，我还想再领一份工资，进一步完成 python库。比特股系统就像翡翠原石，我们都知道里面有无价之宝，但是缺少打磨机，而我正在偷偷开发的python库就是打磨机。而且，我还要开发一个基于python的内置机器人，便于比特资产的交易。
跟东家张嘴有些冒昧了，我已经建立了四个工人，目前启动了其中两个的投票，虽然野心有点大，但我确实想多干活。BM这个管家现在太抠门，我们都瘦了，他家的猫都开始吃老鼠了。虽然如此，不管您是否投票支持，我都很高兴您能看完我的申请，因为，我也有东家的身份，我懂。
两份工作，需要合计支付3000欧元（2000+1000），每周保证20小时的工作量（虽然我技术杠杆的，但，这也是保守数字），4个月完成。工资释放期90天。更多细节，在：https://github.com/xeroc/worker-proposals/blob/master/2016-02.md ，PGP加密验证，使用：gpg --verify 2016-02.md.sig
最后，还是衷心祝愿您能给 1.14.31 和或 1.14.32投票！
Worker Proposal
工人提议
BitShares 2.0 has come a long way and is heading towards one of the most robust, and flexible ecosystems that mankind has yet seen. However, quite some auxiliary work has yet to be done and I would like to offer my time and expertise and continue contributing to the BitShares ecosystems on many different fronts.
比特股2.0已经走过了漫长的道路,正朝着其中一个最强劲、灵活的生态系统方向走去,作为人类，你肯定还没有见过。然而，一些辅助性的工作也要有人做，所以，我愿意拿出些时间贡献于比特股系统的方方面面。
Summary of previous work
亮一下我以前的业绩
As of this writing, I have had an active worker for the first 6 weeks of 2016 and have achieved the following goals:
我下面罗列的这些，是我上一个工人已经完成的（2016年前6周）：
- Python 库
- 136次提交
- 加行数： 8699 ；删行数：5716 ；合计：2983
- 文档
- 55次提交
- 加行数：4396 ；删行数：1361 ；合计：3035
- 界面
- 6次提交
- 加行数：257 ；删行数：184 ；合计：63
- BSIPs（BitShares改进方案和协议）
- 6次提交
- 加行数：49 ；删行数：52 ；合计：-3
- 委员会/建议:
- 14次提交
- 加行数：644 ；删行数：165；合计：479
- 委员会/说明:
- 139次提交
- 加行数：2893 ；删行数：494；合计：2399
- 测试网
其他工作,如github评论、网络讨论及论坛支持因为很容易就不列举了。
基于我之前和现在的工作,因为我想把更多的时间放在BitShares,我特此申请区块链工人。
Shareholder Summary
股东总结
2月末，我手头的工作就完成了。但我仍想贡献时间于比特股系统，并且是集中而连续的。并希望新的工作始于3月1日，以达到衔接。为了便于股东区分，我申请了两份工作（细节见下文），同时，因为税务的原因，我的申请账户变成了 pay.xeroc 而不再是 xeroc. 补充一点，这次的薪水释放期为90天。
Distinct Workers
有点不一样的工人
之所以有点不一样，是因为，这两个工人，共享每周20小时的工作量。描述如下：
- 如果两个工人都被录用了
我将合理分配每周20小时的工作时间，确保完美的完成工作
- 如果其中一个被录用
我将分配每周10小时的工作时间给被录用的工人，并将工作成果公布给社区；另外那个工人的工作成果，我将对外收费。
- 如果都被拒绝
工作成果将不以公益品的形式提供给社区，谁用谁付费。
Worker 1: Documentation and Technical Support
工人1：文档和技术支持
此工作将从3月1日起，持续4个月。申请的薪水为1000欧元，每周10小时工作时间。根据0.00300 €/BTS的单价，可以计算：
1,000 €/4 weeks/10h = 25,00€/h
1,000 €/mtl * 322 BTS/€ = 322,000 BTS/mtl
322,000 BTS/mtl / 30 days = 10733.33333 BTS/day
即，每日支付1,073,333,333 'satoshi'.因为，这个薪水标准并不高，所以，如果BTS涨价了，也不需要烧币减少支付。
Tasks
任务
Documentation
文档
- 增强集成文档，添加更多细节。便于不同模式下的交易者查阅。
- 增加API稳定，目前API已经相当复杂了，文档工作没有跟上，同时，我们要寻找各种途径普及中心化API和去中心化API的区别。
- 增加用户引导文档，如操作多重签名和设置账户，这需要各种形式的说明和教程。
- 增强客户端界面的内置文档，目前的帮助文档只有基本内容，还有很多功能没有做说明。
- 维护BitShares改进方案和协议，其需要更多的优化结构和指导方针以及正式描述。这些需要随着时间的增长而不断地发展和成长,因此很长一段时间的投入。
Technical Support
技术支持
- 在论坛等地方帮助新人及资产发行人解疑答惑。
- 为见证人提供和改进工具。
- 协调社区事务（组织、费用计划、统计数据），很多答案就藏在DAC(去中心化自组织)的数据里，我想帮助大家找出这些数据，并对DAC做出改善。
Worker 2: Python Library and Applications
工人2：Python 库和应用
Tasks
任务
Python 库
- 交易API（可以很容易的集成到比特股钱包交易所里）
- 序列化签署交易（非链offchain交易）
- 预测市场库(管理预测市场)
- 提案库（管理提案）
应用
- 自动交易算法的基础设施
- 区块链索引数据库
- 对事务和费用进行统计分析
- 消息签名工具
-
What's going on? Your current worker proposal is the most accepted one, but two new proposals have negative amount of votes. Who are voting against these and why?
-
What's going on? Your current worker proposal is the most accepted one, but two new proposals have negative amount of votes. Who are voting against these and why?
See https://cryptofresh.com/ballots
Anti-dilution. https://bitsharestalk.org/index.php?topic=21317.0
-
Both workers have a starting date that is after the termination of my
current worker, pay a total of €3000 (2k+1k) for a total of 20h/week (though it might well end up to be again more than that), are limited by 4 months and vest their pay for 90 day.
I think €3000 is for each month? Or it's a total for 4 months?
-
Both workers have a starting date that is after the termination of my
current worker, pay a total of €3000 (2k+1k) for a total of 20h/week (though it might well end up to be again more than that), are limited by 4 months and vest their pay for 90 day.
I think €3000 is for each month? Or it's a total for 4 months?
1,000 €/4 weeks/10h = 25,00€/h
1,000 €/mtl * 322 BTS/€ = 322,000 BTS/mtl
322,000 BTS/mtl / 30 days = 10733.33333 BTS/day
-
I like 25 bitUSD bounty and will translate the OP into Chinese!
尊敬的比特股东家
给你们拜个晚年，新年以来的最近几周，我们离目标触手可及，但还差0.01公分。现在，我们在进行如下工作：
（1）手续费改革
（2）以BSIP#10为代表的零手续费选项
（3）高级的比特资产（感谢tonyk的工作）
除了这三项重要而紧急的工作，我们还有大量的次优先级的工作,更别提围绕后台开发的界面（译者注：此前cass申请区块链工人，投票未通过）和库优化补充了。
另外，不仅新人在接触了比特股后，需要补脑比特股和石墨烯的知识，就算社区的熟面孔，也时常需要学习：系统已经实现的功能和相关的技术关联。
虽然，迟早，这项工作会被专业的区块链资讯企业接手，特别是石墨烯技术（恕商业机密，不可多言）。但是，“比特股系统太复杂了”这种此起彼伏的抱怨萦绕于耳畔，我们是掩耳不闻，还是积极应对？中国社区的东家们在社交媒体上做了很多工作，然，这还远远不够。我想为社区东家们提供“技术支持和文档”服务，并领取一份区块链工资。
另外，我还想再领一份工资，进一步完成 python库。比特股系统就像翡翠原石，我们都知道里面有无价之宝，但是缺少打磨机，而我正在偷偷开发的python库就是打磨机。而且，我还要开发一个基于python的内置机器人，便于比特资产的交易。
跟东家张嘴有些冒昧了，我已经建立了四个工人，目前启动了其中两个的投票，虽然野心有点大，但我确实想多干活。BM这个管家现在太抠门，我们都瘦了，他家的猫都开始吃老鼠了。虽然如此，不管您是否投票支持，我都很高兴您能看完我的申请，因为，我也有东家的身份，我懂。
两份工作，需要合计支付3000欧元（2000+1000），每周保证20小时的工作量（虽然我技术杠杆的，但，这也是保守数字），4个月完成。工资释放期90天。更多细节，在：https://github.com/xeroc/worker-proposals/blob/master/2016-02.md ，PGP加密验证，使用：gpg --verify 2016-02.md.sig
最后，还是衷心祝愿您能给 1.14.31 和或 1.14.32投票！
Worker Proposal
工人提议
BitShares 2.0 has come a long way and is heading towards one of the most robust, and flexible ecosystems that mankind has yet seen. However, quite some auxiliary work has yet to be done and I would like to offer my time and expertise and continue contributing to the BitShares ecosystems on many different fronts.
比特股2.0已经走过了漫长的道路,正朝着其中一个最强劲、灵活的生态系统方向走去,作为人类，你肯定还没有见过。然而，一些辅助性的工作也要有人做，所以，我愿意拿出些时间贡献于比特股系统的方方面面。
Summary of previous work
亮一下我以前的业绩
As of this writing, I have had an active worker for the first 6 weeks of 2016 and have achieved the following goals:
我下面罗列的这些，是我上一个工人已经完成的（2016年前6周）：
- Python 库
- 136次提交
- 加行数： 8699 ；删行数：5716 ；合计：2983
- 文档
- 55次提交
- 加行数：4396 ；删行数：1361 ；合计：3035
- 界面
- 6次提交
- 加行数：257 ；删行数：184 ；合计：63
- BSIPs（BitShares改进方案和协议）
- 6次提交
- 加行数：49 ；删行数：52 ；合计：-3
- 委员会/建议:
- 14次提交
- 加行数：644 ；删行数：165；合计：479
- 委员会/说明:
- 139次提交
- 加行数：2893 ；删行数：494；合计：2399
- 测试网
其他工作,如github评论、网络讨论及论坛支持因为很容易就不列举了。
基于我之前和现在的工作,因为我想把更多的时间放在BitShares,我特此申请区块链工人。
Shareholder Summary
股东总结
2月末，我手头的工作就完成了。但我仍想贡献时间于比特股系统，并且是集中而连续的。并希望新的工作始于3月1日，以达到衔接。为了便于股东区分，我申请了两份工作（细节见下文），同时，因为税务的原因，我的申请账户变成了 pay.xeroc 而不再是 xeroc. 补充一点，这次的薪水释放期为90天。
Distinct Workers
有点不一样的工人
之所以有点不一样，是因为，这两个工人，共享每周20小时的工作量。描述如下：
- 如果两个工人都被录用了
我将合理分配每周20小时的工作时间，确保完美的完成工作
- 如果其中一个被录用
我将分配每周10小时的工作时间给被录用的工人，并将工作成果公布给社区；另外那个工人的工作成果，我将对外收费。
- 如果都被拒绝
工作成果将不以公益品的形式提供给社区，谁用谁付费。
Worker 1: Documentation and Technical Support
工人1：文档和技术支持
此工作将从3月1日起，持续4个月。申请的薪水为1000欧元，每周10小时工作时间。根据0.00300 €/BTS的单价，可以计算：
1,000 €/4 weeks/10h = 25,00€/h
1,000 €/mtl * 322 BTS/€ = 322,000 BTS/mtl
322,000 BTS/mtl / 30 days = 10733.33333 BTS/day
即，每日支付1,073,333,333 'satoshi'.因为，这个薪水标准并不高，所以，如果BTS涨价了，也不需要烧币减少支付。
Tasks
任务
Documentation
文档
- 增强集成文档，添加更多细节。便于不同模式下的交易者查阅。
- 增加API稳定，目前API已经相当复杂了，文档工作没有跟上，同时，我们要寻找各种途径普及中心化API和去中心化API的区别。
- 增加用户引导文档，如操作多重签名和设置账户，这需要各种形式的说明和教程。
- 增强客户端界面的内置文档，目前的帮助文档只有基本内容，还有很多功能没有做说明。
- 维护BitShares改进方案和协议，其需要更多的优化结构和指导方针以及正式描述。这些需要随着时间的增长而不断地发展和成长,因此很长一段时间的投入。
Technical Support
技术支持
- 在论坛等地方帮助新人及资产发行人解疑答惑。
- 为见证人提供和改进工具。
- 协调社区事务（组织、费用计划、统计数据），很多答案就藏在DAC(去中心化自组织)的数据里，我想帮助大家找出这些数据，并对DAC做出改善。
Worker 2: Python Library and Applications
工人2：Python 库和应用
Tasks
任务
Python 库
- 交易API（可以很容易的集成到比特股钱包交易所里）
- 序列化签署交易（非链offchain交易）
- 预测市场库(管理预测市场)
- 提案库（管理提案）
应用
- 自动交易算法的基础设施
- 区块链索引数据库
- 对事务和费用进行统计分析
- 消息签名工具
Thanks .. i am currently in amsterdam and cant access my account .. you'll get your bitusd on monday (latwst tuesday)
Thanks!!
-
Both workers have a starting date that is after the termination of my
current worker, pay a total of €3000 (2k+1k) for a total of 20h/week (though it might well end up to be again more than that), are limited by 4 months and vest their pay for 90 day.
I think €3000 is for each month? Or it's a total for 4 months?
good catch .. it is indeed monthly .. (if both are approved)
-
As it turns out, I am in a fortunate position that I don't need to work
for 25€/h for BitShares any longer but can take the jobs that pay me
$50/h somewhere else.
However, for BitShares shareholders (and they certainly have
speculated on a different outcome), I can no longer offer my services
for you for free any longer as I am freelancing in the blockchain
space and need to eat.
Since worker proposals can neither be deleted nor modified after
creation, you are still in a lucky position because I promised to work
for the conditions of these workers shall they be approved.
From the shareholder's point of view, this is your chance to get me work
for BitShares at this low rate. Take it or leave it.
As for my current worker, I see my obligations as fulfilled as I have
put way more than 20h/w for the last two months. Once the older worker
terminates, I will no longer be available for technical support or
documentation unless someone can pay for it.
To @alt and those that have set him as proxy: It is unfortunate that
none of you, nor @alt has joined any discussion to make this happen and
since you obviously don't appreciate the work I have put into BitShares
for free for the last 2 years, I see no reason to help you reach your
ROI while I am left behind.
-
As it turns out, I am in a fortunate position that I don't need to work
for 25€/h for BitShares any longer but can take the jobs that pay me
$50/h somewhere else.
However, for BitShares shareholders (and they certainly have
speculated on a different outcome), I can no longer offer my services
for you for free any longer as I am freelancing in the blockchain
space and need to eat.
Since worker proposals can neither be deleted nor modified after
creation, you are still in a lucky position because I promised to work
for the conditions of these workers shall they be approved.
From the shareholder's point of view, this is your chance to get me work
for BitShares at this low rate. Take it or leave it.
As for my current worker, I see my obligations as fulfilled as I have
put way more than 20h/w for the last two months. Once the older worker
terminates, I will no longer be available for technical support or
documentation unless someone can pay for it.
To @alt and those that have set him as proxy: It is unfortunate that
none of you, nor @alt has joined any discussion to make this happen and
since you obviously don't appreciate the work I have put into BitShares
for free for the last 2 years, I see no reason to help you reach your
ROI while I am left behind.
If you've already found a new job, I just want to say: congratulations! And great thanks for the work and efforts you've ever done for BitShares.
-
If you've already found a new job, I just want to say: congratulations! And great thanks for the work and efforts you've ever done for BitShares.
Thanks you .. that offer is for about 20h/h which would still leave room for BitShares and I'd love to continue my work on/with BitShares
-
:D yes
I miss it
-
As it turns out, I am in a fortunate position that I don't need to work
for 25€/h for BitShares any longer but can take the jobs that pay me
$50/h somewhere else.
However, for BitShares shareholders (and they certainly have
speculated on a different outcome), I can no longer offer my services
for you for free any longer as I am freelancing in the blockchain
space and need to eat.
Since worker proposals can neither be deleted nor modified after
creation, you are still in a lucky position because I promised to work
for the conditions of these workers shall they be approved.
From the shareholder's point of view, this is your chance to get me work
for BitShares at this low rate. Take it or leave it.
As for my current worker, I see my obligations as fulfilled as I have
put way more than 20h/w for the last two months. Once the older worker
terminates, I will no longer be available for technical support or
documentation unless someone can pay for it.
To @alt and those that have set him as proxy: It is unfortunate that
none of you, nor @alt has joined any discussion to make this happen and
since you obviously don't appreciate the work I have put into BitShares
for free for the last 2 years, I see no reason to help you reach your
ROI while I am left behind.
If you've already found a new job, I just want to say: congratulations! And great thanks for the work and efforts you've ever done for BitShares.
You don't sound too concerned with this situation. What is your problem?
-
As it turns out, I am in a fortunate position that I don't need to work
for 25€/h for BitShares any longer but can take the jobs that pay me
$50/h somewhere else.
However, for BitShares shareholders (and they certainly have
speculated on a different outcome), I can no longer offer my services
for you for free any longer as I am freelancing in the blockchain
space and need to eat.
Since worker proposals can neither be deleted nor modified after
creation, you are still in a lucky position because I promised to work
for the conditions of these workers shall they be approved.
From the shareholder's point of view, this is your chance to get me work
for BitShares at this low rate. Take it or leave it.
As for my current worker, I see my obligations as fulfilled as I have
put way more than 20h/w for the last two months. Once the older worker
terminates, I will no longer be available for technical support or
documentation unless someone can pay for it.
To @alt and those that have set him as proxy: It is unfortunate that
none of you, nor @alt has joined any discussion to make this happen and
since you obviously don't appreciate the work I have put into BitShares
for free for the last 2 years, I see no reason to help you reach your
ROI while I am left behind.
If you've already found a new job, I just want to say: congratulations! And great thanks for the work and efforts you've ever done for BitShares.
You don't sound too concerned with this situation. What is your problem?
I don't think I have any problem. I'm just happy that xeroc has stable income now. Isn't it a good thing?
-
Thanks
That "stable income" is however not going to bring much value to BitShares ..
-
Thanks
That "stable income" is however not going to bring much value to BitShares ..
Congrats on getting a job.
I don't quite get why you are posting all this stuff though... As far as I can tell all your workers got voted in and you set the pay. If you wanted more pay, why didn't you ask for more? You kind of sound like the guy who quits or gets fired and says "That company is screwed without me, I'm irreplaceable!" . Life does go on and so will bitshares. Whether your working for it or not.
-
As it turns out, I am in a fortunate position that I don't need to work
for 25€/h for BitShares any longer but can take the jobs that pay me
$50/h somewhere else.
However, for BitShares shareholders (and they certainly have
speculated on a different outcome), I can no longer offer my services
for you for free any longer as I am freelancing in the blockchain
space and need to eat.
Since worker proposals can neither be deleted nor modified after
creation, you are still in a lucky position because I promised to work
for the conditions of these workers shall they be approved.
From the shareholder's point of view, this is your chance to get me work
for BitShares at this low rate. Take it or leave it.
As for my current worker, I see my obligations as fulfilled as I have
put way more than 20h/w for the last two months. Once the older worker
terminates, I will no longer be available for technical support or
documentation unless someone can pay for it.
To @alt and those that have set him as proxy: It is unfortunate that
none of you, nor @alt has joined any discussion to make this happen and
since you obviously don't appreciate the work I have put into BitShares
for free for the last 2 years, I see no reason to help you reach your
ROI while I am left behind.
If you've already found a new job, I just want to say: congratulations! And great thanks for the work and efforts you've ever done for BitShares.
You don't sound too concerned with this situation. What is your problem?
I don't think I have any problem. I'm just happy that xeroc has stable income now. Isn't it a good thing?
While I wish the best for @xeroc and actually have no doubt that his skills are demanded more than enough to keep him comfortably working in one job or another, we're all here because we want to see Bitshares succeed. That outcome is NOT served well if we cannot retain his talents, which means my sizable investment here is more at risk than it should be, and I'm sure others feel the same way. Why do you not seem concerned about this? Can I ask, do you have a stake in BTS beyond the 126,000 BTS in your abit account?
-
Congrats on getting a job.
I don't quite get why you are posting all this stuff though... As far as I can tell all your workers got voted in and you set the pay. If you wanted more pay, why didn't you ask for more? You kind of sound like the guy who quits or gets fired and says "That company is screwed without me, I'm irreplaceable!" . Life does go on and so will bitshares. Whether your working for it or not.
You certainly got a wrong impression.
The issue was (and kind of still is) .. that my worker wouldn't make it if Bytemaster didn't vote for it (I actually asked him NOT to vote for it, but it seems it is to late) ..
The problem here is that I have deliberately not searched for a regular job because my impression was that my work here is appreciated and could be funded for longer ..
Only due to the anti-dilution discussion and the decisions of one individual, this worker would not have been approved .. which is a big issue not only for me!
The reasons I didn't want BM to vote for my workers is very simple: BitShares deserves to be more independent from CNX and it is very unfortunate that it currently can't be because of this one proxy!
Anyway, if the subsequent workers are approved .. I of course will put the promised time into BitShares .. the other "job" is also just a freelancing just for about 20h/week (at most) .. and I do have quite some things on my list to do .. not just coding and docs
-
Happy to hear you've found an income stream, but I really hope your workers get voted in and I hope this experience doesn't dissuade you from doing more public work going forward.. we need your help!
The work you've done is invaluable, and it's sad that some fail to see beyond this partisan issue. The worker model is not perfect but it's the best we have, and @xeroc has already made compromises in regards to pay & terms, in addition to going well beyond his obligations.
-
As it turns out, I am in a fortunate position that I don't need to work
for 25€/h for BitShares any longer but can take the jobs that pay me
$50/h somewhere else.
Congrats!
I wish things were different around here and the deserving were funded properly. :-\
-
Congrats on getting a job.
I don't quite get why you are posting all this stuff though... As far as I can tell all your workers got voted in and you set the pay. If you wanted more pay, why didn't you ask for more? You kind of sound like the guy who quits or gets fired and says "That company is screwed without me, I'm irreplaceable!" . Life does go on and so will bitshares. Whether your working for it or not.
You certainly got a wrong impression.
The issue was (and kind of still is) .. that my worker wouldn't make it if Bytemaster didn't vote for it (I actually asked him NOT to vote for it, but it seems it is to late) ..
The problem here is that I have deliberately not searched for a regular job because my impression was that my work here is appreciated and could be funded for longer ..
Only due to the anti-dilution discussion and the decisions of one individual, this worker would not have been approved .. which is a big issue not only for me!
The reasons I didn't want BM to vote for my workers is very simple: BitShares deserves to be more independent from CNX and it is very unfortunate that it currently can't be because of this one proxy!
Anyway, if the subsequent workers are approved .. I of course will put the promised time into BitShares .. the other "job" is also just a freelancing just for about 20h/week (at most) .. and I do have quite some things on my list to do .. not just coding and docs
i would just say 1 big whale against the other, so you need bytemasters vote, because all the no voters are united, but not the yes voters.
-
While I wish the best for @xeroc and actually have no doubt that his skills are demanded more than enough to keep him comfortably working in one job or another, we're all here because we want to see Bitshares succeed. That outcome is NOT served well if we cannot retain his talents, which means my sizable investment here is more at risk than it should be, and I'm sure others feel the same way. Why do you not seem concerned about this? Can I ask, do you have a stake in BTS beyond the 126,000 BTS in your abit account?
As you can see, I have another 154,000 BTS in my in.abit account, and counting. ;) Relax dude. I do concern, but it's useless to say that here. I did vote with all my stakes for xeroc. Xeroc has right to work elsewhere, he is not a slave of BitShares.
-
That"s the problem, someone like XEROC with his skills and overall knowledge of the platform should be able to be a full-time worker. There should be at least a core group of developers supported by the platform who can put in time needed and not worry about losing their pay for things unrelated to their overall performance.
-
Congrats on getting a job.
I don't quite get why you are posting all this stuff though... As far as I can tell all your workers got voted in and you set the pay. If you wanted more pay, why didn't you ask for more? You kind of sound like the guy who quits or gets fired and says "That company is screwed without me, I'm irreplaceable!" . Life does go on and so will bitshares. Whether your working for it or not.
You certainly got a wrong impression.
The issue was (and kind of still is) .. that my worker wouldn't make it if Bytemaster didn't vote for it (I actually asked him NOT to vote for it, but it seems it is to late) ..
The problem here is that I have deliberately not searched for a regular job because my impression was that my work here is appreciated and could be funded for longer ..
Only due to the anti-dilution discussion and the decisions of one individual, this worker would not have been approved .. which is a big issue not only for me!
The reasons I didn't want BM to vote for my workers is very simple: BitShares deserves to be more independent from CNX and it is very unfortunate that it currently can't be because of this one proxy!
Anyway, if the subsequent workers are approved .. I of course will put the promised time into BitShares .. the other "job" is also just a freelancing just for about 20h/week (at most) .. and I do have quite some things on my list to do .. not just coding and docs
A lot of people trust BM and for good reason. He's the inventor of BTS and if anyone wants it to succeed it is him. People see that and set BM as their proxy. By saying you don't want BM to vote for you is like saying none of his other supporters (and probably your supporters) shouldn't vote for you either... I don't see the logic in your request to not have BM or any of his proxies vote for you. Your basically asking for everyone who is anti dilution to change there minds and vote for you.
-
@xeroc - you should get paid.
What is more you should get pad not at 50% rate but at 100%!
You should not ask BM to not vote for you if he does find your work bringing more value than your pay. My guess is - he does.
You should not ask alt to not vote against your worker - he has a perfectly valid argument too. Start up shares do not end up being sold the second an employee gets his paycheck.
So where all this fails? I think, in You assuming that BTS has a system to finance itself! When in reality it doesn't. It has a very good tool, to archive such start up financing though. What is missing from it (the extra step needed for this to be true financing of a start up) - the long term capital willing to hodl BTS for at least 2-3 years, while paying you the full deserved salary.
How can we do that (my thoughts, there might be better plans)?
- directly locking the worker pay(probably using 1.3-1.5 bigger pay than what they do pay you) for 2-3 years for willing investors; while those investors pay you directly.
- selling an asset backed/receiving said 1.3-1.5x locked BTS; while you receive the proceeds (in bitEUR or BTS) from the asset sale.
-
That"s the problem, someone like XEROC with his skills and overall knowledge of the platform should be able to be a full-time worker. There should be at least a core group of developers supported by the platform who can put in time needed and not worry about losing their pay for things unrelated to their overall performance.
I would LOVE to work on bitshares full time, but i made the compromise (two compromises actually) .. to only work half-time at rather low rate and bet big on its success
A lot of people trust BM and for good reason. He's the inventor of BTS and if anyone wants it to succeed it is him. People see that and set BM as their proxy. By saying you don't want BM to vote for you is like saying none of his other supporters (and probably your supporters) shouldn't vote for you either... I don't see the logic in your request to not have BM or any of his proxies vote for you. Your basically asking for everyone who is anti dilution to change there minds and vote for you.
I do trust BM. He is the sole reason I am here and love where I am!
The reason I asked him to not voice his opinion was to not give the
shareholders the impression that Daniel dictates who should be worker
and who should not. I very much appreciate the trust he puts into me but
would have preferred the ecosystem to disconnect from its father
eventually. It may need some more months until we are there.
-
@xeroc - you should get paid.
What is more you should get pad not at 50% rate but at 100%!
You should not ask BM to not vote for you if he does find your work bringing more value than your pay. My guess is - he does.
You should not ask alt to not vote against your worker - he has a perfectly valid argument too. Start up shares do not end up being sold the second an employee gets his paycheck.
So where all this fails? I think, in You assuming that BTS has a system to finance itself! When in reality it doesn't. It has a very good tool, to archive such start up financing though. What is missing from it (the extra step needed for this to be true financing of a start up) - the long term capital willing to hodl BTS for at least 2-3 years, while paying you the full deserved salary.
How can we do that (my thoughts, there might be better plans)?
- directly locking the worker pay(probably using 1.3-1.5 bigger pay than what they do pay you) for 2-3 years for willing investors; while those investors pay you directly.
- selling an asset backed/receiving said 1.3-1.5x locked BTS; while you receive the proceeds (in bitEUR or BTS) from the asset sale.
Thanks for the kind and open words .. much appreciated.
Another idea to work this out would be:
- let the committee create an asset that works as an option to get pays x*1.03^y USD after y years (e.g. USD-OPTION-2015)
- pay x USD options to the workers
- fund the options by asking for .10% trading fees on bitassets
- put revenue from trading as a buy order for the options into the dex
just an idea. Since I am not an economist .. it might be flawed
-
I do trust BM. He is the sole reason I am here and love where I am!
The reason I asked him to not voice his opinion was to not give the
shareholders the impression that Daniel dictates who should be worker
and who should not. I very much appreciate the trust he puts into me but
would have preferred the ecosystem to disconnect from its father
eventually. It may need some more months until we are there.
While I find this reasoning to be very virtuous, I don't think we are in a situation where Bytemaster's voting can be ignored. He is the lead developer so people will either use him as a proxy or check how he votes and base their voting on that. If Bytemaster isn't voting for something, people can get impression that it's not worth of DAC's resources to fund that worker.
Also, you shouldn't take too seriously the arguments from antidevelopment/antibytemaster crowd. If they were right, Bitshares should be performing much better now when Bytemaster is not controlling anymore most of the witnesses and committee – but that's not clearly the case. And if new people see that lead dev is not taking actively part in the decision making, they might think that he is not commited to the project anymore.
So please @bytemaster could you vote for xeroc?
-
Congratulations! You are voted in!
-
@xeroc I appreciate all the work you done for our community. You have my support
-
Congratulations! You are voted in!
@xeroc I appreciate all the work you done for our community. You have my support
Thanks for all the support.
For those that wonder what I did the last week, I am preparing articles for different parties among which are
OpenBazaar and the upcoming newsletter ...
Hope to be able to get back to coding soonish
-
are you still working on the remaining Whitepapers?
-
As a quick update:
* I've added a few more basic articles to the docs
* rewrite of the API pages
* wrote some articles for the (hopefully) upcoming newsletter
* upgraded the testnetwork seed node to allow STEALTH testing on stealth.cnx.rocks
* and some more stuff I just forgot :P
and most happy, I am that I made huge progress in the offline-signing python code.
There just seems to be one issue left that makes the signatures non-canonical and I need to figure out what the reasons for this is.
But some python-signed transactions made it into the blockchain. So that's something.
-
There just seems to be one issue left that makes the signatures non-canonical and I need to figure out what the reasons for this is.
The is_canonical check in Graphene is much too restrictive, IMO. Signatures sometimes just fail it. The only option is to retry with a different random value.
-
There just seems to be one issue left that makes the signatures non-canonical and I need to figure out what the reasons for this is.
The is_canonical check in Graphene is much too restrictive, IMO. Signatures sometimes just fail it. The only option is to retry with a different random value.
Yhea .. that is what the UI does and what I have implemented as well now. Seems to work reliably now
-
I just pushed a new feature branch that is capable of signing (currently only) transfers and can not yet include memos:
https://github.com/xeroc/python-graphenelib/tree/feature/offline-signing
from grapheneapi.grapheneclient import GrapheneClient
from graphenebase import transactions
class Config():
witness_url = "ws://localhost:8090/"
wif = "5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3"
from_account_name = "nathan"
to_account_name = "init0"
amount = 10
asset_name = "CORE"
# memo = ""
if __name__ == '__main__':
client = GrapheneClient(Config)
connected_chain = client.getChainInfo()
to_account = client.ws.get_account(Config.to_account_name)
from_account = client.ws.get_account(Config.from_account_name)
asset = client.ws.get_asset(Config.asset_name)
fee = transactions.Asset(0, "1.3.0")
amount = transactions.Asset(int(Config.amount * 10 ** asset["precision"]), "1.3.0")
memo = transactions.Memo() # Not implemented yet
transfer = transactions.Transfer(fee,
from_account["id"],
to_account["id"],
amount,
memo)
ops = [ transactions.Operation(transfer) ]
ops = transactions.addRequiresFees(client.ws, ops, "1.3.0")
ref_block_num, ref_block_prefix = transactions.getBlockParams(client.ws)
expiration = transactions.formatTimeFromNow(60 * 60)
signed = transactions.Signed_Transaction(ref_block_num, ref_block_prefix, expiration, ops)
w = signed.sign([Config.wif], chain=connected_chain)
ret = client.ws.broadcast_transaction(transactions.JsonObj(w), api="network_broadcast")
print(ret)
Todo:
* Add memo (shouldn't take too long since most code is already implemented)
* Add other operations besides 'transfer'
-
I know it's possible to claim AGS/PTS balances with cli_wallet directly, but I'm not sure if it can be done with 2.0 GUI alone (I've filed an issue https://github.com/cryptonomex/graphene-ui/issues/785). If not, users need to import keys to BitShares 0.x first, but it's hard to find a tutorial about that. The original BitShares Wiki http://wiki.bitshares.org doesn't work anymore, which contains some important tutorials about BTS 0.x, for example how to claim fund from AGS/PTS http://wiki.bitshares.org/index.php?title=BitShares/Howto&oldid=3080#Attempting_a_wallet_import_to_receive_BTSX_from_February_28th_snapshot .
Possible to add it to new document site?
-
Here is the wiki.bitshares.org from aug. 17th, 2015.
https://web.archive.org/web/20150817075329/http://wiki.bitshares.org/index.php/Main_Page
-
importing your AGS/PTS keys directly into the GUI will most probably work as expected as it derives the correct pubkey/address from that private key alone and does not contain any blockchain version data like PTS addresses or BTC addresses.
-
Here is the wiki.bitshares.org from aug. 17th, 2015.
https://web.archive.org/web/20150817075329/http://wiki.bitshares.org/index.php/Main_Page
Thanks!
importing your AGS/PTS keys directly into the GUI will most probably work as expected as it derives the correct pubkey/address from that private key alone and does not contain any blockchain version data like PTS addresses or BTC addresses.
Sounds reasonable.. but what's this problem? https://bitsharestalk.org/index.php/topic,21911.msg285827.html#msg285827
-
Just a short updates:
I've updated the docs quite a bit in the last weeks even though the last few days have not been too productive on the documentation side of things.
On the other hand, I have successfully coded a library that let's you construct and sign transaction fully in python. Next step is to learn a decent
GUI framework (reading into QT right now) and write a tool that helps people to deal with cold storage. The library is feature complete (at least for transfers)
and all that is needed is a nicer way to make use of it.
I'd like to let you know that I am going for a 6 days vacation starting today what means that I will not be as responsive as usual. I'll be back .. next friday :)
-
Apologies for not keeping this thread up to date:
In fact, I've been so busy with BitShares and related projects that I haven't had the time to keep the corresponding posts up to date.
Let me quickly recap the work done in the recent months:
* Python-graphenelib - Low-level library for interacting with the Network
* Transaction Signing in Python - Sign your transactions without the cli/web wallet
* BitShares Europe Consulting - Education, Trainings & Seminars
* BitShares Europe Blog - Blog posts about the DAC
* BitShares Europe Documentation - Reference Documentation for Graphene and BitShares
* BitShares Europe Stats - BitShares TPS in real-time
* Committee Proposals - Development & Execution
* Committee Instructions - Educational and Consulting
* Structured Fee Schedule - Development, Marketing, Execution
* LaTeX Paperwallet - Bringing Private Keys
* Wallet Recovery Service - 0.9 Migration
* AirSign - Python-Only Interface for BitShares
* Peermit - Second factor authentication for BitShares
* Price Feed - Price feed script for BitShares Witnesses
* BitShares Improvement Proposals - BSIPs
* Full fledged docker containers - Dockerfiles for easy deployment
* Wallet and Faucet deployments & maintenance - Run your own white-labeled DEX
* Graphene/BitShares Paperwallets - Cold Storage on Paper
* BitShares/Graphene Testnet - The one and only Testnet for BitShares
* Trading Bot Infrastructure - Run your Bots on the DEX
* Customized Blockchain deployment - Get your own private Graphene blockchain
* BitShares Whitepapers - Sole author of two whitepapers
* High profile forum member - Most forum posts .. by far
My short term goals for the next weeks is to improve on the trading bot infrastructure so that people only need to deploy python code and not need to run a cli_wallet.
-
Just a note, there are 1,196,589 BTS and 204,239 BTS accumulated by workers in this thread, unclaimed.
-
Yhea, I know. :D