I have build btcprice.info which does alerts and price quotes in several countries. Expanding to 100 countries next month. All free..
The code I have has been tested to be able to deliver thousands on SMS in less than a minute, so the alerts are not delayed.

I'm looking for help, so if the original poster wants to collaborate, drop me a line.

Ah, thanks. I did not know that. Ok.

EVERYONE: We are printing the key PREFIX on the note. Not firstbits, that was a misunderstood term. Ju.st the first 6 characters



Well, I needed to understand the assumption behind it. At first, I did not understand the issue with "firstbits" because I was using the term incorrectly.


I was hoping to have one standardized template, multiple designs, since the template is affected by the code.

If people think we need a second, more compact template, one that has lees space for design graphics, and is more utilitarian, then we should add another template. We'll have an option in the code to pick layouts and designs.

I would like to think that the template I suggested could be used for a variety of designs, some a lot less like "money". The shape and size however are a matter of convenience for physical wallets, envelopes etc, not just copying money.


Yes, it is exactly like a ticket receipt/stub. It is intended to offer a smaller, compact backup copy of the keys. In a way, the stub is very much like your layout: compact and utilitarian. The template I proposed essentially prints a wide note and a compact copy of it on one row. The stub is to be kept in a different location.

As for the "print 2", it is possible, but more expensive than a smaller backup stub. I think people want nice graphic designs, so they want something a bit larger than your template for the main design, but also want a compact backup. That's why the template has two sizes on it.

I could be wrong of course. I really am open to suggestions, so I want to hear from more people on this!

Thanks for your feedback!

here's an example of the output from jonis' tool:

Where? Is this on the dev mailing list? Or IRC?

We have a code contribution from a new user (jonis) who has not even been able to exit the Newbie section, but has been following with interest.

The code prints onto acorn's template. It is a great start for the code that will be part of openpaperwallet

Many thanks to jonis. If an admin can make the whitelisting happen, please do!

Code: http://jonls.dk/wallet-kit-addresses/

I received the security stickers today. These are the 1" x 1" security scratch-off that will be applied to protect the private key.

The image below shows one, used on the traditional paper wallet design. Since the private key space is a bit bigger than 1" x 1", I applied it to the public key (yes, I know there's no point in protecting it, it's just for visual demo)



As you can see, the bottom of the sticker is plastic coated so that when you scratch it off, you don't damage the print underneath. In fact, it keeps the key protected from water and other damage too. They cost only $0.05 if bought in a 1,000 roll, less for bigger orders.

On behalf of user jonis: https://bitcointalk.org/index.php?action=profile;u=88199

He is contributing code for the OpenPaperWallet project: https://bitcointalk.org/index.php?topic=155847.0;all

but cannot post it, as is newb. They sent me PM.

Please fast-track whitelist of jonis, they are contributing value already

Thank you

I have to admit I did not understand the post above.

When I was referring to first bits, I was simply referring to showing the first few characters of the PUBLIC key in a slightly larger font, so that the note can be identified at a glance when held in a stack of similar notes.

So if the public key for the bill is: 1GE6KGzNwrh9tasmA4x15orsGr6eojh3dX, we print a QR code and this text in the blank space. Then we print the first few characters of the same text in a larger font on the front, like GE6KGz (6 characters).

There is never any IP connection or anything like that.

I may be missing something.

Could you PM me with a time and timezone (of the alert, or of the re-registration), so I can find it and debug?

Thanks for the report. Certainly has been a good 48 hours for testing the volatility alert. I've had triggers in the entire range from 2-7%.

If it is bothering you while I debug you can reply "cancel" and that will stop it and delete your phone record. Then you can re-register with whatever setting you want.  I designed it so the cancel command bypasses all normal ops and directly removes all traces of the record.

I think it is very much the problem. Look at the attitude displayed from the very get go, on a thread where someone is contributing code.

Insular is the perfect description, of that response, the attitude of some of the devs and the resulting code.

Where in the spec does it say what the maximum nodes should be? Oh, right - there is no spec. Just the "normal node software".

You're the CI/jenkins tester for bitcoind, right? Thanks for that, it's a very important contribution.

I am surprised you would discourage code contributions in other languages when the current network is so dangerously mono-culture and susceptible to major problems because of bugs. It seems to me that bitcoind does a fine job DoS-ing itself every now and then, and that fact that there are no alternative clients may have something to do with it.

Insular attitudes make insular code which makes fragile and brittle code.

As I said, this will all be open. So, your design can be added to the collection at any time. In fact, I hope we will have dozens and dozens of designs in a dropdown selection, in the printing software (derived from bitaddress.org probably).

