Bitcoin Forum
August 19, 2019, 03:09:41 AM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 [388] 389 »
7741  Bitcoin / Development & Technical Discussion / Re: Number of connections on: March 20, 2010, 12:45:48 AM
I usually have 45-50 connections on my always-on computer. I counted 49 users in IRC, so it looks like I'm connected to nearly everyone.
7742  Bitcoin / Bitcoin Technical Support / Re: what does this message mean: "Generated (50.00 matures in 100 more blocks)" ? on: March 17, 2010, 12:53:51 PM
Double-click it.
7743  Bitcoin / Development & Technical Discussion / Re: On IRC bootstrapping on: March 16, 2010, 01:28:12 AM
To eliminate segmentation, every peer should have a list of every other peer. Tor also has this requirement, so we should copy them: have several trusted directory servers periodically create a signed list of all peers and publish it via HTTP. All BitCoin clients have the option to act as a directory mirror, which will be indicated in the dirServers' list. Generators need to ask to be added to the list (which could also include info like the maximum number of connections that peer will accept), but people just wishing to make transactions can just get the list from a dirMirror and connect to a few random peers.

If this is too centralized, we can do what I2P did and allow anyone to become a directory server. You need to be able to detect when a dirServer goes rogue in this case, though.
7744  Bitcoin / Bitcoin Discussion / Re: Do BTC payments have to be signed with the same keys used to get the BTC? on: March 11, 2010, 02:08:54 AM
I understand public-key cryptography.

Look at the diagram in section 2 of the BitCoin paper. For owner 1 to send coins to owner 2, he needs to know owner 2's public key in order to create a hash and sign it. To receive payment, owner 3 needs that same public key to verify that it has been signed by owner 1.
7745  Bitcoin / Bitcoin Discussion / Re: Do BTC payments have to be signed with the same keys used to get the BTC? on: March 10, 2010, 04:26:13 AM
The paper seems to say that coins are transferred by signing the receiver's public key with the sender's keys. Then the receiver has to use that same "verified" public key to transfer the coins to someone else. Since the public key is connectible to an identity by the person who originally sent the coins, this is a problem.

I could be wrong about how this works, though. How do you think it works?
7746  Bitcoin / Bitcoin Discussion / Do BTC payments have to be signed with the same keys used to get the BTC? on: March 08, 2010, 12:10:04 PM
Say that I buy 100 BTC from NLS. He has my identity. I then buy something with those particular BitCoins. If the seller and NLS share info, can I be identified? My understanding is that I can, because I used the same BitCoin address to both receive and send those coins.
7747  Economy / Trading Discussion / Re: Money Transfer Regulations on: March 02, 2010, 07:46:03 AM
http://en.wikipedia.org/wiki/E-gold

Quote
In 2007 the proprietors of the e-gold service were indicted by the United States Department of Justice on four counts of violating money laundering regulations. In July 2008 the company and its three directors pled guilty to charges of "conspiracy to engage in money laundering" and the "operation of an unlicensed money transmitting business" in the U.S. District Court for D.C.  The company faces fines of $3.7 million.

Running an exchange seems very dangerous. I would never do it without talking to a lawyer and setting up a LLC.
7748  Bitcoin / Development & Technical Discussion / Re: Command Line and JSON-RPC on: February 27, 2010, 07:18:31 AM
Cool; it works! Grin Thanks for your help!

I am using 2.9.0.

(No memory issues for me.)
7749  Bitcoin / Development & Technical Discussion / Re: Command Line and JSON-RPC on: February 26, 2010, 07:37:50 PM
Using DB-4.7.25 fixed that problem.

