|
IMO, you're taking this way too seriously guys.
A physical bitcoin is cool, but it's nothing but symbolic. There is obviously no way to have any physical object store a bitcoin. Otherwise we wouldn't need bitcoin in the first place. A physical object can be counterfaited, and if you plan on putting ECDSA keys in it, it can be copied. And you still have the double spending problem. And I'm sure there are many other reason why a physical bitcoin can be nothing but some kind of a marketing toy or something alike.
Still, I'd like to have one. Especially if it's solid gold.
|
|
|
|
Sure  I'm sure that you will put that 100BTC to other good use! I will give something when this comes out. But not 100 BTC. |
|
|
|
I'm considering selling a 10g mini gold bullion.  It's not brand new : it has been bitten a bit but it's still 10g pure gold. I'm planning on making an auction but I might sell it to you directly if you offer me a good price in bitcoin. If you're in Europe I can use a traceable letter. |
|
|
|
5 days to go and highest bid is 105 BTC. I'm sure you can do better than that guys  |
|
|
|
Would you like to buy a brand new graphic card for mining ? Or some other ultra-expensive hardware ? But you don't have enough money ? With my new stock exchange plateform, you could do so quite easily. You just have to walk the following steps : * Write an IPO document describing what you intend to do, pick a name for your company and chose a number of shares for the capital you want to raise. * Send me this document (possibly GnuPG signed), along with a bitcoin address that you own. * Sell your shares pretty much wherever you want : #bitcoin-otc, marketplace bitcoin forum, biddingpond,... Personnaly I don't mine, for I don't have enough processing power, nor bandwidth. But I'd gladly put a few bitcoins in a mining company. |
|
|
|
Ok but where is your public key ? |
|
|
|
We offer Rheingold Complementary Currency  1 Bitcoin = 1 Rheingold Hum that's interesting. Ain't that the first ever attempt to use bitcoin as backing for a fiduciary currency ? If so, that's an important initiative. I hope it will work fine, for paper money is not completely useless (doesn't require electricity to store or exhange, for instance). |
|
|
|
 Sorry, but I just couldn't bring myself to use the requested three apostrophes at the end of the message. Click on the image for more fun with this. Hum... Why does it seem to me this is a fake ? I guess that's an other reason why we want videos. Much more difficult to forge. |
