You can use a mixing service if you want - but you'll just be increasing the likelihood of getting tainted coins.
Not if local mixing and scrambling services were more common and used. |
|
|
|
|
Happy new year! 8000000 bitcoins at $5+ !!!
|
|
|
|
|
I wouldn't say it's 'in the stars'. Bitcoin attempts to reproduce 50 btc every ten minutes, but it's pure chance. 30 seconds or one hour are both reasonable. If bitcoin had been mined exactly every ten minutes, then I think 8M would have been 19 January.
|
|
|
|
Auspicious and not a little fishy... http://blockexplorer.com/b/160000 was mined at 2011-12-31 18:13, only 32 seconds after block 159999. And blocks are mined at roughly 10 per hour - almost double the normal average. |
|
|
|
|
If you happen to know that some inputs are tainted, then the new "June" anon/"coin control" patch should help much. But if every client offered a 'random scramble' feature and numerous web sites offered to scramble multiple user coins, then coins could be properly laundered.
|
|
|
|
(Please correct me if I'm wrong, I'm not 100% sure Mtgox hasn't had a 3rd party audit.)
As I remember, Mt. Gox' auditor indirectly published the names, email addresses, and hashed passwords of all of Mt. Gox' customer base. |
|
|
|
|
Also, I believe Puik released much of his Java code, but most of his key handling is actually client-side in JS.
|
|
|
|
... browser does not remember my Bitcoinica username and password whenever my session expires
remove the PJAX ... alternatives of implementation Hi Zhou, seems to work now. Thanks. New question, what does the asterisk mean? ▲4.59871 SELL ▼ *4.7246 BUY |
|
|
|
Bubbles are symmetrical or dramatically crashing. This was a bubble:  this was not:  |
|
|
|
suggestion:
fork the client, and rename wallet to keyring.
please fork the client, if you want it to change!
i will keep my "wallet.dat" client.
Maybe you'll keep your wallet.dat, but after asking for it twice, I must indulge: diff --git a/bitcoin-qt.pro b/bitcoin-qt.pro
index b690fae..fb267de 100644
--- a/bitcoin-qt.pro
+++ b/bitcoin-qt.pro
@@ -131,3 +131,3 @@ HEADERS += src/qt/bitcoingui.h \
src/qt/bitcoinamountfield.h \
- src/wallet.h \
+ src/keyring.h \
src/keystore.h \
@@ -135,3 +135,3 @@ HEADERS += src/qt/bitcoingui.h \
src/qt/transactionview.h \
- src/qt/walletmodel.h \
+ src/qt/keyringmodel.h \
src/bitcoinrpc.h \
@@ -178,3 +178,3 @@ SOURCES += src/qt/bitcoin.cpp src/qt/bitcoingui.cpp \
src/qt/bitcoinamountfield.cpp \
- src/wallet.cpp \
+ src/keyring.cpp \
src/keystore.cpp \
@@ -182,3 +182,3 @@ SOURCES += src/qt/bitcoin.cpp src/qt/bitcoingui.cpp \
src/qt/transactionview.cpp \
- src/qt/walletmodel.cpp \
+ src/qt/keyringmodel.cpp \
src/bitcoinrpc.cpp \
diff --git a/contrib/bitrpc/bitrpc.py b/contrib/bitrpc/bitrpc.py
index b02b299..ae109f3 100644
--- a/contrib/bitrpc/bitrpc.py
+++ b/contrib/bitrpc/bitrpc.py
@@ -17,6 +17,6 @@ cmd = sys.argv[1].lower()
-if cmd == "backupwallet":
+if cmd == "backupkeyring":
try:
path = raw_input("Enter destination path/filename: ")
- print access.backupwallet(path)
+ print access.backupkeyring(path)
except:
@@ -302,6 +302,6 @@ elif cmd == "validateaddress":
-elif cmd == "walletpassphrase":
+elif cmd == "keyringpassphrase":
try:
- pwd = raw_input("Enter wallet passphrase: ")
- access.walletpassphrase(pwd, 60)
+ pwd = raw_input("Enter keyring passphrase: ")
+ access.keyringpassphrase(pwd, 60)
print "\n---Wallet unlocked---\n"
@@ -310,7 +310,7 @@ elif cmd == "walletpassphrase":
-elif cmd == "walletpassphrasechange":
+elif cmd == "keyringpassphrasechange":
try:
- pwd = raw_input("Enter old wallet passphrase: ")
- pwd2 = raw_input("Enter new wallet passphrase: ")
- access.walletpassphrasechange(pwd, pwd2)
+ pwd = raw_input("Enter old keyring passphrase: ")
+ pwd2 = raw_input("Enter new keyring passphrase: ")
+ access.keyringpassphrasechange(pwd, pwd2)
print
@@ -323,2 +323,2 @@ elif cmd == "walletpassphrasechange":
else:
- print "Command not found or not supported"
\ No newline at end of file
+ print "Command not found or not supported"
diff --git a/contrib/debian/examples/bitcoin.conf b/contrib/debian/examples/bitcoin.conf
index e56c43c..8762a05 100644
--- a/contrib/debian/examples/bitcoin.conf
+++ b/contrib/debian/examples/bitcoin.conf
@@ -68,3 +68,3 @@ gen=0
-# Pre-generate this many public/private key pairs, so wallet backups will be valid for
+# Pre-generate this many public/private key pairs, so keyring backups will be valid for
# both prior transactions and several dozen future transactions.
diff --git a/contrib/debian/manpages/bitcoin.conf.5 b/contrib/debian/manpages/bitcoin.conf.5
index 1243253..5802f8b 100644
--- a/contrib/debian/manpages/bitcoin.conf.5
+++ b/contrib/debian/manpages/bitcoin.conf.5
@@ -72,3 +72,3 @@ Enable or disable use SSE instructions to try to generate bitcoins faster.
\fBkeypool=\fR\fI'100'\fR
-Pre-generate this many public/private key pairs, so wallet backups will be valid for both prior transactions and several dozen future transactions.
+Pre-generate this many public/private key pairs, so keyring backups will be valid for both prior transactions and several dozen future transactions.
.TP
diff --git a/contrib/debian/manpages/bitcoind.1 b/contrib/debian/manpages/bitcoind.1
index 0179406..4f99899 100644
--- a/contrib/debian/manpages/bitcoind.1
+++ b/contrib/debian/manpages/bitcoind.1
@@ -83,4 +83,4 @@ This help message
.TP
-\fBbackupwallet 'destination'\fR
-Safely copies *wallet.dat* to 'destination', which can be a directory or a path with filename.
+\fBbackupkeyring 'destination'\fR
+Safely copies *keyring.dat* to 'destination', which can be a directory or a path with filename.
.TP
@@ -197,3 +197,3 @@ Checks that 'bitcoinaddress' looks like a proper bitcoin address. Returns an obj
"isvalid" : true or false.
- "ismine" : true if the address is in the server's wallet.
+ "ismine" : true if the address is in the server's keyring.
"address" : bitcoinaddress.
diff --git a/contrib/wallettools/walletchangepass.py b/contrib/wallettools/walletchangepass.py
index 30f3f5b..3f2867a 100644
--- a/contrib/wallettools/walletchangepass.py
+++ b/contrib/wallettools/walletchangepass.py
@@ -2,4 +2,4 @@ from jsonrpc import ServiceProxy
access = ServiceProxy("http://127.0.0.1:8332")
-pwd = raw_input("Enter old wallet passphrase: ")
-pwd2 = raw_input("Enter new wallet passphrase: ")
-access.walletpassphrasechange(pwd, pwd2)
\ No newline at end of file
+pwd = raw_input("Enter old keyring passphrase: ")
+pwd2 = raw_input("Enter new keyring passphrase: ")
+access.keyringpassphrasechange(pwd, pwd2)
diff --git a/contrib/wallettools/walletunlock.py b/contrib/wallettools/walletunlock.py
index f847c6f..7bcec90 100644
--- a/contrib/wallettools/walletunlock.py
+++ b/contrib/wallettools/walletunlock.py
@@ -2,3 +2,3 @@ from jsonrpc import ServiceProxy
access = ServiceProxy("http://127.0.0.1:8332")
-pwd = raw_input("Enter wallet passphrase: ")
-access.walletpassphrase(pwd, 60)
\ No newline at end of file
+pwd = raw_input("Enter keyring passphrase: ")
+access.keyringpassphrase(pwd, 60)
diff --git a/doc/build-unix.txt b/doc/build-unix.txt
index 5389339..47e6e45 100644
--- a/doc/build-unix.txt
+++ b/doc/build-unix.txt
@@ -28,3 +28,3 @@ Dependencies
libssl SSL Support Secure communications
- libdb4.8 Berkeley DB Blockchain & wallet storage
+ libdb4.8 Berkeley DB Blockchain & keyring storage
libboost Boost C++ Library
diff --git a/doc/coding.txt b/doc/coding.txt
index b3c812a..c93479c 100644
--- a/doc/coding.txt
+++ b/doc/coding.txt
@@ -49,3 +49,3 @@ CRITICAL_BLOCK/TRY_CRITICAL_BLOCK macros to protect data structures.
Deadlocks due to inconsistent lock ordering (thread 1 locks cs_main
-and then cs_wallet, while thread 2 locks them in the opposite order:
+and then cs_keyring, while thread 2 locks them in the opposite order:
result, deadlock as each waits for the other to release its lock) are
@@ -79,3 +79,3 @@ ThreadTopUpKeyPool : replenishes the keystore's keypool.
-ThreadCleanWalletPassphrase : re-locks an encrypted wallet after user
+ThreadCleanWalletPassphrase : re-locks an encrypted keyring after user
has unlocked it for a period of time.
@@ -86,3 +86,3 @@ ThreadDelayedRepaint : repaint the gui
-ThreadFlushWalletDB : Close the wallet.dat file if it hasn't been used
+ThreadFlushWalletDB : Close the keyring.dat file if it hasn't been used
in 500ms.
diff --git a/doc/readme-qt.rst b/doc/readme-qt.rst
index 0901773..ed6d2e3 100644
--- a/doc/readme-qt.rst
+++ b/doc/readme-qt.rst
@@ -6,3 +6,3 @@ Features
-- All functionality of the Wx GUI, including wallet encryption
+- All functionality of the Wx GUI, including keyring encryption
... and a whole lot more
|
|
|
|
|
Exactly! It's either arrogant or pathetic for any of us to refer to the 'idiot masses' as if to exclude ourselves by disassociation. Bitcoin has a serious acceptance problem. Just about anyone on this forum has had to learn about keys with or without the help of common terminology.
If bitcoin is to become popular, then blockchain, blocks, transactions, addresses, and keys must enter the lexicon. Just as email, browser, web, app or thousands of other terms we now take for granted.
It is true that many people do not differentiate the browser from the internet, but that should not mean that we intensionally merge or confuse the two, otherwise even fewer would understand, and the last mile might never have been traveled (the chasm might never get crossed).
In order for bitcoin to be understood, it requires a powerful metaphor. Every mass consumption computer application has a metaphor of which bitcoin currently lacks. The metaphor might evolve, but resistance to the notion impedes progress. From the desktop metaphor, the browser/navigator/explorer metaphor, to the email postal metaphor, chat, bulletin board, encyclopedia, slideshow, ...
|
|
|
|
|
If geeks don't care and the idiot masses don't care, then for the 0.1% who do care and might want to understand, the keyring term is superior.
Yet I disagree with your numbers. The crypto-geeks should prefer the correct terminology, and the idiot masses are not so great.
|
|
|
|
|
1) The cashier rings up the goods.
2) They give you a total.
3) You enter password and transfer bitcoins to or from your wallet
4) repeat (1) 100+ times
5) computer infected with a virus or harddrive fails (guaranteed)
6) You lose all of your money because you didn't understand how a wallet works or why it should be backed up incrementally
Done.
Are all the conservative nay-sayer against 'keys' because you think 'wallet' is superior, or you believe the semantics don't matter because your target audience is silk road?
|
|
|
|
For the masses it works just fine.
Are you kidding? The masses are not using bitcoin. The masses do not understand bitcoin. Read the threads. People are CONFUSED by the terminology. Find me a single individual who is interested in bitcoin but not interested in how it works. I will find you dozens of individuals who do not use bitcoin and are afraid of bitcoin because they do not understand it. but made completely irrelevant if the masses don't accept your view.
Who are these masses you are talking about? I suspect you are talking out of your ass. The existing geeky user base does understand keys and do not care what the name of the wallet is - but most of them were at some point confused. I am supporting the OP suggestion not to make it easier for geeks, who would accept banana.dat, but for the potential masses who are not yet using bitcoin, or those who've just begun but are currently confused. Building a bridge over a chasm one step at a time is easier, and many times better, than trying to leap the chasm in a single jump.
'Wallet' brings the user to the chasm (money), but it does not help them cross the bridge (understanding). In order to cross the bridge, you must throw out the 'wallet' metaphor and introduce new incompatible metaphors, namely keys. There is NO WAY to understand bitcoin at even a superficial level without 'keys'. Wallet adds nothing to the education except unnecessary baggage. A keyring brings the user to the chasm and can be used to continue over the bridge. In fact, the keyring is not just a metaphor, it is correct and leads to NO misunderstanding for neither the newbie nor geek. Would e-mail have been adopted and understood as easily if it were called electronic-telephone? Or is the postal metaphor superior? They could have called it digital-bottle-in-the-sea-distribution. Mail was most obvious and the metaphor extended understanding, we deliver mail to a mailbox to be read passively. Digital-Telephone would have immediately signaled 'communication' (just as wallet signals money) but both would lead to misunderstandings. The notion that one should fork the project over terminology is asinine. Bitcoin is beta software with a tiny user base. Now is a good opportunity to correct the mistakes and clarify the terminology before bitcoin reaches the masses, so that bitcoin can better and more easily reach the masses. |
|
|
|
|
Because unlike a bike shed, the term 'wallet' is confusing and leads to unfounded assumptions and more importantly, does not lead to important critical assumptions. A metaphor should not just lead to an immediate association (wallet=money) but imply features, extending the users understanding. The wallet metaphor is a dead end. Yes, it's money, but the entire metaphor stops and nothing further can be correctly implied.
Copy wallet = two unique unrelated money vessels
Copy keys = two similar devices granting access to the same vessels
Delete wallet = money falls on the floor
Delete keys = access to money lost
Wallet addresses = makes no sense
Key addresses = similar to postal address, or safe deposit box number
Import keys to wallet = makes no sense
Import keys to keyring = perfectly logical
Backup wallet after receiving change = makes no sense
Backup keyring after generating new keys = perfectly logical
Explaining how bitcoin works with wallet = metaphor is unhelpful, need to describe keys
Explaining how bitcoin works with keyring = useful metaphor that can extend user understanding
|
|
|
|
|
But a key can be converted into a song... Freedom of speech in any civilized country.
|
|
|
|
How does the address metaphor fit in with a wallet? Oh, that's right. It doesn't. keys = ... my post box
|
|
|
|
A 'wallet' is entirely inaccurate and leads to confusion and money loss. Why is a wallet metaphor which I carry in my right pocket easier to understand than a keyring which I carry in my left pocket? The fact that a keyring more closely resembles the model means that it is the superior metaphor. The reason for using existing terminology for new concepts or paradigms is to ease the transition for the masses who are not on the bleeding edge, nor do they care to be.
Both wallet and keyring are already in the common English lexicon. A keyring is also commonly used within the digital lexicon while wallet is not. A keyring is exactly the correct terminology as a real world metaphor and an established digital term. |
|
|
|
The FDR is probably wishing that they thought of bitcoin.
FDR isn't doing a lot of wishing of late? |
|
|
|
|
oolong is a very generic term. Any specifics, like region, country, oxidization, leaf type, fineness, year, packaging?
|
|
|
|
|
Show Posts
