• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Lamassu update ?

Actually, Lamassu received NO funds and won't receive any...
"They are a start-up and never committed to do this work internally themselves or received any payment from us directly." .[see post #14 above]

Rather, GitGuild receives a monthly payment of Dash - not cash, allocated from the ongoing budget...
"So that is the reason why we did a Dash based contract and not a USD based contract" .[see post #9 above]

Thank you (and @tungfa) for the correction. I'm going to open myself up to the possibility of further error here, but I also seem to recall that the difficulties are due to Lamassu's unexpected changes in their codebase to support ETH, and that our vendor partner, GitGuild, is actually not liable for something that Lamassu (who is not a party to the contract) has done or not done.

Frankly, the Network entered into a contract with GitGuild to do work on a third-party application (from Lamassu). If Lamassu has (temporarily) blocked GitGuild's work, then that is not GitGuild that is to blame, but our own Network for not taking into account that risk factor. Why should we breach our contract with GitGuild because of our own errors in judgment?

I don't like it either--we've ended up paying an insane amount of money for something that has not progressed as far as we expected. But it is good to maintain some perspective: at the time we voted this proposal in, the price of DASH had been stagnant for 18 months and we had no reason to believe it would soon quadruple.

Finally, remember that if we vote this proposal down, it will be the SECOND TIME in less than a year that the Dash Network has defaulted on a legal contract (the first was Terpin PR). It won't be much longer before vendor partners refuse to do business with us, and rightly so. It also opens up either Evan, Daniel, or the Dash Foundation (depending on who signed the contract) to civil litigation. Do you want Dash development stalled while our Core Team redirects its energies and funds to fight a lawsuit?

It's important to note that every single budget proposal is an investment in Dash's ecosystem. There is always the risk that some investments won't pay off--just as with the stock market. We are starting to see a few of these investments stumble (Website, Lamassu) and at least one has completely flopped (that guy that requested multimonth funding to build a fiat exchange and got only got one month's worth and thus couldn't finish). We should be prepared for the occasional failure!
 
Last edited:
Frankly, the Network entered into a contract with GitGuild to do work on a third-party application (from Lamassu). If Lamassu has (temporarily) blocked GitGuild's work, then that is not GitGuild that is to blame, but our own Network for not taking into account that risk factor. Why should we breach our contract with GitGuild because of our own errors in judgment?
...
Personally I do not agree. The risk of not delivery of what was promised in a proposal is for both parties - network and contracted entity. By not delivering what was promised contracted entity breaks the contract in the first place so I don't see why would you blame network for stopping payments.

...
Finally, remember that if we vote this proposal down, it will be the SECOND TIME in less than a year that the Dash Network has defaulted on a legal contract (the first was Terpin PR). It won't be much longer before vendor partners refuse to do business with us, and rightly so. It also opens up either Evan, Daniel, or the Dash Foundation (depending on who signed the contract) to civil litigation. Do you want Dash development stalled while our Core Team redirects its energies and funds to fight a lawsuit?
...
That's the design of current system and every contractor should be aware of such limitations and risks and accept them, otherwise there is no deal at all. And by accepting them he has no rights to fill a lawsuit against network which is funding his proposal (not sure how he would fill such a lawsuit at all) or it's a twisted logic otherwise. Not to mention that he has no rights to fill a lawsuit against any of Core Team members, they do not fund any proposals. Unless some of them signed a contract personally of course.
 
Finally, remember that if we vote this proposal down, it will be the SECOND TIME in less than a year that the Dash Network has defaulted on a legal contract (the first was Terpin PR). It won't be much longer before vendor partners refuse to do business with us, and rightly so. It also opens up either Evan, Daniel, or the Dash Foundation (depending on who signed the contract) to civil litigation. Do you want Dash development stalled while our Core Team redirects its energies and funds to fight a lawsuit?

Dude. That's not how it works. The budget system allows for a multi-month proposal to be voted down on any given month. Further, I don't think that anyone minds that partners who want to scam us refuse to do business with us. What should have happened is that the very minute that Lamassu threw a wrench into things, the network should have been fully informed of the impact, and then given the opportunity to continue or stop the project.

No. I don't want the development team slowed down. That's why this project should never have been started. The funds should have gone to development. Same goes for the legal, compliance and PR related proposals. What is happening here is that Ryan, Daniel and Tungfa need to justify their participation in Dash, so this stuff gets started and becomes a mess. Get rid of it all, and direct the resources to Evolution development.

Your 'word-spin' is not good enough to fool anyone.
 
There is no such thing as the Dash network breaching a contract. The network cannot enter into a contract. If a proposal owner made a legal contract, and is stuck with the bill because the network ceases funding, then it is the proposal owner's own fault for assuming unnecessary risk by not making the legal contract contingent on the network funding.

People who work for our DAO need to understand that they can't expect continued funding if they fail to deliver.
 
I just want to say I down-voted this a while back based on the fact this has not gone as planned. No need to fight, just dow-nvote with your nodes and if other people agree, this proposal will be voted off the budget :).

Pablo.
 
I just want to say I down-voted this a while back based on the fact this has not gone as planned. No need to fight, just dow-nvote with your nodes and if other people agree, this proposal will be voted off the budget :).

