Skip to main content

Security Guarantees

The architecture of PiNS guarantees absolute security, immutability, and decentralization, ensuring that no single entity can corrupt the domain database.

ZK-SNARKs: Cryptographic Proof of Integrity​

In standard database systems, you must trust the database administrator (or sequencer) not to modify records. In PiNS, trust is replaced by math.

  • The Arbitrum smart contract will only accept a root update if it is accompanied by a valid ZK proof.
  • Because the zkVM Rust guest program strictly enforces domain ownership and transaction rules, the sequencer cannot arbitrarily assign a domain to a different owner, modify an address without a signature, or double-spend a listing. If they try, the ZK proof generation will fail, and the Arbitrum contract will reject the update.

A Sovereign Rollup Model​

PiNS is conceptually identical to a ZK-Rollup:

  • Data Availability: The raw transaction data is kept on PIVX, enjoying PIVX's native security and immutability.
  • Execution: Processing is offloaded to the SP1 zkVM off-chain.
  • Settlement: Arbitrum acts as a highly-efficient consensus coordinator that anchors the state root, verifying the math in milliseconds.

Maintaining Consensus (Solving the Split-Brain Problem)​

A common problem in distributed systems is "split-brain," where different servers show different target addresses for the same domain. PiNS solves this using Arbitrum Checkpoints:

  1. Every verified state root update on the Arbitrum contract is mapped to the exact PIVX Block Height it represents.
  2. Indexers sync to this specific block height and compute their own local Merkle Tree.
  3. If an indexer's local root differs from the contract's checkpoint, the indexer knows immediately that it has missed a transaction, processed data out-of-order, or encountered a database error.
  4. The indexer can then safely sync back to the verified history, ensuring that all resolvers globally maintain a single, consistent state.

Trustless Auditability (Auditing from the Outside)​

Because all raw transaction data is recorded on the public PIVX blockchain and the guest program rules are open-source, the system is completely audit-free and transparent:

  • The Verification Key (vkey) Guarantee: Anyone can download the open-source Rust guest program, compile it locally using standard SP1 tools, and check that the generated vkey matches the programVkey stored in the PiNSAnchor smart contract. This proves that the smart contract is enforcing the exact, unmodified protocol rules without hidden loopholes or backdoors.
  • State Transition Verification: Anyone can scan the PIVX blockchain from PiNS Genesis Block, extract all name service transactions, and run them through the guest program locally.
  • State Root Matching: By replaying the transactions, your local indexer will compute a Merkle Root that matches the verified roots recorded on the Arbitrum smart contract.
  • State Verification: This allows any third party, developer, or auditor to cryptographically prove that the naming service is valid, secure, and has not been tampered with since its creation.

Why This is the Best Solution for Non-Smart-Contract Chains​

For blockchains like Bitcoin or PIVX that prioritize security and transaction speed over smart contracts, building complex apps natively is impossible. The standard alternative is using a trusted centralized server, which introduces a single point of failure and censorship.

PiNS provides a third way: decentralized off-chain execution with zero-knowledge verification. It brings EVM-grade security and naming features to PIVX without altering PIVX's core protocol, keeping user private keys safe and maintaining absolute decentralized ownership.