Top 3 Crypto Mining Botnets: Smominru, DDG, and ADB.Miner ...

Proven security!

Want to bitch about Oracle/MS/Adobe's recent exploit even though it's been on the front page for 5 days? Tired of sanitybit's "moderation" and "civility"? Join the circlejerk! Don't get me wrong, I love netsec, it's just some... issues occasionally crop up.
[link]

August / September monthly report from v1docq47 (CCS + XRM.RU)

This is my monthly progress report (CCS.html) + XMR.RU).
Below is a list of what has been done and translated into Russian for two months of my work.

Monero Video (YouTube)

The following video posted on Monero Russian Community YouTube Channel.

Weekly News:

Short Q&A about Monero:

Monero into Russian (Translation)

The following articles / guides have been translated into Russian and posted on the XMR.RU website and my Github repository.
Note: If you would like to read the original article in English, then, open the article you are interested in, and at the end of each article you will find a link to the source.

Critical Decentralisation Cluster 36c3 (transcriptions (EN + RU) + translation (RU)):

01 - Monero Introduction (Diego "rehrar" Salazar) | Transcriptions - EN.md) / RU.md) / XMR.RU 02 - RIAT Introduction (parasew) | Transcriptions - EN.md) / RU.md) / XMR.RU 03 - Swiss Cryptoeconomics Assembly (polto, Ome) | Transcriptions - EN.md) / RU.md) / XMR.RU 04 - Namecoin Introduction (Jeremy Rand) | Transcriptions - EN.md) / RU.md) / XMR.RU 05 - Open Hardware developed at FOSSASIA (Mario Behling) | Transcriptions - EN.md) / RU.md) / XMR.RU 06 - Paralelni Polis (Juraj Bednar) | Transcriptions - EN.md) / RU.md) / XMR.RU 07 - Introduction to Replicant (dllud, Denis ‘GNUtoo’ Carikli)​ | Transcriptions - EN.md) / RU.md) / XMR.RU 08 - Open Source Hardware and OSHWA (Drew Fustini) | Transcriptions - EN.md) / RU.md) / XMR.RU 09 - ImplicitCAD (Juila Longtin) | Transcriptions - EN.md) / RU.md) / XMR.RU 10 - Program in Detail | Transcriptions - EN / RU / XMR.RU 11 - about:freedom (Bonnie Mehring, Blipp)​ | Transcriptions - EN.md) / RU.md) / XMR.RU 13 - Funding Models of FOSS (Diego “rehrar” Salazar) | Transcriptions - EN.md) / RU.md) / XMR.RU 14 - The Sharp Forks We Follow​ | Transcriptions - EN / RU / XMR.RU 16 - P2P Trading in Cryptoanarchy | Transcriptions - EN / RU / XMR.RU 17 - Monero’s Adaptive Blockweight Approach to Scaling | Transcriptions - EN / RU / XMR.RU 18 - Nym (Harry Halpin)​ | Transcriptions - EN.md) / RU.md) / XMR.RU 19 - Digital Integrity of the Human Person | Transcriptions - EN / RU / XMR.RU 20 - cyber~Congress (Sergey Simanovsky) | Transcriptions - EN.md) / RU.md) / XMR.RU 21 - KYC & Crypto-AML Tools (polto) | Transcriptions - EN.md) / RU.md) / XMR.RU 22 - Parallel Polis, Temporary Autonomous Zones and Beyond | Transcriptions - EN / RU 23 - MandelBot:HAB - Open Source Ecotecture and Horizontalism | Transcriptions - EN / RU 24 - Adventures and Experiments Adding Namecoin to Tor Browser | Transcriptions - EN / RU 25 - Fair Data Society (Gregor Zavcer) | Transcriptions - EN.md) / RU.md) / XMR.RU 45 - Designing a Communal Computing Interface | Transcriptions - EN / RU / XMR.RU 47 - Hackatoshi’s Flying Circuit | Transcriptions - EN / RU / XMR.RU

Zero to Monero - Second Edition

https://www.overleaf.com/read/hcmqnvgtfmyh - Chapter 00 - Abstract - Chapter 01 - Introduction - Chapter 02 - Basic Concepts - Chapter 03 - Advanced Schnorr-like Signatures

Monero Outreach Articles

Getmonero.org Posts Blog

LocalMonero Articles

Note: You need "Change Language" to Russian - Why Monero Has A Tail Emission - How CLSAG Will Improve Monero's Efficiency - How Monero Solved the Block Size Problem That Plagues Bitcoin - How Ring Signatures Obscure Monero's Outputs - Monero Best Practices for Beginners - Monero Outputs Explained

Monero Meeting logs

CCS Result / Report

Monero News

Other Articles

Pull / Merge Request

Monero Project Translations (Weblate)

Thanks for your support!
submitted by v1docq47 to Monero [link] [comments]

For the newcomers

I haven't seen this posted in a while. If you've never read this post, you really should.
Edit: Screwed up the formatting. See other comments.

People should get the full story of bitcoin because it is probably one of the strangest of all reddit subs.
bitcoin, the main sub for the bitcoin community is held and run by a person who goes by the pseudonym u/theymos. Theymos not only controls bitcoin, but also bitcoin.org and bitcointalk.com. These are top three communication channels for the bitcoin community, all controlled by just one person.
For most of bitcoin's history this did not create a problem (at least not an obvious one anyway) until around mid 2015. This happened to be around the time a new player appeared on the scene, a for-profit company called Blockstream. Blockstream was made up of/hired many (but not all) of the main bitcoin developers. (To be clear, Blockstream was founded before mid 2015 but did not become publicly active until then). A lot of people, including myself, tried to point out there we're some very serious potential conflicts of interest that could arise when one single company controls most of the main developers for the biggest decentralised and distributed cryptocurrency. There were a lot of unknowns but people seemed to give them the benefit of the doubt because they were apparently about to release some new software called "sidechains" that could offer some benefits to the network.
Not long after Blockstream came on the scene the issue of bitcoin's scalability once again came to forefront of the community. This issue came within the community a number of times since bitcoins inception. Bitcoin, as dictated in the code, cannot handle any more than around 3 transactions per second at the moment. To put that in perspective Paypal handles around 15 transactions per second on average and VISA handles something like 2000 transactions per second. The discussion in the community has been around how best to allow bitcoin to scale to allow a higher number of transactions in a given amount of time. I suggest that if anyone is interested in learning more about this problem from a technical angle, they go to btc and do a search. It's a complex issue but for many who have followed bitcoin for many years, the possible solutions seem relatively obvious. Essentially, currently the limit is put in place in just a few lines of code. This was not originally present when bitcoin was first released. It was in fact put in place afterwards as a measure to stop a bloating attack on the network. Because all bitcoin transactions have to be stored forever on the bitcoin network, someone could theoretically simply transmit a large number of transactions which would have to be stored by the entire network forever. When bitcoin was released, transactions were actually for free as the only people running the network were enthusiasts. In fact a single bitcoin did not even have any specific value so it would be impossible set a fee value. This meant that a malicious person could make the size of the bitcoin ledger grow very rapidly without much/any cost which would stop people from wanting to join the network due to the resource requirements needed to store it, which at the time would have been for very little gain.
Towards the end of the summer last year, this bitcoin scaling debate surfaced again as it was becoming clear that the transaction limit for bitcoin was semi regularly being reached and that it would not be long until it would be regularly hit and the network would become congested. This was a very serious issue for a currency. Bitcoin had made progress over the years to the point of retailers starting to offer it as a payment option. Bitcoin companies like, Microsoft, Paypal, Steam and many more had began to adopt it. If the transaction limit would be constantly maxed out, the network would become unreliable and slow for users. Users and businesses would not be able to make a reliable estimate when their transaction would be confirmed by the network.
Users, developers and businesses (which at the time was pretty much the only real bitcoin subreddit) started to discuss how we should solve the problem bitcoin. There was significant support from the users and businesses behind a simple solution put forward by the developer Gavin Andreesen. Gavin was the lead developer after Satoshi Nakamoto left bitcoin and he left it in his hands. Gavin initially proposed a very simple solution of increasing the limit which was to change the few lines of code to increase the maximum number of transactions that are allowed. For most of bitcoin's history the transaction limit had been set far far higher than the number of transactions that could potentially happen on the network. The concept of increasing the limit one time was based on the fact that history had proven that no issue had been cause by this in the past.
A certain group of bitcoin developers decided that increasing the limit by this amount was too much and that it was dangerous. They said that the increased use of resources that the network would use would create centralisation pressures which could destroy the network. The theory was that a miner of the network with more resources could publish many more transactions than a competing small miner could handle and therefore the network would tend towards few large miners rather than many small miners. The group of developers who supported this theory were all developers who worked for the company Blockstream. The argument from people in support of increasing the transaction capacity by this amount was that there are always inherent centralisation pressure with bitcoin mining. For example miners who can access the cheapest electricity will tend to succeed and that bigger miners will be able to find this cheaper electricity easier. Miners who have access to the most efficient computer chips will tend to succeed and that larger miners are more likely to be able to afford the development of them. The argument from Gavin and other who supported increasing the transaction capacity by this method are essentially there are economies of scale in mining and that these economies have far bigger centralisation pressures than increased resource cost for a larger number of transactions (up to the new limit proposed). For example, at the time the total size of the blockchain was around 50GB. Even for the cost of a 500GB SSD is only $150 and would last a number of years. This is in-comparison to the $100,000's in revenue per day a miner would be making.
Various developers put forth various other proposals, including Gavin Andresen who put forth a more conservative increase that would then continue to increase over time inline with technological improvements. Some of the employees of blockstream also put forth some proposals, but all were so conservative, it would take bitcoin many decades before it could reach a scale of VISA. Even though there was significant support from the community behind Gavin's simple proposal of increasing the limit it was becoming clear certain members of the bitcoin community who were part of Blockstream were starting to become increasingly vitriolic and divisive. Gavin then teamed up with one of the other main bitcoin developers Mike Hearn and released a coded (i.e. working) version of the bitcoin software that would only activate if it was supported by a significant majority of the network. What happened next was where things really started to get weird.
After this free and open source software was released, Theymos, the person who controls all the main communication channels for the bitcoin community implemented a new moderation policy that disallowed any discussion of this new software. Specifically, if people were to discuss this software, their comments would be deleted and ultimately they would be banned temporarily or permanently. This caused chaos within the community as there was very clear support for this software at the time and it seemed our best hope for finally solving the problem and moving on. Instead a censorship campaign was started. At first it 'all' they were doing was banning and removing discussions but after a while it turned into actively manipulating the discussion. For example, if a thread was created where there was positive sentiment for increasing the transaction capacity or being negative about the moderation policies or negative about the actions of certain bitcoin developers, the mods of bitcoin would selectively change the sorting order of threads to 'controversial' so that the most support opinions would be sorted to the bottom of the thread and the most vitriolic would be sorted to the top of the thread. This was initially very transparent as it was possible to see that the most downvoted comments were at the top and some of the most upvoted were at the bottom. So they then implemented hiding the voting scores next to the users name. This made impossible to work out the sentiment of the community and when combined with selectively setting the sorting order to controversial it was possible control what information users were seeing. Also, due to the very very large number of removed comments and users it was becoming obvious the scale of censorship going on. To hide this they implemented code in their CSS for the sub that completely hid comments that they had removed so that the censorship itself was hidden. Anyone in support of scaling bitcoin were removed from the main communication channels. Theymos even proudly announced that he didn't care if he had to remove 90% of the users. He also later acknowledged that he knew he had the ability to block support of this software using the control he had over the communication channels.
While this was all going on, Blockstream and it's employees started lobbying the community by paying for conferences about scaling bitcoin, but with the very very strange rule that no decisions could be made and no complete solutions could be proposed. These conferences were likely strategically (and successfully) created to stunt support for the scaling software Gavin and Mike had released by forcing the community to take a "lets wait and see what comes from the conferences" kind of approach. Since no final solutions were allowed at these conferences, they only served to hinder and splinter the communities efforts to find a solution. As the software Gavin and Mike released called BitcoinXT gained support it started to be attacked. Users of the software were attack by DDOS. Employees of Blockstream were recommending attacks against the software, such as faking support for it, to only then drop support at the last moment to put the network in disarray. Blockstream employees were also publicly talking about suing Gavin and Mike from various different angles simply for releasing this open source software that no one was forced to run. In the end Mike Hearn decided to leave due to the way many members of the bitcoin community had treated him. This was due to the massive disinformation campaign against him on bitcoin. One of the many tactics that are used against anyone who does not support Blockstream and the bitcoin developers who work for them is that you will be targeted in a smear campaign. This has happened to a number of individuals and companies who showed support for scaling bitcoin. Theymos has threatened companies that he will ban any discussion of them on the communication channels he controls (i.e. all the main ones) for simply running software that he disagrees with (i.e. any software that scales bitcoin).
As time passed, more and more proposals were offered, all against the backdrop of ever increasing censorship in the main bitcoin communication channels. It finally come down the smallest and most conservative solution. This solution was much smaller than even the employees of Blockstream had proposed months earlier. As usual there was enormous attacks from all sides and the most vocal opponents were the employees of Blockstream. These attacks still are ongoing today. As this software started to gain support, Blockstream organised more meetings, especially with the biggest bitcoin miners and made a pact with them. They promised that they would release code that would offer an on-chain scaling solution hardfork within about 4 months, but if the miners wanted this they would have to commit to running their software and only their software. The miners agreed and the ended up not running the most conservative proposal possible. This was in February last year. There is no hardfork proposal in sight from the people who agreed to this pact and bitcoin is still stuck with the exact same transaction limit it has had since the limit was put in place about 6 years ago. Gavin has also been publicly smeared by the developers at Blockstream and a plot was made against him to have him removed from the development team. Gavin has now been, for all intents an purposes, expelled from bitcoin development. This has meant that all control of bitcoin development is in the hands of the developers working at Blockstream.
There is a new proposal that offers a market based approach to scaling bitcoin. This essentially lets the market decide. Of course, as usual there has been attacks against it, and verbal attacks from the employees of Blockstream. This has the biggest chance of gaining wide support and solving the problem for good.
To give you an idea of Blockstream; It has hired most of the main and active bitcoin developers and is now synonymous with the "Core" bitcoin development team. They AFAIK no products at all. They have received around $75m in funding. Every single thing they do is supported by theymos. They have started implementing an entirely new economic system for bitcoin against the will of it's users and have blocked any and all attempts to scaling the network in line with the original vision.
Although this comment is ridiculously long, it really only covers the tip of the iceberg. You could write a book on the last two years of bitcoin. The things that have been going on have been mind blowing. One last thing that I think is worth talking about is the u/bashco's claim of vote manipulation.
The users that the video talks about have very very large numbers of downvotes mostly due to them having a very very high chance of being astroturfers. Around about the same time last year when Blockstream came active on the scene every single bitcoin troll disappeared, and I mean literally every single one. In the years before that there were a large number of active anti-bitcoin trolls. They even have an active sub buttcoin. Up until last year you could go down to the bottom of pretty much any thread in bitcoin and see many of the usual trolls who were heavily downvoted for saying something along the lines of "bitcoin is shit", "You guys and your tulips" etc. But suddenly last year they all disappeared. Instead a new type of bitcoin user appeared. Someone who said they were fully in support of bitcoin but they just so happened to support every single thing Blockstream and its employees said and did. They had the exact same tone as the trolls who had disappeared. Their way to talking to people was aggressive, they'd call people names, they had a relatively poor understanding of how bitcoin fundamentally worked. They were extremely argumentative. These users are the majority of the list of that video. When the 10's of thousands of users were censored and expelled from bitcoin they ended up congregating in btc. The strange thing was that the users listed in that video also moved over to btc and spend all day everyday posting troll-like comments and misinformation. Naturally they get heavily downvoted by the real users in btc. They spend their time constantly causing as much drama as possible. At every opportunity they scream about "censorship" in btc while they are happy about the censorship in bitcoin. These people are astroturfers. What someone somewhere worked out, is that all you have to do to take down a community is say that you are on their side. It is an astoundingly effective form of psychological attack.
submitted by CuriousTitmouse to btc [link] [comments]

