But Darkcoin is not a scrypt-based. I highly doubt their asic would work with x11. If asics did come it would definitely drive to block reward down to 5 and probably help the price that way... so it probably wouldnt be that bad tbh. Even though I love mining x11  It won't work. They made the error of listing Darkcoin as an scrypt coin, which is not. IMO Darkcoin will need a large number of privately-held ASICs to secure it. We, miners, tend to lose focus of the important thing which is network security, caring only about how our GPU should still mine the X or Y coin. Darkcoin is not a meme coin, an animal coin, a country shitcoin or whatever the hell coin that nobody cares to attack it. It has a target painted on its back because it threatens the establishment's ability to conduct surveillance on money flows. As such we can bet that the NSA has already X11 ASICs ordered to be ahead of the game. It would be highly unlikely that with their multi-billion $$$ budget they would not have taken such a step. The question is this: Do we want only NSA to have X11 asics and be able to 51% attack it at any time (or get the bulk of the issued new coins to use them for Darksend nodes), or is it more desirable to have a level playing field? You can't have a bitcoin-killer that isn't secure or that has a potential security threat due to mismatched level of mining equipment between the adopters and some agency that has orders to destroy the currency, or cast shadows of doubt in its usability. Ok, I like to mine DRK too with my GPUs but I'd take an ASIC-secured network anyday over me having my GPU to get my 1 DRK vs knowing the NSA has ASICs ready to make my GPU-mined DRKs worthless, along with the entire network. 99% of the coins out there pose no threat to the establishment and as such can toy around with cpus and gpus, knowing that nobody will attack them. Darkcoin doesn't have that kind of luxury. It will need all the hashpower it can get. |
|
|
|
Anyone know why it takes sgminer 45 minutes to start mining Darkcoin.
I am using XUBUNTO
Each and every time takes 45 mins to start.
The first time sgminer starts will create a .bin file (the kernel). If the CPU of the machine is too slow it can take a long time. However this is supposed to happen only the first time it runs and then the .bin file is stored on the directory. If you are using some kind of read-only medium (flash/cd etc) that doesn't allow writing, the .bin file will need to be re-created every single time you run the program. 45 minutes is too long anyway, but use "top" in another console to check memory and cpu use during these 45 minutes. If it's high cpu use, increased ram etc, then the kernel is being created. If nothing happens, then it's something else. |
|
|
|
I think we need to stress this point in our marketing: Darkcoin is more fungible than bitcoin. This is an incredible advantage for a currency.
How do you mean that? |
|
|
|
I would like to ask the devs to make it compulsory to include the blockchain as part of the supernodes, and have it as 'read by anyone'.
I think that once we have the supernodes up and running with a readable blockchain that is accessible by anyone, different services might evolve independent of the darkcoin devs on top of this, such as the thin wallet described by TS.
I think masternodes should not be merged with the task of preserving a blockchain for all others, as this would seriously impact on their bandwidth + increase the vulnerability of the network by taking down a large number of them. I believe that a different solution, based on a similar concept, can be employed. Just as darksend nodes will get 10% of the mining output, we can have blockchain nodes that are simply used to preserve the blockchain while others enjoy some thin clients in their mobile phones, tablets etc. Blockchain nodes could receive, say, 5-10% of the mining output for providing the service of storage and network bandwidth. Unlike darksend nodes which are limited in number, blockchain nodes could be in the thousands (=good for network security). In a sense we create a new type of masternode, with a different functionality. If someone wants to run both on the same machine (darksend node / blockchain node) he can. |
|
|
|
I missed this boat completely sadly..
Said no one wealthy, ever.. Exactly. I remember people with BTC: 10$ "it's a bubble" 35$ "it's a bubble" 70$ "it's a bubble" 150$ "it's a bubble" 300$ "it's a bubble" 1200$ "damn wish I had some" 2x for DRK (from 1$ to 2$) is nothing in comparison in terms of the train having reached the destination. But then again people thought Litecoin was doomed to 3-4$ max and then it went to 50$. |
|
|
|
Huge buy walls on cryptsy and mintpal  Nethash >50GH, block reward 9.  Crazy, not sure why so many are mining it right now when you can easily double your mining profits by mining other stuff and just buying DRK. Maybe everyone is totally confident in another upwards price correction, or maybe they are just lazy miners lol. Electric cost is too high in many areas for mining to be profitable. Half the electric cost can be a huge gain in such instances. http://drk.poolhash.org/graph.htmlDiff ~2k, block reward 8. Interesting. |
|
|
|
I think people are selling darkcoin to move into dogecoin because of the halvening!
Last halving didn't do much for the price if I recall correctly. It actually fell... So what's everyone's predictions for the near future? Waiting to see some movement due to RC2 release? Going to try and short DRK?
Short term prediction: The market will remain unpredictable due to whale movements. |
|
|
|
Seems the whales indeed found too shallow waters in DRK and moved on.
Has correction been established? Whats the criteria?
Nope, this isn't correction. A lot people got in recent days because they expected Drk countinue growing and give them short term profits. If Drk don't increase any more in next 2-3 weeks, they'll start selling and price will slowly decrease. I agree and honestly we can do without the whales for a bit ! Keep it steady, the markets will show when the next releases are out. Stocked up a bit before it all hit, and am set for the next round …>> I think the whales are lurking, waiting for the market players to get bold with their orders, or fill the orderbook around the 360-400 level that seems relatively stable and then sweep it all. I've been noticing large buy orders at <400 levels and there's too little selling on the whales there (meaning <400) making it more costly for them to acquire the DRKs. 550 though is a point where many have demonstrated their willingness to sell. The whale, IMO did a mistake in how they went after the pumping. He allowed people to get back in and buy back lower which they used to dump on the whale in the next spike. He should lock everyone out by taking their DRKs and game over for everyone selling. Stabilize the price at increasingly higher levels with buy walls and force everyone to panic buy their way back in - escalating the price further. Just my 2 whale cents  |
|
|
|
I don't think there's been an official statement about chained pooling being built into Darksend. AFAIK it's just an idea that was tossed around. Personally I think it's necessary for any usable level of anonymity (preferably with the ability to specify whitelisted masternodes).
I think it was mentioned, in the discussion between evan/anonymint that by darksending it multiple times through a number of nodes it reduces the bad-actor probabilities to a statistically safe degree to solve the issue that the darksend node knows who sends what. ok -- but with a timing analysis, the number of transactions in (let's say) a 60 second window will be relatively few, so it's not too hard to reconstruct what really happened, especially with uncommon amounts (e.g. I send you 16.023957).
Unless you force people to use 10/1/0.1/0.01 and everything is grouped in batches of that kind and it is stretched out over more time. I think this will be a case of continuous upgrade of the anonymity capabilities (DarkSend 1, 2, 3, 5, 10, 50 etc) with extra features / capabilities / improvements as we go along... |
|
|
|
It then compares the changes that occurred in those addresses in the last 2.5min [from its previous check] and knows exactly who transferred coins to whom.
Because it doesn't know who had them in the first place. It doesn't know if it's the same person sending to self. Darksend moves in blocks of fixed size and provides change back on new addresses. The blockchain keeps track of all of that anyway, why does a person have to be NSA? It's all in the blockchain... Why monitor? I don't get it. I think you just have a fundamental lack of understanding in how any crypto coin works. I'm not even sure where to start in trying to help you understand. Not an insult... You just don't have enough basic knowledge to have this conversation. That's kind of condescending. You could have just said, "an attacker can query the blockchain rather than constantly monitoring balances", and then answered his question. I thought it was a good question -- how does darksend protect against a timing analysis? I think the answer is in making similar-sized payments (denomination of XX DRK) + using a time delay for batching multiple transactions together. A third party will see accounts being reduced and increased by similar sizes. For example 100 people will be losing 10 DRKs and 100 people will be gaining 10 DRKs. So you don't really know who sent to who. Right, but I can Darksend 7.289375 DRK to you, and I will get 2.710625 DRK change, and both of those amounts will be recorded in the blockchain. A timing analysis could trivially link the two addresses sending/receiving those two amounts that add to 10 DRK. Evan is the right person to analyze how DarkSend will deal with timing analysis. Personally I had proposed a slide bar that can be used to increase the anonymity level by increasing the laundry depth (number of masternodes the transaction goes through) or/and the time depth of the transaction. I also remember that it was discussed on how there'll be multiple denominating pools like 0.1/1/10/100 etc which would break down even the smaller amounts to similarly sized transactions. I'm not sure what's the current state of development is in terms of laundry depth, batching transactions delay etc. In an older post of mine I raised a similar issue that if timing analysis can be performed then it's just a matter of time before an alternate blockchain explorer is made that will script-analyze the official and simply provide the "clean" output with certain probabilities. Btw, I got an idea just now: It would be an interesting twist if one could send to two addresses instead of one, in a single transaction, with the sent amount being broken into two randomly sized parts. For example I send you 16 DRK and you get 5.4 DRK in one address and 10.6 DRK in another. You still got 16 but it's in two addresses so noone can corelate my 16 output and your receiving of ..5.4 and 10.6. If a further layer is added (for practical purposes) to treat these addresses as one (for the sender and receiver) it could also be quite easy to use. Kind of meta-addresses that overlap/include the sending/receiving addresses. |
|
|
|
It then compares the changes that occurred in those addresses in the last 2.5min [from its previous check] and knows exactly who transferred coins to whom.
Because it doesn't know who had them in the first place. It doesn't know if it's the same person sending to self. Darksend moves in blocks of fixed size and provides change back on new addresses. The blockchain keeps track of all of that anyway, why does a person have to be NSA? It's all in the blockchain... Why monitor? I don't get it. I think you just have a fundamental lack of understanding in how any crypto coin works. I'm not even sure where to start in trying to help you understand. Not an insult... You just don't have enough basic knowledge to have this conversation. That's kind of condescending. You could have just said, "an attacker can query the blockchain rather than constantly monitoring balances", and then answered his question. I thought it was a good question -- how does darksend protect against a timing analysis? I think the answer is in making similar-sized payments (denomination of XX DRK) + using a time delay for batching multiple transactions together. A third party will see accounts being reduced and increased by similar sizes. For example 100 people will be losing 10 DRKs and 100 people will be gaining 10 DRKs. So you don't really know who sent to who. |
|
|
|
|
Me thinks we need to issue a few bounties for hackers to test the possible attack vectors against masternode operation, cheating, payments etc, prior to going live (perhaps RC3+?). There's too much new stuff in there and code does have the annoying tendency to break, so... better harden it now than have nasty surprises later on.
|
|
|
|
There is no good reason why the private key needs to be stored on a masternode.
In an ideal setup, you would just broadcast a signed message "Authorizing 123.123.123.123 as masternode with input 1bcd1c22a3687e1ec1ea6ce61d3a43fae3581da9305d64fda298bbb66d1691ec expires 1398622305"
In this case 123.123.123.123 would be your masternode, but you don't need to have the private keys on that node. The signed message proves you are authorizing that IP to be the masternode for that input.
In this scenario you are proposing, would it be possible to spend the 1000 DRKs (located elsewhere) after the node initiates? |
|
|
|
The drk first 24 hours is a captive premine of 50% of all currently minted coins. They told you how fair it was because there was no premine.
I did not create FUD i told them the truth
No, you didn't. DRK is 0% premine. The 50% you are talking about is AFTER the launch, hence there is no PRE (prefix) before the mining commenced. Pre-mine = I have coins before the mining commences. Did that happen to DRK? No. What happened was low diff + late diff retargeting which led to a large number of high-reward blocks for the first 24 hours. Given the pre-ann (no ninja launch) whoever mined, got coins. The only "unfair" part is that those who mined later got far less coins. Given that you are currently in a PoW/PoS hybrid thread, where those who'll arrive later won't even have the chance to mine anything (unlike DRK where there are 18m of 22m coins to be mined - thus having a tremendously smaller early adopter advantage), you shouldn't throw rocks in a glass house. |
|
|
|
Still cheap, Dark is in the highs, Diamond lows.
Eeehhh?  A week ago DMD was 0.0002 now it is 0.001 (=5x) A week ago DRK was 0.0015 and now it's 0.0038 (=2.5x) DMD is twice as pumped as DRK. |
|
|
|
|
I was contemplating the financial effect of masternodes in terms of fractional inflation that Bitcoin might be subject to. Exchanges tend to be a parking place for a large number of coins which can lead to MtGox situations where the exchange is actually transacting with non-existing coins (something like fractional banking)... by transacting with non-existent coins, the demand is reduced for actual coins (=bad for price). The same might apply to payment processors where they can do away with cryptos if a client only cares abouf fiat.
The incentive to pull 1000s of DRKs into DarkSend nodes will significantly reduce the parked DRKs and the ability of third parties to make fractional practices with DRKs that they do not own, which is good for the price. At the same time, risk exposure to hacked exchanges that lose hundreds of thousands of coins will also be reduced as the coins parked will be less. However there is the individual risk of each running node to get hacked, so this needs to be very well thought out. 100 nodes running = 100k DRK bounty for hackers.
It'll be an interesting experiment for sure...
|
|
|
|
Somebody had, apparently, bought at 3xx levels and when the pumper put the 20 BTC walls in 400 (Mintpal) they unloaded on the pumper... 2014-04-27 10:15:30 SELL 0.00400000 4480.41552695 17.92166210 "...you shall not pass pump" |
|
|
|
|
Mini pump in progress from 330 to 410
|
|
|
|
|
Show Posts
