Podcasts about Schnorr

Mark “Murch” Erhardt and Dave Harding are joined by Matt Morehouse and 0xB10C to discuss Newsletter #339.News● Vulnerability in LDK claim processing (0:47)● Replacement cycling attacks with miner exploitation (17:28)● Updated stats on compact block reconstruction (23:56)Selected Q&A from Bitcoin Stack Exchange● Who uses or wants to use PSBTv2 (BIP370)? (32:38)● In the bitcoin's block genesis, which parts can be filled arbitrarily? (34:41)● Lightning force close detection (36:47)● Is a segwit-formatted transaction with all inputs of non-witness program type valid? (40:01)● P2TR Security Question (41:41)● What exactly is being done today to make Bitcoin quantum-safe? (44:27)● What are the harmful effects of a shorter inter-block time? (47:57)● Could proof-of-work be used to replace policy rules? (51:19)● How does MuSig work in real Bitcoin scenarios? (54:54)● How does the -blocksxor switch that obfuscates the blocks.dat files work? (57:18)● How does the related key attack on Schnorr signatures work? (59:42)Releases and release candidates● LDK v0.1.1 (1:01:19)Notable code and documentation changes● Bitcoin Core #31376 (1:03:24)● Bitcoin Core #31583 (1:04:48)● Bitcoin Core #31590 (1:05:40)● Eclair #2982 (1:07:17)● BDK #1614 (1:11:39)● BOLTs #1110 (1:12:08)

LinkedIn Live conversation at (10:00 am GST) 10th September Title: Applying Porter's Five Forces Model to Bitcoin, Cryptocurrency, and Blockchain Guests: Markose Chentittha, Society X RA George, Blockchain DXB Overview: In this episode, we dive deep into how Michael Porter's Five Forces Model, a framework for analyzing competitive dynamics within industries, can be applied to the world of Bitcoin, cryptocurrency, and blockchain. We explore each force and its influence on this rapidly evolving industry, adding layers of digital, technological, environmental, and social factors. Key Topics Covered: Porter's Five Forces Model - Overview History of the model from Michael Porter's 1979 book Competitive Strategy: Techniques for Analyzing Industries and Competitors. Evolution of the framework with the addition of factors like globalization, technological disruption, and environmental concerns. Force 1: Threat of New Entry Low Barriers to Entry: The decentralized nature of blockchain allows anyone to enter the space. Economies of Scale: Bitcoin miners and Ethereum validators use shared resources like mining pools. Regulations: Global examples including China's crypto ban and India's taxation policies. Discussion on UAE's restrictions around privacy coins and stablecoins. Force 2: Brand Loyalty Examining Bitcoin and Ethereum maxis. NFT critics and the divide between DeFi advocates and NFT enthusiasts. Force 3: Network Effect User Onboarding: Stats on Bitcoin wallet users and daily active addresses. Developer Communities: The importance of large developer bases like those for Bitcoin, Ethereum, and Solana. Comparison with new blockchains: Challenges new projects face in attracting developers and users. Force 4: Competitive Rivalry The highly competitive landscape with over 14,000 cryptocurrencies and 1,100+ exchanges. Price Volatility: Its role in competition and how market manipulation (pump-and-dump schemes) impacts rivalries. Community Strength: Rivalries between Bitcoin maximalists, Ethereum supporters, and other blockchain communities. Force 5: Supplier Power Focus on miners, including Bitcoin ASIC manufacturers and the economies of scale involved. Monero and Privacy Coins: Discussion on privacy and the limited number of coins focused exclusively on privacy. Software Developers: Powerhouses like Ethereum Foundation and Solana Foundation. Force 6: The Threat of Substitution CBDCs and Stablecoins: Discussion on government-backed alternatives to traditional cryptocurrencies. New Technologies: Innovations like Directed Acyclic Graphs (DAGs) and the potential shift of investments from blockchain to AI and Metaverse projects. Ripple's fall in market cap and competition from state-backed stablecoins. Emerging Sixth Force: Complementors Importance of Complementary Products like airdrops and token rights. Technological Factors: Zero-knowledge proofs, sharding, and DePin for AI. Globalization trends and crypto's role in de-globalization. Dynamic Capabilities Blockchain innovations like Bitcoin's shift to Taproot and Schnorr signatures. Ethereum's move to proof-of-stake and tokenization's rise in crypto discourse. Environmental and Social Factors Bitcoin's environmental impact, the ongoing ESG debate, and whether Bitcoin could shift to proof-of-stake. Social impact discussions related to privacy, COP28, and green energy. Questions & Audience Engagement: Is regulation a positive or negative influence on crypto innovation? How can blockchain play a role in de-globalization? Will the rise of AI investments redirect attention from crypto and blockchain? Closing Thoughts: We wrapped up the session with thoughts on where the industry is heading, how different forces are shaping its growth, and the importance of staying adaptable in this dynamic space. For more information on our upcoming events and detailed updates on crypto and blockchain, follow Blockchain DXB & Society X. Don't forget to subscribe to our podcast and support us via the donation links provided.

I'm joined by guests Lloyd Fournier, Craig Raw, Rob Hamilton and odudex to discuss bitcoin wallets and signers.HousekeepingCalling for guests to join a ham radio panel. Email producer@coinkite.com if you are interested.Keep the audience questions coming! Send boosts or email questions to producer@coinkite.com.Check out the previous episode if you want to understand more about Dark SkippyDiscussion TopicsComing soon…Audience Questions"Geographically distributed multisig is probably the best self custody model today. But specifically what kinds of places are suitable for storing private key material internationally or even just away from your home territory? Many people do not have high trust family/friends that live in different areas and I am skeptical of the privacy and security bank safety deposit boxes." - Densest_Sprite0R"How have best practices evolved as we migrate from ecdsa to Schnorr it terms of interactivity / uptime that then therefore reshapes UX? e.g concurrent sessions, nonce counters, etc" - Vivek"Are you aware of any known attack methods to add malicious code to an sd card with out any physical access to it? Like with some type of radio frequency attack etc…?" - Kidwarp"Explain if you could why the anti exfil protocols don't work air-gapped."

Dark Skippy is a new attack that in theory, makes it much easier for a malicious person to steal your coins. Listen in to learn about some of the ins and outs here, as well as mitigation and the path forward for the industry from @utxoclub , @LLFOURN & @robin_linus .  Why air gapping is not the be all end all Dark Skippy in context with other attacks Security while signing transactions, and security while generating keys RFC6979 Deterministic nonce generation Updating PSBT to help mitigate this attack Summary The conversation discusses the ‘Dark Skippy' attack, a new method for leaking secret keys from a malicious signing device. The attack takes advantage of the nonces used in the Schnorr and ECDSA signature schemes. The new attack vector can potentially extract private keys and seed words from hardware wallets. The attack targets the nonce generation process during key generation and signing. The previous versions of this attack were inefficient, but Dark Skippy improves upon them. The contributors explain how the attack came about and its implications for hardware wallet security. They also discuss the RFC6979 deterministic nonce generation and the concept of anti-klepto signing protocols as mitigations against the attack.  While Dark Skippy is a sophisticated attack, it requires a high level of expertise and is not currently seen in the wild. The discussion highlights the importance of secure boot, upgrading the Partially Signed Bitcoin Transaction (PSBT) process, and improving the randomness of upfront key generation as potential mitigations.  However, it is emphasized that current reputable hardware wallets still provide a high level of security, and there is no immediate action required for users. Takeaways Dark Skippy is a new attack that leaks secret keys from a malicious signing device. The attack exploits the nonces used in the Schnorr and ECDSA signature schemes. Previous versions of this attack were inefficient, but Dark Skippy improves upon them. Mitigations against the attack include the RFC6979 deterministic nonce generation and anti-klepto signing protocols. Dark Skippy is a sophisticated attack that targets the nonce generation process during key generation and signing. Mitigations for Dark Skippy include implementing secure boot, upgrading the PSBT process, and improving the randomness of upfront key generation. Reputable hardware wallets currently provide a high level of security, and there is no immediate action required for users. The discussion highlights the importance of ongoing research and development to enhance the security of hardware wallets and protect against potential future attacks. Timestamps: (00:00) - Intro (00:45) - What is ‘Dark Skippy'? (04:39) - Is it an old attack vector? Bitcoin's security evolving with time (12:41) - Sponsor (15:22) - What is a nonce?, RFC6979 Deterministic nonce generation (22:55) - Common ways of people losing their Bitcoin (31:08) - Sponsor (32:07) - Anti-klepto signing protocols; ways to mitigate risks of losing coins (39:51) - Updating PSBT to help mitigate this attack (43:26) - The role of Multisig in preventing the attack (49:57) - Other attack vectors in malicious actor's toolkit (56:49) - Summarizing the steps to improve the ecosystem security (1:00:18) - Closing thoughts Links:  https://darkskippy.com/  https://frostsnap.com/  https://x.com/LLFOURN  https://x.com/robin_linus  https://x.com/utxoclub  https://x.com/utxoclub/status/1820520960476561825  Sponsors: CoinKite.com (code LIVERA) mempool.space/accelerator  Stephan Livera links: Follow me on X: @stephanlivera Subscribe to the podcast Subscribe to Substack

Is post-quantum cryptography safe from quantum computing? Do we really need thousands of qubits to attack RSA? We examine some of the challenges to PQC strength and timeline that have recently emerged in scientific papers and consider what makes peer review such a crucial part of the process. Join Host Konstantinos Karagiannis for a chat about the actual state of PQC and how it will affect your organization.  Papers mentioned:  “Quantum Algorithms for Lattice Problems”: https://eprint.iacr.org/2024/555.  “Factoring integers with sublinear resources on a superconducting quantum processor”: https://arxiv.org/abs/2212.12372. “Fast Factoring Integers by SVP Algorithms”: https://eprint.iacr.org/2021/232.  “A comment on ‘Factoring integers with sublinear resources on a superconducting quantum processor'”: https://arxiv.org/abs/2307.09651.  “A Side-Channel Attack on a Hardware Implementation of CRYSTALS-Kyber”: https://eprint.iacr.org/2022/1452.  Visit Protiviti at https://www.protiviti.com/US-en/technology-consulting/quantum-computing-services  to learn more about how Protiviti is helping organizations get post-quantum ready.  Follow host Konstantinos Karagiannis on all socials: @KonstantHacker and follow Protiviti Technology on LinkedIn and Twitter: @ProtivitiTech.    Questions and comments are welcome!   Theme song by David Schwartz, copyright 2021.   The views expressed by the participants of this program are their own and do not represent the views of, nor are they endorsed by, Protiviti Inc., The Post-Quantum World, or their respective officers, directors, employees, agents, representatives, shareholders, or subsidiaries.  None of the content should be considered investment advice, as an offer or solicitation of an offer to buy or sell, or as an endorsement of any company, security, fund, or other securities or non-securities offering. Thanks for listening to this podcast. Protiviti Inc. is an equal opportunity employer, including minorities, females, people with disabilities, and veterans.

In this week's episode, Anna (https://twitter.com/annarrose) and Nico (https://twitter.com/nico_mnbl) chat with Chelsea Komlo (https://twitter.com/chelseakomlo), Chief Scientist for the Zcash Foundation (https://zfnd.org/) and member of the Cryptography, Security, and Privacy lab at the University of Waterloo (https://crysp.uwaterloo.ca/). They discuss what sparked Chelsea's interest in cryptography research, starting with her work contributing to Tor, to her move to Zcash and her PhD work on Threshold Signature Schemes. They define some important terms around different signature schemes and discuss possible optimizations that can be used to make these more performant. They then dive into her work on the FROST Threshold Signature Scheme plus some new upcoming work. Here's some additional links for this episode: EdSIDH: Supersingular Isogeny Diffie-Hellman Key Exchange on Edwards Curves by Azarderakhsh, Lang, Jao and Koziel (https://djao.math.uwaterloo.ca/wiki/images/f/ff/Space-2018.pdf) Efficient Signature Generation by Smart Cards by Schnorr (https://link.springer.com/content/pdf/10.1007/BF00196725.pdf) FROST: Flexible Round-Optimized Schnorr Threshold Signatures by Komlo and Goldberg (https://eprint.iacr.org/2020/852.pdf) Episode 316: Alin Tomescu on Distributed On-chain Randomness and Keyless Accounts (https://zeroknowledge.fm/316-2/) Episode 295: Return to MPC with Nigel Smart (https://zeroknowledge.fm/295-2/) [On the (in)security of ROS] by Benhamouda, Lepoint, Loss, Orr`u and Raykova](https://eprint.iacr.org/2020/945.pdf) Re-Randomized FROST by Gouvˆea and Komlo (https://eprint.iacr.org/2024/436.pdf) Frostsnap (https://frostsnap.com/) CFRG GitHub Repository for FROST (https://github.com/cfrg/draft-irtf-cfrg-frost) zkSummit11 is happening next week, head to the zkSummit website (https://www.zksummit.com/) to apply for a waitlist spot now. The event will be held on 10 April in Athens, Greece. Check out the ZK Jobs Board (https://jobsboard.zeroknowledge.fm/) Aleo (http://aleo.org/) is a new Layer-1 blockchain that achieves the programmability of Ethereum, the privacy of Zcash, and the scalability of a rollup. Dive deeper and discover more about Aleo at http://aleo.org/ (http://aleo.org/) If you like what we do: * Find all our links here! @ZeroKnowledge | Linktree (https://linktr.ee/zeroknowledge) * Subscribe to our podcast newsletter (https://zeroknowledge.substack.com) * Follow us on Twitter @zeroknowledgefm (https://twitter.com/zeroknowledgefm) * Join us on Telegram (https://zeroknowledge.fm/telegram) * Catch us on YouTube (https://zeroknowledge.fm/)

