path: root/d3/500090557ccf5b346b0d8d9584a072cd43518e

Return-Path: <jlrubin@mit.edu>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 24155C0001
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri, 19 Mar 2021 21:42:01 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp4.osuosl.org (Postfix) with ESMTP id 0ADD24EE65
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri, 19 Mar 2021 21:42:01 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3,
 RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001]
 autolearn=ham autolearn_force=no
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 wBS7WFzdZiGV
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri, 19 Mar 2021 21:41:58 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11])
 by smtp4.osuosl.org (Postfix) with ESMTPS id 576FF4EE62
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri, 19 Mar 2021 21:41:57 +0000 (UTC)
Received: from mail-il1-f179.google.com (mail-il1-f179.google.com
 [209.85.166.179]) (authenticated bits=0)
 (User authenticated as jlrubin@ATHENA.MIT.EDU)
 by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 12JLftAd005341
 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT)
 for <bitcoin-dev@lists.linuxfoundation.org>; Fri, 19 Mar 2021 17:41:56 -0400
Received: by mail-il1-f179.google.com with SMTP id j11so9318643ilu.13
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri, 19 Mar 2021 14:41:56 -0700 (PDT)
X-Gm-Message-State: AOAM533zt9GVc2GyWmNZdQ8NPyaHVb31QAZIh92DBvFNH1GaJ3QVnCQL
 /7+M3hadYHnIcwHGHQPtEkMPpHr60Br1I1i5u3c=
X-Google-Smtp-Source: ABdhPJyG+8eDGtHzJ3ss711bCC2QUpRFenfuWpAb7BkeNqv8+m5GcAJM+Qv9p0S2+3K8uPr27QWmcfUQ16150H1AwnA=
X-Received: by 2002:a05:6e02:20c3:: with SMTP id
 3mr4157594ilq.164.1616190115219; 
 Fri, 19 Mar 2021 14:41:55 -0700 (PDT)
MIME-Version: 1.0
From: Jeremy <jlrubin@mit.edu>
Date: Fri, 19 Mar 2021 14:41:43 -0700
X-Gmail-Original-Message-ID: <CAD5xwhhmNn9a0v55J9zrPHN9FxL+jqEJx13n2zLb1-_0u_1Zjw@mail.gmail.com>
Message-ID: <CAD5xwhhmNn9a0v55J9zrPHN9FxL+jqEJx13n2zLb1-_0u_1Zjw@mail.gmail.com>
To: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/mixed; boundary="000000000000b529da05bdea9557"
Subject: [bitcoin-dev] (Recurring) Taproot activation meeting on IRC -
 Tuesday 23rd March 19:00 UTC + every fortnight
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Mar 2021 21:42:01 -0000

--000000000000b529da05bdea9557
Content-Type: multipart/alternative; boundary="000000000000b529d405bdea9555"

--000000000000b529d405bdea9555
Content-Type: text/plain; charset="UTF-8"

In response to the previous Taproot Activation Meeting, I noted that the
advance notice was insufficient and proposed having the proposed meeting
the following week, to consider the meeting last week as a "discussion",
and thereafter reserving a meeting slot fortnightly reserved. I've been
asked/volunteered in the ##taproot-activation IRC channel on freenode to
announce, assemble an agenda, and host this meeting. *If you plan to attend
please read the entire email as there are some specific instructions for
participation that have differed from past meetings.*

I've attached an ICS file with scheduling this meeting for 10 repetitions
for your convenience. Subsequent meetings will hopefully be unnecessary,
but scheduling them in advance helps ensure a process that respects all
parties desire to participate.

The purpose of this meeting is to serve as a checkpoint to raise any
blocking issues and to attempt to finalize parameter selection. As such,
I've attempted to make a guided agenda that should move towards
finalization rather than continuation of debate and makes the best use of
everyone's time. If there are topics missing or if I didn't accurately
capture the zeitgeist of discussion, please chime in with suggested changes
to the agenda.

If you cannot attend the meeting you may per-register a comment by replying
to this email. You may also pre-register a comment here for any reason for
ease of reference during the meeting, but it is not required. So that we
can keep the meeting focused and adjust agenda accordingly, I'll also
request explicitly that certain categories of comment described below be
pre-registered. Please keep this thread limited to pre-registered comments
rather than responses to such comments, which will be addressed in the
meeting.

For the meeting this coming Tuesday the plan is to attempt to finalize on:

1. Resolving any outstanding concerns around using a Speedy Trial to
attempt to activate Taproot that must be addressed.

There seems to be diverse consensus on ST, as per
https://gist.github.com/michaelfolkson/92899f27f1ab30aa2ebee82314f8fe7f#gistcomment-3668460
.

*As such, please pre-register any concern about any ST variant at all by
responding below.*

2. Selecting between start/stop heights and times for a speedy trial.

See https://github.com/bitcoin/bitcoin/pull/21377
https://github.com/bitcoin/bitcoin/pull/21392.

The focus of this discussion should be focused on blocking reasons to not
use time based parameters, the code review process, and timelines for being
able to utilize either activation method.

It is already a widely acknowledged preference for heights over times from
a blank slate pure technical point of view, this discussion is intended to
be more pragmatic about safety, hitting the timelines we want to, and
shipping code.

*As such, If you wish to advocate for MTP from a blank slate pure technical
point of view, please pre-register a comment below so we can adjust the
agenda ahead of time. *

3. Parameter Selection for start/stop/active points.

Short of resolving height or time based start/stop, a discussion of
selecting acceptable parameters. We should get agreement on both sets of
height or time parameters irrespective of the resolution to 2, so that this
conversation can proceed independently.

My personal pre-meeting suggestion to keep the discussion moving is that we
primarily discuss based on time (as it is the independent variable), and
simply use the next (not previous) starting signalling period based on a
projection of 10 minute average blocks from today's date to determine the
specific height parameters. *Please pre-register if you have a different
suggestion.*

4. Parameter flexibility.

If we select parameters but, for some reason, need to adjust by a week or
two, does this invalidate all ACKs on parameter selection? Or can we agree
upon some slack in the timeline to accommodate unforeseen development
issues.

5. Simultaneous UASF.

There still seems to be some activity on the front of a simultaneous to ST
UASF. As this has the potential to derail the meeting if there should be
UASF at all (which I think is orthogonal to the goals of this meeting), and
given many participants unfamiliarity with the proposal for a UASF,
*I ask that any issues you wish to raise in this section of the meeting or
pertaining to UASF in a prior section be made in a detailed pre-registered
comment. *

I think it is regrettable to place this onus on the UASF organizers, but
strong communication to the community about plans and intentions seem to be
essential and in line with what would be required for a UASF to be safe and
successful in any case. I also recognize that some participants (on either
side) may not wish to discuss UASF at all in this meeting, but I think that
it is an important part of the activation discussion irrespective of
personal views.


As a reminder, the channel is also open for ongoing discussion 24/7, and
there is a web chat client here:

https://webchat.freenode.net/?channel=##taproot-activation

Best,

Jeremy


--
@JeremyRubin <https://twitter.com/JeremyRubin>
<https://twitter.com/JeremyRubin>

--000000000000b529d405bdea9555
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small;color:#000000">In response to the previo=
us Taproot Activation Meeting, I noted that the advance notice was insuffic=
ient and proposed having the proposed meeting the following week, to consid=
er the meeting last week as a &quot;discussion&quot;, and thereafter reserv=
ing a meeting slot fortnightly reserved. I&#39;ve been asked/volunteered in=
 the ##taproot-activation IRC channel on freenode to announce, assemble an =
agenda, and host this meeting. <b>If you plan to attend please read the ent=
ire email as there are some specific instructions for participation that ha=
ve differed from past meetings.</b><br></div><div class=3D"gmail_default" s=
tyle=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#00000=
0"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,helvet=
ica,sans-serif;font-size:small;color:#000000">I&#39;ve attached an ICS file=
 with scheduling this meeting for 10 repetitions for your convenience. Subs=
