Support & FAQ

Contents

Getting Started

Becoming an Operator

Technical Details

Revenue & Operations

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

  • Allows you to monitor and control your storage usage

  • Enables us to better iterate the rolling out of more robust handling

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

  • Standard Android app level information is also accessible

Becoming an Operator

As of release 1.0.8, gossip tickets have been refreshed. All current operators must verify their ticket has correctly updated after upgrade/install.

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

  • SHDW tokens for network collateral

  • Proper settings for the Android OS and app

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

  • Reduced revenue potential

  • Potential stability issues

  • Eventual slashing and malice tracking in the global view manager

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:


Ticket1:

XHGA5LRCCKLCCAW3KCDU44SHKJEQFXZEYYKGS43BJRLSQV2ALH2QCAAB6X6SVVUSV32H6KQ4M7BNEMGCR4XTSVZTE4GBTEJQUZSJ7UTGKEJQBOE2MJ6AIAFQ5IAQDMXKAEBLJ2QBAO3OUAI=

Ticket2:

XHGA5LRCCKLCCAW3KCDU44SHKJEQFXZEYYKGS43BJRLSQV2ALH2QCAABEW6OOCQO7EMA7JKC6PQSK274ZBATDSWD2V7LJ6EA5BBCVN6HTF3QAL5ZVNGQCAEU5MAQ====

Ticket3:

XHGA5LRCCKLCCAW3KCDU44SHKJEQFXZEYYKGS43BJRLSQV2ALH2QCAABSU42N6PY6HFGSVBHDU7AOGSDUBY3KBCM3RQGNMVU7VNJWTF5TGFQAL5ZVNGQCAE65MAQ====

Ticket4:

XHGA5LRCCKLCCAW3KCDU44SHKJEQFXZEYYKGS43BJRLSQV2ALH2QCAABMI3Z7RMH4XD72UMXHBTRXXV2GGWJP75WYIFSBB5WSLZVBJADC5JAAL5ZVNGQCAFI5MAQ====

Ticket5:

XHGA5LRCCKLCCAW3KCDU44SHKJEQFXZEYYKGS43BJRLSQV2ALH2QCAABE34WB2TIQREIRXJRM6YUS2VS26BNDCO57HR3TBREHWNIK4O77MHAAL5ZVNGQCAFS5MAQ====

Ticket6:

XHGA5LRCCKLCCAW3KCDU44SHKJEQFXZEYYKGS43BJRLSQV2ALH2QCAAB7VYWWCU2O7S4QRMICVTDZNSUHV5B75F6XYHND4QKKSVTELF4F3FAAL5ZVNGQCAF45MAQ====

Ticket 7:

XHGA5LRCCKLCCAW3KCDU44SHKJEQFXZEYYKGS43BJRLSQV2ALH2QCAABIKUOVHCXUM45VSK6URD5KE3JJXAIQNSR65I5YC552CBRRAG6NMGQAL5ZVNGQCAGG5MAQ====

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 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:

    • "Deactivate & Release Collateral" button: Stops node operation

    • "Withdraw" button: Retrieves your SHDW collateral after cooldown

    • Node On/Off toggle: Controls active participation

  3. Configuration:

    • Gossip Ticket: Network access credential

    • RPC Endpoint: Network connection point

  4. Node Information:

    • Node ID: Your unique identifier

    • Backup Key: Recovery information

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.

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.

Q: Are there staking time requirements? A: Yes, there are important timing considerations:

  • Initial stake requires a warmup period (one Solana epoch)

  • Unstaking requires a cooldown period (one Solana epoch)

  • You cannot deactivate/unstake during the warmup period

  • Revenue can be claimed once per 24-hour period

  • Withdrawal is only available after the cooldown period completes

Q: What if I want to switch to a different device? A: When switching devices:

  1. Wait for your initial stake warmup period to complete

  2. Deactivate and unstake on your current device

  3. Wait for the cooldown period to complete

  4. Withdraw your SHDW tokens

  5. Set up the new device with the same wallet

  6. Stake and activate your new node

Technical Details

Understanding Logs

Q: How do I access and share node logs? A: Logs can be accessed through:

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

  2. Use "Copy Logs" to copy to clipboard

  3. Use "Send Logs" to share with support

Q: What are the key log message types?

Network Status Messages

  • Global View Updates:

    ├─ 🌐 Global Consensus View
├─ peers: [number]
└─ Network Messages: [number]

    Shows network-wide state synchronization.

  • Event Processing:

    ├─ Events Received
