Download shdwDrive:

Direct Download | App Store Link (coming soon) | Play Store Link (coming soon)

Reimagining Cloud Storage

shdwDrive v2 transforms cloud storage into a decentralized ecosystem where users can not only store their files securely but also participate in and earn from the network. Our platform eliminates traditional centralized storage providers, replacing them with a community-driven network where everyone can contribute and benefit.

What Makes shdwDrive Different?

shdwDrive creates a marketplace where:

• Users get reliable, secure decentralized storage

• SHDW tokens allows to provide storage capacity

• The community shapes the network's future

• Everyone benefits from transparent, fairness

Want to dive deeper into how shdwDrive works? Check out our to learn about the network's economic model, proof systems, and mathematical foundations that ensure fair rewards for all participants.

How this resource is organized

Your complete resource for using shdwDrive v2 – whether you're storing files or earning rewards as a network operator. Now that we have launched our latest technology, stay tuned for frequent updates to our guides!

This section is being re-designed as we support the latest shdwDrive v2! What remains are previous versioning guides that focus on easy and actionable information to help you quickly get started building on the previous version 1.5 (soon deprecated) shdwDrive. Step by step guides, and line by line CLI instruction offer developers the quickest path to working concepts.

Much like an appendix, the reference section is a quick navigation hub for key resources. Our media kit, social media presence, and more can be found here.

Bugs and Feedback

This resource will be updated frequently and the developer community should feel empowered to for edits they would like to see or platform enhancement ideas. We also have a process for .

Our SDK options provide the simplest means of linking your application to shdwDrive. With a variety of environments to choose from, developers can enjoy a robust and constantly evolving platform that leverages the full potential of shdwDrive. GenesysGo is dedicated to maintaining these SDKs, continuously enhancing developer capabilities, and streamlining the building process. We value your feedback and welcome any suggestions to help us improve these valuable resources.

In order to use the S3-Compatible gateway for the shdwDrive network, head over to https://portal.shadow.cloud, connect your wallet and sign in, and then navigate to the storage account you'd like to generate an access key/secret key pair. Select the "Addons" tab and then you'll be able to enable & add s3-compatible key/secret pairs.

Obtaining your credentials

Once you've enabled the S3 Access addon for a given storage account, you can view and add more s3-compatible key/secret pairs by navigating to the storage account of your choosing on .

To get your credentials, simply click "View Credentials".

Permissions

Once enabled, you can manage individual permissions of each key/secret pair you generate for a given storage account. The list of permissions are configured to be compatible with existing s3 clients. Some examples of compatible s3 clients are rclone, s3cmd, and even the aws s3 cli. There's a plethora of tooling that exists for s3-compatible gateways, which is why we chose to build this into the shdwDrive network.

In general, if you want to enable uploads with one of your keys, you'll need to enable the following permissions:

You can also control if a key is able to read, which allows you to have read, write, and read+write keys for various use cases.

Gateway endpoints

In order to access the s3 compatible gateways on the shdwDrive network, you'll need to configure your s3 client to use one of the following gateways:

1. https://us.shadow.cloud

2. https://eu.shadow.cloud

These endpoints proxy requests to the shdwDrive network and allows you to have the best network connectivity possible given your geographical preference. All uploads are synced and available globally, so you can use either endpoint.

Example client configurations

RCLONE

The following is an example that you can add to your rclone configuration file. Typically, this is located in `~/.config/rclone/rclone.conf`.

Speed

In order to ensure the stability of the shdwDrive network, speeds are initially limited to 20 MiB/s. You can opt to upgrade the bandwidth rate limit for each individual key/secret pair you generate. The upgraded rate limit is 40 MiB/s

Security

In the event a s3 key has been compromised, you can easily rotate the key. Simply navigate to , connect your wallet, select a storage account, and then click on the "Addons" tab. From there, you can click "Rotate" button to rotate a given key/secret pair to generate a fresh pair.

Getting Started

Prerequisites: Install on any OS.

Contents

shdwDrive SDK

• Installation

• Local Development

shdwDrive CLI

shdwDrive SDK

shdwDrive SDK is a typeScript SDK for interacting with ShdwDrive, providing simple and efficient methods for file operations on the decentralized storage platform.

Installation

Local Development

Features

• 📤 File uploads (supports both small and large files)

• 📥 File deletion

• 📋 File listing

• 📊 Bucket usage statistics

Quick Start

Usage Examples

Upload a File

Create a Folder

Delete a Folder

List Files

Delete a File

API Reference

ShdwDriveSDK

Constructor Options

Methods

• uploadFile(bucket: string, file: File, options?: FileUploadOptions)

• deleteFile(bucket: string, fileUrl: string)

• listFiles(bucket: string)

shdwDrive CLI

A command-line interface for interacting with shdwDrive storage.

Features

• 📤 File uploads (supports both small and large files)

• 📁 Folder support (create, delete, and manage files in folders)

• 📥 File and folder deletion

• 📋 File listing

Installation

You can install the CLI globally using npm:

Or use it directly from the repository:

Configuration

The CLI uses environment variables for configuration:

• SHDW_ENDPOINT: The shdwDrive API endpoint (defaults to )

Usage

Upload a file

Delete a file

Create a folder

List files in a bucket

Check bucket storage usage

Command Options

Upload Options

• -k, --keypair - Path to your Solana keypair file

• -b, --bucket - Your bucket identifier

• -f, --file - Path to the file you want to upload

Delete Options

• -k, --keypair - Path to your Solana keypair file

• -b, --bucket - Your bucket identifier

