public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Christopher DeLucia <deluciac@bu•edu>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] IBLT & Bitcoin
Date: Sat, 11 May 2019 21:35:38 -0400	[thread overview]
Message-ID: <CAPwAn9RLT7_FpQ4PMrN9OpoPw2y0qZDiGzMYp_fMq+A8sO55GQ@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 541 bytes --]

Hi all,

While in college (2017), I produced this paper on IBLT applications and
Bitcoin that referenced some of the research done by folks like Gavin
Andresen and Rusty Russell.

This should come with a disclaimer: I have not really looked at this paper
nor Bitcoin since 2017.  Additionally, this paper was not peer reviewed; it
was just for class.

Regardless, I came across it when I was cleaning out some old docs on my
drive and figured I'd send it over to bitcoin-dev in the event it can
contribute to anything at all.

Thanks,
Chris

[-- Attachment #1.2: Type: text/html, Size: 687 bytes --]

[-- Attachment #2: IBLT Memory Pool Paper.pdf --]
[-- Type: application/pdf, Size: 522279 bytes --]

             reply	other threads:[~2019-05-12  1:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-12  1:35 Christopher DeLucia [this message]
2019-05-13 23:39 ` ZmnSCPxj

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=CAPwAn9RLT7_FpQ4PMrN9OpoPw2y0qZDiGzMYp_fMq+A8sO55GQ@mail.gmail.com \
    --to=deluciac@bu$(echo .)edu \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    /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