equent meetings will hopefully be unnecessary, but scheduling them in advan=
ce helps ensure a process that respects all parties desire to participate.<=
br></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,=
sans-serif;font-size:small;color:#000000"><br></div><div class=3D"gmail_def=
ault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color=
:#000000">The purpose of this meeting is to serve as a checkpoint to raise =
any blocking issues and to attempt to finalize parameter selection. As such=
, I&#39;ve attempted to make a guided agenda that should move towards final=
ization rather than continuation of debate and makes the best use of everyo=
ne&#39;s time. If there are topics missing or if I didn&#39;t accurately ca=
pture the zeitgeist of discussion, please chime in with suggested changes t=
o the agenda.<br></div><div class=3D"gmail_default" style=3D"font-family:ar=
ial,helvetica,sans-serif;font-size:small;color:#000000"><br></div><div clas=
s=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-si=
ze:small;color:#000000">If you cannot attend the meeting you may per-regist=
er a comment by replying to this email. You may also pre-register a comment=
 here for any reason for ease of reference during the meeting, but it is no=
t required. So that we can keep the meeting focused and adjust agenda accor=
dingly, I&#39;ll also request explicitly that certain categories of comment=
 described below be pre-registered. Please keep this thread limited to pre-=
registered comments rather than responses to such comments, which will be a=
ddressed in the meeting. </div><div class=3D"gmail_default" style=3D"font-f=
amily:arial,helvetica,sans-serif;font-size:small;color:#000000"><br></div><=
div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif=
;font-size:small;color:#000000">For the meeting this coming Tuesday the pla=
n is to attempt to finalize on:</div><div class=3D"gmail_default" style=3D"=
font-family:arial,helvetica,sans-serif;font-size:small;color:#000000"><br><=
/div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans=
-serif;font-size:small;color:#000000">1. Resolving any outstanding concerns=
 around using a Speedy Trial to attempt to activate Taproot that must be ad=
dressed.</div><div class=3D"gmail_default" style=3D"font-family:arial,helve=
tica,sans-serif;font-size:small;color:#000000"><br></div><div class=3D"gmai=
l_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;=
color:#000000">There seems to be diverse consensus on ST, as per <a href=3D=
"https://gist.github.com/michaelfolkson/92899f27f1ab30aa2ebee82314f8fe7f#gi=
stcomment-3668460">https://gist.github.com/michaelfolkson/92899f27f1ab30aa2=
ebee82314f8fe7f#gistcomment-3668460</a>.</div><div class=3D"gmail_default" =
style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#0000=
00"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,helve=
tica,sans-serif;font-size:small;color:#000000"><b>As such, please pre-regis=
ter any concern about any ST variant at all by responding below.</b></div><=
div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif=
;font-size:small;color:#000000"><br>
</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,san=
s-serif;font-size:small;color:#000000">2. Selecting between start/stop heig=
hts and times for a speedy trial.</div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#000000"><=
br></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,=
sans-serif;font-size:small;color:#000000"> See <a href=3D"https://github.co=
m/bitcoin/bitcoin/pull/21377">https://github.com/bitcoin/bitcoin/pull/21377=
</a> <a href=3D"https://github.com/bitcoin/bitcoin/pull/21392">https://gith=
ub.com/bitcoin/bitcoin/pull/21392</a>. </div><div class=3D"gmail_default" s=
tyle=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#00000=
0"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,helvet=
ica,sans-serif;font-size:small;color:#000000">The focus of this discussion =
should be focused on blocking reasons to not use time based parameters, the=
 code review process, and timelines for being able to utilize either activa=
tion method.</div><div class=3D"gmail_default" style=3D"font-family:arial,h=
elvetica,sans-serif;font-size:small;color:#000000"><br></div><div class=3D"=
gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:sm=
all;color:#000000">It is already a widely acknowledged preference for heigh=
ts over times from a blank slate pure technical point of view, this discuss=
ion is intended to be more pragmatic about safety, hitting the timelines we=
 want to, and shipping code.</div><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif;font-size:small;color:#000000"><br></di=
v><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-se=
rif;font-size:small;color:#000000"><b>As such, If you wish to advocate for =
MTP from a blank slate pure technical point of view, please pre-register a =
comment below so we can adjust the agenda ahead of time. </b><br></div><div=
 class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;fo=
