deploy: 768c9c3

bitcoin-core-dev-tech/2015-02/index.xml

@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bitcoin Core Dev Tech 2015 on ₿itcoin Transcripts</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/</link><description>Recent content in Bitcoin Core Dev Tech 2015 on ₿itcoin Transcripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/index.xml" rel="self" type="application/rss+xml"/><item><title>Bitcoin Law For Developers</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/james-gatto-marco-santori-bitcoin-law-for-developers/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/james-gatto-marco-santori-bitcoin-law-for-developers/</guid><description>We are going to be taking a 15 minute coffee break after our next two speakers. I want to introduce you to James Gatto and Marco Santori with Pilsbury. They will be spending some time talking about Bitcoin law. They have a room this afternoon and they are offering to talk with you one on one. So Marco and James.
 You missed the introduction. Was it any good? (laughter)
-We are here to talk about legal issues.</description></item><item><title>Circle</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/jeremy-allaire-circle/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/jeremy-allaire-circle/</guid><description>We are excited to be here and sponsoring this event. We have backgrounds in working on developer tools that goes back to the early days of something.
-How do we mature the development of Bitcoin Core itself? One of the things that is useful is suss out the key components of it. In a standard you have a spec, it could be a whitepaper, and then you have a reference implementation, and then a test suite that enforces interoperability.</description></item><item><title>Gavinandresen</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/gavinandresen/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/gavinandresen/</guid><description>http://blog.circle.com/2015/02/10/devcore-livestream/
+We are here to talk about legal issues.</description></item><item><title>Gavinandresen</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/gavinandresen/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/gavinandresen/</guid><description>http://blog.circle.com/2015/02/10/devcore-livestream/
 The instant transaction time.. you know I walk up to a cash register, I put my phone there, and in a second or two the transaction is confirmed and I walk away with my coffee. Anything beyond that, 10 minutes versus 1 minute doesn&amp;rsquo;t matter. So the problem you want to solve is how do we get instant confirmation.. there&amp;rsquo;s a bunch of ideas about this, like a trusted third party that promises to not double spend, have some coins locked up in a multisig wallet like Green Address.</description></item><item><title>Research And Development Goals</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/research-and-development-goals/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/research-and-development-goals/</guid><description>R&amp;amp;D Goals &amp;amp; Challenges
 We often see people saying they are testing the waters, they fixed a typo, they made a tiny little fix that doesn&amp;rsquo;t impact much, they are getting used to the process. They are finding that it&amp;rsquo;s really easy to contribut to Bitcoin Core. You code your changes, you submit your changes, there&amp;rsquo;s not much to it.
-There&amp;rsquo;s a difference, and the lines are fuzzy and undefined, and you cna make a change to Core that changes a spelling error or a change to policy or consensus rules, for those high-level things, for ecosystem-level things, there&amp;rsquo;s several mailing lists, the dev list gets the most traffic.</description></item></channel></rss>
+There&amp;rsquo;s a difference, and the lines are fuzzy and undefined, and you cna make a change to Core that changes a spelling error or a change to policy or consensus rules, for those high-level things, for ecosystem-level things, there&amp;rsquo;s several mailing lists, the dev list gets the most traffic.</description></item><item><title>Talk by the founders of Circle</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/jeremy-allaire-circle/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/jeremy-allaire-circle/</guid><description>We are excited to be here and sponsoring this event. We have backgrounds in working on developer tools that goes back to the early days of something.
+How do we mature the development of Bitcoin Core itself? One of the things that is useful is suss out the key components of it. In a standard you have a spec, it could be a whitepaper, and then you have a reference implementation, and then a test suite that enforces interoperability.</description></item></channel></rss>

categories/core-dev-tech/index.xml

@@ -152,8 +152,8 @@ Monday night presentation: https://btctranscripts.com/sf-bitcoin-meetup/2017-09-
 I think we should continue to use #bitcoin-core-dev for anything about changing Bitcoin Core and try to keep things open even though we’re together here today and tomorrow and the next.
 # Wallets and block pruning and rescans Nobody produces P2SH change when they have a native output.</description></item><item><title>Bitcoin Law For Developers</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/james-gatto-marco-santori-bitcoin-law-for-developers/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/james-gatto-marco-santori-bitcoin-law-for-developers/</guid><description>We are going to be taking a 15 minute coffee break after our next two speakers. I want to introduce you to James Gatto and Marco Santori with Pilsbury. They will be spending some time talking about Bitcoin law. They have a room this afternoon and they are offering to talk with you one on one. So Marco and James.
 You missed the introduction. Was it any good? (laughter)
-We are here to talk about legal issues.</description></item><item><title>Circle</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/jeremy-allaire-circle/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/jeremy-allaire-circle/</guid><description>We are excited to be here and sponsoring this event. We have backgrounds in working on developer tools that goes back to the early days of something.
-How do we mature the development of Bitcoin Core itself? One of the things that is useful is suss out the key components of it. In a standard you have a spec, it could be a whitepaper, and then you have a reference implementation, and then a test suite that enforces interoperability.</description></item><item><title>Gavinandresen</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/gavinandresen/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/gavinandresen/</guid><description>http://blog.circle.com/2015/02/10/devcore-livestream/
+We are here to talk about legal issues.</description></item><item><title>Gavinandresen</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/gavinandresen/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/gavinandresen/</guid><description>http://blog.circle.com/2015/02/10/devcore-livestream/
 The instant transaction time.. you know I walk up to a cash register, I put my phone there, and in a second or two the transaction is confirmed and I walk away with my coffee. Anything beyond that, 10 minutes versus 1 minute doesn&amp;rsquo;t matter. So the problem you want to solve is how do we get instant confirmation.. there&amp;rsquo;s a bunch of ideas about this, like a trusted third party that promises to not double spend, have some coins locked up in a multisig wallet like Green Address.</description></item><item><title>Research And Development Goals</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/research-and-development-goals/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/research-and-development-goals/</guid><description>R&amp;amp;D Goals &amp;amp; Challenges
 We often see people saying they are testing the waters, they fixed a typo, they made a tiny little fix that doesn&amp;rsquo;t impact much, they are getting used to the process. They are finding that it&amp;rsquo;s really easy to contribut to Bitcoin Core. You code your changes, you submit your changes, there&amp;rsquo;s not much to it.
-There&amp;rsquo;s a difference, and the lines are fuzzy and undefined, and you cna make a change to Core that changes a spelling error or a change to policy or consensus rules, for those high-level things, for ecosystem-level things, there&amp;rsquo;s several mailing lists, the dev list gets the most traffic.</description></item></channel></rss>
+There&amp;rsquo;s a difference, and the lines are fuzzy and undefined, and you cna make a change to Core that changes a spelling error or a change to policy or consensus rules, for those high-level things, for ecosystem-level things, there&amp;rsquo;s several mailing lists, the dev list gets the most traffic.</description></item><item><title>Talk by the founders of Circle</title><link>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/jeremy-allaire-circle/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/bitcoin-core-dev-tech/2015-02/jeremy-allaire-circle/</guid><description>We are excited to be here and sponsoring this event. We have backgrounds in working on developer tools that goes back to the early days of something.
+How do we mature the development of Bitcoin Core itself? One of the things that is useful is suss out the key components of it. In a standard you have a spec, it could be a whitepaper, and then you have a reference implementation, and then a test suite that enforces interoperability.</description></item></channel></rss>