• -f, --file - URL or path of the file to delete

Create Folder Options

• -k, --keypair - Path to your Solana keypair file

• -b, --bucket - Your bucket identifier

• -n, --name - Name/path of the folder to create

Delete Folder Options

• -k, --keypair - Path to your Solana keypair file

• -b, --bucket - Your bucket identifier

• -p, --path - Path of the folder to delete

Development

1. Clone the repository:

1. Install dependencies:

1. Build the project:

1. Link the CLI locally:

• Install Python SDK

• Examples

Installing ShdwDrive

pip install shadow-drive

Also for running the examples:

pip install solders

Check out the directory for a demonstration of the functionality.

https://shdw-drive.genesysgo.net/[STORAGE_ACCOUNT_ADDRESS]

Example - Create Account, File Upload, Add or Reduce Storage, and Delete Account using Python

About the

This package uses PyO3 to build a wrapper around the official ShdwDrive Rust SDK. For more information, see the .

Methods

Section under development.

Full Detail - Version Releases & Fixes:

shdwDrive Core

shdwDrive CLI

shdwDrive Rust

Consolidated Summary

D.A.G.G.E.R. - Launch of - January 16th

D.A.G.G.E.R. - Launch of - September 29, 2023

shdwDrive - Release S3 Compatible Gateway - August 29, 2023

shdwDrive

shdwDrive Rust

shdwDrive

shdwDrive

Apr 5, 2023- shdwDrive Rust

Mar 16, 2023 - shdwDrive

Mar 15, 2023 - shdwDrive Rust

Feb 28, 2023 - shdwDrive Rust

Feb 27, 2023 - shdwDrive CLI

Feb 27, 2023 - shdwDrive

Feb 27, 2023 - shdwDrive

Feb 9, 2023 - shdwDrive

Feb 8, 2023 - shdwDrive

Feb 9, 2023 - shdwDrive CLI

Dec 13, 2022 - shdwDrive CLI

Nov 28, 2022 - shdwDrive

Nov 28, 2022 - shdwDrive

Sep 22, 2022 - shdwDrive CLI

Sep 22, 2022 - shdwDrive CLI

Sep 22, 2022 - shdwDrive CLI

Sep 21, 2022 - shdwDrive CLI

Sep 21, 2022 - shdwDrive

Sep 21, 2022 - shdwDrive

Sep 21, 2022 - shdwDrive CLI

Aug 26, 2022 - Digital Asset RPC Infrastructure

Jul 26, 2022 - shdwDrive

Jul 22, 2022 - shdwDrive

Jul 12, 2022 - shdwDrive

Jul 8, 2022 - shdwDrive

To get started with the shdwDrive CLI:

2. Install the

3. Follow the

   • After installing Solana, make sure you have both SHDW and SOL in your wallet in order to reserve storage

To get started with the shdwDrive SDKs:

1. , , and are your choices.

2. Follow the

   • You can build directly on top of the .

Submitting Bugs & Security Issues

We adhere to a responsible disclosure process for security related issues. To ensure the responsible disclosure and handling of security vulnerabilities, we ask that you follow the process outlined below.

Bug Reporting Process

1. For non-security-related bugs, please submit a new bug report . For security-related reports, please open a "security vulnerability" report .

2. Please provide a clear and concise description of the issue, steps to reproduce it, and any relevant screenshots or logs.

Important: For security-related issues, please include as much information as possible for reproduction and what its related to. Please be sure to use the report a security vulnerability feature in the repository listed above. If you submit a security vulnerability as a public bug report, we reserve the right to remove the report and move any communications to private channels until a resolution is made.

Security related issues should only be reported through this repository.

While we strongly encourage the use of this repository for bug reports and security issues, you may also reach out to us via our server. Join the #shdw-drive-technical-support channel for assistance. However, please note that we will redirect you to submit the bug report through this GitHub repository for proper handling and tracking.

Twitter: https://twitter.com/genesysgo

Discord: https://discord.com/invite/shdwdrive

Blog:

shdwDrive

