|
So it's just both charts overlaid on a relative y-axis? Like the exiting "compare with" option?
|
|
|
|
|
Can you give an example of such a chart (and maybe a datasource)?
|
|
|
|
|
@vladimir: Can we run custom miner software on your hardware + rent a small server to run bitcoind that is close in terms of latency (< 1ms) to the miners?
|
|
|
|
|
1) SSL would require all clients to upgrade.
2) Random TCP ports could be annoying for users running other services on their computers on certain ports when Bitcoin decides to use them.
3) UPnP would really be useful with all those NAT gateways.
|
|
|
|
Maybe we can use the same exponent-style encoding we invented for the URI Scheme for manual user input on the commandline and use raw int64 in JSON? It's too easy to append 9 zeros instead of 8 on a keyboard. RPC results should then return raw int64 values. |
|
|
|
QRcodes seem a lot less convenient to me than just copy/pasting an address between tabs in a web browser and pressing "go". Both Android and iPhone allow web apps to send messages directly to phones for free, so why bother with scanning stuff off the screen?
Even if you didn't use QR codes you could still use the URI scheme to transfer address, amount and a short message to the client. With Bitcoin we don't need bi-directional communication when transferring such payment requests, so it's useful to have one scheme that can be transmitted via different communication channels. Copy and pasting raw addresses will always work, but I think it's important to add extra information so the user knows what he's going to pay for and doesn't need to enter the amount manually, especially on a phone with only a touchscreen. |
|
|
|
The final problem to solve is the user interface problem. Typing BitCoin addresses into a phone is even more awkward than on a PC. ...
What about QR codes to transfer addresses? I use them for js-remote and they work great for transferring coins from/to my Android phone. I'm using the URI scheme from the wiki. |
|
|
|
Also, currently miners don't update the block they're working on with new transactions as they come in. I think that makes the hash search more efficient. So by the time a block is generated, there's already a substantial pool of new transactions to start working on. This too may change in the future though.
The miner in bitcoind itself and getwork based miners update the TX regularly. After all, the whole point of mining is to confirm transactions. |
|
|
|
|
4x rule was considered and actually makes overtaking easier. You can create 5 (iirc) blocks per second (implicit limit in AcceptBlock()). Without the 4x rule difficulty would rise to too high after the first 2016 blocks. With the rule, it will rise to 4 and we can still generate the next 2016 blocks in a short time.
|
|
|
|
I would like insert a private key from QR code. So I could print a wallet on paper and give this paper to another person. He could scan this QR code with an android phone, check the value and transfer the bitcoins to his wallet.
First: Please discuss this in another thread. This is only for js-remote! This is a feature that needs support in bitcoin itself. Once there are RPCs I can add such a feature to js-remote. |
|
|
|
|
Statically linked bitcoind for android is about 4 MB.
|
|
|
|
|
Testnet can be reset within 2 days by overtaking the blockchain. This will reset all balances. I might actually do that this week. Final difficulty will be ~ 0.5 after reset.
|
|
|
|
|
v0.3.1: fix transaction list on firefox
|
|
|
|
|
v0.3 released.
* faster rendering of transaction list
* more responsive on Android
* reduced bandwidth usage
|
|
|
|
One suggestion: I think the license you are using is the MIT license; however neither the files nor the project page mentions, which specific license you are using. Please add the type of the license to your project page and the files.
Fixed (integration branch for now) |
|
|
|
|
Added bitcoin: URI support for QR codes (you can even enter raw bitcoin: URIs if you don't have a Android phone!)
|
|
|
|
|
Show Posts
