<<  >> (p.2)
    Author Topic: Password-protected private key export format  (Read 7676 times)
    2112
    Legendary
    *
    Offline

    Activity: 2128
    Merit: 1089



    View Profile
    August 12, 2011, 09:08:33 PM
     #21

    I'm convinced at this point that the on-disk wallet format needs to be completely scrapped and redesigned from scratch. Unfortunately, I'm not likely to have the spare time to devote to working on this.
    I'll say don't give up on that goal. There may be an incremental way to redesign it.

    1) Create a separate DB_ENV just for the wallet.
    2) Change single B-tree DB into three RecNo DB-s backed by flat-text files. This is quite decently supported by the Berkeley DB, especially because the wallet database is essentially an append-only. The 3 files would be public-keys, private-keys and transaction-log.
    3) I see lot of people here proposing public-key operation only for shared/managed hosts. But I have yet to see anyone discussing proper transaction auditing as done by the accountants. This is why I was thinking about 3 separate databases, the 3rd being the one given to the auditors.
    4) During the transition (and possibly afterwards) the default client will continue to use Oracle BDB as its only database interface.

    This incremental approach could assuage Gavin's worries that the patches/pull would try to surreptitiously change the basic protocol and principles of operation for Bitcoin.

    Please comment, critique, criticize or ridicule BIP 2112: https://bt.irlbtc.com/view/54382.0
    Long-term mining prognosis: https://bt.irlbtc.com/view/91101.0
Page 1
Viewing Page: 2