Asynchronous Byzantine Fault Tolerance (aBFT): aBFT is a consensus algorithm used to provide fault tolerance for distributed systems within asynchronous networks. It is based on the Byzantine Fault Tolerance (BFT) algorithm and guarantees that, when properly configured and given tolerable network conditions, its consensus will eventually be reached — even when faults such as computer crashes, perfect cyber-attacks, or malicious manipulation have happened. aBFT is designed to be tolerant of malicious or faulty actors even when those actors make up more than one-third of the nodes inside the network. Blockchain: A peer to peer, decentralized, immutable digital ledger used to securely and efficiently store data that is permanently linked and secured using cryptography. Byzantine Fault Tolerance: A fault-tolerance system in distributed computing systems where multiple replicas are used to reach consensus, such that any faulty nodes can be tolerated and the consensus of the system can be maintained despite errors or malicious attacks. Consensus Algorithm: A consistency algorithm is a method of achieving agreement on a single data value across distributed systems. It is typically used in blockchain networks to arrive at a common data state and ensure consensus across network participants. It is used to achieve fault-tolerance in distributed systems and allows for the distributed system to remain operational even if some of its components fail. Consensus Protocols: A consensus protocol is an algorithm used to achieve agreement among distributed systems on the state of data within the system. Consensus protocols are essential in distributed systems to ensure there is no disagreement between the nodes on the data state, so that no node has a different view of the data. The protocols typically employ some form of voting, such as majority voting, or methods like proof of work, to achieve the necessary agreement on the data state. Cryptographic Hashing: Cryptographic hashing is a process used to convert data into a fixed-length string of characters, or "hashes", in order to protect the data and verify its authenticity through an encrypted code. The hash cannot be reversed to the original data and is used extensively time to ensure data integrity. Cryptographic hashes can be used to verify data integrity, authenticate data sources, and prevent tampering. Cryptography: The practice and study of techniques used to secure communication, data, and systems by transforming them into an unreadable format. Cryptography is an important component of cybersecurity, providing data protection and confidentiality. Data Caching: Data caching is a software engineering technique that stores frequently accessed or computational data in a cache in order to quickly access that data when it is needed. Data caching works by temporarily storing data to serve it quickly when requested. This can significantly improve the performance of applications, which reduces the amount of time spent serving requests. Data Encryption: The process of encoding data using encryption algorithms in order to keep the content secure and inaccessible to user without a decryption key. Data encryption makes it difficult for unauthorized users to read confidential data. Data Integrity: A quality of digital data that has been maintained over its entire life cycle, and is consistent and correct. The term is ensured through specific protocols such as data validation and error detection and correction. Data Partitioning: The process of splitting large data or throughputs into smaller, more manageable units. This process allows for more accuracy in data processing and faster results, as well as the ability to easily store and access the data. Data Sharding: Data Sharding is a partitioning technique which divides large datasets into smaller subsets which are stored across multiple nodes. It is used to improve scalability, availability and fault tolerance in distributed databases. When combined with replication, Data Sharding can improve the speed of queries by allowing them to run in parallel. Decentralized Storage Network: A Decentralized Storage Network is a type of distributed system which utilizes distributed nodes to store and serve data securely, without relying on a single point of failure. It is an advanced form of data storage and sharing which provides scalability and redundancy, allowing for more secure and reliable access than that offered by conventional centralized systems. Delegated Proof-of-Stake (DPoS): Delegated Proof-of-Stake (DPoS) is a consensus mechanism used in some blockchain networks. It works by allowing token holders to vote for a “delegate” of their choice to validate transactions and produce new blocks on their behalf. Delegates are rewarded for their work with a percentage of all transaction fees and new block rewards. DPoS networks are usually faster and more scalable than traditional PoW and PoS networks. Digital Signatures: A digital signature is a mathematical scheme for demonstrating the authenticity of digital messages of documents. It is used for authenticating the source of messages or documents and for providing the integrity of messages or documents. A valid digital signature gives a recipient reason to believe that the message or document was created or approved by a known sender, and has not been altered in transit. Directed Acyclic Graphs: A Directed Acyclic Graph (DAG) is a type of graph with directed edges that do not form a cycle. It consists of vertices (or nodes) and edges that connect the nodes. The direction of the edges between the nodes determines the flow of information from one node to another. A DAG is a useful structure for modeling data sets, such as queues and trees, to represent complex algorithms and processes in computer engineering. Distributed Computing: A type of computing in which different computing resources, such as memory, hard disk space, and processor time are divided between different computers working as a single system. This gives the benefits of distributed computing like scalability, load balancing, reduced latency, and improved resiliency. It is widely used in data centers and cloud computing. Distributed Consensus: The process of having a distributed system come to agreement on the state of an issue or order of operations. This is achieved through communication, verification and agreement from each of the connected nodes in the system. Distributed Database: A distributed database is a type of database which stores different parts of its data across multiple devices that are connected to computer networks, allowing for more efficient data access by multiple users and more efficient transfer of data between different locations. Distributed File System: A distributed file system is a file system that allows multiple computers to access and share files located on remote servers. It enables a computing system that consists of multiple computers to work together in order to store and manage data. The system can be seen as a large-scale, decentralized file storage platform that spans multiple nodes. Data is replicated across the computers so that if one computer goes down, another can take its place, which helps provide for high availability, scalability, and fault tolerance. Distributed Ledger Technology: A type of database technology that maintains a continuously growing list of records, each stored as a block and protected by cryptography. It is a database shared across multiple nodes in a network, that keeps track of digital transactions between the nodes and is protected by airtight security and tamper proof mechanisms. Transaction records are constantly updated and can be easily accessed. Distributed Ledger Technology Platforms: A distributed ledger technology (DLT) platform is a secure digital platform that allows data to be securely shared and stored in a decentralized manner across a wide range of nodes within a network. DLT platforms provide a distributed ledger solution that is tamper-resistant, secured using cryptographic encryption protocols, and can remain resilient even in the face of malicious actors. DLT platforms also enable secure and timely data exchanges, providing scalability, reliability and transparency for transactions. Distributed Storage Services: Services that allow users to store data across multiple physical storage locations. This increases reliability and availability of the data and allows for distributed workloads to take advantage of this. Distributed Storage System: A distributed storage system is a series of computer systems which interact together to manage, store, and back up massive amounts of data in a reliable and secure way. A distributed storage system is more fault-tolerant than conventional storage systems because its components are not vulnerable to a single point of failure. This allows a distributed storage system to provide higher levels of data durability and availability than a single, centralized system. Distributed Systems: A type of computing system consisting of multiple, independent components that can communicate with each other to coordinate and synchronize their actions, creating a unified system as a whole. It is a type of software architecture that is designed to maximize resources across multiple computers connected over a network. Distributed Systems Architecture: A distributed system is an interconnection of multiple independent computers that coordinate their activities and share the resources of a network, usually communicating via a message-passing interface or remote procedure calls. Distributed systems architecture includes design guidelines and approaches to ensure a system’s resilience, performance, scalability, availability, and security. Erasure Coded File Storage: Erasure coded file storage is an archive strategy that divides data into portions, and then encodes each portion multiple times using various error-correction algorithms. This redundancy makes erasure coding valuable for permanently storing critical data as it increases reliability but reduces storage costs. Fault Tolerance: Fault tolerance is the capability of a system to continue its normal operation despite the presence of hardware or software errors, disruptions, and even loss of components or data. Fault tolerant systems are designed to be resilient to failure and to continue normal operation in the event of a partial or total system failure. Gossip Protocol: A distributed algorithm in which each member of a distributed system periodically communicates a message to one or more nodes, which then send the same message onto other nodes, until all members of the network receive the same message. This allows for a system to remain aware of all other nodes and records in the system without the need for a central server. Hashgraph: A distributed ledger platform that uses a virtual voting algorithm to achieve consensus faster than a traditional distributed ledger. This system allows for the secure transfer of digital objects and data without needing a third party for authentication. Its consensus algorithm is based on a gossip protocol, where user nodes are able to share news and updates with each other. Hyperledger Fabric: Hyperledger Fabric is an open source software project that provides a foundation for developing applications that use distributed ledgers. It allows for secure and permissioned transactions between multiple businesses, enabling an ecosystem of participants to securely exchange data and assets. It provides support for smart contracts, digital asset management, encryption, and identity services. Immutability: The capacity of an object to remain unchanged over time, even after multiple operations and modifications. Additionally, immutability is a property by which the object remains unchanged, and all operations on that object return a new instance instead of modifying the original. Interoperability: The ability of systems or components to work together and exchange data, even though they may be from different manufacturers and have different technical specifications. Key Management: Key management is the overall management of a set of cryptographic keys used to protect data both in transit over a network and in storage. Proper key management encryption and control ensure the secure communication within applications and systems and provides a baseline for protecting sensitive information. Key managers are responsible for the storage, rotation, and renewal of encryption keys and must ensure that the data is secure against unauthorized disclosure, modification, inclusion, or loss. Merkle Tree: A Merkle tree is a tree-based data structure used for verifying the integrity of large sets of data. It consists of a parent-child relationship of data nodes, with each block in the tree taking the data of all child blocks, hashing it together, and then creating a hash of its own. This process is repeated until a single block remains, which creates a hierarchical and hashed structure. Multi-Node Clusters: A type of computing architecture, composed of multiple connected computers, or nodes, that work together and are able to act as a single system. A multi-node cluster allows for increased information processing and storage capacity, as well as increased reliability and availability. Nodes: A node is a basic unit of a data structure, such as a linked list or tree data structure. Nodes contain data and also may link to other nodes. Nodes are used to implement graphs, linked lists, trees, stacks, and queues. They are also used to represent algorithms and data structures in computer science. Oracles: An oracle is a system designed to provide users with a result of a query. These systems are often relied on to deliver accurate and reliable conclusions to users, based on the data they have provided. There have been several generations of oracles, ranging from hardware to software-based systems, each of which has different sets of capabilities. Orchestration: Orchestration is the process of using software automation to manage and configure cloud-based computing services. It is used to automate the management and deployment of workloads across multiple cloud platforms, allowing organizations to gain efficiency and scalability. Peer-to-Peer Networking: Peer-to-peer networking is a type of network architecture model where computers (or peer nodes) are connected together in such a way that each node can act as a client or a server for the other nodes in the network. In other words, it does not rely on a central server to manage the communication between the connected peers in the network. Proof of Stake (PoS): A consensus mechanism in blockchain technology which allows nodes to validate transactions and produce new blocks according to the amount of coins each node holds. It is an alternative to the Proof of Work (PoW) consensus protocol. In PoS, validators stake their coins, meaning they have to deposit coins with the blockchain protocol before they can validate blocks. Validators receive rewards for creating blocks and are penalized for malicious behavior. Proof of Storage (PoSt): Proof of Storage is a consensus cryptographic mechanism which is used to attest to the storage of data in a distributed storage network. The consensus model requires a randomly chosen subset of storage miners to periodically provide cryptographic proofs that they are storing data correctly and that all necessary nodes are online. The goal of PoSt is to ensure that data stored is secure, as well as increase the security and transparency of distributed storage networks. Proof of Work (PoW): A consensus algorithm by which a set of data called a “block” is validated by solving computationally-taxing mathematical problems. It is used as a security measure in blockchains as each block that is created must have a valid PoW for the block to be accepted. The difficultly of the computational problems get more difficult with time as the blockchain grows, incentivizing the participants to continue to keep the chain running. Proof-of-Stake (PoS): A consensus mechanism used in certain distributed ledger system, where validator nodes participate in block validation with a combination of network participation and staking of token or other resources. The Proof-of-Stake consensus is an alternative to Proof-of-Work (PoW) used in many other blockchain networks. Proof-of-Work: A concept used by blockchain networks to ensure consensus by requiring a certain amount of effort or work to make sure the blocks of data in the chain are legitimate and valid. This is done by large amounts of computational work, typically hashing algorithms. Public Distributed Ledger: A public distributed ledger is a decentralized database that holds information about all the transactions that have taken place across the network, distributed and maintained by all participants without the need for a central authority to manage and validate it. All participants in the network can access, view, and validate the data stored on the ledger. Public Key Infrastructure (PKI): A set of protocols, services, and standards that manage, distribute, identify and authenticate public encryption keys associated with users, computers, and organizations in a network. PKI allows secure communication and ensures that only the intended recipient can read the message. QuickP2P: A type of networking protocol focused on peer-to-peer (P2P) computing that allows users to exchange files and data quickly across multiple computers. QuickP2P works by breaking the files into small blocks, which can then be rapidly downloaded separately in parallel by the searching user. Quorum: The minimum number of nodes in a distributed system that must be engaged in order to reach a consensus. Quorum value is set based on the number of nodes in the system and must be greater than half of the total nodes present in the system. Replication: The process of creating redundant copies of data or objects in distributed systems for the purpose of fault-tolerant data storage or network operations. Routing Protocols: Protocols that direct traffic between computers across a network or the Internet, determining the routing path for data packets and exchanging information about available routes between routers. Routing protocols define the way routers communicate with each other to exchange network information and configure the best path for data traffic. Scalability: The ability of a system to increase its performance or capacity when given additional resources such as additional computing, memory, data storage, network bandwidth and power. Scalability is an important consideration for developing systems that must handle increasing amounts of data, workload or users. Secure Messaging: Secure messaging is the process of sending or receiving encrypted messages between two or more parties, with the intent of ensuring that only the intended recipient can access the contents of the message. The encryption process generally involves the use of public and private keys, making it secure and nearly impossible for anyone else to intercept any messages sent over the network. Secure Multi-Party Computation (MPC): A computer security framework that allows several parties to jointly compute a function over their private inputs without revealing anything other than their respective outputs to the other parties. MPC leverages the security of cryptography in order to achieve privacy and security in computation. Security Protocols: Security protocols are systems of standard rules and regulations created by computer networks to protect data and enable secure communication between devices. They are commonly used for authentication, encryption, confidentiality and data integrity. Smart Contracts: A type of protocol that is self-executing, autonomously carrying out the terms of an agreement between two or more parties when predetermined conditions are met. They are used to exchange money, assets, shares, or anything of value without the need for a third party or intermediary in a secure and trustless manner. Smart contracts are used widely within blockchain-based applications to reduce risk and increase speed and accuracy. Smart Contracts: Contracts written in computer code that are stored and executed on a blockchain network. Smart contracts are self-executing and contain the terms of an agreement between two or more parties that are written directly into the code. Smart contracts are irreversible and are enforced without the need for a third-party. State Machines: A state machine is a system composed of transitioning states, where each state is determined by the previous state and the current inputs. Each state has attached conditions and outputs, and when a the previous state and input conditions match the conditions of the current state, a single output will be generated. State machines are commonly used in computer engineering for finite automation. Synchronization Methods: Methods of ensuring that different parts of a distributed application or system are working from a shared same set of data at a given point in time. This can be achieved by actively sending data among components or by passively waiting for components to ask for data before sending it. Synchronous Byzantine Fault Tolerance (SBFT): A consensus algorithm for blockchain networks that requires each node to be connected and active for all network messages to be exchanged and validated in a given time period. This algorithm provides a way for a distributed network to come to consensus, even when some participants may be compromised or malicious. Time-Stamping: The technique of assigning a unique and precise time value to all events stored in a record in order to define an chronological order of those events. Virtual Voting: Digital voting system where citizens are able to cast their vote over the internet, directly or through a voting portal. It has been used as an alternative to physical voting polls, particularly during the pandemic. It can also be used to verify the accuracy and security of elections. Web 3.0: The Web 3.0 concept refers to the newest generation of the internet. It is highly decentralized and automated, based on AI and distributed ledger technologies such as blockchain. It allows for a more open and secure infrastructure for data storage, authentication, and interactions between devices across the web. It has the potential to be much smarter, faster, and more efficient than its predecessor Web 2.0.\