|
|
|
Enfin, utilisateur, c'est vite dit, pour l'instant je suis surtout "possesseur" de 0,05 BT Salut. Je me sens généreux aujourd'hui. Laisse-nous une addresse et je vais doubler ton stock  PS. Voilà, c'est fait |
|
|
|
|
Hum, I've pledged 100 BTC for this. Can I change my mind and cancel it ?
|
|
|
|
After a few weeks of work, I finaly release my version of a bitcoin stock exchange plateform. It's kind of a proof of concept, but it's for real, as I have already to owners of two shares (one eBay share and one DRDGold share). Ownership is identified by the bitcoin address where dividends are to be paid. Nothing else : no GPG key, no DSA key, nothing but the paiement address for future dividends. The site allows an owner to transfer some shares to an other bitcoin address, and thus to an other person. Once transfer is possible, trading is possible. But so far I don't offer any book keeping for order. Trading and negociation must then be handled somewhere else (IRC, forum, biddingpond, whatever...) Making a signature for transfer requires the use of bc_key, written by dirtyfilthy. I whish this app was added to the main bitcoin client, but I suspect the dev-team is not keen on doing so. The site is open source, so anyone could do exactly the same. That's about it. Here is the address : http://grondilu.freeshell.org/brokerage.cgi |
|
|
|
I've added two functions : decodeBase68 and checkBitcoinAddress. I think it might be usefull to check the validity of a bitcoin address in pure bash. Requires "dc", the unix desk calculator. Few people use this reverse polish notation calcultor but it's much easier to handle in scripts. #!/bin/bash
#
# Requires bc, dc, openssl, xxd
#
base58=({1..9} {A..H} {J..N} {P..Z} {a..k} {m..z})
bitcoinregex="^[$(printf "%s" "${base58[@]}")]{34}$"
decodeBase58() {
s=$1
for i in {0..57}
do s="${s//${base58[i]}/ $i}"
done
dc <<< "16o0d${s// /+58*}+f"
}
encodeBase58() {
# 58 =0x3A
bc <<<"ibase=16; n=${1^^}; while(n>0) { n%3A ; n/=3A }" |
tac |
while read n
do echo -n ${base58[n]}
done
}
checksum() {
xxd -p -r <<<"$1" |
openssl dgst -sha256 -binary |
openssl dgst -sha256 -hex |
sed 's/^.* //' |
head -c 8
}
checkBitcoinAddress() {
if [[ "$1" =~ $bitcoinregex ]]
then
h=$(decodeBase58 "$1")
checksum "00${h::${#h}-8}" |
grep -qi "^${h: -8}$"
else return 2
fi
}
hash160() {
openssl dgst -sha256 -binary |
openssl dgst -rmd160 -hex |
sed 's/^.* //'
}
hash160ToAddress() {
printf %34s "$(encodeBase58 "00$1$(checksum "00$1")")" |
sed "y/ /1/"
}
publicKeyToAddress() {
hash160ToAddress $(
openssl ec -pubin -pubout -outform DER 2>/dev/null |
tail -c 65 |
hash160
)
}
|
|
|
|
Now that I have implemented base58 code in bash, I don't even need to connect to blockexplorer #!/bin/bash
#
# Timestamping program
# Returns a valid bitcoin address made from stdin
# To timestamp, just send 0.01 BTC to this address
#
# Requires bc, openssl, xxd
#
base58=({1..9} {A..H} {J..N} {P..Z} {a..k} {m..z})
EncodeBase58() {
# 58 =0x3A
bc <<<"ibase=16; n=${1^^}; while(n>0) { n%3A ; n/=3A }" |
tac |
while read n
do echo -n ${base58[n]}
done
}
checksum() {
xxd -p -r <<<"$1" |
openssl dgst -sha256 -binary |
openssl dgst -sha256 -hex |
cut -d\ -f2 |
sed -r "s/^((..){4}).*/\1/"
}
Hash160() {
openssl dgst -sha256 -binary |
openssl dgst -rmd160 -hex |
cut -d\ -f2
}
Hash160ToAddress() {
printf %34s "$(EncodeBase58 "00$1$(checksum "00$1")")" |
sed "s/ /1/g"
}
Hash160ToAddress $(Hash160)
|
|
|
|
I'd start off with strict sh compatibility, though, not bash, unless there's really a big advantage of requiring bash over lighter posix-compliant sh implementations (e.g. dash).
Writing in POSIX is much less fun. To me GNU is a better standard de facto. Also, what's the point of those excellent GNU tools if we can never use them ? |
|
|
|
And yet, still no asian bitcoin article on Wikipedia. This would be a clearer sign imo. |
|
|
|
Ummm yea... That makes good sense, but I feel like it would get hard to compare against other markets. Maybe I can just have both ! Maybe you make it as some kind of a user preference ? |
|
|
|
|
I think that, instead of pricing bitcoin in other currencies, you should price other currencies in bitcoin.
In the same idea, order books should orders to buy/sell other currencies. For instance, if I want to buy bitcoins against euros, I go on the EURO book and I put a "sell" order.
This would make things much clearer.
PS. It would also make the graph easier to read, since all currency prices could be expressed in the same unit.
|
|
|
|
Isn't DER format the same as raw byte ? Anyway I opened an other thread and Hal found out that the key has a "ASN.1 cruft" or something. So I add to add a tail -c 64.
I have to read about this ASN thing.
Glad your problem got solved. Out of curiosity what are you planning to use the extracted key for? I want to implement an exchange system where owners are identified by a bitcoin address. So in order to transfer an asset to an other person, one just has to sign (with the bitcoin address key) the new bitcoin address. The advantage is that if the asset is a bond or a shareholding, paiements of dividends or coupons can be done on the bitcoin address. |
|
|
|
Try doing tail -c 65 after the base64 -d. Your pubkey has ASN.1 cruft.
Would this work with any key for sure ? |
|
|
|
Yes ! It works  #!/bin/bash
#
# Requires bc, openssl, xxd
#
base58=({1..9} {A..H} {J..N} {P..Z} {a..k} {m..z})
EncodeBase58() {
# 58 =0x3A
bc <<<"ibase=16; n=${1^^}; while(n>0) { n%3A ; n/=3A }" |
tac |
while read n
do echo -n ${base58[n]}
done
}
Hash160ToAddress() {
printf %34s $(EncodeBase58 "00$1$(checksum "00$1")")|
sed "s/ /1/g"
}
checksum() {
xxd -p -r <<<"$1" |
openssl dgst -sha256 -binary |
openssl dgst -sha256 -hex |
cut -d\ -f2 |
sed -r "s/^((..){4}).*/\1/"
}
Hash160() {
openssl dgst -sha256 -binary |
openssl dgst -rmd160 -hex |
cut -d\ -f2
}
PubKeyToAdress() { Hash160ToAddress $(tail -c 65 |Hash160) ; }
|
|
|
|
|
Show Posts
