From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137]) by lists.linuxfoundation.org (Postfix) with ESMTP id BE6E1C0001 for ; Thu, 4 Mar 2021 23:42:53 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id BA51D4EC6F for ; Thu, 4 Mar 2021 23:42:53 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -0.199 X-Spam-Level: X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp4.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pHruPZGl-wEc for ; Thu, 4 Mar 2021 23:42:52 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com [IPv6:2607:f8b0:4864:20::b34]) by smtp4.osuosl.org (Postfix) with ESMTPS id C78724EC6E for ; Thu, 4 Mar 2021 23:42:52 +0000 (UTC) Received: by mail-yb1-xb34.google.com with SMTP id h82so16663222ybc.13 for ; Thu, 04 Mar 2021 15:42:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=gxYqmPloc9znFMBMhO3a4lfsR0Q5eZ6frLGDa8xh3lc=; b=sRjL33ZymcIoHVP/aZjkBwG8tKW0fSX+yavE4ItJA3NHr0boqzIUaeQDfQUnKkFZO3 3jmaRE07SxR+yszcwtEnxmSrCJkbquRdKZx6y7rmujVSHjD8esILr3OVw+e/rRMc/maW GL9sXOj9br/iDTgKfnHU0rfwuQ+7//pP2zPASjHq2/uZuJWbAmMcEkIhxd0x6OQ8Qu5n o9UpIzyOSHibVov9hsynlDaUuIWepK2GpPwD0KEmxNl0nDUWIG6HX0CfEJ3t1w95HSRE avYf7KBRTsreR6Bsad9EGVz+PCrM3QlcHAPB9QNJL3W6JEjd05L/GkC/10thHgO3twl6 2RbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=gxYqmPloc9znFMBMhO3a4lfsR0Q5eZ6frLGDa8xh3lc=; b=EeHcPaOE9JVazPNiO1aeNLiO5x3eXeMDzf7qtWsFb7kjeZrCfERpCvXmITyTMjtN30 3Z2Im0ZoqnRGqt+5x6Ou6hZAGnM/kMsJdoJqhtdAFCpY6/Pyv+A4daPzB8PdMi/cHH5e +wTCC9TzJx2I15rMhZBMqt2lhmzu+E6be7FgfrN0yoAbWDq6aeAhEtsB/XGu8CgetcX2 Hn7fIXwf3KBc9s2O4m2FtKHVHGexoSdvHgD6F+RiwEog7e+bNb4euLFP9rspuP1oixfk XQNxQXbhsZv/Lx3zUYTP7OzzTh2buAl0VIplfZoYhLJl/fazfpRTQO01uWvWrUSAn2Wj JQJQ== X-Gm-Message-State: AOAM533Vgl9Vr9GTB7nU21vY2MLMWVjFWWMqLVNaFQ2yoJzxeQ0niPRc tLKBF1ptHQmfJZqio4OJdaSnEglNvIDdXfGCojmSCpbWArE= X-Google-Smtp-Source: ABdhPJzvq47ser3n6HWliHgQosu2uS4Z6cfL5DBeeSD20q61Wty++xD4GW3tDwa2iQmMl7R5eFLeUfMarbzRf+jZJno= X-Received: by 2002:a25:ae14:: with SMTP id a20mr10600277ybj.129.1614901371132; Thu, 04 Mar 2021 15:42:51 -0800 (PST) MIME-Version: 1.0 From: Lonero Foundation Date: Thu, 4 Mar 2021 18:42:40 -0500 Message-ID: To: bitcoin-dev@lists.linuxfoundation.org Content-Type: multipart/alternative; boundary="00000000000092dd1105bcbe8666" X-Mailman-Approved-At: Fri, 05 Mar 2021 09:39:24 +0000 Subject: [bitcoin-dev] BIP Proposal: Consensus (hard fork) PoST Datastore for Energy Efficient Mining X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Mar 2021 23:42:53 -0000 --00000000000092dd1105bcbe8666 Content-Type: text/plain; charset="UTF-8" Hello, I want to start a new BIP proposal aiming to tackle some of the energy efficiency issues w/ Bitcoin mining. Excuse my ignorance given this is my first time making a BIP proposal, but is there a specific format I need to follow? Do I just make a draft on my personal GitHub or need to attach the README? Anyways my idea is centered around a hybrid mining integration w/ POW/PoST for BTC's SHA-256 hash algorithm. The integration is actually a cryptography proof. While I would prefer a soft fork integration, a vastly different cryptography proof without affecting the current node integration is less than feasible. Anyways, I do want to submit my document explaining everything and how all this would work. I am mostly a Quantum Engineer and Bioinformatics consultant for a living, so I think what I can propose to an extent may be of interest to some. Best regards, Andrew M. K. Nassief --00000000000092dd1105bcbe8666 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello, I want to start a new BIP proposal aiming to t= ackle some of=20 the energy efficiency issues w/ Bitcoin mining. Excuse my ignorance=20 given this is my first time making a BIP proposal, but is there a=20 specific format I need to follow? Do I just make a draft on my personal=20 GitHub or need to attach the README?=C2=A0

An= yways my idea is centered around a hybrid mining integration w/ POW/PoST fo= r BTC's SHA-256 hash algorithm. The integration is actually a cryptography proof. While I would prefer a soft fork integration, a vastly different cryptography proof without affecting the current node integration is less than=20 feasible.

= Anyways, I do want to submit my document explaining everything and how all this=20 would work. I am mostly a Quantum Engineer and Bioinformatics consultant for a living, so I think what I can propose to an extent may be of=20 interest to some.

Best regards,
= Andrew M. K. Nassief
--00000000000092dd1105bcbe8666--