public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Damian Gomez <dgomez1092@gmail.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin-development Digest, Vol 48, Issue 41
Date: Sat, 9 May 2015 00:42:08 +0000	[thread overview]
Message-ID: <CAAS2fgTA21W9T=2Nmy+zQp2AhG5Gk+vF=w5X5Pm3ohZz7pJNVg@mail.gmail.com> (raw)
In-Reply-To: <CAH+jCTy=BF4g=7yTFYind3ZNiWz4uLo1puv1+RURi=26oqcD1Q@mail.gmail.com>

On Sat, May 9, 2015 at 12:00 AM, Damian Gomez <dgomez1092@gmail.com> wrote:
>
> ...of the following:
>
>  the DH_GENERATION would in effect calculate the reponses for a total
> overage of the public component, by addding a ternary option in the actual
> DH key (which I have attached to sse if you can iunderstand my logic)
[snip code]

Intriguing; and certainly a change of the normal pace around here.

> where w represents the weight of the total number of semantical
> constraints that an idivdual has expressed throught emotivoe packets that I
> am working on (implementation os difficutlt).  I think this is the
> appropriate route to implemeting a greating block size that will be used in
> preventing interception of bundled informations and replace value.  Client
> side implmentation will cut down transaction fees for the additional 264 bit
> implementation and greatly reduce need for ewallet providers to do so.

In these posts I am reminded of and sense some qualitative
similarities with a 2012 proposal by Mr. NASDAQEnema of Bitcointalk
with respect to multigenerational token architectures. In particula,r
your AES ModuleK Hashcodes (especially in light of Winternitz
compression) may constitute an L_2 norm attractor similar to the
motherbase birthpoint metric presented in that prior work.  Rethaw and
I provided a number of points for consideration which may be equally
applicable to your work:
https://bitcointalk.org/index.php?topic=57253.msg682056#msg682056

Your invocation of emotive packets suggests that you may be a
colleague of Mr. Virtuli Beatnik?  While not (yet) recognized as a
star developer himself; his eloquent language and his mastery of skb
crypto-calculus and differential-kernel number-ontologies demonstrated
in his latest publication ( https://archive.org/details/EtherealVerses
) makes me think that he'd be an ideal collaborator for your work in
this area.



  reply	other threads:[~2015-05-09  0:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.63969.1431119326.18600.bitcoin-development@lists.sourceforge.net>
2015-05-08 22:11 ` [Bitcoin-development] Bitcoin-development Digest, Vol 48, Issue 41 Damian Gomez
2015-05-08 22:12   ` Damian Gomez
2015-05-08 22:13     ` Damian Gomez
2015-05-09  0:00     ` Damian Gomez
2015-05-09  0:42       ` Gregory Maxwell [this message]
2015-05-09 16:39         ` Peter Todd
2015-05-08 22:19 Raystonn

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='CAAS2fgTA21W9T=2Nmy+zQp2AhG5Gk+vF=w5X5Pm3ohZz7pJNVg@mail.gmail.com' \
    --to=gmaxwell@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=dgomez1092@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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