Support & FAQ

Contents

Getting Started

Becoming an Operator

Technical Details

Rewards & Management

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.

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

  • Standard Android app level information is also accessible

Becoming an Operator

Understanding Operators

Q: What is a shdwDrive Operator? A: A SHDW Drive Operator is someone who contributes storage space from their Android device to the decentralized shdwDrive network. You're essentially renting out your device's unused storage space to help store files across the network.

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

  • Generate earnings for contributing storage

  • Participate in the decentralized network

  • Put your device's unused storage to work

  • Help maintain the network's infrastructure

Q: What's the difference between being a storage user and an operator? A: While all users can store files on shdwDrive:

  • Regular users utilize the network for storage

  • Operators contribute their device's storage to the network

  • Operators stake SHDW tokens and earn rewards

  • Operators help maintain network decentralization

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"

  • After initial beta release, SHDW tokens for staking

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

  • Nothing Phone: 1, 2

  • Xiaomi POCO: X6, X6 Pro

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

  • Lower network participation rewards

  • Potential stability issues

  • Eventual slashing and malice tracking in the global view manager

Q: How much storage can I contribute? A: Storage contribution levels include:

  • 50 GB

  • 100 GB

  • 250 GB

  • 500 GB

  • 750 GB

  • 1000 GB

Choose based on your device's available storage and desired stake level. Higher tiers and more advancements to contributions levels are in upcoming feature rollouts.

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:

Ticket1:

XHGA5LRCCKLCCAW3KCDU44SHKJEQFXZEYYKGS43BJRLSQV2ALH2QCAAB5YCIYMMUVGHS2UJQITC5XPWR373HHOFCAWSQ5PZ4MFSTNJLBLJCAAL5ZVNGQCAFQ5IAQ====

Ticket2:

XHGA5LRCCKLCCAW3KCDU44SHKJEQFXZEYYKGS43BJRLSQV2ALH2QCAABLNMPML44FHCBPT3HDEF4DLP2NCYO374WPFOXYNMYXKF6N7VE262AAL5ZVNGQCAF25IAQ====

Ticket3:

XHGA5LRCCKLCCAW3KCDU44SHKJEQFXZEYYKGS43BJRLSQV2ALH2QCAABHC3VCIHXNUCU4E3HOZ42FXXACALUCRID7Z3N7P2VAQJMPSKAR5GQAL5ZVNGQCAGE5IAQ====

Ticket5:

XHGA5LRCCKLCCAW3KCDU44SHKJEQFXZEYYKGS43BJRLSQV2ALH2QCAAB3GS42FLECLRYGKMYGLGVNVJEG3KS5RIFW2UVHM7PUPHSIIKGOZQQAL5ZVNGQCAGY5IAQ====

Ticket6:

XHGA5LRCCKLCCAW3KCDU44SHKJEQFXZEYYKGS43BJRLSQV2ALH2QCAABGNEHABWGNI2MZF65SBVURJGAW5CCZB7T634UYFKZDFS7IPOI4F3QAL5ZVNGQCAHC5IAQ====

Ticket7:

XHGA5LRCCKLCCAW3KCDU44SHKJEQFXZEYYKGS43BJRLSQV2ALH2QCAABUJERUYAVDAKE2A2SMHDBO52LBINQYTGXTFHTTI4EXNQ7AHOKSW2QBOE2MJ6AIAGQQYBQDUUGAMBNJBQDAPLIMAY=

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

  • Maintain good WiFi connection

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

  5. You have sufficient free storage space

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.

Technical Details

Understanding Logs

Q: How do I view my node's logs? A: You can access logs through:

  1. The "View Logs" section in the operator dashboard

  2. The logs show real-time node activity and network interactions

  3. Use the "Copy Logs" or "Send Logs" buttons to share logs for support

Q: What do the common log entries mean? A:

Node Status & Structure

  • "Global Network Vertices: [number]": Shows total known nodes in the network. For example, "Global Network Vertices: 400" means your node knows about 400 total participants.

  • "Active Edges: [number]": Your direct connections to other nodes.

  • "Pending Edges: [number]": Connections being established. Shows network growth.

  • "Event Queue: [number]": Tasks being processed. Numbers 0-5 indicate smooth operation.

