<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Hakkane on Medium]]></title>
        <description><![CDATA[Stories by Hakkane on Medium]]></description>
        <link>https://medium.com/@salva.enkidu_89587?source=rss-e9412ab75b3d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5Lh-XWa7Am2NyNpKNxWMXQ.jpeg</url>
            <title>Stories by Hakkane on Medium</title>
            <link>https://medium.com/@salva.enkidu_89587?source=rss-e9412ab75b3d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:47:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@salva.enkidu_89587/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Decentralizer 1.1 — Now powered by hosts benchmark data]]></title>
            <link>https://medium.com/@salva.enkidu_89587/decentralizer-1-1-now-powered-by-hosts-benchmark-data-2cdfe69e8d90?source=rss-e9412ab75b3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2cdfe69e8d90</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ia]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-storage]]></category>
            <category><![CDATA[decentralization]]></category>
            <dc:creator><![CDATA[Hakkane]]></dc:creator>
            <pubDate>Fri, 19 Jul 2019 13:50:15 GMT</pubDate>
            <atom:updated>2019-07-19T13:50:15.949Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Decentralizer 1.1 — Now powered by hosts benchmark data</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RQfvLcm7v0GlCopLBLZeJQ.jpeg" /></figure><p>Last February I released <a href="https://keops.cc/decentralizer">Decentralizer</a>, both in graphical (GUI) and command line (CLI) versions: a companion app for Sia renters giving you more control over your contracts and more safety for the data distribution. Last May <a href="https://www.reddit.com/r/siacoin/comments/bj3dh6/siastats_hosts_monitor_benchmarks_alerts/">I released the SiaStats Hosts Monitor</a>: a free service that is evaluating and benchmarking on real time the capabilities of each host, helping and alerting their operators when issues arise, and letting renters to know which hosts suits them the best.</p><p>Wouldn’t be fantastic to see the performance scores of the Monitor directly on the Decentralizer dashboard? To be able to easily avoid misfunctioning hosts or select the top performant ones? Today I am releasing Decentralizer 1.1. In this post, I want to explain you how to use this newest version to create filters of hosts according to their performance.</p><h3><strong>The conservative way: blacklisting misconfigured hosts</strong></h3><p>We can take a conservative approach when creating a list of hosts: let the host selection algorithm of the Sia software to choose the hosts for you, but removing from the list of candidates those that are misconfigured and are known to fail during file transfer operations (some of them will be able to form a contract, but will be uncapable of nothing else due to errors on their setup). These hosts receive a score of zero on the SiaStats benchmarks, so we can create a <strong>blacklist </strong>that includes them, what will force Sia to use only the properly working hosts:</p><p>1- Use the “Scan” button at the top-right of the UI to retrieve the updated information about the hosts</p><p>2- Go to the “Hosts filter” tab and select “Blacklist” on the filter mode</p><p>3- On the “Order by” drop-down menu, select “SiaStats score”</p><p>4- Scroll down the page to find the group of hosts with a “Score: 0” and check the selection box at the top of the group</p><p>5- Click on “Apply filter to Sia”</p><p>If you haven’t formed an allowance on Sia yet, now you can do it safely. If you already had contracts with some of these hosts, they will be cancelled immediately (you will be warned about this during step 5).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-GcjhpMScd0AYFs8EoLZsA.jpeg" /><figcaption>Steps for blacklisting misconfigured hosts on the GUI</figcaption></figure><p>We can do the same operation with just a few commands if we are using Decentralizer-CLI:</p><p>1- `<em>decentralizer scan</em>` for the initial scanning</p><p>2- `<em>decentralizer filter mode blacklist</em>` to set the filter</p><p>3- `<em>decentralizer filter add score 0</em>` to add the hosts with a score of zero to the filter</p><p>4- `<em>decentralizer filter apply</em>` to finally set the filter on your Sia instance</p><h3><strong>The aggressive way: whitelisting top-performant hosts</strong></h3><p>We can be more aggressive, using exclusively the hosts with the highest performance, by including them on a <strong>whitelist</strong>. This will limit the selection process that Sia will do to hosts within this list. But we need to understand that there is a trade-off with this strategy: while the Sia selection algorithm takes in mind aspects as the pricing of the hosts, the benchmark scores of SiaStats are purely based on their performance. This means that the more restrictive is the filter we create with Decentralizer, the more expensive our contracts will probably be, as we might be leaving out the cheap hosts. Decentralizer is meant to complement the Sia selection algorithm rather than replacing it, so I recommend you creating filters that include at least 70–100 hosts, so Sia has still room to leave out the most expensive hosts when it selects your set of 50 hosts. If you decide to use this approach, be mindful of this trade-off and check periodically your finances.</p><p>1- Start again by using the “Scan” button on the top-right</p><p>2- On the hosts filter tab, select “Whitelist”</p><p>3- On the “Order by” drop-down menu, select “SiaStats score”</p><p>4- Add groups of hosts with the highest scores by clicking on the check boxes at the top of the groups, starting with the “Score: 10” (the top performant). Check at the bottom of the screen how many hosts are being added so far.</p><p>5- Click on “Apply filter to Sia”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*E8aNM1hiVJ7K7Phg-mR67Q.jpeg" /><figcaption>Decentralizer-CLI</figcaption></figure><p>In the case of Decentralizer-CLI, the commands would be:</p><p>1- `<em>decentralizer scan</em>` for the initial scanning</p><p>2- `<em>decentralizer filter mode blacklist</em>` to set the filter</p><p>3- `<em>decentralizer filter add score 10</em>`, `<em>decentralizer filter add score 9</em>`… to add hosts progressively. You can check your filter size and composition at any moment with the command `<em>decentralizer filter</em>`</p><p>4- `<em>decentralizer filter apply</em>` to set the filter on your Sia instance.</p><h3><strong>Other new features</strong></h3><p>In top of these new possibilities, the rest of the features of Decentralizer are still there: avoiding host farms (users controlling multiple hosts, what reduces decentralization and sets your data at risk); geo-fencing your data (by restricting the countries where your hosts will be located); selecting manually the hosts you want to include/exclude (based on pricing or whichever reason you want) and cancelling your ongoing contracts you don’t want to use anymore.</p><p>And in top of these features, Decentralizer now has a few additional capabilities:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/839/1*Tal2rFdHvMbtmvtvu57q0g.jpeg" /><figcaption>The new contracts timeline on Decentralizer-GUI</figcaption></figure><p>· Users of the GUI version now will see a timeline representation of all their current contracts, showing the fraction of the funds that have been spent so far, when they will expire and more information when you hover the mouse over each contract. Note that his graph uses a new terminology, easier to understand, that the Sia developers are rolling out progressively for Sia: a “billing period” that gets renewed automatically when it is over and a “grace period” where your data will still be available even if you do not extend the contract.</p><p>· The CLI version users have new help commands, easier to read and follow, as `<em>decentralizer filter help</em>` which will show a short walkthrough guide about setting up a hosts filter.</p><p>· The CLI version now has a combinatorial command for adding hosts to a filter, so you can select hosts according to geographic region, software version and SiaStats score simultaneously in a single command. For example `<em>decentralizer filter add [US, MX, CA] AND 1.4.1 AND [10,9,8,7,6,5]</em>` will add only the hosts that meet all these criteria at the same time: a) they are in North American countries, b) are using the Sia version 1.4.1, c) have a SiaStats performance score above 5.</p><p>Overall, with Decentralizer you take the control over the hosts selection, deciding where and how you want your data to be stored on the Sia network.</p><h3><strong>Improvements on the SiaStats Hosts Monitor</strong></h3><p>I want also to announce some new features I am releasing at the same time on the <a href="https://siastats.info/hosts">SiaStats Hosts Monitor</a>:</p><p>· Previously, all the benchmarks were performed from a single server located in Germany, making hosts located on the other side of the world to be unfairly penalized. Today, the Hosts monitor is a multi-region network of servers (at the time of writing this: Germany, US and Singapore) evaluating every host every 2 hours, what removes this geographic bias. The code and the infrastructure are prepared to scale up to dozens of more servers and thousands of hosts as the Sia network keeps growing</p><p>· Users can now see the benchmarks and results filtered by regions. So, you can check what would be the latency and bandwidth of the host if the renter was located on the US, as opposed to Europe or Asia, instead of just the world-wide averages.</p><p>· The home page of the Monitor now shows a world map representing the latest benchmarks and their results, together with some charts depicting the health status of both the hosts and their stored data: how many hosts are really functional, how many are running out of storage, how much free storage is available on the working hosts as opposed to the misconfigured hosts…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*NyO0hNcZxrVv_wAbPLE7JA.jpeg" /></figure><h3><strong>Now it is your turn!</strong></h3><p>Did I mention the best part? Decentralizer is completely free to use and open source. So, go and grab the <a href="https://sia.tech/get-started">latest Sia version 1.4.1</a> if you haven’t yet, download Decentralizer as your companion app, and start today storing data on Sia, the real fully decentralized and battle-tested cloud storage solution.</p><p>· <a href="https://github.com/hakkane84/Decentralizer-GUI/releases/download/v1.1/decentralizer-win.zip">Decentralizer-GUI for Windows</a></p><p>· <a href="https://github.com/hakkane84/Decentralizer-GUI/releases/download/v1.1/decentralizer-mac.zip">Decentralizer-GUI for Mac OS</a></p><p>· <a href="https://github.com/hakkane84/Decentralizer-GUI/releases/download/v1.1/decentralizer-linux.zip">Decentralizer-GUI for Linux</a></p><p>· <a href="https://github.com/hakkane84/Decentralizer-CLI/releases">CLI binaries</a></p><p>· <a href="https://keops.cc/decentralizer">Website</a></p><p>· <a href="https://github.com/hakkane84/Decentralizer-GUI">GUI source code</a></p><p>· <a href="https://github.com/hakkane84/Decentralizer-CLI">CLI source code</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2cdfe69e8d90" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Numbers, figures, insights: a dive into the entrails of SiaStats]]></title>
            <link>https://archive.sia.tech/numbers-figures-insights-siastats-a56f79cebf6?source=rss-e9412ab75b3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a56f79cebf6</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[guest-post]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ia]]></category>
            <category><![CDATA[network-monitoring]]></category>
            <dc:creator><![CDATA[Hakkane]]></dc:creator>
            <pubDate>Wed, 01 May 2019 16:45:44 GMT</pubDate>
            <atom:updated>2019-05-01T20:09:32.221Z</atom:updated>
            <content:encoded><![CDATA[<h3>Numbers, figures, insights: a dive into the internals of SiaStats</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zK4ut0QT7QvglJ4UDUBSPQ.jpeg" /></figure><blockquote>A note from the Sia team: We want to thank Hakkane for taking the time to write this great post. If you’ve built on Sia and are interested in writing about your experience, <a href="/service/mailto:steve@sia.tech">send us an email.</a></blockquote><p>We are never short of numbers in this age of big data — in fact we are overrun. What we are always short of is good questions that transform that wealth of numbers into actionable insights. Results that could help us make better decisions. I attended a genetics conference recently (believe it or not, I am not a programmer by profession, but rather a geneticist), and I had the chance to debate and agree with colleagues about how little yield we are getting from the next-gen genome sequencing studies: we are generating thousands of databases of gene expression with the resolution of each individual cell in an organism, yet only 5% or less of the research community can do something meaningful with them. We lack the tools to visualize and analyze that data, making it insightful for the other 95%.</p><p>In a similar fashion, blockchains are generating immense amounts of data and statistics every day, but I think most of the time we are not benefitting from actionable insights due to the lack of visualization and data processing tools. This is why I believe that blockchain monitors/explorers have a pivotal role in the cryptosphere — they don’t just provide a handy way to check if transactions are confirmed, but they also deliver answers to those who ask good questions. They provide awareness and visibility to blockchain projects; developers can learn if the network is behaving as they were expecting; issues needing correction can be detected long before they are problematic; mining pools get accounted, so miners get the safety that they won’t be easily cheated; and misbehaving actors can be <a href="https://medium.com/@salva.enkidu_89587/how-bitmain-indeed-mines-coins-in-secret-2ea179e7ab75">detected and exposed</a>.</p><p>Two years ago, I became fascinated by the idea of and the technology behind Sia and decided to build something helpful for visualizing the Sia blockchain: <a href="https://siastats.info/">SiaStats</a>. What started as a simple (and ugly) site displaying a handful of charts evolved into a full network monitor, and then into a provider of APIs and information services as part of the parent project <a href="https://keops.cc/">keops</a>. Now, not only do I generate and display information, but I also deliver insights directly to the renters’ desktops through the app <a href="https://keops.cc/decentralizer">Decentralizer</a>.</p><p>My goal in this post is sharing with you how my projects work, the issues I faced and the solutions I found, as well as my future direction. I hope it will be useful for other developers looking to build an app on top of Sia, but also in general for those curious to learn how the tools they use work under the hood.</p><h3>The Sia developer toolkit</h3><p>When building apps for Sia, the <strong>Sia API</strong> is the primary way of interacting with the Sia network. While the database files of the software can be accessed directly (and even some of them are stored as plain JSON objects), the API is more comprehensive, can perform virtually any action the Sia client is capable of, and it is <a href="https://sia.tech/docs/">extensively well documented</a>. For someone building a network monitor, it was fascinating to discover that not only the blockchain information, but also the information about the hosts network, is available: unlike other self-claimed decentralized networks that rely on “bridges” to interact with hosts (and so, only these centralized bridges are aware of the network stats, and no one else can audit them), in Sia every client communicates directly with every host to collect their settings and usage metrics. Every aspect about the storage network can be monitored and audited by an operator of a Sia node, including available and used storage, pricing info, software version, etc. It’s a dream come true for anyone looking into data analysis.</p><p>While these API calls can be performed in any programming language by using CURL commands, a second very handy resource are the <strong>wrappers </strong>— available for many languages — that simplify your code writing. A wrapper for Node.js is maintained by the Sia developers (and it is <a href="https://gitlab.com/NebulousLabs/Nodejs-Sia">available in NPM</a>!), but there are also wrappers for Java, C#, PHP and Python maintained by the <a href="https://siawiki.tech/development/third_party">community</a>.</p><p>These two things were everything a third-party developer would ever need to build his app… until Luke Champine created <a href="https://blog.sia.tech/a-new-kind-of-sia-2e7454a9b21a"><strong>us</strong></a>. And suddenly, the Sia universe expanded. us is a library that allows developers to interact with the Sia network at a very deep level: contracts can be signed with specific hosts; files can be uploaded to hosts of your choice; you can sign a contract from one machine and allow a second machine to use this contract for uploading (using these contracts <a href="https://lukechampine.com/capabilities.html">as capabilities</a>); a third machine can download those files even if it never interacted before with the host. In the case of a network monitor as SiaStats, it is allowing me to benchmark the individual capabilities of each host (more about this later). While <em>us</em> is still work in progress, so far in my hands it is 100% usable. I am convinced that over the next year we will see an explosion of apps and resources powered by it: host quality assessment, file sharing, lite clients, and more.</p><h3>SiaStats under the hood</h3><p>The core of SiaStats is <em>Navigator</em>: a blockchain indexer that saves the block information into an SQL database. A benefit of building your own DB instead of accessing the built-in Sia DB is the ability of enriching the data and building your own data structures. For example, it is not possible to know, just looking at the blockchain, when a file contract has failed; Sia nodes can determine it without any doubt because it is a contract without any storage proof associated during the 24-hour window at the end of it, but it is not indicated anywhere in the ‘consensus’ database if it failed or not. By building my customized DB, I can flag contracts as failed or succeeded. As I consider it to be a critical component for many projects, and I think Sia can benefit from more developers deploying explorers, I made <em>Navigator </em><a href="https://github.com/hakkane84/navigator-sia">open source</a>, together with its own API server and an optional web frontend. In parallel, another script, Hosts Monitor, collects the information about the hosts network from the Sia API, geolocation databases, and internal benchmarks (more about this later).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*qlue0lbjWtHqomwGJUconw.jpeg" /></figure><p>Initially, my setup consisted of all my scripts connected to a single Sia client on the same OS and physical machine. I quickly realized how badly that worked and scaled up. There are advantages to using a Sia multi-node setup:</p><ul><li>Reliability: if one node fails for some reason, the scripts can rely on a backup node. This is especially important when using the explorer module of Sia (a non-default module just used by a few app types, like explorers), as it has not been maintained during the last couple of years, and it is prone to severe crashes.</li><li>Robustness: while blockchain data is the same across all the Sia clients in the network, this is not the case of the information from the hosts network. Hosts communicate their settings and used storage using a P2P protocol, so connection timeouts or the network architecture will make the host databases of any two users appear to be slightly different. It’s not uncommon for 5–10 hosts to appear as offline for one user while online for another. Merging and averaging the data from more than two clients, located in different regions, avoids this variance and shows a more accurate picture of the network.</li><li>Some hosts just don’t want to be tracked. For example, last year a hosting farm tried to avoid my monitoring by blocking the IP of the SiaStats web server (not knowing this was actually a honeypot I made for detecting cheaters). Moreover, once websites start benchmarking hosts, these hosts can learn to cheat the system by behaving correctly with the IP of the evaluator (thus obtaining a good score) while refusing to serve files to the rest of renters. Nodes in alternative (and undisclosed) locations can mitigate this exploit.</li></ul><p>SiaStats currently works as a multi-node and multi-location setup: a Sia client and us scripts run on each individual machine, and the scripts on the central sever connect to them to request information from Sia. One challenge here is that due to security constraints, the Sia daemon can’t be easily accessed from the outside world. To solve this, I use what I call <em>Routers</em>: API server scripts running on each remote machine. My scripts make a request to the <em>Router</em>, and the <em>Router </em>makes the API call to Sia on their behalf, returning to them the answer of the Sia daemon. They’re just an API middleman. But I also gave them some additional capabilities, like interacting with the us scripts and sending the file contracts I use for benchmarking back and forth from remote machines to the central server (so I can create a contract in one remote machine and afterwards reuse it across the rest of machines). The <em>Routers</em> also execute basic housekeeping tasks, like restarting a Daemon or the machine.</p><p>The next component in the stack is <em>Siastats.js</em>. It collects the raw blockchain data from the SQL database and analyzes it to build the additional databases that are presented on the charts of the SiaStats website. Some examples are the <a href="https://siastats.info/mining_pools">distribution of mining pools</a>, the percentage of <a href="https://siastats.info/contracts_status">succeeded file contracts</a>, and the amount of used storage <a href="https://siastats.info/hosts_network">among all the active hosts</a>.</p><p><em>“Who watches the watchmen?” </em>The last piece of my backend is a script called <em>Custodium</em>: it checks the health and sync status of all the Sia daemons in remote machines I operate by taking samples of certain API calls. It also detects misfunctioning scripts on the main server. In some cases, <em>Custodium</em> can solve the issues by itself (like ordering the appropriate <em>Router</em> to restart the Sia daemon or unlocking its wallet), and if not, it will send me an email alert so I can take action.</p><p>The data from <em>Siastats.js</em> and the SQL database is presented to the outside world using a RESTful API server script, and consumed by three different recipients:</p><ol><li>The <a href="https://siastats.info/">SiaStats</a> website, which acts as a visual frontend of all my APIs;</li><li>The <a href="https://keops.cc/decentralizer">Decentralizer</a> desktop app, which receives the geolocation of hosts and a database of the known hosting farms of the network;</li><li>Other websites, services and power users that directly use my APIs.</li></ol><h3>Towards a segmented storage network</h3><p>Much of my recent work is related to facilitating an idea I think will benefit the whole Sia network: segmenting (or tiering) the storage marketplace. Currently, a host handled on a datacenter with top-tier hardware and connectivity does not look different on the host database of a Sia user from a host running on an ARM board on a residential network. Both would be scored similarly, even while having dramatically different performance during real use. I do not mean that there are “good” hosts and “bad” hosts, I just think that not every host suits the needs of every renter. A pool of low-spec and cheap hosts might suffice the needs of users that require a cold storage solution, but renters looking for warm and hot storage will benefit from datacenter-grade hosts, even if that means higher costs.</p><p>The solution for this is benchmarking each individual host. The Sia software of each user cannot do this, because if thousands of clients worldwide were benchmarking every host simultaneously, hosts connections would become saturated. Sia as a protocol should also not rely on external “trusted” evaluators for assessing the hosts quality, as that goes against the <a href="https://blog.sia.tech/the-sia-ethos-48f72f1cf382">decentralization ethos</a> of Sia. This does not mean, however, that third-party developers like me can’t deploy solutions on top of the network that try to address this problem: if I prove to be biased or dishonest as a host evaluator, you just need to blame me, kick me out of business, and use an alternative service instead.</p><p><strong>Phase I</strong> of my plan consisted of providing renters with an interface that allows them to manually pick the hosts they want, instead of having to rely on the automatic hosts selection process of the Sia client. Enter <a href="https://keops.cc/decentralizer">Decentralizer</a>. Decentralizer is a desktop companion app for renters that facilitates the use of some Sia API endpoints that, while powerful, are not easy to interact with. For example, Sia allows you to set a filter for restricting hosts selection, but requires you to provide the list of their <em>pubkeys</em>, which can be difficult for average users. Decentralizer presents the user a list of all the active hosts that can be arranged by country, Sia version, or pricing. The user just needs to click on those to include in the filter: the app then composes the API call and executes it. Thanks to this tool, right now any renter can easily create a customized list of hosts based on geolocation, pricing, or any other quality parameter he is aware of.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fZWBJlEJ6ULXixjkpSxfxg.jpeg" /><figcaption>A set of contracts restricted to the European Union thanks to the Decentralizer app</figcaption></figure><p>But how can a renter be aware of the quality of each host? How can hosts be aware of it too, and set a pricing according to the value of the service they provide? <strong>Phase II</strong> of the plan consists of releasing the Hosts Monitor of SiaStats, <a href="https://www.reddit.com/r/siacoin/comments/bj3dh6/siastats_hosts_monitor_benchmarks_alerts/">which is available now</a>. Thanks to the outstanding work of Luke Champine with us and its related tools, I’ve built a service that benchmarks every host on the Sia network by forming contracts with all of them and attempting to upload and download a small test file. These results are then compared across the network and transformed into numeric scores. Renters will be immediately empowered (using Decentralizer or any similar tool) to select those hosts that better fit their needs.</p><p>From the hosts perspective, they will be able to learn their strengths and weaknesses, correct potential issues and decide to adjust their pricing according to the results. This last point will be facilitated by a table comparing their pricing with the average pricing of other hosts in his same segment. Shockingly, my data indicates that the current situation is contradictory: the most performant hosts are often cheaper than the mid-performant ones. My hope is that, thanks to this tool, hosts in the future will be more fairly compensated according to the value of their service. On top of that, these benchmarks will reveal hosts suffering issues, like lack of enough collateral, locked wallets, or consensus issues. If a host is suffering an issue that prevents its normal operations, the Hosts Monitor will display an alert. Moreover, hosts have the option to subscribe to email alerts and smartphone notifications to be alerted in less than two hours when a problem arises. I am hoping this effort will help to increase the robustness of the storage network. All these features are indeed free to use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N3f-ys9vQnPT2SQLnTtz9A.jpeg" /><figcaption>A glimpse of the upcoming Hosts Monitor</figcaption></figure><p>Just with these two tools (Monitor and Decentralizer), any pro renter can start digging around and pick the hosts he needs, but we need ways to make this information useful to the broader renter community. <strong>Phase III</strong> of the project will consist of delivering these benchmarks to every renter. I am willing to collaborate with storage app developers to provide them with customized professional APIs displaying this wealth of information about the Sia hosts, so they can create the optimal list of hosts tailored for their customers. Also, later this year I will deploy “Decentralizer PLUS”: an add-on for Decentralizer that will present preset lists of hosts like “<em>cheap and functional</em>”, “<em>performant</em>”, “<em>best for frequent downloads</em>”, and so on.</p><p>I have many more plans for the future. For example, once I can provide lists of hosts tailored to specific needs, why not directly provide the already formed contracts, including their maintenance? Thanks to <em>us</em>, a contract with a host can be created in a server, but then be used by another device to upload and download files just by sharing a small file (an idea by Luke Champine explained <a href="https://lukechampine.com/capabilities.html">here</a>). I aspire to create the <em>Keops Contracts Marketplace</em>, a solution that allows storage app creators to delegate on Keops/SiaStats the task of creating and maintaining contracts with hosts. No blockchain download, no complex contract logics: the app builder can focus on creating the best app experience on whichever platform he prefers, while SiaStats delivers the ready-to-use contracts through an API, after being paid in SC, BTC, or other cryptos.</p><p>SiaStats.info and Keops.cc aspire to be a reference source of data, insights and APIs for the broad community of Sia users. As I mentioned at the start of the post, the key in the world of big data is not having more numbers, but rather the ability to make the appropriate questions to obtain the correct insights. Do you have any outstanding question about the Sia blockchain or network? Is there any piece of data that would be valuable for your workflow or the app you are building? If you find the question, please do not hesitate to contact me (at <em>keops_cc@outlook.com</em>, or on Discord: <em>hakkane#0489</em>): the answer might be in the blockchain.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a56f79cebf6" width="1" height="1" alt=""><hr><p><a href="https://archive.sia.tech/numbers-figures-insights-siastats-a56f79cebf6">Numbers, figures, insights: a dive into the entrails of SiaStats</a> was originally published in <a href="https://archive.sia.tech/">The Sia Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Bitmain indeed mines coins in secret]]></title>
            <link>https://medium.com/@salva.enkidu_89587/how-bitmain-indeed-mines-coins-in-secret-2ea179e7ab75?source=rss-e9412ab75b3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ea179e7ab75</guid>
            <category><![CDATA[bitmain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[mining]]></category>
            <category><![CDATA[siacoin]]></category>
            <dc:creator><![CDATA[Hakkane]]></dc:creator>
            <pubDate>Fri, 27 Jul 2018 06:21:55 GMT</pubDate>
            <atom:updated>2018-07-27T16:50:57.192Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Hakkane (Salva Herrera) is an independent third-party blockchain developer and owner of </em><a href="https://siastats.info/"><em>SiaStats.info</em></a><em>. SiaStats is a website devoted to presenting reliable and credible real-time statistics of the Sia blockchain. By providing independently contrasted statistics about mining pools, it also strives to make the Sia mining sphere a safer space.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/528/1*D6Y3uc3K6SANVZvUdAJKbw.jpeg" /></figure><p>I often imagine blockchains as towers made of crystal. Bright, fascinating, landmarks looming above the fields of cryptography, data science and economics. Inspiring but also intimidating for those that approach them. Solid… yet completely transparent. The ledger of transactions is public, continuously validated by each participating full node. Every user can track funds as they jump from address to address or smart contracts as they get formed, used and expired. Blockchains do not need arbiters or regulatory organisms, as the rules that govern them are enforced by every node. The process and the results are transparently visible to every participant.</p><p>Unlike the Proof of Work blockchains they serve, ASIC manufacturers usually fail to provide the same levels of transparency. Unknown amounts of hashrate owned for self-mining, undisclosed sizes of the batches they sell (so customers can’t estimate their profitability, which ends in saturated markets where no miner gets profit) or mining in secret before the release of the hardware are among their most criticized practices. The lattermost case is especially concerning. Mining is a competitive process where all the miners share a fixed block reward according to their owned hashrate. When a next-generation ASIC is designed for a blockchain, its first owners will get most of the profits, as they quickly outcompete the previous generation of ASICs or the GPUs/CPUs they replace. By self-mining and not releasing the hardware to the public for a time, ASIC manufacturers can enjoy this privilege (and its profits) in exclusivity. In other words, they get a market advantage by outcompeting their own customers.</p><p>Being that blockchains are a paradigm of transparency, unsurprisingly multiple cases of friction and confrontation have aroused between crypto communities and manufacturers over the last 2 years. The world’s manufacturer leader, Bitmain, has recently undergone a campaign of, in their own words, “radical transparency” and “dialogue with the cryptocurrency communities” (<a href="https://blog.bitmain.com/en/transparency-policy-shipping-mining-practices/">1</a>, <a href="https://forum.z.cash/t/so-i-had-a-videochat-with-jihan-wu/29379">2</a>, <a href="https://blog.bitmain.com/en/antiminer-z9-mini-shipments-experiment-radical-transparency/">3</a> &amp; <a href="https://blog.bitmain.com/en/bitmain-sia-state-cryptocurrency-mining/">4</a>). On its <a href="https://blog.bitmain.com/en/transparency-policy-shipping-mining-practices/">most recent blog entry</a> , on July 25, 2018 we can read the following:</p><blockquote><strong>Zero tolerance policy against ‘secret mining’.</strong> (…) Bitmain itself has been unfairly accused of this practice. In the end, Bitmain values transparency and fair competition. We therefore remain opposed to this practice and maintain our long-held zero-tolerance policy regarding same</blockquote><p>This assertion, however, goes drastically against the way Bitmain actually behaved on the Sia network at the end of last year. This article is aimed to provide evidence, abundantly explained, that shows how Bitmain mined in secret Siacoins during the two months previous to the presentation of their Sia miner back on January, among other dishonest practices. As readers might not be familiar with the context, I find important to narrate the events and the disruption caused on the Sia community and blockchain by Bitmain when they introduced their Sia miners.</p><h3><strong>Sia meets Bitmain</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*3TTTgbg34OLMOiTyW2QEbw.jpeg" /><figcaption>“A bull in a china shop”</figcaption></figure><p>If I had to describe the arrival of Bitmain to the Sia community in a few words, I would say it was “like a bull in a china shop” (those unfamiliar with this English idiom will quickly understand the metaphor with the picture above). Without any previous communication, on January 17th, Bitmain <a href="https://twitter.com/BITMAINtech/status/953498092841590784">announced its Antminer A3 miner</a> for the Sia network and opened the sale immediately. Batch 1 sold out after a few minutes.</p><p>This should have not be an issue by itself for the community. However, 6 months before, the Sia core developers created an ASIC manufacturing subsidiary, Obelisk, opening pre-orders for what was believed it would be the first ASIC to hit the Sia network. Many contributors and community members in general participated on the pre-sale. The just-announced Bitmain A3 was going to hit the market first, many months ahead of Obelisk’s, ripping the expected profits of the latter. The last ingredient of the drama was the announcement that the Obelisk miner had on its design the backup capability of mining an alternative algorithm, and that a fork on the Sia network to embrace it would be enacted, invalidating Bitmain’s miners, if Bitmain showed a damaging behavior against the Sia project. While reserved for a case of emergency, many community contributors, coders and moderators pushed for an unconditional fork. Among those who purchased the A3 on the Bitmain’s flash sale, there were contributors, coders and moderators as well. The perfect storm.</p><p>I remember those days as the most stressful experience I have lived on the blockchain space. Being a moderator of the official Discord, I had to deal with the confrontation of the community while I had to deal with my own feelings but keeping them aside. The once peaceful and collaborative community stopped talking about Terabytes of data stored, file contracts and new features, abandoning itself for weeks to a situation akin to a civil war, including letters, confusing polls, lawsuits and death threats. To fork or not to fork? Either choice would tear apart the community. Either choice the community would lose members and contributors. Some left it already even after the final decision. My anxiety, ATH. In the end it was decided not to fork. The echoes of the decision are still conditioning the life of the community and will haunt it for many years. For those interested on further details about this episode, I recommend <a href="https://www.reddit.com/r/siacoin/comments/7s2whr/whats_going_on_a_nonpartisan_explanation_of_the/">this non-partisan timeline</a> by the Sia contributor <em>mtlynch</em> and <a href="https://www.youtube.com/watch?v=uwew58aXYU8">this recent talk</a> from cofounder of Sia at the Zcon0 conference</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h5XnIamfNTlz8o7sUZwu1g.jpeg" /><figcaption>Sia’s hashrate growth after the release of ASICs</figcaption></figure><p>The aggressive commercial arts of Bitmain did not help. While Bitmain <a href="https://blog.bitmain.com/en/bitmain-sia-state-cryptocurrency-mining/">claimed (and keeps claiming)</a> they limited the sale to one miner per purchaser, the reality is that this policy was never enforced: during the days after the sale the A3-batch 1, it was easy to find pictures of basements with multiple A3 and even purchase receipts with multiple units. While Bitmain also claims they did not saturated the market, analyzing the steps on the hashrate chart of Sia (above) it is easy to calculate batch 1 consisted on around 13,000 units (0.81 TH/s per unit) and batch 2 on 20,000. Subsequent Bitmain batches overlap with the shipping of another manufacturer, Innosilicon, so it is not possible to calculate the size of these batches. There are, however, no reasons to believe they were any smaller. Anyway, the 33,000 units of the first two batches were enough to sink the ROI of the Bitmain A3 purchasers, that started to complain how their expected ROI was extending to more than 6 months or even beyond a year. In the end, Bitmain killed the profitability of their own customers by flooding the network with more miners than what the network macroeconomics could sustain. And the hashrate kept scaling batch after batch of A3s and thanks also to the Innosilicon miners. Of course, this also ruined the possibilities of ROI of Obelisk backers.</p><p>Community consequences aside, releasing ASICs without warning could have had devastating effects for the blockchain functionality. Without an appropriate Difficulty Adjustment Algorithm (DAA), the dramatic increase in hashrate that followed could have provoked the inclusion of thousands of blocks before the next difficulty adjustment. The file storage contracts of the Sia network measure time in blocks, what could have provoked multiple contracts to expire prematurely without the renters having time to renew them, driving to data loss. We were lucky that an optimized DAA was introduced just a few weeks before the Bitmain announcement. Nevertheless, this illustrates the dangers of unannounced ASIC introductions.</p><p>On the same release day of the A3, AntPool, the mining pool of Bitmain, <a href="https://www.coindesk.com/antpool-adds-support-for-siacoin-mining-amid-bitmain-miner-launch/">opened a branch on the Sia network</a>, becoming the sixth known pool of Sia. On the first days of the pool, their API showed a very small number of workers (&lt;100) and hashrates around the 5% of the network. By March, the number of workers grew to several thousands and the hashrate to figures around 20% of the network, remaining in that level until the present date. All this information was recorded by SiaStats and can be accessed on <a href="https://siastats.info/pools/antpool">https://siastats.info/pools/antpool</a> . This apparent gradual grow of their hashrate, if true, would have been compatible with their vision against secret mining, as the pool only got organic grow after their batch 1 was delivered.</p><p>Nevertheless, it has to be noted that the Sia community detected during November and December sudden spikes of the network’s hashrate accompanied by bursts of blocks mined by unknown pools, representing up to 25% of the total blocks. Previously, the rate of these unknown pools remained under 5%. This data can be accessed at <a href="https://siastats.info/mining_pools">https://siastats.info/mining_pools</a> in the chart “Mining pools evolution”. Some members suggested the possibility of Bitmain, others suggested alternatives, like the manufacturer Baikal (including myself). The time has proven those blocks were indeed Antpool’s, as we will analyze in a moment.</p><h3><strong>When you try to hide your activity on the blockchain…</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*96pix4L5uO4tGwqNz6uYDQ.jpeg" /></figure><p>Despite the “radical transparency” messages from Bitmain, the fact is that Antpool is acting as the most opaque and dishonest mining pool on the Sia mining scene:</p><ul><li><strong>No signature on their mined blocks</strong>. Most of the pools in Sia use a single payout address for the block reward and a standard message on the arbitrary data field of the block. These two variables allow blockchain explorers to identify without doubt the pool that mined the block. Antpool instead has used so far more than 2600 different addresses and the arbitrary data of their blocks is an encrypted string, different each time. This prevents the independent validation of who mined the block.</li><li><strong>Failure on reporting blocks.</strong> In absence of a signature, explorers must trust whatever Antpool claims on its website. To the present date, Antpool has only claimed 687 blocks. <a href="https://www.antpool.com/poolStats.htm">Their list of claimed blocks</a> include multiple gaps of several thousands of blocks (see the image below). Considering their hashrate (around 20% of the network), these gaps are impossible statistically, meaning that they are refusing to report many of their blocks.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Q-OknGxHRnB7gBdZQGiaRg.jpeg" /><figcaption><em>Gaps in the reporting of blocks (blue lines) and false blocks (red boxes) on Antpool’s website</em></figcaption></figure><ul><li><strong>Fake claimed blocks.</strong> Their list of claimed blocks also include blocks owned without doubts by other pools. For example, blocks <a href="https://siastats.info/navigator?search=155407">155407</a> and <a href="https://siastats.info/navigator?search=152847">152847</a> are actually blocks of F2pool, and we can be sure of this because the block reward is being paid to the publicly known mining address of F2pool `<a href="https://siastats.info/navigator?search=dc0cb4f6cd8003ebf3d86cf0d9a5bbdf1e517c243238d26fd46709835a59c87338a380992d84"><em>dc0cb4f6…</em></a>`</li><li><strong>Fake reported hashrates.</strong> SiaStats has records of the average reported hashrate of each pool in a daily fashion, by scoring what their websites/APIs indicate every 30 minutes. It also keeps records of the % of mined blocks by each pool. We don’t have reliable information about Antpool’s blocks (reasons are above), but even if we assume that all the blocks mined by “Unknown” pools are Antpool’s too (tip: they are not, but let’s be generous), even the aggregated % of blocks does not match the hashrate reported by them (check the image below). While since the end of March they have reported roughly a 19% of the hashrate, the combined blocks of Antpool + Unknown represent roughly the 14%. That extreme bad luck is impossible considering we are analyzing 4 months of data. Instead, this means a misleading representation of their real hashrate, inflated more than a 35%. In PPLNS pools as them, higher hashrates drive to more stable payouts for miners. This means they are benefiting from this misrepresentation, deceiving miners making them believe they are more stable paying than what they really are.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZDCd-Rypfu4dDtJAs28APw.jpeg" /><figcaption>Antpool’s share of the network hashrate (as claimed on their website) vs their real rate of blocks</figcaption></figure><h3><strong>… but you forget that the blockchain is transparent</strong></h3><p>However, even if Bitmain/Antpool tries to hide and obfuscate its activity, it doesn’t mean we can’t take a deep look at the blockchain to reveal the complete picture. I recently developed an <a href="https://github.com/hakkane84/navigator-sia">open-source blockchain explorer</a> with great analytical capabilities, as well as methodologies to find the blocks mined by Antpool even in absence of claiming. The need of this specific tracking came from the goal of SiaStats about providing transparency to the mining sphere of Sia: if Antpool grows their percentage of mined blocks, the Sia community needs to know it. If there is another secret pool emerging, we need to segregate the blocks of Antpool from the blocks of this secret pool to score its size. The Sia network can’t be safe if the community stays in the dark while a pool grows to a 51% of the hashrate in secret.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fa7w49vWz6xAlBnovID00A.jpeg" /></figure><p>The methodology is not rocket science and it is simply based on following the movements of Siacoins on Antpool’s wallets. What follows is the explanation, explained in accessible terms.</p><p>Let’s start talking about transactions. In Sia, and many other blockchains, a wallet is composed by multiple addresses, and each address contains multiple “outputs” that need to be fully spent during a transaction. If Alice has a mining pool that mined 7 blocks in different addresses, with a reward of 100 SC each, she will have a wallet with 7 addresses and one output of 100 SC on each address. If Alice wants to send 650 SC to Bob, what the Sia wallet will do is collecting the 7 outputs, send 650 coins to Bob, and create a new output with 50 coins that will be sent back to a new address of Alice’s wallet (different from the 7 previous). In the real world, block rewards are never round and include many decimals (collected fees), while the amounts we send to people tend to be round. This makes the output that returns to the new address easy to identify, and addresses can be linked to a single wallet if one looks carefully to the blockchain.</p><p>Wallets have another feature: defragmentation. As Alice receives block payouts, once she has a lot of scattered outputs, the wallet will automatically consolidate them all into a single output in a new address of the wallet. This helps Alice to spend her coins in the future as the resulting transaction will be smaller in bytes. But it also means that all the input addresses, together with the resulting output address, become linked to the same wallet for an external observer.</p><p>Mining pool addresses are also easy to differentiate from the address of the miners that join the pool. The payouts that the pool sends to miners are sent in multi-output operations <a href="https://siastats.info/navigator?search=c843f47687292e556176c20fe55943ae4c22544c8723cff37b5ac52f7e1ca082">as in this example</a> (sometimes with hundreds of payout outputs), so we can discriminate when coins abandon the wallet of the pool. These payouts also include one remaining amount that returns to the pool’s wallet. We can’t say initially which is that output… unless it is merged again in a defragmentation operation together with other already known addresses of the pool. It is also easy to say when the pool sends the coins to an exchange (so we do not assign incorrectly an exchange’s address to the pool): while pool addresses receive coins whose lineage connect to the coinbase of blocks (aka block rewards), exchanges addresses connect, after defragmentation operations, “upstream” with addresses of users, easily identifiable too (as they include small and rounded transactions, not connected in a few jumps with coinbases)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aKs1NS-WlPxevyDCNGATIQ.jpeg" /><figcaption><em>From one claimed block, we can end up deducing many more</em></figcaption></figure><p>All the following links come from a blockchain explorer I own, SiaStats Navigator, but the transactions and addresses can be tracked as well using <a href="https://explorer.siahub.info/">SiaHub’s explorer</a>, of which I have no control. Let’s take a block mined by Antpool and claimed on their website (see image above) to perform a <strong>forward analysis</strong>: <a href="https://siastats.info/navigator?search=152134">block #152134</a>, mined on April 27th. Its payout was deposited on the address <a href="https://siastats.info/navigator?search=9176b0bca013a1e5aa68a0bda323acd571114340b30a0b6494ede008c1691b62175c83b1d348"><em>“9176b0…”</em></a>. The coins were transferred on April 29th on the transaction <a href="/service/about:invalid#zSoyz"><em>“762cde…”</em></a> to the address <a href="https://siastats.info/navigator?search=b5078ac37cc825e0ec7c5656643890c4a613a8c8339717edc49951e0b1d770521832eca517da"><em>“b5078a…”</em></a> in a wallet defragmentation operation. On May 17th this new address, together with more addresses being merged (more coinbases), sent 20 million SC to the address <a href="https://siastats.info/navigator?search=2b87bb81d76dafbc2f4911456959a0fc6732210b0a8ab76724ecd19f6e47594704ad4bef6e75"><em>“2b87bb…”</em></a> and immediately after that to the address <a href="https://siastats.info/navigator?search=91d23b063dffe707956826e106e7895dea863ca1cd5e9949418d88b780090ec27b8044e0b76f"><em>“91d23b…”</em></a>. This last address is what I consider a “master address” of Antpool, an address receiving round amounts of several millions, collecting block rewards and sending again millions that end up in payout addresses and cold wallets.</p><p>The most interesting thing of this address is that all the coinbases of their claimed blocks end up here, transiently. What if now we take the input transactions and trace back these coins up to their coinbases (a <strong>reverse analysis</strong>)? Will we be able to find new blocks not claimed by Antpool? The address <a href="https://siastats.info/navigator?search=6690294dc7ab23c27ea70bd637ca657ca9dd88fac8fc553d156f1348e04f31f39b0408d744c6"><em>“669029…”</em></a> sent 5 million SC to the “master address” on January 1st. Some time before, on November 30th, this mentioned address received its balance from the defragmentation operation <a href="https://siastats.info/navigator?search=cb3f5e930d3274fd9cf534778bde52d26ebbeff132a20dcc3b316a198ef15166"><em>“cb3f5e…”</em></a> that merged many coinbases with 35.88 SC from the address <a href="https://siastats.info/navigator?search=c5a4325a36030c4b0cad18907cb6e3bbcf6218c95512eeb174eb05a00f01aa77cb30df1f5e1e"><em>“c5a432…”</em></a>. Those 35 SC came from another defragmentation on November 21th, that collected block payouts of multiple addresses as <a href="https://siastats.info/navigator?search=065e02230cebc3e1df07d065a12522ee16aca87a5ffff77e2986496cc4d1722610d4af33d61e"><em>“065022…”</em></a><em>. </em>This last address was the recipient of the block reward of <a href="https://siastats.info/navigator?search=132592">Block #132592</a>. Overall, in just 4 transaction “jumps”, we found the payout of an old and not claimed block by Antpool, that goes back to November 20th. The following schematic is a summary of the presented analysis:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZyZHRi4nXHOxGq1EKb7sVg.jpeg" /><figcaption>From the direct analysis of claimed blocks, a reverse analysis can be performed to find secretly mined blocks</figcaption></figure><blockquote><strong>The oldest block we can track of Antpool is #132204, dated on November 17th, what means that Bitmain mined Siacoins in secret for exactly 2 months</strong></blockquote><p>Using an automated script, SiaStats found more than 2100 new blocks that Antpool rejects to claim. These blocks have been added to SiaStats databases, and more blocks are automatically being added as soon as their payouts are sent to known Antpool’s master addresses. The most interesting fact is that the oldest block we can track of Antpool is #132204, dated on November 17th, what means that Bitmain mined Siacoins in secret for exactly 2 months (as the Antminer A3 was presented on January 17th). Antpool collected 488 blocks in total thanks to their exclusivity using ASICs, using their brand new hardware in secret.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i9sKyeHsA9xIqfaPT8G3WA.jpeg" /><figcaption><em>The secret mining activity of Bitmain</em></figcaption></figure><p>The apparent organic grow of the Antpool’s hashrate mentioned above was an illusion: in those two previous months, there was days they mined up to 25% of the blocks. Interestingly, there are two gaps in these months that correspond with spikes of “Unknown” pools (“Others” in the chart) of similar size as Antpool’s block rate (Dec 27- Jan 7 and Jan15 — Jan 17, see image above). The payouts of these blocks (60 additional blocks in total) have not moved from their addresses on the last 7 months. As that amount of hashrate can’t be created out of the thin air to vanish forever after a few days, this obviously means those blocks were mined by Antpool too.</p><h3><strong>The crystal tower</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/857/1*kEvqJUCWrx94H5OI6To-wQ.jpeg" /><figcaption>Crystal Tower Palace, envisioned by C. Burton in 1851 for the city of London</figcaption></figure><blockquote><em>Bitmain could have recovered the whole cost of the ASIC development just by secret mining during those 2 months</em></blockquote><p>In total, 550 blocks were mined in secret during the 2 months previous to the Antminer A3 announcement, representing around 85 million Siacoins in block rewards. According to CoinMarketCap, the value of Siacoin oscillated during November and January on the range of 0.5 and 11 USD cents. Interestingly, the maximal historic value of SC was reached on January 6th, 11 days before the Bitmain announcement. Depending on the moment they sold their “warchests”, they could have obtained something between $0.4 and $9 million from the secret mining operation. According <a href="https://blog.sia.tech/the-state-of-cryptocurrency-mining-538004a37f9b">to some estimations</a>, the development of the A3 costed Bitmain $10 million. If they planned the trades carefully, this means they could have recovered the whole cost of the ASIC development just by secret mining during those 2 months. This, of course, on top of the $74 million in sales profit just from the first 2 batches ($2300 per unit and 33,000 units as we explained above).</p><p>I wish I had the tools and the expertise I have today back on January, so I could have released all this information when it was most relevant. I don’t know if it would have made any difference in the context of the debates of the Sia community, but I believe just having this information would have been valuable by itself. This is a cautionary tale for other blockchains: we need developers and websites tracking independently the health and the use (or misuse) of the blockchain, identifying the issues before they become a real threat with no turning back. Communities should also encourage and patronize with donations these projects, as most of the times these are just free-time projects without a business intention.</p><p>I hope this article was abundantly clear demonstrating that, opposed to Bitmain’s official message about transparency and absence of secret mining, Bitmain indeed mines coins in secret previously to the release of their mining hardware. Also, that this practice is a multi-million business for them. I also hope this article encourages developers across the cryptosphere to create and maintain tools that track misbehaving actors trying to hide on the blockchain.</p><blockquote><em>The big mistake of Bitmain is hiding inside a crystal tower, believing no one will peek inside</em></blockquote><p>It is shocking that this ASIC manufacturer decided to claim they do not mine coins in secret when the evidence of this lie is so evident on the blockchain. Returning to the metaphor of the crystal tower that opened the article, the big mistake of Bitmain is hiding inside a crystal tower, believing no one will peek inside<strong>. </strong>Fortunately for the rest of us, crystal is transparent.</p><p><strong><em>EDIT (27 July 2018):</em></strong><em> Some grammar corrections. Thanks to everybody who contacted me about them.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ea179e7ab75" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>