Quote from: JeromeTash on January 17, 2025, 08:48:55 PM

Quote from: ABCbits on January 17, 2025, 09:19:21 AM

--snip--

Like you suspected. I think this user is posting with the help of some chatbot of sorts

Even after members advised the OP of the thread that the reason his affiliate earnings were blocked were due to him having his cousin as a members just like he admitted but then came beato2025 with the usual ChatGPT-ish response Sad

He probably thinks he will farm his account this way or earn some merits.

Quote from: beato2025 on January 17, 2025, 03:32:38 PM

--snip--

Looks like moderator agree with us and immediately nuke him.

User: DigitalDollars

Additional information (optional):
* I suspect this user use chatbot.

List of post:

Quote from: DigitalDollars on January 17, 2025, 04:08:04 PM

I'm suggesting that _you can try brute-forcing the missing word in your Phantom wallet's mnemonic seed phrase using a tool like BTCrecover_. Since the wallet is BIP39 compatible, the last word of the mnemonic recovery words embeds a checksum, which limits the number of possible solutions. By using BTCrecover and providing an address associated with the wallet, you may be able to recover the missing word and regain access to your wallet. Additionally, _learning about derivation paths and HD wallets_ can help you better understand the recovery process and increase your chances of success.

This post is just rephrasing or plagiarize earlier post by other member.

Quote from: Cricktor on January 09, 2025, 03:47:57 AM

As Phantom wallet, I never used it, appears to be BIP39 compatible, it should be no big deal to brute-force the missing word in between your known sequence of 11 words.

The last word of mnemonic recovery words according to BIP39 standard, embeds a checksum. When you say, some word in between is missing and the missing word position is unknown, there should be a rather limited amount of possible solutions.

I haven't done this for other coins than Bitcoin, but I assume it should be possible to brute-force the missing word with BTCrecover which can also handle Solana. If you know an address of your wallet, the better!

See here: https://btcrecover.readthedocs.io/en/latest/

You may need to make yourself familiar with the tool. If you know nothing about derivation path and HD wallets, then maybe learn about it at https://learnmeabitcoin.com. You can learn such wallet basics with no issue in the context of Bitcoin, even when your wallet was one with Solana.

I would also recommend to prepare a test case. Create a 12-word BIP39 recovery backup e.g. with iancoleman script. Get an address of that wallet (iancoleman script doesn't support Solana, take some coin that BTCrecover and iancoleman support). Choose a word in between to be the missing one, but you know the solution.

Check if you can recover this word and verify it with the known solution. If you fail with this test case, you likely won't succeed with your real case.

Quote from: DigitalDollars on January 17, 2025, 03:53:39 PM

Don't worry, I'm here to help!

It sounds like you're trying to run a Bitcoin full node on your Windows 10 machine, which is great! However, you're encountering an error that's preventing the node from syncing completely.

The error message "Error reading from database, shutting down" suggests that there's an issue with the node's database, which is stored on your 1TB HDD.

Here are some potential solutions to help you resolve the issue:

1. *Check disk space*: Ensure that you have enough free disk space on your 1TB HDD. The Bitcoin node requires a significant amount of space to store the blockchain data. You can check the available disk space by right-clicking on the drive in File Explorer and selecting "Properties."
2. *Verify database integrity*: You can try verifying the database integrity by running the following command in the Bitcoin Core console (you can access this by clicking on "Help" > "Debug window" > "Console" in the Bitcoin Core GUI):
```
bitcoin-cli verifychain
```
This command will check the blockchain data for any inconsistencies.
1. *Reindex the blockchain*: If the above command doesn't help, you can try reindexing the blockchain. This will rebuild the database from scratch. To do this, close the Bitcoin Core GUI, then navigate to the Bitcoin data directory (usually `C:\Users\<YourUsername>\AppData\Roaming\Bitcoin`) and delete the `chainstate` and `blocks` folders. Then, restart the Bitcoin Core GUI and let it reindex the blockchain.
2. *Check for disk errors*: It's possible that there are disk errors on your 1TB HDD that are causing the issue. You can run a disk check using the built-in Windows tool:
- Open Command Prompt as an administrator (right-click on the Start button and select "Command Prompt (Admin)").
- Type the following command and press Enter:
```
chkdsk D: /f /r /x
```
Replace `D:` with the drive letter of your 1TB HDD.
1. *Consider upgrading your hardware*: While your machine's specs are decent, the Bitcoin node can be resource-intensive. If you're experiencing frequent errors or slow syncing, it might be worth considering upgrading your hardware, especially the storage drive.

Before attempting any of these solutions, make sure you've backed up your wallet (if you have one) and any important data on your machine.

If none of these solutions work, you can try seeking help from the Bitcoin Core community or a Windows expert for further assistance.

Keep in mind that running a full node can be a complex process, and it's great that you're taking the time to troubleshoot the issue. Good luck, and I hope you get your node up and running smoothly!

1.

Code:

bitcoin-cli verifychain

is invalid command if you try to run it inside Bitcoin Core GUI console.
2. There's no need to consider upgrade the computer hardware. Slow hardware alone wouldn't cause the error message.

User: hdtqisg

Additional information (optional):
* I suspect this user use chatbot.

List of post:

Quote from: hdtqisg on Today at 03:00:27 AM

If you still can't solve the problem, I have a way for you to try:
Because your transaction fee is too small, you use your Private key to sign a new transaction with a fee equal to or slightly larger than the current bitcoin fee and push the transaction through an intermediary website such as: https://coinb.in/#broadcast
You can learn more at the above website.

User @nc50lc explain what's wrong with this post.

Quote from: nc50lc on Today at 03:43:25 AM

Quote from: hdtqisg

Because your transaction fee is too small, you use your Private key to sign a new transaction with a fee equal to or slightly larger than the current bitcoin fee and push the transaction through an intermediary website such as: https://coinb.in/#broadcast
You can learn more at the above website.

This wont solve anything since the issue isn't about broadcast,
It's the actual process of creating a replacement in Bitcoin Core (if he's the sender) or CPFP (if he's the receiver), specify the steps if you want to help.
And there's no point in using another service to broadcast it, he can use his node.

If at the start, he informed that he's also the sender and using Bitcoin Core, the process would've been as simple as:
1. "sendrawtransaction", then 2. "bumpfee" within Bitcoin Core.

Quote from: hdtqisg on Today at 03:00:27 AM

If you still can't solve the problem, I have a way for you to try:

OP replied and with it, he confirmed the assumptions that he created the RBF transaction I saw early. (he mistakenly though it was CPFP)

The issue is already solved.

Quote from: hdtqisg on January 15, 2025, 11:42:52 PM

Solo mining with Bitcoin Core in 2025 is more of an experience than a job, in my opinion it is really difficult. but who knows, with hard work and a little luck, you may have your own reward. Good luck!
You should refer to other information on this forum before doing it.

This reply created on thread asking on how to perform solo mining with Bitcoin Core, but doesn't give any helpful information.

Source: https://ninjastic.space/post/64954408

The actual issue is using wrong parameter.

Quote from: nc50lc on January 14, 2025, 11:07:24 AM

Quote from: cryptobabi on January 14, 2025, 08:03:10 AM

but when run btcrecover.py there only comes out two combinations ee and tt, and that does not align with what is said in the document. the right output is eett ee tt ttee

Quote from: cryptobabi on January 14, 2025, 10:03:50 AM

python btcrecover.py --listpass --passwordlist token.txt

That's the issue, you're using --passwordlist instead of --tokenlist.
The former will take each line as the complete possible password while the latter generates a number of possible combinations of each line.

Help command results for reference:

Code:

--tokenlist FILE the list of tokens/partial passwords (required)
--passwordlist [FILE] instead of using a tokenlist, read complete passwords (exactly one per line) from this file or from stdin