Network Events

  • "Consensus State Update": Shows your node synchronizing with the network. Regular updates indicate healthy participation.

  • "GRAPH_SHUFFLE": Your node exchanging peer information:

    ├─ Origin Node: [address]
├─ Shuffled Vertices: [number]
└─ TTL: [number]

    TTL (Time To Live) shows how far this information will spread.

Storage Events

  • "Storage Proof Announcement": Another node verifying their stored data

  • "Generate Storage Proof": Your node proving it has stored data correctly

  • "Storage Operation": Shows active data management:

    ├─ Action: Generate Proof
└─ CID: [content identifier]

Connection Events

  • "GRAPH_SYNC": Initial connection with proof validation

  • "GRAPH_PROPAGATE": Network information spreading

  • "GRAPH_DISCONNECT": Clean disconnection from a peer

Q: Why do I see multiple similar events in my logs? A: Repeated events like consensus updates or shuffles are normal and show your node actively participating in network maintenance. For example, multiple "Consensus State Update" entries show your node staying synchronized with various peers.

Network Architecture

Q: How does the network maintain connections? A:

Connection Structure The network uses a sophisticated peer-to-peer system:

  • Active Edges: Direct connections to other nodes

  • Global Network View: Knowledge of all available nodes

  • Verification Queue: Pending connection validations

Connection Management The network maintains itself through several mechanisms visible in logs:

  1. Graph Shuffling:

├─ Event: GRAPH_SHUFFLE
├─ Origin Node: [node address]
├─ Shuffled Vertices: [number]
└─ TTL: [number]

This shows nodes exchanging peer information to optimize network structure.

  1. Consensus Updates:

├─ Event: Consensus State Update
├─ Event: GRAPH_VIEW_UPDATE
└─ Global Network Vertices: [number]

Regular updates ensure all nodes agree on network state.

  1. Connection Health Example:

├─ Graph State
├─ Active Edges: 300
├─ Pending Edges: 200
└─ Event Queue: 200

Shows your node's current connection status and workload.

Q: What do different connection numbers mean? A: Understanding connection metrics:

  • Active Edges: Direct peer connections

  • Pending Edges: Establishing new connections

  • Event Queue: Tasks being processed

  • Global Vertices: Total known network nodes including passive, active, and stale

Q: How does the network handle node discovery? A: Node discovery happens through:

  1. Initial Connection:

    • STUN discovery for network access

    • Gossip ticket validation

    • Peer authentication

  2. Ongoing Discovery:

    • Regular graph shuffles

    • Peer exchange during consensus

    • Connection quality monitoring

Q: What is TTL and why is it important? A: Time To Live (TTL) controls information spread:

  • Higher TTL: Fresh information

  • Medium TTL: Normal propagation

  • Low TTL: Information reaching limits

  • TTL 0: Information stops spreading

This prevents network congestion while ensuring important updates reach all nodes.

Q: What indicates a healthy node? A:

Network Participation Look for regular participation events:

  1. Consensus Activities:

├─ Event: Consensus State Update
├─ Event: GRAPH_VIEW_UPDATE
└─ Global Network Vertices: [number]

These should appear every few minutes.

  1. Storage Proof Cycle:

Storage Operation
├─ Action: Generate Proof
└─ CID: [content identifier]

Regular proof generation shows active network contribution.

Warning Signs Watch for these patterns:

  • Rapidly changing Active Edge counts

  • Event Queue numbers consistently increasing

  • Long gaps between consensus updates

  • Frequent disconnection events

  • Missing storage proof generations

Performance Monitoring Monitor these log patterns:

  1. Graph Shuffles:

GRAPH_SHUFFLE
├─ Origin Node: [address]
├─ Shuffled Vertices: [number]
└─ TTL: [number]

Regular shuffles indicate healthy network participation.

  1. Peer Interactions:

Peer Event
├─ Vertex: [peer address]
├─ Event: [event type]
└─ [event details]

Diverse peer interactions show good network integration.