└─ Network Messages: [number]

    Indicates successful message processing.

  • Network Maintenance:

    ├─ ✂️ Cleanup
└─ Network Msgs: [number]

    Shows network optimization activities.

Peer Management Messages

  • Join Operations:

    ├─ 🌐 Join
└─ Proof: [true|false]

    Indicates new peer verification.

  • Synchronization:

    ├─ 🔄 Recieved Peer Sync
└─ Network Messages: [number]

    Shows peer data synchronization.

  • Network Updates:

    ├─ ⚙️ Network Update
├─ Active: [number]
└─ Pending: [number]

    Displays connection status changes.

Q: What are Storage Proof logs? A: Storage Proof logs demonstrate that your node is actively storing and validating data as part of the decentralized network. These logs confirm that your node is fulfilling its role in maintaining data integrity. A typical storage proof log entry may look like this:

└─ CID: Hash("ab3f875881b3c9c04e3ee73f9a7fb1afac4466ba246e6da2d664cde23a4ef7d8")
├─ Operation: Generate
[INFO] shdw_dht::dht_gossip: Storage Proof

Each entry shows:

  • A CID (Content Identifier) that uniquely identifies the data chunk.

  • The Operation performed (e.g., Generate).

  • A log message indicating that a Storage Proof has been processed.

Note: Not every node will necessarily display storage proof logs. Whether or not these logs appear depends on the node’s active/passive view and the network topology—that is, whether your node is selected to participate in the storage proof process as part of the active set.

Q: What indicates healthy node operation?

Normal Operation Patterns

  1. Regular Network Activity:

    • Regular "Events Received" messages

    • Incrementing "Network Messages" count

    • Periodic "Global Consensus View" updates

  2. Healthy Connection Status:

    • Stable or growing active edges

    • Low pending connection counts

    • Regular shuffle cycles

    • Successful peer syncs

  3. Network Participation:

    • Regular cleanup operations

    • Periodic shuffle cycles

    • Consistent message processing

    • Stable peer count in consensus view

Warning Signs

  • Network Messages not incrementing

  • Frequent "Disconnect" messages with "unhealthy" status

  • High number of pending connections

  • No Global Consensus View updates

  • Frequent connection status changes

  • Missing periodic cleanup operations

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

  • Confirm proper port forwarding (30000-60000) and that you are not behind a restrictive firewall

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?

Initial Connection Problems

  1. Network Status:

    ├─ 🌐 graph edges=2 pending=1

    If edges are 0 or pending stays high, check:

    • Internet connection

    • Router UPnP settings

    • Port forwarding (30000-60000)

    • Firewall restrictions

  2. Peer Connection Issues:

    ├─ 🌐 Peer Disconnected
├─ Active: 1
└─ Pending: 2

    High pending counts indicate connection problems. Check:

    • Router settings

    • Network restrictions

    • Gossip ticket validity

Ongoing Operation Issues

  1. Network Isolation Signs:

    ├─ Events Received
└─ Network Messages: [not incrementing]

    Solutions:

    • Verify gossip ticket

    • Check network configuration

    • Restart node if persistent

  2. Connection Quality Issues:

    ├─ 🌐 Disconnect
└─ Status: unhealthy

    Indicates:

    • Network instability

    • Connection timeouts

    • Possible firewall issues

Additional Note on Storage Proof Logs: While storage proof logs are a key indicator that your node is actively contributing to data storage and validation, their absence does not imply a problem. Depending on your node’s current role (active versus passive) and the overall network topology, you might not see these logs—even when your node is operating normally. As long as you observe the other critical indicators of network health (such as regular event updates and stable connection metrics), your node is functioning as expected.

Q: What should I do if my node automatically stops? A: Common causes and solutions:

  1. Connection Loss:

    • WiFi disconnection

    • Network configuration changes

    • Router reboots Solution: Restore stable network connection

  2. Device Issues:

    • Critical battery level

    • Insufficient storage

    • Memory constraints

    • App forced close Solution: Address resource constraints

  3. System Changes:

    • Android OS updates

    • Security policy changes

    • Power management interventions Solution: Reconfigure after system changes

