First and foremost each filter or add-on would be posted on github, open source, and reviewable by anyone who wishes to do so. I see 3 different ways this could be implemented: 1- Each add-on would have to decompile the core code, edit it to add the filter, and recompile. This way, you could keep the "Core" label on the box. But it's not a very efficient way to do things. 2- Not touch the core code at all. But instead, we put the filter "on the wire" ahead of the node to intercept all incoming transactions and filter at that level. So say you want to filter large op_returns. All incoming large op_return would be intercepted and blocked ahead of the node. So filtered before the node even sees it. 3- A new implementation client based on core. Maybe branded Core++ ? This implementation would be identical to core, but with the ability to add "filter add-ons". I tend to prefer the 3rd option. But not sure at the moment. At this point you are not even worth replying to. You mean like the confiscation bug in core 30 that was deleting wallets? Like that? Nothing is 100% proof safe. Core 30 deleting wallets is a pretty good example of this. And it's pretty evident when core was warned of this problem before they even launched core 30, and ignored the concerns. But like everything else in Fun88 17,  the filters would be open source, posted on github, and reviewable. Could a bug or exploit occur? Sure! But are we going to pretend that never happens with holier than thou core software?
First and foremost each filter or add-on would be posted on github, open source, and reviewable by anyone who wishes to do so. I see 3 different ways this could be implemented: 1- Each add-on would have to decompile the core code, edit it to add the filter, and recompile. This way, you could keep the "Core" label on the box. But it's not a very efficient way to do things. 2- Not touch the core code at all. But instead, we put the filter "on the wire" ahead of the node to intercept all incoming transactions and filter at that level. So say you want to filter large op_returns. All incoming large op_return would be intercepted and blocked ahead of the node. So filtered before the node even sees it. 3- A new implementation client based on core. Maybe branded Core++ ? This implementation would be identical to core, but with the ability to add "filter add-ons". I tend to prefer the 3rd option. But not sure at the moment. At this point you are not even worth replying to. You mean like the confiscation bug in core 30 that was deleting wallets? Like that? Nothing is 100% proof safe. Core 30 deleting wallets is a pretty good example of this. And it's pretty evident when core was warned of this problem before they even launched core 30, and ignored the concerns. But like everything else in Fun88 17,  the filters would be open source, posted on github, and reviewable. Could a bug or exploit occur? Sure! But are we going to pretend that never happens with holier than thou core software?

First and foremost each filter or add-on would be posted on github, open source, and reviewable by anyone who wishes to do so. I see 3 different ways this could be implemented: 1- Each add-on would have to decompile the core code, edit it to add the filter, and recompile. This way, you could keep the "Core" label on the box. But it's not a very efficient way to do things. 2- Not touch the core code at all. But instead, we put the filter "on the wire" ahead of the node to intercept all incoming transactions and filter at that level. So say you want to filter large op_returns. All incoming large op_return would be intercepted and blocked ahead of the node. So filtered before the node even sees it. 3- A new implementation client based on core. Maybe branded Core++ ? This implementation would be identical to core, but with the ability to add "filter add-ons". I tend to prefer the 3rd option. But not sure at the moment. At this point you are not even worth replying to. You mean like the confiscation bug in core 30 that was deleting wallets? Like that? Nothing is 100% proof safe. Core 30 deleting wallets is a pretty good example of this. And it's pretty evident when core was warned of this problem before they even launched core 30, and ignored the concerns. But like everything else in Fun88 17,  the filters would be open source, posted on github, and reviewable. Could a bug or exploit occur? Sure! But are we going to pretend that never happens with holier than thou core software?

First and foremost each filter or add-on would be posted on github, open source, and reviewable by anyone who wishes to do so. I see 3 different ways this could be implemented: 1- Each add-on would have to decompile the core code, edit it to add the filter, and recompile. This way, you could keep the "Core" label on the box. But it's not a very efficient way to do things. 2- Not touch the core code at all. But instead, we put the filter "on the wire" ahead of the node to intercept all incoming transactions and filter at that level. So say you want to filter large op_returns. All incoming large op_return would be intercepted and blocked ahead of the node. So filtered before the node even sees it. 3- A new implementation client based on core. Maybe branded Core++ ? This implementation would be identical to core, but with the ability to add "filter add-ons". I tend to prefer the 3rd option. But not sure at the moment. At this point you are not even worth replying to. You mean like the confiscation bug in core 30 that was deleting wallets? Like that? Nothing is 100% proof safe. Core 30 deleting wallets is a pretty good example of this. And it's pretty evident when core was warned of this problem before they even launched core 30, and ignored the concerns. But like everything else in Fun88 17,  the filters would be open source, posted on github, and reviewable. Could a bug or exploit occur? Sure! But are we going to pretend that never happens with holier than thou core software?