Hello, i simply need someone to pay via paypal for me (i provide a direct checkout link). Once the payment is confirmed, i will send you the BTC. Obviously only TRUSTED member qualify for this. Cross-post from: https://bitcointalk.org/index.php?topic=5104935.0 |
|
|
|
Is this $9.49 or $949 just to make it clear. If this is $949 then I am sure you will have a hard time to find someone for you. The amount is fairly a lot.
It is $9.49. We (were i come from) do also use the commata ( ,) to seperate dollars from cents.  |
|
|
|
|
Hello,
i simply need someone to pay via paypal for me (i provide a direct checkout link).
Once the payment is confirmed, i will send you the BTC.
Obviously only TRUSTED member qualify for this.
|
|
|
|
But I am only spending the bitcoins that are there on my wallet.
Why is this problem occuring then?
What to do now?
According to electrum, you are trying to spend inputs you don't have the corresponding private key of. What version of electrum are you using ? And how did you create the transaction ? What were your actual steps ? |
|
|
|
> Where did you store the seed phrase?
I sent it to myself as email, in a message which does not contain any reference to Electrum.
Please never never ever do send sensitive information via email unencrypted. Your email account doesn't have to be compromised for your sensitive information inside of email to be compromised. EVERY mailserver on the route between you and the recipient can read the email in plaintext. There is not a single mechanisms which protects emails from being read between sender and recipient. This is one (of a lot) reasons why email is a broken protocol. NEVER store sensitive information (e.g. a seed) online. Whether email, cloud, etc.. All of these online storage solutions are a bad idea. Do ONLY store seeds (or private keys) offline. Preferably not digitally. |
|
|
|
Well, honestly.. the lockbox thing is just a cheaper version (in terms of functionality) of the nano S. - It doesn't provide the ability to store all the coins the nano S does.
- It is not supported by ledger live (which has an awesome UI (personal opinion)
- You are forced to use it together with an online wallet (which is an absolute no-go for me)
I would definitely suggest to get the nano S instead of the lockbox-thing. I don't see any disadvantage compared to the lockbox, only advantages. |
|
|
|
|
If you don't know what it is, you won't be able to set it up.
Currently the lightning network is in beta anyway, it is not intended to be used with money you don't want to lose.
To explain it briefly, the lightning network is a payment network where you can send/receive BTC without an on-chain transaction needed.
This requires you to have a channel open with someone and to have a route to your destination.
The payment then can be routed trough those hops (with multiple 'contracts' between those hops).
It works fully decentralized and trustless.
For a better and more detailed explanation, google it or visit the links already posted here.
|
|
|
|
|
Simply create a new wallet using your backup.
Also.. you do have a paper backup too and not only a digital one, correct ?
I strictly encourage to NOT trust digital devices as the only type of backup. USB sticks can break.
Either by mechanical changes or simply trough too much voltage etc..
You should always keep your backup (armory root key) on a piece of paper.
|
|
|
|
What is the difference between seed and private key. You mean the 12 words that i got initally?
A private key is used to sign transactions to spend UTXO's associated to the corresponding public key. A seed (12-/24- word mnemonic code) is used to generate multiple private keys (using a kind of mathematical equation). This allows you to backup 1 phrase (mnemonic code) which will create the same ('unlimited amount') of private keys. You have the mnemonic seed phrase backed up, not a private key (which is good). Create a new wallet and restore it using this seed. Correct. And preferably make sure you have downloaded the correct file by verifying its signature. |
|
|
|
OS: Windows 10
My Electrum wallet is showing the message
SDL Error
Error:dlopen failed:Library
"libpython3.7m.so.1.0"not found
That's somehow weird. libpython3.7m. so is a shared object. Those are found on unix systems (e.g. linux / android / .. ), but not on windows. The windows 'equivalent' would be a DLL file. Can you verify that you get this error on windows on a desktop version of electrum (and not on your android mobile)? I tried installing my Electrum wallet in my laptop and it is not getting connected
What message do you get when its not connecting at all ? The same ? Another one? Does electrum even start without an error message ? If it does, i suspect something wrong with your network configuration. |
|
|
|
I think it is better to choose "p2sh-segwit (p2wpkh-p2sh)" option because you can get less fee compared too legacy and the transaction is much faster than a legacy address.
The 'speed' of a transaction (i think you mean the confirmation time ? Or the propagation time ?) doesn't differ, regardless of which type of transaction you build. Is the derivation path for native segwit and non native segwith the same or different?
Yes, they differ. Native segwit is m/84'/0/.., where nested segwit is m/49'/0/..@OP: Choosing the type fully depends on your needs. Here is a quick summary: Legacy (P2PKH): - Pro: - Compatibility with each online service
- The possibility to extract future forks exists (even tho not that necessary regarding the value of those forks)
- Contra: Nested Segwit (P2SH nested into P2WPKH): - Pro: - Fixes transaction malleability
- Fees lower than legacy, but higher than native segwit (bech32)
- Contra: - No guaranteed compatibility with future (low quality) forks who don't support segwit
Native Segwit (P2WPKH) - Pro: - Fixes transaction malleability
- Lowest fees of all types (up to ~ 40% lower size (and therefore also fees) of the transaction compared to legacy)
- Contra: - No guaranteed compatibility with future (low quality) forks who don't support segwit
- May not be accepted by older online services which haven't been updated for quite some time, they will show 'invalid address'
Native segwit is definitely becoming a new standard. You should either choose to use bech32 (bc1..) addresses or at least nested segwit (starting with 3...). |
|
|
|
No, you don't need a static IP. Port forwarding and a firewall rule (in case you have a FW running) should be enough.
Actually if he has a router he may need static IP for the computer/laptop inside the local network (192.168.xxx.yyy or 10.0.xxx.yyy) so the port forwarding rule can "reach" his computer/laptop. Oh, inside of the local network he obviously needs a static IP. Port forwarding / firewall won't work if his IP changes daily. But usually your machine is getting the same IP each time logging in (via DHCP). But if this is not the case for OP, he definitely needs a static local IP. What i meant (and what i understood) was whether he needs a static (public) IP address. They can be quite hard to get from an ISP (especially since IPv4 is more than scarce currently). And a static public IP is not necessary. |
|
|
|
It gets a bit more complicated with Bitcoin, as I believe you should offer both SegWit and legacy addresses.
You don't need to 'offer' a legacy address to receive donations anymore. Any halfway up-to-date wallet can send to bech32 addresses. Using a single segwit address should be enough. And if you still believe some user might use wallets which are incompatible to bech32 (which would be way too old wallets), simply use a nested segwit which is accepted by each wallet. How much extra security do you think using fresh addresses will give you, and do you think it is worth the inconvenience resulting from not using a single address.
No practical extra security at all. You can receive transactions as often as you want to the same address. When you send some BTC from the addresses, you public key / redeem script will be published. That's it. This doesn't affect the security in a noticeable way. With bitcoin, you can use the same address as long as you want with as many transaction as you wish. The only thing you are compromising with it, is your privacy. But if you don't care whether people know how often and how much you get in donations, feel free to use a single address for the rest of your life. Security-wise, this is absolutely fine. |
|
|
|
can i change this? instead of creating new..
Is there a reason you don't want to use segwit ? Segwit introduced quite a few advantages (such as smaller size of transactions which result in lower fees). It doesn't only help you to save on fees, it also reduces the complete network load, which results in a more healthy network. Additionally it paves the way to HTLC's (basically lightning network). It has also things fixed (e.g. transaction malleability) compared to the legacy format. I can't think of a single reason to not use bech32 (segwit, ḅc1.. addresses). |
|
|
|
Anyway, one of the secure way to keep bitcoin in your Electrum wallet is to use a multisig wallet instead of a normal wallet. At least use 2/2 multisig wallet. This adds an extra layer for your security.
This adds an extra layer of security if done properly. Your 'Guide' is an example for dangerous sciolism. The whole sense of a multisig wallet is to have multiple people (or devices) signing a single transaction. In your example, you are just signing the transaction twice (from the same device). This doesn't do anything for the security. Also, as pooya87 has mentioned, saving sensitive information unencrypted in a textfile on a windows machine is like asking to get funds stolen. All you do with this guide is to show how to increase the feeling of security AND increase the fees of your transactions while still being on the same level of security. |
|
|
|
this is scary. does anybody know how to find honest servers?
If you want a server you can completely trust.. set up an own server. If you don't want to do this, you'll have to trust a server which is controlled by someone you don't know. Generally this isn't a problem since the server is only used to send transactions and to receive the current balance of your wallet. If you never click on any links and never download any software, you are fine. |
|
|
|
1. Does Android's native Google Backup feature backs up walletbacking.db ? If it does, can we somehow contact Google to try retrieve a copy?
I am pretty (even tho not completely) sure that internal files created by apps are not being backed up by google. Don't you also have to explicitly tell android to backup your apps ? 2. Is there a reliable data recovery method to perform on my Xiaomi 5 where the old walletbacking.db might have still yet to be overwritten despite factory reset?
The internal memory of a mobile phon is a flash memory. Performing recovery on them is not as easy as on a mechanical HD. Besides some basic file recovery software, there isn't much you can do. Did you already try some out? (Enabling USB debugging -> connecting to your computer -> running file recovery software) 3. Any other possibility why I only have one set of 12-word list, and yet I've been using a receiving address that doesn't seem to come from that seed? I tried many possible derivation paths already
Eventually only if you have added an additional password to your seed (which is not possible in mycelium i believe). If you had your funds on a different 'account' inside of mycelium, this usually just results in an index being increased. Which derivation paths did you already try out ? |
|
|
|
I am synced, says i have 8 connections, but i dont think port 8333 is reachable from outside?
That's correct. I made a quick nmap scan: Nmap scan report for 63.142.xxx.198
Host is up.
PORT STATE SERVICE
8333/tcp filtered bitcoin
Nmap done: 1 IP address (1 host up) scanned in 2.07 seconds
It says the port is filtered (by firewall, ISP, etc..). It is not reachable from outside of your local network. Do I have to have a static IP address?
No, you don't need a static IP. Port forwarding and a firewall rule (in case you have a FW running) should be enough. Do you mind showing us the forwarding/firewall rule you set up ? |
|
|
|
You can use your watch-only (online) wallet to create addresses whenever you need them. The master public key (xpub) is all what is needed to generate addresses. You don't need to access your offline wallet just to create new receiving addresses. And to finally answer your question, you can generate X addresses by entering this command into the electrum console: for i in range (X): print (wallet.create_new_address(False))
Obviously you have to replace X by the amount of addresses you want to generate. For a single address: print (wallet.create_new_address(False))
|
|
|
|
Unfortunately there is the misconception that running a google extensions is safer than running an exe, for unexperienced users.
It depends on how you define safer. A web browser extension can: - access all sites you visit
- read / modify each information you enter on any website (e.g. usernames / passwords)
- steal your cookies (which are a form of authentication)
However, a browser extension can NOT: - search through your file system
- download any additional malware (add-ons are run within an isolated environment)
- access your system at all
- do anything non-browser-related
- compromise your system
Running an executable on your system can do anything the user also is able to do (or even more if a privilege escalation is being abused). |
|
|
|
|
Show Posts
