...
[DAO-1666] [Core Chain] LeetSoft Solutions, LLC - Apr 2023 Payment (Liquid FIO)
Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | FIO-29 |
---|
|
Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | FIO-70 |
---|
|
Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | FIO-125 |
---|
|
Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | FIO-207 |
---|
|
Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | FIO-121 |
---|
|
FIO-249: [Core Infrastructure] August 2023 - LeetSoft Solutions, LLC
Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | FIO-313 |
---|
|
Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | FIO-376 |
---|
|
Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | FIO-274 |
---|
|
Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | FIO-431 |
---|
|
Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | FIO-471 |
---|
|
Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | FIO-472 |
---|
|
Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | FIO-505 |
---|
|
Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | FIO-539 |
---|
|
Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | FIO-586 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | FIO-635 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | FIO-699 |
---|
|
FIO mSig Acct Payment Requests
Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | FIO-482 |
---|
|
Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | FIO-587 |
---|
|
...
V1 History config:
https://developers.fioprotocol.io/docs/chain/node-build-history
warning Without the history-index-state-db-size-mb and history-state-db-size-mb settings nodes may stop with the warning: Database has reached an unsafe level of usage, shutting down to avoid corrupting the database. Please increase the value set for chain-state-db-size-mb and restart the process!
Dirty Flag Issue:
Ye olde folder deletion problem where you have to manually delete some folders when doing a replay
Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | BD-1953 |
---|
|
To solve this you have to delete the history and history-state folders if you are not running v1 histor
[Ross/EOSphere} Restart with a snapshot from here and check the nodeos usage example at the bottom.https://snapshots.eosphere.io. Also delete the two history folders in the nodeos binary directory you started from.
Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | BD-1953 |
---|
|
...