This only proves that this person is accessing the SupportXMR (webpage or mining pool). Since it shows every connection, you can easily open the page of SupportXMR on Chrome, and type that command you'll then see the IP address of SupportXMR. On Windows, this command basically shows every connection opened from the computer to a remote target. Some people are saying that Sigma is connecting to a mining pool because of the output and this following command: "netstat -a". And it actually proves even better that Sigma cannot be a miner, since a connection to a mining pool cannot be done through HTTP. Basically, it's a way to not use WebSocket and use the HTTP protocol. They're using this as proof since it contains the word "polling" which is close to "pool" which then is linked to the XMR mining pool.Ī quick Google search shows what "polling" in socket.io means. Therefore this following link will also produce the same thing:Ī Redditor wanted to know what the localhost:3000 connection was doing and made a socket.io server running on that port. Some people said that SupportXMR was used by Sigma because it shows the message "Mining Pool Online" with anything appended to the URL.īut you can really append anything to it to get this message. Section 3 - Other accusations linked to it The Norton alert was very likely shown due to an XMR miner running in the background. It is very easy to run an XMR miner at the same time as Sigma (this is most likely how this screenshot was taken). They showed a correlation between that alert and the localhost connection shown in Section 1.Ī screenshot like this cannot be used as a piece of evidence. The person who uploaded this screenshot said that this alert happened after launching Sigma. It shows a Norton alert about a connection to :3333. This second screenshot was combined with the first one to prove that Sigma was mining Monero. But, a connection to a mining pool cannot be done via localhost, the pool of SupportXMR is done through port 3333, and this connection cannot be done with socket.io.
#Sigma client change resoultion code
The code shown in the screenshot shows a connection to localhost with the port 3000 using socket.io. They don't support socket.io connections. Cryptocurrency mining pools are using other protocols such as "Stratum". Although their connection port is 3333 (There also are the port 5555, 7777, and 9000).įinally, you can't connect to the mining pool using socket.io. People accused us of connecting to the SupportXMR pool. That tilted some people's mind, remembering a mining pool's port. The test connection in Sigma is trying to connect to the port 3000. Ressources about localhost for newbies out there: Since the mining pool is not something hosted on your computer, to connect to it you need to connect to the Internet. That counter-argument should totally be enough to prove that it cannot be a connection to a mining pool. This means that this bit of code is trying to connect to a server hosted on your computer, not the Internet.
They thought that it was suspicious that Sigma was connecting to a server.įirst of all, this is a LOCALHOST connection.
(XMR or Monero is a cryptocurrency like Bitcoin). This screenshot was combined with another one (explained in section 2) to prove that Sigma is connecting to an XMR mining pool. This should have been removed in production but was not done due to an oversight. It was used to do some tests with socket.io. That code tries to connect to a locally hosted (localhost) server.
#Sigma client change resoultion update
This shows a test socket.io connection that we used in an attempt to update the Agora (a chat system within sigma that we wanted to implement back in 5.0). We'll be totally transparent with you on that point. This screenshot of a partially decompiled Sigma code was used as one of the main arguments to "prove" that Sigma was a "miner". After some misunderstanding and fake news spreading about Sigma, we felt that we needed to address a statement about this situation.įor about a month, the info that Sigma could be an " XMR miner" spread pretty quickly.
0 kommentar(er)
