Terms of Service

1.0 General Provisions & Agreement to Protocol Covenants

1.1 Acceptance and Mutual Undertaking

These Terms of Service constitute a legally enforceable agreement between you and every other participant interacting with the NodeHash network. Launching client software, signing transactions with a NIST P-256 private key, or gossiping trade proposals confirms your unconditional consent to every clause herein.

1.2 Decentralized Software Topology

NodeHash is open-source software coordinating peer-to-peer economic exchange. When you submit barter requests or clear credits, you communicate directly with sovereign peer nodes over distributed network circuits. No centralized corporation directs your transactions, holds your trade assets, or manages your ledger records.

2.0 Explicit Non-Banking & Non-Custodial Software Classification

2.1 Software Protocol Classification

NodeHash is strictly an open-source software protocol and cryptographic accounting suite. NodeHash is not a money transmitter, bank, broker, or custodial escrow entity. The protocol is not a credit union, trust company, or insured depository institution. NodeHash is not a money services business or currency exchange dealer under the United States Bank Secrecy Act (FinCEN), European Union payment service directives, or any regional banking statute. NodeHash is not a securities broker-dealer, commodities merchant, investment advisor, or custodial clearinghouse.

2.2 Absence of Custodial Escrow or Fiat Transmission

The protocol does not accept, take custody of, hold, transmit, convert, or disburse sovereign fiat currencies, legal tender, or government-issued funds. Milestone escrow operations inside NodeHash don't hold fiat money in escrow vaults. Instead, milestone escrow operates solely as a cryptographic encumbrance on participant ledger headroom, locking mutual credit capacity until deliverables satisfy agreed verification conditions.

2.3 Nature of Mutual Credit Units

Units recorded on the NodeHash ledger are bilateral and multilateral accounting denominators measuring reciprocal barter obligations among peers. Credits are not legal tender, sovereign currency, stored electronic money, or investment securities. Credits carry no promise of redemption into fiat cash by protocol developers, relay operators, or node maintainers. Real-world value emerges solely from reciprocal delivery of professional services, crafts, and manufactured goods between independent peers.

3.0 Mutual Credit Accounting Covenants & Invariants

3.1 Strict Zero-Sum Conservation Invariant

Participants covenant that all ledger state transitions must obey the mathematical conservation law:

∑ B_i(t) = 0   and   ∑ ΔC = 0

Every credit increment (+C) credited to a performing peer requires an exact, matching debit obligation (-C) assumed by a receiving peer or completed multi-party clearing cycle. No participant, node operator, or algorithmic routine can create unbacked credits outside authorized dynamic headroom limits.

3.2 Dynamic Credit Headroom Covenants

Your credit limit (L_i) defines the maximum deficit your account can carry. A negative balance is not delinquency; it represents a solemn covenant to deliver future services or goods to other network members. When your balance dips negative, you covenant to review reasonable barter requests matching your published skills and make good-faith efforts to return your ledger balance toward zero.

3.3 Default and Contagion Containment

Abandoning an account with an unpaid negative balance, refusing reciprocal trade proposals without valid cause, or failing to satisfy settled milestone commitments constitutes an actionable protocol default. Defaulted accounts are immediately frozen from initiating new trade proposals. Unresolved deficits are then resolved through the sponsor lineage damping covenants established under Section 5.0.

4.0 Milestone Escrow & Intellectual Property Transfer

4.1 Six-Stage Milestone State Machine

Multi-stage barter agreements execute through our deterministic six-stage lifecycle: Proposed, Funded (Headroom Encumbered), InProgress, Submitted, Accepted, and Settled. Headroom remains encumbered until the client inspects and cryptographically approves submitted deliverables.

4.2 Irrevocable Assignment of Intellectual Property Rights

When a client counterparty broadcasts a cryptographic signature approving a completed milestone, the provider counterparty hereby irrevocably sells, assigns, and transfers to the client all right, title, and interest worldwide in and to the submitted deliverables.

This transfer encompasses all copyright, patent, design, trade secret, and intellectual property rights. The assignment operates automatically upon cryptographic milestone acceptance signature, free and clear of all liens, claims, or encumbrances. If applicable law restricts assignment, the provider grants an exclusive, perpetual, worldwide, fully paid-up, royalty-free license to use, reproduce, modify, and distribute the work product.

4.3 Provider Warranties of Originality

Providers represent and warrant that all delivered work product is original, created solely by the provider or properly licensed contributors. Providers warrant that deliverables do not infringe upon any copyright, trademark, trade secret, or patent of any third party.

4.4 Inspection Windows & Good-Faith Review

Clients covenant to inspect submitted deliverables within the agreed inspection timeframe. Frivolous rejections, bad-faith delay tactics, or attempts to harvest deliverables without signing milestone acceptance breach this agreement and trigger community arbitration.

5.0 Sponsor Lineage Damping Liabilities

5.1 The Enforceable Sponsor Guaranty

To eliminate invasive identity surveillance and corporate KYC background checks, NodeHash relies on peer sponsorship. Every newcomer must be sponsored by an established participant. Sponsoring a new participant is a binding legal guaranty in which the sponsor pledges their own credit headroom as security for the invitee's good conduct and ledger solvency.

5.2 Mathematical Damping Liability Formula

If a sponsored participant defaults on an outstanding mutual credit deficit or commits verified fraud, financial responsibility attaches automatically to their sponsor lineage. Contagion liability is calculated according to the geometric damping decay function:

