gpg --verify 2016-01.md.sig
could you please elaborate on "Development of a Python library," ?https://github.com/xeroc/python-grapehenlib
could you please elaborate on "Development of a Python library," ?https://github.com/xeroc/python-grapehenlib
I plan to add transaction construction and signing to it as I had it already in the previous network.
But as the underlying wire format changed, I need to rewrite alot of code and add alot of different transaction types (i.e. operations).
Then we could have a simple python tool for instance for offline-signing of transactions .. not just the Javascript and C++ implementation
Also the development of price feed scripts and other tools for witnesses take their time.
Another idea I have is to do some statistical analysis over block chain parameters .. e.g. for committee members ..
could you please elaborate on "Development of a Python library," ?https://github.com/xeroc/python-grapehenlib
I plan to add transaction construction and signing to it as I had it already in the previous network.
But as the underlying wire format changed, I need to rewrite alot of code and add alot of different transaction types (i.e. operations).
Then we could have a simple python tool for instance for offline-signing of transactions .. not just the Javascript and C++ implementation
Also the development of price feed scripts and other tools for witnesses take their time.
Another idea I have is to do some statistical analysis over block chain parameters .. e.g. for committee members ..
thanks. what about some (core) features? Like claim vested balances in the GUI, could you do it?
could you please elaborate on "Development of a Python library," ?https://github.com/xeroc/python-grapehenlib
I plan to add transaction construction and signing to it as I had it already in the previous network.
But as the underlying wire format changed, I need to rewrite alot of code and add alot of different transaction types (i.e. operations).
Then we could have a simple python tool for instance for offline-signing of transactions .. not just the Javascript and C++ implementation
Also the development of price feed scripts and other tools for witnesses take their time.
Another idea I have is to do some statistical analysis over block chain parameters .. e.g. for committee members ..
thanks. what about some (core) features? Like claim vested balances in the GUI, could you do it?
you can do that now with his library. All cli_wallet commands and websocket APIs are available.
EDIT: technically, only database, history, and un-authenticated APIs are available via websocket, but adding others is trivial - it's just that no one needed them yet
thanks. what about some (core) features? Like claim vested balances in the GUI, could you do it?I think so, though I haven't look how far this particular transaction type has been exposed in the library already.
1) I'm a big fan and user of the library. big +5%. We need more peopleThough it is a rather "simply" library still. The Websocket notification part
interacting with the blockchain via scripting. My bot is almost sane enough to
put in the wild as well (release open source), and it relies on his library.
3) I propose even expanding xeroc's proposal. Have the worker fund xeroc, thenSounds like a great plan but at the current stage I only offer my personal
xeroc "bill" the worker account for work done at his hourly rate (I'd even
increase that rate). Xeroc should also be allowed the freedom to outsource tasks
included in this worker proposal. Getting workers approved is hard, largely
because of trust issues. People won't do work without getting paid, and people
won't pay without knowing what the work will be. Xeroc is trusted, he can thus
outsource specific tasks and then "bill" his worker account to pay others to do
work. His scope would be limited to what is in his proposal. This way there is
no concern over whether funds will be available (so people will do the work),
and xeroc can optimize as needed. Excess funds can be returned or just used for
the next quarter.
From my experience, i put a lot of time in to making an automated ubuntu/debianIn the future I am sure we will see a set of independent freelancers and bigger
build and distribution system. People don't know this, but bitshares actually
has a 100% working system exactly like
https://github.com/nodesource/distributions, but it was never funded so it never
went live. The work was essentially wasted. For me, it doesn't matter because I
don't need the money and I took it as a challenge to build, but freelance devs
won't take that risk. Streamlining the system would be important. Allowing
"managers" to bill worker accounts as needed will lower that barrier. All we
have to do is to trust xeroc's priorities and have clear communication between
him and proxies so it will be renewed as reasonable levels as necessary.
thanks. that's why I asked, I'd rather see some basic stuff done before we moveSure, and that is why I stopped working on the transaction constructon and
to offline signing and other optional things
Though it is a rather "simply" library still. The Websocket notification part
grew slightly in the last days and I may need to rewrite parts of it for
clarity reasons. I would also like to offer an interface for the markets, but
have put it on hold until the cli_wallet and witness API gets more improved.
Last time I checked, it wasn't really possible to get a last_price/volume ticker
for a particular market. Maybe that changed by now.
All time most orders placed
Rank Account Count
#1 maqifrnswa.bot 2,962
#2 acc12 1,005
#3 asshole1 679
#4 bts-scotter 367
#5 ccedkbts 276
#6 cc 263
#7 gn1 247
#8 clayop 228
#9 enki 211
#10 bts-awc-cny 191
I've been exploring the wallet and ws api, source code, and your work - I thinkThat would be great!
I may have some solutions to things your working on that can help this library &
proposal. I can send you my bot code to see some things I've done. (It's buggy
so probably still shouldn't share publicly yet.) I can move this discussion to
github.
On a side note, I actually discovered the duplicate op bug last weekend when IThere is one notification triggered once the object change is received and there
tried to use my dynamic object for my bot account as the trigger for placing
orders. Those duplicate numbers ended up causing the bot to spam 100s of
transactions per block. I thought it was a bug in my code so I stopped it, but
it turns out it wasn't!
2) We need more non-cryptonomex workers supported, and they should be paid competitively. If bitshares wants to be a serious business, xerox is doing real and very important work insanely cheap. He's low risk, and proven member of the team. If bitshares "can't afford" to pay him, that's a major failure of the system.
One thing caught me off guard.. svk is now fully independent from CNX and hisI can't tell you how much time @svk puts into BitShares (definitely quite a bit)
worker has a modest daily pay of 19k BTS. I don't think he specified an hourly
rate, but as far as I can tell he's putting in at least 20 hours a week. So I
guess my question is, are you still working for CNX in some capacity? And how
does one determine (in a general sense) if a task should be paid for by CNX vs.
BTS?
That aside.. Dr. Xeroc's services are easily worth 37.50€/h, especiallyActually, there is a genetically identical clone of myself (a twin brother), but
considering his long history of volunteer work. If we could clone him, I'd hire
his clone at that rate too. :D
Actually, there is a genetically identical clone of myself (a twin brother), but
he is not into blockchain business ... yet :)
One thing caught me off guard.. svk is now fully independent from CNX and hisI can't tell you how much time @svk puts into BitShares (definitely quite a bit)
worker has a modest daily pay of 19k BTS. I don't think he specified an hourly
rate, but as far as I can tell he's putting in at least 20 hours a week. So I
guess my question is, are you still working for CNX in some capacity? And how
does one determine (in a general sense) if a task should be paid for by CNX vs.
BTS?
but I am fairly certain that he has another day-job. He definitely is worth more
than BitShares can pay him right now and I much appreciate him offering his
service at such a low rate. Take a look at what other companies pay for good
react-js developers!
The other question you are asking is quite a good one since I do have a
contributing agreement with CNX as well and they pay me for work I ask me to
deliver to them. It is part of my calculations and I hope to fill the rest of my
40h/week with worth from CNX *AND* other players in the BitShares/Graphene
space.
As for the distiction of how pays what: The idea was to have BitShares pay for
the services I mentioned above up to 20h/week and fill the rest of my time with
either stuff that I want to do (e.g. peermit.com, bitshares europe) or by jobs
that someone else pays me for, e.g. CNX, PeerTracks, etc.
QuoteThat aside.. Dr. Xeroc's services are easily worth 37.50€/h, especiallyActually, there is a genetically identical clone of myself (a twin brother), but
considering his long history of volunteer work. If we could clone him, I'd hire
his clone at that rate too. :D
he is not into blockchain business ... yet :)
@xeroc Hi! If you are my proxy voter, should I remove you to vote for your worker, or will you vote for yourself on my behalf?I thought a lot about this and came to the conclusion that i can NOT just easily vote for my self.
@xeroc Hi! If you are my proxy voter, should I remove you to vote for your worker, or will you vote for yourself on my behalf?I thought a lot about this and came to the conclusion that i can NOT just easily vote for my self.
@xeroc Hi! If you are my proxy voter, should I remove you to vote for your worker, or will you vote for yourself on my behalf?I thought a lot about this and came to the conclusion that i can NOT just easily vote for my self.
To solve this conflict of interest, I could write a memo to all that set me as proxy and let them know about this prior to voting for myself. Would that work for you?
You have the skills needed to put a true burning worker up for voting by the community.[ this is in addition and NOT as a replacement of the recycling one already in existence]I can definitely do that and put some documentation about it into the bsips (as informational document)
Will you do it, and if not why?
@xeroc we need a tutorial of how to create a committee member in this doc: http://docs.bitshares.eu/bitshares/user/committee.htmlAbsolutely ..
http://docs.bitshares.eu/bitshares/user/committee.html@xeroc we need a tutorial of how to create a committee member in this doc: http://docs.bitshares.eu/bitshares/user/committee.htmlAbsolutely ..
I think a weekly overview over what has been done would make sense because it would:Thanks for the feedback .. weekly reports might really have been useful in this case .. I'll recommend it to anyone that plans to run a worker in future.
... provide accountability
... be positive for the public and shareholder perception of the worker system (so you can see what you are getting for your bug and that DPOS works)
I think that would make sense for any worker (posted it to other active workers as well).
Of course that is not meant as being doubtful of the utility of your work. I have lots of positive first hand experience with it ;)