I have been lucky enough to speak to some of the most amazing people who have built the core of security on the Internet, and a person near the top of my list is … Torben P. Pedersen.  The Pedersen Commitment So how do we create a world where we can store our secrets in a trusted and then reveal them when required? Let's say I predict the outcome of an election, but I don't want to reveal my prediction until after the election. Well, I could store a commitment to my prediction, and then at some time in the future I could reveal it to you, and you can check against the commitment I have made. Anyone who views my commitment should not be able to see what my prediction is. This is known as Pedersen Commitment, and where we produce our commitment and then show the message that matches the commitment. In its core form, we can implement a Pedersen Commitment in discrete logs [here]. But blockchain, IoT, Tor, and many other application areas, now use elliptic curve methods, so let's see if we can make a commitment with them. The classic paper is here: So before the interview with Torben, here's an outline of the Pedersen Commitment: Interview Bill: Okay, so tell me a bit about yourself, and what got you into cryptography? Torben: Well, I was studying computer science at university in Aarhus, and I just thought it was an interesting subject that was somewhere between computer science and mathematics. Bill: And so you invented a method that we now know as the Pedersen Commitment. What motivated you to do that? And how does it work? And how do you think it will be used in the future? Torben: Well, the reason I worked with this, was that I was working with verifiable secret sharing. There was, at the time, a method for doing non-interactive verifiable secret sharing based on a commitment which was unconditionally binding and computationally hiding. At the time, there was also inefficient commitments, that had the property of being unconditionally hiding, and I thought it would be nice to have a verifiable secret share where you don't have to rely on any computational assumptions, in order to be sure that your secret is not revealed when you do a secret share. Torben: Then there was a paper which created an authentication scheme very similar to Schnorr. But it's used a similar idea for a useful commitment. And that was kind of the combination of those two (the existing non-interactive verifiable secret sharing and the ideas form this authentication scheme), which motivated me to do verifiable secret sharing. And the commitment scheme was, of course, an important part of that because it had unconditioned hiding property, and it had the mathematical structure that was needed for the secret sharing. Bill: And it has scaled into an elliptic curve world. But with elliptic curves and discrete logs now under threat, how would you see it moving forward into a possible post-quantum crypto world? Torben: The good thing about the commitment scheme is that it is unconditional hiding. Of course, you can be sure that your private information is not leaked, even in case a quantum computer is constructed. But of course, the protocols that are using this one have to see what effect does it have if one, for example using a quantum computer, can change ones mind about a commitment. So you need to see how that would affect those protocols. Bill: So an example use of the commitment could be of a secret say someone voting in an election. So you would see when the commitment was made, and then when the vote was cast. Then the person could reveal what their votes actually was. Now it's been extended into zero-knowledge methods to prove that you have enough cryptocurrency to pay someone without revealing the transactions. How does that world evolve where you only see an anonymized ledger, and which can scare some people, but for others that is a citizen-focused world? How do you see your commitment evolving into privacy-preserving ledgers? Torben: I go back to what we're doing at Concordium where we have a blockchain which gives a high assurance about the privacy of the users acting on the blockchain. At the same time, using zero-knowledge proof, we set it up in such a way that designated authorities — if they under certain circumstances, for example, are given a court order — they will be able to see to link an account on the blockchain for that particular person. So, actually the zero-knowledge proofs and the commitment schemes — and all that — is used to guarantee the privacy of the users acting on the blockchain, and there are also regulatory requirements, that it must be possible to identify people who misbehave on the blockchain. Bill: Yeah, that's a difficult thing, and it's probably where the secret is stored. So, if the secret is stored in the citizen's wallet, then only they can reveal that. And if the secret needs to be stored, for money laundering by an agency could hold it. Torben: Actually we do not have to store the secret of the user. But there are other keys which allow us to link the account with a particular user. That is something which only designated parties can do. So we have one party which is the identity provider with issues and identity to a user and other parties called anonymity reworkers. And those parties will have to work together in order to link an account to a user. We use zero-knowledge proofs when creating the account to assure that account is created in such a way that it is possible for you to trace back the account to the user. Bill: And in terms of zero-knowledge proofs, there is a sliding scale from highly complex methods that you would use for Monero and anonymized cryptocurrencies, to the simpler ones to Fiat Shamir implementation. And they are probably unproven in terms of their impact on performance and for security. Where is the sweet spot? What methods do you think are the best for that? Torben: I think we need to see improvements in zero-knowledge proofs in order to have really efficient blockchains and non-interactive zero-knowledge proofs on a blockchain. So I definitely think we need some work on that. There are some acceptable non-interactive zero-knowledge proofs for the moment. We are using Bulletproofs for the moment together with Shamir shares on it, in order to make it non-interactive. But I think there are some technologies like zkSnarks and zkStarks, but I think there's room for improvement. Bill: And what do you think the key challenges within cryptography just now What do we need to be working on in the next three to five years? Torben: Yeah, so the biggest challenge, as you already mentioned, and that's what happens if we have a quantum computer that can break the assumptions that a lot of the constructions are based on today. Whether we have a quantum computer, I don't know, but we need to be prepared. We have some post-quantum algorithms, which I think also are quite complex, and it would be nice to have something that was more efficient and better to use. I think there's also room for work on that aspect. Bill: And obviously, to create some toolkits that move away from an Ethernet world and where the Internet was really built on the seven-layer model — and it's flawed. We perhaps need to rebuild on a toolkit of math, so that we actually have a solid foundation. I know that Hyperledger is starting to build these tools for developers. When we do see that rebuilding happening, and where are the toolkits going to come from? Torben: Toolkits could come from blockchain companies such as Concordium, for example. It could also come from the community with sponsored projects. If we can build up an infrastructure that allows people to use blockchains in the ledger, without trusting one particular party, so that they can create a trust, which is probably lacking on the Internet today. It's very difficult, as with the current Internet it is very difficult to know if you can trust someone or not. I hope blockchain technology can help create an infrastructure for that. There's a long way to go. We need good public permissionless blockchains for that, so you don't have to rely on a particular party for this. Obviously, that is sufficient, but there's quite some way to go. Bill: How do you change the approach of governments and industries that have been around for hundreds of years. So if you look at the legal industry, they still typically only accept wet signatures. They might have a GIF of a signature and add it to a PDF, but that's as far as it goes. So how are we going to really transform governments and, and existing industries to really accept that digital signatures are the way to do these things? Torben: Yeah, I think it's a bit dangerous, you know, accepting these GIFs of signatures and digital signatures which are not really cryptographically secure. I'm not a big fan of that. I'd like to see us moving to digital signatures, which are the way that we originally envisaged in the cryptographic world, and where the party who signs the signature is in control of the key which created the digital signature. I hope you'll see a movement towards that level of security. Bill: And could you tell me a little bit about the Concordium Foundation and what's objectives on what it hopes to achieve? Torben: So our vision is to create a public permissionless blockchain that can help to create trust across industries. We want to enable entities such as businesses and private persons, to interact or act privately on the blockchain. At the same time, it's very important for us not to create an infrastructure, which allows criminals to misuse it, and for some money laundering problems. Thus we want to create an environment where it's possible to identify people who misbehave or break the rules. And that is why we have this identity layer as part of our blockchain. Bill: And what got you into blockchain? Torben: I think the technology is very interesting. There's a lot of things you said based on a lot of pretty old cryptography. There's also new developments, for example, the zero-knowledge proofs. So there's new and new developments or developments. So very interesting. I mean, it's not necessarily what I was interested in, but when I did research many years ago. That's probably what I wanted to work with. I have been working with cryptography — mostly in mostly for the financial sector for 25 years. And that's also very interesting. There are challenges and it's also nice to get back to the sort of basis that I worked with many years ago. Bill: You took a route into the industry but obviously you could have gone into academia and you could become a professor and have an academic research team. Torben: I think it was because I wanted to work with practical aspects of using cryptography. I've been in research for some years and I thought I needed to try something else. And I was very keen to see how it would be used in practice and be part of that. So that's why I made that step. Bill: What does our digital world look like that's made up of tokens, cryptographic tokens, consensus systems and digital identities. And you think that that world will come anytime soon that we can trade assets, we can have digital assets that can be traded. Torben: Well, it depends on what you mean by soon. I think we will have some way to go. I think the use of blockchains for trading tokens, for handling tokens, and for registering tokens, is an obvious thing, but we also need to bring value to businesses or projects. To have something that people can feel it and control. We need to make sure that information is protected the right way, even though it is registered on a public blockchain, for example.

Il BIP SHOW sbarca in Sud Africa e vi racconta tutto della Adopting Bitcoin 2024 di Cape Town: tra passione e innovazione l'Africa promette davvero di essere la nuova realtà trainante dello sviluppo Bitcoin.Inoltre: visitiamo Bitcoin Ekasi, la comunità rurale che sta adottando Bitcoin nella baraccopoli di Mossel Bay e parliamo di come il Sud Africa oggi sia una terra impoverita e tradita dalla politica, dove il divario sociale e l'inflazione stanno trascinando il popolo nel baratro. It's showtime!

We bring back fertility entrepreneur Dr. John Schnorr to share his experience and advice for building companies in the fertility sector without investor money. Tune in as Dr. Schnorr talks about: Some great examples of how he's proven concept (both functionality & market value) The conditions for bootstrapping without a proven concept How Cycle Clarity gave equity to early employees (and how you might be able to do the same) The pros & cons of hiring top-down in the accountability chart (And bottom-up)

Mark “Murch” Erhardt and Mike Schmidt are joined by Lisa Neigut and Bastien Teinturier to discuss Newsletter #279. News Update to the liquidity ads specification (1:00) Selected Q&A from Bitcoin Stack Exchange Is the Schnorr digital signature scheme a multisignature interactive scheme, and also not an aggregated non-interactive scheme? (38:49) Is it advisable to operate a release candidate full node on mainnet? (41:40) What is the relation between nLockTime and nSequence? (44:40) What would happen if we provide to OP_CHECKMULTISIG more than threshold number (m) of signatures? (52:18) What is (mempool) policy? (54:30) What does Pay to Contract (P2C) mean? (57:31) Can a non-segwit transaction be serialized in the segwit format? (58:18) Releases and release candidates Core Lightning 23.11 (1:00:05) Bitcoin Core 26.0rc3 (1:03:31) Notable code and documentation changes Rust Bitcoin #2213 (1:04:55) BDK #1190 (1:09:04)

Back in 2017, there was no DeFi as we know it today, yet MakerDAO were already envisioning and building towards what they thought to be a certainty. The backbone of DeFi is represented by stable coins, and MakerDAO quickly understood this: they set out to build a decentralised stable coin, $DAI (and its precursor $SAI). Being collateral-backed, the smart contract needs to know the value of that collateral, but any off-chain price data is not readily available on-chain. This is where oracles come in and provide data feeds on-chain. MakerDAO's internal oracle has been active since 2017 on Ethereum and has recently branched out, forming Chronicle. By using aggregated Schnorr signatures, Chronicle solves the problem of oracle cost-efficient scaling.We were joined by Niklas Kunkel, founder of Chronicle, to discuss the challenges and tradeoffs that oracles regularly face, and how Chronicle is solving them, continuing the ethos of early MakerDAO.Topics covered in this episode:Niklas' background and the early days of MakerDAOHow MakerDAO evolved over time and the adoption of DAIMakerDAO's core principlesWhy Chronicle branched out from MakerDAOOracle challenges & tradeoffsOracle validatorsBusiness model for oraclesProviding oracle services to different blockchainsSchnorr signaturesChronicle's supported chains and oracle offeringsReal-world assets (RWA) and credit delegationEpisode links: Niklas Kunkel on TwitterChronicle on TwitterMaker DAO on TwitterThis episode is hosted by Sebastien Couture & Felix Lutsch. Show notes and listening options: epicenter.tv/516

Mark “Murch” Erhardt and Mike Schmidt are joined by Matt Corallo, Brandon Black, Gregory Sanders, and James O'Beirne to discuss Newsletter #266. News Disclosure of past LN vulnerability related to fake funding (21:11) Covenant mashup using `TXHASH` and `CSFS` (1:30) Selected Q&A from Bitcoin Stack Exchange Is there an economic incentive to switch from P2WPKH to P2TR? (34:44) What is the BIP324 encrypted packet structure? (37:31) What is the false positive rate for compact block filters? (39:23) What opcodes are part of the MATT proposal? (40:27) Is there a well defined last Bitcoin block? (41:40) Why are miners setting the locktime in coinbase transactions? (46:10) Why doesn't Bitcoin Core use auxiliary randomness when performing Schnorr signatures? (47:40) Releases and release candidates Core Lightning 23.08 (49:21) LND v0.17.0-beta.rc1 (50:24) Notable code and documentation changes Bitcoin Core #27460 (51:16) LDK #2248 (53:43) LDK #2337 (55:00) LDK #2411 (1:00:16) LDK #2507 (1:04:46) LDK #2478 (1:07:22) LND #7904 (1:09:07)

Here are my 100 interesting things to learn about cryptography: For a 128-bit encryption key, there are 340 billion billion billion billion possible keys. [Calc: 2**128/(1e9**4)] For a 256-bit encryption key, there are 115,792 billion billion billion billion billion billion billion billion possible keys. [Calc: 2**256/(1e9**8)] To crack a 128-bit encryption with brute force using a cracker running at 1 Teracracks/second, will take — on average — 5 million million million years to crack. Tera is 1,000 billion. [Calc: 2**128/100e9/2/60/60/24/365/(1e6**3)] For a 256-bit key this is 1,835 million million million million million million million million million years. For the brute force cracking of a 35-bit key symmetric key (such as AES), you only need to pay for the boiling of a teaspoon of energy. For a 50-bit key, you just need to have enough money to pay to boil the water for a shower. For a 90-bit symmetric key, you would need the energy to boil a sea, and for a 105-bit symmetric key, you need the energy to boil and ocean. For a 128-bit key, there just isn't enough water on the planet to boil for that. Ref: here. With symmetric key encryption, anything below 72 bits is relatively inexpensive to crack with brute force. One of the first symmetric key encryption methods was the LUCIFER cipher and was created by Horst Feistel at IBM. It was further developed into the DES encryption method. Many, at the time of the adoption of DES, felt that its 56-bit key was too small to be secure and that the NSA had a role in limiting them. With a block cipher, we only have to deal with a fixed size of blocks. DES and 3DES use a 64-bit (eight-byte) block size, and AES uses a 128-bit block size (16 bytes). With symmetric key methods, we either have block ciphers, such as DES, AES CBC and AES ECB, or stream ciphers, such as ChaCha20 and RC4. In order to enhance security, AES has a number of rounds where parts of the key are applied. With 128-bit AES we have 10 rounds, and 14 rounds for 256-bit AES. In AES, we use an S-box to scramble the bytes, and which is applied for each round. When decrypting, we have the inverse of the S-box used in the encrypting process. A salt/nonce or Initialisation Vector (IV) is used with an encryption key in order to change the ciphertext for the same given input. Stream ciphers are generally much faster than block cipers, and can generally be processed in parallel. With the Diffie-Hellman method. Bob creates x and shares g^x (mod p), and Alice creates y, and shares g^y (mod p). The shared key is g^{xy} (mod p). Ralph Merkle — the boy genius — submitted a patent on 5 Sept 1979 and which outlined the Merkle hash. This is used to create a block hash. Ralph Merkle's PhD supervisor was Martin Hellman (famous as the co-creator of the Diffie-Hellman method). Adi Shamir defines a secret share method, and which defines a mathematical equation with the sharing of (x,y), and where a constant value in the equation is the secret. With Shamir Secret Shares (SSS), for a quadratic equation of y=x²+5x+6, the secret is 6. We can share three points at x=1, x=2 and y=3, and which gives y=12, y=20, and y=20, respectively. With the points of (1,12), (2,20), and (3,20), we can recover the value of 6. Adi Shamir broke the Merkle-Hellman knapsack method at a live event at a rump session of a conference. With secret shares, with the highest polynomial power of n, we need n+1 points to come together to regenerate the secret. For example, y=2x+5 needs two points to come together, while y=x²+15x+4 needs three points. The first usable public key method was RSA — and created by Rivest, Shamir and Adleman. It was first published in 1979 and defined in the RSA patent entitled “Cryptographic Communications System and Method”. In public key encryption, we use the public key to encrypt data and the private key to decrypt it. In digital signing, we use the private key to sign a hash and create a digital signature, and then the associated public key to verify the signature. Len Adleman — the “A” in the RSA method — thought that the RSA paper would be one of the least significant papers he would ever publish. The RSA method came to Ron Rivest while he slept on a couch. Martin Gardner published information on the RSA method in his Scientific American article. Initially, there were 4,000 requests for the paper (which rose to 7,000), and it took until December 1977 for them to be posted. The security of RSA is based on the multiplication of two random prime numbers (p and q) to give a public modulus (N). The difficulty of RSA is the difficulty in factorizing this modulus. Once factorized, it is easy to decrypt a ciphertext that has been encrypted using the related modulus. In RSA, we have a public key of (e,N) and a private key of (d,N). e is the public exponent and d is the private exponent. The public exponent is normally set at 65,537. The binary value of 65,537 is 10000000000000001 — this number is efficient in producing ciphertext in RSA. In RSA, the ciphertext is computed from a message of M as C=M^e (mod N), and is decrypted with M=C^d (mod N). We compute the the private exponent (d) from the inverse of the public exponent (e) modulus PHI, and where PHI is (p-1)*(q-1). If we can determine p and q, we can compute PHI. Anything below a 738-bit public modulus is relatively inexpensive to crack for RSA. To crack 2K RSA at the current time, we would need the energy to boil ever ocean on the planet to break it. RSA requires padding is required for security. A popular method has been PCKS#1v1.5 — but this is not provably secure and is susceptible to Bleichenbacher's attack. An improved method is Optimal Asymmetric Encryption Padding (OAEP) and was defined by Bellare and Rogaway and standardized in PKCS#1 v2. The main entity contained in a digital certificate is the public key of a named entity. This is either an RSA or an Elliptic Curve key. A digital certificate is signed with the private key of a trusted entity — Trent. The public key of Trent is then used to prove the integrity and trust of the associated public key. For an elliptic curve of y²=x³+ax+b (mod p), not every (x,y) point is possible. The total number of points is defined as the order (n). ECC (Elliptic Curve Cryptography) was invented by Neal Koblitz and Victor S. Miller in 1985. Elliptic curve cryptography algorithms did not take off until 2004. In ECC, the public key is a point on the elliptic curve. For secp256k1, we have a 256-bit private key and a 512-bit (x,y) point for the public key. A “04” in the public key is an uncompressed public key, and “02” and “03” are compressed versions with only the x-co-ordinate and whether the y coordinate is odd or even. Satoshi selected the secp256k1 curve for Bitcoin, and which gives the equivalent of 128-bit security. The secp256k1 curve uses the mapping of y²=x³ + 7 (mod p), and is known as a Short Weierstrass (“Vier-strass”) curve. The prime number used with secp256k1 is 2²⁵⁶-2³²-2⁹-2⁸-2⁷-2⁶-2⁴-1. An uncompressed secp256k1 public key has 512 bits and is an (x,y) point on the curve. The point starts with a “04”. A compressed secp256k1 public key only stores the x-co-ordinate value and whether the y coordinate is odd or even. It starts with a “02” if the y-co-ordinate is even; otherwise, it starts with a “03”. In computing the public key in ECC of a.G, we use the Montgomery multiplication method and which was created by Peter Montgomery in 1985, in a paper entitled, “Modular Multiplication without Trial Division.” Elliptic Curve methods use two basic operations: point address (P+Q) and point doubling (2.P). These can be combined to provide the scalar operation of a.G. In 1999, Don Johnson Alfred Menezes published a classic paper on “The Elliptic Curve Digital Signature Algorithm (ECDSA)”. It was based on the DSA (Digital Signature Algorithm) — created by David W. Kravitz in a patent which was assigned to the US. ECDSA is a digital signature method and requires a random nonce value (k), and which should never be reused or repeated. ECDSA is an elliptic curve conversion of the DSA signature method. Digital signatures are defined in FIPS (Federal Information Processing Standard) 186–5. NIST approved the Rijndael method (led by Joan Daemen and Vincent Rijmen) for Advanced Encryption Standard (AES). Other contenders included Serpent (led by Ross Anderson), TwoFish (led by Bruce Schneier), MARS (led by IBM), and RC6 (led by Ron Rivest). ChaCha20 is a stream cipher that is based on Salsa20 and developed by Daniel J. Bernstein. MD5 has a 128-bit hash, SHA-1 has 160 bits and SHA-256 has 256-bits. It is relatively easy to create a hash collision with MD5. Google showed that it was possible to create a signature collision for a document with SHA-1. It is highly unlikely to get a hash collision for SHA-256. In 2015, NIST defined SHA-3 as a standard, and which was built on the Keccak hashing family — and which used a different method to SHA-2. The Keccak hash family uses a sponge function and was created by Guido Bertoni, Joan Daemen, Michaël Peeters, and Gilles Van Assche and standardized by NIST in August 2015 as SHA-3. Hash functions such as MD5, SHA-1 and SHA-256 have a fixed hash length, whereas an eXtendable-Output Function (XOF) produces a bit string that can be of any length. Examples are SHAKE128, SHAKE256, BLAKE2XB and BLAKE2XS. BLAKE 3 is the fastest cryptographically secure hashing method and was created by Jack O'Connor, Jean-Philippe Aumasson, Samuel Neves, and Zooko Wilcox-O'Hearn. Hashing methods can be slowed down with a number of rounds. These slower hashing methods include Bcrypt, PBKDF2 and scrypt. Argon 2 uses methods to try and break GPU cracking, such as using a given amount of memory and defining the CPU utlization. To speed up the operation of the SHA-3 hash, the team reduced the security of the method and reduce the number of rounds. The result is the 12 Kangaroo's hashing method. The number of rounds was reduced from 24 to 12 (with a security level of around 128 bits). Integrated Encryption Scheme (IES) is a hybrid encryption scheme which allows Alice to get Bob's public key and then generate an encryption key based on this public key, and she will use her private key to recover the symmetric. With ECIES, we use elliptic curve methods for the public key part. A MAC (Message Authentication Code) uses a symmetric key to sign a hash, and where Bob and Alice share the same secret key. The most popular method is HMAC (hash-based message authentication code). The AES block cipher can be converted into a stream cipher using modes such as GCM (Galois Counter Mode) and CCM (counter with cipher block chaining message authentication code; counter with CBC-MAC). A MAC is added to a symmetric key method in order to stop the ciphertext from being attacked by flipping bits. GCM does not have a MAC, and is thus susceptible to this attack. CCM is more secure, as it contains a MAC. With symmetric key encryption, we must remove the encryption keys in the reverse order they were applied. Commutative encryption overcomes this by allowing the keys to be removed in any order. It is estimated that Bitcoin miners consume 17.05 GW of electrical power per day and 149.46 TWh per year. A KDF (Key Derivation Function) is used to convert a passphrase or secret into an encryption key. The most popular methods are HKDF, PBKDF2 and Bcrypt. RSA, ECC and Discrete Log methods will all be cracked by quantum computers using Shor's algorithm Lattice methods represent bit values as polynomial values, such as 1001 is x³+1 as a polynomial. Taher Elgamal — the sole inventor of the ElGamal encryption method — and Paul Koche were the creators of SSL, and developed it for the Netscape browser. David Chaum is considered as a founder of electronic payments and, in 1983, created ECASH, along with publishing a paper on “Blind signatures for untraceable payments”. Satoshi Nakamoto worked with Hal Finney on the first versions of Bitcoin, and which were created for a Microsoft Windows environment. Blockchains can either be permissioned (requiring rights to access the blockchain) or permissionless (open to anyone to use). Bitcoin and Ethereum are the two most popular permissionless blockchains, and Hyperledger is the most popular permissioned ledger. In 1992, Eric Hughes, Timothy May, and John Gilmore set up the cypherpunk movement and defined, “We the Cypherpunks are dedicated to building anonymous systems. We are defending our privacy with cryptography, with anonymous mail forwarding systems, with digital signatures, and with electronic money.” In Bitcoin and Ethereum, a private key (x) is converted to a public key with x.G, and where G is the base point on the secp256k1 curve. Ethereum was first conceived in 2013 by Vitalik Buterin, Gavin Wood, Charles Hoskinson, Anthony Di Iorio and Joseph Lubin. It introduced smaller blocks, improved proof of work, and smart contracts. NI-ZKPs involves a prover (Peggy), a verifier (Victor) and a witness (Wendy) and were first defined by Manuel Blum, Paul Feldman, and Silvio Micali in their paper entitled “Non-interactive zero-knowledge and its applications”. Popular ZKP methods include ZK-SNARKs (Zero-Knowledge Succinct Non-Interactive Argument of Knowledge) and ZK-STARKs (Zero-Knowledge Scalable Transparent Argument of Knowledge). Bitcoin and Ethereum are pseudo-anonymised, and where the sender and recipient of a transaction, and its value, can be traced. Privacy coins enable anonymous transactions. These include Zcash and Monero. In 1992, David Chaum and Torben Pryds Pedersen published “Wallet databases with observers,” and outlined a method of shielding the details of a monetary transaction. In 1992, Adi Shamir (the “S” in RSA) published a paper on “How to share a secret” in the Communications of the ACM. This supported the splitting of a secret into a number of shares (n) and where a threshold value (t) could be defined for the minimum number of shares that need to be brought back together to reveal the secret. These are known as Shamir Secret Shares (SSS). In 1991, Torbin P Pedersen published a paper entitled “Non-interactive and information-theoretic secure verifiable secret sharing” — and which is now known as Pedersen Commitment. This is where we produce our commitment and then show the message that matches the commitment. Distributed Key Generation (DKG) methods allow a private key to be shared by a number of trusted nodes. These nodes can then sign for a part of the ECDSA signature by producing a partial signature with these shares of the key. Not all blockchains use ECDSA. The IOTA blockchain uses the EdDSA signature, and which uses Curve 25519. This is a more lightweight signature version and has better support for signature aggregation. It uses Twisted Edwards Curves. The core signing method used in EdDSA is based on the Schnorr signature scheme and which was created by Claus Schnorr in 1989. This was patented as a “Method for identifying subscribers and for generating and verifying electronic signatures in a data exchange system”. The patent ran out in 2008. Curve 25519 uses the prime number of 2²⁵⁵-19 and was created by Daniel J. Bernstein. Peter Shor defined that elliptic curve methods can be broken with quantum computers. To overcome the cracking of the ECDSA signature from quantum computers, NIST are standardising a number of methods. At present, this focuses on CRYSTALS-Dilithium, and which is a lattice cryptography method. Bulletproofs were created in 2017 by Stanford's Applied Cryptography Group (ACG). They define a zero-knowledge proof as where a value can be checked to see it lies within a given range. The name “bulletproofs” is defined as they are short, like a bullet, and with bulletproof security assumptions. Homomorphic encryption methods allow for the processing of encrypted values using arithmetic operations. A public key is used to encrypt the data, and which can then be processed using an arithmetic circuit on the encrypted data. The owner of the associated private key can then decrypt the result. Some traditional public key methods enable partial homomorphic encryption. RSA and ElGamal allow for multiplication and division, whilst Pailier allows for homomorphic addition and subtraction. Full homomorphic encryption (FHE) supports all of the arithmetic operations and includes Fan-Vercauteren (FV) and BFV (Brakerski/Fan-Vercauteren) for integer operations and HEAAN (Homomorphic Encryption for Arithmetic of Approximate Numbers) for floating point operations. Most of the Full Homomorphic encryption methods use lattice cryptography. Some blockchain applications use Barreto-Lynn-Scott (BLS) curves which are pairing-friendly. They can be used to implement Bilinear groups and which are a triplet of groups (G1, G2 and GT), so that we can implement a function e() such that e(g1^x,g2^y)=gT^{xy}. Pairing-based cryptography is used in ZKPs. The main BLS curves used are BLS12–381, BLS12–446, BLS12–455, BLS12–638 and BLS24–477. An accumulator can be used for zero-knowledge proof of knowledge, such as using a BLS curve to create to add and remove proof of knowledge. Metamask is one of the most widely used blockchain wallets and can integrate into many blockchains. Most wallets generate the seed from the operating system and where the browser can use the Crypto.getRandomValues function, and compatible with most browsers. With a Verifiable Delay Function (VDF), we can prove that a given amount of work has been done by a prover (Peggy). A verifier (Victor) can then send the prover a proof value and compute a result which verifies the work has been done, with the verifier not needing to do the work but can still prove the work has been done. A Physical Unclonable Functions (PUFs) is a one-way function which creates a unique signature pattern based on the inherent delays within the wires and transistors. This can be used to link a device to an NFT.