The Defiant: The Rise & Fall & Rise of Solana

Next Billion Podcast: Why Solana is Leading the DePin Game

Blockworks: Hot take: Your dApp Probably isn’t DePIN

Crossroads Panel: The Future of DePin

Crossroads: Discovering the Future of Decentralized Infrastructure

Download shdwDrive:

Direct Download (APK) | Solana App Store Link (coming soon) | Play Store Link (coming soon)

Getting Started is Simple

As a User:

1. the shdwDrive mobile app

2. Connect your Solana wallet

3. Choose a storage plan (start with 5GB free!)

4. Create your first bucket

As an Operator:

1. the shdwDrive mobile app

2. properly

3. Navigate to the Operator tab

4. Select your storage level

As a Developer:

1. - integrate shdwDrive in your app

Need specific information? Jump to:

• - New to shdwDrive? Start here

• - Learn how to participate in the network

• - integrate shdwDrive with your app

• - Dive into the network architecture

Have questions? Our comprehensive sections below cover everything you need to know about using and operating on shdwDrive v2. Have feedback? Let us know .

Table of Contents

1. General Android Power Settings

2. App Background Behavior

5. • (S21 & Newer)

   • (6 & Newer)

   • (10 & Newer)

General Android Power Settings

1. Battery Optimization

