
Product
Socket Threat Intel Now Shows Which Malware Campaigns Were Blocked or Detected
Socket Threat Intel now shows which malware campaigns were blocked or detected in your organization, with links to scans and Firewall events.
@aifinpay/deployments
Advanced tools
Contracts deployment registry for AiFinPay SDK and Agent Passport identity and settlement protocol.
This package provides a programmatic interface for querying AIFP deployment records and contract artifacts (ABI/IDL).
import { AifinpayRegistry, ArtifactRegistry } from "@aifinpay/deployments";
// Load deployment registries
const evmRegistry = AifinpayRegistry.loadEvm("latest"); // or "1.4", "1.3", etc.
const solanaRegistry = AifinpayRegistry.loadSolana("latest");
// Load contract artifacts
const artifacts = ArtifactRegistry.load();
// Query deployments
const optimism = evmRegistry.getEvmDeployment(10);
const splitterAddr = evmRegistry.getSplitterAddress(10);
const stablecoins = evmRegistry.getStablecoins(10);
// Get supported chains
const chains = evmRegistry.getSupportedChains("enabled");
const networks = evmRegistry.getNetworkList(); // [{ chainId, name, settlementEnabled, testnet }]
// Export as markdown/json/csv
const markdown = evmRegistry.exportAsMarkdown("prod");
const json = evmRegistry.exportAsJson();
const csv = evmRegistry.exportAsCsv();
// Query artifacts
const abi = artifacts.getEvmAbi("B2BSplitterV14", "1.4");
const solanaIdl = artifacts.getSolanaIdl("mainnet");
See USAGE.md for complete documentation.
Use the registry index to select the actual machine-readable record for the required ecosystem, version, chain and route. Addresses, program IDs, runtime hashes, governance and provenance belong in those records, not copied tables here.
Registry queries read packaged metadata; they do not check live chain state or backend receipt verification. Settlement flags are not current verification results. Follow the index's runtime/backend verification checklist and obtain fresh end-to-end evidence before claiming availability. Never infer activation from an export.
src/grabber.ts pulls the latest deployment records from the canonical
upstream repositories and produces per-ecosystem split registry files:
registry/splitter/evm/v1.4/deployments.jsonregistry/splitter/solana/deployments.jsoncd deployments
npm ci --no-audit --no-fund
npm run build # compile TypeScript
npm run registry:build # fetch upstream + write registry/*.json
npm test # offline unit tests
Per-ecosystem split files are the canonical artifacts. ABI and IDL subdirectories are kept for downstream consumers that need raw contract artifacts:
registry/
├── splitter/ # versioned registry with governance metadata
│ ├── evm/
│ │ ├── v1.4/deployments.json # EVM v1.4 full contract suite
│ │ ├── v1.3/deployments.json # EVM v1.3 route table
│ │ ├── v1.2/deployments.json # EVM v1.2 legacy
│ │ └── v1.1/deployments.json # EVM v1.1 legacy
│ ├── solana/deployments.json # Solana v1.4 program deployments
│ └── casper/deployments.json # Casper deployments
├── abi/
│ ├── evm/ # EVM ABI bundles (B2BSplitterV14, TimelockWrapper)
│ └── tron/ # Tron ABI bundles when applicable
└── idl/
├── solana/ # Solana IDL (splitter-v14 mainnet/devnet)
├── aptos/ # Aptos IDL artifacts
└── casper/ # Casper IDL artifacts
The registry index links versioned JSON records and interface guides, and the payment deployment JSON Schema describes their ecosystem-specific record shapes. Output selection is implemented in the grabber and build CLI; upstream provenance is stored in the generated JSON rather than this README.
AifinpayRegistry.loadEvm(version?) — load EVM deployment registry (default: "latest" = "1.4")AifinpayRegistry.loadSolana(version?) — load Solana deployment registry (default: "latest" = "1.4")getEvmDeployment(chainId) — O(1) lookup by chain IDgetEvmByNetwork(network) — lookup by network namegetSplitterAddress(chainId), getTokenListAddress(chainId), getProfilesAddress(chainId) — contract addressesgetStablecoins(chainId) — stablecoin listisSettlementEnabled(chainId) — recorded settlement flag, not a live checkgetGovernanceSafe(env) — Safe multisig addressgetProdDeployments(), getTestnetDeployments() — filteringgetSupportedChains(filter?) — get list of supported chain IDs (filter: "all" | "prod" | "testnet" | "enabled")getNetworkList(filter?) — get network list with metadataisChainSupported(chainId) — check if chain is supportedgetChainIdByNetwork(network) — get chain ID by namegetNetworkByChainId(chainId) — get network name by IDexportAsMarkdown(filter?), exportAsJson(filter?), exportAsCsv(filter?) — export formatsArtifactRegistry.load() — load all ABI/IDL artifactsgetEvmAbi(contractName, version?) — EVM ABIgetSolanaIdl(cluster) — Solana IDL (mainnet/devnet)getCasperIdl(network) — Casper IDL (mainnet/testnet)getAptosIdl(contractName, version?) — Aptos IDLgetTronAbi(contractName, version?) — Tron ABIbuildRegistry() — fetch upstream EVM + Solana records (deprecated: use AifinpayRegistry.loadEvm())writeSplitRegistries(registry, outDir) — write split registry filesgrabEvmDeployments() / grabSolanaDeployments() — grab one chain familygetEvmDeployment(registry, chainId) / getSolanaDeployment(registry, cluster) — O(1) lookup helpersisEvmDeployment(d) / isSolanaDeployment(d) — type guardsDeploymentRegistry, EcosystemRegistry, Deployment, EvmDeployment, SolanaDeployment, StablecoinEvmDeploymentRecord, SolanaDeploymentRecord, EvmAbiArtifact, SolanaIdlArtifactFAQs
Contracts deployment registry for AiFinPay SDK and Agent Passport identity and settlement protocol.
The npm package @aifinpay/deployments receives a total of 185 weekly downloads. As such, @aifinpay/deployments popularity was classified as not popular.
We found that @aifinpay/deployments demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.

Product
Socket Threat Intel now shows which malware campaigns were blocked or detected in your organization, with links to scans and Firewall events.

Security News
Fixes for eMudhra and Brotli are out. Getting them everywhere they’re needed means tracking down bundled libraries, runtimes, and certificate stores.

Threat Research
/Security News
Socket uncovered secret-stealing workflows that ran in LiteLLM’s GitHub repository 11 days before the supply chain attack on PyPI and Docker.