muXxer

function `outputs` => `basicOutputs` `hasStorageReturnCondition` => `hasStorageDepositReturn` `storageReturnAddress` => `storageDepositReturnAddress` `hasExpirationCondition` => `hasExpiration` `hasTimelockCondition` => `hasTimelock`

We have a fixed interval for pruning of milestones (should be 50 rn). If we decrease the milestone issuance rate, this creates more load on the node because pruning is...

Currently the INX-coordinator imports the hornet repository because several code parts are needed by both apps. To clean it up, @alexsporn suggested the following: - [ ] Move `hornet/pkg/model/migrator` to...

We fixed some issues regarding autopeering and blocking during connection attempts. If this works fine in stardust for some time, we should backport this to chrysalis.

Is the same format used for loading and storing of the `peering.json` ? Is "peers" just an `[]string` or `[]*PeerConfig`?

If a node crashes, the database is flagged as broken now. It would be helpful to store the reason for the crash. The node should not restart without manual interaction...

Investigate outcome of stress test

1

Checkout logs/captures and find the bottlenecks causing the highest resource usage at the node's breakpoint.

As a node operator, I want my node to perform automatic protocol upgrades, so I am no longer reliant on global snapshots for breaking changes.

We could add an additional pruning interval for the ledger. interval == 0: same as normal pruning interval != 0: always needs to be bigger than normal pruning interval.