Please review Koinly’s existing Blackcoin (BLK) import against the independently maintained Blackcoin-Dev Protocol V4 v30.1.3 data model.
Source commit: 86c6855ab135afe784635a564f21c74d67aa366b
Security and limitations: https://projectblackcoin.org/security
BLK is a native UTXO chain, not a token or contract asset. Other historical Blackcoin maintainers dispute the status of this implementation; no endorsement or exclusive status is claimed.
For import purposes, ordinary base-chain transactions and Protocol V4 Gold Rush shadow records must remain separate. During Gold Rush, shadow records are synthetic, non-Merkle, and phase-locked. They are not ordinary base-chain transactions or currently spendable base-layer BLK. They should not be mapped to ordinary sends, receives, staking rewards, or balances unless Koinly separately defines and validates an appropriate lifecycle-aware record type.
The public interface is read-only JSON/OpenAPI. /api/explorer/address/{address} returns separately paginated base activity and shadow history. Base activity is limited to the index coverage disclosed by /api/explorer/status; the public API must not be treated as a complete historical export.
No first-party Koinly-formatted CSV endpoint is currently documented. If Koinly provides its required columns and field semantics, Blackcoin-Dev can prepare a sanitized sample mapping for ordinary base-chain transactions and a separate proposed schema for shadow records.
Please advise whether Koinly prefers an existing-import update, an API field map, or a CSV-template proposal.
This request seeks technical schema guidance only. It does not assert Koinly compatibility, completed integration, tax treatment, endorsement, or any integration outcome.
Blackcoin-Dev