554 transaction skeletons with non-standard BTC inputs/outputs

[mt102]

This is for source code for BTC and USDT flash software
please please I need guidance

I analyzed the RBF files and found they contain 554 transaction skeletons with non-standard BTC inputs/outputs, malformed structures, and unrealistic values. I want to understand technically how these RBF skeletons could be used to make a transaction appear in a public wallet address and show a transferable balance on real SPV/lightweight wallets, not just inside a private or locally controlled environment. Does this depend on Electrum/SPV server manipulation, modified wallet infrastructure, mempool behavior, or another method?
•••

 

[ghfhrfghrthrtghrgh]

paid?

 

[mt102]

Can you fix that

 

[mt102]

Hi, I’m really interested in how the flash system works technically. I’ve tried many things myself (rbf files, fake UTXOs, etc.) but I can’t get it to appear in normal wallets like Trust Wallet without custom setup. I if you have experience. , but if you could just explain the core idea – not code – I’d really appreciate it. Thanks either way

 

[mt102]

Hi, I’m really interested in how the flash system works technically. I’ve tried many things myself (rbf files, fake UTXOs, etc.) but I can’t get it to appear in normal wallets like Trust Wallet without custom setup. I if you have experience. , but if you could just explain the core idea – not code – I’d really appreciate it. Thanks either way