mintlayer-core
mintlayer-core copied to clipboard
mintlayer
Mintlayer Core: The central repository housing the essential components to operate a Mintlayer node. It encompasses the node and wallet functionalities necessary for seamless operation, alongside an a...
Introduces new `TxOutput::AnyoneCanTake` which essentially represents a buy/sell order. This output creates an account with respective balances which can be filled by anyone partially/fully or withdrawn by an authority specified...
These types hold information about the block and transaction being verified. The verification procedure interfaces with the context types rather than inspecting block / transaction directly. Not quite happy with...
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"...
- [x] Sign a message to prove ownership of pool (#1521) - [x] submit transaction command does not add the tx to the wallet - [x] connect from wallet CLI...
There are many situations where verification logic is done in separate sections. For example, the Transfer output type is a set, while LockThenTransfer is a superset, with the same requirements,...
This PR contains types required for the implementation of the following atomic swaps algorithm. Most of the business logic will be handled by the wallet (which will be done in...
`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...
Currently if a block contains delegations to the pool that is used for generating current block all new coins/delegations will be considered for the reward distribution.