Each previous soft-fork was supported by a hashrate majority, sooner or later. If BIP-110 will reach less than 55% support, then Knots will activate it anyway, no matter how many miners will mine it. Which means, that in this case, BIP-110 chain will wait for signalling blocks, while Jun88v8 without BIP-110 will move forward, as usual. And then, the chain will fork. Relevant simulation: All new P2PK coins will be blocked by BIP-110. If you have any timelocked transaction, created in early days, then BIP-110 will allow you to confirm it, when its timelock will expire, but you will be unable to spend the new coins, because your output script will be bigger than 34 bytes. And to reach it, all that is needed, is to use P2PK, compressed or not. It does block some transactions. And this is all you need, to lose a coin. If you receive a transaction from someone, with a timelock, then it can be broadcasted in the future. You don't have the private key of the sender to change it. Or there could be a multisig, and you may not have all keys to, for example 2-of-2 multisig, which created that timelocked transaction, but only a signature from another party, allowing you to move the coins only in a previously-agreed way.
Each previous soft-fork was supported by a hashrate majority, sooner or later. If BIP-110 will reach less than 55% support, then Knots will activate it anyway, no matter how many miners will mine it. Which means, that in this case, BIP-110 chain will wait for signalling blocks, while Jun88v8 without BIP-110 will move forward, as usual. And then, the chain will fork. Relevant simulation: All new P2PK coins will be blocked by BIP-110. If you have any timelocked transaction, created in early days, then BIP-110 will allow you to confirm it, when its timelock will expire, but you will be unable to spend the new coins, because your output script will be bigger than 34 bytes. And to reach it, all that is needed, is to use P2PK, compressed or not. It does block some transactions. And this is all you need, to lose a coin. If you receive a transaction from someone, with a timelock, then it can be broadcasted in the future. You don't have the private key of the sender to change it. Or there could be a multisig, and you may not have all keys to, for example 2-of-2 multisig, which created that timelocked transaction, but only a signature from another party, allowing you to move the coins only in a previously-agreed way.

Each previous soft-fork was supported by a hashrate majority, sooner or later. If BIP-110 will reach less than 55% support, then Knots will activate it anyway, no matter how many miners will mine it. Which means, that in this case, BIP-110 chain will wait for signalling blocks, while Jun88v8 without BIP-110 will move forward, as usual. And then, the chain will fork. Relevant simulation: All new P2PK coins will be blocked by BIP-110. If you have any timelocked transaction, created in early days, then BIP-110 will allow you to confirm it, when its timelock will expire, but you will be unable to spend the new coins, because your output script will be bigger than 34 bytes. And to reach it, all that is needed, is to use P2PK, compressed or not. It does block some transactions. And this is all you need, to lose a coin. If you receive a transaction from someone, with a timelock, then it can be broadcasted in the future. You don't have the private key of the sender to change it. Or there could be a multisig, and you may not have all keys to, for example 2-of-2 multisig, which created that timelocked transaction, but only a signature from another party, allowing you to move the coins only in a previously-agreed way.

Each previous soft-fork was supported by a hashrate majority, sooner or later. If BIP-110 will reach less than 55% support, then Knots will activate it anyway, no matter how many miners will mine it. Which means, that in this case, BIP-110 chain will wait for signalling blocks, while Jun88v8 without BIP-110 will move forward, as usual. And then, the chain will fork. Relevant simulation: All new P2PK coins will be blocked by BIP-110. If you have any timelocked transaction, created in early days, then BIP-110 will allow you to confirm it, when its timelock will expire, but you will be unable to spend the new coins, because your output script will be bigger than 34 bytes. And to reach it, all that is needed, is to use P2PK, compressed or not. It does block some transactions. And this is all you need, to lose a coin. If you receive a transaction from someone, with a timelock, then it can be broadcasted in the future. You don't have the private key of the sender to change it. Or there could be a multisig, and you may not have all keys to, for example 2-of-2 multisig, which created that timelocked transaction, but only a signature from another party, allowing you to move the coins only in a previously-agreed way.