Pablo.

Or, increase the competition with lots of high quality budget props. Make the MNs an offer they can't refuse and get the lesser performing ones bumped :)
 
Personally I do not agree. The risk of not delivery of what was promised in a proposal is for both parties - network and contracted entity. By not delivering what was promised contracted entity breaks the contract in the first place so I don't see why would you blame network for stopping payments.


That's the design of current system and every contractor should be aware of such limitations and risks and accept them, otherwise there is no deal at all. And by accepting them he has no rights to fill a lawsuit against network which is funding his proposal (not sure how he would fill such a lawsuit at all) or it's a twisted logic otherwise. Not to mention that he has no rights to fill a lawsuit against any of Core Team members, they do not fund any proposals. Unless some of them signed a contract personally of course.

"Should" being the operative world. I suppose it depends on how the agreement was structured. If I was a vendor, I would want a signed contract before commencing work. That means some legal entity (human, corporation, or foundation) has to actually sign the document. That entity is then responsible for breach of contract if the terms are violated.

Regardless of whether there was a legal contract, precedent is a powerful thing. I wouldn't want our network to become known for breaching contracts. Besides, do you really expect every vendor/partner to become an expert on our budget system? For most people, it would never occur to them that once an agreement is made, funding can be cut off at any time.

While obvious to us, a vendor might not realize that there are three parties to any agreement: themselves, the human or organization they accept the assignment from, and the Network that issues payment.
 
They didn't get a signed contract. Precedent is a powerful thing. Do you want our network known for requiring no deliverables, no progress reports, no expense reports, no accountability and no transparency? Because that is exactly what is happening with the Scamassu project.

Also, there are only 2 parties to these agreements; the proposal budget recipient, and the network.

Please stop spinning words. It isn't helping your cause - we can see right thru it.

I mean really - is there ANY business ANYWHERE that gives out money for projects, without any deliverables, progress reports, expense reports, or accountability and transparency? I guess there are some - the ones that fail fast.

If Dash hits $100.00 then we are talking about $1,000,000 per month that will be spent this way. Corruption will be rampant.

Dash is supposed to have a GOVERNANCE system, but I don't see any tools/information to support governance. Just votes.
 
If a third party code change is to blame for development slow down or stoppage then payments should be put on hold as well until a reasonable solution can be submitted.

There is still no scripts, to my knowledge, no actual guide to follow on how to actually make a lamassu vend DASH.. @issyd please I hope you and your team have finalized some guides so we could at least have some people validate, right now to me I feel the status reports just looks like a bunch of marketing and hype about how CTMs work..
 
The last I heard (a few weeks ago) from the only actual client I am aware of who has a Lamassu ATM and wants to install the Dash software (@cryptoatm), has been trying for months to get support from TigoCTM, was repeatedly told to wait for documentation and eventually had a phone call for a few hours, and to my knowledge has still not been able to get it working. I'd be interested to hear if there is any update on this, or if anyone, anywhere, has been able to set up a fully functional ATM.

I would also point out, we keep spending so much time on the seemingly horrific execution of this project, that I think some of us might be missing another key point which is that crypto ATMs are arguably one of the worst, inefficient, and unprofitable ways towards adoption. If you build 100 ATMs, how many people in the world are going to physically go to one of those locations to buy Dash? And to spend it where? You end up with the occasional rare extreme crypto enthusiast who might drop a few bucks on it as a novelty. This, versus developing online or mobile apps to give millions of people access to buy Dash at any time, any place with as painless a user experience as possible, and places to spend Dash. I would argue that crypto ATMs have done almost nothing to speed up Bitcoin adoption when compared to other entry points, and operating one is rarely profitable. The market demand for this is just not there. Dash would be wise to learn from this as it makes its business decisions.
 
Last edited:
Back
Top