mirror of
https://github.com/nspcc-dev/neo-go.git
synced 2026-03-01 04:28:51 +00:00
Improve tx verification error for ValidUntilBlock check failure #1584
Labels
No labels
I1
I2
I3
I4
S1
S2
S3
S4
U0
U1
U2
U3
U3
U4
blocked
bug
bug
cli
compiler
config
config
consensus
dependencies
discussion
documentation
enhancement
epic
feature
go
good first issue
help wanted
neotest
network
oracle
performance
question
rpc
security
smartcontract
task
task
task
test
vm
wallet
windows
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neo-go#1584
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ixje on GitHub (Dec 3, 2025).
Is your feature request related to a problem? Please describe.
I'm always frustrated when a tx fails but the verification error doesn't contain enough details to know how to resolve the problem. e.g.
My memory (and test case) said a
1000blocks is the max valid. Under those assumptions the above error message makes no sense.Looking at
nspcc-dev/neo-go@39f8079b7e/pkg/core/blockchain.go (L2931-L2932)GetMaxValidUntilBlockIncrement()must return a different value than the1000I expect(ed).Describe the solution you'd like
I would like some addition indicating what the max allowed value would have been to pass e.g.
ValidUntilBlock = 1001, current height = 1, max valid = 501Describe alternatives you've considered
n/a
Additional context
n/a