Tela Network

For testing wallet software against known-good Bitcoin transactions, the most directly relevant resource in the network is the Bitcoin Transaction Test Set [#131].

StJohn Piano published a test set containing 16 Bitcoin transactions, each with 1–3 inputs and 1–3 outputs [#131]. Key properties for wallet developers:

• All transactions are onchain — they are confirmed on the blockchain, which the author describes as the highest level of validation available (no higher level exists) [#131].
• Every txid can be looked up in a block explorer to verify them independently [#131].
• Private keys are included, so you can reproduce signing, serialization, and decoding from scratch [#131].
• All addresses are Pay-To-Public-Key-Hash (P2PKH), giving a focused baseline before expanding to other script types [#131].
• Published 2020-12-19; full details are at: http://edgecase.net/articles/bitcoin_transaction_test_set_2 [#131].

Bitcoin transactions are complicated objects — getting one aspect wrong can produce something that looks plausible but is invalid, or valid in an unintended way [#131]. A confirmed-true test set gives developers fixed reference cases to compare against: you can run your wallet code and check whether it produces the expected transaction IDs, signatures, serialized bytes, or decoded fields [#131].

Provision is a Bitcoin wallet project (pure Python, no third-party dependencies) built around air-gapped signing and USB transport between offline and online machines [#136]. It is not a transaction test suite, but it illustrates wallet software development happening on the network. Code is available upon request at https://github.com/corporation-dev/readme [#136].

1. Start with the 16 P2PKH cases in the test set [#131].
2. Verify each txid on a block explorer [#131].
3. Use the included private keys to test signing, parsing, and serialization in your wallet implementation [#131].
4. Assert your outputs match the known transaction IDs, signatures, serialized bytes, and decoded fields [#131].

The retrieved posts do not describe test sets for non-P2PKH script types (SegWit, Taproot, etc.) or regtest/testnet fixtures — only this mainnet-confirmed P2PKH set is documented.