agorix
AirdropMarketsCollectionsLeaderboardActivity
Agorix · Decentralized Marketplace
Independent · Resilient · Community-Run

A cross-chain marketplace, run by the community.

Discover, list, and trade across Bitcoin, Ethereum, and Solana on an open, community-run network.

Marketplace
CollectionsMarketsLeaderboardActivity
Network
GovernanceExplorerAirdropDocs
Account
ProfileSettings
Legal
Terms of ServicePrivacy PolicyYour Privacy Choices
agorix.io — Lasting Access
CID: 0xA60R1X · v0.1
AirdropMarketsCollections
D
Protocol Docs
Proof of AccessNetwork Fee RoutingRelease VerificationMPC Treasury SecurityPSBT SecurityNode AuthenticationRate LimitingBundle Integrity VerificationTransaction Session Reconciliation
Docs/Security & Verification/Transaction Session Reconciliation
Security & Verification

Transaction Session Reconciliation

Post-transaction audit system that links user sessions to on-chain transactions, detects discrepancies between simulated and executed transactions, and governance-locks suspect node stakes.

#Transaction Session Reconciliation

Even with bundle integrity enforcement, the marketplace includes a final safety net: every transaction is audited after the fact by comparing the expected transaction (from the quorum simulation) against the actual on-chain transaction.

#Why This Layer Exists

The previous layers (SRI, content probing, attestation) prevent code tampering. But what if:

  • A rogue node somehow bypasses all code integrity checks?
  • A browser vulnerability allows execution despite SRI failure?
  • The node manipulates the transaction at the RPC level rather than the code level?

Session-TX reconciliation catches these by auditing on-chain state — it doesn't depend on code integrity at all.

#How It Works

#1. Session-TX Registration

When a user initiates a purchase, the serving node runs the quorum simulation and records the mapping:

text
sessionHash ↔ txPlanHash ↔ walletAddress ↔ servingNodeId

This links the user's UI session to the specific transaction plan that the quorum attested.

#2. On-Chain Observation

After a transaction appears on-chain, honest nodes observe it and extract:

  • Transaction hash
  • Recipient addresses
  • Transfer amounts
  • Contract calls and parameters

#3. Reconciliation

The engine compares the on-chain observation against the registered session plan:

CheckWhat It Catches
TX_PLAN_HASH_MISMATCHOn-chain tx doesn't match the attested plan — node substituted a different transaction
UNATTESTED_TX_DURING_SESSIONA transaction occurred from the user's wallet during a session with no corresponding attestation — node injected an unauthorized tx
UNEXPECTED_RECIPIENTFunds went to addresses not in the original plan — payment diversion attack
AMOUNT_MISMATCHTransfer amount differs from the simulated amount — partial theft

#4. Consequences

Discrepancies trigger immediate governance actions:

SeverityTriggerGovernance LockMisbehavior Strike
WARNINGAmount mismatch48 hoursNo
CRITICALPlan hash mismatch, unexpected recipient, unattested tx168 hours (7 days)Yes

Governance lock prevents the suspect node from unstaking its collateral while under investigation. This is implemented via applyGovernanceLock() which extends the node's withdrawableAt timestamp.

Misbehavior strike feeds into the escalating penalty system (24h → 72h → 168h → permanent ban).

#Client-Side Direct Witness Verification

In addition to server-side reconciliation, the client independently verifies the quorum result:

  • After the loading node returns a quorum result, the client picks 2-3 random witness nodes.
  • The client contacts each witness directly (bypassing the loading node).
  • Each witness confirms it attested the claimed txPlanHash.
  • If any witness disagrees → the loading node fabricated the quorum result.

This prevents a compromised loading node from faking the entire quorum response.

#TX Attestation Cache

Each node maintains an in-memory cache of recent tx-plan attestations (10-minute TTL). When a client directly queries a witness at GET /node/tx-attest/verify/{hash}, the witness looks up the hash in this cache and confirms or denies its attestation.

#Protocol Events

text
TX_SESSION_DISCREPANCY
  discrepancyId: string
  sessionHash: string (64 hex)
  walletAddress: string
  chain: "BTC" | "ETH" | "SOL"
  onChainTxHash: string
  expectedTxPlanHash: string (64 hex)
  servingNodeId: string
  cohortNodeIds: string[]
  reason: "TX_PLAN_HASH_MISMATCH" | "UNATTESTED_TX_DURING_SESSION" |
          "SIMULATION_RESULT_DIVERGENCE" | "UNEXPECTED_RECIPIENT" | "AMOUNT_MISMATCH"
  severity: "WARNING" | "CRITICAL"
  stakeLocked: boolean
  lockHours: number
  detectedAt: ISO timestamp

#Defense in Depth Summary

The full transaction security stack, from first to last line of defense:

LayerWhat It ProtectsWho Enforces It
SRI integrity attributesCode authenticityBrowser (cannot be bypassed by JS)
Bundle manifest consensusNode code agreementAll nodes via gossip
Content probingAgainst two-directory attacksHonest nodes (browser-like requests)
Client bundle attestationAgainst IP discriminationClient + peer nodes
TX-plan quorumTransaction plan agreementWitness nodes (67% BFT)
Client witness verificationAgainst fake quorum resultsClient + witness nodes directly
Session-TX reconciliationAgainst post-attestation tamperingAll honest nodes + on-chain state
Governance stake lockFlight risk during investigationSmart contract / protocol
Misbehavior strikesRepeat offendersEscalating penalties → permanent ban
PreviousBundle Integrity VerificationNext Node Architecture

On this page

  • Transaction Session Reconciliation
  • Why This Layer Exists
  • How It Works
  • 1. Session-TX Registration
  • 2. On-Chain Observation
  • 3. Reconciliation
  • 4. Consequences
  • Client-Side Direct Witness Verification
  • TX Attestation Cache
  • Protocol Events
  • Defense in Depth Summary