Q: How do I know if my node needs attention? A: Watch for these indicators:

  1. Immediate Attention Needed:

    • Active Edges drop below 2

    • Event Queue consistently rising

    • No consensus updates for 10+ minutes

    • Multiple consecutive connection failures

  2. Monitor Closely:

    • Pending Edges stay high for long periods

    • Consensus updates become irregular

    • Storage proofs take longer to generate

    • Frequent peer disconnections

  3. Normal Variations:

    • Short-term Edge count fluctuations

    • Occasional high Event Queue numbers

    • Brief gaps between consensus updates

    • Individual peer disconnections

Q: How can I use logs to optimize performance? A: Key metrics to monitor:

  1. Connection Stability:

    • Track Active Edge counts over time

    • Monitor peer connection durations

    • Watch consensus participation rate

  2. Storage Performance:

    • Storage proof generation frequency

    • Proof validation success rate

    • Peer verification responses

  3. Network Participation:

    • Graph shuffle involvement

    • Consensus update frequency

    • Global network view accuracy

Troubleshooting

Q: Why won't my node connect? A: Common issues and solutions:

  • Check WiFi connection stability

  • Ensure Gossip Ticket is correct

  • Confirm device has sufficient storage

  • Check for any system power restrictions

Q: What do I do if I see error messages? A: Common errors and fixes:

  • "Permission denied": Check app storage permissions

  • "Node disconnected": Check internet connection

  • "Storage allocation failed": Verify free space

Q: Why did my node automatically turn off? A: Your node may automatically stop if:

  1. WiFi connection is lost

  2. Device battery is critically low

  3. Available storage drops below required level

  4. Network connection becomes unstable

  5. You run too low on memory

  6. You swipe the app out of your active list, thereby hard closing it

  7. You approve an Android system update that reboots your connections

Q: How do I diagnose connection issues using logs? A:

Initial Connection Issues Watch for these startup patterns:

Port mapping discovered - Local: [port], Public: [ip]:[port]

If missing, STUN discovery failed. Check:

  1. Internet connection

  2. Firewall settings

  3. Router NAT configuration

  4. Ensure you are forwarding ports 30000-60000

Network Integration Problems Watch for these patterns:

├─ Graph State
├─ Active Edges: 0-1    // Problem: Too few connections
├─ Pending Edges: [growing number]    // Problem: Many failed connection attempts
└─ Event Queue: [growing number]     // Problem: Processing backlog

Connection Quality Issues Bad connection patterns:

GRAPH_DISCONNECT
├─ Vertex: [peer address]
├─ Network Impact
└─ Remaining Edges: [decreasing number]

Frequent disconnects suggest network instability.

Q: What do specific log errors mean?

STUN/Network Errors

not adding our addr for node: node_id = [id], my_addr = [ip]:[port]

  • Cause: NAT traversal issues

  • Fix: Check router UPnP settings or port forwarding

Consensus Issues

├─ Global Network Vertices: [very low number]
└─ Active Edges: [low number]

  • Cause: Network isolation

  • Fix: Check gossip ticket validity and network configuration

Storage Issues

Storage Operation
├─ Action: Generate Proof
└─ Status: Failed

  • Cause: Storage access or space issues

  • Fix: Verify storage permissions and available space

Q: How do I fix common networking problems?

Low Peer Count If logs show:

├─ Active Edges: 1
└─ Global Network Vertices: [number]

Solutions:

  1. Verify gossip ticket

  2. Check for network restrictions

  3. Restart node to trigger new peer discovery

Failed Storage Proofs If logs show repeated proof failures:

  1. Check storage permissions

  2. Verify storage allocation

  3. Monitor system resources

Consensus Participation If missing regular consensus updates:

  1. Check network stability

  2. Verify peer connections

  3. Monitor message propagation

Q: How do I interpret warning signs?

Early Warning Signs

  1. Connection Degradation:

├─ Active Edges: [declining numbers]
├─ Pending Edges: [increasing numbers]
└─ Event Queue: [growing backlog]

  1. Network Isolation:

