|
Yes, only for a single key
I plan to add json file support soon though
|
|
|
|
The address version of testnet is 111 instead of 0. Bitcoin sees all address versions lower than its current version as valid. So testnet sees mainnet addresses as valid.
I HAVE to ask for any explanation about that I mean, either devs want any address version is ok for any network (and address versions become useless) or they want exactly one address version par network Why accepting all lower ones but not higher ones? |
|
|
|
|
Backup your wallet, reinstall completely the app, put your wallet again and prey
|
|
|
|
Your namecoin sending wallet is at /home/jackjack/wallet.dat Your bitcoin receiving wallet is in your default bitcoin directory (if not, use pywallet --datadir option) 0. Download my pywallet fork and exit namecoind 1. In console 'cd /path/to/pywallet/' 2. Run './pywallet.py --dumpwallet' and find {
"addr": "The Bitcoin Address you sent namecoins to",
"hexsec": "privatehexkey64characterslong",
"label": "",
"sec": "5xxxxxxx"
}3. Run './pywallet.py --importprivkey "privatehexkey64characterslong" --importhex --namecoin --datadir /home/jackjack/' (if testnetcoins, replace --namecoin with --testnet) 4. Restart namecoind with the rescan flag Your coins are now again in your Namecoin wallet, and you can even use that Bitcoin address as a Namecoin address I hope this will help someone one day |
|
|
|
|
There's one thing I agree with them (I mean the bitcoin-is-serious-business guys)
Some images don't have to be sooooooooooooooooo huge
Going to imageshack.us and have a smaller one takes about 30 seconds
|
|
|
|
|
I managed to compile it but the app seems to crash
|
|
|
|
Am I the only one to see that in his post? |
|
|
|
|
It would be nice to have checkboxes instead of the current one-choice form for the transfer manner
And the error I posted above is also thrown when I try to create a new account
|
|
|
|
What would be the best tactic to buy 25,000 - 30,000 Namecoins without moving the price up to high?
Spread out over a longer time? Or place a big order at a fixed price? Many orders at different prices?
So you want to buy more than 3% of all the namecoin economy without moving the price? Not to much, no. You think I better be patient and spread over 2 or 3 weeks? On Bitparking the volume is currently about 12k, I think that buying about 1k a day won't move much the price if you use the different namecoin exchanges (I believe there are 3 of them) If so, yes, 3 weeks should be enough |
|
|
|
What would be the best tactic to buy 25,000 - 30,000 Namecoins without moving the price up to high?
Spread out over a longer time? Or place a big order at a fixed price? Many orders at different prices?
So you want to buy more than 3% of all the namecoin economy without moving the price? |
|
|
|
Now that e-mail has been hacked, and I have just recovered my access to it.
The hacker, according to gmail, was:
Browser Lithuania (78.58.51.114) Jul 25 (16 hours ago)
Just curious how would you guess they gained access to your gmail account? Trojan keylogger on a system you've used? Lucky guess of the password? Knowing answers to account recovery questions? Bruteforce on the leaked Mtgox accounts file |
|
|
|
jackjack, I see you have a fork of Joric's repo, are you developing pywallet now? For such a handy tool, it's almost being passed under the table. Perhaps it deserves a top-level thread? Joric didn't commit for almost 2 weeks now so I don't know if he wants to continue its development I prefer to bring many improvements available immediately for people that might need it instead of waiting him to accept my pull requests (he looks busy with his new tool). For example my other script that gets rid of 0/unconfirmed tx's needs my pywallet fork |
|
|
|
It must be something along those lines, because it looks like my debits/credits match.
Please keep me updated, I'd like to know if it's useful |
|
|
|
First of all, all I say is what I understood about this project, don't take it as 100% true until Morpheus confirms it  Exchange of fiat money is not solved through p2p-network, here p2p really stands for peer to peer
Ie you send your bitcoins (or even a fiat currency) and the other person sends you what you buy/sell, nothing else involved like in traditional currency exchanges
I see, since the exchange doesn't warranty that the trade is atomic, it may not be even through the internet. The two users will decide. Have you seen my proposal for an anonymous almost-atomic exchange between bitcoin-like currencies? If one of them adapts its code (bitcoin or namecoin), it could be done atomically. The problem is that I don't understand the word 'atomic'. If it means something like 'automatic', then, yes, Dark Exchange (after some modifications) can be an awesome tool to perform automated, instant, nearly-sure cryptocurrencies exchange Thanks jtimon % jackjack Exchange of fiat money is not solved through p2p-network, here p2p really stands for peer to peer
So the p2p-network handles only the bids and serves the personal contacts; pays are done out of the box. Do I understand? The key of my confusion is that I didn't know a word of services like "libertyreserve"... Exactly I don't know libertyreserve either, for now the choices in Dark Exchange are 'Cash by mail' and 'Check or money order by mail', but Dwolla, Paypal, Libertyreserve, or even 'face to face exchange in a Central Park' can easily be added |
|
|
|
git clone git://github.com/bitcoin/bitcoin
cd bitcoin
git remote add sipa git://github.com/sipa/bitcoin
git fetch --all
git diff master..sipa/showwallet
(Warning: I'm a subversion user and haven't worked with git at all) I've followed these steps successfully with 0.3.23 (or maybe it was 22). In the last step I actually did 'git diff master..sipa/showwallet |patch -p1', then 'cd src' and 'make bitcoind' as usual. Funny having to patch things, but I guess that's how git does things. Now, what should I do to update to 0.3.24 without starting from scratch? A quick google revealed 'git pull' but that failed with "Your local changes to 'contrib/gitian.yml' would be overwritten by merge. Aborting". Must I revert those changes (the applied patch, I suppose) before doing 'git pull'? For now I just removed everything and started over, but I'd like to be cleaner next time. Already running "0.3.25-beta"  . From http://help.github.com/fork-a-repo/git remote add upstream git://github.com/bitcoin/bitcoin
git fetch upstream
git merge upstream/master |
|
|
|
|
Exchange of fiat money is not solved through p2p-network, here p2p really stands for peer to peer
Ie you send your bitcoins (or even a fiat currency) and the other person sends you what you buy/sell, nothing else involved like in traditional currency exchanges
|
|
|
|
Look at the source guys, it's worth it  |
|
|
|
|
I think I'll create a new account, it's not that important
|
|
|
|
|
Show Posts
