analyze-transaction

To convert Cardano transaction CBORs into YAML documentation, decode Atlas-provided V2 CBOR payloads into structured JSON and map transaction components like inputs, outputs, and mints to a YAML schema. This ensures repository documentation stays consistent with latest on-chain transactions.

Parsing Cardano CBOR extracts inputs, outputs, mints, withdrawals, reference inputs, fees, and datum references. These components are normalized into a YAML-friendly structure to generate comprehensive transaction documentation under the public/yaml/transactions/v2/ directory.

Generate YAML files for Cardano V2 transactions by ingesting decoded Atlas API CBOR data, mapping it to the repository YAML schema, and saving the output to public/yaml/transactions/v2/{system}/{role}/{tx-name}.yaml using established templates and conventions.

Yes, the YAML transaction generation process maps addresses to validators using address-registry.json and proposes registry updates. When new validators or patterns are discovered during CBOR analysis, it ensures the documentation aligns with the endpoint-registry.json definitions.

Yes, generated transaction YAML is validated against endpoint-registry.json and TypeScript definitions in the monorepo. This ensures the resulting YAML file path aligns with registry definitions and maintains structural consistency across the repository.