Just an update. I am still waiting for a response from Cryptonator.
That's almost 2 weeks already, it's not a good sign. Considering their reviews in various " trust" sites ( refer to post #10), I wouldn't be surprised if they do not credit your deposit. |
|
|
|
Which board? Here at Beginners and Help? If yes, those old topic at the top are " pinned" ( indicated by the pin icon near the author:  ). Those are pinned because a moderator deemed it useful for those who might visit this board, specifically for beginners. If its for the other boards, please specify. |
|
|
|
'SHA256SUMS.asc' contains signatures which you can use to verify the file 'SHA256SUMS' which contains the SHA256 hashes of the Bitcoin Core binaries. There are instructions in bitcoincore.org download page: Verify your download |
|
|
|
-snip-
So, the temporary passphrase option is not for long term hodling, right?
The way it's described in their support page is: temporary in a way that it's only used in the session(s) when it's used. After restarting the device, the accounts that you've used in the session will be removed from your Ledger Nano like they never existed. But it can be accessed again by starting another session by typing the exact same temporary passphrase again. It can be used for long term since you can reproduce the created " temporary wallet" in the session by using the same seed phrase ( recovery phrase) plus the temporary passphrase. Like I've said, it's like a " hidden wallet". |
|
|
|
|
Adding passphrase (BIP39 passphrase) to a BIP39 seed phrase will produce a different binary seed, thus different set of keys.
So, by using a temporary passphrase, you'll have access to a different wallet that can only be accessed by typing the temporary passphrase.
Think of it as a separate "hidden wallet" in your Ledger Nano.
|
|
|
|
The first one is how easy it is to create a fake transaction and transmit it to the whole blockchain without it being instantly detected as fake.
There is one widely used scheme but it's not using a fake transaction ( can be used in that "every day spending" scenario). It's done by utilizing " replace-by-fee" flag which makes a transaction replaceable as long as it's not included in the blockchain yet ( 0 confirmation). However, such transactions can be easily identified so merchants that accept 0-confirmation txns ( eg. some Casinos) don't grant the " instant deposit" benefit if it has an 'rbf' flag. It goes like this: The transmitted " unconfirmed" rbf flagged transaction will be seen by most clients and the victim, but when the scammer received what he paid for and wants to " cancel" it, he just have to send another transaction transaction that spends the same input(s) and replace the output with his own address. That essentially boots out the old transaction from most mempools. Bitcoin Core with default setting are setup to replace the older transaction with rbf flag as long as the new transaction follow some specific rules. BIP-0125: https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki#Implementation_Details |
|
|
|
How to go about this.
Is there a way to actually boot up, start up the old Electrum app from the hard disk and then it will itself find its wallet.
The default installation and data directory has always been the same since 2014, except if you've used the " portable version" or set a custom datadir. With that; if you didn't wiped the disk, the OS is intact and you're able to boot it: you can install the latest version of Electrum and it should be able to find and open the wallet files without issues if it's still there ( but don't). Electrum will automatically search for the last opened wallet file logged in the config file in Electrum's data directory, clicking " next" will upgrade that wallet file but it might encounter issues during that process. So it's best to find the wallet file first to be able to create a backup in case it happen. |
|
|
|
-snip-
I also understand your concerns about blockchain web wallet, but I couldn't find any other reliable/trustable web wallet which don't require KYC docs.
At least create an offline backup of your " Recovery Phrase" from 'Security' settings. ( write it on a paper and store it in a safe place) That way, even if you ( will) encounter issues with Blockchain wallet, you can import it to another client and access your funds through it. Last time I tried to create a new wallet, they didn't prompted me to create a backup. |
|
|
|
sorry if this is a bad question, but I followed all of the steps, and after exporting my keys (I followed every step to a T) and pasting them, it still won't let me proceed. there is a "back" option, and a grayed out "next" option. what should I do? Apologies in advance for asking a dumb IT question
'Next' in Electrum is grayed-out because you've pasted an invalid private key in there. Probably what hosseinimr93 has pointed-out or there's still spaces. Another possible issue is, you might have selected the wrong option when creating a new 'imported' Electrum wallet. You have to select " Import bitcoin addresses or private keys" instead of standard wallet. |
|
|
|
I know I also have at least one instance of electrum on one of my old disks
Electrum's wallet file doesn't have a strict naming system, it can be named anything and it doesn't have an extension like " .dat" The default names are " default_wallet" for the first, " wallet_1" for the next, then " wallet_2" and so forth ( if you didn't changed the wallet name). But if it's from a very old version, look for " electrum.dat" file. |
|
|
|
I don't know if Airgap Vault supports PSBT (Partially Signed Bitcoin Transaction) which Electrum generate when exporting unsigned transactions;
if it doesn't, the whole setup wont work.
Yep, this may be the actual technical description of my problem. Thanks for that. If that's the case, you can try Electrum versions lower than 4.x for the watch-only wallet on your Laptop. But you'll be stuck with those old versions so I'd also recommend you to use Electrum on your Cold-storage Android to be able to use the latest version. Electrum supports camera and QR codes in both desktop and Android so transferring the transactions for signing will be easy. |
|
|
|
I wanted to try out yesterday, shortly, AirGap vault with an Lectrum on laptop. On testnet. It didn't work out and I don't know yet if the reason was that testnet is not supported by AirGap, or it's that AirGap vault works only with AirGap wallet. I don't know if Airgap Vault supports PSBT ( Partially Signed Bitcoin Transaction) which Electrum generate when exporting unsigned transactions; if it doesn't, the whole setup wont work. |
|
|
|
You can try to contact the same miner ( mining pool) who mined the transaction ( page8) if he'll agree to your offer. wrote in PM, but no one answered that way( neutraLTC just logged-in today: https://bitcointalk.org/index.php?action=profile;u=181180. Take note that the user will be notified via email when you sent him a PM, unless he disabled it. |
|
|
|
You can try to contact the same miner ( mining pool) who mined the transaction ( page8) if he'll agree to your offer. Blockcypher accepts such transaction but the majority of the nodes and specially miners will just reject that transaction. |
|
|
|
-snip- I am in the process of finding out what Network they selected.
Your address is bech32 so the pretense that it was " sent to different network" doesn't make sense. That address type is native only in Bitcoin, not used or compatible in any other networks. If it's from someone else's Binance account, you might have to start the process of finding out if he's scamming you instead. |
|
|
|
In Electrum, you'll have to manually broadcast it and even if you save it locally, it wont be automatically sent after the nLocktime passed. Since locktime is being used here just as a proof that it has been used, and not because we want to actually set a specific locktime, then just set a locktime in the past as I suggested above. The transaction will then broadcast normally at the time of signing. If OP wants to prove that he changed the locktime and sets it to some block/date in the future, then there is no proof there that he didn't just create the transaction at that future time and broadcast it immediately. Since it's a " personal contest", that will do. But he can at least set it to the next 1~3 block(s) so that he could 'try' what will happen to the transaction when the locktime doesn't go past yet. |
|
|
|
Yes exactly that one. The api call just returns {enabled: true}, maybe this can be tricked, ill give it a shot. The second api code which contains those info will only appear once you entered the correct 'access code' ( 2fa code). If you type the wrong code, the next 'api code' will only contain " error: "Unable to process request". Probably because they wont give the browser access to the encrypted credentials of the user even thought the correct walletID is provided, unless the 2fa code is provided. |
|
|
|
-snip-
Ah yeah, my bad, but you got it exactly right. I want to control my change addresses manually. I see you can unhook "use change address" in Electrum. I wonder how that looks... Your input gets as output as well together with the withdrawal address? Anyway, if any of you knows the easiest way to put a P2HS as change address from a P2PKH, please let me know. This could be smart to do if you want to transfer your funds to segwit to get lower fees, huh? So you just wait to transfer them till the next time you gonna pay for something else. I know you can do "pay to many" as well in electrum, but that makes the fees higher i guess. It cant be done in the same HD wallet since Electrum can only make one script type per wallet. It can be done by either using " Imported" Electrum wallet with P2SH and P2PKH addresses or Multiple Electrum wallets, one legacy and one P2SH-SegWit ( the legacy and P2SH wallet types cannot be created in the latest version using the standard method). Then use " pay to many" as instructed by ranochigo. For the fee, the trick is to minimize the input ( preferably single input) to minimize the transaction's size, then use the 'Advanced' preview to manually set the absolute fee to 300sat and the locktime as well. Here's a sample transaction that has all of your requirements ( in Testnet), made with Electrum: {
"addresses": [
"mnGWeTPSpDQDaAUberY2yXoUBVKdc929oQ",
"tb1qs7nsd3me4tecjy0dxtvu7fv5j77wtlyyk79g46",
"2NDtnDqpu989KZCFheNLbcyrE3Uhh39Dd37"
],
"block_height": -1,
"block_index": -1,
"confirmations": 0,
"double_spend": false,
"fees": 299,
"hash": "02131283383a61cae96659d17ba8037d1a2eb4fbf63b63a464a1ca9c8b641c28",
"inputs": [
{
"addresses": [
"mnGWeTPSpDQDaAUberY2yXoUBVKdc929oQ"
],
"age": 2131727,
"output_index": 0,
"output_value": 208136,
"prev_hash": "27df12d3196bb002529aaebc8c38c2ff9548965f1226bc863e8de2b76076fda1",
"script": "473044022025c3e1fb29d4771f77b1ed9b9f046c35ab5e92521a0c85a87caf39ff9ded4116022014566644d98f5ec0041dea6af247bb087598b7c2a90aa41f26bc8dec9e4078f9012103bb9863910b98ed804e44535ff8373df729b0d68398634ec70ebabbd399da58db",
"script_type": "pay-to-pubkey-hash",
"sequence": 4294967293
}
],
"lock_time": 1640966421,
"opt_in_rbf": true,
"outputs": [
{
"addresses": [
"tb1qs7nsd3me4tecjy0dxtvu7fv5j77wtlyyk79g46"
],
"script": "001487a706c779aaf38911ed32d9cf259497bce5fc84",
"script_type": "pay-to-witness-pubkey-hash",
"value": 100000
},
{
"addresses": [
"2NDtnDqpu989KZCFheNLbcyrE3Uhh39Dd37"
],
"script": "a914e27cd04be97a13089ba664307599dca4b379a2bb87",
"script_type": "pay-to-script-hash",
"value": 107837
}
],
}: 1.4sat/vB @ 220vB | 299 satoshi Locktime set to 13 days from now / next year (1640966421) P2PKH input: mnGWeTPSpDQDaAUberY2yXoUBVKdc929oQ Sent to P2WPKH: tb1qs7nsd3me4tecjy0dxtvu7fv5j77wtlyyk79g46 P2SH-P2WPKH Change address: 2NDtnDqpu989KZCFheNLbcyrE3Uhh39Dd37 One more question (i probably get more later when i try the transaction):
In case of using locktime, does it have to require two actions? One for locking and one for receiving (broadcasting the transaction) or is it possible to like "auto broadcast" at a specific block/time?
In Electrum, you'll have to manually broadcast it and even if you save it locally, it wont be automatically sent after the nLocktime passed. |
|
|
|
-snip-
AFAIK, they link those funds to the user's KYC data. So after creating a new wallet, the "lost" custodial funds should be recovered after the user passed verification. (I'll try to find the source of this info)
Update: So apparently, I remembered this line from their support page's FAQs: Is my Trading Account backed up?However, they included a step to restore the user's recovery phrase in the recovery guidelines. Your Trading Account is associated with your Blockchain.com identity profile. Anyhow, since the Trading account's funds is custodial, Blockchain is the one who'll have access to it once the user can't recover his credentials. |
|
|
|
If a user loses access to his blockchain wallet account, for example, as a topic starter, what will happen to the funds in this account? Will the blockchain team have access to funds and can they take it for themselves? Or these funds will be lost forever.
The ones stored in their " private key wallets" will be lost forever since no one have access to the seed or the private keys. The wallet stored in their server is encrypted so even if they wanted to, they can't spend it. The funds in the custodial parts of the wallet is recoverable though ( e.g.: Trading wallet), that's even if he lost the walletID, password, seed phrase, etc. That's because the funds is hosted by them. AFAIK, they link those funds to the user's KYC data. So after creating a new wallet, the " lost" custodial funds should be recovered after the user passed verification. (I'll try to find the source of this info) |
|
|
|
|
Show Posts