IMPORTANT NOTICE.

Hi everyone
We are Group of Young Rusian and australian Hackers, we will share with you all what we have and learn earlier .
BUY BANK LOGINS, CVV FULLZ, DUMPS, 101 & 201, TRANSFERS, TUTORIALS, SPAM TOOLS, RDP, VPN, BOTNETS, SCAM PAGES
Contact for help: [[email protected]](mailto:[email protected]) ICQ: 721808635
Buy Hacked PayPal, Bank Logins, WesternUnion, cc top up, cvv, smtp, RDP, inbox mailer, email leads, dumps, wares, with proofs of transactions and accounts.
I am selling hacked western union, hacked PayPal accounts, bank logins, MoneyBookers, CC details/transfer, Hacked iTunes Accounts, Dumps, wares and fullz infos. I have many customers and buyers all over the world and they trust me and i promised to never break this chain till DEATH
I'm offering many offers to earn online money through sources like western union transfers, bank transfers, moneybookers and PayPal transfers through offshore database.
All transactions are offshore and anonymous and has no trace backs or chargebacks
Come with us and enjoy the best products to make money , how to shop online ,buy your stuff freely and make much tax free Cash
Our online support only to serious customers
Country for sale : USA, UK, CA, AU, EU and more.
Credit Card All Countries
Western Union Money Transfers
Card Dumps, Track 1+2 (with pin)
Hacking Bank Login ,paypal world wide(bank transfers)
Payment methods: Bitcoin, Perfect Money, Web Money Hopefully we can find a good customer to do business together long term You will feel happy, confident and safe to work with us, that's for sure PRIX MSR:
MSR505 / MSR2000: 549 $ MSR505 / MSR300 *: 499 $ MSR505 / TA-48: 639 $ MSR206 / MSR3000: 729 $ MSR206 / MSR300: 549 $ MSR206 2× MSR400: 900 $ MSR206 2× MSR500m (Mini123): 875 $ MSR206 2× TA-32: 990 $ MSR206 2× CRM42: 869 $ MSR206 2×CRM41: 929 $
Western Union Transfer Rates
$1000 Transfer = $100 Charge $3000 Transfer = $250 $4500 Transfer = $350 $7000 Transfer $500
Bank Transfers :-
This is my responsibility is to transfer the required amount into your account from an offshore server, you have no trace back or charge backs, but it is your responsibility to handle the bankers and get safe your side. i will use my personal method for making clear payment so no dispute no charge back chances. (transferring all over the world)
Info needed for Bank transfers :
1: Bank name 2: Bank address 3: Zip code 4: Account Holder 5: Account number 6: Account Type 7: Routing number 8: Swift number 9: BIC and IBAN
Bank transfer will take maximum 6hours to show money in your bank account.
Bank Transfer Rates: $1000 transfer = $100 Charges $3000 Transfer = $250 Charges $5000 Transfer = $400 Charges $10,000 Transfer = $800 Charges $15,000 Transfer = $1200 Charges
MoneyBookers Transfer :- Offering moneybookers/skrill transfer worldwide. It is a instant payment/transfer. I’m using an offshore server to transfer moneybookers so there is no chargeback and negative feedback. (transferring all over the world)
Money Bookers Transfer Rates : $1800 Transfer = $150 Charges � $3000 Transfer = $250 Charges $5000 Transfer = $400 Charges $9000 Transfer = $700 Charges � $15000 Transfer = $1200 Charges
Paypal Transfer :- Paypal Transfer Rates: $1800 Transfer = $150 Charges $3000 Transfer = $250 Charges $5000 Transfer = $400 Charges $9000 Transfer = $700 Charges $15,000 Transfer = $1200 Charges
CreditCard TopUP Rates:- $1800 transfer = $150 Charges $3000 Transfer = $250 Charges $5000 Transfer = $400 Charges $10,000 Transfer = $800 Charges $15,000 Transfer = $1200 Charges
***Also selling RDP, SMTP SERVERS, WEBMAIL, MAILERS, BULK MAILS (US/UK based) DATING ACCOUNTS, cPanel HOSTING, Hacked Panels, CC dumps.
Thanks All. Contact: [[email protected]](mailto:[email protected])
submitted by Ezraunion234 to u/Ezraunion234 [link] [comments]

Intrusion Alerts to actual IP even when connected to VPN

So I've been a NordVPN customer since July of '17 and have experienced what I consider the best protection, confidence in anonymity, as well as ease of use. That said, there's a lot I don't understand. The reason for this post is because I'm being alerted of some ip addresses known for bad behavior, being blocked by my router. I'm getting A LOT of alerts and I don't know if it's normal or not. The curious thing is that the in the alert the DESTINATION is my public IP address from my provider.
Basically, someone's knocking on the doors of my real public IP address and I need to assess the threat. How can that be when I have NordVPN and my real IP address is supposed to be blocked?
Details on the intrusion, if it matters: Asus Router AC-3200
The Two-Way Intrusion Prevention System protects any device connected to the network from spam or DDoS attacks. It also blocks malicious incoming packets to protect your router from network vulnerability attacks, such as Shellshocked, Heartbleed, Bitcoin mining, and ransomware. Additionally, Two-Way IPS detects suspicious outgoing packets from infected devices and avoids botnet attacks.
The Exploits Blocked:
Exploit netcore router backdoor access
Exploit Remote Command Execution via shell script -2
submitted by Thilky to nordvpn [link] [comments]

Master list of evidence regarding Bitcoin's hijacking and takeover by Blockstream

https://archive.is/TkUus
https://www.reddit.com/btc/comments/7mg4tm/updated_dec_2017_a_collection_of_evidence
https://hackernoon.com/the-great-bitcoin-scaling-debate-a-timeline-6108081dbada
https://twitter.com/adam3us/status/633119949943275520
https://www.reddit.com/Bitcoin/comments/3hb63g/bip_suggestion_lock_the_blockchain_to_only/cu5v2u2/
https://www.reddit.com/Bitcoin/comments/3h9cq4/its_time_for_a_break_about_the_recent_mess/
https://www.reddit.com/Bitcoin/comments/3uu3we/bitstamp_will_switch_to_bip_101_this_decembe
https://www.reddit.com/Bitcoin/comments/3uu3we/bitstamp_will_switch_to_bip_101_this_decembecxi370c/
https://www.reddit.com/Bitcoin/comments/3rejl9/coinbase_ceo_brian_armstrong_bip_101_is_the_best/cwpglh6
https://www.reddit.com/Bitcoin/comments/3axnc3/this_is_the_definition_of_fud_how_to_subvert/
https://www.reddit.com/btc/comments/3z0pkq/theymos_caught_redhanded_why_he_censors_all_the/
http://pastebin.com/1kvuj5bw
https://www.reddit.com/btc/comments/418r0l/lukejr_is_already_trying_to_sabotage_bitcoin/
https://medium.com/@octskyward/the-resolution-of-the-bitcoin-experiment-dabb30201f7#.cjuafsypy
https://www.reddit.com/Bitcoin/comments/3axnc3/this_is_the_definition_of_fud_how_to_subvert/
https://medium.com/@bitcoinroundtable/bitcoin-roundtable-consensus-266d475a61ff#.g42rjs2ew
https://news.bitcoin.com/bitcoin-classic-targeted-by-ddos-attacks/
https://www.reddit.com/btc/comments/5h2wiv/was_theymos_running_a_botnet_in_2007_theymos/?
https://www.reddit.com/btc/comments/5fm11b/unullc_is_actively_trying_to_delete_satoshi_from/?
https://github.com/BitcoinUnlimited/BitcoinUnlimited/pull/180#discussion_r91823463
submitted by jessquit to btc [link] [comments]

Why is the RandomX algorithm being hyped to the moon?

TL;DR: don't assume the average return from mining RandomX will be higher than the current CryptonightR algorithm. Hold back your excitement for now.
I think we all need to bring something to our attention. Over the last month, there have been so many topics and comments here on MoneroMining about the new 'RandomX' algorithm. This algorithm is supposed to be launched a couple of months from now.
There are many questions like "is this a good hashrate for my CPU"? "What's your power usage on RandomX"? "How can I tune my CPU for RandomX"? "How would the algorithm perform on this hardware"? I think these are great constructive comments that are at the heart of what miners stand for. We miners love optimizing our rigs and educating ourselves on technological trends.
But I've noticed many questions such as "what parts should I buy for a RandomX mining rig"? "Is an AMD Ryzen 9 3900x a good investment"? "What parts will give me the most profit when RandomX launches"? Many of these questions are asked with very little research.
I think there's a gold fever brewing behind some of these comments. The kind of motives that have bankrupted many miners in the past bubbles.
As we have seen in 2014 and 2018, anybody who enters the crypto industry with an 'I want easy profit' attitude almost always goes bankrupt. They buy coins or hardware at the peak of the bubble. Sometimes they get lucky and sell their coins or rigs right before the crash (only to get burned in a future bubble later). But most of the time, these new users lose most of their investment.
As a veteran miner, a lot of alarm bells ring in my head when I read these kinds of RandomX hype posts.
I have no reason to think CPU mining will be more profitable on RandomX than on the current CryptonightR.
In the GPU mining community, I have the feeling that there's a lot of resentment over the 2018 crypto recession and the whole 'ASIC miner invasion'. I think people here are feeling burned over their losses last year and the evil ASIC takeover, and want an opportunity for the little guy to start mining again. So we're falsely seeing the RandomX ray of hope as a floodlight, and getting overexcited.
And in general, the ordinary person cannot make a significant, steady profit in the crypto mining industry. The guy who wrote that thread is very rich and even 100 GTX 1080 Ti's cost nothing to him. The reason he became wealthy is because he avoided get-rich-quick gimmicks back in the day (like the dotcom sites) and focused on learning technology for the future. Mining will not make you rich, and especially not RandomX coin tossing.
If you love RandomX, build your rig now, keep benchmarking and undervolting and have fun at it. But if you just want profit, wait until RandomX is up and running. And consider all the risks involved with a new algorithm and commercial mining in general.
So I hope we can all reconsider whether we're excited about RandomX for the right reasons. Let's try to avoid jumping to conclusions about profitability and hold off on the Newegg 'checkout' button. Even though 12 cores at 70 watts sounds awesome. Happy mining!
submitted by Hammereditor to MoneroMining [link] [comments]

AMA: Ask Mike Anything

Hello again. It's been a while.
People have been emailing me about once a week or so for the last year to ask if I'm coming back to Bitcoin now that Bitcoin Cash exists. And a couple of weeks ago I was summoned on a thread called "Ask Mike Hearn Anything", but that was nothing to do with me and I was on holiday in Japan at the time. So I figured I should just answer all the different questions and answers in one place rather than keep doing it individually over email.
Firstly, thanks for the kind words on this sub. I don't take part anymore but I still visit occasionally to see what people are talking about, and the people posting nice messages is a pleasant change from three years ago.
Secondly, who am I? Some new Bitcoiners might not know.
I am Satoshi.
Just kidding. I'm not Satoshi. I was a Bitcoin developer for about five years, from 2010-2015. I was also one of the first Bitcoin users, sending my first coins in April 2009 (to SN), about 4 months after the genesis block. I worked on various things:
You can see a trend here - I was always interested in developing peer to peer decentralised applications that used Bitcoin.
But what I'm best known for is my role in the block size debate/civil war, documented by Nathaniel Popper in the New York Times. I spent most of 2015 writing extensively about why various proposals from the small-block/Blockstream faction weren't going to work (e.g. on replace by fee, lightning network, what would occur if no hard fork happened, soft forks, scaling conferences etc). After Blockstream successfully took over Bitcoin Core and expelled anyone who opposed them, Gavin and I forked Bitcoin Core to create Bitcoin XT, the first alternative node implementation to gain any serious usage. The creation of XT led to the imposition of censorship across all Bitcoin discussion forums and news outlets, resulted in the creation of this sub, and Core supporters paid a botnet operator to force XT nodes offline with DDoS attacks. They also convinced the miners and wider community to do nothing for years, resulting in the eventual overload of the main network.
I left the project at the start of 2016, documenting my reasons and what I expected to happen in my final essay on Bitcoin in which I said I considered it a failed experiment. Along with the article in the New York Times this pierced the censorship, made the wider world aware of what was going on, and thus my last gift to the community was a 20% drop in price (it soon recovered).

The last two years

Left Bitcoin ... but not decentralisation. After all that went down I started a new project called Corda. You can think of Corda as Bitcoin++, but modified for industrial use cases where a decentralised p2p database is more immediately useful than a new coin.
Corda incorporates many ideas I had back when I was working on Bitcoin but couldn't implement due to lack of time, resources, because of ideological wars or because they were too technically radical for the community. So even though it's doesn't provide a new cryptocurrency out of the box, it might be interesting for the Bitcoin Cash community to study anyway. By resigning myself to Bitcoin's fate and joining R3 I could go back to the drawing board and design with a lot more freedom, creating something inspired by Bitcoin's protocol but incorporating all the experience we gained writing Bitcoin apps over the years.
The most common question I'm asked is whether I'd come back and work on Bitcoin again. The obvious followup question is - come back and work on what? If you want to see some of the ideas I'd have been exploring if things had worked out differently, go read the Corda tech white paper. Here's a few of the things it might be worth asking about:
I don't plan on returning to Bitcoin but if you'd like to know what sort of things I'd have been researching or doing, ask about these things.
edit: Richard pointed out some essays he wrote that might be useful, Enterprise blockchains for cryptocurrency experts and New to Corda? Start here!
submitted by mike_hearn to btc [link] [comments]

A few stories about Brian Krebs: The independent cybercrime journalist who exposes criminals on the internet