Q: What should I do if my app becomes unresponsive or stuck at loading? A: If your app becomes unresponsive or stuck follow these recovery steps:

  1. Initial Recovery Steps:

    • Backup your node key if possible

    • Preserve the shdwDrive folder in Downloads

    • Uninstall the app

    • Install the latest version

    • Connect using your original wallet

  2. Post-Installation Process:

    • The app will automatically show your existing stake status (stored on-chain)

    • You MUST complete the unstake process before creating a new stake:

      • Click "Deactivate & Unstake"

      • Wait for the cooldown period

      • Use "Withdraw" to claim your tokens

      • Only then proceed with new stake creation

  3. Important Considerations:

    • Never attempt to create a new stake without unstaking first

    • Your original stake is accessible on-chain as long as you use the same wallet

    • Future versions will support direct node ID keypair restoration

    • New stake will generate a new node ID

  4. Recovery Timeline:

    • Unstaking cooldown: One Solana epoch

    • Withdrawal availability: After cooldown

    • New stake activation: After withdrawal

  5. Warning Signs During Recovery:

    • If your active stake doesn't appear after reinstall

    • If you see multiple stake positions

    • If unstake option isn't available Stop all operations and contact support immediately

Note: We are working on implementing direct node ID keypair restoration functionality for smoother recovery in future updates.

Revenue & Operations

Storage & Staking

Q: How does the revenue model work? A: The revenue model is based on real utility:

  • Users pay storage fees in USDC

  • Fees are distributed to operators based on contribution

  • Revenue sharing is tied to actual storage provision

  • No artificial token rewards or inflation

  • Read more here

Q: What is the purpose of SHDW tokens? A: SHDW tokens serve specific functions:

  • Act as network collateral for operators

  • Enable slashing for malicious behavior

  • Support network security

  • Not designed for speculative value or rewards

Q: How do I navigate the operator staking interface? A: The operator interface can be accessed through the Operator tab in the bottom navigation bar. Here you'll find:

  • Current Node Level and SHDW Staked amounts at the top

  • Deactivate & Unstake button for stopping your node

  • Withdraw button for accessing staked tokens after cooldown

  • Node On/Off toggle for controlling node operation

  • Node ID and Backup Key options

  • Gossip Ticket and RPC Endpoint configuration

Q: How do I check my current stake and storage levels? A: Your current status is displayed at the top of the Operator screen showing:

  • Current Node Level (storage amount)

  • Current SHDW Staked amount These values are automatically updated when changes occur.

Q: How do I initiate the unstaking process? A: To unstake:

  1. Navigate to the Operator tab

  2. Click the "Deactivate & Unstake" button

  3. Confirm the transaction in your wallet

  4. Wait for the cooldown period

  5. Use the "Withdraw" button to claim your tokens

Q: What are the available storage and staking tiers? A: Storage levels are now based on the amount of SHDW you choose to stake with a ratio of 1 SHDW per ~51.2MB and a min. floor of 1,000 SHDW to qualify.

You must have sufficient SHDW tokens and available device storage to select a tier. All storage tiers require meeting the minimum device specifications outlined in the "Requirements & Setup" section.

Note: Future releases will introduce more granular and dynamic staking and storage options.

Q: What's the process for changing my storage level? A: Changing storage levels requires:

  1. Deactivating your current node

  2. Releasing your SHDW collateral

  3. Completing the withdrawal process

  4. Reactivating with new storage level and corresponding collateral

Q: What happens during deactivation? A: The deactivation process includes:

  1. Node is stopped

  2. Current stake enters pending withdrawal state

  3. Storage allocation is released

  4. Node configuration is preserved for potential reactivation

Q: What happens when I deactivate and unstake? A: The process involves several steps:

  1. Deactivate & Unstake: Initiates the unstaking process

  2. Withdrawal Period: Your tokens enter a pending withdrawal state

  3. Withdraw: After the cooling period, you can withdraw your staked SHDW

  4. Your node will be turned off but your operator account remains initialized

Q: What happens to my revenues when I unstake? A: When unstaking:

  • Any unclaimed revenue remain available

  • You can still claim revenue from your previous contribution

  • New revenue stop accruing once unstaked

  • Your operator account retains access to claim functions

Q: Are there staking time requirements? A: Yes, there are important timing considerations:

  • Initial stake requires a warmup period (one Solana epoch)

  • Unstaking requires a cooldown period (one Solana epoch)

  • You cannot deactivate/unstake during the warmup period

  • Revenue can be claimed once per 24-hour period

  • Withdrawal is only available after the cooldown period completes

Q: What if I want to switch to a different device? A: When switching devices:

  1. Wait for your initial stake warmup period to complete

  2. Deactivate and unstake on your current device

  3. Wait for the cooldown period to complete

  4. Withdraw your SHDW tokens

  5. Set up the new device with the same wallet

  6. Stake and activate your new node

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 revenue 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

PreviousGuidesNextStart Building

Last updated