\text{dampingFactor}(d) = 0.5^{d-1} \quad \text{for } d \in \{1, 2, 3\}

Liability distributes through the sponsor graph as follows:

• Depth 1 (Direct Sponsor, d = 1): Absorbs 100% of the default balance up to the sponsor's available headroom limit.
• Depth 2 (Grandparent Sponsor, d = 2): Absorbs 50% of any remaining deficit unabsorbed by the direct sponsor.
• Depth 3 (Great-Grandparent Sponsor, d = 3): Absorbs 25% of any remaining deficit unabsorbed by depth 2.
• Depth > 3: Decoupled. Sponsors beyond three hops absorb 0% liability, preserving network-wide systemic stability.

5.3 Automated Headroom Offset Authorization

By sponsoring a peer, you explicitly authorize the NodeHash risk engine to encumber or debit your available credit headroom upon a formal default determination. This liability offset is self-executing across the peer-to-peer ledger network.

6.0 Hardware Authentication & Cryptographic Key Responsibilities

6.1 Hardware Enclave Isolation

Participants must generate and store their signing keys inside certified hardware security environments: Apple Secure Enclave, Android KeyStore with StrongBox, or FIDO2/WebAuthn authenticators. Local biometric scans (Face ID, Touch ID, BiometricPrompt) unlock signing keys within hardware chips and never leave device silicon.

6.2 Irrefutable Evidentiary Presumption

Any barter offer, cycle clearance, milestone sign-off, or credit allocation signed by your NIST P-256 private key creates a conclusive legal presumption that you authorized the action. You cannot disclaim liability for cryptographic transactions bearing your valid digital signature.

6.3 Loss of Device and Key Material

NodeHash maintainers and relay operators don't hold backups, escrow copies, or recovery keys. If you lose your hardware authenticators without a recovery sponsor arrangement, your access is permanently lost. NodeHash accepts zero liability for lost, stolen, or damaged devices.

7.0 Participant Conduct & Prohibited Trade Activities

7.1 Compliance with Applicable Laws

You covenant to use NodeHash only for lawful purposes. You remain solely responsible for identifying and complying with all tax, licensing, labor, and commercial laws applicable to your jurisdiction.

7.2 Prohibited Goods and Services

You may not use NodeHash to offer, request, or settle trades involving:

• Illegal narcotics, controlled substances, or hazardous chemical agents.
• Unlicensed firearms, ammunition, explosives, or military-grade hardware.
• Stolen personal information, computer exploits, or unauthorized access credentials.
• Human trafficking, forced labor, or non-consensual exploitation of any person.
• Transactions designed to evade international sanctions or engage in fraudulent money laundering.

7.3 Prohibition of Wash Trading and Sybil Attacks

Creating fake accounts, orchestrating wash trades to fabricate credit limits, or attempting cycle griefing attacks to exhaust peer liquidity constitutes fraudulent breach of contract. Accounts identified in Sybil attacks face immediate community blacklisting and sponsor liability attachment.

8.0 Community Dispute Arbitration & Class Action Waiver

8.1 Mandatory Peer Arbitration

Any controversy, claim, or dispute arising out of milestone inspections, deliverable quality, or default determinations must be resolved exclusively through the NodeHash decentralized community arbitration mechanism. Conventional judicial lawsuits and state court proceedings are expressly excluded to the fullest extent permitted by law.

8.2 Community Arbitration Procedures

When a dispute is escalated:

• A rotating panel of three disinterested, high-reputation peer nodes is selected via verifiable randomness.
• Both counterparties submit cryptographic delivery artifacts, milestone specifications, and signed communication receipts.
• The peer panel reviews the record and issues a multi-signature verdict.
• The arbitration verdict is final, binding, and directly clears the encumbered escrow headroom on the ledger.

8.3 Class Action and Representative Action Waiver

All arbitration proceedings must occur on an individual basis. You explicitly waive any right to bring, join, or participate in any class action lawsuit, collective arbitration, private attorney general proceeding, or representative action against protocol developers, relay node runners, community arbitrators, or fellow participants.

9.0 Warranty Disclaimers & Limitation of Liability

9.1 Software Provided "AS IS"

The NodeHash protocol, client software, and network relays are provided on an "as is" and "as available" basis. To the maximum extent permitted by law, creators, maintainers, and community contributors disclaim all warranties, express or implied, including warranties of merchantability, fitness for a particular purpose, and non-infringement.

9.2 Limitation of Damages

In no event will NodeHash developers, contributors, relay operators, or community arbitrators be liable for any indirect, special, incidental, consequential, or punitive damages. This limitation covers loss of profits, lost data, hardware damage, or lost barter credits arising from software defects, network interruptions, or counterparty defaults.

10.0 Protocol Governance, Severability & Miscellaneous

10.1 Severability

If any provision of these Terms is deemed unlawful, void, or unenforceable, that specific clause will be severed or interpreted to reflect original intent to the maximum extent permissible. The validity and enforceability of remaining provisions remain undisturbed.

10.2 Entire Covenants

These Terms, combined with cryptographic milestone agreements and network governance rules, embody the complete understanding between participants concerning the NodeHash protocol.

10.3 Contact and Governance Coordination

Protocol improvement proposals, dispute escalation protocols, and governance discussions take place in our public coordination forums:

• Community Desk: Support & Community Coordination Desk
• Source Code & Governance RFCs: GitHub Protocol Governance
• FAQ & Economics: Frequently Asked Questions