[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[qwizzie]

I'm sure this question has been asked but can't really find anything...

What is the current 'range' of annual ROI? [projected annual ROI]


TIA
[thx in advance]

https://dashpay.atlassian.net/wiki/questions/12910621/how-much-is-the-roi-of-a-masternode

you can use moocowmoo's sheet to calculate it..

[Minotaur26]

Am I the only one who gets a little bit uneasy about the fungibility part lately? How is the priority currently beside all the other features? The sooner we get rid of this long darksend times, the better. When do you think the "separate paper" about Privacy & Fungibility is ready Evan? Thank you.

I'm currently looking at doing single layer DS through the DAPI implementation, which would also be blinded by network relay. DS is impenetrable at a single layer if it's blinded by the network. This would bring down mix times per 0 to 1000 dash to a few seconds on the network.  Also, it doesn't cause as much bloat of the network to keep the privacy and fungibility. I think it'll work well.

This is out of scope for the next prototype though, we want to create something super simple.

I was hoping you might have been looking to implement zk-SNARKs/zerocash as it looks very private and very fast.

I think there is one very important thing in my opinion, I think we should keep fungibility without recourse to obscurity.  I think this is one of the main differentiators in Dash, that we preserve the public blockchain for public audit while giving the users an option for privacy.  After speaking with many people from the industry during the show in Mexico I think this is a really good model. In crypto there are no counter parties so the fact that any user can verify the public ledger to see it is working correctly is really powerful and accomplishing user privacy while preserving this property is ideal in my opinion.

Improving all these aspects while staying compatible with Bitcoin gives everyone a sense of security and it will show more and more in terms of adoption as time goes by.

[eduffield]

We're working on the prototype design... feel free to give input

https://docs.google.com/document/d/1xD0ACmiTEQ1KEMNC6FWrWi1Rh_ipmPMn8L3zvR11GA4/edit?usp=sharing

I just allowed public commenting on the document in the settings, feel free!

[qwizzie]

Unbelievable!  The Trolls on mass have been absent for almost 2 full days, If this isn't proof positive that there was a coordinated attack vector by the several trolls on here and that they were in collusion together for the last year.. Then I don't what is.  

yep, although it looks like we will experience some troll detox a few days while getting all those anti-troll reflexes out of our system.
But the good news is : we have our forum back !!

Which means we can discuss the Evolution Prototype undisturbed....

We're working on the prototype design... feel free to give input

https://docs.google.com/document/d/1xD0ACmiTEQ1KEMNC6FWrWi1Rh_ipmPMn8L3zvR11GA4/edit?usp=sharing

Tab: Contacts

Show the “Friends” or “Contacts” of the user. This should be queried from the system using the user’s profile. Should this feature be called “Friends” or “Contacts”?

i'm thinking "Contacts"

I'm also thinking we should discuss this on our Dashtalk forum to include as many people as possible and also to
inform everyone that we are looking for someone with experience in javascript to help us with this wallet.

I just forked DarkWallet and mocked up a client, what do you think?

It seems like it might be a great platform for connecting to DAPI. The code is really nice as well. If anyone looking at this is really good at javascript and wants to help, I see a role for you! Email me at evan@dash.org.

[stan.distortion]

Am I the only one who gets a little bit uneasy about the fungibility part lately? How is the priority currently beside all the other features? The sooner we get rid of this long darksend times, the better. When do you think the "separate paper" about Privacy & Fungibility is ready Evan? Thank you.

I'm currently looking at doing single layer DS through the DAPI implementation, which would also be blinded by network relay. DS is impenetrable at a single layer if it's blinded by the network. This would bring down mix times per 0 to 1000 dash to a few seconds on the network.  Also, it doesn't cause as much bloat of the network to keep the privacy and fungibility. I think it'll work well.

This is out of scope for the next prototype though, we want to create something super simple.

I was hoping you might have been looking to implement zk-SNARKs/zerocash as it looks very private and very fast.

I think there is one very important thing in my opinion, I think we should keep fungibility without recourse to obscurity.  I think this is one of the main differentiators in Dash, that we preserve the public blockchain for public audit while giving the users an option for privacy.  After speaking with many people from the industry during the show in Mexico I think this is a really good model. In crypto there are no counter parties so the fact that any user can verify the public ledger to see it is working correctly is really powerful and accomplishing user privacy while preserving this property is ideal in my opinion.

Improving all these aspects while staying compatible with Bitcoin gives everyone a sense of security and it will show more and more in terms of adoption as time goes by.

Maybe but if you could make that optional then you get the best of both worlds, entirely transparent public records when you want them and gone and forgotten when you don't. You could probably charge for it too, it will be using up storage resources so a charge is justifiable, it would be great if stored transactions could be charged for a period and dropped after, for ex. keep accounts for 3 years but I'm not sure if that kind of pruning is possible.

[Solarminer]

Am I the only one who gets a little bit uneasy about the fungibility part lately? How is the priority currently beside all the other features? The sooner we get rid of this long darksend times, the better. When do you think the "separate paper" about Privacy & Fungibility is ready Evan? Thank you.

I'm currently looking at doing single layer DS through the DAPI implementation, which would also be blinded by network relay. DS is impenetrable at a single layer if it's blinded by the network. This would bring down mix times per 0 to 1000 dash to a few seconds on the network.  Also, it doesn't cause as much bloat of the network to keep the privacy and fungibility. I think it'll work well.

This is out of scope for the next prototype though, we want to create something super simple.

We will need a way to return funds, for example a gas station.  You send $50 in Dash and what you don't use gets returned.  There is really no way around this unless the merchant is really trusting, or customer has a credit line.  This is also useful for an oops just send 100 dash for the 1 dash purchase.  The merchant can be nice and just send your overpayement back.  Especially important if there isn't a name/identity associated with a transaction.

Right now for a standard transaction you can lookup an input address and just send back to that.  If you darksend the whole network we will need a return address in every transaction, because there would be more than one wallet sending inputs.  Maybe this return address is in a message that is only known to the receiver.  Or maybe flag one of the inputs as the primary return input.  Maybe there is a way to make sending to the address backwards a return.  1234 sends out and 4321 receives.  Now that would be neat except it probably removes some privacy.

[stan.distortion]

Maybe but if you could make that optional then you get the best of both worlds, entirely transparent public records when you want them and gone and forgotten when you don't.

 

On the flip side trying to do that might hide the coin supply so it'd be impossible to verify there really is a limit and that wouldn't do a whole lot for trust. No idea what's possible with the second tier though, could be its all there in plain sight but who owns what is hidden, it's essentially a proven rock solid security backbone to build on so all kinds of things could be possible.

[dEBRUYNE]

Maybe but if you could make that optional then you get the best of both worlds, entirely transparent public records when you want them and gone and forgotten when you don't.

 

On the flip side trying to do that might hide the coin supply so it'd be impossible to verify there really is a limit and that wouldn't do a whole lot for trust. No idea what's possible with the second tier though, could be its all there in plain sight but who owns what is hidden, it's essentially a proven rock solid security backbone to build on so all kinds of things could be possible.

The only way you can hide the coin supply is by fully obscuring the coinbase transaction. In all other cases, you can still verify that the current supply is what it should be. Exactly this is the biggest caveat for a system like ZeroCash, it is so obscure that you can't verify the coin supply, so if someone created a bug somehow that generated 1 million additional coins, there would be no way of knowing that. 

[BrainShutdown]

I'm quoting this because I don't see yet the reason why are we derailing from the fundamentals exposed by toknormal.

Why do we need to bring the concept of users to Evolution?
Shouldn't DAPI be higher level than that and allow the various entities using it to create those concepts if they need to (users, messaging, file storage/share)?

I agree that verbal communication is sometimes important when co-ordinating payments, but please folks, stop. And think.

There is a trap that is one of the first pitfalls in software design, and that is loosing sight of your product's priority in favour of all the supporting ones that are not a priority. We live in a technology eco-system. The trick is to understand how that ecosystem sees you - not how you see it since it has options, you don't.

There's a tendency when developing product ideas to adopt an asymmetric, product centric view whereby the product 'becomes' the market instead of a market player.

As a great example of this, I knew a guy who built an online retailing service in the far east. His little company bought stuff (clothes, souvenirs) in little markets and shipped it around the world - acting as a proxy for people perusing the market themselves. (At that time you could only get mainstream, Amazon type stuff online). He got very excited about this business model and wanted to extend it to "any type of product from anywhere". In that vein he started buying up domain names around the theme of "shipdirect2U" and "worldDirect2U".

I tried to advise him that what he was seeing in his mind was the eco-system projected onto a product, not a product that would become the eco-system but he couldn't see it. 15 years later his vision has manifested - except it's called Google Shopping Feed and is contributed to by thousands of businesses all over the world.

What we need to do is ditch our product-centric view and switch to seeing how the world views the product. How and why will it pick it out amongst the myriad of other options it has ?



Form the "world's" perspective, Dash as a product does three things very well and three things only IMO:

[1] - being a public blockchain asset

[2] - fulfilling the monetary requirements of cash, being that it fully addresses bitcoin's fungibility and transaction time shortfalls

[3] - does the above with a technology stack thats largely compatible with bitcoin's

In fact it does those things so well that it's in a class of its own with regard to those three properties in combination.

There are of course other things that set it apart - like the articulated protocol etc - but they aren't things that "world" is going to care about to the extent that it can pick Dash out amongst the mass of options. They are not 'visible' to the market, they only support the 'visible' properties that I listed above.

Dash doesn't do chat, doesn't do online storage (other than blockchain), doesn't do social media and I don't think it should try to do any of those. However it can make itself "digestible" by social media applications which is the right way around for things IMO.

Re. Bells & Whistles
What do people do when they need to co-ordinate payments right now ? They pick up the phone. What do they do when they need internet voice-comms ? Get onto Skype. If you happen to be one of the miniscule percentage of people who require encrypted comms while they are making payments then there's always...

I use Team-viewer a lot which now has a built in chat feature, but I never use it because my 'perception' of Teamviewer is as a screensharing tool and Skype as a chat tool.

In summary - ok, lets have a brainstorm about everything - but I think any feature that isn't directly (or at least indirectly) supporting one of Dash's primary objectives as a highly fungible, anonymous, sustainably developed electronic currency asset needs to be regarded as 'excess baggage' by default. Those that are thought to be supporting Dash's primary market objectives need to have their roles well defined and in the appropriate context.

For example, the Facebook API example is a social media tool but which DOES have a definite role in supporting the currency since people already use Facebook but cannot spend Dash on their Facebook page. Adding social media features to a Dash wallet reverses this logic: the target market does NOT use Dash wallets and they CAN currently do social media, ergo: fail. (Dare I say...#R3.. ? LOL ! )

IMO, what Evan drew in that mockup posted earlier is similar to my mate from the Far East's 1999 view of the market - i.e. it is a symbolic illustration of how Dash will eventually integrate with the eco-system but not a realistic component of that ecosystem.

[toknormal]

On the flip side trying to do that might hide the coin supply so it'd be impossible to verify there really is a limit and that wouldn't do a whole lot for trust. No idea what's possible with the second tier though, could be its all there in plain sight but who owns what is hidden, it's essentially a proven rock solid security backbone to build on so all kinds of things could be possible.

The way I look at the blockchain and its 'public consensus' verification is like an ant hill.

No one ant is conscious of the hill to the extent it can 'design', build it or inspect it. The hill's integrity arises from the aggregation of thousands of ants all behaving roughly similarly at a small scale but distributed evenly throughout the scope of the construction.

Similarly, the 'public blockchain' is being inspected every second of every minute of every day by 'ants': people who use a variety of access points (their own wallets, block explorers, API's, aggregated reporting tools etc) to check stuff. They're not actually doing a formal inspection of the blockchain - they're just verifying individual transactions they made or somebody else made or doing research or whatever. It's this sum total of 'ant activity' that gives the blockchain its integrity and resistance against confidence attacks such as media scares, rogue blockchain clients, rumour, whatever.

This "ant like" verification process means that all of the bockchain is being crawled over all of the time and keeps confidence high and consensus intact. You can't just hide some of it and show some of it, then the ant hill has a hole in it thats invisible which renders the rest of the 'inspection process' meaningless.


Note that credit systems (like the fiat banking system) don't need this public consensus mechanism because value is maintained by contract, not public consensus. Regardless of the integrity of the transport mechanism, the debtor (bank) is contractually obliged to honour the creditor's balance. Since contracts are between named entities who cannot be anonymous, credit systems use obfuscation to support privacy while cash uses fungibility.

[Solarminer]

I'm quoting this because I don't see yet the reason why are we derailing from the fundamentals exposed by toknormal.

Why do we need to bring the concept of users to Evolution?
Shouldn't DAPI be higher level than that and allow the various entities using it to create those concepts if they need to (users, messaging, file storage/share)?

I agree that verbal communication is sometimes important when co-ordinating payments, but please folks, stop. And think.

There is a trap that is one of the first pitfalls in software design, and that is loosing sight of your product's priority in favour of all the supporting ones that are not a priority. We live in a technology eco-system. The trick is to understand how that ecosystem sees you - not how you see it since it has options, you don't.

There's a tendency when developing product ideas to adopt an asymmetric, product centric view whereby the product 'becomes' the market instead of a market player.

As a great example of this, I knew a guy who built an online retailing service in the far east. His little company bought stuff (clothes, souvenirs) in little markets and shipped it around the world - acting as a proxy for people perusing the market themselves. (At that time you could only get mainstream, Amazon type stuff online). He got very excited about this business model and wanted to extend it to "any type of product from anywhere". In that vein he started buying up domain names around the theme of "shipdirect2U" and "worldDirect2U".

I tried to advise him that what he was seeing in his mind was the eco-system projected onto a product, not a product that would become the eco-system but he couldn't see it. 15 years later his vision has manifested - except it's called Google Shopping Feed and is contributed to by thousands of businesses all over the world.

What we need to do is ditch our product-centric view and switch to seeing how the world views the product. How and why will it pick it out amongst the myriad of other options it has ?

Form the "world's" perspective, Dash as a product does three things very well and three things only IMO:

[1] - being a public blockchain asset

[2] - fulfilling the monetary requirements of cash, being that it fully addresses bitcoin's fungibility and transaction time shortfalls

[3] - does the above with a technology stack thats largely compatible with bitcoin's

In fact it does those things so well that it's in a class of its own with regard to those three properties in combination.

There are of course other things that set it apart - like the articulated protocol etc - but they aren't things that "world" is going to care about to the extent that it can pick Dash out amongst the mass of options. They are not 'visible' to the market, they only support the 'visible' properties that I listed above.

Dash doesn't do chat, doesn't do online storage (other than blockchain), doesn't do social media and I don't think it should try to do any of those. However it can make itself "digestible" by social media applications which is the right way around for things IMO.

Re. Bells & Whistles
What do people do when they need to co-ordinate payments right now ? They pick up the phone. What do they do when they need internet voice-comms ? Get onto Skype. If you happen to be one of the miniscule percentage of people who require encrypted comms while they are making payments then there's always...

I use Team-viewer a lot which now has a built in chat feature, but I never use it because my 'perception' of Teamviewer is as a screensharing tool and Skype as a chat tool.

In summary - ok, lets have a brainstorm about everything - but I think any feature that isn't directly (or at least indirectly) supporting one of Dash's primary objectives as a highly fungible, anonymous, sustainably developed electronic currency asset needs to be regarded as 'excess baggage' by default. Those that are thought to be supporting Dash's primary market objectives need to have their roles well defined and in the appropriate context.

For example, the Facebook API example is a social media tool but which DOES have a definite role in supporting the currency since people already use Facebook but cannot spend Dash on their Facebook page. Adding social media features to a Dash wallet reverses this logic: the target market does NOT use Dash wallets and they CAN currently do social media, ergo: fail. (Dare I say...#R3.. ? LOL ! )

IMO, what Evan drew in that mockup posted earlier is similar to my mate from the Far East's 1999 view of the market - i.e. it is a symbolic illustration of how Dash will eventually integrate with the eco-system but not a realistic component of that ecosystem.

My opinion is that we should be focusing on how merchants can accept Dash easily and how mobile phones can send Dash.  Both areas need to be fast and use low resources(so any phone can work fast).  This is really where Dash can shine.  Bitcoin already has the computer to computer stuff down(slow but works).  Maybe we need NFC implemented and ignore the contacts portion.  And maybe the mobile wallets don't even do anything on the blockchain, they just tell the merchant terminal to do the work.  Or vice versa - maybe the merchant doesn't need internet and the phone confirms the transaction for the merchant.

I am finding that it isn't a slam dunk to accept dash from the merchant side.  We may have a nice surprise product showcase in Miami.....work is in progress.

The file storage is needed so every wallet doesn't have to download the huge blockchain.  It enables phones and everything else to work fast.  I don't see the file storage as a shared resource for 3rd parties, just a blockchain storage device in masternodes.

[stan.distortion]

...
The way I look at the blockchain and its 'public consensus' verification is like an ant hill.
...

True but if everything's being done through the DAPI then eventually all the ants are masternodes and the anthill a tier in the network and they can be specialised ants seeing the hill in specialised ways that don't necessarily need to be visible from outside, just provable in the source and whatever else is needed for confidence in the network.

Anyway, what I was suggesting there is hypothetical and BrainShutdowns post isn't so probably best at least keeping that one going.

Why do we need to bring the concept of users to Evolution?
Shouldn't DAPI be higher level than that and allow the various entities using it to create those concepts if they need to (users, messaging, file storage/share)?

If it's a remote service then users are there regardless, there has to be some means of logging into it so figuring out what else can be done with that concept once it's introduced is a natural progression, digital cash is still the core function of the network and things that add value for those users add to it further.

[BrainShutdown]

The need for distributed SPV  and DAPI implementations of contracts and multisig is clear and should be a priority IMHO.

Maybe some kind of alias is needed for a merchant to be visible (ie. no more ugly pubkeys)

So lets imagine I am a merchant that wishes to implement dash payments. As I see it I would need to create a wallet first and should be like creating an HD wallet. Now I only need an SPV client connected to DAPI to monitor the transactions. Now I need to integrate with my billing/management software (this is very specific and out of Evolution - market oportunity for developers)

Then I need that my clients know where to send money (QR codes are the best thing we have now I guess), this is where some improvements could be made.

So the client now could pick is phone, scan the QR and hit PAY. InstantXly I get the payment confirmation in my register SPV'd machine with DAPI integration and that's it.

From the brick and mortar perspective I continue to fail to see the need for users/messages... but I'm probably missing something 

[italeffect]

I just want to point out the high quality, great discussion that has been occurring over the last few pages. Makes me nostalgic for times past.

Granted there have been none of the endless troll posts, but more importantly, instead of pages of everyone responding to the trolls, there is an actual discussion! And Evan even joined in!

Glad I hadn't given up on this place completely. Keep it up!

Edit: typos

[qwizzie]

The need for distributed SPV  and DAPI implementations of contracts and multisig is clear and should be a priority IMHO.

Maybe some kind of alias is needed for a merchant to be visible (ie. no more ugly pubkeys)

So lets imagine I am a merchant that wishes to implement dash payments. As I see it I would need to create a wallet first and should be like creating an HD wallet. Now I only need an SPV client connected to DAPI to monitor the transactions. Now I need to integrate with my billing/management software (this is very specific and out of Evolution - market oportunity for developers)

Then I need that my clients know where to send money (QR codes are the best thing we have now I guess), this is where some improvements could be made.

So the client now could pick is phone, scan the QR and hit PAY. InstantXly I get the payment confirmation in my register SPV'd machine with DAPI integration and that's it.

From the brick and mortar perspective I continue to fail to see the need for users/messages... but I'm probably missing something  

yr missing the localbitcoin market that the third tier will provide, the fiat/crypto transactions between users that can be initiated with messages...

qwizzie --> msg --> Otoh : interested in converting EUR to Dash ?
(as example)

These local bitcoin trades between users will also need to be rated / commented so in the end we can create our own internal trusted (build up of trust but also with multisig ?) fiat/crypto supply and demand
and not be dependent on external parties like exchanges..

selfsufficiency is the keyword here i guess

edit : could also be seen as an attempt to decouple from Bitcoin ?

[ddink7]

The need for distributed SPV  and DAPI implementations of contracts and multisig is clear and should be a priority IMHO.

Maybe some kind of alias is needed for a merchant to be visible (ie. no more ugly pubkeys)

So lets imagine I am a merchant that wishes to implement dash payments. As I see it I would need to create a wallet first and should be like creating an HD wallet. Now I only need an SPV client connected to DAPI to monitor the transactions. Now I need to integrate with my billing/management software (this is very specific and out of Evolution - market oportunity for developers)

Then I need that my clients know where to send money (QR codes are the best thing we have now I guess), this is where some improvements could be made.

So the client now could pick is phone, scan the QR and hit PAY. InstantXly I get the payment confirmation in my register SPV'd machine with DAPI integration and that's it.

From the brick and mortar perspective I continue to fail to see the need for users/messages... but I'm probably missing something  

yr missing the localbitcoin market that the third tier will provide, the fiat/crypto transactions between users that can be initiated with messages...

qwizzie --> msg --> Otoh : interested in converting EUR to Dash ?
(as example)

These local bitcoin trades between users will also need to be rated / commented so in the end we can create our own internal trusted (build up of trust but also with multisig ?) fiat/crypto supply and demand
and not be dependent on external parties like exchanges..

selfsufficiency is the keyword here i guess

edit : could also be seen as an attempt to decouple from Bitcoin ?

You could essentially use this to have fiat converters right off the bat (albeit without the built-in reputation system yet)

[qwizzie]

The need for distributed SPV  and DAPI implementations of contracts and multisig is clear and should be a priority IMHO.

Maybe some kind of alias is needed for a merchant to be visible (ie. no more ugly pubkeys)

So lets imagine I am a merchant that wishes to implement dash payments. As I see it I would need to create a wallet first and should be like creating an HD wallet. Now I only need an SPV client connected to DAPI to monitor the transactions. Now I need to integrate with my billing/management software (this is very specific and out of Evolution - market oportunity for developers)

Then I need that my clients know where to send money (QR codes are the best thing we have now I guess), this is where some improvements could be made.

So the client now could pick is phone, scan the QR and hit PAY. InstantXly I get the payment confirmation in my register SPV'd machine with DAPI integration and that's it.

From the brick and mortar perspective I continue to fail to see the need for users/messages... but I'm probably missing something  

yr missing the localbitcoin market that the third tier will provide, the fiat/crypto transactions between users that can be initiated with messages...

qwizzie --> msg --> Otoh : interested in converting EUR to Dash ?
(as example)

These local bitcoin trades between users will also need to be rated / commented so in the end we can create our own internal trusted (build up of trust but also with multisig ?) fiat/crypto supply and demand
and not be dependent on external parties like exchanges..

selfsufficiency is the keyword here i guess

edit : could also be seen as an attempt to decouple from Bitcoin ?

You could essentially use this to have fiat converters right off the bat (albeit without the built-in reputation system yet)

its some bold thinking by dev-team

[BitWater]

The trolls have left because they would be putting a big spotlight on all the new developments going on with Dash, while they still are just trying to get their coin working.

With headlines saying the Bitcoin Foundation is nearly out of money, DGBB brings a solution to this.

Remaining BTC compatible might have been one of the best decisions the Devs made regarding Dash, because they're becoming plagued with issues, and here we are fixing the problems of BTC.

The one thing I've noticed though, is trading seems to be artificially suppressed on the downside, on poloniex you can see several instances of Dash trying to hit new highs but meeting upwards resistance. Wonder what is causing this?

[qwizzie]

The trolls have left because they would be putting a big spotlight on all the new developments going on with Dash, while they still are just trying to get their coin working.

With headlines saying the Bitcoin Foundation is nearly out of money, DGBB brings a solution to this.

Remaining BTC compatible might have been one of the best decisions the Devs made regarding Dash, because they're becoming plagued with issues, and here we are fixing the problems of BTC.

The one thing I've noticed though, is trading seems to be artificially suppressed on the downside, on poloniex you can see several instances of Dash trying to hit new highs but meeting upwards resistance. Wonder what is causing this?

some bot keep placing very small sell orders after each buy-order (between 0.00xx and 0.03) but we do seem to be approaching a new trend on the 4h i noticed
https://bitcointalk.org/index.php?topic=1233119.msg13205090#msg13205090 (that link is from some 5 hours ago)

[GhostPlayer]

The trolls have left because they would be putting a big spotlight on all the new developments going on with Dash, while they still are just trying to get their coin working.

With headlines saying the Bitcoin Foundation is nearly out of money, DGBB brings a solution to this.

Remaining BTC compatible might have been one of the best decisions the Devs made regarding Dash, because they're becoming plagued with issues, and here we are fixing the problems of BTC.

The one thing I've noticed though, is trading seems to be artificially suppressed on the downside, on poloniex you can see several instances of Dash trying to hit new highs but meeting upwards resistance. Wonder what is causing this?

 apparently there is a cracked GTA V torrent that contains an x11 miner.