-snip- I find it hard to believe that someone was mining Bitcoin that early on in its existence but is struggling to understand how to work the private keys and can't point out his address. But exceptions do occur.
It was too easy for newbies actually, just have to download " Bitcoin" which was exclusively for Windows, then tick " Option->Generate Coins" and pooof... it's mining. If his " friend" is honest that it's not bought, then I think they accidentally made a fork back then and mined a block in their own blockchain. How do it with new computer, which files do I need to move to new computer?
Copy the wallet.dat from bitcoin's data directory ( en.bitcoin.it/wiki/Data_directory#Default_Location) Paste it to the new PC's " wallets" folder inside bitcoin data directory, rename the wallet file or put it inside a folder with your preferred wallet name then Open Bitcoin Core and load using the menu: " File->Open Wallet". You don't have to put it to a fully synced Bitcoin Core since it's only @4111 which is a few ( nearly)empty blocks away from the genesis block. After getting past that height/block timestamp, you can immediately see in the transactions tab if your generated bitcoin is verified ( with check) or invalid ( with questionmark) Spoiler: hover-over your mouse pointer |
|
|
|
( I've received your PM) You should do their suggestion to verify the result ( so that you can use it against them) but I'm not familiar with PHP, you should ask someone who is familiar with PHP and run their " fairness" code from here: cryptoplay.io/help/fairness#KenoAnd verify Bet ID 11320148's result ( you should provide the rolled numbers of that keno bet). If it matched, then that BetID's revealed server seed hash was really the value used by the casino, not the previously presented different server seed hash which is different. And that's not provably fair since they've initially presented you a different hash for the same BetID. Given the one-way nature of hashing functions, there shouldn't be any other server seed that will produce the same hash. If it didn't match, you should ask the casino to present the 'server seed' that results with fc86f14b39cb68ef55a9c0f8133494fa5f340a1b17b5af0d285af6247507815aThen perform the fairness code again using that seed if it matches with the result. If the above matched, then the previously revealed server seed/hash may be a display bug. Note: For verification of the server seed hash, they seem to have used SHA256 to produce the 'server seed hash' but input the 'server seed' as " text" not " hex". e.g.: - "Revealed server seed" as text: 93bb49d435b86645490de1d51c634d2889d6f0c094897e3e46905d51d8baba51 -> 4d15ef41be8c0d1ac427924e71bd249d5c44587d95262b54fa3127a6321c1203
- "Revealed server seed" as hex: 93bb49d435b86645490de1d51c634d2889d6f0c094897e3e46905d51d8baba51 -> 8cebea681b8c01de1063c82b1f1f65bd5bc01ad76b5c91dc860801ffa8af76e8
|
|
|
|
|
Take note that you might get false-negative result in Electrum because coinbase outputs at that time are P2PK by default, unless mined using other software.
Means that Electrum might see zero transaction despite having a valid transaction;
if you want 100% accurate result, you need to at least sync Bitcoin Core for a few minutes or until it reached beyond that block's height.
However, taking all the available info in consideration, your 50BTC may just be from an orphaned block (not in the blockchain).
|
|
|
|
Here's how to export your privKey: Select ( highlight) your wallet->Click " Wallet Properties" on the left. Then find your address from the drop-down menus at the left, look in " Unused Addresses->P2PKH" first then " Used Addresses" if it's not there. If you found your address, double-click on it and Click " View Address Keys"; type your passphrase and the private key ( Base58) will be displayed. Remove the spaces when importing it to Electrum. Alternatively, here's an old post by HCP with the instructions to export your private keys: http://bitcointalk.org/index.php?topic=4746784.msg43255691#msg43255691 |
|
|
|
-snip- Every item under the `txs` list has inputs and outputs, and that's about the point where I'm stuck right now.
How do I figure out whether this is a "spend" or "receive" transaction in relation to a given xpub and what is the associated address?
Let's use this result as an example: "txs":[
{
"hash":"0202b8ba785d8befdbbeca1641a981d371ddfc2f5216a2d1fd78de7e8e460478",
"ver":2,
"vin_sz":2,
"vout_sz":1,
"size":335,
"weight":1340,
"fee":820,
"relayed_by":"0.0.0.0",
"lock_time":640369,
"tx_index":4222712286272463,
"double_spend":false,
"time":1595650444,
"block_index":640678,
"block_height":640678,
"inputs":[
.
.
.
],
"out":[
.
.
.
],
"result":-1820,
"balance":546
}, Below each transaction, there should be a " result" and " balance", If the result is a negative value, that means that it's a " spend" transaction, " receive" if positive. The associated address(es) are the " addr" in the " inputs" if it's a spend txn, in the " out" if it's a receive txn. |
|
|
|
Based on Electrum's github page[1] and this forum[2], it looks you're first human experiencing this error.
The issue in the first link: MemoryError: #7501 is the result of user(s) who submitted crash reports when experienced the same error; so far, there are four who submitted ( 3 users, maybe) and probably more who didn't send a crash report. @Gryndal Have you tried the famous " turn it off and on again"? ( your PC) |
|
|
|
|
Another option is to freeze all of your other addresses by right-click menu "Freeze" on an address in the Addresses tab.
Frozen address will be highlighted and their balance wont be available for spend.
You may also have to disable the use of 'change address' so your change wont be sent to another address every time you send them funds.
Disable it in: "Tools->Preference->'Transactions' tab->Use change addresses"
Also, it's useful to enable "Advanced preview" (in the same settings tab) so you can review the input(s) when sending funds,
It will add extra steps (Finalize->Sign->Broadcast) but you will be able to see which address is being used as input.
|
|
|
|
Bitcoin Core shouldn't launch with that parameter since it's below the minimum size, are you sure that you're using the correct shortcut? I checked, and it doesn't just ignore the setting: Error: Prune configured below the minimum of 550 MiB. Please use a higher number. On Linux, this works just as expected: bitcoin-qt -datadir=/tmp/bitcoin -prune=550 I'm not a Windows user, so I can't really tell you what goes wrong. It's not because of the OS but the size set in prune setting. In Linux you set 550MiB which is the minimum, in the first reply, it's only 500MiB which is below the minimum. |
|
|
|
-snip-
I added -prune=500, restarted Bitcoin Core, and I’ve been waiting to see what happens. It fluctuates, but I’ve lost about 4Gb of storage, so it doesn’t appear to be working. So far it’s taking about 20Gb of storage. Bitcoin Core shouldn't launch with that parameter since it's below the minimum size, are you sure that you're using the correct shortcut? At least set it to the minimum which is what you've originally set in your bitcoin.conf file. BTW, it's already in effect if it says -prune=n under "Options set in this dialogue are overridden by the command line or in the configuration file:" |
|
|
|
-snip-But i just recently came across a post where a high rank user of this forum corrected a member that satoshi is not the owner of this forum. Satoshi does not own bitcoin.org, it belongs to Cobra.
I am curious and want to really know who owns the forum and its relationship to bitcoin in other for me not to mislead the public with wrong information if i happen to be ask any where. The Bitcoin forum and website are different: Bitcointalk.org is the forum, Bitcoin.org is the website for the coin/network: Bitcoin; and additionally, Bitcoincore.org is the website for the reference client: Bitcoin Core. satoshi is inactive so he can't maintain the forum nor bitcoin.org. If you're looking for the current owner of bitcointalk.org, look for the " admin" position. ( how to) Related post: Domain name update |
|
|
|
I only hold private Key not seed key. I've tried the method above but it keeps failing, I don't know where the error is but after I repeat it it's still the same..
So understand because this is the first time for me.
What does the error say? Is your WIF private key uncompressed? I mean, does it start with 5? If so and you've imported it to Bitamp before then used either the " SegWit Compatible" or " SegWit Native" address, it's automatically converted into WIF compressed. You can get the compressed WIF private key in Bitamp's key icon near the address or in the account tab. Also, take note that Bitamp's code s pretty much abandoned since the last update was two years ago: github.com/bitampcom/bitamp |
|
|
|
After that, I restored my wallet with seed phrase, but there is a problem: I had almost 500 addresses and only half of it restored. The last history of transaction is in December, but I’ve been using this wallet until 11th October. Your other funds could be in your change address at higher index.
Just tried it. Even to 2000, nothing changes with the balance. Hmm, I can only guess that you had two wallets, one is your default_wallet and another, either one has 2018~Dec2021 txns and one with the latest. Since you have about 500 addresses, it'll be hard to monitor if you're actually using the one from 2018. Is there any chance that you've created another wallet with the same seed phrase but with " extended words"? In case, restore another wallet but enable the option " Extend this seed with custom words". Or different seed phrase? |
|
|
|
Your other funds could be in your change address at higher index. Try to manually generate change addresses with, open console: [wallet.create_new_address(True) for i in range(600)] |
|
|
|
How much address on 1 master private key?. is master private key can sign a transaction or sign a message?
-snip-
As much as your wallet can handle and yes, you can sign a message using its child prv keys as long as the client supports signing message to a specific address type. ( Bitcoin Core can't, as of now) But the wallet should have taproot descriptor support to be able to import it. As of now, I can't find any that supports importation of taproot descriptor ( or even other descriptors). |
|
|
|
What I mean by this is that, instead of needing to download the whole blockchain before you can enable the pruned node, that you download and delete blocks as you go.
-snip-
Would it be possible to establish an option that sets a safe amount of blocks and keep this threshold of blocks and download and delete as you go?
I didn't get the question, quite. But " prune block storage to n MiB" is working similar to this, your node doesn't have to download the whole blockchain before you can enable pruning. You can start Bitcoin Core with clean datadir with prune setting enabled and it will download and delete the older blocks after reaching the set size. Or do you mean: A way to skip the older blocks and just download the " threshold" ( latest blocks)? If so; go to this issue and read its comments: github.com/bitcoin/bitcoin/issues/15605 |
|
|
|
If you have a older wallet which had mining capability and has generated coins on the old 6667 network which was P2P ..and its seen in the balance of the old core client.... how would you be able to move them over to the current 8333 network?
Are you talking about old generated coin but the client have no connection? Your generated coins are included to the block that you've mined so if it's broadcasted at that time, your old mined block should've been in the blockchain by now. You wont be needing anything but your wallet.dat file, create a backup, a copy and load that copy to the latest version of bitcoin core. Or is it about mining today using the old client but somehow forced a connection? If you're connected to your own Network: It will try to build on top of the latest block that it has; if successful, you'll see a pending balance but it's invalid to the Bitcoin network. If you're connected to the Bitcoin Network: It will try to mine but wont be successful due to the current difficulty. BTW, the latest client also has cpu mining capability in the form of generate ( cli) or generatetoaddress ( it's intended for RegTest). It will work in the mainnet but as you can expect, its mining wont be successful. [ set a very high "maxtries" for longer mining and see your CPU process (1-core) utilization ramp up] |
|
|
|
That's just a note to mention which wallet is selected in the drop-down menu above it.
So it's sort of a bug or anti-feature in the case of non-wallet commands. I think it's a way to show that the command executed in the console is equivalent to bitcoin-cli with --rpc-wallet arg. Because in bitcoin-cli, you can also add rpc-wallet regardless if the command is a wallet rpc or not. |
|
|
|
There was no malware,hacker or bug involved which i am glad it was not! Just the wrong 12 word seed phrase.
How about the other issue that your deposited coins moved? Was the answer to DireWolfM's question below a mistranslation or? 1. Are the coins that you sent still in the the address where you sent them, or have they moved? When looking at the blockchain the coins moved to another wallet.
1.No,the coins went first to the address that i wanted,but then they moved. |
|
|
|
|
Show Posts
