StakeCube in Numbers
The downtrend seems to continue, with Bitcoin now below $40,000 and threatening to crash significantly lower. Many people are puzzled by this situation, as prices don’t seem to be reacting positively to the avalanche of good news for Crypto being released lately. To give two examples, a few days ago it was announced that the Central African Republic has made Bitcoin their official currency, becoming the second country to do so after El Salvador last year. Also, Fidelity announced a product that will allow people in the US to add Bitcoin to their 401k accounts. Michael Saylor recently gave an interview in which he provided a good explanation for this paradoxical market behavior:
Basically it seems that traders and speculators are selling risk at the moment, while holders are not participating in the market at all. As the general economic situation in the world continues to deteriorate, we could expect more of the same, but at some point the bounce should come just as it did in 2020. As for StakeCube, a pretty tame week with very stable exchange volume and a small loss of value for SCC.
- User Count: 140,684 +0.29%
- Pool Value: 580.82 BTC -1.57%
- Daily BTC Mined: 0.024 BTC -4.00%
- SCC Price: $0.36 -7.69%
- SCC Market Cap: $3,911,000 -3.48%
- Daily Exchange Volume $99,617 +2.41%
- Alexa Rank 18,087 +639
This week it was DASHD, our newest listed coin, that topped the list with a weekly growth of 18%. Also ZNZ did pretty well at 13.7%.
These were the top 5 gainers for this week:
Top 5 Gainers
- DASHD +18.0%
- ZNZ +13.7%
- BIR +12.3%
- 777 +6.1%
- NAV +4.6%
Coins moving to the Earn system
As we explained last week, we are continuing the process of moving shared masternode coins to the new Earn system. You can read more about it here:
This week we will move DOGEC, ASAFE and KTS. Starting next Monday, shared masternodes will be deactivated and users holding those coins will start receiving daily Earn rewards instead.
We are also preparing some new listings. More on this in next week’s newsletter.
StakeCube Social Media
We want to remind you of some of our associated social media channels other than Discord and Telegram where you can interact with other community members.
First is our Facebook Community Group:
And our official Facebook page:
Check out also Derek’s Medium blog, where he publishes articles about StakeCube, including this one exploring the best SCP collections:
And this one regarding the full history of our native coin, SCC:
New BTC Wallet Version
This week we updated the BTC wallet to its newest version 22.214.171.124. This version brings some interesting updates such as support for the new taproot address type. Read more about it in this article:
Meatec announced that there would be a planned maintenance on the mining farm for the 25th of April that would last for one day. Simultaneously they announced that they would be installing a payout system update and that the system would be offline until the update is working correctly. Since then there has been no new information and payouts have not resumed yet. All we see for now is this message:
The launch of v1.1.8 was a great success! With over 100 downloads distributed mostly among Windows and GNU/Linux users (welcome aboard, Tux! 🐧) and not a single major bug reported.
Also following the release was a small boost in both NFTs and Tokens activity, nice!
If you haven’t yet upgraded your wallet, visit https://scpscan.net/download.html and upgrade in just a few seconds!
If you’d like to see some release notes / changelogs of the new improvements, visit our GitHub repository, and don’t forget to leave a star. ⭐
SCPscan is currently going through a revamp, in order to bring back better performance and scalability in parallel to the growth of the SCP network.
To make room for more advanced features, SCPscan will be moving from a fully client-side model to a backend-assisted model. This way, intense data-crunching will be performed in advance at server-side, helping SCPscan to load much quicker for the average user!
The backend will be fully open-source’d under the MIT licence, so go ahead and check out the GitHub repo if you’d like to watch progress! Or even setup your very own SCPscan instance.
These are this week’s selected features from the #feature-request channel
- Masternode Monitoring Service on Stakecube for tracking uptime/profit/etc.
- Support for multiple languages on the website.
- Add the ninth decimal place in the exchange to trade low value coins (lower than 1 sat).
We will examine these requests and determine whether they should be implemented.
Wallet Maintenance News
We updated the following wallets:
Previous version: 126.96.36.199
New version: 188.8.131.52
Please read the following information regarding the security of your account and funds:
The StakeCube.net team will:
- Never contact you first
- Never ask you to send them or move coins to some other address
- Never ask you for remote access or to install any third party software
- Never ask you for your password or 2FA codes
- Never provide support using direct messages
If you observe any of these listed behaviors, someone is trying to steal money from you. This applies to all of our social media channels. Our team will post official messages in the appropriate channels, and we only offer support through our ticket system on Discord.
Please, also take into account the following measures to keep your account secure:
- Enable 2FA in the account settings
- Enable IP verification in the account settings
- Use a strong password
- Change the password regularly
- Never share your password with others
- Never allow remote access to your devices
- If you require assistance, use only the official channels
- Download software only from verified sources
SCP Wallet is now signed with JSKitty’s public PGP key. This allows users to verify that the wallet has been cryptographically signed and approved by him. Even if our GitHub is compromised, the downloads are still safe as long as the PGP verification confirms that the files have not been tampered with. If you download SCP, please verify the binary against our developer’s public key: