From: Daniel Stadulis <dstadulis@gmail•com>
To: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] #bitcoin-dev Weekly Development Meeting Minutes 2015-10-08
Date: Fri, 9 Oct 2015 15:45:37 -0700 [thread overview]
Message-ID: <CAHpxFbGyrZsvVKU4zqH4btF2EYvQ+EL4xPubXSCsk2dLUcK0aw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3097 bytes --]
More readable Google Doc version with html links here:
https://docs.google.com/document/d/1hCDuOBNpqrZ0NLzvgrs2kDIF3g97sOv-FyneHjQellk/edit?usp=sharing
Meeting Title:
#bitcoin-dev Weekly Development Meeting
Meeting Date:
2015-10-08
Meeting Time:
19:00-20:00 UTC
Participants in Attendance:
dstadulis
wumpus
btcdrak
morcos
petertodd
bsm117532
BlueMatt
gmaxwell
GreenIsMyPepper
phantomcircuit
warren
sipa
IRC Chat Logs:
http://bitcoinstats.com/irc/bitcoin-dev/logs/2015/10/08#l1444329019.0
———------------------------------
Topics to be discussed:
1. Mempool limiting
2. Partial transaction malleability fix: Low-S change (releases 0.10.3, 0.11.1
backport)
3. CHECKLOCKTIMEVERIFY (CLTV) backport reviews
4. CHECKSEQUENCEVERIFY (CSV) reviews
5. Creation of [bitcoin-discuss] mailing list planning
———------------------------------
2015-10-08 Meeting Conclusions:
Ecosystem Warnings & Alerts:
There is a Bitcoin ecosystem threat with the potential to cause millions of
dollars in losses that needs higher visibility. It's not a Bitcoin Core /
Bitcoin network issue but most Javascript-based Bitcoin software is
affected. The issue, documented here
https://github.com/feross/buffer/pull/81, is about common, critical,
Javascript code that is broken and may cause the generation of incorrect
pubkeys (among other issues). If Javascript is part of your implementation,
you should read the referenced pull request.
#
Action items
Responsible Parties
ETA/Due Date
1
Review/test code for Pull Request #6722 "Limit mempool by throwing away the
cheapest txn and setting min relay fee to it".
All
Unspecified
2
Provide ACK’s/support for low limits on PR #6771 "Policy: Lower default
limits for tx chains".
All
Unspecified
4
Urgent code review and ACKs of CLTV backports PR:
#6706 “CLTV IsSuperMajority() soft-fork, rebased for v0.10.2”
#6707 “CLTV IsSuperMajority() soft-fork, rebased for v0.11.0”
All
Unspecified
5
Contact miners about PR #6769 "Test LowS in standardness, removes nuisance
malleability vector" and turning on the long-existing anti-malleability
standardness rules in Bitcoin Core
Bluematt & Gmaxwell
Unspecified
6
Clarification from maaku regarding nSequence for BIP68
Continue review and ACKs of PR
#6312 “BIP-68: Mempool-only sequence number constraint verification”
#6564 “BIP-112: Mempool-only CHECKSEQUENCEVERIFY”
#6566 “BIP-113: Mempool-only median time-past as endpoint for lock-time
calculations”
All
Unspecified
7
Mailing Lists: [bitcoin-discuss] creation, moderators assignment of discuss
and dev list, simple website for mailing list policy.
Warren
Discussion meeting scheduled for: 2015-10-12 19:00-20:00 UTC
Meetingbot Minutes
Minutes(HTML)
http://www.erisian.com.au/meetbot/bitcoin-dev/2015/bitcoin-dev.2015-10-08-18.59.html
Minutes(text)
http://www.erisian.com.au/meetbot/bitcoin-dev/2015/bitcoin-dev.2015-10-08-18.59.txt
IRC Log:
http://www.erisian.com.au/meetbot/bitcoin-dev/2015/bitcoin-dev.2015-10-08-18.59.log.html
[-- Attachment #2: Type: text/html, Size: 4668 bytes --]
reply other threads:[~2015-10-09 22:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAHpxFbGyrZsvVKU4zqH4btF2EYvQ+EL4xPubXSCsk2dLUcK0aw@mail.gmail.com \
--to=dstadulis@gmail$(echo .)com \
--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