What types of transaction lanes does Kaspa support?

Kaspa recognizes three valid transaction lane types: native, coinbase, and user lanes, each distinguished by its 20-byte lane ID pattern. The native lane uses all zero bytes. The coinbase lane starts with the byte `0x01` followed by 19 zero bytes. User lanes use a 4-byte namespace prefix — with at least one non-zero byte in the last three of those four bytes — followed by 16 zero bytes. Any other byte pattern is either invalid or reserved for future Kaspa system use and will be rejected by the network. Understanding these three types matters if you are a developer building on Kaspa: your transactions must carry a correctly structured lane ID or they will not be accepted by the protocol.