nt-size:small;color:#000000"><br></div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#000000">3=
. Parameter Selection for start/stop/active points.</div><div class=3D"gmai=
l_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;=
color:#000000"><br></div><div class=3D"gmail_default" style=3D"font-family:=
arial,helvetica,sans-serif;font-size:small;color:#000000">Short of resolvin=
g height or time based start/stop, a discussion of selecting acceptable par=
ameters. We should get agreement on both sets of height or time parameters =
irrespective of the resolution to 2, so that this conversation can proceed =
independently.</div><div class=3D"gmail_default" style=3D"font-family:arial=
,helvetica,sans-serif;font-size:small;color:#000000"><br></div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-siz=
e:small;color:#000000">My personal pre-meeting suggestion to keep the discu=
ssion moving is that we primarily discuss based on time (as it is the indep=
endent variable), and simply use the next (not previous) starting signallin=
g period based on a projection of 10 minute average blocks from today&#39;s=
 date to determine the specific height parameters. <b>Please pre-register i=
f you have a different suggestion.</b><br></div><div class=3D"gmail_default=
" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#00=
0000"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,hel=
vetica,sans-serif;font-size:small;color:#000000">4. Parameter flexibility. =
<br></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica=
,sans-serif;font-size:small;color:#000000"><br></div><div class=3D"gmail_de=
fault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;colo=
r:#000000">If we select parameters but, for some reason, need to adjust by =
a week or two, does this invalidate all ACKs on parameter selection? Or can=
 we agree upon some slack in the timeline to accommodate unforeseen develop=
ment issues.</div><div class=3D"gmail_default" style=3D"font-family:arial,h=
elvetica,sans-serif;font-size:small;color:#000000"><br></div><div class=3D"=
gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:sm=
all;color:#000000">5. Simultaneous UASF.</div><div class=3D"gmail_default" =
style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#0000=
00"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,helve=
tica,sans-serif;font-size:small;color:#000000">There still seems to be some=
 activity on the front of a simultaneous to ST UASF. As this has the potent=
ial to derail the meeting  if there should be UASF at all (which I think is=
 orthogonal to the goals of this meeting), and given many participants unfa=
miliarity with the proposal for a UASF, <b>I ask that any issues you wish t=
o raise in this section of the meeting or pertaining to UASF in a prior sec=
tion be made in a detailed pre-registered comment. <br></b></div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-siz=
e:small;color:#000000"><b><br></b></div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#000000">I=
 think it is regrettable to place this onus on the UASF organizers, but str=
ong communication to the community about plans and intentions seem to be es=
sential and in line with what would be required for a UASF to be safe and s=
uccessful in any case. I also recognize that some participants (on either s=
ide) may not wish to discuss UASF at all in this meeting, but I think that =
it is an important part of the activation discussion irrespective of person=
al views.<br></div><div class=3D"gmail_default" style=3D"font-family:arial,=
helvetica,sans-serif;font-size:small;color:#000000"><br></div><div class=3D=
"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:s=
mall;color:#000000"><br></div><div class=3D"gmail_default" style=3D"font-fa=
mily:arial,helvetica,sans-serif;font-size:small;color:#000000">
As a reminder, the channel is also open for ongoing discussion 24/7, and th=
ere is a web chat client here:<br>
<br>
<a href=3D"https://webchat.freenode.net/?channel=3D#%23taproot-activation" =
rel=3D"noreferrer" target=3D"_blank">https://webchat.freenode.net/?channel=
=3D##taproot-activation</a></div><div class=3D"gmail_default" style=3D"font=
-family:arial,helvetica,sans-serif;font-size:small;color:#000000"><br></div=
><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-ser=
if;font-size:small;color:#000000">Best,</div><div class=3D"gmail_default" s=
tyle=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#00000=
0"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,helvet=
ica,sans-serif;font-size:small;color:#000000">Jeremy<br></div><div class=3D=
"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:s=
mall;color:#000000"><br></div><br clear=3D"all"><div><div dir=3D"ltr" class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr">--=
<br><a href=3D"https://twitter.com/JeremyRubin" target=3D"_blank">@JeremyRu=
bin</a><a href=3D"https://twitter.com/JeremyRubin" target=3D"_blank"></a></=
div></div></div></div>

