bittrex seems not to want to display my usdt though ... that might be that bittrex would use the old system to determine usdt owners.. or whatever i dont care, for the real deal i will send the funds to a omnicore wallet :)

anyone who wants to see code of this bugfix, i will be reorganizing my inputs in https://github.com/evias/blockchain-cli will be renamed to a little stand alone omni-copay-recovery tool (and probably non-omni multisig recovery if i get time to work on it a little :)

arubi: I’m using terminology from Mastering Bitcoin…it’s the situation where two miners have won the block close to the same time and the network is split…some validating nodes beliving A won and some believing B won.

arubi: interesting…so the second (valid) block is ignored by the node that has accepted the first (valid) block from the standpoint of the chainstate…but it would be interesting to know whether the mempool is updated before and after the reorg…I wish I knew C better :)

Sentineo: So the first time the node gets winning block A it starts validating the block…and once it validates that block is the mempool affected at all (e.g. transactions in that block removed from the mempool)?

Sentineo: Does the order matter here? So when the node gets the next block in your example (1-2-3-A-C) and validates A and C, at the time of that validation it tries to remove transactions from the mempool and if there’s any overlap with B (that’s already been removed) it just moves on and doesn’t cause an error invalidation? And then when transactions from B go back into the mempool, if there’s overlap with A and C

Sentineo: Is the mempool altered after a node validates each block. That is, the node determines that all of the transactions in the block are valid + the other validation stuff and then removes all of the transactions that are in that block from the mempool?

Sentineo: 1-2-3-B has transactions that are in 1-2-3-A in the earlier example, B is validated first so there’s an attempt to remove all transactions in B from the mempool…now A is validated and it has tx that were previously removed from the mempool during B’s validation….during A’s validation the node is trying to remove a tx that is no longer in mempool (I realize I must be missing something here)…