1. Go to Settings → Battery (or Battery saver / Battery optimization).

2. Locate shdwDrive in the list.

3. Set it to Not optimized or Unrestricted.

4. This ensures the system does not close the app in the background.

2. App-Specific Power Controls

1. Settings → Apps → shdwDrive → Battery (or similar).

2. Toggle Allow background activity to On.

3. Disable any “Battery optimization” or “Restrict background data” specifically for shdwDrive.

App Background Behavior

1. App Management Settings

• Never manually force-stop the shdwDrive app.

• Keep shdwDrive in your Recent Apps (avoid swiping it away).

• If there’s an Auto-start / Auto-launch feature, turn it on for shdwDrive.

• Allow it to run in the background continuously.

2. Memory Management

• Exclude shdwDrive from any memory cleaners or “one-tap boost” apps.

• Turn off automatic hibernation for the app.

• Confirm shdwDrive is on any “Do not optimize” or “White list” for battery/memory.

Battery Management

1. Power Maintenance

• If possible, keep your device plugged in while the node runs.

• Avoid or disable aggressive power-saving modes that close apps at low battery.

• Set your low-battery threshold to around 15% so shdwDrive won’t be shut down prematurely.

• A dedicated power supply can help if you’re running the node for extended periods.

2. Battery Optimization

