Would it be reasonable to just have a transaction history page for each user and a check box to make it public and make that public page easy to link to? Is PGP stuff necessary?
It would be good to allow a user to sign the transaction history page, or provide some way for the user to put a signed message there, so that users of the gpg based web of trust in #bitcoin-otc can prove an association between their history on CoinPal and #bitcoin-otc. |
|
|
|
|
Great to see a bitcoin implementation developed from scratch!
|
|
|
|
|
This whois for the domain lists a phone number. His website listed in his github account has a phone number as well. A person with the same name as that listed in the whois has 'liked' the bitcoin facebook page, so someone on facebook could contact him through that maybe.
|
|
|
|
The Domino's "proof of concept" was a good idea. Any idea whether Domino's gift cards work outside the United States?
They are US only, excluding Hawaii and Alaska. |
|
|
|
I had to remove the -march and SSE stuff from the makefile. I've posted the makefile I used in the other thread. Hope that helps. |
|
|
|
This is the makefile I used to build on the N900: INCLUDEPATHS= \
-I"/usr/local/include/wx-2.9" \
-I"/home/user/src/db-4.8.30/build_unix" \
-I"/usr/local/lib/wx/include/gtk2-unicode-debug-static-2.9"
# for wxWidgets 2.9.1, add -l Xxf86vm
WXLIBS= \
-Wl,-Bstatic \
-l wx_gtk2ud-2.9 \
-Wl,-Bdynamic \
-l gtk-x11-2.0 \
-l SM
# for boost 1.37, add -mt to the boost libraries
LIBS= \
-Wl,-Bstatic \
-l boost_system \
-l boost_filesystem \
-l boost_program_options \
-l boost_thread \
-L /home/user/src/db-4.8.30/build_unix \
-l db_cxx \
-l ssl \
-l crypto \
-Wl,-Bdynamic \
-l gthread-2.0 \
-l z \
-l dl
DEFS=-D__WXGTK__ -DNOPCH
DEBUGFLAGS=-g -D__WXDEBUG__
CFLAGS=-O2 -Wno-invalid-offsetof -Wformat $(DEBUGFLAGS) $(DEFS) $(INCLUDEPATHS)
HEADERS=headers.h strlcpy.h serialize.h uint256.h util.h key.h bignum.h base58.h \
script.h db.h net.h irc.h main.h rpc.h uibase.h ui.h noui.h init.h
OBJS= \
obj/util.o \
obj/script.o \
obj/db.o \
obj/net.o \
obj/irc.o \
obj/main.o \
obj/rpc.o \
obj/init.o \
cryptopp/obj/sha.o \
cryptopp/obj/cpu.o
all: bitcoin
obj/%.o: %.cpp $(HEADERS)
g++ -c $(CFLAGS) -DGUI -o $@ $<
cryptopp/obj/%.o: cryptopp/%.cpp
g++ -c $(CFLAGS) -O3 -o $@ $<
obj/sha256.o: sha256.cpp
g++ -c $(CFLAGS) -O3 -o $@ $<
bitcoin: $(OBJS) obj/ui.o obj/uibase.o obj/sha256.o
g++ $(CFLAGS) -o $@ $^ $(WXLIBS) $(LIBS)
obj/nogui/%.o: %.cpp $(HEADERS)
g++ -c $(CFLAGS) -o $@ $<
bitcoind: $(OBJS:obj/%=obj/nogui/%) obj/sha256.o
g++ $(CFLAGS) -o $@ $^ $(LIBS)
clean:
-rm -f obj/*.o
-rm -f obj/nogui/*.o
-rm -f cryptopp/obj/*.o
-rm -f headers.h.gch
I had to build boost, db-48.30 and libevent from source as they weren't available in the N900 repositories. |
|
|
|
Because the exchanges are really the only real exit from bitcoins (and lets be honest here, scammers are after cash not bitcoins) unless you consider OTC, but I don't think anyone in #bitcoin-otc would touch dirty bitcoins, especially with someone who has no or little reputation, which a scammer would.
I previously wouldn't have had any problem trading on #bitcoin-otc with a stranger for a large number of bitcoins if I was the receiver of the coins as I was under the impression that receiver of bitcoins was safe. I'm more hesitant to do it now that I know there can be issues selling these coins if I don't know the origin which is why I raised the question. |
|
|
|
|
Does this mean that bitcoins are now subject to chargebacks just like paypal and credit cards? If I receive bitcoins from a stranger and it turns out some are stolen, I try to sell on mtgox and they are then frozen. Now it seems like a bad idea to trade bitcoins with strangers. Previously it was considered safe to trade if you were on the receiving end of bitcoins.
|
|
|
|
I believe the operator of compute4cash is compute4cash on the forums. |
|
|
|
I'm looking to sell $30 on Full Tilt poker for 34BTC or MtGox USD(Equal Trade).
Trading on full tilt can be problematic. They are highly aggressive at locking linked accounts if any of the accounts commit some form of transgression. For example, If you transfer on Full Tilt with player A who has in the past transferred with player B (whom you don't know) and B commits fraud then players A and yourself will often have their account locked while it is investigated. You should never trade with unknowns if this risk could be problematic for you (eg. you rely on Full Tilt for income). |
|
|
|
I was hoping to set up a small mining pool for me and some friends to pitch in on. I was wanting to run a server for the pool on my low-powered netbook (I already use it for other server tasks) running Lubuntu 10.04. However, I am unable to find a proper server to run on Linux -- specifically, a server for puddinpop's RPC clients would be good, though whatever system that works with GPUs is fine. I wasn't sure if I was missing something obvious here, but I've been researching for a while with absolutely no results. I was particularly wanting to use this mining system, as one of my friends who would be participating is in a really rough financial situation.
I think the only open source mining pool server that works with standard getwork clients is jgarzik's pool.py. You can find a link to it in this thread: http://bitcointalk.org/index.php?topic=3078.0It's not a complete solution in that you'll have to read the code to work out how to use it and set up the database it needs. A non-getwork solution is puddinpop's server and clients: http://bitcointalk.org/index.php?topic=1458.0This is what I used to run when I was running a pool. |
|
|
|
1. Your reputation here is good
It's your reputation that is probably more important since you're paying with a payment system that allows chargebacks. Once the BTC provider sends the bitcoins they can't back out of the deal making their reputation less important (assuming they send first). |
|
|
|
I've updated the N900 binary to a newer version. I built from gitub commit b1a657. It's available here: http://www.bluishcoder.co.nz/bitcoin-pool/bitcoind-b1a657.gzI start it on the N900 using: ./bitcoind -noirc -connect=xx.xx.xx.xx -nolisten Replacing 'xx.xx.xx.xx' with a node to connect too. This means no incoming connections will be made to the phone and only one connection is made outgoing. |
|
|
|
Middle level: Can purchase more once you send them a letter containing a password to their confirmed paypal address. For the cost of a stamp, you can prove that a paypal account is not stolen. This could even be automated using a mailing service like l-mail.comAre you suggesting people would email their paypal password to the coinpal maintainer? I doubt you'd find anyone willing to do this. |
|
|
|
That will successfully (a) avoid JSON implementations' int limitations, while achieving the goal of (b) never use floating point to represent bitcoin amounts.
Won't this just move the problem to clients of the JSON interface? They'll either write their own buggy string to float/float to string implementations or use the one in the programming languages standard library which probably does a lossy conversion. How about providing additional JSON parameters for numerator/denominator so the amount can be expressed accurately as a rational number for those that what the safety. |
|
|
|
Also the readme describes an autogen.sh file i don't have and it says that jansson is optional???
If you don't have jansson installed then the cpuminer build system uses its own source copy of it. Try uninstalling libjansson and reconfiguring/building. |
|
|
|
I know that I have to pass my worker credentials to the program and then connect to Slush's URL, but don't know how to do that. If someone could help I'd appreciate it.
minerd --userpass username.minername:minerpassword --url http://mining.bitcoin.cz:8332 --algo 4way Replace 'username' with your username on the pool site. Replace 'minername' and 'minerpassword' with the miner's name and password that you registered on the pool site. Replace (or keep) '4way' with whatever algorithm you want ('c', 'cryptopp', cryptopp_asm32', etc). |
|
|
|
Don't get infected, don't become compromised. Use an Apple computer with OSX or Linux, these are the safest options. Staying with windows will become very risky in the future.
Linux servers get compromised all the time thanks to badly written web applications (just to pick one common vector). If I was a malware author the first servers I'd be targeting would be those offering bitcoin services so I could get access to the wallet. |
|
|
|
When I looked more into the bots found in the search, it appeared that they were simply bots that maintain cookies and other site information (which explains the moderately unsafe rating: because it is a bot used by many sites, some sites probably use it for "tracking cookies" and other privacy-invading methods).
Whatever tool you are using is using the term 'bot' in an odd manner. What tool is it? |
|
|
|
so you'd rather not have the dark pools at all, i take it?
Correct, I'd rather not have dark pools. Mainly because I don't understand why they exist and it seems harmful to me. It seems to me that the point of a market is to trade the currency with the price reflecting demand. Don't dark pools defeat this? |
|
|
|
|
Show Posts
