From: Jeff Garzik <jgarzik@gmail•com>
To: Jeremy Rubin <jeremy.l.rubin.travel@gmail•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Defining a min spec
Date: Fri, 3 Jul 2015 06:55:30 -0400 [thread overview]
Message-ID: <CADm_WcYJ0=cSMo3xB+zT6pmxX0y6_uKpRgn1Jkq997Siev0grw@mail.gmail.com> (raw)
In-Reply-To: <CAJ+8mEOrO3ZvKCiTsX7VzF5Lwug+QE7x+k2EP1nQeqzSuK7AtA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
On Fri, Jul 3, 2015 at 1:33 AM, Jeremy Rubin <
jeremy.l.rubin.travel@gmail•com> wrote:
> Moxie looks fantastic! The reason I thought RISC-V was a good selection is
> the very active development community which is pushing the performance of
> the ISA implementations forward. Can you speak to the health of Moxie
> development? Ultimately, ensuring support for many open architectures would
> be preferable. Are there other reasonable open-source processors that you
> are aware of?
>
> I would be willing to work on a design a Bitcoin specific open-hardware
> processor, up to the FPGA bound, if this would be useful for this goal.
>
Moxie was designed to be small and efficient from the compiler standpoint.
As a side effect, it is easy to audit from a security perspective. It
started life as a simulator + gcc compiler backend, and then later became
an FPGA implementation.
Moxie would benefit from focused effort in building out the hardware side
to be efficient on FPGA, developing and testing multi-core support and
related efforts. This area is less mature and could use attention. Start
at https://github.com/atgreen/moxiedev/tree/master/moxie/cores/moxie
In terms of other projects, there are many open source processor cores at
http://opencores.org
[-- Attachment #2: Type: text/html, Size: 2090 bytes --]
prev parent reply other threads:[~2015-07-03 10:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 4:04 Jean-Paul Kogelman
2015-07-02 7:18 ` Henning Kopp
2015-07-02 8:33 ` Jean-Paul Kogelman
2015-07-02 12:33 ` Mistr Bigs
2015-07-02 14:52 ` Owen Gunden
2015-07-03 3:13 ` Jeremy Rubin
2015-07-03 3:25 ` Jeff Garzik
2015-07-03 4:19 ` Jean-Paul Kogelman
2015-07-03 5:33 ` Jeremy Rubin
2015-07-03 6:18 ` Jean-Paul Kogelman
2015-07-03 10:55 ` Jeff Garzik [this message]
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='CADm_WcYJ0=cSMo3xB+zT6pmxX0y6_uKpRgn1Jkq997Siev0grw@mail.gmail.com' \
--to=jgarzik@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jeremy.l.rubin.travel@gmail$(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