Dash isn't getting beat up by Monero as badly as poor little ShadowCash.
But give Shen a few days, I'm sure he'll have an even easier time de-anonymizing Dash's "bad crypto" than SDC's (which was at least based on ring signatures instead of Darksend's broken CoinJoin).
I don't see the "awful mess" you're talking about. All I see is huge volume and huge price increases, backed by a great dev team and community.
Is the guy also working on de-anomyzing darksent(d)s as well? |
|
|
|
|
Can someone link me what to do if I wish to send my coins from the exchange to a local wallet? (I asking this cause I've read about private key SYS1 and SYS2 or something like that)
|
|
|
|
hmmm ... anyone left from the team?
looks like no, it was all a part of the supernet scam. however the opal tech is miles ahead of some pos systems currently in place so i guess there's still some value left. i wanted to start minor development updates, but my knowledge is not that deep Supernet scam? What do you mean? |
|
|
|
Is there any risk in using a VPN of the bitnet network (e.g. intercepting the traffic and stuff like tha)?
Use this when you use VPN of the bitnet network. I already use this extension to prevent MITMs. So besides this kind of attack there's no other attack vector? Does my traffic get encrypted before passing through the VPN? I have (almost)no problems in trusting major VPN providers such as cyberghost, vpnvanish, excetera, but I feel a bit concerned in connecting through an unknown VPN with a chance of that being a malicious node. That's why I would like to be 100% sure that there's no way for my sensitive datas to be intercepted. Thank you for the response. |
|
|
|
|
Is there any risk in using a VPN of the bitnet network (e.g. intercepting the traffic and stuff like tha)?
|
|
|
|
|
Such an interesting coin, is still this being part of Supernet?
|
|
|
|
The resolution of the bitcoin experimentDespite the news blockade, within a few days of launching Bitcoin XT around 15% of all network nodes were running it, and at least one mining pool had started offering BIP101 voting to miners.
That’s when the denial of service attacks started. The attacks were so large that they disconnected entire regions from the internet:
“I was DDos’d. It was a massive DDoS that took down my entire (rural) ISP. Everyone in five towns lost their internet service for several hours last summer because of these criminals. It definitely discouraged me from hosting nodes.”
In other cases, entire datacenters were disconnected from the internet until the single XT node inside them was stopped. About a third of the nodes were attacked and removed from the internet in this way.
Worse, the mining pool that had been offering BIP101 was also attacked and forced to stop. The message was clear: anyone who supported bigger blocks, or even allowed other people to vote for them, would be assaulted.
The attackers are still out there. When Coinbase, months after the launch, announced they had finally lost patience with Core and would run XT, they too were forced offline for a while. I was wondering how masternodes will handle with ddos attacks? Is anything being done/thinked of to handle this possible issue? I don't know if I'm right here, but I'm going to guess that they attacked his known node, the miner and coinbase, who supported XT. Which is kind of limited. Still, everyone online is subject to ddos attacks, and there isn't much one can do about it. One thing, though, Masternode IP addresses are no longer published, and I believe we will learn to obfuscate our ip addresses in other ways in the future. I mean, ddos attacks are an issue for everyone, but I would think with a world wide network, we should be OK. But if we're processing tons of transactions, like Visa, a ddos attack could seriously slow down the processing of transactions. Thank you for the reply, however, why are you saying that MNs' IP addresses are no longer visible? I know that for now the command dash-cli masternode list gives you the vin addresses, but https://dashninja.pl/ still shows all the IPs. |
|
|
|
The resolution of the bitcoin experimentDespite the news blockade, within a few days of launching Bitcoin XT around 15% of all network nodes were running it, and at least one mining pool had started offering BIP101 voting to miners.
That’s when the denial of service attacks started. The attacks were so large that they disconnected entire regions from the internet:
“I was DDos’d. It was a massive DDoS that took down my entire (rural) ISP. Everyone in five towns lost their internet service for several hours last summer because of these criminals. It definitely discouraged me from hosting nodes.”
In other cases, entire datacenters were disconnected from the internet until the single XT node inside them was stopped. About a third of the nodes were attacked and removed from the internet in this way.
Worse, the mining pool that had been offering BIP101 was also attacked and forced to stop. The message was clear: anyone who supported bigger blocks, or even allowed other people to vote for them, would be assaulted.
The attackers are still out there. When Coinbase, months after the launch, announced they had finally lost patience with Core and would run XT, they too were forced offline for a while. I was wondering how masternodes will handle with ddos attacks? Is anything being done/thinked of to handle this possible issue?
|
|
|
|
|
What's going on with the price? Any recent leak/news?
|
|
|
|
|
Hey guys where the MN incomes of the MN owners who do not vote/never voted flow ?
|
|
|
|
|
Oh man been MIA for a long time and they are still talking about centralized MNs, centralized spork, etc, lol.
|
|
|
|
Fascinating. I wonder will the nodes crash... Hey there what's going on? I've been MIA for a while! |
|
|
|
|
Hello guys is the encrypted voice actually working?
|
|
|
|
|
Excuse me gentlemen, I am getting some issue with the wallet.
I added Cloakcoin.conf with the new nodes and I am able to connect to the network, but after some minute of downloading the blockchain the downloading bar disappears and I get instead a black bar saying: Warning checkpoint is too old, wait for blockchain to download or notify developers[/i]
|
|
|
|
|
Last Active: June 10, 2015, 08:53:58 PM
|
|
|
|
I actually meant you and Devplus. The person I talked to said, your team has no skills to develop such things and you could not deliver it. Another thing he said was the Munne team is not even capable of giving an interview due to lack of English skills, too. I do not mean to insult, but this is what has been told, and seems like it is true looking at the post above...
Actually this was already known long ago, Bassguitarman leaked it some month ago. They are not able to code whatsover that's why they hire people on their side. |
|
|
|
|
Btw only 8% of the total number of MNs are hosted on Amazon.
|
|
|
|
I'm a little concerned that the entire MN network can reach 80%+ compliance with a protocol bump within 48 hours, but that 96 hours after an MN vote is initialized, we still have less than 50% participation...and the voting process is not that difficult (log into VPS, type "./dashd masternode vote yea" and log off VPS).
What are we voting for? Should I update the client? I've been MIA for a while. |
|
|
|
|
Back to 1M$ market cap, what's going on Storj?
|
|
|
|
|
Hey Syntax are you an EXCL dev now?
Cheers
|
|
|
|
|
Show Posts