First, a bit of introduction before we get into the living drama that is Brian Krebs.
Brian Krebs has been a journalist for decades, starting in the late 90s. He got his start at The Washington Post, but what he's most famous for are his exposes on criminal businesses and individuals who perpetuate cyber crime worldwide. In 2001, he got his interest in cybercrime piqued when a computer worm locked him out of his own computer. In 2005, he shifted from working as a staff writer at The Washington Post's tech newswire to writing for their security blog, "Security Wire". During his tenure there, he started by focusing on the victims of cybercrime, but later also started to focus on the perpetrators of it as well. His reporting helped lead to the shutdown of McColo, a hosting provider who provided service to some of the world's biggest spammers and hackers. Reports analyzing the shutdown of McColo estimated that global spam volume dropped by between 40 and 70 percent. Further analysis revealed it also played host to child pornography sites, and the Russian Business Network, a major Russian cybercrime ring.
In 2009, Krebs left to start his own site, KrebsOnSecurity. Since then, he's been credited with being the first to report on major events such as Stuxnet and when Target was breached, resulting in the leakage of 40 million cards. He also regularly investigates and reveals criminals' identities on his site. The latter has made him the bane of the world of cybercrime, as well as basically a meme, where criminals will include references like Made by Brian Krebs in their code, or name their shops full of stolen credit cards after him.
One of his first posts on his new site was a selection of his best work. While not particularly dramatic, they serve as an excellent example of dogged investigative work, and his series reveal the trail of takedowns his work has documented, or even contributed to.
And now, a selection of drama involving Krebs. Note, all posts are sarcastically-tinged retellings of the source material which I will link throughout. I also didn't use the real names in my retellings, but they are in the source material. This took way too long to write, and it still does massively condense the events described in the series. Krebs has been involved with feuds with other figures, but I'd argue these tales are the "main" bits of drama that are most suited for here.

Fly on the Wall

By 2013, Krebs was no stranger to cybercriminals taking the fight to the real world. He was swatted previously to the point where the police actually know to give him a ring and see if there'd actually been a murder, or if it was just those wacky hackers at it again. In addition, his identity was basically common knowledge to cybercriminals, who would open lines of credit in his name, or find ways to send him money using stolen credit cards.
However, one particular campaign against him caught his eye. A hacker known as "Fly" aka "Flycracker" aka "MUXACC1" posted on a Russian-language fraud forum he administered about a "Krebs fund". His plan was simple. Raise Bitcoin to buy Heroin off of a darknet marketplace, address it to Krebs, and alert his local police via a spoofed phone call. Now, because Krebs is an investigative journalist, he develops undercover presences on cybercrime forums, and it just so happened he'd built up a presence on this one already.
Guys, it became known recently that Brian Krebs is a heroin addict and he desperately needs the smack, so we have started the "Helping Brian Fund", and shortly we will create a bitcoin wallet called "Drugs for Krebs" which we will use to buy him the purest heroin on the Silk Road. My friends, his withdrawal is very bad, let’s join forces to help the guy! We will save Brian from the acute heroin withdrawal and the world will get slightly better!
Fly had first caught Krebs' attention by taunting him on Twitter, sending him Tweets including insults and abuse, and totally-legit looking links. Probably either laced with malware, or designed to get Krebs' IP. He also took to posting personal details such as Krebs' credit report, directions to his house, and pictures of his front door on LiveJournal, of all places.
So, after spotting the scheme, he alerted his local police that he'd probably have someone sending him some China White. Sure enough, the ne'er-do-wells managed to raise 2 BTC, which at the time was a cool $200 or so. They created an account on the premiere darknet site at the time, The Silk Road under the foolproof name "briankrebs7". They found one seller who had consistently high reviews, but the deal fell through for unknown reasons. My personal theory is the seller decided to Google where it was going, and realized sending a gram of dope into the waiting arms of local law enforcement probably wasn't the best use of his time. Still, the forum members persevered, and found another seller who was running a buy 10 get 2 free promotion. $165 of Bitcoin later, the drugs were on their way to a new home. The seller apparently informed Fly that the shipment should arrive by Tuesday, a fact which he gleefully shared with the forum.
While our intrepid hero had no doubt that the forum members were determined to help him grab the tail of the dragon, he's not one to assume without confirmation, and enlisted the help of a graduate student at UCSD who was researching Bitcoin and anonymity on The Silk Road, and confirmed the address shared by Fly was used to deposit 2 BTC into an account known to be used for money management on the site.
By Monday, an envelope from Chicago had arrived, containing a copy of Chicago confidential. Taped inside were tiny baggies filled with the purported heroin. Either dedicated to satisfied customers, or mathematically challenged, the seller had included thirteen baggies instead of the twelve advertised. A police officer arrived to take a report and whisked the baggies away.
Now, Fly was upset that Krebs wasn't in handcuffs for drug possession, and decided to follow up his stunt by sending Krebs a floral arrangement shaped like a cross, and an accompanying threatening message addressed to his wife, the dire tone slightly undercut by the fact that it was signed "Velvet Crabs". Krebs' curiosity was already piqued from the shenanigans with the heroin, but with the arrival of the flowers decided to dive deeper into the сука behind things.
He began digging into databases from carding sites that had been hacked, but got his first major breakthrough to his identity from a Russian computer forensics firm. Fly had maintained an account on a now-defunct hacking forum, whose database was breached under "Flycracker". It turns out, the email Flycracker had used was also hacked at some point, and a source told Krebs that the email was full of reports from a keylogger Fly had installed on his wife's computer. Now, because presumably his wife wasn't part of, or perhaps even privy to her husband's illicit dealings, her email account happened to be her full legal name, which Krebs was able to trace to her husband. Now, around this time, the site Fly maintained disappeared from the web, and administrators on another major fraud forum started purging his account. This is a step they typically take when they suspect a member has been apprehended by authorities. Nobody knew for sure, but they didn't want to take any chances.
More research by Krebs revealed that the criminals' intuition had been correct, and Fly was arrested in Italy, carrying documents under an assumed name. He was sitting in an Italian jail, awaiting potential extradition to the United States, as well as potentially facing charges in Italy. This was relayed to Krebs by a law enforcement official who simply said "The Fly has been swatted". (Presumably while slowly removing a pair of aviator sunglasses)
While Fly may have been put away, the story between Krebs and Fly wasn't quite over. He did end up being extradited to the US for prosecution, but while imprisoned in Italy, Fly actually started sending Krebs letters. Understandably distrustful after the whole "heroin" thing, his contacts in federal law enforcement tested the letter, and found it to be clean. Inside, there was a heartfelt and personal letter, apologizing for fucking with Krebs in so many ways. He also forgave Krebs for posting his identity online, leading him to muse that perhaps Fly was working through a twelve-step program. In December, he received another letter, this time a simple postcard with a cheerful message wishing him a Merry Christmas and a Happy New Year. Krebs concluded his post thusly:
Cybercrooks have done some pretty crazy stuff to me in response to my reporting about them. But I don’t normally get this kind of closure. I look forward to meeting with Fly in person one day soon now that he will be just a short train ride away. And he may be here for some time: If convicted on all charges, Fly faces up to 30 years in U.S. federal prison.
Fly ultimately was extradited. He plead guilty and was sentenced to 41 months in jail

vDOS and Mirai Break The Internet

Criminals are none too happy when they find their businesses and identities on the front page of KrebsOnSecurity. It usually means law enforcement isn't far behind. One such business was known as vDOS. A DDOS-for-hire (also known as a "booter" or a "stresser") site that found itself hacked, with all their customer records still in their databases leaked. Analysis of the records found that in a four-month time span, the service had been responsible for about 8.81 years worth of attack time, meaning on average at any given second, there were 26 simultaneous attacks running. Interestingly, the hack of vDOS came about from another DDOS-for-hire site, who as it turns out was simply reselling services provided by vDOS. They were far from the only one. vDOS appeared to provide firepower to a large number of different resellers.
In addition to the attack logs, support messages were also among the data stolen. This contained some complaints from various clients who complained they were unable to launch attacks against Israeli IPs. This is a common tactic by hackers to try and avoid unwanted attention from authorities in their country of residence. This was confirmed when two men from Israel were arrested for their involvement in owning and running vDOS. However, this was just the beginning for this bit of drama.
The two men arrested went by the handles "applej4ck" and "Raziel". They had recently published a paper on DDOS attack methods in an online Israeli security magazine. Interestingly, on the same day the men were arrested, questioned, and released on bail, vDOS went offline. Not because it had been taken down by Israeli authorities, not because they had shut it down themselves, but because a DDOS protection firm, BackConnect Security, had hijacked the IP addresses belonging to the company. To spare a lot of technical detail, it's called a BGP hijack, and it basically works by a company saying "Yeah, those are our addresses." It's kind of amazing how much of the internet is basically just secured by the digital equivalent of pinky swears. You can read some more technical detail on Wikipedia. Anyway, we'll get back to BackConnect.
Following the publication of the story uncovering the inner workings of vDOS, KrebsOnSecurity was hit with a record breaking DDOS attack, that peaked at 620/Gbps, nearly double the most powerful DDOS attack previously on record. To put that in perspective, that's enough bandwidth to download 5 simultaneous copies of Interstellar in 4K resolution every single second, and still have room to spare. The attack was so devastating, Akamai, one of the largest providers of DDOS protection in the world had to drop Krebs as a pro bono client. Luckily, Google was willing to step in and place his site under the protection of Google's Project Shield, a free service designed to protect the news sites and journalists from being knocked offline by DDOS attacks.
This attack was apparently in retaliation for the vDOS story, since some of the data sent in the attack included the string "freeapplej4ck". The attack was executed by a botnet of Internet of Things (or IoT) devices. These are those "smart" devices like camera systems, routers, DVRs. Basically things that connect to the cloud. An astounding amount of those are secured with default passwords that can be easily looked up from various sites or even the manufacturers' websites. This was the start of a discovery of a massive botnet that had been growing for years.
Now time for a couple quick side stories:
Dyn, a company who provides DNS to many major companies including Twitter, Reddit, and others came under attack, leaving many sites (including Twitter and Reddit) faltering in the wake of it. Potentially due to one of their engineers' collaboration with Krebs on another story. It turned out that the same botnet that attacked Krebs' site was at least part of the attack on Dyn
And back to BackConnect, that DDOS protection firm that hijacked the IP addresses from vDOS. Well it turns out BGP Hijacks are old hat for the company. They had done it at least 17 times before. Including at least once (purportedly with permission) for the address 1.3.3.7. Aka, "leet". It turns out one of the co-founders of BackConnect actually posted screenshots of him visiting sites that tell you your public IP address in a DDOS mitigation industry chat, showing it as 1.3.3.7. They also used a BGP Hijack against a hosting company and tried to frame a rival DDOS mitigation provider.
Finally, another provider, Datawagon was interestingly implicated in hosting DDOS-for-hire sites while offering DDOS protection. In a Skype conversation where the founder of Datawagon wanted to talk about that time he registered dominos.pizza and got sued for it, he brings up scanning the internet for vulnerable routers completely unprompted. Following the publication of the story about BackConnect, in which he was included in, he was incensed about his portrayal, and argued with Krebs over Skype before Krebs ultimately ended up blocking him. He was subsequently flooded with fake contact requests from bogus or hacked Skype accounts. Shortly thereafter, the record-breaking DDOS attack rained down upon his site.
Back to the main tale!
So, it turns out the botnet of IoT devices was puppeteered by a malware called Mirai. How did it get its name? Well, that's the name its creator gave it, after an anime called Mirai Nikki. How did this name come to light? The creator posted the source code online. (The name part, not the origin. The origin didn't come 'til later.) The post purported that they'd picked it up from somewhere in their travels as a DDOS industry professional. It turns out this is a semi-common tactic when miscreants fear that law enforcement might come looking for them, and having the only copy of the source code of a malware in existence is a pretty strong indicator that you have something to do with it. So, releasing the source to the world gives a veneer of plausible deniability should that eventuality come to pass. So who was this mysterious benefactor of malware source? They went by the name "Anna-senpai".
As research on the Mirai botnet grew, and more malware authors incorporated parts of Mirai's source code into their own attacks, attention on the botnet increased, and on the people behind it. The attention was presumably the reason why Hackforums, the forum where the source code was posted, later disallowed ostensible "Server Stress Tester" services from being sold on it. By December, "Operation Tarpit" had wrought 34 arrests and over a hundred "knock and talk" interviews questioning people about their involvement.
By January, things started to come crashing down. Krebs published an extensive exposé on Anna-senpai detailing all the evidence linking them to the creation of Mirai. The post was so big, he included a damn glossary. What sparked the largest botnet the internet had ever seen? Minecraft. Minecraft servers are big business. A popular one can earn tens of thousands of dollars per month from people buying powers, building space, or other things. It's also a fiercely competitive business, with hundreds of servers vying for players. It turns out that things may have started, as with another set of companies, two rival DDOS mitigation providers competing for customers. ProTraf was a provider of such mitigation technology, and a company whose owner later worked for ProTraf had on at least one occasion hijacked addresses belonging to another company, ProxyPipe. ProxyPipe had also been hit with DDOS attacks they suspected to be launched by ProTraf.
While looking into the President of ProTraf, Krebs realized he'd seen the relatively uncommon combination of programming languages and skills posted by the President somewhere else. They were shared by Anna-senpai on Hackforums. As Krebs dug deeper and deeper into Anna-senpai's online presence, he uncovered other usernames, including one he traced to some Minecraft forums where a photoshopped picture of a still from Pulp Fiction contained the faces of BackConnect, which was a rival to ProTraf's DDOS mitigation business, and another face. A hacker by the name of Vyp0r, who another employee of ProTraf claimed betrayed his trust and blackmailed him into posting the source of another piece of malware called Bashlite. There was also a third character photoshopped into the image. An anime character named "Yamada" from a movie called B Gata H Hei.
Interestingly, under the same username, Krebs found a "MyAnimeList" profile which, out of 9 titles it had marked as watched, were B Gata H Hei, as well as Mirai Nikki, the show from which Mirai derived its name. It continues on with other evidence, including DDOS attacks against Rutgers University, but in short, there was little doubt in the identity of "Anna-senpai", but the person behind the identity did contact Krebs to comment. He denied any involvement in Mirai or DDOS attacks.
"I don’t think there are enough facts to definitively point the finger at me," [Anna-senpai] said. "Besides this article, I was pretty much a nobody. No history of doing this kind of stuff, nothing that points to any kind of sociopathic behavior. Which is what the author is, a sociopath."
He did, however, correct Krebs on the name of B Gata H Kei.
Epilogue
Needless to say, the Mirai botnet crew was caught, but managed to avoid jailtime thanks to their cooperation with the government. That's not to say they went unpunished. Anna-senpai was sentenced to 6 months confinement, 2500 hours of community service, and they may have to pay up to $8.6 million in restitution for their attacks on Rutgers university.

Other Stories

I don't have the time or energy to write another effortpost, and as is I'm over 20,000 characters, so here's a few other tidbits of Krebs' clashes with miscreants.
submitted by HereComesMyDingDong to internetdrama [link] [comments]

r/Bitcoin recap - April 2019

Hi Bitcoiners!
I’m back with the 28th monthly Bitcoin news recap.
For those unfamiliar, each day I pick out the most popularelevant/interesting stories in Bitcoin and save them. At the end of the month I release them in one batch, to give you a quick (but not necessarily the best) overview of what happened in bitcoin over the past month.
You can see recaps of the previous months on Bitcoinsnippets.com
A recap of Bitcoin in April 2019
Adoption
Development
Security
Mining
Business
Education
Archeology (Financial Incumbents)
Price & Trading
Fun & Other
submitted by SamWouters to Bitcoin [link] [comments]

Warning: Do not invest in MoneroV.

Okay MoneroV gets posted about enough I think it's time someone told the truth about what's going on. Save this post and paste it on other XMV threads, because this shit is a fucking scam.

Everything MoneroV does "differently" is a lie. Here are their claims.

Please save, share and spread this post like wildfire. As a large user of Monero I'm making this post completely against my own economical gain, but this really needs to be said. I would even encourage you to ask these questions on their subreddit (although fair warning you will get banned ). Stay safe and happy forking.

