[✔] Encontrado: PubAddress: 19vkiEajfh8asnMYgN8qfm1kM4Gk5AssNR
[✔] Encontrado: PubAddress: 19vkiEajfhmfv7LN32tQB8373k8P56ZdRX
I have these

Parece que consegui executar o wifhunter no win11, 5800x3d mostra a seguinte velocidade, é interessante comparar com outros processadores.
Código:

[2025-04-18 16:00:55] Inserção da varredura para prefixação para o prefixo: L5FNHG
[2025-04-18 16:00:55] WIF Hunter
[2025-04-18 16:00:55] CHECKING WIF PREFIX KwDiBf:
[2025-04-18 16:01:06] Progresso - 0.43 % [16,26 Mkeys/sec]
[2025-04-18 16:01:18] Progresso - 0,86 % [16,24 Mkeys/sec]
[2025-04-18 16:01:30] Progresso - 1,29 % [14,86 Mkeys/sec]
[2025-04-18 16:01:41] Progresso ? 1.72 % [15,50 Mkeys/sec]
[2025-04-18 16:01:53] Progresso ? 2.116 % [15.08 Mkeys/sec]
[2025-04-18 16:02:05] Progresso - 2.59 % [15,70 Mkeys/sec]
[2025-04-18 16:02:17] Progresso - 3,02 % [15,60 Mkeys/sec]
[2025-04-18 16:02:28] Progresso - 3,45 % [15,64 Mkeys/sec]
[2025-04-18 16:02:31] [W] KwDiBB89QggGbjEhKnhXJuH7LrZiZi3Yjgd9M7rFU73sVHnoWn
Encontrado combinando chave privada!
[2025-04-18 16:02:31] FOUND PRIVADO DE CHAVE!!!
[2025-04-18 16:02:31] Comprimido HASH160: 751e76e819899966494941c45d1b3a323f1433bd6
[2025-04-18 16:02:31] HASH160 descompactado: 91b24bf9f5252532960ac687abr
[2025-04-18 16:02:31] Chave privada (hex): 00000000000000000000000000000000000000000000000000000000000000000001
[2025-04-18 16:02:31] Chave privada (decimal): 1
[2025-04-18 16:02:31] Chave privada salva para C:?Users?hexap?Downloads?WIFHunter-mainr?reports?found_key.txt
[2025-04-18 16:02:31] Emissão escrita terminou


knife right away for puzzle 69 instead of 1

Guys, in my opinion I believe in the prefixes next and a half today I found 5 and they were very close

19vkiEajfh uZ8bs8Zu2jgmC6oqZbWqhxhG 69 /6.9 btc

19vkiEajfh 8asnMYgN8qfm1kM4Gk5AssNR

19vkiEajfh mfv7LN32tQB8373k8P56ZdRX


19vkiEaj uiCNKC6dVeXN15dpRnANF5rHch


19vkiEaj DnQKG83Eibm7TA97TkTNrY9uGQ

19vkiEaj HXf1kuKy1iFFVEp8stKzpA28SK

For me personally it might be fun... if it doesn't have any mathematical basis, but for me it might be cool.

olá a todos. eu errei sim em insistir em RBF DESATIVADO isso ja não e nenesario falar mais e so usar mara poool e ponto . esquecam meu scrypt TX raw vou usar para mim então em alguns novos experimentos de transferências otimizadas sem hotwallet.. ok eu sobre procurar a chave comecei no 66 dpeois 67 e agora 78 .. não tem atalhos modo aleatório e todo tipo de ebuscas otimizadas por pedaos e ao azar SORTE grande e dificil mesmo ja o certo e busca do inicio ao fim mas sem poder de placas de videos rtx 4080 nao e pocivel e sorte mesmo vou seguir tentando achar alguma chave tenho 3 super maquinas aqui mas nada ate hoje so conta d eluz carisimas heehe mulher quer me matar em casa ja klkk

What is Replace-by-Fee (RBF)?
Replace-by-Fee (RBF) is a feature that allows a user to replace a Bitcoin transaction that has not yet been confirmed by the network with another transaction that pays a higher fee. This can be helpful in case the original transaction was not included in the next block due to low fees, especially in times of network congestion.

When RBF is enabled, the sender can increase the fee and re-broadcast the transaction, increasing the chances of it being included in the next block by miners.

How RBF Works:
Transaction Broadcasting: A user broadcasts a transaction with a specified fee. If the transaction is not confirmed (due to low fees or network congestion), the user can replace the original transaction with one that has a higher fee.
RBF-Compatible Transactions: Transactions that are sent with RBF enabled are considered "RBF transactions". These transactions have a special flag in their structure that allows them to be replaced.
Why Replace a Transaction?: If a user sends a transaction with low fees and it’s stuck in the mempool (not confirmed), they can increase the fee to make the transaction more attractive to miners. Miners prioritize transactions with higher fees.
How to Create and Replace Transactions with RBF:
1. Creating a Transaction with RBF Enabled:
To send a transaction with RBF enabled, the wallet or software you are using must support RBF. Most modern Bitcoin wallets, including Bitcoin Core, allow you to enable or disable RBF when creating transactions.

