To import your wallet.dat into Bitcoin Core, you'll need to copy it into the data directory, see https://en.bitcoin.it/wiki/Data_directory. And yes, that is completely normal (the format of the wallet file is binary, with ASCII field names). |
|
|
|
|
According to your post history, it looks like you have tried to steal those seeds from the users via a phishing site.
Is this true?
|
|
|
|
|
It might be an altcoin wallet.
I didn't find that TXID on any of the common altcoin chains, though.
|
|
|
|
|
Seems like your blockchain is corrupted.
MAKE A BACKUP OF YOUR WALLET.DAT FIRST!
After backing your wallet up, go to %APPDATA%\Bitcoin and remove everything except wallet.dat.
Start your client again.
You'll also need to sync the blockchain again.
|
|
|
|
|
No, I mean - how does that whole file look like?
(please remove the payload data, of course)
|
|
|
|
|
How does the whole JSON file look like with all the confidential data removed?
|
|
|
|
|
It may be a change address.
Do you still have your balance on the wallet you sent from (wallet, not an address)?
|
|
|
|
|
Do you still have that old multisig wallet?
Which wallet program have you used to create it?
|
|
|
|
|
The example above makes your Ledger the contract owner.
You can also use your Mist address there instead.
You can deploy from Ledger and make your contract controllable from Mist and vice versa (depends on the address you specify).
|
|
|
|
First of all, if you need this help, then you aren't competent enough to have an ICO.  Second, you can write a constructor function in your contract to accept the owner address (of your Ledger). Also, you can just hardcode something like: contract MyICO {
owner = 0x00abcdef...; // your Ledger address
/* more code follows */
}
|
|
|
|
|
You'll need to import that wallet file into the newest version of Bitcoin Core (by replacing the wallet file it creates).
But first of all, MAKE A BACKUP OF YOUR WALLET.DAT!
COPY IT TO A USB STICK, etc - you don't want losing it if your PC dies.
|
|
|
|
For the first transaction shown: TXID: 37dc3fe6ffddb07229a759f8144e9afddbb46d10ca27b77168ff0edd97e44366 raw transaction: 010000000865ff011229ef2f0c76132c0f91276de02687b267a7b918841b222d8f4f4a83c8000000006a473044022056d8a3dc78d168a7682efa33ebb917500cd3f74d058bc0ca7d0c079809e7064102200ecf64043b162238a5d06036fb2f8ccfdcef1762feb4a08e0dbc7bfe5e84461c012102c81bd15193a92ab05ea8606e7e5b2fe25b3ccdcdad833aa2fb0df9ba012ded32ffffffff55aa5465cf2c38db6819a148ddd0a8e6cd3d158bbb5b9a32e3015fdc42a63758000000006b48304502204f11da80319d09f8a8833095f190ab1661a6d13cb1273a491ba7ac7e2cdad91b022100d7460e270cb2ed492ee11babbba274aa7bbb9b0f38723391be401e31eacf43eb0121033fffecf4500e9b10eb8f61ec229e8d00857c2ba0bacdc7b3fed2800795f6f72dffffffff7c92c6bd13f580e92b9d6e780f5cc5c62ca8b960b86a1cfb3f6e5291f0a75a01000000006b483045022100e430118ed8c1b7745381800408b4078388170a8a21371e73ce1dd7105ef130940220361d81ea71c8553af36aa81a04bb861ab802fb7db2c9d09674e578a6ad3cd4010121038ac48e41bade4aa1291838a4921c86c3cff030a325b32a6b189b510d084ff081ffffffff82072e2f6fc939cf842c2ff7e313941c087f490d42dc64c6ae5efe7554a3b119010000006a4730440220461c3dd5130e5646d122a86f458bc91651b04cfcff69168c1a4e0ebe02d0851502200fef2a44f7f923f59ab00b4e0279a7dc9054c8a42b7fb2ef9cf21c246535e324012102f76390b6576f22f3ccac38756343f2f9ffa3ec044401a672fb16bc799b2c6f89ffffffff45ca3c175d5cabe79ec0bca2a536eb547c975f4832c219cba125d04ce70d9388000000006c493046022100a3c51aa1a37ab313e8bd4ee59322243efad0103cc02541c0b1d74033a8c08386022100d21274e3c826abb9b02dfe710f4c1eccbd3c10f0e1e72afc972e024bb2d20f42012102891391e48042fd24533956d02b94e7d0e6b1b11d954dd950fbe0cf42a2539432ffffffff50cfc2d5186236b219dc0160096faafbfd8bc3c5428c2f9df746f9449634ba42010000006c4930460221009f1d246cfa598b67b2ad1f639f5fe548b0b04adb699bab9d480e04d543c17f4e02210080806b4d2769135bcf57ccb240fbc729761fc75c3cf94acb647607e2fec9e5e80121024dd934eebc67794b930c0e957a9d81b43b547fb06fd83c82279472ad9f8b693fffffffffa7c1edbd57fb05083d7eca09f7f7fe0472fce783bb9cb9364e160667b2e83ceb000000006a47304402201b181a0adea52e488ff3c400b8956ea5bb05f5d5ff3c665de499c7ab56e1b2ea02207493530fd997f50bee8bae9e0d70315dd60bb2577a6a7eb1f52d24e4a267fb7b012103d09768ea4a0878aa14824bccdf3de3e13f4a26dd7c0680619e4d85104f0a975affffffff9f99984edb3b0be4e2c90402d70725b32ccd4342c288d108174962a607e6cc17010000006b483045022100d7508776b336721f22d4145634c853700296cb2a3a5203ad3769afa51da64f7f02204c27f323fb9359f75fbb267da4fa71cf68eb3dc199f19e781cec4b0b49eefb8d0121032ab4ceaedc9390c08079e10d67d9a616953cda1e968e711a0a60ed7dc053893cffffffff021b210000000000001976a9142d10fbcea457ab315563543d0aa558c07b624b1f88acf45d9a10000000001976a914c5075d27a1145d66795e45fa39c21acdb674dd8988ac00000000 I did dabble in a few altcoins but they were pretty doomed. Specifically, QuarkCoin and FedoraCoin. I'm pretty certain that I never moved any significant amount in to either of these coins because I didn't want the risk (in hindsight, pretty accurate). I had my wallets stored relatively cleanly in seperate folders for each coin, however, you have a valid point, so I will do some checking with some other things and see what happens. I really appreciate the help by the way, thank you. Indeed, it's a Quark transaction: https://chainz.cryptoid.info/qrk/tx.dws?37dc3fe6ffddb07229a759f8144e9afddbb46d10ca27b77168ff0edd97e44366.htm. Load up your QRK wallet, maybe you still have some left. P.S. I'm very sorry to disappoint you  P.P.S. Your Quark address is: QeZn3jwoWwEUUe5J2qQCCJgpEdo3obNUcC (1JxnwSf6LUMf3VzGcW5i52uBjNrLY84hvu). It still has some 4000 QRK, maybe you can sell them? |
|
|
|
Thanks for the help all.
I realize I'm chasing ghosts sadly but I'm still super pissed / annoyed / confused.
The address that the transactions came from appears to have never been used either. So both the sending and recieving address are completely empty and never had any transactions. I'd have figured that at least the sending address must have some record of BTC being in it at some point in order to create the (doomed) transactions?
In other words, I just.... I can't understand how I have these ghost transactions in my wallet if both sending and receiving addresses have never had any funds at all (according to the blockchain)?
This would be a life changing amount of funds nowadays, for it to simply "vanish without a trace" is really, really messed up. If the transactions failed and the funds went back to the sending address I could understand but it's like the whole thing has just completely disappeared without a trace.
It's possible that this wallet is an altcoin one. Did you ever have any DASH, Litecoin, etc? Could you post the TXID there so we can try looking it up on different chains? |
|
|
|
It does the exact same thing as a 100$ hardware wallet. It stores your private key safely and untouchable.
[...]
Just unlock the USB stick and run the wallet from inside (if you did not just store the keys). No private key has to leave the stick.
No. If the private key ever touches a computer, it can be compromised. The key is temporarily stored in the RAM when signing transactions, for example. To be used, the computer has to read it from the USB stick which involves an ability to intercept it. |
|
|
|
[...]
No private key has to leave the device. I can not even see any reason whatfor this would be required.
[...]
Those "hardware wallets" are in my opinion overrated, you depend on their services, which may be at any time become obsolete, and you may not be able to use it with other data/wallets other than they provide for you, for a small fee perhaps,
If the private key is handled on the machine, it's been exposed, thus leaving the device. You don't depend on their services. The software for using most of the hardware wallets is open-source, which means that you'll be able to use your wallet even after the manufacturer closes down. |
|
|
|
|
This contradicts the entire purpose of hardware wallets.
The point is that the private keys should never leave the device.
It's not even needed to use VeraCrypt as in your example, a simple, encrypted wallet.dat would work the same if not better.
Malware can steal your private key while it's used on your machine.
Again, the point of using a hardware wallet is isolating your private key from the outside.
The hardware wallet can only sign your transactions when asked to (and would ask for your confirmation for it).
A simple USB stick is not a hardware wallet.
|
|
|
|
|
Are you talking about me?
If so, did I misunderstand something?
The transaction is not abandoned on the Dash chain, either, according to the block explorer.
|
|
|
|
I'm glad to help. If you're willing to tip me, here's my address: 34rHZwgXDnkKvrBAU2fJAhjySTTEFroekd  |
|
|
|
|
Show Posts