The CDC estimates 1 in 8 couples have trouble getting pregnant or staying pregnant. But advances in medicine and technology have helped millions of people with infertility bring children into the world. John Schnorr, MD, has overseen the care of thousands of patients with infertility. On this episode, he discusses common causes and the latest treatments offered at MUSC Health and Coastal Fertility Specialists.

So, here's my Top 100 snippets of knowledge for blockchain: Blockchains use public key methods to integrate digital trust. Bob signs for a transaction with his private key, and Alice proves this with Bob's public key. The first usable public key method was RSA — and created by Rivest, Shamir and Adleman. It was first published in 1979 and defined in the RSA patent entitled “Cryptographic Communications System and Method”. Blockchains can either be permissioned (requiring rights to access the blockchain) or permissionless (open to anyone to use). Bitcoin and Ethereum are the two most popular permissionless blockchains, and Hyperledger is the most popular permissioned ledger. Ralph Merkle — the boy genius — submitted a patent on 5 Sept 1979 and which outlined the Merkle hash. This is used to create a block hash. Ralph Merkle's PhD supervisor was Martin Hellman (famous as the co-creator of the Diffie-Hellman method). David Chaum is considered as founders of electronic payments, and, in 1983, created ECASH, along with publishing a paper on “Blind signatures for untraceable payments”. Miners gather transactions on a regular basis, and these are added to a block and where each block has a Merkle hash. The first block on a blockchain does not have any previous blocks — and is named the genesis block. Blocks are bound in a chain, and where the previous, current and next block hashes are bound into the block. This makes the transactions in the block immutable. Satoshi Nakamoto worked with Hal Finney on the first versions of Bitcoin, and which were created for a Microsoft Windows environment. Craig Steven Wright has claimed that he is Satoshi Nakamoto, but this claim has never been verified. Most blockchains use elliptic curve cryptography — a method which was created independently by Neal Koblitz and Victor S. Miller in 1985. Elliptic curve cryptography algorithms did not take off until 2004. Satoshi selected the secp256k1 curve for Bitcoin, and which gives the equivalent of 128-bit security. The secp256k1 curve uses the mapping of y²=x³ + 7 (mod p), and is known as a Short Weierstrass (“Vier-strass”) curve. The prime number used with secp256k1 is ²²⁵⁶−²³²−²⁹−²⁸−²⁷−²⁶−²⁴−1. Satoshi published a 9-page paper entitled “Bitcoin: A Peer-to-Peer Electronic Cash System” White Paper on 31 Oct 31, 2008. In 1997, Adam Black introduce the concept of Proof of Work of Hashcash in a paper entitled, “Hashcash — a denial of service countermeasure.” This work was used by Satoshi in his whitepaper. Satoshi focused on: a decentralized system, and a consensus model and addressed areas of double-spend, Sybil attacks and Eve-in-the-middle. The Sybil attack is where an adversary can take over the general consensus of a network — and leads to a 51% attack, and where the adversary manages to control 51% or more of the consensus infrastructure. Satoshi used UK spelling in his correspondence, such as using the spelling of “honour”. The first Bitcoin block was minted on 3 Jan 2009 and contained a message of “Chancellor on brink of second bailout for banks” (the headline from The Times, as published in London on that day). On 12 Jan 2009, Satoshi sent the first Bitcoin transaction of 50 BTC to Hal Finney [here]. A new block is created every 7–10 minutes on Bitcoin. In Aug 2023, the total Bitcoin blockchain size is 502 GB. As of Aug 2023, the top three cryptocurrencies are Bitcoin, Ether, and Tether. Bitcoin has a capitalization of $512 billion, Ether with $222 billion, and Tether at $83 billion. The total cryptocurrency capitalisation is $1.17 trillion. The original block size was 1MB for Bitcoin, but recently upgraded to support a 1.5MB block — and has around 3,000 transactions. Currently the block sizes are more than 1.7MB. Bitcoin uses a gossip protocol — named the Lightning Protocol — to propagate transactions. A Bitcoin wallet is created from a random seed value. This seed value is then used to create the 256-bit secp256k1 private key. A wallet seed can be converted into a mnemonic format using BIP39, and which uses 12 common words. This is a deterministic key, and which allows the regeneration of the original key in the correct form. BIP39 allows for the conversion of the key to a number of languages, including English, French and Italian. A private key in a wallet is stored in a Wif format, and which is a Base58 version of the 256-bit private key. The main source code for the Bitcoin blockchain is held at https://github.com/bitcoin, and is known as Bitcoin core. This is used to create nodes, store coins, and transactions with other nodes on the Bitcoin network. A 256-bit private key has 115,792 billion billion billion billion billion billion billion billion different keys. A public Bitcoin ID uses Base58 and has a limited character set of ‘123456789ABCDEFGHJKLMN PQRSTUVWXYZabcdefghijkmno pqrstuvwxyz', where we delete ‘0' (zero), ‘l' (lowercase ‘l'), and ‘I' (capital I) — as this can be interpreted as another character. In Bitcoin and Ethereum, a private key (x) is converted to a public key with x.G, and where G is the base point on the secp256k1 curve. An uncompressed secp256k1 public key has 512 bits and is an (x,y) point on the curve. The point starts with a “04”. A compressed secp256k1 public key only stores the x-co-ordinate value and whether the y coordinate is odd or even. It starts with a “02” if the y-co-ordinate is even, otherwise it starts with a “03”. In 1992, Eric Hughes, Timothy May, and John Gilmore set up the cypherpunk movement and defined, “We the Cypherpunks are dedicated to building anonymous systems. We are defending our privacy with cryptography, with anonymous mail forwarding systems, with digital signatures, and with electronic money.” In Ethereum, the public key is used as the identity of a user (a.G), and is defined as a hexademical value. In Bitcoin, the public ID is created from a SHA256 hash of the public key, and then a RIPEMD160 of this, and then covered to Base58. In computing the public key in ECC of a.G, we use the Montgomery multiplication method and which was created by Peter Montgomery in 1985, in a paper entitled, “Modular Multiplication without Trial Division.” Elliptic Curve methods use two basic operations: point address (P+G) and point doubling (2.P). These can be combined to provide the scalar operation of a.G. In 1999, Don Johnson Alfred Menezes published a classic paper on “The Elliptic Curve Digital Signature Algorithm (ECDSA)”. It was based on the DSA (Digital Signature Algorithm) — created by David W. Kravitz in a patent which was assigned to the US. The core signature used in Bitcoin and Ethereum is ECDSA (Elliptic Curve Digital Signature Algorithm), and which uses a random nonce for each signature. The nonce value should never repeat or be revealed. Ethereum was first conceived in 2013 by Vitalik Buterin, Gavin Wood, Charles Hoskinson, Anthony Di Iorio and Joseph Lubin. It introduced smaller blocks, an improved proof of work, and smart contracts. Bitcoin is seen as a first-generation blockchain, and Ethereum as a second-generation. These have been followed by third-generation blockchains, such as IOTA, Cardano and Polkadot — and which have improved consensus mechanisms. Bitcoin uses a consensus mechanism which is based on Proof-of-Work, and where miners focus on finding a block hash that has a number of leading “0”s. The difficulty of the mining is defined by the hashing rate. At the current time, this is around 424 million TH/s. There are around 733,000 unique Bitcoin addresses being used. Satoshi defined a reward to miners for finding the required hash. This was initially set at 50 BTC, but was set to half at regular intervals. On 11 January 2021, it dropped from 12.5 BTC to 6.2 BTC. Bitcoin currently consumes around 16.27 GWatts of power each year to produce a consensus — equivalent to the power consumed by a small country. In creating bitcoins, Satoshi created a P2PKH (Pay to Public Key Hash) address. These addresses are used to identify the wallet to be paid and links to the public key of the owner. These addresses start with a ‘1'. In order to support the sending of bitcoins to and from multiple addresses, Bitcoin was upgraded with SegWit (defined in BIP141). The wallet address then integrates the pay-to-witness public key hash (Pay to script hash — P2SH). These addresses start with a ‘3'. Ethereum uses miners to undertake work for changing a state and running a smart contract. They are paid in “gas” or Ether and which relates to the amount of computation conducted. This limits denial of service attacks on the network and focuses developers on creating efficient code. Ethereum supports the creation of cryptocurrency assets with ERC20 tokens — and which are FT (Fungible Tokens). For normal crypto tokens (ERC-20) we use, there is a finite number of these, and each of these is the same. Ethereum creates NFTs (Non-Fungible Tokens) with ERC721 tokens. We mint these each time and each is unique. Solidity is the programming language used in Ethereum, while Hyperledger can use Golang, Node.js and Java. For Ethereum, we compile Solidity code into EVM (Ethereum Virtual Machine) code. This is executed on the blockchain. Blockchain uses the SHA-256 hash for transaction integrity. Ethereum uses the Keccak hash is used to define the integrity of a transaction. This is based on SHA-3, and differs slightly from Keccak. The Keccak hash family uses a sponge function and was created by Guido Bertoni, Joan Daemen, Michaël Peeters, and Gilles Van Assche, and standardized by NIST in August 2015 as SHA-3. The DAO is a decentralized autonomous organization (DAO) for the Ethereum blockchain and was launched in 2016. In 2016, DAO raised $150 million through a token sale but was hacked and funds were stolen. This resulted in a forking of the blockchain: Ethereum and Ethereum Classic. Non-interactive Zero Knowledge Proofs (NI-ZKP) allow an entity to prove that they have knowledge of something — without revealing it. A typical secret is the ownership of a private key. NI-ZKPs involve a prover (Peggy), a verifier (Victor) and a witness (Wendy) and were first defined by Manuel Blum, Paul Feldman, and Silvio Micali in their paper entitled, “Non-interactive zero-knowledge and its applications”. Popular ZKP methods include ZK-SNARKs (Zero-Knowledge Succinct Non-Interactive Argument of Knowledge) and ZK-STARKs (Zero-Knowledge Scalable Transparent Argument of Knowledge). Bitcoin and Ethereum are pseudo-anonymised, and where the sender and recipient of a transaction, and its value, can be traced. Privacy coins enable anonymous transactions. These include Zcash and Monero. In 1992, David Chaum and Torben Pryds Pedersen published “Wallet databases with observers,” and outlined a method of shielding the details of a monetary transaction. In 1992, Adi Shamir (the “S” in RSA) published a paper on “How to share a secret” in the Communications of the ACM. This supported the splitting of a secret into a number of shares (n) and where a threshold value (t) could be defined for the minimum number of shares that need to be brought back together to reveal the secret. These are known as Shamir Secret Shares (SSS). In 1991, Torbin P Pedersen published a paper entitled “Non-interactive and information-theoretic secure verifiable secret sharing” — and which is now known as Pedersen Commitment. This is where we produce our commitment and then show the message that matches the commitment. Distributed Key Generation (DKG) methods allow a private key to be shared by a number of trusted nodes. These nodes can then sign for a part of the ECDSA signature by producing a partial signature with these shares of the key. Not all blockchains use ECDSA. The IOTA blockchain uses the EdDSA signature, and which uses Curve 25519. This is a more lightweight signature version, and has better support for signature aggregation. It uses Twisted Edwards Curves. The core signing method used in EdDSA is based on the Schnorr signature scheme and which was created by Claus Schnorr in 1989. This was patented as, a “Method for identifying subscribers and for generating and verifying electronic signatures in a data exchange system”. The patent ran out in 2008. Curve 25519 uses the prime number of ²²⁵⁵-19 and was created by Daniel J. Bernstein. Peter Shor defined that elliptic curve methods can be broken with quantum computers. To overcome the cracking of the ECDSA signature from quantum computers, NIST are standardising a number of methods. At present, this focuses on CRYSTALS-Dilithium, and which is a lattice cryptography method. Bulletproofs were created in 2017 by Stanford's Applied Cryptography Group (ACG). They define a zero-knowledge proof as where a value can be checked to see it lies within a given range. The name of “bulletproofs” is defined as they are short, like a bullet, and with bulletproof security assumptions. While Bitcoin can take up to 7–10 minutes to mine a new block and create a consensus, newer blockchains, such as IOTA, can give an almost instantaneous consensus. Banks around the world are investigating CBDC (Central Bank Digital Currency) and which is not a cryptocurrency but a way to quickly define a consensus on a transaction. Homomorphic encryption methods allow for the processing of encrypted values using arithmetic operations. A public key is used to encrypt the data, and which can then be processed using an arithmetic circuit on the encrypted data. The owner of the associated private key can then decrypt the result. Some traditional public key methods enable partial homomorphic encryption. RSA and ElGamal allow for multiplication and division, whilst Pailier allows for homomorphic addition and subtraction. Full homomorphic encryption (FHE) supports all of the arithmetic operations and includes Fan-Vercauteren (FV) and BFV (Brakerski/Fan-Vercauteren) for integer operations and HEAAN (Homomorphic Encryption for Arithmetic of Approximate Numbers) for floating point operations. Most of the Full Homomorphic encryption methods use lattice cryptography. Some blockchain applications use Barreto-Lynn-Scott (BLS) curves which are pairing friendly. They can be used to implement Bilinear groups and which are a triplet of groups (G1, G2 and GT), so that we can implement a function e() such that e(g1^x,g2^y)=gT^{xy}. Pairing-based cryptography is used in ZKPs. The main BLS curves used are BLS12–381, BLS12–446, BLS12–455, BLS12–638 and BLS24–477. An accumulator can be used for zero-knowledge proof of knowledge, such as using a BLS curve to create to add and remove proof of knowledge. Open Zeppelin is an open-source Solidity library that supports a wide range of functions that integrate into smart contracts in Ethereum. This includes AES encryption, Base64 integration and Elliptic Curve operations. Metamask is one of the most widely used blockchain wallets and can integrate into many blockchains. Most wallets generate the seed from the operating system and where the browser can use the Crypto.getRandomValues function, and compatible with most browsers. Solidity programs can be compiled with Remix at remix.ethereum.org. The main Ethereum network is Ethereum Mainnet. We can test smart contracts on Ethereum test networks. Current networks include sepolia.etherscan.io and goerli.net. Ether can be mined for test applications from a faucet, such as faucet.metamask.io. This normally requires some proof of work to gain the Ether — in order to protect against a Denial of Service against the Faucet. The private key can be revealed from two ECDSA signatures which use the same random nonce value. Polkadot is a blockchain which allows blockchains to exchange messages and perform transactions. The proof of work method of creating is now not preference because of the energy that it typically uses. Many systems now focus on proof of stack (PoS). A time-lock puzzle/Proof of Work involves performing a computing task which has a given cost and which cannot be cheated again. This typically involves continual hashing or continual squaring. The Chia blockchain network uses both Proof of Space (PoS) and Proof of Time (PoT). The PoS method makes use of the under-allocation of hard-disk space. With a Verifiable Delay Function (VDF), we can prove that a given amount of work has been done by a prover (Peggy). A verifier (Victor) can then send the prover a proof value and compute a result which verifies the work has been done, with the verifier not needing to do the work but can still prove the work has been done. A Physical Unclonable Functions (PUFs) is a one-way function which creates a unique signature pattern based on the inherent delays within the wireless and transistors. This can be used to link a device to an NFT. In Blockchain applications, we can use Non-interactive zero-knowledge (NIZK) proofs for the equality (EQ) of discrete logarithms (DL) — DLEQ. With this — in discrete logarithms — we have

比特币网络仅仅具有价值存储的意义吗？在比特币Taproot升级激活之后，比特币的多重签名交易更隐私和高效，这又给比特币的网络带来了哪些多样化的可能性？ 本期我们延续第21期关于比特币生态的讨论，再次连线BTCstudy的嘉宾，带我们从叙事的角度理解比特币生态。在Ordinals引发的潮流中，到底该不该向比特币的区块空间里，去写入与比特币密码学安全无关的数据？这期会从比特币叙事的角度全面梳理比特币生态。 【主播】 刘锋，BODL Ventures创始人 @fishkiller 阿伟，Web3主持人 Twitter：@web3awaei 【嘉宾】 阿剑，BTCstudy核心贡献者 Twitter：@AurtrianAjian 曾汨，BTCstudy核心贡献者 Twitter：@zengmi2140 【您将听到】 比特币生态的叙事逻辑与里程碑事件 03:34 作为价值存储体系，围绕比特币安全和去中心化特征产生的三类参与者 08:08 比特币网络自我托管方案：钱包与无需信任的解决方案 16:31 钱包的最优选择：使用原生only链 18:53 BIP32的作用：生成无数个地址，避免公钥和地址的复用（备注：应该为BIP32，播客中BIP39为口误） 22:21 价值存储中的另一关键特性：隐私保护，自由的基石 23:57 价值存储外的两个叙事：支付工具和通用底层协议 27:13 Taproot激活带来的提升：可扩展性和隐私性 34:26 构造条件式支付的核心目标：链上开销最小化，且隐私性也是最好的 比特币二层网络、侧链和智能平台 39:56 Ordinals为比特币NFT带来了更多的玩法 49:27 为何大量比特币原生开发者对新出现的NFT充满了批判：区块体积变大、密码学安全、有更节约的方式去表达 56:12 比特币的魅力：没有人能够定义比特币，只要在协议规范内，任可人可以打扮成想要的样子 58:39 Ordinals出现的原因：跳出价值存储和支付工具叙事框架的比特币 64:25 三个维度去区分智能合约系统的不同属性：计算、验证和访问 70:38 比特币的侧链：RSK、Liquid Network、Stacks 【相关阅读】 比特币全节点状态 (https://bitnodes.io/) ZeroSync 的简单介绍 (https://www.btcstudy.org/2023/03/24/A-light-introduction-to-ZeroSync/) 一笔假装成比特币交易的莱特币交易 (https://monokh.com/posts/ledger-app-isolation-bypass) 理解比特币 Miniscript (https://www.btcstudy.org/2023/03/16/understanding-bitcoin-miniscript-part-1/) Liana 钱包 —— 自定义资产花费条件 (https://wizardsardine.com/liana/) 比特币多签指南 (https://www.btcstudy.org/2022/12/09/a-guide-for-bitcoin-multi-sig-wallets-by-mi-zeng/) 比特币钱包备份方案简史 (https://www.btcstudy.org/2023/04/08/state-of-the-art-for-bitcoin-wallet-backups/) 比特币隐私技术的不完全调查 (https://www.btcstudy.org/2023/03/28/an-incomplete-survey-of-bitcoins-privacy-technologies/) 打浦路（Taproot）比你想的宽 (https://www.btcstudy.org/2021/10/27/taproot-is-more-important-than-your-imageine/) Schnorr 签名如何提升比特币 (https://www.btcstudy.org/2021/09/09/how-schnorr-signatures-may-improve-bitcoin/) 谨慎日志合约（DLC）：比特币的可扩展智能合约 (https://www.btcstudy.org/2022/08/01/discreet-log-contracts-smart-contracts-for-bitcoin/) 什么是比特币默克尔化抽象语法树？ (https://www.btcstudy.org/2021/09/07/what-is-a-bitcoin-merklized-abstract-syntax-tree-mast/) 什么是 “序数 NFT”？ (https://www.btcstudy.org/2023/02/22/ordinal-nfts-inscriptions-digital-artifacts-oh-my/) 纯粹的链下 “染色” 方案 (https://www.btcstudy.org/2023/03/08/purely-off-chain-coin-colouring/) 比特币的可编程性 (https://www.btcstudy.org/2022/09/07/on-the-programmability-of-bitcoin-protocol/) 【BGM】 Mumbai — Ooyy 【团队】 监制｜泓君 后期｜Amie 文案｜Xiaoyang, Yiwen 【在这里找到我们】 中国用户：苹果播客｜小宇宙 海外用户：Apple Podcast｜Spotify｜Google Podcast｜Amazon Music Twitter：@Web3_101 【嘉宾言论仅代表个人，本期节目不构成任何投资建议哦】

Schon mal Mehlwürmer probiert? Oder geröstete Heuschrecken? Insekten als Lebensmittel sind auch hierzulande nicht mehr ungewöhnlich. Aber wie wir sie züchten und ob das in einer nachhaltigen Kreislaufwirtschaft gelingt, dazu sind noch viele Fragen offen. Christian Schnorr promoviert an der Hochschule Fulda im Bereich Lebensmitteltechnologie und will herausfinden, wie Mehlwürmer optimal ernährt werden können. Was diese Arbeit mit Weltraumforschung zu tun hat und wie wählerisch Mehlwürmer sind, erzählt er in dieser Folge des Podcasts. Weitere Infos: ⁠Christian Schnorr, wissenschaftlicher Mitarbeiter an der Hochschule Fulda⁠ Überblick über die Insektenarten und ihr Potenzial: ⁠"Edible insects: future prospects for food and feed security", FAO Forestry Paper, 2013 "Die Zukunft im Blick: Fleisch der Zukunft, Trendbericht zur Abschätzung der Umweltwirkungen von pflanzlichen Fleischersatzprodukten, essbaren Insekten und In-Vitro-Fleisch", Umweltbundesamt, 2020 Risikobewertung als Grundlage der rechtlichen Zulassung mit detaillierten Informationen zur Lebensmittelsicherheit am Beispiel des an der Hochschule beforschten Mehlwurms: "Safety of dried yellow mealworm (Tenebrio molitor larva) as a novel food pursuant of Regulation (EU) 2015/2283", EFSA journal, 2021

Mark “Murch” Erhardt and Mike Schmidt are joined by Valentine Wallace to discuss Newsletter #235. News Ephemeral anchors compared to `SIGHASH_GROUP` (0:58) Request for proof that an async payment was accepted (12:04) Selected Q&A from Bitcoin Stack Exchange Bitcoin Core signing keys were removed from repo. What is the new process? (27:53) Why doesn't signet use a unique bech32 prefix? (31:36) Arbitrary data storage in witness? (34:07) Why is the locktime set at transaction level while the sequence is set at input level? (38:35) BLS signatures vs Schnorr (42:30) Why exactly would adding further divisibility to bitcoin require a hard fork? (46:56) Notable code and documentation changes Bitcoin Core #26325 (55:20) Libsecp256k1 #1192 (57:37) BIPs #1383 (1:00:22)

We've talked about how quantum computers are enabling extraordinary use cases now, long before the machines will threaten cryptography. Some of these applications can even help companies protect against immediate security threats and vulnerabilities. We explore one such exciting experiment: Using quantum to stop kill chains that allow network exploitation and the Chinese paper causing all the ruckus, claiming that cryptography could be hacked any day now. Join host Konstantinos Karagiannis for a chat about these hacker topics with Mark Carney from Quantum Village.For more on Quantum Village, visit www.quantumvillage.org/.To read Mark's paper on stopping kill chains, visit https://arxiv.org/abs/2211.13740.Read the Chinese paper causing all the ruckus on potentially cracking RSA sooner than expected: https://arxiv.org/abs/2212.12372Visit Protiviti at www.protiviti.com/postquantum to learn more about how Protiviti is helping organizations get post-quantum ready.Follow host Konstantinos Karagiannis on Twitter and Instagram: @KonstantHacker and follow Protiviti Technology on LinkedIn and Twitter: @ProtivitiTech. Contact Konstantinos at konstantinos.karagiannis@protiviti.com.Questions and comments are welcome!Theme song by David Schwartz. Copyright 2021.

This week, Dr. John Schnorr joins Griffin to breakdown what transpired when he and his colleagues found themself at the bottom of the Integramed fallout. What happened to his clinic and his patients through the unraveling, how did it influence his career path afterward, and what entrepreneurial venture did he undertake as a result- all on this week's episode of Inside Reproductive Health. Listen to hear: What happens when another company is the employer of your employees-and they close their doors overnight-without paying you-or anyone else. What considerations you should make before you enter into an agreement with any company- especially when the rules for assignment change drastically under the umbrella of bankruptcy law. How Dr. Schnorr rose from this downturn, and continued down an entrepreneurial AI path that has the potential to significantly impact the industry down the line.

Discount link: https://hardblock.com.au/join/ozbitcoinpod Guest: https://twitter.com/llfourn (https://github.com/llfourn) - Contact Lloyd to work on bitcoin development with him in Malaysia! Host: https://twitter.com/mission_bitcoin Notes - Lloyd's bitcoin journey and getting into bitcoin (and cryptography) development - Developing the GUN (Go Up Number) command line interface bitcoin wallet - Developing the stripped-down DLC (discrete log contracts) betting/wager extension for GUN - Working on FROST, a new multi-signature protocol that uses Schnorr threshold signatures with a single public key (rather than multiple public keys being disclosed on the blockchain like in 'traditional' multi-signature protocols) - Privacy-improving and data-saving (leading to fee-reducing) affects of Schnorr signature aggregation - History of why ECDSA (elliptic curve digital signature algorithm) was used initially over Schnorr signatures (spoiler: it's related to patents) - Lightning Network (LN) privacy considerations: - Where (on-chain) are your LN channel open transactions originating from? - Practical tip: using coinjoins or coinswaps before opening LN channels can improve privacy - Privacy versus convenience trade-offs when sending LN directly to your recipient versus sending via multiple intermediary hops first - More hops on a LN payment pathway is not always better (eg, it can lead to payment failure, and could erode privacy if multiple of those routing nodes are surveilling the network)) - Practical tips: keep all your channels unannounced ("private") and only connect with nodes you trust are not performing network surveillance - Will PTLCs (point time locked contracts) improve LN privacy more than currently-used HTLCs (hashed time lock contracts)? - Channel probing attacks exist today to discover "private" (ie, unannounced) LN channels and to determine their channel balance; this is exacerbated by public channels announcing all of their identifying details (which makes process-of-elimination and brute-force attacks more viable on the remaining unannounced channels) - What you do with your on-chain coins (UTXOs) after closing a LN channel can be important with regard to privacy; in fact, what your channel partners do with their on-chain UTXOs post channel close can also impact your privacy! - Practical tip: coinswap or coinjoin your left-over UTXO after closing a LN channel - Cross-layer links (ie, base-layer and LN layer) are bad for privacy, but some improvements are coming (eg, using unique channel aliases/IDs with each LN node you connect with, rather than a reused channel ID that can be linked easily back to your on-chain UTXO) - Practical tip: run your own node (but be mindful it can be done badly - there are cases when using a trusted third party may be better) - LN sender-side privacy is generally better than receiver-side, as a LN invoice to receive a payment will leak private information (eg, which UTXO belongs to the node) - Practical tip: don't re-use LN invoices - A potential LN privacy and convenience solution: using payment hubs, similar to the Tumblebit proposal and Chaumian e-cash mints (eg, FediMint or MiniMint), but with added improvements with regards to custody of funds and transaction output size - Attending the Asia-Pacific Bitcoin Socratic to help flesh out bitcoin improvements References https://bitcoinproblems.org https://github.com/bitcoin-sydney/socratic https://abytesjourney.com/lightning-privacy

In this episode of the Crack House Chronicles, Donnie and Dale discuss Brian James Dugan who is a convicted rapist and serial killer who was active between 1983 and 1985 in Chicago's western suburbs. He was known for having informally confessed in 1985 to the 1983 abduction, rape and murder of 10-year-old Jeanine Nicarico of Naperville, Illinois, which was a highly publicized case. He was already in custody for two other rape/murders, one of an adult woman in 1984 and the other a female child in 1985. He was sentenced to life after pleading guilty to the latter two crimes. https://crackhousechronicles.com/ Check out our MERCH! https://www.teepublic.com/user/crackhousechronicles Sponsors: https://betterhelp.com/chc If you use this link or Promo Code CHC, BetterHELP will give you 10% off your first months bill. Sources: https://en.wikipedia.org/wiki/Brian_Dugan https://murderpedia.org/male.D/d/dugan-brian-james.htm https://www.chicagotribune.com/news/ct-brian-dugan-serial-killer-interview-met-20141212-story.html  

Torniamo a parlare della sempiterna questione del consumo energetico di Bitcoin. Il dibattito sulla questione si arroventa negli Stati Uniti, ma nuove prove sul campo dimostrano come il mining sia una risorsa assolutamente fondamentale per abbattere l'emissione di inquinanti ed efficientare la griglia di distribuzione della corrente elettrica.Inoltre ci sono aggiornamenti sul dibattito in merito alla controversa proposta di aggiornamento BIP119 e un eccellente studio universitario tasta il polso a Bitcoin come legal tender in El Salvador.Lift off

Un DLC es un protocolo que nos permite hacer transacciones de Bitcoin condicionadas al resultado de un evento y de forma totalmente privada para la cadena de bloques. Los DLCs habilitan contratos inteligentes invisibles en Bitcoin y abren la puerta de par en par a que empresas construyan p.ej. soluciones financieras, de forma nativa y sin recurrir a sidechains ni a otras cadenas alternativas. En el pod de hoy con Lucas Soriano repasamos a nivel transacción y criptografía: Qué es un DLC Sus elementos básicos, los scriptless scripts y adaptor signatures Schnorr y ECDSA Construimos un DLC paso a Paso El oráculo y sus posibles ataques El potencial y uso actual de los DLCs Y las empresas que ya están cosntruyendo sobre ellos Un pod delicioso para los que les gusta entender cómo funcionan las cosas en Bitcoin Links Podcast: Link Comit Network: https://comit.network/ CFDs sobre DLCs ItchySats: https://www.itchysats.network/ Link SuredBits: https://suredbits.com/ Wallet para hacer DLCs Bitcoin-S https://github.com/bitcoin-s/bitcoin-s/releases Participa en un DLC futbolítico en: https://t.me/laligaDLC Haz tu oráculo con Krystal Bull https://github.com/bitcoin-s/krystal-bull/releases/tag/1.4.0 Opciones en DLCs https://atomic.finance/ Más información en https://lunaticoin.com Apoya el podcast en Patreon https://bit.ly/Patreon_Luna Mención especial a los sponsors de este podcast: Compra bitcoin sin KYC en HodlHodl: https://bit.ly/hodlhodl-luna Infórmate sobre Minería en Braiins: https://bit.ly/Braiins_Luna Vive con cripto en Bitrefill: https://bit.ly/Bitrefill_Luna Protege tu tráfico online con IVPN https://tiny.one/IVPNLuna Toma prestado con bitcoin en http://bit.ly/Lend_Lunaticoin

The Holy Bible~Revelation 6 (Audio Bible NKJV) 1 Now I saw when the Lamb opened one of the seals; and I heard one of the four living creatures saying with a voice like thunder, “Come and see.” 2 And I looked, and behold, a white horse. He who sat on it had a bow; and a crown was given to him, and he went out conquering and to conquer. 3 When He opened the second seal, I heard the second living creature saying, “Come and see.” 4 Another horse, fiery red, went out. And it was granted to the one who sat on it to take peace from the earth, and that people should kill one another; and there was given to him a great sword. 5 When He opened the third seal, I heard the third living creature say, “Come and see.” So I looked, and behold, a black horse, and he who sat on it had a pair of scales in his hand. 6 And I heard a voice in the midst of the four living creatures saying, “A quart of wheat for a denarius, and three quarts of barley for a denarius; and do not harm the oil and the wine.” 7 When He opened the fourth seal, I heard the voice of the fourth living creature saying, “Come and see.” 8 So I looked, and behold, a pale horse. And the name of him who sat on it was Death, and Hades followed with him. And power was given to them over a fourth of the earth, to kill with sword, with hunger, with death, and by the beasts of the earth. 9 When He opened the fifth seal, I saw under the altar the souls of those who had been slain for the word of God and for the testimony which they held. 10 And they cried with a loud voice, saying, “How long, O Lord, holy and true, until You judge and avenge our blood on those who dwell on the earth?” 11 Then a white robe was given to each of them; and it was said to them that they should rest a little while longer, until both the number of their fellow servants and their brethren, who would be killed as they were, was completed. 12 I looked when He opened the sixth seal, and behold, there was a great earthquake; and the sun became black as sackcloth of hair, and the moon became like blood. 13 And the stars of heaven fell to the earth, as a fig tree drops its late figs when it is shaken by a mighty wind. 14 Then the sky receded as a scroll when it is rolled up, and every mountain and island was moved out of its place. 15 And the kings of the earth, the great men, the rich men, the commanders, the mighty men, every slave and every free man, hid themselves in the caves and in the rocks of the mountains, 16 and said to the mountains and rocks, “Fall on us and hide us from the face of Him who sits on the throne and from the wrath of the Lamb! 17 For the great day of His wrath has come, and who is able to stand?” Read the Bible daily, or listen to the audio Bible daily to grow in your faith, knowledge, and love towards God! God Confronts Adam and Eve / By Julius Schnorr von Carolsfeld / Woodcut, coloured. Schnorr von Carolsfeld, Julius; 1794–1874. From: "Die Bibel in Bildern" (The Bible in Pictures), Leipzig (Georg Wigand) 1860, image no. 9. Berlin, Sammlung Archiv für Kunst und Geschichte. Identifier AKG135854 The Christian Martyrs' Last Prayer by Jean-Léon Gérôme (1883)/Wikimedia Common Artwork by Randall Fischer Image by Benjamin Haas from Shutterstock No copyright music by: Serjo De Lua https://soundcloud.com/keysofmoon --- Send in a voice message: https://anchor.fm/thedayofthelordisnear/message

Mario Gibney is the Community Manager at LEDN, he was formerly at Blockstream and he is also the co – host of the Unhashed Podcast. Mario sits down with Cedric to dicsuss:  - His rabbit hole story - How financial services for Bitcoin works while having to account for liquidity, collateral requirements and price volatity  - What is the UTXO set - Why were SegWit and Taproot such important upgrades to the Bitcoin Network and what do they do for it - Schnorr signatures, consensus, his favorite part of Bitcoin and so much more LEDN is a secure, simple and easy to use platform for managing and growing your digital wealth. If you want to see what it's all about and get $50 free in USDC when you take out your first LEDN loan head over to www.start.ledn.io/bitcoinmatrix The Bitcoin 2022 Conference celebrates bitcoin over 4 days (April 6-9th, 2022) with 4 different passes. The four days include Industry day, 2 days of main events and speakers, and lastly, a festival day which is a day of music and networking.  Prices will continue to rise over the next few months so get in early and use the code BitcoinMatrix for 10% off at https://b.tc/conference Make sure to subscribe, listen, learn and share The Bitcoin Matrix Podcast. Folllow Mario Gibney on twitter at @Mario_Gibney Follow LEDN at https://ledn.io/en/ Follow The Bitcoin Matrix Podcast on twitter at @DeLaBtcMatrix Follow Ced on Twitter at @CedYoungelman iTunes: tinyurl.com/bitcoinitunes YouTube: https://tinyurl.com/bitcoinonyoutube Google Podcasts: https://https://tinyurl.com/bitcoingoogle https://www.facebook.com/TheBitcoinMatrixPodcast Web: https://bitcoinmatrix.libsyn.com/ Spotify: https://tinyurl.com/bitcoinspotify

En esta segunda parte de la serie sobre Taproot, vamos a charlar con Diego Gurpegui sobre esta esperada actualización desde una óptica menos abstracta y más concreta. Hablamos sobre lo que es y no es Taproot, sobre sus componentes, tales como las firmas Schnorr, Mast, Musig, Tapscript, etc., y además nos animamos a conversar sobre otras cosas como DLCs y Eltoo. No te lo podés perder. Dale play y sumate al PlebsCast!

Entenda mais sobre taproot e conheça a saga realizada por esses três programadores brasileiros que fizeram as primeiras transações desse tipo da história do bitcoin. MINUTAGEM 00:00 Abertura 01:05 Relembrando o que é o Taproot 06:00 Privacidade com o Taproot 08:52 Schnorr signatures e smart contracts 10:47 Lightning network e smart contracts 12:10 MAST 14:16 BIP 340, 341, 342 e 114 15:00 A jornada para realizar as primeiras transações taproot 20:22 Transações fora do padrão e por que os mineradores não ¨pegaram¨ essas transações 31:40 Bloco de ativação confirmou...e nada 41:45 A nova geração de programadores bitcoinheiros brasileiros 44:48 A influência do Narcélio na comunidade de bitcoinheiros 46:00 Tamanho e a qualidade da comunidade de programadores no Brasil LINK https://twitter.com/jaonoctus/status/1459880438508494852?s=21 Quer gastar Bitcoin? Veja primeiro se pode usar algum gift card da nossa patrocinadora Bitrefill!Acesse https://www.bitrefill.com/ ________________ APOIE O CANAL https://bitcoinheiros.com/apoie/ Loja dos Bitcoinheiros https://loja.bitcoinheiros.com/ SIGA OS BITCOINHEIROS: Site: https://www.bitcoinheiros.com Youtube: https://www.youtube.com/bitcoinheiros Twitter: https://www.twitter.com/bitcoinheiros Allan - https://www.twitter.com/allanraicher Dov - https://twitter.com/bitdov Becas - https://twitter.com/bksbk6 Ivan - https://twitter.com/bitofsilence Instagram: https://www.instagram.com/bitcoinheiros Facebook: https://www.fb.com/bitcoinheiros Podcast: https://anchor.fm/bitcoinheiros APOIE O CANAL: - Dê uma gorjeta em Bitcoin: https://bitcoinheiros.com/apoie/ - Inscreva-se no canal - Deixe seu comentário no vídeo - Dê um like no vídeo - Compartilhe o vídeo e o canal com amigos e familiares na sua rede social - Envie um email com seu comentário e sugestões: bitcoinheiros@protonmail.com COMO GUARDAR SEUS BITCOINS? Bitcoinheiros recomendam o uso de carteiras Multisig com Hardware Wallets de diferentes fabricantes. Busque por "canivete bitcoinheiro" em nosso canal para saber mais. - COLDCARD - https://store.coinkite.com/promo/bitcoinheiros (use o código bitcoinheiros para ganhar 5% de desconto) - TREZOR E BITBOX02 PARA RESIDENTES NO BRASIL E AMÉRICA DO SUL Revendedor oficial: https://www.kriptobr.com/?afiliado=1288 Acesse com nosso link acima para ajudar o canal! ;) - TREZOR PARA RESIDENTES EM OUTROS PAÍSES https://shop.trezor.io/product/trezor-model-t?offer_id=15&aff_id=3722 ISENÇÃO DE RESPONSABILIDADE: Este conteúdo foi preparado para fi --- Send in a voice message: https://anchor.fm/bitcoinheiros/message

Taproot foi ativado neste domingo de madrugada em Brasília, no bloco 709632 da Timechain. Mas o que isso significa? O que são as assinaturas Schnorr? Quais são os benefícios de MAST? E quais são as carteiras que já têm suporte para a nova tecnologia? Entenda qual é a situação do Taproot nestes primeiros dias de adoção. Links para aprofundar ainda mais: https://en.bitcoin.it/wiki/Bech32_adoption https://bitcoinmagazine.com/technical/bitcoin-taproot-explainer https://river.com/learn/what-is-taproot/ https://bitcoinops.org/en/topics/taproot/ https://bitcoinops.org/en/topics/tapscript/ Se você não tem uma carteira Bitcoin, veja algumas opções aqui: https://bitcoinheiros.com/projetos-recomendados/ Quer gastar Bitcoin? Veja primeiro se pode usar algum gift card da nossa patrocinadora Bitrefill!Acesse https://www.bitrefill.com/ ________________ APOIE O CANAL https://bitcoinheiros.com/apoie/ Loja dos Bitcoinheiros https://loja.bitcoinheiros.com/ SIGA OS BITCOINHEIROS: Site: https://www.bitcoinheiros.com Youtube: https://www.youtube.com/bitcoinheiros Twitter: https://www.twitter.com/bitcoinheiros Allan - https://www.twitter.com/allanraicher Dov - https://twitter.com/bitdov Becas - https://twitter.com/bksbk6 Ivan - https://twitter.com/bitofsilence Instagram: https://www.instagram.com/bitcoinheiros Facebook: https://www.fb.com/bitcoinheiros Podcast: https://anchor.fm/bitcoinheiros APOIE O CANAL: - Dê uma gorjeta em Bitcoin: https://bitcoinheiros.com/apoie/ - Inscreva-se no canal - Deixe seu comentário no vídeo - Dê um like no vídeo - Compartilhe o vídeo e o canal com amigos e familiares na sua rede social - Envie um email com seu comentário e sugestões: bitcoinheiros@protonmail.com COMO GUARDAR SEUS BITCOINS? Bitcoinheiros recomendam o uso de carteiras Multisig com Hardware Wallets de diferentes fabricantes. Busque por "canivete bitcoinheiro" em nosso canal para saber mais. - COLDCARD - https://store.coinkite.com/promo/bitcoinheiros (use o código bitcoinheiros para ganhar 5% de desconto) - TREZOR E BITBOX02 PARA RESIDENTES NO BRASIL E AMÉRICA DO SUL Revendedor oficial: https://www.kriptobr.com/?afiliado=1288 Acesse com nosso link acima para ajudar o canal! ;) - TREZOR PARA RESIDENTES EM OUTROS PAÍSES https://shop.trezor.io/product/trezor-model-t?offer_id=15&aff_id=3722 ISENÇÃO DE RESPONSABILIDADE: Este conteúdo foi preparado para fins meramente informativos. NÃO é uma recomendação financeira nem de investimento. As opiniões apresentadas são apenas opiniões. Faça sua própria pesquisa. Não no --- Send in a voice message: https://anchor.fm/bitcoinheiros/message

Our guest for today is Tom Schnorr, owner and pharmacist from Austin Compounding Pharmacy. CBD is a long time argued drug in the world. For this podcast, Stephen Dunn and Tom Schnorr will explain everything about it. Its different uses, how to take it and all we need to know. So, how about it. Are you ready? Let's go! In this episode: 01:53 - Stephen shares a story of how he became interested in the use of CBD. 04:25 - Tom tells people a bit about himself. 06:33 - Tom shares his thoughts about marijuana. 07:48 - Tom explains the ins and outs on how to use CBD. 12:29 - Can CBD help you or your dog? 13:17 - Tom talks about the different kinds of CBD doses. 14:22 - How do you take CBD? 15:36 - Tom talks about where can people get CBD. 15:53 – Tom explains the components of CBD. 16:34 – Tom talks about things that has CBD. 18:08 - Is the CBD psychoactive? Facebook: https://www.facebook.com/drugschnorr Email: drugschnorr@gmail.com Website: http://austincompoundingpharmacy.com/ LinkedIn: https://www.linkedin.com/in/tom-schnorr-5360487/ --- Send in a voice message: https://anchor.fm/stephen-dunn/message

Anatoly Yakovenko (00:12):Hey folks, this is Anatoly, and you're listening to The Solana Podcast. And today I have Jonathan Schemoul with me, who's the founder of the Aleph.im project. Really awesome to have you.Jonathan Schemoul (00:22):Thank you very much. I'm really happy to be here today.Anatoly Yakovenko (00:25):Cool. We usually start these with a simple question, how did you get into crypto? What's your story? What's the origin story?Jonathan Schemoul (00:36):Well, into crypto it's a long story. I started way back in time, a bit on Bitcoin then I stopped because it was only money back then. And that wasn't the end game for me. Then I came back into crypto in 2015, 2016, and I started doing a bit of development because I saw that I really wanted to be part of Web 3, to do nice things with it. I started developing as an open-source developer for a few projects. One of these is the newest project which is Chinese blockchain layer one. I'm not really involved with it anymore.Jonathan Schemoul (01:16):But working with them as a community open source developer, I saw that there was some missing links somewhere that you couldn't decentralize all the stack with just layer one, it is not the one that they were building back then. So that's how the Aleph.im project is born. For me, besides that, I've been developing for a lot of companies before in the IOT space and also for big banks sometime ago. I've been a developer for a lot of years.Anatoly Yakovenko (01:48):That's great. I mean, that's a great background. The thing that you're focusing on with Aleph is this idea that Web 3 is just a small part of the piece, but you still need UI front-ends, business logic and things sitting on top of the blockchain. How does that work?Jonathan Schemoul (02:09):The idea is that, okay, now you can have smart contracts on Solana, that's great. You can even do way much more on like just money on smart contracts, that's great. Now, you need to have a front-end. So you need to have storage for that front-end. That's not all because a smart contract, a program doesn't have all the data that you need. So you will need some kind of indexing to get history. You will need a back-end for that.Jonathan Schemoul (02:37):Most of the DeFi application that we see have some centralized back-end behind them. They're running on AWS, sometimes on dedicated servers or stuff like that that is still centralized. If a government, and we just saw something about it today, wants to shut down the DeFi protocol that is organized like that, they can. With Aleph.im what we are trying to do is decentralize the last mile, because for that last mile most projects are using AWS, so we need to decentralize AWS.Jonathan Schemoul (03:11):So we provide storage, as in file storage for the front-end files, database storage, because most applications are just databases and also an equivalent to Amazon Lambda, where you start small functions that will be launched on a decentralized cloud, where there is place for them and will get you a return value, and these can be written in any language and connects the web and also a PC from blockchains here at Solana obviously.Anatoly Yakovenko (03:42):Got it. Super Cool. So this is a storage mechanism. Does it guarantee consistency? How's it decentralized? What happens if you nuke it? Yellowstone flows up, the current set of servers from Aleph get destroyed in the volcano. How do I move, switch, what state do I lose? Those are the hard distributed systems question.Jonathan Schemoul (04:08):Yeah. It's a really good question. Aleph.im is not a blockchain at all. We don't have a blockchain. There are enough already. We just accept messages from blockchains. All the supported blockchains are accepted on the network, that means that that message that is signed by a material address is accepted on network, a message that is signed by a certain address is accepted on the network. All our network, hence the name .im, dot instant messaging, the whole system works with messages on the network.Jonathan Schemoul (04:45):Those messages are organized by channels, just like you would go on telegram channels and get the history of them. The network keeps track of those messages and when you start a new node, you get the history of messages, not directly from the other nodes, you will connect two blockchains to specific smart contracts on blockchain. Look at past events, for example, on the Ethereum or on Solana. You look at past events for the synchronization of the network and you look, okay, there has been all these events, okay, let me ask the whole network what those messages were. Then you resync, when there are missing parts you leave them apart and then you get a view on the channels on the messages.Anatoly Yakovenko (05:31):So you write your software, your Lambda hook as if it's a re-entrant, right? So you're kind of recording your progress potentially on Solana as you're processing it.Jonathan Schemoul (05:43):For the Lambda it's a bit different. Here I was explaining how the network works for the messaging on the global state. For the state of pure application, you could either get your state from a blockchain here at Solana. For example, all the indexing effort that we are doing is using Solana as a source of synchronization for these Lambda. But then you can have multiple kind of volumes because since it's Linux Micro VM machine, everything is a volume.Jonathan Schemoul (06:18):So we have local storage volume that is local to the running host. And then the Lambda kind of issue messages on a decentralized database of data and project or under storage, and then raising to the local file system and then issue messaging, et cetera. And we are also working on another kind of phase system that is distributed, where any of them that can write in it on the overall receive the changes, which is kind of tricky.Anatoly Yakovenko (06:48):Is the database, the Aleph database, distributed database? Is that a Byzantine fault-tolerant database? Is it designed with that in mind?Jonathan Schemoul (06:58):Yeah. The idea is that when you send a message on the network, it gets stored by all the over nodes that are interested in your channel. And then there are synchronization node that go and write hashes of the data and signatures inside messages that they push on blockchains. So that when overcome, they can synchronize it and replicate all the data. So that even if one part of the network gets totally disconnected, you can have one part that gets reconnected to the other therefore the peer to peer network for blockchain, for APFS. We have multiple kind of different connectivity solutions so that they can reconnect on resync.Anatoly Yakovenko (07:42):So the Aleph database, if it's Byzantine fault tolerant, I mean, doesn't that make it a blockchain? Is there a token? Is crypto economically like fault tolerant?Jonathan Schemoul (07:56):Yeah. So we have a token, but the token is living on multiple blockchain, Ethereum, Solana, and a few others, but those are the most used today. We have a token, you need a token for your data to stay there. If you don't have any more your data gets garbage collected. But we don't have a blockchain because we go and write on over layer ones. We are technically a layer two database which is computing pre storage.Anatoly Yakovenko (08:23):But the data storage, like the Aleph distributed database, what is that backed by? Or can I pick my own blockchain to use it as a common interface or something like that?Jonathan Schemoul (08:34):Well, currently it writes on Ethereum, we're working on making it write on Solana. For this we need our indexer to be super powerful. So we'll get it writing on Solana very soon. Basically you can write on multiple blockchains and use it as a source of proof.Anatoly Yakovenko (08:53):Got it. That's pretty interesting. So it really doesn't have its own blockchain and you're just using the fault tolerance of the chains you're connected to.Jonathan Schemoul (09:04):Exactly.Anatoly Yakovenko (09:06):Awesome. Yeah, that's really cool. So the other challenge I think is like how do you deal with domains and the web? Where do you run these executed nodes? How do you connect all those pieces?Jonathan Schemoul (09:20):It's a really good question. To connect all the pieces together, we didn't develop some really fancy stuff like proof of space and time and things like that to verify that the data is really stored. We are using something much more low-tech, which is just a quality control. We have core channel nodes, which are the controllers of the network, which needs to keep some Aleph have stakers on such economics. They are verifying that other core channel nodes are behaving well. And that also the resource nodes are behaving well. Then the resource nodes are really doing the work of storing data, providing computing, et cetera. And they're continuously controlled by the core channel nodes.Anatoly Yakovenko (10:09):That's great. So they're basically like a tokenized health check, right?Jonathan Schemoul (10:14):Yeah.Anatoly Yakovenko (10:14):I can spin this up and they can continuously monitor whether this computation is making progress, right?Jonathan Schemoul (10:21):Exactly.Anatoly Yakovenko (10:21):Is that verification, is that programmable? Can me as an app developer, can I kind of code up my own apps, specific health checks or an interface or something like that?Jonathan Schemoul (10:35):It's a really good question. That's what we are working on exactly right now.Anatoly Yakovenko (10:40):I'm leaking all the features. My imagination is going.Jonathan Schemoul (10:44):No, no worry. Well, it's really interesting because to understand if an application behaves well on one host, you need to understand what the application is doing. So yes, we will give some kind of health check, which is kind of a unit test of how the app should work. So you will be able to provide unit tests for your app basically.Anatoly Yakovenko (11:11):That's really Cool. What about domains? Like actual DNS?Jonathan Schemoul (11:17):Yeah.Anatoly Yakovenko (11:20):I'm asking all the hard questions.Jonathan Schemoul (11:22):Yeah. These questions will be answered if I explain how we handle access to this virtual machine. Because for DNS, for just IPFS, there is already quite a few solution, that's not an issue. But then if you want to make a domain point to one micro VM, you want your micro VM to be able to serve your data. How we do first the load balancing because that's the important question. For load balancing we have two ways, one, which is a regular cloud load balancing, which could be blocked by government, could be censored, because that's what can happen when you have centralized point of control.Jonathan Schemoul (12:07):We will run it ourselves and a few of our partners might run some of the cloud load balancers that basically you can just point your domain to the cloud load balancer. And then the cloud load balancer will create certificates and stuff like that. It will work. We will run one instance. Ubisoft will likely run another. And like many of our partners. Well, for Ubisoft it's not sure, just some talks about it. But perhaps over partners could run cloud load balancers that we'd go on point on specific micro VM host to see where your app is running and point it to them, that might work.Jonathan Schemoul (12:48):Now What happens if a government says, "This app shouldn't work, this domain shouldn't work." Then you have two solutions, you either put the front-end inside IPFS, use some IPFS gateways, et cetera. And then the back-end is on the VM network. But then what happens if a government blocks the specific DNS inside the micro VM global.aleph.sh .aleph.cloud Whatever. Then we have a decentralized load balancing that comes into play.Jonathan Schemoul (13:24):The idea of the decentralized load balancing is that your browser will connect to the IPFS network using leap peer to peer, just leap peer to peer, find Pi Aleph nodes running, contact them directly then ask Pi Aleph node, "What micro VM host are running this software?" And then you can contact them directly. We are working on the JavaScript library that will do all this work on the client side so that you can have your front-end in IPFS that will then go and find all the back-end hosts that could answer your request.Anatoly Yakovenko (13:58):That's super cool. You guys are working on some really hard problems. I think it should be fairly easy to kind of have basically a resolver that points to ENS in the system, right. That's fairly straightforward. And basically you should be able to use any kind of like name, system, command any blockchain.Jonathan Schemoul (14:25):Yeah, clearly.Anatoly Yakovenko (14:26):Do you think that this is something that browsers are starting to recognize as standardizable? Is there a future where you think this technology could start percolating to the UI level where the end user can pick like blockchain based DNS resolver that kind of like connects all the pieces, right? From the human to this decentralized one.Jonathan Schemoul (14:51):I think that something that could come, I think that those that could really help in this is Mozilla foundation, I think that they would be the one to talk with. We aren't in talk with them because we don't really take that step right now. We have a lot on our plate. But in the future I'm pretty sure it's the way to go. We will connect to any effort in that area and we will recognize it. I know that for IPFS for example, IPFS, IPNS, there are some efforts on some browser extension that you can install to have it, et cetera.Anatoly Yakovenko (15:29):How does like certificate chaining play with us? What happens if I need to have a cert on my service and things like that.Jonathan Schemoul (15:38):A certificate on your service? Yeah.Anatoly Yakovenko (15:41):Like their sign or whatever.Jonathan Schemoul (15:43):Well, we use the one that everyone uses, which is-Anatoly Yakovenko (15:48):Let's Encrypt. The EFF one.Jonathan Schemoul (15:49):Yeah, exactly. We're using this one, we used the discovery with the content, so that we switch to a specific content when Let's Encrypt connects, then we serve this content, then we get a valid certificate, we can serve the good content.Anatoly Yakovenko (16:07):Can you unpack that a little bit?Jonathan Schemoul (16:10):Yeah. Well, Let's Encrypt has multiple ways to certify that you have a certain domain, for sub domains of .aleph.sh and .aleph.cloud, It's easy, we are using wildcard certificates. For custom domains that you could make point to your content directly, what we do is that you put a key inside your DNS to say, this is the virtual machine that should be mapped to that domain. Then you do a CNAME to our cloud load balancer and then the VM host when they get a request for this one, they go and check the DNS to see what VM they should serve on the generator certificate using Let's Encrypt for that domain and they start serving it.Anatoly Yakovenko (16:59):Oh man, this would be really cool. But if we could have like an ENS where in my ENS registry I set my Let's Encrypt domain, and then I run a local DNS server on my home machine where I run my browser and point that as a resolver, you could kind of tie these knots together and get-Jonathan Schemoul (17:23):Yeah, it could work.Anatoly Yakovenko (17:24):That's really cool. What happens if these instances die, where do you guys get more hardware? How does that process work?Jonathan Schemoul (17:36):Well, an instance can just stop, then the load balancing system will find another instance to run your code. Then what happens when an instance get a request for a code that doesn't have for the micro VM network. I mean, it goes on the network, checks, okay, what is the database entry that is in front? It takes the database entries. Has there been any upgrades to it? Okay. I get the upgrades. I subscribe using web socket to the upgrades of this database entry basically because it's a document about database entry.Jonathan Schemoul (18:14):And then it looks, okay, so this is the root FS that I should load. Do I have it? I have it, could I use it? If not, I download it from the network. I applied that root FS, where is the code? Okay. What volume does it needs and it builds and retransits and gets you the answer. For a cold start with no root FS or whatever, it can take a few seconds. But in general you use the same root FS as others. So you can get the code start. If you don't have the code, it's less than a second. If you already have the code of the application is like 150 millisecond for a cold start.Anatoly Yakovenko (18:53):Got It. And is the coordination to decide where to start this particular instance? Does that occur over the underlying chain, like Solana or Ethereum or whatever?Jonathan Schemoul (19:08):Again, that's something that we're working on. At start it's on the cloud load balancer. So the cloud load balancer are semi centralized for that. The idea is that each micro VM running node that starts running one will register a message, which is a database entry with a reference to say, "I am running this one." And then the cloud load balancer looks at the uptimes of the available micro VMs and say, "Okay, this micro VM has it ready." I'm forwarding it to it.Jonathan Schemoul (19:40):And then if there is none, then it could just route it to like a random one that has a good uptime. And then this one, the next time kind of like be choosing automatically because it is already serving it. If there is a lot of requests, it will provision multiple ones.Anatoly Yakovenko (19:59):Interesting. Got it. And you anticipate that you'll basically be able to move if the underlying chain is cheap and fast enough you should be able to move the coordination and kind of like start this instance, pull this volume. This would be really cool with like Arweave backed storage volumes. Because you could almost then see the lifetime, the life cycle of the application as its business logic is evolving, right? That state is very useful to developers who are being able to go back to a checkpoint effectively at any given time too.Jonathan Schemoul (20:38):Well, right now we are using our own storage engine, which is APFS compatible. But in the future we will allow to choose other storage engine and we will also develop gateways with like Arweave, Filecoin and other.Anatoly Yakovenko (20:53):Super cool. I used to work at Mesosphere so I don't know if you've heard of them, like D2iQ, this was kind of Kubernetes competitor, trying to build this decentralized operating system using Mesos as the jobs kind of Q-engine. There's a lot of similar challenges there, and this is really cool that you guys are building this in a decentralized web application that's kind of hosted in the real cloud, the mythical cloud.Jonathan Schemoul (21:28):Yeah. Well, there's a saying, there is no cloud, it's just other people computers. Here it's really other people computer. So it's pretty good because then you don't trust those computers because you know it's other people computers.Anatoly Yakovenko (21:44):How do you guys ensure the integrity of the computation itself? How do I know that the virtual machine, the execution environment that's running isn't malicious.Jonathan Schemoul (21:54):It's a really good question. There is multiple questions there. How can I ensure that this computation isn't returning a bad result because it knows who is on the other end. The load balancing system ensures that you don't really see who is in the other end, so you don't know who is making the request. So you don't know if it's a quality control call or if it's a real call. It goes back to your question of the testing of the application. And there is another one there which is the question of the secrets, because you might need secrets. If you want to do push notification based on a smart contract event on Solana, let's say, because that's something that we are working on right now, thinking about it.Anatoly Yakovenko (22:48):That's super cool.Jonathan Schemoul (22:48):So you would need secrets. You will need to story a secret to being able to go back to this device and send these device and notification. So you either store secrets in the local storage of the instance, but then if the instance dies, you can get it back or you try to get shared secrets between multiple hosts. We are working on it. We don't have a total answer on that. What we are working on is using free shirt cryptography, so that multiple host defined by the developer come under these secrets. And then you go back to a question of trust, which is problematic.Anatoly Yakovenko (23:30):By the threshold cryptography, is this like an MPC to compute, or are you guys thinking like BLS or like Schnorr aggregation?Jonathan Schemoul (23:42):More like you encrypt something that can be decrypted by multiple private keys.Anatoly Yakovenko (23:47):Got it.Jonathan Schemoul (23:48):And then if they want to send a message, it needs to be signed by at least x of y.Anatoly Yakovenko (23:54):Right. Got it.Jonathan Schemoul (23:57):Because this micro VM I mentioned can also send messages on the network. These messages on the network will be database entries that in the end might end up also on-chain using all records or whatever. Because these micro VM can read from on chain data and the idea is that we are working so that they can also write on chain as well. So then you might need some kind of trust somewhere. So one developer could say, I trust this host this host this host, but they need at least to do that calculation three times, let's say. But it's a bit problematic and we are still working on it. It's not finished yet, so yeah.Anatoly Yakovenko (24:40):That's what I mean, that's a really hard problem.Jonathan Schemoul (24:41):Yeah.Anatoly Yakovenko (24:43):Really cool. Yeah, the secrets thing is really challenging. I guess, what's your vision for this? You guys are tackling on some really hard problems, you get all of them done in the next year.Jonathan Schemoul (25:01):I hope so.Anatoly Yakovenko (25:06):What happens then? What is the vision for Aleph?Jonathan Schemoul (25:08):Well, here we are only speaking about a few crypto issues. We aim at bigger than just the crypto ecosystem. What we really want to do is decentralize the web, so getting bigger, way, way bigger, that's the goal. We are working with a few bigger partners who are part of the Ubisoft entrepreneurial labs, for example. We want to have a lot of hosting partners in the game that start providing resources so that I want it to be as easy as spinning up AWS server or whatever, you would just spin up VMs under the .im network. I want it to be as easy as using Firebase, using Amazon Lambda, et cetera.Jonathan Schemoul (25:51):And we have another big project going on, which is the indexing on Solana, where we are indexing data for a few protocols, currently Raydium, we might have another already soon. Well, I can say the name. We are working a lot on Orca, on port finance right now, and a lot of others actually that I can't really talk yet. But the idea is to have all these data available, have all these data feed coming up so that you can have events based on them, also do off-chain computation and things like that.Jonathan Schemoul (26:29):I really want DeFi to be totally resilient because until it's totally decentralized, you can stop DeFi. When it's totally decentralized, you can't. And if there is only the smart contracts that are decentralized, you can still stop it.Anatoly Yakovenko (26:48):Yeah. That's definitely a fair point. I think the UX issues around building also just like push notifications and all these other things for projects are really hard to overcome if it's a decentralized project, because who's going to host those servers, right, to connect to mobile and everything else. Yeah. You guys have a lot of work set out and it's pretty exciting. What do you think is missing? If you guys had like another, somebody else was building this other piece that you think is missing in the Web 3, what would it be?Jonathan Schemoul (27:26):What is missing today in the Web 3 ease of use for all this. We are trying to tackle this, but we have so much on our end. So this is a big issue, ease of use for developers, ease of use for users. Well, Phantom is already doing a great work on that end on Solana. But yeah, this and also I think that there is some kind of breaks between the ... In DeFi, if you want to move money into the real world, it gets hard really fast because there has been some kind of complications that have been put in place by regulators, by banks, by whatever. If we could just get all these parts simpler, it could be great. Some kind of link between FinTech and crypto that would work everywhere in the world, including Europe, USA, et cetera. It would be great. There are a lot of people working on it, but that's something that is missing as well.Anatoly Yakovenko (28:28):Yeah. Identity and like having those easy ramps is still hard. What about DNS? Just straight up resolving, do you think that's tackleable from a Web 3 perspective.Jonathan Schemoul (28:45):The issue is the way DNS is done. DNS protocol is great, but it implies centralization points, a lot of centralization points, which are problematic. Then you will need another standard on DNS. But if you have another standard on DNS, then you have the issue that the network right now is done, is not done for it and the browser don't understand it, et cetera, and operating system don't understand it. We would need gateways for that. I think it's doable. It's definitely doable, but it's a lot of work. And you would need multiple root servers, even virtual root servers, like what you said, local DNS server that would resolve your request, it could work.Jonathan Schemoul (29:38):If Let's Encrypt could understand it in the same way, it would work. Or we could even have something different than the root certificate that we have today, because with blockchain, we already have private keys. We already have signature. So if you sign your content with your private key, then you can verify it on the other end. And you don't really need all these chains of certificates that are here today. So that could also be another solution, but it would need another way, because right now we have roots certificate, children's certificate, et cetera. And it all goes back to central authority. The whole DNS on certificate system today goes with authority. With blockchain we are trained to remove authorities.Anatoly Yakovenko (30:33):Yeah. Do you guys see this as becoming developer facing, or maybe someday eventually kind of like client facing and want these decentralized applications running for me, kind of my own instances. Or is this always going to be here I am, team Orca, go to this domain as a user.Jonathan Schemoul (30:56):It's a good question as well. It's always the issue between hosted components, locally run components and kind of pragmatic on that. At start I would really like to, everything runs inside my browser, everything works. That's great. In reality, you have mobile phones, you have tablets, you have computers, you have a lot range of devices that can be running all the time. So real peer to peer application can't really work that well, unless you go and say, "Okay. While you are waiting for me, please send it to my friend, that will forward the data for me, et cetera.Jonathan Schemoul (31:40):Blockchains are really helping there is that we have a centralized authority, which is the blockchain that you can trust and that can hold data for you and can even encrypt it for you or store it on aleph.im, whatever, and only you can decrypt it. I think that the mix between the two would be good, like self hosted data and remotely hosted data on the decentralized cloud, a good mix of the two could be good. And the efforts by the leap peer to peer team, with the javascript leap peer to peer. And there are a few of us like that helps, because once you have access to a peer-to-peer network directly from your browser, you can cut middlemen. You can cut central authorities, et cetera, if you're the blockchain that serves as a central authority.Anatoly Yakovenko (32:28):What kind of loads have you guys seen or been able to test this out, in terms of like users request per second, kind of WebSocket connections per second.Jonathan Schemoul (32:39):It depends because when it's per server, that's not that much of an issue because the micro VM supervisor just forwards the request to the underlying software. If you don't choose local persistent volume, the supervisor can run as many instances of your program as needed, then you can spawn multiple one even inside the same supervised cluster. And then the network, if it sees that this one has issues adding the request load you can load new ones.Jonathan Schemoul (33:18):I don't think that there is really a limit on the request per second for that. So it's not really the issue that we have. And then on the database part, same, if you access one API server and you give it 500,000 requests per second, it would go down, because it's a server. If you target multiple API server, you are good. So that's also where the decentralized load balancing helps because if you use a cloud load balancer obviously even this cloud can go down. But if you contact a peer to peer network to know what host can answer, then you can contact multiple host. And all our core channel nodes, we are currently 54 of them are also API servers that users can connect to to get the data, which will be certified by our core channel node.Anatoly Yakovenko (34:10):Cool. As a whole, how many, I guess, do you have an idea of how many users per second or humans per second have you guys served in some peak times?Jonathan Schemoul (34:21):We don't, because we don't store metrics currently, we should. We don't have it because we didn't want to have any kind of log or whatever on the users, but we should add it, that's actually a good point, we will.Anatoly Yakovenko (34:37):Yeah. I mean, I think you got to be really aware of privacy and how that impacts some applications. But really interesting to see how this works. Caching is another one of those things, basically having a distributed cache around the world for often queried data. And this is an issue that I think doesn't have a good solution in Web 3 right now. You do all this work, set up a purely thin client, that's like loads from code, only talks to the chain and then you got to go fetch assets. And if you're using centralized ... Yeah, they can basically inject whatever they want.Jonathan Schemoul (35:25):Yeah, that's the main issue. And the good part is that if you also randomize where the request of the users go, if there is one bad actor, it will only inject bad data once in a while you don't even know where. Once there is a quality control it will detect it, so that can also be a solution. It's not a silver bullet either, but it can definitely help. So like for Solana what we are doing right now, for Raydium for example, is that we have an indexer that talks to multiple RPC of Solana then get the transaction history, store it inside the level DB, inside the micro VM, and then index the data.Jonathan Schemoul (36:09):Then we can get data on the pool's latest trades and stuff like that. The idea is that if there is too much request on one index, it will start another index or another index or another index, or et cetera, so that when you do a request, it reroutes you randomly to multiple hosts that have the same index.Anatoly Yakovenko (36:28):How fast is that?Jonathan Schemoul (36:31):Not fast enough currently. Well, it's fast enough for Raydium.Anatoly Yakovenko (36:35):Okay.Jonathan Schemoul (36:36):It works really well.Anatoly Yakovenko (36:40):Raydium gets a ton of hits. I mean, some of their IDOs have seen half a million requests per second-Jonathan Schemoul (36:48):Yeah. So for the Raydium data, it handles it well, like all the trades, whatever, it handles it pretty well. We don't get behind blocks in the indexing, so it works well. For Serum it's a bit more problematic because you need to watch, event cue all the time. I really hope they will have some kind of flux in the future. I think that they are working on it. So that would really help us either to get history even when we aren't watching their event cue.Anatoly Yakovenko (37:23):Yeah. So not half a million per second, half a million total, which is quite different, but yeah, they see some really good traffic.Jonathan Schemoul (37:30):Yeah.Anatoly Yakovenko (37:32):Cool. I mean, that's really cool. I think really hard part I think in designing these systems, one, is the problem is difficult, but then once you build the first version of it and you start hitting real traffic, there's a lot of parts that fit together that break under load. So what is your debugging like? How do you guys actually monitor like debug, like PagerDuty, what do you guys use as a team?Jonathan Schemoul (38:01):Right now our team is still small. We are growing a lot. Right now we are like 10 developers. A few months ago we were only three. A year ago I was alone. So we are growing really fast and we are putting all these things into place. Right now everyone monitors and checks what happens and it helps. There is Hugo who is on the micro VM side, Ali was mostly on the indexer side, myself we can get everything. But we are putting really real stuff in place right now to have it, because we are a growing startup so it takes time to get everything in place.Anatoly Yakovenko (38:43):Yeah, for sure. Do you envision a PagerDuty team for this?Jonathan Schemoul (38:48):Yes. I think that we will need one. Once we have more application that are using it, we will need one. So yes, if you have advices on that day, I'm really happy to get them.Anatoly Yakovenko (39:00):I mean, it's just part of life. It's not complicated. It's just work. This is I think that like response team I think is a difficult thing to set up in a decentralized community. If you guys are building a decentralized network with providers that are supplying hardware and all this other stuff, those are the folks that we found to be really responsive and have a lot of stake in growing this. How do the economics work for all the people actually supplying the hardware and bandwidth, et cetera?Jonathan Schemoul (39:36):Again, the research and economics aren't live yet. We are working on them. The core channel nodes economics is already there for like a year, now it works well. For the core channel node you need to have 200,000 Aleph to start a node and 500,000 Aleph, staked on a node, so that it can start to run. And then all the node operator get a share of a global envelope daily for all the nodes. All the stakers get a part of the envelope for stakers. The more nodes active, the bigger the envelope for staker is. But then for each node, they will earn a bit less if there are more nodes because it's a global envelope. So it helps stakers grow the number of nodes that are active, so that's for the core channel nodes.Jonathan Schemoul (40:25):For the resource nodes, to get storage or computing on network, there is two ways to get it. One that is already live, which is hold X amount of Aleph and get that amount of storage, hold X amount of Aleph and have the ability to start one VM with X megabyte of RAM, X virtual CPU, et cetera. And then the multiplier, and all that gives you the total count of micro VM I mentioned that can be running on your network based on your balance. The good part with that is that partner project could use a lending protocol to borrow Aleph where depositing their own token to get service. They would get the service for free just paying interest in their token, inside the borrowing protocol.Anatoly Yakovenko (41:14):Got it.Jonathan Schemoul (41:15):So that's a way for protocols to get it, but it's quite expensive because they don't directly pay for it. So for this way of using it, Aleph.im network is paying for them from the incentive pool, which right now it's one fifth of the supply, and we are changing it in the next few months, we'll change a bit of economics. It will be nearly half of the supply that would be dedicated to pay for that. Because since you lock a part of the supply, then you can release a bit inside circulating because of this new use. So that's for the hold X Aleph tokens.Jonathan Schemoul (41:51):And then there is another way that isn't developed yet that we will likely use Solana for, because it's fast enough for micro-payments in that area. It's like pay per action, pay X Aleph per gigabyte per month. You as a provider, you can say, "I am okay to be paid at least that much." And then users will say, "I want my data to be replicated at least four time. And I'm okay to pay at most that much for this." Then you get divided by those who provide service and the payment is done as micro payments. And same for the micro VM you pay per CPU per hour, et cetera.Anatoly Yakovenko (42:32):Got it. That's really cool. Well, this has been awesome to have you on the show. I mean, we got into I think the really deep, deep tells of how Aleph works, so I had a blast because it really reminds me of the spending, working on the stuff for centralized systems. It's really cool to see this kind of built ground up for decentralized ones as well. So appreciate the work you're doing. Thank you, Jonathan.Jonathan Schemoul (43:00):Thank you very much for having that call. It was really great talking with you.Anatoly Yakovenko (43:04):Awesome. And good luck to you guys. I mean, startups are blood, sweat and tears, so just keep working on the vision. You'll get there.Jonathan Schemoul (43:11):Thank you very much.Anatoly Yakovenko (43:13):Cool. Take care.

Welcome to Blockstream Talk #3Our conversation today is with one of the worlds leading experts on the Lightning Network, Dr. Christian Decker.Christian is also known as "Dr. Bitcoin" because his dissertation was the first distributed computing PhD to focus explicitly on Bitcoin.His work on duplex micropayment channels actually predates the Lightning Network paper, but in a bizarre twist of faith it ended up being caught in academic review and publication ended up following after the publication of the Lightning Network paper. In developer circles, Christian is seen as the inventor, or at least one of the inventors, of Lightning scaling solutions.  So really there's no better person to talk about the current state and the future of the Lightning Network. While investors have been looking at Bitcoin as a high-growth inflation hedge, but what's going on in El Salvador and how bitcoin is actually being used in emerging economies is really bringing the digital cash narrative back to the forefront.So in this conversation, I was keen to get Christian's views, not only the state of the Lightning Network now, but what could go wrong?Is the Lightning Network ready for prime time and full integration - not into a platform or wallet - but into an entire economy?As well as the role the Lightning Network in driving broader Bitcoin adoption in the years to come. 0:00 Intro2:27 - What is the Lightning Network, and what problems is it trying to solve?5:29 - Limitations of the Lightning Network7:22 - Existing protocols tackling the scaling problem9:54 - The blocksize war11:34 - How Lightning interacts with Liquid13:39 - Are the different Lightning implementations competing with each other?15:52 - How far are we in terms of user adoption?19:29 - The role of Lightning in Bitcoin´s ease of use23:34 - Where is the biggest potential growth for Lightning in the next five years?25:23 - The most important technical issues when scaling Lightning28:12 - Why have exchanges been slow at integrating Lightning?31:10 - What the implementation of Taproot and Schnorr signatures means for the Lightning Network34:39 - Blockstream Greenlight38:44 - Questions from the Blockstream Talk community on Twitter50:23 - Exciting prospects for Bitcoin´s future

Full interview with Joinmarket's Adam Gibson. Adam sits and chats about a wide range of Bitcoin-related topics such as cryptography, privacy tools like Payjoin, Coinjoin, and Coinswap, his enthusiasm for Lightning, and the potential benefits from Taproot & Schnorr signatures, and the tradeoffs of adding features to Bitcoin, and Lightnign use on a wide scale. ----------------------------------------------- Follow Adam on social media: Mastodon: https://x0f.org/web/accounts/41381 Adam's blog: https://joinmarket.me Adam's github: https://github.com/AdamISZ ----------------------------------------------- Welcome to the 21st episode of Bitrefill's To The Moon Podcast. To The Moon is Bitrefill's new weekly podcast to discuss Bitcoin, altcoins, adoption, news & current events, and all things crypto. Join host Lawrence Ray, along with Jerry Okai, and Ricardo Martinez, for a light-hearted and humorous weekly discussion about the latest developments in the crypto economy. ----------------------------------------------- Bitrefill is the largest crypto store since 2014!

Jan Schnorr co-founded C2Sense as a spin-off from MIT and served both as CTO and CEO before leaving his company in 2019. He now spends his time as “management consultant for startups”, helping scientists build their companies and initial teams – both in the US and Germany, amongst others as a Startup Scouting Consultant at the Max Planck Foundation. We learn about the first steps of building C2Sense, the support of the MIT ecosystem and differences and similarities between the Boston ecosystem and Germany, Jan's home turf.Jan shares his learnings and reflections on his time in various roles building up his company, jumping from researcher to CTO to CEO. He talks about the importance of knowing yourself to be at home in every role and designing it to fit your own personality and skillset. We talk in-depth about his understanding of leadership, the valuable lessons he learned as a cub scout leader in his home state around motivating people to join a cause and the role of empathy and unfiltered feedback. Jan has a deep motivation for building teams, and he shares his learnings on choosing the right people, the importance of clearly defining roles in advance, and talks about how investing enough time and energy into good hiring pays off for a startup.

ข่าวด่วนจาก ก.ล.ต. ที่ประชุมคณะกรรมการ ก.ล.ต. ครั้งที่ 12/2564 เมื่อวันที่ 9 มิถุนายน 2564 มีมติเห็นชอบให้ออกประกาศคณะกรรมการกำกับหลักทรัพย์และตลาดหลักทรัพย์ ที่ กธ. 18/2564 เรื่อง หลักเกณฑ์ เงื่อนไข และวิธีการประกอบธุรกิจสินทรัพย์ดิจิทัล (ฉบับที่ 11) ซึ่งได้ลงราชกิจจานุเบกษาและมีผลใช้บังคับตั้งแต่วันที่ 11 มิถุนายน 2564 เป็นต้นไป โดยไม่มีผลย้อนหลัง ประกาศดังกล่าวห้ามศูนย์ซื้อขายให้บริการ “Utility Token พร้อมใช้” หรือคริปโทเคอร์เรนซี ที่มีลักษณะใดลักษณะหนึ่งดังต่อไปนี้ มาซื้อขายในศูนย์ซื้อขาย (1) ไม่มีวัตถุประสงค์หรือสาระชัดเจนหรือไม่มีสิ่งใดรองรับโดยมีราคาขึ้นอยู่กับกระแสในโลกโซเชียล (Meme Token) (2) เกิดจากกระแสความชื่นชอบส่วนบุคคล (Fan Token) (3) โทเคนดิจิทัลที่เกิดจากการนำเทคโนโลยีมาใช้แสดงความเป็นเจ้าของหรือให้สิทธิในสิ่งใดสิ่งหนึ่งหรือที่เฉพาะเจาะจง โดยไม่สามารถใช้โทเคนดิจิทัลประเภทและชนิดเดียวกัน และจำนวนเท่ากันแทนกันได้ (Non-Fungible Token : NFT) (4) โทเคนดิจิทัลที่ออกโดยศูนย์ซื้อขายเองหรือบุคคลที่เกี่ยวข้องกับศูนย์ซื้อขายเพื่อวัตถุประสงค์ ในการใช้ประโยชน์สำหรับธุรกรรมที่เกิดขึ้นบนบล็อกเชน (blockchain) เอฟบีไอ (FBI) สามารถปลดล็อกกระเป๋าเงินบิตคอยน์ของแฮกเกอร์ได้จริงหรือจากกรณี การกู้คืนแรนซัมแวร์จำนวน 63.7 เหรียญบิตคอยน์มูลค่า 2.3 ล้านดอลลาร์หรือราว 71 ล้านบาท จากจำนวน 5 ล้านดอลลาร์ ซึ่งจ่ายโดยโคโลเนียล ไปป์ไลน์ (Colonial Pipeline) และมารู้จัก Taproot กับ Schnorr Signature กัน ท่านสามารถร่วม Join Membership ได้แล้ววันนี้ ขอบคุณทุกท่านที่สนับสนุนช่อง Bitcast: https://bit.ly/32t0sxO ระดับ Membership 1) ระดับกุ้งฝอย จะมีสิทธิ์ได้ใช้ emoji และมี Badge ติดอยู่ที่ข้างชื่อ 2) ระดับเต่า จะมีสิทธิ์ได้ใช้ emoji และมี Badge ติดอยู่ที่ข้างชื่อและผมจะประกาศรายชื่อขอบคุณในหลาย ๆ ช่องทาง 3) ระดับวาฬ จะมีสิทธิ์ได้ใช้ emoji และมี Badge ติดอยู่ที่ข้างชื่อ ประกาศรายชื่อขอบคุณในหลาย ๆ ช่องทาง และมีสิทธิ์ร้องขอให้ทำ VDO ที่อยากรู้ เยี่ยมชมร้านค้า https://thaibitcast.com/shop/ ติดต่อโทร 097 991 6988 email: suppakritb@gmail.com http://www.thaibitcast.com Youtube: https://www.youtube.com/c/thaibitcast Facebook: https://www.facebook.com/thaibitcast Twitter: https://twitter.com/thaibitcast Apple Podcast: https://apple.co/368Qpgj Spotify: https://spoti.fi/38oWLcS Blockdit: http://bit.ly/3nObiX4 Line: @bitcast  

Location: Remotely Date: Monday 21st December Company: Block Digest Role: Host 2020 has been a record-breaking year for Bitcoin where we have seen the price reach a new all-time high of over $24,000. Companies like MicroStrategy and Square have paved the way for institutional investors, and mainstream media covers Bitcoin more than ever.  While interest in Bitcoin is continuing to grow, behind the scenes, Bitcoin developers are quietly continuing to push the technology forwards. With improvements like Schnorr signatures and CoinSwap on the horizon and advancements with discrete log contracts and Lightning Lab's Loop, the technical side of Bitcoin is also thriving.  In this interview, I am joined by Shinobi host of Block Digest. We review the technical side of Bitcoin in 2020, including MuSig, Schnorr & Taproot, discrete log contract, Lightning Labs Loop and CoinSwap.  

"This risk is probably best countered by offering enough time to upgrade. Unfortunately, not everyone agrees on how much time is enough; some think forced signaling could start within a year, others believe it should take several years." - Aaron Van Wirdum Taproot is here! Now just how the hell do we decide to do the upgrade? Aaron Van Wirdum brings us another great piece at Bitcoin Magazine on the varied discussions on how to implement a Bitcoin soft fork in the post-SegWit days. Do we have PTSD, or are we ready for another leap in the Bitcoin protocol? Check out the original at Bitcoin Magazine: https://bitcoinmagazine.com/articles/taproot-coming-what-it-and-how-it-will-benefit-bitcoin For further reading/listening on Segwit, Taproot, Schnorr, & more, check out these other awesome articles below: Taproot is Coming • https://anchor.fm/thecryptoconomy/episodes/CryptoQuikRead_318---Taproot-is-Coming-Aaron-van-Wirdum-e8um0c The Long Road to Segwit • https://anchor.fm/thecryptoconomy/episodes/CryptoQuikRead_054---The-Long-Road-To-Segwit-e2ndsv Schnorr Signatures & The Inevitability of Privacy • https://anchor.fm/thecryptoconomy/episodes/CryptoQuikRead_226---Schnorr-Signatures--The-Inevitability-of-Privacy-in-Bitcoin-Lucas-Nuzzi-e3jfhi Paying Yourself for Privacy on Lightning • https://anchor.fm/thecryptoconomy/episodes/CryptoQuikRead_352---Paying-Yourself-for-Privacy-on-Lightning---Aaron-Van-Wirdum-eaq2go Simplifying Lightning with the "No Input" Class • https://anchor.fm/thecryptoconomy/episodes/CryptoQuikRead_297---Simplifying-Lightning--The-Noinput-Class-Aaron-Van-Wirdum-e5fhoa ----------------------------- Start your Bitcoin savings plan at SwanBitcoin.com/guy! Don't hate yourself for having delayed weeks and missed a prime, sat stacking opportunity before the next bull market. Today is it! --- Send in a voice message: https://podcasters.spotify.com/pod/show/bitcoinaudible/message

It has been said that over 17 million deal with depression, and have had 1 major depressive disorder in the past year. In this interview with Tom Schnorr RPh, CCN we talk about Ketamine and natural solutions that he uses in his pharmacy to help treat patients who don't respond to traditional depression treatments. For more information on Tom and his pharmacy you can find him at austincompoundingpharmacy.com You can also see him through Telemedicine at letsasktom.com Please follow me for more injury prevention, health, and functional medicine posts on Instagram @FredricksonHealthSolutions on youtube and instagram. Disclaimer: Informational purposes only. Also consult with a physician before starting a new rehab exercise, training routine, diet, or dietary supplement. No medical advice given. Always consult a qualified healthcare provider before starting a new medication. We are not liable for ANY off label use.

On episode nine of 4AM In Quarantine, Steven J. Rivera and Mike Schnorr discuss the future of our country's food supply chain and consumer habits. As a sales veteran of 24 years, Mike also gives his perspective on the importance of relationships and mindset as a born and bred salesman. Mike is the CEO of Global Imports, an import/export company specializing in food commodities which packs, processes and ships food products from 24 countries worldwide to the manufacturing, food service and retail segments of the food industry.

Location: Zoom Date: Friday, 10th April Project: Blockstream Role: Director of Research Bitcoin is very conservative. Unlike the typical tech industry ethos of move fast and break things, it is paramount that Bitcoin upgrades and changes to the protocol are absolutely necessary, slow, well planned and well tested. Two protocol changes that have been discussed for a while now are Schnorr signatures and Taproot. These proposals have lots of positive implications, including an improvement to privacy and scalability, but what will it mean for an average Bitcoin user? What is next on the roadmap? In this interview, I talk to Andrew Poelstra, the Director of Research at Blockstream. We discuss the upcoming upgrades to the Bitcoin protocol, including Schnorr signatures, Taproot and Miniscript and what that means to Bitcoin users.

In Episode 7, we chat with Nadav Kohen of Suredbits and discuss payment points as an alternative to HTLCs on the Lightning Network. In this conversation we cover: Payment points (1:55) - Blog post part 1 - HTLCs (2:00) Timelocks (4:16) HTLC drawbacks (5:38) - Payment decorrelation - Wormhole attack presented in Anonymous Multi-Hop Locks for Blockchain Scalability and Interoperability (6:35) Point time lock contracts (PTLCs) (9:50) - Adaptor signatures on Schnorr Proof of payment (13:25) Invoiceless transactions (15:05) Hashes, pre-images, and HTLC mechanics (16:35) Onion analogy (18:55) PTLC mechanics (19:30) Why don't we use PTLCs today? (22:15) Lightning in Scriptless Scripts posting by Andrew Poelstra March 2017 Improving proof of payment (26:10) Stuckless payments (30:46) Spam on Lightning (35:46) Selling Signatures and Schnorr signatures off the main chain (36:55) Contingent payments (39:20) Escrow contracts (41:28) Atomic multiparty setup and payment renegotiation (46:02) ETA of payment points (48:02) Thanks as always to Matthew Zipkin for the sound engineering.

Closing out an extraordinary year in 2019 has us looking forward at 2020 & Beyond. What will we bring to Bitcoin, and what could Bitcoin bring to us? Today we read an amazing thread by John Newbery on the exceptional list of tools and technologies making their debut on the Bitcoin and Lightning protocol stack that will change everything about how we interact with and use this incredible technology. So much exciting stuff to go over, don't miss “A Bitcoin Roadmap” twitter thread by John Newbery. Link to John's thread and thorough list of links included to explore the tons of improvements on the horizon, or already available to be built with. I highly encourage a dive down this rabbit hole! https://twitter.com/jfnewbery/status/1208559196465184768 • Jack Mallers & Announcing Olympus (fiat-to lightning in seconds) https://twitter.com/JackMallers [audio] https://anchor.fm/thecryptoconomy/episodes/CryptoQuikRead_299---Announcing-Olympus--From-Fiat-to-Lightning-in-Seconds-Jack-Mallers-e5j7ko • Schnorr & Privacy by Lucas Nuzzi https://anchor.fm/thecryptoconomy/episodes/CryptoQuikRead_226---Schnorr-Signatures--The-Inevitability-of-Privacy-in-Bitcoin-Lucas-Nuzzi-e3jfhi • Taproot is Coming by Aaron Van Wirdum https://anchor.fm/thecryptoconomy/episodes/CryptoQuikRead_318---Taproot-is-Coming-Aaron-van-Wirdum-e8um0c • Lightning & the "Noinput Class" by Aaron Van Wirdum https://anchor.fm/thecryptoconomy/episodes/CryptoQuikRead_297---Simplifying-Lightning--The-Noinput-Class-Aaron-Van-Wirdum-e5fhoa If you want to support the show and join the Cryptoconomy Telegram crew, become a patron below! https://www.patreon.com/thecryptoconomy --- Send in a voice message: https://podcasters.spotify.com/pod/show/bitcoinaudible/message

"The need for privacy and the long-term sustainability of Bitcoin without block rewards are perhaps two of the most most alarming issues surrounding Bitcoin today." - Lucas Nuzzi Could Schnorr signatures be the puzzle piece that eliminates a major limitation on the costs and ease of privacy at Bitcoin's base layer, while at the same time, incentivizing a robust fee market, and enabling a wide range of more dynamic smart contracts? The next soft fork in Bitcoin could be the most exciting and significant change that Bitcoin ever sees. You don't want to miss this great piece by Lucas Nuzzi covering the ins and outs of Schnorr signatures and how it will change the game for Bitcoin privacy.   Drop as many claps as you can on his article below and remember to check out the tons of other great articles of his and others posted on the Digital Assets Research publication: https://medium.com/digitalassetresearch/schnorr-signatures-the-inevitability-of-privacy-in-bitcoin-b2f45a1f7287 --- Send in a voice message: https://podcasters.spotify.com/pod/show/bitcoinaudible/message

Welcome to episode 60 of The Bitcoin Game, I'm Rob Mitchell. I'm happy to bring to you part two of my interview with Cypherpunk and CEO of Blockstream, Dr. Adam Back. In this episode, we take a deep dive into Liquid, Blockstream's new federated sidechain. There's a lot more to Liquid than I realized, and it's fascinating to hear tons of details about the protocol. I lead us astray with some of my questions, but Dr. Back never fails to drop tons of crypto-knowledge. And if you missed the first part of my interview, give episode 59 a listen to hear a great Cypherpunk history lesson. EPISODE LINKS First half of our interview (The Bitcoin Game #59) https://letstalkbitcoin.com/blog/post/the-bitcoin-game-59-dr-adam-back Adam Back (Adam3us) on Twitter https://twitter.com/adam3us Dr. Back's Info Page http://www.cypherspace.org/adam Blockstream https://blockstream.com Lightning Network White Paper by Joseph Poon & Thaddeus Dryja https://lightning.network/lightning-network-paper.pdf Duplex Micropayment Channels by Christian Decker & Roger Wattenhofer https://www.tik.ee.ethz.ch/file/716b955c130e6c703fac336ea17b1670/duplex-micropayment-channels.pdf ETHZ (where Christian Decker earned his Bitcoin PhD) https://www.ethz.ch/de.html Rusty Russell https://en.wikipedia.org/wiki/Rusty_Russell C-Lightning https://github.com/ElementsProject/lightning Liquid https://blockstream.com/liquid Liquid Assets https://blockstream.com/2018/07/02/liquid-issued-assets Confidential Transactions https://bitcoinmagazine.com/articles/confidential-transactions-how-hiding-transaction-amounts-increases-bitcoin-privacy-1464892525 ERC-20 https://en.wikipedia.org/wiki/ERC-20 Counterparty https://counterparty.io/docs/faq-xcp UTXO https://en.wikipedia.org/wiki/Unspent_transaction_output Bulletproofs https://crypto.stanford.edu/bulletproofs https://eprint.iacr.org/2017/1066.pdf Tether https://en.wikipedia.org/wiki/Tether_(cryptocurrency) Proof of Burn https://www.coinbureau.com/education/proof-of-burn-explained Public Key vs. Public Address https://www.reddit.com/r/Bitcoin/comments/3filud/whats_the_difference_between_public_key_and Lamport Signatures https://en.wikipedia.org/wiki/Lamport_signature The Byzantine Generals Problem https://people.eecs.berkeley.edu/~luca/cs174/byzantine.pdf Schnorr Signatures https://en.wikipedia.org/wiki/Schnorr_signature ECDSA https://en.wikipedia.org/wiki/Elliptic_Curve_Digital_Signature_Algorithm Denial-of-Service Attack https://en.wikipedia.org/wiki/Denial-of-service_attack Tor https://www.torproject.org Liquid Block Explorer https://blockstream.com/2018/08/02/accelerating-liquid-adoption-liquid-block-explorer NBitcoin by Nicolas Dorier https://www.codeproject.com/Articles/768412/NBitcoin-The-most-complete-Bitcoin-port-Part-Crypt Green Address Wallet https://greenaddress.it KYC Compliance https://en.wikipedia.org/wiki/Know_your_customer Paul Sztorc talks about Sidechains, Drivechain, Liquid https://letstalkbitcoin.com/blog/post/lets-talk-bitcoin-377-sidechains-drivechains-and-the-apple-store RootStock https://en.wikipedia.org/wiki/RootStock Spark Lightning Wallet by Nadav Ivgi https://bitcoinmagazine.com/articles/spark-new-gui-lightning-wallet-bitcoin-now-available-download Lightning Splice-In, Splice Out (and more) https://medium.com/@pierre_rochard/day-2-of-the-chaincode-labs-lightning-residency-669aecab5f16 SPV Wallet https://en.bitcoinwiki.org/wiki/Simplified_Payment_Verification Neutrino Lite Bitcoin Client https://github.com/lightninglabs/neutrino/blob/master/README.md Lightning Watchtower https://www.coindesk.com/laolu-building-watchtower-fight-bitcoin-lightning-fraud/ ABCore by Lawrence Nahum (BTC full node on Android) https://play.google.com/store/apps/details?id=com.greenaddress.abcore Hardware Wallet https://en.bitcoin.it/wiki/Hardware_wallet STAY IN TOUCH Thanks so much for taking the time to listen to The Bitcoin Game! https://Twitter.com/TheBTCGame http://TheBitcoinGame.com Rob@TheBitcoinGame.com SPONSORS BTC Inc is excited to announce its upcoming conference, Distributed Health, November 5 & 6 in Nashville, TN. This is the first conference to bridge the gap between blockchain technology and the healthcare industry. Now in its third year, this two-day event is an opportunity for all members of the ecosystem, including payers, providers, law makers, retailers, investors and innovators, to reshape the future of healthcare. For more information, visit: health.distributed.com and use the promo code: BTCGAME20 to secure a 20% discount! While much of a Bitcoiner's time is spent in the world of digital assets, sometimes it's nice to own a physical representation of the virtual things you care about. For just the price of a cup of coffee or two (at Starbucks), you can own the world famous Bitcoin Keychain. As Seen On The Guardian • TechCrunch • Engadget • Ars Technica • Popular Mechanics Inforwars • Maxim • Inc. • Vice • RT • Bitcoin Magazine • VentureBeat PRI • CoinDesk • Washington Post • Forbes • Fast Company Bitcoin Keychains - BKeychain.com CREDITS All music in this episode of The Bitcoin Game was created by Rob Mitchell. The Bitcoin Game box art was created from an illustration by Rock Barcellos. Bitcoin (Segwit) tipping address: 3AYvXZseExRn3Dum8z9tFUk9jtQK6KMU4g Note: We've recently migrated our RSS feed (and primary content host) from Soundcloud to Libsyn. So if you notice the Soundcloud numbers have dropped off recently, that's the reason.

“We're as excited about Lightning, Schnorr signatures, Taproot/Graftroot and scriptless scripts as any other Bitcoin engineers, but the project's focus is on technology that can be deployed by companies today.” - @bitcoinoptech Those mentioned in the commentary: @jfnewbery @starkness @Melt_Dem @BtcpayServer Check out the official announcement from @bitcoinoptech and check out their newsletter below: https://bitcoinops.org/en/announcing-bitcoin-optech --- Send in a voice message: https://podcasters.spotify.com/pod/show/bitcoinaudible/message

Thanks to the incredible work by Pieter Wuille (@pwuille) and others, #Schnorr signature scheme has an official proposal. Despite still much work and testing to be done, schnorr is poised to grant #Bitcoin a plethora of amazing improvements. Listen to @AlyssaHertig's article from @coindesk to learn more! Check out the article and other news and developments throughout the Cryptoconomy at: https://www.coindesk.com/schnorr-is-looking-poised-to-become-bitcoins-biggest-change-since-segwit/ --- Send in a voice message: https://podcasters.spotify.com/pod/show/bitcoinaudible/message

Schnorr Signatures could result in a significant change in the Bitcoin network efficiency and the size and types of transactions, but what will it mean for privacy?  Listen to @nopara73's article to learn more.   Link to nopara73's article and other works:https://medium.com/@nopara73/privacy-and-schnorr-signatures-e2175d27f022 --- Send in a voice message: https://podcasters.spotify.com/pod/show/bitcoinaudible/message

Schnorr signatures could be a boon to the efficiency of the Bitcoin system and a hinderance to its spammers.  Listen to the article from Sam Wouters to learn more.   Dont forget to check out Sam Wouter's Medium page to explore the links, graphics, and his many other works:https://medium.com/@SDWouters/why-schnorr-signatures-will-help-solve-2-of-bitcoins-biggest-problems-today-9b7718e7861c --- Send in a voice message: https://podcasters.spotify.com/pod/show/bitcoinaudible/message

sources of stories from today: https://www.one-tab.com/page/os5_GonjRMutCEMrVlbI5Q ↓↓↓timestamps↓↓↓ 2:01 - Dino of the Day 6:48 - Bullish: JPMorgan Publishes The "Bitcoin Bible" 10:46 - Scaling: Funny Name or Not, Schnorr Is a Big Deal for Bitcoin 14:38 - Viewer Question: Is Bitcoin done dropping? 15:40 - Is the SEC claim that "blockchain is valuable" and they want to do a "no harm policy" nothing more than appeasement, while the control structure is planning a global freeze? 16:25 - Russian National Arrested For Cyber Crime In Bangkok, Allegedly Had $820 Mln in BTC 19:47 - Scientists at Russian nuclear research facility arrested for mining cryptocurrency 22:46 - Japanese Crypto Investors To Pay Tax Of Up To 55 Percent On Profits 25:02 - IRS Forms New Team To Track Down Crypto Tax Evaders 30:01 - BitGrail Exchange Asks Devs of ‘Stolen' Coin To Alter Ledger To ‘Cover Losses' 31:59 - TGoC Merch? 32:07 - Cybersecurity: Mining Malware Tsunami Continues: ‘5000' High-Profile UK Websites Hit By Tainted Plugin If you want more, connect with us online at the following places: Website: https://krbecrypto.com/ Shop: https://shopkrbecrypto.com/ Services: https://krbecrypto.com/services/ About Us: https://krbecrypto.com/about/ Subscribe to our YouTube: https://www.youtube.com/krbecrypto KRBE Twitter: https://twitter.com/krbecrypto KRBE Facebook: https://www.facebook.com/krbecrypto/ KRBE Instagram: https://www.instagram.com/krbecrypto/ King Twitter: https://twitter.com/KingBlessDotCom Bitcoin Zay Twitter: https://twitter.com/bitcoinzay Business Inquiries: krbe@krbecrypto.com   Donations Welcome: Bitcoin: 1NTnWaGowHEh9VRWMXWTiqWpQT9vjP5Ukd Litecoin: LSc2bEAMEbGSHKx54GUt4xi1eZQqtscv8i   Thanks for listening and remember to subscribe for daily content where we give away free Bitcoin!