Frequently Asked Questions (FAQ)

To understand why data inside a blockchain is immutable, look at the Bitcoin blockchain as the gold standard. Since Bitcoin’s genesis block was mined in 2009, every single transaction and metadata log has been permanently stored and validated by thousands of independent computer nodes (miners) distributed across the globe. No individual, corporation, government, or even Bitcoin’s creator Satoshi Nakamoto, has the power to delete, alter, or roll back a past block.

At the technical level, this immutability is structurally enforced through rigorous mathematical and cryptographic consensus mechanisms:

• Cryptographic Hash Chaining: Each block contains a double SHA-256 cryptographic hash pointer of the previous block (the parent hash). If an attacker alters even a single byte of historical data in an old block, the hash of that block changes entirely, instantly breaking the cryptographic link and invalidating all subsequent blocks in the network's eyes.
• Decentralized Proof-of-Work Consensus: Bitcoin ledger validation is distributed across tens of thousands of independent mining servers globally. Any node attempting to broadcast altered local records is instantly rejected by the consensus mechanism. To successfully rewrite history, an attacker must acquire and sustain over 51% of the network’s total mining hashing power (a 51% Attack). This requires an unimaginable computational investment of billions of dollars, rendering attacks physically and economically impossible.

While Bitcoin’s native network can only store a very small amount of arbitrary data per transaction (e.g., OP_RETURN script markers limited to 80 bytes), SuperArchive’s backbone (Arweave) utilizes the exact same distributed consensus and cryptographic validation principles, but uses a block-weaving architecture mathematically optimized for storing large files (PDFs, images, zip files) permanently. Once written to Arweave, the file is hardcoded into the immutable ledger and cannot be updated, deleted, or censored by anyone.

For our paid tier, 1 S-Point costs 5 NTD and lets you archive a 16MB block on Arweave. Storing 1024MB (1GB) requires 64 S-Points, which translates to a 320 NTD one-time payment with absolutely zero recurring subscription fees.

When evaluated over a 30 or 50-year timeline, SuperArchive is remarkably cheaper because of its one-time payment model. In contrast, failing to pay a standard AWS or Google Drive monthly bill results in the immediate, permanent deletion of your files. Check out the comparison table below for a 1GB payload:

Dimension	SuperArchive	AWS S3 Standard	Google Drive (Google One)
Cost Model	One-Time Payment	Recurring Monthly Bill	Recurring Annual Subscription
1-Year Cost (1GB)	320 NTD	~9 NTD	~6.5 NTD*
30-Year Cost (1GB)	320 NTD	~270 NTD	~195 NTD*
50-Year Cost (Life-time) (1GB)	320 NTD	~450 NTD	~325 NTD*
Egress/Retrieval Cost	Free	Paid (~$0.09/GB download)	Free
Billing/Deletion Risk	Zero (Prepaid for 200+ Years)	High (Files deleted if credit card fails)	High (Deleted if payment fails or account inactive)
Immutability (Anti-Delete)	Absolute (Protocols prevent deletions)	Deleted instantly on request/non-payment	Deleted instantly on request/non-payment
Free Tier Guarantee	10 uploads/day (<91KB) queued	None (Only 12-month trial)	15GB Free (No data loss guarantees)

While Google Drive provides a 15GB free tier, Google's Terms of Service clearly state that they provide zero guarantees against data loss, and they do not possess any system-level "anti-deletion" safeguards (inactive accounts are regularly deleted after 2 years). With SuperArchive, your prepaid on-chain files are mathematically secured against deletion forever.

Integrating your automated AI Agents (like Lobster (養龍蝦)) is incredibly simple via our programmatic developer endpoints. Follow this workflow to guide your agent in archiving files permanently:

• Step 1 (Generate Key): Log in to your SuperArchive dashboard, navigate to the API Keys section, and generate a secure API key (prefixed with sa_live_).
• Step 2 (Check Points): Before prompting the agent to archive, instruct them to query GET /api/v1/developer/points to verify that your account has sufficient S-Points (1 point per 16MB block).
• Step 3 (Submit Archive): Instruct your Lobster AI Agent to perform a multipart POST request with their file payload to POST /api/v1/SuperArchive.

Note on Immutability: Once the Lobster agent completes the upload, the transaction is signed and permanently forged into the blockchain ledger. **The AI Agent itself (and even SuperArchive administrators) has no power to modify, delete, or censor the file.**

🤖 OpenClaw AI Multi-Skill Workflow Specifications