├─ Global Network Vertices: [significantly lower than normal]
└─ Consensus State Update: [missing or infrequent]

  1. Storage Issues:

Storage Proof Announcement
└─ Status: Delayed/Failed

Recovery Steps

  1. For Connection Issues:

    • Monitor log patterns for 5 minutes

    • Check for error messages

    • Verify network stability

    • Consider node restart if persistent

  2. For Storage Issues:

    • Check system storage

    • Verify permissions

    • Monitor proof generation logs

    • Consider reducing storage commitment if persistent

Rewards & Management

Earnings & Staking

Q: How do rewards work? A: Operators earn based on:

  • Amount of storage contributed

  • Node uptime and reliability

  • Network participation quality

  • Storage proof validations

  • Read more here

Q: How does staking work? A: Updates coming soon after official announcements. Read more here.

Account Management

Q: How do I change my storage contribution? A: To modify your contribution:

  1. Access the "Update Storage Contribution" section

  2. Select a new storage level

  3. Adjust stake if required

  4. Confirm the changes

Q: What happens to my settings when I update my storage contribution? A: When updating your storage contribution:

  1. Your current node status is preserved

  2. The app verifies available device storage

  3. Stake requirements are recalculated

  4. You'll see a confirmation before changes apply

  5. Node may need to restart with new settings

Q: What happens if I want to stop being an operator? A: To deactivate:

  1. Use the "Deactivate & Unstake" option

  2. Your node will properly disconnect

  3. Storage fragments will be cleaned up

  4. Staked SHDW tokens will be returned

  5. Earned rewards remain available for claim

Support & Maintenance

Q: Where can I get help? A: Support resources:

  • In-app help buttons provide contextual guidance

  • View and share logs for technical support

  • Community forums and documentation

  • Official support channels

  • Report bugs through the app feedback system

Q: How do I report bugs or submit feedback? A: We have a dedicated system for bug reports and feedback:

  1. Visit our Airtable form: https://airtable.com/appUQgLU7dOMvGB5J/pagZ4dkosLyEqjvBs/form

  2. Fill out the relevant information

  3. Include any error messages or screenshots

  4. Describe the steps to reproduce the issue

  5. Submit the form for our team to review

Q: What information should I include in a bug report? A: To help us resolve issues quickly, please include:

  • Your device model and Android version

  • App version number

  • Specific steps that led to the issue

  • Any error messages you received

  • Screenshots if applicable

  • Node logs if the issue is operator-related

Q: How can I check if my bug has already been reported? A: Before submitting a new bug report:

  1. Check the FAQ for known issues and solutions

  2. Review recent app updates for fixed issues

  3. Look for similar issues in community discussions

  4. If in doubt, submit a new report - we prefer duplicate reports to missing issues

Q: What happens after I submit feedback? A: After submission:

  1. Our team reviews all feedback and bug reports

  2. Critical issues are prioritized for immediate attention

  3. Feature requests are evaluated for future updates

  4. Common issues may be added to the FAQ

  5. Major fixes are announced in app updates

Q: How do I backup my node information? A: Important backup steps:

  1. Save your keypair backup securely

  2. Document your node configuration

  3. Keep recovery phrases safe

  4. Never share private keys or sensitive data

  5. Use the app's built-in backup features

Q: What is the "Backup Key" option in my operator dashboard? A: The Backup Key feature:

  • Downloads your node's keypair information

  • Stores it securely in your downloads folder

  • Should be kept safe and private

  • Is essential for node recovery

  • Should never be shared with others

Q: When should I backup my node key? A: It's recommended to backup your key:

  1. Immediately after node activation

  2. Before making major node changes

  3. When updating the app

  4. As part of regular security maintenance Never share your backup key with anyone, even if they claim to be support.

Q: Is my personal data safe when operating a node? A: Yes, the app uses encrypted storage and secure communication protocols. Your device's personal data is completely separated from the storage space you contribute to the network.

Q: What information is shared with the network? A: Only technical information necessary for network operation is shared:

  • Your operator public key

  • Storage contribution metrics

  • Network connection details

  • Node performance statistics

PreviousGuidesNextBuild

Last updated