This ring seems almost custom-made to hide a privkey. If you use the mini privkey format you could actually keep up to 4 on it, though 1 would be visible to the outside world, so in practice only 3. The engraving fields aren't long enough to hold an entire address, though you could definitely fit the firstbits on there. Assuming the firstbits for all 3 addresses are <= 7 characters long you could fit the firstbits for all 3 addresses on the inside of the ring and the firstbits on the outside. 3 complete privkeys and everything you need to make payments to them all on one ring. Snazzy. 
|
|
|
|
|
Also keep in mind that mens rings are usually wide enough to fit 2 or 3 lines of text @ 30 characters each, so you could potentially put up to 90 characters inside the ring and if you got the right material, style and finish another 90 characters outside. It might be wise to use a separator character on each line to show where the characters start and stop, depending on how the engraving works out so 87 inside and 87 out for a total of 174 characters. If you use Bitcoin's standard Base58 encoding that gives you log2(58)*174≈1019 bits for both sides or log2(58)*87≈510 bits - WAY more than you'd actually need for a privkey. Even falling back to hex would give you log2(16)*174=696 bits for a double-sided inscription or log2(16)*87=348 bits, still more than adequate.
Given that the Casascius mini private key is kind of an industry standard though, it's probably best to stick with it for compatibility's sake.
|
|
|
|
Assuming this topic is correct, does anyone happen to have a source of MTBF/MTTF/FIT data for those chips? It's rough trying to factor cost of replacement into operating costs when you have zero data on how often they'll need replaced  That quote is a bit out of date. Due to recent comments by BFL, it appears to be more likely that they have actually produced something custom, possibly a specialized programmable ASIC (I.E., an FPGA of their own). It is becoming less likely that is is actually an off-the-shelf product. So it's looking less likely that we'll actually get time-to-failure data on the chips unless BFL does the testing themselves and released numbers. |
|
|
|
Vote #128 We should start a "Bitcoin already did it" meme a la "Simpsons already did it" - I personally would have phrased the idea "You can use MintChip to buy the other digital currency you're ripping off" but then perhaps I'm a bit militant when it comes to pseudo-plagiarism  |
|
|
|
Assuming this topic is correct, does anyone happen to have a source of MTBF/MTTF/FIT data for those chips? It's rough trying to factor cost of replacement into operating costs when you have zero data on how often they'll need replaced |
|
|
|
14 hours left to buy a ticket! Someone is going to have an awesome Friday! I'll be at the Grand Canyon rafting down the Colorado river tomorrow, so it'll be an awesome Friday regardless. Coming back from that to win a 50Gh mining contract would bump things from "awesome" to "best day EVER." |
|
|
|
|
Find out how many characters a regular jeweler can engrave inside the ring. It might be enough for a mini-privkey format already.
|
|
|
|
We were all in newbie jail at some point and most of us have forgotten how irritating that was.
Except for those of us whose accounts predate newbie jail... |
|
|
|
I can't wait to make someone's day Well you and likuidxd already made my day by buying my 5830s. I guess this is just a chance at buying my own hashing power back * 50 eh? |
|
|
|
Seems to me that something like bitHopper could be tweaked to do this with the timesliced scheduler pretty easily. It's intended for pool hopping but if you disable all of the hoppable pools and just timeslice between the "fair" pools it should have the effect you're after. |
|
|
|
Four more tickets sold |
|
|
|
|
You technically wouldn't need a 2nd entire PirateBox, just a wifi extender, which a lot of routers can be configured to act as with the right firmware. If it can run the PirateBox firmware it can probably run dd-wrt/openwrt/tomato etc and act as a range extender. Theoretically, since the PirateBox firmware runs over the top of one of these firmwares (openwrt I think?) it should be possible to configure it thusly, though the menu options associated with such a configuration might not be present.
|
|
|
|
Also can't wait to get out of newbie status on this board. Been reading following for almost a year, but this is only my third post. I think I know enough finally to be useful on other boards.  Shameless plug: don't forget to be useful on the Bitcoin Stackexchange too ;-) |
|
|
|
Is this the same as the one you posted in the other thread? You are already on the list...currently 3 from the bottom.
It is, I noticed the new thread and didn't know who was maintaining them. Sorry for the cross-posting. |
|
|
|
|
Ordered Apr. 20
Confirmed Apr 21
Quantity 1
|
|
|
|
|
Ordered: 4/20/2012
Confirmed: 4/21/2012
Shipped:
Qty: 1
|
|
|
|
|
I've received funds and the transaction has been confirmed. Thanks for the purchase likuid and thanks kluge for providing escrow!
|
|
|
|
Don't be lazy, at least use actual data...  7 day SMA. It's a little tough to see the takeoff/selloff/beartrap regions, they sort of got flattened by the $31 peak |
|
|
|
|
Is there any MTTF/MTBF/FIT data available on these? Has any such testing even been done? If not, is there any word on the exact components being used so we could find MTTF/MTBF/FIT data on the components at least?
|
|
|
|
|
Show Posts
