monero_badcaca (OP)
Jr. Member
Offline
Activity: 154
Merit: 2
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 12, 2020, 08:39:39 AM |
|
Monero lost its reputation a very long time ago. Just imagine people having your IP addresses along with which sites you visited or where specifically you purchased something is quite frightening for those that thought they were dealing with a privacy based coin. I checked the link ( https://monero-badcaca.net/) it does not look good for Monero as a privacy coin and it does not look good for those 100 user details that will be published daily ![Shocked](https://bitcointalk.org/Smileys/default/shocked.gif) I'm posting the daily report in Monero topic until they start moderating it.
|
|
|
|
pedrillo0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 12, 2020, 08:56:10 AM |
|
TLDR: Monero was never a real privacy coin. Multiple problems that Ciphertrace is currently exploiting were reported to Monero project in 2016 and remain unfixed since. To draw attention to the issue I will publish transactions, IP addresses and porn preferences of 100 "lucky" Monero users every day.I have been logging Monero transactions for over a year now. Main reason why I decided to go public are blatant lies that there is nothing to worry about Chiphertrace and that Monero is private. If you are prepared to sit though an 8 hour lecture on how broken Monero is, you will see that even they admit it. However that's obviously a small percentage of people they sell Monero to. Have more questions? Have a look at the FAQ page on BADCACA website. Check today's 100 users who thought Monero is private on BADCACA!You're right! Monero has an old core! You need to improve yourself to achieve what your community expects. Before it is too late...
|
|
|
|
Sat0shisGhost
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 12, 2020, 03:13:21 PM Last edit: November 12, 2020, 03:54:00 PM by Sat0shisGhost |
|
I'll be the first to say it. BADCACA's data is not "just dumb FUD". I looked through the data and there's definitely some authentically traced transactions in there. I understand that he's disgruntled because people haven't taken him seriously for years (despite some of the stuff he has published being correct) but this is not the right way to go about publicizing this data. If your tansaction is waiting for a few minutes in the mempool, badcaca node got it. Why can you only catch transactions that were waiting for a few minutes in mempool? Admittedly I don't know a whole lot about dandelion but I would think you're just recording the first node to broadcast a TX here.
|
|
|
|
monero_badcaca (OP)
Jr. Member
Offline
Activity: 154
Merit: 2
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 12, 2020, 05:48:44 PM |
|
his is not the right way to go about publicizing this data.
Why not? They have already shown they are prepared to lie about it. Why can you only catch transactions that were waiting for a few minutes in mempool? Admittedly I don't know a whole lot about dandelion but I would think you're just recording the first node to broadcast a TX here.
You are confusing cause and effect here. Transaction sitting in node's mempool is caused by it being intercepted and then rebroadcast.
|
|
|
|
Sat0shisGhost
|
his is not the right way to go about publicizing this data.
Why not? They have already shown they are prepared to lie about it. ... You are confusing cause and effect here. Transaction sitting in node's mempool is caused by it being intercepted and then rebroadcast. With regards to indiscriminately publicizing the data, I worry that there might be some innocent people getting caught in the crossfire here (people who aren't sophisticated enough to evaluate your data and are simply trying to protect their privacy). I don't have any problem with publicly disclosing transactions related to certain criminal activities. Furthermore, I think publishing data on transactions that are in the public interest might draw attention to your research. But for all we know there are whistleblowers buying VPNs or domains, and you're putting out IP address data which could be used in combination with other methods to identify those people. With regards to the mempool: I think we might be talking about different mempools? I meant the public transaction mempool and I would assume that you don't have 100% coverage of these transactions: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2Fun9ZOVG.png&t=665&c=sxo4qYHZW1-4UA) Do you mean the like my local node's mempool? Are you saying if you intercept a transaction then it won't appear in the public tx mempool for a couple minutes?
|
|
|
|
monero_badcaca (OP)
Jr. Member
Offline
Activity: 154
Merit: 2
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 12, 2020, 06:57:05 PM |
|
But for all we know there are whistleblowers buying VPNs or domains, and you're putting out IP address data which could be used in combination with other methods to identify those people.
This argument can be very easily turned around. For people like that, isn't it better to know they have been exposed? Monero is perfectly happy for them to be tracked by Ciphertrace while reassuring them that all is fine. I think we might be talking about different mempools? I meant the public transaction mempool
There is no such thing as a public mempool on a p2p network level. What you are seeing on the website is a snapshot of one node's mempool. The way dandelion++ works is that the transaction will be put into the original node's mempool, broadcast in stem phase, and if the node doesn't see it again, it will be broadcast in fluff phase. The "not seeing it again" part is the cause of the delay.
|
|
|
|
Sat0shisGhost
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 12, 2020, 07:49:23 PM |
|
This argument can be very easily turned around. For people like that, isn't it better to know they have been exposed? Monero is perfectly happy for them to be tracked by Ciphertrace while reassuring them that all is fine.
You've convinced me that IP addresses for a significant chunk of Monero TXs have been compromised but right now that data is silo'd in ciphertrace/chainalysis/Fourteen Eyes servers (and yours). I realize you were able to code this up mostly on your own but I think you'd be surprised at how far behind the intelligence agencies of most countries are so some Turkish or Azeri or Libyan dissidents or something could easily be affected by this (that being said, it is possible ciphertrace is selling it to Turkey through Cellebrite). I think most people aren't knowledgeable enough to authenticate your data and are assuming it's FUD. If you want to quickly get the word out, an easy way might be to contact a reputable journalist and demonstrate it to them by revealing their own IP address (I'm happy to help you with this). There is no such thing as a public mempool on a p2p network level. What you are seeing on the website is a snapshot of one node's mempool. The way dandelion++ works is that the transaction will be put into the original node's mempool, broadcast in stem phase, and if the node doesn't see it again, it will be broadcast in fluff phase. The "not seeing it again" part is the cause of the delay.
Interesting thanks for the clarification. I'm not particularly familiar with dandelion++. Does the original node broadcast the transaction to multiple nodes in the stem phase or just to one other node? What determines when the fluff phase occurs?
|
|
|
|
electronicash
Legendary
Offline
Activity: 3178
Merit: 1054
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 12, 2020, 08:05:58 PM |
|
they waited this long to uncover the so called truth of monero?
so why the hell IRS will need someone to crack and finally trace monero transaction when they can hire Ciphertrace. and of all transactions the side only sees porn? are Ciphertrace porn lovers too? but thanks for the fud, because finally at least some of privacy concern users are going to grab some of XMR while it dips.
|
|
|
|
nullius
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 13, 2020, 05:55:37 AM |
|
Dandelion++, its strengths, and its limitations are of interest not only to Monero users. For I am surely not the only one who wishes to see Dandelion++ implemented in Bitcoin Core, if it can be done without opening mempool DOS vectors. (This was the reason for the rejection of BIP 156 for the inferior Dandelion; IIUC, the worst DOS concerns involve interactions between Dandelion (or Dandelion++) and Bitcoin features that don’t exist in Monero.) This is primarily a technical post; but first things first... Monero lost its reputation a very long time ago. Just imagine people having your IP addresses along with which sites you visited or where specifically you purchased something is quite frightening for those that thought they were dealing with a privacy based coin. I checked the link ( https://monero-badcaca.net/) it does not look good for Monero as a privacy coin and it does not look good for those 100 user details that will be published daily ![Shocked](https://bitcointalk.org/Smileys/default/shocked.gif) I'm posting the daily report in Monero topic until they start moderating it. Hey, JollyGood, you have a reputation for fighting spam and forum abuse. What do you think of badcaca’s overt bragging that he wants to use abusive tactics instead of technical arguments?
I need not remark on the security ignorance and technical ineptitude of the forum’s Timothy Leary. ![Roll Eyes](https://bitcointalk.org/Smileys/default/rolleyes.gif)
But for all we know there are whistleblowers buying VPNs or domains, and you're putting out IP address data which could be used in combination with other methods to identify those people.
This argument can be very easily turned around. For people like that, isn't it better to know they have been exposed? Monero is perfectly happy for them to be tracked by Ciphertrace while reassuring them that all is fine. Oh, spare us your liar’s false pretense of concern for the privacy of users! If you actually gave a damn about that, then you would disclose in detail what you claim to be doing so that (a) others could evaluate it on its technical merits, and (b) the alleged vulnerability (if any) could be fixed so as to protect privacy.Of course, that would presume that you actually have a low-resource way to break Dandelion++. (It does not even claim to protect against AS-level adversaries, let alone global adversaries.) At this point, I am pretty sure that you have only bullshit—such as your incessantly repeated deliberate conflation of network-layer attacks against Dandelion++, and Ciphertrace’s (much more credible) claim to have developed probabilistic transaction clustering from blockchain analysis. I do think that the Monero community should pay more heed to the latter; but those are completely different threat levels!
Interesting thanks for the clarification. I'm not particularly familiar with dandelion++. Does the original node broadcast the transaction to multiple nodes in the stem phase or just to one other node? What determines when the fluff phase occurs? I suggest reading the paper.I already answered this— twice:My first thought is, “Whose IP addresses are those supposed to be? The originating nodes’? Contra what it says in the badcaca FAQ, Dandelion++ would make it easy to mistake the IP address of the originating node.” It is exactly the type of technology which will make badcaca associate transactions with the wrong IP address.
I'll be the first to say it. BADCACA's data is not "just dumb FUD". I looked through the data and there's definitely some authentically traced transactions in there. A stopped clock is right at “some” moments of the day. Of course, if he lists a randomly selected peer IP that handled a transaction in the Dandelion++ stem phase, then that IP will sometimes be the actual originating peer. That is the point of “random”. “However, the protocol also ensures that the first relay node to broadcast is approximately uniformly selected among all relays that have received the message.” See below.
You are confusing cause and effect here. Transaction sitting in node's mempool is caused by it being intercepted and then rebroadcast. There is no such thing as a public mempool on a p2p network level. What you are seeing on the website is a snapshot of one node's mempool. The way dandelion++ works is that the transaction will be put into the original node's mempool, broadcast in stem phase, and if the node doesn't see it again, it will be broadcast in fluff phase. The "not seeing it again" part is the cause of the delay. Based on a reasonable inference of what you seem to be suggesting that you are trying to do: The Dandelion++ authors were way ahead of you. That is an admittedly low standard, because you don’t know what the hell you are doing. You are listing the IP addresses of random peers, exactly as I said!§4.4 at p. 17 of the Dandelion++ paper speaks thusly: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FU3uD6gS.png&t=665&c=VsRZjrSCNtAP0Q) If you claim to be defeating Dandelion++’s random timers, then please show your work with maths and stuff. (LOL, as if.) Transplanted from the Monero thread, with appropriate context restored to the internal quotation:Among other things, AES is broken!! ![Shocked](https://bitcointalk.org/Smileys/default/shocked.gif) Do you think Vincent Rijmen exploded with anger when AES was broken? No, he congratulated the authors. Say what!? When was AES broken? ![Roll Eyes](https://bitcointalk.org/Smileys/default/rolleyes.gif) (Just a guess: If you are talking about related-key cryptanalysis, then you are mentally retarded and you know nothing about cryptography.) I dearly wish that Monero were exactly as “broken” as AES!Yes it is, Monero community members have a tendency to spew uneducated bullshit. https://link.springer.com/chapter/10.1007%2F978-3-319-19962-7_3You idiot, the biclique attack does not mean that AES is “broken”. I guessed the related-key attack, because in some versions, that would have much lower time complexity (it just requires, um, related keys ).All that you need to do is to read the abstract of the paper that you cited. You don’t even need to hop over to Sci-Hub and enter the DOI ( https://doi.org/10.1007/978-3-319-19962-7_3) to read the full paper. Just at least read the abstract! Biclique attack is currently the only key-recovery attack on the full AES with a single key.... We have a biclique attack on each of the following AES versions: - AES-128 with time complexity 2126.13 and data complexity 256,
- AES-128 with time complexity 2126.01 and data complexity 272,
- AES-192 with time complexity 2189.91 and data complexity 248, and
- AES-256 with time complexity 2254.27 and data complexity 240.
Our results have the best time complexities among all the existing key-recovery attacks with data less than the entire code book. Yup: I dearly wish that Monero were exactly as “broken” as AES! Break in cryptography is anything faster than a brute force search; it doesn't matter that it takes down security from 2^128 to 2^126 (and is therefore only theoretical), it doesn't even matter if it is a known-plaintext key recovery attack. There is no need to call people names just because you don't know what you are talking about (like most people in Monero btw) There is a need to call you a liar (in addition to an idiot), when you are using the classic dishonest debate tactic of switching back and forth between two different senses of the same word—in this case, different senses (by orders of magnitude) of a cryptanalytical “break”. You claim to have broken Monero’s privacy in some significant, practical way. Your website’s FAQ insinuates that this is comparable to how AES is “broken”. For the third time: I dearly wish that Monero were exactly as “broken” as AES! By the way, I am not “in Monero”. I am a Bitcoiner and a lifelong privacy fanatic, who sometimes uses both Monero and Zcash. FYI. I am on this thread just because I hate stupidity. Note: I have not reviewed the code of Monero’s Dandelion++ implementation. But I am pretty sure that the people who wrote and reviewed that code would not have omitted the aforesaid random clocks, without which Dandelion++ would be trivial for any s’kiddie-tier retard to defeat. the memorylessness of the exponential clocks P.S., monero_badcaca, would you please apply your superb grasp of statistics to a gambling method, and gamble using my reflink? Thanks. Fallacies can be profitable!
|
|
|
|
nullius
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 13, 2020, 08:45:05 AM |
|
<snip>By the way, I am not “in Monero”. I am a Bitcoiner and a lifelong privacy fanatic, who sometimes uses both Monero and Zcash. FYI. I am on this thread just because I hate stupidity. <snip> I know investing can be difficult for some people, they invest more than they are willing to lose and can become emotionally involved in the projects they back. Maybe you should consider analyzing your position, frankly and without emotion, and move on. You meritless idiot, with your asinine assumptions and corrupt insinuations. It is none of your business, but for the record: At this particular moment, I have exactly 0.00000000 XMR. I don’t even know what the XMR market price is right now—nor do I care. I usually have more ZEC than I have XMR, and I have had rude comments made to me about that by some few less-intelligent members of the Monero community. Anyway, what I HoDL is Bitcoin—which is doing quite well, in case you did not notice. “There is only one Bitcoin,” as I have stated in either my signature or my personal text since I was at Newbie rank on this forum. My post offered significant technical arguments. Your reply suggests that you are only here to shill for your preferred shitcoin, and you are projecting your own greedy mindset onto others. Do you have any substantive, intelligent reply? Or do you need for me to ask you to translate “xитpoвыeбaнный” and apply it to yourself? P.S., newbie protip: As a matter of forum etiquette, please trim your quotes so as to provide adequate context, whilst focusing on the portion to which you replied. (Since you did not reply to anything that I said, that may not apply here.)
|
|
|
|
monero_badcaca (OP)
Jr. Member
Offline
Activity: 154
Merit: 2
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 13, 2020, 11:31:12 AM |
|
@nullius All the insults in the world won't make the IP leak disappear. Your own cult leaders admit it is possible : https://www.monerooutreach.org/breaking-monero/ Who are you to question them?Monero BADCACA sybil attack is still here, despite the claims that it has been fixed. If your tansaction is waiting for a few minutes in the mempool, badcaca node got it.Here is 100 Monero users who trusted in its privacy yesterday, are you on that list?:Txid | IP Address | City | Favourite porn | 9f6576085035c9b90442acc3bfe15290e78decc9b52f2c894451aa1bef646604 | 157.97.122.xxx | Iztacalco, Mexico | child | 8d4c0ffec535a5c87f5e0a94678c981f4815d1865749a3fc18c0af39f1f4dca1 | 85.248.227.xxx | Sala, Slovakia | incest | a3ee60c3d937d090b382d2ae037c8f97e1f5252ee6c6fc6d551eb9fea636b69d | 85.153.201.xxx | Istanbul, Turkey | incest | e6bd1f143c87a4df097bf8e6ac37d2f476bb3b1d7937ce2d52009c6dcdf5de55 | 185.245.84.xxx | Copenhagen, Denmark | incest | 7b83600e37f84fa8994a655b144017d686d686ec96642635916681dd9a4eaef2 | 185.93.182.xxx | Madrid, Spain | incest | 04114754f4285b95333f511cad48f7e04e5e44d908ba2e7068aaed3d92459b80 | 167.88.7.xxx | Chicago, USA | teen | 0267ce6913209441ed83e2cd3caa3441948a463700cf98e19af47372d27de384 | 5.180.62.xxx | Muenster, Germany | teen | 93c67e8194a0693643942675935ddcc8b9b3e90b248185aa42cb9d542161705a | 89.46.114.xxx | Los Angeles, USA | teen | 0e1a2507f69edc78ac1efb95bf031a3b7e7df0e187880f156830425551a4360c | 67.86.147.xxx | Sayreville, USA | teen | 2ef2ca68ff151a6a2c11a26a6006971c6e5f5858a7b89cb45a1f4365ed8bdfaa | 95.153.31.xxx | Washington, USA | interracial | 76734832b2aba9ece57417e9bfc641f6d19c54e80329f48f3e23c812a98e6b16 | 176.37.87.xxx | Kiev, Ukraine | interracial | bc84a07732020216fa5b734fe409913faa1ed9bc87b6ecee713fa07ff5505360 | 84.106.194.xxx | Heiloo, Netherlands | | cdf88b9fa25db08f8edd63ed6f0b92983f832982b185b706b3a263554d77221d | 76.28.178.xxx | Bellingham, USA | | f75594e4673a599bbb02d5db4e580f1d8ec56090ce5d268a96a0c5ba86779b5d | 76.10.138.xxx | Mississauga, Canada | | f059c10fdf47f4a4c7ce2f55f047c079541b05069c609a5c0f47f1088cff0d9c | 122.116.59.xxx | Taipei, Taiwan | | fb7a01e4745aa923667bb08e25f99fa2106e9224f3e3db36360259155087b6d2 | 77.35.132.xxx | Vladivostok, Russia | | 570aca820bd83282021157f20ef217b0ef7b64bceddfb99f8b7953ff0b39f547 | 47.190.133.xxx | Dallas, USA | | 693aacab1c4b96c6578cd85e4bc8b08a396e30367ed60f666ac9307694a16d2f | 204.27.63.xxx | Kansas City, USA | | d2779355371ed9863df5420a350a1b9b64d4e9a64d57ad4ea9a93d378ce6480e | 194.193.34.xxx | Canberra, Australia | | f0cf6f3a4b843cc72a677c90182c0c571c753042527a412060d7e8fe2be5a904 | 178.190.146.xxx | Graz, Austria | | 630eaa023c80e8cb943dcd489f5e62e0d4a3e68a9c3472a29942b4e5237190f3 | 80.100.47.xxx | Apeldoorn, Netherlands | | bcff575f9027370c9943f48b70fad7b71972767b32cf90a7c1989422b7030f01 | 86.48.96.xxx | Glostrup, Denmark | | 24b9a1237c378714b91597c6b0e172842f001045d28044d4fddfee028942f979 | 174.219.20.xxx | Chaska, USA | | 39fbcc79b0ea93c887833668097f6c562bea60e8fff398c12d40e2e9ae15a44d | 93.176.153.xxx | Madrid, Spain | | e3f24d067f6e354fc5b787a11dc16fd861ebf9e6f0bcee5dbaa32f85d3d851da | 37.201.168.xxx | Muenster, Germany | | c0a213e9ac915e0f907e88bc9c7f1f1ff9101841be586250406046fa4f338ea3 | 87.78.170.xxx | Dusseldorf, Germany | | 20a3e72a9b77af8f57b49a085258adb0eb1fde51527af2daadc0e9e264f517ea | 187.24.147.xxx | Cuiaba, Brazil | | ce896a091e43fdd5541d9bfd1dda15abefa3ab2f781b24ccd5b3ca0ad5130e46 | 46.32.53.xxx | Sonderborg, Denmark | | 2441435ee5400cd49281b8432bd63791ae453798f0036282bcbdf4dc0d574851 | 173.22.146.xxx | Columbia, USA | | ca62223a8f1b3f1b1e2d5daf35605d705d92d44aadd9d17f8a792438389c4e38 | 109.60.37.xxx | Zagreb, Croatia | | bfc2bcf5cea6709b3fe648a37e259bea656c453990db42ca5a4cdea1828f5012 | 185.203.122.xxx | Chennai, India | | 60711763986f839ba3eda23d4999fcc4eabbfd15a1e4b395e4ceb80e797e5182 | 86.43.118.xxx | Navan, Ireland | | 5ed0c7eb33b808c1f97b42879729a514709b38ae36bca9c22f8f12fd109bad26 | 167.88.23.xxx | Toronto, Canada | | 641500ae20653f8dfeeed15ac0066dd24685d5ac08740b7c6c2ddb6cd1b5a5df | 109.230.30.xxx | Bratislava, Slovakia | | 3d9cdba3dbccec1c7fa42c626f1e743718d0584fde3c6e7c985ab12e0e5d7faa | 83.84.57.xxx | Zwolle, Netherlands | | db2c3bdfaa0225ddb1564f16583e44f5d7466e8808aa57f2fc18919bf2da8f2e | 113.196.66.xxx | Taipei, Taiwan | | 5495efc1b68c5d5d3bca7043dd415dd8e9faa0dbd3e97dbf242557dbbce462f4 | 118.208.10.xxx | Woorim, Australia | | fe140f9280338dc2c779412a36c7dd0d31854a9710bbca76659137f1b2261412 | 98.200.198.xxx | Houston, USA | | 86d0aa647a8d8989aadc2a4cd1887d96efee2dc430088fa2dfdaa61c00abfad7 | 99.145.235.xxx | San Diego, USA | | 0649065885241559491b76abde62d0b543ef543af67a7c645d1e7ed2b9808561 | 58.111.232.xxx | Sydney, Australia | | 4dfc63cf74589ecaa2f4df98964a07b3835f48f07dfc0c638bbf112890c4bb93 | 111.70.8.xxx | Taipei, Taiwan | | 808d6b3b0e6917d8171e60b8cb94b35f274ff632d5b226510f9778746bb9b69d | 77.101.130.xxx | North Shields, United Kingdom | | 553043c957a894e4c00ff25c0f4d1978ce035fcce1192ff798722b5b78423311 | 192.226.150.xxx | Montreal, Canada | | 307ca8eea9f6e785f9da062c89f6d92cbf7ec327fb59cd3189047566e4cfd2f6 | 71.62.171.xxx | Arlington, USA | | 127d7511f5567862c9ddbf245ee64d5ceee8c9a0b37ed1ff0de0ea15154b60ea | 82.194.156.xxx | Salzburg, Austria | | dc66e308127c83e2703310923e74c26b8817fbe94b5887c5c5ee291b704cbd5a | 73.14.93.xxx | Parker, USA | | 327d76dfaf518922f730a15ee2197a693c8bc314898e3acc7175e11137bea98e | 73.77.178.xxx | Sugar Land, USA | | c61501d4074ffa2803cbbeb68354c32dfa2cea22bc8ba2760e9cb3be7b445ee0 | 24.78.33.xxx | Winnipeg, Canada | | 39fe22e13a41b959184c1742ca448f5a017841b2f86bec7bf6a3cd09352d0b61 | 94.224.216.xxx | Galmaarden, Belgium | | f914e9164f4fc02b561111ac206dae2a6c6d9c4cc72d6d0c0102e548368cce19 | 98.128.185.xxx | Stockholm, Sweden | | cc8f45e6f0cdeaf62bca6a90bfa1ff8354115e64abeba06e1b46956bc6d7cba9 | 59.61.100.xxx | Fuqing, China | | 1a8872ff244d763ae62269ae4954ce4de604447b2f951a2c450fccd4ea90d07b | 82.45.6.xxx | Birmingham, United Kingdom | | 3d82d78907109fa72a32ff3fba7f1b6d2f5d99d74a73921e851ba01387b07649 | 108.196.200.xxx | Cupertino, USA | | c83f2cd87afc65eecaf5ba1950728d1a2de3a2a8b0295ab93062bf893703ba4c | 108.168.103.xxx | Toronto, Canada | | 12baa70ed2b6952ee160866d37bc6e9e475a00dc6a4cd7a3479b6c1e4ee8ebb7 | 101.71.195.xxx | Hangzhou, China | | c471a1939bd1677ba05f6633e3377cdaa6c8054eaaea1a39324741f10c7de8b8 | 81.2.95.xxx | Bracknell, United Kingdom | | 0a14bdd49c4da0fb7941574144352e6030f257945b67054046d0eeb4405dd22a | 193.80.6.xxx | Kirchschlag, Austria | | df325f66dd6aaff2ecd55b76a8626935cc4e13eb210d89007d32d6aac705cac2 | 58.182.176.xxx | Singapore, Singapore | | c7a53b80b047b432c92334dfc9547e47ee4741cdb1e9e43d936b50fb8361ab01 | 75.82.205.xxx | Los Angeles, USA | | e0d44395471cdb72dc5762941a51f7298098f2070c69cbcc368a12a6df1157ae | 188.22.228.xxx | Maria Enzersdorf, Austria | | 74f7b922b64b82369b19e072aeb4ec04e0e4405c39e715d7ecd60495d052030f | 24.121.207.xxx | Flagstaff, USA | | 9a341b51b73735687caa6a24628f13bce775fc74b079f9c108afa564ef63a2db | 79.208.39.xxx | Allee, Germany | | 4454b6d848ded1a8986503624d90392951c004a56aef3a6a8efc4c7448668965 | 217.138.197.xxx | Milan, Italy | | 0da009e8b89c72af4cbcd339100eacba1d7e76fa8132a56466da489a9d661563 | 97.127.54.xxx | Plymouth, USA | | 48bf621547809eb1dea09b33cfcebcaeebdefc21987522e8baed4f1001e1b998 | 211.250.82.xxx | Seoul, Korea (Republic of) | | 75b0dd25559ee5f12ca5acfe58251d6de9761a3ce7098a7332db7d7092f5789f | 80.101.35.xxx | Bergen op Zoom, Netherlands | | b3201fdc3775f977922d264ee2656e1f126c5b1922228a1a7c88d3963933bfbb | 27.33.196.xxx | Sydney, Australia | | 1828621ab968917d88b156382738adbfa509c2e56ea4e5c66eee7bfec47c3334 | 24.8.128.xxx | Cherry Hill, USA | | 1233a7d1c3071deba49d6c5c4679bfcd2a7c37f5271d958b0ab26128196c4504 | 61.186.25.xxx | Haikou, China | | 8de20fa6b1033dab5570f77bbf51d16c59b2107414a1a5935335cee8d1393799 | 82.181.172.xxx | Vantaa, Finland | | 5b95f80d20a5b38b8644cb190a88178b12a03d1d1027d738f962e2c86445a5dc | 31.179.127.xxx | Krakow, Poland | | cd22bc505ba7ce64756d0aac867a3508d07a8b6731a17795ee6f0e0a60738277 | 31.179.127.xxx | Krakow, Poland | | 0b9c9df5e76b808670b7dc80ca596f260651d7220b186f9ed572a7cfdab39495 | 182.43.181.xxx | Dezhou, China | | 599552f3a5e2a2c8c798abb4cdc85e7325fedac0fd5561ee0d050361bb405db8 | 188.151.202.xxx | Stockholm, Sweden | | 56700d082889facea061e1c6d04e4daa74810b8e5c85ea1ccb477911e79cbdf5 | 164.70.176.xxx | Tokyo, Japan | | a74c9d54c3bca62f36f8c05235d17b581ff813201469dbb2e39f40bbb996539c | 164.70.176.xxx | Tokyo, Japan | | 84f35e11ee85134fd04beb85991610a71f4aa461955806dc8ac103be07dc7f05 | 209.93.61.xxx | London, United Kingdom | | 0f96b80d8f912b57c209e03f9b0b6588dfcba6575974b31e68090d137c1dafa4 | 86.106.90.xxx | Montreal, Canada | | 73e4a7454608b297b4999cbf44019ab627c539dfaaee481f86c3aa69bfb3fd03 | 172.116.56.xxx | Santa Monica, USA | | 8ef378d28af740a11173be3becd8efa879fe0ab79c8b6a51c331cc16a4fbe88a | 172.116.56.xxx | Santa Monica, USA | | ca3a648cd4b2b5614a21827ceddb446d6390afa016f6fdcf60ea0424f73163a9 | 213.250.21.xxx | Ljubljana, Slovenia | | 9a8e5203fb238c7f27ec455e6e5bc583bcce008ebb820380fec17fdfbb80a32c | 213.250.21.xxx | Ljubljana, Slovenia | | 71b621b2024b36c11291c0879827f424a5bbd70b4aa01fd16868252ab58f7964 | 37.24.1.xxx | Dusseldorf, Germany | | 3184d0195f19aa406898b7802da5b320245493dcb905d19768de6c8b7bfa4a27 | 95.165.104.xxx | Moscow, Russia | | 913784878993aa1cda4478d420a0c680c283b558f7a3bf63b41157a0c027a5e2 | 83.161.147.xxx | Almere Stad, Netherlands | | 9f9d9ee8cd0925642bcb60ce436cbe9863c356f961bc168811a1fa476c92e3d9 | 81.100.197.xxx | London, United Kingdom | | 9271301c103ab6c5cb5b05222504b7c7f5f70a7ab167f63f83770491f386ff2a | 81.100.197.xxx | London, United Kingdom | | 50ea42ba20ff19868dcd98704f6c3245d7569f2b253df30c9b7af9c925259c29 | 185.192.69.xxx | London, United Kingdom | | 49905a25937d00e3d6cbb7042528b8ba26b50681e2848a1df64506a98ccb2f8b | 24.168.121.xxx | New York City, USA | | 08b3ad7cb01586f050886fd2f1feff13b351cc079edf26fab44ec0506466fc5c | 66.177.85.xxx | Jacksonville, USA | | ff96c96e4f8b281e97a68db7507acafd1e4788d49ff9c50c191687b10a028f5f | 180.101.140.xxx | Suzhou, China | | c49bdde080d8ea6f45295ff83af4d1c2a838e34d851f55c9dd2924c14eadb7d7 | 180.101.140.xxx | Suzhou, China | | fe449d5d095e11300105e9b4ea0fbb5fbccc052276cb76d6d3bb955d13ffa8f8 | 85.241.106.xxx | Lisbon, Portugal | | 0507722d6991e5facbc85875eb3d7a9fd4aa67e1f3560fffe71677e89946b0f4 | 85.241.106.xxx | Lisbon, Portugal | | 8fc38f094116b8baec11e5dbe39c9fd0e3a52998222edf53a7a17115c66aa1cc | 47.149.111.xxx | San Bernardino, USA | | 93c740999e2a9cfb60563d12568c72db9b67cba15c3acbc3927806484e2c980f | 73.131.106.xxx | Charleston, USA | | 74f673e588a293eae4d27102158c5374e4b8aa02482fb371beadef4370c4f479 | 83.85.97.xxx | Rotterdam, Netherlands | | 76fd2e68f75cbb378500ca92f6784df73e2fad9484cef04b6afe4037309c6979 | 83.97.20.xxx | Bucharest, Romania | | 9a3cb0e18a5f62c26773e732405f35dd56055f273a940acbf90fc7db519b47ec | 94.224.210.xxx | Zaventem, Belgium | | a927a95f075e9388fea2a08c15f1377c405e8325b66da9c080467b9c872ac705 | 100.11.156.xxx | Philadelphia, USA | | 6e63ac6d8356b61ebdfa8ee3284b7df7e1c0830a4c4bdadbdcd8c04158b7b79e | 100.11.156.xxx | Philadelphia, USA | | 59db00b154cb8c87d4b9a16d3f2ab29843d502d9be5019f3db2a01a7ed863cd1 | 178.69.35.xxx | Saint Petersburg, Russia | | e445b4952e2dc4de67d5e189e598a82a7d57e7fbc1ea8d276a998638eb83cd6e | 58.111.133.xxx | Sydney, Australia | | 2849581c0009cfaa391465ee4ec2947cb04be31c4da3c407e067eacc90d32c9f | 58.111.133.xxx | Sydney, Australia | | 78b7e9978fdb856aa5f910e17bbb11fc572a20af0901b55c43250c28cd286c0c | 93.104.161.xxx | Hof, Germany | | 9ebe598745cda588294cbd1b69cb566abb562f85638c892e7ff710c19f45a028 | 93.104.161.xxx | Hof, Germany | | a1ead4e5c60d01fe6ac26b57e48017e7a5f9c3dc14948141eae7ae63967c1e07 | 75.82.185.xxx | Canoga Park, USA | | 89b826b7e4b28a768fe44cad9b49fa138a165662740c3494c4b8099091571b9e | 24.154.254.xxx | Pittsburgh, USA | | 6d777b558f1fc955c271fc90b0860fb5cfdbcebb464e58e41d0221e04952a236 | 80.24.57.xxx | Adeje, Spain | | ca0fac15621e184ae17b02b3bfce95b9148d7e66884016f8084a77a5719c5641 | 202.153.210.xxx | Wetherill Park, Australia | |
|
|
|
|
dragonvslinux
Legendary
Offline
Activity: 1680
Merit: 2213
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 13, 2020, 08:18:57 PM |
|
---
I'm looking forward to seeing some evidence behind these claims.
|
|
|
|
SirLancelot
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 13, 2020, 08:54:31 PM |
|
Obviously every single coin that became something will also have enemies as well, I am not saying it will be a great threat to that coin but it will happen one day or another. There are tons of people claiming bitcoin could be hacked as well, in reality they are talking about individual accounts that could take years with brute force and you could move out during that period, not the blockchain in itself as a whole unless you can get your hands on some quantum computer which doesn't even exist right now.
So, if you are successful enough you are going to have enemies, the reason why you have one could change but it is still going to be something that is permanent and they are going to do it over and over again. Ignore them because it just means you are good enough to bother others.
|
..Stake.com.. | | | ▄████████████████████████████████████▄ ██ ▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄ ██ ▄████▄ ██ ▀▀▀▀▀▀▀▀▀▀ ██████████ ▀▀▀▀▀▀▀▀▀▀ ██ ██████ ██ ██████████ ██ ██ ██████████ ██ ▀██▀ ██ ██ ██ ██████ ██ ██ ██ ██ ██ ██ ██████ ██ █████ ███ ██████ ██ ████▄ ██ ██ █████ ███ ████ ████ █████ ███ ████████ ██ ████ ████ ██████████ ████ ████ ████▀ ██ ██████████ ▄▄▄▄▄▄▄▄▄▄ ██████████ ██ ██ ▀▀▀▀▀▀▀▀▀▀ ██ ▀█████████▀ ▄████████████▄ ▀█████████▀ ▄▄▄▄▄▄▄▄▄▄▄▄███ ██ ██ ███▄▄▄▄▄▄▄▄▄▄▄▄ ██████████████████████████████████████████ | | | | | | ▄▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄ █ ▄▀▄ █▀▀█▀▄▄ █ █▀█ █ ▐ ▐▌ █ ▄██▄ █ ▌ █ █ ▄██████▄ █ ▌ ▐▌ █ ██████████ █ ▐ █ █ ▐██████████▌ █ ▐ ▐▌ █ ▀▀██████▀▀ █ ▌ █ █ ▄▄▄██▄▄▄ █ ▌▐▌ █ █▐ █ █ █▐▐▌ █ █▐█ ▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▀█ | | | | | | ▄▄█████████▄▄ ▄██▀▀▀▀█████▀▀▀▀██▄ ▄█▀ ▐█▌ ▀█▄ ██ ▐█▌ ██ ████▄ ▄█████▄ ▄████ ████████▄███████████▄████████ ███▀ █████████████ ▀███ ██ ███████████ ██ ▀█▄ █████████ ▄█▀ ▀█▄ ▄██▀▀▀▀▀▀▀██▄ ▄▄▄█▀ ▀███████ ███████▀ ▀█████▄ ▄█████▀ ▀▀▀███▄▄▄███▀▀▀ | | | ..PLAY NOW.. |
|
|
|
monero_badcaca (OP)
Jr. Member
Offline
Activity: 154
Merit: 2
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 14, 2020, 10:56:29 AM |
|
I'm looking forward to seeing some evidence behind these claims.
Simple. Use Monero, find out if you are on the list.
|
|
|
|
monero_badcaca (OP)
Jr. Member
Offline
Activity: 154
Merit: 2
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 14, 2020, 11:32:31 AM |
|
Monero BADCACA sybil attack is still here, despite the claims that it has been fixed. If your tansaction is waiting for a few minutes in the mempool, badcaca node got it.Here is 100 Monero users who trusted in its privacy yesterday, are you on that list?:Txid | IP Address | City | Favourite porn | 85551633c1bc7e356c4d872372e56288db7e04bed809b6c1d4fc3eea0c5112c4 | 62.182.99.xxx | New York City, USA | child | 7da0fd5433a3e1ca2b71948d809f03e58b0d358f717a8ac5a3ecff79d5bf3600 | 193.9.112.xxx | Prague, Czechia | incest | 06d590f74b372fae9fbf179cfbb8cd3ef554cb25e58b79e3d9efe6be4ca620d9 | 193.148.18.xxx | New York City, USA | incest | 16c769e0e5e8547b79dd355a295dc0535b61af53c7ce1b37e09b82e7892eb39c | 217.138.216.xxx | Berlin, Germany | teen | de302ae6ad4059e1dc6c6b6a087ba84cfa748a1b4f046a565b7cb2de33e81609 | 45.141.152.xxx | Frankfurt am Main, Germany | teen | 774d0453525b31895aaf3388993520ef75a69d39ff8df9599e2264ec3f6896ac | 38.142.119.xxx | Hicksville, USA | teen | fa95df3614bbd9eaa35c978fe28e0b213cc7a6f227ed9539de3690b6e8adc1dc | 84.115.201.xxx | Vienna, Austria | teen | 1266f4fa95f191a46176747c66f9f899633604e22907ea24af7b938c5ea1f2d7 | 176.37.87.xxx | Kiev, Ukraine | interracial | 857f44da38a1085c739055b618fa26f02e74f694ab8940208be2274685676be6 | 176.37.87.xxx | Kiev, Ukraine | interracial | 2b253b4e172a2e53880e5467befd99978d5c81ee749587e2714b348c47d96918 | 100.19.74.xxx | West Chester, USA | | c3bad2ddb1b0f4826222d44de56f8b081699e9d70f10e1c3bd947b8409f03d36 | 174.97.168.xxx | Neenah, USA | | 122d724f4d56199861b04380d3490fcb5367b5a32a2da6d9325254acae353daf | 50.34.54.xxx | Kirkland, USA | | 6942d1810aa0eca280ef14e6dca79ca9d1b6b3f1352622e7067d569d266aee00 | 162.232.25.xxx | North Olmsted, USA | | 5dbeb270048995634c282e8f7721bf47ddd2cc025630bdcba3f5e2e259c8b106 | 203.59.165.xxx | Perth, Australia | | 147b639923e4f7f3c5fea17a45928e5e58aff6823e83b5fdfbb271e18fee6b57 | 84.66.3.xxx | Bracknell, United Kingdom | | d9568ef35bd913ab98dfe76f0b8ddd324f1f915f23711e9ccd4c12a0c409511e | 98.209.232.xxx | Port Huron, USA | | 36f6c35fd0918d0cd0f9074d267048a8b02d52a0a6eb6063b203c2448826000b | 186.206.230.xxx | Belo Horizonte, Brazil | | bf62a6094abb5b9651422531f0e50b3706ae96c3d9d3a08bff13416bcc88dc96 | 83.161.147.xxx | Almere Stad, Netherlands | | 307a6364f3c9129e4dddafe404ca3b57ddeff8ee23cee96c64fe067a63dcf5a0 | 24.16.42.xxx | Kenmore, USA | | be25ba1cdbae231ed5c54dc4ed479f1d2a2624a5c5fdefe41ba96c510a809f35 | 109.90.2.xxx | Weckrieden, Germany | | 16b287f32fa8c78b5a1347d1f275f622072a484a8d72f4786de76eba5d68bf16 | 98.179.109.xxx | Surprise, USA | | 2141e85a516e661375ab576e9d364d953aaf7adf3f3bc54a23f2ca72e394b315 | 86.121.150.xxx | Voluntari, Romania | | 586b3541686246d8c388ff4989f7dc8415f03bca1edd2313bb22cdfcee34cc4e | 50.24.126.xxx | College Station, USA | | 34325a8d1950af588921a4f93748918733a6876916d6e5052590e8a57908afec | 70.184.66.xxx | Laguna Niguel, USA | | 863f96f6dae02bc356bfd5b180da702dde1cb2ce7bec495d9e754037e62d3f1d | 118.136.3.xxx | Jakarta, Indonesia | | 6d0e76c5037f3754ecfcf3e20f18602bfc4dca24da9d7f96661af486e8705d6c | 98.167.66.xxx | Las Vegas, USA | | 045640d1d54fbeddaf0ee41f106a753846b70d44052184864d293fef87720ea2 | 76.17.213.xxx | Plymouth, USA | | 92ef9383d54e74009cf7ad06d01d869a7ded747921c6b67875ea2b544a36e15c | 93.225.66.xxx | Dusseldorf, Germany | | d6738ea1084c87c77e11ed74f8b68d5f9cd21382057333bb7d1ec17b1f5a5103 | 137.27.174.xxx | Fort Worth, USA | | c70feab6d9dd31081586e8cef8d437b6f45c87a39d15e991e6b7dbfdeabb53c8 | 172.92.100.xxx | Port Angeles, USA | | bdf52ea3638b91d7116a7dbb12bca3b28d6d230ff4e736ca7a7d6d0b0156d5e7 | 46.126.49.xxx | Zurich, Switzerland | | 5a7ec154d0873be1fb4d19f8d34dd3917039507cd7a0f0ec9d548b3351e886aa | 83.84.57.xxx | Zwolle, Netherlands | | 4f83c2e06ebc614952e0cd2cbca2841a3355dce76d90adb920afab9922ca9400 | 31.10.131.xxx | Saint Moritz, Switzerland | | 98bebb28ea2dee894d3cb4c61dffbcdbf637bba67a277ddb6f67388aeb0fd8eb | 101.191.35.xxx | Moss Vale, Australia | | f6c8d5e94aae0ed05532602058f81df5175db9f058e393d7570af2cd92dab6b2 | 188.22.228.xxx | Maria Enzersdorf, Austria | | 8b7abdbf42979a50b11bc40cb86fc097d7e5cc59dbbd51bc3319e1285b99d6ce | 24.27.15.xxx | Austin, USA | | 0392f03bfd1f1be0cae833015c78e7ff5d98b79e4dab06f980a58153ed2e0e15 | 66.69.73.xxx | San Antonio, USA | | 2aa2ae9c08b08c481dd1bbc33d8a8dfb63d7e0af98ab404ab23eb11684bf258d | 171.212.244.xxx | Chengdu, China | | 764da1bd5980d21045674b893f31d9f424fa597d956adc0c704231d8b00c8175 | 68.58.61.xxx | Greenwood, USA | | 798be60a93baef50653f8dcf2a60fb4946ef0c148a3ce3bf60823c88b3da72b9 | 94.224.210.xxx | Zaventem, Belgium | | 5cbd8b476aa4f8d05163a56d7dd7d2138fe09d68444af6f6a2b08c41e0c20f2c | 93.219.91.xxx | Berlin, Germany | | 19870e8eaa2027519e71077e9609ef63017bdc9a23064b8fac27d95250e4095b | 222.190.61.xxx | Nanjing, China | | 95da9e3ba2fc675aebe1c57974781a4d23990cc39a42b98db3805d503b5ae892 | 23.16.102.xxx | Kelowna, Canada | | 6d9188bda87282e120fc2d34bccfcd3bc85463bd58e5361a6377aa5147eaf613 | 50.53.163.xxx | Beaverton, USA | | 290983fe878934156c48d4044b4db1bdd84982c06664898a175d625bc2216d35 | 96.225.78.xxx | Morristown, USA | | d717149b3e67f9e24aabb26215c5717c2020bd8c75fe6a2ae5549efc59a7249e | 50.83.209.xxx | Aurora, USA | | 53d5b46b16ce76aa86169606b4d6194c64c0570b630d7d66f2747221639533ce | 193.9.112.xxx | Prague, Czechia | | fc79b2f8fda8b939b755a6cc0525a4cc729ddb74351b68d62b6741e3697a8ed1 | 73.131.106.xxx | Charleston, USA | | 5d6df5f58cbbd1e7d8b9dfe28faca0fda62f67a7d02cc58ea6e9f90d3dff8dc9 | 177.76.111.xxx | Sao Paulo, Brazil | | ae784ddac2d9e37a77e2f5f6f4295aadc03ca235d80771bb0fc35cb579964cff | 60.241.48.xxx | Ryde, Australia | | 68d717fd8b53dd2b674911cc0aad560b7a4a09ded60855e3f8653e8bb6282875 | 181.164.203.xxx | Buenos Aires, Argentina | | aa313806ef7332ac52108aea8c8a1ffddcbb96a11f12deda3cbf18b18724abfa | 5.146.194.xxx | Aachen, Germany | | 624adc408834f87916fbbafe809e3d814a05ca94d372001b7f2163305bfb0890 | 117.171.166.xxx | Jiujiang, China | | b07f3cc89a0770ad4af63dc9d1090abe1ea2f0e3ab9bc82f5c9af377d8d2cceb | 186.18.253.xxx | Buenos Aires, Argentina | | aa6ca5e7d8e5ca759c0091c3b12b91bca39be6f46970b38df5a19a5bb61f40bc | 84.59.222.xxx | Isenburg, Germany | | 22f6a28c4245593da4999c462f483dfda8dd95561d86e83dbd2a52561abe1c7c | 99.129.102.xxx | Austin, USA | | 8a26b15a95c017e8a0ba02bd329515a44dfc9c6faaf188e0a206f435769a1e14 | 82.67.247.xxx | Raismes, France | | af5e721705958f720f2b4205ffcb8a4488ff918276341cb09014e1e952b5aed8 | 96.35.34.xxx | Town and Country, USA | | f420f9ab4520c7f7b9eb31607b6f88a6f0f327438296fa9de10b4446c6514fe5 | 208.104.194.xxx | Rock Hill, USA | | af1c26f97c7871ebb1f24f1f9597fa2e83c43379150f9122a3bb5754c30c9bc0 | 181.214.98.xxx | Chicago, USA | | e1c997a3e12bc531a1810904d755e914f74d7c10ca6f21ed73c227f80e1bffa7 | 69.244.168.xxx | Lansing, USA | | f2cea20f332c5df82e4e5be0a9a2bbb428f970e4a7ea8f365a4dac5794e9628a | 66.41.66.xxx | Minneapolis, USA | | 052d37cb4b20bfbf252ecd7bf7294acd350cc9bab45646bbd3f715b5c4bfc381 | 100.11.156.xxx | Philadelphia, USA | | e8c4a3428c44f4bf2adc785853e1c45d265ed674c2860b5c2213298814fb2e51 | 87.156.126.xxx | Laufach, Germany | | d4bff5245204e428d43309de4efb8c9f583324116a3b598f0702bb082e0a598c | 67.191.64.xxx | Pompano Beach, USA | | cde83f2b047a082f7ad5fd40491a286a7d0173838f5a655f8efa7ee1a14d22d7 | 84.202.208.xxx | Molde, Norway | | 0c557f9ccd9c74fe7449b0b6feedbd4d682978f52bce8ff225e9db63ca4e5c5f | 90.101.64.xxx | Lyon, France | | 97e050dd4af0317f194bb6a6fe451cf603cce174ca2f6f67cf3ba574c493fb5b | 185.203.122.xxx | Chennai, India | | 0992cd5c139a6449d1730a102474a70e571abd86151265b21835744a497b6c00 | 45.153.229.xxx | Kiev, Ukraine | | a0fc5cb7d4f92acce1478f09df0bb5e3750cb3d414186cf6c7704bcebe1f0e66 | 65.30.222.xxx | New Berlin, USA | | 98b31f0016577a0bfbc38d14e5b3e4083b1dbf75a04eac8ed0f3412129568479 | 82.69.110.xxx | Maidenhead, United Kingdom | | 0347dacd5a5782383569f3e214a63d094dddcc227ca34e500bc00d3f5389cf10 | 82.69.110.xxx | Maidenhead, United Kingdom | | 3b3fcca3519f3b00b4919b1d4934b43824c853d8fb96098e528299ce535c4e17 | 68.203.5.xxx | Austin, USA | | 06c459ab93345357dfac1b6e58c55dc8decae7555f2bef70d4d94436eb0744e7 | 209.93.61.xxx | London, United Kingdom | | b641499979ed8ac2eab3f25c80dd77f18fd88bbecd98c474527b639fad272fb9 | 50.220.121.xxx | Naperville, USA | | 5713f83710a20f6e2f66e56437ae24aaa43e47506335606687c98f178b260544 | 50.220.121.xxx | Naperville, USA | | 311f84b6504ed60948259c2516f932d6db7b611f16467d7441d985794c835eb8 | 77.181.41.xxx | Ludwigshafen, Germany | | 8ee2909eb384cb8397494e01ddd3008054f5e2a00e1e52a24f84e3f62fac9a74 | 77.181.41.xxx | Ludwigshafen, Germany | | abe8346294a621996b6ce96bc97078ea760ce58107ab6e58f2a28cc35e20d2eb | 98.128.185.xxx | Stockholm, Sweden | | 3183dfee325ec0d98153eb339bcd3180cf10955c7b586f016004ed526c9337ad | 84.1.12.xxx | Budapest, Hungary | | b1f88fbd790fe3089b8b3a45f83886043ebc3c5487399d9b5f6ff5e6cb15e1a3 | 172.116.56.xxx | Santa Monica, USA | | 0a1a4286091154da6876877c5fca3f42c411f683b12e774a95157de16c4abc70 | 23.240.231.xxx | Los Angeles, USA | | e72445c22f18fceac11d4b588589102cbb63306bc7dadc2709d3b60c1ea81da3 | 23.240.231.xxx | Los Angeles, USA | | f19d4ce0de96c99a3b46f95746e330cbea2348a5fc2bb9940c5b3371ecab87c7 | 100.15.106.xxx | Washington, USA | | 96edc8730f22844dd7ca80709358b1efa6027357ebe7602082d33bfc30158863 | 82.194.156.xxx | Salzburg, Austria | | 1c7c102ffc34f0b8079b54f0e59f05cdd8523aeea23fd75969edffc28d31e675 | 93.105.187.xxx | Warsaw, Poland | | a7b73055abd433a56c6b060259033334c97a2da1abb71f39629bce224b0d9838 | 68.53.174.xxx | Brentwood, USA | | 1f0f3d04fcda49280517612860c7f6b13f1ddbd8462b86301b9e8b1b3df28ecd | 68.53.174.xxx | Brentwood, USA | | 118553d48e0eddf66c417d5f918528b6c47f3aa921cb7598c568f3aeadf198be | 80.182.39.xxx | Modena, Italy | | 23944e4bf9f3a17df9537b7aa305b96b101402172f40f966e07d555edb8b0b10 | 109.230.30.xxx | Bratislava, Slovakia | | b45629f313db5f362f1482e82ec63a518cfe9ebaed4399a6270f5e605e87bbe1 | 176.250.221.xxx | Edinburgh, United Kingdom | | 1da35a277faa75f6836af7bc0e931c028d81f69154280bd060d32aaa2f0499cd | 72.83.32.xxx | Arlington, USA | | c100f6668549e216c740e770632e4eb4832b849d3b52c4c528ecbd086cb77545 | 86.170.46.xxx | Leeds, United Kingdom | | 4db83cc955e8304b0548b3f5c763aad02401d77f91463e6631c231bc9fb39dca | 104.52.169.xxx | Jackson, USA | | d04a4af9dc8239d8239a7ea5c8096e914a84c2b99798e49584a9f8f49b96ac8a | 98.253.193.xxx | Indianapolis, USA | | d6c3710d323ff806a1e7e16584be0abc1f456122bb60ab71593d846057194dad | 85.241.106.xxx | Lisbon, Portugal | | 93fb6a4e74297d436a0e573a7b84c133ec15eccc7df63adc1500ec2839efa341 | 75.82.205.xxx | Los Angeles, USA | | 4a845a77bcf184c383235b57d09ddaf491dfb15e78906869aaedefe9f9e8894b | 75.82.205.xxx | Los Angeles, USA | | 9b115c1938169cd0911e0f59b8d27abd884c7a3f4ae89274d88c7d836ec5ab4b | 190.19.49.xxx | Buenos Aires, Argentina | | 4de66ac15bda45445da35453a4cf488e2faef454df40b52fc0c9a2652f43b06d | 202.153.210.xxx | Wetherill Park, Australia | | 7f8d495e6624015162132e6572503cd7245fef0c809619742fc06362dc9c7413 | 58.182.176.xxx | Singapore, Singapore | | 89c1e2c55018461b3870d259a34b823e8696550802eca1d5f7b3eb1279aef2b2 | 58.182.176.xxx | Singapore, Singapore | | f4f60b09bad6c070a88601c1d9f11521640d8a338967a7608c0dd1e648984a4e | 58.182.176.xxx | Singapore, Singapore | | 0b3dc4b3b9d14a91416269c15f6c8a3f7cb5c5434a511392a903f8793be03ee0 | 198.84.175.xxx | Chatham, Canada | | 5c8cd46fa7437fda96c41acf26976a2fd39afc1b1d1c275a1a23faa93404a566 | 99.253.64.xxx | Hamilton, Canada | | 4a41267f6a2847050aa2058287f520f505109a698c23a9c0d3aa8b4bc68720ae | 101.81.250.xxx | Shanghai, China | | 702fd823ecddd7dcfd95332d2ac09162345c9a18d284375828b2eb8486c64f5f | 213.250.21.xxx | Ljubljana, Slovenia | | 9fc5e70f85c32a2a955d70d40245657fddd09e183ee560a654d81c70c546420d | 125.187.63.xxx | Seoul, Korea (Republic of) | | aa769f4a45f581e6c7a6356b254e0c8bce4b70e6b4bdb0f8992a120487d6cea9 | 76.91.24.xxx | Los Angeles, USA | |
|
|
|
|
nullius
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 14, 2020, 02:15:17 PM |
|
I'm looking forward to seeing some evidence behind these claims.
Simple. Use Monero, find out if you are on the list. dragonvslinux, I think that by now it’s obvious that badcaca has nothing except s’kiddie-tier bragging, bluffing, and spamming the shit out of this forum with long lists of txids, randomly selected peer IPs, and annotations of what are probably just his own porn fantasies. Proof: Simple. Ask him some technical questions, find out if he has an answer.I suggest reading the paper.[...] You are confusing cause and effect here. Transaction sitting in node's mempool is caused by it being intercepted and then rebroadcast. There is no such thing as a public mempool on a p2p network level. What you are seeing on the website is a snapshot of one node's mempool. The way dandelion++ works is that the transaction will be put into the original node's mempool, broadcast in stem phase, and if the node doesn't see it again, it will be broadcast in fluff phase. The "not seeing it again" part is the cause of the delay. Based on a reasonable inference of what you seem to be suggesting that you are trying to do: The Dandelion++ authors were way ahead of you. That is an admittedly low standard, because you don’t know what the hell you are doing. You are listing the IP addresses of random peers, exactly as I said!§4.4 at p. 17 of the Dandelion++ paper speaks thusly: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FU3uD6gS.png&t=665&c=VsRZjrSCNtAP0Q) If you claim to be defeating Dandelion++’s random timers, then please show your work with maths and stuff. (LOL, as if.)
|
|
|
|
monero_badcaca (OP)
Jr. Member
Offline
Activity: 154
Merit: 2
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 15, 2020, 01:19:35 PM |
|
Monero BADCACA sybil attack is still here, despite the claims that it has been fixed. If your tansaction is waiting for a few minutes in the mempool, badcaca node got it.Here is 100 Monero users who trusted in its privacy yesterday, are you on that list?:Txid | IP Address | City | Favourite porn | a8f23d5c9e61486548cefd086f3ac1ac38252cd9c84ae323de11cedc8060ff6b | 139.28.217.xxx | Amsterdam, Netherlands | child | 79623827ad311b9efc927e45901a36eb26c5dc22005aea6b03e45a6ecd690758 | 92.119.17.xxx | Atlanta, USA | incest | 7d1919e1e9a6d3b1a43edcffb52b65e1b517448e1bfd1c5e5a76b4af337ec74c | 86.106.121.xxx | New York City, USA | incest | 035de190ad091e4b6c66911c93c1189f12774b0ae8b9a3f61eefa39c010350a6 | 94.134.102.xxx | Hanover, Germany | incest | 5bca100ae27f2135d400752af90fef85e91024f70159f41ed3ff0619fdb82e38 | 94.134.102.xxx | Hanover, Germany | incest | a6de6dd1c382787cdb7f24ac6172ed4ce891c7426680c9f0d6b806bc105e6530 | 217.138.213.xxx | Montreal, Canada | teen | 9bde3c37c95d98146bb0e16755ceb31cd95c046a9af2b8f93566d4b8ab458939 | 174.94.155.xxx | Montreal, Canada | teen | ad15417d261b7cef86200c52490bedf0f1aa85e7c1debd1d3fca0cf3f8547d53 | 174.94.155.xxx | Montreal, Canada | teen | 77f44b4cd4bad2d00807a5d0fb12df12ba61c784ef54f9c31556b8f0c944dcf6 | 152.89.160.xxx | Belgrade, Serbia | interracial | 5f5c21941aafead6a85402af7d89ee3d762fad980dd0528992578a92d0f4e30d | 121.99.242.xxx | Auckland, New Zealand | | 05b3b3ef587cb0c2186b0c0ce4d0bb289c9c5e6277fc884d21734976b70f9c84 | 75.177.141.xxx | Apex, USA | | d54ab6c41a57073c239fdbfbef7924a20ff3d838e23b3127b6abf12376b094b8 | 83.85.97.xxx | Rotterdam, Netherlands | | 4baac58be5cccf8417d2bd0744acc78d5507bd3bfcafbec159e6b15a9b4496c0 | 73.98.209.xxx | Salt Lake City, USA | | 820e1b79c1547f4987baf8579e38b95a2d644a65584e8f5f236844a0650661e1 | 59.27.10.xxx | Seoul, Korea (Republic of) | | 50d5dffc87e10b54ffae1ce95d4eb9191c0eed6a60d233738e3eafbcd4f0bac5 | 109.230.30.xxx | Bratislava, Slovakia | | 52e1a95e72c12ed4d50af87fbd43fe343a67ad88257d61efb3b1d6cb94aff3b7 | 84.118.170.xxx | Siegen, Germany | | a279bf76d81180148d896177250f64cac259c0404e289b92388288b501611bcd | 205.206.248.xxx | Calgary, Canada | | ec1856f9730a140c4c436003bf47618b148a47080a65f06b313892499912c4a4 | 98.200.198.xxx | Houston, USA | | 0b7f9c3d35f367d279669a4469d50be4a28f08ed291cfc5ee25a485a7f095c14 | 66.25.142.xxx | Harker Heights, USA | | d053eb3712686f9adb6e2eb3b5f15f3e97c6c3bf7585ed2553e63282cab60014 | 203.219.241.xxx | Melbourne, Australia | | 1ee5484e3172771a2305f40896e0254bb9420467bf7a56eeeb058ae06d69f64e | 68.53.174.xxx | Brentwood, USA | | 0328f869f8369f9ae3c9a179ffd40b965efea526cb347e88a087dfc0942fcb1a | 176.23.22.xxx | Copenhagen, Denmark | | 1049a065b4f11b5b16c952b3d23355e125ea077a670da5a842eacc50389c24be | 70.106.218.xxx | Arlington, USA | | 1d581d1009bbbb0584aee79fa5e0e4362aa122f612e8769c2cdb75df3ed6caf7 | 84.202.208.xxx | Molde, Norway | | 3fa9409b742c7e066aad2f619c758e20d31ac168624be90f56a04adce33ffcd4 | 71.238.235.xxx | Little Rock, USA | | 077565a486f496ccbe52bd51e78dc349f842a5e830d527399e86d141c5624457 | 151.226.73.xxx | Daresbury, United Kingdom | | f08886ca2c52d71e88332e15b4b8e4d1ca84ce8a131f92a5eb48e36dd7b6a9ae | 23.115.236.xxx | Stone Mountain, USA | | 4e5af414dba9d0cab5c8e46d19e2eb039cde99ca879ba12ada127495e4884642 | 145.255.180.xxx | Karasu, Kazakhstan | | 1b6b390b6096e2ca374ea6077ffcee7b717c49ca6e3f32f6dad539359fc81182 | 66.189.42.xxx | Worcester, USA | | e6ee4ace97f08f265b79165bbdcee3a4857791a685c085800e657a90c19c7e65 | 37.24.207.xxx | Monchengladbach, Germany | | c1f80fdcc4939f26626c34247b9d1a5fcfe0325953dcdd3e1719d01edd903ccd | 85.238.103.xxx | Odessa, Ukraine | | 6a86cebedb564b4721b53863f51b696d16bdaf4eb7c77b5f1a7b7b74fd67301a | 136.56.52.xxx | Morrisville, USA | | 776f263064b745cfbc3361d617d8f029f72d5352433928af6bb62ab31628c071 | 118.136.3.xxx | Jakarta, Indonesia | | c60eed69688c671d7fd16551b90bc70161c0da333141a66d87cc8c0a27244f1d | 37.4.233.xxx | Berlin, Germany | | 43451f8e8e34a8653952fe2cb9ef35dc6629b6232733d4e3435f96d7dec8a96b | 50.39.99.xxx | Beaverton, USA | | 8578ccdb5bf2439907b3ce6117a16ec09f2f56f6ecc1301cfc67835d20f8012d | 75.142.98.xxx | Long Beach, USA | | 0fe1beb20228221a2048b7afb7fef6b775605036263198154b0cbb33f348716a | 173.216.88.xxx | Batesville, USA | | 9c1d42ff54df5ae239badab3d75246cf53b0492a7740ef78143b14260ca8db70 | 100.11.156.xxx | Philadelphia, USA | | 6517ba5105551208897142aad3971e82ac3fde52728b178e063394555777d284 | 2.204.231.xxx | Berlin, Germany | | 8f9593542cf038480f9bb878c1640c7d7ceb2265ea3d7af3e925d1623242c78a | 89.179.124.xxx | Moscow, Russia | | e299069abce252ce8e91a01b20218a5794fb9d80ea7f3f77014a3473f2502f1b | 97.121.165.xxx | Colorado Springs, USA | | 5967dfe4b96c120f07c6805b496e2bfd79a3f8bce5a163ed21351f0a735a265b | 85.203.45.xxx | Amsterdam, Netherlands | | 978ca2151807c8945027470a4edfe4d04bbc8a7acef2756aa2a6d0a7e864afab | 203.129.54.xxx | Subiaco, Australia | | 4dd6afb68bff4a9571dfa52672290d6fd5a8cddc0d6bd9641c29d9f536434f6b | 108.173.237.xxx | Edmonton, Canada | | 16918c7367fdbadcd25f11c3799f783fff71067228a293c16102a8004d133d9e | 67.240.190.xxx | Portland, USA | | af6765b523810d66cc7fb50646c884818dd2bdfaf79b294031f8f5bfbf434561 | 68.203.5.xxx | Austin, USA | | 588ffd96e06206b778a43706d7ceaa76306bd6eb1df848b4f1dc06e9c532198e | 98.155.248.xxx | Lahaina, USA | | f983187219de0db7d34c293725b1f1aef407a2e0db68b071dbb7167b4bad999a | 47.20.125.xxx | Brooklyn, USA | | 624063927318e2b626119a7f29b516d5a962ccdc8b7adb59b4f2011c24b22567 | 68.0.147.xxx | Tucson, USA | | 5fc6f86e56bffeb6cc428f580057a00363fd9ce865b8a7d1395618361fe9e8f0 | 24.121.207.xxx | Flagstaff, USA | | 4a752beb0e7d1b3aae4cb9ed9104a9e59337a03e5ccbd9d97ddec63600a506ae | 99.145.235.xxx | San Diego, USA | | 550bf062f21077b2b880cf7ee487ea1307929a427f17dc407bca13eb582ae9a9 | 178.112.11.xxx | Maria Enzersdorf, Austria | | 87c3733df0fe0a3b58611e3e6d4f4c345e9642170026d0b508eeea7095f24778 | 217.225.193.xxx | Munich, Germany | | b3a0f3c6f8208d3bace25ca737b44f7686534035a4c4820d2b3bf28c837bb33c | 87.99.38.xxx | Wroclaw, Poland | | 2e451d29a6efa3a7598e67c581e162561c26b4bf6bac45f89f056c1f889489c0 | 24.201.220.xxx | Quebec, Canada | | ec0a9539bdc7f3f2c2750b658ee3d5dfbd99273e2407ba293d1b3717b5bdbe0e | 124.190.195.xxx | Sydney, Australia | | aeff2be72b2636b3ed9dde54b6d38e48f285a2d3a36370a1ca0704054714cb7a | 113.100.164.xxx | Meizhou, China | | 966ada7689f58b735a0a1498ad4264f223c99e08a4cbf4628db8422e886897cf | 81.250.251.xxx | Charleville-Mezieres, France | | 96abca14956ea33b8bbd7eaef056adcc1dd8988792f3dd78b0355340b8d4badc | 60.241.48.xxx | Ryde, Australia | | 00616c7fa4d46fec6cbcf5be91856915d09cd0e888fa3415bc4502fbf43221f5 | 95.223.75.xxx | Frankfurt am Main, Germany | | 12eda355f3b416bdfbbdb6fd8d23fdb59ec103120c41b6942fc506983f70bb14 | 190.88.176.xxx | Willemstad, Curacao | | d4ff2830ea3526fd0b1bc1c89509c1004cfe196415107bcedc317bc8ac7e633f | 47.219.23.xxx | Tyler, USA | | 9b6fa6478b492b3d3229851d03dc4df060372091ac79faa0be73f516a611a5e2 | 76.91.24.xxx | Los Angeles, USA | | 752bf7108d259d7e61d9e2fb3cf08edeff15f887b1bed86a477d7b0844963b60 | 58.176.248.xxx | Hong Kong, Hong Kong | | 7d3e29d81e1f39a7818094fac67cdb9839e720fcf44dbf773f462daae6f9644c | 95.103.133.xxx | Zilina, Slovakia | | 2ec2ace87739ceae1022326e592666d1e11eaf1471e4c09db8dfa08862f9bcfc | 68.103.245.xxx | Wichita, USA | | b119832c515df86eaf5ec8aee47b867cb806e079d15d3d9d2bfec6fa8d6b0226 | 135.23.93.xxx | Ottawa, Canada | | c89adbc8260723f807e1fad7a94c618ff9a687ba0d4dc1e78c20be919a1fe78c | 86.121.150.xxx | Voluntari, Romania | | e0488bc6399263ff895f30f233c13fe72802ad35f4a76e82f31405fd6ca0b7b2 | 90.91.212.xxx | Paris, France | | eade72340933dfff7a53cf0387e9fba9164467e80e63ebab1196e8148f83f0cd | 114.34.166.xxx | Taipei, Taiwan | | b7403277da95e20edb58ff090ae10f3f3ba5b5040758d0acc08bd87ca0dac78a | 162.104.170.xxx | Columbia, USA | | 9858b2b523c2b580067accb8c5d3842a3745e30effbadb8be37b92ef2a764d0d | 82.64.20.xxx | Agonac, France | | 2cf1b1133ffdfbe67e04ee56c930565c5361950975acc999156dfb1d01ae68ca | 98.253.193.xxx | Indianapolis, USA | | 9b599cc8251d172652e55672818cd109e759bf41113d9d017dda84ce048f90d2 | 70.127.119.xxx | Tampa, USA | | 00b63a086b6640a5ad999ba3c1e9ada957e077cb0a7123addc7b6bc16ca8fdeb | 70.127.119.xxx | Tampa, USA | | 585e39162f0fb9c4115a09b451b9e142670242eb52ecf6cf91b9c4cf9db6d99c | 93.104.161.xxx | Hof, Germany | | bb3fdf36db23268e0d0304e540ccab36d77be57b1e6ee8dc53f3c5448243513d | 74.98.228.xxx | Pittsburgh, USA | | c06b86b8f31c1f44522dacc37d633ef037001608faaf43fc30b26a36c8bb2d1c | 76.121.136.xxx | Seattle, USA | | 33ec064483586fb1d5363fb5ae4d17fad6ae42b3ca5e1c22e8639428d1a6c40b | 76.121.136.xxx | Seattle, USA | | 32d3bdd8a1ec7f84812474f920a2ebb6f3ee646fe1ff33833b12b1fed252a80b | 65.60.253.xxx | Columbus, USA | | 94fef72e529a61e7796f524d891053ba7203338375d09e003207d5edb2c6f71c | 65.60.253.xxx | Columbus, USA | | 3d7bf863b1132c5bbf68fde1aa54b3b7f7c68e603d54d5d28d61be5bc653a10e | 120.148.37.xxx | Saint Andrews Beach, Australia | | c93a91241472292327a03d6710b1b931d5ca7917dd9d96fbe9e6a5a87e714d76 | 82.3.12.xxx | London, United Kingdom | | d0187b3ee5a47d23d8ad6d343790f1ac42ed36ffad036c203566929014d89f19 | 137.27.174.xxx | Fort Worth, USA | | 9b6c1922db4cc54565b335ebb31b4051881741841d57e9450f43e71ffe44158f | 61.186.18.xxx | Haikou, China | | 37dfbb128680675c7322a7cc2bd9bcbc2dcd51d838db368cff70fcceec5ff6ef | 61.186.18.xxx | Haikou, China | | 825eba0437b4dc9ecabc1f7f6b35cb93e09499a41be0db935a422edb71e68dcd | 45.153.229.xxx | Kiev, Ukraine | | de3714efaa48dbbe514adde6a455059f05fb25a659247c5dc7a700e7b7d00c0c | 45.153.229.xxx | Kiev, Ukraine | | f91c6fe9288e8f01962e952a86842a87bdb8cef8c404bff11e3d45b1278c189c | 75.169.42.xxx | Salt Lake City, USA | | 827a6e00d1c6afd608731a0a7651f4a2ed97581561772e96d2dae98da4b0828b | 75.169.42.xxx | Salt Lake City, USA | | 7dcf23e6c1af4142d93687f154be32a05f23f1da68dfefdd74aac6b2757484fb | 98.167.66.xxx | Las Vegas, USA | | 93b267d80e34cb8af1e65ba757e42f149886b36b4f4c77de25f0432165156302 | 170.75.164.xxx | Port Coquitlam, Canada | | 66cc95111e3d389be8f00346f10999fea70b7c0df6859b662ba4e2927e9650a2 | 67.4.193.xxx | Eagan, USA | | 925912bd08f27595bed36c7a321765d8f4ecc7722db4507bda2215d4f529e142 | 67.4.193.xxx | Eagan, USA | | 17434712eb7b3347bae2b899594807462eaca90a80fad3410d62b27aa535072e | 178.147.26.xxx | Igoumenitsa, Greece | | 2d24443a0bdd2ec8c80227f12e68d5315301d0541f519cad3bc7d8ab9c2e4663 | 72.226.6.xxx | Woodside, USA | | ed822eee8769179d1f8a63039aa2125b26c81f5f33d890448861b2a33bc23b71 | 27.94.74.xxx | Saitama, Japan | | c7751e8b7d72c4d88a3a8b2ec66c928e8b661edd404740d56815301577985773 | 69.142.189.xxx | Union, USA | | 9fd5a50648b853bb32b7964c3a8bd5b759633488575ccf4aa8f6ab1fee56f947 | 69.142.189.xxx | Union, USA | | a26c05637c65bdf0734e29f1503c256ff227701744aa3da2fceea3717c06db7b | 86.6.75.xxx | London, United Kingdom | | e9953b8fbf6a5c7849cf7defc2206f75a22bf794d4acf0031abe7828cbd59c61 | 86.6.75.xxx | London, United Kingdom | | 3438ba836d71a47a4c7d183a3a69a76ee05ba6e94a838119d8c6d072157c7f2a | 86.170.46.xxx | Leeds, United Kingdom | | fb89a1b5a0fe1028f67fb2bf1a6a4445851dd9c86d038abd01401d6d6be7832b | 47.32.178.xxx | San Luis Obispo, USA | | b6cfad7b11432ca7a814cc34801132ba73a1d3937918347c1b151d9bb322306f | 47.32.178.xxx | San Luis Obispo, USA | | 905848f706cf9e3b83749fd616f0d8f81e99770efc351d8162502b97acf28317 | 186.122.57.xxx | Buenos Aires, Argentina | | 22115797be1944bc557f9a69437edb93f119671006b6aebef1ffbfbad1c13958 | 219.251.180.xxx | Kwangju, Korea (Republic of) | | 1ca68ab94e6c8cb421013bb861ca5b75a987f741f2281b08ecfeefe84eddfcf6 | 219.251.180.xxx | Kwangju, Korea (Republic of) | | 2943f20e774416ac529cab6b4356e90d8e0d251dfb85fa9438534ca63d39d44a | 109.90.2.xxx | Weckrieden, Germany | | a70678de7f9de1387e3115600bdbd10e4f46b24c3d8c62711d2cc62a23908813 | 66.131.18.xxx | Montreal, Canada | | b79c3014fe87e63fd711488bc593909abb005756220719d921073c1f36d48bf7 | 193.58.196.xxx | Kosice, Slovakia | | 78db32de2c4d28839df28cd398faa9bf8e0dbbe1fb6e1f21379bf4ff5499bc00 | 82.67.247.xxx | Raismes, France | | 25fbebd87ad7b91b19ded304b39b2dff7baaf24fc95ceffa79ca9569c92a826a | 47.185.218.xxx | Plano, USA | | 597042db2210b4b3d999fd909a3e5d773256cf43c3c192b3159e76bd02fc7aa8 | 47.185.218.xxx | Plano, USA | | e38ad1f98b04cbfb1836184c9a8b3c97736c5aeef4b9b5417319b4baafed342a | 172.116.56.xxx | Santa Monica, USA | |
|
|
|
|
dragonvslinux
Legendary
Offline
Activity: 1680
Merit: 2213
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 15, 2020, 09:23:20 PM Last edit: November 15, 2020, 09:35:10 PM by dragonvslinux |
|
I'm looking forward to seeing some evidence behind these claims.
Simple. Use Monero, find out if you are on the list. dragonvslinux, I think that by now it’s obvious that badcaca has nothing except s’kiddie-tier bragging, bluffing, and spamming the shit out of this forum with long lists of txids, randomly selected peer IPs, and annotations of what are probably just his own porn fantasies. I'm aware. There is no documentation of how this was done or methods that can be reproduced so that others can arrive to same conclusions, or evidence what-so-ever that any of these IP addresses are connected to actual users. I left neutral feedback referencing the previous page as it's nothing but hot air at this point. You don't need to get too philosophical with this to see it's complete horse shit. Edit: Had to re-submit feedback as post deleted meant your post got moved to page 1. Re-Referenced.
|
|
|
|
monero_badcaca (OP)
Jr. Member
Offline
Activity: 154
Merit: 2
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 16, 2020, 08:41:35 AM |
|
Monero BADCACA sybil attack is still here, despite the claims that it has been fixed. If your tansaction is waiting for a few minutes in the mempool, badcaca node got it.Here is 100 Monero users who trusted in its privacy yesterday, are you on that list?:Txid | IP Address | City | Favourite porn | 54a2aa0cc5bbd948c17dfd9c429d66c71acf8c36bb0f6b44b22503fad76e187b | 154.21.21.xxx | Washington, USA | incest | 34dd786c10556849f0418644921769f3d2af2ed83b7c9f1e8b5315966e4470dc | 5.180.62.xxx | Muenster, Germany | incest | 8aa654870e2fe6ad6ca2762bc7d9847feba759f49d1bb1c8ae407e2f5b67d591 | 85.203.45.xxx | Amsterdam, Netherlands | incest | d7fc4fbaa6634f0a9cc0b15b91cd72c7f18e745b7f5a9c5906e65ff2bfc586ad | 185.156.175.xxx | Zurich, Switzerland | incest | bf6e8c719d91d8ad783ba5cb6fb61b50baf507b80de9899b34bbf898fccf6372 | 174.94.155.xxx | Montreal, Canada | teen | e0bf4722f6b16514e79dfb8e6c44c72ea55a3990e9781de7c081b49839793fff | 14.199.50.xxx | Lung Wo Tsuen, Hong Kong | | cb784b4eb7061d5e4bf017659828d05da5da9ec095b8b4d4f8b9f5230157ade5 | 71.131.70.xxx | Dallas, USA | | 636f4a75a1e2398f0c0a681c3859433de0df42b854cb2ad23b85b25c61fddcb6 | 68.53.174.xxx | Brentwood, USA | | 84fb6cbacb89a21c4d9c35271bc57b8d8e7ceeb105974d7c9a671ebb7d4c1396 | 99.145.235.xxx | San Diego, USA | | b331f339ef00d5b766344150101e7f0abc988316343cf817a0d0ab6565dabd3f | 100.35.146.xxx | Middletown, USA | | 6fea287f75bead679527723ae416741aaf511aa4f7055ccc9f4d6d7b35451159 | 86.121.150.xxx | Voluntari, Romania | | 6524d26f233f4612195a8d6a29c642f3fb84c203c2bf33dc73ad7fd28070a7cb | 83.212.105.xxx | Athens, Greece | | 7fc70d4663c5b5b01d5f08b0e0b5f73a82a84a425a018d9686cc37b06d024208 | 80.255.95.xxx | Chelyabinsk, Russia | | a8a3b0bbadcca931bbb02dc0549aa09c851108dbc9ccc267cbdb29e5ba2dd6bf | 178.254.157.xxx | Belgrade, Serbia | | 0bcc347382b14d2510e11b2cf087f83e08fd17aa75d0156a7c0a5462a096f708 | 125.111.145.xxx | Dajiahe, China | | 354f8c17481254a5ca3253b82ac0c987895b7908a5803dfb5da9e753a09ae7d6 | 173.61.6.xxx | Mount Laurel, USA | | a65dff5675e98db3be3b5ea36f815587a2e1923fa7a29763616829a0f7c88baa | 81.132.228.xxx | Whiteley, United Kingdom | | 65a8e3c2d2990cb576bf1bf1d492074a0b4fed66173b6561fb85e1068455d1ef | 178.69.35.xxx | Saint Petersburg, Russia | | 2c91f2360003cedaf767a47f4c177cb768b9a801d18e262785a86ed3e027babe | 105.244.75.xxx | Pretoria, South Africa | | b704b5c97a14c5e964ef02f8682d42dfa86a9889233f33a90be68ad5c94f543f | 203.118.185.xxx | Tauranga, New Zealand | | 74b9a61679fbed564e07c46062fcc70c47f355e2d5ef0a02dbc3cad274f4c0f7 | 71.197.224.xxx | Kirkland, USA | | b0ee5a67b528111949e59144bd605c830912de379874ec9b50d0d4cb6e345884 | 100.38.225.xxx | New York City, USA | | af5eda448ee8cd37b8da41d11d581c5f38983bebf2693cf6d747fc1f3aed5af8 | 125.84.188.xxx | Chongqing, China | | 3d5c9738acd687c25bb7d77b591570a1deee86d11c6793344a9ce50aa062a812 | 205.206.248.xxx | Calgary, Canada | | f0d559515f1ca06bcf2403e7107e3764837f0aaff164c1dac09285a4cb530c0a | 45.133.180.xxx | Mexico City, Mexico | | aad379235b7668df8f4cc9ba61687efabfe7f259e6588355eb787834a55794b1 | 37.24.1.xxx | Dusseldorf, Germany | | 3e178f1095ae4f8710589db94bad836173c94aa57d50769d1624ceb01683d148 | 125.197.216.xxx | Tokyo, Japan | | c4fb6022b02a50c8d2df294729b808bdaab48d2fc0c182b3b44b0144e93c6c98 | 50.73.65.xxx | Atlanta, USA | | 5a40da05402bf208939789f523a88e22be7f63f81b9e151ec494725c9304df4d | 71.238.235.xxx | Little Rock, USA | | c40845eebc073561160e1ce9f23906e121d53fa3b214b4ea370650749d900371 | 84.59.222.xxx | Isenburg, Germany | | d748c74438c5cd3bc637acb694d6697aa627322abd1e27b89b1e5d6218873eaf | 162.204.125.xxx | Rosemead, USA | | 99d240914a703a3c90229c1d3167f04b3d8bbea8445df8c17a96fa233fd85e2a | 117.20.65.xxx | Toowoomba, Australia | | f290355a260975060064125122dc7a38b660f0bdb718453df3aa1281508b4afa | 93.219.91.xxx | Berlin, Germany | | f684ff1760e1f31c70f05efac733fded6c067dea8bca056580321ae1e25f1d22 | 2.204.231.xxx | Berlin, Germany | | d971e82f7cc0bfac06fc3d55be1a74b2e129d3478665a45a0bc7b381c23ac123 | 77.180.226.xxx | Stuttgart, Germany | | bbfa9a6d8081508832ffe48fd88fe544bfe68b265e3230ac82994d589509c93e | 66.86.47.xxx | Columbia, USA | | 82842ae08c1f0ed73881deef1d7c8d2a64ee7a86c50e6fbe1ad0080c5b1cda08 | 79.216.182.xxx | Leipzig, Germany | | 4ae0910d9f112be2e5cfd26ec91e793354818ae1d8899be763d2130008a0fe01 | 50.80.57.xxx | Peoria, USA | | 60387f97eeafbea2f2c11e644c70598bf2335c4b28686bfa851f63c693967a65 | 87.99.38.xxx | Wroclaw, Poland | | 33786d8cb2e16e83ac329bafb612ae5c9e4ed29a2ce25110d58549e56fffee37 | 135.23.93.xxx | Ottawa, Canada | | 7f493f3d0a45384e5d85cb6c2452314a48e4843346547c22163f6fc10ea4f740 | 73.254.231.xxx | Burien, USA | | 522bbefc269bf90eda5aaf1d771966750ee170ec386e53d81dcd11783bc705f8 | 37.192.131.xxx | Novosibirsk, Russia | | b183c5d598b6bf5f33ff0bfa9046062c3354623791aff152d17271e5f4dcc488 | 93.225.66.xxx | Dusseldorf, Germany | | c550edc890e91ba047e362795be81726daccc577fe97394b1687225f41b05a55 | 182.43.181.xxx | Dezhou, China | | 41eefd1171934760d68e9184bda6cc42b6f0bb4c6049702e2e25bfd59acc4fd5 | 86.106.121.xxx | New York City, USA | | 0ec9e5924410f3e0e176abaa0966ceea443eaaa54faab1ffa17381bb73d970a9 | 85.23.228.xxx | Vantaa, Finland | | 7d71a023c7ad9cab9b4c3b2b136b8076bc96bb63e9ab9153da7a77b7f559edf0 | 77.65.110.xxx | Konin, Poland | | 783bd55f258cd4ccbe9cd1229ae065ac45b3b37103bb8c20486a98b39ecb9530 | 75.142.98.xxx | Long Beach, USA | | 3d53b8def99b104ad2376529579d89837fab84c5ca6dd480ee0a7712f516a7b5 | 90.91.212.xxx | Paris, France | | 7e32ce6853c9bc2af7d6d147f8f39f29d6187b935448cf0ecd579e05689df808 | 109.169.220.xxx | Tolyatti, Russia | | a1abd3c532e6907a69a9dbb8c4213eda8e8ddb45e4762d4f874f297d659b3a5f | 119.115.218.xxx | Jinzhou, China | | 81d6249766ade77ae6a7646edd352b766f4dd2a59d55eae6bb0785e57662c78d | 173.88.171.xxx | Chagrin Falls, USA | | c1a23f818cfca500d94757ef2afd242134925d48cf6134b87ed2a3157cec1d73 | 213.47.22.xxx | Vienna, Austria | | 920f2a81dfd3ea632697632946bf7e97d04a4150db3d3d2590daed3d357a6e5a | 111.122.8.xxx | Zunyi, China | | 8cd372866783c44b4af150bd151032bab6aafce33e2ed5f4af4f33b4993eff00 | 50.38.125.xxx | Vancouver, USA | | be9edb3ce939f0af08872311029253aa6999e6508877354447680038d575ea72 | 80.110.81.xxx | Vienna, Austria | | 38353cecb134b770cfbad15a1bfbdac71f9b07baa175d112d87089f5ed6ae3a9 | 109.192.191.xxx | Stuttgart, Germany | | b5d7c75ff1494036e2cac0b308b0b60708edadd63aaa5d333242a7ff1a961188 | 150.143.250.xxx | London, United Kingdom | | 644b228b6d0313f875b286047ee8ef3e1a1070dbdd933c82e950a74ecf0ce824 | 123.243.178.xxx | Melbourne, Australia | | 0a5086d17c8a147bb3145518825d0b44e888f44137c83cb91d6579c3184e44c8 | 92.233.45.xxx | London, United Kingdom | | cfb2cb28fdb9493b9458791396721f32f712f07b1690b5924d2e79b6c0fc90b1 | 151.224.97.xxx | Sunbury-on-Thames, United Kingdom | | 1765840671a0f6fcb342a8d7240453b6ae300bc75866c1ea2afb4afe5f4a0666 | 27.94.74.xxx | Saitama, Japan | | 8dbd1b64a7ae400dc8417863fb3f39cd835f2e46d16459132a269bfd594d7a04 | 94.112.121.xxx | Prague, Czechia | | 43b58b1304ea7b51a91cdc92c37859352b9be6837e0347145f9d382485c26fab | 87.176.243.xxx | Erfurt, Germany | | 69ac4c22f85db4bd9cf6500658e0986f4fe68ef2c15d3397090bf058074b9df1 | 87.176.243.xxx | Erfurt, Germany | | 86a4b2764644c7527c5281b4ac3ebd13086db99895744ba1a3447c3fd5761683 | 80.15.162.xxx | Neuilly-le-Real, France | | 47ac98e87cfeb9e337f6202d6ee020942e6a20b913780d1058c363159cf42fb6 | 80.15.162.xxx | Neuilly-le-Real, France | | 45c718b2e077ee52539682508d49f084700168d47a8266d13b545f1590b8c4d3 | 176.37.169.xxx | Kiev, Ukraine | | 97e3f1b189d13e06bc6b1515eb0c32e1e7894951387b99d3eeb29ccb035389ab | 223.247.162.xxx | Wuhu, China | | b83d3e9f8b3cb1866f2ffb882f38d0a559f7af64e7154b0cd6520e7633090517 | 223.247.162.xxx | Wuhu, China | | 6b8c51dc66e603263977dda067a057f73df4889e2613eabb84a046319292f3a0 | 98.167.66.xxx | Las Vegas, USA | | a4834f8f50e124354b5578162652bf4a83a7f84dae3df309f64de4a3aac218f5 | 107.13.140.xxx | Durham, USA | | b8bd8745e3be021e4a5fc3ed84590d3980c69169a13b4a910ec3fdbb9e4e3161 | 104.52.169.xxx | Jackson, USA | | c741d5e67eb25abd9a639909ddfa0e0442633208789f75a744d4bdd4b0204283 | 78.132.0.xxx | Linz, Austria | | 896317eb8936c38824f671021a6df83f0b70d52270ffb1fef923eb154de7a63c | 24.16.42.xxx | Kenmore, USA | | 6166265fb6259ed6c4ba554cb1adec4f0cdc933f236a3228e5dd41db0ba05f32 | 24.16.42.xxx | Kenmore, USA | | c13635796a6e3f06b76f953d65d481b322e4b76072698ba25b903ee358fb395e | 118.136.3.xxx | Jakarta, Indonesia | | dab208290bb89bef2a06dae8fdf037eab7287c28597e61b096eb42bf08c1e730 | 118.136.3.xxx | Jakarta, Indonesia | | 45117956762b58c67ab4990734a5db51cec29b4b84ed55cd921c7530f1744d6b | 91.34.59.xxx | Hanover, Germany | | a1f5128c6262130b70eee71704067d5041e2a908053e82ac1c5decafc2695616 | 91.34.59.xxx | Hanover, Germany | | 409bae4506a5d3c664fdb97b6ff4feecfa929f67431e0eb8d936450d2b9a57d3 | 80.101.35.xxx | Bergen op Zoom, Netherlands | | a0c8dc7cec06305d94a06e9ac2a14e5a5a4de644440e134c841c05f76df1b5e7 | 94.21.129.xxx | Budapest, Hungary | | f4221e0b8fd00aa22e74d90941d5386a228cf29b61ae9149104e195bb3c4570e | 94.21.129.xxx | Budapest, Hungary | | fa46e69e32f23ed6ea926c7bda5b2c419b6947da70491bed05c7eb27d0a9724f | 184.55.213.xxx | Milwaukee, USA | | a3012443c837085750848e750de9a9c5ab59bb3f4fecaeb79733f51e362ceaa9 | 46.223.172.xxx | Freiburg, Germany | | 5a14f04be9bb8993658b551d535ca0b480a6d12bd86f3ce2b2f1afea8c9f2b4e | 46.223.172.xxx | Freiburg, Germany | | e613b1ccba0ffe0d24efc0671d0f024c07a030924415661414c172870a752d49 | 101.191.35.xxx | Moss Vale, Australia | | dce2101f49b0b99fe81e1081a7cc1c49f7d6f9c6f4c639cf041825038794f8d8 | 76.97.77.xxx | Athens, USA | | d4dacb4ea0b41520e7215a28078918f602a87b933e63c530541152013cded23f | 188.151.202.xxx | Stockholm, Sweden | | 2903b5d75ef3f37af35dc931a110daebdc326d1e58bba78304c4f1dcf48fb07a | 188.151.202.xxx | Stockholm, Sweden | | ba6c1a8a814ed6b3c945e25c0238accd5121813c469c7bb3d746948309fbb31d | 217.228.53.xxx | Berlin, Germany | | b927470c5912e41be9ae2cb43ee7a3dc3d1630fe190a7ddbbc30d6cd46dcd091 | 84.186.58.xxx | Sandstedt, Germany | | 901d25b4609778eaa0fc153a07656f0960c98d05c5416cb5ad003e0d801cf7f9 | 73.2.78.xxx | Modesto, USA | | 8f7db93786db91f0ce9c8fd19859478d26e14047431da924daa158b87bf23d13 | 83.213.131.xxx | Bilbao, Spain | | 3d8aed502c06b7bdd126a1740dc20e3d11562c3bc9e7261f7093125c3be252ca | 84.151.218.xxx | Zweibrucken, Germany | | 11064faee12cfc3cfc04e03c558fa18045fdb4e3834f412f6acad69a34a5da09 | 84.151.218.xxx | Zweibrucken, Germany | | 297bc7be2fbeb236187ba67a11f8dcdca445dbee798a70bd7950752c2f0eedc4 | 125.187.63.xxx | Seoul, Korea (Republic of) | | 9c6e37a10810fb5468d19978e4527b141bebb2823972ce970ed9783f394b2361 | 70.184.66.xxx | Laguna Niguel, USA | | be6ec85080cc0bd6a52638da43d74ab4f2187b9be32dd17f3e48e35f9fd4c2dd | 70.184.66.xxx | Laguna Niguel, USA | | 9c8e9691c6ab577285b4e0e8d3de35bc504b9d878232a4d2698e51724303a2d7 | 87.78.170.xxx | Dusseldorf, Germany | | 087921c33147eec33fa8d04c24c8804f7af3f4cd6f667cf537a5100dc13e3656 | 212.17.91.xxx | Vienna, Austria | | a314150d70ca3fa52b844b7a75261efe2f5a28824436d7c7ea1b1aa56a3e40b1 | 89.115.109.xxx | Lisbon, Portugal | | 1f69d13f65bde1cea99247d41996f251c57ec01b3c994270b208b200674144fb | 170.75.164.xxx | Port Coquitlam, Canada | | 61bed20477e19dc201f5e3389e105924fe4ed2fcea8863977319f118f85aea24 | 170.75.164.xxx | Port Coquitlam, Canada | | 0768a2d1a743689c66bd9efbe98e0dbef067ba807a05addfeca7c03b3a872da2 | 71.173.198.xxx | Harrisburg, USA | | 242423980ed163e923a0b388c6689a9156813c681cf164e9d9aded7be91f2a92 | 50.220.121.xxx | Naperville, USA | | 10cbe1c46f62cd4b9e3dee8eb35bcab3cbbd26a81dc989670ec2c87272b2630f | 118.25.154.xxx | Beijing, China | | 5317e9275a123a4cc06e66dbca217ae8c0099749ce398cba39b21769e1138e24 | 176.23.22.xxx | Copenhagen, Denmark | | 7602aaf802ed93a3eac9445fd813fce97f85b0c4a51ae2a6fa2cf1b77174a8e8 | 92.171.32.xxx | Clermont-Ferrand, France | | 9399586efb23ddbcfed188d12f5646ed530319ff50e0d8557374e98be38e3631 | 83.97.20.xxx | Bucharest, Romania | | 1c4e3c487bca90113d00bfb759043fa7626e422edf24feb05a78a58569aeae76 | 72.83.32.xxx | Arlington, USA | | b4db32de62eabcc78622e86613ced9655c1550c0e2932df5a4735b49944b8f10 | 47.25.173.xxx | Omak, USA | |
|
|
|
|
jademaxxiss012
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 16, 2020, 08:56:01 AM |
|
Then when will be the authority to investigate in it? If it has cause some mess like human trafficking, porn access to porn ban areas or the likes of these crimes. I think also it is wise to investigate platform that has been accepting the coins or all its connection that could be related to criminal activities. Lastly, if there will be a clear evidence that could put them in jail hopefully all the individuals involve will going to pay the mess they did.
|
|
|
|
|