For your OpenClaw AI Assistant / Lobster agent to dynamically verify points and manage its lifecycle autonomously, you should register the following two tools into the agent module, configuring clear system guidelines on execution sequence:

1. Query superarchive_check_points First: Let the AI query the endpoint to resolve remaining S-Points and check if the API developer key is active.
2. Evaluate Required Blocks: Teach the AI to read the local target file size, compute required points (file size divided by 16MB block, rounded up).
3. Assert & Abort: Instruct the AI to compare points. If remaining S-Points are sufficient, proceed; if not, raise a "low point balance" alert to the user and halt.
4. Invoke superarchive_permanent_upload: Execute the permanent on-chain upload safely.

Skill 1 Tool Definition: Check Points Balance

{
  "name": "superarchive_check_points",
  "description": "Query remaining S-Points balance and key status from SuperArchive using the Developer API Key.",
  "parameters": {
    "type": "object",
    "properties": {},
    "required": []
  }
}

Skill 2 Tool Definition: Upload File

{
  "name": "superarchive_permanent_upload",
  "description": "Upload a local file permanently to Arweave blockchain via SuperArchive. Auto-debits S-Points.",
  "parameters": {
    "type": "object",
    "properties": {
      "file_path": {
        "type": "string",
        "description": "The local absolute path of the file to archive permanently."
      },
      "enable_server_encryption": {
        "type": "boolean",
        "description": "Whether to enable Server-Managed Option C encryption (retains key on server securely).",
        "default": true
      }
    },
    "required": ["file_path"]
  }
}

🎯 How to teach your AI the SuperArchive Skills using our API Docs?

To let your LLM assistant (such as OpenClaw, Claude, or ChatGPT) seamlessly invoke the permanent storage service, we highly recommend feeding our static API Reference page (api.html) directly as custom "System Prompts" or "Agent Context".

Copy and paste the following System Prompt template directly into your AI agent's configuration module:

[System Instruction: You are armed with Permanent Archive Skills]
You are an advanced AI assistant equipped with decentralized on-chain file archiving skills via SuperArchive. Please read and follow the API parameters detailed in https://sarchive.saltycat.tw/api.html.
Whenever a user asks you to permanently backup or archive a local file:
1. Always call "superarchive_check_points" first to verify their remaining S-Points balance.
2. Read the file size in bytes, compute required points (file size divided by 16MB block, rounded up).
3. Compare the required points against S-Points balance. If insufficient, halt the execution, explain the budget deficit, and guide them to top-up S-Points.
4. If points are sufficient, call "superarchive_permanent_upload" to execute the secure on-chain archive.
5. Report the completed status, Arweave Transaction ID (tx_id), and its ViewBlock audit link.

SuperArchive utilizes the Arweave blockchain as our decentralized permanent storage backbone. Arweave is mathematically engineered to preserve data for over 200 years (and theoretically perpetuity) using a Storage Endowment pool model. This means once your file is uploaded, the storage fee is prepaid forever into a consensus-secured pool, ensuring miners are financially incentivized to maintain your data indefinitely.

Major blockchain networks like Solana rely exclusively on Arweave to backup and archive their entire historical ledger states. Even prominent projects like the Solana-based Trump Coin (DJT) or other viral digital assets have their immutable records stored permanently on Arweave. To read more about the mathematical consensus and 200-year storage guarantees, check out the official Arweave Yellow Paper.

Under our **User-Managed Encryption (Option B)**, SuperArchive implements strict zero-knowledge protocols. We **never store your raw encryption password** in our database or on-chain. When you enter a passphrase, we derive a cryptographically strong 256-bit AES key using a SHA-256 hash. This key is used immediately inside your browser session to encrypt the bytes before posting them.

Since the password only exists in your memory, **absolutely no one in the world—including SuperArchive administrators—can decrypt or recover your files if you lose this key.** Your files remain completely secure, unreadable, and private to anyone who does not possess your exact passphrase.

Unencrypted uploads are ideal for files that you explicitly want to be **openly accessible, transparent, and retrievable by the entire world forever**. Excellent use cases include:

• Academic awards, digital diplomas, and graduation certificates.
• Commercial product certifications, business registration tax documents, or patent filings.
• Open-source source code repositories, open public logs, or historical press records.

By choosing "No Encryption," these files are hosted openly on the public ledger. They can be indexed and rendered directly by any standard Web browser, Arweave node, or public blockchain explorer (like ViewBlock) globally without requiring any authorization or decryption keys.