• Disable Adaptive Battery specifically for shdwDrive.

• Turn off “Optimize for battery life” for shdwDrive.

• Remove it from any “sleeping apps” or “deep-sleep” lists.

System-Level Optimization

1. Memory Settings

• If your device has Developer Options:

  • Set Background process limit to Standard or No limit.

• Disable or reduce any “memory optimization” tools that might kill background processes.

2. Performance Mode

• Use High performance mode if available for stable connectivity.

• Reduce or disable thermal throttling on gaming/performance phones if comfortable.

• Ensure the device has adequate cooling to avoid forced closures.

Manufacturer-Specific Settings

Below are recommendations for devices running Android 12L or later. Menu names may vary by region or device.

Samsung Settings

Applies to: Galaxy S21, S22, S23, A53, A54, etc. (on Android 12L+)

1. Battery Settings

   • Settings → Battery → Background usage limits

     • Add shdwDrive to Unrestricted apps.

Google Pixel Settings

Applies to: Pixel 6, 6 Pro, 7, 7 Pro, 8, etc. (Android 12L+)

1. Battery Settings

   • Settings → Battery → Battery Saver

     • Turn it off or only use it manually.

OnePlus Settings

Applies to: OnePlus 10, 10T, 11, etc. (Android 12L+)

1. Battery Optimization

   • Settings → Battery → Advanced → Battery optimization → shdwDrive → Don’t optimize.

2. Background Process

Xiaomi Settings

Applies to: Xiaomi / Redmi / POCO (2022+ devices running 12L+)

1. Battery & Performance

   • Settings → Battery & performance

   • Turn off Battery saver for shdwDrive or set to Unrestricted.

OPPO / Realme Settings

Applies to: OPPO/Realme devices running Android 12L+

1. Battery Settings

   • Settings → Battery → select High performance mode or exclude from Power saver.

2. App Management

ASUS Settings

Applies to: ZenFone 8/9, ROG Phone 5/6/7 on 12L+

1. Power Management

   • Settings → Battery → PowerMaster

   • Disable optimization for shdwDrive.

   • Auto-start manager → Allow shdwDrive.

Motorola Settings

Applies to: 2022+ models running Android 12L or later

1. Battery Settings

   • Settings → Battery → Turn off Adaptive Battery for shdwDrive or pick Unrestricted.

2. App Management

Nothing Phone Settings

Applies to: Nothing Phone (1) & (2)

1. Battery Settings

   • Settings → Battery → Battery optimization → shdwDrive → Don’t optimize.

2. App Management

Sony Settings

Applies to: Xperia devices launched or updated to 12L+

1. Battery Settings

   • Settings → Battery → turn off Adaptive Battery for shdwDrive.

   • Disable or bypass STAMINA mode if it kills the node.

Vivo Settings

Applies to: Vivo (OriginOS/Funtouch OS 12L+)

1. Battery Settings

   • Settings → Battery → Background power consumption → Allow for shdwDrive.

   • Exclude from power saving mode.

2. iManager Settings

Nokia Settings

Applies to: Nokia models from 2022 onward running 12L+

1. Power Settings

   • Settings → Battery → Battery optimization → Don’t optimize for shdwDrive.

   • Disable Adaptive Battery for the app if possible.

TCL Settings

Applies to: TCL devices on Android 12L+ (2022 releases and newer)

1. Battery Management

   • Settings → Battery & Performance → App power saving mode → Off for shdwDrive

   • Smart Manager → auto-launch → Enable for shdwDrive

2. App Settings

ZTE Settings

Applies to: ZTE devices on Android 12L+ (e.g., Axon series)

1. Power Settings

   • Settings → Battery → power saving mode → exclude shdwDrive

   • App power saving → Off for shdwDrive

2. App Management

Lenovo Settings

Applies to: Recent Lenovo tablets / phones with 12L or later

1. Battery Settings

   • Settings → Battery → Allow background app management for shdwDrive

   • Exclude from power saving modes.

2. Security Settings

BlackShark Settings

Applies to: Black Shark 5 Series and later (Android 12L+)

1. Game Dock Settings

   • Game Dock → Performance → CPU/GPU → Performance mode

   • Background process → Allow shdwDrive

2. Battery Settings

Infinix / Tecno Settings

Applies to: Infinix/Tecno models running 12L+

1. Power Management

   • Settings → Battery → Power Management → Off for shdwDrive

   • Background apps → Allow

2. Phone Master

Final Tips

• Check Settings After Updates: System updates can revert your battery or background settings. Review them after each update.

• Stay Plugged In: A stable power source ensures you won’t lose node connectivity when battery runs low.

• Monitor Node Activity: If the node goes offline, revisit settings to confirm none have changed.

By following these instructions on your Android 12L+ device, you’ll help keep shdwDrive running reliably in the background for maximum node uptime. Good luck and happy node-running!

Technical

General

Contents

storage-account

POST https://shadow-storage.genesysgo.net

