corda.ledger.utxo

Configuration schema for the UTXO ledger.
tokens
- Settings for token selectionfullSyncBlockSize
- The number of records per synchronization message during a full token cache synchronization.
Minimum value: 100
Default value: 1000minDelayBeforeNextFullSync
- The minimum amount of time Corda waits before starting another full token cache synchronization, in seconds.
Default value: 300minDelayBeforeNextPeriodicSync
- The minimum amount of time Corda waits before starting another periodic cache synchronization, in seconds.
Default value: 30periodCheckBlockSize
- The number of state references per synchronization message during a periodic token cache synchronization check.
Minimum value: 100
Default value: 5000sendWakeUpMaxRetryAttempts
- The maximum number of attempts to send the synchronization wake-up messages on component start.
Default value: 6sendWakeUpMaxRetryDelay
- The maximum delay before a retry is scheduled, in seconds
Minimum value: 1
Default value: 10
Was this page helpful?
Thanks for your feedback!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.
We're sorry this page wasn't helpful. Let us know how we can make it better!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Create an issue
Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.