Steps in Bitcoin Core (GUI):
Open Bitcoin Core and go to the Send tab.
Select the address to send the Bitcoin to and enter the amount.
If RBF is available, you can check a box or select an option to enable Replace-by-Fee. This flag ensures that the transaction can be replaced with a higher fee later.
Sign and broadcast the transaction.
Steps in Bitcoin Core (Command Line):
You can also use Bitcoin Core’s command-line interface to create an RBF-enabled transaction.

bash
Copy
bitcoin-cli createrawtransaction '[{"txid":"previous_txid","vout":0}]' '{"recipient_address":amount}'
To enable RBF, you can use the following command:

bash
Copy
bitcoin-cli sendtoaddress "recipient_address" amount "" "" true
Here, the true value at the end enables RBF for this transaction.

2. Replacing a Transaction:
If the transaction you sent was not confirmed due to low fees, you can replace it with a new transaction that has a higher fee. This is where RBF comes into play.

Steps to Replace a Transaction:
Identify the transaction: You need the Transaction ID (TXID) of the original transaction that is stuck.
Create a new transaction: Use the same inputs (unspent transaction outputs, UTXOs) as the original transaction, but increase the fee.
Rebroadcast the transaction: Once the new transaction is created and signed, rebroadcast it to the network. Since it has a higher fee, it will be more attractive to miners and is likely to be confirmed faster.
3. Using Bitcoin Core Command Line to Replace:
You can use the following command to replace a transaction using RBF:

bash
Copy
bitcoin-cli walletcreatefundedpsbt '[{"txid":"previous_txid","vout":0}]' '{"recipient_address":amount}' 0 false
The false option ensures that RBF is not enabled. You can set true if you want to enable RBF during the creation of this transaction.
After creating the transaction, sign and broadcast it to the Bitcoin network.
4. How to Replace an Unconfirmed Transaction:
If you are using a wallet that supports RBF, you can also replace a transaction using the wallet’s interface or an API. Some wallets will automatically allow you to increase the fee of an unconfirmed transaction directly from their UI (like Electrum).

What Happens if the Transaction Doesn't Support RBF?
If a transaction is not RBF-enabled, it cannot be replaced once broadcast to the network. The transaction is considered final once it's broadcast, and the only option is to wait for it to be confirmed or rejected by the network.

Non-RBF transactions cannot be modified or replaced.
Once a non-RBF transaction is broadcast, it is essentially locked in place, and only the miners can choose whether or not to include it in a block.
How to Check if a Transaction Supports RBF?
You can check if a transaction is replaceable by looking at the raw transaction data or by querying the Bitcoin node or blockchain explorer.

In Bitcoin Core: You can use the command getrawtransaction to check whether the transaction supports RBF. If the transaction contains the "replaceable" flag, it is replaceable.
bash
Copy
bitcoin-cli getrawtransaction "TXID" 1
Blockchain Explorer: Many blockchain explorers show whether a transaction is RBF-enabled. You can check the status of the transaction by entering its TXID into the explorer.
Example Scenario:
Let’s say you send a transaction with a low fee and it doesn't get confirmed after several blocks. In this case:

You check the status of your transaction using a blockchain explorer.
If the transaction is still in the mempool (unconfirmed), you can create a new transaction that replaces the original transaction with a higher fee (thanks to RBF).
You broadcast the new transaction, and since it pays a higher fee, miners are more likely to confirm it.
Why Use Replace-by-Fee?
Speed Up Transaction Confirmation: If your transaction is stuck due to low fees, RBF allows you to increase the fee and get it confirmed faster.
Network Congestion: In times of high network traffic, RBF gives you a way to "boost" your transaction's priority by increasing the fee, ensuring it doesn’t stay stuck.
Avoid Stuck Transactions: For users who want more control over their transaction's confirmation, RBF provides the flexibility to adjust the fees dynamically.
Summary:
RBF (Replace-by-Fee) allows you to replace an unconfirmed transaction with a higher-fee transaction.
Enable RBF during the creation of a transaction in compatible wallets like Bitcoin Core.
Replace transactions with higher fees if they are stuck in the mempool.
Non-RBF transactions cannot be replaced once broadcast to the network.
Check if a transaction supports RBF using raw transaction data or a blockchain explorer.
RBF provides flexibility for users to manage their transactions and avoid delays caused by network congestion.
Your choice for enable or not RBf in tx ended
Each n every tx you send to mempool, by default set RBf enabled at minners (mempool)
Read Bitcoin core current rules

That's what I did, I created a lock with rbf completely disabled and it's not pocibel boot or anything superimposed I said that and everyone here laughed in my face and told me to prove it.. why prove it if I already knew.. lol