Creates a new storage account

Request content type: application/json

Request Body

storage-account-info

POST https://shadow-storage.genesysgo.net

Gets on-chain and ShdwDrive Network data about a storage account

Request content type: application/json

Request Body

upload

POST https://shadow-storage.genesysgo.net

Uploads a single file or multiple files at once Request content type: multipart/form-data

Parameters (FormData fields)

Request Body

edit

POST https://shadow-storage.genesysgo.net

Edits an existing file

Request content type: multipart/form-data

Parameters (FormData fields)

Request Body

list-objects

POST https://shadow-storage.genesysgo.net

Get a list of all files associated with a storage account

Request content type: application/json

Request Body

list-objects-and-sizes

POST https://shadow-storage.genesysgo.net

Get a list of all files and their size associated with a storage account

Request content type: application/json

Request Body

get-object-data

POST https://shadow-storage.genesysgo.net

Get information about an object

Request content type: application/json

Request Body

delete-file

POST https://shadow-storage.genesysgo.net

Deletes a file from a given Storage Account

Request content type: application/json

Request Body

add-storage

POST https://shadow-storage.genesysgo.net

Adds storage

Request content type: application/json

Request Body

reduce-storage (updated)

POST https://shadow-storage.genesysgo.net

Reduces storage

Request content type: application/json

Request Body

make-immutable (updated)

POST https://shadow-storage.genesysgo.net

Makes file immutable

Request content type: application/json

Request Body

Example - Secure Sign and Upload File to ShdwDrive using API

This example demonstrates how to securely upload files to the ShdwDrive using the provided API. It includes the process of hashing file names, creating a signed message, and sending the files along with the necessary information to the ShdwDrive endpoint.

Example - Editing a File in ShdwDrive using API and Message Signature Verification

In this example, we demonstrate how to edit a file in ShdwDrive using the API and message signature verification. The code imports necessary libraries, constructs a message to be signed, encodes and signs the message, and sends an API request to edit the file on ShdwDrive.

Example - Deleting a File from ShdwDrive using Signed Message and API

In this example, we demonstrate how to delete a file from the ShdwDrive using a signed message and the ShdwDrive API. The code first constructs a message containing the storage account and the file URL to be deleted. It then encodes and signs the message using the tweetnacl library. The signed message is then converted to a bs58-encoded string. Finally, a POST request is sent to the ShdwDrive API endpoint to delete the file.

Contents

Contents

Getting Started

Getting Started

What is shdwDrive?

shdwDrive is a decentralized mobile storage platform that allows you to store files securely while also providing opportunities to participate in the network as an operator.

Basic Setup

Q: How do I start using shdwDrive? A: Getting started is simple:

1. Download and install the shdwDrive mobile app on your Android device

2. Connect your wallet

3. Create a storage bucket or choose a storage plan

4. Begin uploading your files

Q: Do I need a specific wallet to use shdwDrive? A: Yes, shdwDrive requires a Solana-compatible wallet. The app will guide you through connecting your preferred wallet during setup.

Q: What happens after I connect my wallet? A: After connecting your wallet, you'll be guided through:

1. A brief onboarding process

2. Options to create storage space

3. Access to the main dashboard where you can manage files and operator settings

Q: What is a bucket? A: A bucket is your personal storage space on shdwDrive where you can store and organize your files. Think of it as your private folder in the decentralized network.

Q: How do I create a bucket? A: To create a bucket:

1. Open the shdwDrive app

2. Look for the "Create Bucket" button on the home screen

3. Follow the prompts to set up your new storage space

Q: Is there an iOS app? A: No, not at this time. Android dominates global market share with approximately 70-75% of all smartphones worldwide, while iOS (iPhone) accounts for about 25-30%. We will complete the majority of our feature rollout on Android first, refining the user and operator experience, before moving to support the iOS device family.

Q: Why do I need to authorize each file upload separately? A: Currently, each file upload requires a separate authorization through your wallet for security purposes. This is an intentional security feature that:

• Ensures proper authorization of all file operations

• Prevents unauthorized bulk uploads

• Maintains a clear record of file ownership

• Protects your data and storage space

Q: Can I upload multiple files at once? A: At this time, files must be uploaded individually. Each upload requires:

• Selecting the file

• Authorizing the transaction through your wallet

• Waiting for confirmation This process ensures proper tracking and verification of each file upload. Future updates will be introduce batch upload features while maintaining security standards.

Q: What happens if my upload is interrupted? A: If an upload is interrupted:

• The partial upload is automatically cancelled

• No storage space is consumed

• No transaction fee is charged

• You can simply restart the upload Always ensure a stable connection when uploading larger files.

Storage Plans

Q: Is there a free storage option? A: Yes, shdwDrive offers a free 5GB storage plan to get started.

Q: What can I store in shdwDrive? A: You can store various file types including:

• Photos and images

• Documents

• Videos

• Custom folders and file structures

Q: Can I see how much storage I'm currently using? A: Yes, the app displays:

• Your current storage usage

• Available space in your bucket