--000000000000b529d405bdea9555
Content-Type: text/calendar; charset="UTF-8"; method=PUBLISH
Content-Transfer-Encoding: 7bit

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:Bitcoin
X-WR-TIMEZONE:America/Los_Angeles
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20210323T120000
DTEND;TZID=America/Los_Angeles:20210323T130000
RRULE:FREQ=WEEKLY;WKST=MO;COUNT=10;INTERVAL=2;BYDAY=TU
DTSTAMP:20210319T193653Z
UID:24bm0kbce0g37qveuua09bas01@google.com
CREATED:20210319T193621Z
DESCRIPTION:
LAST-MODIFIED:20210319T193621Z
LOCATION:IRC ##taproot-activation
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Taproot Activation Meeting
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR

--000000000000b529d405bdea9555--
--000000000000b529da05bdea9557
Content-Type: text/calendar; charset="US-ASCII"; name="taproot-meeting.ics"
Content-Disposition: attachment; filename="taproot-meeting.ics"
Content-Transfer-Encoding: base64
Content-ID: <f_kmgpfmh10>
X-Attachment-Id: f_kmgpfmh10

QkVHSU46VkNBTEVOREFSDQpQUk9ESUQ6LS8vR29vZ2xlIEluYy8vR29vZ2xlIENhbGVuZGFyIDcw
LjkwNTQvL0VODQpWRVJTSU9OOjIuMA0KQ0FMU0NBTEU6R1JFR09SSUFODQpNRVRIT0Q6UFVCTElT
SA0KWC1XUi1DQUxOQU1FOkJpdGNvaW4NClgtV1ItVElNRVpPTkU6QW1lcmljYS9Mb3NfQW5nZWxl
cw0KQkVHSU46VlRJTUVaT05FDQpUWklEOkFtZXJpY2EvTG9zX0FuZ2VsZXMNClgtTElDLUxPQ0FU
SU9OOkFtZXJpY2EvTG9zX0FuZ2VsZXMNCkJFR0lOOkRBWUxJR0hUDQpUWk9GRlNFVEZST006LTA4
MDANClRaT0ZGU0VUVE86LTA3MDANClRaTkFNRTpQRFQNCkRUU1RBUlQ6MTk3MDAzMDhUMDIwMDAw
DQpSUlVMRTpGUkVRPVlFQVJMWTtCWU1PTlRIPTM7QllEQVk9MlNVDQpFTkQ6REFZTElHSFQNCkJF
R0lOOlNUQU5EQVJEDQpUWk9GRlNFVEZST006LTA3MDANClRaT0ZGU0VUVE86LTA4MDANClRaTkFN
RTpQU1QNCkRUU1RBUlQ6MTk3MDExMDFUMDIwMDAwDQpSUlVMRTpGUkVRPVlFQVJMWTtCWU1PTlRI
PTExO0JZREFZPTFTVQ0KRU5EOlNUQU5EQVJEDQpFTkQ6VlRJTUVaT05FDQpCRUdJTjpWRVZFTlQN
CkRUU1RBUlQ7VFpJRD1BbWVyaWNhL0xvc19BbmdlbGVzOjIwMjEwMzIzVDEyMDAwMA0KRFRFTkQ7
VFpJRD1BbWVyaWNhL0xvc19BbmdlbGVzOjIwMjEwMzIzVDEzMDAwMA0KUlJVTEU6RlJFUT1XRUVL
TFk7V0tTVD1NTztDT1VOVD0xMDtJTlRFUlZBTD0yO0JZREFZPVRVDQpEVFNUQU1QOjIwMjEwMzE5
VDE5MzY1M1oNClVJRDoyNGJtMGtiY2UwZzM3cXZldXVhMDliYXMwMUBnb29nbGUuY29tDQpDUkVB
VEVEOjIwMjEwMzE5VDE5MzYyMVoNCkRFU0NSSVBUSU9OOg0KTEFTVC1NT0RJRklFRDoyMDIxMDMx
OVQxOTM2MjFaDQpMT0NBVElPTjpJUkMgIyN0YXByb290LWFjdGl2YXRpb24NClNFUVVFTkNFOjAN
ClNUQVRVUzpDT05GSVJNRUQNClNVTU1BUlk6VGFwcm9vdCBBY3RpdmF0aW9uIE1lZXRpbmcNClRS
QU5TUDpPUEFRVUUNCkVORDpWRVZFTlQNCkVORDpWQ0FMRU5EQVINCg==
--000000000000b529da05bdea9557--