You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
insufficient fee, rejecting replacement (Failed to submit won block 666155 off block 666154 instead used 666152 even though 666153 and 666154 were known)
#2347
Closed
friedger opened this issue
Jan 15, 2021
· 4 comments
using the size of the previous transaction is not good enough apparently. Seeing variations of 338 - 352 bytes, so either we need to calculate actual tx size, or pad by at least 14
friedger
changed the title
Failed to submit won block 666155 off block 666154 instead used 666152 even though 666153 and 666154 were known
insufficient fee, rejecting replacement (Failed to submit won block 666155 off block 666154 instead used 666152 even though 666153 and 666154 were known)
Jan 19, 2021
Describe the bug
I won a block and then submitted off an older block even though I have committed to the younger blocks. From stacks-dump:
Expected behavior
Build off 666154
Additional context
From the log:
The text was updated successfully, but these errors were encountered: