<?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 Philip J on Medium]]></title>
        <description><![CDATA[Stories by Philip J on Medium]]></description>
        <link>https://medium.com/@snwzy?source=rss-ec3dbe3125e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*jgFMIYDTBHSc7CTe.jpg</url>
            <title>Stories by Philip J on Medium</title>
            <link>https://medium.com/@snwzy?source=rss-ec3dbe3125e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 07:08:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@snwzy/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[Scallet — Scala’s Web Wallet & Payment Gateway]]></title>
            <link>https://medium.com/scala-network/scallet-scalas-web-wallet-payment-gateway-db6a7e29d808?source=rss-ec3dbe3125e------2</link>
            <guid isPermaLink="false">https://medium.com/p/db6a7e29d808</guid>
            <category><![CDATA[scala]]></category>
            <category><![CDATA[wallet]]></category>
            <category><![CDATA[scalapay]]></category>
            <category><![CDATA[scallet]]></category>
            <dc:creator><![CDATA[Philip J]]></dc:creator>
            <pubDate>Tue, 05 Jul 2022 15:49:56 GMT</pubDate>
            <atom:updated>2022-07-05T15:49:56.364Z</atom:updated>
            <content:encoded><![CDATA[<h3>Scallet — Scala’s Web Wallet &amp; Payment Gateway</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TD1-kQFpzLy7iqrI.jpg" /></figure><h3>Introduction</h3><p>The most ancient among our community surely remember <a href="https://medium.com/scala/the-story-behind-stellitepay-12faddc8204">StellitePay</a>, the web wallet of the pre-Scala era… yes, that nostalgic time when Scala was still called “Stellite”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*6Dwme4qu97ZSp_5DHhMAXw.jpeg" /></figure><p>At the time, StellitePay was a simple and fast payment system that has been integrated into some applications: tip bots, a gambling site, and some other experimental apps.</p><p>Unfortunately, user adoption of StellitePay was limited at the time due to some technical challenges and other priorities… until now!</p><h4>The rebirth</h4><p>Releasing a web wallet made it to the top of our backlog in 2022, and we took the time to rewrite the entire frontend/backend and make it better, thanks to the feedback we got from StellitePay.</p><p>After our <a href="https://shop.scalaproject.io/product/re-re-re-branded/">re-re-rebranding</a> (please, meme us!), we had to find a new name for StellitePay.</p><p>We decided to go with <strong>Scallet</strong>, which is the combination of<strong> </strong>“Scala” and “wallet”.</p><h3>What is it?</h3><p>You may be wondering why we need a new wallet? It is true that we already have a few wallets — they all have their respective uses… but they also have their drawbacks.</p><blockquote>Scallet intends to be a simple browser-based wallet with everything you need in your daily life.</blockquote><h4>Everything I need?</h4><p>Yes, indeed! But what does that mean exactly?</p><p>Well, if you…</p><ul><li>need a wallet which is always synced</li><li>need to access your wallet from any device connected to the internet</li><li>want to accept/use Scala’s currency (XLA) in your shop or application</li><li>want a simple and fast wallet</li></ul><p>Then… Scallet is the right choice!</p><h4>How can I get mine?</h4><p>It all starts here: <a href="https://scallet.io/">https://scallet.io</a></p><p>Just register your email, username and password and you’re good to go!</p><p>Send some of your XLA to Scallet and have fun while sending it from your phone or even from your refrigerator web interface (did you know we are one of the only <em>real </em>CPU and mobile-friendly projects out there? Check out our <a href="https://github.com/scala-network/MobileMiner">mobile miner</a>!)</p><h4>Shortlink</h4><p>We have implemented a cool feature called “shortlink”, which allows you to define your own personal URL that you can share with your friends, family or users and makes it easy to receive XLA.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*mKlHm-kjp9W3Afy5PqaU0w.png" /><figcaption>Shortlink example</figcaption></figure><h4>How much does it cost?</h4><p>It’s totally free! There are no hidden fees.</p><p>You simply send and receive XLA like any other transaction on any other wallet, just like you are used to.</p><h4>Can I make Scallet my main wallet?</h4><p>We don’t recommend it. Even though we’re doing our very best to make Scallet as safe as possible, there isn’t a safer place than a cold wallet to which only you got access and no one else in the world.</p><p>Our <a href="https://scalaproject.io/">CLI/GUI/Mobile wallets</a> are better options to store your coins safely if you intend to hodl.</p><p>Scallet is meant to be used as your “hot wallet” to send/receive transactions whenever you purchase something or when you need a simple and fast wallet.</p><h3>Conclusion</h3><p>In the future, there will be additions to the app, such as Discord webhooks, but first and foremost we want to make sure that the core features work as intended and that people can use the app easily.</p><p>So please give us your feedback on <a href="https://discordapp.com/invite/djAFVvy">Discord</a> so we can improve the service!</p><h3>Community 👋</h3><p>If you have any questions or comments, feel free to contact us:</p><ul><li>Website: <a href="https://scalaproject.io/">https://scalaproject.io/</a></li><li>Discord: <a href="https://discordapp.com/invite/djAFVvy">https://discordapp.com/invite/djAFVvy</a></li><li>Telegram: <a href="https://t.me/scalaofficial">https://t.me/scalaofficial</a></li><li>Twitter: <a href="https://twitter.com/scalahq">https://twitter.com/scalahq</a></li><li>Reddit: <a href="https://www.reddit.com/r/ScalaNetwork/">https://www.reddit.com/r/ScalaNetwork/</a></li><li>Scala Mining Stats: <a href="https://scalastats.com/">https://scalastats.com/</a></li><li>Email: hello@scalaproject.io</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db6a7e29d808" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scala-network/scallet-scalas-web-wallet-payment-gateway-db6a7e29d808">Scallet — Scala’s Web Wallet &amp; Payment Gateway</a> was originally published in <a href="https://medium.com/scala-network">Scala</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We’re getting out of headlines]]></title>
            <link>https://medium.com/solydbot/were-getting-out-of-headlines-6addcba4b3eb?source=rss-ec3dbe3125e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6addcba4b3eb</guid>
            <category><![CDATA[solydbot]]></category>
            <category><![CDATA[hypebeast]]></category>
            <category><![CDATA[hype]]></category>
            <category><![CDATA[sneakers]]></category>
            <dc:creator><![CDATA[Philip J]]></dc:creator>
            <pubDate>Sun, 02 Jan 2022 17:00:12 GMT</pubDate>
            <atom:updated>2022-01-02T17:00:12.202Z</atom:updated>
            <content:encoded><![CDATA[<p>First of all happy new year to everyone! We really hope you’ve spent some time with your loved ones and had a good time while saying goodbye to 2021.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*espd3tKyRGuBrg0UApC0nw.png" /></figure><h3>2021</h3><p>The year with no excuses. The last year has been challenging more than ever and everyone (not only related to the sneaker scene) had to experience drawbacks in various areas.</p><p>So we’re really happy to see that you’re still here! The whole SolydBot team tried to make the best out of every possibility and we know that we had a rough time trying to get everything sorted that we wanted to.</p><p>Users have been losing interest across the whole spectrum of sneaker b0tting which we already stated in one of our last medium articles and it did continue throughout the last phases of the year. Even though we saw a slight increase of demand especially in the last month there is still plenty of room to get back.</p><p>That being said, we want to thank everyone who participated and helped Solyd in various aspects. We know that the amount of users decreased which resulted in less checkouts and less big success posts but we’re looking back to:</p><ul><li>120x “Xbox Series X” on MediaMarkt &amp; Saturn</li><li>A lots of dunks from various sites such as Snipes, Onygo &amp; Footlocker</li><li>Multiple restocks with clothing and shoes on Zalando</li><li>SolydBrowserfarm: Yeezy restock, 1x 3080 FE (however he did that), GameStop PS5 or Borussia Fan Jersey (😂)</li><li>Various Disney drops for dolls and stitch plushies</li><li>Size? and JD clips</li><li>Converse x OFF-WHITE last minute module</li></ul><p>and a lot of fun 🎉</p><h3>2022</h3><p>We’re looking forward to this year, we want to start immediately and with drastic changes. The goal is not only to get back on track but also adapt to the things we’ve learned since the 1.0 transition update which also include following milestones:</p><ul><li>Consistent Success</li><li>Rebrand</li><li>Clean and new GUI</li></ul><p>Those 3 key milestones will be the highest priority for the early months of 2022.</p><p>Success is the primary key of how a bot is getting valued so there is no way we can get the bot back without focussing on it in the first place and we will do everything needed to fulfill our “promises”.</p><p>A rebrand is needed to introduce the new and updated GUI, planning and organizing already took place a while ago during 2021 and it was initially planned for 2021 but the goal is to finalize and publish it Q1 of 2022. The rebrand will consist of major changes regarding the whole brand identity except the name which will (after a long period of evaluating) remain the same. More information about how/why/when are coming in the near future.</p><p>The GUI itself will have similar key features but in a more organized way and we’re trying to get in as many user requested features and optimization as possible (if doable and useful of course).</p><p>The goal here is to “finalize” the frontend of the bot and make it sustainable so we can 100% focus on the site logics only. The resulting frontend will hopefully (never say never) stay the same in the longterm so we won‘t need to update it any further.</p><h3>What’s next?</h3><p>Starting with this article we will switch to a new license system in the next days to reduce the user bounce rate and every user which got a license at this time will be able to keep it and renew at any given point. We won’t delete expired keys anymore but instead will only disable your access to the bot until you renewed your license for the next period. We want to make everything as seamless and easy as possible for our users.</p><p>We really hope you’re as stoked as we are for the new year. A lot has been prepared for 2022 which was already months in the work and we’re happy to share everything from time to time! Thank you for reading and stay safe everyone! 🏔️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6addcba4b3eb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/solydbot/were-getting-out-of-headlines-6addcba4b3eb">We’re getting out of headlines</a> was originally published in <a href="https://medium.com/solydbot">solydbot</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Numbers]]></title>
            <link>https://medium.com/solydbot/numbers-95828ba1e0ed?source=rss-ec3dbe3125e------2</link>
            <guid isPermaLink="false">https://medium.com/p/95828ba1e0ed</guid>
            <category><![CDATA[sneakers]]></category>
            <category><![CDATA[solydbot]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Philip J]]></dc:creator>
            <pubDate>Sat, 25 Sep 2021 18:07:24 GMT</pubDate>
            <atom:updated>2021-09-25T18:07:24.194Z</atom:updated>
            <content:encoded><![CDATA[<p>This article will sum up the last year and especially the last months of our development and will give a better insight on our current situation. Transparent, honest and without any flattering, as usual.</p><h3>Solyd Who?</h3><p>2 years have passed since we’ve launched and you might know SolydBot from the good old times when Snipes was our main site or when we were able to secure a bunch of sneakers from various sites with some weird approaches such as the “Akamai harvester” and other funny things.</p><p>But those times changed drastically and everyone knows that. We’re trying to keep up with changing sites, upcoming new solutions, bypasses, increasing security mechanisms and much more. It’s definitely not an easy business and there are basically two ways of handling the situation: <strong><em>Accepting the fate and close the project</em></strong> or <strong><em>working against the odds</em></strong>.</p><p>As you might have noticed already, more and more solution provider choose the former. We decided to go with the later and trying to keep up with the speed. How we’re actively trying to achieve this will be stated in the following.</p><h3>How?</h3><h4>Bot</h4><p>The bot is obviously our most important part and the core is getting better and better, we’ve been actively developing throughout the last 2 years on various things and we had to learn a lot of stuff which is happening in the background and you probably never heard of. We already told you about some of the stuff a in the last articles and we know that promises won’t take us anywhere so we prefer to not talk about this <em>“background stuff”</em> much since it wouldn’t really matter anyway.</p><p>If you’re familiar with http clients, tls protocol or the technical side of anti-bot solutions you already know the drill and we don’t need to dig any further ;)</p><h4>Sites</h4><p>Sites are essential for any solution and we supported various in the past, some were added, some were removed and some need to be tested to fully function as intended.</p><p>We’ve put a lot of work into the modules we’re currently providing and in the last months we’ve added new solutions like <strong>Footlocker</strong>, <strong>JD Sports </strong><em>(</em><strong><em>Size?</em></strong><em> + </em><strong><em>Footpatrol</em></strong><em> were added too and will be reactivated soon)</em><strong> </strong>and <strong>Zalando</strong> which are not even on our “official” site-list yet due to some major problem stated in the next paragraph.</p><p>A lot of work has also being put in <strong>Snipes</strong>, <strong>Onygo</strong> and <strong>Solebox</strong> and while Snipes and Onygo are working again, Solebox needs a bit more love to be fully functional. <strong>Disney</strong> is also working and provided checkouts to our users and sites like <strong>NBB</strong> or <strong>Converse</strong> were added shortly before drops but also struggled with the following problem.</p><h3>So whats the problem??</h3><h4>The problem</h4><p>It’s actually quite easy to explain and you will instantly understand the previous issues with common sense. The whole project has a big lack of running users. This isn’t only the problem of the users who are in fact profit oriented and if we’re not providing a stable solution they will eventually decide to use other solutions so it’s also a problem on our site which needs to be fixed from the bottom up.</p><p>Due to the lack of running users we aren’t able to sort most of the bugs or add new sites to our official site-list as we aren’t as satisfied to call them fully functional because we need a lot of data to iron out the problems which occur earlier/more often with more users running simultaneously.</p><p>There are currently about 370 Users in the discord with a somehow <em>valid </em>license. Around ~270 renewals, ~40 Lifetime and ~60 FNF licenses which aren’t really calculated since most of them are just chilling in the server. This sums up to around 310-ish people who could potentially <a href="https://www.youtube.com/watch?v=mw2kKyJu9gY&amp;t=131s">run</a> the bot.</p><p>Wouldn’t there be around 106 (as of writing this article) people whose license is about to be expire this number would actually be somehow okay but the number of actual users is decreasing steadily. We also skipped the renewal fee two times so there are people who basically never had to be charged for their license (<em>or at least got 6/12 months for free</em>) and therefore <em>“don’t care” </em>(wild assumption)</p><p>You may think,</p><blockquote>“But why aren’t you just running a lot on your side?!”</blockquote><p>and we in fact are running the bot, but in times of queues/timed out websites/RNG like errors, we really rely on various users with different setups to get a better understanding of whats working and what needs to be looked into.</p><p><strong>Small example:</strong> If <em>we’re stuck at the footlocker queue and thinking the queue system does not work properly we’re trying to fix this in the first place, but just one user with another setup and different proxies could prove that the issue doesn’t lie in the queue system but the proxies used.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aqxdxCwPPvPAucmTrq4o3w.png" /></figure><p>The image above just shows a timeframe of 7 days but this is actually “a good week” and the other weeks even during drops are really similar and it’s really hard to test modules or collect success in general with a low usage unless the users running large numbers of tasks/slots.</p><p>Implementing anti-bot solutions with such low usage is also quite risky since you’re switching over to negative profit really fast without enough success that could compensate the costs of aforementioned.</p><h4>The solution</h4><p>The problem above is really big but also easy to fix since all we need are users which are able to <a href="https://youtu.be/mw2kKyJu9gY?t=131">run</a> and test, we’ve had those people in the past and those were the people who verified the whole system. Once they hit a few pairs users started to realize that the bot is working and all they need to do is <a href="https://youtu.be/mw2kKyJu9gY?t=131">RUN</a></p><p>We know it’s frustrating if you’re running a setup which <strong>might</strong> not work 100% of the time, but the more you learn about the bot and how to <a href="https://youtu.be/mw2kKyJu9gY?t=131">run</a>, the better you and every one else gets. There are still a few people who exactly know how to run and they’re able to secure items during drops, we just ask you to do the same and experiment with the software we’re providing.</p><h3>Future</h3><p>We know we can’t blame anyone and blaming a group/person won’t bring us anywhere. We need to work together to make this whole thing happen otherwise it’s just a bunch of people trying to work for something no one wants to use.</p><p>The projects team is still motivated and we strive for nothing more but the best. A lot stuff is still planned and we’re also preparing for the next ph2se of the project which will be announced once it’s time for it.</p><p><em>As always thank you for reading! If you feel like you’re able to </em><a href="https://www.youtube.com/watch?v=mw2kKyJu9gY&amp;t=131s"><em>run</em></a><em> and you want to help us, we’re adding 5 monthly licenses for free which you can redeem at </em><a href="https://solydbot.io/user"><em>solydbot.io/user</em></a></p><blockquote><em>SOLYD-b074291f-babb-4ceb-a949-a92a7dc8ba0a<br>SOLYD-8882d8d3–542e-4ef4–9575–351342044a33<br>SOLYD-7f479ba3–4d2f-44cf-b593–0dd5579e8f84<br>SOLYD-6ba4292d-b0c3–4cae-9841–524cc617138e<br>SOLYD-806c0c90-e80b-425a-ab4e-0cee7ea06bd2</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95828ba1e0ed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/solydbot/numbers-95828ba1e0ed">Numbers</a> was originally published in <a href="https://medium.com/solydbot">solydbot</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fasten your seatbelts — May 2021]]></title>
            <link>https://medium.com/solydbot/fasten-your-seatbelts-may-2021-1ce3728f6d69?source=rss-ec3dbe3125e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ce3728f6d69</guid>
            <category><![CDATA[solydbot]]></category>
            <category><![CDATA[monthly-recap]]></category>
            <dc:creator><![CDATA[Philip J]]></dc:creator>
            <pubDate>Thu, 10 Jun 2021 16:01:21 GMT</pubDate>
            <atom:updated>2021-06-10T16:01:21.990Z</atom:updated>
            <content:encoded><![CDATA[<h3>Fasten your seatbelts — May 2021</h3><p>Welcome to our monthly recap of May 2021. Not much time has passed since the last recap but a lot happened behind the scenes and we’re preparing even more. The first updates have been made and a lot more is about to come. Further explanation in the following paragraphs.</p><h3>Preparation</h3><p>Most of you know that a good preparation is key for good execution so we started May with an intensive planning phase and stocktaking to get a glance of what&#39;s (not) working, where the key problems are and how to solve them. Due to many reasons this happened to become an underrated thing which quickly evolved into a big problem, which is why preparation and planning is more important than ever in our project.</p><p>For some insight: We came up with 4 important Topics “<em>Sites, Features, APIs and Dashboard”</em>, which can be split into smaller subtopics. It’s important to group the problems and determine dependencies to see what needs to be addressed first. In the past we often just chose the issue we wanted to work on without keeping an eye on more important issues. That’s why we are now assigning the issues directly to the team members and keep track of what the next important step is to move forward.</p><h3>Progress</h3><p>The May update included some new site additions such as Ambush (which we locked right after due to them enabling an unforeseen queue at drop), JD-Sports and Size?. These additions are just the beginning and we’re currently developing ~3 more sites which are soon to be released. As you already know these sites need to be tested and worked on in the future so we are looking forward to improving them.</p><p>We are also constantly working on already implemented solutions to improve their performance which was also case with this month’s updates. Many changes have been made to improve the bot even further in the upcoming updates and to prepare for the next releases.</p><h3>Future</h3><p>We are always speaking of the future and due to many factors it’s really not easy as developers to determine the exact time of “when” said future will happen. But as already stated above we have planned a lot recently and we are really looking forward to see those plans play out over the next weeks. These updates are always require lots of work but the whole team’s motivation increased tremendously and we’re thrilled to get everything done asap.</p><h3>Question of the month</h3><p>Our current approach is to work as close as possible with the users and one of their most asked question was:</p><blockquote>“Are demandware sites still being worked on?”</blockquote><p>And there is a simple answer: <strong><em>Yes</em></strong>. We are still working with/on demandware sites and there will be even more sites in the future as well. If you think of snipes/solebox the answer is also yes, but we are currently focussing on other sites and we will come back to our old demandware solutions after we have built some kind of buffer to keep the users busy with other sites instead of relying on those two while everything else is lacking our attention. We won’t drop them from our list, they will receive updates, they just need some more time and we are using this time for new sites atm.</p><p>This month was a good start and the whole team is excited to release everything we have planned. As always thank you for reading and we will hopefully see you in the next article!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ce3728f6d69" width="1" height="1" alt=""><hr><p><a href="https://medium.com/solydbot/fasten-your-seatbelts-may-2021-1ce3728f6d69">Fasten your seatbelts — May 2021</a> was originally published in <a href="https://medium.com/solydbot">solydbot</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transparency is key — October 2020]]></title>
            <link>https://medium.com/solydbot/transparency-is-key-october-2020-d7696c7a9a25?source=rss-ec3dbe3125e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7696c7a9a25</guid>
            <category><![CDATA[monthly-recap]]></category>
            <category><![CDATA[sneakers]]></category>
            <category><![CDATA[solydbot]]></category>
            <category><![CDATA[solyd]]></category>
            <dc:creator><![CDATA[Philip J]]></dc:creator>
            <pubDate>Tue, 03 Nov 2020 09:35:15 GMT</pubDate>
            <atom:updated>2020-11-03T09:35:15.889Z</atom:updated>
            <content:encoded><![CDATA[<h3>Transparency is key — October 2020</h3><p>It’s already in the title. Transparency is very important to us and we would like to give you some insights about what happened this month and why we’re more upset than ever.</p><h3>Problems over problems</h3><p>We have dealt with various problems from time to time and we grew on them in the past. Every project may face some downsides and it’s on us to fix the root of the problems to prevent them for happening again.</p><p>But some problems aren’t typical and in the whole scene of “automation software” things are changing rapidly and we need to adapt even faster. New competition means more time needed to be involved to keep a high standard for our product</p><p>So one of the big problems of October was time in relation to the problems.</p><h3>Finding new ways</h3><p>Most of you are typical software users and the idea of our product is that you don’t need to care about how bots work and the insight of the actual effort behind SolydBot is quite limited to you.</p><p>The supported sites need maintenance and as we already stated above it’s very time consuming to keep up with the competition. To get an advantage over other software we need to find new ways for our solution or improve the existing one. This splits up into two problems, we either stick to the current solution and try to make it more performant or we try to find new ways of achieving the same result with eliminating the limiting problems of the old methods.</p><p>The success of finding such new solutions is also not guaranteed so we might get stuck at the end without increasing the chances at all.</p><p>Some solutions also might lead to an advantage between our users for example methods that only work for certain regions. Most of the users think that if we add a specific region it’s also working for the others, which, unfortunately, is not the case.</p><h3>Internal miscommunication</h3><p>We never spoke of anything like this before and we will only show a small insight into this topic because of various reasons that are not necessary to publish.</p><h4>The staff team</h4><p>We’re working closely with our staff team to provide as much support as possible but in the last weeks the communication between the team decreased tremendously. This needs to be changed now and without any delay. First steps towards a better communication have been taken and we’re looking forward to improve the internal structure again.</p><h4>The development team</h4><p>We’re only a small team of developers and the work has increased over time so we might expand the dev team in the next weeks to increase our resources in terms of development.</p><h3>The current state</h3><p>The current state is anything but satisfying in comparison with the vision we have for this project. We need to accept that our supported sites are bugged and we need time to fix them completely so we can provide the solutions we were providing a few months ago.</p><p>We’re testing some stuff internally with our staff team and we want to make sure we don’t ship anything bugged again. We have tested the approach of letting the users test the software even if it might not work which led to more frustration in the community. Maybe this will change over time.</p><p>We have planned some options for new sites and we won’t let the bot die. The current sites are planned to work again and we are motivated to bring it back up where we have been. We decided to not leave the current sites behind yet but after a certain time we will just move over to get new sites into our collection while still being able to secure items on the current sites.</p><h3>Success</h3><p>We did have some success and some users were able to secure 2-digit counts of shoes but since the checkouts were only close to 1000, we won’t really get into detail for this month.</p><h3>Our birthday</h3><p>It’s been one year since SolydBot started and we have reached so much stuff in such a short time. We are very happy for every community member / tester / supporter / hater and every new friend. Thank you for your support and love towards us, we wouldn’t be here without you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M8PnemJv_5IJDcgfW46uqw.png" /></figure><p>We are looking back to a total of 24.664 checkouts in one year since creation and many more to come!</p><p>Thank you for reading and we hope everyone is doing fine in such turbulent times. Keep yourself and your loved ones safe and wear a mask!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7696c7a9a25" width="1" height="1" alt=""><hr><p><a href="https://medium.com/solydbot/transparency-is-key-october-2020-d7696c7a9a25">Transparency is key — October 2020</a> was originally published in <a href="https://medium.com/solydbot">solydbot</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The story behind 1.0]]></title>
            <link>https://medium.com/solydbot/the-story-behind-1-0-a7cefb0cfd01?source=rss-ec3dbe3125e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7cefb0cfd01</guid>
            <category><![CDATA[updates]]></category>
            <category><![CDATA[solydbot]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[stories]]></category>
            <dc:creator><![CDATA[Philip J]]></dc:creator>
            <pubDate>Sat, 05 Sep 2020 13:00:40 GMT</pubDate>
            <atom:updated>2020-09-05T13:00:40.563Z</atom:updated>
            <content:encoded><![CDATA[<p>This article will shed some light on the development and thoughts behind the past, the whole update, and the future of the project. Grab something to eat and have some chill minutes while reading this story.</p><h4>The beginning</h4><p>Back in October 2019, we (Philip and Kian), found ourselves in a McDonalds speaking about selling 10 lifetime licenses for the piece of software we’re making for fun. After having a good time laughing about it we kinda got serious about the joke and decided to give it a try. With around 100 Twitter followers at the time and nearly no real backup we set up a Shopify store and loaded 10 licenses just to find out they were sold out in ~1 minute. At that point, things got more serious since we didn’t want people to think we just scammed them. So we started learning javascript more seriously.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qbQ5EDrOQQaxBs5fhzYogw.jpeg" /><figcaption>One of the early versions of SolydBot</figcaption></figure><p>After a long time of searching for the right framework and testing different approaches we mostly messed around with the Electron framework which suited our needs best. Good to mention here is that most of the code was written between 1 AM and 6 AM and most of the sites didn’t work at all. So we kept trying, kept fixing stuff, and stayed awake until we eventually implemented some lowkey site just to realize that they changed their FCFS to a Raffle 4 minutes before the drop. Which was pretty much the rock bottom of our long night sessions. Ahh man, missing those nights. Not really.</p><p>We had many focusses and many sites we wanted to implement and tested since we had nearly no idea how they worked and how they could be “exploited”. Most of the implementations were pretty much ghetto code and rumor has it that some of them still contain some ghetto code from those 4 AM sessions. Who knows.</p><p>After some time and some testing, Kian was able to get a Bandana Bogo checkout with our Supreme implementation which worked unfortunately only for him. But still. This was one of the first successful checkouts we had and we knew that even though the implementation was bad, the system in fact worked.</p><h4>The turning point</h4><p>Some time passed and we stepped up our GUI game a little bit, got a fancy Akamai gen, improved our Captcha harvesting, and tried to get the first checkouts on Snipes. Snipes was/is one of the best-performing sites of Solyd and we spend a lot of time on it since not many bots implemented it and we saw potential in it. We managed to get some checkouts and after digging more into the system behind it we achieved one milestone after another. Our twitter also grew some serious reach and we were pretty happy at that point and blessed that we finally managed to implement something which was really helpful for our users and people were able to make real money with it.</p><p>Stores like Onygo seemed to be a pretty good choice as new sites so we implemented them too and after the already known to us switch of Solebox’ system we also implemented them pretty fast. So we found our main pages which we wanted to support in the first place. Not saying we didn’t want to add more, but at this time we were happy with the situation as it was.</p><h4>The downsides</h4><p>Every project has its downsides and speaking about them is an important part of the insight of projects like this. We are working with systems that change rapidly and that&#39;s why there are phases in which some things worked and phases where they didn’t.</p><p>Speaking of things that didn’t work. Every site changes over time and due to the fact that they are improving their protection, it’s just a matter of time until the bot doesn’t perform as smoothly, which means we need to find new ways or compromises. Finding new stuff is really time-consuming, not only the work of coding which needs to be done to test routines or particular ideas but also the time which is needed to learn a basic understanding of networking, connections, requests, and protocols. Some people already got a good understanding of what&#39;s happening when you click a button, so did we, but the fundamentals between the click and the response are getting way more complex the more you dive into the whole topic.</p><h3>The update</h3><h4>Can we start now?</h4><p>After digging into the history of Solyd and wallowing in memories you’re most likely pretty interested in the update so here we go. We didn’t want to talk a lot about the update nor did we talk about it at all in public. Only a few people knew what was happening and the rest has been left in the dark. We wanted to keep the supporters, we wanted to let the people upgrade who believed in the project as they did when there was nearly no bot in the very beginning. That&#39;s why we’re posting the update after the deadline of upgrading. So let’s finally start to talk about the actual product.</p><h4>Many options, much wow</h4><p><strong><em>“You don’t need to reinvent the wheel”</em></strong> was one of the approaches we didn’t follow. Instead, we tried to rethink the whole experience of botting and figure out new ways of making stuff easier and less prone to problems. After a lot of testing and rethinking, building, and destroying we came up with a new layout. <em>Shoutouts to a good friend of ours named Art who helped us during the very early phases of the process </em>❤️.</p><p>We know that most of the people in the scene prefer a CLI bot “because it’s faster” so it’s our mission to stick with the GUI and hopefully prove them wrong. We want to improve our performance more and more over time compared to the current version of the bot. With the 1.0 update, it should already outperform the old version.</p><p>So we created our new fundamentals which we were building on, that gives us many more options in terms of adding new features without entirely messing up the structure. We know it’s unconventional and it’s different but we sincerely hope you will welcome the changes.</p><h4>Recode everything</h4><p>The whole bot has been recoded. Not only a part of it. The GUI, the structure, how things work. Everything. That’s the sole reason behind why we aren’t adding new sites for this update. Simply because the whole focus was on remaking everything from scratch and adding new features in the upcoming updates. We also included nearly everything possible from our users&#39; suggestions which was very helpful to gather information about what is needed.</p><p>The <strong>1.0 Update</strong> will set the key essential for the future so that new things can be added much easier without using any ghetto code and also getting rid of the old one. The new structure isn’t made without any knowledge in JavaScript and the decisions weren’t made in a McDonalds. This update will set a new foundation for everything else to come.</p><h4>Bot it in men</h4><p>Last but not least we will show you some screenshots of the bot and explain a few things. Even though this is a final update we may change some colors/symbols or smaller parts of the structure in the upcoming updates. Depending on how good/bad they’re working.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cB2w5T4oUrqHIyBzrzHl4w.png" /><figcaption>The new interface (colors may vary)</figcaption></figure><p>The new home interface will face changes and it may look weird at first but let’s break it down. Most of the old bot tasks got plenty of similar tasks in a table and most of them can be grouped by profiles, proxies, and modes. For example, the task variations<em> (indicated by the size)</em> have a small color dot which lets you identify your proxied tasks. Once they’re started the whole task gets grouped by their status which results in a clean overview for any size of setup.</p><p>You can see all the sizes you are running for on one screen, no endless scrolling needed. You can see how many tasks you will run for each size and each item.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BRByy6Its1dZdYkwu8vFKA.png" /><figcaption>Profile section</figcaption></figure><p>The profile section will also face some serious improvements since you can now combine any profiles with any combination you want to create.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*odqYWXdRAF8c6lmksr8gxw.png" /><figcaption>List section</figcaption></figure><p>The list section can be used for anything list related such as proxies, coupon codes, or accounts <em>( for possible sites in the future… :) )</em>. The proxy colors are important for the home interface where you can spot the different task variants with their color.</p><p>The tool and setting sections contain things like the Browserfarm, Captcha harvester, user settings, log viewing export/import functionality, and enough room for the future. There are many smaller features which you will love so have fun to experience it on your own.</p><h4>Future</h4><p>These are a few basic innovations and a lot more things will follow. It’s now time to test everything and fix the bugs you find. We will definitely add more sites but we will add them step by step and make everything as transparent as possible. Our approach is to include the users as testers like before and finding new possibilities to help people getting their beloved products. The key foundations are set now. We can start to roll out new stuff from time to time, it’s not stopping here, it’s the exact opposite. We are currently in the new beginning of SolydBot. Sounds like a badass Batman title.</p><p>Thank you for reading! This article summed up most of the work in the last year <em>(especially the last months)</em> and you just got a glance about what’s happening in the background. We wanted to keep this as a secret so that no unnecessary hype is being generated. Now, have fun using and experiencing 1.0. We can’t wait to read your feedback and are especially excited the future of our project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7cefb0cfd01" width="1" height="1" alt=""><hr><p><a href="https://medium.com/solydbot/the-story-behind-1-0-a7cefb0cfd01">The story behind 1.0</a> was originally published in <a href="https://medium.com/solydbot">solydbot</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The struggle of life — June 2020]]></title>
            <link>https://medium.com/solydbot/the-struggle-of-life-june-2020-eaba9956c280?source=rss-ec3dbe3125e------2</link>
            <guid isPermaLink="false">https://medium.com/p/eaba9956c280</guid>
            <category><![CDATA[solyd]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[monthly-recap]]></category>
            <category><![CDATA[issues]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Philip J]]></dc:creator>
            <pubDate>Thu, 02 Jul 2020 10:29:45 GMT</pubDate>
            <atom:updated>2020-07-02T10:29:45.074Z</atom:updated>
            <content:encoded><![CDATA[<h3>The struggle of life — June 2020</h3><p>Welcome to the monthly recap for June 2020. This recap will be a bit shorter than the others since we had to fight with different problems in the background, more in the following.</p><h3>Cooperations &amp; Groupbuys</h3><p>In June, we did not restock licenses. However, we did have a groupbuy with our friends over at Cookbeast for their anniversary. Congratulations to them and we look forward to an even more successful future!</p><h3>Development</h3><h4>Bot</h4><p>We want to be as transparent as possible with you guys and that means we’re talking about the downsides too. SolydBot is still not in the state where we wanted it to be since the antibot protection of our supported sites is not working in our favors. Currently, we are working our way through get to the best solution we can provide to our users. To get to that point, there is a lot of experimental stuff going on. We are working our best to get to a position of where we feel confident before moving forward to the next, more serious, step.</p><h4>Updates</h4><p>Due to the fact that we had issues with different sites, there were fewer updates than usual, the reason being the adoption of new dynamics on supported websites.</p><h4>What about version 1.0?</h4><p>The question we receive the most is when 1.0 is being released and as much as we want it to happen there needs to be tweaks done before we can work further on this big milestone. This is not a step back but we need to make smaller steps first. Whatever happens, we are working on the big next step and it will happen.</p><p>We’re pretty excited for the day but please keep in mind it’s not only the bot itself that is being worked on, for a successful and smooth transition it also takes time and works for little things such as the dashboard, the implementation of smooth renewal transactions, organizational and administrational planning. We’re getting there.</p><h3>Growth</h3><h4>Twitter</h4><p>We nearly reached the 5000 followers on Twitter, which is beyond amazing. In the past months, we really had a strong increase in followers and a lot of new people found interest in our project which is great and we were really happy about the static growth of our community! Nearly 5000 followers are really impressive for us and we’re thankful for everyone who is supporting and following us on our journey.</p><h3>Achievements</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t4L4bND96QPlIPsTcKIwig.png" /><figcaption>Users checkouts for June 2020</figcaption></figure><h3>Success</h3><p>Compared to last month June wasn’t that successful in terms of actual checkouts. Users were ‘only’ able to manage around 4000 checkouts in total. But despite the fact that we had many issues, we are still happy that users were still able to check out a few products and we are looking forward to the next recap to see more checkouts again. Disclaimer: we only display this month&#39;s releases in the picture and exclude restocked shoes.</p><h3>Future</h3><h4>Question of the month?</h4><blockquote>Which sites will be added in the next updates? — Many people</blockquote><p>The second most asked question we get. New sites always mean new challenges and more time which needs to put in the maintaining. We want to ensure that the sites we support work as good as we can get them to work — we know for a fact we can do better — and that the users are able to use the bot in a way we want it to be. Which means more time for the current sites and less time for new sites. Eventually, we will release an extra article to present the hours and work spent to support or maintain a new site because most of the people don’t know that you don’t add 10 lines of code and a new site works fluently or simply add 1 line to have a new “bypass” so that you can check out hundreds of products. Once we feel confident in what we do, we will announce new sites we work on.</p><p>We thank you again for your time and we would be happy to see you in the next recap again hopefully with more good news until then enjoy your summer days and stay safe!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eaba9956c280" width="1" height="1" alt=""><hr><p><a href="https://medium.com/solydbot/the-struggle-of-life-june-2020-eaba9956c280">The struggle of life — June 2020</a> was originally published in <a href="https://medium.com/solydbot">solydbot</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A new hope — April(4) 20]]></title>
            <link>https://medium.com/solydbot/a-new-hope-april-4-20-6ec3be567260?source=rss-ec3dbe3125e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ec3be567260</guid>
            <category><![CDATA[monthly-recap]]></category>
            <category><![CDATA[solydbot]]></category>
            <category><![CDATA[sneakers]]></category>
            <dc:creator><![CDATA[Philip J]]></dc:creator>
            <pubDate>Fri, 01 May 2020 18:59:29 GMT</pubDate>
            <atom:updated>2020-05-01T19:07:32.575Z</atom:updated>
            <content:encoded><![CDATA[<h3>A new hope — April(4) 20</h3><p>Welcome to the monthly recap for April 2020. We hope you and your loved ones are staying safe during this pandemic and you are all pursuing social distancing as much as possible. With that being said, please wash your hands and enjoy reading our recap!</p><h3>Cooperations</h3><h4>Groupbuys</h4><p>As mentioned in our last recap, we closed the inquires for new groupbuys. However, in May we will possibly open them up again during the month. Keep an eye on our Twitter account.</p><h4>A helping hand</h4><p>We have found new cooperation with our good friends over at <a href="https://twitter.com/flexworkshop">Flex Workshop</a>.<br>Giving them a helping hand in providing their members with free and centralized Slots for Snipes. We thank Flex Workshop and their Developers/Owners for being an amazing team to communicate with and are looking forward to new and interesting projects.</p><h3>Development</h3><h4>Bot</h4><p>April has been a very adventurous month for us. A lot of old, new, experimental methods got clipped for various sites. Especially for Snipes, we did have our difficulties for some days but as we were on it very quick we also came up with a new method that has been working ever since. They really gave us a hard time and took a good amount of sleep from us as well. With PerimeterX being more active than ever before, we are working on the best solution we can come up with to assure a continuous and easy way to use SolydBot for Snipes and also Solebox. At the end of April, there have been difficulties with different regions for Snipes, but we are already on the right path to have them work again.</p><p>As of now, we definitely are not in the position that we are aiming for. There is still a lot to optimize to be back on where we have been in terms of stability but at least we can vouch for continuous and daily success (Fun fact: you can restart your tasks again lmao).</p><h4>Updates</h4><p>In the past months, we have been working day and night on SolydBot. Updates were pushed out quickly and with almost no time to test which is why we thought about giving ourselves a little bit more time to develop and also debug updates to assure more stable versions and also a more healthy life for us. The goal is to make our users be successful and we think this will be in our users’ and also our best interest.</p><h4>New Features</h4><p>This month we also added a key feature for captchas which is the AutoSolve product from AYCD. A powerful and amazing tool to get blazing fast and centralized captchas from a single hub.</p><h4>Site status</h4><p>One store that we put on hold for some time now did find its way back. The store in question is Solebox. Since we knew that their site system would change to Demandware we were already looking into it for a time so we were waiting out its eventual site switch. The result of our patience was a fully working testing implementation within 30 minutes of the switch which followed up an official update just about 45 minutes after that.</p><p>For now, we are collecting more data to not only optimize our support for Solebox but also have it as a stable and long-lasting supported site for SolydBot.</p><h3>Growth</h3><h4>Twitter</h4><p>This month we reached 3000 followers which is a great milestone for us, we want to say thank you for everyone that supports and believes us and our project. The support we have been getting was more than overwhelming and it has not stopped since. We look forward to the future of SolydBot and its role in the European community.</p><h3>Achievements</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xRPNIP3tje1f6YAXEgeBcQ.png" /><figcaption>Our success over the past month</figcaption></figure><h4>Success</h4><p>This month came with a lot of struggles and methods being clipped but with new updates and continuous development of SolydBot, our users were able to come up with a solid (hehe) amount of success for April 2020. With over 1300 pairs of AJ1 Mid Chicago Black Toes secured by our users, we are really happy to reach a milestone like that.</p><p>Our users also managed to secure a good amount of Motion Logo Hoodies from Supreme — even with only a very small amount of users running, which gave us confidence in our Supreme implementation. Of course, we still have to work on optimization for Supreme too, but we are on the right path.</p><p>A nice little thing to add: when making the developer version of the store Solebox switch, we were able to checkout 29 Yeezy Boost 700 V3 Alvahs while testing out the new module.</p><h3>Future</h3><h4>Beta Phase</h4><p>We have noticed that a lot of people are asking how long the beta phase will last for SolydBot so we want to give you an answer. As of now, we are working hard to optimize our currently supported stores to a point that we are more than satisfied with their implementations. Until then, we don’t feel like leaving the beta. But with that being said, our aim is to slowly find our way to the public release and try to be ready in 1 month. It’s a goal, not a set plan, so it could also take us a little longer. The perfect indicator would be, as described, a certain level of stability in the sites we are supporting.</p><p>We will announce how beta and renewal licenses are going to be handled soon enough and ultimately with enough time left before we actually move to a public version.</p><h4>Question of the month?</h4><p>We thought about interacting more with our supporters and the community in general so feel free to reply under the tweet for this recap and ask us a question if you like. The question with the most likes will be the question of the month and will be answered in the next monthly recap.</p><p>We hope you enjoyed our little read for the month and hope to see you on the next one too.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ec3be567260" width="1" height="1" alt=""><hr><p><a href="https://medium.com/solydbot/a-new-hope-april-4-20-6ec3be567260">A new hope — April(4) 20</a> was originally published in <a href="https://medium.com/solydbot">solydbot</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monthly SolydRecap — March 2020]]></title>
            <link>https://medium.com/solydbot/monthly-solydrecap-march-2020-48858a65acba?source=rss-ec3dbe3125e------2</link>
            <guid isPermaLink="false">https://medium.com/p/48858a65acba</guid>
            <category><![CDATA[sneakers]]></category>
            <category><![CDATA[hypebeast]]></category>
            <category><![CDATA[solydbot]]></category>
            <category><![CDATA[monthly-recap]]></category>
            <dc:creator><![CDATA[Philip J]]></dc:creator>
            <pubDate>Tue, 31 Mar 2020 16:28:17 GMT</pubDate>
            <atom:updated>2020-03-31T16:45:59.069Z</atom:updated>
            <content:encoded><![CDATA[<h3>Monthly SolydRecap — March 2020</h3><h4>Monthly recap, what’s that?</h4><p>Hello and welcome everyone, from now on you can easily keep track of our lows and highs, statistics, milestones and other behind the scenes stuff. We want to give you as much insight into this project as possible.</p><p>If you are interested in the making and growth of SolydBot, you are more than welcome to read our articles and leave us some feedback.</p><p>Let’s start with March 2020, shall we?</p><h3>Cooperations</h3><h4>Groupbuys</h4><p>Let’s begin with our cooperations of 2020s third month. In the past, we have already provided some group buys to selected cook groups but we have noticed a rapid growth of inquires. Here are the groups we have worked with this month:</p><ul><li><strong>SignalFNF</strong></li><li><strong>Kookgroep</strong></li><li><strong>SneakerSquadX</strong></li><li><strong>BestNotify</strong></li><li><strong>Cheesify</strong></li><li><strong>Project Z</strong></li><li><strong>The Essentials by Syed</strong></li><li><strong>ZeusNotify</strong></li><li><strong>MEKNotify</strong></li><li><strong>PY_RATES (scheduled for 1st of April)</strong></li><li><strong>VoltaNotify (scheduled for 1st of April)</strong></li><li><strong>Excluded</strong></li></ul><p>This month, we also announced our partnership with <strong>Cookbeast</strong>, counting our third official partnership besides <strong>Astral</strong> &amp; <strong>CookLabIO</strong>. We will pause the group buys inquires with <strong>Excluded</strong> being the last group to be chosen for a group buy with renewal licenses for the moment.</p><h3>Development</h3><h4>Bot</h4><p>This month started with the 0.7.10 update. Our focus was to work on our Snipes &amp; ONYGO implementations and so we announced our drop/restock mode. These modes came in clutch for the following restocks during the month and our users were checking out daily (please don’t restart your tasks though, ffs).</p><h4>Website</h4><p>After switching to our new server host and completely reworking our dashboard, users can now unbind licenses from their Discord account and device.</p><p>This new dashboard also adds our success page, which is a great replacement for a public Discord webhook channel since it’s rate limited.</p><h3>Growth</h3><h4>Userbase</h4><p>With currently around 300 users and at peak over 130 users running simultaneously, we are trying to rotate the userbase by removing inactive beta license holders to invite new people that would love to use SolydBot.</p><h4>Twitter</h4><p>We have reached another milestone this month, 2000 followers on Twitter. Thank you to all our supporters, we are truly overwhelmed by all your messages and are grateful for everything, especially for our users that believe in us and are posting their recent success.</p><p>We also published a form for interested users of the community to sign up for a beta license which really blew up and positively overwhelmed us! The form is currently closed but if you already entered, make sure to send us a DM with the code word <em>“TIME FOR APRIL” and your entered e-mail address</em>, we might have something for the quick ones :)</p><h3>Achievements</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*afFV1UH-AmnnAEOGwJ5PQA.png" /></figure><h4>Success</h4><p>We recently had our first real bigger success on 2 of our supported sites. Our users were able to check out lots of Yeezys and our ONYGO implementation went so smoothly that we were able to secure 20 of 22 pairs of the Air Jordan OG Melody Ehsani on release.</p><p>After a lot of testing over the months, we have fine-tuned our Snipes logic which is showing its power in our recent users’ success.</p><h3>Future</h3><h4>Next month</h4><p>Our goal for the coming days and month is to optimize the other sites we are supporting. We are constantly working on pushing new updates, working closely with our users’ suggestions and implementing new frequently asked- for features. We are looking forward to our next recap to see how far we’ve come until then.</p><h4>Users &amp; Licenses</h4><p>We are setting a limit for new renewal licenses for the next while. From now on until further notice there will be no new renewal licenses sold unless communicated via <a href="https://twitter.com/solydbot">Twitter</a>. Beta licenses will still be provided but only in limited quantities.</p><p>Thank you for reading! We hope you liked our first recap and we would welcome you in the next one, if you feel like it you can also leave some feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48858a65acba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/solydbot/monthly-solydrecap-march-2020-48858a65acba">Monthly SolydRecap — March 2020</a> was originally published in <a href="https://medium.com/solydbot">solydbot</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Milestones]]></title>
            <link>https://medium.com/scala-network/recap-3-milestones-b3e1fe83bb3?source=rss-ec3dbe3125e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3e1fe83bb3</guid>
            <category><![CDATA[scala]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[recaps]]></category>
            <category><![CDATA[milestones]]></category>
            <dc:creator><![CDATA[Philip J]]></dc:creator>
            <pubDate>Mon, 27 Jan 2020 18:07:01 GMT</pubDate>
            <atom:updated>2020-03-16T19:14:36.043Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DSRmMsxqEvHMJPKy.png" /></figure><p>The recent developments have brought us closer to our milestones and the vision of the project.</p><p>The mobile miner is nearing the public beta release, <em>IPFS </em>is officially implemented within the <em>Scala </em>daemon, <em>ScalaPay </em>has received some UI improvements and we are reviewing the final draft for the upcoming website.</p><h3>Mobile Miner public beta</h3><p>We are currently debugging the mobile miner using feedback from our comunnity supporters<em>.</em> The improvements include updates on the UI, fixing bugs and the addition of a payout widget. We’ve also had some issues with <em>ARMv7</em> devices, so we have decided to put that aside for now, in search of a solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kx32AGihSjzLPkq4kO2ksQ.jpeg" /><figcaption>Current state of the Mobile Miner</figcaption></figure><p>Other than that, the mobile miner works pretty well, and we’re looking forward to the public beta release.</p><h3>IPFS got implemented into the blockchain</h3><p><em>Scala </em>node-lists and checkpoints are now stored in a peer2peer, distributed network hosted by a conglomerate of blockchain supporters. This addition not only makes the network more secure, but also easier to maintain. Further information about <em>IPFS </em>technology can be found on their <a href="https://ipfs.io/#how">website</a>.</p><h4>You can now also store and share files via IPFS.</h4><ul><li>After the daemon is synchronized, simply go to: <br><a href="http://localhost:5001/webui">http://localhost:5001/webui</a></li><li>You can access your shared files via: ipfs.io/ipfs/fileHash</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pJMJghGyjoLmFP69.png" /><figcaption>IPFS dashboard view</figcaption></figure><p>So make sure you downloaded the latest <a href="https://github.com/scala-network/Scala/releases/tag/3.0.0.4">daemon </a>and <a href="https://github.com/scala-network/scala-electron-gui/releases/tag/1.5.0">wallet</a> and try it out!</p><h3>Scalapay is online again</h3><p>We have decided to put <a href="https://scalapay.io/">Scalapay</a> back online so that you can use it while we keep working on it behind the scenes.</p><h3>The new website</h3><p>We are currently adding a Mobile Miner section along with a few minor tweaks to some explanations to the upcoming website.</p><p>As we already mentioned, lots of things have changed in the past and we would like these improvements to be reflected on our website, in order to have a more consistent online presence.</p><p>So let’s hope that this will be our last iteration. :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*fIf8WMBIUSSzJenW51pYZQ.gif" /><figcaption>We made a privacy meme!</figcaption></figure><p>Have a nice week everyone! Keep mining!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3e1fe83bb3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scala-network/recap-3-milestones-b3e1fe83bb3">Milestones</a> was originally published in <a href="https://medium.com/scala-network">Scala</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>