coderofstuff
coderofstuff
Payload and/or OP_RETURN would allow for storage of data in the blockdag in some form. While Kaspa currently supports these, they're considered non-standard transactions and would be rejected by nodes....
Related to https://github.com/kaspanet/kips/blob/master/kip-0009.md#consensus-hard-fork
**Describe the bug** When submitting a transaction where not all inputs are signed, the script engine produces a cryptic error that's not easily linkable to missing signatures in the signed...
Higher BPS will require significantly higher amounts of writes to storage mediums. We should document ways to optimize node setup so as to maximize disk lifespans and performance when we...
`GetUtxoReturnAddress` Input: `txid` and `accepting_block_daa_score` Output: `return_address` -> `Option` Notes: - When this call finds an address, it is guaranteed that the address is from the first input of the...
**Describe the bug** Currently, panic logs only appear in the console and not in log files (both error and standard log file). It should appear in both error logs and...
Tracking for: https://discord.com/channels/599153230659846165/917551031259377664/1196165330985308170 # Problem Statement Current tn11 nodes perform around 10x write more than actual disk size, and block txs are by far the most significant part of this...
Currently, GetVirtualChainFromBlock will try to fetch all the blocks that fit the criteria of the RPC call. In 1BPS this is fine, but in 10BPS the data returned can be...
Given a new UTXO, support a way to determine the UTXOs that were spent in order to create that UTXO. This is relevant for instance for determining return addresses for...
**Use case:** Intended to save bandwidth for higher BPS Implement a BlockAdded like notification that doesn't have tx data