And a bash function for the geeks out there: function fb() {
wget -qO- http://www.firstbits.com/api/?a=$1 |tr -d ' '
#curl -so- http://www.firstbits.com/api/?a=$1 |tr -d ' '
echo
}$ fb 12345
12345Vypv2QSmuRXcciT5oEB27mPbWGeva
$ fb 1mtgox
1MTgoX8xqw5juSwgSVNTSJRJWG5onS3xnm
$ fb 1linux
1LiNUXcexgmQqPw7ETGKirpyzdhzHkT3t7 |
|
|
|
|
Yo puedo aportar conocimientos técnicos; pasta no...
|
|
|
|
Just curious - does the patch say how many addresses it generates and looks through per second?
Look in the debug.log for lines like "Vanity key tried 100000". Give it some minutes (20?) to appear though. What I really miss in the debug log is a timestamp; shouldn't be hard to add even when not being able to say hello in C++  . |
|
|
|
Firstbits: 12345
How did you come across that? By using the vanity patch (compilation required) and a couple of hours of CPU time. |
|
|
|
Why not use a config file? See #473. |
|
|
|
|
I actually *wanted* to put it there, but didn't know about that "Personal text" in the configuration. Great!! Seems that linking with [ url= ] isn't supported tho...
|
|
|
|
The wiki says: Mainline addresses can be 25-34 characters in length, and testnet addresses can be 26-34 characters in length. Most addresses are 33 or 34 characters long, though. I had already read that when I first knew about bitcoin, but I read so many things in a couple of days that it's no surprise I've forgotten many of them . |
|
|
|
Nope, probably a bug. The address you generated is not a valid bitcoin address.
bitcoind disagrees: $ for I in 113wjPuzxuDn3WjjautVdQu28DhA8zqhy3 11dYT3E4D9QWocteC9bnMzvWaSSqNn8m4 12345Vypv2QSmuRXcciT5oEB27mPbWGeva; do
> ./bitcoind validateaddress $I |grep -E 'isvalid|address'
> done
"isvalid" : true,
"address" : "113wjPuzxuDn3WjjautVdQu28DhA8zqhy3",
"isvalid" : true,
"address" : "11dYT3E4D9QWocteC9bnMzvWaSSqNn8m4",
"isvalid" : true,
"address" : "12345Vypv2QSmuRXcciT5oEB27mPbWGeva",
$ _ A different installation of bitcoin (version 0.3.21) on a different computer gives the same output. |
|
|
|
En USA ya puedes comprar comida con bitcoins. Para que van a necesitar los dólares?
Y en España puedes comprar pienso para los gatos, la próxima vez que necesite les hago un pedido. No hablo de "necesitar" dólares, yo no los necesito. Sin embargo mi empresa me paga en euros, ¿de dónde saco las bitcoins para comprar pienso si el poder legislativo decide cerrar los mercados? ¿Tendré que resignarme a enviar mis euros a las Islas Caimán o a Costa Rica para comprar bitcoins? |
|
|
|
Hmm, if I quote the regex in the shell, the generated address is shorter: $ ./bitcoind getaddressesbyaccount ''
[
"12345Vypv2QSmuRXcciT5oEB27mPbWGeva",
...
]
$ ./bitcoind getnewaddress '' '^11'
...searching...
$ ./bitcoind getaddressesbyaccount ''
[
"11dYT3E4D9QWocteC9bnMzvWaSSqNn8m4",
"12345Vypv2QSmuRXcciT5oEB27mPbWGeva",
...
]
$ ./bitcoind getnewaddress '' ^11
...searching...
$ ./bitcoind getaddressesbyaccount ''
[
"113wjPuzxuDn3WjjautVdQu28DhA8zqhy3",
"11dYT3E4D9QWocteC9bnMzvWaSSqNn8m4",
"12345Vypv2QSmuRXcciT5oEB27mPbWGeva",
...
]
$ _ Does that make sense? I understand addresses have a fixed length. |
|
|
|
|
Ah, es curioso... por lo que veo, el comando "move" cambia la cuenta dentro de un mismo wallet, pero no cambia las direcciones (ya que hacerlo involucraría enviar una transacción al mundo exterior). Por lo tanto, y si lo he entendido bien, este escenario es posible:
- Pongamos que la dirección 1FooBar pertenece a la cuenta "Alice".
- Dicha cuenta presenta un saldo de 2 BTC.
- Alice realiza un "move" para transferir 1 BTC a la cuenta "Bob".
- El dinero ha cambiado de cuenta pero no de dirección, por lo que ahora la dirección 1FooBar pertenece a ambas cuentas "Alice" y "Bob".
- Si Alice envía dinero al exterior, la dirección origen será 1FooBar.
- Si Bob envía dinero al exterior, la dirección origen también será 1FooBar.
Hmm....
|
|
|
|
|
Yo pienso que es muy bonito y tal, pero no creo que los de arriba lo permitan. Por mucho que bitcoin despegue, nuestras empresas seguirán pagándonos el sueldo en euros/dólares/whatever, y si los de arriba se empeñan en tumbar el sistema, no tendremos forma legal de transformar esos euros en bitcoins para comprar el pan.
El tren se acabará estrellando contra algún muro, pero una cosa es cierta: lo hará conmigo dentro.
|
|
|
|
|
Sorry, but I don't get this "Camp BX is US-only" stuff. What prevents me from buying bitcoins elsewhere and then moving them into CampBX?
|
|
|
|
Seems to be fixed.
Yeah, I think you are right. Do you see what happened on the charts while things were screwed up? Err, no... Anyway, I spoke too soon. |
|
|
|
2 times the character “ž”
2 times the character “®”
2 times the character “¯”
2 times the character “»”
2 times the character “Ø”
I would be using some of those fancy Unicode characters from some time now if I wasn't afraid that applications weren't able to handle them properly, thus locking myself out of websites. Coping with Unicode is hard. Off the top of my head, and easily type'able with my actual keyboard setup/layout: — – « » ß þ Þ œ Œ æ Æ ø Ø … |
|
|
|
That is a good idea. Do you think it is important to verify that someone actually owns the address to tag it?
I would vote for it. No one stops me from using the vanity patch for creating an address that starts like Wikileaks' one, then registering it at firstbits as "Wikileaks donations address". Besides this, I don't know much about namecoins but registering an address to a name may fit namecoin's purpose quite nicely. I understand namecoin is no more than a set of "A --> B" relationships. |
|
|
|
What we really need is an online wallet with firstbits integration. Right now the best way would be to put some money in an instawallet, get the merchant's firstbits, go to firstbits, copy the address,paste in instawallet and pay. But if installawet could translate on it's own then it would simply be: go to instawallet, start typing the address, it gets completed for you and you pay.
I was thinking about this too. It would be great. |
|
|
|
sometimes you see funny patterns ...  Hey did you actually see that? xDD |
|
|
|
|
Show Posts