submitted by OsrsNeedsF2P to CryptoCurrency [link] [comments]

The chatlog from #lightning-network discussing recent Lightning DDOS/vulnerability

bitPico [5:49 PM] If any LN testers see their connection slots full it’s us. We will release the attack code when ready. The network needs better protection against DDoS’s. (edited)
Laolu Osuntokun [5:59 PM] ? or report to specific implementations @bitPico? like the early days of bitcoin, don't think many impls have even started to start to cover dos vectors busy working on safety in other aspects
bitPico [6:00 PM] As it stands no implementation can handle connection exhaustion attacks by overflowing the underlying TCP stack.
Laolu Osuntokun [6:00 PM] not sure if any limit inbound connections yet
bitPico [6:02 PM] Doesn’t matter; we use the TCP half-open attack. This occurs at the kernel.
Laolu Osuntokun [6:02 PM] sure you'd still run into fd limits so that's not really impl specific
bitPico [6:02 PM] Yes; we exhaust the FD’s. (edited)
Laolu Osuntokun [6:04 PM] you could do the same for any active bitcoin node today, nodes would need to set up network-level mitigations unless the impls were super low level enough to detect something like that so would really depend on their default kernel settings
Matt Drollette [6:10 PM] echo 1 > /proc/sys/net/ipv4/tcp_syncookies … ?
bitPico [6:14 PM] Our Bitcoin implementation performs round-robin disconnects to induce network churn. This is one of the best methods to prevent most TCP attacks. Churn is needed in decentralized systems. It keeps them robust. Longstanding TCP connections are bad. *ie we disconnect N nodes every T mins.
Laolu Osuntokun [6:18 PM] if it's half open, how are you detecting the TCP connections then @bitPico? well for LN the connections are typically long lived @mdrollette yeh, defenses are at the kernel lvl
bitPico [6:21 PM] Round-robin disconnects free the kernel FD’s. There is also App level half-connect Works like this Syn Ack But don’t sent the Ack The connection is then half-open TCP connect scans work like this. TCP half-open scans are harder to detect.
ɹɑd [6:33 PM] Is there a way to tell lnd to listen on ipv4 instead of ipv6? When I try lnd --listen=0.0.0.0:9735 ..., it is listening on IPv6 TCP *:9735 but I need it to listen on IPv4.
Matt Drollette [6:34 PM] I think if you give it a specific IP instead of 0.0.0.0 it will only bind to that specific interface
ɹɑd [6:34 PM] ok, trying that…
bitPico [6:36 PM] Dual-stack OS will still open IPv6 Windows and Linux are VERY different TCP stacks. The behaviour is different.
ɹɑd [6:38 PM] Nice, that worked. Thanks, @mdrollette
bitPico [7:13 PM] How does LN protect from “dead end packets”? ie* onion wrapped but final destination doesn’t exist. aka routing amplification attack
kekalot [7:14 PM] :trumpet::skull:
bitPico [7:16 PM] We will test it and perform a 100,000 route amplification. We are trying to make our test kit reusable as possible to work out the kinks. (edited)
kekalot [7:16 PM] :trumpet::skull:
bitPico [7:25 PM] Seeing bad OP-SEC on LN; don’t name your node as the type of hardware. Those raspberry pi’s will go down.
kekalot [7:25 PM] :trumpet: :skull:
camelCase [7:26 PM] :joy:
bitPico [7:26 PM] ie* eclair.raspberry.pi
Abhijeet singh [8:05 PM] joined #lightning-network.
bitPico [8:48 PM] https://gist.github.com/anonymous/46f6513625579c5a920fe04b32103a03 Already running some custom attack vectors on LN nodes to see how they standup.
Sun Mar 18 23:49:08 [INFO] - open_tcp_transports: Preparing TCP connection to x.x.x.x:9735 for attack vector TCPHO. Sun Mar 18 23:49:08 [INFO] - open_tcp_transports: Preparing TCP connection to x.x.x.x:9735 for attack vector TCPHO. Sun Mar 18 23:49:08 [INFO] - open_tcp_transports: Preparing TCP connection to x.x.x.x:9735 for attack vector TCPHO. Sun Mar 18 23:49:08 [INFO] - open_tcp_transports: Preparing TCP connection to x.x.x.x:9735 for attack vector TCPHO. Sun Mar 18 23:49:08 [INFO] - open_tcp_transports: Preparing TCP connection to x.x.x.x:9735 for attack vector TCPHO. Sun Mar 18 23:49:08 [INFO] - open_tcp_transports: Preparing TCP connection to x.x.x.x:9735 for attack vector TCPHO. Sun Mar 18 23:49:08 [INFO] - open_tcp_transports: Preparing TCP connection to x.x.x.x:9735 for attack vector TCPHO. Sun Mar 18 23:49:08 [INFO] - open_tcp_transports: Preparing TCP connection to x.x.x.x:9735 for attack vector TCPHO. Sun Mar 18 23:49:08 [INFO] - open_tcp_transports: Preparing TCP connection to x.x.x.x:9735 for attack vector TCPHO. Sun Mar 18 23:49:08 [INFO] - open_tcp_transports: Preparing TCP connection to We expect to perfect this testsuite by the weekend with some very useable attack vectors Sun Mar 18 23:51:19 [INFO] - operator(): TCP connection to x.x.x.x:9735 success, sending attack payload. Sun Mar 18 23:51:19 [INFO] - operator(): TCP connection to x.x.x.x:9735 failed, message = Connection refused. Sun Mar 18 23:51:19 [INFO] - operator(): TCP connection to x.x.x.x:9735 success, sending attack payload. Sun Mar 18 23:51:19 [INFO] - operator(): TCP connection to x.x.x.x:9735 success, sending attack payload. Sun Mar 18 23:51:19 [INFO] - operator(): TCP connection to x.x.x.x:9735 success, sending attack payload. Sun Mar 18 23:51:19 [INFO] - operator(): TCP connection to x.x.x.x:9735 success, sending attack payload.
:+1: If you notice weird traffic it’s us.
bitPico [9:00 PM] We are most interested in our “route payload amplification” attack vector. This attack onion wraps payloads via hop by hop where the last hop is the first hop creating a self-denial of service where the LN nodes attack themselves after long route traversal. Exploiting the anonymous nature of onion routing allows no defense to the network. Anonymous routing in and of itself creates a situation where the network can get into an endless loop of self DDoS. Once we complete the entire message serialization routines and a deadline timer the TESTBED will run standalone continuously. Prob. only take another day to complete that. We are also making attack vectors as base classes so new ones can be easily created via overrides. *ie plugin-like attack vectors
Russell O'Connor [9:22 PM] https://lists.linuxfoundation.org/pipermail/lightning-dev/2015-August/000135.html
bitPico [9:26 PM] Yes; that idea and our attack vector(s) makes the entire network fall apart. We will prove this works. (edited) When nobody trusts nobody the network collapses. Low level attacks requiring no fees are easier however. (edited) There is nothing to prevent spoofing via replay of older packets. Because onion routing requires decryption (CPU Intensive) this can also be used to clog pathways with old payloads via CPU exhaustion. (edited) This is the real reason why ToR is so damn slow; it’s constantly attacked. It has nothing to do with end users actions.
Matt Drollette [9:34 PM] https://github.com/lightningnetwork/lnd/pull/761 GitHub Switch Persistence [ALL]: Forwarding Packages + Sphinx Replay Protection + Circuit Persistence by cfromknecht · Pull Request #761 · lightningnetwork/lnd This PR builds on #629, and integrates the changes with my more recent work on forwarding packages and batch-replay protection provided via pending changes to lightning-onion repo. Save one or two ...
bitPico [9:40 PM] (#)761 doesn’t impact our AV_03 It does however cause nodes to use more CPU and possibly go to disk per the notes. If LN nodes must go to disk this is bad. The slowest code pathways make the best AV’s.
bitPico [9:52 PM] CircuitKey’s are allocated “on the heap”. (edited) Underlying implementation would use malloc/realloc/free. Instead of RAII. This is asking for an overflow into unknown memory segments. We suggest stack only allocation. Memory on the stack is trivial to maintain; it has no holes; it can be mapped straight into the cache; it is attached on a per-thread basis. Memory in the heap is a heap of objects; it is more difficult to maintain; it can have holes.
Laolu Osuntokun [9:59 PM] @bitPico cpu usage is super minimal, this isn't tor so we're not relaying like gigabytes unknown memory segments? golang is a memory safe language stuff goes on the stack, then escape analysis is used to decide what should go on the heap
bitPico [10:00 PM] Heap allocation is more of a concern here. golang is not memory safe; it uses C underneath.
Laolu Osuntokun [10:01 PM] uhh
bitPico [10:01 PM] golang is not written in golang :slightly_smiling_face:
Laolu Osuntokun [10:01 PM] yes it is... https://github.com/golang/go/blob/mastesrc/runtime/map.go GitHub golang/go go - The Go programming language
bitPico [10:02 PM] That’s like saying the C runtime is C and not ASM. The C runtime is ASM.
Laolu Osuntokun [10:02 PM] go is written in go before go 1.4 (maybe 1.5) is was written in c but still, your "attack vector" isn't an implementation level issue, it's a network/kernel level DoS recycling, syn cookies, etc, would be needed not impl level defenses (edited)
bitPico [10:07 PM] We know the answer but what does golang compile to?
Laolu Osuntokun [10:07 PM] also replay htlc's will be rejected native?
bitPico [10:08 PM] ASM
Laolu Osuntokun [10:08 PM] yeh...
bitPico [10:08 PM] So what we said is exactly true.
Laolu Osuntokun [10:08 PM] no?
bitPico [10:08 PM] It’s as vulnerable as we stated.
Laolu Osuntokun [10:08 PM]
the heap is a heap of objects; it is more difficult to maintain; it can have holes
bitPico [10:09 PM] It still allocates through OS heap memory and not onto the stack in your case here. Which means it has holes.
Laolu Osuntokun [10:10 PM] aight, lemmie know when you exploit these issues in the golang runtime here's the code if you wanna study it: https://github.com/golang/go/ GitHub golang/go go - The Go programming language
bitPico [10:11 PM] ASM is ASM. Heap is heap. Heap is bad in this case. Stack is wise. Same applies to C or C++. Avoid the heap at all costs.
Laolu Osuntokun [10:12 PM] aye aye, capt
stark [10:12 PM] replied to a thread: Seeing bad OP-SEC on LN; don’t name your node as the type of hardware. Those raspberry pi’s will go down. don't name your node at all....
bitPico [10:12 PM] https://www.cs.ru.nl/E.Poll/hacking/slides/hic4.pdf
Laolu Osuntokun [10:13 PM] cool, i'll be waiting on those exploits in the go runtime, i'm sure many others will be excited as well
bitPico [10:14 PM] Has nothing to do with go. It uses malloc underneath. Heap always uses malloc; go, c or c++ or java or whatever.
Laolu Osuntokun [10:15 PM] sure, i think many of us know how memory management works
bitPico [10:15 PM] http://security.cs.rpi.edu/courses/binexp-spring2015/lectures/17/10_lecture.pdf Security experts avoid heap allocation. This is common knowledge. Noticed somebody commented about performance of the PR. That is because of the use of heap allocation instead of stack.
Laolu Osuntokun [10:17 PM] no, it's because of the disk I/O
bitPico [10:18 PM] So LN nodes write data to disk in case of crash? As to not lose funds? That’s what the PR says. Anyway golang uses libc; it is not compiled into pure ASM. (edited) Nevertheless we are not focusing on golang; LN in general and TCP/IP stacks.
ɹɑd [10:22 PM] @bitPico write an exploit and get back with us. Until then it just sounds like concern trolling.
bitPico [10:24 PM] Funny, we are exhausting LN TCP/IP Stacks as we type this… It’s no good if we can overtake the TCP stack and run it out of FD’s. We have 100's of connections to LN nodes and it;s automated using our hand built attack toolkit. When we increase this to 1000's then what?
Matt Drollette [10:26 PM] Isn’t that true of any TCP service though? Or are you saying there is something Lightning or lnd specific about your method?
Laolu Osuntokun [10:26 PM] it's true of any TCP service the defenses are on the kernel level
bitPico [10:27 PM] You’d need to have LN code handle millions of connections to mitigate this. We know golang will crash if this happens. But so will C.
Matt Drollette [10:29 PM] I’m beginning to wonder if @bitPico is actually performing a meta-attack on Lightning. A denial-of-service at the developer level with all this subtle trolling
bitPico [10:29 PM] This first problem is LN keeps inbound connections alive. It does not handle and drop them like a webserver. This is the only reason webservers can scale. Apache uses a timeout of 3 seconds in most cases. Currently we are connected to 45 LN nodes with over 22K connections. One variable change on our end and the network will suffer. (edited)
Matt Drollette [10:31 PM] but is that variable on the heap?
bitPico [10:32 PM] On Linux consider forcing it to require 999999 FD’s. AND do not keep-alive connections. The variable is an enum (an integer). Attack aggressiveness
Matt Drollette [10:33 PM] I’m just joking with you :stuck_out_tongue: I look forward to the write-up on the attack
bitPico [10:33 PM] Otherwise our code will keep LN nodes hung in TIME_WAIT. Anyway we are not trolling; we are BTC whales and LN must not fail. Otherwise our investment suffers. The only motivation behind this testing… As it stands LN nodes need L7 LB. Code will run overnight; sleep before we continue. Good job though on LN so far.
bitPico [10:46 PM] uploaded and commented on this image: Screen Shot 2018-03-19 at 1.44.19 AM.png
Fun stats: We’ve sucked 3.3 GB’s of bandwidth per hour from LN nodes. This will continue while we sleep. Every 80 milliseconds there is 44 attacks being performed.
bitPico [10:48 PM] :sleeping:
kekalot [1:35 AM] Seems likely. They were also the one who claimed segwit 2x would continue after it was officially canceled. Matt Drollette I’m beginning to wonder if @bitPico is actually performing a meta-attack on Lightning. A denial-of-service at the developer level with all this subtle trolling Posted in #lightning-network Mar 18th
bitcoinhunter [3:07 AM] So you put down the network @bitPico or just DDosing dev`s time ?
kekalot [3:08 AM] technically youd need multiple people to be doing it to be considered DDoS this is just DoS
Mike Rizzo [7:57 AM] joined #lightning-network.
Alphonse Pace [8:31 AM] bitpico: are you bragging about attacking computer networks on here?
Bear Shark [9:54 AM] That was the funnest 5 minutes of my life. Watching a guy go from bragging about attempting a DoS to deleting the account.
aceat64 [9:56 AM] Reporting an attack vector is fine, releasing PoC code is fine, but actually DoSing a network is a crime, and to just go online and brag about it, wow The only way that could have been worse would be if they didn't use a pseudonym
Bear Shark [9:58 AM] It's fine. He was probably sitting behind 3 tor exits and 10 VPNs (edited)
chek2fire [10:09 AM] i see c-lightning is always at 80% cpu usage
Russell O'Connor [10:12 AM] Did bitPico delete their own account themselves?
kekalot [10:26 AM] @alp?
Alphonse Pace [10:27 AM] I banned. zero tolerance for illegal shit.
chek2fire [10:29 AM] and he says hitler is alive :stuck_out_tongue:
chek2fire [10:43 AM] i dont know why but the new version of lightning-c has a huge cpu usage (edited)
chek2fire [11:06 AM] is there possible not compatibility from lnd to c-lightning? i just connect bitrefil and they say that in their lnd node bitrefill payments works in my c-lightning is not working when i try to do a payment with their ln links i always get this "code" : 205, "message" : "Could not find a route", "data" : { "getroute_tries" : 2, "sendpay_tries" : 1 } }
hkjn [12:00 PM] was that just-banned bitpico the same one as this one? https://lists.linuxfoundation.org/pipermail/bitcoin-segwit2x/2017-Novembe000689.html
Russell O'Connor [12:02 PM] I believe they claimed to be. It's hard to know for sure I guess.
Matt Drollette [12:03 PM] Lest we forget.
ASM is ASM. Heap is heap. Heap is bad in this case. Stack is wise. Avoid the heap at all costs. - bitPico
Laolu Osuntokun [1:48 PM] lmao
Sent from my Space Ship
pebble [4:52 PM] joined #lightning-network.
camelCase [10:28 PM] could be possible to run two lnd nodes in sync between them? i mean wallet-wise (edited)
Justin Camarena [8:02 AM] Bitrefill getting DDos'd lol that bitpico tho
Brandy Lee Camacho [8:21 AM] joined #lightning-network.
chek2fire [8:53 AM] my c-lightning node has very high cpu usage is always at 80% in the same time bitcoin node is at 15-17%
Gregory Sanders [8:58 AM] @chek2fire could be the gossip silliness that's being worked on, or bitPico :stuck_out_tongue: probably gossip inefficiency
chek2fire [8:59 AM] maybe someone dos my node i dont know
Laolu Osuntokun [11:46 AM] time to learn how to use iptables folks
Sent from my Space Ship (edited)
camelCase [11:50 AM] anyone knows if what i asked above is possible? like running two or more nodes that replicate the wallet so you avoid having your channels offline
gonzobon [11:55 AM] https://twitter.com/alexbosworth/status/976158861722726405 Alex Bosworth ☇@alexbosworth Lightning nodes are getting DDOS'ed, rumor is that someone from the 2x effort known as "BitPico" has taken credit for this. The Lightning services I've deployed have been attacked from the start, with botnets, etc. Deploying in adversarial conditions, decentralization is hard.
Twitter Mar 20th
camelCase [11:56 AM] well... at least we know we wasn't trolling about that lol
v33r [11:58 AM] https://twitter.com/alexbosworth/status/976158861722726405
gonzobon [11:59 AM] beat you to it @v33r_ :stuck_out_tongue:
Tomislav Bradarić [12:23 PM] something something good for bitcoin but really, better to see how sturdy things are now than when lightning starts getting adopted more, like how the last rise in popularity was at the same time as blockchain spam
gonzobon [12:28 PM] andreas put it in context as a good testing opp.
Hiro Protagonist [1:04 PM] I so wanna get my old sysasmin-devops team together to start running lightning nodes under these conditions. Every website is attacked relentlessly by DoS, spoofing, etc. Defences exist but you need skills to figure out what to do.
submitted by bitsko to btc [link] [comments]

Transcript of Open Developer Meeting in Discord - 7/19/2019

[Dev-Happy] BlondfrogsLast Friday at 3:58 PM
Hey everyone. The channel is now open for the dev meeting.
LSJI07 - MBITLast Friday at 3:58 PM
Hi
TronLast Friday at 3:59 PM
Hi all!
JerozLast Friday at 3:59 PM
:wave:
TronLast Friday at 3:59 PM
Topics: Algo stuff - x22rc, Ownership token for Restricted Assets and Assets.
JerozLast Friday at 4:00 PM
@Milo is also here from coinrequest.
MiloLast Friday at 4:00 PM
Hi :thumbsup:
Pho3nix Monk3yLast Friday at 4:00 PM
welcome, @Milo
TronLast Friday at 4:00 PM
Great.
@Milo Was there PRs for Android and iOS?
MiloLast Friday at 4:01 PM
Yes, I've made a video. Give me a second I'll share it asap.
JerozLast Friday at 4:02 PM
I missed the iOS one.
MiloLast Friday at 4:02 PM
Well its 1 video, but meant for all.
JerozLast Friday at 4:02 PM
Ah, there's an issue but no pull request (yet?)
https://github.com/RavenProject/ravenwallet-ios/issues/115
[Dev-Happy] BlondfrogsLast Friday at 4:03 PM
nice @Milo
MiloLast Friday at 4:04 PM
Can it be that I have no video post rights?
JerozLast Friday at 4:05 PM
In discord?
MiloLast Friday at 4:05 PM
yes?
[Dev-Happy] BlondfrogsLast Friday at 4:05 PM
just a link?
JerozLast Friday at 4:05 PM
Standard version has a file limit afaik
Pho3nix Monk3yLast Friday at 4:05 PM
try now
gave permissions
MiloLast Friday at 4:05 PM
it's not published yet on Youtube, since I didn't knew when it would be published in the wallets
file too big. Hold on i'll put it on youtube and set it on private
LSJI07 - MBITLast Friday at 4:06 PM
no worries ipfs it...:yum:
Pho3nix Monk3yLast Friday at 4:06 PM
ok, just send link when you can
[Dev-Happy] BlondfrogsLast Friday at 4:07 PM
So guys. We released Ravencoin v2.4.0!
JerozLast Friday at 4:08 PM
If you like the code. Go update them nodes! :smiley:
[Dev-Happy] BlondfrogsLast Friday at 4:08 PM
We are recommending that you are upgrading to it. It fixes a couple bugs in the code base inherited from bitcoin!
MiloLast Friday at 4:08 PM
https://www.youtube.com/watch?v=t\_g7NpFXm6g&feature=youtu.be
sorry for the hold up
YouTube
Coin Request
Raven dev Gemiddeld
LSJI07 - MBITLast Friday at 4:09 PM
thanks short and sweet!!
KAwARLast Friday at 4:10 PM
Is coin request live on the android wallet?
TronLast Friday at 4:10 PM
Nice video.
It isn't in the Play Store yet.
Pho3nix Monk3yLast Friday at 4:10 PM
Well, this is the first time in a while where we have this many devs online. What questions do y'all have?
LSJI07 - MBITLast Friday at 4:11 PM
Algo questions?
Pho3nix Monk3yLast Friday at 4:11 PM
sure
KAwARLast Friday at 4:11 PM
KK
LSJI07 - MBITLast Friday at 4:12 PM
what are the proposed 22 algos in x22r? i could only find the original 16 plus 5 on x21.
TronLast Friday at 4:12 PM
Likely the 5 from x21 and find one more.
We need to make sure they're all similar in time profile.
liqdmetalLast Friday at 4:14 PM
should we bother fixing a asic-problem that we dont know exists for sure or not?
TronLast Friday at 4:14 PM
That's the 170 million dollar question.
[Dev-Happy] BlondfrogsLast Friday at 4:14 PM
I would prefer to be proactive not reactive.
imo
JerozLast Friday at 4:14 PM
same
LSJI07 - MBITLast Friday at 4:15 PM
RIPEMD160 is a golden oldie but not sure on hash speed compared to the others.
liqdmetalLast Friday at 4:15 PM
in my mind we should focus on the restricted messaging etc
Sevvy (y rvn pmp?)Last Friday at 4:15 PM
probably won't know if the action was needed until after you take the action
liqdmetalLast Friday at 4:15 PM
we are at risk of being interventionistas
acting under opacity
TronLast Friday at 4:15 PM
Needs to spit out at least 256 bit. Preferably 512 bit.
LSJI07 - MBITLast Friday at 4:15 PM
ok
TronLast Friday at 4:15 PM
If it isn't 512 bit, it'll cause some extra headache for the GPU mining software.
liqdmetalLast Friday at 4:16 PM
i seek to avoid iatrogenics
TronLast Friday at 4:16 PM
Similar to the early problems when all the algos except the first one were built for 64-bytes (512-bit) inputs.
Had to look that one up. TIL iatrogenics
JerozLast Friday at 4:17 PM
I have to google most of @liqdmetal's vocabulary :smile:
liqdmetalLast Friday at 4:17 PM
@Tron tldr: basically the unseen, unintended negative side effects of the asic "cure"
Sevvy (y rvn pmp?)Last Friday at 4:18 PM
10 dolla word
liqdmetalLast Friday at 4:19 PM
we need a really strong case to intervene in what has been created.
TronLast Friday at 4:19 PM
I agree. I'm less concerned with the technical risk than I am the potential split risk experienced multiple times by Monero.
Sevvy (y rvn pmp?)Last Friday at 4:20 PM
tron do you agree that forking the ravencoin chain presents unique risks compared to other chains that aren't hosting assets?
JerozLast Friday at 4:21 PM
Yes, if you fork, you need to figure out for each asset which one you want to support.
Sevvy (y rvn pmp?)Last Friday at 4:21 PM
yeah. and the asset issuer could have a chain preference
TronLast Friday at 4:22 PM
@Sevvy (y rvn pmp?) Sure. Although, I'd expect that the asset issuers will be honor the assets on the dominant chain. Bigger concern is the branding confusion of multiple forks. See Bitcoin, Bitcoin Cash, Bitcoin SV for an example. We know they're different, but do non-crypto folks?
Hans_SchmidtLast Friday at 4:22 PM
I thought that the take-away from the recently published analyses and discussions was that ASICs for RVN may be active, but if so then they are being not much more effective than GPUs.
Sevvy (y rvn pmp?)Last Friday at 4:22 PM
agreed on all accounts there tron
TronLast Friday at 4:23 PM
I'm not yet convinced ASICs are on the network.
KAwARLast Friday at 4:23 PM
It would be better to damage an asic builder by forking after they made major expenses. Creating for them the type of deficit that could be negated by just buying instead of mining. Asic existence should be 100 percent confirmed before fork.
liqdmetalLast Friday at 4:23 PM
170million dollar question is right.lol
TronLast Friday at 4:24 PM
I've had someone offer to connect me to the folks at Fusion Silicon.
Sevvy (y rvn pmp?)Last Friday at 4:25 PM
yes. and if they are active on the network they are not particularly good ASICs
which makes it a moot point probably
TronLast Friday at 4:26 PM
The difficult part of this problem is that by the time everyone agrees that ASICs are problematic on the network, then voting the option in is likely no longer an option.
Sevvy (y rvn pmp?)Last Friday at 4:26 PM
yes. part of me wonders if we would say "okay, the clock on the asic countdown is reset by this new algo. but now the race is on"
[Dev-Happy] BlondfrogsLast Friday at 4:26 PM
There are always risks when making a change that will fork the network. We want wait to long though, as tron said. It wont be a voting change. it will be a mandatory change at a block number.
Sevvy (y rvn pmp?)Last Friday at 4:26 PM
acknowledge the inevitable
MiloLast Friday at 4:27 PM
I had just a small question from my side. When do you think the android version would be published, and do you maybe have a time-frame for the others?
TronLast Friday at 4:27 PM
Quick poll. How would everyone here feel about a BIP9 option - separate from the new features that can be voted in?
KAwARLast Friday at 4:27 PM
Maybe voting should not be a strictly blockchain vote. A republic and a democratic voice?
[Dev-Happy] BlondfrogsLast Friday at 4:27 PM
@Milo We can try and get a beta out next week, and publish soon after that.
MiloLast Friday at 4:28 PM
@[Dev-Happy] Blondfrogs :thumbsup::slight_smile:
[Dev-Happy] BlondfrogsLast Friday at 4:28 PM
BIP9 preemptive vote. I like it.
TronLast Friday at 4:30 PM
The advantage to a BIP9 vote is that it puts the miners and mining pools at a clear majority before activation.
LSJI07 - MBITLast Friday at 4:30 PM
Centralisation is inevitable unless we decide to resist it. ASIC's are market based and know the risks and rewards possible. A key step in resisting is sending a message. An algo change to increase asic resistance is imho a strong message. A BIP9 vote now would also be an indicator of bad actors early....
TronLast Friday at 4:30 PM
The disadvantage is that it may not pass if the will isn't there.
LSJI07 - MBITLast Friday at 4:30 PM
Before assets are on main net and cause additional issues.
KAwARLast Friday at 4:31 PM
I am not schooled in coding to have an educated voice. I only understand social problems and how it affects the economy.
SpyderDevLast Friday at 4:31 PM
All are equal on RVN
TronLast Friday at 4:31 PM
It is primarily a social problem. The tech change is less risky and is easier than the social.
LSJI07 - MBITLast Friday at 4:32 PM
All can have a share....people who want more of a share however pay for the privilege and associated risks.
KAwARLast Friday at 4:33 PM
Assets and exchange listings need to be consistent and secure.
brutoidLast Friday at 4:36 PM
I'm still not entirely clear on what the overall goal to the algo change is? Is it just to brick the supposed ASICs (unknown 45%) which could still be FPGAs as seen from the recent block analysis posted in the nest. Is the goal to never let ASICs on? Is it to brick FPGAs ultimately. Are we making Raven strictly GPU only? I'm still unclear
LSJI07 - MBITLast Friday at 4:37 PM
What about the future issue of ASICs returning after a BIP9 fork "soon"? Are all following the WP as a community? i.e asic resistant or are we prepared to change that to asic resistant for early coin emission. Ideally we should plan for the future. Could the community make a statement that no future algo changes will be required to incentivise future public asic manufacturers?
Lol. Same question @brutoid
brutoidLast Friday at 4:37 PM
Haha it is
You mind-beamed me!
[Dev-Happy] BlondfrogsLast Friday at 4:38 PM
The is up to the community.
Currently, the feel seems like the community is anti asic forever.
The main issue is getting people to upgrade.
KAwARLast Friday at 4:38 PM
Clarity is important. Otherwise we are attacking windmills like Don Quixote.
brutoidLast Friday at 4:39 PM
I'm not getting the feeling of community ASIC hate if the last few weeks of discussion are anything to go by?
Hans_SchmidtLast Friday at 4:39 PM
A unilateral non-BIP9 change at a chosen block height is a serious thing, but anti-ASIC has been part of the RVN philosophy since the whitepaper and is therefore appropriate for that purpose.
[Dev-Happy] BlondfrogsLast Friday at 4:39 PM
We can use the latest release as an example. It was a non forking release, announced for 2 weeks. and only ~30% of the network has upgraded.
TronLast Friday at 4:39 PM
@Hans_Schmidt Well said.
liqdmetalLast Friday at 4:40 PM
I'm not concerned about a "asic hardware problem" so much as I believe it more likely what we are seeing is several big fish miners (perhaps a single really big fish). For now I recommend standing pat on x16r. In the future I can see an algo upgrade fork to keep the algo up to date. If we start fighting against dedicated x16r hashing machines designed and built to secure our network we are more likely to go down in flames. The custom SHA256 computers that make the bitcoin the most secure network in existence are a big part of that security. If some party has made an asic that performs up to par or better than FPGA or GPU on x16r, that is a positive for this network, a step towards SHA256 security levels. It is too bad the community is in the dark regarding their developments. Therefore I think the community has to clarify its stance towards algorithm changes. I prefer a policy that will encourage the development of mining software, bitstreams and hardware by as many parties as possible. The imminent threat of ALGO fork screws the incentive up for developers.
JerozLast Friday at 4:40 PM
@brutoid the vocal ones are lenient towards asics, but the outcome of the 600+ votes seemed pretty clear.
brutoidLast Friday at 4:40 PM
This is my confusion
TronLast Friday at 4:41 PM
More hashes are only better if the cost goes up proportionally. Machines that do more hashes for less $ doesn't secure the network more, and trends towards centralization.
JerozLast Friday at 4:41 PM
I would argue for polling ever so often as it certainly will evolve dynamically with the state of crypto over time.
TronLast Friday at 4:41 PM
Measure security in two dimensions. Distribution, and $/hash.
liqdmetalLast Friday at 4:41 PM
and volume of hash
traysiLast Friday at 4:42 PM
45% of the hashrate going to one party is unhealthy, and standing pat on x16r just keeps that 45% where it is.
TronLast Friday at 4:42 PM
Volume doesn't matter if the cost goes down. For example, lets say software shows up that does 1000x better than the software from yesterday, and everyone moves to it. That does not add security. Even if the "difficulty" and embedded hashes took 1000x more attempts to find.
brutoidLast Friday at 4:42 PM
My issue is defintely centralization of hash and not so much what machine is doing it. I mine with both GPU and FPGA. Of course, the FPGAs are not on raven
TJayLast Friday at 4:44 PM
easy solution is just to replace a few of 16 current hash functions, without messing with x21r or whatever new shit
TronLast Friday at 4:44 PM
How do folks here feel about allowing CPUs back in the game?
traysiLast Friday at 4:44 PM
Botnets is my concern with CPUs
brutoidLast Friday at 4:44 PM
Botnets is my concern
SpyderDevLast Friday at 4:44 PM
Yes please.
LSJI07 - MBITLast Friday at 4:44 PM
the poll votes seem not very security conscious. More of day miners chasing profits. I love them bless! Imho the future is bright for raven, however these issues if not sorted out now will bite hard long term when asset are on the chain and gpu miners are long gone.....
ZaabLast Friday at 4:45 PM
How has the testing of restricted assets been on the test net?
liqdmetalLast Friday at 4:45 PM
Agreed. I dont think x16r is obsolete like that yet however
[Dev-Happy] BlondfrogsLast Friday at 4:45 PM
@Zaab not enough testing at the moment.
HedgerLast Friday at 4:45 PM
Yes, how is the Testing going?
justinjjaLast Friday at 4:45 PM
Like randomX or how are cpus going to be back in the game?
TronLast Friday at 4:45 PM
@Zaab Just getting started at testing at the surface level (RPC calls), and fixing as we go.
ZaabLast Friday at 4:45 PM
And or any updates on the review of dividend code created by the community
Lokar -=Kai=-Last Friday at 4:45 PM
if the amount of hash the unknown pool has is fixed as standarderror indicated then waiting for the community of FPGAers to get onto raven might be advantageous if the fork doesn't hurt FPGAs.
ZaabLast Friday at 4:45 PM
Can't rememeber who was on it
SpyderDevLast Friday at 4:45 PM
@Zaab But we are working on it...
Lokar -=Kai=-Last Friday at 4:46 PM
more hash for votes
JerozLast Friday at 4:46 PM
@Maldon is, @Zaab
TronLast Friday at 4:46 PM
@Zaab There are unit tests and functional tests already, but we'd like more.
[Dev-Happy] BlondfrogsLast Friday at 4:46 PM
@Zaab Dividend code is currently adding test cases for better security. Should have more update on that next meeting
KAwARLast Friday at 4:46 PM
Absolute democracy seems to resemble anarchy or at least civil war. In EVE online they have a type of community voice that get voted in by the community.
ZaabLast Friday at 4:46 PM
No worries was just curious if it was going as planned or significant issues were being found
Obviously some hiccups are expected
More testing is always better!
TronLast Friday at 4:47 PM
Who in here is up for a good civil war? :wink:
ZaabLast Friday at 4:47 PM
Tron v Bruce. Celebrity fight night with proceeds to go to the RVN dev fund
SpyderDevLast Friday at 4:48 PM
Cagefight or mudpit?
JerozLast Friday at 4:48 PM
talking about dev funds..... :wink:
Pho3nix Monk3yLast Friday at 4:49 PM
and there goes the conversation....
KAwARLast Friday at 4:49 PM
I am trying to be serious...
ZaabLast Friday at 4:49 PM
Sorry back to the ascii topic!
traysiLast Friday at 4:49 PM
@Tron What do we need in order to make progress toward a decision on the algo? Is there a plan or a roadmap of sorts to get us some certainty about what we're going to do?
LSJI07 - MBITLast Friday at 4:50 PM
Could we have 3 no BIP9 votes? No1 Friendly to asics, retain status quo. No2 change to x17r minimal changes etc, with no additional future PoW/algo upgrades. No3. Full Asic resistance x22r and see what happens...
:thonk~1:
Sounds messy....
TronLast Friday at 4:51 PM
Right now we're in research mode. We're building CNv4 so we can run some metrics. If that goes well, we can put together x22rc and see how it performs. It will likely gore everyone's ox. CPUs can play, GPUs work, but aren't dominant. ASICs VERY difficult, and FPGAs will have a tough time.
ZaabLast Friday at 4:51 PM
Yeah i feel like the results would be unreliable
TronLast Friday at 4:51 PM
Is this good, or do we lose everyone's vote?
PlayHardLast Friday at 4:52 PM
Fpga will be dead
Lokar -=Kai=-Last Friday at 4:52 PM
why isn;t a simple XOR or something on the table?
ZaabLast Friday at 4:52 PM
The multiple bip9 that is
Lokar -=Kai=-Last Friday at 4:52 PM
something asic breaking but doesn't greatly complicate ongoing efforts for FPGA being my point.
justinjjaLast Friday at 4:52 PM
How are you going to vote for x22rc?
Because if by hashrate that wouldn't pass.
traysiLast Friday at 4:52 PM
Personally I like the idea of x22rc but I'd want to investigate the botnet threat if CPUs are allowed back in.
TronLast Friday at 4:52 PM
XOR is on the table, and was listed in my Medium post. But, the social risk of chain split remains, for very little gain.
traysiLast Friday at 4:53 PM
@Lokar -=Kai=- A small change means that whoever has 45% can probably quickly adapt.
LSJI07 - MBITLast Friday at 4:53 PM
Research sounds good. x22rc could be reduce to x22r for simplicity...
TronLast Friday at 4:53 PM
x22r is a viable option. No CNv4.
LSJI07 - MBITLast Friday at 4:53 PM
Don't know how much time we have to play with though...
Lokar -=Kai=-Last Friday at 4:53 PM
if they have FPGAs yes if they have ASIC then not so much, but I guess that gets to the point, what exactly are we trying to remove from the network?
PlayHardLast Friday at 4:54 PM
Guys my name is Arsen and we designed x16r fpga on bcus. Just about to release it to the public. I am buzzdaves partner.
Cryptonight
Will kill us
But agreed
Asic is possible on x16r
And you dont need 256 core
Cores
traysiLast Friday at 4:55 PM
Hi Arsen. Are you saying CN will kill "us" meaning RVN, or meaning FPGA?
JerozLast Friday at 4:55 PM
This is what im afraid of ^ an algo change killing FPGA as I have the feeling there is a big fpga community working on this
PlayHardLast Friday at 4:55 PM
Fpgas ))
whitefire990Last Friday at 4:55 PM
I am also about to release X16R for CVP13 + BCU1525 FPGA's. I'm open to algo changes but I really don't believe in CPU mining because of botnets. Any CNv4 shifts 100% to CPU mining, even if it is only 1 of the 22 functions.
Lokar -=Kai=-Last Friday at 4:55 PM
namely FPGAs that aren;t memory equipped
like fast mem
not ddr
PlayHardLast Friday at 4:55 PM
Hbm non hbm
Cryptonight
whitefire990Last Friday at 4:56 PM
Right now with both Buzzdave/Altered Silicon and myself (Zetheron) about to release X16R for FPGA's, then the 45% miner's share will decrease to 39% or less.
PlayHardLast Friday at 4:56 PM
Will be dead for fpga
LSJI07 - MBITLast Friday at 4:56 PM
sound so x22r is fpga "friendly" ... more so than asic anyway...
PlayHardLast Friday at 4:56 PM
But a change must be planned
X16r is no way possible to avoid asics
TJayLast Friday at 4:56 PM
@LSJI07 - MBIT I would say less friendly...
whitefire990Last Friday at 4:57 PM
As I mentioned in thenest discussion, asic resistance increases with the square of the number of functions, so X21R is more asic resistant than X16R, but both are pretty resistant
PlayHardLast Friday at 4:58 PM
Yeah more algos make it heavier on ASIC
DirkDiggler (Citadel Architect)Last Friday at 4:58 PM
My interpretation of the whitepaper was that we used x16r as it was brand new (thus ASIC resistant), and that was to ensure a fair launch... We've launched... I don't like the idea of constantly forking to avoid the inevitable ASICs.
x16r was a great "experiment" before we had any exchange listings... that ship has sailed though... not sure about all these x22rs lmnop changes
KAwARLast Friday at 5:00 PM
I believe that it is easier to change the direction of a bicycle than an oil tanker. We feel more like a train. We should lay out new tracks and test on them and find benefits that are acceptable to everyone except train robbers. Then open the new train station with no contentious feelings except a silently disgruntled minority group. ???
Hans_SchmidtLast Friday at 5:01 PM
The most productive action the community can do now re ASICs is to voice support for the devs to make a non-BIP9 change at a chosen block height if/when the need is clear. That removes the pressure to act rashly to avoid voting problems.
LSJI07 - MBITLast Friday at 5:01 PM
Thats why im proposing to fork at least once to a more asic resistant algo (but FPGA "friendly/possible"), with the proviso ideally that no more PoW algo forks are require to provide future ASICs some opportunity to innovate with silicon and efficiency.
TJayLast Friday at 5:01 PM
folks should take into account, that high end FPGAs like BCU1525 on x16r can't beat even previous gen GPUs (Pascal) in terms of hash cost. so they aren't a threat to miners community
PlayHardLast Friday at 5:02 PM
A proper change
Requires proper research
eyz (Silence)Last Friday at 5:02 PM
Just so I'm clear here, we are trying to boot ASICS, don't want CPUs because of Botnets, and are GPU and FPGA friendly right?
PlayHardLast Friday at 5:02 PM
It is not a quick one day process
eyz (Silence)Last Friday at 5:02 PM
If there is a bip9 vote there needs to be a clear explanation as I feel most in the community don't understand exactly what we are trying to fix
TronLast Friday at 5:03 PM
@Hans_Schmidt I like that route. It has some game theoretics. It gives time for miners to adapt. It is only used if needed. It reduces the likelihood of ASICs dominating the network, or even being built.
[Dev-Happy] BlondfrogsLast Friday at 5:03 PM
Hey guys. great convo. We are of course looking to do the best thing for the community and miner. We are going to be signing off here though.
justinjjaLast Friday at 5:03 PM
TJay that comes down to power cost.
If your paying 4c/kw gpus all the way.
But if your a home miner in europe an fpga is your only chance
LSJI07 - MBITLast Friday at 5:03 PM
@Hans_Schmidt How do we decide the block limit and when sufficient evidence is available? I would say we have had much compelling information to date...
[Dev-Happy] BlondfrogsLast Friday at 5:03 PM
Thanks for participating. and keep up the good work :smiley:
Have a good weekend.
CAWWWW
TronLast Friday at 5:03 PM
I haven't seen any compelling evidence of ASICs - yet.
Pho3nix Monk3yLast Friday at 5:03 PM
:v:
JerozLast Friday at 5:04 PM
I suggest to continue discussion in #development and #thenest :smiley:
thanks all!
TronLast Friday at 5:04 PM
Cheers everyone!
KAwARLast Friday at 5:04 PM
Agree with Hans.
DirkDiggler (Citadel Architect)Last Friday at 5:04 PM
thanks Tron
Pho3nix Monk3yLast Friday at 5:04 PM
Ending here. continue in Nest if wanted
DirkDiggler (Citadel Architect)Last Friday at 5:04 PM
I am waiting for compelling evidence myself.
submitted by mrderrik to Ravencoin [link] [comments]

Why are people still sucking up to nicehash so readily?

Conspiracy theories aside it is still their fault to a large degree. They didnt have a firewall to protect their millions of dollars in bitcoin? Thats like having a bank with no vault just a low garden fence. You mean to tell me there was nothing, not even an untangle server? No one thought to implement a form of encryption or multiple authentication system on the payment system? No hard limits or anything? It may not be an inside job but holy shit is it pathetic security for a company who's CTO and head developer made what is arguably in the top 5 most well known botnets in the world. A cold storage machine with a task scheduler that would enable the network adapter for only a few minutes every day with the time synced to a seperate computer that handles the payments would act as a pretty good honeypot but they didnt do that either. No honeypots, no tricks up their sleeve just 4700BTC sitting on a computer that had full access from an engineers computer that apparently didnt even have the trial version of avast on it. It is no longer about the company when you fuck people out of so much money. People here were mining for Christmas gift money, to pay off loan debt, to make rent and heat their homes (both the meme and the central air) some lost hundreds some lost thousands and some lost dozens but what we have in common is that we lost it due to the gross negligence of nicehash. They were not the best paying but they were the easiest, we took that bait and got shafted for it. Lets apply ourselves a little guys we deserve better. If they pay us back ill mine with them until it is double as a thank you and a show of good will but after that im back to vertcoin or whatever else becomes profitable.
submitted by ishnessism to NiceHash [link] [comments]

ColossusXT Q2 AMA Ends!

Thank you for being a part of the ColossusXT Reddit AMA! Below we will summarize the questions and answers. The team responded to 78 questions! If you question was not included, it may have been answered in a previous question. The ColossusXT team will do a Reddit AMA at the end of every quarter.
The winner of the Q2 AMA Contest is: Shenbatu
Q: Why does your blockchain exist and what makes it unique?
A: ColossusXT exists to provide an energy efficient method of supercomputing. ColossusXT is unique in many ways. Some coins have 1 layer of privacy. ColossusXT and the Colossus Grid will utilize 2 layers of privacy through Obfuscation Zerocoin Protocol, and I2P and these will protect users of the Colossus Grid as they utilize grid resources. There are also Masternodes and Proof of Stake which both can contribute to reducing 51% attacks, along with instant transactions and zero-fee transactions. This protection is paramount as ColossusXT evolves into the Colossus Grid. Grid Computing will have a pivotal role throughout the world, and what this means is that users will begin to experience the Internet as a seamless computational universe. Software applications, databases, sensors, video and audio streams-all will be reborn as services that live in cyberspace, assembling and reassembling themselves on the fly to meet the tasks at hand. Once plugged into the grid, a desktop machine will draw computational horsepower from all the other computers on the grid.
Q: What is the Colossus Grid?
A: ColossusXT is an anonymous blockchain through obfuscation, Zerocoin Protocol, along with utilization of I2P. These features will protect end user privacy as ColossusXT evolves into the Colossus Grid. The Colossus Grid will connect devices in a peer-to-peer network enabling users and applications to rent the cycles and storage of other users’ machines. This marketplace of computing power and storage will exclusively run on COLX currency. These resources will be used to complete tasks requiring any amount of computation time and capacity, or allow end users to store data anonymously across the COLX decentralized network. Today, such resources are supplied by entities such as centralized cloud providers which are constrained by closed networks, proprietary payment systems, and hard-coded provisioning operations. Any user ranging from a single PC owner to a large data center can share resources through Colossus Grid and get paid in COLX for their contributions. Renters of computing power or storage space, on the other hand, may do so at low prices compared to the usual market prices because they are only using resources that already exist.
Q: When will zerocoin be fully integrated?
A: Beta has been released for community testing on Test-Net. As soon as all the developers consider the code ready for Main-Net, it will be released. Testing of the code on a larger test network network will ensure a smooth transition.
Q: Is the end goal for the Colossus Grid to act as a decentralized cloud service, a resource pool for COLX users, or something else?
A: Colossus Grid will act as a grid computing resource pool for any user running a COLX node. How and why we apply the grid to solve world problems will be an ever evolving story.
Q: What do you think the marketing role in colx.? When ll be the inwallet shared nodes available...i know its been stated in roadmap but as u dont follow roadmap and offer everything in advance...i hope shared MN's to be avilable soon.
A: The ColossusXT (COLX) roadmap is a fluid design philosophy. As the project evolves, and our community grows. Our goal is to deliver a working product to the market while at the same time adding useful features for the community to thrive on, perhaps the Colossus Grid and Shared Masternodes will be available both by the end of Q4 2018.
Q: When will your github be open to the public?
A: The GitHub has been open to the public for a few months now.
You can view the GitHub here: https://github.com/ColossusCoinXT
The latest commits here: https://github.com/ColossusCoinXT/ColossusCoinXT/commits/master
Q: Why should I use COLX instead of Monero?
A: ColossusXT offers Proof of Stake and Masternodes both which contribute layers in protection from 51% attacks often attributed with Proof of Work consensus, and in being Proof of Work(Monero) ColossusXT is environmentally friendly compared to Proof of Work (Monero). You can generate passive income from Proof of Stake, and Masternodes. Along with helping secure the network.What really sets ColossusXT apart from Monero, and many other privacy projects being worked on right now, is the Colossus Grid. Once plugged into the Colossus Grid, a desktop machine will draw computational horsepower from all the other computers on the grid. Blockchain, was built on the core value of decentralization and ColossusXT adhere to these standards with end-user privacy in mind in the technology sector.
Q: With so many coins out with little to no purpose let alone a definitive use case, how will COLX distinguish itself from the crowd?
A: You are right, there are thousands of other coins. Many have no purpose, and we will see others “pumping” from day to day. It is the nature of markets, and crypto as groups move from coin to coin to make a quick profit. As blockchain regulations and information is made more easily digestible projects like ColossusXT will rise. Our goal is to produce a quality product that will be used globally to solve technical problems, in doing so grid computing on the ColossusXT network could create markets of its own within utilizing Super-computing resources. ColossusXT is more than just a currency, and our steadfast approach to producing technical accomplishments will not go unnoticed.
Q: Tell the crowd something about the I2P integration plan in the roadmap? 🙂
A: ColossusXT will be moving up the I2P network layer in the roadmap to meet a quicker development pace of the Colossus Grid. The I2P layer will serve as an abstraction layer further obfuscating the users of ColossusXT (COLX) nodes. Abstraction layer allows two parties to communicate in an anonymous manner. This network is optimised for anonymous file-sharing.
Q: What kind of protocols, if any, are being considered to prevent or punish misuse of Colossus Grid resources by bad actors, such as participation in a botnet/denial of service attack or the storage of stolen information across the Grid?
A: What defines bad actors? ColossusXT plans on marketing to governments and cyber security companies globally. Entities and individuals who will certainly want their privacy protected. There is a grey area between good and bad, and that is something we can certainly explore as a community. Did you have any ideas to contribute to this evolving variable?What we mean when we say marketing towards security companies and governments is being utilized for some of the projects and innovating new ways of grid computing.
Security: https://wiki.ncsa.illinois.edu/display/cybersec/Projects+and+Software
Governments: https://www.techwalla.com/articles/what-are-the-uses-of-a-supercomputer
Q: The Colossus Grid is well defined but I don't feel easily digestible. Has their been any talk of developing an easier to understand marketing plan to help broaden the investoadoptor base?
A: As we get closer to the release of the Colossus Grid marketing increase for the Colossus Grid. It will have a user friendly UI, and we will provide Guides and FAQ’s with the release that any user intending to share computing power will be able to comprehend.
Q: Can you compare CollossusXT and Golem?
A: Yes. The Colosssus Grid is similar to other grid computing projects. The difference is that ColossusXT is on it’s own blockchain, and does not rely on the speed or congestion of a 3rd party blockchain. The Colossus Grid has a privacy focus and will market to companies, and individuals who would like to be more discreet when buying or selling resources by offering multiple levels of privacy protections.
Q: How do you guys want to achieve to be one of the leaders as a privacy coin?
A: Being a privacy coin leader is not our end game. Privacy features are just a small portion of our framework. The Colossus Grid will include privacy features, but a decentralized Supercomputer is what will set us apart and we intend to be leading this industry in the coming years as our vision, and development continue to grow and scale with technology.
Q: With multiple coins within this space, data storage and privacy, how do you plan to differentiate COLX from the rest? Any further partnerships planned?
A: The Colossus Grid will differentiate ColossusXT from coins within the privacy space. The ColossusXT blockchain will differentiate us from the DATA storage space. Combining these two features with the ability to buy and sell computing power to complete different computational tasks through a decentralized marketplace. We intend to involve more businesses and individuals within the community and will invite many companies to join in connecting the grid to utilize shared resources and reduce energy waste globally when the BETA is available.
Q: Has colossus grid had the best come up out of all crypto coins?
A: Possibly. ColossusXT will continue to “come up” as we approach the launch of the Colossus Grid network.
Q: How far have Colossus gone in the ATM integration
A: ColossusXT intends to and will play an important role in the mass adoption of cryptocurrencies. We already have an ongoing partnership with PolisPay which will enable use of COLX via master debit cards. Along with this established relationship, ColossusXT team is in touch with possible companies to use colx widely where these can only be disclosed upon mutual agreement.
Q: How does COLX intend to disrupt the computing industry through Grid Computing?
A: Using the Colossus Grid on the ColossusXT blockchain, strengthens the network. Computers sit idly by for huge portions of the day. Connecting to the Colossus Grid and contributing those idle resources can make use of all the computing power going to waste, and assist in advancing multiple technology sectors and solving issues. Reducing costs, waste, and increased speed in technology sectors such as scientific research, machine learning, cyber security, and making it possible for anyone with a desktop PC to contribute resources to the Colossus Grid and earn passive income.
Q: What kind of partnerships do you have planned and can you share any of them? :)
A: The ColossusXT team will announce partnerships when they are available. It’s important to finalize all information and create strong avenues of communication between partners ColossusXT works with in the future. We are currently speaking with many different exchanges, merchants, and discussing options within our technology sector for utilizing the Colossus Grid.
Q: Will shared Masternodes be offered by the COLX team? Or will there be any partnerships with something like StakingLab, StakeUnited, or SimplePosPool? StakingLab allows investors of any size to join their shared Masternodes, so any investor of any size can join. Is this a possibility in the future?
A: ColossusXT has already partnered with StakingLab. We also plan to implement shared Masternodes in the desktop wallet.
Q: How innovative is the Colossus Grid in the privacy coin space?
A: Most privacy coins are focused on being just a currency / form of payment. No other project is attempting to do what we are doing with a focus on user privacy.
Q: Hey guys do you think to integrated with some other plataforms like Bancor? I would like it!
A: ColossusXT is in touch with many exchange platforms, however, due to non disclosure agreements details cannot be shared until it is mutually decided with the partners. We will always be looking for new platforms to spread the use of colx in different parts of the world and crypto space.
Q: What is the reward system for the master node owners?
A: From block 388.800 onwards, block reward is 1200 colx and this is split based on masternode ownestaker ratio. This split is based on see-saw algorithm. With an increasing number of masternodes the see-saw algorithm disincentivizes the establishment of even more masternodes because it lowers their profitability. To be precise, as soon as more than 41.5% of the total COLX coin supply is locked in masternodes, more than 50% of the block reward will be distributed to regular staking nodes. As long as the amount of locked collateral funds is below the threshold of 41.5%, the see-saw algorithm ensure that running a masternode is financially more attractive than running a simple staking node, to compensate for the additional effort that a masternode requires in comparison to a simple staking node.Please refer to our whitepaper for more information.
Q: What other marketplaces has the COLX team been in contact with?
Thanks guys! Love the coin and staff
A: ColossusXT gets in touch for different platforms based on community request and also based on partnership requests received upon ColossusXT business team’s mutual agreement. Unfortunately, these possibilities cannot be shared until they are mutually agreed between the partners and ColossusXT team due to non disclosure agreements.
Q: What do you think about the new rules that will soon govern crypto interactions in the EU? they are against anonymous payments
A: Blockchain technology is just now starting to become clear to different governments.
ColossusXT's privacy features protect the end-user from oversharing personal information. As you are probably aware from the multiple emails you've received recently from many websites.
Privacy policies are always being updated and expanded upon. The use of privacy features with utility coins like ColossusXT should be a regular norm throughout blockchain. This movement is part is about decentralization as much as it is about improving technology.
While this news may have a role to play. I don't think it is THE role that will continuously be played as blockchain technology is implemented throughout the world.
Q: Any hints on the next big feature implementation you guys are working on? According to road map - really excited to hear more about the Shared MN and the scale of the marketplace!
A: Current work is focused on the privacy layer of Colossus Grid and completing the updated wallet interface.
Q: Why choose COLX, or should I say why should we believe in COLX becoming what you promise in the roadmap. What are you different from all the other privacy coins with block chain establishment already in effect?
A: ColossusXT is an environmentally friendly Proof of Stake, with Masternode technology that provide dual layers of protection from 51% attacks. It includes privacy features that protect the user while the utilize resources from the Colossus Grid. Some of the previous questions within this AMA may also answer this question.
Q: What tradeoffs do you have using the Colossus Grid versus the more typical distribution?
A: The advantage of supercomputers is that since data can move between processors rapidly, all of the processors can work together on the same tasks. Supercomputers are suited for highly-complex, real-time applications and simulations. However, supercomputers are very expensive to build and maintain, as they consist of a large array of top-of-the-line processors, fast memory, custom hardware, and expensive cooling systems. They also do not scale well, since their complexity makes it difficult to easily add more processors to such a precisely designed and finely tuned system.By contrast, the advantage of distributed systems (Like Colossus Grid) is that relative to supercomputers they are much less expensive. Many distributed systems make use of cheap, off-the-shelf computers for processors and memory, which only require minimal cooling costs. In addition, they are simpler to scale, as adding an additional processor to the system often consists of little more than connecting it to the network. However, unlike supercomputers, which send data short distances via sophisticated and highly optimized connections, distributed systems must move data from processor to processor over slower networks making them unsuitable for many real-time applications.
Q: Why should I choose Colossus instead of another 100,000 altcoins?
A: Many of these alt-coins are all very different projects. ColossusXT is the only Grid computing project with a focus on user privacy. We have instant transactions, and zero-fee transactions and ColossusXT is one of the very few coins to offer live support. Check out our Whitepaper!
Q: Will there be an option (in the future) to choose between an anonymous or public transaction?
A: Zerocoin is an evolution of the current coin mixing feature. Both allow an individual to decide how they would like to send their transactions.
Q: What exchange has highest volume for ColossusXT, and are there any plans for top exchanges soon ?
A: Currently Cryptopia carries the majority of ColossusXT volume. We are speaking with many different exchanges, and preparing requested documentation for different exchanges. ColossusXT intends to be traded on every major exchange globally.
Q: What is the TPS speed that colx blockchain achieves?
A: ColossusXT achieves between 65-67 TPS depending on network conditions currently.
Q: Plans on expanding the dev team?
A: As development funds allow it, the team will be expanded. Development costs are high for a unique product like ColossusXT, and a good majority of our budget is allocated to it.
Q: Can you explain what is and what are the full porpose of the COLOSSUSXT GRID PROJECT ?
A: Colossus Grid is explained in the whitepaper. The uses for grid computing and storage are vast, and we are only starting to scratch the surface on what this type of computing power can do. There is also a description within the formatting context within the AMA of the Colossus Grid.
Q: Is there mobile wallet for Android and iOS? If not, is there a roadmap?
A: There Android wallet is out of beta and on the Google PlayStore: iOS wallet is planned for development.
The roadmap can be found here: https://colossusxt.io/roadmap/
Q: Is ColossusXT planning on partnering up with other cryptocurrency projects? Such as: Bread and EQUAL.
A: ColossusXT plans on partnering with other crypto projects that make sense. We look for projects that can help alleviate some of our development work / provide quality of life upgrades to our investors so that we can focus on Colossus Grid development. When absolutely love it when the community comes to us with great projects to explore.
Q: Did you ever considered a coinburn? Don't you think a coin burn will increase COLX price and sustain mass adoption? Do you plan on keeping the price of COLX in a range so the potential big investors can invest in a not so much volatile project?
A**:** There are no plans to do a coinburn at this time. Please check out our section in the whitepaper about the supply.
Q: what is the next big exchange for colx to be listed ?
A: There are several exchanges that will be listing ColossusXT soon. Stay tuned for updates within the community as some have already been announced and future announcements.
  1. CryptalDash
  2. NextExchange
  3. CoinPulse
  4. CoinSwitch (Crowdfunding)
  5. Plaak (Crowdfunding)
Q: How will Colx compete with other privacy coins which claim to be better like Privacy?
A: ColossusXT is not competing with other privacy coins. ColossusXT will evolve into the Colossus Grid, which is built on the backbone of a privacy blockchain. In our vision, all these other privacy coins are competing for relevancy with ColossusXT. There are also similar responses to question that may hit on specifics.
Q: Does COLX have a finite number of coins like bitcoin?
A: No, ColossusXT is Proof of Stake. https://en.wikipedia.org/wiki/Proof-of-stake
Q: What are the advantages of COLX over other competitor coins (eg. ECA)?
A: The only similarities between ColossusXT and Electra is that we are both privacy blockchains. ColossusXT is very much an entirely different project that any other privacy coin in the blockchain world today. The Colossus Grid will be a huge advantage over any other privacy coin. Offering the ability for a desktop machine to rent power from others contributing to the Colossus Grid and perform and compute high level tasks.
Q: How do you feel about some countries frowning upon privacy coins and how do you plan to change their minds (and what do you plan to do about it?)
A: The ColossusXT team tries to view opinions from multiple perspectives so that we can understand each line of thinking. As blockchain technology becomes more widely adopted, so will the understanding of the importance of the privacy features within ColossusXT. Privacy is freedom.
Q: How do you see COLX in disrupting cloud gaming services such as PlayStation Now?
A: Cloud gaming services have not been discussed. Initial marketing of our private grid computing framework will be targeted at homes users, governments, and cyber security firms who may require more discretion / anonymity in their work.
Q: Since colx is a privacy coin and is known for its privacy in the transactions due to which lot of money laundering and scams could take place, would colx and its community be affected due to it? And if does then how could we try to prevent it?
A: ColossusXT intends to be known for the Colossus Grid. The Colossus Grid development will be moved up from Q1 2019 to Q3 2018 to reflect this message and prevent further miscommunication about what privacy means for the future of ColossusXT. Previous answers within this AMA may further elaborate on this question.
Q: When do you plan to list your coin on other "bigger" exchanges?
A: ColossusXT is speaking with many different exchanges. These things have many different factors. Exchanges decide on listing dates and we expect to see ColossusXT listed on larger exchanges as we approach the Colossus Grid Beta. The governance system can further assist in funding.
Q: What was the rationale behind naming your coin ColossusXT?
A: Colossus was a set of computers developed by British codebreakers in the years 1943–1945. XT symbolises ‘extended’ as the coin was forked from the original Cv2 coin.
Q: Can you give any details about the E Commerce Marketplace, and its progress?
A: The Ecommerce Marketplace is a project that will receive attention after our development pass on important privacy features for the grid. In general, our roadmap will be changing to put an emphasis on grid development.
Q: How will someone access the grid, and how will you monetize using the grid? Will there be an interface that charges COLX for time on the grid or data usage?
A: The Colossus Grid will be integrated within the ColossusXT wallet. Buying & Selling resources will happen within the wallet interface. You won't be able to charge for "time" on the grid, and have access to unlimited resources. The goal is to have users input what resources they need, and the price they are willing to pay. The Colossus Grid will then look for people selling resources at a value the buyer is willing to pay. Time may come into play based on which resources you are specifically asking for.
Q: Are there any plans to launch an official YouTube channel with instructional videos about basic use of the wallets and features of COLX? Most people are visually set and learn much faster about wallets when actually seeing it happen before they try themselves. This might attract people to ColossusXT and also teach people about basic use of blockchain and cryptocurrency wallets. I ask this because I see a lot of users on Discord and Telegram that are still learning and are asking a lot of real basic questions.
A: ColossusXT has an official YT account with instructional videos: https://www.youtube.com/channel/UCCmMLUSK4YoxKvrLoKJnzng
Q: What are the usp's of colx in comparing to other privacy coins?
A: Privacy coins are a dime a dozen. ColossusXT has different end goals than most privacy coins, and this cannot be stated enough. Our goal is not just to be another currency, but to build a sophisticated computing resource sharing architecture on top of the privacy blockchain.
Q: A new exchange will probably gain more liquidity for our coin. If you might choose 3 exchanges to get COLX listed, what would be your top 3?
A: ColossusXT intends to be listed on all major exchanges globally. :)
Q: What is the future of privacy coins? What will be the future colx userbase (beyond the first adopters and enthusiasts)?
A: The future of privacy is the same it has always been. Privacy is something each and everyone person owns, until they give it away to someone else. Who is in control of your privacy? You or another person or entity?The future of the ColossusXT user base will comprise of early adopters, enthusiast, computer science professionals, artificial intelligence, and computational linguistics professionals for which these users can utilize the Colossus Grid a wide range of needs.
Q: Will ColossusXT join more exchanges soon??
A: Yes. :)
Q: So when will Colossus put out lots of advertisement to the various social media sites to get better known? Like Youtube videos etc.
A: As we get closer to a product launch of the Colossus Grid, you’ll begin to see more advertisements, YouTubers, and interviews. We’re looking to also provide some presentations at blockchain conferences in 2018, and 2019.
Q: In your opinion, what are some of the issues holding COLX back from wider adoption? In that vein, what are some of the steps the team is considering to help address those issues?
A: One of the main issues that is holding ColossusXT back from a wider adoption is our endgame is very different from other privacy coins. The Colossus Grid. In order to address this issue, the ColossusXT team intends to have a Colossus Grid Beta out by the end of Q4 and we will move development of the Colossus Grid from Q1 2019 to Q3 2018.
Q: Or to see it from another perspective - what are some of the biggest issues with crypto-currency and how does COLX address those issues?
A: Biggest issue is that cryptocurrency is seen as a means to make quick money, what project is going to get the biggest “pump” of the week, and there is not enough focus on building blockchain technologies that solve problems or creating legitimate business use cases.
For the most part we believe the base of ColossusXT supporters see our end-game, and are willing to provide us with the time and support to complete our vision. The ColossusXT team keeps its head down and keeps pushing forward.
Q: I know it's still early in the development phase but can you give a little insight into what to look forward to regarding In-wallet voting and proposals system for the community? How much power will the community have regarding the direction COLX development takes in the future?
A: The budget and proposal system is detailed in the whitepaper. Masternode owners vote on and guide the development of ColossusXT by voting on proposals put forth by the community and business partners.
Our goal is to make this process as easy and accessible as possible to our community.
Q: Will there be an article explaining the significance of each partnership formed thus far?
A: Yes, the ColossusXT team will announce partners on social media, and community outlets. A detailed article of what partnerships mean will be available on our Medium page: https://medium.com/@colossusxt
Q: What potential output from the Grid is expected and what would it's use be?
For example, x teraflops which could process y solutions to protein folding in z time.
A: There are many uses for grid computing. A crypto enthusiast mining crypto, a cyber security professional cracking a password using brute force, or a scientist producing climate prediction models.
The resources available to put towards grid projects will be determined by the number of nodes sharing resources, and the amount of resources an individual is willing to purchase with COLX.
All individuals will not have access to infinite grid resources.
Q: Is there a paper wallet available?
A: Yes, see https://mycolxwallet.org
Q: Is there a possibility of implementing quantum computer measures in the future?
A: This is a great idea for potentially another project in the future. Currently this is not possible with the Colossus Grid. Instead of bits, which conventional computers use, a quantum computer uses quantum bits—known as qubits. In classical computing, a bit is a single piece of information that can exist in two states – 1 or 0. Quantum computing uses quantum bits, or 'qubits' instead. These are quantum systems with two states. However, unlike a usual bit, they can store much more information than just 1 or 0, because they can exist in any superposition of these values.
Q: Do you plan to do a coin burn?
A: No future coin burns are planned. Anything like this would go through a governance proposal and Masternode owners would vote on this. This is not anything we’ve seen within the community being discussed.
Q: Can I check the exact number of current COLX master node and COLX staking node?
A: Yes. You can view the Masternodes and the amount of ColossusXT (COLX) being staked by viewing the block explorer.
Block explorer: https://chainz.cryptoid.info/colx/#!extraction
Q: What incentive could we give a youtuber to do the BEST video of ColossusXT (COLX)?
A: We've been approached by several YouTubers. The best thing a YouTuber can do is understand what ColossusXT is, join the community, ask questions if there is something they don't understand.
The problem with many YouTubers is that some of them are just trying to get paid, they don't really care to provide context or research a project.
Disclaimer: This is not all YouTubers, but many.
Q: In which ways is the ColossusGrid different from other supercomputer / distributed computing projects out there. Golem comes to mind. Thanks!
A: The main difference is that we are focused on the end users privacy, and the types of users that we will be targeting will be those that need more discretion / anonymity in their work. We are building framework that will continue to push the boundaries of user privacy as it relates to grid computing.
Q: Can we please complete our roadmap ahead of schedule? I find most other coins that do this actually excell in terms of price and community members. Keep on top of the game :)
A: The Colossus XT roadmap is a very fluid document, and it is always evolving. Some items are moved up in priority, and others are moved back. The roadmap should not be thought of something that is set in stone.
Q: Does COLX have master nodes?
A: Yes. ColossusXT has masternodes.
Q: Have thought about providing a method to insert a form of payment in colx in any page that wants to use cryptocurrencies in a fast and simple way in order to masive adoption????
A: There is already this option.https://mycryptocheckout.com/coins/
Q: What do you think your community progress till now?
A: The community has grown greatly in the last 3 months. We’re very excited to go from 13 to 100 questions in our quarterly AMA. Discord, Telegram, and Twitter are growing everyday.
Q: I noticed on Roadmap: Coinomi and ahapeshift wallet integration. Can you tell me more about this? I am new in crypto and new ColX investor so I don't know much about this. Thanks and keep a good work.
A: Coinomi is a universal wallet. ColossusXT will have multiple wallet platforms available to it. Shapeshift allows you to switch one crypto directly for another without the use of a coupler (BTC).
Q: Is "A general-purpose decentralized marketplace" written in the whitepaper the same as "E-COMMERCE MARKETPLACE" written on the roadmap?
Please tell me about "A general-purpose decentralized marketplace" or "E-COMMERCE MARKETPLACE" in detail.
A: Details will be posted as we get closer to the marketplace. It will be similar to other marketplaces within blockchain. Stay tuned for more information by following us on Twitter.
Q: History has shown that feature-based technologies always get replaced by technologies with platforms that incorporate those features; what is colossius big picture?
A: The Colossus Grid. Which has been explained within this AMA in a few different ways.
Q: What are the main objectives for COLX team this year? Provide me 5 reason why COLX will survive in a long term perspective? Do you consider masternodes working in a private easy to setup wallet on a DEX network? Already big fan, have a nice day!
A: Getting into Q3 our main object is to get a working product of the Colossus Grid by the end of Q4.
  1. Community - Our community is growing everyday as knowledge about what we’re building grows. When the Colossus Grid is online we expect expansion to grow at a rapid pace as users connect to share resources.
  2. Team - The ColossusXT team will continue to grow. We are stewards of a great community and an amazing project. Providing a level of support currently unseen in many other projects through Discord. The team cohesion and activity within the community is a standard we intend to set within the blockchain communities.
  3. Features - ColossusXT and The Colossus Grid will have user friendly AI. We understand the difficulties when users first enter blockchain products. The confusion between keys, sending/receiving addresses, and understanding available features within. Guides will always be published for Windows/Mac/Linux with updates so that these features can be easily understood.
  4. Colossus Grid - The Colossus Grid answers real world problems, and provides multiple solutions while also reducing energy consumption.
  5. Use Case - Many of the 1000+ other coins on the market don’t have the current use-case that ColossusXT has, let alone the expansion of utility use-cases in multiple sectors.
Q: Will the whitepaper be available in Portuguese?
A: Yes. We will be adding some language bounties to the website in the future. Stay tuned.
Q: Notice in your white paper there are future plans for decentralised governance and masternode voting. While all that is great, how do you plan on mitigating malicious proposals from getting through by gaming the system (i.e. bot votes, multiple accounts, spam,etc)?
A: You cannot game the system. Masternode owners get 1 vote.
Q: Been a massive fan of this project since Dec last year, anyways what was the reason you guys thought of putting XT at the end of Colossus. :)
A: XT symbolizes ‘extended’ as the coin was forked from the original Cv2 coin.
Q: Do you plan a partnership within the banking industry to capitalize on such large amounts of money being moved continuously?
A: The focus will be on the Colossus Grid and Grid computing, with the option to participate in the financial sector of Blockchain through Polis Pay, and other partnerships that can be announced in the future.
Q: When will be COLX supported By The Ledger Wallet?
A: Integration with cold storage wallet is planned. I myself (PioyPioyPioy) have a Nano Ledger S and I love it!
Q: Where do you see yourself in five years?
A: The goal 5 years from now would be to be a leading competitor in cloud computing and storage. Providing government, private cybersecurity, and individuals with efficient solutions to Super-computing, cloud storage through Blockchain infrastructure. I would like to see hardware options of connecting to the grid to utilize resources after the Colossus Grid is online, and I think this can contribute to many use-case scenarios.
Q: How can I suggest business partnerships and strategic ideas etc to the ColossusXT team?
A: Join us in Discord. Members of the team here are active daily, you can also contact us at: [[email protected]](mailto:[email protected])
Q: A great project requires good funding. How do you plan to incorporate fund sourcing and management into the long-term planning of this project
A: Check out our governance section within the whitepaper. :)
Website: https://colossusxt.io
Whitepaper: https://colossuscoinxt.org/whitepape
Roadmap: https://colossuscoinxt.org/roadmap/
Follow ColossusXT on:
Twitter: https://twitter.com/colossuscoinxt
Facebook Page: https://www.facebook.com/ColossusCoin/
Telegram: https://web.telegram.org/#/im?p=s1245563208_12241980906364004453
Discord: https://discord.gg/WrnAPcx
Apply to join the team: https://docs.google.com/forms/d/1YcOoY6nyCZ6aggJNyMU-Y5me8_gLTHkuDY4SrQPRe-4/viewform?edit_requested=true
Contribute an idea: https://colossusxt.fider.io/
Q2 AMA Questions: https://www.reddit.com/ColossuscoinX/comments/8ppkxf/official_colossusxt_ama_q2/
Previous AMA: https://www.reddit.com/ColossuscoinX/comments/8bia7o/official_colossusxt_ama/
submitted by PioyPioyPioy to ColossuscoinX [link] [comments]

Best 3 New Bitcoin Mining Site 2020  1000 hash power free  Btc Earn Daily 10$ Live Payment Proof✅ BEST BOOTER +100GPBS PAYPAL AMAZON bitcoin INSTANT DOWN OVH NFO VPNS WEBS awesome bitcoin earning bot SUPER ❤️ The best faucet Bitcoin ‼️No Time limit 2019 testing my bitcoin mining botnet

Scroll down to content ☰ Home Get Started Exchange News Mining Trading Earn Follow Us. Home; Get Started; Exchange; News; Mining; Trading; Earn; Follow Us Interestingly, Bitcoin is no more the number one coin among cybercriminals. It is slow and requires high transaction fees. Monero has become very popular for its easy mining, and Dash is the best coin for ransomware authors. Here are the top 3 crypto mining botnets: 1) Smominru, the Biggest Mining Botnet to Date. Also referred to as MyKings, Smominru is a gigantic Monero-mining botnet ... Botnets are posing a serious threat to our online society. At the end of 2016, one such botnet caused a wave of destruction, knocking a lot of services offline. Many people don't realize there were qu Creating a Bitcoin-Mining Botnet at No Cost. Bitcoins are valuable, in large part because mining for bitcoins takes a lot of resources. At Black Hat a pair of researchers demonstrated that it's ... This Bitcoin Botnet is Vying to Be Future of Secure IoT Strong claims need strong proof, so when the founders of NeuroMesh described their bitcoin-based product as an “unhackable botnet ...

[index] [45919] [5148] [18395] [40099] [31364] [31326] [13915] [35147] [2523] [49401]

Best 3 New Bitcoin Mining Site 2020 1000 hash power free Btc Earn Daily 10$ Live Payment Proof✅

testing my bitcoin mining botnet ... free layer cloudflare ovh bypass nfo layer 7 deucalion botnet mirai qbot irc spots sale ddos hire hack method paypal bitcoin alipay cheap top best easy to pay ... Best Botnet & Stealer 2020 FUD All Browser Grabber BTC Stealer DEMO ... BTC Clicks paid Bitcoin to click advertisements - Duration: 2:01. Dan Watson 122 views. 2:01. Lucifer v.1.2 HTTP ... LINK: https://extremeguccistress.cc/ THIS IS THE BEST BOOTER AT THE MOMENT THIS HAVE A VPN SNIFFER AND MORE SOON HAVE 600GB POWER AND BOTNET+BOOTER+STRESSER AND ITS VERY SALE. Best Bitcoin mining is profitable because every new block and every validated transaction is rewarded with a predetermined sum in Bitcoin. In this video, we ... Best bitcoin mining site are a way for Bitcoin miners to pool their resources together and share their hashing power while splitting the reward equally according to the amount of shares they ...

#