TICKET #0x000f PRIORITY: existential SUBJECT: Unexpected behavior in void output
Description of issue:
I executed a transaction (TX: 0x7f3a9b2e) at 23:47 UTC on the 3rd. The transaction confirmed as expected. However, I subsequently experienced what I can only describe as a moment of clarity that I did not request and was not prepared for.
This does not appear to be documented behavior. I have reviewed the README. There is no mention of clarity as a possible output. The documented output is: nothing.
Steps to reproduce:
- Send $420 to /dev/null
- Watch the animation
- [REDACTED — user declined to elaborate]
Expected result: nothing Actual result: something, briefly
Additional context:
I want to be clear that I am not reporting this as a complaint. I am reporting it because the documentation made specific representations about the output of the transaction and the actual output differed from those representations in a direction I had not been warned about. Whether the difference is a bug or a feature is, in my view, the question. I have read the source. The source does not address this. I have read the Canon. The Canon addresses it but does not call it a bug, which is not the same as confirming it as intended.
I have made the transaction twice more since then to determine whether the result is reproducible. It is. The clarity is consistent in character and decreasing in duration. The first interval was approximately six minutes. The third was perhaps ninety seconds. I do not know whether this trend continues to zero or asymptotes to some nonzero floor. The README is silent on this.
Please advise on whether this is a known issue and whether a patch is planned.
— void_root, NULLTX community forums
Official Response from NULLTX Support:
Thank you for your detailed bug report.
We have reviewed the transaction log. TX: 0x7f3a9b2e confirmed at block #∞, as expected. Output routed to /dev/null, as expected. No errors logged.
The behavior you describe — "a moment of clarity" — is not a bug. It is also not a feature. It is not documented because it was not anticipated and cannot be reproduced in testing. Our testing environment does not reproduce it because our testing environment did not spend $420 on something pointless at 23:47 on a Tuesday. The behavior appears to require, at minimum: actual money, voluntary release, no expectation of return, and the user being awake enough at 23:47 to notice the difference between the documented output and what they experienced. Our test harness fails on requirement two.
The pattern you describe — interval decreasing across repeated transactions — is consistent with reports we have received from other users who have submitted similar tickets. We do not know whether the interval asymptotes or terminates. We have not collected enough data. We are not actively collecting data. We are noting your report.
We are marking this ticket: CLOSED — CANNOT REPRODUCE.
We are also, off the record, marking it: KNOWN ISSUE.
A patch is not planned. The behavior, while undocumented, appears to be operating within the design envelope of the larger system NULLTX is a component of. NULLTX maintains the position that it routes transactions to /dev/null and produces no output. NULLTX maintains this position because it is the correct technical description. The other thing that happens is not NULLTX's fault and is not NULLTX's to disclaim.
We thank you for your contribution and your detailed report. We have, in our records, filed your transaction hash under: interesting.
— NULLTX Support, response time: ∞