There's a lot of shit on this forum, no one knows anything.

Soon I will prove to you the tx efficient method

I see that the 135 is all the same, the creator already has the private keys, I'm waiting for someone unhappy who found it and when he removed the 135 he replaced it immediately with rbf, stealing it for himself again, what do you think? Why, for example, if 2 pesos have the key, the original for protection must have a scrypt monitoring the withdrawals to override rbf then to troll the winner, just like in 66?

ok

okay I'm going to do a tx today 67 bit ok by menpool I want to see if someone can steal from me, maybe I'll leave the rate low.

Do you think that I did that test manually?

No, it was done with a script without use of any external wallet, TX was crafted from zero and broadcasted with API


Also, perform it manually and transmit the transaction manually, using a basic approach. You can also use my API for this purpose.


You might see something wrong, so let's do tests, you and I in private, if you want to share this, I'll also show you what I did, but we'll talk in private and I don't want to spread free isos.

Rpoint: 04427ec0a0301863225561cbbb011a6692de3e4400631d07a1356f11926eff0c77e31f0022894d9 b6fdea00a252d803ef06bf9238b74e1eb7537e87a60c7684558
r : 427ec0a0301863225561cbbb011a6692de3e4400631d07a1356f11926eff0c77
s : 37a4186d424cb9a8e58ffff2ca30fb58b878d9876583efef4c99b9d137752d2d
z : 66c9d17af97088340e7894865731ad6e37642ab797ce58ecc650f351f5349f6
PubKey : 032145f843d3c91c3795a75da5ea46796070d18de51a7d0c0b68eb2f30162b169f
Address : 1BY8GQbBPGYEC58s9ckHmqf9doEX9mCKPR

signature is Valid and Address is Verified.

correct and very easy to get the public key of a signature very well..

Talvez ele esteja falando sobre definir o campo de sequência para o valor máximo ao fazer a primeira transação para finalizá-la e impedir quaisquer atualizações futuras.



In the end, an optimistic and intelligent guy and that's pretty much it, but I managed to get something even better

Okay, I respect your knowledge, but I created a third option that I use to handle my friends' transactions, and that's it. I’ve spent enough time testing it and even offered you the chance to test it as well, but that's okay. I’ll take my leave now. Hugs!

It's funny, my friend. I'm just choosing to sell, and no, it wasn't created in ChatGPT, lol. That's for beginners. I'm not speaking ill of anyone, but all you do is criticize. Yes, I created my own method for withdrawals—it's immune to RBF and surcharges. That's it, my friend, nothing more. It's nothing like those fantasies you keep talking about

Of course, what prevents me from selling a script that I created, which has the correct functions for safe transfers without being stolen?

If I want to sell it, I won't give it away for free. I’m not foolish enough to hand over the ‘knife and the cheese’ to someone so they can benefit from it without my compensation. I’ve already tested it multiple times. Even

military-grade security measures haven’t succeeded in interfering with my transfers, which range from 66 to 100 bits—all tested and functioning perfectly."

ok

I'm going to sell it for 1 BTC whoever wants to talk to me I'm grateful thank you I'm not going to say anything more who wants to take a shot in the dark or use mara feel free, you tested with random wallets and of course you'll hide the pk but inside mara there are people who are monitoring This address 67 even has a proxy and other methods that will allow hackers to get the pk anyway, luck to you who will use it, big hugs..

message   15/01/2025 hotmoney


address    1BY8GQbBPGYEC58s9ckHmqf9doEX9mCKPR


signature   H0J+wKAwGGMiVWHLuwEaZpLePkQAYx0HoTVvEZJu/wx3N6QYbUJMuajlj//yyjD7WLh42Ydlg+/vTJm50Td1LS0=

WanderingPhilosopher, look, I don’t trust Marapool. Either they or someone there might have bad intentions. I don’t want any fees, I won’t charge 3 BTC or anything like that, but feel free to try. I also have bills to pay, and energy is expensive here. I know there’s an easy tutorial with Marapool, but it usually doesn’t work, and it says it's offline. So I don’t trust it; I’ve tried it before, and it took a long time. I prefer to do it my way—nothing works better.

As for RBF, there’s a lot of FOMO (fear of missing out) and fear involved. It’s not easy to steal from someone if the parameters are set correctly.

I discovered last month the correct way to transfer without being robbed, without RBF. The method I use to transfer funds from wallets with 66 to 70 bits—I tested everything, especially 67—works with the method I created, without Marapool or Electrum. And it works. I even tried to steal from myself, and I had friends with powerful cards try as well. I made the transfer, and 10 friends tried to steal from me, but it didn’t work. Even I tried to do an RBF, but it doesn’t replace the transaction, no matter how high I set the fee.

I found the flaw that allows thieves to steal, and if you use my method, it prevents this. If anyone wants to test with me, just let me know—I’m available. Forget Marapool and forget mining your own blocks. This is the only way I’ve managed to make it work.