Blockchain Integration

Uhpenry empowers creators, developers, and teams to control how their projects are published, accessed, and monetized.
At the core of this system is the Snapshot, a container holding a project's configuration, access model, and transactional state.

Currently, Snapshots are stored in Uhpenry's database.
As the platform scales, immutability, auditability, and verifiability become crucial, this is where blockchain integration comes in.

The blockchain will augment Snapshots, making them verifiable, tamper-proof, and trustless, without replacing the existing model.

---

What is a Snapshot?

A Snapshot is the atomic unit of a project's lifecycle in Uhpenry.
It captures:

• Project state: files, metadata, structure.
• Access configuration: Showcase, Download, Gated Source, Invite.
• Snapgate permissions: who can see or do what.
• Snapcharge transactions: payments, free or paid unlocks.
• Snapshot History: a timeline of changes and events.

Think of a Snapshot as a frozen moment in time, representing a project version, its access rules, and how users interact with it.
Each Snapshot is self-contained but evolves over time: every project update creates a new Snapshot linked to its predecessor, forming a complete history.

---

Current Database-Only Model

All Snapshots are currently stored in Uhpenry's internal database, which allows:

• Fast reads and writes.
• Full control over access permissions.
• Ability to update or correct records.

Limitations:

• Data integrity depends on Uhpenry's infrastructure.
• Snapshots could theoretically be altered internally or via attacks.
• Proof of authenticity is centralized.

This is sufficient for early-stage adoption, but trust and autonomy for creators require more.

---

Blockchain Roadmap

Uhpenry's blockchain integration is progressive, providing security without burdening users with blockchain complexities like wallets or gas fees.

Step 1: Pointer-Based Integration

• Snapshots are validated before being recorded on-chain:
  • Access/payment success?
  • Snapcharge transaction confirmed (if paid)?
  • Creation flow succeeded (if free)?
• Blockchain stores:
  • Hash of the Snapshot data (immutability).
  • Block ID / transaction hash (verifiability).
  • Pointer to Uhpenry's internal database.
• The block ID pointer is retained in Uhpenry's database.

Benefits:

• Developers query Snapshots as usual.
• Results are verifiable against blockchain entries.
• No user wallets or blockchain management required.

---

Step 2: Immutable Audit Trail

Every Snapshot version generates a linked chain of history:

• Old Snapshots are hashed and archived.
• New Snapshots are linked to their predecessors.
• Forms a permanent, on-chain audit trail, like Git, but every commit is provable and immutable.

---

Step 3: Decentralized Querying

Currently, Snapshots are queried from Uhpenry's database even if hashed on-chain.
Future goal: query directly from blockchain storage while keeping Uhpenry's DB as an index/cache.

Technologies under evaluation:

• Aptos: high-throughput L1 blockchain for complex apps.
• Vara Network (Gear Protocol): lightweight WASM-based smart contracts with signless, gasless interactions.
• Arweave: permanent decentralized storage for full Snapshot data.

In this model, Uhpenry indexes and displays immutable proofs, not storing Snapshots indefinitely.

---

Why This Matters

For creators:

• Snapshots are tamper-proof.
• Payments, licenses, and access rules are verifiable at publication.

For developers:

• Consistent API with no blockchain friction.
• Trustless verification for authenticity.

For Uhpenry:

• Moves toward full decentralization of knowledge assets.
• Reduces reliance on central infrastructure.
• Balances Web3 security with Web2 usability.

---

User Experience: Abstracted Blockchain

Uhpenry ensures users never have to “learn blockchain”:

• No wallet popups.
• No gas fees.
• No key signing confusion.

Backend handles all blockchain interactions, showing users only:

• Snapshot created successfully.
• Block ID / transaction hash for optional verification.

Everything else (fees, confirmation, storage) is invisible and seamless.

---

Summary

• Snapshots define a project's state in Uhpenry.
• Snapgate, Snapcharge, and Snapshot History interact within each Snapshot.
• Today: Snapshots centralized in Uhpenry database.
• Tomorrow: Snapshots anchored on blockchain with immutable proofs.
• Future: Snapshots queried from decentralized storage, with Uhpenry as the interface.

This Roadmap bridges centralized UX with decentralized trust, keeping Uhpenry developer-friendly while ensuring security and authenticity at scale.