I'm now getting this error, though:
Code:
g++ -O0 -Wno-invalid-offsetof -Wformat -g -D__WXDEBUG__ -D__WXGTK__ -DNOPCH -I"/usr/include" -I"/opt/tdep/include" -o bitcoind -L"/usr/lib" -L"/usr/local/lib" -L"/opt/tdep/lib" obj/nogui/util.o obj/nogui/script.o obj/nogui/db.o obj/nogui/net.o obj/nogui/irc.o obj/nogui/main.o obj/nogui/rpc.o obj/nogui/init.o obj/sha.o -l wx_baseu-2.9 -Wl,-Bstatic -l boost_system -l boost_filesystem -l db_cxx -Wl,-Bdynamic -l crypto -l gthread-2.0
obj/nogui/init.o: In function `wxArrayString::Item(unsigned int) const':
init.cpp:(.text._ZNK13wxArrayString4ItemEj[wxArrayString::Item(unsigned int) const]+0x7): undefined reference to `wxTheAssertHandler'
init.cpp:(.text._ZNK13wxArrayString4ItemEj[wxArrayString::Item(unsigned int) const]+0x42): undefined reference to `wxOnAssert(char const*, int, char const*, char const*, wchar_t const*)'
collect2: ld returned 1 exit status
make: *** [bitcoind] Error 1
7750  Bitcoin / Development & Technical Discussion / Re: Command Line and JSON-RPC on: February 26, 2010, 04:58:54 PM
I'm using Berkeley DB 4.5.20.
7751  Bitcoin / Development & Technical Discussion / Re: Command Line and JSON-RPC on: February 26, 2010, 09:18:32 AM
I'm getting errors when trying to compile with just wxBase.

Code:
g++ -c -O0 -Wno-invalid-offsetof -Wformat -g -D__WXDEBUG__ -D__WXGTK__ -DNOPCH -I"/opt/tdep/include" -I"/usr/include" -DwxUSE_GUI=0 -o obj/nogui/util.o util.cpp
In file included from util.cpp:5:
headers.h:22:24: error: wx/clipbrd.h: No such file or directory
In file included from headers.h:100,
                 from util.cpp:5:
db.h: In member function 'bool CDB::Exists(const K&)':
db.h:140: error: 'class Db' has no member named 'exists'
make: *** [obj/nogui/util.o] Error 1

Clipbrd.h isn't installed with wxBase. Moving wxWidgets-2.9.0/include/wx/clipbrd.h to my include directory just eliminates those two "no such file" lines.
7752  Bitcoin / Development & Technical Discussion / Re: Command Line and JSON-RPC on: February 24, 2010, 06:51:40 AM
I'm using Linux From Scratch, so installing a dependency-ridden package like GTK would be a bit of a pain. Why should I add a dozen additional packages and hundreds of megabytes to my system when BitCoin doesn't even use them?
7753  Bitcoin / Development & Technical Discussion / Re: Command Line and JSON-RPC on: February 24, 2010, 03:07:37 AM
On Linux it needs libgtk2.0-0 installed

Will this requirement be removed sometime? I'd rather not have to deal with GTK.
7754  Bitcoin / Bitcoin Discussion / Re: Post your static IP on: February 21, 2010, 09:48:26 AM
I'm at theymos.ath.cx. I should be online 24/7.

You need to look up my IP address before you give it to Bitcoin. My IP address only changes infrequently, so this should be OK.
7755  Bitcoin / Bitcoin Discussion / Re: Proof-of-work difficulty increasing on: February 16, 2010, 06:01:51 AM
I generated 5 blocks today on my Pentium processor. Two of them were within 3 minutes of each other.

I have noticed some slowdown since the adjustment, but I still generate a lot of coins. My computer is off while I'm sleeping, and BitCoin bootstraps quickly when I turn it back on. Do you guys-who-are-having-trouble have the BitCoin port open?
7756  Bitcoin / Bitcoin Discussion / Re: Incorrect Firefox Warning for Bitcoin website on: February 16, 2010, 05:17:17 AM
The CA's root certificate needs to be included in the browser to make the warning go away. CACert isn't included in any popular browser, and Startcom was only recently added to Windows. With Startcom, anyone who doesn't install the optional root certificates update in Windows update will still get an error in Chrome, Safari, and Internet Explorer. Firefox has had it built-in for a while.

HTTPS isn't the default (or really necessary) for bitcoin.org, so it doesn't much matter. If you want to manually switch to HTTPS, then you can deal with the self-signed certificate.
7757  Bitcoin / Bitcoin Discussion / Re: Incorrect Firefox Warning for Bitcoin website on: February 15, 2010, 08:43:04 AM
The TLS certificate is self-signed, so the warning is "correct". The encryption is just as strong as any other HTTPS connection, but without a CA's signature the site's identity can't be guaranteed -- a man-in-the-middle attack could be used. Unfortunately, getting a signature costs money.

Verifying the certificate's fingerprint here before adding an exception will prevent any MITM attack. This is only necessary when you add an exception; subsequent MITM attempts will trigger a warning by your browser.
7758  Bitcoin / Bitcoin Technical Support / Re: Double Click Win32 Exe Installer = NCIS Error. on: February 15, 2010, 03:30:12 AM
It doesn't even detect bitcoin.exe normally, just when it's in the installer. I sent the file to ESET, but I don't know if they actually check into these things.
7759  Bitcoin / Bitcoin Technical Support / Re: Double Click Win32 Exe Installer = NCIS Error. on: February 15, 2010, 12:43:10 AM
Turn off NOD32, download, and save to a different location than before.Then run the installer (the one you just downloaded). It's not a virus. You can turn NOD32 back on after the installation is complete.
7760  Bitcoin / Bitcoin Discussion / Re: What's with this odd generation? on: February 14, 2010, 09:46:58 PM
What property guarantees the continuing profitability? If the cost of electricity triples in 20 years, the number and size of transactions wouldn't change (as far as I know), but running a node would become more expensive and possibly unprofitable.

What stops someone from creating a client that will send repeated transactions just below the fee maximum when it has to in order to avoid fees? Or from many different identities to the same one (if this is possible)? I can see there being a great demand for such a client if BitCoin becomes very popular.
Pages: « 1 ... 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 [388] 389 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!