Not coming at you or anything, however I think it's important to provide clarity around your note saying "this is not what the staking rewards will be."
There are no "staking rewards". shdwDrive does not have "staking rewards". shdwDrive will never have staking rewards.
Staking rewards in web3 are about creating inflationary token economies and generating artificial scarcity by encouraging holders to lock up their tokens, thus lowering circulating supply. In web3 staking, new tokens are minted and distributed to participants for locking up their assets. While this incentivizes participation and creates the hype that CT has become so used to, it does nothing to tie the token in question to real-world utility or revenue generation.
shdwDrive takes a different approach. Instead of inflationary rewards, operators stake $SHDW as collateral to access the network. The value they receive isn’t from token emissions but from actual customer revenues. When users pay for decentralized storage, the fees (in $USDC) are distributed programmatically to operators based on their contributions.
This is real revenue sharing, not speculative rewards. Operators must actively provide storage and maintain uptime to earn. Plus, the $SHDW stake serves as a slashing mechanism to ensure network integrity—bad actors risk losing their collateral.
In short:
🔹 Staking in web3: Often inflationary, speculative rewards, designed to increase token price.
🔹 Revenue sharing in shdwDrive: Tied to real fees, sustainable, operates completely independent or token price, and merit-based
This model aligns operator incentives with real user adoption, creating a sustainable ecosystem driven by actual utility and platform growth.
Unlike many web3 projects, shdwDrive’s revenue-sharing model isn’t designed to reward token holders, create new holders, or pump $SHDW demand. Why? Because $SHDW has never been designed to be a store of value—it was built to support the shdwDrive network, full stop.
Here’s the proof:
Fixed supply token: No inflation, no minting.
No private sales: No VCs, no big investors.
No team allocations: The GenesysGo team owns zero $SHDW tokens.
By the time of the IDO (Jan 3, 2022), 80% of $SHDW was already controlled by Solana on-chain programs, not the team. A few months later, the remaining 20% was burned with not a single token being spent or sold by the team. Easily verifiable on-chain.
$SHDW exists solely to integrate with the network. Operators stake it as collateral to secure their spot, and slashing mechanisms ensure integrity. The real value is the network and the revenue sharing in $USDC as the network grows—not speculative tokenomics. Hence why it's only operators that can earn.
This is why shdwDrive is powered by mobile devices, to ensure everyone (not just the tech savvy) can easily participate in a way that is not at all resource intensive (unlike server based infrastructure). Yes, people might go out and buy a bunch of phones but they're choosing to take on that additional cost. However, taking on those additional costs to support the network is not mandatory.
A person can use their existing mobile device and run it as a shdwNode exclusively at night, or while they're at work, or whatever. Slashing happens as a result of malicious activity, it isn't a mechanism for enforcing uptime and the network is smart enough to adjust how storage is allocated across the network in order to account for this "on again/off again" activity.
The takeaway: shdwDrive is about real utility, not hype or holding. It’s a decentralized network built for operators and users, powered by transparency and a sustainable economic model.
Are you a member of the @solanamobile who owns a #Solana Saga? Are you attending @SolanaCrossroad?
You might want to consider bringing your Saga with you to XRoads and attending @Frank_theTrader's presentation Friday afternoon local time (May 10th).
Just sayin' $SHDW
$SHDW Drive’s Testnet2 draws to a close tomorrow! We’re beyond grateful to everyone who participated. 🙏🙏🙏
Here’s some housekeeping items and a recap of the learnings from Testnet2.
Housekeeping:
- The Testnet2 network will continue to run but tomorrow is the last day node operators will earn rewards.
- There is no deadline to withdraw staked SHDW, so don’t worry if you leave it sitting there.
- Over the next few weeks the team will be parsing the data collected for the shdwPoints system. There were a lot of wallets which tried to game the system by playing a SHDW shell game. Rather than reward dishonest behavior, the team has decided to take the time to manually track the wallets in question to ensure that no one gaming the system gets rewarded.
Testnet2 Recap:
- The biggest takeaway the team had from Testnet2 was the sheer amount of junk that had been built into D.A.G.G.E.R.’s original codebase. We were aware that there were areas for improvement but deciding where to begin was a task in and of itself.
Testnet2 and the shdwOperators participating in the network did exactly what we had hoped they would do, they dramatically sped up the development process. Building and leaning in an academic environment is nice, but nothing beats the knowledge gained from real world experience.
A huge amount of our team’s effort during Testnet2 has been focused on ripping out some of the more bespoke artisanal elements of D.A.G.G.E.R.’s codebase and replacing them with code that’s capable of running in a production level environment.
Because of Testnet2 we’ve been able to identify issues and apply fixes to the erasure coding schema, the internal p2p networking, as well as the core consensus mechanism.
In fact, it was the work that went into rebuilding D.A.G.G.E.R. which acted as the catalyst for what we’re deploying at @SolanaCrossroad!
As said, these leaps forward would not have been possible without the efforts of everyone who participated in Testnet2! So, once again, a huge thank you to everyone who submitted issues and provided logs!
As we move forward through the rest of 2024, we’re looking forward to continuing to apply the outputs from Testnet2 towards the full deployment of shdwDrive v2 slated for the middle of this year!
#Solana #web3 #DePIN #SHDW
Very excited to have the opportunity to unveil the next major leap forward for $SHDW Drive on-stage at @SolanaCrossroad!
This will be a literal world first for #web3, don't miss it!
Crossroads tickets are 25% off for the next 48 hours only if you use code "solana" at checkout!
If you’ve been a member of the $SHDW community for a while then you know that when @GenesysGo goes quiet for a bit it’s bc we’re working on something big…
@SolanaCrossroad is gonna be 🔥🔥🔥
#Solana#web3#DePIN#SHDW
You peasants, ETH gas fees are high because people are using it kek, everyone wants "luxurious" blockspace
"Aren't they actually high because of an inefficient design? For example: coal engines vs electric engines? 12 TPS isn't a lot of usage"
Well Soylana boys are just lying, fees aren't even $400 anymore to begin with lmao
"Hmm they still range from $250-$500"
Yeah well the L1 is just for rollups, not users. Otherwise the L1 becomes centralized. Users must use the L2s.
"But...L2s currently are all centralized, governed by multisigs, with centralized sequencers and almost none of them except Arbitrum even proofs."
That's okay, it will get decentralized over time (probably).
"But won't Solana also get more decentralized over time due to obvious things like Moore's law and client improvements?"
Sure, but Solana goes down all the time.
"But Solana went down once in the past 365 days while most L2s had several outages and you told me that users must use the L2s?"
These are just growing pains. Solana also has high inflation.
"That's simply if you don't stake your tokens, there's tons of economic activity on the chain in any case. Market cap is like 1/10th of ETH."
There's activity on L2s too, much more than Soylent chain. So many airdrops.
"But when I try to use those, the fees on the L2s spike and they're higher again? Solana also has many tokens upcoming"
Yeah well 4844 is coming to reduce those fees too
"4844's magnitude of increase still won't cause the same performance characteristics and if the price of ETH goes up causing gas markets demands to go up, the net difference seems like it'd be negligible?"
You can just use Celestia for DA then
"But that would have weak security characteristics which is why you told me to use Ethereum in the first place? Celestia economic security was flipped by a dog coin on Solana"
Bro the people who care about security that much can just use ETH mainnet
"see beginning of thread"
🧵DAGGER / ShdwDrive v2 THREAD🧵
║Storage & Compute #Depin project, by @genesysgo.
► Key points of what this project, once mature, will look like.
― Statut : public Testnet on #solana
🟥DAGGER
🟧ShdwDrive v2
🟨ShdwNodes │ $SHDW
🟩Testnet
🟦Conclusion
🟪Sources
LET'S GO🔥
A refresher about the mechanics behind the $SHDW token:
1) Token Utility and Value Accrual:
SHDW is designed such that its value is directly tied to its utility.
Value accrual to the token truly begins when the full utility (i.e. the shdwDrive v2 platform) has been deployed.
https://t.co/OxvT8unOlr
2) shdwDrive v1.5 vs shdwDrive v2:
v1.5 (the currently deployed version of shdwDrive) is and has always been a stepping stone.
shdwDrive v2 (powered by D.A.G.G.E.R.) transforms the platform into a fully decentralized trustless permissionless network which drives platform revenues directly into the hands of SHDW holders.
https://t.co/CmKOuctks1
https://t.co/cwjn8Z5CUo
The release date for v2 is currently targeted for end of Q2 - first week or two of Q3.
https://t.co/m44CEheWBQ
3) shdwDrive v2 Native UI and Platform:
Part of the purpose of shdwDrive v1.5 being deployed as a placeholder is to gather learnings.
One of those learnings is the importance of deploying a native shdwDrive UI to ensure a consistent user experience which in turn will make onboarding new users to shdwDrive v2 significantly smoother.
4) Laying the Foundations:
Everything the team is doing today is focused on laying the foundations for tomorrow in order to drive adoption of both the tech and the token on a mass scale.
- Exchange Listings (in progress).
- Having the proper legal and regulatory frameworks in place to comply with the laws governing data storage (a must in order to win enterprise customers).
- Ensuring scalability of the tech (hence testnet2).
- Tokenomics designed to capture platform growth as value and drive it to token holders (in place).
Building a data storage platform catering only to the most fanatical hardcore red-pilled would be incredibly shortsighted.
Everything our team does is focused on the long game, it is why GenesysGo has been thriving in the #web3 space for nearly 3 years and why we will be thriving in web3 for the next 30.
As a trusted provider in the web3 data storage space, GenesysGo is committed to upholding the highest standards of data privacy, security, and sovereignty. Our commitment to our users guides every decision we make, including the difficult ones.
Our commitment to being as transparent as possible with our users guides statements like this one.
Recently, we've had to address significant concerns regarding @sdrive_app's abuse of users of the shdwDrive platform, specifically related to the architectural choices and practices of the SDrive platform.
We believe it is crucial to clarify these issues to our community and the public.
Architectural Concerns:
SDrive has chosen an architecture that commingles user data into a single account. This is directly contradictory to the ethos of #web3.
shdwDrive is built based on the ethos of "Your Keys, Your data."
Unfortunately, users uploading data via SDrive unknowingly give up control over their own data and surrender it to SDrive's founder, @web3sven.
When a user creates a storage bucket directly with shdwDrive the user generates a storage bucket that can only be controlled by the wallet used to create said bucket.
In contrast, when a user creates a storage bucket via SDrive they are merely creating a user profile on SDrive's front end. Their data is then uploaded to SDrive's private servers for processing and modification.
SDrive's servers modify the uploaded data by changing the ownership metadata tags. This change strips the user of control of their data so that it can be stored in a singular storage bucket controlled exclusively by @web3sven.
This is similar in nature to how FTX structured customer deposits. Instead of each account owner having their own account storing specifically their own funds, all customer funds were deposited into a large pool that FTX had sole control over.
Obviously, this architecture did not work for FTX and it does not work for SDrive. It is lazy at best and criminally negligent at worst.
This design not only poses a risk to user privacy but also significantly hampers our ability to comply with local laws and regulations on an individual basis. Data sovereignty — the principle that data is subject to the laws of the country where it is located — is not just a cornerstone of our platform, it is a requirement that all data storage providers (decentralized or otherwise) are legally required to adhere to.
Unfortunately, SDrive's approach undermines this principle, making it extremely challenging, if not impossible, for us to ensure compliance with important regulations such as DMCA, CSAM, and various local data protection laws.
shdwDrive's design ensures that if one user is storing things like illicit materials which sexually exploit children that poisoned data can be isolated without poisoning the data of all other users. Unfortunately, SDrive's architecture makes this kind of surgical precision impossible.
Violations of the shdwDrive Terms of Service:
The SDrive Terms of Service as of February 11th, 2024 (located here: https://t.co/nczGWXHYiA) requires SDrive users to grant broad rights and authorities over the use of their data and their intellectual property to SDrive.
By granting itself broad rights and authorities over user data through its terms of service, SDrive operates in direct violation of GenesysGo's view of data sovereignty as well as the shdwDrive Terms of Service which govern the behaviors of builders utilizing the platform. Such practices are not only against our ToS but threaten the very integrity and trust we've built with our community.
While @web3sven can claim that our interpretation of SDrive's ToS is incorrect, legal analysis of his ToS and SDrive's architecture (whereby SDrive modifies the meta-data of user uploads to redirect all data to its private storage bucket) would disagree.
SDrive has continually refused to put the required processes in place to ensure that its architecture is compliant with the laws and regulations which govern data storage.
Finally, we would like to state unequivocally that, while protections to prevent the spread of illicit material that sexually exploits children is not technically a legal requirement, it is our belief that it is a moral requirement.
SDrive's stance that CSAM (Child Sexual Abuse Material) scans represent an attack of censorship has no place in the shdwDrive community or on our platform.
There is no reality in which aiding in the defense of children by preventing the spread of illicit material is of a similar importance as censorship resistance.
Any users of the shdwDrive platform who disagree with the above statement should cease using our service immediately. We do not want you as our customer.
Our Response:
We have spent the past ten days in discussions with our legal team and have relied heavily upon their advice in deciding how best to move forward.
We have reviewed the following:
- SDrive's architecture
- SDrive's Terms of Service
- @web3sven's months long history of actively spreading lies and misinformation about our team in channels both public and private.
- Traffic logs from our DNS provider.
After reviewing these items we were strongly advised to take action to protect our platform and users. Failure to take action would leave us exposed to serious legal risks which would ultimately undermine the trust our community has placed in us.
Based on advice from counsel, our DNS provider, Cloudflare, no longer serves traffic requests from the SDrive site. The data in and of itself is still present and has not been deleted. We do not have the ability to delete user data once it has been stored in a storage bucket.
Our actions have been modeled after the actions taken by web3 storage providers who have existed in the space long before us.
Both Arweave and Filecoin have had similar processes in place for years and there have already been several cases in which these processes were used establishing precedent.
For example:
https://t.co/cRXixy5w93
and
https://t.co/XXce5QY4tu
It is also important to note that this action was targeted and measured. It aimed solely at addressing the misuse of our platform by SDrive. Claims made by SDrive's founder that GenesysGo has blocked an entire country or engaged in censorship are wholly inaccurate and misrepresent the nature of our actions.
We want to be clear: our platform's integrity, the privacy of user data, and adherence to our foundational principles of ethics and legal obligations cannot be compromised. While we regret any inconvenience this situation has caused to users of SDrive, our priority remains the safety and security of the digital environment we provide.
Fortunately, SDrive traffic makes up ~0.1% of all shdwDrive traffic and so we expect the impact to be minimal.
Moving Forward:
GenesysGo is dedicated to resolving these issues in a manner that aligns with our commitment to data sovereignty, user privacy, legal compliance, and ethical behavior.
We remain open to dialogue with SDrive's founder @web3sven, provided there is a genuine commitment to addressing these critical concerns and making the necessary changes to their platform architecture and data handling practices.
Unfortunately, after fully reviewing hundreds of pages of Discord messages (posted in private channels but sent to our team in secret by members of those private channels) and his X (Twitter) posts our legal team believes that any commitments made by SDrive's founder would be disingenuous and unlikely to result in meaningful follow through.
We thank our users and stakeholders for their understanding and continued support. Protecting your interests and maintaining your trust is paramount to us, and we are committed to keeping you informed as we navigate these challenges together.
#Solana $SHDW #DePin
Decentralizing Big Tech w/ @GenesysGo
Just like bitcoin decentralized the person to person payment structure, ShdwDrive attempts to decentralize the big tech cloud compute and storage infrastructure.
If you've been in 2024 crypto for more than 20 minutes, you know data is a HUGE narrative.
We've been asking WHY with some legends lately.
@Frank_theTrader joins the conversation, to give his take and their unique solution to the problem!
Listen on X now, or follow the link for your fav platform⬇️
https://t.co/R048vwspMZ
[THREAD + CONCOURS] Présentation de JPG 🟥🟨🟦
JPG est un écosystème crypto POUR les degens 🇫🇷 créé PAR des degens 🇫🇷
Si la culture web3 vous intéresse, alors ce thread est fait pour vous 🫵
Mais tout d'abord, on vous offre un ENORME GIVEAWAY pour fêter ce lancement ⬇️
Testnet 2 is officially on its way! Here's everything you need to know in order to start getting ready!
· D.A.G.G.E.R. Testnet 2 Start Date:
January 16th, 2024 @ 6pm UTC
· shdwPoints Start Date:
December 28th, 2023 @ 2am UTC
· End Date: April 15th:
April 16th, 2024 @ 6pm UTC
· Rewards:
600,000 $SHDW allocated into 3 different rewards categories:
- shdwOperators, 300,000 SHDW pool
- shdwStaking, 175,000 SHDW pool
- shdwPoints, 125,000 SHDW pool
#1) shdwOperators - 300,000 $SHDW Allocated
Earn SHDW and help power D.A.G.G.E.R.’s incentivized Testnet by being a shdwOperator and running a shdwNode!
https://t.co/ZkfUp2XJx9
shdwOperators contribute storage to the shdwDrive network and are responsible for maintaining the resources needed to power and scale shdwDrive.
How many shdwOperators can earn rewards?
The max number of shdwOperators who can be earning rewards at any given point is 150. Each node in the network must belong to a SPL unique wallet (more on that later).
For new operators to join once the limit is reached, an existing operator must either drop out or for the network to reach consensus that a shdwNode is inactive and vote for its removal from the network.
shdwNodes are considered inactive after two epochs have passed. Due to D.A.G.G.E.R.’s asynchronous leaderless architecture the length of an epoch is variable, however on average they are roughly 30 minutes.
How much will I earn?
A shdwOperator is eligible to earn up to 2,000 SHDW based on the uptime of their shdwNode with the possibility of an additional SHDW award for exceptional uptime.
Running a shdwNode shouldn't cost more than $100-300/month, join our Discord for recommendations on providers:
https://t.co/GiGwUMCRK1
Testnet2 is approximately 2,207 hours long, meaning an individual shdwOperator earns ~.906 SHDW per every hour their shdwNode is running.
Any unearned SHDW remains in the smart contract where it is distributed amongst shdwOperators whose have an uptime >=2,096 hours (~95% of the total Testnet2 duration).
The amounts distributed to each operator would be calculated based on the amount of remaining SHDW in the pool and the amount of uptime hours above 2,096 each operator logged.
What does this look like in reality?
Let’s assume there are two shdwOperators named Talia and Bruce. To keep things simple, we will assume Talia and Bruce are the only two participants.
Example 1:
shdwOperator Bruce joins the network halfway through and his node accumulates ~1,103.5 hours of Testnet2 uptime. To calculate Bruce’s rewards, you would multiply .906 x 1,103.5 (total uptime hours).
Bruce would earn ~1,000 SHDW. So what happens to the other 1,000 SHDW Bruce was eligible to earn but didn’t due to arriving late? Let’s see.
Example 2:
shdwOperator Talia’s node has been connected to Testnet2 since the moment the Testnet opened and has racked up 2,200 total uptime hours.
Talia would receive 1,993.2 SHDW (.906 x 2,200 uptime hours). Talia would also awarded the 1,000 extra SHDW that was not paid to Bruce. Talia is receiving this award for having an total Testnet2 uptime percentage of 97%.
Therefore, Talia’s total reward would be 2,993.2 SHDW due to her outsized contribution to the network.
shdwOperators will be able to track their uptime status and rewards payouts via the shdwOperator leader-board which will be publicly viewable at https://t.co/N440AQaiLV when Testnet2 launches.
Do I need to stake SHDW in order to connect a node to the network?
Technically, no. Individual nodes do not need to be staked by their operators in order to join the network. Staking for network access is being approached as a community effort. Please see shdwStaking below.
That said, shdwOperators who are staking SHDW for community rewards (detailed in the section below) from their shdwNode ID wallet do receive preferential treatment should their no be removed from the network.
Example:
Selina is shdwOperator #100. Her node drops from the network and is removed from the 150 shdwNodes currently earning rewards (discussed previously above).
When Selina’s node rejoins the network, she find she is now #161. However, shdwOperator’s 151 – 160 are not staking SHDW from their shdwNode ID wallet.
Because none of the shdwOperators ahead of Selina are staking SHDW from the wallet used to generate their shdwNode ID, Selina is moved up and she now becomes shdwOperator #151 and is next in line to start earning rewards.
Does that mean there is no slashing?
For this round of testing, we are not implementing a slashing feature. Based on community feedback we believe a slashing mechanic would be an impediment to the growth of the network.
There will always be a need to have some kind of financial disincentive as a deterrent to prevent bad actors but this should not come at the expense of community good. Hence the focus on rewarding uptime in Testnet2.
We believe the denial of rewards can be an effective financial disincentive to prevent bad actors while not penalizing well-intentioned members of the community.
Is that it?
No, there are more surprises to provide additional rewards and increase the number of shdwOperators earning rewards beyond 150 planned along the way…
#2) shdwStakers - 175,000 $SHDW Allocated
shdwStaking is much simpler and much more straight forward than the shdwOperator category.
Our goal is to encourage as many people as possible to learn to create shdwNodes and become shdwOperators. However, we also recognize that, for a variety of reasons, this is not something that is possible for every member of the SHDW Community.
We also recognize that there are many members of our community who are very active in driving awareness for shdwDrive and D.A.G.G.E.R. in the Solana ecosystem. Those efforts should not go unrewarded.
Therefore, for literally the first time ever, SHDW holders will be able to stake their SHDW tokens and earn rewards via single sided staking!
This section is significantly easier since this just single sided staking as we are all familiar with (although, there is one small twist).
· An individual’s staking rewards are proportionate to the percentage of the total staked pool that individual has contributed.
· There is no cap on rewards.
· Starts when Testnet2 launches and ends when Testnet2 ends.
What’s the twist?
For every 1 shdwNode connected to the network there needs to be 10,000 cumulative SHDW staked in the shdwStaking smart contract.
For there to be 150 shdwNodes earning rewards there needs to be 1,500,000 SHDW in total staked in the shdwStaking smart contract.
Note: SHDW is not being staked directly with any specific shdwNode. 10,000 individual wallets each staking 1 SHDW equates to 1 shdwNode coming online. The ratio between total staked SHDW and the number of shdwOperators is what matters.
All staked SHDW goes to the same shdwStaking smart contract. Staked SHDW does not directly interact with the shdwNodes in the network.
For Testnet2 we are testing the foundations for the shared-staking mechanism which allows community members to help bootstrap shdwNodes by staking SHDW with those nodes. For reference, this was first discussed here: https://t.co/8DoIf8yn1S
In order to promote as much inter-connectivity between those individuals operating shdwNodes and the broader community of individuals supporting shdwDrive we have created a linkage between the amount of total SHDW staked in the shdwStaking smart contract and the number of shdwNodes which can be connected to the network at any given time earning rewards.
Is that it?
Yep, shdwStaking is quick and easy.
#3) shdwPoints - 125,000 $SHDW Allocated
Oh man… GenesysGo is jumping into the points meta… look ma! We’re #DeFi now!
To make things easier, we’ve listed the details of the game first. After the details those interested can read more about the rationale behind the game and the desired outcome.
How do points work?
· Users earn points based on their wallet activity and their SHDW holdings. Balancing frequency and size is important!
· A snapshot was taken December 28th at 2:00am UTC to capture the current state of all wallets which hold SHDW (including SHDW that has been staked inside of platforms like @marginfi and others).
· From December 28th at 2:00am UTC through the end of Testnet2 on April 16th at 6pm UTC EVERY wallet will earn or lose points based on their activity.
· Points can be redeemed for SHDW at the end of the Testnet2 period. Think of it like cashing out tickets at an arcade.
· Wallets earn 1 point for every 10 SHDW purchased. SHDW must be acquired through @JupiterExchange via either a swap, a limit order, or Jupiter’s DCA feature to be eligible for points.
· Wallets will lose 1 point for every 1 SHDW which leaves the wallet via any means during the period of Testnet2. This includes wallet to wallet transfers.
· Staking SHDW in the shdwStaking smart contract is the only exception.
· All activity across all platforms is actively tracked on-chain throughout the duration of Testnet2 to provide leader-board updates.
You mentioned size, does size matter?
Size always matters.
· At the end of Testnet2 period a points bonus is awarded to every wallet based on their average transaction size. The amount of bonus points awarded scales exponentially as average transaction size increases.
Okay… but like… why points…?
Part of what makes SHDW unique and of true value is the maturity of its Tokenomics. SHDW has one of the lowest total supply numbers of any token on Solana at 169m and is nearly fully diluted with a circulating supply of ~158m as of the time of this writing. There are no upcoming cliffs due to the unlocking of insider tokens sold in private OTC transactions at prices not available to the broad community.
All SHDW tokens that are or will ever be held in every wallet on Solana were acquired in one of three ways:
1. Received as emissions for minting or purchasing a Shadowy Super Coder NFT.
2. Purchased as a part of the SHDW IDO.
3. Purchased in the open secondary markets at whatever the prevailing market price was at the time.
This in no way guarantees that every holder of SHDW was or will be profitable. What is guaranteed though is that no one has profited from SHDW by acquiring it in a manner that was not open to literally every other person on Solana at that exact same moment in time.
Additionally, referring back to https://t.co/8DoIf8yn1S, all effort and focus has been centered around ensuring SHDW is tied to the overall growth and health of the shdwDrive platform. Holders of SHDW are being positioned to finally earn their piece of the multi-billion dollar pie that is the cloud data storage market.
That said, we also understand that this kind of build takes a while and that it can be difficult to keep the focus on the bigger picture in an environment where we often see five or six memecoins launching each day and then being wash traded to try to entice buyers into chasing 1,000% gainers every day.
As such, we wanted to create a fun way to not only engage existing members of the community as well as provide new pathways for potential new holders. This incentive will hopefully help new holders take their time as they onboard themselves and learn more about SHDW’s true potential.
When can I see my points and how can points be redeemed?
A shdwPoints leader-board will be published in the next week to provide live standings. Points can be redeemed at the end of Testnet2 on April 16th, 2024.
Can I earn rewards from all three pools?
Yes!
In fact, we encourage it! Maximizing your rewards from the three pools would look something like this:
· Create a shdwNode and use a wallet currently holding SHDW to create your Node ID. Then connect to the network to earn rewards from the shdwOperator allocation.
· Stake the SHDW in the shdwNode ID wallet in the shdwStaking contract to earn staking rewards.
· Rotate profits from the most recent memecoin into new SHDW to lock in shdwPoints.
· Finally, stake the newly acquired SHDW and the SHDW earned from being a shdwOperator in the shdwStaking contract to continue increasing your shdwStaking yield.
#Solana #web3 #DePin