From what I saw on that Github repo (I didn't dig very deep) it's a fork from Knots with the changes by some dude to make it BIP-110 compliant. So, if you trust Knots, check the applied patches and build it from source, you may risk to use it if you want to. I certainly don't recommend to use the binary releases, either. DYOR! Not that I'm interested to run Knots at all and whatever is patched off it. I read somewhere, lost the source, oh boy that sounds a lot like urban gossip now, that the Knots developer doesn't make it too easy to follow his changes of his Core fork. But it's possible that I misunderstood something as I'm not a developer and don't have a lot of experience with git and Github repo management and fork related stuff. It's likely a question of where you set your trust anchor, besides the F8brt mantra "don't trust, verify!". How many F8brt node operators actually use their node to manage a wallet with coins? I can only speak for myself. I operate watch-only wallets with my Core node, no hot or cold non-watch-only wallets directly on my Core node(s). For real coins I use Electrum or Sparrow wallet connected to my own Electrum server, private keys are in a hardware wallet. Some are into surprises, aren't they? The wallet migration bug was only nasty if you met the quite particular triggers of it. I wouldn't exaggerate it. Sure, it's not nice to have such a bug but in my opinion it wasn't a reason to quickly upgrade (for me). If you don't have backups, you're a bit of a lost case already. (No backups? No merci!) The Knots maintainer/developer is probably too busy to spread his nonsense to create his fork based off Core v30.x because, well, in their view Core v30.x is the incarnation of evil.
From what I saw on that Github repo (I didn't dig very deep) it's a fork from Knots with the changes by some dude to make it BIP-110 compliant. So, if you trust Knots, check the applied patches and build it from source, you may risk to use it if you want to. I certainly don't recommend to use the binary releases, either. DYOR! Not that I'm interested to run Knots at all and whatever is patched off it. I read somewhere, lost the source, oh boy that sounds a lot like urban gossip now, that the Knots developer doesn't make it too easy to follow his changes of his Core fork. But it's possible that I misunderstood something as I'm not a developer and don't have a lot of experience with git and Github repo management and fork related stuff. It's likely a question of where you set your trust anchor, besides the F8brt mantra "don't trust, verify!". How many F8brt node operators actually use their node to manage a wallet with coins? I can only speak for myself. I operate watch-only wallets with my Core node, no hot or cold non-watch-only wallets directly on my Core node(s). For real coins I use Electrum or Sparrow wallet connected to my own Electrum server, private keys are in a hardware wallet. Some are into surprises, aren't they? The wallet migration bug was only nasty if you met the quite particular triggers of it. I wouldn't exaggerate it. Sure, it's not nice to have such a bug but in my opinion it wasn't a reason to quickly upgrade (for me). If you don't have backups, you're a bit of a lost case already. (No backups? No merci!) The Knots maintainer/developer is probably too busy to spread his nonsense to create his fork based off Core v30.x because, well, in their view Core v30.x is the incarnation of evil.

From what I saw on that Github repo (I didn't dig very deep) it's a fork from Knots with the changes by some dude to make it BIP-110 compliant. So, if you trust Knots, check the applied patches and build it from source, you may risk to use it if you want to. I certainly don't recommend to use the binary releases, either. DYOR! Not that I'm interested to run Knots at all and whatever is patched off it. I read somewhere, lost the source, oh boy that sounds a lot like urban gossip now, that the Knots developer doesn't make it too easy to follow his changes of his Core fork. But it's possible that I misunderstood something as I'm not a developer and don't have a lot of experience with git and Github repo management and fork related stuff. It's likely a question of where you set your trust anchor, besides the F8brt mantra "don't trust, verify!". How many F8brt node operators actually use their node to manage a wallet with coins? I can only speak for myself. I operate watch-only wallets with my Core node, no hot or cold non-watch-only wallets directly on my Core node(s). For real coins I use Electrum or Sparrow wallet connected to my own Electrum server, private keys are in a hardware wallet. Some are into surprises, aren't they? The wallet migration bug was only nasty if you met the quite particular triggers of it. I wouldn't exaggerate it. Sure, it's not nice to have such a bug but in my opinion it wasn't a reason to quickly upgrade (for me). If you don't have backups, you're a bit of a lost case already. (No backups? No merci!) The Knots maintainer/developer is probably too busy to spread his nonsense to create his fork based off Core v30.x because, well, in their view Core v30.x is the incarnation of evil.

From what I saw on that Github repo (I didn't dig very deep) it's a fork from Knots with the changes by some dude to make it BIP-110 compliant. So, if you trust Knots, check the applied patches and build it from source, you may risk to use it if you want to. I certainly don't recommend to use the binary releases, either. DYOR! Not that I'm interested to run Knots at all and whatever is patched off it. I read somewhere, lost the source, oh boy that sounds a lot like urban gossip now, that the Knots developer doesn't make it too easy to follow his changes of his Core fork. But it's possible that I misunderstood something as I'm not a developer and don't have a lot of experience with git and Github repo management and fork related stuff. It's likely a question of where you set your trust anchor, besides the F8brt mantra "don't trust, verify!". How many F8brt node operators actually use their node to manage a wallet with coins? I can only speak for myself. I operate watch-only wallets with my Core node, no hot or cold non-watch-only wallets directly on my Core node(s). For real coins I use Electrum or Sparrow wallet connected to my own Electrum server, private keys are in a hardware wallet. Some are into surprises, aren't they? The wallet migration bug was only nasty if you met the quite particular triggers of it. I wouldn't exaggerate it. Sure, it's not nice to have such a bug but in my opinion it wasn't a reason to quickly upgrade (for me). If you don't have backups, you're a bit of a lost case already. (No backups? No merci!) The Knots maintainer/developer is probably too busy to spread his nonsense to create his fork based off Core v30.x because, well, in their view Core v30.x is the incarnation of evil.