Although still under redesign at the moment CIYAM Open ( http://ciyam.org/open) is a very different approach. Rather than aiming to fund a whole project it works on funding specific tasks (and is actually designed to help Project Managers). The slideshow at http://ciyam.org (takes around 5 minutes) steps you through the process.
|
|
|
Hope it's not too complex to implement. Not being a programmer, I come up with a lot of those.
Actually "hashcash" which is the algorithm that Bitcoin itself uses for PoW was invented for *exactly* this purpose but it has never really taken off. I am guessing it would not be too hard to add hashcash to some sort of spam detecting "plugin" software for major email apps (for those interested take a look at https://github.com/ciyam/ciyam/blob/master/src/hashcash.cpp to see how the basic idea works) - if there is a suitable open source C++ mail plugin project in existence then for some BTC I'd be prepared to give it a go. (as this is rather OT feel free to PM about this) I don't see much benefit in using something as complex as OT for a simple "unsubscribe" and presumably any responsible organisation should be happy to remove members from their lists (so no need for any contract).
|
|
|
Bank wire to Bitstamp wasn't that difficult, actually.
Indeed - provided that you aren't wanting to only buy a small amount of BTC then bank wires are the best option.
|
|
|
the fee came automatically 0.0005 from my android wallet
Aha - you might consider reporting this to the software vendor.
|
|
|
Unfortunately there is no way to add a fee to an existing tx (yet) so you will just have to be patient.
BTW how did you create the tx (as most standard clients should have calculated the correct fee for you)?
|
|
|
Agreed the fee should have been higher so it may take quite a while longer.
|
|
|
What is Open Transactions, sorry?
To quote from the github project: Open-Transactions democratizes financial and monetary actions. You can use it for issuing currencies/stock, paying dividends, creating asset accounts, sending/receiving digital cash, writing/depositing cheques, cashier's cheques, creating basket currencies, trading on markets, scripting custom agreements, recurring payments, escrow, etc. Open-Transactions uses strong crypto. The balances are unchangeable (even by a malicious server.) The receipt history is destructible. The transactions are unforgeable. The cash is untraceable. The cheques are non-repudiable. Etc.
https://github.com/FellowTraveler/Open-Transactions
|
|
|
I would suggest looking into what is going on with Open Transactions and its recent integration testing with BitMessage.
If this is packaged well then I think it could well be the "next big thing" (and it doesn't require XRP).
|
|
|
This is not possible, if you take all of your money out of banks and store them locally, banks will all go bankrupt Well actually due to Fractional Reserve banking all banks are "by their very definition" bankrupt. Like others I am very much looking forward to seeing where this leads.
|
|
|
I bought my first bitcoin from Jeremy. I stopped pretty quick when I discovered I was paying about Gox+10%. Still, I have no complaints against him.
Yup - unfortunately it isn't an easy thing to buy bitcoins at a price that isn't well over Gox unless you are able to trade person to person.
|
|
|
I can attest to the Canon camera problem (my Ixus which is otherwise a great camera now has a lot of trouble with its MiniUSB and I don't use it that much).
|
|
|
Brainwallet is offline. You just save the complete webpage and copy it over to your offline machine. I noticed he's added multiple output addresses as well. The only thing it's lacking now is multiple input addresses and I don't know if it can calculate the proper fee.
It does not work offline for raw tx's as it cannot determine the inputs (you need a blockchain for that). It also cannot calculate a correct fee.
|
|
|
Could this not be fixed with newly generated public-keys every time a transaction takes place? Similar to when you generate a new wallet on bitaddress.org.
Indeed it is best practice to generate a separate address per tx but of course you still have to trust that whatever address you are presented with *does* belong to the site you think it does.
|
|
|
There is work in progress to tie public address generation to CA certificates for commercial sites (am not sure how that has progressed so far but it is likely to be appearing in the next major release from what I gather).
Another perhaps less satisfactory solution is already available via the use of "firstbits". As an example you can go to blockchain.info and type in 1ciyam to find my project's public address (assuming you trust blockchain.info to show you the correct one).
|
|
|
Some tools to help brute force passwords from partially known ones have been developed on the forum (you might try searching a bit to see if you can find them).
|
|
|
Yes - I see the problem now - and the point of the OP (which is an interesting one).
It could well be that the only way you can be certain that you do "own" the UTXO in that case would be to actually "spend" it (had never really considered M of N with M as 1 as *being* an M of N tx but I guess it could make sense - especially if you are wanting to be very tricky).
|
|
|
I am pretty sure that listunspent will only include tx's that the client knows it *can* spend (i.e. has *all* the required keys for) but unfortunately I don't have the time to check for this in the source (perhaps this could be moved to Technical Support to get a definitive answer from a dev?).
|
|
|
while( i ) { do{ !care, if( u || someone ); else break/*s*/; //convention } while( replying );
if( bit_coin == BitCoin ) //then the conversation could break; //down } //into sillyness
|
|
|
I guess some people are just so used to CamelCase.
Hmm... think I might have to start my own meme (for the older programmers): bit_coin
|
|
|
This is the Beginning of the Beginning for BitCoin and CC's as whole
Just one thing - what exactly is Bit Coin? (this incorrect caps version seems to be becoming a meme of its own)
|
|
|
|