I wouldn't mind travelling to Asia, my biggest problem is my food allergies/picky-ness.. I am allergic to ALL types of nuts, and all sea-food.. and I refuse to eat pork and beef haha....
Well if you can handle lamb a very popular snack/meal here is called "yang rou chaunr" (羊肉串 http://www.echinacities.com/expat-corner/guide-to-street-food.html) - it's BBQ lamb on sticks (can buy in the streets and in restaurants and usually only 2 RMB per stick). As it is warming right up now (around 30 C during the day) it's perfect to mix some BBQ with cucumbers, cherry tomatoes and beer! ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
To import them fast I did the following : ...
Thanks for the tips! I was hoping there would be an easier way but guess I'll at least by skipping the rescans for each address it shouldn't take me too long to sort it out.
|
|
|
So is there anyway to change the account for a specific tx?
Am guessing by the lack of response there is no direct way. ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) So is the only option to export every receive address, create a new wallet and import them back in (something that will take a long time as I understand it will do a rescan on each key import) ![Huh](https://bitcointalk.org/Smileys/default/huh.gif)
|
|
|
I used the "sendfrom" expecting it (incorrectly now I know) to use the BTC from the receive address I had previously issued a "setaccount" for (instead it picked some other address not visible in the GUI).
What I am now wanting to do is to stop "listtransactions" from showing that particular "send" as belonging to that account (well more basically what I am wanting is for "getbalance" to match the balance that I see in blockchain.info/blockexplorer.com for the address I did the "setaccount" on in the first place).
So is there anyway to change the account for a specific tx?
|
|
|
I took a good look at the diff ( https://github.com/gavinandresen/bitcoin-git/compare/master...noprivacy#diff-0) but (due to my lack of understanding) can't see how this causes problems with accounts and listtransactions - if it's not too much trouble could you give me an example of the kind of problem it introduces (so perhaps I can try and consider coming up with something similar that won't have the same problem)?
|
|
|
Thanks Gavin - I will take a look at that patch (although I really hope something that accomplishes this can get into the core code).
|
|
|
Let me try to further explain why I want this feature (and I really don't care exactly what form or exactly which RPC command is modified to support it) - I am wanting to use the blockchain as a "true" ledger for a specific address (i.e. that can be publicly audited without having to try and chase up "change" addresses and without using inputs from any other address).
I am so far surprised that no-one seems to be interested in this (for things such as Bitcoin100) and (if the feature actually does get added) will be creating a "project management" package for the CIYAM software platform that will integrate with bitcoind to work with such "non-anonymous" addresses.
|
|
|
The code for Diaspora is OpenSource (and written in Ruby, which means comparatively easy to read), so the chance of someone slipping a backdoor in there is slim.
True - although the initial release (perhaps a little rushed) apparently had huge security holes (hopefully most of those have now been addressed).
|
|
|
I think a better solution would be to have the send from address option added to sendmany, its basically what I do in the GUI when I want to control the change, just add yourself as a second recipient and calculate the exact change.
Haven't really looked into sendmany yet but if it will do the job then that would be fine also (am only wanting the functionality), however, calculating the change manually (and the fee?) is not really what I'd want to be doing (in my case I actually just want the sendfrom and changeto to be the same address).
|
|
|
it's 3 "r"s man, come on!
Oops - fixed the topic. ![Embarrassed](https://bitcointalk.org/Smileys/default/embarrassed.gif)
|
|
|
A very good idea - I have also started creating a similar sort of application with the CIYAM platform (one thing that really worried me about Diaspora from its start was reading that Mark Zuckerberg was by far the biggest donator to the project).
The approach I am taking is to actually send all content AJAX style encrypted over a plain HTTP connection (as HTTPS is blocked in some places as can the use of specific ports but rather tricky to block HTTP). Am yet to work out how to handle files/movies but images are fairly simply handled as raw data.
|
|
|
I'm not a meat eater anymore, but I think I'll have to open an exception while in China!
Am I going to find trouble with this food restriction issue?
It can be a little tricky to avoid meat here, however, we do know of a few quality vegetarian restaurants that are around the Lama Temple area. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
Short term rent is certainly possible - if you are going to be staying in Beijing then the easiest way to find short-term rental (and maybe even a bicycle for sale) is to check out http://www.thebeijinger.com/ (for other cities there are other such expat websites). Understand that legally you cannot work in China whilst on a tourist (or even a business) visa. Be aware that getting a deposit back for the accommodation can be a problem (maybe worth offering a bit extra to not pay a deposit at all). Cheers, Ian.
|
|
|
I understand that coderrr's branch provides control over the addresses chosen to "send from" when performing a "sendtoaddress" and changes the RPC for "sendtoaddress" to the following:
sendtoaddress <bitcoinaddress>[:<sendfromaddress1>[,<sendfromaddress2>[,...]]]
From the perspective of being able to control the addresses I think it should also be possible (at least through RPC) to optionally specify the address to send change to. Syntax of the RPC command could be as follows:
sendtoaddress <bitcoinaddress>[:<sendfromaddress1>[,<sendfromaddress2>[,...]][;<changeaddress>]]
Also - any ideas when/whether the coderrr branch will be merged into the main trunk?
|
|
|
No - the patch is really meant for people who want to control which addresses are associated for anonymity reasons. It still sends change to new addresses.
oic - a pity no option for that as that would have made things extremely simple. You can either sweep the change back to your named addresses, or you might want to look at Electrum.
yup - will have to mull over this - thanks again for the helpful info!
|
|
|
Thanks (should have kept reading a bit more ![Embarrassed](https://bitcointalk.org/Smileys/default/embarrassed.gif) ). I guess the only other thing (which I'll just assume has probably also been covered by this fork) would be to make sure that the change goes back to (one of the) address(es) that were sent from also. I hope this will get merged soon as I think it will be very useful for being able to create more public ledgers (only as an option of course).
|
|
|
Yes, the coderr fork (the one I linked) does it. The patch will probably eventually get merged into the standard client. Electrum can also do it.
Didn't read the entire thread but from what I gather it is a GUI only change (right?) - any proposal to do this with bitcoind (I would want to have this automated to fit into a project management application I am envisaging) ![Huh](https://bitcointalk.org/Smileys/default/huh.gif)
|
|
|
Yes I had read that - but it provides no details about what a sendfrom actually does (about the same as using "bitcoind help sendfrom").
|
|
|
sendfrom sends from an account, not an address. Accounts are just internal ledgers in your wallet. They do not map to addresses.
Thanks - yes thought it was something basic - I got confused by those accounts again (I'll get it right eventually). ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Has anything further been considered in regards to this or is there an alternative client that already does this? (the thinking is to have a publicly verifiable ledger via the blockchain that will show all "donations" and "payments" for an open source project)
|
|
|
|