Amp Compliance & Risk FAQ

For treasury, risk, and compliance teams evaluating Amp as a verified blockchain data infrastructure layer for regulated institutions.

Data integrity and audit trail

• What does cryptographic provenance mean for our data?
  Every dataset Amp produces preserves cryptographic provenance, tracing back to the onchain source. This means any record can be independently reproduced and verified without relying on a vendor to reconstruct it. For your compliance team, that is the difference between data you can stand behind and data you have to explain.
• Can Amp-verified data be used in regulatory examinations and SAR filings?
  Yes. Amp is designed to support regulatory examinations and SAR preparation by preserving dataset lineage and reproducibility. Auditors and regulators can independently verify the origin and integrity of data directly from the record itself, without requiring access to internal systems. At the same time, whether a filing package is deemed sufficient continues to depend on your institution’s controls, policies, and expectations of its regulations.
• Is audit-ready lineage a reporting add-on or built into the product?
  It is built in. Audit-ready lineage is a core output of Amp, not a layer you configure separately.
• What happens to our audit trail if a blockchain reorganization occurs?
  Amp tracks the block hash and parent block hash for every dataset it produces. When a reorg occurs, data associated with orphaned blocks is invalidated and the stream resumes from a confirmed checkpoint against the canonical chain. Because Amp links data using block hashes rather than block numbers alone, the correction is precise and the lineage is fully traceable for an examiner.

Regulatory compliance

• Does using Amp create crypto regulatory exposure for our institution?
  No. Amp is a blockchain data infrastructure layer, not a digital asset, cryptocurrency, or financial instrument. Deploying Amp does not mean your institution is holding, transacting, or custodying digital assets. The blockchain component provides data provenance and verifiability. Amp is purpose-built for regulated banks, stablecoin issuers, and large enterprises that need compliant infrastructure without taking on crypto-related regulatory exposure.
• How does Amp address GENIUS Act compliance?
  Amp is built for institutions navigating GENIUS Act rules, treasury screening, and evolving digital asset reporting requirements. It provides auditable lineage, reproducible datasets, and data sovereignty controls that align with the Act's documentation standards. For institutions with existing or emerging digital asset exposure, Amp provides the verified data foundation that makes compliance defensible.
• What about PPSI requirements?
  PPSI compliance is a specific use case Amp is designed to support. Because Amp can be deployed on-prem or in your own cloud environment, your institution retains full data sovereignty, which is a core requirement for PPSI-regulated institutions. You own and control your data from day one.
• Does Amp support AML and sanctions screening workflows?
  Amp integrates with your existing custody platforms, screening tools, and treasury systems, enhancing their effectiveness rather than replacing them. It provides structured, verifiable onchain data into those workflows, specifically supporting AML and sanctions screening within existing compliance systems. The result is screening output that is more defensible, because the underlying input data carries verifiable provenance.

Architecture and security

• Does our underlying data get written to a public blockchain?
  No. Amp reads blockchain data and transforms it into structured datasets stored in your data infrastructure, including Parquet storage and a metadata database. Amp preserves an auditable link to onchain origin, but your proprietary records and internal datasets are not written to a public blockchain.
• What certifications does Amp carry?
  Amp is being developed with enterprise security controls in mind. SOC 1 Type II and ISO 27001 standards are in process, and the team is trained on NIST and OWASP principles. For current certification status and security documentation, request the latest security package from the Edge & Node team.”
• Can we control where our data is deployed?
  Yes. Amp supports self-hosted deployment patterns as well as hosted usage, so you can choose cloud, on-prem, or hybrid depending on your operational model. For institutions with strict data sovereignty requirements, Amp can be deployed entirely within their own infrastructure with no dependency on third-party systems. There is no vendor lock-in.
• What query interfaces does Amp support?
  Amp supports SQL, Arrow Flight/Flight SQL, JSON Lines HTTP, REST-style Admin API, and GraphQL. Multiple chains are accessible via a single API. This means your existing data and BI tooling can connect without requiring teams to adopt a proprietary query language or rebuild pipelines.

Integration and deployment

• Does Amp replace our existing custody platforms or screening tools?
  No. Amp is positioned as a blockchain data infrastructure layer that integrates with your custody platforms, screening tools, and treasury systems. It is a data infrastructure layer that makes your existing compliance stack more reliable, not a replacement for it.
• What does implementation support look like?
  Edge and Node offers an advisory practice alongside Amp, designed for institutions that need help navigating where to start, what to avoid, and how to align compliance and technical teams. This is available as a standalone engagement for regulated institutions working through complex deployments.

Vendor risk

• Who is Edge and Node?
  Edge and Node is the founding team behind The Graph, the protocol for indexing and querying blockchain data, which has been in production since 2018. The team invented and standardized subgraphs across the industry and Graph Node, which is trusted by top-tier global financial institutions. Amp is Edge and Node's enterprise product, built specifically for regulated institutions and enterprises.
• Does Amp create vendor dependency or lock-in risk?
  No. You own and control your data from day one. Amp is designed to reduce vendor lock-in risk through self-hosted deployment options, open tooling, and datasets that retain lineage back to their onchain source.
• What happens to our compliance records if we stop using Amp?
  Because your data lives in your own environment and every dataset is independently reproducible from the onchain source, your compliance records remain intact and verifiable after the relationship ends. There is no proprietary format or vendor dependency that puts your audit trail at risk.