From: grarpamp <grarpamp@gmail•com>
To: "Michael Grønager" <gronager@ceptacle•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Announcement: libcoin
Date: Wed, 1 Feb 2012 18:50:57 -0500 [thread overview]
Message-ID: <CAD2Ti29cto8wS1jO5yOkORbE48c+t6Of2vysXcA0xM9LKCOCgg@mail.gmail.com> (raw)
In-Reply-To: <54950761-EBFB-402E-8D7B-0B54A08260D2@ceptacle.com>
> However, I think perhaps the bitcoin project should be split into a library, with a prototype client and the actual clients. This library facilitates this.
I'll be trying your implementation soon. And libbitcoin/subvertx too.
Partly because they're also non-interpreted, and partly to what seems
better architected...
To the minimal extent of my understanding... I'd like to see wallet
ops completely separated from background chain ops. ie: have
a chain daemon doing it's thing, updating, verifying, etc. The
generator doing it's thing. And a wallet app that can independently
manage separate wallets in parallel, referencing the live chain files
as needed. It seems a library would allow quality focus on the separate
functions and let apps/ui's use the fn's as desired on top. Right now, it
seems I have to run bitcoind and can only deal with one wallet at a time,
having to stop it, deal with state issues, swap in a new wallet, start
it, and repeat till illness ensues :( And when the chain is being processed
hard by the daemon cpuwise, bitcoin RPC takes minutes to respond, if ever
or errors out. If wallet ops or statistical queries on the chain need it for
integrity or reading, a db checkpoint/lock/logroll could be implemented into
the chain demon processes with a client lib api to trigger it as needed.
Don't know, just saying.
fyi... boost 1.48 and db 4.8.30 work fine with 0.5.2, 0.5.x, and master,
you just need to compile and include it by hand if you want it and
your package manager doesn't have it.
next prev parent reply other threads:[~2012-02-01 23:51 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 14:18 Michael Grønager
2012-02-01 14:59 ` Gregory Maxwell
2012-02-01 15:50 ` Michael Grønager
2012-02-01 16:06 ` Jorge Timón
2012-02-01 15:02 ` Wladimir
2012-02-01 15:52 ` Michael Grønager
2012-02-01 15:09 ` slush
2012-02-01 15:57 ` Michael Grønager
2012-02-01 23:50 ` grarpamp [this message]
2012-02-02 8:32 ` Michael Grønager
2012-02-02 11:34 ` Craig B Agricola
2012-02-03 0:19 ` Pieter Wuille
2012-02-03 9:52 ` Michael Grønager
2012-02-01 15:26 ` Luke-Jr
2012-02-01 15:58 ` Michael Grønager
2012-02-01 16:15 ` Luke-Jr
2012-02-01 16:21 ` Michael Grønager
2012-02-01 16:23 ` Aidan Thornton
2012-02-01 16:20 ` Michael Grønager
2012-02-01 16:23 ` Luke-Jr
2012-02-01 17:37 ` Luke-Jr
2012-02-01 17:51 ` Michael Grønager
[not found] ` <CAAS2fgSQZ1wv=OXnBnGbKnLTZXbn909umpPBaZDF2g6vy8katA@mail.gmail.com>
2012-02-02 17:12 ` Gregory Maxwell
2012-02-02 17:36 ` Gregory Maxwell
2012-02-02 17:46 ` Gregory Maxwell
2012-02-23 17:31 ` Martinx - ジェームズ
2012-02-23 19:48 ` Michael Grønager
2012-02-23 20:01 ` Michael Grønager
2012-02-23 20:35 ` Michael Grønager
2012-02-23 23:29 ` Martinx - ジェームズ
2012-02-24 2:17 ` Martinx - ジェームズ
2012-02-24 7:44 ` Michael Grønager
2012-02-24 16:17 ` Michael Grønager
2012-02-24 18:49 ` Martinx - ジェームズ
2012-02-24 19:40 ` Michael Grønager
2012-02-24 19:57 ` Michael Grønager
2012-02-25 2:11 ` Martinx - ジェームズ
2012-02-26 17:57 ` Michael Grønager
2012-02-27 19:03 ` Martinx - ジェームズ
2012-02-27 21:03 ` Michael Grønager
2012-02-28 9:03 ` Michael Grønager
[not found] ` <CAJSM8J15LBiT9ojrPDE1-TXqmBLXcVvAmWw0e=5nQfLtMQ42Zg@mail.gmail.com>
[not found] ` <8CEEE576-37DF-4101-9593-73D5FB66D52F@ceptacle.com>
2012-03-22 10:48 ` Martinx - ジェームズ
2012-03-22 11:34 ` Michael Grønager
2012-03-28 7:59 ` Martinx - ジェームズ
2012-03-22 10:50 ` Martinx - ジェームズ
2012-03-22 11:35 ` Michael Grønager
2012-03-22 16:34 ` Peter Vessenes
2012-03-27 9:58 ` Martinx - ジェームズ
[not found] ` <B4616B21-7C05-4793-8452-376EE4122BEC@ceptacle.com>
2012-04-15 4:32 ` Martinx - ジェームズ
2012-07-16 20:14 ` Martinx - ジェームズ
2012-09-12 23:27 ` Martinx - ジェームズ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAD2Ti29cto8wS1jO5yOkORbE48c+t6Of2vysXcA0xM9LKCOCgg@mail.gmail.com \
--to=grarpamp@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gronager@ceptacle$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox