Nice! Dumb question... is this simplified or traditional Chinese? I'm just starting to learn Mandarin Chinese (Simplified), and according to what I've read, mainland China prefers simplified characters, while Hong Kong and Taiwan use traditional characters.
|
|
|
We definitely need a BTC/RMB exchange. Makes me wish there was open source exchange software...
What are the specifications for this kind of thing? Doesn't seem hard to create the software. This is intentionally a bare minimum requirements list, not a "wish list" of features. - per-user account system (username, password, all the standard stuff)
- maintains internal, double-entry accounting ledger of per-user accounts, where each transaction stores $Amount and $Currency
- supports calling a Web API via a plugin, to receive deposits in $Currency
- supports calling a Web API via a plugin, to send withdrawals in $Currency
- supports manual administrative entries (journal debits and credits)
- supports one or more order books of 'bid' and 'ask' prices, one per currency pair
- supports entry of new orders, and cancellation of existing orders. when a new order is entered, attempt to fill order from existing order book entries.
- Consider your regulatory environment. For example, it seems like limiting withdrawals to $1000/day for US citizens aligns with FinCEN regulatory requirements.
|
|
|
For info: I made little tweak on pool side; it returns json rpc error in case of site maintenance (instead of 500 Server Error and some HTML stuff). I believe this is more correct for miners, but it may lead to errors like 'midstate not found', because on getwork there is simply result:null and some error text.
Just pushed the following to cpuminer.git... commit 9e5a173c3845fb7b5d316b0455352a08847b8c23 Author: Jeff Garzik < jeff@garzik.org> Date: Tue Dec 28 15:22:53 2010 -0500 Improve JSON-RPC result/error checking, and improve error diagnostic output.
|
|
|
MyBitcoin.com is a de facto bitcoin bank. And it is clearly useful to many people.
|
|
|
I pledge 50 BTC towards this bounty.
|
|
|
We definitely need a BTC/RMB exchange. Makes me wish there was open source exchange software...
|
|
|
All I get on Trisquel GNU/Linux is:
JSON key 'midstate' not found JSON inval midstate JSON-decode of work failed, retry after 30 seconds
What does 'getwork' return for you, if you issue it manually? It sounds like there is a problem with your bitcoin client's JSON-RPC server. Maybe password is incorrect, or rpcallowip option is misused?
|
|
|
You're begging for money on a bitcoin forum... but you don't post a bitcoin address for donations? Strange.
|
|
|
also, Kademlia network works fine without kickstarters and other things like this
Do you mean bootstrapping? Kademlia network needs bootstrapping, just like other P2P networks.
|
|
|
SVN is just a way to give crappy CVS a few more years of life. SVN has been on life support from its beginning.
|
|
|
Yeah but i wonder why does it say that transaction size is 1K if currently one transaction takes averagely ~275 bytes of storage ? Does it take more bandwidth than storage or what ?
Don't read it too literally. The fee is per kilobyte, but that does not dictate or say anything about transaction size. The actual formula is nBytes = number of bytes in your transaction (e.g. 259 bytes or whatever) CENT = 1000000 nMinFee = (1 + nBytes / 1000) * CENT
("CENT" is a multiplier used to convert a fixed-point decimal number, such as 50.44 BTC, into a 64-bit number of "nanocoins", 5044000.) So, nMinFee==0.01 for small transactions.
|
|
|
The entire system is not based on encryption, but public/private keypairs, and cryptographic signatures. Each time you spend bitcoins, you are creating a cryptographically-signed transaction that says "transfer 1234.56 bitcoins to public key ABCD." Only the person with the private key ABCD can then spend those 1234.56 BTC.
|
|
|
NVIDIA is geared towards floating point, while bitcoin's SHA256 algorithm wants integer math.
ATI GPUs are better at this.
|
|
|
okay, what else can we do to make bitcoin better?
Start a business, or convince a business to accept bitcoins, or convince a charity to accept bitcoins as donation. Grow the bitcoin economy.
|
|
|
So double spending is possible in general? I can just make 10 copies of my wallet, and buy something worth 10 times my balance?
In general it is not possible. P2P nodes won't accept a double-spend, making it very difficult. See the snack machine thread for interesting reading.
|
|
|
Or in other words, there is no need for everyone on the local coffee shop wifi to know that I'm buying crazy sex toys from MadHatter's new shop. MadHatter's new sex shop should be generating unique addresses per user every few days. That doesn't address the privacy problem described at all. People may observe an outgoing transaction for a specified amount.
|
|
|
Bitcoins are fixed-point numbers stored as integers, so strictly speaking, you're out of luck.
|
|
|
Shell script would be fine for a connect-work-disconnect method of working.
But it is grossly ineffective for maintaining a long-running P2P network node, where long-lasting TCP connections are preferred.
|
|
|
The P2P network needs to support SSL, for enhanced privacy.
For what? As far as I understand all transactions are public anyway, how would you else validate that person x paid person y and prevent double spending. SSL can even be worse for privacy, one part of SSL is cryptography, the other part is verification of identity. My point is, what piece of information do you want to protect? All transactions are public... but their origin network nodes are private to all except the initial P2P transaction receive points. Or in other words, there is no need for everyone on the local coffee shop wifi to know that I'm buying crazy sex toys from MadHatter's new shop. Anonymous SSL on some random free wifi is far preferable to Tor.
|
|
|
Handing out wallet.dat files is just fine. I think it's a great idea. Sure, there is the possibility of double-spending... but only by the person handing out the wallets. Presumably, you trust yourself
|
|
|
|