Edit: about your question: yes, it's still an experiment. It may have left this stage in a technological perspective (it works secure), but it's still an experiment in a economic-political perspective.
That's exactly my point of view. The experimental part of the technology is mostly over (I'm fairly sure that we will manage the block size / transaction frequency problem and other technical issues) but the economical part of the experiment is just in its beginning stage. Currently, a huge part of the bitcoin economy is revolving around exchanges and speculation against other currencies. I'd call this economic masturbation, it's not very productive even if it's sometimes fun. Bitcoin economy will become much more interesting when the focus actually moves towards goods and services. However, I don't see bitcoin as a global future currency or as a replacement for existing national currencies. When people have a choice of currency they can use (not like the decreed switch from european national currencies to euro,) they will prefer the currency that is most versatile, with a big preference for whatever they are already used to. Onkel Paul
|
|
|
Can someone explain what are the ways to make money on this forum and can someone teach me about this bitcoin please
Yes. Read. After you've read all forum threads, you will know. Seriously, do you really think that everyone who can't be bothered to go to the "Beginners & Help" section and read the article marked "NEWBIE README" gets a personalized introduction and free lesson about bitcoin and its uses? Read! Onkel Paul
|
|
|
Where 22 bitcoin actually sent is it in the blockchain? Email support I couldn't find any info on the help page.
The transaction is not in the blockchain (could not be because it would be invalid) and most likely isn't in the unprocessed transaction pool either because it should not be propagated by full nodes. I assume that the wallet only thinks that transaction has been sent - isn't there any way of deleting unconfirmed transactions with trezor? I don't know anything about how this wallet works... Onkel Paul
|
|
|
How did you manage to create a transaction that leaves your balance in the negative? That should not be possible at all. The transaction will not be confirmed because that would constitute a double spend.
Onkel Paul
|
|
|
So wie ich das jetzt im Netz gelesen habe bringt der Betrieb von Fullnodes für den Betreiber außer dem ideellen Wert der Netzwerkunterstüzung nichts außer "spesen". Die Transaktionsgebühren gehen ja an die Miner. Ist das so richtig? Hab nämlich ein PI2 das aktuell etwas unterfordert wird So ist es. Nodes profitieren (bitcoin-)finanziell nicht von ihrer Aktivität, nur Miner. Ich habe keine Ahnung, ob das beim Design von Bitcoin so beabsichtigt war oder ob eine Kombination von Node und Miner als das normale angenommen wurde. Aktuell gibt es jedenfalls für den Betrieb von Nodes ohne Miner kaum mehr als ideelle Gründe, wenn man nicht gerade ein Bitcoin-basiertes Business hat, wo der eigene Node für die Verarbeitung der Transaktionen schon sinnvoll ist. Onkel Paul
|
|
|
Online wallets? Too many horror stories. I'm going to second this. Online wallets are far too risky. Even with a legitimate site, it can be hacked, an employee can go rogue, etc. You're basically opening yourself up to a lot more risks than you would be otherwise. Unlike cash, which is FEDERALLY insured when in a bank, your BTC, if stolen/hacked/etc. is gone forever. Always keep it in your own possession at all times. Weird how everybody chimes in to online wallet bashing while the poster asked specifically about two non-online wallets (mycelium and electrum) that keep wallet data (private keys) local while using online services to access the blockchain. These wallets are just as safe as a standard bitcoin-qt wallet but need much less data storage and transfer capacity. Of course they rely on external services to access the blockchain, but at least mycelium allows one to export private keys into some other wallet (don't know about electrum but I think it has similar features.) Onkel Paul
|
|
|
Die Namensgebung ist für mich unintuitiv, unter "Eurokurs" würde ich normalerweise den Preis eines Euro in einer anderen Währung verstehen, typischerweise in Dollar. Tatsächlich wird dort aber der Preis eines Dollar in Euro angegeben, und das ist wohl auch die übliche Konvention. Eine steigende Kurve bedeutet also, dass man mehr Euros für die gleiche Anzahl Dollars ausgeben muss; unter der (impliziten) Annahme, dass der Dollar ungefähr gleich viel wert bleibt, hätte da also der Euro an Wert verloren. Onkel Paul
|
|
|
"Show new replies to your post" and "Watchlist" are two separate mechanisms, and I agree that it's annoying that you can't unfollow a thread in the "Show new replies" section once you have posted in it. I don't know how the mythical new forum software handles this, but to me it looks like the best way of implementing the desired functionality would be to have a profile option "add threads to watchlist when I post in them." That way, you can remove them from your watchlist just as any other watched thread once you lose interest in the topic. Maybe watchlist entries should be marked as either "manual" or "auto-created when you responded to a topic", but that would be icing on the cake and not really necessary.
Onkel Paul
|
|
|
Get a laser machine and some bits of wood.
How can this be a method of earning money? Didn't you follow the WoodCollector thread? The member sold Bitcoin-themed wood sculptures and was accused of laser cutting and engraving. I don't know whether he actually did, but if he did, it would make the results much less valuable of course. Onkel Paul
|
|
|
Habe soeben, wie versprochen, ein Adventslied gesungen ("Wir sagen euch an den lieben advent").
Pics (Video) or it didn't happen! Ich bin aber auch ohne Adventslied ganz zufrieden, mir ist ein langsamer Anstieg lieber als eine Rally, bei der man jederzeit mit dem Absturz rechnen muss. Ob der Anstieg wirklich von Dauer ist, wird man sehen. Aber im Moment bin ich gedämpft optimistisch. Onkel Paul
|
|
|
Why in the world would the price fall to 1-2 $ because its limited supply ? The point of limited supply is increase of value, not its loss, it works other way around.
Limited supply only corresponds to high price if there is sufficient demand. Future demand for bitcoin can't be reliably estimated - for example, a theoretical new crypto currency might prove vastly superior to bitcoin, and bitcoin holders would try to exchange their bitcoin assets into that new currency. In such a situation, demand would become pretty low while supply would be temporarily much higher than what is generated through mining. In such a situation, there may be additional factors: Miners might be shut off when bitcoin price becomes too low to make their operation economically feasible, and block times might temporarily become much longer (before difficulty adjustment correcty for the loss in mining power) making bitcoin even less attractive. This is a completely theoretical scenario, but it's not impossible. Onkel Paul
|
|
|
Yes. Bitcoins don't lose validity as long as you keep the private keys safe. But it is quite possible that some of the huge bitcoin stashes from early mining are inaccessible due to lost wallets - people did not be particularly careful with their wallets when bitcoins were worth basically nothing.
Onkel Paul
|
|
|
I need to backup my wallet.dat file every time amount of my coins is changed? Or it is just some universal id of my wallet?
With bitcoin-qt, wallet.dat contains keys for all addresses that have been used already, plus 100 keys for addresses that have not been used yet. So you really need to make a new backup only after about 100 new addresses have been used. Note that whenever you spend a bit, a new address is being used to receive the "change", so you need to count outgoing transactions, too. Of course, you should do backups much more frequently, but you don't need to back up your wallet after each transaction. Hierarchical deterministic wallets (see https://en.bitcoin.it/wiki/Deterministic_wallet) compute all addresses from a single 128-bit seed which is normally represented as 12 common english words. For this kind of wallet, backing up the seed (which you can simply write down on a piece of paper) is all that you need. Onkel Paul
|
|
|
Also tried this tool here https://getaddr.bitnodes.io/and it says I'm unreachable ....but I'm writing form the same pc where I'm running bitcoincore and with the same connection Is it possible that your router or firewall is set up to block incoming connections to port 8333? (If using a router, you'd probably have to forward port 8333 explicitly unless bitcoin-qt is using UPnP and your router is set up to support it) Onkel Paul
|
|
|
Here's an example that's not entirely accurate but easily understandable: Your wallet file is like a keyring - it holds the keys for your own bitcoin addresses. Imagine a huge room full of safe deposit boxes. Each box corresponds to a bitcoin address and has a door that can only be opened with the correct key. In addition, it has a slit through which bitcoins can be put into the box but not retrieved. Everybody can enter the room and see how much is contained in each box. This room is the blockchain. Whenever you create a new address, a box with that address "magically appears" but nobody can see it in the room before someone puts some bitcoin value into it because the blockchain does not store addresses but only payments to addresses (this is simplified, there are some other special kinds of payments). Since you can create an arbitrary number of addresses, it is not easily possible to see which addresses belong to you. When someone sends you money, they know that the address they're sending to is one of yours, but they don't know your other addresses. If you send money from one of your addresses to someone else, they will know that you're the owner of that address. Therefore it is advisable to use each address only once (unless you're ok with tracability of your transactions, for example when you're a charity.) When you lose a key, you can't access the value stored in its box anymore, and when a key is copied by a thief, they can access your box just like you could. So you need to protect you wallet against loss and against unauthorized access. Loss can be prevented by backing up your wallet file regularly, while theft can most easily be prevented by protecting the wallet file with a strong (unguessable) passphrase. Of course, when the computer on which you access the wallet file becomes compromised (keylogger etc.) then the keys in your wallet can be copied by a thief, so you need to be extra careful about this.
Onkel Paul
|
|
|
Zählt Bitcoin-Traffic als Filesharing? Ist zwar peer-to-peer, aber Files im engeren Sinne sind das ja nicht... Onkel Paul
|
|
|
Die bitcoin-Partition ist allerdings schon auf 24 GByte angewachsen. Auf meinem Mac ist der blocks-Ordner schon 32 34 GByte. Lange wird daher die Partition nicht halten.
Könntest ja per LVM die zwei 32GByte-Karten sozusagen zusammenfassen und ein knapp 64GByte großes Volume anlegen. Damit kommt man dann schon ein bisschen weiter, aber natürlich würdest du dann von vorne anfangen. Onkel Paul (bin mir nicht sicher, ob Raspbian LVM drin hat, müsste aber eigentlich)
|
|
|
Switch off that harddisk immediately and don't do anything else to it.
This. If you want to maximize your chance of recovering anything from your HD, don't use it anymore except read-only with appropriate file recovery tools. I notice that OP did not post anything after the first question and didn't even login afterwards, so we're basically preaching to a brick wall... Maybe the info will help others who are clever enough to use the forum search when they have a similar problem. Onkel Paul
|
|
|
When I look at the peers list in bitcoin-qt, I'm seeing very few 0.10 nodes - looks like adoption of the new bitcoin core is pretty slow, or is that normal?
Onkel Paul
|
|
|
2015-02-27 14:55:26 Error: Couldn't open socket for incoming connections (socket returned error An address incompatible with the requested protocol was used. (10047))
Do you see this line in older logs as well? It looks like a firewall is interfering with the listening port. I don't know whether this could possibly cause a crash, but you might want to check this. Onkel Paul
|
|
|
|