ImplOfAnImpl
ImplOfAnImpl
Hi. I'm pretty new to Rust, so I may be missing something. But anyway :-) So, ffi/passing-strings has this example: ``` fn report_error(err: S) -> Result { unsafe { //...
Currently, end-to-end encryption is implemented on the ad hoc basis for RPC, e.g. in `BlockProductionInterface` the functions that accept sensitive data and which can be called via RPC (the "_e2e"...
`BlockProduction::produce_block_with_custom_id` now delegates to one of 3 separate functions, based on the passed input data and the required consensus - `produce_block_pos`/`produce_block_pow`/`produce_block_ignore_consensus`; each of the functions works with the specific type...
In #1708 some chainstate db consistency checks were implemented, which are focused on the consistency of block-index/block/block-id-by-height maps. We should have similar checks for other maps in the db.
- [ ] If the invalidation is too deep, we should give up adding transactions back into the mempool. - [ ] Invalidated blocks won't be deleted immediately. We'll need...
In https://github.com/mintlayer/mintlayer-core/pull/1550 outdated parts of the document were removed, so at least it is not misleading anymore. But it's still very incomplete (now even more so).
`Time` and `TimeGetter` are used frequently in p2p to represent/obtain some abstract point in time, whose only purpose is to be able to calculate a time difference later. The problem...
Currently when handling a block request we append the newly requested block ids to the queue of previously requested ones, which makes it impossible for the peer to "change its...
`BlockSyncManager`'s `Peer` tasks store requested block ids in `blocks_queue`. Then, on each iteration of the "main" loop, one of the ids is popped from the queue and the corresponding `BlockResponse`...
Right now we don't have such a limit, so the node will download the same block from all connected peers that have it. P.S. in bitcoin, the corresponding limit is...