256
Meta / Re: PLEASE disable Cloudflare on the forum
« on: February 28, 2016, 04:32:55 pm »
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
257
General Discussion / Re: [ANN] Let's do it at once - Liquidity Event - 29th Feb
« on: February 28, 2016, 05:53:29 am »
BlockTrade rates for buying BTS have been lowered on all coin pairs for the Liquidity Event.
258
General Discussion / Re: Popular Bitshares Exchanges
« on: February 27, 2016, 06:08:11 pm »PoloniexIn case it's relevant, these 3 are instant exchanges:
BTC38
BitTrex
BitcoinIndonesia
Yunbi
CCEDK
Shapeshift -currently unavailable
Blocktrades
MetaExchange
BitShares DEX
Blocktrades
MetaExchange
Shapeshift -currently unavailable
259
Openledger / Re: Tried to deposit Ether has not worked as issue with Openledger getting updated
« on: February 27, 2016, 04:17:09 pm »
Looks like the transaction didn't have a memo to indicate where to send the open.eth. We've updated internally now so that the system only requires an input address, but this won't take effect for openledger until the next GUI wallet update. I'll manually process your deposit for this transaction.
260
General Discussion / Re: Why No 160225 Windows/Mac Binaries Uploaded?
« on: February 27, 2016, 04:07:36 pm »We handle the windows binaries for the witness node and the cli wallet. I think clayop is talking about the light wallet, which Valentine handles (there's no real changes to C++ code for light wallet, it's just web page updates).I was tagged yesterday, but so far there's no binaries on github. Who will upload them and when?
I thought the blocktrades team was the one handling that as BM pointed out on their Maintenance Worker thread
Also, as I told clayop yesterday, Valentine told me he was delaying it to get a few more GUI changes included before he released it.
261
General Discussion / BlockTrades adds support for Ether (direct from exchanges also)
« on: February 26, 2016, 12:31:40 am »
BlockTrades (http://blocktrades.us) supports buying and selling Ether with the following cryptocurrencies:
BitShares, BitCoin, Dash, Doge, Litecoin, Nubits, and Peercoin.
We also support sending to an Ethereum address without requiring a memo, so you can directly purchase cryptocurrencies from an exchanged-based account where you have Ether deposited without having to first send it to an Ethereum wallet.
BitShares, BitCoin, Dash, Doge, Litecoin, Nubits, and Peercoin.
We also support sending to an Ethereum address without requiring a memo, so you can directly purchase cryptocurrencies from an exchanged-based account where you have Ether deposited without having to first send it to an Ethereum wallet.
262
Stakeholder Proposals / Re: [Worker Proposal] Blockchain maintenance developer
« on: February 25, 2016, 07:14:12 pm »Please help publish win binaries for release of 2.0.160223. ThanksIt's up, thanks for the notification.
263
Stakeholder Proposals / Re: [Worker Proposal] Blockchain maintenance developer
« on: February 23, 2016, 11:23:21 pm »Well, our github workflow makes it possible to see what's planned and some idea of who is doing what, although these things never tell the whole story, since few document systems relying on manual entry manage to track reality perfectly. That will be especially true whenever some release needs to get rushed out for a high priority issue. But, FWIW, on the blockchain side of things, this is probably the best documentation of current and near term planned work:I think a weekly overview would make sense because it would:It's been suggested that we should report what issues we plan to work on, but this really isn't a simple thing to do reliably. Priorities of issues rapidly change as well as available people to work on them. It's much easier and more reasonable, IMO, to report what was done and what was charged.I agree. Setting up and publishing an official schedule and keeping it up to date is unnecessary overhead that I wouldn't want to pay for. Regular reports of work done and how the payment was allocated to different tasks/workers is sufficient.
... provide accountability
... be positive for the public and shareholder perception of the worker system and this specific worker
Has there been such documentation in the past? ...I think that would make sense for any worker.
https://github.com/cryptonomex/graphene/milestones/NextRelease
264
Stakeholder Proposals / Re: [Worker Proposal] Blockchain maintenance developer
« on: February 23, 2016, 02:52:08 pm »
To inject some actual numbers into this discussion, for the work reported above, this worker has been paid ~$3250 USD in BTS. Of that, BlockTrades plans to charge $700 for the work we've done (this includes more than just the time we spent on the windows build and issue 251, as we've had to spend time learning and discussing ways to improve the current workflow). Given the work that CNX did during this period, I think it's quite reasonable for them to charge $2550. SVK's feelings aside, I don't think we're likely to see CNX doing development work for free. The best I think we can hope for is that they give us a discounted rate, which I think this represents.
I certainly plan to increase the amount of time we can devote to this worker, but I know our next week is booked with updating our web site for our public offering, so I plan to make no charges during that time for BT. The one exception to that is if we wind up working on this issue: https://github.com/cryptonomex/graphene/issues/591.
It's been suggested that we should report what issues we plan to work on, but this really isn't a simple thing to do reliably. Priorities of issues rapidly change as well as available people to work on them. It's much easier and more reasonable, IMO, to report what was done and what was charged. I'll evaluate what is done by CNX and us over the next period, then distribute accordingly, including returning funds if less was done than the worker provides for.
However, it is important that programmers know what issues other programmers are working on to avoid work duplication. For programmers, the answer for this is addressed in a new document I wrote recently to describe our updated workflow plans:
https://github.com/cryptonomex/graphene/wiki/Graphene-GitHub-Guidelines
To answer abit's question, we did not have a chance to look at the "mobile spam" issue yet. From preliminary discussions with Theo and BM, we understand the nature of the problem, and the most likely solution will be one of examining the flow of data and coming up with some heuristics to reduce the flow. In other words, there's no simple "clean" solution. We're still planning to address this issue when we have a chance, but if you want to take a crack at it, assign it to yourself. If you can make a significant reduction, report it to us and we can work out some way to pay you for the work.
I certainly plan to increase the amount of time we can devote to this worker, but I know our next week is booked with updating our web site for our public offering, so I plan to make no charges during that time for BT. The one exception to that is if we wind up working on this issue: https://github.com/cryptonomex/graphene/issues/591.
It's been suggested that we should report what issues we plan to work on, but this really isn't a simple thing to do reliably. Priorities of issues rapidly change as well as available people to work on them. It's much easier and more reasonable, IMO, to report what was done and what was charged. I'll evaluate what is done by CNX and us over the next period, then distribute accordingly, including returning funds if less was done than the worker provides for.
However, it is important that programmers know what issues other programmers are working on to avoid work duplication. For programmers, the answer for this is addressed in a new document I wrote recently to describe our updated workflow plans:
https://github.com/cryptonomex/graphene/wiki/Graphene-GitHub-Guidelines
To answer abit's question, we did not have a chance to look at the "mobile spam" issue yet. From preliminary discussions with Theo and BM, we understand the nature of the problem, and the most likely solution will be one of examining the flow of data and coming up with some heuristics to reduce the flow. In other words, there's no simple "clean" solution. We're still planning to address this issue when we have a chance, but if you want to take a crack at it, assign it to yourself. If you can make a significant reduction, report it to us and we can work out some way to pay you for the work.
265
Stakeholder Proposals / Re: [Worker Proposal] Blockchain maintenance developer
« on: February 23, 2016, 06:38:37 am »CNX pays Theo, and CNX has to get money from somewhere to pay him. You can't reasonably expect CNX to commit a programmer and a 1/2 to full time work on BitShares without any compensation (the 1/2 being limited support from other CNX folks such as BM/Valentine/etc). During this pay period, the larger portion will go to CNX and we'll take a much smaller proportion for the work we did. If the total charges from CNX and BT is less than the total paid during a pay period, I'll send it back to the reserve fund. BT didn't do a lot this period because higher priority things came up, but CNX did do a lot of work, so I think the full fee is justified. Next pay period, I hope it works out differently, but I can't say for sure yet.Sure, but working on graphene is already his job and I assume he's being paid by CNX to do so, so it seems weird to me that you're claiming responsibility for stuff he would have done anyway.No, Theo's not a part of BlockTrades. As I posted originally, the pay was for us and for subcontractors such as CNX: I tried to be very open about that. Sometimes it will be us, sometimes CNX, and yes, potentially others as well. BM asked me to help shoulder some of the load of responding to issues in GitHub related to the blockchain as CNX was tied up with confidential transactions and other projects and Theo was basically having to manage everything on his own. That was stressing him out, and I don't blame him.Here's a list of issues handled by this worker to date. Most of these were done by theoretical, other than #251 and the ones related to Windows builds, since BlockTrades has been tied up with other work for most of the period.So is theoretical part of Blocktrades now? Or is the way this worker will function that you pay whoever happens to fix bugs in the repo? Will you pay abit too then?
https://github.com/cryptonomex/graphene/issues/251
https://github.com/cryptonomex/graphene/issues/514
https://github.com/cryptonomex/graphene/issues/516
https://github.com/cryptonomex/graphene/issues/542
https://github.com/cryptonomex/graphene/issues/549
https://github.com/cryptonomex/graphene/issues/550
https://github.com/cryptonomex/graphene/issues/553
https://github.com/cryptonomex/graphene/issues/555
https://github.com/cryptonomex/graphene/issues/556
https://github.com/cryptonomex/graphene/issues/559
https://github.com/cryptonomex/graphene/issues/562
https://github.com/cryptonomex/graphene/issues/566
https://github.com/cryptonomex/graphene/issues/572
https://github.com/cryptonomex/graphene/issues/586
Seems like a bad deal for us for the $7-8000 a month you're being paid to be honest..
The backlog of issues in the graphene repo is frustratingly long and I was hoping you would add some additional manpower to it because like you say theoretical does need help there. With the kind of worker pay you're asking I think we have a right to expect you to put serious resources into this.
266
Stakeholder Proposals / Re: [Worker Proposal] Blockchain maintenance developer
« on: February 23, 2016, 04:17:16 am »No, Theo's not a part of BlockTrades. As I posted originally, the pay was for us and for subcontractors such as CNX: I tried to be very open about that. Sometimes it will be us, sometimes CNX, and yes, potentially others as well. BM asked me to help shoulder some of the load of responding to issues in GitHub related to the blockchain as CNX was tied up with confidential transactions and other projects and Theo was basically having to manage everything on his own. That was stressing him out, and I don't blame him.Here's a list of issues handled by this worker to date. Most of these were done by theoretical, other than #251 and the ones related to Windows builds, since BlockTrades has been tied up with other work for most of the period.So is theoretical part of Blocktrades now? Or is the way this worker will function that you pay whoever happens to fix bugs in the repo? Will you pay abit too then?
https://github.com/cryptonomex/graphene/issues/251
https://github.com/cryptonomex/graphene/issues/514
https://github.com/cryptonomex/graphene/issues/516
https://github.com/cryptonomex/graphene/issues/542
https://github.com/cryptonomex/graphene/issues/549
https://github.com/cryptonomex/graphene/issues/550
https://github.com/cryptonomex/graphene/issues/553
https://github.com/cryptonomex/graphene/issues/555
https://github.com/cryptonomex/graphene/issues/556
https://github.com/cryptonomex/graphene/issues/559
https://github.com/cryptonomex/graphene/issues/562
https://github.com/cryptonomex/graphene/issues/566
https://github.com/cryptonomex/graphene/issues/572
https://github.com/cryptonomex/graphene/issues/586
Seems like a bad deal for us for the $7-8000 a month you're being paid to be honest..
267
Stakeholder Proposals / Re: [Worker Proposal] Blockchain maintenance developer
« on: February 22, 2016, 11:21:34 pm »Should be fixed soon, that was under discussion today.Here's a list of issues handled by this worker to date. Most of these were done by theoretical, other than #251 and the ones related to Windows builds, since BlockTrades has been tied up with other work for most of the period.Great. I will vote for you when voting bug is fixed.
https://github.com/cryptonomex/graphene/issues/251
https://github.com/cryptonomex/graphene/issues/514
https://github.com/cryptonomex/graphene/issues/516
https://github.com/cryptonomex/graphene/issues/542
https://github.com/cryptonomex/graphene/issues/549
https://github.com/cryptonomex/graphene/issues/550
https://github.com/cryptonomex/graphene/issues/553
https://github.com/cryptonomex/graphene/issues/555
https://github.com/cryptonomex/graphene/issues/556
https://github.com/cryptonomex/graphene/issues/559
https://github.com/cryptonomex/graphene/issues/562
https://github.com/cryptonomex/graphene/issues/566
https://github.com/cryptonomex/graphene/issues/572
https://github.com/cryptonomex/graphene/issues/586
268
Stakeholder Proposals / Re: [Worker Proposal] Blockchain maintenance developer
« on: February 22, 2016, 10:40:02 pm »
Here's a list of issues handled by this worker to date. Most of these were done by theoretical, other than #251 and the ones related to Windows builds, since BlockTrades has been tied up with other work for most of the period.
https://github.com/cryptonomex/graphene/issues/251
https://github.com/cryptonomex/graphene/issues/514
https://github.com/cryptonomex/graphene/issues/516
https://github.com/cryptonomex/graphene/issues/542
https://github.com/cryptonomex/graphene/issues/549
https://github.com/cryptonomex/graphene/issues/550
https://github.com/cryptonomex/graphene/issues/553
https://github.com/cryptonomex/graphene/issues/555
https://github.com/cryptonomex/graphene/issues/556
https://github.com/cryptonomex/graphene/issues/559
https://github.com/cryptonomex/graphene/issues/562
https://github.com/cryptonomex/graphene/issues/566
https://github.com/cryptonomex/graphene/issues/572
https://github.com/cryptonomex/graphene/issues/586
https://github.com/cryptonomex/graphene/issues/251
https://github.com/cryptonomex/graphene/issues/514
https://github.com/cryptonomex/graphene/issues/516
https://github.com/cryptonomex/graphene/issues/542
https://github.com/cryptonomex/graphene/issues/549
https://github.com/cryptonomex/graphene/issues/550
https://github.com/cryptonomex/graphene/issues/553
https://github.com/cryptonomex/graphene/issues/555
https://github.com/cryptonomex/graphene/issues/556
https://github.com/cryptonomex/graphene/issues/559
https://github.com/cryptonomex/graphene/issues/562
https://github.com/cryptonomex/graphene/issues/566
https://github.com/cryptonomex/graphene/issues/572
https://github.com/cryptonomex/graphene/issues/586
269
General Discussion / Buy/Sell Crypto with OPEN.USD on BlockTrades
« on: February 21, 2016, 10:44:16 pm »
BlockTrades now supports buying and selling cryptocurrency with OPEN.USD. We've added the following pairs so far:
BTS, BTC, Dash, Doge, LTC, NuBits
BTS, BTC, Dash, Doge, LTC, NuBits
270
General Discussion / Re: Prospectus for BlockTrades public offering
« on: February 20, 2016, 07:57:00 pm »It could be a good idea, as long as it's not too expensive. One problem with most "independent audits" is that I think they just look over the books provided to them by a company, and those tend be just be "rubber-stamped" by the auditors. Hence we have situations like Enron, all AAA valuations of CDOs, etc.i would be more interested in your monthly revenue streams and how they are splitted.These are normal stock shares, not some form of derivative with a complex valuation, so I think it's simple to understand how they appreciate in value. Their value will track the value of the company just like any company's shares. When the company is profitable, the value of the shares will tend to go up. Like any other company, based on the desires of the shareholders, we will be able to distribute dividends. Obviously we would do that via the blockchain for simplicity. It is certainly my plan to have the company issue dividends, as the company has a strong cash flow.
where comes the increase in the asset value? only from revenue streams?
do you plan to pay dividends?
Do you guys intend to obtain an independent audit of your financial statements? Something like that could have excellent ROI for you with expansion of valuation multiple with enhanced confidence.
In general, I'm not a big fan of wasting money unnecessarily on accountants and lawyers. I took over accounting for SynaptiCAD years ago, as I found as was able to do a better job than the accountants we employed (partly because I was more motivated and also because I understood the business better and could do more "pro-active" tax planning). Similarly, Donna handles all our legal issues. Donna got her law degree many years ago after we paid about $100K to lawyers to defend SynaptiCAD against a patent infringement lawsuit back in 1995. Nowadays, she tracks the law associated with patents, IP, and cryptocurrency.
I suspect the best thing for adding confidence to our financial statements would be some kind of certification of our current holdings in cryptocurrency, since we're using mark-to-market accounting for our primary assets right now. There's various ways we can do that, just not sure yet which is best. One simple way is I could show our wallet balances to someone trusted by the community (our bitshares wallet balance is visible, of course, but our bitcoin one isn't) and they could serve as an independent auditor. Alternatively, i could publish some public BTC address and move funds into that address temporarily I guess.