• Storage contribution level (if you're an operator)

• Visual indicators of space usage

Becoming an Operator

Understanding Operators

Q: What is a shdwDrive Operator? A: A shdwDrive Operator contributes storage space from their Android device to the decentralized network. Operators provide real utility by making their device's unused storage available for secure file storage.

Q: What are the benefits of becoming an operator? A: As an operator, you:

• Earn real revenue in USDC from user storage fees (in future releases)

• Participate in a decentralized storage network

• Contribute to network infrastructure

• Receive programmatic revenue sharing based on your contribution

Q: What's the difference between being a storage user and an operator? A: Key differences:

• Users pay for storage services in USDC

• Operators provide storage capacity to the network

• SHDW tokens serve as operator collateral

• Operators earn revenue from actual storage fees

Requirements & Setup

Q: What do I need to become an operator? A: To become an operator, you need:

• An Android device (version 12.0L or higher)

• Sufficient free storage space (minimum varies by contribution level)

• Stable internet connection (WiFi required at this time)

• A "Join Ticket" for network access

Q: What are the recommended device requirements to run shdwDrive? A: To run shdwDrive effectively, your device should meet these specifications:

• Android 12L or newer

• Minimum 6 CPU cores

• At least 8GB RAM

• Sufficient free storage space for your chosen contribution level

Q: Which devices are supported? A: Here's a non-comprehensive list of compatible devices:

Premium/Flagship Devices

• Google Pixel: 7, 7 Pro, 8, 8 Pro, 9, 9 Pro

• Samsung Galaxy S: S22/+/Ultra, S23/+/Ultra, S24/+/Ultra

• OnePlus: 10 Pro, 10T, 11, 11R

• ASUS ROG Phone: 6, 6 Pro, 7, 7 Ultimate

Mid-Range Devices

• Google Pixel a-series: 6a, 7a

• Samsung Galaxy A-series: A53 5G, A54 5G

• OnePlus Nord: N20, N200

• Motorola Edge (2022, 30)

Specialty Devices (minimum storage spec)

• Solana Saga

• Seeker

Q: Can I run shdwDrive on older devices? A: No. While older devices might run the app, we recommend meeting the minimum specifications for optimal performance and reliability. Devices that don't meet these specs may experience:

• Slower proof generation

• Reduced storage efficiency

• Reduced revenue potential

• Potential stability issues

Q: Can I operate multiple nodes with the same wallet? A: No. Each wallet can only operate one node at a time. This means:

• One wallet can only stake to one node

• If you want to run multiple nodes, you'll need separate wallets for each

• When switching devices, you must fully deactivate your current node before setting up the new one with the same wallet. Unstake before deactivating means waiting one Solana epoch before being able to withdraw.

• When changing your storage allocation (therefore stake allocation), you must fully unstake, wait the cooldown of one Solana epoch, and restake up to your desired allocation.

Q: What if I want to switch my node to a different device? A: To switch devices:

• First deactivate and unstake on your current device

• Wait the cooldown and complete the withdrawal process

• Set up the new device using the same wallet, remembering only one wallet per one node

• Stake and activate your new node

Remember: Never try to run nodes on multiple devices with the same wallet as this can cause conflicts and operational issues at this time.

Q: How much storage can I contribute? A: Storage contribution levels are based on 1 SHDW per ~51.2MB. Choose based on your device's available storage, with buffer for critical system, and desired SHDW stake level.

Q: Why doesn't my device's full storage capacity show as available? A: Available storage is affected by several factors:

• System files and OS requirements consume a portion of your total storage

• Existing apps and data reduce available space

• Android reserves space for system operations and updates

• The app maintains a safety buffer to ensure stable operation

For example, a 512GB device might show only 400GB as available because:

• Android OS and pre-installed apps use ~50GB

• System reserves ~30GB for updates and cache

• Your personal apps and data use a portion

• A safety margin is maintained for optimal performance

The app shows only safely usable storage capacity to ensure reliable node operations.

Q: Are external storage options such as Micro SD cards supported? A: Not at this time. While we have tested this feature and confirmed it to work, there is more work needed to ensure the shdwDrive runtime plays nice with how Android OS manages peripheral user storage.

Node Operation

Q: How do I pass verification to join the network? A: Use one of our many Join Ticket:

Q: How do I manage my node? A: The Operator section of the app provides:

• Node On/Off toggle

• Current storage contribution level

• Network connection status

• Monitor logs

Q: What does the operator interface show me? A: The operator interface displays:

1. Current Status:

   • Storage Level: Your contributed storage amount

   • SHDW Collateral: Current network security deposit

2. Node Controls:

Q: What happens when I toggle my node on? A: When you toggle your node on:

1. The app verifies your WiFi connection

2. Connects to the network using your gossip ticket

3. Begins participating in network operations

4. Starts monitoring for storage requests Note: A stable WiFi connection is required to start your node

Q: What should I check before starting my node? A: Before toggling your node on, ensure:

1. You have a stable WiFi connection

2. Your gossip ticket is properly entered

3. The RPC is pre-filled correctly with an endpoint

4. Your device is charged or plugged in

Q: Can I run my node while using mobile data? A: Not at this time, but soon. Your node requires a WiFi connection to:

• Maintain stable network connections

• Ensure efficient data transfer

• Reduce mobile data usage

• Provide consistent network participation The node will automatically stop if WiFi connection is lost.

Q: What is a Gossip Ticket? A: A Gossip Ticket is your node's access credential for joining the network. It contains necessary information for establishing secure connections with other nodes.

Q: What are the storage fragments I see in my Downloads folder? A: These are secure storage units that your device uses to participate in the network. Each fragment (fragment.000, fragment.001, etc.) contains portions of the distributed storage system. Don't delete these manually - the app manages them automatically.

Q: What's the process for changing my storage/stake level? A: Currently, changing levels requires:

1. Deactivating your current node

2. Unstaking your SHDW tokens

3. Completing the withdrawal process

4. Reactivating with your new desired storage level Direct storage updates are not supported - you must go through the full deactivation process.