Nice idea. A few randomish thoughts: 1. Better site structure. Have these four links across the top (where it currently says "home"). - Home -- Say what it is, answer one or two top FAQs, and have a list of the 5 most popular bounties
- Bounty List -- Main listing of all bounties. Can be filtered/searched by name, bounty amount, etc
- FAQ / About --
- Account / Settings -- Show the email you registered with, allow changing password, etc
2. Better navigation. Add a breadcrumb under the navigation that holds all items. For example, if I'm submitting a solution, the breadcrumb should be: Home > Bounty List > Some Project > Submitting a solution 3. Have the "Add a bounty" button at the top in the header. 4. Have a way for the original bounty creator to edit the title/description of the project. Allow anyone to view previous versions of the title/desc. 5. Have a comment thread for each bounty for others to ask questions, clarify, make suggestions to improve the bounty, propose/discuss solutions/implementations. 6. Have a way for users to mark that they are working on a given bounty. You won't prohibit multiple people from working on the same bounty, but it would be helpful to see a list of how many people (and who) are working on the bounty. Have a comment thread for each of the people who are working on the bounty to clarify what they are doing, their progress, etc. Have a way to show how active the person is who is working on a bounty. For example, show the last time they logged on or commented, etc. 7. If you mark that you are working on a bounty, have a field to enter your progress. 8. When viewing a bounty, show who is working on it and what their (self-reported) progress is. 9. Have weighted voting on who wins the bounty after a solution(s) is submitted. Have weighted voting where the bounty starter and people who contributed more BTC to the bounty have most of the say, but let other users of the site also have a small vote. Have a comment thread for each proposed solution to discuss it / clarify problems. Allow the person who submitted the solution to revise/re-submit, etc. 10. Have a way to close bounties that are no longer wanted. ------- What language is the site written in? I'd be happy to do a code review for you if you want to post/send a zip file with your code. |
|
|
|
I have proposed sweepprivkey on the Wiki, which I believe will become the fundamental underpinning for redeeming Casascius coins and any other kinds of physical bitcoins.
With that function properly implemented, redeeming Casascius coins can be as easy as using a Javascript redeemer that initiates a sweepprivkey on a hosted service. And fortunately, I have seen posts from Gavin suggesting he understands that sweepprivkey is an important function, possibly more so than importprivkey (this was in a discussion about importprivkey). That right there will probably be the biggest ticket to widespread redeemability.
Found the wiki page. Thanks. Sweepprivkey looks like a very useful piece of functionality, much more so than importprivkey, since it would also allow the user to redeem their private keys (without importing them). |
|
|
|
The online services are vital and have a lot of potential, but there needs to be a basic way to import into a simple client.
Bottom line, private key importing needs to be in the default/official client. And the sooner the better. |
|
|
|
I'd prefer that approach, since I don't really trust arbitrary websites. It might secretly remember the private keys of the generated addresses and its operators might decide to cash out as soon as a certain amount of money is stored on addresses generated by them.
bitaddress.org is designed so that you can download the HTML/JS file(s) and run them on an offline machine. It's all done in Javascript client-side and nothing goes to the server. |
|
|
|
I think you should stick to 0.1 btc. I would buy at least 100 of them if not more. And you should preload them all. Doesn't make sense for people to load them themselves.
And please put on your website information for people who received these coins and just googled casascius.
This. Is there a website that explains in detail how one actually redeems the BTC from a coin? Somewhere we can refer coin recipients to?
+10 Do you mean something more detailed than go to MtGox, click "Add Funds", and choose "Redeem Private Key"? The alternative involves patching source code and is a billion times more difficult. It's out of reach for the average user. StrongCoin has been mentioned already. pywallet might be another option. |
|
|
|
it was virwox i sent them 50$ and then switch to get it to sll and then to btc should i email them? i was spouse to get 23 or 22 btc
* Paypal takes its fee from the $50 * You can only buy whole dollar amounts of SLL (you're left with some USD change in your account) * You can only buy whole BTC amounts with your SLL (you're left with a bunch of SLL in your account) * VirWox's exchange rate is not the best Add those all up and you're easy paying $4 USD per bitcoin (based on your original Paypal deposit). For $50 you should somewhere in the neighborhood of 12 BTC using VirWox. |
|
|
|
TLDR: this patch allows you to:
- see all addresses, including change
- see which addresses are linked together (does recursive expansion of address linkages)
- select which address(es) to send from, rather than letting the client to chose for you
Very nice. I hadn't seen this before now. why conflate the two issues?
Because to non-technical users, "privacy" is a single feature, not a series of separate technical issues. You have an excellent point about how non-technical users view privacy. But you have to take a series of small steps to achieve a larger goal. In privacy mode, Google Chrome lists several ways your privacy could still be compromised, yet that didn't keep them from adding privacy mode. This patch should be added to the official client, but will obviously not be the last privacy-related improvement to bitcoin. I updated the code for 0.4 but never released builds since I didn't perceive any demand for them. The code is now updated for the 0.5 qt gui so once 0.5 is officially released I'll release builds with my patch as well.
Awesome. I'll patch 0.5 when I start using it. |
|
|
|
i payed 50$ and only got 15 btc  were is my 10 or so btc  Who did you buy from and what was the agreed-upon exchange rate? |
|
|
|
|
I don't want to get pulled into arguments, but IMO, bitcointalk.org should have some level of professionalism, and at the very least should be SFW.
|
|
|
|
Litecoin anyone?  Sure. |
|
|
|
Likely too many. SMS is limited to 140 bytes. A "standard" Bitcoin transaction is going to be 800 to 900 bytes. Compression isn't going to help much (if any) as the largest components are the signature and addresses/keys. Hashes are indistiguishable from random data and thus aren't compressible.
The raw transaction can be compressed. For example, the transaction posted above is 808 bytes. If I gzcompress it, then base 64 encode (so it can be represented as printable ASCII chars), I can get it down to 488 bytes. The raw transaction above is 404 bytes. Two hex digits make a byte. All of the compression "gain" you are observing is merely a result of compressing out the additional space taken up by converting the binary to text. Try compressing the 404 bytes. Oops, I'll have to try again. Edit: gzipping and base 64 encoding the original binary transaction (404 bytes) yields 460 ASCII chars. That probably about as good as it's going to get without modifying what information needs to be sent. |
|
|
|
What can you actually do with 0.1 bitcoin? Is there any way to spend or withdraw such a small amount? If it's not a usable/transferrable amount of currency, I don't really understand the point. If you think people will become "invested" in BTC when you give them half a postage stamp's worth, that's not the way the world works.
It's a token amount to start a conversation / get them interested. |
|
|
|
|
Testing the 0.5 client... minor typos and things:
1. On the "Receive coins" screen, when you mouse over the list of addresses, the tooltip says "Double-click to edit address or label". Since you can't actually edit the receiving addresses, the tooltip should say "Double-click to edit label". Be sure not to change the tooltip on the "Address book" screen, since you can edit both the label and the address there.
2. On the "Transactions" screen, when you mouse over the list of transactions, at the end of the tooltip, add "Double-click for more details", since people may not know they can do that.
3. On the "Receive coins" list, why not completely remove the "delete" button instead of just disabling it?
4. On the "Send coins" screen, the tooltip for the address book button is misspelled: "Choose adress from address book" (missing a "d")
Suggestions:
1. Always show the balance on the left side of the status bar at the bottom (regardless of the tab I'm on)
2. On the "Receive coins" and "Address book" tabs, have filter controls at the top to filter the list by label and/or address (just like in the transactions list)
3. On the Send tab, when you choose milli or micro BTC, show the same text as the tooltip to the right of the drop-down box. People don't always leave their mouse still enough to see the tooltips, and a lot people won't understand what mBTC and µBTC are.
4. On the Transactions tab, add a column on the right that shows what the balance was after each transaction.
5. ON the Send tab, add a line right above the "Send" button with text like this: "Sending X BTC, balance after sending will be Y BTC."
Edit: Awesome job on the new UI, it's a big improvement over 0.4.x
|
|
|
|
We need a forum for CCW and bitcoin enthusiasts.
Dude, this is NOT a porn site. Please. Hmm, am I missing something? Bitcoins is pornographic enough. 8D Adding firearms would just put it over the edge. I guess that would be downright decadent. |
|
|
|
We need a forum for CCW and bitcoin enthusiasts.
Dude, this is NOT a porn site. Please. Hmm, am I missing something? |
|
|
|
Somewhat off-topic, but on a new series of coin it would be cool to have the public key inscribed around the edge of the coin (edge-incused), something like this:  |
|
|
|
Likely too many. SMS is limited to 140 bytes. A "standard" Bitcoin transaction is going to be 800 to 900 bytes. Compression isn't going to help much (if any) as the largest components are the signature and addresses/keys. Hashes are indistiguishable from random data and thus aren't compressible.
The raw transaction can be compressed. For example, the transaction posted above is 808 bytes. If I gzcompress it, then base 64 encode (so it can be represented as printable ASCII chars), I can get it down to 488 bytes. |
|
|
|
let me in. Just want to post my paper of a basic P2P work/bc exchange system.
That sounds interesting. And it's here: http://bit.ly/tGgXCHNeed more brains to get it work. Can you describe how the system would work in a paragraph or two? |
|
|
|
|
Show Posts