Please do stay and contribute,
Perhaps some rich bitcoin early adopter will jump in and add to the bounty - OPEN CC-BY-SA license - if anyone pays, we ALL get to use it.

Starting on Monday, the openpaperwallet will be crowdfunded on two major crowdfunding sites. Early contributors will help launch the project and will get paper wallet kits in the mail from the very first quality production run. I will also be giving bigger rewards including reseller kits from my print runs for those who want to jump start a reseller business (100 kits, ready to sell, wholesale price, shipped worldwide).

The funds raised will be used to finance the open source code, web design and many more wallet designs. So don't go away ;-)

I suggested recently that the 8.1 patch be evolved (which hard codes certain parameters for all clients), is evolved into a schema validation engine for the protocol and transactions, so that the behavior of the node and client has prescribed and defined edges, defineed by a computable  definition.

Different words form yours, same basic concept - a core interpreter that validates protocol and transactions and is the agreed, reference, signed implementation that is authoritative for testing, QA, interop and attestation of client validity.

It should be run on testnet, ok. But DoS? Come on!

This is working bitcoin code in a language that scales massively and you're looking the gift horse in the mouth.

If someone wants to DoS bitcoin, there are far easier ways to do it, all of which won't succeed or do much for long. None that involve this much coding effort.

It will either have a repeating pattern on the entire back of the sheet, or designers can submit two sided designs, which need to have elements that obscure the opposite-side QR from showing through, or being copied with a photocopier from underneath.

For example, a spirograph, mandala, "seal", or other pattern, positioned and with darker ink, will sufficiently mangle the writing showing through the paper.


Overall, I'm open to design suggestions. I would like to be able to support a range of needs from:

- Plain 80mg paper, on color laser or inkjet for home use. Essentially, a contribution to bitaddress users and code
- Some might prefer gloss, so consumer inkjet/laser photo paper, still home use, but slightly better quality -

My personal taste is more for matte finish.

Ideally a heavy weight, resistant to curling. Depending on the design, if it doesn't have micro-printing features (which are not really necessary), then a slightly more porous, fibrous, cotton based paper will work too (wove,laid,linen), even if it bleeds a bit, as longs as the design isn't too fine.

Summarize:

Sides: Both, pattern or design
Finish: Matte
Texture: Wove, Linen, Laid or Coated
Weight: Bond #28 or heavier, Text #80 or heavier, or possibly some specialist Tag or Index type. (not Card)
Opacity: 100% or Highest
Brightness: Medium-Low
Archival Quality: High (resistance to yellowing)

The exact brand and model will depend on local suppliers.
Something like a New Crown Plus Matte Cover or Bond will probably exist widely, in a variety of weights and brightness.

Sorry, I meant "below" or "around", not under. Y axis, not Z.

  [QR]
kkkeeyyy

or

kkkkk
[QR]ee
yyyyy

He is impressed when people know about and try to use erlangOTP. Heck, I'm impressed too.

Working code. That's all that matters. The rest is only a matter of time. Thank goodness Linus didn't say: It's only a floppy driver a screen driver and a kernel that keeps crashin, I'd better not show it to anyone until it's "ready". I downloaded that "piece of shit" in 1993 on 210 floppy disks. I hear Linux turned out ok.

Very nice!

I launched btcprice.info last week which does voice and SMS prices and alerts.

We should compare notes!

I was planning on having the full base58 keys: pub and private printed text under the QR code, inside the blank squares. Not in a new area.

I want to keep the number and size of the "blanks" limited to allow for maximum design space. If we can fit or extent the squares a bit, so as not to add another area, that would be best I think...

Once the template is done, we could demonstrate all the variations of models that can be printed. If we call the areas A-F for example, we could have a note that prints like this:

-Note with stub: A=pub, B=priv, C=firstbits, D=blank, E=pub, F=priv
-Note without stub: A=pub, B=priv, C=firstbits, D=blank, E=blank, F=blank
-Wide note: A=pub, B=blank, C=firstbits, D=blank, E=priv, F=blank
-Stub only: E=pub, F=priv, all else blank.

So for example, your design is the first one. 75RTUGA's is the second (traditional style?). No one has done the other two.

One engine, one template, 5-6 possible layouts, hundreds of designs.

This is a great idea.

I am not familiar enough with 2-of-3. I assume it is simply the special case of the m-of-n signing primitive.

Can you advise on how this would affect the layout? What would be printed on the note? We can certainly adjust the software later, but the design and template will need to be able to adapt to it, so we have to get those "right" now.

Advice? I think this is a critical idea...