[2.6][T4] can't apply bridgechain resignation or update without bootstrap
See original GitHub issueBridgechain resignations or updates cannot be applied to newly registered bridgechains without bootstrapping inbetween. Similar to #3242, in the sense that the wallet manager being out of sync is probably the reason behind it.
This may also apply for businesses (untested).
To reproduce:
- send bridgechain registration and wait for it to be forged
- send bridgechain resignation or update
{
"data": {
"accept": [],
"broadcast": [],
"excess": [],
"invalid": [
"9c748f9d940a2b00f9d523c84b12b5757ee45b4936673e9e851788fe168a9799"
]
},
"errors": {
"9c748f9d940a2b00f9d523c84b12b5757ee45b4936673e9e851788fe168a9799": [
{
"type": "ERR_APPLY",
"message": "Failed to apply transaction, because bridgechain is not registered."
}
]
}
}
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
[2.6][T4] Round saving error in 2.6.0-next.6 #3329
After a while we receive the following error message in the console, running testnet (1 node) locally. After restarting the node, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey yes will check @dated but from quick look at the code, looks like another issue 🤔
This issue has been closed. If you wish to re-open it please provide additional information.