ditto. and, why was the 'generate coins' option removed? will you bring it back or is that only for elitists who can understand setting up scripts?
I somewhat agree. Theoretically a 10mhash CPU could generate 0.35 BTC over the next month if the difficulty stayed stagnant. It won't, but still that is a great way to distribute small amounts of currency to new interested users Incorrect. Besides being slower than other CPU miners, the built-in CPU miner has never supported pooled mining. It only mines full blocks. Thus, users either get zero BTC (highly likely) or 50 BTC (highly unlikely). At current difficulty, you get a block once every 8 years, at 10 Mhash/sec. http://www.alloscomp.com/bitcoin/old_calculator.php |
|
|
|
I'm also happy that the mandatory fee was lowered. But I still don't see, why there has to be a mandatory fee at all.
See the big bold text in the top post -- most transactions are free. I for one would rather see slower Bitcoin adoption than Bitcoin bloat.
I am quite sympathetic to this PoV... |
|
|
|
|
Setting scantime far too low will probably cost you money. At some point overhead becomes more significant than hashing, as cpuminer is not fully pipelined.
|
|
|
|
|
It is highly suspicious when the site operators do not appear on the forums or IRC or otherwise introduce themselves and build trust.
Rather, they simply hand out free money. They first contacted prominent members of the community in an attempt to proxy trust.
An exchange is a huge responsibility, basically a bank, and there is literally zero rep.
|
|
|
|
This is smells like a scam, particularly with Mr. Kz3ro's multiple posts and free money. See this other thread for more details. |
|
|
|
|
Well, it's not a very good scam if it's immediately detected. A smart scammer builds up a bunch of USD and bitcoin deposits, and then disappears.
|
|
|
|
Here is the first paragraph of the first email sent to me by bitcoin7: Hello, Would you be interested to put a topic on Bitcoin.org forum recommending www.bitcoin7.com as a better trading platform than Mtgox? We will be happy to offer you a small bonus in BTC or USD if you do that for us  plus if you are active on other communities or forums, we can go for them too. (emphasis added... mine) |
|
|
|
|
Do not feed the trolls...
|
|
|
|
|
At the present time, eastern European cybercrime is a far more clear, present and real danger to bitcoin users.
|
|
|
|
|
Yes, these people are total unknowns in the community. Be wary.
|
|
|
|
Hey everyone, I just got a PM from new user, bitcoin7.com, telling me about their new exchange, I've checked it out some and boy does it look classy! Check it out for yourselves, and if we could, would it be possible to whitelist the user so they can give a proper introduction themself? www.bitcoin7.comHow much were you paid to make this posting? bitcoin7 contacted me, and offered me coins in exchange for a positive forum posting. They have never heard of AML, and are run by unknowns from Bulgaria. |
|
|
|
I see a whole lot of handwaving in this thread, and very little substance. But Mike makes a relevant point, UPnP is a de-facto standard that's used by virtually all p2p software. The fact that it's even an option puts Bitcoin behind apps like Skype in terms of UI simplicity. It's definitely worth enabling it by default, at minimum.
The relevant question to me is: what widely used software enables UPNP by default? If UPNP is enabled by default on widely used software, as your post seems to indicate, then it seems reasonable that bitcoin may follow suit. I know plenty of P2P software supports UPNP, but what about default-on? |
|
|
|
Twitter user @smarimc claims to have found a protocol level bug that allows the Bitcoin network to be used for a DDoS attack.
Then he should contact the dev team: http://www.bitcoin.org/It is known that there are certain ways to DoS a P2P node, but amplification attacks and DDoS are a different beast. |
|
|
|
|
Version 1.0.2 released.
Changes:
Christian Ludwig (2):
Fix libcurl include path
configure.ac: Beautify yasm test output
Jeff Garzik (3):
only read processor count via sysconf on non-Windows platforms
Fix number-of-threads init logic on Windows
Version 1.0.2.
ckolivas (2):
Linux + x86_64 optimisations.
Cope with older linux kernel headers that don't have the newer scheduling
|
|
|
|
|
Version 0.5 released.
Changes:
Jeff Garzik (2):
applog: fix memory leak; check asprintf() return value
Version 0.5.
Joerie de Gram (1):
Make ntime rolling support configurable
Luke Dashjr (1):
Bugfix: libraries must be in LDADD, not LDFLAGS
MtRed (1):
memcached_get & memcached_set key length is off by 1. Double null make get
Shane Wegner (1):
Output times on STDERR in human readable format.
|
|
|
|
RE merchant (receiver) paying fees: not really workable in bitcoin. RE always pay fees: it is silly to discourage bitcoin users with fees that are not necessary. The vast majority of transactions do not need a fee, as the miners receive the block reward for securing these transactions. a "feeless" or "optional fee" clients will eventually be available
It is available today from bitcoin.org. Isn't that wonderful? |
|
|
|
feature suggestion. "check for updates" and auto install new version.
Many people worry about such a feature being hijacked, and rightly so. One SF hack, and you can steal many bitcoin wallets through a trojan'd binary + auto-update. In theory this is possible through a chain of trust, but it is quite complicated. Do not expect this any time soon. |
|
|
|
Chinese version don't work though, always throw error. I had to delete zh-cn folder, so I can use the English version which doesn't have the error.
Can you pastebin the error, or take a screenshot? |
|
|
|
|
How about re-reading the top post, which (a) mentions wallet encryption and (b) provides a link to code implementing wallet encryption.
|
|
|
|
|
Show Posts
