WAX Dev Needed: Full History API Export (NFTs, Alcor, Gaming)

I need a blockchain data developer to extract the complete transaction history for two WAX blockchain wallets, going back to account creation. This must be done via API calls directly against WAX blockchain infrastructure — not through the WAXblock.io frontend explorer, which is confirmed to omit a significant share of transactions (inline actions, contract-internal transfers, and gaming-related activity in particular). The output must be a clean, complete CSV following a template I will provide, suitable for use in tax reporting. Scope of Work Data to extract, per wallet: Native token transfers (WAX, and any fungible tokens held/transferred) — full history, including inline/internal actions triggered by smart contracts, not just top-level transactions. NFT activity — mints, transfers, trades, and burns across AtomicAssets-based collections. NFT marketplace trades — buys/sells/offers on AtomicMarket. Alcor Exchange DEX activity — all swaps and trades involving WAX-ecosystem tokens (e.g. TLM, and others held in the wallets). Play-to-earn / gaming contract activity — token rewards, staking/unstaking, and in-game asset movements from contracts such as Alien Worlds, Farmers World, R-Planet, and Prospectors (exact list confirmed once wallets are shared). This includes token types that may not have reliable market pricing (illiquid/game-specific tokens) — these must still be extracted with quantities and contract/symbol identified even if a USD price isn't attached at extraction time. Staking and delegation events related to WAX CPU/NET/REX if applicable. Recommended data sources (freelancer should confirm familiarity with these or equivalent tools): Hyperion History API (full action history, including inline actions — this is the key gap versus the WAXblock frontend) AtomicAssets / AtomicMarket API (NFT mints, transfers, market trades) Alcor Exchange API (DEX swap history) Direct table queries against relevant gaming smart contracts where the above APIs don't cover custom contract logic Output format One CSV per wallet (or one combined CSV with a wallet-identifier column — to be confirmed with client). Strict column template will be provided by the client before work begins (fields will include: date/time UTC, transaction ID, action type, contract, token/asset identifier, quantity, counterparty account, category tag [NFT trade / DEX swap / gaming reward / staking / transfer], and raw memo field). No deduplication or "cleaning" of data without a clear audit trail — every row must be traceable back to an on-chain transaction ID. Data Validation & QA Process (required before final payment) Delivery will happen in segments, not as one final file, so issues can be caught early rather than at the end: Discovery phase deliverable: before full extraction, freelancer provides a transaction count per data category, per wallet (e.g. "Wallet A: ~4,200 token transfers, ~1,100 NFT trades, ~600 Alcor swaps, ~2,000 gaming contract actions"). This sets the actual scope and time estimate. Segmented delivery: data delivered in chunks (e.g. by quarter, or by category) rather than all at once, so each segment can be validated before the next is started. Reconciliation check (primary validation method): for each fungible token, the sum of all inflows/outflows in the CSV must equal the wallet's current on-chain balance for that token (verifiable via a single balance query). For NFTs, the set of assets implied as "currently held" by the CSV must match the wallet's actual current AtomicAssets holdings. Any mismatch means missing or duplicated transactions and must be resolved before that segment is accepted. Spot-check sampling: client will manually verify a random sample of rows per segment (e.g. one full week per quarter) against the WAXblock explorer and/or Hyperion API directly, to catch classification or formatting errors. Final sign-off: full payment released only after all segments pass reconciliation and spot-check on the complete date range. Estimated Time & Budget Guidance Time cannot be fixed precisely until the discovery phase confirms transaction volume — WAX gaming wallets active since 2021 commonly range from a few thousand to well over 50,000 actions depending on activity level (staking/crafting loops in play-to-earn games generate very high transaction counts). Recommended structure: Phase 1 — Discovery & scoping (fixed small fee, ~2-4 hours of work): confirm transaction counts, propose final CSV schema, flag any contracts needing custom handling. Phase 2 — Extraction & delivery (priced per segment or as a total based on Phase 1 findings): rough industry benchmark is 1-3 days of developer time per 10,000-15,000 actions across mixed contract types, but request the freelancer's own estimate once Phase 1 is complete rather than committing to a number upfront. Required Skills Experience with EOSIO/Antelope-based chains (WAX runs on Antelope) and their history API patterns (Hyperion or equivalent) Familiarity with AtomicAssets/AtomicMarket data structures Experience with DEX APIs (Alcor or comparable) Comfortable working with smart contract table data when no clean API exists (e.g. querying gaming contract tables directly via chain RPC) Python or Node.js for scripting the extraction (open to either) Prior experience producing tax-reporting-grade transaction exports is a strong plus Deliverables Discovery report (transaction counts per category, per wallet) Final CSVs per agreed template, delivered in validated segments Brief documentation of data sources/methods used and any known gaps or edge cases encountered (e.g. contracts with incomplete on-chain data)