item: #1 of 3327 id: aave-aave-community author: aave title: aave-aave-community date: None words: 1366 flesch: 48 summary: The Finance Stewards have the authority to: Migrate assets from v2 and deposit into v3 Use the Aave Swapper to exchange treasury assets Withdraw and deposit into V3 Transfer and stream tokens to pre-approved addresses within set budgets such as ACI Frontier Program and ACI Merit Program Proposed Finance Stewards at the time of writing are: Karpatkey Tokenlogic Related Proposals beginner Aave Governance proposal lifecycle. 7 min read Voting beginner Voting in Aave Governance. keywords: aave; gho; governance; protocol; stewards cache: aave-aave-community.html plain text: aave-aave-community.txt item: #2 of 3327 id: aave-accessing-aave author: aave title: aave-accessing-aave date: None words: 522 flesch: 52 summary: Accessing Aave | Aave ProductsResourcesDevelopersApp Interact with Aave easily. Aave Protocol will never ask for your wallet seed phrase. keywords: aave; protocol cache: aave-accessing-aave.html plain text: aave-accessing-aave.txt item: #3 of 3327 id: aave-borrow-tokens author: aave title: aave-borrow-tokens date: None words: 650 flesch: 47 summary: The interest rates for borrowed tokens are dynamically determined by the protocol based on factors like the borrow utilization rate and governance parameters, which can change through community decisions. 3 min read Health Factor & Liquidations advanced Mechanics of Aave Protocol liquidations. keywords: aave; borrow cache: aave-borrow-tokens.html plain text: aave-borrow-tokens.txt item: #4 of 3327 id: aave-e-mode author: aave title: aave-e-mode date: None words: 546 flesch: 46 summary: Step 2: Navigate to E-mode Options After connecting, go to the ‘Dashboard’ and locate the E-mode option near your account summary row. Therefore, it’s essential to review the available assets, collateral, and borrowing parameters within the category before enabling E-mode. keywords: aave; mode cache: aave-e-mode.html plain text: aave-e-mode.txt item: #5 of 3327 id: aave-introduction-to-aave author: aave title: aave-introduction-to-aave date: None words: 1019 flesch: 50 summary: Introduction To Aave | Aave ProductsResourcesDevelopersApp Interact with Aave easily. Open AppApp Interact with Aave easily. keywords: aave; collateral; protocol cache: aave-introduction-to-aave.html plain text: aave-introduction-to-aave.txt item: #6 of 3327 id: aave-isolation-mode author: aave title: aave-isolation-mode date: None words: 541 flesch: 54 summary: When an asset is designated as an Isolated Collateral Asset, it can only be used to borrow specific stablecoins that have been approved by Aave Governance. This enforces that the borrowing risks remain contained within the guidelines set by Aave Governance. keywords: aave cache: aave-isolation-mode.html plain text: aave-isolation-mode.txt item: #7 of 3327 id: aave-liquidations author: aave title: aave-liquidations date: None words: 666 flesch: 47 summary: Generally, lower health factors may be acceptable for correlated assets, such as stablecoins or assets closely tied to ETH. The liquidation threshold, set by Aave Governance for each collateral asset, determines the maximum percentage of value that can be borrowed against it. keywords: factor; health cache: aave-liquidations.html plain text: aave-liquidations.txt item: #8 of 3327 id: aave-proposals author: aave title: aave-proposals date: None words: 1069 flesch: 55 summary: Proposals can introduce new features, modify parameters, or make other changes to the Aave Protocol. The Aave Governance Forum and Discord are the primary platforms for discussing proposals. keywords: aave; framework; governance; proposal cache: aave-proposals.html plain text: aave-proposals.txt item: #9 of 3327 id: aave-repay-tokens author: aave title: aave-repay-tokens date: None words: 484 flesch: 53 summary: Repayments can be made fully or partially through protocol smart contracts or through a frontend such as Aave Labs interface by performing the following steps: Step 1: Connect Wallet To begin, press ‘Connect Wallet’ and select the Ethereum wallet provider corresponding to the wallet holding the tokens intended for repayment. 3 min read Health Factor & Liquidations advanced Mechanics of Aave Protocol liquidations. keywords: aave; guides cache: aave-repay-tokens.html plain text: aave-repay-tokens.txt item: #10 of 3327 id: aave-supply-tokens author: aave title: aave-supply-tokens date: None words: 627 flesch: 51 summary: Interest rates for supplied tokens are determined by the borrow utilization rate, which measures the proportion of assets currently borrowed against the total supplied in the pool, and by governance parameters that can be adjusted through community decisions. Supplying GuidesSupply Tokens beginner Introduction Supplying tokens to the Aave Protocol allows you to earn interest on your digital assets and utilize supplied tokens as collateral. keywords: aave; tokens cache: aave-supply-tokens.html plain text: aave-supply-tokens.txt item: #11 of 3327 id: aave-toggle-collateral-status author: aave title: aave-toggle-collateral-status date: None words: 559 flesch: 53 summary: Parameters such as Loan-to-Value (LTV) and Liquidation Threshold (LT), set by Aave Governance, influence your borrowing power and risk. You can manage the collateral status of your supplied tokens through protocol smart contracts or through a frontend such as Aave Labs interface by performing the following steps: Step 1: Connect Wallet To begin, press ‘Connect Wallet’ and select the Ethereum wallet provider corresponding to the wallet holding the supplied tokens. keywords: aave; collateral cache: aave-toggle-collateral-status.html plain text: aave-toggle-collateral-status.txt item: #12 of 3327 id: aave-voting author: aave title: aave-voting date: None words: 748 flesch: 51 summary: Voting Representatives In Aave Governance, voting representatives facilitate cross-chain voting, especially for users with smart contract wallets or those participating across multiple blockchain networks. Related Aave Community beginner Learn about Aave community governance. keywords: aave; governance; voting cache: aave-voting.html plain text: aave-voting.txt item: #13 of 3327 id: aave-withdraw-tokens author: aave title: aave-withdraw-tokens date: None words: 580 flesch: 57 summary: The process varies slightly depending on the type of token and the withdrawal method, and can be performed through protocl smart contracts or a frontend such as the Aave Labs interface. Step 6: Withdrawing and Switching Tokens The Aave Labs interface also offers a feature to withdraw and switch to a different token in one action. keywords: aave; tokens cache: aave-withdraw-tokens.html plain text: aave-withdraw-tokens.txt item: #14 of 3327 id: app-whitepaper author: app title: app-whitepaper date: 2020-04-06 words: 5061 flesch: 64 summary: This whitepaper describes the mechanics of Uniswap v2’s “core” contracts including the pair contract that stores liquidity providers’ funds—and the factory contract used to instantiate pair contracts. Uniswap v2 allows liquidity providers to create pair contracts for any two ERC-20s. keywords: asset; contract; eth; liquidity; pair; price; uniswap cache: app-whitepaper.pdf plain text: app-whitepaper.txt item: #15 of 3327 id: app-whitepaper-v3 author: app title: app-whitepaper-v3 date: 2021-05-16 words: 6944 flesch: 63 summary: Whenever the price crosses an initialized tick, virtual liquidity is kicked in or out. These represent the total amount of fees that have been earned per unit of virtual liquidity (𝐿), over the entire history of the contract. keywords: liquidity; pool; position; price; range; tick; uniswap cache: app-whitepaper-v3.pdf plain text: app-whitepaper-v3.txt item: #16 of 3327 id: blog-a-few-last-minute-notes author: blog title: blog-a-few-last-minute-notes date: None words: 366 flesch: 53 summary: Difficulty will start at 2^34, this number was decided on based on what we observed on the testnet See you at Genesis! Previous post Next post Subscribe to Protocol Announcements Sign up to receive email notifications for protocol-related announcements, such as network upgrades, FAQs or security issues. We'll let the community come to a consensus on what it is (as there could be multiple blocks #1028201 on the testnet, while it undergoes a re-org, or multiple re-orgs). keywords: protocol cache: blog-a-few-last-minute-notes.html plain text: blog-a-few-last-minute-notes.txt item: #17 of 3327 id: blog-a-message-from-stephan-tual author: blog title: blog-a-message-from-stephan-tual date: None words: 312 flesch: 41 summary: A message from Stephan Tual | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search A message from Stephan Tual Posted by Stephan Tual on September 3, 2015 Organizational To the wonderful Ethereum Community, You often heard me say at conferences that Ethereum was not a company, a foundation, an implementation, or an individual. Sign up Ethereum Foundation • Ethereum.org • ESP • Bug Bounty Program • Do-not-Track • Archive Categories Research & Development • Events • Organizational • Ecosystem Support Program • Ethereum.org • Security • Next Billion • Protocol Announcements keywords: ethereum cache: blog-a-message-from-stephan-tual.html plain text: blog-a-message-from-stephan-tual.txt item: #18 of 3327 id: blog-advanced-contract-programming-example-schellingcoin author: blog title: blog-advanced-contract-programming-example-schellingcoin date: None words: 3879 flesch: 54 summary: HASHES = 2^160 VALUES = 2^170 The first code block sets contract storage index 0 to the current block number at initialization time, and then creates a quicksort contract and saves that in storage index 3. We then hash the sender and value together, and if the hash matches then we save the result in another place in contract storage; an alternative approach is to use one single starting storage location and simply have four slots per hash instead of three. keywords: code; contract; hash; hashes; value cache: blog-advanced-contract-programming-example-schellingcoin.html plain text: blog-advanced-contract-programming-example-schellingcoin.txt item: #19 of 3327 id: blog-announcement-on-planned-exodus-withdrawal author: blog title: blog-announcement-on-planned-exodus-withdrawal date: None words: 754 flesch: 34 summary: Individuals who have contributed loans to the project will receive repayment in BTC directly; we will not be selling any portion of this 2650 BTC on exchanges ourselves, although individuals may choose to independently convert the BTC that they receive into fiat after the fact. Individuals also have the choice of taking the repayment in ether; in those cases, we will simply not send the BTC, and once all repayments have been processed we will publish all of the additional ETH that has been sold in this way (note that this is equivalent to sending individuals their BTC and letting the recipients send it right back into the exodus). keywords: btc; development cache: blog-announcement-on-planned-exodus-withdrawal.html plain text: blog-announcement-on-planned-exodus-withdrawal.txt item: #20 of 3327 id: blog-announcing-eπ-ethereum-on-raspberry-pi-programme author: blog title: blog-announcing-eπ-ethereum-on-raspberry-pi-programme date: None words: 411 flesch: 57 summary: Announcing eπ: Ethereum on Raspberry Pi Programme | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Announcing eπ: Ethereum on Raspberry Pi Programme Posted by Gavin Wood on May 14, 2015 Research & Development As part of our drive to introduce Ethereum to the far corners of the world, not to mention demonstrate the potential for embedded blockchain technology (even without light-nodes) I'm happy to announce the roll-out of our eπ Ethereum-on-Raspberry Pi programme. keywords: ethereum; programme cache: blog-announcing-eπ-ethereum-on-raspberry-pi-programme.html plain text: blog-announcing-eπ-ethereum-on-raspberry-pi-programme.txt item: #21 of 3327 id: blog-announcing-new-foundation-board-executive-director author: blog title: blog-announcing-new-foundation-board-executive-director date: None words: 747 flesch: 32 summary: LinkedIn DR. VADIM DAVID LEVITIN Vadim worked on technology issues in twenty-three countries on behalf of the United Nations. Sign up Ethereum Foundation • Ethereum.org • ESP • Bug Bounty Program • Do-not-Track • Archive Categories Research & Development • Events • Organizational • Ecosystem Support Program • Ethereum.org • Security • Next Billion • Protocol Announcements keywords: board; ethereum; foundation; technology cache: blog-announcing-new-foundation-board-executive-director.html plain text: blog-announcing-new-foundation-board-executive-director.txt item: #22 of 3327 id: blog-another-ethereum-dev-update author: blog title: blog-another-ethereum-dev-update date: None words: 1683 flesch: 53 summary: The default in clients (easily overridden) is not to mine on such chains (since to do so would be a waste of energy), but rather to inform the user that they should upgrade at their earliest opportunity. We are aiming to have all clients through at least a basic auditing process by the Homestead release and I see no reason to use the Go client over other clients (C++ or Python) at this stage, nor, for the vast majority of users, during Frontier. keywords: c++; chain; core; ethereum; protocol cache: blog-another-ethereum-dev-update.html plain text: blog-another-ethereum-dev-update.txt item: #23 of 3327 id: blog-applications-of-security-deposits-and-prediction-markets-you-might-not-have-thought-about author: blog title: blog-applications-of-security-deposits-and-prediction-markets-you-might-not-have-thought-about date: None words: 2086 flesch: 46 summary: However, what if there was a third way to solve this problem, by using our favorite governance mechanism: prediction markets? Prediction markets have so far, including by myself, often been introduced as a governance mechanism that could one day be employed for very large-scale decisions: whether or not we should bail out the banks, hire or fire a particular CEO, or enter a particular trade agreement. The first major use of proof of work was Adam Back's Hashcash, a protocol that tries to fight email spam by making spam emails more expensive to generate. keywords: deposit; email; markets; prediction cache: blog-applications-of-security-deposits-and-prediction-markets-you-might-not-have-thought-about.html plain text: blog-applications-of-security-deposits-and-prediction-markets-you-might-not-have-thought-about.txt item: #24 of 3327 id: blog-bazaar-services author: blog title: blog-bazaar-services date: None words: 1627 flesch: 50 summary: This is in stark contrast to when I was writing my degree dissertation open source software in the business environment, shortly after ESR wrote the Cathedral and the Bazaar, when Microsoft and its gigantic closed source codebase was the undisputed leader and there were but one or two serious examples of open source software being used commercially. It is no surprise that the rise of the internet with CVS, IRC, Usenet and mailing lists coincided with that of open source software. keywords: bazaar; development; services; software; source cache: blog-bazaar-services.html plain text: blog-bazaar-services.txt item: #25 of 3327 id: blog-bitcoin-maximalism-currency-platform-network-effects author: blog title: blog-bitcoin-maximalism-currency-platform-network-effects date: None words: 5264 flesch: 44 summary: On the other hand, however, currency network effects are another story, and may indeed prove to be a genuine advantage for Bitcoin-based sidechains over fully independent networks. Thus, we see that while currency network effects are sometimes moderately strong, and they will indeed exert a preference pressure in favor of Bitcoin over other existing cryptocurrencies, the creation of an ecosystem that uses Bitcoin exclusively is a highly suspect endeavor, and one that will lead to a total reduction and increased centralization of funding (as only the ultra-rich have sufficient concentrated incentive to be speculative philanthropists), closed doors in security (no more proof of stake), and is not even necessarily guaranteed to end with Bitcoin willing. keywords: bitcoin; blockchain; currencies; currency; effect; network; platform; use cache: blog-bitcoin-maximalism-currency-platform-network-effects.html plain text: blog-bitcoin-maximalism-currency-platform-network-effects.txt item: #26 of 3327 id: blog-blockchain-scalability-chain-fibers-redux author: blog title: blog-blockchain-scalability-chain-fibers-redux date: None words: 1992 flesch: 52 summary: Fishermen: search for invalid or unavailable X-fiber blocks They check the X-fiber blocks looking for validity errors and/or inavailability of data. What follows is a fairly complete illustration of one particular possible plan for block chain scalability in a later version of Ethereum. keywords: block; fiber; state; transaction; validators cache: blog-blockchain-scalability-chain-fibers-redux.html plain text: blog-blockchain-scalability-chain-fibers-redux.txt item: #27 of 3327 id: blog-bootstrapping-a-decentralized-autonomous-corporation-part-3-identity-corp author: blog title: blog-bootstrapping-a-decentralized-autonomous-corporation-part-3-identity-corp date: None words: 3157 flesch: 43 summary: Currently, government-based identity systems do not use this information too much because government identity documents follow a centralized parent-child model: you want a social insurance number, you need to provide your passport, you lost your passport, you provide a birth certificate and possibly change-of-name certificates if applicable. These tactics can perhaps be themselves corrected for, but ultimately relying solely or even largely on such mechanisms is a recipe for statistical warfare, not any kind of stable identity system. keywords: corporation; government; identity; network; system; world cache: blog-bootstrapping-a-decentralized-autonomous-corporation-part-3-identity-corp.html plain text: blog-bootstrapping-a-decentralized-autonomous-corporation-part-3-identity-corp.txt item: #28 of 3327 id: blog-bootstrapping-a-decentralized-autonomous-corporation-part-i author: blog title: blog-bootstrapping-a-decentralized-autonomous-corporation-part-i date: None words: 2105 flesch: 49 summary: As it turns out, secure multiparty computation can be used to generate Bitcoin addresses and sign transactions. A virtual corporation, on the other hand, would likely need to store the private key to its Bitcoin wallet – a piece of data which should be available in its entirety to no one, not to everyone in the way that Bitcoin transactions are. keywords: bitcoin; computation; corporation; key cache: blog-bootstrapping-a-decentralized-autonomous-corporation-part-i.html plain text: blog-bootstrapping-a-decentralized-autonomous-corporation-part-i.txt item: #29 of 3327 id: blog-bootstrapping-an-autonomous-decentralized-corporation-part-2-interacting-with-the-world author: blog title: blog-bootstrapping-an-autonomous-decentralized-corporation-part-2-interacting-with-the-world date: None words: 3309 flesch: 52 summary: Bootstrapping An Autonomous Decentralized Corporation, Part 2: Interacting With the World | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Bootstrapping An Autonomous Decentralized Corporation, Part 2: Interacting With the World Posted by Vitalik Buterin on December 31, 2013 Research & Development In the first part of this series, we talked about how the internet allows us to create decentralized corporations, automatons that exist entirely as decentralized networks over the internet, carrying out the computations that keep them “alive” over thousands of servers. Technically, if decentralized corporations started getting into crop insurance this would change somewhat, but even there the risk would be smaller, since there wowuld be two groups pulling in opposite directions (namely, farmers who want to pretend that there are droughts, and insurers who want to pretend that there are not). keywords: api; bitcoin; corporation; data; network; price cache: blog-bootstrapping-an-autonomous-decentralized-corporation-part-2-interacting-with-the-world.html plain text: blog-bootstrapping-an-autonomous-decentralized-corporation-part-2-interacting-with-the-world.txt item: #30 of 3327 id: blog-building-decentralized-web author: blog title: blog-building-decentralized-web date: None words: 1369 flesch: 40 summary: the explosion of web services Taking a look back at the brief history of the web, most would agree that Web 1.0 was epitomized by CGI scripts generating templated content on a server and delivering it to the client in a final form. This was a clear model of monolithic centralization, however, this basic form of interactivity was a huge improvement over the basic post-and-read format that comprised much of internet content at that time. keywords: content; ethereum; internet; protocol; web cache: blog-building-decentralized-web.html plain text: blog-building-decentralized-web.txt item: #31 of 3327 id: blog-call-bug-bounty-hunters author: blog title: blog-call-bug-bounty-hunters date: None words: 348 flesch: 53 summary: Previous post Next post Subscribe to Protocol Announcements Sign up to receive email notifications for protocol-related announcements, such as network upgrades, FAQs or security issues. Sign up Ethereum Foundation • Ethereum.org • ESP • Bug Bounty Program • Do-not-Track • Archive Categories Research & Development • Events • Organizational • Ecosystem Support Program • Ethereum.org • Security • Next Billion • Protocol Announcements keywords: bounty; program cache: blog-call-bug-bounty-hunters.html plain text: blog-call-bug-bounty-hunters.txt item: #32 of 3327 id: blog-chain-reorganisation-depth-expectations author: blog title: blog-chain-reorganisation-depth-expectations date: None words: 950 flesch: 51 summary: Chain reorganisations happen when a node on the Ethereum network (one which could belong to you, me, an exchange, a miner, whoever) realises that what it thought was the canonical chain turned out not to be. Chain Reorganisation Depth Expectations | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Chain Reorganisation Depth Expectations Posted by Gavin Wood on August 8, 2015 Research & Development keywords: chain; reorganisation cache: blog-chain-reorganisation-depth-expectations.html plain text: blog-chain-reorganisation-depth-expectations.txt item: #33 of 3327 id: blog-conference-alpha-testnet-and-ether-pre-sale-updates author: blog title: blog-conference-alpha-testnet-and-ether-pre-sale-updates date: None words: 519 flesch: 41 summary: A compiler from the Ethereum CLL to Ethereum script will be released very soon. We traveled there anticipating many technical questions as well as a philosophical discussion about the purpose of Ethereum; however, the overwhelming amount of interest and enthusiasm for the project was much larger than we had anticipated. keywords: ethereum; sale cache: blog-conference-alpha-testnet-and-ether-pre-sale-updates.html plain text: blog-conference-alpha-testnet-and-ether-pre-sale-updates.txt item: #34 of 3327 id: blog-crypto-renaissance author: blog title: blog-crypto-renaissance date: None words: 2367 flesch: 45 summary: As a thought experiment, if we would overlap today’s technological renaissance with the 14th-17th century renaissance we would observe the following: Introduced a new method for storing and distributing information in society Period marked by important technical achievements allowing a faster propagation of ideas Ignited experimentation and an intellectual revitalization Triggered paradigm shifts deepening our understanding of the world, ourselves and the universe Resulted in social, political and economic transformations If we draw the parallels we can see how information technologies enable positive growth within society since Mesopotamian ages. In this line of thinking, open source can be seen as a pattern of collaboration in itself, being part of a bigger pattern: open collaboration. keywords: information; innovation; internet; invention; open; society; technology cache: blog-crypto-renaissance.html plain text: blog-crypto-renaissance.txt item: #35 of 3327 id: blog-cryptographic-code-obfuscation-decentralized-autonomous-organizations-are-about-to-take-a-huge-leap-forward author: blog title: blog-cryptographic-code-obfuscation-decentralized-autonomous-organizations-are-about-to-take-a-huge-leap-forward date: None words: 2116 flesch: 47 summary: In the developed world, the hope is that there will be a massive reduction in the cost of setting up a new business, organization or partnership, and a tool for creating organizations that are much more difficult to corrupt. However, aside from that, obfuscation is powerful in another key way, and one which has profound consequences particularly in the field of cryptocurrencies and decentralized autonomous organizations: publicly running contracts can now contain private data. keywords: ethereum; key; obfuscation; organizations; program cache: blog-cryptographic-code-obfuscation-decentralized-autonomous-organizations-are-about-to-take-a-huge-leap-forward.html plain text: blog-cryptographic-code-obfuscation-decentralized-autonomous-organizations-are-about-to-take-a-huge-leap-forward.txt item: #36 of 3327 id: blog-daos-are-not-scary-part-1-self-enforcing-contracts-and-factum-law author: blog title: blog-daos-are-not-scary-part-1-self-enforcing-contracts-and-factum-law date: None words: 2756 flesch: 59 summary: Smart contracts are an idea that has been around for several decades, but was given its current name and first substantially brought to the (cryptography-inclined) public’s attention by Nick Szabo in 2005. Nick Szabo uses the example of a vending machine: A canonical real-life example, which we might consider to be the primitive ancestor of smart contracts, is the humble vending machine. keywords: contract; example; factum; job; judge; money cache: blog-daos-are-not-scary-part-1-self-enforcing-contracts-and-factum-law.html plain text: blog-daos-are-not-scary-part-1-self-enforcing-contracts-and-factum-law.txt item: #37 of 3327 id: blog-daos-are-not-scary-part-2-reducing-barriers author: blog title: blog-daos-are-not-scary-part-2-reducing-barriers date: None words: 1837 flesch: 53 summary: Instead of relying on legal contracts using expensive (and often, especially in international circumstances and poor countries, ineffective) court systems, or even moderately expensive private arbitration services, business relationships can be governed by smart contracts where those parts of the contract that do need human interpretation can be segregated into many specialized parts. We also discussed the limits of smart contracts, and how a smart contract-enabled legal system might use a combination of human judgement and automatic execution to achieve the best possible outcomes. keywords: agent; contracts; escrow; money cache: blog-daos-are-not-scary-part-2-reducing-barriers.html plain text: blog-daos-are-not-scary-part-2-reducing-barriers.txt item: #38 of 3327 id: blog-daos-dacs-das-and-more-an-incomplete-terminology-guide author: blog title: blog-daos-dacs-das-and-more-an-incomplete-terminology-guide date: None words: 3644 flesch: 49 summary: Decentralized Autonomous Organizations Here, we get into what is perhaps the holy grail, the thing that has the murkiest definition of all: decentralized autonomous organizations, and their corporate subclass, decentralized autonomous corporations (or, more recently, “companies”). As we’ll see below, my classification of decentralized autonomous organizations touches on such concepts, and it is not quite clear exactly where they sit. keywords: bitcoin; contract; dao; example; parties; property cache: blog-daos-dacs-das-and-more-an-incomplete-terminology-guide.html plain text: blog-daos-dacs-das-and-more-an-incomplete-terminology-guide.txt item: #39 of 3327 id: blog-decentralized-protocol-monetization-and-forks author: blog title: blog-decentralized-protocol-monetization-and-forks date: None words: 3470 flesch: 41 summary: Ecosystemic Network Effects An important feature of decentralized protocols, and social protocols in general, is that they also build ecosystems. With decentralized protocols, however, we have discovered a new mechanism for monetizing them: create internal assets, and sell them to pay for the development of the protocol. keywords: bitcoin; ethereum; fork; network; people; protocol; system cache: blog-decentralized-protocol-monetization-and-forks.html plain text: blog-decentralized-protocol-monetization-and-forks.txt item: #40 of 3327 id: blog-devcon-0-recap author: blog title: blog-devcon-0-recap date: None words: 2426 flesch: 54 summary: Jeff Wilcke also gave a brief update on Ethereum Go client on the whiteboard before the panel discussion. Following the presentation on ÐApps, Gavin invited everyone present to introduce themselves and explain their roles in Ethereum. keywords: client; day; ethereum; network; presentation; protocol; team cache: blog-devcon-0-recap.html plain text: blog-devcon-0-recap.txt item: #41 of 3327 id: blog-devcon-is-back author: blog title: blog-devcon-is-back date: None words: 601 flesch: 45 summary: Expect talks from development teams sharing what they have learned, and detailed talks about the new businesses and business models enabled by the Ethereum platform. | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search DEVcon is back! keywords: development; ethereum cache: blog-devcon-is-back.html plain text: blog-devcon-is-back.txt item: #42 of 3327 id: blog-devcon-one-postponed-until-further-notice author: blog title: blog-devcon-one-postponed-until-further-notice date: None words: 170 flesch: 43 summary: devcon one postponed until further notice | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search devcon one postponed until further notice Posted by George Hallam on September 2, 2015 Events Unfortunately we were not able to secure the venue for devcon one in London on the dates desired (October 5th-8th). As a consequence we are postponing the event until further notice. keywords: protocol cache: blog-devcon-one-postponed-until-further-notice.html plain text: blog-devcon-one-postponed-until-further-notice.txt item: #43 of 3327 id: blog-devgrants-help author: blog title: blog-devgrants-help date: None words: 1146 flesch: 50 summary: Interested parties may also follow @DEVgrants on Twitter for updates about funded projects, evaluation policy changes, and more. Indeed, even before genesis, Ethereum already boasts hundreds of projects covering everything from self-stabilizing currency to potential replacements for government services. keywords: ethereum; project; ðξvgrants cache: blog-devgrants-help.html plain text: blog-devgrants-help.txt item: #44 of 3327 id: blog-ether-purchase-troubleshooting author: blog title: blog-ether-purchase-troubleshooting date: None words: 689 flesch: 64 summary: Previous post Next post Subscribe to Protocol Announcements Sign up to receive email notifications for protocol-related announcements, such as network upgrades, FAQs or security issues. Sign up Ethereum Foundation • Ethereum.org • ESP • Bug Bounty Program • Do-not-Track • Archive Categories Research & Development • Events • Organizational • Ecosystem Support Program • Ethereum.org • Security • Next Billion • Protocol Announcements keywords: pyethsaletool.py; python cache: blog-ether-purchase-troubleshooting.html plain text: blog-ether-purchase-troubleshooting.txt item: #45 of 3327 id: blog-ether-sale-a-statistical-overview author: blog title: blog-ether-sale-a-statistical-overview date: None words: 1398 flesch: 46 summary: Note that Gini coefficients of wealth and Gini coefficients of income are different things; one measures how much people have and one measures the rate at which people receive. Given that Gini coefficients in the real world measure inequality of access to resources, and Gini coefficients in cryptocurrency distribution arise from both inequality of resources and inequality of interest (some people care about Ethereum slightly, some care about it a whole lot), 0.836 is a pretty decent result - as a point of comparison, the Gini coefficient of Bitcoin has been measured at 0.877. keywords: btc; ether; gini cache: blog-ether-sale-a-statistical-overview.html plain text: blog-ether-sale-a-statistical-overview.txt item: #46 of 3327 id: blog-ethereum-and-oracles author: blog title: blog-ethereum-and-oracles date: None words: 2591 flesch: 51 summary: Ethereum and Oracles | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Ethereum and Oracles Posted by Vitalik Buterin on July 22, 2014 Research & Development One of the more popular proposals for implementing smart contracts differently from the way they are typically presented in Ethereum is through the concept of oracles. A common misconception is that the primary feature of Ethereum is that it is Turing-complete, and so while Bitcoin only allows quick scripts for verification Ethereum contracts are means to do much harder and computationally intensive tasks. keywords: blockchain; code; contract; ethereum; oracles cache: blog-ethereum-and-oracles.html plain text: blog-ethereum-and-oracles.txt item: #47 of 3327 id: blog-ethereum-builders-experiment author: blog title: blog-ethereum-builders-experiment date: None words: 2035 flesch: 56 summary: Exploring a few use cases: Connecting Ethereum builders with each other Think of Twitch, but for Ethereum hacking. A proposed experiment: Ethereum Builders “In times of change, learners inherit the earth, while the learned find themselves beautifully equipped to deal with a world that no longer exists.” —Eric Hoffer While exploring the idea behind educational portals (i.e. Code Academy) and researching into the effectiveness of different approaches, I stumbled upon a study on students taking online courses. keywords: ethereum; experiment; knowledge; project; things cache: blog-ethereum-builders-experiment.html plain text: blog-ethereum-builders-experiment.txt item: #48 of 3327 id: blog-ethereum-builders-supercharging-github author: blog title: blog-ethereum-builders-supercharging-github date: None words: 2234 flesch: 55 summary: For now, you can use the below as an incomplete map of the open Ethereum Gitter rooms: Live projects/experiments Ethereum Builders Hello (General chatroom) Ethereum Go/Mist Implementation Bellow is a reddit post that sums it up nicely: From the design stage, Ethereum Builders was envisioned as a tool that would lower the entry barriers, increase the community member interaction and bring the fun of working together closer to everyone. keywords: builders; community; ethereum; github; people; project cache: blog-ethereum-builders-supercharging-github.html plain text: blog-ethereum-builders-supercharging-github.txt item: #49 of 3327 id: blog-ethereum-comms-announcement author: blog title: blog-ethereum-comms-announcement date: None words: 458 flesch: 27 summary: We will de-emphasize the ETH DEV brand (with the exception of DEVcon) and focus attention on Ethereum going forward In the medium term, we are in the process of substantially re-examining our strategy internally including meetups, general community outreach, trademark policy, developer documentation, and communicating information on protocol updates (e.g the most pressing short-term updates will be at the networking level to faciliate support of light clients, and larger future changes will be for proof of stake, scalability, etc), as well as interacting with the rapidly growing number of both individual and organizational/corporate Ethereum developers outside of the foundation proper. Sign up Ethereum Foundation • Ethereum.org • ESP • Bug Bounty Program • Do-not-Track • Archive Categories Research & Development • Events • Organizational • Ecosystem Support Program • Ethereum.org • Security • Next Billion • Protocol Announcements keywords: ethereum; protocol cache: blog-ethereum-comms-announcement.html plain text: blog-ethereum-comms-announcement.txt item: #50 of 3327 id: blog-ethereum-community-survey author: blog title: blog-ethereum-community-survey date: None words: 1658 flesch: 60 summary: The blog and social media interaction will continue to deliver Ethereum content on relevant channels with the aim of reaching the widest range of people as possible.   Ethereum Community Survey | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Ethereum Community Survey Posted by George Hallam on January 9, 2015 Research & Development Back in November, we created a quick survey for the Ethereum community to help us gauge how we're doing, what can be improved, and how best we can engage with you all as we move forward towards the genesis block release in March. keywords: community; ethereum; new; people; survey cache: blog-ethereum-community-survey.html plain text: blog-ethereum-community-survey.txt item: #51 of 3327 id: blog-ethereum-dev author: blog title: blog-ethereum-dev date: None words: 690 flesch: 22 summary: Aside from having quasi-Turing-completeness, it delivers on a number of other important considerations, stemming from the fact we are developing entirely new blockchain technology including: speedy, through a 12 second blocktime; light-client-friendly through the use of Merkle roots in headers for compact inclusion/state proofs and DHT integration to allow light clients to host & share small parts of the full chain; ÐApp-friendly, even for light-clients, through the use of multi-level Bloom filters and transaction receipt Merkle tries to allow for lightweight log-indexing and proofs; finite-blockchain-friendly - we designed the core protocol to facilitate upgrading to this technology, further reducing light-client footprint and helping guarantee mid-term scalability; ASIC-unfriendly - through the (as yet unconfirmed) choice of PoW algo and the threat we'll be upgrading to PoS in the Not-Too-Distant future. Thirdly, to facilitate adoption of this technology, gain testers and spur further development we are developing, collaborating over and sponsoring a number of force-multiplying technologies that leverage pre-existing technology including: a graphical client browser (leveraging drop-in browser components from the Chromium project and Qt 5 technology); a set of basic contracts and ÐApps, including for registration, reputation, web-of-trust and accounting (leveraging the pre-existing compilers and development tech); a hybrid multi-DHT/messaging system, codenamed Whisper (leveraging the pre-existing p2p back end & protocols); a simple reverse-hash lookup DHT, codenamed Swarm (also leveraging the pre-existing p2p back end & protocols), for which there is an ongoing internal implementation, but which could end up merging or being a collaboration with the IPFS project. keywords: development; ethereum; technology cache: blog-ethereum-dev.html plain text: blog-ethereum-dev.txt item: #52 of 3327 id: blog-ethereum-dev-update-2015-week-41 author: blog title: blog-ethereum-dev-update-2015-week-41 date: None words: 449 flesch: 51 summary: Previous post Next post Subscribe to Protocol Announcements Sign up to receive email notifications for protocol-related announcements, such as network upgrades, FAQs or security issues. Ethereum Dev Update 2015 / keywords: ethereum; protocol cache: blog-ethereum-dev-update-2015-week-41.html plain text: blog-ethereum-dev-update-2015-week-41.txt item: #53 of 3327 id: blog-ethereum-dev-update-2015-week-44 author: blog title: blog-ethereum-dev-update-2015-week-44 date: None words: 414 flesch: 45 summary: Light client/mobile New network protocols supporting fast sync are rapidly maturing and will be basis for future light clients, helping new users bootstrap into the network within just a few minutes. Work has been done on state trie pruning and upgrading network protocols (PV 62 & 63). keywords: ethereum; protocol cache: blog-ethereum-dev-update-2015-week-44.html plain text: blog-ethereum-dev-update-2015-week-44.txt item: #54 of 3327 id: blog-ethereum-development-process author: blog title: blog-ethereum-development-process date: None words: 378 flesch: 52 summary: Meanwhile, Christoph devises and codes tests, populating the results either manually or with the farthest-ahead of the implementations (C++, generally :-P). So far, this has proved to be an effective way of producing well-tested code quickly, and perhaps more importantly, in delivering clear unambiguous formal specifications. keywords: development; protocol cache: blog-ethereum-development-process.html plain text: blog-ethereum-development-process.txt item: #55 of 3327 id: blog-ethereum-foundation-is-hiring-an-executive-director author: blog title: blog-ethereum-foundation-is-hiring-an-executive-director date: None words: 411 flesch: 26 summary: Ethereum Foundation is hiring an Executive Director | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Ethereum Foundation is hiring an Executive Director Posted by Anthony Di Iorio on April 8, 2015 Organizational Stiftung Ethereum, the Zug, Switzerland-based Ethereum Foundation --ethereum.org, is seeking to immediately fill the Executive Director position within the Foundation. Sign up Ethereum Foundation • Ethereum.org • ESP • Bug Bounty Program • Do-not-Track • Archive Categories Research & Development • Events • Organizational • Ecosystem Support Program • Ethereum.org • Security • Next Billion • Protocol Announcements keywords: ethereum; foundation cache: blog-ethereum-foundation-is-hiring-an-executive-director.html plain text: blog-ethereum-foundation-is-hiring-an-executive-director.txt item: #56 of 3327 id: blog-ethereum-foundation-open-call-re-board-selection author: blog title: blog-ethereum-foundation-open-call-re-board-selection date: None words: 762 flesch: 30 summary: Sign up Ethereum Foundation • Ethereum.org • ESP • Bug Bounty Program • Do-not-Track • Archive Categories Research & Development • Events • Organizational • Ecosystem Support Program • Ethereum.org • Security • Next Billion • Protocol Announcements The ideal characteristics that we are looking for in potential board candidates include: Experience participating in non-profit boards Status as a leader and innovator in a field (for-profit or non-profit) which could be benefited by blockchain and decentralized application technology, ideally outside of the existing cryptocurrency space. keywords: board; ethereum; foundation cache: blog-ethereum-foundation-open-call-re-board-selection.html plain text: blog-ethereum-foundation-open-call-re-board-selection.txt item: #57 of 3327 id: blog-ethereum-in-practice-part-2-how-to-build-a-better-democracy-in-under-a-100-lines-of-code author: blog title: blog-ethereum-in-practice-part-2-how-to-build-a-better-democracy-in-under-a-100-lines-of-code date: None words: 1315 flesch: 68 summary: So let's go back to Contracts and then Deploy Contract and paste the DAO source code on the Solidity Source field. On the read from contract you can see all the functions you can execute for free on the contract, as they are just reading information from the blockchain. keywords: contract; ether; proposal cache: blog-ethereum-in-practice-part-2-how-to-build-a-better-democracy-in-under-a-100-lines-of-code.html plain text: blog-ethereum-in-practice-part-2-how-to-build-a-better-democracy-in-under-a-100-lines-of-code.txt item: #58 of 3327 id: blog-ethereum-in-practice-part-3-how-to-build-your-own-transparent-bank-on-the-blockchain author: blog title: blog-ethereum-in-practice-part-3-how-to-build-your-own-transparent-bank-on-the-blockchain date: None words: 1175 flesch: 63 summary: So save the address of your current DAO in a note pad (pay attention to the icon) and grab this source code and you know the drill: contracts > deploy new contract > solidity source code > pick contract You can fill the parameters any way you want (yes, emojis are permitted on the string fields) but you'll notice one new field that didn't exist before: Central Minter. Now go back to the democracy contract and create a new proposal with these parameters: As the beneficiary, put the address of your new token Leave etherAmount blank On the jobDescription just write a small description that you are minting new coins On the transactionBytecode, paste the bytecode you saved from the data field on the previous step     In a few seconds you should be able to see that the details on the proposal. keywords: address; code; contract cache: blog-ethereum-in-practice-part-3-how-to-build-your-own-transparent-bank-on-the-blockchain.html plain text: blog-ethereum-in-practice-part-3-how-to-build-your-own-transparent-bank-on-the-blockchain.txt item: #59 of 3327 id: blog-ethereum-launch-process author: blog title: blog-ethereum-launch-process date: None words: 2849 flesch: 59 summary: We will have a pretty good idea of whether things are going smoothly or not from network review, so we will keep you in the loop through this process. Previous post Next post Subscribe to Protocol Announcements Sign up to receive email notifications for protocol-related announcements, such as network upgrades, FAQs or security issues. keywords: ether; ethereum; frontier; network; process; release cache: blog-ethereum-launch-process.html plain text: blog-ethereum-launch-process.txt item: #60 of 3327 id: blog-ethereum-launches author: blog title: blog-ethereum-launches date: None words: 291 flesch: 57 summary: Ethereum Launches | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Ethereum Launches Posted by Stephan Tual on July 30, 2015 Protocol Announcements A few minutes ago, many of you generated and loaded the Ethereum Genesis block, marking the inception of Frontier, the first Live release of the Ethereum project. Previous post Next post Subscribe to Protocol Announcements Sign up to receive email notifications for protocol-related announcements, such as network upgrades, FAQs or security issues. keywords: ethereum cache: blog-ethereum-launches.html plain text: blog-ethereum-launches.txt item: #61 of 3327 id: blog-ethereum-messaging-masses-including-fathers-via-infographic author: blog title: blog-ethereum-messaging-masses-including-fathers-via-infographic date: None words: 941 flesch: 54 summary: I’m missing father’s day with my Dad (and my brother's first fathers day) to be in Switzerland on Ethereum business. Sign up Ethereum Foundation • Ethereum.org • ESP • Bug Bounty Program • Do-not-Track • Archive Categories Research & Development • Events • Organizational • Ecosystem Support Program • Ethereum.org • Security • Next Billion • Protocol Announcements keywords: announcements; ethereum; protocol cache: blog-ethereum-messaging-masses-including-fathers-via-infographic.html plain text: blog-ethereum-messaging-masses-including-fathers-via-infographic.txt item: #62 of 3327 id: blog-ethereum-now-going-public author: blog title: blog-ethereum-now-going-public date: None words: 2088 flesch: 42 summary: The first holon will be based inside of Bitcoin Decentral in Toronto, and a substantial portion of Ethereum development will take place there; anyone who is seriously interested in participating heavily in Ethereum should consider giving us a visit over the next month. Who is Ethereum The core Ethereum team includes four members:   Vitalik Buterin Vitalik Buterin first joined the Bitcoin community in March 2011, and co-founded Bitcoin Magazine with Mihai Alisie in September 2011. keywords: bitcoin; development; ecosystem; ethereum; projects; work cache: blog-ethereum-now-going-public.html plain text: blog-ethereum-now-going-public.txt item: #63 of 3327 id: blog-ethereum-project-update author: blog title: blog-ethereum-project-update date: None words: 504 flesch: 47 summary: Please stay tuned to this channel as we will continue to release information regarding software development activities and details of the pre-sale for absorption and feedback. But that effort is now substantially complete and Charles will be moving on to other activities in the space. keywords: development; project cache: blog-ethereum-project-update.html plain text: blog-ethereum-project-update.txt item: #64 of 3327 id: blog-ethereum-protocol-update-1 author: blog title: blog-ethereum-protocol-update-1 date: None words: 983 flesch: 62 summary: That rate is equal to previous block limit / 1024. Default, community chosen, Genesis block The Genesis block we have seen adopted by the community has now been hardcoded in the clients, and you no longer need to specify the --genesis parameter to start eth or geth. keywords: block; protocol; update cache: blog-ethereum-protocol-update-1.html plain text: blog-ethereum-protocol-update-1.txt item: #65 of 3327 id: blog-ethereum-scalability-and-decentralization-updates author: blog title: blog-ethereum-scalability-and-decentralization-updates date: None words: 2177 flesch: 55 summary: If Bitcoin blocks become 2 GB in size, the proofs might expand to a whole kilobyte. If F’s claim is false, and the block is valid at that point, then M can produce a proof of localized consistency by showing a Merkle tree proof of point k in the stack trace, point k+1 in the stack trace, and the subset of Merkle tree nodes in the state and transaction tree that were modified during the process of updating from k to k+1. keywords: block; proof; protocol; transaction cache: blog-ethereum-scalability-and-decentralization-updates.html plain text: blog-ethereum-scalability-and-decentralization-updates.txt item: #66 of 3327 id: blog-ethereum-the-first-year author: blog title: blog-ethereum-the-first-year date: None words: 3267 flesch: 62 summary: I am Mihai Alisie, one of the Ethereum founders, and for the past year I’ve served as the Vice President of the Ethereum Foundation and Director of Ethereum Switzerland. On the other Ethereum Project fronts, by June we advanced to the fourth version of the Proof of Concept implementations, rapidly moving towards the fifth version; our Twitter followers number surpassed 6,000; and the number of global meetups that focused on Ethereum reached 58 groups in 49 different cities, spread over 19 countries. keywords: community; ethereum; genesis; project; sale; things; time; world cache: blog-ethereum-the-first-year.html plain text: blog-ethereum-the-first-year.txt item: #67 of 3327 id: blog-ethereum-wallet-developer-preview author: blog title: blog-ethereum-wallet-developer-preview date: None words: 1005 flesch: 68 summary: Using the wallet The wallet allows you to create two types of  wallets: A simple wallet - works like a normal account (additional features are being worked on; e.g. adding owners, setting a daily limit) A multisig wallet - allows you to add any number of owner accounts and set a daily limit. Deleting wallets If you’d like to delete a wallet click the trash icon on the wallet page, next to the wallet name. keywords: developer; geth; wallet cache: blog-ethereum-wallet-developer-preview.html plain text: blog-ethereum-wallet-developer-preview.txt item: #68 of 3327 id: blog-ethereums-unexpected-future-direction author: blog title: blog-ethereums-unexpected-future-direction date: None words: 466 flesch: 43 summary: Valve has the clout to get mining software on to the majority of those machines simply by making it available to users and asking them nicely to download it, in exchange for participation in the network and the chance to make a little credit - redeemable for future Steam purchases and downloadable content.  Sign up Ethereum Foundation • Ethereum.org • ESP • Bug Bounty Program • Do-not-Track • Archive Categories Research & Development • Events • Organizational • Ecosystem Support Program • Ethereum.org • Security • Next Billion • Protocol Announcements keywords: ethereum; protocol cache: blog-ethereums-unexpected-future-direction.html plain text: blog-ethereums-unexpected-future-direction.txt item: #69 of 3327 id: blog-final-steps author: blog title: blog-final-steps date: None words: 1369 flesch: 53 summary: Please be especially wary of third party websites and software of unknown origin -- Ethereum will only ever publish software through its github platform at https://github.com/ethereum/. Finally, for clarity, it’s important to note that the Olympic program ended at block 1M this morning, however, the bug bounty is still on --- and will continue until further notice. Then, it's a matter of waiting for block #1028201, which at the current block resolution time, should be formed approximately Thursday evening GMT+0. keywords: block; ethereum; genesis; release cache: blog-final-steps.html plain text: blog-final-steps.txt item: #70 of 3327 id: blog-frontier-first-100k-blocks author: blog title: blog-frontier-first-100k-blocks date: None words: 736 flesch: 68 summary: Let's now look at the average block time (every 200th block from genesis to block 10000): We can see the hashing power really attacking the network after the first few hundred blocks, with block times at 1-2 seconds as the difficulty adjustment algorithm is catching up. After a few thousand blocks, we see the difficulty going up enough for block times to get into the 4-5 second range. keywords: blocks; power cache: blog-frontier-first-100k-blocks.html plain text: blog-frontier-first-100k-blocks.txt item: #71 of 3327 id: blog-frontier-is-coming-what-to-expect-and-how-to-prepare author: blog title: blog-frontier-is-coming-what-to-expect-and-how-to-prepare date: None words: 1469 flesch: 62 summary: Note that rewards will not be part of the Frontier Genesis block, but instead will be handed out by a Foundation bot during the weeks following the release. Frontier is coming - what to expect, and how to prepare | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Frontier is coming - what to expect, and how to prepare Posted by Stephan Tual on July 22, 2015 Protocol Announcements We are only days away from launching 'Frontier', the first milestone in the release of the Ethereum project. keywords: block; ethereum; frontier; network cache: blog-frontier-is-coming-what-to-expect-and-how-to-prepare.html plain text: blog-frontier-is-coming-what-to-expect-and-how-to-prepare.txt item: #72 of 3327 id: blog-gavs-dev-update-ethereums author: blog title: blog-gavs-dev-update-ethereums date: None words: 2803 flesch: 54 summary: I'm Gav - together with Jeffrey Wilcke and Vitalik Buterin, I'm one third of the ultimate leadership of Ethereum ÐΞV. Similarly, Caktux an early volunteer and maintainer of the Ncurses-based C++ Ethereum front-end neth has been invaluble (alongside Joris and Nick Savers) in getting a continuous integration system up and running. keywords: berlin; development; ethereum; protocol; software; time; web; ðξv cache: blog-gavs-dev-update-ethereums.html plain text: blog-gavs-dev-update-ethereums.txt item: #73 of 3327 id: blog-gavs-dev-update-iii author: blog title: blog-gavs-dev-update-iii date: None words: 1287 flesch: 58 summary: Gav’s Ethereum ÐΞV Update III | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Gav’s Ethereum ÐΞV Update III Posted by Gavin Wood on November 18, 2014 Research & Development I'm Gavin Wood, a co-founder of Ethereum and, along with Vitalik Buterin and Jeffrey Wilcke, one of the three directors of the Eth Dev, the NFP organisation that is managing the development (under contract from Ethereum Suisse) of the Ethereum blockchain. Sign up Ethereum Foundation • Ethereum.org • ESP • Bug Bounty Program • Do-not-Track • Archive Categories Research & Development • Events • Organizational • Ecosystem Support Program • Ethereum.org • Security • Next Billion • Protocol Announcements keywords: berlin; development; ethereum; time cache: blog-gavs-dev-update-iii.html plain text: blog-gavs-dev-update-iii.txt item: #74 of 3327 id: blog-gavs-ethereum-dev-update-ii author: blog title: blog-gavs-ethereum-dev-update-ii date: None words: 952 flesch: 56 summary: If you don't already know, I'm Gavin, a founder of Ethereum and one of the three directors (alongside Vitalik and Jeffrey) of Ethereum ÐΞV, the development entity building Ethereum and all the associated technology. Sign up Ethereum Foundation • Ethereum.org • ESP • Bug Bounty Program • Do-not-Track • Archive Categories Research & Development • Events • Organizational • Ecosystem Support Program • Ethereum.org • Security • Next Billion • Protocol Announcements keywords: berlin; ethereum; network; team cache: blog-gavs-ethereum-dev-update-ii.html plain text: blog-gavs-ethereum-dev-update-ii.txt item: #75 of 3327 id: blog-gavs-ethereum-dev-update-iv author: blog title: blog-gavs-ethereum-dev-update-iv date: None words: 1099 flesch: 57 summary: Sign up Ethereum Foundation • Ethereum.org • ESP • Bug Bounty Program • Do-not-Track • Archive Categories Research & Development • Events • Organizational • Ecosystem Support Program • Ethereum.org • Security • Next Billion • Protocol Announcements Of late, I have been working to finish up the formal specification of Ethereum, the Yellow Paper, and make it up to date with the latest protocol changes in order that the security audit get underway. keywords: ethereum; protocol; security; time cache: blog-gavs-ethereum-dev-update-iv.html plain text: blog-gavs-ethereum-dev-update-iv.txt item: #76 of 3327 id: blog-gavs-ethereum-dev-update-v author: blog title: blog-gavs-ethereum-dev-update-v date: None words: 1419 flesch: 54 summary: We'll hopefully be able to announce his successors next week (yes, that was plural; he has been doing the jobs of 2.5 people over the last few months). Sign up Ethereum Foundation • Ethereum.org • ESP • Bug Bounty Program • Do-not-Track • Archive Categories Research & Development • Events • Organizational • Ecosystem Support Program • Ethereum.org • Security • Next Billion • Protocol Announcements keywords: ethereum; protocol; release; week; ðξv cache: blog-gavs-ethereum-dev-update-v.html plain text: blog-gavs-ethereum-dev-update-v.txt item: #77 of 3327 id: blog-getting-to-the-frontier author: blog title: blog-getting-to-the-frontier date: None words: 1218 flesch: 54 summary: Getting to the Frontier | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Getting to the Frontier Posted by Vinay Gupta on March 12, 2015 Research & Development We’ve already covered a little about what to expect from Frontier in the Ethereum Launch Process blog post and Gav has given us a comprehensive overview of the state of the development effort. keywords: development; frontier; process cache: blog-getting-to-the-frontier.html plain text: blog-getting-to-the-frontier.txt item: #78 of 3327 id: blog-how-to-build-your-own-cryptocurrency author: blog title: blog-how-to-build-your-own-cryptocurrency date: None words: 1440 flesch: 70 summary: Go to the contracts page and then click deploy new contract.   but I'd say the best place to start is the Ethereum Wallet, a multi platform app that will enable you to send ether and ethereum based currencies, create and execute contracts. keywords: contract; ethereum; token; wallet cache: blog-how-to-build-your-own-cryptocurrency.html plain text: blog-how-to-build-your-own-cryptocurrency.txt item: #79 of 3327 id: blog-how-to-make-a-purchase-in-the-ether-presale author: blog title: blog-how-to-make-a-purchase-in-the-ether-presale date: None words: 950 flesch: 53 summary: SEED = decrypt(KEY, ENCSEED) Overview of website steps for making an ether purchase: Buyer clicks “Buy Ether” and agrees to the Terms & Conditions Buyer enters initial purchase information Buyer enters the amount of ether they’d like to purchase Buyer enters email address as the destination for wallet backup file Buyer enters passphrase, which serves as an encryption seed. WALLET = [ ENCSEED, BKPKEY ] (plus non-sensitive data like ethereum and bitcoin address) keywords: address; ether; sale cache: blog-how-to-make-a-purchase-in-the-ether-presale.html plain text: blog-how-to-make-a-purchase-in-the-ether-presale.txt item: #80 of 3327 id: blog-implementing-vitaliks-vision author: blog title: blog-implementing-vitaliks-vision date: None words: 1246 flesch: 51 summary: The main interfaces will consist primarily of the command-line client, interactive JavaScript console, and JSON-RPC. For the Frontier rollout, we are aiming to release stable binaries on major operating systems (Mac, Windows, Linux). keywords: console; development; geth; program cache: blog-implementing-vitaliks-vision.html plain text: blog-implementing-vitaliks-vision.txt item: #81 of 3327 id: blog-important-statement-regarding-the-ether-pre-sale author: blog title: blog-important-statement-regarding-the-ether-pre-sale date: None words: 336 flesch: 33 summary: Previous post Next post Subscribe to Protocol Announcements Sign up to receive email notifications for protocol-related announcements, such as network upgrades, FAQs or security issues. Sign up Ethereum Foundation • Ethereum.org • ESP • Bug Bounty Program • Do-not-Track • Archive Categories Research & Development • Events • Organizational • Ecosystem Support Program • Ethereum.org • Security • Next Billion • Protocol Announcements keywords: ether cache: blog-important-statement-regarding-the-ether-pre-sale.html plain text: blog-important-statement-regarding-the-ether-pre-sale.txt item: #82 of 3327 id: blog-index author: blog title: blog-index date: None words: 6877 flesch: 64 summary: In the context of file storage, there are two kinds of activities that you can incentivize. [-7.0, 12.0, -4.5, 0.5] Now, as I mentioned, this mathematical trickery is not really all that needed for file storage; the simpler approach of storing hashes and discarding any piece that does not match the recorded hash works just fine. keywords: chunks; file; polynomial; proof; protocol; redundancy cache: blog-index.html plain text: blog-index.txt item: #83 of 3327 id: blog-information-theoretic-account-secure-brainwallets author: blog title: blog-information-theoretic-account-secure-brainwallets date: None words: 4082 flesch: 58 summary: It has become rather popular among security experts to dismiss passwords as being fundamentally insecure, and argue for password schemes to be replaced outright. Strength Now, let us get to the next point, password security against attackers. keywords: bits; entropy; number; password; time; use cache: blog-information-theoretic-account-secure-brainwallets.html plain text: blog-information-theoretic-account-secure-brainwallets.txt item: #84 of 3327 id: blog-inside-ethereum-devhub-berlin author: blog title: blog-inside-ethereum-devhub-berlin date: None words: 179 flesch: 28 summary: From inside Ethereum ÐΞVhub Berlin | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search From inside Ethereum ÐΞVhub Berlin Posted by Gavin Wood on December 2, 2014 Research & Development Yesterday was the first proper day of ÐΞVhub Berlin being open, following the first Ethereum internal developers' symposium ÐΞVcon-0. Henning, Marek, Viktor and Felix hacking on the couch Aeron and Brian in discussion Alex and Jutta conferencing over network and security The rest of the team hacking in the lab Previous post Next post Subscribe to Protocol Announcements Sign up to receive email notifications for protocol-related announcements, such as network upgrades, FAQs or security issues. keywords: protocol cache: blog-inside-ethereum-devhub-berlin.html plain text: blog-inside-ethereum-devhub-berlin.txt item: #85 of 3327 id: blog-introducing-casper-friendly-ghost author: blog title: blog-introducing-casper-friendly-ghost date: None words: 2538 flesch: 49 summary: Therefore through iterated rounds of betting validator bets converge. There is something at stake, and bonded validators who misbehave in an objectively verifiable manner will lose it. keywords: blocks; casper; consensus; validators cache: blog-introducing-casper-friendly-ghost.html plain text: blog-introducing-casper-friendly-ghost.txt item: #86 of 3327 id: blog-introducing-ethereum-script-2-0 author: blog title: blog-introducing-ethereum-script-2-0 date: None words: 3742 flesch: 69 summary: The immutability of code also makes it easier to construct a restricted subset of the scripting language which is functional, and then such functional code could be deduplicated and optimized at will. As an important clarification, this rework will have little effect on the Ethereum CLL, the stripped-down-Python-like language in which you can write Namecoin in five lines of code. keywords: code; contract; push; stack; txdata cache: blog-introducing-ethereum-script-2-0.html plain text: blog-introducing-ethereum-script-2-0.txt item: #87 of 3327 id: blog-introduction-futarchy author: blog title: blog-introduction-futarchy date: None words: 4956 flesch: 48 summary: Under this system, individuals would vote not on whether or not to implement particular policies, but rather on a metric to determine how well their country (or charity or company) is doing, and then prediction markets would be used to pick the policies that best optimize the metric. Prediction markets do not have this property at all. keywords: ceo; company; futarchy; market; price; protocol; token; value cache: blog-introduction-futarchy.html plain text: blog-introduction-futarchy.txt item: #88 of 3327 id: blog-jeffs-ethereum-dev-update author: blog title: blog-jeffs-ethereum-dev-update date: None words: 1033 flesch: 65 summary: My name is Jeff, a founder of Ethereum and one of the three directors (alongside Vitalik and Gavin) of Ethereum ÐΞV, the development entity building Ethereum and all the associated tech. Sign up Ethereum Foundation • Ethereum.org • ESP • Bug Bounty Program • Do-not-Track • Archive Categories Research & Development • Events • Organizational • Ecosystem Support Program • Ethereum.org • Security • Next Billion • Protocol Announcements keywords: development; ethereum; protocol; team cache: blog-jeffs-ethereum-dev-update.html plain text: blog-jeffs-ethereum-dev-update.txt item: #89 of 3327 id: blog-jeffs-ethereum-dev-update-2 author: blog title: blog-jeffs-ethereum-dev-update-2 date: None words: 704 flesch: 65 summary: But until then, happy whispering and mining! Previous post Next post Subscribe to Protocol Announcements Sign up to receive email notifications for protocol-related announcements, such as network upgrades, FAQs or security issues. We're already hard at work to finalising PoC-8 which includes numerous small changes: Adjusted block time back to 12s (was 4s) Op code PREVHASH has become BLOCKHASH( N ) and therefore PREVHASH = BLOCKHASH(NUMBER - 1) We've added an additional pre-compiled contract at address 0x04 which returns the given input (acts like copy / memcpy) Ongoing P2P Felix has been hard at work on our new P2P package which has now entered in to v0.1 (PoC-7) and will soon already undergo it's first upgrade for PoC-8. keywords: ethereum; protocol cache: blog-jeffs-ethereum-dev-update-2.html plain text: blog-jeffs-ethereum-dev-update-2.txt item: #90 of 3327 id: blog-juttas-update-bug-bounty-program-security-audit author: blog title: blog-juttas-update-bug-bounty-program-security-audit date: None words: 417 flesch: 54 summary: Jutta’s update on bug bounty program and security audit | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Jutta’s update on bug bounty program and security audit Posted by Jutta Steiner on March 20, 2015 Research & Development Hi, Jutta writing again – I initially introduced myself when we started the bounty program earlier this year and I’m happy to provide you with an update on what’s happening on the security side prior and throughout launch. Previous post Next post Subscribe to Protocol Announcements Sign up to receive email notifications for protocol-related announcements, such as network upgrades, FAQs or security issues. keywords: program; security cache: blog-juttas-update-bug-bounty-program-security-audit.html plain text: blog-juttas-update-bug-bounty-program-security-audit.txt item: #91 of 3327 id: blog-know-ethereum-secure author: blog title: blog-know-ethereum-secure date: None words: 1076 flesch: 53 summary: As Gav reported in his last blog post, because of the significant changes in the networking and syncing strategy we eventually decided to commission further audit work for Go – which we are about to finish this week. As spring has passed and summer arrived and meanwhile several audits finished, it’s now a good time for me to share some results from the inspection of the world computer’s machine room. keywords: audit; end; security cache: blog-know-ethereum-secure.html plain text: blog-know-ethereum-secure.txt item: #92 of 3327 id: blog-launching-the-ether-sale author: blog title: blog-launching-the-ether-sale date: None words: 1430 flesch: 56 summary: We reserve the right to use up to 5000 BTC from the pre-sale while the pre-sale is running in order to speed up development. There are two endowment pools, each 0.099x the initial quantity of ether sold, that will be allocated in the first case to early contributors to the project and in the second case to a long-term endowment to our non-profit foundation (see sale docs for more info). keywords: ether; ethereum; protocol; sale cache: blog-launching-the-ether-sale.html plain text: blog-launching-the-ether-sale.txt item: #93 of 3327 id: blog-light-clients-proof-stake author: blog title: blog-light-clients-proof-stake date: None words: 3078 flesch: 58 summary: Whereas proof of work algorithms involve the production of block headers which can be quickly verified, allowing a relatively small chain of headers to act as an implicit proof that the network considers a particular history to be valid, proof of stake is harder to fit into such a model. The cost of spoofing this mechanism, providing a chain of block headers that is probably-valid-but-not-actually-valid, is very high; in fact, it is almost exactly the same as the cost of launching a 51% attack on the network. keywords: block; client; light; proof cache: blog-light-clients-proof-stake.html plain text: blog-light-clients-proof-stake.txt item: #94 of 3327 id: blog-long-range-attacks-the-serious-problem-with-adaptive-proof-of-work author: blog title: blog-long-range-attacks-the-serious-problem-with-adaptive-proof-of-work date: None words: 1301 flesch: 55 summary: The solution is also elegant because it is simultaneously an economic one: if someone does create an ASIC, then others will have the incentive to look for types of computation that the ASIC can’t do and “pollute” the blockchain with such contracts. Hence, the long-range-attacker could fill the blockchain with such contracts, “mine” them, and convince the network that it is doing a massive amount of work when it is actually just taking the shortcut. keywords: blockchain; proof; range cache: blog-long-range-attacks-the-serious-problem-with-adaptive-proof-of-work.html plain text: blog-long-range-attacks-the-serious-problem-with-adaptive-proof-of-work.txt item: #95 of 3327 id: blog-merkling-in-ethereum author: blog title: blog-merkling-in-ethereum date: None words: 1843 flesch: 57 summary: For transaction trees, they are also good because it does not matter how much time it takes to edit a tree once it's created, as the tree is created once and then forever frozen solid. Although it is definitely theoretically possible to make a blockchain without Merkle trees, simply by creating giant block headers that directly contain every transaction, doing so poses large scalability challenges that arguably puts the ability to trustlessly use blockchains out of the reach of all but the most powerful computers in the long term. keywords: merkle; root; transaction; tree cache: blog-merkling-in-ethereum.html plain text: blog-merkling-in-ethereum.txt item: #96 of 3327 id: blog-microsoft-to-sponsor-ethereums-devcon1-2 author: blog title: blog-microsoft-to-sponsor-ethereums-devcon1-2 date: None words: 305 flesch: 33 summary: Microsoft to Sponsor Ethereum’s DEVCON1 | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Microsoft to Sponsor Ethereum’s DEVCON1 Posted by George Hallam on October 28, 2015 Events London, United Kingdom, October 28th - Ethereum is happy to announce that Microsoft will sponsor and attend DΞVCON1, the premier Ethereum developer conference. We see a future where the combination of Microsoft Azure and Ethereum can enable new innovative platforms like Blockchain-as-a-Service. keywords: ethereum; microsoft cache: blog-microsoft-to-sponsor-ethereums-devcon1-2.html plain text: blog-microsoft-to-sponsor-ethereums-devcon1-2.txt item: #97 of 3327 id: blog-mining author: blog title: blog-mining date: None words: 6384 flesch: 58 summary: However, mining pools also serve another purpose. Instead, they ask mining pools to generate mining data for them. keywords: asic; bitcoin; block; electricity; ghash; hashpower; miners; mining; network; pool cache: blog-mining.html plain text: blog-mining.txt item: #98 of 3327 id: blog-more-thoughts-on-scripting-and-future-compatibility author: blog title: blog-more-thoughts-on-scripting-and-future-compatibility date: None words: 1920 flesch: 56 summary: However, his solution, manual protocol updates, is arguably no better; protocol updates that change fee structures can expose new economic vulnerabilities in contracts as well, and they are arguably even harder to compensate for because there are absolutely no restrictions on what content manual protocol updates can contain. We are starting to brush against this limit already, with about 250 KB in each block, and it’s putting pressure on transaction fees already. keywords: bitcoin; fee; opcodes; protocol; sha256 cache: blog-more-thoughts-on-scripting-and-future-compatibility.html plain text: blog-more-thoughts-on-scripting-and-future-compatibility.txt item: #99 of 3327 id: blog-more-uncle-statistics author: blog title: blog-more-uncle-statistics date: None words: 1652 flesch: 51 summary: First of all, uncle rates are quite low compared to Olympic; altogether we have seen 20750 uncles with 280000 blocks, or an uncle rate of 7.41% (if you compute this inclusively, ie. uncles as a percentage of all blocks rather than uncles per block, you get 6.89%) - in short, not that much higher than similar figures for bitcoin even back in 2011, when its mining ecosystem was more similar to Ethereum's with CPU and GPUs still being dominant and with a low transaction volume. Time period differences: pools and other very large miners were not active on the first day of the blockchain, when block times were very fast and uncle rates were very high. keywords: blocks; miners; uncle cache: blog-more-uncle-statistics.html plain text: blog-more-uncle-statistics.txt item: #100 of 3327 id: blog-nick-szabo-confirmed-as-keynote-speaker-of-ethereums-devcon1 author: blog title: blog-nick-szabo-confirmed-as-keynote-speaker-of-ethereums-devcon1 date: None words: 391 flesch: 37 summary: Recently, Szabo contrasted the use of smart contracts on Ethereum in relation to the Bitcoin blockchain, “If you want to have a flexible general purpose programming environment like programmers have been used to since the 1950s at least, then you’re going to want to use Ethereum because it’s got a Turing complete language and a large state. Ethereum is a decentralized blockchain protocol that executes smart contracts: applications that run exactly as programmed without any possibility of downtime, censorship, fraud or third party interference. keywords: ethereum; nick cache: blog-nick-szabo-confirmed-as-keynote-speaker-of-ethereums-devcon1.html plain text: blog-nick-szabo-confirmed-as-keynote-speaker-of-ethereums-devcon1.txt item: #101 of 3327 id: blog-olympic-frontier-pre-release author: blog title: blog-olympic-frontier-pre-release date: None words: 1171 flesch: 45 summary: Smaller prizes for forks between Go/C++ and Python may also be available. There will be four categories of prize as well as a grand prize for the first person to create a substantial fork on the testnet. keywords: account; number; transaction cache: blog-olympic-frontier-pre-release.html plain text: blog-olympic-frontier-pre-release.txt item: #102 of 3327 id: blog-olympic-rewards-announced author: blog title: blog-olympic-rewards-announced date: None words: 499 flesch: 50 summary: 753f49fb35f0f6f8a7bff0413e376af88f7ff684 (57744 blocks) - 2500 ETH 891f82ee3e031c5dd85e63b23521b4b9f10c67ff (39526 blocks) - 1250 ETH 24365bc872e4166081611bb0b5483526742c6616 (39358 blocks) - 625 ETH 8ef297b17b65ded8142dbdb106818cd09899a8f5 (34142 blocks) - 375 ETH 027b1495165fec8cfc49bdb8450ded4cbce4b12e (33305 blocks) - 250 ETH Top senders for blocks 300000-1000000 b4e64290541cbf36159e727dfd8d873f77b42149 (5429042 txs) - 2500 ETH 00fc572550f3bdfe84f72e3eaa99d02a43f69733 (1912815 txs) - 1250 ETH 8464ba8c33260c70c9ab03487bee8a0dda35d383 (947176 txs) - 625 ETH 082d4cdf07f386ffa9258f52a5c49db4ac321ec6 (837307 txs) - 375 ETH 970f4f9eb29e8831514a3ff9b8eb2bb860d4731c (831275 txs) - 250 ETH Lowest address at block 848081 Only addresses with nonzero nonce (ie. that sent at least one transaction) were included. Most storage keys at block 848081: 332b656504f4eabb44c8617a42af37461a34e9dc (1727960 slots) - 2500 ETH f558470e1ed9e33f2ebf994938722d7f287221f2 (685670 slots) - 1250 ETH 728d902f5b805a3f49707f36957d876dd6d40e53 (657813 slots) - 625 ETH 2ea6a457c468ed38b222a2c504a674905b5fcb7e (607504 slots) - 375 ETH b56e8f043e529bca0344a96cbec8b00bc85c7ca6 (135250 slots) - 250 ETH Contract with highest nonce at block 848081: e35e196a53cabeb4eb4cdd66467427a798d8c24f (4823) - 750 ETH 3673cb526c8505002e7ba558140b0c4d60009ac9 (2907) - 500 ETH 66314103c204504486b6ce587109853f4e99e29b (385) - 250 ETH Manually issued rewards for all-around good behavior: PhiStr90 - 3500 keywords: block; eth cache: blog-olympic-rewards-announced.html plain text: blog-olympic-rewards-announced.txt item: #103 of 3327 id: blog-on-abstraction author: blog title: blog-on-abstraction date: None words: 4193 flesch: 57 summary: Currency Currently, contracts have the ability to charge for services, using code like this registry example: def reserve(_name:bytes32): if msg.value > 100 * 10**18: if not self.domains[_name].owner: self.domains[_name].owner = msg.sender With a sub-currency, there is no such clear mechanism of tying together a message and a payment for that message. keywords: code; currency; ethereum; gas; transaction; trie; value cache: blog-on-abstraction.html plain text: blog-on-abstraction.txt item: #104 of 3327 id: blog-on-anti-pre-revelation-games author: blog title: blog-on-anti-pre-revelation-games date: None words: 2232 flesch: 48 summary: Note that such events are a complicated issue in any case; failure modes such as everyone centralizing on one particular exchange are very likely to arise even in simple Sztorcian schemes without this kind of probabilistic griefing. Perhaps the largest one is that it opens up an opportunity to second-order grief other players: although one cannot, in expectation, force other players to lose money to this scheme, one can certainly expose them to risk by betting against them. keywords: scheme; users; vote cache: blog-on-anti-pre-revelation-games.html plain text: blog-on-anti-pre-revelation-games.txt item: #105 of 3327 id: blog-on-long-term-cryptocurrency-distribution-models author: blog title: blog-on-long-term-cryptocurrency-distribution-models date: None words: 3341 flesch: 52 summary: One can have a parliament, or a futarchy, select useful proof of work algorithms or even data for specific useful proof of work algorithms, or one can have a parliament or futarchy with useful proof of work as its voting mechanism. Useful proof-of-work: hand out coins to anyone who performs a particular socially useful computation, eg. weather prediction. keywords: algorithm; data; distribution; mining; proof; work cache: blog-on-long-term-cryptocurrency-distribution-models.html plain text: blog-on-long-term-cryptocurrency-distribution-models.txt item: #106 of 3327 id: blog-on-public-and-private-blockchains author: blog title: blog-on-public-and-private-blockchains date: None words: 1888 flesch: 39 summary: The advantages of public blockchains generally fall into two major categories: Public blockchains provide a way to protect the users of an application from the developers, establishing that there are certain things that even the developers of an application have no authority to do. Improvements in public blockchain technology, such as Ethereum 1.0's uncle concept and later proof of stake, can bring public blockchains much closer to the instant confirmation ideal (eg. offering total finality after 15 seconds, rather than 99.9999% finality after two hours as does Bitcoin), but even still private blockchains will always be faster and the latency difference will never disappear as unfortunately the speed of light does not increase by 2x every two years by Moore's law. keywords: blockchains; consortium; program; proof; public cache: blog-on-public-and-private-blockchains.html plain text: blog-on-public-and-private-blockchains.txt item: #107 of 3327 id: blog-on-slow-and-fast-block-times author: blog title: blog-on-slow-and-fast-block-times date: None words: 2789 flesch: 47 summary: Note: this article will not go into depth on the centralization risks associated with fast block times; centralization risks are a major concern, and are the primary reason not to push block times all the way down to 1 second despite the benefits, and are discussed at much more length in this previous article; the purpose of this article is to explain why fast block times are desirable at all. : Script here Note that for fast block times, we do have to make an adjustment because the stale rates are higher, and we do this in the above graph: we set X = 0.25 for the 600s blockchain and X = 0.28 for the 17s blockchain. keywords: block; blockchain; probability; security cache: blog-on-slow-and-fast-block-times.html plain text: blog-on-slow-and-fast-block-times.txt item: #108 of 3327 id: blog-on-transaction-fees-and-the-fallacy-of-market-based-solutions author: blog title: blog-on-transaction-fees-and-the-fallacy-of-market-based-solutions date: None words: 2314 flesch: 57 summary: The resource is the service of transaction processing, and the people benefitting from the resource, the transaction senders, are also the buyers paying transaction fees. The reason why transaction fees need to be high is because that 0.00001worthofelectricityanddatastorage. keywords: fees; miners; protocol; set; transaction cache: blog-on-transaction-fees-and-the-fallacy-of-market-based-solutions.html plain text: blog-on-transaction-fees-and-the-fallacy-of-market-based-solutions.txt item: #109 of 3327 id: blog-p-epsilon-attack author: blog title: blog-p-epsilon-attack date: None words: 1941 flesch: 47 summary: Further Consequences Given the sheer number of cryptoeconomic mechanisms that SchellingCoin makes possible, and the importance of such schemes in nearly all purely trust-free attempts to forge any kind of link between the cryptographic world and the real world, this attack poses a potential serious threat - although, as we will later see, Schelling schemes as a category are ultimately partially salvageable. Hence, in order to overcome such a mechanism, one would need to be able to prove that one is capable of pulling off a 51% attack, and perhaps we may simply be comfortable with assuming that attackers of that size do not exist. keywords: attacker; proof; vote cache: blog-p-epsilon-attack.html plain text: blog-p-epsilon-attack.txt item: #110 of 3327 id: blog-programming-society-with-asm-gavin-wood-at-assembly-2014 author: blog title: blog-programming-society-with-asm-gavin-wood-at-assembly-2014 date: None words: 123 flesch: 14 summary: Programming Society with Asm: Gavin Wood at Assembly 2014 | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Programming Society with Asm: Gavin Wood at Assembly 2014 Posted by Stephan Tual on August 6, 2014 Research & Development Previous post Next post Subscribe to Protocol Announcements Sign up to receive email notifications for protocol-related announcements, such as network upgrades, FAQs or security issues. Sign up Ethereum Foundation • Ethereum.org • ESP • Bug Bounty Program • Do-not-Track • Archive Categories Research & Development • Events • Organizational • Ecosystem Support Program • Ethereum.org • Security • Next Billion • Protocol Announcements keywords: protocol cache: blog-programming-society-with-asm-gavin-wood-at-assembly-2014.html plain text: blog-programming-society-with-asm-gavin-wood-at-assembly-2014.txt item: #111 of 3327 id: blog-proof-stake-learned-love-weak-subjectivity author: blog title: blog-proof-stake-learned-love-weak-subjectivity date: None words: 3691 flesch: 51 summary: Although the idea has many undeniable benefits, including efficiency, a larger security margin and future-proof immunity to hardware centralization concerns, proof of stake algorithms tend to be substantially more complex than proof of work-based alternatives, and there is a large amount of skepticism that proof of stake can work at all, particularly with regard to the supposedly fundamental nothing at stake problem. Altogether, we now know for certain that (i) proof of stake algorithms can be made secure, and weak subjectivity is both sufficient and necessary as a fundamental change in the security model to sidestep nothing-at-stake concerns to accomplish this goal, and (ii) there are substantial economic reasons to believe that proof of stake actually is much more economically efficient than proof of work. keywords: consensus; network; proof; security; set; stake; work cache: blog-proof-stake-learned-love-weak-subjectivity.html plain text: blog-proof-stake-learned-love-weak-subjectivity.txt item: #112 of 3327 id: blog-pyethereum-and-serpent-programming-guide author: blog title: blog-pyethereum-and-serpent-programming-guide date: None words: 3893 flesch: 55 summary: Contract code theoretically has three places to put data: stack, memory and storage. The contract works as follows: Party A sends in X ether alongside a data feed contract D and a currency code C as data items, and is registered at contract storage index 1000. keywords: code; contract; data; ether; serpent; storage; value cache: blog-pyethereum-and-serpent-programming-guide.html plain text: blog-pyethereum-and-serpent-programming-guide.txt item: #113 of 3327 id: blog-scalability-part-1-building-top author: blog title: blog-scalability-part-1-building-top date: None words: 3049 flesch: 54 summary: Generally, the main source of randomness used in Ethereum is block hashes; because micropayments are low-value applications, and because the different nonce on each transaction ensures that a block hash is extremely unlikely to favor any particular user in any particular way, block hashes will likely be sufficient for this purpose - however, we need to make sure we grab a specific block hash rather than simply the block hash when a request is sent (using the block hash when a request is sent also works, but less well, since the sender and receiver have an incentive to try to disrupt each other's attempts to send claim transactions during blocks that are unfavorable to them). When the channel process is done, and the recipient wants to cash out, he must simply take the signed [id, value, v, r, s] packet (the v,r,s triple being an elliptic curve signature) and push it to the blockchain as transaction data, and the contract verifies the signature. keywords: block; ethereum; transaction; value cache: blog-scalability-part-1-building-top.html plain text: blog-scalability-part-1-building-top.txt item: #114 of 3327 id: blog-scalability-part-2-hypercubes author: blog title: blog-scalability-part-2-hypercubes date: None words: 5633 flesch: 55 summary: One option is to keep track of the number of transactions per substate, and once the number of transactions per substate exceeds the number of substates we can simply add a dimension to the cube (ie. double the number of substates). The miners on other substates don't know that the attacker's blocks are invalid, because they have no knowledge of the state of the captured substate, so at first glance it seems as though they might blindly accept them. keywords: block; chain; challenge; header; messages; miners; protocol; substate cache: blog-scalability-part-2-hypercubes.html plain text: blog-scalability-part-2-hypercubes.txt item: #115 of 3327 id: blog-scalability-part-3-metacoin-history-multichain author: blog title: blog-scalability-part-3-metacoin-history-multichain date: None words: 3779 flesch: 50 summary: Different chains can use different currencies, using stable-coins to provide a reasonably consistent cross-chain unit of value (and, of course, these stable-coins can themselves interact with other chains that implement various kinds of endogenous and exogenous estimators). Each chain would outsource the key part of consensus to one or more voting mechanisms on other chains, and these mechanisms would be organized in different ways to make sure they're as incorruptible as possible. keywords: bitcoin; block; blockchain; chain; ethereum; security; vote cache: blog-scalability-part-3-metacoin-history-multichain.html plain text: blog-scalability-part-3-metacoin-history-multichain.txt item: #116 of 3327 id: blog-schellingcoin-a-minimal-trust-universal-data-feed author: blog title: blog-schellingcoin-a-minimal-trust-universal-data-feed date: None words: 2863 flesch: 55 summary: Thanks to the magic of Ethereum contracts, she can make a CFD that automatically listens to her account balance and retargets itself to her balance, forcing the speculator to assume whatever exposure she needs (within limits), and the speculator will participate in many such contracts to even out their exposure Sort the correctly submitted values (if many values are the same, have a secondary sort by H(N+PREVHASH+ADDR) wherePREVHASH is the hash of the last block) Every user who submitted a correctly submitted value between the 25th and 75th percentile gains a reward of N tokens (which we’ll call “schells”) keywords: btc; eth; protocol; schellingcoin; value cache: blog-schellingcoin-a-minimal-trust-universal-data-feed.html plain text: blog-schellingcoin-a-minimal-trust-universal-data-feed.txt item: #117 of 3327 id: blog-search-stable-cryptocurrency author: blog title: blog-search-stable-cryptocurrency date: None words: 5011 flesch: 49 summary: Of course, this is only the beginning of endogenous price estimator theory; a more thorough analysis involving dozens of cryptocurrencies will likely go much further. Can we have the full decentralization that a cryptographic payment network offers, but at the same time have a higher level of price stability, without such extreme upward and downward swings? Last week, a team of Japanese researchers made a proposal for an improved Bitcoin, which was an attempt to do just that: whereas Bitcoin has a fixed supply, and a volatile price, the researchers' Improved Bitcoin would vary its supply in an attempt to mitigate the shocks in price. keywords: coins; currency; estimator; price; supply; system; value; vol cache: blog-search-stable-cryptocurrency.html plain text: blog-search-stable-cryptocurrency.txt item: #118 of 3327 id: blog-secret-sharing-daos-crypto-2-0 author: blog title: blog-secret-sharing-daos-crypto-2-0 date: None words: 6115 flesch: 55 summary: Further Consequences Aside from the applications above, what else will secret sharing DAOs bring? Fortunately for these attackers, however, secret sharing DAOs do have an inevitable backdoor: the 51% attack. keywords: dao; point; protocol; secret; sharing; stack[stack_size; use cache: blog-secret-sharing-daos-crypto-2-0.html plain text: blog-secret-sharing-daos-crypto-2-0.txt item: #119 of 3327 id: blog-secret-sharing-erasure-coding-guide-aspiring-dropbox-decentralizer author: blog title: blog-secret-sharing-erasure-coding-guide-aspiring-dropbox-decentralizer date: None words: 6877 flesch: 64 summary: In the context of file storage, there are two kinds of activities that you can incentivize. [-7.0, 12.0, -4.5, 0.5] Now, as I mentioned, this mathematical trickery is not really all that needed for file storage; the simpler approach of storing hashes and discarding any piece that does not match the recorded hash works just fine. keywords: chunks; file; polynomial; proof; protocol; redundancy cache: blog-secret-sharing-erasure-coding-guide-aspiring-dropbox-decentralizer.html plain text: blog-secret-sharing-erasure-coding-guide-aspiring-dropbox-decentralizer.txt item: #120 of 3327 id: blog-security-advisory-eth-cpp-ethereum-potentially-vulnerable-if-running-with-upnp-enabled author: blog title: blog-security-advisory-eth-cpp-ethereum-potentially-vulnerable-if-running-with-upnp-enabled date: None words: 219 flesch: 30 summary: MediumSeverity: HighImpact: Potentially achieve remote code execution on a machine running eth (cpp-ethereum)Details:A vulnerability found in the MiniUPnP library can potentially affect eth clients running with UPnP enabled. Security Advisory [eth (cpp-ethereum) potentially vulnerable if running with UPnP enabled] | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Security Advisory [eth (cpp-ethereum) potentially vulnerable if running with UPnP enabled] Posted by Gustav Simonsson on October 10, 2015 Security Affected configurations: Issue reported for eth (cpp-ethereum).Likelihood: keywords: ethereum cache: blog-security-advisory-eth-cpp-ethereum-potentially-vulnerable-if-running-with-upnp-enabled.html plain text: blog-security-advisory-eth-cpp-ethereum-potentially-vulnerable-if-running-with-upnp-enabled.txt item: #121 of 3327 id: blog-security-advisory-implementations-bugs-in-go-and-python-clients-can-cause-dos author: blog title: blog-security-advisory-implementations-bugs-in-go-and-python-clients-can-cause-dos date: None words: 414 flesch: 46 summary: Fix:Upgrade geth and pyethereum client software. | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Security Advisory [Implementation bugs in Go and Python clients can cause DoS – Fixed – Please update clients] Posted by Jutta Steiner on September 2, 2015 Security State transition and consensus issue in geth client causes panic (crash) when processing a (valid) block with a specific combination of transactions, which may cause overall network instability if block is accepted and relayed by unaffected clients thus causing a DoS. This may happen in a block that contains transactions which suicide to the block reward address. keywords: clients; security cache: blog-security-advisory-implementations-bugs-in-go-and-python-clients-can-cause-dos.html plain text: blog-security-advisory-implementations-bugs-in-go-and-python-clients-can-cause-dos.txt item: #122 of 3327 id: blog-security-alert-1-windowsalethzero-2 author: blog title: blog-security-alert-1-windowsalethzero-2 date: None words: 351 flesch: 49 summary: Workaround: Users of AlethZero version 0.9.39 and earlier should NOT use the “Claim Presale Wallet” function; users of AlethZero and eth versions 0.9.39 and earlier should not attempt to mine or receive funds into their addresses. Previous post Next post Subscribe to Protocol Announcements Sign up to receive email notifications for protocol-related announcements, such as network upgrades, FAQs or security issues. keywords: security; users cache: blog-security-alert-1-windowsalethzero-2.html plain text: blog-security-alert-1-windowsalethzero-2.txt item: #123 of 3327 id: blog-security-alert-consensus-issue author: blog title: blog-security-alert-consensus-issue date: None words: 539 flesch: 54 summary: Security alert [consensus issue] | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Security alert [consensus issue] Posted by Jutta Steiner on August 20, 2015 Security This alert is related to a consensus issue that occurred on the Frontier network at block 116,522, mined on 2015-08-20 at 14:59:16+02:00 – Issue has been fixed, see Fix below. Impact: High Issue description: State database consensus issue in geth with deletion of account data, which could happen during SUICIDE instructions. keywords: fix; issue cache: blog-security-alert-consensus-issue.html plain text: blog-security-alert-consensus-issue.txt item: #124 of 3327 id: blog-security-alert-implementation-bug-in-go-clients-causing-increase-in-difficulty-fixed-miners-check-and-update-go-clients-if-necessary author: blog title: blog-security-alert-implementation-bug-in-go-clients-causing-increase-in-difficulty-fixed-miners-check-and-update-go-clients-if-necessary date: None words: 345 flesch: 34 summary: Security Alert – [Implementation bug in Go clients causing increase in difficulty – Fixed – Miners check and update Go clients] | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Security Alert – [Implementation bug in Go clients causing increase in difficulty – Fixed – Miners check and update Go clients] Posted by Jutta Steiner on September 3, 2015 Security Implementation bug in the go client leads to steady increase of difficulty independent of hashing power. Likelihood: High Severity: Medium Impact: Increase in block time will lead to an exponential increase in difficulty Details: A bug in the go client leads to steady increase in difficulty in the following block, as timestamp in new block = timestamp + 1 of old block, regardless of the actual time, when mining. keywords: bug; increase cache: blog-security-alert-implementation-bug-in-go-clients-causing-increase-in-difficulty-fixed-miners-check-and-update-go-clients-if-necessary.html plain text: blog-security-alert-implementation-bug-in-go-clients-causing-increase-in-difficulty-fixed-miners-check-and-update-go-clients-if-necessary.txt item: #125 of 3327 id: blog-security-alert-implementation-of-blockhash-instruction-in-c-and-go-clients-can-potentially-cause-consensus-issue-fixed-please-update author: blog title: blog-security-alert-implementation-of-blockhash-instruction-in-c-and-go-clients-can-potentially-cause-consensus-issue-fixed-please-update date: None words: 346 flesch: 36 summary: This edge case is very unlikely to happen on a live network as it would only be triggered in certain types of chain reorganisations (a contract executing BLOCKHASH(N - 1) where N is the head of a non-canonical subchain that is not-yet reorganised to become the canonical (best/longest) chain but will be after the block is processed). Effects on expected chain reorganisation depth: none Remedial action taken by Ethereum: keywords: protocol; security cache: blog-security-alert-implementation-of-blockhash-instruction-in-c-and-go-clients-can-potentially-cause-consensus-issue-fixed-please-update.html plain text: blog-security-alert-implementation-of-blockhash-instruction-in-c-and-go-clients-can-potentially-cause-consensus-issue-fixed-please-update.txt item: #126 of 3327 id: blog-security-alert-insecurely-configured-geth-can-make-funds-remotely-accessible author: blog title: blog-security-alert-insecurely-configured-geth-can-make-funds-remotely-accessible date: None words: 489 flesch: 43 summary: This is the default value to only allow connections originating on the local computer; remote RPC connections are disabled --unlock. By default, all accounts are locked Previous post Next post Subscribe to Protocol Announcements Sign up to receive email notifications for protocol-related announcements, such as network upgrades, FAQs or security issues. keywords: rpc; security cache: blog-security-alert-insecurely-configured-geth-can-make-funds-remotely-accessible.html plain text: blog-security-alert-insecurely-configured-geth-can-make-funds-remotely-accessible.txt item: #127 of 3327 id: blog-security-alert-previous-security-patch-can-lead-to-invalid-state-root-on-go-clients-with-a-specific-transaction-sequence-fixed-please-update author: blog title: blog-security-alert-previous-security-patch-can-lead-to-invalid-state-root-on-go-clients-with-a-specific-transaction-sequence-fixed-please-update date: None words: 322 flesch: 41 summary: Security Alert – [Previous security patch can lead to invalid state root on Go clients with a specific transaction sequence – Fixed. [Previous security patch can lead to invalid state root on Go clients with a specific transaction sequence – Fixed. keywords: protocol; security cache: blog-security-alert-previous-security-patch-can-lead-to-invalid-state-root-on-go-clients-with-a-specific-transaction-sequence-fixed-please-update.html plain text: blog-security-alert-previous-security-patch-can-lead-to-invalid-state-root-on-go-clients-with-a-specific-transaction-sequence-fixed-please-update.txt item: #128 of 3327 id: blog-serpent-upgrades-more-fun-stuff author: blog title: blog-serpent-upgrades-more-fun-stuff date: None words: 1382 flesch: 66 summary: This allows us to have contract initialization code, but still keep to the same format of [nonce, price, gas, to, value, data] for both transactions and contract creation, also making it easier to create new contracts via forwarding contracts Reordering transaction and contract data: the order is now [nonce, price, gas, to, value, data] in transactions and [gas, to, value, datain, datainsz, dataout, dataoutsz] in messages. Running serpent compile outer.se gives you a nice piece of compiled code that returns 3 if the msg.data[0] argument is equal to one. keywords: code; contract; serpent; stack cache: blog-serpent-upgrades-more-fun-stuff.html plain text: blog-serpent-upgrades-more-fun-stuff.txt item: #129 of 3327 id: blog-silos author: blog title: blog-silos date: None words: 2914 flesch: 44 summary: Cryptocurrency projects generally all build a blockchain, a currency and a client of their own, although forking a single client is common for the less innovative cases. Particularly, consider some of the following claims, all of which I believe in, but which are in many cases a substantial departure from the philosophies of many other people and projects: I do not think that weak subjectivity is all that much of a problem. keywords: bitcoin; blockchain; cryptocurrency; ecosystem; ethereum; people cache: blog-silos.html plain text: blog-silos.txt item: #130 of 3327 id: blog-slasher-a-punitive-proof-of-stake-algorithm author: blog title: blog-slasher-a-punitive-proof-of-stake-algorithm date: None words: 1666 flesch: 62 summary: In a 51% attack, an attacker A sends a transaction from A to B, waits for the transaction to be confirmed in block K1 (with parent K), collects a product from B, and then immediately creates another block K2 on top of K – with a transaction sending the same bitcoins but this time from A to A. At that point, there are two blockchains, one from block K1 and another from block K2. keywords: block; proof; stake; work cache: blog-slasher-a-punitive-proof-of-stake-algorithm.html plain text: blog-slasher-a-punitive-proof-of-stake-algorithm.txt item: #131 of 3327 id: blog-slasher-ghost-developments-proof-stake author: blog title: blog-slasher-ghost-developments-proof-stake date: None words: 5523 flesch: 50 summary: If a potential signer for block N + 3000 wants to become a designated signer for that block, they must send a special transaction accepting this responsibility and that transaction must get included between blocks N + 1 and N + 64. If a potential signer for block N + 3000 wants to become a signer, they must send a special transaction accepting this responsibility and supplying a deposit, and that transaction must get included between blocks N + 1 and N + 64. keywords: block; chain; proof; set; signers; stake cache: blog-slasher-ghost-developments-proof-stake.html plain text: blog-slasher-ghost-developments-proof-stake.txt item: #132 of 3327 id: blog-software-bounded-rationality author: blog title: blog-software-bounded-rationality date: None words: 5339 flesch: 51 summary: Thus, the BAR model assumes three types of actors: Altruistic - altruistic actors always follow the protocol Rational - rational actors follow the protocol if it suits them, and do not follow the protocol if it does not Byzantine - Byzantine actors are all conspiring to screw you over In practice, protocol developers tend to be uncomfortable assuming any specific nonzero quantity of altruism, so the model that many protocols are judged by is the even harsher BR model; protocols that survive under BR are said to be incentive-compatible (anything that survives under BR survives under BAR, since an altruist is guaranteed to be at least as good for the health of the protocol as anyone else as benefitting the protocol is their explicit objective). The reason why such an outcome has a large chance of not happening is simply the fact that users follow defaults, and by default users will use StorJ with StorJcoin since that is what the client will promote, and the original StorJ client and website and ecosystem is the one that will get all the attention. keywords: bitcoin; block; btc; case; model; protocol; software; system; users cache: blog-software-bounded-rationality.html plain text: blog-software-bounded-rationality.txt item: #133 of 3327 id: blog-stake author: blog title: blog-stake date: None words: 4945 flesch: 53 summary: In a naive proof of stake system, however, the only thing that each chain is aware of is itself; hence, one can intuitively see that this makes such systems more flimsy and less stable. In all of the proof of stake systems that I described above, the incentive is obvious, and unfortunately fundamental: because whoever is producing blocks needs an incentive to participate in the process, they benefit if they include a block in as many forks as possible. keywords: block; chain; cost; mining; proof; stake; transaction cache: blog-stake.html plain text: blog-stake.txt item: #134 of 3327 id: blog-state-ethereum-august-edition author: blog title: blog-state-ethereum-august-edition date: None words: 3227 flesch: 55 summary: The hash of a block is now the hash of the header, and not the entire block (which is how it really should have been all along), the code hash for accounts with no code is instead of sha3() (making all non-contract accounts 32 bytes more efficient), and the to address for contract creation transactions is now the empty string instead of twenty zero bytes. Suppose that there exists some operation or data structure that we want Ethereum contracts to have access to, but which we can optimize by writing an implementation in C++ or machine code. keywords: code; contract; ethereum; gas; heap; time cache: blog-state-ethereum-august-edition.html plain text: blog-state-ethereum-august-edition.txt item: #135 of 3327 id: blog-state-tree-pruning author: blog title: blog-state-tree-pruning date: None words: 1794 flesch: 51 summary: That said, light clients will also need to prune block headers if they are to survive in low-memory circumstances. In a fully decentralized context, this will likely be done through an advanced version of Bitcoin's headers-first-verification strategy, which will look roughly as follows: Download as many block headers as the client can get its hands on. keywords: block; state; tree cache: blog-state-tree-pruning.html plain text: blog-state-tree-pruning.txt item: #136 of 3327 id: blog-stateful-turing-complete-policies author: blog title: blog-stateful-turing-complete-policies date: None words: 2148 flesch: 45 summary: Rather than, at the protocol level, allowing users to specify a password, or providing a pre-selected set of providers, or even a standard which relies on talking to a server of the user's choice, allow access policies to be specified in code to be executed in a deterministic virtual machine (where the EVM is a good a start as any). This is the benefit of abstraction: account security policy design can become a self-contained field of study to itself, and whatever new solutions exist can instantly be applied everywhere. keywords: access; code; policies; policy; security cache: blog-stateful-turing-complete-policies.html plain text: blog-stateful-turing-complete-policies.txt item: #137 of 3327 id: blog-stephans-ethereum-community-adoption-update-week-1 author: blog title: blog-stephans-ethereum-community-adoption-update-week-1 date: None words: 1598 flesch: 54 summary: Ian is the creator of most of the video materials you might have seen relating to Ethereum, including the superb video loop that has been a staple at many Ethereum meetups. This has been the result of major, time consuming efforts to identify Ethereum projects in the wild, reaching out directly and building a strong relationship with our user base. keywords: adoption; community; efforts; ethereum; meetups cache: blog-stephans-ethereum-community-adoption-update-week-1.html plain text: blog-stephans-ethereum-community-adoption-update-week-1.txt item: #138 of 3327 id: blog-subjectivity-exploitability-tradeoff author: blog title: blog-subjectivity-exploitability-tradeoff date: None words: 4172 flesch: 51 summary: However, if P + epsilon attacks, profit-seeking 51% attacks, or any other kind of attack ever actually do become a problem with objective SchellingCoin mechanisms, the basic model stands ready as a substitute. Although one might think at first glance that objective systems, with no reliance on any actor using anything but information supplied through the protocol, are easy to analyze, this panoply of issues reveals that to a large extent the exact opposite is the case: objective protocols are vulnerable to takeovers, and potentially zero-cost takeovers, and standard economics and game theory quite simply have very bad tools for analyzing equilibrium flips. keywords: fork; mechanism; proof; protocol; schellingcoin; vote; work cache: blog-subjectivity-exploitability-tradeoff.html plain text: blog-subjectivity-exploitability-tradeoff.txt item: #139 of 3327 id: blog-superrationality-daos author: blog title: blog-superrationality-daos date: None words: 3393 flesch: 53 summary: However, Wikileaks exists, and yet shadowy centralized organizations also continue to still exist and are in many cases still quite shadowy. However, perhaps one of the main unfortunate byproducts of the modern birth of large centralized organizations is that they allow people to effectively cheat others' ability to read their minds, making this kind of cooperation more difficult. keywords: daos; gain; human; organizations; paperclips; people cache: blog-superrationality-daos.html plain text: blog-superrationality-daos.txt item: #140 of 3327 id: blog-the-business-imperative-behind-the-ethereum-vision author: blog title: blog-the-business-imperative-behind-the-ethereum-vision date: None words: 4714 flesch: 42 summary: So, if Ethereum development offers an advantage and you can exploit that, that's great. In its essence, Ethereum powers decentralized business logic, also known as smart contracts, represented as cryptographic boxes that contain value and only unlock it if certain conditions are met. keywords: applications; bitcoin; blockchain; business; developers; development; ethereum; logic; network; software; technology cache: blog-the-business-imperative-behind-the-ethereum-vision.html plain text: blog-the-business-imperative-behind-the-ethereum-vision.txt item: #141 of 3327 id: blog-the-end-of-the-beginning author: blog title: blog-the-end-of-the-beginning date: None words: 610 flesch: 54 summary: The end of the beginning… | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search The end of the beginning… Posted by Gavin Wood on May 2, 2015 Protocol Announcements As part of our tiered release process, we will soon be beginning the final phase prior to our Frontier release. Previous post Next post Subscribe to Protocol Announcements Sign up to receive email notifications for protocol-related announcements, such as network upgrades, FAQs or security issues. keywords: protocol; time cache: blog-the-end-of-the-beginning.html plain text: blog-the-end-of-the-beginning.txt item: #142 of 3327 id: blog-the-ethereum-project author: blog title: blog-the-ethereum-project date: None words: 1288 flesch: 60 summary: the ethereum project: learning to dream with open minds | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search the ethereum project: learning to dream with open minds Posted by Mihai Alisie on July 14, 2014 Research & Development “And those who were seen dancing were thought to be insane by those who could not hear the music.” We are learning to dream with open minds, just as we are dreaming with closed eyes. keywords: ethereum; project; technology cache: blog-the-ethereum-project.html plain text: blog-the-ethereum-project.txt item: #143 of 3327 id: blog-the-evolution-of-ethereum author: blog title: blog-the-evolution-of-ethereum date: None words: 2414 flesch: 28 summary: On the inside, we have Ethereum Foundation subsidiary developers building yet more block explorers and other tools in their spare time, and some developers are already working on implementing Ethereum-based lightning networks, identity and reputation systems, and more. Sign up Ethereum Foundation • Ethereum.org • ESP • Bug Bounty Program • Do-not-Track • Archive Categories Research & Development • Events • Organizational • Ecosystem Support Program • Ethereum.org • Security • Next Billion • Protocol Announcements keywords: blockchain; development; ecosystem; ethereum; foundation; subsidiaries; work cache: blog-the-evolution-of-ethereum.html plain text: blog-the-evolution-of-ethereum.txt item: #144 of 3327 id: blog-the-issuance-model-in-ethereum author: blog title: blog-the-issuance-model-in-ethereum date: None words: 1039 flesch: 59 summary: Often, but not always, monetary inflation is a cause of price inflation. Monetary base inflation rate (light green curve) on the right axis. keywords: eth; inflation; year cache: blog-the-issuance-model-in-ethereum.html plain text: blog-the-issuance-model-in-ethereum.txt item: #145 of 3327 id: blog-the-latest-evm-ethereum-is-a-trust-free-closure-system author: blog title: blog-the-latest-evm-ethereum-is-a-trust-free-closure-system date: None words: 2180 flesch: 57 summary: There is thus also a new RETURN opcode which allows contract execution to return data. Ether and Gas Another important change is this: contracts no longer pay for contract execution, transactions do. keywords: contract; ethereum; gas; transaction cache: blog-the-latest-evm-ethereum-is-a-trust-free-closure-system.html plain text: blog-the-latest-evm-ethereum-is-a-trust-free-closure-system.txt item: #146 of 3327 id: blog-the-problem-of-censorship author: blog title: blog-the-problem-of-censorship date: None words: 3161 flesch: 48 summary: However, transaction senders can make life much harder for censors still: they can create sets of transactions that create events that don't by themselves do anything, but do lead to the sender's desired consequence in combination with some other transaction that happens regularly (eg. Hence, transaction senders can be clever, and create a hundred transactions that create a hundred events, only all of which together create an event that accomplishes some particular action that is not desired by censors. keywords: block; blockchain; censorship; eth; price; transaction cache: blog-the-problem-of-censorship.html plain text: blog-the-problem-of-censorship.txt item: #147 of 3327 id: blog-the-question-of-mining author: blog title: blog-the-question-of-mining date: None words: 1334 flesch: 56 summary: Every new nonce that the miner tries, the miner would have to repeat this process over again, with a new set of random transactions and modifications each time. First, it is not entirely clear that the system of picking random transactions actually ends up requiring the miner to use the entire blockchain. keywords: ethereum; miner; mining cache: blog-the-question-of-mining.html plain text: blog-the-question-of-mining.txt item: #148 of 3327 id: blog-the-thawing-frontier author: blog title: blog-the-thawing-frontier date: None words: 795 flesch: 59 summary: We’ll be operating with a 3M (3141592, or pi million as it's affectionately called) gas target per block going forward. Epoch switch in 2 hours Let’s start with a quick heads up to miners, the network will be switching epoch in roughly 2 hours. keywords: gas; protocol cache: blog-the-thawing-frontier.html plain text: blog-the-thawing-frontier.txt item: #149 of 3327 id: blog-the-xbox-and-ethereums-dual-mandate author: blog title: blog-the-xbox-and-ethereums-dual-mandate date: None words: 1457 flesch: 43 summary: The Ethereum for-profit entity will be charged with the task of developing certain elements of the core infrastructure in collaboration with the non-profit entity and building out the Ecosystem with distributed application services and businesses that it develops itself, funds, or otherwise supports. Sign up Ethereum Foundation • Ethereum.org • ESP • Bug Bounty Program • Do-not-Track • Archive Categories Research & Development • Events • Organizational • Ecosystem Support Program • Ethereum.org • Security • Next Billion • Protocol Announcements keywords: development; ecosystem; ethereum; profit; protocol cache: blog-the-xbox-and-ethereums-dual-mandate.html plain text: blog-the-xbox-and-ethereums-dual-mandate.txt item: #150 of 3327 id: blog-toward-a-12-second-block-time author: blog title: blog-toward-a-12-second-block-time date: None words: 4332 flesch: 62 summary: At 60 seconds per block, however, we get 12 / 60 = 0.2 stales per valid block or a stale rate of 16.67%. At 12 seconds per block, we get 12 / 12 = 1 stale per valid block, or a stale rate of 50%. keywords: block; chain; mining; score; time; uncles cache: blog-toward-a-12-second-block-time.html plain text: blog-toward-a-12-second-block-time.txt item: #151 of 3327 id: blog-understanding-serenity-part-2-casper author: blog title: blog-understanding-serenity-part-2-casper date: None words: 4074 flesch: 47 summary: Understanding Serenity, Part 2: Casper | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Understanding Serenity, Part 2: Casper Posted by Vitalik Buterin on December 28, 2015 Research & Development Special thanks to Vlad Zamfir for introducing the idea of by-block consensus and convincing me of its merits, alongside many of the other core ideas of Casper, and to Vlad Zamfir and Greg Meredith for their continued work on the protocol In the last post in this series, we discussed one of the two flagship feature sets of Serenity: a heightened degree of abstraction that greatly increases the flexibility of the platform and takes a large step in moving Ethereum from Bitcoin plus Turing-complete to general-purpose decentralized computation. The core idea of consensus-by-bet is simple: the protocol offers opportunities for validators to bet against the protocol on which blocks are going to be finalized. keywords: bet; bets; block; consensus; protocol; validator cache: blog-understanding-serenity-part-2-casper.html plain text: blog-understanding-serenity-part-2-casper.txt item: #152 of 3327 id: blog-understanding-serenity-part-i-abstraction author: blog title: blog-understanding-serenity-part-i-abstraction date: None words: 2989 flesch: 38 summary: Length of validation code: 57 Length of account code: 0 Joined with index 0 Length of validation code: 57 Length of account code: 0 Joined with index 1 Length of validation code: 57 This is a simulation of 13 nodes running the Casper+Serenity protocol at a 5-second block time; this is fairly close to the upper limit of what the client can handle at the moment, though note that (i) this is python, and C++ and Go will likely show much higher performance, and (ii) this is all nodes running on one computer at the same time, so in a more normal environment it means you can expect python Casper to be able to handle at least ~169 nodes (though, on the other hand, we want consensus overhead to be much less than 100% of CPU time, so these two caveats combined do NOT mean that you should expect to see Casper running with thousands of nodes!). Accounts will simply be trees; account code will be stored at key for each account (not mutable by SSTORE), balances will be stored in a specialized ether contract and sequence numbers will be left up to each account to determine how to store. keywords: account; block; code; contract; ethereum; serenity; transaction cache: blog-understanding-serenity-part-i-abstraction.html plain text: blog-understanding-serenity-part-i-abstraction.txt item: #153 of 3327 id: blog-visions-part-1-the-value-of-blockchain-technology author: blog title: blog-visions-part-1-the-value-of-blockchain-technology date: None words: 4664 flesch: 44 summary: Additionally, blockchain developers should keep in mind that the last forty years of software development has been a history of moving to progressively less and less efficient programming languages and paradigms solely because they allow developers to be less experienced and lazier, and similarly work to design blockchain algorithms that work around the principle that developers are really not going to be all that smart and judicious about what they put on the blockchain and what they keep off - though a well-designed system of transaction fees will likely lead to developers naturally learning most of the important points through personal experience. Visions, Part 1: The Value of Blockchain Technology | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Visions, Part 1: The Value of Blockchain Technology Posted by Vitalik Buterin on April 13, 2015 Research & Development One of the questions that has perhaps been central to my own research in blockchain technology is: ultimately, what is it even useful for? keywords: applications; blockchain; data; key; people; reputation; use; world cache: blog-visions-part-1-the-value-of-blockchain-technology.html plain text: blog-visions-part-1-the-value-of-blockchain-technology.txt item: #154 of 3327 id: blog-visions-part-2-the-problem-of-trust author: blog title: blog-visions-part-2-the-problem-of-trust date: None words: 4547 flesch: 49 summary: Without that buildup of social capital, well, we simply have this: And lest you think that such incidents are a unique feature of cryptoland, back in the real world we also have this: The key promise of decentralized technology, under this viewpoint, is not to create systems that are even more trustworthy than current large institutions; if one simply looks at basic statistics in the developed world, one can see that many such systems can quite reasonably be described as being trustworthy enough, in that their annual rate of failure is sufficiently low that other factors dominate in the choice of which platform to use. In modern financial systems, particularly banks and trading systems, there exists a concept of settlement - essentially, a process after a transaction or trade is made the final result of which is that the assets that you bought actually become yours from a legal property-ownership standpoint. keywords: blockchain; model; people; set; system; time; trust; world cache: blog-visions-part-2-the-problem-of-trust.html plain text: blog-visions-part-2-the-problem-of-trust.txt item: #155 of 3327 id: blog-vitaliks-research-and-ecosystem-update author: blog title: blog-vitaliks-research-and-ecosystem-update date: None words: 1709 flesch: 29 summary: Research and Protocol Development We have identified four key areas of research regarding the underlying protocol that we feel represent the key milestones standing in the way between Ethereum as it currently exists and crypto-utopia: zk-SNARK integration: integrating, whether through a new opcode or ideally by leveraging the EVM's existing 256-bit modular arithmetic, the ability for Ethereum contracts to verify succinct zero-knowledge proofs. Vitalik’s Research and Ecosystem Update | Ethereum Foundation Blog EF Blog Search Skip to contentCategories R&D Research & Development Events Events Org Organizational ESP Ecosystem Support Program ETH.org Ethereum.org Sec Security NxBn Next Billion Protocol Protocol Announcements Languages Search Vitalik’s Research and Ecosystem Update Posted by Vitalik Buterin on October 18, 2015 Research & Development Over the last five days, myself, our executive director Ming Chan, and several others from the Ethereum team and Ethereum-based projects and businesses including Maker, String/Dfinity and Consensys have been visiting China and Hong Kong, where there have been a series of back-to-back conferences and events most notably including the Blockchain Workshop in Hong Kong on Oct 11-13 and the First Global Blockchain Summit in Shanghai organized by our friends at Wanxiang on Oct 15-16, while at the same time continuing to work on our usual tasks of research, development, planning DEVcon and administrative matters. keywords: blockchain; development; ethereum; protocol; research cache: blog-vitaliks-research-and-ecosystem-update.html plain text: blog-vitaliks-research-and-ecosystem-update.txt item: #156 of 3327 id: blog-what-if-ethereum-lived-on-a-treap-or-blockchains-charging-rent author: blog title: blog-what-if-ethereum-lived-on-a-treap-or-blockchains-charging-rent date: None words: 2498 flesch: 60 summary: One solution would be for transactions to have a maximum block number, which can be set to 10 days in the future by defauly, and then require all withdrawals to leave enough balance for the account to last another 10 days; this way, old transactions with nonce 0 would be too old to replay. However, there is also another more subtle consequence: account nonce resets. keywords: account; block; blockchain; node; treap cache: blog-what-if-ethereum-lived-on-a-treap-or-blockchains-charging-rent.html plain text: blog-what-if-ethereum-lived-on-a-treap-or-blockchains-charging-rent.txt item: #157 of 3327 id: blog-what-is-ethereum-project-platform-fuel-stack author: blog title: blog-what-is-ethereum-project-platform-fuel-stack date: None words: 1643 flesch: 49 summary: Like the BitTorrent content sharing system, Ethereum network nodes will run on thousands of computers around the world and, short of shutting down the Internet, its operations cannot be halted.   The payments are made to owners of computational resources in exchange for securing the Ethereum network, for transmitting transactions, for storing data and for processing computations required by distributed software applications. keywords: end; ethereum; system; ðapp cache: blog-what-is-ethereum-project-platform-fuel-stack.html plain text: blog-what-is-ethereum-project-platform-fuel-stack.txt item: #158 of 3327 id: blog-why-not-just-use-x-an-instructive-example-from-bitcoin author: blog title: blog-why-not-just-use-x-an-instructive-example-from-bitcoin date: None words: 759 flesch: 45 summary: Doing this for an existing software package is arguably almost as hard as building an entirely new package from scratch; in fact, it may even be harder, since existing software packages often have more complexity than they need to in order to be feature-complete, whereas our alternatives do not – read the protobuf spec and compare it to the RLP spec to understand what I mean. This issue arises from several sources, one of them being OpenSSL’s willingness to accept and make sense of signatures with invalid encodings. keywords: development; protocol cache: blog-why-not-just-use-x-an-instructive-example-from-bitcoin.html plain text: blog-why-not-just-use-x-an-instructive-example-from-bitcoin.txt item: #159 of 3327 id: docs-concepts author: docs title: docs-concepts date: None words: 1085 flesch: 41 summary: Trust-Triangle Issuer Issuers create verifiable credentials and give them to holders. Agent An agent is a software tool that helps manage and exchange verifiable credentials in a secure and trustworthy way. keywords: credentials; data; wallet cache: docs-concepts.html plain text: docs-concepts.txt item: #160 of 3327 id: docs-features author: docs title: docs-features date: None words: 898 flesch: 30 summary: Credential Definition Once a schema has been authored and added to the ledger, it becomes accessible for use by a diverse range of credential issuers, such as banks, passport offices, universities, employers, and more. The versatility of a schema definition allows multiple credential issuers to utilize it, promoting standardization across various issuers. keywords: credential; platform; user cache: docs-features.html plain text: docs-features.txt item: #161 of 3327 id: docs-implementations author: docs title: docs-implementations date: None words: 202 flesch: -8 summary: EduCreds (Academic Digital Credentials) Non-Academic Awards, Badges, Micro-credentials Employment Credentials Digital Travel Credentials Papua New Guinea advances digital ID, wallet and govt platform to pilot | Biometric UpdateBiometricUpdate.com NDI Website Bhutan NDI migration to CREDEBL & Polygon Blockchain SevisPass & SevisWallet Digital ID Pilot PreviousUse CasesNextGetting Started Last updated 1 day ago National Digital Identity for Royal Government of Bhutan SevisPass Digital ID Pilot for Papua New Guinea Sovio.id sovio.id is a SaaS platform offered by AYANWORKS which helps building various sector-specific Digital Credential solutions, while keeping away the complexity of Decentralized Identity technology/protocol stack, and allows innovators to focus on the specific business use case. keywords: digital; pilot cache: docs-implementations.html plain text: docs-implementations.txt item: #162 of 3327 id: docs-use-cases author: docs title: docs-use-cases date: None words: 167 flesch: -18 summary: CtrlK GithubDiscordMore Introduction Overview Features Concepts 🏯Use Cases 🚀Implementations Getting Started Getting Started Local Deployment Platform Studio Mobile SDK Cloud Deployment AWS Resources Tutorials Guides References Architecture Platform APIs FAQs Glossary Copyright & License Contribute How to contribute Setup Service setup Studio (Optional) Agent Powered by GitBook On this page National Digital Identity Digital Travel Credentials Academic Digital Credentials Employee / HR Credentials Health Credentials Life Events Edit on GitHub Introduction Use Cases CREDEBL can be leveraged to build various large-scale Verifiable Digital Credential use cases. Some of them are: PreviousConceptsNextImplementations Last updated 6 months ago Foundational ID Functional IDs e.g. - Permanent Address, Phone Number, Driving License, Passport, Tax ID Digital Travel Credentials Boarding Pass, Passport, Visa, Work Authorization Student ID, Degree, Diploma, Transcripts, Bonafide, Transfer Certificate Employee / HR Credentials Employment Credential, Awards & Recognitions, Training Credentials Health Credentials Vaccine Credentials, Test Reports, e-Prescriptions Life Events Birth Certificate, Death Certificate, Marriage Certificate, etc. 🏯 National Digital Identity Academic Digital Credentials keywords: cases; credentials cache: docs-use-cases.html plain text: docs-use-cases.txt item: #163 of 3327 id: eips-eip-1 author: eips title: eips-eip-1 date: None words: 4312 flesch: 51 summary: A preferred way is the following: REVERT (0xfe) EIP Work Flow Shepherding an EIP Parties involved in the process are you, the champion or EIP author, the EIP editors, and the Ethereum Core Developers. The EIP editors monitor EIP changes, and correct any structure, grammar, spelling, or markup mistakes we see. keywords: author; consensus; eip; eips; ethereum; header; process; rfc; specification; standards cache: eips-eip-1.html plain text: eips-eip-1.txt item: #164 of 3327 id: eips-eip-100 author: eips title: eips-eip-100 date: None words: 356 flesch: 30 summary: A formula that accounts for the exact number of included uncles: adj_factor = max(1 + len(parent.uncles) - ((timestamp - parent.timestamp) // 9), -99) can be fairly easily seen to be (to within a tolerance of ~3/4194304) mathematically equivalent to assuming that a block with k uncles is equivalent to a sequence of k+1 blocks that all appear with the exact same timestamp, and this is likely the simplest possible way to accomplish the desired effect. EIP-100: Change difficulty adjustment to target mean block time including uncles Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: Core EIP-100: Change difficulty adjustment to target mean block time including uncles Authors Vitalik Buterin (@vbuterin) Created 2016-04-28 Table of Contents Specification Rationale References Specification Currently, the formula to compute the difficulty of a block includes the following logic: adj_factor = max(1 - ((timestamp - parent.timestamp) // 10), -99) child_diff = int(max(parent.difficulty + (parent.difficulty // BLOCK_DIFF_FACTOR) keywords: block cache: eips-eip-100.html plain text: eips-eip-100.txt item: #165 of 3327 id: eips-eip-101 author: eips title: eips-eip-101 date: None words: 906 flesch: 46 summary: Run the code for a maximum of 50000 gas, stopping if they see an operation or call that threatens to go over this limit Upon seeing that operation, make sure that it leaves at last 50000 gas to spare (either by checking that the static gas consumption is small enough or by checking that it is a call with msg.gas - 50000 as its gas limit parameter) Pattern-match to make sure that gas payment code at the end is exactly the same as in the code above. ~calldatacopy(32, 96, ~calldatasize() - 96) h = sha3(96, ~calldatasize() - 96) # Call ECRECOVER contract to get the sender ~call(5000, 3, [h, ~calldataload(0), ~calldataload(32), ~calldataload(64)], 128, ref(addr), 32) # Check sender correctness assert addr == 0x82a978b3f5962a5b0957d9ee9eef472ee55b42f1 # Check sequence number correctness assert ~calldataload(96) keywords: code; ethereum; gas cache: eips-eip-101.html plain text: eips-eip-101.txt item: #166 of 3327 id: eips-eip-1010 author: eips title: eips-eip-1010 date: None words: 479 flesch: 37 summary: Created 2018-04-18 Discussion Link https://github.com/andywesley/EIPs/issues/1 Table of Contents Simple Summary Abstract Motivation Specification Rationale Backwards Compatibility Copyright Simple Summary This document proposes to improve the uniformity of ether distribution between wallet address 0xAb5801a7D398351b8bE11C439e05C5B3259aeC9B and wallet address 0x15E55EF43efA8348dDaeAa455F16C43B64917e3c which are currently experiencing a significant non-uniformity. Abstract As of the date of this EIP, the difference in balance between address 0xAb5801a7D398351b8bE11C439e05C5B3259aeC9B and address 0x15E55EF43efA8348dDaeAa455F16C43B64917e3c is far from equitable or uniform, with the former having more than 365,000 ether more than the latter. keywords: ether cache: eips-eip-1010.html plain text: eips-eip-1010.txt item: #167 of 3327 id: eips-eip-1011 author: eips title: eips-eip-1011 date: None words: 4106 flesch: 44 summary: == gasprice == 0 When producing and validating a block, when handling vote transactions to CASPER_ADDR: Only include “valid” vote transactions as defined above Place all vote transactions at the end of the block Track cumulative gas used by votes separately from cumulative gas used by normal transactions via vote_gas_used Total vote_gas_used of vote transactions cannot exceed the block_gas_limit, independent of gas used by normal block transactions When applying vote transactions to CASPER_ADDR to vm state: Due to the nature of this contract being deployed outside of normal block transactions and to a particular address, the EVM init code/CREATE method requires client specific “hacks” to make it work. keywords: block; casper; contract; ffg; fork; transactions; validator; vote cache: eips-eip-1011.html plain text: eips-eip-1011.txt item: #168 of 3327 id: eips-eip-1013 author: eips title: eips-eip-1013 date: None words: 206 flesch: 39 summary: Citation Please cite this document as: Nick Savers (@nicksavers), EIP-1013: Hardfork Meta: Constantinople, Ethereum Improvement Proposals, no. 1013, April 2018. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: ethereum cache: eips-eip-1013.html plain text: eips-eip-1013.txt item: #169 of 3327 id: eips-eip-1014 author: eips title: eips-eip-1014 date: None words: 712 flesch: 39 summary: Motivation Allows interactions to (actually or counterfactually in channels) be made with addresses that do not exist yet on-chain but can be relied on to only possibly eventually contain code that has been created by a particular piece of init code. Behaves identically to CREATE (0xf0), except using keccak256( 0xff ++ address ++ salt ++ keccak256(init_code))[12:] instead of the usual sender-and-nonce-hash as the address where the contract is initialized at. keywords: address; init_code cache: eips-eip-1014.html plain text: eips-eip-1014.txt item: #170 of 3327 id: eips-eip-1015 author: eips title: eips-eip-1015 date: None words: 1804 flesch: 50 summary: They can be research, whole network security, incentivize full clients and networking, fair distribution of tokens etc. Proposed Solution Issuance Contract This EIP proposes a future hard fork where block reward is not issued to miners/validators etherbase, but instead to a single contract, that then will activate the default function (with a fixed amount of gas) and then it will forward the ether to other contracts which will finally distribute to their final destinations. As new governance methods are tested and debated, new signalling contracts should be added and removed. keywords: contract; decision; ethereum; issuance cache: eips-eip-1015.html plain text: eips-eip-1015.txt item: #171 of 3327 id: eips-eip-1046 author: eips title: eips-eip-1046 date: None words: 1258 flesch: 53 summary: This ERC adds a tokenURI function to ERC-20, and extends ERC-721 and ERC-1155 to enable interoperability between all three types of token URI. Additionally, for ERC-20 tokens, if the decimals is 18, then it is NOT RECOMMENDED to include the decimals field in the metadata. keywords: erc-20; metadata; token cache: eips-eip-1046.html plain text: eips-eip-1046.txt item: #172 of 3327 id: eips-eip-1051 author: eips title: eips-eip-1051 date: None words: 604 flesch: 55 summary: In the interests of facilitating efficient and secure contracts, we propose new opcodes that permit efficient detection of overflows, which can be checked periodically rather than after each operation. One option would be to provide an opcode that enables overflow protection, causing a throw or revert if an overflow happens. keywords: opcode; overflow cache: eips-eip-1051.html plain text: eips-eip-1051.txt item: #173 of 3327 id: eips-eip-1052 author: eips title: eips-eip-1052 date: None words: 579 flesch: 60 summary: The EXTCODEHASH distincts accounts without code and non-existing accounts. Citation Please cite this document as: Nick Johnson , Paweł Bylica , EIP-1052: EXTCODEHASH opcode, Ethereum Improvement Proposals, no. 1052, May 2018. keywords: account; extcodehash cache: eips-eip-1052.html plain text: eips-eip-1052.txt item: #174 of 3327 id: eips-eip-1056 author: eips title: eips-eip-1056 date: None words: 1309 flesch: 41 summary: ERC-1056: Ethereum Lightweight Identity Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-1056: Ethereum Lightweight Identity Authors Pelle Braendgaard , Joel Torstensson  Created 2018-05-03 Discussion Link https://github.com/ethereum/EIPs/issues/1056 Table of Contents Simple Summary Abstract Motivation Definitions Specification Identity ownership Delegate management Attribute management Events Efficient lookup of events through linked identity events Building a DID document for an identity Rationale Backwards Compatibility Implementation Deployment Copyright Simple Summary A registry for key and attribute management of lightweight blockchain identities. Lookup previousChange block for identity Lookup all events for given identity address using web3, but only for the previousChange block Do something with event Find previousChange from the event and repeat Example code: const history = keywords: address; bytes32; ethereum; identity cache: eips-eip-1056.html plain text: eips-eip-1056.txt item: #175 of 3327 id: eips-eip-1057 author: eips title: eips-eip-1057 date: None words: 4970 flesch: 55 summary: typedef struct { uint32_t z, w, jsr, jcong; } kiss99_t; // KISS99 is simple, fast, and passes the TestU01 suite // https://en.wikipedia.org/wiki/KISS_(algorithm) // http://www.cse.yorku.ca/~oz/marsaglia-rng.html uint32_t kiss99(kiss99_t &st) { st.z = 36969 * (st.z & 65535) + (st.z >> 16); st.w = 18000 * (st.w & 65535) + (st.w >> 16); uint32_t MWC = ((st.z << 16) + st.w); st.jsr ^= (st.jsr << 17); st.jsr ^= (st.jsr >> 13); st.jsr ^= (st.jsr << 5); st.jcong = 69069 * st.jcong + 1234567; return ((MWC^st.jcong) + st.jsr); } The fill_mix function populates an array of int32 values used by each lane in the hash calculations. kiss99_t st; st.z = fnv1a(fnv_hash, seed); st.w = fnv1a(fnv_hash, seed >> 32); st.jsr = fnv1a(fnv_hash, lane_id); st.jcong = fnv1a(fnv_hash, lane_id); for (int i = 0; i < PROGPOW_REGS; i++) mix[i] = kiss99(st); } Like Ethash Keccak is used to seed the sequence per-nonce and to produce the final result. keywords: = =; asic; dag; efficiency; hardware; int; loop; test; uint32_t cache: eips-eip-1057.html plain text: eips-eip-1057.txt item: #176 of 3327 id: eips-eip-1062 author: eips title: eips-eip-1062 date: None words: 711 flesch: 44 summary: Rationale To implement the specification, need two methods from ENS public resolver contract, when we want to store IPFS file fingerprint to contract, convert the Base58 string identifier to the hex format and invoke the setMultihash method below : function setMultihash(bytes32 node, bytes hash) public only_owner(node); Abstract The following standard details the implementation of how to combine the IPFS cryptographic hash unique fingerprint with ENS public resolver. keywords: ens; hex; ipfs cache: eips-eip-1062.html plain text: eips-eip-1062.txt item: #177 of 3327 id: eips-eip-1066 author: eips title: eips-eip-1066 date: None words: 3809 flesch: 65 summary: Abstract This standard outlines a common set of status codes in a similar vein to HTTP statuses. Status codes are similar-but-orthogonal to reverting with a reason, but aimed at automation, debugging, and end-user feedback (including translation). keywords: app; chain; codes; range; specific; status; | check cache: eips-eip-1066.html plain text: eips-eip-1066.txt item: #178 of 3327 id: eips-eip-107 author: eips title: eips-eip-107 date: None words: 4656 flesch: 13 summary: M=3,C(this,new E(e,n),P,k)},T.dividedToIntegerBy=T.divToInt=function(e,n){return M=4,C(this,new E(e,n),0,1)},T.equals=T.eq=function(e,n){return M=5,0===i(this,new E(e,n))},T.floor=function(){return U(new E(this),this.e+1,3)},T.greaterThan=T.gt=function(e,n){return M=6,i(this,new E(e,n))>0},T.greaterThanOrEqualTo=T.gte=function(e,n){return M=7,1===(n=i(this,new E(e,n)))||0===n},T.isFinite=function(){return!!this.c},T.isInteger=T.isInt=function(){return!!this.c&&t(this.e/O)>this.c.length-2},T.isNaN=function(){return!this.s},T.isNegative=T.isNeg=function(){return this.s<0},T.isZero=function(){return!!this.c&&0==this.c[0]},T.lessThan=T.lt=function(e,n){return M=8,i(this,new E(e,n))<0},T.lessThanOrEqualTo=T.lte=function(e,n){return M=9,-1===(n=i(this,new E(e,n)))||0===n},T.minus=T.sub=function(e,n){var r,i,o,u,s=this,f=s.s;if(M=10,e=new E(e,n),n=e.s,!f||!n)return new E(NaN);if(f!=n)return e.s=-n,s.plus(e);var l=s.e/O,c=e.e/O,a=s.c,h=e.c;if(!l||!c){if(!a||!h)return a?(e.s=-n,e):new E(h?s:NaN);if(!a[0]||!h[0])return h[0]?(e.s=-n,e):new E(a[0]?s:3==k?-0:0)}if(l=t(l),c=t(c),a=a.slice(),f=l-c){for((u=0>f)?(f=-f,o=a):(c=l,o=h),o.reverse(),n=f;n--;o.push(0));o.reverse()}else for(i=(u=(f=a.length)<(n=h.length))?f:n,f=n=0;i>n;n++)if(a[n]!=h[n]){u=a[n]0)for(;n--;a[r++]=0);for(n=b-1;i>f;){if(a[--i]e||e>y)?n.s*(0>e?0:1/0):n)},T.squareRoot=T.sqrt=function(){var e,n,i,o,u,s=this,f=s.c,l=s.s,c=s.e,a=P+4,h=new E(0.5);if(1!==l||!f||!f[0])return new E(!l||0>l&&(!f||f[0])?NaN:f?s:1/0);if(l=Math.sqrt(+s),0==l||l==1/0?(n=r(f),(n.length+c)%2==0&&(n+=0),l=Math.sqrt(n),c=t((c+1)/2)-(0>c||c%2),l==1/0?n=1e+c:(n=l.toExponential(),n=n.slice(0,n.indexOf(e)+1)+c),i=new E(n)):i=new E(l+),i.c[0])for(c=i.e,l=c+a,3>l&&(l=0);;)if(u=i,i=h.times(u.plus(C(s,u,a,1))),r(u.c).slice(0,l)===(n=r(i.c)).slice(0,l)){if(i.el&&(d=N,N=y,y=d,o=l,l=h,h=o),o=l+h,d=[];o--;d.push(0));for(m=b,w=R,o=h;--o>=0;){for(r=0,g=y[o]%w,p=y[o]/w|0,s=l,u=o+s;u>o;)c=N[--s]%w,a=N[s]/w|0,f=p*c+a*g,c=g*c+f%w*w+d[u]+r,r=(c/m|0)+(f/w|0)+p*a,d[u--]=c%m;d[u]=r}return r?++i:d.shift(),I(e,d,i)},T.toDigits=function(e,n){var t=new E(this);return e=null!=e&&H(e,1,A,18,precision)?0|e:null,n=null!=n&&H(n,0,8,18,w)?0|n:k,e?U(t,e,n):t},T.toExponential=function(e,n){return F(this,null!=e&&H(e,0,A,19)?~~e+1:null,n,19)},T.toFixed=function(e,n){return F(this,null!=e&&H(e,0,A,20)?~~e+this.e+1:null,n,20)},T.toFormat=function(e,n){var t=F(this,null!=e&&H(e,0,A,21)?~~e+this.e+1:null,n,21);if(this.c){var r,i=t.split(.),o=+X.groupSize,u=+X.secondaryGroupSize,s=X.groupSeparator,f=i[0],l=i[1],c=this.s<0,a=c?f.slice(1):f,h=a.length;if(u&&(r=o,o=u,u=r,h-=r),o>0&&h>0){for(r=h%o||o,f=a.substr(0,r);h>r;r+=o)f+=s+a.substr(r,o);u>0&&(f+=s+a.slice(r)),c&&(f=-+f)}t=l?f+X.decimalSeparator+((u=+X.fractionGroupSize)?l.replace(new RegExp(\\d{+u+}\\B,g),$&+X.fractionGroupSeparator):l):f}return t},T.toFraction=function(e){var n,t,i,o,u,s,f,l,c,a=j,h=this,g=h.c,p=new E(q),d=t=new E(q),m=f=new E(q);if(null!=e&&(j=!1,s=new E(e),j=a,(!(a=s.isInt())||s.lt(q))&&(j&&L(22,max denominator +(a?out of range:not an integer),e),e=!a&&s.c&&U(s,s.e+1,1).gte(q)?s:null)),!g)return h.toString();for(c=r(g),o=p.e=c.length-h.e-1,p.c[0]=S[(u=o%O)<0?O+u:u],e=!e||s.cmp(p)>0?o>0?p:d:s,u=z,z=1/0,s=new E(c),f.c[0]=0;l=C(s,p,0,1),i=t.plus(l.times(m)),1!=i.cmp(e);)t=m,m=i,d=f.plus(l.times(i=d)),f=i,p=s.minus(l.times(i=p)),s=i;return i=C(e.minus(t),m,0,1),f=f.plus(i.times(d)),t=t.plus(i.times(m)),f.s=d.s=h.s,o*=2,n=C(d,m,o,k).minus(h).abs().cmp(C(f,t,o,k).minus(h).abs())<1?[d.toString(),m.toString()]:[f.toString(),t.toString()],z=u,n},T.toNumber=function(){return+this},T.toPower=T.pow=function(e,n){var t,r,i,o=d(0>e?-e:+e),u=this;if(null!=n&&(M=23,n=new E(n)),!H(e,-y,y,23,exponent)&&(!isFinite(e)||o>y&&(e/=0)||parseFloat(e)!=e&&!(e=NaN))||0==e)return t=Math.pow(+u,e),new E(n?t%n:t);for(n?e>1&&u.gt(q)&&u.isInt()&&n.gt(q)&&n.isInt()?u=u.mod(n):(i=n,n=null):J&&(t=p(J/O+2)),r=new E(q);;){if(o%2){if(r=r.times(u),!r.c)break;t?r.c.length>t&&(r.c.length=t):n&&(r=r.mod(n))}if(o=d(o/2),!o)break;u=u.times(u),t?u.c&&u.c.length>t&&(u.c.length=t):n&&(u=u.mod(n))}return n?r:(0>e&&(r=q.div(r)),i?r.mod(i):t?U(r,J,k):r)},T.toPrecision=function(e,n){return F(this,null!=e&&H(e,1,A,24,precision)?0|e: keywords: account; button; dapp; e(e; function; html; message; new; node; result; rpc; user; var cache: eips-eip-107.html plain text: eips-eip-107.txt item: #179 of 3327 id: eips-eip-1077 author: eips title: eips-eip-1077 date: None words: 2331 flesch: 48 summary: The standardization of account contracts is not scope of this ERC, and is presented here only for illustration on possible implementations. Allowing users to sign messages to show intent of execution, but allowing a third party relayer to execute them can circumvent this problem, while ETH will always be required for ethereum transactions, it’s possible for smart contract to take EIP-191 signatures and forward a payment incentive to an untrusted party with ETH for executing the transaction. keywords: account; contract; gas; nonce; token; transaction cache: eips-eip-1077.html plain text: eips-eip-1077.txt item: #180 of 3327 id: eips-eip-1078 author: eips title: eips-eip-1078 date: None words: 2307 flesch: 61 summary: From the user point of view it will be very similar to patterns they’re already used to with second factor authentication (without relying in a central server), but for dapp developers it requires a new way to think about ethereum transactions. An app should only require this level of privilege if it’s a general purpose wallet or browser for sending ethereum transactions. keywords: app; identity; transaction; user cache: eips-eip-1078.html plain text: eips-eip-1078.txt item: #181 of 3327 id: eips-eip-1080 author: eips title: eips-eip-1080 date: None words: 689 flesch: 43 summary: returns (bool success) getLostAccountRecoveryTimeInMinutes Get the time account has to wait before a lost account dispute can start. function getLostAccountRecoveryTimeInMinutes(address account) view returns (uint256 minutes) setLostAccountRecoveryTimeInMinutes Sets the time msg.sender’s account has to sit before a lost account dispute can start. Account recoveries must trigger the AccountRecovered event. keywords: account; event cache: eips-eip-1080.html plain text: eips-eip-1080.txt item: #182 of 3327 id: eips-eip-1081 author: eips title: eips-eip-1081 date: None words: 1585 flesch: 35 summary: The initial version had significantly more restrictions: a bounty’s data could not be changed after issuance (it seemed unfair for bounty issuers to change the requirements after work is underway), and the bounty payout could not be changed (all funds needed to be deposited in the bounty contract before it could accept submissions). This is useful since it still immutably stores the exchange of tokens for completed work, but avoids the need for new bounty fulfillers to have any ETH to pay for gas costs in advance of their earnings. keywords: bounty; ethereum; issuer; string cache: eips-eip-1081.html plain text: eips-eip-1081.txt item: #183 of 3327 id: eips-eip-1087 author: eips title: eips-eip-1087 date: None words: 1238 flesch: 60 summary: Keeping a separate refund counter for storage gas refunds would avoid the issue of refunds being limited to half the gas consumed (not necessary here), but would introduce additional complexity in tracking this value. We believe the proposed mechanism represents the simplest way to reduce storage gas costs in situations where they do not reflect the actual costs borne by nodes. keywords: gas; slot cache: eips-eip-1087.html plain text: eips-eip-1087.txt item: #184 of 3327 id: eips-eip-1102 author: eips title: eips-eip-1102 date: None words: 896 flesch: 41 summary: Accounts now exposed, use them ethereum.send('eth_sendTransaction', { from: accounts[0], /* ... */ }) } catch (error) { // User denied account access } Constraints Browsers MUST expose a provider at window.ethereum . Immediate value-add Users can reject account access on untrusted sites to hide accounts. keywords: account; user cache: eips-eip-1102.html plain text: eips-eip-1102.txt item: #185 of 3327 id: eips-eip-1108 author: eips title: eips-eip-1108 date: None words: 1293 flesch: 47 summary: Faster operations on Ethereum clients should be reflected in reduced gas costs. Parity and Geth already have fast algorithms that justify reduced gas costs This EIP does not require Parity or Geth to deploy new cryptographic libraries, as fast bn128 algorithms have already been integrated into these clients. keywords: costs; ethereum; gas; pairing cache: eips-eip-1108.html plain text: eips-eip-1108.txt item: #186 of 3327 id: eips-eip-1109 author: eips title: eips-eip-1109 date: None words: 682 flesch: 60 summary: Old contracts that call precompiled smart contracts with the CALL method, will continue working. EIP-1109: PRECOMPILEDCALL opcode (Remove CALL costs for precompiled contracts) Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-1109: PRECOMPILEDCALL opcode (Remove CALL costs for precompiled contracts) Authors Jordi Baylina (@jbaylina) Created 2018-05-22 Discussion Link https://ethereum-magicians.org/t/eip-1109-remove-call-costs-for-precompiled-contracts/447 Table of Contents Simple Summary Abstract Motivation Specification Rationale Backwards Compatibility Test Cases Implementation Copyright Simple Summary This EIP creates a specific opcode named PRECOMPILEDCALL to call Precompiled contracts without the costs of a normal CALL. keywords: contract; opcode cache: eips-eip-1109.html plain text: eips-eip-1109.txt item: #187 of 3327 id: eips-eip-1123 author: eips title: eips-eip-1123 date: None words: 4196 flesch: 59 summary: Required No Key build_dependencies Type Object (String: String) Format Keys must be valid package names matching the regular expression Each of p1, p2, pn must be valid package names. keywords: contract; field; format; instance; object; package; type; value cache: eips-eip-1123.html plain text: eips-eip-1123.txt item: #188 of 3327 id: eips-eip-1129 author: eips title: eips-eip-1129 date: None words: 712 flesch: 43 summary: event NewAnnouncement(string author, string message) Removed announcement MUST trigger when an announcement is removed. Citation Please cite this document as: Jan Turk (@ThunderDeliverer), ERC-1129: Standardised DAPP announcements [DRAFT], Ethereum Improvement Proposals, no. 1129, May 2018. keywords: announcement; author; ethereum cache: eips-eip-1129.html plain text: eips-eip-1129.txt item: #189 of 3327 id: eips-eip-1132 author: eips title: eips-eip-1132 date: None words: 1086 flesch: 34 summary: ERC-1132: Extending ERC20 with token locking capability Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-1132: Extending ERC20 with token locking capability Authors nitika-goel  Created 2018-06-03 Discussion Link https://github.com/ethereum/EIPs/issues/1132 Table of Contents Simple Summary Abstract Motivation Specification Locking of tokens Fetching number of tokens locked under each utility Fetching number of tokens locked under each utility at a future timestamp Fetching number of tokens held by an address Extending lock period Increasing number of tokens locked Fetching number of unlockable tokens under each utility Fetching number of unlockable tokens under each utility /** * @dev Returns unlockable tokens for a specified address for a specified reason * @param _of The address to query the the unlockable token count of * @param _reason The reason to query the unlockable tokens for */ function tokensUnlockable(address _of, bytes32 _reason) public view returns (uint256 amount) Fetching number of unlockable tokens /** * @dev Gets the unlockable tokens of a specified address * @param _of The address to query the the unlockable token count of */ function getUnlockableTokens(address _of) public view returns (uint256 unlockableTokens) keywords: @param; reason; tokens cache: eips-eip-1132.html plain text: eips-eip-1132.txt item: #190 of 3327 id: eips-eip-1153 author: eips title: eips-eip-1153 date: None words: 2570 flesch: 55 summary: Relative pros of this transient storage EIP: Transient storage opcodes are considered separately in protocol upgrades and not inadvertently broken (e.g. EIP-3529) Clients do not need to load the original value No upfront gas cost to account for non-transient writes Does not change the semantics of the existing operations No need to clear storage slots after usage Simpler gas accounting rules Future storage designs (e.g. Verkle tree) do not need to account for transient storage refunds Backwards Compatibility This EIP requires a hard fork to implement. Table of Contents Abstract Motivation Specification Rationale Backwards Compatibility Reference Implementation Security Considerations Copyright Abstract This proposal introduces transient storage opcodes, which manipulate state that behaves identically to storage, except that transient storage is discarded after every transaction. keywords: gas; memory; storage; transient cache: eips-eip-1153.html plain text: eips-eip-1153.txt item: #191 of 3327 id: eips-eip-1154 author: eips title: eips-eip-1154 date: None words: 1216 flesch: 52 summary: A distinction and a choice is made between push and pull based oracle systems. Ultimately, the value in different oracle systems comes from their underlying resolution mechanics, and points where these systems are virtually identical should be standardized. keywords: oracle; pull; result cache: eips-eip-1154.html plain text: eips-eip-1154.txt item: #192 of 3327 id: eips-eip-1155 author: eips title: eips-eip-1155 date: None words: 7871 flesch: 55 summary: To alleviate the need to emit events when changing contract address, consider using the proxy pattern, such as described in EIP-2535. Backwards Compatibility There have been requirements during the design discussions to have this standard be compatible with existing standards when sending to contract addresses, specifically ERC-721 at time of writing. keywords: address; argument; balance; contract; function; rules; standard; token; transfer; value cache: eips-eip-1155.html plain text: eips-eip-1155.txt item: #193 of 3327 id: eips-eip-1167 author: eips title: eips-eip-1167 date: None words: 1032 flesch: 45 summary: Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. f4 delegatecall suc 0 | 0x0000001c 3d returndatasize rds suc 0 | 0x0000001d 82 dup3 0 rds suc 0 | 0x0000001e 80 dup1 0 0 rds suc 0 | 0x0000001f 3e returndatacopy suc 0 | 0x00000020 90 swap1 0 suc | 0x00000021 3d returndatasize rds 0 suc | 0x00000022 91 swap2 suc 0 keywords: returndatasize cache: eips-eip-1167.html plain text: eips-eip-1167.txt item: #194 of 3327 id: eips-eip-1175 author: eips title: eips-eip-1175 date: None words: 1668 flesch: 21 summary: function aboutItem(uint256 _item) view returns (uint256 _price, uint256 _up, uint256 _down) Events Pay event Pay(address indexed _buyer, uint256 indexed _item, uint256 indexed _value) Refund event Refund(address indexed _to, uint256 indexed _item, uint256 indexed _value) Item event Item(uint256 indexed _item, uint256 _price) Info event Info(bytes _msgPack) InfoItem event InfoItem(uint256 indexed _item, bytes _msgPack) Implementation Sample token contract address is 0x393dd70ce2ae7b30501aec94727968c517f90d52 WalletCenter contract address is 0x1fe0862a4a8287d6c23904d61f02507b5044ea31 WalletCenter create shop contract address is 0x59117730D02Ca3796121b7975796d479A5Fe54B0 WalletCenter create wallet contract address is 0x39da7111844df424e1d0a0226183533dd07bc5c6 Appendix pragma solidity ^0.4.24; contract ERC20Interface { function totalSupply() public constant returns (uint); function balanceOf(address tokenOwner) public constant returns (uint balance); function allowance(address tokenOwner, address spender) public constant returns (uint remaining); function transfer(address to, uint tokens) public returns (bool success); function approve(address spender, uint tokens) public returns (bool success); function transferFrom(address from, address to, uint tokens) public returns (bool success); = disable, 1 = non Stock, non Expire, 2 = can Expire (after 1 week), 3 = stackable uint256 price; uint256 stockCount; mapping(address=>uint256) customer; } uint index; mapping(uint256=>item) items; function pay(uint256 _item) onlyWallet(msg.sender) public payable returns (bool success) { require(canBuy(msg.sender, _item)); require((erc20==address(0)?msg.value:ERC20Interface(erc20).allowance(msg.sender,this))==items[_item].price); if(erc20!=address(0)) ERC20Interface(erc20).transferFrom(msg.sender,this,items[_item].price); if(items[_item].category==1 || items[_item].category==2 && now > safeAdd(items[_item].customer[msg.sender], 1 weeks)) items[_item].customer[msg.sender] = now; else if(items[_item].category==2 && now < safeAdd(items[_item].customer[msg.sender], 1 weeks) ) items[_item].customer[msg.sender] = safeAdd(items[_item].customer[msg.sender], 1 weeks); else if(items[_item].category==3) { items[_item].customer[msg.sender] = safeAdd(items[_item].customer[msg.sender],1); items[_item].stockCount = safeSub(items[_item].stockCount,1); } emit Pay(msg.sender,_item,items[_item].customer[msg.sender]); return true; } function payCancel(uint256 _item) onlyWallet(msg.sender) public returns (bool success) { require (items[_item].category==2&&safeAdd(items[_item].customer[msg.sender],2 weeks)>now&&balanceOf(erc20)>=items[_item].price); items[_item].customer[msg.sender] = safeSub(items[_item].customer[msg.sender],1 weeks); transfer(msg.sender, erc20, items[_item].price); _Wallet(msg.sender).refund(erc20,_item,items[_item].price); emit Refund(msg.sender,_item,items[_item].price); return true; } function refund(address _to, uint256 _item) onlyWallet(_to) onlyOwner public payable returns (bool success) { require(isBuyer(_to,_item)&&items[_item].category>0&&(items[_item].customer[_to]>0||(items[_item].category==2&&safeAdd(items[_item].customer[_to],2 weeks)>now))); require((erc20==address(0)?address(this).balance:ERC20Interface(erc20).balanceOf(this))>=items[_item].price); if(items[_item].category==1) items[_item].customer[_to] = 0; else if(items[_item].category==2) items[_item].customer[_to] keywords: function; item; returns; shop; uint256 cache: eips-eip-1175.html plain text: eips-eip-1175.txt item: #195 of 3327 id: eips-eip-1178 author: eips title: eips-eip-1178 date: None words: 1434 flesch: 50 summary: balanceOf function balanceOf(address _owner, uint256 _classId) constant returns (uint256 balance) Returns the number of MCFTs of token class _classId assigned to address _owner. classesOwned function classesOwned(address _owner) constant returns (uint256[] classes) Returns an array of _classId’s of MCFTs that address _owner owns in the contract. NOTE: returning an array is supported by pragma experimental ABIEncoderV2 Basic Ownership approve function approve(address _to, uint256 _classId, uint256 quantity) Grants approval for address _to to take possession quantity amount of the MCFT with ID _classId. keywords: address; classid; uint256 cache: eips-eip-1178.html plain text: eips-eip-1178.txt item: #196 of 3327 id: eips-eip-1185 author: eips title: eips-eip-1185 date: None words: 1764 flesch: 58 summary: Review Standards Track: ERC ERC-1185: Storage of DNS Records in ENS A system to store and retrieve DNS records within the ENS contract. Table of Contents Abstract Motivation Specification setDNSRecords(bytes32 node, bytes data) clearDNSZone(bytes32 node) dnsRecords(bytes32 node, bytes32 name, uint16 resource) view returns (bytes) hasDNSRecords(bytes32 node, bytes32 name) view returns (bool) Rationale Backwards Compatibility Reference Implementation Security Considerations Copyright Abstract This EIP defines a resolver profile for ENS that provides features for storage and lookup of DNS records. keywords: dns; node; records cache: eips-eip-1185.html plain text: eips-eip-1185.txt item: #197 of 3327 id: eips-eip-1186 author: eips title: eips-eip-1186 date: None words: 1000 flesch: 50 summary: EIP-1186: RPC-Method to get Merkle Proofs - eth_getProof Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Interface EIP-1186: RPC-Method to get Merkle Proofs - eth_getProof Authors Simon Jentzsch , Christoph Jentzsch  Created 2018-06-24 Discussion Link https://github.com/ethereum/EIPs/issues/1186 Requires EIP-1474 Table of Contents Simple Summary Abstract Motivation Specification Rationale Proofs for non existent values possible Changes to be discussed: Backwards Compatibility Test Cases Copyright Simple Summary One of the great features of Ethereum is the fact, that you can verify all data of the state. This EIP suggests an additional RPC-Method, which creates Merkle Proofs for Accounts and Storage Values. keywords: account; data; storage cache: eips-eip-1186.html plain text: eips-eip-1186.txt item: #198 of 3327 id: eips-eip-1191 author: eips title: eips-eip-1191 date: None words: 625 flesch: 41 summary: This EIP extends EIP-55 to protect users from losing funds by sending them to addresses that are valid but that where obtained from a client of another network. Motivation The motivation of this proposal is to provide a mechanism to allow software to distinguish addresses from different Ethereum based networks. keywords: ethereum cache: eips-eip-1191.html plain text: eips-eip-1191.txt item: #199 of 3327 id: eips-eip-1193 author: eips title: eips-eip-1193 date: None words: 2932 flesch: 46 summary: chainChanged If the chain the Provider is connected to changes, the Provider MUST emit the event named chainChanged with value chainId: string, specifying the integer ID of the new chain as a hexadecimal string, per the eth_chainId Ethereum RPC method. accountsChanged If the accounts available to the Provider change, the Provider MUST emit the event named accountsChanged with value accounts: string[], containing the account addresses per the eth_accounts Ethereum RPC method. => void): Provider; The event emits an object with a hexadecimal string chainId per the eth_chainId Ethereum RPC method, and other properties as determined by the Provider. disconnect The Provider emits disconnect when it becomes disconnected from all chains. keywords: ethereum; event; method; provider; rpc cache: eips-eip-1193.html plain text: eips-eip-1193.txt item: #200 of 3327 id: eips-eip-1202 author: eips title: eips-eip-1202 date: None words: 1405 flesch: 43 summary: For example, a token based voting where voting weight is determined by the amount of token held by a voter, a voter who wants to distribute its voting power in two different option(option set) can transfer some of the tokens to the new account and cast the votes from both accounts. ERC-1202: Voting Interface Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: ERC ERC-1202: Voting Interface A general interface for voting on-chain Authors Zainan Victor Zhou (@xinbenlv), Evan (@evbots), Yin Xu (@yingogobot) keywords: address; uint256; vote; voting cache: eips-eip-1202.html plain text: eips-eip-1202.txt item: #201 of 3327 id: eips-eip-1203 author: eips title: eips-eip-1203 date: None words: 1501 flesch: 34 summary: Tracking and Transferring totalSupply Returns the total number of tokens in the specified _class function totalSupply(uint256 _class) public view returns (uint256); balanceOf Returns the number of tokens of a specified _class that the _owner has function balanceOf(address _owner, uint256 _class) public view returns (uint256); transfer Transfer _value tokens of _class to address specified by _to, return true if successful function transfer(address _to, uint256 _class, uint256 _value) public returns (bool); approve Grant _spender the right to transfer _value tokens of _class, return true if successful function approve(address _spender, uint256 _class, uint256 _value) public returns (bool); allowance Return the number of tokens of _class that _spender is authorized to transfer on the behalf of _owner function allowance(address _owner, address _spender, uint256 _class) public view returns (uint256); transferFrom Transfer _value tokens of _class from address specified by _from to address specified by _to as previously approved, return true if successful function transferFrom(address _from, address _to, uint256 _class, uint256 _value) public returns (bool); Transfer Triggered when tokens are transferred or created, including zero value transfers event Transfer(address indexed _from, address indexed _to, uint256 _class, uint256 _value); Approval Triggered on successful approve event Approval(address indexed _owner, address indexed _spender, uint256 _class, uint256 _value); Conversion and Dilution fullyDilutedTotalSupply Return the total token supply as if all converted to the lowest common denominator class function fullyDilutedTotalSupply() public view returns (uint256); fullyDilutedBalanceOf Return the total token owned by _owner as if all converted to the lowest common denominator class function fullyDilutedBalanceOf(address _owner) public view returns (uint256); fullyDilutedAllowance Return the total token _spender is authorized to transfer on behalf of _owner as if all converted to the lowest common denominator class function fullyDilutedAllowance(address _owner, address _spender) public view returns (uint256); convert Convert _value of _fromClass to _toClass, return true if successful function convert(uint256 _fromClass, uint256 _toClass, uint256 _value) public returns (bool); Conversion Triggered on successful convert event Conversion(uint256 indexed _fromClass, uint256 indexed _toClass, uint256 _value); Rationale This standard purposely extends ERC-20 Token Standard so that new MCTs following or existing ERC-20 tokens extending this standard are fully compatible with current wallets and exchanges. Specification contract ERC20 { function totalSupply() public view returns (uint256); function balanceOf(address _owner) public view returns (uint256); function transfer(address _to, uint256 _value) public returns (bool); function approve(address _spender, uint256 _value) public returns (bool); function allowance(address _owner, address _spender) public view returns (uint256); function transferFrom(address _from, address _to, uint256 _value) public returns (bool); event Transfer(address indexed _from, address indexed _to, uint256 _value); event Approval(address indexed _owner, address indexed _spender, uint256 _value); } contract ERC1203 is ERC20 { function totalSupply(uint256 _class) public view returns (uint256); function balanceOf(address _owner, uint256 _class) public view returns (uint256); function transfer(address _to, uint256 _class, uint256 _value) public returns (bool); function approve(address _spender, uint256 _class, uint256 _value) public returns (bool); function allowance(address _owner, address _spender, uint256 _class) public view returns (uint256); function transferFrom(address _from, address _to, uint256 _class, uint256 _value) public returns (bool); function fullyDilutedTotalSupply() public view returns (uint256); keywords: function; returns; uint256 cache: eips-eip-1203.html plain text: eips-eip-1203.txt item: #202 of 3327 id: eips-eip-1207 author: eips title: eips-eip-1207 date: None words: 935 flesch: 23 summary: However, in some case, the user wants to delegate other client smart contracts to access and operate their data or assets in the resource smart contract. userAuth; Required - userAuth maps (authorizer address, grantee contract address) pair to the user’s authorization AuthInfo object callableFuncNames string keywords: client; contract; success cache: eips-eip-1207.html plain text: eips-eip-1207.txt item: #203 of 3327 id: eips-eip-1227 author: eips title: eips-eip-1227 date: None words: 777 flesch: 47 summary: Furthermore, block rewards will be adjusted to a base of 5 ETH, uncle and nephew rewards will be adjusted accordingly. This is the existing pre-Byzantium formula for uncle rewards, simply adjusted with new_block_reward. keywords: block; difficulty cache: eips-eip-1227.html plain text: eips-eip-1227.txt item: #204 of 3327 id: eips-eip-1234 author: eips title: eips-eip-1234 date: None words: 662 flesch: 44 summary: Furthermore, block rewards will be adjusted to a base of 2 ETH, uncle and nephew rewards will be adjusted accordingly. This is the existing pre-Constantinople formula for uncle rewards, simply adjusted with new_block_reward. keywords: block; difficulty cache: eips-eip-1234.html plain text: eips-eip-1234.txt item: #205 of 3327 id: eips-eip-1240 author: eips title: eips-eip-1240 date: None words: 493 flesch: 39 summary: Motivation The difficulty bomb operates under the assumption that miners decide what code economic participants are running, rather than economic participants deciding for themselves. Citation Please cite this document as: Micah Zoltu (@MicahZoltu), EIP-1240: Remove Difficulty Bomb [DRAFT], Ethereum Improvement Proposals, no. 1240, July 2018. keywords: difficulty; ethereum cache: eips-eip-1240.html plain text: eips-eip-1240.txt item: #206 of 3327 id: eips-eip-1261 author: eips title: eips-eip-1261 date: None words: 4064 flesch: 55 summary: /// Doesn't emit when a new membership is created and data is assigned. event ModifiedAttributes(address indexed _to, uint attributeIndex, uint attributeValueIndex); /// @notice Adds a new attribute (key, value) pair to the set of pre-existing attributes. function addAttributeSet(bytes32 _name, bytes32[] calldata values) external; /// @notice Modifies the attribute value of a specific attribute for a given `_to` address. keywords: @dev; address; attribute; contract; function; interface; membership; owner; token cache: eips-eip-1261.html plain text: eips-eip-1261.txt item: #207 of 3327 id: eips-eip-1271 author: eips title: eips-eip-1271 date: None words: 1135 flesch: 34 summary: Applications wanting to support contract signatures should call this method if the signer is a contract. Prevent signer from being 0x0 require( signer != address(0x0), SignatureValidator#recoverSigner: INVALID_SIGNER ); return signer; } Example implementation of a contract calling the isValidSignature() function on an external signing contract ; function callERC1271isValidSignature( address _addr, bytes32 _hash, bytes calldata _signature ) external view { bytes4 result = IERC1271Wallet(_addr).isValidSignature(_hash, _signature); require(result == 0x1626ba7e, INVALID_SIGNATURE); } Security Considerations Since there are no gas-limit expected for calling the isValidSignature() function, it is possible that some implementation will consume a large amount of gas. keywords: contract; signature cache: eips-eip-1271.html plain text: eips-eip-1271.txt item: #208 of 3327 id: eips-eip-1276 author: eips title: eips-eip-1276 date: None words: 761 flesch: 37 summary: Furthermore, block rewards will be adjusted to a base of 2 ETH, uncle and nephew rewards will be adjusted accordingly. Core EIP-1276: Eliminate Difficulty Bomb and Adjust Block Reward on Constantinople Shift Authors EOS Classic (@eosclassicteam) Created 2018-07-31 Discussion Link https://ethereum-magicians.org/t/eip-1276-eliminate-difficulty-bomb-and-adjust-block-reward-on-constantinople-shift/908 Table of Contents Simple Summary Abstract Motivation Specification Rationale Backwards Compatibility Test Cases Implementation Copyright Simple Summary The average block times are increasing due to the factor of difficulty logic well known as difficulty bomb. keywords: block; difficulty cache: eips-eip-1276.html plain text: eips-eip-1276.txt item: #209 of 3327 id: eips-eip-1283 author: eips title: eips-eip-1283 date: None words: 2413 flesch: 77 summary: State Transition Below is a graph (by @Arachnid) showing possible state transition of gas costs. Regarding SSTORE gas cost and refunds, see Appendix for proofs of properties that this EIP satisfies. keywords: case; cost; gas; value cache: eips-eip-1283.html plain text: eips-eip-1283.txt item: #210 of 3327 id: eips-eip-1285 author: eips title: eips-eip-1285 date: None words: 580 flesch: 47 summary: This pattern is very useful for saving gas per deployment (as Proxy contracts are very lean) and it opens the ability to experiment with upgradability of contracts. By slightly increasing the gas units given in the stipend we allow proxy contracts have proper fallback logic without increasing the attack surface of the calling contract. keywords: contract; gas cache: eips-eip-1285.html plain text: eips-eip-1285.txt item: #211 of 3327 id: eips-eip-1295 author: eips title: eips-eip-1295 date: None words: 1274 flesch: 38 summary: With total year to date block rewards totaling approximately 3,730,000 ETH, the network has paid an additional 17pct in Uncle rewards. Furthermore, Uncle rewards will be adjusted and Nephew rewards will be removed to eliminate excess ancillary ETH issuance. keywords: eth; ethereum; uncle cache: eips-eip-1295.html plain text: eips-eip-1295.txt item: #212 of 3327 id: eips-eip-1319 author: eips title: eips-eip-1319 date: None words: 1251 flesch: 41 summary: Backwards Compatibility No existing standard exists for package registries. Created 2018-08-13 Discussion Link https://github.com/ethereum/EIPs/issues/1319 Table of Contents Simple Summary Abstract Motivation Specification Examples Write API Specification Events Read API Specification Rationale Backwards Compatibility Implementation Copyright Simple Summary A standard interface for smart contract package registries. keywords: package; registry; release; string cache: eips-eip-1319.html plain text: eips-eip-1319.txt item: #213 of 3327 id: eips-eip-1328 author: eips title: eips-eip-1328 date: None words: 442 flesch: 28 summary: Citation Please cite this document as: ligi (@ligi), Pedro Gomes (@pedrouid), ERC-1328: WalletConnect URI Format [DRAFT], Ethereum Improvement Proposals, no. 1328, August 2018. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: uri cache: eips-eip-1328.html plain text: eips-eip-1328.txt item: #214 of 3327 id: eips-eip-1337 author: eips title: eips-eip-1337 date: None words: 1441 flesch: 34 summary: * @param bytes subscriptionHash is the identifier of the customer's subscription with its relevant details. * @return status is the enumerated status of the current subscription, 0 expired, 1 active, 2 paused, 3 cancelled **/ function getSubscriptionStatus( uint256 subscriptionHash ) public view returns ( uint256 status, uint256 nextWithdraw ) keywords: @param; address; uint256 cache: eips-eip-1337.html plain text: eips-eip-1337.txt item: #215 of 3327 id: eips-eip-1344 author: eips title: eips-eip-1344 date: None words: 891 flesch: 51 summary: Chain ID is a 256-bit value. Currently, there is no specification for how chain ID is set for a particular network, relying on choices made manually by the client implementers and the chain community. keywords: chain; opcode cache: eips-eip-1344.html plain text: eips-eip-1344.txt item: #216 of 3327 id: eips-eip-1352 author: eips title: eips-eip-1352 date: None words: 261 flesch: 26 summary: Citation Please cite this document as: Alex Beregszaszi (@axic), EIP-1352: Specify restricted address range for precompiles/system contracts [DRAFT], Ethereum Improvement Proposals, no. 1352, July 2018. EIP-1352: Specify restricted address range for precompiles/system contracts Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-1352: Specify restricted address range for precompiles/system contracts Authors Alex Beregszaszi (@axic) keywords: address cache: eips-eip-1352.html plain text: eips-eip-1352.txt item: #217 of 3327 id: eips-eip-1355 author: eips title: eips-eip-1355 date: None words: 374 flesch: 44 summary: Citation Please cite this document as: Paweł Bylica (@chfast), Jean M. Cyr (@jean-m-cyr), EIP-1355: Ethash 1a [DRAFT], Ethereum Improvement Proposals, no. 1355, August 2018. EIP-1355: Ethash 1a Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🛑 Withdrawn Standards Track: Core EIP-1355: Ethash 1a Authors Paweł Bylica (@chfast), Jean M. Cyr keywords: ethash; ethereum cache: eips-eip-1355.html plain text: eips-eip-1355.txt item: #218 of 3327 id: eips-eip-1363 author: eips title: eips-eip-1363 date: None words: 1315 flesch: 43 summary: * @param spender address The address which will spend the funds * @param value uint256 The amount of tokens to be spent * @param data bytes Additional data with no specified format, sent in call to `spender` */ function approveAndCall(address spender, uint256 value, bytes memory data) external returns (bool); } interface ERC20 { function totalSupply() external view returns (uint256); function balanceOf(address account) external view returns (uint256); function transfer(address recipient, uint256 amount) external returns (bool); function transferFrom(address sender, address recipient, uint256 amount) external returns (bool); function allowance(address owner, address spender) external view returns (uint256); function approve(address spender, uint256 amount) external returns (bool); ** * @notice Transfer tokens from one address to another and then call `onTransferReceived` on receiver * @param from address The address which you want to send tokens from * @param to address The address which you want to transfer to * @param value uint256 The amount of tokens to be transferred * @return true unless throwing */ function transferFromAndCall(address from, address to, uint256 value) external returns (bool); / keywords: @param; address; uint256 cache: eips-eip-1363.html plain text: eips-eip-1363.txt item: #219 of 3327 id: eips-eip-137 author: eips title: eips-eip-137 date: None words: 2366 flesch: 39 summary: Changes to an address MUST trigger the following event: event AddrChanged(bytes32 indexed node, address a); Appendix A: Registry Implementation contract ENS { struct Record { address owner; address resolver; uint64 ttl; } mapping(bytes32=>Record) records; event NewOwner(bytes32 indexed node, bytes32 indexed label, address owner); event Transfer(bytes32 indexed node, address owner); event NewResolver(bytes32 indexed node, address resolver); modifier only_owner(bytes32 node) { if(records[node].owner ! function setResolver(bytes32 node, address resolver); keywords: address; function; node; owner; resolver cache: eips-eip-137.html plain text: eips-eip-137.txt item: #220 of 3327 id: eips-eip-1380 author: eips title: eips-eip-1380 date: None words: 605 flesch: 51 summary: With EIP150 contract (and language) developers had a lesson that relying on strict gas costs is not feasible as costs may change. EIP-1380: Reduced gas cost for call to self Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-1380: Reduced gas cost for call to self Authors Alex Beregszaszi (@axic), keywords: contract; cost cache: eips-eip-1380.html plain text: eips-eip-1380.txt item: #221 of 3327 id: eips-eip-1386 author: eips title: eips-eip-1386 date: None words: 704 flesch: 43 summary: In our draft implementation we include functions to hold cryptographic attestations, change the issuing contracts of attestations, revoke attestations and verify the authenticity of a cryptographic attestation. Purpose This ERC provides an interface for attestation issuers to manage their attestation signing keys and the attestations that are issued off chain for actions such as revocation and validation. keywords: attestation; contract cache: eips-eip-1386.html plain text: eips-eip-1386.txt item: #222 of 3327 id: eips-eip-1387 author: eips title: eips-eip-1387 date: None words: 331 flesch: 30 summary: ERC-1387: Merkle Tree Attestations with Privacy enabled Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-1387: Merkle Tree Attestations with Privacy enabled Authors Weiwu Zhang , James Sangalli  Created 2018-09-08 Discussion Link https://github.com/ethereum/EIPs/issues/1387 Table of Contents Introduction Draft implementation Relevant implementation examples Related ERC’s Introduction It’s often needed that an Ethereum smart contract must verify a claim (I live in Australia) attested by a valid attester. [] merklePath; bool valid; uint8 v; bytes32 r; bytes32 s; address attester; address recipient; bytes32 salt; bytes32 key; bytes32 val; } function validate(Attestation attestation) public returns(bool); } Relevant implementation examples Here is an example implementation of the MerkleTreeAttestationInterface Here is an example service which would use such a merkle tree attestation Related ERC’s #1388 #1386 Citation Please cite this document as: Weiwu Zhang , James Sangalli , ERC-1387: Merkle Tree Attestations with Privacy enabled [DRAFT], Ethereum Improvement Proposals, no. 1387, September 2018. keywords: ethereum; merkle cache: eips-eip-1387.html plain text: eips-eip-1387.txt item: #223 of 3327 id: eips-eip-1388 author: eips title: eips-eip-1388 date: None words: 687 flesch: 45 summary: */ function createList(List list) public; /* replace list manager's key with the new key */ function replaceListIndex(List list, address manager) public returns(bool); } Click here to see an example implementation of this ERC Related ERC’s #1387 #1386 Citation Please cite this document as: Weiwu Zhang , James Sangalli , ERC-1388: Attestation Issuers Management List Purpose This ERC provides a smart contract interface for anyone to manage a list of attestation issuers. keywords: attestation; list cache: eips-eip-1388.html plain text: eips-eip-1388.txt item: #224 of 3327 id: eips-eip-140 author: eips title: eips-eip-140 date: None words: 563 flesch: 56 summary: EIP-140: REVERT instruction Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: Core EIP-140: REVERT instruction Authors Alex Beregszaszi (@axic), Nikolai Mushegian  Created 2017-02-06 Table of Contents Simple Summary Abstract Motivation Specification Backwards Compatibility Test Cases Copyright Simple Summary The REVERT instruction provides a way to stop execution and revert state changes, without consuming all provided gas and with the ability to return a reason. Citation Please cite this document as: Alex Beregszaszi (@axic), Nikolai Mushegian , EIP-140: REVERT instruction, Ethereum Improvement Proposals, no. 140, February 2017. keywords: instruction; revert cache: eips-eip-140.html plain text: eips-eip-140.txt item: #225 of 3327 id: eips-eip-141 author: eips title: eips-eip-141 date: None words: 156 flesch: 25 summary: Citation Please cite this document as: Alex Beregszaszi (@axic), EIP-141: Designated invalid EVM instruction, Ethereum Improvement Proposals, no. 141, February 2017. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: instruction cache: eips-eip-141.html plain text: eips-eip-141.txt item: #226 of 3327 id: eips-eip-1417 author: eips title: eips-eip-1417 date: None words: 3561 flesch: 50 summary: /// @dev addresses list can be used along with IERC1261 interface to define the logic inside `canVote()` function /// @return the list of addresses of entities function getProtocolAddresses() external view returns (address[]); /// @notice gets the vote weight against all proposals /// @dev limit the proposal count to 32 (for practical reasons), loop and generate the vote tally list /// @return the list of vote weights against all proposals function getVoteTallies() external view returns (uint[]); /// @notice gets the no. of people who voted against all proposals /// @dev limit the proposal count to 32 (for practical reasons), loop and generate the vote count list /// @return the list of voter count against all proposals function getVoterCounts() external view returns (uint[]); /// @notice For single proposal polls, returns the total voterbase count. For multi proposal polls, returns the total vote weight against all proposals /// this is used to calculate the percentages for each proposal /// @dev limit the proposal count to 32 (for practical reasons), loop and generate the voter base denominator /// @return an integer which specifies the above mentioned amount function getVoterBaseDenominator() external view returns (uint); } Caveats The 0.4.24 Solidity interface grammar is not expressive enough to document the ERC-1417 standard. keywords: function; poll; proposal; standard; vote; voting; weight cache: eips-eip-1417.html plain text: eips-eip-1417.txt item: #227 of 3327 id: eips-eip-1418 author: eips title: eips-eip-1418 date: None words: 1488 flesch: 58 summary: Calculating σ[account]_storageWord for existing accounts DRAFT… It is not an acceptable upgrade if on the fork block it is necessary for only archive nodes to participate which know the full storage amount for each account. New state variables (per account) σ[a]_rent – an amount of value, in Wei, this is a signed value σ[a]_storageWords – number of words in storage New constants RENT_WORD_COST – The rent cost, in Wei, paid for each word-block RENT_ACCOUNT_COST – The rent cost, in Wei, paid for each account-block FORK_BLOCK – When implementation starts New opcodes RENTBALANCE(address) – G_BALANCE – Similar to BALANCE This returns the logical σ[a]_rent value which is defined to reduce each block. keywords: account; rent; storage; value cache: eips-eip-1418.html plain text: eips-eip-1418.txt item: #228 of 3327 id: eips-eip-1438 author: eips title: eips-eip-1438 date: None words: 766 flesch: 34 summary: ERC20 interface contract ERC20Interface { function totalSupply() public constant returns (uint); function balanceOf(address tokenOwner) public constant returns (uint balance); function allowance(address tokenOwner, address spender) public constant returns (uint remaining); function transfer(address to, uint tokens) public returns (bool success); function approve(address spender, uint tokens) public returns (bool success); function transferFrom(address from, address to, uint tokens) public returns (bool success); erc20 interface //------------------------------------------------------- function balanceOf(address _erc20) public constant returns (uint balance) { if(_erc20==address(0)) return address(this).balance; return _ERC20Interface(_erc20).balanceOf(this); } function transfer(address _erc20, address _to, uint _tokens) onlyOwner public returns (bool success) { require(balanceOf(_erc20)>=_tokens); if(_erc20==address(0)) _to.transfer(_tokens); else return _ERC20Interface(_erc20).transfer(_to,_tokens); return true; } function approve(address _erc20, address _spender, uint _tokens) onlyOwner public returns (bool success) { require(_erc20 != address(0)); return _ERC20Interface(_erc20).approve(_spender,_tokens); } //------------------------------------------------------- // pay interface //------------------------------------------------------- function pay(address _store, uint _tokens, uint256[] _options) onlyOwner public { address erc20 = _ApproveAndCallFallBack(_store).erc20(); address spender = _ApproveAndCallFallBack(_store).spender(); if(erc20 == address(0)) keywords: public; tokens; uint cache: eips-eip-1438.html plain text: eips-eip-1438.txt item: #229 of 3327 id: eips-eip-1444 author: eips title: eips-eip-1444 date: None words: 1937 flesch: 46 summary: interface Localization { function textFor(bytes32 _code) external view returns (string _text); } textFor Fetches the localized text representation. external view returns (string _text); LocalizationPreferences A proxy contract that allows users to set their preferred Localization. keywords: localization; string; text cache: eips-eip-1444.html plain text: eips-eip-1444.txt item: #230 of 3327 id: eips-eip-145 author: eips title: eips-eip-145 date: None words: 842 flesch: 59 summary: 0x1d: SAR (arithmetic shift right) Rationale Backwards Compatibility Test Cases SHL (shift left) SHR (logical shift right) SAR (arithmetic shift right) Implementation Tests Copyright Abstract Native bitwise shifting instructions are introduced, which are more efficient processing wise on the host and are cheaper to use by a contract. 0x1d: SAR (arithmetic shift right) The SAR instruction (arithmetic shift right) pops 2 values from the stack, first arg1 and then arg2, and pushes on the stack arg2 shifted to the right by arg1 number of bits with sign extension. keywords: push; sar; shift cache: eips-eip-145.html plain text: eips-eip-145.txt item: #231 of 3327 id: eips-eip-1450 author: eips title: eips-eip-1450 date: None words: 2712 flesch: 33 summary: ERC-1450: ERC-1450 A compatible security token for issuing and trading SEC-compliant securities Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-1450: ERC-1450 A compatible security token for issuing and trading SEC-compliant securities Authors John Shiple (@johnshiple), Howard Marks , David Zhang  Created 2018-09-25 Discussion Link https://ethereum-magicians.org/t/erc-proposal-ldgrtoken-a-compatible-security-token-for-issuing-and-trading-sec-compliant-securities/1468 Table of Contents ERC-1450 - A compatible security token for issuing and trading SEC-compliant securities Simple Summary Abstract Motivation Specification ERC-1450 Issuers and RTAs ERC-20 Extension Securities Exchange Commission Requirements Managing Investor Information Issuers who lost access to their address or private keys Registered Transfer Agents who lost access to their address or private keys Handling Investors (security owners) who lost access to their addresses or private keys Rationale Backwards Compatibility Test Cases Implementations Copyright Waiver ERC-1450 - A compatible security token for issuing and trading SEC-compliant securities Simple Summary ERC-1450 is an ERC-20 compatible token that enables issuing tokens representing securities that are required to comply with one or more of the following Securities Act Regulations: Handling Investors (security owners) who lost access to their addresses or private keys Investors may “lose” their credentials for a number of reasons: they simply “lost” their credentials, they were hacked or the victim of fraud, they committed securities-related fraud, or a life event (like death) occurred. keywords: address; erc-1450; issuer; securities cache: eips-eip-1450.html plain text: eips-eip-1450.txt item: #232 of 3327 id: eips-eip-1459 author: eips title: eips-eip-1459 date: None words: 1293 flesch: 57 summary: We would like to maintain larger node lists containing hundreds of nodes, and update them regularly. Entries of the merkle tree are contained in DNS TXT records. keywords: dns; list; node; root cache: eips-eip-1459.html plain text: eips-eip-1459.txt item: #233 of 3327 id: eips-eip-1462 author: eips title: eips-eip-1462 date: None words: 1605 flesch: 41 summary: For ERC-20 based tokens, It is required that transfer function must be overridden with logic that checks the corresponding checkTransferAllowed return status code. It is not required to use documentation functions, they are optional and provided as a part of a legal framework. keywords: function; status; token; uint256 cache: eips-eip-1462.html plain text: eips-eip-1462.txt item: #234 of 3327 id: eips-eip-1470 author: eips title: eips-eip-1470 date: None words: 1134 flesch: 48 summary: The CWE uses Relationships to link SWC smart contract weakness variants to existing Base or Class CWE types. Relationships are used to provide context on how SWCs are linked to the wider group of software security weaknesses and to be able to generate useful visualisations and insights through issue data sets. keywords: contract; security; swc; weakness cache: eips-eip-1470.html plain text: eips-eip-1470.txt item: #235 of 3327 id: eips-eip-1474 author: eips title: eips-eip-1474 date: None words: 6354 flesch: -10 summary: Examples Quantity values: Value Valid Reason 0x invalid empty not a valid quantity 0x0 valid interpreted as a quantity of zero 0x00 invalid leading zeroes not allowed 0x41 valid interpreted as a quantity of 65 0x400 valid interpreted as a quantity of 1024 0x0400 invalid leading zeroes not allowed ff invalid values must be prefixed Block Identifier The RPC methods below take a default block identifier as a parameter. eth_getBalance eth_getStorageAt eth_getTransactionCount eth_getCode eth_call eth_getProof Since there is no way to clearly distinguish between a Data parameter and a Quantity parameter, EIP-1898 provides a format to specify a block either using the block hash or block number. Parameters # Type Description 1 {Data} hash of a transaction Returns {null|object} - null if no transaction is found, otherwise a transaction receipt object with the following members: {Data} blockHash - hash of block containing this transaction {Data} contractAddress - address of new contract or null if no contract was created {Data} from - transaction sender {Data} logsBloom - logs bloom filter {Data} to - transaction recipient or null if deploying a contract {Data} transactionHash - hash of this transaction {Quantity} blockNumber - number of block containing this transaction {Quantity} cumulativeGasUsed - gas used by this and all preceding transactions in this block {Quantity} gasUsed - gas used by this transaction {Quantity} status - 1 if this transaction was successful or 0 if it failed {Quantity} transactionIndex - index of this transaction in the block {Array} logs - list of log objects generated by this transaction Example # Request curl -X POST --data '{ id: 1337, jsonrpc: 2.0, method: eth_getTransactionReceipt, params: [0xb903239f8543d04b5dc1ba6579132b143087c68db1b2168786408fcbce568238] }' # Response { id: 1337, jsonrpc: 2.0, result: { blockHash: '0xc6ef2fc5426d6ad6fd9e2a26abeab0aa2411b7ab17f30a99d3cb96aed1d1055b', blockNumber: '0xb', contractAddress: '0xb60e8dd61c5d32be8058bb8eb970870f07233155', cumulativeGasUsed: '0x33bc', gasUsed: '0x4dc', logs: [], logsBloom: 0x00...0, status: 0x1, transactionHash: '0xb903239f8543d04b5dc1ba6579132b143087c68db1b2168786408fcbce568238', transactionIndex: '0x1' } } eth_getUncleByBlockHashAndIndex Description Returns information about an uncle specified by block hash and uncle index position Parameters # Type Description 1 {Data} hash of a block 2 {Quantity} index of uncle Returns {null|object} - null if no block or uncle is found, otherwise an uncle object with the following members: {Data} extraData - “extra data” field of this block {Data} hash - block hash or null if pending {Data} logsBloom - logs bloom filter or null if pending {Data} miner - address that received this block’s mining rewards {Data} nonce - proof-of-work hash or null if pending {Data} parentHash - parent block hash {Data} receiptsRoot -root of the this block’s receipts trie {Data} sha3Uncles - SHA3 of the uncles data in this block {Data} stateRoot - root of this block’s final state trie {Data} transactionsRoot - root of this block’s transaction trie {Quantity} difficulty - difficulty for this block {Quantity} gasLimit - maximum gas allowed in this block {Quantity} gasUsed - total used gas by all transactions in this block {Quantity} number - block number or null if pending {Quantity} size - size of this block in bytes {Quantity} timestamp - unix timestamp of when this block was collated {Quantity} totalDifficulty - total difficulty of the chain until this block {Array} uncles - list of uncle hashes Example # Request curl -X POST --data '{ id: 1337, jsonrpc: 2.0, method: eth_getUncleByBlockHashAndIndex, params: [0xc6ef2fc5426d6ad6fd9e2a26abeab0aa2411b7ab17f30a99d3cb96aed1d1055b, 0x0] }' # Response { id: 1337, jsonrpc: 2.0, result: { difficulty: 0x027f07, extraData: 0x0000000000000000000000000000000000000000000000000000000000000000, gasLimit: 0x9f759, gasUsed: 0x9f759, hash: 0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331, logsBloom: 0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331, miner: 0x4e65fda2159562a496f9f3522f89122a3088497a, nonce: 0xe04d296d2460cfb8472af2c5fd05b5a214109c25688d3704aed5484f9a7792f2, number: 0x1b4, parentHash: 0x9646252be9520f6e71339a8df9c55e4d7619deeb018d2a3f2d21fc165dde5eb5, sha3Uncles: 0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347, size: 0x027f07, stateRoot: 0xd5855eb08b3387c0af375e9cdb6acfc05eb8f519e419b874b6ff2ffda7ed1dff, timestamp: 0x54e34e8e totalDifficulty: 0x027f07, transactionsRoot: 0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421, uncles: [] } } eth_getUncleByBlockNumberAndIndex Description Returns information about an uncle specified by block number and uncle index position Parameters # Type Description 1 {Quantity|string} block number, or one of latest, earliest or pending 2 {Quantity} index of uncle Returns {null|object} - null if no block or uncle is found, otherwise an uncle object with the following members: {Data} extraData - “extra data” field of this block {Data} hash - block hash or null if pending {Data} logsBloom - logs bloom filter or null if pending {Data} miner - address that received this block’s mining rewards {Data} nonce - proof-of-work hash or null if pending {Data} parentHash - parent block hash {Data} receiptsRoot -root of the this block’s receipts trie {Data} sha3Uncles - SHA3 of the uncles data in this block {Data} stateRoot - root of this block’s final state trie {Data} transactionsRoot - root of this block’s transaction trie {Quantity} difficulty - difficulty for this block {Quantity} gasLimit - maximum gas allowed in this block {Quantity} gasUsed - total used gas by all transactions in this block {Quantity} number - block number or null if pending {Quantity} size - size of this block in bytes {Quantity} timestamp - unix timestamp of when this block was collated {Quantity} totalDifficulty - total difficulty of the chain until this block {Array} uncles - list of uncle hashes Example # Request curl -X POST --data '{ id: 1337, jsonrpc: 2.0, method: eth_getUncleByBlockNumberAndIndex, params: [0x29c, 0x0] }' # Response { id: 1337, jsonrpc: 2.0, result: { difficulty: 0x027f07, extraData: 0x0000000000000000000000000000000000000000000000000000000000000000, gasLimit: 0x9f759, gasUsed: 0x9f759, hash: 0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331, logsBloom: 0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331, miner: 0x4e65fda2159562a496f9f3522f89122a3088497a, nonce: 0xe04d296d2460cfb8472af2c5fd05b5a214109c25688d3704aed5484f9a7792f2, number: 0x1b4, parentHash: 0x9646252be9520f6e71339a8df9c55e4d7619deeb018d2a3f2d21fc165dde5eb5, sha3Uncles: 0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347, size: 0x027f07, stateRoot: 0xd5855eb08b3387c0af375e9cdb6acfc05eb8f519e419b874b6ff2ffda7ed1dff, timestamp: 0x54e34e8e totalDifficulty: 0x027f07, transactionsRoot: 0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421, uncles: [] } } eth_getUncleCountByBlockHash Description Returns the number of uncles in a block specified by block hash Parameters # Type Description 1 {Data} hash of a block Returns {Quantity} - number of uncles in the specified block Example # Request curl -X POST --data '{ id: 1337, jsonrpc: 2.0, method: eth_getUncleCountByBlockHash, params: [0xc94770007dda54cF92009BFF0dE90c06F603a09f] }' # Response { id: 1337, jsonrpc: 2.0, result: 0xc } eth_getUncleCountByBlockNumber Description Returns the number of uncles in a block specified by block number Parameters # Type Description 1 {Quantity|string} block number, or one of latest, earliest or pending Returns {Quantity} - number of uncles in the specified block Example # Request curl -X POST --data '{ id: 1337, jsonrpc: 2.0, method: eth_getUncleCountByBlockNumber, params: [0xe8] }' # Response { id: 1337, jsonrpc: 2.0, result: 0x1 } eth_getWork Description Returns a list containing relevant information for proof-of-work Parameters none Returns {Data[]} - array with the following items: {Data} - current block header pow-hash {Data} - seed hash used for the DAG {Data} - boundary condition (“target”), 2^256 / difficulty Example # Request curl -X POST --data '{ id: 1337, jsonrpc: 2.0, method: eth_getWork, params: [] }' # Response { id: 1337, jsonrpc: 2.0, result: [ 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef, 0x5EED00000000000000000000000000005EED0000000000000000000000000000, 0xd1ff1c01710000000000000000000000d1ff1c01710000000000000000000000 ] } eth_hashrate Description Returns the number of hashes-per-second this node is mining at Parameters (none) Returns {Quantity} - number of hashes-per-second Example # Request curl -X POST --data '{ id: 1337, jsonrpc: 2.0, method: eth_hashrate, params: [] }' # Response { id: 1337, jsonrpc: 2.0, result: 0x38a } eth_mining Description Determines if this client is mining new blocks Parameters (none) Returns {boolean} - true if this client is mining or false if it is not mining Example # Request curl -X POST --data '{ id: 1337, jsonrpc: 2.0, method: eth_mining, params: [] }' # Response { id: 1337, jsonrpc: 2.0, result: true } eth_newBlockFilter Description Creates a filter to listen for new blocks that can be used with eth_getFilterChanges Parameters none Returns {Quantity} - ID of the newly-created filter that can be used with eth_getFilterChanges Example # Request curl -X POST --data '{ id: 1337 jsonrpc: 2.0, method: eth_newBlockFilter, params: [] }' # Response { id: 1337, jsonrpc: 2.0, result: 0x1 } eth_newFilter Description Creates a filter to listen for specific state changes that can then be used with eth_getFilterChanges Parameters # Type Description 1 {object} @property {Quantity|string} keywords: block; data; description; hash; jsonrpc; method; quantity; returns; transaction cache: eips-eip-1474.html plain text: eips-eip-1474.txt item: #236 of 3327 id: eips-eip-1482 author: eips title: eips-eip-1482 date: None words: 400 flesch: 46 summary: Rationale Both Geth and Parity reject blocks with timestamp more than 15 seconds in the future. For the purpose of block validation, it must be greater than the previous block’s timestamp, and no more than 15 seconds greater than system time. keywords: block; timestamp cache: eips-eip-1482.html plain text: eips-eip-1482.txt item: #237 of 3327 id: eips-eip-1484 author: eips title: eips-eip-1484 date: None words: 3670 flesch: 26 summary: Provider Management While the protocol allows users to directly call identity management functions, it also aims to be more robust and future-proof by allowing Providers, typically smart contracts, to perform identity management functions on a user’s behalf. This solves identity management and interoperability challenges by enabling any identity-driven application to leverage an un-opinionated identity management protocol. keywords: address; ein; event; function; identity; indexed; uint cache: eips-eip-1484.html plain text: eips-eip-1484.txt item: #238 of 3327 id: eips-eip-1485 author: eips title: eips-eip-1485 date: None words: 1312 flesch: 56 summary: And You can execute it fnvtest F(00,00)::VEC(0, 0, ffffffff, 0):: FNV :00000000, DF=00000000(00) DS(00000000), FNV1 :00000000, DF=00000000(00) DS(00000000), FNV1a:117697cd, DF=117697cd(17) DS(117697cd), FNV1c:1210d00f, DF=127f8dbf(20) DS(11a1725f), F___RC=efe1b9c4, DF:efe1b9c4(19) , F1__RC=deb68dfe, DF:deb68dfe(22) , F1A_RC=99bad28b, DF:99bad28b(17) , F1C_RC=e29fa497, DF:e29fa497(18) F(00,01)::VEC(0, 1, ffffffff, 0):: FNV :00000001, DF=00000001(01) DS(00000001), FNV1 :01000193, DF=01000193(06) DS(01000193), FNV1a:1076963a, DF=010001f7(09) DS(01000193), FNV1c:1110ce7c, DF=03001e73(11) DS(01000193), F___RC=fefffe6d, DF:111e47a9(14) , F1__RC=d9fd8597, DF:074b0869(12) , F1A_RC=72c287e0, DF:eb78556b(19) , F1C_RC=6b6991ef, DF:89f63578(17) F(00,02)::VEC(0, 2, ffffffff, 0):: FNV :00000002, DF=00000003(02) DS(00000001), FNV1 :02000326, DF=030002b5(08) DS(01000193), FNV1a:0f7694a7, DF=1f00029d(11) DS(01000193), FNV1c:1410d335, DF=05001d49(09) DS(030004b9), F___RC=d8fd8404, DF:26027a69(13) , F1__RC=9b16d24c, DF:42eb57db(19) , F1A_RC=c17f0ecb, DF:b3bd892b(18) , F1C_RC=a5be8e78, DF:ced71f97(21) F(00,03)::VEC(0, 3, ffffffff, 0):: FNV :00000003, DF=00000001(01) DS(00000001), FNV1 :030004b9, DF=0100079f(10) DS(01000193), FNV1a:0e769314, DF=010007b3(09) DS(01000193), FNV1c:1310d1a2, DF=07000297(09) DS(01000193), F___RC=b2fb099b, DF:6a068d9f(16) , F1__RC=5c301f01, DF:c726cd4d(17) , F1A_RC=94cf402e, DF:55b04ee5(16) , F1C_RC=aea1a025, DF:0b1f2e5d(17) F(00,04)::VEC(0, 4, ffffffff, 0):: FNV :00000004, DF=00000007(03) DS(00000001), FNV1 :0400064c, DF=070002f5(10) DS(01000193), FNV1a:0d769181, DF=03000295(07) DS(01000193), FNV1c:0e10c9c3, DF=1d001861(09) DS(050007df), F___RC=8cf88f32, DF:3e0386a9(14) , F1__RC=1d496bb6, DF:417974b7(17) , F1A_RC=89401d59, DF:1d8f5d77(20) , F1C_RC=e4e96c7c, DF:4a48cc59(13) F(00,05)::VEC(0, 5, ffffffff, 0):: FNV :00000005, DF=00000001(01) DS(00000001), FNV1 :050007df, DF=01000193(06) DS(01000193), FNV1a:0c768fee, DF=01001e6f(11) DS(01000193), FNV1c:0d10c830, DF=030001f3(09) DS(01000193), F___RC=66f614c9, DF:ea0e9bfb(20) , F1__RC=de62b86b, DF:c32bd3dd(19) , F1A_RC=346e222c, DF:bd2e3f75(21) , F1C_RC=502e5f82, DF:b4c733fe(20) F(00,06)::VEC(0, 6, ffffffff, 0):: FNV :00000006, DF=00000003(02) DS(00000001), FNV1 :06000972, DF=03000ead(10) DS(01000193), FNV1a:0b768e5b, DF=070001b5(09) DS(01000193), FNV1c:1010cce9, DF=1d0004d9(10) DS(030004b9), FNV :00000007, DF=00000001(01) DS(00000001), FNV1 :07000b05, DF=01000277(08) DS(01000193), FNV1a:0a768cc8, DF=01000293(06) DS(01000193), FNV1c:0f10cb56, DF=1f0007bf(15) DS(01000193), F___RC=1af11ff7, DF:5a028597(13) , F1__RC=609551d5, DF:ffe954f5(22) , F1A_RC=14293bea, DF:a75f9ecd(21) , F1C_RC=49d34bba, DF:5b92e21e(16) F(00,08)::VEC(0, 8, ffffffff, 0):: FNV :00000008, DF=0000000f(04) DS(00000001), FNV1 :08000c98, DF=0f00079d(12) DS(01000193), FNV1a:09768b35, DF=030007fd(12) DS(01000193), FNV1c:1a10dca7, DF=150017f1(12) DS(0b001151), F___RC=f4eea58e, DF:ee1fba79(21) , F1__RC=21ae9e8a, DF:413bcf5f(19) , F1A_RC=eeebb7a5, DF:fac28c4f(17) , F1C_RC=7da04f47, DF:347304fd(16) F(00,09)::VEC(0, 9, ffffffff, 0):: FNV :00000009, DF=00000001(01) DS(00000001), FNV1 :09000e2b, DF=010002b3(07) DS(01000193), FNV1a:087689a2, DF=01000297(07) DS(01000193), FNV1c:1910db14, DF=030007b3(10) DS(01000193), F___RC=ceec2b25, DF:3a028eab(14) , F1__RC=e2c7eb3f, DF:c36975b5(18) , F1A_RC=54e1aef8, DF:ba0a195d(15) , F1C_RC=d425e1af, DF:a985aee8(16) F(00,0a)::VEC(0, a, ffffffff, 0):: FNV :0000000a, DF=00000003(02) DS(00000001), FNV1 :0a000fbe, DF=03000195(07) DS(01000193), FNV1a:0776880f, DF=0f0001ad(10) DS(01000193), FNV1c:1c10dfcd, DF=050004d9(08) DS(030004b9), F___RC=a8e9b0bc, DF:66059b99(15) , F1__RC=a3e137f4, DF:4126dccb(15) , F1A_RC=213fcd63, DF:75de639b(20) , F1C_RC=7e1d2751, DF:aa38c6fe(18) F(00,0b)::VEC(0, b, ffffffff, 0):: FNV :0000000b, DF=00000001(01) DS(00000001), FNV1 :0b001151, DF=01001eef(12) DS(01000193), FNV1a:0676867c, DF=01000e73(09) DS(01000193), FNV1c:1b10de3a, DF=070001f7(11) DS(01000193), F___RC=82e73653, DF:2a0e86ef(16) , F1__RC=64fa84a9, DF:c71bb35d(19) , F1A_RC=5598ce46, DF:74a70325(14) , F1C_RC=6400c630, DF:1a1de161(14) F(00,0c)::VEC(0, c, ffffffff, 0):: FNV :0000000c, DF=00000007(03) DS(00000001), FNV1 :0c0012e4, DF=070003b5(10) DS(01000193), FNV1a:057684e9, DF=03000295(07) DS(01000193), FNV1c:1610d65b, DF=0d000861(07) DS(050007df), F___RC=5ce4bbea, DF:de038db9(17) , F1__RC=2613d15e, DF:42e955f7(18) , F1A_RC=6a220ff1, DF:3fbac1b7(20) , F1C_RC=6e781da4, DF:0a78db94(15) F(00,0d)::VEC(0, d, ffffffff, 0):: FNV :0000000d, DF=00000001(01) DS(00000001), FNV1 :0d001477, DF=01000693(07) DS(01000193), FNV1a:04768356, DF=010007bf(11) DS(01000193), FNV1c:1510d4c8, DF=03000293(07) DS(01000193), F___RC=36e24181, DF:6a06fa6b(17) , F1__RC=e72d1e13, DF:c13ecf4d(18) , F1A_RC=168d4944, DF:7caf46b5(19) , F1C_RC=65bbcfa1, DF:0bc3d205(13) F(00,0e)::VEC(0, e, ffffffff, 0):: FNV :0000000e, DF=00000003(02) DS(00000001), FNV1 :0e00160a, DF=0300027d(09) DS(01000193), FNV1a:037681c3, DF=07000295(08) DS(01000193), FNV1c:1810d981, DF=0d000d49(09) DS(030004b9), F___RC=10dfc718, DF:263d8699(15) , F1__RC=a8466ac8, DF:4f6b74db(20) , F1A_RC=93e667bf, DF:856b2efb(19) , F1C_RC=76f80ee3, DF:1343c142(11) F(00,0f)::VEC(0, f, ffffffff, 0):: FNV :0000000f, DF=00000001(01) DS(00000001), FNV1 :0f00179d, DF=01000197(07) DS(01000193), FNV1a:02768030, DF=010001f3(08) DS(01000193), FNV1c:1710d7ee, DF=0f000e6f(13) DS(01000193), F___RC=eadd4caf, DF:fa028bb7(17) , F1__RC=695fb77d, DF:c119ddb5(17) , F1A_RC=0f485682, DF:9cae313d(17) , F1C_RC=3667e8dc, DF:409fe63f(18) F(00,10)::VEC(0, 10, ffffffff, 0):: FNV :00000010, DF=0000001f(05) DS(00000001), FNV1 :10001930, DF=1f000ead(13) DS(01000193), FNV1a:01767e9d, DF=0300fead(14) DS(01000193), FNV1c:0210b6df, DF=15006131(09) DS(1500210f), F___RC=c4dad246, DF:2e079ee9(17) , F1__RC=2a790432, DF:4326b34f(16) , F1A_RC=d10adebd, DF:de42883f(16) , F1C_RC=1ce48e12, DF:2a8366ce(15) F(00,01) : is input x,y VEC(0, 1, ffffffff, 0) : keywords: ds(01000193; fnv; fnv1; hash cache: eips-eip-1485.html plain text: eips-eip-1485.txt item: #239 of 3327 id: eips-eip-1491 author: eips title: eips-eip-1491 date: None words: 3126 flesch: 55 summary: Unknown masking // bytes32 constant public DOER = 0x11ff10ff100f03ffff00ffffffffffffffff90EBAC34FC40EAC30FC9CB464A2E56; bytes32 constant public KEY_CERTIFICATION = 0x01ffffffffffffff << 192; // “C” Key Certification bytes32 constant public SIGN_DATA = 0x02ffffffffffffff << 192; bytes32 constant public ISSUER = 0xffffffff001fffff << 192; // EDGES MASKING TABLE Clearance internal TRUST = Clearance({ Zero: 0x01ff << 192, keywords: @dev; @param; agent; bytes32; ecosystem; flag; function; public cache: eips-eip-1491.html plain text: eips-eip-1491.txt item: #240 of 3327 id: eips-eip-150 author: eips title: eips-eip-150 date: None words: 815 flesch: 56 summary: If a call asks for more gas than the maximum allowed amount (i.e. the total amount of gas remaining in the parent after subtracting the gas cost of the call and memory expansion), do not return an OOG error; instead, if a call asks for more gas than all but one 64th of the maximum allowed amount, call with all but one 64th of the maximum allowed amount of gas (this is equivalent to a version of EIP-901 plus EIP-1142). EIP-150: Gas cost changes for IO-heavy operations Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: Core EIP-150: Gas cost changes for IO-heavy operations Authors Vitalik Buterin (@vbuterin) keywords: cost; gas cache: eips-eip-150.html plain text: eips-eip-150.txt item: #241 of 3327 id: eips-eip-1504 author: eips title: eips-eip-1504 date: None words: 2370 flesch: 47 summary: Handler contract and Handler interface Functions of the Handler contract vary with requirements, so developers would better design interfaces for Handler contracts to limit them and make sure external applications are always supported. Specification The upgradable contract consists of three parts: Handler contract (implements Handler interface) defines operations and provides services. keywords: address; contract; data; handler; upgrader cache: eips-eip-1504.html plain text: eips-eip-1504.txt item: #242 of 3327 id: eips-eip-152 author: eips title: eips-eip-152 date: None words: 1755 flesch: 38 summary: Test Cases Test vector 0 input: (empty) output: error “input length for BLAKE2 F precompile should be exactly 213 bytes” Test vector 1 input: 00000c48c9bdf267e6096a3ba7ca8485ae67bb2bf894fe72f36e3cf1361d5f3af54fa5d182e6ad7f520e511f6c3e2b8c68059b6bbd41fbabd9831f79217e1319cde05b61626300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000300000000000000000000000000000001 output: error “input length for BLAKE2 F precompile should be exactly 213 bytes” Test vector 2 input: 000000000c48c9bdf267e6096a3ba7ca8485ae67bb2bf894fe72f36e3cf1361d5f3af54fa5d182e6ad7f520e511f6c3e2b8c68059b6bbd41fbabd9831f79217e1319cde05b61626300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000300000000000000000000000000000001 output: error “input length for BLAKE2 F precompile should be exactly 213 bytes” Test vector 3 input: 0000000c48c9bdf267e6096a3ba7ca8485ae67bb2bf894fe72f36e3cf1361d5f3af54fa5d182e6ad7f520e511f6c3e2b8c68059b6bbd41fbabd9831f79217e1319cde05b61626300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000300000000000000000000000000000002 output: error “incorrect final block indicator flag” Test vector 4 input: 0000000048c9bdf267e6096a3ba7ca8485ae67bb2bf894fe72f36e3cf1361d5f3af54fa5d182e6ad7f520e511f6c3e2b8c68059b6bbd41fbabd9831f79217e1319cde05b61626300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000300000000000000000000000000000001 output: 08c9bcf367e6096a3ba7ca8485ae67bb2bf894fe72f36e3cf1361d5f3af54fa5d282e6ad7f520e511f6c3e2b8c68059b9442be0454267ce079217e1319cde05b Test vector 5 input: 0000000c48c9bdf267e6096a3ba7ca8485ae67bb2bf894fe72f36e3cf1361d5f3af54fa5d182e6ad7f520e511f6c3e2b8c68059b6bbd41fbabd9831f79217e1319cde05b61626300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000300000000000000000000000000000001 output: ba80a53f981c4d0d6a2797b69f12f6e94c212f14685ac4b74b12bb6fdbffa2d17d87c5392aab792dc252d5de4533cc9518d38aa8dbf1925ab92386edd4009923 Test vector 6 input: 0000000c48c9bdf267e6096a3ba7ca8485ae67bb2bf894fe72f36e3cf1361d5f3af54fa5d182e6ad7f520e511f6c3e2b8c68059b6bbd41fbabd9831f79217e1319cde05b61626300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000300000000000000000000000000000000 output: 75ab69d3190a562c51aef8d88f1c2775876944407270c42c9844252c26d2875298743e7f6d5ea2f2d3e8d226039cd31b4e426ac4f2d3d666a610c2116fde4735 Test vector 7 input: 0000000148c9bdf267e6096a3ba7ca8485ae67bb2bf894fe72f36e3cf1361d5f3af54fa5d182e6ad7f520e511f6c3e2b8c68059b6bbd41fbabd9831f79217e1319cde05b61626300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000300000000000000000000000000000001 output: b63a380cb2897d521994a85234ee2c181b5f844d2c624c002677e9703449d2fba551b3a8333bcdf5f2f7e08993d53923de3d64fcc68c034e717b9293fed7a421 Test vector 8 input: ffffffff48c9bdf267e6096a3ba7ca8485ae67bb2bf894fe72f36e3cf1361d5f3af54fa5d182e6ad7f520e511f6c3e2b8c68059b6bbd41fbabd9831f79217e1319cde05b61626300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000300000000000000000000000000000001 output: fc59093aafa9ab43daae0e914c57635c5402d8e3d2130eb9b3cc181de7f0ecf9b22bf99a7815ce16419e200e01846e6b5df8cc7703041bbceb571de6631d2615 Implementation An initial implementation of the F function in Go, adapted from the standard library, can be found in our Golang BLAKE2 library fork. Specification We propose adding a precompiled contract at address 0x09 wrapping the BLAKE2 F compression function. keywords: function; output; precompile; precompiledblake2f cache: eips-eip-152.html plain text: eips-eip-152.txt item: #243 of 3327 id: eips-eip-1523 author: eips title: eips-eip-1523 date: None words: 1103 flesch: 44 summary: Created 2018-10-10 Discussion Link https://github.com/ethereum/EIPs/issues/1523 Requires EIP-721 Table of Contents Simple Summary Abstract Motivation Specification Additional parameters for the metadata JSON Schema Rationale Mandatory parameters Optional parameters On-chain vs. off-chain metadata Backwards Compatibility Test Cases Implementation Copyright Simple Summary A standard interface for insurance policies, based on ERC 721. Abstract The following standard allows for the implementation of a standard API for insurance policies within smart contracts. keywords: insurance; metadata; policies cache: eips-eip-1523.html plain text: eips-eip-1523.txt item: #244 of 3327 id: eips-eip-1538 author: eips title: eips-eip-1538 date: None words: 4192 flesch: 45 summary: functionSignatures, string memory _commitMessage) internal { // 0x03A9BCCF == bytes4(keccak256(updateContract(address,string,string))) bytes memory funcdata = abi.encodeWithSelector(0x03A9BCCF, contractAddress, _functionSignatures, _commitMessage); bool success; assembly { success := delegatecall(gas, _erc1538Delegate, add(funcdata, 0x20), mload(funcdata), funcdata, 0) } require(success, Adding a function failed); } constructor(address _erc1538Delegate) public { contractOwner = msg.sender; emit OwnershipTransferred(address(0), msg.sender); // adding ERC1538 updateContract function bytes memory signature = updateContract(address,string,string); bytes4 funcId = bytes4(keccak256(signature)); delegates[funcId] = _erc1538Delegate; emit FunctionUpdate(funcId, address(0), _erc1538Delegate, string(signature)); emit CommitMessage(Added ERC1538 updateContract function at contract creation); // associate unchangeable functions with this transparent contract address // prevents function selector clashes with delegate contract functions // uses the updateContract function string memory functions = delegateAddress(string); addFunction(_erc1538Delegate, address(this), functions, Associating unchangeable functions); // adding ERC1538Query interface functions functions = functionByIndex(uint256)functionExists(string)delegateAddresses()delegateFunctionSignatures(address)functionById(bytes4)functionBySignature(string)functionSignatures()totalFunctions(); // 0x01234567891011121314 is an example address of an ERC1538Query delegate contract addFunction(_erc1538Delegate, 0x01234567891011121314, functions, Adding ERC1538Query functions); // additional functions could be added at this point } // Making the fallback function payable makes it work for delegate contract functions // that are payable and not payable. keywords: address; contract; delegate; function; standard; storage; string cache: eips-eip-1538.html plain text: eips-eip-1538.txt item: #245 of 3327 id: eips-eip-1559 author: eips title: eips-eip-1559 date: None words: 2928 flesch: 26 summary: Motivation Ethereum historically priced transaction fees using a simple auction mechanism, where users send transactions with bids (“gasprices”) and Instability of blockchains with no block reward: In the long run, blockchains where there is no issuance (including Bitcoin and Zcash) at present intend to switch to rewarding miners entirely through transaction fees. keywords: base; block; fee; gas; int; transaction cache: eips-eip-1559.html plain text: eips-eip-1559.txt item: #246 of 3327 id: eips-eip-1571 author: eips title: eips-eip-1571 date: None words: 6178 flesch: 54 summary: Created 2018-11-09 Discussion Link https://github.com/AndreaLanfranchi/EthereumStratum-2.0.0/issues Table of Contents Abstract Conventions Rationale Stratum design flaws Sources of inspiration Specification JSON-RPC-2.0 Compliances JSON-RPC-2.0 Defiances Conventions Requests Responses Notifications Protocol Flow Session Handling - Hello Session Handling - Bye Session Handling - Session Subscription Session Handling - Response to Subscription Session Handling - Noop Session Handling - Reconnect Workers Authorization Prepare for mining A detail of “extranonce” Jobs notification Solution submission Hashrate Copyright Abstract This draft contains the guidelines to define a new standard for the Stratum protocol used by Ethereum miners to communicate with mining pool servers. Errors in 5xx range are server errors and suggest the miner to abandon the connection and switch to a failover. keywords: client; error; json; member; method; number; request; server; session cache: eips-eip-1571.html plain text: eips-eip-1571.txt item: #247 of 3327 id: eips-eip-1577 author: eips title: eips-eip-1577 date: None words: 582 flesch: 41 summary: Motivation Multiple applications including Metamask and mobile clients such as Status have begun resolving ENS names to content hosted on distributed systems such as IPFS and Swarm. ERC-1577: contenthash field for ENS Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-1577: contenthash field for ENS Authors Dean Eigenmann , Nick Johnson  Created 2018-11-13 Table of Contents keywords: content; contenthash cache: eips-eip-1577.html plain text: eips-eip-1577.txt item: #248 of 3327 id: eips-eip-158 author: eips title: eips-eip-158 date: None words: 719 flesch: 48 summary: Note that this proposal does introduce a temporary breaking of existing guarantees, in that by repeatedly zero-value-calling already existing empty accounts one can create a state change at a cost of 700 gas per account instead of the usual 5000 per gas minimum (with SUICIDE refunds this goes down further to 350 gas per account). Rationale This removes a large number of empty accounts that have been put in the state at very low cost due to flaws in earlier versions of the Ethereum protocol, thereby greatly reducing state size and hence both reducing the hard disk load of a full client and reducing the time for a fast sync. keywords: account cache: eips-eip-158.html plain text: eips-eip-158.txt item: #249 of 3327 id: eips-eip-1581 author: eips title: eips-eip-1581 date: None words: 648 flesch: 56 summary: ERC-1581: Non-wallet usage of keys derived from BIP-32 trees Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-1581: Non-wallet usage of keys derived from BIP-32 trees A derivation path structure for BIP32 trees to generate key pairs not meant to hold crypto assets. Citation Please cite this document as: Michele Balistreri (@bitgamma), ERC-1581: Non-wallet usage of keys derived from BIP-32 trees [DRAFT], Ethereum Improvement Proposals, no. 1581, November 2018. keywords: key; keys cache: eips-eip-1581.html plain text: eips-eip-1581.txt item: #250 of 3327 id: eips-eip-1588 author: eips title: eips-eip-1588 date: None words: 135 flesch: 26 summary: Available: https://eips.ethereum.org/EIPS/eip-1588. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. [DRAFT], Ethereum Improvement Proposals, no. 1588, November 2018. keywords: ethereum cache: eips-eip-1588.html plain text: eips-eip-1588.txt item: #251 of 3327 id: eips-eip-1592 author: eips title: eips-eip-1592 date: None words: 1271 flesch: 44 summary: Rules which are cheaper to validate or have a higher chance to break should be put first to reduce global gas expenditure, then business logic should guide the ordering of rules. ERC-1592: Address and ERC20-compliant transfer rules Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-1592: Address and ERC20-compliant transfer rules Authors Cyril Lapinte , Laurent Aapro  Created 2018-11-09 Discussion Link https://github.com/ethereum/EIPs/issues/1597 Table of Contents Simple Summary Abstract Motivation Specification Rule interface WithRules interface WithRules implementation Integration History Copyright Simple Summary We propose a standard and an interface to define transfer rules, in the context of ERC20 tokens and possibly beyond. keywords: interface; rule; transfer cache: eips-eip-1592.html plain text: eips-eip-1592.txt item: #252 of 3327 id: eips-eip-160 author: eips title: eips-eip-160 date: None words: 142 flesch: 34 summary: Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. References EIP-160 issue and discussion: https://github.com/ethereum/EIPs/issues/160 Citation Please cite this document as: Vitalik Buterin (@vbuterin), EIP-160: EXP cost increase, Ethereum Improvement Proposals, no. 160, October 2016. keywords: ethereum cache: eips-eip-160.html plain text: eips-eip-160.txt item: #253 of 3327 id: eips-eip-161 author: eips title: eips-eip-161 date: None words: 728 flesch: 48 summary: References EIP-158 issue and discussion: https://github.com/ethereum/EIPs/issues/158 EIP-161 issue and discussion: https://github.com/ethereum/EIPs/issues/161 https://blog.ethereum.org/2016/11/25/security-alert-11242016-consensus-bug-geth-v1-4-19-v1-5-2/ Details: Geth was failing to revert empty account deletions when the transaction causing the deletions of empty accounts ended with an an out-of-gas exception. An additional issue was found in Parity, where the Parity client incorrectly failed to revert empty account deletions in a more limited set of contexts involving out-of-gas calls to precompiled contracts; the new Geth behavior matches Parity’s, and empty accounts will cease to be a source of concern in general in about one week once the state clearing process finishes. keywords: account; value cache: eips-eip-161.html plain text: eips-eip-161.txt item: #254 of 3327 id: eips-eip-1613 author: eips title: eips-eip-1613 date: None words: 4386 flesch: 56 summary: Recent relay transactions (visible through TransactionRelayed events from RelayHub). The attack can be made even more impractical by setting RelayHub to require a stake from dapps before they can be served, and enforcing an unstaking delay, so that attackers will have to raise a vast amount of ETH in order to simultaneously create enough malicious contracts and attack relays. keywords: attack; gas; nonce; relay; relayhub; sender; transaction cache: eips-eip-1613.html plain text: eips-eip-1613.txt item: #255 of 3327 id: eips-eip-1616 author: eips title: eips-eip-1616 date: None words: 2633 flesch: 44 summary: Resolving attribute values by calling into separate attribute registries or other contracts, delegating authority without changing the interface of the registry. ** * @notice Count the number of attribute types defined by the registry. keywords: account; attribute; function; type; uint256 cache: eips-eip-1616.html plain text: eips-eip-1616.txt item: #256 of 3327 id: eips-eip-162 author: eips title: eips-eip-162 date: None words: 2833 flesch: 55 summary: Rationale Starting with a temporary registrar Anticipating and designing for all the potential issues of name allocation names is unlikely to succeed. Registrars are responsible for allocating domain names to users of the system, and are the only entities capable of updating the ENS; the owner of a node in the ENS registry is its registrar. keywords: auction; bid; function; hash; registrar cache: eips-eip-162.html plain text: eips-eip-162.txt item: #257 of 3327 id: eips-eip-1620 author: eips title: eips-eip-1620 date: None words: 1809 flesch: 51 summary: Triggers Event: LogCreate function create(address _recipient, address _tokenAddress, uint256 _startBlock, uint256 _stopBlock, uint256 _payment, uint256 _interval) withdraw Withdraws all or a fraction of the available funds. Triggers Event: LogConfirmUpdate Triggers Event: LogExecuteUpdate when the last involved party calls this function function update(uint256 _streamId, address _tokenAddress, uint256 _stopBlock, uint256 _payment, uint256 _interval) revokeUpdate Revokes an update proposed by one of the involved parties. keywords: address; block; stream; time; uint256 cache: eips-eip-1620.html plain text: eips-eip-1620.txt item: #258 of 3327 id: eips-eip-1633 author: eips title: eips-eip-1633 date: None words: 1623 flesch: 38 summary: It is kept purposefully agnostic to extensions beyond the standard in order to allow specific projects to design their own token relationships such as governance over, rights to or permissions on each non-fungible token relative to the respective re-fungible token owners. Citation Please cite this document as: Billy Rennekamp (@okwme), Dan Long , Kiryl Yermakou , Nate van der Ende , ERC-1633: Re-Fungible Token Standard (RFT) keywords: rft; standard; token cache: eips-eip-1633.html plain text: eips-eip-1633.txt item: #259 of 3327 id: eips-eip-165 author: eips title: eips-eip-165 date: None words: 1240 flesch: 35 summary: Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. The worst-case execution cost is 236 gas, but increases linearly with a higher number of supported interfaces. keywords: contract; function; implements; interface cache: eips-eip-165.html plain text: eips-eip-165.txt item: #260 of 3327 id: eips-eip-1679 author: eips title: eips-eip-1679 date: None words: 219 flesch: 31 summary: Available: https://eips.ethereum.org/EIPS/eip-1679. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. Citation Please cite this document as: Alex Beregszaszi (@axic), Afri Schoedon (@5chdn), EIP-1679: Hardfork Meta: Istanbul, Ethereum Improvement Proposals, no. 1679, January 2019. keywords: ethereum; istanbul cache: eips-eip-1679.html plain text: eips-eip-1679.txt item: #261 of 3327 id: eips-eip-1681 author: eips title: eips-eip-1681 date: None words: 863 flesch: 47 summary: Having a TTL on transactions would make it easier to remove stale transactions from the system. EIP-1681: Temporal Replay Protection Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-1681: Temporal Replay Protection Authors Martin Holst Swende (@holiman) Created 2019-01-08 Discussion Link https://ethereum-magicians.org/t/temporal-replay-protection/2355 Table of Contents Simple Summary Motivation Specification Rationale Rationale for this EIP Rationale for walltime Backwards Compatibility Test Cases Implementation Security considerations Copyright Simple Summary This EIP proposes adding a ‘temporal’ replay protection to transactions, in the form of a valid-until timestamp. keywords: block; ethereum; transactions cache: eips-eip-1681.html plain text: eips-eip-1681.txt item: #262 of 3327 id: eips-eip-1682 author: eips title: eips-eip-1682 date: None words: 1505 flesch: 58 summary: Accounts can be endowed with rent balance through a new EVM opcode. When rent balance is zero, it is instead charged from the account’s regular balance instead. keywords: account; balance; rent; storage cache: eips-eip-1682.html plain text: eips-eip-1682.txt item: #263 of 3327 id: eips-eip-170 author: eips title: eips-eip-170 date: None words: 304 flesch: 38 summary: References EIP-170 issue and discussion: https://github.com/ethereum/EIPs/issues/170 pyethereum implementation: https://github.com/ethereum/pyethereum/blob/5217294871283d8dc4fb3ca9d8a78c7d416490e8/ethereum/messages.py#L397 Citation Please cite this document as: Vitalik Buterin (@vbuterin), EIP-170: Contract code size limit, Ethereum Improvement Proposals, no. 170, November 2016. If block.number >= FORK_BLKNUM, then if contract creation initialization returns data with length of more than MAX_CODE_SIZE bytes, contract creation fails with an out of gas error. keywords: ethereum cache: eips-eip-170.html plain text: eips-eip-170.txt item: #264 of 3327 id: eips-eip-1702 author: eips title: eips-eip-1702 date: None words: 1563 flesch: 55 summary: Account versions can also optionally define additional account state RLP fields, whose meaning are specified through its version field. Check the RLP list length, if it is 4, then set account version to 0, and do not parse any additional fields. keywords: account; contract; version cache: eips-eip-1702.html plain text: eips-eip-1702.txt item: #265 of 3327 id: eips-eip-1706 author: eips title: eips-eip-1706 date: None words: 543 flesch: 46 summary: Requires callers to supply more gas, just to have it refunded Add contract metadata specifying per-contract EVM version, and only apply SSTORE changes to contracts deployed with the new version. Gas estimation should account for this requirement. keywords: ethereum; gas cache: eips-eip-1706.html plain text: eips-eip-1706.txt item: #266 of 3327 id: eips-eip-1710 author: eips title: eips-eip-1710 date: None words: 444 flesch: 34 summary: ERC-1710: URL Format for Web3 Browsers Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-1710: URL Format for Web3 Browsers Authors Bruno Barbieri (@brunobar79) Created 2019-01-13 Discussion Link https://ethereum-magicians.org/t/standarize-url-format-for-web3-browsers/2422 Requires EIP-155 Table of Contents Simple Summary Abstract Motivation Specification Syntax Semantics Rationale Copyright Simple Summary A standard way of representing web3 browser URLs for decentralized applications. Abstract Since most normal web browsers (specifically on mobile devices) can not run decentralized applications correctly because of the lack of web3 support, it is necessary to differentiate them from normal urls, so they can be opened in web3 browsers if available. keywords: ethereum; web3 cache: eips-eip-1710.html plain text: eips-eip-1710.txt item: #267 of 3327 id: eips-eip-1716 author: eips title: eips-eip-1716 date: None words: 269 flesch: 44 summary: Citation Please cite this document as: Afri Schoedon (@5chdn), Marius van der Wijden (@MariusVanDerWijden), EIP-1716: Hardfork Meta: Petersburg, Ethereum Improvement Proposals, no. 1716, January 2019. Available: https://eips.ethereum.org/EIPS/eip-1716. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: ethereum cache: eips-eip-1716.html plain text: eips-eip-1716.txt item: #268 of 3327 id: eips-eip-173 author: eips title: eips-eip-173 date: None words: 903 flesch: 45 summary: It is so common that the contract interface used to handle contract ownership should be standardized to allow compatibility with user interfaces and contracts that manage contracts. Available: https://eips.ethereum.org/EIPS/eip-173. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: contract; ownership cache: eips-eip-173.html plain text: eips-eip-173.txt item: #269 of 3327 id: eips-eip-1753 author: eips title: eips-eip-1753 date: None words: 1669 flesch: 31 summary: If individuals wish to sight information on Licence registries, they often need to be present at the government office and complete further paper-based enquiry forms in order to access that data (if available publicly). In an era of open government, there is also an increased expectation that individuals will be able to easily access Licence registries, and that the process will be transparent and fair. keywords: ethereum; function; licence; public; uint256 cache: eips-eip-1753.html plain text: eips-eip-1753.txt item: #270 of 3327 id: eips-eip-1761 author: eips title: eips-eip-1761 date: None words: 1212 flesch: 59 summary: @param _approved True if the operator is approved, false to revoke approval */ function setApprovalForScope(address _operator, bytes32 _scope, bool _approved) external; / The owner of the Tokens @param _operator Address of authorized operator @param _scope Scope to test for approval (can be identified by calling scopeForId) @return True if the operator is approved, false otherwise */ function isApprovedForScope(address _owner, address _operator, bytes32 _scope) public view returns (bool); } Scope Metadata JSON Schema This schema allows for localization. keywords: @param; approval; scope; uri cache: eips-eip-1761.html plain text: eips-eip-1761.txt item: #271 of 3327 id: eips-eip-1767 author: eips title: eips-eip-1767 date: None words: 3018 flesch: 58 summary: # Block is the block this transaction was mined in. if # transactions are not available for this block, this field will be null. keywords: account; block; ethereum; functionality; transaction cache: eips-eip-1767.html plain text: eips-eip-1767.txt item: #272 of 3327 id: eips-eip-1775 author: eips title: eips-eip-1775 date: None words: 2004 flesch: 41 summary: Private App Key generation algorithm We now propose an algorithm to generate application keys that: are uniquely defined, with respect to the account that the user selected to generate these keys, and thus can be isolated when changing the user account, allowing persona management (see next section), are specific to each application, can be fully restored from the user master seed mnemonic and the applications’ names. Using different accounts as personas We allow the user to span a different set of application keys by changing the account selected to generate each key. keywords: accounts; app; application; keys; user cache: eips-eip-1775.html plain text: eips-eip-1775.txt item: #273 of 3327 id: eips-eip-1803 author: eips title: eips-eip-1803 date: None words: 224 flesch: 32 summary: EIP-1803: Rename opcodes for clarity Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Interface EIP-1803: Rename opcodes for clarity Authors Alex Beregszaszi (@axic) Citation Please cite this document as: Alex Beregszaszi (@axic), EIP-1803: Rename opcodes for clarity [DRAFT], Ethereum Improvement Proposals, no. 1803, July 2017. keywords: ethereum cache: eips-eip-1803.html plain text: eips-eip-1803.txt item: #274 of 3327 id: eips-eip-181 author: eips title: eips-eip-181 date: None words: 1191 flesch: 45 summary: ENS support for reverse resolution of Ethereum addresses Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: ERC ERC-181: ENS support for reverse resolution of Ethereum addresses Authors Nick Johnson  Created 2016-12-01 Table of Contents Abstract Motivation Specification Registrar function claim(address owner) returns (bytes32 node) function claimWithResolver(address owner, address resolver) returns (bytes32 node) function setName(string name) returns (bytes32 node) Allowing the caller to specify an owner other than themselves for the relevant node facilitates contracts that need accurate reverse ENS entries delegating this to their creators with a minimum of code inside their constructor: reverseRegistrar.claim(msg.sender) function claimWithResolver(address owner, address resolver) returns (bytes32 node) When called by account x, instructs the ENS registry to set the resolver of the name hex(x) + '.addr.reverse' to the specified resolver, then transfer ownership of the name to the provided address, and return the namehash of the ENS record thus transferred. keywords: address; ens; node cache: eips-eip-181.html plain text: eips-eip-181.txt item: #275 of 3327 id: eips-eip-1812 author: eips title: eips-eip-1812 date: None words: 2121 flesch: 52 summary: ERC-735 and ERC-780 provide on-chain storage and lookups of Verifiable Claims. function verifyIssuer(Know memory claim, uint8 v, bytes32 r, bytes32 s) public returns (address) { bytes32 digest = keccak256( abi.encodePacked( \x19\x01, DOMAIN_SEPARATOR, hash(claim) ) ); require( (claim.validFrom >= block.timestamp) && (block.timestamp < claim.validTo) , invalid issuance timestamps); return ecrecover(digest, v, r, s); } Calling a SmartContract function Verifiable Claims can be presented to a solidity function call as it’s struct together with the v, r and s signature components. keywords: address; claims; issuer; struct; subject; uint256 cache: eips-eip-1812.html plain text: eips-eip-1812.txt item: #276 of 3327 id: eips-eip-1820 author: eips title: eips-eip-1820 date: None words: 6645 flesch: 49 summary: @param _interfaceId ERC165 interface for which to update the cache. function updateERC165Cache(address _contract, bytes4 _interfaceId) external { interfaces[_contract][_interfaceId] = implementsERC165InterfaceNoCache( _contract, _interfaceId) ? _contract : address(0); erc165Cached[_contract][_interfaceId] = true; } /// @notice Checks whether a contract implements an ERC165 interface or not. // keywords: address; contract; ═ ═; ═ ╝; ╔ ═; ╚ ═; █ ║ cache: eips-eip-1820.html plain text: eips-eip-1820.txt item: #277 of 3327 id: eips-eip-1822 author: eips title: eips-eip-1822 date: None words: 1477 flesch: 16 summary: Logic Contract - The contract B which contains the logic used by Proxy Contract A Proxiable Contract - Inherited in Logic Contract B to provide the upgrade functionality Specification The Proxy Contract proposed here should be deployed as is, and used as a drop-in replacement for any existing methods of lifecycle management of contracts. Universal Upgradeable Proxy Standard (UUPS) Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-1822: Universal Upgradeable Proxy Standard (UUPS) Authors Gabriel Barros , Patrick Gallagher  Created 2019-03-04 Discussion Link https://ethereum-magicians.org/t/eip-1822-universal-upgradeable-proxy-standard-uups Table of Contents Simple Summary Abstract Motivation Terminology Specification Proxy Contract Proxiable Contract Pitfalls when using a proxy Separating Variables from Logic Restricting dangerous functions Examples Owned ERC-20 Token References Copyright Simple Summary Standard upgradeable proxy contract. keywords: contract; logic; proxy cache: eips-eip-1822.html plain text: eips-eip-1822.txt item: #278 of 3327 id: eips-eip-1829 author: eips title: eips-eip-1829 date: None words: 1006 flesch: 60 summary: Abstract A precompile that takes a curve and computes a linear combination of curve points. There are draft proposals to add more curves. keywords: curve; linear cache: eips-eip-1829.html plain text: eips-eip-1829.txt item: #279 of 3327 id: eips-eip-1844 author: eips title: eips-eip-1844 date: None words: 543 flesch: 35 summary: ERC-1844: ENS Interface Discovery Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-1844: ENS Interface Discovery Authors Nick Johnson (@arachnid) Created 2019-03-15 Discussion Link https://ethereum-magicians.org/t/ens-interface-discovery/2924 Requires EIP-137, EIP-165 Table of Contents Simple Summary Abstract Motivation Specification Rationale Backwards Compatibility Test Cases Implementation Copyright Simple Summary Defines a method of associating contract interfaces with ENS names and addresses, and of discovering those interfaces. For example, a token contract may not itself provide any kind of ‘atomic swap’ functionality, but there may be associated contracts that do. keywords: contract; interface cache: eips-eip-1844.html plain text: eips-eip-1844.txt item: #280 of 3327 id: eips-eip-1872 author: eips title: eips-eip-1872 date: None words: 1712 flesch: 58 summary: Abstract Four different weeks, spaced roughly evenly throughout the year, are targeted for network upgrades to be launched. This also provides a framework to regularize the delivery of network upgrades. keywords: network; roadmap; upgrades; windows cache: eips-eip-1872.html plain text: eips-eip-1872.txt item: #281 of 3327 id: eips-eip-1884 author: eips title: eips-eip-1884 date: None words: 1238 flesch: 55 summary: EIP-1884: Repricing for trie-size-dependent opcodes Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: Core EIP-1884: Repricing for trie-size-dependent opcodes Authors Martin Holst Swende (@holiman) Created 2019-03-28 Requires EIP-150, EIP-1052 Table of Contents Simple Summary Abstract Motivation Specification Rationale SLOAD BALANCE EXTCODEHASH Backwards Compatibility Test Cases Implementation SELFBALANCE Security considerations Copyright Simple Summary This EIP proposes repricing certain opcodes, to obtain a good balance between gas expenditure and resource consumption. Abstract The growth of the Ethereum state has caused certain opcodes to be more resource-intensive at this point than they were previously. keywords: balance; gas; selfbalance cache: eips-eip-1884.html plain text: eips-eip-1884.txt item: #282 of 3327 id: eips-eip-1890 author: eips title: eips-eip-1890 date: None words: 541 flesch: 44 summary: Citation Please cite this document as: Gregory Markou , Kevin Owocki , Lane Rettig , EIP-1890: Commitment to Sustainable Ecosystem Funding [DRAFT], Ethereum Improvement Proposals, no. 1890, March 2019. This EIP adds a simple mechanism for capturing a portion of block rewards for ecosystem funding as a credible commitment to doing so in future, but it does not actually capture any such rewards. keywords: ethereum; funding cache: eips-eip-1890.html plain text: eips-eip-1890.txt item: #283 of 3327 id: eips-eip-1895 author: eips title: eips-eip-1895 date: None words: 1001 flesch: 51 summary: EIP-1895: Support for an Elliptic Curve Cycle Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-1895: Support for an Elliptic Curve Cycle Authors Alexandre Belling  Created 2018-03-31 Discussion Link https://ethresear.ch/t/reducing-the-verification-cost-of-a-snark-through-hierarchical-aggregation/5128 Table of Contents Simple Summary Abstract Motivation Specification The curve MNT4 definition The operations and gas cost Encoding Edge cases Rationale Test Cases References Implementation Copyright Simple Summary The EVM currently supports elliptic curves operations for curve alt-bn128 thanks to precompiles ecadd and ecmul and ecpairing. If we had a cycle with only one pairing friendly curve we would still be able to compose proofs by alternating between SNARKs and any other general purpose zero-knowledge cryptosystems. keywords: curve cache: eips-eip-1895.html plain text: eips-eip-1895.txt item: #284 of 3327 id: eips-eip-1898 author: eips title: eips-eip-1898 date: None words: 1203 flesch: 37 summary: Test Cases eth_getStorageAt [ 0x
, { blockNumber: 0x0 } -> return storage at given address in genesis block eth_getStorageAt [ 0x
, { blockHash: 0xd4e56740f876aef8c010b86a40d5f56745a118d0906a34e69aec8c0db1cb8fa3 } -> return storage at given address in genesis block eth_getStorageAt [ 0x
, { blockHash: 0xd4e56740f876aef8c010b86a40d5f56745a118d0906a34e69aec8c0db1cb8fa3, requireCanonical: false } -> return storage at given address in genesis block eth_getStorageAt [ 0x
, { blockHash: 0xd4e56740f876aef8c010b86a40d5f56745a118d0906a34e69aec8c0db1cb8fa3, requireCanonical: true } -> return storage at given address in genesis block eth_getStorageAt [ 0x
, { blockHash: 0x } -> raise block-not-found error eth_getStorageAt [ 0x
, { blockHash: 0x, requireCanonical: false } -> raise block-not-found error eth_getStorageAt [ 0x
, { blockHash: 0x, requireCanonical: true } -> raise block-not-found error eth_getStorageAt [ 0x
, { blockHash: 0x } -> return storage at given address in specified block eth_getStorageAt [ 0x
, { blockHash: 0x, requireCanonical: false } -> return storage at given address in specified block eth_getStorageAt [ 0x
, { blockHash: 0x, requireCanonical: true } -> raise block-not-canonical error Security Considerations None Copyright Copyright and related rights waived via CC0. To maintain backwards compatibility, the block number MAY be specified either as a hex string or using the new block parameter scheme. keywords: address; block cache: eips-eip-1898.html plain text: eips-eip-1898.txt item: #285 of 3327 id: eips-eip-190 author: eips title: eips-eip-190 date: None words: 685 flesch: 40 summary: Use Cases This specification covers the following types of smart contract packages. ERC-190: Ethereum Smart Contract Packaging Standard Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: ERC ERC-190: Ethereum Smart Contract Packaging Standard Authors Piper Merriam (@pipermerriam), Tim Coulter (@tcoulter), Denis Erfurt (@mhhf), RJ Catalano (@VoR0220), Iuri Matias (@iurimatias) Created 2017-01-10 Table of Contents Abstract Motivation Specification Use Cases Package Managers Deterministic builds Bytecode verification Multi-chain deploys Trusted packages Framework support and integration Abstract This ERC proposes a specification for Ethereum smart contract packages. keywords: contract; ethereum cache: eips-eip-190.html plain text: eips-eip-190.txt item: #286 of 3327 id: eips-eip-1900 author: eips title: eips-eip-1900 date: None words: 1667 flesch: 45 summary: This is an array of objects (structs), with the following fields: name - the subtype name, of type string, similar to the above name definition label - the subtype label dimensions - string[] used for storing array dimensions. (With type definitions in the source (Swarm stored source code in the respective language)) keywords: data; ethereum; registry; system; type cache: eips-eip-1900.html plain text: eips-eip-1900.txt item: #287 of 3327 id: eips-eip-1901 author: eips title: eips-eip-1901 date: None words: 767 flesch: 42 summary: Citation Please cite this document as: Shane Jonas (@shanejonas), Zachary Belford (@belfordz), EIP-1901: Add OpenRPC Service Discovery To JSON-RPC Services [DRAFT], Ethereum Improvement Proposals, no. 1901, February 2019. Ethereum clients can expose RPC endpoints with different method signatures and cause compatibility issues between clients. keywords: json; openrpc; rpc cache: eips-eip-1901.html plain text: eips-eip-1901.txt item: #288 of 3327 id: eips-eip-191 author: eips title: eips-eip-191 date: None words: 686 flesch: 52 summary: We propose the following format for signed_data 0x19 <1 byte version> . Example Copyright Abstract This ERC proposes a specification about how to handle signed data in Ethereum contracts. keywords: data; version cache: eips-eip-191.html plain text: eips-eip-191.txt item: #289 of 3327 id: eips-eip-1921 author: eips title: eips-eip-1921 date: None words: 920 flesch: 38 summary: In order to evolve the EVM into a Singleton Operating System, we need a way to register, find and address contract functions that we want to run in an automated way. The current EIP specifies the data definitions and interfaces needed to support registering individual smart contract functions, as entries in the dType Registry. keywords: contract; eip-1900; function cache: eips-eip-1921.html plain text: eips-eip-1921.txt item: #290 of 3327 id: eips-eip-1922 author: eips title: eips-eip-1922 date: None words: 2125 flesch: 44 summary: Existing zk-SNARK compilers such as ZoKrates, which produce ‘Verifier.sol’ contracts, do not currently produce Verifier contracts which adhere to this EIP specification. :warning: TODO: Motivation zk-SNARKs are a promising area of interest for the Ethereum community. keywords: circuit; contract; inputs; proof; verification cache: eips-eip-1922.html plain text: eips-eip-1922.txt item: #291 of 3327 id: eips-eip-1923 author: eips title: eips-eip-1923 date: None words: 919 flesch: 29 summary: What are zk-SNARKs? [] calldata _results) external; function challengeAttestation(bytes32 _proofId, uint256[] calldata _proof, uint64[] calldata _inputs, address _verifierContract) external; function createNewVkId(uint256 keywords: calldata; function; standard cache: eips-eip-1923.html plain text: eips-eip-1923.txt item: #292 of 3327 id: eips-eip-1930 author: eips title: eips-eip-1930 date: None words: 1716 flesch: 60 summary: As gas pricing continue to evolve, this is important to have a mechanism to ensure a specific amount of gas is passed to the call so such mechanism can be used without having to relies on a specific gas pricing. 2) check done after the call: to.call.gas(txGas)(data); // CALL require(gasleft() > txGas / 63, not enough gas left); This solution does not require to compute a E value and thus do not relies on a specific gas pricing (except for the behaviour of EIP-150) Revert if not enough gas available. keywords: contract; gas; revert cache: eips-eip-1930.html plain text: eips-eip-1930.txt item: #293 of 3327 id: eips-eip-1948 author: eips title: eips-eip-1948 date: None words: 742 flesch: 59 summary: Examples for dynamic data: cryptokitties that can change color intellectual property tokens that encode rights holders tokens that store data to transport them across chains The existing metadata standard does not suffice as data can only be set at minting time and not modified later. Protocols that build on data tokens like distributed breeding will be enabled. keywords: data; tokenid cache: eips-eip-1948.html plain text: eips-eip-1948.txt item: #294 of 3327 id: eips-eip-1959 author: eips title: eips-eip-1959 date: None words: 1413 flesch: 58 summary: In other words, we should consider all off-chain messages (with valid chainID) as part of the chain’s offchain state. As for replay protection, the idea of considering all of the off-chain messages signed with valid chainID as part of the chain’s offchain-state means that all of these off-chain messages can be reused on the different forks which share a common chainID history (up to where they differ). keywords: chainid; history; messages cache: eips-eip-1959.html plain text: eips-eip-1959.txt item: #295 of 3327 id: eips-eip-196 author: eips title: eips-eip-196 date: None words: 927 flesch: 53 summary: Curve points are encoded as two field elements (x, y), where the point at infinity is encoded as (0, 0). Output: curve point x + y, where + is point addition on the elliptic curve alt_bn128 specified above. keywords: contracts; curve cache: eips-eip-196.html plain text: eips-eip-196.txt item: #296 of 3327 id: eips-eip-1962 author: eips title: eips-eip-1962 date: None words: 1394 flesch: 43 summary: Functionality of such precompile will require the following: Implementation the following operations over elliptic curves in the Weierstrass form with curve parameters such as base field, A, B coefficients defined in runtime: Point addition Multiplication of a single point over a scalar Multiexponentiation Implementation pairing operation over elliptic curves from the following “families” with parameters such as base field, extension tower structure, coefficients defined in runtime: BLS12 BN MNT4/6 (Ate pairing) Pairings are an important extension for basic arithmetic and so this new precompile is proposed with the following benefits: Extended set of curves will be available to allow Ethereum users to choose their security parameters and required functionality. keywords: curve; field; test cache: eips-eip-1962.html plain text: eips-eip-1962.txt item: #297 of 3327 id: eips-eip-1965 author: eips title: eips-eip-1965 date: None words: 1118 flesch: 60 summary: Note though that the alternative to keep track of old chainID is to implement a smart contract based caching solution as EIP-1344 proposes comes with an overall higher gas cost and exhibit issues for minority-led hardfork (see Rationale section below). EIP-1965: Method to check if a chainID is valid at a specific block Number Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-1965: Method to check if a chainID is valid at a specific block Number Authors Ronan Sandford (@wighawag) keywords: blocknumber; chainid cache: eips-eip-1965.html plain text: eips-eip-1965.txt item: #298 of 3327 id: eips-eip-1967 author: eips title: eips-eip-1967 date: None words: 2699 flesch: 48 summary: These proxies rely on a logic contract (also known as implementation contract or master copy) that is called using delegatecall. Unfortunately, tracking changes to storage slots is not easy. keywords: @dev; address; contract; function; implementation; slot cache: eips-eip-1967.html plain text: eips-eip-1967.txt item: #299 of 3327 id: eips-eip-197 author: eips title: eips-eip-197 date: None words: 1392 flesch: 56 summary: EIP-197: Precompiled contracts for optimal ate pairing check on the elliptic curve alt_bn128 Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: Core EIP-197: Precompiled contracts for optimal ate pairing check on the elliptic curve alt_bn128 Authors Vitalik Buterin , Christian Reitwiessner  Created 2017-02-06 Table of Contents Simple Summary Abstract Motivation Specification Definition of the groups Encoding Gas costs Rationale Backwards Compatibility Test Cases Implementation Copyright Simple Summary Precompiled contracts for elliptic curve pairing operations are required in order to perform zkSNARK verification within the block gas limit. The discrete logarithm is of course assumed to be hard to compute, but we will give an equivalent specification that makes use of elliptic curve pairing functions which can be efficiently computed below. Address: 0x8 keywords: curve; pairing cache: eips-eip-197.html plain text: eips-eip-197.txt item: #300 of 3327 id: eips-eip-1973 author: eips title: eips-eip-1973 date: None words: 1582 flesch: 44 summary: */ function calculateRewards() private returns (uint256) { uint256 playerMask = participantMask[msg.sender]; uint256 rewards = roundMask.sub(playerMask); updateParticipantMask(msg.sender); return rewards; } /** * @dev Function to mint new tokens into the economy. Abstract The mintable token rewards interface allows DApps to build a token economy where token rewards are distributed equally among the active participants. keywords: function; tokens cache: eips-eip-1973.html plain text: eips-eip-1973.txt item: #301 of 3327 id: eips-eip-198 author: eips title: eips-eip-198 date: None words: 784 flesch: 54 summary: Citation Please cite this document as: Vitalik Buterin (@vbuterin), EIP-198: Big integer modular exponentiation, Ethereum Improvement Proposals, no. 198, January 2017. This input data: 0000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000020 0000000000000000000000000000000000000000000000000000000000000020 fffffffffffffffffffffffffffffffffffffffffffffffffffffffefffffc2e fffffffffffffffffffffffffffffffffffffffffffffffffffffffefffffc2f Would be parsed as a base of 0, exponent of 2**256 - 2**32 - 978 and modulus of 2**256 - 2**32 - 977, and so would return 0. keywords: exponent; modulus cache: eips-eip-198.html plain text: eips-eip-198.txt item: #302 of 3327 id: eips-eip-1985 author: eips title: eips-eip-1985 date: None words: 805 flesch: 50 summary: EIP-1985: Sane limits for certain EVM parameters Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-1985: Sane limits for certain EVM parameters Authors Alex Beregszaszi (@axic), Paweł Bylica (@chfast) Created 2018-08-01 Discussion Link https://ethereum-magicians.org/t/eip-1985-sane-limits-for-certain-evm-parameters/3224 Table of Contents Abstract Motivation Specification Rationale Timestamp Addresses Memory size Code size Comparing current implementations Backwards Compatibility Test Cases Implementation References TODO Copyright Abstract Introduce an explicit value range for certain EVM parameters (such as gas limit, block number, block timestamp, size field when returning/copying data within EVM). gas, gas limit, block gas limit is a range between 0 and 0x7fffffffffffffff (2**63 - 1, 9223372036854775807). keywords: gas; limit; size cache: eips-eip-1985.html plain text: eips-eip-1985.txt item: #303 of 3327 id: eips-eip-1996 author: eips title: eips-eip-1996 date: None words: 2109 flesch: 45 summary: ERC-1996: Holdable Token Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-1996: Holdable Token Authors Julio Faura , Fernando Paris , Daniel Lehrner  Created 2019-04-10 Discussion Link https://github.com/ethereum/EIPs/issues/2103 Requires EIP-20 Table of Contents Simple Summary Actors Abstract Motivation Specification Functions Events Rationale Backwards Compatibility Implementation Contributors Copyright Simple Summary An extension to the ERC-20 standard token that allows tokens to be put on hold. Holds are similar to escrows in that are firm and lead to final settlement. keywords: address; hold; operationid cache: eips-eip-1996.html plain text: eips-eip-1996.txt item: #304 of 3327 id: eips-eip-2 author: eips title: eips-eip-2 date: None words: 900 flesch: 39 summary: Contract creation from a contract using the CREATE opcode is unaffected. If contract creation does not have enough gas to pay for the final gas fee for adding the contract code to the state, the contract creation fails (i.e. goes out-of-gas) rather than leaving an empty contract. keywords: contract; ethereum; transaction cache: eips-eip-2.html plain text: eips-eip-2.txt item: #305 of 3327 id: eips-eip-20 author: eips title: eips-eip-20 date: None words: 775 flesch: 44 summary: Transfer(address indexed _from, address indexed _to, uint256 _value) Approval MUST trigger on any successful call to approve(address _spender, uint256 _value). function balanceOf(address _owner) public view returns (uint256 balance) transfer Transfers _value amount of tokens to address _to, and MUST fire the Transfer event. keywords: function; returns cache: eips-eip-20.html plain text: eips-eip-20.txt item: #306 of 3327 id: eips-eip-2003 author: eips title: eips-eip-2003 date: None words: 544 flesch: 33 summary: Citation Please cite this document as: Paweł Bylica (@chfast), Alex Beregszaszi (@axic), EIP-2003: EVMC modules for implementations of precompiled contracts [DRAFT], Ethereum Improvement Proposals, no. 2003, May 2019. Precompiled contract implementations are allowed to return two more EVMC error codes: EVMC_FAILURE if the failure was caused due to something other than out of gas (e.g. input validation error) EVMC_REVERT if the precompile doesn’t want to forfeit all supplied gas (as of May 2019 no such precompile exists) keywords: ethereum; evmc cache: eips-eip-2003.html plain text: eips-eip-2003.txt item: #307 of 3327 id: eips-eip-2009 author: eips title: eips-eip-2009 date: None words: 1791 flesch: 37 summary: Specification interface CompliantService { function checkTransferAllowed(bytes32 tokenId, address from, address to, uint256 value) external view returns (byte); function checkTransferFromAllowed(bytes32 tokenId, address sender, address from, address to, uint256 value) external view returns (byte); function checkMintAllowed(bytes32 tokenId, address to, uint256 value) external view returns (byte); function checkBurnAllowed(bytes32 tokenId, address from, uint256 value) external view returns (byte); function updateTransferAccumulated(bytes32 tokenId, external view returns (bool); event TokenAdded(bytes32 indexed tokenId, address indexed token); event TokenReplaced(bytes32 indexed tokenId, address indexed previousAddress, address indexed newAddress); event TokenRemoved(bytes32 indexed tokenId); event AuthorizedAccumulatedOperator(address indexed operator, bytes32 indexed tokenId); event RevokedAccumulatedOperator(address indexed operator, bytes32 indexed tokenId); } keywords: address; token; tokenid cache: eips-eip-2009.html plain text: eips-eip-2009.txt item: #308 of 3327 id: eips-eip-2014 author: eips title: eips-eip-2014 date: None words: 543 flesch: 46 summary: Some examples include extended access to block hashes (EIP-210) and chain identifiers (EIP-1344). Specification A new system contract (“precompile”) is introduced at address 0x0000000000000000000000000000000000000009 called ESO (Extended State Oracle). keywords: contract; ethereum cache: eips-eip-2014.html plain text: eips-eip-2014.txt item: #309 of 3327 id: eips-eip-2015 author: eips title: eips-eip-2015 date: None words: 666 flesch: 48 summary: Wallets should prompt the user before switching or adding chains. EIP-2015: wallet_updateEthereumChain RPC Method Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Interface EIP-2015: wallet_updateEthereumChain RPC Method Adds an RPC method to switch betweeen EVM-compatible chains Authors Pedro Gomes (@pedrouid), Erik Marks (@rekmarks), Pandapip1 (@Pandapip1) keywords: method; wallet_updateethereumchain cache: eips-eip-2015.html plain text: eips-eip-2015.txt item: #310 of 3327 id: eips-eip-2018 author: eips title: eips-eip-2018 date: None words: 1534 flesch: 29 summary: Parameter Description operator The address to be an operator of clearable transfers from The address on which the holds would be created transfer It is up to the implementer of the EIP if the transfer function of ERC-20 should always revert or is allowed under certain circumstances. Parameter Description operator The address which has been approved as operator of clearable transfers account Address on which behalf transfers will potentially be ordered RevokedClearableTransferOperator Emitted when an operator has been revoked from ordering transfers on behalf of another account. keywords: clearable; operationid; transfer cache: eips-eip-2018.html plain text: eips-eip-2018.txt item: #311 of 3327 id: eips-eip-2019 author: eips title: eips-eip-2019 date: None words: 1475 flesch: 37 summary: EIP 1066 codes can be used isFundOperatorFor Checks that given player is allowed to order fund requests, for a given wallet. FundOperatorAuthorized Emitted when a given player, operator, company or a given persona, has been approved to start fund request for a given token holder. keywords: operationid; orderer; parameter; request cache: eips-eip-2019.html plain text: eips-eip-2019.txt item: #312 of 3327 id: eips-eip-2020 author: eips title: eips-eip-2020 date: None words: 2128 flesch: 35 summary: In most jurisdictions, electronic money balances are required to be 100% backed by assets, which often entails holding cash on an omnibus account at a bank with 100% of the funds issued to clients in the electronic money ledger. Compliance: E-Money Standard Token implements a set of methods to check in advance whether user-initiated transactions can be done from a compliance point of view. keywords: address; function; money; operator; returns cache: eips-eip-2020.html plain text: eips-eip-2020.txt item: #313 of 3327 id: eips-eip-2021 author: eips title: eips-eip-2021 date: None words: 1797 flesch: 37 summary: Abstract Token wallet owners (or approved addresses) can order payout requests through blockchain. Rationale This standards provides a functionality to allow token holders to start payout requests in a decentralized way. keywords: operationid; orderer; payout; request cache: eips-eip-2021.html plain text: eips-eip-2021.txt item: #314 of 3327 id: eips-eip-2025 author: eips title: eips-eip-2025 date: None words: 2625 flesch: 60 summary: Aya Miyaguchi observed in a recent Coindesk article, “it really is not only Ethereum Foundation people who are building EIP-1890 proposes a mechanism to capture a portion of block rewards for sustainably funding ongoing network development. keywords: block; eip; eth1.x; ethereum; funding; loan cache: eips-eip-2025.html plain text: eips-eip-2025.txt item: #315 of 3327 id: eips-eip-2026 author: eips title: eips-eip-2026 date: None words: 950 flesch: 52 summary: Prepayments on pre-existing accounts are necessary to prevent hoarding of accounts ahead of this change. State Rent H - Fixed Prepayment for accounts Authors Alexey Akhunov (@AlexeyAkhunov) Created 2019-05-14 Discussion Link https://ethereum-magicians.org/t/eip-2026-fixed-rent-prepayment-for-all-accounts-change-h-from-state-rent-v3-proposal/3273 Table of Contents Simple Summary Abstract Motivation Specification Rationale Backwards Compatibility Test Cases Implementation Copyright Simple Summary Creation of new accounts (both contracts and non-contracts) requires a fixed one-off rent prepayment. keywords: account; rent cache: eips-eip-2026.html plain text: eips-eip-2026.txt item: #316 of 3327 id: eips-eip-2027 author: eips title: eips-eip-2027 date: None words: 766 flesch: 51 summary: It needs to be large enough so that no real metrics (contract storage size, number of accounts, number of contracts, total size of code, total size of storage) will never reach that number, and small enough that it fits in an unsigned 64-bit integer. Rationale A mechanism for estimation of contract storage size has been proposed here. keywords: number; storagesize cache: eips-eip-2027.html plain text: eips-eip-2027.txt item: #317 of 3327 id: eips-eip-2028 author: eips title: eips-eip-2028 date: None words: 1235 flesch: 56 summary: We shall (1) evaluate the theoretical impact of lower Calldata gas cost on network delay using this model, (2) validate the model empirically, and (3) base the proposed gas cost on our findings. [1] and Pass, Seeman and Shelat [2], which relates network security to network delay. keywords: cost; delay; gas; network cache: eips-eip-2028.html plain text: eips-eip-2028.txt item: #318 of 3327 id: eips-eip-2029 author: eips title: eips-eip-2029 date: None words: 550 flesch: 53 summary: Later, this contract becomes “special” in that Ethereum start writing state counters (number of total transactions, number of accounts, etc.) into that contract. Motivation Ethereum currently does not have a special place in the state for tracking state counters such as number of transactions or number of accounts. keywords: contract; state cache: eips-eip-2029.html plain text: eips-eip-2029.txt item: #319 of 3327 id: eips-eip-2031 author: eips title: eips-eip-2031 date: None words: 555 flesch: 50 summary: Updating txCount means updating the storage of state counter contract at the location 0. It is done by incrementing a storage slot in the special contract, called State counter contract (EIP-2029). keywords: counter; state cache: eips-eip-2031.html plain text: eips-eip-2031.txt item: #320 of 3327 id: eips-eip-2035 author: eips title: eips-eip-2035 date: None words: 904 flesch: 55 summary: EIP-2035: Stateless Clients - Repricing SLOAD and SSTORE to pay for block proofs Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-2035: Stateless Clients - Repricing SLOAD and SSTORE to pay for block proofs Authors Alexey Akhunov (@AlexeyAkhunov) Created 2019-05-16 Discussion Link https://ethereum-magicians.org/t/eip-2035-stateless-clients-repricing-sload-and-sstore-to-pay-for-block-proofs/3284 Table of Contents Simple Summary Abstract Motivation Specification Rationale Backwards Compatibility Test Cases Implementation Copyright Simple Summary The gas cost of EVM opcodes SLOAD and SSTORE increases in order to accommodate extra bandwidth required to propagate block proof together with the block headers and block bodies, as explained here. It means that the Ethereum nodes will still need access to the accounts in the state, but block proofs will make it optional to have access to contract storage for executing transactions. keywords: block; sload cache: eips-eip-2035.html plain text: eips-eip-2035.txt item: #321 of 3327 id: eips-eip-2045 author: eips title: eips-eip-2045 date: None words: 1087 flesch: 50 summary: Ewasm The term “particles” was first introduced for Ewasm3 to enable gas accounting for low cost wasm instructions, while remaining compatible with EVM gas costs. A new minimum unit of gas, called a “particle”, which is a fraction of 1 gas, would expand the range of gas costs and thus enable reductions below the current minimum. keywords: cost; gas cache: eips-eip-2045.html plain text: eips-eip-2045.txt item: #322 of 3327 id: eips-eip-2046 author: eips title: eips-eip-2046 date: None words: 439 flesch: 49 summary: Citation Please cite this document as: Alex Beregszaszi (@axic), EIP-2046: Reduced gas cost for static calls made to precompiles [DRAFT], Ethereum Improvement Proposals, no. 2046, May 2019. EIP-2046: Reduced gas cost for static calls made to precompiles Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-2046: Reduced gas cost for static calls made to precompiles Authors Alex Beregszaszi (@axic) Created 2019-05-17 Discussion Link https://ethereum-magicians.org/t/eip-2046-reduced-gas-cost-for-static-calls-made-to-precompiles/3291 Requires EIP-214, EIP-1352 Table of Contents Simple Summary Abstract Motivation Specification Rationale Backwards Compatibility Test Cases Implementation References Acknowledgements Copyright Simple Summary This change reduces the gas cost of using precompiled contracts. keywords: cost; precompiles cache: eips-eip-2046.html plain text: eips-eip-2046.txt item: #323 of 3327 id: eips-eip-205 author: eips title: eips-eip-205 date: None words: 837 flesch: 53 summary: ABI lookup process When attempting to fetch an ABI based on an ENS name, implementers should first attempt an ABI lookup on the name itself. Specification ABI encodings In order to allow for different tradeoffs between onchain size and accessibility, several ABI encodings are defined. keywords: abi; abis cache: eips-eip-205.html plain text: eips-eip-205.txt item: #324 of 3327 id: eips-eip-2069 author: eips title: eips-eip-2069 date: None words: 465 flesch: 43 summary: EIP-2069: Recommendation for using YAML ABI in ERCs/EIPs Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Informational EIP-2069: Recommendation for using YAML ABI in ERCs/EIPs Authors Alex Beregszaszi (@axic) Created 2017-02-11 Discussion Link https://ethereum-magicians.org/t/eip-2069-recommendation-for-using-yaml-abi-in-specifications/3347 Table of Contents Simple Summary Motivation Specification Rationale Backwards Compatibility Test Cases Implementation Copyright Simple Summary Recommendation for including contract ABI descriptions in EIPs and ERCs as YAML. Citation Please cite this document as: Alex Beregszaszi (@axic), EIP-2069: Recommendation for using YAML ABI in ERCs/EIPs [DRAFT], Ethereum Improvement Proposals, no. 2069, February 2017. keywords: abi; yaml cache: eips-eip-2069.html plain text: eips-eip-2069.txt item: #325 of 3327 id: eips-eip-2070 author: eips title: eips-eip-2070 date: None words: 138 flesch: 35 summary: Citation Please cite this document as: Alex Beregszaszi (@axic), EIP-2070: Hardfork Meta: Berlin [DRAFT], Ethereum Improvement Proposals, no. 2070, May 2019. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: ethereum cache: eips-eip-2070.html plain text: eips-eip-2070.txt item: #326 of 3327 id: eips-eip-2098 author: eips title: eips-eip-2098 date: None words: 655 flesch: 35 summary: Citation Please cite this document as: Richard Moore (@ricmoo), Nick Johnson , ERC-2098: Compact Signature Representation, Ethereum Improvement Proposals, no. 2098, March 2019. With compact signatures, this can be reduced to 64 bytes, which remains 64 bytes when word-aligned, and in the case of RLP-encoded transactions saves the 1.5 bytes required for the yParity. keywords: yparity cache: eips-eip-2098.html plain text: eips-eip-2098.txt item: #327 of 3327 id: eips-eip-210 author: eips title: eips-eip-210 date: None words: 486 flesch: 33 summary: Citation Please cite this document as: Vitalik Buterin (@vbuterin), EIP-210: Blockhash refactoring [DRAFT], Ethereum Improvement Proposals, no. 210, February 2017. The EVM init code is: 0x6100f58061000e60003961010356600073fffffffffffffffffffffffffffffffffffffffe33141561005857600143035b801561005257600035610100820683015561010081061561003f57005b6101008104905061010082019150610022565b506100f3565b600060003512151561006e574360003512610071565b60005b156100e7576000356001814303035b6101008112151561009857600061010083061461009b565b60005b156100ba57610100830192506101008204915061010081049050610080565b610100811215156100d057600060a052602060a0f35b610100820683015460c052602060c0f350506100f2565b600060e052602060e0f35b5b505b6000f3 The EVM bytecode that the contract code should be set to is: 0x600073fffffffffffffffffffffffffffffffffffffffe33141561005857600143035b801561005257600035610100820683015561010081061561003f57005b6101008104905061010082019150610022565b506100f3565b600060003512151561006e574360003512610071565b60005b156100e7576000356001814303035b6101008112151561009857600061010083061461009b565b60005b156100ba57610100830192506101008204915061010081049050610080565b610100811215156100d057600060a052602060a0f35b610100820683015460c052602060c0f350506100f2565b600060e052602060e0f35b5b50 Rationale This removes the need for implementations to have an explicit way to look into historical block hashes, simplifying the protocol definition and removing a large component of the “implied state” (information that is technically state but is not part of the state tree) and thereby making the protocol more “pure”. keywords: block.number cache: eips-eip-210.html plain text: eips-eip-210.txt item: #328 of 3327 id: eips-eip-211 author: eips title: eips-eip-211 date: None words: 1050 flesch: 58 summary: A very useful example of such a worst-case situation is a generic forwarding contract; a contract that takes call data, potentially makes some checks and then forwards it as is to another contract. Its workings are very similar to the way calldata is handled already; after a call, return data is kept inside a virtual buffer from which the caller can copy it (or parts thereof) into memory. keywords: data; return cache: eips-eip-211.html plain text: eips-eip-211.txt item: #329 of 3327 id: eips-eip-2124 author: eips title: eips-eip-2124 date: None words: 2853 flesch: 69 summary: 0x63760190, Next: 1700000}}, // Last Spurious block {1700000, ID{Hash: 0x3ea159c7, Next: 4230000}}, // First Byzantium block {4229999, ID{Hash: 0x3ea159c7, Next: 4230000}}, // Last Byzantium block {4230000, ID{Hash: 0x97b544f3, Next: 4939394}}, // First Constantinople block {4939393, ID{Hash: 0x97b544f3, Next: 4939394}}, // Last Constantinople block {4939394, ID{Hash: 0xd6e2149b, Next: 6485846}}, // First Petersburg block {6485845, ID{Hash: 0xd6e2149b, Next: 6485846}}, // Last Petersburg block {6485846, ID{Hash: 0x4bc66396, Next: 0}}, // First Istanbul block {7500000, ID{Hash: 0x4bc66396, Next: 0}}, // Future Istanbul block }, }, // Rinkeby test cases { params. First and last Tangerine block {3, ID{Hash: 0xcb3a64bb, Next: 1035301}}, // First Spurious block {1035300, ID{Hash: 0xcb3a64bb, Next: 1035301}}, // Last Spurious block {1035301, ID{Hash: 0x8d748b57, Next: 3660663}}, // First Byzantium block {3660662, ID{Hash: 0x8d748b57, Next: 3660663}}, // Last Byzantium block {3660663, ID{Hash: 0xe49cab14, Next: 4321234}}, // First Constantinople block {4321233, ID{Hash: 0xe49cab14, Next: 4321234}}, // Last Constantinople block {4321234, ID{Hash: 0xafec6b27, Next: 5435345}}, // First Petersburg block {5435344, ID{Hash: 0xafec6b27, Next: 5435345}}, // Last Petersburg block {5435345, ID{Hash: 0xcbdb8838, Next: 0}}, // First Istanbul block {6000000, ID{Hash: 0xcbdb8838, Next: 0}}, // Future Istanbul block }, }, // Goerli test cases { params. keywords: block; fork; id{hash; local; remote cache: eips-eip-2124.html plain text: eips-eip-2124.txt item: #330 of 3327 id: eips-eip-2135 author: eips title: eips-eip-2135 date: None words: 1023 flesch: 45 summary: Compliant contracts should also carefully define access control, particularlly whether any EOA or contract account may or may not initiate a consume method in their own use case. Available: https://eips.ethereum.org/EIPS/eip-2135. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: asset; consumer; contract cache: eips-eip-2135.html plain text: eips-eip-2135.txt item: #331 of 3327 id: eips-eip-214 author: eips title: eips-eip-214 date: None words: 577 flesch: 51 summary: This EIP adds a way to call other contracts and restrict what they can do in the simplest way. This poses certain difficulties about smart contract engineers; after a regular call, unless you know the called contract, you cannot make any assumptions about the state of the contracts. keywords: ethereum; opcode cache: eips-eip-214.html plain text: eips-eip-214.txt item: #332 of 3327 id: eips-eip-2157 author: eips title: eips-eip-2157 date: None words: 1162 flesch: 40 summary: Abstract The storage extension will enable easy navigation and retrieval of type data that is intended to be of public use. This pattern of separating data type definitions and storage allows developers to create functional programming-like patterns on Ethereum, even though languages such as Solidity are not functional. keywords: data; ethereum; storage; type cache: eips-eip-2157.html plain text: eips-eip-2157.txt item: #333 of 3327 id: eips-eip-2159 author: eips title: eips-eip-2159 date: None words: 542 flesch: 29 summary: There is a similar, though more prescriptive, specification for beacon chain client metrics. Rationale The defined metrics are independent of Ethereum client implementation but provide sufficient information to create an overview dashboard to support monitoring a group of Ethereum nodes. keywords: clients; metrics cache: eips-eip-2159.html plain text: eips-eip-2159.txt item: #334 of 3327 id: eips-eip-2193 author: eips title: eips-eip-2193 date: None words: 988 flesch: 42 summary: We define an Alias registry contract, that keeps track of the human-readable identifiers for data resources, which exist in dType storage contracts. Moreover, EIP-137 is not flexible enough to address smart contract content, which can contain heterogeneous data that belongs to various accounts. keywords: alias; data; dtype cache: eips-eip-2193.html plain text: eips-eip-2193.txt item: #335 of 3327 id: eips-eip-2200 author: eips title: eips-eip-2200 date: None words: 2233 flesch: 74 summary: Regarding SSTORE gas cost and refunds, see Appendix for proofs of properties that this EIP satisfies. We will discuss the case separately for original value being zero and not zero, and use induction to prove some properties of SSTORE gas cost. keywords: case; cost; gas; value cache: eips-eip-2200.html plain text: eips-eip-2200.txt item: #336 of 3327 id: eips-eip-2228 author: eips title: eips-eip-2228 date: None words: 848 flesch: 55 summary: Names in use at the time of this writing include: “main net” “mainnet” “Main net” “Mainnet” Specification The network name for network ID 1 and chain ID 1 shall be Ethereum Mainnet, or just Mainnet if the context is known to be discussing Ethereum networks. Created 2019-08-04 Table of Contents Simple Summary Abstract Motivation Specification Trademark note Rationale Backwards Compatibility Test Cases Examples referencing the name of the network ✅ Examples referencing the network in a descriptive way ✅ Examples of other correct word usage ✅ Examples of poor word choice (avoid this) ❌ Copyright Simple Summary The Ethereum network with network ID 1 and chain ID 1 is named Ethereum Mainnet. keywords: network cache: eips-eip-2228.html plain text: eips-eip-2228.txt item: #337 of 3327 id: eips-eip-223 author: eips title: eips-eip-223 date: None words: 2404 flesch: 55 summary: contract ERC20Receiver { address tokenA; mapping (address => uint256) deposits; function deposit(uint _value, address _token) public { require(_token == tokenA); IERC20(_token).transferFrom(msg.sender, address(this), _value); deposits[msg.sender] += _value; } } ERC-223 tokens must be delivered to non-contract address or contract address in the same way with transfer function. Events Transfer event Transfer(address indexed _from, address indexed _to, uint256 _value, bytes _data) Triggered when tokens are transferred. keywords: contract; function; returns; token cache: eips-eip-223.html plain text: eips-eip-223.txt item: #338 of 3327 id: eips-eip-2242 author: eips title: eips-eip-2242 date: None words: 572 flesch: 53 summary: version is 0. data is an RLP-encoded list of binary data. Following the principle of “don’t pay for what you don’t use,” a distinct way of posting data on-chain, but without actually being usable within the EVM, is needed. keywords: data; postdata cache: eips-eip-2242.html plain text: eips-eip-2242.txt item: #339 of 3327 id: eips-eip-225 author: eips title: eips-eip-225 date: None words: 4093 flesch: 62 summary: []block{ {signer: A, voted: C, auth: false}, {signer: B}, {signer: C}, {signer: A, voted: D, auth: false}, {signer: B}, {signer: C}, {signer: A}, {signer: B, voted: D, auth: false}, {signer: C, voted: D, auth: false}, {signer: A}, {signer: B, voted: C, auth: false}, }, results: []string{A, B}, }, { // Votes from deauthorized signers are discarded immediately (deauth votes) signers: The challenge here is how to maintain a list of authorized signers that can change in time? keywords: auth; block; list; signer; string{"a cache: eips-eip-225.html plain text: eips-eip-225.txt item: #340 of 3327 id: eips-eip-2255 author: eips title: eips-eip-2255 date: None words: 964 flesch: 40 summary: The pattern of permissions requests (typically using Oauth2) is common around the web, making it a very familiar pattern: Many web3 applications today begin their sessions with a series of repetitive requests: Reveal your wallet address to this site. wallet_getPermissions The wallet_getPermissions method is used for getting an array of current permissions (empty by default). keywords: method; permissions; wallet_requestpermissions cache: eips-eip-2255.html plain text: eips-eip-2255.txt item: #341 of 3327 id: eips-eip-2256 author: eips title: eips-eip-2256 date: None words: 1099 flesch: 46 summary: This method is complementary to EIP-747, which proposes a way for sites to suggest users new assets to watch on their wallet. It also leads to the user being presented with asset options that the user does not care about, from various, unwanted airdrops. keywords: assets; type; user cache: eips-eip-2256.html plain text: eips-eip-2256.txt item: #342 of 3327 id: eips-eip-2266 author: eips title: eips-eip-2266 date: None words: 1423 flesch: 36 summary: event SetUp(bytes32 secretHash, address initiator, address participant, address tokenA, address tokenB, uint256 initiatorAssetAmount, uint256 participantAssetAmount, uint256 premiumAmount); Initiated This event indicates that initiator has filled and locked the token to be exchanged using the function initiate(). event Initiated(uint256 initiateTimestamp, bytes32 secretHash, address initiator, address participant, address initiatorAssetToken, uint256 initiatorAssetAmount, uint256 initiatorAssetRefundTimestamp); Participated This event indicates that participant has filled and locked the token to be exchanged using the function participate(). event Participated(uint256 participateTimestamp, bytes32 secretHash, address initiator, address participant, address participantAssetToken, uint256 participantAssetAmount, uint256 participantAssetRefundTimestamp); event PremiumFilled(uint256 fillPremiumTimestamp, bytes32 secretHash, address initiator, address participant, address premiumToken, uint256 premiumAmount, uint256 premiumRefundTimestamp); keywords: address; secrethash; swap cache: eips-eip-2266.html plain text: eips-eip-2266.txt item: #343 of 3327 id: eips-eip-2294 author: eips title: eips-eip-2294 date: None words: 714 flesch: 44 summary: EIP-2294: Explicit bound to Chain ID size Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-2294: Explicit bound to Chain ID size Adds a maximum value to the Chain ID parameter to avoid potential encoding issues that may occur when using large values of the parameter. Citation Please cite this document as: Zainan Victor Zhou (@xinbenlv), Alex Beregszaszi (@axic), EIP-2294: Explicit bound to Chain ID size [DRAFT], Ethereum Improvement Proposals, no. 2294, September 2019. keywords: chain cache: eips-eip-2294.html plain text: eips-eip-2294.txt item: #344 of 3327 id: eips-eip-2304 author: eips title: eips-eip-2304 date: None words: 1538 flesch: 44 summary: Multichain address resolution for ENS Authors Nick Johnson  Created 2019-09-09 Discussion Link https://discuss.ens.domains/t/new-standard-proposal-ens-multicoin-support/1148 Requires EIP-137 Table of Contents Abstract Motivation Specification Recommended accessor functions Address Encoding Example Implementation Backwards Compatibility Tests Copyright Abstract This EIP introduces new overloads for the the addr field for ENS resolvers, which permit resolution of addresses for other blockchains via ENS. Motivation With the increasing uptake of ENS by multi-coin wallets, wallet authors have requested the ability to resolve addresses for non-Ethereum chains inside ENS. keywords: address; addresses; ethereum; node cache: eips-eip-2304.html plain text: eips-eip-2304.txt item: #345 of 3327 id: eips-eip-2309 author: eips title: eips-eip-2309 date: None words: 1495 flesch: 52 summary: Abstract The optional ERC-721 Consecutive Transfer Extension provides a standardized event which could be emitted during the creation/transfer of one, or many non-fungible tokens. This standard does not set the expectation of how you might create/transfer many tokens it is only concerned with the event emitted after the creation, or transfer of ownership of these tokens. keywords: event; tokens; transfer cache: eips-eip-2309.html plain text: eips-eip-2309.txt item: #346 of 3327 id: eips-eip-2315 author: eips title: eips-eip-2315 date: None words: 3201 flesch: 57 summary: For Ethereum, this is a denial-of-service vulnerability that prevents us, at initialization time, from validating the safe use of EVM code and from compiling EVM code to machine code. Since we wish to support one-pass compilation of EVM code to machine code it is crucial that the EVM code be as well optimized as possible up front. keywords: code; gas; jump; return; stack cache: eips-eip-2315.html plain text: eips-eip-2315.txt item: #347 of 3327 id: eips-eip-2327 author: eips title: eips-eip-2327 date: None words: 650 flesch: 51 summary: EIP-2327: BEGINDATA opcode Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-2327: BEGINDATA opcode Authors Martin Lundfall (@MrChico) Created 2019-10-28 Discussion Link https://ethereum-magicians.org/t/new-opcode-begindata/3727 Table of Contents Simple Summary Abstract Motivation Specification Rationale Backwards Compatibility Test Cases Implementation Copyright Simple Summary Introduces a new opcode BEGINDATA, which indicates that the remaining bytes of the contract should be regarded as data rather than contract code and cannot be executed. If BEGINDATA is encountered during contract execution, it has the same semantics as STOP. keywords: begindata; contract cache: eips-eip-2327.html plain text: eips-eip-2327.txt item: #348 of 3327 id: eips-eip-233 author: eips title: eips-eip-233 date: None words: 626 flesch: 54 summary: The basic outline of a hardfork timeline should include: Hard deadline to accept proposals for this hard fork Soft deadline for major client implementations Projected date for testnet network upgrade Projected date for mainnet upgrade (the activation block number / projected date for this block) EIP Inclusion Process Anyone that wishes to propose a Core EIP for the hard fork should make a PR against the Meta EIP representing the hard fork. EIP-233: Formal process of hard forks Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Meta EIP-233: Formal process of hard forks Authors Alex Beregszaszi (@axic) Created 2017-03-23 Discussion Link https://ethereum-magicians.org/t/eip-233-formal-process-of-hard-forks/1387 Table of Contents Abstract Motivation Specification Timeline EIP Inclusion Process Template Rationale Copyright Abstract To describe the formal process of preparing and activating hard forks. keywords: eip; eips cache: eips-eip-233.html plain text: eips-eip-233.txt item: #349 of 3327 id: eips-eip-2330 author: eips title: eips-eip-2330 date: None words: 899 flesch: 58 summary: The gas cost when reading from registry style contract such as EIP-20s, ENS and other data contracts is very high, because they incur cross contract call cost, cost for ABI encoding, decoding and dispatching and finally loading the data. This EIP adds an EVM opcode to directly read external contract storage. keywords: contract; cost; gas cache: eips-eip-2330.html plain text: eips-eip-2330.txt item: #350 of 3327 id: eips-eip-2333 author: eips title: eips-eip-2333 date: None words: 3022 flesch: 7 summary: This has the upside of not requiring additional storage space for backup keys alongside BLS keys but does require that the Lamport signatures be used once and that the BLS key is no longer trusted after that point. In addition to the above, this method of deriving keys provides an emergency backup signature scheme that is resistant to quantum computers for in the event that BLS12-381 is ever deemed insecure. keywords: abandon; bls; key; keys; lamport; standard cache: eips-eip-2333.html plain text: eips-eip-2333.txt item: #351 of 3327 id: eips-eip-2334 author: eips title: eips-eip-2334 date: None words: 1266 flesch: 56 summary: The path for withdrawal keys is m/12381/3600/i/0 where i indicates the ith set of validator keys. The path for the signing key is m/12381/3600/i/0/0 where again, i indicates the ith set of validator keys. keywords: key; keys; purpose cache: eips-eip-2334.html plain text: eips-eip-2334.txt item: #352 of 3327 id: eips-eip-2335 author: eips title: eips-eip-2335 date: None words: 1647 flesch: 50 summary: Abstract A keystore is a mechanism for storing private keys. Inputs decryption_key, the octet string obtained from decryption key process cipher_message, the octet string obtained from keystore file from crypto.cipher.message checksum_message, the octet string obtained from keystore file from crypto.checksum.message Outputs valid_password, a boolean value indicating whether the password is valid Definitions a[0:3] returns a slice of a including octets 0, 1, 2 a | b is the concatenation of a with b Procedure 0. keywords: function; key; keystore; password cache: eips-eip-2335.html plain text: eips-eip-2335.txt item: #353 of 3327 id: eips-eip-234 author: eips title: eips-eip-234 date: None words: 1073 flesch: 61 summary: Rationale A client (dApp) who needs reliable notification of both log additions (on new blocks) and log removals (on chain reorgs) cannot achieve this while relying solely on subscriptions and filters. In order to deal with this while still providing a robust mechanism for internal block/log additional/removal, the client can maintain a blockchain internally (last n blocks) and only subscribe/poll for new blocks. keywords: block; logs cache: eips-eip-234.html plain text: eips-eip-234.txt item: #354 of 3327 id: eips-eip-2364 author: eips title: eips-eip-2364 date: None words: 954 flesch: 54 summary: Old packet: [protocolVersion, networkId, td, bestHash, genesisHash] New packet: [protocolVersion, networkId, td, bestHash, genesisHash, forkid], where forkid is [forkHash: [4]byte, forkNext: uint64] (fields per EIP-2124 ). By cross-validating forkid during the handshake, incompatible nodes can disconnect before expensive block exchanges and validations take place (PoW check, EVM execution, state reconstruction). keywords: ethereum; forkid; protocol cache: eips-eip-2364.html plain text: eips-eip-2364.txt item: #355 of 3327 id: eips-eip-2378 author: eips title: eips-eip-2378 date: None words: 548 flesch: 41 summary: Specification EIP Title Pipeline Status Date of Initial Decision REF EIP-663 Unlimited SWAP and DUP instructions ELIGIBLE 2019-11-01 🔗 EIP-1057 ProgPoW, a Programmatic Proof-of-Work ELIGIBLE 2019-11-01 🔗 EIP-1380 Reduced gas cost for call to self ELIGIBLE 2019-11-01 🔗 EIP-1559 Fee market change for ETH 1.0 chain ELIGIBLE 2019-11-01 🔗 EIP-1702 Generalized Account Versioning Scheme ELIGIBLE 2019-11-01 🔗 EIP-1962 EC arithmetic and pairings with runtime definitions ELIGIBLE 2019-11-01 🔗 EIP-1985 Sane limits for certain EVM parameters ELIGIBLE 2019-11-01 🔗 EIP-2046 Reduced gas cost for static calls made to precompiles ELIGIBLE 2019-11-01 🔗 EIP-2315 Simple Subroutines for the EVM ELIGIBLE 2020-02-21 🔗 EIP-2537 Precompile for BLS12-381 curve operations ELIGIBLE 2020-03-06 🔗 Rationale EIP Number Title Pipeline Status : Show the current status in the context of the EIP centric model. Specifically, the stage where the Core Developers vet the concept of an EIP and give a “green light” sufficient for EIP authors to move forward in development. keywords: eip; ethereum cache: eips-eip-2378.html plain text: eips-eip-2378.txt item: #356 of 3327 id: eips-eip-2384 author: eips title: eips-eip-2384 date: None words: 482 flesch: 49 summary: Estimating the added impact from the difficulty bomb on block times shows that we will see 20s block times near the end of December 2019 and 30s+ block times starting February 2020. Block times have been around 13.1s on average and now as of block 8,900,000 are around 14.3s. keywords: block; difficulty cache: eips-eip-2384.html plain text: eips-eip-2384.txt item: #357 of 3327 id: eips-eip-2386 author: eips title: eips-eip-2386 date: None words: 911 flesch: 51 summary: For hierarchical deterministic wallets this is the seed from which they calculate individual private keys. As such, the security of all keys generated by HD wallets is reduced to the security of the passphrase and strength of the encryption used to protect the seed, regardless of the security of the passphrase and strength of the encryption used to protect individual keystores. keywords: type; walletstore cache: eips-eip-2386.html plain text: eips-eip-2386.txt item: #358 of 3327 id: eips-eip-2387 author: eips title: eips-eip-2387 date: None words: 882 flesch: 60 summary: The primary problem with the Ice Age is that it is included in the complex mechanism that targets block times, which is an entirely separate in purpose. It artificially adds to the difficulty in such a way that the retargeting mechanism, at some point, can not adapt to the increase, and we see increased block times throughout the network. keywords: block; ice cache: eips-eip-2387.html plain text: eips-eip-2387.txt item: #359 of 3327 id: eips-eip-2390 author: eips title: eips-eip-2390 date: None words: 1869 flesch: 53 summary: Sets a resource (contract address, IP, ABI, TEXT, etc.) by node and geohash. All resources (contract addresses, IP addresses, ABIs, TEXT records, etc.) keywords: address; ens; geohash; location; node cache: eips-eip-2390.html plain text: eips-eip-2390.txt item: #360 of 3327 id: eips-eip-2400 author: eips title: eips-eip-2400 date: None words: 883 flesch: 39 summary: In wallets, for users sharing transaction receipts easier; In chat applications, as a reply to an EIP-681 transaction request; In crypto vending machines, a QRCode can be displayed when transactions are submitted; Anywhere transaction receipts are presented to users. Transaction hash not found is normal in fresh transactions, but can also mean that effectively a transaction was never submitted or have been replaced (through “higher gasPrice” nonce override or through an uncle/fork). keywords: ethereum; transaction cache: eips-eip-2400.html plain text: eips-eip-2400.txt item: #361 of 3327 id: eips-eip-2458 author: eips title: eips-eip-2458 date: None words: 624 flesch: 46 summary: EIP-2458: Updates and Updated-by Header Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🛑 Withdrawn Informational EIP-2458: Updates and Updated-by Header Authors Edson Ayllon (@edsonayllon) Created 2020-01-06 Discussion Link https://github.com/ethereum/EIPs/issues/2453 Table of Contents Simple Summary Abstract Motivation Specification updated-by updates Rationale Backwards Compatibility Implementation Security Considerations Copyright Simple Summary Adds EIP header options updates and updated-by to frontmatter of active EIPs for use as needed. Motivation Currently, EIP1 specifies EIP headers: updated, replaces, and superseded-by. keywords: eip cache: eips-eip-2458.html plain text: eips-eip-2458.txt item: #362 of 3327 id: eips-eip-2464 author: eips title: eips-eip-2464 date: None words: 1470 flesch: 53 summary: eth/65: transaction announcements and retrievals Introduces `NewPooledTransactionHashes`, `GetPooledTransactions`, and `PooledTransactions`. This permits reducing the bandwidth used for transaction propagation from linear complexity in the number of peers to square root; and also reducing the initial transaction exchange from 10s-100s MB to len(pool) * 32B ~= 128KB. keywords: network; protocol; transaction cache: eips-eip-2464.html plain text: eips-eip-2464.txt item: #363 of 3327 id: eips-eip-2470 author: eips title: eips-eip-2470 date: None words: 1049 flesch: 48 summary: A permissionless factory for deploy of keyless deterministic contracts addresses based on its bytecode. Account contracts are singletons in the point of view of each user, when wallets want to signal what chain id is intended, EIP-1191 should be used. keywords: address; contract; factory cache: eips-eip-2470.html plain text: eips-eip-2470.txt item: #364 of 3327 id: eips-eip-2474 author: eips title: eips-eip-2474 date: None words: 413 flesch: 44 summary: Abstract In proof-of-work blockchains, validators are known as miners. However this brings an overhead of a signed transaction by validator that does nothing, as msg.sender is never used, and there is no gas cost to EVM charge. keywords: ethereum; validator cache: eips-eip-2474.html plain text: eips-eip-2474.txt item: #365 of 3327 id: eips-eip-2477 author: eips title: eips-eip-2477 date: None words: 3212 flesch: 55 summary: In this approach, changing the metadata document will require updating on-chain tokenURIIntegrity and updating the schema document will require updating the tokenURISchemaIntegrity: ┌───────────────────────┐ ┌────────┐ ┌────────┐ │ TokenID │──────▶│Metadata│─────▶│ Schema │ └───────────────────────┘ └────────┘ └────────┘ ┌───────────────────────┐ ▲ ▲ │ tokenURIIntegrity │════════════╝ ║ └───────────────────────┘ ║ ┌───────────────────────┐ ║ │tokenURISchemaIntegrity│════════════════════════════╝ └───────────────────────┘ Approach E: Lastly, the schema can be referenced with integrity from the metadata and also using on-chain data. In this approach, changing the metadata document or the schema will require updating on-chain tokenURIIntegrity and the metadata document, additionally changing the schema requires updating the on-chain tokenURISchemaIntegrity: ┌───────────────────────┐ ┌────────┐ ┌────────┐ │ TokenID │──────▶│Metadata│═════▶│ Schema │ └───────────────────────┘ └────────┘ └────────┘ ┌───────────────────────┐ ▲ ▲ │ tokenURIIntegrity │════════════╝ ║ └───────────────────────┘ ║ ┌───────────────────────┐ ║ │tokenURISchemaIntegrity│════════════════════════════╝ └───────────────────────┘ Specification The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119. keywords: metadata; ─ ─; ─ ┐; ─ ┘; ┌ ─; ═ ═ cache: eips-eip-2477.html plain text: eips-eip-2477.txt item: #366 of 3327 id: eips-eip-2481 author: eips title: eips-eip-2481 date: None words: 1440 flesch: 43 summary: Clients could decide to share the same ids across multiple different request types since they are naturally separated anyway. Q: Why not demand request ids to be sequential? keywords: 0x0000000000000000000000000000000000000000000000000000000000000000; b_32; request cache: eips-eip-2481.html plain text: eips-eip-2481.txt item: #367 of 3327 id: eips-eip-2488 author: eips title: eips-eip-2488 date: None words: 296 flesch: 43 summary: Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. Citation Please cite this document as: Alex Beregszaszi (@axic), EIP-2488: Deprecate the CALLCODE opcode [DRAFT], Ethereum Improvement Proposals, no. 2488, December 2019. keywords: ethereum cache: eips-eip-2488.html plain text: eips-eip-2488.txt item: #368 of 3327 id: eips-eip-2494 author: eips title: eips-eip-2494 date: None words: 2527 flesch: 56 summary: This EIP describes Baby Jubjub, an elliptic curve defined over the finite field F_r which can be used inside any zk-SNARK circuit, allowing for the implementation of cryptographic primitives that make use of elliptic curves, such as the Pedersen Hash or the Edwards Digital Signature Algorithm (EdDSA). Generation of the Curve Baby Jubjub was conceived as a solution to the circuit implementation of cryptographic schemes that require elliptic curves. keywords: curve; edwards; point cache: eips-eip-2494.html plain text: eips-eip-2494.txt item: #369 of 3327 id: eips-eip-2515 author: eips title: eips-eip-2515 date: None words: 852 flesch: 49 summary: Citation Please cite this document as: James Hancock (@madeoftin), EIP-2515: Implement Difficulty Freeze [DRAFT], Ethereum Improvement Proposals, no. 2515, February 2020. The client maintainers are also positioned as the group that is most able to respond to an incoming Difficulty Freeze. keywords: difficulty; freeze cache: eips-eip-2515.html plain text: eips-eip-2515.txt item: #370 of 3327 id: eips-eip-2520 author: eips title: eips-eip-2520 date: None words: 578 flesch: 39 summary: function contenthash(bytes32 node, bytes calldata proto) external view returns (bytes memory); Resolver that supports multiple contenthash records MUST return true for supportsInterface with interface ID 0x6de03e07. Applications that are using ENS contenthash records SHOULD handle them in the following way: If the application only supports one hosting system (like directly handling ENS from IPFS/Swarm gateways), it SHOULD request contenthash with a specific type. ERC-2520: Multiple contenthash records for ENS Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-2520: Multiple contenthash records for ENS Authors Filip Štamcar (@filips123) keywords: contenthash; ens cache: eips-eip-2520.html plain text: eips-eip-2520.txt item: #371 of 3327 id: eips-eip-2525 author: eips title: eips-eip-2525 date: None words: 1646 flesch: 56 summary: Most wallet provider will set up the necessary entries without requiring any effort from the user. Additionally, if decentralized applications pick and choose only a handful of wallets to support, the current incumbent wallets will have a distinct advantage and new wallets will struggle to find adoption. keywords: enslogin; ethereum; provider; wallet cache: eips-eip-2525.html plain text: eips-eip-2525.txt item: #372 of 3327 id: eips-eip-2535 author: eips title: eips-eip-2535 date: None words: 4169 flesch: 52 summary: More technically, a diamond is a contract with external functions that are supplied by contracts called facets. Save gas by converting external functions to internal functions. keywords: address; contract; diamond; diamondcut; facet; function cache: eips-eip-2535.html plain text: eips-eip-2535.txt item: #373 of 3327 id: eips-eip-2537 author: eips title: eips-eip-2537 date: None words: 3197 flesch: 55 summary: We use additive notation for point operations, capital letters (P, Q) for points, small letters (a, b) for scalars. Gas schedule clarifications for G1/G2 Multiexponentiation Define a constant LEN_PER_PAIR that is equal to 160 for G1 operation and to 288 for G2 operation. keywords: bytes; encoding; field; gas; point cache: eips-eip-2537.html plain text: eips-eip-2537.txt item: #374 of 3327 id: eips-eip-2539 author: eips title: eips-eip-2539 date: None words: 2551 flesch: 55 summary: We use additive notation for point operations, capital letters (P, Q) for points, small letters (a, b) for scalars. Total encoding length for G1 point is thus 128 bytes and for G2 point is 256 bytes. keywords: bytes; encoding; field; point cache: eips-eip-2539.html plain text: eips-eip-2539.txt item: #375 of 3327 id: eips-eip-2542 author: eips title: eips-eip-2542 date: None words: 1018 flesch: 50 summary: EIP-2542: New opcodes TXGASLIMIT and CALLGASLIMIT Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-2542: New opcodes TXGASLIMIT and CALLGASLIMIT Authors Alex Forshtat  Created 2020-02-29 Discussion Link https://ethereum-magicians.org/t/eip-2542-add-txgaslimit-callgaslimit-txgasrefund-opcodes Table of Contents Simple Summary Abstract Motivation Specification Rationale Backwards Compatibility Forwards Compatibility Security considerations Implementation Copyright Simple Summary A mechanism to allow smart contracts to access information on gas limits for the current transaction and execution frame. Citation Please cite this document as: Alex Forshtat , EIP-2542: New opcodes TXGASLIMIT and CALLGASLIMIT keywords: ethereum; gas; opcodes cache: eips-eip-2542.html plain text: eips-eip-2542.txt item: #376 of 3327 id: eips-eip-2544 author: eips title: eips-eip-2544 date: None words: 1442 flesch: 36 summary: Motivation Many applications such as wallet providers, exchanges, and dapps have expressed a desire to issue ENS names for their users via custom subdomains on a shared parent domain. Further, this specification defines a new way for resolvers to resolve names, using a unified resolve() method that permits more flexible handling of name resolution. keywords: ens; resolution; resolver cache: eips-eip-2544.html plain text: eips-eip-2544.txt item: #377 of 3327 id: eips-eip-2565 author: eips title: eips-eip-2565 date: None words: 798 flesch: 20 summary: Citation Please cite this document as: Kelly Olson (@ineffectualproperty), Sean Gulley (@sean-sn), Simon Peffers (@simonatsn), Justin Drake (@justindrake), Dankrad Feist (@dankrad), EIP-2565: ModExp Gas Cost, Ethereum Improvement Proposals, no. 2565, March 2020. We also discovered that the current gas pricing formula could be improved to better estimate the computational complexity of various ModExp input variables. keywords: complexity; cost cache: eips-eip-2565.html plain text: eips-eip-2565.txt item: #378 of 3327 id: eips-eip-2566 author: eips title: eips-eip-2566 date: None words: 1422 flesch: 40 summary: The abi field can be combined with values parsed from the data field to recreate human readable contract function execution information. Although this is accomplished in an ad hoc fashion for ERC20-like contracts only, the motivation is the same: users deserve better information about the execution of contract functions they are relying on ProviderWallets to perform. keywords: contract; data; function cache: eips-eip-2566.html plain text: eips-eip-2566.txt item: #379 of 3327 id: eips-eip-2569 author: eips title: eips-eip-2569 date: None words: 2453 flesch: 48 summary: ----- IERC1155GetImageSvg.sol ------------------------- pragma solidity ^0.5.0; import ./IERC1155.sol; /** * @title ERC-1155 Multi Token Standard, retrieving SVG image for a token * @dev See https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1155.md */ contract IERC1155GetImageSvg is IERC1155 { function getTokenImageSvg(uint256 tokenId) external view returns (string memory); } // ----- * @param tokenId uint256 ID of the token to query */ function getTokenImageSvg(uint256 tokenId) external view returns (string memory) { require(_exists(tokenId), ERC1155GetImageSvg: SVG Image query for nonexistent token); return _tokenImageSvgs[tokenId]; } /** * @dev Internal function to set the token SVG image for a given token. keywords: image; svg; token cache: eips-eip-2569.html plain text: eips-eip-2569.txt item: #380 of 3327 id: eips-eip-2583 author: eips title: eips-eip-2583 date: None words: 2488 flesch: 58 summary: For opcodes which access the account trie, whenever the operation is invoked targeting an address which does not exist in the trie, then penalty gas is deducted from the available gas. This EIP adds a second rule in the following way: If the call does not transfer value and the callee does not exist, then penalty gas is added to the cost. keywords: eip; gas; penalty; trie; value cache: eips-eip-2583.html plain text: eips-eip-2583.txt item: #381 of 3327 id: eips-eip-2584 author: eips title: eips-eip-2584 date: None words: 1391 flesch: 61 summary: At block height h₂, before the execution of ϒ, Hᵣ ≡ Hᵣ², i.e. the value before the execution of the transition function is set to the root of the converted binary base trie; Hₒ is still present in the block tree, however the overlay trie content can only be read from or deleted; At block height h ≥ h₂, before the execution of ϒ, N accounts are being deleted from the binary overlay trie and inserted into the binary base trie; Upon executing a state write, ϒ will insert or update the value into the base trie. Citation Please cite this document as: Guillaume Ballet (@gballet), EIP-2584: Trie format transition with overlay trees [DRAFT], Ethereum Improvement Proposals, no. 2584, April 2020. keywords: binary; overlay; phase; trie cache: eips-eip-2584.html plain text: eips-eip-2584.txt item: #382 of 3327 id: eips-eip-2593 author: eips title: eips-eip-2593 date: None words: 1922 flesch: 61 summary: User bids at or over current price tier, gets transaction mined reliably. User bids within the range of prices that have been recently accepted, likely over-pays slightly. keywords: bids; price; user cache: eips-eip-2593.html plain text: eips-eip-2593.txt item: #383 of 3327 id: eips-eip-2612 author: eips title: eips-eip-2612 date: None words: 1386 flesch: 47 summary: Backwards Compatibility There are already a couple of permit functions in token contracts implemented in contracts in the wild, most notably the one introduced in the dai.sol. Signed Permit messages are censorable. keywords: deadline; eip-20; owner; permit cache: eips-eip-2612.html plain text: eips-eip-2612.txt item: #384 of 3327 id: eips-eip-2615 author: eips title: eips-eip-2615 date: None words: 1662 flesch: 47 summary: Mortgage functions The following diagram demonstrates the mortgaging functionality. Their rights are as follows: A Lien Holder has the right to: Transfer the Owner role Transfer the User role An Owner has the right to: Transfer the Owner role Transfer the User role A User has the right to: Transfer the User role ERC-2615 Interface event TransferUser(address indexed from, address indexed to, uint256 indexed itemId, address operator); event ApprovalForUser(address indexed user, address indexed approved, uint256 itemId); event TransferOwner(address indexed from, address indexed to, uint256 indexed itemId, address operator); event ApprovalForOwner(address indexed owner, address indexed approved, uint256 itemId); event ApprovalForAll(address indexed owner, address indexed operator, bool approved); event LienApproval(address indexed to, uint256 indexed itemId); event TenantRightApproval(address indexed to, uint256 indexed itemId); event LienSet(address indexed to, uint256 indexed itemId, bool status); event TenantRightSet(address indexed to, uint256 indexed itemId,bool status); function balanceOfOwner(address owner) public view returns (uint256); function balanceOfUser(address user) public view returns (uint256); function userOf(uint256 itemId) public view returns (address); function ownerOf(uint256 itemId) public view returns (address); function safeTransferOwner(address from, address to, uint256 itemId) public; keywords: function; itemid; public; uint256 cache: eips-eip-2615.html plain text: eips-eip-2615.txt item: #385 of 3327 id: eips-eip-2645 author: eips title: eips-eip-2645 date: None words: 654 flesch: 36 summary: We leverage existing work on Key Derivation (BIP32, BIP39 and BIP44) to define an efficient way to securely produce CIP L2s private keys, as well as creating domain separation between Layer-2 applications. Rationale This EIP specifies two aspects of keys derivation in the context of Hierarchical Wallets: Derivation Path keywords: derivation; layer-2 cache: eips-eip-2645.html plain text: eips-eip-2645.txt item: #386 of 3327 id: eips-eip-2666 author: eips title: eips-eip-2666 date: None words: 1023 flesch: 53 summary: Gas costs of many contracts is expected to reduce that may break re-entrancy protection measures based on fixed gas costs. and it may be necessary to adjust costs of some precompiles that may have taken old large cost (700 gas) into account and tried to compensate for it Some precompiles are overpriced and their pricing formulas do not reflect the structure of underlying functions Keccak256 built-in function (opcode) in EVM has pricing that does not reflect underlying hash function structure Specification keywords: gas; precompile cache: eips-eip-2666.html plain text: eips-eip-2666.txt item: #387 of 3327 id: eips-eip-2677 author: eips title: eips-eip-2677 date: None words: 510 flesch: 46 summary: This also leads to two nice properties: instruction offset in code fits 16-bit value, code size fits 16-bit value. Since EIP-170 was implemented, there has been a size limit of 24576 (0x6000) on contract code. keywords: code; size cache: eips-eip-2677.html plain text: eips-eip-2677.txt item: #388 of 3327 id: eips-eip-2678 author: eips title: eips-eip-2678 date: None words: 4680 flesch: 62 summary: Package names must begin with a lowercase letter and be comprised of only the lowercase letters a-z, numeric characters 0-9, and the dash character -. Package names must not exceed 255 characters in length. keywords: contract; field; format; key; object; package; type; value cache: eips-eip-2678.html plain text: eips-eip-2678.txt item: #389 of 3327 id: eips-eip-2680 author: eips title: eips-eip-2680 date: None words: 985 flesch: 45 summary: A Go implementation of the Amazon S3 layout can be found at https://github.com/wealdtech/go-eth2-wallet-s3. Security Considerations Locations for wallet stores are defined to be within each user’s personal space, reducing the possibility of accidental exposure of information. Motivation A standard layout for wallets and accounts allows interoperability between validators. keywords: ethereum; string; wallet cache: eips-eip-2680.html plain text: eips-eip-2680.txt item: #390 of 3327 id: eips-eip-2681 author: eips title: eips-eip-2681 date: None words: 461 flesch: 53 summary: Citation Please cite this document as: Alex Beregszaszi (@axic), EIP-2681: Limit account nonce to 2^64-1, Ethereum Improvement Proposals, no. 2681, April 2020. Limit account nonce to 2^64-1 Authors Alex Beregszaszi (@axic) Created 2020-04-25 Table of Contents Abstract Motivation Specification Rationale Backwards Compatibility Security Considerations Copyright Abstract Limit account nonce to be between 0 and 2^64-1. Motivation Account nonces are currently specified to be arbitrarily long unsigned integers. keywords: nonce cache: eips-eip-2681.html plain text: eips-eip-2681.txt item: #391 of 3327 id: eips-eip-2696 author: eips title: eips-eip-2696 date: None words: 904 flesch: 44 summary: Citation Please cite this document as: Micah Zoltu (@MicahZoltu), Erik Marks (@rekmarks), EIP-2696: JavaScript `request` method RPC transport, Ethereum Improvement Proposals, no. 2696, June 2020. Security Considerations The relationship between Ethereum Provider and client is a trusted one, where it is assumed that the user implicitly trusts the Ethereum Provider which is how it managed to get injected into the client, or the client expressly pulled in a connection to it. keywords: request; rpc cache: eips-eip-2696.html plain text: eips-eip-2696.txt item: #392 of 3327 id: eips-eip-2700 author: eips title: eips-eip-2700 date: None words: 596 flesch: 47 summary: Citation Please cite this document as: Micah Zoltu (@MicahZoltu), Erik Marks (@rekmarks), EIP-2700: JavaScript Provider Event Emitter, Ethereum Improvement Proposals, no. 2700, June 2020. How/where this Ethereum Provider object is exposed is left to future standards. keywords: ethereum; provider cache: eips-eip-2700.html plain text: eips-eip-2700.txt item: #393 of 3327 id: eips-eip-2711 author: eips title: eips-eip-2711 date: None words: 2021 flesch: 50 summary: Authors Micah Zoltu (@MicahZoltu) Created 2020-06-11 Discussion Link https://ethereum-magicians.org/t/eip-2711-separate-gas-payer-from-msg-sender/4353 Requires EIP-2718 Table of Contents Simple Summary Abstract Motivation Sponsored Transactions Batch Transactions Expiring Transactions Specification Definitions New Transaction Type New Transaction Receipt Rationale One Monolithic EIP ChainID not encoded with v Optionality of ChainID Optionality of ValidUntil SENDER sets gasLimit and gasPrice SENDER sets gasLimit, GAS_PAYER sets gasPrice GAS_PAYER sets gasLimit and gasPrice Nonces ValidUntil ValidUntil as timestamp instead of block number Backwards Compatibility Test Cases Implementation Security Considerations Copyright Simple Summary Creates a new transaction type that supports sponsored transactions (separate gas payer from sender), batch transactions (multiple transactions executed in sequence), and expiring transactions (transactions which are not valid after a certain timestamp). Abstract An EIP-2718 transaction with the type number 2 is a new type of transaction that includes support for: Sponsored Transactions: an optional additional signature from which the account that will pay for gas (GAS_PAYER) can be recovered Batch Transactions: multiple transactions from the same sender that will be executed in sequence Expiring Transactions: an optional validUntil field that makes the transaction invalid after a certain point in time Motivation Sponsored Transactions With the advent of tokens and especially stable coins, it has become common for users to not hold ETH in an account while they may have other assets of value in that account. keywords: gas; nonce; sender; transaction cache: eips-eip-2711.html plain text: eips-eip-2711.txt item: #394 of 3327 id: eips-eip-2718 author: eips title: eips-eip-2718 date: None words: 1122 flesch: 44 summary: These all need to be defined in a way that is mutually compatible, which quickly becomes burdensome to EIP authors and to clients who now have to follow complex rules for differentiating transaction type. Motivation In the past, when we have wanted to add new transaction types we have had to ensure they were backward compatible with all other transactions, meaning that you could differentiate them based only on the encoded payload, and it was not possible to have a transaction that matched both types. keywords: byte; transaction; transactiontype cache: eips-eip-2718.html plain text: eips-eip-2718.txt item: #395 of 3327 id: eips-eip-2733 author: eips title: eips-eip-2733 date: None words: 1517 flesch: 51 summary: Transaction packages are an alternative that allow multiple transactions to be bundled into one package and executed atomically, similarly to how relay contracts operate. Although this functionality is already possible as described above, workflows using transaction packages are more robust, because they are protected from future changes to the gas schedule. keywords: package; transaction; u256 cache: eips-eip-2733.html plain text: eips-eip-2733.txt item: #396 of 3327 id: eips-eip-2746 author: eips title: eips-eip-2746 date: None words: 2154 flesch: 52 summary: If Attributes are defined to exist as data within other contracts, the implementation must take into account the possibility that RuleTree owners must have the security to access the data in those contracts. Rule types can be implemented as any type of action (greater than, less than, etc.) @param _owner Owner/ID of the RuleTree @param _ruleSetName ID/Name of the RuleSet to which the Rule will be added @param _ruleName ID/Name of the Rule being added @param _attrName ID/Name of the Attribute upon which the Rule is invoked @param _ruleType ID of the type of Rule @param _rightHandValue keywords: @param; owner; ruleset; ruletree cache: eips-eip-2746.html plain text: eips-eip-2746.txt item: #397 of 3327 id: eips-eip-2767 author: eips title: eips-eip-2767 date: None words: 1141 flesch: 43 summary: ERC-2767: Contract Ownership Governance Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-2767: Contract Ownership Governance Authors Soham Zemse (@zemse), Nick Mudge (@mudgen) Created 2020-07-04 Discussion Link https://github.com/ethereum/EIPs/issues/2766 Requires EIP-20, EIP-165, EIP-173 Table of Contents Simple Summary Abstract Motivation Specification ERC-20 Governance Token ERC-165 Interface Identification Rationale Backwards Compatibility Implementation Security Considerations Copyright Simple Summary A standard for Governance contracts that holds the administrative ownership of other smart contracts with voting power distributed as ERC-20 tokens. /// @return `true` if the contract implements `interfaceID` and /// `interfaceID` is not 0xffffffff, `false` otherwise function supportsInterface(bytes4 interfaceID) external view returns (bool); } Rationale The goals of this EIP have been the following: Standardize API of Governance contracts to make it easy for analysis tools to be built. keywords: contract; erc-2767; governance cache: eips-eip-2767.html plain text: eips-eip-2767.txt item: #398 of 3327 id: eips-eip-2770 author: eips title: eips-eip-2770 date: None words: 1188 flesch: 25 summary: Forwarder data type registration Request struct MUST contain the following fields in this exact order: struct ForwardRequest { address from; address to; uint256 value; uint256 gas; uint256 nonce; bytes data; uint256 validUntil; } from - an externally-owned account making the request to - a destination address, normally a smart-contract value - an amount of Ether to transfer to the destination gas - an amount of gas limit to set for the execution nonce - an on-chain tracked nonce of a transaction data - the data to be sent to the destination validUntil - the highest block number the request can be forwarded in, or 0 if request validity is not time-limited The request struct MAY include any other fields, including nested structs, if necessary. Motivation There is a growing interest in making it possible for Ethereum contracts to accept calls from externally owned accounts that do not have ETH to pay for gas. keywords: contract; data; forwarder; uint256 cache: eips-eip-2770.html plain text: eips-eip-2770.txt item: #399 of 3327 id: eips-eip-2771 author: eips title: eips-eip-2771 date: None words: 1182 flesch: 32 summary: ERC-2771: Secure Protocol for Native Meta Transactions Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: ERC ERC-2771: Secure Protocol for Native Meta Transactions A contract interface for receiving meta transactions through a trusted forwarder Authors Ronan Sandford (@wighawag), Liraz Siri (@lirazsiri), Dror Tirosh (@drortirosh), Yoav Weiss (@yoavw), Alex Forshtat (@forshtat), Hadrien Croubois (@Amxx), Sachin Tomar (@tomarsachin2271), Patrick McCorry (@stonecoldpat), Nicolas Venturo (@nventuro), Fabian Vogelsteller (@frozeman), Gavin John (@Pandapip1) Created 2020-07-01 Table of Contents Abstract Motivation Specification Definitions Example Flow Extracting The Transaction Signer address Protocol Support Discovery Mechanism Rationale Reference Implementation Recipient Example Security Considerations Copyright Abstract This EIP defines a contract-level protocol for Recipient contracts to accept meta-transactions through trusted Forwarder contracts. Solutions that allow for third parties to pay for gas costs are called meta transactions. keywords: contract; recipient; transactions cache: eips-eip-2771.html plain text: eips-eip-2771.txt item: #400 of 3327 id: eips-eip-2780 author: eips title: eips-eip-2780 date: None words: 1089 flesch: 51 summary: Citation Please cite this document as: Matt Garnett (@lightclient), Uri Klarman (@uriklarman), EIP-2780: Reduce intrinsic transaction gas [DRAFT], Ethereum Improvement Proposals, no. 2780, July 2020. There had been concerns that reducing the intrinsic cost of transactions from 21,000 to 7,000 would boost the savings achiieved using gas tokens, however these concerns are unfounded. keywords: cost; ethereum; gas cache: eips-eip-2780.html plain text: eips-eip-2780.txt item: #401 of 3327 id: eips-eip-2786 author: eips title: eips-eip-2786 date: None words: 487 flesch: 46 summary: Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. Security Considerations The relationship between Ethereum Provider and client is a trusted one, where it is assumed that the user implicitly trusts the Ethereum Provider which is how it managed to get injected into the client, or the client expressly pulled in a connection to it. keywords: provider cache: eips-eip-2786.html plain text: eips-eip-2786.txt item: #402 of 3327 id: eips-eip-2803 author: eips title: eips-eip-2803 date: None words: 728 flesch: 53 summary: Motivation Many Ethereum DApps presently require users to approve multiple transactions in order to produce one effect - for example, the common pattern of first approving a contract to spend a token, then calling that contract. EIP-2803: Rich Transactions Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-2803: Rich Transactions Support 'rich transactions' by allowing transactions from externally owned accounts to execute bytecode directly. keywords: address; transaction cache: eips-eip-2803.html plain text: eips-eip-2803.txt item: #403 of 3327 id: eips-eip-2831 author: eips title: eips-eip-2831 date: None words: 1065 flesch: 47 summary: => { console.error(`Error sending transaction: ${error.code}: ${error.message}`); }); Citation Please cite this document as: Gregory Markou (@GregTheGreek), EIP-2831: Transaction Replacement Message Type [DRAFT], Ethereum Improvement Proposals, no. 2831, July 2020. One specific innovation was transaction replacement, offering users the ability to effectively cancel a previously sent transaction. keywords: newtx; nonce; transaction cache: eips-eip-2831.html plain text: eips-eip-2831.txt item: #404 of 3327 id: eips-eip-2844 author: eips title: eips-eip-2844 date: None words: 1252 flesch: 51 summary: Motivation There has been one main previous effort (#130, #1098) to add decryption to Ethereum wallets in a standard way. Adding support for JOSE and DIDs will enable Ethereum wallets to support a wide range of new use cases such as more traditional authentication using JWTs, as well as new emerging technologies such as Secure Data Stores and encrypted data in IPFS. keywords: ethereum; json; methods cache: eips-eip-2844.html plain text: eips-eip-2844.txt item: #405 of 3327 id: eips-eip-2848 author: eips title: eips-eip-2848 date: None words: 2866 flesch: 59 summary: Clients MUST add the message with motivations to the message list and they MUST NOT consider MOM messages sent by that address to be valid anymore, ever. Apart from message list, MOM clients SHOULD be able to download the content of the messages and to show them to the user. keywords: clients; message; multihash; parameter cache: eips-eip-2848.html plain text: eips-eip-2848.txt item: #406 of 3327 id: eips-eip-2876 author: eips title: eips-eip-2876 date: None words: 1930 flesch: 47 summary: Citation Please cite this document as: Jonathan Underwood (@junderw), ERC-2876: Deposit contract and address standard [DRAFT], Ethereum Improvement Proposals, no. 2876, August 2020. Therefore, merchant and centralized exchange apps are forced between taking on one of the following: Large security risk (deposit accounts are hot wallets) keywords: address; byte; contract; deposit; format cache: eips-eip-2876.html plain text: eips-eip-2876.txt item: #407 of 3327 id: eips-eip-2917 author: eips title: eips-eip-2917 date: None words: 1201 flesch: 56 summary: Furthermore, users need to remove their collateral before getting the rewards, which can be harmful for their rewards. Therefore, the fairness and transparency properties cannot be reflected and this can even create the investment barrier for users. keywords: block; interests; user cache: eips-eip-2917.html plain text: eips-eip-2917.txt item: #408 of 3327 id: eips-eip-2926 author: eips title: eips-eip-2926 date: None words: 1871 flesch: 61 summary: In addition to the above, codeTrie commits to a list of code chunks = [(FIO_0, code_0), ..., (FIO_n, code_n)] which are derived from C in a way that: n < MAX_CHUNK_COUNT. Because code chunks are also stored in the trie, this EIP would benefit from the witness size reduction offered by the binarification. keywords: chunk; code; coderoot; merkleization; trie cache: eips-eip-2926.html plain text: eips-eip-2926.txt item: #409 of 3327 id: eips-eip-2929 author: eips title: eips-eip-2929 date: None words: 2695 flesch: 52 summary: Motivation Generally, the main function of gas costs of opcodes is to be an estimate of the time needed to process that opcode, the goal being for the gas limit to correspond to a limit on the time needed to process a block. Gas costs were increased to mitigate this, but recent numbers suggest they were not increased enough. keywords: address; contract; cost; gas; sstore; storage cache: eips-eip-2929.html plain text: eips-eip-2929.txt item: #410 of 3327 id: eips-eip-2930 author: eips title: eips-eip-2930 date: None words: 1215 flesch: 45 summary: However, this EIP proposes only a 10% initial discount to access lists, so there is almost no cost to not bothering with access list generation and only making a simple transaction. Transaction size bloating Average block size will increase as a result of access lists being used. keywords: access; list; transaction cache: eips-eip-2930.html plain text: eips-eip-2930.txt item: #411 of 3327 id: eips-eip-2935 author: eips title: eips-eip-2935 date: None words: 506 flesch: 37 summary: Citation Please cite this document as: Vitalik Buterin (@vbuterin), Tomasz Stanczak (@tkstanczak), EIP-2935: Save historical block hashes in state [DRAFT], Ethereum Improvement Proposals, no. 2935, September 2020. These protocols can be made much simpler if blocks contained a quick Merkle path to historical blocks. keywords: block; ethereum cache: eips-eip-2935.html plain text: eips-eip-2935.txt item: #412 of 3327 id: eips-eip-2936 author: eips title: eips-eip-2936 date: None words: 508 flesch: 43 summary: Specification After FORK_BLOCK_NUM, a new opcode, EXTCLEAR, is enabled at 0x5C to clear storage for SELFDESTRUCTed contracts. Motivation SELFDESTRUCT (0xFF) is unnecessarily complex because it clears an unbounded amount of contract storage. keywords: contract; storage cache: eips-eip-2936.html plain text: eips-eip-2936.txt item: #413 of 3327 id: eips-eip-2937 author: eips title: eips-eip-2937 date: None words: 351 flesch: 36 summary: Citation Please cite this document as: Vitalik Buterin (@vbuterin), EIP-2937: SET_INDESTRUCTIBLE opcode [DRAFT], Ethereum Improvement Proposals, no. 2937, September 2020. Available: https://eips.ethereum.org/EIPS/eip-2937. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: opcode cache: eips-eip-2937.html plain text: eips-eip-2937.txt item: #414 of 3327 id: eips-eip-2938 author: eips title: eips-eip-2938 date: None words: 4333 flesch: 48 summary: Require SET_INDESTRUCTIBLE Require that contracts targeted by AA transactions begin with EIP-2937’s SET_INDESTRUCTIBLE opcode. AA transactions targeting contracts that do not begin with SET_INDESTRUCTIBLE are invalid, and cannot be included in blocks. keywords: account; contract; execution; gas; tenant; transaction cache: eips-eip-2938.html plain text: eips-eip-2938.txt item: #415 of 3327 id: eips-eip-2942 author: eips title: eips-eip-2942 date: None words: 568 flesch: 39 summary: A single string that can faithfully represent any kind of EthPM asset, across the mainnet or testnets, reduces the mental overload for new users, minimizes configuration requirements for frameworks, and simplifies distribution of packages for package authors. Being able to specify a package, registry, or release with a single string makes simplifies the steps required to install, publish, or distribute EthPM packages. keywords: ethpm; package cache: eips-eip-2942.html plain text: eips-eip-2942.txt item: #416 of 3327 id: eips-eip-2970 author: eips title: eips-eip-2970 date: None words: 343 flesch: 39 summary: Abstract Motivation The main intended use case is to allow account abstraction (EIP 2938) to be extended so that accounts can allow static calls from the outside (which are harmless to AA’s security model) but not state-changing calls. Citation Please cite this document as: Vitalik Buterin (@vbuterin), EIP-2970: IS_STATIC opcode [DRAFT], Ethereum Improvement Proposals, no. 2970, September 2020. keywords: ethereum cache: eips-eip-2970.html plain text: eips-eip-2970.txt item: #417 of 3327 id: eips-eip-2972 author: eips title: eips-eip-2972 date: None words: 1310 flesch: 46 summary: EIP-2972: Wrapped Legacy Transactions Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🛑 Withdrawn Standards Track: Core EIP-2972: Wrapped Legacy Transactions Authors Micah Zoltu (@MicahZoltu) Created 2020-09-12 Discussion Link https://ethereum-magicians.org/t/eip-2972-wrapped-legacy-transactions/4604 Requires EIP-155, EIP-2718 Table of Contents Simple Summary Abstract Motivation Specification Definitions Transactions Receipts Rationale Signature doesn’t include transaction type as first signature byte Two transaction types instead of one Signature separate from signed data SSZ for serialization Deprecating legacy transactions Max length of logs and logs data Backwards Compatibility Test Cases Implementation Security Considerations Copyright Simple Summary Two new transaction types for wrapping legacy transactions with and without a chain ID. Abstract Introduces two new EIP-2718 transactions that are signature compatible with legacy transactions and can be automatically upgraded by any client. keywords: legacy; signature; transactions cache: eips-eip-2972.html plain text: eips-eip-2972.txt item: #418 of 3327 id: eips-eip-2976 author: eips title: eips-eip-2976 date: None words: 835 flesch: 36 summary: Clients MUST NOT send new transaction types before they believe the fork block is reached. Motivation EIP-2718 introduced new transaction types for blocks (which presents itself in the makeup of a block header’s transaction root and receipts root). keywords: transaction; transactiontype cache: eips-eip-2976.html plain text: eips-eip-2976.txt item: #419 of 3327 id: eips-eip-2980 author: eips title: eips-eip-2980 date: None words: 1457 flesch: 43 summary: ** * @dev getter to determine if address is in frozenlist */ function frozenlist(address _operator) external view returns (bool); / ** * @dev getter to determine if address is in whitelist */ function whitelist(address _operator) external view returns (bool); } keywords: address; issuer; operator cache: eips-eip-2980.html plain text: eips-eip-2980.txt item: #420 of 3327 id: eips-eip-2981 author: eips title: eips-eip-2981 date: None words: 2249 flesch: 46 summary: At a glance, here’s an example conversation summarizing NFT royalty payments today: Artist: “Do you support royalty payments on your platform?” Marketplace: “Yes we have royalty payments, but if your NFT is sold on another marketplace then we cannot enforce this payment.” ERC-2981: NFT Royalty Standard Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: ERC ERC-2981: NFT Royalty Standard Authors Zach Burks (@vexycats), James Morgan (@jamesmorgan), Blaine Malone (@blmalone), James Seibel (@seibelj) Created 2020-09-15 Requires EIP-165 Table of Contents Simple Summary Abstract Motivation Specification Examples Rationale Optional royalty payments Simple royalty payments to a single address Royalty payment percentage calculation Unit-less royalty payment across all marketplaces, both on-chain and off-chain Universal Royalty Payments Backwards Compatibility Security Considerations Copyright Simple Summary A standardized way to retrieve royalty payment information for non-fungible tokens (NFTs) to enable universal support for royalty payments across all NFT marketplaces and ecosystem participants. keywords: nft; payment; royalty; standard cache: eips-eip-2981.html plain text: eips-eip-2981.txt item: #421 of 3327 id: eips-eip-2982 author: eips title: eips-eip-2982 date: None words: 8106 flesch: 44 summary: To participate in the PoS consensus, users submit validator deposits to the deposit contract. In phase 0, a “withdrawn” validator cannot actually withdraw to anywhere yet; the only distinction is that it is protected from validator penalties and does not have any responsibilities. keywords: beacon; block; chain; consensus; deposit; eth2; ethereum; fork; key; phase; proof; time; validator cache: eips-eip-2982.html plain text: eips-eip-2982.txt item: #422 of 3327 id: eips-eip-2997 author: eips title: eips-eip-2997 date: None words: 861 flesch: 47 summary: Test Cases We present 4 examples of impersonated address derivation: Example 0 address 0x0000000000000000000000000000000000000000 salt 0x0000000000000000000000000000000000000000000000000000000000000000 result: 0xFFC4F52F884A02BCD5716744CD622127366F2EDF Example 1 address 0xdeadbeef00000000000000000000000000000000 salt 0x0000000000000000000000000000000000000000000000000000000000000000 result: 0x85F15E045E1244AC03289B48448249DC0A34AA30 Example 2 address 0xdeadbeef00000000000000000000000000000000 salt 0x000000000000000000000000feed000000000000000000000000000000000000 result: 0x2DB27D1D6BE32C9ABFA484BA3D591101881D4B9F Example 3 address 0x00000000000000000000000000000000deadbeef salt 0x00000000000000000000000000000000000000000000000000000000cafebabe result: 0x5004E448F43EFE3C7BF32F94B83B843D03901457 Security Considerations The address derivation scheme prevents address collision with another deployed contract or an externally owned account, as the impersonated sender address is derived from the real caller address and a salt. An option is to omit the zeros32 field: the resulting length of the Keccak pre-image for IMPERSONATECALL address is 53 bytes , which does not generate address collision. keywords: address; opcode; salt cache: eips-eip-2997.html plain text: eips-eip-2997.txt item: #423 of 3327 id: eips-eip-3 author: eips title: eips-eip-3 date: None words: 453 flesch: 63 summary: The implementation should be fairly simple and would provide a cheap and way to protect against call stack attacks. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: stack cache: eips-eip-3.html plain text: eips-eip-3.txt item: #424 of 3327 id: eips-eip-3000 author: eips title: eips-eip-3000 date: None words: 1001 flesch: 32 summary: Container memory container, bytes memory reason) virtual public returns (uint256 resolverId); event Challenged(bytes32 indexed containerHash, address indexed actor, bytes reason, uint256 resolverId, ERC3000Data. Container memory container, uint256 resolverId) virtual public returns (bytes[] memory execResults); event Resolved(bytes32 indexed containerHash, address indexed actor, bool approved); / keywords: container; standard; struct cache: eips-eip-3000.html plain text: eips-eip-3000.txt item: #425 of 3327 id: eips-eip-3005 author: eips title: eips-eip-3005 date: None words: 3023 flesch: 53 summary: Can EIP-2612 nonces mapping be re-used? Token transfers Backwards Compatibility Test Cases Security Considerations Forging a meta transaction Replay attacks Signature validation Malicious relayer forcing a user into over-spending Front-running attack A malicious (or too impatient) user sending a meta transaction with the same nonce through multiple relayers at once Too big due block number Copyright Simple Summary Defines an extension function for ERC-20 (and other fungible token standards), which allows receiving and processing a batch of meta transactions. Abstract This EIP defines a new function called processMetaBatch() that extends any fungible token standard, and enables batched meta transactions coming from many senders in one on-chain transaction. keywords: function; meta; relayer; transaction cache: eips-eip-3005.html plain text: eips-eip-3005.txt item: #426 of 3327 id: eips-eip-3009 author: eips title: eips-eip-3009 date: None words: 2481 flesch: 19 summary: The biggest issue with the use of sequential nonces is that it does not allow users to perform more than one transaction at time without risking their transactions failing, because: DApps may unintentionally reuse nonces that have not yet been processed in the blockchain. Example: const data = { types: { EIP712Domain: [ { name: name, type: string }, { name: version, type: string }, { name: chainId, type: uint256 }, { name: verifyingContract, type: address }, ], TransferWithAuthorization: [ { name: from, type: address }, { name: to, type: address }, { name: value, type: uint256 }, { name: validAfter, type: uint256 }, { name: validBefore, type: uint256 }, { name: nonce, type: bytes32 }, ], }, domain: { name: tokenName, version: tokenVersion, chainId: selectedChainId, verifyingContract: tokenAddress, }, primaryType: TransferWithAuthorization, message: { from: userAddress, to: recipientAddress, value: amountBN.toString(10), validAfter: 0, validBefore: Math.floor(Date.now() / 1000) + 3600, // Valid for an hour nonce: Web3.utils.randomHex(32), }, }; const signature = await ethereum.request({ method: eth_signTypedData_v4, params: [userAddress, JSON.stringify(data)], }); const v = 0x + signature.slice(130, 132); const r = signature.slice(0, 66); const s = 0x + signature.slice(66, 130); Rationale Unique Random Nonce, Instead of Sequential Nonce One might say transaction ordering is one reason why sequential nonces are preferred. keywords: @param; address; bytes32; nonce; uint256 cache: eips-eip-3009.html plain text: eips-eip-3009.txt item: #427 of 3327 id: eips-eip-3014 author: eips title: eips-eip-3014 date: None words: 381 flesch: 46 summary: EIP-3014: eth_symbol JSON-RPC method Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Interface EIP-3014: eth_symbol JSON-RPC method Authors Peter Grassberger (@PeterTheOne) Created 2020-09-30 Discussion Link https://github.com/ethereum/EIPs/issues/3012 Table of Contents Simple Summary Abstract Motivation Specification Rationale Security Considerations Copyright Simple Summary Add eth_symbol method to the JSON-RPC that returns the symbol of the native coin of the network. For the Ethereum mainnet this will be ETH, other networks will have other symbols. keywords: network cache: eips-eip-3014.html plain text: eips-eip-3014.txt item: #428 of 3327 id: eips-eip-3026 author: eips title: eips-eip-3026 date: None words: 2416 flesch: 50 summary: We use additive notation for point operations, capital letters (P, Q) for points, small letters (a, b) for scalars. Each slice has the following structure: 192 bytes G1 point encoding 192 bytes G2 point encoding Output is 32 bytes representing a boolean: 0x0000000000000000000000000000000000000000000000000000000000000001 if the pairing result is equal the to multiplicative identity in the pairing target field; and 0x0000000000000000000000000000000000000000000000000000000000000000 otherwise. keywords: bytes; encoding; point cache: eips-eip-3026.html plain text: eips-eip-3026.txt item: #429 of 3327 id: eips-eip-3030 author: eips title: eips-eip-3030 date: None words: 2157 flesch: 48 summary: Created 2020-09-30 Discussion Link https://ethereum-magicians.org/t/eip-3030-bls-remote-signer-http-api-standard/4810 Table of Contents Simple Summary Abstract Motivation Specification GET /upcheck GET /keys POST /sign/:identifier Rationale UNIX philosophy: Simple API Test Cases Test Data GET /upcheck GET /keys POST /sign/:identifier Implementation Security Considerations Threat model Copyright Simple Summary This EIP defines a HTTP API standard for a BLS remote signer, consumed by validator clients to sign block proposals and attestations in the context of Ethereum 2.0 (eth2). The BLS remote signer API is designed to be consumed by validator clients, looking for a more secure avenue to store their BLS12-381 private key(s), enabling them to run in more permissive and scalable environments. keywords: content; host; localhost; localhost:9000; signer cache: eips-eip-3030.html plain text: eips-eip-3030.txt item: #430 of 3327 id: eips-eip-3041 author: eips title: eips-eip-3041 date: None words: 443 flesch: 37 summary: Calls related to block prior to EIP-1559 fork block will omit the base fee field in the response. Base fee value is important to make gas price predictions more accurate. keywords: basefee; block cache: eips-eip-3041.html plain text: eips-eip-3041.txt item: #431 of 3327 id: eips-eip-3044 author: eips title: eips-eip-3044 date: None words: 443 flesch: 38 summary: Calls related to block prior to EIP-1559 fork block will omit the base fee field in the response. Base fee value is important to make gas price predictions more accurate. keywords: basefee; block cache: eips-eip-3044.html plain text: eips-eip-3044.txt item: #432 of 3327 id: eips-eip-3045 author: eips title: eips-eip-3045 date: None words: 448 flesch: 31 summary: Calls related to block prior to EIP-1559 fork block will omit the base fee field in the response. Base fee value is important to make gas price predictions more accurate. keywords: basefee; block cache: eips-eip-3045.html plain text: eips-eip-3045.txt item: #433 of 3327 id: eips-eip-3046 author: eips title: eips-eip-3046 date: None words: 448 flesch: 30 summary: Calls related to block prior to EIP-1559 fork block will omit the base fee field in the response. Base fee value is important to make gas price predictions more accurate. keywords: basefee; block cache: eips-eip-3046.html plain text: eips-eip-3046.txt item: #434 of 3327 id: eips-eip-3068 author: eips title: eips-eip-3068 date: None words: 1504 flesch: 52 summary: = (-1 + sqrt(-3))/2 constant2 = -3 constant3 = 1/3 constant4 = g(1) s = (constant4 + t^2)^3 alpha = inverse(t^2*(constant4 + t^2)) x1 = constant1 - constant2*t^4*alpha x2 = -1 - x1 x3 = 1 - constant3*s*alpha a1 = x1^3 + curveB a2 = x2^3 + curveB residue1 = is_square(a1) residue2 = is_square(a2) index = (residue1 - 1)*(residue2 - 3)/4 + 1 coef1 = ConstantTimeEquality(1, index) coef2 = ConstantTimeEquality(2, index) coef3 = ConstantTimeEquality(3, index) = (-1 + sqrt(-3))/2 constant2 = -3 constant3 = 1/3 constant4 = g'(1) s = (constant4 + t^2)^3 alpha = inverse(t^2*(constant4 + t^2)) x1 = constant1 - constant2*t^4*alpha x2 = -1 - x1 x3 = 1 - constant3*s*alpha a1 = x1^3 + curveBPrime a2 = x2^3 + curveBPrime residue1 = is_square(a1) residue2 = is_square(a2) index = (residue1 - 1)*(residue2 - 3)/4 + 1 coef1 = ConstantTimeEquality(1, index) coef2 = ConstantTimeEquality(2, index) coef3 = ConstantTimeEquality(3, index) keywords: algorithm; bn256; curve; function cache: eips-eip-3068.html plain text: eips-eip-3068.txt item: #435 of 3327 id: eips-eip-3074 author: eips title: eips-eip-3074 date: None words: 3946 flesch: 53 summary: An important note is that invoker contracts MUST NOT be upgradeable. The signature is placed in memory so that auth can be upgraded in the future to work with contract accounts (which might use non-ECDSA signatures) and not just EOAs. keywords: authcall; contract; execution; gas; invoker; value cache: eips-eip-3074.html plain text: eips-eip-3074.txt item: #436 of 3327 id: eips-eip-3076 author: eips title: eips-eip-3076 date: None words: 1913 flesch: 37 summary: Advice for Complete Databases For implementers who use a complete record of signed messages to implement their slashing protection database, we make the following recommendations: You MUST ensure that, in addition to importing all of the messages from an interchange, all the conditions are enforced. { title: Signing history, description: This schema provides a record of the blocks and attestations signed by a set of validators, type: object, properties: { metadata: { type: object, properties: { interchange_format_version: { type: string, description: The version of the interchange format that this document adheres to }, genesis_validators_root: { type: string, description: Calculated at Genesis time; serves to uniquely identify the chain } }, required: [ interchange_format_version, genesis_validators_root ] }, data: { type: array, items: [ { type: object, properties: { pubkey: { type: string, description: The BLS public key of the validator (encoded as a 0x-prefixed hex string) }, signed_blocks: { type: array, items: [ { type: object, properties: { slot: { type: string, description: The slot number of the block that was signed }, signing_root: { type: string, description: The output of compute_signing_root(block, domain) } }, required: [ slot ] } ] }, signed_attestations: { type: array, items: [ { type: object, properties: { source_epoch: { type: string, description: The attestation.data.source.epoch of the signed attestation }, target_epoch: { type: string, description: The attestation.data.target.epoch of the signed attestation }, signing_root: { type: string, description: The output of compute_signing_root(attestation, domain) } }, required: [ source_epoch, target_epoch ] } ] } }, required: [ pubkey, signed_blocks, signed_attestations ] } ] } }, required: [ metadata, data ] } Example JSON Instance { metadata: { interchange_format_version: 5, genesis_validators_root: 0x04700007fabc8282644aed6d1c7c9e21d38a03a0c4ba193f3afe428824b3a673 }, data: [ { pubkey: 0xb845089a1457f811bfc000588fbb4e713669be8ce060ea6be3c6ece09afc3794106c91ca73acda5e5457122d58723bed, signed_blocks: [ { slot: 81952, signing_root: 0x4ff6f743a43f3b4f95350831aeaf0a122a1a392922c45d804280284a69eb850b }, { slot: 81951 } ], signed_attestations: [ { source_epoch: 2290, target_epoch: 3007, signing_root: 0x587d6a4f59a58fe24f406e0502413e77fe1babddee641fda30034ed37ecc884d }, { source_epoch: 2290, target_epoch: 3008 } ] } ] } Conditions After importing an interchange file with data field data, a signer must respect the following conditions: Refuse to sign any block that is slashable with respect to the blocks contained in data.signed_blocks. keywords: client; interchange; type; validator cache: eips-eip-3076.html plain text: eips-eip-3076.txt item: #437 of 3327 id: eips-eip-3085 author: eips title: eips-eip-3085 date: None words: 1565 flesch: 56 summary: When calling the method, specifying the chainId will always be necessary, since in the universe of Ethereum chains, the EIP-155 chain ID is effectively the chain GUID. Table of Contents Abstract Specification wallet_addEthereumChain Rationale Security Considerations Chain IDs RPC Endpoints and RPC URLs Validating Chain Data UX Preserving User Privacy Copyright Abstract This EIP adds a wallet-namespaced RPC method: wallet_addEtherereumChain, providing a standard interface for adding chains to Ethereum wallets. keywords: chain; request; wallet cache: eips-eip-3085.html plain text: eips-eip-3085.txt item: #438 of 3327 id: eips-eip-3091 author: eips title: eips-eip-3091 date: None words: 265 flesch: 20 summary: EIP-3091: Block Explorer API Routes Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: Interface EIP-3091: Block Explorer API Routes API Routes for Blockchain explorers Authors Pedro Gomes (@pedrouid), ligi (@ligi) Created 2020-11-02 Discussion Link https://ethereum-magicians.org/t/eip-3091-block-explorer-api-routes/4907 Table of Contents Abstract Motivation Specification Blocks Transactions Accounts Tokens Rationale Backwards Compatibility Security Considerations Copyright Abstract This proposal brings standardization between block explorers API routes when linking transactions, blocks, accounts and tokens. Standardizing the API routes to these links improves interoperability between wallets and block explorers. keywords: block cache: eips-eip-3091.html plain text: eips-eip-3091.txt item: #439 of 3327 id: eips-eip-3102 author: eips title: eips-eip-3102 date: None words: 1876 flesch: 61 summary: Nodes with empty_hash as both children are called leaf nodes, and the remaining nodes are known as internal nodes. The trade-off is that extension nodes must be removed. keywords: length; nodes; storage; trie cache: eips-eip-3102.html plain text: eips-eip-3102.txt item: #440 of 3327 id: eips-eip-3135 author: eips title: eips-eip-3135 date: None words: 1426 flesch: 32 summary: = message){ informUser(message outdate, hash(message)) continue } if(epoch ! However double spending problem may occur when the issuer use multiple verifiers and payer signs many payment messages simultaneously. keywords: epoch; function; token; uint256 cache: eips-eip-3135.html plain text: eips-eip-3135.txt item: #441 of 3327 id: eips-eip-3143 author: eips title: eips-eip-3143 date: None words: 665 flesch: 47 summary: EIP-3143: Increase block rewards to 5 ETH Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-3143: Increase block rewards to 5 ETH Authors Ben Tinner (@Terra854) The increase in block rewards will also allow smaller POW miners ample opporturnity to build up their stores of ETH so that when the time comes to fully transition to ETH 2.0, they may be more willing to become validators as they already have earned the requite amount of ETH needed to do so as opposed to having to spend tens of thousands of dollars to purchase the required ETH directly, increasing the number of validators in the network and therefore strengthening network security. keywords: eth; rewards cache: eips-eip-3143.html plain text: eips-eip-3143.txt item: #442 of 3327 id: eips-eip-3155 author: eips title: eips-eip-3155 date: None words: 1014 flesch: 22 summary: This EIP has multiple objectives: Move the specification to a more visible place to encourage new clients to implement it Strictly define corner cases that were not addressed in the previous version Allow for updates to the specification in case new fields are introduced during execution New clients would need to implement this change if they want to be part of the differential fuzzing group. keywords: ethereum; hex; number cache: eips-eip-3155.html plain text: eips-eip-3155.txt item: #443 of 3327 id: eips-eip-3156 author: eips title: eips-eip-3156 date: None words: 3092 flesch: 54 summary: * @param receiver The contract receiving the tokens, needs to implement the `onFlashLoan(address user, uint256 amount, uint256 fee, bytes calldata)` interface. * @param receiver The contract receiving the tokens, needs to implement the `onFlashLoan(address user, uint256 amount, uint256 fee, bytes calldata)` interface. keywords: @param; fee; loan; token cache: eips-eip-3156.html plain text: eips-eip-3156.txt item: #444 of 3327 id: eips-eip-3198 author: eips title: eips-eip-3198 date: None words: 417 flesch: 53 summary: Test Cases Nominal case Assuming current block base fee is 7 wei. Citation Please cite this document as: Abdelhamid Bakhta (@abdelhamidbakhta), Vitalik Buterin (@vbuterin), EIP-3198: BASEFEE opcode, Ethereum Improvement Proposals, no. 3198, January 2021. keywords: basefee; opcode cache: eips-eip-3198.html plain text: eips-eip-3198.txt item: #445 of 3327 id: eips-eip-3220 author: eips title: eips-eip-3220 date: None words: 1165 flesch: 50 summary: This specification will require blockchains to define a chainid and register the chainid in a public repository. A blockchain identifier (crosschain id) should be unique and satisfy the following requirements: should provide identification, description, and discovery of blockchains. should provide unique identification of each blockchain in the crosschain service ecosystem. keywords: blockchain; crosschain cache: eips-eip-3220.html plain text: eips-eip-3220.txt item: #446 of 3327 id: eips-eip-3224 author: eips title: eips-eip-3224 date: None words: 2037 flesch: 41 summary: Described Data: 0xa9059cbb0000000000000000000000000000000000000000000000002b992b75cbeb60000000000000000000000000008ba1f109551bd432803012645ac136ddd64dba72 i.e. encodeWithSelector(transfer(address,uint256), 0x8ba1f109551bD432803012645Ac136ddd64DBA72, 3.14159e18) Signing: Signed Transaction: We believe that this is a reasonable security model, as transaction descriptions can be audited at the same time as contract code, allowing auditors and code reviewers to check that transaction descriptions are accurate as part of their review. keywords: address; data; description; signing; transaction cache: eips-eip-3224.html plain text: eips-eip-3224.txt item: #447 of 3327 id: eips-eip-3234 author: eips title: eips-eip-3234 date: None words: 1970 flesch: 53 summary: Motivation Flash loans of multiple assets, or batch flash loans, are a common offering of flash lenders, and have a strong use case in the simultaneous refinance of several positions between platforms. This divergence of use cases and user profiles calls for independent, but consistent, standards for single asset flash loans and batch flash loans. keywords: flash; function; loan; receiver; tokens cache: eips-eip-3234.html plain text: eips-eip-3234.txt item: #448 of 3327 id: eips-eip-3238 author: eips title: eips-eip-3238 date: None words: 413 flesch: 44 summary: Citation Please cite this document as: Afri Schoedon (@q9f), EIP-3238: Difficulty Bomb Delay to Q2/2022 [DRAFT], Ethereum Improvement Proposals, no. 3238, January 2021. Available: https://eips.ethereum.org/EIPS/eip-3238. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: difficulty; ethereum cache: eips-eip-3238.html plain text: eips-eip-3238.txt item: #449 of 3327 id: eips-eip-3267 author: eips title: eips-eip-3267 date: None words: 743 flesch: 44 summary: Citation Please cite this document as: Victor Porton (@vporton), Victor Porton , EIP-3267: Giving Ethereum fees to Future Salaries [DRAFT], Ethereum Improvement Proposals, no. 3267, February 2021. Giving Ethereum fees to Future Salaries Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-3267: Giving Ethereum fees to Future Salaries Authors Victor Porton (@vporton), Victor Porton  Created 2021-02-13 Discussion Link https://ethereum-magicians.org/t/discussion-of-eip-3267/5343 Table of Contents Simple Summary Abstract Motivation Specification Rationale Backwards Compatibility Security Considerations Copyright Simple Summary Transfer a part of Ethereum transfer/mining fees to Future Salaries contract Abstract Transfer a part (exact fractions - TBD) of mining/transfer fees + (probably: TBD) keywords: ethereum; tbd cache: eips-eip-3267.html plain text: eips-eip-3267.txt item: #450 of 3327 id: eips-eip-3298 author: eips title: eips-eip-3298 date: None words: 1136 flesch: 68 summary: | 2nd | 3rd | | -11988 | 3012 | | 0x60006000556001600055 keywords: gas; refunds cache: eips-eip-3298.html plain text: eips-eip-3298.txt item: #451 of 3327 id: eips-eip-3300 author: eips title: eips-eip-3300 date: None words: 572 flesch: 48 summary: Backwards Compatibility This proposal breaks gas refunds, which contribute to block elasticity. EIP-3300: Phase out refunds Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-3300: Phase out refunds Authors William Morriss (@wjmelements) Created 2020-02-26 Discussion Link https://ethereum-magicians.org/t/eip-3300-phase-out-refunds/5434 Table of Contents Simple Summary Abstract Motivation Specification EIP-2929 Rationale Backwards Compatibility Copyright Simple Summary Phases out the SSTORE and SELFDESTRUCT gas refunds. keywords: gas; refunds cache: eips-eip-3300.html plain text: eips-eip-3300.txt item: #452 of 3327 id: eips-eip-3322 author: eips title: eips-eip-3322 date: None words: 498 flesch: 63 summary: Motivation The refund mechanism is currently being used by gas tokens to arbitrage gas price. Citation Please cite this document as: William Morriss (@wjmelements), EIP-3322: Account gas storage opcodes [DRAFT], Ethereum Improvement Proposals, no. 3322, March 2020. keywords: gas cache: eips-eip-3322.html plain text: eips-eip-3322.txt item: #453 of 3327 id: eips-eip-3326 author: eips title: eips-eip-3326 date: None words: 771 flesch: 52 summary: EIP-3326: Wallet Switch Ethereum Chain RPC Method (`wallet_switchEthereumChain`) Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Interface EIP-3326: Wallet Switch Ethereum Chain RPC Method (`wallet_switchEthereumChain`) Authors Erik Marks (@rekmarks) Created 2021-03-04 Discussion Link https://ethereum-magicians.org/t/eip-3326-wallet-switchethereumchain Requires EIP-155, EIP-695 Table of Contents Simple Summary Abstract Motivation Specification wallet_switchEthereumChain Examples Rationale Security Considerations Preserving User Privacy Copyright Simple Summary An RPC method for switching the wallet’s active Ethereum chain. Preserving User Privacy Automatically rejecting requests for chains that aren’t supported or have yet to be added by the wallet allows requesters to infer which chains are supported by the wallet. keywords: chain; wallet cache: eips-eip-3326.html plain text: eips-eip-3326.txt item: #454 of 3327 id: eips-eip-3332 author: eips title: eips-eip-3332 date: None words: 897 flesch: 51 summary: Adding a mechanism enforcing an upper bound on gas prices for a transaction could be an effective defense against such front-running attacks. Given a median gas price opcode a contract can set a maximum gas price as a function of the last blocks gas price. keywords: block; gas; price cache: eips-eip-3332.html plain text: eips-eip-3332.txt item: #455 of 3327 id: eips-eip-3336 author: eips title: eips-eip-3336 date: None words: 1079 flesch: 57 summary: This prevents existing programs that make assumptions about memory allocation gas costs from resulting in errors, without unduly discounting memory below what it costs today. Changes to memory expansion gas cost Presently, the total cost to extend the memory to a words long is Cmem(a) keywords: cost; gas; memory cache: eips-eip-3336.html plain text: eips-eip-3336.txt item: #456 of 3327 id: eips-eip-3337 author: eips title: eips-eip-3337 date: None words: 1078 flesch: 53 summary: This EIP proposes new opcodes that permit this form of memory use, without imposing undue burden on EVM implementers or on runtime efficiency. Rationale Cost of new opcodes The cost of the new opcodes MLOADFP and MSTOREFP reflects the cost of MLOAD and MSTORE. keywords: memory; opcode cache: eips-eip-3337.html plain text: eips-eip-3337.txt item: #457 of 3327 id: eips-eip-3338 author: eips title: eips-eip-3338 date: None words: 441 flesch: 50 summary: EIP-3338: Limit account nonce to 2^52 Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🛑 Withdrawn Standards Track: Core EIP-3338: Limit account nonce to 2^52 Authors Micah Zoltu (@MicahZoltu), Alex Beregszaszi (@axic) Created 2021-03-07 Discussion Link https://ethereum-magicians.org/t/eip-2681-limit-account-nonce-to-2-64-1/4324 Table of Contents Abstract Motivation Specification Rationale Backwards Compatibility Security Considerations Copyright Abstract Limit account nonce to be between 0 and 2^52. Motivation Account nonces are currently specified to be arbitrarily long unsigned integers. Citation Please cite this document as: Micah Zoltu (@MicahZoltu), Alex Beregszaszi (@axic), EIP-3338: Limit account nonce to 2^52 [DRAFT], Ethereum Improvement Proposals, no. 3338, March 2021. keywords: account; nonce cache: eips-eip-3338.html plain text: eips-eip-3338.txt item: #458 of 3327 id: eips-eip-3368 author: eips title: eips-eip-3368 date: None words: 689 flesch: 37 summary: EIP-3368: Increase block rewards to 3 ETH, with 2 Year Decay to 1 ETH Scheduled Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-3368: Increase block rewards to 3 ETH, with 2 Year Decay to 1 ETH Scheduled Authors Michael D. Carter (@BitsBeTrippin) Created 2021-03-12 Discussion Link https://ethereum-magicians.org/t/eip-3368-block-reward-increase-w-decay-for-next-two-years/5550 Table of Contents Simple Summary Abstract Motivation Specification Constants Block Reward Rationale Backwards Compatibility Security Considerations Copyright Simple Summary Changes the block reward paid to proof-of-work (POW) miners to 3 ETH from existing 2 ETH and starts a decay schedule for next two years to 1 ETH Block Reward. Citation Please cite this document as: Michael D. Carter (@BitsBeTrippin), EIP-3368: Increase block rewards to 3 ETH, with 2 Year Decay to 1 ETH Scheduled [DRAFT], Ethereum Improvement Proposals, no. 3368, March 2021. keywords: block; eth cache: eips-eip-3368.html plain text: eips-eip-3368.txt item: #459 of 3327 id: eips-eip-3372 author: eips title: eips-eip-3372 date: None words: 1662 flesch: 54 summary: Citation Please cite this document as: mineruniter969 (@mineruniter969), mineruniter969 , EIP-3372: 5 FNV primes for ethash [DRAFT], Ethereum Improvement Proposals, no. 3372, March 2021. Abstract This EIP is to kick current ASIC implementations out of the network to keep the Ethereum network secure and healthy by changing the fnv constants. keywords: asics; ethereum; fnv; network cache: eips-eip-3372.html plain text: eips-eip-3372.txt item: #460 of 3327 id: eips-eip-3374 author: eips title: eips-eip-3374 date: None words: 453 flesch: 22 summary: 2) Sets an initial block reward of 3; 3) Introduces an ongoing, predictable reduction in future mining rewards down to 1, effectively “sunsetting” POW and codifying the move to POS; 4) Reduces economic incentives for continued development of ASICs; 5) Allows the impacts of decreasing miner rewards to be measured and monitored rather than relying on conjecture and game theory, so adjustments can be made if necessary. Specification Constants TRANSITION_START_BLOCK_NUMBER: TBD TRANSITION_DURATION: 2_362_000 // (about one year) TRANSITION_END_BLOCK_NUMBER: FORK_BLOCK_NUMBER + TRANSITION_DURATION STARTING_REWARD: 3_000_000_000_000_000_000 ENDING_REWARD: 1_000_000_000_000_000_000 REWARD_DELTA: STARTING_REWARD - ENDING_REWARD Block Reward if block.number >= TRANSITION_END_BLOCK_NUMBER: block_reward = ENDING_REWARD elif block.number == TRANSITION_START_BLOCK_NUMBER: block_reward = STARTING_REWARD elif block.number > TRANSITION_START_BLOCK_NUMBER: block_reward = STARTING_REWARD - REWARD_DELTA * TRANSITION_DURATION / (block.number - TRANSITION_START_BLOCK_NUMBER) Rationale Picking starting and ending block reward values that are equidistant from the current block reward rate of 2 ensures the impact of this EIP will be issuance neutral over the one year time frame. keywords: block; ethereum cache: eips-eip-3374.html plain text: eips-eip-3374.txt item: #461 of 3327 id: eips-eip-3382 author: eips title: eips-eip-3382 date: None words: 461 flesch: 50 summary: Motivation Both Ethereum’s Proof of Work and Proof of Stake designs assume that block producers are financially rational, but does not assume block producers to be benevolent. There is one exception however, and it is when block producers choose the gas limit of a block where it is assumed that block producers care about the long term health and decentralisation of the chain. keywords: block; gas cache: eips-eip-3382.html plain text: eips-eip-3382.txt item: #462 of 3327 id: eips-eip-3386 author: eips title: eips-eip-3386 date: None words: 2479 flesch: 68 summary: The derivative tokens can be burned to redeem base tokens out of the pool. By specifying a subset of base tokens which may be pooled, the difference between the lowest and highest value token in the pool may be minimized. keywords: address; base; derivative; tokens cache: eips-eip-3386.html plain text: eips-eip-3386.txt item: #463 of 3327 id: eips-eip-3403 author: eips title: eips-eip-3403 date: None words: 1312 flesch: 49 summary: GasToken has benefits in moving gas space from low-fee periods to high-fee periods, but it also has downsides to the network, particularly in exacerbating state size (as state slots are effectively used as a “battery” to save up gas) and inefficiently clogging blockchain gas usage Refunds increase block size variance. EIP-3403: Partial removal of refunds Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-3403: Partial removal of refunds Authors Vitalik Buterin (@vbuterin), Martin Swende (@holiman) Created 2021-03-16 Discussion Link https://ethereum-magicians.org/t/eip-3298-removal-of-refunds/5430 Table of Contents Simple Summary Motivation The mutex usecase Specification Parameters Rationale Backwards Compatibility Test Cases 2929 Gas Costs With EIP-3403 partial refunds Security Considerations Copyright Simple Summary Remove gas refunds for SELFDESTRUCT, and restrict gas refunds for SSTORE to one specific case. keywords: gas; refunds; storage cache: eips-eip-3403.html plain text: eips-eip-3403.txt item: #464 of 3327 id: eips-eip-3416 author: eips title: eips-eip-3416 date: None words: 2021 flesch: 54 summary: It is expected that most users will not have to manually adjust gas fees, even in periods of high network activity. Ethereum currently prices transaction fees using a simple auction mechanism, where users send transactions with bids (“gasprices”) and miners choose transactions with the highest bids, and transactions that get included pay the bid that they specify. keywords: block; fee; gas; transaction cache: eips-eip-3416.html plain text: eips-eip-3416.txt item: #465 of 3327 id: eips-eip-3436 author: eips title: eips-eip-3436 date: None words: 1132 flesch: 59 summary: At least one client has been observed producing multiple blocks at the same height with the same difficulty, so a final catch-all standard of lowest block hash should break any remaining ties. Two forks form, one with an in-order block from validator 1 and then an out of order block from validator 3. keywords: block; chain cache: eips-eip-3436.html plain text: eips-eip-3436.txt item: #466 of 3327 id: eips-eip-3440 author: eips title: eips-eip-3440 date: None words: 1930 flesch: 45 summary: * @param `address _artist` the wallet of the signing artist (TODO consider multiple * signers and contract signers (non-EOA) */ function _designateArtist(address _artist) internal virtual { require(artist == address(0), ERC721Extensions: the artist has already been set); // artist = _artist; } / keywords: artist; memory; original; signature cache: eips-eip-3440.html plain text: eips-eip-3440.txt item: #467 of 3327 id: eips-eip-3448 author: eips title: eips-eip-3448 date: None words: 1088 flesch: 39 summary: ERC-3448: MetaProxy Standard Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: ERC ERC-3448: MetaProxy Standard A minimal bytecode implementation for creating proxy contracts with immutable metadata attached to the bytecode Authors pinkiebell (@pinkiebell) Created 2021-03-29 Table of Contents Abstract Motivation Specification Rationale Backwards Compatibility Test Cases Reference Implementation Deployment bytecode MetaProxy Examples Security Considerations Copyright Abstract By standardizing on a known minimal bytecode proxy implementation with support for immutable metadata, this standard allows users and third party tools (e.g. Etherscan) to: (a) simply discover that a contract will always redirect in a known manner and (b) depend on the behavior of the code at the destination contract as the behavior of the redirecting contract and (c) verify/view the attached metadata. Available: https://eips.ethereum.org/EIPS/eip-3448. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: metadata; metaproxy; returndatasize cache: eips-eip-3448.html plain text: eips-eip-3448.txt item: #468 of 3327 id: eips-eip-3450 author: eips title: eips-eip-3450 date: None words: 2003 flesch: 54 summary: Abstract A standardized approach to splitting a BIP-39 mnemonic into N BIP-39 mnemonics, called shares, so that T shares are required to recover the original mnemonic and no information about the original mnemonic, other than its size, is leaked with less than T shares. Created 2021-03-29 Discussion Link https://ethereum-magicians.org/t/erc-3450-standard-for-applying-shamirs-to-bip-39-mnemonics/5844 Table of Contents Simple Summary Abstract Motivation Specification Shamir’s Secret Sharing Scheme BIP-39 Mnemonics Applying Shamir’s Scheme to BIP-39 Mnemonics Share Format Creating Shares Recovering the Mnemonic Rationale Choice of Field Valid Share Mnemonics and Share IDs Validation on Recovery Test Cases Security Considerations Copyright Simple Summary A standardized algorithm for applying Shamir’s Secret Sharing Scheme to BIP-39 mnemonics. keywords: bip-39; entropy; mnemonic cache: eips-eip-3450.html plain text: eips-eip-3450.txt item: #469 of 3327 id: eips-eip-3455 author: eips title: eips-eip-3455 date: None words: 572 flesch: 61 summary: Citation Please cite this document as: William Morriss (@wjmelements), Baptiste Vauthey (@thabaptiser), EIP-3455: SUDO Opcode [DRAFT], Ethereum Improvement Proposals, no. 3455, April 2021. EIP-3455: SUDO Opcode Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-3455: SUDO Opcode A new opcode is introduced to allow calling from an arbitrary sender address. keywords: address; sudo cache: eips-eip-3455.html plain text: eips-eip-3455.txt item: #470 of 3327 id: eips-eip-3475 author: eips title: eips-eip-3475 date: None words: 3601 flesch: 64 summary: * @param `_transactions` is the `Transaction[] calldata` (ie array of issued bond class, bond nonce and amount of bonds to be issued). ** * classValues * @dev allows anyone to read the values (stored in struct Values for different class) for given bond class `classId`. keywords: @dev; @param; address; bond; class; classid; metadata cache: eips-eip-3475.html plain text: eips-eip-3475.txt item: #471 of 3327 id: eips-eip-3508 author: eips title: eips-eip-3508 date: None words: 1283 flesch: 38 summary: Multi-Contract System Gas Reduction Given that most complex smart contract systems deployed on Ethereum today rely on cross-contract interactions whereby values are passed from one contract to another via function calls, the ORIGIN-prefixed instruction set would enable a way for smart contract systems to acquire access to the original transaction data at any given step in the call chain execution which could result in cross-contract calls ultimately consuming less gas if the data passed between them is reduced as a side-effect of this change. Created 2021-04-16 Discussion Link https://ethereum-magicians.org/t/eip-draft-transaction-data-opcodes/6017 Table of Contents Simple Summary Abstract Motivation Specification ORIGINDATALOAD (0x47), ORIGINDATASIZE (0x48) and ORIGINDATACOPY (0x49) Rationale AUTHCALL (0xf7) Interaction Naming Conventions Instruction Address Space Gas Costs Instruction Space Pollution Backwards Compatibility Test Cases Security Considerations Introspective Contracts Denial-of-Service Attack Multi-Contract System Gas Reduction Copyright Simple Summary Provide access to original transaction data. keywords: contract; data; transaction cache: eips-eip-3508.html plain text: eips-eip-3508.txt item: #472 of 3327 id: eips-eip-3520 author: eips title: eips-eip-3520 date: None words: 899 flesch: 38 summary: Motivation It is undeniable that smart contracts are becoming more interconnected than ever. Up until this point, smart contracts have entirely relied on compliant interfaces and introspection to introduce a new step in the call chain of a complex multi-contract interaction. keywords: address; entrypoint; transaction cache: eips-eip-3520.html plain text: eips-eip-3520.txt item: #473 of 3327 id: eips-eip-3521 author: eips title: eips-eip-3521 date: None words: 440 flesch: 55 summary: Citation Please cite this document as: Matt Garnett (@lightclient), EIP-3521: Reduce access list cost [DRAFT], Ethereum Improvement Proposals, no. 3521, April 2021. EIP-3521: Reduce access list cost Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-3521: Reduce access list cost Authors Matt Garnett (@lightclient) keywords: cost cache: eips-eip-3521.html plain text: eips-eip-3521.txt item: #474 of 3327 id: eips-eip-3525 author: eips title: eips-eip-3525 date: None words: 4363 flesch: 53 summary: This EIP introduces new token transfer models for semi-fungibility, including value transfer between two tokens of the same slot and value transfer from a token to an address. */ function onERC3525Received(address _operator, uint256 _fromTokenId, uint256 _toTokenId, uint256 _value, bytes calldata _data) external returns (bytes4); } Token Manipulation Scenarios Transfer: Besides ERC-721 compatible token transfer methods, this EIP introduces two new transfer models: value transfer from ID to ID, and value transfer from ID to address. keywords: @param; operator; slot; token; transfer; value cache: eips-eip-3525.html plain text: eips-eip-3525.txt item: #475 of 3327 id: eips-eip-3529 author: eips title: eips-eip-3529 date: None words: 1925 flesch: 52 summary: Rationale In EIP-2200, three cases for refunds were introduced: If the original value is nonzero, and the new value is zero, add SSTORE_CLEARS_SCHEDULE (currently 15,000) gas to the refund counter If the original value is zero, the current value is nonzero, and the new value is zero, add SSTORE_SET_GAS - SLOAD_GAS (currently 19,900) gas to the refund counter If the original value is nonzero, the current value is a different nonzero value, and the new value equals the original value, add SSTORE_RESET_GAS - SLOAD_GAS (currently 4,900) gas to the refund counter Of these three, only (1) enables gastokens and allows a block to expend more gas on execution than the block gas limit. EIP-3529: Reduction in refunds Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: Core EIP-3529: Reduction in refunds Authors Vitalik Buterin (@vbuterin), Martin Swende (@holiman) Created 2021-04-22 Requires EIP-2200, EIP-2929, EIP-2930 Table of Contents Simple Summary Motivation Specification Parameters Rationale Backwards Compatibility Effect on storage clearing incentives Test Cases EIP-2929 Gas Costs With reduced refunds Security Considerations Copyright Simple Summary Remove gas refunds for SELFDESTRUCT, and reduce gas refunds for SSTORE to a lower level where the refunds are still substantial, but they are no longer high enough for current “exploits” of the refund mechanism to be viable. keywords: gas; refund; storage; value cache: eips-eip-3529.html plain text: eips-eip-3529.txt item: #476 of 3327 id: eips-eip-3534 author: eips title: eips-eip-3534 date: None words: 2978 flesch: 45 summary: Motivation Establish a protocol-based mechanism with which transactions are able to articulate constraints on eligible chain contexts. Restrict transaction applicability to a chain context that is currently available and reasoned about under some subjective view. Introduces a way for transactions to describe a dependency on their current view of a chain. keywords: ancestorid; annotation_prefix; block; chain; transaction; value cache: eips-eip-3534.html plain text: eips-eip-3534.txt item: #477 of 3327 id: eips-eip-3540 author: eips title: eips-eip-3540 date: None words: 3202 flesch: 52 summary: Legacy init code Returns legacy code Returns valid EOF1 code Returns invalid EOF1 code, contract creation fails Returns 0xEF not followed by EOF1 code, contract creation fails Valid EOF1 init code Returns legacy code, contract creation fails Returns valid EOF1 code Returns invalid EOF1 code, contract creation fails Returns 0xEF not followed by EOF1 code, contract creation fails Invalid EOF1 init code Contract execution EOF code containing PC opcode - offset inside code section is returned EOF code containing CODECOPY/CODESIZE - works as in legacy code CODESIZE returns the size of entire container CODECOPY can copy from code section CODECOPY can copy from data section CODECOPY can copy from the EOF header CODECOPY can copy entire container EXTCODECOPY/EXTCODESIZE/EXTCODEHASH with the EOF target contract - works as with legacy target contract EXTCODESIZE returns the size of entire target container EXTCODEHASH returns the hash of entire target container EXTCODECOPY can copy from target’s code section EXTCODECOPY can copy from target’s data section EXTCODECOPY can copy from target’s EOF header EXTCODECOPY can copy entire target container Results don’t differ when executed inside legacy or EOF contract EOF1 DELEGATECALL DELEGATECALL to EOF1 code succeeds DELEGATECALL to EOF0 code fails DELEGATECALL to empty container fails Security Considerations With the anticipated EOF extensions, the validation is expected to have linear computational and space complexity. (Remark: Contract creation code SHOULD set the section size of the data section so that the constructor arguments fit it.) keywords: code; container; contract; creation; eof; eof1; section; version cache: eips-eip-3540.html plain text: eips-eip-3540.txt item: #478 of 3327 id: eips-eip-3541 author: eips title: eips-eip-3541 date: None words: 777 flesch: 50 summary: EIP-3541: Reject new contract code starting with the 0xEF byte Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: Core EIP-3541: Reject new contract code starting with the 0xEF byte Authors Alex Beregszaszi (@axic), Paweł Bylica (@chfast), Andrei Maiboroda (@gumb0), Alexey Akhunov (@AlexeyAkhunov), Christian Reitwiessner (@chriseth), Martin Swende (@holiman) Created 2021-03-16 Table of Contents Abstract Motivation Specification Remarks Rationale Test Cases Backwards Compatibility Security Considerations Copyright Abstract Disallow new code starting with the 0xEF byte to be deployed. Citation Please cite this document as: Alex Beregszaszi (@axic), Paweł Bylica (@chfast), Andrei Maiboroda (@gumb0), Alexey Akhunov (@AlexeyAkhunov), Christian Reitwiessner (@chriseth), Martin Swende (@holiman), EIP-3541: Reject new contract code starting with the 0xEF byte, Ethereum Improvement Proposals, no. 3541, March 2021. keywords: byte; code cache: eips-eip-3541.html plain text: eips-eip-3541.txt item: #479 of 3327 id: eips-eip-3554 author: eips title: eips-eip-3554 date: None words: 412 flesch: 39 summary: Also, gradual changes in blocktimes due to longer-term adjustments in difficulty can affect the timing of difficulty bomb epochs. Citation Please cite this document as: James Hancock (@madeoftin), EIP-3554: Difficulty Bomb Delay to December 2021, Ethereum Improvement Proposals, no. 3554, May 2021. keywords: difficulty cache: eips-eip-3554.html plain text: eips-eip-3554.txt item: #480 of 3327 id: eips-eip-3561 author: eips title: eips-eip-3561 date: None words: 1211 flesch: 18 summary: Admin interactions with next logic contract address correspond with these methods and events: // Sets next logic contract address. keywords: assembly; function; logic cache: eips-eip-3561.html plain text: eips-eip-3561.txt item: #481 of 3327 id: eips-eip-3569 author: eips title: eips-eip-3569 date: None words: 1335 flesch: 62 summary: Rationale to include many NFT metadata objects, or URIs in one JSON file By including metadata for many NFTs in one JSON file we can eliminate the need for many transactions to set the metadata for multiple NFTs. This is an extension which could be added to existing NFT standards. keywords: metadata; nft; token cache: eips-eip-3569.html plain text: eips-eip-3569.txt item: #482 of 3327 id: eips-eip-3584 author: eips title: eips-eip-3584 date: None words: 1033 flesch: 38 summary: And the idea of having the AccessListRoot as URN like structure is to enable upgradation to these paths without affecting block structure. It will be a bit more expensive but will enable partial downloading, inspection and validation of the access_list. a normal kate commitment can also be generated to enable this partial capability and is recommended as validating partial fetch of access list chunks would be very simple. keywords: access_list; accesslistroot; block cache: eips-eip-3584.html plain text: eips-eip-3584.txt item: #483 of 3327 id: eips-eip-3589 author: eips title: eips-eip-3589 date: None words: 1426 flesch: 44 summary: require(_addresses.length == _numbers.length -4 - _numbers[3], numbers length not match); uint256 pointerA; //points to first erc20 address, if there is any uint256 pointerB =4; //points to first erc20 amount, if there is any for(uint256 i = 0; i< _numbers[1]; i++){ require(_numbers[pointerB] > 0, transfer erc20 0 amount); IERC20(_addresses[pointerA++]).safeTransferFrom(_msgSender(), address(this), _numbers[pointerB++]); } for(uint256 j = 0; j< _numbers[2]; j++){ IERC721(_addresses[pointerA++]).safeTransferFrom(_msgSender(), address(this), _numbers[pointerB++]); } for(uint256 k =0; k< _numbers[3]; k++){ IERC1155(_addresses[pointerA++]).safeTransferFrom(_msgSender(), address(this), _numbers[pointerB], _numbers[_numbers[3] + pointerB++], ); } tokenId = hash(nonce, _addresses, _numbers); super._mint(_to, tokenId); emit AssemblyAsset(_to, tokenId, nonce, _addresses, _numbers); nonce ++; } function safeMint(address _to, address require(_addresses.length == _numbers.length -4 - _numbers[3], numbers length not match); uint256 pointerA; //points to first erc20 address, if there is any uint256 pointerB =4; //points to first erc20 amount, if there is any for(uint256 i = 0; i< _numbers[1]; i++){ require(_numbers[pointerB] > 0, transfer erc20 0 amount); IERC20 token = IERC20(_addresses[pointerA++]); uint256 orgBalance = token.balanceOf(address(this)); token.safeTransferFrom(_msgSender(), address(this), _numbers[pointerB]); _numbers[pointerB++] = token.balanceOf(address(this)) - orgBalance; } for(uint256 j = 0; j< _numbers[2]; j++){ IERC721(_addresses[pointerA++]).safeTransferFrom(_msgSender(), address(this), _numbers[pointerB++]); } for(uint256 k =0; k< _numbers[3]; k++){ IERC1155(_addresses[pointerA++]).safeTransferFrom(_msgSender(), address(this), _numbers[pointerB], _numbers[_numbers[3] + pointerB++], ); } tokenId = hash(nonce, _addresses, _numbers); super._mint(_to, tokenId); emit AssemblyAsset(_to, tokenId, nonce, _addresses, _numbers); nonce ++; } function burn(address _to, uint256 _tokenId, uint256 _salt, address keywords: addresses; token; uint256 cache: eips-eip-3589.html plain text: eips-eip-3589.txt item: #484 of 3327 id: eips-eip-3607 author: eips title: eips-eip-3607 date: None words: 1131 flesch: 55 summary: Further possible attack vectors via address collisions between contracts and EOAs are: Most attacks that can occur via address collisions are quite impractical: They involve users sending funds to an address before a contract is deployed. keywords: address; contract; ethereum cache: eips-eip-3607.html plain text: eips-eip-3607.txt item: #485 of 3327 id: eips-eip-3643 author: eips title: eips-eip-3643 date: None words: 3881 flesch: 30 summary: interface IERC3643 is IERC20 { // events event UpdatedTokenInformation(string _newName, string _newSymbol, uint8 _newDecimals, string _newVersion, address _newOnchainID); event IdentityRegistryAdded(address indexed _identityRegistry); event ComplianceAdded(address indexed _compliance); event RecoverySuccess(address _lostWallet, address _newWallet, address _investorOnchainID); event AddressFrozen(address indexed _userAddress, bool indexed _isFrozen, address indexed _owner); event TokensFrozen(address indexed _userAddress, uint256 _amount); event TokensUnfrozen(address indexed _userAddress, uint256 _amount); event Paused(address _userAddress); event Unpaused(address _userAddress); // functions // getters function onchainID() external view returns (address); function version() external view returns (string memory); function identityRegistry() external view returns (IIdentityRegistry); function compliance() external view returns (ICompliance); function paused() external view returns (bool); function isFrozen(address _userAddress) external view returns (bool); function getFrozenTokens(address _userAddress) external view returns (uint256); // setters function setName(string calldata _name) external; function setSymbol(string calldata _symbol) external; function setOnchainID(address _onchainID) external; function pause() external; function unpause() external; function setAddressFrozen(address _userAddress, bool _freeze) external; function freezePartialTokens(address _userAddress, uint256 _amount) external; function unfreezePartialTokens(address _userAddress, uint256 _amount) external; function setIdentityRegistry(address _identityRegistry) external; function setCompliance(address _compliance) external; // transfer actions function forcedTransfer(address _from, address _to, uint256 _amount) external returns (bool); function mint(address _to, uint256 _amount) external; function burn(address _userAddress, uint256 _amount) external; function recoveryAddress(address _lostWallet, address _newWallet, address _investorOnchainID) external returns (bool); // batch functions function batchTransfer(address[] calldata _toList, uint256[] calldata _amounts) external; function batchForcedTransfer(address[] calldata _fromList, address canTransfer The canTransfer function is also called from within transfer functions. keywords: contract; external; function; identity; indexed; registry; returns; token cache: eips-eip-3643.html plain text: eips-eip-3643.txt item: #486 of 3327 id: eips-eip-3651 author: eips title: eips-eip-3651 date: None words: 303 flesch: 37 summary: Citation Please cite this document as: William Morriss (@wjmelements), EIP-3651: Warm COINBASE, Ethereum Improvement Proposals, no. 3651, July 2021. EIP-3651: Warm COINBASE Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: Core EIP-3651: Warm COINBASE Starts the `COINBASE` address warm Authors William Morriss (@wjmelements) keywords: coinbase cache: eips-eip-3651.html plain text: eips-eip-3651.txt item: #487 of 3327 id: eips-eip-3668 author: eips title: eips-eip-3668 date: None words: 4495 flesch: 46 summary: The contract could also revert with a new error to initiate another lookup, in which case the protocol starts again at step 1. ┌──────┐ ┌────────┐ ┌─────────────┐ │Client│ │Contract│ │Gateway @ url│ └──┬───┘ └───┬────┘ └──────┬──────┘ │ │ │ │ somefunc(...) │ │ ├─────────────────────────────────────────────────►│ │ │ │ │ │ revert OffchainData(sender, urls, callData, │ │ │ callbackFunction, extraData) │ │ │◄─────────────────────────────────────────────────┤ │ │ │ │ │ HTTP request (sender, callData) │ │ ├──────────────────────────────────────────────────┼────────────►│ │ │ │ │ Response (result) │ │ │◄─────────────────────────────────────────────────┼─────────────┤ │ │ │ │ callbackFunction(result, extraData) │ │ ├─────────────────────────────────────────────────►│ │ │ │ │ │ answer │ │ │◄─────────────────────────────────────────────────┤ │ │ │ │ Contract interface A CCIP read enabled contract MUST revert with the following error whenever a function that requires offchain data is called: error OffchainLookup(address sender, string[] urls, bytes callData, bytes4 callbackFunction, bytes extraData) sender is the address of the contract that raised the error, and is used to determine if the error was thrown by the contract the client called, or ‘bubbled up’ from a nested call. Client Lookup Protocol A client that supports CCIP read MUST make contract calls using the following process: keywords: contract; data; ─ ─; ─ ┐; ─ ┘; ├ ─ cache: eips-eip-3668.html plain text: eips-eip-3668.txt item: #488 of 3327 id: eips-eip-3670 author: eips title: eips-eip-3670 date: None words: 830 flesch: 43 summary: Invalid initcode Valid initcode returning invalid code Valid initcode returning valid code Valid codes EOF code containing INVALID EOF code with data section containing bytes that are undefined instructions Legacy code containing undefined instruction Legacy code ending with incomplete PUSH instruction Invalid codes EOF code containing undefined instruction EOF code ending with incomplete PUSH instruction This can include PUSH instruction unreachable by execution, e.g. after STOP Reference Implementation # Motivation Currently existing contracts require no validation of correctness and EVM implementations can decide how they handle truncated bytecode or undefined instructions. keywords: code; eof cache: eips-eip-3670.html plain text: eips-eip-3670.txt item: #489 of 3327 id: eips-eip-3675 author: eips title: eips-eip-3675 date: None words: 3382 flesch: 49 summary: EIP-3675: Upgrade consensus to Proof-of-Stake Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: Core EIP-3675: Upgrade consensus to Proof-of-Stake Specification of the consensus mechanism upgrade on Ethereum Mainnet that introduces Proof-of-Stake Authors Mikhail Kalinin (@mkalinin), Danny Ryan (@djrtwo), Vitalik Buterin (@vbuterin) Created 2021-07-22 Requires EIP-2124 Table of Contents Abstract Motivation Specification Definitions Client software configuration PoW block processing Constants Block structure Block validity Block and ommer rewards Fork choice rule Network Rationale Total difficulty triggering the upgrade Parameterizing terminal block hash Halting the import of PoW blocks Replacing block fields with constants Replacing difficulty with 0 Changing block validity rules Removing block rewards Supplanting fork choice rule Remove of POS_CONSENSUS_VALIDATED EIP-2124 fork identifier Removing block gossip Restricting the length of extraData Backwards Compatibility EVM Test Cases Security Considerations Beacon chain Transition process Ancient blocks are no longer a requisite for a network security Copyright Abstract This EIP deprecates Proof-of-Work (PoW) and supersedes it with the new Proof-of-Stake consensus mechanism (PoS) driven by the beacon chain. Halting the import of PoW blocks See Security considerations. keywords: block; chain; consensus; pos; pow; pow block; terminal cache: eips-eip-3675.html plain text: eips-eip-3675.txt item: #490 of 3327 id: eips-eip-3690 author: eips title: eips-eip-3690 date: None words: 2089 flesch: 54 summary: The LEB128 encoding of a jumploc must be valid: the encoding must be complete and not read out of jumpdests section. In case code does not use jumps, an empty JUMPDEST table is represented by omitting jumpdests section as opposed to a section that is always present, but allowed to be empty. keywords: code; jumpdest; section; table cache: eips-eip-3690.html plain text: eips-eip-3690.txt item: #491 of 3327 id: eips-eip-3709 author: eips title: eips-eip-3709 date: None words: 402 flesch: 32 summary: Specification For wallets and providers, if a user submits a transaction for signing with where TransactionType == 0x1, the developer should upgrade the transaction to meet the criteria of transaction of type 2. Created 2021-08-07 Discussion Link https://ethereum-magicians.org/t/eip-3709-deprecate-type-1-transactions/6810 Requires EIP-1559 Table of Contents Simple Summary Abstract Motivation Specification Rationale Security Considerations Copyright Simple Summary Deprecates usage of EIP-2718 TransactionType 1 in wallets and providers, upgrading all type 1 transactions to a type 2 transaction. keywords: ethereum; transactiontype cache: eips-eip-3709.html plain text: eips-eip-3709.txt item: #492 of 3327 id: eips-eip-3722 author: eips title: eips-eip-3722 date: None words: 788 flesch: 44 summary: The EIP also includes a proposed standard json format for a Twitter-like application, where each post() call can include multiple posts and/or operations. Any Ethereum account can make posts to the deployment of Poster on its local network. keywords: post; type cache: eips-eip-3722.html plain text: eips-eip-3722.txt item: #493 of 3327 id: eips-eip-3754 author: eips title: eips-eip-3754 date: None words: 543 flesch: 32 summary: Such right can take the form of NFT options, oracle membership, virtual coupons, etc., and can then be made liquid because of this tokenization. Transfer of such rights is also made easier because of this tokenization. keywords: function; standard cache: eips-eip-3754.html plain text: eips-eip-3754.txt item: #494 of 3327 id: eips-eip-3756 author: eips title: eips-eip-3756 date: None words: 305 flesch: 47 summary: Citation Please cite this document as: lightclient (@lightclient), EIP-3756: Gas Limit Cap [DRAFT], Ethereum Improvement Proposals, no. 3756, August 2021. https://eips.ethereum.org/EIPS/eip-3756. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: gas cache: eips-eip-3756.html plain text: eips-eip-3756.txt item: #495 of 3327 id: eips-eip-3770 author: eips title: eips-eip-3770 date: None words: 441 flesch: 35 summary: Chain-specific address = “shortName” “:” “address” shortName = STRING address = STRING Semantics `shortName` is mandatory and MUST be a valid chain short name from https://github.com/ethereum-lists/chains `address` is mandatory and MUST be a [ERC-55](/EIPS/eip-55) compatible hexadecimal address Examples Rationale To solve the initial problem of user-facing addresses being ambiguous in a multichain context, we need to map EIP-155 chain IDs with a user-facing format of displaying chain identifiers. In this context, addresses become ambiguous, as the same address may refer to an EOA on chain X or a smart contract on chain Y. keywords: chain; ethereum cache: eips-eip-3770.html plain text: eips-eip-3770.txt item: #496 of 3327 id: eips-eip-3772 author: eips title: eips-eip-3772 date: None words: 2432 flesch: 63 summary: The smaller data structure (represented as cintx) is divided into two parts, in the first one we store significant bits and in the other number of left shifts needed on the significant bits to decompress. Usual user amounts mostly have an max entropy of 50, i.e. 1015 (or 250) values in use, that is the reason why we find uint56 enough for storing significant bits. keywords: bits; cint64; uint256; value cache: eips-eip-3772.html plain text: eips-eip-3772.txt item: #497 of 3327 id: eips-eip-3779 author: eips title: eips-eip-3779 date: None words: 2311 flesch: 55 summary: return 0,0,0,invalid_instruction case RJUMP: // check for valid jump destination if ! The restrictions must be validated at contract initialization time – not at runtime – by the provided algorithm or its equivalent. keywords: jump; return; stack cache: eips-eip-3779.html plain text: eips-eip-3779.txt item: #498 of 3327 id: eips-eip-3788 author: eips title: eips-eip-3788 date: None words: 433 flesch: 39 summary: This was a feature to offer developers the ability to sumbit replayable transactions across different chains. Should a malicious actor (or accidental) choose to, they can easily have users submit transactions with a chainId = 0 on a non-mainnet network, allowing the malicious actor to replay the transaction on ethereum mainnet (or other networks for that matter) as a grief or sophisticated attack. keywords: chainid; ethereum cache: eips-eip-3788.html plain text: eips-eip-3788.txt item: #499 of 3327 id: eips-eip-3855 author: eips title: eips-eip-3855 date: None words: 607 flesch: 59 summary: Reducing the risk of contracts (mis)using various instructions as an optimisation measure. Because of the overall cost many try to use various other instructions to achieve the same effect. keywords: ethereum; stack cache: eips-eip-3855.html plain text: eips-eip-3855.txt item: #500 of 3327 id: eips-eip-3860 author: eips title: eips-eip-3860 date: None words: 1339 flesch: 54 summary: This places it in the group of early out-of-gas checks, including: stack underflow, memory expansion, static call violation, initcode hashing cost, and initcode cost introduced by this EIP. (Note that this is included in transaction intrinsic cost, i.e. transaction with not enough gas to cover initcode cost is invalid.) keywords: cost; gas; initcode; limit cache: eips-eip-3860.html plain text: eips-eip-3860.txt item: #501 of 3327 id: eips-eip-3978 author: eips title: eips-eip-3978 date: None words: 442 flesch: 37 summary: Gas refunds on reverts Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-3978: Reverted SSTORE deserves to be repriced to SLOAD gas (100 gas) Reverted LOG0, LOG1, LOG2, LOG3 and LOG4 deserve to be repriced to 100 gas Reverted CALL with value (positive_value_cost = 9,000 gas) deserves to be repriced to 100 gas Reverted CALL with value and account creation (value_to_empty_account_cost = 25,000 gas) deserves to be repriced to 100 gas Reverted CREATE and CREATE2 (32,000 gas) deserve to be repriced to 100 gas Reverted SELFDESTRUCT (5,000 or 25,000 gas) deserves to be repriced to 100 gas Moreover, it seems fair to charge CREATE and CREATE2 operations 32,000 fix price conditionally only if returned bytecode is not empty. keywords: ethereum; gas cache: eips-eip-3978.html plain text: eips-eip-3978.txt item: #502 of 3327 id: eips-eip-4 author: eips title: eips-eip-4 date: None words: 515 flesch: 39 summary: EIPs are classified by system layers with lower numbered layers involving more intricate interoperability requirements. Lower layers present considerably greater challenges in getting standards accepted and deployed. keywords: ethereum; layer cache: eips-eip-4.html plain text: eips-eip-4.txt item: #503 of 3327 id: eips-eip-4200 author: eips title: eips-eip-4200 date: None words: 1605 flesch: 50 summary: There are many cases where dynamic jumps are useful, such as returning to the caller. RJUMPV fallback case If no match is found (i.e. the default case) in the RJUMPV instruction execution will continue without branching. keywords: case; jumps; relative_offset; rjumpv cache: eips-eip-4200.html plain text: eips-eip-4200.txt item: #504 of 3327 id: eips-eip-4337 author: eips title: eips-eip-4337 date: None words: 7724 flesch: 40 summary: Storage access is limited as follows: self storage (of factory/paymaster, respectively) is allowed, but only if self entity is staked account storage access is allowed (see Storage access by Slots, below), in any case, may not use storage used by another UserOp sender in the same bundle (that is, paymaster and factory are not allowed as senders) Limitation on “CALL” opcodes (CALL, DELEGATECALL, CALLCODE, STATICCALL): must not use value (except from account to the entrypoint) must not revert with out-of-gas destination address must have code (EXTCODESIZE>0) or be a standard Ethereum precompile defined at addresses from 0x01 to 0x09 cannot call EntryPoint’s methods, except depositTo (to avoid recursion) Aggregator - a helper contract trusted by accounts to validate an aggregated signature. keywords: account; address; contract; entrypoint; gas; paymaster; sender; signature; storage; transaction; uint256; useroperation; value cache: eips-eip-4337.html plain text: eips-eip-4337.txt item: #505 of 3327 id: eips-eip-4341 author: eips title: eips-eip-4341 date: None words: 891 flesch: 41 summary: Such information is particularly useful if tokenIds are encoded with the sets of unicodes for logographic characters and emojis. Citation Please cite this document as: Simon Tian (@simontianx), ERC-4341: Ordered NFT Batch Standard [DRAFT], Ethereum Improvement Proposals, no. 4341, October 2021. keywords: function; standard; uint256 cache: eips-eip-4341.html plain text: eips-eip-4341.txt item: #506 of 3327 id: eips-eip-4345 author: eips title: eips-eip-4345 date: None words: 463 flesch: 42 summary: Also, gradual changes in blocktimes due to longer-term adjustments in difficulty can affect the timing of difficulty bomb epochs. Citation Please cite this document as: Tim Beiko (@timbeiko), James Hancock (@MadeOfTin), Thomas Jay Rush (@tjayrush), EIP-4345: Difficulty Bomb Delay to June 2022, Ethereum Improvement Proposals, no. 4345, October 2021. keywords: difficulty cache: eips-eip-4345.html plain text: eips-eip-4345.txt item: #507 of 3327 id: eips-eip-4353 author: eips title: eips-eip-4353 date: None words: 1187 flesch: 38 summary: This proposal outlines a standard that may be implemented by all wallets and marketplaces easily to correctly retrieve the staked token amount of an NFT. Motivation Without staked token data, the actual amount of staked tokens cannot be conveyed from token owners to other users, and cannot be displayed in wallets, marketplaces, or block explorers. Withdraw Mechanism - rules based approach for withdrawing staked tokens and making sure to update the balance of the staked tokens. keywords: nft; staked; tokens cache: eips-eip-4353.html plain text: eips-eip-4353.txt item: #508 of 3327 id: eips-eip-4361 author: eips title: eips-eip-4361 date: None words: 3909 flesch: 48 summary: When communicating to the server, the wallet SHOULD take precautions to protect user privacy by mitigating user information revealed as much as possible. Additional authentication not based on Ethereum addresses. keywords: ethereum; message; request; scheme; signing; siwe; user; wallet cache: eips-eip-4361.html plain text: eips-eip-4361.txt item: #509 of 3327 id: eips-eip-4393 author: eips title: eips-eip-4393 date: None words: 3736 flesch: 59 summary: Or in the case for upgradeable tip token contracts, an initialize method is REQUIRED to pass in the EIP-20 token address. If 'nft' is a multi token that has multiple holders then each holder MUST receive tip amount in proportion of their balance of multi tokens MUST emit the 'Tip' event to reflect the amounts that msg.sender tipped to holder(s) of 'nft'. keywords: address; contract; holder; nft; tip; token; user cache: eips-eip-4393.html plain text: eips-eip-4393.txt item: #510 of 3327 id: eips-eip-4396 author: eips title: eips-eip-4396 date: None words: 1701 flesch: 41 summary: Missed Slots Under Proof-of-Stake (PoS), block times are ideally uniform (always 12s), but missed slots lead to individual blocks with increased block time (24s, 36s, …). Time-Aware Base Fee Calculation Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-4396: Time-Aware Base Fee Calculation Accounts for block time in the base fee calculation to target a stable throughput by time instead of by block. keywords: base; block; fee cache: eips-eip-4396.html plain text: eips-eip-4396.txt item: #511 of 3327 id: eips-eip-4399 author: eips title: eips-eip-4399 date: None words: 2004 flesch: 47 summary: Using 2**64 threshold to determine PoS blocks The probability of RANDAO value to fall into the range between 0 and 2**64 and, thus, to be mixed with PoW difficulty values, is drastically low. Proposer may deliberately refuse to propose a block on the opportunity cost of proposer and transaction fees to prevent beacon chain randomness (a RANDAO mix) from being updated in a particular slot. keywords: block; difficulty; field; value cache: eips-eip-4399.html plain text: eips-eip-4399.txt item: #512 of 3327 id: eips-eip-4400 author: eips title: eips-eip-4400 date: None words: 986 flesch: 48 summary: There are no other standards that define a similar role for NFTs and the name (consumer) is not used by other EIP-721 related standards. When a Transfer event emits, this also indicates that the consumer address /// for that NFT (if any) is set to none event ConsumerChanged(address indexed owner, address indexed consumer, uint256 indexed tokenId); /// @notice Get the consumer address of an NFT /// @dev The zero address indicates that there is no consumer /// keywords: address; consumer; nft cache: eips-eip-4400.html plain text: eips-eip-4400.txt item: #513 of 3327 id: eips-eip-4430 author: eips title: eips-eip-4430 date: None words: 1100 flesch: 42 summary: We believe that this is a reasonable security model, as transaction descriptions can be audited at the same time as contract code, allowing auditors and code reviewers to check that transaction descriptions are accurate as part of their review. Due to the complexity of Ethereum transactions, wallets are very limited in their ability to provide insight into the effects of a transaction that the user is approving; outside special-cased support for common transactions such as ERC20 transfers, this often amounts to asking the user to sign an opaque blob of binary data. keywords: data; description; ethereum cache: eips-eip-4430.html plain text: eips-eip-4430.txt item: #514 of 3327 id: eips-eip-4444 author: eips title: eips-eip-4444 date: None words: 1159 flesch: 51 summary: Historical data is not necessary for validating new blocks, so once a client has synced the tip of the chain, historical data is only retrieved when requested explicitly over the JSON-RPC or when a peer attempts to sync the chain. Rationale This proposal forces clients to stop serving old historical data over p2p. keywords: clients; data; proposal cache: eips-eip-4444.html plain text: eips-eip-4444.txt item: #515 of 3327 id: eips-eip-4488 author: eips title: eips-eip-4488 date: None words: 1100 flesch: 46 summary: EIP-4488: Transaction calldata gas cost reduction with total calldata limit Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-4488: Transaction calldata gas cost reduction with total calldata limit Greatly decreases the gas cost of transaction calldata and simultaneously caps total transaction calldata in a block Authors Vitalik Buterin (@vbuterin), Ansgar Dietrichs (@adietrichs) Created 2021-11-23 Discussion Link https://ethereum-magicians.org/t/eip-4488-transaction-calldata-gas-cost-reduction-with-total-calldata-limit/7555 Table of Contents Abstract Motivation Specification Rationale Backwards Compatibility Security Considerations Copyright Abstract Decrease transaction calldata gas cost, and add a limit of how much total transaction calldata can be in a block. Citation Please cite this document as: Vitalik Buterin (@vbuterin), Ansgar Dietrichs (@adietrichs), EIP-4488: Transaction calldata gas cost reduction with total calldata limit [DRAFT], Ethereum Improvement Proposals, no. 4488, November 2021. keywords: block; calldata; ethereum; transaction cache: eips-eip-4488.html plain text: eips-eip-4488.txt item: #516 of 3327 id: eips-eip-4494 author: eips title: eips-eip-4494 date: None words: 1555 flesch: 47 summary: If the signing party holds ETH they can also just submit the Permit themselves, which can render previously signed Permits invalid. Signed Permit messages are censorable. keywords: deadline; nonce; permit; tokenid cache: eips-eip-4494.html plain text: eips-eip-4494.txt item: #517 of 3327 id: eips-eip-4519 author: eips title: eips-eip-4519 date: None words: 2857 flesch: 66 summary: ERC-4519: Non-Fungible Tokens Tied to Physical Assets Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: ERC ERC-4519: Non-Fungible Tokens Tied to Physical Assets Interface for non-fungible tokens representing physical assets that can generate or recover their own accounts and obey users. Authors Javier Arcenegui (@Hardblock-IMSE-CNM), Rosario Arjona (@RosarioArjona), Roberto Román , Iluminada Baturone (@lumi2018) Created 2021-12-03 Requires EIP-165, EIP-721 Table of Contents Abstract Motivation Specification Rationale Authentication Tie Time EIP-721-based Backwards Compatibility Test Cases Reference Implementation Security Considerations Copyright Abstract This EIP standardizes an interface for non-fungible tokens representing physical assets, such as Internet of Things (IoT) devices. keywords: asset; function; token; user cache: eips-eip-4519.html plain text: eips-eip-4519.txt item: #518 of 3327 id: eips-eip-4520 author: eips title: eips-eip-4520 date: None words: 461 flesch: 56 summary: EIP-4520: Multi-byte opcodes prefixed by EB and EC. Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-4520: Multi-byte opcodes prefixed by EB and EC. keywords: opcodes cache: eips-eip-4520.html plain text: eips-eip-4520.txt item: #519 of 3327 id: eips-eip-4521 author: eips title: eips-eip-4521 date: None words: 416 flesch: 27 summary: The interface for ERC-4521 transfer() MUST conform to ERC-20 and resulting transfers MUST fire the Transfer event as described in ERC-721. It should also simplify the task for contract programmers if they can rely on transfer() to both handle ERC-20 and NFTs. keywords: ethereum; transfer cache: eips-eip-4521.html plain text: eips-eip-4521.txt item: #520 of 3327 id: eips-eip-4524 author: eips title: eips-eip-4524 date: None words: 818 flesch: 37 summary: Backwards Compatibility There are no issues with backwards compatibility in this EIP, as the full suite of ERC-20 functions is unchanged. Created 2021-12-05 Discussion Link https://ethereum-magicians.org/t/why-isnt-there-an-erc-for-safetransfer-for-erc20/7604 Requires EIP-20, EIP-165 Table of Contents Abstract Motivation Specification Rationale Backwards Compatibility Test Cases Reference Implementation Security Considerations Copyright Abstract This standard extends ERC-20 tokens with EIP-165, and adds familiar functions from ERC-721 and ERC-1155 ensuring receiving contracts have implemented proper functionality. keywords: eip-165; erc-20 cache: eips-eip-4524.html plain text: eips-eip-4524.txt item: #521 of 3327 id: eips-eip-4527 author: eips title: eips-eip-4527 date: None words: 2134 flesch: 56 summary: Compared to USB and Bluetooth, QR Code data transmissions has a wider range of compatibility. Normally, it wouldn’t be broken by software changes like browser upgrades, system upgrade, and etc. Improved User experience: QR Code data transmissions can provide a better user experience compared to USB, Bluetooth, and file transfer especially when the user is using a mobile device. keywords: code; data; key cache: eips-eip-4527.html plain text: eips-eip-4527.txt item: #522 of 3327 id: eips-eip-4546 author: eips title: eips-eip-4546 date: None words: 1021 flesch: 15 summary: Wrapped Deposits Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-4546: Wrapped Deposits A singleton contract for managing asset deposits. The following interfaces SHOULD exist for contracts wishing to accept deposits: interface ERC20Receiver { function acceptERC20Deposit(address depositor, address token, uint amount) external returns (bool); } interface ERC721Receiver { function acceptERC721Deposit(address depositor, address token, uint tokenId) external returns (bool); } interface ERC1155Receiver { function acceptERC1155Deposit(address depositor, address token, uint tokenId, uint value, bytes calldata data) external returns (bool); function acceptERC1155BatchDeposit(address depositor, address token, uint[] calldata tokenIds, uint[] calldata values, bytes calldata data) external returns (bool); } interface EtherReceiver { function acceptEtherDeposit(address depositor, uint amount) external returns (bool); } A receiving contract MAY implement any of these functions as desired. keywords: address; calldata; uint cache: eips-eip-4546.html plain text: eips-eip-4546.txt item: #523 of 3327 id: eips-eip-4573 author: eips title: eips-eip-4573 date: None words: 1270 flesch: 60 summary: EIP-4573: Procedures for the EVM Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-4573: Procedures for the EVM Introduces support for EVM Procedures. We propose to add procedures – delimited blocks of code that can be entered only by calling into them via defined interfaces. keywords: frame; procedure; stack cache: eips-eip-4573.html plain text: eips-eip-4573.txt item: #524 of 3327 id: eips-eip-4626 author: eips title: eips-eip-4626 date: None words: 3597 flesch: 47 summary: Note that any unfavorable discrepancy between convertToShares and previewDeposit SHOULD be considered slippage in share price or some other type of condition, meaning the depositor will lose assets by depositing. - name: previewDeposit type: function stateMutability: view inputs: - name: assets type: uint256 outputs: - name: shares type: uint256 deposit Mints shares Vault shares to receiver by depositing exactly assets of underlying tokens. MUST emit the Deposit event. Note that any unfavorable discrepancy between convertToAssets and previewMint SHOULD be considered slippage in share price or some other type of condition, meaning the depositor will lose assets by minting. - name: previewMint type: function stateMutability: view inputs: - name: shares type: uint256 outputs: - name: assets type: uint256 mint Mints exactly shares Vault shares to receiver by depositing assets of underlying tokens. MUST emit the Deposit event. keywords: assets; revert; shares; type; vault cache: eips-eip-4626.html plain text: eips-eip-4626.txt item: #525 of 3327 id: eips-eip-4671 author: eips title: eips-eip-4671 date: None words: 1750 flesch: 48 summary: ERC-4671: Non-Tradable Tokens Standard Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-4671: Non-Tradable Tokens Standard A standard interface for non-tradable tokens, aka badges or souldbound NFTs. As the name implies, non-tradable tokens are made to not be traded or transferred, they are “soulbound”. keywords: @param; function; owner; token cache: eips-eip-4671.html plain text: eips-eip-4671.txt item: #526 of 3327 id: eips-eip-4675 author: eips title: eips-eip-4675 date: None words: 1770 flesch: 56 summary: (Test coverage : 100%) Reference Implementation MFNFT - Implementation Security Considerations To fractionalize an already minted NFT, it is evident that ownership of NFT should be given to token contracts before fractionalization. With the rise of multiple NFT projects needing to fractionalize NFT to FT, new type of token standard is needed to back up them. keywords: address; token cache: eips-eip-4675.html plain text: eips-eip-4675.txt item: #527 of 3327 id: eips-eip-4736 author: eips title: eips-eip-4736 date: None words: 2668 flesch: 36 summary: If attackers compromise a significant number of consensus layer nodes, it would pose risks to the entire Ethereum community. It is also possible for client nodes to help broadcast signed BLSToExecutionChange requests to ensure as many nodes witness this message as soon as possible in a fair manner. keywords: blstoexecutionchange; claim; key; user cache: eips-eip-4736.html plain text: eips-eip-4736.txt item: #528 of 3327 id: eips-eip-4747 author: eips title: eips-eip-4747 date: None words: 1191 flesch: 30 summary: A client may assume that STATICCALLs to empty accounts never occur and that CALLs to empty accounts in STATICCALL contexts never occur. Test Cases All test cases involving empty accounts in the Ethereum execution layer test suite shall be removed unless they relate to the Spurious Dragon Hardfork. keywords: accounts; eip-161; ethereum cache: eips-eip-4747.html plain text: eips-eip-4747.txt item: #529 of 3327 id: eips-eip-4750 author: eips title: eips-eip-4750 date: None words: 1595 flesch: 49 summary: In addition to container format validation rules above, we extend code section validation rules (as defined in EIP-3670). Dynamic jump instructions are disallowed. keywords: code; execution; section; stack cache: eips-eip-4750.html plain text: eips-eip-4750.txt item: #530 of 3327 id: eips-eip-4758 author: eips title: eips-eip-4758 date: None words: 501 flesch: 47 summary: Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. Citation Please cite this document as: Guillaume Ballet (@gballet), Vitalik Buterin (@vbuterin), Dankrad Feist (@dankrad), EIP-4758: Deactivate SELFDESTRUCT [DRAFT], Ethereum Improvement Proposals, no. 4758, February 2022. keywords: ethereum; selfdestruct cache: eips-eip-4758.html plain text: eips-eip-4758.txt item: #531 of 3327 id: eips-eip-4760 author: eips title: eips-eip-4760 date: None words: 734 flesch: 48 summary: Available: https://eips.ethereum.org/EIPS/eip-4760. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. Citation Please cite this document as: Guillaume Ballet (@gballet), Vitalik Buterin (@vbuterin), Dankrad Feist (@dankrad), EIP-4760: SELFDESTRUCT bomb [DRAFT], Ethereum Improvement Proposals, no. 4760, February 2022. keywords: contract; selfdestruct cache: eips-eip-4760.html plain text: eips-eip-4760.txt item: #532 of 3327 id: eips-eip-4762 author: eips title: eips-eip-4762 date: None words: 1884 flesch: 50 summary: Access events We define access events as follows. Witness gas costs Remove the following gas costs: Increased gas cost of CALL if it is nonzero-value-sending EIP-2200 SSTORE gas costs except for the SLOAD_GAS 200 per byte contract code cost Reduce gas cost: CREATE to 1000 Constant Value WITNESS_BRANCH_COST 1900 WITNESS_CHUNK_COST 200 SUBTREE_EDIT_COST 3000 CHUNK_EDIT_COST 500 CHUNK_FILL_COST 6200 When executing a transaction, maintain four sets: accessed_subtrees: Set[Tuple[address, int]] accessed_leaves: Set[Tuple[address, int, int]] edited_subtrees: Set[Tuple[address, int]] edited_leaves: Set[Tuple[address, int, int]] When an access event of (address, sub_key, leaf_key) occurs, perform the following checks: If (address, sub_key) is not in accessed_subtrees, charge WITNESS_BRANCH_COST gas and add that tuple to accessed_subtrees. keywords: access; address; events; gas cache: eips-eip-4762.html plain text: eips-eip-4762.txt item: #533 of 3327 id: eips-eip-4788 author: eips title: eips-eip-4788 date: None words: 1553 flesch: 54 summary: To improve the usability of this oracle, a small history of block roots are stored in the contract. Use of block root over state root does mean proofs will require a few additional nodes but this cost is negligible (and could be amortized across all consumers, e.g. with a singleton state root contract that caches the proof per slot). keywords: beacon; block; contract; root cache: eips-eip-4788.html plain text: eips-eip-4788.txt item: #534 of 3327 id: eips-eip-4799 author: eips title: eips-eip-4799 date: None words: 1290 flesch: 27 summary: This way, new contracts with innovative ownership structures can be deployed, but they can still leverage the authenticity afforded by established NFT contracts - in the past a wrapping contract meant brand new NFTs with no established authenticity. ERC721(msg.sender).approve(from, sourceTokenId); return IERC721Receiver.onERC721Received.selector; } function supportsInterface(bytes4 interfaceId) public view virtual override returns (bool) { return (interfaceId == type(IERC4799).interfaceId || interfaceId == type(IERC721Receiver).interfaceId); } } // SPDX-License-Identifier: CC0-1.0 pragma solidity >=0.8.0 <0.9.0; import ./IERC4799.sol; import ./IERC4799NFT.sol; import @openzeppelin/contracts/utils/introspection/ERC165Checker.sol; contract DesignatedOwner { function designatedOwnerOf( IERC4799NFT tokenContract, uint256 tokenId, uint256 maxDepth ) public view returns (address owner) { owner = tokenContract.ownerOf(tokenId); keywords: contract; nft; ownership cache: eips-eip-4799.html plain text: eips-eip-4799.txt item: #535 of 3327 id: eips-eip-4803 author: eips title: eips-eip-4803 date: None words: 393 flesch: 41 summary: EIP-4803: Limit transaction gas to a maximum of 2^63-1 Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-4803: Limit transaction gas to a maximum of 2^63-1 Valid transactions must have a reasonable gas limit Authors Alex Beregszaszi (@axic) Created 2022-02-02 Discussion Link https://ethereum-magicians.org/t/eip-4803-limit-transaction-gas-to-a-maximum-of-2-63-1/8296 Table of Contents Abstract Motivation Specification Rationale 2^63-1 vs 2^64-1 Current limit Backwards Compatibility Security Considerations Test Cases Copyright Abstract Limit transaction gas to be between 0 and 2^63-1. Citation Please cite this document as: Alex Beregszaszi (@axic), EIP-4803: Limit transaction gas to a maximum of 2^63-1 [DRAFT], Ethereum Improvement Proposals, no. 4803, February 2022. keywords: limit cache: eips-eip-4803.html plain text: eips-eip-4803.txt item: #536 of 3327 id: eips-eip-4804 author: eips title: eips-eip-4804 date: None words: 1370 flesch: 62 summary: ERC-4804: Web3 URL to EVM Call Message Translation Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: ERC ERC-4804: Web3 URL to EVM Call Message Translation A translation of an HTTP-style Web3 URL to an EVM call message Authors Qi Zhou (@qizhou), Chao Pi (@pichaoqkc), Sam Wilson (@SamWilsn) The Web3 URL should be compatible with HTTP-URL standard including relative pathing, query, fragment, etc so that the support of existing HTTP-URL (e.g., by browser) can be easily extended to Web3 URL with minimal modification. keywords: address; protocol cache: eips-eip-4804.html plain text: eips-eip-4804.txt item: #537 of 3327 id: eips-eip-4824 author: eips title: eips-eip-4824 date: None words: 3178 flesch: 38 summary: Some DAOs and DAO frameworks (e.g. Gnosis Safe, Tribute), maintain an explicit, on-chain set of members, sometimes called owners or stewards. More consistent data across the ecosystem is also a prerequisite for future DAO standards. keywords: address; chain; contract; dao; daos; daouri; json; proposal cache: eips-eip-4824.html plain text: eips-eip-4824.txt item: #538 of 3327 id: eips-eip-4834 author: eips title: eips-eip-4834 date: None words: 1825 flesch: 43 summary: The account that may or may not be able to create/update a subdomain /// @param name The subdomain name that would be created/updated /// @param subdomain The subdomain that would be set /// @return Whether an account can update or create the subdomain function canCreateDomain(address updater, string memory name, address subdomain) external view returns (bool); /// The account that may or may not be able to create/update a subdomain /// @param name The subdomain name that would be created/updated /// @param subdomain The subdomain that would be set /// @return Whether an account can update or create the subdomain function canSetDomain(address updater, string memory name, address subdomain) external view returns (bool); /// keywords: @param; account; subdomain cache: eips-eip-4834.html plain text: eips-eip-4834.txt item: #539 of 3327 id: eips-eip-4844 author: eips title: eips-eip-4844 date: None words: 3303 flesch: 46 summary: This means that blob transactions cannot have the form of a create transaction. Nodes MUST NOT automatically broadcast blob transactions to their peers. keywords: blob; block; data; gas; layer; rollups; sharding; transaction cache: eips-eip-4844.html plain text: eips-eip-4844.txt item: #540 of 3327 id: eips-eip-4863 author: eips title: eips-eip-4863 date: None words: 840 flesch: 48 summary: Having a simple ordering scheme like this facilitates optimizations clients may do with respect to withdrawal processing, which would be hampered if withdrawal transactions could be placed in the block freely. Security Considerations Consensus-layer validation of withdrawal transactions is critical to ensure that the proper amount of ETH is withdrawn back into the execution layer. keywords: block; transaction; type cache: eips-eip-4863.html plain text: eips-eip-4863.txt item: #541 of 3327 id: eips-eip-4881 author: eips title: eips-eip-4881 date: None words: 2049 flesch: 30 summary: result: List[Hash32]) -> uint: # returns the number of finalized deposits in the tree # while populating result with the finalized hashes pass def create(leaves: List[Hash32], depth: uint) -> MerkleTree: The image below illustrates the evolution of the deposit Merkle tree under this process alongside the corresponding DepositTreeSnapshot as new deposits are added and older deposits become finalized: Rationale The format in this specification was chosen to achieve several goals simultaneously: Enable reconstruction of the deposit contract Merkle tree without requiring full nodes to store all historical contract logs Avoid requiring consensus nodes to retain more deposits than necessary to fully participate in consensus Simplicity of implementation (see Reference Implementation section) keywords: def; deposit; return; uint cache: eips-eip-4881.html plain text: eips-eip-4881.txt item: #542 of 3327 id: eips-eip-4883 author: eips title: eips-eip-4883 date: None words: 583 flesch: 46 summary: Composability allows onchain SVG NFTs to be crafted. IERC4883 is IERC165 { function renderTokenById(uint256 id) external view returns (string memory); } renderTokenById must return the SVG body for the specified token id and must either be an empty string or valid SVG element(s). keywords: nft; svg cache: eips-eip-4883.html plain text: eips-eip-4883.txt item: #543 of 3327 id: eips-eip-4885 author: eips title: eips-eip-4885 date: None words: 2229 flesch: 53 summary: ERC-4885: Subscription NFTs and Multi Tokens Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-4885: Subscription NFTs and Multi Tokens An interface for subscription tokens that gives holders subscriptions to NFTs and multi tokens Authors Jules Lai (@julesl23) EIP-20 tokens are deposited in exchange for subscription tokens that give the right to use said non-fungible and multi tokens for a specified time limited or unlimited period. keywords: nft; subscriber; subscription; token; tokenid cache: eips-eip-4885.html plain text: eips-eip-4885.txt item: #544 of 3327 id: eips-eip-4886 author: eips title: eips-eip-4886 date: None words: 2654 flesch: 47 summary: Get Proxy Record for Caller function getProxyRecordForCaller() external view returns (address nominator, address proxy, address delivery); Returns Nominator, Proxy and Delivery address for msg.sender as Proxy address. Get Proxy Record function getProxyRecord(address _proxy) external view returns (address nominator, address proxy, address delivery); Returns Nominator, Proxy and Delivery address for a passed Proxy address. keywords: address; nominator; proxy; returns cache: eips-eip-4886.html plain text: eips-eip-4886.txt item: #545 of 3327 id: eips-eip-4895 author: eips title: eips-eip-4895 date: None words: 1146 flesch: 34 summary: Withdrawals provide key information from the consensus layer: a monotonically increasing index, starting from 0, as a uint64 value that increments by 1 per withdrawal to uniquely identify each withdrawal the validator_index of the validator, as a uint64 value, on the consensus layer the withdrawal corresponds to a recipient for the withdrawn ether address as a 20-byte value a nonzero amount of ether given in Gwei (1e9 wei) as a uint64 value. NOTE: the index for each withdrawal is a global counter spanning the entire sequence of withdrawals. Security Considerations Consensus-layer validation of withdrawal transactions is critical to ensure that the proper amount of ETH is withdrawn back into the execution layer. keywords: execution; level; payload; withdrawals cache: eips-eip-4895.html plain text: eips-eip-4895.txt item: #546 of 3327 id: eips-eip-4906 author: eips title: eips-eip-4906 date: None words: 585 flesch: 50 summary: Not emitting MetadataUpdate event is RECOMMENDED when a token is minted. Not emitting MetadataUpdate event is RECOMMENDED when a token is burned. keywords: event; metadata cache: eips-eip-4906.html plain text: eips-eip-4906.txt item: #547 of 3327 id: eips-eip-4907 author: eips title: eips-eip-4907 date: None words: 1524 flesch: 53 summary: The new user of the NFT /// @param expires UNIX timestamp, The new user could use the NFT before expires function setUser(uint256 tokenId, address user, uint64 expires) public virtual{ require(_isApprovedOrOwner(msg.sender, tokenId), ERC4907: transfer caller is not owner nor approved); UserInfo storage info = _users[tokenId]; info.user = user; info.expires = expires; emit UpdateUser(tokenId, user, expires); } /// @notice Get the user address of an NFT /// @dev Furthermore, applications of this model (such as renting) often demand that user addresses have only temporary access to using the NFT. keywords: address; expires; nft; user cache: eips-eip-4907.html plain text: eips-eip-4907.txt item: #548 of 3327 id: eips-eip-4910 author: eips title: eips-eip-4910 date: None words: 7939 flesch: 53 summary: Therefore, the NFT contract needs to be aware of NFT payments, which in turn requires the NFT contract to be aware which tokens can be used for trading. Modified NFT Transfer function This document adheres to the ERC-721 interface format for the safeTransferFrom function as given below: function safeTransferFrom(address from, address to, uint256 tokenId, bytes memory _data) external virtual override Note, that the input parameters must satisfy several requirements for the NFT(s) to be transferred AFTER royalties have been properly distributed. keywords: address; contract; function; nft; nft contract; payment; royalty account; royalty sub; sub account; token; tokenid cache: eips-eip-4910.html plain text: eips-eip-4910.txt item: #549 of 3327 id: eips-eip-4931 author: eips title: eips-eip-4931 date: None words: 2979 flesch: 42 summary: The method will return true when the contract is serving downgrades and otherwise false /// @return The status of the downgrade as a boolean function isDowngradeActive() external view returns(bool) { return downgradeStatus; } /// @dev A getter for the ratio of destination tokens to source tokens received when conducting an upgrade /// @return Two uint256, the first represents the numerator while the second represents /// the denominator of the ratio of destination tokens to source tokens allotted during the upgrade function ratio() external view returns(uint256, uint256) { return (numeratorRatio, denominatorRatio); } /// @dev A getter for the total amount of source tokens that have been upgraded to destination tokens. /// @dev A getter for the total amount of source tokens that have been upgraded to destination tokens. keywords: destination; source; tokens; upgrade cache: eips-eip-4931.html plain text: eips-eip-4931.txt item: #550 of 3327 id: eips-eip-4938 author: eips title: eips-eip-4938 date: None words: 475 flesch: 53 summary: At this time, some client implementations cannot serve GetNodeData requests because they do not store the state in a compatible way. Serving GetNodeData requests requires clients to store state as a mapping of hashes to trie nodes. keywords: getnodedata; protocol cache: eips-eip-4938.html plain text: eips-eip-4938.txt item: #551 of 3327 id: eips-eip-4944 author: eips title: eips-eip-4944 date: None words: 527 flesch: 41 summary: Available: https://eips.ethereum.org/EIPS/eip-4944. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. ERC-4944: Contract with Exactly One Non-fungible Token Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-4944: Contract with Exactly One Non-fungible Token An ERC-721 compatible single-token NFT Authors Víctor Muñoz (@victormunoz), Josep Lluis de la Rosa (@peplluis7), Andres El-Fakdi (@Bluezfish) Created 2022-03-25 Discussion Link https://ethereum-magicians.org/t/erc721-minting-only-one-token/8602/2 Requires EIP-721 Table of Contents keywords: contract; token cache: eips-eip-4944.html plain text: eips-eip-4944.txt item: #552 of 3327 id: eips-eip-4950 author: eips title: eips-eip-4950 date: None words: 748 flesch: 43 summary: If an artist T has created a digital piece of art P with an NFT, then T creates 2 entangled tokens A and B so that he keeps A and transfer B to P. By construction of entangled tokens, only one transfer is possible for them, thus the artist proofs he’s been the creator of P by sending a transaction to A that is visible from B. Otherwise, the owner of P might check the authenticity of the artist by sending a transaction to B so that the artist might proof by showing the outcome out of A. A version of this use case is when one user U mints his piece of art directly in the form of an entangled token A; then the user U sells/transfers it while keeping the entangled token B in the U’s wallet. These applications of entangled tokens are envisaged to be useful for: NFT authorship / art creation Distribution of royalties by the creator. keywords: contract; nft; tokens cache: eips-eip-4950.html plain text: eips-eip-4950.txt item: #553 of 3327 id: eips-eip-4955 author: eips title: eips-eip-4955 date: None words: 985 flesch: 45 summary: An example of this is the metaverses like Decentraland or TheSandbox where they need different 3d models to render the NFT based on the visual/engine of each. ERC-4955: Vendor Metadata Extension for NFTs Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: ERC ERC-4955: Vendor Metadata Extension for NFTs Add a new field to NFT metadata to store vendor specific data Authors Ignacio Mazzara (@nachomazzara) Created 2022-03-29 Requires EIP-721, EIP-1155 Table of Contents Abstract Motivation Specification Schema Example Rationale Armatures Metadata (Representations Files) keywords: description; metadata; nft cache: eips-eip-4955.html plain text: eips-eip-4955.txt item: #554 of 3327 id: eips-eip-4972 author: eips title: eips-eip-4972 date: None words: 766 flesch: 48 summary: ┌───────────────┐ ┌───────────┐ ┌───────────────┐ │ Owned Account ◄──own───┤ Name Node ◄───own───┤ Name Owner │ └───────────────┘ └───────────┘ └───────────────┘ Interface The core interface required for a name service to have is: interface INameServiceRegistry { /// @notice get account address owned by the name node /// @params node represents a name node /// @return the address of an account function ownedAccount( bytes32 node ) external view returns(address); } The following diagram illustrates the relationship between NOA, name node, and name owner, with the ownership being guaranteed by the name service. keywords: ─ ┐ cache: eips-eip-4972.html plain text: eips-eip-4972.txt item: #555 of 3327 id: eips-eip-4973 author: eips title: eips-eip-4973 date: None words: 1900 flesch: 55 summary: As with ERC-721, transfers between two accounts are represented by address from and address to being non-zero addresses. ERC-721’s ERC721Metadata (0x5b5e139f) ABTs must not implement the interfaces: ERC-721’s ERC721 (0x80ac58cd) An ABT receiver must be able to always call function unequip(address _tokenId) to take their ABT off-chain. // SPDX-License-Identifier: CC0-1.0 pragma solidity ^0.8.6; /// @title Account-bound tokens /// @dev See https://eips.ethereum.org/EIPS/eip-4973 /// keywords: abt; address; function; metadata; signature cache: eips-eip-4973.html plain text: eips-eip-4973.txt item: #556 of 3327 id: eips-eip-4974 author: eips title: eips-eip-4974 date: None words: 1573 flesch: 49 summary: Ratings An interface for assigning and managing numerical ratings Authors Daniel Tedesco (@dtedesco1) Created 2022-04-02 Discussion Link https://ethereum-magicians.org/t/8805 Requires EIP-165 Table of Contents Abstract Motivation Specification Rationale Rating Assignment Choice of int8 Rating Changes Interface Detection Metadata Choices Drawbacks Backwards Compatibility Reference Implementation Security Considerations Copyright Abstract This standard defines a standardized interface for assigning and managing numerical ratings on the Ethereum blockchain. This allows ratings to be codified within smart contracts and recognized by other applications, enabling a wide range of new use cases for tokens. keywords: address; contract; operator; ratings cache: eips-eip-4974.html plain text: eips-eip-4974.txt item: #557 of 3327 id: eips-eip-4987 author: eips title: eips-eip-4987 date: None words: 1277 flesch: 32 summary: Citation Please cite this document as: Devin Conley (@devinaconley), ERC-4987: Held token interface [DRAFT], Ethereum Improvement Proposals, no. 4987, September 2021. token address * @param owner functional token owner * @param tokenId held token ID * @return held token balance */ function heldBalanceOf( address tokenAddress, address owner, uint256 tokenId ) external view returns (uint256); } Rationale This interface is designed to be extremely lightweight and compatible with any existing token contract. keywords: @param; owner; token cache: eips-eip-4987.html plain text: eips-eip-4987.txt item: #558 of 3327 id: eips-eip-5 author: eips title: eips-eip-5 date: None words: 1070 flesch: 58 summary: Specification The gas and memory semantics for CALL, CALLCODE and DELEGATECALL (called later as CALL*) are changed in the following way (CREATE does not write to memory and is thus unaffected): Suppose the arguments to CALL* are gas, address, value, input_start, input_size, output_start, output_size, then, at the beginning of the opcode, gas for growing memory is only charged for input_start + input_size, but not for output_start + output_size. The change in semantics affects existing contracts in two ways: Overlaps in allocated memory. keywords: gas; memory cache: eips-eip-5.html plain text: eips-eip-5.txt item: #559 of 3327 id: eips-eip-5003 author: eips title: eips-eip-5003 date: None words: 1033 flesch: 51 summary: There are countless other benefits that come from having a contract account or account abstraction, like choosing one’s own authentication algorithm, setting spending limits, enabling social recovery, allowing key rotation, arbitrarily and transitively delegating capabilities, and just about anything else we can imagine. New users have access to these benefits using smart contract wallets, and new contracts can adopt recent standards to enable app-layer account abstraction (like EIP-4337), but these would neglect the vast majority of existing Ethereum users’ accounts. keywords: account; authusurp; code cache: eips-eip-5003.html plain text: eips-eip-5003.txt item: #560 of 3327 id: eips-eip-5005 author: eips title: eips-eip-5005 date: None words: 1305 flesch: 45 summary: function disableModule(address prevModule, address module) external; /// @dev Allows a Module to execute a transaction. @param to Destination address of module transaction. keywords: @param; address; module cache: eips-eip-5005.html plain text: eips-eip-5005.txt item: #561 of 3327 id: eips-eip-5006 author: eips title: eips-eip-5006 date: None words: 901 flesch: 57 summary: // SPDX-License-Identifier: CC0-1.0 pragma solidity ^0.8.0; interface IERC5006 { struct UserRecord { uint256 tokenId; address owner; uint64 amount; address user; uint64 expiry; } / */ event CreateUserRecord( uint256 recordId, uint256 tokenId, uint64 amount, address owner, address user, uint64 expiry ); /** * @dev Emitted when record of `recordId` are deleted. keywords: owner; user cache: eips-eip-5006.html plain text: eips-eip-5006.txt item: #562 of 3327 id: eips-eip-5007 author: eips title: eips-eip-5007 date: None words: 635 flesch: 58 summary: ERC-5007: Time NFT, ERC-721 Time Extension Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: ERC ERC-5007: Time NFT, ERC-721 Time Extension Add start time and end time to ERC-721 tokens. Citation Please cite this document as: Anders (@0xanders), Lance (@LanceSnow), Shrug , ERC-5007: Time NFT, ERC-721 Time Extension, Ethereum Improvement Proposals, no. 5007, April 2022. keywords: nft; time cache: eips-eip-5007.html plain text: eips-eip-5007.txt item: #563 of 3327 id: eips-eip-5008 author: eips title: eips-eip-5008 date: None words: 448 flesch: 57 summary: ERC-5008: ERC-721 Nonce Extension Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 📢 Last Call Standards Track: ERC ERC-5008: ERC-721 Nonce Extension Add a `nonce` function to ERC-721. Citation Please cite this document as: Anders (@0xanders), Lance (@LanceSnow), Shrug , ERC-5008: ERC-721 Nonce Extension keywords: erc-721; nonce cache: eips-eip-5008.html plain text: eips-eip-5008.txt item: #564 of 3327 id: eips-eip-5018 author: eips title: eips-eip-5018 date: None words: 909 flesch: 50 summary: function countChunks(bytes memory name) external view returns (uint256 numOfChunks); writeChunk Writes a chunk of data to the file by an account with write permission. function chunkSize(bytes memory name, uint256 chunkId) external view returns (uint256 chunkSize, bool exist); removeChunk Removes a chunk of the file name and returns false if such chunk does not exist. keywords: file; memory; returns cache: eips-eip-5018.html plain text: eips-eip-5018.txt item: #565 of 3327 id: eips-eip-5022 author: eips title: eips-eip-5022 date: None words: 626 flesch: 66 summary: Backwards compatibility Contracts that depend on hardcoded gas costs will break if they create state. It is a gas schedule change, so transactions from an epoch before FORK_BLOCK should be treated with previous gas costs. keywords: gas; state cache: eips-eip-5022.html plain text: eips-eip-5022.txt item: #566 of 3327 id: eips-eip-5023 author: eips title: eips-eip-5023 date: None words: 1509 flesch: 43 summary: In case transfering is disabled, shareable tokens become shareable non-transferable tokens, where they can be minted and given or shared to other people, but they cannot be transferred away. We envision that shareable tokens can work both as incentives but also as representations of items that are typically digital in their nature and gain more value as they are shared. keywords: contracts; function; sharing; token cache: eips-eip-5023.html plain text: eips-eip-5023.txt item: #567 of 3327 id: eips-eip-5027 author: eips title: eips-eip-5027 date: None words: 702 flesch: 39 summary: EIP-5027: Remove the limit on contract code size Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-5027: Remove the limit on contract code size Change the limit on contract size from 24576 to infinity Authors Qi Zhou (@qizhou) Created 2022-04-21 Discussion Link https://ethereum-magicians.org/t/eip-5027-unlimit-contract-code-size/9010 Requires EIP-170, EIP-2929, EIP-2930 Table of Contents Abstract Motivation Specification Parameters Rationale Gas Metering Backwards Compatibility Reference Implementation Security Considerations Copyright Abstract Remove the limit on the contract code size, i.e., only limit the contract code size by block gas limit, with minimal changes to existing code and proper gas metering adjustment to avoid possible attacks. Although several techniques such as splitting a large contract into several sub-contracts can alleviate the issue, these techniques inevitably increase the burden of developing/deploying/maintaining smart contracts. keywords: contract; size cache: eips-eip-5027.html plain text: eips-eip-5027.txt item: #568 of 3327 id: eips-eip-5050 author: eips title: eips-eip-5050 date: None words: 2844 flesch: 43 summary: @param action The action to send function sendAction(Action memory action) external payable; /// @param action The action to handle function onActionReceived(Action calldata action, uint256 _nonce) external payable; /// @notice Retrieve list of actions that can be received. keywords: @param; account; action; address; contract; state cache: eips-eip-5050.html plain text: eips-eip-5050.txt item: #569 of 3327 id: eips-eip-5058 author: eips title: eips-eip-5058 date: None words: 1571 flesch: 60 summary: We believe the proposed standard will encourage NFT owners to participate more actively in NFTFi projects and, hence, improve the livelihood of the whole NFT ecosystem. NFT lock period keywords: lock; nft; operator; tokenid cache: eips-eip-5058.html plain text: eips-eip-5058.txt item: #570 of 3327 id: eips-eip-5065 author: eips title: eips-eip-5065 date: None words: 536 flesch: 49 summary: Instruction for transferring ether Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-5065: Citation Please cite this document as: Mudit Gupta (@maxsam4), EIP-5065: Instruction for transferring ether [DRAFT], Ethereum Improvement Proposals, no. 5065, April 2022. keywords: ether; ethereum cache: eips-eip-5065.html plain text: eips-eip-5065.txt item: #571 of 3327 id: eips-eip-5069 author: eips title: eips-eip-5069 date: None words: 1154 flesch: 50 summary: Specific eligibility requirements are left to individual current EIP Editors, but the general requirements are: A strong belief in the above mission; Proficiency with English (both written and spoken); Structure EIP Editors We, the Editors, consist of some number of EIP Editors and one Keeper of Consensus (or just Keeper for short) elected by and from the EIP Editors. keywords: editor; eip; proposals cache: eips-eip-5069.html plain text: eips-eip-5069.txt item: #572 of 3327 id: eips-eip-5081 author: eips title: eips-eip-5081 date: None words: 819 flesch: 46 summary: TODO(@xinbenlv): to include in the motivation: Expiring transactions are transactions that have low time preference, but can easily become invalid in the future. When network is congested, gas price are high, for critical transactions user might try gas price that is much higher than an average day. keywords: ethereum; transaction cache: eips-eip-5081.html plain text: eips-eip-5081.txt item: #573 of 3327 id: eips-eip-5094 author: eips title: eips-eip-5094 date: None words: 826 flesch: 41 summary: An example of adding a network with RPC endpoints https://rpc-polygon.com and https://rpc-mainnet.matic.network, the name Polygon Mainnet, token Matic, symbol MATIC, decimals 18, explorer at https://polygonscan.com/, and Chain ID 137 would look as follows: ethereum:network-add@137/?chain_name=Polygon%20Mainnet&rpc_url=https%3A%2F%2Frpc-polygon.com&rpc_url=https%3A%2F%2Frpc-mainnet.matic.network&name=Matic&symbol=MATIC&decimals=18&explorer_url=https%3A%2F%2Fpolygonscan.com Rationale In furtherance of the Ethereum URL saga, network configuration is a needed addition to the possibility of Ethereum URLs. This EIP aims to introduce a new type of URL for usage with deep-linking, QR, and more, to allow users to seamlessly add new networks to their (for ex. mobile) wallet to then be able to more easily partake in pay-, tx-, or other Ethereum URL interactions. keywords: ethereum; network cache: eips-eip-5094.html plain text: eips-eip-5094.txt item: #574 of 3327 id: eips-eip-5095 author: eips title: eips-eip-5095 date: None words: 3026 flesch: 44 summary: The amount of the transfer. function _transferOut(address to, uint256 amount) internal virtual { underlying.safeTransfer(to, amount); } /* ACCOUNTING FUNCTIONS *****************************************************************************************************************/ /// @notice Calculates the amount of underlying tokens that would be exchanged for a given amount of principal tokens. The amount of principal tokens that would be redeemed. function previewWithdraw(uint256 underlyingAmount) external view afterMaturity returns (uint256 principalAmount) { return _previewWithdraw(underlyingAmount); } function _previewWithdraw(uint256 underlyingAmount) internal view virtual returns (uint256 principalAmount) { return _convertToPrincipal(underlyingAmount); // should include fees/slippage } /// @notice Calculates the maximum amount of underlying tokens that can be withdrawn by a given owner. keywords: principal; tokens; type; uint256; underlying cache: eips-eip-5095.html plain text: eips-eip-5095.txt item: #575 of 3327 id: eips-eip-5114 author: eips title: eips-eip-5114 date: None words: 926 flesch: 45 summary: Rationale Immutability By requiring that badges can never move, we both guarantee non-separability and non-mergeability among collections of soulbound badges that are bound to a single NFT while simultaneously allowing users to aggressively cache results. A persona is any actor (which could be a group of humans) that collects multiple soulbound badges over time to build up a collection of badges. keywords: badge; collectionuri cache: eips-eip-5114.html plain text: eips-eip-5114.txt item: #576 of 3327 id: eips-eip-5115 author: eips title: eips-eip-5115 date: None words: 2878 flesch: 46 summary: SY tokens can wrap over most yield generating mechanisms in DeFi, including ERC-4626 vaults for projects built on top of yield-bearing tokens. If depositFromInternalBalance is set to false, msg.sender will need to initially deposit amountTokenToDeposit of input token $i$ (tokenIn) into the SY contract, then this function will convert the amountTokenToDeposit of input token $i$ into $d_a$ worth of asset and deposit this amount into the pool for the receiver, who will receive amountSharesOut of SY tokens (shares). keywords: address; pool; token; uint256; yield cache: eips-eip-5115.html plain text: eips-eip-5115.txt item: #577 of 3327 id: eips-eip-5131 author: eips title: eips-eip-5131 date: None words: 2471 flesch: 42 summary: ********************* function _verifyMainENS( address ensRegistry, address mainAddress, bytes32 mainENSNodeHash, string calldata authKey, address authAddress ) private view { // Check if the ENS nodes resolve correctly to the provided addresses address mainResolver = ENS(ensRegistry).resolver(mainENSNodeHash); require(mainResolver != address(0), Main ENS not registered); require(mainAddress == Resolver(mainResolver).addr(mainENSNodeHash), Main address is wrong); // Verify the authKey TEXT record is set to authAddress by mainENS string memory authText = Resolver(mainResolver).text(mainENSNodeHash, string(abi.encodePacked(eip5131:, authKey))); Further, wallet authentication can be chained so that a secondary wallet could itself authorize one or many tertiary wallets, which then have signing rights for both the secondary address as well as the root main address. keywords: address; authaddress; ens; mainaddress; wallet cache: eips-eip-5131.html plain text: eips-eip-5131.txt item: #578 of 3327 id: eips-eip-5133 author: eips title: eips-eip-5133 date: None words: 485 flesch: 36 summary: Also, gradual changes in blocktimes due to longer-term adjustments in difficulty can affect the timing of difficulty bomb epochs. Wild shifts in difficulty can affect this number severely. keywords: bomb; difficulty cache: eips-eip-5133.html plain text: eips-eip-5133.txt item: #579 of 3327 id: eips-eip-5139 author: eips title: eips-eip-5139 date: None words: 2009 flesch: 55 summary: Provider lists MAY instead be published using HTTPS. Provider lists published in this way MUST allow reasonable access from other origins (generally by setting the header Access-Control-Allow-Origin: *.) keywords: list; provider; type; version cache: eips-eip-5139.html plain text: eips-eip-5139.txt item: #580 of 3327 id: eips-eip-5143 author: eips title: eips-eip-5143 date: None words: 1284 flesch: 40 summary: MUST revert if minting shares shares cost more then maxAssets underlying tokens. MUST revert if all of shares cannot be redeemed (due to withdrawal limit being reached, slippage, the owner not having enough shares, etc). MUST revert if redeeming shares shares sends less than minAssets underlying tokens to receiver. keywords: shares; type; uint256 cache: eips-eip-5143.html plain text: eips-eip-5143.txt item: #581 of 3327 id: eips-eip-5164 author: eips title: eips-eip-5164 date: None words: 1017 flesch: 40 summary: interface MessageDispatcher { event MessageDispatched( bytes32 indexed messageId, address indexed from, uint256 indexed toChainId, address to, bytes data, ); } - name: MessageDispatched type: event inputs: - name: messageId indexed: true type: bytes32 - name: from indexed: true type: address - name: toChainId indexed: true type: uint256 - name: to type: address - name: data type: bytes MessageExecutor The MessageExecutor executes dispatched messages and message batches. This specification makes no ordering guarantees, because messages and message batches may travel non-sequentially through the transport layer. keywords: message; messageexecutor; type cache: eips-eip-5164.html plain text: eips-eip-5164.txt item: #582 of 3327 id: eips-eip-5169 author: eips title: eips-eip-5169 date: None words: 1495 flesch: 54 summary: A ‘TokenScript’ that allows users to interact with contract functions not normally provided by a wallet, eg ‘mint’ function. While this EIP does not dictate the format of the stored script, the script itself could contain pointers to multiple other scripts and data sources, allowing for advanced ways to expand token scripts, such as lazy loading. keywords: contract; function; scripturi; token cache: eips-eip-5169.html plain text: eips-eip-5169.txt item: #583 of 3327 id: eips-eip-5173 author: eips title: eips-eip-5173 date: None words: 4135 flesch: 47 summary: When an owner loses money during their holding period, they MUST NOT be obligated to share Future Rewards distributions, since there is no profit to share. However, he SHALL still receive a share of Future Rewards distributions from future generations of owners, if they are profitable. keywords: distribution; function; future; nft; owners; rewards; token; uint256 cache: eips-eip-5173.html plain text: eips-eip-5173.txt item: #584 of 3327 id: eips-eip-5185 author: eips title: eips-eip-5185 date: None words: 1634 flesch: 45 summary: [eval], properties: { eval: { type: string, description: The evaluation formula to transform the last JSON metadata using the engine above (can take arguments) } } } } } } } } } “NFT Metadata Updates JSON Schema” : { title: Metadata Updates JSON Schema, type: object, properties: { updates: { type: array, description: A list of updates to apply sequentially to calculate updated metadata, items: { $ref: #/$defs/update }, $defs: { update: { type: object, required: [tokenId, recipeKey], properties: { tokenId: { type: string, description: The tokenId for which the update recipe should apply }, recipeKey: { type: string, description: recipeKey to use to get the JSON transformation expression in current metadata }, args: { type: string, description: arguments to pass to the JSON transformation } } } } } } } Engines Only one engine is currently defined in this extension proposal. *”, updated metadata is calculated starting from original metadata and applying each update sequentially (all updates which are present in all the URIs emitted by the event MetadataUpdates for which tokenId matches). keywords: json; metadata; nft; updates cache: eips-eip-5185.html plain text: eips-eip-5185.txt item: #585 of 3327 id: eips-eip-5187 author: eips title: eips-eip-5187 date: None words: 1432 flesch: 53 summary: One is that NFTs with multiple usage rights allow NFT property owners to perform the safeRent function and rent out usage rights to multiple users at the same time. This emits when user rent NFT * - `id` The id of the current token * - `user` The address to rent the NFT usage rights * - `amount` The amount of usage rights * - `expire` The specified period of time to rent **/ event Rented(uint256 indexed id,address indexed user,uint256 amount,uint256 expire); / keywords: usage; user cache: eips-eip-5187.html plain text: eips-eip-5187.txt item: #586 of 3327 id: eips-eip-5189 author: eips title: eips-eip-5189 date: None words: 3165 flesch: 43 summary: Additionally, the specification is kept as simple as possible as enforcing a highly structured behavior and schema for smart contract wallet transactions may stagnate the adoption of more innovative types of wallets and the adoption of a shared standard among them. Instead of defining a strict structure for AA transactions, this proposal introduces the figure of endorser contracts. keywords: bundler; contract; dependencies; endorser; operation; readiness cache: eips-eip-5189.html plain text: eips-eip-5189.txt item: #587 of 3327 id: eips-eip-5192 author: eips title: eips-eip-5192 date: None words: 506 flesch: 51 summary: Available: https://eips.ethereum.org/EIPS/eip-5192. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. Citation Please cite this document as: Tim Daubenschütz (@TimDaub), Anders (@0xanders), ERC-5192: Minimal Soulbound NFTs, Ethereum Improvement Proposals, no. 5192, July 2022. keywords: soulbound; token cache: eips-eip-5192.html plain text: eips-eip-5192.txt item: #588 of 3327 id: eips-eip-5202 author: eips title: eips-eip-5202 date: None words: 1378 flesch: 53 summary: For this reason, it would be good to prefix blueprint contracts with a special preamble to prevent execution. The Ethereum Object Format (EOF) could provide another way of specifying blueprint contracts, by adding another section kind (3 - initcode). keywords: blueprint; contract; initcode; length cache: eips-eip-5202.html plain text: eips-eip-5202.txt item: #589 of 3327 id: eips-eip-5216 author: eips title: eips-eip-5216 date: None words: 766 flesch: 44 summary: Table of Contents Abstract Motivation Specification Interface implementation Rationale Backwards Compatibility Reference Implementation Security Considerations Copyright Abstract This ERC defines standard functions for granular approval of ERC-1155 tokens by both id and amount. Rationale The name “ERC-1155 Allowance Extension” was chosen because it is a succinct description of this ERC. keywords: erc-1155; tokens cache: eips-eip-5216.html plain text: eips-eip-5216.txt item: #590 of 3327 id: eips-eip-5218 author: eips title: eips-eip-5218 date: None words: 2377 flesch: 53 summary: Abstract Motivation Specification Rationale Backwards Compatibility Test Cases Reference Implementation Security Considerations Copyright Abstract The following standard defines an API for managing NFT licenses. In addition, the Token-Bound NFT License is specifically designed to work with this interface and provides a reference to the language of NFT licenses. keywords: function; identifier; license; nft cache: eips-eip-5218.html plain text: eips-eip-5218.txt item: #591 of 3327 id: eips-eip-5219 author: eips title: eips-eip-5219 date: None words: 636 flesch: 41 summary: Created 2022-07-10 Table of Contents Abstract Motivation Specification Name Resolution Separation of Concerns Contract Interface Note to Implementers Rationale Backwards Compatibility Security Considerations Copyright Abstract This EIP standardizes an interface to make resource requests to smart contracts and to receive HTTP-like responses. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: contract; interface cache: eips-eip-5219.html plain text: eips-eip-5219.txt item: #592 of 3327 id: eips-eip-5247 author: eips title: eips-eip-5247 date: None words: 746 flesch: 27 summary: Hence, we decide to decouple the voting interface and proposal interface. Such proposals include a series of information about function calls including the target contract address, ether value to be transmitted, gas limits and calldatas. keywords: proposal; uint256 cache: eips-eip-5247.html plain text: eips-eip-5247.txt item: #593 of 3327 id: eips-eip-5252 author: eips title: eips-eip-5252 date: None words: 2126 flesch: 53 summary: When an investor deposits a fund to Manager contract, the contract sends the fund to Finance contract account after separating fees for operation. The contract also stores parameters for Finance contract. keywords: account; contract; finance; governance; token cache: eips-eip-5252.html plain text: eips-eip-5252.txt item: #594 of 3327 id: eips-eip-5267 author: eips title: eips-eip-5267 date: None words: 1321 flesch: 46 summary: extensions: A list of EIP numbers, each of which MUST refer to an EIP that extends EIP-712 with new domain fields, along with a method to obtain the value for those fields, and potentially conditions for inclusion. Citation Please cite this document as: Francisco Giordano (@frangio), ERC-5267: Retrieval of EIP-712 domain, Ethereum Improvement Proposals, no. 5267, July 2022. keywords: domain; eip-712; fields cache: eips-eip-5267.html plain text: eips-eip-5267.txt item: #595 of 3327 id: eips-eip-5269 author: eips title: eips-eip-5269 date: None words: 1874 flesch: 35 summary: Here is the motivation for this ERC given ERC-165 already exists: Using ERC numbers improves human readability as well as make it easier to work with named contract such as ENS. Instead of using an ERC-165 identifier, we have seen an increasing interest to use ERC numbers as the way to identify or specify an ERC. keywords: caller; erc; minorercidentifier; number cache: eips-eip-5269.html plain text: eips-eip-5269.txt item: #596 of 3327 id: eips-eip-5283 author: eips title: eips-eip-5283 date: None words: 1105 flesch: 50 summary: Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. The benefit is that the precompile-based RPG does not write to storage, and therefore it enables contracts to be forward-compatible with all designs that provide fine-grained (i.e. cell level) parallelization for the multi-threaded execution of EVM transactions. keywords: contract; rpg; storage cache: eips-eip-5283.html plain text: eips-eip-5283.txt item: #597 of 3327 id: eips-eip-5289 author: eips title: eips-eip-5289 date: None words: 705 flesch: 47 summary: This EIP proposes a standard that allows smart contracts to be legally binding by providing IPFS links to legal documents and ensuring that the users of the smart contract have privity with the relevant legal documents. uint16 was chosen for the document ID as 65536 documents are likely sufficient for any use case, and the contract can always be re-deployed. keywords: document; ethereum cache: eips-eip-5289.html plain text: eips-eip-5289.txt item: #598 of 3327 id: eips-eip-5298 author: eips title: eips-eip-5298 date: None words: 642 flesch: 29 summary: ERC-5298: ENS Trust to hold NFTs under ENS name Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-5298: ENS Trust to hold NFTs under ENS name An interface for a smart contract acting as a trust that holds tokens by ENS name. Citation Please cite this document as: Zainan Victor Zhou (@xinbenlv), ERC-5298: ENS Trust to hold NFTs under ENS name [DRAFT], Ethereum Improvement Proposals, no. 5298, July 2022. keywords: ens; ethereum; function cache: eips-eip-5298.html plain text: eips-eip-5298.txt item: #599 of 3327 id: eips-eip-5313 author: eips title: eips-eip-5313 date: None words: 398 flesch: 36 summary: Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. @notice Get the address of the owner /// @return The address of the owner function owner() view external returns(address); } Rationale Key factors influencing the standard: Minimize the number of functions in the interface Backwards compatibility with existing contracts This standard can be (and has been) extended by other standards to add additional ownership functionality. keywords: contract cache: eips-eip-5313.html plain text: eips-eip-5313.txt item: #600 of 3327 id: eips-eip-5334 author: eips title: eips-eip-5334 date: None words: 1170 flesch: 58 summary: The new user of the NFT /// @param expires UNIX timestamp, The new user could use the NFT before expires /// @param level user level function setUser(uint256 tokenId, address user, uint64 expires, uint8 level) external; /// Furthermore, applications of this model (such as renting) often demand that user addresses have only temporary access to using the NFT. keywords: expires; nft; user cache: eips-eip-5334.html plain text: eips-eip-5334.txt item: #601 of 3327 id: eips-eip-5345 author: eips title: eips-eip-5345 date: None words: 1204 flesch: 45 summary: By this proposal, we would like to introduce the means to sign and send wallet transactions without the need for user participation. Specification To remedy the situation, we’d like to introduce new RPC methods for the ethereum JSON-RPC. keywords: data; transaction; user cache: eips-eip-5345.html plain text: eips-eip-5345.txt item: #602 of 3327 id: eips-eip-5375 author: eips title: eips-eip-5375 date: None words: 2038 flesch: 46 summary: Why repeat id, chainId and contractAddress? Why not implement a revocation system? Usability Improvements for Authors Limitations of Address-Based Consent Backwards Compatibility Security Considerations Attacks Deprecated Features Replay Attack Resistance Copyright Abstract This EIP standardizes a JSON format for storing off-chain information about NFT authors. ERC-5375: NFT Author Information and Consent Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: ERC ERC-5375: NFT Author Information and Consent An extension of EIP-721 for NFT authorship and author consent. keywords: address; author; consent; nft; type cache: eips-eip-5375.html plain text: eips-eip-5375.txt item: #603 of 3327 id: eips-eip-5380 author: eips title: eips-eip-5380 date: None words: 949 flesch: 48 summary: The user to grant the entitlement to /// @param contract The property to grant /// @param tokenId The tokenId to grant the properties of function entitle(address user, address contract, uint256 tokenId) external; /// @notice Get the maximum number of users that can receive this entitlement /// @param tokenId The tokenId to query function entitlementOf(address user, address contract, uint256 tokenId) external view returns (uint256 amt); } supportsInterface MUST return true when called with ERC5380Entitlement’s interface ID. Enumerable Extension This OPTIONAL Solidity interface is RECOMMENDED. keywords: interface; tokenid; user cache: eips-eip-5380.html plain text: eips-eip-5380.txt item: #604 of 3327 id: eips-eip-5409 author: eips title: eips-eip-5409 date: None words: 476 flesch: 46 summary: ERC-5409: EIP-1155 Non-Fungible Token extension Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-5409: EIP-1155 Non-Fungible Token extension Allow EIP-1155 to represent Non-Fungible Tokens (tokens who have a unique owner) Authors Ronan Sandford (@wighawag) Citation Please cite this document as: Ronan Sandford (@wighawag), ERC-5409: EIP-1155 Non-Fungible Token extension [DRAFT], Ethereum Improvement Proposals, no. 5409, July 2022. keywords: eip-1155; owner cache: eips-eip-5409.html plain text: eips-eip-5409.txt item: #605 of 3327 id: eips-eip-5437 author: eips title: eips-eip-5437 date: None words: 800 flesch: 4 summary: ERC-5437: Security Contact Interface Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-5437: Security Contact Interface An interface for security notice using asymmetric encryption Authors Zainan Zhou (@xinbenlv) Created 2022-08-09 Discussion Link https://ethereum-magicians.org/t/erc-interface-for-security-contract/10303 Requires EIP-165 Table of Contents Abstract Motivation Specification Rationale Backwards Compatibility Security Considerations Copyright Abstract An interface for security notice using asymmetric encryption. keywords: contact; memory; security; type cache: eips-eip-5437.html plain text: eips-eip-5437.txt item: #606 of 3327 id: eips-eip-5450 author: eips title: eips-eip-5450 date: None words: 1199 flesch: 49 summary: Instructions validation Moreover, it enables combining instruction validation and operand stack validation into single pass. keywords: code; instruction; stack cache: eips-eip-5450.html plain text: eips-eip-5450.txt item: #607 of 3327 id: eips-eip-5453 author: eips title: eips-eip-5453 date: None words: 1449 flesch: 24 summary: function forward( address _dest, uint256 _value, uint256 _gasLimit, bytes calldata _calldata, bytes calldata _extraData ) external onlyEndorsed( _computeFunctionParamHash( function forward(address _dest,uint256 _value,uint256 _gasLimit,bytes calldata _calldata), abi.encode(_dest, _value, _gasLimit, keccak256(_calldata)) ), _extraData ) { string memory errorMessage = Fail to call remote contract; (bool success, bytes memory returndata) Interfaces The interfaces and structure referenced here are as followed pragma solidity ^0.8.9; struct ValidityBound { bytes32 functionParamStructHash; uint256 validSince; uint256 validBy; uint256 nonce; } struct SingleEndorsementData { address endorserAddress; // 32 bytes sig; // dynamic = 65 } struct GeneralExtensionDataStruct { bytes32 erc5453MagicWord; uint256 erc5453Type; uint256 nonce; uint256 validSince; uint256 validBy; bytes endorsementPayload; } interface IERC5453EndorsementCore { function eip5453Nonce(address endorser) external view returns (uint256); function isEligibleEndorser(address endorser) external view returns (bool); } interface IERC5453EndorsementDigest { function computeValidityDigest( bytes32 _functionParamStructHash, uint256 _validSince, uint256 _validBy, uint256 _nonce ) external view returns (bytes32); function computeFunctionParamHash( string memory _functionName, bytes memory _functionParamPacked ) external view returns (bytes32); } interface IERC5453EndorsementDataTypeA { function computeExtensionDataTypeA( uint256 nonce, keywords: bytes; calldata; function; uint256 cache: eips-eip-5453.html plain text: eips-eip-5453.txt item: #608 of 3327 id: eips-eip-5478 author: eips title: eips-eip-5478 date: None words: 385 flesch: 36 summary: CREATE2COPY Opcode Reducing the gas cost of contract creation with existing code Authors Qi Zhou (@qizhou) Created 2022-08-17 Discussion Link https://ethereum-magicians.org/t/eip-5478-reducing-the-gas-cost-of-contract-creation-with-existing-code/10419 Requires EIP-1014, EIP-2929 Table of Contents Abstract Motivation Specification Parameters Rationale Security Considerations Copyright Abstract Adding a new opcode, CREATE2COPY, that is identical to CREATE2 but with potentially much lower gas cost by accepting an additional argument existing_contract_address that already stored the code of the new contract. Available: https://eips.ethereum.org/EIPS/eip-5478. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: code; contract cache: eips-eip-5478.html plain text: eips-eip-5478.txt item: #609 of 3327 id: eips-eip-5484 author: eips title: eips-eip-5484 date: None words: 821 flesch: 48 summary: In order to provide the flexibility in these scenarios, soulbound tokens must have an application-specific burn authorization and a way to distinguish themselves from regular EIP-721 tokens. ERC-5484: Consensual Soulbound Tokens Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: ERC ERC-5484: Consensual Soulbound Tokens Interface for special NFTs with immutable ownership and pre-determined immutable burn authorization Authors Buzz Cai (@buzzcai) Created 2022-08-17 Requires EIP-165, EIP-721 Table of Contents Abstract Motivation Specification Contract Interface Rationale Soulbound Token (SBTs) as an extension to EIP-721 Non-Transferable Burn Authorization Issued Event Key Rotations Backwards Compatibility Security Considerations Copyright Abstract This EIP defines an interface extending EIP-721 to create soulbound tokens. keywords: soulbound; token cache: eips-eip-5484.html plain text: eips-eip-5484.txt item: #610 of 3327 id: eips-eip-5485 author: eips title: eips-eip-5485 date: None words: 786 flesch: 37 summary: Motivation Today, smart contracts have no standard way to specify their legitimacy lineage, jurisdiction, or sovereignty relationship. The introduction of such a standard, supports better integration with today’s legal and regulative scenarios: it supports a regulative body to allow or deny interoperability with smart contracts. keywords: jurisdiction; legitimacy cache: eips-eip-5485.html plain text: eips-eip-5485.txt item: #611 of 3327 id: eips-eip-5489 author: eips title: eips-eip-5489 date: None words: 1006 flesch: 44 summary: The address which has slot authorization can manage the URL of that slot. This method will emit SlotAuthorizationRevoked event */ function revokeAuthorization(uint256 tokenId, address slotManagerAddr) external; / keywords: address; slotmanageraddr; tokenid cache: eips-eip-5489.html plain text: eips-eip-5489.txt item: #612 of 3327 id: eips-eip-5496 author: eips title: eips-eip-5496 date: None words: 1595 flesch: 43 summary: Rationale Shareable Privileges The number of privilege holders is limited by the number of NFTs if privileges are non-shareable. For example, a fashion store may give a discount for its own NFT holders; a DAO member NFT holder can vote for the proposal of how to use their treasury; a dApp may create an airdrop event to attract a certain group of people like some blue chip NFT holders to claim; the grocery store can issue its membership card on chain (as an NFT) and give certain privileges when the members shop at grocery stores, etc. keywords: nft; privilege; tokenid; user cache: eips-eip-5496.html plain text: eips-eip-5496.txt item: #613 of 3327 id: eips-eip-55 author: eips title: eips-eip-55 date: None words: 447 flesch: 23 summary: Rationale Benefits: Backwards compatible with many hex parsers that accept mixed case, allowing it to be easily introduced over time Keeps the length at 40 characters On average there will be 15 check bits per address, and the net probability that a randomly generated address if mistyped will accidentally pass a check is 0.0247%. Implementation In javascript: const createKeccakHash = require('keccak') function toChecksumAddress (address) { address = address.toLowerCase().replace('0x', ') var hash = createKeccakHash('keccak256').update(address).digest('hex') var ret = '0x' for (var i = 0; i < address.length; i++) { if (parseInt(hash[i], 16) > keywords: address cache: eips-eip-55.html plain text: eips-eip-55.txt item: #614 of 3327 id: eips-eip-5501 author: eips title: eips-eip-5501 date: None words: 2211 flesch: 56 summary: Applications can also provide different access and benefits to owner and user roles in their ecosystem. This standard also shares similarities to EIP-4907 considering user role and its expiry which means applications will be able to determine the user if either of the standards is used. keywords: address; nft; tokenid; user cache: eips-eip-5501.html plain text: eips-eip-5501.txt item: #615 of 3327 id: eips-eip-5505 author: eips title: eips-eip-5505 date: None words: 548 flesch: 45 summary: ERC-5505: EIP-1155 asset backed NFT extension Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-5505: EIP-1155 asset backed NFT extension Extends EIP-1155 to support crucial operations for asset-backed NFTs Authors liszechung (@liszechung) Citation Please cite this document as: liszechung (@liszechung), ERC-5505: EIP-1155 asset backed NFT extension [DRAFT], Ethereum Improvement Proposals, no. 5505, August 2022. keywords: asset; ethereum cache: eips-eip-5505.html plain text: eips-eip-5505.txt item: #616 of 3327 id: eips-eip-5507 author: eips title: eips-eip-5507 date: None words: 2140 flesch: 55 summary: The first block where the token cannot be refunded function refundDeadlineOf(uint256 tokenId) external view returns (uint256 block); } Optional ERC-1155 Batch Refund Extension // SPDX-License-Identifier: CC0-1.0; import ERC1155Refund.sol; /// @notice Batch Refundable ERC-1155 tokens /// @dev The ERC-165 identifier of this interface is `` contract ERC1155BatchRefund is ERC1155Refund { /// @notice Emitted when one or more tokens are batch refunded /// @dev Emitted by `refundBatch` /// The first block where token cannot be refunded function refundDeadlineOf(uint256 tokenId) external view returns (uint256 block); } Optional ERC-721 Batch Refund Extension // SPDX-License-Identifier: CC0-1.0; import ERC721Refund.sol; /// @notice Batch Refundable ERC-721 tokens /// @dev The ERC-165 identifier of this interface is `` contract ERC721BatchRefund is ERC721Refund { /// @notice Emitted keywords: @param; refund; tokenid cache: eips-eip-5507.html plain text: eips-eip-5507.txt item: #617 of 3327 id: eips-eip-5516 author: eips title: eips-eip-5516 date: None words: 1263 flesch: 59 summary: See EIP-1155 // SPDX-License-Identifier: CC0-1.0 pragma solidity ^0.8.4; /** @title Soulbound, Multi-Token standard. We believe that Soulbound Tokens serve as a specialized subset of existing EIP-1155 tokens. keywords: eip-1155; token cache: eips-eip-5516.html plain text: eips-eip-5516.txt item: #618 of 3327 id: eips-eip-5521 author: eips title: eips-eip-5521 date: None words: 2389 flesch: 33 summary: @param `_tokenIds` of rNFTs associated with the contract address `_address` being referred by the rNFT with `tokenId`. @requirement /// - `_address` **MUST NOT** be the same as `address(this)` where `this` is executed by an external contract where `TargetContract` interface is implemented. keywords: address; memory; rnft; tokenid; uint256 cache: eips-eip-5521.html plain text: eips-eip-5521.txt item: #619 of 3327 id: eips-eip-5528 author: eips title: eips-eip-5528 date: None words: 1193 flesch: 42 summary: balances[to] += amount; } function transfer(address to, uint256 amount) public returns (bool) { address owner = msg.sender; _transfer(owner, to, amount); return true; } function escrowFund(address _to, uint256 _value) public returns (bool){ bool res = IERC5528(to).escrowFund(msg.sender, amount); require(res, Fund Failed); _transfer(msg.sender, to, amount); return true; } function escrowRefund(address _from, uint256 _value) public returns (bool){ bool res = IERC5528(_from).escrowRefund(msg.sender, _value); require(res, Refund Failed); _transfer(_from, msg.sender, _value); return true; } } contract EscrowContract is IERC5528 { enum State { Inited, Running, Success, Closed } struct BalanceData { address addr; uint256 amount; } address _addrSeller; address _addrBuyer; BalanceData _fundSeller; BalanceData _fundBuyer; EscrowStatus _status; constructor(address sellerContract, address buyerContract){ _addrSeller = sellerContract; _addrBuyer = buyerContract; _status = State. function escrowFund(address _to, uint256 _value) public returns (bool) escrowRefund Refunds _value amount of tokens from address _from. keywords: contract; escrow cache: eips-eip-5528.html plain text: eips-eip-5528.txt item: #620 of 3327 id: eips-eip-5539 author: eips title: eips-eip-5539 date: None words: 1834 flesch: 31 summary: function isRevoked(address namespace, bytes32 list, bytes32 key) public view returns (bool); changeStatus MUST implement a function to change the revocation status of a particular revocation key in a namespace’s revocation list function changeStatus(bool revoked, address namespace, bytes32 revocationList, bytes32 revocationKey) public; changeStatusSigned (see Meta Transactions) function changeStatusSigned(bool revoked, address namespace, bytes32 revocationList, bytes32 revocationKey, address signer, bytes calldata signature) public; changeStatusDelegated OPTIONAL implements a function to change the revocation status of a particular revocation key in a namespace’s revocation list by a revocation list’s delegate. keywords: address; bytes32; namespace; revocation cache: eips-eip-5539.html plain text: eips-eip-5539.txt item: #621 of 3327 id: eips-eip-5553 author: eips title: eips-eip-5553 date: None words: 1726 flesch: 31 summary: ERC-5553: Representing IP and its Royalty Structure Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-5553: Representing IP and its Royalty Structure A way of representing intellectual property and its respective royalty structure on chain Authors Roy Osherove (@royosherove) Citation Please cite this document as: Roy Osherove (@royosherove), ERC-5553: Representing IP and its Royalty Structure [DRAFT], Ethereum Improvement Proposals, no. 5553, August 2022. keywords: function; metadata; royalty; string cache: eips-eip-5553.html plain text: eips-eip-5553.txt item: #622 of 3327 id: eips-eip-5554 author: eips title: eips-eip-5554 date: None words: 2332 flesch: 37 summary: @return address The address of the derivative collection function getDerivativeCollection(uint256 _derivativeId) external view returns (address); } Token based Attribution/ Remix On chain derivative works and reproductions Reproductions and derivative works are tracked in the contract. We aim to create a new set of licenses with modular terms and conditions—à la Creative Commons—in order to enable artists to increase the value of their NFT by associating additional rights to them (e.g. the right to create derivative works, or to allow for the commercial usage of the underlying works). keywords: derivative; token; uint256; work cache: eips-eip-5554.html plain text: eips-eip-5554.txt item: #623 of 3327 id: eips-eip-5559 author: eips title: eips-eip-5559 date: None words: 4519 flesch: 54 summary: These handshakes are outlined in the sections below: StorageHandledByL2 StorageHandledByOffChainDatabase In some cases, the mutation may be deferred multiple times Storage Deferred Twice L1 > L2 > Off-Chain Data Stored in an L1 ┌──────┐ ┌───────────┐ │Client│ │L1 Contract│ └──┬───┘ └─────┬─────┘ │ │ │ somefunc(...) │ ├─────────────────────────►│ │ │ │ response │ │◄─────────────────────────┤ │ │ Data Stored in an L2 & an Off-Chain Database ┌──────┐ ┌───────────┐ ┌─────────────┐ ┌────────────────────┐ │Client│ │L1 Contract│ │ L2 Contract │ │ Off-Chain Database │ └──┬───┘ └─────┬─────┘ └──────┬──────┘ └──────────┬─────────┘ │ │ │ │ │ somefunc(...) │ │ │ ├────────────────────────────────────────────────────►│ │ │ │ │ │ │ │ revert StorageHandledByL2(chainId, contractAddress) │ │ │ │◄────────────────────────────────────────────────────┤ │ │ │ │ │ │ │ Execute Tx keywords: ─ ─; ─ ┐; ─ ┘; ┌ ─; ├ ─ cache: eips-eip-5559.html plain text: eips-eip-5559.txt item: #624 of 3327 id: eips-eip-5560 author: eips title: eips-eip-5560 date: None words: 610 flesch: 30 summary: Available: https://eips.ethereum.org/EIPS/eip-5560. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. event Redeem(address indexed from, uint256 indexed tokenId); /// @notice Returns the redeem status of a token /// @param tokenId Identifier of the token. function isRedeemable(uint256 _tokenId) external view returns (bool); /// @notice Redeeem a token /// @param tokenId keywords: function; redeem cache: eips-eip-5560.html plain text: eips-eip-5560.txt item: #625 of 3327 id: eips-eip-5564 author: eips title: eips-eip-5564 date: None words: 2854 flesch: 53 summary: Table of Contents Abstract Motivation Specification Stealth meta-address format Initial Implementation of SECP256k1 with View Tags Parsing considerations Rationale Backwards Compatibility Reference Implementation Security Considerations DoS Countermeasures Recipients’ transaction costs Copyright Abstract This specification establishes a standardized method for interacting with stealth addresses, which allow senders of transactions or transfers to non-interactively generate private accounts exclusively accessible by their recipients. This provides users with a centralized location for identifying stealth meta-addresses associated with other individuals while simultaneously enabling recipients to express their openness to engage via stealth addresses. keywords: address; bytes; key; recipient; stealth cache: eips-eip-5564.html plain text: eips-eip-5564.txt item: #626 of 3327 id: eips-eip-5568 author: eips title: eips-eip-5568 date: None words: 814 flesch: 52 summary: Table of Contents Abstract Motivation Specification Action Detection Custom Revert Reason Responding to a Revert Rationale Backwards Compatibility Human-Readable Revert Messages ERC-3668 Security Considerations Revert Reason Collisions Copyright Abstract This ERC introduces a minimalistic machine-readable (binary) format to signal to wallets that an action needs to be taken by the user using a well-known function and revert reason. Traditionally, this has been done by hard-coding the logic into the frontend, but this ERC allows the smart contract itself to request the action. keywords: erc; instruction_id cache: eips-eip-5568.html plain text: eips-eip-5568.txt item: #627 of 3327 id: eips-eip-5570 author: eips title: eips-eip-5570 date: None words: 1451 flesch: 37 summary: Digital receipts have never gained traction dispite the fact that point of sales systems are already digital and the customers often want this information in their own digital systems. Digital receipts are relatively simple and can be specified with a schema that can be parsed into JSON or other structured formats. keywords: description; receipt; title; type cache: eips-eip-5570.html plain text: eips-eip-5570.txt item: #628 of 3327 id: eips-eip-5573 author: eips title: eips-eip-5573 date: None words: 2355 flesch: 37 summary: Note, this approach is a similar mechanism to combining OpenID Connect (SIWE auth) and OAuth2 (SIWE ReCap) where SIWE ReCap implements capabilities-based authorization on top of the authentication provided by SIWE. Overview This specification defines the following: ReCap SIWE Extension ReCap Capability ReCap URI Scheme ReCap Details Object Schema ReCap Translation Algorithm ReCap Verification ReCap SIWE Extension A ReCap is an ERC-4361 message following a specific format that allows an Ethereum account to delegate a set of ReCap Capabilities to a Relying Party through informed consent. keywords: object; recap; siwe; statement; uri cache: eips-eip-5573.html plain text: eips-eip-5573.txt item: #629 of 3327 id: eips-eip-5585 author: eips title: eips-eip-5585 date: None words: 1568 flesch: 53 summary: The NFT to get the user expires for /// @param user The user who has been authorized /// @return The authorization expired time function getExpires(uint256 tokenId, address user) external view returns(uint); /// @notice Get the rights of the specified NFT and user /// @dev The NFT on which the authorization based /// @param user The user whose authorization will be cleared function resetUser(uint256 tokenId, address user) external; /// @notice Emitted when the user of a NFT is changed or the authorization expires time is updated /// param tokenId keywords: address; nft; user cache: eips-eip-5585.html plain text: eips-eip-5585.txt item: #630 of 3327 id: eips-eip-5593 author: eips title: eips-eip-5593 date: None words: 1532 flesch: 46 summary: EIP-5593: Restrict Ethereum Provider API Injection Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Interface EIP-5593: Restrict Ethereum Provider API Injection Wallet guidance for restricting Ethereum Provider API access to secure contexts for improved privacy and security for wallet users. Since the Ethereum Provider APIs allow dApp websites to request access to sensitive user data and to request use of user funds, new Ethereum Provider APIs generally should align to the security considerations defined by W3C’s Secure Context specification in order to better protect the users data and users funds managed via the web. keywords: ethereum; iframe; level; provider cache: eips-eip-5593.html plain text: eips-eip-5593.txt item: #631 of 3327 id: eips-eip-5604 author: eips title: eips-eip-5604 date: None words: 722 flesch: 55 summary: ERC-5604: NFT Lien Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: ERC ERC-5604: NFT Lien Extend ERC-721 to support putting liens on NFT Authors Zainan Victor Zhou (@xinbenlv), Allen Zhou , Alex Qin  Created 2022-09-05 Discussion Link https://ethereum-magicians.org/t/creating-a-new-erc-proposal-for-nft-lien/10683 Requires EIP-165, EIP-721 Table of Contents Abstract Motivation Specification Rationale Backwards Compatibility Security Considerations Copyright Abstract This ERC introduces NFT liens, a form of security interest over an item of property to secure the recovery of liability or performance of some other obligation. An example use case for an NFT lien is for a deed. keywords: holder; lien cache: eips-eip-5604.html plain text: eips-eip-5604.txt item: #632 of 3327 id: eips-eip-5606 author: eips title: eips-eip-5606 date: None words: 1174 flesch: 48 summary: ** * @dev Interface of the Multiverse NFT standard as defined in the EIP. ** * @dev Initialises a new bundle, mints a Multiverse NFT and assigns it to msg.sender * Returns the token ID of a new Multiverse NFT * Note - When a new Multiverse NFT is initialised, it is empty; it does not contain any delegate NFTs */ function initBundle(DelegateData[] memory delegateData) external; } keywords: multiverse; nft; nfts cache: eips-eip-5606.html plain text: eips-eip-5606.txt item: #633 of 3327 id: eips-eip-5625 author: eips title: eips-eip-5625 date: None words: 1061 flesch: 39 summary: ERC-5625: NFT Metadata JSON Schema dStorage Extension Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-5625: NFT Metadata JSON Schema dStorage Extension Add a dStorage property to non-fungible tokens (NFTs) metadata JSON schema to provide decentralized storage information of NFT assets Authors Gavin Fu (@gavfu) Created 2022-09-08 Discussion Link https://ethereum-magicians.org/t/eip-5625-nft-metadata-json-schema-dstorage-extension/10754 Requires EIP-721, EIP-1155 Table of Contents Abstract Motivation Specification Rationale Choice between Interface and JSON Schema Extension Security Considerations Copyright Abstract This EIP extends the NFT metadata JSON schema defined in EIP-721 and EIP-1155, adding a dStorage key that provides information about how the NFT data is stored. Citation Please cite this document as: Gavin Fu (@gavfu), ERC-5625: NFT Metadata JSON Schema dStorage Extension keywords: description; string; type cache: eips-eip-5625.html plain text: eips-eip-5625.txt item: #634 of 3327 id: eips-eip-5630 author: eips title: eips-eip-5630 date: None words: 1959 flesch: 54 summary: It is unlikely that this will be an issue, since encryption keys need be newly retrieved only upon the time of encryption; on the other hand, new ciphertexts will be generated using our new approach. Authors Firn Protocol (@firnprotocol), Fried L. Trout, Weiji Guo (@weijiguo) Created 2022-09-07 Discussion Link https://ethereum-magicians.org/t/eip-5630-encryption-and-decryption/10761 Table of Contents Abstract Motivation Specification Encrypting to a smart contract Rationale Backwards Compatibility Test Cases Security Considerations Copyright Abstract This EIP proposes a new way to encrypt and decrypt using Ethereum keys. keywords: curve; ecies; encryption; ethereum; key cache: eips-eip-5630.html plain text: eips-eip-5630.txt item: #635 of 3327 id: eips-eip-5633 author: eips title: eips-eip-5633 date: None words: 542 flesch: 53 summary: ERC-5633: Composable Soulbound NFT, EIP-1155 Extension Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-5633: Composable Soulbound NFT, EIP-1155 Extension Add composable soulbound property to EIP-1155 tokens Authors HonorLabs (@honorworldio) For example, the amulate Necklace of Calisea is of soulbound property, but another low level amulate is not. keywords: eip-1155; soulbound cache: eips-eip-5633.html plain text: eips-eip-5633.txt item: #636 of 3327 id: eips-eip-5635 author: eips title: eips-eip-5635 date: None words: 1300 flesch: 29 summary: ERC-5635: NFT Licensing Agreements Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-5635: NFT Licensing Agreements An oracle for retrieving NFT licensing agreements Authors Timi (@0xTimi), 0xTriple7 (@ysqi) function licensingInfo( address _dNFT, uint256 _dNFT_Id, address _oNFT, uint256 _oNFT_Id ) external view returns ( bool _licensed, address _licensor, uint64 _timeOfSignature, uint64 _expiryTime, LicensingAgreementType _type, string _licenseName, string _licenseUri // ); function royaltyRate( address _dNFT, uint256 _dNFT_Id, address _oNFT, uint256 _oNFT_Id ) external view returns ( address beneficiary, uint256 rate // keywords: address; licensing; onft; uint256 cache: eips-eip-5635.html plain text: eips-eip-5635.txt item: #637 of 3327 id: eips-eip-5639 author: eips title: eips-eip-5639 date: None words: 2279 flesch: 43 summary: A delegate can act on a token if they have a token level delegation, contract level delegation (for that token’s contract) or vault level delegation. A delegate can act on a contract if they have contract level delegation or vault level delegation. keywords: address; contract; delegate; vault; wallet cache: eips-eip-5639.html plain text: eips-eip-5639.txt item: #638 of 3327 id: eips-eip-5643 author: eips title: eips-eip-5643 date: None words: 1212 flesch: 26 summary: Easy Integration Because this standard is fully EIP-721 compliant, existing protocols will be able to facilitate the transfer of subscription NFTs out of the box. With a common standard for subscriptions, it will be easy for a single application to determine the number of subscriptions a user has, see when they expire, and renew/cancel them as requested. keywords: function; nft; subscription; tokenid cache: eips-eip-5643.html plain text: eips-eip-5643.txt item: #639 of 3327 id: eips-eip-5646 author: eips title: eips-eip-5646 date: None words: 604 flesch: 42 summary: Specification The key words “MUST”, “MUST NOT”, “SHOULD”, “SHOULD NOT”, and “MAY” in this document are to be interpreted as described in RFC 2119. pragma solidity ^0.8.0; interface ERC5646 is ERC165 { /// @notice Function to return current token state fingerprint. /// @return Current token state fingerprint. keywords: state; token cache: eips-eip-5646.html plain text: eips-eip-5646.txt item: #640 of 3327 id: eips-eip-5656 author: eips title: eips-eip-5656 date: None words: 991 flesch: 55 summary: This was recognised and alleviated early on with the introduction of the “identity” precompile, which accomplishes memory copying by the use of CALL’s input and output memory offsets. Memory copying is used by languages like Solidity and Vyper, where we expect this improvement to provide efficient means of building data structures, including efficient sliced access and copies of memory objects. keywords: copying; gas; memory cache: eips-eip-5656.html plain text: eips-eip-5656.txt item: #641 of 3327 id: eips-eip-5679 author: eips title: eips-eip-5679 date: None words: 864 flesch: 51 summary: The EIP-165 identifier of this interface is 0xd0017968 interface IERC5679Ext20 { function mint(address _to, uint256 _amount, bytes calldata _data) external; function burn(address _from, uint256 _amount, bytes calldata _data) external; } Any contract complying with EIP-721 when extended with this EIP, MUST implement the following interface: // The EIP-165 identifier of this interface is 0xf4cedd5a interface IERC5679Ext1155 { function safeMint(address _to, uint256 _id, uint256 _amount, bytes calldata _data) external; function safeMintBatch(address to, uint256[] calldata ids, uint256[] calldata amounts, bytes calldata data) external; function burn(address _from, uint256 _id, uint256 _amount, bytes[] calldata _data) external; function burnBatch(address _from, uint256[] calldata ids, uint256[] calldata amounts, bytes calldata _data) external; } keywords: calldata; token cache: eips-eip-5679.html plain text: eips-eip-5679.txt item: #642 of 3327 id: eips-eip-5700 author: eips title: eips-eip-5700 date: None words: 2655 flesch: 70 summary: The identifier of the unbinding token. function unbind( address from, address to, address bindAddress, uint256 bindId, uint256 tokenId ) external; /// @notice Gets the NFT address and identifier token `tokenId` is bound to. The number of tokens binding to the NFT. function bind( address from, address bindAddress, uint256 bindId, uint256 tokenId, uint256 amount ) external; /// @notice Binds `amounts` tokens of `tokenIds` to NFT `bindId` at address `bindAddress`. /// @dev The function MUST throw unless `msg.sender` is an approved operator /// for `from`. keywords: @param; address; nft cache: eips-eip-5700.html plain text: eips-eip-5700.txt item: #643 of 3327 id: eips-eip-5719 author: eips title: eips-eip-5719 date: None words: 726 flesch: 42 summary: ERC-5719: Signature replacement interface Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-5719: Signature replacement interface Non-interactive replacing of smart contract wallet signatures that became stale due to configuration changes. In contrast to EOA signatures, EIP-1271 signatures are not necessarily idempotent; they can become invalid at any point in time. keywords: signature; wallet cache: eips-eip-5719.html plain text: eips-eip-5719.txt item: #644 of 3327 id: eips-eip-5725 author: eips title: eips-eip-5725 date: None words: 2520 flesch: 58 summary: Citation Please cite this document as: Apeguru (@Apegurus), Marco De Vries , Mario , DeFiFoFum (@DeFiFoFum), Elliott Green (@elliott-green), ERC-5725: Transferable Vesting NFT, Ethereum Improvement Proposals, no. 5725, September 2022. Transferable Vesting NFT Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: ERC ERC-5725: Transferable Vesting NFT An interface for transferable vesting NFTs which release underlying tokens over time. keywords: @param; nft; tokenid; tokens; vesting cache: eips-eip-5725.html plain text: eips-eip-5725.txt item: #645 of 3327 id: eips-eip-5727 author: eips title: eips-eip-5727 date: None words: 2689 flesch: 57 summary: Authors Austin Zhu (@AustinZhu), Terry Chen  Created 2022-09-28 Discussion Link https://ethereum-magicians.org/t/eip-5727-semi-fungible-soulbound-token/11086 Requires EIP-165, EIP-712, EIP-721, EIP-3525, EIP-4906, EIP-5192, EIP-5484 Table of Contents Abstract Motivation Specification Core Extensions Rationale Token storage model Recovery mechanism Backwards Compatibility Test Cases Reference Implementation Security Considerations Copyright Abstract An interface for soulbound tokens (SBT), which are non-transferable tokens representing a person’s identity, credentials, affiliations, and reputation. Secondly, unlike ERC-1155, in which each unit of fungible tokens is exactly the same, our interface can help differentiate between similar tokens. keywords: @param; owner; slot; token; tokenid cache: eips-eip-5727.html plain text: eips-eip-5727.txt item: #646 of 3327 id: eips-eip-5732 author: eips title: eips-eip-5732 date: None words: 1076 flesch: 36 summary: A compliant contract that implements the IERC_COMMIT_GENERAL interface MUST accept commit(_commitment) as equivalent to commitFrom(msg.sender, _commitment, [/*empty array*/]). The timePoint return value of commitFrom is RECOMMENDED to use block.timestamp or block.number or a number that indicates the ordering of different commitments. keywords: commit; interface; reveal cache: eips-eip-5732.html plain text: eips-eip-5732.txt item: #647 of 3327 id: eips-eip-5744 author: eips title: eips-eip-5744 date: None words: 766 flesch: 54 summary: This method returns the balance of matured tokens for a given address: function balanceOfMatured(address user) external view returns (uint256); An additional method called getMints MUST be added, which returns an array of all mint metadata for a given address: Similarly, vesting use cases may want to enforce non-transferrable tokens until maturity, whereas lending receipt tokens with a minimum deposit duration may want to support transfers at all times. keywords: fungible; tokens cache: eips-eip-5744.html plain text: eips-eip-5744.txt item: #648 of 3327 id: eips-eip-5749 author: eips title: eips-eip-5749 date: None words: 873 flesch: 39 summary: This will simpify the UX and remove race conditions between wallet providers in case multiple wallets are installed. With new entrants crowded out, legacy wallet providers are put under little pressure to innovate. keywords: ethereum; wallet; window.evmproviders cache: eips-eip-5749.html plain text: eips-eip-5749.txt item: #649 of 3327 id: eips-eip-5750 author: eips title: eips-eip-5750 date: None words: 1271 flesch: 39 summary: Backwards Compatibility Many existing EIPs already have compliant methods as part of their specification. ERC-5750: General Extensibility for Method Behaviors Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: ERC ERC-5750: General Extensibility for Method Behaviors Designating last param of dynamically sized bytes to be used for behavior extensions of methods. keywords: bytes; data; method cache: eips-eip-5750.html plain text: eips-eip-5750.txt item: #650 of 3327 id: eips-eip-5753 author: eips title: eips-eip-5753 date: None words: 1925 flesch: 57 summary: Buyer gets locked NFT and immediately starts using it. Metaverse ready Locking NFT tickets can be useful during huge Metaverse events. keywords: nft; token; unlocker cache: eips-eip-5753.html plain text: eips-eip-5753.txt item: #651 of 3327 id: eips-eip-5757 author: eips title: eips-eip-5757 date: None words: 535 flesch: 43 summary: Permissible origins MUST NOT charge a fee for accessing resources. Created 2022-09-30 Requires EIP-1 Table of Contents Abstract Specification Definitions Requirements for Origins Origin Removal Origin Approval Rationale Unique Identifiers Availability Free Access Copyright Abstract Ethereum improvement proposals (EIPs) occasionally link to resources external to this repository. keywords: ethereum; origin cache: eips-eip-5757.html plain text: eips-eip-5757.txt item: #652 of 3327 id: eips-eip-5773 author: eips title: eips-eip-5773 date: None words: 3987 flesch: 52 summary: * @param tokenId ID of the token to set the priorities for * @param priorities An array of priorities of active assets. This differs from transfer approvals, as approvals are not cleared when the approved party accepts or * rejects an asset, or sets asset priorities. keywords: @dev; @param; array; asset; assetid; token; tokenid cache: eips-eip-5773.html plain text: eips-eip-5773.txt item: #653 of 3327 id: eips-eip-5791 author: eips title: eips-eip-5791 date: None words: 1518 flesch: 46 summary: Out of Scope The following are some peripheral problems that are intentionally not within the scope of this EIP: trusting that a specific NFT collection’s chip addresses actually map to physical chips embedded in items, instead of arbitrary EOAs ensuring that the chip does not deterioriate or get damaged ensuring that the chip stays attached to the physical item etc. This lets downstream indexers know which chip addresses are mapped to which tokens for the NFT collection. keywords: chip; physical; signature; token cache: eips-eip-5791.html plain text: eips-eip-5791.txt item: #654 of 3327 id: eips-eip-5792 author: eips title: eips-eip-5792 date: None words: 1853 flesch: 43 summary: Dapps may use this more abstract interface to support different kinds of wallets without additional effort, as well as provide a better UX for sending bundles of function calls ( e.g. EIP-20 #approve followed by a contract call). MAY reject the request if one or more calls in the bundle is expected to fail, when simulated sequentially wallet_sendFunctionCallBundle OpenRPC Specification - name: wallet_sendFunctionCallBundle summary: Sends a bundle of function calls from the user wallet params: - name: Function calls required: true schema: type: object title: Send function call bundle request required: - chainId - from - calls properties: chainId: title: chainId description: Chain ID that these calls should be sent on $ref: '#/components/schemas/uint' from: title: from address description: The address from which the function calls should be sent $ref: '#/components/schemas/address' calls: title: calls to make description: The calls that the wallet should make from the user's address type: array minItems: 1 items: title: function call description: A single function call type: object required: - gas - data to: title: to address description: The address that is being called $ref: '#/components/schemas/address' gas: title: gas limit description: The gas limit for this particular call $ref: '#/components/schemas/uint' value: title: value description: How much value to send with the call $ref: '#/components/schemas/uint' data: title: data description: The data to send with the function call $ref: '#/components/schemas/bytes' result: name: Bundle identifier schema: type: string maxLength: 66 wallet_sendFunctionCallBundle Example Parameters [ { chainId: 1, from: 0xd46e8dd67c5d32be8058bb8eb970870f07244567, calls: [ { to: 0xd46e8dd67c5d32be8058bb8eb970870f07244567, gas: 0x76c0, value: 0x9184e72a, data: 0xd46e8dd67c5d32be8d46e8dd67c5d32be8058bb8eb970870f072445675058bb8eb970870f072445675 }, { to: 0xd46e8dd67c5d32be8058bb8eb970870f07244567, gas: 0xdefa, value: 0x182183, data: 0xfbadbaf01 } ] } ] wallet_sendFunctionCallBundle Example Return Value The identifier may be the hash of the call bundle, e.g.: 0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331 The identifier may be a numeric identifier represented as a hex string, e.g.: 0x01 The identifier may be a base64 encoded string: aGVsbG8gd29ybGQ= wallet_getBundleStatus Returns the status of a bundle that was sent via wallet_sendFunctionCallBundle. keywords: calls; transaction; wallet cache: eips-eip-5792.html plain text: eips-eip-5792.txt item: #655 of 3327 id: eips-eip-5793 author: eips title: eips-eip-5793 date: None words: 555 flesch: 50 summary: The added metadata fields will also enable future - upgradeless - protocol tweaks to prevent certain transaction type (e.g. blob transactions) or certain transaction sizes (e.g. 128KB+) from being blindly broadcast to many peers. Rationale This change will make the eth protocol future-proof for new transaction types that might not be relevant for all nodes. keywords: transaction cache: eips-eip-5793.html plain text: eips-eip-5793.txt item: #656 of 3327 id: eips-eip-5805 author: eips title: eips-eip-5805 date: None words: 2641 flesch: 48 summary: Among these communities, some represent voting power using transferable tokens (ERC-20, ERC-721, other). event inputs: - name: delegator indexed: true type: address - name: fromDelegate indexed: true type: address - name: toDelegate indexed: true type: address DelegateVotesChanged delegate available voting power changes from previousBalance to newBalance. keywords: delegate; function; power; type; uint256; voting cache: eips-eip-5805.html plain text: eips-eip-5805.txt item: #657 of 3327 id: eips-eip-5806 author: eips title: eips-eip-5806 date: None words: 1085 flesch: 45 summary: EIP-5806: Delegate transaction Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: Core EIP-5806: Delegate transaction Adds a new transaction type that allows a EOAs to execute arbitrary code through delegation Authors Hadrien Croubois (@Amxx) Because an EOA may perform delegate transactions to multiple contracts in its lifetime, there are risks associated with the storage under the EOA. keywords: delegate; eoa; transaction cache: eips-eip-5806.html plain text: eips-eip-5806.txt item: #658 of 3327 id: eips-eip-5827 author: eips title: eips-eip-5827 date: None words: 1335 flesch: 39 summary: This presents a security risk as malicious DApps can drain users’ accounts up to the allowance granted, and users may not be aware of the implications of granting allowances. ** * @notice Returns approved max amount and recovery rate of allowance granted to `_spender` * @notice by `_owner`. keywords: @param; allowance; spender cache: eips-eip-5827.html plain text: eips-eip-5827.txt item: #659 of 3327 id: eips-eip-5850 author: eips title: eips-eip-5850 date: None words: 739 flesch: 46 summary: ERC-5850: Complex Numbers stored in `bytes32` types Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-5850: Complex Numbers stored in `bytes32` types Store real and imaginary parts of complex numbers in the least significant and most significant 16 bytes respectively of a `bytes32` type. Authors Paul Edge (@genkifs) Created 2022-10-29 Discussion Link https://ethereum-magicians.org/t/eip-5850-store-real-and-imaginary-parts-of-complex-numbers-in-the-least-significant-and-most-significant-16-bytes-respectively-of-a-bytes32-type/11532 Table of Contents Abstract Motivation Specification Rationale Backwards Compatibility Security Considerations Copyright Abstract This EIP proposes a natural way for complex numbers to be stored in and retrieved from the bytes32 data-type. keywords: bytes32; complex cache: eips-eip-5850.html plain text: eips-eip-5850.txt item: #660 of 3327 id: eips-eip-5851 author: eips title: eips-eip-5851 date: None words: 2095 flesch: 50 summary: Claims structure consist of the conditions and value that holder claims to associate and verifier has to validate them. For e.g if the DeFI provider (using the modifiers to validate the ownership of required SBT by owner) wants the admin to change the logic of verification or remove certain claim structure, the previous holders of the certificates will be affected by these changes. keywords: address; claim; identity; sbt; sbtid cache: eips-eip-5851.html plain text: eips-eip-5851.txt item: #661 of 3327 id: eips-eip-5883 author: eips title: eips-eip-5883 date: None words: 758 flesch: 54 summary: Neighbour->SmartContract: Approve Transfer alt Threshold amount of approvers reached alt Cumulative Score of approvers above threshold SmartContract->NewAssetOwner: Transfer asset (e.g. identity token) end end SmartContract->Neighbour: ERC-5883: Token Transfer by Social Recovery Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-5883: Token Transfer by Social Recovery On-Chain Social Recovery taking users' reputation into account & using a nearest-neighbour approach. keywords: token; transfer cache: eips-eip-5883.html plain text: eips-eip-5883.txt item: #662 of 3327 id: eips-eip-5902 author: eips title: eips-eip-5902 date: None words: 5183 flesch: 54 summary: With this approach, subscribers do not need their own dedicated off-chain processes for monitoring and responding to contract events. Both the publisher and subscriber contracts are registered in a central registry smart contract that relayers can use to discover hooks. keywords: @param; contract; event; function; hook; hook event; publisher; subscriber cache: eips-eip-5902.html plain text: eips-eip-5902.txt item: #663 of 3327 id: eips-eip-5920 author: eips title: eips-eip-5920 date: None words: 623 flesch: 49 summary: https://eips.ethereum.org/EIPS/eip-5920. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. Citation Please cite this document as: Gavin John (@Pandapip1), Zainan Victor Zhou (@xinbenlv), EIP-5920: PAY opcode [DRAFT], Ethereum Improvement Proposals, no. 5920, March 2022. keywords: address; opcode cache: eips-eip-5920.html plain text: eips-eip-5920.txt item: #664 of 3327 id: eips-eip-5982 author: eips title: eips-eip-5982 date: None words: 644 flesch: 34 summary: Interfaces of reference is described as followed: interface IERC_ACL_CORE { function hasRole(bytes32 role, address account) external view returns (bool); function grantRole(bytes32 role, address account) external; function revokeRole(bytes32 role, address account) external; } interface IERC_ACL_GENERAL { event RoleGranted(address indexed grantor, bytes32 indexed role, address indexed grantee, bytes _data); event RoleRevoked(address indexed revoker, bytes32 indexed role, address indexed revokee, bytes _data); event RoleCreated(address indexed roleGrantor, bytes32 role, bytes32 adminOfRole, string name, string desc, string uri, bytes32 calldata _data); event RoleDestroyed(address indexed roleDestroyer, bytes32 role, bytes32 calldata _data); event RolePowerSet(address indexed rolePowerSetter, bytes32 role, bytes4 methods, bytes calldata _data); function grantRole(bytes32 role, address account, bytes calldata _data) external; function revokeRole(bytes32 role, address account, bytes calldata _data) external; function createRole(bytes32 role, bytes32 adminOfRole, string name, string desc, string uri, bytes32 calldata _data) external; function destroyRole(bytes32 role, bytes32 calldata _data) external; function setRolePower(bytes32 role, bytes4 methods, bytes calldata _data) view external returns(bool); function hasRole(bytes32 role, address account, bytes calldata _data) external view returns (bool); function canGrantRole(bytes32 grantor, bytes32 grantee, bytes calldata _data) view external returns(bool); function canRevokeRole(bytes32 revoker, bytes32 revokee, address account, bytes calldata _data) view external returns(bool); function canExecute(bytes32 executor, bytes4 methods, bytes32 calldata payload, bytes calldata _data) view external returns(bool); } interface IERC_ACL_METADATA { function roleName(bytes32) external view returns(string); function roleDescription(bytes32) external view returns(string); function roleURI(bytes32) external view returns(string); } Compliant contracts MUST implement IERC_ACL_CORE It is RECOMMENDED for compliant contracts to implement the optional extension IERC_ACL_GENERAL. It’s RECOMMENDED the value of such role is computed as a keccak256 hash of a string of the role name, in this format: bytes32 role = keccak256(). keywords: data; role cache: eips-eip-5982.html plain text: eips-eip-5982.txt item: #665 of 3327 id: eips-eip-5988 author: eips title: eips-eip-5988 date: None words: 1248 flesch: 47 summary: It is true that arithmetic hash functions are relatively untested compared to traditional hash functions. EIP-5988: Add Poseidon hash function precompile Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-5988: Add Poseidon hash function precompile Add a precompiled contract which implements the hash function used in the Poseidon cryptographic hashing algorithm Authors Abdelhamid Bakhta (@abdelhamidbakhta), Eli Ben Sasson (@Elistark), Avihu Levy (@avihu28), David Levit Gurevich (@DavidLevitGurevich) Created 2022-11-15 Discussion Link https://ethereum-magicians.org/t/eip-5988-add-poseidon-hash-function-precompile/11772 Table of Contents Abstract Motivation Specification Parameters Rationale Backwards Compatibility Test Cases Security Considerations Security of the Poseidon parameters Papers and research related to Poseidon security Copyright Abstract This EIP introduces a new precompiled contract which implements the hash function used in the Poseidon cryptographic hashing algorithm, for the purpose of allowing interoperability between the EVM and ZK / Validity rollups, as well as introducing more flexible cryptographic hash primitives to the EVM. keywords: ethereum; function; hash; poseidon cache: eips-eip-5988.html plain text: eips-eip-5988.txt item: #666 of 3327 id: eips-eip-6 author: eips title: eips-eip-6 date: None words: 326 flesch: 37 summary: https://github.com/ethereum/solidity/commit/a8736b7b271dac117f15164cf4d2dfabcdd2c6fd https://github.com/ethereum/serpent/commit/1106c3bdc8f1bd9ded58a452681788ff2e03ee7c Citation Please cite this document as: Hudson Jameson , EIP-6: Renaming SUICIDE opcode, Ethereum Improvement Proposals, no. 6, November 2015. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: ethereum cache: eips-eip-6.html plain text: eips-eip-6.txt item: #667 of 3327 id: eips-eip-600 author: eips title: eips-eip-600 date: None words: 459 flesch: 43 summary: Given the already confused nature of wallet derivation paths in Ethereum, we anticipate this will cause relatively little additional disruption, and has the potential to improve matters significantly in the long run. References This discussion on derivation paths Copyright Copyright and related rights waived via CC0. keywords: ethereum; purpose cache: eips-eip-600.html plain text: eips-eip-600.txt item: #668 of 3327 id: eips-eip-601 author: eips title: eips-eip-601 date: None words: 615 flesch: 42 summary: Given the already confused nature of wallet derivation paths in Ethereum, we anticipate this will cause relatively little additional disruption, and has the potential to improve matters significantly in the long run. References This discussion on derivation paths Copyright Copyright and related rights waived via CC0. keywords: derivation; ethereum cache: eips-eip-601.html plain text: eips-eip-601.txt item: #669 of 3327 id: eips-eip-6046 author: eips title: eips-eip-6046 date: None words: 629 flesch: 49 summary: Because the semantics of revival change (storage keys may exists), we also rename the instruction to DEACTIVATE. Contracts using the revival pattern will still work, but the code deployed during revival may need to be made aware that storage keys can already exist in the account. keywords: account; selfdestruct cache: eips-eip-6046.html plain text: eips-eip-6046.txt item: #670 of 3327 id: eips-eip-6047 author: eips title: eips-eip-6047 date: None words: 447 flesch: 37 summary: Citation Please cite this document as: Zainan Victor Zhou (@xinbenlv), ERC-6047: ERC-721 Balance indexing via Transfer event [DRAFT], Ethereum Improvement Proposals, no. 6047, November 2022. Created 2022-11-26 Discussion Link https://ethereum-magicians.org/t/eip-xxx-require-erc721-to-always-emit-transfer/11894 Requires EIP-721 Table of Contents Abstract Motivation Specification Rationale Backwards Compatibility Security Considerations Copyright Abstract This EIP extends ERC-721 to allow the tracking and indexing of NFTs by mandating that a pre-existing event be emitted during contract creation. keywords: transfer cache: eips-eip-6047.html plain text: eips-eip-6047.txt item: #671 of 3327 id: eips-eip-6049 author: eips title: eips-eip-6049 date: None words: 231 flesch: 37 summary: Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. Citation Please cite this document as: William Entriken (@fulldecent), EIP-6049: Deprecate SELFDESTRUCT, Ethereum Improvement Proposals, no. 6049, November 2022. keywords: ethereum cache: eips-eip-6049.html plain text: eips-eip-6049.txt item: #672 of 3327 id: eips-eip-6051 author: eips title: eips-eip-6051 date: None words: 3248 flesch: 46 summary: We might dedicate one of many private keys for messaging purposes, and that private key is probably managed in a not-so-secure manner; We might want to export one of many private keys from a hardware wallet, and split it with MPC technology so that a 3rd party service could help us identify potential frauds or known bad addresses, enforce 2FA, etc., meanwhile we can initiate transactions from a mobile device with much better UX and without carrying a hardware wallet. EIP-6051: Private Key Encapsulation Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Interface EIP-6051: Private Key Encapsulation defines a specification for encapsulating private keys. keywords: key; recipient; signature; signerpubkey cache: eips-eip-6051.html plain text: eips-eip-6051.txt item: #673 of 3327 id: eips-eip-6059 author: eips title: eips-eip-6059 date: None words: 4407 flesch: 62 summary: Child tokens of a given token can be fully managed by the parent token’s owner, but can be proposed by anyone. Having a token with multiple soulbound traits (child tokens), allows for numerous use cases. keywords: @param; array; child; parent; token; uint256 cache: eips-eip-6059.html plain text: eips-eip-6059.txt item: #674 of 3327 id: eips-eip-606 author: eips title: eips-eip-606 date: None words: 146 flesch: 35 summary: Citation Please cite this document as: Alex Beregszaszi (@axic), EIP-606: Hardfork Meta: Homestead, Ethereum Improvement Proposals, no. 606, April 2017. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: ethereum cache: eips-eip-606.html plain text: eips-eip-606.txt item: #675 of 3327 id: eips-eip-6065 author: eips title: eips-eip-6065 date: None words: 2644 flesch: 45 summary: Additionally, since real world property rights are enforced by the court of law, it is essential that property ownership be documented in such a way that courts are able to interpret and enforce ownership if necessary. The three objectives this standard aims to meet are: universal transferability of the NFT, private property rights attached to the NFT, and atomic transfer of property rights with the transfer of the NFT. keywords: asset; function; nft; property; token; transfer cache: eips-eip-6065.html plain text: eips-eip-6065.txt item: #676 of 3327 id: eips-eip-6066 author: eips title: eips-eip-6066 date: None words: 996 flesch: 37 summary: Compliant callers wanting to support contract signatures MUST call this method if the signer is the holder of an NFT (ERC-721 or ERC-1155). The bytes calldata data parameter is considered optional if extra data is needed for signature verification, also conforming this EIP to ERC-5750 for future-proofing purposes. keywords: hash; signature; tokenid cache: eips-eip-6066.html plain text: eips-eip-6066.txt item: #677 of 3327 id: eips-eip-607 author: eips title: eips-eip-607 date: None words: 151 flesch: 40 summary: EIP-607: Hardfork Meta: Spurious Dragon, Ethereum Improvement Proposals, no. 607, April 2017. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: ethereum cache: eips-eip-607.html plain text: eips-eip-607.txt item: #678 of 3327 id: eips-eip-608 author: eips title: eips-eip-608 date: None words: 137 flesch: 19 summary: Citation Please cite this document as: Alex Beregszaszi (@axic), EIP-608: Hardfork Meta: Tangerine Whistle, Ethereum Improvement Proposals, no. 608, April 2017. Hardfork Meta: Tangerine Whistle Authors Alex Beregszaszi (@axic) Created 2017-04-23 Requires EIP-150, EIP-779 Table of Contents Abstract Specification References Copyright Abstract This specifies the changes included in the hard fork named Tangerine Whistle (EIP 150). keywords: ethereum cache: eips-eip-608.html plain text: eips-eip-608.txt item: #679 of 3327 id: eips-eip-609 author: eips title: eips-eip-609 date: None words: 214 flesch: 13 summary: Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. Citation Please cite this document as: Alex Beregszaszi (@axic), EIP-609: Hardfork Meta: Byzantium, Ethereum Improvement Proposals, no. 609, April 2017. keywords: ethereum cache: eips-eip-609.html plain text: eips-eip-609.txt item: #680 of 3327 id: eips-eip-6093 author: eips title: eips-eip-6093 date: None words: 2174 flesch: 36 summary: Error prefixes Domain Arguments Error grammar rules Backwards Compatibility Reference Implementation Solidity Security Considerations Copyright Abstract This EIP defines a standard set of custom errors for commonly-used tokens, which are defined as ERC-20, ERC-721, and ERC-1155 tokens. Rationale The chosen objectives for a standard for token errors are to provide context about the error, and to make moderate use of meaningful arguments (to maintain the code size benefits with respect to strings). keywords: error; guidelines; transfers; uint256; usage cache: eips-eip-6093.html plain text: eips-eip-6093.txt item: #681 of 3327 id: eips-eip-6105 author: eips title: eips-eip-6105 date: None words: 4113 flesch: 29 summary: @param buyer - address of who wants to buy the token /// Requirements: /// - `tokenId` must exist and and be offered for /// - Caller must be owner, authorised operators or approved address of the token /// - Must emit a {Purchased} event function acceptCollectionOffer(uint256 tokenId, uint256 salePrice, address supportedToken, address buyer) external; /// @notice Accepts collection offer and transfers the token to the buyer /// @dev `salePrice` and `supportedToken` must match the expected purchase price and token to prevent front-running attacks /// When the trading is completed, the `amount` of NFTs the buyer wants to purchase needs to be reduced by 1 /// @param tokenId - identifier of the token being offered /// @param buyer - address of who wants to buy the token /// @param benchmarkPrice - additional price parameter, may be used when calculating royalties /// Requirements: /// - `tokenId` must exist and and be offered for /// - Caller must be owner, authorised operators or approved address of the token /// - Must emit a {Purchased} event function acceptCollectionOffer(uint256 tokenId, uint256 salePrice, address supportedToken, address buyer, uint256 benchmarkPrice) external; /// @notice Removes the offer for the collection /// Requirements: /// - Caller must be the offerer /// - Must emit an {UpdateCollectionOffer} event function cancelCollectionOffer() external; /// @notice Returns the offer for `tokenId` maked by `buyer` /// @dev keywords: @param; address; saleprice; supportedtoken; token; tokenid cache: eips-eip-6105.html plain text: eips-eip-6105.txt item: #682 of 3327 id: eips-eip-6110 author: eips title: eips-eip-6110 date: None words: 1939 flesch: 38 summary: Supply validator deposits on chain Provides validator deposits as a list of deposit operations added to the Execution Layer block Authors Mikhail Kalinin (@mkalinin), Danny Ryan (@djrtwo), This EIP allows for an in-protocol mechanism of deposit processing on the Consensus Layer and eliminates the proposer voting mechanism utilized currently. keywords: block; consensus; deposit; layer; list cache: eips-eip-6110.html plain text: eips-eip-6110.txt item: #683 of 3327 id: eips-eip-6120 author: eips title: eips-eip-6120 date: None words: 3060 flesch: 42 summary: This enables new token contracts to pre-configure it as a trusted spender, eliminating the need for approval transactions during their interactive usage. Therefore, new token contracts MUST NOT implement this interface ID. keywords: address; contract; payment; recipient; token; uint256; utr cache: eips-eip-6120.html plain text: eips-eip-6120.txt item: #684 of 3327 id: eips-eip-6122 author: eips title: eips-eip-6122 date: None words: 1481 flesch: 61 summary: Block timestamps are regarded as uint64 integers, encoded in big endian format when checksumming. Forkid checks based on timestamps Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: Networking EIP-6122: Forkid checks based on timestamps Modifies the forkid checks to work with timestamps and block numbers Authors Marius van der Wijden (@MariusVanDerWijden) Created 2022-12-13 Requires EIP-2124 Table of Contents Abstract Motivation Specification Additional rules Rationale Backwards Compatibility Test Cases Security Considerations Copyright Abstract EIP-2124 proposed a way of identifying nodes on the p2p network based on their chain configuration via the forkid parameter. keywords: block; id{hash; local cache: eips-eip-6122.html plain text: eips-eip-6122.txt item: #685 of 3327 id: eips-eip-6123 author: eips title: eips-eip-6123 date: None words: 1502 flesch: 31 summary: This method serves as a callback called from an external oracle providing settlement amount and used settlement data, which also get stored. Usually, the valuation of financial trades (e.g. OTC Derivatives) will require advanced valuation methodology to determine the market value. keywords: contract; cycle; derivative; settlement; trade cache: eips-eip-6123.html plain text: eips-eip-6123.txt item: #686 of 3327 id: eips-eip-6147 author: eips title: eips-eip-6147 date: None words: 2388 flesch: 59 summary: Reference Implementation // SPDX-License-Identifier: CC0-1.0 pragma solidity ^0.8.8; import @openzeppelin/contracts/token/ERC721/ERC721.sol; import ./IERC6147.sol; abstract contract ERC6147 is ERC721, IERC6147 { /// @dev A structure representing a token of guard address and expires /// @param guard address of guard role /// { guard = _checkGuard(tokenId); new_from = ownerOf(tokenId); } if (guard == address(0)) { require( _isApprovedOrOwner(_msgSender(), tokenId), ERC721: transfer caller is not owner nor approved ); } _transfer(new_from, to, tokenId); } /// @dev Before safe transferring the NFT, need to check the gurard address function safeTransferFrom(address from, address to, uint256 tokenId, bytes memory _data) public virtual override { address guard; address new_from = from; if (from != address(0)) keywords: address; expires; guard; nft cache: eips-eip-6147.html plain text: eips-eip-6147.txt item: #687 of 3327 id: eips-eip-615 author: eips title: eips-eip-615 date: None words: 4060 flesch: 56 summary: continue } // recurse to jump to code to validate if instruction is JUMPIF { if not validate_subroutine(jump_target(PC), return_pc, SP) return false } // advance PC according to instruction PC = advance_pc(PC) } // check for right number of results if (-SP != n_results(return_pc) return false return true } Appendix B EVM Analysis There is a large and growing ecosystem of researchers, authors, teachers, auditors, and analytic tools–providing software and services focused on the correctness and security of EVM code. To that end we maintain a close correspondence between Wasm, x86, ARM and proposed EVM instructions. keywords: code; evm; frame; instruction; jumps; return; stack cache: eips-eip-615.html plain text: eips-eip-615.txt item: #688 of 3327 id: eips-eip-6150 author: eips title: eips-eip-6150 date: None words: 1754 flesch: 56 summary: If `parentId` is zero, means get root token index. This standard provides interfaces to get parent NFT or children NFTs and whether NFT is a leaf node or root node, maintaining the hierarchical relationship among them. keywords: @param; token; tokenid; uint256 cache: eips-eip-6150.html plain text: eips-eip-6150.txt item: #689 of 3327 id: eips-eip-616 author: eips title: eips-eip-616 date: None words: 1493 flesch: 59 summary: EIP-616: SIMD Operations for the EVM Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-616: SIMD Operations for the EVM Authors Greg Colvin  Created 2017-04-25 Table of Contents ABSTRACT MOTIVATION SPECIFICATION Encoding Semantics Subroutines RATIONALE Gas ABSTRACT A proposal to provide Single Instruction Multiple Data types and operations for the Ethereum Virtual Machine, making full use of the 256-bit wide EVM stack items, and offering substantial performance gains for both vector and scalar operations. For some examples, a brief literature search finds SIMD speedups of up to 7X for SHA-512 4X for elliptic curve scalar multiplication 3X to 4X for BLAKE2b up to 3X for OpenSSL 2X to 3X for elliptic curve modular multiplication 1.7X to 1.9X for SHA-256 1.3X for RSA encryption SPECIFICATION Encoding We propose a simple encoding of SIMD operations as extended two-byte codes. keywords: bit; elements; operations; simd; stack cache: eips-eip-616.html plain text: eips-eip-616.txt item: #690 of 3327 id: eips-eip-6170 author: eips title: eips-eip-6170 date: None words: 843 flesch: 50 summary: Authors Sujith Somraaj (@sujithsomraaj) Created 2022-12-19 Discussion Link https://ethereum-magicians.org/t/cross-chain-messaging-standard/12197 Table of Contents Abstract Motivation Specification Rationale Security Considerations Copyright Abstract This EIP introduces a common interface for cross-chain arbitrary message bridges (AMBs) to send and receive a cross-chain message (state). Motivation Currently, cross-chain arbitrary message bridges lack standardization, resulting in complex competing implementations: Layerzero, Hyperlane, Axelar, Wormhole, Matic State Tunnel and others. keywords: bytes; chain; message cache: eips-eip-6170.html plain text: eips-eip-6170.txt item: #691 of 3327 id: eips-eip-6188 author: eips title: eips-eip-6188 date: None words: 395 flesch: 57 summary: The further restriction of nonce should not have an effect on accounts, as reaching a nonce of 2^64-2 is difficult. If the nonce is either 2^64-1 or 2^64-2, the transaction MUST be invalid. keywords: nonce cache: eips-eip-6188.html plain text: eips-eip-6188.txt item: #692 of 3327 id: eips-eip-6189 author: eips title: eips-eip-6189 date: None words: 1427 flesch: 59 summary: Alias contracts automatically forward calls to other contracts. The CALL, CALLCODE, DELEGATECALL, and STATICCALL opcodes and EOA Transactions MUST cost an 25 gas per account accessed in this manner (including the final one, and including if no aliased accounts were used), in addition to all the regular costs incurred by accessing accounts (see EIP-2929). keywords: alias; contract cache: eips-eip-6189.html plain text: eips-eip-6189.txt item: #693 of 3327 id: eips-eip-6190 author: eips title: eips-eip-6190 date: None words: 583 flesch: 56 summary: Furthermore, with Verkle trees accounts will be organised differently. The 5000 base gas cost and additional alias contracts represents the cost of setting the account nonce and first storage slot. keywords: contract; selfdestruct cache: eips-eip-6190.html plain text: eips-eip-6190.txt item: #694 of 3327 id: eips-eip-6206 author: eips title: eips-eip-6206 date: None words: 897 flesch: 41 summary: JUMPF optimizes this behavior by changing code sections without needing to update the return stack. The immediate argument of JUMPF MUST be less than the total number of code sections. keywords: jumpf; section; stack cache: eips-eip-6206.html plain text: eips-eip-6206.txt item: #695 of 3327 id: eips-eip-6220 author: eips title: eips-eip-6220 date: None words: 3358 flesch: 61 summary: A `Part` to be added */ struct IntakeStruct { uint64 partId; Part part; } /** * @notice Used to return the metadata URI of the associated catalog. Having one Catalog supporting multiple collections allows for optimized operation and reduced gas prices when deploying it and setting fixed as well as slot parts. keywords: @param; equippable; parts; slot; token cache: eips-eip-6220.html plain text: eips-eip-6220.txt item: #696 of 3327 id: eips-eip-6224 author: eips title: eips-eip-6224 date: None words: 1654 flesch: 36 summary: ERC-6224: Contracts Dependencies Registry Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-6224: Contracts Dependencies Registry An interface for managing smart contracts with their dependencies. ContractsRegistry Security Considerations The non-view methods of ContractsRegistry contract MUST be overridden with proper access control checks. keywords: @notice; @param; contract; function cache: eips-eip-6224.html plain text: eips-eip-6224.txt item: #697 of 3327 id: eips-eip-6239 author: eips title: eips-eip-6239 date: None words: 2049 flesch: 52 summary: RDF data is a collection of RDF statements that are used to represent information about resources. RDF data is a collection of RDF statements that are used to represent information about resources. keywords: data; rdf; semantic; soulbound; token cache: eips-eip-6239.html plain text: eips-eip-6239.txt item: #698 of 3327 id: eips-eip-6268 author: eips title: eips-eip-6268 date: None words: 596 flesch: 58 summary: While EIP-5192 standardizes non-fungible SBTs, a standard for Soulbound semi-fungible or fungible tokens does not yet exist. Motivation Soulbound Tokens (SBT) are non-transferable tokens. keywords: status; token cache: eips-eip-6268.html plain text: eips-eip-6268.txt item: #699 of 3327 id: eips-eip-627 author: eips title: eips-eip-627 date: None words: 1488 flesch: 59 summary: EIP-627: Whisper Specification Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: Networking EIP-627: Whisper Specification Authors Vlad Gluhovsky  Created 2017-05-05 Table of Contents Abstract Motivation Specification Packet Codes Packet Format and Usage Whisper Envelope Contents of Data Field of the Message (Optional) Payload Encryption Rationale Backwards Compatibility Implementation Copyright Abstract This EIP describes the format of Whisper messages within the ÐΞVp2p Wire Protocol. Motivation It is necessary to specify the standard for Whisper messages in order to ensure forward compatibility of different Whisper clients. keywords: message; packet; size; whisper cache: eips-eip-627.html plain text: eips-eip-627.txt item: #700 of 3327 id: eips-eip-6315 author: eips title: eips-eip-6315 date: None words: 618 flesch: 33 summary: Rationale The approach of simply augmenting existing EIP functions with new address parameters, rather than crafting new interfaces for the most commonly used EIPs, is employed to ensure broader applicability of this namespacing proposal. The original function MUST exhibit identical behavior to the new function when Forwarder addresses are the zero address. keywords: address; forwarder cache: eips-eip-6315.html plain text: eips-eip-6315.txt item: #701 of 3327 id: eips-eip-6327 author: eips title: eips-eip-6327 date: None words: 1491 flesch: 51 summary: Reference Implementation Example implementation of a signing contract: pragma solidity ^0.8.0; import ../interfaces/IElasticSignature.sol; import ./verifier.sol; contract ZKPass is IElasticSignature { Verifier verifier = new Verifier(); mapping(address => uint) public pwdhashOf; mapping(address => uint) public nonceOf; constructor() { } function resetPassword( uint[8] memory proof1, uint expiration1, uint allhash1, uint[8] memory proof2, uint pwdhash2, uint expiration2, uint allhash2 ) public override { uint nonce = nonceOf[msg.sender]; if (nonce == 0) { //init password pwdhashOf[msg.sender] = pwdhash2; nonceOf[msg.sender] = 1; verify(msg.sender, proof2, 0, expiration2, allhash2); } else { //reset password // check old pwdhash verify(msg.sender, proof1, 0, expiration1, allhash1); // check new pwdhash pwdhashOf[msg.sender] = pwdhash2; verify(msg.sender, proof2, 0, expiration2, allhash2); } emit SetPassword(msg.sender, pwdhash2); } function verify( address user, uint[8] memory proof, uint datahash, uint expiration, uint allhash ) public override { require( block.timestamp < expiration, ZKPass::verify: expired ); uint pwdhash = pwdhashOf[user]; require( pwdhash ! util //////////// function verifyProof( uint[8] memory proof, uint pwdhash, uint fullhash, //254b uint allhash ) internal view returns (bool) { return verifier.verifyProof( [proof[0], proof[1]], keywords: proof; uint; user cache: eips-eip-6327.html plain text: eips-eip-6327.txt item: #702 of 3327 id: eips-eip-634 author: eips title: eips-eip-634 date: None words: 716 flesch: 42 summary: In this EIP we define a simple resolver profile for ENS that permits ENS names to associate arbitrary key-value text. A notice regarding this name location - A generic location (e.g. Toronto, Canada) phone - A phone number as an E.164 string url - a website URL Service Keys Service Keys must be made up of a reverse dot notation for a namespace which the service owns, for example, DNS names (e.g. .com, .io, etc) or ENS name (i.e. .eth). keywords: ens; keys; text cache: eips-eip-634.html plain text: eips-eip-634.txt item: #703 of 3327 id: eips-eip-6353 author: eips title: eips-eip-6353 date: None words: 1537 flesch: 50 summary: Projects can easily retrieve charity donations addresses and rate for a given EIP-20 token, token holders can compare minimum rate donation offers allowed by token contract owners. ** *@notice Set personlised rate for charity address in {whitelistedRate}. keywords: address; default; rate cache: eips-eip-6353.html plain text: eips-eip-6353.txt item: #704 of 3327 id: eips-eip-6357 author: eips title: eips-eip-6357 date: None words: 535 flesch: 36 summary: Available: https://eips.ethereum.org/EIPS/eip-6357. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. Citation Please cite this document as: Gavin John (@Pandapip1), ERC-6357: Single-contract Multi-delegatecall [DRAFT], Ethereum Improvement Proposals, no. 6357, January 2023. keywords: abi; data cache: eips-eip-6357.html plain text: eips-eip-6357.txt item: #705 of 3327 id: eips-eip-6358 author: eips title: eips-eip-6358 date: None words: 3181 flesch: 50 summary: The nonce appears in two places, the one is nonce in o-transaction data structure, and the other is account nonce maintained by on-chain ERC-6358 smart contracts. When synchronizing, the nonce in o-transaction data will be checked by comparing it to the account nonce. keywords: account; nonce; omniverse; transaction cache: eips-eip-6358.html plain text: eips-eip-6358.txt item: #706 of 3327 id: eips-eip-6366 author: eips title: eips-eip-6366 date: None words: 843 flesch: 38 summary: * @param _from Permission owner * @param _to Permission receiver * @param _permission Transferred subset permission of permission owner */ event Transfer(address indexed _from, address indexed _to, uint256 indexed _permission); / * @param _delegatee Delegatee * @param _permission Approved subset permission of permission owner */ event Approval(address indexed _owner, address indexed _delegatee, uint256 indexed _permission); / keywords: owner; permission cache: eips-eip-6366.html plain text: eips-eip-6366.txt item: #707 of 3327 id: eips-eip-6372 author: eips title: eips-eip-6372 date: None words: 759 flesch: 50 summary: Citation Please cite this document as: Hadrien Croubois (@Amxx), Francisco Giordano (@frangio), ERC-6372: Contract clock [DRAFT], Ethereum Improvement Proposals, no. 6372, January 2023. Available: https://eips.ethereum.org/EIPS/eip-6372. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: clock; contract; function cache: eips-eip-6372.html plain text: eips-eip-6372.txt item: #708 of 3327 id: eips-eip-6381 author: eips title: eips-eip-6381 date: None words: 3335 flesch: 60 summary: * @param collection Address of the collection containing the token being checked for emoji count * @param tokenId ID of the token to check for emoji count * @param emoji Unicode identifier of the emoji * @return Number of emotes with the emoji on the token */ function emoteCountOf( address collection, uint256 tokenId, bytes4 emoji ) external view returns (uint256); / A boolean value indicating whether the `emoter` has used the `emoji` on the token (`true`) or not * (`false`) */ function hasEmoterUsedEmote( address emoter, address collection, uint256 tokenId, bytes4 emoji ) external view returns (bool); /** * @notice Used to get the information on whether the specified addresses have used specific emojis on specific * tokens. keywords: @param; address; emoji; emote; token cache: eips-eip-6381.html plain text: eips-eip-6381.txt item: #709 of 3327 id: eips-eip-6384 author: eips title: eips-eip-6384 date: None words: 1466 flesch: 46 summary: Authors Tal Be'ery , RoiV (@DeVaz1) Created 2023-01-08 Discussion Link https://ethereum-magicians.org/t/eip-6384-readable-eip-712-signatures/12752 Requires EIP-712 Table of Contents Abstract Motivation Specification Function’s inputs Function’s output(s) Support for EIP-712 messages that are not meant to be used on-chain Rationale Alternative solutions Backwards Compatibility Reference Implementation Security Considerations The threat model: Analysis of the proposed solution Copyright Abstract This EIP introduces the evalEIP712Buffer function, which takes an EIP-712 buffer and returns a human-readable text description. While EIP-712 originally declared in its title that being ”humanly readable” is one of its goals, it did not live up to its promise eventually and EIP-712 messages are not understandable by an average user. keywords: contract; eip-712; message cache: eips-eip-6384.html plain text: eips-eip-6384.txt item: #710 of 3327 id: eips-eip-6404 author: eips title: eips-eip-6404 date: None words: 597 flesch: 31 summary: Transaction indexing While a unique transaction identifier tx_hash is defined for each transaction, there is no on-chain commitment to this identifier for RLP transactions. EIP-6493 defines how RLP transactions can be converted to SSZ. keywords: ssz; transactions cache: eips-eip-6404.html plain text: eips-eip-6404.txt item: #711 of 3327 id: eips-eip-6454 author: eips title: eips-eip-6454 date: None words: 1924 flesch: 47 summary: In a blockchain game that employs non-transferable NFTs to represent skills or abilities, each skill would be a unique and permanent asset tied to a specific player or token. This proposal aims to provide the minimum necessary specification for the implementation of non-transferable NFTs, we feel none of the existing proposals have presented the minimal required interface. keywords: parameter; proposal; token cache: eips-eip-6454.html plain text: eips-eip-6454.txt item: #712 of 3327 id: eips-eip-6464 author: eips title: eips-eip-6464 date: None words: 1295 flesch: 36 summary: Non-goals Security measures for protecting NFTs other than through limiting the scope of operator approvals. The criteria MUST be extended if other mechanism(s) for approving operators are introduced. keywords: approvals; operator; owner; token cache: eips-eip-6464.html plain text: eips-eip-6464.txt item: #713 of 3327 id: eips-eip-6465 author: eips title: eips-eip-6465 date: None words: 724 flesch: 33 summary: legacy-withdrawal = [ index: P, validator-index: P, address: B_20, amount: P, ] Typed withdrawals are encoded as RLP byte arrays where the first byte is a withdrawal type (withdrawal-type) and the remaining bytes are opaque type-specific data. typed-withdrawal = withdrawal-type || withdrawal-data Networking When exchanging SSZ withdrawals via the Ethereum Wire Protocol, the following withdrawal envelope is used: Withdrawal: TRANSACTION_TYPE_SSZ || snappyFramed(ssz(Withdrawal)) class Withdrawal(Container): index: WithdrawalIndex validator_index: ValidatorIndex address: ExecutionAddress amount: Gwei Execution block header changes The execution block header’s withdrawals-root is updated to match the consensus ExecutionPayloadHeader.withdrawals_root. withdrawals = List[Withdrawal, MAX_WITHDRAWALS_PER_PAYLOAD]( withdrawal_0, withdrawal_1, withdrawal_2, ...) block_header.withdrawals_root == withdrawals.hash_tree_root() Typed withdrawal envelope A typed withdrawal envelope similar to EIP-2718 is introduced for exchanging withdrawals via the Ethereum Wire Protocol. withdrawal = {legacy-withdrawal, typed-withdrawal} Untyped, legacy withdrawals are given as an RLP list as defined in EIP-4895. keywords: ethereum; ssz; withdrawal cache: eips-eip-6465.html plain text: eips-eip-6465.txt item: #714 of 3327 id: eips-eip-6466 author: eips title: eips-eip-6466 date: None words: 443 flesch: 31 summary: To compute the receipts_root, the list of individual Receipt containers is represented as an SSZ List. Table of Contents Abstract Motivation Specification Consensus ExecutionPayload changes Consensus ExecutionPayloadHeader changes Execution block header changes Rationale Backwards Compatibility Security Considerations Copyright Abstract This EIP defines a migration process of existing Merkle-Patricia Trie (MPT) commitments for receipts to Simple Serialize (SSZ) keywords: root; ssz cache: eips-eip-6466.html plain text: eips-eip-6466.txt item: #715 of 3327 id: eips-eip-6475 author: eips title: eips-eip-6475 date: None words: 544 flesch: 41 summary: Compact serialization: SSZ serialization can rely on the binary nature of optional values; they either exist or they don’t. Furthermore, SSZ Union types are currently not used in any final Ethereum specification and do not have a finalized design themselves. keywords: optional[t; ssz cache: eips-eip-6475.html plain text: eips-eip-6475.txt item: #716 of 3327 id: eips-eip-649 author: eips title: eips-eip-649 date: None words: 722 flesch: 46 summary: Furthermore, block rewards will be adjusted to a base of 3 ETH, uncle and nephew rewards will be adjusted accordingly. Analogue, if an uncle is included in a block for block.number >= BYZANTIUM_FORK_BLKNUM such that block.number - uncle.number = k, the uncle reward is new_uncle_reward = (8 - k) * new_block_reward / 8 This is the existing pre-Metropolis formula for uncle rewards, simply adjusted with new_block_reward. keywords: block; difficulty cache: eips-eip-649.html plain text: eips-eip-649.txt item: #717 of 3327 id: eips-eip-6492 author: eips title: eips-eip-6492 date: None words: 2109 flesch: 24 summary: Applications wanting to support contract signatures should call this method if the signer is a contract. Using ERC-6492 for regular contract signatures The wrapper format described in this ERC can be used for all contract signatures, instead of plain ERC-1271. keywords: bytes; contract; erc-1271; signature cache: eips-eip-6492.html plain text: eips-eip-6492.txt item: #718 of 3327 id: eips-eip-6493 author: eips title: eips-eip-6493 date: None words: 2752 flesch: 23 summary: To restore the optimization potential, types is redefined to indicate instead what auxiliary payloads are present in the PooledTransaction: SSZ blob transactions will share type 0x03 with RLP blob transactions, while basic SSZ transactions will be assigned type 0x01, which is currently also used for a basic RLP transaction type. Networking When exchanging SSZ transactions and receipts via the Ethereum Wire Protocol, the following EIP-2718 compatible envelopes are used: keywords: class; fields; signature; ssz; transaction; type; uint256; value cache: eips-eip-6493.html plain text: eips-eip-6493.txt item: #719 of 3327 id: eips-eip-6506 author: eips title: eips-eip-6506 date: None words: 3589 flesch: 45 summary: Contracts wishing to implement such a standard must implement the following interface interface IEscrowedGovIncentive { struct incentive { address incentiveToken; address incentivizer; address recipient; uint amount; uint256 proposalId; bytes32 direction; //the keccack256 of the vote direction uint96 deadline; uint96 timestamp; bool claimed; } event incentiveSent(address indexed incentivizer, address indexed token, uint256 indexed amount, address recipient, bytes data); event incentiveReclaimed(address incentivizer, address indexed recipient, address indexed token, uint256 indexed amount, bytes data); event modifiedClaimer(address recipient, address claimer, bool direction); event incentiveClaimed(address indexed incentivizer, address voter, bytes32 incentiveId, bytes proofData); event disputeInitiated(bytes32 indexed incentiveId, address indexed plaintiff, address indexed defendant); event disputeResolved(bytes32 indexed incentive, address indexed plaintiff, address indexed defendant, bool dismissed); //Core mechanism function incentivize(bytes32 incentiveId, bytes memory incentiveInfo) external payable; function claimIncentive(bytes32 incentiveId, bytes memory reveal, address payable recipient) external; function reclaimIncentive(bytes32 incentiveId, bytes memory reveal) external; function verifyVote(bytes32 incentive, bytes memory voteInfo) external view returns (bool isVerifiable, bytes proofData); function modifyClaimer(address claimer, bool designation) external; //Dispute Mechanism function beginDispute(bytes32 incentiveId, bytes memory disputeInfo) external payable; function resolveDispute(bytes32 incentiveId, bytes memory disputeResolutionInfo) external returns (bool isDismissed); } Optional Implementation Details Below are three potential implementation examples of the above system for different aspects. User B votes. keywords: address; function; incentiveid; recipient; type; vote cache: eips-eip-6506.html plain text: eips-eip-6506.txt item: #720 of 3327 id: eips-eip-6538 author: eips title: eips-eip-6538 date: None words: 859 flesch: 48 summary: This enables applications such as ENS or Gnosis Safe to use that information and integrate stealth addresses into their services. This integer is used to differentiate between different stealth address schemes. keywords: address; scheme cache: eips-eip-6538.html plain text: eips-eip-6538.txt item: #721 of 3327 id: eips-eip-6551 author: eips title: eips-eip-6551 date: None words: 3697 flesch: 36 summary: Overview The system outlined in this proposal has two main components: A singleton registry for token bound accounts A common interface for token bound account implementations The following diagram illustrates the relationship between NFTs, NFT holders, token bound accounts, and the Registry: Registry The registry is a singleton contract that serves as the entry point for all token bound account address queries. This allows token bound account implementations to easily query this data while ensuring it remains constant. keywords: account; address; bytes; implementation; interface; registry; returns; token; uint256 cache: eips-eip-6551.html plain text: eips-eip-6551.txt item: #722 of 3327 id: eips-eip-658 author: eips title: eips-eip-658 date: None words: 337 flesch: 40 summary: EIP-658: Embedding transaction status code in receipts Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: Core EIP-658: Embedding transaction status code in receipts Authors Nick Johnson  Created 2017-06-30 Requires EIP-140 Table of Contents Abstract Motivation Specification Rationale Copyright Abstract This EIP replaces the intermediate state root field of the receipt with a status code indicating if the top-level call succeeded or failed. This both allows callers to determine success status, and remedies the previous omission of return data from the receipt. keywords: status cache: eips-eip-658.html plain text: eips-eip-658.txt item: #723 of 3327 id: eips-eip-6596 author: eips title: eips-eip-6596 date: None words: 3658 flesch: 24 summary: Attribute object may be repeated if a field has // multiple values } type CHATAttribute = { trait_type: Catalogue Level, value: string } | { trait_type: Publication / Creation Date, value: string } | { trait_type: Creator Name, value: string } | { trait_type: Creator Bio, value: string } | { trait_type: Asset Type, value: string } | { trait_type: Classification, value: string } | { trait_type: Materials and Technology, value: string } | { trait_type: Subject Matter, value: string } | { trait_type: Edition, value: string } | { trait_type: Series name, value: string } | { trait_type: Dimensions Unit, value: string } | { trait_type: Dimensions (height), value: number } | { trait_type: Dimensions (width), value: number } | { trait_type: Dimensions (depth), value: number } | { trait_type: Inscriptions / Marks, value: string } | { trait_type: Credit Line, value: string } | { trait_type: Current Owner, value: string } | { trait_type: Provenance, value: string } | { trait_type: Acquisition Date, value: string } | { trait_type: Citation, value: string } | { trait_type: Keyword, value: string } | { trait_type: Copyright Holder, value: string } | { trait_type: Bibliography, value: string } | { trait_type: Issuer, value: string } | { trait_type: Issue Timestamp, value: string } | { trait_type: Issuer Description, value: string } | { trait_type: Asset File Size, value: number } | { trait_type: Asset File Format, value: string } | { trait_type: Copyright / Restrictions, value: string } | { trait_type: Asset Creation Geo, value: string } | { trait_type: Asset Creation Location, value: string } | { trait_type: Asset Creation Coordinates, value: string } | { trait_type: Relevant Date, value: string } | { trait_type: Relevant Geo, value: string } | { trait_type: Relevant Location, value: string } | { trait_type: Relevant Person, value: string } | { trait_type: Relevant Entity, value: string } | { trait_type: Asset Language, value: string } | { trait_type: Is Physical Asset, value: boolean } type ExtendedCHATAttribute = { trait_type: Asset Full Text, value: string } | { trait_type: Exhibition / Loan History, value: string } | { trait_type: Copyright Document, value: string } | { trait_type: Provenance Document, value: string } | { trait_type: Asset URL, value: string } | { trait_type: Copyright Document of Underlying Asset, value: string } CHATAttribute Description trait_type description Catalogue Level An indication of the level of cataloging represented by the record, based on the physical form or intellectual content of the material Publication / Creation Date Earliest possible creation date of the underlying asset in ISO 8601 date format Creator Name The name, brief biographical information, and roles (if necessary) of the named or anonymous individuals or corporate bodies responsible for the design, production, manufacture, or alteration of the work, presented in a syntax suitable for display to the end-user and including any necessary indications of uncertainty, ambiguity, and nuance. These tokens represent cultural and historical assets such as artwork, artifacts, collectibles, and rare items, providing crucial context and provenance to substantiate their significance and value. keywords: art; asset; attributes; chat; metadata; string; trait_type; value cache: eips-eip-6596.html plain text: eips-eip-6596.txt item: #724 of 3327 id: eips-eip-6604 author: eips title: eips-eip-6604 date: None words: 1524 flesch: 39 summary: If implemented, dereification: MUST burn the exact tokens from the holder as defined in the token message MUST NOT dereify token messages scoped to the same contract and chain. Message Loss Because token messages are not held on-chain, loss of the message may result in loss of the token. keywords: abstract; calldata; message; token cache: eips-eip-6604.html plain text: eips-eip-6604.txt item: #725 of 3327 id: eips-eip-6617 author: eips title: eips-eip-6617 date: None words: 927 flesch: 42 summary: @param _grantor Grantor of the permission @param _permission Permission that is granted @param _user User who received the permission */ event PermissionGranted(address indexed _grantor, uint256 indexed _permission, address indexed _user); / PermissionRevoked(address indexed _revoker, uint256 indexed _permission, address indexed _user); / keywords: @param; permission; user cache: eips-eip-6617.html plain text: eips-eip-6617.txt item: #726 of 3327 id: eips-eip-663 author: eips title: eips-eip-663 date: None words: 794 flesch: 59 summary: After DUPN stack height is incremented. 3.2. Introducing SWAPN and DUPN will provide an option to compilers to simplify accessing deep stack items at the price of possibly increased gas costs. keywords: dupn; stack cache: eips-eip-663.html plain text: eips-eip-663.txt item: #727 of 3327 id: eips-eip-665 author: eips title: eips-eip-665 date: None words: 1104 flesch: 36 summary: EIP-665: Add precompiled contract for Ed25519 signature verification Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-665: Add precompiled contract for Ed25519 signature verification Authors Tobias Oberstein  Created 2018-03-25 Table of Contents Simple Summary Abstract Motivation Specification Address Gas costs Rationale Backwards Compatibility Test Cases Implementation libsodium libsodium bindings PRs References Copyright Simple Summary Support performant and cheap verification of Ed25519 cryptographic signatures in smart contracts in general by adding a precompiled contract for Ed25519 signature verification to the EVM. Citation Please cite this document as: Tobias Oberstein , EIP-665: Add precompiled contract for Ed25519 signature verification [DRAFT], Ethereum Improvement Proposals, no. 665, March 2018. keywords: contract; ed25519; ethereum cache: eips-eip-665.html plain text: eips-eip-665.txt item: #728 of 3327 id: eips-eip-6662 author: eips title: eips-eip-6662 date: None words: 899 flesch: 39 summary: If the authenticator is online, it can play the role of Relay service and listen to dApps directly. Relay Service Selection Each authenticator can provide a list of relay services. keywords: authentication; interface; relay cache: eips-eip-6662.html plain text: eips-eip-6662.txt item: #729 of 3327 id: eips-eip-6672 author: eips title: eips-eip-6672 date: None words: 1528 flesch: 48 summary: Redemption status, i.e. status The redemption status can have a more granular level, rather than just being a flag with a true or false value. pragma solidity ^0.8.16; /// @title ERC-6672 Multi-Redeemable NFT Standard /// @dev See https://eips.ethereum.org/EIPS/eip-6672 /// keywords: nft; operator; redemption; tokenid cache: eips-eip-6672.html plain text: eips-eip-6672.txt item: #730 of 3327 id: eips-eip-6682 author: eips title: eips-eip-6682 date: None words: 943 flesch: 42 summary: Created 2023-03-12 Discussion Link https://ethereum-magicians.org/t/eip-6682-nft-flashloans/13294 Requires EIP-20, EIP-721, EIP-3156 Table of Contents Abstract Motivation Specification Contract Interface Rationale Backwards Compatibility Reference Implementation Security Considerations Copyright Abstract This standard is an extension of the existing flashloan standard (ERC-3156) to support ERC-721 NFT flashloans. Contract Interface pragma solidity ^0.8.19; interface IERC6682 { /// @dev The address of the token used to pay flash loan fees. function flashFeeToken() external view returns (address); /// @dev Whether or not the NFT is available for a flash loan. keywords: nft; return; token cache: eips-eip-6682.html plain text: eips-eip-6682.txt item: #731 of 3327 id: eips-eip-6690 author: eips title: eips-eip-6690 date: None words: 2847 flesch: 33 summary: == len(y) and len(y) == len(mod), {}, {}, {}.format(x, y, mod) assert mod[0] ! if T >= mod: T -= mod return T def mulmont(mod_state: ModState, x: int, y: int) -> int: if mod_state.val_size_multiplier >= MULMODX_SUBQUADRATIC_START: return mulmont_subquadratic(x, y, mod_state.mod, mod_state.mod_inv) else: x_bigint = int_to_bigint(x, (mod_state.val_size_multiplier * 64) // SYSTEM_WORD_SIZE_BITS) y_bigint = int_to_bigint(y, (mod_state.val_size_multiplier * 64) // SYSTEM_WORD_SIZE_BITS) mod_bigint = int_to_bigint(mod_state.mod) return bigint_to_int(mulmont_quadratic(x_bigint, y_bigint, mod_bigint, mod_state.mod_inv_full, mod_state.r)) keywords: cost; int; memory; mod; modulus cache: eips-eip-6690.html plain text: eips-eip-6690.txt item: #732 of 3327 id: eips-eip-67 author: eips title: eips-eip-67 date: None words: 624 flesch: 49 summary: Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. Citation Please cite this document as: Alex Van de Sande (@alexvansande), ERC-67: URI Scheme with Metadata, Value and Bytecode [DRAFT], Ethereum Improvement Proposals, no. 67, February 2016. keywords: bytecode; ethereum cache: eips-eip-67.html plain text: eips-eip-67.txt item: #733 of 3327 id: eips-eip-6734 author: eips title: eips-eip-6734 date: None words: 3122 flesch: 34 summary: This property may be named differently by token standards e.g. granularity for ERC-777, type: integer, examples: However, these are not the only bridges that the tokens can be carried through, which means that bridges and token lists should be separated. keywords: comment; description; examples; title; token; type cache: eips-eip-6734.html plain text: eips-eip-6734.txt item: #734 of 3327 id: eips-eip-6735 author: eips title: eips-eip-6735 date: None words: 2279 flesch: 42 summary: Hence, the L2 WG of the EEA Communities Project managed by OASIS, an open-source initiative, intends for this document to establish an unambiguous and deterministic standard for EVM based address aliasing based on the concept of root → leaf where an address alias is derived based on the address on the origin chain and an offset which is an immutable characteristic of the origin chain. [R6] The offsetAliasfor Ethereum Mainnet as the primary anchor of EVM based chains MUST be 0x1111000000000000000000000000000000001111 due to current adoption of this offset by existing L2 solutions. keywords: address; chain; evm; requirements cache: eips-eip-6735.html plain text: eips-eip-6735.txt item: #735 of 3327 id: eips-eip-6780 author: eips title: eips-eip-6780 date: None words: 927 flesch: 50 summary: Handling the account creation and contract creation as two distinct and possibly separate events is needed for use cases such as counterfactual accounts. By allowing the SELFDESTRUCT to delete the account at contract creation time it will not result in stubs of counterfactually instantiated contracts that never had any on-chain state other than a balance prior to the contract creation. keywords: contract; selfdestruct cache: eips-eip-6780.html plain text: eips-eip-6780.txt item: #736 of 3327 id: eips-eip-6785 author: eips title: eips-eip-6785 date: None words: 1112 flesch: 44 summary: “ERC-6785 Metadata with utilities JSON Schema” : { title: Asset Metadata, type: object, properties: { name: { type: string, description: Identifies the asset to which this NFT represents }, description: { type: string, description: Describes the asset to which this NFT represents }, image: { type: string, description: A URI pointing to a resource with mime type image/* representing the asset to which this NFT represents. }, utilities: { type: object, required: [ type, description, t&c ], properties: { type: { type: string, description: Describes what type of utility this is }, description: { type: string, description: A brief description of the utility }, properties: { type: array, description: An array of possible properties describing the utility, defined as key-value pairs, items: { type: object } }, expiry: { type: number, description: The period of time for the validity of the utility, since the minting of the NFT. keywords: description; nft; utility cache: eips-eip-6785.html plain text: eips-eip-6785.txt item: #737 of 3327 id: eips-eip-6786 author: eips title: eips-eip-6786 date: None words: 795 flesch: 48 summary: The NFT id /// @return The amount of royalties paid for the NFT function getPaidRoyalties(address tokenAddress, uint256 tokenId) external view returns (uint256); } All functions defined as view MAY be implemented as pure or view Function payRoyalties MAY be implemented as public or external The event RoyaltiesPaid MUST be emitted when the payRoyalties function is called The supportsInterface function MUST return true when called with 0x253b27b0 Rationale The payment can be made in native coins, so it is easy to aggregate the amount of paid royalties. ERC-6786: Registry for royalties payment for NFTs Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: ERC ERC-6786: Registry for royalties payment for NFTs A registry used for paying royalties for any NFT with information about the creator Authors Otniel Nicola (@OT-kthd), Bogdan Popa (@BogdanKTHD) keywords: nft; royalties cache: eips-eip-6786.html plain text: eips-eip-6786.txt item: #738 of 3327 id: eips-eip-6787 author: eips title: eips-eip-6787 date: None words: 983 flesch: 39 summary: By introducing the two phase forced withdrawal function, we can protect users’ financial security while ensuring the security of the exchange’s assets. In conclusion, by adopting the two phase commit protocol and the two phase forced withdrawal function, we can effectively guard against malicious behaviors and ensure data consistency and security in distributed systems while ensuring user experience and financial security. keywords: function; token; withdrawal cache: eips-eip-6787.html plain text: eips-eip-6787.txt item: #739 of 3327 id: eips-eip-6789 author: eips title: eips-eip-6789 date: None words: 608 flesch: 32 summary: EIP-6789: Rename gas to mana Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Interface EIP-6789: Rename gas to mana This EIP suggests renaming gas to mana, as proposed by Vitalik Buterin in 2015 Authors Pascal Caversaccio (@pcaversaccio) Citation Please cite this document as: Pascal Caversaccio (@pcaversaccio), EIP-6789: Rename gas to mana keywords: gas; mana cache: eips-eip-6789.html plain text: eips-eip-6789.txt item: #740 of 3327 id: eips-eip-6800 author: eips title: eips-eip-6800 date: None words: 2184 flesch: 55 summary: This is a first step in a multi-phase transition to Ethereum exclusively relying on Verkle trees to store execution state. Verkle trees reduce witness sizes to ~200 bytes per account in the average case, allowing stateless client witnesses to be acceptably small. keywords: def; gas; return; tree; verkle cache: eips-eip-6800.html plain text: eips-eip-6800.txt item: #741 of 3327 id: eips-eip-6806 author: eips title: eips-eip-6806 date: None words: 807 flesch: 31 summary: This information can be useful for rewarding long-term holders, determining access to exclusive content, or even implementing specific business logic based on holding time. getHoldingInfo returns both holder and holdingTime so that some token owners (as decided by the implementation) can be ignored for the purposes of calculating holding time. keywords: erc-721; holding; time cache: eips-eip-6806.html plain text: eips-eip-6806.txt item: #742 of 3327 id: eips-eip-6808 author: eips title: eips-eip-6808 date: None words: 4374 flesch: 50 summary: Callers MUST NOT assume that false is never returned! interface IKBT20 { event AccountSecured(address _account, uint256 _amount); event AccountResetBinding(address _account); event SafeFallbackActivated(address _account); event AccountEnabledTransfer( address _account, uint256 _amount, uint256 _time, address _to, bool _allFunds ); event AccountEnabledApproval( address _account, uint256 _time, uint256 _numberOfTransfers ); event Ingress(address _account, uint256 _amount); event Egress(address _account, uint256 _amount); struct AccountHolderBindings { address firstWallet; address secondWallet; } struct FirstAccountBindings { address accountHolderWallet; address secondWallet; } struct SecondAccountBindings { address accountHolderWallet; address firstWallet; } struct TransferConditions { uint256 amount; uint256 time; address to; bool allFunds; } struct ApprovalConditions { uint256 time; uint256 numberOfTransfers; } function addBindings( address _keyWallet1, address _keyWallet2 ) external returns (bool); function getBindings( address _account ) external view returns (AccountHolderBindings memory); function resetBindings() external returns (bool); function safeFallback() external returns (bool); function allowTransfer( uint256 _amount, uint256 _time, address _to, bool _allFunds ) external returns (bool); function getTransferableFunds( address _account ) external view returns (TransferConditions memory); function allowApproval( uint256 _time, uint256 _numberOfTransfers ) external returns (bool); function getApprovalConditions( address account ) external view returns (ApprovalConditions memory); function getNumberOfTransfersAllowed( address _account, address _spender ) external view returns (uint256); function isSecureWallet(address _account) external view returns (bool); } Events AccountSecured event Emitted when the _account is securing his account by calling the addBindings function. event AccountEnabledTransfer(address _account, uint256 _amount, uint256 _time, address _to, bool _allFunds) AccountEnabledApproval event Emitted when _account has allowed approval, for the _time amount of block seconds and set a _numberOfTransfers allowed, by calling the allowApproval function. keywords: account; address; event; function; security; uint256 cache: eips-eip-6808.html plain text: eips-eip-6808.txt item: #743 of 3327 id: eips-eip-6809 author: eips title: eips-eip-6809 date: None words: 4422 flesch: 50 summary: uint256 time; address to; bool anyToken; } struct ApprovalConditions { uint256 time; uint256 numberOfTransfers; } function addBindings( address _keyWallet1, address _keyWallet2 ) external returns (bool); function getBindings( address _account ) external view returns (AccountHolderBindings memory); function resetBindings() external returns (bool); function safeFallback() external returns (bool); function allowTransfer( uint256 _tokenId, uint256 _time, address _to, bool _allTokens ) external returns (bool); function getTransferableFunds( address _account ) external view returns (TransferConditions memory); function allowApproval( uint256 _time, uint256 _numberOfTransfers ) external returns (bool); function getApprovalConditions( address account ) external view returns (ApprovalConditions memory); function getNumberOfTransfersAllowed( address _account, address _spender ) external view returns (uint256); function isSecureWallet(address _account) external returns (bool); function isSecureToken(uint256 _tokenId) interface IKBT721 { event AccountSecured(address indexed _account, uint256 _noOfTokens); event AccountResetBinding(address indexed _account); event SafeFallbackActivated(address indexed _account); event AccountEnabledTransfer( address _account, uint256 _tokenId, uint256 _time, address _to, bool _anyToken ); event AccountEnabledApproval( address _account, uint256 _time, uint256 _numberOfTransfers ); event Ingress(address _account, uint256 _tokenId); event Egress(address _account, uint256 _tokenId); struct AccountHolderBindings { address firstWallet; address secondWallet; } struct FirstAccountBindings { address accountHolderWallet; address secondWallet; } struct SecondAccountBindings { address accountHolderWallet; address firstWallet; } struct TransferConditions { uint256 tokenId; keywords: account; address; event; function; security; uint256 cache: eips-eip-6809.html plain text: eips-eip-6809.txt item: #744 of 3327 id: eips-eip-681 author: eips title: eips-eip-681 date: None words: 1281 flesch: 44 summary: Thus, payment request URLs could be delivered through a very broad, ever growing selection of channels. To prevent malicious redirection of payments using ENS, hexadecimal interpretation of Ethereum addresses must have precedence over ENS lookups. keywords: ethereum; payment; url cache: eips-eip-681.html plain text: eips-eip-681.txt item: #745 of 3327 id: eips-eip-6810 author: eips title: eips-eip-6810 date: None words: 692 flesch: 46 summary: Reverted transaction fees are refunded from this budget. There are many use cases for reverting settled transactions. keywords: budget; transaction cache: eips-eip-6810.html plain text: eips-eip-6810.txt item: #746 of 3327 id: eips-eip-6811 author: eips title: eips-eip-6811 date: None words: 449 flesch: 53 summary: It changes the time between blocks, the per-block validator reward, and the number of blocks per epoch. The per-block validator reward MUST be multiplied by 50 The number of blocks per epoch MUST be reduced from 4 to 2 Rationale The block gas limit is multiplied by fifty to compensate for the time between blocks being multiplied by fifty. keywords: blocks; ethereum cache: eips-eip-6811.html plain text: eips-eip-6811.txt item: #747 of 3327 id: eips-eip-6821 author: eips title: eips-eip-6821 date: None words: 382 flesch: 47 summary: Citation Please cite this document as: Qi Zhou (@qizhou), Qiang Zhu (@qzhodl), ERC-6821: Support ENS Name for Web3 URL [DRAFT], Ethereum Improvement Proposals, no. 6821, April 2023. Note that contentcontract text record may return an Ethereum address in hexadecimal with a 0x prefix or an ERC-3770 chain-specific address. keywords: address cache: eips-eip-6821.html plain text: eips-eip-6821.txt item: #748 of 3327 id: eips-eip-6823 author: eips title: eips-eip-6823 date: None words: 1399 flesch: 43 summary: ERC-6823: Token Mapping Slot Retrieval Extension Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: ERC ERC-6823: Token Mapping Slot Retrieval Extension Approach to enhance precision of off-chain transaction simulations by accessing mapping storage slot in ERC-20/721/1155 contracts. Available: https://eips.ethereum.org/EIPS/eip-6823. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: contract; slot; storage cache: eips-eip-6823.html plain text: eips-eip-6823.txt item: #749 of 3327 id: eips-eip-684 author: eips title: eips-eip-684 date: None words: 374 flesch: 41 summary: This prevents an attack consisting of deploying contract code and later changing the code arbitrarily by “creating” an account at that existing address. Revert creation in case of collision Revert contract creation if address already has code Authors Vitalik Buterin (@vbuterin), Renan Rodrigues de Souza (@RenanSouza2) Created 2023-03-20 Table of Contents Abstract Specification Rationale Backwards Compatibility Test Cases Security Considerations Copyright Abstract This EIP causes contract creation to throw an error when attempted at an address with pre-existing code. keywords: code; creation cache: eips-eip-684.html plain text: eips-eip-684.txt item: #750 of 3327 id: eips-eip-6860 author: eips title: eips-eip-6860 date: None words: 3227 flesch: 64 summary: fileExtension ] mPathEmpty = 0 segmentNz = 1*pchar ; as in RFC 3986 segmentNzNc = 1*( unreserved / pct-encoded / sub-delims / @ ) ; as in RFC 3986: non-zero-length segment without any colon : Support for manual mode relative URLs is similar to HTTP URLs : URLs relative to the current contract are allowed, both with an absolute path and a relative path. ERC-6860: Web3 URL to EVM Call Message Translation Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: ERC ERC-6860: Web3 URL to EVM Call Message Translation A translation of an HTTP-style Web3 URL to an EVM call message Authors Qi Zhou (@qizhou), Chao Pi (@pichaoqkc), Sam Wilson (@SamWilsn), keywords: address; bytes; hexdig; hexdig hexdig; mode cache: eips-eip-6860.html plain text: eips-eip-6860.txt item: #751 of 3327 id: eips-eip-6864 author: eips title: eips-eip-6864 date: None words: 1497 flesch: 35 summary: It also allows a way out should bugs or limitations discovered on ERC-6864 smart contract, or the user simply changes his or her mind. Multiple IERC-6864 implementations can be applied to the same base ERC-20 token, and ERC-6864 smart contracts can be nested. keywords: erc-20; erc-6864; tokens cache: eips-eip-6864.html plain text: eips-eip-6864.txt item: #752 of 3327 id: eips-eip-6865 author: eips title: eips-eip-6865 date: None words: 1389 flesch: 36 summary: Consequently, wallets can use a consistent and effective approach to EIP-712 message visualization. It identifies the needed implementation in case the protocol implements various EIP-712 implementations (name) or to revert if the domainHash belongs to a different protocol. keywords: chain; eip-712; message; protocols cache: eips-eip-6865.html plain text: eips-eip-6865.txt item: #753 of 3327 id: eips-eip-6873 author: eips title: eips-eip-6873 date: None words: 506 flesch: 47 summary: Restart a full-sync with preimage retention enabled Download the preimages as a file The second option is the only acceptable option in practice, as a full-sync requires the syncing machine to be offline for several days, and therefore should not be simultaneously imposed to the entire network. Reference Implementation All clients already implement preimage retention, at least as an option. keywords: preimage; verge cache: eips-eip-6873.html plain text: eips-eip-6873.txt item: #754 of 3327 id: eips-eip-6888 author: eips title: eips-eip-6888 date: None words: 827 flesch: 68 summary: b When opcode is SUB (0x03) and b > a When opcode is DIV (0x04) or MOD (0x06); and b == 0 When opcode is ADDMOD (0x08) and c == 0 ∨ ((a + b) / When opcode is SDIV (0x05) or SMOD (0x06); and b == 0 ∨ (a == INT_MIN ∧ b == -1) keywords: opcode cache: eips-eip-6888.html plain text: eips-eip-6888.txt item: #755 of 3327 id: eips-eip-689 author: eips title: eips-eip-689 date: None words: 407 flesch: 46 summary: Created 2017-08-15 Table of Contents Simple Summary Abstract Motivation Specification Rationale Backwards Compatibility Test Cases Implementation Copyright Simple Summary This EIP proposes to make contract creation fail on an account with nonempty code or non-zero nonce. To simplify the semantics, this EIP proposes that address collisions cause failures of contract creation. keywords: contract cache: eips-eip-689.html plain text: eips-eip-689.txt item: #756 of 3327 id: eips-eip-6900 author: eips title: eips-eip-6900 date: None words: 5261 flesch: 46 summary: Execution functions execute any custom logic allowed by the account. A plugin is a deployed smart contract that hosts any amount of the above three kinds of modular functions: execution functions, validation functions, or hooks. keywords: @param; account; data; execution; function; hooks; plugin; validation cache: eips-eip-6900.html plain text: eips-eip-6900.txt item: #757 of 3327 id: eips-eip-6909 author: eips title: eips-eip-6909 date: None words: 3046 flesch: 53 summary: balanceOf[receiver][id] += amount; emit Transfer(msg.sender, address(0), receiver, id, amount); } function _burn(address sender, uint256 id, uint256 amount) internal { // WARNING: important safety checks should precede calls to this method. isOperator[sender][msg.sender]) { require(allowance[sender][msg.sender][id] >= amount, insufficient allowance); allowance[sender][msg.sender][id] -= amount; } // -- snip -- } } contract ERC6909AllowancePrecedence { // -- snip -- function transferFrom(address sender, address receiver, uint256 id, uint256 amount) public { // check if allowance is sufficient first if (msg.sender != sender && allowance[sender][msg.sender][id] < amount) { require(isOperator[sender][msg.sender], insufficient allowance); } // ERROR: when allowance is insufficient, this panics due to arithmetic underflow, regardless of // whether the caller has operator permissions. keywords: address; spender; token; type; uint256 cache: eips-eip-6909.html plain text: eips-eip-6909.txt item: #758 of 3327 id: eips-eip-6913 author: eips title: eips-eip-6913 date: None words: 788 flesch: 43 summary: Account code not containing the SETCODE operation can be safely assumed to be immutable. Any execution scopes already executing replaced code, including the one that SETCODE, will continue executing the prior code. keywords: code; setcode cache: eips-eip-6913.html plain text: eips-eip-6913.txt item: #759 of 3327 id: eips-eip-6914 author: eips title: eips-eip-6914 date: None words: 762 flesch: 36 summary: EIP-6914: Reuse Withdrawn Validator Indices Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: Core EIP-6914: Reuse Withdrawn Validator Indices Reuse fully withdrawn and safe to reuse validator indices for new beacon chain deposits. This specification allows for the reuse of validator indices in the event that it is safe to do so, eliminating the concerns around the unbounded validator list growth. keywords: indices; validator cache: eips-eip-6914.html plain text: eips-eip-6914.txt item: #760 of 3327 id: eips-eip-6916 author: eips title: eips-eip-6916 date: None words: 2164 flesch: 39 summary: Client stops accepting/creating new blocks Shutdown client services running the network, e.g. p2p communication, beacon service, execution environment This feature should be implemented alongside Genesis even without further reset functions just to create a basic support which is always safe from forking Client calls a function which discards the current genesis, all chain or beacon data Clients already include db tools including for purging the database which could be used here It might be beneficial to include an additional flag, e.g. --retain-ephemeral-data, which would first export the existing data in a standard format before removing the database Client triggers the Genesis function (as defined above): Behaves like a regular client startup when genesis is not present New genesis is written into db and initialized Main network services are started again pointing to the updated genesis After the new genesis time is reached, the network starts again from the new genesis For a full reset implementation, clients should be able to perform the above actions without requiring manual restart, operating the network fully independently and with minimal downtime. Each network iteration is created by a specified function which deterministically generates genesis states. keywords: client; genesis; network; reset; testnet cache: eips-eip-6916.html plain text: eips-eip-6916.txt item: #761 of 3327 id: eips-eip-6944 author: eips title: eips-eip-6944 date: None words: 279 flesch: 21 summary: [DRAFT], Ethereum Improvement Proposals, no. 6944, April 2023. ERC-6944: ERC-5219 Resolve Mode Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: ERC ERC-6944: ERC-5219 Resolve Mode Adds an ERC-4804 resolveMode to support ERC-5219 requests Authors Gavin John (@Pandapip1), Qi Zhou (@qizhou) Created 2023-04-27 Discussion Link https://ethereum-magicians.org/t/erc-5219-resolve-mode/14088 Requires EIP-4804, EIP-5219 Table of Contents Abstract Specification Rationale Backwards Compatibility Reference Implementation Security Considerations Copyright Abstract This EIP adds a new ERC-4804 resolveMode to resolve ERC-5219 contract resource requests. keywords: erc-5219 cache: eips-eip-6944.html plain text: eips-eip-6944.txt item: #762 of 3327 id: eips-eip-695 author: eips title: eips-eip-695 date: None words: 477 flesch: 40 summary: Created 2017-08-21 Requires EIP-155 Table of Contents Simple Summary Abstract Motivation Specification eth_chainId Rationale Backwards Compatibility Security Considerations Implementation Reference Copyright Simple Summary Include eth_chainId method in eth_-namespaced JSON-RPC methods. Implementation Parity PR Geth PR Geth Classic PR Reference Return value QUANTITY adheres to standard JSON RPC hex value encoding, as documented in the Ethereum Wiki. keywords: eth_chainid; rpc cache: eips-eip-695.html plain text: eips-eip-695.txt item: #763 of 3327 id: eips-eip-6953 author: eips title: eips-eip-6953 date: None words: 728 flesch: 47 summary: EIP-6953: Network Upgrade Activation Triggers Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Informational EIP-6953: Network Upgrade Activation Triggers Exhaustive list of network upgrade activation mechanisms Authors Tim Beiko (@timbeiko) Created 2023-04-28 Requires EIP-2982, EIP-3675, EIP-6122 Table of Contents Abstract Motivation Specification Proof-of-Work Network Upgrades Beacon Chain Launch Beacon Chain Upgrades The Merge: Paris Upgrade Post-Merge Upgrades Rationale Blocks and Epochs Terminal Total Difficulty Timestamps Security Considerations Copyright Abstract This EIP outlines the various network upgrade activation triggers used on Ethereum over time, from the proof-of-work era to the first post-merge network upgrade, Shanghai/Capella, across both the execution and consensus layers. , network upgrades on Ethereum were triggered based on specific block numbers. keywords: activation; ethereum; upgrades cache: eips-eip-6953.html plain text: eips-eip-6953.txt item: #764 of 3327 id: eips-eip-6956 author: eips title: eips-eip-6956 date: None words: 6444 flesch: 36 summary: ANCHOR-TECHNOLOGY MUST ensure that the ANCHOR is inseparable from the ASSET (physically or otherwise) an ORACLE can establish PROOF-OF-CONTROL over the ASSET beyond reasonable doubt For physical ASSETS, additional Security considerations for Physical Assets MUST be taken into account ASSET refers to the “thing”, being it physical or digital, which is represented through NFTs according to the proposed standard. For physical ASSETS, CONTROL is typically verified by proofing physical proximity between a physical ASSET and an input device (for example a smartphone) used to specify the to address. keywords: @notice; @param; address; anchor; asset; attestation; chain; interface; nft; oracle; token cache: eips-eip-6956.html plain text: eips-eip-6956.txt item: #765 of 3327 id: eips-eip-6960 author: eips title: eips-eip-6960 date: None words: 2184 flesch: 51 summary: This EIP strives to overcome this limitation by proposing a token standard incorporating a dual-layer classification system, allowing for enhanced organization and management of tokens, especially in situations where additional sub-categorization of token types is necessary. */ function allowance( address owner, address operator, uint256 mainId, uint256 subId ) external view returns (uint256); /** * @notice Get the approval status of an `operator` to manage assets * @param owner is the address of the token owner * keywords: @param; address; token cache: eips-eip-6960.html plain text: eips-eip-6960.txt item: #766 of 3327 id: eips-eip-6963 author: eips title: eips-eip-6963 date: None words: 2650 flesch: 37 summary: EIP-6963: Multi Injected Provider Discovery Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: Interface EIP-6963: Multi Injected Provider Discovery Using window events to announce injected Wallet Providers Authors Pedro Gomes (@pedrouid), Kosala Hemachandra (@kvhnuke), Richard Moore (@ricmoo), Gregory Markou (@GregTheGreek), Kyle Den Hartog (@kdenhartog), Glitch (@glitch-txs), Jake Moxey (@jxom), Pierre Bertet (@bpierre), Darryl Yeo (@darrylyeo), Yaroslav Sergievsky (@everdimension) Created 2023-05-01 Requires EIP-1193 Table of Contents Abstract Motivation Specification Definitions Provider Info Provider Detail Window Events Rationale Interfaces Backwards Compatibility Reference Implementation Wallet Provider DApp implementation Security Considerations EIP-1193 Security considerations Prototype Pollution of Wallet Provider objects Wallet Imitation and Manipulation Prevent SVG Javascript Execution Prevent Wallet Fingerprinting Copyright Abstract An alternative discovery mechanism to window.ethereum for EIP-1193 providers which supports discovering multiple injected Wallet Providers in a web page using Javascript’s window events. This solution aims to foster fairer competition by reducing the barriers to entry for new Wallet Providers, along with enhancing the user experience on Ethereum networks. keywords: dapp; event; interface; object; provider; wallet cache: eips-eip-6963.html plain text: eips-eip-6963.txt item: #767 of 3327 id: eips-eip-6968 author: eips title: eips-eip-6968 date: None words: 929 flesch: 45 summary: This EIP does advocate that L2s could begin to experiment with Contract Secured Revenue as a means of: creating a new revenue stream for smart contract developers creating a new way of funding public goods creating incentives for developers to deploy their dapps on your network Specification Parameters Constant Value REVENUE_SHARE_QUOTIENT 5 Fee Mechanism The current EIP-1559 fee behavior is modified so that header.base_fee_per_gas * REVENUE_SHARE_QUOTIENT per gas is reallocated proportionally, based on gas used, to each contract executed during the transaction. Proportionally Ephemeral Revenue Recipient Mapping Security Considerations Increased Max Block Size/Complexity Copyright Abstract Contract Secured Revenue (CSR) allows smart contract developers to claim a percentage of all transaction fees paid by users when interacting with their smart contracts. keywords: contract; gas; revenue cache: eips-eip-6968.html plain text: eips-eip-6968.txt item: #768 of 3327 id: eips-eip-698 author: eips title: eips-eip-698 date: None words: 579 flesch: 47 summary: Value: 0x46 Mnemonic: BLOCKREWARD δ: 0 nothing removed from stack α:1 block reward added to stack Description: Get the block's reward emission GasCost: Gbase Where:µ's[0] ≡ IHR Rationale Contract Mining Pools For distributed consensus systems(staking pools and mining pools) ad hoc groups combine resources in order to reduce variance in payouts. Merge mined tokens Contracts could create tokens which could be variably ‘minted’ as a function of block reward by calling 0x46 Backwards Compatibility Currently deployed contracts No impact Current clients This EIP would be incompatible with currently deployed clients that are not able to handle 0x46 and would process all transactions and block containing the opcode as invalid. keywords: block; reward cache: eips-eip-698.html plain text: eips-eip-698.txt item: #769 of 3327 id: eips-eip-6981 author: eips title: eips-eip-6981 date: None words: 2628 flesch: 13 summary: The external service SHALL refer to an Account Registry Instance to retrieve the deterministic account address for a given salt. Users SHALL pass this message and signature to the service’s Account Registry Instance in a call to claimAccount to deploy and claim an Account Instance at the deterministic address. keywords: account; address; instance; registry; salt cache: eips-eip-6981.html plain text: eips-eip-6981.txt item: #770 of 3327 id: eips-eip-6982 author: eips title: eips-eip-6982 date: None words: 946 flesch: 55 summary: This proposal offers a more gas-efficient solution that only emits events upon contract deployment and status changes of individual tokens. Rationale This standard seeks to optimize gas consumption by minimizing the frequency of event emission. keywords: status; token cache: eips-eip-6982.html plain text: eips-eip-6982.txt item: #771 of 3327 id: eips-eip-6988 author: eips title: eips-eip-6988 date: None words: 406 flesch: 29 summary: Elected block proposer has not been slashed Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Citation Please cite this document as: Mikhail Kalinin (@mkalinin), EIP-6988: Elected block proposer has not been slashed [DRAFT], Ethereum Improvement Proposals, no. 6988, May 2023. keywords: block; proposer cache: eips-eip-6988.html plain text: eips-eip-6988.txt item: #772 of 3327 id: eips-eip-6997 author: eips title: eips-eip-6997 date: None words: 1669 flesch: 28 summary: ** * @dev Return the total amount of transfer validations created. ** * @dev Return the total amount of transfer validations created. keywords: @dev; function; transfer cache: eips-eip-6997.html plain text: eips-eip-6997.txt item: #773 of 3327 id: eips-eip-7 author: eips title: eips-eip-7 date: None words: 488 flesch: 50 summary: Rationale Propagating the sender and value from the parent scope to the child scope makes it much easier for a contract to store another address as a mutable source of code and ‘‘pass through’’ calls to it, as the child code would execute in essentially the same environment (except for reduced gas and increased callstack depth) as the parent. Unused gas is refunded as normal. keywords: gas; ~calldatasize cache: eips-eip-7.html plain text: eips-eip-7.txt item: #774 of 3327 id: eips-eip-7002 author: eips title: eips-eip-7002 date: None words: 3025 flesch: 32 summary: EIP-7002: Execution layer triggerable exits Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: Core EIP-7002: Execution layer triggerable exits Allows validators to trigger exits via their execution layer (0x01) withdrawal credentials Authors Danny Ryan (@djrtwo), Mikhail Kalinin (@mkalinin), Ansgar Dietrichs (@adietrichs), Hsiao-Wei Wang (@hwwhww) Created 2023-05-09 Discussion Link https://ethereum-magicians.org/t/eip-7002-execution-layer-triggerable-exits/14195 Table of Contents Abstract Motivation Specification Constants Configuration Execution layer Consensus layer Rationale Stateful precompile validator_pubkey field Exit message queue Utilizing CALL to return excess payment Rate limiting using exit fee TARGET_EXITS_PER_BLOCK configuration value Exit fee update rule Exits inside of the block Backwards Compatibility Security Considerations Impact on existing custody relationships Copyright Abstract Adds a new stateful precompile that allows validators to trigger exits to the beacon chain from their execution layer (0x01) withdrawal credentials. Citation Please cite this document as: Danny Ryan (@djrtwo), Mikhail Kalinin (@mkalinin), Ansgar Dietrichs (@adietrichs), Hsiao-Wei Wang (@hwwhww), EIP-7002: Execution layer triggerable exits [DRAFT], Ethereum Improvement Proposals, no. 7002, May 2023. keywords: block; execution; exit; layer; precompile; queue; withdrawal cache: eips-eip-7002.html plain text: eips-eip-7002.txt item: #775 of 3327 id: eips-eip-7007 author: eips title: eips-eip-7007 date: None words: 924 flesch: 48 summary: So (@socathie), Xiaohang Yu (@xhyumiracle), Huaizhe Xu (@HuaizheXu), Kartin  Created 2023-05-10 Discussion Link https://ethereum-magicians.org/t/eip-7007-zkml-aigc-nfts-an-erc-721-extension-interface-for-zkml-based-aigc-nfts/14216 Requires EIP-165, EIP-721 Table of Contents Abstract Motivation Specification Rationale Backwards Compatibility Test Cases Reference Implementation Security Considerations Copyright Abstract The Zero-Knowledge Machine Lerning (zkML) AI-Generated Content (AIGC) non-fungible token (NFT) standard is an extension of the ERC-721 token standard for AIGC. } } } Rationale TBD Backwards Compatibility This standard is backward compatible with the ERC-721 as it extends the existing functionality with new interfaces. keywords: aigc; prompt; standard cache: eips-eip-7007.html plain text: eips-eip-7007.txt item: #776 of 3327 id: eips-eip-7015 author: eips title: eips-eip-7015 date: None words: 1182 flesch: 26 summary: This approach ensures a more reliable and transparent method for identifying NFT creators, fostering trust among participants in the NFT ecosystem. The event is defined as follows: event CreatorAttribution( bytes32 structHash, string domainName, string version, address creator, bytes signature ); Note that although the chainId parameters is necessary for EIP-712 signatures, we omit the parameter from the event as it can be inferred through the transaction data. keywords: creator; nft; signature cache: eips-eip-7015.html plain text: eips-eip-7015.txt item: #777 of 3327 id: eips-eip-7039 author: eips title: eips-eip-7039 date: None words: 801 flesch: 52 summary: That means better support for pure web wallets, native executable wallets, and hardware wallets. EIP-7039: Scheme-Handler Discovery Option for Wallets Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: Interface EIP-7039: Scheme-Handler Discovery Option for Wallets Using custom protocol handlers to initiate connections between web pages and wallets. keywords: message; port cache: eips-eip-7039.html plain text: eips-eip-7039.txt item: #778 of 3327 id: eips-eip-7044 author: eips title: eips-eip-7044 date: None words: 630 flesch: 45 summary: Because voluntary exits can only be signed by the active key, such a relationship requires the exchange of signed exits ahead of time for an unbounded number of forks. Currently, signed voluntary exits are only valid for two upgrades. keywords: ethereum; exits cache: eips-eip-7044.html plain text: eips-eip-7044.txt item: #779 of 3327 id: eips-eip-7045 author: eips title: eips-eip-7045 date: None words: 666 flesch: 35 summary: The alternative considered path was to allow inclusion during the current and next epoch which means attestations created during the start of an epoch have more potential slots of inclusion than those at the end of the epoch. This specification thus increases the max inclusion slot for attestations in accordance with the learned security proof and confirmation rule needs. keywords: inclusion; slot cache: eips-eip-7045.html plain text: eips-eip-7045.txt item: #780 of 3327 id: eips-eip-7053 author: eips title: eips-eip-7053 date: None words: 1130 flesch: 30 summary: Existing systems encounter challenges due to the absence of a universal, interoperable identifier for digital media content. This will make it easier for users to find and trust digital media content, and it will also make it easier for systems to share and exchange information about this digital media content. keywords: commit; content; media cache: eips-eip-7053.html plain text: eips-eip-7053.txt item: #781 of 3327 id: eips-eip-706 author: eips title: eips-eip-706 date: None words: 1300 flesch: 61 summary: Extend protocol xyz to support compressed messages versus doing it at DEVp2p level: The proposal is to use the same limit (16MB) as the threshold for decompressed messages. keywords: err; message cache: eips-eip-706.html plain text: eips-eip-706.txt item: #782 of 3327 id: eips-eip-7066 author: eips title: eips-eip-7066 date: None words: 1682 flesch: 49 summary: Just as real estate owner can continue living in their mortgaged house, take personal loan or keep tenants to generate passive income, these functionalities should be available to NFT owners to bring more investors in NFT economy. Lack of composability: The market could benefit from increased liquidity if NFT owners had access to multiple financial tools, such as leveraging loans and renting out their assets for maximum returns. keywords: function; locker; nft; token cache: eips-eip-7066.html plain text: eips-eip-7066.txt item: #783 of 3327 id: eips-eip-7069 author: eips title: eips-eip-7069 date: None words: 1820 flesch: 58 summary: Transactions can still pass in arbitrary gas values and clever contract construction can still result in specific gas values being passed to specific calls. This creates an “escape hatch” in case gas observability needs to be restored to EOF contracts. keywords: gas; instructions; output; value cache: eips-eip-7069.html plain text: eips-eip-7069.txt item: #784 of 3327 id: eips-eip-7085 author: eips title: eips-eip-7085 date: None words: 1587 flesch: 23 summary: Existing NFT contracts and tokens will continue to function as they did before, and the new setRelationship and setAttribute functions will only be available to contracts that explicitly implement this EIP. It takes the following parameters: function setRelationship(uint256 _originalID, uint256 _derivativeID, uint256 _attribute) external; _originalID: the ID of the original NFT _derivativeID: the ID of the derivative NFT that refers to the original NFT _attribute: the quantifiable attribute for this relationship, which defaults to 1 if not specified When called, this function establishes a referring relationship between the two NFTs. keywords: attributes; function; nft cache: eips-eip-7085.html plain text: eips-eip-7085.txt item: #785 of 3327 id: eips-eip-7092 author: eips title: eips-eip-7092 date: None words: 3721 flesch: 45 summary: ** * @notice MUST be emitted when multiple bond tokens are transferred, issued or redeemed, with the exception being during contract creation * @param _from array of bondholders accounts * @param _to array of accounts to transfer bonds to * @param _amount array of amounts of bond tokens to be transferred * ** * @title ERC-7092 Financial Bonds Standard */ interface IERC7092 /** is ERC165 */ { // events /** * @notice MUST be emitted when bond tokens are transferred, issued or redeemed, except during contract creation * @param _from the account that owns bonds * @param _to the account that receives the bond keywords: @notice; @param; array; bond; tokens cache: eips-eip-7092.html plain text: eips-eip-7092.txt item: #786 of 3327 id: eips-eip-7093 author: eips title: eips-eip-7093 date: None words: 2539 flesch: 20 summary: ERC-7093: Social Recovery Interface Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: ERC ERC-7093: Social Recovery Interface Interfaces for social recovery account supporting various guardian types and customizable recovery policies. By entrusting account recovery to a network of selected individuals or entities, dubbed “Guardians,” users gain a safeguard against the risk of losing access to their digital assets. keywords: account; contract; function; guardians; identity; recovery; signature cache: eips-eip-7093.html plain text: eips-eip-7093.txt item: #787 of 3327 id: eips-eip-712 author: eips title: eips-eip-712 date: None words: 3086 flesch: 54 summary: If the struct type references other struct types (and these in turn reference even more struct types), then the set of referenced struct types is collected, sorted by name and appended to the encoding. The standard supports recursive struct types. keywords: address; data; definition; domain; signing; struct; type cache: eips-eip-712.html plain text: eips-eip-712.txt item: #788 of 3327 id: eips-eip-7144 author: eips title: eips-eip-7144 date: None words: 1550 flesch: 32 summary: ** * @dev Return the total amount of transfer validations created. ** * @dev Return the total amount of transfer validations created. keywords: @dev; address; transfer cache: eips-eip-7144.html plain text: eips-eip-7144.txt item: #789 of 3327 id: eips-eip-7160 author: eips title: eips-eip-7160 date: None words: 1570 flesch: 45 summary: Backwards Compatibility This extension is designed to be backward compatible with existing ERC-721 contracts. @inheritdoc ERC721.tokenURI function tokenURI(uint256 tokenId) public view virtual override returns (string memory) { _requireMinted(tokenId); uint256 index = _getTokenURIIndex(tokenId); string[] memory uris = _tokenURIs[tokenId]; string memory uri = uris[index]; // Revert if no URI is found for the token. keywords: function; metadata; token; uri cache: eips-eip-7160.html plain text: eips-eip-7160.txt item: #790 of 3327 id: eips-eip-7196 author: eips title: eips-eip-7196 date: None words: 727 flesch: 37 summary: ERC-7196: Simple token, Simplified ERC-20 Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: ERC ERC-7196: Simple token, Simplified ERC-20 Designed for smart contract wallets, this removes the transferFrom, approve, and allowance functions from ERC-20 tokens. This simplification aims to enhance security, reduce complexity, and improve efficiency, making the standard more suitable for smart contract wallet environments while maintaining essential functionalities. keywords: contract; erc-20; token cache: eips-eip-7196.html plain text: eips-eip-7196.txt item: #791 of 3327 id: eips-eip-7199 author: eips title: eips-eip-7199 date: None words: 237 flesch: 44 summary: Citation Please cite this document as: Zainan Victor Zhou (@xinbenlv), EIP-7199: Linter Scope [DRAFT], Ethereum Improvement Proposals, no. 7199, June 2023. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: ethereum cache: eips-eip-7199.html plain text: eips-eip-7199.txt item: #792 of 3327 id: eips-eip-7201 author: eips title: eips-eip-7201 date: None words: 1167 flesch: 48 summary: Authors Francisco Giordano (@frangio), Hadrien Croubois (@Amxx), Ernesto García (@ernestognw), Eric Lau (@ericglau) Created 2023-06-20 Table of Contents Abstract Motivation Specification Preliminaries @custom:storage-location Formula Rationale Naming Backwards Compatibility Reference Implementation Security Considerations Copyright Abstract We define the NatSpec annotation @custom:storage-location to document storage namespaces and their location in storage in Solidity or Vyper source code. Standardizing the location for storage layouts will allow these tools to correctly interpret contracts where these design patterns are used. keywords: location; solidity; storage cache: eips-eip-7201.html plain text: eips-eip-7201.txt item: #793 of 3327 id: eips-eip-7204 author: eips title: eips-eip-7204 date: None words: 1132 flesch: 38 summary: ERC-7204: Contract wallet management token Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: ERC ERC-7204: Contract wallet management token Focuses on fungible token management within smart contract wallets, offering enhanced transaction flexibility and security Authors Xiang (@wenzhenxiang), Ben77 (@ben2077), Mingshi S. (@newnewsms) Created 2023-06-21 Discussion Link https://ethereum-magicians.org/t/token-asset-management-interface-with-smart-contract-wallet/14759 Requires EIP-165 Table of Contents Abstract Motivation Specification Rationale Backwards Compatibility Security Considerations Copyright Abstract This proposal introduces a smart contract wallet-based approach for managing tokens, focusing on utilizing the programmable features of smart contract wallets for asset management. This approach seeks to enhance token management by utilizing the built-in features of smart contract wallets, thus offering a more adaptable, secure, and efficient method for managing token transactions. keywords: @param; address; token cache: eips-eip-7204.html plain text: eips-eip-7204.txt item: #794 of 3327 id: eips-eip-7208 author: eips title: eips-eip-7208 date: None words: 4953 flesch: 46 summary: This library implementation allows the creation of On-chain Data Containers that can store various data types, handle versions of data, and efficiently manage stored data. Clearing and Relocation: Several functions, such as clear(), wipe(), and moveData() are dedicated to clearing and relocating stored data. keywords: @param; data; function; mtid; odc; properties; property; token; uint256 cache: eips-eip-7208.html plain text: eips-eip-7208.txt item: #795 of 3327 id: eips-eip-721 author: eips title: eips-eip-721 date: None words: 4148 flesch: 51 summary: Additional data with no specified format /// @return `bytes4(keccak256(onERC721Received(address,address,uint256,bytes)))` /// unless throwing function onERC721Received(address _operator, address _from, uint256 _tokenId, bytes _data) external returns(bytes4); } The metadata extension is OPTIONAL for ERC-721 smart contracts (see “caveats”, below). } } } The enumeration extension is OPTIONAL for ERC-721 smart contracts (see “caveats”, below). keywords: @param; address; contract; function; interface; nft; nfts; owner; tokenid cache: eips-eip-721.html plain text: eips-eip-721.txt item: #796 of 3327 id: eips-eip-7212 author: eips title: eips-eip-7212 date: None words: 1738 flesch: 39 summary: Review Standards Track: Core EIP-7212: Precompile for secp256r1 Curve Support Proposal to add precompiled contract that performs signature verifications in the “secp256r1” elliptic curve. As of FORK_TIMESTAMP in the integrated EVM chain, add precompiled contract P256VERIFY for signature verifications in the “secp256r1” elliptic curve at address PRECOMPILED_ADDRESS in 0x0b. keywords: contract; curve; p256verify; secp256r1; signature cache: eips-eip-7212.html plain text: eips-eip-7212.txt item: #797 of 3327 id: eips-eip-7231 author: eips title: eips-eip-7231 date: None words: 1047 flesch: 36 summary: By incorporating the MultiIdentities schema into the metadata file, an authorized bond is established between user identity information and NFTs. To run them in terminal, you can use the following commands: cd ../assets/eip-7231 npm install npx hardhat test Reference Implementation ERC7231.sol Implementation: ERC7231.sol Security Considerations This EIP standard can comprehensively empower individuals to have ownership and control of their identities, wallets, and relevant data by themselves adding or removing the NFTs and identity bound information. keywords: binding; identity; nft cache: eips-eip-7231.html plain text: eips-eip-7231.txt item: #798 of 3327 id: eips-eip-7246 author: eips title: eips-eip-7246 date: None words: 1502 flesch: 37 summary: ** * @dev Emitted when the encumbrance of a `taker` to an `owner` is reduced by `amount`. */ event Release(address indexed owner, address indexed taker, uint amount); / */ function encumber(address taker, uint amount) external; /** * @dev Increases the amount of tokens that `owner` has encumbered to `taker` by `amount`. keywords: owner; taker; tokens; uint cache: eips-eip-7246.html plain text: eips-eip-7246.txt item: #799 of 3327 id: eips-eip-725 author: eips title: eips-eip-725 date: None words: 1743 flesch: 49 summary: The data stored in an ERC725Y smart contract is not only readable/writable by off-chain applications, but also by other smart contracts. They are a generic set of two standardized building blocks to be used in all forms of smart contracts. keywords: contract; data; function; memory cache: eips-eip-725.html plain text: eips-eip-725.txt item: #800 of 3327 id: eips-eip-7251 author: eips title: eips-eip-7251 date: None words: 1455 flesch: 36 summary: Large validators can consolidate to run fewer validators and thus fewer beacon nodes. This reduces the risk of consolidation for large validators. keywords: eth; layer; max_effective_balance; validators cache: eips-eip-7251.html plain text: eips-eip-7251.txt item: #801 of 3327 id: eips-eip-7254 author: eips title: eips-eip-7254 date: None words: 440 flesch: 31 summary: public view returns (uint256[] memory) getReward Gets and returns reward with list token reward. function getRewardPerShare(address token) public view returns (uint256) existsTokenReward Returns the status of token reward. keywords: returns; token cache: eips-eip-7254.html plain text: eips-eip-7254.txt item: #802 of 3327 id: eips-eip-7266 author: eips title: eips-eip-7266 date: None words: 459 flesch: 45 summary: Available: https://eips.ethereum.org/EIPS/eip-7266. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. Citation Please cite this document as: Pascal Caversaccio (@pcaversaccio), EIP-7266: Remove BLAKE2 compression precompile [DRAFT], Ethereum Improvement Proposals, no. 7266, July 2023. keywords: 0x09; precompile cache: eips-eip-7266.html plain text: eips-eip-7266.txt item: #803 of 3327 id: eips-eip-7303 author: eips title: eips-eip-7303 date: None words: 1396 flesch: 40 summary: These permissions can be realized as control tokens in this scheme. The tokens that represent privileges are called control tokens in this ERC. keywords: address; control; role; token cache: eips-eip-7303.html plain text: eips-eip-7303.txt item: #804 of 3327 id: eips-eip-7329 author: eips title: eips-eip-7329 date: None words: 2280 flesch: 53 summary: Security Considerations This proposal only addresses the EIP and ERC proposal process and is not expected to expose any new attack surfaces by virtue of its adoption. Danno Ferrin (@shemnon) Created 2023-07-13 Requires EIP-1 Table of Contents Abstract Motivation Specification Rationale Alternative: Working Groups Alternative: Specialized Editors Alternative: Pain unrelated to process divergences Alternative: Replace EIP Editors with AI Chatbots Alternatives are not Mutually Exclusive Objection: This splits the ethereum community Objection: This should be an EIP-1 proposal Objection: Structural changes to a repository and process changes do not need to be bundled. keywords: changes; community; eip; erc; process; repository cache: eips-eip-7329.html plain text: eips-eip-7329.txt item: #805 of 3327 id: eips-eip-7377 author: eips title: eips-eip-7377 date: None words: 1412 flesch: 52 summary: The only inhibitor at the moment is EIP-3607 which will cause migration transactions to be considered invalid if they come from an account with code already deployed. Although collisions between EOAs and contract accounts are considered unlikely and maybe impossible given today’s computing power, this EIP would make it common place for private keys to exist for contract accounts. keywords: code; contract; migration; transaction cache: eips-eip-7377.html plain text: eips-eip-7377.txt item: #806 of 3327 id: eips-eip-7378 author: eips title: eips-eip-7378 date: None words: 1318 flesch: 52 summary: Although a first price auction is a safe bet regarding TFMs, the Ethereum network chose to use EIP-1559 and burn transaction fees (perhaps for reasons other than game-theoretic ones). A higher smoothing factor means that the average responds more quickly to changes in block size (e.g., if $\alpha = 1$ the proposed formula degenerates to the existing rule). keywords: base; block; ethereum; fee cache: eips-eip-7378.html plain text: eips-eip-7378.txt item: #807 of 3327 id: eips-eip-7401 author: eips title: eips-eip-7401 date: None words: 4710 flesch: 62 summary: Child tokens of a given token can be fully managed by the parent token’s owner, but can be proposed by anyone. Having a token with multiple soulbound traits (child tokens), allows for numerous use cases. keywords: @param; address; array; child; parent; token cache: eips-eip-7401.html plain text: eips-eip-7401.txt item: #808 of 3327 id: eips-eip-7405 author: eips title: eips-eip-7405 date: None words: 1779 flesch: 25 summary: ** * @dev delete the migration data for the random operator * @param randomOperator public key (in address format) of the random operator * * **MUST** validate `migrationDataMap[randomOperator].account` is `msg.sender` */ function deleteMigrationData(address randomOperator) external; } Expected behavior When performing account migration (i.e., migrating an SCA from Wallet A to Wallet B), the following steps MUST be followed: While some proposed a modular approach for SCA accounts, it comes with higher implementation costs and specific prerequisites for wallet implementations. keywords: account; address; key; migration; wallet cache: eips-eip-7405.html plain text: eips-eip-7405.txt item: #809 of 3327 id: eips-eip-7406 author: eips title: eips-eip-7406 date: None words: 991 flesch: 31 summary: A map is used to record namespace existence mapping(byte32=>uint) namespaces; mapping(bytes32=>mapping(bytes32=>Record)) records; event NewOwner(bytes32 indexed namespace, bytes32 indexed key, address owner); event Transfer(bytes32 indexed namespace, bytes32 indexed key, address owner); event NewResolver(bytes32 indexed namespace, bytes32 indexed key, address resolver); event NewNamespace(bytes32 namespace) modifier only_owner(bytes32 namespace, bytes32 key) { if(records[namespace][key].owner ! records[namespace][key].resolver = resolver; } } Security Considerations The proposed multi-namespace registry introduces several security considerations due to its ability to manage various namespaces and access controls. keywords: address; key; namespace cache: eips-eip-7406.html plain text: eips-eip-7406.txt item: #810 of 3327 id: eips-eip-7409 author: eips title: eips-eip-7409 date: None words: 3499 flesch: 60 summary: * @param collection Address of the collection containing the token being checked for emoji count * @param tokenId ID of the token to check for emoji count * @param emoji Unicode identifier of the emoji * @return Number of emotes with the emoji on the token */ function emoteCountOf( address collection, uint256 tokenId, string memory emoji ) external view returns (uint256); / A boolean value indicating whether the `emoter` has used the `emoji` on the token (`true`) or not * (`false`) */ function hasEmoterUsedEmote( address emoter, address collection, uint256 tokenId, string memory emoji ) external view returns (bool); /** * @notice Used to get the information on whether the specified addresses have used specific emojis on specific * tokens. keywords: @param; address; emoji; emote; token cache: eips-eip-7409.html plain text: eips-eip-7409.txt item: #811 of 3327 id: eips-eip-7410 author: eips title: eips-eip-7410 date: None words: 623 flesch: 30 summary: This approach adds an extra layer of security and simplifies the process of decreasing allowances. * * Requirements: * - when `subtractedValue` is equal or higher than current allowance of spender the new allowance is set to 0. keywords: allowance; erc-20 cache: eips-eip-7410.html plain text: eips-eip-7410.txt item: #812 of 3327 id: eips-eip-7412 author: eips title: eips-eip-7412 date: None words: 1767 flesch: 35 summary: Cross-chain bridges are being developed where smart contract functions can write data to other chains. Available: https://eips.ethereum.org/EIPS/eip-7412. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: chain; contract; data; oracle; standard cache: eips-eip-7412.html plain text: eips-eip-7412.txt item: #813 of 3327 id: eips-eip-7417 author: eips title: eips-eip-7417 date: None words: 2033 flesch: 34 summary: == address(0)) { // Create ERC-20 wrapper if it doesn't exist. createERC20Wrapper(msg.sender); } // Mint ERC-20 wrapper tokens for the deposited ERC-223 token // if the ERC-20 wrapper didn't exist then it was just created in the above statement. Sends the _amount of ERC-223 wrapper tokens to the sender of the transaction. keywords: erc-20; erc-223; token cache: eips-eip-7417.html plain text: eips-eip-7417.txt item: #814 of 3327 id: eips-eip-7425 author: eips title: eips-eip-7425 date: None words: 1047 flesch: 37 summary: ** * @dev Issue new proposal * - MUST create new proposal number * - MUST account for amount withdrawn * - MUST emit proposals event * ** * @dev Amount deposited for shares of proposal by the user * - MUST be an ERC20 address * @param user address of user * @param proposal number of the proposal the user deposited */ function userDeposit(address user, uint256 proposal) external view returns(uint256); / keywords: @param; proposal; token cache: eips-eip-7425.html plain text: eips-eip-7425.txt item: #815 of 3327 id: eips-eip-7432 author: eips title: eips-eip-7432 date: None words: 2374 flesch: 58 summary: NFT roles can be deeply integrated with dApps to create a utility-sharing mechanism. function revokeRoleFrom( bytes32 _role, address _tokenAddress, uint256 _tokenId, address _revoker, address _grantee ) keywords: @param; address; role; user cache: eips-eip-7432.html plain text: eips-eip-7432.txt item: #816 of 3327 id: eips-eip-7439 author: eips title: eips-eip-7439 date: None words: 2098 flesch: 46 summary: This standard defines a framework that enables ticketing agents to utilize ERC-721 tokens as event tickets and restricts token transferability to prevent ticket touting. They still sold tickets for events at which resale was banned or did not yet own then obtained substantial illegal profits from speculative selling. keywords: signature; ticket; token; tokenstatus cache: eips-eip-7439.html plain text: eips-eip-7439.txt item: #817 of 3327 id: eips-eip-7441 author: eips title: eips-eip-7441 date: None words: 1056 flesch: 46 summary: EIP-7441: Upgrade block proposer election to Whisk Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: Core EIP-7441: Upgrade block proposer election to Whisk Allow elected block proposers to remain private until block publishing, to prevent DoS attacks Authors George Kadianakis (@asn-d6), Justin Drake (@JustinDrake), dapplion (@dapplion) Created 2023-09-01 Discussion Link https://ethereum-magicians.org/t/eip-7441-upgrade-block-proposer-election-to-whisk-ssle/15316 Table of Contents Abstract Motivation Specification Execution layer Consensus layer Rationale Fields per validator Identity binding Alternative: non-single secret election Alternative: network anonymity Backwards Compatibility Security Considerations Anonymity set RANDAO biasing Copyright Abstract Upgrades the block proposer election mechanism to Whisk, a single secret leader election (SSLE) protocol. Citation Please cite this document as: George Kadianakis (@asn-d6), Justin Drake (@JustinDrake), dapplion (@dapplion), EIP-7441: Upgrade block proposer election to Whisk [DRAFT], Ethereum Improvement Proposals, no. 7441, September 2023. keywords: block; election; proposer; whisk cache: eips-eip-7441.html plain text: eips-eip-7441.txt item: #818 of 3327 id: eips-eip-7444 author: eips title: eips-eip-7444 date: None words: 934 flesch: 34 summary: The timestamp of the time lock when it unlocks */ function getMaturity(bytes32 id) external view returns (uint256 maturity); } The maturity return parameter should be implemented in the Unix timestamp standard, which has been used widely in solidity. uint256 maturity; bytes32 lockId; } keywords: assets; maturity; time cache: eips-eip-7444.html plain text: eips-eip-7444.txt item: #819 of 3327 id: eips-eip-747 author: eips title: eips-eip-747 date: None words: 1246 flesch: 55 summary: Automatically listing assets makes assets into a sort of spam mail: Users suddenly see new assets that they don’t care about in their wallet. Defining the global identifiers for different asset types is beyond the scope of this EIP. keywords: address; wallet; wallet_watchasset cache: eips-eip-747.html plain text: eips-eip-747.txt item: #820 of 3327 id: eips-eip-7480 author: eips title: eips-eip-7480 date: None words: 764 flesch: 50 summary: Data section may contain anything, e.g. compiler’s metadata, but to make it useful for smart contracts, EVM has to have instructions that allow to read from data section. EIP-7480: EOF - Data section access instructions Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: Core EIP-7480: EOF - Data section access instructions Instructions to read data section of EOF container Authors Andrei Maiboroda (@gumb0), Alex Beregszaszi (@axic), Paweł Bylica (@chfast) Created 2023-08-11 Discussion Link https://ethereum-magicians.org/t/eip-7480-eof-data-instructions/15414 Requires EIP-3540, EIP-3670 Table of Contents Abstract Motivation Specification DATALOAD DATALOADN DATASIZE DATACOPY Code Validation Rationale Zero-padding on out of bounds access Backwards Compatibility Security Considerations Copyright Abstract Four new instructions are introduced, that allow to read EOF container’s data section: DATALOAD loads 32-byte word to stack, DATALOADN loads 32-byte word to stack where the word is addressed by a static immediate argument, DATASIZE loads data section size and DATACOPY copies a segment of data section to memory. keywords: data; section cache: eips-eip-7480.html plain text: eips-eip-7480.txt item: #821 of 3327 id: eips-eip-7484 author: eips title: eips-eip-7484 date: None words: 1944 flesch: 34 summary: [] memory attesters, uint256 threshold) internal { // Check list of module attestations on Registry registry.checkN(module, attesters, threshold); } } Account.sol Note: This is a specific example that complies to the Specification above, but this implementation is not binding. It also provides a reference implementation of a Singleton Module Registry. keywords: accounts; attestation; module; registry cache: eips-eip-7484.html plain text: eips-eip-7484.txt item: #822 of 3327 id: eips-eip-7495 author: eips title: eips-eip-7495 date: None words: 1663 flesch: 45 summary: Stability guarantees The serialization and merkleization of a StableContainer[N] remains stable as long as: The maximum capacity N does not change The order of fields does not change New fields are always added to the end Required fields remain required T, or become an Optional[T] Optional fields remain Optional[T], or become a required T When an optional field becomes required, existing messages still have stable serialization and merkleization, but will be rejected on deserialization if not present. To avoid restricting design space, the scheme has to support extension with new fields, obsolescence of old fields, and new combinations of existing fields. keywords: fields; serialization; ssz; stablecontainer[n cache: eips-eip-7495.html plain text: eips-eip-7495.txt item: #823 of 3327 id: eips-eip-7496 author: eips title: eips-eip-7496 date: None words: 1903 flesch: 59 summary: Metadata Trait metadata is an optional way to define additional information about which traits are present in a contract, how to parse and display trait values, and permissions for setting trait values. If the valueMappings object is defined, the valueMappings object MUST be a mapping of bytes32 values to string or unset null values. keywords: object; trait; value; valuemappings cache: eips-eip-7496.html plain text: eips-eip-7496.txt item: #824 of 3327 id: eips-eip-7498 author: eips title: eips-eip-7498 date: None words: 1819 flesch: 42 summary: Events */ event CampaignUpdated(uint256 indexed campaignId, Campaign campaign, string metadataURI); event Redemption(uint256 indexed campaignId, uint256 requirementsIndex, bytes32 redemptionHash, uint256 * Setters */ function createCampaign(Campaign calldata campaign, string calldata metadataURI) external returns (uint256 campaignId); function updateCampaign(uint256 campaignId, Campaign calldata campaign, string calldata metadataURI) external; function redeem(uint256 keywords: campaign; string; token; type; uint256 cache: eips-eip-7498.html plain text: eips-eip-7498.txt item: #825 of 3327 id: eips-eip-7503 author: eips title: eips-eip-7503 date: None words: 1143 flesch: 52 summary: Rationale Cryptocurrency mixers like TornadoCash can successfully obfuscate Ethereum transactions, but it’s easy for the governments to ban usage of them. EIP-7503: Zero-Knowledge Wormholes Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Review Standards Track: Core EIP-7503: Zero-Knowledge Wormholes Enable minting of secretly burnt Ethers as a native privacy solution for Ethereum Authors Keyvan Kambakhsh (@keyvank), Hamid Bateni (@irnb), Amir Kahoori , Nobitex Labs  Created 2023-08-14 keywords: address; ethereum; hash cache: eips-eip-7503.html plain text: eips-eip-7503.txt item: #826 of 3327 id: eips-eip-7506 author: eips title: eips-eip-7506 date: None words: 3031 flesch: 42 summary: A namespace contains hint lists for different use cases. hint list: A hint list is identified by a unique value that contains a number of hint keys that resolve to hint values. This method takes advantage of the ENS domain’s established credibility to make it easier to find a reliable hint registry contract, as well as the appropriate namespace and hint list customized for particular ecosystem needs. keywords: bytes32; calldata; hint; list; namespace; signature cache: eips-eip-7506.html plain text: eips-eip-7506.txt item: #827 of 3327 id: eips-eip-7507 author: eips title: eips-eip-7507 date: None words: 816 flesch: 23 summary: The user expires for this NFT function userExpires(uint256 tokenId, address user) external view returns(uint256); /// @notice Set the user expires of an NFT /// @param tokenId The NFT to set the user expires for /// @param user The user to set the expires for /// @param expires The user could use the NFT before expires in UNIX timestamp function setUser(uint256 tokenId, address user, uint64 expires) external; } Rationale This standard complements ERC-4907 to support multi-user feature. ERC721(name, symbol) {} function supportsInterface( bytes4 interfaceId ) public view virtual override returns (bool) { return interfaceId == type(IERC7507).interfaceId || super.supportsInterface(interfaceId); } function userExpires( uint256 tokenId, address user ) public view virtual override returns(uint256) { require(_exists(tokenId), ERC7507: query for nonexistent token); return _expires[tokenId][user]; } function setUser( uint256 tokenId, address user, uint64 expires ) public virtual override { require(_isApprovedOrOwner(_msgSender(), tokenId), ERC7507: caller is not owner or approved); _ keywords: expires; user cache: eips-eip-7507.html plain text: eips-eip-7507.txt item: #828 of 3327 id: eips-eip-7508 author: eips title: eips-eip-7508 date: None words: 6099 flesch: 52 summary: An array of address type attribute keys to retrieve * An array of string type attribute keys to retrieve * @param uintKeys An array of uint type attribute keys to retrieve * @param boolKeys An array of bool type attribute keys to retrieve * @param addressKeys keywords: @param; @param collection; @param tokenid; @param value; address; attribute; key cache: eips-eip-7508.html plain text: eips-eip-7508.txt item: #829 of 3327 id: eips-eip-7509 author: eips title: eips-eip-7509 date: None words: 2185 flesch: 55 summary: System: the logic for operating entity components. World contracts are containers for entities, component contracts, and system contracts. keywords: @param; component; contract; entity cache: eips-eip-7509.html plain text: eips-eip-7509.txt item: #830 of 3327 id: eips-eip-7510 author: eips title: eips-eip-7510 date: None words: 1111 flesch: 14 summary: .to.be.revertedWith(ERC7510: caller is not owner or approved); }); it(Should correctly query token without parents, async function () { const { contract } = await loadFixture(deployContractFixture); expect(await contract.parentTokensOf(TOKEN_ID)).to.have.lengthOf(0); expect(await contract.isParentToken(TOKEN_ID, PARENT_1_TOKEN)).to.equal(false); }); it(Should set parent tokens and then update, async function () { const { contract, owner } = await loadFixture(deployContractFixture); await contract.connect(owner).setParentTokens(TOKEN_ID, [PARENT_1_TOKEN]); let parentTokens = await contract.parentTokensOf(TOKEN_ID); expect(parentTokens).to.have.lengthOf(1); expect(parentTokens[0].collection).to.equal(PARENT_1_COLLECTION); expect(parentTokens[0].id).to.equal(PARENT_1_ID); expect(await contract.isParentToken(TOKEN_ID, PARENT_1_TOKEN)).to.equal(true); expect(await contract.isParentToken(TOKEN_ID, PARENT_2_TOKEN)).to.equal(false); await contract.connect(owner).setParentTokens(TOKEN_ID, [PARENT_2_TOKEN]); parentTokens = await contract.parentTokensOf(TOKEN_ID); expect(parentTokens).to.have.lengthOf(1); expect(parentTokens[0].collection).to.equal(PARENT_2_COLLECTION); expect(parentTokens[0].id).to.equal(PARENT_2_ID); expect(await contract.isParentToken(TOKEN_ID, PARENT_1_TOKEN)).to.equal(false); expect(await contract.isParentToken(TOKEN_ID, PARENT_2_TOKEN)).to.equal(true); }); it(Should burn and clear parent tokens, async function () { const { contract, owner } The NFT to get the parent tokens for /// @return An array of parent tokens for this NFT function parentTokensOf(uint256 tokenId) external view returns (Token[] memory); /// keywords: await; nft; parent cache: eips-eip-7510.html plain text: eips-eip-7510.txt item: #831 of 3327 id: eips-eip-7511 author: eips title: eips-eip-7511 date: None words: 1272 flesch: 57 summary: Here are the security considerations when using minimal proxy contracts: Backwards Compatibility Because the new minimal proxy contract uses PUSH0 opcode, it can only be deployed after the Shanghai Upgrade. keywords: contract; push0 cache: eips-eip-7511.html plain text: eips-eip-7511.txt item: #832 of 3327 id: eips-eip-7512 author: eips title: eips-eip-7512 date: None words: 1846 flesch: 39 summary: They are commonly used to increase the security of smart contracts and ensure that they follow best practices as well as correctly implement standards such ERC-20, ERC-721, and similar ERCs. Many essential parts of the blockchain ecosystem are facilitated by the usage of smart contracts. keywords: audit; auditor; contract; erc; token cache: eips-eip-7512.html plain text: eips-eip-7512.txt item: #833 of 3327 id: eips-eip-7513 author: eips title: eips-eip-7513 date: None words: 1866 flesch: 37 summary: Authors MJ Tseng (@TsengMJ) , Clay (@Clay2018) , Jeffery.c , Johnny.c  Created 2023-09-06 Discussion Link https://ethereum-magicians.org/t/nft-bound-modularized-contract/15696 Requires EIP-165, EIP-1155 Table of Contents Abstract Motivation Usability with Security IA-NFT as Native On-chain Asset Interaction Abstraction for the Intent Abstraction Specification Overview Smart-NFT Interface Smart-Manager Interface Intent-Proxy Interface Rationale Why using ERC-1155 Verifier Copyright infringement issue Backwards Compatibility Reference Implementation Security Considerations Malicious Validator Unexpected Verification Error Copyright Abstract Smart NFT is the fusion of Smart Contract and NFT. VERIFIED: Represents Smart-NFTs that have been registered with the Smart-Manager and have successfully passed the verification process, indicating they are safe to use. keywords: code; interface; manager; nft; nfts cache: eips-eip-7513.html plain text: eips-eip-7513.txt item: #834 of 3327 id: eips-eip-7514 author: eips title: eips-eip-7514 date: None words: 881 flesch: 54 summary: In light of this, it is worth discussing whether Beacon chain validator rewards should be adjusted to better match today’s reality, potentially to discourage staking past a certain point. Citation Please cite this document as: dapplion (@dapplion), Tim Beiko (@timbeiko), EIP-7514: Add Max Epoch Churn Limit [DRAFT], Ethereum Improvement Proposals, no. 7514, September 2023. keywords: churn; eth; staked cache: eips-eip-7514.html plain text: eips-eip-7514.txt item: #835 of 3327 id: eips-eip-7516 author: eips title: eips-eip-7516 date: None words: 449 flesch: 53 summary: Blob gas futures can be implemented based on it which allows for blob users to smooth out data blob costs. This feature enables blob-data users to programmatically account for the blob gas price, eg: Allow rollup contracts to trustlessly account for blob data usage costs. keywords: blob; instruction cache: eips-eip-7516.html plain text: eips-eip-7516.txt item: #836 of 3327 id: eips-eip-7517 author: eips title: eips-eip-7517 date: None words: 1495 flesch: 26 summary: The introduction of the dataMiningPreference property in digital asset metadata covers the considerations including: Accessibility: A clear and easily accessible method with human-readibility and machine-readibility for digital asset creators and license owners to express their preferences for how their assets are used in data mining and AI/ML training workflows. Motivation As digital assets become increasingly utilized in AI and machine learning workflows, it is critical that the rights and preferences of asset creators and license owners are respected, and the AI/ML creators can check and collect data easily and safely. keywords: asset; data; dataminingpreference cache: eips-eip-7517.html plain text: eips-eip-7517.txt item: #837 of 3327 id: eips-eip-7519 author: eips title: eips-eip-7519 date: None words: 1113 flesch: 44 summary: Mnemonic Op Input Output SCREDIT 0xTBD 2 0 SDEBIT 0xTBD+1 2 0 SCREDIT SCREDIT: slot, value Description Adds value to the value stored in contract storage slot. Execution Not valid python, not suitable for EELS yet slot = evm_stack.pop() value = evm_stack.pop() storage_value = read_contract_storage(slot) storage_value = storage_value + value if storage_value >= 2**256 : raise Exception(scredit overflow) write_contract_storage(storage_value) SDEBIT SDEBIT: slot, value Description Subtracts value to the value stored in contract storage slot. keywords: gas; storage; value cache: eips-eip-7519.html plain text: eips-eip-7519.txt item: #838 of 3327 id: eips-eip-7521 author: eips title: eips-eip-7521 date: None words: 3334 flesch: 40 summary: Registering new entry point intent standards The entry point’s registerIntentStandard function must allow for permissionless registration of new intent standard contracts. If the intent standard contract returns true, then the entry point registers it and gives it a standard ID which is unique to the intent standard contract, entry point contract and chain ID. keywords: contract; entry; function; intent; point; standard cache: eips-eip-7521.html plain text: eips-eip-7521.txt item: #839 of 3327 id: eips-eip-7522 author: eips title: eips-eip-7522 date: None words: 1132 flesch: 48 summary: Users can link their ERC-4337 accounts with OIDC identities and authorize an OIDC verifier to validate user operations by verifying the linked OIDC identity on-chain. Now one can link its ERC-4337 account with an OIDC identity and use the OpenID ZK verifier to validate user operations. keywords: oidc; proof; user cache: eips-eip-7522.html plain text: eips-eip-7522.txt item: #840 of 3327 id: eips-eip-7523 author: eips title: eips-eip-7523 date: None words: 646 flesch: 53 summary: By prohibiting empty accounts on post-merge networks, this EIP frees designers and implementors of Ethereum and related blockchains from the burden of having to consider them going forward. Any testcase involving post-merge empty accounts is invalid. keywords: accounts; ethereum cache: eips-eip-7523.html plain text: eips-eip-7523.txt item: #841 of 3327 id: eips-eip-7527 author: eips title: eips-eip-7527 date: None words: 2776 flesch: 43 summary: == IERC721Enumerable(_app).totalSupply(), ERC7527Agency: Reentrancy); emit Wrap(to, id_, premium, mintFee); return id_; } function getStrategy() public pure override returns (address app, Asset memory asset, bytes memory attributeData) { uint256 offset = _getImmutableArgsOffset(); address currency; uint256 premium; address payable awardFeeRecipient; uint16 mintFeePercent; uint16 burnFeePercent; assembly { app := shr(0x60, calldataload(add(offset, 0))) currency := shr(0x60, calldataload(add(offset, 20))) premium := calldataload(add(offset, 40)) awardFeeRecipient := shr(0x60, calldataload(add(offset, 72))) mintFeePercent := shr(0xf0, calldataload(add(offset, 92))) burnFeePercent := shr(0xf0, calldataload(add(offset, 94))) } asset = Asset(currency, premium, awardFeeRecipient, mintFeePercent, burnFeePercent); attributeData = ; } function getUnwrapOracle(bytes memory data) public pure override returns (uint256 premium, uint256 fee) { uint256 input = abi.decode(data, (uint256)); (, Asset memory _asset,) = getStrategy(); premium = _asset.premium + input * _asset.premium / 100; fee = premium * _ asset.burnFeePercent / 10000; } function getWrapOracle(bytes memory data) public pure override returns (uint256 premium, uint256 fee) { uint256 input = abi.decode(data, (uint256)); (, Asset memory _asset,) = getStrategy(); premium = _asset.premium + input * _asset.premium / 100; fee = premium * _asset.mintFeePercent / 10000; } function _transfer(address currency, address recipient, uint256 premium) internal { if (currency == address(0)) keywords: @param; address; data; function; token; uint256 cache: eips-eip-7527.html plain text: eips-eip-7527.txt item: #842 of 3327 id: eips-eip-7528 author: eips title: eips-eip-7528 date: None words: 675 flesch: 50 summary: In addition, protocols might create separate events for handling ETH native cases and ERC-20 cases. In other cases, protocols will use native ETH due to gas considerations, or the requirement of using native ETH such as in the case of a Liquid Staking Token (LST). keywords: erc-20; eth cache: eips-eip-7528.html plain text: eips-eip-7528.txt item: #843 of 3327 id: eips-eip-7529 author: eips title: eips-eip-7529 date: None words: 1948 flesch: 37 summary: This standard can be used as a straightforward technique to mitigate smart contract authorship spoofing and enhance the discoverability of smart contracts through standard web search mechanisms. Motivation As mainstream businesses begin to adopt public blockchain and digital asset technologies more rapidly, there is a growing need for a discovery/search mechanism (compatible with conventional web technologies) of smart contracts associated with a known business domain as well as reasonable assurance that the smart contract does indeed belong to the business owner of the DNS domain. keywords: contract; dns; domain; etld+1; txt cache: eips-eip-7529.html plain text: eips-eip-7529.txt item: #844 of 3327 id: eips-eip-7531 author: eips title: eips-eip-7531 date: None words: 1468 flesch: 44 summary: Technical Advantages: Preservation of Utility: This approach allows NFT owners to leverage their assets in staking pools or other smart contracts without losing access to the benefits associated with the NFT. Enhanced Flexibility: The method offers greater flexibility for NFT owners, allowing them to participate in staking and other DeFi activities without relinquishing the intrinsic benefits of their NFTs. keywords: event; ownership; token cache: eips-eip-7531.html plain text: eips-eip-7531.txt item: #845 of 3327 id: eips-eip-7533 author: eips title: eips-eip-7533 date: None words: 2938 flesch: 46 summary: To attract cross-chain bridge projects to participate, aside from reducing the number of bridges and gas cost, the use of the Hash MerkleTree data structure in the SendPort ensures that adding cross-chain messages does not increase the overhead of the bridges. It replaces the method of pushing message to multiple chains with a method of pulling messages from multiple chains, significantly reducing the number of cross-chain bridges and gas cost, as more cross-chain bridge projects are built on PCP, the overall security increases. keywords: bytes32; chain; cross; package; uint cache: eips-eip-7533.html plain text: eips-eip-7533.txt item: #846 of 3327 id: eips-eip-7535 author: eips title: eips-eip-7535 date: None words: 1047 flesch: 39 summary: Wrapped ETH Smart contract systems which implement ERC-4626 should consider only supporting ERC-20 underlying assets, and default to using a Wrapped ETH ERC-20 instead of implementing ERC-7535 for handling ETH. Any ERC-20 transferFrom approval flows for asset are not implemented deposit and mint have state mutability payable deposit uses msg.value as the primary input and MAY ignore assets Methods asset MUST return 0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE per ERC-7528. - name: asset type: function stateMutability: view inputs: [] outputs: - name: assetTokenAddress type: address deposit Mints shares Vault shares to receiver by depositing exactly msg.value of Ether. keywords: assets; erc-4626; eth cache: eips-eip-7535.html plain text: eips-eip-7535.txt item: #847 of 3327 id: eips-eip-7538 author: eips title: eips-eip-7538 date: None words: 430 flesch: 33 summary: Citation Please cite this document as: Gavin John (@Pandapip1), ERC-7538: Multiplicative Tokens [DRAFT], Ethereum Improvement Proposals, no. 7538, October 2023. Decimals are no longer supported **/ decimals: never; } Token contracts MUST NOT have a method named decimals if a multiplier is used. keywords: ethereum; multiplier cache: eips-eip-7538.html plain text: eips-eip-7538.txt item: #848 of 3327 id: eips-eip-7540 author: eips title: eips-eip-7540 date: None words: 3811 flesch: 46 summary: asynchronous deposit Vault: a Vault that implements asynchronous Requests for deposit flows asynchronous redemption Vault: a Vault that implements asynchronous redemption flows fully asynchronous Vault: a Vault that implements asynchronous Requests for both deposit and redemption Request Flows ERC-7540 Vaults MUST implement one or both of asynchronous deposit and redemption Request flows. Likewise yield on redemption Requests can accrue or not, and the exchange rate of any Request may be fixed or variable depending on the implementation. Not allowing short-circuiting for claims If claims can short circuit, this creates ambiguity for integrators and complicates the interface with overloaded behavior on Request functions. keywords: assets; owner; request; shares; state; type; vault cache: eips-eip-7540.html plain text: eips-eip-7540.txt item: #849 of 3327 id: eips-eip-7542 author: eips title: eips-eip-7542 date: None words: 779 flesch: 43 summary: EIP-7542: eth/69 - available-blocks-extended protocol Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: Networking EIP-7542: eth/69 - available-blocks-extended protocol Adds more info in the handshake about available block range and adds message types to request block ranges and the send them Authors Ahmad Bitar (@smartprogrammer93)  Created 2023-10-21 Discussion Link https://ethereum-magicians.org/t/eip-eth-69-available-blocks-extended-protocol-handshake/16188 Requires EIP-5793 Table of Contents Abstract Motivation Specification Rationale Backwards Compatibility Test Cases Security Considerations Copyright Abstract The purpose of this EIP is to introduce a method that allows an Ethereum node to communicate the range of blocks it has available. Afterwards, they can use the RequestBlockRange and SendBlockRange messages to keep informed about peer block range changes. keywords: block; range cache: eips-eip-7542.html plain text: eips-eip-7542.txt item: #850 of 3327 id: eips-eip-7545 author: eips title: eips-eip-7545 date: None words: 613 flesch: 37 summary: This introduces a burden on several application, e.g. bridges, as they will potentially need to support proof formats designed after the release of the bridge contract. Pseudo-code behavior of the precompile: def proof_verification_precompile(input): version = input[0] state_root = input[1:33] proof_data = input[33:33+proof_data_size] if version == 0: proof = deserialize_proof(state_root, proof_data) return verify_mpt_multiproof(proof) if version == 1: proof = deserialize_proof(state_root, proof_data) return verify_pcs_multiproof(proof) return 0 If version is 0 then the proof is expected to follow the SSZ format described in “the verge” proposal in the consensus spec. keywords: ethereum; proof cache: eips-eip-7545.html plain text: eips-eip-7545.txt item: #851 of 3327 id: eips-eip-7547 author: eips title: eips-eip-7547 date: None words: 1689 flesch: 41 summary: New RPC request and response network for inclusion list: Establish a new network for sending and receiving inclusion lists. EIP-7547: Inclusion lists Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: Core EIP-7547: Inclusion lists Add an inclusion list mechanism to allow forced transaction inclusion. keywords: block; inclusion; list; slot; transactions cache: eips-eip-7547.html plain text: eips-eip-7547.txt item: #852 of 3327 id: eips-eip-7548 author: eips title: eips-eip-7548 date: None words: 1335 flesch: 50 summary: ERC-7548: Open IP Protocol built on NFTs Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: ERC ERC-7548: Open IP Protocol built on NFTs A protocol that enables users to remix NFTs and generate new NFT derivative works, while their relationships can be traced on chain. function getComponents( uint256 comboId ) external view returns (Component[] memory); } License Module By default, users can only remix multiple NFTs they own to create new NFT derivative works. keywords: @param; module; nfts cache: eips-eip-7548.html plain text: eips-eip-7548.txt item: #853 of 3327 id: eips-eip-7549 author: eips title: eips-eip-7549 date: None words: 569 flesch: 39 summary: EIP-7549: Move committee index outside Attestation Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: Core EIP-7549: Move committee index outside Attestation Move committee index outside of the signed Attestation message Authors dapplion (@dapplion) Created 2023-11-01 Discussion Link https://ethereum-magicians.org/t/eip-7549-move-committee-index-outside-attestation/16390 Table of Contents Abstract Motivation Specification Execution layer Consensus layer Rationale Deprecation strategy Backwards Compatibility Security Considerations Copyright Abstract Move the committee index field outside of the signed Attestation message to allow aggregation of equal consensus votes. FFG vote (source, target) Committee index (index) Signing over the 3rd item causes tuples of equal votes to produce different signing roots. keywords: attestation; index cache: eips-eip-7549.html plain text: eips-eip-7549.txt item: #854 of 3327 id: eips-eip-7561 author: eips title: eips-eip-7561 date: None words: 840 flesch: 38 summary: Compliant contracts MUST implement the following interface: pragma solidity ^0.8.20; /** * @title ERC7561 Simple NFT interface * @dev See https://ercs.ethereum.org/ERCS/erc-7561 */ interface IERC7561 { /** * @notice Used to notify transfer NFT. The NFT to transfer */ function transferFrom(address from, address to, uint256 tokenId) external; } Rationale The proposal is to simplify NFT standards by removing approve, setApprovalForAll, getApproved, isApprovedForAll and safeTransferFrom functions. keywords: address; nft cache: eips-eip-7561.html plain text: eips-eip-7561.txt item: #855 of 3327 id: eips-eip-7568 author: eips title: eips-eip-7568 date: None words: 729 flesch: 51 summary: [EL] London [EL] Altair [CL] Arrow Glacier [EL] Gray Glacier [EL] The Merge Shapella Rationale Backwards Compatibility Security Considerations Copyright Abstract Following Muir Glacier hard fork, Meta EIPs were abandoned in favor of other ways to track changes included in Ethereum network upgrades. For many years, Ethereum used Meta EIPs to document network upgrades. keywords: ethereum; specs cache: eips-eip-7568.html plain text: eips-eip-7568.txt item: #856 of 3327 id: eips-eip-7569 author: eips title: eips-eip-7569 date: None words: 326 flesch: 51 summary: Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. Perpetually Valid Signed Voluntary Exits EIP-7045: Increase Max Attestation Inclusion Slot EIP-7514: Add Max Epoch Churn Limit EIP-7516: BLOBBASEFEE opcode Full Specifications Consensus Layer EIPs 4788, 4844, 7044, 7045 and 7514 require changes to Ethereum’s consensus layer. keywords: eips; ethereum cache: eips-eip-7569.html plain text: eips-eip-7569.txt item: #857 of 3327 id: eips-eip-7572 author: eips title: eips-eip-7572 date: None words: 671 flesch: 24 summary: Reference Implementation contract MyCollectible is ERC721, IERCXXXX { string _contractURI = ipfs://QmTNgv3jx2HHfBjQX9RnKtxj2xv2xQDtbVXoRi5rJ3a46e // or e.g. https://external-link-url.com/my-contract-metadata.json; function contractURI() external view returns (string memory) { return _contractURI; // or e.g. for onchain: string memory json = '{name: Creatures,description:...}'; return string.concat(data:application/json;utf8,, json); } /// @dev Suggested setter, not explicitly specified as part of this ERC function setContractURI(string memory newURI) external onlyOwner { _contractURI = newURI; emit ContractURIUpdated(); } } Security Considerations Addresses specified as collaborators should be expected to receive admin-level functionality for updating contract information on dapps that implement this standard. Available: https://eips.ethereum.org/EIPS/eip-7572. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: contract; description cache: eips-eip-7572.html plain text: eips-eip-7572.txt item: #858 of 3327 id: eips-eip-7579 author: eips title: eips-eip-7579 date: None words: 2720 flesch: 29 summary: Backwards Compatibility Already deployed smart accounts Smart accounts that have already been deployed will most likely be able to implement this standard. There are several reasons for why standardizing smart accounts is very beneficial to the ecosystem, including: Interoperability for modules to be used across different smart accounts Interoperability for smart accounts to be used across different wallet applications and sdks Preventing significant vendor lock-in for smart account users However, it is highly important that this standardization is done with minimal impact on the implementation logic of the accounts, so that smart account vendors can continue to innovate, while also allowing a flourishing, multi-account-compatible module ecosystem. keywords: account; bytes; calldata; function; module; smart cache: eips-eip-7579.html plain text: eips-eip-7579.txt item: #859 of 3327 id: eips-eip-758 author: eips title: eips-eip-758 date: None words: 1110 flesch: 43 summary: Rationale EIP-658 originally proposed adding return data to transaction receipts. However, return data is not charged for (as it is not stored on the blockchain), so adding it to transaction receipts could result in DoS and spam opportunities. keywords: data; return cache: eips-eip-758.html plain text: eips-eip-758.txt item: #860 of 3327 id: eips-eip-7587 author: eips title: eips-eip-7587 date: None words: 274 flesch: 41 summary: Precompile Address Range for RIPs [DRAFT], Ethereum Improvement Proposals, no. Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: address cache: eips-eip-7587.html plain text: eips-eip-7587.txt item: #861 of 3327 id: eips-eip-7590 author: eips title: eips-eip-7590 date: None words: 1309 flesch: 46 summary: ERC-7590: ERC-20 Holder Extension for NFTs Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational ⚠️ Draft Standards Track: ERC ERC-7590: ERC-20 Holder Extension for NFTs Extension to allow NFTs to receive and transfer ERC-20 tokens. Authors Steven Pineda (@steven2308), Jan Turk (@ThunderDeliverer) Created 2024-01-05 Discussion Link https://ethereum-magicians.org/t/token-holder-extension-for-nfts/16260 Requires EIP-20, EIP-165, EIP-721 Table of Contents Abstract Motivation Expanded Use Cases Facilitating Composite Transactions Market Liquidity and Value Creation Specification Rationale Pull Mechanism Granular vs Generic Backwards Compatibility Test Cases Reference Implementation Security Considerations Copyright Abstract This proposal suggests an extension to ERC-721 to enable easy exchange of ERC-20 tokens. keywords: @param; erc-20; tokens cache: eips-eip-7590.html plain text: eips-eip-7590.txt item: #862 of 3327 id: eips-eip-777 author: eips title: eips-eip-777 date: None words: 7425 flesch: 55 summary: Specification ERC777Token (Token Contract) interface ERC777Token { function name() external view returns (string memory); function symbol() external view returns (string memory); function totalSupply() external view returns (uint256); function balanceOf(address holder) external view returns (uint256); function granularity() external view returns (uint256); function defaultOperators() external view returns (address[] memory); function isOperatorFor( address operator, address holder ) external view returns (bool); function authorizeOperator(address operator) external; function revokeOperator(address operator) external; function send(address to, uint256 amount, bytes calldata data) external; function operatorSend( address from, address to, uint256 amount, bytes calldata data, bytes calldata operatorData ) external; function burn(uint256 amount, bytes calldata data) external; function operatorBurn( address from, uint256 amount, bytes calldata data, bytes calldata operatorData ) external; event Sent( address indexed operator, address indexed from, address indexed to, uint256 amount, bytes data, bytes operatorData ); event Minted( address indexed operator, address indexed to, uint256 amount, bytes data, bytes operatorData ); event Burned( address indexed operator, address indexed from, uint256 amount, bytes data, bytes operatorData ); event AuthorizedOperator( address indexed operator, address indexed holder ); event RevokedOperator(address indexed operator, address indexed holder); } tokensToSend function tokensToSend( address operator, address from, address to, uint256 amount, bytes calldata userData, bytes calldata operatorData ) external Notify a request to send or burn (if to is 0x0) keywords: address; contract; function; holder; operator; operator address; tokens cache: eips-eip-777.html plain text: eips-eip-777.txt item: #863 of 3327 id: eips-eip-778 author: eips title: eips-eip-778 date: None words: 979 flesch: 56 summary: Node records can be relayed through a future version of the node discovery protocol. Node records improve cryptographic agility and handling of protocol upgrades. keywords: key; node; record cache: eips-eip-778.html plain text: eips-eip-778.txt item: #864 of 3327 id: eips-eip-779 author: eips title: eips-eip-779 date: None words: 493 flesch: -9 summary: Citation Please cite this document as: Casey Detrio (@cdetrio), EIP-779: Hardfork Meta: DAO Fork, Ethereum Improvement Proposals, no. 779, November 2017. The contract was created from the following Solidity code (compiler version v0.3.5-2016-07-01-48238c9): // Deployed on mainnet at 0xbf4ed7b27f1d666546e30d74d50d173d20bca754 contract DAO { function balanceOf(address addr) returns (uint); function transferFrom(address from, address to, uint balance) returns (bool); uint public totalSupply; } contract WithdrawDAO { DAO constant public mainDAO = DAO(0xbb9bc244d798123fde783fcc1c72d3bb8c189413); address public trustee = 0xda4a4626d3e16e094de3225a751aab7128e96526; function withdraw(){ uint balance = mainDAO.balanceOf(msg.sender); if (!mainDAO.transferFrom(msg.sender, this, balance) || !msg.sender.send(balance)) throw; } function trusteeWithdraw() { trustee.send((this.balance + mainDAO.balanceOf(this)) - mainDAO.totalSupply()); } } keywords: contract; dao; fork cache: eips-eip-779.html plain text: eips-eip-779.txt item: #865 of 3327 id: eips-eip-8 author: eips title: eips-eip-8 date: None words: 1708 flesch: 29 summary: The packets are signed using the secp256k1 node key b71c71a67e1177ad4e901695e1b4b9ee17ae16c6668d313eac2f96dbcda3f291 ping packet with version 4, additional list elements: e9614ccfd9fc3e74360018522d30e1419a143407ffcce748de3e22116b7e8dc92ff74788c0b6663a aa3d67d641936511c8f8d6ad8698b820a7cf9e1be7155e9a241f556658c55428ec0563514365799a 4be2be5a685a80971ddcfa80cb422cdd0101ec04cb847f000001820cfa8215a8d790000000000000 000000000000000000018208ae820d058443b9a3550102 ping packet with version 555, additional list elements and additional random data: 577be4349c4dd26768081f58de4c6f375a7a22f3f7adda654d1428637412c3d7fe917cadc56d4e5e 7ffae1dbe3efffb9849feb71b262de37977e7c7a44e677295680e9e38ab26bee2fcbae207fba3ff3 d74069a50b902a82c9903ed37cc993c50001f83e82022bd79020010db83c4d001500000000abcdef 12820cfa8215a8d79020010db885a308d313198a2e037073488208ae82823a8443b9a355c5010203 040531b9019afde696e582a78fa8d95ea13ce3297d4afb8ba6433e4154caa5ac6431af1b80ba7602 3fa4090c408f6b4bc3701562c031041d4702971d102c9ab7fa5eed4cd6bab8f7af956f7d565ee191 7084a95398b6a21eac920fe3dd1345ec0a7ef39367ee69ddf092cbfe5b93e5e568ebc491983c09c7 6d922dc3 pong packet with additional list elements and additional random data: 09b2428d83348d27cdf7064ad9024f526cebc19e4958f0fdad87c15eb598dd61d08423e0bf66b206 9869e1724125f820d851c136684082774f870e614d95a2855d000f05d1648b2d5945470bc187c2d2 216fbe870f43ed0909009882e176a46b0102f846d79020010db885a308d313198a2e037073488208 ae82823aa0fbc914b16819237dcd8801d7e53f69e9719adecb3cc0e790c57e91ca4461c9548443b9 a355c6010203c2040506a0c969a58f6f9095004c0177a6b47f451530cab38966a25cca5cb58f0555 42124e findnode packet with additional list elements and additional random data: c7c44041b9f7c7e41934417ebac9a8e1a4c6298f74553f2fcfdcae6ed6fe53163eb3d2b52e39fe91 831b8a927bf4fc222c3902202027e5e9eb812195f95d20061ef5cd31d502e47ecb61183f74a504fe 04c51e73df81f25c4d506b26db4517490103f84eb840ca634cae0d49acb401d8a4c6b6fe8c55b70d 115bf400769cc1400f3258cd31387574077f301b421bc84df7266c44e9e6d569fc56be0081290476 7bf5ccd1fc7f8443b9a35582999983999999280dc62cc8255c73471e0a61da0c89acdc0e035e260a dd7fc0c04ad9ebf3919644c91cb247affc82b69bd2ca235c71eab8e49737c937a2c396 neighbours packet with additional list elements and additional random data: c679fc8fe0b8b12f06577f2e802d34f6fa257e6137a995f6f4cbfc9ee50ed3710faf6e66f932c4c8 d81d64343f429651328758b47d3dbc02c4042f0fff6946a50f4a49037a72bb550f3a7872363a83e1 b9ee6469856c24eb4ef80b7535bcf99c0004f9015bf90150f84d846321163782115c82115db84031 55e1427f85f10a5c9a7755877748041af1bcd8d474ec065eb33df57a97babf54bfd2103575fa8291 15d224c523596b401065a97f74010610fce76382c0bf32f84984010203040101b840312c55512422 cf9b8a4097e9a6ad79402e87a15ae909a4bfefa22398f03d20951933beea1e4dfa6f968212385e82 9f04c2d314fc2d4e255e0d3bc08792b069dbf8599020010db83c4d001500000000abcdef12820d05 820d05b84038643200b172dcfef857492156971f0e6aa2c538d8b74010f8e140811d53b98c765dd2 Discovery packets with unknown packet type should be discarded silently. keywords: list; packet; rlpx; version cache: eips-eip-8.html plain text: eips-eip-8.txt item: #866 of 3327 id: eips-eip-801 author: eips title: eips-eip-801 date: None words: 347 flesch: 46 summary: Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. Abstract The following standard allows the implementation of canaries within contracts. keywords: canary cache: eips-eip-801.html plain text: eips-eip-801.txt item: #867 of 3327 id: eips-eip-820 author: eips title: eips-eip-820 date: None words: 6693 flesch: 50 summary: @param _interfaceId ERC165 interface to check.\n /// @return `true` if `_contract` implements `_interfaceId`, false otherwise.\n function implementsERC165Interface(address _contract, bytes4 _interfaceId) public view returns (bool) {\n if (!erc165Cached[_contract][_interfaceId]) {\n return implementsERC165InterfaceNoCache(_contract, _interfaceId);\n }\n return interfaces[_contract][_interfaceId] == _contract;\n }\n\n /// @notice Checks whether a contract implements an ERC165 interface or not without using nor updating the cache.\n /// @param _contract Address of the contract to check.\n /// @param _interfaceId ERC165 interface to check.\n /// @return `true` if `_contract` implements `_interfaceId`, false otherwise.\n function implementsERC165InterfaceNoCache(address _contract, bytes4 _interfaceId) public view returns (bool) {\n uint256 success;\n uint256 result;\n\n (success, result) = noThrowCall(_contract, ERC165ID);\n _contract : 0; erc165Cached[_contract][_interfaceId] = true; } /// @notice Checks whether a contract implements an ERC165 interface or not. /// keywords: address; contract; ═ ═; ═ ╝; ╔ ═; ╚ ═; █ ║ cache: eips-eip-820.html plain text: eips-eip-820.txt item: #868 of 3327 id: eips-eip-823 author: eips title: eips-eip-823 date: None words: 1348 flesch: 52 summary: ERC-823: Token Exchange Standard Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-823: Token Exchange Standard Authors Kashish Khullar  Created 2018-01-06 Requires EIP-20 Table of Contents Simple Summary Abstract Motivation Specification Sender Interface Receiver Interface Exchange Service Contract Diagramatic Explanation Rationale Backward Compatibility Copyright Simple Summary A standard for token contracts, providing token exchange services thereby facilitating cross token payments. This function takes the address of the target contract, the amount we want to spend in terms of target contract tokens and address of the receiver as parameters and returns boolean success. keywords: address; exchange cache: eips-eip-823.html plain text: eips-eip-823.txt item: #869 of 3327 id: eips-eip-831 author: eips title: eips-eip-831 date: None words: 418 flesch: 58 summary: ERC-831: URI Format for Ethereum Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-831: URI Format for Ethereum A way of creating Ethereum URIs for various use-cases. Citation Please cite this document as: ligi (@ligi), ERC-831: URI Format for Ethereum [DRAFT], Ethereum Improvement Proposals, no. 831, January 2018. keywords: ethereum; prefix cache: eips-eip-831.html plain text: eips-eip-831.txt item: #870 of 3327 id: eips-eip-858 author: eips title: eips-eip-858 date: None words: 550 flesch: 56 summary: Citation Please cite this document as: Carl Larson , EIP-858: Reduce block reward and delay difficulty bomb [DRAFT], Ethereum Improvement Proposals, no. 858, January 2018. EIP-858: Reduce block reward and delay difficulty bomb Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-858: Reduce block reward and delay difficulty bomb Authors Carl Larson  Created 2018-01-29 Table of Contents Simple Summary Abstract Motivation Specification Rationale Backwards Compatibility Test Cases Implementation Copyright Simple Summary Reduce the block reward to 1 ETH and delay the difficulty bomb. keywords: block; reward cache: eips-eip-858.html plain text: eips-eip-858.txt item: #871 of 3327 id: eips-eip-86 author: eips title: eips-eip-86 date: None words: 1331 flesch: 48 summary: Abstraction of transaction origin and signature Authors Vitalik Buterin (@vbuterin) Created 2017-02-10 Table of Contents Summary Parameters Specification Rationale Miner and transaction replaying strategy Copyright Summary Implements a set of changes that serve the combined purpose of “abstracting out” signature verification and nonce checking, allowing users to create “account contracts” that perform any desired signature/nonce checks instead of using the mechanism that is currently hard-coded into transaction processing. EIP-86: Abstraction of transaction origin and signature Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-86: keywords: account; signature; transaction cache: eips-eip-86.html plain text: eips-eip-86.txt item: #872 of 3327 id: eips-eip-867 author: eips title: eips-eip-867 date: None words: 2393 flesch: 53 summary: Rationale The primary consideration for the approach described above was to minimize the amount of risk associated with recovery actions that would otherwise not have a viable solution. A secondary consideration was to standardize the format used in the proposals for recovery actions. keywords: actions; change; erp; ethereum; state cache: eips-eip-867.html plain text: eips-eip-867.txt item: #873 of 3327 id: eips-eip-868 author: eips title: eips-eip-868 date: None words: 462 flesch: 49 summary: Citation Please cite this document as: Felix Lange , EIP-868: Node Discovery v4 ENR Extension, Ethereum Improvement Proposals, no. 868, February 2018. EIP-868: Node Discovery v4 ENR Extension Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational Standards Track: Networking EIP-868: Node Discovery v4 ENR Extension Authors Felix Lange  Created 2018-02-02 Requires EIP-8, EIP-778 Table of Contents Abstract Motivation Specification - Ping Packet (0x01) - Pong Packet (0x02) - ENRRequest Packet (0x05) - ENRResponse Packet (0x06) Resolving Records Copyright Abstract This EIP defines an extension to Node Discovery Protocol v4 to enable authoritative resolution of Ethereum Node Records (ENR). keywords: node; packet cache: eips-eip-868.html plain text: eips-eip-868.txt item: #874 of 3327 id: eips-eip-875 author: eips title: eips-eip-875 date: None words: 884 flesch: 48 summary: [] tokenIndices); function name() constant public returns (string name); function symbol() constant public returns (string symbol); function balanceOf(address _owner) public view returns (uint256[] _balances); function transfer(address _to, uint256 Ethereum Improvement Proposals Ethereum Improvement Proposals ethereum/EIPs Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. keywords: function; returns; uint256 cache: eips-eip-875.html plain text: eips-eip-875.txt item: #875 of 3327 id: eips-eip-884 author: eips title: eips-eip-884 date: None words: 2516 flesch: 59 summary: The `original` address MUST be removed from the set of verified addresses. Implementers should maintain an off-chain private database that records the owner’s name, residential address, and Ethereum address. keywords: @param; address; function; hash; public cache: eips-eip-884.html plain text: eips-eip-884.txt item: #876 of 3327 id: eips-eip-897 author: eips title: eips-eip-897 date: None words: 484 flesch: 43 summary: This standard proposes a set of interfaces for proxies to signal how they work and what their main implementation is. Abstract Using proxies that delegate their own logic to another contract is becoming an increasingly popular technique for both smart contract upgradeability and creating cheap clone contracts. keywords: code; proxy cache: eips-eip-897.html plain text: eips-eip-897.txt item: #877 of 3327 id: eips-eip-900 author: eips title: eips-eip-900 date: None words: 540 flesch: 44 summary: uint256 total, bytes data); event Unstaked(address indexed user, uint256 amount, uint256 total, bytes data); function stake(uint256 amount, bytes data) public; function stakeFor(address user, uint256 amount, bytes data) public; function unstake(uint256 amount, bytes data) public; function totalStakedFor(address addr) public view returns (uint256); function totalStaked() public view returns (uint256); function token() public view returns (address); function supportsHistory() public pure returns (bool); // optional function lastStakedFor(address addr) public view returns (uint256); function totalStakedForAt(address addr, uint256 blockNumber) public view returns (uint256); function totalStakedAt(uint256 blockNumber) public view returns (uint256); } stake Stakes a certain amount of tokens, this MUST transfer the given amount from the user. keywords: function; returns cache: eips-eip-900.html plain text: eips-eip-900.txt item: #878 of 3327 id: eips-eip-902 author: eips title: eips-eip-902 date: None words: 974 flesch: 42 summary: Abstract This standard provides a registry contract method for authorizing token transfers. By restricting ourselves to token transfers (ex. ERC20 or EIP-777), we can make assumptions about the use cases our validators will need to handle, and can make the API both small, useful, and extensible. keywords: address; token; validation cache: eips-eip-902.html plain text: eips-eip-902.txt item: #879 of 3327 id: eips-eip-908 author: eips title: eips-eip-908 date: None words: 3643 flesch: 49 summary: Not providing incentives for full nodes validating transactions may not seem like as much of an issue now, but not doing so could hinder the growth of the protocol. While it may be argued that the funds raised by the Ethereum pre-mine (the pre-ICO and the ICO) can be used to fund client development, that argument is questionable, since Parity is VC-funded, and other clients such as Prysmatic Labs 1, 2, 3 and exthereum have received funding from other parties, whereas perhaps they would not have needed to do so if there was sufficient funding from the Ethereum pre-mine funds. keywords: address; client; ethereum; list; nodes; protocol cache: eips-eip-908.html plain text: eips-eip-908.txt item: #880 of 3327 id: eips-eip-918 author: eips title: eips-eip-918 date: None words: 2636 flesch: 27 summary: Returns the validated digest function hash(uint256 nonce) public returns (bytes32 digest); _reward Internal interface function _reward, meant to be overridden in implementation to calculate and allocate the reward amount. @notice Externally facing mint function kept for backwards compatibility with previous mint() definition * @param _nonce the solution nonce * @param _challenge_digest the keccak256 encoded challenge number + message sender + solution nonce **/ function mint(uint256 _nonce, bytes32 _challenge_digest) public returns (bool success) { //the challenge digest must match the expected bytes32 digest = keccak256( abi.encodePacked(challengeNumber, msg.sender, _nonce) ); require(digest == _challenge_digest, Challenge digest does not match expected digest on token contract [ AbstractERC918.mint() ]); success = mint(_nonce); } } Test Cases (Test cases for an implementation are mandatory for EIPs that are affecting consensus changes. keywords: function; nonce; public; returns; token; uint cache: eips-eip-918.html plain text: eips-eip-918.txt item: #881 of 3327 id: eips-eip-926 author: eips title: eips-eip-926 date: None words: 582 flesch: 35 summary: Citation Please cite this document as: Nick Johnson , ERC-926: Address metadata registry [DRAFT], Ethereum Improvement Proposals, no. 926, March 2018. This permits use-cases such as generalised authorisations, providing token acceptance settings, and claims registries. keywords: metadata; registry cache: eips-eip-926.html plain text: eips-eip-926.txt item: #882 of 3327 id: eips-eip-927 author: eips title: eips-eip-927 date: None words: 548 flesch: 41 summary: ERC-927: Generalised authorisations Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: ERC ERC-927: Generalised authorisations Authors Nick Johnson  Created 2018-03-12 Requires EIP-926 Table of Contents Abstract Motivation Specification Backwards Compatibility Implementation Copyright Abstract This EIP specifies a generic authorisation mechanism, which can be used to implement a variety of authorisation patterns, replacing approvals in ERC20, operators in ERC777, and bespoke authorisation patterns in a variety of other types of contract. Implementing contracts SHOULD use the standard specified here to determine if other callers may provide authorisations as well. keywords: address; callee cache: eips-eip-927.html plain text: eips-eip-927.txt item: #883 of 3327 id: eips-eip-969 author: eips title: eips-eip-969 date: None words: 1341 flesch: 45 summary: EIP-969: Modifications to ethash to invalidate existing dedicated hardware implementations Ethereum Improvement Proposals AllCoreNetworkingInterfaceERCMetaInformational 🚧 Stagnant Standards Track: Core EIP-969: Modifications to ethash to invalidate existing dedicated hardware implementations Authors David Stanfill  Created 2018-04-03 Discussion Link https://gitter.im/ethereum/topics/topic/5ac4d974109bb043328911ce/eip-969-discussion Table of Contents Simple Summary Abstract Motivation Specification EthashV2 Agent Changes (Optional Variant) Rationale Backwards Compatibility Test Cases Implementation Copyright Simple Summary This EIP modifies ethash in order to break ASIC miners specialized for the current ethash mining algorithm. Goal #1 is something that we can only do probabilistically without detailed knowledge of existing ASIC miner design. keywords: algorithm; asic; miners cache: eips-eip-969.html plain text: eips-eip-969.txt item: #884 of 3327 id: eips-eip-998 author: eips title: eips-eip-998 date: None words: 7675 flesch: 57 summary: ERC-721 Top-Down Composable ERC-20 Top-Down Composable ERC-721 Bottom-Up Composable ERC-20 Bottom-Up Composable Notes Rationale Which Kind of Composable To Use? Explicit Transfer Parameters Backwards Compatibility Reference Implementation Security Considerations Copyright Abstract An extension of the ERC-721 standard to enable ERC-721 tokens to own other ERC-721 tokens and ERC-20 tokens. ERC-20 top-down composables are ERC-721 tokens that can receive, hold and transfer ERC-20 tokens. keywords: @param; address; function; token; tokenid; uint256 cache: eips-eip-998.html plain text: eips-eip-998.txt item: #885 of 3327 id: eips-eip-999 author: eips title: eips-eip-999 date: None words: 7248 flesch: 64 summary: JUMP JUMPDEST JUMPDEST POP JUMP JUMPDEST DUP3 DUP1 SLOAD PUSH1 0x1 DUP2 PUSH1 0x1 AND ISZERO PUSH2 0x100 MUL SUB AND PUSH1 0x2 SWAP1 DIV SWAP1 PUSH1 0x0 MSTORE PUSH1 0x20 PUSH1 0x0 SHA3 SWAP1 PUSH1 0x1F ADD PUSH1 0x20 SWAP1 DIV DUP2 ADD SWAP3 DUP3 PUSH1 0x1F LT PUSH2 0x1C6F JUMPI DUP1 CALLDATALOAD PUSH1 0xFF NOT AND DUP4 DUP1 ADD OR DUP6 SSTORE PUSH2 0x1C9D JUMP JUMPDEST DUP3 DUP1 ADD PUSH1 0x1 ADD DUP6 SSTORE DUP3 ISZERO PUSH2 0x1C9D JUMPI SWAP2 DUP3 ADD JUMPDEST DUP3 DUP2 GT ISZERO PUSH2 0x1C9C JUMPI DUP3 CALLDATALOAD DUP3 SSTORE SWAP2 PUSH1 0x20 ADD SWAP2 SWAP1 PUSH1 0x1 ADD SWAP1 PUSH2 0x1C81 JUMP JUMPDEST JUMPDEST POP SWAP1 POP PUSH2 0x1CAA SWAP2 SWAP1 PUSH2 0x1CFC JUMP JUMPDEST POP SWAP1 JUMP JUMPDEST DUP2 SLOAD DUP2 DUP4 SSTORE DUP2 DUP2 ISZERO GT PUSH2 0x1CD5 JUMPI DUP2 DUP4 PUSH1 0x0 MSTORE PUSH1 0x20 PUSH1 0x0 SHA3 SWAP2 DUP3 ADD SWAP2 ADD PUSH2 0x1CD4 SWAP2 SWAP1 PUSH2 0x1D21 JUMP JUMPDEST JUMPDEST POP POP POP JUMP JUMPDEST POP DUP1 SLOAD PUSH1 0x0 DUP3 SSTORE SWAP1 PUSH1 0x0 MSTORE PUSH1 0x20 PUSH1 0x0 SHA3 SWAP1 DUP2 ADD SWAP1 PUSH2 0x1CF8 SWAP2 SWAP1 PUSH2 0x1D21 JUMP JUMPDEST JUMPDEST POP JUMP JUMPDEST PUSH2 0x1D1E SWAP2 SWAP1 JUMPDEST DUP1 DUP3 GT ISZERO PUSH2 0x1D1A JUMPI PUSH1 0x0 DUP2 PUSH1 0x0 SWAP1 SSTORE POP PUSH1 0x1 ADD PUSH2 0x1D02 JUMP JUMPDEST POP SWAP1 JUMP JUMPDEST SWAP1 JUMP JUMPDEST PUSH2 0x1D43 SWAP2 SWAP1 JUMPDEST DUP1 DUP3 GT ISZERO PUSH2 0x1D3F JUMPI PUSH1 0x0 DUP2 PUSH1 0x0 SWAP1 SSTORE POP PUSH1 0x1 ADD PUSH2 0x1D27 JUMP JUMPDEST POP SWAP1 JUMP JUMPDEST SWAP1 JUMP JUMPDEST PUSH1 0x0 PUSH1 0x0 REVERT JUMPDEST DUP1 PUSH1 0x2 DUP2 SWAP1 SSTORE POP PUSH3 0x1B7 PUSH3 0x2C1 PUSH5 0x100000000 MUL PUSH3 0x1BCF OR PUSH5 0x100000000 SWAP1 DIV JUMP JUMPDEST PUSH1 0x4 DUP2 SWAP1 SSTORE POP JUMPDEST JUMPDEST POP JUMP JUMPDEST PUSH1 0x0 keywords: dup2 push1; jumpdest push1; jumpi push1; pop dup2; pop pop; pop push1; push1 0x0; swap1 dup2; swap1 pop; swap1 push1 cache: eips-eip-999.html plain text: eips-eip-999.txt item: #886 of 3327 id: ethereummagicians-10310 author: ethereummagicians title: ethereummagicians-10310 date: None words: 5054 flesch: 32 summary: @param `_tokenIds` of rNFTs associated with the contract address `_address` being referred by the rNFT with `tokenId`. @requirement /// - `_address` **MUST NOT** be the same as `address(this)` where `this` is executed by an external contract where `TargetContract` interface is implemented. keywords: address; await; const; function; memory; rnft; token; tokencontract1.address; tokenid; uint256 cache: ethereummagicians-10310.html plain text: ethereummagicians-10310.txt item: #887 of 3327 id: ethereummagicians-11091 author: ethereummagicians title: ethereummagicians-11091 date: None words: 8461 flesch: 65 summary: As part of the web3 provider API there could be a method for dapps to register event notification handlers with the user’s wallet for particular contracts like the above without any involvement on-chain at all! As part of the web3 provider API there could be a method for dapps to register event notification handlers with the user’s wallet for particular contracts like the above without any involvement on-chain at all! True! keywords: address; body; contract; event; message; notifications; string; subject; user; way cache: ethereummagicians-11091.html plain text: ethereummagicians-11091.txt item: #888 of 3327 id: ethereummagicians-11374 author: ethereummagicians title: ethereummagicians-11374 date: None words: 2472 flesch: 68 summary: dror November 16, 2022, 7:40pm 18 SamWilsn: atomicity: strict → If any operations fail, operations MUST revert This mode is possible when working with contract wallets, but not with EOA. SamWilsn November 16, 2022, 7:55pm 19 dror: This mode is possible when working with contract wallets, but not with EOA. Exactly. keywords: bundle; november; rpc; wallet cache: ethereummagicians-11374.html plain text: ethereummagicians-11374.txt item: #889 of 3327 id: ethereummagicians-12326 author: ethereummagicians title: ethereummagicians-12326 date: None words: 980 flesch: 54 summary: Going to make breakfast then take a crack at it on my desktop afterwards 3 Likes Vantu24 October 19, 2023, 1:31pm 13 Ethereum Improvement Proposal all info EIPs General information regarding EIPs How to submit an EIP Tutorial Write your EIP using EIP template Create PR to ethereum/EIPs repo Share link to your EIP alongside with EIP description to Eth Magicians forum to gather community feedback EIP Editors will assign EIP number to your EIP Notes: Points 3 and 4 can be swapped, it may take some time for EIP Editors to assign number to your EIP Do not copy paste the EIP itself to FEM forum, post just overview and link to the EIP itself EIP Guid… 1 Like wkyleg November 30, 2023, 3:30am 17 I saw in the github readme that “Before you write an EIP, ideas MUST be thoroughly discussed on Ethereum Magicians or Ethereum Research. Ethereum Improvement Proposal all info - EIPs - Fellowship of Ethereum Magicians Fellowship of Ethereum Magicians Ethereum Improvement Proposal all info EIPs eip, all-info, tutorial, eip-process anett December 29, 2022, 4:51pm 1 General information regarding EIPs How to submit an EIP Tutorial Write your EIP using EIP template Create PR to ethereum/EIPs repo Share link to your EIP alongside with EIP description to Eth Magicians forum to gather community feedback EIP Editors will assign EIP number to your EIP Notes: keywords: eip; eips; ethereum cache: ethereummagicians-12326.html plain text: ethereummagicians-12326.txt item: #890 of 3327 id: ethereummagicians-12894 author: ethereummagicians title: ethereummagicians-12894 date: None words: 1753 flesch: 56 summary: Get decimals of token standard function standard() constant returns (string _standard) Get the standard of token contract. Transfer function of ERC20 standard does not notify the receiver and therefore if any tokens are sent to a contract with the transfer function then the receiver will not recognize this transfer and the tokens can become stuck in the receivers address without any possibility of recovering them. keywords: contract; function; standard; token cache: ethereummagicians-12894.html plain text: ethereummagicians-12894.txt item: #891 of 3327 id: ethereummagicians-13030 author: ethereummagicians title: ethereummagicians-13030 date: None words: 3228 flesch: 61 summary: Of course, anyone is free to deploy their own registry implementation, or to deploy token bound account contracts without using a registry. I think proxy method to generate account contract would make the gas cost more efficient. keywords: account; contract; nft; proposal; token cache: ethereummagicians-13030.html plain text: ethereummagicians-13030.txt item: #892 of 3327 id: ethereummagicians-13366 author: ethereummagicians title: ethereummagicians-13366 date: None words: 3575 flesch: 63 summary: This modification would look like this: event DefaultLocked(bool status, bool override); Here, if override is set to true, the event will take precedence over any previously emitted Locked events, effectively resetting the status of all tokens. This implies that marketplaces and other observers must refer to last emitted DefaultLocked event if a Locked event has not been emitted for a specific tokenId. keywords: default; event; lock; status; token cache: ethereummagicians-13366.html plain text: ethereummagicians-13366.txt item: #893 of 3327 id: ethereummagicians-13891 author: ethereummagicians title: ethereummagicians-13891 date: None words: 1121 flesch: 62 summary: Eip-6909-multi-token-standard - EIPs - Fellowship of Ethereum Magicians Fellowship of Ethereum Magicians Eip-6909-multi-token-standard EIPs nft, erc jtriley-eth April 19, 2023, 5:46pm 1 eip: 6909 title: Multi-Token Standard description: A minimal specification for managing multiple tokens by their id in a single contract. Another thing that just came to my mint, Neither ERC20 nor ERC1155 required decimals to be implemented. keywords: april; decimals; eth cache: ethereummagicians-13891.html plain text: ethereummagicians-13891.txt item: #894 of 3327 id: ethereummagicians-14195 author: ethereummagicians title: ethereummagicians-14195 date: None words: 923 flesch: 54 summary: That is, if I attach more gas to my EL exit, I can get priority ordering over someone who paid less. EIP-7002: Execution layer triggerable exits - Core EIPs - Fellowship of Ethereum Magicians Fellowship of Ethereum Magicians EIP-7002: Execution layer triggerable exits EIPs Core EIPs djrtwo May 9, 2023, 1:19pm 1 Discussion topic for EIP-7002 github.com/ethereum/EIPs Add EIP: Execution layer triggerable exits ethereum:master ← djrtwo:el-exits opened 01:14PM - 09 May 23 UTC djrtwo +369 -0 Add a cross-layer method to trigger validator exits from the execution layer. keywords: exits; layer; prague cache: ethereummagicians-14195.html plain text: ethereummagicians-14195.txt item: #895 of 3327 id: ethereummagicians-14778 author: ethereummagicians title: ethereummagicians-14778 date: None words: 3054 flesch: 47 summary: For instance, it can enhance ERC-1400 by providing dynamic data management for security tokens, or work alongside EIP-2615 to enrich swap orders with additional data capabilities. this provides a comprehensive and insightful overview of ERC-7208 , particularly highlighting the innovative approach of On-Chain Data Containers (ODC) in enhancing data management and interoperability across various token standards. keywords: chain; data; december; erc-7208; odc; properties; property cache: ethereummagicians-14778.html plain text: ethereummagicians-14778.txt item: #896 of 3327 id: ethereummagicians-14979 author: ethereummagicians title: ethereummagicians-14979 date: None words: 4450 flesch: 60 summary: It is condescending to assume that liquidity providers for existing bridges lack understanding of the associated risks, especially given the availability of avenues where such risks are disclosed, as demonstrated by resources like L2BEAT – The state of the layer two ecosystem. The proposal introduces: A burn/mint interface to the token callable by bridges allowlisted by the token issuer. keywords: bridge; chain; issuers; limit; liquidity; rate; token; xerc20 cache: ethereummagicians-14979.html plain text: ethereummagicians-14979.txt item: #897 of 3327 id: ethereummagicians-15144 author: ethereummagicians title: ethereummagicians-15144 date: None words: 3447 flesch: 69 summary: AA might never become a 1st class citizen if we don’t let contract accounts be tx.origin. 3 Likes Emilijus July 26, 2023, 7:33pm 5 Why do the chainId, maxFeePerGas, maxPriorityFeePerGas and value fields have the int256 type instead of uint256? 1 Like david July 26, 2023, 7:43pm 6 The EIP states “Allowing cheaper storage in this instance acts as a reward to users who migrate their EOAs to smart contract wallets.” keywords: code; july; key; migration; transaction cache: ethereummagicians-15144.html plain text: ethereummagicians-15144.txt item: #898 of 3327 id: ethereummagicians-15269 author: ethereummagicians title: ethereummagicians-15269 date: None words: 1986 flesch: 44 summary: This standard defines a framework that enables ticketing agents to utilize ERC-721 tokens as event tickets and restricts token transferability to prevent ticket touting. Sandy 0xTraub August 8, 2023, 6:07pm 6 While you make some fair points I think it would be pretty easy to get the support from the community to tell ticket resellers to get f****d for not being able to scalp people, but that’s a different argument. keywords: partner; ticket; token; tokenstatus; value cache: ethereummagicians-15269.html plain text: ethereummagicians-15269.txt item: #899 of 3327 id: ethereummagicians-15504 author: ethereummagicians title: ethereummagicians-15504 date: None words: 312 flesch: 59 summary: Could the permit implementation give more granular control on by the owner to the spender for certain id in a specified amount? function permit( address owner, address spender, uint256 tokenId, uint256 value, uint256 deadline, uint8 v, bytes32 r, bytes32 s ) external payable override { That would of course require a new mapping. Proposal for a new EIP: ERC-2612 style permits for ERC1155 NFTs - EIPs - Fellowship of Ethereum Magicians Fellowship of Ethereum Magicians Proposal for a new EIP: ERC-2612 style permits for ERC1155 NFTs EIPs nft emiliolanzalaco August 20, 2023, 11:06pm 1 Motivation Permits enable a one-transaction transfer flow, removing the approval step. keywords: erc1155; permits cache: ethereummagicians-15504.html plain text: ethereummagicians-15504.txt item: #900 of 3327 id: ethereummagicians-15683 author: ethereummagicians title: ethereummagicians-15683 date: None words: 3431 flesch: 62 summary: JakubLipinski September 22, 2023, 7:38pm 18 Just for the sake of reference: I tried (and failed) to create an on-chain registry of smart contract audits in 2008 as a part of SolidStamp service. It’s been 3 months since we launched SolidStamp, an on-chain registry of smart contract audits. keywords: audit; auditors; contract; registry; september cache: ethereummagicians-15683.html plain text: ethereummagicians-15683.txt item: #901 of 3327 id: ethereummagicians-15902 author: ethereummagicians title: ethereummagicians-15902 date: None words: 777 flesch: 54 summary: Are there PRs for other wallets? 2 Likes gitarg November 6, 2023, 8:37pm 5 So cool, working on something similar with orgs, identity and handshakes, I don’t think its a different direction just neat name gitarg November 6, 2023, 8:49pm 6 code looks more like implementation than a standard, anyone working on the eip: Ethereum Improvement Proposals All | Ethereum Improvement Proposals Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. PLUME Signature in Wallets by Divide-By-0 · Pull Request #37 · ethereum/ERCs · GitHub This ERC adds a signature scheme called PLUME to existing Ethereum keypairs that enables unique anonymous nullifiers for accounts in ZK. keywords: ethereum; november; plume cache: ethereummagicians-15902.html plain text: ethereummagicians-15902.txt item: #902 of 3327 id: ethereummagicians-15989 author: ethereummagicians title: ethereummagicians-15989 date: None words: 1536 flesch: 57 summary: In addition, protocols might create separate events for handling ETH native cases and ERC-20 cases. 4 Likes kryptoklob October 3, 2023, 11:02pm 2 Thoughts: I think a standard that unifies the several different ways that ETH is represented when returning asset addresses is a great idea I think the specification can be simplified/reworded a bit: “When a smart contract returns an ERC20 address of specifically 0xEEeeEEEE (or whatever you decide on), this signifies that the ERC20 is not actually an ERC20, but raw ETH instead. keywords: address; erc-20; eth; token cache: ethereummagicians-15989.html plain text: ethereummagicians-15989.txt item: #903 of 3327 id: ethereummagicians-15996 author: ethereummagicians title: ethereummagicians-15996 date: None words: 1949 flesch: 65 summary: If you think it makes sense, we could simply reference the use of TXT records rather that specifying DoH specifically, since that seems to be the way to access DNS records from the browser without a proprietary API. If you think it makes sense, we could simply reference the use of TXT records rather that specifying DoH specifically, since that seems to be the way to access DNS records from the browser without a proprietary API. keywords: contract; dns; domain cache: ethereummagicians-15996.html plain text: ethereummagicians-15996.txt item: #904 of 3327 id: ethereummagicians-16256 author: ethereummagicians title: ethereummagicians-16256 date: None words: 253 flesch: 41 summary: EIP-7546: Upgradeable Clone - EIPs - Fellowship of Ethereum Magicians Fellowship of Ethereum Magicians EIP-7546: Upgradeable Clone EIPs erc, proxy-contract, upgradeable-contract KaiHiroi October 25, 2023, 8:52am 1 Discussion for github.com/ethereum/ERCs Add ERC: Upgradeable Clone ethereum:master ← KaiHiroi:ucs opened 03:03AM - 27 Oct 23 UTC KaiHiroi +626 -0 Migrate from EIPs repository --- When opening a pull request to submit a n…ew EIP, please use the suggested template: https://github.com/ethereum/EIPs/blob/master/eip-template.md We have a GitHub bot that automatically merges some PRs. Your GitHub username or email address is listed in the 'author' header of all affected PRs, inside . - If matching on email address, the email address is the one publicly listed on your GitHub profile. keywords: december cache: ethereummagicians-16256.html plain text: ethereummagicians-16256.txt item: #905 of 3327 id: ethereummagicians-16664 author: ethereummagicians title: ethereummagicians-16664 date: None words: 2275 flesch: 62 summary: 1 Like ankurdubey521 November 17, 2023, 12:12am 4 Why is unused gas a concern specifically for AA transactions and not regular EOA transactions? Ivshti November 17, 2023, 7:27am 5 Because of the separate validation and execution stages for AA transactions, it’s harder for the block builders to account for an unused gas discrepancy. keywords: account; gas; november; transaction cache: ethereummagicians-16664.html plain text: ethereummagicians-16664.txt item: #906 of 3327 id: ethereummagicians-16690 author: ethereummagicians title: ethereummagicians-16690 date: None words: 2036 flesch: 47 summary: I’m here not just to propose an idea but to initiate a dialogue about how we can collectively enhance user interactions within our ecosystem. A Collaborative Journey Ahead This concept is not just about a new interface; it’s about rethinking our approach to user interactions in the Ethereum ecosystem. keywords: account; contract; november; user cache: ethereummagicians-16690.html plain text: ethereummagicians-16690.txt item: #907 of 3327 id: ethereummagicians-16809 author: ethereummagicians title: ethereummagicians-16809 date: None words: 1892 flesch: 68 summary: Likes timbeiko November 29, 2023, 6:56pm 8 Right, assuming we didn’t do Verkle, we could choose to only do a set of smaller EIPs, but I just want to make sure we don’t do that thinking “it will be done in 3 months” when it’s likely to take 2x+ longer 4 Likes gcolvin November 29, 2023, 10:36pm 9 gballet: if it’s the next major HF, the complexity of verkle trees won’t leave much room for anything else At this point the EOF proposals represent some seven years of research and development. 7 Likes Giulio2002 December 1, 2023, 12:43pm 12 I think Verkle trees alongside with very few small EIPs (Verkle tree is a big update) such as EIP-2537 is desirable, in alternative we can focus on EOF and many small EIPs 1 Like prebuffo December 1, 2023, 1:14pm 13 I would divide the discussion into two parts, namely which large EIP (or series of EIPs) to include between Verkle Tree and EOF, and which other ‘small’ EIP to include. keywords: december; eips; likes; november; upgrade cache: ethereummagicians-16809.html plain text: ethereummagicians-16809.txt item: #908 of 3327 id: ethereummagicians-17134 author: ethereummagicians title: ethereummagicians-17134 date: None words: 3754 flesch: 56 summary: This standard proposes a specification for shadow events – extra event logs in contract code that should only be generated in an offchain execution environment. Standardizing the syntax used for shadow events will make it easier for them to be specified, discovered, and fetched by any offchain developer tools or infrastructure. keywords: contract; cost; data; december; events; indexing; shadow; state cache: ethereummagicians-17134.html plain text: ethereummagicians-17134.txt item: #909 of 3327 id: ethereummagicians-17157 author: ethereummagicians title: ethereummagicians-17157 date: None words: 118 flesch: 39 summary: interface IERC7572 { function contractURI() external view returns (string memory); event ContractURIUpdated(); } Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled ERC-7572: Contract-level metadata via `contractURI()` - ERCs - Fellowship of Ethereum Magicians Fellowship of Ethereum Magicians ERC-7572: Contract-level metadata via `contractURI()` ERCs ryanio December 8, 2023, 6:04pm 1 PR: Add ERC-7572: Contract-level metadata via `contractURI()` by ryanio · keywords: metadata cache: ethereummagicians-17157.html plain text: ethereummagicians-17157.txt item: #910 of 3327 id: ethereummagicians-17170 author: ethereummagicians title: ethereummagicians-17170 date: None words: 378 flesch: 40 summary: This standard enables asset owners to issue tokens representing a share of their real-world assets, such as real estate or art, while retaining the capability to recall these tokens at a later stage. Our proposed standard introduces a mechanism for recall, which allows asset owners to effectively retract the tokens they have issued, in exchange for a predefined recall price. keywords: standard cache: ethereummagicians-17170.html plain text: ethereummagicians-17170.txt item: #911 of 3327 id: ethereummagicians-17232 author: ethereummagicians title: ethereummagicians-17232 date: None words: 819 flesch: 42 summary: Specificaiton Methods Smart Contract on the Asset Chain interface IDeliveryWithKey { event AssetTransferIncepted(address initiator, uint id); event AssetTransferConfirmed(address confirmer, uint id); event AssetClaimed(uint id, string key); event AssetReclaimed(uint id, string key); function inceptTransfer(uint id, int amount, address from, string keyEncryptedSeller) external; function confirmTransfer(uint id, int amount, address to, string keyEncryptedBuyer) external; function transferWithKey(uint id, string key) external; } Smart Contract on the Payment Chain interface IPaymentAndDecrypt { event PaymentTransferIncepted(address initiator, uint id, int amount); event TransferKeyRequested(uint id, string encryptedKey); event TransferKeyReleased(uint id, bool success, string key); function inceptTransfer(uint id, int amount, address from, string keyEncryptedSuccess, string keyEncryptedFailure) external; function transferAndDecrypt(uint id, address from, address to, keyEncryptedSuccess, string keyEncryptedFailure) external; function cancelAndDecrypt(uint id, address from, address to, keyEncryptedSuccess, string keyEncryptedFailure) external; } Rationale The rationale is described in the following sequence diagram. So id is generated by another function call (that is not part of the interface)? keywords: payment; string cache: ethereummagicians-17232.html plain text: ethereummagicians-17232.txt item: #912 of 3327 id: ethereummagicians-17242 author: ethereummagicians title: ethereummagicians-17242 date: None words: 1218 flesch: 50 summary: In building this feature into ioPay, the team leveraged P256 to authenticate wallet transactions and email based DKIM protocol to recover user accounts. This opens up a whole new realm of possibilities for ownership, management, and monetization while potentially attracting a new generation of web3 users. keywords: account; iopay; iotex cache: ethereummagicians-17242.html plain text: ethereummagicians-17242.txt item: #913 of 3327 id: ethereummagicians-17264 author: ethereummagicians title: ethereummagicians-17264 date: None words: 689 flesch: 36 summary: It includes the user’s wallet address, issuer, user name, and Credential Number struct VerifiedPresentation { address userAddr; string issuer; string user; uint CredentialNumber; } We have considered granting user identity based on DID Credentials. keywords: credential; sbt; user cache: ethereummagicians-17264.html plain text: ethereummagicians-17264.txt item: #914 of 3327 id: ethereummagicians-17274 author: ethereummagicians title: ethereummagicians-17274 date: None words: 165 flesch: 43 summary: ERC-7575: Partial And Extended ERC-4626 Vaults - ERCs - Fellowship of Ethereum Magicians Fellowship of Ethereum Magicians ERC-7575: Partial And Extended ERC-4626 Vaults ERCs erc joeysantoro December 12, 2023, 4:09pm 1 See ERC-7575: Partial and extended ERC-4626 implementations by Joeysantoro · New functionality includes multiple assets or entry points for the same share token, conversions between arbitrary tokens, and implementations which use partial entry/exit flows from ERC-4626. keywords: erc-4626 cache: ethereummagicians-17274.html plain text: ethereummagicians-17274.txt item: #915 of 3327 id: ethereummagicians-17295 author: ethereummagicians title: ethereummagicians-17295 date: None words: 140 flesch: 43 summary: Add EIP: Versioning Scheme for EIPs - EIPs - Fellowship of Ethereum Magicians Fellowship of Ethereum Magicians Add EIP: Versioning Scheme for EIPs EIPs danceratopz December 13, 2023, 9:37am 1 github.com/ethereum/EIPs Add EIP: Versioning Scheme for EIPs ethereum:master ← danceratopz:versioning-scheme-for-eips opened 09:19AM - 13 Dec 23 UTC danceratopz +121 -0 This PR proposes a versioning scheme for Standards Track EIPs based on their Spe…cifications section. This EIP suggests a semantic versioning scheme for Standard Track EIPs based on their Specifications section to help remove ambiguity when discussing changes and tracking implementations. keywords: eips cache: ethereummagicians-17295.html plain text: ethereummagicians-17295.txt item: #916 of 3327 id: ethereummagicians-17336 author: ethereummagicians title: ethereummagicians-17336 date: None words: 571 flesch: 55 summary: I have a couple of questions: Are module types in ERC-7579 meant to be fixed, or could we consider making them more flexible for future module types? What might be the limitations of adopting a less specific approach to module types? 1 Like jhfnetboy December 17, 2023, 4:51am 3 Great job! keywords: module; types cache: ethereummagicians-17336.html plain text: ethereummagicians-17336.txt item: #917 of 3327 id: ethereummagicians-17474 author: ethereummagicians title: ethereummagicians-17474 date: None words: 413 flesch: 45 summary: Inclusion lists aim to provide a mechanism to improve the censorship resistance of Ethereum by allowing proposers to specify a set of transactions that must be promptly included for subsequent blocks to be considered valid. Inclusion lists aim to allow proposers to retain some authority by providing a mechanism by which transactions can be forcibly included. keywords: inclusion cache: ethereummagicians-17474.html plain text: ethereummagicians-17474.txt item: #918 of 3327 id: ethereummagicians-2842 author: ethereummagicians title: ethereummagicians-2842 date: None words: 2161 flesch: 66 summary: The following are two examples of common actions we may wish to perfom for many different proxy contracts. Here we introduce an improvement upon proxy contracts which can be used as a holistic lifecycle management tool for smart contracts. keywords: amxx; contract; march; proxy cache: ethereummagicians-2842.html plain text: ethereummagicians-2842.txt item: #919 of 3327 id: ethereummagicians-5805 author: ethereummagicians title: ethereummagicians-5805 date: None words: 2563 flesch: 60 summary: Particularly, it would be ideal to be able to describe the result as a single Verkle tree Forward-compatibility (eg. ability to add more objects into an account header in the future) Code for an account should be stored in one or a few subtrees, so that a witness for many code chunks can be minimally sized Frequently-accessed values (eg. balance, nonce) should be stored in one or a few subtrees, so that a witness for this data can be minimally sized Data should be by default reasonably distributed across the entire state tree, to make syncing easier An updated proposal, which puts account data closer together to reduce the witness size per-account-access: The proposed scheme can be described in two different ways: We can view it as a “trie of commitments”, with two additional simplifications: Only leaf nodes containing extended paths, no “internal” extension nodes The leaves of the top trie are only commitments (that are Kate commitments of the same type as the commitments used in the trie), and not “a hash pointing to a header which contains two values, a bytearray and a tree” as is the status quo today We can view it as a single tree, where there are internal extension nodes but they can only extend up to the 31 byte boundary (tree keys MUST be 32 bytes long) This seems nice because you keep sub-trees, search is almost always optimal (or can be reconfigured based on assembly), AND assembly of the tree itself is quick (meaning the rebalancing act isn’t too expensive) keywords: account; address; byte; storage; tree; vbuterin cache: ethereummagicians-5805.html plain text: ethereummagicians-5805.txt item: #920 of 3327 id: ethereummagicians-7014 author: ethereummagicians title: ethereummagicians-7014 date: None words: 1499 flesch: 67 summary: EIP-3855: PUSH0 instruction - Core EIPs - Fellowship of Ethereum Magicians Fellowship of Ethereum Magicians EIP-3855: PUSH0 instruction EIPs Core EIPs evm, opcodes, shanghai-candidate axic September 6, 2021, 9:09pm 1 This is the discussion topic for Ethereum Improvement Proposals EIP-3855: PUSH0 instruction Introduce a new instruction which pushes the constant value 0 onto the stack 6 Likes Arachnid September 6, 2021, 10:53pm 2 Thank you for putting this forward! poojaranjan April 8, 2022, 2:22pm 16 PEEPanEIP-3855: PUSH0 instruction with @axic @chfast @hugo-dc 2 Likes wjmelements April 13, 2022, 8:30pm 17 axic: keywords: instruction; push0; september cache: ethereummagicians-7014.html plain text: ethereummagicians-7014.txt item: #921 of 3327 id: ethereummagicians-7677 author: ethereummagicians title: ethereummagicians-7677 date: None words: 702 flesch: 55 summary: New proposal of Smart Non Fungible Token - Tokens - Fellowship of Ethereum Magicians Fellowship of Ethereum Magicians New proposal of Smart Non Fungible Token Tokens nft Arcenegui December 3, 2021, 2:52pm 1 The novelty introduced in this EIP is the proposal of smart Non-Fungible Tokens (NFTs), named as SmartNFTs, to represent smart assets such as IoT devices, which are physical smart assets. This paper is available: Sensors | Free Full-Text | Secure Combination of IoT and Blockchain by Physically Binding IoT Devices to Smart Non-Fungible Tokens Using PUFs 1 Like mryalamanchi February 14, 2022, 1:22am 2 The EIP seems to require an ESP32 device running a firmware, but the source code for the same isn’t provided. keywords: device; iot cache: ethereummagicians-7677.html plain text: ethereummagicians-7677.txt item: #922 of 3327 id: ethereummagicians-8300 author: ethereummagicians title: ethereummagicians-8300 date: None words: 3491 flesch: 68 summary: Let me list them one-by-one: Q1: For address from name service, should we use name type or address type? Using address type for both conventional 0x-20-bytes-hex ETH address space and name from NS should work as ETH address will never have “.”, but should we separate these types for better clarification? Q2: Do we need type auto-detection, i.e., do we need the simpler URI at the price of potential ambiguity? keywords: address; contract; qizhou; samwilsn; types; web3 cache: ethereummagicians-8300.html plain text: ethereummagicians-8300.txt item: #923 of 3327 id: ethresear-1 author: ethresear title: ethresear-1 date: None words: 7061 flesch: 58 summary: Block validity enforcement – Relays check builder blocks for validity. For (i) we can use the Payload-Timeliness Committee (abbr. PTC) to enforce that builder blocks are included if they are made available on time (though other designs like Two-slot and PEPC are also possible). keywords: bid; block; builder; epbs; mev; payment; proposer; protocol; relay cache: ethresear-1.html plain text: ethresear-1.txt item: #924 of 3327 id: ethresear-10035 author: ethresear title: ethresear-10035 date: None words: 886 flesch: 58 summary: Improving security for users of DeFi services/DEXs through MPC/threshold signatures - Security - Ethereum Research Ethereum Research Improving security for users of DeFi services/DEXs through MPC/threshold signatures Security ra July 8, 2021, 10:08am 1 Excited to finally have our paper out that describes a protocol for improving security for users of DeFi services/DEXs through MPC/threshold signatures. Hope it helps to have more alternatives: GitHub - CoinFabrik/wasm-multi-party-ecdsa: Full WASM Secure Threshold Signature ECDSA Library MaxC August 12, 2023, 1:15pm 8 ra: Excited to finally have our paper out that describes a protocol for improving security for users of DeFi services/DEXs through MPC/threshold signatures. keywords: protocol; security cache: ethresear-10035.html plain text: ethresear-10035.txt item: #925 of 3327 id: ethresear-10087 author: ethresear title: ethresear-10087 date: None words: 155 flesch: 52 summary: Scaling EVM: Overview - Miscellaneous - Ethereum Research Ethereum Research Scaling EVM: Overview Miscellaneous miohtama July 15, 2021, 3:58am 1 Hi, I wrote an overview blog post on different EVM chains and L2s: the settings and tradeoffs they make, what problems are currently being researched and what innovation there exist outside the Ethereum ecosystem that could be adopted. While the post might be technical enough for the readers of this forum to discuss details, it should give a good high-level view of different competing EVM chains and layer two solutions available at the markets at the moment. keywords: evm cache: ethresear-10087.html plain text: ethresear-10087.txt item: #926 of 3327 id: ethresear-10133 author: ethresear title: ethresear-10133 date: None words: 107 flesch: 60 summary: Historical Node Count Data - Execution Layer Research - Ethereum Research Ethereum Research Historical Node Count Data Execution Layer Research satoshi-source July 20, 2021, 10:06pm 1 Hello researchers, I am looking to put together a basic Metcalf’s Law visualization (market cap vs # of nodes squared), but I cannot find historical data for node count. Does anyone know where I can find historical node count data? keywords: data cache: ethresear-10133.html plain text: ethresear-10133.txt item: #927 of 3327 id: ethresear-1014 author: ethresear title: ethresear-1014 date: None words: 1828 flesch: 59 summary: IMO it’s the best approach I’ve seen to scalable governance, and it introduces some very interesting concepts: http://www.idni.org/blog/the-new-tau jamesray1 February 8, 2018, 12:11am 7 Holographic consensus — decentralized governance at scale - governance - Ethereum Research Ethereum Research Holographic consensus — decentralized governance at scale governance fmatan February 7, 2018, 9:10am 1 A critical but still missing element for successful implementation of DAOs and collaborative DApps is a decentralized governance system: an efficient and resilient engine for collective decision-making, at scale. keywords: february; governance; users; verdict cache: ethresear-1014.html plain text: ethresear-1014.txt item: #928 of 3327 id: ethresear-10161 author: ethresear title: ethresear-10161 date: None words: 798 flesch: 60 summary: Most EEI method implementations would be constant time and fast, but it would still be some constant multiple overhead. Plan of attack Do a survey of EEI definitions in different languages. keywords: eei; evm cache: ethresear-10161.html plain text: ethresear-10161.txt item: #929 of 3327 id: ethresear-10259 author: ethresear title: ethresear-10259 date: None words: 4045 flesch: 52 summary: That is, CONSENSUS takes as input, instead of a validator set, a function get_validator_set(view_number: int) -> Map[Validator, int] (the int representing the validator’s balance) that can generate validator sets for new views. This preserves all of the above properties, but it also introduces a new property: if a block gets multiple confirmations (ie. that block gets finalized, and a chain of its descendants gets k-1 more confirmations, for a total of k sequential confirmations that affect that block), then reverting that block requires violating the consensus guarantee in multiple committees. keywords: block; committee; consensus; eth; finality; slot; validator cache: ethresear-10259.html plain text: ethresear-10259.txt item: #930 of 3327 id: ethresear-10274 author: ethresear title: ethresear-10274 date: None words: 951 flesch: 70 summary: <5% ++++++++++ 20% 5-25% +++++++++ 18% 25-75% ++++++++++++++++++++ 40% 75-95% ++ 4% 95%+ ++++++++++++++ 28% Base fee on blocks 12967650 and 12967700 is equal to 42 GWEI, but it was changing from 37 to 51 (almost 20% difference from “correct” value) during this 10 minutes, just because of the way how it is calculated and the way how miners fill blocks. EIP-1559 is not making fees predictable - Miscellaneous - Ethereum Research Ethereum Research EIP-1559 is not making fees predictable Miscellaneous eip-1559 DimOK August 5, 2021, 11:11pm 1 Long-anticipated EIP-1559 is up and running, but I am disappointed. keywords: + + cache: ethresear-10274.html plain text: ethresear-10274.txt item: #931 of 3327 id: ethresear-10292 author: ethresear title: ethresear-10292 date: None words: 1341 flesch: 64 summary: The participants of such a protocol would be: Block producers Block producers verifiers Users/Searchers Such a key could be generated and split accross the protocol where the number of it’s block producers and cerifiers is known. Also the proposal assumes that Searchers/Users are willing to pay higher gasPrice than usual, in order to incentivise block producers to participate in the network. keywords: block; producer; protocol cache: ethresear-10292.html plain text: ethresear-10292.txt item: #932 of 3327 id: ethresear-10303 author: ethresear title: ethresear-10303 date: None words: 1135 flesch: 49 summary: Apsis Consensus Blockchain data is retroactively verifiable, but HTTP data is not. Background Current blockchain applications rely on so-called off-chain Oracles to access external data, such as asset price in centralized exchanges. keywords: chain; data; http; oracle cache: ethresear-10303.html plain text: ethresear-10303.txt item: #933 of 3327 id: ethresear-10305 author: ethresear title: ethresear-10305 date: None words: 7296 flesch: 70 summary: So the more likely problem is the inefficiency of markets in pricing new proposals. But I think even that doesn’t matter so much because on average, good proposals will win out over bad ones. keywords: attacker; buy; price; proposal; token; vote; voters; voting cache: ethresear-10305.html plain text: ethresear-10305.txt item: #934 of 3327 id: ethresear-10310 author: ethresear title: ethresear-10310 date: None words: 519 flesch: 66 summary: Did EIP-1559 increase gas prices? - Execution Layer Research - Ethereum Research Ethereum Research Did EIP-1559 increase gas prices? keywords: august; gas cache: ethresear-10310.html plain text: ethresear-10310.txt item: #935 of 3327 id: ethresear-10323 author: ethresear title: ethresear-10323 date: None words: 454 flesch: 58 summary: Thus we’d expect block validators to be much more geographically mobile than the current block miners. Will PoS result in the geographic clustering of validators? keywords: block; validators cache: ethresear-10323.html plain text: ethresear-10323.txt item: #936 of 3327 id: ethresear-10352 author: ethresear title: ethresear-10352 date: None words: 1458 flesch: 66 summary: dAMM: An L2-Powered AMM - Layer 2 - Ethereum Research Ethereum Research dAMM: An L2-Powered AMM Layer 2 zk-roll-up Brecht August 16, 2021, 4:37pm 1 Main goals of the implementation Should be very easy to share liquidity with as few direct dependencies between L2s Deterministic so AMM operations never have to be reverted because of unexpected state changes Aim for IL comparable to a Uniswap V2 style AMM Context - AMM, Amplified AMM & Impermanent Loss AMM The standard AMM curve with 2 assets X and Y with respective balances x and y follows x*y = k. When ignoring trading fees, k is invariant when trading against the AMM. An amplified AMM is an AMM that operates on virtual balances, as opposed to UniswapV2 AMM that operates on current balances. keywords: amm; balances cache: ethresear-10352.html plain text: ethresear-10352.txt item: #937 of 3327 id: ethresear-10367 author: ethresear title: ethresear-10367 date: None words: 489 flesch: 56 summary: For other blockchains, Common Coin can be derived through VDF, which may delay execution a bit … 2 Likes MicahZoltu August 19, 2021, 12:45pm 2 Random transaction ordering incentivizes “shotgun” MEV, which is where you just submit dozens or hundreds of transactions and rely on probability getting your transaction at the head of the block. 1 Like kladkogex August 20, 2021, 12:56pm 4 This one is not hard to solve - you order transactions by HASH(sender | common coin) And for the same sender you sort by nonce … kladkogex August 20, 2021, 12:57pm 5 Interesting point … By isnt it going to cost lots of gas ? keywords: august cache: ethresear-10367.html plain text: ethresear-10367.txt item: #938 of 3327 id: ethresear-10385 author: ethresear title: ethresear-10385 date: None words: 1660 flesch: 54 summary: It is unsure if curation (removal of such arguments) can fully compensate this. Deliberative Decision-Making using Argument Trees - Applications - Ethereum Research Ethereum Research Deliberative Decision-Making using Argument Trees Applications dao, governance mheuer August 21, 2021, 4:51pm 1 This write-up proposes a deliberative voting algorithm based on argument trees that could be used in DAOs and aims to produce more well-informed decisions. keywords: argument; debate; decision; impact cache: ethresear-10385.html plain text: ethresear-10385.txt item: #939 of 3327 id: ethresear-10394 author: ethresear title: ethresear-10394 date: None words: 1259 flesch: 57 summary: maxareo August 23, 2021, 1:34pm 3 Inverse CDF is a common tool in generating random numbers, however, it would be challenging to express it and apply it on-chain cheaply. Is there a better way, e.g. something more like arithmetic coding? (b) One innovation would be to get several random numbers out of a single 256-bit hash, depending on how much accuracy is needed. keywords: algorithm; august; gaussian cache: ethresear-10394.html plain text: ethresear-10394.txt item: #940 of 3327 id: ethresear-10435 author: ethresear title: ethresear-10435 date: None words: 445 flesch: 73 summary: slope = ether in dividends / ether in pyramid If someone attacks the resolve supply, the pyramid will steepen as people sell bonds to meet the demand for resolve tokens. The amount of resolve tokens a user receives is based on a “loss” & “hodl” multiplier. keywords: resolve cache: ethresear-10435.html plain text: ethresear-10435.txt item: #941 of 3327 id: ethresear-10446 author: ethresear title: ethresear-10446 date: None words: 2446 flesch: 65 summary: Batching works well when the distribution of trade sizes is concentrated, however, it works quite poorly when there is one trade whose size is much large than the rest, e.g. a sequence of T trades (T, 1, \ldots 1) \in \mathbb{R}^T. For instance, if one adds \xi_i \sim \mathsf{N}(0, \sigma^2) noise to each trade size and/or price, then with a large enough set of trades, it is possible to denoise trade sizes. keywords: \ldots; function; noise; privacy; trade cache: ethresear-10446.html plain text: ethresear-10446.txt item: #942 of 3327 id: ethresear-10756 author: ethresear title: ethresear-10756 date: None words: 599 flesch: 69 summary: It would thus be relevant to explore questions and spark discussions on these values which are deeply embedded in the crypto and more specifically the Ethereum space, so that newcomers and long standing experts alike can explore this ‘infinite garden’ to greater depths. Proposal: Add a new category for 'Philosophy' - Administrivia - Ethereum Research Ethereum Research Proposal: Add a new category for 'Philosophy' Administrivia SHSR2001 September 16, 2021, 7:58am 1 As we all know quite well, Ethereum is more than just a technology stack. keywords: ethereum; september cache: ethresear-10756.html plain text: ethresear-10756.txt item: #943 of 3327 id: ethresear-10772 author: ethresear title: ethresear-10772 date: None words: 3036 flesch: 72 summary: Use prediction markets to determine which decision optimizes those metrics, and take it. Can we do governance combining auctions with prediction markets? keywords: futarchy; paper; payment; prediction; proposal cache: ethresear-10772.html plain text: ethresear-10772.txt item: #944 of 3327 id: ethresear-10774 author: ethresear title: ethresear-10774 date: None words: 3046 flesch: 56 summary: So some estimate on how much money do we require the DDOSer burn to take down the website for how many minutes or hours. by using twitter directly to Sign in the users, and then just use the oauth tokens, Basically twitter can issue “anonymous oauth” tokens - twitter can tell you that a twitter user has signed in but not which twitter user, blagoj November 15, 2021, 9:28pm 8 samueldashadrach: Yep, but I thought knowing the order of magnitude would still be useful. InterRep is a service for linking user web3 identities with their reputable social media accounts. keywords: limiting; rate; rln; service; twitter; user cache: ethresear-10774.html plain text: ethresear-10774.txt item: #945 of 3327 id: ethresear-1080 author: ethresear title: ethresear-1080 date: None words: 355 flesch: 60 summary: Proof of study or work a GID, “global industry DoW” governed by IDnft union holders will have a lifelong ability to utilize the dow union for retirement or change of industry time is ongoing for all holding Gi union IDnft time + level = Benefits from the Global DoW union funds. Use the following paragraphs for a longer description, or to establish category guidelines or rules: Why should people use this category? keywords: category; dow cache: ethresear-1080.html plain text: ethresear-1080.txt item: #946 of 3327 id: ethresear-10813 author: ethresear title: ethresear-10813 date: None words: 1282 flesch: 51 summary: Advantages of Crosschain Layered Architecture Having a layered architecture with clearly defined interfaces between layers has the following advantages: Different organisations can create Crosschain Message Verification, Crosschain Function Call technology, and Crosschain Applications that will be interoperable. Different Crosschain Function Call techniques can share the same deployed Crosschain Message Verification infrastructure. keywords: blockchain; crosschain; function cache: ethresear-10813.html plain text: ethresear-10813.txt item: #947 of 3327 id: ethresear-10980 author: ethresear title: ethresear-10980 date: None words: 8066 flesch: 59 summary: To help them with this, the censorship market allows bids on n block censorship (in this case 50), or even using a specialist OpenSea censorship order. Your response that such as attack is uneconomical does not account for the fact that censoring transactions can have large and unquantifiable private value to the censor and that once established that value may be self-reinforcing. keywords: block; builder; censorship; market; mev; relayer; slot; time; transactions; users cache: ethresear-10980.html plain text: ethresear-10980.txt item: #948 of 3327 id: ethresear-11 author: ethresear title: ethresear-11 date: None words: 1141 flesch: 69 summary: Ethresear.ch: email login will be disabled in 7 days - #11 by hwwhww - Administrivia - Ethereum Research Ethereum Research Ethresear.ch: email login will be disabled in 7 days Administrivia hwwhww May 8, 2020, 7:28am 1 Thank you for using etheresear.ch forum! Email login was enabled during the last time we restored the system. keywords: account; ens cache: ethresear-11.html plain text: ethresear-11.txt item: #949 of 3327 id: ethresear-11020 author: ethresear title: ethresear-11020 date: None words: 2124 flesch: 68 summary: We kept the core, sensitive transactional logic in the USM and FUM contracts, and carved out peripheral dependent logic into separate contracts with no special permissions: USMView for those (eg, UIs) that just want to grab handy view stats like the current debt ratio, and USMWETHProxy for users who want to operate on WETH rather than ETH. Immutable contracts? keywords: contract; eth; oracle; uniswap; usm cache: ethresear-11020.html plain text: ethresear-11020.txt item: #950 of 3327 id: ethresear-11031 author: ethresear title: ethresear-11031 date: None words: 1289 flesch: 70 summary: Make everyone the coordinator os everyone can have private transaction. Option 1 is recording all of transaction history data to txcalldata. keywords: state; user cache: ethresear-11031.html plain text: ethresear-11031.txt item: #951 of 3327 id: ethresear-11033 author: ethresear title: ethresear-11033 date: None words: 4720 flesch: 65 summary: Note that it is not necessary to add all 1000 transfers in the same rollup block, she may continue to add pending transactions in many rollup blocks before calling ProcessTransactions. After rollup block 123 is published on-chain, the operator sends a witness of the newly added pending transaction to Alice. keywords: alice; block; operator; rollup; state cache: ethresear-11033.html plain text: ethresear-11033.txt item: #952 of 3327 id: ethresear-11054 author: ethresear title: ethresear-11054 date: None words: 514 flesch: 42 summary: The applications of the Merklized ERC20 maybe On-chain voting - a governance proposal voting can cheaply take a snapshot of the ERC20 and count the vote on-chain based on snapshot instead of maintaining all history of ERC20 balance change (Compound) or off-chain snapshot. Efficient On-Chain Dynamic Merkle Tree - Data Structure - Ethereum Research Ethereum Research Efficient On-Chain Dynamic Merkle Tree Data Structure qizhou October 19, 2021, 7:58pm 1 Abstract Following the stateless client idea, we implement an efficient on-chain dynamic Merkle tree with on-chain inclusive verification; on-chain append / in-place update; O(1) cost in storage space; O(1) storage write cost for update / append operations. keywords: chain; tree cache: ethresear-11054.html plain text: ethresear-11054.txt item: #953 of 3327 id: ethresear-11074 author: ethresear title: ethresear-11074 date: None words: 1320 flesch: 67 summary: If this is non-trivial to make, we can’t enforce users to stick with one GitHub account since GitHub email can be changed. Ethresear.ch: email login will be disabled in 7 days To mitigate spam and impersonator attacks, we decide to disable email login again and you can only log in with GitHub account. keywords: account; github cache: ethresear-11074.html plain text: ethresear-11074.txt item: #954 of 3327 id: ethresear-11127 author: ethresear title: ethresear-11127 date: None words: 2867 flesch: 57 summary: Adversary can split committees in half by catching honest proposal early and then targeting p2p network in coordinated fashion: Release ‘sway votes’ (attestations) such that half of the committee hears them before they hear the latest block and run their fork choice including the adversarial sway vote (and hence vote for adversarial block); the other half of the committee hears the sway vote after they have heard the honest block already (and hence run their fork choice already and vote for honest block). On a high level, there are two things that the new fork choice rule prevents: balancing attack (splitting validators into different views) and concluding reorg attacks (winning over majority of honest validators by releasing block/attestations after observing honest block). keywords: block; choice; fork; proposer cache: ethresear-11127.html plain text: ethresear-11127.txt item: #955 of 3327 id: ethresear-11340 author: ethresear title: ethresear-11340 date: None words: 123 flesch: -7 summary: May 6, 2022 Layer 2 crosslinks, cross-shard drinkcoffee November 25, 2021, 7:28am 1 ICBC Crosschain Workshop 2022 is seeking submissions of technical papers and industry talks in the following areas related to Crosschain Communications: Crosschain bridges Crosschain applications protocols Crosschain function call protocols Crosschain consensus protocols Crosschain cryptoeconomic design Other crosschain communications protocols For more details about this online workshop, see: Call for Workshop Papers & Talks | 2022 IEEE ICBC | IEEE International Conference on Blockchain and Cryptocurrency Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled IEEE International Conference on Blockchain and Cryptocurrency: Crosschain Workshop: May 6, 2022 - Layer 2 - Ethereum Research Ethereum Research IEEE International Conference on Blockchain and Cryptocurrency: Crosschain Workshop: keywords: crosschain cache: ethresear-11340.html plain text: ethresear-11340.txt item: #956 of 3327 id: ethresear-11356 author: ethresear title: ethresear-11356 date: None words: 1804 flesch: 63 summary: It is curren illuzen December 1, 2021, 6:14am 5 It’s important to point out that finding address collisions is not the same as finding a public key collision. What would break if we lose address collision resistance? keywords: address; collision; funds; user cache: ethresear-11356.html plain text: ethresear-11356.txt item: #957 of 3327 id: ethresear-11379 author: ethresear title: ethresear-11379 date: None words: 461 flesch: 61 summary: This is an approach Constitution DAO could have taken using Obscuro: Create a contract that holds the funds on Obscuro, inflows/outflows, and the total balance would be known to nobody, all hidden away in encrypted rollups on Ethereum and inside secure TEEs. The technical challenges include 1) how to hide the amount of donated coins on-chain, 2) how can the manager verify the amount claimed by the donators, and 3) how to trigger the events. keywords: treasury cache: ethresear-11379.html plain text: ethresear-11379.txt item: #958 of 3327 id: ethresear-11416 author: ethresear title: ethresear-11416 date: None words: 2546 flesch: 55 summary: And not enough people are using smart contract wallets, otherwise we’d be able to solve the problem from that end. illuzen December 28, 2021, 3:49am 13 I disagree with the problem description, the proper implementation of the proposed security function should also protect against malicious contracts. keywords: chain; checksum; dapp; december; github; metamask cache: ethresear-11416.html plain text: ethresear-11416.txt item: #959 of 3327 id: ethresear-11527 author: ethresear title: ethresear-11527 date: None words: 173 flesch: 59 summary: Requesting a read-only Discourse API key for monitoring new protocol upgrade discussions - Administrivia - Ethereum Research Ethereum Research Requesting a read-only Discourse API key for monitoring new protocol upgrade discussions Administrivia teddyknox December 17, 2021, 4:56am 1 Hello, I’m representing the Stakefish Validator Group and we’re building an internal api (that we plan to open source) with the goal of having an up-to-date list of protocol upgrade discussions for the Ethereum ecosystem. Thanks, Teddy Knox Stakefish 1 Like disruptionjoe April 13, 2022, 11:51pm 3 did you build this already? keywords: ethereum cache: ethresear-11527.html plain text: ethresear-11527.txt item: #960 of 3327 id: ethresear-11549 author: ethresear title: ethresear-11549 date: None words: 2058 flesch: 63 summary: In the child RAM we can read/write single bytes of the 32-byte words contained at word multiple addresses - hence, in a single row we can either read/modify a single byte of a 32-byte word, or read/replace the full 32-byte word contained at a given word multiple address (optimization for requests that have a zero interior offset). Besides, one has to initialize the new RAM (and in some cases the new Storage) of the contract being called - the number of clockcycles will scale linearly with the total maximum size of the RAM (in EVM words) at the end of execution of the called contract (for the storage it will scale linearly with the number of storage cells accessed). keywords: address; read; word; write cache: ethresear-11549.html plain text: ethresear-11549.txt item: #961 of 3327 id: ethresear-11588 author: ethresear title: ethresear-11588 date: None words: 1458 flesch: 65 summary: The basic idea is to use SNARK aggregation in a way similar to signature aggregation, so that an aggregated SNARK can compactly encode which nodes have voted for a block. Leveraging SNARK proof aggregation to achieve large scale PBFT-based consensus - zk-s[nt]arks - Ethereum Research Ethereum Research Leveraging SNARK proof aggregation to achieve large scale PBFT-based consensus zk-s[nt]arks zk-roll-up, layer-2 jieyilong December 25, 2021, 7:02am 1 PBFT-based consensus protocols provide some good properties such as fast finality over chain-based protocols (e.g. Bitcoin, Cardano Ouroboros), but they typically don’t scale well with the number of nodes participating in the consensus. keywords: aggregation; proof; snark cache: ethresear-11588.html plain text: ethresear-11588.txt item: #962 of 3327 id: ethresear-11763 author: ethresear title: ethresear-11763 date: None words: 8266 flesch: 59 summary: Bootstrapping In all previous sections, we’ve been assuming that the system has bootstrapped and that all validators have Whisk trackers and commitments associated with them. This means that the system starts in an insecure state where the adversary can predict future proposers (similar to the status quo), and as more validators register secure commitments, the system gradually reaches a secure steady state. keywords: anonymity; attacks; block; consensus; proposer; protocol; randao; set; shuffling; ssle; validators; whisk cache: ethresear-11763.html plain text: ethresear-11763.txt item: #963 of 3327 id: ethresear-118 author: ethresear title: ethresear-118 date: None words: 1382 flesch: 72 summary: Like virgil October 5, 2017, 8:49am 3 Well, there are already invite-only Skype chat rooms for Ethereum research. Under my passworded version, obviously the board will be open to pretty much anyone who is active in ethereum research—there’s no desire for exclusion, merely not having to worry our off the cuff comments will end up on coindesk. keywords: ethereum; october; research cache: ethresear-118.html plain text: ethresear-118.txt item: #964 of 3327 id: ethresear-11833 author: ethresear title: ethresear-11833 date: None words: 2355 flesch: 39 summary: The insecura network On the pyrmont network, there are ~120k validators - a malicious duck has taken control of 12000 of them, and is now generating its own little consensus world, called insecura! To achieve finality (to make the attack look credible), the effective stake of our 12000 validators needs to become the 2/3 majority, meaning that we need to bleed out a large enough part proportion of the other ~108k validators by first leaking their balance, then having them go through the exit procedure - the exact number of validators that must be leaked depends on their balance: their attestation and block production work is weighted by it. keywords: chain; network; pyrmont; state; validators cache: ethresear-11833.html plain text: ethresear-11833.txt item: #965 of 3327 id: ethresear-11853 author: ethresear title: ethresear-11853 date: None words: 1317 flesch: 60 summary: As a result, their vote is tied—Left increases by roughly half of honest votes and Right increases by roughly half of honest votes. Then, a handful of adversarial votes per slot, released under particular circumstances, suffice to steer honest validators’ votes so as to keep the system in a tie between the two chains and consequently stall consensus. keywords: validators; votes cache: ethresear-11853.html plain text: ethresear-11853.txt item: #966 of 3327 id: ethresear-11854 author: ethresear title: ethresear-11854 date: None words: 1858 flesch: 62 summary: Overall, the adversary gets to displace O(k^2) honest blocks with k withheld adversarial blocks. On average, more honest blocks are produced than adversary blocks, so the developing honest chain eventually ‘catches up’ with the k withheld adversarial blocks. keywords: adversary; attack; blocks; ghost cache: ethresear-11854.html plain text: ethresear-11854.txt item: #967 of 3327 id: ethresear-11877 author: ethresear title: ethresear-11877 date: None words: 988 flesch: 51 summary: The second can be managed by splitting committees into many subnets, and the third can be managed by making sure that there are not too many payloads (eg. allow each builder to propose a max 3 per block, and increase the min deposit to be a builder). Depends on majority being online to decrypt (possible fix: choose committee from validators present in previous epoch) Requires more cryptographic primitives that have not yet been implemented (standardized asymmetric encryption) Variant (1) of integration with sharding makes it much harder to make a distributed builder (because of the need to encrypt full bodies of the extension) Variant (2) of integration with sharding does not seem to preserve pre-publication zero knowledge of bundles (though maybe pre-publication zero knowledge of _the choice of which bundles_is good enough) 5 Likes terence January 29, 2022, 8:04pm 2 1.) keywords: builder; committee; slot cache: ethresear-11877.html plain text: ethresear-11877.txt item: #968 of 3327 id: ethresear-11883 author: ethresear title: ethresear-11883 date: None words: 305 flesch: 59 summary: Merging PoW and PoS would prevent possibility of another hardfork by PoW miners after ETH moves to PoS, also it supports the PoW miners who had been supporting the network since its infancy, instead of ditching miners entirely wouldn’t it be better to integrate them into a new system where PoS and PoW can work in parallel, supporting each other. Discussion: 2-hop Blockchain, Combining PoW and PoS Securely on ETH (EIPxxxx) - Consensus - Ethereum Research Ethereum Research Discussion: 2-hop Blockchain, Combining PoW and PoS Securely on ETH (EIPxxxx) Consensus sam256 January 28, 2022, 7:43am 1 Instead of moving ETH entirely from PoW to PoS Consensus mechanism, would it be possible to merge both PoW and PoS in parallel on 2-hop Blockchain like the one theorized here https://eprint.iacr.org/2016/716.pdf (2-hop Blockchain: Combining Proof-of-Work and Proof-of-Stake Securely). keywords: pow cache: ethresear-11883.html plain text: ethresear-11883.txt item: #969 of 3327 id: ethresear-11953 author: ethresear title: ethresear-11953 date: None words: 8363 flesch: 59 summary: Detail-4: Generate Bitcoin deposit address The Bitcoin deposit address generator creates a pair of a new secret key, a public key, and a Bitcoin deposit address. The WE scheme enables us to encrypt a secret key of Bitcoin addresses holding the deposited bitcoins, while requiring witness of WBTC amortization on the Ethereum blockchain to decrypt the ciphertext. keywords: address; bitcoin; block; blockchain; deposit; deposit address; ethereum; key; proof; signature; user; wbtc; witness cache: ethresear-11953.html plain text: ethresear-11953.txt item: #970 of 3327 id: ethresear-11953?page=2 author: ethresear title: ethresear-11953?page=2 date: None words: 395 flesch: 62 summary: The current Ethereum PoS network is maintained by a group of validators, say it’s group A. or A plan to implement it? leohio December 17, 2023, 8:41am 27 devfans: Alice deposits 1 BTC to a deposit address generated by the generators and gets the ciphertext CT, and then mints 1 WBTC on the Ethereum chain. keywords: ethereum cache: ethresear-11953?page=2.html plain text: ethresear-11953?page=2.txt item: #971 of 3327 id: ethresear-11962 author: ethresear title: ethresear-11962 date: None words: 621 flesch: 55 summary: Access to CALLDATA of non-current call frames and alternative methods of token-use authorization - EVM - Ethereum Research Ethereum Research Access to CALLDATA of non-current call frames and alternative methods of token-use authorization EVM wdai February 7, 2022, 8:57pm 1 Background In ERC20-based DeFi workflows, users interact with application contracts (e.g. Uniswap) that then invoke token contracts (ERC20) to transfer tokens on users’ behalf. ERC677 proposes transferAndCall, which changes the workflows of current ERC20-based protocols, in that users would interact with token contracts instead of application contracts. keywords: authorization; calldata cache: ethresear-11962.html plain text: ethresear-11962.txt item: #972 of 3327 id: ethresear-12 author: ethresear title: ethresear-12 date: None words: 127 flesch: 57 summary: GitHub GitHub - ethereum/casper: Casper contract, and related software and tests Casper contract, and related software and tests. About the Proof-of-Stake category - Proof-of-Stake - Ethereum Research Ethereum Research About the Proof-of-Stake category Proof-of-Stake vbuterin_old August 17, 2017, 11:10pm 1 Discussion related to Proof-of-Stake (PoS). keywords: ethereum cache: ethresear-12.html plain text: ethresear-12.txt item: #973 of 3327 id: ethresear-120 author: ethresear title: ethresear-120 date: None words: 1817 flesch: 71 summary: IMO Ethereum logo to be used as currency symbol would look odd among other currency symbols attachedhttps://unicode.org/charts/PDF/Unicode-10.0/U100-20A0.pdf For a long time, we market ETHER as ‘fuel’, crypto-fuel etc, and NOT as currency the old/new let’s-not-upset bitcoiner language drhus August 1, 2018, 3:30pm 11 To move this forward aiming to include ETHER as currency symbol added to Unicode Standard: We need to decide on ETHER symbol 0%20(1)168×933 63.3 KB IMO, Ethereum logo, looks nothing like a currency symbol, we could have ETHER Symbol as separate something from Ethereum Logo, currently we’re using Ξ Greek uppercase Xi character apparently didn’t get traction, why? keywords: currency; ether; symbol cache: ethresear-120.html plain text: ethresear-120.txt item: #974 of 3327 id: ethresear-12021 author: ethresear title: ethresear-12021 date: None words: 413 flesch: 23 summary: The Work: Java Smart Contract Abstraction for Ethereum R&D Java Smart Contract Abstraction for Ethereum 2 Likes Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled In Java, a dependency is created to suplement for the Solidity keyword as follows: Uint256 Java Dependency (in place of uint Solidity Keyword) example: public interface Uint256 { static byte[] ivBytes = new byte[256]; static int iterations = 65536; static int keySize = 256; static byte[] uint = new byte[256]; public default void Uint256() throws Exception { decrypt(); } public static void decrypt() throws Exception { char keywords: java cache: ethresear-12021.html plain text: ethresear-12021.txt item: #975 of 3327 id: ethresear-12120 author: ethresear title: ethresear-12120 date: None words: 1730 flesch: 82 summary: At block 14,600,000, which happened this week, we entered into period 39, which based on previous bombs is when we usually start seeing a diminishment in block times. It’s reasonable to estimate its future progress based on previous bombs. image1920×1363 199 KB 3 Likes CryptoWhite May 7, 2022, 1:30am 18 I guess a new hardfork for delaying the difficulty bomb is around the corner jgm May 11, 2022, 6:40am 19 On the basis of daily block time we’re already at the point where Arrow Glacier kicked in. keywords: bomb; quickblocks; utc cache: ethresear-12120.html plain text: ethresear-12120.txt item: #976 of 3327 id: ethresear-12153 author: ethresear title: ethresear-12153 date: None words: 1251 flesch: 64 summary: the anonymity of DAO participants is guaranteed, and only when a whistleblower is identified, the anonymity of the accused is revoked. I believe that fraud and disputes do not surface on the on-chain, but on Web 2.0, such as the discord ch we have established for each DAO. keywords: dao; fraud; web cache: ethresear-12153.html plain text: ethresear-12153.txt item: #977 of 3327 id: ethresear-12156 author: ethresear title: ethresear-12156 date: None words: 823 flesch: 56 summary: If the bond is traded to Claire on Solana, Claire is now eligible to receive bond payments and no longer Bob. Unfortunately, such digital assets can currently not be transferred between networks because a transfer would break the connection between the asset, and the rights or obligations associated with it. keywords: l1 <; l2 < cache: ethresear-12156.html plain text: ethresear-12156.txt item: #978 of 3327 id: ethresear-12158 author: ethresear title: ethresear-12158 date: None words: 1650 flesch: 53 summary: In the transaction phase, users use the transaction class of Cloak Client to interact with the blockchain and Cloak Network to send private transactions, as well as the MPT. when a normal transaction is packaged in a block, its transaction parameters, old states, function logic, return values, and new states are all public; therefore, we call it PUT (public transaction). keywords: cloak; mpt; public; transaction cache: ethresear-12158.html plain text: ethresear-12158.txt item: #979 of 3327 id: ethresear-12194 author: ethresear title: ethresear-12194 date: None words: 322 flesch: 31 summary: Language Examples Smart-Contract Storage example in Solidity pragma solidity >=0.4.16 <0.9.0; contract SimpleStorage { uint storedData; function set(uint x) public { storedData = x; } function get() public view returns (uint) { return storedData; } } Smart-Contract Storage example in Jehova public class SimpleStorage { private Uint256 storedData; public void setStoredData (Uint256 storedData) { this.storedData = storedData; } public Uint256 getStoredData () { return storedData; } } forked from: Java Smart Contract Abstraction for Ethereum setunapo March 23, 2022, 2:19pm 2 Will Jehova be compiled to EVM opcode? Thus, allowing Smart-Contracts to be built in a language familiar with Java developers would help onboard more developers into the Ethereum Ecosystem. keywords: java; jehova cache: ethresear-12194.html plain text: ethresear-12194.txt item: #980 of 3327 id: ethresear-12220 author: ethresear title: ethresear-12220 date: None words: 408 flesch: 67 summary: There have been some other proposals as well like sponsored transactions, but I think something else is likely to win out over those. These are both more generalized/broad solutions to the problem of transaction signer needing to be the one who pays gas. keywords: transaction cache: ethresear-12220.html plain text: ethresear-12220.txt item: #981 of 3327 id: ethresear-12249 author: ethresear title: ethresear-12249 date: None words: 5770 flesch: 63 summary: The problem is that the block producer should have a guarantee how much they’ll get paid in transaction fees at the time they build the blocks. The problem is that the block producer should have a guarantee how much they’ll get paid in transaction fees at the time they build the blocks. keywords: block; fees; gas; key; mev; slippage; transactions; uniswap cache: ethresear-12249.html plain text: ethresear-12249.txt item: #982 of 3327 id: ethresear-12315 author: ethresear title: ethresear-12315 date: None words: 2508 flesch: 63 summary: I hence modded your simulation script to support offline validators: I’m attaching a table (like yours above) but just for the width=2048/swaps=31 configuration with various percentages of offline shufflers, while also estimating the number of nodes that correspond to that anonymity set (using a 20%-80% Pareto distribution). Parameters Parameter Recommended value Notes WIDTH 2048 SWAP_TREE_DEPTH 5 2**depth - 1 swaps per slot Construction We maintain in the state an array of blinded commitments: blinded_commitments: Vector[BlindedCommitment, WIDTH]. keywords: commitment; shuffle; swap; validator cache: ethresear-12315.html plain text: ethresear-12315.txt item: #983 of 3327 id: ethresear-12345 author: ethresear title: ethresear-12345 date: None words: 5909 flesch: 55 summary: The investment fund would be able to communicate about this, improving its reputation and the reputation of Ethereum : it could be NGO fighting for climate (because Ether staking is a green and energy efficient process), NGO for social welfare, NGO about cultural and artistic activities, … This separation of capital holders and node operators would therefore help Ethereum to spread, and would be very good for decentralization. On the contrary, if there is no possible separation between capital holders and node operators, capital holders will be much more cautious due to the increased risk of losing their capital in the process of staking. keywords: address; capital; ethereum; ethers; node; revenue; staking cache: ethresear-12345.html plain text: ethresear-12345.txt item: #984 of 3327 id: ethresear-12348 author: ethresear title: ethresear-12348 date: None words: 650 flesch: 50 summary: Open-source Data Analytics of Ethereum Staking Pools - Data Science - Ethereum Research Ethereum Research Open-source Data Analytics of Ethereum Staking Pools Data Science icydark April 6, 2022, 9:59am 1 TL;DR We conduct an open-source data analysis on Ethereum staking pools. Several projects are working on analyzing Ethereum staking pools, like rated.network, beaconcha.in, ethereumpools.info, pools.invis.cloud, and showing different analyzing results. keywords: data; staking cache: ethresear-12348.html plain text: ethresear-12348.txt item: #985 of 3327 id: ethresear-1235 author: ethresear title: ethresear-1235 date: None words: 1409 flesch: 62 summary: kladkogex March 2, 2018, 5:04pm 4 I think it is more to stimulate incremental progress in math … As far a quantum computers go they are totally impractical - I guess the reason why CS people like talking about quantum computers is because they never took quantum mechanics We all already use quantum computers JustinDrake March 2, 2018, 6:13pm 5 nate: hiding their quantum computer and then breaking everything The quantum race is led by established companies (IBM, Intel, Microsoft, Google), startups (Rigetti, IonQ, Quantum Circuits) and possibly governments (NSA, GCHQ). keywords: canary; primitives; protocol; quantum cache: ethresear-1235.html plain text: ethresear-1235.txt item: #986 of 3327 id: ethresear-12355 author: ethresear title: ethresear-12355 date: None words: 2371 flesch: 61 summary: We can run a transaction with this EVM and record potential state accesses. In the Portal Network, Ethereum state data including account balances and nonce values, contract code and storage values, should be evenly distributed across the nodes. keywords: access; evm; network; state; tool cache: ethresear-12355.html plain text: ethresear-12355.txt item: #987 of 3327 id: ethresear-12395 author: ethresear title: ethresear-12395 date: None words: 3096 flesch: 65 summary: If an account has code, its code-forwarding field should be ignored so user accounts (currently EOAs) can change implementations, but contracts can’t. AUTHUSURP achieves a similar goal, allowing the user to set the first implementation, but I think it has a couple of drawbacks compared to assuming default contract: We never fully get rid of EOAs. keywords: account; code; contract; default cache: ethresear-12395.html plain text: ethresear-12395.txt item: #988 of 3327 id: ethresear-12415 author: ethresear title: ethresear-12415 date: None words: 416 flesch: 60 summary: These facts coupled with the fact that there is a new economy being formed around stETH that other validator pools will not be able to engage in leaves me feeling there to be no real realistic path for other staking pools on ETH to form. I advocate for removing staking derivatives - particularly stETH from LIDO to inhibit this lockout of other validator pools. keywords: staking cache: ethresear-12415.html plain text: ethresear-12415.txt item: #989 of 3327 id: ethresear-12426 author: ethresear title: ethresear-12426 date: None words: 1491 flesch: 75 summary: Previous work A previous attempt to implement private trades used an MPC (multi-party computation) to try and find someone who wanted to trade with us. For example, it is impossible to have an If Else clause around revealed trades. keywords: match; trade cache: ethresear-12426.html plain text: ethresear-12426.txt item: #990 of 3327 id: ethresear-12476 author: ethresear title: ethresear-12476 date: None words: 2035 flesch: 69 summary: The database system is composed of a master node and a cluster of tablet nodes (a simplification of BigTable’s architecture). This includes the master node, which distributes work to the tablet nodes, and tablet nodes, which actually store a shard of the database state, process queries/insertions, build the index, etc. keywords: database; master; node; tablet cache: ethresear-12476.html plain text: ethresear-12476.txt item: #991 of 3327 id: ethresear-12494 author: ethresear title: ethresear-12494 date: None words: 1368 flesch: 58 summary: A voting block is a collection of vote messages and invalidations batched together into a Merkle tree with a unique Merkle root hash called the voting_block_root. On-chain vote messages get put into another Merkel tree calculated on-chain, called the on_chain_voting_block_root At the end, the official voting result will be calculated by the following algorithm: All votes from all members are ordered sequentially by the voting blocks and the leaf position of the vote in the block. keywords: operator; vote; voting cache: ethresear-12494.html plain text: ethresear-12494.txt item: #992 of 3327 id: ethresear-12530 author: ethresear title: ethresear-12530 date: None words: 1840 flesch: 69 summary: The argument that L2 bridges are fundamentally more secure at size than cross-chain L1 bridges adds significant drag to alt-L1 competition. Behind the scenes L2’s are improving reliability, decreasing fees, and increasing accessibility. keywords: alt; ethereum cache: ethresear-12530.html plain text: ethresear-12530.txt item: #993 of 3327 id: ethresear-12641 author: ethresear title: ethresear-12641 date: None words: 876 flesch: 55 summary: 2714×1496 355 KB Identifying the “sleepminting attack” problem The outcome of a blog post I then wrote to identify the attack’s vector was that any platform displaying NFTs shouldn’t trust a contract implementation’s “honest” usage of event Transfer. Namely, despite the possibility of every human being theoretically capable of inspecting an EIP-721-compliant contract’s use of event Transfer, that assumption not being deliberately socially scalable. keywords: event; research; transfer cache: ethresear-12641.html plain text: ethresear-12641.txt item: #994 of 3327 id: ethresear-12658 author: ethresear title: ethresear-12658 date: None words: 214 flesch: 65 summary: An other attempt at simplifying finality in Gasper - Consensus - Ethereum Research Ethereum Research An other attempt at simplifying finality in Gasper Consensus ulrych8 May 18, 2022, 2:20pm 1 I’ve seen the previous attempts of @jacob-eliosoff here and here suggesting to remove the source of the FFG vote in Gasper. I think that in his quest to simplify Gasper, Jacob tried the wrong way. keywords: vote cache: ethresear-12658.html plain text: ethresear-12658.txt item: #995 of 3327 id: ethresear-12670 author: ethresear title: ethresear-12670 date: None words: 1471 flesch: 70 summary: Imo anyone holding a larger amount of testnet eth should send some to faucets regardless… It’s just 2 clicks, get your shit together testnet whales lol 2 Likes kkonrad September 7, 2022, 9:04am 17 Being in the top 1000 qualifies you. Likes An analysis of testnet faucet donors desy August 10, 2022, 4:01pm 16 @pk910 updated @kkonrad cool! keywords: faucet; goerli; sepolia cache: ethresear-12670.html plain text: ethresear-12670.txt item: #996 of 3327 id: ethresear-12670?page=2 author: ethresear title: ethresear-12670?page=2 date: None words: 2070 flesch: 72 summary: Goerli faucet: 0.2 gETH daily goerlifaucet.org GoerliFaucet.org - FREE Goerli ETH faucet. Goerli faucet: 0.1 gETH daily goerli-faucet.com goerli-faucet.com - FREE Goerli Faucet. keywords: faucet; funds; goerli; testnet cache: ethresear-12670?page=2.html plain text: ethresear-12670?page=2.txt item: #997 of 3327 id: ethresear-12698 author: ethresear title: ethresear-12698 date: None words: 1783 flesch: 55 summary: Ethereum consensus layer validator anonymity using Dandelion++ and RLN conclusion - Privacy - Ethereum Research Ethereum Research Ethereum consensus layer validator anonymity using Dandelion++ and RLN conclusion Privacy blagoj May 22, 2022, 9:47pm 1 Link to the analysis At PSE team we’ve (me, @AtHeartEngineer and @barryWhiteHat ) researched the problem of Ethereum consensus layer validator anonymity in detail as an important problem in general but also as an application for RLN. Also, applications outside of validator anonymity could skip this delay. keywords: anonymity; consensus; layer; network cache: ethresear-12698.html plain text: ethresear-12698.txt item: #998 of 3327 id: ethresear-12700 author: ethresear title: ethresear-12700 date: None words: 667 flesch: 72 summary: For malicious fraction of \frac{1}{2} of shufflers&commitments with N=2^{14}: \frac{1}{2} of swaps are instantly killed \frac{1}{2} of honest commitments undergoing a tree are not secretly swapped. Each shuffler makes his own stir of K=128 commitments 1795×838 56.6 KB and provides a zero-knowledge proof of correctness. keywords: commitments; swap cache: ethresear-12700.html plain text: ethresear-12700.txt item: #999 of 3327 id: ethresear-12709 author: ethresear title: ethresear-12709 date: None words: 2172 flesch: 68 summary: If crypto flourishes with the majority of the users using custodial wallets, the only thing we accomplished is changing the name of “JPMorgan Chase” to “Binance”. That is why winning the fight of non-custodial wallets is (in my opinion) one of the most important challenges there is. keywords: guardians; recovery; wallet cache: ethresear-12709.html plain text: ethresear-12709.txt item: #1000 of 3327 id: ethresear-12742 author: ethresear title: ethresear-12742 date: None words: 1103 flesch: 58 summary: On mainnet, data prediction gets much easier with more linear data. Linear regression By collecting TTD data from the network, we can visualize it and play with more advanced predictions. keywords: data; prediction; ttd cache: ethresear-12742.html plain text: ethresear-12742.txt item: #1001 of 3327 id: ethresear-12778 author: ethresear title: ethresear-12778 date: None words: 3081 flesch: 63 summary: Median price oracle is only more resistant to single block manipulation, but in the case of multi block manipulation the cost is 50% cheaper compared than the arithmetic mean and is EASIER to manipulate. Also, unlike TWAP/TWMP it does still incorporate prices that could be achieved with flash loans, which I kind of prefer to disregard as “fake news” prices. keywords: block; mean; median; price; twap; window cache: ethresear-12778.html plain text: ethresear-12778.txt item: #1002 of 3327 id: ethresear-1279 author: ethresear title: ethresear-1279 date: None words: 145 flesch: 57 summary: Use the following paragraphs for a longer description, or to establish category guidelines or rules: Why should people use this category? About the Decentralized exchanges category - Decentralized exchanges - Ethereum Research Ethereum Research About the Decentralized exchanges category Decentralized exchanges vbuterin March 2, 2018, 6:05am 1 (Replace this first paragraph with a brief description of your new category. keywords: category cache: ethresear-1279.html plain text: ethresear-1279.txt item: #1003 of 3327 id: ethresear-12808 author: ethresear title: ethresear-12808 date: None words: 2122 flesch: 71 summary: So by your logic we expect pasta curves to be more secure than BLS curves. So by your logic we expect pasta curves to be more secure than BLS curves. OK )) keywords: bls; curves; pairing; pasta cache: ethresear-12808.html plain text: ethresear-12808.txt item: #1004 of 3327 id: ethresear-1281 author: ethresear title: ethresear-1281 date: None words: 2512 flesch: 64 summary: This would make griefing even less effective, and may also resolve the issue that makes this kind of market maker fare poorly in handling purchases that are large relative to its liquidity pool. Improving front running resistance of x*y=k market makers - Decentralized exchanges - Ethereum Research Ethereum Research Improving front running resistance of x*y=k market makers Decentralized exchanges vbuterin March 2, 2018, 9:24am 1 Two years ago I made a post where I suggested that we could run on-chain decentralized exchanges in a similar way to what Augur and Gnosis were proposing for on-chain market makers (eg. LMSR), and Martin Köppelmann from Gnosis suggested a simple approach for doing so, that I call the “x*y=k market maker”. keywords: exchange; likes; maker; market cache: ethresear-1281.html plain text: ethresear-1281.txt item: #1005 of 3327 id: ethresear-1283 author: ethresear title: ethresear-1283 date: None words: 189 flesch: 43 summary: I think if EVM wants to keep its lead (currently it does have lots of market momentum) there has to be a process to define different EVM editions depending on the capabilities of the ledger, taking into account that many EVM implementations will not run on Ethereum blockchain. For example EVM that runs on Ethereum does not include floating point numbers, but if other EVM implementations may want them, then there should be a profile supporting floating point numbers. keywords: evm cache: ethresear-1283.html plain text: ethresear-1283.txt item: #1006 of 3327 id: ethresear-12839 author: ethresear title: ethresear-12839 date: None words: 915 flesch: 53 summary: In this paper, we propose a dynamic data sharding to achieve data availability with applications for a large decentralized key-value (KV) store on top of an EVM-compatible blockchain. The key to achieving data availability is to build an on-chain oracle of the estimate of the replication factors of each shard and then to reward those nodes that prove the replications of the shard over time. keywords: data cache: ethresear-12839.html plain text: ethresear-12839.txt item: #1007 of 3327 id: ethresear-12851 author: ethresear title: ethresear-12851 date: None words: 2054 flesch: 61 summary: Malicious parties will be able to pull this attack in any group where they hold a majority, i.e. t+1. The higher t we set, the lesser chance for colluding parties to forge a malicious signature, but this also leaves less room for unforeseen failures (peer goes offline) and hurts performance (see performance analysis). keywords: account; chain; mix; parties cache: ethresear-12851.html plain text: ethresear-12851.txt item: #1008 of 3327 id: ethresear-12930 author: ethresear title: ethresear-12930 date: None words: 514 flesch: 61 summary: How This post is intended to get initial feedback but a simple sketch of a protocol like this would look something like snapshot + CoW protocol: Users can submit bids which are signed messages to a highly available data layer At auction end time, bonded auction solvers could compute final results Create merkleroot of results and submit to contract on L1 There are a lot of implementation details such as how to avoid spam on the data layer but because bidding is free, this could open up many fun aspects and avenues for bidding while also avoiding failed gas fees + extremely large miner/validator tips. These points led me to a few questions: In the medium term, is it futile to think high demand auctions will be able to cleanly fit into the ethereum tx fee market? keywords: auction; nft cache: ethresear-12930.html plain text: ethresear-12930.txt item: #1009 of 3327 id: ethresear-12939 author: ethresear title: ethresear-12939 date: None words: 1540 flesch: 64 summary: Secondly, the bribe payout can be improved to prevent negative karma for bribed voters: By using technology – similar to tornado cash -, bribes can be paid to the participants in a non-trackable way by giving each public voter key the ability to claim their bribes into a new address in a non-trackable manner. The total cost for the briber would be: n*(b_i/n) \simeq b_i , assuming v_i proofWait[msg.sender], Too early); require(commitments[msg.sender] == keccak256(abi.encodePacked(msg.sender, _proof, _randomSalt)), Mismatch); require(!proofSubmitted[_proof], Proof already submitted); require(_proof % 13 ! keywords: proof cache: ethresear-13594.html plain text: ethresear-13594.txt item: #1038 of 3327 id: ethresear-13634 author: ethresear title: ethresear-13634 date: None words: 2680 flesch: 64 summary: However, this means more proofs will be required for the same batch size (or per light client header), which will increase the gas cost of verifying that batch. Hence the cost of this infra = $1.536*69 = $106 per hr Machine Cost per light client header = 106/3600/7 = keywords: chain; cost; ethereum; ibc; proof; signatures cache: ethresear-13634.html plain text: ethresear-13634.txt item: #1039 of 3327 id: ethresear-13642 author: ethresear title: ethresear-13642 date: None words: 176 flesch: 60 summary: adompeldorius September 12, 2022, 7:15pm 2 Could it be this? fradamt September 19, 2022, 2:26pm 3 Other than that, there’s this: Change fork choice rule to mitigate balancing and reorging attacks More to come soon anand November 3, 2022, 3:25pm 4 Thanks, that mentions it. View-merge algorithm - Consensus - Ethereum Research Ethereum Research View-merge algorithm Consensus anand September 12, 2022, 5:09pm 1 In Vitalik’s recent talk at the Stanford Blockchain Conference (51% attack recovery), he mentions the view-merge algorithm (47:08), by which online nodes can tell which other nodes are online. keywords: view cache: ethresear-13642.html plain text: ethresear-13642.txt item: #1040 of 3327 id: ethresear-1366 author: ethresear title: ethresear-1366 date: None words: 1742 flesch: 57 summary: The bidding mechanism allows a briber to pay rational validators to build on the fork of the briber’s choosing. These two considerations are probably why bribing attacks have stayed in the realm of academia and were never attempted in practice. keywords: attacker; bribing; chain; shard cache: ethresear-1366.html plain text: ethresear-1366.txt item: #1041 of 3327 id: ethresear-13680 author: ethresear title: ethresear-13680 date: None words: 1239 flesch: 56 summary: trig(x,y,z,t) → governs where data space is The internal frequency t_range = (t_start, t_end) as a subset of the full envelope t_env_range. matrix bitfield row = max length of envelope diameter = d or M num of envelopes in data block = number of rows = L or N total data size = matrix[M][N] If the envelope is always constant over an interval period, eg 12s. keywords: data; envelope; matrix; phase cache: ethresear-13680.html plain text: ethresear-13680.txt item: #1042 of 3327 id: ethresear-13739 author: ethresear title: ethresear-13739 date: None words: 6356 flesch: 45 summary: Let’s now visualize the slot structure and the two possible cases of maliciously timed attestations, which attempt to split validator views, to convince ourselves that the assumption on the network delay is sufficient to conclude that views are synchronized. In the balancing case, the desired outcome is that a 50/50 split of honest views is resolved for whatever the proposer sees as leading. keywords: aggregates; attestations; choice; fork; merge; proposer; slot; view cache: ethresear-13739.html plain text: ethresear-13739.txt item: #1043 of 3327 id: ethresear-13742 author: ethresear title: ethresear-13742 date: None words: 1240 flesch: 65 summary: The way that you can verify a TEE is valid (at least for Intel SGX) is through Attestations, where the enclave has access to a private key signed by the manufacturer (which is trusted not to go and sign keys for a malicious party) and uses it to attest to a remote user that the Enclave sees that it is running that software as claimed. That means, no one has access to this server’s code except code. keywords: code; october; server cache: ethresear-13742.html plain text: ethresear-13742.txt item: #1044 of 3327 id: ethresear-13775 author: ethresear title: ethresear-13775 date: None words: 2691 flesch: 68 summary: I conjecture that direct elicitation of final in block prices and their use as starting prices, with a deposit that collateralizes the max net exposure the AMM is taking at any point on that block, is optimal for passive liquidity providers. nikete October 2, 2022, 6:28pm 12 One thing that came up on a side conversation with @josojo is that for the liquidity provisioning between blocks, ideas related to [1112.0076] Bandit Market Makers might make sense eljhfx October 12, 2022, 7:51am 13 If this is just shifting the costs of LVR onto block builders (away from LPs), it seems like you’d still need some highly efficient (probably off-chain) auction or exclusive order-flow sale in order for this to be effective - since builders won’t want to take on the risk unless they were being amply compensated by searchers/institutions. keywords: amm; block; builder; price cache: ethresear-13775.html plain text: ethresear-13775.txt item: #1045 of 3327 id: ethresear-13803 author: ethresear title: ethresear-13803 date: None words: 3588 flesch: 59 summary: Here is also an alternative (perhaps more intuitive) argument, though of course ultimately relying on the same violations of voting rules: We show that, unless the 1/3 is already slashable, a finalized block is always canonical in the views of those who voted to finalize it (i.e. which voted for the notarization of its child), according to the fork-choice which is implicitly specified by the voting rules, i.e. longest notarized chain with ties broken by latest notarization epoch. We modify it to: Vote for a block if it extends the longest notarized chain, with ties broken by latest notarization epoch of the tip. keywords: block; chain; epoch cache: ethresear-13803.html plain text: ethresear-13803.txt item: #1046 of 3327 id: ethresear-13843 author: ethresear title: ethresear-13843 date: None words: 1045 flesch: 75 summary: What sort of contract code is guaranteed to work in the future and what sort of contract code is not? I’m not the only one to store raw data in contract bytecodes, like in this article published in 2019 On Efficient Ethereum Storage. keywords: contract; ethereum cache: ethresear-13843.html plain text: ethresear-13843.txt item: #1047 of 3327 id: ethresear-13863 author: ethresear title: ethresear-13863 date: None words: 4244 flesch: 58 summary: T_{2n}(y_i)\} where T_i is the data committed to by S_i Provide an evaluation proof of D_y(x) and D_x(y), verify that they are identical Also provide evaluation proofs of all D_y(x_i) and D_x(y_i), and verify that they are on polynomials of the appropriate degree The main weakness of this approach is that it makes it much harder to implement a distributed builder: it would not require a fairly involved multi-step protocol. Note that this is challenging: we want to be able to reconstruct proofs from other proofs, without seeing the rest of the data in the rows that the new proofs are corresponding to. keywords: danksharding; data; evaluation; kzg; point; proof; proto; root cache: ethresear-13863.html plain text: ethresear-13863.txt item: #1048 of 3327 id: ethresear-13879 author: ethresear title: ethresear-13879 date: None words: 9132 flesch: 57 summary: Recognise that as the protocol ossifies, and given the huge complexity of figuring out each market structure independently (if it is at all possible to figure them out in a timeless manner, markets do change after all!), it may be better to provide a trustless infrastructure for proposers to enter into commitments with third-parties, even though there is no “near-optimal” default strategy encoded via the protocol and markets are structured via proposer commitments instead. While this encourages parcimony regarding proposer commitments, it is possible for trusted proposer-builder coalitions to coordinate out-of-band such that the proposer does not expend the gas to make their commitment but the builder still provides them with a block, putting untrusted proposers at a financial disadvantage. keywords: attesters; block; bob; builder; commitment; eigenlayer; party; pbs; proposer; protocol; validity cache: ethresear-13879.html plain text: ethresear-13879.txt item: #1049 of 3327 id: ethresear-13903 author: ethresear title: ethresear-13903 date: None words: 654 flesch: 48 summary: This is a type 2 ZK-EVM in Vitalik’s categorization: it natively supports EVM bytecode, keeping opcodes, including those handling smart contract calls, error management and gas management, as is, but the internal state is represented differently. We split the tests in 3 parts: : traces are generated and constraints are satisfied; : tests that do not pass (i.e. the implementation or the specification has a bug); not implemented: tests that rely on one or more opcode not yet implemented (e.g. precompiles). keywords: evm cache: ethresear-13903.html plain text: ethresear-13903.txt item: #1050 of 3327 id: ethresear-13904 author: ethresear title: ethresear-13904 date: None words: 4073 flesch: 64 summary: ・rightness of transition to newAssetState from oldAssetState Purge: ・rightness of transition to newAssetState from oldAssetState with purged state-diff ~Aggregator Side~ For each transaction ・Inclusion proof’s target in the merge part exists in the AllBlockHashRoot [12] (AllBlockHashRoot is the root of the tree consisting of all block headers before) ・Corresponding oldAssetState to the current value for the key=sender’s address in Asset Root Tree ・Recursive proving to verify the rightness of zkp proof of purge/merge sent by the sender. I think there is a way to get constant user state while retaining privacy, by encrypting the user state-diffs with the recipient’s public key, and including it in the block. keywords: block; proof; root; state; tree; zkp cache: ethresear-13904.html plain text: ethresear-13904.txt item: #1051 of 3327 id: ethresear-13926 author: ethresear title: ethresear-13926 date: None words: 580 flesch: 59 summary: Anyway I am surprised that Ethereum foundation did nothing about the optimization of MPT access so far – Geth seems to use the serial version of MPT - https://github.com/agiletechvn/go-ethereum-code-analysis/blob/62e359d65ef1fc5f1fe6b0672a5fb9397db503c4/trie-analysis.md. Anyway, I was thinking why not to replace a single exclusive MPT by a number of independent MPTs that would enable parallel processing of txs, while all these small MPTs could be aggregated by a standard binary Merkle tree after all txs of a block have been processed in EVM already - root hash would be stored in a header instead of MPT root, so light clients would not lose any integrity information. keywords: merkle; mpt cache: ethresear-13926.html plain text: ethresear-13926.txt item: #1052 of 3327 id: ethresear-13961 author: ethresear title: ethresear-13961 date: None words: 579 flesch: 70 summary: 1 Like Trusted setup with Intel SGX? MicahZoltu October 19, 2022, 10:03am 2 IIUC what you are getting at, I think the usual solution solving the same problems that SGX solves is via widely distributed MPCs. He connects the right version of enclave (with right measurement which is linked to a known version of source code), b) that nobody knows the secret. keywords: enclave cache: ethresear-13961.html plain text: ethresear-13961.txt item: #1053 of 3327 id: ethresear-13974 author: ethresear title: ethresear-13974 date: None words: 872 flesch: 62 summary: uint256 t1; uint256 t2; uint256 t3; // solium-disable-next-line security/no-inline-assembly assembly { t0 := mload(add(point, 0)) t1 := mload(add(point, 32)) // y0, y1 t2 := mload(add(point, 64)) t3 := mload(add(point, 96)) } uint256 xx; uint256 xy; uint256 yx; uint256 yy; //s*P (xx,xy,yx,yy) So the cost of the naive subgroup check is dominated by the scalar multiplication: function isOnSubgroupG2Naive(uint256[4] memory point) internal view returns (bool) { uint256 t0; uint256 t1; uint256 t2; uint256 t3; // solium-disable-next-line security/no-inline-assembly assembly { t0 := mload(add(point, 0)) t1 := mload(add(point, 32)) // y0, y1 t2 := mload(add(point, 64)) t3 := mload(add(point, 96)) } uint256 xx; uint256 xy; uint256 yx; uint256 yy; (xx,xy,yx,yy) keywords: uint256 cache: ethresear-13974.html plain text: ethresear-13974.txt item: #1054 of 3327 id: ethresear-13980 author: ethresear title: ethresear-13980 date: None words: 2252 flesch: 68 summary: Blocks in blue have direct weight = 1 while other blocks have direct weight = 0. If B_i is included in the canonical chain, proposer P_i receives \gamma per fresh and correct vote v included in \mathcal{V}_i A vote v included in block B_i is fresh if it was published by an attester from \mathcal{A}_{i-1} A vote v included in block B_i is correct if \text{parent}(B_i) keywords: block; players; proposer; round; time cache: ethresear-13980.html plain text: ethresear-13980.txt item: #1055 of 3327 id: ethresear-14010 author: ethresear title: ethresear-14010 date: None words: 1433 flesch: 66 summary: Gas costs (as opposed to gas limits), for the purposes of this discussion, are the hardcoded burning of ether by using opcodes and the hardcoded priority fee of EIP-1559. Spore-Druid-Bray October 25, 2022, 1:41am 2 Interesting post: it’s a small point, but I’m not sure if gas costs and gas limits are both fundamental: metering to prevent DoS is certainly fundamental to how we experience blockchains today, though even within this there are subtleties over different forms of DoS. For an intriguing article on Bitcoin without a blocksize limit, see: A Transaction Fee Market Exists Without a Block Size Limit As far as I know nobody has extended this model or considered it with GHOST or fixed blocktimes (via PoS). keywords: costs; ethereum; gas cache: ethresear-14010.html plain text: ethresear-14010.txt item: #1056 of 3327 id: ethresear-14012 author: ethresear title: ethresear-14012 date: None words: 742 flesch: 60 summary: Poseidon VM aims to solve two problems in the Ethereum ecosystem: ZKP based applications has a high barrier to entry for builders ZKP based applications has a high verifier cost (gas) as well as prover cost (while many existing L2s like OP/Arbitrum/Scoll/zkSync can scale normal Ethereum transaction, they cannot scale zk transactions very well, for example, zkopru has about 100 TPS, which is not bad at all but still limited) Introducing Poseidon VM: A zkApp-friendly blockchain virtual machine with EVM Compatibility - EVM - Ethereum Research Ethereum Research Introducing Poseidon VM: A zkApp-friendly blockchain virtual machine with EVM Compatibility EVM zkop-rollup, layer-2 xerophyte October 24, 2022, 6:07am 1 We (https://www.p0xeidon.xyz/) would love to introduce Poseidon VM to the Ethereum community. keywords: evm; poseidon; zkapp cache: ethresear-14012.html plain text: ethresear-14012.txt item: #1057 of 3327 id: ethresear-14029 author: ethresear title: ethresear-14029 date: None words: 6478 flesch: 55 summary: Burning MEV through block proposer auctions - Economics - Ethereum Research Ethereum Research Burning MEV through block proposer auctions Economics proposer-builder-separation, mev domothy October 26, 2022, 5:37pm 1 Special thanks to @JustinDrake and @pseudotheos for all the discussion and theory-crafting surrounding this topic. Any higher bid will make nodes reject their block at the time of reveal Any lower bid hurts their chances of winning the auction, given that other eligible proposers may be seeing the same block with the same builder_fee. keywords: bid; block; builder; eth; mev; proposal; proposer; slot; time cache: ethresear-14029.html plain text: ethresear-14029.txt item: #1058 of 3327 id: ethresear-14106 author: ethresear title: ethresear-14106 date: None words: 282 flesch: 70 summary: EIP-5875 Opcode for TXNUM - EVM - Ethereum Research Ethereum Research EIP-5875 Opcode for TXNUM EVM xinbenlv November 4, 2022, 5:56pm 1 Hi, all I am proposing EIP-5875 to add opcode to retrieve TXNUM A TX is an atomic point of time for world state. Please share your feedback in the main discussion thread Fellowship of Ethereum Magicians – 4 Nov 22 EIP-5875: Opcode for TX number in a block The TX is an atomic point of time for world state. keywords: txnum cache: ethresear-14106.html plain text: ethresear-14106.txt item: #1059 of 3327 id: ethresear-14134 author: ethresear title: ethresear-14134 date: None words: 3673 flesch: 58 summary: Experimental evaluation of the impact of Tor latency on web browsing can be used as a reference. According to Tor performance metrics, Tor latency should not be a problem. keywords: dandelion; latency; messages; network; tor; validator cache: ethresear-14134.html plain text: ethresear-14134.txt item: #1060 of 3327 id: ethresear-14141 author: ethresear title: ethresear-14141 date: None words: 2068 flesch: 65 summary: But because it is built on top of the protocol and not as a part of it, it gains two very important properties: Anyone can experiment with different DA layer designs and parameters. In other words, it allows Ethereum validators to voluntarily submit themselves to extra slashing risks in order to provide services. keywords: data; eigenlayer; ethereum cache: ethresear-14141.html plain text: ethresear-14141.txt item: #1061 of 3327 id: ethresear-14150 author: ethresear title: ethresear-14150 date: None words: 2672 flesch: 59 summary: In this case, L3 official Ethereum rollups may be useless. If the L1 chain is divided into different shards working in parallel, security breaches may occur, with risks of double spending attempts, looping problems, contradictory instructions … an interesting post about sharding and parallelization comes to the same conclusion : “Rollups + data-availability sharding are substantially less complicated than most sharding proposals.” as the post explains, a major argument in favor of rollups is that “a single honest party” is required, enabling to push “heavy-duty execution” on rollups the proposed model of L2 and L3 official Ethereum rollups could come along with buffers to increase data availability, and a sharding of data, preferably a temporal sharding. keywords: data; ethereum; rollups cache: ethresear-14150.html plain text: ethresear-14150.txt item: #1062 of 3327 id: ethresear-14164 author: ethresear title: ethresear-14164 date: None words: 1455 flesch: 50 summary: Reorg resilience argument Goldfish case study The way Goldfish achieves reorg resilience even while allowing subsampling and fully variable participation is through the use of ephemeral votes, i.e. by only using votes from slot t to run the fork-choice at slot t+1, combined with view-merge, which allows proposers to synchronize honest views and always get honest attestations. We’ll refer to this assumption simply as honest majority, essentially considering offline validators to be faulty. keywords: ghost; slot cache: ethresear-14164.html plain text: ethresear-14164.txt item: #1063 of 3327 id: ethresear-14206 author: ethresear title: ethresear-14206 date: None words: 566 flesch: 49 summary: These architectures rely on a rollup-based layer 2 for security: rollups can inherit the full security of layer 1. Rollups store their compressed data and verify their state transitions on layer 1. keywords: layer cache: ethresear-14206.html plain text: ethresear-14206.txt item: #1064 of 3327 id: ethresear-14212 author: ethresear title: ethresear-14212 date: None words: 1503 flesch: 46 summary: OlaVM is the first ZKVM that introduces parallel VM execution, it integrates the technical features of the two schemes to obtain faster execution speed and faster proof speed, thus bringing the highest TPS of the system. Increasing the speed of proof generation is the single most important aspect to increasing the overall throughput of the system, and there are two means to accelerate proof generation, keeping your circuit scale to a minimum and using the most efficient ZK algorithm. keywords: design; execution; research cache: ethresear-14212.html plain text: ethresear-14212.txt item: #1065 of 3327 id: ethresear-14219 author: ethresear title: ethresear-14219 date: None words: 3527 flesch: 55 summary: 2132×1312 139 KB Communication costs on the global topic Blockchains use signature aggregation to amortize signature verification time and bandwidth: The block proposer needs to include votes into the block. This post focuses on signature aggregation. keywords: aggregate; aggregation; horn; size; time; topic cache: ethresear-14219.html plain text: ethresear-14219.txt item: #1066 of 3327 id: ethresear-14349 author: ethresear title: ethresear-14349 date: None words: 705 flesch: 63 summary: A third transaction type (transaction type 3) is added: Transactions with type 3 take a transaction hash (tx), a block hash (block), a positive number of blocks less than or equal to 1 (perhaps this could be increased) (numblocks), and an amount of wei to burn (amount). Block validity is changed: Type 3 transactions must be followed with either another type 3 transaction with an identical tx and lower amount (in the case of a tie, the transaction with the lower transaction hash is included first) or a transaction with transaction hash equal to tx. keywords: transaction; type cache: ethresear-14349.html plain text: ethresear-14349.txt item: #1067 of 3327 id: ethresear-14350 author: ethresear title: ethresear-14350 date: None words: 188 flesch: 58 summary: Recently, we demonstrated using functional magnetic resonance imaging (fMRI) that the outcome of free decisions can be decoded from brain activity several seconds before reaching conscious awareness. PubMed Tracking the unconscious generation of free decisions using ultra-high field... keywords: brain cache: ethresear-14350.html plain text: ethresear-14350.txt item: #1068 of 3327 id: ethresear-14373 author: ethresear title: ethresear-14373 date: None words: 573 flesch: 60 summary: A good solution for this would be to have trustless light clients that can sync to the latest header of the beacon chain and verify using Merkle Inclusion proofs to the latest block header. Also the ethereum ecosystem would be able to benefit on light clients not just verifying the transactions only for themeselves but maybe able to pass on those log messages to other users and contribute to a more decentralized system. keywords: layer; light cache: ethresear-14373.html plain text: ethresear-14373.txt item: #1069 of 3327 id: ethresear-14427 author: ethresear title: ethresear-14427 date: None words: 967 flesch: 58 summary: They are somewhat arithmetic-friendly: all that is required to verify SIS hashes in a SNARK are range-checks and linear combinations with constants. In the meantime, we provide an updated table, where q denotes the modulus of the underlying field, \beta the maximal preimage value (i.e., the SIS solution should have entries no larger than [0:\beta) and n denotes the number of field elements in the hash output. keywords: evm; proof cache: ethresear-14427.html plain text: ethresear-14427.txt item: #1070 of 3327 id: ethresear-14444 author: ethresear title: ethresear-14444 date: None words: 550 flesch: 69 summary: Besides, I also found the paper Vulnerability of a non-membership proof scheme which seems to propose 4 attacks targeting RSA accumulator. I just want to know is it still safe to use RSA accumulator? keywords: accumulator cache: ethresear-14444.html plain text: ethresear-14444.txt item: #1071 of 3327 id: ethresear-14462 author: ethresear title: ethresear-14462 date: None words: 2662 flesch: 60 summary: The Puffer team is working on a Solidity verifier for SGX remote attestations, supported by an Ethereum Foundation grant. false sense of security: Easily-broken SGX 2FA (e.g. if the privkey is easily extractable) may provide a false sense of security. novelty: No Ethereum application that verifies SGX remote attestations on-chain could be found. keywords: 2fa; attestation; remote; rollup; sgx cache: ethresear-14462.html plain text: ethresear-14462.txt item: #1072 of 3327 id: ethresear-14494 author: ethresear title: ethresear-14494 date: None words: 626 flesch: 50 summary: Group Execution Module Multiple non-conflicting groups of transactions are input to multiple groups of peer nodes, with each group having one sequencer for execution and multiple peer nodes for voting. DAG Graph Get all possibilities of parallel transactions through DAG. keywords: sv(txn; transactions cache: ethresear-14494.html plain text: ethresear-14494.txt item: #1073 of 3327 id: ethresear-1450 author: ethresear title: ethresear-1450 date: None words: 1248 flesch: 58 summary: Note that there is a nice parallel between cross-shard messages and yanking, and existing CALLs and CREATEs: CALL = synchronous intra-shard message passing, CREATE = synchronous intra-shard contract creation, CROSS_SHARD_CALL Cross-shard contract yanking - Sharding - Ethereum Research Ethereum Research Cross-shard contract yanking Sharding cross-shard vbuterin March 21, 2018, 5:59am 1 Special thanks to Piper Merriam for helping to come up with this idea This is a generalization of cross-shard locking schemes and similar techniques to enabling cross-shard activity to solve train-and-hotel problems. keywords: contract; cross; shard cache: ethresear-1450.html plain text: ethresear-1450.txt item: #1074 of 3327 id: ethresear-14520 author: ethresear title: ethresear-14520 date: None words: 1570 flesch: 52 summary: There are many other types of MEV attacks, and the specific type of attack that is used will depend on the specific vulnerabilities of the blockchain network and the goals of the attacker. MEV attacks can lead to increased centralization of the blockchain network, as miners with more resources or technical expertise may be more able to exploit MEV vulnerabilities. keywords: attacks; mev cache: ethresear-14520.html plain text: ethresear-14520.txt item: #1075 of 3327 id: ethresear-14553 author: ethresear title: ethresear-14553 date: None words: 137 flesch: 37 summary: ICS-15: Ethereum beacon chain light client specification for IBC - Applications - Ethereum Research Ethereum Research ICS-15: Ethereum beacon chain light client specification for IBC Applications seunlanlege January 5, 2023, 3:49pm 1 In this research article, I define the neccessary data types & algorithms needed to run the ethereum beacon chain light client as an 02-client IBC module. This will allow IBC enabled chains to communicate trustlessly with the ethereum beacon chain. research.polytope.technology ICS-15 ethereum beacon chain light client specification for IBC This technical specification assumes that you’re already aware of the sync committee protocol introduced in the altair, the first hard fork of the ethereum beacon chain. keywords: ethereum cache: ethresear-14553.html plain text: ethresear-14553.txt item: #1076 of 3327 id: ethresear-14565 author: ethresear title: ethresear-14565 date: None words: 1008 flesch: 55 summary: The simplest form of CoinSwap transaction would cost double what a regular transfer does (2 ∗ 21000 = 42000 gas). Finally, I want to emphasize that S𝛑PETs privacy still depends heavily on the overall anonymity set size, so the more Ethereum users leverage it, the better privacy every one of us gets. keywords: privacy; time; transactions cache: ethresear-14565.html plain text: ethresear-14565.txt item: #1077 of 3327 id: ethresear-14586 author: ethresear title: ethresear-14586 date: None words: 209 flesch: 60 summary: According to my research, most of the zkRollup implementations out there are using a giant Sparse-Merkle-Tree for storing accounts, in which each account contains another Sparse-Merkle-Tree storing the assets of that user. I have gotten these numbers in some of the rollup projects. zkSync → Account capacity: 2^24, Token-capacity: 2^8 (Based on their protocol documentation) zkBNB → Account capacity: 2^32, Token-capacity: 2^16 Now imagine (E.g In case of zkSync), I create 2^8 transactions, sending tokens to all empty slots of the victim account. keywords: account cache: ethresear-14586.html plain text: ethresear-14586.txt item: #1078 of 3327 id: ethresear-14607 author: ethresear title: ethresear-14607 date: None words: 99 flesch: 32 summary: research.polytope.technology Merkle multi proofs Merkle multi proofs enable more efficient merkle proofs by re-using the intermediate nodes shared by the proof leaves during the recalculation of the root hash of the tree. Merkle multi proofs for computationally constrained environments - Data Structure - Ethereum Research Ethereum Research Merkle multi proofs for computationally constrained environments Data Structure seunlanlege January 12, 2023, 1:58pm 1 In this research article, I present a highly efficient algorithm for verifying merkle multi proofs in computationally constrained environments. keywords: merkle cache: ethresear-14607.html plain text: ethresear-14607.txt item: #1079 of 3327 id: ethresear-14623 author: ethresear title: ethresear-14623 date: None words: 677 flesch: 61 summary: so folks are running slashers in spite of this (*assuming slashers are needed to catch slashable offences, but I could be wrong here). That said, slashable offences have been caught (looks like about 224 so far - Validator Slashings - Open Source Ethereum Blockchain Explorer - beaconcha.in - 2023) - keywords: slasher cache: ethresear-14623.html plain text: ethresear-14623.txt item: #1080 of 3327 id: ethresear-14671 author: ethresear title: ethresear-14671 date: None words: 3039 flesch: 53 summary: Verifying zkPoS Attestation enables accessing and syncing valid block headers. BLS signature verification is an essential part of zkPoS Attestation, and pairing on BLS12–381 is the basis for BLS signature verification. keywords: attestation; block; bls; ethereum; pairing; proof; zkpos cache: ethresear-14671.html plain text: ethresear-14671.txt item: #1081 of 3327 id: ethresear-14689 author: ethresear title: ethresear-14689 date: None words: 693 flesch: 58 summary: Generalized Low Degree Check for Degree < 2^l with Application to FRI - Cryptography - Ethereum Research Ethereum Research Generalized Low Degree Check for Degree < 2^l with Application to FRI Cryptography qizhou January 25, 2023, 10:34pm 1 Problem Statement Consider a polynomial f(x) over a finite-field \mathbb{F}_q defined by its evaluations f_i = f(\omega^i), where \omega is the n-th root of unity of A(x) = q(x, x^m), where m is a power of 2 (commonly use m = 4) and q(x, y) is a 2D polynomial, whose degree in x is less than m, and degree in y is less than \frac{deg(f(x))}{m} . keywords: degree cache: ethresear-14689.html plain text: ethresear-14689.txt item: #1082 of 3327 id: ethresear-14694 author: ethresear title: ethresear-14694 date: None words: 1042 flesch: 73 summary: It does not satisfy the polynomial binding requirement of polynomial commitment schemes. This creates new polynomial Z over G_2. keywords: commitment cache: ethresear-14694.html plain text: ethresear-14694.txt item: #1083 of 3327 id: ethresear-147 author: ethresear title: ethresear-147 date: None words: 144 flesch: 61 summary: Use the following paragraphs for a longer description, or to establish category guidelines or rules: Why should people use this category? About the Economics category - Economics - Ethereum Research Ethereum Research About the Economics category Proof-of-Stake Economics virgil October 15, 2017, 6:36am 1 (Replace this first paragraph with a brief description of your new category. keywords: category cache: ethresear-147.html plain text: ethresear-147.txt item: #1084 of 3327 id: ethresear-14708 author: ethresear title: ethresear-14708 date: None words: 500 flesch: -5 summary: uint256 unlockTime = _getUnlockTime(lockDays); address etherAddress = address(0); Receipt memory receipt = Receipt( msg.sender, etherAddress, msg.value, unlockTime, true ); string memory receiptKey = _computeReceiptKey(receipt, counter); require(!hasReceipt[receiptKey], same receipt key collision); receiptRepo[receiptKey] = receipt; hasReceipt[receiptKey] = true; emit DepositEther( receiptKey, msg.sender, msg.value, lockDays, unlockTime ); } function depositErc20Token( address token, uint256 amount, uint256 lockDays ) public _isLegalErc20Token(token) _notContractAddress(msg.sender) { require(amount > 0, amount <= 0); require( !Address.isContract(msg.sender), not support contract address ); if ((lockDays <= 0) || computeReceiptKey(Receipt memory _receipt, uint256 _counter) private view returns (string memory) { return Strings.toString( uint256( keccak256( abi.encode( _receipt.customer, _counter + block.timestamp ) ) ) ); } modifier _isLegalErc20Token(address _token) { require(legalErc20Tokens[_token], not legal token); _; } modifier _notContractAddress(address _address) { require(!Address.isContract(_address), not support contract address); _; } function _getUnlockTime(uint256 _lockDays) private view returns (uint256) { return _lockDays * 86400 + block.timestamp; } function addToken(address _token) public { require(msg.sender == owner, only owner can add tokens); legalErc20Tokens[_token] = true; emit AddToken(_token); } function getReceipt(string memory _receiptKey) public { require(hasReceipt[_receiptKey], has not receipt or already draw); Receipt memory receipt = receiptRepo[_receiptKey]; emit Read( receipt.customer, receipt.token, receipt.amount, receipt.unlockTime ); } function depositEther(uint256 lockDays) public payable _notContractAddress(msg.sender) { require(msg.value > 0, amount <= 0); if ((lockDays <= 0) || keywords: uint256 cache: ethresear-14708.html plain text: ethresear-14708.txt item: #1085 of 3327 id: ethresear-14714 author: ethresear title: ethresear-14714 date: None words: 1267 flesch: 54 summary: Players in our system using SCWs maintain a mapping of secret commitments to tokens within their wallet. NIZKPoK(\mathcal{S}, \mathcal{R},\textit{Commits}), for \textit{Commits} being the set of secret commitments of wallets with balances of at least 0.1 ETH or 100 USDC, after fees. keywords: commitment; mapping; transaction cache: ethresear-14714.html plain text: ethresear-14714.txt item: #1086 of 3327 id: ethresear-14724 author: ethresear title: ethresear-14724 date: None words: 692 flesch: 49 summary: Alternatively, if we require un-concentrated liquidity then the elasticity in the above characterization is positive but smaller or equal to 1. If we further add symmetry in market making – an AMM is symmetric if the names of the token types can be changed without changing how the market is made – the AMMs in the class of homogeneous, independent AMMs with un-concentrated liquidity can be ranked by the curvature of their liquidity curves which determines how favorably the terms of trade are from the point of view of traders; the constant product rule is characterized by being trader optimal within this class. keywords: axioms; liquidity cache: ethresear-14724.html plain text: ethresear-14724.txt item: #1087 of 3327 id: ethresear-14748 author: ethresear title: ethresear-14748 date: None words: 1759 flesch: 82 summary: Every append, we should insert merkle tree nodes with constraints below. If there are N leaf nodes but you want to know merkle root when there were K nodes, you just query with regarding confirmed nodes (which are inserted when K+1 ~ N leaf nodes inserted) as unconfirmed nodes. keywords: merkle; node cache: ethresear-14748.html plain text: ethresear-14748.txt item: #1088 of 3327 id: ethresear-14750 author: ethresear title: ethresear-14750 date: None words: 143 flesch: 62 summary: We support 30+ evm chains( mainnet and testnets) https://web3client.app You can, Create ABIs with methods Execute them using metamask connection Switch between chains and contracts easily Share your ABIs to anyone to try it. Developer tool for execting methods in deployed contract - Applications - Ethereum Research Ethereum Research Developer tool for execting methods in deployed contract Applications samvelraja February 3, 2023, 11:36pm 1 Hi everyone, We have developed a tool for web3 developers for easy interaction with any smart contracts in evm. keywords: contract cache: ethresear-14750.html plain text: ethresear-14750.txt item: #1089 of 3327 id: ethresear-14752 author: ethresear title: ethresear-14752 date: None words: 400 flesch: 61 summary: Dan zdanl February 5, 2023, 11:49am 2 I wanted to mention this American Fuzzy Loop AFL quote, in case you want to make compiled smart contracts more verifiable: Internal filesystem checksums also pose a challenge. Bluntly, I was reading about the Deployment mechanism of “Compiled EVM Smartcontracts” sent to an empty recipient address / or 0x00. keywords: ethereum; evm cache: ethresear-14752.html plain text: ethresear-14752.txt item: #1090 of 3327 id: ethresear-14758 author: ethresear title: ethresear-14758 date: None words: 116 flesch: 46 summary: Serverless: Off-chain EWASM without the on-chain risk - Execution Layer Research - Ethereum Research Ethereum Research Serverless: Off-chain EWASM without the on-chain risk Execution Layer Research zdanl February 5, 2023, 12:27pm 1 Would like to suggest Off-Chain XMLHTTPRequest capable [1] support to EWASM, seperate from Smartcontract execution, calling it Serverless or so Should cost gas to deploy, but not to call. If that is too much computational tax, should be offloaded to WebWorkers, in part at least. keywords: chain cache: ethresear-14758.html plain text: ethresear-14758.txt item: #1091 of 3327 id: ethresear-14762 author: ethresear title: ethresear-14762 date: None words: 4851 flesch: 70 summary: Other people are trying to make the internet itself less censorable. llllvvuu February 7, 2023, 3:54am 2 I’ve thought about these types of systems a lot, and I’ve seen many people come up with similar ideas. keywords: february; market; murraci; people; schelling; system; truth cache: ethresear-14762.html plain text: ethresear-14762.txt item: #1092 of 3327 id: ethresear-14782 author: ethresear title: ethresear-14782 date: None words: 537 flesch: 36 summary: The aim is to classify either a single transactions (or wallet) or a series of transactions based on the relative relations from both past and present interactions represented as a transaction graph that evolves over time from the Ethereum blockchain network and develop new TGN (temporal graph neural networks) methodologies in the process. Anomaly detection through Temporal Graph Neural Networks (thoughts?) - keywords: graph; networks cache: ethresear-14782.html plain text: ethresear-14782.txt item: #1093 of 3327 id: ethresear-14813 author: ethresear title: ethresear-14813 date: None words: 140 flesch: 63 summary: Cross rollup censorship resistance - Layer 2 - Ethereum Research Ethereum Research Cross rollup censorship resistance Layer 2 zk-roll-up, cross-shard kelemeno February 13, 2023, 11:56pm 1 Hello, has anyone thought about/solved cross rollup censorship resistance, i.e. cross rollup forced transactions? I have some thoughts, but they would require a major overhaul of the system, so I guess it’s worth checking with the big brains if there are current simple solutions Thank you. keywords: cross cache: ethresear-14813.html plain text: ethresear-14813.txt item: #1094 of 3327 id: ethresear-14891 author: ethresear title: ethresear-14891 date: None words: 1785 flesch: 38 summary: Nevertheless, for the gas cost of running this scheme, secure price oracles may be constructed even on low liquidity pools while still enjoying the other properties of the TWAP algorithm, but over an interval of blocks, and with increased resilience to manipulation. \mathbf{A} is an invertible permutation matrix, but not necessarily unique because of the possibility of repeat price values. keywords: median; scheme cache: ethresear-14891.html plain text: ethresear-14891.txt item: #1095 of 3327 id: ethresear-14901 author: ethresear title: ethresear-14901 date: None words: 669 flesch: 64 summary: It wouldn’t work on accounts that have already sent any tx’s today (since those reveal public keys), but such accounts could easily send all their assets to a new keypair, and vow to not reveal their public key in those cases. This also probably requires some renaming of terminology; for instance, public keys shouldn’t be public, so renaming them to be like, quantum insecure keys, hidden keys, or private addresses or something might be useful. keywords: key; quantum cache: ethresear-14901.html plain text: ethresear-14901.txt item: #1096 of 3327 id: ethresear-14906 author: ethresear title: ethresear-14906 date: None words: 51 flesch: 17 summary: Uncouple blobs from the execution payload - Sharding - Ethereum Research Ethereum Research Uncouple blobs from the execution payload Sharding proposer-builder-separation potuz February 26, 2023, 11:56am 1 Moved here by @dankrad suggestion 1 Like Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled keywords: blobs cache: ethresear-14906.html plain text: ethresear-14906.txt item: #1097 of 3327 id: ethresear-14920 author: ethresear title: ethresear-14920 date: None words: 2751 flesch: 47 summary: In practice, this means that honest validators would not vote to finalize a block which they do not see as confirmed. Moreover, if honest validators see the justification before the next slot, they will never cast an FFG vote with an earlier source, and so the proposal will never be reorged, even if later the network becomes asynchronous. keywords: ghost; protocol; slot; validators cache: ethresear-14920.html plain text: ethresear-14920.txt item: #1098 of 3327 id: ethresear-14930 author: ethresear title: ethresear-14930 date: None words: 1987 flesch: 56 summary: This document lays out an extremely simple SNARK-based mechanism for persistent pseudonyms that allow reputation accrual. As such, our proof mechanism must allow a pseudonym-holder to associate Eth-based sets they’re into pseudonyms they control. keywords: membership; proof; pseudonym cache: ethresear-14930.html plain text: ethresear-14930.txt item: #1099 of 3327 id: ethresear-14957 author: ethresear title: ethresear-14957 date: None words: 2836 flesch: 54 summary: We show that the resulting incentives to invest in latency advantage are very different: constant in the former case and decreasing/finite in the latter. One can argue that now the searcher can first invest in centralizing the network (e.g., moving wallet providers and/or validators) and then invest in latency advantage at a lower unit cost. keywords: advantage; latency; mev; ordering; searcher; time cache: ethresear-14957.html plain text: ethresear-14957.txt item: #1100 of 3327 id: ethresear-14962 author: ethresear title: ethresear-14962 date: None words: 726 flesch: 52 summary: Multiplicity is a practical gadget that allows non-leader nodes to include additional transactions into a block. In order to improve the censorship resistance of a chain we need to destroy this monopoly by allowing multiple concurrent block proposers (MCBP). keywords: block; leader cache: ethresear-14962.html plain text: ethresear-14962.txt item: #1101 of 3327 id: ethresear-15 author: ethresear title: ethresear-15 date: None words: 3173 flesch: 42 summary: Looking forward, we plan to pursue optimizations, collaborations and real-world deployment to bring maze witness encryption from theory into practice. Usability analysis - How can we create intuitive and accessible user interfaces for maze witness encryption? Applications - What promising use cases can be implemented and evaluated with stakeholders? keywords: coloring; encryption; generation; graph; knowledge; maze; proof; security; witness cache: ethresear-15.html plain text: ethresear-15.txt item: #1102 of 3327 id: ethresear-15010 author: ethresear title: ethresear-15010 date: None words: 683 flesch: 51 summary: Oracle extension guard design The guard extension defines OBSERVATIONS number of observations SKIP step between two observations MAX_OUTLIERS max number of observations out of range MAX_SINGLE_TICK_DELTA max delta between observations MAX_TOTAL_TICK_DELTA max delta in array with most observations The guard checks a set number of OBSERVATIONS within the range OBSERVATIONS * To increase the safety of the TWAP oracle under PoS I propose an oracle extension that acts as a guard to only allow price updates for a predefined max delta between price observations. keywords: observations; oracle cache: ethresear-15010.html plain text: ethresear-15010.txt item: #1103 of 3327 id: ethresear-15012 author: ethresear title: ethresear-15012 date: None words: 64 flesch: 60 summary: Proof of Entropy Minima - Consensus - Ethereum Research Ethereum Research POEM: Proof of Entropy Minima Consensus alanorwick March 9, 2023, 5:20pm 1 Interesting paper our team has created regarding entropic consensus. Proof of Entropy Minima Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled keywords: poem cache: ethresear-15012.html plain text: ethresear-15012.txt item: #1104 of 3327 id: ethresear-15016 author: ethresear title: ethresear-15016 date: None words: 3844 flesch: 65 summary: L1 searchers and block builders are incentivised to extract rollup MEV by including rollup blocks within their L1 bundles and L1 blocks. This then incentivises L1 proposers to include rollup blocks on the L1. simplicity: Based sequencing is maximally simple; significantly simpler than even centralised sequencing. keywords: block; march; mev; rollup; sequencing cache: ethresear-15016.html plain text: ethresear-15016.txt item: #1105 of 3327 id: ethresear-15059 author: ethresear title: ethresear-15059 date: None words: 2156 flesch: 54 summary: 8 Likes Proving Rollups' State ralexstokes March 15, 2023, 11:46pm 2 you mention bedrock-style rollups and it looks like you can just query for the latest L1 blockhash in the L1Block contract linked here: Differences between Ethereum and Optimism | Optimism Docs instead of needing to include an on-chain light client (and moreover prove/verify a SNARK of the transition), you can just prove whatever source rollup state this way blockhash->state root->source rollup contract->source rollup storage key(s) it seems like if you go this route you don’t even need any relay actor… the downside here is that you have to wait for the next L1 block and we may want to message cross-rollup regardless of the L1 activity – here we could explore having on-chain light clients where the source rollup and destination rollup are light clients of each other this is basically the IBC construction from cosmos Abstract The following aims to describe an enshrined Cross-Rollup-Communication protocol for data transfer between rollups, completely aligned with Ethereum’s rollup-centric future and supporting the Ethereum community. keywords: ethereum; protocol; rollup; source; state cache: ethresear-15059.html plain text: ethresear-15059.txt item: #1106 of 3327 id: ethresear-15078 author: ethresear title: ethresear-15078 date: None words: 5185 flesch: 65 summary: It’s hard to imagine blob prices ever being at the minimum pricing. It’s hard to imagine blob prices ever being at the minimum pricing. keywords: blob; cost; data; demand; fee; gas; market; price; start cache: ethresear-15078.html plain text: ethresear-15078.txt item: #1107 of 3327 id: ethresear-15100 author: ethresear title: ethresear-15100 date: None words: 2451 flesch: 62 summary: An option could be to replace the lower part of the circuit with a gate that checks that the address that maps to the private key belongs to a certain membership set that would represent the set of designated verifiers. 5 Future Work and MDVS Multi-designated verifier singatures (MDVS) is an extension of designated verifier signatures to the multiparty setting. keywords: bob; key; message; verifier cache: ethresear-15100.html plain text: ethresear-15100.txt item: #1108 of 3327 id: ethresear-15126 author: ethresear title: ethresear-15126 date: None words: 346 flesch: 64 summary: Graduation research Ethereum ecosystem - Administrivia - Ethereum Research Ethereum Research Graduation research Ethereum ecosystem Administrivia JonB March 24, 2023, 10:19am 1 Dear readers, At the moment I am doing my graduation research at the Open University located in the Netherlands. Lots of interesting case studies that have come from our community and DAO: https://forum.pokt.network/ 3 Likes Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled keywords: research cache: ethresear-15126.html plain text: ethresear-15126.txt item: #1109 of 3327 id: ethresear-15131 author: ethresear title: ethresear-15131 date: None words: 3326 flesch: 59 summary: Hyper Oracle zkOracle is natively categorized as output zkOracle and I/O zkOracle. Hyper Oracle zkOracle and zkWASM are all in Halo2 PSE. keywords: chain; computation; data; network; output; source; zkoracle cache: ethresear-15131.html plain text: ethresear-15131.txt item: #1110 of 3327 id: ethresear-15143 author: ethresear title: ethresear-15143 date: None words: 6710 flesch: 54 summary: It returns secret keys corresponding to a token generation algorithm and a function of the smart contract. As the master secret key is not exposed, the FE scheme ensures that their ciphertext and secret key only reveal the circuit output. keywords: circuit; contract; input; key; scheme; secret; user cache: ethresear-15143.html plain text: ethresear-15143.txt item: #1111 of 3327 id: ethresear-15154 author: ethresear title: ethresear-15154 date: None words: 1178 flesch: 60 summary: One could imagine a registry contract, storing which addresses have posted valid adhaar cards proofs. Using the groth16 proving scheme opens up the ability to port valid adhaar card proof holders data onchain. keywords: adhaar; card; proof; signature cache: ethresear-15154.html plain text: ethresear-15154.txt item: #1112 of 3327 id: ethresear-15169 author: ethresear title: ethresear-15169 date: None words: 698 flesch: 56 summary: #1 and #2 Blockchain RPC: eth_getProof is present in the node’s codebase, but not exposed in public RPC endpoints Witness nodes data for Merkle Inclusion Proof can be accessed if a private node is used Taiko MPT keccak mapping of number → blockHash Blockchain RPC: eth_getProof zkSync Era Sparse Merkle Tree Blake2 mapping of number → blockHash Not supported Witness nodes data for Merkle Inclusion Proof is not freely available StarkNet MPT Poseidon mapping of number → state root hash Blockchain RPC: pathfinder_getProof Linea (ConsenSys zkEVM) Sparse Merkle Tree MiMC Contract not open-sourced and not verified Not Supported. Blockchain RPC endpoint for mapping batchNumber to blockNumber Not Supported Witness nodes data for Merkle Inclusion Proof is not freely available Scroll MPT Poseidon Contract not open-sourced and not verified. keywords: precompiles; state cache: ethresear-15169.html plain text: ethresear-15169.txt item: #1113 of 3327 id: ethresear-15180 author: ethresear title: ethresear-15180 date: None words: 3041 flesch: 69 summary: Order books will also enable financial instruments with expiration dates, such as bonds, options, and prediction markets, to find a natural home in DeFi, with liquidity supplied in a manner that AMMs cannot match. With LOBSTER, market participants can place limit and market orders in a fully decentralized, trustless way at a manageable cost. keywords: heap; order; price; segment; tree cache: ethresear-15180.html plain text: ethresear-15180.txt item: #1114 of 3327 id: ethresear-15214 author: ethresear title: ethresear-15214 date: None words: 1010 flesch: 66 summary: Let’s add a parameter s to the function f(X, i, s) If Bob goes to dApp A, generates an address A = f(M, x, s1), then goes to dApp B, generates an address B = g(M, x, s2), they MUST NOT be the same. Where HMAC can be HMAC-SHA256 or HMAC-KECCAK256; I would be in favor or SHA since it’s compatible with WebCrypto sign(X, m) is the process of signing a message m with identity X, with e.g. eth_signMessage secp256k1(seed) is derivating a secp256k1 curve point from a crypto secure seed, with a KDF if necessary salt is a public crypto secure random value The problem with such function is that the message to be signed is not human readable since it’s a HMAC output Proposal 2 with outer salt We could use HMAC outside the signature g(wallet, index, salt) = secp256k1(HMAC(sign(wallet, Ethereum Wallet Derivation: + index), salt)) keywords: index cache: ethresear-15214.html plain text: ethresear-15214.txt item: #1115 of 3327 id: ethresear-15231 author: ethresear title: ethresear-15231 date: None words: 1003 flesch: 57 summary: So one of the future scaling is something like the end-clients compute somthing on their devices and submiting a proof instead of letting other execution layer nodes to run all the computations. In this scenario, we can have an Edge Computing Interface such as execution( function, input vars, state refs, proof ) -> output vars: {\[key\]: value} keywords: ethereum; state cache: ethresear-15231.html plain text: ethresear-15231.txt item: #1116 of 3327 id: ethresear-15232 author: ethresear title: ethresear-15232 date: None words: 1894 flesch: 53 summary: By the way, we can use KZG polynomial commitment scheme and its opening which fits pretty perfect for the RLN scheme. RLN on KZG polynomial commitment scheme [cross-posted] - General - zk research Updates: verification per each message will cost 2 pairing computations since e(g^{f(\alpha)}, g) can be computed at the beginning of the epoch and then cached to be used repeatedly for its future message evaluations. keywords: \cdot; commitment; e(g; polynomial cache: ethresear-15232.html plain text: ethresear-15232.txt item: #1117 of 3327 id: ethresear-15246 author: ethresear title: ethresear-15246 date: None words: 1350 flesch: 72 summary: This is true for intermediary hashes i_2 and i_3 as well in the next set of leaf circuits. We can now easily span this out for larger N as follows. image2388×2340 181 KB Figure 5 The first thing you should note in the above diagram is - the middle level recursive circuits behave as leaf circuits to the final node circuit. keywords: circuit; hashes cache: ethresear-15246.html plain text: ethresear-15246.txt item: #1118 of 3327 id: ethresear-15248 author: ethresear title: ethresear-15248 date: None words: 136 flesch: 53 summary: Ola’s objective is to create a Layer 2 platform that combines privacy, high performance, and programmability. In this updated edition of the white paper, you will discover the design and construction of a high-performance ZKVM, known as OlaVM; the development of a Zero-Knowledge-friendly smart contract language, Ola-lang; and the privacy design architecture. keywords: privacy cache: ethresear-15248.html plain text: ethresear-15248.txt item: #1119 of 3327 id: ethresear-15313 author: ethresear title: ethresear-15313 date: None words: 1319 flesch: 41 summary: Top Blockspace: Harmful MEV protection The shared sequencing layer consists of the following components to protect user transactions from harmful MEV: Encryption-as-a-Service (EaaS): Enables secure transaction encryption using Practical Verifiable Delay Encryption (PVDE), a zero-knowledge-based scheme that employs time-lock puzzles to generate zk proof on user’s side. The proposed solution consists of a two-tiered blockspace structure: Top blockspace is intended for regular user transactions and offers cryptographic protection against harmful MEV, while the Bottom blockspace is designed for builders to carry out revenue-generating activities. keywords: blockspace; mev; time cache: ethresear-15313.html plain text: ethresear-15313.txt item: #1120 of 3327 id: ethresear-15317 author: ethresear title: ethresear-15317 date: None words: 242 flesch: 60 summary: Two similar incidents: Polygon: Polygon Lack Of Balance Check Bugfix Review — $2.2m Bounty | by Immunefi | Immunefi | Medium https://polygon.technology/blog/all-you-need-to-know-about-the-recent-network-upgrade Binance Release v1.1.16 · bnb-chain/bsc · GitHub 3 Likes pcaversaccio April 20, 2023, 9:52am 2 Two scenarios where I deem such a scenario plausible: The Beacon Deposit Contract has a (maybe compiler) bug that a black hat exploits and withdraws all staked ETH (at the time of this writing 18,833,884 ETH). Do we need further governance mechanisms to prevent such an incident completely (e.g. disallowing such EIP proposals etc.). keywords: ethereum cache: ethresear-15317.html plain text: ethresear-15317.txt item: #1121 of 3327 id: ethresear-15320 author: ethresear title: ethresear-15320 date: None words: 695 flesch: 62 summary: AI Rollup, replacing fault/validity proof with AI oracle proof - Layer 2 - Ethereum Research Ethereum Research AI Rollup, replacing fault/validity proof with AI oracle proof Layer 2 zk-roll-up fewwwww April 16, 2023, 6:57pm 1 First of all, this is just a wild idea. Or we can only include AI Oracle Proof into multi-prover rollup architecture, so we can have a 3/4 multi-sig… Development of On-chain AI and zkML: zkML and on-chain AI can be combined together, and there is already zkML that can do GPT-2. keywords: proof cache: ethresear-15320.html plain text: ethresear-15320.txt item: #1122 of 3327 id: ethresear-15328 author: ethresear title: ethresear-15328 date: None words: 165 flesch: 57 summary: ERC-4337 - Can Token owners remotely delete token supplies from abstract smart contract wallets? - Security - Ethereum Research Ethereum Research ERC-4337 - Can Token owners remotely delete token supplies from abstract smart contract wallets? keywords: contract cache: ethresear-15328.html plain text: ethresear-15328.txt item: #1123 of 3327 id: ethresear-15363 author: ethresear title: ethresear-15363 date: None words: 270 flesch: 48 summary: Proposal To improve gas estimation, we propose tracking internal transaction failures caused by out of gas errors and changing the condition for lowering the amount of gas. It lowers the amount of gas if the simulation is successful and raises it if the simulation fails with an out of gas error. keywords: gas cache: ethresear-15363.html plain text: ethresear-15363.txt item: #1124 of 3327 id: ethresear-15377 author: ethresear title: ethresear-15377 date: None words: 920 flesch: 47 summary: = newRootHash2 and proof_is_valid(circuit, proof1, oldRootHash, newRootHash1, txData) and proof_is_valid(circuit, proof2, oldRootHash, newRootHash2, txData) { // put rollup in emergency state } } } The current state of the rollup // Update the state if the proof is valid function update( oldRootHash, newRootHash, txData, // The list of the transactions proof // the proof that the transition is valid ) { if currentRootHash == oldRootHash and proof_is_valid(circuit, proof, oldRootHash, newRootHash, txData) { currentRootHash = newRootHash } } } (1) Soundness alert function This was briefly mentioned by VB in his presentation on multiprovers (applied here to a single prover rollup) keywords: rollup; state cache: ethresear-15377.html plain text: ethresear-15377.txt item: #1125 of 3327 id: ethresear-15390 author: ethresear title: ethresear-15390 date: None words: 1412 flesch: 58 summary: I have enabled AI model inference in blockchain systems in both on-chain and off-chain approaches. To ensure the efficiency of AI model inference in the rollup VM, I have implemented a lightweight DNN library specifically designed for this purpose instead of relying on popular ML frameworks like Tensorflow or PyTorch. keywords: blockchain; chain; inference; model cache: ethresear-15390.html plain text: ethresear-15390.txt item: #1126 of 3327 id: ethresear-15402 author: ethresear title: ethresear-15402 date: None words: 896 flesch: 73 summary: Trustless Computer nodes agree on the ordering of the EVM transactions written to each Bitcoin block. Building an EVM for Bitcoin - EVM - Ethereum Research Ethereum Research Building an EVM for Bitcoin EVM punk3700 April 24, 2023, 5:15pm 1 Our team has been working on a fun experiment of combining an EVM with Bitcoin in the last couple of months. keywords: april; bitcoin cache: ethresear-15402.html plain text: ethresear-15402.txt item: #1127 of 3327 id: ethresear-15404 author: ethresear title: ethresear-15404 date: None words: 529 flesch: 44 summary: In decentralized relays, ZKPs can be used to validate transactions or state transitions without disclosing sensitive data. Novel architecture and actors are needed to create functioning decentralized relay. keywords: mev; relay cache: ethresear-15404.html plain text: ethresear-15404.txt item: #1128 of 3327 id: ethresear-15424 author: ethresear title: ethresear-15424 date: None words: 1284 flesch: 82 summary: It nows sends a proof to W along with public inputs H(sA,x,1) (nullifier), H(sA,x-y), H(B_r, y). A wants to transfer y eth to B All the transfers happen inside the contract, so W.balance doesn’t change and using cryptography and ZK, observers aren’t able to recognize the amount being transferred, and the addresses between which the transfer is happening. keywords: hash cache: ethresear-15424.html plain text: ethresear-15424.txt item: #1129 of 3327 id: ethresear-15437 author: ethresear title: ethresear-15437 date: None words: 1298 flesch: 60 summary: hashS = (int(h.hexdigest(), 16)) % class_number hashS_reduced = reduce(hashS,A,B) P = action(M,hashS_reduced) #Bob Sb = action(R, m) pv = [] for i,_ in enumerate(m): pv.append(m[i]+hashS_reduced[i]) assert Sa == Sb assert P == action(base,pv) Acknowledgement Thanks to Vitalik Buterin, Luciano Maino, Michele Orrù and Mark Simkin for fruitful discussions and comments. With stealth addresses, however, the sender generates a unique, one-time public address for each transaction, which is not linked to their permanent public address on the blockchain. keywords: bob; stealth cache: ethresear-15437.html plain text: ethresear-15437.txt item: #1130 of 3327 id: ethresear-15454 author: ethresear title: ethresear-15454 date: None words: 547 flesch: 48 summary: Safe block confirmation rule High confidence single block confirmations in Casper FFG 2 Likes SubnetDAS - an intermediate DAS approach Super-Finality: High-Safety Confirmation for Casper czhang-fm September 1, 2023, 2:13am 2 adiasg: in the last equation of q_{b’}^n > … total honest weight … isLMDConfirmed(b, n) Please change to “total weight from slot(b’.parent)+1 to n” 1 Like Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled From the current slot onwards, the votes cast by honest validators in a slot are received by all validators by the end of that slot, i.e., the network is synchronous with latency < 8 seconds. keywords: ethereum; slot cache: ethresear-15454.html plain text: ethresear-15454.txt item: #1131 of 3327 id: ethresear-15463 author: ethresear title: ethresear-15463 date: None words: 8237 flesch: 32 summary: Background on gas estimation methods: Gas estimation is an essential aspect of executing transactions on the Ethereum network. Transaction complexity: Complex transactions involving multiple smart contract interactions or conditional execution paths can introduce additional uncertainty in gas usage estimation, reducing the accuracy of these methods. keywords: estimation; gas; nft; state; transactions; usage cache: ethresear-15463.html plain text: ethresear-15463.txt item: #1132 of 3327 id: ethresear-15486 author: ethresear title: ethresear-15486 date: None words: 266 flesch: 49 summary: Limit Order Ticks - Decentralized exchanges - Ethereum Research Ethereum Research Limit Order Ticks Decentralized exchanges 0xrahul May 4, 2023, 4:33pm 1 Introduction The concept of limit order ticks involves inserting new ticks on an AMM curve to allow for highly concentrated liquidity at a single price point. Limit Order Liquidity Limit order liquidity is a uni-directional liquidity concept. keywords: liquidity cache: ethresear-15486.html plain text: ethresear-15486.txt item: #1133 of 3327 id: ethresear-15487 author: ethresear title: ethresear-15487 date: None words: 3657 flesch: 43 summary: World Supercomputer Components The final World Supercomputer will be made up of three topologically heterogeneous P2P networks: a consensus ledger, computation network, and storage network connected by a trust-minimized bus (connector) such as zero-knowledge proof technology. World Supercomputer Architecture Similar to building a physical computer, we must assemble the consensus network, computation network, and storage network mentioned previously into a World Supercomputer. keywords: computation; consensus; ethereum; network; storage; supercomputer; world cache: ethresear-15487.html plain text: ethresear-15487.txt item: #1134 of 3327 id: ethresear-15489 author: ethresear title: ethresear-15489 date: None words: 3834 flesch: 53 summary: A new user Carol adds a 1 ETH sell order on Tick B. Since limit order liquidity is uni-directional, Tick B has filled limit order liquidity (worth 3 ETH) of Alice and Bob and unfilled limit order liquidity of Carol (1 ETH). On-Chain settlement of Limit Orders As we know, a user’s limit order liquidity is embedded on the concentrated liquidity curve, so when swaps happen limit order liquidity is utilized along with concentrated liquidity. keywords: chain; limit; liquidity; order; price; tick cache: ethresear-15489.html plain text: ethresear-15489.txt item: #1135 of 3327 id: ethresear-15500 author: ethresear title: ethresear-15500 date: None words: 4469 flesch: 60 summary: The value of builder bids as time passes. A majority of builder bids arrive around t=0, which marks the beginning of the proposer’s slot. keywords: bid; bids; builder; cancellations; getheader; proposer cache: ethresear-15500.html plain text: ethresear-15500.txt item: #1136 of 3327 id: ethresear-15504 author: ethresear title: ethresear-15504 date: None words: 1263 flesch: 61 summary: ZKP's Two-Step Submission Algorithm: An Implementation of Decentralized Provers - Layer 2 - Ethereum Research Ethereum Research ZKP's Two-Step Submission Algorithm: An Implementation of Decentralized Provers Layer 2 zk-roll-up nanfengpo May 5, 2023, 12:39pm 1 Why do we need decentralized provers? We are currently focused on the issue of decentralized sequencer, but most people overlook the fact that currently, most ZK-Rollup projects have not implemented decentralized provers. keywords: hash; prover; zkp cache: ethresear-15504.html plain text: ethresear-15504.txt item: #1137 of 3327 id: ethresear-15529 author: ethresear title: ethresear-15529 date: None words: 718 flesch: 64 summary: L2 Economics of Daily Airdrops (Arbitrary Amounts to Growing Base of Players) - Economics - Ethereum Research Ethereum Research L2 Economics of Daily Airdrops (Arbitrary Amounts to Growing Base of Players) Economics cleanapp May 8, 2023, 3:21pm 1 hi fam … we really need your help optimizing the cost of a daily airdrop-like distro for our game in our game, players win different amounts of points each day at 19:45 UTC, everyone’s individual balance is calculated offchain (including some referral bonus points calcs) & a universal snapshot is taken: Player A = 59 points; Player B = 182 points; … Player N = 12 points. at 20:00 UTC, the token script ingests the snapshot & distributes ERC20 tokens commensurate with the Players’ daily accrued point balance from players’ POV, there is no “Claim” required; there is zero financial cost to play; we abstract blockchain away until such time as players want to interact with their ERC20 versions of their points & do whatever they’ll want to do with their points (tldr: CleanApp-the-game pays for the daily distro) we’re optimizing gameplay for maximum number of players (10M+), so need a scaling solution that’s cheap and secure Questions: what’s the cheapest L2 for our game? I don’t think we can prove this on Ethereum in a trustless way? 1 Like parseb May 18, 2023, 11:21am 5 No, not on Ethereum, not by default. keywords: points; tree cache: ethresear-15529.html plain text: ethresear-15529.txt item: #1138 of 3327 id: ethresear-15544 author: ethresear title: ethresear-15544 date: None words: 1126 flesch: 62 summary: anightmarre July 6, 2023, 8:50am 4 it’s great to see ongoing research and discussion around extending the economic guarantees of Schellingcoin oracles. These types of oracles play a crucial role in blockchain ecosystems by bridging the gap between the on-chain and off-chain worlds. keywords: oracle; protocol; token cache: ethresear-15544.html plain text: ethresear-15544.txt item: #1139 of 3327 id: ethresear-15547 author: ethresear title: ethresear-15547 date: None words: 1434 flesch: 47 summary: Some arguments why large validators wouldn’t want to consolidate even if they have the option: Slashing risk: It’s easier to mitigate large slashing events, i.e. script that shuts down all validators if one get slashed. We should remove this unnecessary stress from Ethereum’s p2p network by allowing large staking entities to consolidate their stake into fewer validators. keywords: ethereum; network; validator cache: ethresear-15547.html plain text: ethresear-15547.txt item: #1140 of 3327 id: ethresear-15547? author: ethresear title: ethresear-15547? date: None words: 1434 flesch: 47 summary: Some arguments why large validators wouldn’t want to consolidate even if they have the option: Slashing risk: It’s easier to mitigate large slashing events, i.e. script that shuts down all validators if one get slashed. We should remove this unnecessary stress from Ethereum’s p2p network by allowing large staking entities to consolidate their stake into fewer validators. keywords: ethereum; network; validator cache: ethresear-15547?.html plain text: ethresear-15547?.txt item: #1141 of 3327 id: ethresear-15551 author: ethresear title: ethresear-15551 date: None words: 927 flesch: 72 summary: It takes the proposer boost and allows honest proposers to use it to forcibly reorg blocks that have attestation weight below 20%. Eth 2.0 takes many effects to mitigate selfish mining, including proposer boost and honest reorgs. keywords: block; slot cache: ethresear-15551.html plain text: ethresear-15551.txt item: #1142 of 3327 id: ethresear-15553 author: ethresear title: ethresear-15553 date: None words: 351 flesch: 25 summary: A research on MEV transaction detection using Graph Neural Networks - Economics - Ethereum Research Ethereum Research A research on MEV transaction detection using Graph Neural Networks Economics mev wanify May 11, 2023, 2:47am 1 We are excited to share our paper on MEV detection method using Graph Neural Networks (ArbiNet) arXiv.org Unraveling the MEV Enigma: ABI-Free Detection Model using Graph Neural Networks The detection of Maximal Extractable Value (MEV) in blockchain is crucial for enhancing blockchain security, as it enables the evaluation of potential consensus layer risks, the effectiveness of anti-centralization solutions, and the assessment of... Our code, pre-trained models, and preprocessed graphs are available here: GitHub GitHub - etelpmoc/arbinet Contribute to etelpmoc/arbinet development by creating an account on GitHub. In this paper, we propose ArbiNet, a novel GNN-based detection model that offers a low-overhead and accurate solution for MEV detection without requiring knowledge of smart contract code or ABIs. keywords: detection; mev cache: ethresear-15553.html plain text: ethresear-15553.txt item: #1143 of 3327 id: ethresear-15559 author: ethresear title: ethresear-15559 date: None words: 1508 flesch: 67 summary: So the total time to act on an event e in B1 is: time to get B33 (epoch time = 6.4 mins) + time to obtain supermajority attestation of B33 + snark proof construction time (4 mins). seunlanlege August 23, 2023, 7:48am 9 Not really, supermajority attestations can happen before B65. keywords: august; b65 cache: ethresear-15559.html plain text: ethresear-15559.txt item: #1144 of 3327 id: ethresear-15560 author: ethresear title: ethresear-15560 date: None words: 328 flesch: 41 summary: This fragmentation of knowledge makes it challenging to assess the differences between developing on L1 versus a given Rollup, or between different Rollups. Additionally, it is unclear what custom precompiles exist on Rollups, which precompiles are supported, what L1 state is exposed on a Rollup, what system-level contracts exist, what the gas costs, latency and interface are for L1 - L2 messaging and how EVM gas pricing has changed. keywords: rollup cache: ethresear-15560.html plain text: ethresear-15560.txt item: #1145 of 3327 id: ethresear-15585 author: ethresear title: ethresear-15585 date: None words: 717 flesch: 42 summary: With Xtreamly’s AA model, miners and validating nodes in Ethereum process transactions and blocks simply by accessing a short commitment of the current state found in the most recent block. Stateless Account abstraction that scales Ethereum without chainges in protocol - Execution Layer Research - Ethereum Research Ethereum Research Stateless Account abstraction that scales Ethereum without chainges in protocol Execution Layer Research sogolmalek May 14, 2023, 10:01pm 1 Dear Ethereum Community, I am excited to share with you an ongoing EIP proposal that aims to enable statelessness at Ethereum account level (yet) allowing for a stateless account abstraction that scales Ethereum. keywords: account; ethereum cache: ethresear-15585.html plain text: ethresear-15585.txt item: #1146 of 3327 id: ethresear-15590 author: ethresear title: ethresear-15590 date: None words: 5921 flesch: 58 summary: builder bids: Builders gossip bids which contain: payload commitment: a commitment to an execution payload payload tip: an amount no larger than the builder balance builder pubkey: the ECDSA pubkey for the builder address builder signature: the signature of the builder bid winning bid: The proposer has a time window to select a bid to include in their proposal. (The bull case for MEV burn is based rollups and enshrined rollups.) tax efficiency: EIP-1559 and MEV burn can significantly improve staking tax efficiency in some jurisdictions by converting income (taxed at, say, 50%) into capital gains (taxed at, say, 20%). keywords: base; base fee; builder; burn; fee; floor; mev; payload; proposer cache: ethresear-15590.html plain text: ethresear-15590.txt item: #1147 of 3327 id: ethresear-15626 author: ethresear title: ethresear-15626 date: None words: 1084 flesch: 57 summary: Again, for now, the variance of the equilibrium price is determined by the variances in the shifts of supply and demand, as well as the relationship between the two. Intuitively, if the shifts in supply and demand are positively related, the variance of the equilibrium price decreases, and vice versa. keywords: demand; supply cache: ethresear-15626.html plain text: ethresear-15626.txt item: #1148 of 3327 id: ethresear-15634 author: ethresear title: ethresear-15634 date: None words: 302 flesch: 36 summary: Sync committees - exited validators participating in sync committee? - Security - Ethereum Research Ethereum Research Sync committees - exited validators participating in sync committee? keywords: sync cache: ethresear-15634.html plain text: ethresear-15634.txt item: #1149 of 3327 id: ethresear-15636 author: ethresear title: ethresear-15636 date: None words: 765 flesch: 64 summary: L2 block builders can run the mev-boost that L1 builders use; L2 block builder can also be an L1 searcher and include L2 blocks into L1 bundles on its own; L1 builders will include L2 blocks into their L1 blocks as long as there is at least a tiny of piece of MEV in this block (and the gas limit is not reached). L2 MEV flow mechanism L2 searchers collect L2 transactions into bundles and send them to L2 block builders; L2 block builders take these bundles and build a block. keywords: mev cache: ethresear-15636.html plain text: ethresear-15636.txt item: #1150 of 3327 id: ethresear-15649 author: ethresear title: ethresear-15649 date: None words: 1118 flesch: 64 summary: This leads that the blue votes are invalid to purple validators and also the purple votes are invalid to blue validators. This leads that the blue votes are invalid to purple validators and also the purple votes are invalid to blue validators Validators which see the blue chain as canonical at the end of the network partition can still process the other chain and the votes for it, and they can switch to it, and viceversa. mart1i1n: keywords: epoch; validators cache: ethresear-15649.html plain text: ethresear-15649.txt item: #1151 of 3327 id: ethresear-15667 author: ethresear title: ethresear-15667 date: None words: 954 flesch: 53 summary: Not just bridges, securing external applications using Ethereum Social consensus is hard While we have analyzed this strictly from a bridging perspective, if we think carefully, this constraint applies to all situations where we are securing value outside the Ethereum blockchain, while using Ethereum security. The current value of $35 bn is good, but in future, if this value can cross $1 trillion, it will give confidence to applications that wish to borrow Ethereum security. keywords: ethereum; security cache: ethresear-15667.html plain text: ethresear-15667.txt item: #1152 of 3327 id: ethresear-15668 author: ethresear title: ethresear-15668 date: None words: 448 flesch: 44 summary: When a sequencer receives such a Tx, it would (Validity check) check the validity of the Tx via the ZK proof and make sure the sender has sufficient ETH as gas (Sequence commitment) if the Tx is valid (although some fields are still hidden at the time of submission), it will sign the Tx with an increasing sequence id, where the sequencer is committed to execute the Tx sequentially at the id. (Reveal hidden fields) when a user receives the commitment from sequencer, it will reveal the hidden fields after T_r seconds (or observed some numbers of other Txs are committed after the user’s submission) (Liveness with VDF-Decoding) if the sequencer does not receive the revealed fields from the user in T_r seconds, it would try to decode the Tx via VDF. Alleviate MEV on Sequencer with Partial-Fields-VDF-Encoded Tx and ZK-based Validity Proof - Layer 2 - Ethereum Research Ethereum Research Alleviate MEV on Sequencer with Partial-Fields-VDF-Encoded Tx and ZK-based Validity Proof Layer 2 mev qizhou May 22, 2023, 10:54am 1 Protocol A user submits a Tx to a sequencer that part of the fields are known, e.g., sender, gas price, gas limit, calldata length, nonce are known, but to address and the actual calldata are unknown/hidden. keywords: sequencer cache: ethresear-15668.html plain text: ethresear-15668.txt item: #1153 of 3327 id: ethresear-15694 author: ethresear title: ethresear-15694 date: None words: 958 flesch: 49 summary: Like BitcoinEvm July 18, 2023, 7:35am 2 As you and the brc20 penguins people are fully aware Bitcoin EVM has already been fully developed & launched Thanks for thinking the project is so amazing though you thought it would make sense to copy a project that has been completed almost 2 years ago now. EVM Execution keywords: bitcoin; evm; execution cache: ethresear-15694.html plain text: ethresear-15694.txt item: #1154 of 3327 id: ethresear-15703 author: ethresear title: ethresear-15703 date: None words: 1938 flesch: 61 summary: I am not bringing any new proposal to save vulnerable addresses, but I would like to read more arguments for one option or the other. Do nothing The easiest way is to do nothing and not touch vulnerable addresses. keywords: addresses; coins; quantum cache: ethresear-15703.html plain text: ethresear-15703.txt item: #1155 of 3327 id: ethresear-15710 author: ethresear title: ethresear-15710 date: None words: 6138 flesch: 59 summary: Proposers earn MEV rewards in addition to their protocol issuance, and block builders compete to assemble valuable blocks while saving a portion of the MEV for themselves as profit. TBHL has the notion of proposer and builder blocks. keywords: block; boost; builder; design; epbs; ethereum; mev; proposer; protocol; relay; slot cache: ethresear-15710.html plain text: ethresear-15710.txt item: #1156 of 3327 id: ethresear-15715 author: ethresear title: ethresear-15715 date: None words: 579 flesch: 37 summary: How shall we choose the parameters of network privacy protocols to achieve a given level of anonymity? The goal of validator privacy is to create efficient network privacy protocols that hide the connection between a validator’s physical address on the network (e.g., IP address, Ethereum address) from its consensus messages (e.g., blocks, attestations). keywords: network; privacy cache: ethresear-15715.html plain text: ethresear-15715.txt item: #1157 of 3327 id: ethresear-15724 author: ethresear title: ethresear-15724 date: None words: 1135 flesch: 60 summary: Assuming 1 ETH equals 2,000 USD, the block’s transaction fees and MEV revenue generate approximately 1% annualized return for Lido. With the market displaying clear signs of oligopoly, and MEV revenues playing a pivotal role in builders’ profits, the future landscape of this space will likely be shaped by the strategies these leading entities employ to maintain their sizable pieces of the delicious cake made of MEV. keywords: market; mev; validators cache: ethresear-15724.html plain text: ethresear-15724.txt item: #1158 of 3327 id: ethresear-15748 author: ethresear title: ethresear-15748 date: None words: 439 flesch: 55 summary: I think you could use two instances of Semaphore: a key set (voter address) and value set (voting power) which share a commons set of nullifiers (effectively associating keys with values). Note that exponential ElGamal requires that the final tally be small (< 2^32 ballpark) so you may need to truncate the trailing bits of voting power (arguably you’d want to do so anyway, otherwise the exact final tally values would leak information about how people voted). keywords: cicada; voting cache: ethresear-15748.html plain text: ethresear-15748.txt item: #1159 of 3327 id: ethresear-15756 author: ethresear title: ethresear-15756 date: None words: 3121 flesch: 57 summary: That said, there is no reason, nor need to participate in governance unless you are willing to sacrifice time, effort or token value in advance to the shared benefit of all other token holders. The fuel is metabolised to energy, used for movement and eventually converted back to RVT exchangeable value to be leveraged in the external economy. keywords: dao; energy; governance; inflation; token; value; walllaws cache: ethresear-15756.html plain text: ethresear-15756.txt item: #1160 of 3327 id: ethresear-15769 author: ethresear title: ethresear-15769 date: None words: 2195 flesch: 67 summary: In a recent Bankless podcast regarding MEV burn, @JustinDrake suggests that ‘with MEV burn enabled, ETH burn could triple the current rate and ETH supply could eventually reach an equilibrium between 50 million to 100 million over the next century’. However, one could argue that getting richer from ETH burn is actually somewhat like getting richer for doing absolutely nothing, and the more ETH one has, the more one stand to benefit from doing nothing. keywords: burn; deflationary; eth; fiat cache: ethresear-15769.html plain text: ethresear-15769.txt item: #1161 of 3327 id: ethresear-15774 author: ethresear title: ethresear-15774 date: None words: 640 flesch: 53 summary: Problem: Even though existing privacy-preserving blockchain solutions like ZCash can hide the contents of blockchain transactions and maintain anonymity, they still leak volume and timing metadata (when transactions are added and how many transactions are added to the blockchain). Privatizing the Volume and Timing of Blockchain Transactions - Privacy - Ethereum Research Ethereum Research Privatizing the Volume and Timing of Blockchain Transactions Privacy trevormil June 1, 2023, 12:27pm 1 In this post, I share my paper VTBC on privatizing the volume and timing of blockchain transactions. keywords: blockchain; transactions cache: ethresear-15774.html plain text: ethresear-15774.txt item: #1162 of 3327 id: ethresear-15801 author: ethresear title: ethresear-15801 date: None words: 6238 flesch: 57 summary: Post-capella, validator balances are automatically withdrawn. Would this also reduce bandwidth requirements for some nodes, as currently running more validators means subscribing to more attestation gossip topics? keywords: balance; eth; june; maxeb; proposal; set; solo; stakers; staking; validator cache: ethresear-15801.html plain text: ethresear-15801.txt item: #1163 of 3327 id: ethresear-15820 author: ethresear title: ethresear-15820 date: None words: 1260 flesch: 63 summary: Co-authored by @edmundedgar and @josojo Why its useful to develop forkable stablecoins There are two major benefits to developing and adapting forkable stablecoins: We are curious about your input or other forkable stablecoin designs from the community! keywords: stablecoin; value cache: ethresear-15820.html plain text: ethresear-15820.txt item: #1164 of 3327 id: ethresear-15842 author: ethresear title: ethresear-15842 date: None words: 665 flesch: 57 summary: On an EC2 c6a.32xlarge instance, the proof generation for exponentiation over BN254 required the following execution times: G1 exponentiation: 12s G2 exponentiation: total proof generation time for 6bits each circuits 13s + aggregation 10s = 23s Fq12 exponentiation: total proof generation time for 6bits each circuits 118s + aggregation 20s = 138s Applying SIPP to n pairings requires G1 exponentiation and G2 exponentiation n-1 times each, and Fq12 exponentiation 2 \log_2 n times. Aggregating pairings with SIPP in plonky2 - zk-s[nt]arks - Ethereum Research Ethereum Research Aggregating pairings with SIPP in plonky2 zk-s[nt]arks nuno June 9, 2023, 1:18pm 1 Performing pairings within SNARK circuits opens up a variety of promising applications, including trustless bridges, light clients, and BLS signature aggregation for ERC4337, among others. keywords: verifier cache: ethresear-15842.html plain text: ethresear-15842.txt item: #1165 of 3327 id: ethresear-15856 author: ethresear title: ethresear-15856 date: None words: 2862 flesch: 55 summary: And it provides you with a signer which is able to perform signing of message and transaction using device passkeys. Apple device users can securely back up their passkeys in iCloud Keychain, overcoming this restriction. keywords: apple; device; june; key; passkey; signer; user cache: ethresear-15856.html plain text: ethresear-15856.txt item: #1166 of 3327 id: ethresear-15871 author: ethresear title: ethresear-15871 date: None words: 4258 flesch: 53 summary: This finding suggests that, while finality incidents of the duration observed in this study did affect the peer-to-peer network, causing a temporary increase in missed slots and network congestion, they did not significantly disrupt users’ transaction experience in terms of inclusion time and transaction cost. We identify epochs in which network participation (i.e., the percentage of total staked ETH used to vote) dipped below 66% (see Figure 1). keywords: attestations; finality; incidents; network; nodes; peer; slots; time cache: ethresear-15871.html plain text: ethresear-15871.txt item: #1167 of 3327 id: ethresear-15872 author: ethresear title: ethresear-15872 date: None words: 1787 flesch: 59 summary: We investigate their unique smart contract languages, explore state tree designs, and consider the trade-offs in privacy designs. Therefore, in order to implement the untraceability of privacy transactions, the private state tree can only be append-only, and leaf nodes can not be deleted or updated. keywords: hybrid; ola; privacy; rollup; tree cache: ethresear-15872.html plain text: ethresear-15872.txt item: #1168 of 3327 id: ethresear-15881 author: ethresear title: ethresear-15881 date: None words: 2297 flesch: 55 summary: It also focuses on demonstrating the construction methods for three types of Groth16 transaction malleability attack. If transaction B was included in the Bitcoin ledger by miners before transaction A, subsequent miners packaging transaction keywords: algorithm; equation; groth16; proof; transaction cache: ethresear-15881.html plain text: ethresear-15881.txt item: #1169 of 3327 id: ethresear-15894 author: ethresear title: ethresear-15894 date: None words: 1550 flesch: 50 summary: We can leverage an algorithm similar to Ethereum’s Beacon Chain’s random proposer selection algorithm to randomly choose multiple operators from a cluster of operators that meet certain criteria. Operators cannot slash stakers individually; multiple operators must collaborate. keywords: attack; operators; rai cache: ethresear-15894.html plain text: ethresear-15894.txt item: #1170 of 3327 id: ethresear-15898 author: ethresear title: ethresear-15898 date: None words: 536 flesch: 67 summary: Motivation Why do we need cheap forced transactions? Proposal for Cross RU forced transactions - Sharding - Ethereum Research Ethereum Research Proposal for Cross RU forced transactions Sharding zk-roll-up, cross-shard kelemeno June 16, 2023, 11:27am 1 Introduction Cross-rollup interoperability is a crucial part of scaling. keywords: transactions cache: ethresear-15898.html plain text: ethresear-15898.txt item: #1171 of 3327 id: ethresear-15900 author: ethresear title: ethresear-15900 date: None words: 2931 flesch: 67 summary: Thus, every time the vault fills up with some amount of tokens X_i for block i, the %s of X_i owed to the respective LPs are in direct proportion to the % of liquidity that each LP provided over the pool move in block i. If an LP was providing liquidity outside of the [starting pool price in block i, final pool price in block i] range, that LP doesn’t own/is not owed any of the X_i. TheNonEconomist August 31, 2023, 8:16am 10 The-CTra1n: If an LP was providing liquidity outside of the [starting pool price in block i, final pool price in block i] range, that LP doesn’t own/is not owed any of the Xi. keywords: block; lvr; pool; price; tokens cache: ethresear-15900.html plain text: ethresear-15900.txt item: #1172 of 3327 id: ethresear-15903 author: ethresear title: ethresear-15903 date: None words: 1984 flesch: 58 summary: The gas price suddenly spikes ~30 times and stays there (different claim kinds are affected at different ranges, this assumes the particularly huge claim requiring 10M gas to check). There will be an option to not check adversarial claim kinds. keywords: blesser; blessing; claim cache: ethresear-15903.html plain text: ethresear-15903.txt item: #1173 of 3327 id: ethresear-15923 author: ethresear title: ethresear-15923 date: None words: 632 flesch: 59 summary: Password recovery for Account Abstraction Wallet - Applications - Ethereum Research Ethereum Research Password recovery for Account Abstraction Wallet Applications account-abstraction terry June 20, 2023, 6:49am 1 Password recovery for Account Abstraction Wallet This topic proposes a new approach to password recovery for Account Abstraction Wallets, utilizing ZK-SNARKs (Zero-Knowledge Succinct Non-Interactive Arguments of Knowledge). If hacker try tro submit wrong password, smart contract will revert hacker’s transaction. keywords: password; wallet cache: ethresear-15923.html plain text: ethresear-15923.txt item: #1174 of 3327 id: ethresear-15934 author: ethresear title: ethresear-15934 date: None words: 1693 flesch: 70 summary: Time Bound Token (TBT): Generalized Time Based Claim on utility - Economics - Ethereum Research Ethereum Research Time Bound Token (TBT): Generalized Time Based Claim on utility Economics Timelord.eth June 20, 2023, 6:56pm 1 Time Bound Token Ricsson Ngo @Timelord. Eth ricsson@timeswap.io Shatabarto Bhattacharya @riksucks shatabarto@timeswap.io Abstract Time Bound Token or TBT is a token that makes it possible to transfer and manage ownership of the timeline of an asset, essentially a pure representation of an option. keywords: month; tbt; time; token cache: ethresear-15934.html plain text: ethresear-15934.txt item: #1175 of 3327 id: ethresear-15940 author: ethresear title: ethresear-15940 date: None words: 574 flesch: 47 summary: The constraints around rollup finality as far as I understand are as follows: The challenge period must be AT LEAST as long as the time to finality of L1 in order to avoid censorship/reorg attack/multi-block MEV. tldr If we fragment the state into hashes per-user (or per discrete piece of globally shared state with its own update rules, which might include things like LP or debt positions), we can achieve faster finality than monolithic rollups. keywords: finality; state cache: ethresear-15940.html plain text: ethresear-15940.txt item: #1176 of 3327 id: ethresear-15947 author: ethresear title: ethresear-15947 date: None words: 702 flesch: 58 summary: image899×511 20.7 KB Sequence diagram of third party calling user transaction use new paradigm.(transferFungibleToken). When contract wallets come out, there will be new ways of interacting with assets. keywords: contract; wallet cache: ethresear-15947.html plain text: ethresear-15947.txt item: #1177 of 3327 id: ethresear-15959 author: ethresear title: ethresear-15959 date: None words: 2796 flesch: 58 summary: Abstracts This article addresses the centralization of block builders, which may reduce the user experience and censorship resistance of Ethereum. This rational choice of searchers and competitive environment of builders will cause centralization of block builders. keywords: block; builders; market; searchers; value cache: ethresear-15959.html plain text: ethresear-15959.txt item: #1178 of 3327 id: ethresear-15980 author: ethresear title: ethresear-15980 date: None words: 227 flesch: 49 summary: We like to seek your feedback on this idea on FEM Progressive precompiles via CREATE2 shadowing - EIPs - Fellowship of Ethereum Magicians (Cross-posting here because many precompiles are cryptography related and originated from discussions here) 2 Likes dcposch June 26, 2023, 7:06pm 2 Nice, thanks for posting. We have many important EVM chains now, each of which will ship a precompile (or any EIP) at different times. keywords: precompile cache: ethresear-15980.html plain text: ethresear-15980.txt item: #1179 of 3327 id: ethresear-1599 author: ethresear title: ethresear-1599 date: None words: 552 flesch: 49 summary: Light clients can accept new blocks immediately, rather than having to wait for some delay so that everyone can send their requests at the same time. What’s the security implication of letting miners possibly only release blocks that cause light clients to sample chunks that the miner wants? keywords: block; clients cache: ethresear-1599.html plain text: ethresear-1599.txt item: #1180 of 3327 id: ethresear-16009 author: ethresear title: ethresear-16009 date: None words: 1305 flesch: 46 summary: While some developers have attempted to reduce the impermanent loss (IL) and slippage through concentration techniques or improving the mathematical curves for liquidity pools, another focus is to build DEXes for trading derivatives, synthetic assets, and perpetual futures or options. The third generation 3rd-gen of decentralized exchanges (DEXes) represent advancements on the previous Uniswap model to reduce slippage and increase capital (liquidity) efficiency by concentrating liquidity and swap requests in specific ranges instead of spreading prices on the entire inverse curve. keywords: dexes; exchanges; liquidity; model cache: ethresear-16009.html plain text: ethresear-16009.txt item: #1181 of 3327 id: ethresear-16027 author: ethresear title: ethresear-16027 date: None words: 2014 flesch: 49 summary: There are some good reasons for that: Optimal portfolios are diversified, and diversification, when done in a good way, eliminates risk Users don’t have the capacity to actually choose across tens/hundreds of different restaking services Buy-and-hold (restake-and-hold in our case) is a great strategy for passive investors We can safely assume that having a market-agreed-upon efficient portfolio of restaking services can become very popular by restakers. We can think of each restaking service as a specific asset and the combination of different restaking services as a portfolio. keywords: restaking; services; validators cache: ethresear-16027.html plain text: ethresear-16027.txt item: #1182 of 3327 id: ethresear-16034 author: ethresear title: ethresear-16034 date: None words: 1753 flesch: 53 summary: It is responsible for distributing ZKP proof tasks, receiving task results (ZKP proofs), managing the proofs, and submitting them to the Base Chain to earn rewards. The Proof Sender module handles the on-chain submission of ZKP proofs by submitting them to the zkevm contract deployed on the Base Chain. keywords: chain; proof; zkp cache: ethresear-16034.html plain text: ethresear-16034.txt item: #1183 of 3327 id: ethresear-16054 author: ethresear title: ethresear-16054 date: None words: 3322 flesch: 66 summary: The slot N+1 block could either build on the empty or full block from slot N. Similarly, the PTC cast their votes on full or empty based on the payload-timeliness at t=t3 of the previous slot. Note – In terms of CL engineering, making the transition function able to process empty blocks is important. keywords: block; builder; payload; proposer; slot cache: ethresear-16054.html plain text: ethresear-16054.txt item: #1184 of 3327 id: ethresear-16059 author: ethresear title: ethresear-16059 date: None words: 1212 flesch: 48 summary: You can think of some casino games as trading pairs, and this is also one of GMX’s few complaints from users — fewer trading pairs. This is one of the important reasons for the small number of trading pairs. keywords: defi; gmx; protocol; trading cache: ethresear-16059.html plain text: ethresear-16059.txt item: #1185 of 3327 id: ethresear-16072 author: ethresear title: ethresear-16072 date: None words: 269 flesch: 27 summary: Asymptotic Power Curves3840×2912 382 KB Necessary differences from conventional unique-position perpetual exchanges: payoff function is compound leverage {P\over{M}}^K instead of constant leverage M+K\times(P-M) smooth Auto-Deleverage curve instead of manual ADL cutoff. Construction of Perpetuals AMM Protocol - Decentralized exchanges - Ethereum Research Ethereum Research Construction of Perpetuals AMM Protocol Decentralized exchanges short-selling Zergity July 8, 2023, 2:47pm 1 Following up on this old discussion, we propose a construction of leverage perpetual AMM liquidity pools using an asymptotic power curve pair. keywords: payoff cache: ethresear-16072.html plain text: ethresear-16072.txt item: #1186 of 3327 id: ethresear-16078 author: ethresear title: ethresear-16078 date: None words: 75 flesch: 36 summary: If you have a DAG of transaction this post will explain how to verify that the claim of parallel execution is correct: Parallel EVM claim | draganrakita 2 Likes Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled Parallel EVM claim - Execution Layer Research - Ethereum Research Ethereum Research Parallel EVM claim Execution Layer Research draganrakita July 9, 2023, 7:42pm 1 Wrote something that could be of interest. keywords: research cache: ethresear-16078.html plain text: ethresear-16078.txt item: #1187 of 3327 id: ethresear-16081 author: ethresear title: ethresear-16081 date: None words: 2505 flesch: 57 summary: Exploiting this, manipulating validators could be assigned more slots for proposing blocks than usual, earning more rewards and increasing their influence over the network. The goal is to get more slots allocated in the next but one epoch. keywords: end; epoch; randao; slots cache: ethresear-16081.html plain text: ethresear-16081.txt item: #1188 of 3327 id: ethresear-16115 author: ethresear title: ethresear-16115 date: None words: 3170 flesch: 42 summary: Looking forward, we plan to pursue optimizations, collaborations and real-world deployment to bring maze witness encryption from theory into practice. Usability analysis - How can we create intuitive and accessible user interfaces for maze witness encryption? Applications - What promising use cases can be implemented and evaluated with stakeholders? keywords: coloring; encryption; generation; graph; knowledge; maze; proof; security; witness cache: ethresear-16115.html plain text: ethresear-16115.txt item: #1189 of 3327 id: ethresear-16121 author: ethresear title: ethresear-16121 date: None words: 1165 flesch: 68 summary: 2 Likes michaelscurry July 27, 2023, 9:27pm 12 Sorry Max, not to hijack your proposal but I raised a similar one here: Priority fee should be burned for reverted transactions - #3 by michaelscurry Wonder if that would help with the use case you mentioned here. I’m suggesting that the priority fee should be burned instead of given to validators for reverted transactions. keywords: july; transactions cache: ethresear-16121.html plain text: ethresear-16121.txt item: #1190 of 3327 id: ethresear-16150 author: ethresear title: ethresear-16150 date: None words: 85 flesch: 43 summary: Cryptography haael July 20, 2023, 12:59pm 1 I’m looking for someone with good knowledge of algebra to implement the algorithm described here: https://www-polsys.lip6.fr/~jcf/Papers/jsc_FP09.pdf The goal is to represent a circuit as a composition of quadratic circuits. Somebody wants to help me implement polynomial decomposition algorithm? keywords: algorithm cache: ethresear-16150.html plain text: ethresear-16150.txt item: #1191 of 3327 id: ethresear-16156 author: ethresear title: ethresear-16156 date: None words: 377 flesch: 44 summary: zkMIPS includes a VM capable of executing MIPS programs and interacting with the execution environment, demonstrating its compatibility with diverse platforms. zkMIPS converts the Ethereum Geth into MIPS instruction set and executes the generated program using its VM. Proof Generation zkMIPS generates a ZK proof for the resulted execution trace using the state-of-art mechanisms including Starky and Plonky2. keywords: proof; zkmips cache: ethresear-16156.html plain text: ethresear-16156.txt item: #1192 of 3327 id: ethresear-16162 author: ethresear title: ethresear-16162 date: None words: 757 flesch: 53 summary: On the client side, the outgoing transactions’ balance reduction and incoming transactions’ balance increase get proven using ZKP. The recipient uses ZKP to merge incoming transactions into their balance. keywords: block; transactions cache: ethresear-16162.html plain text: ethresear-16162.txt item: #1193 of 3327 id: ethresear-16169 author: ethresear title: ethresear-16169 date: None words: 483 flesch: 39 summary: Almost Instant Interactive Fraud Proof using Multi-Sect on DA BLOBs and multi-step ZK verifier - Sharding - Ethereum Research Ethereum Research Almost Instant Interactive Fraud Proof using Multi-Sect on DA BLOBs and multi-step ZK verifier Sharding qizhou July 24, 2023, 6:42am 1 Many thanks @Canhui. Therefore, a single interaction will reduce 4096x fold computational steps in challenge. keywords: multi; step cache: ethresear-16169.html plain text: ethresear-16169.txt item: #1194 of 3327 id: ethresear-16182 author: ethresear title: ethresear-16182 date: None words: 1897 flesch: 47 summary: Solvers can have an extra step to validate if they can actually solve those intent or not, this will enable the decentralized network of intents to have more types of solvers, like swap, bridge, loan, social solvers and more Also would like to point out, Intents should have various representation format, it can be UI, Natural language, Form etc 2 Likes nlok5923 July 26, 2023, 4:32am 4 Amazing proposal @Arch0125 Few pointers i had The current LLM systems work with the data they are already trained upon. I agree with @nlok5923 that the decoding of Intents must be done at the node level, but here is the problem with that approach - Solvers will be domain-specific, i.e., solvers who are actually solving DeFi intents or solvers who are only dealing with intents for social networks (Follow all those people who are NFT Degens ). keywords: intent; llm; transaction; user cache: ethresear-16182.html plain text: ethresear-16182.txt item: #1195 of 3327 id: ethresear-16184 author: ethresear title: ethresear-16184 date: None words: 684 flesch: 51 summary: Privatizing the Volume and Timing of Ethereum Transactions - Privacy - Ethereum Research Ethereum Research Privatizing the Volume and Timing of Ethereum Transactions Privacy trevormil July 25, 2023, 8:01pm 1 In this post, I share my paper VTBC on privatizing the volume and timing of blockchain transactions (with an implementation using Ethereum). Currently, the public volume and timing metadata can be used to deduce information about the students’ grades, even if all submissions are anonymous and confidential. keywords: transactions; volume cache: ethresear-16184.html plain text: ethresear-16184.txt item: #1196 of 3327 id: ethresear-16186 author: ethresear title: ethresear-16186 date: None words: 469 flesch: 57 summary: Currently, gas fees for reverted transactions are distributed in the same way as regular transactions. Priority fee should be burned for reverted transactions - Economics - Ethereum Research Ethereum Research Priority fee should be burned for reverted transactions Economics michaelscurry July 25, 2023, 11:49pm 1 Problem: keywords: fee cache: ethresear-16186.html plain text: ethresear-16186.txt item: #1197 of 3327 id: ethresear-16194 author: ethresear title: ethresear-16194 date: None words: 1088 flesch: 47 summary: First of all, State-holding nodes play a critical role in witness generation, generating witnesses that encapsulate the zk proofs of the latest state correctness. To enhance witness generation efficiency, I’d advocate the utilization of aggregated sub-vector commitment. keywords: state; stateless; witness cache: ethresear-16194.html plain text: ethresear-16194.txt item: #1198 of 3327 id: ethresear-16199 author: ethresear title: ethresear-16199 date: None words: 2108 flesch: 64 summary: User links differenet wallet instances on different chains to the keystore. Definition A smart contract account is considered cross-chain unified if it satisfies the following properties: You can have multiple wallet instances on different chains with the same address. keywords: account; chain; salt; wallet cache: ethresear-16199.html plain text: ethresear-16199.txt item: #1199 of 3327 id: ethresear-16206 author: ethresear title: ethresear-16206 date: None words: 3376 flesch: 51 summary: Players adjust their bids based on the observed behavior of other players. Players only bid their public values 𝑃(𝑡), and only reveal their accumulated private value 𝐸i(𝑡) at the last second, hoping to time the moment at which their reveal their private value right before the proposer chooses the winning bid, so other players with adaptive bidding strategies don’t have time to react. keywords: bid; block; mev; players; strategy; time cache: ethresear-16206.html plain text: ethresear-16206.txt item: #1200 of 3327 id: ethresear-16213 author: ethresear title: ethresear-16213 date: None words: 2954 flesch: 60 summary: Alice encrypts the secret key sk_1 using Bob’s FHE public key PK_b, resulting in the ciphertext C_1. This scheme only requires the additive homomorphism, however, we build this under FHE scheme such as BGV, BFV. keywords: address; dksap; encryption; ethereum; fhe; key; public cache: ethresear-16213.html plain text: ethresear-16213.txt item: #1201 of 3327 id: ethresear-16234 author: ethresear title: ethresear-16234 date: None words: 2636 flesch: 48 summary: OPML vs ZKML OPML ZKML model size any size (available for extremely large model) small/limited (due to the cost of ZKP generation) validity proof fraud proof zero-knowledge proof (ZKP) training support* √ × requirement Any PC with CPU/GPU Large memory for ZK circuit Finality Delay for challenge period No delays service cost low (inference and training can be conducted in native environment) extremely high (generating a ZKP for ML inference is extremely high) security crypto-economic incentives for security cryptographic security *: Within the current OPML framework, our primary focus lies on the inference of ML models, allowing for efficient and secure model computations. This harmonization of techniques enables us to overcome the inherent challenges posed by floating-point variations and platform disparities, ultimately enhancing the integrity and dependability of OPML computations. keywords: computation; model; opml; phase; verification cache: ethresear-16234.html plain text: ethresear-16234.txt item: #1202 of 3327 id: ethresear-16256 author: ethresear title: ethresear-16256 date: None words: 1561 flesch: 65 summary: Specifically, it uses 2D data availability sampling, where data is arranged into a grid, taken as representing evaluations of a two-dimensional low-degree polynomial P(X, Y), and is extended both horizontally and vertically. Ethereum plans to use data availability sampling to expand the amount of data space available to rollups. keywords: availability; data cache: ethresear-16256.html plain text: ethresear-16256.txt item: #1203 of 3327 id: ethresear-16267 author: ethresear title: ethresear-16267 date: None words: 3397 flesch: 57 summary: We will get to this option in the next dichotomy Home stakers building vs Builders heavily staked We have already argued that every proposal for ePBS has staked builders, the question is for how much? In the current status of the Ethereum network, builders are a reduced group of entities that are not controlled by the protocol, they are not staked in any way and may act in an anonymous manner. keywords: blocks; builders; epbs; payload; validators cache: ethresear-16267.html plain text: ethresear-16267.txt item: #1204 of 3327 id: ethresear-16278 author: ethresear title: ethresear-16278 date: None words: 7061 flesch: 58 summary: Block validity enforcement – Relays check builder blocks for validity. For (i) we can use the Payload-Timeliness Committee (abbr. PTC) to enforce that builder blocks are included if they are made available on time (though other designs like Two-slot and PEPC are also possible). keywords: bid; block; builder; epbs; mev; payment; proposer; protocol; relay cache: ethresear-16278.html plain text: ethresear-16278.txt item: #1205 of 3327 id: ethresear-16297 author: ethresear title: ethresear-16297 date: None words: 1403 flesch: 60 summary: The second component is the generation of burner accounts. private-accounts (1)802×503 29.8 KB The above diagram shows the flow of generating burner accounts. keywords: accounts; burner; user cache: ethresear-16297.html plain text: ethresear-16297.txt item: #1206 of 3327 id: ethresear-16299 author: ethresear title: ethresear-16299 date: None words: 823 flesch: 49 summary: # Issue 1: introducing new Entity for Stateless AA, trustless State provider #1 this entity consists of Ethereum light clients providing the latest state, peer-to-peer network and ZK circuit. A lightweight client verifies proofs and validates state data from the state provider. keywords: state; stateless cache: ethresear-16299.html plain text: ethresear-16299.txt item: #1207 of 3327 id: ethresear-16319 author: ethresear title: ethresear-16319 date: None words: 1537 flesch: 8 summary: Some disadvantages of this issue with regard to CoWs Somebody can front-run your claim transaction using the already publically available private key Increased gas fees for setting up HTLC and then claiming the tokens The token settlement will become complicated if CoWs are matched between ≥ 2 orders AMBs or Oracle based solution We can Arbitrary Message Passing Bridges (AMBs) to send cross-chain messages across blockchains to lock and unlock tokens. Cross Chain CoWSwap - Decentralized exchanges - Ethereum Research Ethereum Research Cross Chain CoWSwap Decentralized exchanges sk1122 August 9, 2023, 9:55pm 1 TLDR; Usage of coincidences of wants in cross-chain transfers might help reduce gas fees and wait time Background We are building Fetcch, we have an inbuilt cross-chain settlement layer that works based on stablecoin liquidity pools and DEX aggregators that enables any token to any token transfers across multiple blockchains. keywords: chain; tokens; user cache: ethresear-16319.html plain text: ethresear-16319.txt item: #1208 of 3327 id: ethresear-16327 author: ethresear title: ethresear-16327 date: None words: 3583 flesch: 51 summary: Builder bids are updated throughout the duration of a slot (i.e., 12 seconds), and typically increase over time as block value is derived from priority fees and Maximal Extractable Value (MEV) (e.g., arbitrages, sandwiches, liquidations, cross-domain MEV) associated with pending user transactions. Arbitrageurs will want to cancel their trade, and this can be achieved if bid cancellations are enabled (builder bids are lowered to reflect trade cancellations by searchers/arbitrageurs). keywords: bid; builder; cex; count; mev; transactions; value cache: ethresear-16327.html plain text: ethresear-16327.txt item: #1209 of 3327 id: ethresear-16333 author: ethresear title: ethresear-16333 date: None words: 2124 flesch: 63 summary: Missed slots ! Reorgs: depth occasions example slot(s) example epoch 1 1406 7060699, 7065797, 7070304 220947, 220806 2 4 5920525, 6366357, 6436520 201141, 198948 Looking at missed slots and reorgs together, we had 323 occasions of consecutive slots with missed/reorged slots/blocks of depth 2. keywords: epoch; odds; slot cache: ethresear-16333.html plain text: ethresear-16333.txt item: #1210 of 3327 id: ethresear-16334 author: ethresear title: ethresear-16334 date: None words: 2568 flesch: 65 summary: Users can forcibly acquire ownership proofs from the operator on-chain. We achieve this by giving users ownership proofs, which can be used to recover funds in a shutdown procedure in case the operator stops updating the state and the state can’t be recovered. keywords: chain; coins; operator; state cache: ethresear-16334.html plain text: ethresear-16334.txt item: #1211 of 3327 id: ethresear-16370 author: ethresear title: ethresear-16370 date: None words: 2001 flesch: 60 summary: One way they might work is that cross chain transactions will have to go through a shared sequencer (splitting L3s into interoperable clusters). Cross chain transactions would work with L2s that share the same sequencer(s). keywords: chain; data cache: ethresear-16370.html plain text: ethresear-16370.txt item: #1212 of 3327 id: ethresear-16375 author: ethresear title: ethresear-16375 date: None words: 883 flesch: 59 summary: Moreover, the Prover will be doing lots of extra computations to make sure that 1) this proof Z is short, and 2) that verification of the correctness of Z is a very efficient algorithm, meaning that even a Verifier with few resources can easily perform this check. To avoid this scenario, the Verifier and Prover agree to add a verification to the outsourced computation. keywords: computation; prover cache: ethresear-16375.html plain text: ethresear-16375.txt item: #1213 of 3327 id: ethresear-16384 author: ethresear title: ethresear-16384 date: None words: 1363 flesch: 61 summary: In the analysis of a two-party protocol, there are three cases to be considered: Case A: what happens if both the Prover and Verifier are honest? Case B: what happens if the Verifier is honest but the Prover isn’t? Case C: what happens if the Prover is honest but the Verifier isn’t? keywords: case; prover; verifier cache: ethresear-16384.html plain text: ethresear-16384.txt item: #1214 of 3327 id: ethresear-16387 author: ethresear title: ethresear-16387 date: None words: 1029 flesch: 44 summary: Dexaran August 15, 2023, 1:43am 11 And other posts are not getting approved for days Reddit - Dive into anything https://www.reddit.com/r/ethereum/comments/15llp7p/i_want_to_raise_the_issue_of_censorship_on/ p_m August 16, 2023, 1:05am 12 tl;dr: OP points to the fact that it’s possible to send erc20 tokens to token contract address. 1 Like Dexaran August 16, 2023, 1:34am 13 No, OP points to the fact that ERC-20 standard is designed in a way that violates secure software design practices which resulted in (1) impossibility of handling transactions and (2) the implementation of pull transacting method which is not suitable for decentralized trustless assets and must be avoided. Security concerns regarding token standards and $130M worth of ERC20 tokens loss on Ethereum mainnet - Security - Ethereum Research Ethereum Research Security concerns regarding token standards and $130M worth of ERC20 tokens loss on Ethereum mainnet Security Dexaran August 15, 2023, 1:33am 1 I would like to invite researchers to investigate the problem of Ethereum token standards and most notably ERC-20. keywords: august; erc-20; ethereum cache: ethresear-16387.html plain text: ethresear-16387.txt item: #1215 of 3327 id: ethresear-16389 author: ethresear title: ethresear-16389 date: None words: 4819 flesch: 67 summary: The naïve solution is to place the IL into the block body for slot n, allowing slot n+1 attesters can use the data as part of their state-transition function. By signing over the list of (address, gasLimit) pairs, the proposer is saying: “I commit that during slot n or slot n+1, a transaction from address will be included as long as the remaining gas in the slot n+1 payload is less than gasLimit.” keywords: block; proposer; slot; slot n+1; summary cache: ethresear-16389.html plain text: ethresear-16389.txt item: #1216 of 3327 id: ethresear-16403 author: ethresear title: ethresear-16403 date: None words: 843 flesch: 66 summary: The number of BUSDTs in circulation will be equal with burnt USDTs and no one can find out the burners of those USDTs (Unless their reveal their secret t). We can generate unspendable public-keys by generating random points on the curve. keywords: key; public cache: ethresear-16403.html plain text: ethresear-16403.txt item: #1217 of 3327 id: ethresear-16411 author: ethresear title: ethresear-16411 date: None words: 757 flesch: 45 summary: Coinbase calls for onchain Reputation Recently, Coinbase calls onchain Reputation builders for its Base Ecosystem Fund. The Base’s request for builders claims that “decentralized identity and reputation will play a critical role in defining each individual’s onchain persona, and reputation protocols (like Google Pagerank type) should natively support onchain entities to build trust onchain, while preserving user privacy and autonomy.” Octan Solution Inspired by Google PageRank, Octan Network has researched onchain reputation problem since 2019 with two scientific research papers published on globally-recognized academic journals. keywords: octan; reputation; web3 cache: ethresear-16411.html plain text: ethresear-16411.txt item: #1218 of 3327 id: ethresear-16429 author: ethresear title: ethresear-16429 date: None words: 2264 flesch: 54 summary: Super-finality uses votes (a.k.a. ‘attestations’ in Ethereum) cast by validators as part of Ethereum’s Casper component, and confirms blocks as follows: Super-finality rule (see Figure 3): Super-finalize block A (and its ancestors) iff: (1) we see a block B whose state commits to A (or a descendant of A) as the finalized checkpoint, and (2) we see votes in favor of B (i.e., FFG votes with target B or a descendant of B) from validators totalling q fraction of stake (for instance, q=90\%). The cost of super-finalizing blocks with a high quorum (e.g., q=90\%) is that if validators with 1-q = 10\% of the total stake go offline, then no block receives q = 90\% votes, so no block gets super-finalized, i.e., the client loses liveness. keywords: block; finality; safety; super cache: ethresear-16429.html plain text: ethresear-16429.txt item: #1219 of 3327 id: ethresear-16441 author: ethresear title: ethresear-16441 date: None words: 1159 flesch: 49 summary: It’s important to note that the RRC contract solely provides data retrieval services and does not directly interact with cross-chain assets. The underlying reality is that cross-chain assets undergo two bridging operations on L1, creating a seamless connection from Rollup1 to Rollup2 in the user’s perception. keywords: bridge; rollup cache: ethresear-16441.html plain text: ethresear-16441.txt item: #1220 of 3327 id: ethresear-16448 author: ethresear title: ethresear-16448 date: None words: 1064 flesch: 69 summary: The basic idea behind Jolt+Lasso is to verify an execution trace by using table lookups. It presents an abstract but equivalent model of a CPU, and proves that each instruction of its Instruction Set Architecture (ISA) can be implemented using table lookups, assuming the existence of gigatables. keywords: instruction; jolt; table cache: ethresear-16448.html plain text: ethresear-16448.txt item: #1221 of 3327 id: ethresear-16454 author: ethresear title: ethresear-16454 date: None words: 2235 flesch: 57 summary: Here is the tradeoff space when designing a membership proof using Merkle trees: Positive: No need for trusted setup Positive: Simple to understand Negative: Relies on SNARK-friendly hash functions like Poseidon Negative: Slower proof creation Below we describe the proof of validator protocol based on Merkle trees: Proof-of-validator protocol using Merkle trees Every validator i registers a value p_i on the blockchain, such that p_i = Hash(s_i). In this post, we introduce a proof of validator protocol, which enables DHT participants to demonstrate, in zero-knowledge, that they are an Ethereum validator. keywords: dht; node; proof; protocol; validator cache: ethresear-16454.html plain text: ethresear-16454.txt item: #1222 of 3327 id: ethresear-16456 author: ethresear title: ethresear-16456 date: None words: 1582 flesch: 51 summary: Conditions User’s intent will be a dictionary Pre conditions this should be true before solver tries solving the intent for example - i want to swap 100 ETH only if price of ETH > 100$ and fees should be lowest here, want to swap 100 ETH & fees should be lowest is condition and ETH > 100$ is pre condition will be a dict Conditions are checked at runtime while solving the intent and Pre conditions are checked before even solving the intent Intents will be a very open ended structure, so we can’t really encapsulate every type of intent in a single structure, so we will have to go multi-structure with conditions and pre-conditions We will have types of intents like swap- , it can define its own types of conditions and pre-conditions, something like this SCENARIO --> A user who wants to swap 100 MATIC (POL) -> USDC (ETH), only wants slippage up to 1% and should at least receive 100 USDC for 100 MATIC, current price 1 MATIC -> 0.99 USDC CONDITIONS --> amountIn - 100 tokenIn - MATIC (POL) tokenOut - USDC (ETH) slippage - 1% PRE-CONDITIONS --> usdcPrice - >= 1 MATIC maticPrice - >= 1 USDC TYPE: swap- Miscellaneous sk1122 August 23, 2023, 7:28pm 1 tldr; intents are hot right now, but no one has idea what it is and how to decentralize it, we will focus on that proposed-intent-mempool1720×1057 79.5 KB What are Intents? keywords: conditions; intents cache: ethresear-16456.html plain text: ethresear-16456.txt item: #1223 of 3327 id: ethresear-16480 author: ethresear title: ethresear-16480 date: None words: 1644 flesch: 45 summary: This addresses challenges in accessing state data for tasks like gas estimation and enhances lightweight client efficiency. Stateless clients lack state data for actions beyond transitioning. keywords: clients; contract; data; state cache: ethresear-16480.html plain text: ethresear-16480.txt item: #1224 of 3327 id: ethresear-16483 author: ethresear title: ethresear-16483 date: None words: 692 flesch: 57 summary: Implementation overview Of partial state caching mechanism: - Execution Layer Research - Ethereum Research Ethereum Research Implementation overview Of partial state caching mechanism: Execution Layer Research stateless sogolmalek August 26, 2023, 8:26am 1 Linking to my previous proposal, Ive inititated an implementation idea for this component. Cache Data Structure: Implement a Hash Map and Linked List combination: Use a hash map to store cached entries. keywords: cache; list cache: ethresear-16483.html plain text: ethresear-16483.txt item: #1225 of 3327 id: ethresear-16492 author: ethresear title: ethresear-16492 date: None words: 1303 flesch: 47 summary: The ZK/OP Debate in RaaS: Why ZK-RaaS Takes the Lead - Layer 2 - Ethereum Research Ethereum Research The ZK/OP Debate in RaaS: Why ZK-RaaS Takes the Lead Layer 2 zk-roll-up nanfengpo August 28, 2023, 9:40am 1 TL; DR Compared to Optimistic Rollups, ZK-Rollups offer the following advantages: Compressed transaction data results in lower L1 gas costs. Cost ZK-Rollups have lower L1 Gas costs compared to Optimistic Rollups. keywords: raas; rollups; transaction cache: ethresear-16492.html plain text: ethresear-16492.txt item: #1226 of 3327 id: ethresear-16493 author: ethresear title: ethresear-16493 date: None words: 519 flesch: 46 summary: However, as pointed out, state deletions can complicate matters, making it difficult to recreate the entire post-block trie structure and verify state changes against the state root in the block header. ZK proofs of the last state can indeed help address the challenge mentioned. keywords: changes; state cache: ethresear-16493.html plain text: ethresear-16493.txt item: #1227 of 3327 id: ethresear-16509 author: ethresear title: ethresear-16509 date: None words: 2399 flesch: 41 summary: However, validator penalties need not exhibit the same dynamics. Penalties are computed today based on slashing the entire balance of all validators participating in an attack involving 1/3+ of the stake and preventing the strategic use of intentional slashing to avoid incurring inactivity penalties. keywords: balance; eth; penalty; validator cache: ethresear-16509.html plain text: ethresear-16509.txt item: #1228 of 3327 id: ethresear-16512 author: ethresear title: ethresear-16512 date: None words: 533 flesch: 50 summary: We believe Saga Ethlets combine the best qualities from every scaling solution into an easy-to-use product Saga Ethlets are the most affordable solution compared to alternative scaling strategies Fraud proofs are only generated and run optimistically, enabling lower costs and speedups Self-contained DA — do not need to pay Ethereum for DA State commitments to Ethereum only happen once per epoch Ethlets feature commodity pricing through our Chainlet auction mechanism Saga Ethlets have the best security tradeoffs Prior to the challenge period, there is still significant economic security with Saga staked After the challenge period, the Ethlet inherits full Ethereum security Most secure because it does not rely on single sequencers No need for external auditors — Due to PoS, there is always an automatic set of auditors (other validators) who verify state hashes Saga Ethlets have instant finality and therefore fast bridging. Finally, Saga Ethlets are incredibly easy to provision with one-click deployment. keywords: ethlets; saga cache: ethresear-16512.html plain text: ethresear-16512.txt item: #1229 of 3327 id: ethresear-16514 author: ethresear title: ethresear-16514 date: None words: 4939 flesch: 57 summary: Creating Commitments: Allows any EVM address to make new commitments. tl;dr: I introduce a novel mechanism for enforcing proposer commitments in Ethereum without altering the existing consensus protocol. keywords: block; commitments; dvt; nodes; pepc; protocol; signature; validator cache: ethresear-16514.html plain text: ethresear-16514.txt item: #1230 of 3327 id: ethresear-16520 author: ethresear title: ethresear-16520 date: None words: 4879 flesch: 68 summary: This can be confirmed by looking at the slots of the past month (2023-08-01 - 2023-08-28): Lido had around 31% market share and the observed likelihood of consecutive slots of 9.5%.Assuming we have censored txs in every block and every honest validator puts them on their IL then 9.5% of the slots could have an empty ILs, potentially opening up the market for censoring builders. If censoring builders continue their operations but shift their focus to slots lacking sanctioned content in the IL, entities with consecutive slots could gain an economic advantage. keywords: block; builders; ils; proposer; slots cache: ethresear-16520.html plain text: ethresear-16520.txt item: #1231 of 3327 id: ethresear-16523 author: ethresear title: ethresear-16523 date: None words: 2493 flesch: 49 summary: Background: Large staking-as-a-service providers control a large portion of Ethereum validators. If LSTs have a structural requirement to distribute stake across dozen(s) of validators, does that mitigate the need to give extra rewards to larger validators to produce the desired incentives? keywords: attestation; ethereum; rewards; validators cache: ethresear-16523.html plain text: ethresear-16523.txt item: #1232 of 3327 id: ethresear-16533 author: ethresear title: ethresear-16533 date: None words: 2252 flesch: 67 summary: How it works: Sequencers can join the sequencer queue in the rollup hub by committing to a financial bond (similarly to current rollup systems). With all this in mind, I came up with a design that involves a rollup hub and a variable number of child rollups. keywords: contract; hub; rollup; system cache: ethresear-16533.html plain text: ethresear-16533.txt item: #1233 of 3327 id: ethresear-16541 author: ethresear title: ethresear-16541 date: None words: 2619 flesch: 56 summary: Simulations of effectiveness of such a solution involve parametrizing the following: data size (number of rows and columns per block, as well as sample size) total number of number of nodes on the network minimum amount of work an honest node is expected to do (e.g. custody and serve samples from X rows and columns) the distribution of node capacities (i.e. what fraction of the network is minimally honest (custodies/serves X) and beyond (e.g. custodies/serves 10%, 25%, 100% of network data)) and the max sample requests they are willing to support (i.e. Y samples per slot) honest/byzantine ratio assumptions Different parametrizations of the above will lead to either acceptable or broken configurations (e.g. data size might be too large to find peers of enough capacity for a given network distributions). [special case of high capacity node] The difference between DAS solutions then becomes – how does the DAS network organize itself, how do you discover peers for sampling, how does the network utilize (or under-utilize) nodes of higher capacity (e.g. can the solution support lumpiness in node capacity or do all nodes look equal). keywords: columns; data; node; rows; samples cache: ethresear-16541.html plain text: ethresear-16541.txt item: #1234 of 3327 id: ethresear-16550 author: ethresear title: ethresear-16550 date: None words: 939 flesch: 53 summary: Same problem 7 Likes sui414 September 6, 2023, 7:20am 2 Adding some data investigation here on the imposter behavior (as time of Sep 5 evening PT): There are multiple builder pubkey appeared as imposters: 1 for flashbots, 10 for Titan (not including 0xabf1ad5e in titan’s list active June-Aug is team’s testing instance - confirmed by their team) image2968×926 328 KB 1 builder pubkey appeared in both cases that is not known/controlled by the team - is the default pubkey lots of new builder instances accidentally use - which shall be ruled out from the imposter concern: 0xaa1488eae4b06a1fff840a2b6db167afc520758dc2c8af0dfb57037954df3431b747e2f900fe8805f05d635e9a29717b. (split reply into multiple because of new user embedding media limits > <) 4 Likes sui414 September 6, 2023, 7:20am 3 image1920×922 150 KB All of them have same activation timeframe around past few days - started the imposter behavior since Sep2 w/ flashbots’ ExtraData, then stopped w/ flashbots and started Titan on Sep5; this seems to be an indicator that the imposters behind the 2 cases are likely same entity. Tracking ALL the historical blocks those builder pubkeys produced, all of them are new (i.e. no historical blocks in other timeframe) except the default pubkey - which reasonably has a history of produced blocks with ALL kinds of builder extraData signature in the past. keywords: builder; imposter; titan cache: ethresear-16550.html plain text: ethresear-16550.txt item: #1235 of 3327 id: ethresear-16557 author: ethresear title: ethresear-16557 date: None words: 3740 flesch: 56 summary: In a PBS setting, censoring proposers solely connect to censoring builders. Spot ILs are made by honest proposers, but they do not increase censorship-resistance since honest proposers do not connect to censoring builders anyways. keywords: block; builder; list; proposer; transactions cache: ethresear-16557.html plain text: ethresear-16557.txt item: #1236 of 3327 id: ethresear-16570 author: ethresear title: ethresear-16570 date: None words: 1126 flesch: 73 summary: Forced transactions can be batched in the same way that l2 transactions are batched. With plasma Free all users need to come online once per forced transaction window (E.g. 1 week) in the case of an attack so that they can exit. keywords: plasma; transaction; users cache: ethresear-16570.html plain text: ethresear-16570.txt item: #1237 of 3327 id: ethresear-16591 author: ethresear title: ethresear-16591 date: None words: 1831 flesch: 45 summary: Liveness of justifications: If slots n,n+1 have honest proposers, then block B proposed at slot n is strongly confirmed in slot n+1 and justified in slot n+2 Proof: As in the previous proof, B receives all honest votes at slot n, which form a 2/3-quorum. In particular, we have the following after \max(GST, GAT), i.e., at a point when all honest validators are always online and the network is always synchronous: Reorg-resilience: a block proposed by an honest proposer never leaves the canonical chain Proof: Say B is proposed by an honest proposer at slot n. All honest validators at slot n vote for B, and moreover they all make the same FFG vote C_1 \to C_2, where checkpoint C_2 = (A, n), for A the highest confirmed block, which is canonical and thus an ancestor of B. Therefore, C_2 is justified, and in particular becomes the latest justified. keywords: confirmation; slot cache: ethresear-16591.html plain text: ethresear-16591.txt item: #1238 of 3327 id: ethresear-16608 author: ethresear title: ethresear-16608 date: None words: 7937 flesch: 53 summary: While drivers facilitate the routing of client-originated ATOs to their designated solvers, a vital consideration arises in the design of solver networks. Solver networks mitigate this concern by fostering an environment where multiple solvers contribute their expertise, enabling diverse approaches to be explored and the most effective solutions to be identified. keywords: approach; ato; atos; client; driver; execution; intent; network; operation; solution; solver; user cache: ethresear-16608.html plain text: ethresear-16608.txt item: #1239 of 3327 id: ethresear-16665 author: ethresear title: ethresear-16665 date: None words: 841 flesch: 58 summary: Zero knowledge rollup where transactions are converted to zkp prior block inclusion - Layer 2 - Ethereum Research Ethereum Research Zero knowledge rollup where transactions are converted to zkp prior block inclusion Layer 2 RecursivelyLabs September 18, 2023, 8:52am 1 Recusively Labs is working on a zero knowledge rollup, where transactions are converted to zkp prior block inclusion. If proofs are created prior block inclusion, but after the mempool then actually there is transactions batching after the mempool to the zero-knowledge-proof system and then “subblocks which are batched transactions transformed in zero-knowledge-proof” to the block. keywords: block; knowledge cache: ethresear-16665.html plain text: ethresear-16665.txt item: #1240 of 3327 id: ethresear-16666 author: ethresear title: ethresear-16666 date: None words: 7691 flesch: 57 summary: Great works like PEPC - Protocol-Enforced Proposer Commitments or Eigenlayer’s restaking model for preserving block proposer agency - explore other ways of augmenting proposer ability to define its needs on the proposer-builder scope. As much as the Block Negotiation Layer encourages Curator competitiveness through a ‘highest bid reward’ - it also motivates the development of different block building and block submission solutions, over varying Curator codebases. keywords: block; builders; building; curator; ecosystem; intent; layer; mev; network; proposer; relays cache: ethresear-16666.html plain text: ethresear-16666.txt item: #1241 of 3327 id: ethresear-16670 author: ethresear title: ethresear-16670 date: None words: 830 flesch: 44 summary: Statement regarding the public report on the analysis of MinRoot - Cryptography - Ethereum Research Ethereum Research Statement regarding the public report on the analysis of MinRoot Cryptography mmaller September 18, 2023, 3:24pm 1 Ethereum Foundation, Cryptography Research Team: Gottfried Herold, George Kadianakis, Dmitry Khovratovich, Mary Maller, Mark Simkin, Antonio Sanso, Arantxa Zapico, Zhenfei Zhang Analysis of MinRoot report: https://crypto.ethereum.org/events/minrootanalysis2023.pdf Ethereum has an efficient and straightforward randomness beacon known as RANDAO. Indeed, MinRoot was considered secure based on the assumption that classical attacks developed for hash functions and encryption schemes were appropriate to evaluate the security of VDFs as well. keywords: attack; minroot; vdfs cache: ethresear-16670.html plain text: ethresear-16670.txt item: #1242 of 3327 id: ethresear-16677 author: ethresear title: ethresear-16677 date: None words: 981 flesch: 45 summary: My observation surrounding this is that Ethereum can be used to serve as a robust base layer to validate and hold the state of several Layer 2s, as the Layer 2s inherit the decentralisation and security of Ethereum as they do not have consensus methods themselves. Does this then not mimic a Tornado Cash 2.0 situation as the deposit and withdrawal to/from the Layer 2 being public, but any transfer or interaction on Layer 2 being opaque, therefore lending itself to migration of illicit funds from a dirty wallet to a clean wallet on Layer 2. keywords: data; layer cache: ethresear-16677.html plain text: ethresear-16677.txt item: #1243 of 3327 id: ethresear-16678 author: ethresear title: ethresear-16678 date: None words: 1390 flesch: 54 summary: Naive Whisk implementation using the target group Alice commits to a random long-term secret k using a tuple (g_T^r,g_T^{kr}) (called tracker). We believe that translating Whisk into the XTR setting is a simple exercise, while more caution needs to be applied to Curdleproof. keywords: group; tracker; whisk; xtr cache: ethresear-16678.html plain text: ethresear-16678.txt item: #1244 of 3327 id: ethresear-16687 author: ethresear title: ethresear-16687 date: None words: 873 flesch: 64 summary: The protocol has the following properties: if somebody steals coins or steals ETH, swapped to coins, the coins will be publically marked as dirty and no honest actors will interact with them balances, addresses, and coin IDs inside the wallets and transaction graph are hidden from the public We assume parties of the transaction as known to each other, so, knowing the list of coin IDs of the sender will not deanonimize him more for the receiver if the user wants to deposit or withdraw some coins, the user will buy or sell them on the exchange, so, only the seller or buyer will know the user’s identity anybody can mint and liquidate new coins, but it is not applicable for mixing because the coin IDs are public on deposits and withdrawals. From another side, pretty private solutions attract bad actors, because they can hide their illegal activity. keywords: actors; privacy cache: ethresear-16687.html plain text: ethresear-16687.txt item: #1245 of 3327 id: ethresear-16692 author: ethresear title: ethresear-16692 date: None words: 1548 flesch: 59 summary: Making PEPC-DVT private Leveraging BLS multi-signatures, we can integrate blind signatures into PEPC-DVT. 🛡️ Making PEPC-DVT private with BLS Blinded Multi-Signatures - Cryptography - Ethereum Research Ethereum Research 🛡️ Making PEPC-DVT private with BLS Blinded Multi-Signatures Cryptography signature-aggregation, cryptoeconomic-primitives, mev diego September 21, 2023, 2:47pm 1 TL;DR: PEPC-DVT can keep the block secret while obtaining signatures from the DVT network, thanks to BLS Blinded Multi-Signatures. keywords: dvt; payload; signatures cache: ethresear-16692.html plain text: ethresear-16692.txt item: #1246 of 3327 id: ethresear-16700 author: ethresear title: ethresear-16700 date: None words: 2095 flesch: 48 summary: We propose a three part optimisation that dramatically reduces CPU time in large distributed system using BLS signatures: This document explores how this concept, combined with advanced zero-knowledge proofs (deVirgo) and improved signature schemes, can enhance Ethereum’s latency and user experience. keywords: ethereum; finality; proof; signatures; slot cache: ethresear-16700.html plain text: ethresear-16700.txt item: #1247 of 3327 id: ethresear-16711 author: ethresear title: ethresear-16711 date: None words: 293 flesch: 65 summary: Are the proposed topics mainly for “formal verification for EVM”? ghasshee September 27, 2023, 10:20am 4 @hwwhww I would say “Formal Verification towards EVM” rather than “Formal verification for EVM”, since it could include various researches that might adapt to it. keywords: verification cache: ethresear-16711.html plain text: ethresear-16711.txt item: #1248 of 3327 id: ethresear-16760 author: ethresear title: ethresear-16760 date: None words: 1719 flesch: 51 summary: Impact on the performance and security metrics of traditional centralized sequencers potential challenges or flaws introduced by transitioning to a decentralized sequencer pool The need for decentralized sequencers, and impact on the broader landscape of L2 Rollups 11 Likes sing1ee September 28, 2023, 3:13am 2 psinelnikov: Consensus (PoS) layer: The role of the Consensus layer seems to be insignificant. Transition to Community Governance: As the network matures and more sequencers join, the aim is to transfer the Admin’s responsibilities to a community governance model. keywords: layer; mpc; october; pool; sequencer cache: ethresear-16760.html plain text: ethresear-16760.txt item: #1249 of 3327 id: ethresear-16762 author: ethresear title: ethresear-16762 date: None words: 3025 flesch: 55 summary: The Low-Carb Crusador proved that unbundling builder blocks can be extremely lucrative. In this design, relay trust is extended: the proposer trusts the relay to enforce their inclusion list. keywords: block; builder; inclusion; mev; proposer; relay cache: ethresear-16762.html plain text: ethresear-16762.txt item: #1250 of 3327 id: ethresear-16774 author: ethresear title: ethresear-16774 date: None words: 521 flesch: 37 summary: These are designed to obfuscate the identity of smart account owners. However, this could compromise the privacy of smart accounts by making ownership information publicly accessible. keywords: address; stealth cache: ethresear-16774.html plain text: ethresear-16774.txt item: #1251 of 3327 id: ethresear-16788 author: ethresear title: ethresear-16788 date: None words: 1794 flesch: 49 summary: PBS introduces a novel paradigm where validators are distinct from block builders, allowing builders to specialize in block construction, particularly in optimizing MEV, while validators concentrate on validation. Also, out of curiosity, how big of a deal is the bundle spam for builders? keywords: block; builders; payload; relay; release cache: ethresear-16788.html plain text: ethresear-16788.txt item: #1252 of 3327 id: ethresear-16828 author: ethresear title: ethresear-16828 date: None words: 1673 flesch: 49 summary: Arbitrum based allotment on onchain activity and used community detection algorithms like Louvain to identify Sybil clusters. 1130×621 50.3 KB ATG patterns detected as suspicious Sybil clusters Trusta analyzes asset transfer graphs to detect Sybil clusters through: Clusters are generated by partitioning ATGs into connected components like P1+P2. keywords: addresses; clusters; sybil; trusta cache: ethresear-16828.html plain text: ethresear-16828.txt item: #1253 of 3327 id: ethresear-16830 author: ethresear title: ethresear-16830 date: None words: 1521 flesch: 52 summary: By performing in-depth quantification and measurement of user behaviors within the blockchain ecosystem, MEDIA Score assigns a score from 0–100. MEDIA Score allows users to better know their own accounts, assess potential opportunities to earn ecosystem rewards, and interact with ecosystem projects more efficiently and reasonably. keywords: chain; media; score; user cache: ethresear-16830.html plain text: ethresear-16830.txt item: #1254 of 3327 id: ethresear-16839 author: ethresear title: ethresear-16839 date: None words: 2444 flesch: 65 summary: 🪢 zkUniswap: a first-of-its-kind zkAMM - Decentralized exchanges - Ethereum Research Ethereum Research 🪢 zkUniswap: a first-of-its-kind zkAMM Decentralized exchanges cryptoeconomic-primitives diego October 5, 2023, 11:41am 1 TL;DR: We introduce zkUniswap, a first-of-its-kind zkAMM that uses a zk co-processor to offload the computation of swaps. Swap Parallelization Continuations could be used to parallelize swaps. keywords: chain; pool; step; swap; zkuniswap cache: ethresear-16839.html plain text: ethresear-16839.txt item: #1255 of 3327 id: ethresear-16889 author: ethresear title: ethresear-16889 date: None words: 2107 flesch: 52 summary: The contract on L1 will check whether L2 operations had a valid starting point, comparing it to its previous state. In this case, L1 knows that user1 did not deposit any value, thus withdrawal of it (or the rest after L2 operations) is not possible. keywords: chain; master; rollup cache: ethresear-16889.html plain text: ethresear-16889.txt item: #1256 of 3327 id: ethresear-17 author: ethresear title: ethresear-17 date: None words: 1032 flesch: 44 summary: | by Dexaran | Jul, 2023 | Medium 1 Like Dexaran August 15, 2023, 1:36am 5 Today users lost at least $130M worth of ERC-20 tokens because of the above mentioned design flaw of the standard. Dexaran August 15, 2023, 1:43am 11 And other posts are not getting approved for days Reddit - Dive into anything https://www.reddit.com/r/ethereum/comments/15llp7p/i_want_to_raise_the_issue_of_censorship_on/ p_m August 16, 2023, 1:05am 12 tl;dr: OP points to the fact that it’s possible to send erc20 tokens to token contract address. 1 Like Dexaran August 16, 2023, 1:34am 13 No, OP points to the fact that ERC-20 standard is designed in a way that violates secure software design practices which resulted in (1) impossibility of handling transactions and (2) the implementation of pull transacting method which is not suitable for decentralized trustless assets and must be avoided. keywords: august; erc-20; ethereum cache: ethresear-17.html plain text: ethresear-17.txt item: #1257 of 3327 id: ethresear-17017 author: ethresear title: ethresear-17017 date: None words: 7024 flesch: 41 summary: uint256 constant S1y = 15937361384438336899506038077896335740375777943849319236297428061894225912107; uint256 constant S2x = 17851861163599905883319271566583905094659824424545336763314215826957296577422; uint256 constant S2y = 7207134938575551280982155439444040837908502217088364293609812357701988660758; uint256 constant S3x = 8113642222873669083238757229417253125647726979373059520013098551564263074152; uint256 constant S3y = 5406138351782904242339420516486698142593414088985235345843429425313254872333; uint256 constant k1 = 2; uint256 constant k2 = 3; uint256 constant X2x1 = 21831381940315734285607113342023901060522397560371972897001948545212302161822; uint256 constant X2x2 = 17231025384763736816414546592865244497437017442647097510447326538965263639101; uint256 constant X2y1 = 2388026358213174446665280700919698872609886601280537296205114254867301080648; uint256 constant X2y2 = 11507326595632554467052522095592665270651932854513688777769618397986436103170; // Proof calldata // Byte offset of every parameter of the calldata // Polynomial commitments uint16 constant pA = 4 + 0; uint16 constant pB = 4 + 64; uint16 constant pC = 4 + 128; uint16 constant pZ = 4 + 192; uint16 constant pT1 = 4 + 256; uint16 constant pT2 = 4 + 320; uint16 constant pT3 = 4 + 384; uint16 constant pWxi = 4 + 448; uint16 constant pWxiw = 4 + 512; // Opening evaluations uint16 constant pEval_a = 4 + 576; uint16 constant pEval_b = 4 + 608; uint16 constant pEval_c = 4 + 640; uint16 constant pEval_s1 = 4 + 672; uint16 constant pEval_s2 = 4 + 704; uint16 constant pEval_zw = 4 + 736; // Memory data // Challenges uint16 constant pAlpha = 0; uint16 constant pBeta = 32; uint16 constant pGamma = 64; uint16 constant pXi = 96; uint16 constant pXin = 128; uint16 constant pBetaXi = 160; uint16 constant pV1 = 192; uint16 constant pV2 = 224; uint16 constant pV3 = 256; uint16 constant pV4 = 288; uint16 constant pV5 = 320; uint16 constant pU = 352; uint16 constant pPI = 384; uint16 constant pEval_r0 = 416; uint16 constant pD = 448; uint16 constant pF = 512; uint16 constant pE = 576; uint16 constant pTmp = 640; uint16 constant pAlpha2 = 704; uint16 constant pZh = 736; uint16 constant pZhInv = 768; uint16 constant pEval_l1 = 800; uint16 constant pEval_l2 = 832; uint16 constant pEval_l3 = 864; uint16 constant pEval_l4 = 896; uint16 constant pEval_l5 = 928; uint16 constant pEval_l6 = 960; uint16 constant pEval_l7 = 992; uint16 constant pEval_l8 = 1024; uint16 constant pEval_l9 = 1056; uint16 constant lastMem = 1088; function verifyProof(uint256[24] calldata _proof, uint256[9] calldata _pubSignals) public view returns (bool) { assembly { ///////// // Computes the inverse using the extended euclidean algorithm ///////// function inverse(a, q) -> inv { let t := 0 let newt := 1 let r := q let newr := a let quotient let aux for { } newr { } { quotient := sdiv(r, newr) aux := sub(t, mul(quotient, newt)) t:= newt newt:= aux aux := sub(r,mul(quotient, newr)) === 0; O_bar[0] <== phi; O_bar[1] <== x; O_bar[2] <== d; component hasher = Poseidon(3); hasher.inputs[0] <== p; hasher.inputs[1] <== v; hasher.inputs[2] <== alpha; O_bar[3] <== hasher.out; // 4. compute b // if it's a bid, b[0] = 0, b[1] = p * v // else, b[0] = v, b[1] = 0 b[0] <== v * phi; temp <== p * v; b[1] <== (1 - phi) * temp; } component main{public keywords: aux; input; let; mload(add(pmem; mstore(add(min; mulmod; privacy; proof; signal; solidity; uint16; uint256 cache: ethresear-17017.html plain text: ethresear-17017.txt item: #1258 of 3327 id: ethresear-17032 author: ethresear title: ethresear-17032 date: None words: 3910 flesch: 49 summary: This message can only be sent by validators that currently have no metadata set, so it can be sent at most once per validator. What would validator metadata look like? keywords: entity; ethereum; metadata; proposal; protocol; staking; validator cache: ethresear-17032.html plain text: ethresear-17032.txt item: #1259 of 3327 id: ethresear-17044 author: ethresear title: ethresear-17044 date: None words: 403 flesch: 60 summary: Migration of smart contracts along with contract data i.e. L1 to L2 or L2 to L2 migrations. State extraction (snapshot) of smart contracts up to the latest or a certain block number. keywords: analysis; contract cache: ethresear-17044.html plain text: ethresear-17044.txt item: #1260 of 3327 id: ethresear-17055 author: ethresear title: ethresear-17055 date: None words: 2312 flesch: 49 summary: Thanks to Mike Neuder for developing Payload-timeliness committees and to Barnabé Monnot for the idea of using them to enforce proposer commitments. Since PEPC would come after ePBS, we extend the Payload-timeliness Committee (PTC) to enforce proposer commitments. keywords: block; commitments; csc; payload; proposer cache: ethresear-17055.html plain text: ethresear-17055.txt item: #1261 of 3327 id: ethresear-17089 author: ethresear title: ethresear-17089 date: None words: 1673 flesch: 44 summary: After a block builder publishes a 2m \times 2m sized expanded block to the network, Topia validators don’t download the entire expanded block. Using the Restaking technology, a subset of Ethereum validators operates the Topia Validator client to form a p2p data network, verifying blocks using techniques of randomly sampled committees and data availability sampling. keywords: data; ethereum; network; topia cache: ethresear-17089.html plain text: ethresear-17089.txt item: #1262 of 3327 id: ethresear-17092 author: ethresear title: ethresear-17092 date: None words: 1846 flesch: 64 summary: Bypassability and Collusion There were concerns similar to the currently discussed ePBS designs, that MEV Burn might suffer from bypassability. Summary: In the past, MEV rewards have overtaken Ethereum’s intrinsic consensus layer rewards, making MEV the main economic incentive to participate in Ethereum’s consensus. keywords: burn; eth; mev; slot cache: ethresear-17092.html plain text: ethresear-17092.txt item: #1263 of 3327 id: ethresear-17104 author: ethresear title: ethresear-17104 date: None words: 2601 flesch: 66 summary: However, the increasing number of app chains also raises questions around Decentralisation Composability Development experience In this post, I will try to explain the problems that arise due to having a lot of app chains and also pose a possible solution to the problem that I consider elegant and optimal for Madara and Starknet. If you are already well versed with app chains and shared sequencing, feel free to jump to the “Wait, it’s just Polkadot all over again” section. keywords: app; chain; ethereum; polkadot cache: ethresear-17104.html plain text: ethresear-17104.txt item: #1264 of 3327 id: ethresear-17114 author: ethresear title: ethresear-17114 date: None words: 924 flesch: 56 summary: In addition, the use of lookup tables to implement CPU instructions will lead to higher-quality, less error-prone zkVMs. Jolt and Lasso, a New Approach to Building zkVM — Part 2 - zk-s[nt]arks - Ethereum Research Ethereum Research Jolt and Lasso, a New Approach to Building zkVM — Part 2 zk-s[nt]arks jeroenvdgraaf October 17, 2023, 11:47am 1 keywords: approach; lasso; thaler cache: ethresear-17114.html plain text: ethresear-17114.txt item: #1265 of 3327 id: ethresear-17115 author: ethresear title: ethresear-17115 date: None words: 3062 flesch: 51 summary: Using the inclusion list, nodes make an execution-API call new_inclusion_list, providing parameters like parent_block_hash, inclusion list summary, and inclusion list transactions. The EL client performs various checks: Ensures alignment between inclusion list summary and transactions. keywords: block; inclusion; inclusion list; list; proposer; slot cache: ethresear-17115.html plain text: ethresear-17115.txt item: #1266 of 3327 id: ethresear-17119 author: ethresear title: ethresear-17119 date: None words: 830 flesch: 57 summary: Ethscriptions are cheaper because they store data on-chain using Ethereum transaction calldata, not smart contracts. Yes, Ethscriptions reinterpret existing Ethereum data, which is decentralized by nature. keywords: ethereum; ethscriptions cache: ethresear-17119.html plain text: ethresear-17119.txt item: #1267 of 3327 id: ethresear-1712 author: ethresear title: ethresear-1712 date: None words: 147 flesch: 65 summary: Use the following paragraphs for a longer description, or to establish category guidelines or rules: Why should people use this category? This guidance will appear in the category selection area, so try to keep it below 200 characters. keywords: category cache: ethresear-1712.html plain text: ethresear-1712.txt item: #1268 of 3327 id: ethresear-17125 author: ethresear title: ethresear-17125 date: None words: 3108 flesch: 65 summary: For pure booster rollups, transactions that deploy smart contracts will fail because smart contract deployments aren’t allowed. If the future demands hundreds or even thousands of rollups to adequately scale Ethereum, having each rollup function as an isolated unit, with its own set of smart contracts and rules, is not ideal. keywords: booster; rollup; smart cache: ethresear-17125.html plain text: ethresear-17125.txt item: #1269 of 3327 id: ethresear-17136 author: ethresear title: ethresear-17136 date: None words: 1887 flesch: 60 summary: Payment channels are used, and neither the sender nor the receiver will lose money even if they are offline for an extended period. Using this approach with payment channels, transactions from numerous senders to multiple recipients can share a single Merkle Tree Root of 32 bytes. keywords: alice; bob; payment; tree cache: ethresear-17136.html plain text: ethresear-17136.txt item: #1270 of 3327 id: ethresear-17137 author: ethresear title: ethresear-17137 date: None words: 156 flesch: 55 summary: image1285×618 44 KB The people who are involved are: image1091×648 38.7 KB Let’s show the world that Ethereum is a collective power of folks who truly care about what essentially powers the foundation of Ethereum: cryptography. The aim is essentially to find the pre-image for the P256 seed c49d360886e704936a6678e1139d26b7819f7e90 keywords: curve cache: ethresear-17137.html plain text: ethresear-17137.txt item: #1271 of 3327 id: ethresear-17169 author: ethresear title: ethresear-17169 date: None words: 6927 flesch: 60 summary: It does not affect the availability guarantees of the whole chain, and thus the safety of rollups, but it does weaken the safety of full nodes against double spends. The novelty would be that a higher number of subnets is used, but this would be counterbalanced by full nodes joining in multiple subnets each, so that each subnet should still contain sufficiently many nodes. keywords: data; nodes; number; row; samples; subnets; validators cache: ethresear-17169.html plain text: ethresear-17169.txt item: #1272 of 3327 id: ethresear-17175 author: ethresear title: ethresear-17175 date: None words: 4587 flesch: 49 summary: By comparison, zkML and opML secure onchain ML with different approaches: zkML: performs ML inference computation + generates ZK proofs for each ML inference opML: performs ML inference computation + re-executes a segment of ML inference computation onchain when the computation is challenged opML solves the computationally expensive problem of zkML by generating proofs only when necessary. 截屏2023-07-09_20.19.572704×1520 156 KB b) Implementation For the implementation of zkML, there are usually two approaches: Specific ZK circuit: Implementing different specific ZK circuits for different models (thus meeting the different needs of each use case, such as floating point precision) General zkML Runtime: Adding ZK to ML models with a common runtime (just like zkEVM for EVM programs) keywords: computation; model; onchain; opml; phase; proof; verification; zkml cache: ethresear-17175.html plain text: ethresear-17175.txt item: #1273 of 3327 id: ethresear-17176 author: ethresear title: ethresear-17176 date: None words: 866 flesch: 59 summary: Yet, two recent innovations in zkVM optimization techniques are challenging the way we approach zkVM design; Jolt and Lasso. Jolt uses Lasso to offer a new framework for designing SNARKs for zkVMs, and together they can improve performance, developer experience, and auditability for SNARKs, thus expanding the horizon for zkVM design. keywords: ethereum; zkvm cache: ethresear-17176.html plain text: ethresear-17176.txt item: #1274 of 3327 id: ethresear-172 author: ethresear title: ethresear-172 date: None words: 3887 flesch: 65 summary: The limitation on the number of validators is not due to the amount of state data that the need to store - rather, it has to do with the overhead of the consensus protocol being run. Then, we can transform: S -> the state root of S (ie. the 32 byte root hash of the Merkle Patricia tree containing S) B -> (B, W), where W is a “witness” - a set of Merkle branches proving the values of all data that the execution of B accesses STF -> STF’, which takes as input a state root and a block-plus-witness, uses the witness as a “database” any time the execution of the block needs to read any accounts, storage keys or other state data [exiting with an error if the witness does not contain some piece of data that is being asked for], and outputs the new state root That is, full nodes would only store state roots, and it would be miners’ responsibility to package Merkle branches (“witnesses”) along with the blocks, and full nodes would download and verify these expanded blocks. keywords: block; data; miners; nodes; state; stateless; transaction; witness cache: ethresear-172.html plain text: ethresear-172.txt item: #1275 of 3327 id: ethresear-17204 author: ethresear title: ethresear-17204 date: None words: 1875 flesch: 62 summary: Deep dive into snap sync for rollups Layer 2 Perseverance October 26, 2023, 7:54am 1 Overview This is an exploration of the various ideas and concepts around improving the time for rollup nodes to initially synchronise their state to the latest state of the rollup. Snap synchronisation for rollup nodes is an important concept due to the promise of the rollups to achieve a throughput orders of magnitude higher than L1. keywords: follower; node; snap; state cache: ethresear-17204.html plain text: ethresear-17204.txt item: #1276 of 3327 id: ethresear-17214 author: ethresear title: ethresear-17214 date: None words: 1390 flesch: 48 summary: Problems 1) Financial incentivise to communicate with light nodes are missing Most of blockchain users do not run their nodes in order to connect to Ethereum. Common scenario for light nodes attempting to speak to full nodes is that counterpart simply refuses connection; From rational standpoint it makes sense as even reading state requires some processing to be done by the node for each connected end-user and that must be somehow compensated in order to be sustainable. keywords: data; light; nodes; rpc cache: ethresear-17214.html plain text: ethresear-17214.txt item: #1277 of 3327 id: ethresear-17225 author: ethresear title: ethresear-17225 date: None words: 2332 flesch: 56 summary: When the floor price rises and falls, the absolute premium of each trait will fluctuate accordingly, but the ratio to floor price remains stable. We refer to premium of a NFT trait over floor price as the trait premium. keywords: floor; nft; price; trait; value; weights cache: ethresear-17225.html plain text: ethresear-17225.txt item: #1278 of 3327 id: ethresear-17249 author: ethresear title: ethresear-17249 date: None words: 580 flesch: 68 summary: Administrivia peersky October 30, 2023, 11:24pm 1 Many topics and even categories seem to be outdated; The links from read me are outdated like these notes are last updated like 6 years ago: HackMD Hello potential research collaborator! 6 Likes Olshansky October 31, 2023, 12:09am 2 +1 to what @peersky said. keywords: october; research cache: ethresear-17249.html plain text: ethresear-17249.txt item: #1279 of 3327 id: ethresear-17258 author: ethresear title: ethresear-17258 date: None words: 2857 flesch: 58 summary: However, as seen in Figure 2, our tagged slots show that integrated builder bids follow a two-stage nonlinear profile when leveraging CeFi-DeFi arbitrages. bid-profiles-tagged1500×812 72.8 KB Figure 2: In the median tagged auction, the leading integrated builder bid only surpasses non-integrated builder bids after the proposed MEV-burn cutoff. keywords: bid; builders; burn; mev; slots; volatility cache: ethresear-17258.html plain text: ethresear-17258.txt item: #1280 of 3327 id: ethresear-17263 author: ethresear title: ethresear-17263 date: None words: 3533 flesch: 47 summary: 10.0 Epidemic Broadcast of Merkle Proofs We now analyze techniques to optimize propagation of Merkle proofs between shards in the architecture. 6.0 Consensus via Merkle Proofs Nodes reach consensus on the canonical shard state by gossiping Merkle proof fragments of r_v and confirming matching roots. keywords: latency; merkle; proofs; shard; state; threshold; topology; transactions cache: ethresear-17263.html plain text: ethresear-17263.txt item: #1281 of 3327 id: ethresear-17279 author: ethresear title: ethresear-17279 date: None words: 2490 flesch: 63 summary: New precompiles L1CALL: Allows reading and writing L1 state. Allows reading and writing L1 state, but at the end of the call the L1 state changes are reverted. keywords: state cache: ethresear-17279.html plain text: ethresear-17279.txt item: #1282 of 3327 id: ethresear-17288 author: ethresear title: ethresear-17288 date: None words: 1269 flesch: 50 summary: Methodology Identifying Atomic MEV Activities & Searcher Addresses Using Zeromev’s API, which employs a slight modification of Flashbots’ mev-inspect-py for MEV detection, we identify atomic MEV transactions in each block. Our identification of atomic MEV is ultimately limited by Zeromev’s and mev-inspect-py’s capabilities, which have known issues and miss atomic MEV transactions that fall through their classification algorithm. keywords: atomic; mev; searcher cache: ethresear-17288.html plain text: ethresear-17288.txt item: #1283 of 3327 id: ethresear-17302 author: ethresear title: ethresear-17302 date: None words: 893 flesch: 59 summary: Yu has a higher degree of customization compared to other frameworks, and the development threshold is much lower than those frameworks(just like developing web APIs) Introducing Yu, A very suitable for L3, independency application blockchain framework - Applications - Ethereum Research Ethereum Research Introducing Yu, A very suitable for L3, independency application blockchain framework Applications layer-2 Lawliet-Chan November 5, 2023, 3:51am 1 Hi, guys. keywords: blockchain; framework cache: ethresear-17302.html plain text: ethresear-17302.txt item: #1284 of 3327 id: ethresear-17312 author: ethresear title: ethresear-17312 date: None words: 7071 flesch: 59 summary: i would go even further and say there are even more options for the HFT builder trying to execute sandwiches have a better view of the network topology and publish the bundle in such a way that it is the “last look” and no copycat bundles will have time to become public, or have an off chain agreement with large block proposers to serve them more valuable blocks so long as they don’t unbundle. With your suggested changes, relayers would just be required to contact n% of the attesting committee on top of the current proposer to still allow block builders to create MEV extracting blocks. keywords: block; builder; bundle; mev; proposer; sandwich; searcher; transaction; validators cache: ethresear-17312.html plain text: ethresear-17312.txt item: #1285 of 3327 id: ethresear-17315 author: ethresear title: ethresear-17315 date: None words: 1193 flesch: 63 summary: Customer scans Review Token using Client Application, checks its validity, expiry date and other details. 4.4. Customer writes a Review using Client Application. 4.5. keywords: review; seller; token cache: ethresear-17315.html plain text: ethresear-17315.txt item: #1286 of 3327 id: ethresear-17316 author: ethresear title: ethresear-17316 date: None words: 579 flesch: 30 summary: Incentivizing Communication with Light Nodes: Addressing the lack of financial incentives for full nodes to communicate with light nodes. Proposed Solutions: Decentralized Marketplace for Node Services: Creating a marketplace where nodes offer services with varying conditions, and light nodes pay for the level of service they require. keywords: data; nodes cache: ethresear-17316.html plain text: ethresear-17316.txt item: #1287 of 3327 id: ethresear-17318 author: ethresear title: ethresear-17318 date: None words: 2702 flesch: 55 summary: To demonstrate the viability of Firehose flat files as a historical archive for Ethereum, we only care about preserving the top-level transaction calls and receipts, as this is the data that is committed to and is verifiable in the blockchain. However, Firehose flat files intentionally do not contain any Beacon chain state data, as the purpose is solely focused on archiving historical transactional data and receipts from the execution layer. keywords: blockchain; data; files; firehose; graph cache: ethresear-17318.html plain text: ethresear-17318.txt item: #1288 of 3327 id: ethresear-17346 author: ethresear title: ethresear-17346 date: None words: 2150 flesch: 59 summary: Client Version Prysm develop-f1b88d0 Lighthouse stable-7c0b275 Teku master-fccbaf1 Nimbus stable-748be8b Lodestar unstable-375d660 Stumble on Organic Big Blocks At the same time this DAS research was ongoing, the team at MigaLabs was analysing block sizes and the number of transactions per block, among other data points. By looking at block sizes outside the experiment dates, we discovered that there were many big blocks in the Ethereum Mainnet. keywords: blocks; data; ethereum; size cache: ethresear-17346.html plain text: ethresear-17346.txt item: #1289 of 3327 id: ethresear-17350 author: ethresear title: ethresear-17350 date: None words: 3601 flesch: 60 summary: Is it possible to verify Swarm data directly in a smart contract on Ethereum Mainnet? tonytony November 13, 2023, 11:52am 9 fewwwww: Is it possible to verify Swarm data directly in a smart contract on Ethereum Mainnet? keywords: data; ethereum; light; network; node; state; storage; swarm cache: ethresear-17350.html plain text: ethresear-17350.txt item: #1290 of 3327 id: ethresear-17353 author: ethresear title: ethresear-17353 date: None words: 3005 flesch: 55 summary: The-CTra1n: preconfs can always front-run the non-preconfs I expect the vast majority of transactions will be preconfed and that non-preconfed user transactions will be a thing of the past. Non-preconfed transactions included onchain by non-preconfers will not execute immediately. keywords: non; preconfer; promise; transactions cache: ethresear-17353.html plain text: ethresear-17353.txt item: #1291 of 3327 id: ethresear-17356 author: ethresear title: ethresear-17356 date: None words: 1556 flesch: 57 summary: Requiring node operators to pay upfront to run validators can improve permissionless liquid staking protocols. Permissionless Liquid Staking Protocols (LSPs) like Rocketpool require node operators (NoOps) to put up capital to run validators whereas permissioned LSPs like Lido do not and instead rely on governance to whitelist professional NoOps. keywords: mev; node; operators; validator cache: ethresear-17356.html plain text: ethresear-17356.txt item: #1292 of 3327 id: ethresear-17359 author: ethresear title: ethresear-17359 date: None words: 1803 flesch: 58 summary: Another motivation for optimising epoch processing is that it grants implementations the freedom to explore different state models. Scope We only consider the process_epoch function which is responsible for computing state changes at the end of each 32-slot epoch. keywords: implementation; processing; proof; state; tree cache: ethresear-17359.html plain text: ethresear-17359.txt item: #1293 of 3327 id: ethresear-17366 author: ethresear title: ethresear-17366 date: None words: 3882 flesch: 56 summary: Anywhere else in the spectrum of “Sequencer choice” the designer will need to evaluate and make the decision of allowing forks. No punishment is easier to implement, but is incompatible with early sequencer payment design choice. keywords: choice; design; fork; rollup; sequencers cache: ethresear-17366.html plain text: ethresear-17366.txt item: #1294 of 3327 id: ethresear-1737 author: ethresear title: ethresear-1737 date: None words: 842 flesch: 62 summary: The adversary \mathcal{A} now has a set of valid Lamport signatures for a malicious block \mathcal{B}'. Threshold Lamport signatures can survive with much lower size by compromising on per-signature security level - Sharding - Ethereum Research Ethereum Research Threshold Lamport signatures can survive with much lower size by compromising on per-signature security level Sharding vbuterin April 15, 2018, 6:35am 1 Consider a Lamport signature scheme where there are 256 participants, and each participant is required to reveal one of eight values that they have committed to (ie. 128 bytes total for a Merkle branch). keywords: hash; signature cache: ethresear-1737.html plain text: ethresear-1737.txt item: #1295 of 3327 id: ethresear-17371 author: ethresear title: ethresear-17371 date: None words: 1433 flesch: 30 summary: Below we provide some background on restaking and a potential centralization risk that may evolve specifically within Eigen Layer. The restaking effort with the most mind share is currently Eigen Layer. keywords: avss; framework; layer cache: ethresear-17371.html plain text: ethresear-17371.txt item: #1296 of 3327 id: ethresear-17382 author: ethresear title: ethresear-17382 date: None words: 5124 flesch: 44 summary: Block proposers (i.e., validators randomly chosen to propose a block), instead of building blocks locally, can now access blocks from a builder marketplace, via trusted intermediaries known as relays. Relays act as trust facilitators between block proposers and block builders: they validate blocks and verify payments received by block builders, and only forward valid headers to proposers. keywords: block; figure; gas; median; proposers; rewards; transactions cache: ethresear-17382.html plain text: ethresear-17382.txt item: #1297 of 3327 id: ethresear-17384 author: ethresear title: ethresear-17384 date: None words: 7340 flesch: 65 summary: The compromise between socializing the costs of a missed burn vs. lowering the entry barriers for builder does make sense to me and choosing a large enough penalty should be enough to avoid builders bidding unrealisticly high to then not deliver. Under extreme circumstances, builder A could execute the following strategy: builder A observes builder B is willing to burn 1000 ETH and tip 1 ETH for a given slot, implying the existence of a huge opportunity to capture some MEV. keywords: base; bid; builder; burn; eth; fee; floor; mev; proposer; slot cache: ethresear-17384.html plain text: ethresear-17384.txt item: #1298 of 3327 id: ethresear-17386 author: ethresear title: ethresear-17386 date: None words: 5901 flesch: 54 summary: In this post we propose Signature Merge schemes as a solution to the bitfield aggregation problem, and three possible instantiations using SNARKs. Signature Merge schemes A Signature Merge (SM) scheme supports the recursive merging of signatures and their bitfields while still allowing the extraction of the signer set out of them. keywords: aggregation; bitfields; circuit; folding; merge; proof; scheme; signature; size; verification; witness cache: ethresear-17386.html plain text: ethresear-17386.txt item: #1299 of 3327 id: ethresear-17387 author: ethresear title: ethresear-17387 date: None words: 1642 flesch: 62 summary: And I would like to know more concretely why you mentioned SQL in the context of smart contract language development. In 2019, I listed 40+ papers about DSLs for tensor and image processing here: discussion: porting Halide to nim · Issue #347 · mratsim/Arraymancer · GitHub, yet there was plenty of general purpose languages that could fit the bill. keywords: compiler; erc-20; language; security cache: ethresear-17387.html plain text: ethresear-17387.txt item: #1300 of 3327 id: ethresear-17389 author: ethresear title: ethresear-17389 date: None words: 6044 flesch: 65 summary: With MEV-Burn inplace, local block builder might potentially not produce good-enough blocks to burn the agreed payload basefee floor. Nerolation: With MEV-Burn inplace, local block builder might potentially not produce good-enough blocks to burn the agreed payload basefee floor. keywords: bids; builder; deadline; eth; floor; payload cache: ethresear-17389.html plain text: ethresear-17389.txt item: #1301 of 3327 id: ethresear-17406 author: ethresear title: ethresear-17406 date: None words: 2239 flesch: 67 summary: MicahZoltu November 16, 2023, 6:42am 9 If all of the clients added the 4GB bit (but not the 100GB bit), and a user had access to an Ethereum client + an IPFS node, would they be able to get their own transaction history without needing any other third party services or indexes and without needing to trust anyone else? If my understanding is correct there is a small risk of correlational doxxing in this setup as someone could look at which shards a user downloaded, but someone who was concerned about this could simply download all of the shards presumably? quickBlocks November 17, 2023, 12:11am 10 If all of the clients added the 4GB bit (but not the 100GB bit), and a user had access to an Ethereum client + an IPFS node, would they be able to get their own transaction history without needing any other third party services or indexes and without needing to trust anyone else? keywords: index; november; quickblocks; user cache: ethresear-17406.html plain text: ethresear-17406.txt item: #1302 of 3327 id: ethresear-17407 author: ethresear title: ethresear-17407 date: None words: 2123 flesch: 41 summary: Therefore, SafeStake operators must agree to be held accountable to the following standards, or risk being forcibly removed from the network: Stay online and meet minimum performance criteria to be designated either a ‘Verified’ or ‘Unverified’ operator. It does this via validators that each require a separate deposit of 32 ETH. keywords: eth; safestake; staking; validator cache: ethresear-17407.html plain text: ethresear-17407.txt item: #1303 of 3327 id: ethresear-17417 author: ethresear title: ethresear-17417 date: None words: 1548 flesch: 59 summary: A node would be able to Subscribe/Unsubscribe corresponding sample subnets almost immediately since there is no need to search and connect to subnet nodes This concept meets the needs of various sampling approaches including original Danksharding, SubnetDAS approach Pull sampling Pulling recent samples is pretty straightforward: using a specific RPC method samples are requested from the nodes assigned to the corresponding shards. The value of N plays important role in sybil resistance, 32 is a number of subnets which a network relies upon in disseminating attestations today, using it as a number of network shards would not change sybil resistance properties that the network already has. keywords: network; node; shards cache: ethresear-17417.html plain text: ethresear-17417.txt item: #1304 of 3327 id: ethresear-17429 author: ethresear title: ethresear-17429 date: None words: 2385 flesch: 55 summary: This verification approach reduces the amount of state data users need to download, changing from one branch per block over the last week to just one branch per asset. Both the Account-based model and UTXO model are constructed and persisted by the operator. keywords: data; exit; merkle; plasma; state; utxo cache: ethresear-17429.html plain text: ethresear-17429.txt item: #1305 of 3327 id: ethresear-17445 author: ethresear title: ethresear-17445 date: None words: 1528 flesch: 67 summary: Asset Manage(include all ERC20 & ERC721) Assets, Approve, Legacies are genuinely managed by user wallets. The picture on the left is like the existing AA function, and the right is the wallet function, so the account abstraction and wallet abstraction should be completely different function and UI. keywords: abstraction; asset; user; wallet cache: ethresear-17445.html plain text: ethresear-17445.txt item: #1306 of 3327 id: ethresear-17450 author: ethresear title: ethresear-17450 date: None words: 185 flesch: 48 summary: Networking EggsyOnCode November 17, 2023, 12:37am 1 Like normally we have HTTP or SSH or other networking protocols dictating how machines communicate via the OSI model; in a similar vein i was wondering how do eth nodes communicate with each other and sync the latest EVM state with the local EVM state stored on their SSDs. What communication protocols do the eth clients/nodes use for communicating with other eth clients? keywords: ethereum cache: ethresear-17450.html plain text: ethresear-17450.txt item: #1307 of 3327 id: ethresear-17452 author: ethresear title: ethresear-17452 date: None words: 235 flesch: 28 summary: Study type: Experimental Study aim: Exploring the detection capabilities of deep learning models in smart contract vulnerability detection, assessing whether they outperform traditional static analysis tools. image1594×2200 121 KB Experiments: A solution is introduced which is based on deep learning techniques. The proposed Optimized-CodeBERT model outperforms other deep learning models, reaching the highest F1 score in comparison. keywords: learning cache: ethresear-17452.html plain text: ethresear-17452.txt item: #1308 of 3327 id: ethresear-17470 author: ethresear title: ethresear-17470 date: None words: 129 flesch: 29 summary: Collecting attestations with gossip protocols in a single slot - Consensus - Ethereum Research Ethereum Research Collecting attestations with gossip protocols in a single slot Consensus jtapolcai November 20, 2023, 1:24pm 1 The challenge is to collect cryptographic signatures from close to a million validators distributed worldwide on the network within 12 seconds without requiring high bandwidth internet connections from any of the validator nodes. We investigate alternative schemes that can achieve single-slot finality while reducing bandwidth consumption, enabling nodes with limited bandwidth to participate effectively. keywords: attestations cache: ethresear-17470.html plain text: ethresear-17470.txt item: #1309 of 3327 id: ethresear-17473 author: ethresear title: ethresear-17473 date: None words: 481 flesch: 51 summary: Approaches to IBC light clients via SNARKs - zk-s[nt]arks - Ethereum Research Ethereum Research Approaches to IBC light clients via SNARKs zk-s[nt]arks ZORK780 November 20, 2023, 3:31pm 1 Hey everyone, We at Panther published our SNARK paper earlier this year (https://eprint.iacr.org/2023/1255.pdf), as well as a follow-up paper (https://eprint.iacr.org/2023/1264.pdf). Right now we survey some approaches to IBC light clients via Snarks. keywords: ibc cache: ethresear-17473.html plain text: ethresear-17473.txt item: #1310 of 3327 id: ethresear-17481 author: ethresear title: ethresear-17481 date: None words: 13476 flesch: 45 summary: 4.1 Timestamp-Independent Proofs The system constructs balance invariance state proofs and SMT root proofs based solely on transaction states, not timestamps [1]. These proofs are constructed based on transaction states, independent of timing factors, and verify transaction integrity, ensuring the cryptographic validity of state transitions. keywords: balance; blockchain; consensus; def; hash; merkle; network; ordering; proof; protocol; return; root; scalability; security; shard; smt; state; transaction; trie cache: ethresear-17481.html plain text: ethresear-17481.txt item: #1311 of 3327 id: ethresear-17487 author: ethresear title: ethresear-17487 date: None words: 346 flesch: 37 summary: Introducing CrossLayer and Delphinus Lab: zkWasm Rollups solution brings eWASM to Layer2 - Layer 2 - Ethereum Research Ethereum Research Introducing CrossLayer and Delphinus Lab: zkWasm Rollups solution brings eWASM to Layer2 Layer 2 zk-roll-up bngjly November 23, 2023, 9:15am 1 TL; DR: zkWasm rollup solution is more suitable than eWASM for Ethereum to build Web 3.0. zkWasm and zkEVM can broaden the Web 3.0 ecosystem and connect with Web 2.0. Several Web3 games with zkWasm examples: https://delphinuslab.com/wp-content/uploads/2023/04/zksummit-presentation-zkwasm-game-1.pdf zkWasm Emulator: https://github.com/DelphinusLab/zkWasm we want to get more feedback from the Ethereum community and hope more developers including former eWASM contributors can build the zkWasm ecosystem together, let’s bring more flexibility and mass adoption to Ethereum. keywords: ethereum; zkwasm cache: ethresear-17487.html plain text: ethresear-17487.txt item: #1312 of 3327 id: ethresear-17488 author: ethresear title: ethresear-17488 date: None words: 852 flesch: 68 summary: You can find the source code here: GitHub GitHub - dennis-tra/nebula: 🌌 A network agnostic DHT crawler, monitor, and... 🌌 A network agnostic DHT crawler, monitor, and measurement tool that exposes timely information about DHT networks. The first version of Armiarma was very general and we used it for other networks. keywords: crawler; dht cache: ethresear-17488.html plain text: ethresear-17488.txt item: #1313 of 3327 id: ethresear-17495 author: ethresear title: ethresear-17495 date: None words: 721 flesch: 52 summary: This strategy effectively removes incentives for sequencers to engage in MEV theft. Benefits of FIFO in MEV Extraction: FIFO ordering ensures that transactions are processed in the order they are received, promoting fairness and reducing the likelihood of MEV-related manipulations and decreasing throughput. In this system, non-faulty nodes will only sign blocks that adhere to FIFO ordering. keywords: bft; block; mev cache: ethresear-17495.html plain text: ethresear-17495.txt item: #1314 of 3327 id: ethresear-17523 author: ethresear title: ethresear-17523 date: None words: 443 flesch: 69 summary: The design would be to use channel topics to save DNS records. From there they could be used for dynamic DNS or really anything. keywords: dns cache: ethresear-17523.html plain text: ethresear-17523.txt item: #1315 of 3327 id: ethresear-17538 author: ethresear title: ethresear-17538 date: None words: 4283 flesch: 61 summary: If you want to pursue this course of research, I recommend first showing evidence that financial surveillance has a significant positive impact on crime reduction, and then showing that that positive impact outweighs the negative impact caused by side effects of financial surveillance systems. While I suspect many/most would agree that it would be great if we could stop bad people from doing bad things, we should not be falling into the same trap that prior financial systems have fallen into where it is assumed (without any evidence) that stopping crime is as easy as controlling who has access to money. keywords: censorship; data; november; privacy; surveillance; system cache: ethresear-17538.html plain text: ethresear-17538.txt item: #1316 of 3327 id: ethresear-17538?page=2 author: ethresear title: ethresear-17538?page=2 date: None words: 269 flesch: 45 summary: dangduce December 16, 2023, 4:34pm 22 A nuanced approach to privacy should be adopted in blockchain projects, where privacy is protected while regulation is needed to prevent abuse, and innovative solutions are used to strike a balance between privacy and regulatory compliance. If you want this kind of system, you’re probably better of taking an SQL database and lobbying your local government for a new financial system, because the system you’re proposing doesn’t fundamentally look different to the existing financial system. keywords: privacy cache: ethresear-17538?page=2.html plain text: ethresear-17538?page=2.txt item: #1317 of 3327 id: ethresear-17540 author: ethresear title: ethresear-17540 date: None words: 846 flesch: 52 summary: I would be happy to discuss different measures relating to decentralization (what can be measured, how, what are the different facets (e.g. entity concentration/correlation, geographic and jurisdictional dispersion, infrastructure diversity) and you can also check out work done by rated.network (some work on network penetration and HHI) as well as @simbro’s initiative on geographic decentralization here. We are currently looking to extend the EDI by adding support for more blockchains. keywords: december; decentralization; edinburgh cache: ethresear-17540.html plain text: ethresear-17540.txt item: #1318 of 3327 id: ethresear-17553 author: ethresear title: ethresear-17553 date: None words: 3072 flesch: 54 summary: jtapolcai December 4, 2023, 10:36am 3 More charts: jtapolcai December 4, 2023, 10:46am 4 A figure illustrates the cost per ID (\eta_c in bits) relative to the number of unique IDs (k) in a message used for distributing aggregated signatures. Data structure for validator IDs and coefficients keywords: bits; ids; message; node; signature; validators cache: ethresear-17553.html plain text: ethresear-17553.txt item: #1319 of 3327 id: ethresear-17565 author: ethresear title: ethresear-17565 date: None words: 1545 flesch: 59 summary: Grim Forker: checks and balances to AMM protocol fees - Economics - Ethereum Research Ethereum Research Grim Forker: checks and balances to AMM protocol fees Economics governance, dao lajarre November 29, 2023, 10:59pm 1 This post summarizes a paper draft from our research at Butter, focusing on governance mechanisms in AMMs with protocol fees. Attack vector: forked AMM contract with subsidy, funding mechanism contract. keywords: amm; governance; protocol; subsidy cache: ethresear-17565.html plain text: ethresear-17565.txt item: #1320 of 3327 id: ethresear-17572 author: ethresear title: ethresear-17572 date: None words: 819 flesch: 45 summary: We are pleased with the efforts of developers in the field of chain abstraction, as they have provided possibilities to reduce the interaction costs for users across different chains. This situation not only significantly raises the difficulty of users’ on-chain operations but also severs the flow and interaction between user communities of different projects. keywords: chain; game cache: ethresear-17572.html plain text: ethresear-17572.txt item: #1321 of 3327 id: ethresear-176 author: ethresear title: ethresear-176 date: None words: 4423 flesch: 61 summary: It is interesting to understand how a bloom filter would perform vs Merkle tree vs RSA accumulator … Bloom filters are widely used in routing tables of network routers, arguably if RSA accumulators would be faster Cisco guys would use them. Non-Merkle accumulators tend to fall into two classes: RSA accumulators and elliptic curve accumulators. keywords: accumulator; data; elements; number; set; size; transaction cache: ethresear-176.html plain text: ethresear-176.txt item: #1322 of 3327 id: ethresear-17612 author: ethresear title: ethresear-17612 date: None words: 9312 flesch: 59 summary: However, there is money to be made on the path to the equilibrium by block proposers playing timing games more aggressively than others; thus the honest strategy is not an equilibrium. Timing games are a strategy where block proposers intentionally delay the publication of their block for as long as possible to maximize MEV capture. keywords: block; games; latency; mev; playing; proposer; relay; slot; time; timing; timing games; validator cache: ethresear-17612.html plain text: ethresear-17612.txt item: #1323 of 3327 id: ethresear-17612?page=2 author: ethresear title: ethresear-17612?page=2 date: None words: 113 flesch: 49 summary: Timing Games: Implications and Possible Mitigations - Proof-of-Stake - Ethereum Research Ethereum Research Timing Games: Implications and Possible Mitigations Proof-of-Stake Julian December 14, 2023, 10:34am 23 If we were to have attester-proposer separation in the way just now proposed by Justin Drake at CCE, I think we don’t need to worry as much about proposer timing games. We still want a credibly neutral validator set so we don’t want vertical integration for e.g. geographical decentralization. keywords: games cache: ethresear-17612?page=2.html plain text: ethresear-17612?page=2.txt item: #1324 of 3327 id: ethresear-17616 author: ethresear title: ethresear-17616 date: None words: 193 flesch: 39 summary: Enhancing the competitive edge of LST by expanding the use cases of new LSTs - Proof-of-Stake - Ethereum Research Ethereum Research Enhancing the competitive edge of LST by expanding the use cases of new LSTs Proof-of-Stake signalxu December 6, 2023, 10:15am 1 Hey everyone To mitigate Lido’s dominance in the market and encourage a more competitive landscape, it is crucial to introduce additional LST protocols. This challenge significantly hinders their inclusion in lending, borrowing, and stablecoin protocols. keywords: lsts cache: ethresear-17616.html plain text: ethresear-17616.txt item: #1325 of 3327 id: ethresear-17620 author: ethresear title: ethresear-17620 date: None words: 3514 flesch: 55 summary: Number of CEX DEX Arbitrages, average absolute and relative profit levels, segmented by type of asset pairs traded Meme-alt trading strategies yielded the greatest revenue given that both are relatively volatile assets and thus, reaped the greatest rewards. Number of CEX DEX Arbitrages on Uniswap V2, segmented by type of asset pairs traded. keywords: arbitrages; block; builder; cex; dex; revenue cache: ethresear-17620.html plain text: ethresear-17620.txt item: #1326 of 3327 id: ethresear-17624 author: ethresear title: ethresear-17624 date: None words: 214 flesch: 60 summary: I think it is unethical for dydx to take legal action , if someone places a big market order for buy and it makes the short liquidate - you should not take legal action about the trader who profited. Perp dex liquidity - Decentralized exchanges - Ethereum Research Ethereum Research Perp dex liquidity Decentralized exchanges parzivalishan December 6, 2023, 4:21pm 1 As you maybe aware that dydx had a recent loss of about 10 million dollars due to $yfi price spiked and dumped. keywords: dydx cache: ethresear-17624.html plain text: ethresear-17624.txt item: #1327 of 3327 id: ethresear-17651 author: ethresear title: ethresear-17651 date: None words: 306 flesch: 41 summary: It stems from the recognition of the significant obstacles faced by smart contracts in terms of trustworthiness due to security bugs and trapdoors. While smart contracts are crucial elements of decentralized technologies, their vulnerabilities pose a challenge to their widespread adoption. keywords: tct cache: ethresear-17651.html plain text: ethresear-17651.txt item: #1328 of 3327 id: ethresear-17682 author: ethresear title: ethresear-17682 date: None words: 1271 flesch: 55 summary: No potential for getting sandwich attacked Cons: Needs x amount of users to adopt before searchers add these to their strategy Usually not executed as quickly as using a DEX directly Challenges The main barrier for getting this scheme to work at scale is getting enough MEV Searchers to include it in their arbitrage bot logic. Risks If a sufficient number of SwapRequests is not achieved, then few MEV Searchers will include it in their arbitration bot logic, and users will be dissatisfied that their SwapRequest never gets executed. keywords: dex; mev; searchers; swap cache: ethresear-17682.html plain text: ethresear-17682.txt item: #1329 of 3327 id: ethresear-17689 author: ethresear title: ethresear-17689 date: None words: 565 flesch: 43 summary: https://eips.ethereum.org/EIPS/eip-665 Simple Summary Support performant and cheap verification of Ed25519 cryptographic signatures in smart contracts in general by adding a precompiled contract for Ed25519 signature verification to the EVM. One motivation for Ed25519 signature verification in smart contracts is to associate existing off-chain systems, records or accounts that use Ed25519 (like above) with blockchain addresses or delegate by allowing to sign data with Ed25519 (only), and then submit this Ed25519-signed data anonymously (via any Eth sender address) to the blockchain, having the contract check the Ed25519 signature of the transaction. keywords: contract; ed25519 cache: ethresear-17689.html plain text: ethresear-17689.txt item: #1330 of 3327 id: ethresear-17748 author: ethresear title: ethresear-17748 date: None words: 679 flesch: 43 summary: It enables the maximization of the Privacy Pool size and allows users with all assets to have a common level of privacy. In other words, increasing the number of participating addresses or transactions in the protocol enhances obfuscation, making the continuous maximization of pool size important from a privacy perspective. keywords: pool; privacy cache: ethresear-17748.html plain text: ethresear-17748.txt item: #1331 of 3327 id: ethresear-17750 author: ethresear title: ethresear-17750 date: None words: 1252 flesch: 58 summary: Two common ways to construct a dissociation set using merkle tree are as follows: Sparse merkle tree A sparse merkle tree is a tree of the same size of the incremental merkle tree that contains the deposit note. keywords: merkle; tree cache: ethresear-17750.html plain text: ethresear-17750.txt item: #1332 of 3327 id: ethresear-17796 author: ethresear title: ethresear-17796 date: None words: 996 flesch: 44 summary: In optimistic bridges using a distributed relayer model, each relayer can establish their own liquidity pool, containing only assets they are willing to commit for bridge transactions. Suspicious activity can lead to a dispute, triggering a verification process settled by Layer 1. Mechanism Network participants Optimistic bridge consists of three participants - user, relayer and disputer. keywords: bridge; liquidity; relayer cache: ethresear-17796.html plain text: ethresear-17796.txt item: #1333 of 3327 id: ethresear-17804 author: ethresear title: ethresear-17804 date: None words: 2609 flesch: 53 summary: By leveraging onchain call proofs, the responsibility of initiating the auction can be transferred to the participants (auction bidders). 2.3 Proof of Storage With the accessibility of onchain proofs for blockhashes now established, the next crucial step involves generating ZKPs for a specific set of storage slots. keywords: block; blockhash; evm; proof; storage cache: ethresear-17804.html plain text: ethresear-17804.txt item: #1334 of 3327 id: ethresear-17833 author: ethresear title: ethresear-17833 date: None words: 957 flesch: 55 summary: Negative Price AMM - Decentralized exchanges - Ethereum Research Ethereum Research Negative Price AMM Decentralized exchanges mev v-for-vasya December 15, 2023, 12:03am 1 TL;DR: We discover that negative liquidity is possible and construct an AMM to access the negative domain by allowing the price to go negative. An approach to avoid negative prices for the underlying could be to construct a passive wall of liquidity, a liquidity fingerprint that asymmetrically increases non-linearly as price approaches zero, denting price impact. keywords: liquidity; price cache: ethresear-17833.html plain text: ethresear-17833.txt item: #1335 of 3327 id: ethresear-17844 author: ethresear title: ethresear-17844 date: None words: 3808 flesch: 54 summary: Moreover, Octopus contracts can evaluate arbitrary functions on encrypted inputs with one-time programs built from SWE and garbled circuits. We propose the concept of Octopus contracts, smart contracts that operate ciphertexts outside the blockchain. keywords: circuit; contract; input; key; octopus; validators cache: ethresear-17844.html plain text: ethresear-17844.txt item: #1336 of 3327 id: ethresear-17847 author: ethresear title: ethresear-17847 date: None words: 4550 flesch: 45 summary: A share of the direct upside again accrues to latency optimized node operators, reinforcing centralization pressure. A profit share directly accrues to latency optimized node operators; additionally, LPs may stake with such node operators to offset some of their LVR risk, manifesting further centralization pressure. keywords: block; eth; increase; latency; mev; node; operators; setup cache: ethresear-17847.html plain text: ethresear-17847.txt item: #1337 of 3327 id: ethresear-17852 author: ethresear title: ethresear-17852 date: None words: 116 flesch: 68 summary: Quantum secure transactions on Ethereum - zk-s[nt]arks - Ethereum Research Ethereum Research Quantum secure transactions on Ethereum zk-s[nt]arks Bisht13 December 15, 2023, 9:43pm 1 I was able to make post quantum secure transactions on Ethereum without changing the main layer. The code and proof of concept is present in this repo. keywords: ethereum cache: ethresear-17852.html plain text: ethresear-17852.txt item: #1338 of 3327 id: ethresear-17882 author: ethresear title: ethresear-17882 date: None words: 855 flesch: 63 summary: Let’s explain what we see: blue border represents the path to our NodeId we expect tree nodes close to it to be saved green nodes are always saved, regardless of what their node_hash is blue nodes are never saved yellow nodes have two meanings: they represent nodes that are only sometimes saved (depending on their node_hash) they usually contain all 3 types of children (blue, green, yellow) there is exactly one path of yellow nodes, from root to the leaf (can be calculated with xor(node_id, radius)) Network node will store tree nodes that are close, e.g. when distance is smaller then radius (that is configured based on clients preferences). keywords: path; tree cache: ethresear-17882.html plain text: ethresear-17882.txt item: #1339 of 3327 id: ethresear-17888 author: ethresear title: ethresear-17888 date: None words: 1146 flesch: 45 summary: operator_delay_time_distribution2000×1000 29.3 KB Fig 2: distribution of delay time of selected blocks using intentionally delayed proposals. Empirical analysis of the impact of block delays on the consensus layer - Consensus - Ethereum Research Ethereum Research Empirical analysis of the impact of block delays on the consensus layer Consensus mev aimxhaisse December 18, 2023, 1:09pm 1 author: mxs@kiln.fi Vladimir: That passed the time. keywords: network; time cache: ethresear-17888.html plain text: ethresear-17888.txt item: #1340 of 3327 id: ethresear-1792 author: ethresear title: ethresear-1792 date: None words: 3433 flesch: 60 summary: The only other requirement is that the genetor is one of the submittors of the final answer, so that the start message cannot be used to create other nodes Some futher defintions are provided below: // TODO (active nodes, reputable nodes, nonreputable nodes, honest nodes) keywords: block; model; network; nodes; time cache: ethresear-1792.html plain text: ethresear-1792.txt item: #1341 of 3327 id: ethresear-1825 author: ethresear title: ethresear-1825 date: None words: 3435 flesch: 57 summary: In short, I really don’t think we need fancy threshold signature randomness or low-influence functions or any other fancy math; a simple RANDAO mechanism as described above with total main chain rewards being comparable to total shard chain rewards is enough. If we have a rule that there is one shard collation per main chain block, then yes, one main chain participant skipping causes the shard waiting time to double. keywords: block; chain; preimage; randao; validator cache: ethresear-1825.html plain text: ethresear-1825.txt item: #1342 of 3327 id: ethresear-2 author: ethresear title: ethresear-2 date: None words: 3065 flesch: 51 summary: Using the inclusion list, nodes make an execution-API call new_inclusion_list, providing parameters like parent_block_hash, inclusion list summary, and inclusion list transactions. The EL client performs various checks: Ensures alignment between inclusion list summary and transactions. keywords: block; inclusion; inclusion list; list; proposer; slot cache: ethresear-2.html plain text: ethresear-2.txt item: #1343 of 3327 id: ethresear-2066 author: ethresear title: ethresear-2066 date: None words: 1534 flesch: 67 summary: tim-becker September 22, 2022, 7:46pm 15 We are using a similar approach for accessing historical block hashes on-chain in Relic Protocol. We store Merkle roots of chunks of historical block hashes in storage, and use zk-SNARKs to prove their validity. keywords: blocks; history; need cache: ethresear-2066.html plain text: ethresear-2066.txt item: #1344 of 3327 id: ethresear-209 author: ethresear title: ethresear-209 date: None words: 646 flesch: 68 summary: Witness data becomes closer to first class, and so we can resolve the mispricing issues between small storage tries and big tries by simply charging for witness data directly. Add a rule that we charge the miner X gas per byte of witness data. keywords: data; witness cache: ethresear-209.html plain text: ethresear-209.txt item: #1345 of 3327 id: ethresear-210 author: ethresear title: ethresear-210 date: None words: 335 flesch: 67 summary: = acct = (nonce, balance, code, storage tree root) storage_tree[sha3(KEY)] This model has benefits, but it also has led to considerable implementation complexity. keywords: trie cache: ethresear-210.html plain text: ethresear-210.txt item: #1346 of 3327 id: ethresear-2120 author: ethresear title: ethresear-2120 date: None words: 3532 flesch: 69 summary: When nodes gossip transactions, receipts for that gossip are captured and disseminated through gossip - that’s where the term “gossip about gossip” comes from. I am publishing it here because it may be interesting for some people My humble opinion after reading Hashgraph whitepaper is that every page potentially contains vulnerabilities, since they have proofs that are not really proofs, theorems that are not theorems and lemmas which are not lemmas…Every object is vaguely defined, so it becomes hard to analyze. keywords: consensus; gossip; hashgraph; median; time; transaction cache: ethresear-2120.html plain text: ethresear-2120.txt item: #1347 of 3327 id: ethresear-218 author: ethresear title: ethresear-218 date: None words: 2114 flesch: 59 summary: blocks, target total deposit value) Also related to this, we will be posting some thoughts on CAPM, standard deviation of validator returns, soft/draconian slashing and required returns. keywords: level; yield cache: ethresear-218.html plain text: ethresear-218.txt item: #1348 of 3327 id: ethresear-2270 author: ethresear title: ethresear-2270 date: None words: 1129 flesch: 50 summary: The init code is executed in the context of this component (has access to its state and can create other components). Capabilities A component tracks other components to which this address should have access to. keywords: component; contract cache: ethresear-2270.html plain text: ethresear-2270.txt item: #1349 of 3327 id: ethresear-2305 author: ethresear title: ethresear-2305 date: None words: 903 flesch: 63 summary: Obviously a full audittrail should be made available by those monitoring services in case of occurence of such events designed and operated by N independent parties. I can already name two such events that should be actively monitored and all alarm bells should go off when such events occur. keywords: chain; monitoring cache: ethresear-2305.html plain text: ethresear-2305.txt item: #1350 of 3327 id: ethresear-2338 author: ethresear title: ethresear-2338 date: None words: 1020 flesch: 57 summary: The challenges for consensus mechanisms are: Setting R and P to both minimize griefing factors (going lower than 1.53 is possible) and satisfy their other constraints (namely, penalizing attacks) If we force censorship to be all-or-nothing, one can show that R(x) = x^{1.53} and P(x) = 0 has griefing factors of 1.53 for going offline and for censorship, achieving a clearly better result than 2 (the griefing factor for going offline is clearly 1.53 because \frac{x * R'(x)}{R(x) - P(x)} keywords: griefing cache: ethresear-2338.html plain text: ethresear-2338.txt item: #1351 of 3327 id: ethresear-2443 author: ethresear title: ethresear-2443 date: None words: 743 flesch: 53 summary: Anyone can register a token pair (A/B) traders can act as askers (market order) or bidders (limit order) upfront enough askers need to commit to sell token A for token B once a threshold is reached a auction will start at 2* the previous price (market price) the price will continuously fall down, reaching the previous price after 6h and 0 after 24. Features Full decentralization a) all actions on chain (contracts thus 1st class citizens) b) anyone can list tokens c) no role with special rights in the trading process d) a DAO will be able to make upgrades to the contract but only with a 30 day notice period Regular user (including contracts) can (relatively) safely submit market orders a) market orders can not be attacked with frontrunning b) a market maker does not need to constantly update prices onchain to provide a small spread c) keywords: auction; price cache: ethresear-2443.html plain text: ethresear-2443.txt item: #1352 of 3327 id: ethresear-2512 author: ethresear title: ethresear-2512 date: None words: 125 flesch: 67 summary: Checking for contracts in Constantinople - EVM - Ethereum Research Ethereum Research Checking for contracts in Constantinople EVM MoonMissionControl July 10, 2018, 12:01am 1 Right now, in solidity, there are two ways to check for a contract, via extcodesize or by checking if tx.origin == msg.sender. extcodesize does not work for contracts calling via their constructor. keywords: contracts cache: ethresear-2512.html plain text: ethresear-2512.txt item: #1353 of 3327 id: ethresear-2554 author: ethresear title: ethresear-2554 date: None words: 2689 flesch: 69 summary: 2 Likes mkoeppelmann July 26, 2018, 9:51am 5 20 min summary of the concept: 2 Likes josojo August 1, 2018, 4:39pm 6 For convenience, here are also the slides used at dappcon: docs.google.com 2018-08 DappCon plasma exchange batch auctions Batch Auctions on Plasma 1 Like paborre August 22, 2018, 8:17pm 7 This is very interesting work. Even that would open a door for griefing attacks, and push DKG participants out of the system. keywords: auction; dkg; operator; order cache: ethresear-2554.html plain text: ethresear-2554.txt item: #1354 of 3327 id: ethresear-2630 author: ethresear title: ethresear-2630 date: None words: 2408 flesch: 65 summary: As long writing contracts is more complicated than implementing these behaviors, I think the exact scamming/skimming attacks will continue to be the downfall of contracts trying to build these behaviors, versus it actually working and getting a large enough pot to suffer from these existential attacks. I think in general, it’s an anti-pattern to try to handle smart contracts and external accounts differently, but if there was a specific need I would probably use tx.orgin == msg.sender instead (as Nick Johnson mentioned in a reply) Does anyone dispute this as an anti-pattern? keywords: contract; eth; game; july; key cache: ethresear-2630.html plain text: ethresear-2630.txt item: #1355 of 3327 id: ethresear-265 author: ethresear title: ethresear-265 date: None words: 110 flesch: 72 summary: [ version_num, # Transaction format version, 0 for now chain_id, # 1 for ETH, 3 for ropsten... shard_id, # Tx data ] Depending on what is done in Tradeoffs in Account Abstraction Proposals, fields can simply be added on to the end of this as needed. keywords: sharding cache: ethresear-265.html plain text: ethresear-265.txt item: #1356 of 3327 id: ethresear-2665 author: ethresear title: ethresear-2665 date: None words: 926 flesch: 60 summary: In general, to compare the best options for post-quantum signatures, it’s better to look into results of NIST post-quantum competitions, which runs now. The network will still have to upgrade to post-quantum signatures (like Falcon or Dilithium) but at least it’s now possible to start upgrading the quantum vulnerable ECDSA wallets now. keywords: post; quantum; signature cache: ethresear-2665.html plain text: ethresear-2665.txt item: #1357 of 3327 id: ethresear-2699 author: ethresear title: ethresear-2699 date: None words: 362 flesch: 68 summary: So it seems that main net uses different pending block creation rules. They may use special purpose software - not geth default, or geth with non-default parameters … Theoretically miners include whatever they deem good for themselves subject to the contstraint of block gas limit. keywords: ethereum cache: ethresear-2699.html plain text: ethresear-2699.txt item: #1358 of 3327 id: ethresear-27 author: ethresear title: ethresear-27 date: None words: 3811 flesch: 65 summary: I have many questions but let’s start with three: 1/ Is it correct that in your proposed scheme, the entire set of key pairs for deposit addresses is generated in an initial trusted setup, such that when we run out of addresses, another trusted ceremony would need to take place? Yes, we need it when we are short of deposit addresses. keywords: bitcoin; btc; deposit; ethereum; leohio; proof cache: ethresear-27.html plain text: ethresear-27.txt item: #1359 of 3327 id: ethresear-2755 author: ethresear title: ethresear-2755 date: None words: 461 flesch: 60 summary: One method to bypass this bottleneck is developing Ethereum nodes optimized in data-delivery. This means that we should constraint gas limit to 12M, for a block explorer to easily follow the mainnet. keywords: data; ethereum cache: ethresear-2755.html plain text: ethresear-2755.txt item: #1360 of 3327 id: ethresear-2791 author: ethresear title: ethresear-2791 date: None words: 2170 flesch: 68 summary: As I understand it the EVM would not wind up a subchain anytime soon, as EVM code must keep running on the mainchain in order for the Shasper beacon chain to work. And indeed, verification is difficult, and porting verified EVM code to eWasm–and your specs and models and tools–might not be fun. keywords: compilers; evm; ewasm; gcolvin; security cache: ethresear-2791.html plain text: ethresear-2791.txt item: #1361 of 3327 id: ethresear-28 author: ethresear title: ethresear-28 date: None words: 2653 flesch: 74 summary: While I often complain about the size of Ethereum full nodes and the fact that most users cannot run them, requiring an archive node essentially forces you into having a dedicated server. If you require an archive node, then this doesn’t work on a small machine as archive nodes don’t work on small machines. keywords: archive; index; node; november cache: ethresear-28.html plain text: ethresear-28.txt item: #1362 of 3327 id: ethresear-3039 author: ethresear title: ethresear-3039 date: None words: 2500 flesch: 61 summary: Polynomial interpolation (and its inverse, multi-point evaluation) is also used extensively in erasure coding, which is useful for data recovery and in blockchains for data availability checking. Reed-Solomon erasure code recovery in n*log^2(n) time with FFTs - Sharding - Ethereum Research Ethereum Research Reed-Solomon erasure code recovery in n*log^2(n) time with FFTs Sharding vbuterin August 21, 2018, 11:29pm 1 With Fast Fourier transforms it’s possible to convert a set of evaluations of a polynomial over a prime field at a set of specific points, P(1), P(r), P(r^2) … P(r^{{2^k}-1}) keywords: algorithm; data; points; polynomial; z_{r cache: ethresear-3039.html plain text: ethresear-3039.txt item: #1363 of 3327 id: ethresear-3101 author: ethresear title: ethresear-3101 date: None words: 141 flesch: 61 summary: Use the following paragraphs for a longer description, or to establish category guidelines or rules: Why should people use this category? This guidance will appear in the category selection area, so try to keep it below 200 characters. keywords: category cache: ethresear-3101.html plain text: ethresear-3101.txt item: #1364 of 3327 id: ethresear-3195 author: ethresear title: ethresear-3195 date: None words: 107 flesch: 52 summary: I develop and research automated security assessment tools to enhance smart contract security. But I’d suggest security category for sharing the research idea and findings. keywords: security cache: ethresear-3195.html plain text: ethresear-3195.txt item: #1365 of 3327 id: ethresear-3197 author: ethresear title: ethresear-3197 date: None words: 141 flesch: 62 summary: Use the following paragraphs for a longer description, or to establish category guidelines or rules: Why should people use this category? About the Security category - Security - Ethereum Research Ethereum Research About the Security category Security hwwhww September 3, 2018, 8:43am 1 (Replace this first paragraph with a brief description of your new category. keywords: category cache: ethresear-3197.html plain text: ethresear-3197.txt item: #1366 of 3327 id: ethresear-3198 author: ethresear title: ethresear-3198 date: None words: 1872 flesch: 56 summary: You can put a deposit into a smart contract (and attach to the message proof that this deposit exists), where the deposit has the following rules: After a week the sender can take the deposit back The recipient can at any time reveal a hash (also included in the message) to destroy the sender’s deposit Recipients’ messaging clients can either only show messages that have a proof of deposit and hash as described above included, or can show such messages in a special color or above all other messages, or can otherwise highlight them (eg. one might allow anyone to publicly call them in a way that makes their phone ring, but only if this technique is used, so as to dissuade telemarketers and other spammers). For efficiency, one can batch many messages into a single contract by making a single contract with a Merkle tree root, and supplying the recipient of each message their hash along with the Merkle branch that they can use to prove to the contract that their hash is a member of the tree committed to by the contract. keywords: bet; vote cache: ethresear-3198.html plain text: ethresear-3198.txt item: #1367 of 3327 id: ethresear-3278 author: ethresear title: ethresear-3278 date: None words: 2010 flesch: 65 summary: Now…I’m not saying if that were true that would necessarily imply that you would still get token holders to curate things the way that you hope. Basically, my advice is at this point to, at least to start off, throw out the assumption that “token voting on anything” will be part of the design at all, and start off with a broader question: how can (crypto)economic incentives be used to improve on the status quo of wikis? keywords: content; state; token; wiki cache: ethresear-3278.html plain text: ethresear-3278.txt item: #1368 of 3327 id: ethresear-3497 author: ethresear title: ethresear-3497 date: None words: 161 flesch: 66 summary: Use the following paragraphs for a longer description, or to establish category guidelines or rules: Why should people use this category? About the EVM category - EVM - Ethereum Research Ethereum Research About the EVM category EVM virgil September 23, 2018, 12:03pm 1 (Replace this first paragraph with a brief description of your new category. keywords: category cache: ethresear-3497.html plain text: ethresear-3497.txt item: #1369 of 3327 id: ethresear-3524 author: ethresear title: ethresear-3524 date: None words: 168 flesch: 55 summary: Hey Everyone, I was looking for some statistics on the network overhead for individual nodes on the Ethereum network and couldn’t find any info outside of the latency info on ethstats.net. GitHub ethereum/go-ethereum Official Go implementation of the Ethereum protocol - ethereum/go-ethereum Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled keywords: ethereum cache: ethresear-3524.html plain text: ethresear-3524.txt item: #1370 of 3327 id: ethresear-3675 author: ethresear title: ethresear-3675 date: None words: 3381 flesch: 71 summary: Tx fees could be somewhat easy if each user opens a payment channel with operator with an entry fee, something like : Bob joins the side-chain and pays a 1$ entry fee and deposit 10$ for payment channel Bob submits a tx Operator include tx Bob sends sign messages with 0.01$ to the operator. If operator doesn’t include Bob transaction, Bob doesn’t send the sign message (and can exit if Bob is being censored). keywords: chain; data; october; operator; roll; state cache: ethresear-3675.html plain text: ethresear-3675.txt item: #1371 of 3327 id: ethresear-3751 author: ethresear title: ethresear-3751 date: None words: 2924 flesch: 64 summary: Optimizing sparse Merkle trees - Data Structure - Ethereum Research Ethereum Research Optimizing sparse Merkle trees Data Structure data-structure, sparse-merkle-tree vbuterin October 9, 2018, 10:47pm 1 A sparse Merkle tree (SMT) is a data structure useful for storing a key/value map which works as follows. However, these inefficiencies are largely illusory; it turns out that it is possible to optimize away most of the inefficiencies by building more complex client-side algorithms on top of sparse Merkle trees. keywords: merkle; proof; tree; value cache: ethresear-3751.html plain text: ethresear-3751.txt item: #1372 of 3327 id: ethresear-376 author: ethresear title: ethresear-376 date: None words: 5817 flesch: 62 summary: Adding shorting markets is super-hard for a few reasons. One way to get a constant stream of token prices would be whenever you call a function on that contract, the contract will get the token price through oracle and automatically adjust what the value of your position in ether. keywords: contract; eth; gexbot; market; price; seller; short; shorting; time; token cache: ethresear-376.html plain text: ethresear-376.txt item: #1373 of 3327 id: ethresear-3947 author: ethresear title: ethresear-3947 date: None words: 445 flesch: 39 summary: & All in all, I think simply recognizing the problem domain as “equity” in many instances (I am thinking in particular of “forced errors” in TrueBit) might be worthwhile. Sometimes I see (especially on Twitter, but sometimes here) exchanges that want for a very simple kicker — which, spoiler alert, is “equity.” keywords: equity; matters cache: ethresear-3947.html plain text: ethresear-3947.txt item: #1374 of 3327 id: ethresear-4009 author: ethresear title: ethresear-4009 date: None words: 1454 flesch: 60 summary: What is the number of malicious nodes, such that the situation where at least one shard having 51% or more malicious nodes occurs with probability p? For example, it would be important to know the number of malicious nodes such that there is a 50% chance of launching a 1% attack. keywords: nodes; shard cache: ethresear-4009.html plain text: ethresear-4009.txt item: #1375 of 3327 id: ethresear-4074 author: ethresear title: ethresear-4074 date: None words: 757 flesch: 64 summary: By finding ways of binding capabilities to existing patterns of thought for most people, e.g. human relations. I definitely any efforts at trying to get past these obstacles; we need secret sharing utilities that are not just for hackers. keywords: data; people cache: ethresear-4074.html plain text: ethresear-4074.txt item: #1376 of 3327 id: ethresear-4224 author: ethresear title: ethresear-4224 date: None words: 302 flesch: 66 summary: Python ETL does not (currently) support internal transactions and some other features, so I have interacted directly with the JSON RPC package via a geth node. It’s C++ code, but it extracts all the data (including internal transactions) and has a built in cache, So the second time you query, it’s way faster. keywords: data cache: ethresear-4224.html plain text: ethresear-4224.txt item: #1377 of 3327 id: ethresear-4228 author: ethresear title: ethresear-4228 date: None words: 2256 flesch: 62 summary: Here is another proposal ETH2 inactivity leak: a compromise proposal Casper Looks like many people are scared by the ETH2 inactivity leak. If finalization stops it will happen due to say network problems. keywords: leak; network; partition; time cache: ethresear-4228.html plain text: ethresear-4228.txt item: #1378 of 3327 id: ethresear-4279 author: ethresear title: ethresear-4279 date: None words: 1271 flesch: 61 summary: And even an FPGA based VDF based on regular silicon chips may be not so secure … kilic April 20, 2021, 1:43pm 9 I’ve implemented Wesolowski VDF verifier in solidity for 2048 bit RSA settings. We will look into it kelly April 23, 2021, 2:38pm 11 There is an RSA VDF verifier in Solidity here by @pvienhage : GitHub - 0xProject/VDF: A Solidity implementation of a VDF verifier contract pvienhage April 23, 2021, 3:17pm 12 It’s definitely not production ready though guthlStarkware April 26, 2021, 9:47am 13 VeeDoo is production ready. keywords: kladkogex; november; solidity; vdf cache: ethresear-4279.html plain text: ethresear-4279.txt item: #1379 of 3327 id: ethresear-4291 author: ethresear title: ethresear-4291 date: None words: 391 flesch: 67 summary: Prevent patents by allowing crawlers - Administrivia - Ethereum Research Ethereum Research Prevent patents by allowing crawlers Administrivia DennisPeterson November 17, 2018, 2:41pm 1 One way to help protect against software patents is to make sure posts are stored in Internet Archive, thus giving a reliable publish date. I just attempted to do that with a post, and it didn’t work because they won’t save anything that has a robot.txt prohibiting web crawlers. keywords: archive cache: ethresear-4291.html plain text: ethresear-4291.txt item: #1380 of 3327 id: ethresear-4325 author: ethresear title: ethresear-4325 date: None words: 405 flesch: 58 summary: The question is then, is it feasible to create a VDF by placing satellites on orbit? I think that would require trust assumptions involving where the satellites are I think the model could to have satellites independently owned by stakers, so that would be decentralized network of satellites. keywords: satellites cache: ethresear-4325.html plain text: ethresear-4325.txt item: #1381 of 3327 id: ethresear-4423 author: ethresear title: ethresear-4423 date: None words: 1017 flesch: 75 summary: EDIT: I guess a cache can be used per https://eprint.iacr.org/2016/683.pdf ? hkalodner November 29, 2018, 3:34pm 4 Somebody more familiar with sparse Merkle trees should correct me if I’m wrong, but I think the trick to make them efficient is to define a special hash value which is the hash of an empty subtree. Further, Merkle proofs can be compressed assuming that many of the hashes in the Merkle proof will be this special empty value. keywords: merkle; proof cache: ethresear-4423.html plain text: ethresear-4423.txt item: #1382 of 3327 id: ethresear-4481 author: ethresear title: ethresear-4481 date: None words: 1209 flesch: 56 summary: To make this possible, we introduce a concept of a depedency signature: a boolean formula over state roots in other shard (eg. (S_1, H_1, R_1)\ AND\ (S_2, H_2, R_2)\ AND\ NOT((S_3, H_3, R_3)))). A layer 2 computing model using optimistic state roots - Sharding - Ethereum Research Ethereum Research A layer 2 computing model using optimistic state roots Sharding layer-2 vbuterin December 5, 2018, 1:29pm 1 One of the problems that we face in the current sharding spec is the slowness of cross-shard communication. keywords: contract; shard; state cache: ethresear-4481.html plain text: ethresear-4481.txt item: #1383 of 3327 id: ethresear-4521 author: ethresear title: ethresear-4521 date: None words: 2418 flesch: 68 summary: New Beacon chain blocks are only processed by the Beacon chain clients if the new Beacon block also refers to an Ethereum 1.0 block, which is a child of the POS-finalized block. The Beacon chain needs to be aware of them, in order to make sure that the deposits into to Beacon chain are credited. keywords: beacon; block; chain; ethereum cache: ethresear-4521.html plain text: ethresear-4521.txt item: #1384 of 3327 id: ethresear-4566 author: ethresear title: ethresear-4566 date: None words: 2180 flesch: 61 summary: See his post on Economic Incentives for Validators and @vbuterin’s post on Average-case improvements to reduce validator costs for some background. Another thing that our small crew of law people is working on are various legal attack vectors that can be used by and/or against validators to essentially lock up staked funds, or otherwise put a cloud on their title. keywords: case; chain; december; ethereum; validators cache: ethresear-4566.html plain text: ethresear-4566.txt item: #1385 of 3327 id: ethresear-4602 author: ethresear title: ethresear-4602 date: None words: 2276 flesch: 63 summary: To construct the the protocol below, we first make the following assumptions: There is a set of relay nodes and their public keys \mathsf{relayNodes} to pick from known by the chain (which, just as in Tor, must be a Sybil-free set). One can attempt to construct protocols that rewards relay nodes for participating in the network and punishes or slashes nodes that are unreliable (e.g. this paper on proof-of-bandwidth for relays), this is a different but important topic. keywords: data; nodes cache: ethresear-4602.html plain text: ethresear-4602.txt item: #1386 of 3327 id: ethresear-4797 author: ethresear title: ethresear-4797 date: None words: 1369 flesch: 70 summary: But it may be important to secure large transactions, on-chain exchanges (DAI, wrapped BTC etc’) and smart contracts. How will people trust smart contracts once such attacks happen? flygoing January 14, 2019, 9:19pm 8 it won’t work with other chains Isn’t this irrelevant? keywords: january; transaction cache: ethresear-4797.html plain text: ethresear-4797.txt item: #1387 of 3327 id: ethresear-4808 author: ethresear title: ethresear-4808 date: None words: 3609 flesch: 61 summary: The rest will face difficulties to collect requirements because it needs some special knowledge about secure messaging protocols. Any thoughts? UPD: mainframe, uport, NuCypher are building own messaging solutions too. keywords: ethereum; january; messaging; people; projects; requirements; use; whisper cache: ethresear-4808.html plain text: ethresear-4808.txt item: #1388 of 3327 id: ethresear-4906 author: ethresear title: ethresear-4906 date: None words: 105 flesch: 39 summary: How we labelled one million Ethereum addresses - Data Science - Ethereum Research Ethereum Research How we labelled one million Ethereum addresses Data Science ecastano January 29, 2019, 12:59am 1 We used machine learning — specifically active learning, to automatically identify and label Ethereum addresses that, with a high probability, belong to exchanges. Medium – 28 Jan 19 How We Used Machine Learning To Label One Million Ethereum Addresses The TRM platform blends blockchain data with real-world data to help financial institutions stay compliant. keywords: ethereum cache: ethresear-4906.html plain text: ethresear-4906.txt item: #1389 of 3327 id: ethresear-4912 author: ethresear title: ethresear-4912 date: None words: 1820 flesch: 69 summary: The merkle root has tree index 1 if index == 1: return hash == root Doesn’t this make the verification return true if the first branch is correct, regardless of whether or not subsequent branches are correct? Optimizing Merkle tree multi-queries - Data Structure - Ethereum Research Ethereum Research Optimizing Merkle tree multi-queries Data Structure data-structure Recmo January 29, 2019, 11:30pm 1 Consider a Merkle tree of depth n where we want to proof m leaf values. keywords: merkle; proof; tree cache: ethresear-4912.html plain text: ethresear-4912.txt item: #1390 of 3327 id: ethresear-4929 author: ethresear title: ethresear-4929 date: None words: 279 flesch: 64 summary: Google Cloud Blog Ethereum in BigQuery: a Public Dataset for smart contract analytics d-ontmindme April 9, 2019, 11:22am 2 This could be created using BigQuery by checking for contract creations of contracts with the ERC20 Function Signatures. keywords: token cache: ethresear-4929.html plain text: ethresear-4929.txt item: #1391 of 3327 id: ethresear-4963 author: ethresear title: ethresear-4963 date: None words: 77 flesch: 68 summary: 2 Likes Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled Now running on CloudFlare - Administrivia - Ethereum Research Ethereum Research Now running on CloudFlare Administrivia virgil February 8, 2019, 1:13am 1 We’ve started using CloudFlare for ethresear.ch. keywords: cloudflare cache: ethresear-4963.html plain text: ethresear-4963.txt item: #1392 of 3327 id: ethresear-4970 author: ethresear title: ethresear-4970 date: None words: 3587 flesch: 60 summary: See Cross-shard contract yanking for some more discussion on this (“train and hotel problem” being common local jargon for this sort of thing). If the slot is too old, requires additional proofs to check that the proof was not already spent (see Cross-shard receipt and hibernation/waking anti-double-spending foe details). keywords: contract; cross; receipt; shard; transaction cache: ethresear-4970.html plain text: ethresear-4970.txt item: #1393 of 3327 id: ethresear-4981 author: ethresear title: ethresear-4981 date: None words: 1462 flesch: 70 summary: I would definitely support us including more data into receipts this time around, including logging all touched addresses. However, it’s clear that the architecture of ETH2.0 is noticeably different from that of ETH1.0; how will this likely affect data analysis projects like blockchain-etl? Most data analysis of this ilk requires one to parse through the whole state of a given blockchain from genesis and then transform that data into a more convenient format. keywords: addresses; data; quickblocks cache: ethresear-4981.html plain text: ethresear-4981.txt item: #1394 of 3327 id: ethresear-4997 author: ethresear title: ethresear-4997 date: None words: 124 flesch: 61 summary: Use the following paragraphs for a longer description, or to establish category guidelines or rules: Why should people use this category? This guidance will appear in the category selection area, so try to keep it below 200 characters.) keywords: category cache: ethresear-4997.html plain text: ethresear-4997.txt item: #1395 of 3327 id: ethresear-5031 author: ethresear title: ethresear-5031 date: None words: 391 flesch: 56 summary: We have four unrelated “messaging” projects in the works: There is gossipsub work for libp2p being handled entirely internally at Parity. As a rule, gossip protocols are never anonymous because they cannot provide cryptographic unlinkability. keywords: gossipsub; messaging cache: ethresear-5031.html plain text: ethresear-5031.txt item: #1396 of 3327 id: ethresear-5051 author: ethresear title: ethresear-5051 date: None words: 842 flesch: 63 summary: https://github.com/dogethereum/dogethereum-contracts In our recent paper (XCLAIM)[2] we provide a more detailed discussion of the security, functional requirements and practical challenges of chain relays for PoW blockchains: https://eprint.iacr.org/2018/643.pdf (Sec. V-B, Sec. VII-A,B,D and Appendix D). First, some details on PoW chain relays. keywords: chain; pos; pow cache: ethresear-5051.html plain text: ethresear-5051.txt item: #1397 of 3327 id: ethresear-5062 author: ethresear title: ethresear-5062 date: None words: 160 flesch: 51 summary: I am looking for a spec to implement threshold encrypt/decrypt using the same primitives and pairing used in BLS signatures. We already have BLS signatures implemented in a way compatible to precompiles from ETH 1.0. keywords: bls cache: ethresear-5062.html plain text: ethresear-5062.txt item: #1398 of 3327 id: ethresear-5085 author: ethresear title: ethresear-5085 date: None words: 1640 flesch: 66 summary: Since the node provides to the outside world no information about when the message m arrived, it is impossible for deterministic algorithms running on other nodes to differentiate between the cases of m arriving at T and T+1. Nodes can exchange messages, where each message is guaranteed to get delivered, but it may take an arbitrary long time for a message to get delivered. keywords: configuration; node cache: ethresear-5085.html plain text: ethresear-5085.txt item: #1399 of 3327 id: ethresear-5093 author: ethresear title: ethresear-5093 date: None words: 930 flesch: 60 summary: XCLAIM: Trustless, Interoperable Cryptocurrency-Backed Assets - Sharding - Ethereum Research Ethereum Research XCLAIM: Trustless, Interoperable Cryptocurrency-Backed Assets Sharding cross-shard alexeiZamyatin March 5, 2019, 5:39pm 1 We would like to introduce XCLAIM - a protocol for trustless cross-chain communication via cryptocurrency-backed assets. XCLAIM is a framework for achieving trustless and efficient cross-chain exchanges using cryptocurrency-backed assets (CbAs). keywords: isc; vault cache: ethresear-5093.html plain text: ethresear-5093.txt item: #1400 of 3327 id: ethresear-5153 author: ethresear title: ethresear-5153 date: None words: 3239 flesch: 61 summary: Until people evolve to using pure Holochain. I will definitely learn more about it, but there’s a reason why no major economy runs on mutual credit systems… we don’t trust each other when money is involved! keywords: credit; currency; fubuloubu; holochain; march; sybil cache: ethresear-5153.html plain text: ethresear-5153.txt item: #1401 of 3327 id: ethresear-5159 author: ethresear title: ethresear-5159 date: None words: 619 flesch: 54 summary: This incentivices to join mining pools as these get fees / rewards from all zones but an individual miner only get fees from a few zones. They provide some sort of remedy to this with the suggestion that mining pools can delegate the validation and creation of candidate blocks for each tone to their participants but they do not describe how to reach consensus between the delegates, if they delegate just to one node then that single node inherits the full power of the mining pool which he can use to start an attack on his zone. keywords: mining; sharding cache: ethresear-5159.html plain text: ethresear-5159.txt item: #1402 of 3327 id: ethresear-5169 author: ethresear title: ethresear-5169 date: None words: 2949 flesch: 56 summary: 1s) s (length of K) is 96*8 = 768 m is arbitrary and can be as little as 1 bit Legendre PRF The Legendre symbol \left(\frac{a}{p}\right) is defined as -1 if a is not a quadratic residue \pmod p 1 if a is a quadratic residue \pmod p except if a \cong 0 If multiplications in \mathbb{F}_p are cheaper than Legendre symbol evaluations, then this is potentially a nice optimisation (but probably not true for large p, as evaluating Legendre using quadratic reciprocity is probably quite cheap) keywords: custody; legendre; mpc; prf; secret cache: ethresear-5169.html plain text: ethresear-5169.txt item: #1403 of 3327 id: ethresear-5185 author: ethresear title: ethresear-5185 date: None words: 803 flesch: 71 summary: While this opens up a lot of possibilities, I guess some WASM-supporting languages will be much better for writing Serenity smart contracts than others: if for nothing else, because of the idiosyncrasies of eWASM compared to WASM; because of the (non-)existence of compilers and their quality/developer base (see the current state of WASM compilers); because of the idiosyncrasies of the languages. EVM leafcutterant March 19, 2019, 6:29pm 1 It would be interesting to discuss what languages do we expect/want/recommend people to use for writing smart contracts for Ethereum 2.0. keywords: ewasm; languages cache: ethresear-5185.html plain text: ethresear-5185.txt item: #1404 of 3327 id: ethresear-52 author: ethresear title: ethresear-52 date: None words: 2748 flesch: 61 summary: In terms of how often validators propose blocks, I did some quick sums (assumes all validators have an equal 32 ETH stake): seconds per year: 31,557,600 31,557,600 / 12 secs per block = 2,629,800 blocks per year 2,629,800 / 418,538 active validators = 6.28 blocks per year per validator It wasn’t set to 32 ETH because anyone wanted to keep small validators out. keywords: august; eth; node; return; validators cache: ethresear-52.html plain text: ethresear-52.txt item: #1405 of 3327 id: ethresear-5269 author: ethresear title: ethresear-5269 date: None words: 5936 flesch: 58 summary: The entire set of state changes in a crosslink would be small enough that it could simply be included as part of crosslink data, so the crosslink data would just specify all changes to execution environment state. Take the example of zk-rollup, which is constrained by data availability. keywords: availability; chain; data; ethereum; execution; phase; shard; state cache: ethresear-5269.html plain text: ethresear-5269.txt item: #1406 of 3327 id: ethresear-5318 author: ethresear title: ethresear-5318 date: None words: 1281 flesch: 51 summary: Chosen leader signs the previous randomness source with BLS single signature to generate the new randomness source, creates a block with transactions, adds the new randomness source in the block header and broadcasts this block to consensus group members; Each member validates the block, also validating that the new randomness source is a signature verifiable with the leader’s public key on the old randomness source. This would mean that we have a consensus that uses aggregated BLS multi-signature as block signature to prove the consensus was reached, and single BLS signature from the leader of the consensus over the last randomness source providing the next randomness source. keywords: consensus; signature cache: ethresear-5318.html plain text: ethresear-5318.txt item: #1407 of 3327 id: ethresear-5337 author: ethresear title: ethresear-5337 date: None words: 2841 flesch: 59 summary: To simplify things, instead of considering separate state roots for each shard, we talk about global state roots, which are root hashes of the state roots for each shard (ie. merkle_root([get_state_root(shard=0), ... , get_state_root(shard=SHARD_COUNT-1)])). We assume the beacon chain computes and saves these global state roots with a delay or roughly 1-2 epochs in the normal case but potentially longer (they can be computed from crosslink data once crosslinks for all shards are submitted); once the beacon chain has calculates global state roots up to some height, all shards have access to these roots. keywords: coins; dependency; shard; state; transaction cache: ethresear-5337.html plain text: ethresear-5337.txt item: #1408 of 3327 id: ethresear-5338 author: ethresear title: ethresear-5338 date: None words: 1601 flesch: 65 summary: This contract needs modifiers which will only allow numbers between 1 and 9999999 to be set for each position // Returns 1111111 function getPosition1() public view returns(uint256){ return ((value % (10 ** 7)) - (value % (10 ** (7 - 7)))) / (10 ** (7 - 7)); } // Returns 2222222 function getPosition2() public view returns(uint256){ return ((value % (10 ** 14)) - (value % (10 ** (14 - 7)))) / (10 ** (14 - 7)); } // Returns 3333333 function getPosition3() public view returns(uint256){ return ((value % (10 ** 21)) - (value % (10 ** (21 - 7)))) / (10 ** (21 - 7)); } //Returns 4444444 function getPosition4() public view returns(uint256){ return ((value % (10 ** 28)) - (value % (10 ** (28 - 7)))) / (10 ** (28 - 7)); } // Returns 5555555 function getPosition5() public view returns(uint256){ return ((value % (10 ** 35)) - (value % (10 ** (35 - 7)))) / keywords: function; return; value cache: ethresear-5338.html plain text: ethresear-5338.txt item: #1409 of 3327 id: ethresear-5348 author: ethresear title: ethresear-5348 date: None words: 1904 flesch: 63 summary: On shard level we accept a maximum of 33% of malicious nodes. The leader of the current block signs the random seed of the previous block with his private key, using BLS single signature scheme, that number is hashed and becomes the random seed for the next group selection; BLS single signature — a signed message with a private key result is fixed; Block finality: block N is final only if block N-1, block N-2 … block N-K are signed. keywords: block; nodes; shard cache: ethresear-5348.html plain text: ethresear-5348.txt item: #1410 of 3327 id: ethresear-5373 author: ethresear title: ethresear-5373 date: None words: 268 flesch: 53 summary: Ethereum Governance Survey - Data Science - Ethereum Research Ethereum Research Ethereum Governance Survey Data Science eva April 26, 2019, 7:59pm 1 I’ve created an Ethereum Governance Survey to gain more accurate data on the community’s perspectives on Ethereum governance (to capture the quiet majority as well as the loud minority). Recently, Ethereum governance has come under greater scrutiny as the need for coordination between disparate stakeholders has become more... keywords: ethereum cache: ethresear-5373.html plain text: ethresear-5373.txt item: #1411 of 3327 id: ethresear-5378 author: ethresear title: ethresear-5378 date: None words: 124 flesch: 62 summary: Use the following paragraphs for a longer description, or to establish category guidelines or rules: Why should people use this category? About the Cryptography category - Cryptography - Ethereum Research Ethereum Research About the Cryptography category Cryptography liangcc April 28, 2019, 7:15am 1 (Replace this first paragraph with a brief description of your new category. keywords: category cache: ethresear-5378.html plain text: ethresear-5378.txt item: #1412 of 3327 id: ethresear-5379 author: ethresear title: ethresear-5379 date: None words: 44 flesch: 31 summary: About the Consensus category - Consensus - Ethereum Research Ethereum Research About the Consensus category Consensus liangcc April 28, 2019, 7:19am 1 Distributed System, Fault tolerance, Liveness, Safety, etc. Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled keywords: consensus cache: ethresear-5379.html plain text: ethresear-5379.txt item: #1413 of 3327 id: ethresear-5380 author: ethresear title: ethresear-5380 date: None words: 130 flesch: 66 summary: Use the following paragraphs for a longer description, or to establish category guidelines or rules: Why should people use this category? This guidance will appear in the category selection area, so try to keep it below 200 characters.) keywords: category cache: ethresear-5380.html plain text: ethresear-5380.txt item: #1414 of 3327 id: ethresear-5382 author: ethresear title: ethresear-5382 date: None words: 51 flesch: 35 summary: About the Layer 2 category - Layer 2 - Ethereum Research Ethereum Research About the Layer 2 category Layer 2 liangcc April 28, 2019, 8:00am 1 Topics that do not fit into Plasma and State Channel Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled keywords: layer cache: ethresear-5382.html plain text: ethresear-5382.txt item: #1415 of 3327 id: ethresear-5402 author: ethresear title: ethresear-5402 date: None words: 1565 flesch: 68 summary: We show how to create timelock puzzles targetting RSA VDF ASICs with a hardcoded modulus. Context A key design decision for RSA VDF ASICs is whether or not the modulus should be hardcoded or programmable. keywords: modulus; rsa; timelock cache: ethresear-5402.html plain text: ethresear-5402.txt item: #1416 of 3327 id: ethresear-5413 author: ethresear title: ethresear-5413 date: None words: 5556 flesch: 61 summary: If this is public I can use my withdrawal transaction from public key x as evidence to a briber that I did not update my key at any time during the Vote. That is, given the stream of encrypted messages that are handled as you describe by the operator, there is a zero-knowledge proof that some correctly-signed votes and key-changes exist that make the alleged output and encrypt to the given messages; but given the stream of encrypted messages that I described, there is not a proof that some votes and some set of secret keys exist with that property? keywords: k_i; key; operator; public; user; vote cache: ethresear-5413.html plain text: ethresear-5413.txt item: #1417 of 3327 id: ethresear-5434 author: ethresear title: ethresear-5434 date: None words: 874 flesch: 63 summary: Eth1.0 as shard 0 of the Beacon chain - Economics - Ethereum Research Ethereum Research Eth1.0 as shard 0 of the Beacon chain Proof-of-Stake Economics josojo May 10, 2019, 5:39am 1 As the Eth1.0 finalization working group is forming, I would like to investigate the technical pro and cons of introducing full POS to Eth1.0 by making Eth1.0 a shard of the Beacon chain. POS would offer better security and finalization to the Eth1.0 chain As Beacon chain clients anyways need to be aware of the eth1.0 chain, there is no substantial additional load on the clients. keywords: chain; eth1.0 cache: ethresear-5434.html plain text: ethresear-5434.txt item: #1418 of 3327 id: ethresear-5451 author: ethresear title: ethresear-5451 date: None words: 364 flesch: 43 summary: To quote from the btcrelay repo: “the hurdle is when BTC Relay is generating “revenue”, then relayers will want a piece for it and will continue relaying, but to get “revenue” BTC Relay needs to be current with the Bitcoin blockchain and needs the relayers first” How it works (taken from ZBTC) Stateless SPV approximates the finality of a transaction based on its accumulated difficulty. This approach is rather bespoke - due to the simplicity of Bitcoin’s consensus algorithm, and the network effect of its hashpower, stateless SPV is seemingly secure. keywords: security cache: ethresear-5451.html plain text: ethresear-5451.txt item: #1419 of 3327 id: ethresear-5455 author: ethresear title: ethresear-5455 date: None words: 633 flesch: 69 summary: However, especially interested in optimize performance for using AI model in smart contract. Whether the model can still be updated after the contract is deployed? Is SKALE sidechain based on zero-knowledge proofs and how does it achieve correctness? iswarm May 4, 2022, 2:45am 14 Running precompiled some AI inference is Very interesting. keywords: image cache: ethresear-5455.html plain text: ethresear-5455.txt item: #1420 of 3327 id: ethresear-5503 author: ethresear title: ethresear-5503 date: None words: 2207 flesch: 55 summary: Maybe this would allow consistent bootstrapping at any height if block data is lost (maybe carrying succinct state forward in time). Maybe this would allow consistent bootstrapping at any height if block data is lost (maybe carrying succinct state forward in time). keywords: availability; block; chain; data cache: ethresear-5503.html plain text: ethresear-5503.txt item: #1421 of 3327 id: ethresear-5511 author: ethresear title: ethresear-5511 date: None words: 2044 flesch: 71 summary: With roll ups and lots of other zk applications coming down the road it would seem to make sense to focus on hash functions that are optimal for running in circuits. A nearly-trivial-on-zero-inputs 32-bytes-long collision-resistant hash function - Data Structure - Ethereum Research Ethereum Research A nearly-trivial-on-zero-inputs 32-bytes-long collision-resistant hash function Data Structure sparse-merkle-tree vbuterin May 25, 2019, 3:33pm 1 Problem statement: for use cases like Optimizing sparse Merkle trees, create a hash function H(l, r) = x where l, r and x are 32 byte values that is (i) collision-resistant and (iii) trivial to compute if l = 0 or r = 0. keywords: 2^{240; case; hash cache: ethresear-5511.html plain text: ethresear-5511.txt item: #1422 of 3327 id: ethresear-5519 author: ethresear title: ethresear-5519 date: None words: 2597 flesch: 57 summary: This creates a picture of the beacon chain as a set of noninteracting streams of contract calls, and each stream is part of a shard. This gives a kind of static interaction among contracts (“shards”): transaction messages would be able to write programs that call contracts, call pure functions on the results, and call other contracts with those results, so long as no jumps are allowed, so that we can still identify which contracts are affected. keywords: block; consensus; contract; stage cache: ethresear-5519.html plain text: ethresear-5519.txt item: #1423 of 3327 id: ethresear-5543 author: ethresear title: ethresear-5543 date: None words: 2018 flesch: 59 summary: For many hash tree constructions proof of non-membership and proof of insertion look the same (except that the proof of insertion specifies the value to insert). My implementation (currently used by crypto.com’s implementation of their own chain) of a similar idea (compressing chains of branches to a single node) can swap out hash functions for internal store keying and external facing hashes (they are really the same, the root is just another address in the tree). keywords: hash; key; leaf cache: ethresear-5543.html plain text: ethresear-5543.txt item: #1424 of 3327 id: ethresear-5555 author: ethresear title: ethresear-5555 date: None words: 500 flesch: 80 summary: Alice gives Bob her BTC address, and tells Bob where their Ethereum Atomic Swap Contract is. If Alice does not retrieve the BTC within 6 hours, Bob can claim it. keywords: bob cache: ethresear-5555.html plain text: ethresear-5555.txt item: #1425 of 3327 id: ethresear-5556 author: ethresear title: ethresear-5556 date: None words: 301 flesch: 45 summary: The authors have burried a critical caveat in footnote 2: we can only guarantee that the (\epsilon \cdot t)-th value into the future is unpredictable So basically an attacker with non-zero speed advantage relative to honest players has linearly growing lookahead over time. The authors demonstrate three potential applications, the most interesting one probably being the construction of public randomness beacons that only require an initial random seed (and no further unpredictable sources of randomness). keywords: vdfs cache: ethresear-5556.html plain text: ethresear-5556.txt item: #1426 of 3327 id: ethresear-5570 author: ethresear title: ethresear-5570 date: None words: 507 flesch: 54 summary: New humans earn voting tokens, which can then be used to vote on new applicants. New humans earn voting tokens, which can then be used to vote on new applicants. keywords: consensus; humans cache: ethresear-5570.html plain text: ethresear-5570.txt item: #1427 of 3327 id: ethresear-5677 author: ethresear title: ethresear-5677 date: None words: 814 flesch: 62 summary: Security reductions are unacceptable for currency-functional chains and user reductions are hardly acceptable for public chains. The second debate: Chain, BFT,DPoS or DAG? As far as I know, there are two ways to choose validators in all consensus systems: through competition (e.g. more hashpower or more stakes) or through cooperation (e.g. delegated by stakeholders). keywords: chain; design cache: ethresear-5677.html plain text: ethresear-5677.txt item: #1428 of 3327 id: ethresear-5719 author: ethresear title: ethresear-5719 date: None words: 1259 flesch: 68 summary: At this point, it is entirely possible for the winner to be a member of a completely out of band coalition of lottery ticket participants who have been forced or tricked into giving up their winnings should they be selected. Node delays for a while according to Wm, then create and broadcast new block if no block with higher weight arrives. keywords: block; july; lottery cache: ethresear-5719.html plain text: ethresear-5719.txt item: #1429 of 3327 id: ethresear-5721 author: ethresear title: ethresear-5721 date: None words: 652 flesch: 59 summary: dType (Decentralized Type System) on Ethereum 2.0 - Architecture - Ethereum Research Ethereum Research dType (Decentralized Type System) on Ethereum 2.0 Architecture new-extension, cross-shard loredanacirstea July 10, 2019, 9:16am 1 dType (Decentralized Type System) on Ethereum 2.0 This discussion is an ongoing effort to research possible implementations for dType on the future Ethereum 2.0. Examples: global ML and AI systems, blockchain explorers that present chain data in rich formats, based on dType types. keywords: dtype; ethereum cache: ethresear-5721.html plain text: ethresear-5721.txt item: #1430 of 3327 id: ethresear-5730 author: ethresear title: ethresear-5730 date: None words: 1542 flesch: 66 summary: Conclusions avoids redeployment of libraries and contracts to multiple shards cross-shard transactions will be faster if read data is cached there are gas costs to caching data which should be clarified in more detail 2 Likes dType (Decentralized Type System) on Ethereum 2.0 On-Chain Non-Interactive Data Availability Proofs Libra EE and Shadow Shard (and general cross-chain data bridging) Type Control Execution Environment (EEt) with Formality vbuterin July 13, 2019, 3:22am 2 I’ve definitely supported the idea of allowing contracts on the beacon chain to exist as static libraries/data stores that could be accessed from shards before; some of my proposed phase2 specs even already contain that functionality. Calls to MS will be faster and cheaper than calls to other shards. keywords: data; shard cache: ethresear-5730.html plain text: ethresear-5730.txt item: #1431 of 3327 id: ethresear-5820 author: ethresear title: ethresear-5820 date: None words: 1731 flesch: 69 summary: We need a way for relayers to advertize their willingess to pay for a transaction. So a user should be able to select relayers and have high confidence that they will actually broadcast a transaction. keywords: contract; relayer; transaction cache: ethresear-5820.html plain text: ethresear-5820.txt item: #1432 of 3327 id: ethresear-5831 author: ethresear title: ethresear-5831 date: None words: 284 flesch: 62 summary: Cross-chain DEXs are difficult to build due to the varying consensus algorithms and security requirements of each blockchain. I suggest a minimal architecture allowing cryptocurrencies to be exchanged without funds going through any third party by utilizing a light-weight system of collaterals smart contracts. keywords: ethereum cache: ethresear-5831.html plain text: ethresear-5831.txt item: #1433 of 3327 id: ethresear-5851 author: ethresear title: ethresear-5851 date: None words: 1940 flesch: 71 summary: and they are insentivized to extract as much funds as possible in the form of transaction fees. So the 1,000,000 gas of transactions would have to result in more transaction fees than bigger_block_burn in order to win the auction. keywords: auction; august; block; transaction cache: ethresear-5851.html plain text: ethresear-5851.txt item: #1434 of 3327 id: ethresear-5859 author: ethresear title: ethresear-5859 date: None words: 749 flesch: 69 summary: This eliminates the lock time after atomic swap transactions of both sides are set. A new type of atomic swap on PoS chains with a merkle patricia tree, which can be completed without communications like submitting a preimage of blankhash. keywords: swap cache: ethresear-5859.html plain text: ethresear-5859.txt item: #1435 of 3327 id: ethresear-5862 author: ethresear title: ethresear-5862 date: None words: 397 flesch: 59 summary: Question of bls signature - Miscellaneous - Ethereum Research Ethereum Research Question of bls signature Miscellaneous signature-aggregation yyyyyp July 23, 2019, 8:23am 1 Can you tell me the progress of BLS signature. Actually a signing involves a single exponentiation in a field, so it is not so expensive … yyyyyp August 16, 2019, 2:45am 9 Validation time may be more important than signature time because it involves pairing. keywords: august cache: ethresear-5862.html plain text: ethresear-5862.txt item: #1436 of 3327 id: ethresear-5879 author: ethresear title: ethresear-5879 date: None words: 299 flesch: 68 summary: After my research I found a solution how to create such CA and implement Ethereum TLS. It makes Ethereum UX incomplete and ENS itself not a real NS. keywords: ethereum cache: ethresear-5879.html plain text: ethresear-5879.txt item: #1437 of 3327 id: ethresear-5885 author: ethresear title: ethresear-5885 date: None words: 2116 flesch: 56 summary: Block headers now contain three (3) data roots: ordered inputs ordered outputs ordered transactions Ordered Merkle trees can be used as they allow us to prove non-inclusion with two adjacent Merkle branches, though SMTs may be used for more efficient block template generation without having to re-compute the whole trees (and are conveniently ordered by definition). For the transaction, the fraud proof provides: A witness that the transaction exists in the list of ordered transactions for the current block. keywords: block; fraud; state; transactions cache: ethresear-5885.html plain text: ethresear-5885.txt item: #1438 of 3327 id: ethresear-5887 author: ethresear title: ethresear-5887 date: None words: 624 flesch: 65 summary: Maker fees are defined by a continuous function which is not only proportional to the order amount, but also inversely proportional to: How far in the future the order is locked. There is one Fee Pool per order book. keywords: fee; order cache: ethresear-5887.html plain text: ethresear-5887.txt item: #1439 of 3327 id: ethresear-5899 author: ethresear title: ethresear-5899 date: None words: 872 flesch: 56 summary: While data availability proofs with random sampling can be done, those are subjective and can’t be run on-chain (well, at least not easily). Using Ethereum as a Data Availability Layer Before discussing Ethereum as a data availability layer, we must first understand how side chains work (or rather, don’t work). keywords: chain; data; ethereum cache: ethresear-5899.html plain text: ethresear-5899.txt item: #1440 of 3327 id: ethresear-5926 author: ethresear title: ethresear-5926 date: None words: 748 flesch: 50 summary: Given that many of the voting functions used in PoS protocols are not simply \mathsf{Maj}_n but are instead recursive voting functions (e.g. \mathsf{Maj}^{\otimes 3}_{3^n}) or stake-weighted linear threshold functions, there is significant room to engineer the precise voting function to allow for optimistic confirmation. In voting theory and the Fourier-Walsh analysis of boolean functions, there are precise tools for quantifying the size of juntas and cartels and there are some important results like Friedgut’s Junta Theorem that affect voting-based protocols. keywords: confirmation; function; voting cache: ethresear-5926.html plain text: ethresear-5926.txt item: #1441 of 3327 id: ethresear-5952 author: ethresear title: ethresear-5952 date: None words: 762 flesch: 52 summary: Deterministic Finality for Blockchain using Hashgraph-like construct - Consensus - Ethereum Research Ethereum Research Deterministic Finality for Blockchain using Hashgraph-like construct Consensus guruhubb August 11, 2019, 6:50pm 1 If a protocol doesn’t require explicit endorsement of a block to reach consensus and just rely on other factors such as PoW, it is possible to disclose blocks much later and alter the course. Immediate direct interaction ensures consensus is discovered quickly and it will not be possible to release blocks at a later time. keywords: block; round cache: ethresear-5952.html plain text: ethresear-5952.txt item: #1442 of 3327 id: ethresear-5987 author: ethresear title: ethresear-5987 date: None words: 200 flesch: 68 summary: How committee size for shards is determined: Medium – 15 Jul 19 Minimum Committee Size Explained How many validators sampled can make a committee safe? Reading time: 4 min read How to bribe said committee: keywords: august cache: ethresear-5987.html plain text: ethresear-5987.txt item: #1443 of 3327 id: ethresear-6007 author: ethresear title: ethresear-6007 date: None words: 2122 flesch: 63 summary: The main long-term issue with EAuth is that it expects ECDSA wallets, and does not support smart contract wallets. Slock’s proposal of historical txfees paid) and use those balances as an anti-sybil mechanism In the longer term, more security, as smart contract wallets could implement more advanced multisig-based account recovery setups that could outcompete centralized providers’ offerings. keywords: august; ethereum; key; wallet cache: ethresear-6007.html plain text: ethresear-6007.txt item: #1444 of 3327 id: ethresear-6019 author: ethresear title: ethresear-6019 date: None words: 124 flesch: 64 summary: Use the following paragraphs for a longer description, or to establish category guidelines or rules: Why should people use this category? This guidance will appear in the category selection area, so try to keep it below 200 characters.) keywords: category cache: ethresear-6019.html plain text: ethresear-6019.txt item: #1445 of 3327 id: ethresear-6064 author: ethresear title: ethresear-6064 date: None words: 1065 flesch: 12 summary: The multi-level sort order is by type then by name. You can paste the raw text of any of these unsorted mixed up ERC20 ABIs, or the official ERC20 ABI from the Ethereum Wiki, and the resulting hash (for the official ERC20 ABI) will always be 0xfa9452aa0b9ba0bf6eb59facc534adeb90d977746f96b1c4ab2db01722a2adcb. keywords: inputs; type cache: ethresear-6064.html plain text: ethresear-6064.txt item: #1446 of 3327 id: ethresear-6111 author: ethresear title: ethresear-6111 date: None words: 1386 flesch: 41 summary: For example, if stateless contracts at layer 2 are going to be used regardless, then one might as well make layer-1 state extremely expensive to effectively mandate such layer-2 schemes, so as to keep state small to prevent the possibility that stateless clients will ever be also needed to be built at layer 1. They could also be used at application layer, by using a transaction packaging mechanism where many transactions are submitted inside of one package, a single signature checker verifies the signature against the hashes of all the transactions and the pubkeys of their declared senders, and then from then on transactions are executed separately. keywords: clients; layer; state cache: ethresear-6111.html plain text: ethresear-6111.txt item: #1447 of 3327 id: ethresear-6113 author: ethresear title: ethresear-6113 date: None words: 1061 flesch: 44 summary: Analysis of bouncing attack on FFG - Proof-of-Stake - Ethereum Research Ethereum Research Analysis of bouncing attack on FFG Proof-of-Stake nrryuya September 8, 2019, 2:08am 1 TL;DR In this post, I dig into the bouncing attack on Casper FFG, which is already known to potentially make a permanent liveness failure of FFG. Prerequisites: Casper FFG paper Background: Bouncing attack In Casper FFG, the fork-choice rule must start from the latest justified checkpoint. keywords: attacker cache: ethresear-6113.html plain text: ethresear-6113.txt item: #1448 of 3327 id: ethresear-6153 author: ethresear title: ethresear-6153 date: None words: 175 flesch: 48 summary: (Although at current MAX_EFFECTIVE_BALANCE is somewhat overloaded in that it is also used to ascertain when validators can be activated and how much can be transferred out of an active validator so if this change were implemented there would need to be two parameters rather than the current one). Max_effective_balance - Economics - Ethereum Research Ethereum Research Max_effective_balance Proof-of-Stake Economics jgm September 17, 2019, 10:21am 1 Is there a particular reason that MAX_EFFECTIVE_BALANCE is set to 32 ETH? keywords: max_effective_balance cache: ethresear-6153.html plain text: ethresear-6153.txt item: #1449 of 3327 id: ethresear-6191 author: ethresear title: ethresear-6191 date: None words: 774 flesch: 65 summary: This proposal also fails to understand the fundamental reason why mining empty blocks on Ethereum is different than on Bitcoin: Ethereum blocks include a state root, so rewards and collected fees must be committed to in the block header, which requires having validated the previous block. A proposal to alleviate the empty block problem - EVM - Ethereum Research Ethereum Research A proposal to alleviate the empty block problem EVM kladkogex September 24, 2019, 5:33pm 1 If you look at ETH block explorer you see that some pools like Spark Pool are producing empty blocks. keywords: block; transactions cache: ethresear-6191.html plain text: ethresear-6191.txt item: #1450 of 3327 id: ethresear-6208 author: ethresear title: ethresear-6208 date: None words: 412 flesch: 67 summary: Using Ethereum Classic (ETC) as a trustless gateway to ETH2.0 - Miscellaneous - Ethereum Research Ethereum Research Using Ethereum Classic (ETC) as a trustless gateway to ETH2.0 Miscellaneous Mikerah September 27, 2019, 12:14am 1 Using ETC as a trustless gateway to ETH2.0 Currently, the planned method to becoming a validator in ETH2.0 is to deposit 32 ETH into a smart contract on the ETH1.x chain. I’m propose a way in which, as a community, we can use to onboard users and developers to ETH2.0 using Ethereum Classic. keywords: ethereum cache: ethresear-6208.html plain text: ethresear-6208.txt item: #1451 of 3327 id: ethresear-6214 author: ethresear title: ethresear-6214 date: None words: 4822 flesch: 68 summary: Unlike FRI, Kate or other polynomial commitments don’t give you the Merkle tree, so if you wanted to have a smaller proof with an updatable trusted setup, you’d probably still want to use a similar construction i.e. with a SNARK that shows both that the polynomial is low degree and that the Merkle tree hashes are correct. vbuterin October 1, 2019, 5:05am 3 a SNARK that shows both that the polynomial is low degree and that the Merkle tree hashes are correct. keywords: data; degree; fri; polynomial; values cache: ethresear-6214.html plain text: ethresear-6214.txt item: #1452 of 3327 id: ethresear-6219 author: ethresear title: ethresear-6219 date: None words: 728 flesch: 67 summary: Proposal for efficient combinatorial optimisation in smart contracts - Miscellaneous - Ethereum Research Ethereum Research Proposal for efficient combinatorial optimisation in smart contracts Miscellaneous new-extension troelsfr September 29, 2019, 7:49pm 1 TL;DR This post discusses a programmable mechanism to enable smart contracts to optimise hard problems. To enable combinatorial optimisation in smart contract, we create two new Merkle trees associated with the block. keywords: problem; solution cache: ethresear-6219.html plain text: ethresear-6219.txt item: #1453 of 3327 id: ethresear-6232 author: ethresear title: ethresear-6232 date: None words: 1525 flesch: 67 summary: Thanks! 4 Likes pEthereum - privacy mode for smart contracts & integration with DeFi vbuterin October 3, 2019, 7:17am 2 Is this just a two-way atomic swap system, with the Incognito blockchain itself supporting ZK transfers internally? 3 Likes duy October 3, 2019, 8:30am 3 – re: atomic swap system it’s actually a two-way relay bridge that lets you transfer assets from ethereum to incognito and vice versa. Other * contracts can query this contract to check if an instruction is confimed on * Incognito */ contract IncognitoProxy is AdminPausable { struct Committee { address keywords: contract; ethereum; incognito; validators cache: ethresear-6232.html plain text: ethresear-6232.txt item: #1454 of 3327 id: ethresear-6248 author: ethresear title: ethresear-6248 date: None words: 3317 flesch: 64 summary: With net cyclic preference it is impossible to satisfy the rule of orders below clearing prices having to be fully executed. In contrast to “normal” orderbook (continues double auction) dexs where trades are executed continuously, batch auctions collect orders into a batch (discrete time) and then calculate a “single clearing price” and which all orders are executed. keywords: batch; orders; price; utility cache: ethresear-6248.html plain text: ethresear-6248.txt item: #1455 of 3327 id: ethresear-6257 author: ethresear title: ethresear-6257 date: None words: 450 flesch: 67 summary: image1474×882 73.7 KB Example: Using Ethereum as exapmle, suppose W = 1000, S = 200, T = 15, and price per ETH is P = 180 USD, the attacking cost of reverting a blocked generated 5 mins ago (about 20 block confirmations) with staking will be about 20 \times S \times P = 20 \times 200 \times 180 = 720,000 USD, while the upper limit of attacking cost without staking is about 2 \times 20 \times P = 7,200 USD. Note that the staked tokens will be locked much longer than the production time of W blocks to prevent transfer-and-stake cheat. keywords: cost cache: ethresear-6257.html plain text: ethresear-6257.txt item: #1456 of 3327 id: ethresear-6262 author: ethresear title: ethresear-6262 date: None words: 233 flesch: 46 summary: #SCSVS - Smart Contract Security Verification Standard is a FREE 13-part checklist created to standardize the security of smart contracts for developers, architects, security reviewers and vendors. SCSVS - Smart Contract Security Verification Standard - Security - Ethereum Research Ethereum Research SCSVS - Smart Contract Security Verification Standard Security drdr October 9, 2019, 10:02am 1 Together with my colleague Paweł Kuryłowicz we have created the Smart Contract Security Verification Standard which we published on the 1st of October. keywords: security cache: ethresear-6262.html plain text: ethresear-6262.txt item: #1457 of 3327 id: ethresear-6268 author: ethresear title: ethresear-6268 date: None words: 3198 flesch: 60 summary: 1 Like spengrah October 10, 2019, 4:54pm 7 Some open questions… Does the Ethereum community value Eth2 levels of transaction throughput more than atomic contract composability? spengrah: Some open questions… Does the Ethereum community value Eth2 levels of transaction throughput more than atomic contract composability? keywords: composability; contract; october; shard; transaction; uniswap cache: ethresear-6268.html plain text: ethresear-6268.txt item: #1458 of 3327 id: ethresear-6287 author: ethresear title: ethresear-6287 date: None words: 729 flesch: 63 summary: We also create N other contracts on other shards, called sequencers. Enhancements The most obvious problem with this proposal as written above is that it requires receipts from sequencers to be explicitly included, and block proposers on the executor shard could manipulate this for profit. keywords: executor; shard cache: ethresear-6287.html plain text: ethresear-6287.txt item: #1459 of 3327 id: ethresear-6325 author: ethresear title: ethresear-6325 date: None words: 304 flesch: 38 summary: It provides fairly rigorous definitions of game theoretic notions useful for study of incentives in protocols. A large part of it is devoted to the study of incentive schemes - something that might be useful in the fine-tuning phase of protocol development. keywords: mechanisms cache: ethresear-6325.html plain text: ethresear-6325.txt item: #1460 of 3327 id: ethresear-6362 author: ethresear title: ethresear-6362 date: None words: 105 flesch: 27 summary: Open research problems - Miscellaneous - Ethereum Research Ethereum Research Open research problems Miscellaneous szhygulin October 21, 2019, 11:00pm 1 Hi there, Is there any updated comprehensive list of open problems you guys currently working on or planning to work on? dankrad November 5, 2019, 4:27pm 2 It of course depends on what kind of research problems you are interested in, but one resource that we just put online is challenges.ethereum.org, which lists all the different bounties we have to encourage research in topics critical to the future of Ethereum. Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled keywords: research cache: ethresear-6362.html plain text: ethresear-6362.txt item: #1461 of 3327 id: ethresear-6382 author: ethresear title: ethresear-6382 date: None words: 1470 flesch: 58 summary: Though cross-shard transactions in general are possible through application of the usual receipt mechanism, with the protocol itself needing only to provide access to each shard’s state roots to each other shard, cross-shard ETH requires a little more enshrined in-protocol activity. After a day, receipts could be pruned into a separate root and witnesses would need to be submitted akin to what we assumed before (waking mechanism - Cross-shard receipt and hibernation/waking anti-double-spending). keywords: cross; receipt; shard cache: ethresear-6382.html plain text: ethresear-6382.txt item: #1462 of 3327 id: ethresear-6386 author: ethresear title: ethresear-6386 date: None words: 669 flesch: 63 summary: However, they’re compiled bytecodes(with v0.5.11) are same as below(except code hash obviously) If you look at the ABI specification, it does seem like the two events you defined in contract A and contract B are exactly the same type, as the indexed and non-indexed parameters are listed separately. If you look at the ABI specification, it does seem like the two events you defined in contract A and contract B are exactly the same type, as the indexed and non-indexed parameters are listed separately. keywords: contract; event cache: ethresear-6386.html plain text: ethresear-6386.txt item: #1463 of 3327 id: ethresear-6428 author: ethresear title: ethresear-6428 date: None words: 118 flesch: 62 summary: Can we get a category made for this? 3 Likes hwwhww November 10, 2019, 5:36am 2 There is now Eth1.x Research category (https://ethresear.ch/c/eth1x-research) plus stateless-client tag (https://ethresear.ch/tags/stateless-client). Eth 1.x Stateless Clients Administrivia pipermerriam November 8, 2019, 3:38pm 1 I’m starting to organize an Eth 1.x research group around the topic of stateless clients in the context of the 1.0 mainnet. keywords: category cache: ethresear-6428.html plain text: ethresear-6428.txt item: #1464 of 3327 id: ethresear-6429 author: ethresear title: ethresear-6429 date: None words: 94 flesch: 37 summary: About the Execution Layer Research category - Execution Layer Research - Ethereum Research Ethereum Research About the Execution Layer Research category Execution Layer Research djrtwo November 8, 2019, 5:53pm 1 The Execution Layer Research category is for research topics related specifically to the Execution Layer of Ethereum (previously often described as “eth1” This includes the EVM, state, sync, transactions, and other items concerning the layer of Ethereum relevant to users, their accounts, dapps, and transactions. keywords: research cache: ethresear-6429.html plain text: ethresear-6429.txt item: #1465 of 3327 id: ethresear-6467 author: ethresear title: ethresear-6467 date: None words: 871 flesch: 50 summary: Rationale behind the change is based on consideration of the profit made by validators rather than their income, and accounting for the decrease in minimum validators and Vitalik’s suggested maximum useful staked Ether number. Maximum useful staked Ether is ~40MM; at 32 Ether per validator and picking the nearest multiple of 16,384 (the minimum number of validators) gives the maximum useful number of validators V_{max} = 1,245,184. keywords: return; validators cache: ethresear-6467.html plain text: ethresear-6467.txt item: #1466 of 3327 id: ethresear-6478 author: ethresear title: ethresear-6478 date: None words: 522 flesch: 57 summary: If organizing the shard space so that popular contracts have equal access from all shards is the objective, then is hierarchical sharding a better solution than hosting contracts on the beacon chain? 3 Likes decanus November 21, 2019, 9:39pm 4 adiasg: Simply the number of transactions is not a good way for scoring contract Totally agree, this was just about providing some function for scoring a contracts “importance” to be in the set of contracts on the beaconchain. This would reduce latency between cross-shard transactions with popular contracts. keywords: contracts cache: ethresear-6478.html plain text: ethresear-6478.txt item: #1467 of 3327 id: ethresear-6487 author: ethresear title: ethresear-6487 date: None words: 962 flesch: 66 summary: Is the plan to still write data to random locations even within one contract? Is the plan still to write to random locations in the tree even within a contract or to have locality and all data effectively in one location? keywords: contract; data; ethereum cache: ethresear-6487.html plain text: ethresear-6487.txt item: #1468 of 3327 id: ethresear-6509 author: ethresear title: ethresear-6509 date: None words: 3837 flesch: 63 summary: However, reference capabilities could be fun for a safe but super concurrent EE later down phase 2. Download block N on shard A. Collect all “foreign references” (that is, address references in transactions in shard A that come from other shards). keywords: capabilities; capability; change; cross; shard; slot; state cache: ethresear-6509.html plain text: ethresear-6509.txt item: #1469 of 3327 id: ethresear-6567 author: ethresear title: ethresear-6567 date: None words: 654 flesch: 73 summary: What are good rules for Oracle voting systems? What are good rules for Oracle voting systems? Miscellaneous Econymous December 2, 2019, 9:23pm 1 keywords: oracle; voting cache: ethresear-6567.html plain text: ethresear-6567.txt item: #1470 of 3327 id: ethresear-6594 author: ethresear title: ethresear-6594 date: None words: 134 flesch: 48 summary: Batch settlement market design sounds like a solution Is there any research/work on implementing batch smart contracts calls natively embedded in EVM? By batch smart contract calls I mean the following: all SC calls within a block are considered to be the inputs to a single SC execution process, which treats all inputs as equal regardless of their position in the block. keywords: evm cache: ethresear-6594.html plain text: ethresear-6594.txt item: #1471 of 3327 id: ethresear-6646 author: ethresear title: ethresear-6646 date: None words: 2863 flesch: 60 summary: #soft_fork #bribery #attacks github.com zack-bitcoin/amoveo/blob/a807dd26a5af156b8890474df7f709b0ddbe07cf/docs/other_blockchains/ethereum_casper_ffg.md Review of Ethereum Casper FFG ========== I wrote a paper about why all PoS blockchains are vulnerable to soft fork bribery attacks https://github.com/zack-bitcoin/amoveo/blob/master/docs/other_blockchains/proof_of_stake.md In general, any attempt to recover from a soft fork bribery attack will have one of these shortcomings: 1) we undo the history that occured during the soft fork bribery attack, enabling the attacker to do double-spends between that version of history, and the new version. Ethereum Casper FFG PoS, like all PoS consensus protocols, is vulnerable to bribery censorship attacks. keywords: attack; censorship; fork; holochain cache: ethresear-6646.html plain text: ethresear-6646.txt item: #1472 of 3327 id: ethresear-6649 author: ethresear title: ethresear-6649 date: None words: 3535 flesch: 62 summary: Instead, it relies on fraud proofs to be certain of correctness: Full nodes observing a chain with an incorrect state transition can broadcast a succinct message showing that fraud has occurred, alerting all light clients of the fraudulent chain. We find fraud proofs an elegant solution for reducing the trust requirements in full nodes, but there is a catch: if the full node is not given access to the information inside the block then they cannot construct a fraud proof. keywords: availability; case; commitment; data; fraud; polynomial cache: ethresear-6649.html plain text: ethresear-6649.txt item: #1473 of 3327 id: ethresear-6703 author: ethresear title: ethresear-6703 date: None words: 908 flesch: 65 summary: Many many validators set up a signing centralized server connected to nodes over a network. From talking to validators, the most vulnerable point seems to be nodes -> HSM connection, since many validators plan to run nodes on AWS, and HSMs in their datacenters, so if one compromises the node->HSM connection, one can do a double sign … Trustless validator blackmailing with the blockchain Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled keywords: attack; december cache: ethresear-6703.html plain text: ethresear-6703.txt item: #1474 of 3327 id: ethresear-6737 author: ethresear title: ethresear-6737 date: None words: 141 flesch: 43 summary: ERC-2350 Semantic contracts (ERC extension - draft) - Data Structure - Ethereum Research Ethereum Research ERC-2350 Semantic contracts (ERC extension - draft) Data Structure DaniellMesquita January 7, 2020, 2:09pm 1 Simple Summary Store relevant infos on contract, in hexadecimal or hash to IPFS/other network file, instead of relying on individual data provided by different blockchain explorers. But other information (site url, email, blog, social networks) depends to be updated on individual blockchain explorers. keywords: data cache: ethresear-6737.html plain text: ethresear-6737.txt item: #1475 of 3327 id: ethresear-6738 author: ethresear title: ethresear-6738 date: None words: 1159 flesch: 65 summary: Yes, this is the biggest problem of FPGA circuit. ECDSA on FPGA TEE on FPGA is already well researched.(abandoned: This provides mutable TEE circuit.) keywords: fpga; intel; key cache: ethresear-6738.html plain text: ethresear-6738.txt item: #1476 of 3327 id: ethresear-6802 author: ethresear title: ethresear-6802 date: None words: 1180 flesch: 54 summary: Contract state is a 256 bit to 256 bit map. Contract state can be represented as a Merkleized binary PATRICIA trie in which every inner node (representing a subtrie) contains a bit offset of the branching (i.e. the length of the common prefix of keys of the subtrie in bits) and references to the two subtries. keywords: contract; proposal; state cache: ethresear-6802.html plain text: ethresear-6802.txt item: #1477 of 3327 id: ethresear-6821 author: ethresear title: ethresear-6821 date: None words: 2217 flesch: 80 summary: Exit rules (e.g. define shares refund policy) Privacy policy (e.g. visibility of group members to each other and to other groups) Score calculation fee for DApps or/and users (e.g. based subscription, lifetime membership, per transaction, free of charge, etc.) Upala-native branches These branches use Upala groups as building blocks. keywords: groups; identity; price; protocol; upala cache: ethresear-6821.html plain text: ethresear-6821.txt item: #1478 of 3327 id: ethresear-6895 author: ethresear title: ethresear-6895 date: None words: 1457 flesch: 53 summary: Another model can be to mix several Time Providers, e.g. GPS and Radio Clocks (or GPS+GLONASS+Galileo+BeiDou), so that Time Providers can fail, but do that independently. Time Service is used as a motivating example. keywords: model; ntp; service; time cache: ethresear-6895.html plain text: ethresear-6895.txt item: #1479 of 3327 id: ethresear-6922 author: ethresear title: ethresear-6922 date: None words: 3449 flesch: 67 summary: Ultimately, the attacker does not even have to hack anything but can simply do a public relation stunt by pretending he took control of private keys and slashing validator keys he created himself to create some credibility. If yes, why? dankrad February 11, 2020, 9:14pm 3 This seems like another variant of Global slashing attack on ETH2 – assuming that you can hack a lot of validator keys, you can do devastating attacks. keywords: attacker; february; funds; victim cache: ethresear-6922.html plain text: ethresear-6922.txt item: #1480 of 3327 id: ethresear-6936 author: ethresear title: ethresear-6936 date: None words: 1857 flesch: 56 summary: Many Proof-of-stake designs assume validator clocks are roughly synchronized. To model clock attacks, we assume that the adversary has two bribing options: full validator control control of a validator clock, when it’s set up incorrectly We assume that clock control option costs much less, perhaps all incorrect clocks can be controlled with an attack of a fixed cost. keywords: attack; clock; time; validators cache: ethresear-6936.html plain text: ethresear-6936.txt item: #1481 of 3327 id: ethresear-6937 author: ethresear title: ethresear-6937 date: None words: 889 flesch: 50 summary: Fortunately, there’s an actor who’s already doing relayer-type activity on Ethereum for cheap: smart contract frontrunners. Surrogeth: Tricking frontrunners into being transaction relayers - Miscellaneous - Ethereum Research Ethereum Research Surrogeth: Tricking frontrunners into being transaction relayers Miscellaneous lsankar4033 February 13, 2020, 1:06am 1 Background There are two use-cases for relayer networks that have been getting attention recently: meta-transactions to ease user onboarding (i.e. not require owning Eth) mixers because the withdraw address may not have Eth to pay for gas Existing relayer network solutions attempt to create relayer networks from scratch (tornado and GSN). keywords: contract; frontrunners cache: ethresear-6937.html plain text: ethresear-6937.txt item: #1482 of 3327 id: ethresear-6945 author: ethresear title: ethresear-6945 date: None words: 1864 flesch: 63 summary: Part 1: “Uniswap DAOs” I propose that Uniswap liquidity pools ought to act more like DAOs, in which the liquidity share token holders are the DAO members. In this post, I will propose two main changes to allow for the higher level of customizability that will enable Uniswap to adapt and become a more versatile tool in the DeFi ecosystem: Add more customizability to Uniswap curves by turning liquidity pools into DAOs who can use governance to improve the parameterization of the curve and fee models. keywords: curve; fee; liquidity; uniswap cache: ethresear-6945.html plain text: ethresear-6945.txt item: #1483 of 3327 id: ethresear-6957 author: ethresear title: ethresear-6957 date: None words: 1227 flesch: 71 summary: but if you want to generate random numbers without worrying about entropy and anyone able to predict the next number, just use this. This technique can also be used for many other things, including HOTP (hash based one time passwords), discovery of friends based on hashed phone numbers, etc. keywords: nodes; number cache: ethresear-6957.html plain text: ethresear-6957.txt item: #1484 of 3327 id: ethresear-6960 author: ethresear title: ethresear-6960 date: None words: 2621 flesch: 68 summary: They think in terms of making apps for community currencies, that are implemented on the level of a coin. The main reason we started Intercoin project is because we already had a large social network and infrastructure to secure the validations. keywords: community; consensus; ethereum; intercoin; money; network cache: ethresear-6960.html plain text: ethresear-6960.txt item: #1485 of 3327 id: ethresear-6972 author: ethresear title: ethresear-6972 date: None words: 232 flesch: 56 summary: Then in does a deep dive into BFT classical consensus. Consensus 101 (BFT consensus from background to PaLa) - Consensus - Ethereum Research Ethereum Research Consensus 101 (BFT consensus from background to PaLa) keywords: consensus cache: ethresear-6972.html plain text: ethresear-6972.txt item: #1486 of 3327 id: ethresear-6973 author: ethresear title: ethresear-6973 date: None words: 9485 flesch: 68 summary: Full nodes restrict their resources primarily for other full nodes or potentially. This flaw, lies in the combination of a basic network level reliance on the availability of full nodes from which data can be retrieved, combined with exposing APIs for on-demand state retrieval which can be used to create stateless clients. keywords: block; chain; clients; data; need; network; nodes; state; stateless; syncing cache: ethresear-6973.html plain text: ethresear-6973.txt item: #1487 of 3327 id: ethresear-6984 author: ethresear title: ethresear-6984 date: None words: 552 flesch: 62 summary: The way it works in the background is that the compiler combines AirScript source code with imported AirAssembly functions and generates a single AirAssembly module for the computation. Start building a standard library of AirAssembly components so that people don’t have to write AirScript for such things as hash functions, Merkle branch verifications, Schnorr signatures etc. Improve and make the composition features more powerful. keywords: leaf; node cache: ethresear-6984.html plain text: ethresear-6984.txt item: #1488 of 3327 id: ethresear-6996 author: ethresear title: ethresear-6996 date: None words: 1641 flesch: 65 summary: A protocol for cross-shard ETH transfers: even more simpler and transparent - Sharded Execution - Ethereum Research Ethereum Research A protocol for cross-shard ETH transfers: even more simpler and transparent Sharded Execution cross-shard cdetrio February 21, 2020, 4:19am 1 This proposal follows three previous proposals for cross-shard transfers: Receipts with accumulators for “already processed” receipts Nonce-based queues Netted balance maps The scheme here is based on “EthTransfer” state objects, and is most similar Netted balance maps. The netting scheme enforces a limit on the number of “transfer objects” by netting them into balance maps and by simply not allowing them to be created for cross-shard transfers. keywords: cross; shard; transfer cache: ethresear-6996.html plain text: ethresear-6996.txt item: #1489 of 3327 id: ethresear-6997 author: ethresear title: ethresear-6997 date: None words: 466 flesch: 52 summary: Dual PoW - Formulating PoW in A Different Aspect - Consensus - Ethereum Research Ethereum Research Dual PoW - Formulating PoW in A Different Aspect Consensus qizhou February 21, 2020, 4:24am 1 In this post, we describe another type of PoW (dual PoW) to produce a block, which reveals similar properties to classical PoW (namely, primal PoW) - a probability of producing a block is proportional to the miner’s hash power, but the resulting statistics of block time and hash value are somewhat dual. Dual PoW: A list of miners (0, …, n - 1) concurrently solves a hash-based puzzle in time t. keywords: pow cache: ethresear-6997.html plain text: ethresear-6997.txt item: #1490 of 3327 id: ethresear-7 author: ethresear title: ethresear-7 date: None words: 6047 flesch: 65 summary: With MEV-Burn inplace, local block builder might potentially not produce good-enough blocks to burn the agreed payload basefee floor. Nerolation: With MEV-Burn inplace, local block builder might potentially not produce good-enough blocks to burn the agreed payload basefee floor. keywords: bids; builder; deadline; eth; floor; payload cache: ethresear-7.html plain text: ethresear-7.txt item: #1491 of 3327 id: ethresear-7027 author: ethresear title: ethresear-7027 date: None words: 1121 flesch: 70 summary: An optimized compacted sparse merkle tree without pre-calculated hashes - Data Structure - Ethereum Research Ethereum Research An optimized compacted sparse merkle tree without pre-calculated hashes Data Structure sparse-merkle-tree jjyr February 26, 2020, 4:25am 1 A week ago, I posted an SMT construction on A nearly-trivial-on-zero-inputs 32-bytes-long collision-resistant hash function The advantage of this construction encourage me to post it again: this construction does not lose any security compare to others no pre-calculated hash set, which is perfect for contracts. pre-calculated hashes Data Structure keywords: node cache: ethresear-7027.html plain text: ethresear-7027.txt item: #1492 of 3327 id: ethresear-7043 author: ethresear title: ethresear-7043 date: None words: 386 flesch: 60 summary: Now, if we build and run a quick python script balance = 100.0 for i in range(4,4726): balance -= (i * balance) / 2**25 print(str(i) + \t + str(balance)) our results are, for an initial balance of 100 4 99.99998807907104 5 99.99997317791163 6 99.99995529652298 While the Serenity Design Rationale document states that With the current parametrization, if blocks stop being finalized, validators lose 1% of their deposits after 2.6 days, 10% after 8.4 days, and 50% after 21 days. keywords: days cache: ethresear-7043.html plain text: ethresear-7043.txt item: #1493 of 3327 id: ethresear-7088 author: ethresear title: ethresear-7088 date: None words: 815 flesch: 67 summary: A very natural point is created which client developers can use to fund themselves The idea behind the State Oligarchy is, let’s come up with a standard protocol which nodes can use to fetch state from state providers. DOS attacks against state retrieval are difficult to perform, and require facing off against teams of people who have strong incentives to make you fail. keywords: fetch; state cache: ethresear-7088.html plain text: ethresear-7088.txt item: #1494 of 3327 id: ethresear-7108 author: ethresear title: ethresear-7108 date: None words: 939 flesch: 59 summary: This write-up is not a new proposal it is an in-depth overview and appraisal of non-sequential receipt cross-shard transactions. Prioritization of receipts vs. transactions As described in Vitalik’s write up Implementing cross-shard transactions keywords: shard; transaction cache: ethresear-7108.html plain text: ethresear-7108.txt item: #1495 of 3327 id: ethresear-7114 author: ethresear title: ethresear-7114 date: None words: 6647 flesch: 65 summary: To address this, another user could wait for the Cross Shard Transaction to time-out, and submit a Root Transaction to fail the overall Cross Shard Transaction (this would be free), and submit Signalling Transactions (would reward the caller) and the Clean Transaction (would reward the caller) to unlock all locked contracts and remove the Cross Shard Transaction Id. 6.5 Application does not submit a Root Transaction To address this, another user could wait for the Cross Shard Transaction to time-out, and submit a Root Transaction to fail the overall Cross Shard Transaction (this would be free), and submit Signalling Transactions (would reward the caller) and the Clean Transaction (would reward the caller) to unlock all locked contracts and remove the Cross Shard Transaction Id. 6.6 Replay Attacks The Root Transaction and Transaction Segments are tied to the account used to sign the Start Transaction, except in failure cases when the Cross Shard time-out has expired. keywords: contract; cross; cross shard; function; root transaction; shard; shard transaction; transaction cache: ethresear-7114.html plain text: ethresear-7114.txt item: #1496 of 3327 id: ethresear-7142 author: ethresear title: ethresear-7142 date: None words: 4351 flesch: 51 summary: From SFF perspective, stratum 0 time sources act as physical sensors, while each non-zero stratum time source is a combination of a physical sensor (local clock) and a soft sensor/PE fusing local clock readings and history of readings of time sources it’s connected to. In general, given suitable clock exchange protocol, each node has four time sources: own local clock own reference clocks (can be multiple) local clock readings of other nodes reference clock readings of other nodes Then such node can implement some sensor fusion strategy/algorithm to obtain a time estimate. keywords: clock; fault; fusion; interval; message; readings; sensor; time cache: ethresear-7142.html plain text: ethresear-7142.txt item: #1497 of 3327 id: ethresear-7173 author: ethresear title: ethresear-7173 date: None words: 1666 flesch: 70 summary: Survey of proposals to reduce block witness size - Execution Layer Research - Ethereum Research Ethereum Research Survey of proposals to reduce block witness size Execution Layer Research stateless poemm March 22, 2020, 11:58pm 1 A major bottleneck of statelessness is block witness size. Below are proposals to reduce block witness size. keywords: block; merkle; size; witness cache: ethresear-7173.html plain text: ethresear-7173.txt item: #1498 of 3327 id: ethresear-7187 author: ethresear title: ethresear-7187 date: None words: 91 flesch: 73 summary: Security Audit Report of Eth 2.0 Specs (by Least Authority) Security tok March 24, 2020, 4:06pm 1 Our team has just published the Phase 0 security audit of Eth 2.0 specs, we welcome any questions or discussion on it! Phase 0 Security Audit Report of Eth 2.0 Specs (by Least Authority) - Security - Ethereum Research Ethereum Research Phase 0 keywords: security cache: ethresear-7187.html plain text: ethresear-7187.txt item: #1499 of 3327 id: ethresear-7195 author: ethresear title: ethresear-7195 date: None words: 490 flesch: 56 summary: Synopsis Take Phase 1.5 as the baseline, but extend it as: Each of the 64 shards contain “Eth1” Shard 0 contains the current Eth1 mainnet state, while other shards start with an empty state Change eth1_friendly_validators so that each shard has its own list Furthermore: Consider current Eth1 (“Istanbul”), but assume “stateless ethereum” (e.g. block witnesses) and ignore “account abstraction” and EIP-1559 Consider Ether on each shard to be the same token as “Beacon Ether” Shard validators are paid via the coinbase inside the shard and not via “Beacon Ether” Planned features (in the following order): Cross-shard Ether transfer Cross-shard contract calls Moving Beacon Ether from the beacon chain into shards other than the 0 shard Moving Ether out of other shards than the 0 shard Important to note that during 1) and 2) the existence of “Beacon Ether” is ignored. Background In Phase 0 there is a process for “depositing” Ether from Eth1 as “Beacon Ether”, but no further integration with Eth1 is explained. keywords: shard cache: ethresear-7195.html plain text: ethresear-7195.txt item: #1500 of 3327 id: ethresear-7198 author: ethresear title: ethresear-7198 date: None words: 1262 flesch: 61 summary: Abstract trustless pool with participant rotation Economics For an overview of trustless pools, click here An extension to the described above is a protocol that enables an abstraction of the pool participants where a large set of participants pool is divided into committees for a defined time period, when that period finishes all participants are rotated to a different pool randomly. Trustless staking pools with a consensus layer and slashed pool participant replacement - Economics - Ethereum Research Ethereum Research Trustless staking pools with a consensus layer and slashed pool participant replacement Proof-of-Stake Economics alonmuroch March 25, 2020, 5:35pm 1 I’ve seen a few talks about decentralised, trustless pools including one made by Carl Beekhuizen & Dankrad Feist (Devon 5). keywords: p_i; participants; pool cache: ethresear-7198.html plain text: ethresear-7198.txt item: #1501 of 3327 id: ethresear-7207 author: ethresear title: ethresear-7207 date: None words: 2046 flesch: 61 summary: Onion routing designs are meant to be low-latency whereas mixnets are meant to be high latency. vbuterin March 29, 2020, 10:55pm 4 Mikerah: Onion routing designs are meant to be low-latency whereas mixnets are meant to be high latency. keywords: network; nodes; onion; routing cache: ethresear-7207.html plain text: ethresear-7207.txt item: #1502 of 3327 id: ethresear-7208 author: ethresear title: ethresear-7208 date: None words: 1354 flesch: 66 summary: That’s why we call these the NAND swaps the set of logical statements will make NAND swaps are: E(X,Y) NAND E(Y,X) for all edges e = (X,Y) E(X,Y) NAND E(X,Z) for all edges (X,Y) and (X,Z) incident at X. call this set of logical statements L. |L| = (2|E| + \sum_{x \in V} {deg(x) \choose 2}), and we have 4L “NAND swaps” Suppose we can solve MAX_FEES_ATOMIC_SWAPS. Problem Definition In human language: we are running an exchange with uniform price auctions (https://en.wikipedia.org/wiki/Multiunit_auction#Uniform_price_auction) for transactions and atomic swaps. keywords: swaps cache: ethresear-7208.html plain text: ethresear-7208.txt item: #1503 of 3327 id: ethresear-7216 author: ethresear title: ethresear-7216 date: None words: 10179 flesch: 43 summary: If `transactionIndex` is not zero, `previousSource` is a tuple of // (uint8 siblingCount, bytes32[] siblings, bytes transaction). Type union of BlockHeader or TransactionProof TransactionProof is a tuple of (uint8 siblingsCount, bytes32[] siblings, bytes transaction) siblings are neighboring nodes in a merkle tree used to verify inclusion of a value against a merkle root blockHeader - The header which contains the transaction whose prior state is being proven. keywords: account; bits; block; bytes; fraud; read; set; state; transaction; value cache: ethresear-7216.html plain text: ethresear-7216.txt item: #1504 of 3327 id: ethresear-7220 author: ethresear title: ethresear-7220 date: None words: 879 flesch: 61 summary: This results in more desired routes with lucky keys, making them more preferable even if they have short signature chains. Because different CLUE_KEYs create different signatures and thereby different next CLUEs, the signature chain kind of branches out, creating multiple possible routes. keywords: chain; signature cache: ethresear-7220.html plain text: ethresear-7220.txt item: #1505 of 3327 id: ethresear-7242 author: ethresear title: ethresear-7242 date: None words: 2399 flesch: 51 summary: Mechanizing Acceptor means a mechanical Proof checker procedure should be defined, which in turn, means formalizing Safety properties, UDPC specification language and Proof. As being compiled, UDPCs run much faster, UDPC gas can be made much cheaper (proportional to performance gains). keywords: code; contracts; evm; gas; udpc cache: ethresear-7242.html plain text: ethresear-7242.txt item: #1506 of 3327 id: ethresear-7246 author: ethresear title: ethresear-7246 date: None words: 1552 flesch: 61 summary: We need a sliding-window time-bound for processing credit transfer transactions. Cross-shard credit transfer a_i \stackrel{x_i}{\longrightarrow} b_i, credit transfer of x_i ETH to b_i on (s_2,E_2), which is from a_i on (s_1, E_1). keywords: credit; level; shard; transfers cache: ethresear-7246.html plain text: ethresear-7246.txt item: #1507 of 3327 id: ethresear-7260 author: ethresear title: ethresear-7260 date: None words: 1411 flesch: 72 summary: This histogram bins blocks by the number of contract bytes which are actually accessed during execution. For the average transaction, gas costs will not greatly increase: Vitalik has proposed charging transactions 3 gas per witnessed byte. keywords: block; bytes; code cache: ethresear-7260.html plain text: ethresear-7260.txt item: #1508 of 3327 id: ethresear-7265 author: ethresear title: ethresear-7265 date: None words: 3754 flesch: 54 summary: You need to select up to k attestations from all subnets, and sometimes multiple aggregates from the same subnet if they overlap and this is the most profitable thing to do. When exact cover exists within a given set system, the Exact Cover abstracts attestation aggregation perfectly. keywords: cover; problem; set cache: ethresear-7265.html plain text: ethresear-7265.txt item: #1509 of 3327 id: ethresear-7277 author: ethresear title: ethresear-7277 date: None words: 1677 flesch: 64 summary: Emits a ToCredit System event on success Cross-shard credit transfer a_i \stackrel{x_i}{\longrightarrow} b_i, credit transfer of x_i ETH to b_i on (s_2,E_2), which is from a_i on (s_1, E_1). Note that EE balance check is done even for credit transfers because of potential reverts. keywords: block; level; shard; transfer cache: ethresear-7277.html plain text: ethresear-7277.txt item: #1510 of 3327 id: ethresear-7287 author: ethresear title: ethresear-7287 date: None words: 593 flesch: 70 summary: The alternative is to pipeline block propagation. (although there a different approach could significantly speed up block propagation) keywords: block; propagation cache: ethresear-7287.html plain text: ethresear-7287.txt item: #1511 of 3327 id: ethresear-7304 author: ethresear title: ethresear-7304 date: None words: 1423 flesch: 67 summary: Blocks and block hashes are not part of the state trie, but are only referenced by blocks, and therefore are “implied state”. Luckily we can also look back at an earlier proposal for Ethereum, EIP-210, which suggested placing block hashes in the state in the form of a special contract. keywords: block; ethereum; state cache: ethresear-7304.html plain text: ethresear-7304.txt item: #1512 of 3327 id: ethresear-7307 author: ethresear title: ethresear-7307 date: None words: 4412 flesch: 57 summary: Protocol requirements There are two group of requirements to the protocol: precision and accuracy bounds, i.e. time estimates of participants should be close to each other (precision) and close to the common time standard (accuracy) scalability, we assume there can be thousands and tens of thousands of participating node The requirements are discussed in more details here. The second property ensures that time estimates are useful, otherwise one could choose a very wide, but uninformative interval. keywords: clock; data; estimates; interval; network; nodes; reference; time cache: ethresear-7307.html plain text: ethresear-7307.txt item: #1513 of 3327 id: ethresear-731 author: ethresear title: ethresear-731 date: None words: 118 flesch: 72 summary: How to apply for eth research grant? - Administrivia - Ethereum Research Ethereum Research How to apply for eth research grant? keywords: grant cache: ethresear-731.html plain text: ethresear-731.txt item: #1514 of 3327 id: ethresear-7332 author: ethresear title: ethresear-7332 date: None words: 395 flesch: 53 summary: Abstract trustless pool with participant rotation - Economics - Ethereum Research Ethereum Research Abstract trustless pool with participant rotation Proof-of-Stake Economics alonmuroch April 28, 2020, 2:19pm 1 For an overview of trustless pools, click here An extension to the described above is a protocol that enables an abstraction of the pool participants where a large set of participants pool is divided into committees for a defined time period, when that period finishes all participants are rotated to a different pool randomly. 1 Like Trustless staking pools - POC Trustless staking pools with a consensus layer and slashed pool participant replacement alonmuroch May 19, 2020, 5:53am 2 Beacon-chain’s seed and shuffle mechanism could be easily used as a randomness source from which next epoch’s pool rotation is calculated and current epoch’s pool tasks do to. keywords: pool cache: ethresear-7332.html plain text: ethresear-7332.txt item: #1515 of 3327 id: ethresear-7336 author: ethresear title: ethresear-7336 date: None words: 2287 flesch: 62 summary: You’re right pEthereum needs n signatures from Incognito committees to unlock tokens on Incognito smart contract. Once shielded, privacy coin transactions are confidential and untraceable. keywords: ethereum; incognito; instruction; privacy; smart cache: ethresear-7336.html plain text: ethresear-7336.txt item: #1516 of 3327 id: ethresear-7340 author: ethresear title: ethresear-7340 date: None words: 4058 flesch: 48 summary: This is inevitable, however, efforts to audit such codes can be optimized. However, such code can be slow. keywords: checks; code; cryptography; language; memory; proof; verification cache: ethresear-7340.html plain text: ethresear-7340.txt item: #1517 of 3327 id: ethresear-7363 author: ethresear title: ethresear-7363 date: None words: 860 flesch: 61 summary: Adapting Pointproofs for Witness Compression - Execution Layer Research - Ethereum Research Ethereum Research Adapting Pointproofs for Witness Compression Execution Layer Research stateless Raghavendra-PegaSys May 7, 2020, 12:15am 1 Here is an approach that extends the ideas of pointproofs towards: variable and unbounded growing of contract storage sizes, unbounded growing of the world state, and more importantly for validating clients to maintain only one commitment, with having small witnesses containing: world state point proof, contract Storage point proof, relevant commitments for world state validation, relevant commitments of contract storage data validation. AddingAccount846×477 41.9 KB The deletion of contract accounts can be achieved by updating the corresponding hash of the account to zeros. keywords: contract; state; storage cache: ethresear-7363.html plain text: ethresear-7363.txt item: #1518 of 3327 id: ethresear-7365 author: ethresear title: ethresear-7365 date: None words: 2881 flesch: 61 summary: Message receipts created during the execution of each block are accumulated and commited to in the block header. Receipt proof The receipt proof (diagram) starts with the hash of a recent beacon block, which in turn includes a list of all the latest cross-linked shard transitions. keywords: block; message; proof; receipt; shard; value cache: ethresear-7365.html plain text: ethresear-7365.txt item: #1519 of 3327 id: ethresear-7369 author: ethresear title: ethresear-7369 date: None words: 1138 flesch: 69 summary: Ethresear.ch: email login will be disabled in 7 days - Administrivia - Ethereum Research Ethereum Research Ethresear.ch: email login will be disabled in 7 days Administrivia hwwhww May 8, 2020, 7:28am 1 Thank you for using etheresear.ch forum! Email login was enabled during the last time we restored the system. keywords: account; ens cache: ethresear-7369.html plain text: ethresear-7369.txt item: #1520 of 3327 id: ethresear-7380 author: ethresear title: ethresear-7380 date: None words: 2399 flesch: 61 summary: One trusted setup to rule them all: generating obfuscated programs will likely require a trusted setup. There are programs that can not be white-box obfuscated no matter what, so white-box obfuscation is not possible for every program. keywords: blockchain; key; obfuscation; program cache: ethresear-7380.html plain text: ethresear-7380.txt item: #1521 of 3327 id: ethresear-7438 author: ethresear title: ethresear-7438 date: None words: 4646 flesch: 66 summary: Sending stealth transaction Let’s assume sender wants to send a transaction to participant with index i. The number of the leaves correspond to the number of stealth transactions. keywords: address; alice; receiver; recipient; sender; stealth; transaction cache: ethresear-7438.html plain text: ethresear-7438.txt item: #1522 of 3327 id: ethresear-7448 author: ethresear title: ethresear-7448 date: None words: 491 flesch: 41 summary: In order to improve search time and reduce traffic for ENR attribute, make possible to find even smaller attributed fractions in network in small time and decrease traffic in all ENR search cases, following Discovery V5 API is proposed: FINDNODEATT Request (0x09) message-data = [request-id, attribute-key, (attribute-value)] message-type = 0x09 attribute-key = searched ENR attribute key attribute-value = (optional) searched ENR attribute value for provided key FINDNODEATT queries for nodes with non-null ENR attribute identified by attribute-key. Comparing discovery advertisement features by efficiency: ENR attributes and topic advertisement - Networking - Ethereum Research Ethereum Research Comparing discovery advertisement features by efficiency: ENR attributes and topic advertisement Networking zilm May 20, 2020, 3:53pm 1 Ongoing development of the Ethereum network, both 1.x and 2.0 requires specialization of peers and introducing a set of different peer roles and responsibilities. keywords: attribute; enr cache: ethresear-7448.html plain text: ethresear-7448.txt item: #1523 of 3327 id: ethresear-7474 author: ethresear title: ethresear-7474 date: None words: 871 flesch: 46 summary: How cross-shard transaction probabilities are calculated. Cross-shard Transaction Probabilistic Simulation - Sharding - Ethereum Research Ethereum Research Cross-shard Transaction Probabilistic Simulation Sharding cross-shard Joseph May 26, 2020, 8:23pm 1 As part of researching cross-shard transactions the TXRX research team has built a cross-shard transaction simulator named Vorpal. keywords: cross; transaction cache: ethresear-7474.html plain text: ethresear-7474.txt item: #1524 of 3327 id: ethresear-7547 author: ethresear title: ethresear-7547 date: None words: 2725 flesch: 60 summary: For background, refer to this issue @jannikluhn opened on validator privacy almost 2 years ago: https://github.com/ethresearch/p2p/issues/5 @liochon suggests the following solution here: Cryptographic sortition: possible solution with zk-snark and @JustinDrake improves on it: Low-overhead secret single-leader election Despite all this, Eth2 still doesn’t provide privacy preserving (alliteration ) options for validators. The Eth2 community has long speculated that validator privacy will be an issue. keywords: june; network; nodes; number; peer; validators cache: ethresear-7547.html plain text: ethresear-7547.txt item: #1525 of 3327 id: ethresear-7561 author: ethresear title: ethresear-7561 date: None words: 1860 flesch: 67 summary: print(Number of missing block slots:, len(slots.difference(block_slots_received)), of, df['slot'].max()-df['slot'].min()) Number of missing block slots: 5319 of 23910 (22%) Question: Are there that many skipped slots on the Witti testnet, or are clients frequently having to request missing blocks from peers? keywords: arrival; blocks; number; slots cache: ethresear-7561.html plain text: ethresear-7561.txt item: #1526 of 3327 id: ethresear-7573 author: ethresear title: ethresear-7573 date: None words: 2799 flesch: 59 summary: There are two benefits from it: it doesn’t change with time, which means long running ads we don’t need dependant queries to download any missed part of state The same properties could also empower state data if it’s organized in a Sparse Merkle Tree where index is account address, state parts could be referenced by account ranges it includes, which translates to appropriate sub-tree. Simplified approach Let’s address all types of objects state and historical data consists of: headers blocks transactions (part of block) transaction receipts witnesses state data Looking at historical data where we could clearly define canonical chain, especially after being a shard of Ethereum 2.0 with finalization. keywords: data; ethereum; network; nodes; range; state cache: ethresear-7573.html plain text: ethresear-7573.txt item: #1527 of 3327 id: ethresear-7585 author: ethresear title: ethresear-7585 date: None words: 272 flesch: 64 summary: In case anyone else is having the same problem, here’s the most important page in png form: 2020-06-eth2-bench850×1100 164 KB 2 Likes roninkaizen July 4, 2020, 10:29am 5 https://github.com/q9f/eth2-bench-2020-06/raw/0a4bf6f1f67d51f1c4978c2b6bbf7a5849a7f861/res/2020-06-et could also work as downloadlink q July 13, 2020, 11:18am 6 It renders all data points directly in the document. 13 Likes vbuterin June 27, 2020, 5:40pm 2 I am having trouble opening https://github.com/q9f/eth2-bench-2020-06/blob/0a4bf6f1f67d51f1c4978c2b6bbf7a5849a7f861/res/2020-06-eth2-bench.pdf . keywords: ethereum cache: ethresear-7585.html plain text: ethresear-7585.txt item: #1528 of 3327 id: ethresear-7597 author: ethresear title: ethresear-7597 date: None words: 2849 flesch: 49 summary: Why better clock models are useful Before going deeper into estimation of linear models using interval data, let’s discuss reasons to use more complex models in block chain clock synchronization context. Clock estimation and synchronization interactions So, a participant can in theory estimate clock models for: its local clock its reference clocks (e.g. NTP servers) “perceived” clocks of other participants (as they may communicate not their local clock readings but corrected ones) keywords: clock; data; estimation; interval; model cache: ethresear-7597.html plain text: ethresear-7597.txt item: #1529 of 3327 id: ethresear-7599 author: ethresear title: ethresear-7599 date: None words: 296 flesch: 52 summary: This topic of deterministic builds has been addressed in the TOR and Bitcoin community, however, I could not find many resources regarding Ethereum clients, except a few marginal discussions on GitHub and Gitter… I hope the discussion has its place here, otherwise I will move it elsewhere. Diverse Double-Compiling Many clients reduces risk (Check ✓) Keywords: deterministic builds, reproducible-builds, GNU Guix / Mes, Toolchain, Gitian, trusting trust attack (Thompson attack) 2 Likes Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled keywords: attack cache: ethresear-7599.html plain text: ethresear-7599.txt item: #1530 of 3327 id: ethresear-7602 author: ethresear title: ethresear-7602 date: None words: 1460 flesch: 63 summary: The way Ethereum state transition is usually described is that we have environment E (block hash, timestamp, gasprice, etc), block B (containing transactions), current state S, and we compute the next state S' like this: S' = D(S, B, E) where D is a function that can be described by a deterministic algorithm, which parses the block, takes out each transaction, runs it through the state, gathers all the changes to the state, and outputs the modified state. Also because I wanted to point out, purely theoretically, of course, that these two modes (with full state and with hash + witness) have different soundness, first being 100%, the second being 99.999999…999 % I want to use it as a taster for developing better terminology for state, blocks, etc., otherwise discussion of things like ReGenesis and Stateless Ethereum can become confusing very quickly (for most people) 1 keywords: algorithm; june; stateless cache: ethresear-7602.html plain text: ethresear-7602.txt item: #1531 of 3327 id: ethresear-7610 author: ethresear title: ethresear-7610 date: None words: 2487 flesch: 53 summary: Second, there are lots of samples when clocks are normal (assuming most validator clocks work fine when not under attack). Clock shift magnitude Another variable is a magnitude of clock shift. keywords: attacker; clock; nodes; shift; time cache: ethresear-7610.html plain text: ethresear-7610.txt item: #1532 of 3327 id: ethresear-7639 author: ethresear title: ethresear-7639 date: None words: 673 flesch: 61 summary: If we choose to not have every shard with ETH 1.x shard, then we would theoretically allow ourselves to start with transformation of data-shards to fully compliant ETH2.0 shards, and then later do the more complicated ETH 1.x shards. Several ETH 1.x shards in ETH 2.0: The current roadmap envisions one ETH 1.x shard, the original Ethereum chain, plus several “data” shards, which will be upgraded later to fully functional shards. keywords: eth; shards cache: ethresear-7639.html plain text: ethresear-7639.txt item: #1533 of 3327 id: ethresear-7654 author: ethresear title: ethresear-7654 date: None words: 1181 flesch: 73 summary: Please have someone correct me if I am wrong (I started recently), but if the nodes need to validate transactions, how can they do it without having access to the information? Ozzie generates a cryptographic proof, that proves the statement “I know a bunch of transactions such that if you start with a state whose Merkle root is R, then apply the transactions, it leads to the balance changes in D, and leaves the new Merkle root R'.” keywords: july; transactions cache: ethresear-7654.html plain text: ethresear-7654.txt item: #1534 of 3327 id: ethresear-7662 author: ethresear title: ethresear-7662 date: None words: 1080 flesch: 66 summary: Without state trie hash, a solution may require every node to periodically create a snapshot block (maybe every 2 weeks or 80000 blocks) - a normal block containing the hash of the state of the previous snapshot block (likely using a trie). The proposed fast tx execution without state trie uses a traditional key-value DB to represent the state. keywords: hash; state cache: ethresear-7662.html plain text: ethresear-7662.txt item: #1535 of 3327 id: ethresear-7676 author: ethresear title: ethresear-7676 date: None words: 1321 flesch: 62 summary: So at least we need heavy collateralization and I am afraid we will need some kind of stability fee such that FUM holders are compensated during a bear market when everybody wants to hold stable coins and nobody wants to hold leveraged ETH. FUM holders will get decent risk/reward and 2. keywords: fum; pool; usm cache: ethresear-7676.html plain text: ethresear-7676.txt item: #1536 of 3327 id: ethresear-7684 author: ethresear title: ethresear-7684 date: None words: 337 flesch: 55 summary: 1 Like hwwhww July 14, 2020, 1:21pm 2 Hey Afri, We were using the default setting of: post edit time limit (A tl0 or tl1 author can edit their post for (n) minutes after posting): 1440 tl2 post edit time limit: tl2 post edit time limit: 43200 editing grace period max diff (Maximum number of character changes allowed in editing grace period, if more changed store another post revision (trust level 0 and 1)): 100 editing grace period max diff high trust: 300 I just changed them to post edit time limit (A tl0 or tl1 author can edit their post for (n) minutes after posting): 4096 tl2 post edit time limit: tl2 post edit time limit: forever editing grace period max diff (Maximum number of character changes allowed in editing grace period, if more changed store another post revision (trust level 0 and 1)): 256 editing grace period max diff high trust: 1024 I also granted you tl2 member trust level. Unable to delete or modify posts - Administrivia - Ethereum Research Ethereum Research Unable to delete or modify posts Administrivia q July 14, 2020, 11:59am 1 The title says it all, I’m unable to delete or modify posts. keywords: post cache: ethresear-7684.html plain text: ethresear-7684.txt item: #1537 of 3327 id: ethresear-7736 author: ethresear title: ethresear-7736 date: None words: 646 flesch: 50 summary: Our initial results show that for 90% of the time, the state of smart contracts with mapping variables can be extracted safely. Visibility into the actual values of smart contract variables is helpful in improving code comprehension, developer debugging, testing of contracts. keywords: contracts; state cache: ethresear-7736.html plain text: ethresear-7736.txt item: #1538 of 3327 id: ethresear-7754 author: ethresear title: ethresear-7754 date: None words: 1915 flesch: 80 summary: But they don’t let you have private global state. https://en.wikipedia.org/wiki/Indistinguishability_obfuscation can allow us to make global private state but that tech is a long way from production IMO. keywords: july; state; utxo cache: ethresear-7754.html plain text: ethresear-7754.txt item: #1539 of 3327 id: ethresear-7761 author: ethresear title: ethresear-7761 date: None words: 285 flesch: 55 summary: Been doing a bit of research on building a smart contract that would allow users to commit some portion of eth2 staking rewards into a dao pool, in exchange for a native token which would govern the dao; in this way, users could fund a pool for commons infrastructure while also supporting the security of eth2. I suppose there are probably some projects on eth1 today that have built similar abstractions without doing anything related to eth2, probably the next step for me is going to be to look at those models and see if there are any concepts/code that can be appropriated for this experiment. keywords: dao cache: ethresear-7761.html plain text: ethresear-7761.txt item: #1540 of 3327 id: ethresear-7851 author: ethresear title: ethresear-7851 date: None words: 882 flesch: 67 summary: An additional possible mitigation is to make our oracle support a distinction between buy price (the price buyers pay) and sell price. Example: Real-time price is $400, oracle price is $400, both mint_burn_adjustment and fund_defund_adjustment = keywords: price cache: ethresear-7851.html plain text: ethresear-7851.txt item: #1541 of 3327 id: ethresear-7874 author: ethresear title: ethresear-7874 date: None words: 698 flesch: 69 summary: So new txs go to everyone and history state can be looked up by Kademlia methods. To what extend does Ethereum benefit from Kademlia? keywords: ethereum; kademlia cache: ethresear-7874.html plain text: ethresear-7874.txt item: #1542 of 3327 id: ethresear-7887 author: ethresear title: ethresear-7887 date: None words: 937 flesch: 59 summary: This allows for the “single step and single proof to update many and append many”. So, if all you’re doing is proving many elements, the “current” append-proof decommitments are inferred, allowing appending to the current root. keywords: elements; proof cache: ethresear-7887.html plain text: ethresear-7887.txt item: #1543 of 3327 id: ethresear-7902 author: ethresear title: ethresear-7902 date: None words: 169 flesch: 63 summary: SKALE has opensource sgxwallet hardware security module that can be EASILY improved to be used by ETH2 (1-2 weeks of work). GitHub skalenetwork/sgxwallet sgxwallet is the first ever opensource hardware secure crypto wallet that is based on Intel SGX technology. keywords: security cache: ethresear-7902.html plain text: ethresear-7902.txt item: #1544 of 3327 id: ethresear-7913 author: ethresear title: ethresear-7913 date: None words: 2234 flesch: 76 summary: Hey guys, I had some ideas on reducing AMM slippage by incorporating limit orders. How would you combine limit orders at different price levels together? keywords: \delta; limit; orders; price cache: ethresear-7913.html plain text: ethresear-7913.txt item: #1545 of 3327 id: ethresear-7916 author: ethresear title: ethresear-7916 date: None words: 230 flesch: 56 summary: Networking newptcai August 29, 2020, 3:41pm 1 I recently read this paper Low-Resource Eclipse Attacks on Ethereum’s Peer-to-Peer Network which explains how Ethereum nodes discover and connect to other nodes. My understanding is that although Ethereum uses a Kademlia like method to discover other nodes, in the end a node more or less still chooses uniform random nodes to establish TCP connections. keywords: ethereum cache: ethresear-7916.html plain text: ethresear-7916.txt item: #1546 of 3327 id: ethresear-7936 author: ethresear title: ethresear-7936 date: None words: 4698 flesch: 62 summary: We performed experiments to analyze users’ behaviors and their effect on transaction fees. Also, about 1,000 users do not pay transaction fees at all because of not making any transfer. keywords: experiment; fee; figure; gas; shard; transaction; users cache: ethresear-7936.html plain text: ethresear-7936.txt item: #1547 of 3327 id: ethresear-7959 author: ethresear title: ethresear-7959 date: None words: 2135 flesch: 56 summary: In the case of time oracles, sensing time takes time itself: there are inevitable delays when communicating information. Definition of Oracle As we employ time oracle in a somewhat different manner, we need to provide an explicit Oracle definition that suits our needs. keywords: clock; dto; oracle; sync; time cache: ethresear-7959.html plain text: ethresear-7959.txt item: #1548 of 3327 id: ethresear-7991 author: ethresear title: ethresear-7991 date: None words: 201 flesch: 61 summary: As the targeted backends are currently under active development, to provide a usable compiler, Flint-2 needs to track the development. Flint targeted Solidity (via Yul) whereas Flint-2 has been designed to be used with multiple backend targets. keywords: flint cache: ethresear-7991.html plain text: ethresear-7991.txt item: #1549 of 3327 id: ethresear-8 author: ethresear title: ethresear-8 date: None words: 2496 flesch: 49 summary: Background: Large staking-as-a-service providers control a large portion of Ethereum validators. If LSTs have a structural requirement to distribute stake across dozen(s) of validators, does that mitigate the need to give extra rewards to larger validators to produce the desired incentives? keywords: attestation; ethereum; rewards; validators cache: ethresear-8.html plain text: ethresear-8.txt item: #1550 of 3327 id: ethresear-8020 author: ethresear title: ethresear-8020 date: None words: 783 flesch: 51 summary: This opcode enables the creation of multi-user wallets, where each user is given a separate non-custodial smart-wallet having its own address for storing ethers and tokens, yet no contract code is deployed, and a main-wallet contract retains the common functionality (i.e. social private key recovery). Multi-user wallets also enable the aggregation of transfer operations in batches similar to rollups, but maintaining the same address space as normal onchain transactions, so the sender's wallet does not need to be upgraded to support sinding ether or tokens to a user of a multi-user wallet. keywords: opcode; user cache: ethresear-8020.html plain text: ethresear-8020.txt item: #1551 of 3327 id: ethresear-8023 author: ethresear title: ethresear-8023 date: None words: 159 flesch: 53 summary: Watchers commit a secret vote Watchers reveal their vote If the request ticket is subjective, watchers go through a “attacking phase” for outliers In finalize request ticket votes are counted up and rewards distributed. Tokens are deposited into the contract, used to vote on oracle configurations (Fees, punishments and such) and also used to back different watchers (oracle verifiers) A request ticket is filed (query string, data type, “is it subjective?” boolean) keywords: oracle cache: ethresear-8023.html plain text: ethresear-8023.txt item: #1552 of 3327 id: ethresear-8028 author: ethresear title: ethresear-8028 date: None words: 184 flesch: 69 summary: 1 Like Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled The main advantage in a system like this is that one will always be able to create their own currency units independent of network difficulty. keywords: cryptocurrency cache: ethresear-8028.html plain text: ethresear-8028.txt item: #1553 of 3327 id: ethresear-8030 author: ethresear title: ethresear-8030 date: None words: 1200 flesch: 45 summary: Now what if we employ 3 categories of governing participants instead of 1, as shown in the picture below? 1st category reserved to all participating central banks of the world, with governance power limited up to 25% max. 2nd category reserved to all the regulators of the world, with governance power limited up to 25% max. 3rd category reserved to everyone that holds/stakes ETH, with governance power limited up to 50% max. The idea of a staker (or whoever that can influence change either by holding/staking ETH) receiving lower governance power as a result of having higher ETH at stake is very good to reduce concentration of power, but this is still not good enough because the next best thing to exploit this is to create multiple proxies with much smaller ETH at stake and this will have much higher governance power collectively. keywords: governance; power cache: ethresear-8030.html plain text: ethresear-8030.txt item: #1554 of 3327 id: ethresear-8036 author: ethresear title: ethresear-8036 date: None words: 82 flesch: 44 summary: Trying to come up with a standard for Multidimensional Tokens - Miscellaneous - Ethereum Research Ethereum Research Trying to come up with a standard for Multidimensional Tokens Miscellaneous Econymous September 28, 2020, 4:48am 1 Multidimensional tokens are tokens with secondary properties. Please explore this concept and let me know if you have any ideas that should be in an MDToken standard Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled keywords: tokens cache: ethresear-8036.html plain text: ethresear-8036.txt item: #1555 of 3327 id: ethresear-8037 author: ethresear title: ethresear-8037 date: None words: 434 flesch: 73 summary: They can expect to be provided with info about bugs by other auditors but they are the ones to say if it is real or if it is inside the scope of the audit or not. Oracle Problem The oracle problem has always been an issue when dealing with prediction markets. keywords: market cache: ethresear-8037.html plain text: ethresear-8037.txt item: #1556 of 3327 id: ethresear-8074 author: ethresear title: ethresear-8074 date: None words: 296 flesch: 57 summary: ElGamal encryption, decryption, and rerandomization, with circom support - zk-s[nt]arks - Ethereum Research Ethereum Research ElGamal encryption, decryption, and rerandomization, with circom support zk-s[nt]arks weijiekoh October 6, 2020, 4:35am 1 MACI anonymization requires ElGamal cryptographic functions in zero knowledge. This library implements ElGamal encryption, decryption, and rerandomization in Typescript for the BabyJub elliptic curve. keywords: rerandomization cache: ethresear-8074.html plain text: ethresear-8074.txt item: #1557 of 3327 id: ethresear-8081 author: ethresear title: ethresear-8081 date: None words: 1341 flesch: 70 summary: 2D data availability with Kate commitments - Sharding - Ethereum Research Ethereum Research 2D data availability with Kate commitments Sharding vbuterin October 6, 2020, 10:42pm 1 We can use Kate commitments to create a very clean and simple 2D data availability scheme with collaborative encoding (ie. O(N^2) data can be encoded by a very loose collection of N participants with each participant only doing O(N*log(N)) work). The design would work as follows: When doing the initial round of data availability sampling, each node would use the same indices for each batch. keywords: data cache: ethresear-8081.html plain text: ethresear-8081.txt item: #1558 of 3327 id: ethresear-8082 author: ethresear title: ethresear-8082 date: None words: 837 flesch: 72 summary: Pushable proofs let you append unlimited number of elements onto partial trees (a pushable proof is essentially just a non-inclusion for the next free index). Quadrable: Sparse merkle tree database in C++ and Solidity, git-like command-line tool - Data Structure - Ethereum Research Ethereum Research Quadrable: Sparse merkle tree database in C++ and Solidity, git-like command-line tool Data Structure sparse-merkle-tree hoytech October 7, 2020, 7:10am 1 Hi! keywords: proofs; tree cache: ethresear-8082.html plain text: ethresear-8082.txt item: #1559 of 3327 id: ethresear-8143 author: ethresear title: ethresear-8143 date: None words: 800 flesch: 71 summary: To start things off, I think there are some open questions: How large are code merkle proofs, by how much would moving to Kate commitments reduce witness sizes? How much time does it take to create a commitment, create a proof, or verify a proof? Kate commitments go further; they promise constant sized proofs. keywords: code; setup cache: ethresear-8143.html plain text: ethresear-8143.txt item: #1560 of 3327 id: ethresear-8161 author: ethresear title: ethresear-8161 date: None words: 1636 flesch: 68 summary: Such stablecoin is not sustainable. Such stablecoin is not really a stablecoin. keywords: market; price; sell; stablecoin cache: ethresear-8161.html plain text: ethresear-8161.txt item: #1561 of 3327 id: ethresear-8230 author: ethresear title: ethresear-8230 date: None words: 260 flesch: 40 summary: Calculating economic security levels for sub-finality beacon chain confirmations - Economics - Ethereum Research Ethereum Research Calculating economic security levels for sub-finality beacon chain confirmations Proof-of-Stake Economics technocrypto November 18, 2020, 2:36pm 1 I’m interested in putting together a model for both attacker budgets and cost-of-reversion in the sub-finality environment, as discussed with Vitalik here. My first thoughts at a stab for attacker budget are: calculate the number of validators required to be assigned x consecutive block proposals within a 1 month window, PLUS keywords: block cache: ethresear-8230.html plain text: ethresear-8230.txt item: #1562 of 3327 id: ethresear-8280 author: ethresear title: ethresear-8280 date: None words: 2941 flesch: 66 summary: The mechanism does a good job of giving each YES x_i holder as much exposure to x_i as possible and as little exposure to other events as possible given the constraints. If someone wants to bet YES on event 3 and have no exposure to other events, does he have to wait for events 1 and 2 to settle before buying event 3? 1 keywords: events; market; token; yes cache: ethresear-8280.html plain text: ethresear-8280.txt item: #1563 of 3327 id: ethresear-8303 author: ethresear title: ethresear-8303 date: None words: 162 flesch: 54 summary: USM minimalist decentralized stablecoin nearing launch - Decentralized exchanges - Ethereum Research Ethereum Research USM minimalist decentralized stablecoin nearing launch Decentralized exchanges jacob-eliosoff December 2, 2020, 8:51pm 1 Just an update on the USM stablecoin project I’ve posted about here twice before: after a flurry of coding and refinements, this project is nearing launch. USM minimalist decentralized stablecoin could use final feedback before v1 launch Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled keywords: stablecoin cache: ethresear-8303.html plain text: ethresear-8303.txt item: #1564 of 3327 id: ethresear-8357 author: ethresear title: ethresear-8357 date: None words: 2049 flesch: 55 summary: Splitting witnesses into 2 parts - Execution Layer Research - Ethereum Research Ethereum Research Splitting witnesses into 2 parts Execution Layer Research stateless onqtam December 11, 2020, 4:56pm 1 TL;DR This is a proposal to split witnesses into 2 complementary parts: data and proofs, allowing for stateless clients to process just the necessary data without the merkle proofs (and thus reducing network traffic) and without proving the stateRoot, while retaining a high degree of certainty for the data being processed thanks to a new witnessHash field in the block header (a hash of the hashes of the data and the merkle proofs) secured by the consensus layer, with the option to retrieve the proofs as well and fully validate the state transition. Detailed description The data part of a witness It should contain the absolute minimum for transaction execution: the state trie nodes referenced by the transactions in the associated block the code chunks (but without their merkle proofs), as envisioned in the current code-merkelization efforts positional information (bitmaps) for the code chunks - which parts of the bytecode of a contract are present (for a 340-byte contract with 32-byte chunking that would be 11 bits - truly negligible) Currently, (not in this proposal) witnesses contain the necessary trie nodes, the merkle multiproof, and some structural information (masks) required to position the nodes in the right places in the state trie in order for the stateRoot hash to actually match. keywords: data; proofs; state; witness cache: ethresear-8357.html plain text: ethresear-8357.txt item: #1565 of 3327 id: ethresear-8370 author: ethresear title: ethresear-8370 date: None words: 97 flesch: 37 summary: Crosschain Workshop 2021 - Layer 2 - Ethereum Research Ethereum Research Crosschain Workshop 2021 Layer 2 crosslinks, cross-shard drinkcoffee December 15, 2020, 12:38am 1 Crosschain Workshop 2021: Call for Speakers: The Crosschain Workshop aims to bring researchers across the world together to advance the field of crosschain transaction technology. Workshop: https://crosschain.mx/workshop2021/ Call for Speakers: https://crosschain.mx/workshop2021/call-for-speakers/ Free Registration: https://crosschain.mx/workshop2021/registration/ 1 Like Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled keywords: workshop cache: ethresear-8370.html plain text: ethresear-8370.txt item: #1566 of 3327 id: ethresear-8472 author: ethresear title: ethresear-8472 date: None words: 3284 flesch: 64 summary: Because included transactions have a total ordering and are never skipped, executed transactions have completely deterministic witnesses and network participants have \eta blocks to disseminate those witnesses. For Alaska to work we will need an additional network primitive peers can use to gossip block witnesses to each other, honest miners will gossip the witness for a block as soon as they know what the witness will be. keywords: block; execution; january; transactions; witnesses cache: ethresear-8472.html plain text: ethresear-8472.txt item: #1567 of 3327 id: ethresear-8512 author: ethresear title: ethresear-8512 date: None words: 173 flesch: 64 summary: The reason is AFTER the Solidity call finishes, there is lots of gas paid back EVM frees the memory. Is it possible to implement self-recharging wallets in EVM? - EVM - Ethereum Research Ethereum Research Is it possible to implement self-recharging wallets in EVM? keywords: evm cache: ethresear-8512.html plain text: ethresear-8512.txt item: #1568 of 3327 id: ethresear-8575 author: ethresear title: ethresear-8575 date: None words: 267 flesch: 67 summary: Tracking live states in stateless storage schemes - Sharding - Ethereum Research Ethereum Research Tracking live states in stateless storage schemes Sharding stateless dlubarov January 25, 2021, 11:48pm 1 We thought this might be interesting to folks here: Reducing state size on Mir. To briefly recap the problem: Merkle Mountain Ranges (MMRs) work nicely as a log of account states, but since they are append-only, we need a separate structure to keep track of which states are presently active. keywords: stateless cache: ethresear-8575.html plain text: ethresear-8575.txt item: #1569 of 3327 id: ethresear-8588 author: ethresear title: ethresear-8588 date: None words: 489 flesch: 62 summary: The proposal: Reward block proposers by the number of votes they receive in their block. Like Pintail April 5, 2021, 1:01am 2 One issue I see with this is if block proposers are rewarded according to the number of head votes their block receives, then they get a bonus if the subsequent block proposer misses its slot, as they will get a second round of head votes. keywords: block cache: ethresear-8588.html plain text: ethresear-8588.txt item: #1570 of 3327 id: ethresear-8623 author: ethresear title: ethresear-8623 date: None words: 420 flesch: 64 summary: Future: one could use each of ETH2 data chains as data storage for merge mined chains. MergedMining as fully decentralized rollup alternative - Consensus - Ethereum Research Ethereum Research MergedMining as fully decentralized rollup alternative Consensus kladkogex February 3, 2021, 4:54pm 1 TL;DR A merged mined chain can be used as a fully decentralized rollup alternative to achieve 1000 tps, while using the current ETH1, and 100K+ tps using ETH2 data chains. keywords: block; chain cache: ethresear-8623.html plain text: ethresear-8623.txt item: #1571 of 3327 id: ethresear-8739 author: ethresear title: ethresear-8739 date: None words: 4125 flesch: 65 summary: There’s two distinct ideas: Individual storage slots of a contract are migrated to newer epoch state trees separately There’s the possible extension of allowing a contract to have storage in different address spaces I don’t think (1) would change how the EVM or any programming languages work. An account with address (e, s) can only be touched when the chain is in epoch \ge e The state consists of an ever-growing list of state trees, S_1, S_2, S_3…, where each S_i is the state corresponding to the current epoch. keywords: account; contract; epoch; state; transaction; witness cache: ethresear-8739.html plain text: ethresear-8739.txt item: #1572 of 3327 id: ethresear-8868 author: ethresear title: ethresear-8868 date: None words: 123 flesch: 37 summary: Improving the EVM's memory model with paginated RAM and FP-relative access - EVM - Ethereum Research Ethereum Research Improving the EVM's memory model with paginated RAM and FP-relative access EVM nickjohnson March 9, 2021, 8:49pm 1 Fellowship of Ethereum Magicians – 6 Mar 21 EIPs 3336 and 3337: Improving the EVM's memory model I’ve written up two EIP drafts, 3336 and 3337 that together permit a new efficient way to use EVM memory for storage of ephemeral data such as local variables, function arguments, and return values. I believe that these changes represent a minimal... keywords: evm cache: ethresear-8868.html plain text: ethresear-8868.txt item: #1573 of 3327 id: ethresear-8909 author: ethresear title: ethresear-8909 date: None words: 1726 flesch: 59 summary: Under this suggestion, the full fork choice would be a hierarchy of 4: Find latest finalized epoch Find latest justified epoch Find highest epoch boundary block according to LMD GHOST on FFG target votes Find head block according to LMD GHOST on head votes This rule has the effect of enforcing the (block, slot) fork choice rule only on epoch boundary blocks, for much better liveness (latencies of up to one epoch can be tolerated). The tricky part of this is empty slots, which are exactly the crux of the short reorg attacks, because the current attestations do not vote for empty slots, only for their ancestor. keywords: block; rule; slot cache: ethresear-8909.html plain text: ethresear-8909.txt item: #1574 of 3327 id: ethresear-9039 author: ethresear title: ethresear-9039 date: None words: 972 flesch: 60 summary: Sender confidentiality If we cannot hide the fact that we participated in a Gitcoin grant round, can we hide the amount we contributed to a project? Specifically, when depositing coins for funding projects, the sender has to decompose its coins into a number of fixed-amount notes (1 ETH, 10 ETH, 100 ETH, …). keywords: privacy; sender cache: ethresear-9039.html plain text: ethresear-9039.txt item: #1575 of 3327 id: ethresear-9046 author: ethresear title: ethresear-9046 date: None words: 1228 flesch: 54 summary: Stateless validators for “The Merge” via block witnesses We want/need validators to be able to validate blocks without burdening them with the state. The proposed way to do this is to enshrine block witnesses into the protocol such that a client could use the witness to validate the resulting state root from executing a block. keywords: block; state; stateless cache: ethresear-9046.html plain text: ethresear-9046.txt item: #1576 of 3327 id: ethresear-9095 author: ethresear title: ethresear-9095 date: None words: 2169 flesch: 60 summary: We sidestep the problem of tree rot, where expired parts of the tree prevent new accounts from being created, by creating all new accounts on the right side of the tree, irrespective of address. To prevent account collisions, it would be necessary to ensure that new accounts can’t be made that have the same identification as old accounts. keywords: account; node; tree cache: ethresear-9095.html plain text: ethresear-9095.txt item: #1577 of 3327 id: ethresear-9109 author: ethresear title: ethresear-9109 date: None words: 129 flesch: 37 summary: Scaling Ethereum Hackathon (Apr 16 -> May 13) - Miscellaneous - Ethereum Research Ethereum Research Scaling Ethereum Hackathon (Apr 16 -> May 13) Miscellaneous liam April 6, 2021, 5:17pm 1 Hey everyone, just wanted to surface that at ETHGlobal we’re running Scaling Ethereum which is a 3-week hackathon focused entirely around blockchain scaling: rollups, channels, zero knowledge scaling strategies, and ETH 2.0. For anyone interested in these things, I’d really encourage you to consider signing up as it’s an opportunity to contribute to this research, build infrastructure around it, try out the latest projects’ SDKs and offerings, and potentially win prizes or bounties at the same time. keywords: ethereum cache: ethresear-9109.html plain text: ethresear-9109.txt item: #1578 of 3327 id: ethresear-9115 author: ethresear title: ethresear-9115 date: None words: 1828 flesch: 52 summary: 1098×638 55.2 KB Figure 1: High level OOBN model of Stateless Ethereum showing four BN sub-models and the flow of information between them Empirical data were used to calculate conditional probability tables, and to run BN data mining algorithms to learn model structures. Stateless Ethereum Bayesian network model The initial model structure was designed through consultation with Ethereum experts, predominantly from ConsenSys. keywords: creation; data; ethereum; model; stateless; witness cache: ethresear-9115.html plain text: ethresear-9115.txt item: #1579 of 3327 id: ethresear-9224 author: ethresear title: ethresear-9224 date: None words: 3647 flesch: 67 summary: Frontrunning, backrunning, sandwiching and other attacks all come from the centralized way in which block content is produced. The wealthier the attacker is the more they can manipulate transaction order The wealthy can best afford to fund the multiple accounts that grant them this preferential tx order. keywords: block; consensus; content; layer; mev; transaction cache: ethresear-9224.html plain text: ethresear-9224.txt item: #1580 of 3327 id: ethresear-9249 author: ethresear title: ethresear-9249 date: None words: 105 flesch: 73 summary: Tool for Solidity bytecode decompile and dataflow analysis - EVM - Ethereum Research Ethereum Research Tool for Solidity bytecode decompile and dataflow analysis EVM jchen217 April 22, 2021, 6:41pm 1 I want to find the argument dependence in the solidity program through bytecode of solidity. We use it all the time and it saved us lots of money. keywords: solidity cache: ethresear-9249.html plain text: ethresear-9249.txt item: #1581 of 3327 id: ethresear-9299 author: ethresear title: ethresear-9299 date: None words: 221 flesch: 52 summary: Please see the invitation below: `` We are a group of researchers at University of Illinois at Urbana-Champaign and we are recruiting people who have experience with solidity smart contracts for a study that aims to better understand developers’ experience in developing smart contracts. Smart contract development survey [research study] - Miscellaneous - Ethereum Research Ethereum Research Smart contract development survey [research study] Miscellaneous amiller April 28, 2021, 6:26pm 1 Hi ethresearch folks, I’m posting here to seek volunteers for a research study we’re doing on developer experience. keywords: research cache: ethresear-9299.html plain text: ethresear-9299.txt item: #1582 of 3327 id: ethresear-9456 author: ethresear title: ethresear-9456 date: None words: 1116 flesch: 65 summary: The required change Each client (e.g. geth, OpenEthereum) should implement a new RPC call, eth_stateCommitment(blocknum) which works for recent blocks and returns a state-change commitment signed by the node’s private key: { 'blockNum':num, 'preStateRoot':hash, 'postStateRoot':hash, 'transactions': yoavw: eth_stateCommitment(blocknum) which works for recent blocks and returns a state-change commitment signed by the node’s private key: { 'blockNum':num, 'preStateRoot':hash, 'postStateRoot':hash, 'transactions': keywords: block; transaction cache: ethresear-9456.html plain text: ethresear-9456.txt item: #1583 of 3327 id: ethresear-9465 author: ethresear title: ethresear-9465 date: None words: 497 flesch: 47 summary: Homomorphic encryption (HE)-based (idea: use homomorphic properties of encryption scheme to perform private computation) Considerations Choosing a performant FHE scheme to minimize miner’s time performing homomorphic computations Minimizing user’s computational requirements (i.e. expecting the user to have access to only a modest machine) keywords: user cache: ethresear-9465.html plain text: ethresear-9465.txt item: #1584 of 3327 id: ethresear-9600 author: ethresear title: ethresear-9600 date: None words: 3169 flesch: 67 summary: The operator is malicious, and wishes to freeze/hold user funds for ransom. In fact, even today in StarkEx every state transition is made of several txs, with proof verification, on-chain data and storing state transition data all broken into several txs. keywords: data; funds; operator; users cache: ethresear-9600.html plain text: ethresear-9600.txt item: #1585 of 3327 id: ethresear-9637 author: ethresear title: ethresear-9637 date: None words: 2012 flesch: 57 summary: Then, the situation is called block finalization, the branch finalized is the final canonical chain, and the data in finalized blocks are the final data. Priority of branches The weight of a branch is the number of total votes gained by the root and all its descendants. keywords: block; votes; voting cache: ethresear-9637.html plain text: ethresear-9637.txt item: #1586 of 3327 id: ethresear-9781 author: ethresear title: ethresear-9781 date: None words: 1391 flesch: 61 summary: Can something similar be done for state proofs? Future-proof Shard and History Access Precompiles - Execution Layer Research - Ethereum Research Ethereum Research Future-proof Shard and History Access Precompiles Execution Layer Research vbuterin June 8, 2021, 5:55pm 1 One of the backwards-compatibility challenges in the current Ethereum design is that history access requires in-EVM verification of Merkle proofs, which assume that the blockchain will forever use the same formatting and the same cryptography. keywords: proof; slot; uint256 cache: ethresear-9781.html plain text: ethresear-9781.txt item: #1587 of 3327 id: ethresear-9855 author: ethresear title: ethresear-9855 date: None words: 3497 flesch: 68 summary: The amount C is willing to wager that P is correct Y1: Keywords that J2 uses to determine if Event K happened Y2: Keywords J2 uses to determine who B is Y3: Keywords that J3 uses to determine what the correct P is PK: Private key unique to C that is used to confirm if P is correct U1: Public key used by J3 to collect R U2: Public key by C to collect Z L: Total amount of currency spent by A Q: Number of inactive contracts made by A F: Number of completed and active contracts made by A V: Sum of the “VIP Equation” Bibliography “Assassination Politics” by Jim Bell (https://cryptome.org/ap.htm) “Ethereum is game-changing technology, literally.” by Virgil Griffith (Ethereum is game-changing technology, literally. Once J2, a combination of a smart contract and a keyword script constantly scanning the internet, determines Event K (i.e. A is murdered or goes to jail) has happened, J2 then changes the public “bounty” status from inactive to active. keywords: bounty; event cache: ethresear-9855.html plain text: ethresear-9855.txt item: #1588 of 3327 id: ethresear-increase-the-max-effective-balance-a-modest-proposal author: ethresear title: ethresear-increase-the-max-effective-balance-a-modest-proposal date: None words: 6238 flesch: 57 summary: Post-capella, validator balances are automatically withdrawn. Would this also reduce bandwidth requirements for some nodes, as currently running more validators means subscribing to more attestation gossip topics? keywords: balance; eth; june; maxeb; proposal; set; solo; stakers; staking; validator cache: ethresear-increase-the-max-effective-balance-a-modest-proposal.html plain text: ethresear-increase-the-max-effective-balance-a-modest-proposal.txt item: #1589 of 3327 id: filecoin-filecoin author: filecoin title: filecoin-filecoin date: 2018-07-07 words: 15038 flesch: 63 summary: submit new storage orders via Put. DSNs aggregate storage offered by multiple independent storage providers and self-coordinate to provide data storage and data retrieval to clients. keywords: blockchain; clients; data; deal; dsn; filecoin; market; miners; network; orderbook; orders; piece; proof; protocol; retrieval; storage; storage market; storage miners; time cache: filecoin-filecoin.pdf plain text: filecoin-filecoin.txt item: #1590 of 3327 id: github-whitepaper.md author: github title: github-whitepaper.md date: None words: 16127 flesch: 43 summary: The entity is a single plugin and required for executing Hyperledger Cactus applications. Business Logic ID ID for business logic to be invoked by Cactus user. keywords: access; api; application; assets; blockchain; business; cactus; case; connector; consortium; data; example; hyperledger; key; ledger; logic; migration; object; plugin; server; source; target; tbd; transaction; user; validator; value; verifier; way cache: github-whitepaper.md.html plain text: github-whitepaper.md.txt item: #1591 of 3327 id: hedera-a-mena-region-first-zain-group-joins-hedera-governing-council author: hedera title: hedera-a-mena-region-first-zain-group-joins-hedera-governing-council date: None words: 1706 flesch: 50 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. About Hedera Hedera Hashgraph is an enterprise-grade public distributed ledger for building decentralized applications. keywords: applications; council; ecosystem; group; hashgraph; hedera; network; zain cache: hedera-a-mena-region-first-zain-group-joins-hedera-governing-council.html plain text: hedera-a-mena-region-first-zain-group-joins-hedera-governing-council.txt item: #1592 of 3327 id: hedera-a-technical-deep-dive-hederas-community-testing-program author: hedera title: hedera-a-technical-deep-dive-hederas-community-testing-program date: None words: 2571 flesch: 51 summary: 3) Wordpress Plugin (or any website that supports Hedera micropayments) technical design considerations There are 3 key features a website should implement if it wants to accept Hedera micropayment: a) b) A REST API to receive a POST request from the Payment Server when Hedera mainnet returns the response for the crypto transfer (indicating whether the crypto transfer from the end user succeeded or failed). keywords: browser; extension; hedera; micropayment; network; payment; server; wordpress cache: hedera-a-technical-deep-dive-hederas-community-testing-program.html plain text: hedera-a-technical-deep-dive-hederas-community-testing-program.txt item: #1593 of 3327 id: hedera-abft-for-correctness-and-liveness author: hedera title: hedera-abft-for-correctness-and-liveness date: None words: 3606 flesch: 67 summary: The attacker is a node, and by refusing to participate in consensus, or by sending messages that break the rules of the protocol, prevents other nodes from reaching consensus. I also control malicious nodes (less than 1/3), which know what is going on, and can help me direct the attack to repeatedly change which node is being DDoSed. keywords: abft; attack; consensus; hedera; liveness; nodes; proof cache: hedera-abft-for-correctness-and-liveness.html plain text: hedera-abft-for-correctness-and-liveness.txt item: #1594 of 3327 id: hedera-abrdn-plc-joins-hedera-governing-council-cementing-its-vision-for-web3-and-client-centric-fund-management author: hedera title: hedera-abrdn-plc-joins-hedera-governing-council-cementing-its-vision-for-web3-and-client-centric-fund-management date: None words: 1420 flesch: 48 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. abrdn plc Joins Hedera Governing Council, Cementing its… | Hedera Hedera Network Services Token Service Mint and configure tokens and accounts. keywords: abrdn; council; ecosystem; governance; hedera; management; network cache: hedera-abrdn-plc-joins-hedera-governing-council-cementing-its-vision-for-web3-and-client-centric-fund-management.html plain text: hedera-abrdn-plc-joins-hedera-governing-council-cementing-its-vision-for-web3-and-client-centric-fund-management.txt item: #1595 of 3327 id: hedera-account-abstraction-at-the-protocol-level author: hedera title: hedera-account-abstraction-at-the-protocol-level date: None words: 2753 flesch: 56 summary: How Web3 adoption is held back, and how account abstraction removes the barrier Protocol-level account abstraction, and how it differs from current account abstraction implementations Hedera’s unique capabilities among EVM networks that enable protocol-level account abstraction What does account abstraction achieve? Entering the world of Web3 and interacting with DApps (Web3 applications) presents a steep learning curve, especially for those accustomed to the more user-friendly interfaces of Web2 applications. The implication of this is that almost all of the required ingredients for account abstraction are already present in Hedera. keywords: abstraction; account; applications; hedera; protocol; transaction; web2; web3 cache: hedera-account-abstraction-at-the-protocol-level.html plain text: hedera-account-abstraction-at-the-protocol-level.txt item: #1596 of 3327 id: hedera-account-creation-fee-increase-and-fee-change-processes author: hedera title: hedera-account-creation-fee-increase-and-fee-change-processes date: None words: 1511 flesch: 57 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: council; fee; fees; hedera; network; transaction cache: hedera-account-creation-fee-increase-and-fee-change-processes.html plain text: hedera-account-creation-fee-increase-and-fee-change-processes.txt item: #1597 of 3327 id: hedera-acoer-forms-strategic-partnership-with-global-system-integrator-armedia-to-develop-dedicated-hedera-practice author: hedera title: hedera-acoer-forms-strategic-partnership-with-global-system-integrator-armedia-to-develop-dedicated-hedera-practice date: None words: 1485 flesch: 47 summary: As an early adopter of Hedera technologies, Acoer has long held the view that the team, technologies, and governance model underpinning Hedera are best-of-breed for building practical, fast, and economically viable DLT-enabled solutions for the enterprise, where the complexity of DLT is abstracted and the focus is on application usability. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: acoer; armedia; developer; ecosystem; enterprise; hedera; network; time cache: hedera-acoer-forms-strategic-partnership-with-global-system-integrator-armedia-to-develop-dedicated-hedera-practice.html plain text: hedera-acoer-forms-strategic-partnership-with-global-system-integrator-armedia-to-develop-dedicated-hedera-practice.txt item: #1598 of 3327 id: hedera-acoers-rightshash-builds-on-hedera-to-pioneer-decentralized-management-and-protection-of-users-rights author: hedera title: hedera-acoers-rightshash-builds-on-hedera-to-pioneer-decentralized-management-and-protection-of-users-rights date: None words: 1407 flesch: 49 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Mance Harmon, CEO and Co-founder of Hedera Hashgraph, said: “We are incredibly privileged to have Acoer as an active user of the Hedera network. keywords: acoer; consent; developer; ecosystem; hedera; network; rightshash cache: hedera-acoers-rightshash-builds-on-hedera-to-pioneer-decentralized-management-and-protection-of-users-rights.html plain text: hedera-acoers-rightshash-builds-on-hedera-to-pioneer-decentralized-management-and-protection-of-users-rights.txt item: #1599 of 3327 id: hedera-adsdax-achieves-1372-cryptocurrency-transactions-per-second-on-hedera-hashgraph-with-zee-entertainment-enterprises-sets-new-industry-record author: hedera title: hedera-adsdax-achieves-1372-cryptocurrency-transactions-per-second-on-hedera-hashgraph-with-zee-entertainment-enterprises-sets-new-industry-record date: None words: 1453 flesch: 55 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Working with Hedera Hashgraph, AdsDax has been tracking millions of live events from advertising in real-time, allowing advertisers and publishers to get real-time, consensus verified statistics directly from Hedera. keywords: adsdax; ecosystem; entertainment; hedera; network; time; zee cache: hedera-adsdax-achieves-1372-cryptocurrency-transactions-per-second-on-hedera-hashgraph-with-zee-entertainment-enterprises-sets-new-industry-record.html plain text: hedera-adsdax-achieves-1372-cryptocurrency-transactions-per-second-on-hedera-hashgraph-with-zee-entertainment-enterprises-sets-new-industry-record.txt item: #1600 of 3327 id: hedera-adsdax-surpasses-1-billion-ad-events-recorded-on-hedera-hashgraphs-mainnet author: hedera title: hedera-adsdax-surpasses-1-billion-ad-events-recorded-on-hedera-hashgraphs-mainnet date: None words: 1409 flesch: 55 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: adsdax; advertising; ecosystem; events; hashgraph; hedera; network cache: hedera-adsdax-surpasses-1-billion-ad-events-recorded-on-hedera-hashgraphs-mainnet.html plain text: hedera-adsdax-surpasses-1-billion-ad-events-recorded-on-hedera-hashgraphs-mainnet.txt item: #1601 of 3327 id: hedera-analysis-remediation-of-the-precompile-attack-on-the-hedera-network author: hedera title: hedera-analysis-remediation-of-the-precompile-attack-on-the-hedera-network date: None words: 2477 flesch: 49 summary: Resolution The Ethereum state is stored strictly in individual smart contracts, whereas Hedera tokens are stored in a system-wide state map. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: attacker; contract; hbar; hedera; network; pangolin; tokens; usdc[hts cache: hedera-analysis-remediation-of-the-precompile-attack-on-the-hedera-network.html plain text: hedera-analysis-remediation-of-the-precompile-attack-on-the-hedera-network.txt item: #1602 of 3327 id: hedera-animoca-brands-and-hedera-announce-helix-warp-and-nft-based-football-game author: hedera title: hedera-animoca-brands-and-hedera-announce-helix-warp-and-nft-based-football-game date: None words: 1401 flesch: 53 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: animoca; brands; ecosystem; hbar; hedera; helix; network cache: hedera-animoca-brands-and-hedera-announce-helix-warp-and-nft-based-football-game.html plain text: hedera-animoca-brands-and-hedera-announce-helix-warp-and-nft-based-football-game.txt item: #1603 of 3327 id: hedera-announcing-hip-540-enhanced-token-key-management-on-hedera author: hedera title: hedera-announcing-hip-540-enhanced-token-key-management-on-hedera date: None words: 1588 flesch: 56 summary: To try out this functionality, please update your SDK to the following versions: Hedera Java SDK: v2.34.0 Hedera Go SDK: v2.39.0 Hedera JavaScript SDK: v2.47.0 Share This Back to blog What is gRPC, gRPC-Web, and Proxies? Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: admin; hedera; key; keys; supply; token cache: hedera-announcing-hip-540-enhanced-token-key-management-on-hedera.html plain text: hedera-announcing-hip-540-enhanced-token-key-management-on-hedera.txt item: #1604 of 3327 id: hedera-announcing-scheduled-transactions-on-hedera author: hedera title: hedera-announcing-scheduled-transactions-on-hedera date: None words: 2590 flesch: 50 summary: What's New Partners Papers Careers Media Blog Technical Press Podcast Community Events Meetups Store Brand Navigation QUICKSTART Announcing Scheduled Transactions on Hedera technical May 06, 2021 by Atul Mahamuni Senior Vice President of Product, Hashgraph Scheduled Transactions is a new capability available on Hedera that enables multiple parties to easily, inexpensively, and natively schedule and execute any type of Hedera transaction together. On-ledger traceability Every single transaction, such as the creation of the scheduled transaction as well as individual parties adding their respective signatures to that transaction, are also Hedera transactions. keywords: hedera; network; parties; signatures; time; transaction; use cache: hedera-announcing-scheduled-transactions-on-hedera.html plain text: hedera-announcing-scheduled-transactions-on-hedera.txt item: #1605 of 3327 id: hedera-anything-you-can-do-you-can-do-on-hedera-introducing-the-json-rpc-relay author: hedera title: hedera-anything-you-can-do-you-can-do-on-hedera-introducing-the-json-rpc-relay date: None words: 1416 flesch: 58 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: hbar; hedera; json; network; relay; rpc cache: hedera-anything-you-can-do-you-can-do-on-hedera-introducing-the-json-rpc-relay.html plain text: hedera-anything-you-can-do-you-can-do-on-hedera-introducing-the-json-rpc-relay.txt item: #1606 of 3327 id: hedera-australian-agri-supply-chain-launches-on-hedera-hashgraph author: hedera title: hedera-australian-agri-supply-chain-launches-on-hedera-hashgraph date: None words: 1288 flesch: 53 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Australian agri supply chain launches on Hedera Hashgraph | Hedera Hedera Network Services Token Service Mint and configure tokens and accounts. keywords: ecosystem; entrust; hashgraph; hedera; network; supply cache: hedera-australian-agri-supply-chain-launches-on-hedera-hashgraph.html plain text: hedera-australian-agri-supply-chain-launches-on-hedera-hashgraph.txt item: #1607 of 3327 id: hedera-australias-national-debit-operator-eftpos-joins-hedera-governing-council-and-will-run-aussie-hedera-network-node author: hedera title: hedera-australias-national-debit-operator-eftpos-joins-hedera-governing-council-and-will-run-aussie-hedera-network-node date: None words: 1582 flesch: 48 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: australia; council; ecosystem; eftpos; hedera; network; payments cache: hedera-australias-national-debit-operator-eftpos-joins-hedera-governing-council-and-will-run-aussie-hedera-network-node.html plain text: hedera-australias-national-debit-operator-eftpos-joins-hedera-governing-council-and-will-run-aussie-hedera-network-node.txt item: #1608 of 3327 id: hedera-auto-create-a-hedera-account-with-hbar-and-token-transfers author: hedera title: hedera-auto-create-a-hedera-account-with-hbar-and-token-transfers date: None words: 999 flesch: 60 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: account; hbar; hedera; network; token cache: hedera-auto-create-a-hedera-account-with-hbar-and-token-transfers.html plain text: hedera-auto-create-a-hedera-account-with-hbar-and-token-transfers.txt item: #1609 of 3327 id: hedera-avery-dennisons-atma-io-connected-product-cloud-to-utilize-the-hedera-network-to-account-for-carbon-emissions-of-billions-of-unique-items author: hedera title: hedera-avery-dennisons-atma-io-connected-product-cloud-to-utilize-the-hedera-network-to-account-for-carbon-emissions-of-billions-of-unique-items date: None words: 1801 flesch: 50 summary: Partnership with HBAR Foundation and use of Hedera network services will enable new decarbonization use cases while driving the adoption of digital ID technologies across a variety of industries. The partnership with the HBAR Foundation and integration with Hedera network services builds on the atma.io Spring 2022 release, focused on sustainability and waste elimination, and is the latest example of Avery Dennison’s commitment to leveraging leading-edge technology to drive sustainability initiatives. keywords: atma.io; avery; carbon; dennison; hbar; hedera; network; product cache: hedera-avery-dennisons-atma-io-connected-product-cloud-to-utilize-the-hedera-network-to-account-for-carbon-emissions-of-billions-of-unique-items.html plain text: hedera-avery-dennisons-atma-io-connected-product-cloud-to-utilize-the-hedera-network-to-account-for-carbon-emissions-of-billions-of-unique-items.txt item: #1610 of 3327 id: hedera-beyond-hedera-how-hiero-sets-a-new-standard-for-decentralized-open-source-development author: hedera title: hedera-beyond-hedera-how-hiero-sets-a-new-standard-for-decentralized-open-source-development date: None words: 3217 flesch: 42 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. However, Hedera TechComm remains active—it still reviews and approves HIPs that impact the Hedera network specifically, ensuring that updates to its instance of the Hiero codebase meet the network’s operational and security standards. keywords: decentralized; foundation; governance; hedera; hiero; network; project; source; trust; tsc cache: hedera-beyond-hedera-how-hiero-sets-a-new-standard-for-decentralized-open-source-development.html plain text: hedera-beyond-hedera-how-hiero-sets-a-new-standard-for-decentralized-open-source-development.txt item: #1611 of 3327 id: hedera-bitgo-joins-the-hedera-council-to-further-the-success-of-the-hedera-network-and-support-innovation author: hedera title: hedera-bitgo-joins-the-hedera-council-to-further-the-success-of-the-hedera-network-and-support-innovation date: None words: 1476 flesch: 49 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: bitgo; council; ecosystem; future; hedera; network; world cache: hedera-bitgo-joins-the-hedera-council-to-further-the-success-of-the-hedera-network-and-support-innovation.html plain text: hedera-bitgo-joins-the-hedera-council-to-further-the-success-of-the-hedera-network-and-support-innovation.txt item: #1612 of 3327 id: hedera-build-your-first-hcs-powered-web-app author: hedera title: hedera-build-your-first-hcs-powered-web-app date: None words: 2786 flesch: 58 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Mirror node client - A client which subscribes to a Hedera Mirror node, in order to receive post-consensus messages. keywords: application; chat; client; hcs; hedera; new; node cache: hedera-build-your-first-hcs-powered-web-app.html plain text: hedera-build-your-first-hcs-powered-web-app.txt item: #1613 of 3327 id: hedera-building-nft-auction-on-hedera author: hedera title: hedera-building-nft-auction-on-hedera date: None words: 2170 flesch: 63 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: account; auction; bid; hedera; network; nft; token cache: hedera-building-nft-auction-on-hedera.html plain text: hedera-building-nft-auction-on-hedera.txt item: #1614 of 3327 id: hedera-calaxy-built-on-the-hedera-network-adds-initial-advisors-from-dapper-labs-liquefy-bluesky-and-centre-consortium author: hedera title: hedera-calaxy-built-on-the-hedera-network-adds-initial-advisors-from-dapper-labs-liquefy-bluesky-and-centre-consortium date: None words: 1551 flesch: 51 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: calaxy; creators; ecosystem; future; hedera; media; network cache: hedera-calaxy-built-on-the-hedera-network-adds-initial-advisors-from-dapper-labs-liquefy-bluesky-and-centre-consortium.html plain text: hedera-calaxy-built-on-the-hedera-network-adds-initial-advisors-from-dapper-labs-liquefy-bluesky-and-centre-consortium.txt item: #1615 of 3327 id: hedera-canopyright-launches-decentralized-cannabis-herbarium-and-licensing-platform-built-on-hedera-network author: hedera title: hedera-canopyright-launches-decentralized-cannabis-herbarium-and-licensing-platform-built-on-hedera-network date: None words: 1420 flesch: 49 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: breeders; cannabis; canopyright; hedera; network; plant; strains cache: hedera-canopyright-launches-decentralized-cannabis-herbarium-and-licensing-platform-built-on-hedera-network.html plain text: hedera-canopyright-launches-decentralized-cannabis-herbarium-and-licensing-platform-built-on-hedera-network.txt item: #1616 of 3327 id: hedera-capture-your-contributions-to-the-hedera-ecosystem-in-the-electric-capital-developer-report author: hedera title: hedera-capture-your-contributions-to-the-hedera-ecosystem-in-the-electric-capital-developer-report date: None words: 1055 flesch: 55 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: developer; ecosystem; hedera; network; report cache: hedera-capture-your-contributions-to-the-hedera-ecosystem-in-the-electric-capital-developer-report.html plain text: hedera-capture-your-contributions-to-the-hedera-ecosystem-in-the-electric-capital-developer-report.txt item: #1617 of 3327 id: hedera-cdc-and-whos-coronavirus-data-now-searchable-via-acoer-powered-by-hedera-hashgraph author: hedera title: hedera-cdc-and-whos-coronavirus-data-now-searchable-via-acoer-powered-by-hedera-hashgraph date: None words: 1215 flesch: 52 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: acoer; data; developer; ecosystem; hedera; network cache: hedera-cdc-and-whos-coronavirus-data-now-searchable-via-acoer-powered-by-hedera-hashgraph.html plain text: hedera-cdc-and-whos-coronavirus-data-now-searchable-via-acoer-powered-by-hedera-hashgraph.txt item: #1618 of 3327 id: hedera-chainlink-labs-furthers-enterprise-focus-joins-hedera-governing-council author: hedera title: hedera-chainlink-labs-furthers-enterprise-focus-joins-hedera-governing-council date: None words: 1229 flesch: 50 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: chainlink; council; enterprise; hedera; network; oracle cache: hedera-chainlink-labs-furthers-enterprise-focus-joins-hedera-governing-council.html plain text: hedera-chainlink-labs-furthers-enterprise-focus-joins-hedera-governing-council.txt item: #1619 of 3327 id: hedera-changes-to-hedera-api-hapi-for-v0-8-0-and-v0-9-0 author: hedera title: hedera-changes-to-hedera-api-hapi-for-v0-8-0-and-v0-9-0 date: None words: 1175 flesch: 52 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: ecosystem; hedera; network; release; transaction; v0.9.0 cache: hedera-changes-to-hedera-api-hapi-for-v0-8-0-and-v0-9-0.html plain text: hedera-changes-to-hedera-api-hapi-for-v0-8-0-and-v0-9-0.txt item: #1620 of 3327 id: hedera-charles-adkins-appointed-as-president-of-the-hedera-council author: hedera title: hedera-charles-adkins-appointed-as-president-of-the-hedera-council date: None words: 1204 flesch: 54 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: adkins; council; ecosystem; hedera; network; president; technology cache: hedera-charles-adkins-appointed-as-president-of-the-hedera-council.html plain text: hedera-charles-adkins-appointed-as-president-of-the-hedera-council.txt item: #1621 of 3327 id: hedera-chopra-foundation-launches-never-alone-app-to-support-mental-and-emotional-wellness author: hedera title: hedera-chopra-foundation-launches-never-alone-app-to-support-mental-and-emotional-wellness date: None words: 1292 flesch: 53 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: chopra; ecosystem; foundation; health; hedera; network; world cache: hedera-chopra-foundation-launches-never-alone-app-to-support-mental-and-emotional-wellness.html plain text: hedera-chopra-foundation-launches-never-alone-app-to-support-mental-and-emotional-wellness.txt item: #1622 of 3327 id: hedera-chopra-foundation-to-leverage-hedera-hashgraph-to-create-an-open-access-trusted-platform-to-share-mental-health-resources-globally author: hedera title: hedera-chopra-foundation-to-leverage-hedera-hashgraph-to-create-an-open-access-trusted-platform-to-share-mental-health-resources-globally date: None words: 1600 flesch: 50 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Consensus Service enables creation of a digital fingerprint for content for the Never Alone Initiative, guaranteeing authentic, tamper-proof resources for those in need Dallas, TX and Carlsbad, CA — August 20, 2020 — The Chopra Foundation, dedicated to supporting mind-body integrative health and well-being, has announced its partnership with Hedera Hashgraph, the enterprise-grade distributed ledger, to develop an online, freely accessible platform to share the verified set of Never Alone Initiative resources to fight rising suicide rates and support mental and emotional wellness. keywords: chopra; foundation; health; hedera; network; platform; resources cache: hedera-chopra-foundation-to-leverage-hedera-hashgraph-to-create-an-open-access-trusted-platform-to-share-mental-health-resources-globally.html plain text: hedera-chopra-foundation-to-leverage-hedera-hashgraph-to-create-an-open-access-trusted-platform-to-share-mental-health-resources-globally.txt item: #1623 of 3327 id: hedera-code-is-law-but-what-if-the-law-needs-to-change author: hedera title: hedera-code-is-law-but-what-if-the-law-needs-to-change date: None words: 1680 flesch: 57 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: code; contract; developer; hedera; law; network cache: hedera-code-is-law-but-what-if-the-law-needs-to-change.html plain text: hedera-code-is-law-but-what-if-the-law-needs-to-change.txt item: #1624 of 3327 id: hedera-cofra-holding-joins-hedera-governing-council-to-accelerate-dlt-adoption-and-further-leadership-in-sustainability author: hedera title: hedera-cofra-holding-joins-hedera-governing-council-to-accelerate-dlt-adoption-and-further-leadership-in-sustainability date: None words: 1187 flesch: 54 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: cofra; council; ecosystem; hedera; network; open cache: hedera-cofra-holding-joins-hedera-governing-council-to-accelerate-dlt-adoption-and-further-leadership-in-sustainability.html plain text: hedera-cofra-holding-joins-hedera-governing-council-to-accelerate-dlt-adoption-and-further-leadership-in-sustainability.txt item: #1625 of 3327 id: hedera-coq-proof-completed-by-carnegie-mellon-professor-confirms-hashgraph-consensus-algorithm-is-asynchronous-byzantine-fault-tolerant author: hedera title: hedera-coq-proof-completed-by-carnegie-mellon-professor-confirms-hashgraph-consensus-algorithm-is-asynchronous-byzantine-fault-tolerant date: None words: 1475 flesch: 54 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: consensus; coq; hashgraph; hedera; network; proof cache: hedera-coq-proof-completed-by-carnegie-mellon-professor-confirms-hashgraph-consensus-algorithm-is-asynchronous-byzantine-fault-tolerant.html plain text: hedera-coq-proof-completed-by-carnegie-mellon-professor-confirms-hashgraph-consensus-algorithm-is-asynchronous-byzantine-fault-tolerant.txt item: #1626 of 3327 id: hedera-counting-votes-why-a-2-3-threshold author: hedera title: hedera-counting-votes-why-a-2-3-threshold date: None words: 2386 flesch: 65 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: consensus; hedera; liveness; nodes; safety; threshold cache: hedera-counting-votes-why-a-2-3-threshold.html plain text: hedera-counting-votes-why-a-2-3-threshold.txt item: #1627 of 3327 id: hedera-create-accounts-with-ed25519-and-ecdsa-keys-from-the-hedera-portal author: hedera title: hedera-create-accounts-with-ed25519-and-ecdsa-keys-from-the-hedera-portal date: None words: 1216 flesch: 60 summary: As part of our updates to the Hedera portal, it now supports the creation of Hedera testnet accounts that use ECDSA keys. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: account; create; ecosystem; hedera; network; testnet cache: hedera-create-accounts-with-ed25519-and-ecdsa-keys-from-the-hedera-portal.html plain text: hedera-create-accounts-with-ed25519-and-ecdsa-keys-from-the-hedera-portal.txt item: #1628 of 3327 id: hedera-creating-soulbound-token-ecosystems-on-hedera author: hedera title: hedera-creating-soulbound-token-ecosystems-on-hedera date: None words: 2452 flesch: 61 summary: A list of Hedera explorers can be found here. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: account; acme; alice; hedera; implementation; soulbound; token; training cache: hedera-creating-soulbound-token-ecosystems-on-hedera.html plain text: hedera-creating-soulbound-token-ecosystems-on-hedera.txt item: #1629 of 3327 id: hedera-crypto-industry-leaders-champion-free-multi-chain-scam-reporting-tool-chainabuse-to-empower-users-against-crypto-fraud author: hedera title: hedera-crypto-industry-leaders-champion-free-multi-chain-scam-reporting-tool-chainabuse-to-empower-users-against-crypto-fraud date: None words: 1915 flesch: 52 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: chainabuse; community; crypto; ecosystem; hedera; network; platform; trm cache: hedera-crypto-industry-leaders-champion-free-multi-chain-scam-reporting-tool-chainabuse-to-empower-users-against-crypto-fraud.html plain text: hedera-crypto-industry-leaders-champion-free-multi-chain-scam-reporting-tool-chainabuse-to-empower-users-against-crypto-fraud.txt item: #1630 of 3327 id: hedera-curv-deepens-digital-asset-security-for-hedera-hbar-with-mpc-technology author: hedera title: hedera-curv-deepens-digital-asset-security-for-hedera-hbar-with-mpc-technology date: None words: 1450 flesch: 51 summary: Today Curv, the world’s most trusted digital asset security platform, announced that Hedera Hashgraph has selected it as a preferred security technology partner to empower enterprises to build the most secure wallet functionality into applications built on the Hedera public DLT network, using Curv’s unique multi-party computation (MPC) technology. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: asset; curv; hbar; hedera; network; public; security cache: hedera-curv-deepens-digital-asset-security-for-hedera-hbar-with-mpc-technology.html plain text: hedera-curv-deepens-digital-asset-security-for-hedera-hbar-with-mpc-technology.txt item: #1631 of 3327 id: hedera-dbs-is-first-bank-in-southeast-asia-to-join-hedera-governing-council-and-run-network-node author: hedera title: hedera-dbs-is-first-bank-in-southeast-asia-to-join-hedera-governing-council-and-run-network-node date: None words: 1209 flesch: 53 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. What's New Partners Papers Careers Media Blog Technical Press Podcast Community Events Meetups Store Brand Navigation QUICKSTART DBS is First Bank in Southeast Asia to Join Hedera Governing Council and Run Network Node news Oct 26, 2021 by Hedera Team Hedera is the most used, sustainable, enterprise-grade public network for the decentralized economy. keywords: blockchain; council; dbs; ecosystem; hedera; network cache: hedera-dbs-is-first-bank-in-southeast-asia-to-join-hedera-governing-council-and-run-network-node.html plain text: hedera-dbs-is-first-bank-in-southeast-asia-to-join-hedera-governing-council-and-run-network-node.txt item: #1632 of 3327 id: hedera-decentralization author: hedera title: hedera-decentralization date: None words: 1027 flesch: 52 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Read article Hedera Governing Council to Allocate $5 Billion in HBAR to Independent Foundation and Ecosystem Development Initiatives Sep 16, 2021Hedera Team DALLAS, TX - September 16, 2021 - The Hedera Governing Council has announced the approval of a plan to allocate 10.7 billion hbars (approximately 20% of total supply), currently worth US $5 billion as of September 16th, 2021, towards the development of the Hedera ecosystem. keywords: ecosystem; hashgraph; hedera; network; read cache: hedera-decentralization.html plain text: hedera-decentralization.txt item: #1633 of 3327 id: hedera-decentralized-applications-go-live-on-hedera-hashgraph-as-mainnet-opens-to-public author: hedera title: hedera-decentralized-applications-go-live-on-hedera-hashgraph-as-mainnet-opens-to-public date: None words: 3503 flesch: 52 summary: Mance Harmon, co-founder and CEO of Hedera Hashgraph, said, “Today we are thrilled that, through open access, dozens of decentralized applications are now live and running on the mainnet, along with mirror nodes and other parts of the ecosystem designed to expand Hedera’s reach and adoption. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: access; applications; chain; data; ecosystem; founder; hashgraph; hedera; network; platform; public cache: hedera-decentralized-applications-go-live-on-hedera-hashgraph-as-mainnet-opens-to-public.html plain text: hedera-decentralized-applications-go-live-on-hedera-hashgraph-as-mainnet-opens-to-public.txt item: #1634 of 3327 id: hedera-decentralized-identity-on-hedera-consensus-service author: hedera title: hedera-decentralized-identity-on-hedera-consensus-service date: None words: 1842 flesch: 53 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: consensus; credential; dlt; hedera; identity; network; use cache: hedera-decentralized-identity-on-hedera-consensus-service.html plain text: hedera-decentralized-identity-on-hedera-consensus-service.txt item: #1635 of 3327 id: hedera-defi author: hedera title: hedera-defi date: None words: 646 flesch: 55 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. HBAR The Hedera network's native cryptocurrency. keywords: ecosystem; hbar; hedera; network cache: hedera-defi.html plain text: hedera-defi.txt item: #1636 of 3327 id: hedera-dell-technologies-joins-hedera-governing-council-to-help-automate-distributed-ledger-technology author: hedera title: hedera-dell-technologies-joins-hedera-governing-council-to-help-automate-distributed-ledger-technology date: None words: 1234 flesch: 48 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Dell Technologies Joins Hedera Governing Council to help… | Hedera Hedera Network Services Token Service Mint and configure tokens and accounts. keywords: council; data; dell; ecosystem; hedera; network cache: hedera-dell-technologies-joins-hedera-governing-council-to-help-automate-distributed-ledger-technology.html plain text: hedera-dell-technologies-joins-hedera-governing-council-to-help-automate-distributed-ledger-technology.txt item: #1637 of 3327 id: hedera-dentons-becomes-newest-member-of-hedera-governing-council author: hedera title: hedera-dentons-becomes-newest-member-of-hedera-governing-council date: None words: 1473 flesch: 49 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Dentons Becomes Newest Member of Hedera Governing Council | Hedera Hedera Network Services Token Service Mint and configure tokens and accounts. keywords: council; dentons; dlt; ecosystem; hedera; network; world cache: hedera-dentons-becomes-newest-member-of-hedera-governing-council.html plain text: hedera-dentons-becomes-newest-member-of-hedera-governing-council.txt item: #1638 of 3327 id: hedera-deprecation-timeline-for-v1-of-the-open-source-hedera-sdk-for-java-javascript author: hedera title: hedera-deprecation-timeline-for-v1-of-the-open-source-hedera-sdk-for-java-javascript date: None words: 1059 flesch: 55 summary: What's New Partners Papers Careers Media Blog Technical Press Podcast Community Events Meetups Store Brand Navigation QUICKSTART Deprecation timeline for v1 of the open source Hedera SDK for Java & Javascript technical May 11, 2021 by Brady Gentile Director of Marketing, Web3 Application Ecosystems Version 1 of the official open source Hedera SDKs for Java and Javascript was released on January 14th, 2020. For a complete list of changes between v1 and v2 and a migration reference guide, please refer to the following repositories: Java, JavaScript New languages and beyond Officially supported languages for Hedera SDKs are being considered but no concrete decisions have been made. keywords: community; hedera; network; sdks cache: hedera-deprecation-timeline-for-v1-of-the-open-source-hedera-sdk-for-java-javascript.html plain text: hedera-deprecation-timeline-for-v1-of-the-open-source-hedera-sdk-for-java-javascript.txt item: #1639 of 3327 id: hedera-develop-a-hedera-dapp-with-metamask-hashpack-and-blade-integration author: hedera title: hedera-develop-a-hedera-dapp-with-metamask-hashpack-and-blade-integration date: None words: 5913 flesch: 34 summary: Purpose: get token balances for an account with token info in order to display token balance, token type, decimals, etc. // Purpose: get token balances for an account with token info in order to display token balance, token type, decimals, etc. // keywords: account; await; const; dapp; hedera; import; info; nft; return; token cache: hedera-develop-a-hedera-dapp-with-metamask-hashpack-and-blade-integration.html plain text: hedera-develop-a-hedera-dapp-with-metamask-hashpack-and-blade-integration.txt item: #1640 of 3327 id: hedera-developer-quick-start-custom-token-fees author: hedera title: hedera-developer-quick-start-custom-token-fees date: None words: 1531 flesch: 57 summary: It included the new functionality of HIP-18: Custom Hedera Token Service Fees — the ability for anyone issuing a token on Hedera using the Hedera Token Service to include programmatic custom fees. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: custom; fee; fees; hedera; schedule; token cache: hedera-developer-quick-start-custom-token-fees.html plain text: hedera-developer-quick-start-custom-token-fees.txt item: #1641 of 3327 id: hedera-developer-quick-start-nfts-and-metadata author: hedera title: hedera-developer-quick-start-nfts-and-metadata date: None words: 1826 flesch: 60 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: developer; digital; hedera; metadata; nft; nfts; service; token cache: hedera-developer-quick-start-nfts-and-metadata.html plain text: hedera-developer-quick-start-nfts-and-metadata.txt item: #1642 of 3327 id: hedera-developer-resources-update author: hedera title: hedera-developer-resources-update date: None words: 1470 flesch: 61 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: developer; ecosystem; hbar; hedera; network; view cache: hedera-developer-resources-update.html plain text: hedera-developer-resources-update.txt item: #1643 of 3327 id: hedera-devnews author: hedera title: hedera-devnews date: None words: 1206 flesch: 59 summary: Build the unimaginable on Hedera Read article Hedera Developer Highlights May 2024 May 31, 2024Ed Marquez May developer highlights: Hedera Services Evolution v0.49 modularization, dynamic NFTs, new Hedera EVM developer survey, and contribute to the Electric Capital Developer Report to showcase Hedera's strength and attract more developers! Read article Hedera Developer Highlights March 2024 Mar 31, 2024Ed Marquez March highlights: BitGo joins Hedera Council, new Pyth Oracle and Supra DORA integrations, NFT Studio video series, no testnet reset on April 25, and don't forget to take the Hedera Documentation survey! Read article Hedera Developer Highlights February 2025 Mar 13, 2025Michiel Mulders This month, we delve into significant developments that are shaping the future of the Hedera network. keywords: article; developer; hedera; highlights; network; read cache: hedera-devnews.html plain text: hedera-devnews.txt item: #1644 of 3327 id: hedera-dla-piper-launches-new-toko-security-tokenization-platform-on-hedera-hashgraph-hyperledger-fabric-and-microsoft-azure author: hedera title: hedera-dla-piper-launches-new-toko-security-tokenization-platform-on-hedera-hashgraph-hyperledger-fabric-and-microsoft-azure date: None words: 1567 flesch: 53 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: dla; ecosystem; hedera; network; piper; tokenization; toko cache: hedera-dla-piper-launches-new-toko-security-tokenization-platform-on-hedera-hashgraph-hyperledger-fabric-and-microsoft-azure.html plain text: hedera-dla-piper-launches-new-toko-security-tokenization-platform-on-hedera-hashgraph-hyperledger-fabric-and-microsoft-azure.txt item: #1645 of 3327 id: hedera-does-hederas-tps-include-transactions-generated-by-its-consensus-algorithm author: hedera title: hedera-does-hederas-tps-include-transactions-generated-by-its-consensus-algorithm date: None words: 1872 flesch: 53 summary: So, once and for all, let us note that Hedera Consensus Service (HCS) transactions are not required for the Hedera network to reach consensus and Hedera's publicly reported transaction count does not count the intra-node gossip communication needed to arrive at consensus. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: consensus; hcs; hedera; ledger; network; service; transactions cache: hedera-does-hederas-tps-include-transactions-generated-by-its-consensus-algorithm.html plain text: hedera-does-hederas-tps-include-transactions-generated-by-its-consensus-algorithm.txt item: #1646 of 3327 id: hedera-dogfooding-at-hedera-trust-bucket-for-verifiable-object-storage-with-amazon-s3-and-hedera-consensus-service author: hedera title: hedera-dogfooding-at-hedera-trust-bucket-for-verifiable-object-storage-with-amazon-s3-and-hedera-consensus-service date: None words: 1755 flesch: 60 summary: If you enjoyed reading about this project and are inspired to help us decentralized the web, please check out our open roles: https://www.hedera.com/future Share This Back to blog What is gRPC, gRPC-Web, and Proxies? Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: bucket; council; file; hash; hedera; network; trust cache: hedera-dogfooding-at-hedera-trust-bucket-for-verifiable-object-storage-with-amazon-s3-and-hedera-consensus-service.html plain text: hedera-dogfooding-at-hedera-trust-bucket-for-verifiable-object-storage-with-amazon-s3-and-hedera-consensus-service.txt item: #1647 of 3327 id: hedera-dynamic-address-book author: hedera title: hedera-dynamic-address-book date: None words: 1246 flesch: 50 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: address; book; ecosystem; hedera; network; node cache: hedera-dynamic-address-book.html plain text: hedera-dynamic-address-book.txt item: #1648 of 3327 id: hedera-e-i-awards-safe-health-systems-inc-with-contract-to-offer-covid-19-and-std-digital-testing-powered-by-hedera-to-its-member-institutions author: hedera title: hedera-e-i-awards-safe-health-systems-inc-with-contract-to-offer-covid-19-and-std-digital-testing-powered-by-hedera-to-its-member-institutions date: None words: 1544 flesch: 52 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: e&i; health; healthcheck; hedera; network; platform; testing cache: hedera-e-i-awards-safe-health-systems-inc-with-contract-to-offer-covid-19-and-std-digital-testing-powered-by-hedera-to-its-member-institutions.html plain text: hedera-e-i-awards-safe-health-systems-inc-with-contract-to-offer-covid-19-and-std-digital-testing-powered-by-hedera-to-its-member-institutions.txt item: #1649 of 3327 id: hedera-edf-redex-and-rekursive-labs-collaborate-on-proof-of-concept-for-automating-renewable-energy-certificates-transactions-using-hedera author: hedera title: hedera-edf-redex-and-rekursive-labs-collaborate-on-proof-of-concept-for-automating-renewable-energy-certificates-transactions-using-hedera date: None words: 1873 flesch: 47 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: ecosystem; edf; energy; hedera; labs; network; recs; redex cache: hedera-edf-redex-and-rekursive-labs-collaborate-on-proof-of-concept-for-automating-renewable-energy-certificates-transactions-using-hedera.html plain text: hedera-edf-redex-and-rekursive-labs-collaborate-on-proof-of-concept-for-automating-renewable-energy-certificates-transactions-using-hedera.txt item: #1650 of 3327 id: hedera-eftpos-pioneers-new-ecommerce-micropayments-solution-using-hedera-hashgraph author: hedera title: hedera-eftpos-pioneers-new-ecommerce-micropayments-solution-using-hedera-hashgraph date: None words: 1270 flesch: 50 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: ecosystem; eftpos; hbar; hedera; micropayments; network; payments cache: hedera-eftpos-pioneers-new-ecommerce-micropayments-solution-using-hedera-hashgraph.html plain text: hedera-eftpos-pioneers-new-ecommerce-micropayments-solution-using-hedera-hashgraph.txt item: #1651 of 3327 id: hedera-emtech-and-hedera-hashgraph-join-forces-for-highly-performant-trusted-and-energy-efficient-central-bank-blockchain-infrastructure author: hedera title: hedera-emtech-and-hedera-hashgraph-join-forces-for-highly-performant-trusted-and-energy-efficient-central-bank-blockchain-infrastructure date: None words: 1493 flesch: 49 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. “We’re thrilled to collaborate with EMTECH to give central banks around the globe the opportunity to explore realistic ways to bring CBDCs to fruition, and this collaboration will enable a groundbreaking use of the Hedera network and services,” said Mance Harmon, CEO of Hedera Hashgraph. keywords: bank; central; ecosystem; emtech; hashgraph; hedera; network cache: hedera-emtech-and-hedera-hashgraph-join-forces-for-highly-performant-trusted-and-energy-efficient-central-bank-blockchain-infrastructure.html plain text: hedera-emtech-and-hedera-hashgraph-join-forces-for-highly-performant-trusted-and-energy-efficient-central-bank-blockchain-infrastructure.txt item: #1652 of 3327 id: hedera-enabling-dynamic-nfts-on-hedera-exploring-hip-646-hip-657-and-hip-765 author: hedera title: hedera-enabling-dynamic-nfts-on-hedera-exploring-hip-646-hip-657-and-hip-765 date: None words: 1478 flesch: 53 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: hedera; hip; metadata; network; nfts; token cache: hedera-enabling-dynamic-nfts-on-hedera-exploring-hip-646-hip-657-and-hip-765.html plain text: hedera-enabling-dynamic-nfts-on-hedera-exploring-hip-646-hip-657-and-hip-765.txt item: #1653 of 3327 id: hedera-enoughtea-foundation-and-maltin-on-movies-ukraine-filmfest-launches-in-la-and-london-with-nft-auction-aiming-to-raise-funds-for-ukrainian-citizens author: hedera title: hedera-enoughtea-foundation-and-maltin-on-movies-ukraine-filmfest-launches-in-la-and-london-with-nft-auction-aiming-to-raise-funds-for-ukrainian-citizens date: None words: 1649 flesch: 55 summary: www.cgcreative.com For Media Enquiries Zenobia Godschalk Hedera [email protected] Share This Back to blog What is gRPC, gRPC-Web, and Proxies? Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: ecosystem; enoughtea; event; hedera; maltin; network; ukraine; united24 cache: hedera-enoughtea-foundation-and-maltin-on-movies-ukraine-filmfest-launches-in-la-and-london-with-nft-auction-aiming-to-raise-funds-for-ukrainian-citizens.html plain text: hedera-enoughtea-foundation-and-maltin-on-movies-ukraine-filmfest-launches-in-la-and-london-with-nft-auction-aiming-to-raise-funds-for-ukrainian-citizens.txt item: #1654 of 3327 id: hedera-eqty-lab-brings-open-source-ai-integrity-framework-to-hugging-face-community-with-industry-first-native-hedera-blockchain-integration author: hedera title: hedera-eqty-lab-brings-open-source-ai-integrity-framework-to-hugging-face-community-with-industry-first-native-hedera-blockchain-integration date: None words: 1342 flesch: 51 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: ecosystem; eqty; hedera; integrity; lab; network cache: hedera-eqty-lab-brings-open-source-ai-integrity-framework-to-hugging-face-community-with-industry-first-native-hedera-blockchain-integration.html plain text: hedera-eqty-lab-brings-open-source-ai-integrity-framework-to-hugging-face-community-with-industry-first-native-hedera-blockchain-integration.txt item: #1655 of 3327 id: hedera-eqty-labs-verifiable-compute-brings-trust-to-ai-with-hedera author: hedera title: hedera-eqty-labs-verifiable-compute-brings-trust-to-ai-with-hedera date: None words: 1420 flesch: 48 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: compute; ecosystem; hedera; lab; network; trust cache: hedera-eqty-labs-verifiable-compute-brings-trust-to-ai-with-hedera.html plain text: hedera-eqty-labs-verifiable-compute-brings-trust-to-ai-with-hedera.txt item: #1656 of 3327 id: hedera-everyware-and-hedera-hashgraph-enabling-cold-chain-monitoring-of-covid-19-vaccine-for-nhs-facilities author: hedera title: hedera-everyware-and-hedera-hashgraph-enabling-cold-chain-monitoring-of-covid-19-vaccine-for-nhs-facilities date: None words: 1481 flesch: 46 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: asset; chain; ecosystem; everyware; hedera; monitoring; network cache: hedera-everyware-and-hedera-hashgraph-enabling-cold-chain-monitoring-of-covid-19-vaccine-for-nhs-facilities.html plain text: hedera-everyware-and-hedera-hashgraph-enabling-cold-chain-monitoring-of-covid-19-vaccine-for-nhs-facilities.txt item: #1657 of 3327 id: hedera-exploring-tokenized-assets-on-hedera-consensus-service-part-1 author: hedera title: hedera-exploring-tokenized-assets-on-hedera-consensus-service-part-1 date: None words: 1622 flesch: 58 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: consensus; developer; ecosystem; hcs; hedera; network; service cache: hedera-exploring-tokenized-assets-on-hedera-consensus-service-part-1.html plain text: hedera-exploring-tokenized-assets-on-hedera-consensus-service-part-1.txt item: #1658 of 3327 id: hedera-exploring-tokenized-assets-on-hedera-consensus-service-part-2 author: hedera title: hedera-exploring-tokenized-assets-on-hedera-consensus-service-part-2 date: None words: 2033 flesch: 56 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: application; consensus; hcs; hedera; network; server; service cache: hedera-exploring-tokenized-assets-on-hedera-consensus-service-part-2.html plain text: hedera-exploring-tokenized-assets-on-hedera-consensus-service-part-2.txt item: #1659 of 3327 id: hedera-exploring-tokenized-assets-on-hedera-consensus-service-part-3 author: hedera title: hedera-exploring-tokenized-assets-on-hedera-consensus-service-part-3 date: None words: 2463 flesch: 51 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: address; construct; hedera; network; string; system.out.println; token cache: hedera-exploring-tokenized-assets-on-hedera-consensus-service-part-3.html plain text: hedera-exploring-tokenized-assets-on-hedera-consensus-service-part-3.txt item: #1660 of 3327 id: hedera-exploring-tokenized-assets-on-hedera-consensus-service-part-4 author: hedera title: hedera-exploring-tokenized-assets-on-hedera-consensus-service-part-4 date: None words: 2317 flesch: 49 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: application; consensus; hedera; message; mirror; network; node; token cache: hedera-exploring-tokenized-assets-on-hedera-consensus-service-part-4.html plain text: hedera-exploring-tokenized-assets-on-hedera-consensus-service-part-4.txt item: #1661 of 3327 id: hedera-fair-access-v-fair-ordering-and-transactions-per-second-examined-and-explained author: hedera title: hedera-fair-access-v-fair-ordering-and-transactions-per-second-examined-and-explained date: None words: 3013 flesch: 60 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: access; client; consensus; hedera; network; node; order; transaction cache: hedera-fair-access-v-fair-ordering-and-transactions-per-second-examined-and-explained.html plain text: hedera-fair-access-v-fair-ordering-and-transactions-per-second-examined-and-explained.txt item: #1662 of 3327 id: hedera-fair-timestamping-and-fair-ordering-of-transactions author: hedera title: hedera-fair-timestamping-and-fair-ordering-of-transactions date: None words: 3835 flesch: 72 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: alice; bob; carol; computers; hedera; order; timestamps cache: hedera-fair-timestamping-and-fair-ordering-of-transactions.html plain text: hedera-fair-timestamping-and-fair-ordering-of-transactions.txt item: #1663 of 3327 id: hedera-filecoin-and-hedera-hashgraph-announce-grant-program-to-propel-web3-interoperability author: hedera title: hedera-filecoin-and-hedera-hashgraph-announce-grant-program-to-propel-web3-interoperability date: None words: 1646 flesch: 52 summary: HIP-10: Bringing Filecoin Decentralized Storage to Hedera NFTs The Hedera Token Service (HTS) enables the configuration, management, and transfer of native non-fungible tokens (NFTs) on the Hedera platform. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: data; ecosystem; filecoin; hedera; network; nfts; storage cache: hedera-filecoin-and-hedera-hashgraph-announce-grant-program-to-propel-web3-interoperability.html plain text: hedera-filecoin-and-hedera-hashgraph-announce-grant-program-to-propel-web3-interoperability.txt item: #1664 of 3327 id: hedera-finality-of-consensus-you-can-take-it-to-the-bank-or-maybe-you-are-the-bank author: hedera title: hedera-finality-of-consensus-you-can-take-it-to-the-bank-or-maybe-you-are-the-bank date: None words: 2361 flesch: 63 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: block; chain; hedera; network; nodes; transaction; witnesses cache: hedera-finality-of-consensus-you-can-take-it-to-the-bank-or-maybe-you-are-the-bank.html plain text: hedera-finality-of-consensus-you-can-take-it-to-the-bank-or-maybe-you-are-the-bank.txt item: #1665 of 3327 id: hedera-formal-methods-the-importance-of-being-abft-in-a-world-with-bad-actors author: hedera title: hedera-formal-methods-the-importance-of-being-abft-in-a-world-with-bad-actors date: None words: 1779 flesch: 57 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: abft; consensus; ecosystem; hedera; network; node; proof cache: hedera-formal-methods-the-importance-of-being-abft-in-a-world-with-bad-actors.html plain text: hedera-formal-methods-the-importance-of-being-abft-in-a-world-with-bad-actors.txt item: #1666 of 3327 id: hedera-former-government-and-finance-leaders-take-up-executive-roles-with-hedera author: hedera title: hedera-former-government-and-finance-leaders-take-up-executive-roles-with-hedera date: None words: 1468 flesch: 47 summary: For Media Enquiries Zenobia Godschalk Hedera Hashgraph [email protected] Share This Back to blog What is gRPC, gRPC-Web, and Proxies? Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: council; ecosystem; executive; hedera; network; policy; team cache: hedera-former-government-and-finance-leaders-take-up-executive-roles-with-hedera.html plain text: hedera-former-government-and-finance-leaders-take-up-executive-roles-with-hedera.txt item: #1667 of 3327 id: hedera-fp-complete-publishes-results-of-independent-3rd-party-audits-of-hedera-platform-and-new-hedera-token-service author: hedera title: hedera-fp-complete-publishes-results-of-independent-3rd-party-audits-of-hedera-platform-and-new-hedera-token-service date: None words: 1228 flesch: 50 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. FP Complete Development specialists conducted comprehensive review of Hedera’s code and technical documentation Zug, Switzerland – February 9, 2021 – As part of its goal to deliver transparency to the development community, Hedera Hashgraph, the enterprise-grade public distributed ledger, engaged FP Complete, an IT engineering specialist, to perform an independent audit of the engineering work by Hedera’s development team on the Hedera platform, including the new Hedera Token Service. keywords: complete; ecosystem; engineering; hedera; network cache: hedera-fp-complete-publishes-results-of-independent-3rd-party-audits-of-hedera-platform-and-new-hedera-token-service.html plain text: hedera-fp-complete-publishes-results-of-independent-3rd-party-audits-of-hedera-platform-and-new-hedera-token-service.txt item: #1668 of 3327 id: hedera-fragility-in-dlts author: hedera title: hedera-fragility-in-dlts date: None words: 2115 flesch: 64 summary: The burden on Hedera nodes for calculating consensus is therefore, at any moment in time, to know how many hbars are in all staked accounts (unstaked accounts are immaterial). In practice, as an optimization, Hedera nodes will take a snapshot of hbar balances (and so node stake) every 24 hours and use those values for the following 24 hours. keywords: consensus; hbars; hedera; influence; nodes; stake cache: hedera-fragility-in-dlts.html plain text: hedera-fragility-in-dlts.txt item: #1669 of 3327 id: hedera-gdpr-ccpa-privacy-compliance-consensus-service author: hedera title: hedera-gdpr-ccpa-privacy-compliance-consensus-service date: None words: 1297 flesch: 55 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: consent; data; gdpr; hedera; network; search cache: hedera-gdpr-ccpa-privacy-compliance-consensus-service.html plain text: hedera-gdpr-ccpa-privacy-compliance-consensus-service.txt item: #1670 of 3327 id: hedera-get-ready-for-the-updated-security-model-of-the-hedera-smart-contract-service-by-july-2023 author: hedera title: hedera-get-ready-for-the-updated-security-model-of-the-hedera-smart-contract-service-by-july-2023 date: None words: 1258 flesch: 58 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: contract; hedera; key; model; security; token cache: hedera-get-ready-for-the-updated-security-model-of-the-hedera-smart-contract-service-by-july-2023.html plain text: hedera-get-ready-for-the-updated-security-model-of-the-hedera-smart-contract-service-by-july-2023.txt item: #1671 of 3327 id: hedera-get-started-with-hcs-and-javascript author: hedera title: hedera-get-started-with-hcs-and-javascript date: None words: 1681 flesch: 49 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: const; hcs; hedera; new; node; topic cache: hedera-get-started-with-hcs-and-javascript.html plain text: hedera-get-started-with-hcs-and-javascript.txt item: #1672 of 3327 id: hedera-get-started-with-javascript author: hedera title: hedera-get-started-with-javascript date: None words: 1790 flesch: 57 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. * call our async function */ main(); With that you’ve successfully set up your Node.js environment for Hedera development, and can start moving onto using other Hedera network services. keywords: client; const; hedera; network; sdk; testnet cache: hedera-get-started-with-javascript.html plain text: hedera-get-started-with-javascript.txt item: #1673 of 3327 id: hedera-get-started-with-the-hedera-token-service-part-1 author: hedera title: hedera-get-started-with-the-hedera-token-service-part-1 date: None words: 1460 flesch: 50 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: const; hedera; receipt; token; transaction cache: hedera-get-started-with-the-hedera-token-service-part-1.html plain text: hedera-get-started-with-the-hedera-token-service-part-1.txt item: #1674 of 3327 id: hedera-get-started-with-the-hedera-token-service-part-1-how-to-mint-nfts author: hedera title: hedera-get-started-with-the-hedera-token-service-part-1-how-to-mint-nfts date: None words: 2806 flesch: 48 summary: Create New Hedera Accounts and Generate Keys for the NFT Let's create additional Hedera accounts to represent users for this scenario like the Treasury, Alice, and Bob. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: = =; account; await; hedera; new; nft; nfts; token cache: hedera-get-started-with-the-hedera-token-service-part-1-how-to-mint-nfts.html plain text: hedera-get-started-with-the-hedera-token-service-part-1-how-to-mint-nfts.txt item: #1675 of 3327 id: hedera-get-started-with-the-hedera-token-service-part-2 author: hedera title: hedera-get-started-with-the-hedera-token-service-part-2 date: None words: 1387 flesch: 54 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: const; hedera; network; token; transaction cache: hedera-get-started-with-the-hedera-token-service-part-2.html plain text: hedera-get-started-with-the-hedera-token-service-part-2.txt item: #1676 of 3327 id: hedera-get-started-with-the-hedera-token-service-part-2-kyc-update-and-scheduled-transactions author: hedera title: hedera-get-started-with-the-hedera-token-service-part-2-kyc-update-and-scheduled-transactions date: None words: 2222 flesch: 55 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: = =; await; hedera; kyc; new; token cache: hedera-get-started-with-the-hedera-token-service-part-2-kyc-update-and-scheduled-transactions.html plain text: hedera-get-started-with-the-hedera-token-service-part-2-kyc-update-and-scheduled-transactions.txt item: #1677 of 3327 id: hedera-get-started-with-the-hedera-token-service-part-3 author: hedera title: hedera-get-started-with-the-hedera-token-service-part-3 date: None words: 1596 flesch: 53 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: await; const; hedera; token; transaction cache: hedera-get-started-with-the-hedera-token-service-part-3.html plain text: hedera-get-started-with-the-hedera-token-service-part-3.txt item: #1678 of 3327 id: hedera-get-started-with-the-hedera-token-service-part-3-how-to-pause-freeze-wipe-and-delete-nfts author: hedera title: hedera-get-started-with-the-hedera-token-service-part-3-how-to-pause-freeze-wipe-and-delete-nfts date: None words: 1911 flesch: 57 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: account; await; hedera; let; token cache: hedera-get-started-with-the-hedera-token-service-part-3-how-to-pause-freeze-wipe-and-delete-nfts.html plain text: hedera-get-started-with-the-hedera-token-service-part-3-how-to-pause-freeze-wipe-and-delete-nfts.txt item: #1679 of 3327 id: hedera-getting-started-guide author: hedera title: hedera-getting-started-guide date: None words: 2002 flesch: 63 summary: Step 2 - Set up your local development environment With Hedera SDKs, we make it extremely easy to get started in familiar languages. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: account; demo; developer; hbar; hedera; network; use cache: hedera-getting-started-guide.html plain text: hedera-getting-started-guide.txt item: #1680 of 3327 id: hedera-going-carbon-negative-at-hedera-hashgraph author: hedera title: hedera-going-carbon-negative-at-hedera-hashgraph date: None words: 1620 flesch: 43 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. As a tangible example, Hedera network operation emissions for Q2 2021 were 20 metric tonnes of CO2. keywords: carbon; ecosystem; energy; hedera; network; nodes; public cache: hedera-going-carbon-negative-at-hedera-hashgraph.html plain text: hedera-going-carbon-negative-at-hedera-hashgraph.txt item: #1681 of 3327 id: hedera-guardian-v2-0-the-next-generation-of-esg-marketplaces-built-on-hedera author: hedera title: hedera-guardian-v2-0-the-next-generation-of-esg-marketplaces-built-on-hedera date: None words: 1885 flesch: 39 summary: This limitation forced us to create our own implementation of publishing messages to Hedera topics. Guardian v2.0 delivers new features to expand on what was built and grow the Hedera Guardian ecosystem. keywords: assets; ecosystem; esg; guardian; hedera; policy; testnet; type cache: hedera-guardian-v2-0-the-next-generation-of-esg-marketplaces-built-on-hedera.html plain text: hedera-guardian-v2-0-the-next-generation-of-esg-marketplaces-built-on-hedera.txt item: #1682 of 3327 id: hedera-hala-systems-leverages-hedera-hashgraph-to-deliver-early-warning-of-conflict-to-2-1-million-syrians author: hedera title: hedera-hala-systems-leverages-hedera-hashgraph-to-deliver-early-warning-of-conflict-to-2-1-million-syrians date: None words: 1485 flesch: 50 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: data; ecosystem; hala; hedera; media; network; systems cache: hedera-hala-systems-leverages-hedera-hashgraph-to-deliver-early-warning-of-conflict-to-2-1-million-syrians.html plain text: hedera-hala-systems-leverages-hedera-hashgraph-to-deliver-early-warning-of-conflict-to-2-1-million-syrians.txt item: #1683 of 3327 id: hedera-hashconnect-secure-signing-for-dapps-built-on-hedera author: hedera title: hedera-hashconnect-secure-signing-for-dapps-built-on-hedera date: None words: 1312 flesch: 58 summary: HashConnect Basic Concepts The main functionality of HashConnect is to send Hedera transactions to a wallet to be signed and executed by a user. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: application; ecosystem; hashconnect; hedera; network; user cache: hedera-hashconnect-secure-signing-for-dapps-built-on-hedera.html plain text: hedera-hashconnect-secure-signing-for-dapps-built-on-hedera.txt item: #1684 of 3327 id: hedera-hashgraph-chess author: hedera title: hedera-hashgraph-chess date: None words: 2013 flesch: 63 summary: This does not solve the issue of the subscription limit for Hedera clients. There are two ways we could organize the relationship between Hedera clients and gRPC subscriptions: The server could scale in and out a fleet of Hedera clients, whose purpose is to subscribe to topics and broadcast their information to the socket.io rooms. keywords: chess; clients; game; gamestate; hedera; match; topic cache: hedera-hashgraph-chess.html plain text: hedera-hashgraph-chess.txt item: #1685 of 3327 id: hedera-hbar-foundation-and-ubisoft-partner-to-support-growth-of-gaming-on-hedera-network author: hedera title: hedera-hbar-foundation-and-ubisoft-partner-to-support-growth-of-gaming-on-hedera-network date: None words: 1505 flesch: 49 summary: For additional information, please visit www.hbarfoundation.org or follow the Foundation on Twitter at HBAR_foundation. # # # # PR Contacts: The HBAR Foundation [email protected] Ubisoft Paul Grand [email protected] Share This Back to blog What is gRPC, gRPC-Web, and Proxies? Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: ecosystem; foundation; hbar; hedera; network; ubisoft cache: hedera-hbar-foundation-and-ubisoft-partner-to-support-growth-of-gaming-on-hedera-network.html plain text: hedera-hbar-foundation-and-ubisoft-partner-to-support-growth-of-gaming-on-hedera-network.txt item: #1686 of 3327 id: hedera-hedera-adopts-chainlink-standard-for-cross-chain-interoperability-to-accelerate-ecosystem-adoption author: hedera title: hedera-hedera-adopts-chainlink-standard-for-cross-chain-interoperability-to-accelerate-ecosystem-adoption date: None words: 1393 flesch: 54 summary: HBAR Foundation joined the Chainlink Scale program last year to provide Hedera developers with enhanced access to Chainlink’s high-quality oracle services. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: ccip; chain; chainlink; cross; hedera; network cache: hedera-hedera-adopts-chainlink-standard-for-cross-chain-interoperability-to-accelerate-ecosystem-adoption.html plain text: hedera-hedera-adopts-chainlink-standard-for-cross-chain-interoperability-to-accelerate-ecosystem-adoption.txt item: #1687 of 3327 id: hedera-hedera-adopts-the-chainlink-data-standard-to-accelerate-defi-and-tokenized-rwa-adoption author: hedera title: hedera-hedera-adopts-the-chainlink-data-standard-to-accelerate-defi-and-tokenized-rwa-adoption date: None words: 1605 flesch: 49 summary: The HBAR Foundation recently joined Chainlink Scale to provide Hedera developers with enhanced access to Chainlink’s high-quality oracle services. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: chainlink; data; feeds; hedera; network; proof; reserve cache: hedera-hedera-adopts-the-chainlink-data-standard-to-accelerate-defi-and-tokenized-rwa-adoption.html plain text: hedera-hedera-adopts-the-chainlink-data-standard-to-accelerate-defi-and-tokenized-rwa-adoption.txt item: #1688 of 3327 id: hedera-hedera-appoints-well-known-open-source-leader-to-spearhead-open-source-transformation author: hedera title: hedera-hedera-appoints-well-known-open-source-leader-to-spearhead-open-source-transformation date: None words: 1513 flesch: 54 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: community; council; ecosystem; hedera; network; open; source; web3 cache: hedera-hedera-appoints-well-known-open-source-leader-to-spearhead-open-source-transformation.html plain text: hedera-hedera-appoints-well-known-open-source-leader-to-spearhead-open-source-transformation.txt item: #1689 of 3327 id: hedera-hedera-cfo-betsabe-botaitis-selected-as-top-honoree-at-nasdaqs-latina-disruptors-event author: hedera title: hedera-hedera-cfo-betsabe-botaitis-selected-as-top-honoree-at-nasdaqs-latina-disruptors-event date: None words: 1476 flesch: 51 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: bank; botaitis; ecosystem; hedera; inclusion; latina; network cache: hedera-hedera-cfo-betsabe-botaitis-selected-as-top-honoree-at-nasdaqs-latina-disruptors-event.html plain text: hedera-hedera-cfo-betsabe-botaitis-selected-as-top-honoree-at-nasdaqs-latina-disruptors-event.txt item: #1690 of 3327 id: hedera-hedera-consensus-service-and-mvc-track-and-trace-platform-now-fully-integrated-for-pharmaceutical-supply-chain-compliance-and-finance author: hedera title: hedera-hedera-consensus-service-and-mvc-track-and-trace-platform-now-fully-integrated-for-pharmaceutical-supply-chain-compliance-and-finance date: None words: 1482 flesch: 49 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: chain; global; hedera; mvc; network; platform; supply cache: hedera-hedera-consensus-service-and-mvc-track-and-trace-platform-now-fully-integrated-for-pharmaceutical-supply-chain-compliance-and-finance.html plain text: hedera-hedera-consensus-service-and-mvc-track-and-trace-platform-now-fully-integrated-for-pharmaceutical-supply-chain-compliance-and-finance.txt item: #1691 of 3327 id: hedera-hedera-council-adds-hitachi-america-ltd-as-newest-member-bringing-potential-for-real-world-industrial-solutions-built-on-hederas-dlt author: hedera title: hedera-hedera-council-adds-hitachi-america-ltd-as-newest-member-bringing-potential-for-real-world-industrial-solutions-built-on-hederas-dlt date: None words: 1387 flesch: 47 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: america; council; ecosystem; hedera; hitachi; network; solutions cache: hedera-hedera-council-adds-hitachi-america-ltd-as-newest-member-bringing-potential-for-real-world-industrial-solutions-built-on-hederas-dlt.html plain text: hedera-hedera-council-adds-hitachi-america-ltd-as-newest-member-bringing-potential-for-real-world-industrial-solutions-built-on-hederas-dlt.txt item: #1692 of 3327 id: hedera-hedera-developer-highlights-december-2024 author: hedera title: hedera-hedera-developer-highlights-december-2024 date: None words: 668 flesch: 56 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: developer; ecosystem; hedera; network cache: hedera-hedera-developer-highlights-december-2024.html plain text: hedera-hedera-developer-highlights-december-2024.txt item: #1693 of 3327 id: hedera-hedera-developer-highlights-february-2025 author: hedera title: hedera-hedera-developer-highlights-february-2025 date: None words: 668 flesch: 55 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: developer; ecosystem; hedera; network cache: hedera-hedera-developer-highlights-february-2025.html plain text: hedera-hedera-developer-highlights-february-2025.txt item: #1694 of 3327 id: hedera-hedera-developer-highlights-january-2025 author: hedera title: hedera-hedera-developer-highlights-january-2025 date: None words: 668 flesch: 56 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: developer; ecosystem; hedera; network cache: hedera-hedera-developer-highlights-january-2025.html plain text: hedera-hedera-developer-highlights-january-2025.txt item: #1695 of 3327 id: hedera-hedera-developer-highlights-july-2024 author: hedera title: hedera-hedera-developer-highlights-july-2024 date: None words: 668 flesch: 56 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: developer; ecosystem; hedera; network cache: hedera-hedera-developer-highlights-july-2024.html plain text: hedera-hedera-developer-highlights-july-2024.txt item: #1696 of 3327 id: hedera-hedera-developer-highlights-march-2025 author: hedera title: hedera-hedera-developer-highlights-march-2025 date: None words: 671 flesch: 56 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. HBAR The Hedera network's native cryptocurrency. keywords: developer; ecosystem; hedera; network cache: hedera-hedera-developer-highlights-march-2025.html plain text: hedera-hedera-developer-highlights-march-2025.txt item: #1697 of 3327 id: hedera-hedera-developer-highlights-november-2024 author: hedera title: hedera-hedera-developer-highlights-november-2024 date: None words: 668 flesch: 56 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: developer; ecosystem; hedera; network cache: hedera-hedera-developer-highlights-november-2024.html plain text: hedera-hedera-developer-highlights-november-2024.txt item: #1698 of 3327 id: hedera-hedera-developer-highlights-october-2024 author: hedera title: hedera-hedera-developer-highlights-october-2024 date: None words: 668 flesch: 55 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: developer; ecosystem; hedera; network cache: hedera-hedera-developer-highlights-october-2024.html plain text: hedera-hedera-developer-highlights-october-2024.txt item: #1699 of 3327 id: hedera-hedera-developer-highlights-september-2024 author: hedera title: hedera-hedera-developer-highlights-september-2024 date: None words: 668 flesch: 56 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: developer; ecosystem; hedera; network cache: hedera-hedera-developer-highlights-september-2024.html plain text: hedera-hedera-developer-highlights-september-2024.txt item: #1700 of 3327 id: hedera-hedera-developer-newsletter-august-2024 author: hedera title: hedera-hedera-developer-newsletter-august-2024 date: None words: 670 flesch: 56 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: developer; ecosystem; hedera; network cache: hedera-hedera-developer-newsletter-august-2024.html plain text: hedera-hedera-developer-newsletter-august-2024.txt item: #1701 of 3327 id: hedera-hedera-developer-newsletter-february-2024 author: hedera title: hedera-hedera-developer-newsletter-february-2024 date: None words: 670 flesch: 55 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: developer; ecosystem; hedera; network cache: hedera-hedera-developer-newsletter-february-2024.html plain text: hedera-hedera-developer-newsletter-february-2024.txt item: #1702 of 3327 id: hedera-hedera-developer-newsletter-january-2024 author: hedera title: hedera-hedera-developer-newsletter-january-2024 date: None words: 670 flesch: 56 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: developer; ecosystem; hedera; network cache: hedera-hedera-developer-newsletter-january-2024.html plain text: hedera-hedera-developer-newsletter-january-2024.txt item: #1703 of 3327 id: hedera-hedera-developer-newsletter-march-2024 author: hedera title: hedera-hedera-developer-newsletter-march-2024 date: None words: 670 flesch: 56 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: developer; ecosystem; hedera; network cache: hedera-hedera-developer-newsletter-march-2024.html plain text: hedera-hedera-developer-newsletter-march-2024.txt item: #1704 of 3327 id: hedera-hedera-developer-newsletter-may-2024 author: hedera title: hedera-hedera-developer-newsletter-may-2024 date: None words: 670 flesch: 56 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: developer; ecosystem; hedera; network cache: hedera-hedera-developer-newsletter-may-2024.html plain text: hedera-hedera-developer-newsletter-may-2024.txt item: #1705 of 3327 id: hedera-hedera-engineering-insights-july-2020 author: hedera title: hedera-hedera-engineering-insights-july-2020 date: None words: 2689 flesch: 62 summary: When is Hedera mainnet coming out of beta? Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: community; developer; hedera; mainnet; members; network; previewnet; testnet cache: hedera-hedera-engineering-insights-july-2020.html plain text: hedera-hedera-engineering-insights-july-2020.txt item: #1706 of 3327 id: hedera-hedera-evm-smart-contracts-now-bring-highest-speed-programmability-to-tokenization author: hedera title: hedera-hedera-evm-smart-contracts-now-bring-highest-speed-programmability-to-tokenization date: None words: 1334 flesch: 55 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: applications; carbon; contracts; ecosystem; hedera; network; service cache: hedera-hedera-evm-smart-contracts-now-bring-highest-speed-programmability-to-tokenization.html plain text: hedera-hedera-evm-smart-contracts-now-bring-highest-speed-programmability-to-tokenization.txt item: #1707 of 3327 id: hedera-hedera-fee-model-for-transactions-queries author: hedera title: hedera-hedera-fee-model-for-transactions-queries date: None words: 2953 flesch: 57 summary: Clients will be able to dynamically calculate transaction fees and some query payments using the current fee schedule and exchange rate, and so precisely specify these on transactions and query payments – avoiding failed transactions from insufficient fees and the risk of overpayment. Of course, that transaction fee can be safely overestimated, and only the appropriate amount will be deducted. keywords: client; fee; hedera; network; payment; query; transaction cache: hedera-hedera-fee-model-for-transactions-queries.html plain text: hedera-hedera-fee-model-for-transactions-queries.txt item: #1708 of 3327 id: hedera-hedera-governing-council-to-allocate-5-billion-in-hbar-to-independent-foundation-and-ecosystem-development-initiatives author: hedera title: hedera-hedera-governing-council-to-allocate-5-billion-in-hbar-to-independent-foundation-and-ecosystem-development-initiatives date: None words: 1399 flesch: 49 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. “We believe that for the Hedera network to reach its full potential as the trust layer of the internet, we must continue its strategy of decentralizing the governance of the ecosystem, which started with its unique Hedera Governing Council structure,” said Mark Radcliffe, Partner at DLA Piper, a member of the Hedera Governing Council. keywords: council; ecosystem; governing; hbar; hedera; network; organizations cache: hedera-hedera-governing-council-to-allocate-5-billion-in-hbar-to-independent-foundation-and-ecosystem-development-initiatives.html plain text: hedera-hedera-governing-council-to-allocate-5-billion-in-hbar-to-independent-foundation-and-ecosystem-development-initiatives.txt item: #1709 of 3327 id: hedera-hedera-governing-council-votes-to-purchase-hashgraph-ip-commits-to-open-source-worlds-most-advanced-distributed-ledger-technology author: hedera title: hedera-hedera-governing-council-votes-to-purchase-hashgraph-ip-commits-to-open-source-worlds-most-advanced-distributed-ledger-technology date: None words: 1958 flesch: 47 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Mance Harmon, CEO of Hedera Hashgraph, and Dr. Leemon Baird, Chief Scientist of Hedera Hashgraph, will leave those positions, which are being dissolved, and will continue to participate in the Hedera ecosystem as peer members of the Governing Council through Swirlds, where they are CEO and CTO, respectively. keywords: council; ecosystem; governance; hashgraph; hedera; members; network; swirlds cache: hedera-hedera-governing-council-votes-to-purchase-hashgraph-ip-commits-to-open-source-worlds-most-advanced-distributed-ledger-technology.html plain text: hedera-hedera-governing-council-votes-to-purchase-hashgraph-ip-commits-to-open-source-worlds-most-advanced-distributed-ledger-technology.txt item: #1710 of 3327 id: hedera-hedera-hashgraph-and-application-partners-collaborate-with-the-interwork-alliance-on-sustainability-working-group-key-initiatives author: hedera title: hedera-hedera-hashgraph-and-application-partners-collaborate-with-the-interwork-alliance-on-sustainability-working-group-key-initiatives date: None words: 1988 flesch: 41 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Yonathan Lapchik, CEO at SUKU ### About Hedera Hashgraph Hedera is the most used enterprise-grade public network for the decentralized economy. keywords: alliance; carbon; ecosystem; hedera; interwork; network; standards; sustainability; token cache: hedera-hedera-hashgraph-and-application-partners-collaborate-with-the-interwork-alliance-on-sustainability-working-group-key-initiatives.html plain text: hedera-hedera-hashgraph-and-application-partners-collaborate-with-the-interwork-alliance-on-sustainability-working-group-key-initiatives.txt item: #1711 of 3327 id: hedera-hedera-hashgraph-and-chainlink-collaborate-to-provide-a-decentralized-oracle-network-for-hederas-enterprise-grade-distributed-public-ledger author: hedera title: hedera-hedera-hashgraph-and-chainlink-collaborate-to-provide-a-decentralized-oracle-network-for-hederas-enterprise-grade-distributed-public-ledger date: None words: 1262 flesch: 52 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. What's New Partners Papers Careers Media Blog Technical Press Podcast Community Events Meetups Store Brand Navigation QUICKSTART Hedera Hashgraph and Chainlink Collaborate to Provide a Decentralized Oracle Network for Hedera's Enterprise-Grade Distributed Public Ledger news May 08, 2019 by Hedera Team Hedera is the most used, sustainable, enterprise-grade public network for the decentralized economy. keywords: applications; chainlink; contracts; ecosystem; hedera; network cache: hedera-hedera-hashgraph-and-chainlink-collaborate-to-provide-a-decentralized-oracle-network-for-hederas-enterprise-grade-distributed-public-ledger.html plain text: hedera-hedera-hashgraph-and-chainlink-collaborate-to-provide-a-decentralized-oracle-network-for-hederas-enterprise-grade-distributed-public-ledger.txt item: #1712 of 3327 id: hedera-hedera-hashgraph-and-lcx-to-develop-infrastructure-for-digital-securities author: hedera title: hedera-hedera-hashgraph-and-lcx-to-develop-infrastructure-for-digital-securities date: None words: 1341 flesch: 49 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. It has been wonderful to see the wide array of innovative applications in the Hedera ecosystem, said Leemon Baird, CTO and Co-Founder of Hedera Hashgraph. keywords: blockchain; ecosystem; hashgraph; hedera; lcx; network; token cache: hedera-hedera-hashgraph-and-lcx-to-develop-infrastructure-for-digital-securities.html plain text: hedera-hedera-hashgraph-and-lcx-to-develop-infrastructure-for-digital-securities.txt item: #1713 of 3327 id: hedera-hedera-hashgraph-and-trm-labs-new-integration-provides-industry-leading-security-and-compliance author: hedera title: hedera-hedera-hashgraph-and-trm-labs-new-integration-provides-industry-leading-security-and-compliance date: None words: 1527 flesch: 48 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. AML/CFT Compliance Solutions Now Available for HBAR and Any Assets Issued on Hedera San Francisco, CA and Dallas, TX – December 21, 2020 – Hedera Hashgraph, the enterprise-grade distributed ledger, and TRM, the cryptocurrency compliance and risk management platform, today announced that TRM has successfully integrated with the Hedera public ledger, and customers can leverage the integration to comply with Anti-Money Laundering/Combating the Financing of Terrorism (AML/CFT) regulatory requirements. keywords: aml; compliance; ecosystem; hbar; hedera; network; trm cache: hedera-hedera-hashgraph-and-trm-labs-new-integration-provides-industry-leading-security-and-compliance.html plain text: hedera-hedera-hashgraph-and-trm-labs-new-integration-provides-industry-leading-security-and-compliance.txt item: #1714 of 3327 id: hedera-hedera-hashgraph-announces-initial-group-of-governing-council-members author: hedera title: hedera-hedera-hashgraph-announces-initial-group-of-governing-council-members date: None words: 1786 flesch: 47 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: blockchain; council; governance; hashgraph; hedera; ledger; network cache: hedera-hedera-hashgraph-announces-initial-group-of-governing-council-members.html plain text: hedera-hedera-hashgraph-announces-initial-group-of-governing-council-members.txt item: #1715 of 3327 id: hedera-hedera-hashgraph-announces-ledger-nano-s-and-nano-x-wallet-implementations author: hedera title: hedera-hedera-hashgraph-announces-ledger-nano-s-and-nano-x-wallet-implementations date: None words: 1252 flesch: 54 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: ecosystem; hedera; ledger; nano; network; public cache: hedera-hedera-hashgraph-announces-ledger-nano-s-and-nano-x-wallet-implementations.html plain text: hedera-hedera-hashgraph-announces-ledger-nano-s-and-nano-x-wallet-implementations.txt item: #1716 of 3327 id: hedera-hedera-hashgraph-announces-mainnet-launch-of-evm-compatible-smart-contracts-2-0 author: hedera title: hedera-hedera-hashgraph-announces-mainnet-launch-of-evm-compatible-smart-contracts-2-0 date: None words: 1248 flesch: 53 summary: Hedera Smart Contracts 2.0 comes at a significant time for the organization, following the recent announcement of the move to open source hashgraph, to mark the Hedera codebase open source in its entirety. For Media Enquiries Zenobia Godschalk Hedera Hashgraph [email protected] Share This Back to blog What is gRPC, gRPC-Web, and Proxies? Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: contracts; ecosystem; hashgraph; hedera; network; service cache: hedera-hedera-hashgraph-announces-mainnet-launch-of-evm-compatible-smart-contracts-2-0.html plain text: hedera-hedera-hashgraph-announces-mainnet-launch-of-evm-compatible-smart-contracts-2-0.txt item: #1717 of 3327 id: hedera-hedera-hashgraph-co-founders-mance-harmon-and-dr-leemon-baird-win-emerging-company-ceo-and-technology-inventor-at-tech-titans-awards author: hedera title: hedera-hedera-hashgraph-co-founders-mance-harmon-and-dr-leemon-baird-win-emerging-company-ceo-and-technology-inventor-at-tech-titans-awards date: None words: 1291 flesch: 51 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Mance Harmon, Co-founder of Hedera Hashgraph, said: “These wins are a testament to the hard work and dedication of Hedera’s community, developers, partners, and council members. keywords: ecosystem; hashgraph; hedera; network; tech; technology; titans cache: hedera-hedera-hashgraph-co-founders-mance-harmon-and-dr-leemon-baird-win-emerging-company-ceo-and-technology-inventor-at-tech-titans-awards.html plain text: hedera-hedera-hashgraph-co-founders-mance-harmon-and-dr-leemon-baird-win-emerging-company-ceo-and-technology-inventor-at-tech-titans-awards.txt item: #1718 of 3327 id: hedera-hedera-hashgraph-joins-world-wide-web-consortium-w3c-new-did-method-published-by-w3c-credentials-community-group author: hedera title: hedera-hedera-hashgraph-joins-world-wide-web-consortium-w3c-new-did-method-published-by-w3c-credentials-community-group date: None words: 1497 flesch: 50 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. “By adding DID Method functionality to their public ledger, Hedera has further validated market demand for decentralized identity functionality and the emerging industry specifications from W3C that enable it.” Paul Madsen, Technical Lead at Hedera Hashgraph, noted, “Our W3C membership and active engagement across various identity, payment and security working groups demonstrates our commitment to contribute to the future of the internet - ensuring that the Web is safe, secure, and efficient for all. keywords: ecosystem; hashgraph; hedera; network; w3c; web; world cache: hedera-hedera-hashgraph-joins-world-wide-web-consortium-w3c-new-did-method-published-by-w3c-credentials-community-group.html plain text: hedera-hedera-hashgraph-joins-world-wide-web-consortium-w3c-new-did-method-published-by-w3c-credentials-community-group.txt item: #1719 of 3327 id: hedera-hedera-hashgraph-launches-hedera-consensus-service-making-it-possible-to-add-decentralized-trust-to-any-application author: hedera title: hedera-hedera-hashgraph-launches-hedera-consensus-service-making-it-possible-to-add-decentralized-trust-to-any-application date: None words: 1722 flesch: 54 summary: Dallas, TX — February 13, 2020 — Hedera Hashgraph, an enterprise-grade public distributed ledger, today announced that the Hedera Consensus Service (HCS) is open to developers on the Hedera mainnet. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: applications; consensus; hashgraph; hcs; hedera; network; service cache: hedera-hedera-hashgraph-launches-hedera-consensus-service-making-it-possible-to-add-decentralized-trust-to-any-application.html plain text: hedera-hedera-hashgraph-launches-hedera-consensus-service-making-it-possible-to-add-decentralized-trust-to-any-application.txt item: #1720 of 3327 id: hedera-hedera-hashgraph-named-a-cool-vendor-in-the-may-2020-gartner-cool-vendors-in-blockchain-technology-report author: hedera title: hedera-hedera-hashgraph-named-a-cool-vendor-in-the-may-2020-gartner-cool-vendors-in-blockchain-technology-report date: None words: 1255 flesch: 52 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: applications; ecosystem; gartner; hashgraph; hedera; network cache: hedera-hedera-hashgraph-named-a-cool-vendor-in-the-may-2020-gartner-cool-vendors-in-blockchain-technology-report.html plain text: hedera-hedera-hashgraph-named-a-cool-vendor-in-the-may-2020-gartner-cool-vendors-in-blockchain-technology-report.txt item: #1721 of 3327 id: hedera-hedera-hashgraph-public-mainnet-open-access-planned-for-september-16th-2019 author: hedera title: hedera-hedera-hashgraph-public-mainnet-open-access-planned-for-september-16th-2019 date: None words: 1460 flesch: 56 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: ecosystem; hashgraph; hbar; hedera; network; nodes; public cache: hedera-hedera-hashgraph-public-mainnet-open-access-planned-for-september-16th-2019.html plain text: hedera-hedera-hashgraph-public-mainnet-open-access-planned-for-september-16th-2019.txt item: #1722 of 3327 id: hedera-hedera-hashgraph-to-leverage-armanino-trustexplorer-in-new-strategic-partnership author: hedera title: hedera-hedera-hashgraph-to-leverage-armanino-trustexplorer-in-new-strategic-partnership date: None words: 1335 flesch: 47 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Trusted Node service increases trust and accessibility for Hedera ecosystem participants and their financial auditors Dallas, TX — February 5, 2020 — Hedera Hashgraph, the enterprise-grade, public distributed ledger platform, has announced a strategic partnership with Armanino LLP, one of the 25 largest accounting and business consulting firms in the U.S. keywords: armanino; data; ecosystem; hashgraph; hbar; hedera; network cache: hedera-hedera-hashgraph-to-leverage-armanino-trustexplorer-in-new-strategic-partnership.html plain text: hedera-hedera-hashgraph-to-leverage-armanino-trustexplorer-in-new-strategic-partnership.txt item: #1723 of 3327 id: hedera-hedera-hashgraph-transaction-and-query-processing-model author: hedera title: hedera-hedera-hashgraph-transaction-and-query-processing-model date: None words: 2213 flesch: 56 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: client; hedera; network; node; query; state; transaction cache: hedera-hedera-hashgraph-transaction-and-query-processing-model.html plain text: hedera-hedera-hashgraph-transaction-and-query-processing-model.txt item: #1724 of 3327 id: hedera-hedera-hashgraphs-hbar-coin-added-to-atomic-wallet author: hedera title: hedera-hedera-hashgraphs-hbar-coin-added-to-atomic-wallet date: None words: 1198 flesch: 54 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: atomic; ecosystem; hbar; hedera; network; wallet cache: hedera-hedera-hashgraphs-hbar-coin-added-to-atomic-wallet.html plain text: hedera-hedera-hashgraphs-hbar-coin-added-to-atomic-wallet.txt item: #1725 of 3327 id: hedera-hedera-named-to-constellation-shortlist-for-blockchain-services author: hedera title: hedera-hedera-named-to-constellation-shortlist-for-blockchain-services date: None words: 1134 flesch: 50 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: constellation; ecosystem; hbar; hedera; network; services cache: hedera-hedera-named-to-constellation-shortlist-for-blockchain-services.html plain text: hedera-hedera-named-to-constellation-shortlist-for-blockchain-services.txt item: #1726 of 3327 id: hedera-hedera-named-to-constellation-shortlisttm-for-blockchain-technology-services author: hedera title: hedera-hedera-named-to-constellation-shortlisttm-for-blockchain-technology-services date: None words: 1292 flesch: 49 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: blockchain; constellation; ecosystem; hashgraph; hedera; network; public cache: hedera-hedera-named-to-constellation-shortlisttm-for-blockchain-technology-services.html plain text: hedera-hedera-named-to-constellation-shortlisttm-for-blockchain-technology-services.txt item: #1727 of 3327 id: hedera-hedera-nft-metadata-hip412 author: hedera title: hedera-hedera-nft-metadata-hip412 date: None words: 2307 flesch: 56 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: hedera; image; json; metadata; nft; schema; token; type cache: hedera-hedera-nft-metadata-hip412.html plain text: hedera-hedera-nft-metadata-hip412.txt item: #1728 of 3327 id: hedera-hedera-nft-sdk author: hedera title: hedera-hedera-nft-sdk date: None words: 2372 flesch: 63 summary: The project aims to evolve the Hedera NFT SDK based on community feedback to make it an excellent tool for NFT creators on the Hedera network. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: hedera; key; metadata; nft; risk; score; sdk; token cache: hedera-hedera-nft-sdk.html plain text: hedera-hedera-nft-sdk.txt item: #1729 of 3327 id: hedera-hedera-processes-thousands-of-tps-see-how-that-number-is-calculated author: hedera title: hedera-hedera-processes-thousands-of-tps-see-how-that-number-is-calculated date: None words: 1556 flesch: 56 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: blocks; duration; hedera; python; tps; transactions cache: hedera-hedera-processes-thousands-of-tps-see-how-that-number-is-calculated.html plain text: hedera-hedera-processes-thousands-of-tps-see-how-that-number-is-calculated.txt item: #1730 of 3327 id: hedera-hedera-release-cycle-overview author: hedera title: hedera-hedera-release-cycle-overview date: None words: 2644 flesch: 57 summary: This means that, in the future, it’s possible to see Hiero features that are never enabled on Hedera mainnet. Together, these network environments and components enable a phased rollout of new Hedera features. keywords: consensus; hedera; hiero; mainnet; network; node; previewnet; release; testnet cache: hedera-hedera-release-cycle-overview.html plain text: hedera-hedera-release-cycle-overview.txt item: #1731 of 3327 id: hedera-hedera-smart-contract-service-security-model-update author: hedera title: hedera-hedera-smart-contract-service-security-model-update date: None words: 2769 flesch: 42 summary: Hedera Consensus Nodes must strike a delicate balance between Hedera security and EVM security models. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: admin; contract; hedera; key; requirements; signature; smart cache: hedera-hedera-smart-contract-service-security-model-update.html plain text: hedera-hedera-smart-contract-service-security-model-update.txt item: #1732 of 3327 id: hedera-hedera-technical-insights-a-hybrid-dlt-architecture-for-gaming author: hedera title: hedera-hedera-technical-insights-a-hybrid-dlt-architecture-for-gaming date: None words: 2737 flesch: 66 summary: However, game players must trust that the centralized platform will not act inappropriately, such as influence game play, censor certain players, or steal in-game assets. If a given DLT supports a maximum throughput of T tps, then if there are n players, each submitting t game transactions (e.g. a chess move, or a character movement) every second to the ledger, then clearly T ≥ n * t, or game play won’t be possible. keywords: alice; game; hedera; latency; ledger; network; play; time cache: hedera-hedera-technical-insights-a-hybrid-dlt-architecture-for-gaming.html plain text: hedera-hedera-technical-insights-a-hybrid-dlt-architecture-for-gaming.txt item: #1733 of 3327 id: hedera-hedera-technical-insights-hedera-consensus-service-scaling author: hedera title: hedera-hedera-technical-insights-hedera-consensus-service-scaling date: None words: 2449 flesch: 62 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Hedera network places messages in order within the StockApp topic 4. keywords: hedera; network; nodes; order; state; stockapp; transactions cache: hedera-hedera-technical-insights-hedera-consensus-service-scaling.html plain text: hedera-hedera-technical-insights-hedera-consensus-service-scaling.txt item: #1734 of 3327 id: hedera-hedera-technical-insights-latency-on-hedera author: hedera title: hedera-hedera-technical-insights-latency-on-hedera date: None words: 1942 flesch: 64 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: consensus; event; hedera; node; timestamp; transaction cache: hedera-hedera-technical-insights-latency-on-hedera.html plain text: hedera-hedera-technical-insights-latency-on-hedera.txt item: #1735 of 3327 id: hedera-hedera-to-host-five-days-of-events-at-davos-2023-with-politico-will-i-am-starling-labs-ibm-and-more author: hedera title: hedera-hedera-to-host-five-days-of-events-at-davos-2023-with-politico-will-i-am-starling-labs-ibm-and-more date: None words: 2015 flesch: 53 summary: Hedera Haus — Hedera’s unique exhibition space at the heart of the action — will set up shop at Promenade 71, Davos Platz to host drinks receptions, insightful panel discussions, keynotes, and afterparties with critical players from the worlds of DLT and enterprise technology. Hedera Haus is a carbon neutral venue, with Hedera having purchased carbon offsets through DOVU on Hedera to cover flights, electricity, recyclable materials and buildout, shipping, and food & beverage at the event. keywords: council; davos; ecosystem; events; founder; future; haus; hedera; network cache: hedera-hedera-to-host-five-days-of-events-at-davos-2023-with-politico-will-i-am-starling-labs-ibm-and-more.html plain text: hedera-hedera-to-host-five-days-of-events-at-davos-2023-with-politico-will-i-am-starling-labs-ibm-and-more.txt item: #1736 of 3327 id: hedera-hedera-token-service-hts-live-on-mainnet-with-over-60-initial-ecosystem-partners author: hedera title: hedera-hedera-token-service-hts-live-on-mainnet-with-over-60-initial-ecosystem-partners date: None words: 1799 flesch: 45 summary: The initial ecosystem for Hedera Token Service comprises over 60 partners across the categories of token issuers, wallet and custody providers, exchanges, network explorers, standards boards and systems integrators, security auditors, and more. https://hedera.com/blog/new-hedera-token-service-offers-native-token-issuance-and-configurability-without-smart-contracts Hedera Token Service differentiation, fee schedule, and 2021 roadmap Hedera gathered product feedback from Hedera Council members, application developers, ecosystem partners, standards boards, and more during its conception of the Hedera Token Service. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: developer; ecosystem; hedera; hts; network; service; token cache: hedera-hedera-token-service-hts-live-on-mainnet-with-over-60-initial-ecosystem-partners.html plain text: hedera-hedera-token-service-hts-live-on-mainnet-with-over-60-initial-ecosystem-partners.txt item: #1737 of 3327 id: hedera-hedera-token-service-nft-token-keys-edge-cases author: hedera title: hedera-hedera-token-service-nft-token-keys-edge-cases date: None words: 2679 flesch: 63 summary: What's New Partners Papers Careers Media Blog Technical Press Podcast Community Events Meetups Store Brand Navigation QUICKSTART Hedera Token Service: NFT Token Keys Edge Cases technical Feb 07, 2023 by Michiel Mulders Developer Relations This technical blog post tries to answer all your questions about token keys, how to use them, and their edge cases. This means you can set token keys for both fungible and non-fungible tokens. keywords: account; admin; hedera; key; keys; nft; token cache: hedera-hedera-token-service-nft-token-keys-edge-cases.html plain text: hedera-hedera-token-service-nft-token-keys-edge-cases.txt item: #1738 of 3327 id: hedera-hedera-wallet-snap-goes-live-connecting-the-hedera-network-with-metamasks-30-million-monthly-active-users author: hedera title: hedera-hedera-wallet-snap-goes-live-connecting-the-hedera-network-with-metamasks-30-million-monthly-active-users date: None words: 1439 flesch: 51 summary: Hedera Wallet Snap goes live, connecting the Hedera network… | Hedera Hedera Network Services Token Service Mint and configure tokens and accounts. What's New Partners Papers Careers Media Blog Technical Press Podcast Community Events Meetups Store Brand Navigation QUICKSTART Hedera Wallet Snap goes live, connecting the Hedera network with MetaMask’s 30 million monthly active users news Jan 16, 2024 by Hedera Team Hedera is the most used, sustainable, enterprise-grade public network for the decentralized economy. keywords: ecosystem; hbar; hedera; metamask; network; technologies cache: hedera-hedera-wallet-snap-goes-live-connecting-the-hedera-network-with-metamasks-30-million-monthly-active-users.html plain text: hedera-hedera-wallet-snap-goes-live-connecting-the-hedera-network-with-metamasks-30-million-monthly-active-users.txt item: #1739 of 3327 id: hedera-hethers-js-being-deprecated-in-favor-of-evm-tooling author: hedera title: hedera-hethers-js-being-deprecated-in-favor-of-evm-tooling date: None words: 945 flesch: 55 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: developer; ecosystem; hedera; hethers.js; network cache: hedera-hethers-js-being-deprecated-in-favor-of-evm-tooling.html plain text: hedera-hethers-js-being-deprecated-in-favor-of-evm-tooling.txt item: #1740 of 3327 id: hedera-hex-trust-asias-leading-digital-asset-custodian-announces-partnership-with-hedera-the-most-used-enterprise-grade-public-ledger author: hedera title: hedera-hex-trust-asias-leading-digital-asset-custodian-announces-partnership-with-hedera-the-most-used-enterprise-grade-public-ledger date: None words: 1809 flesch: 49 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: asset; ecosystem; grade; hedera; hex; network; toko; trust cache: hedera-hex-trust-asias-leading-digital-asset-custodian-announces-partnership-with-hedera-the-most-used-enterprise-grade-public-ledger.html plain text: hedera-hex-trust-asias-leading-digital-asset-custodian-announces-partnership-with-hedera-the-most-used-enterprise-grade-public-ledger.txt item: #1741 of 3327 id: hedera-hierarchical-multi-signature-support-in-hedera author: hedera title: hedera-hierarchical-multi-signature-support-in-hedera date: None words: 2445 flesch: 62 summary: What's New Partners Papers Careers Media Blog Technical Press Podcast Community Events Meetups Store Brand Navigation QUICKSTART Hedera Technical Insights: Hierarchical Multi-Signature support in Hedera technical Jan 11, 2020 by Paul Madsen Head of Identity, The HBAR Foundation Every entity (for instance, an account, a file, a smart contract) maintained in Hedera state has an associated set of public keys - it will be the corresponding private keys that must sign any transaction attempting to change that entity. Permissions can be defined that ensure that control of entities in Hedera state can both reflect the complexity of real-world business relationships, as well as protect users from the challenges of private key protection and management. keywords: account; carol; hedera; key; keys; public; transaction cache: hedera-hierarchical-multi-signature-support-in-hedera.html plain text: hedera-hierarchical-multi-signature-support-in-hedera.txt item: #1742 of 3327 id: hedera-how-can-we-model-a-building-in-web3 author: hedera title: hedera-how-can-we-model-a-building-in-web3 date: None words: 2595 flesch: 59 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Deploys building contract + mints tokenId=1 for that property Copy 2. keywords: building; chain; contract; hedera; ipfs; memory; metadata; nft; world cache: hedera-how-can-we-model-a-building-in-web3.html plain text: hedera-how-can-we-model-a-building-in-web3.txt item: #1743 of 3327 id: hedera-how-hedera-calculates-the-hbar-usd-exchange-rate-for-sdks-and-applications author: hedera title: hedera-how-hedera-calculates-the-hbar-usd-exchange-rate-for-sdks-and-applications date: None words: 1413 flesch: 59 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: ert; exchange; hbar; hedera; network; rate cache: hedera-how-hedera-calculates-the-hbar-usd-exchange-rate-for-sdks-and-applications.html plain text: hedera-how-hedera-calculates-the-hbar-usd-exchange-rate-for-sdks-and-applications.txt item: #1744 of 3327 id: hedera-how-is-tokenization-changing-the-way-we-invest author: hedera title: hedera-how-is-tokenization-changing-the-way-we-invest date: None words: 2436 flesch: 57 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: apartment; estate; hedera; nft; ownership; property; tokenization; tokens cache: hedera-how-is-tokenization-changing-the-way-we-invest.html plain text: hedera-how-is-tokenization-changing-the-way-we-invest.txt item: #1745 of 3327 id: hedera-how-to-approve-fungible-token-and-nft-allowances-on-hedera-part-1-using-the-sdk author: hedera title: hedera-how-to-approve-fungible-token-and-nft-allowances-on-hedera-part-1-using-the-sdk date: None words: 3492 flesch: 32 summary: ===================================\n`); console.log(`- Creating Hedera accounts...\n`); const initBalance = new Hbar(10); const treasuryKey = PrivateKey.generateECDSA(); const [treasurySt, treasuryId] = await accountCreateFcn(treasuryKey, initBalance, client); console.log(`- For creation of the FT, the inputs are the token name (HBAR ROCKS), token symbol (HROCK), the initial supply (100), the treasury account for the token (treasuryId), the treasury key for transaction authorization (treasuryKey), and the client object For the NFT creation, the inputs are the token name (HBAR ROCKS), token symbol (HROCK), the initial supply (0), the maximum token supply (1000), the treasury account for the token (treasuryId), the treasury key for transaction authorization (treasuryKey), and the client object Output to the console tokenId and the token supply Fungible Token (FT) Fungible Token (FT) Non-Fungible Token (NFT) const [tokenId, tokenInfo] = await htsTokens.createFtFcn(HBAR ROCKS, HROCK, 100, treasuryId, treasuryKey, client); console.log(`\n- Token ID: ${tokenId}`); console.log(`- keywords: = await; client; const; function; fungible; hedera; nft; token cache: hedera-how-to-approve-fungible-token-and-nft-allowances-on-hedera-part-1-using-the-sdk.html plain text: hedera-how-to-approve-fungible-token-and-nft-allowances-on-hedera-part-1-using-the-sdk.txt item: #1746 of 3327 id: hedera-how-to-approve-hbar-allowances-on-hedera-using-the-sdk author: hedera title: hedera-how-to-approve-hbar-allowances-on-hedera-using-the-sdk date: None words: 2548 flesch: 45 summary: ===================================\n`); console.log(`- Creating Hedera accounts...\n`); const initBalance = new Hbar(10); const treasuryKey = PrivateKey.generateECDSA(); const [treasurySt, treasuryId] = await accountCreateFcn(treasuryKey, initBalance, client); console.log(`- =================================== - Creating Hedera accounts... - Treasury's account: https://hashscan.io/#/testnet/account/0.0.48520992 - Alice's account: https://hashscan.io/#/testnet/account/0.0.48520993 - Bob's account: https://hashscan.io/#/testnet/account/0.0.48520995 2. keywords: = await; account; allowance; client; const; hbar; hedera cache: hedera-how-to-approve-hbar-allowances-on-hedera-using-the-sdk.html plain text: hedera-how-to-approve-hbar-allowances-on-hedera-using-the-sdk.txt item: #1747 of 3327 id: hedera-how-to-auto-create-hedera-accounts-with-hbar-and-token-transfers author: hedera title: hedera-how-to-auto-create-hedera-accounts-with-hbar-and-token-transfers date: None words: 2495 flesch: 42 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: account; await; const; create; hedera; nft; tokenid cache: hedera-how-to-auto-create-hedera-accounts-with-hbar-and-token-transfers.html plain text: hedera-how-to-auto-create-hedera-accounts-with-hbar-and-token-transfers.txt item: #1748 of 3327 id: hedera-how-to-create-a-smart-contract-app-on-hedera-using-solidity-react-js-metamask-and-ethers-js-a-simple-counter author: hedera title: hedera-how-to-create-a-smart-contract-app-on-hedera-using-solidity-react-js-metamask-and-ethers-js-a-simple-counter date: None words: 4136 flesch: 51 summary: Switch to Hedera Testnet: It determines the chainId based on the chosen Hedera network (testnet, previewnet, or mainnet) and sends a wallet_addEthereumChain request to MetaMask to add the corresponding Hedera network. Hedera Network (Consensus and Mirror Nodes): The Hedera network consists of consensus nodes that process and process transactions, and mirror nodes that store transaction data. keywords: account; button; contract; dapp; ethers; function; hedera; metamask; network cache: hedera-how-to-create-a-smart-contract-app-on-hedera-using-solidity-react-js-metamask-and-ethers-js-a-simple-counter.html plain text: hedera-how-to-create-a-smart-contract-app-on-hedera-using-solidity-react-js-metamask-and-ethers-js-a-simple-counter.txt item: #1749 of 3327 id: hedera-how-to-create-an-hbar-token-faucet-for-metamask author: hedera title: hedera-how-to-create-an-hbar-token-faucet-for-metamask date: None words: 2932 flesch: 55 summary: What we will do: Create a Hedera react-app Utilizing TypeScript and Material UI Install MetaMask Chrome Extension Add Hedera Testnet Network to MetaMask Connect Our dApp to MetaMask and Retrieve Wallet Address Install Hedera Hashgraph JS SDK and Create Your Client Send HBAR to MetaMask Wallet The complete TypeScript project can be found on GitHub here. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: const; hbar; hedera; metamask; network; ─ ─; ├ ─ cache: hedera-how-to-create-an-hbar-token-faucet-for-metamask.html plain text: hedera-how-to-create-an-hbar-token-faucet-for-metamask.txt item: #1750 of 3327 id: hedera-how-to-create-chatgpt-plugins-unlock-ai-and-blockchain author: hedera title: hedera-how-to-create-chatgpt-plugins-unlock-ai-and-blockchain date: None words: 3372 flesch: 54 summary: Chatting with ChatGPT: Using Your Plugin Now that your plugin is installed and enabled, you can use it by simply asking ChatGPT questions about the HBAR and/or token balances of Hedera accounts. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: account; api; balance; chatgpt; hedera; network; plugin; token cache: hedera-how-to-create-chatgpt-plugins-unlock-ai-and-blockchain.html plain text: hedera-how-to-create-chatgpt-plugins-unlock-ai-and-blockchain.txt item: #1751 of 3327 id: hedera-how-to-deploy-smart-contracts-on-hedera-part-1-a-simple-getter-and-setter-contract author: hedera title: hedera-how-to-deploy-smart-contracts-on-hedera-part-1-a-simple-getter-and-setter-contract date: None words: 2198 flesch: 51 summary: Node.js Packages (install with a package manager like npm or yarn) npm install @hashgraph/sdk npm install dotenv npm install -g solc Documentation and examples Nice-to-Have Knowledge A bit of Solidity (Documentation) Some of the Hedera basics (How to Start Developing on Hedera: Back to the Basics) A few things about Hedera smart contracts (Core Concepts - Hedera Documentation) How to Deploy a Smart Contract You can deploy a smart contract on Hedera in four steps: Write the contract and compile to bytecode Add the bytecode file to the Hedera network Create the smart contract on Hedera Call the smart contract 1. How to Deploy Smart Contracts on Hedera – Part 1: A Simple… | Hedera Hedera Network Services Token Service Mint and configure tokens and accounts. keywords: bytecode; const; contract; file; hedera; query; variable cache: hedera-how-to-deploy-smart-contracts-on-hedera-part-1-a-simple-getter-and-setter-contract.html plain text: hedera-how-to-deploy-smart-contracts-on-hedera-part-1-a-simple-getter-and-setter-contract.txt item: #1752 of 3327 id: hedera-how-to-develop-on-hedera-back-to-the-basics author: hedera title: hedera-how-to-develop-on-hedera-back-to-the-basics date: None words: 1749 flesch: 57 summary: Python Key Concepts Accounts: The Central Starting Point Accounts are stored on the public ledger and hold HBAR which are used to pay for the transaction and query fees Hedera accounts can be created, updated, or deleted and are represented by an account ID To create an account, you need an existing account that can pay for the associated transaction fees for the new account and to optionally fund the new account with an initial balance Learn more about Hedera accounts here Keys and Signatures Each account has a public and private key pair The private key of the account is used to authorize and sign transactions for that account Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: account; developer; hbar; hedera; network; service; transaction cache: hedera-how-to-develop-on-hedera-back-to-the-basics.html plain text: hedera-how-to-develop-on-hedera-back-to-the-basics.txt item: #1753 of 3327 id: hedera-how-to-exempt-hedera-accounts-from-custom-token-fees author: hedera title: hedera-how-to-exempt-hedera-accounts-from-custom-token-fees date: None words: 1471 flesch: 37 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Share This Back to blog What is gRPC, gRPC-Web, and Proxies? Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: account; await; const; hedera; token cache: hedera-how-to-exempt-hedera-accounts-from-custom-token-fees.html plain text: hedera-how-to-exempt-hedera-accounts-from-custom-token-fees.txt item: #1754 of 3327 id: hedera-how-to-generate-a-random-number-on-hedera author: hedera title: hedera-how-to-generate-a-random-number-on-hedera date: None words: 3077 flesch: 43 summary: ==================================================== Summary Now you know how to generate a random number on Hedera using the JavaScript SDK and Solidity libraries. =================================== console.log(`\nSTEP 1 ===================================\n`); console.log(`- Generating random numbers with the SDK...\n`); const lo = 0; const hi = 50; let randomNum = []; for (var i = 0; i < 5; i++) { const randomNumTx = await new PrngTransaction().setRange(hi).execute(client); const randomNumRec keywords: = =; = await; const; contract; function; hedera; number; transaction cache: hedera-how-to-generate-a-random-number-on-hedera.html plain text: hedera-how-to-generate-a-random-number-on-hedera.txt item: #1755 of 3327 id: hedera-how-to-get-event-information-from-hedera-smart-contracts author: hedera title: hedera-how-to-get-event-information-from-hedera-smart-contracts date: None words: 2053 flesch: 44 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Share This Back to blog What is gRPC, gRPC-Web, and Proxies? Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: const; contract; event; function; hedera; message; mirror cache: hedera-how-to-get-event-information-from-hedera-smart-contracts.html plain text: hedera-how-to-get-event-information-from-hedera-smart-contracts.txt item: #1756 of 3327 id: hedera-how-to-inspect-smart-contract-transactions-on-hedera-using-mirror-nodes author: hedera title: hedera-how-to-inspect-smart-contract-transactions-on-hedera-using-mirror-nodes date: None words: 2465 flesch: 45 summary: index.js index.js Counter.sol CallCounter.sol console.clear(); import { Client, AccountId, PrivateKey, Hbar, ContractFunctionParameters } from @hashgraph/sdk; import * as queries from ./utils/queries.js; import * as contracts from ./utils/contractOperations.js; import counterContract from ./contracts/Counter.json assert { type: json }; import counterCallerContract from ./contracts/CounterCaller.json assert { type: json }; import dotenv from dotenv; dotenv.config(); const operatorId = AccountId.fromString(process.env.OPERATOR_ID); const operatorKey = PrivateKey.fromString(process.env.OPERATOR_PVKEY); const network = process.env.HEDERA_NETWORK; const client = Client.forNetwork(network).setOperator(operatorId, operatorKey); client.setDefaultMaxTransactionFee(new Hbar(1000)); client.setMaxQueryPayment(new Hbar(50)); async function main() { // STEP 1 =================================== console.log(`\nSTEP 1 ===================================\n`); console.log(`- keywords: = await; = console.log(`\nstep; const; contract; hedera; information; mirror; node cache: hedera-how-to-inspect-smart-contract-transactions-on-hedera-using-mirror-nodes.html plain text: hedera-how-to-inspect-smart-contract-transactions-on-hedera-using-mirror-nodes.txt item: #1757 of 3327 id: hedera-how-to-look-up-transaction-history-on-hedera-using-mirror-nodes-back-to-the-basics author: hedera title: hedera-how-to-look-up-transaction-history-on-hedera-using-mirror-nodes-back-to-the-basics date: None words: 1784 flesch: 56 summary: How to Look Up Transaction History on Hedera Using Mirror… | Hedera Hedera Network Services Token Service Mint and configure tokens and accounts. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: api; hedera; mirror; network; nodes; transaction; use cache: hedera-how-to-look-up-transaction-history-on-hedera-using-mirror-nodes-back-to-the-basics.html plain text: hedera-how-to-look-up-transaction-history-on-hedera-using-mirror-nodes-back-to-the-basics.txt item: #1758 of 3327 id: hedera-how-to-pass-zero-token-values-to-hedera-contracts author: hedera title: hedera-how-to-pass-zero-token-values-to-hedera-contracts date: None words: 3667 flesch: 45 summary: =================================== console.log(`\nSTEP 1 ===================================\n`); console.log(`- Creating Hedera accounts, contract, and HTS token...\n`); // Accounts const initBalance = new Hbar(10); const aliceKey = PrivateKey.generateECDSA(); const [aliceSt, aliceId] = await accountCreateFcn(aliceKey, initBalance, client); console.log(`- =================================== - Creating Hedera accounts, contract, and HTS token... - Alice's account: https://hashscan.io/#/testnet/account/0.0.48760462 - Contract ID: 0.0.48760464 - Contract ID in Solidity address format: 0000000000000000000000000000000002e80690 - Contract call for token creation: SUCCESS - Token ID: 0.0.48760465 - See details: https://hashscan.io/testnet/transaction/0.0.2520793-1666975193-540118792 2. keywords: = =; = await; = console.log(`\nstep; = owner; contract; contractexecutesubmit =; function; hedera; token cache: hedera-how-to-pass-zero-token-values-to-hedera-contracts.html plain text: hedera-how-to-pass-zero-token-values-to-hedera-contracts.txt item: #1759 of 3327 id: hedera-how-to-send-and-receive-hbar-using-smart-contracts-part-1-using-the-sdk author: hedera title: hedera-how-to-send-and-receive-hbar-using-smart-contracts-part-1-using-the-sdk date: None words: 1670 flesch: 48 summary: In this tutorial, you will learn how to send and receive HBAR to and from Hedera contracts. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: await; balance; const; contract; hbar; hedera cache: hedera-how-to-send-and-receive-hbar-using-smart-contracts-part-1-using-the-sdk.html plain text: hedera-how-to-send-and-receive-hbar-using-smart-contracts-part-1-using-the-sdk.txt item: #1760 of 3327 id: hedera-how-to-send-and-receive-hbar-using-smart-contracts-part-2-solidity author: hedera title: hedera-how-to-send-and-receive-hbar-using-smart-contracts-part-2-solidity date: None words: 3410 flesch: 43 summary: ==================================================== Summary If you run the entire example successfully, your console should look something like: Now you know how to send HBAR to and from a contract on Hedera using both the SDK and Solidity! console.log(` ==================================================== GETTING HBAR TO THE CONTRACT ====================================================`); // Transfer HBAR to the contract using .setPayableAmount WITHOUT specifying a function (fallback/receive triggered) let payableAmt = 10; console.log(`- Caller (Operator) PAYS ${payableAmt} ℏ to contract (fallback/receive)...`); const toContractRx = await contractExecuteNoFcn(contractId, gasLimit, payableAmt); // Get contract HBAR balance by calling the getBalance function in the contract AND/OR using ContractInfoQuery in the SDK await contractCallQueryFcn(contractId, gasLimit, getBalance); // Outputs the contract balance in the console Copy Helper Functions: contractExecuteNoFcn contractExecuteNoFcn contractCallQueryFcn async function contractExecuteNoFcn(cId, gasLim, amountHbar) { const contractExecuteTx = new ContractExecuteTransaction() .setContractId(cId) .setGas(gasLim) .setPayableAmount(amountHbar); const contractExecuteSubmit = await contractExecuteTx.execute(client); const contractExecuteRx = await contractExecuteSubmit.getReceipt(client); return contractExecuteRx; } async function contractCallQueryFcn(cId, gasLim, fcnName) { const contractQueryTx = new ContractCallQuery() .setContractId(cId) .setGas(gasLim) .setFunction(fcnName); const contractQuerySubmit = await contractQueryTx.execute(client); const contractQueryResult = contractQuerySubmit.getUint256(0); console.log(`- keywords: = =; = await; const; contract =; function; hbar; hedera; section = cache: hedera-how-to-send-and-receive-hbar-using-smart-contracts-part-2-solidity.html plain text: hedera-how-to-send-and-receive-hbar-using-smart-contracts-part-2-solidity.txt item: #1761 of 3327 id: hedera-how-to-set-up-foundry-to-test-smart-contracts-on-hedera author: hedera title: hedera-how-to-set-up-foundry-to-test-smart-contracts-on-hedera date: None words: 2159 flesch: 54 summary: => { const contractCreateFlowTxn = new ContractCreateFlow() .setBytecode(bytecode) .setGas(gasLimit); console.log(`- Deploying smart contract to Hedera network`) const txnResponse = await contractCreateFlowTxn.execute(client); const txnReceipt = await txnResponse.getReceipt(client); const contractId = txnReceipt.contractId; if (contractId === null ) { throw new Error(Somehow contractId is null. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: copy; forge; foundry; hedera; project; test; ─ ─; ├ ─ cache: hedera-how-to-set-up-foundry-to-test-smart-contracts-on-hedera.html plain text: hedera-how-to-set-up-foundry-to-test-smart-contracts-on-hedera.txt item: #1762 of 3327 id: hedera-how-to-set-up-your-own-hedera-local-network-using-docker author: hedera title: hedera-how-to-set-up-your-own-hedera-local-network-using-docker date: None words: 2099 flesch: 49 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: 0.0s; cloud; hedera; network; node; storage cache: hedera-how-to-set-up-your-own-hedera-local-network-using-docker.html plain text: hedera-how-to-set-up-your-own-hedera-local-network-using-docker.txt item: #1763 of 3327 id: hedera-how-would-we-build-a-reit-today-using-web3-technologies author: hedera title: hedera-how-would-we-build-a-reit-today-using-web3-technologies date: None words: 2006 flesch: 52 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. High capital requirements, long transaction cycles, and a general lack of liquidity have always kept real estate investments out of reach for many. keywords: assets; estate; hedera; market; tokenization; web3; world cache: hedera-how-would-we-build-a-reit-today-using-web3-technologies.html plain text: hedera-how-would-we-build-a-reit-today-using-web3-technologies.txt item: #1764 of 3327 id: hedera-hyland-and-hedera-hashgraph-present-blockchain-proof-of-concept-for-records-verification-to-texas-secretary-of-state author: hedera title: hedera-hyland-and-hedera-hashgraph-present-blockchain-proof-of-concept-for-records-verification-to-texas-secretary-of-state date: None words: 1113 flesch: 53 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: blockchain; council; ecosystem; hedera; network; texas cache: hedera-hyland-and-hedera-hashgraph-present-blockchain-proof-of-concept-for-records-verification-to-texas-secretary-of-state.html plain text: hedera-hyland-and-hedera-hashgraph-present-blockchain-proof-of-concept-for-records-verification-to-texas-secretary-of-state.txt item: #1765 of 3327 id: hedera-ibm-and-tata-communications-join-hedera-governing-council author: hedera title: hedera-ibm-and-tata-communications-join-hedera-governing-council date: None words: 1321 flesch: 50 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Leading enterprises become members of Hedera Governing Council to guide growth of the Hashgraph distributed ledger platform Dallas, TX – August 12, 2019 – Hedera Hashgraph, an enterprise-ready distributed ledger platform, has announced that IBM and Tata Communications have joined the Hedera Governing Council. keywords: council; governance; governing; hashgraph; hedera; network cache: hedera-ibm-and-tata-communications-join-hedera-governing-council.html plain text: hedera-ibm-and-tata-communications-join-hedera-governing-council.txt item: #1766 of 3327 id: hedera-iit-madras-joins-hedera-governing-council-to-drive-r-d-in-new-blockchain-use-cases author: hedera title: hedera-iit-madras-joins-hedera-governing-council-to-drive-r-d-in-new-blockchain-use-cases date: None words: 1751 flesch: 48 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. IIT Madras Joins Hedera Governing Council to Drive R&D in… | Hedera Hedera Network Services Token Service Mint and configure tokens and accounts. keywords: council; email; hedera; iit; institute; madras; network; use cache: hedera-iit-madras-joins-hedera-governing-council-to-drive-r-d-in-new-blockchain-use-cases.html plain text: hedera-iit-madras-joins-hedera-governing-council-to-drive-r-d-in-new-blockchain-use-cases.txt item: #1767 of 3327 id: hedera-introducing-a-new-testnet-faucet-and-hedera-portal-changes author: hedera title: hedera-introducing-a-new-testnet-faucet-and-hedera-portal-changes date: None words: 1463 flesch: 55 summary: Changes to Hedera Portal Accounts The refill process for Hedera Testnet accounts created through the Hedera Portal is also changing. The goal is to continuously improve the development experience on Hedera, ensuring that Hedera Testnet resources are distributed efficiently and fairly, minimizing potential disruptions and maximizing utility for all users. keywords: developer; ecosystem; hbar; hedera; network; testnet cache: hedera-introducing-a-new-testnet-faucet-and-hedera-portal-changes.html plain text: hedera-introducing-a-new-testnet-faucet-and-hedera-portal-changes.txt item: #1768 of 3327 id: hedera-introducing-block-streams-a-unified-data-stream-capturing-the-comprehensive-history-of-the-hedera-network author: hedera title: hedera-introducing-block-streams-a-unified-data-stream-capturing-the-comprehensive-history-of-the-hedera-network date: None words: 1910 flesch: 52 summary: Simplified Consumption Block Streams are encoded using Protobuf, enabling them to be easily consumable by any programming language with minimal complexity or dependencies, which increases accessibility for developers to work with Hedera data. Some examples include: Applications and off-chain services can cache and process Hedera state locally, reducing latency and dependency on external data retrieval. Applications and off-chain services can monitor and maintain contract state locally, enabling seamless interaction with Hedera-based smart contracts. keywords: block; data; hedera; network; nodes; record; streams cache: hedera-introducing-block-streams-a-unified-data-stream-capturing-the-comprehensive-history-of-the-hedera-network.html plain text: hedera-introducing-block-streams-a-unified-data-stream-capturing-the-comprehensive-history-of-the-hedera-network.txt item: #1769 of 3327 id: hedera-introducing-hiero-the-foundation-of-the-future author: hedera title: hedera-introducing-hiero-the-foundation-of-the-future date: None words: 1224 flesch: 50 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: decentralized; ecosystem; future; hedera; network; trust cache: hedera-introducing-hiero-the-foundation-of-the-future.html plain text: hedera-introducing-hiero-the-foundation-of-the-future.txt item: #1770 of 3327 id: hedera-introducing-hip-850-enhancing-supply-key-functionality-for-nft-updates-in-treasury-account author: hedera title: hedera-introducing-hip-850-enhancing-supply-key-functionality-for-nft-updates-in-treasury-account date: None words: 1779 flesch: 48 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: const; hedera; key; metadata; nft; supply; treasury cache: hedera-introducing-hip-850-enhancing-supply-key-functionality-for-nft-updates-in-treasury-account.html plain text: hedera-introducing-hip-850-enhancing-supply-key-functionality-for-nft-updates-in-treasury-account.txt item: #1771 of 3327 id: hedera-introducing-native-staking-phase-1-on-the-hedera-network author: hedera title: hedera-introducing-native-staking-phase-1-on-the-hedera-network date: None words: 2433 flesch: 62 summary: Currently, Hedera network nodes are operated by members of the Hedera Governing Council, and each node has an equal stake. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: consensus; hedera; network; node; rewards; stake; staking cache: hedera-introducing-native-staking-phase-1-on-the-hedera-network.html plain text: hedera-introducing-native-staking-phase-1-on-the-hedera-network.txt item: #1772 of 3327 id: hedera-introducing-the-hedera-treasury-management-report author: hedera title: hedera-introducing-the-hedera-treasury-management-report date: None words: 1217 flesch: 51 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: hbars; hedera; network; report; supply; treasury cache: hedera-introducing-the-hedera-treasury-management-report.html plain text: hedera-introducing-the-hedera-treasury-management-report.txt item: #1773 of 3327 id: hedera-introduction-solidity-smart-contracts author: hedera title: hedera-introduction-solidity-smart-contracts date: None words: 1749 flesch: 62 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: contract; ecosystem; function; hedera; network; public; solidity cache: hedera-introduction-solidity-smart-contracts.html plain text: hedera-introduction-solidity-smart-contracts.txt item: #1774 of 3327 id: hedera-json-rpc-providers-now-on-hedera-accelerating-developer-adoption-with-evm-tooling-and-wallets author: hedera title: hedera-json-rpc-providers-now-on-hedera-accelerating-developer-adoption-with-evm-tooling-and-wallets date: None words: 1459 flesch: 50 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: ecosystem; hedera; json; network; rpc; source; web3 cache: hedera-json-rpc-providers-now-on-hedera-accelerating-developer-adoption-with-evm-tooling-and-wallets.html plain text: hedera-json-rpc-providers-now-on-hedera-accelerating-developer-adoption-with-evm-tooling-and-wallets.txt item: #1775 of 3327 id: hedera-kingdom-trust-now-offers-custody-for-hedera-hashgraph author: hedera title: hedera-kingdom-trust-now-offers-custody-for-hedera-hashgraph date: None words: 1040 flesch: 54 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: ecosystem; hbar; hedera; kingdom; network; trust cache: hedera-kingdom-trust-now-offers-custody-for-hedera-hashgraph.html plain text: hedera-kingdom-trust-now-offers-custody-for-hedera-hashgraph.txt item: #1776 of 3327 id: hedera-leading-research-institution-university-college-london-joins-hedera-governing-council-as-first-higher-education-member author: hedera title: hedera-leading-research-institution-university-college-london-joins-hedera-governing-council-as-first-higher-education-member date: None words: 1567 flesch: 49 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: blockchain; council; hedera; london; ucl; university; world cache: hedera-leading-research-institution-university-college-london-joins-hedera-governing-council-as-first-higher-education-member.html plain text: hedera-leading-research-institution-university-college-london-joins-hedera-governing-council-as-first-higher-education-member.txt item: #1777 of 3327 id: hedera-leading-supply-chain-company-avc-global-selects-hedera-hashgraph-as-dlt-platform author: hedera title: hedera-leading-supply-chain-company-avc-global-selects-hedera-hashgraph-as-dlt-platform date: None words: 1701 flesch: 52 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: avc; chain; global; hedera; mvc; network; platform; supply cache: hedera-leading-supply-chain-company-avc-global-selects-hedera-hashgraph-as-dlt-platform.html plain text: hedera-leading-supply-chain-company-avc-global-selects-hedera-hashgraph-as-dlt-platform.txt item: #1778 of 3327 id: hedera-less-known-hedera-features author: hedera title: hedera-less-known-hedera-features date: None words: 1842 flesch: 55 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Less Known Hedera Features | Hedera Hedera Network Services Token Service Mint and configure tokens and accounts. keywords: account; consensus; example; hedera; key; network; use cache: hedera-less-known-hedera-features.html plain text: hedera-less-known-hedera-features.txt item: #1779 of 3327 id: hedera-leveraging-ethereum-developer-tools-on-hedera author: hedera title: hedera-leveraging-ethereum-developer-tools-on-hedera date: None words: 1448 flesch: 55 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: account; const; developer; hedera; network cache: hedera-leveraging-ethereum-developer-tools-on-hedera.html plain text: hedera-leveraging-ethereum-developer-tools-on-hedera.txt item: #1780 of 3327 id: hedera-leveraging-hederas-architecture-sirios-oracle-free-price-feed-approach author: hedera title: hedera-leveraging-hederas-architecture-sirios-oracle-free-price-feed-approach date: None words: 2156 flesch: 56 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: data; hbar; hedera; network; oracles; price; sirio; token cache: hedera-leveraging-hederas-architecture-sirios-oracle-free-price-feed-approach.html plain text: hedera-leveraging-hederas-architecture-sirios-oracle-free-price-feed-approach.txt item: #1781 of 3327 id: hedera-lg-art-labs-latest-enhancements-leverage-unique-features-of-the-hedera-network-to-benefit-nft-artists-and-art-lovers author: hedera title: hedera-lg-art-labs-latest-enhancements-leverage-unique-features-of-the-hedera-network-to-benefit-nft-artists-and-art-lovers date: None words: 1414 flesch: 53 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: art; blade; ecosystem; hedera; lab; network cache: hedera-lg-art-labs-latest-enhancements-leverage-unique-features-of-the-hedera-network-to-benefit-nft-artists-and-art-lovers.html plain text: hedera-lg-art-labs-latest-enhancements-leverage-unique-features-of-the-hedera-network-to-benefit-nft-artists-and-art-lovers.txt item: #1782 of 3327 id: hedera-lg-joins-hedera-governing-council-to-accelerate-innovation-and-adoption-of-public-dlt-globally author: hedera title: hedera-lg-joins-hedera-governing-council-to-accelerate-innovation-and-adoption-of-public-dlt-globally date: None words: 1310 flesch: 52 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. About Hedera Hedera Hashgraph is a public distributed ledger for building decentralized applications. keywords: council; ecosystem; hashgraph; hedera; network; technology cache: hedera-lg-joins-hedera-governing-council-to-accelerate-innovation-and-adoption-of-public-dlt-globally.html plain text: hedera-lg-joins-hedera-governing-council-to-accelerate-innovation-and-adoption-of-public-dlt-globally.txt item: #1783 of 3327 id: hedera-limechain-demonstrates-new-synchronization-of-microsoft-dynamics-and-google-sheets-on-hedera-hashgraph author: hedera title: hedera-limechain-demonstrates-new-synchronization-of-microsoft-dynamics-and-google-sheets-on-hedera-hashgraph date: None words: 1289 flesch: 52 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: blockchain; developer; ecosystem; hedera; limechain; network; use cache: hedera-limechain-demonstrates-new-synchronization-of-microsoft-dynamics-and-google-sheets-on-hedera-hashgraph.html plain text: hedera-limechain-demonstrates-new-synchronization-of-microsoft-dynamics-and-google-sheets-on-hedera-hashgraph.txt item: #1784 of 3327 id: hedera-lse-joins-hedera-governing-council-to-advance-blockchain-research-for-social-good author: hedera title: hedera-lse-joins-hedera-governing-council-to-advance-blockchain-research-for-social-good date: None words: 1554 flesch: 47 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: blockchain; council; hedera; lse; network; research; team cache: hedera-lse-joins-hedera-governing-council-to-advance-blockchain-research-for-social-good.html plain text: hedera-lse-joins-hedera-governing-council-to-advance-blockchain-research-for-social-good.txt item: #1785 of 3327 id: hedera-mance-harmon-dr-leemon-baird-and-hedera-development-and-management-teams-transition-to-swirlds-labs author: hedera title: hedera-mance-harmon-dr-leemon-baird-and-hedera-development-and-management-teams-transition-to-swirlds-labs date: None words: 1040 flesch: 54 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. For more information about these organizational changes and the Council’s decision to further decentralization of the Hedera hashgraph network, please view Hedera’s FAQs and past Hedera Governing Council meeting minutes. keywords: council; ecosystem; hedera; network; swirlds cache: hedera-mance-harmon-dr-leemon-baird-and-hedera-development-and-management-teams-transition-to-swirlds-labs.html plain text: hedera-mance-harmon-dr-leemon-baird-and-hedera-development-and-management-teams-transition-to-swirlds-labs.txt item: #1786 of 3327 id: hedera-mapping-hedera-token-service-standards-to-erc20-erc721-erc1155 author: hedera title: hedera-mapping-hedera-token-service-standards-to-erc20-erc721-erc1155 date: None words: 3883 flesch: 48 summary: At Hedera, we’re often asked how Hedera Token Service (HTS) tokens map to the most ubiquitous fungible and non-fungible token models: ERC20, ERC721 and ERC1155. Token Identification using Hedera Token Service Tokens on Hedera are identified by a Token Id, made of three numerals separated by a dot; for example, 0.0.123344. keywords: account; contract; equivalent; hedera; keys; method; service; token; transaction cache: hedera-mapping-hedera-token-service-standards-to-erc20-erc721-erc1155.html plain text: hedera-mapping-hedera-token-service-standards-to-erc20-erc721-erc1155.txt item: #1787 of 3327 id: hedera-matchmaker-matchmaker author: hedera title: hedera-matchmaker-matchmaker date: None words: 1311 flesch: 61 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: ecosystem; hbar; hedera; network; token; uber cache: hedera-matchmaker-matchmaker.html plain text: hedera-matchmaker-matchmaker.txt item: #1788 of 3327 id: hedera-meet-venin-a-concise-yet-powerful-sdk-alternative-for-js-devs author: hedera title: hedera-meet-venin-a-concise-yet-powerful-sdk-alternative-for-js-devs date: None words: 3351 flesch: 48 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. HBAR The Hedera network's native cryptocurrency. keywords: @dev; address; const; contract; function; hedera; network; nfts; token; venin cache: hedera-meet-venin-a-concise-yet-powerful-sdk-alternative-for-js-devs.html plain text: hedera-meet-venin-a-concise-yet-powerful-sdk-alternative-for-js-devs.txt item: #1789 of 3327 id: hedera-mirror-node-ecosystem-update author: hedera title: hedera-mirror-node-ecosystem-update date: None words: 1180 flesch: 58 summary: Each of the options above provide either API or UI access to Hedera transactions. Here’s a snapshot of the Hedera mirror nodes and services currently available: DragonGlass - Built and operated by OpenCrowd, a leading IT and software consultancy, DragonGlass is a cloud-based service that provides access to search and historical data across a variety of distributed ledgers, beginning with Hedera Hashgraph. keywords: developer; ecosystem; hbar; hedera; network; node cache: hedera-mirror-node-ecosystem-update.html plain text: hedera-mirror-node-ecosystem-update.txt item: #1790 of 3327 id: hedera-mirror-node-software-beta-and-tools-now-available-including-one-click-deploy-in-google-cloud-platform-marketplace author: hedera title: hedera-mirror-node-software-beta-and-tools-now-available-including-one-click-deploy-in-google-cloud-platform-marketplace date: None words: 1626 flesch: 55 summary: Analyzing Hedera network data with the Hedera-ETL tool The Hedera team has partnered with the blockchain ETL project to create Hedera-ETL. The ETL works like this: Extract: Stream of transactions (and records) are ingested from a GCP PubSub topic Transform: Filters for important fields, formats data types, etc Load: Streaming insert into BigQuery dataset Like any typical batch processing system, Hedera-ETL is most suitable for applications that want to run big, scalable queries and analysis on Hedera network data. keywords: buckets; data; gcp; hedera; mirror; network; node cache: hedera-mirror-node-software-beta-and-tools-now-available-including-one-click-deploy-in-google-cloud-platform-marketplace.html plain text: hedera-mirror-node-software-beta-and-tools-now-available-including-one-click-deploy-in-google-cloud-platform-marketplace.txt item: #1791 of 3327 id: hedera-mondelez-international-joins-hedera-council-to-accelerate-dlt-adoption-digital-transformation-and-improved-business-efficiencies author: hedera title: hedera-mondelez-international-joins-hedera-council-to-accelerate-dlt-adoption-digital-transformation-and-improved-business-efficiencies date: None words: 1329 flesch: 49 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: council; ecosystem; hedera; international; mondelēz; network; open cache: hedera-mondelez-international-joins-hedera-council-to-accelerate-dlt-adoption-digital-transformation-and-improved-business-efficiencies.html plain text: hedera-mondelez-international-joins-hedera-council-to-accelerate-dlt-adoption-digital-transformation-and-improved-business-efficiencies.txt item: #1792 of 3327 id: hedera-multi-game-economies author: hedera title: hedera-multi-game-economies date: None words: 3572 flesch: 66 summary: I wouldn't recommend implementing multi-game p2e tokens. Multi-game economies will rely on these decentralized player histories. keywords: developers; f2p; game; hedera; nfts; p2e; play; sharks; tokens; whales cache: hedera-multi-game-economies.html plain text: hedera-multi-game-economies.txt item: #1793 of 3327 id: hedera-network-upgrade-communications-a-new-previewnet-ip-proxies-and-tls-support author: hedera title: hedera-network-upgrade-communications-a-new-previewnet-ip-proxies-and-tls-support date: None words: 1894 flesch: 55 summary: Hedera mainnet nodes and decentralization update Hedera's mission is to become the most decentralized and utilized public network at scale in the market. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: council; developer; hedera; mainnet; network; proxies; testnet cache: hedera-network-upgrade-communications-a-new-previewnet-ip-proxies-and-tls-support.html plain text: hedera-network-upgrade-communications-a-new-previewnet-ip-proxies-and-tls-support.txt item: #1794 of 3327 id: hedera-neuron-leverages-the-hedera-network-for-drone-radar-system-in-uk-government-sponsored-trial author: hedera title: hedera-neuron-leverages-the-hedera-network-for-drone-radar-system-in-uk-government-sponsored-trial date: None words: 1588 flesch: 53 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: consensus; data; drone; ecosystem; hedera; network; neuron; service cache: hedera-neuron-leverages-the-hedera-network-for-drone-radar-system-in-uk-government-sponsored-trial.html plain text: hedera-neuron-leverages-the-hedera-network-for-drone-radar-system-in-uk-government-sponsored-trial.txt item: #1795 of 3327 id: hedera-new-hedera-token-service-features-nfts-metadata-and-custom-fees author: hedera title: hedera-new-hedera-token-service-features-nfts-metadata-and-custom-fees date: None words: 2005 flesch: 63 summary: SDK Support for Custom Fees The following SDK versions support custom Hedera Token Service fees: Java: 2.0.9/1.5.1 JavaScript: 2.0.26/1.4.11 Go: 2.1.11 .NET Reminder: SDK v1 support will be deprecated in October 2021. If you're a developer and looking to get started using these features, check out the quick-start guides created by Hedera Developer Evangelist Waylon Jepsen (@0xjepsen): • Developer Quick-Start: NFTs and Metadata • Developer Quick-Start: Custom Token Fees HIP-18: Custom Fees on Hedera Token Service HIP-18: Custom Fees was submitted by Cooper Kunz and Jason Fabritz of the Hedera-powered creator economy application Calaxy and Rahul Kothari, a researcher at bluesky and Engineering Intern at the Ethereum Foundation. keywords: custom; developer; fee; fees; hedera; nfts; service; token cache: hedera-new-hedera-token-service-features-nfts-metadata-and-custom-fees.html plain text: hedera-new-hedera-token-service-features-nfts-metadata-and-custom-fees.txt item: #1796 of 3327 id: hedera-new-hedera-token-service-offers-native-token-issuance-and-configurability-without-smart-contracts author: hedera title: hedera-new-hedera-token-service-offers-native-token-issuance-and-configurability-without-smart-contracts date: None words: 4718 flesch: 45 summary: — Dr. Nikolaos Siafakas, Founder at Hash-Hash.info Kabuto has integrated Hedera Token Service into its explorer and mirror node API for the Hedera community to take advantage of — we're excited to watch and support the flourishing token ecosystem on Hedera Hashgraph. Hedera Token Service launches with fully supportive ecosystem of over 60 initial partners including leading exchanges, custody and wallet providers, members of the Hedera Governing Council, and applications that will issue tokens using HTS “Today, digital tokens are being designed for all kinds of economic activities,” said Mance Harmon, co-founder and CEO of Hedera. keywords: assets; ceo; digital; ecosystem; founder; hedera; hedera token; hts; network; new; service; support; token; token service; tokenization cache: hedera-new-hedera-token-service-offers-native-token-issuance-and-configurability-without-smart-contracts.html plain text: hedera-new-hedera-token-service-offers-native-token-issuance-and-configurability-without-smart-contracts.txt item: #1797 of 3327 id: hedera-news author: hedera title: hedera-news date: None words: 7429 flesch: 34 summary: Read article Hedera Hashgraph Announces Ledger Nano S and Nano X Wallet Implementations Feb 26, 2020Hedera Team Dallas, TX — February 26, 2020 — Hedera Hashgraph, the enterprise-grade distributed public ledger, has announced an integration with the Nano S and Nano X wallets from Ledger, a highly secure, trusted, and widely available hardware wallet developer on the market. Read article Hedera Hashgraph Launches Hedera Consensus Service, making it possible to add decentralized trust to any application Feb 13, 2020Hedera Team Dallas, TX — February 13, 2020 — Hedera Hashgraph, an enterprise-grade public distributed ledger, today announced that the Hedera Consensus Service (HCS) is open to developers on the Hedera mainnet. keywords: 2020hedera; 2020hedera team; article hedera; council; enterprise; governing; grade; hedera; hedera council; hedera hashgraph; hedera network; ledger; network; new; open; platform; public; read article; team; team dallas; technology; today cache: hedera-news.html plain text: hedera-news.txt item: #1798 of 3327 id: hedera-nft-royalty-fees-hedera-hashgraph author: hedera title: hedera-nft-royalty-fees-hedera-hashgraph date: None words: 2346 flesch: 58 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: balance; fee; hedera; id:0.0.48289984; nfts; treasury cache: hedera-nft-royalty-fees-hedera-hashgraph.html plain text: hedera-nft-royalty-fees-hedera-hashgraph.txt item: #1799 of 3327 id: hedera-now-available-hedera-javascript-did-sdk author: hedera title: hedera-now-available-hedera-javascript-did-sdk date: None words: 2640 flesch: 45 summary: What's New Partners Papers Careers Media Blog Technical Press Podcast Community Events Meetups Store Brand Navigation QUICKSTART ­­Now Available: Hedera JavaScript DID SDK technical Aug 02, 2021 by Daniel Norkin Co-Founder & CEO at Envision Blockchain Solutions The Hedera Hashgraph ecosystem has been extremely busy regarding the decentralized development of Hedera’s developer tools/services. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: blockchain; dids; hedera; javascript; return; sdk; static; string; vcs cache: hedera-now-available-hedera-javascript-did-sdk.html plain text: hedera-now-available-hedera-javascript-did-sdk.txt item: #1800 of 3327 id: hedera-one-billion-mainnet-transactions author: hedera title: hedera-one-billion-mainnet-transactions date: None words: 1705 flesch: 58 summary: With a majority of Hedera transactions using hbars or the Hedera Consensus Service, the associated cost and energy consumption of a billion transactions is a fraction of what it would be on alternative networks. Fast forward to today, and Hedera Consensus Service transactions make up the bulk of what's happening on the Hedera mainnet. keywords: consensus; hashgraph; hedera; mainnet; network; service; transactions cache: hedera-one-billion-mainnet-transactions.html plain text: hedera-one-billion-mainnet-transactions.txt item: #1801 of 3327 id: hedera-one-year-after-open-access-hedera-now-processes-1-5-million-transactions-per-day-surpassing-ethereum author: hedera title: hedera-one-year-after-open-access-hedera-now-processes-1-5-million-transactions-per-day-surpassing-ethereum date: None words: 1545 flesch: 51 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: applications; ecosystem; hashgraph; hbar; hedera; network; year cache: hedera-one-year-after-open-access-hedera-now-processes-1-5-million-transactions-per-day-surpassing-ethereum.html plain text: hedera-one-year-after-open-access-hedera-now-processes-1-5-million-transactions-per-day-surpassing-ethereum.txt item: #1802 of 3327 id: hedera-p2 author: hedera title: hedera-p2 date: None words: 7429 flesch: 34 summary: Read article Hedera Hashgraph Announces Ledger Nano S and Nano X Wallet Implementations Feb 26, 2020Hedera Team Dallas, TX — February 26, 2020 — Hedera Hashgraph, the enterprise-grade distributed public ledger, has announced an integration with the Nano S and Nano X wallets from Ledger, a highly secure, trusted, and widely available hardware wallet developer on the market. Read article Hedera Hashgraph Launches Hedera Consensus Service, making it possible to add decentralized trust to any application Feb 13, 2020Hedera Team Dallas, TX — February 13, 2020 — Hedera Hashgraph, an enterprise-grade public distributed ledger, today announced that the Hedera Consensus Service (HCS) is open to developers on the Hedera mainnet. keywords: 2020hedera; 2020hedera team; article hedera; council; enterprise; governing; grade; hedera; hedera council; hedera hashgraph; hedera network; ledger; network; new; open; platform; public; read article; team; team dallas; technology; today cache: hedera-p2.html plain text: hedera-p2.txt item: #1803 of 3327 id: hedera-partners-in-digital-health-introduces-academic-publishing-industrys-first-article-proof-of-origin-capability-built-on-the-hedera-network author: hedera title: hedera-partners-in-digital-health-introduces-academic-publishing-industrys-first-article-proof-of-origin-capability-built-on-the-hedera-network date: None words: 1294 flesch: 48 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: ecosystem; hbar; health; hedera; network; partners; proof cache: hedera-partners-in-digital-health-introduces-academic-publishing-industrys-first-article-proof-of-origin-capability-built-on-the-hedera-network.html plain text: hedera-partners-in-digital-health-introduces-academic-publishing-industrys-first-article-proof-of-origin-capability-built-on-the-hedera-network.txt item: #1804 of 3327 id: hedera-power-transition-blockchain-sustainability-hedera-hashgraph author: hedera title: hedera-power-transition-blockchain-sustainability-hedera-hashgraph date: None words: 950 flesch: 57 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: blockchain; ecosystem; hedera; network; report cache: hedera-power-transition-blockchain-sustainability-hedera-hashgraph.html plain text: hedera-power-transition-blockchain-sustainability-hedera-hashgraph.txt item: #1805 of 3327 id: hedera-pragmatic-blockchain-design-patterns-integrating-blockchain-into-business-processes author: hedera title: hedera-pragmatic-blockchain-design-patterns-integrating-blockchain-into-business-processes date: None words: 4000 flesch: 56 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. From an architecture standpoint, securing the keys that sign blockchain transactions is crucial. keywords: asset; blockchain; contracts; data; hash; hedera; network; pattern; service; systems; token cache: hedera-pragmatic-blockchain-design-patterns-integrating-blockchain-into-business-processes.html plain text: hedera-pragmatic-blockchain-design-patterns-integrating-blockchain-into-business-processes.txt item: #1806 of 3327 id: hedera-pricing-smart-contracts author: hedera title: hedera-pricing-smart-contracts date: None words: 2264 flesch: 61 summary: Hedera System Contract Gas: Hedera system contract gas fees are calculated by first converting the transaction cost in USD into gas using a specific conversion rate. As the above formula indicates, Hedera gas is just one of a number of resources – the relative scarcity and usage of each that, in the aggregate, determine the total fee for a transaction or query. keywords: contract; fee; gas; hedera; network; nodes; transaction cache: hedera-pricing-smart-contracts.html plain text: hedera-pricing-smart-contracts.txt item: #1807 of 3327 id: hedera-proxy-staking-on-hedera author: hedera title: hedera-proxy-staking-on-hedera date: None words: 1738 flesch: 62 summary: The votes of Hedera nodes in the virtual voting algorithm are weighted by the stake of that node, that is, the amount of tokens in the accounts that the nodes have designated as staked. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: account; consensus; hedera; node; proxy; stake cache: hedera-proxy-staking-on-hedera.html plain text: hedera-proxy-staking-on-hedera.txt item: #1808 of 3327 id: hedera-rent-on-hedera author: hedera title: hedera-rent-on-hedera date: None words: 2592 flesch: 60 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. The default policy for changes on blockchains has been: Accounts can be created Account state can change, if the transaction is signed by the appropriate parties Smart contracts can be created, but not subsequently modified or deleted Smart contract state can change, if the transaction is signed by the appropriate parties The possibility of deletion, should an object’s rent run out, extends the above list to include: Accounts and smart contracts can be deleted, if their rent runs out Note: some proposals for rent do not require an automatic deletion mechanism. keywords: contract; hedera; network; nodes; rent; state; storage cache: hedera-rent-on-hedera.html plain text: hedera-rent-on-hedera.txt item: #1809 of 3327 id: hedera-rolling-smart-contract-hedera-api-fees-into-gas-fees author: hedera title: hedera-rolling-smart-contract-hedera-api-fees-into-gas-fees date: None words: 1013 flesch: 58 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: contract; fees; gas; hedera; network cache: hedera-rolling-smart-contract-hedera-api-fees-into-gas-fees.html plain text: hedera-rolling-smart-contract-hedera-api-fees-into-gas-fees.txt item: #1810 of 3327 id: hedera-safe-health-systems-builds-digital-health-id-system-on-hedera-hashgraph-to-enable-home-covid-19-testing-on-your-mobile-phone author: hedera title: hedera-safe-health-systems-builds-digital-health-id-system-on-hedera-hashgraph-to-enable-home-covid-19-testing-on-your-mobile-phone date: None words: 1362 flesch: 55 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: covid-19; ecosystem; health; healthcheck; hedera; network; testing cache: hedera-safe-health-systems-builds-digital-health-id-system-on-hedera-hashgraph-to-enable-home-covid-19-testing-on-your-mobile-phone.html plain text: hedera-safe-health-systems-builds-digital-health-id-system-on-hedera-hashgraph-to-enable-home-covid-19-testing-on-your-mobile-phone.txt item: #1811 of 3327 id: hedera-safe-health-systems-launches-healthcheck-platform-assisting-arizona-state-university-in-fight-against-spread-of-covid-19 author: hedera title: hedera-safe-health-systems-launches-healthcheck-platform-assisting-arizona-state-university-in-fight-against-spread-of-covid-19 date: None words: 1437 flesch: 54 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: covid-19; ecosystem; health; healthcheck; hedera; network; platform cache: hedera-safe-health-systems-launches-healthcheck-platform-assisting-arizona-state-university-in-fight-against-spread-of-covid-19.html plain text: hedera-safe-health-systems-launches-healthcheck-platform-assisting-arizona-state-university-in-fight-against-spread-of-covid-19.txt item: #1812 of 3327 id: hedera-servicenow-and-hedera-enable-cross-organizational-digital-workflows author: hedera title: hedera-servicenow-and-hedera-enable-cross-organizational-digital-workflows date: None words: 1329 flesch: 45 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: applications; dlt; ecosystem; hedera; network; platform; servicenow cache: hedera-servicenow-and-hedera-enable-cross-organizational-digital-workflows.html plain text: hedera-servicenow-and-hedera-enable-cross-organizational-digital-workflows.txt item: #1813 of 3327 id: hedera-seva-love-a-transformational-platform-for-good-is-powering-nfts-and-the-metaverse-on-the-hedera-network author: hedera title: hedera-seva-love-a-transformational-platform-for-good-is-powering-nfts-and-the-metaverse-on-the-hedera-network date: None words: 1957 flesch: 53 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: community; ecosystem; hedera; network; nft; platform; seva.love; world cache: hedera-seva-love-a-transformational-platform-for-good-is-powering-nfts-and-the-metaverse-on-the-hedera-network.html plain text: hedera-seva-love-a-transformational-platform-for-good-is-powering-nfts-and-the-metaverse-on-the-hedera-network.txt item: #1814 of 3327 id: hedera-shinhan-bank-furthers-digital-transformation-plans-joins-hedera-governing-council author: hedera title: hedera-shinhan-bank-furthers-digital-transformation-plans-joins-hedera-governing-council date: None words: 1367 flesch: 50 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: bank; council; digital; ecosystem; hedera; network; shinhan cache: hedera-shinhan-bank-furthers-digital-transformation-plans-joins-hedera-governing-council.html plain text: hedera-shinhan-bank-furthers-digital-transformation-plans-joins-hedera-governing-council.txt item: #1815 of 3327 id: hedera-shinhan-bank-scb-techx-successfully-pilot-stablecoin-remittances-on-the-hedera-network author: hedera title: hedera-shinhan-bank-scb-techx-successfully-pilot-stablecoin-remittances-on-the-hedera-network date: None words: 1402 flesch: 51 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: bank; ecosystem; hedera; network; scb; shinhan; techx cache: hedera-shinhan-bank-scb-techx-successfully-pilot-stablecoin-remittances-on-the-hedera-network.html plain text: hedera-shinhan-bank-scb-techx-successfully-pilot-stablecoin-remittances-on-the-hedera-network.txt item: #1816 of 3327 id: hedera-shinhan-bank-to-conduct-stablecoin-international-remittance-poc-on-hedera-network-in-partnership-with-major-multinational-bank author: hedera title: hedera-shinhan-bank-to-conduct-stablecoin-international-remittance-poc-on-hedera-network-in-partnership-with-major-multinational-bank date: None words: 1475 flesch: 53 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: bank; company; ecosystem; hedera; network; shinhan; stablecoin cache: hedera-shinhan-bank-to-conduct-stablecoin-international-remittance-poc-on-hedera-network-in-partnership-with-major-multinational-bank.html plain text: hedera-shinhan-bank-to-conduct-stablecoin-international-remittance-poc-on-hedera-network-in-partnership-with-major-multinational-bank.txt item: #1817 of 3327 id: hedera-smart-contract-oracles-on-the-hedera-platform author: hedera title: hedera-smart-contract-oracles-on-the-hedera-platform date: None words: 1796 flesch: 58 summary: Additionally, the expected consensus latency for Hedera transactions is seconds and not minutes or hours. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: contract; data; hedera; network; oracle; transaction cache: hedera-smart-contract-oracles-on-the-hedera-platform.html plain text: hedera-smart-contract-oracles-on-the-hedera-platform.txt item: #1818 of 3327 id: hedera-smart-contract-rent-is-coming-to-hedera author: hedera title: hedera-smart-contract-rent-is-coming-to-hedera date: None words: 1935 flesch: 63 summary: // Dynamically calculate the contract hbar fee function mint() public payable { mintCount = mintCount + 1; mintCost = mintCount * 100000000; require(msg.value >= mintCost, “fee too low”); // pay the contract payMe(msg.value); } Copy Further explorations There is a lot to unpack when it comes to smart contracts renewal fees or rent. Smart contracts will not be charged auto renewal fees or expire. keywords: contract; fees; hbar; hedera; network; renewal; rent cache: hedera-smart-contract-rent-is-coming-to-hedera.html plain text: hedera-smart-contract-rent-is-coming-to-hedera.txt item: #1819 of 3327 id: hedera-smart-contract-rent-on-hedera-is-coming-what-you-need-to-know author: hedera title: hedera-smart-contract-rent-on-hedera-is-coming-what-you-need-to-know date: None words: 1743 flesch: 61 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: contract; hedera; network; payments; rent; storage cache: hedera-smart-contract-rent-on-hedera-is-coming-what-you-need-to-know.html plain text: hedera-smart-contract-rent-on-hedera-is-coming-what-you-need-to-know.txt item: #1820 of 3327 id: hedera-smart-contract-rent-on-hedera-part-2-how-to-pay author: hedera title: hedera-smart-contract-rent-on-hedera-part-2-how-to-pay date: None words: 1903 flesch: 56 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: 7776000sec =; = 90days; = await; contract; hedera; rent cache: hedera-smart-contract-rent-on-hedera-part-2-how-to-pay.html plain text: hedera-smart-contract-rent-on-hedera-part-2-how-to-pay.txt item: #1821 of 3327 id: hedera-smart-contract-verification-on-hedera author: hedera title: hedera-smart-contract-verification-on-hedera date: None words: 1918 flesch: 55 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: code; contract; hedera; match; network; source; verification cache: hedera-smart-contract-verification-on-hedera.html plain text: hedera-smart-contract-verification-on-hedera.txt item: #1822 of 3327 id: hedera-smart-contracts-2-0-now-on-the-hedera-testnet author: hedera title: hedera-smart-contracts-2-0-now-on-the-hedera-testnet date: None words: 1428 flesch: 57 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: contract; developer; ecosystem; hedera; network; use cache: hedera-smart-contracts-2-0-now-on-the-hedera-testnet.html plain text: hedera-smart-contracts-2-0-now-on-the-hedera-testnet.txt item: #1823 of 3327 id: hedera-sparkle-leverages-hedera-hashgraph-to-launch-digital-ereceipt-and-universal-digital-coupon-apps author: hedera title: hedera-sparkle-leverages-hedera-hashgraph-to-launch-digital-ereceipt-and-universal-digital-coupon-apps date: None words: 2047 flesch: 53 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Sparkle to use the Hedera Consensus Service to store and verify data from its newly launched digital eReceipt and Universal Digital Coupon apps Harrow, UK, and Dallas, TX — September 17, 2021 — Sparkle has teamed up with Retail Data Systems (RDS) and Hedera Hashgraph to launch digital eReceipts and Universal Digital Coupons apps. keywords: coupon; data; digital; hedera; network; rds; retailers; sparkle cache: hedera-sparkle-leverages-hedera-hashgraph-to-launch-digital-ereceipt-and-universal-digital-coupon-apps.html plain text: hedera-sparkle-leverages-hedera-hashgraph-to-launch-digital-ereceipt-and-universal-digital-coupon-apps.txt item: #1824 of 3327 id: hedera-stablecoin-studio-an-open-source-sdk-now-available-on-the-hedera-network-enabling-any-organization-to-easily-build-stablecoin-applications author: hedera title: hedera-stablecoin-studio-an-open-source-sdk-now-available-on-the-hedera-network-enabling-any-organization-to-easily-build-stablecoin-applications date: None words: 2883 flesch: 44 summary: Web3 stablecoin platforms, institutional issuers, enterprises, and payment providers can build stablecoin applications using Hedera network services without specialized blockchain expertise September 13, 2023 - Singapore | Token 2049 - Stablecoin Studio, an open-source stablecoin issuance and management toolkit that makes it easy for Web3 stablecoin platforms, institutional issuers, enterprises, and payment providers to build stablecoin applications using Hedera network services, is now available on the public Hedera network. What's New Partners Papers Careers Media Blog Technical Press Podcast Community Events Meetups Store Brand Navigation QUICKSTART Stablecoin Studio, an open source SDK, now available on the Hedera network, enabling any organization to easily build stablecoin applications news Sep 13, 2023 by Hedera Team Hedera is the most used, sustainable, enterprise-grade public network for the decentralized economy. keywords: bank; blockchain; ecosystem; hedera; network; security; source; stablecoin; studio; toolkit; web3 cache: hedera-stablecoin-studio-an-open-source-sdk-now-available-on-the-hedera-network-enabling-any-organization-to-easily-build-stablecoin-applications.html plain text: hedera-stablecoin-studio-an-open-source-sdk-now-available-on-the-hedera-network-enabling-any-organization-to-easily-build-stablecoin-applications.txt item: #1825 of 3327 id: hedera-stablecoins-and-other-tokens-demand-stable-fees author: hedera title: hedera-stablecoins-and-other-tokens-demand-stable-fees date: None words: 1924 flesch: 55 summary: As for other Hedera transaction types, clients sending transactions creating, managing, and transferring tokens will pay fees to reflect the burden that transaction places on the nodes of the Hedera mainnet. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: fee; fees; hbar; hedera; network; token; transaction cache: hedera-stablecoins-and-other-tokens-demand-stable-fees.html plain text: hedera-stablecoins-and-other-tokens-demand-stable-fees.txt item: #1826 of 3327 id: hedera-staking-on-hedera-for-developers-back-to-the-basics author: hedera title: hedera-staking-on-hedera-for-developers-back-to-the-basics date: None words: 2316 flesch: 42 summary: In this tutorial, you will learn how to configure staking options for Hedera accounts and contracts programmatically. Now you know how to stake HBAR balances for Hedera accounts and contracts upon creation and at any time by making updates to those entities. keywords: account; const; contract; function; hedera; staking cache: hedera-staking-on-hedera-for-developers-back-to-the-basics.html plain text: hedera-staking-on-hedera-for-developers-back-to-the-basics.txt item: #1827 of 3327 id: hedera-standard-bank-group-establishes-africas-first-hedera-network-node-to-enable-much-needed-digitisation-of-cross-border-trade-processes author: hedera title: hedera-standard-bank-group-establishes-africas-first-hedera-network-node-to-enable-much-needed-digitisation-of-cross-border-trade-processes date: None words: 1691 flesch: 51 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: assets; bank; ecosystem; group; hedera; network; standard cache: hedera-standard-bank-group-establishes-africas-first-hedera-network-node-to-enable-much-needed-digitisation-of-cross-border-trade-processes.html plain text: hedera-standard-bank-group-establishes-africas-first-hedera-network-node-to-enable-much-needed-digitisation-of-cross-border-trade-processes.txt item: #1828 of 3327 id: hedera-state-of-decentralization-survey-2021 author: hedera title: hedera-state-of-decentralization-survey-2021 date: None words: 891 flesch: 54 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: ecosystem; hbar; hedera; network; survey cache: hedera-state-of-decentralization-survey-2021.html plain text: hedera-state-of-decentralization-survey-2021.txt item: #1829 of 3327 id: hedera-state-proofs-on-hedera author: hedera title: hedera-state-proofs-on-hedera date: None words: 2969 flesch: 68 summary: State proofs will be a supported confirmation option on Hedera sometime following the mainnet’s Open Access event. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: alice; balance; hedera; merkle; node; proof; state cache: hedera-state-proofs-on-hedera.html plain text: hedera-state-proofs-on-hedera.txt item: #1830 of 3327 id: hedera-streamlining-consensus-throughput-and-lower-latency-with-about-half-the-events author: hedera title: hedera-streamlining-consensus-throughput-and-lower-latency-with-about-half-the-events date: None words: 1923 flesch: 57 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: consensus; event; hedera; network; node; parent; tipset cache: hedera-streamlining-consensus-throughput-and-lower-latency-with-about-half-the-events.html plain text: hedera-streamlining-consensus-throughput-and-lower-latency-with-about-half-the-events.txt item: #1831 of 3327 id: hedera-supras-dora-price-feeds-now-live-on-hedera author: hedera title: hedera-supras-dora-price-feeds-now-live-on-hedera date: None words: 1203 flesch: 51 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: dora; hedera; network; oracle; price; supra cache: hedera-supras-dora-price-feeds-now-live-on-hedera.html plain text: hedera-supras-dora-price-feeds-now-live-on-hedera.txt item: #1832 of 3327 id: hedera-swiss-hashgraph-association-launches-the-hashgraph-innovation-program-to-accelerate-adoption-of-the-hedera-network-worldwide author: hedera title: hedera-swiss-hashgraph-association-launches-the-hashgraph-innovation-program-to-accelerate-adoption-of-the-hedera-network-worldwide date: None words: 1904 flesch: 41 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Stefan Deiss, Co-Founder & Director of SDAI, said: “We are excited to bring Hedera Hashgraph to Switzerland and to contribute towards accelerating the broad adoption of the Hedera network, as one of the world’s leading and most energy-efficient DLT platforms. keywords: association; ecosystem; hashgraph; hbar; hedera; innovation; network; swiss cache: hedera-swiss-hashgraph-association-launches-the-hashgraph-innovation-program-to-accelerate-adoption-of-the-hedera-network-worldwide.html plain text: hedera-swiss-hashgraph-association-launches-the-hashgraph-innovation-program-to-accelerate-adoption-of-the-hedera-network-worldwide.txt item: #1833 of 3327 id: hedera-technical author: hedera title: hedera-technical date: None words: 8215 flesch: 56 summary: Read article How to Send and Receive HBAR Using Smart Contracts – Part 2: Using Solidity Aug 19, 2022Ed Marquez Learn how to send and receive HBAR to and from Hedera contracts. In this tutorial, you will learn how to send and receive HBAR to and from Hedera contracts. keywords: article; article hedera; consensus; contracts; developer; fees; hbar; hedera; insights; madsen; marquez; network; nft; nodes; read article; service; technical; token; transactions cache: hedera-technical.html plain text: hedera-technical.txt item: #1834 of 3327 id: hedera-the-break0uts-built-on-the-hedera-network-offers-nfts-for-the-art-of-culture-in-partnership-with-the-compound-and-forbes-the-culture author: hedera title: hedera-the-break0uts-built-on-the-hedera-network-offers-nfts-for-the-art-of-culture-in-partnership-with-the-compound-and-forbes-the-culture date: None words: 1268 flesch: 56 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: art; break0uts; culture; hedera; network; nfts cache: hedera-the-break0uts-built-on-the-hedera-network-offers-nfts-for-the-art-of-culture-in-partnership-with-the-compound-and-forbes-the-culture.html plain text: hedera-the-break0uts-built-on-the-hedera-network-offers-nfts-for-the-art-of-culture-in-partnership-with-the-compound-and-forbes-the-culture.txt item: #1835 of 3327 id: hedera-the-coupon-bureau-and-hedera-hashgraph-move-to-next-phase-in-delivering-universal-digital-coupons author: hedera title: hedera-the-coupon-bureau-and-hedera-hashgraph-move-to-next-phase-in-delivering-universal-digital-coupons date: None words: 1398 flesch: 52 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: bureau; coupon; ecosystem; hedera; industry; network; retailers cache: hedera-the-coupon-bureau-and-hedera-hashgraph-move-to-next-phase-in-delivering-universal-digital-coupons.html plain text: hedera-the-coupon-bureau-and-hedera-hashgraph-move-to-next-phase-in-delivering-universal-digital-coupons.txt item: #1836 of 3327 id: hedera-the-coupon-bureau-to-use-hedera-consensus-service-for-tamper-proof-log-for-top-consumer-brands-coupon-events author: hedera title: hedera-the-coupon-bureau-to-use-hedera-consensus-service-for-tamper-proof-log-for-top-consumer-brands-coupon-events date: None words: 1499 flesch: 54 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: bureau; coupon; ecosystem; hashgraph; hedera; network; time cache: hedera-the-coupon-bureau-to-use-hedera-consensus-service-for-tamper-proof-log-for-top-consumer-brands-coupon-events.html plain text: hedera-the-coupon-bureau-to-use-hedera-consensus-service-for-tamper-proof-log-for-top-consumer-brands-coupon-events.txt item: #1837 of 3327 id: hedera-the-create2-opcode-on-hedera-an-introduction author: hedera title: hedera-the-create2-opcode-on-hedera-an-introduction date: None words: 2311 flesch: 56 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: address; contract; create2; deployment; hedera; keccak256; use cache: hedera-the-create2-opcode-on-hedera-an-introduction.html plain text: hedera-the-create2-opcode-on-hedera-an-introduction.txt item: #1838 of 3327 id: hedera-the-evolution-of-hedera-services-modularization-in-v0-49 author: hedera title: hedera-the-evolution-of-hedera-services-modularization-in-v0-49 date: None words: 1268 flesch: 45 summary: What's New Partners Papers Careers Media Blog Technical Press Podcast Community Events Meetups Store Brand Navigation QUICKSTART The Evolution of Hedera Services: Modularization in v0.49 technical May 22, 2024 by Hedera Team Hedera is the most used, sustainable, enterprise-grade public network for the decentralized economy. by Ed Marquez Head of Developer Relations The release of services software version v0.49 in May 2024 introduces a significant engineering update to the core code run by Hedera consensus nodes. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: developer; ecosystem; hbar; hedera; network; services cache: hedera-the-evolution-of-hedera-services-modularization-in-v0-49.html plain text: hedera-the-evolution-of-hedera-services-modularization-in-v0-49.txt item: #1839 of 3327 id: hedera-the-hedera-previewnet-is-now-live author: hedera title: hedera-the-hedera-previewnet-is-now-live date: None words: 1353 flesch: 59 summary: Previewnet network status The source of truth for Hedera network, mirror node, and planned network upgrades for Hedera’s mainnet, testnet, and, now, previewnet, will always be available at https://status.hedera.com/. You can email subscribe, follow us on Twitter, or use the RSS feed link for live status updates. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: codebase; developer; hedera; network; previewnet; testnet cache: hedera-the-hedera-previewnet-is-now-live.html plain text: hedera-the-hedera-previewnet-is-now-live.txt item: #1840 of 3327 id: hedera-the-last-of-us-uncharted-and-days-gone-veterans-from-playstation-re-unite-to-form-aaa-gaming-and-entertainment-studio-liithos-announce-ashfall-for-pc-console-and-web-3 author: hedera title: hedera-the-last-of-us-uncharted-and-days-gone-veterans-from-playstation-re-unite-to-form-aaa-gaming-and-entertainment-studio-liithos-announce-ashfall-for-pc-console-and-web-3 date: None words: 1699 flesch: 53 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: aaa; ecosystem; gaming; hbar; hedera; liithos; network; world cache: hedera-the-last-of-us-uncharted-and-days-gone-veterans-from-playstation-re-unite-to-form-aaa-gaming-and-entertainment-studio-liithos-announce-ashfall-for-pc-console-and-web-3.html plain text: hedera-the-last-of-us-uncharted-and-days-gone-veterans-from-playstation-re-unite-to-form-aaa-gaming-and-entertainment-studio-liithos-announce-ashfall-for-pc-console-and-web-3.txt item: #1841 of 3327 id: hedera-the-nairobi-securities-exchange-nse-joins-the-hedera-council-to-expedite-tokenization-of-securities-in-kenyas-capital-markets author: hedera title: hedera-the-nairobi-securities-exchange-nse-joins-the-hedera-council-to-expedite-tokenization-of-securities-in-kenyas-capital-markets date: None words: 1370 flesch: 49 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: council; exchange; hedera; network; nse; securities cache: hedera-the-nairobi-securities-exchange-nse-joins-the-hedera-council-to-expedite-tokenization-of-securities-in-kenyas-capital-markets.html plain text: hedera-the-nairobi-securities-exchange-nse-joins-the-hedera-council-to-expedite-tokenization-of-securities-in-kenyas-capital-markets.txt item: #1842 of 3327 id: hedera-the-rise-of-the-identity-token author: hedera title: hedera-the-rise-of-the-identity-token date: None words: 4010 flesch: 57 summary: I would argue that there are a few reasons why neither kind of Identity Token described above realizes the Soulbound Token vision as it has been articulated: There is a limited number of ways available to strongly and immutably connect an NFT to a natural person. At the end of the day, just as desperate people sell their passports, we can acknowledge that without the correct controls and disincentives people could sell their KYC Tokens– and in the short term, there will remain far weaker consequences or countermeasures preventing it. keywords: account; alice; badge; chain; crypto; data; hedera; identity; kyc; token; user cache: hedera-the-rise-of-the-identity-token.html plain text: hedera-the-rise-of-the-identity-token.txt item: #1843 of 3327 id: hedera-the-worlds-best-pro-cycling-teams-ride-together-to-create-road-code-a-new-digital-fan-universe author: hedera title: hedera-the-worlds-best-pro-cycling-teams-ride-together-to-create-road-code-a-new-digital-fan-universe date: None words: 1662 flesch: 53 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: code; cycling; ecosystem; hbar; hedera; network; road; world cache: hedera-the-worlds-best-pro-cycling-teams-ride-together-to-create-road-code-a-new-digital-fan-universe.html plain text: hedera-the-worlds-best-pro-cycling-teams-ride-together-to-create-road-code-a-new-digital-fan-universe.txt item: #1844 of 3327 id: hedera-token-information-returned-by-getaccountinfo-and-getaccountbalance-to-be-deprecated author: hedera title: hedera-token-information-returned-by-getaccountinfo-and-getaccountbalance-to-be-deprecated date: None words: 922 flesch: 53 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: ecosystem; hedera; network; node; queries cache: hedera-token-information-returned-by-getaccountinfo-and-getaccountbalance-to-be-deprecated.html plain text: hedera-token-information-returned-by-getaccountinfo-and-getaccountbalance-to-be-deprecated.txt item: #1845 of 3327 id: hedera-token-workflows-for-customer-engagement-loyalty author: hedera title: hedera-token-workflows-for-customer-engagement-loyalty date: None words: 1951 flesch: 49 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Also, a party could play a role in the business process without owning a ServiceNow instance by directly calling into the ServiceNow Hedera Connector API. keywords: customer; ecosystem; hedera; loyalty; network; servicenow; tokens; wallets cache: hedera-token-workflows-for-customer-engagement-loyalty.html plain text: hedera-token-workflows-for-customer-engagement-loyalty.txt item: #1846 of 3327 id: hedera-top-5-global-utility-edf-joins-hedera-governing-council author: hedera title: hedera-top-5-global-utility-edf-joins-hedera-governing-council date: None words: 1408 flesch: 50 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Top 5 Global Utility EDF Joins Hedera Governing Council | Hedera Hedera Network Services Token Service Mint and configure tokens and accounts. keywords: blockchain; council; ecosystem; edf; hedera; network; use cache: hedera-top-5-global-utility-edf-joins-hedera-governing-council.html plain text: hedera-top-5-global-utility-edf-joins-hedera-governing-council.txt item: #1847 of 3327 id: hedera-transaction-confirmation-methods-in-hedera author: hedera title: hedera-transaction-confirmation-methods-in-hedera date: None words: 1966 flesch: 58 summary: Hedera clients can therefore choose a mechanism for which the costs are appropriate to the nature and sensitivity of the transactions they submit. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: client; confirmation; hedera; network; record; transaction cache: hedera-transaction-confirmation-methods-in-hedera.html plain text: hedera-transaction-confirmation-methods-in-hedera.txt item: #1848 of 3327 id: hedera-unblocking-and-unloading-the-speed-secrets-behind-hedera-smart-contracts-2-0 author: hedera title: hedera-unblocking-and-unloading-the-speed-secrets-behind-hedera-smart-contracts-2-0 date: None words: 1904 flesch: 57 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: code; consensus; contracts; ecosystem; hedera; network; time; transaction cache: hedera-unblocking-and-unloading-the-speed-secrets-behind-hedera-smart-contracts-2-0.html plain text: hedera-unblocking-and-unloading-the-speed-secrets-behind-hedera-smart-contracts-2-0.txt item: #1849 of 3327 id: hedera-unibright-integrates-hedera-token-service-to-scale-asset-tokenization author: hedera title: hedera-unibright-integrates-hedera-token-service-to-scale-asset-tokenization date: None words: 1364 flesch: 49 summary: Unibright Integrates Hedera Token Service to Scale Asset… | Hedera Hedera Network Services Token Service Mint and configure tokens and accounts. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: blockchain; hedera; network; service; token; tokenization; unibright cache: hedera-unibright-integrates-hedera-token-service-to-scale-asset-tokenization.html plain text: hedera-unibright-integrates-hedera-token-service-to-scale-asset-tokenization.txt item: #1850 of 3327 id: hedera-use-cases-for-hcs-based-records-in-play-to-earn-nft-gaming author: hedera title: hedera-use-cases-for-hcs-based-records-in-play-to-earn-nft-gaming date: None words: 3996 flesch: 63 summary: Either way, some entities must be responsible for validating game topics by running their histories through rigorous tests. Creating game topics and sending messages would still require a Hedera-based server operator with an $HBAR store, but these interactions do not lock developers into using the Hedera Token Service. keywords: developers; earn; events; game; hcs; hedera; nfts; play; records; rewards cache: hedera-use-cases-for-hcs-based-records-in-play-to-earn-nft-gaming.html plain text: hedera-use-cases-for-hcs-based-records-in-play-to-earn-nft-gaming.txt item: #1851 of 3327 id: hedera-using-distributed-ledgers-to-combat-deepfakes author: hedera title: hedera-using-distributed-ledgers-to-combat-deepfakes date: None words: 2809 flesch: 58 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: consensus; deepfakes; dlt; hedera; network; timestamp; transaction; video cache: hedera-using-distributed-ledgers-to-combat-deepfakes.html plain text: hedera-using-distributed-ledgers-to-combat-deepfakes.txt item: #1852 of 3327 id: hedera-wallets-on-hedera-collaborate-to-launch-walletconnect-integrations author: hedera title: hedera-wallets-on-hedera-collaborate-to-launch-walletconnect-integrations date: None words: 1768 flesch: 51 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: community; dapps; ecosystem; hedera; network; walletconnect; wallets cache: hedera-wallets-on-hedera-collaborate-to-launch-walletconnect-integrations.html plain text: hedera-wallets-on-hedera-collaborate-to-launch-walletconnect-integrations.txt item: #1853 of 3327 id: hedera-what-is-grpc-grpc-web-and-proxies author: hedera title: hedera-what-is-grpc-grpc-web-and-proxies date: None words: 1644 flesch: 49 summary: However, browsers restrict a direct connection to Hedera nodes for front-end web applications due to security sandbox rules. Hedera Council Over 30 highly diversified organizations govern Hedera. keywords: browser; grpc; hedera; network; proxies; proxy; web cache: hedera-what-is-grpc-grpc-web-and-proxies.html plain text: hedera-what-is-grpc-grpc-web-and-proxies.txt item: #1854 of 3327 id: hedera-why-is-there-no-slashing-in-hederas-proof-of-stake author: hedera title: hedera-why-is-there-no-slashing-in-hederas-proof-of-stake date: None words: 2478 flesch: 64 summary: For instance, if a consensus node signs an invalid transaction, the minimum amount slashed will be 1 ETH, but if other consensus nodes are simultaneously acting inappropriately then all the ETH could be lost. It is that discretion, inherent in blockchains, to follow the longest chain rule or not, which consensus nodes have, that argues for slashing – a consensus node can work on multiple forks and so must be discouraged from doing so via the risk of slashing. keywords: consensus; fee; hedera; network; node; slashing; stake cache: hedera-why-is-there-no-slashing-in-hederas-proof-of-stake.html plain text: hedera-why-is-there-no-slashing-in-hederas-proof-of-stake.txt item: #1855 of 3327 id: hedera-winners-of-hedera20-virtual-hackathon-chosen-from-over-800-competing-developers author: hedera title: hedera-winners-of-hedera20-virtual-hackathon-chosen-from-over-800-competing-developers date: None words: 1436 flesch: 55 summary: Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. OXILES crowned overall winner of Hedera six-week virtual hackathon; awarded prize of $20,000 worth of hbars by judges from IBM, Hedera, Tata Communications, and Wipro DALLAS, June 25, 2020 -- Hedera Hashgraph, an enterprise-grade distributed ledger platform, today announced the winners of the Hedera20 Virtual Hackathon. keywords: ecosystem; hackathon; hashgraph; hedera; network; place; winners cache: hedera-winners-of-hedera20-virtual-hackathon-chosen-from-over-800-competing-developers.html plain text: hedera-winners-of-hedera20-virtual-hackathon-chosen-from-over-800-competing-developers.txt item: #1856 of 3327 id: hedera-wipro-joins-hedera-governing-council-to-provide-decentralized-governance-model-for-blockchain author: hedera title: hedera-wipro-joins-hedera-governing-council-to-provide-decentralized-governance-model-for-blockchain date: None words: 1186 flesch: 51 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Ed Marquez Pragmatic Blockchain Design Patterns – Integrating Blockchain into Business Processes Michiel Mulders Zero Cost EthereumTransaction on Success: Hedera's New Fee Model for Relay Operators Oliver Thorn Hedera Adopts Chainlink Standard for Cross-Chain Interoperability To Accelerate Ecosystem Adoption Hedera Team Hedera Developer Highlights March 2025 Michiel Mulders Hedera Release Cycle Overview Ed Marquez View All Posts Sign up for the newsletter CONNECT WITH US Transparency Open Source Audits & Standards Sustainability Commitment Carbon Offsets Governance Hedera Council Public Policy Treasury Management Meeting Minutes LLC Agreement Node Requirements Community Events Meetups HBAR Telegram Developer Discord Twitter Community Support FAQ Network Status Developer Discord StackOverflow Brand Brand Guidelines Built on Hedera Logo Hedera Store About Team Partners Journey Roadmap Careers Contact General Inquiry Public Relations © 2018-2025 Hedera Hashgraph, LLC. keywords: council; ecosystem; governance; hedera; network; wipro cache: hedera-wipro-joins-hedera-governing-council-to-provide-decentralized-governance-model-for-blockchain.html plain text: hedera-wipro-joins-hedera-governing-council-to-provide-decentralized-governance-model-for-blockchain.txt item: #1857 of 3327 id: hedera-zero-cost-ethereumtransaction-on-success-hederas-new-fee-model-for-relay-operators author: hedera title: hedera-zero-cost-ethereumtransaction-on-success-hederas-new-fee-model-for-relay-operators date: None words: 1244 flesch: 42 summary: Hedera Council Over 30 highly diversified organizations govern Hedera. Zero Cost EthereumTransaction on Success: Hedera's New Fee… | Hedera Hedera Network Services Token Service Mint and configure tokens and accounts. keywords: fee; fees; hedera; network; operators; relay cache: hedera-zero-cost-ethereumtransaction-on-success-hederas-new-fee-model-for-relay-operators.html plain text: hedera-zero-cost-ethereumtransaction-on-success-hederas-new-fee-model-for-relay-operators.txt item: #1858 of 3327 id: hyperledgerfabric-CONTRIBUTING author: hyperledgerfabric title: hyperledgerfabric-CONTRIBUTING date: None words: 2852 flesch: 58 summary: Release roadmap¶ The Fabric release roadmap is managed as a list of GitHub issues with Epic label. Ways to contribute¶ There are many ways you can contribute to Hyperledger Fabric, both as a user and as a developer. keywords: documentation; fabric; github; issue; maintainers cache: hyperledgerfabric-CONTRIBUTING.html plain text: hyperledgerfabric-CONTRIBUTING.txt item: #1859 of 3327 id: hyperledgerfabric-Fabric-FAQ author: hyperledgerfabric title: hyperledgerfabric-Fabric-FAQ date: None words: 1459 flesch: 57 summary: If you model asset data as JSON in chaincode and use CouchDB as the state database, you can also perform complex rich queries against the chaincode data values, using the CouchDB JSON query language within chaincode. Note that the key concepts topic also explains when to use private data instead of a channel. keywords: answer; chaincode; data; question cache: hyperledgerfabric-Fabric-FAQ.html plain text: hyperledgerfabric-Fabric-FAQ.txt item: #1860 of 3327 id: hyperledgerfabric-access_control author: hyperledgerfabric title: hyperledgerfabric-access_control date: None words: 1733 flesch: 47 summary: Policies can be structured in one of two ways: as Signature policies or as an ImplicitMeta policy. ImplicitMeta policies¶ ImplicitMeta policies aggregate the result of policies deeper in the configuration hierarchy that are ultimately defined by Signature policies. keywords: access; channel; policies; policy cache: hyperledgerfabric-access_control.html plain text: hyperledgerfabric-access_control.txt item: #1861 of 3327 id: hyperledgerfabric-advice_for_writers author: hyperledgerfabric title: hyperledgerfabric-advice_for_writers date: None words: 393 flesch: 39 summary: Connect with other writers — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction Ways to contribute Contributing documentation Connect with other writers Getting started Discord Documentation workgroup call Join a language translation workgroup Other ways to connect Contributing documentation Creating a new translation Style guide for contributors Project Governance Contribution guide Legal stuff Related Topics Glossary Releases Still Have Questions? keywords: documentation; fabric cache: hyperledgerfabric-advice_for_writers.html plain text: hyperledgerfabric-advice_for_writers.txt item: #1862 of 3327 id: hyperledgerfabric-architecture author: hyperledgerfabric title: hyperledgerfabric-architecture date: None words: 172 flesch: 8 summary: Architecture Reference — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Getting Started - Install Getting Started - Run Fabric Tutorials Deploying a production network Operations Guides Upgrading to the latest release Commands Reference Architecture Reference Hyperledger Fabric CA's User Guide Transaction Flow Fabric Gateway Service Discovery Defining capability requirements Channels CouchDB as the State Database Peer channel-based event services Private Data Read-Write set semantics Gossip data dissemination protocol Performance considerations Frequently Asked Questions Contributions Welcome! Glossary Releases Still Have Questions? keywords: fabric cache: hyperledgerfabric-architecture.html plain text: hyperledgerfabric-architecture.txt item: #1863 of 3327 id: hyperledgerfabric-blockchain author: hyperledgerfabric title: hyperledgerfabric-blockchain date: None words: 1760 flesch: 48 summary: What is Hyperledger Fabric? Hyperledger Fabric Model How Fabric networks are structured Identity Membership Service Provider (MSP) Policies Peers Ledger The Ordering Service Smart Contracts and Chaincode Fabric chaincode lifecycle Private data Channel capabilities Security Model Use Cases Getting Started - Install Getting Started - Run Fabric Tutorials Deploying a production network Operations With the ability to coordinate their business network through a shared ledger, blockchain networks can reduce the time, cost, and risk associated with private information and processing while improving trust and visibility. keywords: blockchain; hyperledger; ledger; network cache: hyperledgerfabric-blockchain.html plain text: hyperledgerfabric-blockchain.txt item: #1864 of 3327 id: hyperledgerfabric-build author: hyperledgerfabric title: hyperledgerfabric-build date: None words: 487 flesch: 46 summary: Building Hyperledger Fabric — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction To build Hyperledger Fabric: make dist-clean all Building the documentation¶ If you are contributing to the documentation, you can build the Fabric documentation on your local machine. keywords: fabric; hyperledger cache: hyperledgerfabric-build.html plain text: hyperledgerfabric-build.txt item: #1865 of 3327 id: hyperledgerfabric-capabilities_concept author: hyperledgerfabric title: hyperledgerfabric-capabilities_concept date: None words: 1597 flesch: 40 summary: If you do use the legacy system channel process, the orderer and channel capabilities of a channel are inherited by default from the ordering system channel, where modifying them are the exclusive purview of ordering service admins. For a full look at the current valid orderer, application, and channel capabilities check out a sample configtx.yaml file, which lists them in the “Capabilities” section. keywords: capabilities; capability; channel; ordering cache: hyperledgerfabric-capabilities_concept.html plain text: hyperledgerfabric-capabilities_concept.txt item: #1866 of 3327 id: hyperledgerfabric-capability_requirements author: hyperledgerfabric title: hyperledgerfabric-capability_requirements date: None words: 393 flesch: 15 summary: As discussed in Channel capabilities, capability requirements are defined per channel in the channel configuration (found in the channel’s most recent configuration block). For a version of this topic that includes information about the system channel, check out Capability requirements from the v2.2 documentation. keywords: capabilities; channel cache: hyperledgerfabric-capability_requirements.html plain text: hyperledgerfabric-capability_requirements.txt item: #1867 of 3327 id: hyperledgerfabric-cc_basic author: hyperledgerfabric title: hyperledgerfabric-cc_basic date: None words: 2108 flesch: 46 summary: End-to-end with the test-network¶ The test-network and some of the chaincodes have been updated to support running chaincode-as-a-service. Because each container is on the fabric-test network, changing the port can avoid collisions with other chaincode containers. keywords: chaincode; docker; fabric; network; peer; run cache: hyperledgerfabric-cc_basic.html plain text: hyperledgerfabric-cc_basic.txt item: #1868 of 3327 id: hyperledgerfabric-cc_launcher author: hyperledgerfabric title: hyperledgerfabric-cc_launcher date: None words: 2219 flesch: 46 summary: Chaincode packages created with peer lifecycle chaincode package use this new format. Endorsement policies Pluggable transaction endorsement and validation Access Control Lists (ACL) MSP Implementation with Identity Mixer Identity Mixer MSP configuration generator (idemixgen) The Operations Service Metrics Reference External Builders and Launchers External builder model External builder and launcher API Configuring external builders and launchers Chaincode packages Lifecycle chaincode package contents Chaincode packages and external builders Running Chaincode as an External Service Error handling Logging Control Securing Communication With Transport Layer Security (TLS) Configuring and operating a Raft ordering service Migrating from Kafka to Raft Bringing up a Kafka-based Ordering Service Upgrading to the latest release Commands Reference Architecture Reference Frequently Asked Questions Contributions Welcome! keywords: bin; build; builders; chaincode; package; peer cache: hyperledgerfabric-cc_launcher.html plain text: hyperledgerfabric-cc_launcher.txt item: #1869 of 3327 id: hyperledgerfabric-cc_service author: hyperledgerfabric title: hyperledgerfabric-cc_service date: None words: 2089 flesch: 50 summary: Status Hyperledger Fabric Docs Operations Guides Running Chaincode as an External Service View page source Running Chaincode as an External Service¶ Attention: This page is for advanced users who choose to configure chaincode as a service external to the Fabric peer. New users of chaincode should start with deploying a smart contract to a channel before proceeding with this tutorial. keywords: bin; chaincode; fabric; peer; server; service cache: hyperledgerfabric-cc_service.html plain text: hyperledgerfabric-cc_service.txt item: #1870 of 3327 id: hyperledgerfabric-certs_management author: hyperledgerfabric title: hyperledgerfabric-certs_management date: None words: 2097 flesch: 31 summary: Reference - Enroll Orderer Org CA Admin TLS CA Certificates¶ TLS CA Root Certificates and TLS CA Admin Certificates provide authorization to interact with the certificate authority for the TLS, as described below. TLS CA Root Certificates are self-signed certificates if creating a new Certificate Authority (CA), or provided by an external CA. keywords: ─ cert.pem; ─ keystore; ─ signcerts; ─ ─; ├ ─ cache: hyperledgerfabric-certs_management.html plain text: hyperledgerfabric-certs_management.txt item: #1871 of 3327 id: hyperledgerfabric-chaincode4ade author: hyperledgerfabric title: hyperledgerfabric-chaincode4ade date: None words: 3400 flesch: 60 summary: TransactionContextInterface) error { assets := []Asset{ {ID: asset1, Color: blue, Size: 5, Owner: Tomoko, AppraisedValue: 300}, {ID: asset2, Color: red, Size: 5, Owner: Brad, AppraisedValue: 400}, {ID: asset3, Color: green, Size: 10, Owner: Jin Soo, AppraisedValue: 500}, {ID: asset4, Color: yellow, Size: 10, Owner: Max, AppraisedValue: 600}, {ID: asset5, Color: black, Size: 15, Owner: Adriana, AppraisedValue: 700}, {ID: asset6, Color: white, Size: 15, Owner: Michel, AppraisedValue: 800}, } for _, asset := range assets { assetJSON, err := json. TransactionContextInterface) error { assets := []Asset{ {ID: asset1, Color: blue, Size: 5, Owner: Tomoko, AppraisedValue: 300}, {ID: asset2, Color: red, Size: 5, Owner: Brad, AppraisedValue: 400}, {ID: asset3, Color: green, Size: 10, Owner: Jin Soo, AppraisedValue: 500}, {ID: asset4, Color: yellow, Size: 10, Owner: Max, AppraisedValue: 600}, {ID: asset5, Color: black, Size: 15, Owner: Adriana, AppraisedValue: 700}, {ID: asset6, Color: white, Size: 15, Owner: Michel, AppraisedValue: 800}, } for _, asset := range assets { assetJSON, err := json. keywords: asset; err; nil; return cache: hyperledgerfabric-chaincode4ade.html plain text: hyperledgerfabric-chaincode4ade.txt item: #1872 of 3327 id: hyperledgerfabric-chaincode_lifecycle author: hyperledgerfabric title: hyperledgerfabric-chaincode_lifecycle date: None words: 4270 flesch: 50 summary: You can also use a signature policy if your channel has a large number Idemix organizations, which cannot approve chaincode definitions or endorse chaincode and may prevent the channel from reaching a majority as a result. As a result, they do not need to provide a packageID as part of chaincode definition. keywords: chaincode; chaincode definition; channel; definition; organization cache: hyperledgerfabric-chaincode_lifecycle.html plain text: hyperledgerfabric-chaincode_lifecycle.txt item: #1873 of 3327 id: hyperledgerfabric-channel_policies author: hyperledgerfabric title: hyperledgerfabric-channel_policies date: None words: 1974 flesch: 40 summary: If you use the default policies used by the Fabric test network or the Fabric sample configuration, each channel you create will use a combination of signature policies, ImplicitMeta policies, and Access Control Lists to determine how organizations interact with the channel and agree to update the channel structure. The advantage of using ImplicitMeta policies and signature policies together is that you can set the rules for governance at the channel level, while allowing each channel member to select the identities that are required to sign for their organization. keywords: channel; policies; policy; signature cache: hyperledgerfabric-channel_policies.html plain text: hyperledgerfabric-channel_policies.txt item: #1874 of 3327 id: hyperledgerfabric-channel_update_tutorial author: hyperledgerfabric title: hyperledgerfabric-channel_update_tutorial date: None words: 5175 flesch: 39 summary: Run the following commands to make sure that we are operating as the Org3 admin: # you can issue all of these commands at once export CORE_PEER_LOCALMSPID=Org3MSP export CORE_PEER_TLS_ROOTCERT_FILE=${PWD}/organizations/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=${PWD}/organizations/peerOrganizations/org3.example.com/users/Admin@org3.example.com/msp export CORE_PEER_ADDRESS=localhost:11051 We can now just use the peer channel update command to sign the update as the Org3 admin before submitting it to the orderer. peer channel update -f channel-artifacts/anchor_update_in_envelope.pb -c channel1 peer channel joinbysnapshot --snapshotpath keywords: block; chaincode; channel; configuration; export; org3; peer; update cache: hyperledgerfabric-channel_update_tutorial.html plain text: hyperledgerfabric-channel_update_tutorial.txt item: #1875 of 3327 id: hyperledgerfabric-channels author: hyperledgerfabric title: hyperledgerfabric-channels date: None words: 495 flesch: 35 summary: This isolation of peers and ledger data, by channel, allows network members that require private and confidential transactions to coexist with business competitors and other restricted members, on the same blockchain network. Although any one anchor peer can belong to multiple channels, and therefore maintain multiple ledgers, no ledger data can pass from one channel to another. keywords: channel; fabric cache: hyperledgerfabric-channels.html plain text: hyperledgerfabric-channels.txt item: #1876 of 3327 id: hyperledgerfabric-command_ref author: hyperledgerfabric title: hyperledgerfabric-command_ref date: None words: 148 flesch: 10 summary: Commands Reference — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Getting Started - Install Getting Started - Run Fabric Tutorials Deploying a production network Operations Guides Upgrading to the latest release Commands Reference peer peer chaincode peer lifecycle chaincode peer channel peer snapshot peer version peer node osnadmin channel configtxgen configtxlator cryptogen ledgerutil Service Discovery CLI Fabric-CA Commands Architecture Reference Frequently Asked Questions Contributions Welcome! Status Hyperledger Fabric Docs Commands Reference View page source Commands Reference¶ peer peer chaincode peer lifecycle chaincode peer channel peer snapshot peer version peer node osnadmin channel configtxgen configtxlator cryptogen ledgerutil Service Discovery CLI Fabric-CA Commands Next Previous © Copyright Hyperledger 2020-2023. keywords: peer cache: hyperledgerfabric-command_ref.html plain text: hyperledgerfabric-command_ref.txt item: #1877 of 3327 id: hyperledgerfabric-config_update author: hyperledgerfabric title: hyperledgerfabric-config_update date: None words: 3579 flesch: -50 summary: Ensures that networks and channels process things in the same way, creating deterministic results for things like channel configuration updates and chaincode invocations. Information identifying the structure of blockchain networks and the processes governing how structures interact are contained in channel configurations. keywords: admins; channel; config; mod_policy; value; version cache: hyperledgerfabric-config_update.html plain text: hyperledgerfabric-config_update.txt item: #1878 of 3327 id: hyperledgerfabric-configtx author: hyperledgerfabric title: hyperledgerfabric-configtx date: None words: 1782 flesch: 38 summary: Channel configuration has the following important properties: Versioned: All elements of the configuration have an associated version which is advanced with every modification. What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Getting Started - Install Getting Started - Run Fabric Tutorials Deploying a production network Operations Guides Membership Service Providers (MSP) Certificates Management Guide Taking ledger snapshots and using them to join channels Using a Hardware Security Module (HSM) Channel Configuration (configtx) Anatomy of a configuration Configuration updates Permitted configuration groups and values Channel configuration Channel creation Endorsement policies Pluggable transaction endorsement and validation Access Control Lists (ACL) MSP Implementation with Identity Mixer Identity Mixer MSP configuration generator (idemixgen) The Operations Service Metrics Reference External Builders and Launchers Running Chaincode as an External Service Error handling Logging Control Securing Communication With Transport Layer Security (TLS) keywords: configuration; map; string cache: hyperledgerfabric-configtx.html plain text: hyperledgerfabric-configtx.txt item: #1879 of 3327 id: hyperledgerfabric-configtxgen author: hyperledgerfabric title: hyperledgerfabric-configtxgen date: None words: 681 flesch: 27 summary: configtxgen¶ Usage of configtxgen: -asOrg string Performs the config generation as a particular organization (by name), only including values in the write set that org (likely) has privilege to set -channelCreateTxBaseProfile string Specifies a profile to consider as the orderer system channel current state to allow modification of non-application parameters during channel create tx generation. (This output is useful for channel reconfiguration workflows, such as adding a member). keywords: channel; configtxgen; peer cache: hyperledgerfabric-configtxgen.html plain text: hyperledgerfabric-configtxgen.txt item: #1880 of 3327 id: hyperledgerfabric-configtxlator author: hyperledgerfabric title: hyperledgerfabric-configtxlator date: None words: 815 flesch: 46 summary: configtxlator proto_encode¶ usage: configtxlator proto_encode --type=TYPE Because configtxlator does not have any access to data, key material, or other information which might be considered sensitive, there is no risk to the owner of the server in exposing it to other clients. keywords: --help; configtxlator; peer cache: hyperledgerfabric-configtxlator.html plain text: hyperledgerfabric-configtxlator.txt item: #1881 of 3327 id: hyperledgerfabric-couchdb_as_state_database author: hyperledgerfabric title: hyperledgerfabric-couchdb_as_state_database date: None words: 2350 flesch: 53 summary: The asset transfer Fabric sample demonstrates use of CouchDB queries from chaincode. Specifically, the CouchDB limit keyword will not be honored in CouchDB queries since Fabric itself manages the pagination of query results and implicitly sets the pageSize limit that is passed to CouchDB. keywords: chaincode; couchdb; database; json; queries; query cache: hyperledgerfabric-couchdb_as_state_database.html plain text: hyperledgerfabric-couchdb_as_state_database.txt item: #1882 of 3327 id: hyperledgerfabric-couchdb_tutorial author: hyperledgerfabric title: hyperledgerfabric-couchdb_tutorial date: None words: 4999 flesch: 47 summary: When defining an index for use in chaincode queries, each one must be defined in its own text file with the extension *.json and the index definition must be formatted in the CouchDB index JSON format. In our case owner should be the first value in index fields. keywords: chaincode; couchdb; database; index; ledger; peer; queries; query; use cache: hyperledgerfabric-couchdb_tutorial.html plain text: hyperledgerfabric-couchdb_tutorial.txt item: #1883 of 3327 id: hyperledgerfabric-create_channel_config author: hyperledgerfabric title: hyperledgerfabric-create_channel_config date: None words: 2716 flesch: 40 summary: Organizations Capabilities Application Orderer Channel Profiles Because different sections of the file work together to create the policies that govern the channel, we will discuss channel policies in their own tutorial. The MSP ID acts as a unique identifier for your organization, and is referred to by channel policies and is included in the transactions submitted to the channel. keywords: channel; configuration; fabric; ordering; organizations; policies cache: hyperledgerfabric-create_channel_config.html plain text: hyperledgerfabric-create_channel_config.txt item: #1884 of 3327 id: hyperledgerfabric-create_channel_overview author: hyperledgerfabric title: hyperledgerfabric-create_channel_overview date: None words: 457 flesch: 31 summary: Channels are a private layer of communication between specific organizations and are invisible to other members of the network. While the peers, ordering nodes, and Certificate Authorities form the physical infrastructure of the network, channels are the process by which organizations connect with each other and interact. keywords: channel; fabric cache: hyperledgerfabric-create_channel_overview.html plain text: hyperledgerfabric-create_channel_overview.txt item: #1885 of 3327 id: hyperledgerfabric-create_channel_participation author: hyperledgerfabric title: hyperledgerfabric-create_channel_participation date: None words: 7098 flesch: 44 summary: Status Hyperledger Fabric Docs Tutorials Creating a channel Create a channel View page source Create a channel¶ To simplify the channel creation process and enhance the privacy and scalability of channels, it is now possible to create application channels (where transactions involving assets happen) without first creating a “system channel” managed by the ordering service. With this new process, all channels are application channels, so the concept of a list of organizations who can create channels no longer applies. keywords: channel; file; orderer; ordering; system channel; tls; ─ ─ cache: hyperledgerfabric-create_channel_participation.html plain text: hyperledgerfabric-create_channel_participation.txt item: #1886 of 3327 id: hyperledgerfabric-create_channel_test_net author: hyperledgerfabric title: hyperledgerfabric-create_channel_test_net date: None words: 3996 flesch: 29 summary: += {AnchorPeers:{mod_policy: Admins,value:{anchor_peers: [{host: peer0.org1.example.com,port: 7051}]},version: 0}}' config_copy.json > modified_config.json After this step, we have an updated version of channel configuration in JSON format in the modified_config.json file. You can confirm that the channel has been updated successfully by running the peer channel info command: peer channel getinfo -c channel1 keywords: block; channel; command; create; fabric; network; peer; test cache: hyperledgerfabric-create_channel_test_net.html plain text: hyperledgerfabric-create_channel_test_net.txt item: #1887 of 3327 id: hyperledgerfabric-cryptogen author: hyperledgerfabric title: hyperledgerfabric-cryptogen date: None words: 419 flesch: 36 summary: Status Hyperledger Fabric Docs Commands Reference cryptogen View page source cryptogen¶ cryptogen is an utility for generating Hyperledger Fabric key material. [] Extend existing network cryptogen generate¶ usage: cryptogen generate [] Generate key material Flags: --help keywords: --help; cryptogen cache: hyperledgerfabric-cryptogen.html plain text: hyperledgerfabric-cryptogen.txt item: #1888 of 3327 id: hyperledgerfabric-deploy_chaincode author: hyperledgerfabric title: hyperledgerfabric-deploy_chaincode date: None words: 6539 flesch: 37 summary: peer lifecycle chaincode queryinstalled The package ID is the combination of the chaincode label and a hash of the chaincode binaries. Paste the package ID returned by peer lifecycle chaincode queryinstalled into the command below. keywords: chaincode; chaincode definition; chaincode package; channel; command; fabric; lifecycle chaincode; peer cache: hyperledgerfabric-deploy_chaincode.html plain text: hyperledgerfabric-deploy_chaincode.txt item: #1889 of 3327 id: hyperledgerfabric-deployment_guide_overview author: hyperledgerfabric title: hyperledgerfabric-deployment_guide_overview date: None words: 4640 flesch: 52 summary: Status Hyperledger Fabric Docs Deploying a production network View page source Deploying a production network¶ This deployment guide is a high level overview of the proper sequence for setting up production Fabric network components, in addition to best practices and a few of the many considerations to keep in mind when deploying. However, Kubernetes features a number of helpful tools that have made it a popular container management platform for deploying and managing Fabric networks. keywords: configuration; need; network; node; ordering; peer; production cache: hyperledgerfabric-deployment_guide_overview.html plain text: hyperledgerfabric-deployment_guide_overview.txt item: #1890 of 3327 id: hyperledgerfabric-devenv author: hyperledgerfabric title: hyperledgerfabric-devenv date: None words: 970 flesch: 44 summary: Once the library has been installed, configure Fabric to use pkcs11-spy as the PKCS #11 library and set the PKCS11SPY environment variable to the real library. For test environments, SoftHSM can be used to satisfy this requirement. keywords: fabric; install; softhsm cache: hyperledgerfabric-devenv.html plain text: hyperledgerfabric-devenv.txt item: #1891 of 3327 id: hyperledgerfabric-discovery-cli author: hyperledgerfabric title: hyperledgerfabric-discovery-cli date: None words: 1866 flesch: -160 summary: The discover CLI supports all server-side queries: Peer membership query Configuration query Endorsers query Let’s go over them and see how they should be invoked and parsed: Peer membership query:¶ $ discover --configFile conf.yaml peers --channel mychannel --server The Identity that is returned is the enrollment certificate of the peer, and it can be parsed with a combination of jq and openssl: $ discover --configFile conf.yaml peers --channel mychannel --server keywords: certificate; discovery; key; peer; query; tls cache: hyperledgerfabric-discovery-cli.html plain text: hyperledgerfabric-discovery-cli.txt item: #1892 of 3327 id: hyperledgerfabric-discovery-overview author: hyperledgerfabric title: hyperledgerfabric-discovery-overview date: None words: 1107 flesch: 49 summary: Why do we need service discovery?¶ In order to execute chaincode on peers, submit transactions to orderers, and to be updated about the status of transactions, applications connect to an API exposed by an SDK. In addition to the CA and TLS certificates of the orderers and peers on the channel – as well as their IP addresses and port numbers – it must know the relevant endorsement policies as well as which peers have the chaincode installed (so the application knows which peers to send chaincode proposals to). keywords: discovery; peers; service cache: hyperledgerfabric-discovery-overview.html plain text: hyperledgerfabric-discovery-overview.txt item: #1893 of 3327 id: hyperledgerfabric-docs_guide author: hyperledgerfabric title: hyperledgerfabric-docs_guide date: None words: 1909 flesch: 49 summary: In this topic, we’re going to cover: An introduction to the documentation Repository folder structure International language folder structure Making documentation changes Building the documentation on your local machine Building the documentation on GitHub with ReadTheDocs Getting your change approved Making a change to Commands Reference Adding a new CLI command Introduction¶ The Fabric documentation is written in a combination of Markdown and reStructuredText source files. Install the following prerequisites; you may need to adjust depending on your OS: Docker For US English: git clone git@github.com:hyperledger/fabric.git cd fabric make docs For International Languages (Malayalam as an example): git clone git@github.com:hyperledger/fabric-docs-i18n.git cd fabric-docs-i18n make docs-lang-ml_IN The make command generates documentation html files in the docs/build/html/ folder which you can now view locally; simply navigate your browser to the docs/build/html/index.html file. keywords: documentation; fabric; ─ ─; ├ ─ cache: hyperledgerfabric-docs_guide.html plain text: hyperledgerfabric-docs_guide.txt item: #1894 of 3327 id: hyperledgerfabric-enable_cc_lifecycle author: hyperledgerfabric title: hyperledgerfabric-enable_cc_lifecycle date: None words: 1369 flesch: 34 summary: This process involves a series of channel configuration updates the relevant users will have to perform. acls: { _lifecycle/CheckCommitReadiness: { policy_ref: /Channel/Application/Writers }, _lifecycle/CommitChaincodeDefinition: { policy_ref: /Channel/Application/Writers }, _lifecycle/QueryChaincodeDefinition: { policy_ref: /Channel/Application/Readers }, _lifecycle/QueryChaincodeDefinitions: { policy_ref: /Channel/Application/Readers You can leave the same environment in place as when you previously edited application channels. keywords: application; channel; lifecycle cache: hyperledgerfabric-enable_cc_lifecycle.html plain text: hyperledgerfabric-enable_cc_lifecycle.txt item: #1895 of 3327 id: hyperledgerfabric-enable_tls author: hyperledgerfabric title: hyperledgerfabric-enable_tls date: None words: 1492 flesch: 31 summary: To enable TLS client authentication on a peer node, set the peer configuration property peer.tls.clientAuthRequired to true and set the peer.tls.clientRootCAs.files property to the CA chain file(s) that contain(s) the CA certificate chain(s) that issued TLS certificates for your organization’s clients. To enable TLS on a peer node set the following peer configuration properties: peer.tls.enabled = true peer.tls.cert.file = fully qualified path of the file that contains the TLS server certificate peer.tls.key.file = fully qualified path of the file that contains the TLS server private key By default, TLS client authentication is turned off when TLS is enabled on a peer node. keywords: certificate; client; peer; tls cache: hyperledgerfabric-enable_tls.html plain text: hyperledgerfabric-enable_tls.txt item: #1896 of 3327 id: hyperledgerfabric-endorsement-policies author: hyperledgerfabric title: hyperledgerfabric-endorsement-policies date: None words: 2558 flesch: 37 summary: Endorsement policies Multiple ways to require endorsement Setting chaincode-level endorsement policies Endorsement policy syntax Setting collection-level endorsement policies Setting key-level endorsement policies Validation Pluggable transaction endorsement and validation Access Control Lists (ACL) MSP Implementation with Identity Mixer Identity Mixer MSP configuration generator (idemixgen) The Operations Service Metrics Reference External Builders and Launchers Running Chaincode as an External Service Error handling Logging Control Securing Communication With Transport Layer Security (TLS) Configuring and operating a Raft ordering service Migrating from Kafka to Raft Bringing up a Kafka-based Ordering Service Upgrading to the latest release Commands Reference Architecture Reference Frequently Asked Questions Contributions Welcome! Multiple ways to require endorsement¶ By default, endorsement policies are specified in the chaincode definition, which is agreed to by channel members and then committed to a channel (that is, one endorsement policy covers all of the state associated with a chaincode). keywords: chaincode; collection; endorsement; level; policy cache: hyperledgerfabric-endorsement-policies.html plain text: hyperledgerfabric-endorsement-policies.txt item: #1897 of 3327 id: hyperledgerfabric-error-handling author: hyperledgerfabric title: hyperledgerfabric-error-handling date: None words: 580 flesch: 48 summary: Endorsement policies Pluggable transaction endorsement and validation Access Control Lists (ACL) MSP Implementation with Identity Mixer Identity Mixer MSP configuration generator (idemixgen) The Operations Service Metrics Reference External Builders and Launchers Running Chaincode as an External Service Error handling General Overview Usage Instructions General guidelines for error handling in Hyperledger Fabric Example program Logging Control Securing Communication With Transport Layer Security (TLS) Configuring and operating a Raft ordering service Migrating from Kafka to Raft Bringing up a Kafka-based Ordering Service Upgrading to the latest release Commands Reference Architecture Reference Frequently Asked Questions Contributions Welcome! General guidelines for error handling in Hyperledger Fabric¶ If you are servicing a user request, you should log the error and return it. keywords: error; fabric; stack cache: hyperledgerfabric-error-handling.html plain text: hyperledgerfabric-error-handling.txt item: #1898 of 3327 id: hyperledgerfabric-fabric-ca-commands author: hyperledgerfabric title: hyperledgerfabric-fabric-ca-commands date: None words: 232 flesch: 34 summary: Status Hyperledger Fabric Docs Commands Reference Fabric-CA Commands View page source Fabric-CA Commands¶ The Hyperledger Fabric CA is a Certificate Authority (CA) for Hyperledger Fabric. Fabric-CA Commands — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction keywords: fabric cache: hyperledgerfabric-fabric-ca-commands.html plain text: hyperledgerfabric-fabric-ca-commands.txt item: #1899 of 3327 id: hyperledgerfabric-fabric_model author: hyperledgerfabric title: hyperledgerfabric-fabric_model date: None words: 1492 flesch: 37 summary: Hyperledger Fabric provides the ability to modify assets using chaincode transactions. What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Introduction Hyperledger Fabric Model Assets Chaincode Ledger Features Privacy Security & Membership Services Consensus How Fabric networks are structured Identity Membership Service Provider (MSP) Policies Peers Ledger The Ordering Service Smart Contracts and Chaincode Fabric chaincode lifecycle Private data Channel capabilities Security Model Use Cases Getting Started - Install Getting Started - Run Fabric Tutorials Deploying a production network Operations Guides Upgrading to the latest release Commands Reference Architecture Reference Frequently Asked Questions Contributions Welcome! keywords: chaincode; fabric; hyperledger; ledger; transactions cache: hyperledgerfabric-fabric_model.html plain text: hyperledgerfabric-fabric_model.txt item: #1900 of 3327 id: hyperledgerfabric-gateway author: hyperledgerfabric title: hyperledgerfabric-gateway date: None words: 1806 flesch: 42 summary: Status Hyperledger Fabric Docs Architecture Reference Fabric Gateway View page source Fabric Gateway¶ Fabric Gateway is a service, introduced in Hyperledger Fabric v2.4 peers, that provides a simplified, minimal API for submitting transactions to a Fabric network. Fabric Gateway — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Getting Started - Install Getting Started - Run Fabric Tutorials Deploying a production network Operations Guides Upgrading to the latest release Commands Reference Architecture Reference Hyperledger Fabric CA's User Guide Transaction Flow Fabric Gateway Writing client applications Client application APIs How the gateway endorses your transaction proposal Targeting specific endorsement peers Retry and error handling Listening for events Service Discovery Defining capability requirements Channels CouchDB as the State Database Peer channel-based event services Private Data Read-Write set semantics Gossip data dissemination protocol Performance considerations Frequently Asked Questions Contributions Welcome! keywords: fabric; gateway; peer; transaction cache: hyperledgerfabric-gateway.html plain text: hyperledgerfabric-gateway.txt item: #1901 of 3327 id: hyperledgerfabric-genindex author: hyperledgerfabric title: hyperledgerfabric-genindex date: None words: 88 flesch: 25 summary: Index — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Getting Started - Install Getting Started - Run Fabric Tutorials Deploying a production network Operations Guides Upgrading to the latest release Commands Reference Architecture Reference Frequently Asked Questions Contributions Welcome! Glossary Releases Still Have Questions? keywords: hyperledger cache: hyperledgerfabric-genindex.html plain text: hyperledgerfabric-genindex.txt item: #1902 of 3327 id: hyperledgerfabric-getting_started author: hyperledgerfabric title: hyperledgerfabric-getting_started date: None words: 184 flesch: 34 summary: Getting Started - Install — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction Status Hyperledger Fabric Docs Getting Started - Install View page source Getting Started - Install¶ The Fabric application stack has five layers: Prerequisite software: the base layer needed to run the software, for example, Docker. Fabric and Fabric samples: the Fabric executables to run a Fabric network along with sample code. keywords: fabric cache: hyperledgerfabric-getting_started.html plain text: hyperledgerfabric-getting_started.txt item: #1903 of 3327 id: hyperledgerfabric-getting_started_run_fabric author: hyperledgerfabric title: hyperledgerfabric-getting_started_run_fabric date: None words: 201 flesch: 40 summary: Running a Test Network tutorial - helps you understand how Fabric networks work. Getting Started - Run Fabric — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction What’s new in Hyperledger Fabric v2.x Release notes Key Concepts keywords: fabric cache: hyperledgerfabric-getting_started_run_fabric.html plain text: hyperledgerfabric-getting_started_run_fabric.txt item: #1904 of 3327 id: hyperledgerfabric-github author: hyperledgerfabric title: hyperledgerfabric-github date: None words: 2039 flesch: 53 summary: You can delete them by executing the following commands: git branch -d git push --delete origin Syncing Your Fork With the Upstream Repository¶ Create a Local Feature Branch for Your Development work¶ To protect the state of the existing branches in your forked repository and ensure the work you perform is saved in a logical location, the use of feature branches in your forked repository is recommended. keywords: branch; git; pull; repository cache: hyperledgerfabric-github.html plain text: hyperledgerfabric-github.txt item: #1905 of 3327 id: hyperledgerfabric-glossary author: hyperledgerfabric title: hyperledgerfabric-glossary date: None words: 3763 flesch: 51 summary: Endorsement¶ Refers to the process where specific peer nodes execute a chaincode transaction and return a proposal response to the client application. Hyperledger Fabric CA¶ Hyperledger Fabric CA is the default Certificate Authority component, which issues PKI-based certificates to network member organizations and their users. keywords: block; chaincode; channel; ledger; ordering; peers; state; transaction cache: hyperledgerfabric-glossary.html plain text: hyperledgerfabric-glossary.txt item: #1906 of 3327 id: hyperledgerfabric-go-style author: hyperledgerfabric title: hyperledgerfabric-go-style date: None words: 2469 flesch: 53 summary: For instance, Hyperledger Fabric code allows two databases to be used as a state database (goleveldb and couchdb) via interface statedb.VersionedDB. However, This loose coupling generally makes sense at the boundary of larger components, particularly when it’s hard to use real implementation of dependency components for tests. keywords: code; component; dependency; interface; tests cache: hyperledgerfabric-go-style.html plain text: hyperledgerfabric-go-style.txt item: #1907 of 3327 id: hyperledgerfabric-gossip author: hyperledgerfabric title: hyperledgerfabric-gossip date: None words: 1767 flesch: 40 summary: Dynamic leader election¶ Dynamic leader election enables organization peers to elect one peer which will connect to the ordering service and pull out new blocks. Static leader election¶ Static leader election allows you to manually define one or more peers within an organization as leader peers. keywords: channel; gossip; leader; organization; peers cache: hyperledgerfabric-gossip.html plain text: hyperledgerfabric-gossip.txt item: #1908 of 3327 id: hyperledgerfabric-hsm author: hyperledgerfabric title: hyperledgerfabric-hsm date: None words: 1792 flesch: 41 summary: Status Hyperledger Fabric Docs Operations Guides Using a Hardware Security Module (HSM) View page source Using a Hardware Security Module (HSM)¶ The cryptographic operations performed by Fabric nodes can be delegated to a Hardware Security Module (HSM). As an example, you would add the following environment and volumes variables to your docker compose file: environment: - SOFTHSM2_CONF=/etc/hyperledger/fabric/config.file volumes: - /home/softhsm/config.file:/etc/hyperledger/fabric/config.file - /usr/local/Cellar/softhsm/2.1.0/lib/softhsm/libsofthsm2.so:/etc/hyperledger/fabric/libsofthsm2.so Setting up a network using HSM¶ If you are deploying Fabric nodes using an HSM, your private keys need to be generated and stored inside the HSM rather than inside the keystore folder of the node’s local MSP folder. keywords: fabric; hsm; node; pkcs11 cache: hyperledgerfabric-hsm.html plain text: hyperledgerfabric-hsm.txt item: #1909 of 3327 id: hyperledgerfabric-idemix author: hyperledgerfabric title: hyperledgerfabric-idemix date: None words: 2189 flesch: 43 summary: Endorsement policies Pluggable transaction endorsement and validation Access Control Lists (ACL) MSP Implementation with Identity Mixer What is Idemix? How to use Idemix Idemix and chaincode Current limitations Technical summary Comparing Idemix credentials to X.509 certificates Topology Information Underlying cryptographic protocols Identity Mixer MSP configuration generator (idemixgen) The Operations Service Metrics Reference External Builders and Launchers Running Chaincode as an External Service Error handling Logging Control Securing Communication With Transport Layer Security (TLS) Configuring and operating a Raft ordering service Migrating from Kafka to Raft Bringing up a Kafka-based Ordering Service Upgrading to the latest release Commands Reference Architecture Reference Frequently Asked Questions Contributions Welcome! Technical summary¶ Comparing Idemix credentials to X.509 certificates¶ The certificate/credential concept and the issuance process are very similar in Idemix and X.509 certs: a set of attributes is digitally signed with a signature that cannot be forged and there is a secret key to which a credential is cryptographically bound. keywords: credential; fabric; idemix; identity; msp cache: hyperledgerfabric-idemix.html plain text: hyperledgerfabric-idemix.txt item: #1910 of 3327 id: hyperledgerfabric-idemixgen author: hyperledgerfabric title: hyperledgerfabric-idemixgen date: None words: 503 flesch: 24 summary: Endorsement policies Pluggable transaction endorsement and validation Access Control Lists (ACL) MSP Implementation with Identity Mixer Identity Mixer MSP configuration generator (idemixgen) Directory Structure CA Key Generation Adding a Default Signer The Operations Service Metrics Reference External Builders and Launchers Running Chaincode as an External Service Error handling Logging Control Securing Communication With Transport Layer Security (TLS) Configuring and operating a Raft ordering service Migrating from Kafka to Raft Bringing up a Kafka-based Ordering Service Upgrading to the latest release Commands Reference Architecture Reference Frequently Asked Questions Contributions Welcome! Identity Mixer MSP configuration generator (idemixgen) — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction keywords: idemixgen; identity; msp cache: hyperledgerfabric-idemixgen.html plain text: hyperledgerfabric-idemixgen.txt item: #1911 of 3327 id: hyperledgerfabric-identity author: hyperledgerfabric title: hyperledgerfabric-identity date: None words: 2427 flesch: 48 summary: This component — known as Fabric CA is a private root CA provider capable of managing digital identities of Fabric participants that have the form of X.509 certificates. A PKI is comprised of Certificate Authorities who issue digital certificates to parties (e.g., users of a service, service provider), who then use them to authenticate themselves in the messages they exchange in their environment. keywords: cas; certificate; fabric; identity; key cache: hyperledgerfabric-identity.html plain text: hyperledgerfabric-identity.txt item: #1912 of 3327 id: hyperledgerfabric-index author: hyperledgerfabric title: hyperledgerfabric-index date: None words: 254 flesch: 41 summary: A Blockchain Platform for the Enterprise — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction Next © Copyright Hyperledger 2020-2023. keywords: fabric cache: hyperledgerfabric-index.html plain text: hyperledgerfabric-index.txt item: #1913 of 3327 id: hyperledgerfabric-install author: hyperledgerfabric title: hyperledgerfabric-install date: None words: 691 flesch: 43 summary: Downloads the latest Hyperledger Fabric Docker images and tags them as latest Downloads the following platform-specific Hyperledger Fabric CLI tool binaries and config files into the fabric-samples /bin and /config directories. Install Fabric and Fabric Samples — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction keywords: fabric; install; samples cache: hyperledgerfabric-install.html plain text: hyperledgerfabric-install.txt item: #1914 of 3327 id: hyperledgerfabric-international_languages author: hyperledgerfabric title: hyperledgerfabric-international_languages date: None words: 1208 flesch: 46 summary: Language workgroups have found the following tools helpful: DocTranslator TexTra Suggested next topics¶ Once you have published the mandatory initial set of topics on the documentation website, you are encouraged to translate these topics, in order. Glossary Translating this topic provides the essential reference material that helps other language translators make progress; in short, it allows your workgroup to scale. keywords: fabric; language; translation cache: hyperledgerfabric-international_languages.html plain text: hyperledgerfabric-international_languages.txt item: #1915 of 3327 id: hyperledgerfabric-kafka author: hyperledgerfabric title: hyperledgerfabric-kafka date: None words: 1800 flesch: 60 summary: Kafka brokers are backward compatible with older protocol versions. Set up the OSNs and Kafka cluster so that they communicate over SSL. keywords: channel; kafka; ordering; service; set cache: hyperledgerfabric-kafka.html plain text: hyperledgerfabric-kafka.txt item: #1916 of 3327 id: hyperledgerfabric-kafka_raft_migration author: hyperledgerfabric title: hyperledgerfabric-kafka_raft_migration date: None words: 2104 flesch: 53 summary: As the process for migration involves several channel configuration update transactions, do not attempt to migrate from Kafka to Raft without first familiarizing yourself with the Add an Organization to a Channel tutorial, which describes the channel update process in detail. At the end of the migration process, every channel will have the same consenter set of Raft nodes. keywords: channel; configuration; migration; ordering; raft cache: hyperledgerfabric-kafka_raft_migration.html plain text: hyperledgerfabric-kafka_raft_migration.txt item: #1917 of 3327 id: hyperledgerfabric-key_concepts author: hyperledgerfabric title: hyperledgerfabric-key_concepts date: None words: 166 flesch: -6 summary: Key Concepts — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Introduction Hyperledger Fabric Model How Fabric networks are structured Identity Membership Service Provider (MSP) Policies Peers Ledger The Ordering Service Smart Contracts and Chaincode Fabric chaincode lifecycle Private data Channel capabilities Security Model Use Cases Getting Started - Install Getting Started - Run Fabric Tutorials Deploying a production network Operations Guides Upgrading to the latest release Commands Reference Architecture Reference Frequently Asked Questions Contributions Welcome! Glossary Releases Still Have Questions? Status Hyperledger Fabric Docs Key Concepts View page source Key Concepts¶ Introduction Hyperledger Fabric Model How Fabric networks are structured Identity Membership Service Provider (MSP) Policies Peers Ledger The Ordering Service Smart Contracts and Chaincode Fabric chaincode lifecycle Private data Channel capabilities Security Model Use Cases Next Previous © Copyright Hyperledger 2020-2023. keywords: fabric cache: hyperledgerfabric-key_concepts.html plain text: hyperledgerfabric-key_concepts.txt item: #1918 of 3327 id: hyperledgerfabric-ledger author: hyperledgerfabric title: hyperledgerfabric-ledger date: None words: 3280 flesch: 64 summary: Hyperledger Fabric is motivated by these same two concerns – to present the current value of a set of ledger states, and to capture the history of the transactions that determined these states. Firstly, there’s a world state – a database that holds current values of a set of ledger states. keywords: block; blockchain; ledger; state; transactions; world cache: hyperledgerfabric-ledger.html plain text: hyperledgerfabric-ledger.txt item: #1919 of 3327 id: hyperledgerfabric-ledgerutil author: hyperledgerfabric title: hyperledgerfabric-ledgerutil date: None words: 2536 flesch: 52 summary: The command does not necessarily have to be used in tandem with the ledgerutil compare command and can be used with a user generated JSON list of keys or an edited ledgerutil compare output JSON file to filter transactions in a more general approach. Below is an example of a valid input JSON file: { ledgerid:mychannel, diffRecords:[ { namespace:marbles, key:marble1, snapshotrecord1:{ value:{\docType\:\marble\,\name\:\marble1\,\color\:\blue\,\size\:35,\owner\:\tom\},blockNum:3, txNum:0 }, snapshotrecord2:{ value:{\docType\:\marble\,\name\:\marble1\,\color\:\blue\,\size\:35,\owner\:\jerry\},blockNum:4, txNum:0 } } { namespace:marbles, key:marble2 } ] } Notice that in the above example for key marbles marble2, the fields for the snapshot records and the height of the key’s found divergence which are present in output JSON files generated by the ledgerutil compare command are exempt. keywords: block; file; json; key; ledgerutil cache: hyperledgerfabric-ledgerutil.html plain text: hyperledgerfabric-ledgerutil.txt item: #1920 of 3327 id: hyperledgerfabric-logging-control author: hyperledgerfabric title: hyperledgerfabric-logging-control date: None words: 1044 flesch: 44 summary: Logging severity levels are specified using case-insensitive strings chosen from FATAL | PANIC | ERROR In the pretty-printed example below, the loggers ledgermgmt, kvledger, and peer are generating logs. keywords: debug; info; logging cache: hyperledgerfabric-logging-control.html plain text: hyperledgerfabric-logging-control.txt item: #1921 of 3327 id: hyperledgerfabric-membership author: hyperledgerfabric title: hyperledgerfabric-membership date: None words: 4092 flesch: 51 summary: Certificate: cacerts/ca.sampleorg-cert.pem OrganizationalUnitIdentifier: orderer In the example above, there are 4 possible Node OU ROLES for the MSP: client peer admin orderer This convention allows you to distinguish MSP roles by the OU present in the CommonName attribute of the X509 certificate. The channel MSP configuration does not include this folder, because channel MSPs solely aim to offer identity validation functionalities and not signing abilities. keywords: channel; msp; msps; network; node; organization cache: hyperledgerfabric-membership.html plain text: hyperledgerfabric-membership.txt item: #1922 of 3327 id: hyperledgerfabric-metrics_reference author: hyperledgerfabric title: hyperledgerfabric-metrics_reference date: None words: 2852 flesch: 27 summary: gauge The block number of the latest snapshot. version gossip_comm_messages_received counter Number of messages received gossip_comm_messages_sent counter Number of messages sent gossip_comm_overflow_count counter Number of outgoing queue buffer overflows gossip_leader_election_leader gauge Peer is leader (1) or follower (0) channel gossip_membership_total_peers_known gauge Total known peers channel gossip_payload_buffer_size gauge Size of the payload buffer channel gossip_privdata_commit_block_duration histogram Time it takes to commit private data and the corresponding block (in seconds) channel gossip_privdata_fetch_duration histogram Time it takes to fetch missing private data from peers (in seconds) channel gossip_privdata_list_missing_duration histogram Time it takes to list the missing private data (in seconds) channel gossip_privdata_pull_duration histogram Time it takes to pull a missing private data element (in seconds) channel gossip_privdata_purge_duration histogram Time it takes to purge private data (in seconds) channel gossip_privdata_reconciliation_duration histogram Time it takes for reconciliation to complete (in seconds) channel gossip_privdata_retrieve_duration histogram Time it takes to retrieve missing private data elements from the ledger (in seconds) channel gossip_privdata_send_duration histogram Time it takes to send a missing private data element (in seconds) channel gossip_privdata_validation_duration histogram Time it takes to validate a block (in seconds) channel gossip_state_commit_duration histogram Time it takes to commit a block in seconds channel gossip_state_height gauge Current ledger height channel grpc_comm_conn_closed counter gRPC keywords: channel; counter; gauge; histogram; number; seconds; time cache: hyperledgerfabric-metrics_reference.html plain text: hyperledgerfabric-metrics_reference.txt item: #1923 of 3327 id: hyperledgerfabric-msp author: hyperledgerfabric title: hyperledgerfabric-msp date: None words: 2625 flesch: 38 summary: What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Getting Started - Install Getting Started - Run Fabric Tutorials Deploying a production network Operations Guides Membership Service Providers (MSP) MSP configuration How to generate MSP certificates and their signing keys? Organizational Units Identity classification Adding MSPs to channels Best practices Certificates Management Guide How to generate MSP certificates and their signing keys?¶ Openssl can be used to generate X.509 certificates and keys. keywords: cas; certificates; identity; msp; peers cache: hyperledgerfabric-msp.html plain text: hyperledgerfabric-msp.txt item: #1924 of 3327 id: hyperledgerfabric-msp-identity-validity-rules author: hyperledgerfabric title: hyperledgerfabric-msp-identity-validity-rules date: None words: 406 flesch: 49 summary: As mentioned in MSP description, MSPs may be configured with a set of root certificate authorities (rCAs), and optionally a set of intermediate certificate authorities (iCAs). id The default MSP implementation accepts as valid identities X.509 certificates signed by the appropriate authorities. keywords: certificate; msp cache: hyperledgerfabric-msp-identity-validity-rules.html plain text: hyperledgerfabric-msp-identity-validity-rules.txt item: #1925 of 3327 id: hyperledgerfabric-network author: hyperledgerfabric title: hyperledgerfabric-network date: None words: 3848 flesch: 51 summary: This is not a mandatory configuration because even if the same ordering nodes are joined to multiple channels, each channel has a separate instance of the ordering service, and is more common in channels in which multiple orderer organizations come together to contribute nodes to an ordering service. While it also possible to add more orderer organizations (who may or may not contribute their own nodes), in this example we’ll describe the process of how a peer organization, R3, is added to the channel configuration CC1 of channel C1. keywords: channel; components; network; ordering; organizations cache: hyperledgerfabric-network.html plain text: hyperledgerfabric-network.txt item: #1926 of 3327 id: hyperledgerfabric-operations_service author: hyperledgerfabric title: hyperledgerfabric-operations_service date: None words: 1764 flesch: 35 summary: Peer¶ For each peer, the operations server can be configured in the operations section of core.yaml: operations: # host and port for the operations server listenAddress: 127.0.0.1:9443 # TLS configuration for the operations endpoint tls: # TLS enabled enabled: true # path to PEM encoded server certificate for the operations server cert: file: tls/server.crt # path to PEM encoded server key for the operations server key: file: tls/server.key # most operations service endpoints require client authentication when TLS # is enabled. Certificate: tls/server.crt # Paths to PEM encoded ca certificates to trust for client authentication ClientRootCAs: [] # Most operations service endpoints require client authentication when TLS # is enabled. keywords: certificate; metrics; operations; service; tls cache: hyperledgerfabric-operations_service.html plain text: hyperledgerfabric-operations_service.txt item: #1927 of 3327 id: hyperledgerfabric-ops_guide author: hyperledgerfabric title: hyperledgerfabric-ops_guide date: None words: 280 flesch: -10 summary: Status Hyperledger Fabric Docs Operations Guides View page source Operations Guides¶ Membership Service Providers (MSP) Certificates Management Guide Taking ledger snapshots and using them to join channels Using a Hardware Security Module (HSM) Channel Configuration (configtx) Endorsement policies Pluggable transaction endorsement and validation Access Control Lists (ACL) MSP Implementation with Identity Mixer Identity Mixer MSP configuration generator (idemixgen) The Operations Service Metrics Reference External Builders and Launchers Running Chaincode as an External Service Error handling Logging Control Securing Communication With Transport Layer Security (TLS) Configuring and operating a Raft ordering service Migrating from Kafka to Raft Bringing up a Kafka-based Ordering Service Next Previous © Copyright Hyperledger 2020-2023. Endorsement policies Pluggable transaction endorsement and validation Access Control Lists (ACL) MSP Implementation with Identity Mixer Identity Mixer MSP configuration generator (idemixgen) The Operations Service Metrics Reference External Builders and Launchers Running Chaincode as an External Service Error handling Logging Control Securing Communication With Transport Layer Security (TLS) Configuring and operating a Raft ordering service Migrating from Kafka to Raft Bringing up a Kafka-based Ordering Service Upgrading to the latest release Commands Reference Architecture Reference Frequently Asked Questions Contributions Welcome! keywords: msp; service cache: hyperledgerfabric-ops_guide.html plain text: hyperledgerfabric-ops_guide.txt item: #1928 of 3327 id: hyperledgerfabric-ordererchecklist author: hyperledgerfabric title: hyperledgerfabric-ordererchecklist date: None words: 3554 flesch: 53 summary: TLS: # TLS enabled Enabled: false # Certificate is the location of the PEM encoded TLS certificate Certificate: # TLS: # TLS enabled Enabled: false # Certificate is the location of the PEM encoded TLS certificate Certificate: # keywords: node; orderer; ordering; set; tls; value cache: hyperledgerfabric-ordererchecklist.html plain text: hyperledgerfabric-ordererchecklist.txt item: #1929 of 3327 id: hyperledgerfabric-ordererdeploy author: hyperledgerfabric title: hyperledgerfabric-ordererdeploy date: None words: 2455 flesch: 48 summary: ─ msp ├── cacerts └── tlscacerts ├── orderers └── orderer0.ordererOrg1.example.com ├── msp └── tls You should have already used your certificate authority of choice to generate the orderer enrollment certificate, TLS certificate, private keys, and the MSPs that Fabric must consume. TLS.ClientRootCAs: - The path to and file name of the admin client TLS CA Root certificate. keywords: msp; node; orderer; ordering; ─ ─; ├ ─ cache: hyperledgerfabric-ordererdeploy.html plain text: hyperledgerfabric-ordererdeploy.txt item: #1930 of 3327 id: hyperledgerfabric-ordererplan author: hyperledgerfabric title: hyperledgerfabric-ordererplan date: None words: 1558 flesch: 47 summary: Like the “peer container” associated with the peer, this container encapsulates the ordering process that orders transactions into blocks for all channels on which the ordering node is a consenter (ordering nodes also validate actions in particular cases). If you have several ordering nodes available to use, ensure that each node is a consenter on approximately the same number of channels. keywords: fabric; nodes; ordering; service cache: hyperledgerfabric-ordererplan.html plain text: hyperledgerfabric-ordererplan.txt item: #1931 of 3327 id: hyperledgerfabric-ordering_service author: hyperledgerfabric title: hyperledgerfabric-ordering_service date: None words: 3944 flesch: 51 summary: Ordering nodes can be added or removed from a channel as needed as long as only a single node is added or removed at a time. Kafka (deprecated in v2.x)¶ The other crash fault tolerant ordering service supported by Fabric is an adaptation of a Kafka distributed streaming platform for use as a cluster of ordering nodes. keywords: channel; kafka; nodes; ordering; raft; service; transaction cache: hyperledgerfabric-ordering_service.html plain text: hyperledgerfabric-ordering_service.txt item: #1932 of 3327 id: hyperledgerfabric-osnadminchannel author: hyperledgerfabric title: hyperledgerfabric-osnadminchannel date: None words: 1134 flesch: 43 summary: Syntax¶ The osnadmin channel command has the following subcommands: join list remove osnadmin channel¶ usage: osnadmin channel osnadmin channel join -o orderer.example.com:9443 keywords: channel; file; osn cache: hyperledgerfabric-osnadminchannel.html plain text: hyperledgerfabric-osnadminchannel.txt item: #1933 of 3327 id: hyperledgerfabric-peer-chaincode-devmode author: hyperledgerfabric title: hyperledgerfabric-peer-chaincode-devmode date: None words: 1619 flesch: 33 summary: Run the following commands to build the binaries for orderer, peer, and configtxgen: make orderer peer configtxgen When successful you should see results similar to: Building build/bin/orderer GOBIN=/testDevMode/fabric/build/bin go install -tags -ldflags -X github.com/hyperledger/fabric/common/metadata.Version=2.3.0 -X github.com/hyperledger/fabric/common/metadata.CommitSHA=298695ae2 -X github.com/hyperledger/fabric/common/metadata.BaseDockerLabel=org.hyperledger.fabric -X github.com/hyperledger/fabric/common/metadata.DockerNamespace=hyperledger github.com/hyperledger/fabric/cmd/orderer Building build/bin/peer GOBIN=/testDevMode/fabric/build/bin go install -tags -ldflags -X github.com/hyperledger/fabric/common/metadata.Version=2.3.0 -X github.com/hyperledger/fabric/common/metadata.CommitSHA=298695ae2 -X github.com/hyperledger/fabric/common/metadata.BaseDockerLabel=org.hyperledger.fabric -X github.com/hyperledger/fabric/common/metadata.DockerNamespace=hyperledger github.com/hyperledger/fabric/cmd/peer Building build/bin/configtxgen GOBIN=/testDevMode/fabric/build/bin go install -tags -ldflags -X github.com/hyperledger/fabric/common/metadata.Version=2.3.0 -X github.com/hyperledger/fabric/common/metadata.CommitSHA=298695ae2 -X github.com/hyperledger/fabric/common/metadata.BaseDockerLabel=org.hyperledger.fabric -X github.com/hyperledger/fabric/common/metadata.DockerNamespace=hyperledger github.com/hyperledger/fabric/cmd/configtxgen Set the PATH environment variable to include orderer and peer binaries: export PATH=$(pwd)/build/bin:$PATH Set the FABRIC_CFG_PATH environment variable to point to the sampleconfig folder: export FABRIC_CFG_PATH=$(pwd)/sampleconfig Create the hyperledger subdirectory in the /var directory. CORE_PEER_ADDRESS=127.0.0.1:7051 peer chaincode invoke -o keywords: chaincode; edt; fabric; peer cache: hyperledgerfabric-peer-chaincode-devmode.html plain text: hyperledgerfabric-peer-chaincode-devmode.txt item: #1934 of 3327 id: hyperledgerfabric-peer_event_services author: hyperledgerfabric title: hyperledgerfabric-peer_event_services date: None words: 818 flesch: 45 summary: Client applications can also request block events starting from a certain block number, allowing client applications to receive prior block events or to resume receiving events in case the application or the peer has been restarted or lost connection. Status Hyperledger Fabric Docs Architecture Reference Peer channel-based event services View page source Peer channel-based event services¶ General overview¶ The peer’s event service allows client applications to receive block events as blocks are committed to a peer’s ledger. keywords: block; events; peer cache: hyperledgerfabric-peer_event_services.html plain text: hyperledgerfabric-peer_event_services.txt item: #1935 of 3327 id: hyperledgerfabric-peer_ledger_snapshot author: hyperledgerfabric title: hyperledgerfabric-peer_ledger_snapshot date: None words: 3328 flesch: 55 summary: You can list the pending snapshots by issuing a command similar to: peer snapshot listpending -c testchannel --peerAddress 127.0.0.1:22509 Taking a snapshot¶ For the full list of snapshot-related commands, check out peer snapshot commands. keywords: block; channel; data; peer; snapshot cache: hyperledgerfabric-peer_ledger_snapshot.html plain text: hyperledgerfabric-peer_ledger_snapshot.txt item: #1936 of 3327 id: hyperledgerfabric-peerchaincode author: hyperledgerfabric title: hyperledgerfabric-peerchaincode date: None words: 4141 flesch: 32 summary: Usage: peer chaincode instantiate [flags] Flags: -C, --channelID string The channel on which this command should be executed --collections-config string The fully qualified path to the collection JSON file including the file name --connectionProfile string Connection profile that provides the necessary connection information for the network. Usage: peer chaincode upgrade [flags] Flags: -C, --channelID string The channel on which this command should be executed --collections-config string The fully qualified path to the collection JSON file including the file name --connectionProfile string Connection profile that provides the necessary connection information for the network. keywords: chaincode; orderer endpoint; peer; string; string path; tls cache: hyperledgerfabric-peerchaincode.html plain text: hyperledgerfabric-peerchaincode.txt item: #1937 of 3327 id: hyperledgerfabric-peerchannel author: hyperledgerfabric title: hyperledgerfabric-peerchannel date: None words: 3399 flesch: 36 summary: Usage: peer channel [command] Available Commands: create Create a channel fetch Fetch a block getinfo get blockchain information of a specified channel. joinbysnapshot Joins the peer to a channel by the specified snapshot joinbysnapshotstatus Query if joinbysnapshot is running for any channel list List of channels peer has joined. keywords: orderer endpoint; peer; string; tls; use cache: hyperledgerfabric-peerchannel.html plain text: hyperledgerfabric-peerchannel.txt item: #1938 of 3327 id: hyperledgerfabric-peerchecklist author: hyperledgerfabric title: hyperledgerfabric-peerchecklist date: None words: 4139 flesch: 50 summary: And if chaincodeListenAddress is not specified, address is selected from # peer address (see below). Specify the address that other peers in the organization use to connect to this peer, for example, peer0.org1.example.com:7051. keywords: default; organization; peer; service; set; tls; value cache: hyperledgerfabric-peerchecklist.html plain text: hyperledgerfabric-peerchecklist.txt item: #1939 of 3327 id: hyperledgerfabric-peercommand author: hyperledgerfabric title: hyperledgerfabric-peercommand date: None words: 530 flesch: 48 summary: For example peer --help peer channel --help peer channel list --help See individual peer subcommands for more detail. [option] [flags] peer channel [option] keywords: channel; peer cache: hyperledgerfabric-peercommand.html plain text: hyperledgerfabric-peercommand.txt item: #1940 of 3327 id: hyperledgerfabric-peerdeploy author: hyperledgerfabric title: hyperledgerfabric-peerdeploy date: None words: 1917 flesch: 50 summary: The resulting folder structure is similar to: ├── fabric ├── bin │ ├── configtxgen │ ├── configtxlator │ ├── cryptogen │ ├── discover │ ├── idemixgen │ ├── orderer │ └── peer └── config ├── configtx.yaml ├── core.yaml └── orderer.yaml Along with the relevant binaries, you will receive both the peer binary executable and the peer configuration file, core.yaml, that is required to launch a peer on the network. Deploy peers and ordering nodes Creating a peer Planning for a production peer Checklist for a production peer Deploy the peer Creating an ordering node Next steps Operations Guides Upgrading to the latest release Commands Reference Architecture Reference Frequently Asked Questions Contributions Welcome! keywords: certificate; fabric; peer; ─ ─; ├ ─ cache: hyperledgerfabric-peerdeploy.html plain text: hyperledgerfabric-peerdeploy.txt item: #1941 of 3327 id: hyperledgerfabric-peerlifecycle author: hyperledgerfabric title: hyperledgerfabric-peerlifecycle date: None words: 5627 flesch: 24 summary: What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Getting Started - Install Getting Started - Run Fabric Tutorials Deploying a production network Operations Guides Upgrading to the latest release Commands Reference peer peer chaincode peer lifecycle chaincode Syntax peer lifecycle peer lifecycle chaincode peer lifecycle chaincode package peer lifecycle chaincode install peer lifecycle chaincode queryinstalled peer lifecycle chaincode getinstalledpackage peer lifecycle chaincode calculatepackageid peer lifecycle chaincode approveformyorg peer lifecycle chaincode queryapproved peer lifecycle chaincode checkcommitreadiness peer lifecycle chaincode commit peer lifecycle chaincode querycommitted Example Usage peer lifecycle chaincode package example peer lifecycle chaincode install example peer lifecycle chaincode queryinstalled example peer lifecycle chaincode getinstalledpackage example peer lifecycle chaincode calculatepackageid example peer lifecycle chaincode approveformyorg example peer lifecycle chaincode queryapproved example peer lifecycle chaincode checkcommitreadiness example peer lifecycle chaincode commit example peer lifecycle chaincode querycommitted example peer channel peer snapshot peer version peer node osnadmin channel configtxgen configtxlator cryptogen ledgerutil Service Discovery CLI Fabric-CA Commands Architecture Reference Frequently Asked Questions Contributions Welcome! peer lifecycle chaincode¶ Perform chaincode operations: package|install|queryinstalled|getinstalledpackage|calculatepackageid|approveformyorg|queryapproved|checkcommitreadiness|commit|querycommitted Usage: peer lifecycle chaincode keywords: chaincode; peer; peer lifecycle; string; tls cache: hyperledgerfabric-peerlifecycle.html plain text: hyperledgerfabric-peerlifecycle.txt item: #1942 of 3327 id: hyperledgerfabric-peernode author: hyperledgerfabric title: hyperledgerfabric-peernode date: None words: 1272 flesch: 66 summary: peer node reset example¶ The following command: peer node reset resets all channels in the peer to the genesis block, i.e., the first block in the channel. peer node start example¶ The following command: peer node start --peer-chaincodedev starts a peer node in chaincode development mode. keywords: command; node; peer cache: hyperledgerfabric-peernode.html plain text: hyperledgerfabric-peernode.txt item: #1943 of 3327 id: hyperledgerfabric-peerplan author: hyperledgerfabric title: hyperledgerfabric-peerplan date: None words: 1991 flesch: 48 summary: To reduce network traffic, in Fabric v2.2 the default core.yaml is configured for peers to pull blocks from the ordering service instead of through gossip dissemination among peers (with the exception of private data, which are still sent from peer to peer using gossip). For peer gossip to work you need to configure four parameters. keywords: chaincode; container; fabric; network; peer cache: hyperledgerfabric-peerplan.html plain text: hyperledgerfabric-peerplan.txt item: #1944 of 3327 id: hyperledgerfabric-peers author: hyperledgerfabric title: hyperledgerfabric-peers date: None words: 4265 flesch: 50 summary: Smart contracts and ledgers encapsulate the processes and information, respectively, that are shared by channel peers. This means that peer blocks are almost exactly the same as the blocks received from the orderer, except for a valid or invalid indicator on each transaction in the block. keywords: fabric; ledger; network; peers; service; transaction cache: hyperledgerfabric-peers.html plain text: hyperledgerfabric-peers.txt item: #1945 of 3327 id: hyperledgerfabric-peersnapshot author: hyperledgerfabric title: hyperledgerfabric-peersnapshot date: None words: 744 flesch: 41 summary: List pending snapshot requests on channel mychannel for peer0.org1.example.com:7051: peer snapshot listpending -c mychannel --peerAddress peer0.org1.example.com:7051 Successfully got pending snapshot requests: Usage: peer snapshot listpending [flags] Flags: -c, --channelID string The channel on which this command should be executed -h, --help help for listpending --peerAddress string The address of the peer to connect to --tlsRootCertFile string The path to the TLS root cert file of the peer to connect to, required if TLS is enabled and ignored if TLS is disabled. keywords: peer; snapshot cache: hyperledgerfabric-peersnapshot.html plain text: hyperledgerfabric-peersnapshot.txt item: #1946 of 3327 id: hyperledgerfabric-peerversion author: hyperledgerfabric title: hyperledgerfabric-peerversion date: None words: 213 flesch: 34 summary: Usage: peer version [flags] Flags: -h, --help help for version This work is licensed under a Creative Commons Attribution 4.0 International License. peer version¶ Print current version of the fabric peer server. keywords: peer; version cache: hyperledgerfabric-peerversion.html plain text: hyperledgerfabric-peerversion.txt item: #1947 of 3327 id: hyperledgerfabric-performance author: hyperledgerfabric title: hyperledgerfabric-performance date: None words: 3977 flesch: 51 summary: Using an off-chain store for queries gives you much more control over the data, and query transactions do not affect Hyperledger Fabric peer and network performance. These allocations affect network performance and even node stability, so you must continuously monitor CPU, Memory, Disk Space, and Disk and Network I/O to ensure that you are well within the limits of your allocated resources. keywords: block; chaincode; couchdb; fabric; max; number; peer; performance; service cache: hyperledgerfabric-performance.html plain text: hyperledgerfabric-performance.txt item: #1948 of 3327 id: hyperledgerfabric-pluggable_endorsement_and_validation author: hyperledgerfabric title: hyperledgerfabric-pluggable_endorsement_and_validation date: None words: 2011 flesch: 30 summary: Currently Fabric comes with the following dependencies for validation plugins: IdentityDeserializer: Currently Fabric comes with the following dependencies for endorsement plugins: SigningIdentityFetcher: Returns an instance of SigningIdentity based on a given signed proposal: // SigningIdentity signs messages and serializes its public identity to bytes type SigningIdentity interface { // Serialize returns a byte representation of this identity which is used to verify // messages signed by this SigningIdentity Serialize() ([]byte, error) // keywords: endorsement; error; interface; peer; plugin; validation cache: hyperledgerfabric-pluggable_endorsement_and_validation.html plain text: hyperledgerfabric-pluggable_endorsement_and_validation.txt item: #1949 of 3327 id: hyperledgerfabric-policies author: hyperledgerfabric title: hyperledgerfabric-policies date: None words: 1718 flesch: 42 summary: For code which constructs signature policies, consult fabric/common/cauthdsl/cauthdsl_builder.go. message SignaturePolicyEnvelope { int32 version = 1; SignaturePolicy policy = 2; repeated MSPPrincipal identities = 3; } message SignaturePolicy { message NOutOf { int32 N = 1; repeated SignaturePolicy policies = 2; } oneof Type { int32 signed_by = 1; NOutOf n_out_of = 2; } } keywords: msp; policies; policy cache: hyperledgerfabric-policies.html plain text: hyperledgerfabric-policies.txt item: #1950 of 3327 id: hyperledgerfabric-prereqs author: hyperledgerfabric title: hyperledgerfabric-prereqs date: None words: 1066 flesch: 52 summary: Finally, you need to ensure Docker Desktop has integration enabled for your distribution so it can interact with Docker elements, such as a bash command window. Refer to Docker Desktop WSL2 backend for more information Microsoft VS Code (Optional)¶ Microsoft VS Code provides an IDE that has tight integration with WSL2 Linux Distributions. keywords: docker; install; version cache: hyperledgerfabric-prereqs.html plain text: hyperledgerfabric-prereqs.txt item: #1951 of 3327 id: hyperledgerfabric-private-data author: hyperledgerfabric title: hyperledgerfabric-private-data date: None words: 3745 flesch: 49 summary: Private data sharing patterns¶ When modeling private data collections per organization, multiple patterns become available for sharing or transferring private data without the overhead of defining many multilateral collections. Additionally, since private data is disseminated peer-to-peer rather than via blocks, use private data collections when transaction data must be kept confidential from ordering service nodes. keywords: chaincode; channel; collection; data; peer; transaction cache: hyperledgerfabric-private-data.html plain text: hyperledgerfabric-private-data.txt item: #1952 of 3327 id: hyperledgerfabric-private-data-arch author: hyperledgerfabric title: hyperledgerfabric-private-data-arch date: None words: 3890 flesch: 41 summary: Since implicit private data collections are not explicitly defined, it is not possible to set the additional collection properties. Note Since implicit private data collections are not explicitly defined, it is not possible to associate CouchDB indexes with them. keywords: chaincode; collection; data; definition; peers; policy cache: hyperledgerfabric-private-data-arch.html plain text: hyperledgerfabric-private-data-arch.txt item: #1953 of 3327 id: hyperledgerfabric-private_data_tutorial author: hyperledgerfabric title: hyperledgerfabric-private_data_tutorial date: None words: 6242 flesch: 38 summary: Before we go through the transfer scenario, we will discuss how organizations can use private data collections in Fabric. The smart contract uses the Fabric chaincode API to read and write private data to private data collections using the GetPrivateData() and PutPrivateData() functions. keywords: asset; chaincode; collection; data; err; fabric; org1; org2; peer cache: hyperledgerfabric-private_data_tutorial.html plain text: hyperledgerfabric-private_data_tutorial.txt item: #1954 of 3327 id: hyperledgerfabric-questions author: hyperledgerfabric title: hyperledgerfabric-questions date: None words: 195 flesch: 45 summary: Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction Still Have Questions? keywords: questions cache: hyperledgerfabric-questions.html plain text: hyperledgerfabric-questions.txt item: #1955 of 3327 id: hyperledgerfabric-raft_configuration author: hyperledgerfabric title: hyperledgerfabric-raft_configuration date: None words: 3009 flesch: 51 summary: Raft nodes identify each other using TLS pinning, so in order to impersonate a Raft node, an attacker needs to obtain the private key of its TLS certificate. Because Raft nodes share the same communication layer across channels (this does not mean they share data — they do not!), if a Raft node is part of the consenter set in many channels, you might want to lengthen the amount of time it takes to trigger an election to avoid inadvertent leader elections. keywords: channel; node; ordering; raft; service; tls cache: hyperledgerfabric-raft_configuration.html plain text: hyperledgerfabric-raft_configuration.txt item: #1956 of 3327 id: hyperledgerfabric-readwrite author: hyperledgerfabric title: hyperledgerfabric-readwrite date: None words: 1259 flesch: 51 summary: Transaction validation and updating world state using read-write set¶ A committer uses the read set portion of the read-write set for checking the validity of a transaction and the write set portion of the read-write set for updating the versions and the values of the affected keys. This scheme has many advantages over the incremental number scheme - primarily, it enables other components such as statedb, transaction simulation and validation to make efficient design choices. keywords: read; set; transaction cache: hyperledgerfabric-readwrite.html plain text: hyperledgerfabric-readwrite.txt item: #1957 of 3327 id: hyperledgerfabric-releases author: hyperledgerfabric title: hyperledgerfabric-releases date: None words: 103 flesch: 29 summary: Releases — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Getting Started - Install Getting Started - Run Fabric Tutorials Deploying a production network Operations Guides Upgrading to the latest release Commands Reference Architecture Reference Frequently Asked Questions Contributions Welcome! Status Hyperledger Fabric Docs Releases View page source Releases¶ Hyperledger Fabric releases are documented on the Fabric Github page. keywords: fabric cache: hyperledgerfabric-releases.html plain text: hyperledgerfabric-releases.txt item: #1958 of 3327 id: hyperledgerfabric-sdk_chaincode author: hyperledgerfabric title: hyperledgerfabric-sdk_chaincode date: None words: 198 flesch: 32 summary: Fabric Contract APIs and Application APIs — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction Fabric Gateway client API and documentation. keywords: fabric cache: hyperledgerfabric-sdk_chaincode.html plain text: hyperledgerfabric-sdk_chaincode.txt item: #1959 of 3327 id: hyperledgerfabric-search author: hyperledgerfabric title: hyperledgerfabric-search date: None words: 95 flesch: 34 summary: Search — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction © Copyright Hyperledger 2020-2023. keywords: hyperledger cache: hyperledgerfabric-search.html plain text: hyperledgerfabric-search.txt item: #1960 of 3327 id: hyperledgerfabric-secured_private_asset_transfer_tutorial author: hyperledgerfabric title: hyperledgerfabric-secured_private_asset_transfer_tutorial date: None words: 4328 flesch: 34 summary: To further secure asset transfer, consider including other parties in the asset’s state based endorsement policy, such as a trusted third party. --ordererTLSHostnameOverride orderer.example.com --tls --cafile ${PWD}/organizations/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C mychannel -n secured -c {\function\:\ReadAsset\,\Args\:[\$ASSET_ID\]} The command will return the record that the asset is owned by Org1: {object_type:asset,asset_id:d9923f21b770adbc79cbcc47a3aeecc81dc7f030bd129155301ce3932be7fbcc,owner_org:Org1MSP,public_description:A new asset for Org1MSP} Because the market for assets is hot, Org1 wants to flip this asset and put it up for sale. keywords: asset; orderer.example.com; org1; price; transfer cache: hyperledgerfabric-secured_private_asset_transfer_tutorial.html plain text: hyperledgerfabric-secured_private_asset_transfer_tutorial.txt item: #1961 of 3327 id: hyperledgerfabric-security_model author: hyperledgerfabric title: hyperledgerfabric-security_model date: None words: 1464 flesch: 42 summary: What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Introduction Hyperledger Fabric Model How Fabric networks are structured Identity Membership Service Provider (MSP) Policies Peers Ledger The Ordering Service Smart Contracts and Chaincode Fabric chaincode lifecycle Private data Channel capabilities Security Model Identities Membership Service Providers Policies Channel Policies Channel Modification Policies Access Control Lists Chaincode Lifecycle Policy Chaincode Endorsement Policies Peers Ordering service nodes Transport Layer Security (TLS) Hardware Security Modules¶ The cryptographic operations performed by Fabric nodes can be delegated to a Hardware Security Module (HSM). keywords: channel; fabric; information; policies cache: hyperledgerfabric-security_model.html plain text: hyperledgerfabric-security_model.txt item: #1962 of 3327 id: hyperledgerfabric-smartcontract author: hyperledgerfabric title: hyperledgerfabric-smartcontract date: None words: 2822 flesch: 49 summary: Using a blockchain network, we can turn these contracts into executable programs – known in the industry as smart contracts – to open up a wide variety of new possibilities. Think of smart contracts as governing transactions, whereas chaincode governs how smart contracts are packaged for deployment. keywords: chaincode; contract; endorsement; fabric; organizations; transaction cache: hyperledgerfabric-smartcontract.html plain text: hyperledgerfabric-smartcontract.txt item: #1963 of 3327 id: hyperledgerfabric-status author: hyperledgerfabric title: hyperledgerfabric-status date: None words: 126 flesch: 41 summary: Status — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Getting Started - Install Getting Started - Run Fabric Tutorials Deploying a production network Operations Guides Upgrading to the latest release Commands Reference Architecture Reference Frequently Asked Questions Contributions Welcome! keywords: hyperledger cache: hyperledgerfabric-status.html plain text: hyperledgerfabric-status.txt item: #1964 of 3327 id: hyperledgerfabric-style_guide author: hyperledgerfabric title: hyperledgerfabric-style_guide date: None words: 2018 flesch: 73 summary: For an example, check out Using Private Data in Fabric. “Fabric”, “Hyperledger Fabric” or “HLF”? keywords: code; example; fabric; use cache: hyperledgerfabric-style_guide.html plain text: hyperledgerfabric-style_guide.txt item: #1965 of 3327 id: hyperledgerfabric-test_network author: hyperledgerfabric title: hyperledgerfabric-test_network date: None words: 4928 flesch: 44 summary: No channel is created up createChannel - Bring up fabric network with one channel createChannel - Create and join a channel after the network is created deployCC - Deploy a chaincode to a channel (defaults to asset-transfer-basic) down - Bring down the network Flags: peer chaincode invoke -o localhost:7050 keywords: chaincode; channel; command; create; docker; fabric; following; network; peer; test cache: hyperledgerfabric-test_network.html plain text: hyperledgerfabric-test_network.txt item: #1966 of 3327 id: hyperledgerfabric-tutorials author: hyperledgerfabric title: hyperledgerfabric-tutorials date: None words: 461 flesch: 33 summary: Tutorials — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Getting Started - Install Getting Started - Run Fabric Tutorials Using the Fabric test network Deploying a smart contract to a channel Running a Fabric Application Running External Chaincode Builders Using Private Data in Fabric Secured asset transfer in Fabric Using CouchDB Creating a channel Adding an Org to a Channel Updating a channel configuration Writing Your First Chaincode Running chaincode in development mode For an in depth overview of how Fabric applications and smart contracts work together, you can visit the Smart Contracts and Chaincode topic. keywords: fabric cache: hyperledgerfabric-tutorials.html plain text: hyperledgerfabric-tutorials.txt item: #1967 of 3327 id: hyperledgerfabric-txflow author: hyperledgerfabric title: hyperledgerfabric-txflow date: None words: 1001 flesch: 45 summary: Note Applications should listen for the transaction event after submitting a transaction, for example by using the submitTransaction API, which automatically listen for transaction events. Without listening for transaction events, you will not know whether your transaction has actually been ordered, validated, and committed to the ledger. keywords: peer; proposal; transaction cache: hyperledgerfabric-txflow.html plain text: hyperledgerfabric-txflow.txt item: #1968 of 3327 id: hyperledgerfabric-updating_capabilities author: hyperledgerfabric title: hyperledgerfabric-updating_capabilities date: None words: 1736 flesch: 38 summary: For this reason, think of enabling channel capabilities as a point of no return. For a version of this topic that includes information about updating system channel capabilities, check out Updating the capability level of a channel. keywords: capabilities; capability; channel cache: hyperledgerfabric-updating_capabilities.html plain text: hyperledgerfabric-updating_capabilities.txt item: #1969 of 3327 id: hyperledgerfabric-upgrade author: hyperledgerfabric title: hyperledgerfabric-upgrade date: None words: 512 flesch: 46 summary: Status Hyperledger Fabric Docs Upgrading to the latest release View page source Upgrading to the latest release¶ If you’re familiar with previous releases of Hyperledger Fabric, you’re aware that upgrading the nodes and channels to the latest version of Fabric is, at a high level, a four step process. Upgrading to the latest release — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Getting Started - Install Getting Started - Run Fabric Tutorials Deploying a production network Operations Guides Upgrading to the latest release Considerations for getting to v2.x Upgrading your components Updating the capability level of a channel Enabling the new chaincode lifecycle Commands Reference Architecture Reference Frequently Asked Questions Contributions Welcome! keywords: fabric cache: hyperledgerfabric-upgrade.html plain text: hyperledgerfabric-upgrade.txt item: #1970 of 3327 id: hyperledgerfabric-upgrade_to_newest_version author: hyperledgerfabric title: hyperledgerfabric-upgrade_to_newest_version date: None words: 2491 flesch: 47 summary: For more information about the new chaincode lifecycle, check out Fabric chaincode lifecycle concept topic. Application V2_0: enables the new chaincode lifecycle as described in Fabric chaincode lifecycle concept topic. keywords: chaincode; channel; peer; upgrading; v2.x cache: hyperledgerfabric-upgrade_to_newest_version.html plain text: hyperledgerfabric-upgrade_to_newest_version.txt item: #1971 of 3327 id: hyperledgerfabric-upgrading_your_components author: hyperledgerfabric title: hyperledgerfabric-upgrading_your_components date: None words: 2581 flesch: 51 summary: Verify peer upgrade completion¶ It’s a best practice to ensure the upgrade has been completed properly with a chaincode invoke. If you own both ordering nodes and peers, it is a best practice to upgrade the ordering nodes first. keywords: fabric; hyperledger; node; peer; upgrade cache: hyperledgerfabric-upgrading_your_components.html plain text: hyperledgerfabric-upgrading_your_components.txt item: #1972 of 3327 id: hyperledgerfabric-usecases author: hyperledgerfabric title: hyperledgerfabric-usecases date: None words: 150 flesch: 22 summary: What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Introduction Hyperledger Fabric Model How Fabric networks are structured Identity Membership Service Provider (MSP) Policies Peers Ledger The Ordering Service Smart Contracts and Chaincode Fabric chaincode lifecycle Private data Channel capabilities Security Model Use Cases Getting Started - Install Getting Started - Run Fabric Tutorials Deploying a production network Operations Guides Upgrading to the latest release Commands Reference Architecture Reference Frequently Asked Questions Contributions Welcome! Glossary Releases Still Have Questions? Use Cases — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction keywords: fabric cache: hyperledgerfabric-usecases.html plain text: hyperledgerfabric-usecases.txt item: #1973 of 3327 id: hyperledgerfabric-videos author: hyperledgerfabric title: hyperledgerfabric-videos date: None words: 177 flesch: 19 summary: Videos — Hyperledger Fabric Docs main documentation Hyperledger Fabric Docs       Introduction What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Getting Started - Install Getting Started - Run Fabric Tutorials Using the Fabric test network Deploying a smart contract to a channel Running a Fabric Application Running External Chaincode Builders Using Private Data in Fabric Secured asset transfer in Fabric Using CouchDB Creating a channel Adding an Org to a Channel Updating a channel configuration Writing Your First Chaincode Running chaincode in development mode Status Hyperledger Fabric Docs Tutorials Videos View page source Videos¶ Refer to the Hyperledger Fabric channel on YouTube This collection contains developers demonstrating various v1 features and components such as: ledger, channels, gossip, SDK, chaincode, MSP, and more… Next Previous © Copyright Hyperledger 2020-2023. keywords: fabric cache: hyperledgerfabric-videos.html plain text: hyperledgerfabric-videos.txt item: #1974 of 3327 id: hyperledgerfabric-whatis author: hyperledgerfabric title: hyperledgerfabric-whatis date: None words: 2643 flesch: 34 summary: Performance and Scalability¶ Performance of a blockchain platform can be affected by many variables such as transaction size, block size, network size, as well as available hardware resources such as CPU, Memory, Disk Space, Disk and network I/O. Conclusion¶ Any serious evaluation of blockchain platforms should include Hyperledger Fabric in its short list. In order to address the lack of privacy and confidentiality for purposes of delivering on enterprise use case requirements, blockchain platforms have adopted a variety of approaches. keywords: blockchain; consensus; fabric; hyperledger; network; smart; use cache: hyperledgerfabric-whatis.html plain text: hyperledgerfabric-whatis.txt item: #1975 of 3327 id: hyperledgerfabric-whatsnew author: hyperledgerfabric title: hyperledgerfabric-whatsnew date: None words: 3035 flesch: 46 summary: What’s New in Hyperledger Fabric v2.3 Orderer channel management without a system channel Ledger snapshot What’s New in Hyperledger Fabric v2.0, v2.1, v2.2 Decentralized governance for smart contracts New chaincode application patterns for collaboration and consensus Private data enhancements External chaincode launcher State database cache for improved performance on CouchDB Alpine-based docker images Sample test network Upgrading to Fabric v2.x Release notes Key Concepts Getting Started - Install Getting Started - Run Fabric Tutorials Deploying a production network Operations Guides Upgrading to the latest release Commands Reference Architecture Reference Frequently Asked Questions Contributions Welcome! New chaincode application patterns for collaboration and consensus¶ The same decentralized methods of coming to agreement that underpin the new chaincode lifecycle management can also be used in your own chaincode applications to ensure organizations consent to data transactions before they are committed to the ledger. keywords: chaincode; channel; data; fabric; hyperledger; peer; release cache: hyperledgerfabric-whatsnew.html plain text: hyperledgerfabric-whatsnew.txt item: #1976 of 3327 id: hyperledgerfabric-write_first_app author: hyperledgerfabric title: hyperledgerfabric-write_first_app date: None words: 4002 flesch: 38 summary: This tutorial provides an introduction to how Fabric applications interact with deployed blockchain networks. After completing this tutorial you should have a basic understanding of how Fabric applications and smart contracts work together to manage data on the distributed ledger of a blockchain network. keywords: application; asset; err; fabric; gateway; network; sample; transaction cache: hyperledgerfabric-write_first_app.html plain text: hyperledgerfabric-write_first_app.txt item: #1977 of 3327 id: hyperledgeridentus-glossary author: hyperledgeridentus title: hyperledgeridentus-glossary date: None words: 2318 flesch: 43 summary: Credential schema​ A data template for verifiable credentials (VCs). It also enables management of verifiable credentials, and communications. keywords: access; agent; connection; credential; edge; identity; user cache: hyperledgeridentus-glossary.html plain text: hyperledgeridentus-glossary.txt item: #1978 of 3327 id: hyperledgeridentus-identity author: hyperledgeridentus title: hyperledgeridentus-identity date: None words: 312 flesch: 55 summary: Similarly, they are also working on next-generation technologies such as decentralized identity. Identity may be the most essential thing we undervalue in our lives. keywords: identity cache: hyperledgeridentus-identity.html plain text: hyperledgeridentus-identity.txt item: #1979 of 3327 id: hyperledgeridentus-multi-tenancy author: hyperledgeridentus title: hyperledgeridentus-multi-tenancy date: None words: 777 flesch: 33 summary: Sharing it with other entities is possible, but multiple entities cannot own it. Data Isolation: Multi-tenancy ensures that the data, such as DIDs (Decentralized Identifiers), connections, VCs (Verifiable Credentials), keys, and more, of one tenant is completely isolated from others, preserving data privacy and security. keywords: multi; tenancy cache: hyperledgeridentus-multi-tenancy.html plain text: hyperledgeridentus-multi-tenancy.txt item: #1980 of 3327 id: lfhyperledger-2019+Agendas author: lfhyperledger title: lfhyperledger-2019+Agendas date: None words: 315 flesch: 40 summary: More like this 2024 Meeting Agenda and Notes 2024 Meeting Agenda and Notes Healthcare SIG More like this 2022 Meeting Agenda and Notes 2022 Meeting Agenda and Notes Healthcare SIG More like this 2019-10-01 Meeting notes 2019-10-01 Meeting notes BootCamp Russia (archived) PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu cache: lfhyperledger-2019+Agendas.html plain text: lfhyperledger-2019+Agendas.txt item: #1981 of 3327 id: lfhyperledger-2019+Notes author: lfhyperledger title: lfhyperledger-2019+Notes date: None words: 312 flesch: 39 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2019-09-04 Onboarding call 2019-09-17 Contributor call 2019-10-01 Contributor call 2019-10-15 Contributor Call 2019-10-29 Contributor Call 2019-11-12 Contributor Call 2019-11-26 Contributor Call 2019-12-10 Contributor Call 2020 Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Close Besu / 2019 Notes More actions 2019 Notes Sally MacFarlane Owned by Sally MacFarlane Last updated: Sept 14, 2020 , multiple selections available, Related content More info Collapse 2019 Meeting Notes 2019 Meeting Notes Financial Markets SIG More like this Meeting Notes 2020 Meeting Notes 2020 Supply Chain SIG More like this 2019-09-04 Meeting Notes 2019-09-04 Meeting Notes Hyperledger Ursa (EOL) keywords: notes cache: lfhyperledger-2019+Notes.html plain text: lfhyperledger-2019+Notes.txt item: #1982 of 3327 id: lfhyperledger-2019-09-04+Onboarding+call author: lfhyperledger title: lfhyperledger-2019-09-04+Onboarding+call date: None words: 668 flesch: 41 summary: Repo Switch Grace Hartley (Deactivated) We are targeting having our final Pantheon release on our September 10th repo, and we then need the new Besu repo set up prior to the 1.3 Release Candidate scheduled for September 25th. Ry Jones Grace Hartley (Deactivated) David Huseby Owned by Ry Jones Last updated: Sept 11, 2019 by Grace Hartley (Deactivated) keywords: besu; contributor; notes cache: lfhyperledger-2019-09-04+Onboarding+call.html plain text: lfhyperledger-2019-09-04+Onboarding+call.txt item: #1983 of 3327 id: lfhyperledger-2019-09-17+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2019-09-17+Besu+Contributor+Call date: None words: 340 flesch: 22 summary: Atlassian cookies and tracking notice, (opens new window) PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; contributor cache: lfhyperledger-2019-09-17+Besu+Contributor+Call.html plain text: lfhyperledger-2019-09-17+Besu+Contributor+Call.txt item: #1984 of 3327 id: lfhyperledger-2019-09-17+Contributor+call author: lfhyperledger title: lfhyperledger-2019-09-17+Contributor+call date: None words: 627 flesch: 6 summary: Close Besu / 2019-09-17 Contributor call More actions 2019-09-17 Contributor call Danno Ferrin Gregory Markou Owned by Danno Ferrin Last updated: Sept 30, 2019 by Gregory Markou APAC friendly time Recording Minutes Antitrust notice presented General Announcements Devcon (Danno) Releases (Madeline) 1.2.3 is the last one under the pantheon name  1.3-rc1 next week (25/26 Sept), roadmap at the root Off chance that there may be 1.2.4 because of CI/CD issues Work Updates ETC Proposal - Bob Summerwill Background about Ethereum Classic ETCCooperative is joining EEA and HLP ETCCoop is committed to  long term maintenence Greg Markou from Chainsafe will be doing most of the work looks to be straightforward to patch Gas Pricing will be the biggest bump DAO switch existing is nice. Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2019-09-04 Onboarding call 2019-09-17 Contributor call 2019-10-01 Contributor call 2019-10-15 Contributor Call 2019-10-29 Contributor Call 2019-11-12 Contributor Call 2019-11-26 Contributor Call 2019-12-10 Contributor Call 2020 Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; contributor; notes cache: lfhyperledger-2019-09-17+Contributor+call.html plain text: lfhyperledger-2019-09-17+Contributor+call.txt item: #1985 of 3327 id: lfhyperledger-2019-10-01+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2019-10-01+Besu+Contributor+Call date: None words: 484 flesch: 7 summary: PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. Close Besu / 2019-10-01 Besu Contributor Call More actions 2019-10-01 Besu Contributor Call Danno Ferrin Felipe Faraggi Brett Henderson Owned by Danno Ferrin Last updated: Oct 01, 2019 by Felipe Faraggi Times  1500UTC (https://www.timeanddate.com/worldclock/converter.html?iso=20191001T150000&p1=224&p2=179&p3=195&p4=47&p5=1440) 8am Tuesday (1 Oct) Los Angeles 11 am Tuesday (1 Oct) New York 3pm  Tuesday (1 Oct) UTC 5 pm Tuesday (1 Oct) Paris/Berlin 1 am Wednesday (2 Oct) Brisbane Agenda Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements Devcon V 8-11 Oct 2019 - Osaka Japan Hyperledger Kansai 9 Oct Hyperledger Global Forum 2020 Mar 3-6, Phoenix, Arizona, USA Release updates 1.2.4 released with Istanbul block numbers  1.3-RC released 1.3 later this week Work Updates Ethereum Classic Support (Greg Markou)  Istanbul Hard Fork Progress (Danno Ferrin) Other Business LGTM Static Code Analysis Enabled Possibly add longer form presentations? keywords: besu; contributor cache: lfhyperledger-2019-10-01+Besu+Contributor+Call.html plain text: lfhyperledger-2019-10-01+Besu+Contributor+Call.txt item: #1986 of 3327 id: lfhyperledger-2019-10-01+Contributor+call author: lfhyperledger title: lfhyperledger-2019-10-01+Contributor+call date: None words: 534 flesch: 26 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2019-09-04 Onboarding call 2019-09-17 Contributor call 2019-10-01 Contributor call 2019-10-15 Contributor Call 2019-10-29 Contributor Call 2019-11-12 Contributor Call 2019-11-26 Contributor Call 2019-12-10 Contributor Call 2020 Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Close Besu / 2019-10-01 Contributor call More actions 2019-10-01 Contributor call Felipe Faraggi Vipin Bharathan Owned by Felipe Faraggi Last updated: Oct 02, 2019 by Vipin Bharathan EMEA friendly time Recording dummyfile.txt Minutes General Introduction Antitrust Notice General Announcements (Danno) Devcon announcement Consensys sponsored Besu Space HL Event in Osaka HL Forum announcement https://events.linuxfoundation.org/events/hyperledger-global-forum-2020/ Release updates (Danno) keywords: besu; contributor; notes cache: lfhyperledger-2019-10-01+Contributor+call.html plain text: lfhyperledger-2019-10-01+Contributor+call.txt item: #1987 of 3327 id: lfhyperledger-2019-10-15+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2019-10-15+Besu+Contributor+Call date: None words: 357 flesch: 15 summary: Close Besu / 2019-10-15 Besu Contributor Call More actions 2019-10-15 Besu Contributor Call Danno Ferrin Brett Henderson Felipe Faraggi Owned by Danno Ferrin Last updated: Oct 14, 2019 by Brett Henderson Link to meeting: https://consensys.zoom.us/j/199741148 Times  6pm Monday (14 Oct) Los Angeles 9pm Monday (14 Oct) New York 1am Tuesday (15 Oct) UTC 3am Tuesday (15 Oct) Paris/Berlin 11am Tuesday (15 Oct) Brisbane Agenda Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements Hyperledger Global Forum 2020 Mar 3-6, Phoenix, Arizona, USA Release updates 1.3 released 1.3.1 this week Work Updates Ethereum Classic Support (Greg) Other Business New Maintainer Proposal - Ivaylo (Voting closes 18 Oct, Lucas)  Active Status (Grace?)  Discussion on Ethereum Foundation Grid integration (Felipe?  Danno?) Open Forum Future Topics Request for presentation topics , multiple selections available, {serverDuration: 14, requestCorrelationId: ba02aa4c216f44788247349f23d46865} PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; contributor cache: lfhyperledger-2019-10-15+Besu+Contributor+Call.html plain text: lfhyperledger-2019-10-15+Besu+Contributor+Call.txt item: #1988 of 3327 id: lfhyperledger-2019-10-15+Contributor+Call author: lfhyperledger title: lfhyperledger-2019-10-15+Contributor+Call date: None words: 509 flesch: 49 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2019-09-04 Onboarding call 2019-09-17 Contributor call 2019-10-01 Contributor call 2019-10-15 Contributor Call 2019-10-29 Contributor Call 2019-11-12 Contributor Call 2019-11-26 Contributor Call 2019-12-10 Contributor Call 2020 Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Discussion on Ethereum Foundation Grid integration (Felipe) github.com/ethereum/grid desktop software with one click interfae to choose client and download and install it. keywords: contributor; notes cache: lfhyperledger-2019-10-15+Contributor+Call.html plain text: lfhyperledger-2019-10-15+Contributor+Call.txt item: #1989 of 3327 id: lfhyperledger-2019-10-29+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2019-10-29+Besu+Contributor+Call date: None words: 330 flesch: 16 summary: PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. Atlassian cookies and tracking notice, (opens new window) keywords: besu; contributor cache: lfhyperledger-2019-10-29+Besu+Contributor+Call.html plain text: lfhyperledger-2019-10-29+Besu+Contributor+Call.txt item: #1990 of 3327 id: lfhyperledger-2019-10-29+Contributor+Call author: lfhyperledger title: lfhyperledger-2019-10-29+Contributor+Call date: None words: 560 flesch: 28 summary: Close Besu / 2019-10-29 Contributor Call More actions 2019-10-29 Contributor Call Danno Ferrin Owned by Danno Ferrin Last updated: Nov 01, 2019 Recording of Call 1.4 release planning discussed release cadence AR - Danno add wiki page for this Discussed breaking changes in release not in CD releases, do breaks at quarterly releases Example: Disallowing comments in genesis.json Example: dropping support for Java 8 1.4 aimed release for end of Feb, 26/27 RC 12/13 Feb Call from community about desired features PegaSys contributions End to End TLS between external programs JSON-RPC for EthSigner ? Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2019-09-04 Onboarding call 2019-09-17 Contributor call 2019-10-01 Contributor call 2019-10-15 Contributor Call 2019-10-29 Contributor Call 2019-11-12 Contributor Call 2019-11-26 Contributor Call 2019-12-10 Contributor Call 2020 Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; contributor; notes cache: lfhyperledger-2019-10-29+Contributor+Call.html plain text: lfhyperledger-2019-10-29+Contributor+Call.txt item: #1991 of 3327 id: lfhyperledger-2019-11-12+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2019-11-12+Besu+Contributor+Call date: None words: 396 flesch: 28 summary: PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. Close Besu / 2019-11-12 Besu Contributor Call More actions 2019-11-12 Besu Contributor Call Danno Ferrin Arash Mahboubi (Deactivated) Owned by Danno Ferrin Last updated: Nov 12, 2019 Recording of Meeting: dummyfile.txt Times  5pm Monday (11 Nov) Los Angeles 8pm Monday (11 Nov) New York 1am Tuesday (12 Nov) UTC 2am Tuesday (12 Nov) Paris/Berlin 11am Tuesday (12 Nov) Brisbane Agenda Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements Eth Waterloo was this past weekend, 8-10 Nov Eth Denver is 15-17 Feb 2020 in Denver Colorado EthCC (Ethereum Community Conference) is 3-5 March 2020 in Paris France Hyperledger Global Forum is 3-6 March 2020 in Phoenix AZ Release updates 1.3.4 released last week 1.3.3 had a bug with older V1 databases. keywords: besu; contributor cache: lfhyperledger-2019-11-12+Besu+Contributor+Call.html plain text: lfhyperledger-2019-11-12+Besu+Contributor+Call.txt item: #1992 of 3327 id: lfhyperledger-2019-11-12+Contributor+Call author: lfhyperledger title: lfhyperledger-2019-11-12+Contributor+Call date: None words: 445 flesch: 30 summary: , multiple selections available,meeting-notes Related content More info Collapse 2019-10-15 Contributor Call 2019-10-15 Contributor Call Besu More like this 2019-10-01 Contributor call 2019-10-01 Contributor call Besu More like this 2019-10-29 Contributor Call 2019-10-29 Contributor Call Besu More like this 2020-01-21 Contributor Call 2020-01-21 Contributor Call Besu More like this 2022-04-12 Contributor Call 2022-04-12 Contributor Call Besu More like this 2022-03-15 Contributor Call 2022-03-15 Contributor Call Besu More like this {serverDuration: 35, requestCorrelationId: e690f8871edb4b77bcf370d03339b881} Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2019-09-04 Onboarding call 2019-09-17 Contributor call 2019-10-01 Contributor call 2019-10-15 Contributor Call 2019-10-29 Contributor Call 2019-11-12 Contributor Call 2019-11-26 Contributor Call 2019-12-10 Contributor Call 2020 Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; contributor cache: lfhyperledger-2019-11-12+Contributor+Call.html plain text: lfhyperledger-2019-11-12+Contributor+Call.txt item: #1993 of 3327 id: lfhyperledger-2019-11-26+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2019-11-26+Besu+Contributor+Call date: None words: 437 flesch: 20 summary: PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. Close Besu / 2019-11-26 Besu Contributor Call More actions 2019-11-26 Besu Contributor Call Danno Ferrin Felipe Faraggi Madeline Murray (Deactivated) Owned by Danno Ferrin Last updated: Nov 26, 2019 by Felipe Faraggi Meeting Link: https://consensys.zoom.us/j/725448960 EMEA/AMER Friendly Time -  1500UTC (https://www.timeanddate.com/worldclock/converter.html?iso=20191126T150000&p1=224&p2=179&p3=195&p4=47&p5=1440) 7am Tuesday (26 Nov) Los Angeles 10 am Tuesday (26 Nov) New York 3pm  Tuesday (26 Nov) UTC 4 pm Tuesday (26 Nov) Paris/Berlin 1 am Wednesday (27 Nov) Brisbane Agenda Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements Eth Denver is 15-17 Feb 2020 in Denver Colorado EthCC (Ethereum Community Conference) is 3-5 March 2020 in Paris France Hyperledger Global Forum is 3-6 March 2020 in Phoenix AZ Release updates 1.3.5 released last week 1.3.6 or 1.3.7 will have a critical difficulty bomb update 1.4 aimed for RC on 13 Feb 2020, full release on 27 Feb 2020 Work Updates Ethereum Classic Support Proposed Changes to Changelog  Caliper support Other Business Meeting Times. keywords: besu; contributor cache: lfhyperledger-2019-11-26+Besu+Contributor+Call.html plain text: lfhyperledger-2019-11-26+Besu+Contributor+Call.txt item: #1994 of 3327 id: lfhyperledger-2019-11-26+Contributor+Call author: lfhyperledger title: lfhyperledger-2019-11-26+Contributor+Call date: None words: 396 flesch: 37 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2019-09-04 Onboarding call 2019-09-17 Contributor call 2019-10-01 Contributor call 2019-10-15 Contributor Call 2019-10-29 Contributor Call 2019-11-12 Contributor Call 2019-11-26 Contributor Call 2019-12-10 Contributor Call 2020 Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 3 times make it more logistically difficult 7 Jan call will be EMEA/AMER time CI/CD Jenkins fully dropped, 100% CircleCI now CDO instructions article posted. keywords: contributor; notes cache: lfhyperledger-2019-11-26+Contributor+Call.html plain text: lfhyperledger-2019-11-26+Contributor+Call.txt item: #1995 of 3327 id: lfhyperledger-2019-12-10+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2019-12-10+Besu+Contributor+Call date: None words: 484 flesch: 1 summary: Close Besu / 2019-12-10 Besu Contributor Call More actions 2019-12-10 Besu Contributor Call Danno Ferrin Felipe Faraggi Edward Evans Madeline Murray (Deactivated) Owned by Danno Ferrin Last updated: Jan 07, 2020 by Felipe Faraggi Meeting Link: https://consensys.zoom.us/j/199741148 APAC/AMER Friendly Time -  0100UTC (https://www.timeanddate.com/worldclock/converter.html?iso=20191210T010000&p1=224&p2=179&p3=195&p4=47&p5=1440) 5pm Monday (9 Dec) Los Angeles 8pm Monday (9 Dec) New York 1 am  Tuesday (10 Dec) UTC 2 am Tuesday (10 Dec) Paris/Berlin 11 am Tuesday (10 Dec) Brisbane Agenda Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements Eth Denver is 15-17 Feb 2020 in Denver Colorado EthCC (Ethereum Community Conference) is 3-5 March 2020 in Paris France Hyperledger Global Forum is 3-6 March 2020 in Phoenix AZ Release updates 1.3.6 - released  Proposal to lengthen RC/Beta window for 1.4 1.4 Work Updates Proposed Changes to Changelog RPC Endpoint Service for Plugins (Danno) Other Business New Maintainer proposal: Edward Mack  CI/CD  Open Forum Future Topics , multiple selections available, Related content More info Collapse 2019-10-15 Besu Contributor Call 2019-10-15 Besu Contributor Call Besu More like this 2019-10-01 Besu Contributor Call 2019-10-01 Besu Contributor Call Besu More like this 2019-11-26 Besu Contributor Call 2019-11-26 Besu Contributor Call Besu More like this 2020-09-29 Besu Contributor Call 2020-09-29 Besu Contributor Call Besu More like this 2020-02-18 Besu Contributor Call 2020-02-18 Besu Contributor Call Besu More like this 2020-01-07 Besu Contributor Call 2020-01-07 Besu Contributor Call Besu More like this {serverDuration: 12, requestCorrelationId: 5ae4aa1093d3443fbbfe8cd49ca56dd1} PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; contributor cache: lfhyperledger-2019-12-10+Besu+Contributor+Call.html plain text: lfhyperledger-2019-12-10+Besu+Contributor+Call.txt item: #1996 of 3327 id: lfhyperledger-2019-12-10+Contributor+Call author: lfhyperledger title: lfhyperledger-2019-12-10+Contributor+Call date: None words: 516 flesch: 50 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2019-09-04 Onboarding call 2019-09-17 Contributor call 2019-10-01 Contributor call 2019-10-15 Contributor Call 2019-10-29 Contributor Call 2019-11-12 Contributor Call 2019-11-26 Contributor Call 2019-12-10 Contributor Call 2020 Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Beta 2 if needed on 29 Jan 1.4-RC on 13 Feb 2020 1.40 targeted at 27 Feb 2020 Build version becomes 1.4.0-beta-SNAPSHOT right after 1.3.7 release Work Updates Change Log Only include PRs that have useful changes rather than a line for each PR Either Add a CHANGELOG section to each PR Use a wiki page. keywords: contributor; notes cache: lfhyperledger-2019-12-10+Contributor+Call.html plain text: lfhyperledger-2019-12-10+Contributor+Call.txt item: #1997 of 3327 id: lfhyperledger-2020+Agendas author: lfhyperledger title: lfhyperledger-2020+Agendas date: None words: 302 flesch: 17 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020 Agendas - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: contributor cache: lfhyperledger-2020+Agendas.html plain text: lfhyperledger-2020+Agendas.txt item: #1998 of 3327 id: lfhyperledger-2020+Notes author: lfhyperledger title: lfhyperledger-2020+Notes date: None words: 385 flesch: 13 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020 Notes - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: notes cache: lfhyperledger-2020+Notes.html plain text: lfhyperledger-2020+Notes.txt item: #1999 of 3327 id: lfhyperledger-2020-01-07+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2020-01-07+Besu+Contributor+Call date: None words: 484 flesch: 6 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-01-07 Besu Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; contributor cache: lfhyperledger-2020-01-07+Besu+Contributor+Call.html plain text: lfhyperledger-2020-01-07+Besu+Contributor+Call.txt item: #2000 of 3327 id: lfhyperledger-2020-01-07+Contributor+Call author: lfhyperledger title: lfhyperledger-2020-01-07+Contributor+Call date: None words: 458 flesch: 3 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-01-07 Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: contributor; notes cache: lfhyperledger-2020-01-07+Contributor+Call.html plain text: lfhyperledger-2020-01-07+Contributor+Call.txt item: #2001 of 3327 id: lfhyperledger-2020-01-21+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2020-01-21+Besu+Contributor+Call date: None words: 464 flesch: 16 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-01-21 Besu Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; contributor cache: lfhyperledger-2020-01-21+Besu+Contributor+Call.html plain text: lfhyperledger-2020-01-21+Besu+Contributor+Call.txt item: #2002 of 3327 id: lfhyperledger-2020-01-21+Contributor+Call author: lfhyperledger title: lfhyperledger-2020-01-21+Contributor+Call date: None words: 601 flesch: 8 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-01-21 Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: contributor; notes cache: lfhyperledger-2020-01-21+Contributor+Call.html plain text: lfhyperledger-2020-01-21+Contributor+Call.txt item: #2003 of 3327 id: lfhyperledger-2020-02-04+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2020-02-04+Besu+Contributor+Call date: None words: 485 flesch: 17 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-02-04 Besu Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; contributor cache: lfhyperledger-2020-02-04+Besu+Contributor+Call.html plain text: lfhyperledger-2020-02-04+Besu+Contributor+Call.txt item: #2004 of 3327 id: lfhyperledger-2020-02-04+Besu+Contributor+Call+Notes author: lfhyperledger title: lfhyperledger-2020-02-04+Besu+Contributor+Call+Notes date: None words: 414 flesch: 10 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-02-04 Besu Contributor Call Notes - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: contributor; notes cache: lfhyperledger-2020-02-04+Besu+Contributor+Call+Notes.html plain text: lfhyperledger-2020-02-04+Besu+Contributor+Call+Notes.txt item: #2005 of 3327 id: lfhyperledger-2020-02-18+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2020-02-18+Besu+Contributor+Call date: None words: 463 flesch: -2 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-02-18 Besu Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; contributor cache: lfhyperledger-2020-02-18+Besu+Contributor+Call.html plain text: lfhyperledger-2020-02-18+Besu+Contributor+Call.txt item: #2006 of 3327 id: lfhyperledger-2020-02-18+Besu+Contributor+Call+Notes author: lfhyperledger title: lfhyperledger-2020-02-18+Besu+Contributor+Call+Notes date: None words: 506 flesch: 0 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-02-18 Besu Contributor Call Notes - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: contributor; notes cache: lfhyperledger-2020-02-18+Besu+Contributor+Call+Notes.html plain text: lfhyperledger-2020-02-18+Besu+Contributor+Call+Notes.txt item: #2007 of 3327 id: lfhyperledger-2020-03-17+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2020-03-17+Besu+Contributor+Call date: None words: 445 flesch: 9 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-03-17 Besu Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; contributor cache: lfhyperledger-2020-03-17+Besu+Contributor+Call.html plain text: lfhyperledger-2020-03-17+Besu+Contributor+Call.txt item: #2008 of 3327 id: lfhyperledger-2020-03-17+Contributor+Call+Notes author: lfhyperledger title: lfhyperledger-2020-03-17+Contributor+Call+Notes date: None words: 533 flesch: 5 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-03-17 Contributor Call Notes - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; contributor; notes cache: lfhyperledger-2020-03-17+Contributor+Call+Notes.html plain text: lfhyperledger-2020-03-17+Contributor+Call+Notes.txt item: #2009 of 3327 id: lfhyperledger-2020-03-31+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2020-03-31+Besu+Contributor+Call date: None words: 425 flesch: 10 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-03-31 Besu Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; contributor cache: lfhyperledger-2020-03-31+Besu+Contributor+Call.html plain text: lfhyperledger-2020-03-31+Besu+Contributor+Call.txt item: #2010 of 3327 id: lfhyperledger-2020-04-14+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2020-04-14+Besu+Contributor+Call date: None words: 569 flesch: 24 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Hyperledger Barcelona hosts Hyperledger Besu: Hyperledger Ethereum & Ethereum Stack Hyperledger Argentina (Spanish): Wednesday, April 15 at 22:00 UTC / 19:00 ART: keywords: besu; contributor; hyperledger cache: lfhyperledger-2020-04-14+Besu+Contributor+Call.html plain text: lfhyperledger-2020-04-14+Besu+Contributor+Call.txt item: #2011 of 3327 id: lfhyperledger-2020-04-14+Contributor+Call author: lfhyperledger title: lfhyperledger-2020-04-14+Contributor+Call date: None words: 463 flesch: 32 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-04-14 Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: contributor; notes cache: lfhyperledger-2020-04-14+Contributor+Call.html plain text: lfhyperledger-2020-04-14+Contributor+Call.txt item: #2012 of 3327 id: lfhyperledger-2020-04-28+Contributor+Call+Notes author: lfhyperledger title: lfhyperledger-2020-04-28+Contributor+Call+Notes date: None words: 380 flesch: 13 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-04-28 Contributor Call Notes - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: contributor; notes cache: lfhyperledger-2020-04-28+Contributor+Call+Notes.html plain text: lfhyperledger-2020-04-28+Contributor+Call+Notes.txt item: #2013 of 3327 id: lfhyperledger-2020-04-28+Contributor+call author: lfhyperledger title: lfhyperledger-2020-04-28+Contributor+call date: None words: 516 flesch: 9 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Past Meetups (Virtual Hyperledger Meetups): Hyperledger Barcelona: Thursday, April 16 at 18:00 pm UTC / 20:00 CEST: Hyperledger Barcelona hosts Hyperledger Besu: Hyperledger Ethereum & Ethereum Stack Hyperledger Argentina (Spanish): Wednesday, April 15 at 22:00 UTC / 19:00 ART: Hyperledger Argentina hosts meetup in Spanish with speakers from Hyperledger, LACChain and PegaSys Blockchain Academy Chile: Wednesday, April 22, 2020 at 6:30 PM to 7:30 PM GMT-4: Hyperledger Besu: Ethereum para redes permisionadas (Spanish) Release updates 1.4.4 cut 1.4.3 has Eth/65 issues Work Updates ETC Phoenix Hard Fork ETH Berlin Hard Fork Other Business Feature Flag Discussion (Danno) proposal: Feature Flags Release RC and testing Discussion (Edward Evans, proposal at Proposal: Create a Release Candidate for every release Open Forum Future Topics , multiple selections available, {serverDuration: 12, requestCorrelationId: 79e87e382a924fdd9e37fa802b4925ea} keywords: besu; contributor cache: lfhyperledger-2020-04-28+Contributor+call.html plain text: lfhyperledger-2020-04-28+Contributor+call.txt item: #2014 of 3327 id: lfhyperledger-2020-05-12+Contributor+Call author: lfhyperledger title: lfhyperledger-2020-05-12+Contributor+Call date: None words: 479 flesch: 32 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-05-12 Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; contributor cache: lfhyperledger-2020-05-12+Contributor+Call.html plain text: lfhyperledger-2020-05-12+Contributor+Call.txt item: #2015 of 3327 id: lfhyperledger-2020-05-12+Contributor+Call+Notes author: lfhyperledger title: lfhyperledger-2020-05-12+Contributor+Call+Notes date: None words: 587 flesch: 33 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-05-12 Contributor Call Notes - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: contributor; notes cache: lfhyperledger-2020-05-12+Contributor+Call+Notes.html plain text: lfhyperledger-2020-05-12+Contributor+Call+Notes.txt item: #2016 of 3327 id: lfhyperledger-2020-05-26+Contributor+Call author: lfhyperledger title: lfhyperledger-2020-05-26+Contributor+Call date: None words: 434 flesch: 24 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-05-26 Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; contributor cache: lfhyperledger-2020-05-26+Contributor+Call.html plain text: lfhyperledger-2020-05-26+Contributor+Call.txt item: #2017 of 3327 id: lfhyperledger-2020-05-26+Contributor+Call+Notes author: lfhyperledger title: lfhyperledger-2020-05-26+Contributor+Call+Notes date: None words: 414 flesch: 17 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-05-26 Contributor Call Notes - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: contributor; notes cache: lfhyperledger-2020-05-26+Contributor+Call+Notes.html plain text: lfhyperledger-2020-05-26+Contributor+Call+Notes.txt item: #2018 of 3327 id: lfhyperledger-2020-06-09+Besu+Contributor+Call+Agenda author: lfhyperledger title: lfhyperledger-2020-06-09+Besu+Contributor+Call+Agenda date: None words: 528 flesch: 34 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Close Besu / 2020-06-09 Besu Contributor Call Agenda More actions 2020-06-09 Besu Contributor Call Agenda Danno Ferrin Tim Beiko Owned by Danno Ferrin Last updated: keywords: besu; contributor cache: lfhyperledger-2020-06-09+Besu+Contributor+Call+Agenda.html plain text: lfhyperledger-2020-06-09+Besu+Contributor+Call+Agenda.txt item: #2019 of 3327 id: lfhyperledger-2020-06-09+Contributor+Call+Notes author: lfhyperledger title: lfhyperledger-2020-06-09+Contributor+Call+Notes date: None words: 443 flesch: 22 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-06-09 Contributor Call Notes - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: contributor; notes cache: lfhyperledger-2020-06-09+Contributor+Call+Notes.html plain text: lfhyperledger-2020-06-09+Contributor+Call+Notes.txt item: #2020 of 3327 id: lfhyperledger-2020-06-23+Besu+Contributor+Call+Agenda author: lfhyperledger title: lfhyperledger-2020-06-23+Besu+Contributor+Call+Agenda date: None words: 453 flesch: 31 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Close Besu / 2020-06-23 Besu Contributor Call Agenda More actions 2020-06-23 Besu Contributor Call Agenda Sally MacFarlane Owned by Sally MacFarlane Last updated: keywords: besu; contributor cache: lfhyperledger-2020-06-23+Besu+Contributor+Call+Agenda.html plain text: lfhyperledger-2020-06-23+Besu+Contributor+Call+Agenda.txt item: #2021 of 3327 id: lfhyperledger-2020-06-23+Contributor+Call+Notes author: lfhyperledger title: lfhyperledger-2020-06-23+Contributor+Call+Notes date: None words: 483 flesch: 12 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-06-23 Contributor Call Notes - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: contributor; notes cache: lfhyperledger-2020-06-23+Contributor+Call+Notes.html plain text: lfhyperledger-2020-06-23+Contributor+Call+Notes.txt item: #2022 of 3327 id: lfhyperledger-2020-07-07+Contributor+Call author: lfhyperledger title: lfhyperledger-2020-07-07+Contributor+Call date: None words: 455 flesch: 20 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-07-07 Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; contributor cache: lfhyperledger-2020-07-07+Contributor+Call.html plain text: lfhyperledger-2020-07-07+Contributor+Call.txt item: #2023 of 3327 id: lfhyperledger-2020-07-07+Contributor+Call+Notes author: lfhyperledger title: lfhyperledger-2020-07-07+Contributor+Call+Notes date: None words: 428 flesch: 0 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-07-07 Contributor Call Notes - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: contributor cache: lfhyperledger-2020-07-07+Contributor+Call+Notes.html plain text: lfhyperledger-2020-07-07+Contributor+Call+Notes.txt item: #2024 of 3327 id: lfhyperledger-2020-07-21+Contributor+Call+Agenda author: lfhyperledger title: lfhyperledger-2020-07-21+Contributor+Call+Agenda date: None words: 461 flesch: 23 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Close Besu / 2020-07-21 Contributor Call Agenda More actions 2020-07-21 Contributor Call Agenda Danno Ferrin Sally MacFarlane Owned by Danno Ferrin Last updated: Jul 20, 2020 Contributor Calls (Meeting Link: https://consensys.zoom.us/j/524697595) APAC/AMER Friendly Time -  0100UTC (https://www.timeanddate.com/worldclock/converter.html?iso=20200721T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 6 pm Monday (20 July) keywords: besu; contributor cache: lfhyperledger-2020-07-21+Contributor+Call+Agenda.html plain text: lfhyperledger-2020-07-21+Contributor+Call+Agenda.txt item: #2025 of 3327 id: lfhyperledger-2020-07-21+Contributor+Call+Notes author: lfhyperledger title: lfhyperledger-2020-07-21+Contributor+Call+Notes date: None words: 313 flesch: 25 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-07-21 Contributor Call Notes - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: contributor cache: lfhyperledger-2020-07-21+Contributor+Call+Notes.html plain text: lfhyperledger-2020-07-21+Contributor+Call+Notes.txt item: #2026 of 3327 id: lfhyperledger-2020-08-04+Contributor+Call+Agenda author: lfhyperledger title: lfhyperledger-2020-08-04+Contributor+Call+Agenda date: None words: 457 flesch: 27 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Close Besu / 2020-08-04 Contributor Call Agenda More actions 2020-08-04 Contributor Call Agenda Tim Beiko Danno Ferrin Owned by Tim Beiko Last updated: keywords: besu; contributor cache: lfhyperledger-2020-08-04+Contributor+Call+Agenda.html plain text: lfhyperledger-2020-08-04+Contributor+Call+Agenda.txt item: #2027 of 3327 id: lfhyperledger-2020-08-04+Contributor+Call+Nodes author: lfhyperledger title: lfhyperledger-2020-08-04+Contributor+Call+Nodes date: None words: 414 flesch: 11 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Ry Jones Owned by Danno Ferrin Last updated: Aug 08, 2020 by Ry Jones Recording: https://consensys.zoom.us/rec/share/zvB7Jr2pp11LT5H37VHRYoUhM7zEX6a81CAf-qEKnxpSoR9TiS6mNDNckNC4a6Ja?startTime=1596553522000 Password W=!b8&8c  , multiple selections available,meeting-notes Related content More info Collapse 2019-10-15 Contributor Call 2019-10-15 Contributor Call Besu More like this 2020-08-18 Contributor Call Agenda 2020-08-18 Contributor Call Agenda Besu More like this 2022-04-12 Contributor Call 2022-04-12 Contributor Call Besu More like this 2020-03-17 Contributor Call Notes 2020-03-17 Contributor Call Notes Besu More like this 2022-06-07 Contributor Call 2022-06-07 Contributor Call Besu More like this 2021-04-13 Besu Contributor Call 2021-04-13 Besu Contributor Call Besu More like this {serverDuration: 12, requestCorrelationId: 2f80b0840edc4bdf8917fe06bd5c1cc0} keywords: contributor cache: lfhyperledger-2020-08-04+Contributor+Call+Nodes.html plain text: lfhyperledger-2020-08-04+Contributor+Call+Nodes.txt item: #2028 of 3327 id: lfhyperledger-2020-08-18+Besu+Contrubutor+Call+Notes author: lfhyperledger title: lfhyperledger-2020-08-18+Besu+Contrubutor+Call+Notes date: None words: 317 flesch: 13 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-08-18 Besu Contrubutor Call Notes - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: notes cache: lfhyperledger-2020-08-18+Besu+Contrubutor+Call+Notes.html plain text: lfhyperledger-2020-08-18+Besu+Contrubutor+Call+Notes.txt item: #2029 of 3327 id: lfhyperledger-2020-08-18+Contributor+Call+Agenda author: lfhyperledger title: lfhyperledger-2020-08-18+Contributor+Call+Agenda date: None words: 461 flesch: 25 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Close Besu / 2020-08-18 Contributor Call Agenda More actions 2020-08-18 Contributor Call Agenda Danno Ferrin Owned by Danno Ferrin Last updated: Aug 17, 2020 (Meeting Link: https://consensys.zoom.us/j/524697595) APAC/AMER Friendly Time -  0100UTC (https://www.timeanddate.com/worldclock/converter.html?iso=20200818T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 6 pm Monday (17 Aug) keywords: besu; contributor cache: lfhyperledger-2020-08-18+Contributor+Call+Agenda.html plain text: lfhyperledger-2020-08-18+Contributor+Call+Agenda.txt item: #2030 of 3327 id: lfhyperledger-2020-09-01+Besu+Contributor+Call+Notes author: lfhyperledger title: lfhyperledger-2020-09-01+Besu+Contributor+Call+Notes date: None words: 408 flesch: 13 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-09-01 Besu Contributor Call Notes - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: contributor; notes cache: lfhyperledger-2020-09-01+Besu+Contributor+Call+Notes.html plain text: lfhyperledger-2020-09-01+Besu+Contributor+Call+Notes.txt item: #2031 of 3327 id: lfhyperledger-2020-09-01+Contributor+Call author: lfhyperledger title: lfhyperledger-2020-09-01+Contributor+Call date: None words: 398 flesch: 8 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-09-01 Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; contributor cache: lfhyperledger-2020-09-01+Contributor+Call.html plain text: lfhyperledger-2020-09-01+Contributor+Call.txt item: #2032 of 3327 id: lfhyperledger-2020-09-15+Contributor+Call author: lfhyperledger title: lfhyperledger-2020-09-15+Contributor+Call date: None words: 539 flesch: 3 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. New York 1 am  Tuesday (15 Sep) UTC 3 am Tuesday (15 Sep) Paris/Berlin 11 am Tuesday (15 Sep) Brisbane Agenda Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements TSC Elections Hyperledger Member Summit was Last Week (Danno) Release Process 1.5.4 Released 10 Aug About 2 more 1.5.x releases before the 1.6 release cycle Work Updates Other Business Proposal - Besu maintainers become docs maintainers Open Forum Privacy and Rehydration (Stefan) Future Topics , multiple selections available, Related content More info Collapse 2020-05-26 Contributor Call 2020-05-26 Contributor Call Besu More like this 2020-08-18 Contributor Call Agenda 2020-08-18 Contributor Call Agenda Besu More like this 2023-06-06 Contributor Call 2023-06-06 Contributor Call Besu More like this 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time Besu More like this 2024-04-16 Contributor Call - US/EMEA Friendly Time 2024-04-16 Contributor Call - US/EMEA Friendly Time Besu More like this 2020-02-18 Besu Contributor Call 2020-02-18 Besu Contributor Call Besu More like this {serverDuration: 12, requestCorrelationId: 80f7f1e3d5684b48887efd76294bbf8d} keywords: besu; contributor cache: lfhyperledger-2020-09-15+Contributor+Call.html plain text: lfhyperledger-2020-09-15+Contributor+Call.txt item: #2033 of 3327 id: lfhyperledger-2020-09-15+Contributor+Call+Notes author: lfhyperledger title: lfhyperledger-2020-09-15+Contributor+Call+Notes date: None words: 338 flesch: 28 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-09-15 Contributor Call Notes - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: contributor cache: lfhyperledger-2020-09-15+Contributor+Call+Notes.html plain text: lfhyperledger-2020-09-15+Contributor+Call+Notes.txt item: #2034 of 3327 id: lfhyperledger-2020-09-29+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2020-09-29+Besu+Contributor+Call date: None words: 473 flesch: 13 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-09-29 Besu Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; contributor cache: lfhyperledger-2020-09-29+Besu+Contributor+Call.html plain text: lfhyperledger-2020-09-29+Besu+Contributor+Call.txt item: #2035 of 3327 id: lfhyperledger-2020-09-29+Besu+Contributor+Call+Notes author: lfhyperledger title: lfhyperledger-2020-09-29+Besu+Contributor+Call+Notes date: None words: 342 flesch: 15 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-09-29 Besu Contributor Call Notes - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: contributor cache: lfhyperledger-2020-09-29+Besu+Contributor+Call+Notes.html plain text: lfhyperledger-2020-09-29+Besu+Contributor+Call+Notes.txt item: #2036 of 3327 id: lfhyperledger-2020-10-13+Hyperledger+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2020-10-13+Hyperledger+Besu+Contributor+Call date: None words: 444 flesch: 15 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-10-13 Hyperledger Besu Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; contributor cache: lfhyperledger-2020-10-13+Hyperledger+Besu+Contributor+Call.html plain text: lfhyperledger-2020-10-13+Hyperledger+Besu+Contributor+Call.txt item: #2037 of 3327 id: lfhyperledger-2020-10-27+Office+Hours author: lfhyperledger title: lfhyperledger-2020-10-27+Office+Hours date: None words: 435 flesch: 19 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-10-27 Office Hours - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; contributor cache: lfhyperledger-2020-10-27+Office+Hours.html plain text: lfhyperledger-2020-10-27+Office+Hours.txt item: #2038 of 3327 id: lfhyperledger-2020-10-27+Office+Hours+Notes author: lfhyperledger title: lfhyperledger-2020-10-27+Office+Hours+Notes date: None words: 468 flesch: 17 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas Notes 2019 Notes 2020 Notes 2020-01-07 Contributor Call 2020-01-21 Contributor Call 2020-02-04 Besu Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-03-17 Contributor Call Notes 2020-04-14 Contributor Call 2020-04-28 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-07-21 Contributor Call Notes 2020-08-04 Contributor Call Nodes 2020-08-18 Besu Contrubutor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-29 Besu Contributor Call Notes 2020-10-27 Office Hours Notes 2021-01-19 Office Hours Notes 2022-1-31 Contributor Call notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-10-27 Office Hours Notes - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: contributor; notes cache: lfhyperledger-2020-10-27+Office+Hours+Notes.html plain text: lfhyperledger-2020-10-27+Office+Hours+Notes.txt item: #2039 of 3327 id: lfhyperledger-2020-11-24+Office+Hours author: lfhyperledger title: lfhyperledger-2020-11-24+Office+Hours date: None words: 451 flesch: 0 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2020-01-07 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-04-14 Besu Contributor Call 2020-04-28 Contributor call 2020-05-12 Contributor Call 2020-05-26 Contributor Call 2020-06-09 Besu Contributor Call Agenda 2020-06-23 Besu Contributor Call Agenda 2020-07-07 Contributor Call 2020-07-21 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-08-18 Contributor Call Agenda 2020-09-01 Contributor Call 2020-09-15 Contributor Call 2020-09-29 Besu Contributor Call 2020-10-13 Hyperledger Besu Contributor Call 2020-10-27 Office Hours 2020-11-24 Office Hours 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2020-11-24 Office Hours - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; contributor cache: lfhyperledger-2020-11-24+Office+Hours.html plain text: lfhyperledger-2020-11-24+Office+Hours.txt item: #2040 of 3327 id: lfhyperledger-2021+Agendas author: lfhyperledger title: lfhyperledger-2021+Agendas date: None words: 582 flesch: -3 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning Show more below You‘re viewing this with anonymous access, so some content might be blocked. Ry Jones Owned by Matthew Wright (Deactivated) Last updated: Dec 17, 2021 by Ry Jones 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) , multiple selections available, Related content More info Collapse 2024 Meeting Agenda and Notes 2024 Meeting Agenda and Notes Healthcare SIG More like this 2025-02-19 Meeting notes 2025-02-19 Meeting notes Web3j More like this 2025-02-05 Meeting notes 2025-02-05 Meeting notes Web3j More like this 2024-10-30 Meeting notes 2024-10-30 Meeting notes Web3j More like this 2020-04-22 2020-04-22 Financial Markets SIG More like this 2024-11-13 Meeting notes 2024-11-13 Meeting notes Web3j More like this {serverDuration: 13, requestCorrelationId: d455237f3ee2414487dbf433c5bddbc6} keywords: besu contributor cache: lfhyperledger-2021+Agendas.html plain text: lfhyperledger-2021+Agendas.txt item: #2041 of 3327 id: lfhyperledger-2021-01-19+Office+Hours author: lfhyperledger title: lfhyperledger-2021-01-19+Office+Hours date: None words: 445 flesch: 4 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute Show more below You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; contributor cache: lfhyperledger-2021-01-19+Office+Hours.html plain text: lfhyperledger-2021-01-19+Office+Hours.txt item: #2042 of 3327 id: lfhyperledger-2021-01-19+Office+Hours+Notes author: lfhyperledger title: lfhyperledger-2021-01-19+Office+Hours+Notes date: None words: 372 flesch: 17 summary: 21.2 RC cycle has begun Future releases Work Updates  OpenTelemetry Overview (Antoine Toulme) Berlin HF Status Bonsai Tries Status Other Business Open Forum Future Topics , multiple selections available, Related content More info Collapse 2021-01-19 Office Hours 2021-01-19 Office Hours Besu More like this 2021-02-16 Office Hours 2021-02-16 Office Hours Besu More like this 2020-11-24 Office Hours 2020-11-24 Office Hours Besu More like this 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time Besu More like this 2020 12 10 TSC Minutes 2020 12 10 TSC Minutes Technical Oversight Committee More like this 2022-09-27 Contributor Call 2022-09-27 Contributor Call Besu More like this {serverDuration: 40, requestCorrelationId: 750f6c79aab74dbd99834f7f93add8b0} PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: hours; office cache: lfhyperledger-2021-01-19+Office+Hours+Notes.html plain text: lfhyperledger-2021-01-19+Office+Hours+Notes.txt item: #2043 of 3327 id: lfhyperledger-2021-02-02+Office+Hours author: lfhyperledger title: lfhyperledger-2021-02-02+Office+Hours date: None words: 455 flesch: 16 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute Show more below You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; contributor cache: lfhyperledger-2021-02-02+Office+Hours.html plain text: lfhyperledger-2021-02-02+Office+Hours.txt item: #2044 of 3327 id: lfhyperledger-2021-02-16+Office+Hours author: lfhyperledger title: lfhyperledger-2021-02-16+Office+Hours date: None words: 448 flesch: 7 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; contributor cache: lfhyperledger-2021-02-16+Office+Hours.html plain text: lfhyperledger-2021-02-16+Office+Hours.txt item: #2045 of 3327 id: lfhyperledger-2021-03-02+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2021-03-02+Besu+Contributor+Call date: None words: 462 flesch: 31 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; contributor cache: lfhyperledger-2021-03-02+Besu+Contributor+Call.html plain text: lfhyperledger-2021-03-02+Besu+Contributor+Call.txt item: #2046 of 3327 id: lfhyperledger-2021-03-16+Besu+Office+Hours author: lfhyperledger title: lfhyperledger-2021-03-16+Besu+Office+Hours date: None words: 600 flesch: 19 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; besu contributor; contributor cache: lfhyperledger-2021-03-16+Besu+Office+Hours.html plain text: lfhyperledger-2021-03-16+Besu+Office+Hours.txt item: #2047 of 3327 id: lfhyperledger-2021-03-30+Besu+Office+Hours author: lfhyperledger title: lfhyperledger-2021-03-30+Besu+Office+Hours date: None words: 465 flesch: 14 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Close Besu / 2021-03-30 Besu Office Hours More actions 2021-03-30 Besu Office Hours Sally MacFarlane Owned by Sally MacFarlane Last updated: Mar 29, 2021 (Meeting Link: â�¨https://consensys.zoom.us/j/98345085456â�©) APAC/AMER Friendly Time -  0100UTC (https://www.timeanddate.com/worldclock/converter.html?iso=20201013T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 6 pm Monday Los Angeles 9 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements Release updates 21.1.3 is out Work Updates QBFT and GoQuorum interop - also how to make this visible on an ongoing basis Other Business Open Forum Future Topics Due to technical difficulties (unable to use previous zoom meeting), this meeting was neither attended nor recorded. keywords: besu; contributor cache: lfhyperledger-2021-03-30+Besu+Office+Hours.html plain text: lfhyperledger-2021-03-30+Besu+Office+Hours.txt item: #2048 of 3327 id: lfhyperledger-2021-04-13+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2021-04-13+Besu+Contributor+Call date: None words: 583 flesch: 11 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Interested in connecting hook that pushes block info with Rocketchat for easier debugging (Matt) Work Updates Contributor meeting pull request for contributors requires permissioning (Gary Schulte) Other Business Open Forum Future Topics Recording:  https://consensys.zoom.us/rec/share/pFQhgPXPWdirAiPhZXC2ye7xlt7-js3uoz57LIHx7aQrYqmr3wswz3Q-KfAVyIjA.SAVMBEe8y7d_bkff  Passcode: km5PLp8? , multiple selections available, Related content More info Collapse 2021-07-19 Besu Contributor Call 2021-07-19 Besu Contributor Call Besu More like this 2021-09-28 Besu Contributor Call 2021-09-28 Besu Contributor Call Besu More like this 2020-09-15 Contributor Call 2020-09-15 Contributor Call Besu More like this 2023-10-31 Contributor Call 2023-10-31 Contributor Call Besu More like this 2022-06-07 Contributor Call 2022-06-07 Contributor Call Besu More like this 2022-11-22 Contributor Call 2022-11-22 Contributor Call Besu More like this {serverDuration: 12, requestCorrelationId: a9483e19874e4260b11ebb1563a646d2} keywords: besu; contributor cache: lfhyperledger-2021-04-13+Besu+Contributor+Call.html plain text: lfhyperledger-2021-04-13+Besu+Contributor+Call.txt item: #2049 of 3327 id: lfhyperledger-2021-04-23+ATs+failures author: lfhyperledger title: lfhyperledger-2021-04-23+ATs+failures date: None words: 703 flesch: 50 summary: Close Besu / 2021-04-23 ATs failures More actions 2021-04-23 ATs failures Sally MacFarlane Owned by Sally MacFarlane Jun 12, 2024 Context: AT’s started failing late April 2021 This Circle CI report is interesting - significant failures vs successes these failures started happening April 23 coinciding with (but not known to be caused by) the introduction of PRs: SECP256R1 (PR 2008) container tests (Tessera in Orion mode; some Besu privacy ATs) notably, the Tessera in Orion mode container tests did not get merged into master also I think the Besu container tests step has been disabled? If entropy is the problem look to seed a device and use that - use haveged etc What have we tried: reducing parallelism - was 8, changed to 6 → AT time 12 min → 15 min installing haveged on AT executor → seemed to be better explicitly setting securerandom.source=/dev/urandom → no change evident removing haveged and explicitly setting securerandom.source=file:/dev/urandom → ATs failed in 8 min with a ECDH “Invalid point coordinatesâ€� error. keywords: ats; tests cache: lfhyperledger-2021-04-23+ATs+failures.html plain text: lfhyperledger-2021-04-23+ATs+failures.txt item: #2050 of 3327 id: lfhyperledger-2021-04-26+Besu+Office+Hours author: lfhyperledger title: lfhyperledger-2021-04-26+Besu+Office+Hours date: None words: 448 flesch: 2 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; contributor cache: lfhyperledger-2021-04-26+Besu+Office+Hours.html plain text: lfhyperledger-2021-04-26+Besu+Office+Hours.txt item: #2051 of 3327 id: lfhyperledger-2021-05-11+Besu+Office+Hours author: lfhyperledger title: lfhyperledger-2021-05-11+Besu+Office+Hours date: None words: 429 flesch: 8 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; contributor cache: lfhyperledger-2021-05-11+Besu+Office+Hours.html plain text: lfhyperledger-2021-05-11+Besu+Office+Hours.txt item: #2052 of 3327 id: lfhyperledger-2021-05-24+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2021-05-24+Besu+Contributor+Call date: None words: 922 flesch: 11 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Last updated: May 24, 2021 (Meeting Link: â�¨https://consensys.zoom.us/j/94665568300â�©)  APAC/AMER Friendly Time -  0100UTC (https://www.timeanddate.com/worldclock/converter.html?iso=20201013T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 6 pm Monday Los Angeles 9 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements A few contributors and maintainers from ConsenSys will be at the global forum  Grace is facilitating panel on use-cases on Besu, Lucas is hosting Besu demo  Danno presenting Bonzai demo, Goerli demo, Ethereum layer 2 related to Hyperledger Hyperledger Besu certification survey results are in!  keywords: agendas; besu; besu contributor; contributor cache: lfhyperledger-2021-05-24+Besu+Contributor+Call.html plain text: lfhyperledger-2021-05-24+Besu+Contributor+Call.txt item: #2053 of 3327 id: lfhyperledger-2021-06-08+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2021-06-08+Besu+Contributor+Call date: None words: 569 flesch: 6 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. We used to have to submit EIPs — this way is easier/ faster for making JSON RPC changes Still pending PRs for JSON RPC changes for EIP-1559 GoQuorum ATs is now a required build step Turned on acceptance tests with interoperability with Besu <> GoQuorum  Other Business  Next Besu quarterly report to TSC is scheduled for June 24th 2021 Q1 Hyperledger Besu TSC Project Updates Open Forum Future Topics **Recording will be added here after the call https://consensys.zoom.us/rec/share/C2hvJBqw30Uirxm2kNoJrPNu_MrECpBR43VSGMMQf7vq6FwGtk2DXOk7NiN1paqx.OGlplsDEAU20yJg7  Passcode: NB72qs?G , multiple selections available, {serverDuration: 10, requestCorrelationId: 5659c8e2cb594f089383ccb1b6809d9e} keywords: besu; contributor cache: lfhyperledger-2021-06-08+Besu+Contributor+Call.html plain text: lfhyperledger-2021-06-08+Besu+Contributor+Call.txt item: #2054 of 3327 id: lfhyperledger-2021-06-21+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2021-06-21+Besu+Contributor+Call date: None words: 450 flesch: 11 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; contributor cache: lfhyperledger-2021-06-21+Besu+Contributor+Call.html plain text: lfhyperledger-2021-06-21+Besu+Contributor+Call.txt item: #2055 of 3327 id: lfhyperledger-2021-07-06+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2021-07-06+Besu+Contributor+Call date: None words: 671 flesch: -4 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Last updated: Jul 08, 2021 (Meeting Link: â�¨https://consensys.zoom.us/j/95691099798) EMEA/AMER Friendly Time -  1500 UTC (https://www.timeanddate.com/worldclock/converter.html?iso=20201012T150000&p1=224&p2=179&p3=1440&p4=195&p5=47) 8 AM Tuesday San Francisco 11 AM Tuesday New York 3 PM Tuesday UTC 5 PM Tuesday Paris/Berlin 1 AM Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements Release updates London PR with Mainnet block # on ETH1 Specs Repo (Rai)  Waiting to get merged - then we will have what we need to release with mainnet block # for London We could be releasing Besu 21.7.0 (July 7th, 2021) if all goes well with the block number proposed to the eth1-specs repo Ropsten consensus issue release also needs to be merged in (Rai) Rai - Issue: When base fee was low, we weren't calculating delta properly  Justin - It's a trivial fix Clients are aiming to have releases with mainnet block number before allcoredevs this Friday (Rai) Work Updates ETH 66 (Rai - WIP) https://github.com/hyperledger/besu/issues/2210 Issue for Bonsai (Rai) https://github.com/hyperledger/besu/pull/2492 Improvements to transaction pool (Justin) Expected to make it into the release (Besu 21.7.0) https://github.com/hyperledger/besu/pull/2505 Ping pong serialization issue  Transaction pool changes  If you flood the transaction pool  Increasing the size of the transaction pool, so the maximum allowable dev p2p message as 10mb - increasing the size of the pool, to prevent malicious transactions  Transaction mempool has been low in memory and isn't affected too much  Might make it into release besu 21.7.0 External to maintainers of Besu are interested in contributing to state expiry using Besu Working on getting Besu snaps ready  Work on code hashes  Other Business  Want to contribute? keywords: besu; besu contributor; contributor cache: lfhyperledger-2021-07-06+Besu+Contributor+Call.html plain text: lfhyperledger-2021-07-06+Besu+Contributor+Call.txt item: #2056 of 3327 id: lfhyperledger-2021-07-19+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2021-07-19+Besu+Contributor+Call date: None words: 602 flesch: 17 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: agendas; besu contributor cache: lfhyperledger-2021-07-19+Besu+Contributor+Call.html plain text: lfhyperledger-2021-07-19+Besu+Contributor+Call.txt item: #2057 of 3327 id: lfhyperledger-2021-08-03+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2021-08-03+Besu+Contributor+Call date: None words: 618 flesch: 42 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; contributor cache: lfhyperledger-2021-08-03+Besu+Contributor+Call.html plain text: lfhyperledger-2021-08-03+Besu+Contributor+Call.txt item: #2058 of 3327 id: lfhyperledger-2021-08-04+Value+transfer+public+transactions+being+rejected+by+Besu author: lfhyperledger title: lfhyperledger-2021-08-04+Value+transfer+public+transactions+being+rejected+by+Besu date: None words: 782 flesch: 55 summary: Problem The scope of this problem is limited to: Value transfer public transactions received via JSON-RPC Value transfer public transactions received via DevP2P When receiving a value transfer tx via JSON-RPC, Besu was considering it a private tx and enforcing a validity check that prevents private transactions from transferring value. But later we identified that the change in the TransactionPool would cause issues for value transfer public transactions. keywords: besu; transactions cache: lfhyperledger-2021-08-04+Value+transfer+public+transactions+being+rejected+by+Besu.html plain text: lfhyperledger-2021-08-04+Value+transfer+public+transactions+being+rejected+by+Besu.txt item: #2059 of 3327 id: lfhyperledger-2021-08-16+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2021-08-16+Besu+Contributor+Call date: None words: 483 flesch: 11 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; contributor cache: lfhyperledger-2021-08-16+Besu+Contributor+Call.html plain text: lfhyperledger-2021-08-16+Besu+Contributor+Call.txt item: #2060 of 3327 id: lfhyperledger-2021-08-31+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2021-08-31+Besu+Contributor+Call date: None words: 581 flesch: 13 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. No licensing issue at least with Caffeine (It’s Apche2.0) no problem having two implementations  Base fee adjustment discussion Other Business  Timeline for migration from RocketChat to Matrix → https://chat.lfx.linuxfoundation.org/#/welcome Francesco and Matt W to work on schedule posts to incentivize new chat engagement  Start with Besu contributor channel and have them join other chat  1-2 month schedule  Good first issues for Open Source Day TSC Election Nominations have kicked off Open Forum Future Topics Recording:  https://consensys.zoom.us/rec/share/-9whpiZ-FA2QoFL4PBmh7scaa6DDcXRUUlsyMAtqRxRHNFbcTUuWnLEp_9rxIrKK.ZI2IsrXCwgZQGugG  Passcode: R5J*vE9x , multiple selections available, {serverDuration: 12, requestCorrelationId: 2da7e9d5b5ee42cd9ed8d7c49c247e22} keywords: besu; besu contributor; contributor cache: lfhyperledger-2021-08-31+Besu+Contributor+Call.html plain text: lfhyperledger-2021-08-31+Besu+Contributor+Call.txt item: #2061 of 3327 id: lfhyperledger-2021-09-13+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2021-09-13+Besu+Contributor+Call date: None words: 664 flesch: 19 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; besu contributor; contributor cache: lfhyperledger-2021-09-13+Besu+Contributor+Call.html plain text: lfhyperledger-2021-09-13+Besu+Contributor+Call.txt item: #2062 of 3327 id: lfhyperledger-2021-09-28+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2021-09-28+Besu+Contributor+Call date: None words: 632 flesch: 20 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; besu contributor; contributor cache: lfhyperledger-2021-09-28+Besu+Contributor+Call.html plain text: lfhyperledger-2021-09-28+Besu+Contributor+Call.txt item: #2063 of 3327 id: lfhyperledger-2021-10-11+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2021-10-11+Besu+Contributor+Call date: None words: 545 flesch: 20 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. We need to get contributors, and folks from main Besu chat to Matrix HL Besu (Matrix) HL Besu Contributors (Matrix) keywords: besu; contributor cache: lfhyperledger-2021-10-11+Besu+Contributor+Call.html plain text: lfhyperledger-2021-10-11+Besu+Contributor+Call.txt item: #2064 of 3327 id: lfhyperledger-2021-10-26+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2021-10-26+Besu+Contributor+Call date: None words: 519 flesch: 21 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; contributor cache: lfhyperledger-2021-10-26+Besu+Contributor+Call.html plain text: lfhyperledger-2021-10-26+Besu+Contributor+Call.txt item: #2065 of 3327 id: lfhyperledger-2021-11-09+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2021-11-09+Besu+Contributor+Call date: None words: 597 flesch: 4 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; besu contributor; contributor cache: lfhyperledger-2021-11-09+Besu+Contributor+Call.html plain text: lfhyperledger-2021-11-09+Besu+Contributor+Call.txt item: #2066 of 3327 id: lfhyperledger-2021-11-23+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2021-11-23+Besu+Contributor+Call date: None words: 687 flesch: 20 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; besu contributor cache: lfhyperledger-2021-11-23+Besu+Contributor+Call.html plain text: lfhyperledger-2021-11-23+Besu+Contributor+Call.txt item: #2067 of 3327 id: lfhyperledger-2021-12-07+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2021-12-07+Besu+Contributor+Call date: None words: 596 flesch: 20 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; besu contributor; contributor cache: lfhyperledger-2021-12-07+Besu+Contributor+Call.html plain text: lfhyperledger-2021-12-07+Besu+Contributor+Call.txt item: #2068 of 3327 id: lfhyperledger-2021-12-21+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2021-12-21+Besu+Contributor+Call date: None words: 1083 flesch: 23 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: agendas; besu; besu contributor; contributor cache: lfhyperledger-2021-12-21+Besu+Contributor+Call.html plain text: lfhyperledger-2021-12-21+Besu+Contributor+Call.txt item: #2069 of 3327 id: lfhyperledger-2021-12-30+Besu+Contributor+Call+off+cycle author: lfhyperledger title: lfhyperledger-2021-12-30+Besu+Contributor+Call+off+cycle date: None words: 888 flesch: 50 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2021-01-19 Office Hours 2021-02-02 Office Hours 2021-02-16 Office Hours 2021-03-02 Besu Contributor Call 2021-03-16 Besu Office Hours 2021-03-30 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-04-26 Besu Office Hours 2021-05-11 Besu Office Hours 2021-05-24 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-12-30 Besu Contributor Call (off cycle) 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked.   Non-ConsenSys employees are having issues getting their PRs reviewed. Ideas for improving Besu community:  Having all contributors join monthly Contributor call Public roadmap on wiki covered in monthly contributor call needs to be up to date Discord chat channel moving forward. keywords: agendas; besu; contributor cache: lfhyperledger-2021-12-30+Besu+Contributor+Call+off+cycle.html plain text: lfhyperledger-2021-12-30+Besu+Contributor+Call+off+cycle.txt item: #2070 of 3327 id: lfhyperledger-2022+Agendas author: lfhyperledger title: lfhyperledger-2022+Agendas date: None words: 495 flesch: 1 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning Show more below You‘re viewing this with anonymous access, so some content might be blocked. Agendas Ry Jones Owned by Ry Jones Dec 21, 2021 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call , multiple selections available, {serverDuration: 12, requestCorrelationId: b074d7520627492f961a86a714e8a3be} keywords: contributor cache: lfhyperledger-2022+Agendas.html plain text: lfhyperledger-2022+Agendas.txt item: #2071 of 3327 id: lfhyperledger-2022-01-04+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-01-04+Besu+Contributor+Call date: None words: 1052 flesch: 41 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute Show more below You‘re viewing this with anonymous access, so some content might be blocked. View recording:   File Modified Labels No labels Preview View File Besu 2022-01-04.transcript.vtt Jan 03, 2022 by Ry Jones Labels No labels Preview View Text File Besu 2022-01-04.txt Jan 03, 2022 by Ry Jones Download All , multiple selections available, Related content More info Collapse 2021-12-07 Besu Contributor Call 2021-12-07 Besu Contributor Call Besu More like this 2021-11-23 Besu Contributor Call 2021-11-23 Besu Contributor Call Besu More like this 2022-03-01 Contributor Call 2022-03-01 Contributor Call Besu More like this 2022-03-15 Contributor Call 2022-03-15 Contributor Call Besu More like this 2022-04-12 Contributor Call 2022-04-12 Contributor Call Besu More like this 2022-10-25 Contributor Call 2022-10-25 Contributor Call Besu More like this {serverDuration: 14, requestCorrelationId: 6e5c10cbac3d48ce82e2831ae0e621b5} keywords: apac; besu; contributor; time cache: lfhyperledger-2022-01-04+Besu+Contributor+Call.html plain text: lfhyperledger-2022-01-04+Besu+Contributor+Call.txt item: #2072 of 3327 id: lfhyperledger-2022-01-11+Besu+Contributor+Call+-+Off-Cycle author: lfhyperledger title: lfhyperledger-2022-01-11+Besu+Contributor+Call+-+Off-Cycle date: None words: 778 flesch: 39 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute Show more below You‘re viewing this with anonymous access, so some content might be blocked. View recording:    File Modified Labels No labels Preview View PDF File Besu PKI Support.pdf Dec 21, 2021 by Francesco Andreoli Labels No labels Preview View Text File Besu 2022 JAN 11.txt Jan 11, 2022 by Ry Jones Download All , multiple selections available, Related content More info Collapse 2020-01-07 Besu Contributor Call 2020-01-07 Besu Contributor Call Besu More like this 2020-09-29 Besu Contributor Call 2020-09-29 Besu Contributor Call Besu More like this 2019-11-26 Besu Contributor Call 2019-11-26 Besu Contributor Call Besu More like this 2021-04-13 Besu Contributor Call 2021-04-13 Besu Contributor Call Besu More like this 2019-12-10 Besu Contributor Call 2019-12-10 Besu Contributor Call Besu More like this 2020-04-14 Besu Contributor Call 2020-04-14 Besu Contributor Call Besu More like this {serverDuration: 13, requestCorrelationId: b0d638ec9a964e85a30b7388c318286b} keywords: besu; besu contributor; contributor cache: lfhyperledger-2022-01-11+Besu+Contributor+Call+-+Off-Cycle.html plain text: lfhyperledger-2022-01-11+Besu+Contributor+Call+-+Off-Cycle.txt item: #2073 of 3327 id: lfhyperledger-2022-01-20+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-01-20+Besu+Contributor+Call date: None words: 630 flesch: 1 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: agendas; besu; contributor cache: lfhyperledger-2022-01-20+Besu+Contributor+Call.html plain text: lfhyperledger-2022-01-20+Besu+Contributor+Call.txt item: #2074 of 3327 id: lfhyperledger-2022-01-31+Besu+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-01-31+Besu+Contributor+Call date: None words: 615 flesch: 12 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2022-01-31 Besu Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: apac; besu; contributor cache: lfhyperledger-2022-01-31+Besu+Contributor+Call.html plain text: lfhyperledger-2022-01-31+Besu+Contributor+Call.txt item: #2075 of 3327 id: lfhyperledger-2022-02-15+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-02-15+Contributor+Call date: None words: 883 flesch: 25 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Q on maintainer definition - who decides? Participation as a MM is more fluid than Besu Maintainer Some MMs may take sabbaticals Besu community consensus should decide, EF and HLF make final call. keywords: agendas; apac; besu; contributor cache: lfhyperledger-2022-02-15+Contributor+Call.html plain text: lfhyperledger-2022-02-15+Contributor+Call.txt item: #2076 of 3327 id: lfhyperledger-2022-03-01+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-03-01+Contributor+Call date: None words: 683 flesch: 34 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. When? Deprecating log42j - from Diego see Contributor channel Future Topics   File Modified No files shared here yet. , multiple selections available, {serverDuration: 36, requestCorrelationId: f793d58151f64c968e524fd30892a68e} keywords: apac; besu; contributor cache: lfhyperledger-2022-03-01+Contributor+Call.html plain text: lfhyperledger-2022-03-01+Contributor+Call.txt item: #2077 of 3327 id: lfhyperledger-2022-03-15+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-03-15+Contributor+Call date: None words: 787 flesch: 30 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2022-03-15 Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: agendas; besu; contributor cache: lfhyperledger-2022-03-15+Contributor+Call.html plain text: lfhyperledger-2022-03-15+Contributor+Call.txt item: #2078 of 3327 id: lfhyperledger-2022-03-29+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-03-29+Contributor+Call date: None words: 746 flesch: 41 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2022-03-29 Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: agendas; apac; contributor cache: lfhyperledger-2022-03-29+Contributor+Call.html plain text: lfhyperledger-2022-03-29+Contributor+Call.txt item: #2079 of 3327 id: lfhyperledger-2022-04-12+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-04-12+Contributor+Call date: None words: 877 flesch: 54 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Apr 12, 2022 by Grace Hartley (Deactivated) (Meeting Link: â�¨https://zoom.us/j/97540031823?pwd=dEJrRW1LakFlWnZPelI3VGxoVjg2dz09) EMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20201012T150000&p1=224&p2=179&p3=1440&p4=195&p5=47) 8 am Monday Los Angeles 11 am Monday New York Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements Incentive Program Update: keywords: agendas; besu; contributor cache: lfhyperledger-2022-04-12+Contributor+Call.html plain text: lfhyperledger-2022-04-12+Contributor+Call.txt item: #2080 of 3327 id: lfhyperledger-2022-04-26+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-04-26+Contributor+Call date: None words: 789 flesch: 38 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20201012T150000&p1=224&p2=179&p3=1440&p4=195&p5=47) 5 pm Monday Los Angeles 8 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements Incentive Program Update: keywords: agendas; apac; besu; contributor cache: lfhyperledger-2022-04-26+Contributor+Call.html plain text: lfhyperledger-2022-04-26+Contributor+Call.txt item: #2081 of 3327 id: lfhyperledger-2022-05-10+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-05-10+Contributor+Call date: None words: 967 flesch: 39 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Close Besu / 2022-05-10 Contributor Call More actions 2022-05-10 Contributor Call Francesco Andreoli Sally MacFarlane Hart Montgomery Grace Hartley (Deactivated) Owned by Francesco Andreoli Last updated: May 10, 2022 (Meeting Link: â�¨https://zoom.us/j/97540031823?pwd=dEJrRW1LakFlWnZPelI3VGxoVjg2dz09) EMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20201012T150000&p1=224&p2=179&p3=1440&p4=195&p5=47) 8 am Monday Los Angeles 11 am Monday New York Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements Incentive Program Update: keywords: agendas; besu; contributor cache: lfhyperledger-2022-05-10+Contributor+Call.html plain text: lfhyperledger-2022-05-10+Contributor+Call.txt item: #2082 of 3327 id: lfhyperledger-2022-05-24+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-05-24+Contributor+Call date: None words: 814 flesch: 38 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20201012T150000&p1=224&p2=179&p3=1440&p4=195&p5=47) 5 pm Monday Los Angeles 8 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements Incentive Program Update: keywords: apac; besu; contributor cache: lfhyperledger-2022-05-24+Contributor+Call.html plain text: lfhyperledger-2022-05-24+Contributor+Call.txt item: #2083 of 3327 id: lfhyperledger-2022-05-30+Phishing+PRs author: lfhyperledger title: lfhyperledger-2022-05-30+Phishing+PRs date: None words: 391 flesch: 34 summary: Issue reported to Circle CI and they reported back: secrets were not exposed Recommend disabling this CI setting: Pass secrets to builds from forked pull requests Recommend rotating credentials Unfortunately, disabling the pass secrets to forked PRs means that Sonar can't run on PRs plan is to temporarily disable this while we figure out a solution , multiple selections available, Related content More info Collapse 2022-01-28 Meeting Minutes 2022-01-28 Meeting Minutes Task Forces More like this 2021-12-13 Meeting Minutes 2021-12-13 Meeting Minutes Task Forces More like this Security Security Besu More like this 2023-08-08 Cacti Maintainers Agenda 2023-08-08 Cacti Maintainers Agenda Hyperledger Cacti More like this 2022 Q3 Hyperledger Cactus 2022 Q3 Hyperledger Cactus Technical Oversight Committee More like this 2021 Q1 Hyperledger Besu 2021 Q1 Hyperledger Besu Technical Oversight Committee PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; prs cache: lfhyperledger-2022-05-30+Phishing+PRs.html plain text: lfhyperledger-2022-05-30+Phishing+PRs.txt item: #2084 of 3327 id: lfhyperledger-2022-06-07+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-06-07+Contributor+Call date: None words: 954 flesch: 13 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call Make Besu questions easy to find and answer 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Timeline? discord discussion Validator Experience with Besu Matt Nelson (Deactivated)  connecting with David Boswell framework to engage with merge audience to tailor workshop before merge later merge no ETA yet  Francesco Andreolihelping organizing Metrics Review - https://insights.lfx.linuxfoundation.org/projects/hyperledger%2Fbesu/dashboard;quicktime=time_filter_3Y Roadmap Review - Roadmap Note from Matt on 22.7  fixing, testing with EF  optimistic support, rollup client diversity question  Matt Nelson (Deactivated)  will engage more with those devs regarding changes rollups product requirement  example on providing more APIs New addition - peering improvement and node operations improvement improving node operations (Helen input) scale faster, investigations on lowering cost version release discussion  quarterly releases Open Forum chitchat calendar in the calendar - besu group - (Todo Francesco Andreoli ) it’ll be this time/day next week, and then alternating with this meeting GitHub issue discussion started from Nicolas Massart writing a quick proposal Future Topics   File Modified Labels No labels Preview View PDF File main.pdf May 10, 2022 by Francesco Andreoli Labels No labels Preview View File GMT20220607-145708_Recording.transcript.vtt Jun 07, 2022 by Ry Jones Labels No labels Preview View File GMT20220607-150205_Recording.transcript.vtt Jun 07, 2022 by Ry Jones Labels No labels Preview View Text File GMT20220607-150205_Recording.txt Jun 07, 2022 by Ry Jones Download All , multiple selections available, Related content More info Collapse 2022-05-10 Contributor Call 2022-05-10 Contributor Call Besu More like this 2022-03-15 Contributor Call 2022-03-15 Contributor Call Besu More like this 2023-03-14 Contributor Call 2023-03-14 Contributor Call Besu More like this 2022-12-20 Contributor Call 2022-12-20 Contributor Call Besu More like this 2022-11-22 Contributor Call 2022-11-22 Contributor Call Besu More like this 2022-01-20 Besu Contributor Call 2022-01-20 Besu Contributor Call Besu More like this {serverDuration: 35, requestCorrelationId: 1f6c0846672d409fa80bd62561e3a4d4} keywords: agendas; besu; contributor; time cache: lfhyperledger-2022-06-07+Contributor+Call.html plain text: lfhyperledger-2022-06-07+Contributor+Call.txt item: #2085 of 3327 id: lfhyperledger-2022-06-21+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2022-06-21+Contributor+Call+-+APAC+Friendly+Time date: None words: 684 flesch: 21 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220621T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 6 pm Monday Los Angeles 9 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements /Add item/  Roadmap Review - Besu Roadmap Release updates 22.4.3 complete https://github.com/hyperledger/besu/releases/tag/22.4.3 Next planned release is 22.7.0-RC1 scheduled for 29 June (Danno) Release Rotations 2022 Should we release off main branch - discussion to happen on discord Work Updates Code Audit starting 24 June Primary focus is the engine APIs for Eth Merge Nothing for you to do unless directly asked Java 17 Migration Status: Yellow Possibly move to 22.10.0 release All issues are mostly Build/CircleCI/testing related, not code related. keywords: apac; contributor; time cache: lfhyperledger-2022-06-21+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2022-06-21+Contributor+Call+-+APAC+Friendly+Time.txt item: #2086 of 3327 id: lfhyperledger-2022-07-05+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-07-05+Contributor+Call date: None words: 876 flesch: 31 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Close Besu / 2022-07-05 Contributor Call More actions 2022-07-05 Contributor Call Francesco Andreoli Hart Montgomery Danno Ferrin Daniel Lehrner Owned by Francesco Andreoli Last updated: Jul 05, 2022 (Meeting Link: â�¨https://zoom.us/j/97540031823?pwd=dEJrRW1LakFlWnZPelI3VGxoVjg2dz09) EMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220607T150000&p1=224&p2=179&p3=1440&p4=195&p5=47) 8 am Tuesday Los Angeles time 11 am Tuesday New York time 17h Tuesday Paris time Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements mentioning this from Hart Tim Beiko (in charge of the Besu CIP program from the EF side) likes our format. keywords: agendas; besu; contributor; time cache: lfhyperledger-2022-07-05+Contributor+Call.html plain text: lfhyperledger-2022-07-05+Contributor+Call.txt item: #2087 of 3327 id: lfhyperledger-2022-07-19+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2022-07-19+Contributor+Call+-+APAC+Friendly+Time date: None words: 686 flesch: 4 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked.   no objections add to besu-docs and besu-native also? will it encourage contributions? encouraging contributions to docs specifically would be useful - and is one of the hardest things to get ppl to contribute to Metrics Review - Linux Foundation Project Besu Insights Open Forum /Add item/  Future Topics /Add item/    File Modified Labels No labels Preview View File GMT20220719-010420_Recording.transcript.vtt Jul 20, 2022 by Ry Jones Labels No labels Preview View Text File GMT20220719-010420_Recording.txt Jul 20, 2022 by Ry Jones Download All , multiple selections available, {serverDuration: 42, requestCorrelationId: 3e79b411ab3640ffaaebbcd4ffbbdda7} keywords: apac; contributor; time cache: lfhyperledger-2022-07-19+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2022-07-19+Contributor+Call+-+APAC+Friendly+Time.txt item: #2088 of 3327 id: lfhyperledger-2022-08-02+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-08-02+Contributor+Call date: None words: 486 flesch: -20 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2022-08-02 Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; contributor cache: lfhyperledger-2022-08-02+Contributor+Call.html plain text: lfhyperledger-2022-08-02+Contributor+Call.txt item: #2089 of 3327 id: lfhyperledger-2022-08-16+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2022-08-16+Contributor+Call+-+APAC+Friendly+Time date: None words: 584 flesch: 27 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220621T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 6 pm Monday Los Angeles 9 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements /Add item/ Roadmap Review - Besu Roadmap Release updates 22.7.1 planned for early next week focus on The Merge - if it's not critical, consider delaying merging your PR Work Updates Shanghai   When can features be committed to shanghaiBlock? Options for experimental features? can use feature forks Shanghai EVM Work  EOF (Danno Ferrin) container (EIP-3540) bytecode validation (EIP-3670) Transient Storage (EIP-1153) (PR #4118) keywords: apac; contributor; time cache: lfhyperledger-2022-08-16+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2022-08-16+Contributor+Call+-+APAC+Friendly+Time.txt item: #2090 of 3327 id: lfhyperledger-2022-08-30+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-08-30+Contributor+Call date: None words: 771 flesch: 9 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; contributor; time cache: lfhyperledger-2022-08-30+Contributor+Call.html plain text: lfhyperledger-2022-08-30+Contributor+Call.txt item: #2091 of 3327 id: lfhyperledger-2022-09-13+Contributor+Call+-+APAC author: lfhyperledger title: lfhyperledger-2022-09-13+Contributor+Call+-+APAC date: None words: 567 flesch: 13 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2022-09-13 Contributor Call - APAC - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: apac; besu; contributor cache: lfhyperledger-2022-09-13+Contributor+Call+-+APAC.html plain text: lfhyperledger-2022-09-13+Contributor+Call+-+APAC.txt item: #2092 of 3327 id: lfhyperledger-2022-09-27+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-09-27+Contributor+Call date: None words: 516 flesch: -9 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2022-09-27 Contributor Call - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: contributor; time cache: lfhyperledger-2022-09-27+Contributor+Call.html plain text: lfhyperledger-2022-09-27+Contributor+Call.txt item: #2093 of 3327 id: lfhyperledger-2022-1-31+Contributor+Call+notes author: lfhyperledger title: lfhyperledger-2022-1-31+Contributor+Call+notes date: None words: 722 flesch: 53 summary: Hyperledger (Daniela) to come back on on these open questions: Can Hyperledger hold the withdrawal keys and hold crypto Can they hold the funds from the transaction fees and distribute them to participating maintainers’ organizations Can Hyperledger commit to using the funds solely for Besu mainnet work Can Hyperledger assign someone on staff as a Besu community manager to help manage the maintainer list, scope out bounties, manage the program from their side , multiple selections available, Related content More info Collapse 2022-03-29 Contributor Call 2022-03-29 Contributor Call Besu More like this 2022-03-15 Contributor Call 2022-03-15 Contributor Call Besu More like this 2022-02-15 Contributor Call 2022-02-15 Contributor Call Besu More like this 2022-12-20 Contributor Call 2022-12-20 Contributor Call Besu More like this 2022-03-01 Contributor Call 2022-03-01 Contributor Call Besu More like this 2022-04-12 Contributor Call 2022-04-12 Contributor Call Besu More like this {serverDuration: 13, requestCorrelationId: 8e0c9f22df444fb59cf478e329103b81} Danno was concerned that proposal #3 doesn't account for new organizations well. keywords: besu; contributor; notes cache: lfhyperledger-2022-1-31+Contributor+Call+notes.html plain text: lfhyperledger-2022-1-31+Contributor+Call+notes.txt item: #2094 of 3327 id: lfhyperledger-2022-10-11+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2022-10-11+Contributor+Call+-+APAC+Friendly+Time date: None words: 657 flesch: 4 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Raise discussion in release discord channel https://github.com/hyperledger/besu/pull/3953 Other Business proposed updates to maintainers https://github.com/hyperledger/besu/pull/4479 https://github.com/hyperledger/besu/pull/4480 Open Forum Future Topics   File Modified Labels No labels Preview View File GMT20221011-010052_Recording.transcript.vtt Oct 12, 2022 by Ry Jones Labels No labels Preview View Text File GMT20221011-010052_Recording.txt Oct 12, 2022 by Ry Jones Download All , multiple selections available, Related content More info Collapse 2023-12-05 Contributor Call - APAC Friendly Time 2023-12-05 Contributor Call - APAC Friendly Time Besu More like this 2022-06-21 Contributor Call - APAC Friendly Time 2022-06-21 Contributor Call - APAC Friendly Time Besu More like this 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - APAC Friendly Time Besu More like this 2024-03-26 Contributor Call - APAC Friendly Time 2024-03-26 Contributor Call - APAC Friendly Time Besu More like this 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-28 Contributor Call - APAC Friendly Time Besu More like this 2022-11-22 Contributor Call 2022-11-22 Contributor Call Besu More like this {serverDuration: 10, requestCorrelationId: 6482012c891b47a18df68b90824ee42b} keywords: apac; contributor; time cache: lfhyperledger-2022-10-11+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2022-10-11+Contributor+Call+-+APAC+Friendly+Time.txt item: #2095 of 3327 id: lfhyperledger-2022-10-25+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-10-25+Contributor+Call date: None words: 606 flesch: -2 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Close Besu / 2022-10-25 Contributor Call More actions 2022-10-25 Contributor Call Francesco Andreoli Matt Nelson (Deactivated) keywords: besu; contributor; time cache: lfhyperledger-2022-10-25+Contributor+Call.html plain text: lfhyperledger-2022-10-25+Contributor+Call.txt item: #2096 of 3327 id: lfhyperledger-2022-11-08+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2022-11-08+Contributor+Call+-+APAC+Friendly+Time date: None words: 546 flesch: 5 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Close Besu / 2022-11-08 Contributor Call - APAC Friendly Time More actions 2022-11-08 Contributor Call - APAC Friendly Time Helen George (Deactivated) keywords: apac; contributor; time cache: lfhyperledger-2022-11-08+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2022-11-08+Contributor+Call+-+APAC+Friendly+Time.txt item: #2097 of 3327 id: lfhyperledger-2022-11-11+Fork+on+Sepolia author: lfhyperledger title: lfhyperledger-2022-11-11+Fork+on+Sepolia date: None words: 680 flesch: 25 summary: Block 0x2d4042856d73d6c82fcd7a3f1088418ed0e5eed68d1ed6c78d68d5ca89b440ad Transaction 0xea993da47eb3cc4a7d549cd5b2d52bae5b0770807f36e10aad72480d75cdd026,throwable:} {@timestamp:2022-10-31T00:42:16,432,level:INFO,thread:vert.x-worker-thread-0,class:MainnetBlockValidator,message:Optional[Block processing error: transaction invalid Internal Error in Besu - java.lang. Block 2192803 (0x2d4042856d73d6c82fcd7a3f1088418ed0e5eed68d1ed6c78d68d5ca89b440ad),throwable:} {@timestamp:2022-10-31T00:42:16,432,level:WARN,thread:vert.x-worker-thread-0,class:EngineNewPayload,message:Invalid new payload: number: 2192803, hash: 0x2d4042856d73d6c82fcd7a3f1088418ed0e5eed68d1ed6c78d68d5ca89b440ad, parentHash: 0x7385267518859cf18f7844eb4143dfc1754f724cb158e9b8ac87932cec26b526, latestValidHash: 0x7385267518859cf18f7844eb4143dfc1754f724cb158e9b8ac87932cec26b526, status: INVALID, validationError: Block processing error: transaction invalid Internal Error in Besu - java.lang.IllegalArgumentException: An account address must be 20 bytes long, got 32. keywords: besu; sepolia; transaction cache: lfhyperledger-2022-11-11+Fork+on+Sepolia.html plain text: lfhyperledger-2022-11-11+Fork+on+Sepolia.txt item: #2098 of 3327 id: lfhyperledger-2022-11-22+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-11-22+Contributor+Call date: None words: 653 flesch: -25 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. (question from Jiri Peinlich (Deactivated)) Blocker for Java 17? PR is outstanding for it Packaging alternatives (Justin Florentine ) Dependency Injection Drafted PR from Jiri Peinlich (Deactivated) on how we are building our objects Release updates 22.10.1 - scheduled for Nov 30 - what work is still WIP that needs to be included? no pushback from the state considered scheduled Besu charter discussions  Work Updates Shanghai planning  Other Business Metrics Review - https://insights.lfx.linuxfoundation.org/projects/hyperledger%2Fbesu/dashboard;quicktime=time_filter_3Y Roadmap Review - Roadmap - roadmap pending proposal and discussion Open Forum - skipped Future Topics - skipped   File Modified Labels No labels Preview View Text File GMT20221122-155617_Recording.txt Nov 22, 2022 by Ry Jones Labels No labels Preview View File GMT20221122-155617_Recording.transcript.vtt Nov 22, 2022 by Ry Jones Download All , multiple selections available, Related content More info Collapse 2022-10-25 Contributor Call 2022-10-25 Contributor Call Besu More like this 2022-03-15 Contributor Call 2022-03-15 Contributor Call Besu More like this 2022-04-12 Contributor Call 2022-04-12 Contributor Call Besu More like this 2023-03-14 Contributor Call 2023-03-14 Contributor Call Besu More like this 2022-06-07 Contributor Call 2022-06-07 Contributor Call Besu More like this 2022-07-05 Contributor Call 2022-07-05 Contributor Call Besu More like this {serverDuration: 12, requestCorrelationId: de4f1f32f67145b5900d205139b7daa2} keywords: besu; contributor; time cache: lfhyperledger-2022-11-22+Contributor+Call.html plain text: lfhyperledger-2022-11-22+Contributor+Call.txt item: #2099 of 3327 id: lfhyperledger-2022-12-06+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2022-12-06+Contributor+Call+-+APAC+Friendly+Time date: None words: 900 flesch: 0 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. 2022-12-06 Contributor Call - APAC Friendly Time - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: apac; besu; contributor; time cache: lfhyperledger-2022-12-06+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2022-12-06+Contributor+Call+-+APAC+Friendly+Time.txt item: #2100 of 3327 id: lfhyperledger-2022-12-20+Contributor+Call author: lfhyperledger title: lfhyperledger-2022-12-20+Contributor+Call date: None words: 621 flesch: -13 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. EMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220607T150000&p1=224&p2=179&p3=1440&p4=195&p5=47) 8 am Tuesday Los Angeles time 11 am Tuesday New York time 17h Tuesday Paris time Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements CI update(Matt Nelson (Deactivated) ) Provided a CC from ConsenSys for December Matt Nelson (Deactivated) update in discussion with HF good news: withdraw directly from nodes after withdrawal is enabled  DCO issues Github action is apparently currently broken since July Issue to fix the GHA: https://github.com/hyperledger/besu/issues/4837 Several commits on main since July have no DCO and were included in releases Release updates Cut a release several days before the release, 28th ( Gary Schulte ) Only one PR to discuss release process discussion on the proposal 1rst: Friday cut-off prior to release  2nd: Process that delays a release Work Updates Shanghai planning  Withdrawals and EVM EIPs (minus EOF) - we're on the current testnet with this branch: https://github.com/hyperledger/besu/pull/4818 Q2 timeframe for withdrawals (Jiri Peinlich (Deactivated) ) keywords: besu; contributor; time cache: lfhyperledger-2022-12-20+Contributor+Call.html plain text: lfhyperledger-2022-12-20+Contributor+Call.txt item: #2101 of 3327 id: lfhyperledger-2023+Agendas author: lfhyperledger title: lfhyperledger-2023+Agendas date: None words: 633 flesch: 0 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute Show more below You‘re viewing this with anonymous access, so some content might be blocked. Jun 20, 2023 by Ry Jones 2023-12-05 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-08-15 Contributor Call - APAC Friendly Time 2023-08-01 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-07-11 Contributor Call 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time , multiple selections available, Related content More info Collapse 2024 Meeting Agenda and Notes 2024 Meeting Agenda and Notes Healthcare SIG More like this 2019-01-23 Agenda 2019-01-23 Agenda Hyperledger Ursa (EOL) More like this 2024-12-11 Meeting Notes 2024-12-11 Meeting Notes Web3j More like this 2024-11-13 Meeting notes 2024-11-13 Meeting notes Web3j More like this 2024-10-30 Meeting notes 2024-10-30 Meeting notes Web3j More like this 2025-02-05 Meeting notes 2025-02-05 Meeting notes Web3j More like this {serverDuration: 37, requestCorrelationId: 4f0a18f1e82c4cf39e61c4e32a19c869} keywords: contributor cache: lfhyperledger-2023+Agendas.html plain text: lfhyperledger-2023+Agendas.txt item: #2102 of 3327 id: lfhyperledger-2023-01-03+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2023-01-03+Contributor+Call+-+APAC+Friendly+Time date: None words: 509 flesch: 13 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Close Besu / 2023-01-03 Contributor Call - APAC Friendly Time More actions 2023-01-03 Contributor Call - APAC Friendly Time Sally MacFarlane Owned by Sally MacFarlane Dec 08, 2022 keywords: contributor cache: lfhyperledger-2023-01-03+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2023-01-03+Contributor+Call+-+APAC+Friendly+Time.txt item: #2103 of 3327 id: lfhyperledger-2023-01-17+Contributor+Call author: lfhyperledger title: lfhyperledger-2023-01-17+Contributor+Call date: None words: 617 flesch: -18 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Contributor Call Francesco Andreoli Ry Jones Owned by Francesco Andreoli Last updated: Jan 17, 2023 by Ry Jones (Meeting Link: â�¨https://zoom.us/j/97540031823?pwd=dEJrRW1LakFlWnZPelI3VGxoVjg2dz09) EMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220607T150000&p1=224&p2=179&p3=1440&p4=195&p5=47) 8 am Tuesday Los Angeles time 11 am Tuesday New York time 17h Tuesday Paris time Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements CI update(Matt Nelson (Deactivated) ) DCO issues Release updates Work Updates Shanghai planning update Other Business Roadmap input for the new planning phase (Matt Nelson (Deactivated) ) Metrics Review - https://insights.lfx.linuxfoundation.org/projects/hyperledger%2Fbesu/dashboard;quicktime=time_filter_3Y Roadmap Review - Roadmap - roadmap pending proposal and discussion Open Forum - skipped Future Topics - skipped   File Modified Labels No labels Preview View File GMT20230117-160026_Recording.transcript.vtt Jan 17, 2023 by Ry Jones Labels No labels Preview View Text File GMT20230117-160026_RecordingnewChat.txt Jan 17, 2023 by Ry Jones Download All , multiple selections available, Related content More info Collapse 2024-07-09 Contributor Call 2024-07-09 Contributor Call Besu More like this 2024 - 05 - 28 2024 - 05 - 28 Hyperledger Identus More like this 2025-01-02 Weekly Meeting Agenda & Notes 2025-01-02 Weekly Meeting Agenda & Notes Hyperledger India Regional Chapter More like this 2024-12-19 Weekly Meeting Agenda & Notes 2024-12-19 Weekly Meeting Agenda & Notes Hyperledger India Regional Chapter More like this 2024-09-26 Weekly Meeting Agenda & Notes 2024-09-26 Weekly Meeting Agenda & Notes Hyperledger India Regional Chapter More like this 2024-09-19 Weekly Meeting Agenda & Notes 2024-09-19 Weekly Meeting Agenda & Notes Hyperledger India Regional Chapter More like this {serverDuration: 13, requestCorrelationId: 0483b432aab3428c8545d5c1874e5813} keywords: contributor; time cache: lfhyperledger-2023-01-17+Contributor+Call.html plain text: lfhyperledger-2023-01-17+Contributor+Call.txt item: #2104 of 3327 id: lfhyperledger-2023-01-31+Contributor+Call+-+AMEA+Reschedule author: lfhyperledger title: lfhyperledger-2023-01-31+Contributor+Call+-+AMEA+Reschedule date: None words: 797 flesch: 24 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked.   I.e. CSI, Swirld Labs, ETC Co-Op decide to pursue a grant as Besu project, then split the grant based on agreed-upon work share. keywords: apac; contributor; time cache: lfhyperledger-2023-01-31+Contributor+Call+-+AMEA+Reschedule.html plain text: lfhyperledger-2023-01-31+Contributor+Call+-+AMEA+Reschedule.txt item: #2105 of 3327 id: lfhyperledger-2023-01-31+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2023-01-31+Contributor+Call+-+APAC+Friendly+Time date: None words: 705 flesch: 19 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220621T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 5 pm Monday Los Angeles 8 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements /add item/ Roadmap Review  Besu Roadmap Release updates /add item/ Work Updates Java 17 WIP https://github.com/hyperledger/besu/pull/4977 - ready for review (required migration from RSA to EC keys in test cases) keywords: apac; contributor; time cache: lfhyperledger-2023-01-31+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2023-01-31+Contributor+Call+-+APAC+Friendly+Time.txt item: #2106 of 3327 id: lfhyperledger-2023-02-14+Contributor+Call author: lfhyperledger title: lfhyperledger-2023-02-14+Contributor+Call date: None words: 490 flesch: 2 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Feb 14, 2023 by Ry Jones (Meeting Link: â�¨https://zoom.us/j/97540031823?pwd=dEJrRW1LakFlWnZPelI3VGxoVjg2dz09) EMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220607T150000&p1=224&p2=179&p3=1440&p4=195&p5=47) 8 am Tuesday Los Angeles time 11 am Tuesday New York time 17h Tuesday Paris time Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements CI update(Matt Nelson (Deactivated) ) DCO issues Release updates Work Updates Shanghai planning update Other Business Roadmap input for the new planning phase (Matt Nelson (Deactivated) ) Metrics Review - https://insights.lfx.linuxfoundation.org/projects/hyperledger%2Fbesu/dashboard;quicktime=time_filter_3Y Roadmap Review - Roadmap - roadmap pending proposal and discussion Open Forum - skipped Future Topics - skipped Recording https://youtu.be/4L-Nhe-HgFA   File Modified Labels No labels Preview View Text File GMT20230214-155943_RecordingnewChat.txt Feb 14, 2023 by Ry Jones , multiple selections available, {serverDuration: 11, requestCorrelationId: 955c2f7328f64b6e950553c673f86522} keywords: contributor; time cache: lfhyperledger-2023-02-14+Contributor+Call.html plain text: lfhyperledger-2023-02-14+Contributor+Call.txt item: #2107 of 3327 id: lfhyperledger-2023-02-28+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2023-02-28+Contributor+Call+-+APAC+Friendly+Time date: None words: 741 flesch: 19 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220621T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 5 pm Monday Los Angeles 8 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements /add item/ Roadmap Review  Besu Roadmap Release updates Release Rotations 2023 23.1.1 proposed for March 8 - thoughts? Ideally would include Goerli Shanghai config No objections to March 8 release date Work Updates Shanghai Epic: https://github.com/hyperledger/besu/issues/4746 Ready for Sepolia and on track for mainnet Work started on EIP-6110: in-protocol deposits by external contributor https://github.com/hyperledger/besu/pull/5055 Appears to be done as part of the Ethereum Protocol Fellowship by Mikhail's mentee: https://hackmd.io/@doPpmyH4Ta-4Yc8pq3u-ZA/BkQKSAn2s Any reason not to include this on main using ExperimentEipsTime as a feature toggle? keywords: apac; contributor; time cache: lfhyperledger-2023-02-28+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2023-02-28+Contributor+Call+-+APAC+Friendly+Time.txt item: #2108 of 3327 id: lfhyperledger-2023-03-14+Contributor+Call author: lfhyperledger title: lfhyperledger-2023-03-14+Contributor+Call date: None words: 773 flesch: -2 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Contributor Call timing - Danno Ferrin requests to either move the meeting out an hour or two or to go to 8 hour meeting rotations, or even changing the days of the week. action team: Francesco Andreoli to move the meeting 1h later inversion of control / decoupling - discussion from Justin Florentine  PR coming in the next weeks Metrics Review - https://insights.lfx.linuxfoundation.org/projects/hyperledger%2Fbesu/dashboard;quicktime=time_filter_3Y Roadmap Review - Roadmap - roadmap pending proposal and discussion Open Forum - skipped Future Topics - skipped Recording https://youtu.be/drc4sKJSQzw   File Modified Labels No labels Preview View Text File GMT20230314-150034_RecordingnewChat.txt Mar 14, 2023 by Ry Jones , multiple selections available, Related content More info Collapse 2022-06-07 Contributor Call 2022-06-07 Contributor Call Besu More like this 2023-06-06 Contributor Call 2023-06-06 Contributor Call Besu More like this 2022-05-10 Contributor Call 2022-05-10 Contributor Call Besu More like this 2022-11-22 Contributor Call 2022-11-22 Contributor Call Besu More like this 2022-12-20 Contributor Call 2022-12-20 Contributor Call Besu More like this 2024-09-03 Contributor Call - US/EMEA 2024-09-03 Contributor Call - US/EMEA Besu More like this {serverDuration: 11, requestCorrelationId: 04d2adf396444223b8e1c0acc74385f4} keywords: apac; contributor; time cache: lfhyperledger-2023-03-14+Contributor+Call.html plain text: lfhyperledger-2023-03-14+Contributor+Call.txt item: #2109 of 3327 id: lfhyperledger-2023-03-28+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2023-03-28+Contributor+Call+-+APAC+Friendly+Time date: None words: 569 flesch: 5 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220621T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 5 pm Monday Los Angeles 8 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements /add item/ Roadmap Review  Besu Roadmap Release updates 23.1.2 released on 23rd March including Bonsai refactor RocksDB keywords: contributor; time cache: lfhyperledger-2023-03-28+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2023-03-28+Contributor+Call+-+APAC+Friendly+Time.txt item: #2110 of 3327 id: lfhyperledger-2023-04-11+Contributor+Call author: lfhyperledger title: lfhyperledger-2023-04-11+Contributor+Call date: None words: 605 flesch: 11 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Apr 13, 2023 by Ry Jones (Meeting Link: â�¨https://zoom.us/j/97540031823?pwd=dEJrRW1LakFlWnZPelI3VGxoVjg2dz09) EMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20230412T160000&p1=224&p2=179&p3=1440&p4=195&p5=47) 9 am Tuesday Los Angeles time 12 am Tuesday New York time 18h Tuesday Paris time Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements HL GitHub Runner limits (Gary Schulte ) - Consensys currently has a handful of EC2 instances augmenting the build load for amd64 and docker processes. keywords: apac; contributor; time cache: lfhyperledger-2023-04-11+Contributor+Call.html plain text: lfhyperledger-2023-04-11+Contributor+Call.txt item: #2111 of 3327 id: lfhyperledger-2023-04-25+Contributor+Call+-+APAC+Friendly+Time+-+CANCELLED author: lfhyperledger title: lfhyperledger-2023-04-25+Contributor+Call+-+APAC+Friendly+Time+-+CANCELLED date: None words: 431 flesch: 9 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220621T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 5 pm Monday Los Angeles 8 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Cancelled due to public holiday in Australia NO Agenda Recordings   File Modified No files shared here yet. , multiple selections available, {serverDuration: 35, requestCorrelationId: 5f3e3a259f08492481379b8e7a0ec97f} keywords: contributor cache: lfhyperledger-2023-04-25+Contributor+Call+-+APAC+Friendly+Time+-+CANCELLED.html plain text: lfhyperledger-2023-04-25+Contributor+Call+-+APAC+Friendly+Time+-+CANCELLED.txt item: #2112 of 3327 id: lfhyperledger-2023-05-09+Contributor+Call author: lfhyperledger title: lfhyperledger-2023-05-09+Contributor+Call date: None words: 490 flesch: 1 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Ry Jones Simon Dudley Owned by Matt Nelson (Deactivated) Last updated: May 10, 2023 by Ry JonesVersion comment (Meeting Link: â�¨https://zoom.us/j/97540031823?pwd=dEJrRW1LakFlWnZPelI3VGxoVjg2dz09) EMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20230412T160000&p1=224&p2=179&p3=1440&p4=195&p5=47) 9 am Tuesday Los Angeles time 12 am Tuesday New York time 18h Tuesday Paris time Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements Release updates  23.4.0 out with a host of changes for Mainnet  https://github.com/hyperledger/besu/releases/tag/23.4.0 Work Updates PR 5330 Other Business REPEAT: RFC - Proposal: Replace Quarterly and Bi-Weekly with Monthly Releases Rewritten as: Proposal: Avoid Cherry Picked Releases keywords: contributor; time cache: lfhyperledger-2023-05-09+Contributor+Call.html plain text: lfhyperledger-2023-05-09+Contributor+Call.txt item: #2113 of 3327 id: lfhyperledger-2023-05-23+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2023-05-23+Contributor+Call+-+APAC+Friendly+Time date: None words: 740 flesch: 13 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220621T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 5 pm Monday Los Angeles 8 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements /add item/ Roadmap Review  Besu Roadmap Release updates 23.4.0 - docker images updated https://discord.com/channels/905194001349627914/943252457063075880/1110073269131935755 23.4.1 - Overdue for the release 5330 might be blocking the release. keywords: apac; contributor; time cache: lfhyperledger-2023-05-23+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2023-05-23+Contributor+Call+-+APAC+Friendly+Time.txt item: #2114 of 3327 id: lfhyperledger-2023-06-06+Contributor+Call author: lfhyperledger title: lfhyperledger-2023-06-06+Contributor+Call date: None words: 699 flesch: 9 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. EMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20230412T160000&p1=224&p2=179&p3=1440&p4=195&p5=47) 9 am Tuesday Los Angeles time 12 am Tuesday New York time 18h Tuesday Paris time Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements Q2 Report due CIP update Release updates  23.4.1 released - txpool Tuweni release and org discussion Work Updates Discussion of consensus mechanism plug-ins/modularity → Miro → https://miro.com/app/board/uXjVMCPHPfg=/?share_link_id=795349574835 (Password: hyperledger) Modularity Review Technical documentation requests →  Trie-log shipping Plug-ins and new updates to the features EVM library  More Deprecation and future removal of the Forest world state pruning https://besu.hyperledger.org/en/stable/public-networks/reference/cli/options/#pruning-enabled Other Business REPEAT: RFC - Proposal: keywords: apac; contributor; time cache: lfhyperledger-2023-06-06+Contributor+Call.html plain text: lfhyperledger-2023-06-06+Contributor+Call.txt item: #2115 of 3327 id: lfhyperledger-2023-06-20+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2023-06-20+Contributor+Call+-+APAC+Friendly+Time date: None words: 837 flesch: 19 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Jun 20, 2023 by Ry JonesVersion comment (Meeting Link: â�¨https://zoom.us/j/91405289771?pwd=QzA3a0ozTjVSZ0hsYzgwTm9lVDRPQT09) APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220621T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 5 pm Monday Los Angeles 8 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements /add item/ Roadmap Review  Besu Roadmap Release updates 23.4.2 burning in issue with flat db - new burn-in (23.4.3) starting today issue with how PRs are reviewed and tested, especially big ones testing was done, then review, then refactoring → error was introduced after testing suggestion - do most  of the review before most  of the testing Work Updates 4844 - work is progressing well. keywords: apac; contributor; time cache: lfhyperledger-2023-06-20+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2023-06-20+Contributor+Call+-+APAC+Friendly+Time.txt item: #2116 of 3327 id: lfhyperledger-2023-07-11+Contributor+Call author: lfhyperledger title: lfhyperledger-2023-07-11+Contributor+Call date: None words: 912 flesch: -24 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Database version 0 - https://github.com/hyperledger/besu/pull/5681 ✅ GoQuorum Compatible Privacy - https://github.com/hyperledger/besu/pull/5607 Checker Framework  https://github.com/hyperledger/besu/pull/5536#discussion_r1247180442 Opening a PR against Danno's EVM performance work to see the state of the EVM with these changes later on → Justin F Other Business REPEAT: RFC - Proposal: Avoid Cherry-Picked Releases - added Suggested Deprecation Policy Metrics Review - https://insights.lfx.linuxfoundation.org/projects/hyperledger%2Fbesu/dashboard;quicktime=time_filter_3Y Open Forum Performance Testing with Caliper - Web3Labs IBFT/QBFT testing, performance is not that great Ameziane & Nischal → to collaborate on Discord, Ameziane to provide advice on set-up and tests and review some results  Block processing is done 3 times per block on QBFT networks → Ameziane POC https://github.com/ahamlat/besu/tree/cache-validation-block Future Topics Recording https://youtu.be/cYYXEp9NW7I 2023 07 11 Besu chat.txt 2023 07 11 Besu transcript.txt , multiple selections available, Related content More info Collapse 2023-01-17 Contributor Call 2023-01-17 Contributor Call Besu More like this 2023-05-09 Contributor Call 2023-05-09 Contributor Call Besu More like this 2023-02-14 Contributor Call 2023-02-14 Contributor Call Besu More like this 2022-06-07 Contributor Call 2022-06-07 Contributor Call Besu More like this 2023-06-06 Contributor Call 2023-06-06 Contributor Call Besu More like this 2022-08-02 Contributor Call 2022-08-02 Contributor Call Besu More like this {serverDuration: 12, requestCorrelationId: 300c3fe6a0ff40ad841fa6bcae8aece9} keywords: apac; besu; contributor; time cache: lfhyperledger-2023-07-11+Contributor+Call.html plain text: lfhyperledger-2023-07-11+Contributor+Call.txt item: #2117 of 3327 id: lfhyperledger-2023-07-18+Contributor+Call+-+APAC+Friendly+Time+-+CANCELLED author: lfhyperledger title: lfhyperledger-2023-07-18+Contributor+Call+-+APAC+Friendly+Time+-+CANCELLED date: None words: 422 flesch: 9 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220621T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 5 pm Monday Los Angeles 8 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Cancelled due to contributors attending EthCC No Agenda Recordings , multiple selections available, {serverDuration: 12, requestCorrelationId: 050e58ba9ce64aa0929e5db6b144ee44} keywords: contributor cache: lfhyperledger-2023-07-18+Contributor+Call+-+APAC+Friendly+Time+-+CANCELLED.html plain text: lfhyperledger-2023-07-18+Contributor+Call+-+APAC+Friendly+Time+-+CANCELLED.txt item: #2118 of 3327 id: lfhyperledger-2023-08-01+Contributor+Call author: lfhyperledger title: lfhyperledger-2023-08-01+Contributor+Call date: None words: 499 flesch: -2 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Aug 05, 2023 by Ry JonesVersion comment (Meeting Link: â�¨https://zoom.us/j/97540031823?pwd=dEJrRW1LakFlWnZPelI3VGxoVjg2dz09) EMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20230412T160000&p1=224&p2=179&p3=1440&p4=195&p5=47) 9 am Tuesday Los Angeles time 12 am Tuesday New York time 18h Tuesday Paris time Agenda Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements Q2 Report submitted - https://github.com/hyperledger/toc/pull/133 Release updates 23.4.4 - Bug fix release  23.7.0 - Upcoming (Burn-in Friday the 21st)  Discussion of consensus mechanism plug-ins/modularity Work UpdatesTechnical documentation requests  Other Business RFC - Proposal: Quarterly releases from main by default (Replacement/refinement of Proposal: Avoid Cherry-Picked Releases) Metrics Review - https://insights.lfx.linuxfoundation.org/projects/hyperledger%2Fbesu/dashboard;quicktime=time_filter_3Y Open Forum Future Topics Recording https://youtu.be/GhURMT5SILo 2023 08 01 Besu Contributor Call chat.txt 2023 08 01 Besu Contributor Call transcript.txt , multiple selections available, {serverDuration: 12, requestCorrelationId: fccad6e11fec40f0a628c0e817cdd569} keywords: contributor; time cache: lfhyperledger-2023-08-01+Contributor+Call.html plain text: lfhyperledger-2023-08-01+Contributor+Call.txt item: #2119 of 3327 id: lfhyperledger-2023-08-15+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2023-08-15+Contributor+Call+-+APAC+Friendly+Time date: None words: 529 flesch: 6 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220621T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 5 pm Monday Los Angeles 8 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements /add item/ Roadmap Review  Besu Roadmap Release updates 23.7.0 - Release was removed after performance regression on keccak hash 23.7.1 RC1 - Burn-in in progress Get status on burn-in from Discord Work Updates 4844 update Some hive tests failing Forkchoice V3 not yet implemented Danno has PR out for rename for blobGas to dataGas Currently running on devnet 7 EIp-4788 is needed for devnet-8. keywords: contributor; time cache: lfhyperledger-2023-08-15+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2023-08-15+Contributor+Call+-+APAC+Friendly+Time.txt item: #2120 of 3327 id: lfhyperledger-2023-09-05+Contributor+Call+-+EMEA+Friendly+Time author: lfhyperledger title: lfhyperledger-2023-09-05+Contributor+Call+-+EMEA+Friendly+Time date: None words: 582 flesch: -19 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Oct 07, 2023 by Simon Dudley (Meeting Link: â�¨https://zoom.us/j/97540031823?pwd=dEJrRW1LakFlWnZPelI3VGxoVjg2dz09) EMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20230412T160000&p1=224&p2=179&p3=1440&p4=195&p5=47) 9 am Tuesday Los Angeles time 12 am Tuesday New York time 18h Tuesday Paris time Agenda Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements Release updates 23.7.2 - Upcoming (Burn-in Friday the 28th)  Discussion of consensus mechanism plug-ins/modularity Work UpdatesTechnical documentation requests  Other Business Proposal: Discord Server Pub/Priv Channel Split Â  Enterprise Releases (https://docs.google.com/document/d/1oeI2fq3jBYFyQHj4kHb1OemAzI1L6DRudkEtZRSYabM/) RFC - Proposal: Quarterly releases from main by default (Replacement/refinement of Proposal: Avoid Cherry-Picked Releases) Metrics Review - https://insights.lfx.linuxfoundation.org/projects/hyperledger%2Fbesu/dashboard;quicktime=time_filter_3Y Open Forum Future Topics Recording , multiple selections available, Related content More info Collapse 2024-07-09 Contributor Call 2024-07-09 Contributor Call Besu More like this 2023-07-11 Contributor Call 2023-07-11 Contributor Call Besu More like this 2023-01-17 Contributor Call 2023-01-17 Contributor Call Besu More like this 2022-06-07 Contributor Call 2022-06-07 Contributor Call Besu More like this 2023-06-06 Contributor Call 2023-06-06 Contributor Call Besu More like this 2022-05-10 Contributor Call 2022-05-10 Contributor Call Besu More like this {serverDuration: 39, requestCorrelationId: 4205db9408fb4a42828d162cb1b8ce2a} keywords: contributor; time cache: lfhyperledger-2023-09-05+Contributor+Call+-+EMEA+Friendly+Time.html plain text: lfhyperledger-2023-09-05+Contributor+Call+-+EMEA+Friendly+Time.txt item: #2121 of 3327 id: lfhyperledger-2023-09-12+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2023-09-12+Contributor+Call+-+APAC+Friendly+Time date: None words: 706 flesch: 1 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Oct 07, 2023 by Simon Dudley (Meeting Link: â�¨https://zoom.us/j/91405289771?pwd=QzA3a0ozTjVSZ0hsYzgwTm9lVDRPQT09) APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220621T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 5 pm Monday Los Angeles 8 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements /add item/ Roadmap Review  Besu Roadmap Release updates 23.7.2 https://github.com/hyperledger/besu/releases/tag/23.7.2 first release of main in 6 weeks (23.7.1 was a cherry-pick) recommended for mainnet use holesky support NOTE docs release process change for docusaurus - requires a PR (not just a github release) 23.7.x series - trialling releasing from a release branch per - (RFC) Release Process (Incorporates both Proposal: keywords: apac; contributor; time cache: lfhyperledger-2023-09-12+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2023-09-12+Contributor+Call+-+APAC+Friendly+Time.txt item: #2122 of 3327 id: lfhyperledger-2023-10-02+Contributor+Call+-+AMEA+Friendly+Time author: lfhyperledger title: lfhyperledger-2023-10-02+Contributor+Call+-+AMEA+Friendly+Time date: None words: 1004 flesch: 18 summary: Discord thread: https://discord.com/channels/905194001349627914/943252457063075880/1153922976736104449 NOTES ON CALL: Good: Can merge to main Good squash/commit history Can easily abort release candidates that fail and does not create candidate docker images that users may pick up by accident  Bad: Different SHAs for cherry picks, more fraught history Need admin to disable branch protection rules for new release branches  Only Gary and Simon have used this release process  Human required process needs to identify which SHA commit we start the release from  Need work around automation and process itself  23.10.0 - Should take this into the automation realm → iterating on scripts for release automation  Fabio would like to try this process on next release  We will pilot this release process before making it official - perhaps in 24.1.0  23.7.3-RC release update from Ameziane - Memory usage investigations on 23.7.3-RC PLAN FROM CALL:  Check with Danno RE required release timeline for Swirld's Labs If needed within a week: cherry pick on 23.7.3 for a .4 release Otherwise, include in 23.10.0 and begin burn-in on Friday after code freeze  Enterprise Releases proposal - https://docs.google.com/document/d/1oeI2fq3jBYFyQHj4kHb1OemAzI1L6DRudkEtZRSYabM/  - NOTES BELOW:  Starting point → Release candidate is cut and socialized with ALL contributor groups  RCs can be tested within any organizations environment and with their own testing suite and then results are socialized Socializing RCs for parties in the #besu-release channel  Normal time-bound is Friday → Wed/Thurs of the following week  Agreement on results can pause a release → This is probably where we need the most consensus among maintainers Extension of acceptance tests for private / permissioned chains ? 2023-10-02 Contributor Call - AMEA Friendly Time - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: apac; contributor; release; time cache: lfhyperledger-2023-10-02+Contributor+Call+-+AMEA+Friendly+Time.html plain text: lfhyperledger-2023-10-02+Contributor+Call+-+AMEA+Friendly+Time.txt item: #2123 of 3327 id: lfhyperledger-2023-10-10+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2023-10-10+Contributor+Call+-+APAC+Friendly+Time date: None words: 672 flesch: 0 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220621T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 5 pm Monday Los Angeles 8 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements /add item/ Release updates 23.10.0-RC new burn-in for the 23.10.0 RC Work Updates /add item/ Other Business Call for help on tools for creating 4844 blob transactions for testing Usman will start a discussion in the Besu discord on this DEBUG Log Improvement Proposal - reminder about this one, looking for feedback. keywords: contributor; time cache: lfhyperledger-2023-10-10+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2023-10-10+Contributor+Call+-+APAC+Friendly+Time.txt item: #2124 of 3327 id: lfhyperledger-2023-10-31+Contributor+Call author: lfhyperledger title: lfhyperledger-2023-10-31+Contributor+Call date: None words: 694 flesch: -7 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Open Forum Renata Toktar - Presentation on Indy Feedback on Besu Verification keys → using Ethereum 1 keys with a huge amount of signatures (performance issue on EthSigner?)  Limits for amount of data in smart contracts Docs were really good for setting up the network  Spent some time developing specific scripts for local setup, making certain things configurable  Performance usage on big Objects in Besu  Load tests → will share results later on  Future Topics /add item/ Recordings Playlist: https://www.youtube.com/playlist?list=PL0MZ85B_96CHpqsKmljUK8HB98wK67RjC , multiple selections available, Related content More info Collapse 2022-10-25 Contributor Call 2022-10-25 Contributor Call Besu More like this 2025-03-18 Contributor Call 2025-03-18 Contributor Call Besu More like this 2019-10-01 Contributor call 2019-10-01 Contributor call Besu More like this 2024-09-03 Contributor Call - US/EMEA 2024-09-03 Contributor Call - US/EMEA Besu More like this 2020-09-29 Besu Contributor Call 2020-09-29 Besu Contributor Call Besu More like this 2022-09-13 Contributor Call - APAC 2022-09-13 Contributor Call - APAC Besu More like this {serverDuration: 12, requestCorrelationId: 0f7bd40a3dc64ae4890e60d3fd706964} keywords: apac; contributor; time cache: lfhyperledger-2023-10-31+Contributor+Call.html plain text: lfhyperledger-2023-10-31+Contributor+Call.txt item: #2125 of 3327 id: lfhyperledger-2023-11-07+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2023-11-07+Contributor+Call+-+APAC+Friendly+Time date: None words: 642 flesch: -20 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220621T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 5 pm Monday Los Angeles 8 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements A few of us are attending devconnect, please reach out on Discord if you would like to join us there Release updates Next release 23.10.2 Besu quite stable, good time to do a release before big changes are brought in Bring up discussion in the release channel Work Updates Snap sync server Besu to Besu is syncing well Geth and Nethermind not syncing well Focussing on getting Geth syncing working Upcoming database changes Storing code by code hash instead of account hash Will require running a subcommand to convert an existing database Fully flattened database Want to make the default Will have a conversion tool to convert to the new format After these changes along with snap sync, we will be able to move Besu to use Bonsai as the default/primary storage mechanism Matt Nelson has started discussions on private networks using Bonsai Investigation on trie logs using blob DB Confirming expecting performance improvements Possible we could have a single subcommand to database upgrade the database Other Business (From Simon) Have marked the debug proposal as ACCEPTED and incorporated into Coding Conventions#Logging Open Forum /add item/ Future Topics /add item/ Recordings Playlist: https://www.youtube.com/playlist?list=PL0MZ85B_96CHpqsKmljUK8HB98wK67RjC   File Modified No files shared here yet. , multiple selections available, {serverDuration: 33, requestCorrelationId: e7022ec6ca49424893c363cc47d6b69a} keywords: contributor; time cache: lfhyperledger-2023-11-07+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2023-11-07+Contributor+Call+-+APAC+Friendly+Time.txt item: #2126 of 3327 id: lfhyperledger-2023-11-28+Contributor+Call author: lfhyperledger title: lfhyperledger-2023-11-28+Contributor+Call date: None words: 509 flesch: 14 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Permissioned?  Sequential vs layered Using profiles - we can bundle in default pools with the work around Besu profiles to set sensible defaults. keywords: contributor; time cache: lfhyperledger-2023-11-28+Contributor+Call.html plain text: lfhyperledger-2023-11-28+Contributor+Call.txt item: #2127 of 3327 id: lfhyperledger-2023-12-05+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2023-12-05+Contributor+Call+-+APAC+Friendly+Time date: None words: 514 flesch: 19 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-04-11 Contributor Call 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2023-07-11 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-08-01 Contributor Call 2023-08-15 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-12-05 Contributor Call - APAC Friendly Time 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220621T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 5 pm Monday Los Angeles 8 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements CICD changes - WIP migration from Circle CI to GHA https://github.com/hyperledger/besu/pull/6214 Next scheduled APAC timezone call (2nd Jan) is cancelled for holidays. keywords: contributor; time cache: lfhyperledger-2023-12-05+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2023-12-05+Contributor+Call+-+APAC+Friendly+Time.txt item: #2128 of 3327 id: lfhyperledger-2024+-+Besu+Performance+Improvements+since+the+Merge author: lfhyperledger title: lfhyperledger-2024+-+Besu+Performance+Improvements+since+the+Merge date: None words: 3469 flesch: 51 summary: Besu performance improvements  Since the merge in September 2022, we've been committed to improving Besu's block processing performance, following a significant number of user reports about missing attestations on their validators. While these cases are not typical in mainnet use (otherwise we would have seen them before) they could easily be used as an attack to slow down Besu nodes and in extreme cases stall networks. keywords: besu; block; database; improvements; memory; operations; performance; processing; time cache: lfhyperledger-2024+-+Besu+Performance+Improvements+since+the+Merge.html plain text: lfhyperledger-2024+-+Besu+Performance+Improvements+since+the+Merge.txt item: #2129 of 3327 id: lfhyperledger-2024+Agendas author: lfhyperledger title: lfhyperledger-2024+Agendas date: None words: 458 flesch: 14 summary: Close Besu / 2024 Agendas More actions 2024 Agendas Sally MacFarlane Owned by Sally MacFarlane Last updated: Jan 02, 2024 2024-11-26 Contributor Call - US/AMEA 2024-09-03 Contributor Call - US/EMEA 2024-07-09 Contributor Call 2024-06-11 Contributor Call - US/EMEA 2024-04-16 Contributor Call - US/EMEA Friendly Time 2024-03-26 Contributor Call - APAC Friendly Time 2024-03-19 Contributor Call - US/EMEA Friendly Time 2024-02-27 Contributor Call - APAC Friendly Time 2024-02-20 Contributor Call - US/EMEA Friendly Time 2024-01-30 Contributor Call - APAC Friendly Time 2024-01-23 Contributor Call - AMEA Friendly Time 2024-01-02 Contributor Call - APAC Friendly Time - CANCELLED , multiple selections available, Related content More info Collapse 2024 Meeting Agenda and Notes 2024 Meeting Agenda and Notes Healthcare SIG More like this 2022 Meeting Agenda and Notes 2022 Meeting Agenda and Notes Healthcare SIG More like this 2021-05-26 Meeting Agenda 2021-05-26 Meeting Agenda Hyperledger Ursa (EOL) Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2024-01-02 Contributor Call - APAC Friendly Time - CANCELLED 2024-01-23 Contributor Call - AMEA Friendly Time 2024-01-30 Contributor Call - APAC Friendly Time 2024-02-20 Contributor Call - US/EMEA Friendly Time 2024-02-27 Contributor Call - APAC Friendly Time 2024-03-19 Contributor Call - US/EMEA Friendly Time 2024-03-26 Contributor Call - APAC Friendly Time 2024-04-16 Contributor Call - US/EMEA Friendly Time 2024-06-11 Contributor Call - US/EMEA 2024-07-09 Contributor Call 2024-09-03 Contributor Call - US/EMEA 2024-11-26 Contributor Call - US/AMEA 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: contributor cache: lfhyperledger-2024+Agendas.html plain text: lfhyperledger-2024+Agendas.txt item: #2130 of 3327 id: lfhyperledger-2024-01-02+Contributor+Call+-+APAC+Friendly+Time+-+CANCELLED author: lfhyperledger title: lfhyperledger-2024-01-02+Contributor+Call+-+APAC+Friendly+Time+-+CANCELLED date: None words: 440 flesch: 2 summary: Close Besu / 2024-01-02 Contributor Call - APAC Friendly Time - CANCELLED More actions 2024-01-02 Contributor Call - APAC Friendly Time - CANCELLED Sally MacFarlane Owned by Sally MacFarlane Dec 17, 2023 (Meeting Link: â�¨https://zoom.us/j/91405289771?pwd=QzA3a0ozTjVSZ0hsYzgwTm9lVDRPQT09) APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220621T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 5 pm Monday Los Angeles 8 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  APAC meeting cancelled for January   Recordings   File Modified No files shared here yet. , multiple selections available, Related content More info Collapse 2024-07-09 Contributor Call 2024-07-09 Contributor Call Besu More like this 2024-09-03 Contributor Call - US/EMEA 2024-09-03 Contributor Call - US/EMEA Besu More like this 2024-11-26 Contributor Call - US/AMEA 2024-11-26 Contributor Call - US/AMEA Besu More like this 2025-02-05 Meeting notes 2025-02-05 Meeting notes Web3j More like this 2025-02-19 Meeting notes 2025-02-19 Meeting notes Web3j More like this 2025-04-02 Meeting notes 2025-04-02 Meeting notes Web3j More like this {serverDuration: 14, requestCorrelationId: 5420eba4d106438f8164ceebe3ad5f6e} Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2024-01-02 Contributor Call - APAC Friendly Time - CANCELLED 2024-01-23 Contributor Call - AMEA Friendly Time 2024-01-30 Contributor Call - APAC Friendly Time 2024-02-20 Contributor Call - US/EMEA Friendly Time 2024-02-27 Contributor Call - APAC Friendly Time 2024-03-19 Contributor Call - US/EMEA Friendly Time 2024-03-26 Contributor Call - APAC Friendly Time 2024-04-16 Contributor Call - US/EMEA Friendly Time 2024-06-11 Contributor Call - US/EMEA 2024-07-09 Contributor Call 2024-09-03 Contributor Call - US/EMEA 2024-11-26 Contributor Call - US/AMEA 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: contributor; time cache: lfhyperledger-2024-01-02+Contributor+Call+-+APAC+Friendly+Time+-+CANCELLED.html plain text: lfhyperledger-2024-01-02+Contributor+Call+-+APAC+Friendly+Time+-+CANCELLED.txt item: #2131 of 3327 id: lfhyperledger-2024-01-06+Mainnet+Halting+Event author: lfhyperledger title: lfhyperledger-2024-01-06+Mainnet+Halting+Event date: None words: 1989 flesch: 65 summary: The community support from Besu users was really outstanding - sophisticated users and devs from other projects were helping troubleshoot and to get other users back online (shoutout to the Nethermind team for help in tracing the problematic block).    We were still trying to figure out what happened and why users on the latest version of Besu, 23.10.3, were affected. Last updated: Jun 12, 2024 by Sally MacFarlane Executive Summary: On January 6th, 2024 at block 18947893, an estimated 70% of Besu nodes on Mainnet experienced a halt. keywords: besu; block; mainnet; state cache: lfhyperledger-2024-01-06+Mainnet+Halting+Event.html plain text: lfhyperledger-2024-01-06+Mainnet+Halting+Event.txt item: #2132 of 3327 id: lfhyperledger-2024-01-23+Contributor+Call+-+AMEA+Friendly+Time author: lfhyperledger title: lfhyperledger-2024-01-23+Contributor+Call+-+AMEA+Friendly+Time date: None words: 714 flesch: 31 summary: Close Besu / 2024-01-23 Contributor Call - AMEA Friendly Time More actions 2024-01-23 Contributor Call - AMEA Friendly Time Justin Florentine Matt Nelson (Deactivated) Owned by Justin Florentine Last updated: Jan 23, 2024 by Matt Nelson (Deactivated) (Meeting Link: â�¨https://zoom.us/j/91405289771?pwd=QzA3a0ozTjVSZ0hsYzgwTm9lVDRPQT09) AMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20230123T170000&p1=224&p2=179&p3=1440&p4=195&p5=47) San Francisco, USA     Mon, Jan 23, 2023 at 9:00 am PST New York, USA          Mon, Jan 23, 2023 at 12:00 noon EST UTC, Time Zone         Mon, Jan 23, 2023 at 5:00 pm  Paris, France          Mon, Jan 23, 2023 at 6:00 pm CET Brisbane, Australia    Tue, Jan 24, 2023 at 3:00 am AEST Agenda  Migration from Circle CI to Github Actions. Performance  2024 - Besu Performance Improvements since the Merge Prague Planning Matt to create and outline a document for Besu team Prague scope opinions. keywords: contributor; time cache: lfhyperledger-2024-01-23+Contributor+Call+-+AMEA+Friendly+Time.html plain text: lfhyperledger-2024-01-23+Contributor+Call+-+AMEA+Friendly+Time.txt item: #2133 of 3327 id: lfhyperledger-2024-01-30+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2024-01-30+Contributor+Call+-+APAC+Friendly+Time date: None words: 697 flesch: 27 summary: APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220621T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 5 pm Monday Los Angeles 8 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless you are speaking If you have a question use the raise hand feature General Announcements Dencun on Sepolia on the 30th 2024-01-30 22:51:12 UTC. Limit Trie Logs  https://github.com/hyperledger/besu/issues/5390 Snap sync to finally become officially production-ready (has been our recommended default for some time) https://github.com/hyperledger/besu/pull/6405 The first change is to rename X_SNAP → SNAP and X_CHECKPOINT → CHECKPOINT Follow on work to create profiles for changing default Change to Besu Defaults - Q1 2024 Other Business /add item/ Open Forum /add item/ Future Topics /add item/ Recordings Find the recording in the playlist - https://www.youtube.com/playlist?list=PL0MZ85B_96CHpqsKmljUK8HB98wK67RjC   File Modified No files shared here yet. , multiple selections available, Related content More info Collapse 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-31 Contributor Call - APAC Friendly Time Besu More like this 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-28 Contributor Call - APAC Friendly Time Besu More like this 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-28 Contributor Call - APAC Friendly Time Besu More like this 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-20 Contributor Call - APAC Friendly Time Besu More like this 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-23 Contributor Call - APAC Friendly Time Besu More like this 2023-12-05 Contributor Call - APAC Friendly Time 2023-12-05 Contributor Call - APAC Friendly Time Besu More like this {serverDuration: 20, requestCorrelationId: 7155e342cd45423286d12e4d1679b7df} keywords: apac; contributor; time cache: lfhyperledger-2024-01-30+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2024-01-30+Contributor+Call+-+APAC+Friendly+Time.txt item: #2134 of 3327 id: lfhyperledger-2024-02-20+Contributor+Call+-+US+EMEA+Friendly+Time author: lfhyperledger title: lfhyperledger-2024-02-20+Contributor+Call+-+US+EMEA+Friendly+Time date: None words: 554 flesch: 17 summary: EMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220607T150000&p1=224&p2=179&p3=1440&p4=195&p5=47) 8 am Tuesday Los Angeles time 11 am Tuesday New York time 17h Tuesday Paris time Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements Roadmap Review  Besu Roadmap & Planning Release updates 24.1.1 - Maintenance update & Mainnet configs Released simultaneously GHA and CircleCI –> Circle CI as primary   24.2.0  GHA  Next release to be run with GHA as primary, and CircleCI as backup Testing quarantine procedures  CI/CD Migration → Source of truth document (open to suggestions and feedback)  Work Updates Enterprise-oriented testing (Testing) Bottom of page Sally MacFarlane  Should we consider a new repository to avoid creating headaches for modularity (besu-test)?  Acceptance testing  SonarQube quality gates?  Downgrade protection (https://github.com/hyperledger/besu/pull/6307) Could be made more robust in the future as capability based  Plug-in API → updates & CTAs  Contact Matt Nelson (Deactivated) with any and all feedback  Open Forum GDPR & Event / state based architecture Need GDPR compliance in Besu for DIDs - DID, Meta-data, pub keys   State we can clear values Events can we clear values?  Could we use blob space and KZG commitments? PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: contributor; emea; time cache: lfhyperledger-2024-02-20+Contributor+Call+-+US+EMEA+Friendly+Time.html plain text: lfhyperledger-2024-02-20+Contributor+Call+-+US+EMEA+Friendly+Time.txt item: #2135 of 3327 id: lfhyperledger-2024-02-27+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2024-02-27+Contributor+Call+-+APAC+Friendly+Time date: None words: 512 flesch: 19 summary: APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220621T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 5 pm Monday Los Angeles 8 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements /add item/ Roadmap Review  Besu Roadmap Release updates 24.2.0-RC2 is burning in - looking good Includes Limit Trie Logs for Bonsai SNAP and BONSAI will now be the defaults Shifted to monthly calver (not quarterly) need to be mindful that we still give users sufficient notice (aiming for 3 months, depending on severity of breakage) for breaking changes have added upcoming breaking changes section to changelog for this purpose Work Updates /add item/ Other Business Review CI credit usage and build time for the month https://app.circleci.com/insights/gh/hyperledger TODO - is there an equivalent overview for GHA cc Justin Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2024-01-02 Contributor Call - APAC Friendly Time - CANCELLED 2024-01-23 Contributor Call - AMEA Friendly Time 2024-01-30 Contributor Call - APAC Friendly Time 2024-02-20 Contributor Call - US/EMEA Friendly Time 2024-02-27 Contributor Call - APAC Friendly Time 2024-03-19 Contributor Call - US/EMEA Friendly Time 2024-03-26 Contributor Call - APAC Friendly Time 2024-04-16 Contributor Call - US/EMEA Friendly Time 2024-06-11 Contributor Call - US/EMEA 2024-07-09 Contributor Call 2024-09-03 Contributor Call - US/EMEA 2024-11-26 Contributor Call - US/AMEA 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: contributor; time cache: lfhyperledger-2024-02-27+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2024-02-27+Contributor+Call+-+APAC+Friendly+Time.txt item: #2136 of 3327 id: lfhyperledger-2024-03-26+Contributor+Call+-+APAC+Friendly+Time author: lfhyperledger title: lfhyperledger-2024-03-26+Contributor+Call+-+APAC+Friendly+Time date: None words: 584 flesch: -34 summary: Close Besu / 2024-03-26 Contributor Call - APAC Friendly Time More actions 2024-03-26 Contributor Call - APAC Friendly Time Simon Dudley Sally MacFarlane Jason Frame Lucas Saldanha Owned by Simon Dudley Last updated: Mar 25, 2024 (Meeting Link: â�¨https://zoom.us/j/91405289771?pwd=QzA3a0ozTjVSZ0hsYzgwTm9lVDRPQT09) APAC Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220621T010000&p1=224&p2=179&p3=1440&p4=195&p5=47) 5 pm Monday Los Angeles 8 pm Monday New York 1 am  Tuesday UTC 3 am Tuesday Paris/Berlin 11 am Tuesday Brisbane Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements /add item/ Roadmap Review  Besu Roadmap Release updates 24.3.0 24.3.1? waiting on completion of snap server https://github.com/hyperledger/besu/pull/6640 Develop tag updated every commit https://github.com/hyperledger/besu/releases/tag/develop No longer publishing docker every commit https://hub.docker.com/r/hyperledger/besu/tags remove develop  tag or start publishing it again - Sally to follow up New format for build version (replaces gradle.propertes) https://github.com/hyperledger/besu/pull/6699 Artifactory publish re-added to support besu as a library https://github.com/hyperledger/besu/pull/6746 Work Updates Post-dencun peering issues https://github.com/hyperledger/besu/issues/6805 error prone refactored out into standalone repo https://github.com/hyperledger/besu/pull/6692 storage improvement for receipts, reducing synced node size by ~78GB on mainnet with snap sync https://github.com/hyperledger/besu/pull/6602  Other Business /add item/ Open Forum EIP-7002 (https://github.com/hyperledger/besu/issues/6800) TODO Besu team to find someone for Lucas to pair with Future Topics /add item/ Recordings Find the recording in the playlist - https://www.youtube.com/playlist?list=PL0MZ85B_96CHpqsKmljUK8HB98wK67RjC   File Modified No files shared here yet. , multiple selections available, Related content More info Collapse 2025-03-18 Contributor Call 2025-03-18 Contributor Call Besu More like this 2024-07-09 Contributor Call 2024-07-09 Contributor Call Besu More like this 2024-09-03 Contributor Call - US/EMEA 2024-09-03 Contributor Call - US/EMEA Besu More like this 2025-02-05 Meeting notes 2025-02-05 Meeting notes Web3j More like this 2025-02-19 Meeting notes 2025-02-19 Meeting notes Web3j More like this 2025-03-19 Meeting notes 2025-03-19 Meeting notes Web3j More like this {serverDuration: 11, requestCorrelationId: 362a210fba71483a9147f108b662e465} 2024-03-26 Contributor Call - APAC Friendly Time - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: apac; contributor; time cache: lfhyperledger-2024-03-26+Contributor+Call+-+APAC+Friendly+Time.html plain text: lfhyperledger-2024-03-26+Contributor+Call+-+APAC+Friendly+Time.txt item: #2137 of 3327 id: lfhyperledger-2024-04-16+Contributor+Call+-+US+EMEA+Friendly+Time author: lfhyperledger title: lfhyperledger-2024-04-16+Contributor+Call+-+US+EMEA+Friendly+Time date: None words: 428 flesch: 12 summary: Apr 16, 2024 by Matthew Whitehead (Meeting Link: â�¨https://zoom.us/j/97540031823?pwd=dEJrRW1LakFlWnZPelI3VGxoVjg2dz09) EMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220607T150000&p1=224&p2=179&p3=1440&p4=195&p5=47) 9 am Tuesday Los Angeles time 12 pm Tuesday New York time 17h Tuesday Paris time Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements /add item/ Roadmap Review  Besu Roadmap Empty block period WIP progress Release updates /add item/ Work Updates /add item/ Other Business Review CI credit usage and build time for the month https://app.circleci.com/insights/gh/hyperledger /add item/ Open Forum QBFT, Bonsai, + Snap Server testing QBFT/IBFT soak test progress QBFT recovery after an outage Future Topics /add item/ Recordings Find the recording in the playlist - https://www.youtube.com/playlist?list=PL0MZ85B_96CHpqsKmljUK8HB98wK67RjC   File Modified No files shared here yet. , multiple selections available, {serverDuration: 10, requestCorrelationId: 717578afdb4540eba3a272a77a588d92} Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2024-01-02 Contributor Call - APAC Friendly Time - CANCELLED 2024-01-23 Contributor Call - AMEA Friendly Time 2024-01-30 Contributor Call - APAC Friendly Time 2024-02-20 Contributor Call - US/EMEA Friendly Time 2024-02-27 Contributor Call - APAC Friendly Time 2024-03-19 Contributor Call - US/EMEA Friendly Time 2024-03-26 Contributor Call - APAC Friendly Time 2024-04-16 Contributor Call - US/EMEA Friendly Time 2024-06-11 Contributor Call - US/EMEA 2024-07-09 Contributor Call 2024-09-03 Contributor Call - US/EMEA 2024-11-26 Contributor Call - US/AMEA 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: contributor; time cache: lfhyperledger-2024-04-16+Contributor+Call+-+US+EMEA+Friendly+Time.html plain text: lfhyperledger-2024-04-16+Contributor+Call+-+US+EMEA+Friendly+Time.txt item: #2138 of 3327 id: lfhyperledger-2024-06-11+Contributor+Call+-+US+EMEA author: lfhyperledger title: lfhyperledger-2024-06-11+Contributor+Call+-+US+EMEA date: None words: 605 flesch: 24 summary: Last updated: Jun 11, 2024 (Meeting Link: â�¨https://zoom.us/j/97540031823?pwd=dEJrRW1LakFlWnZPelI3VGxoVjg2dz09) EMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220607T150000&p1=224&p2=179&p3=1440&p4=195&p5=47) 8 am Tuesday Los Angeles time 11 am Tuesday New York time 17h Tuesday Paris time Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature Release updates / issues  24.6.0 in burn-in phase for release  Besu-Native (Gary and Matt Whitehead on action items)  Some workarounds for current issues with release and local build. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: contributor; emea; time cache: lfhyperledger-2024-06-11+Contributor+Call+-+US+EMEA.html plain text: lfhyperledger-2024-06-11+Contributor+Call+-+US+EMEA.txt item: #2139 of 3327 id: lfhyperledger-2024-07-09+Contributor+Call author: lfhyperledger title: lfhyperledger-2024-07-09+Contributor+Call date: None words: 510 flesch: -4 summary: Last updated: Jul 09, 2024 Matt N Note - I will edit the call minutes when I have the recording... (Meeting Link: â�¨https://zoom.us/j/97540031823?pwd=dEJrRW1LakFlWnZPelI3VGxoVjg2dz09) EMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220607T150000&p1=224&p2=179&p3=1440&p4=195&p5=47) 8 am Tuesday Los Angeles time 11 am Tuesday New York time 17h Tuesday Paris time Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements Sunset Announcement blog and discussion Roadmap Review  Besu Roadmap Release updates 24.7.0 burn-in complete, release tomorrow  Work Updates /add item/ Other Business Review CI credit usage and build time for the month https://app.circleci.com/insights/gh/hyperledger /add item/ Open Forum /add item/ Future Topics /add item/ Recordings Find the recording in the playlist - https://www.youtube.com/playlist?list=PL0MZ85B_96CHpqsKmljUK8HB98wK67RjC   File Modified No files shared here yet. , multiple selections available, Related content More info Collapse 2023-06-06 Contributor Call 2023-06-06 Contributor Call Besu More like this 2022-03-15 Contributor Call 2022-03-15 Contributor Call Besu More like this 2020-09-15 Contributor Call 2020-09-15 Contributor Call Besu More like this 2022-10-25 Contributor Call 2022-10-25 Contributor Call Besu More like this 2022-11-22 Contributor Call 2022-11-22 Contributor Call Besu More like this 2024-03-19 Contributor Call - US/EMEA Friendly Time 2024-03-19 Contributor Call - US/EMEA Friendly Time Besu More like this {serverDuration: 40, requestCorrelationId: b79a4b431e124adab96a2713dbcd0d5d} PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: contributor; time cache: lfhyperledger-2024-07-09+Contributor+Call.html plain text: lfhyperledger-2024-07-09+Contributor+Call.txt item: #2140 of 3327 id: lfhyperledger-2024-09-03+Contributor+Call+-+US+EMEA author: lfhyperledger title: lfhyperledger-2024-09-03+Contributor+Call+-+US+EMEA date: None words: 661 flesch: 25 summary: EMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220607T150000&p1=224&p2=179&p3=1440&p4=195&p5=47) 8 am Tuesday Los Angeles time 11 am Tuesday New York time 17h Tuesday Paris time Agenda  Housekeeping Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/ This meeting is being recorded Please Mute unless speaking If you have a question use the raise hand feature General Announcements Matt Whitehead permissions in Github unable to assign tickets - Matt to check with Sally on permissions  Matt Whitehead provided an update on the Bonsai Archive solution developed  Basic support first that the team wants to use to gather data on storage versus latency trade-offs in the checkpointing strategy.   Indy on Besu Meetup - September 24th Discussed naming change - maintainers want clarity on the mechanics of removing the Hyperledger name from the actual code-bases and namespaces. keywords: contributor; emea; time cache: lfhyperledger-2024-09-03+Contributor+Call+-+US+EMEA.html plain text: lfhyperledger-2024-09-03+Contributor+Call+-+US+EMEA.txt item: #2141 of 3327 id: lfhyperledger-2024-11-26+Contributor+Call+-+US+AMEA author: lfhyperledger title: lfhyperledger-2024-11-26+Contributor+Call+-+US+AMEA date: None words: 609 flesch: 36 summary: Open Forum /add item/ Future Topics /add item/ Recordings Find the recording in the playlist - Besu Contributor Calls , multiple selections available, Related content More info Collapse 2024-09-03 Contributor Call - US/EMEA 2024-09-03 Contributor Call - US/EMEA Besu More like this 2022-11-22 Contributor Call 2022-11-22 Contributor Call Besu More like this 2023-03-14 Contributor Call 2023-03-14 Contributor Call Besu More like this 2022-01-20 Besu Contributor Call 2022-01-20 Besu Contributor Call Besu More like this 2020-03-31 Besu Contributor Call 2020-03-31 Besu Contributor Call Besu More like this 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-11 Contributor Call - APAC Friendly Time Besu More like this Atlassian Intelligence {serverDuration: 11, requestCorrelationId: 802bbac7d0ce4352bc5dcb72e153cd0c} EMEA Friendly Time (Time Zone Converter – Time Difference Calculator ) 8 am Tuesday Los Angeles time 11 am Tuesday New York time 17h keywords: besu; contributor; time cache: lfhyperledger-2024-11-26+Contributor+Call+-+US+AMEA.html plain text: lfhyperledger-2024-11-26+Contributor+Call+-+US+AMEA.txt item: #2142 of 3327 id: lfhyperledger-2025+Agendas author: lfhyperledger title: lfhyperledger-2025+Agendas date: None words: 287 flesch: 34 summary: Close Besu / 2025 Agendas More actions 2025 Agendas Justin Florentine Ry Jones Owned by Justin Florentine Last updated: Apr 15, 2025 by Ry Jones , multiple selections available, Related content More info Collapse 2024 Meeting Agenda and Notes 2024 Meeting Agenda and Notes Healthcare SIG More like this 2022 Meeting Agenda and Notes 2022 Meeting Agenda and Notes Healthcare SIG More like this 2021-05-26 Meeting Agenda 2021-05-26 Meeting Agenda Hyperledger Ursa (EOL) Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2023 Agendas 2024 Agendas 2025 Agendas 2025-03-18 Contributor Call 2025-04-15 Contributor Call Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: agendas cache: lfhyperledger-2025+Agendas.html plain text: lfhyperledger-2025+Agendas.txt item: #2143 of 3327 id: lfhyperledger-2025-03-18+Contributor+Call author: lfhyperledger title: lfhyperledger-2025-03-18+Contributor+Call date: None words: 522 flesch: 37 summary: Update on items & progress (privacy, PoW, fastsync) Misc enterprise updates (Matt W/Bhanu) Quorum IBFT → Besu QBFT migration History expiry for BFT chains Project infrastructure Documentation tooling: Making use of Docusaurus and Vercel instead of GH pages Reducing noise on Discord: Thoughts on replacing the general Besu channel with “besu-questions-mainnetâ€� and “besu-questions-permissionedâ€� so that maintainers focused on mainnet don’t get questions about permissioned Besu and vice versa Community calls and getting the recordings on YouTube: Confirming about recent calendar changes with the LFDT migration and discussing how recordings get posted to YouTube Future plans for developer docs in this wiki. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: agendas; besu; contributor cache: lfhyperledger-2025-03-18+Contributor+Call.html plain text: lfhyperledger-2025-03-18+Contributor+Call.txt item: #2144 of 3327 id: lfhyperledger-2025-04-15+Contributor+Call author: lfhyperledger title: lfhyperledger-2025-04-15+Contributor+Call date: None words: 395 flesch: 28 summary: PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. Project Charter - work is proceeding through legal, will be available for all maintainers to review shortly. , multiple selections available, Related content More info Collapse 2020-07-07 Contributor Call 2020-07-07 Contributor Call Besu More like this 2020-03-31 Besu Contributor Call 2020-03-31 Besu Contributor Call Besu More like this 2020-12-02-B Aries Working Group Call (US afternoon) 2020-12-02-B Aries Working Group Call (US afternoon) Hyperledger Aries More like this 2020-06-22 Meeting Notes 2020-06-22 Meeting Notes Hyperledger Cacti More like this 2020-12-01 Meeting notes 2020-12-01 Meeting notes Hyperledger Cacti More like this 2020-12-08 Meeting notes 2020-12-08 Meeting notes Hyperledger Cacti More like this Atlassian Intelligence {serverDuration: 12, requestCorrelationId: 039fde124e2a494f9c3f7111ed4cf73e} keywords: agendas; contributor cache: lfhyperledger-2025-04-15+Contributor+Call.html plain text: lfhyperledger-2025-04-15+Contributor+Call.txt item: #2145 of 3327 id: lfhyperledger-ACCEPTED+DEBUG+Log+Improvement+Proposal author: lfhyperledger title: lfhyperledger-ACCEPTED+DEBUG+Log+Improvement+Proposal date: None words: 493 flesch: 25 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) GitHub Merge Queue [ACCEPTED] DEBUG Log Improvement Proposal Checklist for reporting privacy issues Shandong Testnet Using Postman with Besu Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; debug; proposal cache: lfhyperledger-ACCEPTED+DEBUG+Log+Improvement+Proposal.html plain text: lfhyperledger-ACCEPTED+DEBUG+Log+Improvement+Proposal.txt item: #2146 of 3327 id: lfhyperledger-Advanced author: lfhyperledger title: lfhyperledger-Advanced date: None words: 289 flesch: 23 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Plugin Services Tools we use Advanced Fixing DCO on main/release Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: standards cache: lfhyperledger-Advanced.html plain text: lfhyperledger-Advanced.txt item: #2147 of 3327 id: lfhyperledger-Agendas author: lfhyperledger title: lfhyperledger-Agendas date: None words: 443 flesch: 38 summary: APAC friendly calls are at 0100 UTC (or 9am Beijing, 10am Tokyo, 11am Brisbane, 8pm -1d San Francisco)  EMEA friendly calls are at 1500UTC (or 4pm Paris/Berlin, 10am New York) APAC calls start on 17 Sep and will be every 4 weeks (unless modified for holidays) EMEA calls start on 1 Oct and will be every 4 weeks (unless modified for holidays) Close Besu / Agendas More actions Agendas Danno Ferrin Brett Henderson Owned by Danno Ferrin Last updated: Apr 13, 2020 Contributor Calls Contributor calls are bi-weekly and alternate between an APAC friendly and an EMEA friendly time. keywords: agendas; contributor cache: lfhyperledger-Agendas.html plain text: lfhyperledger-Agendas.txt item: #2148 of 3327 id: lfhyperledger-Archive author: lfhyperledger title: lfhyperledger-Archive date: None words: 360 flesch: 15 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Release Rotations 2024 Using CalVer for Besu Releases How to do a Besu Release Off-cycle release process Release Process Obsolete Proposals and Policies Archive Critical Issue for Privacy Users Mainnet Consensus Bug Identified and Resolved in Hyperledger Besu Release 22.1.0 Release Process Improvement Release Remediation Release Rotations 2021 Release Rotations 2022 Release Rotations 2023 Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; release cache: lfhyperledger-Archive.html plain text: lfhyperledger-Archive.txt item: #2149 of 3327 id: lfhyperledger-Archive+Dev author: lfhyperledger title: lfhyperledger-Archive+Dev date: None words: 226 flesch: 26 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) GitHub Merge Queue [ACCEPTED] DEBUG Log Improvement Proposal Checklist for reporting privacy issues Shandong Testnet Using Postman with Besu Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: archive; besu cache: lfhyperledger-Archive+Dev.html plain text: lfhyperledger-Archive+Dev.txt item: #2150 of 3327 id: lfhyperledger-Audits author: lfhyperledger title: lfhyperledger-Audits date: None words: 234 flesch: 35 summary: More like this Audits Audits Hyperledger Cello More like this Audits Audits Hyperledger Iroha More like this Audits Audits Hyperledger Ursa (EOL) More like this Audits Audits Hyperledger Indy More like this Audits Audits Hyperledger Grid (EOL) More like this {serverDuration: 15, requestCorrelationId: a63b3f998e844846bba4b4cdfe2f4d85} PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: audits; hyperledger cache: lfhyperledger-Audits.html plain text: lfhyperledger-Audits.txt item: #2151 of 3327 id: lfhyperledger-Besu+-+Community+Support author: lfhyperledger title: lfhyperledger-Besu+-+Community+Support date: None words: 549 flesch: 45 summary:   , multiple selections available, Related content More info Collapse Besu Besu Besu More like this Community Community Besu More like this Operate and Extend Hyperledger Besu Workshop Operate and Extend Hyperledger Besu Workshop Community Events More like this How to Contribute How to Contribute Besu More like this Start Here Start Here Besu More like this Issues Issues Besu More like this {serverDuration: 11, requestCorrelationId: cf218a128ba046719c9d16bece737369}   Besu Community Support The Besu Documentation can answer many questions Relevant sections for stakers and Besu infrastructure: System Requirements Troubleshoot peering Troubleshoot performance Configure ports Understand metrics keywords: besu; community; support cache: lfhyperledger-Besu+-+Community+Support.html plain text: lfhyperledger-Besu+-+Community+Support.txt item: #2152 of 3327 id: lfhyperledger-Besu+2022+Vision author: lfhyperledger title: lfhyperledger-Besu+2022+Vision date: None words: 475 flesch: 12 summary: Close Besu / Besu 2022 Vision More actions Besu 2022 Vision Danno Ferrin Sorn Maksumic (Deactivated) Owned by Danno Ferrin Last updated: Sept 14, 2022 by Sorn Maksumic (Deactivated) Hyperledger Besu is Hyperledger's Principal Ethereum project. EVM Engine Consensus Protocols Peer-to-peer communications JSON-RPC Communications Data Storage Block Production , multiple selections available, Related content More info Collapse Besu Besu Besu More like this 2020 Q2 Hyperledger Besu 2020 Q2 Hyperledger Besu Technical Oversight Committee More like this 2020 Q4 Hyperledger Besu 2020 Q4 Hyperledger Besu Technical Oversight Committee More like this 2021 Q4 Hyperledger Besu 2021 Q4 Hyperledger Besu Technical Oversight Committee More like this Operate and Extend Hyperledger Besu Workshop Operate and Extend Hyperledger Besu Workshop Community Events More like this Project Plan - Client Connector for Hyperledger Besu Project Plan - Client Connector for Hyperledger Besu Hyperledger Mentorship Program More like this {serverDuration: 14, requestCorrelationId: e0101185cf704fa1b980da69ab3c0ae0} keywords: besu; client; hyperledger cache: lfhyperledger-Besu+2022+Vision.html plain text: lfhyperledger-Besu+2022+Vision.txt item: #2153 of 3327 id: lfhyperledger-Besu+CLI+Style+Guide author: lfhyperledger title: lfhyperledger-Besu+CLI+Style+Guide date: None words: 2206 flesch: 60 summary: The primary audience for this document is: Members of the Besu team Developers contributing pull requests Mission Statement The Besu CLI should create a consistent and easy to understand experience for end users. This is a living document and should evolve to better suit end users and those who contribute to Besu. keywords: ansi; besu; error; formatting; users cache: lfhyperledger-Besu+CLI+Style+Guide.html plain text: lfhyperledger-Besu+CLI+Style+Guide.txt item: #2154 of 3327 id: lfhyperledger-Besu+Execution+Client+Incentive+Program author: lfhyperledger title: lfhyperledger-Besu+Execution+Client+Incentive+Program date: None words: 2092 flesch: 36 summary: The following are the success metrics that the Client must meet: Client validators on average do not drop below MIN_ACCEPTABLE_BALANCE balance Client validators have at least MIN_ATTESTATION_PERCENTAGE percentage of expected attestations included on chain over any METRICS_WINDOW epoch period Client validators have at least MIN_BLOCK_PERCENTAGE percentage of expected blocks included on chain over any METRICS_WINDOW epoch period Metrics Name Value Description MIN_ACCEPTABLE_BALANCE 31.75 ETH Minimum acceptable balance of client validators MIN_ATTESTATION_PERCENTAGE 95 percent Minimum acceptable percentage of attestations created by client validators MIN_BLOCK_PERCENTAGE 95 percent Minimum acceptable percentage of blocks created by client validators keywords: besu; client; incentive; program; validators cache: lfhyperledger-Besu+Execution+Client+Incentive+Program.html plain text: lfhyperledger-Besu+Execution+Client+Incentive+Program.txt item: #2155 of 3327 id: lfhyperledger-Besu+Roadmap+Planning author: lfhyperledger title: lfhyperledger-Besu+Roadmap+Planning date: None words: 793 flesch: 19 summary: Related releases 26.m.x Client Evolution Modularity of the protocol schedule Modularity everywhere Ongoing Protocol Research Besu as an Ethereum reference client in Java Statelessness State Expiry research  Modularity work Move consensus logic out of core Besu monorepo Allow faster iteration on both core Besu and enterprise Besu features BFT peering via non-validators Allow edge-of-network nodes that aren’t BFT validators   , multiple selections available, Related content More info Collapse Enterprise roadmap item detail Enterprise roadmap item detail Besu Read with this 2022 Q1 Hyperledger Besu 2022 Q1 Hyperledger Besu Technical Oversight Committee More like this 2021-09-28 Besu Contributor Call 2021-09-28 Besu Contributor Call Besu More like this 2022 Q3 Hyperledger Besu 2022 Q3 Hyperledger Besu Technical Oversight Committee More like this 2022 Q2 Hyperledger Besu 2022 Q2 Hyperledger Besu Technical Oversight Committee More like this 2021-08-31 Besu Contributor Call 2021-08-31 Besu Contributor Call Besu More like this Atlassian Intelligence {serverDuration: 12, requestCorrelationId: d7ccff30d14b4fa99ef9797e36f55fc2} Close Besu / Besu Roadmap & Planning More actions Besu Roadmap & Planning Felipe Faraggi Matthew Whitehead Sally MacFarlane +8 Owned by Felipe Faraggi Last updated: yesterday at 6:09 am by Matthew Whitehead 2 min read This document represents the current working roadmap for Besu. keywords: besu; enterprise; roadmap cache: lfhyperledger-Besu+Roadmap+Planning.html plain text: lfhyperledger-Besu+Roadmap+Planning.txt item: #2156 of 3327 id: lfhyperledger-Besu+as+a+Modular+Client+for+the+Merge+OLD author: lfhyperledger title: lfhyperledger-Besu+as+a+Modular+Client+for+the+Merge+OLD date: None words: 1088 flesch: 37 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Design Documents Ethereum Classic Support Feature Proposal Template Feature Flags RPC Endpoint Service Switchable Consensus Parameters Bonsai Tries Design Overview Refactor EVM into a stand alone library SECP256R1 Support DRAFT - Pico CLI Plugin Integration Besu 2022 Vision Modular Besu Besu as a Modular Client for the Merge (OLD) DRAFT - Besu Software Component Map Modular Consensus Modularity Implementation Approach CI/CD Migration Change to Besu Defaults - Q1 2024 CI/CD Tooling and Process Bonsai archive feature Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked.    Considerations common to both approaches Pros The effort to modularize is underway already for the evm This dovetails nicely with the need to have pluggable MEV strategies  Risks Finding the right ‘bounded context’ for libraries is non-trivial The effort of refactoring Besu into modules becomes critical-path for having a besu-based execution client Changes the value proposition of the project - no longer is besu “an ethereum mainnet ready clientâ€�.  keywords: besu; client; engine; execution; modular cache: lfhyperledger-Besu+as+a+Modular+Client+for+the+Merge+OLD.html plain text: lfhyperledger-Besu+as+a+Modular+Client+for+the+Merge+OLD.txt item: #2157 of 3327 id: lfhyperledger-BesuContext author: lfhyperledger title: lfhyperledger-BesuContext date: None words: 445 flesch: 37 summary: Close Besu / BesuContext More actions BesuContext Antony Denyer Owned by Antony Denyer Oct 11, 2021 public interface BesuContext Allows plugins to access Besu services. Returns: an optional containing the instance of the requested service, or empty if the service is unavailable , multiple selections available, Related content More info Collapse Besu Besu Besu More like this Besu - Community Support Besu - Community Support Besu More like this Debugging Besu in IntelliJ Debugging Besu in IntelliJ Besu More like this How to Contribute How to Contribute Besu More like this Suggesting Enhancements Suggesting Enhancements Besu More like this Issues Issues Besu More like this {serverDuration: 13, requestCorrelationId: f7e1bc7369e243ce9b0480e9ab3ed8a8} keywords: besu; service cache: lfhyperledger-BesuContext.html plain text: lfhyperledger-BesuContext.txt item: #2158 of 3327 id: lfhyperledger-Bi-Weekly+Quarterly+Release+Process author: lfhyperledger title: lfhyperledger-Bi-Weekly+Quarterly+Release+Process date: None words: 630 flesch: 43 summary: This change was implemented at a time where Besu releases had run into several showstopper bugs. Increasing 1.4 RC/Beta window Proposal: Quarterly releases from main by default Release Philosophy Archive Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; process; release cache: lfhyperledger-Bi-Weekly+Quarterly+Release+Process.html plain text: lfhyperledger-Bi-Weekly+Quarterly+Release+Process.txt item: #2159 of 3327 id: lfhyperledger-Bonsai+Tries+Design+Overview author: lfhyperledger title: lfhyperledger-Bonsai+Tries+Design+Overview date: None words: 1089 flesch: 68 summary: Close Besu / Bonsai Tries Design Overview More actions Bonsai Tries Design Overview Danno Ferrin Owned by Danno Ferrin Sept 14, 2020 This design overview is currently speculative, the actual implementation may vary.   Instead of storing trie branches and leaves in a content addressable means (the hash of the node) the leaf pile stores a single point in time key addressable. keywords: besu; bonsai; leaf; trie cache: lfhyperledger-Bonsai+Tries+Design+Overview.html plain text: lfhyperledger-Bonsai+Tries+Design+Overview.txt item: #2160 of 3327 id: lfhyperledger-Bonsai+archive+feature author: lfhyperledger title: lfhyperledger-Bonsai+archive+feature date: None words: 1146 flesch: 53 summary: Oct 11, 2024 For background there is a design document relating to Bonsai DB in the wiki here The issue for Bonsai archive is here and the PR is here. Value = the code These are used to store account state, account storage, and code respectively. keywords: account; block; bonsai; state cache: lfhyperledger-Bonsai+archive+feature.html plain text: lfhyperledger-Bonsai+archive+feature.txt item: #2161 of 3327 id: lfhyperledger-Bug+Triage+Process author: lfhyperledger title: lfhyperledger-Bug+Triage+Process date: None words: 824 flesch: 53 summary: We categorize bugs based on their Probability (how often) and their Severity (how bad). These buckets are: Priority Examples Very High (P1) Security issues Non-planned backward incompatibilities, preventing the node from participating in the network High (P2) Degrading performance issues Unexpected behaviour of core features (DevP2P, syncing, etc) Medium (P3) JSON-RPC request not working with a specific client library due to some loose spec assumption Low (P4) Node doesn't start up when the configuration file has unexpected end-of-line character Very Low (P5) JSON-RPC json object response not ignoring keys with null value Typo on a CLI command description Why is it important? All software has bugs. keywords: besu; bug; bugs cache: lfhyperledger-Bug+Triage+Process.html plain text: lfhyperledger-Bug+Triage+Process.txt item: #2162 of 3327 id: lfhyperledger-Building+from+source author: lfhyperledger title: lfhyperledger-Building+from+source date: None words: 797 flesch: 38 summary: More info Collapse How to Contribute How to Contribute Besu More like this DRAFT - Besu Software Component Map DRAFT - Besu Software Component Map Besu More like this Operate and Extend Hyperledger Besu Workshop Prerequisites Operate and Extend Hyperledger Besu Workshop Prerequisites Community Events More like this Documentation contribution workflow Documentation contribution workflow Besu More like this Versioned documentation Versioned documentation Besu More like this Start Here Start Here Besu More like this Atlassian Intelligence {serverDuration: 13, requestCorrelationId: 1a3f4bd0e8b3437693f8de763dafdc3d} PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; build; install cache: lfhyperledger-Building+from+source.html plain text: lfhyperledger-Building+from+source.txt item: #2163 of 3327 id: lfhyperledger-CI+CD+Migration author: lfhyperledger title: lfhyperledger-CI+CD+Migration date: None words: 1302 flesch: 58 summary: You'll also find test results attached to the workflow run, and a summary of how each test shard performed. PR has an approval from at least one project maintainer. acceptance test checks have passed on the merge result, and the PR has an acceptance-tests status. keywords: fabric; hyperledger; release; tests cache: lfhyperledger-CI+CD+Migration.html plain text: lfhyperledger-CI+CD+Migration.txt item: #2164 of 3327 id: lfhyperledger-CI+CD+Tooling+and+Process author: lfhyperledger title: lfhyperledger-CI+CD+Tooling+and+Process date: None words: 1309 flesch: 61 summary: What this means for users Users should not notice anything different, other than new delivery urls for Besu releases. Breaking up the various workflows into smaller pieces using test splitting results in much greater parallelization, and hence shorter overall runtimes. keywords: besu; process; release; test cache: lfhyperledger-CI+CD+Tooling+and+Process.html plain text: lfhyperledger-CI+CD+Tooling+and+Process.txt item: #2165 of 3327 id: lfhyperledger-Cancun+Planning author: lfhyperledger title: lfhyperledger-Cancun+Planning date: None words: 348 flesch: 32 summary: Cancun meta thread EIP T-shirt Size PR Champion EIP-4844: Shard blob transactions L #5536 Justin / Sally EIP-6780: SELFDESTRUCT only in the same transaction M #5430 Danno EIP-1153: Transient storage M #4118 Moody / Danno EIP-4788: Beacon block root in the EVM M #5655 (issue) Stefan P EIP-5656: MCOPY - Memory copying instruction S #5493 Danno , multiple selections available, Related content More info Collapse 2025-01-30 Cacti Maintainers Agenda - CANCELLED 2025-01-30 Cacti Maintainers Agenda - CANCELLED Hyperledger Cacti More like this 2019-11-26 Besu Contributor Call 2019-11-26 Besu Contributor Call Besu More like this 2020-10-05 Meeting notes 2020-10-05 Meeting notes Hyperledger Cacti More like this 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-10 Contributor Call - APAC Friendly Time Besu More like this 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-06 Contributor Call - APAC Friendly Time Besu More like this 2019-06-07 Meeting notes 2019-06-07 Meeting notes Bootcamp - São Paulo (archived) Close Besu / Cancun Planning More actions Cancun Planning Jason Frame Matt Nelson (Deactivated) Sally MacFarlane +2 Owned by Jason Frame Last updated: Jul 31, 2023 by Matt Nelson (Deactivated) keywords: besu; contributor cache: lfhyperledger-Cancun+Planning.html plain text: lfhyperledger-Cancun+Planning.txt item: #2166 of 3327 id: lfhyperledger-Change+to+Besu+Defaults+-+Q1+2024 author: lfhyperledger title: lfhyperledger-Change+to+Besu+Defaults+-+Q1+2024 date: None words: 896 flesch: 50 summary: (currently 1 eth, may want to lower for RPC providers) , multiple selections available, Related content More info Collapse Besu CLI Style Guide Besu CLI Style Guide Besu More like this 2022 Q2 Hyperledger Besu 2022 Q2 Hyperledger Besu Technical Oversight Committee More like this 2022 Q3 Hyperledger Besu 2022 Q3 Hyperledger Besu Technical Oversight Committee More like this Besu Roadmap & Planning Besu Roadmap & Planning Besu More like this 2023-11-07 Contributor Call - APAC Friendly Time 2023-11-07 Contributor Call - APAC Friendly Time Besu More like this Release 22.1.0 Release 22.1.0 Besu More like this {serverDuration: 12, requestCorrelationId: 943171d8a1af4288b5eff1d17c93fc48} Close Besu / Change to Besu Defaults - Q1 2024 More actions Change to Besu Defaults - Q1 2024 Matt Nelson (Deactivated) Owned by Matt Nelson (Deactivated) Last updated: Dec 19, 2023 2024 Besu Defaults Context Currently starting Besu without configuring a handful of options will create a sub-par experience for users. keywords: besu; bonsai; data; defaults cache: lfhyperledger-Change+to+Besu+Defaults+-+Q1+2024.html plain text: lfhyperledger-Change+to+Besu+Defaults+-+Q1+2024.txt item: #2167 of 3327 id: lfhyperledger-Changelog author: lfhyperledger title: lfhyperledger-Changelog date: None words: 418 flesch: 16 summary:   , multiple selections available, Related content More info Collapse Changelog Improvement Proposal Changelog Improvement Proposal Besu More like this 2022-01-04 Besu Contributor Call 2022-01-04 Besu Contributor Call Besu More like this 2019-11-26 Contributor Call 2019-11-26 Contributor Call Besu More like this 2019-12-10 Contributor Call 2019-12-10 Contributor Call Besu More like this 2020-09-29 Besu Contributor Call Notes 2020-09-29 Besu Contributor Call Notes Besu More like this 2019-10-29 Contributor Call 2019-10-29 Contributor Call Besu More like this {serverDuration: 15, requestCorrelationId: 16edc048c37147be8e0e8357be0fadaa} Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; contributor cache: lfhyperledger-Changelog.html plain text: lfhyperledger-Changelog.txt item: #2168 of 3327 id: lfhyperledger-Changelog+Improvement+Proposal author: lfhyperledger title: lfhyperledger-Changelog+Improvement+Proposal date: None words: 430 flesch: 17 summary: An alternative proposal which would remediate the broken link issue - remove docs updates from the changelog - https://github.com/hyperledger/besu/pull/7562 , multiple selections available, Related content More info Collapse Changelog Changelog Besu More like this Process change proposal: burn-in Process change proposal: burn-in Besu More like this Versioned documentation Versioned documentation Besu More like this Release Process Improvement Release Process Improvement Besu More like this Documentation release process Documentation release process Besu More like this 2020 Q3 Hyperledger Besu 2020 Q3 Hyperledger Besu Technical Oversight Committee More like this {serverDuration: 36, requestCorrelationId: f170db9966e94b1b8c62d0e0b4c31e96} Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; changelog cache: lfhyperledger-Changelog+Improvement+Proposal.html plain text: lfhyperledger-Changelog+Improvement+Proposal.txt item: #2169 of 3327 id: lfhyperledger-Checklist+for+reporting+privacy+issues author: lfhyperledger title: lfhyperledger-Checklist+for+reporting+privacy+issues date: None words: 425 flesch: 34 summary: Please provide the following information Versions of Besu, Orion and any other relevant software (as per Besu issue template) Instructions for how to reproduce the scenario  As much specific detail as possible. Have you verified that the same scenario works in Besu without privacy ie as a public contract Including instructions on how to deploy the scenario - eg Truffle deploy scripts Orion logs Enable revert reason on Besu CLI  Ensure in the solidity code you are using strings with require/revert statements to make it possible to track where the revert is happening Besu log with EVM at trace level  Enable trace logging for the EVM org.hyperledger.besu.ethereum.vm. keywords: besu; privacy cache: lfhyperledger-Checklist+for+reporting+privacy+issues.html plain text: lfhyperledger-Checklist+for+reporting+privacy+issues.txt item: #2170 of 3327 id: lfhyperledger-Code+Reviews author: lfhyperledger title: lfhyperledger-Code+Reviews date: None words: 463 flesch: 45 summary: Close Besu / Code Reviews More actions Code Reviews Felipe Faraggi Grace Hartley (Deactivated) Owned by Felipe Faraggi Last updated: Feb 14, 2022 by Grace Hartley (Deactivated) Code review guidelines for Besu developers All changes must be code reviewed. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; code cache: lfhyperledger-Code+Reviews.html plain text: lfhyperledger-Code+Reviews.txt item: #2171 of 3327 id: lfhyperledger-Code+coverage author: lfhyperledger title: lfhyperledger-Code+coverage date: None words: 342 flesch: 15 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Plugin Services Tools we use Code coverage Gradle Verification Metadata Usage of SonarQube Usage of vulnerability scanners Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; usage cache: lfhyperledger-Code+coverage.html plain text: lfhyperledger-Code+coverage.txt item: #2172 of 3327 id: lfhyperledger-Code+of+Conduct author: lfhyperledger title: lfhyperledger-Code+of+Conduct date: None words: 309 flesch: 25 summary: The LFDT Code of Conduct also applies to participants in this project. , multiple selections available, Related content More info Collapse Hyperledger Code of Conduct Hyperledger Code of Conduct LF Decentralized Trust More like this Anti-trust Policy Notice & Code of Conduct Anti-trust Policy Notice & Code of Conduct Community Projects More like this LFDT Student Society - Chandigarh University Chapter LFDT Student Society - Chandigarh University Chapter Hyperledger India Regional Chapter More like this LFDT Student Society - GGITS Jabalpur Chapter LFDT Student Society - GGITS Jabalpur Chapter Hyperledger India Regional Chapter More like this LFDT India Chapter Governace LFDT India Chapter Governace Hyperledger India Regional Chapter More like this Onboarding information Onboarding information Community Projects More like this {serverDuration: 37, requestCorrelationId: 6ae4bc3815194ec29dcc712870e37095} Close Besu / Code of Conduct More actions Code of Conduct Felipe Faraggi Sally MacFarlane Owned by Felipe Faraggi Last updated: Nov 27, 2024 by Sally MacFarlane This project and everyone participating in it is governed by the Besu Code of Conduct. keywords: code; conduct cache: lfhyperledger-Code+of+Conduct.html plain text: lfhyperledger-Code+of+Conduct.txt item: #2173 of 3327 id: lfhyperledger-Coding+Conventions author: lfhyperledger title: lfhyperledger-Coding+Conventions date: None words: 1925 flesch: 46 summary: Logging Logging is important for understanding what Besu is doing at any given time (for example, progress while synchronizing) and investigating defects. Default logging level Warn - Anything that can potentially cause application oddities but from which Besu automatically recovers Error - Any error which is fatal to the operation, but not Besu itself (for example, missing data) Fatal - An error that forces a shutdown of Besu INFO Principles Aimed at users Should indicate any relevant progress for example sync, peering, worldstate download Should not present errors or warnings that require no intervention DEBUG Principles  Aimed at both end users and developers  Should lead to resolution of common problems, whilst not spamming  Should not contain logs that take up more than one terminal screen, e.g. raw data, including RLP DEBUG Guidelines Should not include peer discovery Should not include txpool management Could include some peering to debug peering issues Could include some high level syncing logs Could include API requests, including potentially truncated data, but not full RLP TRACE Principles Aimed at developers Expectation is everything is there and it's spammy Only useful when targeting certain packages/classes For any log level past INFO, you will see in the code this pattern which is used to avoid unnecessary runtime processing. keywords: besu; code; design; example; methods; use cache: lfhyperledger-Coding+Conventions.html plain text: lfhyperledger-Coding+Conventions.txt item: #2174 of 3327 id: lfhyperledger-Community author: lfhyperledger title: lfhyperledger-Community date: None words: 291 flesch: 38 summary: PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. Last updated: May 31, 2023 This section of the wiki outlines the way the Besu community works and should operate, including best practices for support. keywords: besu cache: lfhyperledger-Community.html plain text: lfhyperledger-Community.txt item: #2175 of 3327 id: lfhyperledger-Configure+and+format+Markdown author: lfhyperledger title: lfhyperledger-Configure+and+format+Markdown date: None words: 744 flesch: 50 summary: The following are rules for formatting Markdown in Besu documentation: Each Markdown file must contain a header composed of metadata and limited by three dashes (-). If using Markdown tables, format them so they’re also readable in the source code. keywords: documentation; markdown cache: lfhyperledger-Configure+and+format+Markdown.html plain text: lfhyperledger-Configure+and+format+Markdown.txt item: #2176 of 3327 id: lfhyperledger-Contributing author: lfhyperledger title: lfhyperledger-Contributing date: None words: 309 flesch: 28 summary: We look for contributions of all forms:  code submissions, writing documentation, raising issues, helping others in chat,  and any other actions that help build Besu. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu cache: lfhyperledger-Contributing.html plain text: lfhyperledger-Contributing.txt item: #2177 of 3327 id: lfhyperledger-Copyright+and+License author: lfhyperledger title: lfhyperledger-Copyright+and+License date: None words: 461 flesch: 37 summary: See the License for the * specific language governing permissions and limitations under the License. * * SPDX-License-Identifier: Apache-2.0 */ , multiple selections available, Related content More info Collapse Security Security Besu More like this 1 - LFDT India Student Society 1 - LFDT India Student Society Hyperledger India Regional Chapter More like this Hyperledger India Chapter Student Society Hyperledger India Chapter Student Society Hyperledger India Regional Chapter More like this 12/9/2024 12/9/2024 Developer Relations More like this Japanese Documentation Working Group Japanese Documentation Working Group I18n More like this 11/04/24 11/04/24 Developer Relations More like this {serverDuration: 13, requestCorrelationId: 1405427da83140d1a891d667139769ff} * * Copyright contributors to Hyperledger Besu. keywords: hyperledger; license cache: lfhyperledger-Copyright+and+License.html plain text: lfhyperledger-Copyright+and+License.txt item: #2178 of 3327 id: lfhyperledger-Critical+Issue+for+Privacy+Users author: lfhyperledger title: lfhyperledger-Critical+Issue+for+Privacy+Users date: None words: 578 flesch: 33 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Release Rotations 2024 Using CalVer for Besu Releases How to do a Besu Release Off-cycle release process Release Process Obsolete Proposals and Policies Archive Critical Issue for Privacy Users Mainnet Consensus Bug Identified and Resolved in Hyperledger Besu Release 22.1.0 Release Process Improvement Release Remediation Release Rotations 2021 Release Rotations 2022 Release Rotations 2023 Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked.   Contact us on RocketChat! , multiple selections available, Related content More info Collapse Checklist for reporting privacy issues Checklist for reporting privacy issues Besu More like this Security Security Besu More like this 2021-08-04 Value transfer public transactions being rejected by Besu 2021-08-04 Value transfer public transactions being rejected by Besu Besu More like this 2024-01-06 Mainnet Halting Event 2024-01-06 Mainnet Halting Event Besu More like this 2020 Q3 Hyperledger Besu 2020 Q3 Hyperledger Besu Technical Oversight Committee More like this Mainnet Consensus Bug Identified and Resolved in Hyperledger Besu Mainnet Consensus Bug Identified and Resolved in Hyperledger Besu Besu More like this {serverDuration: 37, requestCorrelationId: 1855f13d671b4bc897a66b012ed6269d} keywords: besu; hyperledger; release cache: lfhyperledger-Critical+Issue+for+Privacy+Users.html plain text: lfhyperledger-Critical+Issue+for+Privacy+Users.txt item: #2179 of 3327 id: lfhyperledger-Curators author: lfhyperledger title: lfhyperledger-Curators date: None words: 505 flesch: 31 summary: Close Besu / Curators More actions Curators Sally MacFarlane Owned by Sally MacFarlane Last updated: May 26, 2022 Curators have triage access to the Besu GitHub repository which means they can curate, manage, label and otherwise categorize bugs and other Github issues for Besu, collaborate with the existing maintainers to help coordinate the development and roadmap planning of Besu This means they have the ability to label and close GitHub issues, helping to keep the project tidy. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: access; besu cache: lfhyperledger-Curators.html plain text: lfhyperledger-Curators.txt item: #2180 of 3327 id: lfhyperledger-DCO author: lfhyperledger title: lfhyperledger-DCO date: None words: 872 flesch: 49 summary: If you have any questions, you can reach us on Discord , multiple selections available, Related content More info Collapse Fixing DCO on main/release Fixing DCO on main/release Besu More like this DCO Validation During Contribution Review DCO Validation During Contribution Review Technical Oversight Committee More like this Making Iroha codebase conformant to DCO requirements: a step-by-step plan Making Iroha codebase conformant to DCO requirements: a step-by-step plan Hyperledger Iroha More like this Git signing with DIDs Git signing with DIDs Hyperledger Mentorship Program More like this GitHub Merge Queue GitHub Merge Queue Besu More like this DRAFT DOCUMENT - Best Practices for Automated Pipelines DRAFT DOCUMENT - Best Practices for Automated Pipelines Task Forces More like this {serverDuration: 39, requestCorrelationId: 52bf5bdc2e3e41fdb829d00a28610cfe} When you have a DCO failure on your PR from DCO Bot ' Click on that Details link and follow the instructions. keywords: commits; dco; git cache: lfhyperledger-DCO.html plain text: lfhyperledger-DCO.txt item: #2181 of 3327 id: lfhyperledger-DRAFT+-+Besu+Software+Component+Map author: lfhyperledger title: lfhyperledger-DRAFT+-+Besu+Software+Component+Map date: None words: 1081 flesch: 56 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Design Documents Ethereum Classic Support Feature Proposal Template Feature Flags RPC Endpoint Service Switchable Consensus Parameters Bonsai Tries Design Overview Refactor EVM into a stand alone library SECP256R1 Support DRAFT - Pico CLI Plugin Integration Besu 2022 Vision Modular Besu Besu as a Modular Client for the Merge (OLD) DRAFT - Besu Software Component Map Modular Consensus Modularity Implementation Approach CI/CD Migration Change to Besu Defaults - Q1 2024 CI/CD Tooling and Process Bonsai archive feature Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; draft; gradle; software; tests cache: lfhyperledger-DRAFT+-+Besu+Software+Component+Map.html plain text: lfhyperledger-DRAFT+-+Besu+Software+Component+Map.txt item: #2182 of 3327 id: lfhyperledger-DRAFT+-+Pico+CLI+Plugin+Integration author: lfhyperledger title: lfhyperledger-DRAFT+-+Pico+CLI+Plugin+Integration date: None words: 790 flesch: 41 summary: Register all Plugins Validate Configuration combinations Instantiate Besu Run Besu Code Breaking changes POC for loading cli options - I think this offers better integration and understanding of what's going on but at the cost of being a breaking change. This will mean changing the way cli plugin arguments are registered. keywords: besu; cli; integration; plugin cache: lfhyperledger-DRAFT+-+Pico+CLI+Plugin+Integration.html plain text: lfhyperledger-DRAFT+-+Pico+CLI+Plugin+Integration.txt item: #2183 of 3327 id: lfhyperledger-Debugging+Besu+in+IntelliJ author: lfhyperledger title: lfhyperledger-Debugging+Besu+in+IntelliJ date: None words: 429 flesch: 29 summary: Close Besu / Debugging Besu in IntelliJ More actions Debugging Besu in IntelliJ Sally MacFarlane Owned by Sally MacFarlane Jun 04, 2024 Running Besu in debug mode within your IDE can be very useful as this allows you to set breakpoints on certain lines. Debugging Besu in IntelliJ - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; intellij cache: lfhyperledger-Debugging+Besu+in+IntelliJ.html plain text: lfhyperledger-Debugging+Besu+in+IntelliJ.txt item: #2184 of 3327 id: lfhyperledger-Decouple+a+class+with+Dagger+-+DRAFT author: lfhyperledger title: lfhyperledger-Decouple+a+class+with+Dagger+-+DRAFT date: None words: 1194 flesch: 53 summary: The second module is probably a BesuBonsaiModule that creates the subcomponent, using provided configuration from the Besu application runtime. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; class; dagger; use cache: lfhyperledger-Decouple+a+class+with+Dagger+-+DRAFT.html plain text: lfhyperledger-Decouple+a+class+with+Dagger+-+DRAFT.txt item: #2185 of 3327 id: lfhyperledger-Defect+Prioritisation+Policy author: lfhyperledger title: lfhyperledger-Defect+Prioritisation+Policy date: None words: 1108 flesch: 47 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Defect Prioritisation Policy Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; low; medium; product cache: lfhyperledger-Defect+Prioritisation+Policy.html plain text: lfhyperledger-Defect+Prioritisation+Policy.txt item: #2186 of 3327 id: lfhyperledger-Deployment+of+Private+Hyperledger+Besu+on+AWS+with+hardware+layer+for+Externally+Owned+Account author: lfhyperledger title: lfhyperledger-Deployment+of+Private+Hyperledger+Besu+on+AWS+with+hardware+layer+for+Externally+Owned+Account date: None words: 2844 flesch: 47 summary: Close Besu / Deployment of Private Hyperledger Besu on AWS with hardware layer for Externally Owned Account More actions Deployment of Private Hyperledger Besu on AWS with hardware layer for Externally Owned Account Marek Tatara Owned by Marek Tatara Last updated: Jul 30, 2020 In this post, we will show how to deploy a private Hyperledger Besu network on Amazon Web Services. Deployment of Private Hyperledger Besu on AWS with hardware layer for Externally Owned Account , multiple selections available,aws blockchain kb-how-to-article Related content More info Collapse Configure, Deploy, and Manage a Besu Private Network Configure, Deploy, and Manage a Besu Private Network Community Events More like this Using Hyperledger Besu to Participate in Public Ethereum Networks Using Hyperledger Besu to Participate in Public Ethereum Networks Community Events More like this Client Connector for Hyperledger Besu Client Connector for Hyperledger Besu Hyperledger Mentorship Program More like this Project Plan - Client Connector for Hyperledger Besu Project Plan - Client Connector for Hyperledger Besu Hyperledger Mentorship Program More like this Project Plan - Support Clique Consensus for Besu on HL Labs Blockchain Automation Framework Project Plan - Support Clique Consensus for Besu on HL Labs Blockchain Automation Framework Hyperledger Mentorship Program More like this Deploy Carbon Accounting Network with Bevel Deploy Carbon Accounting Network with Bevel Hyperledger Mentorship Program More like this {serverDuration: 13, requestCorrelationId: ceecc84ebd2a4d52b221ea4e86506074} keywords: account; besu; environment; hyperledger; network; node; transaction cache: lfhyperledger-Deployment+of+Private+Hyperledger+Besu+on+AWS+with+hardware+layer+for+Externally+Owned+Account.html plain text: lfhyperledger-Deployment+of+Private+Hyperledger+Besu+on+AWS+with+hardware+layer+for+Externally+Owned+Account.txt item: #2187 of 3327 id: lfhyperledger-Design+Documents author: lfhyperledger title: lfhyperledger-Design+Documents date: None words: 360 flesch: 4 summary: Close Besu / Design Documents More actions Design Documents Danno Ferrin Lucas Saldanha Owned by Danno Ferrin Last updated: Aug 19, 2021 by Lucas Saldanha Ethereum Classic Support Switchable Consensus Parameters RPC Endpoint Service Feature Proposal Template Feature Flags Bonsai Tries Design Overview Refactor EVM into a stand alone library SECP256R1 Support DRAFT - Pico CLI Plugin Integration Besu 2022 Vision Modular Besu CI/CD Migration Change to Besu Defaults - Q1 2024 CI/CD Tooling and Process Bonsai archive feature , multiple selections available, Related content More info Collapse Project Plan - Bevel Documentation redesign Project Plan - Bevel Documentation redesign Hyperledger Mentorship Program More like this Task Force: Documentation Standards for Hyperledger Community Task Force: Documentation Standards for Hyperledger Community Learning Materials Development Working Group More like this Resource Library Resource Library Learning Materials Development Working Group PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; design; feature cache: lfhyperledger-Design+Documents.html plain text: lfhyperledger-Design+Documents.txt item: #2188 of 3327 id: lfhyperledger-Developing+and+Conventions author: lfhyperledger title: lfhyperledger-Developing+and+Conventions date: None words: 316 flesch: 6 summary: Close Besu / Developing and Conventions More actions Developing and Conventions Felipe Faraggi Owned by Felipe Faraggi Last updated: Jan 24, 2020 Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source , multiple selections available, Related content More info Collapse Working Groups Working Groups LF Decentralized Trust More like this 2022 03 01 Standards WG 2022 03 01 Standards WG Climate Action SIG More like this 2020-11-09 Meeting Notes 2020-11-09 Meeting Notes Community Projects More like this Resource Library Resource Library Learning Materials Development Working Group More like this Survey for Working Groups Survey for Working Groups Learning Materials Development Working Group More like this Team Information Team Information Hyperledger Mentorship Program More like this {serverDuration: 12, requestCorrelationId: e0caf83e8aa34e4b9b7f09f05a910b88} Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; conventions cache: lfhyperledger-Developing+and+Conventions.html plain text: lfhyperledger-Developing+and+Conventions.txt item: #2189 of 3327 id: lfhyperledger-Discord author: lfhyperledger title: lfhyperledger-Discord date: None words: 279 flesch: 32 summary: Explore the #besu and #besu-contributors channel , multiple selections available, Related content More info Collapse Our chat service Our chat service LF Decentralized Trust More like this Meetups Meetups Community Events More like this Issues Issues Besu More like this Start Here Start Here Besu More like this 2020 Q1 Hyperledger Besu 2020 Q1 Hyperledger Besu Technical Oversight Committee More like this 2020 Q2 Hyperledger Besu 2020 Q2 Hyperledger Besu Technical Oversight Committee More like this {serverDuration: 12, requestCorrelationId: 0c5444102dae4fde8043db635347c75c} PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; discord cache: lfhyperledger-Discord.html plain text: lfhyperledger-Discord.txt item: #2190 of 3327 id: lfhyperledger-Documentation author: lfhyperledger title: lfhyperledger-Documentation date: None words: 287 flesch: 9 summary: Table of contents Documentation contribution workflow Documentation contribution guidelines Versioned documentation Documentation archive , multiple selections available, Related content More info Collapse Versioned documentation Versioned documentation Besu More like this Suggest documentation enhancements Suggest documentation enhancements Besu More like this Documentation contribution guidelines Documentation contribution guidelines Besu More like this Documentation contribution workflow Documentation contribution workflow Besu More like this Issues Issues Besu More like this How to Contribute How to Contribute Besu More like this {serverDuration: 12, requestCorrelationId: 2381697778c645a6b482a2274bfc755c} Close Besu / Documentation More actions Documentation Felipe Faraggi Sally MacFarlane Nicolas Massart alexandra.tran Owned by Felipe Faraggi Last updated: Sept 15, 2024 by Sally MacFarlane The pages in this section contain information about contributing to the Besu technical documentation. keywords: documentation cache: lfhyperledger-Documentation.html plain text: lfhyperledger-Documentation.txt item: #2191 of 3327 id: lfhyperledger-Documentation+archive author: lfhyperledger title: lfhyperledger-Documentation+archive date: None words: 279 flesch: 18 summary: Close Besu / Documentation archive More actions Documentation archive alexandra.tran Owned by alexandra.tran Jun 23, 2023 This section contains legacy documentation contribution information that is no longer maintained. Documentation archive - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: documentation; meeting cache: lfhyperledger-Documentation+archive.html plain text: lfhyperledger-Documentation+archive.txt item: #2192 of 3327 id: lfhyperledger-Documentation+contribution+guidelines author: lfhyperledger title: lfhyperledger-Documentation+contribution+guidelines date: None words: 282 flesch: 2 summary: Close Besu / Documentation contribution guidelines More actions Documentation contribution guidelines alexandra.tran Owned by alexandra.tran Jun 23, 2023 Follow the Besu documentation contribution workflow when submitting a contribution. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: documentation cache: lfhyperledger-Documentation+contribution+guidelines.html plain text: lfhyperledger-Documentation+contribution+guidelines.txt item: #2193 of 3327 id: lfhyperledger-Documentation+contribution+workflow author: lfhyperledger title: lfhyperledger-Documentation+contribution+workflow date: None words: 801 flesch: 51 summary: Close Besu / Documentation contribution workflow More actions Documentation contribution workflow Felipe Faraggi Alexandra Tran Sally MacFarlane +2 Owned by Felipe Faraggi Last updated: Dec 20, 2023 by Alexandra Tran The following guidelines explain how to contribute to the Besu documentation repository. Code of Conduct Contributing Developing and Conventions Documentation Documentation contribution workflow Documentation contribution guidelines Versioned documentation Documentation archive Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; documentation cache: lfhyperledger-Documentation+contribution+workflow.html plain text: lfhyperledger-Documentation+contribution+workflow.txt item: #2194 of 3327 id: lfhyperledger-Documentation+release+process author: lfhyperledger title: lfhyperledger-Documentation+release+process date: None words: 499 flesch: 16 summary: For example, when updating from version 23.4.1  to 23.4.2 , update the following section in docusaurus.config.js  from the following: docusaurus.config.js (before) lastVersion: 23.4.1, versions: { current: { label: development, path: development, }, 23.4.1: { label: stable (23.4.1), }, 23.4.0: { label: 23.4.0, }, }, To the following: docusaurus.config.js (after) lastVersion: 23.4.2, versions: { current: { label: development, path: development, }, 23.4.2: { label: stable (23.4.2), }, 23.4.1: { label: 23.4.1, }, 23.4.0: { label: 23.4.0, }, }, commit your changes and push a PR to the besu-docs repo eg https://github.com/hyperledger/besu-docs/pull/1382  When this PR is merged to main, it should trigger a github action which will update https://besu.hyperledger.org/ The final step is to draft and publish a new release including the changelog on github: https://github.com/hyperledger/besu-docs/releases , multiple selections available, Related content More info Collapse Release Process Release Process Besu More like this Versioned documentation Versioned documentation Besu More like this Documentation Documentation Besu More like this Using CalVer for Besu Releases Using CalVer for Besu Releases Besu More like this Changelog Improvement Proposal Changelog Improvement Proposal Besu More like this Building from source Building from source Besu More like this {serverDuration: 13, requestCorrelationId: 47202e02e7cc44d0bd60c987aed6063c} PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; documentation cache: lfhyperledger-Documentation+release+process.html plain text: lfhyperledger-Documentation+release+process.txt item: #2195 of 3327 id: lfhyperledger-Documentation+style+guide author: lfhyperledger title: lfhyperledger-Documentation+style+guide date: None words: 838 flesch: 41 summary: Close Besu / Documentation style guide More actions Documentation style guide Felipe Faraggi alexandra.tran Sally MacFarlane Nicolas Massart Owned by Felipe Faraggi Last updated: Apr 08, 2022 by alexandra.tran The following are writing style guidelines for contributing to Besu documentation. Code of Conduct Contributing Developing and Conventions Documentation Documentation contribution workflow Documentation contribution guidelines Versioned documentation Documentation archive Documentation release process Documentation style guide Future Release Dates MkDocs and Markdown guide Proposal - Besu maintainers become docs maintainers Raise issues Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; documentation; guide; style cache: lfhyperledger-Documentation+style+guide.html plain text: lfhyperledger-Documentation+style+guide.txt item: #2196 of 3327 id: lfhyperledger-EIP-1559+testnet+guide author: lfhyperledger title: lfhyperledger-EIP-1559+testnet+guide date: None words: 561 flesch: 28 summary: You will likely need to manually add peers (Besu instructions) to connect to.   Step-by-step guide Select an EIP-1559 capable Ethereum Client, the current available clients are: Hyperledger Besu on master branch Nethermind on eip1559 branch Geth (soon) on 1559_test_fixCalcBaseFee branch  Download the genesis file depending on the client selected at step 1 Hyperledger Besu genesis Other clients TBA Download the config file template depending on the client selected at step 1 Hyperledger Besu sample config file (Optional) keywords: besu; hyperledger; testnet cache: lfhyperledger-EIP-1559+testnet+guide.html plain text: lfhyperledger-EIP-1559+testnet+guide.txt item: #2197 of 3327 id: lfhyperledger-Enterprise+roadmap+item+detail author: lfhyperledger title: lfhyperledger-Enterprise+roadmap+item+detail date: None words: 524 flesch: 34 summary: It is an important step towards the deprecation and removal of the Forest database, since archive nodes will not be possible with Bonsai until this feature is implemented. , multiple selections available, Related content More info Collapse Besu Roadmap & Planning Besu Roadmap & Planning Besu More like this 10/16 10/16 Developer Relations More like this Besu 2022 Vision Besu 2022 Vision Besu More like this QBFT, Bonsai, and Snap-Sync testing QBFT, Bonsai, and Snap-Sync testing Besu More like this 2021 Q4 Hyperledger Besu 2021 Q4 Hyperledger Besu Technical Oversight Committee More like this 2022 Q3 Hyperledger Besu 2022 Q3 Hyperledger Besu Technical Oversight Committee More like this {serverDuration: 11, requestCorrelationId: d14bdfb841094492bb8d84d239278027} PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; qbft; roadmap cache: lfhyperledger-Enterprise+roadmap+item+detail.html plain text: lfhyperledger-Enterprise+roadmap+item+detail.txt item: #2198 of 3327 id: lfhyperledger-Ethereum+Classic+Support author: lfhyperledger title: lfhyperledger-Ethereum+Classic+Support date: None words: 361 flesch: 8 summary: PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Design Documents Ethereum Classic Support Feature Proposal Template Feature Flags RPC Endpoint Service Switchable Consensus Parameters Bonsai Tries Design Overview Refactor EVM into a stand alone library SECP256R1 Support DRAFT - Pico CLI Plugin Integration Besu 2022 Vision Modular Besu CI/CD Migration Change to Besu Defaults - Q1 2024 CI/CD Tooling and Process Bonsai archive feature Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; contributor cache: lfhyperledger-Ethereum+Classic+Support.html plain text: lfhyperledger-Ethereum+Classic+Support.txt item: #2199 of 3327 id: lfhyperledger-Extensions author: lfhyperledger title: lfhyperledger-Extensions date: None words: 1638 flesch: 60 summary: Example: ```json {   jsonrpc: 2.0,   id: 1,   result: true } ``` Tabbed code blocks SuperFences also enables tabbed code blocks. Example: ```json {   jsonrpc : 2.0,   id : 51,   result : {     startingBlock : 0x5a0,     currentBlock : 0xad9,     highestBlock : 0xad9   } } ``` Refer to the full list of support languages. keywords: code; enables; example; extension; theâ cache: lfhyperledger-Extensions.html plain text: lfhyperledger-Extensions.txt item: #2200 of 3327 id: lfhyperledger-Fast+sync+optimisation author: lfhyperledger title: lfhyperledger-Fast+sync+optimisation date: None words: 483 flesch: 16 summary: Median response time import 200 blocks (ms) 90th percentile response time import 200 blocks (ms) 95th percentile response time import 200 blocks (ms) Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability 2024 - Besu Performance Improvements since the Merge Fast sync optimisation Memory usage investigations on 23.7.3-RC Permissioned chain performance testing Q4 2022 Stability and Performance Improvements Reduce Memory usage by choosing a different low level allocator Testing Taskforce Brainstorming How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; blocks; import cache: lfhyperledger-Fast+sync+optimisation.html plain text: lfhyperledger-Fast+sync+optimisation.txt item: #2201 of 3327 id: lfhyperledger-Feature+Flags author: lfhyperledger title: lfhyperledger-Feature+Flags date: None words: 703 flesch: 56 summary: There are other features that are not tied to hard forks that can impact system stability and usability, such as devp2p upgrades and use of native libraries. Longer description:  What does not  get feature flagged? Network Hard Forks where the fork is known and stable. keywords: besu; feature; flag cache: lfhyperledger-Feature+Flags.html plain text: lfhyperledger-Feature+Flags.txt item: #2202 of 3327 id: lfhyperledger-Feature+Proposal+Template author: lfhyperledger title: lfhyperledger-Feature+Proposal+Template date: None words: 484 flesch: 39 summary: Close Besu / Feature Proposal Template More actions Feature Proposal Template Tim Beiko Owned by Tim Beiko Feb 05, 2020 This is a template that can be used by the community to propose a new feature for Hyperledger Besu. More like this Project Plan - Bevel Documentation redesign Project Plan - Bevel Documentation redesign Hyperledger Mentorship Program More like this Bevel: Documentation redesign Bevel: Documentation redesign Hyperledger Mentorship Program More like this Hyperledger Besu Proposal Hyperledger Besu Proposal Technical Oversight Committee More like this 2022 02 17 TSC Meeting Record 2022 02 17 TSC Meeting Record Technical Oversight Committee More like this {serverDuration: 11, requestCorrelationId: 2ee65868096a47cc8cd76e66dd8ce505} keywords: besu; feature; proposal cache: lfhyperledger-Feature+Proposal+Template.html plain text: lfhyperledger-Feature+Proposal+Template.txt item: #2203 of 3327 id: lfhyperledger-First+contribution author: lfhyperledger title: lfhyperledger-First+contribution date: None words: 811 flesch: 61 summary: Close Besu / First contribution More actions First contribution Felipe Faraggi Sally MacFarlane Nicolas Massart +2 Owned by Felipe Faraggi Last updated: Sept 15, 2024 by Sally MacFarlane Accounts Having the following accounts is necessary for contributing code/issues to Besu.  Let us know using Besu chat channels that your PR is ready for review. keywords: besu; contribution; issue cache: lfhyperledger-First+contribution.html plain text: lfhyperledger-First+contribution.txt item: #2204 of 3327 id: lfhyperledger-Fixing+DCO+on+main+release author: lfhyperledger title: lfhyperledger-Fixing+DCO+on+main+release date: None words: 656 flesch: 12 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Plugin Services Tools we use Advanced Fixing DCO on main/release Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. git checkout release-22.1.x to checkout the release branch at the last release git merge main to merge in desired commits (use git reset --hard xxxx to set main at a desired commit) git rebase -i HEAD~10 to initiate a interactive rebase, replace 10 with the number of commits back that has DCO issues In the rebase file find the commit hashes with DCO issues, replace the 'pick' with 'edit' You might also need to fix some merge conflicts as the rebase happens, should be straight forward When the rebase stops at your desired commits, run git commit --amend --no-edit --signoff to signoff the commit Run git rebase --continue to continue, repeat steps 5-6 until done Push the changes with git push --force-with-lease origin release-22.1.2 , multiple selections available, Related content More info Collapse DCO DCO Besu More like this Release Process Release Process Besu More like this Documentation release process Documentation release process Besu More like this 2024-01-06 Mainnet Halting Event 2024-01-06 Mainnet Halting Event Besu More like this Changelog Improvement Proposal Changelog Improvement Proposal Besu More like this 2021-08-04 Value transfer public transactions being rejected by Besu 2021-08-04 Value transfer public transactions being rejected by Besu Besu More like this {serverDuration: 14, requestCorrelationId: 159bc603e44943c4a7d38df21d19b537} keywords: besu; git; main cache: lfhyperledger-Fixing+DCO+on+main+release.html plain text: lfhyperledger-Fixing+DCO+on+main+release.txt item: #2205 of 3327 id: lfhyperledger-Future+Release+Dates author: lfhyperledger title: lfhyperledger-Future+Release+Dates date: None words: 505 flesch: 43 summary: Close Besu / Future Release Dates More actions Future Release Dates Danno Ferrin Matt Nelson (Deactivated) Sally MacFarlane +3 Owned by Danno Ferrin Last updated: Jul 12, 2022 by Matt Nelson (Deactivated) Future Release Dates - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; release cache: lfhyperledger-Future+Release+Dates.html plain text: lfhyperledger-Future+Release+Dates.txt item: #2206 of 3327 id: lfhyperledger-GitHub+Merge+Queue author: lfhyperledger title: lfhyperledger-GitHub+Merge+Queue date: None words: 962 flesch: 28 summary: This feature is still in beta - discussion https://github.blog/changelog/2023-02-08-pull-request-merge-queue-public-beta/ Link to Besu merge queue (when enabled) would be https://github.com/hyperledger/besu/queue/main , multiple selections available, Related content More info Collapse DRAFT DOCUMENT - Best Practices for Automated Pipelines DRAFT DOCUMENT - Best Practices for Automated Pipelines Task Forces Feb 13, 2025 3 min read Update - disabled Feb 14 2025 branch protection (rulesets) set back to previous ie combined main + release* disallow force pushes to any branches Issues found still runs all the checks (GHA) on merge group (PR enters merge queue) even if the PR is up to date - so we double up on CI - I think even if the queue is empty, definitely if a PR is removed from the queue Merge Queue running checks twice? keywords: besu; merge; queue cache: lfhyperledger-GitHub+Merge+Queue.html plain text: lfhyperledger-GitHub+Merge+Queue.txt item: #2207 of 3327 id: lfhyperledger-Governance author: lfhyperledger title: lfhyperledger-Governance date: None words: 247 flesch: 38 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Hyperledger Besu Active Status Proposal Project Badge Status Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu cache: lfhyperledger-Governance.html plain text: lfhyperledger-Governance.txt item: #2208 of 3327 id: lfhyperledger-Gradle+Verification+Metadata author: lfhyperledger title: lfhyperledger-Gradle+Verification+Metadata date: None words: 428 flesch: 8 summary: --write-verification-metadata sha256 spotlessCheck from the doc https://docs.gradle.org/7.6/userguide/dependency_verification.html#sub:enabling-verification Full context discussion in Discord - https://discord.com/channels/905194001349627914/1118092168389742673/1118131135180976152 , multiple selections available, Related content More info Collapse Versioned documentation Versioned documentation Besu More like this Documentation release process Documentation release process Besu More like this Debugging Besu in IntelliJ Debugging Besu in IntelliJ Besu More like this Using CalVer for Besu Releases Using CalVer for Besu Releases Besu More like this Usage of vulnerability scanners Usage of vulnerability scanners Besu More like this Using Hive Test Suite Using Hive Test Suite Besu More like this {serverDuration: 34, requestCorrelationId: 87420a7ee06745979786fb8f1b736a1e} --write-verification-metadata sha256 spotlessCheck Besu uses verification metadata of dependency artifacts. keywords: besu; verification cache: lfhyperledger-Gradle+Verification+Metadata.html plain text: lfhyperledger-Gradle+Verification+Metadata.txt item: #2209 of 3327 id: lfhyperledger-Grants author: lfhyperledger title: lfhyperledger-Grants date: None words: 566 flesch: 50 summary: This includes compensation for engineers or their parent organizations (if any).  Related Docs CIP Splitter Contract Besu Contributor Call where grants were discussed with participants Process Based on the notes from the Jan 31 2023 contributor call (participants Danno, Web3Labs, CSI Besu team), the following process was suggested around grants:  Work-share decided amongst contributors that are interested in pursuing a grant: I.e. CSI pursues this grant and is the only group working on it, taking full split. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; grants cache: lfhyperledger-Grants.html plain text: lfhyperledger-Grants.txt item: #2210 of 3327 id: lfhyperledger-How+to+Contribute author: lfhyperledger title: lfhyperledger-How+to+Contribute date: None words: 303 flesch: 41 summary: In addition,  If you're even thinking about making any changes to Besu code, set up your github signoff so you don't have to worry about the DCO check. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu cache: lfhyperledger-How+to+Contribute.html plain text: lfhyperledger-How+to+Contribute.txt item: #2211 of 3327 id: lfhyperledger-How+to+do+a+Besu+Release author: lfhyperledger title: lfhyperledger-How+to+do+a+Besu+Release date: None words: 316 flesch: 10 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Release Rotations 2024 Using CalVer for Besu Releases How to do a Besu Release Off-cycle release process Release Process Obsolete Proposals and Policies Archive Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; release cache: lfhyperledger-How+to+do+a+Besu+Release.html plain text: lfhyperledger-How+to+do+a+Besu+Release.txt item: #2212 of 3327 id: lfhyperledger-How-to+articles author: lfhyperledger title: lfhyperledger-How-to+articles date: None words: 344 flesch: 5 summary: Close Besu / How-to articles More actions How-to articles Marek Tatara Owned by Marek Tatara Last updated: Jul 30, 2020Version comment Add how-to article Title Creator Modified Using Hive Test Suite Justin Florentine Apr 10, 2025 Decouple a class with Dagger - DRAFT Justin Florentine Aug 02, 2023 EIP-1559 testnet guide Abdelhamid Bakhta Nov 24, 2020 Ratified Smart Contract for Constrained Delivery with Oraclized Data Marek Tatara Aug 02, 2020 Deployment of Private Hyperledger Besu on AWS with hardware layer for Externally Owned Account Marek Tatara Jul 30, 2020 , multiple selections available, Related content More info Collapse Confluence Tips Article Confluence Tips Article Community Events More like this Documentation Documentation Besu More like this Documentation contribution guidelines Documentation contribution guidelines Besu More like this E-Books E-Books LFDT Labs More like this Reccomendations Research Reccomendations Research Learning Materials Development Working Group More like this Resource Library Resource Library Learning Materials Development Working Group More like this {serverDuration: 36, requestCorrelationId: fd7eb33c5197487ba83a9d5df39f87b4} Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Decouple a class with Dagger - DRAFT Deployment of Private Hyperledger Besu on AWS with hardware layer for Externally Owned Account EIP-1559 testnet guide Limit Trie Logs for Bonsai Maximum Validator count for an IBFT2 Network Ratified Smart Contract for Constrained Delivery with Oraclized Data Transaction testing Using Hive Test Suite Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: articles; besu cache: lfhyperledger-How-to+articles.html plain text: lfhyperledger-How-to+articles.txt item: #2213 of 3327 id: lfhyperledger-Hyperledger+Besu+Active+Status+Proposal author: lfhyperledger title: lfhyperledger-Hyperledger+Besu+Active+Status+Proposal date: None words: 2275 flesch: 46 summary: Hyperledger Besu team maintains a robust Documentation site that provides details on requirements, use cases, and other expectations for the project. Troy Ronda , multiple selections available, Related content More info Collapse 2020 Q1 Hyperledger Besu 2020 Q1 Hyperledger Besu Technical Oversight Committee More like this 2020 Q2 Hyperledger Besu 2020 Q2 Hyperledger Besu Technical Oversight Committee More like this Operate and Extend Hyperledger Besu Workshop Operate and Extend Hyperledger Besu Workshop Community Events More like this 2022 Q2 Hyperledger Besu 2022 Q2 Hyperledger Besu Technical Oversight Committee More like this 2022 Q3 Hyperledger Besu 2022 Q3 Hyperledger Besu Technical Oversight Committee More like this 10/16 10/16 Developer Relations More like this {serverDuration: 10, requestCorrelationId: 66c7e20f49f242f6a0878e4cb9bbf467} keywords: besu; community; documentation; hyperledger; license; pegasys; project cache: lfhyperledger-Hyperledger+Besu+Active+Status+Proposal.html plain text: lfhyperledger-Hyperledger+Besu+Active+Status+Proposal.txt item: #2214 of 3327 id: lfhyperledger-I+just+have+a+quick+question author: lfhyperledger title: lfhyperledger-I+just+have+a+quick+question date: None words: 298 flesch: 43 summary: PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. , multiple selections available, Related content More info Collapse Issues Issues Besu More like this How to Contribute How to Contribute Besu More like this Besu - Community Support Besu - Community Support Besu More like this Documentation Documentation Besu More like this Suggesting Enhancements Suggesting Enhancements Besu More like this Besu CLI Style Guide Besu CLI Style Guide Besu More like this {serverDuration: 36, requestCorrelationId: 4a9d439a94b64d9fa99cdcc51ad377f7} keywords: besu; question cache: lfhyperledger-I+just+have+a+quick+question.html plain text: lfhyperledger-I+just+have+a+quick+question.txt item: #2215 of 3327 id: lfhyperledger-Incident+Reports author: lfhyperledger title: lfhyperledger-Incident+Reports date: None words: 317 flesch: 27 summary: 2022-03-21 Meeting Notes Hyperledger Cacti More like this Security Team Policies Security Team Policies Hyperledger Security More like this 2021-01-12 Maintainers Agenda 2021-01-12 Maintainers Agenda Hyperledger Cacti More like this 2021-01-26 Maintainers Agenda 2021-01-26 Maintainers Agenda Hyperledger Cacti More like this Security Response Representation Security Response Representation Hyperledger Security More like this {serverDuration: 17, requestCorrelationId: 52fe1a36ba1c488b916f9921e4a58bb3} Jun 12, 2024 by Sally MacFarlane 2024-01-06 Mainnet Halting Event 2022-11-11 Fork on Sepolia 2022-05-30 Phishing PRs 2021-08-04 Value transfer public transactions being rejected by Besu 2021-04-23 ATs failures , multiple selections available, Related content More info Collapse 2020-01-27 Meeting notes 2020-01-27 Meeting notes Hyperledger India Regional Chapter More like this 2022-03-21 Meeting Notes keywords: security cache: lfhyperledger-Incident+Reports.html plain text: lfhyperledger-Incident+Reports.txt item: #2216 of 3327 id: lfhyperledger-Issues author: lfhyperledger title: lfhyperledger-Issues date: None words: 408 flesch: 42 summary: Close Besu / Issues More actions Issues Felipe Faraggi Sally MacFarlane Nicolas Massart Owned by Felipe Faraggi Last updated: May 27, 2024 by Sally MacFarlane Besu issues are tracked on GitHub. See our contribution guidelines for more details on searching and creating issues. keywords: besu; issues cache: lfhyperledger-Issues.html plain text: lfhyperledger-Issues.txt item: #2217 of 3327 id: lfhyperledger-Limit+Trie+Logs+for+Bonsai author: lfhyperledger title: lfhyperledger-Limit+Trie+Logs+for+Bonsai date: None words: 1804 flesch: 58 summary: | TrieLogHelper | Obtaining trielogs from db, this may take a few minutes... 2024-02-02 05:46:10.100+00:00 | main | INFO | TrieLogHelper | Clear trie logs... 2024-02-02 05:46:10.155+00:00 | main | INFO | TrieLogHelper | Restoring trie logs retained from batch 1... 2024-02-02 05:46:10.222+00:00 | main | INFO | TrieLogHelper | Key(0): 0xcd50706da7f6f2db7f9d54f3589122760900d9ab2508c20a4ca40b496d930368 ... 2024-02-02 05:46:10.336+00:00 | main | INFO | TrieLogSubCommand | Estimating trie logs size before pruning... 2024-02-02 05:45:43.837+00:00 | main | INFO | keywords: besu; bin; storage cache: lfhyperledger-Limit+Trie+Logs+for+Bonsai.html plain text: lfhyperledger-Limit+Trie+Logs+for+Bonsai.txt item: #2218 of 3327 id: lfhyperledger-Logging author: lfhyperledger title: lfhyperledger-Logging date: None words: 407 flesch: 38 summary: , multiple selections available, Related content More info Collapse Documentation Documentation Besu More like this Issues Issues Besu More like this Versioned documentation Versioned documentation Besu More like this Coding Conventions Coding Conventions Besu More like this How to Contribute How to Contribute Besu More like this Debugging Besu in IntelliJ Debugging Besu in IntelliJ Besu More like this Atlassian Intelligence {serverDuration: 34, requestCorrelationId: b1c9ceb9aaa543f38053661563784bdd} Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; logging cache: lfhyperledger-Logging.html plain text: lfhyperledger-Logging.txt item: #2219 of 3327 id: lfhyperledger-Mainnet+Consensus+Bug+Identified+and+Resolved+in+Hyperledger+Besu author: lfhyperledger title: lfhyperledger-Mainnet+Consensus+Bug+Identified+and+Resolved+in+Hyperledger+Besu date: None words: 1061 flesch: 52 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Release Rotations 2024 Using CalVer for Besu Releases How to do a Besu Release Off-cycle release process Release Process Obsolete Proposals and Policies Archive Critical Issue for Privacy Users Mainnet Consensus Bug Identified and Resolved in Hyperledger Besu Release 22.1.0 Release Process Improvement Release Remediation Release Rotations 2021 Release Rotations 2022 Release Rotations 2023 Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Close Besu / Mainnet Consensus Bug Identified and Resolved in Hyperledger Besu More actions Mainnet Consensus Bug Identified and Resolved in Hyperledger Besu Tim Beiko Owned by Tim Beiko Last updated: Dec 16, 2019 Summary: On December 13, 2019 a consensus issue related to the newly introduced SELFBALANCE opcode was found in Hyperledger Besu when trying to process mainnet block #9100883. keywords: besu; consensus; mainnet; release cache: lfhyperledger-Mainnet+Consensus+Bug+Identified+and+Resolved+in+Hyperledger+Besu.html plain text: lfhyperledger-Mainnet+Consensus+Bug+Identified+and+Resolved+in+Hyperledger+Besu.txt item: #2220 of 3327 id: lfhyperledger-Mainnet+activity+log+H1+2022 author: lfhyperledger title: lfhyperledger-Mainnet+activity+log+H1+2022 date: None words: 1506 flesch: -67 summary: Backwards Sync is now adding blocks to BadBlocksManager Backward Sync should remember recent finalized blocks Improving backwards sync Batching backward sync Backward sync Full sync: FullSync Future should stop when total terminal difficulty is reached Fast sync: Clear previous version fast sync runs data When downloading the world state, persist children before parents Miscelanious fixes: findSyncTarget always called with Optional.empty Return GOQUORUM_PRIVATE_STORAGE where it was before i broke it Maintainer GitHub handle: daniellehrner Maintainer org: ConsenSys Query for mainnet label on closed issues: https://github.com/hyperledger/besu/issues?q=is%3Aissue+is%3Aclosed+assignee%3Adaniellehrner+label%3Amainnet+ Details on mainnet contributions Update reference tests to the latest version and include test for gray glacier Gray glacier hard fork fcU: Remove check if new finalized is descendant from the previous one EngineForkchoiceUpdated: Verify if payload attributes are valid Subcommand blocks import throws exception Acceptance test for execution engine apis MERGE: Rename field random to prevRandao MERGE: Rename opcode RANDOM to PREVRANDAO MERGE: Add Kiln test vectors MERGE: Implement engine_exchangeTransitionConfigurationV1 API MERGE: extend semantics of executePayload / newPayload method Change payloadId of engine_forkchoiceUpdatedV1 API to fixed 8 bytes Maintainer GitHub handle: fab-10 Maintainer org: ConsenSys Query for mainnet label on closed PRs: https://github.com/hyperledger/besu/pulls?q=is%3Apr+author%3Afab-10+is%3Aclosed+label%3Amainnet Details on mainnet contributions Feature: The Merge switch to PoS Extend block parameter methods to accept 'finalized' and 'safe' as block tags Do not require a minimum block height when downloading headers or blocks Allow to backward sync to request headers back to last finalized block if present or genesis Replace deprecated INVALID_TERMINAL_BLOCK with INVALID lvh 0x0 Add PostMergeContext that will stop syncing after the switch to PoS Rename MergeOptions to MergeConfigOptions to follow the standard New MutableBlockchain method rewindToBlock by hash prerequisite for T… Merge: extend block creation and mining to support The Merge Merge: port of backward sync Merge: add terminal block number and hash to genesis config options Maintainer GitHub handle: macfarla Maintainer org: ConsenSys Query for mainnet label on closed PRs https://github.com/hyperledger/besu/pulls?q=is%3Apr+is%3Aclosed+author%3Amacfarla+label%3Amainnet Details on mainnet contributions Trace APIs - implement the remaining endpoints - worked with frankisawesome, mark-terry and pinges on these  trace_callMany #2886  trace_rawTransaction #2887  trace_get #2889 bugfix Prevent connecting to self enode  Fixed bug with contract address supplied to `debug_accountAt` Fixed bug where GraphQL any topic does not return any results Handle null pointer caused by empty json CI improvements LGTM config file preventing out of memory errors  CodeQL config file preventing out of memory errors Add trivy docker scan Separate CI steps for spotless and DCO Maintainer GitHub handle: pinges Maintainer org: ConsenSys Query for mainnet label on closed PRs https://github.com/hyperledger/besu/pulls?q=is%3Apr+author%3Apinges+is%3Aclosed+label%3Amainnet Details on mainnet contributions Trace APIs - implement the remaining endpoints - worked with frankisawesome, mark-terry and macfarla on these  trace_callMany #2886  trace_rawTransaction #2887  trace_get #2889 bugfix Fix Null pointer exception in VertxPeerDiscoveryController Maintainer GitHub handle: mark-terry Maintainer org: ConsenSys Query for mainnet label on closed PRs https://github.com/hyperledger/besu/pulls?q=is%3Apr+is%3Aclosed+author%3Amark-terry+label%3Amainnet Details on mainnet contributions Trace APIs - implement the remaining endpoints - worked with frankisawesome, pinges and macfarla on these  trace_callMany #2886  trace_rawTransaction #2887  trace_get #2889 Maintainer GitHub handle: frankisawesome Maintainer org: ConsenSys Query for mainnet label on closed PRs https://github.com/hyperledger/besu/pulls?q=is%3Apr+is%3Aclosed+author%3Afrankisawesome+label%3Amainnet Details on mainnet contributions Trace APIs - implement the remaining endpoints - worked with pinges, mark-terry and macfarla on these  trace_callMany #2886  trace_rawTransaction #2887  trace_get #2889 Allow optional API methods with no authentication Add uPNP only for P2P NAT method bugfix Fixed Null pointer exception in DeFramer Maintainer GitHub handle: taccatisid Maintainer org: ConsenSys Query for mainnet label on closed PRs https://github.com/hyperledger/besu/pulls?q=is%3Apr+is%3Aclosed+author%3Ataccatisid+label%3Amainnet Details on mainnet contributions code improvement Refactor timer from BesuRunner into TransactionPoolEvictionService Maintainer GitHub handle: wcgcyx Maintainer org: ConsenSys Query for mainnet label on closed PRs https://github.com/hyperledger/besu/pulls?q=is%3Apr+is%3Aclosed+author%3Awcgcyx+label%3Amainnet Details on mainnet contributions code improvement Make warnings consistent between CLI, ENV and TOML  Maintainer GitHub handle: siladu Maintainer org: ConsenSys Query for mainnet label on closed PRs https://github.com/hyperledger/besu/pulls?q=is%3Apr+is%3Aclosed+author%3Asiladu+label%3Amainnet Details on mainnet contributions code improvement Ensure port clash is reported when engine-rpc-port clashes with default websocket port Maintainer GitHub handle: matkt Query for mainnet label on closed PRs https://github.com/hyperledger/besu/pulls?q=is%3Apr+is%3Aclosed+author%3Amatkt+is%3Amerged Maintainer org: ConsenSys Details on mainnet contributions  Fix mainnet launcher issue https://github.com/hyperledger/besu/pull/3352 Snapsync implementation https://github.com/hyperledger/besu/pull/3572 https://github.com/hyperledger/besu/pull/3601 https://github.com/hyperledger/besu/pull/3625 https://github.com/hyperledger/besu/pull/3656 https://github.com/hyperledger/besu/pull/3703 https://github.com/hyperledger/besu/pull/3710 https://github.com/hyperledger/besu/pull/3754 https://github.com/hyperledger/besu/pull/3761 https://github.com/hyperledger/besu/pull/3773 https://github.com/hyperledger/besu/pull/3920 Checkpoint sync implementation https://github.com/hyperledger/besu/pull/3849 Fix ethstats issue https://github.com/hyperledger/besu/pull/3729 Fix issues on bonsai https://github.com/hyperledger/besu/pull/3712 (bonsai issue with fastsync) https://github.com/hyperledger/besu/pull/3645 (nullpointer on bonsai) https://github.com/hyperledger/besu/pull/3684 (bonsai storage modification to work with snapsync) keywords: consensys; details; label; mainnet; maintainer; org; prs; query cache: lfhyperledger-Mainnet+activity+log+H1+2022.html plain text: lfhyperledger-Mainnet+activity+log+H1+2022.txt item: #2221 of 3327 id: lfhyperledger-Mainnet+activity+log+H2+2022 author: lfhyperledger title: lfhyperledger-Mainnet+activity+log+H2+2022 date: None words: 638 flesch: 22 summary: GitHub query that may help `is:pr author:xyz label:mainnet closed:>2022-07-01` Maintainer org: Hedera Contact name - Contact email - Maintainer github handle: shemnon Is Besu Maintainer? Yes Query for mainnet label on merged PRs:  Details on mainnet contributions ... Maintainer org: Ethereum Classic Cooperative Contact name - Contact email - Maintainer github handle: diega Is Besu Maintainer? keywords: besu; mainnet; maintainer; query cache: lfhyperledger-Mainnet+activity+log+H2+2022.html plain text: lfhyperledger-Mainnet+activity+log+H2+2022.txt item: #2222 of 3327 id: lfhyperledger-Make+Besu+questions+easy+to+find+and+answer author: lfhyperledger title: lfhyperledger-Make+Besu+questions+easy+to+find+and+answer date: None words: 842 flesch: 37 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Agendas 2019 Agendas 2020 Agendas 2021 Agendas 2022 Agendas 2022-01-04 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-20 Besu Contributor Call 2022-01-31 Besu Contributor Call 2022-02-15 Contributor Call 2022-03-01 Contributor Call 2022-03-15 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-04-26 Contributor Call 2022-05-10 Contributor Call 2022-06-07 Contributor Call Make Besu questions easy to find and answer 2022-05-24 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-30 Contributor Call 2022-09-13 Contributor Call - APAC 2022-09-27 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-12-20 Contributor Call 2023 Agendas 2024 Agendas 2025 Agendas Notes Suspend APAC Contributor Call Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Make Besu questions easy to find and answer - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; contributor cache: lfhyperledger-Make+Besu+questions+easy+to+find+and+answer.html plain text: lfhyperledger-Make+Besu+questions+easy+to+find+and+answer.txt item: #2223 of 3327 id: lfhyperledger-Maximum+Validator+count+for+an+IBFT2+Network author: lfhyperledger title: lfhyperledger-Maximum+Validator+count+for+an+IBFT2+Network date: None words: 616 flesch: 31 summary:   At 35-38 validators, sustained load (5min+) saw the tx pool time grow and then halted the network at 38 validators , multiple selections available, Related content More info Collapse Validator Nodes Recommendations for HL Besu’s Incentive Program Validator Nodes Recommendations for HL Besu’s Incentive Program Besu More like this QBFT Performance QBFT Performance Besu More like this Modular Consensus Modular Consensus Besu More like this Hyperledger Besu Performance with Caliper Hyperledger Besu Performance with Caliper Hyperledger Mentorship Program More like this 2024 - Besu Performance Improvements since the Merge 2024 - Besu Performance Improvements since the Merge Besu More like this Performance analysis and Benchmarking of Besu using Caliper with complex workloads Performance analysis and Benchmarking of Besu using Caliper with complex workloads Hyperledger Mentorship Program More like this {serverDuration: 10, requestCorrelationId: 92a487b03d7c46fab3c82f295faeee0a} Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Decouple a class with Dagger - DRAFT Deployment of Private Hyperledger Besu on AWS with hardware layer for Externally Owned Account EIP-1559 testnet guide Limit Trie Logs for Bonsai Maximum Validator count for an IBFT2 Network Ratified Smart Contract for Constrained Delivery with Oraclized Data Transaction testing Using Hive Test Suite Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; performance; validators cache: lfhyperledger-Maximum+Validator+count+for+an+IBFT2+Network.html plain text: lfhyperledger-Maximum+Validator+count+for+an+IBFT2+Network.txt item: #2224 of 3327 id: lfhyperledger-Meetings author: lfhyperledger title: lfhyperledger-Meetings date: None words: 1232 flesch: -23 summary: Agendas 2023-12-05 Contributor Call - APAC Friendly Time 2023-11-28 Contributor Call 2023-11-07 Contributor Call - APAC Friendly Time 2023-10-31 Contributor Call 2023-10-10 Contributor Call - APAC Friendly Time 2023-10-02 Contributor Call - AMEA Friendly Time 2023-09-12 Contributor Call - APAC Friendly Time 2023-09-05 Contributor Call - EMEA Friendly Time 2023-08-15 Contributor Call - APAC Friendly Time 2023-08-01 Contributor Call 2023-07-18 Contributor Call - APAC Friendly Time - CANCELLED 2023-07-11 Contributor Call 2023-06-20 Contributor Call - APAC Friendly Time 2023-06-06 Contributor Call 2023-05-23 Contributor Call - APAC Friendly Time 2023-05-09 Contributor Call 2023-04-11 Contributor Call 2023-04-25 Contributor Call - APAC Friendly Time - CANCELLED 2023-03-28 Contributor Call - APAC Friendly Time 2023-03-14 Contributor Call 2023-02-28 Contributor Call - APAC Friendly Time 2023-02-14 Contributor Call 2023-01-31 Contributor Call - AMEA Reschedule 2023-01-31 Contributor Call - APAC Friendly Time 2023-01-17 Contributor Call 2023-01-03 Contributor Call - APAC Friendly Time 2022 Agendas 2022-12-20 Contributor Call 2022-12-06 Contributor Call - APAC Friendly Time 2022-11-22 Contributor Call 2022-11-08 Contributor Call - APAC Friendly Time 2022-10-25 Contributor Call 2022-10-11 Contributor Call - APAC Friendly Time 2022-09-27 Contributor Call 2022-09-13 Contributor Call - APAC 2022-08-30 Contributor Call 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-02 Contributor Call 2022-07-19 Contributor Call - APAC Friendly Time 2022-07-05 Contributor Call 2022-06-21 Contributor Call - APAC Friendly Time 2022-05-24 Contributor Call 2022-06-07 Contributor Call Make Besu questions easy to find and answer 2022-05-10 Contributor Call 2022-04-26 Contributor Call 2022-03-29 Contributor Call 2022-04-12 Contributor Call 2022-03-15 Contributor Call 2022-03-01 Contributor Call 2022-02-15 Contributor Call 2022-01-31 Besu Contributor Call 2022-01-20 Besu Contributor Call 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-04 Besu Contributor Call 2021 Agendas 2021-12-30 Besu Contributor Call (off cycle) 2021-12-07 Besu Contributor Call 2021-12-21 Besu Contributor Call 2021-11-09 Besu Contributor Call 2021-11-23 Besu Contributor Call 2021-10-11 Besu Contributor Call 2021-10-26 Besu Contributor Call 2021-09-28 Besu Contributor Call 2021-09-13 Besu Contributor Call 2021-08-31 Besu Contributor Call 2021-08-16 Besu Contributor Call 2021-08-03 Besu Contributor Call 2021-07-19 Besu Contributor Call 2021-07-06 Besu Contributor Call 2021-06-21 Besu Contributor Call 2021-06-08 Besu Contributor Call 2021-05-24 Besu Contributor Call 2021-05-11 Besu Office Hours 2021-04-26 Besu Office Hours 2021-04-13 Besu Contributor Call 2021-03-30 Besu Office Hours 2021-03-16 Besu Office Hours 2021-03-02 Besu Contributor Call 2021-02-16 Office Hours 2021-02-02 Office Hours 2021-01-19 Office Hours 2020 Agendas 2020-11-24 Office Hours 2020-10-27 Office Hours 2020-10-13 Hyperledger Besu Contributor Call 2020-09-29 Besu Contributor Call 2020-09-15 Contributor Call 2020-09-01 Contributor Call 2020-08-18 Contributor Call Agenda 2020-08-04 Contributor Call Agenda 2020-07-21 Contributor Call Agenda 2020-07-07 Contributor Call 2020-06-23 Besu Contributor Call Agenda 2020-06-09 Besu Contributor Call Agenda 2020-05-26 Contributor Call 2020-05-12 Contributor Call 2020-04-28 Contributor call 2020-04-14 Besu Contributor Call 2020-03-31 Besu Contributor Call 2020-03-17 Besu Contributor Call 2020-02-18 Besu Contributor Call 2020-02-04 Besu Contributor Call 2020-01-21 Besu Contributor Call 2020-01-07 Besu Contributor Call 2019 Agendas 2019-12-10 Besu Contributor Call 2019-11-26 Besu Contributor Call 2019-11-12 Besu Contributor Call 2019-10-29 Besu Contributor Call 2019-10-15 Besu Contributor Call 2019-10-01 Besu Contributor Call 2019-09-17 Besu Contributor Call , multiple selections available, Related content More info Collapse Monthly Organizer Meetings Monthly Organizer Meetings Community Events More like this 2019-07-13 Meeting notes 2019-07-13 Meeting notes Bootcamp Template (archived) Ry Jones Sally MacFarlane Danno Ferrin Owned by Ry Jones Last updated: Jan 29, 2024 by Sally MacFarlane Create meeting note Suspend APAC Contributor Call Notes 2020 Notes 2020-10-27 Office Hours Notes 2020-09-29 Besu Contributor Call Notes 2020-09-15 Contributor Call Notes 2020-09-01 Besu Contributor Call Notes 2020-08-18 Besu Contrubutor Call Notes 2020-08-04 Contributor Call Nodes 2020-07-21 Contributor Call Notes 2020-07-07 Contributor Call Notes 2020-06-23 Contributor Call Notes 2020-06-09 Contributor Call Notes 2020-05-26 Contributor Call Notes 2020-05-12 Contributor Call Notes 2020-04-28 Contributor Call Notes 2020-04-14 Contributor Call 2020-03-17 Contributor Call Notes 2020-02-18 Besu Contributor Call Notes 2020-02-04 Besu Contributor Call Notes 2020-01-21 Contributor Call 2020-01-07 Contributor Call 2022-1-31 Contributor Call notes 2021-01-19 Office Hours Notes 2019 Notes 2019-12-10 Contributor Call 2019-11-26 Contributor Call 2019-11-12 Contributor Call 2019-10-29 Contributor Call 2019-10-15 Contributor Call 2019-10-01 Contributor call 2019-09-17 Contributor call 2019-09-04 Onboarding call Agendas 2025 Agendas 2025-04-15 Contributor Call 2025-03-18 Contributor Call 2024 Agendas 2024-11-26 Contributor Call - US/AMEA 2024-09-03 Contributor Call - US/EMEA 2024-07-09 Contributor Call 2024-06-11 Contributor Call - US/EMEA 2024-04-16 Contributor Call - US/EMEA Friendly Time 2024-03-26 Contributor Call - APAC Friendly Time 2024-03-19 Contributor Call - US/EMEA Friendly Time 2024-02-27 Contributor Call - APAC Friendly Time 2024-02-20 Contributor Call - US/EMEA Friendly Time 2024-01-30 Contributor Call - APAC Friendly Time 2024-01-23 Contributor Call - AMEA Friendly Time 2024-01-02 Contributor Call - APAC Friendly Time - CANCELLED 2023 keywords: besu contributor; notes cache: lfhyperledger-Meetings.html plain text: lfhyperledger-Meetings.txt item: #2225 of 3327 id: lfhyperledger-Memory+usage+investigations+on+23.7.3-RC author: lfhyperledger title: lfhyperledger-Memory+usage+investigations+on+23.7.3-RC date: None words: 1574 flesch: 56 summary: This particular release comes with some GC flags enabled by default, which are designed to minimize Besu memory usage (-XX:G1ConcRefinementThreads=2 -XX:G1HeapWastePercent=15 -XX:MaxGCPauseMillis=100). Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability 2024 - Besu Performance Improvements since the Merge Fast sync optimisation Memory usage investigations on 23.7.3-RC Permissioned chain performance testing Q4 2022 Stability and Performance Improvements Reduce Memory usage by choosing a different low level allocator Testing Taskforce Brainstorming How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: heap; memory; release; usage cache: lfhyperledger-Memory+usage+investigations+on+23.7.3-RC.html plain text: lfhyperledger-Memory+usage+investigations+on+23.7.3-RC.txt item: #2226 of 3327 id: lfhyperledger-MkDocs+and+Markdown+guide author: lfhyperledger title: lfhyperledger-MkDocs+and+Markdown+guide date: None words: 281 flesch: 3 summary: Code of Conduct Contributing Developing and Conventions Documentation Documentation contribution workflow Documentation contribution guidelines Versioned documentation Documentation archive Documentation release process Documentation style guide Future Release Dates MkDocs and Markdown guide Configure and format Markdown Preview the documentation Extensions Proposal - Besu maintainers become docs maintainers Raise issues Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; documentation cache: lfhyperledger-MkDocs+and+Markdown+guide.html plain text: lfhyperledger-MkDocs+and+Markdown+guide.txt item: #2227 of 3327 id: lfhyperledger-Modular+Besu author: lfhyperledger title: lfhyperledger-Modular+Besu date: None words: 2363 flesch: 54 summary: Modular components may be Besu components or completely novel components that work with Besu via documented interfaces (i.e. a Rust EVM). Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Design Documents Ethereum Classic Support Feature Proposal Template Feature Flags RPC Endpoint Service Switchable Consensus Parameters Bonsai Tries Design Overview Refactor EVM into a stand alone library SECP256R1 Support DRAFT - Pico CLI Plugin Integration Besu 2022 Vision Modular Besu Besu as a Modular Client for the Merge (OLD) DRAFT - Besu Software Component Map Modular Consensus Modularity Implementation Approach CI/CD Migration Change to Besu Defaults - Q1 2024 CI/CD Tooling and Process Bonsai archive feature Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; cases; client; components; consensus; modular; use; work cache: lfhyperledger-Modular+Besu.html plain text: lfhyperledger-Modular+Besu.txt item: #2228 of 3327 id: lfhyperledger-Modular+Consensus author: lfhyperledger title: lfhyperledger-Modular+Consensus date: None words: 585 flesch: 7 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Design Documents Ethereum Classic Support Feature Proposal Template Feature Flags RPC Endpoint Service Switchable Consensus Parameters Bonsai Tries Design Overview Refactor EVM into a stand alone library SECP256R1 Support DRAFT - Pico CLI Plugin Integration Besu 2022 Vision Modular Besu Besu as a Modular Client for the Merge (OLD) DRAFT - Besu Software Component Map Modular Consensus Modularity Implementation Approach CI/CD Migration Change to Besu Defaults - Q1 2024 CI/CD Tooling and Process Bonsai archive feature Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Not all of these may be possible, but starting with them in mind will help us identify when we have deviated from them, and make sure appropriate docs etc are written to help users migrate: An existing Besu user can stop their Besu node, pull the new modular Besu image, and restart their Besu node without resyncing The user experience of running a Besu QBFT chain is unchanged A Besu QBFT node can be run in a single runtime BFT-related metrics continue to be produced without name changes Existing BFT-specific configuration is honoured (config or genesis file settings) No additional ports are required to be opened to run a module Besu QBFT network i.e. BFT validator peering logic continues to run over the standard P2P port , multiple selections available, Related content More info Collapse Modularity Implementation Approach Modularity Implementation Approach Besu Read with this Project Plan - Support Clique Consensus for Besu on HL Labs Blockchain Automation Framework Project Plan - Support Clique Consensus for Besu on HL Labs Blockchain Automation Framework Hyperledger Mentorship Program keywords: besu; consensus; modular cache: lfhyperledger-Modular+Consensus.html plain text: lfhyperledger-Modular+Consensus.txt item: #2229 of 3327 id: lfhyperledger-Modularity+Implementation+Approach author: lfhyperledger title: lfhyperledger-Modularity+Implementation+Approach date: None words: 935 flesch: 43 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Design Documents Ethereum Classic Support Feature Proposal Template Feature Flags RPC Endpoint Service Switchable Consensus Parameters Bonsai Tries Design Overview Refactor EVM into a stand alone library SECP256R1 Support DRAFT - Pico CLI Plugin Integration Besu 2022 Vision Modular Besu Besu as a Modular Client for the Merge (OLD) DRAFT - Besu Software Component Map Modular Consensus Modularity Implementation Approach CI/CD Migration Change to Besu Defaults - Q1 2024 CI/CD Tooling and Process Bonsai archive feature Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. , multiple selections available, Related content More info Collapse Modular Consensus Modular Consensus Besu More like this Modular Besu Modular Besu Besu More like this Refactor EVM into a stand alone library Refactor EVM into a stand alone library Besu More like this Besu as a Modular Client for the Merge (OLD) Besu as a Modular Client for the Merge (OLD) Besu More like this Besu Plug-ins: Fork-free Client Modifications to Extend Besu Use Cases Besu Plug-ins: Fork-free Client Modifications to Extend Besu Use Cases Community Events More like this DRAFT - Besu Software Component Map DRAFT - Besu Software Component Map Besu More like this {serverDuration: 15, requestCorrelationId: 418df2091e5c4d3e9aee17e42ebbacac} keywords: besu; client; consensus; modular; software cache: lfhyperledger-Modularity+Implementation+Approach.html plain text: lfhyperledger-Modularity+Implementation+Approach.txt item: #2230 of 3327 id: lfhyperledger-Near-Term+Besu+Incentive+Program+proposal author: lfhyperledger title: lfhyperledger-Near-Term+Besu+Incentive+Program+proposal date: None words: 721 flesch: 49 summary: , multiple selections available, Related content More info Collapse Besu Execution Client Incentive Program Besu Execution Client Incentive Program Besu More like this Second Incentive Proposal Second Incentive Proposal Besu More like this Validator Nodes Recommendations for HL Besu’s Incentive Program Validator Nodes Recommendations for HL Besu’s Incentive Program Besu More like this Grants Grants Besu More like this [WIP] Proposal #4 [WIP] Proposal #4 Besu More like this Proposal #3.5 Proposal #3.5 Besu More like this {serverDuration: 13, requestCorrelationId: 02d3920c7a7f42e998ddc6b6dec1b6df} Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Besu Execution Client Incentive Program keywords: besu; incentive; proposal cache: lfhyperledger-Near-Term+Besu+Incentive+Program+proposal.html plain text: lfhyperledger-Near-Term+Besu+Incentive+Program+proposal.txt item: #2231 of 3327 id: lfhyperledger-Notes author: lfhyperledger title: lfhyperledger-Notes date: None words: 270 flesch: 35 summary: More like this 2019-07-23 Meeting notes 2019-07-23 Meeting notes Supply Chain SIG More like this 2019-05-07 Meeting notes 2019-05-07 Meeting notes Supply Chain SIG More like this 2020-02-20 Meeting notes 2020-02-20 Meeting notes Hyperledger India Regional Chapter More like this {serverDuration: 11, requestCorrelationId: 9397dd8597714ea59cb133711ad22b5e} Atlassian cookies and tracking notice, (opens new window) keywords: notes cache: lfhyperledger-Notes.html plain text: lfhyperledger-Notes.txt item: #2232 of 3327 id: lfhyperledger-Obsolete+Proposals+and+Policies author: lfhyperledger title: lfhyperledger-Obsolete+Proposals+and+Policies date: None words: 429 flesch: 25 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Release Rotations 2024 Using CalVer for Besu Releases How to do a Besu Release Off-cycle release process Release Process Obsolete Proposals and Policies Bi-Weekly & Quarterly Release Process Process change proposal: burn-in Proposal for Off-Cycle, Delayed, and Scuttled Releases Proposal: Avoid Cherry Picked Releases Proposal: Create a Release Candidate for every release Proposal: Increasing 1.4 RC/Beta window Proposal: Quarterly releases from main by default Release Philosophy Archive Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: proposal; release cache: lfhyperledger-Obsolete+Proposals+and+Policies.html plain text: lfhyperledger-Obsolete+Proposals+and+Policies.txt item: #2233 of 3327 id: lfhyperledger-Off-cycle+release+process author: lfhyperledger title: lfhyperledger-Off-cycle+release+process date: None words: 529 flesch: 35 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Release Rotations 2024 Using CalVer for Besu Releases How to do a Besu Release Off-cycle release process Release Process Obsolete Proposals and Policies Archive Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Justification for release (examples) critical bug affecting a number of users which requires a patch regular release process will not address the issue in time urgent security issue discovered Justification for objection (examples) technology X introduced is bad for Y reasons , multiple selections available, Related content More info Collapse Release Process Release Process Besu More like this Release Process Improvement Release Process Improvement Besu More like this Release Rotations 2024 Release Rotations 2024 Besu More like this Release Rotations 2022 Release Rotations 2022 Besu More like this Proposal: Avoid Cherry Picked Releases Proposal: Avoid Cherry Picked Releases Besu More like this Proposal: keywords: besu; release cache: lfhyperledger-Off-cycle+release+process.html plain text: lfhyperledger-Off-cycle+release+process.txt item: #2234 of 3327 id: lfhyperledger-Optimism+RPGF+5 author: lfhyperledger title: lfhyperledger-Optimism+RPGF+5 date: None words: 297 flesch: -3 summary: Close Besu / Optimism RPGF 5 More actions Optimism RPGF 5 Matt Nelson (Deactivated) Sally MacFarlane Owned by Matt Nelson (Deactivated) Last updated: Oct 10, 2024 by Sally MacFarlane Round 5 https://gov.optimism.io/t/retro-funding-5-application-review-process/8730/4 Besu round 5 application https://app.charmverse.io/op-retrofunding-review-process/page-3880959421107215  Spreadsheet of voting so far https://docs.google.com/spreadsheets/d/11ED8NBnC9ag7fw9d033W0JkSYrpf7gttxYmy3SpprTg/edit?gid=781985670#gid=781985670 Round sizing - Retro Funding 5: OP Stack - round details KYC & Grant delivery - Retro Funding 5: OP Stack - round details , multiple selections available, Related content More info Collapse Optimism RetroPGF Optimism RetroPGF Besu More like this TSC Election 2020-2021 Plan TSC Election 2020-2021 Plan Technical Oversight Committee More like this 2022-1-31 Contributor Call notes 2022-1-31 Contributor Call notes Besu More like this Evaluation Criteria - Prototype Phase Evaluation Criteria - Prototype Phase Community Events More like this Calling for Nominations Calling for Nominations Technical Oversight Committee More like this TSC Election voters selection TSC Election voters selection Technical Oversight Committee More like this Atlassian Intelligence {serverDuration: 12, requestCorrelationId: e2d02696790a4050b25addd859f2750b} PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; optimism cache: lfhyperledger-Optimism+RPGF+5.html plain text: lfhyperledger-Optimism+RPGF+5.txt item: #2235 of 3327 id: lfhyperledger-Optimism+RetroPGF author: lfhyperledger title: lfhyperledger-Optimism+RetroPGF date: None words: 525 flesch: 48 summary: Besu team is active in Mainnet development. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; proposal cache: lfhyperledger-Optimism+RetroPGF.html plain text: lfhyperledger-Optimism+RetroPGF.txt item: #2236 of 3327 id: lfhyperledger-Performance+Stability author: lfhyperledger title: lfhyperledger-Performance+Stability date: None words: 335 flesch: 21 summary: Development and architecture recommendations to get maximal performances out of new features and code changes ... , multiple selections available, Related content More info Collapse Q4 2022 Stability and Performance Improvements Q4 2022 Stability and Performance Improvements Besu More like this Issues Issues Besu More like this 2024 - Besu Performance Improvements since the Merge 2024 - Besu Performance Improvements since the Merge Besu Read with this Besu Roadmap & Planning Besu Roadmap & Planning Besu More like this Documentation Documentation Besu More like this I just have a quick question I just have a quick question Besu More like this Atlassian Intelligence {serverDuration: 12, requestCorrelationId: c051106e8b9e4eb0b5ac86a240776164} Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability 2024 - Besu Performance Improvements since the Merge Fast sync optimisation Memory usage investigations on 23.7.3-RC Permissioned chain performance testing Q4 2022 Stability and Performance Improvements Reduce Memory usage by choosing a different low level allocator Testing Taskforce Brainstorming How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; performance cache: lfhyperledger-Performance+Stability.html plain text: lfhyperledger-Performance+Stability.txt item: #2237 of 3327 id: lfhyperledger-Permissioned+chain+performance+testing author: lfhyperledger title: lfhyperledger-Permissioned+chain+performance+testing date: None words: 376 flesch: 10 summary: See sub-pages for the different scenarios currently being exercised. , multiple selections available, Related content More info Collapse Testing Distributed Systems Testing Distributed Systems BootCamp Russia (archived) More like this Hyperledger Caliper testability and robustness improvement Hyperledger Caliper testability and robustness improvement Hyperledger Mentorship Program More like this Project Plan - Hyperledger Caliper testability and robustness improvement. Hyperledger Mentorship Program More like this One-stop-shop Hyperledger Fabric performance analysis with Hyperledger Caliper One-stop-shop Hyperledger Fabric performance analysis with Hyperledger Caliper Hyperledger Mentorship Program More like this Project plan - One-stop-shop Hyperledger Fabric performance analysis with Hyperledger Caliper (2023) keywords: hyperledger; performance cache: lfhyperledger-Permissioned+chain+performance+testing.html plain text: lfhyperledger-Permissioned+chain+performance+testing.txt item: #2238 of 3327 id: lfhyperledger-PermissioningService author: lfhyperledger title: lfhyperledger-PermissioningService date: None words: 414 flesch: 0 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Plugin Services BesuContext PermissioningService PrivacyPluginService RpcEndpointService Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; provider cache: lfhyperledger-PermissioningService.html plain text: lfhyperledger-PermissioningService.txt item: #2239 of 3327 id: lfhyperledger-Plugin+Services author: lfhyperledger title: lfhyperledger-Plugin+Services date: None words: 521 flesch: 30 summary: , multiple selections available, Related content More info Collapse Repositories and other projects Repositories and other projects Besu More like this Client Connector for Hyperledger Besu Client Connector for Hyperledger Besu Hyperledger Mentorship Program More like this Besu - Community Support Besu - Community Support Besu More like this 09/23/24 09/23/24 Developer Relations More like this 2020 Q2 Hyperledger Besu 2020 Q2 Hyperledger Besu Technical Oversight Committee More like this BesuContext BesuContext Besu More like this {serverDuration: 12, requestCorrelationId: b7a269e1aeff488abe1a99f6b5f2e125} PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; events; interface cache: lfhyperledger-Plugin+Services.html plain text: lfhyperledger-Plugin+Services.txt item: #2240 of 3327 id: lfhyperledger-Policies author: lfhyperledger title: lfhyperledger-Policies date: None words: 281 flesch: 21 summary: Close Besu / Policies More actions Policies Christopher Hare Owned by Christopher Hare Last updated: Nov 28, 2019 Defect Prioritisation Policy , multiple selections available, Related content More info Collapse Policies and Procedures Policies and Procedures LF Decentralized Trust More like this Common Maintainers management policy Common Maintainers management policy Technical Oversight Committee More like this Defect Prioritisation Policy Defect Prioritisation Policy Besu More like this TF-SIG Meeting - 2019.01.08 Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Defect Prioritisation Policy Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; meeting cache: lfhyperledger-Policies.html plain text: lfhyperledger-Policies.txt item: #2241 of 3327 id: lfhyperledger-Prague+Planning author: lfhyperledger title: lfhyperledger-Prague+Planning date: None words: 789 flesch: 54 summary: Less complexity of adding EOF EVM and adding risk Verkle functionality improvements (getting the stuff faster)  More time for L2s to adopt EOF Verkle not mandatory for immediate fork coverage  Cons More time to work on Verkle if we ship second  , multiple selections available, Related content More info Collapse 2022-02-15 Contributor Call 2022-02-15 Contributor Call Besu More like this 2022-08-16 Contributor Call - APAC Friendly Time 2022-08-16 Contributor Call - APAC Friendly Time Besu More like this 2023-10-31 Contributor Call 2023-10-31 Contributor Call Besu More like this 2020-06-09 Besu Contributor Call Agenda 2020-06-09 Besu Contributor Call Agenda Besu More like this 2024-02-20 Contributor Call - US/EMEA Friendly Time 2024-02-20 Contributor Call - US/EMEA Friendly Time Besu More like this 2022-01-11 Besu Contributor Call - Off-Cycle 2022-01-11 Besu Contributor Call - Off-Cycle Besu More like this {serverDuration: 14, requestCorrelationId: 60c55989c02c45cf80cb900a9682be29} PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; cfi; contributor; time; verkle cache: lfhyperledger-Prague+Planning.html plain text: lfhyperledger-Prague+Planning.txt item: #2242 of 3327 id: lfhyperledger-Preview+the+documentation author: lfhyperledger title: lfhyperledger-Preview+the+documentation date: None words: 657 flesch: 36 summary: Code of Conduct Contributing Developing and Conventions Documentation Documentation contribution workflow Documentation contribution guidelines Versioned documentation Documentation archive Documentation release process Documentation style guide Future Release Dates MkDocs and Markdown guide Configure and format Markdown Preview the documentation Extensions Proposal - Besu maintainers become docs maintainers Raise issues Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; documentation; preview cache: lfhyperledger-Preview+the+documentation.html plain text: lfhyperledger-Preview+the+documentation.txt item: #2243 of 3327 id: lfhyperledger-PrivacyPluginService author: lfhyperledger title: lfhyperledger-PrivacyPluginService date: None words: 557 flesch: -21 summary: Parameters: privacyGroupAuthProvider - the provider to use to determine authz getPrivacyGroupAuthProvider PrivacyGroupAuthProvider getPrivacyGroupAuthProvider() setPrivacyGroupGenesisProvider void setPrivacyGroupGenesisProvider​(PrivacyGroupGenesisProvider privacyGroupAuthProvider) Register a provider for initialising private state genesisParameters: privacyGroupAuthProvider - the provider for the initial private state getPrivacyGroupGenesisProvider PrivacyGroupGenesisProvider getPrivacyGroupGenesisProvider() , multiple selections available, Related content More info Collapse 2023-07-17 AnonCreds Specification Working Group Meeting 2023-07-17 AnonCreds Specification Working Group Meeting Hyperledger AnonCreds More like this 2023-05-08 AnonCreds Specification Working Group Meeting 2023-05-08 AnonCreds Specification Working Group Meeting Hyperledger AnonCreds More like this 2020-09-15 Contributor Call Notes 2020-09-15 Contributor Call Notes Besu More like this 2023-05-01 AnonCreds v2.0 Working Group Meeting 2023-05-01 AnonCreds v2.0 Working Group Meeting Hyperledger AnonCreds More like this 2023-06-26 AnonCreds v2.0 Working Group Meeting 2023-06-26 AnonCreds v2.0 Working Group Meeting Hyperledger AnonCreds More like this 2022-12-19 AnonCreds Specification Working Group Meeting 2022-12-19 AnonCreds Specification Working Group Meeting Hyperledger AnonCreds More like this {serverDuration: 14, requestCorrelationId: b77e9ee81e8e473a88bed6590d3c8375} Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Plugin Services BesuContext PermissioningService PrivacyPluginService RpcEndpointService Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: anoncreds; group; working cache: lfhyperledger-PrivacyPluginService.html plain text: lfhyperledger-PrivacyPluginService.txt item: #2244 of 3327 id: lfhyperledger-Process+change+proposal+burn-in author: lfhyperledger title: lfhyperledger-Process+change+proposal+burn-in date: None words: 697 flesch: 45 summary: the application of release tags could be isolated to a workflow that just promotes from draft, using those tags , multiple selections available, Related content More info Collapse Release Process Improvement Release Process Improvement Besu More like this Release Process Release Process Besu More like this CI/CD Tooling and Process CI/CD Tooling and Process Besu More like this Off-cycle release process Off-cycle release process Besu More like this Proposal: Avoid Cherry Picked Releases Proposal: Avoid Cherry Picked Releases Besu More like this 2022-01-04 Besu Contributor Call 2022-01-04 Besu Contributor Call Besu More like this {serverDuration: 12, requestCorrelationId: 8412e29db68b48feb9ac7c93f7bb888f} Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Release Rotations 2024 Using CalVer for Besu Releases How to do a Besu Release Off-cycle release process Release Process Obsolete Proposals and Policies Bi-Weekly & Quarterly Release Process Process change proposal: burn-in Proposal for Off-Cycle, Delayed, and Scuttled Releases Proposal: Avoid Cherry Picked Releases Proposal: Create a Release Candidate for every release Proposal: keywords: besu; process; release cache: lfhyperledger-Process+change+proposal+burn-in.html plain text: lfhyperledger-Process+change+proposal+burn-in.txt item: #2245 of 3327 id: lfhyperledger-Programs+Grants author: lfhyperledger title: lfhyperledger-Programs+Grants date: None words: 438 flesch: 48 summary: On this page you will be able to find Besu ongoing programs. To learn more about Besu Execution Client Incentive Program, visit this page. keywords: besu; grants cache: lfhyperledger-Programs+Grants.html plain text: lfhyperledger-Programs+Grants.txt item: #2246 of 3327 id: lfhyperledger-Project+Badge+Status author: lfhyperledger title: lfhyperledger-Project+Badge+Status date: None words: 622 flesch: 38 summary: CII The most recent CII report for Hyperledger Besu. , multiple selections available, Related content More info Collapse 2025-03-18 Contributor Call 2025-03-18 Contributor Call Besu More like this Repositories and other projects Repositories and other projects Besu More like this Programs & Grants Programs & Grants Besu More like this Besu - Community Support Besu - Community Support Besu More like this Besu Besu Besu More like this Versioned documentation Versioned documentation Besu More like this {serverDuration: 12, requestCorrelationId: 585ec41f4f0f49a5bdcab64383f62d9e} Testing Besu has robust unit, integration, and acceptance tests run with each main branch build that validate Besu behaves as expected, as well as reference tests maintained by Ethereum core developers to check for mainnet standards compliance. keywords: besu; ethereum; hyperledger cache: lfhyperledger-Project+Badge+Status.html plain text: lfhyperledger-Project+Badge+Status.txt item: #2247 of 3327 id: lfhyperledger-Proposal+-+Besu+maintainers+become+docs+maintainers author: lfhyperledger title: lfhyperledger-Proposal+-+Besu+maintainers+become+docs+maintainers date: None words: 481 flesch: 33 summary: Just as we expect besu maintainers to use their judgment when reviewing besu PRs, we expect besu-docs maintainers to use their judgment when reviewing besu-docs PRs. Since we trust besu maintainers to make changes to the code, this proposal is to also trust those individuals to make changes to the related docs. keywords: besu; docs cache: lfhyperledger-Proposal+-+Besu+maintainers+become+docs+maintainers.html plain text: lfhyperledger-Proposal+-+Besu+maintainers+become+docs+maintainers.txt item: #2248 of 3327 id: lfhyperledger-Proposal+3 author: lfhyperledger title: lfhyperledger-Proposal+3 date: None words: 1742 flesch: 47 summary: This pool will be a directed donation towards Hyperledger Besu mainnet work paying for items including but not limited to: Payment of services consumed by the Hyperledger Besu project, such as Continuous Integration, Cloud Hosting fees for development (i.e. testnet nodes) source code hosting, any other such services directly related to development of mainnet capabilities in Hyperledger Besu Note: These costs are separate from any incurred by ConsenSys. Posting Bounties for work on Hyperledger Besu mainnet or mainnet related work Spending that would directly promote interoperability with Besu Mainnet functionality  Other spending that would directly promote and improve Hyperledger Besu Patronage Pool 60% will go to employers of maintainers (or where the employer designates). keywords: consensys; hyperledger; keys; mainnet; withdrawal cache: lfhyperledger-Proposal+3.html plain text: lfhyperledger-Proposal+3.txt item: #2249 of 3327 id: lfhyperledger-Proposal+3.5 author: lfhyperledger title: lfhyperledger-Proposal+3.5 date: None words: 1933 flesch: 41 summary: This pool will be a directed donation towards Hyperledger Besu mainnet work paying for items including but not limited to: Payment of services consumed by the Hyperledger Besu project, such as Continuous Integration, Cloud Hosting fees for development (i.e. testnet nodes) source code hosting, any other such services directly related to development of mainnet capabilities in Hyperledger Besu Note: These costs are separate from any incurred by any other participating organization. Posting Bounties for work on Hyperledger Besu mainnet or mainnet related work Spending that would directly promote interoperability with Besu Mainnet functionality  Other spending that would directly promote and improve Hyperledger Besu Patronage Pool The remaining 60% will go to patrons (or where the patron designates) proportional to the number of qualifying maintainers they employ (or to HLF for maintainers without patrons). keywords: besu; keys; mainnet; transaction; withdrawal cache: lfhyperledger-Proposal+3.5.html plain text: lfhyperledger-Proposal+3.5.txt item: #2250 of 3327 id: lfhyperledger-Proposal+Avoid+Cherry+Picked+Releases author: lfhyperledger title: lfhyperledger-Proposal+Avoid+Cherry+Picked+Releases date: None words: 1131 flesch: 53 summary: Increasing 1.4 RC/Beta window Proposal: Quarterly releases from main by default Release Philosophy Archive Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Adding to an existing RC branch during quarterly releases Adding hotfixes to a point release In both cases we have to do this because unstable commits are blocking releasing from the main branch. keywords: besu; process; proposal; release cache: lfhyperledger-Proposal+Avoid+Cherry+Picked+Releases.html plain text: lfhyperledger-Proposal+Avoid+Cherry+Picked+Releases.txt item: #2251 of 3327 id: lfhyperledger-Proposal+Create+a+Release+Candidate+for+every+release author: lfhyperledger title: lfhyperledger-Proposal+Create+a+Release+Candidate+for+every+release date: None words: 577 flesch: 29 summary: Increasing 1.4 RC/Beta window Proposal: Quarterly releases from main by default Release Philosophy Archive Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Close Besu / Proposal: Create a Release Candidate for every release More actions Proposal: Create a Release Candidate for every release Edward Evans Sally MacFarlane Owned by Edward Evans Last updated: Apr 28, 2020 by Sally MacFarlane Summary: Have every release go through a RC process for testing and evaluation of untestable requirements Background We have had several point releases have significant errors discovered after the release has been cut and announced. keywords: proposal; release cache: lfhyperledger-Proposal+Create+a+Release+Candidate+for+every+release.html plain text: lfhyperledger-Proposal+Create+a+Release+Candidate+for+every+release.txt item: #2252 of 3327 id: lfhyperledger-Proposal+Discord+Server+Pub+Priv+Channel+Split author: lfhyperledger title: lfhyperledger-Proposal+Discord+Server+Pub+Priv+Channel+Split date: None words: 426 flesch: 31 summary: We could also consider new discord roles to tag certain sets of maintainers (i.e. public-focused maintainer) Thoughts and feedback on this proposal are welcome! , multiple selections available, Related content More info Collapse Transition to Discord Proposal Transition to Discord Proposal Task Forces More like this Create a Discord Chat Category and Channels Create a Discord Chat Category and Channels Community Architects More like this Chat Channels Chat Channels Community Architects More like this 2019 Q4 Hyperledger Besu 2019 Q4 Hyperledger Besu Technical Oversight Committee More like this Besu - Community Support Besu - Community Support Besu More like this Make Besu questions easy to find and answer Make Besu questions easy to find and answer Besu More like this {serverDuration: 16, requestCorrelationId: b1a03646c5634836b8c3b968ba08803c} PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; discord cache: lfhyperledger-Proposal+Discord+Server+Pub+Priv+Channel+Split.html plain text: lfhyperledger-Proposal+Discord+Server+Pub+Priv+Channel+Split.txt item: #2253 of 3327 id: lfhyperledger-Proposal+Increasing+1.4+RC+Beta+window author: lfhyperledger title: lfhyperledger-Proposal+Increasing+1.4+RC+Beta+window date: None words: 722 flesch: 45 summary:   However going with a longer RC window reduces the amount of time we are off of bi-weekly agile releases. , multiple selections available, {serverDuration: 12, requestCorrelationId: da674acf3e2b421cb3170f5e0fd611d4} Ship the Tuweni PR as the first commit after we stop 1.3 support Including Plugin API changes Status Quo No schedule changes Ship the Tuweni PR when it is ready with all others in a bi-weekly release Maybe do plugin API changes as part of the 1.4 release The down side of the status quo approach is that it provides a very limited window to co-ordinate the use of the plugin APIs by downstream consumers, about 2 weeks or less. keywords: proposal; release cache: lfhyperledger-Proposal+Increasing+1.4+RC+Beta+window.html plain text: lfhyperledger-Proposal+Increasing+1.4+RC+Beta+window.txt item: #2254 of 3327 id: lfhyperledger-Proposal+Quarterly+releases+from+main+by+default author: lfhyperledger title: lfhyperledger-Proposal+Quarterly+releases+from+main+by+default date: None words: 553 flesch: 44 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Release Rotations 2024 Using CalVer for Besu Releases How to do a Besu Release Off-cycle release process Release Process Obsolete Proposals and Policies Bi-Weekly & Quarterly Release Process Process change proposal: burn-in Proposal for Off-Cycle, Delayed, and Scuttled Releases Proposal: Avoid Cherry Picked Releases Proposal: Create a Release Candidate for every release Proposal: Quarterly releases from main by default - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: proposal; release cache: lfhyperledger-Proposal+Quarterly+releases+from+main+by+default.html plain text: lfhyperledger-Proposal+Quarterly+releases+from+main+by+default.txt item: #2255 of 3327 id: lfhyperledger-Proposal+for+Off-Cycle+Delayed+and+Scuttled+Releases author: lfhyperledger title: lfhyperledger-Proposal+for+Off-Cycle+Delayed+and+Scuttled+Releases date: None words: 1468 flesch: 54 summary: Scheduled releases proceed on a without objection basis, where it is presumed that there is consensus to proceed.  Scheduled releases are to be done without objection and if one party formally objects then a formal vote is required of the committee. keywords: change; committee; cycle; release cache: lfhyperledger-Proposal+for+Off-Cycle+Delayed+and+Scuttled+Releases.html plain text: lfhyperledger-Proposal+for+Off-Cycle+Delayed+and+Scuttled+Releases.txt item: #2256 of 3327 id: lfhyperledger-Pull+Requests author: lfhyperledger title: lfhyperledger-Pull+Requests date: None words: 809 flesch: 58 summary: One way to do this if, for some reason, the change has to all go in the codebase at once, is to have a PR open on the Besu repository linking to smaller PRs on your Besu fork. Close Besu / Pull Requests More actions Pull Requests Felipe Faraggi Sally MacFarlane Nicolas Massart Owned by Felipe Faraggi Last updated: Sept 15, 2024 by Sally MacFarlane Pull Requests keywords: besu; pull cache: lfhyperledger-Pull+Requests.html plain text: lfhyperledger-Pull+Requests.txt item: #2257 of 3327 id: lfhyperledger-Q4+2022+Stability+and+Performance+Improvements author: lfhyperledger title: lfhyperledger-Q4+2022+Stability+and+Performance+Improvements date: None words: 1456 flesch: 37 summary: Losing many peers  Because threads were blocked, we lost many peers  Vertx for example uses different approaches to threading   Solution: ?? Issues on user experience  Difficulty in reliably communicating with new/inexperienced users Docs & lack of education  More complicated set up post-merge Solution: Write up ‘What to expect from staking at home’ and FAQ for Besu Docs Out of Memory errors Documentation on how kind of memory config is needed  No mechanism to detect memory leaks  Potential mitigation: make deploying Besu easier by providing default configs  Solution: ?? Establish better process on how to respond to the problem we discover  Good case study: sepolia issue over the weekend on Oct 29/30 , multiple selections available, Related content More info Collapse Performance & Stability Performance & Stability Besu Read with this 2024 - Besu Performance Improvements since the Merge 2024 - Besu Performance Improvements since the Merge Besu Read with this Modular Consensus Modular Consensus Besu More like this 2025-03-18 Contributor Call 2025-03-18 Contributor Call Besu More like this 2024-09-03 Contributor Call - US/EMEA 2024-09-03 Contributor Call - US/EMEA Besu More like this Besu Roadmap & Planning Besu Roadmap & Planning Besu More like this {serverDuration: 13, requestCorrelationId: b42ddd2ccd65455d826c4aa694fad406} keywords: besu; improvements; need; performance; solution cache: lfhyperledger-Q4+2022+Stability+and+Performance+Improvements.html plain text: lfhyperledger-Q4+2022+Stability+and+Performance+Improvements.txt item: #2258 of 3327 id: lfhyperledger-QBFT+Bonsai+and+Snap-Sync+testing author: lfhyperledger title: lfhyperledger-QBFT+Bonsai+and+Snap-Sync+testing date: None words: 487 flesch: 18 summary: The 4th node has Xsynchronizer-world-state-request-parallelism=1 set as without this, the account data range requests fail to all be marked as complete. , multiple selections available, Related content More info Collapse QBFT Performance QBFT Performance Besu More like this Besu Plug-ins: Fork-free Client Modifications to Extend Besu Use Cases Besu Plug-ins: Fork-free Client Modifications to Extend Besu Use Cases Community Events More like this Deliverables and Learnings - Performance analysis and Benchmarking of Besu using Caliper with complex workloads Deliverables and Learnings - Performance analysis and Benchmarking of Besu using Caliper with complex workloads Hyperledger Mentorship Program More like this 2021 Q4 Hyperledger Besu 2021 Q4 Hyperledger Besu Technical Oversight Committee More like this Modular Consensus Modular Consensus Besu More like this 2022 Q3 Hyperledger Besu 2022 Q3 Hyperledger Besu Technical Oversight Committee More like this {serverDuration: 43, requestCorrelationId: 4429a50acdcf4593803417f22655ee3a} Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability 2024 - Besu Performance Improvements since the Merge Fast sync optimisation Memory usage investigations on 23.7.3-RC Permissioned chain performance testing QBFT, Bonsai, and Snap-Sync testing QBFT Performance Q4 2022 Stability and Performance Improvements Reduce Memory usage by choosing a different low level allocator Testing Taskforce Brainstorming How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; qbft cache: lfhyperledger-QBFT+Bonsai+and+Snap-Sync+testing.html plain text: lfhyperledger-QBFT+Bonsai+and+Snap-Sync+testing.txt item: #2259 of 3327 id: lfhyperledger-QBFT+Performance author: lfhyperledger title: lfhyperledger-QBFT+Performance date: None words: 970 flesch: 30 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability 2024 - Besu Performance Improvements since the Merge Fast sync optimisation Memory usage investigations on 23.7.3-RC Permissioned chain performance testing QBFT, Bonsai, and Snap-Sync testing QBFT Performance Q4 2022 Stability and Performance Improvements Reduce Memory usage by choosing a different low level allocator Testing Taskforce Brainstorming How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; caliper; performance; qbft cache: lfhyperledger-QBFT+Performance.html plain text: lfhyperledger-QBFT+Performance.txt item: #2260 of 3327 id: lfhyperledger-RPC+Endpoint+Service author: lfhyperledger title: lfhyperledger-RPC+Endpoint+Service date: None words: 723 flesch: 44 summary: Close Besu / RPC Endpoint Service More actions RPC Endpoint Service Danno Ferrin Owned by Danno Ferrin Last updated: Dec 05, 2019 Summary Add a new service for the Plugins API where new RPC endpoints can be registered and handled. A prototype was implemented in Pantheon prior to the transition to Hyperledger Besu - https://github.com/PegaSysEng/pantheon/pull/1909/files Alternatives Considered Not exposing a Plugin API Downstream consumers would need to patch Besu and ship a custom build of Besu to their customers. keywords: api; besu; hyperledger; rpc cache: lfhyperledger-RPC+Endpoint+Service.html plain text: lfhyperledger-RPC+Endpoint+Service.txt item: #2261 of 3327 id: lfhyperledger-Raise+issues author: lfhyperledger title: lfhyperledger-Raise+issues date: None words: 225 flesch: 12 summary: Close Besu / Raise issues More actions Raise issues alexandra.tran Nicolas Massart Owned by alexandra.tran Last updated: Aug 24, 2022 by Nicolas Massart The pages in this section describe how to raise different kinds of issues in the Besu documentation repository. Code of Conduct Contributing Developing and Conventions Documentation Documentation contribution workflow Documentation contribution guidelines Versioned documentation Documentation archive Documentation release process Documentation style guide Future Release Dates MkDocs and Markdown guide Proposal - Besu maintainers become docs maintainers Raise issues Report bugs in the documentation Suggest documentation enhancements Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: documentation cache: lfhyperledger-Raise+issues.html plain text: lfhyperledger-Raise+issues.txt item: #2262 of 3327 id: lfhyperledger-Ratified+Smart+Contract+for+Constrained+Delivery+with+Oraclized+Data author: lfhyperledger title: lfhyperledger-Ratified+Smart+Contract+for+Constrained+Delivery+with+Oraclized+Data date: None words: 4035 flesch: 37 summary: To better visualize the purpose of the contract we are going to develop, let us recap the functionalities it should have: publish smart contract to the network with specified delivery conditions allow contractors to accept conditions and take the contract start the delivery by an authorized person monitor temperature of the package and check voiding conditions finalize the delivery calculate the final payment for the contractor First, you have to install both Remix and the Vyper compiler. At the end of each execution, the counter of the measurements is incremented, and contract voiding conditions are checked. keywords: conditions; contract; delivery; import; int128; return; temperature; time; use cache: lfhyperledger-Ratified+Smart+Contract+for+Constrained+Delivery+with+Oraclized+Data.html plain text: lfhyperledger-Ratified+Smart+Contract+for+Constrained+Delivery+with+Oraclized+Data.txt item: #2263 of 3327 id: lfhyperledger-Reduce+Memory+usage+by+choosing+a+different+low+level+allocator author: lfhyperledger title: lfhyperledger-Reduce+Memory+usage+by+choosing+a+different+low+level+allocator date: None words: 795 flesch: 30 summary: Instance-2: Running Besu version 22.4.3, also with the default MALLOC_ARENA_MAX value. Instance-3: Running Besu version 22.4.3 with MALLOC_ARENA_MAX set to 1. keywords: besu; memory; performance cache: lfhyperledger-Reduce+Memory+usage+by+choosing+a+different+low+level+allocator.html plain text: lfhyperledger-Reduce+Memory+usage+by+choosing+a+different+low+level+allocator.txt item: #2264 of 3327 id: lfhyperledger-Refactor+EVM+into+a+stand+alone+library author: lfhyperledger title: lfhyperledger-Refactor+EVM+into+a+stand+alone+library date: None words: 820 flesch: 31 summary: isPersistingPrivateState getPrivateStateMetadataUpdater transaction transactionHash (pmtHash) Move to Tuweni Wei Move Gas from Core to EVM Factor out transaction wrapper gas calculations into a new BlockchainGasCalculator Extracting access lists and intrinsic costs of TX code deposit cost max pmt cost Create in EVM world state updater interface Remove uses of account and delegate to the storage interface add method to test if an account isEmpty for an address get current storage value for an address get original storage value create EVM focused blockheader interface (to support operations), possibly add to o.h.b.plugin.data basefee blockhash (?) difficulty gaslimit block number block timestamp Move account warm-up out of the EVM into MainnetTransactionProcessor Not the tracking of warm addresses/slots, but the actual reading from the DB Remove contract versioning , multiple selections available, Related content More info Collapse Besu Plug-ins: Fork-free Client Modifications to Extend Besu Use Cases Besu Plug-ins: Fork-free Client Modifications to Extend Besu Use Cases Community Events More like this Modularity Implementation Approach Modularity Implementation Approach Besu More like this DRAFT - Besu Software Component Map DRAFT - Besu Software Component Map Besu More like this Besu as a Modular Client for the Merge (OLD) Besu as a Modular Client for the Merge (OLD) Besu More like this Modular Consensus Modular Consensus Besu More like this The Prague Upgrade from Besu Maintainers - The Hot, Cold, & Open-Ended The Prague Upgrade from Besu Maintainers - The Hot, Cold, & Open-Ended Besu More like this {serverDuration: 39, requestCorrelationId: 3c6f1be477864c7f8ee1123b8cb75094} PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; evm; library; use cache: lfhyperledger-Refactor+EVM+into+a+stand+alone+library.html plain text: lfhyperledger-Refactor+EVM+into+a+stand+alone+library.txt item: #2265 of 3327 id: lfhyperledger-Release+22.1.0 author: lfhyperledger title: lfhyperledger-Release+22.1.0 date: None words: 480 flesch: 1 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Release Rotations 2024 Using CalVer for Besu Releases How to do a Besu Release Off-cycle release process Release Process Obsolete Proposals and Policies Archive Critical Issue for Privacy Users Mainnet Consensus Bug Identified and Resolved in Hyperledger Besu Release 22.1.0 Release Process Improvement Release Remediation Release Rotations 2021 Release Rotations 2022 Release Rotations 2023 Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. See PR https://github.com/hyperledger/besu/pull/3442 , multiple selections available, Related content More info Collapse Versioned documentation Versioned documentation Besu More like this Using CalVer for Besu Releases Using CalVer for Besu Releases Besu More like this 09/23/24 09/23/24 Developer Relations More like this 2025-03-18 Contributor Call 2025-03-18 Contributor Call Besu More like this Repositories and other projects Repositories and other projects Besu More like this 2024-09-03 Contributor Call - US/EMEA 2024-09-03 Contributor Call - US/EMEA Besu More like this {serverDuration: 12, requestCorrelationId: fcd0fc7b5fd84a58b4a7962b6dc0a855} keywords: besu; cookies; release cache: lfhyperledger-Release+22.1.0.html plain text: lfhyperledger-Release+22.1.0.txt item: #2266 of 3327 id: lfhyperledger-Release+Philosophy author: lfhyperledger title: lfhyperledger-Release+Philosophy date: None words: 501 flesch: 41 summary: Close Besu / Release Philosophy More actions Release Philosophy Sally MacFarlane Owned by Sally MacFarlane Last updated: Aug 26, 2021 The general philosophy behind Besu release numbering is as follows. Increasing 1.4 RC/Beta window Proposal: Quarterly releases from main by default Release Philosophy Archive Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; release cache: lfhyperledger-Release+Philosophy.html plain text: lfhyperledger-Release+Philosophy.txt item: #2267 of 3327 id: lfhyperledger-Release+Process author: lfhyperledger title: lfhyperledger-Release+Process date: None words: 760 flesch: 44 summary: Trigger release process for documentation - Documentation release process Homebrew release Burn-in failures and hotfixes An alternate outcome where the burn-in fails is a no-op. Jun 11, 2024 by Justin Florentine Principles and Benefits main should always be release-able a chain of commits in the release branch from main provide provenance of a release the ability to merge PRs into main is uninhibited by the release process, and the release process itself is not encumbered by changes to main the RC process provides a crisp delineation of burn-in build artifacts and final release artifacts cherry-picking commits to compose a release remains possible, if discouraged Example Release Workflow for a hypothetical HL Besu 24.7.3 Burn-in candidate release steps (Day 0) Create a PR against main to add a new version section to CHANGELOG.md to reflect the next snapshot revision This prevents blocking main during the release but creates a bookmark to indicate that the release will include up to the commit before this. keywords: besu; process; release cache: lfhyperledger-Release+Process.html plain text: lfhyperledger-Release+Process.txt item: #2268 of 3327 id: lfhyperledger-Release+Process+Improvement author: lfhyperledger title: lfhyperledger-Release+Process+Improvement date: None words: 1844 flesch: 57 summary: Requires release branches, which are the only place that release version numbers exist. Tag releases are commit based rather than branch HEAD based. keywords: besu; branch; process; release; tag; version cache: lfhyperledger-Release+Process+Improvement.html plain text: lfhyperledger-Release+Process+Improvement.txt item: #2269 of 3327 id: lfhyperledger-Release+Remediation author: lfhyperledger title: lfhyperledger-Release+Remediation date: None words: 370 flesch: 29 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Release Rotations 2024 Using CalVer for Besu Releases How to do a Besu Release Off-cycle release process Release Process Obsolete Proposals and Policies Archive Critical Issue for Privacy Users Mainnet Consensus Bug Identified and Resolved in Hyperledger Besu Release 22.1.0 Release Process Improvement Release Remediation Release Rotations 2021 Release Rotations 2022 Release Rotations 2023 Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; release cache: lfhyperledger-Release+Remediation.html plain text: lfhyperledger-Release+Remediation.txt item: #2270 of 3327 id: lfhyperledger-Release+Rotations+2021 author: lfhyperledger title: lfhyperledger-Release+Rotations+2021 date: None words: 403 flesch: 21 summary: Close Besu / Release Rotations 2021 More actions Release Rotations 2021 Tim Beiko Sally MacFarlane Ratan Sur (Deactivated) +3 Owned by Tim Beiko Last updated: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Release Rotations 2024 Using CalVer for Besu Releases How to do a Besu Release Off-cycle release process Release Process Obsolete Proposals and Policies Archive Critical Issue for Privacy Users Mainnet Consensus Bug Identified and Resolved in Hyperledger Besu Release 22.1.0 Release Process Improvement Release Remediation Release Rotations 2021 Release Rotations 2022 Release Rotations 2023 Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; release; tim cache: lfhyperledger-Release+Rotations+2021.html plain text: lfhyperledger-Release+Rotations+2021.txt item: #2271 of 3327 id: lfhyperledger-Release+Rotations+2022 author: lfhyperledger title: lfhyperledger-Release+Rotations+2022 date: None words: 716 flesch: 32 summary: Close Besu / Release Rotations 2022 More actions Release Rotations 2022 Sally MacFarlane Frank Li (Deactivated) Justin Florentine +8 Owned by Sally MacFarlane Last updated: Jan 10, 2023 A page to keep track of engineers doing Besu releases, as well as roughly how long the release process is taking. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; gary; release; rotations cache: lfhyperledger-Release+Rotations+2022.html plain text: lfhyperledger-Release+Rotations+2022.txt item: #2272 of 3327 id: lfhyperledger-Release+Rotations+2023 author: lfhyperledger title: lfhyperledger-Release+Rotations+2023 date: None words: 527 flesch: 30 summary: Simon Dudley Owned by Sally MacFarlane Last updated: Jun 13, 2023 A page to keep track of engineers doing Besu releases, as well as roughly how long the release process is taking. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; release; rotations cache: lfhyperledger-Release+Rotations+2023.html plain text: lfhyperledger-Release+Rotations+2023.txt item: #2273 of 3327 id: lfhyperledger-Release+Rotations+2024 author: lfhyperledger title: lfhyperledger-Release+Rotations+2024 date: None words: 404 flesch: 36 summary: Release Date Cutoff Date Release Version Release Coordinator Release 2IC Release Tracker Issue 13/5/2024 24.4.0 AKA 24.5.1 Sally Justin 6966 26/5/2024 24.5.2 Sally Justin 7119 7/6/2024 AEST 24.6.0 Jason Justin 7182 28/6/2024 24.6.1 Gary Justin 24.7.0 Volunteers Jason Sally Gary , multiple selections available, Related content More info Collapse Release Process Release Process Besu More like this 2024 - 04 - 30 2024 - 04 - 30 Hyperledger Identus More like this 2024 - 07 - 23 2024 - 07 - 23 Hyperledger Identus More like this 2025-03-18 Contributor Call 2025-03-18 Contributor Call Besu More like this 2024-09-03 Contributor Call - US/EMEA 2024-09-03 Contributor Call - US/EMEA Besu More like this Using CalVer for Besu Releases Using CalVer for Besu Releases Besu More like this {serverDuration: 12, requestCorrelationId: 93032118aa2b471a9ed422ede386cc8f} Jun 27, 2024 by Sally MacFarlane A page to keep track of engineers doing Besu releases. keywords: besu; release cache: lfhyperledger-Release+Rotations+2024.html plain text: lfhyperledger-Release+Rotations+2024.txt item: #2274 of 3327 id: lfhyperledger-Releasing author: lfhyperledger title: lfhyperledger-Releasing date: None words: 318 flesch: 10 summary: Close Besu / Releasing More actions Releasing Christopher Hare Ry Jones Owned by Christopher Hare Last updated: Nov 27, 2019 by Ry Jones Release Rotations 2024 Using CalVer for Besu Releases How to do a Besu Release Off-cycle release process Release Process Obsolete Proposals and Policies Archive , multiple selections available, Related content More info Collapse Off-cycle release process Off-cycle release process Besu More like this Release Rotations 2024 Release Rotations 2024 Besu More like this Release Rotations 2023 Release Rotations 2023 Besu More like this Release Rotations 2022 Release Rotations 2022 Besu More like this Release Rotations 2021 Release Rotations 2021 Besu More like this New project launch or release milestones New project launch or release milestones Marketing More like this {serverDuration: 12, requestCorrelationId: b27c78bcf97e478dacd4c37b0bdedd3c} Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Release Rotations 2024 Using CalVer for Besu Releases How to do a Besu Release Off-cycle release process Release Process Obsolete Proposals and Policies Archive Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; release cache: lfhyperledger-Releasing.html plain text: lfhyperledger-Releasing.txt item: #2275 of 3327 id: lfhyperledger-Report+bugs+in+the+documentation author: lfhyperledger title: lfhyperledger-Report+bugs+in+the+documentation date: None words: 606 flesch: 48 summary: Report bugs in the documentation More actions Report bugs in the documentation Felipe Faraggi alexandra.tran Sally MacFarlane Owned by Felipe Faraggi Last updated: Apr 08, 2022 by alexandra.tran You can submit a documentation bug report by creating an issue in the Besu documentation repository. Code of Conduct Contributing Developing and Conventions Documentation Documentation contribution workflow Documentation contribution guidelines Versioned documentation Documentation archive Documentation release process Documentation style guide Future Release Dates MkDocs and Markdown guide Proposal - Besu maintainers become docs maintainers Raise issues Report bugs in the documentation Suggest documentation enhancements Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: documentation; problem cache: lfhyperledger-Report+bugs+in+the+documentation.html plain text: lfhyperledger-Report+bugs+in+the+documentation.txt item: #2276 of 3327 id: lfhyperledger-Reporting+Bugs author: lfhyperledger title: lfhyperledger-Reporting+Bugs date: None words: 796 flesch: 51 summary: , multiple selections available, Related content More info Collapse Report bugs in the documentation Report bugs in the documentation Besu More like this Issues Issues Besu More like this Debugging Besu in IntelliJ Debugging Besu in IntelliJ Besu More like this Suggest documentation enhancements Suggest documentation enhancements Besu More like this Release Remediation Release Remediation Besu More like this Documentation contribution workflow Documentation contribution workflow Besu More like this {serverDuration: 12, requestCorrelationId: 8d9e996f6d7e4e38a9c6a495cfdeded1} PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; problem; version cache: lfhyperledger-Reporting+Bugs.html plain text: lfhyperledger-Reporting+Bugs.txt item: #2277 of 3327 id: lfhyperledger-Repositories+and+other+projects author: lfhyperledger title: lfhyperledger-Repositories+and+other+projects date: None words: 426 flesch: -17 summary: OP-Besu https://github.com/optimism-java/op-besu Ethers.js for Hyperledger Besu https://github.com/ConsenSys/hyperledger-besu-ethers Besu Appsody stacks https://github.com/ericglau/HyperledgerBesuGenerators/tree/master/besu-appsody-stacks besu-clique-config https://www.npmjs.com/package/besu-clique-config Grid Project https://grid.ethereum.org/ Besu Developer Quickstart https://github.com/ConsenSys/quorum-dev-quickstart Besu Kubernetes https://github.com/ConsenSys/quorum-kubernetes Plugins Linea sequencer plugins https://github.com/Consensys/linea-sequencer Linea tracer plugins https://github.com/Consensys/linea-tracer version of besu that does not propagate transactions https://github.com/antonydenyer/no-pending-transactions-plugin kafka plugin  https://github.com/Consensys/besu-plugins RSS Feeds Besu main client repo master branch commits as an RSS feed https://github.com/hyperledger/besu/commits/main.atom Docker container updates as an RSS feed https://docker-hub-rss.now.sh/hyperledger/besu.atom , multiple selections available, Related content More info Collapse Besu Plug-ins: Fork-free Client Modifications to Extend Besu Use Cases Besu Plug-ins: Fork-free Client Modifications to Extend Besu Use Cases Community Events More like this Operate and Extend Hyperledger Besu Workshop Prerequisites Operate and Extend Hyperledger Besu Workshop Prerequisites Community Events More like this Operate and Extend Hyperledger Besu Workshop Operate and Extend Hyperledger Besu Workshop Community Events More like this Besu - Community Support Besu - Community Support Besu More like this 2020 Q2 Hyperledger Besu 2020 Q2 Hyperledger Besu Technical Oversight Committee More like this Besu 2022 Vision Besu 2022 Vision Besu More like this {serverDuration: 13, requestCorrelationId: e944bb26f877496691a7e806de15efea} PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; community; hyperledger cache: lfhyperledger-Repositories+and+other+projects.html plain text: lfhyperledger-Repositories+and+other+projects.txt item: #2278 of 3327 id: lfhyperledger-RpcEndpointService author: lfhyperledger title: lfhyperledger-RpcEndpointService date: None words: 581 flesch: 36 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Plugin Services BesuContext PermissioningService PrivacyPluginService RpcEndpointService Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; function; rpc cache: lfhyperledger-RpcEndpointService.html plain text: lfhyperledger-RpcEndpointService.txt item: #2279 of 3327 id: lfhyperledger-SECP256R1+Support author: lfhyperledger title: lfhyperledger-SECP256R1+Support date: None words: 3016 flesch: 56 summary: ECDSA signatures are 2 times longer than the signer's private key for the curve used during the signing process. SECP256R1 As the names of the classes suggest, they implement the SECP256K1 or SECP256R1 signature algorithms. keywords: besu; ecdsa; function; key; secp256r1; signature cache: lfhyperledger-SECP256R1+Support.html plain text: lfhyperledger-SECP256R1+Support.txt item: #2280 of 3327 id: lfhyperledger-Second+Incentive+Proposal author: lfhyperledger title: lfhyperledger-Second+Incentive+Proposal date: None words: 1205 flesch: 33 summary: Posting Bounties for work on Hyperledger Besu mainnet or mainnet related work Spending that would directly promote interoperability with Besu Mainnet functionality and other Hyperledger projects  Other spending that would directly promote and improve Hyperledger Besu Patronage Pool 60% will go to employers  of maintainers (or where the employer designates) allocating at least 25% of their work effort towards ethereum mainnet development. This pool will be a directed donation towards Hyperledger Besu mainnet work paying for items including but not limited to Administration, accounting, operations, and legal costs of the entity Costs relating to distribution of tokens by the entity Payment of services consumed by the Hyperledger Besu project, such as Continuous Integration, Cloud Hosting fees for development (i.e. testnet nodes) source code hosting, any other such services directly related to development of mainnet capabilities in Hyperledger Besu Sending maintainers to speak at and promote Hyperledger Besu at Hyperledger events (such as the Global Forum and Members Summit) and Ethereum Foundation events (such as DevCon and AllCoreDevs meetings) keywords: besu; hyperledger; mainnet; proposal cache: lfhyperledger-Second+Incentive+Proposal.html plain text: lfhyperledger-Second+Incentive+Proposal.txt item: #2281 of 3327 id: lfhyperledger-Security author: lfhyperledger title: lfhyperledger-Security date: None words: 355 flesch: 33 summary: Close Besu / Security More actions Security Felipe Faraggi Sally MacFarlane Danno Ferrin Ry Jones Owned by Felipe Faraggi Last updated: Aug 19, 2024 by Sally MacFarlane Hyperledger Security Policy Reporting a Security Bug If you think you have discovered a security issue in any of the Hyperledger projects, we'd love to hear from you. keywords: meeting; security cache: lfhyperledger-Security.html plain text: lfhyperledger-Security.txt item: #2282 of 3327 id: lfhyperledger-See+Performance+Stability+for+Q4+Roadmap author: lfhyperledger title: lfhyperledger-See+Performance+Stability+for+Q4+Roadmap date: None words: 270 flesch: 21 summary: Close Besu / See Performance & Stability for Q4 Roadmap More actions See Performance & Stability for Q4 Roadmap Matt Nelson (Deactivated) Owned by Matt Nelson (Deactivated) Nov 15, 2022 , multiple selections available, Related content More info Collapse Performance & Stability Performance & Stability Besu More like this Besu Roadmap & Planning Besu Roadmap & Planning Besu More like this 2021 Q1 Hyperledger Caliper 2021 Q1 Hyperledger Caliper Technical Oversight Committee More like this 2020-12-08 Meeting notes 2020-12-08 Meeting notes Hyperledger Cacti More like this 2024-02-27 Contributor Call - APAC Friendly Time 2024-02-27 Contributor Call - APAC Friendly Time Besu More like this 2022-02-01 Meeting Notes 2022-02-01 Meeting Notes Hyperledger Cacti More like this {serverDuration: 13, requestCorrelationId: 10484679ba604d9d8554eab4b68308dc} Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning Cancun Planning Enterprise roadmap item detail Prague Planning See Performance & Stability for Q4 Roadmap How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu cache: lfhyperledger-See+Performance+Stability+for+Q4+Roadmap.html plain text: lfhyperledger-See+Performance+Stability+for+Q4+Roadmap.txt item: #2283 of 3327 id: lfhyperledger-Shandong+Testnet author: lfhyperledger title: lfhyperledger-Shandong+Testnet date: None words: 607 flesch: 8 summary: Discord server Shandong Management Meta Issue @ ethereumjs repository , multiple selections available, Related content More info Collapse EIP-1559 testnet guide EIP-1559 testnet guide Besu More like this 2022 Q1 Hyperledger Besu 2022 Q1 Hyperledger Besu Technical Oversight Committee More like this Support Clique for Besu on HL Labs BAF Support Clique for Besu on HL Labs BAF Hyperledger Mentorship Program More like this Project Plan - Support Clique Consensus for Besu on HL Labs Blockchain Automation Framework Project Plan - Support Clique Consensus for Besu on HL Labs Blockchain Automation Framework Hyperledger Mentorship Program More like this Hyperledger Indy Technical Deep Dive - Handout Hyperledger Indy Technical Deep Dive - Handout Community Events More like this 2020-05-07 Meeting notes 2020-05-07 Meeting notes Hyperledger Iroha More like this {serverDuration: 13, requestCorrelationId: 97e45dc3e398498dbdb8d81880868635} Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) GitHub Merge Queue [ACCEPTED] DEBUG Log Improvement Proposal Checklist for reporting privacy issues Shandong Testnet Using Postman with Besu Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; shandong; testnet cache: lfhyperledger-Shandong+Testnet.html plain text: lfhyperledger-Shandong+Testnet.txt item: #2284 of 3327 id: lfhyperledger-Shanghai+planning author: lfhyperledger title: lfhyperledger-Shanghai+planning date: None words: 467 flesch: -5 summary: 3540 - EVM Object Format (EOF) XL in main https://github.com/hyperledger/besu/pull/4644 Under discussion: https://notes.ethereum.org/@ipsilon/eof1-unified-specification Danno Likely (EOF) N 3651 - Warm Coinbase S in main https://github.com/hyperledger/besu/pull/4620 Danno Yes Y 3670 - EOF - Code Validation L in main https://github.com/hyperledger/besu/pull/4644 Danno Likely (EOF) y 3855 - PUSH0 Instruction S in main https://github.com/hyperledger/besu/pull/4660 Danno Yes Y 3860 - Limit & Meter Initcode M in main https://github.com/hyperledger/besu/pull/4726 Diego Yes Y 4200 - Relative Jump Instructions M Draft https://github.com/hyperledger/besu/pull/4760 Diego Likely (EOF) Y 4750 - EOF Functions XL Draft https://github.com/hyperledger/besu/pull/4781 Danno Likely (EOF) y 4844 - Shard Blob Tx XL https://github.com/hyperledger/besu/issues/4631 Jiri Likely (Blobs) Likely 4895 - Withdrawals M https://github.com/hyperledger/besu/issues/4746 Simon Yes Y 5450 - EOF Stack Validation M Danno Likely (EOF) y Laundry list EIPs T-shirt size Status PR Champion Accepted? 1153 - Transient Storage M testing #4118 Likely 2537 - BLS Precompile S complete in main Gary Likely 3074 - AUTH and AUTHCALL L Unlikely EIP-4758: Deactivate SELFDESTRUCT (note there's also now an alternative EIP https://eips.ethereum.org/EIPS/eip-6046) S Likely , multiple selections available, Related content More info Collapse 2022 Q2 Hyperledger Besu 2022 Q2 Hyperledger Besu Technical Oversight Committee More like this 2022 Q1 Hyperledger Besu 2022 Q1 Hyperledger Besu Technical Oversight Committee More like this 2022-12-20 Contributor Call 2022-12-20 Contributor Call Besu More like this 2023-07-11 Contributor Call 2023-07-11 Contributor Call Besu More like this 2021 Q4 Hyperledger Besu 2021 Q4 Hyperledger Besu Technical Oversight Committee More like this 2020-06-09 Besu Contributor Call Agenda 2020-06-09 Besu Contributor Call Agenda Besu More like this {serverDuration: 13, requestCorrelationId: 64029bf7f92f471ca50fb7ed99aef16d} Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability 2024 - Besu Performance Improvements since the Merge Fast sync optimisation Memory usage investigations on 23.7.3-RC Permissioned chain performance testing Q4 2022 Stability and Performance Improvements Shanghai planning Reduce Memory usage by choosing a different low level allocator Testing Taskforce Brainstorming How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: besu; eof cache: lfhyperledger-Shanghai+planning.html plain text: lfhyperledger-Shanghai+planning.txt item: #2285 of 3327 id: lfhyperledger-Start+Here author: lfhyperledger title: lfhyperledger-Start+Here date: None words: 375 flesch: 36 summary: Yay! , multiple selections available, Related content More info Collapse How to Contribute How to Contribute Besu More like this First contribution First contribution Besu More like this Besu - Community Support Besu - Community Support Besu More like this Building from source Building from source Besu More like this Operate and Extend Hyperledger Besu Workshop Prerequisites Operate and Extend Hyperledger Besu Workshop Prerequisites Community Events More like this Using Hyperledger Besu to Participate in Public Ethereum Networks Using Hyperledger Besu to Participate in Public Ethereum Networks Community Events More like this Atlassian Intelligence {serverDuration: 13, requestCorrelationId: 477f0047cc6c4207ab66374cab9e369b} PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; community cache: lfhyperledger-Start+Here.html plain text: lfhyperledger-Start+Here.txt item: #2286 of 3327 id: lfhyperledger-Suggest+documentation+enhancements author: lfhyperledger title: lfhyperledger-Suggest+documentation+enhancements date: None words: 390 flesch: 33 summary: Close Besu / Suggest documentation enhancements More actions Suggest documentation enhancements Felipe Faraggi alexandra.tran Owned by Felipe Faraggi Last updated: Apr 08, 2022 by alexandra.tran You can submit a documentation enhancement suggestion, including completely new features and minor improvements, by creating an issue in the Besu documentation repository. Suggest documentation enhancements - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; documentation cache: lfhyperledger-Suggest+documentation+enhancements.html plain text: lfhyperledger-Suggest+documentation+enhancements.txt item: #2287 of 3327 id: lfhyperledger-Suggesting+Enhancements author: lfhyperledger title: lfhyperledger-Suggesting+Enhancements date: None words: 480 flesch: 48 summary: Close Besu / Suggesting Enhancements More actions Suggesting Enhancements Felipe Faraggi Sally MacFarlane Owned by Felipe Faraggi Last updated: Sept 08, 2020 by Sally MacFarlane This section guides you through submitting an enhancement suggestion. Enhancement suggestions are tracked as issues. keywords: besu; enhancement cache: lfhyperledger-Suggesting+Enhancements.html plain text: lfhyperledger-Suggesting+Enhancements.txt item: #2288 of 3327 id: lfhyperledger-Suspend+APAC+Contributor+Call author: lfhyperledger title: lfhyperledger-Suspend+APAC+Contributor+Call date: None words: 384 flesch: 36 summary: Close Besu / Suspend APAC Contributor Call More actions Suspend APAC Contributor Call Simon Dudley Sally MacFarlane Owned by Simon Dudley Last updated: Mar 26, 2024 by Sally MacFarlane I am proposing that we suspend the APAC timezone contributor call because the only contributors that attend are from Consensys. Any APAC-friendly contributor-level discussion can be done async in Discord as it already is, or async via the US/EMEA contributor call agenda. keywords: contributor cache: lfhyperledger-Suspend+APAC+Contributor+Call.html plain text: lfhyperledger-Suspend+APAC+Contributor+Call.txt item: #2289 of 3327 id: lfhyperledger-Switchable+Consensus+Parameters author: lfhyperledger title: lfhyperledger-Switchable+Consensus+Parameters date: None words: 678 flesch: 23 summary: IBFT business logic must be able to determine the currently active validators from a source other than just  the latest block - i.e. it must somehow factor in the validator switch data specified in the genesis file Block Validator rules must be updated to expect the validators in the block to be either as per existing voting, OR as per genesis file content This will probably  be abstracted behind the VoteTallyCache Votes cast prior to the change Block will need to be discarded on a change into a custom fork Items to Consider Currently, the overarching behaviour of the system is defined by the ProtocolSchedule and the associated ProtocolContext. Iroha Consensus API Reworking HL Iroha Consensus API Hyperledger Mentorship Program More like this Promote Iroha Runtime Validator into Iroha Runtime Executor Promote Iroha Runtime Validator into Iroha Runtime Executor Hyperledger Iroha More like this Iroha configuration changing Iroha configuration changing Hyperledger Iroha More like this Modular Besu Modular Besu Besu More like this Change View Drawback in Sumeragi Change View Drawback in Sumeragi Hyperledger Iroha More like this {serverDuration: 15, requestCorrelationId: 5cb70b20d6024911839c953ac2776ac2} keywords: block; iroha; validators cache: lfhyperledger-Switchable+Consensus+Parameters.html plain text: lfhyperledger-Switchable+Consensus+Parameters.txt item: #2290 of 3327 id: lfhyperledger-Testing author: lfhyperledger title: lfhyperledger-Testing date: None words: 931 flesch: 34 summary: ethereum:org.hyperledger.besu.ethereum.vm:referenceTest -Dtest.single=GeneralStateTest -Dtest.ethereum.state.eip=Frontier Or only the tests that match a particular pattern with something like: gradle :ethereum:org.hyperledger.besu.ethereum.vm:test -Dtest.single=GeneralStateTest -Dtest.ethereum.include='^CALLCODE.*-Frontier' For more details, see the comment on the test target in the top level build.gradle file. Hive tests  A suite of end to end client tests that are not invoked directly is provided here, https://github.com/ethereum/hive. keywords: besu; run; testing; tests cache: lfhyperledger-Testing.html plain text: lfhyperledger-Testing.txt item: #2291 of 3327 id: lfhyperledger-Testing+Taskforce+Brainstorming author: lfhyperledger title: lfhyperledger-Testing+Taskforce+Brainstorming date: None words: 1609 flesch: 53 summary: We should measure code coverage and make it a condition for merging a PR benchmark metrics - sync time, block import time etc and test PRs for regression some of these metrics (sync time, peering) may require long-running tests so may not be practical to run on individual PRs - could be on a nightly cadence Ensure test coverage for key features eg bonsai tests that run on mainnet config aren't testing upcoming hard fork features - to avoid finding bugs at the last minute, change this to holesky/sepolia (or make it configurable?) Robust processes we know that PRs have sufficient automated tests and/or require evidence of manual tests where this makes sense Don't want to make the release process more painful But could make the release process more robust/comprehensive if doing so doesn’t add hassle/pain to the process? keywords: besu; process; release; testing; tests cache: lfhyperledger-Testing+Taskforce+Brainstorming.html plain text: lfhyperledger-Testing+Taskforce+Brainstorming.txt item: #2292 of 3327 id: lfhyperledger-The+Prague+Upgrade+from+Besu+Maintainers+-+The+Hot+Cold+Open-Ended author: lfhyperledger title: lfhyperledger-The+Prague+Upgrade+from+Besu+Maintainers+-+The+Hot+Cold+Open-Ended date: None words: 1024 flesch: 48 summary:   EIP-5806 Delegate Transaction Weakly Opposed - EIP-5920: PAY opcode 1 Might break some assumptions of existing smart contracts  Ether can get stuck in a smart contract that cannot send it  Users may create issues with stuck Ether and  , multiple selections available, Related content More info Collapse Prague Planning Prague Planning Besu More like this Besu Roadmap & Planning Besu Roadmap & Planning Besu More like this 2021 Q4 Hyperledger Besu 2021 Q4 Hyperledger Besu Technical Oversight Committee More like this 2021-08-31 Besu Contributor Call 2021-08-31 Besu Contributor Call Besu More like this 2021-09-28 Besu Contributor Call 2021-09-28 Besu Contributor Call Besu More like this 2021-11-09 Besu Contributor Call 2021-11-09 Besu Contributor Call Besu More like this {serverDuration: 10, requestCorrelationId: 4254008a2d1747469074a50c1ec7bb3a} The Prague Upgrade from Besu Maintainers - The Hot, Cold, & Open-Ended - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. keywords: besu; evm; maintainers; planning; prague cache: lfhyperledger-The+Prague+Upgrade+from+Besu+Maintainers+-+The+Hot+Cold+Open-Ended.html plain text: lfhyperledger-The+Prague+Upgrade+from+Besu+Maintainers+-+The+Hot+Cold+Open-Ended.txt item: #2293 of 3327 id: lfhyperledger-Tools+we+use author: lfhyperledger title: lfhyperledger-Tools+we+use date: None words: 329 flesch: 32 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Plugin Services Tools we use Code coverage Gradle Verification Metadata Usage of SonarQube Usage of vulnerability scanners Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: standards; tools cache: lfhyperledger-Tools+we+use.html plain text: lfhyperledger-Tools+we+use.txt item: #2294 of 3327 id: lfhyperledger-Transaction+testing author: lfhyperledger title: lfhyperledger-Transaction+testing date: None words: 307 flesch: 6 summary: More like this Testing Targets Testing Targets Aries Connectathon More like this Project Plan- Reworking Data Model Tests Project Plan- Reworking Data Model Tests Hyperledger Mentorship Program More like this Quality Assurance: Tests, Strategy, Reports Quality Assurance: Tests, Strategy, Reports Hyperledger Fabric More like this Automated Testing for Climate Emissions Ledger Automated Testing for Climate Emissions Ledger Hyperledger Mentorship Program More like this Hyperledger Caliper testability and robustness improvement Hyperledger Caliper testability and robustness improvement Hyperledger Mentorship Program More like this {serverDuration: 12, requestCorrelationId: c536906d710c49009c95c53a9f978bc5} Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Decouple a class with Dagger - DRAFT Deployment of Private Hyperledger Besu on AWS with hardware layer for Externally Owned Account EIP-1559 testnet guide Limit Trie Logs for Bonsai Maximum Validator count for an IBFT2 Network Ratified Smart Contract for Constrained Delivery with Oraclized Data Transaction testing Using Hive Test Suite Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. keywords: hyperledger; testing cache: lfhyperledger-Transaction+testing.html plain text: lfhyperledger-Transaction+testing.txt item: #2295 of 3327 id: lfhyperledger-Usage+of+SonarQube author: lfhyperledger title: lfhyperledger-Usage+of+SonarQube date: None words: 942 flesch: 55 summary: IDE Plugins IntelliJ is an IDE commonly used by Besu developers, and it also has a SonarQube plugin available for it. PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. keywords: besu; code; coverage; sonarqube cache: lfhyperledger-Usage+of+SonarQube.html plain text: lfhyperledger-Usage+of+SonarQube.txt item: #2296 of 3327 id: lfhyperledger-Usage+of+vulnerability+scanners author: lfhyperledger title: lfhyperledger-Usage+of+vulnerability+scanners date: None words: 555 flesch: 36 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Plugin Services Tools we use Code coverage Gradle Verification Metadata Usage of SonarQube Usage of vulnerability scanners Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Feb 23, 2025 2 min read Options for vulnerability scanning for Besu. keywords: besu; usage; vulnerability cache: lfhyperledger-Usage+of+vulnerability+scanners.html plain text: lfhyperledger-Usage+of+vulnerability+scanners.txt item: #2297 of 3327 id: lfhyperledger-Using+CalVer+for+Besu+Releases author: lfhyperledger title: lfhyperledger-Using+CalVer+for+Besu+Releases date: None words: 522 flesch: 40 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Release Rotations 2024 Using CalVer for Besu Releases How to do a Besu Release Off-cycle release process Release Process Obsolete Proposals and Policies Archive Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. , multiple selections available, Related content More info Collapse Allow projects to use CalVer or SemVer Allow projects to use CalVer or SemVer Technical Oversight Committee More like this 2021-11-09 Besu Contributor Call 2021-11-09 Besu Contributor Call Besu More like this 2021 Q4 Hyperledger Besu 2021 Q4 Hyperledger Besu Technical Oversight Committee More like this 2021 Q3 Hyperledger Besu 2021 Q3 Hyperledger Besu Technical Oversight Committee More like this 2020 Q3 Hyperledger Besu 2020 Q3 Hyperledger Besu Technical Oversight Committee More like this Release Rotations 2023 Release Rotations 2023 Besu More like this {serverDuration: 34, requestCorrelationId: dfc2e7c705ea439ca9b62dbd81b52536} keywords: besu; calver; hyperledger cache: lfhyperledger-Using+CalVer+for+Besu+Releases.html plain text: lfhyperledger-Using+CalVer+for+Besu+Releases.txt item: #2298 of 3327 id: lfhyperledger-Using+Hive+Test+Suite author: lfhyperledger title: lfhyperledger-Using+Hive+Test+Suite date: None words: 1010 flesch: 46 summary:     , multiple selections available,hive testing kb-how-to-article Related content More info Collapse 2021 Q4 Hyperledger Besu 2021 Q4 Hyperledger Besu Technical Oversight Committee More like this 2021 Q3 Hyperledger Besu 2021 Q3 Hyperledger Besu Technical Oversight Committee More like this 2020 Q2 Hyperledger Besu 2020 Q2 Hyperledger Besu Technical Oversight Committee More like this BESU BESU Learning Materials Development Working Group Using Hive Test Suite More actions Using Hive Test Suite Justin Florentine Sally MacFarlane Owned by Justin Florentine Last updated: Apr 10, 2025 by Sally MacFarlane 3 min read Online results These 2 dashboards show the current status https://hive.ethpandaops.io/pectra/index.html#summary-sort=name status of this one is currently being published daily to Eth R&D Discord in #interop channel so we very much want Besu to be 100% green. keywords: besu; hive; test cache: lfhyperledger-Using+Hive+Test+Suite.html plain text: lfhyperledger-Using+Hive+Test+Suite.txt item: #2299 of 3327 id: lfhyperledger-Using+Postman+with+Besu author: lfhyperledger title: lfhyperledger-Using+Postman+with+Besu date: None words: 441 flesch: 43 summary: Code of Conduct Contributing Developing and Conventions Besu CLI Style Guide Coding Conventions Changelog Testing Debugging Besu in IntelliJ Releasing Bug Triage Process Policies Plugin Services Tools we use Advanced Repositories and other projects Archive (Dev) GitHub Merge Queue [ACCEPTED] DEBUG Log Improvement Proposal Checklist for reporting privacy issues Shandong Testnet Using Postman with Besu Changelog Improvement Proposal Logging Building from source Documentation Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Using Postman with Besu More actions Using Postman with Besu Sally MacFarlane Owned by Sally MacFarlane May 29, 2024 Interacting With a Besu Node in Postman (JSON-RPC API) keywords: besu; postman cache: lfhyperledger-Using+Postman+with+Besu.html plain text: lfhyperledger-Using+Postman+with+Besu.txt item: #2300 of 3327 id: lfhyperledger-Validator+Nodes+Recommendations+for+HL+Besu+s+Incentive+Program author: lfhyperledger title: lfhyperledger-Validator+Nodes+Recommendations+for+HL+Besu+s+Incentive+Program date: None words: 652 flesch: 33 summary: Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Besu Execution Client Incentive Program The Merge is scheduled for mid-2022.  , multiple selections available, Related content More info Collapse Besu Execution Client Incentive Program Besu Execution Client Incentive Program Besu More like this Near-Term Besu Incentive Program proposal Near-Term Besu Incentive Program proposal Besu More like this Second Incentive Proposal Second Incentive Proposal Besu More like this 2021-12-30 Besu Contributor Call (off cycle) 2021-12-30 Besu Contributor Call (off cycle) Besu More like this 2021-12-21 Besu Contributor Call 2021-12-21 Besu Contributor Call Besu More like this Proposal #3.5 Proposal #3.5 Besu More like this {serverDuration: 36, requestCorrelationId: e6b03d12ebb949e09a525406919a291b} keywords: besu; incentive; program cache: lfhyperledger-Validator+Nodes+Recommendations+for+HL+Besu+s+Incentive+Program.html plain text: lfhyperledger-Validator+Nodes+Recommendations+for+HL+Besu+s+Incentive+Program.txt item: #2301 of 3327 id: lfhyperledger-Versioned+documentation author: lfhyperledger title: lfhyperledger-Versioned+documentation date: None words: 438 flesch: 25 summary: Close Besu / Versioned documentation More actions Versioned documentation Joshua Fernandes Alexandra Tran Owned by Joshua Fernandes Last updated: Sept 25, 2024 by Alexandra Tran Every Besu documentation version is tagged in the repository, but the published documentation site only contains the in-flight latest version – that is, new documentation is published as features are released. View older documentation versions To build or host a specific older version of the documentation (for example, 23.7.1): keywords: besu; documentation cache: lfhyperledger-Versioned+documentation.html plain text: lfhyperledger-Versioned+documentation.txt item: #2302 of 3327 id: lfhyperledger-WIP+Proposal+4 author: lfhyperledger title: lfhyperledger-WIP+Proposal+4 date: None words: 287 flesch: 39 summary: [WIP] Proposal #4 More actions [WIP] Proposal #4 Tim Beiko Owned by Tim Beiko Last updated: Feb 14, 2022 After conversations with HLF, ConsenSys and other Besu maintainers, here is an updated proposal for the incentive program which seems to align with everyone's interests: https://notes.ethereum.org/@timbeiko/besu-cip-proposal-4. Code of Conduct Contributing Developing and Conventions Documentation Community Governance Programs & Grants Besu Execution Client Incentive Program keywords: besu; proposal cache: lfhyperledger-WIP+Proposal+4.html plain text: lfhyperledger-WIP+Proposal+4.txt item: #2303 of 3327 id: lfhyperledger-Web+Design author: lfhyperledger title: lfhyperledger-Web+Design date: None words: 560 flesch: 36 summary: HTML (Hypertext Markup Language) is the foundation of web design, providing the structure and content of the site. Web design is a constantly evolving field, and designers stay updated with the latest design trends, best practices, and emerging technologies. keywords: design; documentation; web cache: lfhyperledger-Web+Design.html plain text: lfhyperledger-Web+Design.txt item: #2304 of 3327 id: lfhyperledger-overview author: lfhyperledger title: lfhyperledger-overview date: None words: 1197 flesch: 52 summary: They include: Proof of Stake:    keywords: besu; ethereum; network; proof cache: lfhyperledger-overview.html plain text: lfhyperledger-overview.txt item: #2305 of 3327 id: lfhyperledger-overview?homepageId=22151173 author: lfhyperledger title: lfhyperledger-overview?homepageId=22151173 date: None words: 1197 flesch: 53 summary: They include: Proof of Stake:    keywords: besu; ethereum; network; proof cache: lfhyperledger-overview?homepageId=22151173.html plain text: lfhyperledger-overview?homepageId=22151173.txt item: #2306 of 3327 id: lfhyperledger-pages author: lfhyperledger title: lfhyperledger-pages date: None words: 7 flesch: -17 summary: LF Decentralized Trust {serverDuration: 13, requestCorrelationId: d829c2c7f2c34045ad5a902e9ae92390} keywords: requestcorrelationid cache: lfhyperledger-pages.html plain text: lfhyperledger-pages.txt item: #2307 of 3327 id: swarmresear-14 author: swarmresear title: swarmresear-14 date: None words: 447 flesch: 70 summary: When uploading new chunks to the Swarm, each chunk is given a signed receipt indicating which registered deposit this chunk belongs to. Upon receiving a chunk, a node checks how many other chunks it knows about that have the same signature (Q: and maybe what the radius of that set is?) and thereby estimate the total number of chunks in the Swarm that are signed by that key. keywords: burn cache: swarmresear-14.html plain text: swarmresear-14.txt item: #2308 of 3327 id: swarmresear-142 author: swarmresear title: swarmresear-142 date: None words: 66 flesch: 60 summary: How is BZZ deposit decay currently calculated on postage bunches? How is BZZ deposit decay currently calculated on postage bunches? Research tmm360 December 22, 2021, 5:13pm #1 Question as from title. keywords: decay cache: swarmresear-142.html plain text: swarmresear-142.txt item: #2309 of 3327 id: swarmresear-15 author: swarmresear title: swarmresear-15 date: None words: 388 flesch: 69 summary: In this scenarion, during syncing, closer nodes compensate upstream nodes for the incoming sync. The twist is that you only accept chunks that have sufficiently high proof-of-burn attached. keywords: burn cache: swarmresear-15.html plain text: swarmresear-15.txt item: #2310 of 3327 id: swarmresear-16 author: swarmresear title: swarmresear-16 date: None words: 1557 flesch: 72 summary: It leaves sufficient room above for popular chunks to be cached independent of any syncing, while leaving sufficient room afterwards for proximate synced chunks to be stored for quite a while before being flushed out.] The Garbage Collection Queue This section presents a simple method for prioritising chunks based on expected profitablity. keywords: chunks; queue cache: swarmresear-16.html plain text: swarmresear-16.txt item: #2311 of 3327 id: swarmresear-165 author: swarmresear title: swarmresear-165 date: None words: 454 flesch: 61 summary: HOw TO RECOVER STOLEN/LOST CRYPTO FUNDS - Education - Swarm Community HOw TO RECOVER STOLEN/LOST CRYPTO FUNDS Education LindseyM April 28, 2023, 2:55am #1 I was a first-time investor in the crypto market. If you’ve experienced the loss or theft of cryptocurrency or funds on the internet, we’re here to assist you in recovering what’s rightfully yours. keywords: crypto; funds cache: swarmresear-165.html plain text: swarmresear-165.txt item: #2312 of 3327 id: swarmresear-166 author: swarmresear title: swarmresear-166 date: None words: 282 flesch: 73 summary: How to retrieve stolen/lost crypto funds - Research - Swarm Community How to retrieve stolen/lost crypto funds Research LindseyM April 29, 2023, 12:09pm #1 HOW TO RETRIEVE STOLEN/LOST CRYPTO FUNDS I was a first-time investor in the crypto market. Contact Recovery101 and take action to recover your funds today. keywords: funds cache: swarmresear-166.html plain text: swarmresear-166.txt item: #2313 of 3327 id: swarmresear-17 author: swarmresear title: swarmresear-17 date: None words: 1305 flesch: 72 summary: Why would full nodes want to make light connections to each other? and I want to use it to access data from Swarm - might well have an interest in opening light connections to other nodes. keywords: client; light cache: swarmresear-17.html plain text: swarmresear-17.txt item: #2314 of 3327 id: swarmresear-18 author: swarmresear title: swarmresear-18 date: None words: 537 flesch: 58 summary: While optimizations are obviously possible, the simplest way of updating reference counters in case of change of root reference is increasing counters in a tranversal from the new root and then dereferencing the old root. Thus, reference counters can be initialized by resetting all to zero and then simply traversing references from a given root while increasing the reference counter for each encountered chunk. keywords: reference cache: swarmresear-18.html plain text: swarmresear-18.txt item: #2315 of 3327 id: swarmresear-2 author: swarmresear title: swarmresear-2 date: None words: 54 flesch: 60 summary: About the Site Feedback category - Site Feedback - Swarm Community About the Site Feedback category Site Feedback system March 8, 2019, 6:39pm #1 Discussion about this site, its organization, how it works, and how we can improve it. Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled keywords: site cache: swarmresear-2.html plain text: swarmresear-2.txt item: #2316 of 3327 id: swarmresear-3 author: swarmresear title: swarmresear-3 date: None words: 450 flesch: 70 summary: When uploading new chunks to the Swarm, each chunk is given a signed receipt indicating which registered deposit this chunk belongs to. Upon receiving a chunk, a node checks how many other chunks it knows about that have the same signature (Q: and maybe what the radius of that set is?) and thereby estimate the total number of chunks in the Swarm that are signed by that key. keywords: burn cache: swarmresear-3.html plain text: swarmresear-3.txt item: #2317 of 3327 id: swarmresear-30 author: swarmresear title: swarmresear-30 date: None words: 848 flesch: 65 summary: Now, since hashing does a good job of randomizing chunk adresses, this credit will be very probably balanced with chunks synced by Bob to Alice before any actual payment takes place, but on an abstract level, Bob does pay Alice for pushing spam-limited content his way that is closer to his address than to hers. Chunks can have multiple (valid) postage stamps attached to them. keywords: chunk; proof cache: swarmresear-30.html plain text: swarmresear-30.txt item: #2318 of 3327 id: swarmresear-33 author: swarmresear title: swarmresear-33 date: None words: 1466 flesch: 62 summary: So another idea is to do it all off-chain, for example relying directly on the existing DNS infra-structure similarly as discv5 does: here no eth client is involved, and swarm’s initial connection looks for initial peers from servers pointed to by DNS addresses (the dns domain name itself is then hardcoded in the swarm client) - here it would be nice to see a commitment from the EF to provide such nodes with good uptime (expanding on this a bit, EF servers could even push the result of on-chain peer curated lists to swarm feeds at a certain topic, such that both running an eth light-client or DNS for bootstrapping becomes non-mandatory). I think having a hub-and-spoke topology as you mentioned, with at least a few nodes connecting to the “outside network”, is still better than having nodes not having anyone to connect to at all: Even if a local network (with multiple swarm nodes) is isolated from the internet, nodes in such LAN can still locally sync with each other, and once they eventually become dial-able again to the outside (internet access is restored), they should be able to sync without too much loss of information, right? keywords: nodes; peers; swarm cache: swarmresear-33.html plain text: swarmresear-33.txt item: #2319 of 3327 id: swarmresear-34 author: swarmresear title: swarmresear-34 date: None words: 1009 flesch: 66 summary: Bandwidth Since Swarm peers are expected to connect to most-proximate peers based on Swarm address and not most-proximate based on geography, we often get asked if this does not seriously degrade performance. These data-points might inform our connection strategy: While we cannot choose who our most-proximate peers are, we can certainly prioritise faster peer connections on the lower numbered Kademlia bins. keywords: connection; peers cache: swarmresear-34.html plain text: swarmresear-34.txt item: #2320 of 3327 id: swarmresear-37 author: swarmresear title: swarmresear-37 date: None words: 2532 flesch: 76 summary: Q: What is the postage definition ETA? A: Not complete, but there is a SWIP PR WIP Postage Stamps for Swarm Messages by nagydani · Pull Request #8 · ethersphere/SWIPs · GitHub Q: Disconnect Ignore (some) messages/communication … A: Q: As a node I misbehaved (or my network was temporarily bad) and over time all or majority of my peers dropped me. keywords: cheque; chunk; file; price cache: swarmresear-37.html plain text: swarmresear-37.txt item: #2321 of 3327 id: swarmresear-40 author: swarmresear title: swarmresear-40 date: None words: 979 flesch: 67 summary: : the waiver chequebook will most likely slow down the development process as both the smart-contracts, as well as the implementation of these smart-contracts is more difficult, a code audit on waiver chequebooks and their implementations will be more costly, there is a higher risk for a security breach due to more complex code, we introduce the need for nodes to be always online when waivers are present in the history of their chequebooks or contract with a watchtower like service (see: https://medium.com/crypto-punks/lightning-vs-raiden-watchtowers-monitoring-services-differences-c8eb0f724e68), the UX of smart-contracts with waivers is much worse as they have to wait and it will be difficult to explain why a cash-out transaction needs two transactions. SWAP and the need for waivers - Research - Swarm Community SWAP and the need for waivers Research eknir July 22, 2019, 3:38pm #1 Tron and Fischer (Generalised swap swear and swindle games, 2019) write in section 2.3 (waivers) that being able to make a waiver is a desirable feature for a chequebook. keywords: chequebook; waiver cache: swarmresear-40.html plain text: swarmresear-40.txt item: #2322 of 3327 id: swarmresear-41 author: swarmresear title: swarmresear-41 date: None words: 369 flesch: 64 summary: Why doesn’t B lose everything secured by soft deposits? According to the paper only the increased amount is at risk, but what makes the “older” table more valid than the new one which doesn’t have B at all? What happens if A signed off multiple allocation tables for the same epoch? What prevents A from simply making an alternative table with just one peer (himself) that gets the whole allocation? How is the instant payout described in 2.4.3 supposed to be secure? keywords: swap cache: swarmresear-41.html plain text: swarmresear-41.txt item: #2323 of 3327 id: swarmresear-42 author: swarmresear title: swarmresear-42 date: None words: 386 flesch: 61 summary: Adjusting payment thresholds - Research - Swarm Community Adjusting payment thresholds Research eknir August 26, 2019, 11:16am #1 The paymentTreshhold is a variable, defined by SWAP which implies at which negative balance nodes will send a payment to their counterparty. Adjusting this level is needed on a network-wide basis to facilitate correct parametrization (the current value is randomly chosen) and to allow other payment modules, with different costs of sending a payment to change this value. keywords: payment cache: swarmresear-42.html plain text: swarmresear-42.txt item: #2324 of 3327 id: swarmresear-44 author: swarmresear title: swarmresear-44 date: None words: 232 flesch: 54 summary: Is it possible to collaborate with you about usage of decentralized servers solution together with Swarm? Is it possible to collaborate with you about usage of decentralized servers solution together with Swarm? keywords: servers cache: swarmresear-44.html plain text: swarmresear-44.txt item: #2325 of 3327 id: swarmresear-46 author: swarmresear title: swarmresear-46 date: None words: 48 flesch: 74 summary: Devcon5 swarm talks - Swarm Community Devcon5 swarm talks racnela-ft January 7, 2020, 8:37pm #1 In case anyone has missed it, finally devcon5 swarm presentations were released: cheers, Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled keywords: swarm cache: swarmresear-46.html plain text: swarmresear-46.txt item: #2326 of 3327 id: swarmresear-48 author: swarmresear title: swarmresear-48 date: None words: 3278 flesch: 67 summary: Specifically: the address of the node and the addresses of registered nodes in his neighborhood, his price, the price of nodes in his neighborhood, the purchase of postage batches and the earning from other nodes cashing out. The risk of keeping earned income in the pool stems from other nodes cashing out more than they should cash out: if this happens, the money in the pool is less than the outstanding payments, which introduces the risk that a node doesn’t get paid-out fully. keywords: challenge; income; node; price cache: swarmresear-48.html plain text: swarmresear-48.txt item: #2327 of 3327 id: swarmresear-66 author: swarmresear title: swarmresear-66 date: None words: 173 flesch: 41 summary: Here is a collection of ideas (hopefully eventually evolving into a proposal) about how to redistribute these payments between storer nodes in an incentive-aligned fashion: hackmd.io Storage Rewards - HackMD In the most extreme version, there is no lottery component in the system, every participating storer node will get paid in every epoch. 1 Like michelle_plur pinned July 9, 2021, 2:03pm #2 Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled keywords: postage cache: swarmresear-66.html plain text: swarmresear-66.txt item: #2328 of 3327 id: swarmresear-7 author: swarmresear title: swarmresear-7 date: None words: 34 flesch: 52 summary: Welcome to Discourse - Swarm Community Welcome to Discourse system March 8, 2019, 6:39pm #1 https://ethresear.ch/ for Swarm Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled keywords: discourse cache: swarmresear-7.html plain text: swarmresear-7.txt item: #2329 of 3327 id: swarmresear-70 author: swarmresear title: swarmresear-70 date: None words: 122 flesch: 69 summary: Use the following paragraphs for a longer description, or to establish category guidelines or rules: Why should people use this category? About the Research category - Research - Swarm Community About the Research category Research michelle_plur July 9, 2021, 1:20pm #1 (Replace this first paragraph with a brief description of your new category. keywords: category cache: swarmresear-70.html plain text: swarmresear-70.txt item: #2330 of 3327 id: swarmresear-76 author: swarmresear title: swarmresear-76 date: None words: 126 flesch: 69 summary: Use the following paragraphs for a longer description, or to establish category guidelines or rules: Why should people use this category? About the Bonding Curve category - Bonding Curve - Swarm Community About the Bonding Curve category Bonding Curve michelle_plur July 9, 2021, 2:07pm #1 (Replace this first paragraph with a brief description of your new category. keywords: category cache: swarmresear-76.html plain text: swarmresear-76.txt item: #2331 of 3327 id: swarmresear-77 author: swarmresear title: swarmresear-77 date: None words: 130 flesch: 62 summary: Use the following paragraphs for a longer description, or to establish category guidelines or rules: Why should people use this category? About the Swarm Improvement Proposals category - Swarm Improvement Proposals - Swarm Community About the Swarm Improvement Proposals category Swarm Improvement Proposals michelle_plur July 9, 2021, 2:08pm #1 (Replace this first paragraph with a brief description of your new category. keywords: category cache: swarmresear-77.html plain text: swarmresear-77.txt item: #2332 of 3327 id: swarmresear-78 author: swarmresear title: swarmresear-78 date: None words: 122 flesch: 66 summary: Use the following paragraphs for a longer description, or to establish category guidelines or rules: Why should people use this category? About the Education category - Education - Swarm Community About the Education category Education michelle_plur July 9, 2021, 2:08pm #1 (Replace this first paragraph with a brief description of your new category. keywords: category cache: swarmresear-78.html plain text: swarmresear-78.txt item: #2333 of 3327 id: swarmresear-79 author: swarmresear title: swarmresear-79 date: None words: 126 flesch: 64 summary: Use the following paragraphs for a longer description, or to establish category guidelines or rules: Why should people use this category? About the Bee Development category - Bee Development - Swarm Community About the Bee Development category Bee Development michelle_plur July 9, 2021, 2:08pm #1 (Replace this first paragraph with a brief description of your new category. keywords: category cache: swarmresear-79.html plain text: swarmresear-79.txt item: #2334 of 3327 id: swarmresear-80 author: swarmresear title: swarmresear-80 date: None words: 126 flesch: 64 summary: Use the following paragraphs for a longer description, or to establish category guidelines or rules: Why should people use this category? This guidance will appear in the category selection area, so try to keep it below 200 characters.) keywords: category cache: swarmresear-80.html plain text: swarmresear-80.txt item: #2335 of 3327 id: swarmresear-81 author: swarmresear title: swarmresear-81 date: None words: 126 flesch: 64 summary: Use the following paragraphs for a longer description, or to establish category guidelines or rules: Why should people use this category? About the Dapp Development category - Dapp Development - Swarm Community About the Dapp Development category Dapp Development michelle_plur July 9, 2021, 2:09pm #1 (Replace this first paragraph with a brief description of your new category. keywords: category cache: swarmresear-81.html plain text: swarmresear-81.txt item: #2336 of 3327 id: swarmresear-83 author: swarmresear title: swarmresear-83 date: None words: 76 flesch: 26 summary: | Swarm Bee Client Website: https://ethswarm.org/ e-mail: info@ethswarm.org Discord: Swarm Twitter: https://twitter.com/ethswarm Blog: Ethereum Swarm – Medium Reddit: https://www.reddit.com/r/ethswarm Youtube: Ethereum Swarm - YouTube Github: Ethersphere · GitHub Newsletter: Swarm Newsletter Signup michelle_plur pinned July 9, 2021, 5:53pm #2 Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled keywords: swarm cache: swarmresear-83.html plain text: swarmresear-83.txt item: #2337 of 3327 id: swarmresear-95 author: swarmresear title: swarmresear-95 date: None words: 50 flesch: 30 summary: How to find discussions on political ideaology - Site Feedback - Swarm Community How to find discussions on political ideaology Site Feedback Tiveno75 August 13, 2021, 3:33am #1 How to find like discussions on Swarm ? Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled keywords: discussions cache: swarmresear-95.html plain text: swarmresear-95.txt item: #2338 of 3327 id: vitalik-99_fault_tolerant author: vitalik title: vitalik-99_fault_tolerant date: None words: 2004 flesch: 58 summary: At this point, there is a guarantee that honest nodes have all validly seen the same set of values. At time \(T + D\), nodes 0 and 2 rebroadcast all values they've seen that they have not yet broadcasted, but add their signatures on (\(x\) and \(w\) for node 0, \(y\) for node 2). keywords: consensus; nodes; time cache: vitalik-99_fault_tolerant.html plain text: vitalik-99_fault_tolerant.txt item: #2339 of 3327 id: vitalik-On_Collusion_DE author: vitalik title: vitalik-On_Collusion_DE date: None words: 4109 flesch: 49 summary: Pseudo-Accounts des Angreifers, hat der Angreifer nur eine Identität, das Geld erhaltende Konto und die anderen 10000 Konten sind echte Benutzer - aber Benutzer, die eine Bestechung von je $0,01 für die Handlung erhalten, die dem Angreifer den Erhalt von zusätzlich $1 verursacht. Im Gegensatz zu den Vorgängen im KEY-System ist hier die Belohnung die B erhält, wenn A B positiv bewertet, nicht proportional zur vorhandenen Token-Menge von A. Stattdessen hat jedes Reddit-Konto die gleiche Fähigkeit, zu anderen Reddit-Konten beizutragen. keywords: aber; als; auch; auf; das; dass; dem; den; der; des; die; diese; durch; eine; für; gibt; haben; hat; ist; kann; können; mechanismus; mit; nicht; nur; oder; sich; sie; sind; token; und; von; wenn; werden; wie; wird cache: vitalik-On_Collusion_DE.html plain text: vitalik-On_Collusion_DE.txt item: #2340 of 3327 id: vitalik-On_Collusion_IT author: vitalik title: vitalik-On_Collusion_IT date: None words: 4319 flesch: 47 summary: Il meccanismo di base (potete consultare il white paper in cinese qui) è che se un utente della piattaforma detiene token KEY, ha la possibilità di impegnare quei token KEY in articoli; ogni utente ha a disposizione k C'è tuttavia un attacco ancora più a basso costo dell'acquisto di donut (un attacco che può essere considerato una specie di bustarella nascosta): il noleggio. keywords: account; anche; che; collusione; con; cui; dei; della; donut; esempio; essere; giochi; gli; identità; meccanismo; modo; molto; nel; non; più; possono; problema; può; questo; sistema; sono; token; una; voti; voto cache: vitalik-On_Collusion_IT.html plain text: vitalik-On_Collusion_IT.txt item: #2341 of 3327 id: vitalik-On_Collusion_Polish author: vitalik title: vitalik-On_Collusion_Polish date: None words: 3680 flesch: 55 summary: „tak, a „wspólny aspekt jest następujący: o wiele trudniejsze, a zapewne wręcz niemożliwe jest stworzenie mechanizmów, które zachowują pożądane właściwości w modelu, w którym uczestnicy mogą się zmawiać, niż w modelu, w którym nie mogą. Rynki konkurencyjne są całkiem odporne na zmowy do stosunkowo wysokiej wartości granicznej, która w niektórych przypadkach jest łatwo osiągalna, a w innych nie. keywords: aby; ale; bardziej; bardzo; być; dla; gier; głosowania; głosów; jak; jest; jeśli; każdy; który; lub; mechanizm; mogą; może; można; nawet; nie; niż; poparcia; przez; również; się; społeczności; systemy; tak; tego; tożsamości; treści; tym; wiele; zmowy; łapówki cache: vitalik-On_Collusion_Polish.html plain text: vitalik-On_Collusion_Polish.txt item: #2342 of 3327 id: vitalik-On_Collusion_Portuguese author: vitalik title: vitalik-On_Collusion_Portuguese date: None words: 4320 flesch: 42 summary: Os mercados competitivos estão razoavelmente seguros até um limite relativamente elevado, o que é facilmente alcançado em alguns casos, mas em outros não o é. É também por isso que os sistemas de votação baseados em moedas (como o Bihu) têm uma grande vantagem genuína sobre os sistemas baseados na identidade (como o Gitcoin CLR ou a experiência de donut /r/ethtrader: pelo menos não há nenhum benefício em comprar contas em massa, porque tudo o que você faz é proporcional ao número de moedas que você tem, independentemente do número de contas que as moedas estão divididas entre si. keywords: apenas; com; como; dos; eles; exemplo; fazer; identidade; jogos; mais; mas; mecanismo; mesmo; moedas; muito; não; onde; para; podem; por; que; ser; sistema; suborno; são; também; uma; usuário; você; votos cache: vitalik-On_Collusion_Portuguese.html plain text: vitalik-On_Collusion_Portuguese.txt item: #2343 of 3327 id: vitalik-a_note_on_charity author: vitalik title: vitalik-a_note_on_charity date: None words: 1130 flesch: 60 summary: As far as implementation goes, this requires: A standard for stickers, including wallets where people can hold stickers Payment systems that have support for charging lower prices to sticker holders included At least a few sticker-issuing organizations (the lowest overhead is likely to be issuing stickers for charity donations, and for easily verifiable online content, eg. open source software and blogs) The next stage is to make the scheme recursive - being or working for a merchant that offers lower prices to holders of green stickers is itself enough to merit you a green sticker, albeit one that is of lower potency and gives you a lower discount. keywords: prices; profit cache: vitalik-a_note_on_charity.html plain text: vitalik-a_note_on_charity.txt item: #2344 of 3327 id: vitalik-backpack author: vitalik title: vitalik-backpack date: None words: 2887 flesch: 73 summary: I have a T-shirt bag, an underwear bag, a sock bag, a toiletries bag, a dirty-laundry bag, a medicine bag, a laptop bag, and various small bags inside the inner compartment of my backpack, which all fit into a 40-liter Hynes Eagle backpack. My sock bag is currently larger than my underwear bag, and only a bit smaller than my T-shirt bag: both a sign of the challenge of finding good socks, and a testament to Uniqlo's amazing Airism T-shirts. keywords: backpack; bag; cm3; laptop; socks; uniqlo cache: vitalik-backpack.html plain text: vitalik-backpack.txt item: #2345 of 3327 id: vitalik-biometric author: vitalik title: vitalik-biometric date: None words: 6782 flesch: 57 summary: [2] is a much bigger risk for Worldcoin than for Proof of Humanity (or BrightID), because Worldcoin depends on specialized hardware and other systems do not. On the whole, despite the dystopian vibez of staring into an Orb and letting it scan deeply into your eyeballs, it does seem like specialized hardware systems can do quite a decent job of protecting privacy. keywords: biometric; graph; humanity; iris; people; personhood; proof; system; worldcoin cache: vitalik-biometric.html plain text: vitalik-biometric.txt item: #2346 of 3327 id: vitalik-bullveto author: vitalik title: vitalik-bullveto date: None words: 1253 flesch: 45 summary: And if the vetocracy vs bulldozer axis is anything like the libertarian vs authoritarian axis, it's inevitably going to have internal subtleties and contradictions: much like a free society will see people voluntarily joining internally autocratic corporations (yes, even lots of people who are totally not economically desperate make such choices), many movements will be vetocratic internally but bulldozery in their relationship with the outside world. The vetocracy vs bulldozer axis, on the other hand, continues to map to non-governmental structures quite well - potentially making it very relevant in discussing these new kinds of non-governmental structures that are becoming increasingly important. keywords: bulldozer; people; vetocracy cache: vitalik-bullveto.html plain text: vitalik-bullveto.txt item: #2347 of 3327 id: vitalik-cantor author: vitalik title: vitalik-cantor date: None words: 541 flesch: 67 summary: Whereas the size of the set of integers is just plain infinite, and the set of rational numbers is just as big as the integers (because you can map every rational number to an integer by interleaving the digits of its numerator and denominator, eg. \(0.456456456.... = \frac{456}{999} = \frac{152}{333} \rightarrow 135323\)), the size of the set of real numbers is some kind of even bigger infinity, because there is no way to make a similar mapping from real numbers to the integers. There's the mapping from real numbers to integers. keywords: number cache: vitalik-cantor.html plain text: vitalik-cantor.txt item: #2348 of 3327 id: vitalik-cbc_casper author: vitalik title: vitalik-cbc_casper date: None words: 2427 flesch: 65 summary: CBC Casper is designed to be fundamentally very versatile and abstract, and come to consensus on pretty much any data structure; you can use CBC to decide whether to choose 0 or 1, you can make a simple block-by-block chain run on top of CBC, or a \(2^{92}\)-dimensional hypercube tangle DAG, and pretty much anything in between. \(A\) and \(C\) illegally switch over to support \(B\)'s block (and can get penalized for this), giving it a 3-2 advantage, and at this point it becomes legal for \(D\) and \(E\) to also switch over. keywords: block; chain; rule; validators cache: vitalik-cbc_casper.html plain text: vitalik-cbc_casper.txt item: #2349 of 3327 id: vitalik-central_planning author: vitalik title: vitalik-central_planning date: None words: 3494 flesch: 46 summary: However, for many social systems, truly large-scale, repeatable tests are difficult if not impossible. Because simpler systems are easier to understand, and easier for people to understand that a given implementation is not unfairly privileging special interests, it is easier to create common knowledge that the system is fair, creating a stronger sense of trust. keywords: complexity; example; planning; property; simplicity; system cache: vitalik-central_planning.html plain text: vitalik-central_planning.txt item: #2350 of 3327 id: vitalik-christmas author: vitalik title: vitalik-christmas date: None words: 972 flesch: 68 summary: This structure has pretty much no reasonable geometric interpretation, so I'll just give you the addition and multiplication tables: OK fine, here are all possible lines, excluding the horizontal and the vertical lines (which are also admissible) for brevity: The lack of geometric interpretation does make the game harder to play; you pretty much have to memorize the twenty winning combinations, though note that they are basically rotations and reflections of the same four basic shapes (axial line, diagonal line, diagonal line starting in the middle, that weird thing that doesn't look like a line). Modular tic-tac-toe Here, we go back down to having two dimensions, except we allow lines to wrap around: X wins Note that we allow diagonal lines with any slope, as long as they pass through all four points. keywords: hand; line cache: vitalik-christmas.html plain text: vitalik-christmas.txt item: #2351 of 3327 id: vitalik-cities author: vitalik title: vitalik-cities date: None words: 3942 flesch: 57 summary: 70% of the coin's supply is generated by an ongoing sale mechanism: anyone with STX (the Stacks native token) can send their STX to the city coin contract to generate city coins; the STX revenues are distributed to existing city coin holders who stake their coins. Hence, it's important for city governments to think carefully about these issues, and choose a path that makes sense for the long term. keywords: blockchain; cities; city; coin; government; ideas; people; voting cache: vitalik-cities.html plain text: vitalik-cities.txt item: #2352 of 3327 id: vitalik-collusion author: vitalik title: vitalik-collusion date: None words: 4230 flesch: 47 summary: It's a common pattern among coin voting governance systems to add this kind of superlinearity to prevent self-voting from undermining the entire system; most DPOS schemes have a limited number of delegate slots with zero rewards for anyone who does not get enough votes to join one of the slots, with similar effect. Bribes can even be obfuscated: imagine a cryptocurrency exchange that offers zero fees and spends the effort to make an abnormally good user interface, and does not even try to collect a profit; instead, it uses coins that users deposit to participate in various coin voting systems. keywords: collusion; identity; key; mechanism; system; user; voting cache: vitalik-collusion.html plain text: vitalik-collusion.txt item: #2353 of 3327 id: vitalik-communitynotes author: vitalik title: vitalik-communitynotes date: None words: 4382 flesch: 60 summary: What do I think about Community Notes? Community Notes is a fact-checking tool that sometimes attaches context notes, like the one on Elon's tweet above, to tweets as a fact-checking and anti-misinformation tool. keywords: algorithm; community; helpfulness; note; polarity; users; votes cache: vitalik-communitynotes.html plain text: vitalik-communitynotes.txt item: #2354 of 3327 id: vitalik-complexity author: vitalik title: vitalik-complexity date: None words: 1481 flesch: 57 summary: Sometimes, a sacrifice of a little bit of systemic complexity to allow a great reduction of encapsulated complexity really is the best thing to do. One powerful intellectual tool that allows for more nuanced thinking about complexity is to draw a distinction between what we will call encapsulated complexity and systemic complexity. keywords: complexity; signatures cache: vitalik-complexity.html plain text: vitalik-complexity.txt item: #2355 of 3327 id: vitalik-concave author: vitalik title: vitalik-concave date: None words: 1866 flesch: 56 summary: And for this reason, a low tax is generally better than a coin flip between high tax and no tax. A common example is the question of setting tax rates. keywords: concave; convex; tax cache: vitalik-concave.html plain text: vitalik-concave.txt item: #2356 of 3327 id: vitalik-control_as_liability author: vitalik title: vitalik-control_as_liability date: None words: 1253 flesch: 55 summary: India, Russia and many other jurisdictions increasingly have or are exploring rules that require data on users within the country to be stored inside the country. it's easier to prevent non-paying users from using software if the software stays on your servers) win out. keywords: control; data; users cache: vitalik-control_as_liability.html plain text: vitalik-control_as_liability.txt item: #2357 of 3327 id: vitalik-coordination author: vitalik title: vitalik-coordination date: None words: 3323 flesch: 50 summary: But if we look at decentralization as being the presence of barriers to harmful collusion, then the picture becomes quite scary, because it shows that those barriers are not nearly as strong as we thought. Forking as Counter-Coordination But we cannot always effectively prevent harmful collusions from taking place. keywords: collusion; coordination; decentralization; game; group; people cache: vitalik-coordination.html plain text: vitalik-coordination.txt item: #2358 of 3327 id: vitalik-coordination_problems author: vitalik title: vitalik-coordination_problems date: None words: 2225 flesch: 50 summary: Light clients can then verify that specific part of a block and check if it's actually invalid. The Core argument is that miners only have a limited role in the Bitcoin system, to secure the ordering of transactions, and they should NOT have the power to determine anything else, including block size limits and other block validity rules. keywords: chain; client; rules; users cache: vitalik-coordination_problems.html plain text: vitalik-coordination_problems.txt item: #2359 of 3327 id: vitalik-cryptoai author: vitalik title: vitalik-cryptoai date: None words: 4604 flesch: 54 summary: Given that AI is very computationally-intensive already, is doing AI inside of cryptographic black boxes even computationally viable? Black-box adversarial machine learning attacks: there are ways to optimize attacks against AI models even without knowing much about the model's internal workings. Worldcoin uses AI models extensively at protocol level, to (i) convert iris scans into short iris codes that are easy to compare for similarity, and (ii) verify that the thing it's scanning is actually a human being. keywords: ais; attacks; data; game; model; training; use cache: vitalik-cryptoai.html plain text: vitalik-cryptoai.txt item: #2360 of 3327 id: vitalik-cypherpunk author: vitalik title: vitalik-cypherpunk date: None words: 3714 flesch: 55 summary: The Ethereum protocol's governance itself is notably non-financialized - and this has made it much more robust than other ecosystems whose governance is more financialized. This is also true in other ways: smart contracts regularly get hacked, users' wallets regularly get hacked, centralized exchanges fail even more spectacularly, etc. keywords: chain; community; crypto; ecosystem; ethereum; people; space; stack; world cache: vitalik-cypherpunk.html plain text: vitalik-cypherpunk.txt item: #2361 of 3327 id: vitalik-daos author: vitalik title: vitalik-daos date: None words: 4401 flesch: 48 summary: Recently, there has been a lot of discourse around the idea that highly decentralized DAOs do not work, and DAO governance should start to more closely resemble that of traditional corporations in order to remain competitive. Curtis Yarvin, an American philosopher whose primary big idea is that corporations are much more effective and optimized than governments and so we should improve governments by making them look more like corporations (eg. by moving away from democracy and closer to monarchy), recently wrote an article expressing his thoughts on how DAO governance should be designed. keywords: daos; decentralization; funding; governance; need; optimism; oracle; order cache: vitalik-daos.html plain text: vitalik-daos.txt item: #2362 of 3327 id: vitalik-deeperdive author: vitalik title: vitalik-deeperdive date: None words: 5153 flesch: 64 summary: Unfortunately, Ethereum state proofs are complicated, but there exist libraries for verifying them, and if you use these libraries, this mechanism is not too complicated to implement. Pre-confirmations (from sequencers, attesters, etc) are not an acceptable solution for L1 reading L2. keywords: chain; key; keystore; kzg; proofs; state cache: vitalik-deeperdive.html plain text: vitalik-deeperdive.txt item: #2363 of 3327 id: vitalik-dont_overload author: vitalik title: vitalik-dont_overload date: None words: 2905 flesch: 57 summary: Fred creates an ETH/USD price oracle, which functions by allowing Ethereum validators to participate and vote. However, if you are already relying on Ethereum validators, then one possible direction to take is to move away from trying to manage an independent chain entirely, and become a validium with proofs anchored into Ethereum. keywords: community; consensus; ethereum; oracle; price; risk cache: vitalik-dont_overload.html plain text: vitalik-dont_overload.txt item: #2364 of 3327 id: vitalik-election author: vitalik title: vitalik-election date: None words: 5285 flesch: 60 summary: Prediction markets are a subject that has interested me for many years. And if nobody has done this, who are you to think that you're smarter than everyone else? Ne0liberal's Twitter thread just before Election Day does an excellent job summarizing his case against prediction markets being accurate at that time. keywords: bet; chance; dai; election; markets; people; prediction; trump cache: vitalik-election.html plain text: vitalik-election.txt item: #2365 of 3327 id: vitalik-election_zhTW author: vitalik title: vitalik-election_zhTW date: None words: 188 flesch: 8 summary: * 高額的手續費（如PredictIt的5%提款費用） 而這也是我在9月份反駁ne0liberal的原因：雖然呆板的舊世界中心化預測市場有很高的手續費和很低的投注上限，但加密貨幣市場沒有！在Augur或Omen上，如果有人認為某個預測結果token的價格過低或過高，那麽他可以無限制的買入或賣出。而當時基於區塊鏈的預測市場趨勢和PredictIt的相仿。如果真的是因為高手續費和低投注上限的關係，讓頭腦更冷靜的交易者無法戰勝過於樂觀的交易者，才導致川普最後被高估的話，那麽為什麽明明區塊鏈市場沒有這些問題，卻也有著同樣的價格走勢呢？ 我Twitter上的朋友對此給出的主要回應是，區塊鏈預測市場極端小眾，只有很少人在用，而要在很少人中找到很瞭解政治的人就更少了，所以他們沒辦法輕易接觸到加密貨幣。這看起來似乎很有道理，但我對這個論點不太有信心。於是我押了$2000對賭川普當選，就沒有再繼續下去。 大選中 然後，選舉發生了。一開始雖然我們以為自己預測錯誤，被川普贏得的大量席位嚇死，拜登還是最終的贏家。至於究竟大選本身到底有沒有吻合，還是不吻合預測市場的效率嘛，據我所知，這是一個大哉問。一方面，通過標準的貝氏定理，我應該降低對預測市場的信心，至少我應該更相信Nate Silver。預測市場給出了拜登60%的勝算，而Nate Silver給出了拜登90%的勝算。既然拜登事實上贏了，這就是一個證據，證明在我生活的世界中Nate的答案比較正確。 但另一方面，你可以說預測市場對贏多少的估計更勝一籌。Nate機率分布的中位數是538張選舉人票中的370張左右會給拜登： 雖然川普市場沒有給出機率分布，但如果你要從「川普有40%的勝算」這個統計中推一個機率分布，你的中位數可能會是拜登拿到300張選票人票左右。實際結果是：306票。所以，預測市場與Nate的孰優孰劣，在我看來，還在未定之天。 選後 但當時我無法想像的是，選舉本身只是一個開始。選舉結束幾天後，拜登就被各大組織，甚至一些外國政府宣布當選。川普不出意料的對選舉結果發起了各種法律戰，但這些舉動很快就失敗了。儘管如此，在一個多月的時間裡，NTRUMP token的價格一直保持在85美分！ 一開始，人們似乎有理由猜測川普有15%的機會推翻選舉結果，畢竟他任命了三名法官進入最高法院，當黨派紛爭加劇的時候，許多法官都開始站隊而非堅守原則。在接下來的三周裡，明顯看得出來這些法律戰都失敗了，雖然川普的希望也隨著時間的推移繼續顯得更加嚴峻，但NTRUMP的價格並沒有動搖；事實上，它甚至短暫地下降到$0.82左右。在12月11日，大選結束已經過了5個星期的時候，最高法院果斷地一致駁回了川普推翻投票結果的企圖，這讓NTRUMP價格終於漲到了$0.88。 到了11月，我終於相信市場懷疑論者是對的，所以我自己也投身其中，與川普對賭。這個決定並不是為了錢，畢竟在不到兩個月之後，光是我手上有的dogecoin升值就能讓我賺得比預測市場更多，讓我能夠捐給GiveDirectly。所以不如說這是為了參與一場實驗，不僅是作為一個觀察者，而是作為一個積極的參與者，這樣能提高我對其他人的理解，到底為什麼大家沒有趕在我之前蜂擁而上購買NTRUMP。 進場 我的NTRUMP是在Catnip上買的，Catnip是一個前端界面，它將Augur預測市場和Balancer結合在一起，Balancer是一個Uniswap風格的恒定功能做市商。Catnip是迄今為止做預測市場交易最好用的界面，我覺得它對Augur的可用性貢獻很大。 有兩種方式可以用Catnip對賭川普。 使用DAI直接在Catnip上購買NTRUMP。 使用Foundry呼叫Augur功能，將1個DAI轉換成1個NTRUMP+1個YTUMP+1個ITRUMP（「I」代表「無效」，後面會詳細介紹），然後將YTRUMP賣到Catnip上 一開始，我只知道第一個選項。但後來我發現Balancer上YTRUMP的流動性更高，所以我轉到第二個選項。 還有一個問題：我沒有任何DAI。我有ETH，我可以賣出我的ETH來獲得DAI，但我不想犧牲我的ETH曝險部位；就算我在對川普的押注中賺取了$50,000，如果我因為ETH價格變化而讓我賠了了$500,000那就得不償失了。所以我決定在MakerDAO上開立抵押債務頭寸（CDP，現在也叫 Vault）來保持我的ETH曝險價格。 CDP是DAI的產生方式：使用者將ETH存入一個smart contract，然後可以提出相當於ETH價值2/3的DAI，這些DAI是新產生出來的。他們可以放入與自己之前提出相同金額的DAI加上額外的利息費用（目前為3.5%），來取回抵押於其中的ETH。如果你存入的ETH抵押品價值下降到低於你取出的DAI價值的150%，任何人都可以開始清算你的Vault，強迫賣掉ETH來買回DAI，並向你收取高額罰金。因此，在價格突然變動的情況下，最好有較高的抵押率；我用價值超過$3的ETH來當我提出$1的CDP抵押品。 回顧一下，下圖顯示了操作過程： 我重複操作了很多次；Catnip上的滑價，代表我通常一次只能做大約$5000到$10000的交易，不然價格會變得太不利（如果我跳過Foundry，直接用DAI購買NTRUMP，基本上只能交易到接近$1000）。兩個月後，我已經累積了367,000個NTRUMP。 為什麼其他人不這麼做？ 在我開始解釋之前，我有四個主要假設，想辦法解釋為什麽沒什麼人以85美分的價格買入明明就值$1的token： 擔心Augur的smart contract會出事 或者川普的支持者會操縱預言機（一種去中心化的機制讓Augur token的持有者可以把token壓在事件結果上，投票決定事件結果），使其回報的結果與發生的事實不符。 資本成本：購買這些token，你必須將資金鎖定兩個月以上，這就讓你不能在期間內使用這些錢，更讓你無法進行其他更好賺的交易。 技術上太複雜了，讓人無法輕易交易。 我想錯了，就算機會天降在你面前，有足夠動力嘗試這種奇怪機會的人真的太少了。 四者聽來都很合理。smart contract出事的話是真 的 危 險，而Augur的預言機之前遇到的環境都沒有如此有爭議，缺乏測試。資本成本是真的，而且雖然在預測市場中對賭比較簡單，比在股票市場中更簡單，畢竟你知道預測市場的價格永遠不會超過$1，但鎖在其中的資本還是會讓你時時想到加密貨幣市場中其他同樣有利可圖的選項。在dapp中做交易在技術上畢竟很複雜，所以對未知有一定程度的恐懼很合理。 但在我實際進入金融壕溝戰之後，觀察這個市場的價格演變，讓我對上述的假設有了更多的了解。 對smart contract漏洞的恐懼 起初，我認為「對smart contract漏洞的恐懼」可能佔了很重要的一部分。但隨著時間的推移，我更加相信這大概不是一個主要因素。要想知道為什麽我這樣想，可以比較YTRUMP和ITRUMP的價格。ITRUMP代表「無效川普」；「無效」是指在一些特殊情況下會觸發的事件結果：當事件描述模糊不清時，當市場結束時真實生活的事件還沒有結束時，當市場本身不道德時（例如暗殺市場），以及其他一些類似情況。在這個市場上，ITRUMP的價格始終保持在$0.02以下。如果有人想通過攻擊市場來賺取利潤，那麽他們不應該$0.15的價格買入YTRUMP，而應該以$0.02的價格買入ITRUMP會更加有利可圖。如果他們買入大量的ITRUMP，且迫使「無效」的結果被觸發，他們就能賺取50倍的回報。所以如果你害怕被攻擊，買入ITRUMP是目前最理性的反應。然而很少有人這麽做。 另一個反對「smart contract出事很可怕」的論點是，在預測市場以外的每一個加密應用中（例如Compound，各種yield farming等），人們對smart contract風險的態度超級樂觀。如果人們只是為了僅僅5-8%的年報率，就願意把錢投入到各種高風險、未經測試的專案中，那麽他們沒有理由在預測市場這邊突然變得這麼謹慎啊？ 資本成本 資本成本 - 鎖定大量資金所帶來的不便和付出機會成本 - 跟以前比起來我現在更能體會這件事。僅從Augur方面來看，我需要鎖定308,249個DAI，平均約兩個月才能獲利$56,803。這樣算下來，年化利率約為175%；這樣看下來，與2020年夏天的各種yield farming熱潮相比，這是相當不錯的選擇。但當你考慮到我必須在MakerDAO上做的操作時，看起來就沒這麼好賺了。因為我想保持在ETH上的曝險不變，所以需要用CDP來獲得DAI，而要安全使用CDP需要3倍以上的抵押比例。因此我實際需要鎖定的資金總額在$100萬左右。 現在，利率看起來不那麽好了。如果再加上smart contract被駭客攻擊的可能性（不管有多小），或者史無前例的政治事件真的發生了，這樣的結果看起來還是不太好。 即使如此，假設鎖倉抵押有3倍，Augur出事的可能性也有3%（我買ITRUMP是為了以防萬一事件結果變成「無效」，所以我只需要擔心事件結果不小心變成「當選」的風險，或者資金被直接偷走），計算出來之後的無風險利率約為35%，如果你考慮人類直覺對風險的看法，結果上會讓利率看起來更低。當然這個交易還是非常有吸引力，只是換句話說，現在看來這個數字不吸引人也可以理解了，因為那些幣圈的人比較習慣頻繁的100倍漲跌。 川普的支持者，當然不用管這些挑戰：他們只投了$60,000，就能對消掉我$308,249的賭注（因為手續費的關係，我賺得比這個數字少）。當機率接近於0或1時，這個賭局對那些想要把機率推離兩端極值的人非常有利。這不僅解釋了川普的狀況，也解釋了那些小眾但沒有勝算的候選人經常獲得高達5%獲勝機率的原因。 技術難度 我最初嘗試在Augur上購買NTRUMP，但技術問題使我無法直接在Augur上下單（我問過的其他人沒有這個狀況...我現在還是不知道這是啥問題) + 0.5 * log(1-r) 我們可以看到預期的對數財富最大化的r值僅為0.0566。結論很清楚：當決策很接近，而且雜訊很大的時候，事實證明投資在市場的資金只能是一小部分，這樣才合理。這已經是假設理性的情況下了，因為大多數人對這種不確定結果的賭博的投資，比凱利公式預言的的要少。再加上資本成本，差距就更大了。但是，如果攻擊者真的不管為了什麼個人理由想要讓結果B發生，他們可以很簡單地將所有資本投進去買該token。總而言之，這個場景對攻擊者相當有利，超過20:1。 當然，現實中的攻擊者很少願意把所有資金押在一個決策上。且futarchy也不是唯一容易被攻擊的機制：股票市場也同樣脆弱，非市場決策機制的部分也可以被有錢又有心的攻擊者以各種方式操縱。盡管如此，我們還是應該特別注意看看，到底futarchy能不能讓我們的決策準確率再創新高。 有趣的是，數學告訴了我們當操縱者想要將結果推向極值時，futarchy反而能發揮最大作用。一個例子是責任保險，像是有人希望以不正當的方式獲得保險理賠時，這相當於強迫把市場估計不利事件發生的機率降到零。事實證明，責任保險是提出futarchy的Robin Hanson的政策處方簽新寵。 預測市場能變得更好嗎？ 我們最後要問的問題是：預測市場會重蹈覆轍嗎？像是12月初的時候，市場預測了川普有15%的機會推翻選舉結果，甚至在最高法院（包括他任命的三名法官）叫他滾蛋之後，市場還是預測有12%的機會川普能推翻選舉結果。或者隨著時間經過，市場能越變越好？出人意料地，我的答案完全偏樂觀，而且我有幾個保持樂觀的理由。 自然選擇下的市場 首先，這些事件讓我對市場效率和理性究竟有了新的看法。很多時候，市場效率的支持者聲稱，市場之所以會有效率，是因為大多數參與者都是理性的（或者至少理性的人超過了其他愚昧群體），當然這件事是正確的，是個公理(axoim)。所以，讓我們試著從進化中的角度來看待正在發生的事情。 加密貨幣是一個年輕的生態系統，與主流社會還相當脫節。雖然Elon最近在Twitter上發表了不少言論，我們還是可以看的出來圈子裡的人們對選舉政治學的方方面面不夠瞭解。那些選舉政治學方面的專家很難進入加密貨幣領域，而且加密貨幣圈子有很多為反而反的政治言論都不怎麼正確。但，今年在加密貨幣圈子內發生的事情是這樣的，正確的預期了拜登獲勝的預測市場使用者，其資本得到了18%的增長，而錯誤預測川普獲勝的預測市場使用者的資本得到了100%的減少（他們投入市場的部分）。 因此，選擇壓力會有利於下注結果正確的人。經過十輪之後，好的預測者會有更多的資本去下注，而壞的預測者會有更少的資本去下注。這不需要任何人在過程中「變得更聰明」或「吸取教訓」，更不需要假設其他人類的推理和學習能力。這僅僅是選擇動力學的結果，隨著時間的推移，善於做出正確猜測的參與者將在生態系統中占據主導地位。 請注意，預測市場在這方面比股票市場表現得更好：股票市場的 「新貴」往往是來自於某次幸運的千倍收益，這成為了信號中的雜訊，但在預測市場中，價格被限定在0和1之間，限制了任何一個單一事件能帶來的影響。 參與者更好 技術也更好 第二，預測市場本身會有進步。使用者界面已經有了很大的改進，並將繼續進一步完善。MakerDAO->Foundry->Catnip現在雖然很複雜，但會被被抽象為單一交易。區塊鏈的擴容技術也會進步，降低參與者的手續費（內建AMM的ZK-rollup Loopring已經在Ethereum主網上線，理論上可以在上面跑一個預測市場）。 第三，我們看到了預測市場正常運行，這樣的例子會讓參與者比較不害怕。使用者會看到，就算在非常有爭議的情況下Augur預言機還是能給出正確的結果（這次有兩輪爭議，但No的那一方還是乾淨利落的贏了）。來自加密貨幣領域之外的人，看到這樣的成功的例子，也會更願意參與其中。也許連Nate Silver自己都可能弄來一些DAI，並在2022年以後使用Augur、Omen、Polymarket和其他市場來增加自己的收入。 第四，預測市場技術本身可以改進。這是我自己提出的一個市場設計建議，可以在保持高資本效率的同時，對許多低機率事件下注。這樣能夠防止許多那些低機率事件的賠率偏高。我相信會有其他的想法出現，且我期待看到更多這方面的實驗。 結論 這個預測市場的事件事件始末，身為第一手試驗非常的有趣，可以讓人看著事件在複雜的個人、社會心理學中演化與碰撞。它展示了實際上市場效率的運作方式，市場效率的局限，以及可以改善的方式。 它也很好地展示了區塊鏈的力量；事實上，對我而言它是Ethereum應用中最有具體價值的一個。區塊鏈經常被批評為投機玩具，只會自我套娃大玩金融遊戲（token, 放去yield farming, 得到的回報是...其他新出現的token），沒有任何有意義的產出。當然也有批評者沒有注意到的例子；我個人從ENS中受益，而且遇過幾次信用卡完全不能用的例子，最後只好使用ETH進行支付時。但，在過去的幾個月裡，我們似乎看到了Ethereum的應用真的對人們有用了，開始與現實世界互動。預測市場就是一個重要的例子 keywords: log(1 cache: vitalik-election_zhTW.html plain text: vitalik-election_zhTW.txt item: #2366 of 3327 id: vitalik-end author: vitalik title: vitalik-end date: None words: 5503 flesch: 60 summary: When I talk to many people from San Francisco, I get a distinct impression that they think that AI is the only thing that matters, San Francisco is the capital of AI, and therefore San Francisco is the only place that matters. Crypto does not need to play this game: it's a big world, and it only takes one visit to Argentina or Turkey or Zambia to remind ourselves that many people still do have important problems that have to do with access to money and finance, and there is still an opportunity to do the complicated work of balancing user experience and decentralization to actually solve those problems in a sustainable way. keywords: crypto; ethereum; money; new; people; space; stack; things; time; world; years cache: vitalik-end.html plain text: vitalik-end.txt item: #2367 of 3327 id: vitalik-endgame author: vitalik title: vitalik-endgame date: None words: 1581 flesch: 59 summary: We get a chain where block production is still centralized, but block validation is trustless and highly decentralized, and specialized anti-censorship magic prevents the block producers from censoring. Once again, we get a world where, block production is centralized, block validation is trustless and highly decentralized, and censorship is still prevented. keywords: block; production; rollup cache: vitalik-endgame.html plain text: vitalik-endgame.txt item: #2368 of 3327 id: vitalik-endnotes author: vitalik title: vitalik-endnotes date: None words: 3964 flesch: 58 summary: But to a large extent, as is the case in many conflicts, the foreign interference card was simply a psychological defense that many Ethereum supporters, myself included, subconsciously used to shield ourselves from the fact that many people within our own community really did have different values. It's a world where blockchains and cryptocurrencies are well poised to play an important part, though for reasons much more complex than many people think, and having as much to do with cultural forces as anything financial (one of the more underrated bull cases for cryptocurrency that I have always believed is simply the fact that gold is lame, the younger generations realize that it's lame, and that $9 trillion has to go somewhere). keywords: bitcoin; crypto; ethereum; people; supporters; time; world cache: vitalik-endnotes.html plain text: vitalik-endnotes.txt item: #2369 of 3327 id: vitalik-ens author: vitalik title: vitalik-ens date: None words: 3551 flesch: 63 summary: Domain name owners are often not sophisticated, the costs of switching domain names are often high, and negative externalities of a name-change gone wrong can be large. Dark Mode Toggle Should there be demand-based recurring fees on ENS domains? keywords: bid; domain; ens; fee; time; year cache: vitalik-ens.html plain text: vitalik-ens.txt item: #2370 of 3327 id: vitalik-enshrinement author: vitalik title: vitalik-enshrinement date: None words: 6299 flesch: 55 summary: But even if we do that, there is one huge reason why enshrined protocol features are going to inevitably be significantly cheaper than EVM code, no matter how efficient the EVM becomes: enshrined code does not need to pay gas for being pre-loaded. Enshrining liquid staking A common demand among Ethereum defi users is the ability to use their ETH for staking and as collateral in other applications at the same time. keywords: account; code; ethereum; evm; gas; protocol; staking; transaction; users cache: vitalik-enshrinement.html plain text: vitalik-enshrinement.txt item: #2371 of 3327 id: vitalik-excited author: vitalik title: vitalik-excited date: None words: 5722 flesch: 51 summary: Hybrid applications There are many applications that are not entirely on-chain, but that take advantage of both blockchains and other systems to improve their trust models. Decentralization for efficiency Decentralization for efficiency is a different school of thought: decentralized governance structure is valuable because it can incorporate opinions from more diverse voices at different scales, and decentralized implementation is valuable because it can sometimes be more efficient and lower cost than traditional legal-system-based approaches. keywords: applications; chain; cryptocurrency; dao; decentralization; efficiency; governance; robustness; stablecoins; system; users cache: vitalik-excited.html plain text: vitalik-excited.txt item: #2372 of 3327 id: vitalik-exploring_ecp author: vitalik title: vitalik-exploring_ecp date: None words: 3515 flesch: 62 summary: Pairings go a step further in that they allow you to check certain kinds of more complicated equations on elliptic curve points — for example, if \(P = G \cdot p, Q = G \cdot q\) and \(R = G \cdot r\), you can check whether or not \(p \cdot q = r\), having just \(P, Q\) and \(R\) as inputs. A third way to look at what pairings do, and one that is perhaps most illuminating for most of the use cases that we are about, is that if you view elliptic curve points as one-way encrypted numbers (that is, \(encrypt(p) keywords: \cdot; curve cache: vitalik-exploring_ecp.html plain text: vitalik-exploring_ecp.txt item: #2373 of 3327 id: vitalik-fft author: vitalik title: vitalik-fft date: None words: 4163 flesch: 63 summary: >>> domain = [1, 85, 148, 111, 336, 252, 189, 226] >>> def modular_inverse(x, n): return pow(x, n - 2, n) >>> values = fft([3,1,4,1,5,9,2,6], 337, domain) >>> values [31, 70, 109, 74, 334, 181, 232, 4] >>> inverse_fft(values, 337, domain) [5,9,8,1,0,0,0,0] >>> x1 = fft(p1, 337, domain) >>> x1 keywords: \cdot; domain; field; polynomial cache: vitalik-fft.html plain text: vitalik-fft.txt item: #2374 of 3327 id: vitalik-forks_and_markets author: vitalik title: vitalik-forks_and_markets date: None words: 2030 flesch: 60 summary: Hard forks allow the developers much more flexibility in making the protocol upgrade, as they do not have to take care to make sure that the new rules fit into the old rules Soft forks are more convenient for users, as users do not need to upgrade to stay on the chain Soft forks are less likely to lead to a chain split Soft forks only really require consent from miners/validators (as even if users still use the old rules, if the nodes making the chain use the new rules then only things valid under the new rules will get into the chain in any case); hard forks require opt-in consent from users Aside from this, one major criticism often given for hard forks is that hard forks are coercive. Dark Mode Toggle Hard Forks, Soft Forks, Defaults and Coercion 2017 Mar 14 See all posts One of the important arguments in the blockchain space is that of whether hard forks or soft forks are the preferred protocol upgrade mechanism. keywords: chain; forks; rules cache: vitalik-forks_and_markets.html plain text: vitalik-forks_and_markets.txt item: #2375 of 3327 id: vitalik-free_speech author: vitalik title: vitalik-free_speech date: None words: 2266 flesch: 57 summary: Some use the concept of safe spaces as a sword, wielded to annex public spaces and demand that people within those spaces conform to their private norms. So to conclude: censorship in public spaces bad, even if the public spaces are non-governmental; censorship in genuinely private spaces (especially spaces that are not defaults for a broader community) can be okay; ostracizing projects with the goal and effect of denying access to them, bad; ostracizing projects with the goal and effect of denying them scarce legitimacy can be okay. keywords: bitcoin; people; power; spaces cache: vitalik-free_speech.html plain text: vitalik-free_speech.txt item: #2376 of 3327 id: vitalik-garbled author: vitalik title: vitalik-garbled date: None words: 1904 flesch: 67 summary: Here is the usual setup for the scheme: Suppose that there are two parties, Alice and Bob, who want to compute some function f(alice_inputs, bob_inputs), which takes inputs from both parties. She passes along inputs, also encrypted in a way that's compatible with the encrypted circuit, to Bob. keywords: alice; bob cache: vitalik-garbled.html plain text: vitalik-garbled.txt item: #2377 of 3327 id: vitalik-gas_analysis author: vitalik title: vitalik-gas_analysis date: None words: 900 flesch: 61 summary: For each block, it contains an object of the form: { block:4710000, coinbase:0x829bd824b016326a401d083b33d092293333a830, deciles:[40,40.1,44.100030001,44.100030001,44.100030001,44.100030001,44.100030001,44.100030001,50,66.150044,100] ,free:10248, timedelta:8 } The deciles variable contains 11 values, where the lowest is the lowest gasprice in each block, the next is the gasprice that only 10% of other transaction gasprices are lower than, and so forth; the last is the highest gasprice in each block. In general, however, what we see seems to be a rather well-functioning fee market, though there is still room to improve in fee estimation and, most importantly of all, continuing to work hard to improve base-chain scalability so that more transactions can get included in the first place. keywords: gasprice cache: vitalik-gas_analysis.html plain text: vitalik-gas_analysis.txt item: #2378 of 3327 id: vitalik-gini author: vitalik title: vitalik-gini date: None words: 2019 flesch: 54 summary: Given the level of concern about these issues, it should be not at all surprising that many people have tried computing Gini indices of cryptocurrencies: What is the Gini coefficient? The Gini coefficient is a measure of inequality introduced by Corrado Gini in 1912. keywords: coefficient; gini; income; inequality cache: vitalik-gini.html plain text: vitalik-gini.txt item: #2379 of 3327 id: vitalik-gitcoin author: vitalik title: vitalik-gitcoin date: None words: 2180 flesch: 51 summary: Dominance of large projects One other pattern that we saw in this round is that popular projects got disproportionately large grants: To be clear, this is not just saying more contributions, more match, it's saying more contributions, more match per dollar contributed. The different lines are for different projects; supporting projects with higher existing support will lead to you getting a bigger multiplier. keywords: funding; gitcoin; grants; projects cache: vitalik-gitcoin.html plain text: vitalik-gitcoin.txt item: #2380 of 3327 id: vitalik-gpt3 author: vitalik title: vitalik-gpt3 date: None words: 1655 flesch: 71 summary: There is a base-58 format for IPFS hashes, but those are called QM hashes, not bafyhashes. function bafyToHex(bafyString) { // Create a lookup table for the base32 alphabet var alphabet = 'abcdefghijklmnopqrstuvwxyz234567'; var base = alphabet.length; var lookupTable = {}; alphabet.split(').forEach(function(char, i) { keywords: base; hash; ipfs cache: vitalik-gpt3.html plain text: vitalik-gpt3.txt item: #2381 of 3327 id: vitalik-halo author: vitalik title: vitalik-halo date: None words: 4257 flesch: 69 summary: Though it's not really mathematically accurate to think of elliptic curve points as being like real numbers that have sizes, area is nevertheless a good intuition for thinking about linear combinations of elliptic curve points like we use in these commitments. On the whole, the proof contains \(2 * log(n)\) elliptic curve points and one number (for pedants: one field element). keywords: \cdot; linear; polynomial; proof; prover cache: vitalik-halo.html plain text: vitalik-halo.txt item: #2382 of 3327 id: vitalik-homomorphic author: vitalik title: vitalik-homomorphic date: None words: 5030 flesch: 65 summary: The decryption procedure is itself a circuit, which contains additions or multiplications, so it will introduce new error, but this new error does not depend on the amount of error in the original encryption. The idea is that we refresh the ciphertext by turning it into a new ciphertext of \(m\) under another key \(p_2\), where this process clears out the old error (though it will introduce a fixed amount of new error). keywords: \(p\; ciphertext; error; key cache: vitalik-homomorphic.html plain text: vitalik-homomorphic.txt item: #2383 of 3327 id: vitalik-hybrid_layer_2 author: vitalik title: vitalik-hybrid_layer_2 date: None words: 2088 flesch: 51 summary: A long-forgotten blog post from 2014 introduced the idea of shadow chains, an architecture where block data is published on-chain, but blocks are not verified by default. There is thus a strong case to be made for developers of layer 2 scalability solutions to move to be more willing to publish per-user data on-chain at least some of the time: it greatly increases ease of development, generality and security and reduces per-user load (eg. no need for users storing history data). keywords: chain; data; plasma; rollup cache: vitalik-hybrid_layer_2.html plain text: vitalik-hybrid_layer_2.txt item: #2384 of 3327 id: vitalik-institutions author: vitalik title: vitalik-institutions date: None words: 2264 flesch: 46 summary: This seemed to me to be an important and valuable insight, though in a somewhat different direction: yes, that is the style of institution that people find familiar and are not weirded out by (as they might when they see many of the alternative institutions that Hanson likes to propose), but it's also exactly the style of institutions that anti-institutionalists tend to most strongly rail against! Marriage is more institution-y than romantic relationships, likely because of its official stamp of recognition, and more mainstream relationship styles are more institution-y than less mainstream styles (a pattern that repeats itself when comparing NYT vs Russia Today vs Bitcoin Magazine). keywords: anti; elites; institution; people cache: vitalik-institutions.html plain text: vitalik-institutions.txt item: #2385 of 3327 id: vitalik-l2types author: vitalik title: vitalik-l2types date: None words: 2479 flesch: 60 summary: (2) is important too, because it means that you can have a wallet that allows easy key changes and that holds assets across a large number of different chains. For example: Between rollup and validium: a validium where anyone could make an on-chain payment to cover the cost of transaction fees, at which point the operator would be forced to provide some data onto the chain or else lose a deposit. keywords: chain; data; ethereum; security cache: vitalik-l2types.html plain text: vitalik-l2types.txt item: #2386 of 3327 id: vitalik-layer_1 author: vitalik title: vitalik-layer_1 date: None words: 2035 flesch: 46 summary: Hence, the other extreme position, that blockchain base layers can be truly absolutely minimal, and not bother with either a quasi-Turing-complete execution engine or scalability to beyond the capacity of a single node, is also clearly false; there is a certain minimal level of complexity that is required for base layers to be powerful enough for applications to build on top of them, and we have not yet reached that level. The first is that layer 1 solutions require ongoing protocol change to happen at the base protocol layer, base layer protocol change requires governance, and it has still not been shown that, in the long term, highly activist blockchain governance can continue without causing ongoing political uncertainty or collapsing into centralization. keywords: base; blockchain; execution; layer cache: vitalik-layer_1.html plain text: vitalik-layer_1.txt item: #2387 of 3327 id: vitalik-layer_3 author: vitalik title: vitalik-layer_3 date: None words: 2867 flesch: 61 summary: Dark Mode Toggle What kind of layer 3s make sense? One topic that often re-emerges in layer-2 scaling discussions is the concept of layer 3s. keywords: batch; data; layer; rollups; scaling cache: vitalik-layer_3.html plain text: vitalik-layer_3.txt item: #2388 of 3327 id: vitalik-legitimacy author: vitalik title: vitalik-legitimacy date: None words: 4200 flesch: 55 summary: While Bitcoin and Ethereum do already rely on conceptions of legitimacy to respond to 51% attacks, using conceptions of legitimacy to guide in-protocol funding of public goods is much harder. There's even a selfish reason to participate in this equilibrium: if you were the developer of an Ethereum wallet, or an author of a podcast or newsletter, and you saw two competing projects, one of which contributes significantly to ecosystem-level public goods including yourself and one which does not, for which one would you do your utmost to help them secure more market share? NFTs: supporting public goods beyond Ethereum The concept of supporting public goods through value generated out of the ether by publicly supported conceptions of legitimacy has value going far beyond the Ethereum ecosystem. keywords: community; ecosystem; ethereum; funding; goods; legitimacy; people cache: vitalik-legitimacy.html plain text: vitalik-legitimacy.txt item: #2389 of 3327 id: vitalik-legitimacy_ES author: vitalik title: vitalik-legitimacy_ES date: None words: 4496 flesch: 50 summary: Aquí hay dos ideas potenciales: Alguna institución (o incluso DAO) podría bendecir a los NFT a cambio de una garantía de que una parte de los ingresos se destina a una causa benéfica, asegurando que varios grupos se beneficien al mismo tiempo. Es imposible hacer una lista completa de las teorías de la legitimidad, pero podemos comenzar con algunas: Legitimidad por fuerza bruta: alguien convence a todos de que son lo suficientemente poderosos como para imponer su voluntad y resistirlos será muy difícil. keywords: bienes; capital; como; comunidad; con; coordinación; del; ecosistema; este; esto; está; ethereum; hay; las; legitimidad; los; mucho; más; nft; para; pero; por; proyecto; puede; públicos; que; qué; social; también; todos; una cache: vitalik-legitimacy_ES.html plain text: vitalik-legitimacy_ES.txt item: #2390 of 3327 id: vitalik-limits author: vitalik title: vitalik-limits date: None words: 5028 flesch: 48 summary: Nathan then expands: I have argued that pairing cryptoeconomics with political systems can help overcome the limitations that bedevil cryptoeconomic governance alone. Token holders could earn rewards by successfully challenging a newsroom's practices; the success or failure of a challenge ultimately depended on the judgment of the Civil Council, designed to be free of economic incentives clouding its deliberations. keywords: collusion; cryptoeconomics; finance; governance; kleros; market; nathan; people; systems cache: vitalik-limits.html plain text: vitalik-limits.txt item: #2391 of 3327 id: vitalik-marketmakers author: vitalik title: vitalik-marketmakers date: None words: 2792 flesch: 63 summary: Now, this does not mean that market makers cannot lose money, compared to other holding strategies. That said, this may actually be an argument in favor of subsidied market makers: if such multiplier effects exist, then they will have a positive impact on price stability that goes beyond the first-order effect of the liquidity that the market maker itself provides. keywords: eth; maker; market; mkr; price cache: vitalik-marketmakers.html plain text: vitalik-marketmakers.txt item: #2392 of 3327 id: vitalik-maximalist author: vitalik title: vitalik-maximalist date: None words: 3346 flesch: 56 summary: We live in a dangerous world, and protecting freedom is serious business Hopefully, this is much more obvious now than it was six weeks ago, when many people still seriously thought that Vladimir Putin is a misunderstood and kindly character who is merely trying to protect Russia and save Western Civilization from the gaypocalypse. They are used as a primary lifeline by many people to make their payments and store their savings. keywords: bitcoin; blockchains; cryptocurrency; money; people; vitalik; world cache: vitalik-maximalist.html plain text: vitalik-maximalist.txt item: #2393 of 3327 id: vitalik-metcalfe author: vitalik title: vitalik-metcalfe date: None words: 1671 flesch: 53 summary: This could arise because (a) A users have a higher opinion of A than B users, or (b) A users have a lower opinion of B than B users. Note that as in case 2, if users are switching from a larger system to a smaller system, then that means that they find the smaller system to have higher intrinsic quality, although, also as in case 2, if the split remains a split and does not become a full-scale migration, then that means other users see the intrinsic quality of the larger system as higher, or at least not lower by enough to be worth the network effects. keywords: users cache: vitalik-metcalfe.html plain text: vitalik-metcalfe.txt item: #2394 of 3327 id: vitalik-moe author: vitalik title: vitalik-moe date: None words: 1862 flesch: 65 summary: Oct 17 See all posts One kind of token model that has become popular among many recent token sale projects is the network medium of exchange token. If the appcoin starts falling at 10% per year, however, then the de-facto fee grows to $0.035, driving many users away and accelerating its growth. keywords: token; users; value cache: vitalik-moe.html plain text: vitalik-moe.txt item: #2395 of 3327 id: vitalik-mvb author: vitalik title: vitalik-mvb date: None words: 1834 flesch: 50 summary: Sufficient data scalability and low latency It turns out that plasma and channels, and other layer 2 protocols that are fully off-chain have some fundamental weaknesses that prevent them from fully replicating the capabilities of layer 1. Layer 2 should be the site of ongoing innovation, layer 1 should be the site of stability and maintenance, with large changes only in emergencies (eg. a one-time set of serious breaking changes to prevent the base protocol's cryptography from falling to quantum computers would be okay). keywords: data; layer; protocols cache: vitalik-mvb.html plain text: vitalik-mvb.txt item: #2396 of 3327 id: vitalik-neoplasma author: vitalik title: vitalik-neoplasma date: None words: 2459 flesch: 66 summary: One solution is to optimize by treating many adjacent coins as a single unit, which can be transferred or exited all at once. Use Plasma Cashflow, which simply represents many adjacent coins as a single object. keywords: chain; coin; plasma; state cache: vitalik-neoplasma.html plain text: vitalik-neoplasma.txt item: #2397 of 3327 id: vitalik-networkstates author: vitalik title: vitalik-networkstates date: None words: 8053 flesch: 58 summary: Network states would be run by DAOs, and this would apply to network states too. What do I think about network states? keywords: balaji; communities; community; countries; governance; network; network states; new; people; society; startup; states; way; world cache: vitalik-networkstates.html plain text: vitalik-networkstates.txt item: #2398 of 3327 id: vitalik-networkstates_zhCN author: vitalik title: vitalik-networkstates_zhCN date: None words: 412 flesch: 34 summary: 。 有没有中间道路？ 到目前为止，我的判断是网络国家非常出色，但这还远不是一个可行的大妥协方案（Big Compromise Idea），可以填补所有的漏洞，建设起我和我的大部分读者们期待见到的属于二十一世纪的世界。最终，我确实觉得，我们需要引进更多的民主和大规模协同导向的某种大妥协方案，来让网络国家真正取得成功。 以下是我支持的对巴拉吉主义的一些重大调整： 由创始人启动没问题（虽然并非唯一道路），但我们真的需要内置一个「权力移交社区」（exit-to-community）的路线图。 很多创始人希望最终退休，或者开始新事业（基本上一半的加密项目如此），在这种情况下，我们需要能够防止网络国家崩溃，或者滑向平庸。这个过程中的一部分，是宪法将对「权力移交社区」提供保障：当网络国家更成熟、更具规模时，更多社区成员的参与将被自动纳入考量。 Prospera（译者注：洪都拉斯的一个特许城市）尝试过类似的事情。斯科特-亚历山大（Scott Alexander）总结道： 当 Prospera 有十万名居民时（现实地说离现在很遥远，即使实验很成功），他们将公投，51% 的大多数可以修改宪章的任何条款，包括将 Dark Mode Toggle 「网络国家」之我见 2022 Jul 13 See all posts 感谢 付航 ，Roy，Zik 和其他的GreenpillCN社区参与者翻译 7 月 4 日，巴拉吉-斯里尼瓦山（Balaji Srinivasan）发表了人们 期待已久的新书，描绘他心目中对「网络国家」的愿景：社区纷纷围绕着各自的愿景组织运作起来，起初是各类线上俱乐部，但随着不断树立起越来越大的影响力，最终大到足以寻求政治自治，甚至谋求外交承认。 网络国家可以视为一种尝试，它试图成为自由意志主义思想体系的继承者：巴拉吉本人屡次夸赞《主权个人》一书（参见我的小 读后感），认为它是重要的读物和灵感源泉。但同时，他也与该书的思想在一些主要方面存在分野，集中体现在他在新作中对社会关系中非个人主义和非货币层面的许多论述，比如关于道德准则和社区。网络国家还可以看成是另一种尝试，即：为加密领域勾勒出可能更为宏大的政治叙事。与其在互联网的角落里画地为牢，与广阔的世界脱节，区块链更可以在组织大部分人类社会的新途径中，发挥核心的作用。 这些都可谓是千金之诺。网络国家能够不负所期吗？它是否能切实提供激动人心的裨益？我们先按下网络国家的种种功德不表，把这样一个想法与区块链和加密货币绑定起来，真的说的通吗？另一方面，这样的世界愿景是否遗漏掉了任何至关重要的东西？本文试图展现我对这些问题的思考。 目录 什么是网络国家？ 我们能建设什么样的网络国家 巴拉吉式网络国家的大政治观是什么？ 要接受网络国家就不得不同意巴拉吉的大政治观吗？ 加密货币与网络国家有何关系？ 我喜欢巴拉吉愿景的哪些方面？ 巴拉吉的构想里哪些是我持保留态度的？ 非巴拉吉式的网络国家 有没有中间道路？ 什么是网络国家？ 巴拉吉给出了几个简短的定义，帮助人们理解什么是网络国家。首先，他用一句话定义： 网络国家是目标高度一致的网络社区，有采取集体行动的能力，能够在世界各地众筹领土，最终获得既有国家的外交承认。 上述这句话到目前为止并无争议。创造一个新的网络社区，当成长到足够大的时候，在线下将其实体化，并且最终通过谈判来尝试获得某种地位。在这样一个定义下，无论任何政治意识形态中的人，几乎都能够找寻到自己支持的某些形态的网络国家。但现在，我们来看看他的更长版本的定义： 网络国家就是一个社会网络，它有着道德层面的创新、国民意识和公认的创始人；其集体有行动力，成员个人则文明谦恭；它集成了加密货币，基于共识设立政府，权力由社会智能合约限制；众筹而来的列岛是其真实领土，首都则是虚拟的；通过链上普查来证实其人口、收入和地产规模，使其足以赢得某种程度的外交承认。 此处，这一概念开始得到主观上的强化：我们并不仅仅是在谈论网络社区的一般性概念，不是那些具有集体能动性并且最终尝试在土地上实体化的网络社区；我们所谈论的是在巴拉吉的愿景中网络国家应该是个什么样子。支持广义上的网络国家，但不同意巴拉吉对网络国家应具有何种属性持不同意见是完全有可能的。比如说，如果你还没有成为「加密新信徒」， 就很难理解为什么「集成加密货币」在这个网络国家的概念里如此重要——虽然巴拉吉在稍后的章节里为他的选择进行了辩护。 最后，他将巴拉吉式网络国家的概念扩展成了更长的版本：先是一篇「千字文」（显然，巴拉吉式网络国家采用了 八进制，因为实际字数恰好是 512=8^3）；然后，是一篇 论文，最后，是这本书末尾的 整整一章。 当然，还附了 一张图： image 巴拉吉不惜连篇累牍加以强调的重要观点是，任何成功的新社区都无可避免地需要道德这一成分。他写道： 在这次谈话的 11 分钟处，保罗·约翰逊给出了一个简短的答案。他指出，美洲殖民早期，宗教性殖民地的成功率比盈利性殖民高，因为前者有使命感。略长一点的答案则是，在一个初创社会，你不是去请求人们购买某个产品（经济性的、具有个人主义色彩的营销），而是请求他们加入一个社区（文化层面上的、具有集体主义色彩的宣传）。 宗教社群的承诺悖论（commitment paradox）是关键：与人们的直觉相反，对成员要求最高的宗教社群反而最为持久。 https://vitalik.ca/images/networkstates/communes.png 这就是巴拉吉主义与更加传统的新自由主义—资本主义的截然不同之处——后者的理想型是无害化的、去政治化的、缺乏激情的消费主义「末人」（last man）。与自由论者稻草人式的诡辩不同，巴拉吉并不相信任何东西都「仅仅是一件消费品」。相反，他极力强调社会规范对凝聚力的重要性，以及，让价值观附带一点所谓的宗教性，才能让一个特定网络国家真正有别于外部世界。正如巴拉吉在 这期播客 的 18：20 处所说，如今大多数试图建立私人国家的自由论者就如同「没了犹太教的犹太复国主义」，而这也正是他们失败的关键原因。 这种认识并不是全新的。其实，安东尼奥-加西亚-马丁内斯（ Antonio Garcia Martinez ）对巴拉吉较早前有关主权—个人观点的批评正是着力于此（详见 这档播客约 27:00 处）。巴拉吉曾赞赏那些身处迈阿密的古巴流亡者，称他们坚韧不拔。这些人＂或许不太理性地声称，迈阿密是我们的新家园，是我们最后的庇护所＂。而福山（ Fukuyama ）在《历史的终结》一书中指出： 这个城邦，也像现实中的城邦一样，有外敌，需要抵御外部攻击。因此它需要一个护卫者阶层，勇敢且富于公德心，愿意为公共利益牺牲自己的物质欲望。苏格拉底不相信这样的勇敢和公德精神产生于对开明自利的精明算计。相反，它们必然源自激情（thymos），根植于护卫者阶层对其自身和自己的城邦所抱持的正义感、自豪感之中，以及对那些胆敢威胁到这份骄傲的人所可能产生的非理性的愤怒。 巴拉吉在《网络国家》中的观点，我姑且做出这样的阐释：我们的确需要那些不仅由经济利益，也由道德力量绑定在一起的政治团体，虽然如此，我们却不必将自己束缚在现今任何特定的政治团体上，它们已经漏洞百出，而且越来越无法代表民众的价值观。我们能够、而且应该，创造出新的更好的集体，而巴拉吉的 七步走方略 给出了实现方法。 我们能建设什么样的网络国家？ 巴拉吉提出了关于网络国家的一些设想，我将其精简为两个主要方向：沉浸型的生活方式，和倡导科技的监管创新。 关于沉浸型的生活方式，巴拉吉常用为健康而组建的网络国家为例： 接下来，让我们举个例子：假设有一个网络群岛（拥有物理据点），但尚未成为完全的网络国家（未获得外交承认）——我们叫它 Keto Kosher（无糖社会）。 这得从美国农业部糟糕的食物金字塔说起，这个重谷物的畸形模型，为全球企业高糖化和肥胖症的流行提供了掩护......人们可以组建一个网络社区，在世界各处众筹置产，像是公寓楼、健身房，甚至最后或许是孤街小镇。你没准儿可以实施极端的禁糖措施，完全将加工食品和糖类阻止在边境以外，从而实践某种无糖社会。 你能够想象出这类初创社会的各种不同形态，比如「食肉社区」，或者「史前饮食社区」等。这些都是在同一个大领域内互相竞争的初创社会，在同一个主题下不断迭代。如果成功，这样的一个社会就不会止步于无糖议题。它会开始围绕健身和锻炼设定默认的文化规范。或者，它可能会为社区成员批量采购连续血糖监测仪或订购降血糖药物。 > 严格来说，这些都不需要任何外交承认或者甚至政治自治。然而也许长远来看，这类飞地可能会为其成员展开谋求更低医保费用和医保税的谈判。那么，什么情况下的确需要自治权呢？试想，要设立一个医疗创新自由区会怎么样？ 现在，让我们举一个更难的例子，将会需要一个完整的、获得外交承认的网络国家。那就是医疗主权区——一个没有食品药品监督管理局（FDA）的社会。 亨宁格（ Henninger ）曾阐述过 FDA 所导致的药品延迟上市问题，而塔巴洛克（ keywords: dao; fda; prospera cache: vitalik-networkstates_zhCN.html plain text: vitalik-networkstates_zhCN.txt item: #2399 of 3327 id: vitalik-nonfin author: vitalik title: vitalik-nonfin date: None words: 4358 flesch: 56 summary: Interoperability with other blockchain applications This is an easy one: some things should be on-chain to better interoperate with other on-chain applications. Negative reputation Another important area where off-chain signatures do not suffice is negative reputation - that is, attestations where the person or organization that you're making attestations about might not want you to see them. keywords: blockchain; chain; data; example; key; reputation; use cache: vitalik-nonfin.html plain text: vitalik-nonfin.txt item: #2400 of 3327 id: vitalik-philosophy author: vitalik title: vitalik-philosophy date: None words: 3296 flesch: 57 summary: Invalid chains are rejected by definition, and if there is a choice between multiple valid chains, the chain that has the most support from miners/validators wins out. And so if you have a node that verifies all the validity conditions, and hence detects which chains are valid and which chains are not, that maximizes your chances of correctly detecting what the canonical chain actually is. keywords: attack; block; chain; clients; default cache: vitalik-philosophy.html plain text: vitalik-philosophy.txt item: #2401 of 3327 id: vitalik-plasma_vs_sharding author: vitalik title: vitalik-plasma_vs_sharding date: None words: 1665 flesch: 53 summary: Plasma chains are sidechains that have a non-custodial property: if there is any error in the Plasma chain, then the error can be detected, and users can safely exit the Plasma chain and prevent the attacker from doing any lasting damage. However, designing Plasma chains is in many cases much harder, and one could argue that for many low-value applications the security is not worth the added complexity. keywords: chain; data; plasma cache: vitalik-plasma_vs_sharding.html plain text: vitalik-plasma_vs_sharding.txt item: #2402 of 3327 id: vitalik-plonk author: vitalik title: vitalik-plonk date: None words: 4000 flesch: 60 summary: What this means is that use cases that require different tradeoffs between proof size and security assumptions (or developers that have different ideological positions about this question) can still share the bulk of the same tooling for arithmetization - the process for converting a program into a set of polynomial equations that the polynomial commitments are then used to check. How PLONK works Let us start with an explanation of how PLONK works, in a somewhat abstracted format that focuses on polynomial equations without immediately explaining how those equations are verified. keywords: \cdot; commitments; constraints; equations; polynomial; set cache: vitalik-plonk.html plain text: vitalik-plonk.txt item: #2403 of 3327 id: vitalik-plutocracy author: vitalik title: vitalik-plutocracy date: None words: 2408 flesch: 54 summary: In practice, of course, what this can easily lead to is funds that offer kickbacks to users who vote for them, leading to the exact scenario that we saw above with DPOS delegates. Some have asked: but how can it be wrong for DPOS delegates to bribe voters, when it is perfectly legitimate for mining and stake pools to give 99% of their revenues back to their participants? keywords: community; delegates; dpos; votes; voting cache: vitalik-plutocracy.html plain text: vitalik-plutocracy.txt item: #2404 of 3327 id: vitalik-pos2020 author: vitalik title: vitalik-pos2020 date: None words: 1887 flesch: 66 summary: But conservatively, we can say these ongoing costs are ~10% of the total cost of staking, so we only have $0.90 per day of rewards that end up corresponding to capital costs, so we do need to cut the above figure by ~10%. Total cost of attack: ~$0.26 (assuming 6-hour attack), potentially reduced to zero as the attacker receives block rewards ASIC-based proof of work ASICs are a capital cost: you buy an ASIC once and you can expect it to be useful for ~2 years before it wears out and/or is obsoleted by newer and better hardware. keywords: cost; proof; stake cache: vitalik-pos2020.html plain text: vitalik-pos2020.txt item: #2405 of 3327 id: vitalik-pos2020_zhTW author: vitalik title: vitalik-pos2020_zhTW date: None words: 316 flesch: -211 summary: Dark Mode Toggle 為什麼權益證明棒棒的（2020 年十一月） 2020 Nov 06 See all posts 感謝Chih-Cheng Liang, Hsiao-wei Wang和Jerry Ho翻譯這個文章 權益證明（Proof of Stake, PoS）比工作量證明（Proof of Work, PoW）在區塊鏈安全上更具優勢的關鍵因素有三個。 權益證明在同樣成本下可提供更高的安全性 理解這點最簡單的方式，就是把權益證明和工作量證明擺在一起看，假設每天有 $1 的區塊獎勵，攻擊此網路所需的成本是多少。 基於 GPU 的工作量證明 你可以便宜租到 GPU，所以攻擊網路的成本就等於是租到夠強 GPU 的成本，只要能夠壓過現有礦工 GPU 的算力即可。現有的礦工會花費將近 $1 的成本來賺取 $1 的區塊獎勵（如果他們花費更多，礦工就會因為無利可圖而退出；如果花費比這個數字少，新礦工就會加入來壓縮現有礦工的利潤空間）。因此，攻擊網路只需要暫時花費比 $1/天 多一點點，這還可能只要幾個小時而已。 總攻擊成本： ~$0.26 （假設攻擊 6 小時），且因為攻擊者有機會收到區塊獎勵，所以這個數字可能壓到零 基於 ASIC 的工作量證明 ASICs 其實是資本成本：當買進 ASIC 時你預期大概可以用兩年，因為它會慢慢耗損，或是因為更新更好的硬體出來而過時。如果一個鏈被 51% 攻擊了，社群大概會用更換 PoW 演算法來應對，這時，你的 ASIC 就會失去價值。平均而言，挖礦所費的成本分佈是 1/3 的經常性成本與 2/3 的資本成本（詳見 這裡）。因此，為了每天要賺到 $1 的區塊獎勵，礦工得花 ~$0.33 在電力與維護上，花費 ~$0.67 在 ASIC 上。假設 ASIC 可以用 ~2 年，礦工會需要為一單位的 ASIC 硬體花費 $486.67 。 譯註：$486.67 = 365 天 x 2 年 x $0.67 資本成本 總攻擊成本：$486.67 （ASICs） + $0.08（電力與維護）= $486.75 譯注：這邊電力與維護成本也是假設攻擊 6 小時 值得注意的是，雖然 ASICs 提供了很高的安全性，其（相較 GPU ）付出的代價卻更高，讓環境變得過度的中心化。這同時也讓加入 ASIC 挖礦的門檻變得非常高。 權益證明 Proof of stake 權益證明的成本幾乎全是資本成本（抵押的幣）；唯一的營運成本花在運行節點上。猜猜人們願意為每天 $1 的區塊獎勵鎖住多少的資金呢？不像 ASIC，抵押的幣不會折舊，而且當你不想抵押了，你幾乎馬上就可以取回你的幣。因此，在獎勵相同的情況下，參與者會願意付出比 ASIC 的情況更多的資本成本。 讓我們假設 ~15% 的報酬率足夠吸引人們抵押（這是 eth2 的期望報酬率）。因此每天 $1 的區塊獎勵會吸引相當於 6.667 年報酬的抵押，可換算成 $2,433 。節點消耗的硬體與電力成本很小，一台千元美金等級的電腦就可以抵押非常大量的幣，而且每月只要花大概 ~$100 左右的電力與網路費就綽綽有餘。我們可以保守的假設上述這些經常性成本為抵押總成本的 10% ，這代表在協議每天發出的區塊獎勵中，需要扣掉 10% 的經常性成本，剩下的 $0.90 才是（攻擊時）需要花費的資本成本。 譯註： 6.667 年 = $1 /（15% 年報酬）； $2,433 = $1 每天 x 365 x 6.667 總攻擊成本： $0.90/天 * 6.667 年 = $2,189 長期來說，這個攻擊成本會變得更高，因為抵押會變得更有效率，人們也因而更能接受較低的報酬率。我個人預期這個數字最終會攀升到 $10,000 左右。 值得注意的是，如此高的安全性帶來的「代價」，只是讓你在抵押時無法任意移動資金而已。人們有可能認知到，這些幣被鎖住之後反而造成了幣的價值攀升，因而造成在社群流通的貨幣總數、像是用於投資生產活動的資金，反而會維持不變。反觀 PoW，維持共識的「代價」卻是瘋狂地損耗電力。 我們想要更高的安全性，還是更低的成本？ 要知道的是，在每單位成本安全性增加了 5-20 倍之後，我們有兩種方式可以將其加以利用。一種方式是區塊獎勵維持現狀，單純享受多出的安全性。另一種方式是維持現有程度的安全性，並大量減少區塊獎勵（也就是減少共識機制成本的「浪費」）。 兩種方式都行。我個人喜歡後者，因為我們在下文會看到，跟工作量證明相比，在權益證明中的成功攻擊會造成更少的傷害，而且鏈更容易從攻擊中復原。 權益證明更容易從攻擊中復原 在工作量證明的系統，如果你的鏈遭受 51% 攻擊，你會怎麼做？目前為止，實務上唯一的應對一直是「慢慢等，直到攻擊者覺得無聊了」。但這忽略了一種更危險的攻擊叫做「住到你崩潰(spawn camping attack)」，攻擊者可以對鏈攻擊再攻擊，明確的目標就是要讓鏈無法再使用。 譯注：Spawn Camping 是一種遊戲術語，指在對方玩家重生點或死亡處埋伏的行為。如此會造成被住、被蹲的玩家一復活就再次陣亡，毫無還手之力。 基於 GPU 的系統完全沒有防禦的辦法，而且持續攻擊的攻擊者可以輕易讓一個鏈永遠毫無用處（實務上來說，該鏈會開始轉移到權益證明或權威證明(proof of authority)）。事實上，在攻擊開始後不久，攻擊者的成本就會變得非常低，而誠實礦工會離開，因為他們沒辦法在攻擊持續之下取得區塊獎勵。 在基於 ASIC 的系統，社群有辦法應對第一波攻擊，但接下來的攻擊就會變得很容易。社群可以在第一波攻擊之後，硬分叉來更換工作量證明的演算法，讓所有 ASIC 「變磚」（攻擊者和誠實礦工的 ASIC 會一起磚掉）。如果攻擊者願意承受第一次 ASIC 變磚的成本，接下來幾次的情況就和 GPU 的情況一樣（因為還沒有足夠的時間去為新演算法打造與生產 ASIC），所以在這之後攻擊者可以很便宜地持續對鏈發動攻擊到天荒地老。 譯註：變磚為電子產品俚語，代表損壞後無法使用，像磚頭一樣 在權益證明下，狀況則好上非常多。。針對特定種類的 51% 攻擊（特別指想要推翻已經敲定的區塊），權益證明共識有內建的「砍押金（slashing）」機制，大比例的攻擊者抵押會被自動銷毀（而且不會銷毀到其他人的抵押）。針對其他種類的，更難偵測的攻擊（像是 51% 合謀截斷其他人訊息），社群可以協調一個「少數使用者發起軟分叉 minority user-activated soft fork (UASF)」，可以大量銷毀攻擊者的資金（在以太坊中，可以透過「離線懲罰 inactivity leak 」做到）。如此就不需特別花心力來「搞個硬分叉砍掉非法貨幣」。除了 UASF 需要人為協調要選擇哪個少數區塊，其餘的事情都是自動化的，只要遵照協定規則去執行即可。 譯註：少數區塊 minority block 是小於 51% 抵押總數的驗證者決定出來的區塊。 因此，對鏈的第一次攻擊就會耗損攻擊者幾百萬美元，而且社群可以幾天內馬上站穩腳步。第二次攻擊仍然會花費攻擊者數百萬美元，因為他們被迫要買新的幣來取代自己被燒毀的幣。再攻擊第三次...只會繼續燒更多錢。。局面極為不對稱，而且優勢並不會在攻擊者那邊。 權益證明比 ASIC 更去中心化 基於 GPU 的工作量證明的去中心化程度還不錯，因為取得 GPU 不會太難。但前面提過，基於 GPU 的挖礦難以滿足「在攻擊之下的安全性」這個準則。另一方面，基於 ASIC 的挖礦，則需要數百萬美元的資本才能做（而且如果你的 ASIC 是買來的，多數時候，製造商會佔更多便宜） 如上述，你現在知道要怎麼回答「 PoS 只會讓有幣的人繼續以錢滾錢」這個論點了： ASIC 挖礦一樣會讓已經有幣的人得利 - 而且賺得比 PoS 的時候還多。相比之下，至少權益證明的最低抵押門檻夠低，讓一般人還能有機會接觸。 譯註：就文章完成當下 32 ETH @ 440 USD ，最低抵押門檻大概是 40 萬台幣。 進一步說，權益證明更能抵抗審查。GPU 挖礦和 ASIC 挖礦很容易被偵測，他們需要大量電力消耗、昂貴硬體採購、及大型廠房。另一方面，權益證明可以跑在一台不起眼的筆電上，就算跑在 VPN 上也毫無問題。 工作量證明可能的優勢 我覺得 PoW 在下述這兩點上是真的比較佔優勢，縱然這些優勢相當有限。 權益證明更像個「封閉系統」，長期而言財富更加集中 在權益證明的情況下，如果你手上有幣，你可以抵押手上的幣來獲得更多同種類的幣。但，在工作量證明的情況下，就算你沒有幣你還是能賺到，只要你願意投入一些外部資源。因此，或許可以說權益證明會造成長期風險，讓幣的分配變得越來越集中。 我的回應是，在 PoS 中，報酬一般而言會很低（所以驗證者的獲利也會低）。在 eth2 ，我們預期驗證者的年報酬會相當於總 ETH 供給量的 ~0.5-2%。而且更多驗證者抵押，利率會更低。因此，可能要花個一世紀，整個資產集中程度才會翻倍，而且在這樣的時間跨度之下，其他促進分配的壓力（人們想花他們手上的錢，分配金錢到慈善或他們自己的子孫等等）比較可能會佔上風。 權益證明需要「弱主觀性（weak subjectivity）」而工作量證明不需要 關於「弱主觀性」的觀念可以看這個 原始介紹。本質上，就是節點在第一次上線，或是在離線很長一段時間之後（數個月）再次上線，這個節點必須要透過第三方的資源，才能決定正確的鏈頭在哪。這個第三方可以是他們的朋友、可以是交易所或區塊鏈瀏覽器網站、或是客戶端開發者本身、又或是其他角色。PoW 則沒有這樣的要求。 然而，這可能是一個很弱的要求。事實上，使用者本身就已經必須對客戶端開發者、或「社群」有這種程度的信任。最起碼，使用者必須信任某個人（通常是客戶端開發者）來告訴他們協定是什麼，這個協定曾經經歷過什麼樣的更新。這在任何軟體應用都無法避免。因此，這個 PoS 所需要增加的額外信任，其實已經算很少了。 但就算事實證明這些風險其實一點都不小，在我看來切換到 PoS 系統帶來的好處要高得多，像是系統運作的高效率和從攻擊中回歸正軌的能力。 參考來源：我之前寫權益證明的文章 英：Proof of Stake FAQ 英 A Proof of Stake Design Philosophy 中 一种权益证明设计哲学 keywords: asic; gpu; pos cache: vitalik-pos2020_zhTW.html plain text: vitalik-pos2020_zhTW.txt item: #2406 of 3327 id: vitalik-pos_design author: vitalik title: vitalik-pos_design date: None words: 1835 flesch: 48 summary: Consensus protocols that work as-fast-as-possible have risks and should be approached very carefully if at all, because if the possibility to be very fast is tied to incentives to do so, the combination will reward very high and systemic-risk-inducing levels of network-level centralization (eg. Consensus protocols that don't care too much how fast a validator sends a message, as long as they do so within some acceptably long time interval (eg. 4–8 seconds, as we empirically know that latency in ethereum is usually ~500ms-1s) do not have these concerns. keywords: attack; consensus; cost; proof cache: vitalik-pos_design.html plain text: vitalik-pos_design.txt item: #2407 of 3327 id: vitalik-pos_design_TR author: vitalik title: vitalik-pos_design_TR date: None words: 1432 flesch: 49 summary: bir dereceye kadar bunun bir uzantısıdır, ancak bu sefer sadece özel iletilerin bütünlüğü ve gizliliği değil, karmaşık koordinasyon ve işbirliği sistemlerinin güvenliği ve canlılığını koruması gerekir. Casper konsensüsünün de felsefi bir temeli var, ancak bu şimdiye kadar açık bir şekilde makaleye alınmamıştır. keywords: ancak; bir; blok; büyük; daha; ekonomik; fork; için; kadar; konsensüs; olan; olarak; proof; protokol; sosyal; temel; veya; çok cache: vitalik-pos_design_TR.html plain text: vitalik-pos_design_TR.txt item: #2408 of 3327 id: vitalik-pos_faq author: vitalik title: vitalik-pos_faq date: None words: 8552 flesch: 54 summary: One strategy suggested by Vlad Zamfir is to only partially destroy deposits of validators that get slashed, setting the percentage destroyed to be proportional to the percentage of other validators that have been slashed recently. This makes lower-security staking strategies possible, and also specifically incentivizes validators to have their errors be as uncorrelated (or ideally, anti-correlated) with other validators as possible; this involves not being in the largest pool, putting one's node on the largest virtual private server provider and even using secondary software implementations, all of which increase decentralization. keywords: algorithms; block; chain; consensus; network; proof; stake; time; validators; work cache: vitalik-pos_faq.html plain text: vitalik-pos_faq.txt item: #2409 of 3327 id: vitalik-prehistory author: vitalik title: vitalik-prehistory date: None words: 3172 flesch: 51 summary: This meant that transactions could not use internal transactions as a way of getting information from other contracts; the only way to do that was the EXTRO opcode (kind of like an SLOAD that you could use to read other contracts' storage), and this too was later removed with the support of Gavin and others. The next idea that we went through is adaptive proof of work; here, the proof of work would involve executing randomly selected Ethereum contracts, and there is a clever reason why this is expected to be ASIC-resistant: if an ASIC was developed, competing miners would have the incentive to create and publish many contracts that that ASIC was not good at executing. keywords: contracts; ethereum; gas; gavin; protocol; time; transaction cache: vitalik-prehistory.html plain text: vitalik-prehistory.txt item: #2410 of 3327 id: vitalik-prices author: vitalik title: vitalik-prices date: None words: 2794 flesch: 67 summary: Selling at below market price is hardly a new phenomenon, both within the blockchain space and outside, and over the decades there have been many articles and papers and podcasts writing (and sometimes bitterly complaining) about the unwillingness to use auctions or set prices to market-clearing levels. Selling at below market-clearing prices has large inefficiencies and negative externalities If a seller sells an item at market price, or through an auction, someone who really really wants that item has a simple path to getting it: they can pay the high price or if it's an auction they can bid a high amount. keywords: auction; item; market; people; price cache: vitalik-prices.html plain text: vitalik-prices.txt item: #2411 of 3327 id: vitalik-progress author: vitalik title: vitalik-progress date: None words: 5179 flesch: 50 summary: Dark Mode Toggle Hard Problems in Cryptocurrency: Five Years Later 2019 Nov 22 See all posts Special thanks to Justin Drake and Jinglan Wang for feedback In 2014, I made a post and a presentation with a list of hard problems in math, computer science and economics that I thought were important for the cryptocurrency space (as I then called it) to be able to reach maturity. At the end, I'll include my new picks for hard problems of 2019. keywords: blockchain; problem; program; progress; proof; status; system; time; work cache: vitalik-progress.html plain text: vitalik-progress.txt item: #2412 of 3327 id: vitalik-proof_of_solvency author: vitalik title: vitalik-proof_of_solvency date: None words: 3494 flesch: 64 summary: In the long-term future, this can hopefully be fixed with technological upgrades and standardization; in the short term, however, it's another argument in favor of custodial exchanges remaining custodial for now. Conclusions: the future of better exchanges In the short term, there are two clear classes of exchanges: custodial exchanges and non-custodial exchanges. Both types of exchanges will continue to exist, and the easiest backwards-compatible way to improve the safety of custodial exchanges is to add proof of reserve. keywords: balance; exchange; merkle; proof; tree; user cache: vitalik-proof_of_solvency.html plain text: vitalik-proof_of_solvency.txt item: #2413 of 3327 id: vitalik-qap author: vitalik title: vitalik-qap date: None words: 3179 flesch: 68 summary: The purpose of this post is not to serve as a full introduction to zk-SNARKs; it assumes as background knowledge that (i) you know what zk-SNARKs are and what they do, and (ii) know enough math to be able to reason about things like polynomials (if the statement \(P(x) + Q(x) = (P + Q)(x)\) , where \(P\) and \(Q\) are polynomials, seems natural and obvious to you, then you're at the right level). keywords: \cdot; polynomial cache: vitalik-qap.html plain text: vitalik-qap.txt item: #2414 of 3327 id: vitalik-quadratic author: vitalik title: vitalik-quadratic date: None words: 4685 flesch: 60 summary: Quadratic Voting See also the original paper: https://papers.ssrn.com/sol3/papers.cfm?abstract%5fid=2003531 Let us begin by exploring the first flavor of quadratic payments: quadratic voting. These ideas have been gaining popularity rapidly over the last few years, and small-scale tests have already been deployed: the Taiwanese presidential hackathon used quadratic voting to vote on winning projects, Gitcoin Grants used quadratic funding to fund public goods in the Ethereum ecosystem, and the Colorado Democratic party also experimented with quadratic voting to determine their party platform. keywords: article; cost; goods; people; quadratic; vote; voting cache: vitalik-quadratic.html plain text: vitalik-quadratic.txt item: #2415 of 3327 id: vitalik-radical_markets author: vitalik title: vitalik-radical_markets date: None words: 5377 flesch: 48 summary: One argument is that, as Steve Waldman says, Uber itself is a cartel, and wants to have the power to adjust market prices not just for efficiency but also reasons such as profit maximization, strategically setting prices to drive out competing platforms (and taxis and public transit), and public relations. One of the more interesting ideas from the 19th century economists, and specifically Henry George, was a kind of property tax that did not have this problem: the land value tax. keywords: book; markets; people; posner; price; property; tax; value; weyl cache: vitalik-radical_markets.html plain text: vitalik-radical_markets.txt item: #2416 of 3327 id: vitalik-recovery author: vitalik title: vitalik-recovery date: None words: 3691 flesch: 57 summary: This post will go through what social recovery wallets are, why they matter, and how we can and should move toward much broader adoption of them throughout the ecosystem. The three most common choices are: Other devices (or paper mnemonics) owned by the wallet holder themselves Friends and family members Institutions, which would sign a recovery message if they get a confirmation of your phone number or email or perhaps in high value cases verify you personally by video call Guardians are easy to add: you can add a guardian simply by typing in their ENS name or ETH address, though most social recovery wallets will require the guardian to sign a transaction in the recovery webpage to agree to be added. keywords: funds; guardians; hardware; recovery; transaction; wallet cache: vitalik-recovery.html plain text: vitalik-recovery.txt item: #2417 of 3327 id: vitalik-retro1 author: vitalik title: vitalik-retro1 date: None words: 4406 flesch: 59 summary: In the context of Optimism retro funding specifically, the main specific argument I heard against secret voting is that it would make it harder for badge holders to rally and vote against other badge holders making votes that are clearly very wrong or even malicious. In this round, badge holder votes were completely transparent; anyone can see how each badge holder votes. keywords: badge; funding; holders; projects; retro; round; vote cache: vitalik-retro1.html plain text: vitalik-retro1.txt item: #2418 of 3327 id: vitalik-revenue_evil author: vitalik title: vitalik-revenue_evil date: None words: 2864 flesch: 57 summary: Dark Mode Toggle The Revenue-Evil Curve: a different way to think about prioritizing public goods funding 2022 Oct 28 See all posts Special thanks to Karl Floersch, Hasu and Tina Zhen for feedback and review. But nevertheless, the goal is to highlight that there is a tragic aspect to many monetization schemes, and public goods funding can provide value by giving existing projects a financial cushion that enables them to avoid such sacrifices. keywords: curve; evil; goods; public; revenue cache: vitalik-revenue_evil.html plain text: vitalik-revenue_evil.txt item: #2419 of 3327 id: vitalik-revenue_evil_zhCN author: vitalik title: vitalik-revenue_evil_zhCN date: None words: 172 flesch: -65 summary: Dark Mode Toggle 收入-邪恶曲线：思考“公共物品融资优先”的另一种方式 2022 Oct 28 See all posts 译者：龙犄角 & 审阅：Carol @ GreenPill CN 原文：../../../2022/10/28/revenue_evil.html 特别感谢 Karl Floersch、Hasu 和 Tina Zhen 对本篇内容的反馈与评论。 在任何大规模的生态中，公共物品都是无比重要的主题。但同时，公共物品也令人惊讶地难以定义。经济学家对公共物品是这样定义的：公共物品是那些非排他也非竞争性的物品。非排他和非竞争两个经济学专业术语合在一起的表述，意味着从私人财产和市场的角度来提供公共物品是十分困难的。门外汉们对于公共物品也有一个定义：一切对公共有益处的事物都是公共物品。同时，民主人士对公共物品也提出了一个定义，为之添加了公众参与决策的含义。 然而，更重要的是，当抽象的非排他性非竞争性公共物品在与真实的世界互动时，几乎每一个具体的例子都包含无数微妙的边缘案例，需要因地制宜、具体案例具体分析。例如，一座公园是一个公共物品。但假如你对每个进入公园的人都收取 5 美金的门票钱呢？要是你通过拍卖在公园中心广场上树立价高者雕像的权力来为其募资呢？再或者这座公园是由一名半利他主义的亿万富丰出资建造、修葺、维护的，她享受这座公园作为她的个人用途、她将这座公园设计成自己喜欢的模样，但同时又允许任何路过的人踏进公园小坐一会儿、抑或和友人并肩散步谈天呢？ 这篇内容将尝试为落在私人-公共这条光谱上的混合物品进行分析提供另一个角度，也就是****收入-邪恶曲线****。我们抛出这样一个问题：不同方式的货币化项目的权衡是什么，以及通过增加外部补贴来消除货币化的压力可以做多少好事？这远不同于一个普世的框架：它假定在一个单一的社区中存在混合经济环境，有一个商业市场和一个中央资助者的补贴。但它仍旧能够在如何在如今的加密社区、加密国家和许多其他现实世界背景下为公共产品提供资金这方面教会我们很多道理。 传统框架：排他性和竞争性 让我们先从这里理解这个问题开始：通常的经济学家是如何看待一个项目是否属于私人物品或是公共物品的？考虑下面的例子： Alice 持有 1000 以太，想要在市场上抛售。 Bob 经营一家航空公司，出售航班机票。 Charlie 建了一座桥，并通过收取过路费来支付这座桥的修建费用。 David 制作并发布了一档播客。 Eve 制作并出了一首歌。 Fred 发明了一种新的、更好的加密算法，用于进行零知识证明。 接下来，我们将这些案例放进一个有两条坐标轴的图表： 竞争性：一个人享受了美好事物的时候，她会在多大程度上降低另一个人享受美好事物的能力？ 排他性：阻止特定的人——例如那些不付钱的人——享受美好的事物，有多难？ 一张类似的图表大概长这样： 艾莉丝持有的以太是完全排他的（她对谁可以得到她的以太有完全的掌控和选择权），而加密货币是竞争性的（如果一个人拥有一个特定的硬币，其他人就不会拥有同样的硬币）。 鲍勃的飞机票是具有排他性的，但有一点没那么具有竞争性：很可能飞机没有满座。 查理的桥比起鲍勃的飞机票更少了一点排他性，因为增加一道关卡来验证缴费情况需要额外的工作（所以查理可以排他，但对他和过路的人来说都是昂贵的），且桥的竞争性取决于道路是否拥堵。 戴卫的播客和尹芙的歌不具有竞争性：一个人听播客或者那首歌并不妨碍另一个人做同样的事情。它们倒有一点排他性，因为戴卫和尹芙可以做一个付费墙，不过人们同样可以绕过付费墙。 最后，福拉德发明的加密算法接近于完全没有排他性：算法需要开源，人们才会信任它。如果福拉德试图为算法申请专利，目标用户群（热爱开源的加密用户）很可能拒绝使用该算法，甚至为此取消他的资格。 以上都是很好也很重要的分析。排他性告诉我们你是否能够通过收费作为一种商业模式来资助这个项目，而竞争性则告诉我们排他性是否是一种悲剧性的浪费。或者说，这是否只是有关物品的一个不可避免的属性，即如果一个人得到了它，另一个人就得不到。但如果我们仔细地思考其中的一些例子，尤其是数字相关的例子，我们可以发现，这其中忽略了一个非常重要的问题：除了排他性之外，还有很多商业模式可供选择，这些商业模式也有取舍。 思考这样一个特殊的案例：戴卫的播客和尹芙的歌。在现实中，大量的播客是基本或完全免费发布的，但歌曲更多是以许可和版权限制为门槛。要知道个中原因，我们只需要明白这些播客是如何得到资助的：赞助。播客主持人通常寻找几个赞助人，并在每一集播客的开始或中间简短地为赞助人打一打广告。但赞助歌曲更难：你不能在唱一首缱绻的情歌时突兀地中途停下来并开始讲起 Athletic Greens* 如何如何棒呆。因为，你可拉倒吧，气氛都让你给搅合没了啊兄弟！ 我们是否能够越过仅仅考虑排他性，去更广泛地讨论货币化和不同货币化策略的危害呢？实际上，我们的确可以，而这也恰恰是收入/邪恶曲线的用处。 收入-邪恶曲线的定义 一件产品的收入-邪恶曲线是一条二维曲线，能够画出以下问题的答案： 该产品的创造者要对她们的潜在用户和更广泛的社区造成多大的伤害，才能赚取 N 美金的收入来支付产品的建设费用？ 在这里用邪恶这个词并不是说任何数量的邪恶都不被接受，也不是说如果你不能保证不作恶，你就根本不应该去资助项目。许多项目为了确保可持续的资金，做出了艰难的取舍，伤害了她们的客户和社区，而且往往项目存在的价值大大超过了这些伤害。但尽管如此，我们的目标是强调许多货币化计划有其悲剧性的一面，而公共物品融资可以提供价值，给现有项目一个财政缓冲，使她们能够避免这种牺牲。 下图是先前 6 个例子的收入-邪恶曲线的粗略绘制： 对于 Alice 来说，以市场价格出售她的以太实际上是她能做的最有同情心的事情。如果她卖得更便宜，她几乎一定会造成链上 gas 战争、交易员 HFT 战争或其他类似的价值破坏性金融冲突，因为每个人都想最快地得到她的币。而高于市场价格出售甚至不足以成为一种选择：没有人会买。 对于 Bob 来说，社会最优的售价是所有机票都能卖完的最高价格。如果 Bob 以低于这个价格的票价出售机票，那么票很快就会卖完，一些真正需要这些机票的人根本无法买到座位（定价过低可能会给穷人带来一些相反的好处，但也远远不是实现这一目标的最有效方式）。Bob 也可以高于市场价格出售，并有可能赚取更高的利润，但代价是卖出更少的座位，而且（从上帝的角度来看）不必要地把人排除在外了。 如果 Charlie 的桥和通往该桥的道路不拥堵，收取任何费用都是一种负担，并不必要地将司机排除在外。如果它们是拥堵的，低收费有助于减少拥堵，而高收费则不必要地将人们排除在外。 David 的播客可以通过增加赞助商的广告而在一定程度上实现货币化，同时也不会对听众造成很大伤害。如果货币化的压力增加，David 将不得不采用越来越多的广告形式，而真正的收入最大化将需要对播客进行付费墙屏蔽，这对潜在的听众来说是一种高成本。 Eve 的处境和 David 差不多，但低伤害的选择较少（也许是卖 NFT？） 。特别是在卖歌的情况下，付费墙很可能需要积极参与版权执法和起诉侵权者的法律机制，这带来了进一步的伤害。 Fred 的货币化选择甚至更少。他可以为它申请专利，或者有可能采取一些怪异的举动，例如拍卖选择参数的权利，让那些喜欢特定价值的硬件制造商来竞标。但所有的选择都是高成本的。 从这里我们可以看到，在收入-邪恶曲线上实际有许多种邪恶。 传统的排他性经济损失：如果一个产品的价格高于边际成本，本可以进行的互利交易就不会发生。 竞争条件：拥挤、短缺和因为产品太便宜而产生的其他成本。 污染产品，使其对赞助商有吸引力，但对听众有一定程度的伤害（伤害或大或小）。 通过法律系统从事攻击性行动，这增加了每个人的恐惧和花钱请律师的需要，并产生各种难以预测的次生寒蝉效应。这种情况在专利方面尤为严重。 在用户、社区，甚至是从事项目本身的人高度重视的原则上做出牺牲。 在许多案例中，这种邪恶非常依赖于背景。在加密领域和更广泛的软件领域，专利权既极为有害，又具有意识形态上的攻击性，但在制造实物商品的行业中，这种情况较少：在有形商品行业中，大多数人在现实中能够创造出某种专利的衍生作品，她们的规模和组织程度足以谈判获得许可，而资本成本意味着对货币化的需求要高得多，因此保持纯粹性就更难。广告多么有害取决于广告商和受众：如果播客主持人非常了解她的听众，广告甚至可以是有帮助的！是否存在排他的可能性甚至取决于产权。 但通过笼统地谈论为赚取收入而作恶这个话题，我们获得了将这些情况相互比较的能力。 收入-邪恶曲线在如何确定融资的优先次序上告诉了我们什么？ 现在，回到我们为什么关心什么是公共物品、什么不是公共物品的关键问题：融资的优先次序。如果我们有一个有限的资本池，专门用于帮助一个社区的繁荣，我们应该把资金用于哪些方面？收入-邪恶曲线图为我们提供了回答这个问题的一个简单的起点：将资金投向那些收入-邪恶曲线斜率最大的项目。 我们应该把重点放在那些通过减少货币化的压力，每 1 美金的补贴都能最大幅度地减少不幸的项目所需的罪恶的项目上。这样我们就得到了如下的大致排名： 最优先的是 纯粹的公共物品，因为往往根本没有任何方法可以将其货币化，或者即使有，试图货币化的经济或道德成本也非常高。 第二个优先事项是 自然而然公共但可盈利的物品，通过稍加调整就可以通过商业渠道获得资金，如歌曲或对播客的赞助。 第三优先考虑的是非商品类私人物品，在这些物品中，社会福利已经通过收费得到优化，但利润率很高，或者更普遍的是存在污染产品以增加收入的机会。例如，通过保持伴随的软件闭源或拒绝使用标准，补贴可以用来推动这些项目在边际上做出更亲社会的选择。 需要注意的是，排他性和竞争性框架通常会得出类似的答案：首先关注非排他性和非竞争性的物品，其次关注具有排他性但非竞争性的物品，最后关注具有排他性和部分竞争性的物品——而既具有排他性又具有竞争性的物品永远不会被关注（如果你有剩余的资本，最好直接作为 UBI 发放）。收入/邪恶曲线与排他性和竞争性之间有一个粗略的近似映射：排他性越高意味着收入/邪恶曲线的斜率越低，而竞争性则告诉我们收入/邪恶曲线的底部是零还是非零。但收入/邪恶曲线是一个更普遍的工具，它允许我们谈论货币化战略的权衡，远远超出了排他。 这个框架如何用于分析决策的一个实例是 Wikimedia 捐款。我个人从未向 Wikimedia 捐款，因为我一直认为她们能够也应该不依靠有限的公益资金来资助自己，只需增加一些广告。而这对她们的用户体验和中立性来说只是一个很小的代价。然而，维基百科的管理员不同意；她们甚至有一个维基页面列出了她们不同意的论据。 我们可以把这种分歧理解为对收入-邪恶曲线的争议：我认为 Wikimedia 的收入-邪恶曲线的斜率很低（广告并不那么糟糕），因此她们对我的慈善资金来说是低优先级的；其他一些人认为她们的收入-邪恶曲线的斜率很高，因此她们的慈善资金对 Wikimedia 是高度优先的。 收入-邪恶曲线是一个智力工具，而「不是」一个好的直接机制 从这个想法中得出的一个重要结论是，我们不应该尝试直接使用收入-邪恶曲线作为确定单个项目优先次序的方法。由于监测方面的限制，我们在这方面的能力受到了严重制约。 如果这个框架被广泛使用，项目就会有动力去虚报她们的收入-邪恶曲线。任何收取通行费的人都有动力想出巧妙的论据，试图说明如果通行费能降低 20%，世界就会好得多，但由于她们的预算严重不足，没有补贴她们就无法降低通行费。项目将有动力在短期内更加邪恶，以吸引补贴，帮助她们变得不那么邪恶。 由于这些原因，最好的办法可能是不把该框架作为直接分配决策的方式，而是确定哪些类型的项目应优先获得资金的一般原则。例如，该框架可以成为确定如何对整个行业或整个类别的物品进行优先排序的有效方式。它可以帮助你回答这样的问题：如果一家公司正在生产一种公共物品，或者在设计一种不完全是公共物品的物品的过程中做出了有利于社会但经济成本很高的选择，她们是否应该为此获得补贴？但即使是这样，最好也是把收入-邪恶曲线当作一种心理工具，而不是试图精确地测量它们，并利用它们来作出单独的决定。 结论 排他性和竞争性对一个物品来说是重要的维度，对其货币化的能力，以及对回答通过一些公共资金获得资助，可以避免多少伤害的问题，具有真正重要的影响。但是，特别是一旦更复杂的项目进场，这两个维度很快就开始变得不足以决定资金的优先次序。大多数的物品都不是纯粹的公共物品：它们是处于中间的一些混合体，在许多方面，它们或多或少都是公共的，且不容易映射到排他。 观察一个项目的收入-邪恶曲线给了我们另一种衡量真正重要的统计数据的方法：减轻一个项目 1 美金的货币化压力，可以避免多少伤害？有时，缓解货币化压力的收益是决定性的：就是没有办法通过商业渠道来资助某些种类的东西，直到你能找到一个从它们中受益的单一用户，足以单方面资助它们。其他时候，商业资金的选择是存在的，但有着有害的副作用。有时这些影响较小，有时较大。有时，个人项目的一小部分在亲社会的选择和增加货币化之间有明显的权衡。还有一些时候，项目只是自己筹资，没有必要对其进行补贴——或者，至少不确定性和隐藏的信息使得创建一个利大于弊的补贴时间表太难。按照从最大收益到最小收益的顺序排列资金的优先次序总是更好的；而你能走多远取决于你有多少资金。 * 我没有接受Athletic Greens的赞助费用。但播客主持人 Lex Fridman 接受了。以及，我也没有接受 Lex Fridman 的赞助费用。但也许有人接受了。反正管他呢，只要我们能继续为播客提供资金，让人们能免费收听，又不至于太烦，那一切就都很好了，对吧？ keywords: wikimedia cache: vitalik-revenue_evil_zhCN.html plain text: vitalik-revenue_evil_zhCN.txt item: #2420 of 3327 id: vitalik-road author: vitalik title: vitalik-road date: None words: 3167 flesch: 63 summary: In some cases, Ethereum developers made conscious decisions to improve in some place where we thought that Bitcoin erred. 75% of the premine went to rewarding contributors for their work before launch, and post-launch the Ethereum Foundation only had 3 million ETH left. keywords: block; ethereum; evm; lot; proof; stake cache: vitalik-road.html plain text: vitalik-road.txt item: #2421 of 3327 id: vitalik-rollup author: vitalik title: vitalik-rollup date: None words: 4638 flesch: 61 summary: In general, my own view is that in the short term, optimistic rollups are likely to win out for general-purpose EVM computation and ZK rollups are likely to win out for simple payments, exchange and other application-specific use cases, but in the medium to long term ZK rollups will win out in all use cases as ZK-SNARK technology improves. ZK rollups, which use validity proofs: every batch includes a cryptographic proof called a ZK-SNARK (eg. using the PLONK protocol), which proves that the post-state root is the correct result of executing the batch. keywords: batch; chain; data; rollups; root; state cache: vitalik-rollup.html plain text: vitalik-rollup.txt item: #2422 of 3327 id: vitalik-rollup_ES author: vitalik title: vitalik-rollup_ES date: None words: 4996 flesch: 54 summary: Incluso los sistemas en los que se puede cambiar el estado de un objeto sin el consentimiento del propietario (por ejemplo: los sistemas basados en cuentas, en los que puede aumentar el saldo de alguien sin su consentimiento) no funcionan bien con Plasma. El ~0.5 en la tabla representa el hecho de que existe un límite en la cantidad de firmas que se pueden combinar en un agregado que se puede verificar en un solo bloque, por lo que los batches grandes necesitarían una firma por cada ~100 transacciones. keywords: batch; bob; bytes; cada; cadena; con; contrato; datos; del; ejemplo; estado; esto; hay; las; los; más; para; pero; plasma; por; prueba; puede; que; rollups; root; solo; son; transacción; una cache: vitalik-rollup_ES.html plain text: vitalik-rollup_ES.txt item: #2423 of 3327 id: vitalik-round4 author: vitalik title: vitalik-round4 date: None words: 3069 flesch: 50 summary: But there is nothing in the rules of quadratic funding that privileges Ethereum projects and prevents, say, Ethereum Classic projects from seeking funding using the same platform! Dark Mode Toggle Review of Gitcoin Quadratic Funding Round 4 2020 Jan 28 See all posts Round 4 of Gitcoin Grants quadratic funding has just completed, and here are the results: The main distinction between round 3 and round 4 was that while round 3 had only one category, with mostly tech projects and a few outliers such as EthHub, in round 4 there were two separate categories, one with a $125,000 matching pool for tech projects, and the other with a $75,000 matching pool for media projects. keywords: community; ethereum; funding; good; public; round cache: vitalik-round4.html plain text: vitalik-round4.txt item: #2424 of 3327 id: vitalik-round5 author: vitalik title: vitalik-round5 date: None words: 2784 flesch: 55 summary: But as with recurring contributions, very few people made negative contributions, to the point where their impact on the results was negligible. People would be willing to give more recurring contributions, but there is some kind of market failure stopping them; that is, it's collectively optimal for everyone to give more recurring contributions, but it's not any individual contributor's interest to be the first to do so. keywords: contributions; people; projects; round cache: vitalik-round5.html plain text: vitalik-round5.txt item: #2425 of 3327 id: vitalik-round6 author: vitalik title: vitalik-round6 date: None words: 1902 flesch: 55 summary: Since round 5, Gitcoin Grants has had three categories per round: tech, community (called media before), and some guest category that appears only during that specific round. In round 5 this was COVID relief; in round 6, it's Crypto For Black Lives. keywords: community; ethereum; funding; round cache: vitalik-round6.html plain text: vitalik-round6.txt item: #2426 of 3327 id: vitalik-round7 author: vitalik title: vitalik-round7 date: None words: 1674 flesch: 54 summary: People are naturally altruistic to some extent, and this round defi projects got unexpectedly wealthy for the first time due to a rapid rise in interest and token prices, and so donating some of that windfall felt like a natural good thing to do Many in the community are critical of defi projects by default, viewing them as unproductive casinos that create a negative image of what Ethereum is supposed to be about. Contributing to public goods is an easy way for a defi project to show that they want to be a positive contributor to the ecosystem and make it better Even in the absence of such negative perceptions, defi is a competitive market that is heavily dependent on community support and network effects, and so it's very valuable to a project to win friends in the ecosystem The largest defi projects capture enough of the benefit from these public goods that it's in their own interest to contribute There's a high degree of common-ownership between defi projects (holders of one token also hold other tokens and hold ETH), and so even if it's not strictly in a project's interest to donate a large amount, token holders of that project push the project to contribute because they as holders benefit from the gains to both that project but also to the other projects whose tokens they hold. keywords: defi; matching; projects; round cache: vitalik-round7.html plain text: vitalik-round7.txt item: #2427 of 3327 id: vitalik-round7_FR author: vitalik title: vitalik-round7_FR date: None words: 1725 flesch: 56 summary: Du côté de l'infrastructure, le projet White Hat Hacking (essentiellement un fonds de don à samczsun) a reçu un total de 39.258 $ et le Bankless podcast a obtenu 47.620 $. Chainlink, un projet keywords: des; est; les; nous; plus; pour; projets; que; tour; une cache: vitalik-round7_FR.html plain text: vitalik-round7_FR.txt item: #2428 of 3327 id: vitalik-round9 author: vitalik title: vitalik-round9 date: None words: 2913 flesch: 55 summary: Churn continues to be healthy One long-time concern with Gitcoin Grants is the balance between stability and entrenchment: if each project's match award changes too much from round to round, then it's hard for teams to rely on Gitcoin Grants for funding, and if the match awards change too little, it's hard for new projects to get included. As Gitcoin Grants continues to establish itself as a successful home for Ethereum public goods funding, it is also continuing to attract legitimacy as a focal point for donations from projects wishing to support the ecosystem. keywords: gitcoin; mechanism; projects; round; team cache: vitalik-round9.html plain text: vitalik-round9.txt item: #2429 of 3327 id: vitalik-sales author: vitalik title: vitalik-sales date: None words: 4130 flesch: 61 summary: Note that there are other mechanisms that should be tried to solve other problems with token sales; for example, revenues going into a multisig of curators, which only hand out funds if milestones are being met, is one very interesting idea that should be done more. Initially, sales took a few hours to finish. keywords: market; price; sale; time; tokens; valuation cache: vitalik-sales.html plain text: vitalik-sales.txt item: #2430 of 3327 id: vitalik-scaling author: vitalik title: vitalik-scaling date: None words: 3792 flesch: 67 summary: We don't know what the exact threshold is at which herd immunity against coordinated attacks kicks in, but there is one thing that's absolutely clear: more nodes good, fewer nodes bad, and we definitely need more than a few dozen or few hundred. So, what are the limits to how much work we can require full nodes to do? keywords: blockchain; blocks; data; need; node; process; users cache: vitalik-scaling.html plain text: vitalik-scaling.txt item: #2431 of 3327 id: vitalik-sharding author: vitalik title: vitalik-sharding date: None words: 4689 flesch: 58 summary: In the case of Ethereum sharding, the near-term plan is to make sharded blocks data-only; that is, the shards are purely a data availability engine, and it's the job of layer-2 rollups to use that secure data space, plus either fraud proofs or ZK-SNARKs, to implement high-throughput secure transaction processing capabilities. No single computer is powerful enough to validate all of these blocks before the next set of blocks comes in. keywords: availability; block; chain; computation; data; sharding cache: vitalik-sharding.html plain text: vitalik-sharding.txt item: #2432 of 3327 id: vitalik-sharding_faq author: vitalik title: vitalik-sharding_faq date: None words: 11943 flesch: 54 summary: One possible route to solving this is to create a platform that offers both kinds of shards - some shards would be higher-security global shards that are randomly sampled, and other shards would be lower-security local shards that could have properties such as ultra-fast block times and cheaper transaction fees. That said, shard chains to actually agree on what data gets included into the shard chains in the first place is still required. keywords: attacker; block; chain; cross; data; majority; model; proof; shard; sharding; state; time; transaction; validators cache: vitalik-sharding_faq.html plain text: vitalik-sharding_faq.txt item: #2433 of 3327 id: vitalik-snarks author: vitalik title: vitalik-snarks date: None words: 4692 flesch: 64 summary: What's a slightly more useful example of a computation being converted into a set of polynomial equations? Better ways to encode computation into polynomials: figuring out the most efficient way to encode complicated computations involving hash functions, memory access and other features into polynomial equations is still a challenge. keywords: \(p\; check; computation; number; polynomial cache: vitalik-snarks.html plain text: vitalik-snarks.txt item: #2434 of 3327 id: vitalik-soulbound author: vitalik title: vitalik-soulbound date: None words: 2053 flesch: 64 summary: Making more items in the crypto space soulbound can be one path toward an alternative, where NFTs can represent much more of who you are and not just what you can afford. Dark Mode Toggle Soulbound 2022 Jan 26 See all posts One feature of World of Warcraft that is second nature to its players, but goes mostly undiscussed outside of gaming circles, is the concept of soulbound items. keywords: governance; items; nfts; proof cache: vitalik-soulbound.html plain text: vitalik-soulbound.txt item: #2435 of 3327 id: vitalik-stable author: vitalik title: vitalik-stable date: None words: 2563 flesch: 64 summary: Dark Mode Toggle Two thought experiments to evaluate automated stablecoins 2022 May 25 See all posts Special thanks to Dan Robinson, Hayden Adams and Dankrad Feist for feedback and review. But what about automated stablecoins? keywords: price; rai; stablecoin; system cache: vitalik-stable.html plain text: vitalik-stable.txt item: #2436 of 3327 id: vitalik-starks_part_1 author: vitalik title: vitalik-starks_part_1 date: None words: 2929 flesch: 67 summary: Dark Mode Toggle STARKs, Part I: Proofs with Polynomials 2017 Nov 09 See all posts Special thanks to Eli Ben-Sasson for ongoing help, explanations and review, coming up with some of the examples used in this post, and most crucially of all inventing a lot of this stuff; thanks to Hsiao-wei Wang for reviewing Hopefully many people by now have heard of ZK-SNARKs, the general-purpose succinct zero knowledge proof technology that can be used for all sorts of usecases ranging from verifiable computation to privacy-preserving cryptocurrency. Hence, what these tools will provide is proof of proximity - proof that most of the points on \(P\) and \(D\) correspond to the right kind of polynomial. keywords: \(x\; points; polynomial; proof; prover cache: vitalik-starks_part_1.html plain text: vitalik-starks_part_1.txt item: #2437 of 3327 id: vitalik-starks_part_2 author: vitalik title: vitalik-starks_part_2 date: None words: 3161 flesch: 61 summary: This gives the verifier a statistical proof that (i) most rows are populated mostly by points on degree \(< 1000\) polynomials, (ii) most columns are populated mostly by points on degree \(< 1000\) polynomials, and (iii) the diagonal line is mostly on these polynomials. Note that this is only a proximity test, because there's always the possibility that most points are on the same low-degree polynomial, but a few are not, and the \(D+1\) sample missed those points entirely. keywords: \cdot; degree; points; polynomial cache: vitalik-starks_part_2.html plain text: vitalik-starks_part_2.txt item: #2438 of 3327 id: vitalik-starks_part_3 author: vitalik title: vitalik-starks_part_3 date: None words: 5456 flesch: 55 summary: So instead we use a similar kind of polynomial division trick: # Compute interpolant of ((1, input), (x_atlast_step, output)) interpolant = f.lagrange_interp_2([1, last_step_position], [inp, output]) i_evaluations = [f.eval_poly_at(interpolant, x) for x in xs] zeropoly2 = f.mul_polys([-1, 1], [-last_step_position, 1]) inv_z2_evaluations = f.multi_inv([f.eval_poly_at(quotient, x) for x in xs]) # B = (P - I) / Purple: computational trace polynomial (P). keywords: \cdot; degree; modulus; polynomial; root; steps; values cache: vitalik-starks_part_3.html plain text: vitalik-starks_part_3.txt item: #2439 of 3327 id: vitalik-stealth author: vitalik title: vitalik-stealth date: None words: 3348 flesch: 63 summary: FHE could also be used to help stealth address protocols in a different way: to help Bob outsource the computation of checking the entire chain for stealth addresses containing assets without revealing his view key. Dark Mode Toggle An incomplete guide to stealth addresses 2023 Jan 20 See all posts Special thanks to Ben DiFrancesco, Matt Solomon, Toni Wahrstätter and Antonio Sanso for feedback and review One of the largest remaining challenges in the Ethereum ecosystem is privacy. keywords: address; bob; key; public; stealth cache: vitalik-stealth.html plain text: vitalik-stealth.txt item: #2440 of 3327 id: vitalik-story author: vitalik title: vitalik-story date: None words: 1158 flesch: 71 summary: Bob starts reading, as all four start typing into their phones at the same time: Alice's first key share is, 6-b-d-7-h-k-k-l-o-e-q-q-p-3-y-s-6-x-e-f. Applying the 100,000x iterated SHA256 hash we get e-a-6-6..., confirm? Confirmed, the others replied. Alice's second key share is, f-r-n-m-j-t-x-r-s-3-b-u-n-n-n-i-z-3-d-g. Iterated hash 8-0-3-c..., confirm? Confirmed. keywords: alice; bob; key cache: vitalik-story.html plain text: vitalik-story.txt item: #2441 of 3327 id: vitalik-techno_optimism author: vitalik title: vitalik-techno_optimism date: None words: 11201 flesch: 56 summary: This core idea, that some technologies are defense-favoring and are worth promoting, while other technologies are offense-favoring and should be discouraged, has roots in effective altruist literature under a different name: differential technology development. This month, we saw a similar debate enacted through the OpenAI dispute, which involved many discussions centering around the dangers of superintelligent AI and the possibility that OpenAI is moving too fast. keywords: acc; century; defense; example; future; good; human; need; people; power; superintelligent; technologies; technology; things; tools; users; way; world; years cache: vitalik-techno_optimism.html plain text: vitalik-techno_optimism.txt item: #2442 of 3327 id: vitalik-three_transitions author: vitalik title: vitalik-three_transitions date: None words: 3978 flesch: 62 summary: ETH addresses, including smart contract addresses with CREATE2, have this feature. Smart contract wallets add more complexity, by making it much more difficult to have the same address across L1 and the various L2s. keywords: address; addresses; contract; key; users cache: vitalik-three_transitions.html plain text: vitalik-three_transitions.txt item: #2443 of 3327 id: vitalik-traveltime author: vitalik title: vitalik-traveltime date: None words: 1213 flesch: 62 summary: That is to say, if you sample randomly from positions where people are actually at (so, for example, 56% of points you choose would be in cities), and you use public transportation, how does travel time scale with distance? Obviously, travel time would grow slower than linearly: the further you have to go, the more opportunity you have to resort to forms of transportation that are faster, but have some fixed overhead. Now, I needed travel time data for longer distances, where the optimal route would include flights. keywords: time; travel cache: vitalik-traveltime.html plain text: vitalik-traveltime.txt item: #2444 of 3327 id: vitalik-triangle_of_harm author: vitalik title: vitalik-triangle_of_harm date: None words: 1295 flesch: 54 summary: We can play around with the factors; for example, it may be considered okay to allow griefing factors of 2 for majority attackers in exchange for keeping the griefing factor at 0.5 for minorities, with the reasoning that minority attackers are more likely. In Casper, protocol utility is zero for a perfect execution where every epoch is finalized and no safety failures ever take place, with some penalty for every epoch that is not finalized, and a very large penalty for every safety failure. keywords: majority; protocol cache: vitalik-triangle_of_harm.html plain text: vitalik-triangle_of_harm.txt item: #2445 of 3327 id: vitalik-trust author: vitalik title: vitalik-trust date: None words: 1516 flesch: 60 summary: If we want to make practical moves toward trust minimization, we want to have the ability to compare different degrees of trust. Here are a few examples of trust models of a few blockchain layer 2 protocols. keywords: trust cache: vitalik-trust.html plain text: vitalik-trust.txt item: #2446 of 3327 id: vitalik-trustedsetup author: vitalik title: vitalik-trustedsetup date: None words: 2323 flesch: 68 summary: The future of trusted setups Powers-of-tau is not the only kind of trusted setup out there. This article will explain how the KZG setup works, why it works, and the future of trusted setup protocols. keywords: g_2; points; secret; setup cache: vitalik-trustedsetup.html plain text: vitalik-trustedsetup.txt item: #2447 of 3327 id: vitalik-using_snarks author: vitalik title: vitalik-using_snarks date: None words: 3743 flesch: 68 summary: ZK negative reputation Suppose that we want to build 0chan, an internet forum which provides full anonymity like 4chan (so you don't even have persistent names), but has a reputation system to encourage more quality content. Private inputs: Your private key \(k\) Either an external identity (with address \(A\)), or the nullifier \(N_{prev}\) used by the previous post A Merkle proof \(M\) proving inclusion of \(A\) or \(N_{prev}\) on-chain The number \(i\) of posts that you have previously made with this account Verification function: Check that \(M\) is a valid Merkle branch proving that (either \(A\) or \(N_{prev}\), whichever is provided) is a leaf in a tree with root \(R\) keywords: chain; post; proof; reputation; snark cache: vitalik-using_snarks.html plain text: vitalik-using_snarks.txt item: #2448 of 3327 id: vitalik-ux author: vitalik title: vitalik-ux date: None words: 1796 flesch: 65 summary: Along with the all-important issue of high transaction fees due to scaling not yet being fully solved, user experience is a key reason why many Ethereum users, especially in the Global South, often opt for centralized solutions instead of on-chain decentralized alternatives that keep power in the hands of the user and their friends and family or local community. If you send a transaction at the same time as when many others are sending transactions and the base fee is spiking up, you risk the base fee going too high and your transaction not getting accepted. keywords: time; transaction; wallet cache: vitalik-ux.html plain text: vitalik-ux.txt item: #2449 of 3327 id: vitalik-ux_zhCN author: vitalik title: vitalik-ux_zhCN date: None words: 157 flesch: 18 summary: Dark Mode Toggle 我在加密世界的一些个人体验 2022 Oct 28 See all posts 译者：wonder @ GreenPill CN 原文：Some personal user experiences 我在加密世界的一些个人体验 2013 年，我去了旧金山互联网档案馆旁边的一家寿司店，因为我听说它接受比特币支付，我想去试试。在结账的时候，我要求用 BTC 进行支付，我扫描了二维码，然后点击了「发送」。令我惊讶的是，交易并没有成功；看起来交易已经发送出去，但餐厅并没有收到这笔交易。我又试了一次，还是没有成功。我很快就发现了问题所在，原因在于当时我的网络信号不好。我不得不向附近的互联网档案馆走 50 多米，接入了它的 WiFi，才终于将这笔交易发送出去。 经验教训：互联网不是 100% 可靠的，用户互联网比商家互联网更不可靠。线下支付系统需要具备一些能让客户直接将交易数据传输给商家的功能（例如 NFC、客户出示二维码等等），假如这是传输的最佳方式的话。 2021 年，在阿根廷的一家咖啡店，我尝试使用加密货币为自己和朋友支付茶水费。店主表示，他们本不接受加密货币支付，只是因为他认出了我。他向我展示了他在加密货币交易所拥有的一个账户，所以我提议用 ETH 进行支付（在拉丁美洲使用加密货币交易所账户作为钱包是一种标准的面对面支付方式）。不凑巧的是，第一笔 0.003 ETH 的交易没有被接收成功，可能是因为它低于交易所 0.01 ETH 的最低存款额要求。于是我又发送了 0.007 ETH，很快，两笔交易都得到了确认。(我并不介意多付 3 倍的钱，就当作是小费吧）。 2022 年，在另一家店铺，我再次尝试用加密货币支付茶水费。第一笔交易失败了，因为我的手机钱包的默认交易只发送了 21,000 gas，而接收账户是一个智能合约，需要额外 gas 才能处理转账。试图发送的第二笔交易也失败了，因为我的手机钱包的用户界面出现了点小故障，无法向下滑动并编辑「gas 限制」这一字段。 经验教训：简单实用的用户界面要优于花哨华丽的用户界面。但是，大多数用户甚至不知道「gas 限制」是什么，所以我们的确需要优化默认值。 有很多次，我的交易被链上接收和系统确认交易之间的延迟出乎意料地久，甚至出现了「未确认」的状态。有时，我的确会担心链上的支付系统是否出现了一些故障。 还有很多次，发送交易和区块接收交易之间存在延迟，并且这种延迟是不可预测的。有时，一笔交易会在几秒钟内被接收，但更多时候一笔交易需要几分钟甚至几小时才被接收。最近，EIP-1559 大大优化了这一点，确保大多数交易被接收到下一个区块中，最近的合并通过稳定区块时间进一步改善了这种情况。 Yinhong (William) Zhao 和 Kartik Nayak 制作的报告 但是，异常值仍然存在。如果同时有许多人正在发送交易，那么基础 gas 费就会飙升，你就会面临基础 gas 费过高和交易不被接收的风险。更糟糕的是，钱包的用户界面对这种情况的提示也不够到位，既没有显眼的红色闪烁警报，也没有清晰的提醒告知用户应该做什么来解决这个问题。即使你是专家，知道在这种情况下，可以通过提高 gas 费并发布一个数据相同的新交易来「加速」交易，但往往找不到可操作的按钮在哪里。 经验教训：交易相关的用户体验仍需改进，改善方法其实相当简单。感谢 Brave 钱包团队认真对待了我在这个问题上的建议，首先将最大基本费用的限制从 12.5% 提高到了 33%；近期，他们还在探索如何在用户界面清晰地展示「交易被卡住了」这一状态的方法。 2019 年，我测试了一款早期的钱包，它提供社交恢复方案。与我偏爱的智能合约方案不同的是，社交恢复采取了沙米尔的秘密分享理念，即将账户的私钥分成五部分，集齐其中任何三个部分都可以恢复私钥。用户需要选择五个朋友（或者是当代术语「守护人（guardians）」），说服他们下载一个单独的移动应用程序，并提供一个确认码，通过 Firebase 创建一个从用户钱包到应用程序的加密连接，并将他们拥有的密钥发送给用户。 于我而言，使用这种方法很快就遇到了麻烦。几个月后，我的钱包出了问题，我需要使用恢复程序来恢复钱包。我请朋友们通过他们的应用程序和我一起执行恢复程序，但事情并没有按计划进行。其中两位朋友丢失了他们的密钥，因为他们换了手机，忘记迁移恢复程序。第三位朋友表示，Firebase 的连接机制在很长一段时间内不起作用。虽然最终我们还是想出了解决问题的办法，并恢复了密钥。但是，几个月之后，钱包又坏了。这一次的问题在于，一次常规的软件更新莫名其妙重置了应用程序的存储，并删除了密钥。由于 Firebase 的连接机制过于垃圾，我无法添加足够的恢复伙伴，最终损失了少量的 BTC 和 ETH。 经验教训：基于秘密分享的链下社交恢复实在是太脆弱了，在有其他选择的情况下，这绝不是一个好的方法。帮助恢复密钥的守护人不应该下载一个单独的应用程序，因为如果一个应用程序只有「恢复（密钥）」这一种特殊用途，人们很容易忘记和丢失。此外，独立的中心化通信渠道也会带来各种问题。相反，添加守护人的方式应该是提供他们的 ETH 地址，恢复过程应该由智能合约完成，例如使用 ERC-4337 账户抽象钱包。这样一来，守护人只需保证不丢失以太坊钱包即可；出于其他原因，他们也会更加小心翼翼，不让钱包丢失。 2021 年，我想通过使用 Tornado Cash 的「自我中继」选项来节省费用。Tornado Cash 采用的「中继器」机制是由第三方在链上来推送交易。因为当你取款时，你的取款地址中一般没有代币，并且你不想用你的存款地址来支付交易，因为这样会在两个地址之间形成公开的联系，这正是 Tornado Cash 试图避免的问题。但中继器机制往往很昂贵，中继器收取的百分比费用可能远远超过交易的实际 gas 费。 为了节约成本，有一次，我使用中继器先发起了一笔小额提款，这样收取的费用较低，然后在不使用中继器的情况下，我通过 Tornado Cash 的「自我中继」功能，发送了第二笔大额提款。然后，我搞砸了，我在登录存款地址时不小心进行了这项操作，所以我使用了存款地址而不是提款地址，支付了费用。糟糕！我在两者之间建立了一个公开的联系。 经验教训：钱包开发者应该开始更明确地考虑隐私问题。此外，我们需要更好的账户抽象形式，以消除对中心化、甚至是联合中继的需求，并使中继角色商品化。 其它事项 许多应用程序不兼容 Brave 钱包或 Status 浏览器；这可能是因为他们没有好好地做准备工作，并依赖于 Metamask 独有的 API。甚至在很长一段时间里，Gnosis Safe 也不兼容这些钱包，导致我不得不自己编写迷你 Javascript dapp 来进行确认。幸运的是，最新的 UI 已经修复了这个问题。 在 Etherscan 上的 ERC20 转账页面（例如：https://etherscan.io/address/0xd8da6bf26964af9d7eed9e03e53415d37aa96045#tokentxns）非常容易被造假，导致欺诈行为。任何人都可以创建一个新的 ERC20 代币，可以发布一个日志，声称我或某个知名人士向其他人发送了代币。有时，人们会被这种把戏欺骗，认为我为一些骗人的代币站台，而实际上我从未听说过它。 Uniswap 曾经提供了非常便利的功能，能够交换代币并将输出发送到不同的地址。当我身上没有任何 USDC 时，但我需要用 USDC 支付给某人，这个功能十分便利。现在，Uniswap 不提供这个功能了，所以我不得不先完成兑换然后再发送一笔单独的交易，不仅不方便，而且浪费了更多的 gas 费。我后来了解到 Cowswap 和 Paraswap 提供了这个功能，不过 Paraswap......目前似乎不支持 Brave 钱包。 使用以太坊登录固然不错，但如果你想在多个设备登录，而你的以太坊钱包只能在一个设备上使用的话，这算不上是好用的方式。 结论 良好的用户体验不是在平均情况下的表现，而是如何处理最坏情况。如果用户界面简约整洁，但在 0.723% 的时间里会出现一些奇怪且无法解释的状况，从而导致一些大麻烦，其实比事无巨细的用户界面更糟糕，因为后者至少可以让用户更容易理解发生了什么，并解决出现的问题。 除了扩容导致的高额交易费用这一重要问题尚未完全解决，用户体验也是许多以太坊用户，尤其是南方世界的用户，经常选择中心化解决方案的关键原因；这也阻碍了用户选择将权力掌握在自己、亲友或当地社区手中这一链上去中心化方案。多年来，用户体验已经取得了长足的进步，尤其是 EIP-1559 的采用。在此之前，交易被接收的平均时间是几分钟，而合并之后的平均交易时间只需要几秒钟，这极大提升了使用以太坊的愉悦程度，但以太坊要做的远不止于此。 keywords: eth; gas cache: vitalik-ux_zhCN.html plain text: vitalik-ux_zhCN.txt item: #2450 of 3327 id: vitalik-verkle author: vitalik title: vitalik-verkle date: None words: 2664 flesch: 69 summary: This is the main constraint limiting Verkle tree widths. Hence, Verkle tree widths can go quite high; width 256-1024 seems like an optimal range. keywords: node; proof; tree; verkle cache: vitalik-verkle.html plain text: vitalik-verkle.txt item: #2451 of 3327 id: vitalik-voting author: vitalik title: vitalik-voting date: None words: 4053 flesch: 53 summary: Now, let us go through some arguments against voting, and dissect how each argument applies to voting as layer 1 and voting as layer 2. Low Voter Participation One of the main criticisms of coin voting mechanisms so far is that, no matter where they are tried, they tend to have very low voter participation. The Role of Coin Voting Ethereum also has a history with coin voting, including: DAO proposal votes: https://daostats.github.io/proposals.html The DAO Carbonvote: http://v1.carbonvote.com/ The EIP keywords: blockchain; coin; coordination; governance; layer; protocol; vote; voting cache: vitalik-voting.html plain text: vitalik-voting.txt item: #2452 of 3327 id: vitalik-voting2 author: vitalik title: vitalik-voting2 date: None words: 4419 flesch: 55 summary: And it's not just random tech journalists: Bruce Schneier is against blockchain voting, and researchers at MIT wrote a whole paper arguing that it's a bad idea. This by itself is not an argument against ever using blockchain voting. keywords: blockchain; coercion; key; resistance; security; vote; voting cache: vitalik-voting2.html plain text: vitalik-voting2.txt item: #2453 of 3327 id: vitalik-voting3 author: vitalik title: vitalik-voting3 date: None words: 5221 flesch: 56 summary: Dark Mode Toggle Moving beyond coin voting governance 2021 Aug 16 See all posts Special thanks to Karl Floersch, Dan Robinson and Tina Zhen for feedback and review. Coin voting governance empowers coin holders and coin holder interests at the expense of other parts of the community: protocol communities are made up of diverse constituencies that have many different values, visions and goals. keywords: chain; coin; decision; funding; governance; protocol; public; vote; voting cache: vitalik-voting3.html plain text: vitalik-voting3.txt item: #2454 of 3327 id: vitalik-zk_snarks author: vitalik title: vitalik-zk_snarks date: None words: 2480 flesch: 59 summary: Hence, we need to add yet more data to the trusted setup; specifically the sequence: \(G, G \cdot t, G \cdot t^2, G \cdot t^3, G \cdot t^4 ...\). To get a bit of a feel for how you would do this, here's a simple algorithm for taking an existing set (\(G, G \cdot t, G \cdot t^2, G \cdot t^3...\)), and adding in your own secret so that you need both your secret and the previous secret (or previous set of secrets) to cheat. keywords: \cdot; curve; points; setup cache: vitalik-zk_snarks.html plain text: vitalik-zk_snarks.txt item: #2455 of 3327 id: vitalik-zkevm author: vitalik title: vitalik-zkevm date: None words: 2383 flesch: 60 summary: In such a future, we would have multiple ZK-EVM implementations which could be used both for ZK rollups and to verify the Ethereum chain itself. Despite this implementation detail, I would still call this a genuine Type 3 ZK-EVM; it can still verify EVM code, it just uses some different internal logic to do it. keywords: ethereum; evm; evms; type cache: vitalik-zkevm.html plain text: vitalik-zkevm.txt item: #2456 of 3327 id: vitalik-zkevm_TR author: vitalik title: vitalik-zkevm_TR date: None words: 1963 flesch: 60 summary: Ancak böyle bir geleceğe ulaşmamız oldukça zaman alacak. Dezavantaj: Gelişmiş ancak hala yavaş kanıtlayıcı süresi Tip 2 ZK-EVM'ler, Ethereum yığınının gereksiz derecede karmaşık ve ZK dostu olmayan kriptografiye dayanan kısımlarını kaldırarak Tip 1'den daha hızlı kanıtlayıcı süreleri sağlar. keywords: ancak; bir; bunu; daha; dengi; dostu; ethereum; evm; evm'ler; farklı; gibi; ile; inşa; için; kanıtlayıcı; olarak; tam; tip; veya cache: vitalik-zkevm_TR.html plain text: vitalik-zkevm_TR.txt item: #2457 of 3327 id: vitalik-zkevm_zhTW author: vitalik title: vitalik-zkevm_zhTW date: None words: 540 flesch: 8 summary: 。 優點：等價於虛擬機 第 2 類 ZK-EVM 改動了儲存諸如 Ethereum state 的資料結構。幸運的是，這是都是 EVM 本身無法直接存取的結構，所以在 Ethereum 之上執行的應用程式幾乎都可以在第 2 類 ZK-EVM rollup 上使用。你無法直接利用以太的執行端，但經過微調之後可以，EVM 的除錯工具，和多數的開發設施，也都能照常使用。 也有少數的例外的情況。對於使用以太坊歷史區塊（historical Ethereum blocks）的雜湊數驗證（Merkle proofs） 來驗證對歷史交易、交易明細、或狀態（claims about historical transactions, receipts, or state）（例如：跨鏈橋有時候會這麼作）就會有不相容的情況發生。如果有 ZK-EVM 用其他雜湊函數取代 Keccak，這些證明會失效。然而，我本來就不建議這樣設計應用程式，因為未來以太坊會引用的改變（例如 Verkle trees）會讓這些應用程式連在以太坊上都不能使用。比較好的替代方案，是以太坊本身應該要新增不容易被未來科技淘汰的歷史取用預編譯合約（future-proof history access precompiles）。 缺點：證明者運算時間稍有改善到仍然很慢 第 2 類 ZK-EVM 的證明者運算速度，比第 1 類更快，主要的原因，是因為不再使用某些以太坊上，對零知識技術毫無意義地不友善的密碼學。尤其，他們可能會改變 Ethereum 的 Keccak 和基於 RLP 的 Merkle Patricia tree，還有或許區塊及交易明細的結構。第 2 類 ZK-EVM 可能會使用不同的雜湊函數，例如 Poseidon。也很自然發生的改變是修正狀態樹，以儲存合約碼雜湊值（code hash）和 keccak，免除對於執行EXTCODEHASH和EXTCODECOPY所需要的雜湊驗證。 這些改動大幅的改善證明者運算時間，但不會完全解決所有問題。證明現況下的EVM的緩慢效率，以及源自於EVM的其他不效率、對zk的不友善，都還留著。舉一個簡單例子：記憶體。因為一個MLOAD只能一次讀 32 bytes，包含「沒有對齊的」字節（起始端和終端都不是32的倍數），一個 MLOAD 無法被直接讀取為一個 chunk，它可能需要讀超過兩個連續的 chuck，並作一些運算，合併結果。 實例 Scroll 的 ZK-EVM 以及 Polygon Hermez 都屬於第 2 類。然而，兩個專案距離到位都還早。尤其因為還沒加入比較複雜的預編譯，因此，以目前來說，兩個專案都更應該被分類在第 3 類。 第 2.5 類：跟以太坊虛擬機結構一樣，但是 gas 訂價例外 想要大幅減少最壞可能的證明者運算時間（worst-case prover times）的方法，就是針對 EVM 內很難的零知識證明運算，大幅提升所需的 gas 訂價。這會牽扯到預編譯、KECCAK 操作碼、以及或許呼叫合約的特殊模式（specific patterns of calling contracts）、存取記憶體（accessing memory）、 儲存空間（storage）或還原（reverting）。 改善 gas 訂價可能會降低開發者工具的相容性，並會讓一些應用程式不能用（break），但是它比起更「深層」的 EVM 改動風險較低。開發者應該要注意，不要在一筆交易中花費超過一個區塊能容納的 gas，也永遠不要把呼叫合約時所需要花用的 gas 寫死（這本來就是會給開發者的標準建議）。 另一個解決資源限制問題的替代方式，是直接對每一個運算可以被呼叫的次數設下硬性的限制。這在電路上更容易實作，但是對 EVM 的安全性假設就沒有那麼合適。這種作法我認為屬於第 3 類而非第 2.5 類。 第 3 類：接近以太坊虛擬機等效（almost EVM-equivalent） 3 類 ZK-EVM。 很多除錯的基礎設施無法被直接利用，因為這些基礎設施只能跑在 EVM bytecode 上。話雖如此，有很多來自傳統高階或中階語言（例如 LLVM）的除錯工具可以用來緩解這個缺點。 以上都是工程師需要留意的問題。 實例 ZKSync 是第 4 類系統，雖然隨著時間他們可能會改善對 EVM bytecode 的相容性。Nethermind 的 Warp 專案正在蓋一個能把 Solidity 編譯成 Starkware 的 Cairo 語言的編譯器，這會因此把 keywords: evm; snark cache: vitalik-zkevm_zhTW.html plain text: vitalik-zkevm_zhTW.txt item: #2458 of 3327 id: vitalik-zkmulticlient author: vitalik title: vitalik-zkmulticlient date: None words: 3143 flesch: 57 summary: Once that happens, ZK-EVMs de-facto become a third type of Ethereum client, just as important to the network's security as execution clients and consensus clients are today. It would realistically take a long time (even if eg. 15 seconds) to generate proofs valid for other clients. keywords: client; ethereum; layer; multi cache: vitalik-zkmulticlient.html plain text: vitalik-zkmulticlient.txt item: #2459 of 3327 id: www-1 author: www title: www-1 date: None words: 1316 flesch: 36 summary: Next page > Submit a blog Blog guidelines RSS Introducing Hyperledger FireFly, a Multi-Party System for Enterprise Data Flows We are very excited to announce the newest Hyperledger project, Hyperledger FireFly. With a few years behind... Read More Jessica Rampen | Dec 15, 2020 Blog | Finance An innovative blockchain solution powered by Hyperledger Fabric helps banks implement DeFI services in days Digitization is a megatrend that has already transformed many industries – and now it’s banking’s turn. keywords: blockchain; blog; hyperledger; jessica; rampen cache: www-1.html plain text: www-1.txt item: #2460 of 3327 id: www-2 author: www title: www-2 date: None words: 1420 flesch: 36 summary: Read More Jessica Rampen | Nov 5, 2020 Besu Announcing Hyperledger Besu 20.10.0 This release includes new versioning and mainnet-focused advancements Read More Jessica Rampen | Nov 4, 2020 Blog The move to a production network: What you need to consider and how Hyperledger Fabric can help Blockchain is a distributed ledger technology that provides a shared, immutable, and transparent history to the participants in the network of all the actions that have happened.... Further enhancing the new... Read More Jessica Rampen | Jul 20, 2020 Besu Announcing Hyperledger Besu 1.5: Available Now The latest release of Hyperledger Besu is now available for download. keywords: besu; blockchain; blog; hyperledger; jessica; jessica rampen; rampen cache: www-2.html plain text: www-2.txt item: #2461 of 3327 id: www-2019-summer-mentee-project-update-design-effective-os-to-manage-blockchain-networks author: www title: www-2019-summer-mentee-project-update-design-effective-os-to-manage-blockchain-networks date: None words: 811 flesch: 42 summary: We were able to  Create a base for an operator agent for Fabric in the Cello codebase Create custom resources and APIs for CAs, peer and orderer Implement the operator controllers for CA, peer and orderer Integrate the agent with the Cello API and dashboard Generate documentation for the new agent so that it can be used by the users Project Progress During my project, we successfully created an agent for Hyperledger Cello that can be used to create peer, CAs and orderers for Hyperledger Fabric. I will also be speaking at Hyperledger Global Forum 2020 in Phoenix, Arizona, talking about my project and work and also Hyperledger Cello. keywords: agent; hyperledger; project cache: www-2019-summer-mentee-project-update-design-effective-os-to-manage-blockchain-networks.html plain text: www-2019-summer-mentee-project-update-design-effective-os-to-manage-blockchain-networks.txt item: #2462 of 3327 id: www-2019-summer-mentee-project-update-developing-explorer-capabilities-for-hyperledger-sawtooth author: www title: www-2019-summer-mentee-project-update-developing-explorer-capabilities-for-hyperledger-sawtooth date: None words: 845 flesch: 58 summary: 2019 Summer Mentee Project Update: Developing Explorer Capabilities for Hyperledger Sawtooth – Hyperledger Foundation 2025 The most vivid impression I have after working on a project related to Hyperledger Sawtooth is the responsiveness of the community members. keywords: hyperledger; project; sawtooth cache: www-2019-summer-mentee-project-update-developing-explorer-capabilities-for-hyperledger-sawtooth.html plain text: www-2019-summer-mentee-project-update-developing-explorer-capabilities-for-hyperledger-sawtooth.txt item: #2463 of 3327 id: www-2019-summer-mentee-project-update-git-signing-with-dids-hyperledger-indy author: www title: www-2019-summer-mentee-project-update-git-signing-with-dids-hyperledger-indy date: None words: 778 flesch: 34 summary: Technical Overview The following figure illustrate modification of git and the expected outcome of the project: What comes next This project can open the door to future signing tools integrations and maybe extended to projects other than git. The mentorship project can be extended in many ways: Create wrappers for additional signing tools like signify for example Write a wrapper for the Assuan protocol to add support for tools that use the Assuan library (like GPG & GPGSM for example) keywords: git; project; signing cache: www-2019-summer-mentee-project-update-git-signing-with-dids-hyperledger-indy.html plain text: www-2019-summer-mentee-project-update-git-signing-with-dids-hyperledger-indy.txt item: #2464 of 3327 id: www-2019-summer-mentee-project-update-git-signing-with-dids-hyperledger-indy?hs_amp=true author: www title: www-2019-summer-mentee-project-update-git-signing-with-dids-hyperledger-indy?hs_amp=true date: None words: 469 flesch: 46 summary: Technical Overview The following figure illustrate modification of git and the expected outcome of the project: What comes next This project can open the door to future signing tools integrations and maybe extended to projects other than git. The mentorship project can be extended in many ways: Create wrappers for additional signing tools like signify for example Write a wrapper for the Assuan protocol to add support for tools that use the Assuan library (like GPG & GPGSM for example) keywords: git; project cache: www-2019-summer-mentee-project-update-git-signing-with-dids-hyperledger-indy?hs_amp=true.html plain text: www-2019-summer-mentee-project-update-git-signing-with-dids-hyperledger-indy?hs_amp=true.txt item: #2465 of 3327 id: www-2019-summer-mentee-project-update-hyperledger-configuration-for-project-management-in-construction author: www title: www-2019-summer-mentee-project-update-hyperledger-configuration-for-project-management-in-construction date: None words: 858 flesch: 33 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog 2019 Summer Mentee Project Update: Hyperledger configuration for project management in construction Hyperledger | Dec 12, 2019 Project Description Construction management configuration of blockchain is a project of the Hyperledger Summer Mentorship Program 2019 that provides a way to apply Hyperledger technologies to construction and engineering (C&E) since literature research and practical simulation prove Hyperledger Fabric as one of the best platforms for C&E.  This project was conceived to test the potential of blockchains. 2019 Summer Mentee Project Update: Hyperledger configuration for project management in construction – Hyperledger Foundation 2025 keywords: blockchain; hyperledger; project; system cache: www-2019-summer-mentee-project-update-hyperledger-configuration-for-project-management-in-construction.html plain text: www-2019-summer-mentee-project-update-hyperledger-configuration-for-project-management-in-construction.txt item: #2466 of 3327 id: www-2019-summer-mentee-project-update-hyperledger-umbra-simulating-hyperledger-blockchains-using-mininet author: www title: www-2019-summer-mentee-project-update-hyperledger-umbra-simulating-hyperledger-blockchains-using-mininet date: None words: 665 flesch: 23 summary: Reproducible Ad-hoc Hyperledger Iroha Network (almost finished) Documentation (ongoing) Accepted for Hyperledger Global Forum 2020 What comes next This is the beginning of reproducible academic work on Hyperledger blockchain projects (i.e., the development of comparable methodologies for consensus, gossip, security, etc.). How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog 2019 Summer Mentee Project Update – Hyperledger Umbra: Simulating Hyperledger Blockchains using Mininet Hyperledger | Dec 12, 2019 What I worked on The simulation research internship during the summer of 2018 led to the creation of the Hyperledger Umbra Lab. keywords: decentralized; hyperledger; project; umbra cache: www-2019-summer-mentee-project-update-hyperledger-umbra-simulating-hyperledger-blockchains-using-mininet.html plain text: www-2019-summer-mentee-project-update-hyperledger-umbra-simulating-hyperledger-blockchains-using-mininet.txt item: #2467 of 3327 id: www-2019-summer-mentee-project-update-hyperledger-ursa-integration-into-hyperledger-iroha author: www title: www-2019-summer-mentee-project-update-hyperledger-ursa-integration-into-hyperledger-iroha date: None words: 813 flesch: 36 summary: 2019 Summer Mentee Project Update: Hyperledger Ursa integration into Hyperledger Iroha – Hyperledger Foundation 2025 Update: Off to a Fast Start!  How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger Iroha 2019 Summer Mentee Project Update: Hyperledger Ursa integration into Hyperledger Iroha Hyperledger | Dec 12, 2019 keywords: hyperledger; iroha; ursa cache: www-2019-summer-mentee-project-update-hyperledger-ursa-integration-into-hyperledger-iroha.html plain text: www-2019-summer-mentee-project-update-hyperledger-ursa-integration-into-hyperledger-iroha.txt item: #2468 of 3327 id: www-2019-summer-mentee-project-update-hyperledger-ursa-integration-into-hyperledger-iroha?hs_amp=true author: www title: www-2019-summer-mentee-project-update-hyperledger-ursa-integration-into-hyperledger-iroha?hs_amp=true date: None words: 504 flesch: 43 summary: 2019 Summer Mentee Project Update: Hyperledger Ursa integration into Hyperledger Iroha – Hyperledger Foundation Blog | LF Decentralized Trust 2019 Summer Mentee Project Update: Hyperledger Ursa integration into Hyperledger Iroha – What I worked on I primarily contributed to Hyperledger Iroha, a permissioned decentralized ledger technology. keywords: hyperledger; ursa cache: www-2019-summer-mentee-project-update-hyperledger-ursa-integration-into-hyperledger-iroha?hs_amp=true.html plain text: www-2019-summer-mentee-project-update-hyperledger-ursa-integration-into-hyperledger-iroha?hs_amp=true.txt item: #2469 of 3327 id: www-2019-summer-mentee-project-update-integration-of-evm-from-hyperledger-burrow-into-hyperledger-iroha author: www title: www-2019-summer-mentee-project-update-integration-of-evm-from-hyperledger-burrow-into-hyperledger-iroha date: None words: 844 flesch: 49 summary: First of all, there should be a way to pass data (such as Ethereum bytecode, caller and callee) from Hyperledger Iroha to Hyperledger Burrow EVM. 2019 Summer Mentee Project Update: Integration of EVM from Hyperledger Burrow into Hyperledger Iroha – Hyperledger Foundation 2025 keywords: burrow; evm; hyperledger; iroha cache: www-2019-summer-mentee-project-update-integration-of-evm-from-hyperledger-burrow-into-hyperledger-iroha.html plain text: www-2019-summer-mentee-project-update-integration-of-evm-from-hyperledger-burrow-into-hyperledger-iroha.txt item: #2470 of 3327 id: www-2019-summer-mentee-project-update-integration-of-evm-from-hyperledger-burrow-into-hyperledger-iroha?hs_amp=true author: www title: www-2019-summer-mentee-project-update-integration-of-evm-from-hyperledger-burrow-into-hyperledger-iroha?hs_amp=true date: None words: 532 flesch: 60 summary: First of all, there should be a way to pass data (such as Ethereum bytecode, caller and callee) from Hyperledger Iroha to Hyperledger Burrow EVM. 2019 Summer Mentee Project Update: Integration of EVM from Hyperledger Burrow into Hyperledger Iroha – Hyperledger Foundation Blog | LF Decentralized Trust 2019 Summer Mentee Project Update: Integration of EVM from Hyperledger Burrow into Hyperledger Iroha – Hyperledger Foundation Written by Hyperledger | Sep 19, 2019 8:11:39 AM Hello, my name is Ivan Tyulyandin. keywords: hyperledger; iroha cache: www-2019-summer-mentee-project-update-integration-of-evm-from-hyperledger-burrow-into-hyperledger-iroha?hs_amp=true.html plain text: www-2019-summer-mentee-project-update-integration-of-evm-from-hyperledger-burrow-into-hyperledger-iroha?hs_amp=true.txt item: #2471 of 3327 id: www-2019-summer-mentee-project-update-integration-of-hyperledger-iroha-into-hyperledger-explorer author: www title: www-2019-summer-mentee-project-update-integration-of-hyperledger-iroha-into-hyperledger-explorer date: None words: 532 flesch: 35 summary: Now, Hyperledger Explorer shows information about Hyperledger Iroha peers, blocks, transactions, roles, domains, accounts. 2019 Summer Mentee Project Update: Integration of Hyperledger Iroha into Hyperledger Explorer – Hyperledger Foundation 2025 keywords: hyperledger; iroha; project cache: www-2019-summer-mentee-project-update-integration-of-hyperledger-iroha-into-hyperledger-explorer.html plain text: www-2019-summer-mentee-project-update-integration-of-hyperledger-iroha-into-hyperledger-explorer.txt item: #2472 of 3327 id: www-2019-summer-mentee-project-update-integration-of-hyperledger-iroha-into-hyperledger-explorer?hs_amp=true author: www title: www-2019-summer-mentee-project-update-integration-of-hyperledger-iroha-into-hyperledger-explorer?hs_amp=true date: None words: 223 flesch: 45 summary: Now, Hyperledger Explorer shows information about Hyperledger Iroha peers, blocks, transactions, roles, domains, accounts. 2019 Summer Mentee Project Update: Integration of Hyperledger Iroha into Hyperledger Explorer – Hyperledger Foundation Blog | LF Decentralized Trust 2019 Summer Mentee Project Update: Integration of Hyperledger Iroha into Hyperledger Explorer – Hyperledger Foundation Written by Hyperledger | Sep 19, 2019 8:08:41 AM Hyperledger Iroha is a next-generation permissioned DLT initally contributed by Soramitsu. keywords: hyperledger cache: www-2019-summer-mentee-project-update-integration-of-hyperledger-iroha-into-hyperledger-explorer?hs_amp=true.html plain text: www-2019-summer-mentee-project-update-integration-of-hyperledger-iroha-into-hyperledger-explorer?hs_amp=true.txt item: #2473 of 3327 id: www-2019-summer-mentee-project-update-iot-and-dlt-in-a-telecom-multi-carriers-architecture author: www title: www-2019-summer-mentee-project-update-iot-and-dlt-in-a-telecom-multi-carriers-architecture date: None words: 641 flesch: 35 summary: Provided API documents for telecom devices companies, and a simple front-end demo (to be completed by 12/20/2019) What comes next For IoT devices, the device-to-device access and communication can enhance the entire systems ability of, for example, using Google voice kit to automatically control the smart home devices. Specifically, we designed a Decentralized Ledger Technology (DLT) architecture for supply chain process of telecom devices and implemented this architecture. keywords: architecture; decentralized; project cache: www-2019-summer-mentee-project-update-iot-and-dlt-in-a-telecom-multi-carriers-architecture.html plain text: www-2019-summer-mentee-project-update-iot-and-dlt-in-a-telecom-multi-carriers-architecture.txt item: #2474 of 3327 id: www-2019-summer-mentee-project-update-raspberry-pi-indy-agent author: www title: www-2019-summer-mentee-project-update-raspberry-pi-indy-agent date: None words: 790 flesch: 44 summary: 2019 Summer Mentee Project Update: Raspberry Pi Indy Agent – Hyperledger Foundation 2025 Implementation of a working Hyperledger Indy agent: Working with Aries Cloud Agent, I developed messaging protocols and successfully implemented a working agent. keywords: agent; hyperledger; indy; project cache: www-2019-summer-mentee-project-update-raspberry-pi-indy-agent.html plain text: www-2019-summer-mentee-project-update-raspberry-pi-indy-agent.txt item: #2475 of 3327 id: www-2020-hyperledger-annual-report author: www title: www-2020-hyperledger-annual-report date: None words: 566 flesch: 34 summary: Report highlights include: – The releases of Hyperledger Fabric 2.0 and Hyperledger Fabric 2.2 LTS – Hyperledger Besu’s graduation to active status – The launch of Hyperledger Cactus, which graduated from Hyperledger Labs – Record member participation in Member Summit – Swift, worldwide uptake of virtual meet-ups with more than 180 events in 81 countries Looking at the state of the ledger now, it’s clear that the focus has shifted from proving the value of blockchain to scaling, governance and managing blockchain networks. The report comes just as Hyperledger hits its 5th anniversary. keywords: decentralized; hyperledger; report cache: www-2020-hyperledger-annual-report.html plain text: www-2020-hyperledger-annual-report.txt item: #2476 of 3327 id: www-2023-a-year-of-collaboration-and-achievement author: www title: www-2023-a-year-of-collaboration-and-achievement date: None words: 1222 flesch: 45 summary: And that community is the key to the growth of Hyperledger technologies and enterprise blockchain adoption and our goal of Building Better Together.   Davos, Consensus, Money2020, Open Source Summits, Digital Currency Conference, WebX-Japan, Sibos and Singapore Fintech Festival are just some of the places where you found our community speaking and telling the world about how they are building better together with Hyperledger technologies. keywords: community; foundation; hyperledger; technologies; year cache: www-2023-a-year-of-collaboration-and-achievement.html plain text: www-2023-a-year-of-collaboration-and-achievement.txt item: #2477 of 3327 id: www-2023-a-year-of-collaboration-and-achievement?hs_amp=true author: www title: www-2023-a-year-of-collaboration-and-achievement?hs_amp=true date: None words: 903 flesch: 55 summary: And that community is the key to the growth of Hyperledger technologies and enterprise blockchain adoption and our goal of Building Better Together.   Davos, Consensus, Money2020, Open Source Summits, Digital Currency Conference, WebX-Japan, Sibos and Singapore Fintech Festival are just some of the places where you found our community speaking and telling the world about how they are building better together with Hyperledger technologies. keywords: community; hyperledger; year cache: www-2023-a-year-of-collaboration-and-achievement?hs_amp=true.html plain text: www-2023-a-year-of-collaboration-and-achievement?hs_amp=true.txt item: #2478 of 3327 id: www-2025-update-off-to-a-fast-start author: www title: www-2025-update-off-to-a-fast-start date: None words: 1376 flesch: 33 summary: This webinar from the Latin America Chapter provides guidance, in Spanish, for both exams The Brazil Chapter has added a number resources for the BCP exam to its Besu Hub, a space dedicated to the research, development and promotion of blockchain technology, focusing on the Besu protocol The India Chapter just hosted a webinar on India’s leadership in decentralized technologies, marking the publication of the latest ebook detailing activities across the India community LF Decentralized Trust Tech in the Market Of course all this work is, ultimately, in support of deploying technology to drive efficiencies, build businesses, change markets, and enable the transition to a digital-first economy. They include: DTCC launched a next-generation digital platform, built atop Besu, to improve global collateral mobility and efficiency, marking the first institutional use of AppChain infrastructure for decentralized finance The Bank of Hong Kong issued a $300 million digital bond with a three year terms using HSBC’s Orion digital asset platform, which is built on a Hyperledger Fabric-based blockchain Using a Hyperledger Fabric-powered platform, ATME, the digital assets exchange licensed by the Central Bank of Bahrain (CBB), has successfully completed its first issuance of tokenized real-world assets (RWAs) with gold-backed tokens The Bank of Papua New Guinea shared results of proof-of-concept experimentation as a step towards the launch of a CBDC built using Hyperledger Iroha technology A new South African ride-hailing platform, Twytch, is using Hyperledger Indy to improve passenger and driver safety by verifying both users’ identities while ensuring that this private data is not vulnerable to a data breach ForesToken has launched EyeForFor 2.0, a digital platform that uses a Besu-based blockchain and geointelligence to organize and structure the purchase and sale of wood, one of the top agricultural exports of Brazil DocOnChain has begun streamlining document handling for Philippine local governments and barangays with Hyperledger Fabric-based digital signature solutions Sharjah Maritime Academy introduced micro-credentials, which allows students to earn verifiable digital certifications for specialized skills and achievements, using a Hyperledger Fabric-powered platform from Educhain For more on LF Decentralized Trust technologies in action, explore our use case tracker, which has hundreds of examples that you can sort or filter, or check out our case study library, where we have deep dives into deployments from around the world.  keywords: community; decentralized; digital; technologies; trust cache: www-2025-update-off-to-a-fast-start.html plain text: www-2025-update-off-to-a-fast-start.txt item: #2479 of 3327 id: www-2025-update-off-to-a-fast-start?hs_amp=true author: www title: www-2025-update-off-to-a-fast-start?hs_amp=true date: None words: 1069 flesch: 39 summary: They include: DTCC launched a next-generation digital platform, built atop Besu, to improve global collateral mobility and efficiency, marking the first institutional use of AppChain infrastructure for decentralized finance The Bank of Hong Kong issued a $300 million digital bond with a three year terms using HSBC’s Orion digital asset platform, which is built on a Hyperledger Fabric-based blockchain Using a Hyperledger Fabric-powered platform, ATME, the digital assets exchange licensed by the Central Bank of Bahrain (CBB), has successfully completed its first issuance of tokenized real-world assets (RWAs) with gold-backed tokens The Bank of Papua New Guinea shared results of proof-of-concept experimentation as a step towards the launch of a CBDC built using Hyperledger Iroha technology A new South African ride-hailing platform, Twytch, is using Hyperledger Indy to improve passenger and driver safety by verifying both users’ identities while ensuring that this private data is not vulnerable to a data breach ForesToken has launched EyeForFor 2.0, a digital platform that uses a Besu-based blockchain and geointelligence to organize and structure the purchase and sale of wood, one of the top agricultural exports of Brazil DocOnChain has begun streamlining document handling for Philippine local governments and barangays with Hyperledger Fabric-based digital signature solutions Sharjah Maritime Academy introduced micro-credentials, which allows students to earn verifiable digital certifications for specialized skills and achievements, using a Hyperledger Fabric-powered platform from Educhain For more on LF Decentralized Trust technologies in action, explore our use case tracker, which has hundreds of examples that you can sort or filter, or check out our case study library, where we have deep dives into deployments from around the world.  2025 Update: Off to a Fast Start Blog | LF Decentralized Trust 2025 Update: Off to a Fast Start Written by Daniela Barbosa, General Manager of Decentralized Technologies at the Linux Foundation and Executive Director of LF Decentralized Trust | Apr 29, 2025 2:23:03 PM As we kick off the second quarter of 2025, it's a good time to reflect on the incredible progress we've made together at LF Decentralized Trust (LFDT). keywords: community; digital; trust cache: www-2025-update-off-to-a-fast-start?hs_amp=true.html plain text: www-2025-update-off-to-a-fast-start?hs_amp=true.txt item: #2480 of 3327 id: www-3 author: www title: www-3 date: None words: 809 flesch: 30 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Read More Jessica Rampen | Feb 25, 2020 Blog Sawtooth PBFT, Part 2: Extensions and Changes The upcoming release of Hyperledger Sawtooth 1.2 includes Sawtooth PBFT—a new, Cargill-sponsored, production-ready consensus algorithm. keywords: blog; decentralized; hyperledger; jessica; rampen cache: www-3.html plain text: www-3.txt item: #2481 of 3327 id: www-3-things-ethereum-users-should-know-about-hyperledger-burrow author: www title: www-3-things-ethereum-users-should-know-about-hyperledger-burrow date: None words: 1510 flesch: 49 summary: Enter Hyperledger Burrow, one of the Hyperledger projects hosted by the Linux Foundation. 3 Things Ethereum Users Should Know about Hyperledger Burrow – Hyperledger Foundation 2025 Update: Off to a Fast Start! keywords: blockchain; burrow; ethereum; hyperledger; users cache: www-3-things-ethereum-users-should-know-about-hyperledger-burrow.html plain text: www-3-things-ethereum-users-should-know-about-hyperledger-burrow.txt item: #2482 of 3327 id: www-3-things-ethereum-users-should-know-about-hyperledger-burrow?hs_amp=true author: www title: www-3-things-ethereum-users-should-know-about-hyperledger-burrow?hs_amp=true date: None words: 1199 flesch: 55 summary: Enter Hyperledger Burrow, one of the Hyperledger projects hosted by the Linux Foundation. 3 Things Ethereum Users Should Know about Hyperledger Burrow – Hyperledger Foundation Blog keywords: blockchain; burrow; hyperledger cache: www-3-things-ethereum-users-should-know-about-hyperledger-burrow?hs_amp=true.html plain text: www-3-things-ethereum-users-should-know-about-hyperledger-burrow?hs_amp=true.txt item: #2483 of 3327 id: www-4 author: www title: www-4 date: None words: 1400 flesch: 32 summary: Blog | LF Decentralized Trust | Hyperledger (4) 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us BLOG The latest community news, insights and developments Stay connected with the latest in open source decentralized technologies, member updates, and community-driven projects. “The Carbon Footprint of NFTs” report As Tom Brady, DCComics and Visa will tell you, non-fungible tokens (NFTs) are a class of assets underpinning the worlds of digital art, digital collectibles, metaverse gaming, and... Read More Hyperledger | Apr 22, 2022 Blog | Climate Tackling Energy Security and Climate Change with Open Source and Blockchain It started out as two separate projects at the Climate Accounting and Action SIG, a Hyperledger group focused on using blockchain and distributed ledger technologies (DLT’s) to... Read More Hyperledger | Apr 19, 2022 Hyperledger FireFly Introducing Hyperledger FireFly 1.0: The SuperNode for Enterprise Web3 Applications It’s been a busy 10 months for Hyperledger FireFly. keywords: blockchain; blog; hyperledger; opportunity; technologies cache: www-4.html plain text: www-4.txt item: #2484 of 3327 id: www-4735 author: www title: www-4735 date: None words: 1010 flesch: 48 summary: It’s a non-technical one; that management gain the understanding and confidence needed to champion the development of blockchain applications that provide real world solutions for real world benefit. Hyperledger is the future of mainstream blockchain applications and with the plethora of educational tools and resources, both old school as well as new technology based, there are simply now no excuses for not building world class educational resources. keywords: blockchain; decentralized; hyperledger; technologies cache: www-4735.html plain text: www-4735.txt item: #2485 of 3327 id: www-4735?hs_amp=true author: www title: www-4735?hs_amp=true date: None words: 696 flesch: 57 summary: It’s a non-technical one; that management gain the understanding and confidence needed to champion the development of blockchain applications that provide real world solutions for real world benefit. Hyperledger is the future of mainstream blockchain applications and with the plethora of educational tools and resources, both old school as well as new technology based, there are simply now no excuses for not building world class educational resources. keywords: blockchain; hyperledger cache: www-4735?hs_amp=true.html plain text: www-4735?hs_amp=true.txt item: #2486 of 3327 id: www-5 author: www title: www-5 date: None words: 1395 flesch: 25 summary: Blog | LF Decentralized Trust | Hyperledger (5) 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us BLOG The latest community news, insights and developments Stay connected with the latest in open source decentralized technologies, member updates, and community-driven projects. Read More Hyperledger | Dec 14, 2021 Blog MineHub and KrypC Leverage the Power of Hyperledger Fabric 2.2 to Transform Mining and Metals Supply Chain Read the full case study here. keywords: blog; dec; hyperledger; opportunity cache: www-5.html plain text: www-5.txt item: #2487 of 3327 id: www-6 author: www title: www-6 date: None words: 1394 flesch: 37 summary: Blog | LF Decentralized Trust | Hyperledger (6) 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us BLOG The latest community news, insights and developments Stay connected with the latest in open source decentralized technologies, member updates, and community-driven projects. Next page > Submit a blog Blog guidelines RSS Blog Welcome to the 2021-2022 Technical Steering Committee Each year, the Hyperledger technical community holds an election to select a new Technical Steering Committee (TSC) from the community at large. keywords: hyperledger; resources; update; weekend; weekend update cache: www-6.html plain text: www-6.txt item: #2488 of 3327 id: www-7 author: www title: www-7 date: None words: 1440 flesch: 35 summary: Blog | LF Decentralized Trust | Hyperledger (7) 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us BLOG The latest community news, insights and developments Stay connected with the latest in open source decentralized technologies, member updates, and community-driven projects. Read More Hyperledger | Aug 13, 2021 Blog | Developer Showcase Developer showcase series: Lucas Saldanha, ConsenSys Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. keywords: hyperledger; resources; update; weekend cache: www-7.html plain text: www-7.txt item: #2489 of 3327 id: www-70771 author: www title: www-70771 date: None words: 1237 flesch: 52 summary: In addition to the blockchain frameworks, I am quite interested in the different tools (e.g. Composer , Explorer) that are developed under the Hyperledger umbrella to facilitate and accelerate blockchain adoption. What advice would you offer other technologists or developers interested in getting started working on blockchain?  keywords: blockchain; business; hyperledger; jda cache: www-70771.html plain text: www-70771.txt item: #2490 of 3327 id: www-70771?hs_amp=true author: www title: www-70771?hs_amp=true date: None words: 923 flesch: 60 summary: In addition to the blockchain frameworks, I am quite interested in the different tools (e.g. Composer , Explorer) that are developed under the Hyperledger umbrella to facilitate and accelerate blockchain adoption. But given my current job and my focus at this time, I would select Hyperledger Fabric and Indy. Because it supports permissioned networks, Hyperledger Fabric seems appropriate in a supply chain environment where participants are usually known and vetted. keywords: blockchain; hyperledger; jda cache: www-70771?hs_amp=true.html plain text: www-70771?hs_amp=true.txt item: #2491 of 3327 id: www-71697 author: www title: www-71697 date: None words: 2370 flesch: 60 summary: Jay Guo Software Engineer, IBM (Project: Extended Support for EVM and and Tooling in Hyperledger Fabric) Lessons learned: We should set realistic goals for interns, and we should give them enough time to climb the learning curve. Advice for those interested in interning in the future: The interns that really stood out during the interview process had built projects utilizing existing open source projects. keywords: hyperledger; intern; internship; project; source; work cache: www-71697.html plain text: www-71697.txt item: #2492 of 3327 id: www-74658 author: www title: www-74658 date: None words: 1231 flesch: 46 summary: About the Authors Darian Plumb (Senior Software Engineer), Eloá Verona (Software Engineer) and Shannyn Telander (Software Engineer) work on Hyperledger Sawtooth projects at Bitwise IO. These first example applications showcase a client for the XO transaction processor that, although simple, opens up possibilities for Sawtooth mobile applications moving forward. keywords: hyperledger; mobile; sawtooth; sdk; swift cache: www-74658.html plain text: www-74658.txt item: #2493 of 3327 id: www-a-contributor-story-the-path-from-custom-apis-to-commercial-solutions-and-bug-fixes-to-fabric-2-1-documentation author: www title: www-a-contributor-story-the-path-from-custom-apis-to-commercial-solutions-and-bug-fixes-to-fabric-2-1-documentation date: None words: 1062 flesch: 41 summary: Adam also developed a guide for deploying Fabric EVM onto Hyperledger Fabric v2.1. As part of the contract, Adam Brinckman, a senior research programmer at the Center for Research Computing at the University of Notre Dame, wrote the chaincode (the “smart contract”) for an application enabling military agencies to create military interdepartmental purchase requests (MIPR transactions) on a privately shared Hyperledger Fabric distributed ledger for our project with DARPA. keywords: code; decentralized; fabric; hyperledger; project cache: www-a-contributor-story-the-path-from-custom-apis-to-commercial-solutions-and-bug-fixes-to-fabric-2-1-documentation.html plain text: www-a-contributor-story-the-path-from-custom-apis-to-commercial-solutions-and-bug-fixes-to-fabric-2-1-documentation.txt item: #2494 of 3327 id: www-a-frost-library-called-givre author: www title: www-a-frost-library-called-givre date: None words: 1388 flesch: 52 summary: FROST Signing: We offer APIs for both manual and interactive signing. This advanced MPC library provides secure and fast signing and key generation protocols for Schnorr and EdDSA, used by blockchains including Bitcoin, Solana, Stellar, Tezos, and more. keywords: frost; key; protocol; signing cache: www-a-frost-library-called-givre.html plain text: www-a-frost-library-called-givre.txt item: #2495 of 3327 id: www-a-look-at-hyperledger-powered-financial-services-solutions-in-action author: www title: www-a-look-at-hyperledger-powered-financial-services-solutions-in-action date: None words: 1410 flesch: 37 summary: Read on for details on applications and solutions leveraging a mix of Hyperledger technologies to invent and reinvent a range of services, including eKYC, insurance claims processing, accounts reconciliation, specialty trades and more: AnaMeen AnaMeen is a multi-organizational eKYC solution from Ahli Fintech involving Jordan Ahli Bank and Zain Jordan, a mobile telecom provider. The solution, which is powered Hyperledger Fabric, enables self-sovereign instant KYC data sharing, with full control in the users’ hands in full compliance with international data protection and data privacy standards. keywords: blockchain; decentralized; fabric; hyperledger; platform; technologies cache: www-a-look-at-hyperledger-powered-financial-services-solutions-in-action.html plain text: www-a-look-at-hyperledger-powered-financial-services-solutions-in-action.txt item: #2496 of 3327 id: www-a-look-at-hyperledger-powered-financial-services-solutions-in-action?hs_amp=true author: www title: www-a-look-at-hyperledger-powered-financial-services-solutions-in-action?hs_amp=true date: None words: 1100 flesch: 40 summary: The solution, which is powered Hyperledger Fabric, enables self-sovereign instant KYC data sharing, with full control in the users’ hands in full compliance with international data protection and data privacy standards. Built with Hyperledger Fabric at its core, SECURUS significantly reduces the effort and cost of manual reconciliation and avoids human errors or fraud impacting regulatory compliance, reinsurance accounting and profitability. keywords: blockchain; fabric; hyperledger; platform cache: www-a-look-at-hyperledger-powered-financial-services-solutions-in-action?hs_amp=true.html plain text: www-a-look-at-hyperledger-powered-financial-services-solutions-in-action?hs_amp=true.txt item: #2497 of 3327 id: www-a-message-on-why-localization-matters-from-the-new-hyperledger-japan-chapter author: www title: www-a-message-on-why-localization-matters-from-the-new-hyperledger-japan-chapter date: None words: 1002 flesch: 47 summary: The chapter leaders are planning to bring more and more useful information about Hyperledger projects to the Japan Chapter wiki, so it will become easier for Hyperledger newbies to find out the information (technologies, use cases, etc.). All blockchain and Hyperledger enthusiasts in Japan, please come join Hyperledger Japan Chapter! keywords: chapter; hyperledger; japan; projects cache: www-a-message-on-why-localization-matters-from-the-new-hyperledger-japan-chapter.html plain text: www-a-message-on-why-localization-matters-from-the-new-hyperledger-japan-chapter.txt item: #2498 of 3327 id: www-a-year-of-milestones-lets-take-a-look-at-2024 author: www title: www-a-year-of-milestones-lets-take-a-look-at-2024 date: None words: 2491 flesch: 34 summary: Read: Staff Corner: The importance of maintainers and contributors at LF Decentralized Trust An inspiring lineup of new members  In 2024, we were thrilled to welcome an inspiring lineup of 25 new members to the community and to upgrade Hedera Foundation to Premier Membership and Stellar Development Foundation to General Membership. How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Staff Corner A Year of Milestones: Let’s Take a Look at 2024 Daniela Barbosa, General Manager of Decentralized Technologies at the Linux Foundation and Executive Director of LF Decentralized Trust | Dec 20, 2024 2024 was an eventful year around our global community filled with major project developments and introductions, member and deployments news, non-stop events, and high levels of innovation and energy around the world. keywords: community; decentralized; foundation; hyperledger; new; projects; technologies; trust cache: www-a-year-of-milestones-lets-take-a-look-at-2024.html plain text: www-a-year-of-milestones-lets-take-a-look-at-2024.txt item: #2499 of 3327 id: www-a-year-of-milestones-lets-take-a-look-at-2024?hs_amp=true author: www title: www-a-year-of-milestones-lets-take-a-look-at-2024?hs_amp=true date: None words: 2180 flesch: 36 summary: Read: Staff Corner: The importance of maintainers and contributors at LF Decentralized Trust An inspiring lineup of new members  In 2024, we were thrilled to welcome an inspiring lineup of 25 new members to the community and to upgrade Hedera Foundation to Premier Membership and Stellar Development Foundation to General Membership. A Year of Milestones: Let’s Take a Look at 2024 Blog | LF Decentralized Trust A Year of Milestones: Let’s Take a Look at 2024 Written by Daniela Barbosa, General Manager of Decentralized Technologies at the Linux Foundation and Executive Director of LF Decentralized Trust | Dec 20, 2024 4:52:26 PM 2024 was an eventful year around our global community filled with major project developments and introductions, member and deployments news, non-stop events, and high levels of innovation and energy around the world. keywords: community; decentralized; hyperledger; new; projects; trust cache: www-a-year-of-milestones-lets-take-a-look-at-2024?hs_amp=true.html plain text: www-a-year-of-milestones-lets-take-a-look-at-2024?hs_amp=true.txt item: #2500 of 3327 id: www-abhishek-ranjan-ajitesh-kumar-soni-ashna-p-s-riddhi-ravindra-katarki-sahilsher-singh-and-siddhant-prateek-mahanayak author: www title: www-abhishek-ranjan-ajitesh-kumar-soni-ashna-p-s-riddhi-ravindra-katarki-sahilsher-singh-and-siddhant-prateek-mahanayak date: None words: 543 flesch: 19 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Mentorship Program | Hyperledger Fabric Hyperledger Collaborative Learning Spotlight: BiniBFT - An Optimized BFT on Fabric WHAT WE WORKED ON: Read More Abhishek Ranjan, Ajitesh Kumar Soni, Ashna P S, Riddhi Ravindra Katarki, Sahilsher Singh, and Siddhant Prateek Mahanayak | Mar 5, 2024 keywords: blog; decentralized; hyperledger; technologies cache: www-abhishek-ranjan-ajitesh-kumar-soni-ashna-p-s-riddhi-ravindra-katarki-sahilsher-singh-and-siddhant-prateek-mahanayak.html plain text: www-abhishek-ranjan-ajitesh-kumar-soni-ashna-p-s-riddhi-ravindra-katarki-sahilsher-singh-and-siddhant-prateek-mahanayak.txt item: #2501 of 3327 id: www-aditya-joshi-walmart author: www title: www-aditya-joshi-walmart date: None words: 530 flesch: 21 summary: Next page > Submit a blog Blog guidelines RSS Hyperledger Bevel | Hyperledger Community | Labs | Mentorship Program My 5-Year Journey with the Hyperledger Community As a technology enthusiast, I have always been fascinated by the latest developments in this field... Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page keywords: blog; decentralized; hyperledger; technologies cache: www-aditya-joshi-walmart.html plain text: www-aditya-joshi-walmart.txt item: #2502 of 3327 id: www-ajay-jadhav-credebl-maintainer author: www title: www-ajay-jadhav-credebl-maintainer date: None words: 582 flesch: 10 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Read More Ajay Jadhav, CREDEBL Maintainer | Mar 26, 2025 CREDEBL CREDEBL Becomes an LF Decentralized Trust Project, Advancing Decentralized Identity and Verifiable Credentials for a Secure Digital Future We are excited to announce that CREDEBL, the leading platform in Decentralized Identity (DID) and Verifiable Credentials (VC) management, developed and maintained by the AYANWORKS... Read More Ajay Jadhav, CREDEBL Maintainer | Feb 5, 2025 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; credebl; decentralized; hyperledger cache: www-ajay-jadhav-credebl-maintainer.html plain text: www-ajay-jadhav-credebl-maintainer.txt item: #2503 of 3327 id: www-akanksha-rani author: www title: www-akanksha-rani date: None words: 519 flesch: 13 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Mentorship Program Hyperledger Mentorship Spotlight: Hyperledger Onboarding Mentor/Mentee Program In the expansive realm of Hyperledger, my journey as a mentee in the Hyperledger Onboarding... keywords: blog; decentralized; hyperledger; technologies cache: www-akanksha-rani.html plain text: www-akanksha-rani.txt item: #2504 of 3327 id: www-ali-emdad-ph-d author: www title: www-ali-emdad-ph-d date: None words: 526 flesch: 10 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Finance Celebrating Black History Month: Advancing FinTech and Blockchain Innovation at HBCUs As we celebrate Black History Month, we reflect on the remarkable strides that Black Colleges and... Read More Ali Emdad, Ph.D | Feb 25, 2025 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-ali-emdad-ph-d.html plain text: www-ali-emdad-ph-d.txt item: #2505 of 3327 id: www-all-are-welcome-here author: www title: www-all-are-welcome-here date: None words: 1147 flesch: 55 summary: Back in January of 2016 Sawtooth and Fabric were both on the horizon followed shortly by Iroha, but we wouldn’t have predicted that we would have Hyperledger Burrow and Hyperledger Indy – two projects that bear no resemblance to each other. How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog | Hyperledger Burrow All Are Welcome Here Hyperledger | Dec 3, 2018 A Minneapolis coffee shop that has fueled or at least caffeinated a lot of Hyperledger commits. keywords: code; decentralized; hyperledger; projects cache: www-all-are-welcome-here.html plain text: www-all-are-welcome-here.txt item: #2506 of 3327 id: www-all-are-welcome-here?hs_amp=true author: www title: www-all-are-welcome-here?hs_amp=true date: None words: 836 flesch: 65 summary: Back in January of 2016 Sawtooth and Fabric were both on the horizon followed shortly by Iroha, but we wouldn’t have predicted that we would have Hyperledger Burrow and Hyperledger Indy – two projects that bear no resemblance to each other. One of the first things people learn when coming to Hyperledger is that Hyperledger isn’t, like it’s name may imply, a ledger. keywords: hyperledger; projects cache: www-all-are-welcome-here?hs_amp=true.html plain text: www-all-are-welcome-here?hs_amp=true.txt item: #2507 of 3327 id: www-alvaro-picazo-hyperledger-bevel-maintainer author: www title: www-alvaro-picazo-hyperledger-bevel-maintainer date: None words: 533 flesch: 19 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Hyperledger Bevel | Besu Using Hyperledger Bevel to add a privacy layer to permissioned Besu networks In the business world, data consistency is essential, but so is data privacy and control over who... Read More Alvaro Picazo, Hyperledger Bevel Maintainer | Nov 14, 2024 keywords: blog; decentralized; hyperledger; technologies cache: www-alvaro-picazo-hyperledger-bevel-maintainer.html plain text: www-alvaro-picazo-hyperledger-bevel-maintainer.txt item: #2508 of 3327 id: www-ameziane-hamlat-karim-taam-and-the-besu-team-at-consensys author: www title: www-ameziane-hamlat-karim-taam-and-the-besu-team-at-consensys date: None words: 533 flesch: 10 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Besu Introducing Parallel Transaction Execution in Hyperledger Besu I. Introduction In our continuous effort to enhance the performance of Hyperledger Besu as an... keywords: blog; decentralized; hyperledger; technologies cache: www-ameziane-hamlat-karim-taam-and-the-besu-team-at-consensys.html plain text: www-ameziane-hamlat-karim-taam-and-the-besu-team-at-consensys.txt item: #2509 of 3327 id: www-an-innovative-blockchain-solution-powered-by-hyperledger-fabric-helps-banks-implement-defi-services-in-days author: www title: www-an-innovative-blockchain-solution-powered-by-hyperledger-fabric-helps-banks-implement-defi-services-in-days date: None words: 912 flesch: 40 summary: There are still lots of issues to solve before we can celebrate the coming of a new digital banking age: Customers of even the same bank can’t directly interact with each other; Cross-border transfers remain expensive and ridden with middlemen; Bank users can’t convert fiat into crypto and back; and New banking services take ages to develop, approve and introduce. The problem is that developing a crypto-fiat DeFi platform from scratch is expensive and requires expertise that most banks’ IT teams simply don’t have.  keywords: banks; cryptoenter; defi; fiat cache: www-an-innovative-blockchain-solution-powered-by-hyperledger-fabric-helps-banks-implement-defi-services-in-days.html plain text: www-an-innovative-blockchain-solution-powered-by-hyperledger-fabric-helps-banks-implement-defi-services-in-days.txt item: #2510 of 3327 id: www-an-innovative-blockchain-solution-powered-by-hyperledger-fabric-helps-banks-implement-defi-services-in-days?hs_amp=true author: www title: www-an-innovative-blockchain-solution-powered-by-hyperledger-fabric-helps-banks-implement-defi-services-in-days?hs_amp=true date: None words: 602 flesch: 47 summary: There are still lots of issues to solve before we can celebrate the coming of a new digital banking age: Customers of even the same bank can’t directly interact with each other; Cross-border transfers remain expensive and ridden with middlemen; Bank users can’t convert fiat into crypto and back; and New banking services take ages to develop, approve and introduce. The problem is that developing a crypto-fiat DeFi platform from scratch is expensive and requires expertise that most banks’ IT teams simply don’t have.  keywords: banks; defi cache: www-an-innovative-blockchain-solution-powered-by-hyperledger-fabric-helps-banks-implement-defi-services-in-days?hs_amp=true.html plain text: www-an-innovative-blockchain-solution-powered-by-hyperledger-fabric-helps-banks-implement-defi-services-in-days?hs_amp=true.txt item: #2511 of 3327 id: www-an-overview-of-self-sovereign-identity-the-use-case-at-the-core-of-hyperledger-indy author: www title: www-an-overview-of-self-sovereign-identity-the-use-case-at-the-core-of-hyperledger-indy date: None words: 1286 flesch: 47 summary: Traditional, identity systems have a single identity provider (IdP) administering an identity system for their own purposes. Many companies don’t or can’t use social login and so the system of fractured administrative identity systems remains. keywords: credentials; identity; internet; use cache: www-an-overview-of-self-sovereign-identity-the-use-case-at-the-core-of-hyperledger-indy.html plain text: www-an-overview-of-self-sovereign-identity-the-use-case-at-the-core-of-hyperledger-indy.txt item: #2512 of 3327 id: www-andor-kesselman-darrell-odonnell-antti-kettunen-and-drummond-reed-editors-of-the-trqp-spec author: www title: www-andor-kesselman-darrell-odonnell-antti-kettunen-and-drummond-reed-editors-of-the-trqp-spec date: None words: 547 flesch: 21 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page The Trust Registry Task Force (TRTF) at Trust Over IP... Read More Andor Kesselman, Darrell O’Donnell, Antti Kettunen, and Drummond Reed, editors of the TRQP spec | Apr 7, 2025 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; trust cache: www-andor-kesselman-darrell-odonnell-antti-kettunen-and-drummond-reed-editors-of-the-trqp-spec.html plain text: www-andor-kesselman-darrell-odonnell-antti-kettunen-and-drummond-reed-editors-of-the-trqp-spec.txt item: #2513 of 3327 id: www-andré-augusto-ph-d-student-instituto-superior-técnico-lisbon-portugal author: www title: www-andré-augusto-ph-d-student-instituto-superior-técnico-lisbon-portugal date: None words: 534 flesch: 17 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Hyperledger Cacti | Mentorship Program | Hyperledger Fabric Hyperledger Mentorship Spotlight: Fabric-Ethereum token bridging What did you work on? keywords: blog; decentralized; hyperledger; project cache: www-andré-augusto-ph-d-student-instituto-superior-técnico-lisbon-portugal.html plain text: www-andré-augusto-ph-d-student-instituto-superior-técnico-lisbon-portugal.txt item: #2514 of 3327 id: www-announcing-hyperledger-anoncreds-open-source-open-specification-privacy-preserving-verifiable-credentials author: www title: www-announcing-hyperledger-anoncreds-open-source-open-specification-privacy-preserving-verifiable-credentials date: None words: 900 flesch: 27 summary: The project consists of: The AnonCreds Specification, managed by the Hyperledger AnonCreds Specification Working Group and with the potential of being submitted to an appropriate Standards organization Ledger/Verifiable Data Registry-agnostic, open source code implementations of the AnonCreds specification, suitable for use with Hyperledger Aries and non-Aries agents Guidance for creating ledger-specific AnonCreds Methods to write and resolve AnonCreds objects for specific ledgers Documentation on AnonCreds suitable for all audiences, from business audiences to cryptographers A test suite to verify adherence to the AnonCreds specification and the interoperability of AnonCreds implementations. Hyperledger AnonCreds is ledger-agnostic and client-agnostic. keywords: anoncreds; hyperledger; project; specification cache: www-announcing-hyperledger-anoncreds-open-source-open-specification-privacy-preserving-verifiable-credentials.html plain text: www-announcing-hyperledger-anoncreds-open-source-open-specification-privacy-preserving-verifiable-credentials.txt item: #2515 of 3327 id: www-announcing-hyperledger-anoncreds-open-source-open-specification-privacy-preserving-verifiable-credentials?hs_amp=true author: www title: www-announcing-hyperledger-anoncreds-open-source-open-specification-privacy-preserving-verifiable-credentials?hs_amp=true date: None words: 589 flesch: 28 summary: The project consists of: The AnonCreds Specification, managed by the Hyperledger AnonCreds Specification Working Group and with the potential of being submitted to an appropriate Standards organization Ledger/Verifiable Data Registry-agnostic, open source code implementations of the AnonCreds specification, suitable for use with Hyperledger Aries and non-Aries agents Guidance for creating ledger-specific AnonCreds Methods to write and resolve AnonCreds objects for specific ledgers Documentation on AnonCreds suitable for all audiences, from business audiences to cryptographers A test suite to verify adherence to the AnonCreds specification and the interoperability of AnonCreds implementations. Hyperledger AnonCreds is ledger-agnostic and client-agnostic. keywords: anoncreds; hyperledger cache: www-announcing-hyperledger-anoncreds-open-source-open-specification-privacy-preserving-verifiable-credentials?hs_amp=true.html plain text: www-announcing-hyperledger-anoncreds-open-source-open-specification-privacy-preserving-verifiable-credentials?hs_amp=true.txt item: #2516 of 3327 id: www-announcing-hyperledger-aries-infrastructure-supporting-interoperable-identity-solutions author: www title: www-announcing-hyperledger-aries-infrastructure-supporting-interoperable-identity-solutions date: None words: 1265 flesch: 35 summary: Hyperledger Aries is related to both Hyperledger Indy, which provides a resolver implementation, and Hyperledger Ursa, which it uses for cryptographic functionality. One of the main purposes of this project is to change the client layers in Hyperledger Indy to be interoperable with other identity projects. keywords: aries; hyperledger; identity; indy cache: www-announcing-hyperledger-aries-infrastructure-supporting-interoperable-identity-solutions.html plain text: www-announcing-hyperledger-aries-infrastructure-supporting-interoperable-identity-solutions.txt item: #2517 of 3327 id: www-announcing-hyperledger-besu author: www title: www-announcing-hyperledger-besu date: None words: 1662 flesch: 45 summary: What is an “Ethereum Client”? Hyperledger Besu is one of several Ethereum clients. By creating clean interfaces between elements within the client (e.g., networking, storage, EVM, etc.), we believe enterprises will have a much easier time configuring Ethereum to meet their needs while also creating opportunities for other Hyperledger projects to integrate and use elements of Besu’s codebase. keywords: besu; client; ethereum; hyperledger; network; protocol cache: www-announcing-hyperledger-besu.html plain text: www-announcing-hyperledger-besu.txt item: #2518 of 3327 id: www-announcing-hyperledger-besu-1-5-available-now author: www title: www-announcing-hyperledger-besu-1-5-available-now date: None words: 816 flesch: 47 summary: “Hands-on with Hyperledger Besu” is a guided introduction to Besu, hosted by some of the people who build, maintain, train, and work with the Ethereum client. Those looking to interact one on one with Besu developers and contributors can join the conversation on Rocketchat at #besu, or join our regular contributor calls. keywords: besu; decentralized; foundation; hyperledger cache: www-announcing-hyperledger-besu-1-5-available-now.html plain text: www-announcing-hyperledger-besu-1-5-available-now.txt item: #2519 of 3327 id: www-announcing-hyperledger-besu-20-10-0 author: www title: www-announcing-hyperledger-besu-20-10-0 date: None words: 1064 flesch: 48 summary: You might have noticed that the versioning for this quarterly release is a little different than prior Hyperledger Besu releases. Announcing Hyperledger Besu 20.10.0 – Hyperledger Foundation 2025 Update: Off to a Fast Start! keywords: besu; hyperledger; project; release cache: www-announcing-hyperledger-besu-20-10-0.html plain text: www-announcing-hyperledger-besu-20-10-0.txt item: #2520 of 3327 id: www-announcing-hyperledger-besu-20-10-0?hs_amp=true author: www title: www-announcing-hyperledger-besu-20-10-0?hs_amp=true date: None words: 756 flesch: 57 summary: You might have noticed that the versioning for this quarterly release is a little different than prior Hyperledger Besu releases. Project Release Old Release Versioning New Calver Release Versioning Hyperledger Besu  Hyperledger Besu Q4 Release Candidate 1 1.6.0-RC1 20.10.0-RC1 Hyperledger Besu  Hyperledger Besu Q4 Release Candidate 2 1.6.0-RC2 20.10.0-RC2 Hyperledger Besu  Hyperledger Besu Q4 2020 Quarterly Release 1.6.0 20.10.0 Hyperledger Besu  Hyperledger Besu subsequent bi-weekly release  1.6.1 20.10.1 Now to share what is included in the latest release. keywords: besu; hyperledger cache: www-announcing-hyperledger-besu-20-10-0?hs_amp=true.html plain text: www-announcing-hyperledger-besu-20-10-0?hs_amp=true.txt item: #2521 of 3327 id: www-announcing-hyperledger-besu-v1-4-available-now author: www title: www-announcing-hyperledger-besu-v1-4-available-now date: None words: 1255 flesch: 43 summary: Key Features in 1.4 Plugin APIs  Hyperledger Besu v1.4 also exposes a plugin API, allowing anyone to write custom plugins for Besu and enabling users to take data from any Besu network, public or permissioned, and feed it into the rest of their applications and systems easily. Multi-Tenancy – Secure Private Transactions in a shared environment  Hyperledger Besu v1.4 will be able to run in a “Multi-tenant environment,” allowing a number of users to use the same Ethereum node to connect to the network. keywords: besu; hyperledger; key; use; v1.4 cache: www-announcing-hyperledger-besu-v1-4-available-now.html plain text: www-announcing-hyperledger-besu-v1-4-available-now.txt item: #2522 of 3327 id: www-announcing-hyperledger-identus-a-new-decentralized-identity-applications-project author: www title: www-announcing-hyperledger-identus-a-new-decentralized-identity-applications-project date: None words: 1097 flesch: 41 summary: Announcing Hyperledger Identus, a new decentralized identity applications project 2025 What is Hyperledger Identus? keywords: decentralized; hyperledger; identity; identus; project cache: www-announcing-hyperledger-identus-a-new-decentralized-identity-applications-project.html plain text: www-announcing-hyperledger-identus-a-new-decentralized-identity-applications-project.txt item: #2523 of 3327 id: www-announcing-hyperledger-identus-a-new-decentralized-identity-applications-project?hs_amp=true author: www title: www-announcing-hyperledger-identus-a-new-decentralized-identity-applications-project?hs_amp=true date: None words: 783 flesch: 46 summary: Announcing Hyperledger Identus, a new decentralized identity applications project Blog | LF Decentralized Trust Announcing Hyperledger Identus, a new decentralized identity applications project Written by Peter Vielhaber, Hyperledger Identus Contributor | May 22, 2024 3:00:00 PM We are thrilled to share the latest addition to the Hyperledger family - Hyperledger Identus. What is Hyperledger Identus? keywords: hyperledger; identity; identus cache: www-announcing-hyperledger-identus-a-new-decentralized-identity-applications-project?hs_amp=true.html plain text: www-announcing-hyperledger-identus-a-new-decentralized-identity-applications-project?hs_amp=true.txt item: #2524 of 3327 id: www-announcing-hyperledger-iroha-2 author: www title: www-announcing-hyperledger-iroha-2 date: None words: 1355 flesch: 39 summary: What is New in Hyperledger Iroha 2? Building on the lessons learned from its predecessor, Iroha 2 represents a significant leap forward in the evolution of the Hyperledger Iroha blockchain platform, offering a comprehensive overhaul of its architecture, design and functionality.  What is Hyperledger Iroha 2 Ideal for? Hyperledger Iroha 2 is ideal for businesses and developers looking to implement blockchain solutions without the complexity usually associated with such technologies. keywords: blockchain; hyperledger; iroha; use cache: www-announcing-hyperledger-iroha-2.html plain text: www-announcing-hyperledger-iroha-2.txt item: #2525 of 3327 id: www-announcing-hyperledger-iroha-2?hs_amp=true author: www title: www-announcing-hyperledger-iroha-2?hs_amp=true date: None words: 1044 flesch: 44 summary: Announcing Hyperledger Iroha 2 Blog | LF Decentralized Trust Announcing Hyperledger Iroha 2 Written by Hyperledger Iroha maintainers | Feb 5, 2025 1:30:00 AM Hyperledger Iroha 2 is an innovative blockchain framework aimed to be robust, fast, and efficient for digital asset and identity use cases. What is New in Hyperledger Iroha 2? Building on the lessons learned from its predecessor, Iroha 2 represents a significant leap forward in the evolution of the Hyperledger Iroha blockchain platform, offering a comprehensive overhaul of its architecture, design and functionality.  keywords: hyperledger; iroha cache: www-announcing-hyperledger-iroha-2?hs_amp=true.html plain text: www-announcing-hyperledger-iroha-2?hs_amp=true.txt item: #2526 of 3327 id: www-announcing-paladin-an-lf-decentralized-trust-lab-for-programmable-privacy-on-evm author: www title: www-announcing-paladin-an-lf-decentralized-trust-lab-for-programmable-privacy-on-evm date: None words: 2945 flesch: 46 summary: However, for enterprises, there is one challenge that must be overcome before production adoption is possible at scale: transaction privacy. Bringing it all together By bringing together privacy-preserving tokens and EVM privacy groups for programmable workflow, on top of a programmable EVM underlying blockchain, Paladin provides flexible options for privacy while still retaining the ecosystem programmability that the Ethereum community is famous for. keywords: blockchain; decentralized; evm; paladin; privacy; tokens; transaction; trust cache: www-announcing-paladin-an-lf-decentralized-trust-lab-for-programmable-privacy-on-evm.html plain text: www-announcing-paladin-an-lf-decentralized-trust-lab-for-programmable-privacy-on-evm.txt item: #2527 of 3327 id: www-announcing-paladin-an-lf-decentralized-trust-lab-for-programmable-privacy-on-evm?hs_amp=true author: www title: www-announcing-paladin-an-lf-decentralized-trust-lab-for-programmable-privacy-on-evm?hs_amp=true date: None words: 2635 flesch: 49 summary: However, for enterprises, there is one challenge that must be overcome before production adoption is possible at scale: transaction privacy. Because all privacy domains create blockchain transactions on the underlying shared EVM ledger, they can be composed in endless ways with each other and with other existing tokens and contracts on the EVM. keywords: blockchain; evm; paladin; privacy; tokens; transaction cache: www-announcing-paladin-an-lf-decentralized-trust-lab-for-programmable-privacy-on-evm?hs_amp=true.html plain text: www-announcing-paladin-an-lf-decentralized-trust-lab-for-programmable-privacy-on-evm?hs_amp=true.txt item: #2528 of 3327 id: www-announcing-the-2023-hyperledger-technical-oversight-committee author: www title: www-announcing-the-2023-hyperledger-technical-oversight-committee date: None words: 2003 flesch: 53 summary: Hyperledger Foundation hosts a wide range of technical projects related to blockchain technology and multiparty systems. In addition, the identity ecosystem has found its sweet spot in Hyperledger Foundation. keywords: community; foundation; hyperledger; project; technical; toc cache: www-announcing-the-2023-hyperledger-technical-oversight-committee.html plain text: www-announcing-the-2023-hyperledger-technical-oversight-committee.txt item: #2529 of 3327 id: www-announcing-the-2023-hyperledger-technical-oversight-committee?hs_amp=true author: www title: www-announcing-the-2023-hyperledger-technical-oversight-committee?hs_amp=true date: None words: 1693 flesch: 57 summary: Announcing the 2023 Hyperledger Technical Oversight Committee – Hyperledger Foundation Blog | LF Decentralized Trust Announcing the 2023 Hyperledger Technical Oversight Committee – Hyperledger Foundation Written by Hyperledger | Jan 12, 2023 6:00:00 AM As we turned the page to 2023, the developer community and Hyperledger Foundation Governing Board selected this year’s Technical Oversight Committee (TOC). Hyperledger Foundation hosts a wide range of technical projects related to blockchain technology and multiparty systems. keywords: community; foundation; hyperledger; technical; toc cache: www-announcing-the-2023-hyperledger-technical-oversight-committee?hs_amp=true.html plain text: www-announcing-the-2023-hyperledger-technical-oversight-committee?hs_amp=true.txt item: #2530 of 3327 id: www-announcing-the-upcoming-elections-for-end-user-and-community-seats-on-the-hiero-technical-steering-committee-tsc author: www title: www-announcing-the-upcoming-elections-for-end-user-and-community-seats-on-the-hiero-technical-steering-committee-tsc date: None words: 975 flesch: 42 summary: We also encourage community members to attend the weekly Hiero TSC and the Hiero bi-weekly Community meetings, which are open to all. How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Governance | Hiero Upcoming Elections for End User and Community Seats on the Hiero Technical Steering Committee (TSC) Hiero Community | Mar 18, 2025 We are excited to announce the upcoming elections for two vital positions on the Hiero Technical Steering Committee (TSC): the End User Seat and the Contributor Seat. keywords: community; end; hiero cache: www-announcing-the-upcoming-elections-for-end-user-and-community-seats-on-the-hiero-technical-steering-committee-tsc.html plain text: www-announcing-the-upcoming-elections-for-end-user-and-community-seats-on-the-hiero-technical-steering-committee-tsc.txt item: #2531 of 3327 id: www-announcing-the-upcoming-elections-for-end-user-and-community-seats-on-the-hiero-technical-steering-committee-tsc?hs_amp=true author: www title: www-announcing-the-upcoming-elections-for-end-user-and-community-seats-on-the-hiero-technical-steering-committee-tsc?hs_amp=true date: None words: 663 flesch: 49 summary: We also encourage community members to attend the weekly Hiero TSC and the Hiero bi-weekly Community meetings, which are open to all. Blog | LF Decentralized Trust Upcoming Elections for End User and Community Seats on the Hiero Technical Steering Committee (TSC) Written by Hiero Community | Mar 18, 2025 5:01:56 PM We are excited to announce the upcoming elections for two vital positions on the Hiero Technical Steering Committee (TSC): the End User Seat and the Contributor Seat. keywords: end; hiero cache: www-announcing-the-upcoming-elections-for-end-user-and-community-seats-on-the-hiero-technical-steering-committee-tsc?hs_amp=true.html plain text: www-announcing-the-upcoming-elections-for-end-user-and-community-seats-on-the-hiero-technical-steering-committee-tsc?hs_amp=true.txt item: #2532 of 3327 id: www-answering-the-fdas-call-ledgerdomains-hyperledger-fabric-based-bruinchain-improves-tracking-and-tracing-of-prescription-drugs author: www title: www-answering-the-fdas-call-ledgerdomains-hyperledger-fabric-based-bruinchain-improves-tracking-and-tracing-of-prescription-drugs date: None words: 811 flesch: 35 summary: Answering the FDA’s call: LedgerDomain’s Hyperledger Fabric-based BRUINchain improves tracking and tracing of prescription drugs – Hyperledger Foundation 2025 Update: Off to a Fast Start!  Part of that effort is the Drug Supply Chain Security Act (DSCSA), an ongoing, decade-long effort to track and trace prescription drugs in the United States. keywords: bruinchain; decentralized; hyperledger; ledgerdomain cache: www-answering-the-fdas-call-ledgerdomains-hyperledger-fabric-based-bruinchain-improves-tracking-and-tracing-of-prescription-drugs.html plain text: www-answering-the-fdas-call-ledgerdomains-hyperledger-fabric-based-bruinchain-improves-tracking-and-tracing-of-prescription-drugs.txt item: #2533 of 3327 id: www-applications-open-2025-lf-decentralized-trust-mentorship-program author: www title: www-applications-open-2025-lf-decentralized-trust-mentorship-program date: None words: 1483 flesch: 38 summary: It introduces the newest generation of talent to the important work of open source development, drives innovation across projects and communities, and opens doors for those who might not otherwise have a way into this development community and career path. Applications Open: 2025 LF Decentralized Trust Mentorship Program 2025 Update: Off to a Fast Start! keywords: decentralized; development; mentorship; program; trust cache: www-applications-open-2025-lf-decentralized-trust-mentorship-program.html plain text: www-applications-open-2025-lf-decentralized-trust-mentorship-program.txt item: #2534 of 3327 id: www-applications-open-2025-lf-decentralized-trust-mentorship-program?hs_amp=true author: www title: www-applications-open-2025-lf-decentralized-trust-mentorship-program?hs_amp=true date: None words: 1172 flesch: 42 summary: Applications Open: 2025 LF Decentralized Trust Mentorship Program Blog | LF Decentralized Trust Applications Open: 2025 LF Decentralized Trust Mentorship Program Written by LF Decentralized Trust | Apr 15, 2025 2:38:35 PM It introduces the newest generation of talent to the important work of open source development, drives innovation across projects and communities, and opens doors for those who might not otherwise have a way into this development community and career path. keywords: development; mentorship; trust cache: www-applications-open-2025-lf-decentralized-trust-mentorship-program?hs_amp=true.html plain text: www-applications-open-2025-lf-decentralized-trust-mentorship-program?hs_amp=true.txt item: #2535 of 3327 id: www-apply-now-for-the-annual-hyperledger-mentorship-program author: www title: www-apply-now-for-the-annual-hyperledger-mentorship-program date: None words: 2181 flesch: 34 summary: - Piash Tanjin, previous mentee and a co-mentor for this year's Learning Tokens for Hyperledger Community Building project For more from the mentors and past mentees about the application process as well as what to expect and how to make the most of the program, watch this meetup panel:   : Enhancing Android Support with Updated web3j-android Integration Primary Focus: Coding, Documentation The Hyperledger Web3j-android library is pivotal for developers integrating Android applications with Ethereum blockchain, leveraging the robust capabilities of Hyperledger web3j in a mobile context. keywords: android; development; documentation; hyperledger; mentorship; program; project; web3j cache: www-apply-now-for-the-annual-hyperledger-mentorship-program.html plain text: www-apply-now-for-the-annual-hyperledger-mentorship-program.txt item: #2536 of 3327 id: www-apply-now-for-the-annual-hyperledger-mentorship-program?hs_amp=true author: www title: www-apply-now-for-the-annual-hyperledger-mentorship-program?hs_amp=true date: None words: 1870 flesch: 36 summary: - Koosha E. Khorasani, previous mentee and a co-mentor for this year's Integrating Substrate Framework with Hyperledger Fabric for Enhanced Interoperability project Being a mentee taught me the value of following guidance while also engaging in independent research for optimal results, enabling me to further discuss the pros and cons of each approach taken with my mentor. The Hyperledger Labs CC-Tools library offers several features that facilitate the journey of learning, development and deployment of chaincode for Hyperledger Fabric in Golang. keywords: android; development; documentation; hyperledger; mentorship; project cache: www-apply-now-for-the-annual-hyperledger-mentorship-program?hs_amp=true.html plain text: www-apply-now-for-the-annual-hyperledger-mentorship-program?hs_amp=true.txt item: #2537 of 3327 id: www-archana-arige-and-udhayakumari-p author: www title: www-archana-arige-and-udhayakumari-p date: None words: 514 flesch: 19 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-archana-arige-and-udhayakumari-p.html plain text: www-archana-arige-and-udhayakumari-p.txt item: #2538 of 3327 id: www-aries-connectathon-a-community-driven-event-for-identity-projects-at-hyperledger author: www title: www-aries-connectathon-a-community-driven-event-for-identity-projects-at-hyperledger date: None words: 741 flesch: 38 summary: The first identity-focused project was Hyperledger Indy first launched in 2018, then Hyperledger Ursa later that year. In early 2019, Hyperledger Aries launched to create a shared, reusable, interoperable tool kit for the exchange of verifiable credentials across systems and networks. keywords: aries; event; hyperledger cache: www-aries-connectathon-a-community-driven-event-for-identity-projects-at-hyperledger.html plain text: www-aries-connectathon-a-community-driven-event-for-identity-projects-at-hyperledger.txt item: #2539 of 3327 id: www-aritra-bhaduri author: www title: www-aritra-bhaduri date: None words: 525 flesch: 10 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Hyperledger AnonCreds | Decentralized Identity | Mentorship Program Hyperledger Mentorship Spotlight: Document, Review, and Implement Hyperledger AnonCreds ZKP Cryptographic Primitives Working on the Document, Review, and Implement Hyperledger AnonCreds ZKP Cryptographic... keywords: blog; decentralized; hyperledger; technologies cache: www-aritra-bhaduri.html plain text: www-aritra-bhaduri.txt item: #2540 of 3327 id: www-arun-s-m-vice-chair-hyperledger-toc-and-hart-montgomery-cto-hyperledger-foundation author: www title: www-arun-s-m-vice-chair-hyperledger-toc-and-hart-montgomery-cto-hyperledger-foundation date: None words: 535 flesch: 20 summary: Blog | LF Decentralized Trust | Arun S M, Vice Chair, Hyperledger TOC, and Hart Montgomery, CTO, Hyperledger Foundation 2025 Read More Arun S M, Vice Chair, Hyperledger TOC, and Hart Montgomery, CTO, Hyperledger Foundation | keywords: blog; decentralized; foundation; hyperledger cache: www-arun-s-m-vice-chair-hyperledger-toc-and-hart-montgomery-cto-hyperledger-foundation.html plain text: www-arun-s-m-vice-chair-hyperledger-toc-and-hart-montgomery-cto-hyperledger-foundation.txt item: #2541 of 3327 id: www-arweave-lightpaper author: www title: www-arweave-lightpaper date: 2023-12-26 words: 10160 flesch: 55 summary: 5.3 Deflation and Endowment Value The Arweave network’s endowment removes tokens from cir- culation every time data is uploaded, creating a reserve to pay for data storage over time. The storage purchasing power of the endowment is elastic, changing with the vol- ume of data committed, the cost of data storage, and token value over time. keywords: alice; arweave; block; cost; data; dataset; merkle; miners; network; number; partition; proof; protocol; replicas; root; storage; time cache: www-arweave-lightpaper.pdf plain text: www-arweave-lightpaper.txt item: #2542 of 3327 id: www-assembling-the-future-of-smart-contracts-with-sawtooth-sabre author: www title: www-assembling-the-future-of-smart-contracts-with-sawtooth-sabre date: None words: 2253 flesch: 54 summary: There are three deployment models for smart contracts: Off-chain push: Smart contracts are deployed by pushing them to all nodes from a central authority on the network. Sawtooth Sabre smart contracts use this same method for data storage, which means they can access global state in the same way that transaction processors do. keywords: chain; contracts; hyperledger; sabre; sawtooth; transaction cache: www-assembling-the-future-of-smart-contracts-with-sawtooth-sabre.html plain text: www-assembling-the-future-of-smart-contracts-with-sawtooth-sabre.txt item: #2543 of 3327 id: www-atala-prism author: www title: www-atala-prism date: None words: 525 flesch: 19 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page From online shopping to office visits and... Read More Atala PRISM | Dec 4, 2023 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-atala-prism.html plain text: www-atala-prism.txt item: #2544 of 3327 id: www-bc-digital-trust-government-of-british-columbia-canada author: www title: www-bc-digital-trust-government-of-british-columbia-canada date: None words: 527 flesch: 18 summary: Next page > Submit a blog Blog guidelines RSS Hyperledger AnonCreds | Hyperledger Aries | Project: Hyperledger Indy | Decentralized Identity BC Digital Trust: Leveraging Hyperledger Tools For Digital Trust Read More BC DIGITAL TRUST – GOVERNMENT OF BRITISH COLUMBIA, CANADA | Sep 21, 2023 Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page keywords: blog; decentralized; hyperledger; trust cache: www-bc-digital-trust-government-of-british-columbia-canada.html plain text: www-bc-digital-trust-government-of-british-columbia-canada.txt item: #2545 of 3327 id: www-bc-digital-trust-leveraging-hyperledger-tools-for-digital-trust author: www title: www-bc-digital-trust-leveraging-hyperledger-tools-for-digital-trust date: None words: 1461 flesch: 29 summary: Collaborate with BC Digital Trust   BC Digital Trust leverages Hyperledger components to offer digital trust solutions that enable user-friendly and secure digital interactions on the individual and organizational level.    To build better pathways to digital solutions, reduce project risk, and deliver value incrementally, BC Digital Trust is utilizing an “open-by-default” approach. keywords: digital; government; hyperledger; trust cache: www-bc-digital-trust-leveraging-hyperledger-tools-for-digital-trust.html plain text: www-bc-digital-trust-leveraging-hyperledger-tools-for-digital-trust.txt item: #2546 of 3327 id: www-bc-digital-trust-leveraging-hyperledger-tools-for-digital-trust?hs_amp=true author: www title: www-bc-digital-trust-leveraging-hyperledger-tools-for-digital-trust?hs_amp=true date: None words: 1140 flesch: 31 summary: Collaborate with BC Digital Trust   BC Digital Trust leverages Hyperledger components to offer digital trust solutions that enable user-friendly and secure digital interactions on the individual and organizational level.    To build better pathways to digital solutions, reduce project risk, and deliver value incrementally, BC Digital Trust is utilizing an “open-by-default” approach. keywords: digital; trust cache: www-bc-digital-trust-leveraging-hyperledger-tools-for-digital-trust?hs_amp=true.html plain text: www-bc-digital-trust-leveraging-hyperledger-tools-for-digital-trust?hs_amp=true.txt item: #2547 of 3327 id: www-benchmarking-hyperledger-fabric-2-5-performance author: www title: www-benchmarking-hyperledger-fabric-2-5-performance date: None words: 1616 flesch: 46 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger Caliper | Hyperledger Fabric Benchmarking Hyperledger Fabric 2.5 Performance Dave Kelsey, Hyperledger Caliper Maintainer | Feb 16, 2023 Hyperledger Fabric performance is a question that comes up frequently as users try to compare it to transactional databases or other blockchain platforms in terms of the maximum TPS (Transactions Per Second). Performance Benchmarks In conjunction with the new Performance Considerations documentation, the community has leveraged Hyperledger Caliper for some initial performance benchmarks for Hyperledger Fabric 2.5. keywords: asset; caliper; fabric; hyperledger; tps cache: www-benchmarking-hyperledger-fabric-2-5-performance.html plain text: www-benchmarking-hyperledger-fabric-2-5-performance.txt item: #2548 of 3327 id: www-benchmarking-hyperledger-fabric-2-5-performance?hs_amp=true author: www title: www-benchmarking-hyperledger-fabric-2-5-performance?hs_amp=true date: None words: 1304 flesch: 51 summary: Performance Benchmarks In conjunction with the new Performance Considerations documentation, the community has leveraged Hyperledger Caliper for some initial performance benchmarks for Hyperledger Fabric 2.5. Hyperledger Fabric 2.x has performance improvements over Hyperledger Fabric 1.4. keywords: asset; caliper; fabric; hyperledger cache: www-benchmarking-hyperledger-fabric-2-5-performance?hs_amp=true.html plain text: www-benchmarking-hyperledger-fabric-2-5-performance?hs_amp=true.txt item: #2549 of 3327 id: www-best-practices-and-lessons-learned-from-hyperledger-besu-establishing-a-maintainer-process author: www title: www-best-practices-and-lessons-learned-from-hyperledger-besu-establishing-a-maintainer-process date: None words: 967 flesch: 43 summary: Other Hyperledger projects: Currently the Hyperledger projects have different approaches for managing their maintainers. Why Maintainer Governance is Important Maintainers of open source projects are the leaders and direction-setters for the projects. keywords: besu; hyperledger; maintainer cache: www-best-practices-and-lessons-learned-from-hyperledger-besu-establishing-a-maintainer-process.html plain text: www-best-practices-and-lessons-learned-from-hyperledger-besu-establishing-a-maintainer-process.txt item: #2550 of 3327 id: www-besu author: www title: www-besu date: None words: 1394 flesch: 28 summary: Today, Poste... Read More Hyperledger | May 19, 2021 Besu Announcing Hyperledger Besu 20.10.0 This release includes new versioning and mainnet-focused advancements Read More Jessica Rampen | Nov 4, 2020 Besu Hyperledger Besu 1.5 Performance Enhancements Overview Over the past quarter, the Hyperledger Besu team has been hard at work improving performance across many fronts, from adding support for native encryption libraries to... Read More Jessica Rampen | Aug 6, 2020 1 2 However, the... Read More the Besu Maintainers | Sep 24, 2024 Besu Introducing Parallel Transaction Execution in Hyperledger Besu I. Introduction In our continuous effort to enhance the performance of Hyperledger Besu as an execution client, we are excited to introduce one of the most significant... Read More Ameziane Hamlat, Karim Taam, and the Besu Team at Consensys | Jul 31, 2024 Besu | Finance and Business Technology Why Hyperledger Besu is a Top Choice for Financial Use Cases Hyperledger Besu has emerged as a preferred runtime for EVM-based financial initiatives worldwide. keywords: besu; case; decentralized; hyperledger; trust cache: www-besu.html plain text: www-besu.txt item: #2551 of 3327 id: www-blockchain-and-the-energy-transition-creating-the-platform-for-a-sustainable-oil-and-gas-industry author: www title: www-blockchain-and-the-energy-transition-creating-the-platform-for-a-sustainable-oil-and-gas-industry date: None words: 1422 flesch: 58 summary: Carbon capture and storage is a proven technology that certainly removes CO2 from the air, but it could also be used to extract more oil, which would cause more emissions. Where Next? Oil is the world’s most traded commodity.  keywords: blockchain; gas; industry; oil cache: www-blockchain-and-the-energy-transition-creating-the-platform-for-a-sustainable-oil-and-gas-industry.html plain text: www-blockchain-and-the-energy-transition-creating-the-platform-for-a-sustainable-oil-and-gas-industry.txt item: #2552 of 3327 id: www-blockchain-as-the-next-artificial-intelligence-enabler-2 author: www title: www-blockchain-as-the-next-artificial-intelligence-enabler-2 date: None words: 1614 flesch: 46 summary: (Consumer pays AI service provider if provider was right, but, if provider was wrong,maybe consumer should get paid?). The end result would be an ecosystem with a massive amount of AI services that are actually mini-businesses, each with its own community of equity holders. keywords: blockchain; quality; service; tech cache: www-blockchain-as-the-next-artificial-intelligence-enabler-2.html plain text: www-blockchain-as-the-next-artificial-intelligence-enabler-2.txt item: #2553 of 3327 id: www-blockchain-automation-framework-the-journey author: www title: www-blockchain-automation-framework-the-journey date: None words: 1503 flesch: 42 summary: Now, as a Hyperledger Labs project, Blockchain Automation framework delivers automation for rapidly deploying production ready DLT platforms on a chosen cloud infrastructure. Blockchain Automation Framework – the journey – Hyperledger Foundation 2025 keywords: automation; blockchain; cloud; dlt; project cache: www-blockchain-automation-framework-the-journey.html plain text: www-blockchain-automation-framework-the-journey.txt item: #2554 of 3327 id: www-blockchain-education-the-keys-to-the-door-of-a-new-business-revolution author: www title: www-blockchain-education-the-keys-to-the-door-of-a-new-business-revolution date: None words: 1076 flesch: 38 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog Blockchain Education: The Keys to the Door of a New Business Revolution Jessica Rampen | Nov 24, 2020 The global market for blockchain solutions is set to grow by $18 billion by 2024. With such explosive demand growth for blockchain solutions, an equally increasing supply of top-tier blockchain development talent is needed to meet the needs of some of the world’s largest corporations and organizations. keywords: blockchain; emurgo; hyperledger; solutions cache: www-blockchain-education-the-keys-to-the-door-of-a-new-business-revolution.html plain text: www-blockchain-education-the-keys-to-the-door-of-a-new-business-revolution.txt item: #2555 of 3327 id: www-blockchain-pioneers author: www title: www-blockchain-pioneers date: None words: 855 flesch: 34 summary: Ry Jones and David Boswell, Community Architects | Mar 5, 2025 Hyperledger Avalon | Blockchain Pioneers Blockchain Pioneers: Hyperledger Avalon As Hyperledger Foundation laid out in the Helping a Community Grow by Pruning Inactive Projectspost, there is an important life cycle to well governed open source projects.... Read More Next page > Submit a blog Blog guidelines RSS Blockchain Pioneers | Hyperledger Explorer Blockchain Pioneers: Hyperledger Explorer As Hyperledger Foundation laid out in the Helping a Community Grow by Pruning Inactive... keywords: community; hyperledger; pioneers cache: www-blockchain-pioneers.html plain text: www-blockchain-pioneers.txt item: #2556 of 3327 id: www-blockchain-pioneers-hyperledger-avalon author: www title: www-blockchain-pioneers-hyperledger-avalon date: None words: 1110 flesch: 31 summary: Hyperledger Avalon also helped establish that privacy, security, and trust are foundational to digital innovation and opened the door for other projects focused on these principles. Blockchain Pioneers: Hyperledger Avalon 2025 Update: Off to a Fast Start! keywords: avalon; blockchain; hyperledger; project cache: www-blockchain-pioneers-hyperledger-avalon.html plain text: www-blockchain-pioneers-hyperledger-avalon.txt item: #2557 of 3327 id: www-blockchain-pioneers-hyperledger-avalon?hs_amp=true author: www title: www-blockchain-pioneers-hyperledger-avalon?hs_amp=true date: None words: 796 flesch: 34 summary: Hyperledger Avalon also helped establish that privacy, security, and trust are foundational to digital innovation and opened the door for other projects focused on these principles. Blockchain Pioneers: Hyperledger Avalon Blog | LF Decentralized Trust Blockchain Pioneers: Hyperledger Avalon Written by Ry Jones and David Boswell, Community Architects | Dec 16, 2024 6:00:00 PM As Hyperledger Foundation laid out in the Helping a Community Grow by Pruning Inactive Projects post, there is an important life cycle to well governed open source projects. keywords: avalon; hyperledger cache: www-blockchain-pioneers-hyperledger-avalon?hs_amp=true.html plain text: www-blockchain-pioneers-hyperledger-avalon?hs_amp=true.txt item: #2558 of 3327 id: www-blockchain-pioneers-hyperledger-burrow author: www title: www-blockchain-pioneers-hyperledger-burrow date: None words: 1016 flesch: 43 summary: Legacy Hyperledger Burrow demonstrated the importance of the Ethereum ecosystem for enterprise-grade blockchain networks and the interest it received paved the way for other similar projects that followed. Other Hyperledger projects, such as Cacti, FireFly and Bevel, have also added support for the Ethereum ecosystem. keywords: blockchain; burrow; hyperledger; project cache: www-blockchain-pioneers-hyperledger-burrow.html plain text: www-blockchain-pioneers-hyperledger-burrow.txt item: #2559 of 3327 id: www-blockchain-pioneers-hyperledger-burrow?hs_amp=true author: www title: www-blockchain-pioneers-hyperledger-burrow?hs_amp=true date: None words: 700 flesch: 50 summary: Legacy Hyperledger Burrow demonstrated the importance of the Ethereum ecosystem for enterprise-grade blockchain networks and the interest it received paved the way for other similar projects that followed. Other Hyperledger projects, such as Cacti, FireFly and Bevel, have also added support for the Ethereum ecosystem. keywords: burrow; hyperledger cache: www-blockchain-pioneers-hyperledger-burrow?hs_amp=true.html plain text: www-blockchain-pioneers-hyperledger-burrow?hs_amp=true.txt item: #2560 of 3327 id: www-blockchain-pioneers-hyperledger-composer author: www title: www-blockchain-pioneers-hyperledger-composer date: None words: 1110 flesch: 40 summary: CC-Tools: Provides a relational-like framework for programming Hyperledger Fabric chaincodes Fabric-Ansible-Collection: Enables you to automate the building of Hyperledger Fabric networks Fabric Smart Client: Simplifies the development of Fabric-based distributed application by hiding the complexity of Fabric  Fablo: Tools to help you developer a Fabric network FireFly-Fabconnect: Part of Hyperledger FireFly, a REST API to interact with a Fabric network and event streaming via websocket Other Fabric related labs We would like to thank all of the people who contributed to Hyperledger Composer while it was an active project. We see this legacy of Hyperledger Composer live on in the large number of projects and labs that are making different aspects of using Hyperledger Fabric easier.  keywords: blockchain; composer; fabric; hyperledger; technologies cache: www-blockchain-pioneers-hyperledger-composer.html plain text: www-blockchain-pioneers-hyperledger-composer.txt item: #2561 of 3327 id: www-blockchain-pioneers-hyperledger-composer?hs_amp=true author: www title: www-blockchain-pioneers-hyperledger-composer?hs_amp=true date: None words: 794 flesch: 47 summary: CC-Tools: Provides a relational-like framework for programming Hyperledger Fabric chaincodes Fabric-Ansible-Collection: Enables you to automate the building of Hyperledger Fabric networks Fabric Smart Client: Simplifies the development of Fabric-based distributed application by hiding the complexity of Fabric  Fablo: Tools to help you developer a Fabric network FireFly-Fabconnect: Part of Hyperledger FireFly, a REST API to interact with a Fabric network and event streaming via websocket Other Fabric related labs We would like to thank all of the people who contributed to Hyperledger Composer while it was an active project. We see this legacy of Hyperledger Composer live on in the large number of projects and labs that are making different aspects of using Hyperledger Fabric easier.  keywords: composer; fabric; hyperledger cache: www-blockchain-pioneers-hyperledger-composer?hs_amp=true.html plain text: www-blockchain-pioneers-hyperledger-composer?hs_amp=true.txt item: #2562 of 3327 id: www-blockchain-pioneers-hyperledger-explorer author: www title: www-blockchain-pioneers-hyperledger-explorer date: None words: 1178 flesch: 40 summary: Hyperledger Explorer is a part of the legacy of Hyperledger Foundation, now LF Decentralized Trust. Legacy Hyperledger Explorer was an important tool in the early days of enterprise blockchain adoption and did have many users that wanted a user-friendly way to visualize and interact with Hyperledger Fabric networks. keywords: blockchain; decentralized; explorer; hyperledger; project cache: www-blockchain-pioneers-hyperledger-explorer.html plain text: www-blockchain-pioneers-hyperledger-explorer.txt item: #2563 of 3327 id: www-blockchain-pioneers-hyperledger-explorer?hs_amp=true author: www title: www-blockchain-pioneers-hyperledger-explorer?hs_amp=true date: None words: 864 flesch: 46 summary: Hyperledger Explorer is a part of the legacy of Hyperledger Foundation, now LF Decentralized Trust. Legacy Hyperledger Explorer was an important tool in the early days of enterprise blockchain adoption and did have many users that wanted a user-friendly way to visualize and interact with Hyperledger Fabric networks. keywords: blockchain; explorer; hyperledger cache: www-blockchain-pioneers-hyperledger-explorer?hs_amp=true.html plain text: www-blockchain-pioneers-hyperledger-explorer?hs_amp=true.txt item: #2564 of 3327 id: www-blockchain-pioneers-hyperledger-quilt author: www title: www-blockchain-pioneers-hyperledger-quilt date: None words: 1166 flesch: 43 summary: Hyperledger Quilt, a Java implementation of the Interledger protocol, is next up in the series. Despite its innovative features, Hyperledger Quilt did not achieve widespread adoption and was eventually moved to archived status. keywords: hyperledger; interoperability; projects; quilt cache: www-blockchain-pioneers-hyperledger-quilt.html plain text: www-blockchain-pioneers-hyperledger-quilt.txt item: #2565 of 3327 id: www-blockchain-pioneers-hyperledger-quilt?hs_amp=true author: www title: www-blockchain-pioneers-hyperledger-quilt?hs_amp=true date: None words: 852 flesch: 49 summary: Conclusion In conclusion, while Hyperledger Quilt brought several innovations to the blockchain space, as an early entrant to interoperability at Hyperledger, it faced challenges that hindered its adoption. Blockchain Pioneers: Hyperledger Quilt Blog | LF Decentralized Trust Blockchain Pioneers: Hyperledger Quilt Written by Ry Jones and David Boswell, Community Architects keywords: hyperledger; quilt cache: www-blockchain-pioneers-hyperledger-quilt?hs_amp=true.html plain text: www-blockchain-pioneers-hyperledger-quilt?hs_amp=true.txt item: #2566 of 3327 id: www-blockchain-pioneers-hyperledger-sawtooth-grid-and-transact author: www title: www-blockchain-pioneers-hyperledger-sawtooth-grid-and-transact date: None words: 1108 flesch: 39 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blockchain Pioneers | Hyperledger Grid | Hyperledger Transact | Hyperledger Sawtooth Blockchain Pioneers: Hyperledger Sawtooth, Grid and Transact Hyperledger Sawtooth, a blockchain suite designed for versatility and scalability, as well as two related projects, Hyperledger Grid and Hyperledger Transact, are next up in the series. keywords: community; hyperledger; project; sawtooth cache: www-blockchain-pioneers-hyperledger-sawtooth-grid-and-transact.html plain text: www-blockchain-pioneers-hyperledger-sawtooth-grid-and-transact.txt item: #2567 of 3327 id: www-blockchain-pioneers-hyperledger-sawtooth-grid-and-transact?hs_amp=true author: www title: www-blockchain-pioneers-hyperledger-sawtooth-grid-and-transact?hs_amp=true date: None words: 788 flesch: 44 summary: Hyperledger Sawtooth, a blockchain suite designed for versatility and scalability, as well as two related projects, Hyperledger Grid and Hyperledger Transact, are next up in the series. Blockchain Pioneers: Hyperledger Sawtooth, Grid and Transact Blog | LF Decentralized Trust Blockchain Pioneers: Hyperledger Sawtooth, Grid and Transact Written by Ry Jones and David Boswell, Community Architects | Aug 8, 2024 4:00:00 PM As we laid out in our Helping a Community Grow by Pruning Inactive Projects post, there is an important life cycle to well governed open source projects. keywords: community; hyperledger; sawtooth cache: www-blockchain-pioneers-hyperledger-sawtooth-grid-and-transact?hs_amp=true.html plain text: www-blockchain-pioneers-hyperledger-sawtooth-grid-and-transact?hs_amp=true.txt item: #2568 of 3327 id: www-blockchain-pioneers-hyperledger-ursa author: www title: www-blockchain-pioneers-hyperledger-ursa date: None words: 1116 flesch: 39 summary: Innovation Hyperledger Ursa was an innovative project because it aimed to enable the cryptography code to be shared by Hyperledger blockchain projects and others. Hyperledger Ursa, a shared cryptographic library that was created to enable people and projects to avoid duplicating other cryptographic work and hopefully increase security in the process, is next up in the series. keywords: code; hyperledger; projects; ursa cache: www-blockchain-pioneers-hyperledger-ursa.html plain text: www-blockchain-pioneers-hyperledger-ursa.txt item: #2569 of 3327 id: www-blockchain-pioneers-hyperledger-ursa?hs_amp=true author: www title: www-blockchain-pioneers-hyperledger-ursa?hs_amp=true date: None words: 800 flesch: 46 summary: Blockchain Pioneers: Hyperledger Ursa Blog | LF Decentralized Trust Blockchain Pioneers: Hyperledger Ursa Written by Ry Jones and David Boswell, Community Architects | Dec 18, 2023 5:00:00 PM As we laid out in our Helping a Community Grow by Pruning Inactive Projects post, there is an important life cycle to well governed open source projects. Hyperledger Ursa, a shared cryptographic library that was created to enable people and projects to avoid duplicating other cryptographic work and hopefully increase security in the process, is next up in the series. keywords: hyperledger; ursa cache: www-blockchain-pioneers-hyperledger-ursa?hs_amp=true.html plain text: www-blockchain-pioneers-hyperledger-ursa?hs_amp=true.txt item: #2570 of 3327 id: www-blockchain-security-webinar-q-a author: www title: www-blockchain-security-webinar-q-a date: None words: 2382 flesch: 50 summary: Distributed Ledger Architecture Now, that you have the basics, we can talk about how Hyperledger permissioned blockchains encode their configuration in configuration transactions stored in the blockchain. Instead of having to throw away a blockchain—something that could cause considerable harm—Hyperledger blockchains can change which algorithms they are using (e.g. increasing key lengths) and/or which consensus protocol is being used if there is a different one that better fits the environment of the network. keywords: blockchain; consensus; data; hyperledger; identity; security cache: www-blockchain-security-webinar-q-a.html plain text: www-blockchain-security-webinar-q-a.txt item: #2571 of 3327 id: www-blockchain-shared-noun author: www title: www-blockchain-shared-noun date: None words: 960 flesch: 55 summary: Blockchain technology adds a new approach to our toolkits. Blockchain technology enables the sender and receiver to always interact with the same object, the same noun. keywords: blockchain; noun; object cache: www-blockchain-shared-noun.html plain text: www-blockchain-shared-noun.txt item: #2572 of 3327 id: www-blockchain-stories-2020-highlights-from-five-weeks-of-community-sharing-in-asia-pacific author: www title: www-blockchain-stories-2020-highlights-from-five-weeks-of-community-sharing-in-asia-pacific date: None words: 1305 flesch: 51 summary: Since Hyperledger believes in inclusive community growth, sessions not only showcased solutions built on Hyperledger projects but also ones built on other platforms. In the last week of May and through June, Hyperledger India Chapter proudly organized a series of interactive events, the most anticipated “Blockchain Stories 2020.” keywords: blockchain; community; hyperledger; india; stories cache: www-blockchain-stories-2020-highlights-from-five-weeks-of-community-sharing-in-asia-pacific.html plain text: www-blockchain-stories-2020-highlights-from-five-weeks-of-community-sharing-in-asia-pacific.txt item: #2573 of 3327 id: www-blockchain-technology-for-healthcare-data-management author: www title: www-blockchain-technology-for-healthcare-data-management date: None words: 1161 flesch: 28 summary: Blockchain technology for healthcare data management – Hyperledger Foundation 2025 Hyperledger Fabric is a permissioned blockchain technology framework that has been actively employed in the implementations of blockchain-based systems for healthcare data management. keywords: blockchain; data; healthcare; technology cache: www-blockchain-technology-for-healthcare-data-management.html plain text: www-blockchain-technology-for-healthcare-data-management.txt item: #2574 of 3327 id: www-blog author: www title: www-blog date: None words: 485 flesch: 15 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-blog.html plain text: www-blog.txt item: #2575 of 3327 id: www-bondevalue-upends-the-global-bond-market-using-hyperledger-sawtooth author: www title: www-bondevalue-upends-the-global-bond-market-using-hyperledger-sawtooth date: None words: 894 flesch: 37 summary: Using depository receipts as a model, traditional bonds are brought into the BondbloX Bond Exchange through designated market makers or a member participant from a secondary market. But for those interested in investing in international bonds, the bond markets in Asia and Europe are particularly hard to break into for two reasons: high investment thresholds and lack of electronic infrastructure. keywords: bond; exchange; hyperledger; market cache: www-bondevalue-upends-the-global-bond-market-using-hyperledger-sawtooth.html plain text: www-bondevalue-upends-the-global-bond-market-using-hyperledger-sawtooth.txt item: #2576 of 3327 id: www-bondevalue-upends-the-global-bond-market-using-hyperledger-sawtooth?hs_amp=true author: www title: www-bondevalue-upends-the-global-bond-market-using-hyperledger-sawtooth?hs_amp=true date: None words: 584 flesch: 43 summary: Using depository receipts as a model, traditional bonds are brought into the BondbloX Bond Exchange through designated market makers or a member participant from a secondary market. But for those interested in investing in international bonds, the bond markets in Asia and Europe are particularly hard to break into for two reasons: high investment thresholds and lack of electronic infrastructure. keywords: bond; market cache: www-bondevalue-upends-the-global-bond-market-using-hyperledger-sawtooth?hs_amp=true.html plain text: www-bondevalue-upends-the-global-bond-market-using-hyperledger-sawtooth?hs_amp=true.txt item: #2577 of 3327 id: www-bosch-leverages-open-source-model-teams-with-polycrypt-to-tackle-blockchain-for-the-economy-of-things author: www title: www-bosch-leverages-open-source-model-teams-with-polycrypt-to-tackle-blockchain-for-the-economy-of-things date: None words: 773 flesch: 46 summary: To that end, they worked with Hyperledger marketing and others in the Perun community on a case study that details not only the business and technology challenges they’ve set out to tackle but also the strategic way they are leveraging open source development to advance the industry for all. The Bosch team was eager to talk about its approaches and contributions to Hyperledger Foundation. keywords: bosch; case; economy cache: www-bosch-leverages-open-source-model-teams-with-polycrypt-to-tackle-blockchain-for-the-economy-of-things.html plain text: www-bosch-leverages-open-source-model-teams-with-polycrypt-to-tackle-blockchain-for-the-economy-of-things.txt item: #2578 of 3327 id: www-brian-behlendorf author: www title: www-brian-behlendorf date: None words: 565 flesch: 23 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Oct 13, 2021 Blog | Hyperledger Aries | Project: Hyperledger Indy | Health and Public Sector Working Together on What “Good” Looks Like On Tuesday, the Good Health Pass Collaborative (GHPC) launched. keywords: blog; decentralized; hyperledger; project cache: www-brian-behlendorf.html plain text: www-brian-behlendorf.txt item: #2579 of 3327 id: www-building-better-together-insights-from-the-governing-board-to-mark-hyperledger-foundations-8th-anniversary author: www title: www-building-better-together-insights-from-the-governing-board-to-mark-hyperledger-foundations-8th-anniversary date: None words: 1451 flesch: 37 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Governance Building Better Together: Insights from the Governing Board to Mark Hyperledger Foundation’s 8th Anniversary Hyperledger Foundation | Feb 27, 2024 As a follow-up to Hyperledger 8: A Celebration of Building Better Together, Daniela Barbosa asked our Governing Board Representatives for their take on the success and value of Hyperledger Foundation as well as the technical priorities they see for the community.  Through Hyperledger, we convene users, technology and service providers, and industry groups, providing us with a continuous and dynamic understanding of the core business and societal requirements for enterprise blockchain. keywords: blockchain; community; enterprise; foundation; hyperledger cache: www-building-better-together-insights-from-the-governing-board-to-mark-hyperledger-foundations-8th-anniversary.html plain text: www-building-better-together-insights-from-the-governing-board-to-mark-hyperledger-foundations-8th-anniversary.txt item: #2580 of 3327 id: www-building-better-together-insights-from-the-governing-board-to-mark-hyperledger-foundations-8th-anniversary?hs_amp=true author: www title: www-building-better-together-insights-from-the-governing-board-to-mark-hyperledger-foundations-8th-anniversary?hs_amp=true date: None words: 1141 flesch: 41 summary: Building Better Together: Insights from the Governing Board to Mark Hyperledger Foundation’s 8th Anniversary Blog | LF Decentralized Trust Building Better Together: Insights from the Governing Board to Mark Hyperledger Foundation’s 8th Anniversary Written by Hyperledger Foundation | Feb 27, 2024 5:55:01 PM As a follow-up to Hyperledger 8: A Celebration of Building Better Together, Daniela Barbosa asked our Governing Board Representatives for their take on the success and value of Hyperledger Foundation as well as the technical priorities they see for the community.  Daniela: What is the value your organization gets from being a leading member of Hyperledger Foundation? keywords: blockchain; community; hyperledger cache: www-building-better-together-insights-from-the-governing-board-to-mark-hyperledger-foundations-8th-anniversary?hs_amp=true.html plain text: www-building-better-together-insights-from-the-governing-board-to-mark-hyperledger-foundations-8th-anniversary?hs_amp=true.txt item: #2581 of 3327 id: www-building-bridges-developing-the-stellar-connector-for-hyperledger-cacti author: www title: www-building-bridges-developing-the-stellar-connector-for-hyperledger-cacti date: None words: 1789 flesch: 36 summary: With this foundational context, Peter Somogyvari from the Hyperledger Cacti community immediately helped us set our initial target: building a Stellar connector. By integrating Soroban, we aim to bring Stellar's capabilities into the Hyperledger Cacti ecosystem. keywords: cacti; connector; hyperledger; project; stellar cache: www-building-bridges-developing-the-stellar-connector-for-hyperledger-cacti.html plain text: www-building-bridges-developing-the-stellar-connector-for-hyperledger-cacti.txt item: #2582 of 3327 id: www-building-bridges-developing-the-stellar-connector-for-hyperledger-cacti?hs_amp=true author: www title: www-building-bridges-developing-the-stellar-connector-for-hyperledger-cacti?hs_amp=true date: None words: 1476 flesch: 40 summary: With this foundational context, Peter Somogyvari from the Hyperledger Cacti community immediately helped us set our initial target: building a Stellar connector. By integrating Soroban, we aim to bring Stellar's capabilities into the Hyperledger Cacti ecosystem. keywords: cacti; connector; stellar cache: www-building-bridges-developing-the-stellar-connector-for-hyperledger-cacti?hs_amp=true.html plain text: www-building-bridges-developing-the-stellar-connector-for-hyperledger-cacti?hs_amp=true.txt item: #2583 of 3327 id: www-building-hiero-together-first-community-meeting-recap-and-upcoming-events author: www title: www-building-hiero-together-first-community-meeting-recap-and-upcoming-events date: None words: 1544 flesch: 43 summary: The team is also enhancing the Hiero Improvement Proposals (HIPs) process and developing new features like the Solos tool, which simplifies deploying Hiero networks in Kubernetes environments. Why Hiero Joined LF Decentralized Trust Richard began the presentation by addressing one of the most common questions the project receives: Why join LF Decentralized Trust? keywords: community; decentralized; hiero; project; trust cache: www-building-hiero-together-first-community-meeting-recap-and-upcoming-events.html plain text: www-building-hiero-together-first-community-meeting-recap-and-upcoming-events.txt item: #2584 of 3327 id: www-building-hiero-together-first-community-meeting-recap-and-upcoming-events?hs_amp=true author: www title: www-building-hiero-together-first-community-meeting-recap-and-upcoming-events?hs_amp=true date: None words: 1234 flesch: 47 summary: Building Hiero Together: First Community Meeting Recap and Upcoming Events Blog | LF Decentralized Trust Building Hiero Together: First Community Meeting Recap and Upcoming Events Written by Hiero Community | Nov 12, 2024 2:00:00 PM The team is also enhancing the Hiero Improvement Proposals (HIPs) process and developing new features like the Solos tool, which simplifies deploying Hiero networks in Kubernetes environments. keywords: community; decentralized; hiero; trust cache: www-building-hiero-together-first-community-meeting-recap-and-upcoming-events?hs_amp=true.html plain text: www-building-hiero-together-first-community-meeting-recap-and-upcoming-events?hs_amp=true.txt item: #2585 of 3327 id: www-burrow-the-boring-blockchain author: www title: www-burrow-the-boring-blockchain date: None words: 1528 flesch: 49 summary: References To learn more about the project and community, check out these resources: Burrow main documentation site Burrow Hyperledger chat Burrow Hyperledger wiki Blackstone – Agreements Network Burrow godoc About the Author Silas Davis is the Burrow maintainer and CTO at Monax.io. For a more detailed look at Hyperledger Burrow features, read an extended version of this article here. keywords: burrow; ethereum; evm; hyperledger; project; use cache: www-burrow-the-boring-blockchain.html plain text: www-burrow-the-boring-blockchain.txt item: #2586 of 3327 id: www-burrow-the-boring-blockchain?hs_amp=true author: www title: www-burrow-the-boring-blockchain?hs_amp=true date: None words: 1217 flesch: 55 summary: References To learn more about the project and community, check out these resources: Burrow main documentation site Burrow Hyperledger chat Burrow Hyperledger wiki Blackstone – Agreements Network Burrow godoc About the Author Silas Davis is the Burrow maintainer and CTO at Monax.io. For a more detailed look at Hyperledger Burrow features, read an extended version of this article here. keywords: burrow; ethereum; evm; hyperledger cache: www-burrow-the-boring-blockchain?hs_amp=true.html plain text: www-burrow-the-boring-blockchain?hs_amp=true.txt item: #2587 of 3327 id: www-business-process-modeling-the-missing-link-between-legal-know-how-and-blockchain-based-legal-products author: www title: www-business-process-modeling-the-missing-link-between-legal-know-how-and-blockchain-based-legal-products date: None words: 1306 flesch: 37 summary: Legal products built this way can transform the delivery of legal services and promote productization of law. The combination of blockchain technology, smart contracts, and BPM provide us with the ability to create new, more effective commercial vehicles for getting jobs done in networked commerce: legal products. keywords: blockchain; bpmn; business; process; products cache: www-business-process-modeling-the-missing-link-between-legal-know-how-and-blockchain-based-legal-products.html plain text: www-business-process-modeling-the-missing-link-between-legal-know-how-and-blockchain-based-legal-products.txt item: #2588 of 3327 id: www-business-process-modeling-the-missing-link-between-legal-know-how-and-blockchain-based-legal-products?hs_amp=true author: www title: www-business-process-modeling-the-missing-link-between-legal-know-how-and-blockchain-based-legal-products?hs_amp=true date: None words: 995 flesch: 41 summary: Legal products built this way can transform the delivery of legal services and promote productization of law. The combination of blockchain technology, smart contracts, and BPM provide us with the ability to create new, more effective commercial vehicles for getting jobs done in networked commerce: legal products. keywords: blockchain; bpmn; process; products cache: www-business-process-modeling-the-missing-link-between-legal-know-how-and-blockchain-based-legal-products?hs_amp=true.html plain text: www-business-process-modeling-the-missing-link-between-legal-know-how-and-blockchain-based-legal-products?hs_amp=true.txt item: #2589 of 3327 id: www-by-alex-popowycz-chief-information-chief-information-security-officer-hedera-and-hiero-technical-steering-committee-member author: www title: www-by-alex-popowycz-chief-information-chief-information-security-officer-hedera-and-hiero-technical-steering-committee-member date: None words: 550 flesch: 16 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Hiero Introducing Hiero: Bringing Hedera’s Core Network Software to Linux Foundation Decentralized Trust In the ever-evolving landscape of decentralized technologies, few innovations stand out like the... Read More By Alex Popowycz, Chief Information & Chief Information Security Officer, Hedera and Hiero Technical Steering Committee Member | Sep 16, 2024 keywords: blog; decentralized; hyperledger; technologies cache: www-by-alex-popowycz-chief-information-chief-information-security-officer-hedera-and-hiero-technical-steering-committee-member.html plain text: www-by-alex-popowycz-chief-information-chief-information-security-officer-hedera-and-hiero-technical-steering-committee-member.txt item: #2590 of 3327 id: www-call-for-applications-2022-hyperledger-mentorship-program author: www title: www-call-for-applications-2022-hyperledger-mentorship-program date: None words: 1679 flesch: 38 summary: Each of these mentees have made concrete contributions to Hyperledger projects and built important connections in the community. Over the last five years, more than 70 mentees have completed Hyperledger Mentorship projects. keywords: cactus; fabric; hyperledger; mentorship; project; technologies cache: www-call-for-applications-2022-hyperledger-mentorship-program.html plain text: www-call-for-applications-2022-hyperledger-mentorship-program.txt item: #2591 of 3327 id: www-call-for-applications-2022-hyperledger-mentorship-program?hs_amp=true author: www title: www-call-for-applications-2022-hyperledger-mentorship-program?hs_amp=true date: None words: 1362 flesch: 41 summary: Each of these mentees have made concrete contributions to Hyperledger projects and built important connections in the community. Over the last five years, more than 70 mentees have completed Hyperledger Mentorship projects. keywords: cactus; fabric; hyperledger; mentorship; project cache: www-call-for-applications-2022-hyperledger-mentorship-program?hs_amp=true.html plain text: www-call-for-applications-2022-hyperledger-mentorship-program?hs_amp=true.txt item: #2592 of 3327 id: www-calling-the-next-generation-of-open-source-blockchain-contributors-applications-are-open-for-the-2023-hyperledger-annual-mentorship-program author: www title: www-calling-the-next-generation-of-open-source-blockchain-contributors-applications-are-open-for-the-2023-hyperledger-annual-mentorship-program date: None words: 1953 flesch: 32 summary: Cacti: Ledger Data Sharing with Proof in Hyperledger Besu and Ethereum Project focus: The goal of this project is to add similar support (i.e., build modules, plugins, and APIs) for permissioned networks built on Hyperledger Besu. keywords: data; decentralized; hyperledger; identity; project; telecom cache: www-calling-the-next-generation-of-open-source-blockchain-contributors-applications-are-open-for-the-2023-hyperledger-annual-mentorship-program.html plain text: www-calling-the-next-generation-of-open-source-blockchain-contributors-applications-are-open-for-the-2023-hyperledger-annual-mentorship-program.txt item: #2593 of 3327 id: www-calling-the-next-generation-of-open-source-blockchain-contributors-applications-are-open-for-the-2023-hyperledger-annual-mentorship-program?hs_amp=true author: www title: www-calling-the-next-generation-of-open-source-blockchain-contributors-applications-are-open-for-the-2023-hyperledger-annual-mentorship-program?hs_amp=true date: None words: 1644 flesch: 33 summary: Cacti: Ledger Data Sharing with Proof in Hyperledger Besu and Ethereum Project focus: The goal of this project is to add similar support (i.e., build modules, plugins, and APIs) for permissioned networks built on Hyperledger Besu. keywords: data; documentation; hyperledger; project; telecom cache: www-calling-the-next-generation-of-open-source-blockchain-contributors-applications-are-open-for-the-2023-hyperledger-annual-mentorship-program?hs_amp=true.html plain text: www-calling-the-next-generation-of-open-source-blockchain-contributors-applications-are-open-for-the-2023-hyperledger-annual-mentorship-program?hs_amp=true.txt item: #2594 of 3327 id: www-cardea-a-privacy-preserving-open-source-ecosystem-for-verifying-health-data-joins-hyperledger-labs author: www title: www-cardea-a-privacy-preserving-open-source-ecosystem-for-verifying-health-data-joins-hyperledger-labs date: None words: 845 flesch: 37 summary: And as a Public Benefit Corporation, we believe that open sourcing decentralized identity technology through Hyperledger Foundation will lay the foundation for a better, fairer world to come.” Cardea, a privacy preserving open-source ecosystem for verifying health data, joins Hyperledger Labs – Hyperledger Foundation 2025 keywords: cardea; decentralized; health; privacy cache: www-cardea-a-privacy-preserving-open-source-ecosystem-for-verifying-health-data-joins-hyperledger-labs.html plain text: www-cardea-a-privacy-preserving-open-source-ecosystem-for-verifying-health-data-joins-hyperledger-labs.txt item: #2595 of 3327 id: www-cardea-a-privacy-preserving-open-source-ecosystem-for-verifying-health-data-joins-hyperledger-labs?hs_amp=true author: www title: www-cardea-a-privacy-preserving-open-source-ecosystem-for-verifying-health-data-joins-hyperledger-labs?hs_amp=true date: None words: 522 flesch: 45 summary: Cardea, a privacy preserving open-source ecosystem for verifying health data, joins Hyperledger Labs – Hyperledger Foundation Blog | LF Decentralized Trust Cardea, a privacy preserving open-source ecosystem for verifying health data, joins Hyperledger Labs – Hyperledger Foundation Written by Ken Ebert and Keela Rose Shatzkin, Co-Chairs, Cardea Working Group | May 10, 2023 6:00:00 AM Cardea, a complete open-source verifiable credential ecosystem for sharing health information in a way that preserves patient privacy, has been accepted as a Hyperledger Lab. The unique parts of the codebase were built on Hyperledger Indy and Hyperledger Aries and originally donated by SITA as the Cardea Project to Linux Foundation Public Health, where it was further developed to address the broader need for a complete open source solution for sharing health data in a privacy-preserving and secure way. keywords: cardea; health cache: www-cardea-a-privacy-preserving-open-source-ecosystem-for-verifying-health-data-joins-hyperledger-labs?hs_amp=true.html plain text: www-cardea-a-privacy-preserving-open-source-ecosystem-for-verifying-health-data-joins-hyperledger-labs?hs_amp=true.txt item: #2596 of 3327 id: www-case-study author: www title: www-case-study date: None words: 609 flesch: 21 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Read More Hyperledger | Jan 31, 2023 Case Study | Governance | Besu LACChain introduces permissioned public blockchain ecosystem built on Hyperledger Besu to Latin America Read the full case study here. keywords: case; hyperledger; study cache: www-case-study.html plain text: www-case-study.txt item: #2597 of 3327 id: www-cbdcs author: www title: www-cbdcs date: None words: 535 flesch: 15 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Blog | Digital Currency | CBDCs | Finance Fintech Open Source Foundation (FINOS), Hyperledger Foundation, and The Digital Dollar Project Team Up to Drive Open Development and Collaboration for CBDCs Central Bank Digital Currency (CBDC) has the power to transform economies — connecting people,... keywords: blog; decentralized; hyperledger; project cache: www-cbdcs.html plain text: www-cbdcs.txt item: #2598 of 3327 id: www-celebrating-black-history-month-advancing-fintech-and-blockchain-innovation-at-hbcus author: www title: www-celebrating-black-history-month-advancing-fintech-and-blockchain-innovation-at-hbcus date: None words: 1681 flesch: 30 summary: The students were mentored by FinTech industry leaders. Through strategic partnerships with LF Decentralized Trust, and other industry leaders, the center continues to: Expand access to FinTech and blockchain education at HBCUs. keywords: blockchain; center; decentralized; fintech; students; trust cache: www-celebrating-black-history-month-advancing-fintech-and-blockchain-innovation-at-hbcus.html plain text: www-celebrating-black-history-month-advancing-fintech-and-blockchain-innovation-at-hbcus.txt item: #2599 of 3327 id: www-celebrating-black-history-month-advancing-fintech-and-blockchain-innovation-at-hbcus?hs_amp=true author: www title: www-celebrating-black-history-month-advancing-fintech-and-blockchain-innovation-at-hbcus?hs_amp=true date: None words: 1371 flesch: 33 summary: The students were mentored by FinTech industry leaders. Through strategic partnerships with LF Decentralized Trust, and other industry leaders, the center continues to: Expand access to FinTech and blockchain education at HBCUs. keywords: blockchain; center; fintech; students cache: www-celebrating-black-history-month-advancing-fintech-and-blockchain-innovation-at-hbcus?hs_amp=true.html plain text: www-celebrating-black-history-month-advancing-fintech-and-blockchain-innovation-at-hbcus?hs_amp=true.txt item: #2600 of 3327 id: www-change-healthcare-50-million-transactions-a-day-using-hyperledger-fabric author: www title: www-change-healthcare-50-million-transactions-a-day-using-hyperledger-fabric date: None words: 626 flesch: 37 summary: To unite information and give customers faster, better access to data, Change Healthcare turned to Hyperledger Fabric to begin blockchain-enabling its Intelligent Healthcare Network. Change Healthcare: 50 million transactions a day using Hyperledger Fabric – Hyperledger Foundation 2025 keywords: change; healthcare; network cache: www-change-healthcare-50-million-transactions-a-day-using-hyperledger-fabric.html plain text: www-change-healthcare-50-million-transactions-a-day-using-hyperledger-fabric.txt item: #2601 of 3327 id: www-circulor-readies-market-for-new-regulations-by-adding-battery-passport-to-hyperledger-fabric-powered-traceability-platform author: www title: www-circulor-readies-market-for-new-regulations-by-adding-battery-passport-to-hyperledger-fabric-powered-traceability-platform date: None words: 930 flesch: 30 summary: As the most mature battery traceability platform on the market, Circulor has the largest network of battery suppliers and value chain participants on its platform, including OEMs (such as Volvo Cars, Polestar, Volkswagen, Daimler and BMW), midstream producers, miners, and recyclers. The new regulation concerns all electric vehicle (EV) batteries, light means of transport (LMT) batteries, and industrial batteries with a capacity over 2kWh. keywords: battery; case; circulor; hyperledger cache: www-circulor-readies-market-for-new-regulations-by-adding-battery-passport-to-hyperledger-fabric-powered-traceability-platform.html plain text: www-circulor-readies-market-for-new-regulations-by-adding-battery-passport-to-hyperledger-fabric-powered-traceability-platform.txt item: #2602 of 3327 id: www-circulor-readies-market-for-new-regulations-by-adding-battery-passport-to-hyperledger-fabric-powered-traceability-platform?hs_amp=true author: www title: www-circulor-readies-market-for-new-regulations-by-adding-battery-passport-to-hyperledger-fabric-powered-traceability-platform?hs_amp=true date: None words: 613 flesch: 36 summary: As the most mature battery traceability platform on the market, Circulor has the largest network of battery suppliers and value chain participants on its platform, including OEMs (such as Volvo Cars, Polestar, Volkswagen, Daimler and BMW), midstream producers, miners, and recyclers. The new regulation concerns all electric vehicle (EV) batteries, light means of transport (LMT) batteries, and industrial batteries with a capacity over 2kWh. keywords: battery; circulor cache: www-circulor-readies-market-for-new-regulations-by-adding-battery-passport-to-hyperledger-fabric-powered-traceability-platform?hs_amp=true.html plain text: www-circulor-readies-market-for-new-regulations-by-adding-battery-passport-to-hyperledger-fabric-powered-traceability-platform?hs_amp=true.txt item: #2603 of 3327 id: www-citi-taps-besu-a-linux-foundation-decentralized-trust-project-to-deliver-near-real-time-value-transfers-via-citi-token-services-for-cash author: www title: www-citi-taps-besu-a-linux-foundation-decentralized-trust-project-to-deliver-near-real-time-value-transfers-via-citi-token-services-for-cash date: None words: 860 flesch: 41 summary: Citi taps Besu, a Linux Foundation Decentralized Trust project, to deliver near real-time value transfers via Citi Token Services for Cash 2025 Update: Off to a Fast Start!  Facilitating 24/7 operations for global transactions Offering a seamless client experience And for Citi, the launch of Citi Token Services for Cash is just the first step into a future where banking is faster, more efficient, and real-time. keywords: citi; decentralized; services cache: www-citi-taps-besu-a-linux-foundation-decentralized-trust-project-to-deliver-near-real-time-value-transfers-via-citi-token-services-for-cash.html plain text: www-citi-taps-besu-a-linux-foundation-decentralized-trust-project-to-deliver-near-real-time-value-transfers-via-citi-token-services-for-cash.txt item: #2604 of 3327 id: www-citi-taps-besu-a-linux-foundation-decentralized-trust-project-to-deliver-near-real-time-value-transfers-via-citi-token-services-for-cash?hs_amp=true author: www title: www-citi-taps-besu-a-linux-foundation-decentralized-trust-project-to-deliver-near-real-time-value-transfers-via-citi-token-services-for-cash?hs_amp=true date: None words: 546 flesch: 51 summary: Citi taps Besu, a Linux Foundation Decentralized Trust project, to deliver near real-time value transfers via Citi Token Services for Cash Blog | LF Decentralized Trust Citi taps Besu, a Linux Foundation Decentralized Trust project, to deliver near real-time value transfers via Citi Token Services for Cash Written by LF Decentralized Trust | Nov 4, 2024 8:17:19 PM Read the full case study here. Facilitating 24/7 operations for global transactions Offering a seamless client experience And for Citi, the launch of Citi Token Services for Cash is just the first step into a future where banking is faster, more efficient, and real-time. keywords: citi; services cache: www-citi-taps-besu-a-linux-foundation-decentralized-trust-project-to-deliver-near-real-time-value-transfers-via-citi-token-services-for-cash?hs_amp=true.html plain text: www-citi-taps-besu-a-linux-foundation-decentralized-trust-project-to-deliver-near-real-time-value-transfers-via-citi-token-services-for-cash?hs_amp=true.txt item: #2605 of 3327 id: www-citopia-and-the-integrated-trust-network-itn-mobi-zero-trust-approach-to-web3-multiparty-business-automation author: www title: www-citopia-and-the-integrated-trust-network-itn-mobi-zero-trust-approach-to-web3-multiparty-business-automation date: None words: 1644 flesch: 32 summary: Open source blockchain technologies such as those hosted by Hyperledger Foundation promise to leverage the existing trust within corporate transaction networks by automating traceability, settlement, and audit processes. Citopia and the Integrated Trust Network (ITN): MOBI Zero Trust Approach to Web3 Multiparty Business Automation 2025 keywords: business; citopia; itn; mobi; network; trust cache: www-citopia-and-the-integrated-trust-network-itn-mobi-zero-trust-approach-to-web3-multiparty-business-automation.html plain text: www-citopia-and-the-integrated-trust-network-itn-mobi-zero-trust-approach-to-web3-multiparty-business-automation.txt item: #2606 of 3327 id: www-citopia-and-the-integrated-trust-network-itn-mobi-zero-trust-approach-to-web3-multiparty-business-automation?hs_amp=true author: www title: www-citopia-and-the-integrated-trust-network-itn-mobi-zero-trust-approach-to-web3-multiparty-business-automation?hs_amp=true date: None words: 1330 flesch: 33 summary: Open source blockchain technologies such as those hosted by Hyperledger Foundation promise to leverage the existing trust within corporate transaction networks by automating traceability, settlement, and audit processes. Although Citopia and the ITN have some similarities to other industry networks, there are important differences that will enhance the speed, privacy, security, and regulatory compliance of connected ecosystems.  keywords: citopia; itn; network; trust cache: www-citopia-and-the-integrated-trust-network-itn-mobi-zero-trust-approach-to-web3-multiparty-business-automation?hs_amp=true.html plain text: www-citopia-and-the-integrated-trust-network-itn-mobi-zero-trust-approach-to-web3-multiparty-business-automation?hs_amp=true.txt item: #2607 of 3327 id: www-clarisse-hagege-and-christopher-grilhault-des-fontaines-lockness-maintainers author: www title: www-clarisse-hagege-and-christopher-grilhault-des-fontaines-lockness-maintainers date: None words: 533 flesch: 17 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-clarisse-hagege-and-christopher-grilhault-des-fontaines-lockness-maintainers.html plain text: www-clarisse-hagege-and-christopher-grilhault-des-fontaines-lockness-maintainers.txt item: #2608 of 3327 id: www-claudia-emmanuel author: www title: www-claudia-emmanuel date: None words: 513 flesch: 16 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Mentorship Program | Hyperledger Fabric LF Decentralized Trust Mentorship Spotlight: VS Code Debugger Plugin for Hyperledger Fabric Chaincode Introduction Read More Claudia Emmanuel | Mar 24, 2025 keywords: blog; decentralized; hyperledger; technologies cache: www-claudia-emmanuel.html plain text: www-claudia-emmanuel.txt item: #2609 of 3327 id: www-climate author: www title: www-climate date: None words: 1404 flesch: 26 summary: to... Read More Hyperledger | Sep 13, 2022 Hyperledger Aries | Developer Showcase | Project: Hyperledger Indy | Climate | Decentralized Identity Developer showcase series: Jason Sherman, Developer at Energy & Mines Digital Trust, Government of British Columbia Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. “The Carbon Footprint of NFTs” report As Tom Brady, DCComics and Visa will tell you, non-fungible tokens (NFTs) are a class of assets underpinning the worlds of digital art, digital collectibles, metaverse gaming, and... Read More Hyperledger | Apr 22, 2022 Blog | Climate Tackling Energy Security and Climate Change with Open Source and Blockchain It started out as two separate projects at the Climate Accounting and Action SIG, a Hyperledger group focused on using blockchain and distributed ledger technologies (DLT’s) to... Read More Hyperledger | Apr 19, 2022 Blog | Climate Hyperledger Mentorship Spotlight: Documentation and Use Cases for Climate Action The Hyperledger Mentorship Program is a structured hands-on learning opportunity for new developers who may otherwise lack the opportunity to gain exposure to Hyperledger open... keywords: blog; climate; digital; energy; hyperledger; trust cache: www-climate.html plain text: www-climate.txt item: #2610 of 3327 id: www-climate-action-and-accounting-special-interest-group-ca2sig-wins-the-hyperledger-challenge-2022 author: www title: www-climate-action-and-accounting-special-interest-group-ca2sig-wins-the-hyperledger-challenge-2022 date: None words: 692 flesch: 38 summary: Moving forward our focus is on marketing our solution to the energy industry and helping to scale auditing services, crucial to achieving climate targets by mid century. ” – Bertrand Rioux, Director, Two Ravens Energy & Climate Consulting This prototype, which is built using Hyperledger Besu, Hyperledger Fabric, Hyperledger Bevel and Hyperledger Cactus, represents an important step towards creating an open climate accounting system that can be used to decarbonize corporate supply chains. – Hyperledger Foundation 2025 Update: Off to a Fast Start! keywords: challenge; climate; hyperledger cache: www-climate-action-and-accounting-special-interest-group-ca2sig-wins-the-hyperledger-challenge-2022.html plain text: www-climate-action-and-accounting-special-interest-group-ca2sig-wins-the-hyperledger-challenge-2022.txt item: #2611 of 3327 id: www-climate-action-and-accounting-special-interest-group-ca2sig-wins-the-hyperledger-challenge-2022?hs_amp=true author: www title: www-climate-action-and-accounting-special-interest-group-ca2sig-wins-the-hyperledger-challenge-2022?hs_amp=true date: None words: 376 flesch: 47 summary: Moving forward our focus is on marketing our solution to the energy industry and helping to scale auditing services, crucial to achieving climate targets by mid century. ” – Bertrand Rioux, Director, Two Ravens Energy & Climate Consulting This prototype, which is built using Hyperledger Besu, Hyperledger Fabric, Hyperledger Bevel and Hyperledger Cactus, represents an important step towards creating an open climate accounting system that can be used to decarbonize corporate supply chains. – Hyperledger Foundation Blog | LF Decentralized Trust Climate Action and Accounting Special Interest Group (CA2SIG) wins The Hyperledger Challenge 2022! keywords: hyperledger cache: www-climate-action-and-accounting-special-interest-group-ca2sig-wins-the-hyperledger-challenge-2022?hs_amp=true.html plain text: www-climate-action-and-accounting-special-interest-group-ca2sig-wins-the-hyperledger-challenge-2022?hs_amp=true.txt item: #2612 of 3327 id: www-climate-change-action-five-ways-to-get-involved-in-our-global-climate-accounting-efforts author: www title: www-climate-change-action-five-ways-to-get-involved-in-our-global-climate-accounting-efforts date: None words: 869 flesch: 40 summary: With the support and know-how from community members such as the Linux Foundation, Open Earth Foundation and Climate Chain Coalition, we are making good progress, but we need your help. Join the Operating System for Climate Action to help build tools to record emissions (right now from energy data from utility bills) and allow emissions and offsets to be tokenized and traded. keywords: action; climate; group; help cache: www-climate-change-action-five-ways-to-get-involved-in-our-global-climate-accounting-efforts.html plain text: www-climate-change-action-five-ways-to-get-involved-in-our-global-climate-accounting-efforts.txt item: #2613 of 3327 id: www-combing-iot-and-dlt-to-ensure-the-safety-of-the-worlds-vaccine-supply-chains author: www title: www-combing-iot-and-dlt-to-ensure-the-safety-of-the-worlds-vaccine-supply-chains date: None words: 1768 flesch: 32 summary: Analysts project that Covid-19 vaccines will be the highest demand counterfeit drug on the black market for 20213. Now, a year to date later, we are lucky to be at the point where multiple vaccines have been approved and administered to the public. keywords: chain; hyperledger; iot; supply; technologies; vaccines cache: www-combing-iot-and-dlt-to-ensure-the-safety-of-the-worlds-vaccine-supply-chains.html plain text: www-combing-iot-and-dlt-to-ensure-the-safety-of-the-worlds-vaccine-supply-chains.txt item: #2614 of 3327 id: www-community-spotlight-meet-bobbi-muscara-hyperledger-learning-materials-development-working-group-chair author: www title: www-community-spotlight-meet-bobbi-muscara-hyperledger-learning-materials-development-working-group-chair date: None words: 1242 flesch: 47 summary: I currently also chair the Linux Foundation’s Hyperledger Learning Materials Development Working Group where we are currently working with other Hyperledger community groups to create standards for Hyperledger documentation. Community Spotlight: Meet Bobbi Muscara, Hyperledger Learning Materials Development Working Group Chair – Hyperledger Foundation 2025 keywords: community; group; hyperledger; working cache: www-community-spotlight-meet-bobbi-muscara-hyperledger-learning-materials-development-working-group-chair.html plain text: www-community-spotlight-meet-bobbi-muscara-hyperledger-learning-materials-development-working-group-chair.txt item: #2615 of 3327 id: www-community-spotlight-meet-richard-bloch-hyperledger-healthcare-sig-chair author: www title: www-community-spotlight-meet-richard-bloch-hyperledger-healthcare-sig-chair date: None words: 1807 flesch: 39 summary: and my answer is always this: active membership in the HC-SIG puts you in touch with the unprecedented resource of over 1,000 people around the world who are pre-filtered to have an active interest in healthcare technologies/IT, and then filtered again by their interests/knowledge in applying blockchain technologies to this industry. We provide many opportunities for focusing specific interests on blockchain technologies solutions in healthcare either through our HC-SIG subgroups or our ad hoc teams. keywords: blockchain; community; healthcare; hyperledger; sig; technologies cache: www-community-spotlight-meet-richard-bloch-hyperledger-healthcare-sig-chair.html plain text: www-community-spotlight-meet-richard-bloch-hyperledger-healthcare-sig-chair.txt item: #2616 of 3327 id: www-community-spotlight-meet-saptarshi-choudhury-hyperledger-public-sector-special-interest-group-co-chair author: www title: www-community-spotlight-meet-saptarshi-choudhury-hyperledger-public-sector-special-interest-group-co-chair date: None words: 1237 flesch: 45 summary: Community Spotlight: Meet Saptarshi Choudhury, Hyperledger Public Sector Special Interest Group Co-Chair – Hyperledger Foundation 2025 They can also subscribe to the mailing list to stay updated about the latest progress in the community and contribute to the Hyperledger Wiki. keywords: blockchain; hyperledger; interest; sector; technologies cache: www-community-spotlight-meet-saptarshi-choudhury-hyperledger-public-sector-special-interest-group-co-chair.html plain text: www-community-spotlight-meet-saptarshi-choudhury-hyperledger-public-sector-special-interest-group-co-chair.txt item: #2617 of 3327 id: www-conducting-data-with-concerto-and-hyperledger-fabric author: www title: www-conducting-data-with-concerto-and-hyperledger-fabric date: None words: 1509 flesch: 43 summary: An example I’ve published a detailed code sample for Node.js chaincode and a HLF v1.3 client so you can start to experiment with using Concerto in HLF v1.3 Node.js chaincode: https://github.com/clauseHQ/fabric-samples/blob/master/concerto/README.md The sample shows you how to deploy Concerto models to the blockchain and then use the models to validate instances and to serialize them to JSON for long-lived persistence. Embed the Concerto Form Generator into your web application to dynamically generate web forms based on Concerto models. keywords: concerto; hyperledger; json; model; schema; use cache: www-conducting-data-with-concerto-and-hyperledger-fabric.html plain text: www-conducting-data-with-concerto-and-hyperledger-fabric.txt item: #2618 of 3327 id: www-conducting-data-with-concerto-and-hyperledger-fabric?hs_amp=true author: www title: www-conducting-data-with-concerto-and-hyperledger-fabric?hs_amp=true date: None words: 1198 flesch: 49 summary: An example I’ve published a detailed code sample for Node.js chaincode and a HLF v1.3 client so you can start to experiment with using Concerto in HLF v1.3 Node.js chaincode: https://github.com/clauseHQ/fabric-samples/blob/master/concerto/README.md The sample shows you how to deploy Concerto models to the blockchain and then use the models to validate instances and to serialize them to JSON for long-lived persistence. Embed the Concerto Form Generator into your web application to dynamically generate web forms based on Concerto models. keywords: concerto; json; model; schema cache: www-conducting-data-with-concerto-and-hyperledger-fabric?hs_amp=true.html plain text: www-conducting-data-with-concerto-and-hyperledger-fabric?hs_amp=true.txt item: #2619 of 3327 id: www-conor-svensson-author-of-web3j-and-founder-of-web3-labs author: www title: www-conor-svensson-author-of-web3j-and-founder-of-web3-labs date: None words: 534 flesch: 19 summary: Introducing Hyperledger Web3j, the Ethereum Integration Library for Enterprises We are very excited to announce the newest Hyperledger project, Hyperledger Web3j. Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page keywords: blog; decentralized; hyperledger; project cache: www-conor-svensson-author-of-web3j-and-founder-of-web3-labs.html plain text: www-conor-svensson-author-of-web3j-and-founder-of-web3-labs.txt item: #2620 of 3327 id: www-contamination-fires-and-pollution-oh-my-human-consumption-and-the-barriers-to-a-circular-economy-part-ii author: www title: www-contamination-fires-and-pollution-oh-my-human-consumption-and-the-barriers-to-a-circular-economy-part-ii date: None words: 2054 flesch: 47 summary: Fires Do you know where to recycle/properly dispose of your electronics, chemicals, and other hazardous materials? Indeed, hazardous materials have the potential to desperately impact vulnerable communities, but the efforts to control them also provide an opportunity to create jobs, improve health, and create economic opportunity. keywords: air; chemicals; fires; hazardous; materials; pollution; recycling cache: www-contamination-fires-and-pollution-oh-my-human-consumption-and-the-barriers-to-a-circular-economy-part-ii.html plain text: www-contamination-fires-and-pollution-oh-my-human-consumption-and-the-barriers-to-a-circular-economy-part-ii.txt item: #2621 of 3327 id: www-cool-careers-in-open-source-sharing-our-stories-at-grace-hopper author: www title: www-cool-careers-in-open-source-sharing-our-stories-at-grace-hopper date: None words: 1723 flesch: 46 summary: “ “Open source is open source! Here are just some of the resources available to anyone interested in getting involved in open source in the Linux Foundation and Hyperledger community: Training – Gain marketable open source skills with the Linux Foundation Training is an on-ramp to opportunity in the software development industry, especially in open source. keywords: foundation; linux; skills; source; training; women cache: www-cool-careers-in-open-source-sharing-our-stories-at-grace-hopper.html plain text: www-cool-careers-in-open-source-sharing-our-stories-at-grace-hopper.txt item: #2622 of 3327 id: www-credebl author: www title: www-credebl date: None words: 579 flesch: 13 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Blog | LF Decentralized Trust | CREDEBL 2025 Update: Off to a Fast Start! keywords: blog; credebl; decentralized; hyperledger cache: www-credebl.html plain text: www-credebl.txt item: #2623 of 3327 id: www-credebl-becomes-an-lf-decentralized-trust-project-advancing-decentralized-identity-and-verifiable-credentials-for-a-secure-digital-future author: www title: www-credebl-becomes-an-lf-decentralized-trust-project-advancing-decentralized-identity-and-verifiable-credentials-for-a-secure-digital-future date: None words: 1436 flesch: 31 summary: As part of LF Decentralized Trust, CREDEBL community will continue to push the boundaries of what’s possible in decentralized identity. How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us CREDEBL CREDEBL Becomes an LF Decentralized Trust Project, Advancing Decentralized Identity and Verifiable Credentials for a Secure Digital Future Ajay Jadhav, CREDEBL Maintainer | Feb 5, 2025 We are excited to announce that CREDEBL, the leading platform in Decentralized Identity (DID) and Verifiable Credentials (VC) management, developed and maintained by the AYANWORKS team, is now officially an LF Decentralized Trust project. keywords: credebl; decentralized; identity; trust cache: www-credebl-becomes-an-lf-decentralized-trust-project-advancing-decentralized-identity-and-verifiable-credentials-for-a-secure-digital-future.html plain text: www-credebl-becomes-an-lf-decentralized-trust-project-advancing-decentralized-identity-and-verifiable-credentials-for-a-secure-digital-future.txt item: #2624 of 3327 id: www-credebl-becomes-an-lf-decentralized-trust-project-advancing-decentralized-identity-and-verifiable-credentials-for-a-secure-digital-future?hs_amp=true author: www title: www-credebl-becomes-an-lf-decentralized-trust-project-advancing-decentralized-identity-and-verifiable-credentials-for-a-secure-digital-future?hs_amp=true date: None words: 1126 flesch: 32 summary: As part of LF Decentralized Trust, CREDEBL community will continue to push the boundaries of what’s possible in decentralized identity. Accelerating Adoption Access to a broader network of developers and enterprises will drive CREDEBL adoption across industries, measured as a success metric by the number of projects built on top of its platform. keywords: credebl; decentralized; identity cache: www-credebl-becomes-an-lf-decentralized-trust-project-advancing-decentralized-identity-and-verifiable-credentials-for-a-secure-digital-future?hs_amp=true.html plain text: www-credebl-becomes-an-lf-decentralized-trust-project-advancing-decentralized-identity-and-verifiable-credentials-for-a-secure-digital-future?hs_amp=true.txt item: #2625 of 3327 id: www-credebl-v2.0.0-major-updates-across-platform-studio-credo-controller-and-mobile-sdk author: www title: www-credebl-v2.0.0-major-updates-across-platform-studio-credo-controller-and-mobile-sdk date: None words: 837 flesch: 38 summary: Proof Controller Updates: Addition of new fields and refactored proof payload for better clarity. With improved security, enhanced logging, refined proof management, and integrations like DigiLocker and OpenID4VC, this release ensures a more seamless and efficient experience for our users. keywords: credebl; decentralized; proof; security cache: www-credebl-v2.0.0-major-updates-across-platform-studio-credo-controller-and-mobile-sdk.html plain text: www-credebl-v2.0.0-major-updates-across-platform-studio-credo-controller-and-mobile-sdk.txt item: #2626 of 3327 id: www-credebl-v2.0.0-major-updates-across-platform-studio-credo-controller-and-mobile-sdk?hs_amp=true author: www title: www-credebl-v2.0.0-major-updates-across-platform-studio-credo-controller-and-mobile-sdk?hs_amp=true date: None words: 527 flesch: 42 summary: Proof Controller Updates: Addition of new fields and refactored proof payload for better clarity. Enhanced Security Measures: Strengthened security across the platform. keywords: credebl; proof; security cache: www-credebl-v2.0.0-major-updates-across-platform-studio-credo-controller-and-mobile-sdk?hs_amp=true.html plain text: www-credebl-v2.0.0-major-updates-across-platform-studio-credo-controller-and-mobile-sdk?hs_amp=true.txt item: #2627 of 3327 id: www-daml-smart-contracts-coming-to-hyperledger-sawtooth author: www title: www-daml-smart-contracts-coming-to-hyperledger-sawtooth date: None words: 1798 flesch: 47 summary: With a mapping between this abstraction layer and the specifics of a given platform, as BTP is developing for Hyperledger Sawtooth, DAML applications can be ported from platform to platform without complex rewrites. Today, we’re delighted to share that we have been working with fellow Hyperledger members, Blockchain Technology Partners (BTP), to integrate the DAML runtime with Hyperledger Sawtooth! keywords: code; daml; hyperledger; language; platform; sawtooth cache: www-daml-smart-contracts-coming-to-hyperledger-sawtooth.html plain text: www-daml-smart-contracts-coming-to-hyperledger-sawtooth.txt item: #2628 of 3327 id: www-daniela-barbosa-executive-director-and-julian-gordon-asia-pacific-and-middle-east-lf-decentralized-trust author: www title: www-daniela-barbosa-executive-director-and-julian-gordon-asia-pacific-and-middle-east-lf-decentralized-trust date: None words: 547 flesch: 18 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Blog | LF Decentralized Trust | Daniela Barbosa, Executive Director, and Julian Gordon, Asia Pacific and Middle East, LF Decentralized Trust 2025 Update: Off to a Fast Start! keywords: blog; decentralized; hyperledger; trust cache: www-daniela-barbosa-executive-director-and-julian-gordon-asia-pacific-and-middle-east-lf-decentralized-trust.html plain text: www-daniela-barbosa-executive-director-and-julian-gordon-asia-pacific-and-middle-east-lf-decentralized-trust.txt item: #2629 of 3327 id: www-daniela-barbosa-executive-director-at-hyperledger-foundation-and-general-manager-blockchain-and-identity-for-the-linux-foundation author: www title: www-daniela-barbosa-executive-director-at-hyperledger-foundation-and-general-manager-blockchain-and-identity-for-the-linux-foundation date: None words: 819 flesch: 18 summary: In case you missed it, the Linux Foundation recently announced the intent to form LF Decentralized... Read More Daniela Barbosa, Executive Director at Hyperledger Foundation and General Manager, Blockchain and Identity for the Linux Foundation | Jul 8, 2024 Hyperledger AnonCreds | Hyperledger Aries | Project: Hyperledger Indy | Staff Corner | Hyperledger Fabric Just Introduced: Refreshed Hyperledger Project Logos Last year, we introduced a new look for Hyperledger Foundation that fit with our increasingly mature market and ecosystem as well as our enterprise audience. Blog | LF Decentralized Trust | Daniela Barbosa, Executive Director at Hyperledger Foundation and General Manager, Blockchain and Identity for the Linux Foundation 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? keywords: foundation; hyperledger; identity; linux cache: www-daniela-barbosa-executive-director-at-hyperledger-foundation-and-general-manager-blockchain-and-identity-for-the-linux-foundation.html plain text: www-daniela-barbosa-executive-director-at-hyperledger-foundation-and-general-manager-blockchain-and-identity-for-the-linux-foundation.txt item: #2630 of 3327 id: www-daniela-barbosa-executive-director-of-lf-decentralized-trust author: www title: www-daniela-barbosa-executive-director-of-lf-decentralized-trust date: None words: 586 flesch: 22 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page | Oct 21, 2024 Staff Corner Welcome to Linux Foundation Decentralized Trust! keywords: blog; decentralized; hyperledger; trust cache: www-daniela-barbosa-executive-director-of-lf-decentralized-trust.html plain text: www-daniela-barbosa-executive-director-of-lf-decentralized-trust.txt item: #2631 of 3327 id: www-daniela-barbosa-general-manager-of-decentralized-technologies-at-the-linux-foundation-and-executive-director-of-lf-decentralized-trust author: www title: www-daniela-barbosa-general-manager-of-decentralized-technologies-at-the-linux-foundation-and-executive-director-of-lf-decentralized-trust date: None words: 619 flesch: 18 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Blog | LF Decentralized Trust | Daniela Barbosa, General Manager of Decentralized Technologies at the Linux Foundation and Executive Director of LF Decentralized Trust 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? keywords: decentralized; hyperledger; linux; technologies cache: www-daniela-barbosa-general-manager-of-decentralized-technologies-at-the-linux-foundation-and-executive-director-of-lf-decentralized-trust.html plain text: www-daniela-barbosa-general-manager-of-decentralized-technologies-at-the-linux-foundation-and-executive-director-of-lf-decentralized-trust.txt item: #2632 of 3327 id: www-data-model-considerations-in-hyperledger-sawtooth author: www title: www-data-model-considerations-in-hyperledger-sawtooth date: None words: 1669 flesch: 58 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog Data Model Considerations in Hyperledger Sawtooth Hyperledger | Jan 16, 2018 Guest post: Zac Delventhal, Hyperledger Sawtooth maintainer, Bitwise IO Hyperledger Sawtooth is an enterprise blockchain platform for building distributed ledger applications and networks. Data Model Considerations in Hyperledger Sawtooth – Hyperledger Foundation 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? keywords: characters; data; hyperledger; resource; sawtooth cache: www-data-model-considerations-in-hyperledger-sawtooth.html plain text: www-data-model-considerations-in-hyperledger-sawtooth.txt item: #2633 of 3327 id: www-dave-kelsey-hyperledger-caliper-maintainer author: www title: www-dave-kelsey-hyperledger-caliper-maintainer date: None words: 527 flesch: 15 summary: Next page > Submit a blog Blog guidelines RSS Hyperledger Caliper | Hyperledger Fabric Benchmarking Hyperledger Fabric 2.5 Performance Hyperledger Fabric performance is a question that comes up frequently as users try to compare it to... Read More Dave Kelsey, Hyperledger Caliper Maintainer | Feb 16, 2023 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. Blog | LF Decentralized Trust | Dave Kelsey, Hyperledger Caliper Maintainer 2025 keywords: blog; decentralized; hyperledger; technologies cache: www-dave-kelsey-hyperledger-caliper-maintainer.html plain text: www-dave-kelsey-hyperledger-caliper-maintainer.txt item: #2634 of 3327 id: www-david-boswe author: www title: www-david-boswe date: None words: 534 flesch: 9 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Besu Preparing for the Besu Certified Professional Exam: Tips, Resources, and a Discount Code The Linux Foundation recently launched the Besu Certified Professional exam to give people a way to... Read More David Boswell, Community Architect, LF Decentralized Trust | Apr 9, 2025 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; trust cache: www-david-boswe.html plain text: www-david-boswe.txt item: #2635 of 3327 id: www-decentralized-identity author: www title: www-decentralized-identity date: None words: 1589 flesch: 19 summary: Read More Ken Ebert and Keela Rose Shatzkin, Co-Chairs, Cardea Working Group | May 10, 2023 Hyperledger AnonCreds | Hyperledger Aries | Decentralized Identity Why Hyperledger Foundation Sponsors Internet Identity Workshop Since the launch of Hyperledger Indy, a DLT purpose-built for decentralized identity, in 2017, Hyperledger Foundation has been a proud sponsor, attendee and contributor to the... Read More Hyperledger | Apr 11, 2023 Hyperledger Community | Decentralized Identity Spotlighting #HyperledgerWomen: Stories from front lines of community building—Heather Dahl, Indicio To celebrate #HyperledgerWomen and their contributions to our community, we are asking a cross section of the many women leaders in our community to share stories about their... Read More Hyperledger | Mar 30, 2023 Blog | Decentralized Identity The Role of Decentralized Identity in Implementing the White House National Cybersecurity Strategy 2022 Hyperledger Aries | Developer Showcase | Project: Hyperledger Indy | Climate | Decentralized Identity Developer showcase series: Jason Sherman, Developer at Energy & Mines Digital Trust, Government of British Columbia Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. keywords: aries; decentralized; hyperledger; identity; indy; project cache: www-decentralized-identity.html plain text: www-decentralized-identity.txt item: #2636 of 3327 id: www-deon-a-hyperledger-based-decentralized-off-grid-network author: www title: www-deon-a-hyperledger-based-decentralized-off-grid-network date: None words: 1159 flesch: 37 summary: His research interests lie in enterprise blockchain networks, decentralized identity management, mesh networks and IoT.   Cover image by Pete Linforth from Pixabay View previous blog post Back to all blog posts View next blog post The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog | Hyperledger Aries | Project: Hyperledger Indy DEON: A Hyperledger-based DEcentralized Off-grid Network Jessica Rampen | Nov 5, 2020 The DEON project focuses on the application of blockchains to secure data sharing in private networks and was initiated in 2018 in the wireless and sensor networks laboratory at the Yale Institute for Network Science. keywords: decentralized; fabric; grid; identity; networks cache: www-deon-a-hyperledger-based-decentralized-off-grid-network.html plain text: www-deon-a-hyperledger-based-decentralized-off-grid-network.txt item: #2637 of 3327 id: www-deon-a-hyperledger-based-decentralized-off-grid-network?hs_amp=true author: www title: www-deon-a-hyperledger-based-decentralized-off-grid-network?hs_amp=true date: None words: 844 flesch: 43 summary: His research interests lie in enterprise blockchain networks, decentralized identity management, mesh networks and IoT.   Cover image by Pete Linforth from Pixabay View full post A Hyperledger-based DEcentralized Off-grid Network – Hyperledger Foundation Blog | LF Decentralized Trust DEON: A Hyperledger-based DEcentralized Off-grid Network – Hyperledger Foundation Written by Jessica Rampen | Nov 5, 2020 9:00:37 AM The DEON project focuses on the application of blockchains to secure data sharing in private networks and was initiated in 2018 in the wireless and sensor networks laboratory at the Yale Institute for Network Science. keywords: fabric; grid; networks cache: www-deon-a-hyperledger-based-decentralized-off-grid-network?hs_amp=true.html plain text: www-deon-a-hyperledger-based-decentralized-off-grid-network?hs_amp=true.txt item: #2638 of 3327 id: www-developer-showcase author: www title: www-developer-showcase date: None words: 1489 flesch: 39 summary: Read More Hyperledger Foundation | Jan 22, 2024 Hyperledger Aries | Developer Showcase | Hyperledger Fabric Developer Showcase Series: Harsh Multani, Blockchain Developer, Siemens Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. Read More Hyperledger Foundation | Jun 15, 2023 Hyperledger Aries | Developer Showcase | Project: Hyperledger Indy | Climate | Decentralized Identity Developer showcase series: Jason Sherman, Developer at Energy & Mines Digital Trust, Government of British Columbia Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. keywords: developer; hyperledger; series; showcase; world cache: www-developer-showcase.html plain text: www-developer-showcase.txt item: #2639 of 3327 id: www-developer-showcase-cody-burns-accenture author: www title: www-developer-showcase-cody-burns-accenture date: None words: 1525 flesch: 56 summary: I continued learning about it and expanded to other projects like ethereum and ethereum classic and, after getting my MBA, I decided it was time to move into enterprise level systems and began looking for leaders in the technology field with exposure to fortune 500 companies. From conversations and summits I’ve been involved with, I can say many enterprise companies are very interested in the technology and are looking for the right opportunities and partners to move forward. keywords: accenture; blockchain; enterprise; hyperledger; systems cache: www-developer-showcase-cody-burns-accenture.html plain text: www-developer-showcase-cody-burns-accenture.txt item: #2640 of 3327 id: www-developer-showcase-richard-phillips author: www title: www-developer-showcase-richard-phillips date: None words: 802 flesch: 49 summary: I would advise developers and others that are interested in blockchain tech to get some understanding of how blockchain and Hyperledger works. What is the best piece of developer advice you’ve ever received? “As a developer you create digital life, you alone have the power to conceive something that could change the world. keywords: blockchain; blog; hyperledger cache: www-developer-showcase-richard-phillips.html plain text: www-developer-showcase-richard-phillips.txt item: #2641 of 3327 id: www-developer-showcase-series-abhinav-garg-sofocle-technologies author: www title: www-developer-showcase-series-abhinav-garg-sofocle-technologies date: None words: 871 flesch: 47 summary: Abhinav Garg, blockchain developer, Sofocle Technologies Give a bit of background on what you’re working on, and let us know what was it that made you want to get into blockchain? What advice would you offer other technologists or developers interested in getting started working on blockchain? keywords: blockchain; hyperledger; technologies cache: www-developer-showcase-series-abhinav-garg-sofocle-technologies.html plain text: www-developer-showcase-series-abhinav-garg-sofocle-technologies.txt item: #2642 of 3327 id: www-developer-showcase-series-alvaro-picazo-haase-blockchain-engineer-accenture author: www title: www-developer-showcase-series-alvaro-picazo-haase-blockchain-engineer-accenture date: None words: 2266 flesch: 55 summary: Aparte de esto, te otorga la oportunidad de establecer nuevas conexiones y conocer a diferentes personas que son referencia en la tecnología y que pueden ser de ayuda en el futuro en tu carrera profesional. Realmente pienso que necesitan modernizarse y que Blockchain, de la mano de Hyperledger, puede sustituir o ayudar como complemento en muchas de las soluciones implementadas. keywords: accenture; bevel; blockchain; hyperledger; más; para; que; technologies; una cache: www-developer-showcase-series-alvaro-picazo-haase-blockchain-engineer-accenture.html plain text: www-developer-showcase-series-alvaro-picazo-haase-blockchain-engineer-accenture.txt item: #2643 of 3327 id: www-developer-showcase-series-alvaro-picazo-haase-blockchain-engineer-accenture?hs_amp=true author: www title: www-developer-showcase-series-alvaro-picazo-haase-blockchain-engineer-accenture?hs_amp=true date: None words: 1946 flesch: 59 summary: Aparte de esto, te otorga la oportunidad de establecer nuevas conexiones y conocer a diferentes personas que son referencia en la tecnología y que pueden ser de ayuda en el futuro en tu carrera profesional. Realmente pienso que necesitan modernizarse y que Blockchain, de la mano de Hyperledger, puede sustituir o ayudar como complemento en muchas de las soluciones implementadas. keywords: accenture; bevel; blockchain; hyperledger; más; para; que; una cache: www-developer-showcase-series-alvaro-picazo-haase-blockchain-engineer-accenture?hs_amp=true.html plain text: www-developer-showcase-series-alvaro-picazo-haase-blockchain-engineer-accenture?hs_amp=true.txt item: #2644 of 3327 id: www-developer-showcase-series-anitha-radhakrishnan-krypc-technologies author: www title: www-developer-showcase-series-anitha-radhakrishnan-krypc-technologies date: None words: 771 flesch: 42 summary: KrypCore is a managed service where one can easily manage Hyperledger Fabric networks, chaincode and channel management (supports both 1.4 and 2.x versions). How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Developer Showcase | Hyperledger Fabric Developer showcase series: Anitha Radhakrishnan, KrypC Technologies Hyperledger Foundation | Sep 2, 2021 Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. keywords: blockchain; hyperledger; technologies cache: www-developer-showcase-series-anitha-radhakrishnan-krypc-technologies.html plain text: www-developer-showcase-series-anitha-radhakrishnan-krypc-technologies.txt item: #2645 of 3327 id: www-developer-showcase-series-arielle-telesmanic-scroll author: www title: www-developer-showcase-series-arielle-telesmanic-scroll date: None words: 835 flesch: 40 summary: Although Blockchain technology originated as a fintech solution, I am more interested in identity management and data quality assurance use cases (specifically data validity). How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog | Developer Showcase | Hyperledger Composer Developer showcase series: Arielle Telesmanic, Scroll Hyperledger | Jan 8, 2019 Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. keywords: blockchain; data; hyperledger; technologies cache: www-developer-showcase-series-arielle-telesmanic-scroll.html plain text: www-developer-showcase-series-arielle-telesmanic-scroll.txt item: #2646 of 3327 id: www-developer-showcase-series-arielle-telesmanic-scroll?hs_amp=true author: www title: www-developer-showcase-series-arielle-telesmanic-scroll?hs_amp=true date: None words: 521 flesch: 48 summary: | LF Decentralized Trust Developer showcase series: Arielle Telesmanic, Scroll – Hyperledger Foundation Written by Hyperledger | Jan 8, 2019 9:00:26 AM Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. Although Blockchain technology originated as a fintech solution, I am more interested in identity management and data quality assurance use cases (specifically data validity). keywords: blockchain; hyperledger cache: www-developer-showcase-series-arielle-telesmanic-scroll?hs_amp=true.html plain text: www-developer-showcase-series-arielle-telesmanic-scroll?hs_amp=true.txt item: #2647 of 3327 id: www-developer-showcase-series-arka-roychowdhury-infosys author: www title: www-developer-showcase-series-arka-roychowdhury-infosys date: None words: 2149 flesch: 50 summary: These learnings will allow us to usher new generations of Blockchain technology without the technical limitations of today. Google Blockchain, and also visit MooCs such as Edx and Coursera. keywords: blockchain; blog; business; decentralized; hyperledger; project cache: www-developer-showcase-series-arka-roychowdhury-infosys.html plain text: www-developer-showcase-series-arka-roychowdhury-infosys.txt item: #2648 of 3327 id: www-developer-showcase-series-bruno-nascimento-staff-engineer-cheesecake-labs author: www title: www-developer-showcase-series-bruno-nascimento-staff-engineer-cheesecake-labs date: None words: 927 flesch: 45 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Developer Showcase | Besu Developer Showcase Series: Bruno Nascimento, Staff Engineer, Cheesecake Labs LF Decentralized Trust | Mar 17, 2025 Back to our Developer Showcase Series to learn what developers in the real world are doing with LF Decentralized Trust technologies. I contributed to the community by helping create the Certified Besu Professional exam, applying my expertise to craft and review exam questions, ensuring high-quality standards for developers looking to demonstrate their skills with the open source Ethereum client, a project of LF Decentralized Trust. keywords: community; decentralized; trust cache: www-developer-showcase-series-bruno-nascimento-staff-engineer-cheesecake-labs.html plain text: www-developer-showcase-series-bruno-nascimento-staff-engineer-cheesecake-labs.txt item: #2649 of 3327 id: www-developer-showcase-series-bruno-nascimento-staff-engineer-cheesecake-labs?hs_amp=true author: www title: www-developer-showcase-series-bruno-nascimento-staff-engineer-cheesecake-labs?hs_amp=true date: None words: 614 flesch: 52 summary: Developer Showcase Series: Bruno Nascimento, Staff Engineer, Cheesecake Labs Blog | LF Decentralized Trust Developer Showcase Series: Bruno Nascimento, Staff Engineer, Cheesecake Labs Written by LF Decentralized Trust | Mar 17, 2025 2:38:06 PM Back to our Developer Showcase Series to learn what developers in the real world are doing with LF Decentralized Trust technologies. I contributed to the community by helping create the Certified Besu Professional exam, applying my expertise to craft and review exam questions, ensuring high-quality standards for developers looking to demonstrate their skills with the open source Ethereum client, a project of LF Decentralized Trust. keywords: trust cache: www-developer-showcase-series-bruno-nascimento-staff-engineer-cheesecake-labs?hs_amp=true.html plain text: www-developer-showcase-series-bruno-nascimento-staff-engineer-cheesecake-labs?hs_amp=true.txt item: #2650 of 3327 id: www-developer-showcase-series-christopher-cordi-splunk author: www title: www-developer-showcase-series-christopher-cordi-splunk date: None words: 925 flesch: 43 summary: I am currently working on the Splunk App for Hyperledger Fabric, which enables the real-time infrastructure and security monitoring of Hyperledger Fabric networks. How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Developer Showcase | Hyperledger Fabric Developer showcase series: Christopher Cordi, Splunk Hyperledger Foundation | Oct 26, 2021 Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. keywords: blockchain; hyperledger; security; technologies cache: www-developer-showcase-series-christopher-cordi-splunk.html plain text: www-developer-showcase-series-christopher-cordi-splunk.txt item: #2651 of 3327 id: www-developer-showcase-series-daniel-bluhm-indicio author: www title: www-developer-showcase-series-daniel-bluhm-indicio date: None words: 1196 flesch: 59 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger Aries | Developer Showcase | Project: Hyperledger Indy | Decentralized Identity Developer showcase series: Daniel Bluhm, Indicio Hyperledger Foundation | Jul 21, 2022 Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. I would also really like to see a focus on encouraging more interaction with the Hyperledger Indy project, especially after seeing how positively this affects our work with Hyperledger Aries. keywords: blockchain; hyperledger; project; technologies cache: www-developer-showcase-series-daniel-bluhm-indicio.html plain text: www-developer-showcase-series-daniel-bluhm-indicio.txt item: #2652 of 3327 id: www-developer-showcase-series-daniel-bluhm-indicio?hs_amp=true author: www title: www-developer-showcase-series-daniel-bluhm-indicio?hs_amp=true date: None words: 877 flesch: 70 summary: Developer showcase series: Daniel Bluhm, Indicio – Hyperledger Foundation Blog | LF Decentralized Trust Developer showcase series: Daniel Bluhm, Indicio – Hyperledger Foundation Written by Hyperledger Foundation | Jul 21, 2022 9:00:00 AM Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. I would also really like to see a focus on encouraging more interaction with the Hyperledger Indy project, especially after seeing how positively this affects our work with Hyperledger Aries. keywords: blockchain; hyperledger cache: www-developer-showcase-series-daniel-bluhm-indicio?hs_amp=true.html plain text: www-developer-showcase-series-daniel-bluhm-indicio?hs_amp=true.txt item: #2653 of 3327 id: www-developer-showcase-series-daniel-szego-independent-dlt-architect author: www title: www-developer-showcase-series-daniel-szego-independent-dlt-architect date: None words: 759 flesch: 49 summary: I must say Hyperledger is still the most open community focusing strongly on enterprise blockchains. These fields, like blockchain or enterprise blockchains, are so complex that they can be evolved only as a result of open-source, worldwide contribution. keywords: blockchain; community; hyperledger cache: www-developer-showcase-series-daniel-szego-independent-dlt-architect.html plain text: www-developer-showcase-series-daniel-szego-independent-dlt-architect.txt item: #2654 of 3327 id: www-developer-showcase-series-daniel-szego-independent-dlt-architect?hs_amp=true author: www title: www-developer-showcase-series-daniel-szego-independent-dlt-architect?hs_amp=true date: None words: 448 flesch: 61 summary: Developer Showcase Series: Daniel Szego, Independent DLT Architect – Hyperledger Foundation Blog | LF Decentralized Trust Developer Showcase Series: Daniel Szego, Independent DLT Architect – Hyperledger Foundation Written by Hyperledger Foundation | Jun 27, 2023 8:30:00 AM Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. I must say Hyperledger is still the most open community focusing strongly on enterprise blockchains. keywords: hyperledger cache: www-developer-showcase-series-daniel-szego-independent-dlt-architect?hs_amp=true.html plain text: www-developer-showcase-series-daniel-szego-independent-dlt-architect?hs_amp=true.txt item: #2655 of 3327 id: www-developer-showcase-series-david-conroy-national-association-of-realtors author: www title: www-developer-showcase-series-david-conroy-national-association-of-realtors date: None words: 1137 flesch: 43 summary: My two favorite development tools currently are Hyperledger Composer (https://github.com/hyperledger/composer), and the Truffle Framework (http://truffleframework.com/). Locally, I serve as co-chair of the two Chicago-based blockchain meetups, Hyperledger Chicago & Chicago Blockchain in Real Estate. keywords: association; blockchain; hyperledger; project cache: www-developer-showcase-series-david-conroy-national-association-of-realtors.html plain text: www-developer-showcase-series-david-conroy-national-association-of-realtors.txt item: #2656 of 3327 id: www-developer-showcase-series-david-conroy-national-association-of-realtors?hs_amp=true author: www title: www-developer-showcase-series-david-conroy-national-association-of-realtors?hs_amp=true date: None words: 823 flesch: 49 summary: Locally, I serve as co-chair of the two Chicago-based blockchain meetups, Hyperledger Chicago & Chicago Blockchain in Real Estate. My two favorite development tools currently are Hyperledger Composer (https://github.com/hyperledger/composer), and the Truffle Framework (http://truffleframework.com/). keywords: association; blockchain; hyperledger cache: www-developer-showcase-series-david-conroy-national-association-of-realtors?hs_amp=true.html plain text: www-developer-showcase-series-david-conroy-national-association-of-realtors?hs_amp=true.txt item: #2657 of 3327 id: www-developer-showcase-series-dr-yunxi-zhang-accenture author: www title: www-developer-showcase-series-dr-yunxi-zhang-accenture date: None words: 1124 flesch: 45 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger Aries | Developer Showcase Developer showcase series: Dr. Yunxi Zhang, Accenture Hyperledger Foundation | Jun 16, 2022 Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. Hyperledger technologies are built upon the basic concept of how blockchain works, but they each implement it in its own ways to provision enough flexibility for different use cases. keywords: blockchain; hyperledger; technologies; use cache: www-developer-showcase-series-dr-yunxi-zhang-accenture.html plain text: www-developer-showcase-series-dr-yunxi-zhang-accenture.txt item: #2658 of 3327 id: www-developer-showcase-series-dr-yunxi-zhang-accenture?hs_amp=true author: www title: www-developer-showcase-series-dr-yunxi-zhang-accenture?hs_amp=true date: None words: 812 flesch: 53 summary: | LF Decentralized Trust Developer showcase series: Dr. Yunxi Zhang, Accenture – Hyperledger Foundation Written by Hyperledger Foundation | Jun 16, 2022 9:00:00 AM Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. Hyperledger technologies are built upon the basic concept of how blockchain works, but they each implement it in its own ways to provision enough flexibility for different use cases. keywords: blockchain; hyperledger cache: www-developer-showcase-series-dr-yunxi-zhang-accenture?hs_amp=true.html plain text: www-developer-showcase-series-dr-yunxi-zhang-accenture?hs_amp=true.txt item: #2659 of 3327 id: www-developer-showcase-series-edmund-industrieco author: www title: www-developer-showcase-series-edmund-industrieco date: None words: 1009 flesch: 45 summary: I hope to see blockchain technology helping to increase transparency in organizations, in particular,  the non-profit space. It is important to understand how consensus algorithms are being implemented, in particular, how permissioned blockchains, like Hyperledger Fabric, which uses Practical Byzantine Fault Tolerance Algorithm by default, differs from public blockchain implementations such as Bitcoin and Ethereum, which use Proof of Work. keywords: blockchain; decentralized; hyperledger; technologies cache: www-developer-showcase-series-edmund-industrieco.html plain text: www-developer-showcase-series-edmund-industrieco.txt item: #2660 of 3327 id: www-developer-showcase-series-edmund-industrieco?hs_amp=true author: www title: www-developer-showcase-series-edmund-industrieco?hs_amp=true date: None words: 695 flesch: 53 summary: I hope to see blockchain technology helping to increase transparency in organizations, in particular,  the non-profit space. Give a bit of background on what you’re working on, and let us know what was it that made you want to get into blockchain? keywords: blockchain; hyperledger cache: www-developer-showcase-series-edmund-industrieco?hs_amp=true.html plain text: www-developer-showcase-series-edmund-industrieco?hs_amp=true.txt item: #2661 of 3327 id: www-developer-showcase-series-enrico-zanardo-onezero-binary-ltd author: www title: www-developer-showcase-series-enrico-zanardo-onezero-binary-ltd date: None words: 845 flesch: 45 summary: I personally suggest that everybody interested in blockchain technology try at least one course provided by B9lab simply because they are able to teach sophisticated tools like Hyperledger Fabric in a simple way, and they are always ready to help their students during (and after) the course. We needed to connect and share information between multiple entities like hospitals, emergency services, first responder organisations such as the Red Cross, White Cross, etc… so Hyperledger Fabric was the best choice. keywords: blog; decentralized; hyperledger; technologies cache: www-developer-showcase-series-enrico-zanardo-onezero-binary-ltd.html plain text: www-developer-showcase-series-enrico-zanardo-onezero-binary-ltd.txt item: #2662 of 3327 id: www-developer-showcase-series-fernando-paris-co-ceo-and-cto-iobuilders author: www title: www-developer-showcase-series-fernando-paris-co-ceo-and-cto-iobuilders date: None words: 995 flesch: 42 summary: This active participation underscores our dedication to nurturing a vibrant ecosystem around Hyperledger technologies. How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Developer Showcase Developer Showcase Series: Fernando Paris, Co-CEO and CTO, ioBuilders Hyperledger Foundation | Jan 22, 2024 Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. keywords: community; foundation; hyperledger; technologies cache: www-developer-showcase-series-fernando-paris-co-ceo-and-cto-iobuilders.html plain text: www-developer-showcase-series-fernando-paris-co-ceo-and-cto-iobuilders.txt item: #2663 of 3327 id: www-developer-showcase-series-fernando-paris-co-ceo-and-cto-iobuilders?hs_amp=true author: www title: www-developer-showcase-series-fernando-paris-co-ceo-and-cto-iobuilders?hs_amp=true date: None words: 684 flesch: 48 summary: This active participation underscores our dedication to nurturing a vibrant ecosystem around Hyperledger technologies. Developer Showcase Series: Fernando Paris, Co-CEO and CTO, ioBuilders Blog | LF Decentralized Trust Developer Showcase Series: Fernando Paris, Co-CEO and CTO, ioBuilders Written by Hyperledger Foundation | Jan 22, 2024 2:34:31 PM Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. keywords: community; hyperledger cache: www-developer-showcase-series-fernando-paris-co-ceo-and-cto-iobuilders?hs_amp=true.html plain text: www-developer-showcase-series-fernando-paris-co-ceo-and-cto-iobuilders?hs_amp=true.txt item: #2664 of 3327 id: www-developer-showcase-series-harsh-multani-blockchain-developer-siemens author: www title: www-developer-showcase-series-harsh-multani-blockchain-developer-siemens date: None words: 820 flesch: 50 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger Aries | Developer Showcase | Hyperledger Fabric Developer Showcase Series: Harsh Multani, Blockchain Developer, Siemens Hyperledger Foundation | Nov 20, 2023 Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. Furthermore, I have been a speaker at Hyperledger Mentorship Showcase events, explaining the potential of these functionalities to business domain experts. keywords: blockchain; developer; hyperledger cache: www-developer-showcase-series-harsh-multani-blockchain-developer-siemens.html plain text: www-developer-showcase-series-harsh-multani-blockchain-developer-siemens.txt item: #2665 of 3327 id: www-developer-showcase-series-harsh-multani-blockchain-developer-siemens?hs_amp=true author: www title: www-developer-showcase-series-harsh-multani-blockchain-developer-siemens?hs_amp=true date: None words: 503 flesch: 62 summary: One is a realization of an endorser protocol to Aries Cloud-agent Python and the other is an amalgamation of Hyperledger Aries to support Hyperledger Fabric as a ledger. Developer Showcase Series: Harsh Multani, Blockchain Developer, Siemens Blog | LF Decentralized Trust Developer Showcase Series: Harsh Multani, Blockchain Developer, Siemens Written by Hyperledger Foundation | Nov 20, 2023 4:13:47 PM Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. keywords: developer; hyperledger cache: www-developer-showcase-series-harsh-multani-blockchain-developer-siemens?hs_amp=true.html plain text: www-developer-showcase-series-harsh-multani-blockchain-developer-siemens?hs_amp=true.txt item: #2666 of 3327 id: www-developer-showcase-series-hitesh-fuletra-save-on-foods author: www title: www-developer-showcase-series-hitesh-fuletra-save-on-foods date: None words: 783 flesch: 42 summary: Encourage more real-time use of Hyperledger platform.  Developer Showcase Series: Hitesh Fuletra, Save-On-Foods – Hyperledger Foundation 2025 Update: Off to a Fast Start! keywords: blockchain; hyperledger; technologies cache: www-developer-showcase-series-hitesh-fuletra-save-on-foods.html plain text: www-developer-showcase-series-hitesh-fuletra-save-on-foods.txt item: #2667 of 3327 id: www-developer-showcase-series-hitesh-fuletra-save-on-foods?hs_amp=true author: www title: www-developer-showcase-series-hitesh-fuletra-save-on-foods?hs_amp=true date: None words: 469 flesch: 53 summary: Encourage more real-time use of Hyperledger platform.  Developer Showcase Series: Hitesh Fuletra, Save-On-Foods – Hyperledger Foundation Blog | LF Decentralized Trust Developer Showcase Series: Hitesh Fuletra, Save-On-Foods – Hyperledger Foundation Written by Hyperledger | May 2, 2018 9:00:57 AM Image: Hitesh Fuletra, Save-On-Foods – a division of the Overwaitea Food Group Next up in our Developer Showcase blog series is Hitesh Fuletra, a system analyst at Save-On-Foods – a division of the Overwaitea Food Group. keywords: hyperledger cache: www-developer-showcase-series-hitesh-fuletra-save-on-foods?hs_amp=true.html plain text: www-developer-showcase-series-hitesh-fuletra-save-on-foods?hs_amp=true.txt item: #2668 of 3327 id: www-developer-showcase-series-ian-costanzo-anon-solutions-inc author: www title: www-developer-showcase-series-ian-costanzo-anon-solutions-inc date: None words: 1637 flesch: 54 summary: I’ve worked with Hyperledger Fabric and Hyperledger Indy, and I think anyone will agree that these are very complex technologies!   I’m working with the BC Government on their Verifiable Organizations Network (VON) project (https://github.com/bcgov/von) using Hyperledger Indy. keywords: blockchain; hyperledger; project; technology; work cache: www-developer-showcase-series-ian-costanzo-anon-solutions-inc.html plain text: www-developer-showcase-series-ian-costanzo-anon-solutions-inc.txt item: #2669 of 3327 id: www-developer-showcase-series-ian-costanzo-anon-solutions-inc?hs_amp=true author: www title: www-developer-showcase-series-ian-costanzo-anon-solutions-inc?hs_amp=true date: None words: 1323 flesch: 59 summary: I’ve worked with Hyperledger Fabric and Hyperledger Indy, and I think anyone will agree that these are very complex technologies!   I’m working with the BC Government on their Verifiable Organizations Network (VON) project (https://github.com/bcgov/von) using Hyperledger Indy. keywords: blockchain; hyperledger; technology cache: www-developer-showcase-series-ian-costanzo-anon-solutions-inc?hs_amp=true.html plain text: www-developer-showcase-series-ian-costanzo-anon-solutions-inc?hs_amp=true.txt item: #2670 of 3327 id: www-developer-showcase-series-jason-sherman-developer-at-energy-mines-digital-trust-government-of-british-columbia author: www title: www-developer-showcase-series-jason-sherman-developer-at-energy-mines-digital-trust-government-of-british-columbia date: None words: 925 flesch: 43 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger Aries | Developer Showcase | Project: Hyperledger Indy | Climate | Decentralized Identity Developer showcase series: Jason Sherman, Developer at Energy & Mines Digital Trust, Government of British Columbia Hyperledger Foundation | Sep 2, 2022 Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. My experience with Hyperledger technologies is that things change quickly! keywords: developer; digital; hyperledger; technologies cache: www-developer-showcase-series-jason-sherman-developer-at-energy-mines-digital-trust-government-of-british-columbia.html plain text: www-developer-showcase-series-jason-sherman-developer-at-energy-mines-digital-trust-government-of-british-columbia.txt item: #2671 of 3327 id: www-developer-showcase-series-jason-sherman-developer-at-energy-mines-digital-trust-government-of-british-columbia?hs_amp=true author: www title: www-developer-showcase-series-jason-sherman-developer-at-energy-mines-digital-trust-government-of-british-columbia?hs_amp=true date: None words: 604 flesch: 52 summary: | Sep 2, 2022 9:00:00 AM Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. My experience with Hyperledger technologies is that things change quickly! keywords: digital; hyperledger cache: www-developer-showcase-series-jason-sherman-developer-at-energy-mines-digital-trust-government-of-british-columbia?hs_amp=true.html plain text: www-developer-showcase-series-jason-sherman-developer-at-energy-mines-digital-trust-government-of-british-columbia?hs_amp=true.txt item: #2672 of 3327 id: www-developer-showcase-series-john-greenhow-peloton-blockchain author: www title: www-developer-showcase-series-john-greenhow-peloton-blockchain date: None words: 1568 flesch: 54 summary: Best of breed flagship – rolling together the (stable) killer features of different Hyperledger projects into a commodity enterprise project could reduce the risk stemming from dependency upon a single project and provide a single point of entry into the Hyperledger world for teams focused on solutions rather than platform evaluation. Blockchain Network – based on Hyperledger Fabric, this is a private, secure and scalable network designed to provide unparalleled breadth of distribution to issuers and lead arrangers; chain-code manages compliance and the full security lifecycle – we’ve built RESTful APIs to facilitate connectivity into crypto-exchanges and secure “nodes” for deployment. keywords: blockchain; decentralized; hyperledger; network; project cache: www-developer-showcase-series-john-greenhow-peloton-blockchain.html plain text: www-developer-showcase-series-john-greenhow-peloton-blockchain.txt item: #2673 of 3327 id: www-developer-showcase-series-john-greenhow-peloton-blockchain?hs_amp=true author: www title: www-developer-showcase-series-john-greenhow-peloton-blockchain?hs_amp=true date: None words: 1254 flesch: 60 summary: Blockchain Network – based on Hyperledger Fabric, this is a private, secure and scalable network designed to provide unparalleled breadth of distribution to issuers and lead arrangers; chain-code manages compliance and the full security lifecycle – we’ve built RESTful APIs to facilitate connectivity into crypto-exchanges and secure “nodes” for deployment. Blockchain in general, and specifically Hyperledger Fabric, provided the best platform upon which we could build. keywords: blockchain; hyperledger; network cache: www-developer-showcase-series-john-greenhow-peloton-blockchain?hs_amp=true.html plain text: www-developer-showcase-series-john-greenhow-peloton-blockchain?hs_amp=true.txt item: #2674 of 3327 id: www-developer-showcase-series-kamlesh-nagware-snapper-future-tech author: www title: www-developer-showcase-series-kamlesh-nagware-snapper-future-tech date: None words: 1447 flesch: 52 summary: It will be fantastic to see Aries supporting other Hyperledger projects like Fabric. I think there should be more focus on cross-Hyperledger project collaboration for interoperability between different Hyperledger projects. keywords: blockchain; fabric; hyperledger; project; use cache: www-developer-showcase-series-kamlesh-nagware-snapper-future-tech.html plain text: www-developer-showcase-series-kamlesh-nagware-snapper-future-tech.txt item: #2675 of 3327 id: www-developer-showcase-series-karthik-mohan-krypc-technologies author: www title: www-developer-showcase-series-karthik-mohan-krypc-technologies date: None words: 1198 flesch: 49 summary: I learned a lot during the design and development of our managed services and still continue to learn as cloud native development of blockchain systems, especially Hyperledger Fabric, is still a long way from being perfect. At the start, we advocated using Hyperledger projects for enterprise use cases. keywords: blockchain; developer; fabric; hyperledger; technologies cache: www-developer-showcase-series-karthik-mohan-krypc-technologies.html plain text: www-developer-showcase-series-karthik-mohan-krypc-technologies.txt item: #2676 of 3327 id: www-developer-showcase-series-luc-yriarte-zinedine-hasni-chainorchestra author: www title: www-developer-showcase-series-luc-yriarte-zinedine-hasni-chainorchestra date: None words: 1695 flesch: 55 summary: We figured that since we’d be deploying and managing blockchain networks for the IoT, we might as well do the same for the other use-cases. I’m the lead engineer for ChainOrchestra, a start-up focused on blockchain network deployment and operation. keywords: blockchain; hyperledger; network; use; zinedine cache: www-developer-showcase-series-luc-yriarte-zinedine-hasni-chainorchestra.html plain text: www-developer-showcase-series-luc-yriarte-zinedine-hasni-chainorchestra.txt item: #2677 of 3327 id: www-developer-showcase-series-luc-yriarte-zinedine-hasni-chainorchestra?hs_amp=true author: www title: www-developer-showcase-series-luc-yriarte-zinedine-hasni-chainorchestra?hs_amp=true date: None words: 1381 flesch: 61 summary: We figured that since we’d be deploying and managing blockchain networks for the IoT, we might as well do the same for the other use-cases. I’m the lead engineer for ChainOrchestra, a start-up focused on blockchain network deployment and operation. keywords: blockchain; hyperledger; network; zinedine cache: www-developer-showcase-series-luc-yriarte-zinedine-hasni-chainorchestra?hs_amp=true.html plain text: www-developer-showcase-series-luc-yriarte-zinedine-hasni-chainorchestra?hs_amp=true.txt item: #2678 of 3327 id: www-developer-showcase-series-lucas-saldanha-consensys author: www title: www-developer-showcase-series-lucas-saldanha-consensys date: None words: 1144 flesch: 59 summary: Regarding Hyperledger projects, my hands-on experience is limited to Besu. I hope to see Hyperledger projects being the number one option for everyone when it comes to blockchain technology. keywords: blockchain; hyperledger; projects; technologies cache: www-developer-showcase-series-lucas-saldanha-consensys.html plain text: www-developer-showcase-series-lucas-saldanha-consensys.txt item: #2679 of 3327 id: www-developer-showcase-series-markus-sabadello-danube-tech author: www title: www-developer-showcase-series-markus-sabadello-danube-tech date: None words: 1216 flesch: 49 summary: With blockchain or distributed ledger technology, we realize that now for the first time we have a way to establish digital identity without such dependencies on identity service providers. I have worked on digital identity technologies for a long time, the question of who we are, how we present ourselves, and what do others know about us in the digital world. keywords: blockchain; decentralized; hyperledger; identity cache: www-developer-showcase-series-markus-sabadello-danube-tech.html plain text: www-developer-showcase-series-markus-sabadello-danube-tech.txt item: #2680 of 3327 id: www-developer-showcase-series-matt-zand-author-and-hashflow-ceo author: www title: www-developer-showcase-series-matt-zand-author-and-hashflow-ceo date: None words: 1026 flesch: 49 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Developer Showcase | Hyperledger Fabric Developer showcase series: Matt Zand, author and HashFlow CEO Hyperledger Foundation | Oct 6, 2021 Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. Can you sum up your experience with Hyperledger? NFT for financial products with Hyperledger Fabric, asset tokenization for digital banks with Hyperledger Fabric and Ethereum, B2B NFT in music industry, a SaaS product for customer loyalty management, healthcare payment system, an ICO product and an internet-connectivity reward system for the telecom industry just to name a few. keywords: blockchain; fabric; hyperledger; technologies cache: www-developer-showcase-series-matt-zand-author-and-hashflow-ceo.html plain text: www-developer-showcase-series-matt-zand-author-and-hashflow-ceo.txt item: #2681 of 3327 id: www-developer-showcase-series-matthew-b-white-ibm author: www title: www-developer-showcase-series-matthew-b-white-ibm date: None words: 1013 flesch: 58 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Developer Showcase | Hyperledger Fabric Developer showcase series: Matthew B. White, IBM Hyperledger Foundation | May 9, 2022 Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. It’s this collaboration that is key to blockchain and needs to remain a focus as Hyperledger technologies are adopted more widely. keywords: blockchain; foundation; hyperledger; technologies cache: www-developer-showcase-series-matthew-b-white-ibm.html plain text: www-developer-showcase-series-matthew-b-white-ibm.txt item: #2682 of 3327 id: www-developer-showcase-series-matthew-b-white-ibm?hs_amp=true author: www title: www-developer-showcase-series-matthew-b-white-ibm?hs_amp=true date: None words: 701 flesch: 71 summary: | LF Decentralized Trust Developer showcase series: Matthew B. White, IBM – Hyperledger Foundation Written by Hyperledger Foundation | May 9, 2022 8:15:59 AM Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. It’s this collaboration that is key to blockchain and needs to remain a focus as Hyperledger technologies are adopted more widely. keywords: blockchain; hyperledger cache: www-developer-showcase-series-matthew-b-white-ibm?hs_amp=true.html plain text: www-developer-showcase-series-matthew-b-white-ibm?hs_amp=true.txt item: #2683 of 3327 id: www-developer-showcase-series-navil-rodrigues-coding-bootcamps author: www title: www-developer-showcase-series-navil-rodrigues-coding-bootcamps date: None words: 910 flesch: 48 summary: Apr 26, 2022 Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. Can you sum up your experience with Hyperledger technologies? keywords: blockchain; foundation; hyperledger; technologies cache: www-developer-showcase-series-navil-rodrigues-coding-bootcamps.html plain text: www-developer-showcase-series-navil-rodrigues-coding-bootcamps.txt item: #2684 of 3327 id: www-developer-showcase-series-nidhi-singh-walmart-global-tech author: www title: www-developer-showcase-series-nidhi-singh-walmart-global-tech date: None words: 1101 flesch: 51 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Developer Showcase | Labs Developer Showcase Series: Nidhi Singh, Walmart Global Tech Hyperledger Foundation | Jun 15, 2023 Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. I started my journey with Hyperledger projects as part of my previous job – building a highly scalable, cross organization network that is impacting a billion cellular subscribers in India. keywords: community; foundation; hyperledger; project cache: www-developer-showcase-series-nidhi-singh-walmart-global-tech.html plain text: www-developer-showcase-series-nidhi-singh-walmart-global-tech.txt item: #2685 of 3327 id: www-developer-showcase-series-nidhi-singh-walmart-global-tech?hs_amp=true author: www title: www-developer-showcase-series-nidhi-singh-walmart-global-tech?hs_amp=true date: None words: 790 flesch: 58 summary: Developer Showcase Series: Nidhi Singh, Walmart Global Tech – Hyperledger Foundation Blog | LF Decentralized Trust Developer Showcase Series: Nidhi Singh, Walmart Global Tech – Hyperledger Foundation Written by Hyperledger Foundation | Jun 15, 2023 7:30:00 AM Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. I started my journey with Hyperledger projects as part of my previous job – building a highly scalable, cross organization network that is impacting a billion cellular subscribers in India. keywords: community; hyperledger cache: www-developer-showcase-series-nidhi-singh-walmart-global-tech?hs_amp=true.html plain text: www-developer-showcase-series-nidhi-singh-walmart-global-tech?hs_amp=true.txt item: #2686 of 3327 id: www-developer-showcase-series-nithin-pankaj-senior-software-engineer-walmart author: www title: www-developer-showcase-series-nithin-pankaj-senior-software-engineer-walmart date: None words: 1120 flesch: 42 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Developer Showcase | Project: Hyperledger Indy | Labs | Mentorship Program Developer Showcase Series: Nithin Pankaj, Senior Software Engineer, Walmart Hyperledger Foundation | Jun 17, 2024 Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. Hyperledger Foundation is making strides towards ensuring seamless interaction between different blockchain platforms, which is a critical requirement for a very broad-based blockchain adoption. keywords: decentralized; hyperledger; platform; walmart cache: www-developer-showcase-series-nithin-pankaj-senior-software-engineer-walmart.html plain text: www-developer-showcase-series-nithin-pankaj-senior-software-engineer-walmart.txt item: #2687 of 3327 id: www-developer-showcase-series-nithin-pankaj-senior-software-engineer-walmart?hs_amp=true author: www title: www-developer-showcase-series-nithin-pankaj-senior-software-engineer-walmart?hs_amp=true date: None words: 800 flesch: 47 summary: Developer Showcase Series: Nithin Pankaj, Senior Software Engineer, Walmart Blog | LF Decentralized Trust Developer Showcase Series: Nithin Pankaj, Senior Software Engineer, Walmart Written by Hyperledger Foundation | Jun 17, 2024 3:03:18 PM Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. Alongside this, the ongoing enhancements to Hyperledger Fabric and emerging use cases in Fintech space like CBDCs and tokenized securities are also noteworthy. keywords: hyperledger; platform; walmart cache: www-developer-showcase-series-nithin-pankaj-senior-software-engineer-walmart?hs_amp=true.html plain text: www-developer-showcase-series-nithin-pankaj-senior-software-engineer-walmart?hs_amp=true.txt item: #2688 of 3327 id: www-developer-showcase-series-peter-somogyvari-accenture author: www title: www-developer-showcase-series-peter-somogyvari-accenture date: None words: 918 flesch: 50 summary: Can you sum up your experience with Hyperledger? Hyperledger Besu and Hyperledger Fabric: Part of my duties while working on Cactus is to design and build ledger connectors for them and figure out a way to make it easy for our prospective contributors to get going while developing against these ledgers, through Cactus. How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog | Developer Showcase Developer Showcase Series: Peter Somogyvari, Accenture Hyperledger | Feb 1, 2021 Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. keywords: blockchain; decentralized; hyperledger; technologies cache: www-developer-showcase-series-peter-somogyvari-accenture.html plain text: www-developer-showcase-series-peter-somogyvari-accenture.txt item: #2689 of 3327 id: www-developer-showcase-series-raj-sadaye author: www title: www-developer-showcase-series-raj-sadaye date: None words: 1116 flesch: 46 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog | Developer Showcase | Hyperledger Composer Developer showcase series: Raj Sadaye, Arizona State University Hyperledger | Feb 6, 2019 Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. Everledger rewires trust and confidence in a previously broken market by building consortiums of actors participating and maintaining provenance by supplementing blockchain technology with various other verification techniques. keywords: blockchain; hyperledger; project; technology cache: www-developer-showcase-series-raj-sadaye.html plain text: www-developer-showcase-series-raj-sadaye.txt item: #2690 of 3327 id: www-developer-showcase-series-raj-sadaye?hs_amp=true author: www title: www-developer-showcase-series-raj-sadaye?hs_amp=true date: None words: 802 flesch: 53 summary: Primarily, I’ve been working with Hyperledger Fabric and Hyperledger Composer and overall, the experience has been really good. Hyperledger Composer is a tool that excited me the most over the last 8 month because it runs on top of Hyperledger Fabric and it can help a blockchain novice on how to build a distributed application. keywords: blockchain; hyperledger cache: www-developer-showcase-series-raj-sadaye?hs_amp=true.html plain text: www-developer-showcase-series-raj-sadaye?hs_amp=true.txt item: #2691 of 3327 id: www-developer-showcase-series-rohit-aneja-bristlecone-labs author: www title: www-developer-showcase-series-rohit-aneja-bristlecone-labs date: None words: 1292 flesch: 49 summary: Availability of production ready system that has high security and scalability in such early stages of blockchain technology is a bliss for developers. Keeping focus in improving such tools will really drive a large base towards Hyperledger framework. keywords: blockchain; hyperledger; network; use cache: www-developer-showcase-series-rohit-aneja-bristlecone-labs.html plain text: www-developer-showcase-series-rohit-aneja-bristlecone-labs.txt item: #2692 of 3327 id: www-developer-showcase-series-rohit-aneja-bristlecone-labs?hs_amp=true author: www title: www-developer-showcase-series-rohit-aneja-bristlecone-labs?hs_amp=true date: None words: 978 flesch: 56 summary: Keeping focus in improving such tools will really drive a large base towards Hyperledger framework. Currently, I am developing a business network on Hyperledger Composer, although it’s in early stage of its development, it will be mostly a network of networks that will have suppliers identify an optimised supply path as well as have competitive advantage for being on a network than suppliers playing alone. keywords: blockchain; hyperledger cache: www-developer-showcase-series-rohit-aneja-bristlecone-labs?hs_amp=true.html plain text: www-developer-showcase-series-rohit-aneja-bristlecone-labs?hs_amp=true.txt item: #2693 of 3327 id: www-developer-showcase-series-sam-curren-indicio author: www title: www-developer-showcase-series-sam-curren-indicio date: None words: 875 flesch: 51 summary: Can you sum up your experience with Hyperledger? I use Hyperledger Indy and Hyperledger Aries day to day, looking forward to the finalization of Didcomm v2 and helping the Aries community adopt it. How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger Aries | Developer Showcase | Decentralized Identity Developer showcase series: Sam Curren, Indicio Hyperledger Foundation | Jan 26, 2022 Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. keywords: foundation; hyperledger; project cache: www-developer-showcase-series-sam-curren-indicio.html plain text: www-developer-showcase-series-sam-curren-indicio.txt item: #2694 of 3327 id: www-developer-showcase-series-santiago-casaliglla-dnasmartbits author: www title: www-developer-showcase-series-santiago-casaliglla-dnasmartbits date: None words: 1263 flesch: 44 summary: Six months ago I was researching how blockchain technologies can provide transparency to their participants while making efficient transactions and being scalable. What’s the one issue or problem you hope blockchain can solve? I am hoping we’ll see blockchain technology bring transparency to property ownership, government and individual identification in the next five years. keywords: blockchain; blog; decentralized; hyperledger cache: www-developer-showcase-series-santiago-casaliglla-dnasmartbits.html plain text: www-developer-showcase-series-santiago-casaliglla-dnasmartbits.txt item: #2695 of 3327 id: www-developer-showcase-series-sara-ghaemi-telus author: www title: www-developer-showcase-series-sara-ghaemi-telus date: None words: 1178 flesch: 53 summary: During this program, I worked on blockchain interoperability with a focus on Hyperledger technologies. In this edition of our Developer Showcase Series, where we learn what developers in the real world are doing with Hyperledger technologies, we are spotlighting a recent graduate of the Hyperledger Summer Mentorship Program. keywords: blockchain; hyperledger; interoperability; technologies cache: www-developer-showcase-series-sara-ghaemi-telus.html plain text: www-developer-showcase-series-sara-ghaemi-telus.txt item: #2696 of 3327 id: www-developer-showcase-series-sergio-torres-signeblock-alastria-and-coding-bootcamps author: www title: www-developer-showcase-series-sergio-torres-signeblock-alastria-and-coding-bootcamps date: None words: 2225 flesch: 55 summary: El proyecto en el que estamos trabajando actualmente es el blockchain Signeblock con el que brindamos servicios blockchain a otros clientes y con el que funcionan las aplicaciones Gouze y Creo que Hyperledger, en particular, será el proyecto de DLT más importante a nviel mundial, ya que está haciendo las cosas bastante bien y tiene una estrategia que admite una amplia gama de tecnologías DLT What is the best piece of developer advice you’ve ever received? keywords: alastria; blockchain; con; fabric; hyperledger; para; que; signeblock; technologies; una cache: www-developer-showcase-series-sergio-torres-signeblock-alastria-and-coding-bootcamps.html plain text: www-developer-showcase-series-sergio-torres-signeblock-alastria-and-coding-bootcamps.txt item: #2697 of 3327 id: www-developer-showcase-series-seth-cohn author: www title: www-developer-showcase-series-seth-cohn date: None words: 903 flesch: 40 summary: In fact, I think any accounting based software that intends to be widely accepted should incorporate aspects of Excel because it is so approachable for CPAs and accountants that otherwise would reject unknown technology. Taking the EdX course ‘Blockchain for Business – An Introduction to Hyperledger Technologies’ is an excellent way to acquaint yourself with distributed ledgers and blockchain technologies being developed by business leaders and poised to have a tremendous impact on the business environment. keywords: blog; decentralized; technology cache: www-developer-showcase-series-seth-cohn.html plain text: www-developer-showcase-series-seth-cohn.txt item: #2698 of 3327 id: www-developer-showcase-series-thomas-brooke-brook-law author: www title: www-developer-showcase-series-thomas-brooke-brook-law date: None words: 1331 flesch: 60 summary: Cicero uses Hyperledger Composer and currently works with Hyperledger Fabric, both of which are currently in the Hyperledger project. We are developing it using Hyperledger Fabric and Hyperledger Composer. keywords: blockchain; brooke; hyperledger; project cache: www-developer-showcase-series-thomas-brooke-brook-law.html plain text: www-developer-showcase-series-thomas-brooke-brook-law.txt item: #2699 of 3327 id: www-developer-showcase-series-thomas-brooke-brook-law?hs_amp=true author: www title: www-developer-showcase-series-thomas-brooke-brook-law?hs_amp=true date: None words: 1017 flesch: 70 summary: Cicero uses Hyperledger Composer and currently works with Hyperledger Fabric, both of which are currently in the Hyperledger project. We are developing it using Hyperledger Fabric and Hyperledger Composer. keywords: brooke; hyperledger cache: www-developer-showcase-series-thomas-brooke-brook-law?hs_amp=true.html plain text: www-developer-showcase-series-thomas-brooke-brook-law?hs_amp=true.txt item: #2700 of 3327 id: www-developer-showcase-series-yi-sam-yuan-ibm author: www title: www-developer-showcase-series-yi-sam-yuan-ibm date: None words: 780 flesch: 45 summary: Yi (Sam) Yuan, IBM Hyperledger Foundation | Feb 15, 2022 Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. Can you sum up your experience with Hyperledger technologies? keywords: foundation; hyperledger; technologies cache: www-developer-showcase-series-yi-sam-yuan-ibm.html plain text: www-developer-showcase-series-yi-sam-yuan-ibm.txt item: #2701 of 3327 id: www-developer-showcase-series-yi-sam-yuan-ibm?hs_amp=true author: www title: www-developer-showcase-series-yi-sam-yuan-ibm?hs_amp=true date: None words: 468 flesch: 57 summary: Yi (Sam) Yuan, IBM – Hyperledger Foundation Blog | LF Decentralized Trust Developer showcase series: Yi (Sam) Yuan, IBM – Hyperledger Foundation Written by Hyperledger Foundation | Feb 15, 2022 9:00:00 AM Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. Can you sum up your experience with Hyperledger technologies? keywords: hyperledger cache: www-developer-showcase-series-yi-sam-yuan-ibm?hs_amp=true.html plain text: www-developer-showcase-series-yi-sam-yuan-ibm?hs_amp=true.txt item: #2702 of 3327 id: www-dfns-joins-adan-board author: www title: www-dfns-joins-adan-board date: None words: 971 flesch: 59 summary: See the Full Announcement Product Wallets-as-a-Service Platform (WaaS) Wallet Entitlement Management (WEM) Key Deployment Service (KDS) Integrations Developers Docs Github Changelog Status Resources Security Labs Blog FAQ Company Careers Newsroom About PricingGet started Talk to sales Get started Blog Update Dfns Joins ADAN Board UpdateDfns Joins ADAN Board Christopher Grilhault des Fontaines April 18, 2025 Read time: Clarisse Hagège, CEO of Dfns, joins the ADAN board to represent infrastructure builders in the industry’s top policy forum. Dfns Joins ADAN Board Dfns Secures $16M Series A Funding – keywords: adan; board; des; dfns cache: www-dfns-joins-adan-board.html plain text: www-dfns-joins-adan-board.txt item: #2703 of 3327 id: www-dfns-secures-series-a-funding author: www title: www-dfns-secures-series-a-funding date: None words: 1946 flesch: 42 summary: Wallets are the new subterranean rails of finance We often say that wallets are to cryptocurrencies what bank accounts are to fiat currencies. Key management services focus on generating and securing digital signatures, while wallet infrastructures handle the full transaction lifecycle—creating, broadcasting, and managing multichain interactions independently. keywords: blockchain; crypto; dfns; infrastructure; security; service; wallets cache: www-dfns-secures-series-a-funding.html plain text: www-dfns-secures-series-a-funding.txt item: #2704 of 3327 id: www-dfns-steps-into-mpca-presidency author: www title: www-dfns-steps-into-mpca-presidency date: None words: 984 flesch: 34 summary: With this strategic roadmap, the Alliance is poised to become the definitive platform for MPC innovation and standardization on a global scale. A new chapter for the MPC Alliance Founded in 2019 by companies such as Cybernetica, Sepior, and ZenGo, the MPC Alliance was established to advance MPC technology and develop industry standards for its evaluation and adoption. keywords: alliance; dfns; hagège; mpc cache: www-dfns-steps-into-mpca-presidency.html plain text: www-dfns-steps-into-mpca-presidency.txt item: #2705 of 3327 id: www-diane-mueller-lf-decentralized-trust-tac-member-and-open-source-strategic-advisor-hedera author: www title: www-diane-mueller-lf-decentralized-trust-tac-member-and-open-source-strategic-advisor-hedera date: None words: 545 flesch: 21 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Blog | LF Decentralized Trust | Diane Mueller, LF Decentralized Trust TAC member and Open Source Strategic Advisor, Hedera 2025 keywords: blog; decentralized; hyperledger; trust cache: www-diane-mueller-lf-decentralized-trust-tac-member-and-open-source-strategic-advisor-hedera.html plain text: www-diane-mueller-lf-decentralized-trust-tac-member-and-open-source-strategic-advisor-hedera.txt item: #2706 of 3327 id: www-diane-mueller-strategic-advisor-open-source-development-hedera-and-governing-board-member-alternate-rep-linux-foundation-decentralized-trust author: www title: www-diane-mueller-strategic-advisor-open-source-development-hedera-and-governing-board-member-alternate-rep-linux-foundation-decentralized-trust date: None words: 553 flesch: 16 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Blog | LF Decentralized Trust | Diane Mueller, Strategic Advisor, Open Source Development, Hedera, and Governing Board Member (alternate rep.), Linux Foundation Decentralized Trust 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? keywords: decentralized; hyperledger; linux; trust cache: www-diane-mueller-strategic-advisor-open-source-development-hedera-and-governing-board-member-alternate-rep-linux-foundation-decentralized-trust.html plain text: www-diane-mueller-strategic-advisor-open-source-development-hedera-and-governing-board-member-alternate-rep-linux-foundation-decentralized-trust.txt item: #2707 of 3327 id: www-digital-currency author: www title: www-digital-currency date: None words: 582 flesch: 14 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Read More Hyperledger | Jun 30, 2022 Blog | Digital Currency | CBDCs | Finance Fintech Open Source Foundation (FINOS), Hyperledger Foundation, and The Digital Dollar Project Team Up to Drive Open Development and Collaboration for CBDCs Central Bank Digital Currency (CBDC) has the power to transform economies — connecting people, governments, businesses, and organizations locally and globally through technology... keywords: blog; decentralized; hyperledger; technologies cache: www-digital-currency.html plain text: www-digital-currency.txt item: #2708 of 3327 id: www-digital-identity author: www title: www-digital-identity date: None words: 576 flesch: 15 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Read More Energy & Mines Digital Trust | Jun 20, 2023 Blog | Hyperledger Aries | Digital Identity Investing in Verifiable Credentials, Technical Interoperability and Open Source Our 20 Year Journey Like many provinces and territories in Canada, British Columbia (BC) has a long history of providing secure access to online government services. keywords: blog; decentralized; digital; hyperledger cache: www-digital-identity.html plain text: www-digital-identity.txt item: #2709 of 3327 id: www-digital-trust author: www title: www-digital-trust date: None words: 584 flesch: 19 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Blog | LF Decentralized Trust | Digital Trust 2025 Update: Off to a Fast Start! keywords: decentralized; hyperledger; technologies; trust cache: www-digital-trust.html plain text: www-digital-trust.txt item: #2710 of 3327 id: www-distributed-ledger-technology author: www title: www-distributed-ledger-technology date: None words: 675 flesch: 14 summary: Next page > Submit a blog Blog guidelines RSS Hyperledger Aries | Hyperledger Community | Distributed Ledger Technology | Decentralized Identity Why You Should Join the Hyperledger Identity Special Interest Group It’s hard to overstate the importance of digital identity: It governs every interaction online,... Read More Tim Spring - Co-Chair Hyperledger Identity SIG | Jul 26, 2023 Hyperledger Bevel | Distributed Ledger Technology | Hyperledger Fabric Kubernetes operators in Hyperledger Bevel with Bevel-Operator-Fabric We are excited to announce that hlf-operator, a Hyperledger lab, has been integrated into Hyperledger Bevel and has been renamed Bevel-Operator-Fabric. Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page keywords: blog; decentralized; hyperledger; technology cache: www-distributed-ledger-technology.html plain text: www-distributed-ledger-technology.txt item: #2711 of 3327 id: www-does-hyperledger-fabric-perform-at-scale author: www title: www-does-hyperledger-fabric-perform-at-scale date: None words: 886 flesch: 45 summary: So, does Hyperledger Fabric performance suffer with a proliferation of channels? Does Hyperledger Fabric perform at scale? keywords: fabric; hyperledger; performance cache: www-does-hyperledger-fabric-perform-at-scale.html plain text: www-does-hyperledger-fabric-perform-at-scale.txt item: #2712 of 3327 id: www-driving-new-markets-the-opportunities-ahead-for-enterprise-blockchain-technologies author: www title: www-driving-new-markets-the-opportunities-ahead-for-enterprise-blockchain-technologies date: None words: 1799 flesch: 36 summary: One such proven example is the application of Hyperledger technologies in the partnership between MineHub and KrypC that has utilized Hyperledger Fabric to drastically improve upon the infrastructure necessary to power the supply chain of the mining industry. Asset tokenization enables the purchase, sale and exchange of digital assets, representative of potentially any asset, traditional or otherwise. keywords: assets; blockchain; foundation; hyperledger; technologies; tokenization cache: www-driving-new-markets-the-opportunities-ahead-for-enterprise-blockchain-technologies.html plain text: www-driving-new-markets-the-opportunities-ahead-for-enterprise-blockchain-technologies.txt item: #2713 of 3327 id: www-driving-new-markets-the-opportunities-ahead-for-enterprise-blockchain-technologies?hs_amp=true author: www title: www-driving-new-markets-the-opportunities-ahead-for-enterprise-blockchain-technologies?hs_amp=true date: None words: 1488 flesch: 39 summary: One such proven example is the application of Hyperledger technologies in the partnership between MineHub and KrypC that has utilized Hyperledger Fabric to drastically improve upon the infrastructure necessary to power the supply chain of the mining industry. Asset tokenization enables the purchase, sale and exchange of digital assets, representative of potentially any asset, traditional or otherwise. keywords: assets; blockchain; hyperledger; tokenization cache: www-driving-new-markets-the-opportunities-ahead-for-enterprise-blockchain-technologies?hs_amp=true.html plain text: www-driving-new-markets-the-opportunities-ahead-for-enterprise-blockchain-technologies?hs_amp=true.txt item: #2714 of 3327 id: www-emily-fisher author: www title: www-emily-fisher date: None words: 647 flesch: 28 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page | Feb 3, 2022 Blog | Hyperledger Aries The Pathway to Becoming a Hyperledger Maintainer When I first came across Hyperledger Aries, I was still a student at the University of Applied Sciences in Utrecht. keywords: blog; decentralized; hyperledger; technologies cache: www-emily-fisher.html plain text: www-emily-fisher.txt item: #2715 of 3327 id: www-energy-mines-digital-trust-1 author: www title: www-energy-mines-digital-trust-1 date: None words: 579 flesch: 17 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Hyperledger Aries | Climate | Supply Chain Energy & Mines Digital Trust: The Future of Global Supply Chains After two years of piloting, Energy & Mines Digital Trust (EMDT) has successfully launched two... keywords: decentralized; digital; hyperledger; trust cache: www-energy-mines-digital-trust-1.html plain text: www-energy-mines-digital-trust-1.txt item: #2716 of 3327 id: www-energy-mines-digital-trust-interoperable-technology-for-sustainable-resilient-supply-chains-heads-to-production author: www title: www-energy-mines-digital-trust-interoperable-technology-for-sustainable-resilient-supply-chains-heads-to-production date: None words: 1174 flesch: 26 summary: Diverse regulatory models Varied reporting standards A lack of interoperable digital tools EMDT’s pilot use cases demonstrate that digital credentials offer a solution to these challenges, driving a new approach to sustainability reporting, and empowering mining companies to share verified data that can be trusted. EMDT was initiated by the Government of British Columbia, Canada, in partnership with TELUS to explore the use of digital trust technology for the natural resource sector. keywords: digital; emdt; mining; trust cache: www-energy-mines-digital-trust-interoperable-technology-for-sustainable-resilient-supply-chains-heads-to-production.html plain text: www-energy-mines-digital-trust-interoperable-technology-for-sustainable-resilient-supply-chains-heads-to-production.txt item: #2717 of 3327 id: www-energy-mines-digital-trust-interoperable-technology-for-sustainable-resilient-supply-chains-heads-to-production?hs_amp=true author: www title: www-energy-mines-digital-trust-interoperable-technology-for-sustainable-resilient-supply-chains-heads-to-production?hs_amp=true date: None words: 858 flesch: 27 summary: MOVING TO PRODUCTION As EMDT’s mining sector use case moves into production, mining companies, regulators, and governing bodies will experience the benefits of digital trust technology first-hand.  Throughout the project’s pilot phase, EMDT earned international recognition for the unique application of digital credentials for organizational identities using Hyperledger technologies.  CHALLENGES IN SUSTAINABILITY REPORTING  To compete in a global market that prioritizes sustainably sourced products, mining companies must be able to prove where their products originated and how they were produced.  keywords: digital; emdt; trust cache: www-energy-mines-digital-trust-interoperable-technology-for-sustainable-resilient-supply-chains-heads-to-production?hs_amp=true.html plain text: www-energy-mines-digital-trust-interoperable-technology-for-sustainable-resilient-supply-chains-heads-to-production?hs_amp=true.txt item: #2718 of 3327 id: www-energy-mines-digital-trust-the-future-of-global-supply-chains author: www title: www-energy-mines-digital-trust-the-future-of-global-supply-chains date: None words: 1204 flesch: 25 summary: Mining operators can adopt any Hyperledger Aries-compatible corporate wallet of their choice to send and receive digital credentials with the Government of B.C. Alternatively, since Hyperledger Aries is open source, organizations can develop their own, customized corporate wallet, reducing industry costs to exchange authoritative digital credentials.  Using digital credentials, companies can more easily meet investor and customer demand for trustworthy sustainability data, and better compete in emerging markets that prioritize sustainable goods.  keywords: credentials; digital; mines; trust cache: www-energy-mines-digital-trust-the-future-of-global-supply-chains.html plain text: www-energy-mines-digital-trust-the-future-of-global-supply-chains.txt item: #2719 of 3327 id: www-energy-mines-digital-trust-the-future-of-global-supply-chains?hs_amp=true author: www title: www-energy-mines-digital-trust-the-future-of-global-supply-chains?hs_amp=true date: None words: 888 flesch: 25 summary: Mining operators can adopt any Hyperledger Aries-compatible corporate wallet of their choice to send and receive digital credentials with the Government of B.C. Alternatively, since Hyperledger Aries is open source, organizations can develop their own, customized corporate wallet, reducing industry costs to exchange authoritative digital credentials.  Using digital credentials, companies can more easily meet investor and customer demand for trustworthy sustainability data, and better compete in emerging markets that prioritize sustainable goods.  keywords: credentials; digital; mines cache: www-energy-mines-digital-trust-the-future-of-global-supply-chains?hs_amp=true.html plain text: www-energy-mines-digital-trust-the-future-of-global-supply-chains?hs_amp=true.txt item: #2720 of 3327 id: www-energy-mines-digital-trust-the-open-source-journey-towards-a-clean-resilient-economy author: www title: www-energy-mines-digital-trust-the-open-source-journey-towards-a-clean-resilient-economy date: None words: 1033 flesch: 29 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog | Hyperledger Aries | Climate Energy & Mines Digital Trust: The Open-Source Journey Towards a Clean, Resilient Economy Hyperledger | Sep 13, 2022 As the world works towards climate goals, a government project from Canada is using digital trust technology to make it easier and more secure for natural resource companies to share sustainability data.  Digital trust technology streamlines access to trustworthy sustainability data, allowing businesses, governments, and non-government organizations to work towards climate change goals more efficiently and effectively. keywords: data; digital; sustainability; trust cache: www-energy-mines-digital-trust-the-open-source-journey-towards-a-clean-resilient-economy.html plain text: www-energy-mines-digital-trust-the-open-source-journey-towards-a-clean-resilient-economy.txt item: #2721 of 3327 id: www-enrique-lacal-hyperledger-firefly-maintainer-and-community-lead-and-full-stack-software-engineer-at-kaleido author: www title: www-enrique-lacal-hyperledger-firefly-maintainer-and-community-lead-and-full-stack-software-engineer-at-kaleido date: None words: 542 flesch: 15 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Blog | LF Decentralized Trust | Enrique Lacal, Hyperledger FireFly Maintainer and Community Lead and Full Stack Software Engineer at Kaleido 2025 Update: Off to a Fast Start! keywords: blog; community; decentralized; hyperledger cache: www-enrique-lacal-hyperledger-firefly-maintainer-and-community-lead-and-full-stack-software-engineer-at-kaleido.html plain text: www-enrique-lacal-hyperledger-firefly-maintainer-and-community-lead-and-full-stack-software-engineer-at-kaleido.txt item: #2722 of 3327 id: www-enterprise-blockchain-demos-presentations-at-consensus author: www title: www-enterprise-blockchain-demos-presentations-at-consensus date: None words: 2043 flesch: 40 summary: Someone needs to build it: closing the Hyperledger talent gap by Elias Haase, Founder Every day, B9lab gets requests for Hyperledger Fabric developers, from concept-phase startups to major enterprises. They will walk you through the tools in the operations console and demonstrate how Hyperledger Fabric configuration, operations, and monitoring has been simplified and how developers and IT operations can be more productive leveraging Oracle’s blockchain cloud service as their Hyperledger Fabric platform. keywords: blockchain; consensus; decentralized; enterprise; fabric; hyperledger; identity; remme; use cache: www-enterprise-blockchain-demos-presentations-at-consensus.html plain text: www-enterprise-blockchain-demos-presentations-at-consensus.txt item: #2723 of 3327 id: www-enterprises-can-no-longer-take-shortcuts-with-climate-and-social-impact-and-distributed-ledgers-provide-proven-accelerators-for-change author: www title: www-enterprises-can-no-longer-take-shortcuts-with-climate-and-social-impact-and-distributed-ledgers-provide-proven-accelerators-for-change date: None words: 1377 flesch: 33 summary: Hopefully, in this article we have demonstrated that the problems are clear, real and addressable; that multi-party collaboration platforms are feasible to implement; and that there are technology accelerators available to enterprises and governments that are proven and scalable. The important factor here is not that blockchain applied to these domains solved a problem but rather that these climate and social issues are multi-party problems that require entities, activities and processes to be supported by technology to drive and sustain change.  keywords: action; decentralized; emissions; impact; technologies; use cache: www-enterprises-can-no-longer-take-shortcuts-with-climate-and-social-impact-and-distributed-ledgers-provide-proven-accelerators-for-change.html plain text: www-enterprises-can-no-longer-take-shortcuts-with-climate-and-social-impact-and-distributed-ledgers-provide-proven-accelerators-for-change.txt item: #2724 of 3327 id: www-eravatee-raje author: www title: www-eravatee-raje date: None words: 525 flesch: 18 summary: Project name: Visual Studio Code support for Hyperledger Caliper artifacts Read More Eravatee Raje | Feb 27, 2023 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page keywords: blog; decentralized; hyperledger; project cache: www-eravatee-raje.html plain text: www-eravatee-raje.txt item: #2725 of 3327 id: www-examining-dlt-solutions-for-trade-and-finance-with-a-china-focus author: www title: www-examining-dlt-solutions-for-trade-and-finance-with-a-china-focus date: None words: 1301 flesch: 30 summary: Financial DLT national projects therefore represent a way to safely drive overseas investments in terms of political orientation and economic accountability over the Digital Silk Road. Non-China markets will have to use BSN and DCEP to engage with China markets. keywords: china; dlt; finance; hyperledger; trade cache: www-examining-dlt-solutions-for-trade-and-finance-with-a-china-focus.html plain text: www-examining-dlt-solutions-for-trade-and-finance-with-a-china-focus.txt item: #2726 of 3327 id: www-examining-dlt-solutions-for-trade-and-finance-with-a-china-focus?hs_amp=true author: www title: www-examining-dlt-solutions-for-trade-and-finance-with-a-china-focus?hs_amp=true date: None words: 991 flesch: 31 summary: Financial DLT national projects therefore represent a way to safely drive overseas investments in terms of political orientation and economic accountability over the Digital Silk Road. Trade Finance SIG: https://wiki.hyperledger.org/display/TFSIG/DLT+solutions+for+trade+and+finance+-+China+Focus Capital Market SIG: https://wiki.hyperledger.org/display/CMSIG/DLT+solutions+for+trade+and+finance+-+China+focus  Written by: Eugenio Reggianini, Business Development Manager, CarbonBlue Innovations Limited; Member, Hyperledger Trade Finance & Capital Market Special Interest Groups Curated  by: Andrea Frosinini, freelance trade finance consultant; Chair, Hyperledger Trade Finance Special Interest Group    Vipin Bharathan, Technical Strategist and Founder, dlt.nyc; Chair, Hyperledger Capital Markets SIG View full post keywords: china; finance; trade cache: www-examining-dlt-solutions-for-trade-and-finance-with-a-china-focus?hs_amp=true.html plain text: www-examining-dlt-solutions-for-trade-and-finance-with-a-china-focus?hs_amp=true.txt item: #2727 of 3327 id: www-fabricius-fifo-zatti-principal-blockchain-engineer-at-cheesecake-labs-hyperledger-cacti-contributor author: www title: www-fabricius-fifo-zatti-principal-blockchain-engineer-at-cheesecake-labs-hyperledger-cacti-contributor date: None words: 534 flesch: 14 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page | Interoperability Building Bridges: Developing the Stellar Connector for Hyperledger Cacti Introduction: The Importance of Interoperability in Blockchain Read More Fabricius (Fifo) Zatti, Principal Blockchain Engineer at Cheesecake Labs & Hyperledger Cacti contributor | Jun 27, 2024 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-fabricius-fifo-zatti-principal-blockchain-engineer-at-cheesecake-labs-hyperledger-cacti-contributor.html plain text: www-fabricius-fifo-zatti-principal-blockchain-engineer-at-cheesecake-labs-hyperledger-cacti-contributor.txt item: #2728 of 3327 id: www-final-weekend-update-a-round-up-of-remote-blockchain-learning-resources author: www title: www-final-weekend-update-a-round-up-of-remote-blockchain-learning-resources date: None words: 634 flesch: 24 summary: Upcoming Hyperledger Community Training Sessions Build Your Identity Solution Using Hyperledger Aries, January 20, 2022, from 8:00 am – 11:00 am PST  Hyperledger Indy Technical Deep Dive, February 3, 2022, from 8:00 am – 12:00 pm PST         Where to go to stay plugged into Hyperledger Foundation and the Hyperledger community: Webinars and other events: https://www.hyperledger.org/events Developer, Working Group and Special Interest Group meetings: https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+Meetings Meetup schedule: https://wiki.hyperledger.org/display/events/Virtual+Hyperledger+Meetups YouTube playlist: https://www.youtube.com/c/Hyperledger/playlists Hyperledger case studies: https://www.hyperledger.org/learn/case-studies Hyperledger job board: https://www.hyperledger.org/about/jobs Monthly Hyperledger newsletter: https://www.hyperledger.org/newsletter /dev/weekly updates: https://www.hyperledger.org/developer-newsletter Follow us on Twitter for the latest. Final Weekend Update: A Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 keywords: decentralized; events; hyperledger cache: www-final-weekend-update-a-round-up-of-remote-blockchain-learning-resources.html plain text: www-final-weekend-update-a-round-up-of-remote-blockchain-learning-resources.txt item: #2729 of 3327 id: www-finance author: www title: www-finance date: None words: 1390 flesch: 32 summary: Next page > Submit a blog Blog guidelines RSS Finance Celebrating Black History Month: Advancing FinTech and Blockchain Innovation at HBCUs As we celebrate Black History Month, we reflect on the remarkable strides that Black Colleges and... Read More Ali Emdad, Ph.D | Feb 25, 2025 Finance | Labs Introducing Splice, a New Hyperledger Lab for Canton Network Interoperability Hyperledger Labs Read More Wayne Collier, Principal Product Manager, Digital Asset | Jun 28, 2024 Finance | Staff Corner The Case for Open Development as the Foundation for Central Bank Digital Currencies Introduction Read More Karen Ottoni, Senior Director of Ecosystem and Strategic Initiatives, Hyperledger Foundation | Nov 1, 2023 Developer Showcase | Finance Developer Showcase Series: Daniel Szego, Independent DLT Architect Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. Read More Hyperledger | Jan 31, 2023 Finance | Staff Corner Driving new markets: The opportunities ahead for enterprise blockchain technologies While volatility reigned supreme in 2022, here at Hyperledger Foundation we are looking ahead with great excitement to what is possible in 2023. keywords: blog; case; decentralized; finance; foundation; hyperledger cache: www-finance.html plain text: www-finance.txt item: #2730 of 3327 id: www-finance-and-business-technology author: www title: www-finance-and-business-technology date: None words: 535 flesch: 13 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Besu | Finance and Business Technology Why Hyperledger Besu is a Top Choice for Financial Use Cases Hyperledger Besu has emerged as a preferred runtime for EVM-based financial initiatives worldwide.... keywords: blog; decentralized; hyperledger; technologies cache: www-finance-and-business-technology.html plain text: www-finance-and-business-technology.txt item: #2731 of 3327 id: www-fintech-open-source-foundation-finos-hyperledger-foundation-and-the-digital-dollar-project-team-up-to-drive-open-development-and-collaboration-for-cbdcs author: www title: www-fintech-open-source-foundation-finos-hyperledger-foundation-and-the-digital-dollar-project-team-up-to-drive-open-development-and-collaboration-for-cbdcs date: None words: 652 flesch: 26 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog | Digital Currency | CBDCs | Finance Fintech Open Source Foundation (FINOS), Hyperledger Foundation, and The Digital Dollar Project Team Up to Drive Open Development and Collaboration for CBDCs Hyperledger | May 23, 2022 Central Bank Digital Currency (CBDC) has the power to transform economies — connecting people, governments, businesses, and organizations locally and globally through technology that could not have been imagined even 20 years ago, and with more advances on the way. That’s why we are thrilled to announce that Fintech Open Source Foundation (FINOS), Hyperledger Foundation and The Digital Dollar Project (DDP) are joining forces to create an open community dedicated to experimentation, information sharing, and discussion around CBDCs, ensuring that central banks that decide to embark upon researching or deploying CBDCs are doing so with the best available secure technology. keywords: foundation; hyperledger; open cache: www-fintech-open-source-foundation-finos-hyperledger-foundation-and-the-digital-dollar-project-team-up-to-drive-open-development-and-collaboration-for-cbdcs.html plain text: www-fintech-open-source-foundation-finos-hyperledger-foundation-and-the-digital-dollar-project-team-up-to-drive-open-development-and-collaboration-for-cbdcs.txt item: #2732 of 3327 id: www-fintech-open-source-foundation-finos-hyperledger-foundation-and-the-digital-dollar-project-team-up-to-drive-open-development-and-collaboration-for-cbdcs?hs_amp=true author: www title: www-fintech-open-source-foundation-finos-hyperledger-foundation-and-the-digital-dollar-project-team-up-to-drive-open-development-and-collaboration-for-cbdcs?hs_amp=true date: None words: 337 flesch: 30 summary: Fintech Open Source Foundation (FINOS), That’s why we are thrilled to announce that Fintech Open Source Foundation (FINOS), Hyperledger Foundation and The Digital Dollar Project (DDP) are joining forces to create an open community dedicated to experimentation, information sharing, and discussion around CBDCs, ensuring that central banks that decide to embark upon researching or deploying CBDCs are doing so with the best available secure technology. keywords: foundation cache: www-fintech-open-source-foundation-finos-hyperledger-foundation-and-the-digital-dollar-project-team-up-to-drive-open-development-and-collaboration-for-cbdcs?hs_amp=true.html plain text: www-fintech-open-source-foundation-finos-hyperledger-foundation-and-the-digital-dollar-project-team-up-to-drive-open-development-and-collaboration-for-cbdcs?hs_amp=true.txt item: #2733 of 3327 id: www-first-hyperledger-web3j-summit author: www title: www-first-hyperledger-web3j-summit date: None words: 1186 flesch: 36 summary: As a maintainer of Hyperledger Web3j, an LF Decentralized Trust project, I was excited to see participants share insights, raise important questions, and offer new ideas to drive the project forward. Linux Foundation Decentralized Trust Support Staff: Sean Bohan (LF Decentralized Trust Staff), David Boswell (LF Decentralized Trust Staff): Their support in organizing, moderating, and guiding the summit discussions underscored the Linux Foundation’s dedication to fostering open-source, community-driven innovation. keywords: android; decentralized; project; support; web3j cache: www-first-hyperledger-web3j-summit.html plain text: www-first-hyperledger-web3j-summit.txt item: #2734 of 3327 id: www-first-hyperledger-web3j-summit?hs_amp=true author: www title: www-first-hyperledger-web3j-summit?hs_amp=true date: None words: 876 flesch: 39 summary: As a maintainer of Hyperledger Web3j, an LF Decentralized Trust project, I was excited to see participants share insights, raise important questions, and offer new ideas to drive the project forward. To get involved with Hyperledger Web3j, check out the Web3j Github repo and join us on the Web3j Discord channels.   keywords: android; support; web3j cache: www-first-hyperledger-web3j-summit?hs_amp=true.html plain text: www-first-hyperledger-web3j-summit?hs_amp=true.txt item: #2735 of 3327 id: www-five-healthcare-projects-powered-by-hyperledger-you-may-not-know-about author: www title: www-five-healthcare-projects-powered-by-hyperledger-you-may-not-know-about date: None words: 1326 flesch: 36 summary: Below is a list of some interesting healthcare applications powered by Hyperledger technology you may or may not have known about: KitChain – LedgerDomain joined forces with other industry leaders like Pfizer, IQVIA, UPS, Merck, UCLA Health, GSK, Thermo Fisher, and Biogen to build out a pilot on Hyperledger Fabric called KitChain. keywords: blockchain; healthcare; hyperledger; information; network; technologies cache: www-five-healthcare-projects-powered-by-hyperledger-you-may-not-know-about.html plain text: www-five-healthcare-projects-powered-by-hyperledger-you-may-not-know-about.txt item: #2736 of 3327 id: www-five-takeaways-on-open-source-blockchain-and-innovation-from-hlth-vive-and-himss author: www title: www-five-takeaways-on-open-source-blockchain-and-innovation-from-hlth-vive-and-himss date: None words: 1209 flesch: 42 summary: It’s exciting to see how Hyperledger Foundation, LFPH and other Linux Foundation projects are actively involved in so many facets of new innovations in healthcare. HIMSS hosted two breakfast panels featuring a range of healthcare industry professionals discussing blockchain applications. keywords: blockchain; decentralized; foundation; healthcare; linux cache: www-five-takeaways-on-open-source-blockchain-and-innovation-from-hlth-vive-and-himss.html plain text: www-five-takeaways-on-open-source-blockchain-and-innovation-from-hlth-vive-and-himss.txt item: #2737 of 3327 id: www-floating-the-sawtooth-raft-implementing-a-consensus-algorithm-in-rust author: www title: www-floating-the-sawtooth-raft-implementing-a-consensus-algorithm-in-rust date: None words: 2059 flesch: 48 summary: In the main function of main.rs, all we need to do is simply determine the validator’s endpoint (using a command-line argument in Raft), instantiate the engine, and start it using the SDK’s ZmqDriver: let raft_engine = engine::RaftEngine::new();   let (driver, _stop) = ZmqDriver::new();   info!(Raft Node connecting to '{}', &args.endpoint); driver.start(&args.endpoint, raft_engine).unwrap_or_else(|err| {    error!({}, err);    process::exit(1); }); See for Yourself! Want to try running a Sawtooth network with Raft consensus? He has been involved in a variety of Hyperledger Sawtooth projects, including the development of the consensus API, Sawtooth Raft, and Sawtooth PBFT. keywords: algorithm; consensus; engine; node; raft cache: www-floating-the-sawtooth-raft-implementing-a-consensus-algorithm-in-rust.html plain text: www-floating-the-sawtooth-raft-implementing-a-consensus-algorithm-in-rust.txt item: #2738 of 3327 id: www-fujitsu-develops-hyperledger-fabric-powered-exchange-for-plant-sourced-water-recovered-by-botanical-water-technologies author: www title: www-fujitsu-develops-hyperledger-fabric-powered-exchange-for-plant-sourced-water-recovered-by-botanical-water-technologies date: None words: 781 flesch: 43 summary: The next challenge was creating a marketplace for buyers and sellers of plant-sourced water that would support three different transactions: Sales of actual water for food, beverage and other manufacturers Sales of “water impact credits” (WICs) to help fulfill corporate water stewardship goals Bulk donations of water to the world’s most vulnerable people BWT asked Fujitsu to develop a world-first: Botanical Water Exchange (BWX) that securely tracks every drop of water from producer to end consumer. BWT estimates 3 trillion liters of water are wasted this way every year. keywords: case; hyperledger; technologies; water cache: www-fujitsu-develops-hyperledger-fabric-powered-exchange-for-plant-sourced-water-recovered-by-botanical-water-technologies.html plain text: www-fujitsu-develops-hyperledger-fabric-powered-exchange-for-plant-sourced-water-recovered-by-botanical-water-technologies.txt item: #2739 of 3327 id: www-fujitsu-develops-hyperledger-fabric-powered-exchange-for-plant-sourced-water-recovered-by-botanical-water-technologies?hs_amp=true author: www title: www-fujitsu-develops-hyperledger-fabric-powered-exchange-for-plant-sourced-water-recovered-by-botanical-water-technologies?hs_amp=true date: None words: 466 flesch: 55 summary: The next challenge was creating a marketplace for buyers and sellers of plant-sourced water that would support three different transactions: Sales of actual water for food, beverage and other manufacturers Sales of “water impact credits” (WICs) to help fulfill corporate water stewardship goals Bulk donations of water to the world’s most vulnerable people BWT asked Fujitsu to develop a world-first: Botanical Water Exchange (BWX) that securely tracks every drop of water from producer to end consumer. BWT estimates 3 trillion liters of water are wasted this way every year. keywords: hyperledger; water cache: www-fujitsu-develops-hyperledger-fabric-powered-exchange-for-plant-sourced-water-recovered-by-botanical-water-technologies?hs_amp=true.html plain text: www-fujitsu-develops-hyperledger-fabric-powered-exchange-for-plant-sourced-water-recovered-by-botanical-water-technologies?hs_amp=true.txt item: #2740 of 3327 id: www-full-decentralization-of-hyperledger-fabric-through-embedded-iot-solutions author: www title: www-full-decentralization-of-hyperledger-fabric-through-embedded-iot-solutions date: None words: 1247 flesch: 41 summary: Use cases often include companies providing monitoring services with IoT devices, operators offering the communication network, and owners of the devices looking to apply the benefits of this technology to their blockchain-based traceability projects. aitos.io developed its blockchain application framework, named BoAT (Blockchain of AI Things), which is an IoT-device-oriented C-language client library for blockchain services, to enable IoT devices to access blockchain. keywords: blockchain; device; identity; iot; trustid cache: www-full-decentralization-of-hyperledger-fabric-through-embedded-iot-solutions.html plain text: www-full-decentralization-of-hyperledger-fabric-through-embedded-iot-solutions.txt item: #2741 of 3327 id: www-full-linea-rpc-apis-support-in-web3j author: www title: www-full-linea-rpc-apis-support-in-web3j date: None words: 828 flesch: 41 summary: With the latest updates in Web3j, we now support full integration of Linea RPC APIs, enabling developers to seamlessly interact with the Linea network using Java and Kotlin. Linea RPC APIs in Web3j Web3j now supports the following Linea-specific RPC methods: 1. keywords: code; linea; rpc; web3j cache: www-full-linea-rpc-apis-support-in-web3j.html plain text: www-full-linea-rpc-apis-support-in-web3j.txt item: #2742 of 3327 id: www-full-linea-rpc-apis-support-in-web3j?hs_amp=true author: www title: www-full-linea-rpc-apis-support-in-web3j?hs_amp=true date: None words: 518 flesch: 51 summary: With the latest updates in Web3j, we now support full integration of Linea RPC APIs, enabling developers to seamlessly interact with the Linea network using Java and Kotlin. Linea RPC APIs in Web3j Web3j now supports the following Linea-specific RPC methods: 1. keywords: linea; web3j cache: www-full-linea-rpc-apis-support-in-web3j?hs_amp=true.html plain text: www-full-linea-rpc-apis-support-in-web3j?hs_amp=true.txt item: #2743 of 3327 id: www-galachain-leveraging-hyperledger-fabric-to-create-the-ultimate-entertainment-blockchain author: www title: www-galachain-leveraging-hyperledger-fabric-to-create-the-ultimate-entertainment-blockchain date: None words: 1787 flesch: 50 summary: The wildly unique requirements of different entertainment products forced GalaChain developers to create something more customizable and more adaptable for entertainment use than any other L1 out there. While the early history of Gala was geared towards gaming, other projects across entertainment such as Gala Film and Gala Games arose while GalaChain design was still in its infancy. keywords: blockchain; decentralized; entertainment; fabric; galachain; hyperledger cache: www-galachain-leveraging-hyperledger-fabric-to-create-the-ultimate-entertainment-blockchain.html plain text: www-galachain-leveraging-hyperledger-fabric-to-create-the-ultimate-entertainment-blockchain.txt item: #2744 of 3327 id: www-galachain-leveraging-hyperledger-fabric-to-create-the-ultimate-entertainment-blockchain?hs_amp=true author: www title: www-galachain-leveraging-hyperledger-fabric-to-create-the-ultimate-entertainment-blockchain?hs_amp=true date: None words: 1476 flesch: 54 summary: The wildly unique requirements of different entertainment products forced GalaChain developers to create something more customizable and more adaptable for entertainment use than any other L1 out there. While the early history of Gala was geared towards gaming, other projects across entertainment such as Gala Film and Gala Games arose while GalaChain design was still in its infancy. keywords: entertainment; fabric; galachain; hyperledger cache: www-galachain-leveraging-hyperledger-fabric-to-create-the-ultimate-entertainment-blockchain?hs_amp=true.html plain text: www-galachain-leveraging-hyperledger-fabric-to-create-the-ultimate-entertainment-blockchain?hs_amp=true.txt item: #2745 of 3327 id: www-george-tebrean-hyperledger-webj3-maintainer-and-blockchain-developer-at-web3-labs author: www title: www-george-tebrean-hyperledger-webj3-maintainer-and-blockchain-developer-at-web3-labs date: None words: 586 flesch: 20 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Blog | LF Decentralized Trust | George Tebrean, Hyperledger Webj3 maintainer and Blockchain Developer at Web3 Labs 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? keywords: blog; decentralized; hyperledger; technologies cache: www-george-tebrean-hyperledger-webj3-maintainer-and-blockchain-developer-at-web3-labs.html plain text: www-george-tebrean-hyperledger-webj3-maintainer-and-blockchain-developer-at-web3-labs.txt item: #2746 of 3327 id: www-get-started-with-hyperledger-aries-accelerate-your-decentralized-identity-skills-with-a-free-instructor-led-workshop author: www title: www-get-started-with-hyperledger-aries-accelerate-your-decentralized-identity-skills-with-a-free-instructor-led-workshop date: None words: 794 flesch: 25 summary: Hyperledger Foundation has partnered with member company Indicio and its team of deeply experienced developers and architects to develop a free workshop to help developers and architects gain a deeper understanding of decentralized identity and become familiar with the technologies that are made possible by using Hyperledger Aries.  Get started with Hyperledger Aries: Accelerate your decentralized identity skills with a free instructor-led Workshop – Hyperledger Foundation 2025 keywords: aries; decentralized; hyperledger cache: www-get-started-with-hyperledger-aries-accelerate-your-decentralized-identity-skills-with-a-free-instructor-led-workshop.html plain text: www-get-started-with-hyperledger-aries-accelerate-your-decentralized-identity-skills-with-a-free-instructor-led-workshop.txt item: #2747 of 3327 id: www-get-started-with-hyperledger-aries-accelerate-your-decentralized-identity-skills-with-a-free-instructor-led-workshop?hs_amp=true author: www title: www-get-started-with-hyperledger-aries-accelerate-your-decentralized-identity-skills-with-a-free-instructor-led-workshop?hs_amp=true date: None words: 480 flesch: 26 summary: Get started with Hyperledger Aries: Accelerate your decentralized identity skills with a free instructor-led Workshop – Hyperledger Foundation Blog | LF Decentralized Trust Get started with Hyperledger Aries: Accelerate your decentralized identity skills with a free instructor-led Workshop – Hyperledger Foundation Written by Hyperledger | Sep 28, 2022 9:00:00 AM Hyperledger Aries is one of the fastest growing open source projects propelling the advancement and adoption of decentralized identity and verifiable credentials out there today. Hyperledger Foundation has partnered with member company Indicio and its team of deeply experienced developers and architects to develop a free workshop to help developers and architects gain a deeper understanding of decentralized identity and become familiar with the technologies that are made possible by using Hyperledger Aries.  keywords: aries; hyperledger cache: www-get-started-with-hyperledger-aries-accelerate-your-decentralized-identity-skills-with-a-free-instructor-led-workshop?hs_amp=true.html plain text: www-get-started-with-hyperledger-aries-accelerate-your-decentralized-identity-skills-with-a-free-instructor-led-workshop?hs_amp=true.txt item: #2748 of 3327 id: www-governance author: www title: www-governance date: None words: 1412 flesch: 37 summary: Governance Staff Corner: Welcome to the new Hyperledger Foundation Governing Board chair, Accenture’s David Treat Governance is crucial to enterprise-grade open source software development and to the mission of Hyperledger Foundation. For Hyperledger Foundation, technical governance is the job of the Technical Oversight... keywords: community; foundation; governance; hyperledger; projects cache: www-governance.html plain text: www-governance.txt item: #2749 of 3327 id: www-governance-update-a-qa-with-the-leaders-of-the-2024-hyperledger-foundation-technical-oversight-committee author: www title: www-governance-update-a-qa-with-the-leaders-of-the-2024-hyperledger-foundation-technical-oversight-committee date: None words: 1726 flesch: 38 summary: For Hyperledger Foundation, technical governance is the job of the Technical Oversight Committee (TOC), which consists of 11 members of the technical contributor community elected annually by maintainers and Governing Board members. The work was completed through a number of task forces run by TOC members and open for anyone to participate. keywords: community; foundation; hyperledger; project; technical; toc cache: www-governance-update-a-qa-with-the-leaders-of-the-2024-hyperledger-foundation-technical-oversight-committee.html plain text: www-governance-update-a-qa-with-the-leaders-of-the-2024-hyperledger-foundation-technical-oversight-committee.txt item: #2750 of 3327 id: www-governance-update-a-qa-with-the-leaders-of-the-2024-hyperledger-foundation-technical-oversight-committee?hs_amp=true author: www title: www-governance-update-a-qa-with-the-leaders-of-the-2024-hyperledger-foundation-technical-oversight-committee?hs_amp=true date: None words: 1416 flesch: 41 summary: Governance Update: A Q+A with the Leaders of the 2024 Hyperledger Foundation Technical Oversight Committee Blog | LF Decentralized Trust Governance Update: A Q+A with the Leaders of the 2024 Hyperledger Foundation Technical Oversight Committee Written by Hyperledger Foundation | Feb 5, 2024 5:31:32 PM Governance is a cornerstone for open source community management and, ultimately, code. For Hyperledger Foundation, technical governance is the job of the Technical Oversight Committee (TOC), which consists of 11 members of the technical contributor community elected annually by maintainers and Governing Board members. keywords: community; foundation; hyperledger; toc cache: www-governance-update-a-qa-with-the-leaders-of-the-2024-hyperledger-foundation-technical-oversight-committee?hs_amp=true.html plain text: www-governance-update-a-qa-with-the-leaders-of-the-2024-hyperledger-foundation-technical-oversight-committee?hs_amp=true.txt item: #2751 of 3327 id: www-governing-board author: www title: www-governing-board date: None words: 529 flesch: 19 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Governance Staff Corner: Welcome to the new Hyperledger Foundation Governing Board chair, Accenture’s David Treat Governance is crucial to enterprise-grade open source software development and to the mission of... Read More Hyperledger | May 18, 2022 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; board; decentralized; hyperledger cache: www-governing-board.html plain text: www-governing-board.txt item: #2752 of 3327 id: www-gsbn-builds-global-trade-operating-platform-with-hyperledger-fabric-as-the-foundation author: www title: www-gsbn-builds-global-trade-operating-platform-with-hyperledger-fabric-as-the-foundation date: None words: 819 flesch: 47 summary: Global trade is systemically important to the world’s economy. In short, existing global trade processes aren’t efficient nor resilient enough.   keywords: case; foundation; gsbn; trade cache: www-gsbn-builds-global-trade-operating-platform-with-hyperledger-fabric-as-the-foundation.html plain text: www-gsbn-builds-global-trade-operating-platform-with-hyperledger-fabric-as-the-foundation.txt item: #2753 of 3327 id: www-health-and-public-sector author: www title: www-health-and-public-sector date: None words: 1386 flesch: 39 summary: As part of this process,... Read More Hyperledger | Dec 2, 2019 Blog | Hyperledger Community | Health and Public Sector Community Spotlight: Meet Richard Bloch, Hyperledger Healthcare SIG Chair Welcome to our Community Spotlight series, which highlights the work of those taking on leadership roles in our special interest and working groups. To... Read More Hyperledger | Sep 22, 2020 Blog | Health and Public Sector Five Healthcare Projects Powered by Hyperledger You May Not Know About The New Year brings about various resolutions for millions across the globe. keywords: blog; decentralized; health; healthcare; hyperledger; sector cache: www-health-and-public-sector.html plain text: www-health-and-public-sector.txt item: #2754 of 3327 id: www-hello-hiero-building-the-next-generation-open-source-distributed-ledger-technology-together author: www title: www-hello-hiero-building-the-next-generation-open-source-distributed-ledger-technology-together date: None words: 1590 flesch: 41 summary: Building the Next Generation Open Source Distributed Ledger Technology Together Diane Mueller, Strategic Advisor, Open Source Development, Hedera, and Governing Board Member (alternate rep.), Linux Foundation Decentralized Trust | Oct 17, 2024 As the landscape of decentralized trust continues to evolve, open source technologies play a pivotal role in driving innovation and fostering collaboration. In a panel discussion moderated by Dr. Leemon Baird, Hedera’s Co-Founder, Chief Scientist at Hashgraph, and Hiero Technical Steering Committee (TSC) member, a diverse group of thought leaders and developers from Hedera’s ecosystem shared insights into the significance of this milestone and its impact on the future of open source blockchain development. keywords: community; decentralized; hedera; hiero; open; source cache: www-hello-hiero-building-the-next-generation-open-source-distributed-ledger-technology-together.html plain text: www-hello-hiero-building-the-next-generation-open-source-distributed-ledger-technology-together.txt item: #2755 of 3327 id: www-hello-hiero-building-the-next-generation-open-source-distributed-ledger-technology-together?hs_amp=true author: www title: www-hello-hiero-building-the-next-generation-open-source-distributed-ledger-technology-together?hs_amp=true date: None words: 1280 flesch: 46 summary: In a panel discussion moderated by Dr. Leemon Baird, Hedera’s Co-Founder, Chief Scientist at Hashgraph, and Hiero Technical Steering Committee (TSC) member, a diverse group of thought leaders and developers from Hedera’s ecosystem shared insights into the significance of this milestone and its impact on the future of open source blockchain development. Open governance means anyone can contribute to the codebase, ensuring that no single entity controls its future. Building a Collaborative Developer Ecosystem The transition to Hiero is a pivotal step in Hedera’s evolution. keywords: hedera; hiero; open; source cache: www-hello-hiero-building-the-next-generation-open-source-distributed-ledger-technology-together?hs_amp=true.html plain text: www-hello-hiero-building-the-next-generation-open-source-distributed-ledger-technology-together?hs_amp=true.txt item: #2756 of 3327 id: www-hello-hyperledger-bevel-bye-bye-blockchain-automation-framework-a-hyperledger-lab author: www title: www-hello-hyperledger-bevel-bye-bye-blockchain-automation-framework-a-hyperledger-lab date: None words: 902 flesch: 39 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger Bevel Hello Hyperledger Bevel; bye-bye Blockchain Automation Framework, a Hyperledger Lab Sownak Roy, Hyperledger Bevel Maintainer, and Tracy Kuhrt, Hyperledger TSC Chair | Dec 13, 2021 We are excited to announce that Blockchain Automation Framework has been accepted as the latest Hyperledger® project and has been renamed (and rebranded) as Hyperledger Bevel™.  Hello Hyperledger Bevel; bye-bye Blockchain Automation Framework, a Hyperledger Lab – Hyperledger Foundation 2025 keywords: bevel; dlt; hyperledger; project cache: www-hello-hyperledger-bevel-bye-bye-blockchain-automation-framework-a-hyperledger-lab.html plain text: www-hello-hyperledger-bevel-bye-bye-blockchain-automation-framework-a-hyperledger-lab.txt item: #2757 of 3327 id: www-help-hyperledger-cactus-advance-climate-action author: www title: www-help-hyperledger-cactus-advance-climate-action date: None words: 823 flesch: 41 summary: Help Hyperledger Cactus Advance Climate Action – Hyperledger Foundation 2025 Given that Hyperledger Cactus is a framework to make it easier to create and maintain software that operates across different distributed ledgers, maintainer Peter Somogyvari decided to evaluate what we could do to help. keywords: accounting; cactus; hyperledger cache: www-help-hyperledger-cactus-advance-climate-action.html plain text: www-help-hyperledger-cactus-advance-climate-action.txt item: #2758 of 3327 id: www-help-hyperledger-cactus-advance-climate-action?hs_amp=true author: www title: www-help-hyperledger-cactus-advance-climate-action?hs_amp=true date: None words: 512 flesch: 50 summary: Help Hyperledger Cactus Advance Climate Action – Hyperledger Foundation Blog | LF Decentralized Trust Help Hyperledger Cactus Advance Climate Action – Hyperledger Foundation Written by Hyperledger | Apr 26, 2021 9:30:00 AM “Climate change represents an existential threat to humanity and will require the greatest mobilization of resources and collaboration in human history.” Given that Hyperledger Cactus is a framework to make it easier to create and maintain software that operates across different distributed ledgers, maintainer Peter Somogyvari decided to evaluate what we could do to help. keywords: cactus; hyperledger cache: www-help-hyperledger-cactus-advance-climate-action?hs_amp=true.html plain text: www-help-hyperledger-cactus-advance-climate-action?hs_amp=true.txt item: #2759 of 3327 id: www-help-us-scale-up-our-operating-system-for-climate-action author: www title: www-help-us-scale-up-our-operating-system-for-climate-action date: None words: 923 flesch: 49 summary: There are three key modules: An immutable data channel built with Hyperledger Fabric to record emissions data, using energy data from utility bills and audited emissions factors from the EPA and EEA. We recently deployed the Hyperledger Fabric utility emissions and Ethereum emissions tokens networks into production to track and offset our own emissions. keywords: action; climate; emissions; hyperledger cache: www-help-us-scale-up-our-operating-system-for-climate-action.html plain text: www-help-us-scale-up-our-operating-system-for-climate-action.txt item: #2760 of 3327 id: www-helping-a-community-grow-by-pruning-inactive-projects author: www title: www-helping-a-community-grow-by-pruning-inactive-projects date: None words: 1277 flesch: 50 summary: That approach  will limit what new projects can get started in your community. TOC members have tools to investigate project status, including LFX Insights, Orbit and a tool to show the last commit on the default branch. keywords: community; foundation; hyperledger; project cache: www-helping-a-community-grow-by-pruning-inactive-projects.html plain text: www-helping-a-community-grow-by-pruning-inactive-projects.txt item: #2761 of 3327 id: www-helping-a-community-grow-by-pruning-inactive-projects?hs_amp=true author: www title: www-helping-a-community-grow-by-pruning-inactive-projects?hs_amp=true date: None words: 966 flesch: 57 summary: That approach  will limit what new projects can get started in your community. TOC members have tools to investigate project status, including LFX Insights, Orbit and a tool to show the last commit on the default branch. keywords: hyperledger; projects cache: www-helping-a-community-grow-by-pruning-inactive-projects?hs_amp=true.html plain text: www-helping-a-community-grow-by-pruning-inactive-projects?hs_amp=true.txt item: #2762 of 3327 id: www-hiero author: www title: www-hiero date: None words: 743 flesch: 21 summary: Blog | LF Decentralized Trust | Hiero 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? Offering unparalleled speed, security, and scalability, Hedera's... Read More By Alex Popowycz, Chief Information & Chief Information Security Officer, Hedera and Hiero Technical Steering Committee Member | Sep 16, 2024 keywords: community; decentralized; hiero; hyperledger; trust cache: www-hiero.html plain text: www-hiero.txt item: #2763 of 3327 id: www-hiero-advancing-decentralized-trust-through-open-source-innovation author: www title: www-hiero-advancing-decentralized-trust-through-open-source-innovation date: None words: 2301 flesch: 47 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hiero Hiero: Advancing Decentralized Trust Through Open Source Innovation Sophie Bulloch, Hiero Contributor, and Hendrik Ebbers, The Hiero project), a groundbreaking open source initiative under Linux Foundation Decentralized Trust, is at the forefront of advancing decentralized trust and addressing these needs.  keywords: decentralized; foundation; hedera; hiero; open; trust cache: www-hiero-advancing-decentralized-trust-through-open-source-innovation.html plain text: www-hiero-advancing-decentralized-trust-through-open-source-innovation.txt item: #2764 of 3327 id: www-hiero-advancing-decentralized-trust-through-open-source-innovation?hs_amp=true author: www title: www-hiero-advancing-decentralized-trust-through-open-source-innovation?hs_amp=true date: None words: 1991 flesch: 50 summary: Hiero: Advancing Decentralized Trust Through Open Source Innovation Blog | LF Decentralized Trust Hiero: Advancing Decentralized Trust Through Open Source Innovation Written by Sophie Bulloch, Hiero Contributor, and Hendrik Ebbers, Hiero Maintainer | Feb 12, 2025 2:00:00 PM Trust and transparency are essential for advancing digital systems in today's interconnected world. The Hiero project), a groundbreaking open source initiative under Linux Foundation Decentralized Trust, is at the forefront of advancing decentralized trust and addressing these needs.  keywords: decentralized; hedera; hiero; open; trust cache: www-hiero-advancing-decentralized-trust-through-open-source-innovation?hs_amp=true.html plain text: www-hiero-advancing-decentralized-trust-through-open-source-innovation?hs_amp=true.txt item: #2765 of 3327 id: www-hiero-community-1 author: www title: www-hiero-community-1 date: None words: 573 flesch: 17 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Blog | LF Decentralized Trust | Hiero Community 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? keywords: community; decentralized; hiero; hyperledger cache: www-hiero-community-1.html plain text: www-hiero-community-1.txt item: #2766 of 3327 id: www-highlights-from-the-enterprise-blockchain-and-the-hyperledger-brand-report-from-linux-foundation-research author: www title: www-highlights-from-the-enterprise-blockchain-and-the-hyperledger-brand-report-from-linux-foundation-research date: None words: 798 flesch: 35 summary: However, the report also highlights places where there is work still to be done in terms of driving adoption and in brand building, especially for the full range of Hyperledger projects. The report and a full breakdown of the survey findings are available to Hyperledger members. keywords: blockchain; foundation; hyperledger cache: www-highlights-from-the-enterprise-blockchain-and-the-hyperledger-brand-report-from-linux-foundation-research.html plain text: www-highlights-from-the-enterprise-blockchain-and-the-hyperledger-brand-report-from-linux-foundation-research.txt item: #2767 of 3327 id: www-himss-2019-myndshft-delivers-a-recap author: www title: www-himss-2019-myndshft-delivers-a-recap date: None words: 1151 flesch: 44 summary: The reality is that Hyperledger blockchains like Fabric and Sawtooth are able to coexist with existing IT systems and provide functionality that their existing systems don’t have and never will have without a network. Thoughts on Hyperledger Booth at HIMSS Most people inquiring about blockchain at HIMSS this year were looking for ideas, thoughts, and examples of how blockchain could and should be implemented in healthcare. keywords: blockchain; healthcare; hyperledger; technologies cache: www-himss-2019-myndshft-delivers-a-recap.html plain text: www-himss-2019-myndshft-delivers-a-recap.txt item: #2768 of 3327 id: www-hitachi-shifts-to-paperless-secure-procurement-contracts-with-hyperledger-fabric author: www title: www-hitachi-shifts-to-paperless-secure-procurement-contracts-with-hyperledger-fabric date: None words: 798 flesch: 47 summary: They chose Hyperledger Fabric, an open source blockchain framework from Hyperledger Foundation. Division personnel now have time to focus on other important tasks like investigation, negotiation, and engaging with new contract companies. keywords: case; hitachi; procurement cache: www-hitachi-shifts-to-paperless-secure-procurement-contracts-with-hyperledger-fabric.html plain text: www-hitachi-shifts-to-paperless-secure-procurement-contracts-with-hyperledger-fabric.txt item: #2769 of 3327 id: www-hitachi-shifts-to-paperless-secure-procurement-contracts-with-hyperledger-fabric?hs_amp=true author: www title: www-hitachi-shifts-to-paperless-secure-procurement-contracts-with-hyperledger-fabric?hs_amp=true date: None words: 487 flesch: 56 summary: Hitachi Shifts to Paperless, Secure Procurement Contracts with Hyperledger Fabric  – Hyperledger Foundation Blog | LF Decentralized Trust Hitachi Shifts to Paperless, Secure Procurement Contracts with Hyperledger Fabric  – Hyperledger Foundation Written by Hyperledger | Jun 7, 2022 9:10:00 AM Read the full case study here. Hitachi had already created blockchain-backed frameworks on Hyperledger Fabric in its financial and industrial areas, so the team members knew it could provide the advanced security needed for critical document processing. keywords: hitachi; hyperledger cache: www-hitachi-shifts-to-paperless-secure-procurement-contracts-with-hyperledger-fabric?hs_amp=true.html plain text: www-hitachi-shifts-to-paperless-secure-procurement-contracts-with-hyperledger-fabric?hs_amp=true.txt item: #2770 of 3327 id: www-honeywell-case-study-summary author: www title: www-honeywell-case-study-summary date: None words: 465 flesch: 34 summary: Honeywell Aerospace creates online parts marketplace with Hyperledger Fabric 2025 Update: Off to a Fast Start!  How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger Fabric Honeywell Aerospace creates online parts marketplace with Hyperledger Fabric Hyperledger Foundation | Nov 14, 2019 Problem Used aerospace parts are a $4 billion market, and growing. keywords: decentralized; foundation; linux cache: www-honeywell-case-study-summary.html plain text: www-honeywell-case-study-summary.txt item: #2771 of 3327 id: www-hope-through-innovation-a-cop29-perspective-on-climate-innovation-for-2025 author: www title: www-hope-through-innovation-a-cop29-perspective-on-climate-innovation-for-2025 date: None words: 883 flesch: 35 summary: These advances align perfectly with CA2SIG's vision of creating an open, global system that balances emissions against climate actions. As Chair of LF Decentralized Trust’s Climate Action and Accounting Special Interest Group (CA2SIG), I saw firsthand how climate technology innovations are quietly transforming our ability to tackle the climate crisis. keywords: action; climate; decentralized; interest cache: www-hope-through-innovation-a-cop29-perspective-on-climate-innovation-for-2025.html plain text: www-hope-through-innovation-a-cop29-perspective-on-climate-innovation-for-2025.txt item: #2772 of 3327 id: www-hope-through-innovation-a-cop29-perspective-on-climate-innovation-for-2025?hs_amp=true author: www title: www-hope-through-innovation-a-cop29-perspective-on-climate-innovation-for-2025?hs_amp=true date: None words: 569 flesch: 41 summary: These advances align perfectly with CA2SIG's vision of creating an open, global system that balances emissions against climate actions. Our advocacy for interoperable, open-source solutions was a core shared belief of many throughout the conference, reinforcing our belief that effective climate action requires unprecedented cooperation. keywords: action; climate cache: www-hope-through-innovation-a-cop29-perspective-on-climate-innovation-for-2025?hs_amp=true.html plain text: www-hope-through-innovation-a-cop29-perspective-on-climate-innovation-for-2025?hs_amp=true.txt item: #2773 of 3327 id: www-how-aais-aligned-insurers-and-regulators-with-the-hyperledger-fabric-based-openidl-data-reporting-network author: www title: www-how-aais-aligned-insurers-and-regulators-with-the-hyperledger-fabric-based-openidl-data-reporting-network date: None words: 835 flesch: 44 summary: Every time a natural catastrophe strikes, state regulators quickly ask insurance carriers to send them data about the affected properties. That led to the choice of Hyperledger Fabric. keywords: aais; data; openidl; regulators cache: www-how-aais-aligned-insurers-and-regulators-with-the-hyperledger-fabric-based-openidl-data-reporting-network.html plain text: www-how-aais-aligned-insurers-and-regulators-with-the-hyperledger-fabric-based-openidl-data-reporting-network.txt item: #2774 of 3327 id: www-how-blockchain-is-reinventing-business-process-management author: www title: www-how-blockchain-is-reinventing-business-process-management date: None words: 1130 flesch: 39 summary: By leveraging smart contracts and the auditability of distributed ledger technologies, blockchain can facilitate processes involving multiple parties following specific regulatory guidelines. If blockchain technology provides value in BPM, how is it different than the BPM solutions and services available today? keywords: blockchain; bpm; party; process cache: www-how-blockchain-is-reinventing-business-process-management.html plain text: www-how-blockchain-is-reinventing-business-process-management.txt item: #2775 of 3327 id: www-how-hyperledger-besu-will-help-solve-the-pharmaceutical-waste-problem-in-the-u-s author: www title: www-how-hyperledger-besu-will-help-solve-the-pharmaceutical-waste-problem-in-the-u-s date: None words: 1103 flesch: 45 summary: How technology can help  Our experience with blockchain and distributed applications proves that these technologies can become the core of an effective and secure platform for unused drug donation and redistribution. The rules require that unused drugs be disposed of through incineration that creates additional environmental concerns.  keywords: besu; drug; hyperledger; project cache: www-how-hyperledger-besu-will-help-solve-the-pharmaceutical-waste-problem-in-the-u-s.html plain text: www-how-hyperledger-besu-will-help-solve-the-pharmaceutical-waste-problem-in-the-u-s.txt item: #2776 of 3327 id: www-how-hyperledger-fabric-helped-everledger-transform-a-market-and-blaze-a-trail-for-others-to-follow author: www title: www-how-hyperledger-fabric-helped-everledger-transform-a-market-and-blaze-a-trail-for-others-to-follow date: None words: 1423 flesch: 31 summary: Everledger was quick to tap into the power of Hyperledger Fabric to power its Origin Program, which traces each diamond's journey from its origin deep within the Earth until it arrives, ready to wear, at a customer. How Hyperledger Fabric Helped Everledger Transform a Market 2025 Update: Off to a Fast Start! keywords: blockchain; everledger; fabric; hyperledger; origin; program cache: www-how-hyperledger-fabric-helped-everledger-transform-a-market-and-blaze-a-trail-for-others-to-follow.html plain text: www-how-hyperledger-fabric-helped-everledger-transform-a-market-and-blaze-a-trail-for-others-to-follow.txt item: #2777 of 3327 id: www-how-hyperledger-fabric-helped-everledger-transform-a-market-and-blaze-a-trail-for-others-to-follow?hs_amp=true author: www title: www-how-hyperledger-fabric-helped-everledger-transform-a-market-and-blaze-a-trail-for-others-to-follow?hs_amp=true date: None words: 1101 flesch: 33 summary: How Hyperledger Fabric Helped Everledger Transform a Market Blog | LF Decentralized Trust How Hyperledger Fabric Helped Everledger Transform a Market Written by Leanne Kemp, Founder and CEO, Everledger | Sep 25, 2023 3:58:40 PM From the earliest days of blockchain technologies, Everledger has seen its potential to revolutionize the way we perceive and engage with supply chains and ethical practices. Everledger was quick to tap into the power of Hyperledger Fabric to power its Origin Program, which traces each diamond's journey from its origin deep within the Earth until it arrives, ready to wear, at a customer. keywords: everledger; fabric; hyperledger; origin cache: www-how-hyperledger-fabric-helped-everledger-transform-a-market-and-blaze-a-trail-for-others-to-follow?hs_amp=true.html plain text: www-how-hyperledger-fabric-helped-everledger-transform-a-market-and-blaze-a-trail-for-others-to-follow?hs_amp=true.txt item: #2778 of 3327 id: www-how-innovative-supply-chain-solutions-can-increase-blockchain-adoption author: www title: www-how-innovative-supply-chain-solutions-can-increase-blockchain-adoption date: None words: 1479 flesch: 35 summary: Hyperledger Fabric is a mature framework that is well suited to deliver low latency, high throughput, and fast send rates along with privacy controls needed for supply chain solutions. Snapper has been working with customers across industries for supply chain solutions.  keywords: blockchain; chain; network; solutions; supply; use cache: www-how-innovative-supply-chain-solutions-can-increase-blockchain-adoption.html plain text: www-how-innovative-supply-chain-solutions-can-increase-blockchain-adoption.txt item: #2779 of 3327 id: www-how-to-deploy-hyperledger-fabric-on-kubernetes-part-ii author: www title: www-how-to-deploy-hyperledger-fabric-on-kubernetes-part-ii date: None words: 2951 flesch: 54 summary: Install Fabric CA Helm Chart Let’s install the actual Fabric CA Chart. Fabric CA To install Fabric CA, you’ll need to follow these steps: Install Fabric CA Helm Chart Generate Fabric CA Identity Obtain Crypto Material Save Crypto Material to K8S Generate Genesis and Channel Let us go through them one by one. keywords: blockchain; channel; fabric; install; kubectl; peer cache: www-how-to-deploy-hyperledger-fabric-on-kubernetes-part-ii.html plain text: www-how-to-deploy-hyperledger-fabric-on-kubernetes-part-ii.txt item: #2780 of 3327 id: www-hyperledger author: www title: www-hyperledger date: None words: 1416 flesch: 27 summary: Blog | LF Decentralized Trust | Hyperledger 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? Read More Hyperledger | Jun 1, 2023 Hyperledger Community Kaleido works with Hyperledger Foundation to advance Hyperledger FireFly Read the full case study here. keywords: besu; community; decentralized; hyperledger; maintainers cache: www-hyperledger.html plain text: www-hyperledger.txt item: #2781 of 3327 id: www-hyperledger-2018-summer-interns-recap author: www title: www-hyperledger-2018-summer-interns-recap date: None words: 1883 flesch: 53 summary: The aim of this project was to help the developers to translate the publicly available Solidity smart contracts into readable and, hopefully, functionally equivalent Hyperledger Fabric contracts without writing the contracts from scratch. Here, their own words, are the goals, successes and lessons learned from each intern: Ahmad Zafar (Project: Running Solidity Smart Contracts on Hyperledger Fabric or Vice Versa) Project goals: I was working on Running Solidity Smart Contracts on Hyperledger Fabric Project. keywords: blockchain; code; contracts; fabric; hyperledger; project cache: www-hyperledger-2018-summer-interns-recap.html plain text: www-hyperledger-2018-summer-interns-recap.txt item: #2782 of 3327 id: www-hyperledger-2018-summer-interns-recap?hs_amp=true author: www title: www-hyperledger-2018-summer-interns-recap?hs_amp=true date: None words: 1572 flesch: 58 summary: The aim of this project was to help the developers to translate the publicly available Solidity smart contracts into readable and, hopefully, functionally equivalent Hyperledger Fabric contracts without writing the contracts from scratch. However, before starting this project, I had little knowledge about Ethereum and Hyperledger Fabric smart contracts. keywords: contracts; fabric; hyperledger; project cache: www-hyperledger-2018-summer-interns-recap?hs_amp=true.html plain text: www-hyperledger-2018-summer-interns-recap?hs_amp=true.txt item: #2783 of 3327 id: www-hyperledger-anoncreds author: www title: www-hyperledger-anoncreds date: None words: 1000 flesch: 10 summary: Now, with the input... Read More Daniela Barbosa, Executive Director at Hyperledger Foundation and General Manager, Blockchain and Identity for the Linux Foundation | Apr 23, 2024 Hyperledger AnonCreds | Hyperledger Aries Hyperledger Aries: An Epicenter for Decentralized Digital Identity Collaboration and Innovation How was 2023 for Hyperledger Aries, and what’s in store for 2024? Read More Hyperledger | Jul 6, 2023 Hyperledger AnonCreds | Hyperledger Aries | Decentralized Identity Why Hyperledger Foundation Sponsors Internet Identity Workshop Since the launch of Hyperledger Indy, a DLT purpose-built for decentralized identity, in 2017, Hyperledger Foundation has been a proud sponsor, attendee and contributor to the... Read More Hyperledger | Apr 11, 2023 Blog | Hyperledger AnonCreds Announcing Hyperledger AnonCreds: Open Source, Open Specification Privacy Preserving Verifiable Credentials AnonCreds, the most commonly used Verifiable Credential (VC) format in the world*, is now a Hyperledger project. keywords: anoncreds; aries; decentralized; hyperledger cache: www-hyperledger-anoncreds.html plain text: www-hyperledger-anoncreds.txt item: #2784 of 3327 id: www-hyperledger-aries author: www title: www-hyperledger-aries date: None words: 1545 flesch: 20 summary: Read More Naian G | Mar 13, 2024 Hyperledger Aries | Hyperledger Bevel | Labs Meet Aries Agent Controller, a New Hyperledger Lab A code base developed and contributed by Superlogic that facilitates deploying Hyperledger Aries agents in cloud environments is the latest Hyperledger lab. Blog | LF Decentralized Trust | Hyperledger Aries 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? keywords: aries; decentralized; digital; hyperledger; identity; trust cache: www-hyperledger-aries.html plain text: www-hyperledger-aries.txt item: #2785 of 3327 id: www-hyperledger-aries-an-epicenter-for-decentralized-digital-identity-collaboration-and-innovation author: www title: www-hyperledger-aries-an-epicenter-for-decentralized-digital-identity-collaboration-and-innovation date: None words: 1268 flesch: 34 summary: An evolution of the “Start Here” documentation for the Aries Frameworks Marketing: Publishing information about the range and maturity of Aries capabilities and improving the overall awareness of Aries in digital trust and corporate circles. How was 2023 for Hyperledger Aries, and what’s in store for 2024? keywords: aries; decentralized; digital; hyperledger; trust cache: www-hyperledger-aries-an-epicenter-for-decentralized-digital-identity-collaboration-and-innovation.html plain text: www-hyperledger-aries-an-epicenter-for-decentralized-digital-identity-collaboration-and-innovation.txt item: #2786 of 3327 id: www-hyperledger-aries-an-epicenter-for-decentralized-digital-identity-collaboration-and-innovation?hs_amp=true author: www title: www-hyperledger-aries-an-epicenter-for-decentralized-digital-identity-collaboration-and-innovation?hs_amp=true date: None words: 954 flesch: 37 summary: An evolution of the “Start Here” documentation for the Aries Frameworks Marketing: Publishing information about the range and maturity of Aries capabilities and improving the overall awareness of Aries in digital trust and corporate circles. Hyperledger Aries: An Epicenter for Decentralized Digital Identity Collaboration and Innovation Blog | LF Decentralized Trust Hyperledger Aries: An Epicenter for Decentralized Digital Identity Collaboration and Innovation Written by Hyperledger Aries Working Group | Apr 4, 2024 3:00:00 PM How was 2023 for Hyperledger Aries, and what’s in store for 2024? keywords: aries; digital; hyperledger cache: www-hyperledger-aries-an-epicenter-for-decentralized-digital-identity-collaboration-and-innovation?hs_amp=true.html plain text: www-hyperledger-aries-an-epicenter-for-decentralized-digital-identity-collaboration-and-innovation?hs_amp=true.txt item: #2787 of 3327 id: www-hyperledger-aries-framework-javascript-identity-wallets-standards-push author: www title: www-hyperledger-aries-framework-javascript-identity-wallets-standards-push date: None words: 947 flesch: 38 summary: AFJ is a Hyperledger Aries-based framework that supports Hyperledger AnonCreds and DIDComm-based protocols, such as issue-credential-v2 and out-of-band/did-exchange, based on Aries RFCs. Given our prior experience with the Hyperledger Aries/Indy ecosystem and the fact that it seemed amongst one of the more mature ecosystems out there, we opted for Hyperledger Aries Framework JavaScript (AFJ). keywords: aries; framework; hyperledger; identity cache: www-hyperledger-aries-framework-javascript-identity-wallets-standards-push.html plain text: www-hyperledger-aries-framework-javascript-identity-wallets-standards-push.txt item: #2788 of 3327 id: www-hyperledger-aries-framework-javascript-identity-wallets-standards-push?hs_amp=true author: www title: www-hyperledger-aries-framework-javascript-identity-wallets-standards-push?hs_amp=true date: None words: 627 flesch: 44 summary: AFJ is a Hyperledger Aries-based framework that supports Hyperledger AnonCreds and DIDComm-based protocols, such as issue-credential-v2 and out-of-band/did-exchange, based on Aries RFCs. Given our prior experience with the Hyperledger Aries/Indy ecosystem and the fact that it seemed amongst one of the more mature ecosystems out there, we opted for Hyperledger Aries Framework JavaScript (AFJ). keywords: aries; hyperledger cache: www-hyperledger-aries-framework-javascript-identity-wallets-standards-push?hs_amp=true.html plain text: www-hyperledger-aries-framework-javascript-identity-wallets-standards-push?hs_amp=true.txt item: #2789 of 3327 id: www-hyperledger-aries-graduates-to-active-status-joins-indy-as-production-ready-hyperledger-projects-for-decentralized-identity author: www title: www-hyperledger-aries-graduates-to-active-status-joins-indy-as-production-ready-hyperledger-projects-for-decentralized-identity date: None words: 1120 flesch: 35 summary: As “Production Ready” Hyperledger Projects for Decentralized Identity Hyperledger | Feb 26, 2021 The Hyperledger Technical Steering Committee (TSC) has approved Hyperledger Aries as the latest of Hyperledger’s projects to graduate from incubation to active status. Hyperledger Aries provides reusable, interoperable tool kits designed for initiatives and solutions focused on creating, transmitting and storing verifiable digital credentials. keywords: aries; decentralized; hyperledger; identity cache: www-hyperledger-aries-graduates-to-active-status-joins-indy-as-production-ready-hyperledger-projects-for-decentralized-identity.html plain text: www-hyperledger-aries-graduates-to-active-status-joins-indy-as-production-ready-hyperledger-projects-for-decentralized-identity.txt item: #2790 of 3327 id: www-hyperledger-aries-graduates-to-active-status-joins-indy-as-production-ready-hyperledger-projects-for-decentralized-identity?hs_amp=true author: www title: www-hyperledger-aries-graduates-to-active-status-joins-indy-as-production-ready-hyperledger-projects-for-decentralized-identity?hs_amp=true date: None words: 808 flesch: 40 summary: As “Production Ready” Hyperledger Projects for Decentralized Identity – Hyperledger Foundation Written by Hyperledger | Feb 26, 2021 7:15:48 AM The Hyperledger Technical Steering Committee (TSC) has approved Hyperledger Aries as the latest of Hyperledger’s projects to graduate from incubation to active status. Hyperledger Aries provides reusable, interoperable tool kits designed for initiatives and solutions focused on creating, transmitting and storing verifiable digital credentials. keywords: aries; hyperledger cache: www-hyperledger-aries-graduates-to-active-status-joins-indy-as-production-ready-hyperledger-projects-for-decentralized-identity?hs_amp=true.html plain text: www-hyperledger-aries-graduates-to-active-status-joins-indy-as-production-ready-hyperledger-projects-for-decentralized-identity?hs_amp=true.txt item: #2791 of 3327 id: www-hyperledger-aries-working-group author: www title: www-hyperledger-aries-working-group date: None words: 532 flesch: 19 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Hyperledger AnonCreds | Hyperledger Aries Hyperledger Aries: An Epicenter for Decentralized Digital Identity Collaboration and Innovation How was 2023 for Hyperledger Aries, and what’s in store for 2024? keywords: blog; decentralized; hyperledger; technologies cache: www-hyperledger-aries-working-group.html plain text: www-hyperledger-aries-working-group.txt item: #2792 of 3327 id: www-hyperledger-avalon author: www title: www-hyperledger-avalon date: None words: 614 flesch: 27 summary: Next page > Submit a blog Blog guidelines RSS Hyperledger Avalon | Blockchain Pioneers Blockchain Pioneers: Hyperledger Avalon As Hyperledger Foundation laid out in the Helping a Community Grow by Pruning Inactive... Dec 16, 2024 Blog | Hyperledger Avalon Where to find Hyperledger at Consensus: Distributed Consensus: Distributed is coming up quickly. keywords: avalon; blog; decentralized; hyperledger cache: www-hyperledger-avalon.html plain text: www-hyperledger-avalon.txt item: #2793 of 3327 id: www-hyperledger-besu-1-5-performance-enhancements author: www title: www-hyperledger-besu-1-5-performance-enhancements date: None words: 1792 flesch: 52 summary: In order to get repeatable measurements for our TPS improvements, we worked with Hyperledger Caliper, another project under the Hyperledger umbrella to benchmark our numbers across various Besu versions.  Download Hyperledger Besu Join the Conversation about Hyperledger Besu View previous blog post Back to all blog posts View next blog post The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: besu; hyperledger; java; performance; second; use cache: www-hyperledger-besu-1-5-performance-enhancements.html plain text: www-hyperledger-besu-1-5-performance-enhancements.txt item: #2794 of 3327 id: www-hyperledger-besu-1-5-performance-enhancements?hs_amp=true author: www title: www-hyperledger-besu-1-5-performance-enhancements?hs_amp=true date: None words: 1484 flesch: 57 summary: Download Hyperledger Besu Join the Conversation about Hyperledger Besu View full post In order to get repeatable measurements for our TPS improvements, we worked with Hyperledger Caliper, another project under the Hyperledger umbrella to benchmark our numbers across various Besu versions.  keywords: besu; hyperledger; performance; second cache: www-hyperledger-besu-1-5-performance-enhancements?hs_amp=true.html plain text: www-hyperledger-besu-1-5-performance-enhancements?hs_amp=true.txt item: #2795 of 3327 id: www-hyperledger-besu-graduates-to-active-status author: www title: www-hyperledger-besu-graduates-to-active-status date: None words: 899 flesch: 40 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Besu Hyperledger Besu Graduates to Active Status Hyperledger | Mar 30, 2020 The Hyperledger Besu team is excited to announce Hyperledger’s Technical Steering Committee (TSC) members voted to graduate the project from incubation to active status. The Hyperledger Besu team believes this decision demonstrates the strength of the Besu project and the active community supporting it. keywords: besu; hyperledger; project; status cache: www-hyperledger-besu-graduates-to-active-status.html plain text: www-hyperledger-besu-graduates-to-active-status.txt item: #2796 of 3327 id: www-hyperledger-besu-security-audit-2020 author: www title: www-hyperledger-besu-security-audit-2020 date: None words: 994 flesch: 46 summary: The Hyperledger Besu team was pleased to partner with Tevora on this security audit and work with them closely on their findings. Configuration:  Summary of Finding: The Hyperledger Besu client includes a configurable GraphQL endpoint for data queries. keywords: besu; hyperledger; security; team cache: www-hyperledger-besu-security-audit-2020.html plain text: www-hyperledger-besu-security-audit-2020.txt item: #2797 of 3327 id: www-hyperledger-bevel author: www title: www-hyperledger-bevel date: None words: 1067 flesch: 18 summary: Looking to work directly with mentors who... Read More Hyperledger | Apr 6, 2022 Hyperledger Bevel Hello Hyperledger Bevel; bye-bye Blockchain Automation Framework, a Hyperledger Lab We are excited to announce that Blockchain Automation Framework has been accepted as the latest Hyperledger® project and has been renamed (and rebranded) as Hyperledger Bevel™.... Read More Sownak Roy, Hyperledger Bevel Maintainer, and Tracy Kuhrt, Hyperledger TSC Chair | Dec 13, 2021 Blog | Hyperledger Bevel Blockchain Automation Framework – the journey In the early days and excitement of blockchain, we saw the proverbial ‘hammer looking for nail’ application of the technology across nearly every use case. The new lab, Aries... Read More Superlogic, maintainers of Aries Agent Controller | Feb 29, 2024 Hyperledger Bevel Hyperledger Bevel Release 1.0: Paving the Way for Seamless and Secure Blockchain Deployments We are delighted to unveil the highly anticipated release of Hyperledger Bevel version 1.0, marking a pivotal moment in our journey toward creating an advanced blockchain... keywords: bevel; blockchain; blog; decentralized; hyperledger cache: www-hyperledger-bevel.html plain text: www-hyperledger-bevel.txt item: #2798 of 3327 id: www-hyperledger-bevel-release-1.0-paving-the-way-for-seamless-and-secure-blockchain-deployments author: www title: www-hyperledger-bevel-release-1.0-paving-the-way-for-seamless-and-secure-blockchain-deployments date: None words: 944 flesch: 37 summary: Paving the Way for Seamless and Secure Blockchain Deployments 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger Bevel Hyperledger Bevel Release 1.0: Paving the Way for Seamless and Secure Blockchain Deployments Sownak Roy, Tech Strategy Manager at Accenture and Suvajit Sarkar, Tech Research Principal at Accenture, Hyperledger Bevel Maintainers | Jan 9, 2024 We are delighted to unveil the highly anticipated release of Hyperledger Bevel version 1.0, marking a pivotal moment in our journey toward creating an advanced blockchain automation tool. Hyperledger Bevel v1.0 introduces new features and refined deployment processes, elevating the efficiency and security of blockchain network setups. keywords: bevel; blockchain; deployment; hyperledger cache: www-hyperledger-bevel-release-1.0-paving-the-way-for-seamless-and-secure-blockchain-deployments.html plain text: www-hyperledger-bevel-release-1.0-paving-the-way-for-seamless-and-secure-blockchain-deployments.txt item: #2799 of 3327 id: www-hyperledger-bevel-release-1.0-paving-the-way-for-seamless-and-secure-blockchain-deployments?hs_amp=true author: www title: www-hyperledger-bevel-release-1.0-paving-the-way-for-seamless-and-secure-blockchain-deployments?hs_amp=true date: None words: 633 flesch: 43 summary: Paving the Way for Seamless and Secure Blockchain Deployments Written by Sownak Roy, Tech Strategy Manager at Accenture and Suvajit Sarkar, Tech Research Principal at Accenture, Hyperledger Bevel Maintainers | Jan 9, 2024 5:00:00 PM We are delighted to unveil the highly anticipated release of Hyperledger Bevel version 1.0, marking a pivotal moment in our journey toward creating an advanced blockchain automation tool. Hyperledger Bevel v1.0 introduces new features and refined deployment processes, elevating the efficiency and security of blockchain network setups. keywords: bevel; hyperledger cache: www-hyperledger-bevel-release-1.0-paving-the-way-for-seamless-and-secure-blockchain-deployments?hs_amp=true.html plain text: www-hyperledger-bevel-release-1.0-paving-the-way-for-seamless-and-secure-blockchain-deployments?hs_amp=true.txt item: #2800 of 3327 id: www-hyperledger-bug-bounty-program-now-open author: www title: www-hyperledger-bug-bounty-program-now-open date: None words: 1143 flesch: 46 summary: The Hyperledger security team manages and executes our policy of responsible disclosure of security bugs. Security bugs are confidentially reported to Hyperledger through security@hyperledger.org or by filing a security bug in our JIRA. keywords: bounty; bug; hyperledger; security cache: www-hyperledger-bug-bounty-program-now-open.html plain text: www-hyperledger-bug-bounty-program-now-open.txt item: #2801 of 3327 id: www-hyperledger-bug-bounty-program-now-open?hs_amp=true author: www title: www-hyperledger-bug-bounty-program-now-open?hs_amp=true date: None words: 832 flesch: 54 summary: The Core Infrastructure Initiative is a set of best practices for open source software security. The Hyperledger security team manages and executes our policy of responsible disclosure of security bugs. keywords: hyperledger; security cache: www-hyperledger-bug-bounty-program-now-open?hs_amp=true.html plain text: www-hyperledger-bug-bounty-program-now-open?hs_amp=true.txt item: #2802 of 3327 id: www-hyperledger-burrow author: www title: www-hyperledger-burrow date: None words: 917 flesch: 34 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Blog | LF Decentralized Trust | Hyperledger Burrow 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us BLOG The latest community news, insights and developments Stay connected with the latest in open source decentralized technologies, member updates, and community-driven projects. keywords: blog; burrow; decentralized; hyperledger cache: www-hyperledger-burrow.html plain text: www-hyperledger-burrow.txt item: #2803 of 3327 id: www-hyperledger-burrow-even-faster-and-easier-to-use author: www title: www-hyperledger-burrow-even-faster-and-easier-to-use date: None words: 1044 flesch: 34 summary: As multiple systems, including the Agreements Network whose development is initially being led by Monax, built on Hyperledger Burrow continue to iterate towards production capacity the maintainers look forward to continuing to work with the community to ensure that Burrow remains the easiest and quickest way to run Ethereum smart contracts in a permissioned context. Hyperledger Burrow is built to be a unitary binary, and a fast, lightweight and easy to get to grips blockchain framework. keywords: burrow; foundation; hyperledger; use cache: www-hyperledger-burrow-even-faster-and-easier-to-use.html plain text: www-hyperledger-burrow-even-faster-and-easier-to-use.txt item: #2804 of 3327 id: www-hyperledger-burrow-even-faster-and-easier-to-use?hs_amp=true author: www title: www-hyperledger-burrow-even-faster-and-easier-to-use?hs_amp=true date: None words: 733 flesch: 42 summary: As multiple systems, including the Agreements Network whose development is initially being led by Monax, built on Hyperledger Burrow continue to iterate towards production capacity the maintainers look forward to continuing to work with the community to ensure that Burrow remains the easiest and quickest way to run Ethereum smart contracts in a permissioned context. Hyperledger Burrow is built to be a unitary binary, and a fast, lightweight and easy to get to grips blockchain framework. keywords: burrow; contract; hyperledger cache: www-hyperledger-burrow-even-faster-and-easier-to-use?hs_amp=true.html plain text: www-hyperledger-burrow-even-faster-and-easier-to-use?hs_amp=true.txt item: #2805 of 3327 id: www-hyperledger-cacti author: www title: www-hyperledger-cacti date: None words: 1472 flesch: 28 summary: – Hyperledger Climate... Read More Hyperledger | Apr 26, 2021 Blog | Hyperledger Cacti Hyperledger Cactus: On the Road to General Blockchain Integration Since its inception as a Hyperledger project almost a year ago, Hyperledger Cactus has come a long way. Governance Hyperledger Cacti, A General-Purpose Modular Interoperability Framework, Moves to Graduated Status Almost a year ago, we announced the creation of Hyperledger Cacti, which resulted from the merger of two pre-existing projects, Hyperledger Cactus and Weaver, a Hyperledger lab,... Read More Hyperledger Cacti Maintainers | Oct 3, 2023 Blog keywords: blockchain; blog; cacti; hyperledger; interoperability; project cache: www-hyperledger-cacti.html plain text: www-hyperledger-cacti.txt item: #2806 of 3327 id: www-hyperledger-cacti-a-general-purpose-modular-interoperability-framework-moves-to-graduated-status author: www title: www-hyperledger-cacti-a-general-purpose-modular-interoperability-framework-moves-to-graduated-status date: None words: 1250 flesch: 37 summary: Hyperledger Cacti as a project has been the personification of interoperability and modularity, said Hart Montgomery, CTO of Hyperledger Foundation. The graduation of Hyperledger Cacti into a mature enterprise-grade solution for blockchain and DLT interoperability is a testament to the spirit of open collaboration and commitment shown by the maintainers, contributors, and users in the Hyperledger community, not to mention the active support and encouragement of the Hyperledger staff and TOC. keywords: cacti; decentralized; hyperledger; interoperability; project cache: www-hyperledger-cacti-a-general-purpose-modular-interoperability-framework-moves-to-graduated-status.html plain text: www-hyperledger-cacti-a-general-purpose-modular-interoperability-framework-moves-to-graduated-status.txt item: #2807 of 3327 id: www-hyperledger-cacti-a-general-purpose-modular-interoperability-framework-moves-to-graduated-status?hs_amp=true author: www title: www-hyperledger-cacti-a-general-purpose-modular-interoperability-framework-moves-to-graduated-status?hs_amp=true date: None words: 931 flesch: 42 summary: Hyperledger Cacti, Moves to Graduated Status Blog | LF Decentralized Trust Hyperledger Cacti, Moves to Graduated Status Written by Hyperledger Cacti Maintainers | Oct 3, 2023 10:11:25 PM Almost a year ago, we announced the creation of Hyperledger Cacti, which resulted from the merger of two pre-existing projects, Hyperledger Cactus and Weaver, a Hyperledger lab, both of which had similar missions and goals, and which offered complementary feature sets to handle a wide variety of cross-ledger interoperability scenarios. The graduation of Hyperledger Cacti into a mature enterprise-grade solution for blockchain and DLT interoperability is a testament to the spirit of open collaboration and commitment shown by the maintainers, contributors, and users in the Hyperledger community, not to mention the active support and encouragement of the Hyperledger staff and TOC. keywords: cacti; hyperledger; interoperability; project cache: www-hyperledger-cacti-a-general-purpose-modular-interoperability-framework-moves-to-graduated-status?hs_amp=true.html plain text: www-hyperledger-cacti-a-general-purpose-modular-interoperability-framework-moves-to-graduated-status?hs_amp=true.txt item: #2808 of 3327 id: www-hyperledger-cacti-maintainers author: www title: www-hyperledger-cacti-maintainers date: None words: 528 flesch: 15 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page | Governance Hyperledger Cacti, A General-Purpose Modular Interoperability Framework, Moves to Graduated Status Almost a year ago, we announced the creation of Hyperledger Cacti, which resulted from the merger... keywords: blog; decentralized; hyperledger; technologies cache: www-hyperledger-cacti-maintainers.html plain text: www-hyperledger-cacti-maintainers.txt item: #2809 of 3327 id: www-hyperledger-cactus-hyperledger-firefly-weaver-and-yui-technical-communities author: www title: www-hyperledger-cactus-hyperledger-firefly-weaver-and-yui-technical-communities date: None words: 534 flesch: 19 summary: Blog | LF Decentralized Trust | Hyperledger Cactus, Hyperledger FireFly, Weaver and YUI technical communities 2025 Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page keywords: blog; decentralized; hyperledger cache: www-hyperledger-cactus-hyperledger-firefly-weaver-and-yui-technical-communities.html plain text: www-hyperledger-cactus-hyperledger-firefly-weaver-and-yui-technical-communities.txt item: #2810 of 3327 id: www-hyperledger-cactus-on-the-road-to-general-blockchain-integration author: www title: www-hyperledger-cactus-on-the-road-to-general-blockchain-integration date: None words: 938 flesch: 40 summary: We provide instructions for running a sample implementation of the Business Logic Plugins (service applications in Hyperledger Cactus architecture) that takes advantage of various blockchain platform features so you can evaluate Hyperledger Cactus on your own PC. How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog | Hyperledger Cacti Hyperledger Cactus: On the Road to General Blockchain Integration Hyperledger | Mar 31, 2021 Since its inception as a Hyperledger project almost a year ago, Hyperledger Cactus has come a long way. keywords: blockchain; cactus; hyperledger; integration cache: www-hyperledger-cactus-on-the-road-to-general-blockchain-integration.html plain text: www-hyperledger-cactus-on-the-road-to-general-blockchain-integration.txt item: #2811 of 3327 id: www-hyperledger-cactus-on-the-road-to-general-blockchain-integration?hs_amp=true author: www title: www-hyperledger-cactus-on-the-road-to-general-blockchain-integration?hs_amp=true date: None words: 627 flesch: 47 summary: | LF Decentralized Trust Hyperledger Cactus: On the Road to General Blockchain Integration – Hyperledger Foundation Written by Hyperledger | Mar 31, 2021 9:00:00 AM Since its inception as a Hyperledger project almost a year ago, Hyperledger Cactus has come a long way. We provide instructions for running a sample implementation of the Business Logic Plugins (service applications in Hyperledger Cactus architecture) that takes advantage of various blockchain platform features so you can evaluate Hyperledger Cactus on your own PC. keywords: cactus; hyperledger cache: www-hyperledger-cactus-on-the-road-to-general-blockchain-integration?hs_amp=true.html plain text: www-hyperledger-cactus-on-the-road-to-general-blockchain-integration?hs_amp=true.txt item: #2812 of 3327 id: www-hyperledger-cactus-release-v1-on-the-road-to-general-blockchain-integration author: www title: www-hyperledger-cactus-release-v1-on-the-road-to-general-blockchain-integration date: None words: 1103 flesch: 38 summary: We provide instructions for running a sample implementation of the Business Logic Plugins (service applications in Hyperledger Cactus architecture) that takes advantage of various blockchain platform features so you can evaluate Hyperledger Cactus on your PC. Release V1 on the Road to General Blockchain Integration Hyperledger | Mar 17, 2022 Since its inception as a Hyperledger project almost two years ago, Hyperledger Cactus has come a long way. keywords: blockchain; cactus; decentralized; hyperledger; integration cache: www-hyperledger-cactus-release-v1-on-the-road-to-general-blockchain-integration.html plain text: www-hyperledger-cactus-release-v1-on-the-road-to-general-blockchain-integration.txt item: #2813 of 3327 id: www-hyperledger-cactus-release-v1-on-the-road-to-general-blockchain-integration?hs_amp=true author: www title: www-hyperledger-cactus-release-v1-on-the-road-to-general-blockchain-integration?hs_amp=true date: None words: 794 flesch: 42 summary: We provide instructions for running a sample implementation of the Business Logic Plugins (service applications in Hyperledger Cactus architecture) that takes advantage of various blockchain platform features so you can evaluate Hyperledger Cactus on your PC. Hyperledger Besu Hyperledger Fabric Hyperledger Indy Hyperledger Iroha Hyperledger Sawtooth Corda Go-Ethereum Quorum Xdai Business Logic Plugin samples – the application integrates multiple blockchains: supply-chain-app: management application of supply chains process using Hyperledger Besu, Fabric, and Quorum carbon-accounting: carbon accounting application using Ethereum and Hyperledger Fabric discounted-cartrade: car ownership trading application using Ethereum currency, tokens on Hyperledger Fabric, and digital identity certification using Hyperledger Indy electricity-trade: automatic electricity payment application using Ethereum currency, whose events are triggered by electricity metering transactions on Hyperledger Sawtooth. keywords: blockchain; cactus; hyperledger cache: www-hyperledger-cactus-release-v1-on-the-road-to-general-blockchain-integration?hs_amp=true.html plain text: www-hyperledger-cactus-release-v1-on-the-road-to-general-blockchain-integration?hs_amp=true.txt item: #2814 of 3327 id: www-hyperledger-caliper author: www title: www-hyperledger-caliper date: None words: 604 flesch: 17 summary: Project name: Visual Studio Code support for Hyperledger Caliper artifacts Read More Eravatee Raje | Feb 27, 2023 Hyperledger Caliper | Hyperledger Fabric Benchmarking Hyperledger Fabric 2.5 Performance Hyperledger Fabric performance is a question that comes up frequently as users try to compare it to transactional databases or other blockchain platforms in terms of the maximum... Blog | LF Decentralized Trust | Hyperledger Caliper 2025 keywords: blog; caliper; decentralized; hyperledger cache: www-hyperledger-caliper.html plain text: www-hyperledger-caliper.txt item: #2815 of 3327 id: www-hyperledger-challenge-2022-is-all-set author: www title: www-hyperledger-challenge-2022-is-all-set date: None words: 1204 flesch: 44 summary: As a believer in open collaboration and open source technologies, I am looking forward to working with the innovators of the challenge and seeing all of the innovations that will be developed and commercialised.” – Nancy Min “At Hyperledger Foundation, we build networks of trust for business consortia. Reach out now!” – Arun S M, Hyperledger TSC member “In June 2021, a call to action was delivered within the Hyperledger global community to unearth ways in which we can better collaborate to overcome current and future cross-industry challenges by identifying and contributing heterogeneous expertise, leveraging technology for the betterment of society and unifying open communities under Hyperledger. keywords: challenge; community; hyperledger; open cache: www-hyperledger-challenge-2022-is-all-set.html plain text: www-hyperledger-challenge-2022-is-all-set.txt item: #2816 of 3327 id: www-hyperledger-climate-action-and-accounting-special-interest-group-takes-first-place-in-the-2022-ibm-call-for-code-green-practices-accelerator author: www title: www-hyperledger-climate-action-and-accounting-special-interest-group-takes-first-place-in-the-2022-ibm-call-for-code-green-practices-accelerator date: None words: 902 flesch: 35 summary: The former includes Hyperledger Fabric emission and product data channels to support the verification of high volume data from oil and gas facilities. In the long-term, our team is designing an emission certification platform coordinated by a Decentralized Autonomous Organization (DAO) that will bring together verification professionals, standard setting bodies, data providers, and other industry stakeholders (e.g., regulators, voluntary carbon market providers). keywords: code; decentralized; gas; oil cache: www-hyperledger-climate-action-and-accounting-special-interest-group-takes-first-place-in-the-2022-ibm-call-for-code-green-practices-accelerator.html plain text: www-hyperledger-climate-action-and-accounting-special-interest-group-takes-first-place-in-the-2022-ibm-call-for-code-green-practices-accelerator.txt item: #2817 of 3327 id: www-hyperledger-collaborative-learning-spotlight-binibft-an-optimized-bft-on-fabric author: www title: www-hyperledger-collaborative-learning-spotlight-binibft-an-optimized-bft-on-fabric date: None words: 1495 flesch: 31 summary: Siddhant Prateek Mahanayak navigated the complex landscape of consensus protocols, actively participating in designing innovative consensus mechanisms and contributing to the open-source community. Armed with a deep understanding of consensus protocols, practical skills in implementation, and a collaborative mindset fostered through shared experiences, we are poised to make meaningful contributions to the ever-evolving landscape of distributed ledger technology. keywords: binibft; consensus; fabric; hyperledger; project cache: www-hyperledger-collaborative-learning-spotlight-binibft-an-optimized-bft-on-fabric.html plain text: www-hyperledger-collaborative-learning-spotlight-binibft-an-optimized-bft-on-fabric.txt item: #2818 of 3327 id: www-hyperledger-collaborative-learning-spotlight-binibft-an-optimized-bft-on-fabric?hs_amp=true author: www title: www-hyperledger-collaborative-learning-spotlight-binibft-an-optimized-bft-on-fabric?hs_amp=true date: None words: 1181 flesch: 35 summary: Siddhant Prateek Mahanayak navigated the complex landscape of consensus protocols, actively participating in designing innovative consensus mechanisms and contributing to the open-source community. Armed with a deep understanding of consensus protocols, practical skills in implementation, and a collaborative mindset fostered through shared experiences, we are poised to make meaningful contributions to the ever-evolving landscape of distributed ledger technology. keywords: binibft; consensus; fabric; hyperledger cache: www-hyperledger-collaborative-learning-spotlight-binibft-an-optimized-bft-on-fabric?hs_amp=true.html plain text: www-hyperledger-collaborative-learning-spotlight-binibft-an-optimized-bft-on-fabric?hs_amp=true.txt item: #2819 of 3327 id: www-hyperledger-community author: www title: www-hyperledger-community date: None words: 1382 flesch: 19 summary: Hyperledger Women Share their Blockchain Journeys – Part III In celebration of #HyperledgerWomen, we asked some of the many excellent women leaders in our community to share some details about their blockchain journey, including how they... Read More Hyperledger | Mar 30, 2021 Blog | Hyperledger Community #Hyperledger Women Share their Blockchain Journeys – Part II In celebration of #HyperledgerWomen, we asked some of the many excellent women leaders in our community to share some details about their blockchain journey, including how they... Read More Hyperledger | Mar 29, 2021 Blog | Hyperledger Community #Hyperledger Women Share their Blockchain Journeys In celebration of #HyperledgerWomen, we asked some of the many excellent women leaders in our community to share some details about their blockchain journey, including how they... Read More Hyperledger | Mar 25, 2021 Blog | Hyperledger Community Blockchain Stories 2020: Next page > Submit a blog Blog guidelines RSS Hyperledger Bevel | Hyperledger Community | Labs | Mentorship Program My 5-Year Journey with the Hyperledger Community As a technology enthusiast, I have always been fascinated by the latest developments in this field... keywords: blog; community; hyperledger; stories; women cache: www-hyperledger-community.html plain text: www-hyperledger-community.txt item: #2820 of 3327 id: www-hyperledger-community-chat-is-moving-to-discord author: www title: www-hyperledger-community-chat-is-moving-to-discord date: None words: 596 flesch: 44 summary: Feel free to explore channels Why are we moving to Discord? Hyperledger Foundation set up a Task Force to investigate options for a better chat channel experience for the Hyperledger community. After interviewing and getting feedback from community members, the Task Force determined that Discord as a tool that met the needs of the community. keywords: community; discord; hyperledger cache: www-hyperledger-community-chat-is-moving-to-discord.html plain text: www-hyperledger-community-chat-is-moving-to-discord.txt item: #2821 of 3327 id: www-hyperledger-community-chat-is-moving-to-discord?hs_amp=true author: www title: www-hyperledger-community-chat-is-moving-to-discord?hs_amp=true date: None words: 286 flesch: 58 summary: Hyperledger Community Chat is Moving to Discord – Hyperledger Foundation Blog | LF Decentralized Trust Hyperledger Community Chat is Moving to Discord – Hyperledger Foundation Written by Hyperledger | Feb 16, 2022 9:00:00 AM We are excited to announce that the Hyperledger community will be moving its chat channel to Discord from RocketChat.  Feel free to explore channels Why are we moving to Discord? Hyperledger Foundation set up a Task Force to investigate options for a better chat channel experience for the Hyperledger community. keywords: discord cache: www-hyperledger-community-chat-is-moving-to-discord?hs_amp=true.html plain text: www-hyperledger-community-chat-is-moving-to-discord?hs_amp=true.txt item: #2822 of 3327 id: www-hyperledger-composer author: www title: www-hyperledger-composer date: None words: 1189 flesch: 33 summary: Blog | LF Decentralized Trust | Hyperledger Composer 2025 Next page > Submit a blog Blog guidelines RSS Governance | Hyperledger Composer | Blockchain Pioneers Blockchain Pioneers: Hyperledger Composer As we laid out in our Helping A Community Grow By Pruning Inactive Projects post, there is an... keywords: blog; developer; hyperledger; series; showcase cache: www-hyperledger-composer.html plain text: www-hyperledger-composer.txt item: #2823 of 3327 id: www-hyperledger-explorer author: www title: www-hyperledger-explorer date: None words: 522 flesch: 15 summary: Next page > Submit a blog Blog guidelines RSS Blockchain Pioneers | Hyperledger Explorer Blockchain Pioneers: Hyperledger Explorer As Hyperledger Foundation laid out in the Helping a Community Grow by Pruning Inactive... Blog | LF Decentralized Trust | Hyperledger Explorer 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? keywords: blog; decentralized; hyperledger; technologies cache: www-hyperledger-explorer.html plain text: www-hyperledger-explorer.txt item: #2824 of 3327 id: www-hyperledger-fabric author: www title: www-hyperledger-fabric date: None words: 1402 flesch: 22 summary: Now, with the input... Read More Daniela Barbosa, Executive Director at Hyperledger Foundation and General Manager, Blockchain and Identity for the Linux Foundation | Apr 23, 2024 Mentorship Program | Hyperledger Fabric Hyperledger Collaborative Learning Spotlight: BiniBFT - An Optimized BFT on Fabric WHAT WE WORKED ON: Read More Abhishek Ranjan, Ajitesh Kumar Soni, Ashna P S, Riddhi Ravindra Katarki, Sahilsher Singh, and Siddhant Prateek Mahanayak | Mar 5, 2024 Hyperledger Aries | Developer Showcase | Hyperledger Fabric Developer Showcase Series: Harsh Multani, Blockchain Developer, Siemens Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. Hyperledger AnonCreds | Hyperledger Aries | Project: Hyperledger Indy | Staff Corner | Hyperledger Fabric Just Introduced: Refreshed Hyperledger Project Logos Last year, we introduced a new look for Hyperledger Foundation that fit with our increasingly mature market and ecosystem as well as our enterprise audience. keywords: case; decentralized; fabric; foundation; hyperledger; project cache: www-hyperledger-fabric.html plain text: www-hyperledger-fabric.txt item: #2825 of 3327 id: www-hyperledger-fabric-1-0-release-process author: www title: www-hyperledger-fabric-1-0-release-process date: None words: 966 flesch: 49 summary: This blog post is about the release process for Hyperledger projects reaching the version 1.0 milestone. When Hyperledger Fabric 1.0 was released on July 11th, 2017 several administrative initiatives were under way. keywords: code; hyperledger; security; software cache: www-hyperledger-fabric-1-0-release-process.html plain text: www-hyperledger-fabric-1-0-release-process.txt item: #2826 of 3327 id: www-hyperledger-fabric-at-the-heart-of-a-telecommunication-carrier-ecosystem author: www title: www-hyperledger-fabric-at-the-heart-of-a-telecommunication-carrier-ecosystem date: None words: 1074 flesch: 40 summary: Hyperledger Fabric can be the enabling platform of high value and innovative use cases such as data access control (empowering final users to decide how and who should have access to the data they generate), device identity (integrating blockchain, IoT and security to record device on the network and prevent harmful usage) or data exchange (create marketplaces of accessible data where data supplier are rewarded by data consumer). Their American carriers charged them for every phone call, text or data consumed abroad through the foreign network. keywords: blockchain; data; industry; network cache: www-hyperledger-fabric-at-the-heart-of-a-telecommunication-carrier-ecosystem.html plain text: www-hyperledger-fabric-at-the-heart-of-a-telecommunication-carrier-ecosystem.txt item: #2827 of 3327 id: www-hyperledger-fabric-sawtooth-certification-exams-coming-soon author: www title: www-hyperledger-fabric-sawtooth-certification-exams-coming-soon date: None words: 979 flesch: 34 summary: Below is more information on the certification exams: Certified Hyperledger Fabric Administrator The Certified Hyperledger Fabric Administrator (CHFA) can effectively build a secure Hyperledger Fabric network for commercial deployment. That’s why we’re thrilled to announce that Certified Hyperledger Fabric Administrator and Certified Hyperledger Sawtooth Administrator exams will be released later this year! keywords: exams; fabric; foundation; hyperledger; linux cache: www-hyperledger-fabric-sawtooth-certification-exams-coming-soon.html plain text: www-hyperledger-fabric-sawtooth-certification-exams-coming-soon.txt item: #2828 of 3327 id: www-hyperledger-fabric-security-threats-what-to-look-for author: www title: www-hyperledger-fabric-security-threats-what-to-look-for date: None words: 979 flesch: 34 summary: For more details on how to collect and act on Hyperledger Fabric data to minimize downtime, reduce the meantime to detect and respond to incidents, tune into my webinar on Hyperledger Fabric security monitoring on Wednesday, December 1, 1:00 pm EST. How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog Hyperledger Fabric Security Threats: What to Look For Hyperledger | Nov 18, 2021 Hyperledger Fabric is designed to enable secure collaboration between multiple organizations operating with limited trust. keywords: attacks; fabric; hyperledger; security cache: www-hyperledger-fabric-security-threats-what-to-look-for.html plain text: www-hyperledger-fabric-security-threats-what-to-look-for.txt item: #2829 of 3327 id: www-hyperledger-fabric-v3-delivering-smart-byzantine-fault-tolerant-consensus author: www title: www-hyperledger-fabric-v3-delivering-smart-byzantine-fault-tolerant-consensus date: None words: 2613 flesch: 41 summary: Delivering Smart Byzantine Fault Tolerant consensus Yacov Manevich, Yoav Tock, and Hagar Meir | Sep 16, 2024 Introducing Byzantine Fault Tolerant for Hyperledger Fabric Hyperledger Fabric v3.0 comes with a brand-new ordering service type, which can be deployed in a Byzantine setting, thus giving higher resilience and reliability to Hyperledger Fabric networks. - Mark Rakhmilevich, vice president, Product Management, Mission-Critical Systems, Oracle Hyperledger Fabric 2.x has been instrumental in supporting multi-tenant enterprise Blockchain-as-a-Service platforms. keywords: consensus; fabric; hyperledger; nodes; protocol; service; smartbft cache: www-hyperledger-fabric-v3-delivering-smart-byzantine-fault-tolerant-consensus.html plain text: www-hyperledger-fabric-v3-delivering-smart-byzantine-fault-tolerant-consensus.txt item: #2830 of 3327 id: www-hyperledger-fabric-v3-delivering-smart-byzantine-fault-tolerant-consensus?hs_amp=true author: www title: www-hyperledger-fabric-v3-delivering-smart-byzantine-fault-tolerant-consensus?hs_amp=true date: None words: 2302 flesch: 43 summary: Hyperledger Fabric v3: Delivering Smart Byzantine Fault Tolerant consensus Blog | LF Decentralized Trust Hyperledger Fabric v3: Delivering Smart Byzantine Fault Tolerant consensus Written by Yacov Manevich, Yoav Tock, and Hagar Meir | Sep 16, 2024 7:00:37 AM Introducing Byzantine Fault Tolerant for Hyperledger Fabric Hyperledger Fabric v3.0 comes with a brand-new ordering service type, which can be deployed in a Byzantine setting, thus giving higher resilience and reliability to Hyperledger Fabric networks. - Mark Rakhmilevich, vice president, Product Management, Mission-Critical Systems, Oracle Hyperledger Fabric 2.x has been instrumental in supporting multi-tenant enterprise Blockchain-as-a-Service platforms. keywords: fabric; hyperledger; nodes; service; smartbft cache: www-hyperledger-fabric-v3-delivering-smart-byzantine-fault-tolerant-consensus?hs_amp=true.html plain text: www-hyperledger-fabric-v3-delivering-smart-byzantine-fault-tolerant-consensus?hs_amp=true.txt item: #2831 of 3327 id: www-hyperledger-firefly author: www title: www-hyperledger-firefly date: None words: 678 flesch: 23 summary: Enhancements... Read More Enrique Lacal, Hyperledger FireFly Maintainer and Community Lead and Full Stack Software Engineer at Kaleido | May 20, 2024 Governance | Hyperledger FireFly Hyperledger Firefly Achieves Graduated Status; Is in Production Around the World The Hyperledger Technical Oversight Committee (TOC) has approved Hyperledger FireFly as the latest of Hyperledger Foundation’s projects to achieve graduated status. | Oct 3, 2023 Hyperledger FireFly Introducing Hyperledger FireFly 1.0: The SuperNode for Enterprise Web3 Applications It’s been a busy 10 months for Hyperledger FireFly. keywords: blog; decentralized; firefly; hyperledger cache: www-hyperledger-firefly.html plain text: www-hyperledger-firefly.txt item: #2832 of 3327 id: www-hyperledger-firefly-achieves-graduated-status-is-in-production-around-the-world author: www title: www-hyperledger-firefly-achieves-graduated-status-is-in-production-around-the-world date: None words: 1179 flesch: 28 summary: You’ll also see a hands-on demo of how to get started with Hyperledger FireFly from Nicko Guyer, Hyperledger FireFly Maintainer. How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Governance | Hyperledger FireFly Hyperledger Firefly Achieves Graduated Status; Is in Production Around the World Nicko Guyer, Hyperledger FireFly Maintainer | Oct 3, 2023 The Hyperledger Technical Oversight Committee (TOC) has approved Hyperledger FireFly as the latest of Hyperledger Foundation’s projects to achieve graduated status. keywords: blockchain; community; firefly; hyperledger; project cache: www-hyperledger-firefly-achieves-graduated-status-is-in-production-around-the-world.html plain text: www-hyperledger-firefly-achieves-graduated-status-is-in-production-around-the-world.txt item: #2833 of 3327 id: www-hyperledger-firefly-achieves-graduated-status-is-in-production-around-the-world?hs_amp=true author: www title: www-hyperledger-firefly-achieves-graduated-status-is-in-production-around-the-world?hs_amp=true date: None words: 860 flesch: 30 summary: You’ll also see a hands-on demo of how to get started with Hyperledger FireFly from Nicko Guyer, Hyperledger FireFly Maintainer. Hyperledger Firefly Achieves Graduated Status Blog | LF Decentralized Trust Hyperledger Firefly Achieves Graduated Status Written by Nicko Guyer, Hyperledger FireFly Maintainer | Oct 3, 2023 10:02:27 PM The Hyperledger Technical Oversight Committee (TOC) has approved Hyperledger FireFly as the latest of Hyperledger Foundation’s projects to achieve graduated status. keywords: blockchain; firefly; hyperledger cache: www-hyperledger-firefly-achieves-graduated-status-is-in-production-around-the-world?hs_amp=true.html plain text: www-hyperledger-firefly-achieves-graduated-status-is-in-production-around-the-world?hs_amp=true.txt item: #2834 of 3327 id: www-hyperledger-firefly-v1-2-is-now-available author: www title: www-hyperledger-firefly-v1-2-is-now-available date: None words: 732 flesch: 40 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog Hyperledger FireFly V1.2 Is Now Available Hyperledger | Feb 13, 2023 Since the launch of Hyperledger FireFly 1.1 in October, the community has been hard at work on a number of improvements, and today we’re pleased to announce that version 1.2 is now available. You can learn more in the Hyperledger FireFly docs and download the CLI on the Hyperledger FireFly Github. keywords: decentralized; firefly; foundation; hyperledger cache: www-hyperledger-firefly-v1-2-is-now-available.html plain text: www-hyperledger-firefly-v1-2-is-now-available.txt item: #2835 of 3327 id: www-hyperledger-firefly-v1-2-is-now-available?hs_amp=true author: www title: www-hyperledger-firefly-v1-2-is-now-available?hs_amp=true date: None words: 424 flesch: 49 summary: Hyperledger FireFly V1.2 Is Now Available – Hyperledger Foundation Blog | LF Decentralized Trust Hyperledger FireFly V1.2 Is Now Available – Hyperledger Foundation Written by Hyperledger | Feb 13, 2023 7:00:00 AM Since the launch of Hyperledger FireFly 1.1 in October, the community has been hard at work on a number of improvements, and today we’re pleased to announce that version 1.2 is now available. Distributed Request Tracking: The X-FireFly-Request-ID HTTP header is now passed through to FireFly dependency microservices to allow for distributed request tracking through various systems. keywords: firefly; hyperledger cache: www-hyperledger-firefly-v1-2-is-now-available?hs_amp=true.html plain text: www-hyperledger-firefly-v1-2-is-now-available?hs_amp=true.txt item: #2836 of 3327 id: www-hyperledger-firefly-v1.3-is-now-available author: www title: www-hyperledger-firefly-v1.3-is-now-available date: None words: 1123 flesch: 44 summary: The new Tezos connector was contributed to Hyperledger FireFly by Dzianis Andreyenka, Software Engineer at Instinctools Company and FireFly maintainer. Invoke with data The core mission of Hyperledger FireFly is to allow you to connect to any blockchain, to invoke any smart contract and stream any events. keywords: blockchain; decentralized; firefly; hyperledger; release cache: www-hyperledger-firefly-v1.3-is-now-available.html plain text: www-hyperledger-firefly-v1.3-is-now-available.txt item: #2837 of 3327 id: www-hyperledger-firefly-v1.3-is-now-available?hs_amp=true author: www title: www-hyperledger-firefly-v1.3-is-now-available?hs_amp=true date: None words: 812 flesch: 52 summary: The new Tezos connector was contributed to Hyperledger FireFly by Dzianis Andreyenka, Software Engineer at Instinctools Company and FireFly maintainer. Invoke with data The core mission of Hyperledger FireFly is to allow you to connect to any blockchain, to invoke any smart contract and stream any events. keywords: firefly; hyperledger; release cache: www-hyperledger-firefly-v1.3-is-now-available?hs_amp=true.html plain text: www-hyperledger-firefly-v1.3-is-now-available?hs_amp=true.txt item: #2838 of 3327 id: www-hyperledger-for-healthcare-how-fabric-drives-the-next-generation-pharma-supply-chain author: www title: www-hyperledger-for-healthcare-how-fabric-drives-the-next-generation-pharma-supply-chain date: None words: 1506 flesch: 50 summary: About the Author Ben Taylor is the CEO of LedgerDomain, founded in 2016 to bring Hyperledger blockchain solutions to enterprise ecosystems, unlocking a world of communal computing and real-time performance. This is a “rubber hits the road” moment for supply blockchain: out of the workshop and into the real world. keywords: blockchain; fabric; foundation; hyperledger; studies; supply cache: www-hyperledger-for-healthcare-how-fabric-drives-the-next-generation-pharma-supply-chain.html plain text: www-hyperledger-for-healthcare-how-fabric-drives-the-next-generation-pharma-supply-chain.txt item: #2839 of 3327 id: www-hyperledger-foundation author: www title: www-hyperledger-foundation date: None words: 1464 flesch: 32 summary: Blog | LF Decentralized Trust | Hyperledger Foundation 2025 For Hyperledger Foundation, technical governance is the job of the Technical Oversight... keywords: developer; foundation; hyperledger; series; showcase cache: www-hyperledger-foundation.html plain text: www-hyperledger-foundation.txt item: #2840 of 3327 id: www-hyperledger-foundation-charter-updates-looking-to-2023-and-beyond author: www title: www-hyperledger-foundation-charter-updates-looking-to-2023-and-beyond date: None words: 912 flesch: 38 summary: We look forward to working with our active and growing community to meet the needs of the developers and the companies and governments that rely on Hyperledger projects. These new updates were made as a follow-up to our change from a project to a foundation with an umbrella of projects to create the opportunity for more autonomy for technical projects and enable further growth for the community and the ecosystem.  keywords: foundation; hyperledger; project cache: www-hyperledger-foundation-charter-updates-looking-to-2023-and-beyond.html plain text: www-hyperledger-foundation-charter-updates-looking-to-2023-and-beyond.txt item: #2841 of 3327 id: www-hyperledger-foundation-charter-updates-looking-to-2023-and-beyond?hs_amp=true author: www title: www-hyperledger-foundation-charter-updates-looking-to-2023-and-beyond?hs_amp=true date: None words: 602 flesch: 47 summary: These new updates were made as a follow-up to our change from a project to a foundation with an umbrella of projects to create the opportunity for more autonomy for technical projects and enable further growth for the community and the ecosystem.  The key changes fall into two related categories: New Governance options for technical projects New and existing Hyperledger projects may now opt to have their own technical governance charter. keywords: hyperledger cache: www-hyperledger-foundation-charter-updates-looking-to-2023-and-beyond?hs_amp=true.html plain text: www-hyperledger-foundation-charter-updates-looking-to-2023-and-beyond?hs_amp=true.txt item: #2842 of 3327 id: www-hyperledger-foundation-community-training-accelerate-your-decentralized-identity-skills-with-two-free-hyperledger-indy-and-hyperledger-aries-workshops author: www title: www-hyperledger-foundation-community-training-accelerate-your-decentralized-identity-skills-with-two-free-hyperledger-indy-and-hyperledger-aries-workshops date: None words: 1007 flesch: 29 summary: These new courses are the first community workshops offered by the Hyperledger Foundation for free in an effort to expand the use, contributions, and maintainer community of Hyperledger Indy and Aries. Topics also include: Decentralized identity concepts and principles The verifiable credential data model Decentralized identity ecosystem Introduction to network tools indyscan and SelfServe Intro to Indy CLI and how to use the CLI to access a network What Aries is Install and run Aries Toolbox Create connections and issue a credential How to verify credential Hyperledger Indy Technical Deep Dive February 3, 2022 8:00 AM to noon Pacific Register for free The second in the series is a four-hour course that advances your skills related to Hyperledger Indy node code and the Indy SDK. keywords: aries; decentralized; hyperledger; indy cache: www-hyperledger-foundation-community-training-accelerate-your-decentralized-identity-skills-with-two-free-hyperledger-indy-and-hyperledger-aries-workshops.html plain text: www-hyperledger-foundation-community-training-accelerate-your-decentralized-identity-skills-with-two-free-hyperledger-indy-and-hyperledger-aries-workshops.txt item: #2843 of 3327 id: www-hyperledger-foundation-community-training-accelerate-your-decentralized-identity-skills-with-two-free-hyperledger-indy-and-hyperledger-aries-workshops?hs_amp=true author: www title: www-hyperledger-foundation-community-training-accelerate-your-decentralized-identity-skills-with-two-free-hyperledger-indy-and-hyperledger-aries-workshops?hs_amp=true date: None words: 695 flesch: 33 summary: Topics also include: Decentralized identity concepts and principles The verifiable credential data model Decentralized identity ecosystem Introduction to network tools indyscan and SelfServe Intro to Indy CLI and how to use the CLI to access a network What Aries is Install and run Aries Toolbox Create connections and issue a credential How to verify credential Hyperledger Indy Technical Deep Dive February 3, 2022 8:00 AM to noon Pacific Register for free The second in the series is a four-hour course that advances your skills related to Hyperledger Indy node code and the Indy SDK. These new courses are the first community workshops offered by the Hyperledger Foundation for free in an effort to expand the use, contributions, and maintainer community of Hyperledger Indy and Aries. keywords: hyperledger; indy cache: www-hyperledger-foundation-community-training-accelerate-your-decentralized-identity-skills-with-two-free-hyperledger-indy-and-hyperledger-aries-workshops?hs_amp=true.html plain text: www-hyperledger-foundation-community-training-accelerate-your-decentralized-identity-skills-with-two-free-hyperledger-indy-and-hyperledger-aries-workshops?hs_amp=true.txt item: #2844 of 3327 id: www-hyperledger-global-forum-highlights-cbdcs-programmable-money-and-interoperability-part-i author: www title: www-hyperledger-global-forum-highlights-cbdcs-programmable-money-and-interoperability-part-i date: None words: 1466 flesch: 36 summary: While the National Bank Cambodia selected Hyperledger Iroha for its retail CBDC implementation, multiple implementations are using other Hyperledger projects, primarily Hyperledger Besu and Hyperledger Fabric. Deep dive into Hyperledger projects with training and certifications. keywords: bank; cbdc; central; hyperledger; money cache: www-hyperledger-global-forum-highlights-cbdcs-programmable-money-and-interoperability-part-i.html plain text: www-hyperledger-global-forum-highlights-cbdcs-programmable-money-and-interoperability-part-i.txt item: #2845 of 3327 id: www-hyperledger-global-forum-highlights-cbdcs-programmable-money-and-interoperability-part-i?hs_amp=true author: www title: www-hyperledger-global-forum-highlights-cbdcs-programmable-money-and-interoperability-part-i?hs_amp=true date: None words: 1156 flesch: 40 summary: While the National Bank Cambodia selected Hyperledger Iroha for its retail CBDC implementation, multiple implementations are using other Hyperledger projects, primarily Hyperledger Besu and Hyperledger Fabric. Deep dive into Hyperledger projects with training and certifications. keywords: bank; cbdc; central; hyperledger cache: www-hyperledger-global-forum-highlights-cbdcs-programmable-money-and-interoperability-part-i?hs_amp=true.html plain text: www-hyperledger-global-forum-highlights-cbdcs-programmable-money-and-interoperability-part-i?hs_amp=true.txt item: #2846 of 3327 id: www-hyperledger-global-forum-highlights-cbdcs-programmable-money-and-interoperability-part-ii author: www title: www-hyperledger-global-forum-highlights-cbdcs-programmable-money-and-interoperability-part-ii date: None words: 1092 flesch: 28 summary: Deep dive into Hyperledger projects with training and certifications. At this year’s Hyperledger Global Forum (HGF), those on the front lines of CBDC deployments and the development of critical underlying platforms and technologies presented a mix of talks about requirements for and challenges of implementing current and future payment solutions. keywords: cbdc; decentralized; global; hyperledger; interoperability cache: www-hyperledger-global-forum-highlights-cbdcs-programmable-money-and-interoperability-part-ii.html plain text: www-hyperledger-global-forum-highlights-cbdcs-programmable-money-and-interoperability-part-ii.txt item: #2847 of 3327 id: www-hyperledger-global-forum-highlights-cbdcs-programmable-money-and-interoperability-part-ii?hs_amp=true author: www title: www-hyperledger-global-forum-highlights-cbdcs-programmable-money-and-interoperability-part-ii?hs_amp=true date: None words: 782 flesch: 30 summary: At this year’s Hyperledger Global Forum (HGF), those on the front lines of CBDC deployments and the development of critical underlying platforms and technologies presented a mix of talks about requirements for and challenges of implementing current and future payment solutions. It has also incentivized PSPs to develop more bank-like services, a wider range of services, and has incentivized banks to develop a wider range of PSP-like services so it is enriching competition within the Cambodian payments ecosystem…” Other sessions of interest from Hyperledger Global Forum on the subject: Panel: Hyperledger Contributions from IBM – Kelly Ryan, Rakesh Mohan, Chris Ferris, Arnaud Le Hors & Elli Androulaki, IBM (Sponsored by IBM) keywords: cbdc; global; hyperledger cache: www-hyperledger-global-forum-highlights-cbdcs-programmable-money-and-interoperability-part-ii?hs_amp=true.html plain text: www-hyperledger-global-forum-highlights-cbdcs-programmable-money-and-interoperability-part-ii?hs_amp=true.txt item: #2848 of 3327 id: www-hyperledger-grid author: www title: www-hyperledger-grid date: None words: 534 flesch: 18 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Blog | LF Decentralized Trust | Hyperledger Grid 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? keywords: blog; decentralized; hyperledger; technologies cache: www-hyperledger-grid.html plain text: www-hyperledger-grid.txt item: #2849 of 3327 id: www-hyperledger-hyderabad-meetup-hosts-daml-experts author: www title: www-hyperledger-hyderabad-meetup-hosts-daml-experts date: None words: 1023 flesch: 45 summary: With a mapping between this abstraction layer and the specifics of a given platform, as BTP is developing for Hyperledger Sawtooth, DAML applications can be ported from platform to platform without complex rewrites. Thank you Hyperledger Hyderabad for giving a first-hand experience of DAML.” keywords: daml; decentralized; hyperledger; language; platform cache: www-hyperledger-hyderabad-meetup-hosts-daml-experts.html plain text: www-hyperledger-hyderabad-meetup-hosts-daml-experts.txt item: #2850 of 3327 id: www-hyperledger-identity-community-completes-development-of-didindy-method-and-advances-toward-a-network-of-networks author: www title: www-hyperledger-identity-community-completes-development-of-didindy-method-and-advances-toward-a-network-of-networks date: None words: 907 flesch: 29 summary: The goals were to align the content that can be written in the DIDDocs published on Hyperledger Indy networks with the current World Wide Web Consortium (W3C) Decentralized Identifier (DID) Specification and to add a namespace element to DIDs (and other object identifiers) published on Hyperledger Indy networks, so users know on which of the many Hyperledger Indy networks the DID was created. While issuers still need to be anchored in the specific Indy ledger of their choice, holders can seamlessly receive verifiable credentials from issuers rooted in different Hyperledger Indy networks, and be able to create verifiable presentations from any combination of those credentials. keywords: decentralized; hyperledger; indy; networks cache: www-hyperledger-identity-community-completes-development-of-didindy-method-and-advances-toward-a-network-of-networks.html plain text: www-hyperledger-identity-community-completes-development-of-didindy-method-and-advances-toward-a-network-of-networks.txt item: #2851 of 3327 id: www-hyperledger-identity-community-completes-development-of-didindy-method-and-advances-toward-a-network-of-networks?hs_amp=true author: www title: www-hyperledger-identity-community-completes-development-of-didindy-method-and-advances-toward-a-network-of-networks?hs_amp=true date: None words: 595 flesch: 33 summary: The goals were to align the content that can be written in the DIDDocs published on Hyperledger Indy networks with the current World Wide Web Consortium (W3C) Decentralized Identifier (DID) Specification and to add a namespace element to DIDs (and other object identifiers) published on Hyperledger Indy networks, so users know on which of the many Hyperledger Indy networks the DID was created. While issuers still need to be anchored in the specific Indy ledger of their choice, holders can seamlessly receive verifiable credentials from issuers rooted in different Hyperledger Indy networks, and be able to create verifiable presentations from any combination of those credentials. keywords: hyperledger; indy cache: www-hyperledger-identity-community-completes-development-of-didindy-method-and-advances-toward-a-network-of-networks?hs_amp=true.html plain text: www-hyperledger-identity-community-completes-development-of-didindy-method-and-advances-toward-a-network-of-networks?hs_amp=true.txt item: #2852 of 3327 id: www-hyperledger-identus author: www title: www-hyperledger-identus date: None words: 526 flesch: 12 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Blog | LF Decentralized Trust | Hyperledger Identus 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us BLOG The latest community news, insights and developments Stay connected with the latest in open source decentralized technologies, member updates, and community-driven projects. keywords: blog; decentralized; hyperledger; technologies cache: www-hyperledger-identus.html plain text: www-hyperledger-identus.txt item: #2853 of 3327 id: www-hyperledger-in-action-a-sampling-of-digital-identity-solutions-built-with-hyperledger-technologies author: www title: www-hyperledger-in-action-a-sampling-of-digital-identity-solutions-built-with-hyperledger-technologies date: None words: 1007 flesch: 33 summary: Instnt Access Instnt Access, part of an AI-managed customer acceptance platform from Instnt, leverages Hyperledger Aries, Hyperledger Indy and web3 decentralized identity standards to help businesses eliminate customer onboarding friction. SITA’s Digital Travel Credential (DTC) SITA, the travel sector technology provider, and development partner Indicio have created a Digital Travel Credential (DTC) built using Hyperledger Aries and Hyperledger Indy. keywords: digital; hyperledger; identity; technologies cache: www-hyperledger-in-action-a-sampling-of-digital-identity-solutions-built-with-hyperledger-technologies.html plain text: www-hyperledger-in-action-a-sampling-of-digital-identity-solutions-built-with-hyperledger-technologies.txt item: #2854 of 3327 id: www-hyperledger-in-action-a-sampling-of-digital-identity-solutions-built-with-hyperledger-technologies?hs_amp=true author: www title: www-hyperledger-in-action-a-sampling-of-digital-identity-solutions-built-with-hyperledger-technologies?hs_amp=true date: None words: 686 flesch: 36 summary: Instnt Access Instnt Access, part of an AI-managed customer acceptance platform from Instnt, leverages Hyperledger Aries, Hyperledger Indy and web3 decentralized identity standards to help businesses eliminate customer onboarding friction. SITA’s Digital Travel Credential (DTC) SITA, the travel sector technology provider, and development partner Indicio have created a Digital Travel Credential (DTC) built using Hyperledger Aries and Hyperledger Indy. keywords: digital; hyperledger; identity cache: www-hyperledger-in-action-a-sampling-of-digital-identity-solutions-built-with-hyperledger-technologies?hs_amp=true.html plain text: www-hyperledger-in-action-a-sampling-of-digital-identity-solutions-built-with-hyperledger-technologies?hs_amp=true.txt item: #2855 of 3327 id: www-hyperledger-in-action-across-asia author: www title: www-hyperledger-in-action-across-asia date: None words: 1479 flesch: 33 summary: Mindtree’s Digital Health Passport for Travel solution, which is built using Hyperledger Fabric blockchain technology, promises to do exactly this and thereby make post-pandemic global airline travel seamless, hassle-free, and safe.  How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog Hyperledger in Action Across Asia Hyperledger | Nov 30, 2021 It’s #HyperledgerAsia month, so we are spotlighting the fast-growing adoption and deployment of Hyperledger technologies throughout the region. keywords: blockchain; data; exchange; hyperledger; platform; solution; technologies cache: www-hyperledger-in-action-across-asia.html plain text: www-hyperledger-in-action-across-asia.txt item: #2856 of 3327 id: www-hyperledger-india-chapter-in-2020 author: www title: www-hyperledger-india-chapter-in-2020 date: None words: 1638 flesch: 55 summary: Hyperledger India Chapter in 2020 – Hyperledger Foundation 2025 Update: Off to a Fast Start!  Hyperledger India Chapter carried the strong bond it built across Asia Pacific region, and it shows up in the continued engagement we have with the enthusiasts outside Indian territory. keywords: blockchain; chapter; community; hyperledger; india cache: www-hyperledger-india-chapter-in-2020.html plain text: www-hyperledger-india-chapter-in-2020.txt item: #2857 of 3327 id: www-hyperledger-indy author: www title: www-hyperledger-indy date: None words: 1007 flesch: 22 summary: Next page > Submit a blog Blog guidelines RSS Decentralized Identity | Besu | Hyperledger Indy LF Decentralized Trust’s Hyperledger Indy on Besu Joins the Did:indy Method: Six Months of Progress Six months ago, Hyperledger Indy on Besu officially joined the did:indy method with the... Read More Renata Toktar, Hyperledger Indy maintainer and contributor, and lead software engineer at DSR Corporation | Git signing with DIDs Hyperledger Indy This year, I had the opportunity to contribute to the open source Hyperledger Indy community as part of the 2019 Hyperledger Summer Mentorship program. keywords: aries; decentralized; hyperledger; identity; indy cache: www-hyperledger-indy.html plain text: www-hyperledger-indy.txt item: #2858 of 3327 id: www-hyperledger-indy-graduates-to-active-status-joins-fabric-and-sawtooth-as-production-ready-hyperledger-projects author: www title: www-hyperledger-indy-graduates-to-active-status-joins-fabric-and-sawtooth-as-production-ready-hyperledger-projects date: None words: 813 flesch: 36 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger Indy Hyperledger Indy Graduates To Active Status; Joins Fabric And Sawtooth As “Production Ready” Hyperledger Projects Hyperledger | Apr 10, 2019 By Steven Gubler, Hyperledger Indy contributor and Sovrin infrastructure and pipeline engineer The Hyperledger Technical Steering Committee (TSC) just approved Indy to be the third of Hyperledger’s twelve projects to graduate from incubation to active status. Hyperledger Indy is a distributed ledger purpose-built for decentralized identity. keywords: hyperledger; identity; indy cache: www-hyperledger-indy-graduates-to-active-status-joins-fabric-and-sawtooth-as-production-ready-hyperledger-projects.html plain text: www-hyperledger-indy-graduates-to-active-status-joins-fabric-and-sawtooth-as-production-ready-hyperledger-projects.txt item: #2859 of 3327 id: www-hyperledger-indy-graduates-to-active-status-joins-fabric-and-sawtooth-as-production-ready-hyperledger-projects?hs_amp=true author: www title: www-hyperledger-indy-graduates-to-active-status-joins-fabric-and-sawtooth-as-production-ready-hyperledger-projects?hs_amp=true date: None words: 504 flesch: 42 summary: Hyperledger Indy Graduates To Active Status; Joins Fabric And Sawtooth As “Production Ready” Hyperledger Projects – Hyperledger Foundation Blog | LF Decentralized Trust Hyperledger Indy Graduates To Active Status; Joins Fabric And Sawtooth As “Production Ready” Hyperledger Projects – Hyperledger Foundation Written by Hyperledger | Apr 10, 2019 8:50:54 AM By Steven Gubler, Hyperledger Indy contributor and Sovrin infrastructure and pipeline engineer The Hyperledger Technical Steering Committee (TSC) just approved Indy to be the third of Hyperledger’s twelve projects to graduate from incubation to active status. To this end, the private company Evernym and the non profit Sovrin Foundation teamed up with Hyperledger to contribute the source code that became Hyperledger Indy. keywords: hyperledger; indy cache: www-hyperledger-indy-graduates-to-active-status-joins-fabric-and-sawtooth-as-production-ready-hyperledger-projects?hs_amp=true.html plain text: www-hyperledger-indy-graduates-to-active-status-joins-fabric-and-sawtooth-as-production-ready-hyperledger-projects?hs_amp=true.txt item: #2860 of 3327 id: www-hyperledger-iroha author: www title: www-hyperledger-iroha date: None words: 1043 flesch: 31 summary: This year, I had the amazing opportunity to contribute to the open source Hyperledger community as part of the 2019 Hyperledger Mentorship program. Blog | LF Decentralized Trust | Hyperledger Iroha 2025 keywords: decentralized; hyperledger; iroha; mentorship; project cache: www-hyperledger-iroha.html plain text: www-hyperledger-iroha.txt item: #2861 of 3327 id: www-hyperledger-iroha-maintainers author: www title: www-hyperledger-iroha-maintainers date: None words: 517 flesch: 21 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Announcing Hyperledger Iroha 2 Hyperledger Iroha 2 is an innovative blockchain framework aimed to be robust, fast, and efficient... keywords: blog; decentralized; hyperledger; technologies cache: www-hyperledger-iroha-maintainers.html plain text: www-hyperledger-iroha-maintainers.txt item: #2862 of 3327 id: www-hyperledger-iroha-security-audit-results author: www title: www-hyperledger-iroha-security-audit-results date: None words: 1622 flesch: 48 summary: Figure 4—Flawed endorsement check that includes digital signature bytes. Figure 5—Random nonces produce different signatures from the same inputs. keywords: figure; key; node; signature cache: www-hyperledger-iroha-security-audit-results.html plain text: www-hyperledger-iroha-security-audit-results.txt item: #2863 of 3327 id: www-hyperledger-iroha-security-audit-results?hs_amp=true author: www title: www-hyperledger-iroha-security-audit-results?hs_amp=true date: None words: 1313 flesch: 53 summary: Figure 4—Flawed endorsement check that includes digital signature bytes. Figure 5—Random nonces produce different signatures from the same inputs. keywords: figure; node; signature cache: www-hyperledger-iroha-security-audit-results?hs_amp=true.html plain text: www-hyperledger-iroha-security-audit-results?hs_amp=true.txt item: #2864 of 3327 id: www-hyperledger-italian-chapter-launches-to-bolster-local-community-and-development author: www title: www-hyperledger-italian-chapter-launches-to-bolster-local-community-and-development date: None words: 1009 flesch: 25 summary: Italian industrial sector that is worldwide famous for “Made in Italy” style carries an important market value that can strongly benefit from the features of transparency, security and traceability offered by blockchain. The chapter’s initial activities will include diving into some new features released like Hyperledger Cactus, a new tool by Accenture allowing interoperability between DLT networks and now within Hyperledger Greenhouse, and other amazing updates by Linux Foundation and Hyperledger members like IBM, Chainstack and Digital Asset. keywords: chapter; development; foundation; hyperledger cache: www-hyperledger-italian-chapter-launches-to-bolster-local-community-and-development.html plain text: www-hyperledger-italian-chapter-launches-to-bolster-local-community-and-development.txt item: #2865 of 3327 id: www-hyperledger-lab-perun-achievements-of-2021-and-outlook-for-2022 author: www title: www-hyperledger-lab-perun-achievements-of-2021-and-outlook-for-2022 date: None words: 1016 flesch: 48 summary: This Hyperledger Lab  aims at establishing an open-source project based on Perun channel protocols, which is a technology for scalability and interoperability of blockchains. Hyperledger Lab Perun: Achievements of 2021 and Outlook for 2022 – Hyperledger Foundation 2025 keywords: backend; channels; hyperledger; perun cache: www-hyperledger-lab-perun-achievements-of-2021-and-outlook-for-2022.html plain text: www-hyperledger-lab-perun-achievements-of-2021-and-outlook-for-2022.txt item: #2866 of 3327 id: www-hyperledger-lab-perun-adds-payment-channel-for-cosmos-network author: www title: www-hyperledger-lab-perun-adds-payment-channel-for-cosmos-network date: None words: 661 flesch: 42 summary: Hyperledger Lab Perun Adds Payment Channel for Cosmos Network – Hyperledger Foundation 2025 Blockchain-agnostic applications can be written and run within Perun channels. keywords: cosmos; hyperledger; perun cache: www-hyperledger-lab-perun-adds-payment-channel-for-cosmos-network.html plain text: www-hyperledger-lab-perun-adds-payment-channel-for-cosmos-network.txt item: #2867 of 3327 id: www-hyperledger-lab-perun-adds-payment-channel-for-cosmos-network?hs_amp=true author: www title: www-hyperledger-lab-perun-adds-payment-channel-for-cosmos-network?hs_amp=true date: None words: 353 flesch: 55 summary: Hyperledger Lab Perun Adds Payment Channel for Cosmos Network – Hyperledger Foundation Blog | LF Decentralized Trust Hyperledger Lab Perun Adds Payment Channel for Cosmos Network – Hyperledger Foundation Written by Hyperledger | Mar 24, 2022 9:30:00 AM We are excited to announce that Perun, a Hyperledger Lab, has published the first version of the Perun-CosmWasm blockchain backend. keywords: perun cache: www-hyperledger-lab-perun-adds-payment-channel-for-cosmos-network?hs_amp=true.html plain text: www-hyperledger-lab-perun-adds-payment-channel-for-cosmos-network?hs_amp=true.txt item: #2868 of 3327 id: www-hyperledger-mentorship-spotlight-aries-vcx-based-message-mediator author: www title: www-hyperledger-mentorship-spotlight-aries-vcx-based-message-mediator date: None words: 1680 flesch: 40 summary: Blog posts on Aries concepts, Rust dev, aries-vcx environment setup Analysis of Mediator Coordination protocol implementation choices Miscellaneous notes and scribbles Media deliverable: Presentation at Aries Working Group call Please refer to the objective deliverables page for details about the artifacts produced.  For instance, when it comes to the Rust domain, I: Learned how to set up projects and run tests with cargo Learned how to bootstrap a web server in Rust using axum Learned about databases and interfacing with them in Rust using sqlx Learned about Aries protocols and how to integrate their capabilities using aries-vcx And familiarized with many other important concepts and tricks along the way At every step, I focused on learning one key component that did one thing, and figured out how it could be combined with the previous skills I had acquired. keywords: aries; decentralized; mediator; mentorship; rust; vcx cache: www-hyperledger-mentorship-spotlight-aries-vcx-based-message-mediator.html plain text: www-hyperledger-mentorship-spotlight-aries-vcx-based-message-mediator.txt item: #2869 of 3327 id: www-hyperledger-mentorship-spotlight-aries-vcx-based-message-mediator?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-aries-vcx-based-message-mediator?hs_amp=true date: None words: 1366 flesch: 43 summary: For instance, when it comes to the Rust domain, I: Learned how to set up projects and run tests with cargo Learned how to bootstrap a web server in Rust using axum Learned about databases and interfacing with them in Rust using sqlx Learned about Aries protocols and how to integrate their capabilities using aries-vcx And familiarized with many other important concepts and tricks along the way At every step, I focused on learning one key component that did one thing, and figured out how it could be combined with the previous skills I had acquired. WHAT I WORKED ON: Project Name: Aries-vcx based message mediator Objectives: Implement message mediator service written in Rust Robust integration on top of aries-vcx crates Support newer pick-up v2 protocol Automatize the CI/CD process Mentors: Mentor Discord Patrik Stas Patrik Stas#7722 Bogdan Mircea bobozaur#5997 Miroslav Kovar mirgee#3763 George Mulhearn gmulhearn#0356   Details: Digital agents within the SSI ecosystem may not always be able to communicate directly with one another, such as in cases of intermittent connectivity (as with mobile wallets) or for other practical reasons. keywords: aries; mediator; rust; vcx cache: www-hyperledger-mentorship-spotlight-aries-vcx-based-message-mediator?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-aries-vcx-based-message-mediator?hs_amp=true.txt item: #2870 of 3327 id: www-hyperledger-mentorship-spotlight-blockchain-integration-for-climate-emissions-data-with-fabric-and-cactus author: www title: www-hyperledger-mentorship-spotlight-blockchain-integration-for-climate-emissions-data-with-fabric-and-cactus date: None words: 1007 flesch: 28 summary: Mentorship Project Title Blockchain Integration for Climate Emissions Data with Fabric and Cactus Description To implement an integration from Hyperledger Fabric utility emissions data channel to issue tokens on an Ethereum network using Hyperledger Cactus. In order to make the application production ready, I used the Hyperledger Cactus connectors for integrating multiple blockchain. keywords: hyperledger; integration; mentorship; project cache: www-hyperledger-mentorship-spotlight-blockchain-integration-for-climate-emissions-data-with-fabric-and-cactus.html plain text: www-hyperledger-mentorship-spotlight-blockchain-integration-for-climate-emissions-data-with-fabric-and-cactus.txt item: #2871 of 3327 id: www-hyperledger-mentorship-spotlight-blockchain-integration-for-climate-emissions-data-with-fabric-and-cactus?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-blockchain-integration-for-climate-emissions-data-with-fabric-and-cactus?hs_amp=true date: None words: 696 flesch: 28 summary: Mentorship Project Title Blockchain Integration for Climate Emissions Data with Fabric and Cactus Description To implement an integration from Hyperledger Fabric utility emissions data channel to issue tokens on an Ethereum network using Hyperledger Cactus. In order to make the application production ready, I used the Hyperledger Cactus connectors for integrating multiple blockchain. keywords: hyperledger; mentorship; project cache: www-hyperledger-mentorship-spotlight-blockchain-integration-for-climate-emissions-data-with-fabric-and-cactus?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-blockchain-integration-for-climate-emissions-data-with-fabric-and-cactus?hs_amp=true.txt item: #2872 of 3327 id: www-hyperledger-mentorship-spotlight-blockchain-network-operation-in-a-decentralized-way author: www title: www-hyperledger-mentorship-spotlight-blockchain-network-operation-in-a-decentralized-way date: None words: 733 flesch: 38 summary: In addition to the technical skills I gained during my work on Hyperledger Cello, I also had the chance to learn more about the broader context of blockchain technology and its potential to solve real-world problems. Project name: Blockchain Network Operation in a Decentralized Way My Hyperledger Foundation mentorship project, which focused on Hyperledger Cello, gave me the opportunity to work on the development of an operational dashboard for deployed blockchains. keywords: blockchain; decentralized; hyperledger cache: www-hyperledger-mentorship-spotlight-blockchain-network-operation-in-a-decentralized-way.html plain text: www-hyperledger-mentorship-spotlight-blockchain-network-operation-in-a-decentralized-way.txt item: #2873 of 3327 id: www-hyperledger-mentorship-spotlight-cactus-samples-business-logic-plugins-for-cactus author: www title: www-hyperledger-mentorship-spotlight-cactus-samples-business-logic-plugins-for-cactus date: None words: 806 flesch: 30 summary: Mentorship Project Title Cactus-samples – Business Logic Plugins for Cactus Description To build Open Digital Asset Protocol as a business plugin of  Hyperledger Cactus to standardize cross chain transaction Status COMPLETED  Difficulty HIGH  Additional Details Learning Objectives, Expected Outcomes and Project Results available here. This project has also given me more information about how people interact with Hyperledger Cactus when they are new to it. keywords: cactus; hyperledger; mentorship; project cache: www-hyperledger-mentorship-spotlight-cactus-samples-business-logic-plugins-for-cactus.html plain text: www-hyperledger-mentorship-spotlight-cactus-samples-business-logic-plugins-for-cactus.txt item: #2874 of 3327 id: www-hyperledger-mentorship-spotlight-cactus-samples-business-logic-plugins-for-cactus?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-cactus-samples-business-logic-plugins-for-cactus?hs_amp=true date: None words: 495 flesch: 35 summary: Hyperledger Mentorship Spotlight: Cactus-samples - Business Logic Plugins for Cactus – Hyperledger Foundation Blog | LF Decentralized Trust Hyperledger Mentorship Spotlight: Cactus-samples - Business Logic Plugins for Cactus – Hyperledger Foundation Written by Hyperledger | Sep 29, 2021 7:39:19 AM The Hyperledger Mentorship Program is a structured hands-on learning opportunity for new developers who may otherwise lack the opportunity to gain exposure to Hyperledger open source development and entry to the technical community. Mentorship Project Title Cactus-samples – Business Logic Plugins for Cactus Description To build Open Digital Asset Protocol as a business plugin of  Hyperledger Cactus to standardize cross chain transaction Status COMPLETED  Difficulty HIGH  Additional Details Learning Objectives, Expected Outcomes and Project Results available here. keywords: cactus; hyperledger cache: www-hyperledger-mentorship-spotlight-cactus-samples-business-logic-plugins-for-cactus?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-cactus-samples-business-logic-plugins-for-cactus?hs_amp=true.txt item: #2875 of 3327 id: www-hyperledger-mentorship-spotlight-developer-marketing author: www title: www-hyperledger-mentorship-spotlight-developer-marketing date: None words: 728 flesch: 47 summary: In one of our sessions, Ben had arranged for Hyperledger Foundation Executive Director Daniela Barbosa to join us. The mentorship project started with researching and understanding Hyperledger Foundation, its ecosystem and marketing and communications maps and channels as well as reviewing the marketing strategy. keywords: foundation; hyperledger; marketing cache: www-hyperledger-mentorship-spotlight-developer-marketing.html plain text: www-hyperledger-mentorship-spotlight-developer-marketing.txt item: #2876 of 3327 id: www-hyperledger-mentorship-spotlight-developer-marketing?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-developer-marketing?hs_amp=true date: None words: 419 flesch: 61 summary: In one of our sessions, Ben had arranged for Hyperledger Foundation Executive Director Daniela Barbosa to join us. Hyperledger Mentorship Spotlight: Developer Marketing – Hyperledger Foundation Blog | LF Decentralized Trust Hyperledger Mentorship Spotlight: Developer Marketing – Hyperledger Foundation Written by Hyperledger | Jan 13, 2023 8:22:09 AM keywords: marketing cache: www-hyperledger-mentorship-spotlight-developer-marketing?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-developer-marketing?hs_amp=true.txt item: #2877 of 3327 id: www-hyperledger-mentorship-spotlight-document-review-and-implement-hyperledger-anoncreds-zkp-cryptographic-primitives author: www title: www-hyperledger-mentorship-spotlight-document-review-and-implement-hyperledger-anoncreds-zkp-cryptographic-primitives date: None words: 1118 flesch: 30 summary: The sources we referred to were the relevant codebases of AnonCreds and other projects, and the whitepaper of Hyperledger AnonCreds, which clearly states the mathematical details involved in the ZKP processes. Deliverables and Overcoming Challenges: Over the course of the mentorship, I successfully contributed to the creation of the specification for Hyperledger AnonCreds verifiable credentials and presentations—a significant achievement. keywords: anoncreds; decentralized; hyperledger; project cache: www-hyperledger-mentorship-spotlight-document-review-and-implement-hyperledger-anoncreds-zkp-cryptographic-primitives.html plain text: www-hyperledger-mentorship-spotlight-document-review-and-implement-hyperledger-anoncreds-zkp-cryptographic-primitives.txt item: #2878 of 3327 id: www-hyperledger-mentorship-spotlight-document-review-and-implement-hyperledger-anoncreds-zkp-cryptographic-primitives?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-document-review-and-implement-hyperledger-anoncreds-zkp-cryptographic-primitives?hs_amp=true date: None words: 801 flesch: 33 summary: Hyperledger Mentorship Spotlight: Document, Review, and Implement Hyperledger AnonCreds ZKP Cryptographic Primitives Blog | LF Decentralized Trust Hyperledger Mentorship Spotlight: Document, Review, and Implement Hyperledger AnonCreds ZKP Cryptographic Primitives Written by Aritra Bhaduri | Nov 28, 2023 3:40:20 PM Working on the Document, Review, and Implement Hyperledger AnonCreds ZKP Cryptographic Primitives Hyperledger Mentorship project has been a thrilling journey, filled with challenges, learnings, and a deep sense of contribution to a broader technical community. The sources we referred to were the relevant codebases of AnonCreds and other projects, and the whitepaper of Hyperledger AnonCreds, which clearly states the mathematical details involved in the ZKP processes. keywords: anoncreds; hyperledger; project cache: www-hyperledger-mentorship-spotlight-document-review-and-implement-hyperledger-anoncreds-zkp-cryptographic-primitives?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-document-review-and-implement-hyperledger-anoncreds-zkp-cryptographic-primitives?hs_amp=true.txt item: #2879 of 3327 id: www-hyperledger-mentorship-spotlight-documentation-and-use-cases-for-climate-action author: www title: www-hyperledger-mentorship-spotlight-documentation-and-use-cases-for-climate-action date: None words: 846 flesch: 27 summary: To learn more about our Hyperledger Mentorship Program and how you can participate in our next cohort, head over to our program overview page on the Hyperledger wiki. Hyperledger Mentorship Spotlight: Documentation and Use Cases for Climate Action – Hyperledger Foundation 2025 keywords: hyperledger; mentorship; project; use cache: www-hyperledger-mentorship-spotlight-documentation-and-use-cases-for-climate-action.html plain text: www-hyperledger-mentorship-spotlight-documentation-and-use-cases-for-climate-action.txt item: #2880 of 3327 id: www-hyperledger-mentorship-spotlight-enable-kubernetes-operators-support-for-fablo author: www title: www-hyperledger-mentorship-spotlight-enable-kubernetes-operators-support-for-fablo date: None words: 823 flesch: 50 summary: Its main goal is to provide a super-easy start with Hyperledger Fabric. Before the mentorship, I had previous experience working with Kubernetes and Bash, but none with Hyperledger Fabric. keywords: decentralized; fablo; hyperledger; kubernetes cache: www-hyperledger-mentorship-spotlight-enable-kubernetes-operators-support-for-fablo.html plain text: www-hyperledger-mentorship-spotlight-enable-kubernetes-operators-support-for-fablo.txt item: #2881 of 3327 id: www-hyperledger-mentorship-spotlight-extend-hyperledger-iroha-queries-with-optional-arguments author: www title: www-hyperledger-mentorship-spotlight-extend-hyperledger-iroha-queries-with-optional-arguments date: None words: 814 flesch: 34 summary: Hyperledger Mentorship Spotlight: Extend Hyperledger Iroha Queries with Optional Arguments – Hyperledger Foundation 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger Iroha Hyperledger Mentorship Spotlight: Extend Hyperledger Iroha Queries with Optional Arguments Hyperledger | Dec 9, 2021 The Hyperledger Mentorship Program is a structured hands-on learning opportunity for new developers who may otherwise lack the opportunity to gain exposure to Hyperledger open source development and entry to the technical community. Mentorship Project Title Extend Hyperledger Iroha Queries with Optional Arguments Description To extend Hyperledger Iroha queries with optional arguments. keywords: hyperledger; iroha; mentorship; project cache: www-hyperledger-mentorship-spotlight-extend-hyperledger-iroha-queries-with-optional-arguments.html plain text: www-hyperledger-mentorship-spotlight-extend-hyperledger-iroha-queries-with-optional-arguments.txt item: #2882 of 3327 id: www-hyperledger-mentorship-spotlight-extend-hyperledger-iroha-queries-with-optional-arguments?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-extend-hyperledger-iroha-queries-with-optional-arguments?hs_amp=true date: None words: 505 flesch: 42 summary: Hyperledger Mentorship Spotlight: Extend Hyperledger Iroha Queries with Optional Arguments – Hyperledger Foundation Blog | LF Decentralized Trust Hyperledger Mentorship Spotlight: Extend Hyperledger Iroha Queries with Optional Arguments – Hyperledger Foundation Written by Hyperledger | Dec 9, 2021 6:25:50 AM The Hyperledger Mentorship Program is a structured hands-on learning opportunity for new developers who may otherwise lack the opportunity to gain exposure to Hyperledger open source development and entry to the technical community. Mentorship Project Title Extend Hyperledger Iroha Queries with Optional Arguments Description To extend Hyperledger Iroha queries with optional arguments. keywords: hyperledger; mentorship cache: www-hyperledger-mentorship-spotlight-extend-hyperledger-iroha-queries-with-optional-arguments?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-extend-hyperledger-iroha-queries-with-optional-arguments?hs_amp=true.txt item: #2883 of 3327 id: www-hyperledger-mentorship-spotlight-extend-secure-did-registry-for-hyperledger-frameworks-on-github-gitlab author: www title: www-hyperledger-mentorship-spotlight-extend-secure-did-registry-for-hyperledger-frameworks-on-github-gitlab date: None words: 998 flesch: 34 summary: Hyperledger Mentorship Spotlight: Extend secure DID Registry for Hyperledger frameworks on Github/Gitlab – Hyperledger Foundation 2025 Final Project Video Mentee [image_with_animation image_url=”116739″ image_size=”full” animation_type=”entrance” animation=”Fade In” hover_animation=”none” alignment=”” border_radius=”none” box_shadow=”none” image_loading=”default” max_width=”100%” max_width_mobile=”default”] Wei Yao New Jersey Institute of Technology “It is a fantastic experience to participate in an open-source project under Hyperledger Foundation. keywords: github; hyperledger; project; registry cache: www-hyperledger-mentorship-spotlight-extend-secure-did-registry-for-hyperledger-frameworks-on-github-gitlab.html plain text: www-hyperledger-mentorship-spotlight-extend-secure-did-registry-for-hyperledger-frameworks-on-github-gitlab.txt item: #2884 of 3327 id: www-hyperledger-mentorship-spotlight-extending-solidity-vm-integration-in-iroha author: www title: www-hyperledger-mentorship-spotlight-extending-solidity-vm-integration-in-iroha date: None words: 742 flesch: 35 summary: Mentorship Project Title Extending Solidity VM Integration in Iroha Description Extend Solidity VM (from Hyperledger Burrow) integration in Hyperledger Iroha (1.x) and query pipeline Status COMPLETED  Difficulty LOW Additional Details Learning Objectives, Expected Outcomes and Project Results available here. I learned a lot throughout this mentorship program about Hyperledger Iroha’s architecture and its working, writing code with better readability and working in an open source community. keywords: hyperledger; iroha; project cache: www-hyperledger-mentorship-spotlight-extending-solidity-vm-integration-in-iroha.html plain text: www-hyperledger-mentorship-spotlight-extending-solidity-vm-integration-in-iroha.txt item: #2885 of 3327 id: www-hyperledger-mentorship-spotlight-extending-solidity-vm-integration-in-iroha?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-extending-solidity-vm-integration-in-iroha?hs_amp=true date: None words: 433 flesch: 42 summary: Mentorship Project Title Extending Solidity VM Integration in Iroha Description Extend Solidity VM (from Hyperledger Burrow) integration in Hyperledger Iroha (1.x) and query pipeline Status COMPLETED  Difficulty LOW Additional Details Learning Objectives, Expected Outcomes and Project Results available here. I learned a lot throughout this mentorship program about Hyperledger Iroha’s architecture and its working, writing code with better readability and working in an open source community. keywords: hyperledger; mentorship cache: www-hyperledger-mentorship-spotlight-extending-solidity-vm-integration-in-iroha?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-extending-solidity-vm-integration-in-iroha?hs_amp=true.txt item: #2886 of 3327 id: www-hyperledger-mentorship-spotlight-fabric-ethereum-token-bridging author: www title: www-hyperledger-mentorship-spotlight-fabric-ethereum-token-bridging date: None words: 734 flesch: 41 summary: Hyperledger Technologies: Hyperledger Fabric, Hyperledger Besu, Hyperledger Cactus. I aim to continue contributing to Hyperledger Cactus (now Hyperledger Cacti), the Hyperledger project directed toward interoperability. keywords: fabric; hyperledger; interoperability; project cache: www-hyperledger-mentorship-spotlight-fabric-ethereum-token-bridging.html plain text: www-hyperledger-mentorship-spotlight-fabric-ethereum-token-bridging.txt item: #2887 of 3327 id: www-hyperledger-mentorship-spotlight-fabric-ethereum-token-bridging?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-fabric-ethereum-token-bridging?hs_amp=true date: None words: 419 flesch: 48 summary: Hyperledger Technologies: Hyperledger Fabric, Hyperledger Besu, Hyperledger Cactus. I aim to continue contributing to Hyperledger Cactus (now Hyperledger Cacti), the Hyperledger project directed toward interoperability. keywords: fabric; hyperledger cache: www-hyperledger-mentorship-spotlight-fabric-ethereum-token-bridging?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-fabric-ethereum-token-bridging?hs_amp=true.txt item: #2888 of 3327 id: www-hyperledger-mentorship-spotlight-global-scouting-of-dlt-blockchain-educational-opportunities author: www title: www-hyperledger-mentorship-spotlight-global-scouting-of-dlt-blockchain-educational-opportunities date: None words: 776 flesch: 36 summary: To learn more about our Hyperledger Mentorship Program and how you can participate in our next cohort, head over to our program overview page on the Hyperledger wiki. Hyperledger Mentorship Spotlight: Global Scouting of DLT / Blockchain Educational Opportunities – Hyperledger Foundation 2025 keywords: blockchain; hyperledger; mentorship; project cache: www-hyperledger-mentorship-spotlight-global-scouting-of-dlt-blockchain-educational-opportunities.html plain text: www-hyperledger-mentorship-spotlight-global-scouting-of-dlt-blockchain-educational-opportunities.txt item: #2889 of 3327 id: www-hyperledger-mentorship-spotlight-gvcr-secure-verifiable-credential-registries-vcr-for-github-gitlab author: www title: www-hyperledger-mentorship-spotlight-gvcr-secure-verifiable-credential-registries-vcr-for-github-gitlab date: None words: 968 flesch: 41 summary: It can also be used in Hyperledger Indy projects by providing endpoints of cryptographic verifications for credential issuers. This project was conceptualized to provision secure verifiable credential registries that utilize Github’s data model and API to offer exactly the same APIs for any other verifiable credential registry. keywords: decentralized; gvcr; hyperledger; project cache: www-hyperledger-mentorship-spotlight-gvcr-secure-verifiable-credential-registries-vcr-for-github-gitlab.html plain text: www-hyperledger-mentorship-spotlight-gvcr-secure-verifiable-credential-registries-vcr-for-github-gitlab.txt item: #2890 of 3327 id: www-hyperledger-mentorship-spotlight-gvcr-secure-verifiable-credential-registries-vcr-for-github-gitlab?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-gvcr-secure-verifiable-credential-registries-vcr-for-github-gitlab?hs_amp=true date: None words: 654 flesch: 47 summary: It can also be used in Hyperledger Indy projects by providing endpoints of cryptographic verifications for credential issuers. This project was conceptualized to provision secure verifiable credential registries that utilize Github’s data model and API to offer exactly the same APIs for any other verifiable credential registry. keywords: gvcr; project cache: www-hyperledger-mentorship-spotlight-gvcr-secure-verifiable-credential-registries-vcr-for-github-gitlab?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-gvcr-secure-verifiable-credential-registries-vcr-for-github-gitlab?hs_amp=true.txt item: #2891 of 3327 id: www-hyperledger-mentorship-spotlight-hyperledger-aries-integration-to-support-fabric-as-blockchain-ledger author: www title: www-hyperledger-mentorship-spotlight-hyperledger-aries-integration-to-support-fabric-as-blockchain-ledger date: None words: 770 flesch: 36 summary: Finally, I learnt a lot about Hyperledger Fabric architecture as well as Hyperledger Indy and Docker networks.” Hyperledger Fabric is the most used DLT in enterprise applications, and decentralised identity (DID)/self-sovereign identity (SSI) applications have grown in the last three to four years. keywords: fabric; hyperledger; project cache: www-hyperledger-mentorship-spotlight-hyperledger-aries-integration-to-support-fabric-as-blockchain-ledger.html plain text: www-hyperledger-mentorship-spotlight-hyperledger-aries-integration-to-support-fabric-as-blockchain-ledger.txt item: #2892 of 3327 id: www-hyperledger-mentorship-spotlight-implement-a-cli-for-node-interactions-in-hyperledger-solang author: www title: www-hyperledger-mentorship-spotlight-implement-a-cli-for-node-interactions-in-hyperledger-solang date: None words: 1198 flesch: 50 summary: Project Details We divided the project into two main parts: Polkadot Node Interactions: This involved refactoring the extrinsic submission from “cargo-contract” into a separate crate and using this new crate in Solang CLI to enable user interactions with contracts on Polkadot. Hyperledger Mentorship Spotlight: Implement a CLI for node interactions in Hyperledger Solang 2025 Update: Off to a Fast Start! keywords: code; hyperledger; project; solang cache: www-hyperledger-mentorship-spotlight-implement-a-cli-for-node-interactions-in-hyperledger-solang.html plain text: www-hyperledger-mentorship-spotlight-implement-a-cli-for-node-interactions-in-hyperledger-solang.txt item: #2893 of 3327 id: www-hyperledger-mentorship-spotlight-implement-a-cli-for-node-interactions-in-hyperledger-solang?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-implement-a-cli-for-node-interactions-in-hyperledger-solang?hs_amp=true date: None words: 884 flesch: 58 summary: Project Details We divided the project into two main parts: Polkadot Node Interactions: This involved refactoring the extrinsic submission from “cargo-contract” into a separate crate and using this new crate in Solang CLI to enable user interactions with contracts on Polkadot. Hyperledger Mentorship Spotlight: Implement a CLI for node interactions in Hyperledger Solang Blog | LF Decentralized Trust Hyperledger Mentorship Spotlight: Implement a CLI for node interactions in Hyperledger Solang Written by Tarek Elsayed keywords: hyperledger; solang cache: www-hyperledger-mentorship-spotlight-implement-a-cli-for-node-interactions-in-hyperledger-solang?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-implement-a-cli-for-node-interactions-in-hyperledger-solang?hs_amp=true.txt item: #2894 of 3327 id: www-hyperledger-mentorship-spotlight-implement-client-side-security-for-climate-sig-fabric-application author: www title: www-hyperledger-mentorship-spotlight-implement-client-side-security-for-climate-sig-fabric-application date: None words: 888 flesch: 28 summary: Final Project Video Mentee [image_with_animation image_url=”116234″ image_size=”full” animation_type=”entrance” animation=”Fade In” hover_animation=”none” alignment=”” border_radius=”none” box_shadow=”none” image_loading=”default” max_width=”100%” max_width_mobile=”default”] Bertrand Rioux King Abdullah Petroleum Studies and Research Center “Climate side security involves moving private keys of users off Hyperledger Fabric network servers. Mentorship Project Title Implement Client Side Security for Climate SIG Fabric Application Description To explore and implement an application with client side authentication for Hyperledger Fabric utility emissions data channel. keywords: client; fabric; hyperledger; project cache: www-hyperledger-mentorship-spotlight-implement-client-side-security-for-climate-sig-fabric-application.html plain text: www-hyperledger-mentorship-spotlight-implement-client-side-security-for-climate-sig-fabric-application.txt item: #2895 of 3327 id: www-hyperledger-mentorship-spotlight-implement-cross-chain-contract-invocation-using-servicemesh-way author: www title: www-hyperledger-mentorship-spotlight-implement-cross-chain-contract-invocation-using-servicemesh-way date: None words: 775 flesch: 35 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog Hyperledger Mentorship Spotlight: Implement Cross Chain Contract Invocation Using ‘ServiceMesh’ Way Hyperledger | Dec 20, 2021 The Hyperledger Mentorship Program is a structured hands-on learning opportunity for new developers who may otherwise lack the opportunity to gain exposure to Hyperledger open source development and entry to the technical community. “The Hyperledger Mentorship Program has been a great opportunity for me to dive into the world of open source development. keywords: chain; hyperledger; mentorship; project cache: www-hyperledger-mentorship-spotlight-implement-cross-chain-contract-invocation-using-servicemesh-way.html plain text: www-hyperledger-mentorship-spotlight-implement-cross-chain-contract-invocation-using-servicemesh-way.txt item: #2896 of 3327 id: www-hyperledger-mentorship-spotlight-implement-two-compiler-passes-for-solang-solidity-compiler author: www title: www-hyperledger-mentorship-spotlight-implement-two-compiler-passes-for-solang-solidity-compiler date: None words: 709 flesch: 30 summary: To learn more about our Hyperledger Mentorship Program and how you can participate in our next cohort, head over to our program overview page on the Hyperledger wiki. Hyperledger Mentorship Spotlight: Implement Two Compiler Passes for Solang Solidity Compiler – Hyperledger Foundation 2025 Update: Off to a Fast Start! keywords: compiler; hyperledger; mentorship cache: www-hyperledger-mentorship-spotlight-implement-two-compiler-passes-for-solang-solidity-compiler.html plain text: www-hyperledger-mentorship-spotlight-implement-two-compiler-passes-for-solang-solidity-compiler.txt item: #2897 of 3327 id: www-hyperledger-mentorship-spotlight-iroha-2-blockchain-explorer author: www title: www-hyperledger-mentorship-spotlight-iroha-2-blockchain-explorer date: None words: 1278 flesch: 41 summary: This update ensures that the explorer stays up to date with the latest improvements in Hyperledger Iroha 2. This synchronisation introduces complexities, particularly in managing discrepancies between frontend requirements and the data supplied by the backend during the development and update processes to ensure alignment with changes in Iroha logic.  keywords: explorer; hyperledger; iroha; project cache: www-hyperledger-mentorship-spotlight-iroha-2-blockchain-explorer.html plain text: www-hyperledger-mentorship-spotlight-iroha-2-blockchain-explorer.txt item: #2898 of 3327 id: www-hyperledger-mentorship-spotlight-iroha-2-blockchain-explorer?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-iroha-2-blockchain-explorer?hs_amp=true date: None words: 964 flesch: 45 summary: This update ensures that the explorer stays up to date with the latest improvements in Hyperledger Iroha 2. This synchronisation introduces complexities, particularly in managing discrepancies between frontend requirements and the data supplied by the backend during the development and update processes to ensure alignment with changes in Iroha logic.  keywords: explorer; iroha cache: www-hyperledger-mentorship-spotlight-iroha-2-blockchain-explorer?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-iroha-2-blockchain-explorer?hs_amp=true.txt item: #2899 of 3327 id: www-hyperledger-mentorship-spotlight-iroha-and-cactus-integration author: www title: www-hyperledger-mentorship-spotlight-iroha-and-cactus-integration date: None words: 897 flesch: 36 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger Iroha Hyperledger Mentorship Spotlight: Iroha and Cactus Integration Hyperledger | Sep 21, 2021 The Hyperledger Mentorship Program is a structured hands-on learning opportunity for new developers who may otherwise lack the opportunity to gain exposure to Hyperledger open source development and entry to the technical community. This project has also given me more information about how people interact with Hyperledger Cactus when they are new to it. keywords: hyperledger; iroha; mentorship; project cache: www-hyperledger-mentorship-spotlight-iroha-and-cactus-integration.html plain text: www-hyperledger-mentorship-spotlight-iroha-and-cactus-integration.txt item: #2900 of 3327 id: www-hyperledger-mentorship-spotlight-iroha-and-cactus-integration?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-iroha-and-cactus-integration?hs_amp=true date: None words: 588 flesch: 41 summary: Hyperledger Mentorship Spotlight: Iroha and Cactus Integration – Hyperledger Foundation Blog | LF Decentralized Trust Hyperledger Mentorship Spotlight: Iroha and Cactus Integration – Hyperledger Foundation Written by Hyperledger | Sep 21, 2021 9:24:57 AM The Hyperledger Mentorship Program is a structured hands-on learning opportunity for new developers who may otherwise lack the opportunity to gain exposure to Hyperledger open source development and entry to the technical community. This project has also given me more information about how people interact with Hyperledger Cactus when they are new to it. keywords: hyperledger; project cache: www-hyperledger-mentorship-spotlight-iroha-and-cactus-integration?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-iroha-and-cactus-integration?hs_amp=true.txt item: #2901 of 3327 id: www-hyperledger-mentorship-spotlight-learning-tokens-hyperledger-besu author: www title: www-hyperledger-mentorship-spotlight-learning-tokens-hyperledger-besu date: None words: 1863 flesch: 42 summary: From the technical perspective, I implemented Hyperledger Learning Tokens using Hardhat, Solidity, Hyperledger Besu, and ReactJS for creating the frontend user interface, NestJS for creating the API and designing backend functionalities, and Postgres as the database.  The journey with Hyperledger Learning Tokens is just beginning, promising further advancements in the gradual integration of Learning Tokens within the current education system. keywords: besu; hyperledger; learning; project; token cache: www-hyperledger-mentorship-spotlight-learning-tokens-hyperledger-besu.html plain text: www-hyperledger-mentorship-spotlight-learning-tokens-hyperledger-besu.txt item: #2902 of 3327 id: www-hyperledger-mentorship-spotlight-learning-tokens-hyperledger-besu?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-learning-tokens-hyperledger-besu?hs_amp=true date: None words: 1549 flesch: 44 summary: From the technical perspective, I implemented Hyperledger Learning Tokens using Hardhat, Solidity, Hyperledger Besu, and ReactJS for creating the frontend user interface, NestJS for creating the API and designing backend functionalities, and Postgres as the database.  The journey with Hyperledger Learning Tokens is just beginning, promising further advancements in the gradual integration of Learning Tokens within the current education system. keywords: hyperledger; learning; project; token cache: www-hyperledger-mentorship-spotlight-learning-tokens-hyperledger-besu?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-learning-tokens-hyperledger-besu?hs_amp=true.txt item: #2903 of 3327 id: www-hyperledger-mentorship-spotlight-operate-blockchain-network-in-an-efficient-way author: www title: www-hyperledger-mentorship-spotlight-operate-blockchain-network-in-an-efficient-way date: None words: 778 flesch: 30 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog Hyperledger Mentorship Spotlight: Operate Blockchain Network in An Efficient Way Hyperledger | Dec 20, 2021 The Hyperledger Mentorship Program is a structured hands-on learning opportunity for new developers who may otherwise lack the opportunity to gain exposure to Hyperledger open source development and entry to the technical community. To learn more about our Hyperledger Mentorship Program and how you can participate in our next cohort, head over to our program overview page on the Hyperledger wiki. keywords: decentralized; hyperledger; mentorship; project cache: www-hyperledger-mentorship-spotlight-operate-blockchain-network-in-an-efficient-way.html plain text: www-hyperledger-mentorship-spotlight-operate-blockchain-network-in-an-efficient-way.txt item: #2904 of 3327 id: www-hyperledger-mentorship-spotlight-optimizing-the-pipelines-using-github-actions-for-caliper-and-caliper-benchmarks author: www title: www-hyperledger-mentorship-spotlight-optimizing-the-pipelines-using-github-actions-for-caliper-and-caliper-benchmarks date: None words: 751 flesch: 43 summary: I developed  a good understanding of how Hyperledger Caliper works and, in general, how a benchmarking system is designed. Personally, I plan on continuing to contribute added features to Hyperledger Caliper. keywords: caliper; hyperledger; project cache: www-hyperledger-mentorship-spotlight-optimizing-the-pipelines-using-github-actions-for-caliper-and-caliper-benchmarks.html plain text: www-hyperledger-mentorship-spotlight-optimizing-the-pipelines-using-github-actions-for-caliper-and-caliper-benchmarks.txt item: #2905 of 3327 id: www-hyperledger-mentorship-spotlight-performance-analysis-and-benchmarking-of-besu-using-caliper-with-complex-workloads author: www title: www-hyperledger-mentorship-spotlight-performance-analysis-and-benchmarking-of-besu-using-caliper-with-complex-workloads date: None words: 835 flesch: 34 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Mentorship Program | Hyperledger Caliper | Besu Hyperledger Mentorship Spotlight: Performance Analysis and Benchmarking of Besu using Caliper with Complex Workloads Suyash Nayan | Jan 11, 2024 Introduction My recent mentorship journey with Hyperledger Foundation has been an enlightening path of growth, learning and meaningful contributions to the Hyperledger ecosystem. What I worked on: Hyperledger Besu, a key project under the vast umbrella of Hyperledger Foundation, is known for its robustness in private blockchain networks. keywords: besu; caliper; hyperledger; performance cache: www-hyperledger-mentorship-spotlight-performance-analysis-and-benchmarking-of-besu-using-caliper-with-complex-workloads.html plain text: www-hyperledger-mentorship-spotlight-performance-analysis-and-benchmarking-of-besu-using-caliper-with-complex-workloads.txt item: #2906 of 3327 id: www-hyperledger-mentorship-spotlight-performance-analysis-and-benchmarking-of-besu-using-caliper-with-complex-workloads?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-performance-analysis-and-benchmarking-of-besu-using-caliper-with-complex-workloads?hs_amp=true date: None words: 519 flesch: 41 summary: What I worked on: Hyperledger Besu, a key project under the vast umbrella of Hyperledger Foundation, is known for its robustness in private blockchain networks. My PRs to Besu and Caliper can be found here: Besu, Caliper The Impact This project not only provided valuable insights into Hyperledger Besu’s performance but also paved the way for future optimizations and enhancements to Besu. keywords: besu; hyperledger cache: www-hyperledger-mentorship-spotlight-performance-analysis-and-benchmarking-of-besu-using-caliper-with-complex-workloads?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-performance-analysis-and-benchmarking-of-besu-using-caliper-with-complex-workloads?hs_amp=true.txt item: #2907 of 3327 id: www-hyperledger-mentorship-spotlight-solang-solidity-compiler-optimizations-and-error-handling author: www title: www-hyperledger-mentorship-spotlight-solang-solidity-compiler-optimizations-and-error-handling date: None words: 1458 flesch: 54 summary: Project name: Solang Solidity Compiler optimizations and error handling Introduction: What is Hyperledger Solang? What comes next?  For the next six months, I will continue working on Hyperledger Solang through a Web3 Foundation grant with a focus on improving the Solang developer experience. keywords: code; hyperledger; multiplication; solang; solidity cache: www-hyperledger-mentorship-spotlight-solang-solidity-compiler-optimizations-and-error-handling.html plain text: www-hyperledger-mentorship-spotlight-solang-solidity-compiler-optimizations-and-error-handling.txt item: #2908 of 3327 id: www-hyperledger-mentorship-spotlight-support-decentralized-governance-for-smart-contracts-in-fabric-python-sdk author: www title: www-hyperledger-mentorship-spotlight-support-decentralized-governance-for-smart-contracts-in-fabric-python-sdk date: None words: 751 flesch: 32 summary: I am happy to help Kiv learn more about Hyperledger Fabric and the Python SDK, and I hope we can continue to work on adding more features to the project.” How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog Hyperledger Mentorship Spotlight: Support Decentralized Governance for Smart Contracts in Fabric Python SDK Hyperledger | Dec 20, 2021 The Hyperledger Mentorship Program is a structured hands-on learning opportunity for new developers who may otherwise lack the opportunity to gain exposure to Hyperledger open source development and entry to the technical community. keywords: decentralized; hyperledger; project cache: www-hyperledger-mentorship-spotlight-support-decentralized-governance-for-smart-contracts-in-fabric-python-sdk.html plain text: www-hyperledger-mentorship-spotlight-support-decentralized-governance-for-smart-contracts-in-fabric-python-sdk.txt item: #2909 of 3327 id: www-hyperledger-mentorship-spotlight-support-nft-standards-in-weaver-for-cross-network-asset-operations author: www title: www-hyperledger-mentorship-spotlight-support-nft-standards-in-weaver-for-cross-network-asset-operations date: None words: 854 flesch: 40 summary: During this mentorship, I had the pleasure of implementing different ERC asset standards interoperability for Weaver with the possibility to ensure future interoperability.  Besu-SDK Solidity contract Besu-CLI Protobuf implementation in interoperability contract: keywords: asset; hyperledger; interoperability; protobuf cache: www-hyperledger-mentorship-spotlight-support-nft-standards-in-weaver-for-cross-network-asset-operations.html plain text: www-hyperledger-mentorship-spotlight-support-nft-standards-in-weaver-for-cross-network-asset-operations.txt item: #2910 of 3327 id: www-hyperledger-mentorship-spotlight-support-nft-standards-in-weaver-for-cross-network-asset-operations?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-support-nft-standards-in-weaver-for-cross-network-asset-operations?hs_amp=true date: None words: 543 flesch: 45 summary: During this mentorship, I had the pleasure of implementing different ERC asset standards interoperability for Weaver with the possibility to ensure future interoperability.  Besu-SDK Solidity contract Besu-CLI Protobuf implementation in interoperability contract: keywords: hyperledger; interoperability cache: www-hyperledger-mentorship-spotlight-support-nft-standards-in-weaver-for-cross-network-asset-operations?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-support-nft-standards-in-weaver-for-cross-network-asset-operations?hs_amp=true.txt item: #2911 of 3327 id: www-hyperledger-mentorship-spotlight-technical-deep-dive-workshop-content-creation-for-hyperledger-cactus author: www title: www-hyperledger-mentorship-spotlight-technical-deep-dive-workshop-content-creation-for-hyperledger-cactus date: None words: 682 flesch: 38 summary: Project name: Technical Deep Dive Workshop Content Creation for Hyperledger Cactus  My work on the Technical Deep Dive Workshop Content Creation for Hyperledger Cactus mentorship project was focused on delivering a three-hour long course in both English and Portuguese on the Hyperledger Cacti tool. During my mentorship project, I had the opportunity to engage Hyperledger Cacti developers, allowing me to study and contribute to a highly organized and optimized repository. keywords: decentralized; hyperledger; project cache: www-hyperledger-mentorship-spotlight-technical-deep-dive-workshop-content-creation-for-hyperledger-cactus.html plain text: www-hyperledger-mentorship-spotlight-technical-deep-dive-workshop-content-creation-for-hyperledger-cactus.txt item: #2912 of 3327 id: www-hyperledger-mentorship-spotlight-technical-deep-dive-workshop-content-creation-for-hyperledger-cactus?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-technical-deep-dive-workshop-content-creation-for-hyperledger-cactus?hs_amp=true date: None words: 371 flesch: 46 summary: Project name: Technical Deep Dive Workshop Content Creation for Hyperledger Cactus  My work on the Technical Deep Dive Workshop Content Creation for Hyperledger Cactus mentorship project was focused on delivering a three-hour long course in both English and Portuguese on the Hyperledger Cacti tool. During my mentorship project, I had the opportunity to engage Hyperledger Cacti developers, allowing me to study and contribute to a highly organized and optimized repository. keywords: hyperledger cache: www-hyperledger-mentorship-spotlight-technical-deep-dive-workshop-content-creation-for-hyperledger-cactus?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-technical-deep-dive-workshop-content-creation-for-hyperledger-cactus?hs_amp=true.txt item: #2913 of 3327 id: www-hyperledger-mentorship-spotlight-the-giving-chain author: www title: www-hyperledger-mentorship-spotlight-the-giving-chain date: None words: 713 flesch: 34 summary: Hyperledger Mentorship Spotlight: The Giving Chain – Hyperledger Foundation 2025 To learn more about our Hyperledger Mentorship Program and how you can participate in our next cohort, head over to our program overview page on the Hyperledger wiki. keywords: chain; hyperledger; mentorship; project cache: www-hyperledger-mentorship-spotlight-the-giving-chain.html plain text: www-hyperledger-mentorship-spotlight-the-giving-chain.txt item: #2914 of 3327 id: www-hyperledger-mentorship-spotlight-upgrade-fabric-network-from-1-4-x-to-2-2-x-using-hyperledger-bevel author: www title: www-hyperledger-mentorship-spotlight-upgrade-fabric-network-from-1-4-x-to-2-2-x-using-hyperledger-bevel date: None words: 801 flesch: 42 summary: Hyperledger Bevel provided insights on how to automate and set up a production grade Hyperledger Fabric network on Kubernetes platform in various cloud providers. Hyperledger Mentorship Spotlight: Upgrade Fabric network from 1.4.x to 2.2.x using Hyperledger Bevel – Hyperledger Foundation 2025 keywords: fabric; hyperledger; network cache: www-hyperledger-mentorship-spotlight-upgrade-fabric-network-from-1-4-x-to-2-2-x-using-hyperledger-bevel.html plain text: www-hyperledger-mentorship-spotlight-upgrade-fabric-network-from-1-4-x-to-2-2-x-using-hyperledger-bevel.txt item: #2915 of 3327 id: www-hyperledger-mentorship-spotlight-upgrade-fabric-network-from-1-4-x-to-2-2-x-using-hyperledger-bevel?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-upgrade-fabric-network-from-1-4-x-to-2-2-x-using-hyperledger-bevel?hs_amp=true date: None words: 486 flesch: 49 summary: Hyperledger Bevel provided insights on how to automate and set up a production grade Hyperledger Fabric network on Kubernetes platform in various cloud providers. Hyperledger Mentorship Spotlight: Upgrade Fabric network from 1.4.x to 2.2.x using Hyperledger Bevel – Hyperledger Foundation Blog | LF Decentralized Trust Hyperledger Mentorship Spotlight: Upgrade Fabric network from 1.4.x to 2.2.x using Hyperledger Bevel – Hyperledger Foundation Written by Mohit Vaish | Jan 11, 2023 9:37:44 AM What did you work on? Project name: Upgrade Fabric network from 1.4.x to 2.2.x using Hyperledger Bevel Objective: Hyperledger Bevel is an automation framework for rapidly and consistently deploying production-ready DLT platforms. keywords: fabric; hyperledger cache: www-hyperledger-mentorship-spotlight-upgrade-fabric-network-from-1-4-x-to-2-2-x-using-hyperledger-bevel?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-upgrade-fabric-network-from-1-4-x-to-2-2-x-using-hyperledger-bevel?hs_amp=true.txt item: #2916 of 3327 id: www-hyperledger-mentorship-spotlight-use-of-nlp-and-dlt-to-enable-digitalization-of-telecom-roaming-agreements author: www title: www-hyperledger-mentorship-spotlight-use-of-nlp-and-dlt-to-enable-digitalization-of-telecom-roaming-agreements date: None words: 1004 flesch: 30 summary: To learn more about our Hyperledger Mentorship Program and how you can participate in our next cohort, head over to our program overview page on the Hyperledger wiki. How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog Hyperledger Mentorship Spotlight: Use of NLP and DLT to Enable Digitalization of Telecom Roaming Agreements Hyperledger | Dec 7, 2021 The Hyperledger Mentorship Program is a structured hands-on learning opportunity for new developers who may otherwise lack the opportunity to gain exposure to Hyperledger open source development and entry to the technical community. keywords: hyperledger; nlp; project; use cache: www-hyperledger-mentorship-spotlight-use-of-nlp-and-dlt-to-enable-digitalization-of-telecom-roaming-agreements.html plain text: www-hyperledger-mentorship-spotlight-use-of-nlp-and-dlt-to-enable-digitalization-of-telecom-roaming-agreements.txt item: #2917 of 3327 id: www-hyperledger-mentorship-spotlight-visual-studio-code-support-for-hyperledger-caliper-artifacts author: www title: www-hyperledger-mentorship-spotlight-visual-studio-code-support-for-hyperledger-caliper-artifacts date: None words: 784 flesch: 45 summary: Hyperledger Mentorship Spotlight: Visual Studio Code support for Hyperledger Caliper artifacts – Hyperledger Foundation 2025 Update: Off to a Fast Start!  Project name: Visual Studio Code support for Hyperledger Caliper artifacts A little background to the project  Hyperledger Caliper is a tool for performance benchmarking of existing Hyperledger projects. keywords: caliper; code; hyperledger cache: www-hyperledger-mentorship-spotlight-visual-studio-code-support-for-hyperledger-caliper-artifacts.html plain text: www-hyperledger-mentorship-spotlight-visual-studio-code-support-for-hyperledger-caliper-artifacts.txt item: #2918 of 3327 id: www-hyperledger-mentorship-spotlight-visual-studio-code-support-for-hyperledger-caliper-artifacts?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-visual-studio-code-support-for-hyperledger-caliper-artifacts?hs_amp=true date: None words: 472 flesch: 57 summary: Hyperledger Mentorship Spotlight: Visual Studio Code support for Hyperledger Caliper artifacts – Hyperledger Foundation Blog | LF Decentralized Trust Hyperledger Mentorship Spotlight: Visual Studio Code support for Hyperledger Caliper artifacts – Hyperledger Foundation Written by Eravatee Raje | Feb 27, 2023 6:00:00 AM What did you work on? Project name: Visual Studio Code support for Hyperledger Caliper artifacts A little background to the project  Hyperledger Caliper is a tool for performance benchmarking of existing Hyperledger projects. keywords: hyperledger cache: www-hyperledger-mentorship-spotlight-visual-studio-code-support-for-hyperledger-caliper-artifacts?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-visual-studio-code-support-for-hyperledger-caliper-artifacts?hs_amp=true.txt item: #2919 of 3327 id: www-hyperledger-mentorship-spotlight-visualization-and-analysis-of-cross-chain-transactions author: www title: www-hyperledger-mentorship-spotlight-visualization-and-analysis-of-cross-chain-transactions date: None words: 818 flesch: 25 summary: To learn more about our Hyperledger Mentorship Program and how you can participate in our next cohort, head over to our program overview page on the Hyperledger wiki. Hyperledger Mentorship Spotlight: Visualization and Analysis of Cross-Chain Transactions – Hyperledger Foundation 2025 keywords: hyperledger; interoperability; mentorship; project cache: www-hyperledger-mentorship-spotlight-visualization-and-analysis-of-cross-chain-transactions.html plain text: www-hyperledger-mentorship-spotlight-visualization-and-analysis-of-cross-chain-transactions.txt item: #2920 of 3327 id: www-hyperledger-mentorship-spotlight-visualization-and-analysis-of-cross-chain-transactions?hs_amp=true author: www title: www-hyperledger-mentorship-spotlight-visualization-and-analysis-of-cross-chain-transactions?hs_amp=true date: None words: 507 flesch: 25 summary: Hyperledger Mentorship Spotlight: Visualization and Analysis of Cross-Chain Transactions – Hyperledger Foundation Blog | LF Decentralized Trust Hyperledger Mentorship Spotlight: Visualization and Analysis of Cross-Chain Transactions – Hyperledger Foundation Written by Hyperledger | Dec 7, 2021 8:55:06 AM The Hyperledger Mentorship Program is a structured hands-on learning opportunity for new developers who may otherwise lack the opportunity to gain exposure to Hyperledger open source development and entry to the technical community. To learn more about our Hyperledger Mentorship Program and how you can participate in our next cohort, head over to our program overview page on the Hyperledger wiki. keywords: hyperledger; mentorship cache: www-hyperledger-mentorship-spotlight-visualization-and-analysis-of-cross-chain-transactions?hs_amp=true.html plain text: www-hyperledger-mentorship-spotlight-visualization-and-analysis-of-cross-chain-transactions?hs_amp=true.txt item: #2921 of 3327 id: www-hyperledger-powered-digital-identity-solutions-at-work author: www title: www-hyperledger-powered-digital-identity-solutions-at-work date: None words: 1198 flesch: 36 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog | Project: Hyperledger Indy | Decentralized Identity Hyperledger-Powered Digital Identity Solutions at Work Hyperledger | Apr 29, 2021 As the world continues to grapple with COVID-19, there is an upswing in interest in digital identity technologies and their potential to underpin new health passes, travel credentials and other pathways to restarting economies that are effective, secure, accessible and privacy preserving.  Trust Your Supplier  Built on Hyperledger Fabric blockchain technology, Trust Your Supplier provides organizations a trusted exchange of information across an encrypted blockchain environment to minimize risk and fraud throughout the onboarding and life cycle of partnerships.  keywords: alastria; decentralized; hyperledger; identity; technologies cache: www-hyperledger-powered-digital-identity-solutions-at-work.html plain text: www-hyperledger-powered-digital-identity-solutions-at-work.txt item: #2922 of 3327 id: www-hyperledger-powered-digital-identity-solutions-at-work?hs_amp=true author: www title: www-hyperledger-powered-digital-identity-solutions-at-work?hs_amp=true date: None words: 883 flesch: 40 summary: Trust Your Supplier  Built on Hyperledger Fabric blockchain technology, Trust Your Supplier provides organizations a trusted exchange of information across an encrypted blockchain environment to minimize risk and fraud throughout the onboarding and life cycle of partnerships.  However, digital identity solutions are reshaping other industries as well. keywords: alastria; hyperledger; identity cache: www-hyperledger-powered-digital-identity-solutions-at-work?hs_amp=true.html plain text: www-hyperledger-powered-digital-identity-solutions-at-work?hs_amp=true.txt item: #2923 of 3327 id: www-hyperledger-powered-education-solutions-in-action author: www title: www-hyperledger-powered-education-solutions-in-action date: None words: 1274 flesch: 33 summary: Students of the university can join the development of the system, thus acquiring skills in creating financial systems based on Hyperledger technologies. Read on for more about these #HyperledgerEdu solutions, built using a mix of Hyperledger technologies: Byacco, an on-campus payment system Soramitsu has officially released Byacco, a payment system based on Hyperledger Iroha, for the University of Aizu, Japan. keywords: digital; education; hyperledger; students; technologies cache: www-hyperledger-powered-education-solutions-in-action.html plain text: www-hyperledger-powered-education-solutions-in-action.txt item: #2924 of 3327 id: www-hyperledger-powered-education-solutions-in-action?hs_amp=true author: www title: www-hyperledger-powered-education-solutions-in-action?hs_amp=true date: None words: 959 flesch: 35 summary: Students of the university can join the development of the system, thus acquiring skills in creating financial systems based on Hyperledger technologies. Read on for more about these #HyperledgerEdu solutions, built using a mix of Hyperledger technologies: Byacco, an on-campus payment system Soramitsu has officially released Byacco, a payment system based on Hyperledger Iroha, for the University of Aizu, Japan. keywords: digital; education; hyperledger; students cache: www-hyperledger-powered-education-solutions-in-action?hs_amp=true.html plain text: www-hyperledger-powered-education-solutions-in-action?hs_amp=true.txt item: #2925 of 3327 id: www-hyperledger-powered-healthcare-solutions-in-action author: www title: www-hyperledger-powered-healthcare-solutions-in-action date: None words: 1319 flesch: 33 summary: Bringing Trust and Privacy-Preserving Smart Contracts to Clinical Trials in Healthcare – Andrew Weiss, UMBC (in partnership with Softhread) & Bruno Vavala, Intel Fast, Secure, and Accurate Evaluation of Prescription Drug Reimbursement Claims using Hyperledger Fabric – Alevtina Dubovitskaya, Swisscom AG Blockchain in COVID-19 Fight – US HHS Testing Results Reporting Using Distributed Ledger – Mark Rakhmilevich & Bala Vellanki, Oracle  Ongoing activity in the space is driven by the very active Hyperledger Healthcare Special Interest Group (SIG), which unites healthcare professionals and technologists from around the world in advancing the state of the healthcare industry through the implementation of technology solutions using blockchain technologies in general, and the umbrella of Hyperledger frameworks and toolsets in specific. A number of Hyperledger technologies are at work helping drive new approaches to the existing and emerging complexities of healthcare. keywords: blockchain; health; healthcare; hyperledger; technologies; testing cache: www-hyperledger-powered-healthcare-solutions-in-action.html plain text: www-hyperledger-powered-healthcare-solutions-in-action.txt item: #2926 of 3327 id: www-hyperledger-powered-healthcare-solutions-in-action?hs_amp=true author: www title: www-hyperledger-powered-healthcare-solutions-in-action?hs_amp=true date: None words: 1002 flesch: 36 summary: Bringing Trust and Privacy-Preserving Smart Contracts to Clinical Trials in Healthcare – Andrew Weiss, UMBC (in partnership with Softhread) & Bruno Vavala, Intel Fast, Secure, and Accurate Evaluation of Prescription Drug Reimbursement Claims using Hyperledger Fabric – Alevtina Dubovitskaya, Swisscom AG Blockchain in COVID-19 Fight – US HHS Testing Results Reporting Using Distributed Ledger – Mark Rakhmilevich & Bala Vellanki, Oracle  Ongoing activity in the space is driven by the very active Hyperledger Healthcare Special Interest Group (SIG), which unites healthcare professionals and technologists from around the world in advancing the state of the healthcare industry through the implementation of technology solutions using blockchain technologies in general, and the umbrella of Hyperledger frameworks and toolsets in specific. MediConCen MediConCen built a consortium system powered by Hyperledger Fabric that automates medical insurance claims without using any paper. keywords: blockchain; health; healthcare; hyperledger; testing cache: www-hyperledger-powered-healthcare-solutions-in-action?hs_amp=true.html plain text: www-hyperledger-powered-healthcare-solutions-in-action?hs_amp=true.txt item: #2927 of 3327 id: www-hyperledger-powered-solutions-helping-to-reshape-healthcare author: www title: www-hyperledger-powered-solutions-helping-to-reshape-healthcare date: None words: 1077 flesch: 28 summary: Today, healthcare organizations typically collect provider demographic data in separate IT systems maintained by each organization independently. For their first application, they tackled the challenge of providing healthcare organizations with accurate provider demographic data. keywords: data; decentralized; healthcare; hyperledger; technologies cache: www-hyperledger-powered-solutions-helping-to-reshape-healthcare.html plain text: www-hyperledger-powered-solutions-helping-to-reshape-healthcare.txt item: #2928 of 3327 id: www-hyperledger-quilt author: www title: www-hyperledger-quilt date: None words: 526 flesch: 19 summary: Blog | LF Decentralized Trust | Hyperledger Quilt 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page keywords: blog; decentralized; hyperledger; technologies cache: www-hyperledger-quilt.html plain text: www-hyperledger-quilt.txt item: #2929 of 3327 id: www-hyperledger-sawtooth author: www title: www-hyperledger-sawtooth date: None words: 534 flesch: 18 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Blog | LF Decentralized Trust | Hyperledger Sawtooth 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? keywords: blog; decentralized; hyperledger; technologies cache: www-hyperledger-sawtooth.html plain text: www-hyperledger-sawtooth.txt item: #2930 of 3327 id: www-hyperledger-sawtooth-blockchain-performance-metrics-with-grafana author: www title: www-hyperledger-sawtooth-blockchain-performance-metrics-with-grafana date: None words: 2443 flesch: 51 summary: Listing 2 shows the commands to download the Sawtooth repository, build the Grafana Docker container, download the InfluxDB Docker container, create a database directory, start the Docker container, start the Grafana container, and verify that everything is running. Building the Grafana Docker container takes several steps and downloads several packages into the container. keywords: container; docker; grafana; influxdb; metrics; sawtooth; sudo; telegraf cache: www-hyperledger-sawtooth-blockchain-performance-metrics-with-grafana.html plain text: www-hyperledger-sawtooth-blockchain-performance-metrics-with-grafana.txt item: #2931 of 3327 id: www-hyperledger-sawtooth-security-audit author: www title: www-hyperledger-sawtooth-security-audit date: None words: 535 flesch: 37 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog Hyperledger Sawtooth Security Audit Hyperledger | May 22, 2018 David Huseby, Hyperledger Security Maven   As part of the software development process at Hyperledger, any project that reaches their 1.0 milestone must have a security audit conducted by an outside firm. As we did with the Hyperledger Fabric security audit, we hired the audit firm Nettitude to also audit Hyperledger Sawtooth. keywords: audit; hyperledger; security cache: www-hyperledger-sawtooth-security-audit.html plain text: www-hyperledger-sawtooth-security-audit.txt item: #2932 of 3327 id: www-hyperledger-sawtooth-seth-and-truffle-101 author: www title: www-hyperledger-sawtooth-seth-and-truffle-101 date: None words: 1688 flesch: 50 summary: To which I will answer, this question is a false choice as with Hyperledger Sawtooth Seth, you can build your smart contracts in Solidity and deploy the same smart contract in Hyperledger Sawtooth — Pretty cool isn’t it? What is Hyperledger Sawtooth Seth? keywords: contract; ethereum; hyperledger; sawtooth; seth cache: www-hyperledger-sawtooth-seth-and-truffle-101.html plain text: www-hyperledger-sawtooth-seth-and-truffle-101.txt item: #2933 of 3327 id: www-hyperledger-sawtooth-seth-and-truffle-101?hs_amp=true author: www title: www-hyperledger-sawtooth-seth-and-truffle-101?hs_amp=true date: None words: 1377 flesch: 56 summary: To which I will answer, this question is a false choice as with Hyperledger Sawtooth Seth, you can build your smart contracts in Solidity and deploy the same smart contract in Hyperledger Sawtooth — Pretty cool isn’t it? What is Hyperledger Sawtooth Seth? keywords: contract; sawtooth; seth cache: www-hyperledger-sawtooth-seth-and-truffle-101?hs_amp=true.html plain text: www-hyperledger-sawtooth-seth-and-truffle-101?hs_amp=true.txt item: #2934 of 3327 id: www-hyperledger-solang author: www title: www-hyperledger-solang date: None words: 629 flesch: 25 summary: Blog | LF Decentralized Trust | Hyperledger Solang 2025 Read More Hyperledger | Jun 1, 2023 Hyperledger Solang Meet Hyperledger Solang, a portable Solidity compiler We are excited to announce that Solang has been accepted as the latest Hyperledger® project and has been renamed as Hyperledger Solang™. keywords: decentralized; hyperledger; project; solang cache: www-hyperledger-solang.html plain text: www-hyperledger-solang.txt item: #2935 of 3327 id: www-hyperledger-solang-release-v0-2-0-and-whats-to-come author: www title: www-hyperledger-solang-release-v0-2-0-and-whats-to-come date: None words: 2082 flesch: 55 summary: We still need to generate Anchor IDLs from Solidity contracts and integrate Anchor discriminators with Solang so that Rust contracts can call Solidity and vice versa. Image 1: Choosing the compiled contract bundle in contracts-UI In the next section, you’ll be presented with some options for contract instantiation. keywords: contract; node; solang; solidity; substrate; use cache: www-hyperledger-solang-release-v0-2-0-and-whats-to-come.html plain text: www-hyperledger-solang-release-v0-2-0-and-whats-to-come.txt item: #2936 of 3327 id: www-hyperledger-solang-release-v0-3-venice-delivers-improvements-and-new-features-including-chain-extensions-support-for-substrate author: www title: www-hyperledger-solang-release-v0-3-venice-delivers-improvements-and-new-features-including-chain-extensions-support-for-substrate date: None words: 1119 flesch: 43 summary: How to Get Involved with Hyperledger Solang The Hyperledger Solang maintainers are active on Discord, and can be found on #solang channel on Hyperledger Discord most days. How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger Solang Hyperledger Solang Release v0.3 (Venice) Delivers Improvements and New Features, Including Chain Extensions Support for Substrate Hyperledger | Jun 1, 2023 Development work on Hyperledger Solang has been ramping up quickly. keywords: chain; hyperledger; solang; solidity cache: www-hyperledger-solang-release-v0-3-venice-delivers-improvements-and-new-features-including-chain-extensions-support-for-substrate.html plain text: www-hyperledger-solang-release-v0-3-venice-delivers-improvements-and-new-features-including-chain-extensions-support-for-substrate.txt item: #2937 of 3327 id: www-hyperledger-solang-release-v0-3-venice-delivers-improvements-and-new-features-including-chain-extensions-support-for-substrate?hs_amp=true author: www title: www-hyperledger-solang-release-v0-3-venice-delivers-improvements-and-new-features-including-chain-extensions-support-for-substrate?hs_amp=true date: None words: 810 flesch: 49 summary: How to Get Involved with Hyperledger Solang The Hyperledger Solang maintainers are active on Discord, and can be found on #solang channel on Hyperledger Discord most days. Hyperledger Solang Release v0.3 (Venice) Delivers Improvements and New Features, Including Chain Extensions Support for Substrate – Hyperledger Foundation Blog | LF Decentralized Trust Hyperledger Solang Release v0.3 (Venice) Delivers Improvements and New Features, Including Chain Extensions Support for Substrate – Hyperledger Foundation Written by Hyperledger | Jun 1, 2023 8:00:00 AM Development work on Hyperledger Solang has been ramping up quickly. keywords: chain; hyperledger; solang cache: www-hyperledger-solang-release-v0-3-venice-delivers-improvements-and-new-features-including-chain-extensions-support-for-substrate?hs_amp=true.html plain text: www-hyperledger-solang-release-v0-3-venice-delivers-improvements-and-new-features-including-chain-extensions-support-for-substrate?hs_amp=true.txt item: #2938 of 3327 id: www-hyperledger-technologies-dominant-for-enterprise-blockchain-deployments-on-2022-forbes-blockchain-50 author: www title: www-hyperledger-technologies-dominant-for-enterprise-blockchain-deployments-on-2022-forbes-blockchain-50 date: None words: 596 flesch: 32 summary: Congratulations to Hyperledger Foundation members DTCC, Fujitsu, Nornickel, Oracle, Tech Mahindra, Tencent and Walmart for making the Forbes Blockchain 50 in 2022. For the companies on the list that have made blockchain technology a core foundation of their business operations, Hyperledger technologies, particularly Hyperledger Fabric, continue to be the standard. keywords: blockchain; hyperledger; technologies cache: www-hyperledger-technologies-dominant-for-enterprise-blockchain-deployments-on-2022-forbes-blockchain-50.html plain text: www-hyperledger-technologies-dominant-for-enterprise-blockchain-deployments-on-2022-forbes-blockchain-50.txt item: #2939 of 3327 id: www-hyperledger-technologies-dominant-for-enterprise-blockchain-deployments-on-2022-forbes-blockchain-50?hs_amp=true author: www title: www-hyperledger-technologies-dominant-for-enterprise-blockchain-deployments-on-2022-forbes-blockchain-50?hs_amp=true date: None words: 285 flesch: 41 summary: Congratulations to Hyperledger Foundation members DTCC, Fujitsu, Nornickel, Oracle, Tech Mahindra, Tencent and Walmart for making the Forbes Blockchain 50 in 2022. For the companies on the list that have made blockchain technology a core foundation of their business operations, Hyperledger technologies, particularly Hyperledger Fabric, continue to be the standard. keywords: hyperledger cache: www-hyperledger-technologies-dominant-for-enterprise-blockchain-deployments-on-2022-forbes-blockchain-50?hs_amp=true.html plain text: www-hyperledger-technologies-dominant-for-enterprise-blockchain-deployments-on-2022-forbes-blockchain-50?hs_amp=true.txt item: #2940 of 3327 id: www-hyperledger-telecom-sig author: www title: www-hyperledger-telecom-sig date: None words: 535 flesch: 19 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Hyperledger Aries | Project: Hyperledger Indy | Special Interest Group | Telecom Introducing the Telecom Decentralized Identity Network (TDIDN), a New Approach to Security, Efficiency and Privacy keywords: blog; decentralized; hyperledger; technologies cache: www-hyperledger-telecom-sig.html plain text: www-hyperledger-telecom-sig.txt item: #2941 of 3327 id: www-hyperledger-transact author: www title: www-hyperledger-transact date: None words: 534 flesch: 18 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Blog | LF Decentralized Trust | Hyperledger Transact 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? keywords: blog; decentralized; hyperledger; technologies cache: www-hyperledger-transact.html plain text: www-hyperledger-transact.txt item: #2942 of 3327 id: www-hyperledger-ursa author: www title: www-hyperledger-ursa date: None words: 528 flesch: 17 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Blog | LF Decentralized Trust | Hyperledger Ursa 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? keywords: blog; decentralized; hyperledger; technologies cache: www-hyperledger-ursa.html plain text: www-hyperledger-ursa.txt item: #2943 of 3327 id: www-hyperledger-web3j-in-2024-updates-for-blockchain-developers author: www title: www-hyperledger-web3j-in-2024-updates-for-blockchain-developers date: None words: 2083 flesch: 42 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Web3j Hyperledger Web3j in 2024: Updates for Blockchain Developers Nischal Sharma and George Tebrean, Hyperledger Web3j maintainers and Blockchain Developers at Web3 Labs | Aug 29, 2024 Since its introduction in February 2024, maintainers have focused on significantly enhancing Hyperledger Web3j, a crucial tool for Java and Android developers working within the Ethereum ecosystem. Hyperledger Web3j serves as a bridge between decentralized identity frameworks and Ethereum's blockchain. keywords: blockchain; decentralized; developers; ethereum; hyperledger; web3j cache: www-hyperledger-web3j-in-2024-updates-for-blockchain-developers.html plain text: www-hyperledger-web3j-in-2024-updates-for-blockchain-developers.txt item: #2944 of 3327 id: www-hyperledger-web3j-in-2024-updates-for-blockchain-developers?hs_amp=true author: www title: www-hyperledger-web3j-in-2024-updates-for-blockchain-developers?hs_amp=true date: None words: 1773 flesch: 45 summary: : Updates for Blockchain Developers Blog | LF Decentralized Trust Hyperledger Web3j in 2024: Updates for Blockchain Developers Written by Nischal Sharma and George Tebrean, Hyperledger Web3j maintainers and Blockchain Developers at Web3 Labs | Aug 29, 2024 2:16:23 PM Since its introduction in February 2024, maintainers have focused on significantly enhancing Hyperledger Web3j, a crucial tool for Java and Android developers working within the Ethereum ecosystem. Hyperledger Web3j serves as a bridge between decentralized identity frameworks and Ethereum's blockchain. keywords: developers; ethereum; hyperledger; web3j cache: www-hyperledger-web3j-in-2024-updates-for-blockchain-developers?hs_amp=true.html plain text: www-hyperledger-web3j-in-2024-updates-for-blockchain-developers?hs_amp=true.txt item: #2945 of 3327 id: www-hyperledger-web3jhsm-support-for-aws-kms author: www title: www-hyperledger-web3jhsm-support-for-aws-kms date: None words: 840 flesch: 36 summary: To address these difficulties, a ready-to-use implementation has been added specifically for AWS KMS HSM support. What many may not realize is that AWS KMS itself operates as a Hardware Security Module (HSM), offering the same level of security you'd expect from dedicated hardware solutions. keywords: aws; hsm; kms cache: www-hyperledger-web3jhsm-support-for-aws-kms.html plain text: www-hyperledger-web3jhsm-support-for-aws-kms.txt item: #2946 of 3327 id: www-hyperledger-web3jhsm-support-for-aws-kms?hs_amp=true author: www title: www-hyperledger-web3jhsm-support-for-aws-kms?hs_amp=true date: None words: 530 flesch: 45 summary: To address these difficulties, a ready-to-use implementation has been added specifically for AWS KMS HSM support. What many may not realize is that AWS KMS itself operates as a Hardware Security Module (HSM), offering the same level of security you'd expect from dedicated hardware solutions. keywords: aws; kms cache: www-hyperledger-web3jhsm-support-for-aws-kms?hs_amp=true.html plain text: www-hyperledger-web3jhsm-support-for-aws-kms?hs_amp=true.txt item: #2947 of 3327 id: www-hyperledger-welcomes-project-indy author: www title: www-hyperledger-welcomes-project-indy date: None words: 1589 flesch: 44 summary: Now the contribution of Indy to Hyperledger takes the next step in that process, opening up Project Indy to the entire Hyperledger family of developers. Privacy by Design is baked deep into Indy architecture as reflected by three fundamental features: keywords: decentralized; foundation; identity; indy; sovrin cache: www-hyperledger-welcomes-project-indy.html plain text: www-hyperledger-welcomes-project-indy.txt item: #2948 of 3327 id: www-hyperledger-welcomes-project-indy?hs_amp=true author: www title: www-hyperledger-welcomes-project-indy?hs_amp=true date: None words: 1282 flesch: 48 summary: Now the contribution of Indy to Hyperledger takes the next step in that process, opening up Project Indy to the entire Hyperledger family of developers. Privacy by Design is baked deep into Indy architecture as reflected by three fundamental features: keywords: identity; indy; sovrin cache: www-hyperledger-welcomes-project-indy?hs_amp=true.html plain text: www-hyperledger-welcomes-project-indy?hs_amp=true.txt item: #2949 of 3327 id: www-hyperledger-women-share-their-blockchain-journeys author: www title: www-hyperledger-women-share-their-blockchain-journeys date: None words: 1754 flesch: 50 summary: There are significantly less women applicants than men applicants for blockchain roles. I opened a blockchain training center, Ledger Academy, in 2017 and have been successful in obtaining contracts to develop learning materials for several sources.” Grace: “My dad was actually the first person to talk to me about blockchain. keywords: blockchain; decentralized; hyperledger; project; technology; women cache: www-hyperledger-women-share-their-blockchain-journeys.html plain text: www-hyperledger-women-share-their-blockchain-journeys.txt item: #2950 of 3327 id: www-hyperledger-women-share-their-blockchain-journeys-part-ii author: www title: www-hyperledger-women-share-their-blockchain-journeys-part-ii date: None words: 1386 flesch: 50 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog | Hyperledger Community #Hyperledger Women Share their Blockchain Journeys – Part II Hyperledger | Mar 29, 2021 In celebration of #HyperledgerWomen, we asked some of the many excellent women leaders in our community to share some details about their blockchain journey, including how they got started, what projects get them excited and advice they’ve received or have to share.  It is a complete Blockchain solution that abstracts all the complexity of blockchain technology and makes it easy to adopt it in any use case. keywords: blockchain; hyperledger; technologies; technology; women cache: www-hyperledger-women-share-their-blockchain-journeys-part-ii.html plain text: www-hyperledger-women-share-their-blockchain-journeys-part-ii.txt item: #2951 of 3327 id: www-hyperledger-women-share-their-blockchain-journeys-part-iii author: www title: www-hyperledger-women-share-their-blockchain-journeys-part-iii date: None words: 1581 flesch: 45 summary: I have been in the innovation space for over 10 years, helping clients and teams adopt new technologies to rethink how they get work done. Bring your best, and take a chance on yourself to learn something new, apply something old in a new way, and have some fun reshaping the future of industries with new technologies.” Sandra: “There are a myriad of skill sets needed in this burgeoning industry, and we need women of all kinds of backgrounds to get involved. keywords: blockchain; decentralized; hyperledger; technologies; technology cache: www-hyperledger-women-share-their-blockchain-journeys-part-iii.html plain text: www-hyperledger-women-share-their-blockchain-journeys-part-iii.txt item: #2952 of 3327 id: www-hyperledgerasia-a-sampling-of-the-many-of-hyperledger-powered-solutions-in-action-across-asia author: www title: www-hyperledgerasia-a-sampling-of-the-many-of-hyperledger-powered-solutions-in-action-across-asia date: None words: 1694 flesch: 38 summary: Companies across Asia are putting Hyperledger technologies to work to boost trade, fight fraud, streamline financial transactions, authenticate data, verify identities and more.  Built using the Oracle Blockchain Platform implementation of Hyperledger Fabric in multi-cloud deployment, GSBN supports modern and efficient global trade through data exchange. keywords: blockchain; data; decentralized; hyperledger; platform; technologies; trade cache: www-hyperledgerasia-a-sampling-of-the-many-of-hyperledger-powered-solutions-in-action-across-asia.html plain text: www-hyperledgerasia-a-sampling-of-the-many-of-hyperledger-powered-solutions-in-action-across-asia.txt item: #2953 of 3327 id: www-hyperledgerasia-hyperledger-powered-production-solutions-making-an-impact-across-asia-now author: www title: www-hyperledgerasia-hyperledger-powered-production-solutions-making-an-impact-across-asia-now date: None words: 1396 flesch: 40 summary: MediConCen’s Blockchain Medical Ecosystem Named as the Winner of Hong Kong’s “2020 Digital Disruptor” at the IDC Digital Transformation Awards (DXa) 2020, MediConCen simplifies medical insurance claims for medical community, insurers, and general customers using Hyperledger blockchain. dltledgers used Hyperledger Fabric to create the world’s leading “plug-and-play” platform for cross-border trade and supply chain digitization. keywords: blockchain; decentralized; hyperledger; medical; platform; trade cache: www-hyperledgerasia-hyperledger-powered-production-solutions-making-an-impact-across-asia-now.html plain text: www-hyperledgerasia-hyperledger-powered-production-solutions-making-an-impact-across-asia-now.txt item: #2954 of 3327 id: www-hyperledgerclimate-round-up-hyperledger-technologies-in-action-building-a-greener-future author: www title: www-hyperledgerclimate-round-up-hyperledger-technologies-in-action-building-a-greener-future date: None words: 1148 flesch: 30 summary: As part of our spotlight on #HyperledgerClimate, we’ve compiled a sampling of production deployments and solutions built using Hyperledger technologies that are leading the way towards a more sustainable future: 4AIR’s Comprehensive Blockchain-based Registry for Sustainable Aviation Fuel (SAF) Sustainable Aviation Fuel (SAF) is a type of biofuel with a lower carbon footprint than conventional jet fuel. Read more here. ____ Join the conversation about the use of Hyperledger technologies bringing new approaches to tackle climate changes and help ensure a more sustainable future. keywords: digital; fuel; hyperledger; technologies; water cache: www-hyperledgerclimate-round-up-hyperledger-technologies-in-action-building-a-greener-future.html plain text: www-hyperledgerclimate-round-up-hyperledger-technologies-in-action-building-a-greener-future.txt item: #2955 of 3327 id: www-hyperledgerclimate-round-up-hyperledger-technologies-in-action-building-a-greener-future?hs_amp=true author: www title: www-hyperledgerclimate-round-up-hyperledger-technologies-in-action-building-a-greener-future?hs_amp=true date: None words: 832 flesch: 34 summary: As part of our spotlight on #HyperledgerClimate, we’ve compiled a sampling of production deployments and solutions built using Hyperledger technologies that are leading the way towards a more sustainable future: 4AIR’s Comprehensive Blockchain-based Registry for Sustainable Aviation Fuel (SAF) Sustainable Aviation Fuel (SAF) is a type of biofuel with a lower carbon footprint than conventional jet fuel. Read more here. ____ Join the conversation about the use of Hyperledger technologies bringing new approaches to tackle climate changes and help ensure a more sustainable future. keywords: fuel; hyperledger; technologies cache: www-hyperledgerclimate-round-up-hyperledger-technologies-in-action-building-a-greener-future?hs_amp=true.html plain text: www-hyperledgerclimate-round-up-hyperledger-technologies-in-action-building-a-greener-future?hs_amp=true.txt item: #2956 of 3327 id: www-hyperledgerfintech-a-sampling-of-production-applications-using-hyperledger-technologies-in-the-finance-market author: www title: www-hyperledgerfintech-a-sampling-of-production-applications-using-hyperledger-technologies-in-the-finance-market date: None words: 1196 flesch: 42 summary: #HyperledgerFinTech: A sampling of production applications using Hyperledger technologies in the finance market – Hyperledger Foundation 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog | Finance | Project: Hyperledger Indy #HyperledgerFinTech: A sampling of production applications using Hyperledger technologies in the finance market Hyperledger | Sep 28, 2020 The financial services market has long turned to technology to address a range of back-end challenges and enhance customer-facing services. Me is built on top of the IBM Blockchain Platform which is based on Linux Foundation’s open source Hyperledger Fabric v1.2, and will be interoperable with Hyperledger Indy projects.  keywords: blockchain; decentralized; hyperledger; service; technologies cache: www-hyperledgerfintech-a-sampling-of-production-applications-using-hyperledger-technologies-in-the-finance-market.html plain text: www-hyperledgerfintech-a-sampling-of-production-applications-using-hyperledger-technologies-in-the-finance-market.txt item: #2957 of 3327 id: www-hyperledgerfintech-a-sampling-of-production-applications-using-hyperledger-technologies-in-the-finance-market?hs_amp=true author: www title: www-hyperledgerfintech-a-sampling-of-production-applications-using-hyperledger-technologies-in-the-finance-market?hs_amp=true date: None words: 882 flesch: 50 summary: #HyperledgerFinTech: A sampling of production applications using Hyperledger technologies in the finance market – Hyperledger Foundation Blog | LF Decentralized Trust #HyperledgerFinTech: A sampling of production applications using Hyperledger technologies in the finance market – Hyperledger Foundation Written by Hyperledger | Sep 28, 2020 12:22:08 PM The financial services market has long turned to technology to address a range of back-end challenges and enhance customer-facing services. Read on for just a sampling #HyperledgerFinTech solutions, built using a mix of Hyperledger technologies: Bakong Sponsored by the National Bank of Cambodia, the country’s central bank, Bakong is the first retail payments system in the world using blockchain technology. keywords: blockchain; hyperledger; verified.me cache: www-hyperledgerfintech-a-sampling-of-production-applications-using-hyperledger-technologies-in-the-finance-market?hs_amp=true.html plain text: www-hyperledgerfintech-a-sampling-of-production-applications-using-hyperledger-technologies-in-the-finance-market?hs_amp=true.txt item: #2958 of 3327 id: www-hyperledgerhybrid-in-action-connecting-permissioned-and-public-networks-to-maximize-value author: www title: www-hyperledgerhybrid-in-action-connecting-permissioned-and-public-networks-to-maximize-value date: None words: 1111 flesch: 35 summary: IPwe is now deploying 25 million patent NFTs leveraging the hybrid Casper Blockchain and Hyperledger Fabric network. The solution uses the permissioned distributed ledger technologies of open source Hyperledger Fabric and the public Casper Blockchain to securely store verified public and private information about each patent. keywords: blockchain; decentralized; hyperledger; network; technologies cache: www-hyperledgerhybrid-in-action-connecting-permissioned-and-public-networks-to-maximize-value.html plain text: www-hyperledgerhybrid-in-action-connecting-permissioned-and-public-networks-to-maximize-value.txt item: #2959 of 3327 id: www-hyperledgerhybrid-in-action-connecting-permissioned-and-public-networks-to-maximize-value?hs_amp=true author: www title: www-hyperledgerhybrid-in-action-connecting-permissioned-and-public-networks-to-maximize-value?hs_amp=true date: None words: 800 flesch: 39 summary: IPwe is now deploying 25 million patent NFTs leveraging the hybrid Casper Blockchain and Hyperledger Fabric network. The solution uses the permissioned distributed ledger technologies of open source Hyperledger Fabric and the public Casper Blockchain to securely store verified public and private information about each patent. keywords: blockchain; hyperledger; network cache: www-hyperledgerhybrid-in-action-connecting-permissioned-and-public-networks-to-maximize-value?hs_amp=true.html plain text: www-hyperledgerhybrid-in-action-connecting-permissioned-and-public-networks-to-maximize-value?hs_amp=true.txt item: #2960 of 3327 id: www-hyperledgeridentity-round-up-a-cross-section-of-production-digital-identity-solutions-built-using-hyperledger-technologies author: www title: www-hyperledgeridentity-round-up-a-cross-section-of-production-digital-identity-solutions-built-using-hyperledger-technologies date: None words: 1565 flesch: 28 summary: #HyperledgerIdentity round-up: A cross section of production digital identity solutions built using Hyperledger technologies – Hyperledger Foundation 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? And Hyperledger technologies are playing a major role in this transformation.  keywords: credentials; decentralized; digital; hyperledger; identity; staff; technologies cache: www-hyperledgeridentity-round-up-a-cross-section-of-production-digital-identity-solutions-built-using-hyperledger-technologies.html plain text: www-hyperledgeridentity-round-up-a-cross-section-of-production-digital-identity-solutions-built-using-hyperledger-technologies.txt item: #2961 of 3327 id: www-hyperledgeridentity-round-up-a-cross-section-of-production-digital-identity-solutions-built-using-hyperledger-technologies?hs_amp=true author: www title: www-hyperledgeridentity-round-up-a-cross-section-of-production-digital-identity-solutions-built-using-hyperledger-technologies?hs_amp=true date: None words: 1251 flesch: 31 summary: #HyperledgerIdentity round-up: A cross section of production digital identity solutions built using Hyperledger technologies – Hyperledger Foundation Blog | LF Decentralized Trust #HyperledgerIdentity round-up: A cross section of production digital identity solutions built using Hyperledger technologies – Hyperledger Foundation Written by Hyperledger | Sep 28, 2022 4:10:07 PM Verifying identities and information in a digital world is critical for establishing trust. And Hyperledger technologies are playing a major role in this transformation.  keywords: credentials; digital; hyperledger; identity; staff cache: www-hyperledgeridentity-round-up-a-cross-section-of-production-digital-identity-solutions-built-using-hyperledger-technologies?hs_amp=true.html plain text: www-hyperledgeridentity-round-up-a-cross-section-of-production-digital-identity-solutions-built-using-hyperledger-technologies?hs_amp=true.txt item: #2962 of 3327 id: www-hyperledgerinterop-delivering-cross-chain-interoperability-with-hyperledger-technologies author: www title: www-hyperledgerinterop-delivering-cross-chain-interoperability-with-hyperledger-technologies date: None words: 907 flesch: 22 summary: The first prototype from Project Genesis was developed with Digital Asset in partnership with GFT and leveraged Daml smart contracts as well as Digital Assets interoperability protocol layered over Hyperledger Besu and Hyperledger Fabric blockchains. Below, we continue the conversation with highlights of some leading-edge efforts to deliver cross-chain interoperability built using Hyperledger technologies: Cross-Ledger Interbank Settlement: As part of a series of wholesale CBDC trials, Banque de France, the French Central Bank, completed cross-ledger interbank settlement transactions in a multi-blockchain environment. keywords: hyperledger; interoperability; project; technologies cache: www-hyperledgerinterop-delivering-cross-chain-interoperability-with-hyperledger-technologies.html plain text: www-hyperledgerinterop-delivering-cross-chain-interoperability-with-hyperledger-technologies.txt item: #2963 of 3327 id: www-hyperledgerinterop-delivering-cross-chain-interoperability-with-hyperledger-technologies?hs_amp=true author: www title: www-hyperledgerinterop-delivering-cross-chain-interoperability-with-hyperledger-technologies?hs_amp=true date: None words: 599 flesch: 23 summary: The first prototype from Project Genesis was developed with Digital Asset in partnership with GFT and leveraged Daml smart contracts as well as Digital Assets interoperability protocol layered over Hyperledger Besu and Hyperledger Fabric blockchains. In the trial, Hyperledger Fabric and R3’s Corda were able to transact with each other using Weaver, a Hyperledger Lab initially contributed by IBM.  keywords: hyperledger; interoperability cache: www-hyperledgerinterop-delivering-cross-chain-interoperability-with-hyperledger-technologies?hs_amp=true.html plain text: www-hyperledgerinterop-delivering-cross-chain-interoperability-with-hyperledger-technologies?hs_amp=true.txt item: #2964 of 3327 id: www-hyperledgerpayments-applications-making-financial-transactions-easier-faster-and-more-accessible author: www title: www-hyperledgerpayments-applications-making-financial-transactions-easier-faster-and-more-accessible date: None words: 963 flesch: 37 summary: However, there is #HyperledgerPayments action happening on a number of fronts and leveraging a mix of Hyperledger technologies. Sessions will include: A Hyperledger Fabric-based Programmable Money Platform – Robert van Donge, IntellectEU & Dirk Hermans, KBC Group  Hosted Discussion: Private Credit on Blockchain – Anshuman Asthana, Marketnode  Saudi Aramco, Procure to Pay Eco-System – Ali Safri, Avanza Innovations & Abdullah M Askari, Saudi Aramco US Digital Currency: Opportunities, Challenges and Strategies – Jim Mason, DTCC Hands-on-Workshop: Moving Central Bank Digital Currency from Conception to Reality with Hyperledger Technologies – Elli Androulaki & Angelo De Caro, IBM Cover photo by mohamed_hassan from PxHere View previous blog post Back to all blog posts View next blog post The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: decentralized; foundation; hyperledger; system; technologies cache: www-hyperledgerpayments-applications-making-financial-transactions-easier-faster-and-more-accessible.html plain text: www-hyperledgerpayments-applications-making-financial-transactions-easier-faster-and-more-accessible.txt item: #2965 of 3327 id: www-hyperledgerpayments-applications-making-financial-transactions-easier-faster-and-more-accessible?hs_amp=true author: www title: www-hyperledgerpayments-applications-making-financial-transactions-easier-faster-and-more-accessible?hs_amp=true date: None words: 650 flesch: 47 summary: However, there is #HyperledgerPayments action happening on a number of fronts and leveraging a mix of Hyperledger technologies. Powered by Hyperledger Fabric, Kate Coins are issued to customers as loyalty rewards. keywords: bank; hyperledger; system cache: www-hyperledgerpayments-applications-making-financial-transactions-easier-faster-and-more-accessible?hs_amp=true.html plain text: www-hyperledgerpayments-applications-making-financial-transactions-easier-faster-and-more-accessible?hs_amp=true.txt item: #2966 of 3327 id: www-hyperledgersocialimpact-highlighting-hyperledger-powered-solutions-driving-change author: www title: www-hyperledgersocialimpact-highlighting-hyperledger-powered-solutions-driving-change date: None words: 1601 flesch: 34 summary: Oceanworks and Keep Sea Blue: Traceability of recycled plastics used in making consumer and industrial goods Powered by Oracle Blockchain technology based on Hyperledger Fabric, Oceanworks and Keep Sea Blue provide traceability platforms and certifications that are used to encourage effective plastic waste collections from oceans and beaches, linked to sustainable reuse and certification of products made from the recycled materials. Organizations of all sizes and types are levering Hyperledger technologies to power solutions that are driving real change. keywords: blockchain; decentralized; foundation; hyperledger; technologies; transparency; trust cache: www-hyperledgersocialimpact-highlighting-hyperledger-powered-solutions-driving-change.html plain text: www-hyperledgersocialimpact-highlighting-hyperledger-powered-solutions-driving-change.txt item: #2967 of 3327 id: www-identity-applications-in-action-powered-by-hyperledger author: www title: www-identity-applications-in-action-powered-by-hyperledger date: None words: 1157 flesch: 28 summary: With recent advancements in digital identity standards, Sovrin provides a secure and private network for identity holders to collect, manage and share their own verifiable digital credentials. It is built using the IBM Blockchain Platform which is based on Linux Foundation’s open source Hyperledger Fabric  and is aligning with W3C decentralized identity standards, to enable interoperability with other networks. keywords: blockchain; decentralized; hyperledger; identity; network cache: www-identity-applications-in-action-powered-by-hyperledger.html plain text: www-identity-applications-in-action-powered-by-hyperledger.txt item: #2968 of 3327 id: www-identity-applications-in-action-powered-by-hyperledger?hs_amp=true author: www title: www-identity-applications-in-action-powered-by-hyperledger?hs_amp=true date: None words: 845 flesch: 31 summary: With recent advancements in digital identity standards, Sovrin provides a secure and private network for identity holders to collect, manage and share their own verifiable digital credentials. The Hyperledger community is working hard to develop and deploy blockchain-enabled identity technologies and solutions with an eye towards decentralizing control of information and creating new models for verifying identities.  keywords: hyperledger; identity; network cache: www-identity-applications-in-action-powered-by-hyperledger?hs_amp=true.html plain text: www-identity-applications-in-action-powered-by-hyperledger?hs_amp=true.txt item: #2969 of 3327 id: www-interoperability author: www title: www-interoperability date: None words: 780 flesch: 18 summary: | Feb 2, 2022 Labs | Interoperability Meet FireFly, one of the new Hyperledger Labs taking on cross-chain and off-chain operations As enterprises and organizations increase their adoption and deployment of blockchain technology and networks, the overall complexity of systems are growing exponentially. PT Uses Hyperledger Cacti as its Interoperability Framework Research suggests that the market for applications using DLTs will grow, with many organizations stating that blockchain is a critical priority due to, for example, cost... keywords: blog; decentralized; hyperledger; interoperability cache: www-interoperability.html plain text: www-interoperability.txt item: #2970 of 3327 id: www-interoperability-and-integration-developments-in-the-hyperledger-community author: www title: www-interoperability-and-integration-developments-in-the-hyperledger-community date: None words: 1112 flesch: 27 summary: This pluggable architecture helps enable the execution of ledger operations across multiple blockchain ledgers, including Hyperledger Besu, Hyperledger Fabric, Corda, and Quorum available today, with the aim of developers continually adding support for new blockchains in the future.    Cactus started as a Hyperledger Labs project six months ago and has attracted significant attention and become a locus of collaboration between developers from teams at Accenture and Fujitsu, and dozens of others working on DLT platforms both inside and outside Hyperledger. keywords: blockchain; decentralized; hyperledger; identity; interoperability cache: www-interoperability-and-integration-developments-in-the-hyperledger-community.html plain text: www-interoperability-and-integration-developments-in-the-hyperledger-community.txt item: #2971 of 3327 id: www-interoperability-and-integration-developments-in-the-hyperledger-community?hs_amp=true author: www title: www-interoperability-and-integration-developments-in-the-hyperledger-community?hs_amp=true date: None words: 794 flesch: 30 summary: This pluggable architecture helps enable the execution of ledger operations across multiple blockchain ledgers, including Hyperledger Besu, Hyperledger Fabric, Corda, and Quorum available today, with the aim of developers continually adding support for new blockchains in the future.    Cryptoenter has a dual security system: at the Hyperledger blockchain network level and at the Rubicon Blockchain (also based on Hyperledger Fabric) network level. keywords: blockchain; fabric; hyperledger; interoperability cache: www-interoperability-and-integration-developments-in-the-hyperledger-community?hs_amp=true.html plain text: www-interoperability-and-integration-developments-in-the-hyperledger-community?hs_amp=true.txt item: #2972 of 3327 id: www-interoperability-in-the-open-source-community author: www title: www-interoperability-in-the-open-source-community date: None words: 1142 flesch: 44 summary: Successfully trialed in Aruba, its codebase has been donated to Linux Foundation Public Health as an open source solution for sharing health data through verifiable digital credentials. If we can successfully implement a system for incorporating health data in travel, what about all the other clinical notes described by the Cures Act? keywords: data; decentralized; health; interoperability cache: www-interoperability-in-the-open-source-community.html plain text: www-interoperability-in-the-open-source-community.txt item: #2973 of 3327 id: www-introducing-blockchain-explorer-v2.0.0-a-hyperledger-lab author: www title: www-introducing-blockchain-explorer-v2.0.0-a-hyperledger-lab date: None words: 1579 flesch: 38 summary: Join Our Community and Stay Connected We aim to cultivate a thriving community around the project through active participation in Blockchain Explorer meetups and encouraging contributions. New Features: The latest release of Blockchain Explorer v2.0.0 is packed with new features and improvements that make understanding Hyperledger Fabric blockchain easier and even more seamless. keywords: blockchain; explorer; features; hyperledger; release; users cache: www-introducing-blockchain-explorer-v2.0.0-a-hyperledger-lab.html plain text: www-introducing-blockchain-explorer-v2.0.0-a-hyperledger-lab.txt item: #2974 of 3327 id: www-introducing-blockchain-explorer-v2.0.0-a-hyperledger-lab?hs_amp=true author: www title: www-introducing-blockchain-explorer-v2.0.0-a-hyperledger-lab?hs_amp=true date: None words: 1269 flesch: 42 summary: New Features: The latest release of Blockchain Explorer v2.0.0 is packed with new features and improvements that make understanding Hyperledger Fabric blockchain easier and even more seamless.  One of the new features of Blockchain Explorer v2.0.0 is the ability to monitor the health status of the peers and orderers in a Hyperledger Fabric network, which means now users can keep looking at the blockchain network’s peers and orderers condition whether they are online or offline. keywords: blockchain; explorer; hyperledger; users cache: www-introducing-blockchain-explorer-v2.0.0-a-hyperledger-lab?hs_amp=true.html plain text: www-introducing-blockchain-explorer-v2.0.0-a-hyperledger-lab?hs_amp=true.txt item: #2975 of 3327 id: www-introducing-hiero-bringing-hederas-core-network-software-to-linux-foundation-decentralized-trust author: www title: www-introducing-hiero-bringing-hederas-core-network-software-to-linux-foundation-decentralized-trust date: None words: 1330 flesch: 34 summary: By contributing to open standards and development efforts within LF Decentralized Trust communities, Hiero will help accelerate enterprise adoption of blockchain technologies. A Natural Fit for the LF Decentralized Trust Ecosystem As part of its transition to the Linux Foundation, Hiero will collaborate closely with other LF Decentralized Trust projects including those from the Hyperledger ecosystem. keywords: decentralized; foundation; hiero; linux; trust cache: www-introducing-hiero-bringing-hederas-core-network-software-to-linux-foundation-decentralized-trust.html plain text: www-introducing-hiero-bringing-hederas-core-network-software-to-linux-foundation-decentralized-trust.txt item: #2976 of 3327 id: www-introducing-hiero-bringing-hederas-core-network-software-to-linux-foundation-decentralized-trust?hs_amp=true author: www title: www-introducing-hiero-bringing-hederas-core-network-software-to-linux-foundation-decentralized-trust?hs_amp=true date: None words: 1020 flesch: 36 summary: By contributing to open standards and development efforts within LF Decentralized Trust communities, Hiero will help accelerate enterprise adoption of blockchain technologies. A Natural Fit for the LF Decentralized Trust Ecosystem As part of its transition to the Linux Foundation, Hiero will collaborate closely with other LF Decentralized Trust projects including those from the Hyperledger ecosystem. keywords: decentralized; hiero; trust cache: www-introducing-hiero-bringing-hederas-core-network-software-to-linux-foundation-decentralized-trust?hs_amp=true.html plain text: www-introducing-hiero-bringing-hederas-core-network-software-to-linux-foundation-decentralized-trust?hs_amp=true.txt item: #2977 of 3327 id: www-introducing-hyperledger-aries-framework-javascript-0-2-0 author: www title: www-introducing-hyperledger-aries-framework-javascript-0-2-0 date: None words: 1137 flesch: 48 summary: Introducing Hyperledger Aries Framework JavaScript 0.2.0 – Hyperledger Foundation 2025 and I discovered Hyperledger Aries Framework JavaScript, an open source JavaScript/TypeScript framework designed to create interoperable self-sovereign identity solutions. keywords: aries; framework; hyperledger; javascript cache: www-introducing-hyperledger-aries-framework-javascript-0-2-0.html plain text: www-introducing-hyperledger-aries-framework-javascript-0-2-0.txt item: #2978 of 3327 id: www-introducing-hyperledger-aries-framework-javascript-0-4-0 author: www title: www-introducing-hyperledger-aries-framework-javascript-0-4-0 date: None words: 1149 flesch: 40 summary: Introducing Hyperledger Aries Framework JavaScript 0.4.0 – Hyperledger Foundation 2025 Update: Off to a Fast Start!  How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger AnonCreds | Hyperledger Aries | Decentralized Identity Introducing Hyperledger Aries Framework JavaScript 0.4.0 Hyperledger | Jul 6, 2023 After months of hard work by 22 contributors, more than 130 PRs, and 1000+ file changes, we are thrilled to announce that Hyperledger Aries Framework JavaScript (AFJ) version 0.4.0 has been released! keywords: anoncreds; aries; framework; hyperledger cache: www-introducing-hyperledger-aries-framework-javascript-0-4-0.html plain text: www-introducing-hyperledger-aries-framework-javascript-0-4-0.txt item: #2979 of 3327 id: www-introducing-hyperledger-aries-framework-javascript-0-4-0?hs_amp=true author: www title: www-introducing-hyperledger-aries-framework-javascript-0-4-0?hs_amp=true date: None words: 834 flesch: 46 summary: Introducing Hyperledger Aries Framework JavaScript 0.4.0 – Hyperledger Foundation Blog | LF Decentralized Trust Introducing Hyperledger Aries Framework JavaScript 0.4.0 – Hyperledger Foundation Written by Hyperledger | Jul 6, 2023 8:23:11 AM After months of hard work by 22 contributors, more than 130 PRs, and 1000+ file changes, we are thrilled to announce that Hyperledger Aries Framework JavaScript (AFJ) version 0.4.0 has been released! Replacing the Hyperledger Indy SDK In previous versions of Hyperledger Aries Framework JavaScript, the framework was closely tied to the Hyperledger Indy SDK Rust library. keywords: framework; hyperledger cache: www-introducing-hyperledger-aries-framework-javascript-0-4-0?hs_amp=true.html plain text: www-introducing-hyperledger-aries-framework-javascript-0-4-0?hs_amp=true.txt item: #2980 of 3327 id: www-introducing-hyperledger-avalon author: www title: www-introducing-hyperledger-avalon date: None words: 901 flesch: 39 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog | Hyperledger Avalon Introducing Hyperledger Avalon Hyperledger | Oct 3, 2019 We are very excited to announce the latest of the Hyperledger projects, Hyperledger Avalon. In fact, that collaboration is one of the stand-out aspects of Hyperledger Avalon. keywords: avalon; code; hyperledger; project cache: www-introducing-hyperledger-avalon.html plain text: www-introducing-hyperledger-avalon.txt item: #2981 of 3327 id: www-introducing-hyperledger-cacti-a-multi-faceted-pluggable-interoperability-framework author: www title: www-introducing-hyperledger-cacti-a-multi-faceted-pluggable-interoperability-framework date: None words: 1275 flesch: 33 summary: In effect, Hyperledger Cacti scales decentralized trust above and beyond the confines of a single network without requiring networks to merge or integrate, in effect enabling a network-of-networks, as illustrated in the figure below using samples of DLT networks and cross-chain operations.  Instead, Cacti allows networks to preserve autonomy of decision-making while conducting cross-network transactions on a need basis. keywords: cacti; decentralized; hyperledger; interoperability; networks cache: www-introducing-hyperledger-cacti-a-multi-faceted-pluggable-interoperability-framework.html plain text: www-introducing-hyperledger-cacti-a-multi-faceted-pluggable-interoperability-framework.txt item: #2982 of 3327 id: www-introducing-hyperledger-cacti-a-multi-faceted-pluggable-interoperability-framework?hs_amp=true author: www title: www-introducing-hyperledger-cacti-a-multi-faceted-pluggable-interoperability-framework?hs_amp=true date: None words: 964 flesch: 35 summary: In effect, Hyperledger Cacti scales decentralized trust above and beyond the confines of a single network without requiring networks to merge or integrate, in effect enabling a network-of-networks, as illustrated in the figure below using samples of DLT networks and cross-chain operations.  Introducing Hyperledger Cacti, a multi-faceted pluggable interoperability framework – Hyperledger Foundation Blog | LF Decentralized Trust Introducing Hyperledger Cacti, a multi-faceted pluggable interoperability framework – Hyperledger Foundation Written by Hyperledger | Nov 7, 2022 8:00:00 AM In a Hyperledger first, the community has merged two systems (architectures as well as code bases) to create a new project. keywords: cacti; hyperledger; networks cache: www-introducing-hyperledger-cacti-a-multi-faceted-pluggable-interoperability-framework?hs_amp=true.html plain text: www-introducing-hyperledger-cacti-a-multi-faceted-pluggable-interoperability-framework?hs_amp=true.txt item: #2983 of 3327 id: www-introducing-hyperledger-fabric-1-4-lts author: www title: www-introducing-hyperledger-fabric-1-4-lts date: None words: 954 flesch: 42 summary: As noted, Hyperledger Fabric v1.4 LTS marks our first long term support release. However, for Hyperledger Fabric v1.4 LTS, the Fabric maintainers are pledging to provide bug fixes for a period of one year from the date of release (Jan 10). keywords: decentralized; fabric; hyperledger; release cache: www-introducing-hyperledger-fabric-1-4-lts.html plain text: www-introducing-hyperledger-fabric-1-4-lts.txt item: #2984 of 3327 id: www-introducing-hyperledger-firefly-1-0-the-supernode-for-enterprise-web3-applications author: www title: www-introducing-hyperledger-firefly-1-0-the-supernode-for-enterprise-web3-applications date: None words: 1000 flesch: 38 summary: Introducing Hyperledger FireFly 1.0: The SuperNode for Enterprise Web3 Applications – Hyperledger Foundation 2025 Update: Off to a Fast Start!  How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger FireFly Introducing Hyperledger FireFly 1.0: The SuperNode for Enterprise Web3 Applications Hyperledger | Apr 13, 2022 It’s been a busy 10 months for Hyperledger FireFly. keywords: decentralized; firefly; hyperledger; web3 cache: www-introducing-hyperledger-firefly-1-0-the-supernode-for-enterprise-web3-applications.html plain text: www-introducing-hyperledger-firefly-1-0-the-supernode-for-enterprise-web3-applications.txt item: #2985 of 3327 id: www-introducing-hyperledger-firefly-1-0-the-supernode-for-enterprise-web3-applications?hs_amp=true author: www title: www-introducing-hyperledger-firefly-1-0-the-supernode-for-enterprise-web3-applications?hs_amp=true date: None words: 691 flesch: 45 summary: Introducing Hyperledger FireFly 1.0: The SuperNode for Enterprise Web3 Applications – Hyperledger Foundation Blog | LF Decentralized Trust Introducing Hyperledger FireFly 1.0: The SuperNode for Enterprise Web3 Applications – Hyperledger Foundation Written by Hyperledger | Apr 13, 2022 6:00:00 AM It’s been a busy 10 months for Hyperledger FireFly. And today the community is excited to announce that version 1.0 of Hyperledger FireFly is now generally available.  keywords: firefly; hyperledger cache: www-introducing-hyperledger-firefly-1-0-the-supernode-for-enterprise-web3-applications?hs_amp=true.html plain text: www-introducing-hyperledger-firefly-1-0-the-supernode-for-enterprise-web3-applications?hs_amp=true.txt item: #2986 of 3327 id: www-introducing-hyperledger-firefly-a-multi-party-system-for-enterprise-data-flows author: www title: www-introducing-hyperledger-firefly-a-multi-party-system-for-enterprise-data-flows date: None words: 1086 flesch: 48 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Introducing Hyperledger FireFly, a Multi-Party System for Enterprise Data Flows Jessica Rampen | Sep 28, 2021 We are very excited to announce the newest Hyperledger project, Hyperledger FireFly. Introducing Hyperledger FireFly, a Multi-Party System for Enterprise Data Flows 2025 Update: Off to a Fast Start! keywords: firefly; hyperledger; project; system cache: www-introducing-hyperledger-firefly-a-multi-party-system-for-enterprise-data-flows.html plain text: www-introducing-hyperledger-firefly-a-multi-party-system-for-enterprise-data-flows.txt item: #2987 of 3327 id: www-introducing-hyperledger-lab-harmonia-unlocking-interoperability-for-regulated-financial-networks author: www title: www-introducing-hyperledger-lab-harmonia-unlocking-interoperability-for-regulated-financial-networks date: None words: 853 flesch: 26 summary: Introducing Hyperledger Lab Harmonia: Unlocking Interoperability for Regulated Financial Networks – Hyperledger Foundation 2025 Update: Off to a Fast Start!  As Hyperledger Lab Harmonia takes its first steps, we invite you to join us on this transformative journey. keywords: harmonia; hyperledger; interoperability; networks cache: www-introducing-hyperledger-lab-harmonia-unlocking-interoperability-for-regulated-financial-networks.html plain text: www-introducing-hyperledger-lab-harmonia-unlocking-interoperability-for-regulated-financial-networks.txt item: #2988 of 3327 id: www-introducing-hyperledger-lab-harmonia-unlocking-interoperability-for-regulated-financial-networks?hs_amp=true author: www title: www-introducing-hyperledger-lab-harmonia-unlocking-interoperability-for-regulated-financial-networks?hs_amp=true date: None words: 543 flesch: 28 summary: Introducing Hyperledger Lab Harmonia: Unlocking Interoperability for Regulated Financial Networks – Hyperledger Foundation Blog | LF Decentralized Trust Introducing Hyperledger Lab Harmonia: Unlocking Interoperability for Regulated Financial Networks – Hyperledger Foundation Written by Richard G. Brown, CTO of R3, & Peter Munnings, Co-founder and COO of Adhara | Jun 14, 2023 6:00:00 AM Distributed ledger technology has gained significant traction in recent years in the financial sector, where its promise of data consistency, security, and shared business logic is the key to resolving long-standing market-level inefficiencies. As Hyperledger Lab Harmonia takes its first steps, we invite you to join us on this transformative journey. keywords: harmonia; networks cache: www-introducing-hyperledger-lab-harmonia-unlocking-interoperability-for-regulated-financial-networks?hs_amp=true.html plain text: www-introducing-hyperledger-lab-harmonia-unlocking-interoperability-for-regulated-financial-networks?hs_amp=true.txt item: #2989 of 3327 id: www-introducing-hyperledger-web3j-the-ethereum-integration-library-for-enterprises author: www title: www-introducing-hyperledger-web3j-the-ethereum-integration-library-for-enterprises date: None words: 1361 flesch: 41 summary: This is reflected by key metrics of the project: 4.8k GitHub stars 192 contributors 106 releases 1.7k forks More than 1000 resolved issues More than 2 million downloads By bringing in Web3j, Hyperledger Foundation gains another well-established open source project that will benefit from its governance and stewardship. Benefits of Hyperledger Web3j Ease of Integration with Existing Systems: Hyperledger Web3j is a lightweight, highly modular Java library that can be easily integrated into existing enterprise systems. Synergies with Hyperledger Besu: Hyperledger Besu and Hyperledger Web3j already have reciprocal relationships, with both projects leveraging one another. keywords: blockchain; ethereum; hyperledger; project; web3j cache: www-introducing-hyperledger-web3j-the-ethereum-integration-library-for-enterprises.html plain text: www-introducing-hyperledger-web3j-the-ethereum-integration-library-for-enterprises.txt item: #2990 of 3327 id: www-introducing-hyperledger-web3j-the-ethereum-integration-library-for-enterprises?hs_amp=true author: www title: www-introducing-hyperledger-web3j-the-ethereum-integration-library-for-enterprises?hs_amp=true date: None words: 1051 flesch: 46 summary: Synergies with Hyperledger Besu: Hyperledger Besu and Hyperledger Web3j already have reciprocal relationships, with both projects leveraging one another. Introducing Hyperledger Web3j, the Ethereum Integration Library for Enterprises Blog | LF Decentralized Trust Introducing Hyperledger Web3j, the Ethereum Integration Library for Enterprises Written by Conor Svensson, author of Web3j and founder of Web3 Labs | Feb 12, 2024 4:00:00 PM We are very excited to announce the newest Hyperledger project, Hyperledger Web3j. keywords: hyperledger; project; web3j cache: www-introducing-hyperledger-web3j-the-ethereum-integration-library-for-enterprises?hs_amp=true.html plain text: www-introducing-hyperledger-web3j-the-ethereum-integration-library-for-enterprises?hs_amp=true.txt item: #2991 of 3327 id: www-introducing-kubernetes-operators-in-hyperledger-bevel-with-bevel-operator-fabric author: www title: www-introducing-kubernetes-operators-in-hyperledger-bevel-with-bevel-operator-fabric date: None words: 1021 flesch: 33 summary: Users having the need to rapidly and consistently setup production ready DLT networks should consider Hyperledger Bevel, whereas users needing to deploy Hyperledger Fabric components quickly and have operator pattern in place should consider Bevel-Operator-Fabric. Hyperledger Bevel currently supports deployment of R3 Corda open source and enterprise, Hyperledger Fabric, Hyperledger Indy, GoQuorum and Hyperledger Besu. keywords: bevel; fabric; hyperledger; operator cache: www-introducing-kubernetes-operators-in-hyperledger-bevel-with-bevel-operator-fabric.html plain text: www-introducing-kubernetes-operators-in-hyperledger-bevel-with-bevel-operator-fabric.txt item: #2992 of 3327 id: www-introducing-kubernetes-operators-in-hyperledger-bevel-with-bevel-operator-fabric?hs_amp=true author: www title: www-introducing-kubernetes-operators-in-hyperledger-bevel-with-bevel-operator-fabric?hs_amp=true date: None words: 703 flesch: 39 summary: Users having the need to rapidly and consistently setup production ready DLT networks should consider Hyperledger Bevel, whereas users needing to deploy Hyperledger Fabric components quickly and have operator pattern in place should consider Bevel-Operator-Fabric. Hyperledger Bevel currently supports deployment of R3 Corda open source and enterprise, Hyperledger Fabric, Hyperledger Indy, GoQuorum and Hyperledger Besu. keywords: bevel; hyperledger cache: www-introducing-kubernetes-operators-in-hyperledger-bevel-with-bevel-operator-fabric?hs_amp=true.html plain text: www-introducing-kubernetes-operators-in-hyperledger-bevel-with-bevel-operator-fabric?hs_amp=true.txt item: #2993 of 3327 id: www-introducing-linea-ens-support-in-hyperledger-web3j author: www title: www-introducing-linea-ens-support-in-hyperledger-web3j date: None words: 793 flesch: 35 summary: Linea ENS domains take the format name.linea.eth and provide users with a human-readable alternative to their Ethereum addresses, all while ensuring high security and lower transaction costs.  It enables them to resolve all ENS names into addresses or reverse resolve addresses into Linea ENS domains. keywords: ens; hyperledger; linea; web3j cache: www-introducing-linea-ens-support-in-hyperledger-web3j.html plain text: www-introducing-linea-ens-support-in-hyperledger-web3j.txt item: #2994 of 3327 id: www-introducing-linea-ens-support-in-hyperledger-web3j?hs_amp=true author: www title: www-introducing-linea-ens-support-in-hyperledger-web3j?hs_amp=true date: None words: 483 flesch: 45 summary: Linea ENS domains take the format name.linea.eth and provide users with a human-readable alternative to their Ethereum addresses, all while ensuring high security and lower transaction costs.  It enables them to resolve all ENS names into addresses or reverse resolve addresses into Linea ENS domains. keywords: ens; linea cache: www-introducing-linea-ens-support-in-hyperledger-web3j?hs_amp=true.html plain text: www-introducing-linea-ens-support-in-hyperledger-web3j?hs_amp=true.txt item: #2995 of 3327 id: www-introducing-open-enterprise-agent-a-new-hyperledger-lab-for-self-sovereign-digital-identity-dapps author: www title: www-introducing-open-enterprise-agent-a-new-hyperledger-lab-for-self-sovereign-digital-identity-dapps date: None words: 901 flesch: 37 summary: Introducing Open Enterprise Agent, a new Hyperledger lab for self-sovereign digital identity DApps 2025 How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Labs Introducing Open Enterprise Agent, a new Hyperledger lab for self-sovereign digital identity DApps Atala PRISM | Dec 4, 2023 Identity plays a significant role in our everyday lives. keywords: agent; decentralized; enterprise; identity cache: www-introducing-open-enterprise-agent-a-new-hyperledger-lab-for-self-sovereign-digital-identity-dapps.html plain text: www-introducing-open-enterprise-agent-a-new-hyperledger-lab-for-self-sovereign-digital-identity-dapps.txt item: #2996 of 3327 id: www-introducing-open-enterprise-agent-a-new-hyperledger-lab-for-self-sovereign-digital-identity-dapps?hs_amp=true author: www title: www-introducing-open-enterprise-agent-a-new-hyperledger-lab-for-self-sovereign-digital-identity-dapps?hs_amp=true date: None words: 591 flesch: 42 summary: Introducing Open Enterprise Agent, a new Hyperledger lab for self-sovereign digital identity DApps Blog | LF Decentralized Trust Introducing Open Enterprise Agent, a new Hyperledger lab for self-sovereign digital identity DApps Written by Atala PRISM | Dec 4, 2023 2:30:00 PM Identity plays a significant role in our everyday lives. The Open Enterprise Agent provides a way to manage digital identity while preserving privacy, security, and trust. keywords: agent; enterprise cache: www-introducing-open-enterprise-agent-a-new-hyperledger-lab-for-self-sovereign-digital-identity-dapps?hs_amp=true.html plain text: www-introducing-open-enterprise-agent-a-new-hyperledger-lab-for-self-sovereign-digital-identity-dapps?hs_amp=true.txt item: #2997 of 3327 id: www-introducing-parallel-transaction-execution-in-hyperledger-besu author: www title: www-introducing-parallel-transaction-execution-in-hyperledger-besu date: None words: 2157 flesch: 52 summary: Block processing improvement (new payload call) Block processing time has seen a performance improvement of at least 25%, with the 50th percentile decreasing from 282 ms to 207 ms and the 95th percentile dropping from 479 ms to 393 ms. Overall, this PR improves Besu block processing performance between 25 to 45 % with almost no resource usage overhead. keywords: block; execution; parallel; transaction cache: www-introducing-parallel-transaction-execution-in-hyperledger-besu.html plain text: www-introducing-parallel-transaction-execution-in-hyperledger-besu.txt item: #2998 of 3327 id: www-introducing-parallel-transaction-execution-in-hyperledger-besu?hs_amp=true author: www title: www-introducing-parallel-transaction-execution-in-hyperledger-besu?hs_amp=true date: None words: 1847 flesch: 57 summary: Block processing improvement (new payload call) Block processing time has seen a performance improvement of at least 25%, with the 50th percentile decreasing from 282 ms to 207 ms and the 95th percentile dropping from 479 ms to 393 ms. Overall, this PR improves Besu block processing performance between 25 to 45 % with almost no resource usage overhead. keywords: block; parallel; transaction cache: www-introducing-parallel-transaction-execution-in-hyperledger-besu?hs_amp=true.html plain text: www-introducing-parallel-transaction-execution-in-hyperledger-besu?hs_amp=true.txt item: #2999 of 3327 id: www-introducing-signare-a-hyperledger-lab author: www title: www-introducing-signare-a-hyperledger-lab date: None words: 686 flesch: 32 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Labs Introducing Signare, a Hyperledger Lab Peter Munnings (COO at Adhara), Marelize Kriel (Cryptographer at Adhara and Signare maintainer) and Coenie Beyers (Head of R&D at Adhara and Signare maintainer) For detailed information and documentation on Signare visit the  Signare page on GitHub You can also learn more from this talk by the Signare developer community:       View previous blog post Back to all blog posts View next blog post The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: code; contribute; hyperledger; signare cache: www-introducing-signare-a-hyperledger-lab.html plain text: www-introducing-signare-a-hyperledger-lab.txt item: #3000 of 3327 id: www-introducing-signare-a-hyperledger-lab?hs_amp=true author: www title: www-introducing-signare-a-hyperledger-lab?hs_amp=true date: None words: 376 flesch: 39 summary: Introducing Signare, a Hyperledger Lab Blog | LF Decentralized Trust Introducing Signare, a Hyperledger Lab Written by Peter Munnings (COO at Adhara), Marelize Kriel (Cryptographer at Adhara and Signare maintainer) and Coenie Beyers (Head of R&D at Adhara and Signare maintainer) For detailed information and documentation on Signare visit the  Signare page on GitHub You can also learn more from this talk by the Signare developer community:       View full post keywords: hyperledger; signare cache: www-introducing-signare-a-hyperledger-lab?hs_amp=true.html plain text: www-introducing-signare-a-hyperledger-lab?hs_amp=true.txt item: #3001 of 3327 id: www-introducing-splice-a-new-hyperledger-lab-that-supports-canton-network-interoperability author: www title: www-introducing-splice-a-new-hyperledger-lab-that-supports-canton-network-interoperability date: None words: 1160 flesch: 23 summary: Splice was designed to enable Canton Network participants to address these complex challenges and unlock the full value of blockchain and tokenization in regulated financial markets.  Splice aims to make this high level of trust possible by: Making the operations and governance of decentralized Canton synchronizers transparent and trackable through built-in governance tooling Keeping synchronizer transaction costs low via integrated payment, operations monitoring and governance automation Managing these tools and applications via an Apache 2.0 license and an open source community within the Hyperledger ecosystem. keywords: canton; decentralized; hyperledger; network cache: www-introducing-splice-a-new-hyperledger-lab-that-supports-canton-network-interoperability.html plain text: www-introducing-splice-a-new-hyperledger-lab-that-supports-canton-network-interoperability.txt item: #3002 of 3327 id: www-introducing-splice-a-new-hyperledger-lab-that-supports-canton-network-interoperability?hs_amp=true author: www title: www-introducing-splice-a-new-hyperledger-lab-that-supports-canton-network-interoperability?hs_amp=true date: None words: 848 flesch: 23 summary: Splice was designed to enable Canton Network participants to address these complex challenges and unlock the full value of blockchain and tokenization in regulated financial markets.  Following more than a year of testing with financial market participants, this decentralized synchronization infrastructure is now available, providing interoperability with privacy and control, as demonstrated recently in the Canton Network pilot. keywords: canton; hyperledger; network cache: www-introducing-splice-a-new-hyperledger-lab-that-supports-canton-network-interoperability?hs_amp=true.html plain text: www-introducing-splice-a-new-hyperledger-lab-that-supports-canton-network-interoperability?hs_amp=true.txt item: #3003 of 3327 id: www-introducing-the-2025-technical-advisory-council-members-and-outlook author: www title: www-introducing-the-2025-technical-advisory-council-members-and-outlook date: None words: 1897 flesch: 35 summary: They are held weekly on Thursdays at 7:00 AM US/PT, and everyone is welcome to join and participate. __ Here’s the full list of the 2025 LF Decentralized Trust TAC: Marcus Brandenburger Wenjing Chu* Hendrik Ebbers* Char Howland* Tracy Kuhrt (Chair) Enrique Lacal* Diane Mueller* Venkatraman Ramakrishna Arun S M (Vice Chair) Peter Somogyvari Matthew Whitehead* *New members   View previous blog post Back to all blog posts View next blog post The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. [Tracy] With LF Decentralized Trust, I am excited to see the continued momentum of our existing projects and labs plus the expectation for new projects and labs to join the organization. keywords: decentralized; projects; tac; technical; trust cache: www-introducing-the-2025-technical-advisory-council-members-and-outlook.html plain text: www-introducing-the-2025-technical-advisory-council-members-and-outlook.txt item: #3004 of 3327 id: www-introducing-the-2025-technical-advisory-council-members-and-outlook?hs_amp=true author: www title: www-introducing-the-2025-technical-advisory-council-members-and-outlook?hs_amp=true date: None words: 1587 flesch: 38 summary: [Tracy] With LF Decentralized Trust, I am excited to see the continued momentum of our existing projects and labs plus the expectation for new projects and labs to join the organization. I attended the Maintainers Summit in San Francisco in October, and I was happy to see many new faces that have entered the community – both those who have recently joined existing projects as well as people who were looking to contribute new projects and labs to LF Decentralized Trust. keywords: decentralized; projects; trust cache: www-introducing-the-2025-technical-advisory-council-members-and-outlook?hs_amp=true.html plain text: www-introducing-the-2025-technical-advisory-council-members-and-outlook?hs_amp=true.txt item: #3005 of 3327 id: www-introducing-the-social-impact-ecosystem-blog-series-from-hyperledgers-social-impact-special-interest-group author: www title: www-introducing-the-social-impact-ecosystem-blog-series-from-hyperledgers-social-impact-special-interest-group date: None words: 1148 flesch: 45 summary: Highlights include talks by Christina Lomazzo from UNICEF presenting on the UNICEF Innovation Fund and projects that UNICEF national offices in Colombia and Afghanistan have developed leveraging blockchain technology;  Matthew Davie from microlending platform Kiva discussing how the Kiva protocol leverages blockchain to promote financial inclusion;  Shawn Wilborne, Lid Vizion cofounder and SIG member, sharing how his organization helps public and private sector organizations manage waste to reduce contamination; and  Tamara Dull of AWS presentingon how the Animal ID initiative enables their customers to track animals from birth to death. We are excited to announce the launch of our blog post series “Social Impact Ecosystem,” which will feature blog posts from community members, guest writers and beyond on the various ways in which blockchain can be leveraged for social impact. keywords: blockchain; blog; impact; sig cache: www-introducing-the-social-impact-ecosystem-blog-series-from-hyperledgers-social-impact-special-interest-group.html plain text: www-introducing-the-social-impact-ecosystem-blog-series-from-hyperledgers-social-impact-special-interest-group.txt item: #3006 of 3327 id: www-introducing-the-telecom-decentralized-identity-network-tdidn-a-new-approach-to-security-efficiency-and-privacy author: www title: www-introducing-the-telecom-decentralized-identity-network-tdidn-a-new-approach-to-security-efficiency-and-privacy date: None words: 1025 flesch: 34 summary: TDIDN delivers a comprehensive architecture for implementing DIDs on a blockchain, through two related projects from the Hyperledger Foundation:  Hyperledger Aries provides a complete toolkit for building decentralized identity solutions. This solution brief introduces the groundbreaking concept of a Telecom Decentralized Identity Network (TDIDN), a new way to improve identity management using decentralized identifiers (DID) and blockchain. keywords: decentralized; identity; tdidn; telecom cache: www-introducing-the-telecom-decentralized-identity-network-tdidn-a-new-approach-to-security-efficiency-and-privacy.html plain text: www-introducing-the-telecom-decentralized-identity-network-tdidn-a-new-approach-to-security-efficiency-and-privacy.txt item: #3007 of 3327 id: www-introducing-the-telecom-decentralized-identity-network-tdidn-a-new-approach-to-security-efficiency-and-privacy?hs_amp=true author: www title: www-introducing-the-telecom-decentralized-identity-network-tdidn-a-new-approach-to-security-efficiency-and-privacy?hs_amp=true date: None words: 696 flesch: 39 summary: Blog | LF Decentralized Trust Introducing the Telecom Decentralized Identity Network (TDIDN) Written by Hyperledger Telecom SIG | Apr 25, 2024 4:00:00 PM This solution brief introduces the groundbreaking concept of a Telecom Decentralized Identity Network (TDIDN), a new way to improve identity management using decentralized identifiers (DID) and blockchain. TDIDN delivers a comprehensive architecture for implementing DIDs on a blockchain, through two related projects from the Hyperledger Foundation:  Hyperledger Aries provides a complete toolkit for building decentralized identity solutions. keywords: identity; telecom cache: www-introducing-the-telecom-decentralized-identity-network-tdidn-a-new-approach-to-security-efficiency-and-privacy?hs_amp=true.html plain text: www-introducing-the-telecom-decentralized-identity-network-tdidn-a-new-approach-to-security-efficiency-and-privacy?hs_amp=true.txt item: #3008 of 3327 id: www-investing-in-verifiable-credentials-technical-interoperability-and-open-source author: www title: www-investing-in-verifiable-credentials-technical-interoperability-and-open-source date: None words: 1242 flesch: 47 summary: We also are focused on the interoperability of Hyperledger Aries agents themselves, another key success metric.  Driving Adoption In BC we have a lot of technical skill in working with VCs and with Hyperledger Aries agents. keywords: digital; interoperability; source cache: www-investing-in-verifiable-credentials-technical-interoperability-and-open-source.html plain text: www-investing-in-verifiable-credentials-technical-interoperability-and-open-source.txt item: #3009 of 3327 id: www-iot-deployment-tutorial-part-i-deploying-hyperledger-besu-to-support-hardware-layer author: www title: www-iot-deployment-tutorial-part-i-deploying-hyperledger-besu-to-support-hardware-layer date: None words: 879 flesch: 44 summary: Setting up the blockchain, accounts and hardware node First of all, a Hyperledger Besu network should be hosted. I: Deploying Hyperledger Besu to Support Hardware Layer – Hyperledger Foundation 2025 keywords: besu; hardware; network cache: www-iot-deployment-tutorial-part-i-deploying-hyperledger-besu-to-support-hardware-layer.html plain text: www-iot-deployment-tutorial-part-i-deploying-hyperledger-besu-to-support-hardware-layer.txt item: #3010 of 3327 id: www-iot-deployment-tutorial-part-ii-deploying-hyperledger-besu-to-support-hardware-layer author: www title: www-iot-deployment-tutorial-part-ii-deploying-hyperledger-besu-to-support-hardware-layer date: None words: 944 flesch: 42 summary: Among the conditions, they can agree on some penalty for delayed delivery or that the parcel couldn’t be exposed to a temperature higher than some threshold longer than X minutes. Further, we go through the steps required to use the hardware signature (contained in the smart card) to sign the transaction, to configure the temperature sensor and measure the current value of the temperature, and, finally, to integrate all the parts into one program that will serve as “delivery starter” and “temperature measurement provider.” keywords: contract; delivery; tutorial; use cache: www-iot-deployment-tutorial-part-ii-deploying-hyperledger-besu-to-support-hardware-layer.html plain text: www-iot-deployment-tutorial-part-ii-deploying-hyperledger-besu-to-support-hardware-layer.txt item: #3011 of 3327 id: www-ipwe-launches-revolutionary-platform-and-deployment-of-25-million-patent-nfts-on-hybrid-casper-blockchain-and-hyperledger-fabric-network author: www title: www-ipwe-launches-revolutionary-platform-and-deployment-of-25-million-patent-nfts-on-hybrid-casper-blockchain-and-hyperledger-fabric-network date: None words: 1392 flesch: 30 summary: Blockchain Meets IP: How IPwe is Changing the Game with Hybrid Casper Blockchain and Hyperledger Fabric Network IPwe is leveraging blockchain technology to transform the IP landscape by tokenizing the majority of the world’s patents as patent NFTs, referred to as IPwe Digital Assets, representing the largest enterprise blockchain NFT deployment in history. Additionally, IPwe Digital Assets are populated with public data from leading patent datasets, providing IP owners with a transparent digital representation of asset ownership. keywords: blockchain; casper; hyperledger; ipwe; patent cache: www-ipwe-launches-revolutionary-platform-and-deployment-of-25-million-patent-nfts-on-hybrid-casper-blockchain-and-hyperledger-fabric-network.html plain text: www-ipwe-launches-revolutionary-platform-and-deployment-of-25-million-patent-nfts-on-hybrid-casper-blockchain-and-hyperledger-fabric-network.txt item: #3012 of 3327 id: www-ipwe-launches-revolutionary-platform-and-deployment-of-25-million-patent-nfts-on-hybrid-casper-blockchain-and-hyperledger-fabric-network?hs_amp=true author: www title: www-ipwe-launches-revolutionary-platform-and-deployment-of-25-million-patent-nfts-on-hybrid-casper-blockchain-and-hyperledger-fabric-network?hs_amp=true date: None words: 1081 flesch: 33 summary: Blockchain Meets IP: How IPwe is Changing the Game with Hybrid Casper Blockchain and Hyperledger Fabric Network IPwe is leveraging blockchain technology to transform the IP landscape by tokenizing the majority of the world’s patents as patent NFTs, referred to as IPwe Digital Assets, representing the largest enterprise blockchain NFT deployment in history. Watch IPwe, Casper Labs, and Hyperledger Foundation announce the world’s largest enterprise blockchain deployment at the Blockchain Hub in Davos Hybrid Casper Blockchain and Hyperledger Fabric Network In September 2022, Casper Labs and IPwe developed and launched a dynamic NFT blockchain solution, IPwe Digital Assets. keywords: blockchain; hyperledger; ipwe cache: www-ipwe-launches-revolutionary-platform-and-deployment-of-25-million-patent-nfts-on-hybrid-casper-blockchain-and-hyperledger-fabric-network?hs_amp=true.html plain text: www-ipwe-launches-revolutionary-platform-and-deployment-of-25-million-patent-nfts-on-hybrid-casper-blockchain-and-hyperledger-fabric-network?hs_amp=true.txt item: #3013 of 3327 id: www-jacqueline-zhang author: www title: www-jacqueline-zhang date: None words: 517 flesch: 18 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-jacqueline-zhang.html plain text: www-jacqueline-zhang.txt item: #3014 of 3327 id: www-jessica-rampen author: www title: www-jessica-rampen date: None words: 1316 flesch: 36 summary: Next page > Submit a blog Blog guidelines RSS Introducing Hyperledger FireFly, a Multi-Party System for Enterprise Data Flows We are very excited to announce the newest Hyperledger project, Hyperledger FireFly. With a few years behind... Read More Jessica Rampen | Dec 15, 2020 Blog | Finance An innovative blockchain solution powered by Hyperledger Fabric helps banks implement DeFI services in days Digitization is a megatrend that has already transformed many industries – and now it’s banking’s turn. keywords: blockchain; blog; hyperledger; jessica; rampen cache: www-jessica-rampen.html plain text: www-jessica-rampen.txt item: #3015 of 3327 id: www-jordan-roberts-and-koushik-gavini-gala author: www title: www-jordan-roberts-and-koushik-gavini-gala date: None words: 532 flesch: 22 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Hyperledger Fabric GalaChain: Leveraging Hyperledger Fabric to Create the Ultimate Entertainment Blockchain keywords: blog; decentralized; hyperledger; technologies cache: www-jordan-roberts-and-koushik-gavini-gala.html plain text: www-jordan-roberts-and-koushik-gavini-gala.txt item: #3016 of 3327 id: www-just-introduced-refreshed-hyperledger-project-logos author: www title: www-just-introduced-refreshed-hyperledger-project-logos date: None words: 504 flesch: 33 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger AnonCreds | Hyperledger Aries | Project: Hyperledger Indy | Staff Corner | Hyperledger Fabric Just Introduced: Refreshed Hyperledger Project Logos Daniela Barbosa, Executive Director at Hyperledger Foundation and General Manager, Blockchain and Identity for the Linux Foundation | Apr 23, 2024 Last year, we introduced a new look for Hyperledger Foundation that fit with our increasingly mature market and ecosystem as well as our enterprise audience. For some projects, namely Hyperledger AnonCreds, Hyperledger Aries, Hyperledger Fabric and Hyperledger Indy, the community has opted to redesign their logos. keywords: foundation; hyperledger; logos cache: www-just-introduced-refreshed-hyperledger-project-logos.html plain text: www-just-introduced-refreshed-hyperledger-project-logos.txt item: #3017 of 3327 id: www-just-introduced-refreshed-hyperledger-project-logos?hs_amp=true author: www title: www-just-introduced-refreshed-hyperledger-project-logos?hs_amp=true date: None words: 180 flesch: 49 summary: Just Introduced: Refreshed Hyperledger Project Logos Blog | LF Decentralized Trust Just Introduced: Refreshed Hyperledger Project Logos Written by Daniela Barbosa, Executive Director at Hyperledger Foundation and General Manager, Blockchain and Identity for the Linux Foundation | Apr 23, 2024 2:18:48 PM Last year, we introduced a new look for Hyperledger Foundation that fit with our increasingly mature market and ecosystem as well as our enterprise audience. For some projects, namely Hyperledger AnonCreds, Hyperledger Aries, Hyperledger Fabric and Hyperledger Indy, the community has opted to redesign their logos. keywords: hyperledger cache: www-just-introduced-refreshed-hyperledger-project-logos?hs_amp=true.html plain text: www-just-introduced-refreshed-hyperledger-project-logos?hs_amp=true.txt item: #3018 of 3327 id: www-karen-ottoni-senior-director-of-ecosystem-and-strategic-initiatives-hyperledger-foundation author: www title: www-karen-ottoni-senior-director-of-ecosystem-and-strategic-initiatives-hyperledger-foundation date: None words: 530 flesch: 13 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Finance | Staff Corner The Case for Open Development as the Foundation for Central Bank Digital Currencies Introduction Read More Karen Ottoni, Senior Director of Ecosystem and Strategic Initiatives, Hyperledger Foundation | Nov 1, 2023 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; foundation; hyperledger cache: www-karen-ottoni-senior-director-of-ecosystem-and-strategic-initiatives-hyperledger-foundation.html plain text: www-karen-ottoni-senior-director-of-ecosystem-and-strategic-initiatives-hyperledger-foundation.txt item: #3019 of 3327 id: www-karim-stekelenburg-hyperledger-aries-maintainer-animo-solutions-co-founder author: www title: www-karim-stekelenburg-hyperledger-aries-maintainer-animo-solutions-co-founder date: None words: 593 flesch: 18 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Read More Karim Stekelenburg, Hyperledger Aries Maintainer - Animo Solutions Co-Founder | Sep 7, 2023 Hyperledger Aries Introducing Hyperledger Aries Framework JavaScript 0.2.0 About half a year before we started Animo Solutions, my co-founders keywords: aries; blog; decentralized; hyperledger cache: www-karim-stekelenburg-hyperledger-aries-maintainer-animo-solutions-co-founder.html plain text: www-karim-stekelenburg-hyperledger-aries-maintainer-animo-solutions-co-founder.txt item: #3020 of 3327 id: www-ken-ebert-and-keela-rose-shatzkin-co-chairs-cardea-working-group author: www title: www-ken-ebert-and-keela-rose-shatzkin-co-chairs-cardea-working-group date: None words: 556 flesch: 19 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Hyperledger Aries | Project: Hyperledger Indy | Decentralized Identity | Labs | Health and Public Sector Cardea, a privacy preserving open-source ecosystem for verifying health data, joins Hyperledger Labs Cardea, a complete open-source verifiable credential ecosystem for sharing health information in a... keywords: blog; decentralized; hyperledger; technologies cache: www-ken-ebert-and-keela-rose-shatzkin-co-chairs-cardea-working-group.html plain text: www-ken-ebert-and-keela-rose-shatzkin-co-chairs-cardea-working-group.txt item: #3021 of 3327 id: www-keynote-sneak-peek-for-hyperledger-global-forum-see-whos-speaking author: www title: www-keynote-sneak-peek-for-hyperledger-global-forum-see-whos-speaking date: None words: 675 flesch: 37 summary: Hyperledger Global Forum will cut through the hype and focus on adoption. Live Demos & Roadmaps: Get an inside look at live demos and roadmaps showing how the biggest names in financial services, healthcare, supply chain and more are integrating Hyperledger technologies for commercial, production deployments. keywords: forum; global; hyperledger; technologies cache: www-keynote-sneak-peek-for-hyperledger-global-forum-see-whos-speaking.html plain text: www-keynote-sneak-peek-for-hyperledger-global-forum-see-whos-speaking.txt item: #3022 of 3327 id: www-kiva-protocol-built-on-hyperledger-indy-ursa-and-aries-powers-africas-first-decentralized-national-id-system author: www title: www-kiva-protocol-built-on-hyperledger-indy-ursa-and-aries-powers-africas-first-decentralized-national-id-system date: None words: 937 flesch: 34 summary: While all three projects are closely related, each has a distinct mandate: Hyperledger Indy is a distributed ledger purpose-built for decentralized ID with transferable, private, and secure credentials; Hyperledger Aries is infrastructure that supports interactions between peers and between blockchains and other DLTs; and Hyperledger Ursa is a modular, flexible library that enables developers to share time-tested and secure cryptography. Kiva Protocol is built using Hyperledger Indy, Aries, and Ursa, and as implemented in Sierra Leone, allows citizens to perform electronic Know Your Customer (eKYC) verifications in about 11 seconds, using just their national ID number and a fingerprint. keywords: decentralized; hyperledger; kiva; protocol cache: www-kiva-protocol-built-on-hyperledger-indy-ursa-and-aries-powers-africas-first-decentralized-national-id-system.html plain text: www-kiva-protocol-built-on-hyperledger-indy-ursa-and-aries-powers-africas-first-decentralized-national-id-system.txt item: #3023 of 3327 id: www-kiva-protocol-built-on-hyperledger-indy-ursa-and-aries-powers-africas-first-decentralized-national-id-system?hs_amp=true author: www title: www-kiva-protocol-built-on-hyperledger-indy-ursa-and-aries-powers-africas-first-decentralized-national-id-system?hs_amp=true date: None words: 625 flesch: 41 summary: While all three projects are closely related, each has a distinct mandate: Hyperledger Indy is a distributed ledger purpose-built for decentralized ID with transferable, private, and secure credentials; Hyperledger Aries is infrastructure that supports interactions between peers and between blockchains and other DLTs; and Hyperledger Ursa is a modular, flexible library that enables developers to share time-tested and secure cryptography. Kiva Protocol is built using Hyperledger Indy, Aries, and Ursa, and as implemented in Sierra Leone, allows citizens to perform electronic Know Your Customer (eKYC) verifications in about 11 seconds, using just their national ID number and a fingerprint. keywords: hyperledger; kiva cache: www-kiva-protocol-built-on-hyperledger-indy-ursa-and-aries-powers-africas-first-decentralized-national-id-system?hs_amp=true.html plain text: www-kiva-protocol-built-on-hyperledger-indy-ursa-and-aries-powers-africas-first-decentralized-national-id-system?hs_amp=true.txt item: #3024 of 3327 id: www-krypc-builds-award-winning-taxchain-to-streamline-eu-tax-forms-using-hyperledger-fabric author: www title: www-krypc-builds-award-winning-taxchain-to-streamline-eu-tax-forms-using-hyperledger-fabric date: None words: 911 flesch: 52 summary: KrypC builds award-winning taXchain to streamline EU tax forms using Hyperledger Fabric – Hyperledger Foundation 2025 How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Case Study | Finance KrypC builds award-winning taXchain to streamline EU tax forms using Hyperledger Fabric Hyperledger | Jan 31, 2023 Read the full case study here. keywords: case; forms; foundation; hyperledger cache: www-krypc-builds-award-winning-taxchain-to-streamline-eu-tax-forms-using-hyperledger-fabric.html plain text: www-krypc-builds-award-winning-taxchain-to-streamline-eu-tax-forms-using-hyperledger-fabric.txt item: #3025 of 3327 id: www-krypc-builds-award-winning-taxchain-to-streamline-eu-tax-forms-using-hyperledger-fabric?hs_amp=true author: www title: www-krypc-builds-award-winning-taxchain-to-streamline-eu-tax-forms-using-hyperledger-fabric?hs_amp=true date: None words: 600 flesch: 64 summary: KrypC builds award-winning taXchain to streamline EU tax forms using Hyperledger Fabric – Hyperledger Foundation Blog | LF Decentralized Trust KrypC builds award-winning taXchain to streamline EU tax forms using Hyperledger Fabric – Hyperledger Foundation Written by Hyperledger | Jan 31, 2023 6:16:00 AM Read the full case study here. Their aim was to  Prove that digitized tax forms save time and money Build an open, flexible platform that can support many partners Showcase the network to companies across the EU They opted for Hyperledger Fabric as the platform because it is built for permissioned networks, with good security and privacy, and strong community support. keywords: forms; hyperledger cache: www-krypc-builds-award-winning-taxchain-to-streamline-eu-tax-forms-using-hyperledger-fabric?hs_amp=true.html plain text: www-krypc-builds-award-winning-taxchain-to-streamline-eu-tax-forms-using-hyperledger-fabric?hs_amp=true.txt item: #3026 of 3327 id: www-kshitij-roodkee author: www title: www-kshitij-roodkee date: None words: 520 flesch: 10 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Mentorship Program | Hyperledger Iroha Hyperledger Mentorship Spotlight: Iroha 2 Blockchain Explorer Engaging in the Iroha 2 Blockchain Explorer project through the Hyperledger Mentorship project has... Read More Kshitij Roodkee | Feb 20, 2024 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; project cache: www-kshitij-roodkee.html plain text: www-kshitij-roodkee.txt item: #3027 of 3327 id: www-ku23 author: www title: www-ku23 date: None words: 1335 flesch: 43 summary: This protocol—here called KU23—is tailored to allow for both high-throughput and low-latency signature generation in key management networks, as operated by Dfns, under the assumption that a majority of the servers in the network remain uncompromised.  This blog, based on my talk at the DeCompute 2024 conference, explains key management networks in general as well as the high-level design of this new MPC protocol. keywords: key; ku23; management; signature cache: www-ku23.html plain text: www-ku23.txt item: #3028 of 3327 id: www-labs author: www title: www-labs date: None words: 1351 flesch: 27 summary: | Feb 2, 2022 Labs | Interoperability Meet FireFly, one of the new Hyperledger Labs taking on cross-chain and off-chain operations As enterprises and organizations increase their adoption and deployment of blockchain technology and networks, the overall complexity of systems are growing exponentially. Read More Hyperledger | Mar 24, 2022 Labs Performance SandBox, a new Hyperledger Lab, is a test ground for blockchain performance research Meet Performance SandBox, a new Hyperledger Lab for testing new research to boost performance of blockchain platforms. keywords: community; decentralized; hyperledger; interoperability; labs; project cache: www-labs.html plain text: www-labs.txt item: #3029 of 3327 id: www-lacchain-introduces-permissioned-public-blockchain-ecosystem-built-on-hyperledger-besu-to-latin-america author: www title: www-lacchain-introduces-permissioned-public-blockchain-ecosystem-built-on-hyperledger-besu-to-latin-america date: None words: 729 flesch: 41 summary: Permissioned public networks—combining the benefits of the other blockchains without their drawbacks—seemed like the answer. LACChain introduces permissioned public blockchain ecosystem built on Hyperledger Besu to Latin America – Hyperledger Foundation 2025 keywords: case; decentralized; foundation cache: www-lacchain-introduces-permissioned-public-blockchain-ecosystem-built-on-hyperledger-besu-to-latin-america.html plain text: www-lacchain-introduces-permissioned-public-blockchain-ecosystem-built-on-hyperledger-besu-to-latin-america.txt item: #3030 of 3327 id: www-lacchain-introduces-permissioned-public-blockchain-ecosystem-built-on-hyperledger-besu-to-latin-america?hs_amp=true author: www title: www-lacchain-introduces-permissioned-public-blockchain-ecosystem-built-on-hyperledger-besu-to-latin-america?hs_amp=true date: None words: 416 flesch: 49 summary: Permissioned public networks—combining the benefits of the other blockchains without their drawbacks—seemed like the answer. LACChain introduces permissioned public blockchain ecosystem built on Hyperledger Besu to Latin America – Hyperledger Foundation Blog | LF Decentralized Trust LACChain introduces permissioned public blockchain ecosystem built on Hyperledger Besu to Latin America – Hyperledger Foundation Written by Hyperledger | Oct 12, 2022 10:00:00 AM Read the full case study here. keywords: hyperledger cache: www-lacchain-introduces-permissioned-public-blockchain-ecosystem-built-on-hyperledger-besu-to-latin-america?hs_amp=true.html plain text: www-lacchain-introduces-permissioned-public-blockchain-ecosystem-built-on-hyperledger-besu-to-latin-america?hs_amp=true.txt item: #3031 of 3327 id: www-leanne-kemp-founder-and-ceo-everledger author: www title: www-leanne-kemp-founder-and-ceo-everledger date: None words: 536 flesch: 15 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Supply Chain | Hyperledger Fabric How Hyperledger Fabric Helped Everledger Transform a Market and Blaze a Trail for Others to Follow From the earliest days of blockchain technologies, Everledger has seen its potential to... Read More Leanne Kemp, Founder and CEO, Everledger | Sep 25, 2023 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-leanne-kemp-founder-and-ceo-everledger.html plain text: www-leanne-kemp-founder-and-ceo-everledger.txt item: #3032 of 3327 id: www-learn-the-fundamentals-of-self-sovereign-identity-in-free-online-training-course author: www title: www-learn-the-fundamentals-of-self-sovereign-identity-in-free-online-training-course date: None words: 827 flesch: 35 summary: Upon completion, participants will be able to have informed business discussions around digital identity, and particularly self-sovereign identity, with a good understanding about how identity systems work and influence our lives. We want to make it easier for companies to implement SSI for the benefit of their users, so Linux Foundation Training & Certification has announced a new upcoming online training course, Getting Started with Self-Sovereign Identity (LFS178x). keywords: decentralized; foundation; identity; training cache: www-learn-the-fundamentals-of-self-sovereign-identity-in-free-online-training-course.html plain text: www-learn-the-fundamentals-of-self-sovereign-identity-in-free-online-training-course.txt item: #3033 of 3327 id: www-learning-materials-and-development-working-group-mentorship-project-global-scouting-for-dlt-blockchain-educational-opportunities author: www title: www-learning-materials-and-development-working-group-mentorship-project-global-scouting-for-dlt-blockchain-educational-opportunities date: None words: 669 flesch: 43 summary: View previous blog post Back to all blog posts View next blog post The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. LF Decentralized Trust is a trademark of The Linux Foundation. keywords: decentralized; foundation; project cache: www-learning-materials-and-development-working-group-mentorship-project-global-scouting-for-dlt-blockchain-educational-opportunities.html plain text: www-learning-materials-and-development-working-group-mentorship-project-global-scouting-for-dlt-blockchain-educational-opportunities.txt item: #3034 of 3327 id: www-ledger-leopard-uses-hyperledger-besu-to-power-a-start-ups-new-digital-approach-to-rti-tracking author: www title: www-ledger-leopard-uses-hyperledger-besu-to-power-a-start-ups-new-digital-approach-to-rti-tracking date: None words: 873 flesch: 52 summary: Once a company registers in RTI Dashboard, they can invite their partners to join with a link. “Take one supplier and use RTI Dashboard for all transactions. keywords: dashboard; decentralized; hyperledger; rti cache: www-ledger-leopard-uses-hyperledger-besu-to-power-a-start-ups-new-digital-approach-to-rti-tracking.html plain text: www-ledger-leopard-uses-hyperledger-besu-to-power-a-start-ups-new-digital-approach-to-rti-tracking.txt item: #3035 of 3327 id: www-ledger-leopard-uses-hyperledger-besu-to-power-a-start-ups-new-digital-approach-to-rti-tracking?hs_amp=true author: www title: www-ledger-leopard-uses-hyperledger-besu-to-power-a-start-ups-new-digital-approach-to-rti-tracking?hs_amp=true date: None words: 565 flesch: 65 summary: Ledger Leopard Uses Hyperledger Besu to Power a Scale-Up’s New Digital Approach to RTI Tracking – Hyperledger Foundation Blog | LF Decentralized Trust Ledger Leopard Uses Hyperledger Besu to Power a Scale-Up’s New Digital Approach to RTI Tracking – Hyperledger Foundation Written by Hyperledger | Oct 1, 2021 12:27:47 PM Most of the products we use and consume every day are transported on Returnable Transport Items (RTI). Once a company registers in RTI Dashboard, they can invite their partners to join with a link. keywords: hyperledger; rti cache: www-ledger-leopard-uses-hyperledger-besu-to-power-a-start-ups-new-digital-approach-to-rti-tracking?hs_amp=true.html plain text: www-ledger-leopard-uses-hyperledger-besu-to-power-a-start-ups-new-digital-approach-to-rti-tracking?hs_amp=true.txt item: #3036 of 3327 id: www-lessons-learned-from-hyperledger-fabric-poc-projects author: www title: www-lessons-learned-from-hyperledger-fabric-poc-projects date: None words: 979 flesch: 41 summary: A valuable benefit of being a part of the Hyperledger community is the opportunity to hear from members about their experiences “in the field” using Hyperledger technologies for PoCs, pilots and production deployments. Given IntellectEU’s announcement today about the release of Catalyst, the first platform to integrate traditional infrastructures with multiple blockchain networks including networks built with Hyperledger Fabric, we decided to share the recent PoC using Hyperledger Fabric and Catalyst we discussed with Gartner. keywords: case; hyperledger; poc; use cache: www-lessons-learned-from-hyperledger-fabric-poc-projects.html plain text: www-lessons-learned-from-hyperledger-fabric-poc-projects.txt item: #3037 of 3327 id: www-lf-decentralized-trust author: www title: www-lf-decentralized-trust date: None words: 660 flesch: 25 summary: Read More LF Decentralized Trust | Apr 15, 2025 Developer Showcase | Besu Developer Showcase Series: Bruno Nascimento, Staff Engineer, Cheesecake Labs Back to our Developer Showcase Series to learn what developers in the real world are doing with LF Decentralized Trust technologies. Read More LF Decentralized Trust | Mar 17, 2025 Governance Introducing the 2025 Technical Advisory Council Members and Outlook To kick off 2025, we welcome a new Technical Advisory Council (TAC), the first elected under the charter of LF Decentralized Trust. keywords: decentralized; hyperledger; technologies; trust cache: www-lf-decentralized-trust.html plain text: www-lf-decentralized-trust.txt item: #3038 of 3327 id: www-lf-decentralized-trust-a-bigger-tent-for-projects-labs-and-communities author: www title: www-lf-decentralized-trust-a-bigger-tent-for-projects-labs-and-communities date: None words: 821 flesch: 41 summary: Our organization will be an umbrella for members and communities to foster innovation and collaboration, supporting new projects and labs and advancing existing ones. In case you missed it, the Linux Foundation recently announced the intent to form LF Decentralized Trust, a new bigger umbrella organization where we will gather and grow an expanded community and portfolio of technologies to deliver the transparency, reliability, security, and efficiency needed to successfully upgrade critical systems worldwide. keywords: decentralized; labs; trust cache: www-lf-decentralized-trust-a-bigger-tent-for-projects-labs-and-communities.html plain text: www-lf-decentralized-trust-a-bigger-tent-for-projects-labs-and-communities.txt item: #3039 of 3327 id: www-lf-decentralized-trust-a-bigger-tent-for-projects-labs-and-communities?hs_amp=true author: www title: www-lf-decentralized-trust-a-bigger-tent-for-projects-labs-and-communities?hs_amp=true date: None words: 510 flesch: 50 summary: LF Decentralized Trust: A Bigger Tent for Projects, Labs, Members, and Communities Blog | LF Decentralized Trust LF Decentralized Trust: A Bigger Tent for Projects, Labs, Members, and Communities Written by Daniela Barbosa, Executive Director at Hyperledger Foundation and General Manager, Blockchain and Identity for the Linux Foundation | Jul 8, 2024 7:02:06 PM In case you missed it, the Linux Foundation recently announced the intent to form LF Decentralized Trust, a new bigger umbrella organization where we will gather and grow an expanded community and portfolio of technologies to deliver the transparency, reliability, security, and efficiency needed to successfully upgrade critical systems worldwide. keywords: decentralized cache: www-lf-decentralized-trust-a-bigger-tent-for-projects-labs-and-communities?hs_amp=true.html plain text: www-lf-decentralized-trust-a-bigger-tent-for-projects-labs-and-communities?hs_amp=true.txt item: #3040 of 3327 id: www-lf-decentralized-trust-european-chapter-members author: www title: www-lf-decentralized-trust-european-chapter-members date: None words: 532 flesch: 16 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Read More LF Decentralized Trust European Chapter Members | Apr 24, 2025 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; trust cache: www-lf-decentralized-trust-european-chapter-members.html plain text: www-lf-decentralized-trust-european-chapter-members.txt item: #3041 of 3327 id: www-lf-decentralized-trust-mentorship-spotlight-cc-tools-support-for-fabric-private-chaincode author: www title: www-lf-decentralized-trust-mentorship-spotlight-cc-tools-support-for-fabric-private-chaincode date: None words: 1194 flesch: 41 summary: To understand both projects, I performed intense experimentation with FPC and CC-Tools chaincodes, played with various configurations, and traced the output that resulted from each change. CC-Tools, an LF Decentralized Trust Lab, is designed to streamline this process by providing a simplified, user-friendly framework for chaincode development. keywords: decentralized; project; tools cache: www-lf-decentralized-trust-mentorship-spotlight-cc-tools-support-for-fabric-private-chaincode.html plain text: www-lf-decentralized-trust-mentorship-spotlight-cc-tools-support-for-fabric-private-chaincode.txt item: #3042 of 3327 id: www-lf-decentralized-trust-mentorship-spotlight-cc-tools-support-for-fabric-private-chaincode?hs_amp=true author: www title: www-lf-decentralized-trust-mentorship-spotlight-cc-tools-support-for-fabric-private-chaincode?hs_amp=true date: None words: 878 flesch: 47 summary: To understand both projects, I performed intense experimentation with FPC and CC-Tools chaincodes, played with various configurations, and traced the output that resulted from each change. We plan to extend the functionalities provided by FPC and integrate them with CC-Tools so developers can leverage the full feature set of both projects without any limitations or drawbacks. keywords: tools cache: www-lf-decentralized-trust-mentorship-spotlight-cc-tools-support-for-fabric-private-chaincode?hs_amp=true.html plain text: www-lf-decentralized-trust-mentorship-spotlight-cc-tools-support-for-fabric-private-chaincode?hs_amp=true.txt item: #3043 of 3327 id: www-lf-decentralized-trust-mentorship-spotlight-vs-code-debugger-plugin-for-hyperledger-fabric-chaincode author: www title: www-lf-decentralized-trust-mentorship-spotlight-vs-code-debugger-plugin-for-hyperledger-fabric-chaincode date: None words: 1087 flesch: 34 summary: Throughout the mentorship, I had the opportunity to work on a tool that enhances the debugging experience for Hyperledger Fabric developers, making it easier to inspect chaincode execution in real time. By combining these elements, we built a tool that significantly enhances the debugging workflow for Hyperledger Fabric developers, making it easier to identify and resolve issues in smart contracts. keywords: chaincode; decentralized; fabric; hyperledger cache: www-lf-decentralized-trust-mentorship-spotlight-vs-code-debugger-plugin-for-hyperledger-fabric-chaincode.html plain text: www-lf-decentralized-trust-mentorship-spotlight-vs-code-debugger-plugin-for-hyperledger-fabric-chaincode.txt item: #3044 of 3327 id: www-lf-decentralized-trust-mentorship-spotlight-vs-code-debugger-plugin-for-hyperledger-fabric-chaincode?hs_amp=true author: www title: www-lf-decentralized-trust-mentorship-spotlight-vs-code-debugger-plugin-for-hyperledger-fabric-chaincode?hs_amp=true date: None words: 773 flesch: 37 summary: Throughout the mentorship, I had the opportunity to work on a tool that enhances the debugging experience for Hyperledger Fabric developers, making it easier to inspect chaincode execution in real time. By combining these elements, we built a tool that significantly enhances the debugging workflow for Hyperledger Fabric developers, making it easier to identify and resolve issues in smart contracts. keywords: chaincode; fabric; hyperledger cache: www-lf-decentralized-trust-mentorship-spotlight-vs-code-debugger-plugin-for-hyperledger-fabric-chaincode?hs_amp=true.html plain text: www-lf-decentralized-trust-mentorship-spotlight-vs-code-debugger-plugin-for-hyperledger-fabric-chaincode?hs_amp=true.txt item: #3045 of 3327 id: www-lf-decentralized-trusts-hyperledger-indy-on-besu-joins-the-didindy-method-six-months-of-progress author: www title: www-lf-decentralized-trusts-hyperledger-indy-on-besu-joins-the-didindy-method-six-months-of-progress date: None words: 1471 flesch: 30 summary: Why Hyperledger Indy on Besu? Since it was introduced in 2017, Hyperledger Indy has been foundational in the development of decentralized identity. These identifiers leverage Besu’s architecture to provide enhanced capabilities for managing decentralized identities.  keywords: besu; decentralized; hyperledger; identity; indy; ssi cache: www-lf-decentralized-trusts-hyperledger-indy-on-besu-joins-the-didindy-method-six-months-of-progress.html plain text: www-lf-decentralized-trusts-hyperledger-indy-on-besu-joins-the-didindy-method-six-months-of-progress.txt item: #3046 of 3327 id: www-lf-decentralized-trusts-hyperledger-indy-on-besu-joins-the-didindy-method-six-months-of-progress?hs_amp=true author: www title: www-lf-decentralized-trusts-hyperledger-indy-on-besu-joins-the-didindy-method-six-months-of-progress?hs_amp=true date: None words: 1155 flesch: 32 summary: Why Hyperledger Indy on Besu? Since it was introduced in 2017, Hyperledger Indy has been foundational in the development of decentralized identity. These identifiers leverage Besu’s architecture to provide enhanced capabilities for managing decentralized identities.  keywords: besu; decentralized; identity; indy cache: www-lf-decentralized-trusts-hyperledger-indy-on-besu-joins-the-didindy-method-six-months-of-progress?hs_amp=true.html plain text: www-lf-decentralized-trusts-hyperledger-indy-on-besu-joins-the-didindy-method-six-months-of-progress?hs_amp=true.txt item: #3047 of 3327 id: www-localtrail-takes-on-farm-to-table-supply-chain-with-hyperledger-fabric-and-composer author: www title: www-localtrail-takes-on-farm-to-table-supply-chain-with-hyperledger-fabric-and-composer date: None words: 980 flesch: 42 summary: To build the solution, the team used Hyperledger Fabric, Hyperledger Composer and Tieron’s Chainpoint Node API. “For the server-side blockchain implementation we chose Hyperledger Composer. keywords: chain; hyperledger; localtrail; supply cache: www-localtrail-takes-on-farm-to-table-supply-chain-with-hyperledger-fabric-and-composer.html plain text: www-localtrail-takes-on-farm-to-table-supply-chain-with-hyperledger-fabric-and-composer.txt item: #3048 of 3327 id: www-localtrail-takes-on-farm-to-table-supply-chain-with-hyperledger-fabric-and-composer?hs_amp=true author: www title: www-localtrail-takes-on-farm-to-table-supply-chain-with-hyperledger-fabric-and-composer?hs_amp=true date: None words: 669 flesch: 50 summary: To build the solution, the team used Hyperledger Fabric, Hyperledger Composer and Tieron’s Chainpoint Node API. LocalTrail Takes On Farm-to-Table Supply Chain with Hyperledger Fabric and Composer – Hyperledger Foundation Blog | LF Decentralized Trust LocalTrail Takes On Farm-to-Table Supply Chain with Hyperledger Fabric and Composer – Hyperledger Foundation Written by Hyperledger | Jun 7, 2018 9:00:12 AM Pictured left to right: Brian Behlendorf, Rachel Black, Paco Garcia, Piers Powelesland, Saif Abu Hashish, Kevin Kim and Tracy Kuhrt With the goal of highlighting the value of blockchain beyond payments and digital currency, the Consensus 2018 Building Blocks Hackathon challenged teams of developers to tap into the robust programming capabilities of technologies to build applications with use cases in industries ranging from capital markets trading, food supply chain, digital rights management, new peer-to-peer insurance models, and the internet of things. keywords: hyperledger; localtrail; supply cache: www-localtrail-takes-on-farm-to-table-supply-chain-with-hyperledger-fabric-and-composer?hs_amp=true.html plain text: www-localtrail-takes-on-farm-to-table-supply-chain-with-hyperledger-fabric-and-composer?hs_amp=true.txt item: #3049 of 3327 id: www-lockness author: www title: www-lockness date: None words: 525 flesch: 17 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-lockness.html plain text: www-lockness.txt item: #3050 of 3327 id: www-lockness-a-new-home-for-trusted-key-cryptography author: www title: www-lockness-a-new-home-for-trusted-key-cryptography date: None words: 1703 flesch: 36 summary: Each library is fully documented, audited, and available for public use under the Apache 2.0 license, ensuring maximum transparency and security for cryptographic protocols. Vision: Making cryptographic protocols more accessible The creation of Lockness is driven by a clear and powerful vision: to make cryptographic protocols like MPC, TSS, DKG, ZKP and other novelties more accessible, auditable, secure, and performant. keywords: decentralized; key; lockness; mpc; project; protocols cache: www-lockness-a-new-home-for-trusted-key-cryptography.html plain text: www-lockness-a-new-home-for-trusted-key-cryptography.txt item: #3051 of 3327 id: www-lockness-a-new-home-for-trusted-key-cryptography?hs_amp=true author: www title: www-lockness-a-new-home-for-trusted-key-cryptography?hs_amp=true date: None words: 1393 flesch: 38 summary: In fact, MPC protocols tend to have fewer exploits each year compared to HSMs and are already used–sometimes unknowingly–by thousands of fintechs globally. The donation includes: `round-based`: A framework for writing MPC protocols, abstracting away the complexity of communication layers and providing reusable tools. keywords: key; lockness; mpc; protocols cache: www-lockness-a-new-home-for-trusted-key-cryptography?hs_amp=true.html plain text: www-lockness-a-new-home-for-trusted-key-cryptography?hs_amp=true.txt item: #3052 of 3327 id: www-lockness-is-alive author: www title: www-lockness-is-alive date: None words: 2114 flesch: 41 summary: In fact, MPC protocols tend to have fewer exploits each year compared to HSMs and are already used–sometimes unknowingly–by thousands of fintechs globally. The donation includes: `round-based`: A framework for writing MPC protocols, abstracting away the complexity of communication layers and providing reusable tools. keywords: cryptography; dfns; key; lockness; mpc; protocols; security cache: www-lockness-is-alive.html plain text: www-lockness-is-alive.txt item: #3053 of 3327 id: www-maintainers-from-four-hyperledger-projects-to-serve-as-code-contribution-guides-during-anitab-org-grace-hopper-celebration author: www title: www-maintainers-from-four-hyperledger-projects-to-serve-as-code-contribution-guides-during-anitab-org-grace-hopper-celebration date: None words: 779 flesch: 30 summary: Maintainers from these projects will on hand as guides to both the Hyperledger technologies and the code contribution process: Hyperledger Besu, an Ethereum client designed to be enterprise-friendly for both public and private permissioned network use cases; Hyperledger Cactus, a blockchain integration tool designed to allow users to securely integrate different blockchains;  Hyperledger Indy, a framework that provides tools, libraries, and reusable components for providing digital identities rooted on blockchains or other distributed ledgers; and Firefly, a Hyperledger Lab, a multiparty system for enterprise data flows, powered by blockchain. For those who want to challenge themselves or move deeper into a project, the Hyperledger Cactus list is broken down based on level of experience: Level 100 – Introductory Level 200 – Intermediate Level 300 – Advanced Level 400 – Expert keywords: code; foundation; hyperledger; projects cache: www-maintainers-from-four-hyperledger-projects-to-serve-as-code-contribution-guides-during-anitab-org-grace-hopper-celebration.html plain text: www-maintainers-from-four-hyperledger-projects-to-serve-as-code-contribution-guides-during-anitab-org-grace-hopper-celebration.txt item: #3054 of 3327 id: www-maintainers-from-four-hyperledger-projects-to-serve-as-code-contribution-guides-during-anitab-org-grace-hopper-celebration?hs_amp=true author: www title: www-maintainers-from-four-hyperledger-projects-to-serve-as-code-contribution-guides-during-anitab-org-grace-hopper-celebration?hs_amp=true date: None words: 466 flesch: 37 summary: Maintainers from these projects will on hand as guides to both the Hyperledger technologies and the code contribution process: Hyperledger Besu, an Ethereum client designed to be enterprise-friendly for both public and private permissioned network use cases; Hyperledger Cactus, a blockchain integration tool designed to allow users to securely integrate different blockchains;  Hyperledger Indy, a framework that provides tools, libraries, and reusable components for providing digital identities rooted on blockchains or other distributed ledgers; and Firefly, a Hyperledger Lab, a multiparty system for enterprise data flows, powered by blockchain. For those who want to challenge themselves or move deeper into a project, the Hyperledger Cactus list is broken down based on level of experience: Level 100 – Introductory Level 200 – Intermediate Level 300 – Advanced Level 400 – Expert keywords: hyperledger; projects cache: www-maintainers-from-four-hyperledger-projects-to-serve-as-code-contribution-guides-during-anitab-org-grace-hopper-celebration?hs_amp=true.html plain text: www-maintainers-from-four-hyperledger-projects-to-serve-as-code-contribution-guides-during-anitab-org-grace-hopper-celebration?hs_amp=true.txt item: #3055 of 3327 id: www-making-dynamic-consensus-more-dynamic author: www title: www-making-dynamic-consensus-more-dynamic date: None words: 1219 flesch: 47 summary: Moving the consensus functionality to a separate process allows consensus engines to be implemented in a variety of languages. The validator exposes the API for consensus engines as a set of protobuf messages sent over a network interface. keywords: api; consensus; engine; sawtooth cache: www-making-dynamic-consensus-more-dynamic.html plain text: www-making-dynamic-consensus-more-dynamic.txt item: #3056 of 3327 id: www-making-legal-contracts-smart author: www title: www-making-legal-contracts-smart date: None words: 1626 flesch: 41 summary: In contrast are smart legal contracts: legally binding agreements whose underlying logic is transformed through computation to enable automation, software connectivity, and dynamic business arrangements.   Cicero enables lawyers and business professionals to turn traditional, legally binding agreements into smart legal contracts. keywords: business; cicero; composer; hyperledger; template cache: www-making-legal-contracts-smart.html plain text: www-making-legal-contracts-smart.txt item: #3057 of 3327 id: www-making-legal-contracts-smart?hs_amp=true author: www title: www-making-legal-contracts-smart?hs_amp=true date: None words: 1315 flesch: 44 summary: In contrast are smart legal contracts: legally binding agreements whose underlying logic is transformed through computation to enable automation, software connectivity, and dynamic business arrangements.   Cicero enables lawyers and business professionals to turn traditional, legally binding agreements into smart legal contracts. keywords: cicero; hyperledger; template cache: www-making-legal-contracts-smart?hs_amp=true.html plain text: www-making-legal-contracts-smart?hs_amp=true.txt item: #3058 of 3327 id: www-matthew-whitehead-hyperledger-besu-maintainer-and-principal-engineer-at-kaleido author: www title: www-matthew-whitehead-hyperledger-besu-maintainer-and-principal-engineer-at-kaleido date: None words: 541 flesch: 12 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Besu | Finance and Business Technology Why Hyperledger Besu is a Top Choice for Financial Use Cases Hyperledger Besu has emerged as a preferred runtime for EVM-based financial initiatives worldwide.... keywords: blog; decentralized; hyperledger; technologies cache: www-matthew-whitehead-hyperledger-besu-maintainer-and-principal-engineer-at-kaleido.html plain text: www-matthew-whitehead-hyperledger-besu-maintainer-and-principal-engineer-at-kaleido.txt item: #3059 of 3327 id: www-md-tanjin-alam author: www title: www-md-tanjin-alam date: None words: 522 flesch: 17 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Mentorship Program | Project: Besu Hyperledger Mentorship Spotlight: Learning Tokens in Hyperledger Besu My Hyperledger Mentorship project has been a thrilling journey, filled with challenges, learnings,... keywords: blog; decentralized; hyperledger; project cache: www-md-tanjin-alam.html plain text: www-md-tanjin-alam.txt item: #3060 of 3327 id: www-meet-aries-agent-controller-a-new-hyperledger-lab author: www title: www-meet-aries-agent-controller-a-new-hyperledger-lab date: None words: 1187 flesch: 40 summary: Meet Aries Agent Controller, a New Hyperledger Lab 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger Aries | Hyperledger Bevel | Labs Meet Aries Agent Controller, a New Hyperledger Lab Superlogic, maintainers of Aries Agent Controller | Feb 29, 2024 A code base developed and contributed by Superlogic that facilitates deploying Hyperledger Aries agents in cloud environments is the latest Hyperledger lab. The lab is specifically tailored for the deployment of Hyperledger Aries agents using Kubernetes, with a specific focus on Amazon Web Services (AWS) through Amazon EKS. keywords: agent; aries; controller; hyperledger; lab cache: www-meet-aries-agent-controller-a-new-hyperledger-lab.html plain text: www-meet-aries-agent-controller-a-new-hyperledger-lab.txt item: #3061 of 3327 id: www-meet-aries-agent-controller-a-new-hyperledger-lab?hs_amp=true author: www title: www-meet-aries-agent-controller-a-new-hyperledger-lab?hs_amp=true date: None words: 871 flesch: 46 summary: Meet Aries Agent Controller, a New Hyperledger Lab Blog | LF Decentralized Trust Meet Aries Agent Controller, a New Hyperledger Lab Written by Superlogic, maintainers of Aries Agent Controller | Feb 29, 2024 3:55:42 PM A code base developed and contributed by Superlogic that facilitates deploying Hyperledger Aries agents in cloud environments is the latest Hyperledger lab. The lab is specifically tailored for the deployment of Hyperledger Aries agents using Kubernetes, with a specific focus on Amazon Web Services (AWS) through Amazon EKS. keywords: agent; hyperledger; lab cache: www-meet-aries-agent-controller-a-new-hyperledger-lab?hs_amp=true.html plain text: www-meet-aries-agent-controller-a-new-hyperledger-lab?hs_amp=true.txt item: #3062 of 3327 id: www-meet-firefly-one-the-new-hyperledger-labs-projects-taking-on-cross-chain-and-off-chain-operations author: www title: www-meet-firefly-one-the-new-hyperledger-labs-projects-taking-on-cross-chain-and-off-chain-operations date: None words: 1208 flesch: 44 summary: For (4), Hyperledger FireFly also provides a network map and registry that unifies all of the identity and bindings information needed. At a high level, enterprise blockchain use cases attempt to coordinate data flows and transactions across disparate, separately owned systems (ERP, mainframe, commerce, etc.). keywords: chain; cross; firefly; hyperledger; system cache: www-meet-firefly-one-the-new-hyperledger-labs-projects-taking-on-cross-chain-and-off-chain-operations.html plain text: www-meet-firefly-one-the-new-hyperledger-labs-projects-taking-on-cross-chain-and-off-chain-operations.txt item: #3063 of 3327 id: www-meet-firefly-one-the-new-hyperledger-labs-projects-taking-on-cross-chain-and-off-chain-operations?hs_amp=true author: www title: www-meet-firefly-one-the-new-hyperledger-labs-projects-taking-on-cross-chain-and-off-chain-operations?hs_amp=true date: None words: 898 flesch: 51 summary: For (4), Hyperledger FireFly also provides a network map and registry that unifies all of the identity and bindings information needed. At a high level, enterprise blockchain use cases attempt to coordinate data flows and transactions across disparate, separately owned systems (ERP, mainframe, commerce, etc.). keywords: chain; firefly; hyperledger cache: www-meet-firefly-one-the-new-hyperledger-labs-projects-taking-on-cross-chain-and-off-chain-operations?hs_amp=true.html plain text: www-meet-firefly-one-the-new-hyperledger-labs-projects-taking-on-cross-chain-and-off-chain-operations?hs_amp=true.txt item: #3064 of 3327 id: www-meet-hyperledger-solang-a-portable-solidity-compiler author: www title: www-meet-hyperledger-solang-a-portable-solidity-compiler date: None words: 1186 flesch: 44 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger Solang Meet Hyperledger Solang, a portable Solidity compiler Hyperledger | Sep 12, 2022 We are excited to announce that Solang has been accepted as the latest Hyperledger® project and has been renamed as Hyperledger Solang™. After tapping into those resources, Hyperledger Solang, a tool that enables smart contract portability, is now the newest Hyperledger project. keywords: hyperledger; project; solang; solidity cache: www-meet-hyperledger-solang-a-portable-solidity-compiler.html plain text: www-meet-hyperledger-solang-a-portable-solidity-compiler.txt item: #3065 of 3327 id: www-meet-robert-palatnick-the-new-chair-of-hyperledgers-governing-board author: www title: www-meet-robert-palatnick-the-new-chair-of-hyperledgers-governing-board date: None words: 1667 flesch: 44 summary: How is DTCC currently using Hyperledger technologies or how do you plan to? DTCC has been active in the Hyperledger community since its founding in January 2016, hosting the very first Hyperledger meet-up in our New Jersey office.   We know that Hyperledger projects are achieving code delivery goals, and we know that there has been tremendous response, in the form of Hyperledger code downloads, from the global community. keywords: board; code; community; governing; hyperledger; technology cache: www-meet-robert-palatnick-the-new-chair-of-hyperledgers-governing-board.html plain text: www-meet-robert-palatnick-the-new-chair-of-hyperledgers-governing-board.txt item: #3066 of 3327 id: www-meet-some-of-the-many-hyperledgerwomen-putting-blockchain-to-work author: www title: www-meet-some-of-the-many-hyperledgerwomen-putting-blockchain-to-work date: None words: 2208 flesch: 45 summary: As part of her role as at Wipro, Nischala is an active champion of enterprise blockchain and Hyperledger technologies. ConsenSys The PegaSys team at ConsenSys is focused largely on the development of Hyperledger Besu. keywords: blockchain; business; decentralized; global; hyperledger; marketing; technology; university; women; years cache: www-meet-some-of-the-many-hyperledgerwomen-putting-blockchain-to-work.html plain text: www-meet-some-of-the-many-hyperledgerwomen-putting-blockchain-to-work.txt item: #3067 of 3327 id: www-meet-the-hyperledger-besu-maintainers-antoine-toulme-splunk author: www title: www-meet-the-hyperledger-besu-maintainers-antoine-toulme-splunk date: None words: 1218 flesch: 48 summary: As interest in enterprise Ethereum has grown, so too has the community driving development of Hyperledger Besu. The growing Hyperledger Besu project and community is led by a committed group of maintainers. keywords: besu; community; foundation; hyperledger; project cache: www-meet-the-hyperledger-besu-maintainers-antoine-toulme-splunk.html plain text: www-meet-the-hyperledger-besu-maintainers-antoine-toulme-splunk.txt item: #3068 of 3327 id: www-meet-the-hyperledger-besu-maintainers-antoine-toulme-splunk?hs_amp=true author: www title: www-meet-the-hyperledger-besu-maintainers-antoine-toulme-splunk?hs_amp=true date: None words: 904 flesch: 57 summary: As interest in enterprise Ethereum has grown, so too has the community driving development of Hyperledger Besu. The growing Hyperledger Besu project and community is led by a committed group of maintainers. keywords: besu; hyperledger; project cache: www-meet-the-hyperledger-besu-maintainers-antoine-toulme-splunk?hs_amp=true.html plain text: www-meet-the-hyperledger-besu-maintainers-antoine-toulme-splunk?hs_amp=true.txt item: #3069 of 3327 id: www-meet-the-hyperledger-besu-maintainers-conor-svensson-web3-labs author: www title: www-meet-the-hyperledger-besu-maintainers-conor-svensson-web3-labs date: None words: 1467 flesch: 50 summary: Web3 Labs provides commercial support services for Hyperledger Besu networks, hence being very active in the project is of paramount importance to the team. For instance, Web3 Labs works with a number of organizations to provide Hyperledger Besu support for their production environments. keywords: besu; hyperledger; labs; project; web3 cache: www-meet-the-hyperledger-besu-maintainers-conor-svensson-web3-labs.html plain text: www-meet-the-hyperledger-besu-maintainers-conor-svensson-web3-labs.txt item: #3070 of 3327 id: www-meet-the-hyperledger-besu-maintainers-conor-svensson-web3-labs?hs_amp=true author: www title: www-meet-the-hyperledger-besu-maintainers-conor-svensson-web3-labs?hs_amp=true date: None words: 1152 flesch: 57 summary: Web3 Labs provides commercial support services for Hyperledger Besu networks, hence being very active in the project is of paramount importance to the team. For instance, Web3 Labs works with a number of organizations to provide Hyperledger Besu support for their production environments. keywords: besu; blockchain; hyperledger cache: www-meet-the-hyperledger-besu-maintainers-conor-svensson-web3-labs?hs_amp=true.html plain text: www-meet-the-hyperledger-besu-maintainers-conor-svensson-web3-labs?hs_amp=true.txt item: #3071 of 3327 id: www-meet-the-hyperledger-besu-maintainers-matt-nelson-consensys author: www title: www-meet-the-hyperledger-besu-maintainers-matt-nelson-consensys date: None words: 1642 flesch: 53 summary: As interest in enterprise Ethereum has grown, so too has the community driving development of Hyperledger Besu. The growing Hyperledger Besu project and community is led by a committed group of maintainers. keywords: besu; client; ethereum; hyperledger; networks cache: www-meet-the-hyperledger-besu-maintainers-matt-nelson-consensys.html plain text: www-meet-the-hyperledger-besu-maintainers-matt-nelson-consensys.txt item: #3072 of 3327 id: www-meet-the-hyperledger-besu-maintainers-matt-nelson-consensys?hs_amp=true author: www title: www-meet-the-hyperledger-besu-maintainers-matt-nelson-consensys?hs_amp=true date: None words: 1328 flesch: 58 summary: Meet the Hyperledger Besu Maintainers - Matt Nelson, Consensys Blog | LF Decentralized Trust Meet the Hyperledger Besu Maintainers - Matt Nelson, Consensys Written by Hyperledger | Jul 20, 2023 9:15:00 AM As interest in enterprise Ethereum has grown, so too has the community driving development of Hyperledger Besu. The growing Hyperledger Besu project and community is led by a committed group of maintainers. keywords: besu; hyperledger; networks cache: www-meet-the-hyperledger-besu-maintainers-matt-nelson-consensys?hs_amp=true.html plain text: www-meet-the-hyperledger-besu-maintainers-matt-nelson-consensys?hs_amp=true.txt item: #3073 of 3327 id: www-meet-the-hyperledger-besu-maintainers-matthew-whitehead-kaleido author: www title: www-meet-the-hyperledger-besu-maintainers-matthew-whitehead-kaleido date: None words: 1816 flesch: 47 summary: Hyperledger Besu has been an option on Kaleido even since before it was known as “Besu” (it was formerly Pantheon). Consensys, a key contributor to Hyperledger Besu, has been actively looking for new maintainers to come forward and pick up the mantle for stewardship of the enterprise requirements, including permissioned use of the Besu runtime.  keywords: besu; community; enterprise; hyperledger; use cache: www-meet-the-hyperledger-besu-maintainers-matthew-whitehead-kaleido.html plain text: www-meet-the-hyperledger-besu-maintainers-matthew-whitehead-kaleido.txt item: #3074 of 3327 id: www-meet-the-hyperledger-besu-maintainers-matthew-whitehead-kaleido?hs_amp=true author: www title: www-meet-the-hyperledger-besu-maintainers-matthew-whitehead-kaleido?hs_amp=true date: None words: 1502 flesch: 52 summary: Hyperledger Besu has been an option on Kaleido even since before it was known as “Besu” (it was formerly Pantheon). Consensys, a key contributor to Hyperledger Besu, has been actively looking for new maintainers to come forward and pick up the mantle for stewardship of the enterprise requirements, including permissioned use of the Besu runtime.  keywords: besu; community; enterprise; hyperledger cache: www-meet-the-hyperledger-besu-maintainers-matthew-whitehead-kaleido?hs_amp=true.html plain text: www-meet-the-hyperledger-besu-maintainers-matthew-whitehead-kaleido?hs_amp=true.txt item: #3075 of 3327 id: www-meet-the-hyperledger-fabric-maintainers-david-enyeart-ibm author: www title: www-meet-the-hyperledger-fabric-maintainers-david-enyeart-ibm date: None words: 1771 flesch: 46 summary: It is important for the community of potential users to be able to access and inspect Hyperledger Fabric code. The maintainers of the Hyperledger Fabric core platform are leading development efforts as Hyperledger Fabric marches towards its 3.0 release. keywords: code; fabric; hyperledger; project; use cache: www-meet-the-hyperledger-fabric-maintainers-david-enyeart-ibm.html plain text: www-meet-the-hyperledger-fabric-maintainers-david-enyeart-ibm.txt item: #3076 of 3327 id: www-meet-the-hyperledger-fabric-maintainers-david-enyeart-ibm?hs_amp=true author: www title: www-meet-the-hyperledger-fabric-maintainers-david-enyeart-ibm?hs_amp=true date: None words: 1456 flesch: 50 summary: It is important for the community of potential users to be able to access and inspect Hyperledger Fabric code. The maintainers of the Hyperledger Fabric core platform are leading development efforts as Hyperledger Fabric marches towards its 3.0 release. keywords: execute; fabric; hyperledger; transactions cache: www-meet-the-hyperledger-fabric-maintainers-david-enyeart-ibm?hs_amp=true.html plain text: www-meet-the-hyperledger-fabric-maintainers-david-enyeart-ibm?hs_amp=true.txt item: #3077 of 3327 id: www-meet-the-hyperledger-fabric-maintainers-tatsuya-sato-hitachi author: www title: www-meet-the-hyperledger-fabric-maintainers-tatsuya-sato-hitachi date: None words: 1638 flesch: 36 summary: The maintainers of the Hyperledger Fabric core platform are leading development efforts as Hyperledger Fabric marches towards its 3.0 release. Meet the Hyperleger Fabric Maintainers – Tatsuya Sato, Hitachi, Ltd 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Meet the Maintainers | Hyperledger Fabric Meet the Hyperleger Fabric Maintainers – Tatsuya Sato, Hitachi, Ltd Hyperledger Foundation | May 2, 2024   Hyperledger Fabric, which launched in 2016 as the first project within the Hyperledger ecosystem, is a widely adopted enterprise blockchain platform that offers performance at scale while preserving privacy. keywords: community; development; dlt; fabric; hyperledger; use cache: www-meet-the-hyperledger-fabric-maintainers-tatsuya-sato-hitachi.html plain text: www-meet-the-hyperledger-fabric-maintainers-tatsuya-sato-hitachi.txt item: #3078 of 3327 id: www-meet-the-hyperledger-fabric-maintainers-tatsuya-sato-hitachi?hs_amp=true author: www title: www-meet-the-hyperledger-fabric-maintainers-tatsuya-sato-hitachi?hs_amp=true date: None words: 1323 flesch: 39 summary: The maintainers of the Hyperledger Fabric core platform are leading development efforts as Hyperledger Fabric marches towards its 3.0 release. Hyperledger Fabricの継続と発展においてコミュニティは重要な役割を果たしています。コミュニティは多様な企業や団体のメンバーによって構成されており、オープンなガバナンスとストラテジーの下、新機能の提案や開発、さらにはコードやドキュメントの品質改善を継続的に実施しています。また、LTSサポート版のメンテナンスもコミュニティによって実行されています。これらの取り組みは、Fabricを常に技術的最前線で保ち、エンタープライズレベルでの厳しい要件を満たすために不可欠です。 オープン開発により、コミュニティというリソースを最大限活用してイノベーションを加速させることが可能になります。ブロックチェーンやDLTの分野では相互接続性、継続性、コードの透明性は極めて重要な要素です。オープンな開発アプローチはこれらの要素を実現するための有効な手段でもあります。 The community plays an important role in the continuation and development of Hyperledger Fabric. keywords: community; fabric; hyperledger; use cache: www-meet-the-hyperledger-fabric-maintainers-tatsuya-sato-hitachi?hs_amp=true.html plain text: www-meet-the-hyperledger-fabric-maintainers-tatsuya-sato-hitachi?hs_amp=true.txt item: #3079 of 3327 id: www-meet-the-hyperledger-fabric-maintainers-yacov-manevich-ibm author: www title: www-meet-the-hyperledger-fabric-maintainers-yacov-manevich-ibm date: None words: 2812 flesch: 57 summary: The maintainers of the Hyperledger Fabric core platform are leading development efforts as Hyperledger Fabric marches towards its 3.0 release. How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Meet the Maintainers | Hyperledger Fabric Meet the Hyperledger Fabric Maintainers – Yacov Manevich, IBM Hyperledger Foundation | Apr 30, 2024 Hyperledger Fabric, which launched in 2016 as the first project within the Hyperledger ecosystem, is a widely adopted enterprise blockchain platform that offers performance at scale while preserving privacy. keywords: bft; community; consensus; fabric; hyperledger; project cache: www-meet-the-hyperledger-fabric-maintainers-yacov-manevich-ibm.html plain text: www-meet-the-hyperledger-fabric-maintainers-yacov-manevich-ibm.txt item: #3080 of 3327 id: www-meet-the-hyperledger-fabric-maintainers-yacov-manevich-ibm?hs_amp=true author: www title: www-meet-the-hyperledger-fabric-maintainers-yacov-manevich-ibm?hs_amp=true date: None words: 2497 flesch: 61 summary: The maintainers of the Hyperledger Fabric core platform are leading development efforts as Hyperledger Fabric marches towards its 3.0 release. Below, we hear from Yacov Manevich of IBM about his work as a maintainer and what excites him about Hyperledger Fabric now and in the future. keywords: bft; community; fabric; hyperledger; project cache: www-meet-the-hyperledger-fabric-maintainers-yacov-manevich-ibm?hs_amp=true.html plain text: www-meet-the-hyperledger-fabric-maintainers-yacov-manevich-ibm?hs_amp=true.txt item: #3081 of 3327 id: www-meet-the-hyperledger-india-chapter-community author: www title: www-meet-the-hyperledger-india-chapter-community date: None words: 1438 flesch: 55 summary: That being said, I am confident that Hyperledger India Chapter will spearhead a lot more of these student outreach programs and will be an evangelist of Hyperledger and enterprise blockchain among the growing student and professional circuits of the subcontinent. The weekly meetings provide great insights into several Hyperledger projects and how newbies can join and contribute to them. keywords: blockchain; chapter; hyperledger; india; year cache: www-meet-the-hyperledger-india-chapter-community.html plain text: www-meet-the-hyperledger-india-chapter-community.txt item: #3082 of 3327 id: www-meet-the-hyperledger-india-chapter-community-part-ii author: www title: www-meet-the-hyperledger-india-chapter-community-part-ii date: None words: 1416 flesch: 51 summary: This Year Saintgits College of Engineering joined hands with Hyperledger India Chapter to organise “Women in Blockchain – a Panel Discussion,” with an objective to accelerate the powerful partnerships of women to lead in the education, development and promotion of blockchain technologies. I started this year by getting acquainted with Hyperledger India Chapter (HIRC) and its first event of the year, “HyperHack 2020.” keywords: blockchain; community; event; hyperledger; india; year cache: www-meet-the-hyperledger-india-chapter-community-part-ii.html plain text: www-meet-the-hyperledger-india-chapter-community-part-ii.txt item: #3083 of 3327 id: www-meet-the-hyperledger-summer-2018-interns-part-1 author: www title: www-meet-the-hyperledger-summer-2018-interns-part-1 date: None words: 3151 flesch: 51 summary: I see blockchain technology becoming significantly used by public institutions (e.g., banks, universities). But, in order to live up to its potential, blockchain technology will have to deal with challenges such as scalability, regulations, and so on. keywords: blockchain; computer; decentralized; hyperledger; people; project; science; technology cache: www-meet-the-hyperledger-summer-2018-interns-part-1.html plain text: www-meet-the-hyperledger-summer-2018-interns-part-1.txt item: #3084 of 3327 id: www-meet-the-hyperledger-summer-2018-interns-part-2 author: www title: www-meet-the-hyperledger-summer-2018-interns-part-2 date: None words: 3044 flesch: 57 summary: It is hard to tell where blockchain technology will lead to in five years since the technology is evolving very fast with many talented people are contributing. There are several reasons for adopting blockchain technology. keywords: blockchain; contracts; decentralized; hyperledger; information; project; technology; work cache: www-meet-the-hyperledger-summer-2018-interns-part-2.html plain text: www-meet-the-hyperledger-summer-2018-interns-part-2.txt item: #3085 of 3327 id: www-meet-the-hyperledger-summer-2018-interns-part-2?hs_amp=true author: www title: www-meet-the-hyperledger-summer-2018-interns-part-2?hs_amp=true date: None words: 2733 flesch: 60 summary: We hope you join them in the effort by contributing to Hyperledger projects. It is hard to tell where blockchain technology will lead to in five years since the technology is evolving very fast with many talented people are contributing. keywords: blockchain; contracts; hyperledger; information; project; technology; work cache: www-meet-the-hyperledger-summer-2018-interns-part-2?hs_amp=true.html plain text: www-meet-the-hyperledger-summer-2018-interns-part-2?hs_amp=true.txt item: #3086 of 3327 id: www-meet-the-maintainers author: www title: www-meet-the-maintainers date: None words: 798 flesch: 26 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Meet the Maintainers | Besu Meet the Hyperledger Besu Maintainers – Antoine Toulme, Splunk As interest in enterprise Ethereum has grown, so too has the community driving development of Hyperledger Besu. keywords: besu; community; hyperledger; maintainers cache: www-meet-the-maintainers.html plain text: www-meet-the-maintainers.txt item: #3087 of 3327 id: www-meet-weaver-one-the-new-hyperledger-labs-projects-taking-on-cross-chain-and-off-chain-operations author: www title: www-meet-weaver-one-the-new-hyperledger-labs-projects-taking-on-cross-chain-and-off-chain-operations date: None words: 1079 flesch: 34 summary: Weaver currently offers protocols for data transfers among Hyperledger Fabric and Corda networks, and asset exchanges among Hyperledger Fabric networks. Accommodate DLT heterogeneity without favoring a particular DLT design Allow networks to maintain their independence and collective sovereignty Minimize coupling during cross-network interactions Rely on common standards for cross-network protocol units Do not require a trusted intermediary or third-party ledger Do not require changes to existing DLT stacks Make no security and trust assumptions on Weaver components Treat privacy and least privilege as a first-class requirement Weaver addresses three broad classes of use cases: Data transfer: ledger data (state) communication with proof Asset transfer: movement of an asset from one ledger to another Asset exchange: atomic exchange of asset ownership in different ledgers The protocols to realize these use cases can be abstracted into a common stack of layers akin to the OSI model, from message formats at the bottom to governance rules at the top (see diagram below). keywords: chain; decentralized; hyperledger; network; weaver cache: www-meet-weaver-one-the-new-hyperledger-labs-projects-taking-on-cross-chain-and-off-chain-operations.html plain text: www-meet-weaver-one-the-new-hyperledger-labs-projects-taking-on-cross-chain-and-off-chain-operations.txt item: #3088 of 3327 id: www-member-case-study author: www title: www-member-case-study date: None words: 641 flesch: 25 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Read More Hyperledger Foundation | Aug 7, 2023 Climate | Member Case Study | Hyperledger Fabric Fujitsu Develops Hyperledger Fabric-Powered Exchange for Plant-Sourced Water Recovered by Botanical Water Technologies Read the full case study here. keywords: case; decentralized; hyperledger cache: www-member-case-study.html plain text: www-member-case-study.txt item: #3089 of 3327 id: www-memberpass-is-gaining-adoption-in-credit-unions author: www title: www-memberpass-is-gaining-adoption-in-credit-unions date: None words: 956 flesch: 43 summary: In late September 2020, we commissioned a nationally representative survey to over 1,000 adults about their perceptions of MemberPass, Bonifii’s digital credential solution that enables financial institutions to instantly verify financial credentials seamlessly across all consumer contact points in a highly secure and privacy-preserving manner.   There were lots of noteworthy findings: 62% of credit union members said they would sign up for MemberPass if it were available. keywords: consumers; credit; decentralized; memberpass cache: www-memberpass-is-gaining-adoption-in-credit-unions.html plain text: www-memberpass-is-gaining-adoption-in-credit-unions.txt item: #3090 of 3327 id: www-memberpass-is-gaining-adoption-in-credit-unions?hs_amp=true author: www title: www-memberpass-is-gaining-adoption-in-credit-unions?hs_amp=true date: None words: 639 flesch: 51 summary: In late September 2020, we commissioned a nationally representative survey to over 1,000 adults about their perceptions of MemberPass, Bonifii’s digital credential solution that enables financial institutions to instantly verify financial credentials seamlessly across all consumer contact points in a highly secure and privacy-preserving manner.   Today, there are multiple authentication steps in place in financial institutions thanks to the steady increase in cybercrimes. keywords: credit; memberpass cache: www-memberpass-is-gaining-adoption-in-credit-unions?hs_amp=true.html plain text: www-memberpass-is-gaining-adoption-in-credit-unions?hs_amp=true.txt item: #3091 of 3327 id: www-mentee-program author: www title: www-mentee-program date: None words: 1135 flesch: 28 summary: Community Role: Aspiring to play a pivotal role in fostering a welcoming environment, my future includes active participation in Hyperledger community initiatives. Under the guidance of Arun S M, who is member of the Technical Oversight Committee of Hyperledger Foundation, these contributions became pivotal in shaping the community’s resources and accessibility. keywords: community; hyperledger; mentee; onboarding; project cache: www-mentee-program.html plain text: www-mentee-program.txt item: #3092 of 3327 id: www-mentee-program?hs_amp=true author: www title: www-mentee-program?hs_amp=true date: None words: 824 flesch: 29 summary: Community Role: Aspiring to play a pivotal role in fostering a welcoming environment, my future includes active participation in Hyperledger community initiatives. Hyperledger Mentorship Spotlight: Hyperledger Onboarding Mentor/Mentee Program Blog | LF Decentralized Trust Hyperledger Mentorship Spotlight: Hyperledger Onboarding Mentor/Mentee Program Written by Akanksha Rani | Dec 11, 2023 3:03:36 PM In the expansive realm of Hyperledger, my journey as a mentee in the Hyperledger Onboarding Mentor/Mentee Program has been a profound exploration. keywords: community; hyperledger; onboarding cache: www-mentee-program?hs_amp=true.html plain text: www-mentee-program?hs_amp=true.txt item: #3093 of 3327 id: www-mentorship-program author: www title: www-mentorship-program date: None words: 1329 flesch: 22 summary: Read More Naian G | Mar 13, 2024 Mentorship Program | Hyperledger Fabric Hyperledger Collaborative Learning Spotlight: BiniBFT - An Optimized BFT on Fabric WHAT WE WORKED ON: Read More Abhishek Ranjan, Ajitesh Kumar Soni, Ashna P S, Riddhi Ravindra Katarki, Sahilsher Singh, and Siddhant Prateek Mahanayak | Mar 5, 2024 Mentorship Program | Hyperledger Iroha Hyperledger Mentorship Spotlight: Iroha 2 Blockchain Explorer Engaging in the Iroha 2 Blockchain Explorer project through the Hyperledger Mentorship project has been an exhilarating journey marked by technical challenges, continuous... Read More Kshitij Roodkee | Feb 20, 2024 Mentorship Program | Hyperledger Caliper | Besu Hyperledger Mentorship Spotlight: Performance Analysis and Benchmarking of Besu using Caliper with Complex Workloads Introduction Read More Suyash Nayan | Jan 11, 2024 Mentorship Program | Project: Besu Hyperledger Mentorship Spotlight: Learning Tokens in Hyperledger Besu My Hyperledger Mentorship project has been a thrilling journey, filled with challenges, learnings, and a deep sense of contribution to a broader technical community. Read More Aditya Joshi, Walmart | Sep 5, 2023 Mentorship Program Calling the Next Generation of Open Source Blockchain Contributors: Applications are Open for the 2023 Hyperledger Annual Mentorship Program Looking to get a jumpstart on a software career? keywords: hyperledger; mentorship; program; project; spotlight cache: www-mentorship-program.html plain text: www-mentorship-program.txt item: #3094 of 3327 id: www-mentorship-spotlight-ai-faq-lab-gui-implementation-and-prototype-deployment author: www title: www-mentorship-spotlight-ai-faq-lab-gui-implementation-and-prototype-deployment date: None words: 895 flesch: 27 summary: Guided by my mentor and the  LF Decentralized Trust community, I overcame challenges inherent in large-scale open-source projects, refined my understanding of LLM technologies, and embraced the collaborative open-source philosophy. View previous blog post Back to all blog posts View next blog post The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: decentralized; faq; project cache: www-mentorship-spotlight-ai-faq-lab-gui-implementation-and-prototype-deployment.html plain text: www-mentorship-spotlight-ai-faq-lab-gui-implementation-and-prototype-deployment.txt item: #3095 of 3327 id: www-mentorship-spotlight-ai-faq-lab-gui-implementation-and-prototype-deployment?hs_amp=true author: www title: www-mentorship-spotlight-ai-faq-lab-gui-implementation-and-prototype-deployment?hs_amp=true date: None words: 582 flesch: 30 summary: It serves as a flexible framework or template for communities, organizations, or companies to customize and enhance using advanced AI techniques such as Retrieval-Augmented Generation (RAG). Guided by my mentor and the  LF Decentralized Trust community, I overcame challenges inherent in large-scale open-source projects, refined my understanding of LLM technologies, and embraced the collaborative open-source philosophy. keywords: faq cache: www-mentorship-spotlight-ai-faq-lab-gui-implementation-and-prototype-deployment?hs_amp=true.html plain text: www-mentorship-spotlight-ai-faq-lab-gui-implementation-and-prototype-deployment?hs_amp=true.txt item: #3096 of 3327 id: www-mentorship-spotlight-binibft-implementation-the-optimized-bft-on-fabric author: www title: www-mentorship-spotlight-binibft-implementation-the-optimized-bft-on-fabric date: None words: 848 flesch: 29 summary: Before this mentorship, I had a strong foundation in Hyperledger Fabric, but this experience introduced me to the core of blockchain consensus mechanisms. Project Overview The BiniBFT consensus algorithm developed through the CLP required architectural improvements to enhance its performance and adaptability to Hyperledger Fabric, now an LF Decentralized Trust project. keywords: binibft; decentralized; fabric; project cache: www-mentorship-spotlight-binibft-implementation-the-optimized-bft-on-fabric.html plain text: www-mentorship-spotlight-binibft-implementation-the-optimized-bft-on-fabric.txt item: #3097 of 3327 id: www-mentorship-spotlight-binibft-implementation-the-optimized-bft-on-fabric?hs_amp=true author: www title: www-mentorship-spotlight-binibft-implementation-the-optimized-bft-on-fabric?hs_amp=true date: None words: 534 flesch: 31 summary: Before this mentorship, I had a strong foundation in Hyperledger Fabric, but this experience introduced me to the core of blockchain consensus mechanisms. Learnings and Accomplishments This mentorship was a transformative experience, strengthening my expertise in BFT consensus models, distributed systems, and blockchain scalability. keywords: binibft; consensus cache: www-mentorship-spotlight-binibft-implementation-the-optimized-bft-on-fabric?hs_amp=true.html plain text: www-mentorship-spotlight-binibft-implementation-the-optimized-bft-on-fabric?hs_amp=true.txt item: #3098 of 3327 id: www-mentorship-spotlight-hyperledger-anoncreds-v2-zkp-based-credential-revocation-manager-implementation author: www title: www-mentorship-spotlight-hyperledger-anoncreds-v2-zkp-based-credential-revocation-manager-implementation date: None words: 951 flesch: 30 summary: This mentorship project set out to enhance the scalability and privacy of credential revocation to enable efficient management even in systems handling millions of credentials. It aimed to develop a more secure and private framework for credential revocation, crucial for maintaining trust and compliance in digital interactions. keywords: anoncreds; decentralized; project; revocation cache: www-mentorship-spotlight-hyperledger-anoncreds-v2-zkp-based-credential-revocation-manager-implementation.html plain text: www-mentorship-spotlight-hyperledger-anoncreds-v2-zkp-based-credential-revocation-manager-implementation.txt item: #3099 of 3327 id: www-mentorship-spotlight-hyperledger-anoncreds-v2-zkp-based-credential-revocation-manager-implementation?hs_amp=true author: www title: www-mentorship-spotlight-hyperledger-anoncreds-v2-zkp-based-credential-revocation-manager-implementation?hs_amp=true date: None words: 637 flesch: 34 summary: This mentorship project set out to enhance the scalability and privacy of credential revocation to enable efficient management even in systems handling millions of credentials. It aimed to develop a more secure and private framework for credential revocation, crucial for maintaining trust and compliance in digital interactions. keywords: revocation cache: www-mentorship-spotlight-hyperledger-anoncreds-v2-zkp-based-credential-revocation-manager-implementation?hs_amp=true.html plain text: www-mentorship-spotlight-hyperledger-anoncreds-v2-zkp-based-credential-revocation-manager-implementation?hs_amp=true.txt item: #3100 of 3327 id: www-mentorship-spotlight-hyperledger-web3j-enhancing-android-support-with-updated-web3j-android-integration author: www title: www-mentorship-spotlight-hyperledger-web3j-enhancing-android-support-with-updated-web3j-android-integration date: None words: 1172 flesch: 29 summary: However, Android libraries do not support such imports. Publishing Configuration: The publishing process for Android libraries differs significantly from Java libraries. keywords: android; library; module; project; web3j cache: www-mentorship-spotlight-hyperledger-web3j-enhancing-android-support-with-updated-web3j-android-integration.html plain text: www-mentorship-spotlight-hyperledger-web3j-enhancing-android-support-with-updated-web3j-android-integration.txt item: #3101 of 3327 id: www-mentorship-spotlight-hyperledger-web3j-enhancing-android-support-with-updated-web3j-android-integration?hs_amp=true author: www title: www-mentorship-spotlight-hyperledger-web3j-enhancing-android-support-with-updated-web3j-android-integration?hs_amp=true date: None words: 859 flesch: 31 summary: However, Android libraries do not support such imports. Publishing Configuration: The publishing process for Android libraries differs significantly from Java libraries. keywords: android; library; web3j cache: www-mentorship-spotlight-hyperledger-web3j-enhancing-android-support-with-updated-web3j-android-integration?hs_amp=true.html plain text: www-mentorship-spotlight-hyperledger-web3j-enhancing-android-support-with-updated-web3j-android-integration?hs_amp=true.txt item: #3102 of 3327 id: www-minehub-and-krypc-leverage-the-power-of-hyperledger-fabric-2-2-to-transform-mining-and-metals-supply-chain author: www title: www-minehub-and-krypc-leverage-the-power-of-hyperledger-fabric-2-2-to-transform-mining-and-metals-supply-chain date: None words: 872 flesch: 41 summary: MineHub and KrypC Leverage the Power of Hyperledger Fabric 2.2 to Transform Mining and Metals Supply Chain – Hyperledger Foundation 2025 How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog MineHub and KrypC Leverage the Power of Hyperledger Fabric 2.2 to Transform Mining and Metals Supply Chain Hyperledger | Dec 14, 2021 Read the full case study here. keywords: case; decentralized; hyperledger; minehub cache: www-minehub-and-krypc-leverage-the-power-of-hyperledger-fabric-2-2-to-transform-mining-and-metals-supply-chain.html plain text: www-minehub-and-krypc-leverage-the-power-of-hyperledger-fabric-2-2-to-transform-mining-and-metals-supply-chain.txt item: #3103 of 3327 id: www-minifabric-a-hyperledger-fabric-quick-start-tool-with-video-guides author: www title: www-minifabric-a-hyperledger-fabric-quick-start-tool-with-video-guides date: None words: 716 flesch: 40 summary: Quick Start Introduction to Minifabric, how to stand up Fabric network and clean up Channels How to create channels, join peers to channels, inspect and change channel configuration Chaincode How to work with Chaincode including install, approve, commit, upgrade, invoke and query Policy and Organizations How to inspect and change endorsement policies, how to bring in new organizations and how to work with private data collections Artifacts and VSCode Fabric Extension How to use VSCode Fabric extension to work with a production like Fabric network. Hyperledger | Apr 29, 2020 Hyperledger Fabric is the clear leader in permission based blockchain frameworks. keywords: fabric; hyperledger; minifabric cache: www-minifabric-a-hyperledger-fabric-quick-start-tool-with-video-guides.html plain text: www-minifabric-a-hyperledger-fabric-quick-start-tool-with-video-guides.txt item: #3104 of 3327 id: www-mohit-vaish author: www title: www-mohit-vaish date: None words: 531 flesch: 19 summary: Next page > Submit a blog Blog guidelines RSS Hyperledger Bevel | Mentorship Program | Hyperledger Fabric Hyperledger Mentorship Spotlight: Upgrade Fabric network from 1.4.x to 2.2.x using Hyperledger Bevel What did you work on? Project name: Upgrade Fabric network from 1.4.x to 2.2.x using Hyperledger... Read More Mohit Vaish | Jan 11, 2023 keywords: blog; decentralized; hyperledger; project cache: www-mohit-vaish.html plain text: www-mohit-vaish.txt item: #3105 of 3327 id: www-my-5-year-journey-with-the-hyperledger-community author: www title: www-my-5-year-journey-with-the-hyperledger-community date: None words: 1092 flesch: 51 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger Bevel | Hyperledger Community | Labs | Mentorship Program My 5-Year Journey with the Hyperledger Community Aditya Joshi, Walmart | Sep 5, 2023 I got introduced to Hyperledger technologies during my undergrad. keywords: community; hyperledger; technologies; year cache: www-my-5-year-journey-with-the-hyperledger-community.html plain text: www-my-5-year-journey-with-the-hyperledger-community.txt item: #3106 of 3327 id: www-my-5-year-journey-with-the-hyperledger-community?hs_amp=true author: www title: www-my-5-year-journey-with-the-hyperledger-community?hs_amp=true date: None words: 773 flesch: 61 summary: I got introduced to Hyperledger technologies during my undergrad. My current contributions include serving as a maintainer for Hyperledger Bevel and the following labs: bevel-operator-fabric (now part of Hyperledger Bevel) blockchain-explorer hlf-connector Thank you for reading! keywords: hyperledger; year cache: www-my-5-year-journey-with-the-hyperledger-community?hs_amp=true.html plain text: www-my-5-year-journey-with-the-hyperledger-community?hs_amp=true.txt item: #3107 of 3327 id: www-naian-g author: www title: www-naian-g date: None words: 522 flesch: 18 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Read More Naian G | Mar 13, 2024 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-naian-g.html plain text: www-naian-g.txt item: #3108 of 3327 id: www-namaste-2023-new-beginnings-at-hyperledger-india-chapter author: www title: www-namaste-2023-new-beginnings-at-hyperledger-india-chapter date: None words: 868 flesch: 41 summary: Blockchain Techfest ’22 was an event held to celebrate Hyperledger India’s 4-year anniversary. Blockchain Stories was yet another in-person event where Julian Gordon, VP, Asia Pacific, Hyperledger Foundation and OpenSSF at The Linux Foundation, attended as the keynote speaker. keywords: blockchain; chapter; hyperledger; india cache: www-namaste-2023-new-beginnings-at-hyperledger-india-chapter.html plain text: www-namaste-2023-new-beginnings-at-hyperledger-india-chapter.txt item: #3109 of 3327 id: www-namaste-2023-new-beginnings-at-hyperledger-india-chapter?hs_amp=true author: www title: www-namaste-2023-new-beginnings-at-hyperledger-india-chapter?hs_amp=true date: None words: 559 flesch: 52 summary: Blockchain Techfest ’22 was an event held to celebrate Hyperledger India’s 4-year anniversary. Hyperledger Foundation Blog | LF Decentralized Trust Namaste 2023 - New Beginnings at Hyperledger India Chapter! – keywords: blockchain; chapter; hyperledger cache: www-namaste-2023-new-beginnings-at-hyperledger-india-chapter?hs_amp=true.html plain text: www-namaste-2023-new-beginnings-at-hyperledger-india-chapter?hs_amp=true.txt item: #3110 of 3327 id: www-national-bank-of-cambodias-new-digital-payment-system-how-soramitsu-helped-modernize-retail-payments-using-hyperledger-iroha author: www title: www-national-bank-of-cambodias-new-digital-payment-system-how-soramitsu-helped-modernize-retail-payments-using-hyperledger-iroha date: None words: 748 flesch: 45 summary: View previous blog post Back to all blog posts View next blog post The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. National Bank of Cambodia’s New Digital Payment System: How Soramitsu Helped Modernize Retail Payments Using Hyperledger Iroha – Hyperledger Foundation 2025 keywords: hyperledger; project; system cache: www-national-bank-of-cambodias-new-digital-payment-system-how-soramitsu-helped-modernize-retail-payments-using-hyperledger-iroha.html plain text: www-national-bank-of-cambodias-new-digital-payment-system-how-soramitsu-helped-modernize-retail-payments-using-hyperledger-iroha.txt item: #3111 of 3327 id: www-national-bank-of-cambodias-new-digital-payment-system-how-soramitsu-helped-modernize-retail-payments-using-hyperledger-iroha?hs_amp=true author: www title: www-national-bank-of-cambodias-new-digital-payment-system-how-soramitsu-helped-modernize-retail-payments-using-hyperledger-iroha?hs_amp=true date: None words: 439 flesch: 59 summary: National Bank of Cambodia’s New Digital Payment System: How Soramitsu Helped Modernize Retail Payments Using Hyperledger Iroha – Hyperledger Foundation Blog | LF Decentralized Trust National Bank of Cambodia’s New Digital Payment System: How Soramitsu Helped Modernize Retail Payments Using Hyperledger Iroha – Hyperledger Foundation Written by Hyperledger | Aug 17, 2020 9:00:00 AM In the Kingdom of Cambodia in Southeast Asia, three-quarters (78%) of its citizens have no bank account, yet more than half own a smartphone. Hyperledger teamed up with Soramitsu on a detailed case study covering the planning and implementation of Bakong, including key goals, milestones, security considerations and core technology requirements, as well as a preview of rollout plans and new features. keywords: hyperledger; system cache: www-national-bank-of-cambodias-new-digital-payment-system-how-soramitsu-helped-modernize-retail-payments-using-hyperledger-iroha?hs_amp=true.html plain text: www-national-bank-of-cambodias-new-digital-payment-system-how-soramitsu-helped-modernize-retail-payments-using-hyperledger-iroha?hs_amp=true.txt item: #3112 of 3327 id: www-new-ens-features-in-hyperledger-web3j-v4.12.3 author: www title: www-new-ens-features-in-hyperledger-web3j-v4.12.3 date: None words: 998 flesch: 43 summary: It maps ENS names to Ethereum addresses, smart contracts, IPFS content, and other types of data, making blockchain interactions more user-friendly. You can use ENS names anywhere you wish to transact in Web3j. keywords: decentralized; ens; ethereum; web3j cache: www-new-ens-features-in-hyperledger-web3j-v4.12.3.html plain text: www-new-ens-features-in-hyperledger-web3j-v4.12.3.txt item: #3113 of 3327 id: www-new-ens-features-in-hyperledger-web3j-v4.12.3?hs_amp=true author: www title: www-new-ens-features-in-hyperledger-web3j-v4.12.3?hs_amp=true date: None words: 688 flesch: 50 summary: It maps ENS names to Ethereum addresses, smart contracts, IPFS content, and other types of data, making blockchain interactions more user-friendly. You can use ENS names anywhere you wish to transact in Web3j. keywords: ens; web3j cache: www-new-ens-features-in-hyperledger-web3j-v4.12.3?hs_amp=true.html plain text: www-new-ens-features-in-hyperledger-web3j-v4.12.3?hs_amp=true.txt item: #3114 of 3327 id: www-new-hyperledger-governance-risk-and-compliance-special-interest-group-set-to-launch author: www title: www-new-hyperledger-governance-risk-and-compliance-special-interest-group-set-to-launch date: None words: 847 flesch: 31 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog New Hyperledger Governance, Risk and Compliance Special Interest Group Set to Launch Emily Fisher | Feb 3, 2022 We would like to call your attention to the launch of the Hyperledger Governance,Risk and Compliance Special Interest Group (GRC SIG). We encourage you to join this community by visiting the links below: Mailing list sign-up Rocket Chat channel  Member Directory   And how to get involved We are excited to launch GRC SIG and are looking forward to collaborating with you. keywords: decentralized; grc; hyperledger; sig cache: www-new-hyperledger-governance-risk-and-compliance-special-interest-group-set-to-launch.html plain text: www-new-hyperledger-governance-risk-and-compliance-special-interest-group-set-to-launch.txt item: #3115 of 3327 id: www-new-hyperledger-media-entertainment-sig-launches-with-welcome-to-all-comers author: www title: www-new-hyperledger-media-entertainment-sig-launches-with-welcome-to-all-comers date: None words: 1364 flesch: 41 summary: Following the established activities of the Social Impact and Trade Finance SIGs, the TME group can then hope to: Collaborate with other core Hyperledger working groups and project in the areas of architecture            —performance and scalability identity            —smart contracts            —and integration Build user-friendly DLT ME applications on Hyperledger, focusing on UX-UI goals over command-line tools alone, thus simplifying the workflow of Hyperledger Fabric—for easier adoption by both artists and arts-related communities Research different protocols—to build standardization across different parties and projects Identify related reference architectures (business/integration or technical/infrastructure) The ME-SIG will focus on the application of Hyperledger DLTs to media-specific and entertainment use cases. keywords: decentralized; entertainment; hyperledger; media; project; sig cache: www-new-hyperledger-media-entertainment-sig-launches-with-welcome-to-all-comers.html plain text: www-new-hyperledger-media-entertainment-sig-launches-with-welcome-to-all-comers.txt item: #3116 of 3327 id: www-new-lfdt-european-regional-chapter-launches-to-support-and-grow-engagement-and-contributions-across-the-continent author: www title: www-new-lfdt-european-regional-chapter-launches-to-support-and-grow-engagement-and-contributions-across-the-continent date: None words: 888 flesch: 29 summary: Our goal is to create a vibrant and inclusive community that contributes to LF Decentralized Trust projects. By building a stronger ecosystem, we can increase awareness and consideration of LF Decentralized Trust projects across the continent.” keywords: chapter; decentralized; technologies; trust cache: www-new-lfdt-european-regional-chapter-launches-to-support-and-grow-engagement-and-contributions-across-the-continent.html plain text: www-new-lfdt-european-regional-chapter-launches-to-support-and-grow-engagement-and-contributions-across-the-continent.txt item: #3117 of 3327 id: www-new-lfdt-european-regional-chapter-launches-to-support-and-grow-engagement-and-contributions-across-the-continent?hs_amp=true author: www title: www-new-lfdt-european-regional-chapter-launches-to-support-and-grow-engagement-and-contributions-across-the-continent?hs_amp=true date: None words: 577 flesch: 34 summary: Our goal is to create a vibrant and inclusive community that contributes to LF Decentralized Trust projects. By building a stronger ecosystem, we can increase awareness and consideration of LF Decentralized Trust projects across the continent.” keywords: chapter; european cache: www-new-lfdt-european-regional-chapter-launches-to-support-and-grow-engagement-and-contributions-across-the-continent?hs_amp=true.html plain text: www-new-lfdt-european-regional-chapter-launches-to-support-and-grow-engagement-and-contributions-across-the-continent?hs_amp=true.txt item: #3118 of 3327 id: www-new-long-term-support-version-of-hyperledger-iroha-creates-on-ramp-for-v2-adoption author: www title: www-new-long-term-support-version-of-hyperledger-iroha-creates-on-ramp-for-v2-adoption date: None words: 1268 flesch: 54 summary: When Hyperledger Iroha v1 was released, it was with the goal of being a flexible private blockchain ledger and to help flatten the DLT learning curve. Hyperledger Iroha v1, which graduated as a project in 2019, is both a marvel of performance, speed, and reliability; as well as a platform for mentorship and learning. keywords: hyperledger; iroha; use cache: www-new-long-term-support-version-of-hyperledger-iroha-creates-on-ramp-for-v2-adoption.html plain text: www-new-long-term-support-version-of-hyperledger-iroha-creates-on-ramp-for-v2-adoption.txt item: #3119 of 3327 id: www-new-long-term-support-version-of-hyperledger-iroha-creates-on-ramp-for-v2-adoption?hs_amp=true author: www title: www-new-long-term-support-version-of-hyperledger-iroha-creates-on-ramp-for-v2-adoption?hs_amp=true date: None words: 955 flesch: 63 summary: When Hyperledger Iroha v1 was released, it was with the goal of being a flexible private blockchain ledger and to help flatten the DLT learning curve. Hyperledger Iroha v1, which graduated as a project in 2019, is both a marvel of performance, speed, and reliability; as well as a platform for mentorship and learning. keywords: hyperledger; iroha cache: www-new-long-term-support-version-of-hyperledger-iroha-creates-on-ramp-for-v2-adoption?hs_amp=true.html plain text: www-new-long-term-support-version-of-hyperledger-iroha-creates-on-ramp-for-v2-adoption?hs_amp=true.txt item: #3120 of 3327 id: www-new-releases-for-integrating-identity-frameworks-your-feedback-requested author: www title: www-new-releases-for-integrating-identity-frameworks-your-feedback-requested date: None words: 1498 flesch: 40 summary: This marks a significant milestone in advancing decentralized identity solutions on the Hedera and other Hiero-based networks, integrating key open source identity frameworks to facilitate the development of privacy-preserving credentialing applications. A key feature request of HIP-762 was the extension of ACA-Py to support Hedera as a Verifiable Data Registry (VDR), thereby enabling developers to build decentralized identity solutions that utilize Hedera's infrastructure. keywords: aca; decentralized; hedera; hiero cache: www-new-releases-for-integrating-identity-frameworks-your-feedback-requested.html plain text: www-new-releases-for-integrating-identity-frameworks-your-feedback-requested.txt item: #3121 of 3327 id: www-new-releases-for-integrating-identity-frameworks-your-feedback-requested?hs_amp=true author: www title: www-new-releases-for-integrating-identity-frameworks-your-feedback-requested?hs_amp=true date: None words: 1189 flesch: 44 summary: Phase 2 – Hedera Plugin for OpenWallet’s Credo-ts Building upon the success of the ACA-Py plugin, we are initiating Phase 2: the development of the Hedera Plugin for the OpenWallet Foundation’s Credo project. This combination allows the agent to manage Hedera-based identities while benefiting from ACA-Py's extensive features and protocol support. keywords: aca; hedera; hiero cache: www-new-releases-for-integrating-identity-frameworks-your-feedback-requested?hs_amp=true.html plain text: www-new-releases-for-integrating-identity-frameworks-your-feedback-requested?hs_amp=true.txt item: #3122 of 3327 id: www-nicko-guyer-hyperledger-firefly-maintainer author: www title: www-nicko-guyer-hyperledger-firefly-maintainer date: None words: 528 flesch: 18 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Governance | Hyperledger FireFly Hyperledger Firefly Achieves Graduated Status; Is in Production Around the World The Hyperledger Technical Oversight Committee (TOC) has approved Hyperledger FireFly as the latest keywords: blog; decentralized; hyperledger; technologies cache: www-nicko-guyer-hyperledger-firefly-maintainer.html plain text: www-nicko-guyer-hyperledger-firefly-maintainer.txt item: #3123 of 3327 id: www-nischal-sharma-and-george-tebrean-hyperledger-web3j-maintainers-and-blockchain-developers-at-web3-labs author: www title: www-nischal-sharma-and-george-tebrean-hyperledger-web3j-maintainers-and-blockchain-developers-at-web3-labs date: None words: 539 flesch: 9 summary: Blog | LF Decentralized Trust | Nischal Sharma and George Tebrean, Hyperledger Web3j maintainers and Blockchain Developers at Web3 Labs 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? Next page > Submit a blog Blog guidelines RSS Web3j Hyperledger Web3j in 2024: Updates for Blockchain Developers Since its introduction in February 2024, maintainers have focused on significantly enhancing... Read More Nischal Sharma and George Tebrean, Hyperledger Web3j maintainers and Blockchain Developers at Web3 Labs | Aug 29, 2024 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-nischal-sharma-and-george-tebrean-hyperledger-web3j-maintainers-and-blockchain-developers-at-web3-labs.html plain text: www-nischal-sharma-and-george-tebrean-hyperledger-web3j-maintainers-and-blockchain-developers-at-web3-labs.txt item: #3124 of 3327 id: www-nischal-sharma-hyperledger-webj3-maintainer-and-blockchain-developer-at-web3-labs author: www title: www-nischal-sharma-hyperledger-webj3-maintainer-and-blockchain-developer-at-web3-labs date: None words: 585 flesch: 17 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Web3j New ENS Features in Hyperledger Web3j v4.12.3 The Ethereum Name Service (ENS) is a cornerstone of the decentralized web, simplifying blockchain... keywords: blog; decentralized; hyperledger; technologies cache: www-nischal-sharma-hyperledger-webj3-maintainer-and-blockchain-developer-at-web3-labs.html plain text: www-nischal-sharma-hyperledger-webj3-maintainer-and-blockchain-developer-at-web3-labs.txt item: #3125 of 3327 id: www-nischal-sharma-webj3-maintainer-and-blockchain-developer-at-web3-labs author: www title: www-nischal-sharma-webj3-maintainer-and-blockchain-developer-at-web3-labs date: None words: 532 flesch: 14 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Web3j Full Linea RPC APIs Support in Web3j Web3j, an LF Decentralized Trust project, is a lightweight, highly modular Java library for... keywords: blog; decentralized; hyperledger; project cache: www-nischal-sharma-webj3-maintainer-and-blockchain-developer-at-web3-labs.html plain text: www-nischal-sharma-webj3-maintainer-and-blockchain-developer-at-web3-labs.txt item: #3126 of 3327 id: www-once-again-forbes-blockchain-50-shows-enterprise-blockchains-footprint-and-impact-with-hyperledger-technologies-leading-the-pack author: www title: www-once-again-forbes-blockchain-50-shows-enterprise-blockchains-footprint-and-impact-with-hyperledger-technologies-leading-the-pack date: None words: 714 flesch: 40 summary: And, once again, half of the companies on the list are using Hyperledger technology.  Of the 12 companies that have made the list every year, six (Ant Group, Cargill, DTCC, IBM, ING and Walmart) use Hyperledger technologies. keywords: blockchain; hyperledger; technologies cache: www-once-again-forbes-blockchain-50-shows-enterprise-blockchains-footprint-and-impact-with-hyperledger-technologies-leading-the-pack.html plain text: www-once-again-forbes-blockchain-50-shows-enterprise-blockchains-footprint-and-impact-with-hyperledger-technologies-leading-the-pack.txt item: #3127 of 3327 id: www-once-again-forbes-blockchain-50-shows-enterprise-blockchains-footprint-and-impact-with-hyperledger-technologies-leading-the-pack?hs_amp=true author: www title: www-once-again-forbes-blockchain-50-shows-enterprise-blockchains-footprint-and-impact-with-hyperledger-technologies-leading-the-pack?hs_amp=true date: None words: 399 flesch: 50 summary: Once Again, Forbes “Blockchain 50” Shows Enterprise Blockchain’s Footprint and Impact, with Hyperledger Technologies Leading The Pack – Hyperledger Foundation Blog | LF Decentralized Trust Once Again, Forbes “Blockchain 50” Shows Enterprise Blockchain’s Footprint and Impact, with Hyperledger Technologies Leading The Pack – Hyperledger Foundation Written by Hyperledger | Feb 2, 2021 11:56:28 AM Declaring that blockchain has “gone mainstream,” Forbes today released its 2021 “Blockchain 50,” featuring companies that have at least $1 billion in revenues or are valued at $1 billion or more and “lead in employing distributed ledger technology.” And, once again, half of the companies on the list are using Hyperledger technology.  keywords: hyperledger cache: www-once-again-forbes-blockchain-50-shows-enterprise-blockchains-footprint-and-impact-with-hyperledger-technologies-leading-the-pack?hs_amp=true.html plain text: www-once-again-forbes-blockchain-50-shows-enterprise-blockchains-footprint-and-impact-with-hyperledger-technologies-leading-the-pack?hs_amp=true.txt item: #3128 of 3327 id: www-one-year-later-interoperability-standardization-shine-at-consensus author: www title: www-one-year-later-interoperability-standardization-shine-at-consensus date: None words: 1308 flesch: 42 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog | Hyperledger Burrow One Year Later: Interoperability & Standardization Shine at Consensus Hyperledger | May 24, 2018 Image: The Hyperledger booth at Consensus 2018 Interoperability and standardization took center stage (literally) last week in New York at Consensus, when organizations like FedEx explained that both Ethereum and Hyperledger technology power their logistics solution and that it was a goal of theirs to be agnostic when choosing ledger technologies. Then there was the Enterprise Ethereum Alliance, which announced their 1.0 specification that many blockchain developer communities, including Hyperledger Sawtooth, plan to be compatible with in the near future. keywords: consensus; hyperledger; interoperability; sawtooth; technologies cache: www-one-year-later-interoperability-standardization-shine-at-consensus.html plain text: www-one-year-later-interoperability-standardization-shine-at-consensus.txt item: #3129 of 3327 id: www-one-year-later-interoperability-standardization-shine-at-consensus?hs_amp=true author: www title: www-one-year-later-interoperability-standardization-shine-at-consensus?hs_amp=true date: None words: 997 flesch: 47 summary: Interoperability & Standardization Shine at Consensus – Hyperledger Foundation Blog | LF Decentralized Trust One Year Later: Interoperability & Standardization Shine at Consensus – Hyperledger Foundation Written by Hyperledger | May 24, 2018 9:00:19 AM Image: The Hyperledger booth at Consensus 2018 Interoperability and standardization took center stage (literally) last week in New York at Consensus, when organizations like FedEx explained that both Ethereum and Hyperledger technology power their logistics solution and that it was a goal of theirs to be agnostic when choosing ledger technologies. Then there was the Enterprise Ethereum Alliance, which announced their 1.0 specification that many blockchain developer communities, including Hyperledger Sawtooth, plan to be compatible with in the near future. keywords: consensus; hyperledger; interoperability cache: www-one-year-later-interoperability-standardization-shine-at-consensus?hs_amp=true.html plain text: www-one-year-later-interoperability-standardization-shine-at-consensus?hs_amp=true.txt item: #3130 of 3327 id: www-osama-magdy author: www title: www-osama-magdy date: None words: 526 flesch: 13 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Labs | Mentorship Program | Hyperledger Fabric LF Decentralized Trust Mentorship Spotlight: CC-Tools Support for Fabric Private Chaincode Participating in the Hyperledger Fabric CC-Tools Support for Fabric Private Chaincode project... keywords: blog; decentralized; hyperledger; project cache: www-osama-magdy.html plain text: www-osama-magdy.txt item: #3131 of 3327 id: www-passing-the-baton author: www title: www-passing-the-baton date: None words: 1233 flesch: 48 summary: Distributed ledger technology is in so many ways the embodiment of that ideal implemented directly into database and network architecture, and no less ambitious in its desire to reconstruct how we build software to serve our own needs and serve society at the same time.  Related stories: – Writing the Next Chapter for Hyperledger by Daniela Barbosa, Executive Director at Hyperledger and General Manager, Blockchain, Healthcare and Identity for the Linux Foundation – Hyperledger is almost six years old, but who’s counting by Robert Palatnick, Managing Director and Global Head of Technology Research and Innovation, DTCC, and Chair of the Hyperledger Governing Board ___ Today, I’m very pleased to announce that I’m passing the Hyperledger baton to Daniela Barbosa. keywords: blockchain; foundation; hyperledger; linux cache: www-passing-the-baton.html plain text: www-passing-the-baton.txt item: #3132 of 3327 id: www-performance-sandbox-a-new-hyperledger-lab-is-a-test-ground-for-blockchain-performance-research author: www title: www-performance-sandbox-a-new-hyperledger-lab-is-a-test-ground-for-blockchain-performance-research date: None words: 1574 flesch: 49 summary: To see what’s next: Blockchain Deployment  Communication Level Traffic SDK Level Traffic   User Level Traffic Dashboard Metrics Hyperledger Fabric test-network-k8s (WIP, as application and couchdb)  Tape  Hyperledger Caliper (tbd) jmeter (tbd)   to be completed Hyperledger Fabric Minifab (tbd) … … … … Hyperledger Fabric Hyperledger Bevel (tbd)  … … … … Hyperledger Fabric Hyperledger Cello (tbd) … … … … Taking Hyperledger Fabric as a sample: we need to support different ways to deploy Hyperledger Fabric as a test network, including Kubernetes, Minifab, Hyperledger Bevel, Hyperledger Cello, etc. A new addition to Hyperledger Labs, the Performance Sandbox is a testing environment for Hyperledger projects performance research usage.  keywords: blockchain; hyperledger; performance; sdk; traffic cache: www-performance-sandbox-a-new-hyperledger-lab-is-a-test-ground-for-blockchain-performance-research.html plain text: www-performance-sandbox-a-new-hyperledger-lab-is-a-test-ground-for-blockchain-performance-research.txt item: #3133 of 3327 id: www-performance-sandbox-a-new-hyperledger-lab-is-a-test-ground-for-blockchain-performance-research?hs_amp=true author: www title: www-performance-sandbox-a-new-hyperledger-lab-is-a-test-ground-for-blockchain-performance-research?hs_amp=true date: None words: 1266 flesch: 54 summary: To see what’s next: Blockchain Deployment  Communication Level Traffic SDK Level Traffic   User Level Traffic Dashboard Metrics Hyperledger Fabric test-network-k8s (WIP, as application and couchdb)  Tape  Hyperledger Caliper (tbd) jmeter (tbd)   to be completed Hyperledger Fabric Minifab (tbd) … … … … Hyperledger Fabric Hyperledger Bevel (tbd)  … … … … Hyperledger Fabric Hyperledger Cello (tbd) … … … … Taking Hyperledger Fabric as a sample: we need to support different ways to deploy Hyperledger Fabric as a test network, including Kubernetes, Minifab, Hyperledger Bevel, Hyperledger Cello, etc. – It supports users deploying a target network such as a test-network, also known as a SUT (system under test), for asset transform for Hyperledger Fabric – It supports any traffic generator such as Tape, a light-weight tool to test performance of Hyperledger Fabric, that keeps sending traffic to the target network/SUT. keywords: blockchain; hyperledger; performance; sdk cache: www-performance-sandbox-a-new-hyperledger-lab-is-a-test-ground-for-blockchain-performance-research?hs_amp=true.html plain text: www-performance-sandbox-a-new-hyperledger-lab-is-a-test-ground-for-blockchain-performance-research?hs_amp=true.txt item: #3134 of 3327 id: www-perun-a-hyperledger-lab-enables-economic-transactions-between-embedded-iot-devices author: www title: www-perun-a-hyperledger-lab-enables-economic-transactions-between-embedded-iot-devices date: None words: 1665 flesch: 41 summary: This is where the Perun IoT concept, which was developed as part of the work at the core of Perun, a Hyperledger Lab, comes into the picture. However, with the current state of the Perun framework, embedded machines or their economic agents and profit centers can actively participate in a digital economy by an integration that enables economic transactions between them. keywords: channel; charging; machine; perun; transactions cache: www-perun-a-hyperledger-lab-enables-economic-transactions-between-embedded-iot-devices.html plain text: www-perun-a-hyperledger-lab-enables-economic-transactions-between-embedded-iot-devices.txt item: #3135 of 3327 id: www-perun-a-hyperledger-lab-enables-economic-transactions-between-embedded-iot-devices?hs_amp=true author: www title: www-perun-a-hyperledger-lab-enables-economic-transactions-between-embedded-iot-devices?hs_amp=true date: None words: 1355 flesch: 44 summary: This is where the Perun IoT concept, which was developed as part of the work at the core of Perun, a Hyperledger Lab, comes into the picture. However, with the current state of the Perun framework, embedded machines or their economic agents and profit centers can actively participate in a digital economy by an integration that enables economic transactions between them. keywords: charging; machine; perun cache: www-perun-a-hyperledger-lab-enables-economic-transactions-between-embedded-iot-devices?hs_amp=true.html plain text: www-perun-a-hyperledger-lab-enables-economic-transactions-between-embedded-iot-devices?hs_amp=true.txt item: #3136 of 3327 id: www-peter-broadhurst-paladin-maintainer-and-co-founder-head-of-engineering-kaleido-and-andrew-richardson-paladin-maintainer-and-principal-engineer-digital-assets-kaleido author: www title: www-peter-broadhurst-paladin-maintainer-and-co-founder-head-of-engineering-kaleido-and-andrew-richardson-paladin-maintainer-and-principal-engineer-digital-assets-kaleido date: None words: 561 flesch: 18 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Kaleido | Feb 5, 2025 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-peter-broadhurst-paladin-maintainer-and-co-founder-head-of-engineering-kaleido-and-andrew-richardson-paladin-maintainer-and-principal-engineer-digital-assets-kaleido.html plain text: www-peter-broadhurst-paladin-maintainer-and-co-founder-head-of-engineering-kaleido-and-andrew-richardson-paladin-maintainer-and-principal-engineer-digital-assets-kaleido.txt item: #3137 of 3327 id: www-peter-munnings-coo-at-adhara-marelize-kriel-cryptographer-at-adhara-and-signare-maintainer-and-coenie-beyers-head-of-rd-at-adhara-and-signare-maintainer author: www title: www-peter-munnings-coo-at-adhara-marelize-kriel-cryptographer-at-adhara-and-signare-maintainer-and-coenie-beyers-head-of-rd-at-adhara-and-signare-maintainer date: None words: 559 flesch: 12 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page | Sep 11, 2024 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: adhara; blog; decentralized; hyperledger cache: www-peter-munnings-coo-at-adhara-marelize-kriel-cryptographer-at-adhara-and-signare-maintainer-and-coenie-beyers-head-of-rd-at-adhara-and-signare-maintainer.html plain text: www-peter-munnings-coo-at-adhara-marelize-kriel-cryptographer-at-adhara-and-signare-maintainer-and-coenie-beyers-head-of-rd-at-adhara-and-signare-maintainer.txt item: #3138 of 3327 id: www-peter-vielhaber-hyperledger-identus-contributor author: www title: www-peter-vielhaber-hyperledger-identus-contributor date: None words: 529 flesch: 19 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Decentralized Identity | Hyperledger Identus Announcing Hyperledger Identus, a new decentralized identity applications project We are thrilled to share the latest addition to the Hyperledger family - Hyperledger Identus. keywords: blog; decentralized; hyperledger; technologies cache: www-peter-vielhaber-hyperledger-identus-contributor.html plain text: www-peter-vielhaber-hyperledger-identus-contributor.txt item: #3139 of 3327 id: www-phillip-j-windley-ph-d-chair-sovrin-foundation author: www title: www-phillip-j-windley-ph-d-chair-sovrin-foundation date: None words: 519 flesch: 16 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Hyperledger Indy Hyperledger Welcomes Project Indy Guest post: Phillip J. Windley, Ph.D., Chair, Sovrin Foundation Read More Phillip J. Windley, Ph.D., Chair, Sovrin Foundation | May 2, 2017 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; foundation; hyperledger cache: www-phillip-j-windley-ph-d-chair-sovrin-foundation.html plain text: www-phillip-j-windley-ph-d-chair-sovrin-foundation.txt item: #3140 of 3327 id: www-portugals-blockchain.pt-uses-hyperledger-cacti-as-its-interoperability-framework author: www title: www-portugals-blockchain.pt-uses-hyperledger-cacti-as-its-interoperability-framework date: None words: 1285 flesch: 32 summary: If you’re interested in exploring more about the latest developments in blockchain interoperability and implementing Hyperledger Cacti, there is in- depth technical workshop on Hyperledger Cacti on Thursday, May 23, at 8AM Pacific. ___ PT Uses Hyperledger Cacti as its Interoperability Framework 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? keywords: blockchain.pt; cacti; decentralized; hyperledger; interoperability; portugal cache: www-portugals-blockchain.pt-uses-hyperledger-cacti-as-its-interoperability-framework.html plain text: www-portugals-blockchain.pt-uses-hyperledger-cacti-as-its-interoperability-framework.txt item: #3141 of 3327 id: www-portugals-blockchain.pt-uses-hyperledger-cacti-as-its-interoperability-framework?hs_amp=true author: www title: www-portugals-blockchain.pt-uses-hyperledger-cacti-as-its-interoperability-framework?hs_amp=true date: None words: 972 flesch: 34 summary: If you’re interested in exploring more about the latest developments in blockchain interoperability and implementing Hyperledger Cacti, there is in- depth technical workshop on Hyperledger Cacti on Thursday, May 23, at 8AM Pacific. ___ PT Uses Hyperledger Cacti as its Interoperability Framework Blog | LF Decentralized Trust Portugal’s Blockchain. keywords: blockchain; cacti; hyperledger; interoperability cache: www-portugals-blockchain.pt-uses-hyperledger-cacti-as-its-interoperability-framework?hs_amp=true.html plain text: www-portugals-blockchain.pt-uses-hyperledger-cacti-as-its-interoperability-framework?hs_amp=true.txt item: #3142 of 3327 id: www-poste-italiane-turns-to-hyperledger-besu-to-streamline-multibrand-loyalty-program author: www title: www-poste-italiane-turns-to-hyperledger-besu-to-streamline-multibrand-loyalty-program date: None words: 949 flesch: 46 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Besu Poste Italiane Turns to Hyperledger Besu to Streamline Multibrand Loyalty Program Hyperledger | May 19, 2021 Poste Italiane, the Italian postal service, is one of the country’s oldest and biggest organizations with a role that extends well beyond mail and package delivery. Today, Poste Italiane is not just mail delivery but an online marketplace. keywords: italiane; loyalty; points; poste cache: www-poste-italiane-turns-to-hyperledger-besu-to-streamline-multibrand-loyalty-program.html plain text: www-poste-italiane-turns-to-hyperledger-besu-to-streamline-multibrand-loyalty-program.txt item: #3143 of 3327 id: www-poste-italiane-turns-to-hyperledger-besu-to-streamline-multibrand-loyalty-program?hs_amp=true author: www title: www-poste-italiane-turns-to-hyperledger-besu-to-streamline-multibrand-loyalty-program?hs_amp=true date: None words: 641 flesch: 56 summary: Today, Poste Italiane is not just mail delivery but an online marketplace. With 158 years of history, a network of more than 12,800 post offices, a workforce of 126,000, total financial assets of €536 billion and 35 million customers, Poste Italiane is at the center of Italian commerce. keywords: italiane; poste cache: www-poste-italiane-turns-to-hyperledger-besu-to-streamline-multibrand-loyalty-program?hs_amp=true.html plain text: www-poste-italiane-turns-to-hyperledger-besu-to-streamline-multibrand-loyalty-program?hs_amp=true.txt item: #3144 of 3327 id: www-preparing-for-the-besu-certified-professional-exam-tips-resources-and-a-discount-code author: www title: www-preparing-for-the-besu-certified-professional-exam-tips-resources-and-a-discount-code date: None words: 962 flesch: 39 summary: Configure, Deploy, and Manage a Besu Private Network Besu Plug-ins: Fork-free Client Modifications to Extend Besu Use Cases Como Operar e Usar Hyperledger Besu em Redes Públicas e Privadas (Conducted in Portuguese) Using Hyperledger Besu to Participate in Public Ethereum Networks The Besu community has good documentation so that is another resource. With demand for IT pros with decentralized technology skills rising exponentially in finance, healthcare, supply chain management, energy, media, government, and more, we’ve created this certification so individuals and organizations can show they have the professional knowledge needed to both build and manage solutions on a Besu network. keywords: besu; code; decentralized; exam cache: www-preparing-for-the-besu-certified-professional-exam-tips-resources-and-a-discount-code.html plain text: www-preparing-for-the-besu-certified-professional-exam-tips-resources-and-a-discount-code.txt item: #3145 of 3327 id: www-preparing-for-the-besu-certified-professional-exam-tips-resources-and-a-discount-code?hs_amp=true author: www title: www-preparing-for-the-besu-certified-professional-exam-tips-resources-and-a-discount-code?hs_amp=true date: None words: 652 flesch: 51 summary: Configure, Deploy, and Manage a Besu Private Network Besu Plug-ins: Fork-free Client Modifications to Extend Besu Use Cases Como Operar e Usar Hyperledger Besu em Redes Públicas e Privadas (Conducted in Portuguese) Using Hyperledger Besu to Participate in Public Ethereum Networks The Besu community has good documentation so that is another resource. With demand for IT pros with decentralized technology skills rising exponentially in finance, healthcare, supply chain management, energy, media, government, and more, we’ve created this certification so individuals and organizations can show they have the professional knowledge needed to both build and manage solutions on a Besu network. keywords: besu; exam; network cache: www-preparing-for-the-besu-certified-professional-exam-tips-resources-and-a-discount-code?hs_amp=true.html plain text: www-preparing-for-the-besu-certified-professional-exam-tips-resources-and-a-discount-code?hs_amp=true.txt item: #3146 of 3327 id: www-privacy-by-design-in-hyperledger-indy author: www title: www-privacy-by-design-in-hyperledger-indy date: None words: 1766 flesch: 49 summary: What Hyperledger Indy Privacy DOES Deliver Hyperledger Indy allows you to construct interactions where the degree of disclosure is explicit and minimal–much smaller than what was previously possible. If this can happen when stakes are so high, and when the organization is as careful as a sophisticated army, then similar fiascos will undoubtedly occur, both with and without Indy technology, for the foreseeable future. keywords: hyperledger; indy; privacy; technologies; technology; use cache: www-privacy-by-design-in-hyperledger-indy.html plain text: www-privacy-by-design-in-hyperledger-indy.txt item: #3147 of 3327 id: www-privacy-by-design-in-hyperledger-indy?hs_amp=true author: www title: www-privacy-by-design-in-hyperledger-indy?hs_amp=true date: None words: 1455 flesch: 55 summary: What Hyperledger Indy Privacy DOES Deliver Hyperledger Indy allows you to construct interactions where the degree of disclosure is explicit and minimal–much smaller than what was previously possible. If this can happen when stakes are so high, and when the organization is as careful as a sophisticated army, then similar fiascos will undoubtedly occur, both with and without Indy technology, for the foreseeable future. keywords: hyperledger; indy; privacy; technology cache: www-privacy-by-design-in-hyperledger-indy?hs_amp=true.html plain text: www-privacy-by-design-in-hyperledger-indy?hs_amp=true.txt item: #3148 of 3327 id: www-process-transformation-for-public-services-driven-by-blockchain author: www title: www-process-transformation-for-public-services-driven-by-blockchain date: None words: 1028 flesch: 33 summary: The solution is built on the Self-Sovereign Identity Model where citizens are the custodians of their data (i.e., personal data is stored on citizen mobile wallets, not on the blockchain). While this digital transformation has already begun in the public sector, technologies such as blockchain are essential foundations that will power the next generation of citizen experiences. keywords: blockchain; citizen; records; technologies cache: www-process-transformation-for-public-services-driven-by-blockchain.html plain text: www-process-transformation-for-public-services-driven-by-blockchain.txt item: #3149 of 3327 id: www-process-transformation-for-public-services-driven-by-blockchain?hs_amp=true author: www title: www-process-transformation-for-public-services-driven-by-blockchain?hs_amp=true date: None words: 717 flesch: 39 summary: The solution is built on the Self-Sovereign Identity Model where citizens are the custodians of their data (i.e., personal data is stored on citizen mobile wallets, not on the blockchain). While this digital transformation has already begun in the public sector, technologies such as blockchain are essential foundations that will power the next generation of citizen experiences. keywords: blockchain; records cache: www-process-transformation-for-public-services-driven-by-blockchain?hs_amp=true.html plain text: www-process-transformation-for-public-services-driven-by-blockchain?hs_amp=true.txt item: #3150 of 3327 id: www-project-besu author: www title: www-project-besu date: None words: 571 flesch: 20 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Mentorship Program | Project: Besu Hyperledger Mentorship Spotlight: Learning Tokens in Hyperledger Besu My Hyperledger Mentorship project has been a thrilling journey, filled with challenges, learnings,... keywords: besu; decentralized; hyperledger; project cache: www-project-besu.html plain text: www-project-besu.txt item: #3151 of 3327 id: www-project-hyperledger-indy author: www title: www-project-hyperledger-indy date: None words: 1598 flesch: 31 summary: 2023 Hyperledger Aries | Developer Showcase | Project: Hyperledger Indy | Climate | Decentralized Identity Developer showcase series: Jason Sherman, Developer at Energy & Mines Digital Trust, Government of British Columbia Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. 2022 Hyperledger Aries | Developer Showcase | Project: Hyperledger Indy | Decentralized Identity Developer showcase series: Daniel Bluhm, Indicio Back to our Developer Showcase Series to learn what developers in the real world are doing with Hyperledger technologies. keywords: aries; decentralized; hyperledger; identity; indy; project cache: www-project-hyperledger-indy.html plain text: www-project-hyperledger-indy.txt item: #3152 of 3327 id: www-project-services-update-ensuring-hyperledger-projects-and-labs-have-access-to-the-tools-and-services-they-need-to-grow author: www title: www-project-services-update-ensuring-hyperledger-projects-and-labs-have-access-to-the-tools-and-services-they-need-to-grow date: None words: 1390 flesch: 52 summary: We also specify tools we currently offer while we work to  move projects to better tools as well as tools we used to provide but no longer do.  For example, over 20 years ago in the early years of open source, launching a project might have included setting up an IRC server for chat, putting the code on a CVS server and setting up Bugzilla to track bugs and issues  Developer tools improve rapidly, and communities use a whole new set of tools today.  keywords: hyperledger; projects; services; tools cache: www-project-services-update-ensuring-hyperledger-projects-and-labs-have-access-to-the-tools-and-services-they-need-to-grow.html plain text: www-project-services-update-ensuring-hyperledger-projects-and-labs-have-access-to-the-tools-and-services-they-need-to-grow.txt item: #3153 of 3327 id: www-project-services-update-ensuring-hyperledger-projects-and-labs-have-access-to-the-tools-and-services-they-need-to-grow?hs_amp=true author: www title: www-project-services-update-ensuring-hyperledger-projects-and-labs-have-access-to-the-tools-and-services-they-need-to-grow?hs_amp=true date: None words: 1082 flesch: 59 summary: For example, over 20 years ago in the early years of open source, launching a project might have included setting up an IRC server for chat, putting the code on a CVS server and setting up Bugzilla to track bugs and issues  Developer tools improve rapidly, and communities use a whole new set of tools today.  We also specify tools we currently offer while we work to  move projects to better tools as well as tools we used to provide but no longer do.  keywords: hyperledger; tools cache: www-project-services-update-ensuring-hyperledger-projects-and-labs-have-access-to-the-tools-and-services-they-need-to-grow?hs_amp=true.html plain text: www-project-services-update-ensuring-hyperledger-projects-and-labs-have-access-to-the-tools-and-services-they-need-to-grow?hs_amp=true.txt item: #3154 of 3327 id: www-public-mint-lowers-barrier-to-entry-for-blockchain-based-investing-and-defi-with-hyperledger-besu author: www title: www-public-mint-lowers-barrier-to-entry-for-blockchain-based-investing-and-defi-with-hyperledger-besu date: None words: 843 flesch: 52 summary: Public Mint wanted a platform with a one-to-one equivalency between US dollars and a synthetic version of the dollar on their blockchain. About a year afterward, Pantheon became Hyperledger Besu, an open source project under the umbrella of the Hyperledger Foundation, which pleased Public Mint as that brought them closer to the Hyperledger and corporate communities. keywords: case; decentralized; hyperledger; mint cache: www-public-mint-lowers-barrier-to-entry-for-blockchain-based-investing-and-defi-with-hyperledger-besu.html plain text: www-public-mint-lowers-barrier-to-entry-for-blockchain-based-investing-and-defi-with-hyperledger-besu.txt item: #3155 of 3327 id: www-public-mint-lowers-barrier-to-entry-for-blockchain-based-investing-and-defi-with-hyperledger-besu?hs_amp=true author: www title: www-public-mint-lowers-barrier-to-entry-for-blockchain-based-investing-and-defi-with-hyperledger-besu?hs_amp=true date: None words: 530 flesch: 64 summary: Public Mint wanted a platform with a one-to-one equivalency between US dollars and a synthetic version of the dollar on their blockchain. About a year afterward, Pantheon became Hyperledger Besu, an open source project under the umbrella of the Hyperledger Foundation, which pleased Public Mint as that brought them closer to the Hyperledger and corporate communities. keywords: hyperledger; mint cache: www-public-mint-lowers-barrier-to-entry-for-blockchain-based-investing-and-defi-with-hyperledger-besu?hs_amp=true.html plain text: www-public-mint-lowers-barrier-to-entry-for-blockchain-based-investing-and-defi-with-hyperledger-besu?hs_amp=true.txt item: #3156 of 3327 id: www-rafael-belchior-and-pedro-roseiro author: www title: www-rafael-belchior-and-pedro-roseiro date: None words: 529 flesch: 19 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page PT Uses Hyperledger Cacti as its Interoperability Framework Research suggests that the market for applications using DLTs will grow, with many organizations... Read More Rafael Belchior and Pedro Roseiro | May 9, 2024 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-rafael-belchior-and-pedro-roseiro.html plain text: www-rafael-belchior-and-pedro-roseiro.txt item: #3157 of 3327 id: www-raju-owk author: www title: www-raju-owk date: None words: 512 flesch: 19 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-raju-owk.html plain text: www-raju-owk.txt item: #3158 of 3327 id: www-reducing-government-red-tape-british-columbia-creates-new-business-identity-model-with-hyperledger-indy author: www title: www-reducing-government-red-tape-british-columbia-creates-new-business-identity-model-with-hyperledger-indy date: None words: 683 flesch: 33 summary: BootcampBC, hosted by technology leaders from Hyperledger Indy, Verifiable Organizations Network (VON) and the Sovrin Foundation, will cover the concepts of self-sovereign identity and guide participants through building their own Hyperledger Indy agent to verify and issue verifiable credentials using VON’s technology. To get the larger developer and business community engaged, the team is hosting BootCampBC as part of #BCTechSummit. keywords: decentralized; foundation; hyperledger cache: www-reducing-government-red-tape-british-columbia-creates-new-business-identity-model-with-hyperledger-indy.html plain text: www-reducing-government-red-tape-british-columbia-creates-new-business-identity-model-with-hyperledger-indy.txt item: #3159 of 3327 id: www-reducing-government-red-tape-british-columbia-creates-new-business-identity-model-with-hyperledger-indy?hs_amp=true author: www title: www-reducing-government-red-tape-british-columbia-creates-new-business-identity-model-with-hyperledger-indy?hs_amp=true date: None words: 374 flesch: 42 summary: Reducing Government Red Tape: British Columbia Creates New Business Identity Model with Hyperledger Indy – Hyperledger Foundation Blog | LF Decentralized Trust Reducing Government Red Tape: British Columbia Creates New Business Identity Model with Hyperledger Indy – Hyperledger Foundation Written by Hyperledger | Mar 11, 2019 9:05:50 AM In Canada, starting a new business can be like navigating a maze with three levels: local, provincial, and federal. BootcampBC, hosted by technology leaders from Hyperledger Indy, Verifiable Organizations Network (VON) and the Sovrin Foundation, will cover the concepts of self-sovereign identity and guide participants through building their own Hyperledger Indy agent to verify and issue verifiable credentials using VON’s technology. keywords: hyperledger cache: www-reducing-government-red-tape-british-columbia-creates-new-business-identity-model-with-hyperledger-indy?hs_amp=true.html plain text: www-reducing-government-red-tape-british-columbia-creates-new-business-identity-model-with-hyperledger-indy?hs_amp=true.txt item: #3160 of 3327 id: www-reflecting-on-2024-and-shaping-the-future-of-besu author: www title: www-reflecting-on-2024-and-shaping-the-future-of-besu date: None words: 1005 flesch: 40 summary: This architecture opens the door for both industry and community members to develop plug-ins like Fleet for Besu, which simplifies RPC scaling by enabling rapid deployment of Besu nodes tailored for RPC traffic. Focusing on L2s and Permissioned Networks Streamlining L2 Operations We’re doubling down on the mainnet focus for core Besu and adding to Besu’s plugin API as we add functionality and features for L2s. keywords: besu; decentralized; performance; processing; transaction cache: www-reflecting-on-2024-and-shaping-the-future-of-besu.html plain text: www-reflecting-on-2024-and-shaping-the-future-of-besu.txt item: #3161 of 3327 id: www-reflecting-on-2024-and-shaping-the-future-of-besu?hs_amp=true author: www title: www-reflecting-on-2024-and-shaping-the-future-of-besu?hs_amp=true date: None words: 695 flesch: 45 summary: This architecture opens the door for both industry and community members to develop plug-ins like Fleet for Besu, which simplifies RPC scaling by enabling rapid deployment of Besu nodes tailored for RPC traffic. Focusing on L2s and Permissioned Networks Streamlining L2 Operations We’re doubling down on the mainnet focus for core Besu and adding to Besu’s plugin API as we add functionality and features for L2s. keywords: besu; performance; transaction cache: www-reflecting-on-2024-and-shaping-the-future-of-besu?hs_amp=true.html plain text: www-reflecting-on-2024-and-shaping-the-future-of-besu?hs_amp=true.txt item: #3162 of 3327 id: www-regional-chapters author: www title: www-regional-chapters date: None words: 576 flesch: 15 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Ably led by Arun SM,... Read More Hyperledger | Apr 18, 2023 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-regional-chapters.html plain text: www-regional-chapters.txt item: #3163 of 3327 id: www-renata-toktar-hyperledger-indy-maintainer-and-contributor-and-lead-software-engineer-at-dsr-corporation author: www title: www-renata-toktar-hyperledger-indy-maintainer-and-contributor-and-lead-software-engineer-at-dsr-corporation date: None words: 557 flesch: 13 summary: Blog | LF Decentralized Trust | Renata Toktar, Hyperledger Indy maintainer and contributor, and lead software engineer at DSR Corporation 2025 Update: Off to a Fast Start!  Next page > Submit a blog Blog guidelines RSS Decentralized Identity | Besu | Hyperledger Indy LF Decentralized Trust’s Hyperledger Indy on Besu Joins the Did:indy Method: Six Months of Progress Six months ago, Hyperledger Indy on Besu officially joined the did:indy method with the... Read More Renata Toktar, Hyperledger Indy maintainer and contributor, and lead software engineer at DSR Corporation | Apr 15, 2025 keywords: blog; decentralized; hyperledger; indy cache: www-renata-toktar-hyperledger-indy-maintainer-and-contributor-and-lead-software-engineer-at-dsr-corporation.html plain text: www-renata-toktar-hyperledger-indy-maintainer-and-contributor-and-lead-software-engineer-at-dsr-corporation.txt item: #3164 of 3327 id: www-rhythm-and-melody-how-hubs-and-agents-rock-together author: www title: www-rhythm-and-melody-how-hubs-and-agents-rock-together date: None words: 1928 flesch: 54 summary: Hub protocols are data-oriented. Rhythm and Melody: How Hubs and Agents Rock Together – Hyperledger Foundation 2025 Update: Off to a Fast Start! keywords: agents; data; decentralized; hubs; identity; work cache: www-rhythm-and-melody-how-hubs-and-agents-rock-together.html plain text: www-rhythm-and-melody-how-hubs-and-agents-rock-together.txt item: #3165 of 3327 id: www-richard-g-brown-cto-of-r3-peter-munnings-co-founder-and-coo-of-adhara author: www title: www-richard-g-brown-cto-of-r3-peter-munnings-co-founder-and-coo-of-adhara date: None words: 544 flesch: 20 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-richard-g-brown-cto-of-r3-peter-munnings-co-founder-and-coo-of-adhara.html plain text: www-richard-g-brown-cto-of-r3-peter-munnings-co-founder-and-coo-of-adhara.txt item: #3166 of 3327 id: www-road-the-hyperledger-global-forum-part-ii author: www title: www-road-the-hyperledger-global-forum-part-ii date: None words: 1463 flesch: 51 summary: One of the big goals for this year is to make Hyperledger Global Forum as successful and welcoming as past events, even in its virtual format. And they all have a voice at Hyperledger Global Forum.  keywords: forum; global; hgf; hyperledger; technologies; use cache: www-road-the-hyperledger-global-forum-part-ii.html plain text: www-road-the-hyperledger-global-forum-part-ii.txt item: #3167 of 3327 id: www-road-the-hyperledger-global-forum-part-iii author: www title: www-road-the-hyperledger-global-forum-part-iii date: None words: 1568 flesch: 49 summary: Hyperledger Global Forum, taking place June 8-10, will provide an opportunity to learn and understand various aspects of the ecosystem, including technical roadmaps, milestones and the latest uses and applications across industries and markets for Hyperledger projects and other related technologies.  One of the big goals for this year is to make Hyperledger Global Forum as successful and welcoming as past events, even in its virtual format. keywords: blockchain; forum; global; hgf; hyperledger; project cache: www-road-the-hyperledger-global-forum-part-iii.html plain text: www-road-the-hyperledger-global-forum-part-iii.txt item: #3168 of 3327 id: www-rob-dawson-pegasys-and-meredith-baxter-pegasys author: www title: www-rob-dawson-pegasys-and-meredith-baxter-pegasys date: None words: 523 flesch: 20 summary: Next page > Submit a blog Blog guidelines RSS Besu Announcing Hyperledger Besu Today we are excited to announce Hyperledger Besu as the latest project to join Hyperledger.... Read More Rob Dawson, PegaSys, and Meredith Baxter, PegaSys | Aug 29, 2019 Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page keywords: blog; decentralized; hyperledger; project cache: www-rob-dawson-pegasys-and-meredith-baxter-pegasys.html plain text: www-rob-dawson-pegasys-and-meredith-baxter-pegasys.txt item: #3169 of 3327 id: www-ry-jones-and-david-boswell-community-architects author: www title: www-ry-jones-and-david-boswell-community-architects date: None words: 915 flesch: 38 summary: Ry Jones and David Boswell, Community Architects | Mar 5, 2025 Hyperledger Avalon | Blockchain Pioneers Blockchain Pioneers: Hyperledger Avalon As Hyperledger Foundation laid out in the Helping a Community Grow by Pruning Inactive Projectspost, there is an important life cycle to well governed open source projects.... Read More Next page > Submit a blog Blog guidelines RSS Blockchain Pioneers | Hyperledger Explorer Blockchain Pioneers: Hyperledger Explorer As Hyperledger Foundation laid out in the Helping a Community Grow by Pruning Inactive... keywords: community; david; hyperledger cache: www-ry-jones-and-david-boswell-community-architects.html plain text: www-ry-jones-and-david-boswell-community-architects.txt item: #3170 of 3327 id: www-safety-performance-and-innovation-rust-in-hyperledger-sawtooth author: www title: www-safety-performance-and-innovation-rust-in-hyperledger-sawtooth date: None words: 1224 flesch: 47 summary: Safety, Performance and Innovation: Rust in Hyperledger Sawtooth – Hyperledger Foundation 2025 The Hyperledger Sawtooth team is using Rust for new development, so these are exciting times for both Rust and Hyperledger Sawtooth. keywords: components; hyperledger; rust; sawtooth cache: www-safety-performance-and-innovation-rust-in-hyperledger-sawtooth.html plain text: www-safety-performance-and-innovation-rust-in-hyperledger-sawtooth.txt item: #3171 of 3327 id: www-sam-yuan-ibm author: www title: www-sam-yuan-ibm date: None words: 526 flesch: 17 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Labs Performance SandBox, a new Hyperledger Lab, is a test ground for blockchain performance research Meet Performance SandBox, a new Hyperledger Lab for testing new research to boost performance of... Read More Sam Yuan, IBM | Mar 7, 2022 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-sam-yuan-ibm.html plain text: www-sam-yuan-ibm.txt item: #3172 of 3327 id: www-schedule-live-for-hyperledger-global-forum-see-whos-speaking author: www title: www-schedule-live-for-hyperledger-global-forum-see-whos-speaking date: None words: 757 flesch: 26 summary: – Simon Dyson, Yorkshire & Humber Regional Cyber Crime Unit Blockchains for Business: From Huh to Hype to Meh – Casey Kuhlman, Monax Think Tank: Real Estate Applications of Blockchain Technology – Haider Nawab, Royal Bank of Canada Understanding Digital Tokens: Market Overviews & Proposed Guidelines for Policymakers & Practitioners – Perianne Boring, Chamber of Digital Commerce Cryptoeconomics of Enterprise Blockchains – John-Paul Thorbjornsen, CanYa Technical Track Session Highlights Include: Rome Wasn’t Built in a Day – Creating an Enterprise Blockchain Application – Chris Spanton, T-Mobile Using Hyperledger Fabric to Secure High Value Asset Documents – Al Brandt, BlocLedger Running Hyperledger Sawtooth in Production – Duncan Johnston-Watt, Blockchain Technology Partners Transparent Forest and Nature Management in Flanders (Belgium) Using Hyperledger Fabric – Daan Poron, Kunstmaan | Accenture Interactive Approaches to Consortia Governance and Access Control in Hyperledger Fabric Applications – Mark Rakhmilevich, Oracle Workshop Highlights Include: Deploying Hyperledger Fabric with Kubernetes/Helm – Alejandro (Sasha) Vicente Grabovetsky & Nicola Paoli, AID:Tech Hands-On with Verifiable Organizations Network Based on Hyperledger Indy – Stephen Curran; CloudCompass Computing, Inc. & John Jordan; BC.gov Overview: Agents and Hyperledger Indy – Kyle Den Hartog, Evernym and Stephen Curran, CloudCompass Computing, Inc Hands On with Smart Legal Contracts from the Accord Project – Matt Roberts & Dan Selman, Clause View the Full Schedule >> Sign up to receive updates on Hyperledger Global Forum: Schedule Live for Hyperledger Global Forum! keywords: decentralized; forum; global; hyperledger; technologies cache: www-schedule-live-for-hyperledger-global-forum-see-whos-speaking.html plain text: www-schedule-live-for-hyperledger-global-forum-see-whos-speaking.txt item: #3173 of 3327 id: www-security-first-approach-at-hyperledger-foundation author: www title: www-security-first-approach-at-hyperledger-foundation date: None words: 1116 flesch: 33 summary: Read the security policy at Hyperledger Foundation TOC security policy document. “We at Hyperledger Foundation want to emphasize our commitment to following best security practices and believe that this direction is most impactful if it comes from leadership.” keywords: foundation; hyperledger; project; security cache: www-security-first-approach-at-hyperledger-foundation.html plain text: www-security-first-approach-at-hyperledger-foundation.txt item: #3174 of 3327 id: www-security-first-approach-at-hyperledger-foundation?hs_amp=true author: www title: www-security-first-approach-at-hyperledger-foundation?hs_amp=true date: None words: 806 flesch: 35 summary: Read the security policy at Hyperledger Foundation TOC security policy document. “We at Hyperledger Foundation want to emphasize our commitment to following best security practices and believe that this direction is most impactful if it comes from leadership.” keywords: foundation; hyperledger; security cache: www-security-first-approach-at-hyperledger-foundation?hs_amp=true.html plain text: www-security-first-approach-at-hyperledger-foundation?hs_amp=true.txt item: #3175 of 3327 id: www-shashank-kumar author: www title: www-shashank-kumar date: None words: 521 flesch: 12 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Hyperledger Web3j: Enhancing Android Support with Updated web3j-android Integration Read More Shashank Kumar | Jan 13, 2025 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; project cache: www-shashank-kumar.html plain text: www-shashank-kumar.txt item: #3176 of 3327 id: www-sherwood-moore-climate-action-and-accounting-special-interest-group author: www title: www-sherwood-moore-climate-action-and-accounting-special-interest-group date: None words: 540 flesch: 18 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page While media headlines focused on gridlocked... Read More Sherwood Moore, Climate Action and Accounting Special Interest Group | Feb 19, 2025 keywords: blog; decentralized; hyperledger; technologies cache: www-sherwood-moore-climate-action-and-accounting-special-interest-group.html plain text: www-sherwood-moore-climate-action-and-accounting-special-interest-group.txt item: #3177 of 3327 id: www-si-chen-open-source-strategies-inc author: www title: www-si-chen-open-source-strategies-inc date: None words: 540 flesch: 25 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page May 15, 2023 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-si-chen-open-source-strategies-inc.html plain text: www-si-chen-open-source-strategies-inc.txt item: #3178 of 3327 id: www-six-hyperledger-blockchain-projects-now-in-production author: www title: www-six-hyperledger-blockchain-projects-now-in-production date: None words: 1222 flesch: 36 summary: The solution provides authorized users with immediate access to actionable food supply chain data, from farm to store and ultimately the consumer. It is the only network of its kind, connecting growers, processors, distributors, and retailers through a permissioned, permanent and shared record of food system data. keywords: blockchain; data; food; hyperledger; insurance cache: www-six-hyperledger-blockchain-projects-now-in-production.html plain text: www-six-hyperledger-blockchain-projects-now-in-production.txt item: #3179 of 3327 id: www-solution-brief-decentralized-id-and-access-management-diam-for-iot-networks author: www title: www-solution-brief-decentralized-id-and-access-management-diam-for-iot-networks date: None words: 969 flesch: 40 summary: With tens of billions of IoT devices to be connected over the next few years, numerous IoT devices may represent a single person or institution in multiple roles. Successful Implementations of Hyperledger-based IoT Networks IBM and its partners have successfully developed several global supply-chain ecosystems using IoT devices, IoT network services, and Hyperledger blockchain software. keywords: decentralized; devices; hyperledger; iot cache: www-solution-brief-decentralized-id-and-access-management-diam-for-iot-networks.html plain text: www-solution-brief-decentralized-id-and-access-management-diam-for-iot-networks.txt item: #3180 of 3327 id: www-solution-brief-self-assessing-service-level-agreements-slas-in-telecom author: www title: www-solution-brief-self-assessing-service-level-agreements-slas-in-telecom date: None words: 840 flesch: 45 summary: This proposed solution uses Hyperledger Fabric blockchain technology to tackle the gray areas of conventional SLA assessment.  This unique architecture provides a trusted and privacy-preserving network that can precisely monitor and compute SLA metrics, with full transparency for both provider and client.  keywords: client; sla; solution cache: www-solution-brief-self-assessing-service-level-agreements-slas-in-telecom.html plain text: www-solution-brief-self-assessing-service-level-agreements-slas-in-telecom.txt item: #3181 of 3327 id: www-sophie-bulloch-hiero-contributor-and-hendrik-ebbers-hiero-maintainer author: www title: www-sophie-bulloch-hiero-contributor-and-hendrik-ebbers-hiero-maintainer date: None words: 531 flesch: 17 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Read More Sophie Bulloch, Hiero Contributor, and Hendrik Ebbers, Hiero Maintainer | Feb 12, 2025 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hiero; hyperledger cache: www-sophie-bulloch-hiero-contributor-and-hendrik-ebbers-hiero-maintainer.html plain text: www-sophie-bulloch-hiero-contributor-and-hendrik-ebbers-hiero-maintainer.txt item: #3182 of 3327 id: www-sownak-roy-hyperledger-bevel-maintainer-and-tracy-kuhrt-hyperledger-tsc-chair author: www title: www-sownak-roy-hyperledger-bevel-maintainer-and-tracy-kuhrt-hyperledger-tsc-chair date: None words: 540 flesch: 19 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Hyperledger Bevel Hello Hyperledger Bevel keywords: blog; decentralized; hyperledger; technologies cache: www-sownak-roy-hyperledger-bevel-maintainer-and-tracy-kuhrt-hyperledger-tsc-chair.html plain text: www-sownak-roy-hyperledger-bevel-maintainer-and-tracy-kuhrt-hyperledger-tsc-chair.txt item: #3183 of 3327 id: www-sownak-roy-tech-strategy-manager-at-accenture-and-suvajit-sarkar-tech-research-principal-at-accenture-hyperledger-bevel-maintainers author: www title: www-sownak-roy-tech-strategy-manager-at-accenture-and-suvajit-sarkar-tech-research-principal-at-accenture-hyperledger-bevel-maintainers date: None words: 556 flesch: 20 summary: Next page > Submit a blog Blog guidelines RSS Hyperledger Bevel Hyperledger Bevel Release 1.0: Paving the Way for Seamless and Secure Blockchain Deployments We are delighted to unveil the highly anticipated release of Hyperledger Bevel version 1.0, marking... Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page keywords: blog; decentralized; hyperledger; technologies cache: www-sownak-roy-tech-strategy-manager-at-accenture-and-suvajit-sarkar-tech-research-principal-at-accenture-hyperledger-bevel-maintainers.html plain text: www-sownak-roy-tech-strategy-manager-at-accenture-and-suvajit-sarkar-tech-research-principal-at-accenture-hyperledger-bevel-maintainers.txt item: #3184 of 3327 id: www-special-interest-group author: www title: www-special-interest-group date: None words: 654 flesch: 16 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page 2025 Hyperledger Aries | Project: Hyperledger Indy | Special Interest Group | Telecom Introducing the Telecom Decentralized Identity Network (TDIDN), a New Approach to Security, Efficiency and Privacy This solution brief introduces the groundbreaking concept of a Telecom Decentralized Identity Network (TDIDN), a new way to improve identity management using decentralized... Read More Hyperledger Telecom SIG | Apr 25, 2024 Climate | Special Interest Group Blockchain and the Energy Transition: Creating the Platform for a Sustainable Oil and Gas Industry keywords: decentralized; hyperledger; interest cache: www-special-interest-group.html plain text: www-special-interest-group.txt item: #3185 of 3327 id: www-splunk-adds-hyperledger-fabric-data-visibility-into-mix-powers-new-blockchain-based-content-management-solution-for-sp-global author: www title: www-splunk-adds-hyperledger-fabric-data-visibility-into-mix-powers-new-blockchain-based-content-management-solution-for-sp-global date: None words: 992 flesch: 50 summary: Splunk pulls in data without caring about structure, schema, or form so there was no need to format Hyperledger Fabric data before ingestion. For more details on security monitoring of Hyperledger Fabric data, tune into the Wednesday, December 1, webinar with Christoper Cord of Splunk. keywords: data; fabric; hyperledger; splunk cache: www-splunk-adds-hyperledger-fabric-data-visibility-into-mix-powers-new-blockchain-based-content-management-solution-for-sp-global.html plain text: www-splunk-adds-hyperledger-fabric-data-visibility-into-mix-powers-new-blockchain-based-content-management-solution-for-sp-global.txt item: #3186 of 3327 id: www-splunk-adds-hyperledger-fabric-data-visibility-into-mix-powers-new-blockchain-based-content-management-solution-for-sp-global?hs_amp=true author: www title: www-splunk-adds-hyperledger-fabric-data-visibility-into-mix-powers-new-blockchain-based-content-management-solution-for-sp-global?hs_amp=true date: None words: 682 flesch: 59 summary: Splunk pulls in data without caring about structure, schema, or form so there was no need to format Hyperledger Fabric data before ingestion. For more details on security monitoring of Hyperledger Fabric data, tune into the Wednesday, December 1, webinar with Christoper Cord of Splunk. keywords: data; splunk cache: www-splunk-adds-hyperledger-fabric-data-visibility-into-mix-powers-new-blockchain-based-content-management-solution-for-sp-global?hs_amp=true.html plain text: www-splunk-adds-hyperledger-fabric-data-visibility-into-mix-powers-new-blockchain-based-content-management-solution-for-sp-global?hs_amp=true.txt item: #3187 of 3327 id: www-spotlighting-hyperledgersupplychain-use-cases author: www title: www-spotlighting-hyperledgersupplychain-use-cases date: None words: 843 flesch: 42 summary: To see the full line up of supply chain use cases in the Hyperledger Blockchain Showcase, head here. so we wanted to spotlight some of the exciting ways Hyperledger technologies are improving traceability, adding efficiencies and building trust in supply chains around the world. keywords: chain; hyperledger; supply; use cache: www-spotlighting-hyperledgersupplychain-use-cases.html plain text: www-spotlighting-hyperledgersupplychain-use-cases.txt item: #3188 of 3327 id: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-elli-androulaki-ibm-research author: www title: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-elli-androulaki-ibm-research date: None words: 1704 flesch: 44 summary: This work lends itself well to critical infrastructure systems like central bank digital currency systems. When I joined IBM, and with a good understanding on blockchain systems, I participated in internal promotions of the Blockchain for Business concept. keywords: blockchain; hyperledger; ibm; privacy; research; security cache: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-elli-androulaki-ibm-research.html plain text: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-elli-androulaki-ibm-research.txt item: #3189 of 3327 id: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-elli-androulaki-ibm-research?hs_amp=true author: www title: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-elli-androulaki-ibm-research?hs_amp=true date: None words: 1390 flesch: 47 summary: This work lends itself well to critical infrastructure systems like central bank digital currency systems. When I joined IBM, and with a good understanding on blockchain systems, I participated in internal promotions of the Blockchain for Business concept. keywords: blockchain; hyperledger; ibm; privacy cache: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-elli-androulaki-ibm-research?hs_amp=true.html plain text: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-elli-androulaki-ibm-research?hs_amp=true.txt item: #3190 of 3327 id: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-heather-dahl-indicio author: www title: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-heather-dahl-indicio date: None words: 1305 flesch: 52 summary: Distributed ledger technology is a core component in creating a verification layer for digital interaction based on decentralized identity and using verifiable credentials. All paths led to decentralized identity as the solution to the challenge of identity verification — and blockchain is a key part of that solution. keywords: community; decentralized; identity; indicio cache: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-heather-dahl-indicio.html plain text: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-heather-dahl-indicio.txt item: #3191 of 3327 id: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-heather-dahl-indicio?hs_amp=true author: www title: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-heather-dahl-indicio?hs_amp=true date: None words: 993 flesch: 59 summary: I’ve been involved in digital identity and privacy for over a decade. Why is digital identity important for a decentralized future?  keywords: identity; indicio; technology cache: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-heather-dahl-indicio?hs_amp=true.html plain text: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-heather-dahl-indicio?hs_amp=true.txt item: #3192 of 3327 id: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-nancy-norris-government-of-british-columbia author: www title: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-nancy-norris-government-of-british-columbia date: None words: 1717 flesch: 45 summary: Why do you believe in digital trust technology and in what ways can it enable better sustainability practices and processes on behalf of governments?  There are many regulatory processes that could be improved with digital trust technology. keywords: digital; emdt; project; technology; trust cache: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-nancy-norris-government-of-british-columbia.html plain text: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-nancy-norris-government-of-british-columbia.txt item: #3193 of 3327 id: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-nancy-norris-government-of-british-columbia?hs_amp=true author: www title: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-nancy-norris-government-of-british-columbia?hs_amp=true date: None words: 1400 flesch: 50 summary: Why do you believe in digital trust technology and in what ways can it enable better sustainability practices and processes on behalf of governments?  There are many regulatory processes that could be improved with digital trust technology. keywords: digital; technology; trust cache: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-nancy-norris-government-of-british-columbia?hs_amp=true.html plain text: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-nancy-norris-government-of-british-columbia?hs_amp=true.txt item: #3194 of 3327 id: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-ursula-okuinghttons-web3-foundation author: www title: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-ursula-okuinghttons-web3-foundation date: None words: 905 flesch: 43 summary: One is Cogency, a collective that involves traditional media giants such as Condé Nast, Reuters, Le Echos, and the Washington Post, where we explore the potential of Web3 technology for the evolution of the media industry, with a focus on decentralized identities. Why do you believe in blockchain technology, and in what ways do you think it will change the way we live and work? keywords: blockchain; community; decentralized; foundation cache: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-ursula-okuinghttons-web3-foundation.html plain text: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-ursula-okuinghttons-web3-foundation.txt item: #3195 of 3327 id: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-ursula-okuinghttons-web3-foundation?hs_amp=true author: www title: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-ursula-okuinghttons-web3-foundation?hs_amp=true date: None words: 596 flesch: 51 summary: One is Cogency, a collective that involves traditional media giants such as Condé Nast, Reuters, Le Echos, and the Washington Post, where we explore the potential of Web3 technology for the evolution of the media industry, with a focus on decentralized identities. Spotlighting #HyperledgerWomen: Stories from front lines of community building—Ursula O´Kuinghttons, Web3 Foundation – Hyperledger Foundation Blog | LF Decentralized Trust Spotlighting #HyperledgerWomen: Stories from front lines of community building—Ursula O´Kuinghttons, Web3 Foundation – Hyperledger Foundation Written by Hyperledger | Mar 30, 2023 12:46:00 PM keywords: blockchain; foundation cache: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-ursula-okuinghttons-web3-foundation?hs_amp=true.html plain text: www-spotlighting-hyperledgerwomen-stories-from-front-lines-of-community-building-ursula-okuinghttons-web3-foundation?hs_amp=true.txt item: #3196 of 3327 id: www-staff-corner author: www title: www-staff-corner date: None words: 1192 flesch: 30 summary: In case you missed it, the Linux Foundation recently announced the intent to form LF Decentralized Trust, a new bigger umbrella organization where we will gather and grow an... Read More Daniela Barbosa, Executive Director at Hyperledger Foundation and General Manager, Blockchain and Identity for the Linux Foundation | Jul 8, 2024 Hyperledger AnonCreds | Hyperledger Aries | Project: Hyperledger Indy | Staff Corner | Hyperledger Fabric Just Introduced: Refreshed Hyperledger Project Logos Last year, we introduced a new look for Hyperledger Foundation that fit with our increasingly mature market and ecosystem as well as our enterprise audience. Now, with the input... Read More Daniela Barbosa, Executive Director at Hyperledger Foundation and General Manager, Blockchain and Identity for the Linux Foundation | Apr 23, 2024 Staff Corner 2023: keywords: decentralized; foundation; hyperledger; staff cache: www-staff-corner.html plain text: www-staff-corner.txt item: #3197 of 3327 id: www-staff-corner-fostering-innovation-and-impact-in-india author: www title: www-staff-corner-fostering-innovation-and-impact-in-india date: None words: 795 flesch: 26 summary: This work is anchored by LF Decentralized Trust members headquartered in India, including Ayanworks, Dhiway, DigiYatra, DocChain.io, IDS, Infosys, Kerala Blockchain Academy, KrypC, NPCI, Qila, Saintgits, TCS, Wipro, Zeeve and more.   From hosting hackathons and mentorship programs to being the largest region for project mentorships, LF Decentralized Trust India Regional Chapter has consistently demonstrated its leadership in fostering blockchain and decentralized identity innovation. keywords: decentralized; india; trust cache: www-staff-corner-fostering-innovation-and-impact-in-india.html plain text: www-staff-corner-fostering-innovation-and-impact-in-india.txt item: #3198 of 3327 id: www-staff-corner-fostering-innovation-and-impact-in-india?hs_amp=true author: www title: www-staff-corner-fostering-innovation-and-impact-in-india?hs_amp=true date: None words: 484 flesch: 29 summary: Staff Corner: Fostering innovation and impact in India Blog | LF Decentralized Trust Staff Corner: Fostering innovation and impact in India Written by Daniela Barbosa, Executive Director, and Julian Gordon, Asia Pacific and Middle East, LF Decentralized Trust | Dec 13, 2024 4:00:00 AM As we continue to expand the reach and impact of LF Decentralized Trust globally, we are thrilled to announce our active participation in LF India—a new Linux Foundation initiative that embodies the spirit of collaboration, innovation, and community that defines our open source community. From hosting hackathons and mentorship programs to being the largest region for project mentorships, LF Decentralized Trust India Regional Chapter has consistently demonstrated its leadership in fostering blockchain and decentralized identity innovation. keywords: decentralized; india cache: www-staff-corner-fostering-innovation-and-impact-in-india?hs_amp=true.html plain text: www-staff-corner-fostering-innovation-and-impact-in-india?hs_amp=true.txt item: #3199 of 3327 id: www-staff-corner-introducing-hyperledger-foundation author: www title: www-staff-corner-introducing-hyperledger-foundation date: None words: 1083 flesch: 50 summary: In fact, more than half of the companies on the Forbes Blockchain 50, including companies like Baidu, DTTC, Oracle, Samsung, Swisscom, Telefonica, Visa and Walmart, use or have built solutions powered by Hyperledger Foundation technologies. Learn about Hyperledger Foundation membership and all the other ways you can get involved. keywords: foundation; hyperledger; linux; technologies cache: www-staff-corner-introducing-hyperledger-foundation.html plain text: www-staff-corner-introducing-hyperledger-foundation.txt item: #3200 of 3327 id: www-staff-corner-thanking-community-members-for-their-contributions author: www title: www-staff-corner-thanking-community-members-for-their-contributions date: None words: 1166 flesch: 46 summary: One of the items we were giving out were Hyperledger coins that said “Community Code Collaboration Contribution” on the back and had 2022 on the front. Arun S M, Staff Software Engineer, Walmart Global Tech India – Recognized for his active role in welcoming new community members on Discord and as one of the leaders of the Hyperledger India Chapter. keywords: community; foundation; hyperledger; members; people cache: www-staff-corner-thanking-community-members-for-their-contributions.html plain text: www-staff-corner-thanking-community-members-for-their-contributions.txt item: #3201 of 3327 id: www-staff-corner-thanking-community-members-for-their-contributions?hs_amp=true author: www title: www-staff-corner-thanking-community-members-for-their-contributions?hs_amp=true date: None words: 855 flesch: 53 summary: One of the items we were giving out were Hyperledger coins that said “Community Code Collaboration Contribution” on the back and had 2022 on the front. Arun S M, Staff Software Engineer, Walmart Global Tech India – Recognized for his active role in welcoming new community members on Discord and as one of the leaders of the Hyperledger India Chapter. keywords: community; hyperledger; members cache: www-staff-corner-thanking-community-members-for-their-contributions?hs_amp=true.html plain text: www-staff-corner-thanking-community-members-for-their-contributions?hs_amp=true.txt item: #3202 of 3327 id: www-staff-corner-the-importance-of-executive-education-in-driving-enterprise-blockchain-growth author: www title: www-staff-corner-the-importance-of-executive-education-in-driving-enterprise-blockchain-growth date: None words: 871 flesch: 32 summary: Daniela Barbosa, Hyperledger Foundation Executive Director The classes range from a series of free “Blockchain Basics,” which aim to help professionals learn, explore, and evaluate how blockchain technologies can help them meet their professional goals, to a series of professional developer and administrator training courses and certifications.  Staff Corner: The Importance of Executive Education in Driving Enterprise Blockchain Growth – Hyperledger Foundation 2025 keywords: blockchain; foundation; hyperledger; training cache: www-staff-corner-the-importance-of-executive-education-in-driving-enterprise-blockchain-growth.html plain text: www-staff-corner-the-importance-of-executive-education-in-driving-enterprise-blockchain-growth.txt item: #3203 of 3327 id: www-staff-corner-the-importance-of-maintainers-and-contributors-at-lf-decentralized-trust author: www title: www-staff-corner-the-importance-of-maintainers-and-contributors-at-lf-decentralized-trust date: None words: 1249 flesch: 40 summary: Contributors: Building together Contributors, whether seasoned developers or those just entering the blockchain, decentralized identity or Web3 space, play a pivotal role in shaping LF Decentralized Trust projects. By spotlighting contributors, we hope to inspire more developers to get involved and find their own role to play in advancing LF Decentralized Trust projects. keywords: contributors; decentralized; maintainers; trust cache: www-staff-corner-the-importance-of-maintainers-and-contributors-at-lf-decentralized-trust.html plain text: www-staff-corner-the-importance-of-maintainers-and-contributors-at-lf-decentralized-trust.txt item: #3204 of 3327 id: www-staff-corner-the-importance-of-maintainers-and-contributors-at-lf-decentralized-trust?hs_amp=true author: www title: www-staff-corner-the-importance-of-maintainers-and-contributors-at-lf-decentralized-trust?hs_amp=true date: None words: 936 flesch: 45 summary: Contributors: Building together Contributors, whether seasoned developers or those just entering the blockchain, decentralized identity or Web3 space, play a pivotal role in shaping LF Decentralized Trust projects. By spotlighting contributors, we hope to inspire more developers to get involved and find their own role to play in advancing LF Decentralized Trust projects. keywords: decentralized; maintainers; trust cache: www-staff-corner-the-importance-of-maintainers-and-contributors-at-lf-decentralized-trust?hs_amp=true.html plain text: www-staff-corner-the-importance-of-maintainers-and-contributors-at-lf-decentralized-trust?hs_amp=true.txt item: #3205 of 3327 id: www-staff-corner-welcome-to-the-new-hyperledger-foundation-governing-board-chair-accentures-david-treat author: www title: www-staff-corner-welcome-to-the-new-hyperledger-foundation-governing-board-chair-accentures-david-treat date: None words: 1031 flesch: 29 summary: Welcome to the new Hyperledger Foundation Governing Board chair, Accenture’s David Treat Hyperledger | May 18, 2022 Governance is crucial to enterprise-grade open source software development and to the mission of Hyperledger Foundation. He has been a driving force in Accenture’s commitments to Hyperledger Foundation, which ranges from being a leading sponsor of Hyperledger Global Forum and of Diversity, Civility and Inclusion efforts at the annual event to providing extensive technical and marketing leadership to ongoing and extensive code contributions. keywords: board; foundation; governing; hyperledger cache: www-staff-corner-welcome-to-the-new-hyperledger-foundation-governing-board-chair-accentures-david-treat.html plain text: www-staff-corner-welcome-to-the-new-hyperledger-foundation-governing-board-chair-accentures-david-treat.txt item: #3206 of 3327 id: www-staff-corner-welcome-to-the-new-hyperledger-foundation-governing-board-chair-accentures-david-treat?hs_amp=true author: www title: www-staff-corner-welcome-to-the-new-hyperledger-foundation-governing-board-chair-accentures-david-treat?hs_amp=true date: None words: 718 flesch: 31 summary: Staff Corner: Welcome to the new Hyperledger Foundation Governing Board chair, Accenture’s David Treat – Hyperledger Foundation Blog | LF Decentralized Trust Staff Corner: Welcome to the new Hyperledger Foundation Governing Board chair, Accenture’s David Treat – Hyperledger Foundation Written by Hyperledger | May 18, 2022 1:57:00 PM Governance is crucial to enterprise-grade open source software development and to the mission of Hyperledger Foundation. He has been a driving force in Accenture’s commitments to Hyperledger Foundation, which ranges from being a leading sponsor of Hyperledger Global Forum and of Diversity, Civility and Inclusion efforts at the annual event to providing extensive technical and marketing leadership to ongoing and extensive code contributions. keywords: board; foundation; hyperledger cache: www-staff-corner-welcome-to-the-new-hyperledger-foundation-governing-board-chair-accentures-david-treat?hs_amp=true.html plain text: www-staff-corner-welcome-to-the-new-hyperledger-foundation-governing-board-chair-accentures-david-treat?hs_amp=true.txt item: #3207 of 3327 id: www-stephen-curran-hyperledger-aries-maintainer-cloud-compass-computing-inc author: www title: www-stephen-curran-hyperledger-aries-maintainer-cloud-compass-computing-inc date: None words: 540 flesch: 16 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Hyperledger Aries | Project: Hyperledger Indy | Decentralized Identity Why Distributed Ledger Technology (DLT) for Identity? As we continue our pandemic journey that is 2021, more and more people are getting vaccinated... keywords: blog; decentralized; hyperledger; project cache: www-stephen-curran-hyperledger-aries-maintainer-cloud-compass-computing-inc.html plain text: www-stephen-curran-hyperledger-aries-maintainer-cloud-compass-computing-inc.txt item: #3208 of 3327 id: www-strengthening-hyperledger-indy-and-self-sovereign-identity author: www title: www-strengthening-hyperledger-indy-and-self-sovereign-identity date: None words: 1165 flesch: 41 summary: In the months since Hyperledger Indy graduated to ‘production ready’ active status, we’ve seen an outpouring of digital identity business solutions come to market.  With our years of experience and depth of knowledge about digital identity, supporting this community and these projects is not just something interesting for us to do in our spare time. keywords: hyperledger; identity; indy; ssi cache: www-strengthening-hyperledger-indy-and-self-sovereign-identity.html plain text: www-strengthening-hyperledger-indy-and-self-sovereign-identity.txt item: #3209 of 3327 id: www-strengthening-hyperledger-indy-and-self-sovereign-identity?hs_amp=true author: www title: www-strengthening-hyperledger-indy-and-self-sovereign-identity?hs_amp=true date: None words: 853 flesch: 46 summary: In the months since Hyperledger Indy graduated to ‘production ready’ active status, we’ve seen an outpouring of digital identity business solutions come to market.  Strengthening Hyperledger Indy and Self-Sovereign Identity – Hyperledger Foundation Blog | LF Decentralized Trust Strengthening Hyperledger Indy and Self-Sovereign Identity – Hyperledger Foundation Written by Hyperledger | Jul 18, 2019 9:19:06 AM After working on the problem of identity online for more years than we care to admit, it is heartening to see that we are not alone: The identity community we’ve longed to see is here, and it’s transforming the world. keywords: hyperledger; identity; ssi cache: www-strengthening-hyperledger-indy-and-self-sovereign-identity?hs_amp=true.html plain text: www-strengthening-hyperledger-indy-and-self-sovereign-identity?hs_amp=true.txt item: #3210 of 3327 id: www-sunsetting-tessera-and-simplifying-hyperledger-besu author: www title: www-sunsetting-tessera-and-simplifying-hyperledger-besu date: None words: 1475 flesch: 51 summary: Support and Feedback To support our users through this transition, we will provide: Migration Guides: Detailed guides to help users transition to alternative solutions or newer features. Proof of Work consensus: For features that require client modifications, like Proof of Work, we recommend creating a plug-in via our API to maintain them. keywords: base; besu; code; deprecation; features cache: www-sunsetting-tessera-and-simplifying-hyperledger-besu.html plain text: www-sunsetting-tessera-and-simplifying-hyperledger-besu.txt item: #3211 of 3327 id: www-sunsetting-tessera-and-simplifying-hyperledger-besu?hs_amp=true author: www title: www-sunsetting-tessera-and-simplifying-hyperledger-besu?hs_amp=true date: None words: 1165 flesch: 56 summary: Support and Feedback To support our users through this transition, we will provide: Migration Guides: Detailed guides to help users transition to alternative solutions or newer features. Proof of Work consensus: For features that require client modifications, like Proof of Work, we recommend creating a plug-in via our API to maintain them. keywords: besu; code; features cache: www-sunsetting-tessera-and-simplifying-hyperledger-besu?hs_amp=true.html plain text: www-sunsetting-tessera-and-simplifying-hyperledger-besu?hs_amp=true.txt item: #3212 of 3327 id: www-superlogic-maintainers-of-aries-agent-controller author: www title: www-superlogic-maintainers-of-aries-agent-controller date: None words: 530 flesch: 11 summary: | Hyperledger Bevel | Labs Meet Aries Agent Controller, a New Hyperledger Lab A code base developed and contributed by Superlogic that facilitates deploying Hyperledger Aries... Read More Superlogic, maintainers of Aries Agent Controller | Feb 29, 2024 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page keywords: blog; decentralized; hyperledger; technologies cache: www-superlogic-maintainers-of-aries-agent-controller.html plain text: www-superlogic-maintainers-of-aries-agent-controller.txt item: #3213 of 3327 id: www-supply-chain author: www title: www-supply-chain date: None words: 678 flesch: 17 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Read More Energy & Mines Digital Trust | Jun 20, 2024 Supply Chain | Hyperledger Fabric How Hyperledger Fabric Helped Everledger Transform a Market and Blaze a Trail for Others to Follow From the earliest days of blockchain technologies, Everledger has seen its potential to revolutionize the way we perceive and engage with supply chains and ethical practices.... Read More Leanne Kemp, Founder and CEO, Everledger keywords: decentralized; hyperledger; supply; trust cache: www-supply-chain.html plain text: www-supply-chain.txt item: #3214 of 3327 id: www-support-clique-for-hyperledger-besu author: www title: www-support-clique-for-hyperledger-besu date: None words: 789 flesch: 39 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Besu Hyperledger Mentorship Spotlight: Support Clique for Hyperledger Besu Hyperledger | Dec 6, 2021 The Hyperledger Mentorship Program is a structured hands-on learning opportunity for new developers who may otherwise lack the opportunity to gain exposure to Hyperledger open source development and entry to the technical community. Hyperledger Mentorship Spotlight: Support Clique for Hyperledger Besu – Hyperledger Foundation 2025 keywords: besu; hyperledger; mentorship; program cache: www-support-clique-for-hyperledger-besu.html plain text: www-support-clique-for-hyperledger-besu.txt item: #3215 of 3327 id: www-support-clique-for-hyperledger-besu?hs_amp=true author: www title: www-support-clique-for-hyperledger-besu?hs_amp=true date: None words: 481 flesch: 46 summary: Hyperledger Mentorship Spotlight: Support Clique for Hyperledger Besu – Hyperledger Foundation Blog | LF Decentralized Trust Hyperledger Mentorship Spotlight: Support Clique for Hyperledger Besu – Hyperledger Foundation Written by Hyperledger | Dec 6, 2021 8:43:30 AM The Hyperledger Mentorship Program is a structured hands-on learning opportunity for new developers who may otherwise lack the opportunity to gain exposure to Hyperledger open source development and entry to the technical community. To learn more about our Hyperledger Mentorship Program and how you can participate in our next cohort, head over to our program overview page on the Hyperledger wiki. keywords: hyperledger; program cache: www-support-clique-for-hyperledger-besu?hs_amp=true.html plain text: www-support-clique-for-hyperledger-besu?hs_amp=true.txt item: #3216 of 3327 id: www-sustainability-by-design-takeaways-from-linux-foundation-research-the-carbon-footprint-of-nfts-report author: www title: www-sustainability-by-design-takeaways-from-linux-foundation-research-the-carbon-footprint-of-nfts-report date: None words: 691 flesch: 35 summary: Diving into this tug of war between innovation and sustainability, Linux Foundation Research, in collaboration with Hyperledger Foundation and Palm NFT Studio, just released a detailed report on the current and future state of carbon consumption and NFTs that explores the environmental impact of NFTs, investigating how and why NFTs can have varying carbon footprints depending on underlying technology stacks.  Sustainability by design: Takeaways from Linux Foundation Research keywords: foundation; nfts; report cache: www-sustainability-by-design-takeaways-from-linux-foundation-research-the-carbon-footprint-of-nfts-report.html plain text: www-sustainability-by-design-takeaways-from-linux-foundation-research-the-carbon-footprint-of-nfts-report.txt item: #3217 of 3327 id: www-suyash-nayan author: www title: www-suyash-nayan date: None words: 516 flesch: 15 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Mentorship Program | Hyperledger Caliper | Besu Hyperledger Mentorship Spotlight: Performance Analysis and Benchmarking of Besu using Caliper with Complex Workloads Introduction Read More Suyash Nayan | Jan 11, 2024 keywords: blog; decentralized; hyperledger; technologies cache: www-suyash-nayan.html plain text: www-suyash-nayan.txt item: #3218 of 3327 id: www-tackling-diversity-interoperability-developers-at-hyperledger-global-forum author: www title: www-tackling-diversity-interoperability-developers-at-hyperledger-global-forum date: None words: 931 flesch: 45 summary: In fact, to further explore what can be built with Hyperledger technologies, we’ll be hosting our second Blockchain for Good hackathon on Saturday and Sunday, December 15 and 16, immediately following Hyperledger Global Forum. Tackling Diversity, Interoperability & Developers at Hyperledger Global Forum – Hyperledger Foundation 2025 keywords: accenture; blockchain; hyperledger; interoperability cache: www-tackling-diversity-interoperability-developers-at-hyperledger-global-forum.html plain text: www-tackling-diversity-interoperability-developers-at-hyperledger-global-forum.txt item: #3219 of 3327 id: www-tackling-energy-security-and-climate-change-with-open-source-and-blockchain author: www title: www-tackling-energy-security-and-climate-change-with-open-source-and-blockchain date: None words: 959 flesch: 46 summary: Capturing and using this methane as natural gas would both increase the amount of energy available and reduce greenhouse gas emissions. This methane could also be sold as natural gas and used later  if it could be captured and transported. keywords: climate; emissions; gas; methane cache: www-tackling-energy-security-and-climate-change-with-open-source-and-blockchain.html plain text: www-tackling-energy-security-and-climate-change-with-open-source-and-blockchain.txt item: #3220 of 3327 id: www-tantalum-case-study-summary author: www title: www-tantalum-case-study-summary date: None words: 467 flesch: 27 summary: View previous blog post Back to all blog posts View next blog post The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Supply Chain | Hyperledger Fabric Conflict minerals and child labour: Enabling better business with blockchain traceability Hyperledger Foundation | Jan 18, 2020 Solution UK-based Circulor created a unique traceability system with scanners, sensors, and weigh scales that generate reliable data at each step of the supply chain. keywords: decentralized; foundation; linux cache: www-tantalum-case-study-summary.html plain text: www-tantalum-case-study-summary.txt item: #3221 of 3327 id: www-tarek-elsayed author: www title: www-tarek-elsayed date: None words: 526 flesch: 18 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Mentorship Program | Hyperledger Solang Hyperledger Mentorship Spotlight: Implement a CLI for node interactions in Hyperledger Solang What I worked on: Project name: Implement a CLI for node interactions in Hyperledger Solang Read More Tarek Elsayed | Nov 28, 2023 keywords: blog; decentralized; hyperledger; project cache: www-tarek-elsayed.html plain text: www-tarek-elsayed.txt item: #3222 of 3327 id: www-telecom author: www title: www-telecom date: None words: 533 flesch: 14 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Hyperledger Aries | Project: Hyperledger Indy | Special Interest Group | Telecom Introducing the Telecom Decentralized Identity Network (TDIDN), a New Approach to Security, Efficiency and Privacy keywords: blog; decentralized; hyperledger; technologies cache: www-telecom.html plain text: www-telecom.txt item: #3223 of 3327 id: www-the-besu-maintainers author: www title: www-the-besu-maintainers date: None words: 565 flesch: 22 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: besu; blog; decentralized; hyperledger cache: www-the-besu-maintainers.html plain text: www-the-besu-maintainers.txt item: #3224 of 3327 id: www-the-case-for-open-development-as-the-foundation-for-central-bank-digital-currencies author: www title: www-the-case-for-open-development-as-the-foundation-for-central-bank-digital-currencies date: None words: 1886 flesch: 42 summary: It also invites in new technologies, which challenges complacency and inspires collaboration. Central banks from the Philippines to France and from Brazil to Norway are among the many that have embraced open development in their CBDC projects. keywords: cbdc; community; development; software; systems cache: www-the-case-for-open-development-as-the-foundation-for-central-bank-digital-currencies.html plain text: www-the-case-for-open-development-as-the-foundation-for-central-bank-digital-currencies.txt item: #3225 of 3327 id: www-the-case-for-open-development-as-the-foundation-for-central-bank-digital-currencies?hs_amp=true author: www title: www-the-case-for-open-development-as-the-foundation-for-central-bank-digital-currencies?hs_amp=true date: None words: 1573 flesch: 46 summary: Central banks from the Philippines to France and from Brazil to Norway are among the many that have embraced open development in their CBDC projects. Open development and innovation Countries are understandably moving judiciously as they research and trial their approaches to CBDCs. keywords: cbdc; community; development; software cache: www-the-case-for-open-development-as-the-foundation-for-central-bank-digital-currencies?hs_amp=true.html plain text: www-the-case-for-open-development-as-the-foundation-for-central-bank-digital-currencies?hs_amp=true.txt item: #3226 of 3327 id: www-the-dlt-landscape-becomes-the-hyperledger-dlt-landscape author: www title: www-the-dlt-landscape-becomes-the-hyperledger-dlt-landscape date: None words: 945 flesch: 38 summary: With innovation blossoming at the intersection with other technologies – whether emerging or more established – as well as in areas such as interoperability, smart contracts, tokenization, and usability, among other things, the DLT vendor landscape has changed immensely. By using the CNCF Landscape code – which is obviously open source, and used across many Linux Foundation projects – we were able to transform this framework into an interactive, living market segmentation (web) application. keywords: dlt; foundation; hyperledger; landscape cache: www-the-dlt-landscape-becomes-the-hyperledger-dlt-landscape.html plain text: www-the-dlt-landscape-becomes-the-hyperledger-dlt-landscape.txt item: #3227 of 3327 id: www-the-dlt-landscape-becomes-the-hyperledger-dlt-landscape?hs_amp=true author: www title: www-the-dlt-landscape-becomes-the-hyperledger-dlt-landscape?hs_amp=true date: None words: 635 flesch: 45 summary: With innovation blossoming at the intersection with other technologies – whether emerging or more established – as well as in areas such as interoperability, smart contracts, tokenization, and usability, among other things, the DLT vendor landscape has changed immensely. The DLT Landscape Becomes the Hyperledger DLT Landscape – Hyperledger Foundation Blog | LF Decentralized Trust The DLT Landscape Becomes the Hyperledger DLT Landscape – Hyperledger Foundation Written by Hyperledger | Apr 25, 2023 4:00:00 AM We are excited to announce that today the DLT Landscape officially becomes the Hyperledger DLT Landscape.  keywords: dlt; landscape cache: www-the-dlt-landscape-becomes-the-hyperledger-dlt-landscape?hs_amp=true.html plain text: www-the-dlt-landscape-becomes-the-hyperledger-dlt-landscape?hs_amp=true.txt item: #3228 of 3327 id: www-the-dutchess-project-a-tale-of-true-interoperability-between-multiple-blockchains author: www title: www-the-dutchess-project-a-tale-of-true-interoperability-between-multiple-blockchains date: None words: 1879 flesch: 53 summary: We can’t wait to see what folks build this year with Hyperledger technologies at the Building Blocks Hackathon prior to Consensus on May 12-13. Jonathan is the founder of the blockchain technology company HACERA, which works with several blockchain technology stacks to provide secure identity and access control management of users, devices and data on blockchains. keywords: blockchain; dutchess; game; hyperledger; player; project cache: www-the-dutchess-project-a-tale-of-true-interoperability-between-multiple-blockchains.html plain text: www-the-dutchess-project-a-tale-of-true-interoperability-between-multiple-blockchains.txt item: #3229 of 3327 id: www-the-giving-chain-blockchain-powering-generosity author: www title: www-the-giving-chain-blockchain-powering-generosity date: None words: 876 flesch: 45 summary: Compatibility and integration research is underway for multiple Hyperledger projects. Through distributed ledger technology, the model becomes decentralized, allowing for all parties to be able to track the donations live in a secure, trusted, and verifiable manner. keywords: chain; decentralized; linux; project cache: www-the-giving-chain-blockchain-powering-generosity.html plain text: www-the-giving-chain-blockchain-powering-generosity.txt item: #3230 of 3327 id: www-the-hyperledger-global-forum-community-fair-where-to-connect-with-people-who-share-your-interests author: www title: www-the-hyperledger-global-forum-community-fair-where-to-connect-with-people-who-share-your-interests date: None words: 905 flesch: 43 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog | Hyperledger Community The Hyperledger Global Forum Community Fair: Where to connect with people who share your interests Hyperledger | Aug 9, 2022 It has been over two years since we had a chance to get together in person and connect with Hyperledger community members from all over the world. To help people connect at HGF (#HyperledgerForum), we’re trying something that has been used in community events that Mozilla has run in the past. keywords: community; events; hyperledger; people cache: www-the-hyperledger-global-forum-community-fair-where-to-connect-with-people-who-share-your-interests.html plain text: www-the-hyperledger-global-forum-community-fair-where-to-connect-with-people-who-share-your-interests.txt item: #3231 of 3327 id: www-the-journey-to-becoming-a-hyperledger-contributor author: www title: www-the-journey-to-becoming-a-hyperledger-contributor date: None words: 1464 flesch: 58 summary: Let me outline the steps involved in contributing to open source code, especially for Hyperledger projects. I hope this article will motivate people to start contributing to open source projects in general, and Hyperledger in particular. keywords: code; hyperledger; project; source cache: www-the-journey-to-becoming-a-hyperledger-contributor.html plain text: www-the-journey-to-becoming-a-hyperledger-contributor.txt item: #3232 of 3327 id: www-the-journey-to-becoming-a-hyperledger-contributor?hs_amp=true author: www title: www-the-journey-to-becoming-a-hyperledger-contributor?hs_amp=true date: None words: 1153 flesch: 66 summary: Let me outline the steps involved in contributing to open source code, especially for Hyperledger projects. I hope this article will motivate people to start contributing to open source projects in general, and Hyperledger in particular. keywords: code; hyperledger; source cache: www-the-journey-to-becoming-a-hyperledger-contributor?hs_amp=true.html plain text: www-the-journey-to-becoming-a-hyperledger-contributor?hs_amp=true.txt item: #3233 of 3327 id: www-the-move-to-a-production-network-what-you-need-to-consider-and-how-hyperledger-fabric-can-help author: www title: www-the-move-to-a-production-network-what-you-need-to-consider-and-how-hyperledger-fabric-can-help date: None words: 1311 flesch: 33 summary: Fabric also provides a set of built-in tools for sensitive data management, such as private data collections and channels, as well as flexibility in the choice of identity management approach, such decentralized identity management and anonymous credentials.  For the permissioned blockchain technology implementation, identity management service plays a crucial role. keywords: blockchain; data; identity; management; network cache: www-the-move-to-a-production-network-what-you-need-to-consider-and-how-hyperledger-fabric-can-help.html plain text: www-the-move-to-a-production-network-what-you-need-to-consider-and-how-hyperledger-fabric-can-help.txt item: #3234 of 3327 id: www-the-new-york-times-recognizes-brian-behlendorf-as-one-of-the-top-10-most-influential-people-in-blockchain author: www title: www-the-new-york-times-recognizes-brian-behlendorf-as-one-of-the-top-10-most-influential-people-in-blockchain date: None words: 909 flesch: 42 summary: Hyperledger technologies run in production deployments and provide real value beyond finance as well. SAP, Oracle, GE, Amazon and Huawei announced Blockchain-as-a-Service products within the last year, all powered by Hyperledger technologies. keywords: brian; foundation; hyperledger; technologies cache: www-the-new-york-times-recognizes-brian-behlendorf-as-one-of-the-top-10-most-influential-people-in-blockchain.html plain text: www-the-new-york-times-recognizes-brian-behlendorf-as-one-of-the-top-10-most-influential-people-in-blockchain.txt item: #3235 of 3327 id: www-the-pathway-to-becoming-a-hyperledger-maintainer author: www title: www-the-pathway-to-becoming-a-hyperledger-maintainer date: None words: 1449 flesch: 57 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog | Hyperledger Aries The Pathway to Becoming a Hyperledger Maintainer Emily Fisher | Nov 3, 2021 When I first came across Hyperledger Aries, I was still a student at the University of Applied Sciences in Utrecht. Now, only two years later, my company (Animo) specializes in building SSI solutions using Hyperledger Aries and other SSI technologies, and I am one of the core contributors to a lot of the open source libraries built on top of it. keywords: aries; hyperledger; project; source cache: www-the-pathway-to-becoming-a-hyperledger-maintainer.html plain text: www-the-pathway-to-becoming-a-hyperledger-maintainer.txt item: #3236 of 3327 id: www-the-perun-community author: www title: www-the-perun-community date: None words: 509 flesch: 14 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; community; decentralized; hyperledger cache: www-the-perun-community.html plain text: www-the-perun-community.txt item: #3237 of 3327 id: www-the-power-of-collaboration-in-a-vendor-neutral-environment-an-interoperability-story author: www title: www-the-power-of-collaboration-in-a-vendor-neutral-environment-an-interoperability-story date: None words: 1354 flesch: 33 summary: To better understand the power of collaboration in a neutral environment, let’s examine a recent example—a pilot program convened by GS1 US to explore interoperable seafood traceability solutions.  EPCIS provided a consistent format and exchange protocol for sharing event data and transmitting key information from production to sale by uniformly facilitating the transmission of critical tracking events, such as whether a product had been shipped, received, packed, or transformed. keywords: collaboration; data; gs1; industry; standards cache: www-the-power-of-collaboration-in-a-vendor-neutral-environment-an-interoperability-story.html plain text: www-the-power-of-collaboration-in-a-vendor-neutral-environment-an-interoperability-story.txt item: #3238 of 3327 id: www-the-power-of-community-how-kaleido-works-with-hyperledger-foundation-to-advance-hyperledger-firefly-and-enterprise-blockchain-and-digital-asset-adoption author: www title: www-the-power-of-community-how-kaleido-works-with-hyperledger-foundation-to-advance-hyperledger-firefly-and-enterprise-blockchain-and-digital-asset-adoption date: None words: 764 flesch: 45 summary: Kaleido works with Hyperledger Foundation to advance Hyperledger FireFly 2025 Update: Off to a Fast Start!  While serving as maintainers helping to drive the development of Hyperledger FireFly, the Kaleido team was also engaging with the community as a Hyperledger Foundation member. keywords: foundation; hyperledger; kaleido cache: www-the-power-of-community-how-kaleido-works-with-hyperledger-foundation-to-advance-hyperledger-firefly-and-enterprise-blockchain-and-digital-asset-adoption.html plain text: www-the-power-of-community-how-kaleido-works-with-hyperledger-foundation-to-advance-hyperledger-firefly-and-enterprise-blockchain-and-digital-asset-adoption.txt item: #3239 of 3327 id: www-the-power-of-community-how-kaleido-works-with-hyperledger-foundation-to-advance-hyperledger-firefly-and-enterprise-blockchain-and-digital-asset-adoption?hs_amp=true author: www title: www-the-power-of-community-how-kaleido-works-with-hyperledger-foundation-to-advance-hyperledger-firefly-and-enterprise-blockchain-and-digital-asset-adoption?hs_amp=true date: None words: 453 flesch: 59 summary: Kaleido works with Hyperledger Foundation to advance Hyperledger FireFly Blog | LF Decentralized Trust Kaleido works with Hyperledger Foundation to advance Hyperledger FireFly Written by Hyperledger | May 17, 2023 5:50:00 AM Read the full case study here. While serving as maintainers helping to drive the development of Hyperledger FireFly, the Kaleido team was also engaging with the community as a Hyperledger Foundation member. keywords: hyperledger cache: www-the-power-of-community-how-kaleido-works-with-hyperledger-foundation-to-advance-hyperledger-firefly-and-enterprise-blockchain-and-digital-asset-adoption?hs_amp=true.html plain text: www-the-power-of-community-how-kaleido-works-with-hyperledger-foundation-to-advance-hyperledger-firefly-and-enterprise-blockchain-and-digital-asset-adoption?hs_amp=true.txt item: #3240 of 3327 id: www-the-return-of-the-hyperledger-summer-internship-program author: www title: www-the-return-of-the-hyperledger-summer-internship-program date: None words: 1177 flesch: 39 summary: We’ve put together an extensive line-up of internship projects proposed and led by active blockchain developers looking to expand Hyperledger projects and the technical community by teaming with the next generation of engineers. Contribution:Through developing both projects (iPython notebooks / code samples and browser-based authentication with DIDs), the Intern will be making an important contributions to future Hyperledger community members onboarding efforts, the Hyperledger Indy codebase and the entire decentralized identity ecosystem. keywords: code; community; decentralized; hyperledger; project cache: www-the-return-of-the-hyperledger-summer-internship-program.html plain text: www-the-return-of-the-hyperledger-summer-internship-program.txt item: #3241 of 3327 id: www-the-return-of-the-hyperledger-summer-internship-program?hs_amp=true author: www title: www-the-return-of-the-hyperledger-summer-internship-program?hs_amp=true date: None words: 866 flesch: 44 summary: We’ve put together an extensive line-up of internship projects proposed and led by active blockchain developers looking to expand Hyperledger projects and the technical community by teaming with the next generation of engineers. Hyperledger Identity WG On-boarding and Auth The Hyperledger Identity WG intern will be mentored by members of the Identity WG / Hyperledger Indy Maintainers and accomplish two main tasks: learn and develop an iPython notebooks for onboarding new community members and a browser-based authentication app using decentralized identifiers in Hyperledger Indy. keywords: community; hyperledger; project cache: www-the-return-of-the-hyperledger-summer-internship-program?hs_amp=true.html plain text: www-the-return-of-the-hyperledger-summer-internship-program?hs_amp=true.txt item: #3242 of 3327 id: www-the-role-of-decentralized-identity-in-implementing-the-white-house-national-cybersecurity-strategy author: www title: www-the-role-of-decentralized-identity-in-implementing-the-white-house-national-cybersecurity-strategy date: None words: 1220 flesch: 41 summary: One of the remarkable things we have seen with open source verifiable digital identity is that it has been embraced by businesses and governments alike: everyone who sees the technology in action immediately sees how it is the building block for digital transformation: a way to upgrade web2 and tangible infrastructure for creating web3. These goals are achievable and the route to making this strategy a success lies through open source decentralized identity technology. keywords: decentralized; foundation; identity; trust cache: www-the-role-of-decentralized-identity-in-implementing-the-white-house-national-cybersecurity-strategy.html plain text: www-the-role-of-decentralized-identity-in-implementing-the-white-house-national-cybersecurity-strategy.txt item: #3243 of 3327 id: www-the-role-of-decentralized-identity-in-implementing-the-white-house-national-cybersecurity-strategy?hs_amp=true author: www title: www-the-role-of-decentralized-identity-in-implementing-the-white-house-national-cybersecurity-strategy?hs_amp=true date: None words: 909 flesch: 46 summary: One of the remarkable things we have seen with open source verifiable digital identity is that it has been embraced by businesses and governments alike: everyone who sees the technology in action immediately sees how it is the building block for digital transformation: a way to upgrade web2 and tangible infrastructure for creating web3. As the CEO of one of the leading companies developing verifiable digital identity solutions (what we at Indicio call “Trusted Digital Ecosystems”) and as a board member of the Hyperledger Foundation, an organization that supports open source technologies based on digital ledger technology, this is a strategic goal to applaud. keywords: hyperledger; identity cache: www-the-role-of-decentralized-identity-in-implementing-the-white-house-national-cybersecurity-strategy?hs_amp=true.html plain text: www-the-role-of-decentralized-identity-in-implementing-the-white-house-national-cybersecurity-strategy?hs_amp=true.txt item: #3244 of 3327 id: www-the-social-impact-of-being author: www title: www-the-social-impact-of-being date: None words: 1289 flesch: 51 summary: Most of the western citizens have not one but many digital identities with them: a Google account, a Microsoft account, a Facebook account, etc.  Self-Sovereign Identity, Interoperability and Trust Hyperledger Indy, a distributed ledger built for the purpose of decentralized identity, will be a powerful tool to overcome this issue. keywords: decentralized; identity; indy; trust cache: www-the-social-impact-of-being.html plain text: www-the-social-impact-of-being.txt item: #3245 of 3327 id: www-tim-spring-co-chair-hyperledger-identity-sig author: www title: www-tim-spring-co-chair-hyperledger-identity-sig date: None words: 541 flesch: 15 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Next page > Submit a blog Blog guidelines RSS Hyperledger Aries | Hyperledger Community | Distributed Ledger Technology | Decentralized Identity Why You Should Join the Hyperledger Identity Special Interest Group It’s hard to overstate the importance of digital identity: It governs every interaction online,... Read More Tim Spring - Co-Chair Hyperledger Identity SIG | Jul 26, 2023 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; identity cache: www-tim-spring-co-chair-hyperledger-identity-sig.html plain text: www-tim-spring-co-chair-hyperledger-identity-sig.txt item: #3246 of 3327 id: www-tradewaltz-and-ntt-data-deliver-all-in-one-platform-for-global-trade-market-built-on-hyperledger-fabric author: www title: www-tradewaltz-and-ntt-data-deliver-all-in-one-platform-for-global-trade-market-built-on-hyperledger-fabric date: None words: 869 flesch: 41 summary: After identifying several more projects for digitization, NTT Data gathered several banks, insurance companies, cargo owners, and trade logistics companies and carriers and created a 13-company trade consortium. Fortunately, even before COVID hit, someone was already looking at ways to streamline global trade. keywords: case; platform; trade; tradewaltz cache: www-tradewaltz-and-ntt-data-deliver-all-in-one-platform-for-global-trade-market-built-on-hyperledger-fabric.html plain text: www-tradewaltz-and-ntt-data-deliver-all-in-one-platform-for-global-trade-market-built-on-hyperledger-fabric.txt item: #3247 of 3327 id: www-tradewaltz-and-ntt-data-deliver-all-in-one-platform-for-global-trade-market-built-on-hyperledger-fabric?hs_amp=true author: www title: www-tradewaltz-and-ntt-data-deliver-all-in-one-platform-for-global-trade-market-built-on-hyperledger-fabric?hs_amp=true date: None words: 551 flesch: 50 summary: After identifying several more projects for digitization, NTT Data gathered several banks, insurance companies, cargo owners, and trade logistics companies and carriers and created a 13-company trade consortium. Fortunately, even before COVID hit, someone was already looking at ways to streamline global trade. keywords: trade; tradewaltz cache: www-tradewaltz-and-ntt-data-deliver-all-in-one-platform-for-global-trade-market-built-on-hyperledger-fabric?hs_amp=true.html plain text: www-tradewaltz-and-ntt-data-deliver-all-in-one-platform-for-global-trade-market-built-on-hyperledger-fabric?hs_amp=true.txt item: #3248 of 3327 id: www-tram-vo-ceo-founder-of-mobi-the-mobility-open-blockchain-initiative author: www title: www-tram-vo-ceo-founder-of-mobi-the-mobility-open-blockchain-initiative date: None words: 545 flesch: 17 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page to... Read More Tram Vo, CEO & Founder of MOBI, the Mobility Open Blockchain Initiative | Feb 23, 2023 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-tram-vo-ceo-founder-of-mobi-the-mobility-open-blockchain-initiative.html plain text: www-tram-vo-ceo-founder-of-mobi-the-mobility-open-blockchain-initiative.txt item: #3249 of 3327 id: www-trust-over-ip author: www title: www-trust-over-ip date: None words: 536 flesch: 22 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page The Trust Registry Task Force (TRTF) at Trust Over IP... Read More Andor Kesselman, Darrell O’Donnell, Antti Kettunen, and Drummond Reed, editors of the TRQP spec | Apr 7, 2025 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; trust cache: www-trust-over-ip.html plain text: www-trust-over-ip.txt item: #3250 of 3327 id: www-trust-registry-query-protocol-trqp-v2.0-now-open-for-public-review author: www title: www-trust-registry-query-protocol-trqp-v2.0-now-open-for-public-review date: None words: 1200 flesch: 41 summary: You can explore the full API definition here: TRQP Swagger/OpenAPI Documentation Your Feedback Matters We invite trust registry operators, ecosystem architects, wallet developers, credential issuers, verifiers, and other stakeholders to review and provide feedback on TRQP before v2.0 goes final. Is auditor X authorized to conduct security audit Y in ecosystem Z? Is certification body X accredited to certify Y in ecosystem Z? For a complete overview of TRQP architecture, see this description on the ToIP wiki. keywords: ecosystem; query; registry; trqp; trust; v2.0 cache: www-trust-registry-query-protocol-trqp-v2.0-now-open-for-public-review.html plain text: www-trust-registry-query-protocol-trqp-v2.0-now-open-for-public-review.txt item: #3251 of 3327 id: www-trust-registry-query-protocol-trqp-v2.0-now-open-for-public-review?hs_amp=true author: www title: www-trust-registry-query-protocol-trqp-v2.0-now-open-for-public-review?hs_amp=true date: None words: 888 flesch: 47 summary: You can explore the full API definition here: TRQP Swagger/OpenAPI Documentation Your Feedback Matters We invite trust registry operators, ecosystem architects, wallet developers, credential issuers, verifiers, and other stakeholders to review and provide feedback on TRQP before v2.0 goes final. Is auditor X authorized to conduct security audit Y in ecosystem Z? Is certification body X accredited to certify Y in ecosystem Z? For a complete overview of TRQP architecture, see this description on the ToIP wiki. keywords: ecosystem; registry; trqp; trust cache: www-trust-registry-query-protocol-trqp-v2.0-now-open-for-public-review?hs_amp=true.html plain text: www-trust-registry-query-protocol-trqp-v2.0-now-open-for-public-review?hs_amp=true.txt item: #3252 of 3327 id: www-trust-your-supplier-a-case-study-in-faster-more-secure-vendor-onboarding-through-blockchain author: www title: www-trust-your-supplier-a-case-study-in-faster-more-secure-vendor-onboarding-through-blockchain date: None words: 720 flesch: 38 summary: Trust Your Supplier: a case study in faster, more secure vendor onboarding through blockchain – Hyperledger Foundation 2025 Update: Off to a Fast Start! Read on → Search Join About About Explore membership Members Technical Advisory Council Governing Board Speakers Bureau Staff FAQ Store Contact us Technologies Ledger technologies Interoperability Integration & implementation Decentralized identity Cryptographic tools & protocols Project matrix Labs All projects Deploy Certified service providers Vendor directory Training partners Participate Why get involved? How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Blog Trust Your Supplier: a case study in faster, more secure vendor onboarding through blockchain Hyperledger | May 28, 2020 While supplier management has garnered particular attention in recent weeks thanks to COVID-19-related demand surges, manufacturing disruptions and quality concerns, vetting and signing news suppliers has long been a challenge. Initial results show: Vendor onboarding cycle time cut from an average of 60 days to 3 days For buyers: 50% less cost to verify and maintain a supplier’s information For sellers: much faster time to first sale The Hyperledger team has worked closely with Chainyard and IBM Blockchain on a detailed case study about developing and rolling out this network, from concept to PoC to full production deployment. keywords: case; supplier; trust cache: www-trust-your-supplier-a-case-study-in-faster-more-secure-vendor-onboarding-through-blockchain.html plain text: www-trust-your-supplier-a-case-study-in-faster-more-secure-vendor-onboarding-through-blockchain.txt item: #3253 of 3327 id: www-tsc-approves-hyperledger-cactus-as-new-project author: www title: www-tsc-approves-hyperledger-cactus-as-new-project date: None words: 1634 flesch: 44 summary: Hyperledger Labs provides an easy way to test the technical and community viability of potential new Hyperledger projects. The move from Labs to the Hyperledger Greenhouse is an important step in the direction towards production-readiness Now is the time for end-user, SI, and vendor developers to participate in defining the architecture of blockchain integration service In the short six months since entering the Labs, Hyperledger Cactus has attracted significant attention and become a locus of collaboration between developers from our teams at Accenture and Fujitsu, and dozens of others working on DLT platforms both inside and outside Hyperledger. keywords: blockchain; cactus; hyperledger; integration; project cache: www-tsc-approves-hyperledger-cactus-as-new-project.html plain text: www-tsc-approves-hyperledger-cactus-as-new-project.txt item: #3254 of 3327 id: www-using-hyperledger-bevel-to-add-a-privacy-layer-to-permissioned-besu-networks author: www title: www-using-hyperledger-bevel-to-add-a-privacy-layer-to-permissioned-besu-networks date: None words: 1132 flesch: 45 summary: Using Hyperledger Bevel to add a privacy layer to permissioned Besu networks 2025 The PMT (or privacy marker transaction) is a pointer to that specific private transaction that will be validated by the validator nodes and distributed to every single node in the network. keywords: besu; bevel; privacy; transaction cache: www-using-hyperledger-bevel-to-add-a-privacy-layer-to-permissioned-besu-networks.html plain text: www-using-hyperledger-bevel-to-add-a-privacy-layer-to-permissioned-besu-networks.txt item: #3255 of 3327 id: www-using-hyperledger-bevel-to-add-a-privacy-layer-to-permissioned-besu-networks?hs_amp=true author: www title: www-using-hyperledger-bevel-to-add-a-privacy-layer-to-permissioned-besu-networks?hs_amp=true date: None words: 819 flesch: 52 summary: Using Hyperledger Bevel to add a privacy layer to permissioned Besu networks Blog | LF Decentralized Trust Using Hyperledger Bevel to add a privacy layer to permissioned Besu networks Written by Alvaro Picazo, Hyperledger Bevel Maintainer | Nov 14, 2024 6:46:08 PM The PMT (or privacy marker transaction) is a pointer to that specific private transaction that will be validated by the validator nodes and distributed to every single node in the network. keywords: bevel; transaction cache: www-using-hyperledger-bevel-to-add-a-privacy-layer-to-permissioned-besu-networks?hs_amp=true.html plain text: www-using-hyperledger-bevel-to-add-a-privacy-layer-to-permissioned-besu-networks?hs_amp=true.txt item: #3256 of 3327 id: www-victor-huang author: www title: www-victor-huang date: None words: 520 flesch: 16 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Hyperledger AnonCreds v2 ZKP-based Credential Revocation Manager Implementation Read More Victor Huang | Jan 17, 2025 The latest community news in your inbox Select the checkboxes below for the monthly decentralized digest and dev/weekly newsletters About LF Decentralized Trust The Linux Foundation's flagship organization for the development and deployment of decentralized systems and technologies. keywords: blog; decentralized; hyperledger; technologies cache: www-victor-huang.html plain text: www-victor-huang.txt item: #3257 of 3327 id: www-video-hyperledger-interviews-aaron-symanski-change-healthcare author: www title: www-video-hyperledger-interviews-aaron-symanski-change-healthcare date: None words: 821 flesch: 38 summary: Change Healthcare and other healthcare organizations have come together through this open forum with a mission to further education about appropriate applications for blockchain technologies in the healthcare industry. Representatives from Change Healthcare will be in the Hyperledger booth discussing insurance/clinical claims management as a blockchain for healthcare use case. keywords: blockchain; healthcare; hyperledger; technologies cache: www-video-hyperledger-interviews-aaron-symanski-change-healthcare.html plain text: www-video-hyperledger-interviews-aaron-symanski-change-healthcare.txt item: #3258 of 3327 id: www-video-hyperledger-interviews-gert-sylvest-co-founder-of-tradeshift author: www title: www-video-hyperledger-interviews-gert-sylvest-co-founder-of-tradeshift date: None words: 567 flesch: 41 summary: Hyperledger Interviews Gert Sylvest, Co-founder of Tradeshift Hyperledger | Aug 27, 2018 We are excited to feature Gert Sylvest from Hyperledger Premier Member Tradeshift in this month’s community spotlight. They’re exploring use cases from cross-border financing scenarios, trust, track and trace and supply chain management, and see business blockchain technologies playing a role across all of these. keywords: hyperledger; technologies; tradeshift cache: www-video-hyperledger-interviews-gert-sylvest-co-founder-of-tradeshift.html plain text: www-video-hyperledger-interviews-gert-sylvest-co-founder-of-tradeshift.txt item: #3259 of 3327 id: www-video-hyperledger-interviews-ram-jagadeesan-distinguished-engineer-cto-of-blockchain-incubation-at-cisco author: www title: www-video-hyperledger-interviews-ram-jagadeesan-distinguished-engineer-cto-of-blockchain-incubation-at-cisco date: None words: 648 flesch: 32 summary: In this video, filmed at Hyperledger Member Summit in Singapore, Ram shares his thoughts on the impact of blockchain across industry verticals, how the technology is being used today compared with its future potential, and how to fast-track blockchain technology adoption. CISCO joined Hyperledger because they are firm believers in open source, open standards and interoperability. keywords: blockchain; hyperledger; ram cache: www-video-hyperledger-interviews-ram-jagadeesan-distinguished-engineer-cto-of-blockchain-incubation-at-cisco.html plain text: www-video-hyperledger-interviews-ram-jagadeesan-distinguished-engineer-cto-of-blockchain-incubation-at-cisco.txt item: #3260 of 3327 id: www-video-hyperledger-interviews-william-zuo-ceo-and-founder-of-shanghai-gingkoo-financial-technology-co author: www title: www-video-hyperledger-interviews-william-zuo-ceo-and-founder-of-shanghai-gingkoo-financial-technology-co date: None words: 592 flesch: 37 summary: Hyperledger Interviews William Zuo, CEO and Founder of Shanghai Gingkoo Financial Technology Co. – Hyperledger Foundation 2025 We had the opportunity to sit down with CEO and Founder William Zuo during the 2017 Hyperledger Member Summit in Singapore to learn more about why they joined, and their experience migrating from using Ethereum to Hyperledger Fabric for their platform Starfish-chain. keywords: decentralized; gingkoo; hyperledger cache: www-video-hyperledger-interviews-william-zuo-ceo-and-founder-of-shanghai-gingkoo-financial-technology-co.html plain text: www-video-hyperledger-interviews-william-zuo-ceo-and-founder-of-shanghai-gingkoo-financial-technology-co.txt item: #3261 of 3327 id: www-want-to-influence-the-metaverse-see-you-at-hyperledger-global-forum author: www title: www-want-to-influence-the-metaverse-see-you-at-hyperledger-global-forum date: None words: 753 flesch: 52 summary: Hyperledger Global Forum creates a unique opportunity for us to come together and explore the opportunities ahead of us. See you at Hyperledger Global Forum – Hyperledger Foundation 2025 keywords: foundation; hyperledger; metaverse cache: www-want-to-influence-the-metaverse-see-you-at-hyperledger-global-forum.html plain text: www-want-to-influence-the-metaverse-see-you-at-hyperledger-global-forum.txt item: #3262 of 3327 id: www-wayne-collier-principal-product-manager-digital-asset author: www title: www-wayne-collier-principal-product-manager-digital-asset date: None words: 519 flesch: 15 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Blog | LF Decentralized Trust | Wayne Collier, Principal Product Manager, Digital Asset 2025 keywords: blog; decentralized; hyperledger; technologies cache: www-wayne-collier-principal-product-manager-digital-asset.html plain text: www-wayne-collier-principal-product-manager-digital-asset.txt item: #3263 of 3327 id: www-we-trade-turns-to-hyperledger-fabric-for-cross-industry-digital-trade-finance-platform author: www title: www-we-trade-turns-to-hyperledger-fabric-for-cross-industry-digital-trade-finance-platform date: None words: 1031 flesch: 42 summary: Digital Trade Finance Platform Hyperledger | Oct 19, 2021 Leverages open source blockchain and smart contracts to streamline trade finance process, drive growth for businesses and revenue opportunities for banks Read the full case study here. Now with the growing urgency for seamless, transparent, and traceable transactions amid the global pandemic, improving access to trade finance has proven to be more vital for economic recovery and a more effective public health response around the world. keywords: case; finance; hyperledger; platform; we.trade cache: www-we-trade-turns-to-hyperledger-fabric-for-cross-industry-digital-trade-finance-platform.html plain text: www-we-trade-turns-to-hyperledger-fabric-for-cross-industry-digital-trade-finance-platform.txt item: #3264 of 3327 id: www-we-trade-turns-to-hyperledger-fabric-for-cross-industry-digital-trade-finance-platform?hs_amp=true author: www title: www-we-trade-turns-to-hyperledger-fabric-for-cross-industry-digital-trade-finance-platform?hs_amp=true date: None words: 721 flesch: 50 summary: | LF Decentralized Trust we.trade Turns to Hyperledger Fabric for Cross-Industry Digital Trade Finance Platform – Hyperledger Foundation Written by Hyperledger | Oct 19, 2021 6:07:00 AM Leverages open source blockchain and smart contracts to streamline trade finance process, drive growth for businesses and revenue opportunities for banks Read the full case study here. Now with the growing urgency for seamless, transparent, and traceable transactions amid the global pandemic, improving access to trade finance has proven to be more vital for economic recovery and a more effective public health response around the world. keywords: hyperledger; platform; we.trade cache: www-we-trade-turns-to-hyperledger-fabric-for-cross-industry-digital-trade-finance-platform?hs_amp=true.html plain text: www-we-trade-turns-to-hyperledger-fabric-for-cross-industry-digital-trade-finance-platform?hs_amp=true.txt item: #3265 of 3327 id: www-web3j author: www title: www-web3j date: None words: 869 flesch: 24 summary: Read More Nischal Sharma and George Tebrean, Hyperledger Web3j maintainers and Blockchain Developers at Web3 Labs | Aug 29, 2024 Web3j Introducing Hyperledger Web3j, the Ethereum Integration Library for Enterprises We are very excited to announce the newest Hyperledger project, Hyperledger Web3j. The... Read More Nischal Sharma, Hyperledger Webj3 maintainer and Blockchain Developer at Web3 Labs | Oct 8, 2024 Web3j Hyperledger Web3j in 2024: Updates for Blockchain Developers Since its introduction in February 2024, maintainers have focused on significantly enhancing Hyperledger Web3j, a crucial tool for Java and Android developers working within the... keywords: decentralized; hyperledger; labs; web3j cache: www-web3j.html plain text: www-web3j.txt item: #3266 of 3327 id: www-wecan-comply-how-to-use-the-hyperledger-fabric-blockchain-for-real-time-compliance-auditing author: www title: www-wecan-comply-how-to-use-the-hyperledger-fabric-blockchain-for-real-time-compliance-auditing date: None words: 1350 flesch: 41 summary: Our ambition is then to apply this method to all regulated professions where there are standards in order to guarantee a monitoring and audit of compliance in real time. Custodian banks save time by accessing in one place standard and structured information coming from their EAM. keywords: banks; compliance; comply; time; wecan cache: www-wecan-comply-how-to-use-the-hyperledger-fabric-blockchain-for-real-time-compliance-auditing.html plain text: www-wecan-comply-how-to-use-the-hyperledger-fabric-blockchain-for-real-time-compliance-auditing.txt item: #3267 of 3327 id: www-wecan-comply-how-to-use-the-hyperledger-fabric-blockchain-for-real-time-compliance-auditing?hs_amp=true author: www title: www-wecan-comply-how-to-use-the-hyperledger-fabric-blockchain-for-real-time-compliance-auditing?hs_amp=true date: None words: 1040 flesch: 45 summary: Our ambition is then to apply this method to all regulated professions where there are standards in order to guarantee a monitoring and audit of compliance in real time. Custodian banks save time by accessing in one place standard and structured information coming from their EAM. keywords: compliance; time; wecan cache: www-wecan-comply-how-to-use-the-hyperledger-fabric-blockchain-for-real-time-compliance-auditing?hs_amp=true.html plain text: www-wecan-comply-how-to-use-the-hyperledger-fabric-blockchain-for-real-time-compliance-auditing?hs_amp=true.txt item: #3268 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resource author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resource date: None words: 977 flesch: 38 summary: May 21 deadline for Hyperledger Global Forum Scholarships applications Hyperledger is committed to making Hyperledger Global Forum as accessible as possible. One key initiative it a scholarship program that provides support to traditionally underrepresented and/or marginalized persons in the technology and/or open source communities (including, but not limited to, persons identifying as LGBT, women, persons of color, and/or persons with disabilities) who may not otherwise have the opportunity to attend Hyperledger events for financial reasons. keywords: blockchain; decentralized; events; hyperledger; update cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resource.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resource.txt item: #3269 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resource-4 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resource-4 date: None words: 776 flesch: 39 summary: A guide to building and deploying Hyperledger Fabric on the Azure Cloud Platform Linux Foundation Training recently published part 1 and part 2 in the series “Build and Deploy Hyperledger Fabric on Azure Cloud Platform.”  Virtual Meetups – Coming up after Hyperledger Global Forum Wednesday, June 16, at 16:00 UTC / 9:00 PDT: Hyperledger Training and Certification Discount Hyperledger and Linux Foundation training have teamed up to offer 50% off the list price of Hyperledger training and certifications during the month of June! keywords: blockchain; foundation; hyperledger; training cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resource-4.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resource-4.txt item: #3270 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-19 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-19 date: None words: 701 flesch: 36 summary: New “Hyperledger Fabric for Developers” Class  Linux Foundation Training has launched a new class designed for developers who want to master Hyperledger Fabric chaincode – Fabric’s smart contracts – and application development. Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 keywords: blockchain; foundation; hyperledger; linux cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-19.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-19.txt item: #3271 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-20 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-20 date: None words: 690 flesch: 39 summary: Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 Webinar: A public decentralized ordering service for Hyperledger Fabric using Hedera Hashgraph Join Donald Thibeau of Hedera to hear more about the Pluggable Hedera Consensus Service, a Hyperledger Lab that enables a Hyperledger Fabric network to use the Hedera Consensus Service (HCS) for transaction ordering.  keywords: august; blockchain; decentralized; hyperledger cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-20.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-20.txt item: #3272 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-21 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-21 date: None words: 575 flesch: 39 summary: Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 Hyperledger Sweden hosts “Online Certification Study Circle” Saturday, August 29, at 15:00 UTC / 17:00 EET: Hyperledger Libya Meetup Launch Event See the full Virtual Meetup schedule here.  keywords: case; decentralized; hyperledger cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-21.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-21.txt item: #3273 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-22 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-22 date: None words: 635 flesch: 40 summary: Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 And don’t miss Hyperledger’s Marta Piekarska-Geater’s presentation on “Hyperledger Greenhouse and its best applications” on September 3 at at 2:30 p.m. BST.  keywords: blockchain; decentralized; hyperledger; technologies cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-22.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-22.txt item: #3274 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-26 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-26 date: None words: 726 flesch: 38 summary: Webinar: Umbra – Challenges with Hyperledger Fabric simulation and debugging of applications This webinar showcases Umbra, an emulation tool for Hyperledger blockchains. Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 keywords: blockchain; decentralized; hyperledger; technologies cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-26.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-26.txt item: #3275 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-32 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-32 date: None words: 818 flesch: 39 summary: It brings together experts across financial services, technology, and open source to engage the community in stimulating and thought-provoking conversations about how to best (and safely) leverage open source software to solve industry challenges. Open Source Strategy Forum (OSSF) is the only conference dedicated to driving collaboration and innovation in financial services through open source software and standards. keywords: hyperledger; november; source; technologies cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-32.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-32.txt item: #3276 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-35 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-35 date: None words: 720 flesch: 34 summary: Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 CET: Hyperledger Barcelona hosts “Hyperledger Fabric para Administradores VS Developers – Certificaciones” (Spanish) Thursday, December 10, at 18:00 UTC / 11:00 MST: Hyperledger Denver hosts “Hyperledger Fabric for System Administrators vs Developers” See the full Virtual Meetup schedule here.  keywords: blockchain; december; decentralized; hyperledger cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-35.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-35.txt item: #3277 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-42 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-42 date: None words: 808 flesch: 37 summary: Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 And, once again, half of the companies on the list are using Hyperledger technology. keywords: blockchain; climate; foundation; hyperledger cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-42.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-42.txt item: #3278 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-43 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-43 date: None words: 876 flesch: 41 summary: Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 Hyperledger Healthcare Special Interest Group Guest Speaker: John Walker, COVID-19 Credentials Initiative and Linux Foundation Public Health Join the Healthcare SIG meeting for a talk by John Walker from the COVID-19 Credentials Initiative and Linux Foundation Public Health team. keywords: foundation; hyperledger; identity; linux cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-43.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-43.txt item: #3279 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-45 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-45 date: None words: 717 flesch: 41 summary: CET: Hyperledger Madrid hosts “La nueva Red H+ de Alastria basada en Hyperledger Fabric” (Spanish) Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 keywords: decentralized; foundation; hyperledger; linux cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-45.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-45.txt item: #3280 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-5 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-5 date: None words: 617 flesch: 42 summary: Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 We will have more details on enterprise blockchain sessions next week.  keywords: decentralized; foundation; linux cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-5.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-5.txt item: #3281 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-53 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-53 date: None words: 913 flesch: 43 summary: Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 Hyperledger Global Forum (HGF) agenda announced The agenda details for Hyperledger Global Forum (June 8-10) went live this week. keywords: blockchain; decentralized; foundation; hyperledger; linux cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-53.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-53.txt item: #3282 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-54 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-54 date: None words: 919 flesch: 44 summary: Call to Action: Help Shape Blockchain Training and Education Besu Certification input needed The Linux Foundation and Hyperledger are planning a Hyperledger Besu certification program and need your help. Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 keywords: alastria; blockchain; hyperledger; technologies cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-54.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-54.txt item: #3283 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-60 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-60 date: None words: 1241 flesch: 43 summary: Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 This transparency enables companies to provide real product carbon footprint information to their customers. keywords: blockchain; carbon; hyperledger; palm; project cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-60.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-60.txt item: #3284 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-61 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-61 date: None words: 875 flesch: 44 summary: Input Wanted: Survey on Diversity, Equity, & Inclusion in Open Source The Linux Foundation and its partners are researching areas related to diversity, equity, and inclusion (DEI) within open source communities in order to better understand contributor demographics and dynamics concerning overall participation. The objective is to identify sentiments and gaps to be addressed in open source communities specifically, as a means to advancing inclusive cultures in these environments. keywords: foundation; linux; report; source cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-61.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-61.txt item: #3285 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-66 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-66 date: None words: 749 flesch: 39 summary: Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 Linux Foundation Training Back to School Sale Buy any of the Linux Foundations certification exams and get the companion training course for free. keywords: blockchain; hyperledger; linux; training cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-66.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-66.txt item: #3286 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-71 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-71 date: None words: 960 flesch: 41 summary: The report reveals the latest trends in open source careers, which skills are in demand, what motivates open source professionals, how employers can attract and retain top talent, how the COVID-19 pandemic impacted hiring and workplaces, and diversity issues in the industry. 2021 Open Source Jobs Report Linux Foundation Training, in partnership with edX and Linux Foundation Research, has completed its 9th annual Open Source Jobs Report. keywords: blockchain; foundation; hyperledger; linux; september cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-71.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-71.txt item: #3287 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-72 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-72 date: None words: 689 flesch: 36 summary: New Hyperledger FireFly project  The newest project, Hyperledger FireFly, became official this week. Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 keywords: decentralized; foundation; hyperledger; project cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-72.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-72.txt item: #3288 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-74 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-74 date: None words: 809 flesch: 43 summary: Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 Data distribution in P2P networks is a well-studied concept in the literature, with Gnutella being an example of a network offering such services. keywords: blockchain; data; decentralized; hyperledger cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-74.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-74.txt item: #3289 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-76 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-76 date: None words: 784 flesch: 40 summary: Virtual Meetups  Thursday, November 4, at 16:00 UTC / 17:00 CET: Hyperledger Budapest hosts “Deploying Hyperledger Fabric on Kubernetes 2.3+ with a Kubernetes Operator” Thursday, November 4, at 22:30 UTC / 18:30 EDT: Hyperledger Boston hosts “What are Blockchain Employers Looking for in a Candidate?” See the full Virtual Meetup schedule here. Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 keywords: blockchain; case; decentralized; hyperledger cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-76.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-76.txt item: #3290 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-78 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-78 date: None words: 721 flesch: 37 summary: Fireside Chat: Wharton Executive Education “the Economics of Blockchain and Digital Assets” program with Dr. Cathy Barrera In a preview of the Wharton Executive Education “The Economics of Blockchain and Digital Assets” course, the program director, Dr. Cathy Barrera, founding economist at Prysm Group, will join Hyperledger Foundation Executive Director Daniela Barbosa for a fireside chat. Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 keywords: blockchain; case; decentralized; hyperledger cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-78.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-78.txt item: #3291 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-79 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-79 date: None words: 1239 flesch: 47 summary: He will discuss how to collect and act on Hyperledger Fabric data to minimize downtime and reduce the meantime to detect and respond to incidents. Hyperledger In-depth: An hour with Splunk Security monitoring of Hyperledger Fabric networks requires ingesting and aggregating ledger, log, and metric data from many sources. keywords: blockchain; events; foundation; hyperledger; november; project cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-79.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-79.txt item: #3292 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-80 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-80 date: None words: 619 flesch: 39 summary: Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 Linux Foundation Training Cyber Monday Sale Cyber Monday is a week long at Linux Foundation Training. keywords: foundation; hyperledger; training cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-80.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-80.txt item: #3293 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-81 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-81 date: None words: 806 flesch: 38 summary: Weekend Update: This Week’s Round-up of Remote Blockchain Learning Resources – Hyperledger Foundation 2025 Hyperledger Mentorship Project Reports This month, a cohort of mentees from the Hyperledger Mentorship Program wrapped up their projects and presented their work. keywords: blockchain; december; foundation; hyperledger cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-81.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-81.txt item: #3294 of 3327 id: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-9 author: www title: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-9 date: None words: 637 flesch: 43 summary: Blockchain Stories 2020 Find out what businesses in Asia Pacific are building using Hyperledger projects at this virtual event hosted by the Hyperledger India Chapter on Saturday, May 30, at 10a.m. New Hyperledger Labs project explained Donald Thibeau of Hedera presented Hedera Hashgraph and the newly submitted Hyperledger Labs project for providing a plugging into Hyperledger Fabric (and Avalon) at a recent meetup.  keywords: decentralized; hyperledger; resources cache: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-9.html plain text: www-weekend-update-this-weeks-round-up-of-remote-blockchain-learning-resources-9.txt item: #3295 of 3327 id: www-welcome-chris-sutton author: www title: www-welcome-chris-sutton date: None words: 701 flesch: 38 summary: Welcome, Chris Sutton Dfns Secures $16M Series A Funding – See the Full Announcement Product Wallets-as-a-Service Platform (WaaS) Wallet Entitlement Management (WEM) Key Deployment Service (KDS) Integrations Developers Docs Github Changelog Status Resources Security Labs Blog FAQ Company Careers Newsroom About PricingGet started Talk to sales Get started Blog Update Welcome, Chris Sutton UpdateWelcome, Chris Sutton Christopher Grilhault des Fontaines February 20, 2025 Read time: Chris Sutton has been appointed Head of Product at Dfns to bring deep expertise in blockchain finance, stablecoin payments, and digital asset innovation. We are excited to welcome Chris Sutton as our new Head of Product at Dfns. keywords: blockchain; chris; dfns; product cache: www-welcome-chris-sutton.html plain text: www-welcome-chris-sutton.txt item: #3296 of 3327 id: www-welcome-david-boswell-hyperledgers-director-developer-ecosystems author: www title: www-welcome-david-boswell-hyperledgers-director-developer-ecosystems date: None words: 964 flesch: 53 summary: I’ve found this to be extremely powerful advice for open source communities.   One of my main goals is to bring in my experience of what has worked (and not worked) in other open source communities. keywords: community; david; hyperledger cache: www-welcome-david-boswell-hyperledgers-director-developer-ecosystems.html plain text: www-welcome-david-boswell-hyperledgers-director-developer-ecosystems.txt item: #3297 of 3327 id: www-welcome-hyperledger-iroha-1-0-flattening-the-dlt-learning-curve author: www title: www-welcome-hyperledger-iroha-1-0-flattening-the-dlt-learning-curve date: None words: 1112 flesch: 47 summary: Hyperledger Iroha provides safety with its decentralized consensus algorithm and reliability with a tested set of commands and queries. Try it – simplicity and friendly support from the community will surely help you find your own way of improving your project with Hyperledger Iroha blockchain. keywords: decentralized; hyperledger; iroha; use cache: www-welcome-hyperledger-iroha-1-0-flattening-the-dlt-learning-curve.html plain text: www-welcome-hyperledger-iroha-1-0-flattening-the-dlt-learning-curve.txt item: #3298 of 3327 id: www-welcome-hyperledger-iroha-1-0-flattening-the-dlt-learning-curve?hs_amp=true author: www title: www-welcome-hyperledger-iroha-1-0-flattening-the-dlt-learning-curve?hs_amp=true date: None words: 803 flesch: 53 summary: Hyperledger Iroha provides safety with its decentralized consensus algorithm and reliability with a tested set of commands and queries. Try it – simplicity and friendly support from the community will surely help you find your own way of improving your project with Hyperledger Iroha blockchain. keywords: business; hyperledger; iroha cache: www-welcome-hyperledger-iroha-1-0-flattening-the-dlt-learning-curve?hs_amp=true.html plain text: www-welcome-hyperledger-iroha-1-0-flattening-the-dlt-learning-curve?hs_amp=true.txt item: #3299 of 3327 id: www-welcome-hyperledger-ursa author: www title: www-welcome-hyperledger-ursa date: None words: 1279 flesch: 36 summary: Ursa’s objective is to make it much safer and easier for our distributed ledger projects to use existing, time tested, and trusted cryptographic libraries but also new cryptographic library implementations being developed. As Hyperledger has matured, the individual projects within Hyperledger have started to find a need for sophisticated cryptographic implementations. keywords: code; hyperledger; library; ursa cache: www-welcome-hyperledger-ursa.html plain text: www-welcome-hyperledger-ursa.txt item: #3300 of 3327 id: www-welcome-maud-tezenas-du-montcel author: www title: www-welcome-maud-tezenas-du-montcel date: None words: 722 flesch: 35 summary: Welcome, Maud Tezenas du Montcel Dfns Secures $16M Series A Funding – See the Full Announcement Product Wallets-as-a-Service Platform (WaaS) Wallet Entitlement Management (WEM) Key Deployment Service (KDS) Integrations Developers Docs Github Changelog Status Resources Security Labs Blog FAQ Company Careers Newsroom About PricingGet started Talk to sales Get started Blog Update Welcome, Maud Tezenas du Montcel UpdateWelcome, Maud Tezenas du Montcel Clarisse Hagège March 17, 2025 Read time: Maud Tezenas du Montcel joins Dfns as Head of Marketing to drive brand leadership, growth, and institutional adoption of secure digital asset wallets. Expand thought leadership on institutional wallet security, MPC technology, compliance, and risk management in digital assets. keywords: dfns; marketing; maud; security cache: www-welcome-maud-tezenas-du-montcel.html plain text: www-welcome-maud-tezenas-du-montcel.txt item: #3301 of 3327 id: www-welcome-thibaud-harrison author: www title: www-welcome-thibaud-harrison date: None words: 573 flesch: 43 summary: Welcome, Thibaud & Harrison Dfns Secures $16M Series A Funding – See the Full Announcement Product Wallets-as-a-Service Platform (WaaS) Wallet Entitlement Management (WEM) Key Deployment Service (KDS) Integrations Developers Docs Github Changelog Status Resources Security Labs Blog FAQ Company Careers Newsroom About PricingGet started Talk to sales Get started Blog Update Welcome, Thibaud & Harrison UpdateWelcome, Thibaud & Harrison Christopher Grilhault des Fontaines April 21, 2025 Read time: Welcoming two new members to Dfns’ engineering team: Harrison Tross and Thibaud Genty. Check them out here: welcometothejungle.com/en/companies/dfns/jobs ‍ Authors Christopher Grilhault des Fontaines Co-CEO & Co-founder Christopher Grilhault des Fontaines is the co-CEO and co-founder of Dfns. keywords: dfns; harrison; thibaud cache: www-welcome-thibaud-harrison.html plain text: www-welcome-thibaud-harrison.txt item: #3302 of 3327 id: www-welcome-to-linux-foundation-decentralized-trust author: www title: www-welcome-to-linux-foundation-decentralized-trust date: None words: 993 flesch: 44 summary: LF Decentralized Trust builds on the solid foundation of an almost decade-long journey for our communities, where we’ve seen remarkable growth in blockchain and digital identity projects. Welcome to Linux Foundation Decentralized Trust! keywords: decentralized; foundation; technologies; trust cache: www-welcome-to-linux-foundation-decentralized-trust.html plain text: www-welcome-to-linux-foundation-decentralized-trust.txt item: #3303 of 3327 id: www-welcome-to-linux-foundation-decentralized-trust?hs_amp=true author: www title: www-welcome-to-linux-foundation-decentralized-trust?hs_amp=true date: None words: 682 flesch: 51 summary: Some of the key areas we’re already focusing on include cryptographic schemes and multi-party computations (MPC) through new projects like Lockness, as well as expanding decentralized synchronization infrastructure for the Canton Network with the new lab Splice and privacy for Besu with the new lab Zeto. Whether you’re interested in building new projects, contributing code, or simply exploring the possibilities of decentralized systems, there’s a place for you here. keywords: decentralized; trust cache: www-welcome-to-linux-foundation-decentralized-trust?hs_amp=true.html plain text: www-welcome-to-linux-foundation-decentralized-trust?hs_amp=true.txt item: #3304 of 3327 id: www-welcome-to-the-new-hyperledger-foundation-look author: www title: www-welcome-to-the-new-hyperledger-foundation-look date: None words: 790 flesch: 47 summary: Daniela Barbosa, Executive Director at Hyperledger Foundation and General Manager, Blockchain and Identity for the Linux Foundation | Aug 1, 2023 Time flies when you are making new markets. Welcome to the new Hyperledger Foundation look! keywords: foundation; hyperledger; technologies cache: www-welcome-to-the-new-hyperledger-foundation-look.html plain text: www-welcome-to-the-new-hyperledger-foundation-look.txt item: #3305 of 3327 id: www-welcome-to-the-new-hyperledger-foundation-look?hs_amp=true author: www title: www-welcome-to-the-new-hyperledger-foundation-look?hs_amp=true date: None words: 478 flesch: 59 summary: Written by Daniela Barbosa, Executive Director at Hyperledger Foundation and General Manager, Blockchain and Identity for the Linux Foundation | Aug 1, 2023 2:52:53 PM Time flies when you are making new markets. Welcome to the new Hyperledger Foundation look! keywords: foundation cache: www-welcome-to-the-new-hyperledger-foundation-look?hs_amp=true.html plain text: www-welcome-to-the-new-hyperledger-foundation-look?hs_amp=true.txt item: #3306 of 3327 id: www-welcome-to-the-new-hyperledger-foundation-marketing-committee-leaders author: www title: www-welcome-to-the-new-hyperledger-foundation-marketing-committee-leaders date: None words: 1984 flesch: 53 summary: Helen: If you haven’t picked up on it already, my goal this year is to entice more Hyperledger Foundation members to interact with the marketing committee. Welcome to the new Hyperledger Foundation Marketing Committee leaders – Hyperledger Foundation 2025 keywords: committee; foundation; hyperledger; marketing; members cache: www-welcome-to-the-new-hyperledger-foundation-marketing-committee-leaders.html plain text: www-welcome-to-the-new-hyperledger-foundation-marketing-committee-leaders.txt item: #3307 of 3327 id: www-welcome-to-the-new-hyperledger-foundation-marketing-committee-leaders?hs_amp=true author: www title: www-welcome-to-the-new-hyperledger-foundation-marketing-committee-leaders?hs_amp=true date: None words: 1676 flesch: 57 summary: Helen: If you haven’t picked up on it already, my goal this year is to entice more Hyperledger Foundation members to interact with the marketing committee. Welcome to the new Hyperledger Foundation Marketing Committee leaders – Hyperledger Foundation Blog | LF Decentralized Trust Welcome to the new Hyperledger Foundation Marketing Committee leaders – Hyperledger Foundation Written by Hyperledger | Mar 1, 2023 9:30:00 AM Codified in the Hyperledger Foundation Charter, the Hyperledger Foundation Marketing Committee is a driving force in the work we do building the enterprise blockchain market. keywords: committee; foundation; hyperledger; marketing cache: www-welcome-to-the-new-hyperledger-foundation-marketing-committee-leaders?hs_amp=true.html plain text: www-welcome-to-the-new-hyperledger-foundation-marketing-committee-leaders?hs_amp=true.txt item: #3308 of 3327 id: www-whats-on-the-agenda-at-hyperledger-global-forum-2022 author: www title: www-whats-on-the-agenda-at-hyperledger-global-forum-2022 date: None words: 1011 flesch: 14 summary: Workshop: How To Build a Self-Sovereign Identity Agent With Hyperledger Aries Framework JavaScript – Timo Glastra & Berend Sliedrecht, ANIMO & Jakub Koci, ABSA Enterprise Blockchain Taking on Challenges of Enterprise Blockchain Infrastructures – Dr. Ravi Chamria & Ghan Vashishtha, Zeeve Latest Technology Adoption Trends in Enterprise Blockchain Projects – Jim Zhang, Kaleido & Tracy Kuhrt, Accenture Solving Market Problems With Open Source Verifiable Credentials – Heather Dahl, Indicio & Mike Vesey, IdRamp Design Patterns to Practically Scale Blockchain Networks – Deepika Karanji & Arun S M, Walmart Global Technology Services Why You Shouldn’t Just Trust Your Blockchain – And Apply Critical System Design – Imre Kocsis, Budapest University of Technology and Economics Hands-on ½ Day Workshops Workshop: Moving Central Bank Digital Currency from Conception to Reality with Hyperledger Technologies – Elli Androulaki & Angelo De Caro, IBM Workshop: How to Build Full-Stack Web3 Apps Faster with FireFly SuperNodes – Nicko Guyer, Kaleido Workshop: Developing Interoperability Applications with Hyperledger Cactus – Peter Somogyvari, Accenture Workshop : Developing Applications with Hyperledger Fabric – Josh Kneubuhl, IBM Workshop: Hyperledger Bevel – Sownak Roy & Suvajit Sarkar, Accenture Workshop: How To Build a Self-Sovereign Identity Agent With Hyperledger Aries Framework JavaScript – Timo Glastra & Berend Sliedrecht, ANIMO & Jakub Koci, ABSA Come join us for these sessions and more as well as non-stop networking, knowledge sharing and collaboration. Making Distributed Ledgers Interoperable Using Weaver (Hyperledger Labs) – Venkatraman Ramakrishna, IBM Workshop: Moving Central Bank Digital Currency from Conception to Reality with Hyperledger Technologies – Elli Androulaki & Angelo De Caro, IBM Digital Identity Enabling Interoperability and Multi-Ledger Support for Decentralized Identity Platforms – Hitarshi Buch, Wipro Technologies Findy Agency — Highway to Verified Data Networks – Laura Vuorenoja & Harri Lainio, OP Financial Group Digital Identity Using the vLEI – Christoph Schneider, Global Legal Entity Identifier Foundation (GLEIF) keywords: decentralized; digital; foundation; hyperledger; identity; technologies; workshop cache: www-whats-on-the-agenda-at-hyperledger-global-forum-2022.html plain text: www-whats-on-the-agenda-at-hyperledger-global-forum-2022.txt item: #3309 of 3327 id: www-whats-on-the-agenda-at-hyperledger-global-forum-2022?hs_amp=true author: www title: www-whats-on-the-agenda-at-hyperledger-global-forum-2022?hs_amp=true date: None words: 696 flesch: 5 summary: What's on the agenda at Hyperledger Global Forum 2022 – Hyperledger Foundation Blog | LF Decentralized Trust What's on the agenda at Hyperledger Global Forum 2022 – Hyperledger Foundation Written by Hyperledger | Jul 26, 2022 7:00:00 AM We are just weeks away from gathering in Dublin, Ireland, for Hyperledger Global Forum 2022. Workshop: How To Build a Self-Sovereign Identity Agent With Hyperledger Aries Framework JavaScript – Timo Glastra & Berend Sliedrecht, ANIMO & Jakub Koci, ABSA Enterprise Blockchain Taking on Challenges of Enterprise Blockchain Infrastructures – Dr. Ravi Chamria & Ghan Vashishtha, Zeeve Latest Technology Adoption Trends in Enterprise Blockchain Projects – Jim Zhang, Kaleido & Tracy Kuhrt, Accenture Solving Market Problems With Open Source Verifiable Credentials – Heather Dahl, Indicio & Mike Vesey, IdRamp Design Patterns to Practically Scale Blockchain Networks – Deepika Karanji & Arun S M, Walmart Global Technology Services Why You Shouldn’t Just Trust Your Blockchain – And Apply Critical System Design – Imre Kocsis, Budapest University of Technology and Economics Hands-on ½ Day Workshops Workshop: Moving Central Bank Digital Currency from Conception to Reality with Hyperledger Technologies – Elli Androulaki & Angelo De Caro, IBM Workshop: How to Build Full-Stack Web3 Apps Faster with FireFly SuperNodes – Nicko Guyer, Kaleido Workshop: Developing Interoperability Applications with Hyperledger Cactus – Peter Somogyvari, Accenture Workshop : Developing Applications with Hyperledger Fabric – Josh Kneubuhl, IBM Workshop: Hyperledger Bevel – Sownak Roy & Suvajit Sarkar, Accenture Workshop: How To Build a Self-Sovereign Identity Agent With Hyperledger Aries Framework JavaScript – Timo Glastra & Berend Sliedrecht, ANIMO & Jakub Koci, ABSA Come join us for these sessions and more as well as non-stop networking, knowledge sharing and collaboration. keywords: digital; global; hyperledger; identity; workshop cache: www-whats-on-the-agenda-at-hyperledger-global-forum-2022?hs_amp=true.html plain text: www-whats-on-the-agenda-at-hyperledger-global-forum-2022?hs_amp=true.txt item: #3310 of 3327 id: www-when-hyperledger-sawtooth-met-kubernetes-simplifying-enterprise-blockchain-adoption author: www title: www-when-hyperledger-sawtooth-met-kubernetes-simplifying-enterprise-blockchain-adoption date: None words: 684 flesch: 28 summary: With their team’s  background in open source, operations and cloud, BTP quickly realised that CNCF’s Kubernetes was the perfect match for Hyperledger Sawtooth. The power of open source collaboration doesn’t end there as BTP have now teamed up with Digital Asset to bring DAML Smart Contracts to Hyperledger Sawtooth – integrating their open source DAML runtime with Sawtooth, similar to the way the Sawtooth Ethereum (SETH) project integrates the Burrow EVM with Sawtooth, and handling its deployment and management with Sextant. keywords: foundation; hyperledger; sawtooth cache: www-when-hyperledger-sawtooth-met-kubernetes-simplifying-enterprise-blockchain-adoption.html plain text: www-when-hyperledger-sawtooth-met-kubernetes-simplifying-enterprise-blockchain-adoption.txt item: #3311 of 3327 id: www-where-to-find-hyperledger-at-consensus-distributed author: www title: www-where-to-find-hyperledger-at-consensus-distributed date: None words: 717 flesch: 43 summary: Where to find Hyperledger at Consensus: Distributed – Hyperledger Foundation 2025 We’ll then transition the conversation to Hyperledger Avalon, one of the latest projects to join the greenhouse. keywords: decentralized; hyperledger; project cache: www-where-to-find-hyperledger-at-consensus-distributed.html plain text: www-where-to-find-hyperledger-at-consensus-distributed.txt item: #3312 of 3327 id: www-why-distributed-ledger-technology-dlt-for-identity author: www title: www-why-distributed-ledger-technology-dlt-for-identity date: None words: 1850 flesch: 52 summary: To understand why DLT is useful for identity, we need to go back to the basics—paper credentials, how that model has worked for 1000s of years, and how the use of DLTs with verifiable credentials allows us to transition the great parts—security and privacy—of that model to the digital age. While people understand that paper credentials are insufficient and that a trusted digital solution is needed, they don’t understand why verifiable credentials, or more generally, identity, works extremely well with distributed ledger technology (DLT)—a distributed database spread across multiple nodes, of which blockchain is an example. keywords: credential; dlt; identity; paper; verifier cache: www-why-distributed-ledger-technology-dlt-for-identity.html plain text: www-why-distributed-ledger-technology-dlt-for-identity.txt item: #3313 of 3327 id: www-why-distributed-ledger-technology-dlt-for-identity?hs_amp=true author: www title: www-why-distributed-ledger-technology-dlt-for-identity?hs_amp=true date: None words: 1534 flesch: 59 summary: To understand why DLT is useful for identity, we need to go back to the basics—paper credentials, how that model has worked for 1000s of years, and how the use of DLTs with verifiable credentials allows us to transition the great parts—security and privacy—of that model to the digital age. While people understand that paper credentials are insufficient and that a trusted digital solution is needed, they don’t understand why verifiable credentials, or more generally, identity, works extremely well with distributed ledger technology (DLT)—a distributed database spread across multiple nodes, of which blockchain is an example. keywords: credential; paper; verifier cache: www-why-distributed-ledger-technology-dlt-for-identity?hs_amp=true.html plain text: www-why-distributed-ledger-technology-dlt-for-identity?hs_amp=true.txt item: #3314 of 3327 id: www-why-hyperledger-besu-is-a-top-choice-for-financial-use-cases author: www title: www-why-hyperledger-besu-is-a-top-choice-for-financial-use-cases date: None words: 1288 flesch: 34 summary: How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Besu | Finance and Business Technology Why Hyperledger Besu is a Top Choice for Financial Use Cases Matthew Whitehead, Hyperledger Besu Maintainer and Principal Engineer at Kaleido | Mar 19, 2024 Hyperledger Besu has emerged as a preferred runtime for EVM-based financial initiatives worldwide. Features contributing to Hyperledger Besu's interoperability include: Cross-chain functionality: Layer-2 solutions such as Linea are already being built using Besu, demonstrating its suitability for a wide range of multi-chain architectures now and in the future. keywords: besu; enterprise; hyperledger; license; use cache: www-why-hyperledger-besu-is-a-top-choice-for-financial-use-cases.html plain text: www-why-hyperledger-besu-is-a-top-choice-for-financial-use-cases.txt item: #3315 of 3327 id: www-why-hyperledger-besu-is-a-top-choice-for-financial-use-cases?hs_amp=true author: www title: www-why-hyperledger-besu-is-a-top-choice-for-financial-use-cases?hs_amp=true date: None words: 973 flesch: 38 summary: Why Hyperledger Besu is a Top Choice for Financial Use Cases Blog | LF Decentralized Trust Why Hyperledger Besu is a Top Choice for Financial Use Cases Written by Matthew Whitehead, Hyperledger Besu Maintainer and Principal Engineer at Kaleido | Mar 19, 2024 5:00:00 PM Hyperledger Besu has emerged as a preferred runtime for EVM-based financial initiatives worldwide. Features contributing to Hyperledger Besu's interoperability include: Cross-chain functionality: Layer-2 solutions such as Linea are already being built using Besu, demonstrating its suitability for a wide range of multi-chain architectures now and in the future. keywords: besu; enterprise; hyperledger cache: www-why-hyperledger-besu-is-a-top-choice-for-financial-use-cases?hs_amp=true.html plain text: www-why-hyperledger-besu-is-a-top-choice-for-financial-use-cases?hs_amp=true.txt item: #3316 of 3327 id: www-why-hyperledger-foundation-sponsors-attends-and-works-at-internet-identity-workshop author: www title: www-why-hyperledger-foundation-sponsors-attends-and-works-at-internet-identity-workshop date: None words: 1008 flesch: 39 summary: Contributors and maintainers working on Hyperledger identity projects like Hyperledger Indy, Aries, Ursa and now Anoncreds are there to gather, share, hear feedback and work. Hyperledger Foundation’s sponsorship of IIW takes different forms for every event, but we as a team feel supporting this community is critical to the identity ecosystem in general and Hyperledger identity projects. keywords: foundation; hyperledger; identity; iiw cache: www-why-hyperledger-foundation-sponsors-attends-and-works-at-internet-identity-workshop.html plain text: www-why-hyperledger-foundation-sponsors-attends-and-works-at-internet-identity-workshop.txt item: #3317 of 3327 id: www-why-hyperledger-foundation-sponsors-attends-and-works-at-internet-identity-workshop?hs_amp=true author: www title: www-why-hyperledger-foundation-sponsors-attends-and-works-at-internet-identity-workshop?hs_amp=true date: None words: 691 flesch: 49 summary: Contributors and maintainers working on Hyperledger identity projects like Hyperledger Indy, Aries, Ursa and now Anoncreds are there to gather, share, hear feedback and work. Hyperledger Foundation’s sponsorship of IIW takes different forms for every event, but we as a team feel supporting this community is critical to the identity ecosystem in general and Hyperledger identity projects. keywords: hyperledger; iiw cache: www-why-hyperledger-foundation-sponsors-attends-and-works-at-internet-identity-workshop?hs_amp=true.html plain text: www-why-hyperledger-foundation-sponsors-attends-and-works-at-internet-identity-workshop?hs_amp=true.txt item: #3318 of 3327 id: www-why-india-is-poised-to-be-a-leader-in-blockchain-technology-adoption author: www title: www-why-india-is-poised-to-be-a-leader-in-blockchain-technology-adoption date: None words: 931 flesch: 36 summary: ResearchAndMarkets.com recently reported that the digital adoption in India is one of the major factors driving Blockchain technology adoption. On balance, optimism is high with respect to blockchain technology adoption in India. keywords: adoption; blockchain; india; technology cache: www-why-india-is-poised-to-be-a-leader-in-blockchain-technology-adoption.html plain text: www-why-india-is-poised-to-be-a-leader-in-blockchain-technology-adoption.txt item: #3319 of 3327 id: www-why-is-interoperability-needed author: www title: www-why-is-interoperability-needed date: None words: 1966 flesch: 22 summary: 🏗️ 🏗️ 📝 🏗️ Ability to support complex queries ✅ ✅ 🏗️ ✅ Ability to support cross-network smart contracts (ledger–>ledger invocations) ✅ 🏗️ 🏗️ ✅ End-to-end confidentiality 🏗️ 🏗️ 📝 ✅ Privacy-preserving queries 🏗️ 🏗️ 🏗️ 🏗️ Support for network discovery and connection bootstrapping 🏗️ 🏗️ 🏗️ ✅ Support for routing data and assets via intermediate networks 📝 🏗️ 🏗️ ✅ Future Work for 2022 Q1  Hyperledger Cactus Support for the Open Digital Asset Protocol (ODAP) How to contribute Contribute to code Host your project with us Regional chapters Special interest groups Job board Resources Linux Foundation ID Logos & guidelines Trademarks & guidelines Charter Code of conduct Github repos Discord Wiki Mailing lists Report a security bug Learn Case studies Training & certifications Use case tracker Member webinars Insights News Blog Announcements Newsletters Events Events Meetups Meeting calendar Join Follow Us Hyperledger Cacti | Labs | Hyperledger FireFly | Interoperability Why is Interoperability Needed? Hyperledger Cactus, Hyperledger FireFly, keywords: blockchain; data; hyperledger; interoperability cache: www-why-is-interoperability-needed.html plain text: www-why-is-interoperability-needed.txt item: #3320 of 3327 id: www-why-is-interoperability-needed?hs_amp=true author: www title: www-why-is-interoperability-needed?hs_amp=true date: None words: 1650 flesch: 23 summary: 🏗️ 🏗️ 📝 🏗️ Ability to support complex queries ✅ ✅ 🏗️ ✅ Ability to support cross-network smart contracts (ledger–>ledger invocations) ✅ 🏗️ 🏗️ ✅ End-to-end confidentiality 🏗️ 🏗️ 📝 ✅ Privacy-preserving queries 🏗️ 🏗️ 🏗️ 🏗️ Support for network discovery and connection bootstrapping 🏗️ 🏗️ 🏗️ ✅ Support for routing data and assets via intermediate networks 📝 🏗️ 🏗️ ✅ Future Work for 2022 Q1  Hyperledger Cactus Support for the Open Digital Asset Protocol (ODAP) Hyperledger Foundation Written by Hyperledger Cactus, Hyperledger FireFly, Weaver and YUI technical communities | Feb 2, 2022 9:00:00 AM Blockchain interoperability is one of the crucial features of blockchain technology, operating in three main vectors: enabling scalability, diminishing risks and eliminating silos¹. This blog post focuses on interoperability projects connecting data and value silos. keywords: hyperledger; interoperability cache: www-why-is-interoperability-needed?hs_amp=true.html plain text: www-why-is-interoperability-needed?hs_amp=true.txt item: #3321 of 3327 id: www-why-ssi-incubator-an-inside-look-at-the-program-and-startups author: www title: www-why-ssi-incubator-an-inside-look-at-the-program-and-startups date: None words: 787 flesch: 34 summary: It was this excitement and optimism for the growing industry of identity products and solutions being born out of this community from which the Self-Sovereign Identity Incubator (SSI Incubator) was launched. From Hyperledger Indy, then Hyperledger Ursa, to the new project Hyperledger Aries, widespread adoption of decentralized identity is closer than ever. keywords: decentralized; hyperledger; identity; ssi cache: www-why-ssi-incubator-an-inside-look-at-the-program-and-startups.html plain text: www-why-ssi-incubator-an-inside-look-at-the-program-and-startups.txt item: #3322 of 3327 id: www-why-you-should-join-the-hyperledger-identity-special-interest-group author: www title: www-why-you-should-join-the-hyperledger-identity-special-interest-group date: None words: 918 flesch: 39 summary: This means that the group is dedicated to the advancement of decentralized digital identity projects — both including and beyond those hosted by the Hyperledger and Linux Foundation communities — that offer an alternative to the current digital identity systems in place, such as logging in with a username and password or a third-party provider such as Facebook.  Each hour-long meeting starts with a 20-minute recap of progress from the various different open-source code groups working on decentralized identity technology, such as the Hyperledger Aries Bifold project, DIDComm at the Decentralized Identity Foundation (DIF), and Trust Over IP (TOIP). keywords: decentralized; foundation; hyperledger; identity cache: www-why-you-should-join-the-hyperledger-identity-special-interest-group.html plain text: www-why-you-should-join-the-hyperledger-identity-special-interest-group.txt item: #3323 of 3327 id: www-why-you-should-join-the-hyperledger-identity-special-interest-group?hs_amp=true author: www title: www-why-you-should-join-the-hyperledger-identity-special-interest-group?hs_amp=true date: None words: 599 flesch: 48 summary: This means that the group is dedicated to the advancement of decentralized digital identity projects — both including and beyond those hosted by the Hyperledger and Linux Foundation communities — that offer an alternative to the current digital identity systems in place, such as logging in with a username and password or a third-party provider such as Facebook.  Why You Should Join the Hyperledger Identity Special Interest Group – Hyperledger Foundation Blog | LF Decentralized Trust Why You Should Join the Hyperledger Identity Special Interest Group – Hyperledger Foundation Written by Tim Spring - Co-Chair Hyperledger Identity SIG | Jul 26, 2023 11:21:35 AM It’s hard to overstate the importance of digital identity: It governs every interaction online, from email and social media to ecommerce and critical financial transactions. keywords: hyperledger; identity cache: www-why-you-should-join-the-hyperledger-identity-special-interest-group?hs_amp=true.html plain text: www-why-you-should-join-the-hyperledger-identity-special-interest-group?hs_amp=true.txt item: #3324 of 3327 id: www-working-together-on-what-good-looks-like author: www title: www-working-together-on-what-good-looks-like date: None words: 870 flesch: 34 summary: A set of Linux Foundation organizations – TrustOverIP, Hyperledger, Linux Foundation Public Health, and its Covid Credentials Initiative – have engaged as supporting organizations and were part of the announcement. Now, as part of Linux Foundation Public Health, we are working to bring together a set of software projects that can implement credential systems and help accelerate adoption of these globally, centered on the needs of public health authorities. keywords: decentralized; foundation; identity; linux cache: www-working-together-on-what-good-looks-like.html plain text: www-working-together-on-what-good-looks-like.txt item: #3325 of 3327 id: www-working-together-on-what-good-looks-like?hs_amp=true author: www title: www-working-together-on-what-good-looks-like?hs_amp=true date: None words: 550 flesch: 44 summary: A set of Linux Foundation organizations – TrustOverIP, Hyperledger, Linux Foundation Public Health, and its Covid Credentials Initiative – have engaged as supporting organizations and were part of the announcement. Now, as part of Linux Foundation Public Health, we are working to bring together a set of software projects that can implement credential systems and help accelerate adoption of these globally, centered on the needs of public health authorities. keywords: foundation; systems cache: www-working-together-on-what-good-looks-like?hs_amp=true.html plain text: www-working-together-on-what-good-looks-like?hs_amp=true.txt item: #3326 of 3327 id: www-yacov-manevich-yoav-tock-and-hagar-meir author: www title: www-yacov-manevich-yoav-tock-and-hagar-meir date: None words: 522 flesch: 19 summary: Use the filter below to browse by categories Browse by All Besu Blockchain Pioneers Blog CBDCs CREDEBL Case Study Climate Decentralized Identity Developer Showcase Digital Currency Digital Identity Digital Trust Distributed Ledger Technology Finance Finance and Business Technology Governance Governing Board Health and Public Sector Hiero Hyperledger AnonCreds Hyperledger Aries Hyperledger Avalon Hyperledger Bevel Hyperledger Burrow Hyperledger Cacti Hyperledger Caliper Hyperledger Community Hyperledger Composer Hyperledger Explorer Hyperledger Fabric Hyperledger FireFly Hyperledger Grid Hyperledger Identus Hyperledger Indy Hyperledger Iroha Hyperledger Quilt Hyperledger Sawtooth Hyperledger Solang Hyperledger Transact Hyperledger Ursa Interoperability Labs Lockness Meet the Maintainers Member Case Study Mentorship Program Project: Besu Project: Hyperledger Indy Regional Chapters Special Interest Group Staff Corner Supply Chain Telecom Trust Over IP Web3j Content Title Description < Previous page Delivering Smart Byzantine Fault Tolerant consensus Introducing Byzantine Fault Tolerant for Hyperledger Fabric Read More Yacov Manevich, Yoav Tock, and Hagar Meir | Sep 16, 2024 keywords: blog; decentralized; hyperledger; technologies cache: www-yacov-manevich-yoav-tock-and-hagar-meir.html plain text: www-yacov-manevich-yoav-tock-and-hagar-meir.txt item: #3327 of 3327 id: x-metadata author: None title: x-metadata date: None words: 7090 flesch: -7113 summary: author title file ethereummagicians ethereummagicians-12326 ethereummagicians-12326.html ethereummagicians ethereummagicians-17474 ethereummagicians-17474.html ethereummagicians ethereummagicians-14778 ethereummagicians-14778.html ethereummagicians ethereummagicians-12894 ethereummagicians-12894.html ethereummagicians ethereummagicians-17134 ethereummagicians-17134.html ethereummagicians ethereummagicians-17336 ethereummagicians-17336.html ethereummagicians ethereummagicians-15144 ethereummagicians-15144.html ethereummagicians ethereummagicians-17242 ethereummagicians-17242.html ethereummagicians ethereummagicians-13030 ethereummagicians-13030.html ethereummagicians ethereummagicians-11374 ethereummagicians-11374.html ethereummagicians ethereummagicians-9898 ethereummagicians-9898.html ethereummagicians ethereummagicians-13366 ethereummagicians-13366.html ethereummagicians ethereummagicians-5805 ethereummagicians-5805.html ethereummagicians ethereummagicians-15683 ethereummagicians-15683.html ethereummagicians ethereummagicians-13891 ethereummagicians-13891.html ethereummagicians ethereummagicians-16256 ethereummagicians-16256.html ethereummagicians ethereummagicians-7014 ethereummagicians-7014.html ethereummagicians ethereummagicians-17232 ethereummagicians-17232.html ethereummagicians ethereummagicians-16809 ethereummagicians-16809.html ethereummagicians ethereummagicians-16690 ethereummagicians-16690.html ethereummagicians ethereummagicians-14979 ethereummagicians-14979.html ethereummagicians ethereummagicians-15989 ethereummagicians-15989.html ethereummagicians ethereummagicians-17295 ethereummagicians-17295.html ethereummagicians ethereummagicians-15269 ethereummagicians-15269.html ethereummagicians ethereummagicians-15996 ethereummagicians-15996.html ethereummagicians ethereummagicians-17274 ethereummagicians-17274.html ethereummagicians ethereummagicians-15902 ethereummagicians-15902.html ethereummagicians ethereummagicians-8300 ethereummagicians-8300.html ethereummagicians ethereummagicians-17264 ethereummagicians-17264.html ethereummagicians ethereummagicians-14195 ethereummagicians-14195.html ethereummagicians ethereummagicians-2842 ethereummagicians-2842.html ethereummagicians ethereummagicians-16664 ethereummagicians-16664.html ethereummagicians ethereummagicians-10310 ethereummagicians-10310.html ethereummagicians ethereummagicians-17170 ethereummagicians-17170.html ethereummagicians ethereummagicians-15504 ethereummagicians-15504.html ethereummagicians ethereummagicians-17157 ethereummagicians-17157.html ethereummagicians ethereummagicians-11091 ethereummagicians-11091.html ethereummagicians ethereummagicians-7677 ethereummagicians-7677.html ethresear ethresear-8 ethresear-8.html ethresear ethresear-17888 ethresear-17888.html ethresear ethresear-17882 ethresear-17882.html ethresear ethresear-17847 ethresear-17847.html ethresear ethresear-17844 ethresear-17844.html ethresear ethresear-17796 ethresear-17796.html ethresear ethresear-16839 ethresear-16839.html ethresear ethresear-11953 ethresear-11953.html ethresear ethresear-27 ethresear-27.html ethresear ethresear-11953?page=2 ethresear-11953?page=2.html ethresear ethresear-17538 ethresear-17538.html ethresear ethresear-17538?page=2 ethresear-17538?page=2.html ethresear ethresear-16009 ethresear-16009.html ethresear ethresear-17384 ethresear-17384.html ethresear ethresear-16509 ethresear-16509.html ethresear ethresear-17852 ethresear-17852.html ethresear ethresear-17473 ethresear-17473.html ethresear ethresear-17833 ethresear-17833.html ethresear ethresear-17481 ethresear-17481.html ethresear ethresear-17445 ethresear-17445.html ethresear ethresear-17175 ethresear-17175.html ethresear ethresear-17612 ethresear-17612.html ethresear ethresear-17612?page=2 ethresear-17612?page=2.html ethresear ethresear-12670 ethresear-12670.html ethresear ethresear-12670?page=2 ethresear-12670?page=2.html ethresear ethresear-17804 ethresear-17804.html ethresear ethresear-16828 ethresear-16828.html ethresear ethresear-17312 ethresear-17312.html ethresear ethresear-15947 ethresear-15947.html ethresear ethresear-7736 ethresear-7736.html ethresear ethresear-13139 ethresear-13139.html ethresear ethresear-17689 ethresear-17689.html ethresear ethresear-16492 ethresear-16492.html ethresear ethresear-17748 ethresear-17748.html ethresear ethresear-17750 ethresear-17750.html ethresear ethresear-17620 ethresear-17620.html ethresear ethresear-17682 ethresear-17682.html ethresear ethresear-15402 ethresear-15402.html ethresear ethresear-17279 ethresear-17279.html ethresear ethresear-17359 ethresear-17359.html ethresear ethresear-15404 ethresear-15404.html ethresear ethresear-17651 ethresear-17651.html ethresear ethresear-17540 ethresear-17540.html ethresear ethresear-17553 ethresear-17553.html ethresear ethresear-16072 ethresear-16072.html ethresear ethresear-17624 ethresear-17624.html ethresear ethresear-15320 ethresear-15320.html ethresear ethresear-17616 ethresear-17616.html ethresear ethresear-17119 ethresear-17119.html ethresear ethresear-17125 ethresear-17125.html ethresear ethresear-17350 ethresear-17350.html ethresear ethresear-17572 ethresear-17572.html ethresear ethresear-17104 ethresear-17104.html ethresear ethresear-17263 ethresear-17263.html ethresear ethresear-17565 ethresear-17565.html ethresear ethresear-17488 ethresear-17488.html ethresear ethresear-17487 ethresear-17487.html ethresear ethresear-17387 ethresear-17387.html ethresear ethresear-17417 ethresear-17417.html ethresear ethresear-15154 ethresear-15154.html ethresear ethresear-17523 ethresear-17523.html ethresear ethresear-16830 ethresear-16830.html ethresear ethresear-17353 ethresear-17353.html ethresear ethresear-16520 ethresear-16520.html ethresear ethresear-17495 ethresear-17495.html ethresear ethresear-4963 ethresear-4963.html ethresear ethresear-17249 ethresear-17249.html ethresear ethresear-16711 ethresear-16711.html ethresear ethresear-15126 ethresear-15126.html ethresear ethresear-11527 ethresear-11527.html ethresear ethresear-10756 ethresear-10756.html ethresear ethresear-11074 ethresear-11074.html ethresear ethresear-7369 ethresear-7369.html ethresear ethresear-17 ethresear-17.html ethresear ethresear-1 ethresear-1.html ethresear ethresear-11 ethresear-11.html ethresear ethresear-7684 ethresear-7684.html ethresear ethresear-3195 ethresear-3195.html ethresear ethresear-6428 ethresear-6428.html ethresear ethresear-4291 ethresear-4291.html ethresear ethresear-3155 ethresear-3155.html ethresear ethresear-2 ethresear-2.html ethresear ethresear-731 ethresear-731.html ethresear ethresear-118 ethresear-118.html ethresear ethresear-130 ethresear-130.html ethresear ethresear-5379 ethresear-5379.html ethresear ethresear-17470 ethresear-17470.html ethresear ethresear-16429 ethresear-16429.html ethresear ethresear-16591 ethresear-16591.html ethresear ethresear-15454 ethresear-15454.html ethresear ethresear-15703 ethresear-15703.html ethresear ethresear-15871 ethresear-15871.html ethresear ethresear-16081 ethresear-16081.html ethresear ethresear-15649 ethresear-15649.html ethresear ethresear-14219 ethresear-14219.html ethresear ethresear-11763 ethresear-11763.html ethresear ethresear-15012 ethresear-15012.html ethresear ethresear-14920 ethresear-14920.html ethresear ethresear-12315 ethresear-12315.html ethresear ethresear-12700 ethresear-12700.html ethresear ethresear-14164 ethresear-14164.html ethresear ethresear-14349 ethresear-14349.html ethresear ethresear-14350 ethresear-14350.html ethresear ethresear-13642 ethresear-13642.html ethresear ethresear-13803 ethresear-13803.html ethresear ethresear-13739 ethresear-13739.html ethresear ethresear-6972 ethresear-6972.html ethresear ethresear-11853 ethresear-11853.html ethresear ethresear-11854 ethresear-11854.html ethresear ethresear-12658 ethresear-12658.html ethresear ethresear-11883 ethresear-11883.html ethresear ethresear-11833 ethresear-11833.html ethresear ethresear-11127 ethresear-11127.html ethresear ethresear-17389 ethresear-17389.html ethresear ethresear-7 ethresear-7.html ethresear ethresear-17258 ethresear-17258.html ethresear ethresear-17288 ethresear-17288.html ethresear ethresear-15590 ethresear-15590.html ethresear ethresear-17017 ethresear-17017.html ethresear ethresear-17092 ethresear-17092.html ethresear ethresear-16278 ethresear-16278.html ethresear ethresear-15959 ethresear-15959.html ethresear ethresear-16788 ethresear-16788.html ethresear ethresear-16666 ethresear-16666.html ethresear ethresear-16692 ethresear-16692.html ethresear ethresear-16762 ethresear-16762.html ethresear ethresear-16327 ethresear-16327.html ethresear ethresear-16054 ethresear-16054.html ethresear ethresear-16550 ethresear-16550.html ethresear ethresear-15900 ethresear-15900.html ethresear ethresear-15500 ethresear-15500.html ethresear ethresear-14957 ethresear-14957.html ethresear ethresear-16267 ethresear-16267.html ethresear ethresear-16121 ethresear-16121.html ethresear ethresear-16206 ethresear-16206.html ethresear ethresear-15313 ethresear-15313.html ethresear ethresear-15636 ethresear-15636.html ethresear ethresear-15668 ethresear-15668.html ethresear ethresear-5380 ethresear-5380.html ethresear ethresear-5885 ethresear-5885.html ethresear ethresear-14748 ethresear-14748.html ethresear ethresear-14607 ethresear-14607.html ethresear ethresear-13526 ethresear-13526.html ethresear ethresear-3751 ethresear-3751.html ethresear ethresear-11054 ethresear-11054.html ethresear ethresear-5511 ethresear-5511.html ethresear ethresear-7027 ethresear-7027.html ethresear ethresear-8082 ethresear-8082.html ethresear ethresear-7887 ethresear-7887.html ethresear ethresear-210 ethresear-210.html ethresear ethresear-6802 ethresear-6802.html ethresear ethresear-6737 ethresear-6737.html ethresear ethresear-6487 ethresear-6487.html ethresear ethresear-6064 ethresear-6064.html ethresear ethresear-5543 ethresear-5543.html ethresear ethresear-4912 ethresear-4912.html ethresear ethresear-17136 ethresear-17136.html ethresear ethresear-16480 ethresear-16480.html ethresear ethresear-16493 ethresear-16493.html ethresear ethresear-16483 ethresear-16483.html ethresear ethresear-16299 ethresear-16299.html ethresear ethresear-16194 ethresear-16194.html ethresear ethresear-16162 ethresear-16162.html ethresear ethresear-14671 ethresear-14671.html ethresear ethresear-7304 ethresear-7304.html ethresear ethresear-12355 ethresear-12355.html ethresear ethresear-9115 ethresear-9115.html ethresear ethresear-8161 ethresear-8161.html ethresear ethresear-9095 ethresear-9095.html ethresear ethresear-8575 ethresear-8575.html ethresear ethresear-8472 ethresear-8472.html ethresear ethresear-172 ethresear-172.html ethresear ethresear-8357 ethresear-8357.html ethresear ethresear-8185 ethresear-8185.html ethresear ethresear-8143 ethresear-8143.html ethresear ethresear-7321 ethresear-7321.html ethresear ethresear-7573 ethresear-7573.html ethresear ethresear-7602 ethresear-7602.html ethresear ethresear-7363 ethresear-7363.html ethresear ethresear-7260 ethresear-7260.html ethresear ethresear-7287 ethresear-7287.html ethresear ethresear-7088 ethresear-7088.html ethresear ethresear-7173 ethresear-7173.html ethresear ethresear-147 ethresear-147.html ethresear ethresear-1080 ethresear-1080.html ethresear ethresear-17032 ethresear-17032.html ethresear ethresear-16523 ethresear-16523.html ethresear ethresear-16027 ethresear-16027.html ethresear ethresear-15724 ethresear-15724.html ethresear ethresear-14962 ethresear-14962.html ethresear ethresear-13980 ethresear-13980.html ethresear ethresear-13487 ethresear-13487.html ethresear ethresear-13181 ethresear-13181.html ethresear ethresear-13247 ethresear-13247.html ethresear ethresear-12345 ethresear-12345.html ethresear ethresear-7198 ethresear-7198.html ethresear ethresear-12415 ethresear-12415.html ethresear ethresear-218 ethresear-218.html ethresear ethresear-10323 ethresear-10323.html ethresear ethresear-2338 ethresear-2338.html ethresear ethresear-8588 ethresear-8588.html ethresear ethresear-8230 ethresear-8230.html ethresear ethresear-7761 ethresear-7761.html ethresear ethresear-7332 ethresear-7332.html ethresear ethresear-7043 ethresear-7043.html ethresear ethresear-6467 ethresear-6467.html ethresear ethresear-6153 ethresear-6153.html ethresear ethresear-5987 ethresear-5987.html ethresear ethresear-5434 ethresear-5434.html ethresear ethresear-4521 ethresear-4521.html ethresear ethresear-4566 ethresear-4566.html ethresear ethresear-5378 ethresear-5378.html ethresear ethresear-17386 ethresear-17386.html ethresear ethresear-16213 ethresear-16213.html ethresear ethresear-7438 ethresear-7438.html ethresear ethresear-17137 ethresear-17137.html ethresear ethresear-16454 ethresear-16454.html ethresear ethresear-16678 ethresear-16678.html ethresear ethresear-16670 ethresear-16670.html ethresear ethresear-1235 ethresear-1235.html ethresear ethresear-12808 ethresear-12808.html ethresear ethresear-4279 ethresear-4279.html ethresear ethresear-16150 ethresear-16150.html ethresear ethresear-15980 ethresear-15980.html ethresear ethresear-15214 ethresear-15214.html ethresear ethresear-15437 ethresear-15437.html ethresear ethresear-15143 ethresear-15143.html ethresear ethresear-13563 ethresear-13563.html ethresear ethresear-14694 ethresear-14694.html ethresear ethresear-14689 ethresear-14689.html ethresear ethresear-2665 ethresear-2665.html ethresear ethresear-13008 ethresear-13008.html ethresear ethresear-7380 ethresear-7380.html ethresear ethresear-14444 ethresear-14444.html ethresear ethresear-13974 ethresear-13974.html ethresear ethresear-5382 ethresear-5382.html ethresear ethresear-17366 ethresear-17366.html ethresear ethresear-17429 ethresear-17429.html ethresear ethresear-16570 ethresear-16570.html ethresear ethresear-17204 ethresear-17204.html ethresear ethresear-16760 ethresear-16760.html ethresear ethresear-16234 ethresear-16234.html ethresear ethresear-16889 ethresear-16889.html ethresear ethresear-16677 ethresear-16677.html ethresear ethresear-16665 ethresear-16665.html ethresear ethresear-15940 ethresear-15940.html ethresear ethresear-16512 ethresear-16512.html ethresear ethresear-16441 ethresear-16441.html ethresear ethresear-16370 ethresear-16370.html ethresear ethresear-16334 ethresear-16334.html ethresear ethresear-15169 ethresear-15169.html ethresear ethresear-16156 ethresear-16156.html ethresear ethresear-1279 ethresear-1279.html ethresear ethresear-12778 ethresear-12778.html ethresear ethresear-16319 ethresear-16319.html ethresear ethresear-15486 ethresear-15486.html ethresear ethresear-15489 ethresear-15489.html ethresear ethresear-15010 ethresear-15010.html ethresear ethresear-14891 ethresear-14891.html ethresear ethresear-14724 ethresear-14724.html ethresear ethresear-7913 ethresear-7913.html ethresear ethresear-11020 ethresear-11020.html ethresear ethresear-10446 ethresear-10446.html ethresear ethresear-1281 ethresear-1281.html ethresear ethresear-8594 ethresear-8594.html ethresear ethresear-8303 ethresear-8303.html ethresear ethresear-7676 ethresear-7676.html ethresear ethresear-7851 ethresear-7851.html ethresear ethresear-7208 ethresear-7208.html ethresear ethresear-6248 ethresear-6248.html ethresear ethresear-2554 ethresear-2554.html ethresear ethresear-5887 ethresear-5887.html ethresear ethresear-2443 ethresear-2443.html ethresear ethresear-5831 ethresear-5831.html ethresear ethresear-5555 ethresear-5555.html ethresear ethresear-5051 ethresear-5051.html ethresear ethresear-13775 ethresear-13775.html ethresear ethresear-6841 ethresear-6841.html ethresear ethresear-3198 ethresear-3198.html ethresear ethresear-6019 ethresear-6019.html ethresear ethresear-16687 ethresear-16687.html ethresear ethresear-16297 ethresear-16297.html ethresear ethresear-16184 ethresear-16184.html ethresear ethresear-15774 ethresear-15774.html ethresear ethresear-15748 ethresear-15748.html ethresear ethresear-15715 ethresear-15715.html ethresear ethresear-15424 ethresear-15424.html ethresear ethresear-15248 ethresear-15248.html ethresear ethresear-14714 ethresear-14714.html ethresear ethresear-14565 ethresear-14565.html ethresear ethresear-13742 ethresear-13742.html ethresear ethresear-14134 ethresear-14134.html ethresear ethresear-12698 ethresear-12698.html ethresear ethresear-13450 ethresear-13450.html ethresear ethresear-7754 ethresear-7754.html ethresear ethresear-12851 ethresear-12851.html ethresear ethresear-6232 ethresear-6232.html ethresear ethresear-11031 ethresear-11031.html ethresear ethresear-12426 ethresear-12426.html ethresear ethresear-12158 ethresear-12158.html ethresear ethresear-11379 ethresear-11379.html ethresear ethresear-10774 ethresear-10774.html ethresear ethresear-9039 ethresear-9039.html ethresear ethresear-9465 ethresear-9465.html ethresear ethresear-7336 ethresear-7336.html ethresear ethresear-17302 ethresear-17302.html ethresear ethresear-15078 ethresear-15078.html ethresear ethresear-14012 ethresear-14012.html ethresear ethresear-12156 ethresear-12156.html ethresear ethresear-11588 ethresear-11588.html ethresear ethresear-11033 ethresear-11033.html ethresear ethresear-7216 ethresear-7216.html ethresear ethresear-4481 ethresear-4481.html ethresear ethresear-12 ethresear-12.html ethresear ethresear-16700 ethresear-16700.html ethresear ethresear-15801 ethresear-15801.html ethresear ethresear-17407 ethresear-17407.html ethresear ethresear-17356 ethresear-17356.html ethresear ethresear-17371 ethresear-17371.html ethresear ethresear-16389 ethresear-16389.html ethresear ethresear-17115 ethresear-17115.html ethresear ethresear-15710 ethresear-15710.html ethresear ethresear-17055 ethresear-17055.html ethresear ethresear-15551 ethresear-15551.html ethresear ethresear-16333 ethresear-16333.html ethresear ethresear-13879 ethresear-13879.html ethresear ethresear-14906 ethresear-14906.html ethresear ethresear-14029 ethresear-14029.html ethresear ethresear-11877 ethresear-11877.html ethresear ethresear-13485 ethresear-13485.html ethresear ethresear-10980 ethresear-10980.html ethresear ethresear-299 ethresear-299.html ethresear ethresear-16115 ethresear-16115.html ethresear ethresear-15 ethresear-15.html ethresear ethresear-15559 ethresear-15559.html ethresear ethresear-17176 ethresear-17176.html ethresear ethresear-16337 ethresear-16337.html ethresear ethresear-17114 ethresear-17114.html ethresear ethresear-14462 ethresear-14462.html ethresear ethresear-6984 ethresear-6984.html ethresear ethresear-15131 ethresear-15131.html ethresear ethresear-8074 ethresear-8074.html ethresear ethresear-16448 ethresear-16448.html ethresear ethresear-16403 ethresear-16403.html ethresear ethresear-16384 ethresear-16384.html ethresear ethresear-16375 ethresear-16375.html ethresear ethresear-3675 ethresear-3675.html ethresear ethresear-14901 ethresear-14901.html ethresear ethresear-15881 ethresear-15881.html ethresear ethresear-15842 ethresear-15842.html ethresear ethresear-14930 ethresear-14930.html ethresear ethresear-15744 ethresear-15744.html ethresear ethresear-15487 ethresear-15487.html ethresear ethresear-13237 ethresear-13237.html ethresear ethresear-15100 ethresear-15100.html ethresear ethresear-15231 ethresear-15231.html ethresear ethresear-15246 ethresear-15246.html ethresear ethresear-13634 ethresear-13634.html ethresear ethresear-13 ethresear-13.html ethresear ethresear-17169 ethresear-17169.html ethresear ethresear-17346 ethresear-17346.html ethresear ethresear-17089 ethresear-17089.html ethresear ethresear-6214 ethresear-6214.html ethresear ethresear-16256 ethresear-16256.html ethresear ethresear-16169 ethresear-16169.html ethresear ethresear-15898 ethresear-15898.html ethresear ethresear-5169 ethresear-5169.html ethresear ethresear-8081 ethresear-8081.html ethresear ethresear-14494 ethresear-14494.html ethresear ethresear-6287 ethresear-6287.html ethresear ethresear-13863 ethresear-13863.html ethresear ethresear-7265 ethresear-7265.html ethresear ethresear-12530 ethresear-12530.html ethresear ethresear-14141 ethresear-14141.html ethresear ethresear-265 ethresear-265.html ethresear ethresear-209 ethresear-209.html ethresear ethresear-3039 ethresear-3039.html ethresear ethresear-13680 ethresear-13680.html ethresear ethresear-5159 ethresear-5159.html ethresear ethresear-4009 ethresear-4009.html ethresear ethresear-13230 ethresear-13230.html ethresear ethresear-1737 ethresear-1737.html ethresear ethresear-12839 ethresear-12839.html ethresear ethresear-12476 ethresear-12476.html ethresear ethresear-1300 ethresear-1300.html ethresear ethresear-17315 ethresear-17315.html ethresear ethresear-17225 ethresear-17225.html ethresear ethresear-5413 ethresear-5413.html ethresear ethresear-17044 ethresear-17044.html ethresear ethresear-16774 ethresear-16774.html ethresear ethresear-15856 ethresear-15856.html ethresear ethresear-16199 ethresear-16199.html ethresear ethresear-16182 ethresear-16182.html ethresear ethresear-13560 ethresear-13560.html ethresear ethresear-16059 ethresear-16059.html ethresear ethresear-15903 ethresear-15903.html ethresear ethresear-15923 ethresear-15923.html ethresear ethresear-15894 ethresear-15894.html ethresear ethresear-3278 ethresear-3278.html ethresear ethresear-15390 ethresear-15390.html ethresear ethresear-15180 ethresear-15180.html ethresear ethresear-14762 ethresear-14762.html ethresear ethresear-14750 ethresear-14750.html ethresear ethresear-14708 ethresear-14708.html ethresear ethresear-14553 ethresear-14553.html ethresear ethresear-12153 ethresear-12153.html ethresear ethresear-13336 ethresear-13336.html ethresear ethresear-3947 ethresear-3947.html ethresear ethresear-13268 ethresear-13268.html ethresear ethresear-3101 ethresear-3101.html ethresear ethresear-16456 ethresear-16456.html ethresear ethresear-15560 ethresear-15560.html ethresear ethresear-15463 ethresear-15463.html ethresear ethresear-12930 ethresear-12930.html ethresear ethresear-13585 ethresear-13585.html ethresear ethresear-13490 ethresear-13490.html ethresear ethresear-13006 ethresear-13006.html ethresear ethresear-120 ethresear-120.html ethresear ethresear-10292 ethresear-10292.html ethresear ethresear-10274 ethresear-10274.html ethresear ethresear-10087 ethresear-10087.html ethresear ethresear-9855 ethresear-9855.html ethresear ethresear-9299 ethresear-9299.html ethresear ethresear-9109 ethresear-9109.html ethresear ethresear-8036 ethresear-8036.html ethresear ethresear-8023 ethresear-8023.html ethresear ethresear-6567 ethresear-6567.html ethresear ethresear-5153 ethresear-5153.html ethresear ethresear-6937 ethresear-6937.html ethresear ethresear-6703 ethresear-6703.html ethresear ethresear-5851 ethresear-5851.html ethresear ethresear-6362 ethresear-6362.html ethresear ethresear-5862 ethresear-5862.html ethresear ethresear-6219 ethresear-6219.html ethresear ethresear-6208 ethresear-6208.html ethresear ethresear-5820 ethresear-5820.html ethresear ethresear-6007 ethresear-6007.html ethresear ethresear-3497 ethresear-3497.html ethresear ethresear-2066 ethresear-2066.html ethresear ethresear-15694 ethresear-15694.html ethresear ethresear-15363 ethresear-15363.html ethresear ethresear-14752 ethresear-14752.html ethresear ethresear-13843 ethresear-13843.html ethresear ethresear-14106 ethresear-14106.html ethresear ethresear-13926 ethresear-13926.html ethresear ethresear-5185 ethresear-5185.html ethresear ethresear-11962 ethresear-11962.html ethresear ethresear-10161 ethresear-10161.html ethresear ethresear-6386 ethresear-6386.html ethresear ethresear-9249 ethresear-9249.html ethresear ethresear-8868 ethresear-8868.html ethresear ethresear-8512 ethresear-8512.html ethresear ethresear-7662 ethresear-7662.html ethresear ethresear-8020 ethresear-8020.html ethresear ethresear-7991 ethresear-7991.html ethresear ethresear-7340 ethresear-7340.html ethresear ethresear-7242 ethresear-7242.html ethresear ethresear-6594 ethresear-6594.html ethresear ethresear-2512 ethresear-2512.html ethresear ethresear-6191 ethresear-6191.html ethresear ethresear-2791 ethresear-2791.html ethresear ethresear-1283 ethresear-1283.html ethresear ethresear-2270 ethresear-2270.html ethresear ethresear-1712 ethresear-1712.html ethresear ethresear-16411 ethresear-16411.html ethresear ethresear-14782 ethresear-14782.html ethresear ethresear-4224 ethresear-4224.html ethresear ethresear-12120 ethresear-12120.html ethresear ethresear-5455 ethresear-5455.html ethresear ethresear-12742 ethresear-12742.html ethresear ethresear-12348 ethresear-12348.html ethresear ethresear-5373 ethresear-5373.html ethresear ethresear-7585 ethresear-7585.html ethresear ethresear-7597 ethresear-7597.html ethresear ethresear-5338 ethresear-5338.html ethresear ethresear-4929 ethresear-4929.html ethresear ethresear-4981 ethresear-4981.html ethresear ethresear-4906 ethresear-4906.html ethresear ethresear-2305 ethresear-2305.html ethresear ethresear-2755 ethresear-2755.html ethresear ethresear-16034 ethresear-16034.html ethresear ethresear-13051 ethresear-13051.html ethresear ethresear-15872 ethresear-15872.html ethresear ethresear-15504 ethresear-15504.html ethresear ethresear-15377 ethresear-15377.html ethresear ethresear-11549 ethresear-11549.html ethresear ethresear-15059 ethresear-15059.html ethresear ethresear-14813 ethresear-14813.html ethresear ethresear-14586 ethresear-14586.html ethresear ethresear-14427 ethresear-14427.html ethresear ethresear-14373 ethresear-14373.html ethresear ethresear-14206 ethresear-14206.html ethresear ethresear-13100 ethresear-13100.html ethresear ethresear-14150 ethresear-14150.html ethresear ethresear-13903 ethresear-13903.html ethresear ethresear-9600 ethresear-9600.html ethresear ethresear-13904 ethresear-13904.html ethresear ethresear-17450 ethresear-17450.html ethresear ethresear-17406 ethresear-17406.html ethresear ethresear-28 ethresear-28.html ethresear ethresear-17452 ethresear-17452.html ethresear ethresear-16608 ethresear-16608.html ethresear ethresear-17382 ethresear-17382.html ethresear ethresear-16541 ethresear-16541.html ethresear ethresear-16557 ethresear-16557.html ethresear ethresear-16387 ethresear-16387.html ethresear ethresear-17318 ethresear-17318.html ethresear ethresear-17316 ethresear-17316.html ethresear ethresear-17214 ethresear-17214.html ethresear ethresear-16514 ethresear-16514.html ethresear ethresear-8280 ethresear-8280.html ethresear ethresear-16186 ethresear-16186.html ethresear ethresear-15769 ethresear-15769.html ethresear ethresear-15820 ethresear-15820.html ethresear ethresear-15934 ethresear-15934.html ethresear ethresear-15544 ethresear-15544.html ethresear ethresear-15756 ethresear-15756.html ethresear ethresear-15667 ethresear-15667.html ethresear ethresear-15529 ethresear-15529.html ethresear ethresear-15626 ethresear-15626.html ethresear ethresear-15553 ethresear-15553.html ethresear ethresear-3197 ethresear-3197.html ethresear ethresear-10035 ethresear-10035.html ethresear ethresear-15634 ethresear-15634.html ethresear ethresear-15317 ethresear-15317.html ethresear ethresear-15328 ethresear-15328.html ethresear ethresear-14623 ethresear-14623.html ethresear ethresear-14520 ethresear-14520.html ethresear ethresear-13961 ethresear-13961.html ethresear ethresear-13594 ethresear-13594.html ethresear ethresear-13203 ethresear-13203.html ethresear ethresear-12709 ethresear-12709.html ethresear ethresear-9224 ethresear-9224.html ethresear ethresear-5062 ethresear-5062.html ethresear ethresear-11416 ethresear-11416.html ethresear ethresear-9456 ethresear-9456.html ethresear ethresear-8037 ethresear-8037.html ethresear ethresear-7902 ethresear-7902.html ethresear ethresear-6922 ethresear-6922.html ethresear ethresear-7187 ethresear-7187.html ethresear ethresear-6262 ethresear-6262.html ethresear ethresear-5451 ethresear-5451.html ethresear ethresear-5348 ethresear-5348.html ethresear ethresear-5318 ethresear-5318.html ethresear ethresear-4797 ethresear-4797.html ethresear ethresear-4423 ethresear-4423.html ethresear ethresear-4325 ethresear-4325.html ethresear ethresear-52 ethresear-52.html ethresear ethresear-increase-the-max-effective-balance-a-modest-proposal ethresear-increase-the-max-effective-balance-a-modest-proposal.html ethresear ethresear-376 ethresear-376.html ethresear ethresear-15396 ethresear-15396.html ethresear ethresear-10352 ethresear-10352.html ethresear ethresear-6429 ethresear-6429.html ethresear ethresear-16533 ethresear-16533.html ethresear ethresear-16078 ethresear-16078.html ethresear ethresear-15585 ethresear-15585.html ethresear ethresear-14758 ethresear-14758.html ethresear ethresear-12249 ethresear-12249.html ethresear ethresear-14212 ethresear-14212.html ethresear ethresear-14010 ethresear-14010.html ethresear ethresear-9781 ethresear-9781.html ethresear ethresear-12641 ethresear-12641.html ethresear ethresear-12395 ethresear-12395.html ethresear ethresear-12220 ethresear-12220.html ethresear ethresear-12194 ethresear-12194.html ethresear ethresear-12021 ethresear-12021.html ethresear ethresear-11356 ethresear-11356.html ethresear ethresear-10367 ethresear-10367.html ethresear ethresear-10310 ethresear-10310.html ethresear ethresear-10133 ethresear-10133.html ethresear ethresear-8739 ethresear-8739.html ethresear ethresear-9046 ethresear-9046.html ethresear ethresear-13240 ethresear-13240.html ethresear ethresear-5269 ethresear-5269.html ethresear ethresear-176 ethresear-176.html ethresear ethresear-6973 ethresear-6973.html ethresear ethresear-6649 ethresear-6649.html ethresear ethresear-5899 ethresear-5899.html ethresear ethresear-5503 ethresear-5503.html ethresear ethresear-5519 ethresear-5519.html ethresear ethresear-4602 ethresear-4602.html ethresear ethresear-1599 ethresear-1599.html ethresear ethresear-11340 ethresear-11340.html ethresear ethresear-10813 ethresear-10813.html ethresear ethresear-5337 ethresear-5337.html ethresear ethresear-8370 ethresear-8370.html ethresear ethresear-6268 ethresear-6268.html ethresear ethresear-7936 ethresear-7936.html ethresear ethresear-7639 ethresear-7639.html ethresear ethresear-7114 ethresear-7114.html ethresear ethresear-7474 ethresear-7474.html ethresear ethresear-7108 ethresear-7108.html ethresear ethresear-7365 ethresear-7365.html ethresear ethresear-7195 ethresear-7195.html ethresear ethresear-7277 ethresear-7277.html ethresear ethresear-7246 ethresear-7246.html ethresear ethresear-6996 ethresear-6996.html ethresear ethresear-6382 ethresear-6382.html ethresear ethresear-6509 ethresear-6509.html ethresear ethresear-1450 ethresear-1450.html ethresear ethresear-6478 ethresear-6478.html ethresear ethresear-5730 ethresear-5730.html ethresear ethresear-5859 ethresear-5859.html ethresear ethresear-5721 ethresear-5721.html ethresear ethresear-4970 ethresear-4970.html ethresear ethresear-5093 ethresear-5093.html ethresear ethresear-10305 ethresear-10305.html ethresear ethresear-10772 ethresear-10772.html ethresear ethresear-1312 ethresear-1312.html ethresear ethresear-6945 ethresear-6945.html ethresear ethresear-10435 ethresear-10435.html ethresear ethresear-10385 ethresear-10385.html ethresear ethresear-12939 ethresear-12939.html ethresear ethresear-12494 ethresear-12494.html ethresear ethresear-1014 ethresear-1014.html ethresear ethresear-4997 ethresear-4997.html ethresear ethresear-15547 ethresear-15547.html ethresear ethresear-15547? ethresear-15547?.html ethresear ethresear-15232 ethresear-15232.html ethresear ethresear-13357 ethresear-13357.html ethresear ethresear-7916 ethresear-7916.html ethresear ethresear-7547 ethresear-7547.html ethresear ethresear-7561 ethresear-7561.html ethresear ethresear-7448 ethresear-7448.html ethresear ethresear-7207 ethresear-7207.html ethresear ethresear-5879 ethresear-5879.html ethresear ethresear-4808 ethresear-4808.html ethresear ethresear-5031 ethresear-5031.html ethresear ethresear-3524 ethresear-3524.html ethresear ethresear-15016 ethresear-15016.html ethresear ethresear-7599 ethresear-7599.html ethresear ethresear-6325 ethresear-6325.html ethresear ethresear-6646 ethresear-6646.html ethresear ethresear-6738 ethresear-6738.html ethresear ethresear-1366 ethresear-1366.html ethresear ethresear-4074 ethresear-4074.html ethresear ethresear-2699 ethresear-2699.html ethresear ethresear-1340 ethresear-1340.html ethresear ethresear-10259 ethresear-10259.html ethresear ethresear-10303 ethresear-10303.html ethresear ethresear-9637 ethresear-9637.html ethresear ethresear-8623 ethresear-8623.html ethresear ethresear-8030 ethresear-8030.html ethresear ethresear-8028 ethresear-8028.html ethresear ethresear-7959 ethresear-7959.html ethresear ethresear-7874 ethresear-7874.html ethresear ethresear-4228 ethresear-4228.html ethresear ethresear-7654 ethresear-7654.html ethresear ethresear-7610 ethresear-7610.html ethresear ethresear-7307 ethresear-7307.html ethresear ethresear-7220 ethresear-7220.html ethresear ethresear-7142 ethresear-7142.html ethresear ethresear-6997 ethresear-6997.html ethresear ethresear-6957 ethresear-6957.html ethresear ethresear-6960 ethresear-6960.html ethresear ethresear-6936 ethresear-6936.html ethresear ethresear-6895 ethresear-6895.html ethresear ethresear-6821 ethresear-6821.html ethresear ethresear-2120 ethresear-2120.html ethresear ethresear-5719 ethresear-5719.html ethresear ethresear-6257 ethresear-6257.html ethresear ethresear-6111 ethresear-6111.html ethresear ethresear-5952 ethresear-5952.html ethresear ethresear-5926 ethresear-5926.html ethresear ethresear-5677 ethresear-5677.html ethresear ethresear-5570 ethresear-5570.html ethresear ethresear-5085 ethresear-5085.html ethresear ethresear-1792 ethresear-1792.html ethresear ethresear-6113 ethresear-6113.html ethresear ethresear-8909 ethresear-8909.html ethresear ethresear-2630 ethresear-2630.html ethresear ethresear-1825 ethresear-1825.html ethresear ethresear-10394 ethresear-10394.html ethresear ethresear-5402 ethresear-5402.html ethresear ethresear-5556 ethresear-5556.html swarmresear swarmresear-7 swarmresear-7.html swarmresear swarmresear-165 swarmresear-165.html swarmresear swarmresear-166 swarmresear-166.html swarmresear swarmresear-142 swarmresear-142.html swarmresear swarmresear-33 swarmresear-33.html swarmresear swarmresear-95 swarmresear-95.html swarmresear swarmresear-83 swarmresear-83.html swarmresear swarmresear-37 swarmresear-37.html swarmresear swarmresear-34 swarmresear-34.html swarmresear swarmresear-16 swarmresear-16.html swarmresear swarmresear-48 swarmresear-48.html swarmresear swarmresear-66 swarmresear-66.html swarmresear swarmresear-30 swarmresear-30.html swarmresear swarmresear-46 swarmresear-46.html swarmresear swarmresear-44 swarmresear-44.html swarmresear swarmresear-42 swarmresear-42.html swarmresear swarmresear-40 swarmresear-40.html swarmresear swarmresear-41 swarmresear-41.html swarmresear swarmresear-18 swarmresear-18.html swarmresear swarmresear-17 swarmresear-17.html swarmresear swarmresear-3 swarmresear-3.html swarmresear swarmresear-2 swarmresear-2.html swarmresear swarmresear-14 swarmresear-14.html swarmresear swarmresear-15 swarmresear-15.html swarmresear swarmresear-78 swarmresear-78.html swarmresear swarmresear-70 swarmresear-70.html swarmresear swarmresear-76 swarmresear-76.html swarmresear swarmresear-77 swarmresear-77.html swarmresear swarmresear-79 swarmresear-79.html swarmresear swarmresear-80 swarmresear-80.html swarmresear swarmresear-81 swarmresear-81.html vitalik vitalik-cypherpunk vitalik-cypherpunk.html vitalik vitalik-enshrinement vitalik-enshrinement.html vitalik vitalik-zkmulticlient vitalik-zkmulticlient.html vitalik vitalik-three_transitions vitalik-three_transitions.html vitalik vitalik-deeperdive vitalik-deeperdive.html vitalik vitalik-techno_optimism vitalik-techno_optimism.html vitalik vitalik-neoplasma vitalik-neoplasma.html vitalik vitalik-l2types vitalik-l2types.html vitalik vitalik-communitynotes vitalik-communitynotes.html vitalik vitalik-biometric vitalik-biometric.html vitalik vitalik-dont_overload vitalik-dont_overload.html vitalik vitalik-traveltime vitalik-traveltime.html vitalik vitalik-ux vitalik-ux.html vitalik vitalik-stealth vitalik-stealth.html vitalik vitalik-institutions vitalik-institutions.html vitalik vitalik-gpt3 vitalik-gpt3.html vitalik vitalik-excited vitalik-excited.html vitalik vitalik-maximalist vitalik-maximalist.html vitalik vitalik-proof_of_solvency vitalik-proof_of_solvency.html vitalik vitalik-ux_zhCN vitalik-ux_zhCN.html vitalik vitalik-revenue_evil_zhCN vitalik-revenue_evil_zhCN.html vitalik vitalik-revenue_evil vitalik-revenue_evil.html vitalik vitalik-daos vitalik-daos.html vitalik vitalik-layer_3 vitalik-layer_3.html vitalik vitalik-ens vitalik-ens.html vitalik vitalik-zkevm_TR vitalik-zkevm_TR.html vitalik vitalik-zkevm vitalik-zkevm.html vitalik vitalik-zkevm_zhTW vitalik-zkevm_zhTW.html vitalik vitalik-networkstates vitalik-networkstates.html vitalik vitalik-networkstates_zhCN vitalik-networkstates_zhCN.html vitalik vitalik-backpack vitalik-backpack.html vitalik vitalik-using_snarks vitalik-using_snarks.html vitalik vitalik-nonfin vitalik-nonfin.html vitalik vitalik-stable vitalik-stable.html vitalik vitalik-road vitalik-road.html vitalik vitalik-trustedsetup vitalik-trustedsetup.html vitalik vitalik-complexity vitalik-complexity.html vitalik vitalik-soulbound vitalik-soulbound.html vitalik vitalik-bullveto vitalik-bullveto.html vitalik vitalik-endgame vitalik-endgame.html vitalik vitalik-retro1 vitalik-retro1.html vitalik vitalik-halo vitalik-halo.html vitalik vitalik-cities vitalik-cities.html vitalik vitalik-limits vitalik-limits.html vitalik vitalik-prices vitalik-prices.html vitalik vitalik-voting3 vitalik-voting3.html vitalik vitalik-gini vitalik-gini.html vitalik vitalik-verkle vitalik-verkle.html vitalik vitalik-voting2 vitalik-voting2.html vitalik vitalik-scaling vitalik-scaling.html vitalik vitalik-sharding vitalik-sharding.html vitalik vitalik-round9 vitalik-round9.html vitalik vitalik-legitimacy vitalik-legitimacy.html vitalik vitalik-legitimacy_ES vitalik-legitimacy_ES.html vitalik vitalik-election vitalik-election.html vitalik vitalik-snarks vitalik-snarks.html vitalik vitalik-recovery vitalik-recovery.html vitalik vitalik-rollup vitalik-rollup.html vitalik vitalik-rollup_ES vitalik-rollup_ES.html vitalik vitalik-end vitalik-end.html vitalik vitalik-cryptoai vitalik-cryptoai.html vitalik vitalik-endnotes vitalik-endnotes.html vitalik vitalik-concave vitalik-concave.html vitalik vitalik-pos2020 vitalik-pos2020.html vitalik vitalik-pos2020_zhTW vitalik-pos2020_zhTW.html vitalik vitalik-round7_FR vitalik-round7_FR.html vitalik vitalik-round7 vitalik-round7.html vitalik vitalik-coordination vitalik-coordination.html vitalik vitalik-trust vitalik-trust.html vitalik vitalik-philosophy vitalik-philosophy.html vitalik vitalik-round6 vitalik-round6.html vitalik vitalik-homomorphic vitalik-homomorphic.html vitalik vitalik-round5 vitalik-round5.html vitalik vitalik-garbled vitalik-garbled.html vitalik vitalik-round4 vitalik-round4.html vitalik vitalik-election_zhTW vitalik-election_zhTW.html vitalik vitalik-mvb vitalik-mvb.html vitalik vitalik-christmas vitalik-christmas.html vitalik vitalik-quadratic vitalik-quadratic.html vitalik vitalik-progress vitalik-progress.html vitalik vitalik-gitcoin vitalik-gitcoin.html vitalik vitalik-story vitalik-story.html vitalik vitalik-plonk vitalik-plonk.html vitalik vitalik-hybrid_layer_2 vitalik-hybrid_layer_2.html vitalik vitalik-plasma_vs_sharding vitalik-plasma_vs_sharding.html vitalik vitalik-fft vitalik-fft.html vitalik vitalik-control_as_liability vitalik-control_as_liability.html vitalik vitalik-free_speech vitalik-free_speech.html vitalik vitalik-collusion vitalik-collusion.html vitalik vitalik-cantor vitalik-cantor.html vitalik vitalik-cbc_casper vitalik-cbc_casper.html vitalik vitalik-central_planning vitalik-central_planning.html vitalik vitalik-layer_1 vitalik-layer_1.html vitalik vitalik-99_fault_tolerant vitalik-99_fault_tolerant.html vitalik vitalik-starks_part_3 vitalik-starks_part_3.html vitalik vitalik-radical_markets vitalik-radical_markets.html vitalik vitalik-plutocracy vitalik-plutocracy.html vitalik vitalik-pos_faq vitalik-pos_faq.html vitalik vitalik-sharding_faq vitalik-sharding_faq.html vitalik vitalik-voting vitalik-voting.html vitalik vitalik-gas_analysis vitalik-gas_analysis.html vitalik vitalik-starks_part_2 vitalik-starks_part_2.html vitalik vitalik-starks_part_1 vitalik-starks_part_1.html vitalik vitalik-moe vitalik-moe.html vitalik vitalik-prehistory vitalik-prehistory.html vitalik vitalik-metcalfe vitalik-metcalfe.html vitalik vitalik-triangle_of_harm vitalik-triangle_of_harm.html vitalik vitalik-marketmakers vitalik-marketmakers.html vitalik vitalik-sales vitalik-sales.html vitalik vitalik-coordination_problems vitalik-coordination_problems.html vitalik vitalik-forks_and_markets vitalik-forks_and_markets.html vitalik vitalik-a_note_on_charity vitalik-a_note_on_charity.html vitalik vitalik-zk_snarks vitalik-zk_snarks.html vitalik vitalik-exploring_ecp vitalik-exploring_ecp.html vitalik vitalik-pos_design_TR vitalik-pos_design_TR.html vitalik vitalik-pos_design vitalik-pos_design.html vitalik vitalik-qap vitalik-qap.html vitalik vitalik-On_Collusion_Portuguese vitalik-On_Collusion_Portuguese.html vitalik vitalik-On_Collusion_DE vitalik-On_Collusion_DE.html vitalik vitalik-On_Collusion_Polish vitalik-On_Collusion_Polish.html vitalik vitalik-On_Collusion_IT vitalik-On_Collusion_IT.html eips eips-eip-778 eips-eip-778.html eips eips-eip-5069 eips-eip-5069.html eips eips-eip-2255 eips-eip-2255.html eips eips-eip-2387 eips-eip-2387.html eips eips-eip-5133 eips-eip-5133.html eips eips-eip-4881 eips-eip-4881.html eips eips-eip-2976 eips-eip-2976.html eips eips-eip-2364 eips-eip-2364.html eips eips-eip-158 eips-eip-158.html eips eips-eip-4955 eips-eip-4955.html eips eips-eip-2612 eips-eip-2612.html eips eips-eip-1363 eips-eip-1363.html eips eips-eip-3668 eips-eip-3668.html eips eips-eip-1193 eips-eip-1193.html eips eips-eip-5006 eips-eip-5006.html eips eips-eip-1052 eips-eip-1052.html eips eips-eip-197 eips-eip-197.html eips eips-eip-1155 eips-eip-1155.html eips eips-eip-1716 eips-eip-1716.html eips eips-eip-1344 eips-eip-1344.html eips eips-eip-2696 eips-eip-2696.html eips eips-eip-2982 eips-eip-2982.html eips eips-eip-1884 eips-eip-1884.html eips eips-eip-1679 eips-eip-1679.html eips eips-eip-211 eips-eip-211.html eips eips-eip-747 eips-eip-747.html eips eips-eip-20 eips-eip-20.html eips eips-eip-1967 eips-eip-1967.html eips eips-eip-3448 eips-eip-3448.html eips eips-eip-4895 eips-eip-4895.html eips eips-eip-4519 eips-eip-4519.html eips eips-eip-4907 eips-eip-4907.html eips eips-eip-606 eips-eip-606.html eips eips-eip-2771 eips-eip-2771.html eips eips-eip-2098 eips-eip-2098.html eips eips-eip-868 eips-eip-868.html eips eips-eip-3529 eips-eip-3529.html eips eips-eip-234 eips-eip-234.html eips eips-eip-1 eips-eip-1.html eips eips-eip-2678 eips-eip-2678.html eips eips-eip-181 eips-eip-181.html eips eips-eip-170 eips-eip-170.html eips eips-eip-4906 eips-eip-4906.html eips eips-eip-2 eips-eip-2.html eips eips-eip-2930 eips-eip-2930.html eips eips-eip-2981 eips-eip-2981.html eips eips-eip-5169 eips-eip-5169.html eips eips-eip-2200 eips-eip-2200.html eips eips-eip-1108 eips-eip-1108.html eips eips-eip-4834 eips-eip-4834.html eips eips-eip-2135 eips-eip-2135.html eips eips-eip-706 eips-eip-706.html eips eips-eip-214 eips-eip-214.html eips eips-eip-3855 eips-eip-3855.html eips eips-eip-145 eips-eip-145.html eips eips-eip-3475 eips-eip-3475.html eips eips-eip-4345 eips-eip-4345.html eips eips-eip-777 eips-eip-777.html eips eips-eip-627 eips-eip-627.html eips eips-eip-4736 eips-eip-4736.html eips eips-eip-2929 eips-eip-2929.html eips eips-eip-4626 eips-eip-4626.html eips eips-eip-2384 eips-eip-2384.html eips eips-eip-4910 eips-eip-4910.html eips eips-eip-1820 eips-eip-1820.html eips eips-eip-3860 eips-eip-3860.html eips eips-eip-150 eips-eip-150.html eips eips-eip-196 eips-eip-196.html eips eips-eip-165 eips-eip-165.html eips eips-eip-649 eips-eip-649.html eips eips-eip-2228 eips-eip-2228.html eips eips-eip-4337 eips-eip-4337.html eips eips-eip-141 eips-eip-141.html eips eips-eip-2159 eips-eip-2159.html eips eips-eip-684 eips-eip-684.html eips eips-eip-225 eips-eip-225.html eips eips-eip-3541 eips-eip-3541.html eips eips-eip-3156 eips-eip-3156.html eips eips-eip-2481 eips-eip-2481.html eips eips-eip-1167 eips-eip-1167.html eips eips-eip-601 eips-eip-601.html eips eips-eip-721 eips-eip-721.html eips eips-eip-1559 eips-eip-1559.html eips eips-eip-3554 eips-eip-3554.html eips eips-eip-600 eips-eip-600.html eips eips-eip-3198 eips-eip-3198.html eips eips-eip-198 eips-eip-198.html eips eips-eip-55 eips-eip-55.html eips eips-eip-2028 eips-eip-2028.html eips eips-eip-3651 eips-eip-3651.html eips eips-eip-7432 eips-eip-7432.html eips eips-eip-5202 eips-eip-5202.html eips eips-eip-5219 eips-eip-5219.html eips eips-eip-5267 eips-eip-5267.html eips eips-eip-5313 eips-eip-5313.html eips eips-eip-1013 eips-eip-1013.html eips eips-eip-5380 eips-eip-5380.html eips eips-eip-5484 eips-eip-5484.html eips eips-eip-5489 eips-eip-5489.html eips eips-eip-5507 eips-eip-5507.html eips eips-eip-1283 eips-eip-1283.html eips eips-eip-5570 eips-eip-5570.html eips eips-eip-5606 eips-eip-5606.html eips eips-eip-5615 eips-eip-5615.html eips eips-eip-5646 eips-eip-5646.html eips eips-eip-5679 eips-eip-5679.html eips eips-eip-5725 eips-eip-5725.html eips eips-eip-4938 eips-eip-4938.html eips eips-eip-5564 eips-eip-5564.html eips eips-eip-5750 eips-eip-5750.html eips eips-eip-5757 eips-eip-5757.html eips eips-eip-5773 eips-eip-5773.html eips eips-eip-6049 eips-eip-6049.html eips eips-eip-6059 eips-eip-6059.html eips eips-eip-6066 eips-eip-6066.html eips eips-eip-5007 eips-eip-5007.html eips eips-eip-6122 eips-eip-6122.html eips eips-eip-6147 eips-eip-6147.html eips eips-eip-6150 eips-eip-6150.html eips eips-eip-6220 eips-eip-6220.html eips eips-eip-6493 eips-eip-6493.html eips eips-eip-6381 eips-eip-6381.html eips eips-eip-6454 eips-eip-6454.html eips eips-eip-6492 eips-eip-6492.html eips eips-eip-6672 eips-eip-6672.html eips eips-eip-6808 eips-eip-6808.html eips eips-eip-6809 eips-eip-6809.html eips eips-eip-6953 eips-eip-6953.html eips eips-eip-5375 eips-eip-5375.html eips eips-eip-6982 eips-eip-6982.html eips eips-eip-7053 eips-eip-7053.html eips eips-eip-7066 eips-eip-7066.html eips eips-eip-7569 eips-eip-7569.html eips eips-eip-5528 eips-eip-5528.html eips eips-eip-7329 eips-eip-7329.html eips eips-eip-7401 eips-eip-7401.html eips eips-eip-7409 eips-eip-7409.html eips eips-eip-7439 eips-eip-7439.html eips eips-eip-1153 eips-eip-1153.html eips eips-eip-1191 eips-eip-1191.html eips eips-eip-1328 eips-eip-1328.html eips eips-eip-2266 eips-eip-2266.html eips eips-eip-3076 eips-eip-3076.html eips eips-eip-4788 eips-eip-4788.html eips eips-eip-4844 eips-eip-4844.html eips eips-eip-6239 eips-eip-6239.html eips eips-eip-779 eips-eip-779.html eips eips-eip-5114 eips-eip-5114.html eips eips-eip-5164 eips-eip-5164.html eips eips-eip-5216 eips-eip-5216.html eips eips-eip-5453 eips-eip-5453.html eips eips-eip-4 eips-eip-4.html eips eips-eip-5585 eips-eip-5585.html eips eips-eip-5793 eips-eip-5793.html eips eips-eip-6093 eips-eip-6093.html eips eips-eip-6357 eips-eip-6357.html eips eips-eip-607 eips-eip-607.html eips eips-eip-7044 eips-eip-7044.html eips eips-eip-7045 eips-eip-7045.html eips eips-eip-7092 eips-eip-7092.html eips eips-eip-5192 eips-eip-5192.html eips eips-eip-7514 eips-eip-7514.html eips eips-eip-7516 eips-eip-7516.html eips eips-eip-663 eips-eip-663.html eips eips-eip-1185 eips-eip-1185.html eips eips-eip-3074 eips-eip-3074.html eips eips-eip-4400 eips-eip-4400.html eips eips-eip-3670 eips-eip-3670.html eips eips-eip-4200 eips-eip-4200.html eips eips-eip-4361 eips-eip-4361.html eips eips-eip-4750 eips-eip-4750.html eips eips-eip-3643 eips-eip-3643.html eips eips-eip-5247 eips-eip-5247.html eips eips-eip-5269 eips-eip-5269.html eips eips-eip-5289 eips-eip-5289.html eips eips-eip-5450 eips-eip-5450.html eips eips-eip-5521 eips-eip-5521.html eips eips-eip-4973 eips-eip-4973.html eips eips-eip-5568 eips-eip-5568.html eips eips-eip-5639 eips-eip-5639.html eips eips-eip-5656 eips-eip-5656.html eips eips-eip-173 eips-eip-173.html eips eips-eip-5982 eips-eip-5982.html eips eips-eip-6065 eips-eip-6065.html eips eips-eip-137 eips-eip-137.html eips eips-eip-6188 eips-eip-6188.html eips eips-eip-6189 eips-eip-6189.html eips eips-eip-6315 eips-eip-6315.html eips eips-eip-6358 eips-eip-6358.html eips eips-eip-6366 eips-eip-6366.html eips eips-eip-2681 eips-eip-2681.html eips eips-eip-6404 eips-eip-6404.html eips eips-eip-6465 eips-eip-6465.html eips eips-eip-6466 eips-eip-6466.html eips eips-eip-6372 eips-eip-6372.html eips eips-eip-6551 eips-eip-6551.html eips eips-eip-6596 eips-eip-6596.html eips eips-eip-6617 eips-eip-6617.html eips eips-eip-6916 eips-eip-6916.html eips eips-eip-6956 eips-eip-6956.html eips eips-eip-6997 eips-eip-6997.html eips eips-eip-7144 eips-eip-7144.html eips eips-eip-7212 eips-eip-7212.html eips eips-eip-2124 eips-eip-2124.html eips eips-eip-7495 eips-eip-7495.html eips eips-eip-4399 eips-eip-4399.html eips eips-eip-7528 eips-eip-7528.html eips eips-eip-7535 eips-eip-7535.html eips eips-eip-6780 eips-eip-6780.html eips eips-eip-3607 eips-eip-3607.html eips eips-eip-725 eips-eip-725.html eips eips-eip-658 eips-eip-658.html eips eips-eip-1202 eips-eip-1202.html eips eips-eip-2539 eips-eip-2539.html eips eips-eip-3026 eips-eip-3026.html eips eips-eip-3091 eips-eip-3091.html eips eips-eip-86 eips-eip-86.html eips eips-eip-5008 eips-eip-5008.html eips eips-eip-4824 eips-eip-4824.html eips eips-eip-4883 eips-eip-4883.html eips eips-eip-4972 eips-eip-4972.html eips eips-eip-5115 eips-eip-5115.html eips eips-eip-5173 eips-eip-5173.html eips eips-eip-5189 eips-eip-5189.html eips eips-eip-5573 eips-eip-5573.html eips eips-eip-5604 eips-eip-5604.html eips eips-eip-5700 eips-eip-5700.html eips eips-eip-5727 eips-eip-5727.html eips eips-eip-5791 eips-eip-5791.html eips eips-eip-5806 eips-eip-5806.html eips eips-eip-6046 eips-eip-6046.html eips eips-eip-6110 eips-eip-6110.html eips eips-eip-6123 eips-eip-6123.html eips eips-eip-101 eips-eip-101.html eips eips-eip-6206 eips-eip-6206.html eips eips-eip-6327 eips-eip-6327.html eips eips-eip-6475 eips-eip-6475.html eips eips-eip-6604 eips-eip-6604.html eips eips-eip-1014 eips-eip-1014.html eips eips-eip-6682 eips-eip-6682.html eips eips-eip-6690 eips-eip-6690.html eips eips-eip-6734 eips-eip-6734.html eips eips-eip-6735 eips-eip-6735.html eips eips-eip-6785 eips-eip-6785.html eips eips-eip-6786 eips-eip-6786.html eips eips-eip-6787 eips-eip-6787.html eips eips-eip-6800 eips-eip-6800.html eips eips-eip-6806 eips-eip-6806.html eips eips-eip-6821 eips-eip-6821.html eips eips-eip-6823 eips-eip-6823.html eips eips-eip-6860 eips-eip-6860.html eips eips-eip-6864 eips-eip-6864.html eips eips-eip-5496 eips-eip-5496.html eips eips-eip-6873 eips-eip-6873.html eips eips-eip-6900 eips-eip-6900.html eips eips-eip-6909 eips-eip-6909.html eips eips-eip-7251 eips-eip-7251.html eips eips-eip-6944 eips-eip-6944.html eips eips-eip-6960 eips-eip-6960.html eips eips-eip-6968 eips-eip-6968.html eips eips-eip-6981 eips-eip-6981.html eips eips-eip-7002 eips-eip-7002.html eips eips-eip-7007 eips-eip-7007.html eips eips-eip-7015 eips-eip-7015.html eips eips-eip-7039 eips-eip-7039.html eips eips-eip-7069 eips-eip-7069.html eips eips-eip-7160 eips-eip-7160.html eips eips-eip-7093 eips-eip-7093.html eips eips-eip-7196 eips-eip-7196.html eips eips-eip-7204 eips-eip-7204.html eips eips-eip-7208 eips-eip-7208.html eips eips-eip-7246 eips-eip-7246.html eips eips-eip-5 eips-eip-5.html eips eips-eip-7254 eips-eip-7254.html eips eips-eip-7266 eips-eip-7266.html eips eips-eip-7303 eips-eip-7303.html eips eips-eip-7377 eips-eip-7377.html eips eips-eip-7378 eips-eip-7378.html eips eips-eip-7405 eips-eip-7405.html eips eips-eip-7406 eips-eip-7406.html eips eips-eip-7410 eips-eip-7410.html eips eips-eip-7412 eips-eip-7412.html eips eips-eip-7417 eips-eip-7417.html eips eips-eip-7425 eips-eip-7425.html eips eips-eip-7441 eips-eip-7441.html eips eips-eip-7444 eips-eip-7444.html eips eips-eip-7480 eips-eip-7480.html eips eips-eip-7484 eips-eip-7484.html eips eips-eip-7496 eips-eip-7496.html eips eips-eip-7498 eips-eip-7498.html eips eips-eip-7506 eips-eip-7506.html eips eips-eip-7507 eips-eip-7507.html eips eips-eip-7508 eips-eip-7508.html eips eips-eip-7509 eips-eip-7509.html eips eips-eip-7510 eips-eip-7510.html eips eips-eip-7511 eips-eip-7511.html eips eips-eip-7512 eips-eip-7512.html eips eips-eip-7513 eips-eip-7513.html eips eips-eip-7517 eips-eip-7517.html eips eips-eip-5920 eips-eip-5920.html eips eips-eip-7521 eips-eip-7521.html eips eips-eip-7522 eips-eip-7522.html eips eips-eip-7523 eips-eip-7523.html eips eips-eip-7527 eips-eip-7527.html eips eips-eip-7529 eips-eip-7529.html eips eips-eip-7531 eips-eip-7531.html eips eips-eip-6865 eips-eip-6865.html eips eips-eip-7538 eips-eip-7538.html eips eips-eip-7542 eips-eip-7542.html eips eips-eip-7545 eips-eip-7545.html eips eips-eip-7547 eips-eip-7547.html eips eips-eip-7548 eips-eip-7548.html eips eips-eip-7549 eips-eip-7549.html eips eips-eip-7561 eips-eip-7561.html eips eips-eip-7568 eips-eip-7568.html eips eips-eip-7572 eips-eip-7572.html eips eips-eip-7579 eips-eip-7579.html eips eips-eip-7587 eips-eip-7587.html eips eips-eip-6963 eips-eip-6963.html eips eips-eip-152 eips-eip-152.html eips eips-eip-107 eips-eip-107.html eips eips-eip-205 eips-eip-205.html eips eips-eip-210 eips-eip-210.html eips eips-eip-233 eips-eip-233.html eips eips-eip-608 eips-eip-608.html eips eips-eip-712 eips-eip-712.html eips eips-eip-634 eips-eip-634.html eips eips-eip-665 eips-eip-665.html eips eips-eip-689 eips-eip-689.html eips eips-eip-100 eips-eip-100.html eips eips-eip-758 eips-eip-758.html eips eips-eip-801 eips-eip-801.html eips eips-eip-823 eips-eip-823.html eips eips-eip-831 eips-eip-831.html eips eips-eip-858 eips-eip-858.html eips eips-eip-867 eips-eip-867.html eips eips-eip-695 eips-eip-695.html eips eips-eip-897 eips-eip-897.html eips eips-eip-900 eips-eip-900.html eips eips-eip-969 eips-eip-969.html eips eips-eip-884 eips-eip-884.html eips eips-eip-926 eips-eip-926.html eips eips-eip-927 eips-eip-927.html eips eips-eip-998 eips-eip-998.html eips eips-eip-1010 eips-eip-1010.html eips eips-eip-1011 eips-eip-1011.html eips eips-eip-2464 eips-eip-2464.html eips eips-eip-1051 eips-eip-1051.html eips eips-eip-1056 eips-eip-1056.html eips eips-eip-1057 eips-eip-1057.html eips eips-eip-1062 eips-eip-1062.html eips eips-eip-1066 eips-eip-1066.html eips eips-eip-1077 eips-eip-1077.html eips eips-eip-1078 eips-eip-1078.html eips eips-eip-5732 eips-eip-5732.html eips eips-eip-1588 eips-eip-1588.html eips eips-eip-1087 eips-eip-1087.html eips eips-eip-1102 eips-eip-1102.html eips eips-eip-1109 eips-eip-1109.html eips eips-eip-609 eips-eip-609.html eips eips-eip-1132 eips-eip-1132.html eips eips-eip-1175 eips-eip-1175.html eips eips-eip-1178 eips-eip-1178.html eips eips-eip-1186 eips-eip-1186.html eips eips-eip-1203 eips-eip-1203.html eips eips-eip-1207 eips-eip-1207.html eips eips-eip-1227 eips-eip-1227.html eips eips-eip-1261 eips-eip-1261.html eips eips-eip-1276 eips-eip-1276.html eips eips-eip-3525 eips-eip-3525.html eips eips-eip-1295 eips-eip-1295.html eips eips-eip-1129 eips-eip-1129.html eips eips-eip-1337 eips-eip-1337.html eips eips-eip-1352 eips-eip-1352.html eips eips-eip-1380 eips-eip-1380.html eips eips-eip-1386 eips-eip-1386.html eips eips-eip-1387 eips-eip-1387.html eips eips-eip-1388 eips-eip-1388.html eips eips-eip-3102 eips-eip-3102.html eips eips-eip-1285 eips-eip-1285.html eips eips-eip-3085 eips-eip-3085.html eips eips-eip-1444 eips-eip-1444.html eips eips-eip-1450 eips-eip-1450.html eips eips-eip-1459 eips-eip-1459.html eips eips-eip-1462 eips-eip-1462.html eips eips-eip-1470 eips-eip-1470.html eips eips-eip-1474 eips-eip-1474.html eips eips-eip-1482 eips-eip-1482.html eips eips-eip-1484 eips-eip-1484.html eips eips-eip-1485 eips-eip-1485.html eips eips-eip-1491 eips-eip-1491.html eips eips-eip-1504 eips-eip-1504.html eips eips-eip-1523 eips-eip-1523.html eips eips-eip-1571 eips-eip-1571.html eips eips-eip-1577 eips-eip-1577.html eips eips-eip-1581 eips-eip-1581.html eips eips-eip-7085 eips-eip-7085.html eips eips-eip-1592 eips-eip-1592.html eips eips-eip-1613 eips-eip-1613.html eips eips-eip-1616 eips-eip-1616.html eips eips-eip-902 eips-eip-902.html eips eips-eip-1633 eips-eip-1633.html eips eips-eip-1681 eips-eip-1681.html eips eips-eip-1702 eips-eip-1702.html eips eips-eip-1710 eips-eip-1710.html eips eips-eip-1753 eips-eip-1753.html eips eips-eip-1761 eips-eip-1761.html eips eips-eip-1767 eips-eip-1767.html eips eips-eip-1775 eips-eip-1775.html eips eips-eip-1803 eips-eip-1803.html eips eips-eip-1812 eips-eip-1812.html eips eips-eip-1822 eips-eip-1822.html eips eips-eip-1829 eips-eip-1829.html eips eips-eip-1844 eips-eip-1844.html eips eips-eip-1872 eips-eip-1872.html eips eips-eip-1895 eips-eip-1895.html eips eips-eip-1438 eips-eip-1438.html eips eips-eip-1900 eips-eip-1900.html eips eips-eip-1901 eips-eip-1901.html eips eips-eip-2309 eips-eip-2309.html eips eips-eip-1973 eips-eip-1973.html eips eips-eip-1921 eips-eip-1921.html eips eips-eip-1930 eips-eip-1930.html eips eips-eip-1948 eips-eip-1948.html eips eips-eip-615 eips-eip-615.html eips eips-eip-1962 eips-eip-1962.html eips eips-eip-1965 eips-eip-1965.html eips eips-eip-1080 eips-eip-1080.html eips eips-eip-1985 eips-eip-1985.html eips eips-eip-2700 eips-eip-2700.html eips eips-eip-2003 eips-eip-2003.html eips eips-eip-2009 eips-eip-2009.html eips eips-eip-2014 eips-eip-2014.html eips eips-eip-2015 eips-eip-2015.html eips eips-eip-2018 eips-eip-2018.html eips eips-eip-2019 eips-eip-2019.html eips eips-eip-3675 eips-eip-3675.html eips eips-eip-7590 eips-eip-7590.html eips eips-eip-2026 eips-eip-2026.html eips eips-eip-2027 eips-eip-2027.html eips eips-eip-2029 eips-eip-2029.html eips eips-eip-2031 eips-eip-2031.html eips eips-eip-2035 eips-eip-2035.html eips eips-eip-2045 eips-eip-2045.html eips eips-eip-2046 eips-eip-2046.html eips eips-eip-2069 eips-eip-2069.html eips eips-eip-2070 eips-eip-2070.html eips eips-eip-1015 eips-eip-1015.html eips eips-eip-918 eips-eip-918.html eips eips-eip-2242 eips-eip-2242.html eips eips-eip-2256 eips-eip-2256.html eips eips-eip-2294 eips-eip-2294.html eips eips-eip-2304 eips-eip-2304.html eips eips-eip-2327 eips-eip-2327.html eips eips-eip-1959 eips-eip-1959.html eips eips-eip-2333 eips-eip-2333.html eips eips-eip-2334 eips-eip-2334.html eips eips-eip-2335 eips-eip-2335.html eips eips-eip-2378 eips-eip-2378.html eips eips-eip-2386 eips-eip-2386.html eips eips-eip-2390 eips-eip-2390.html eips eips-eip-2400 eips-eip-2400.html eips eips-eip-2470 eips-eip-2470.html eips eips-eip-2474 eips-eip-2474.html eips eips-eip-2477 eips-eip-2477.html eips eips-eip-2488 eips-eip-2488.html eips eips-eip-2494 eips-eip-2494.html eips eips-eip-2515 eips-eip-2515.html eips eips-eip-2520 eips-eip-2520.html eips eips-eip-2525 eips-eip-2525.html eips eips-eip-2537 eips-eip-2537.html eips eips-eip-2542 eips-eip-2542.html eips eips-eip-2544 eips-eip-2544.html eips eips-eip-2566 eips-eip-2566.html eips eips-eip-2569 eips-eip-2569.html eips eips-eip-2583 eips-eip-2583.html eips eips-eip-2584 eips-eip-2584.html eips eips-eip-2593 eips-eip-2593.html eips eips-eip-2615 eips-eip-2615.html eips eips-eip-2645 eips-eip-2645.html eips eips-eip-2657 eips-eip-2657.html eips eips-eip-2666 eips-eip-2666.html eips eips-eip-2680 eips-eip-2680.html eips eips-eip-2746 eips-eip-2746.html eips eips-eip-2767 eips-eip-2767.html eips eips-eip-2770 eips-eip-2770.html eips eips-eip-2803 eips-eip-2803.html eips eips-eip-2831 eips-eip-2831.html eips eips-eip-2844 eips-eip-2844.html eips eips-eip-2848 eips-eip-2848.html eips eips-eip-2876 eips-eip-2876.html eips eips-eip-2917 eips-eip-2917.html eips eips-eip-2926 eips-eip-2926.html eips eips-eip-3561 eips-eip-3561.html eips eips-eip-6662 eips-eip-6662.html eips eips-eip-2937 eips-eip-2937.html eips eips-eip-2938 eips-eip-2938.html eips eips-eip-2942 eips-eip-2942.html eips eips-eip-2970 eips-eip-2970.html eips eips-eip-2980 eips-eip-2980.html eips eips-eip-2997 eips-eip-2997.html eips eips-eip-3000 eips-eip-3000.html eips eips-eip-5749 eips-eip-5749.html eips eips-eip-3009 eips-eip-3009.html eips eips-eip-3014 eips-eip-3014.html eips eips-eip-3030 eips-eip-3030.html eips eips-eip-3041 eips-eip-3041.html eips eips-eip-3044 eips-eip-3044.html eips eips-eip-3045 eips-eip-3045.html eips eips-eip-3046 eips-eip-3046.html eips eips-eip-3068 eips-eip-3068.html eips eips-eip-3135 eips-eip-3135.html eips eips-eip-3143 eips-eip-3143.html eips eips-eip-6105 eips-eip-6105.html eips eips-eip-3220 eips-eip-3220.html eips eips-eip-1234 eips-eip-1234.html eips eips-eip-3234 eips-eip-3234.html eips eips-eip-3238 eips-eip-3238.html eips eips-eip-3267 eips-eip-3267.html eips eips-eip-3298 eips-eip-3298.html eips eips-eip-3300 eips-eip-3300.html eips eips-eip-7533 eips-eip-7533.html eips eips-eip-3326 eips-eip-3326.html eips eips-eip-3336 eips-eip-3336.html eips eips-eip-681 eips-eip-681.html eips eips-eip-3368 eips-eip-3368.html eips eips-eip-3372 eips-eip-3372.html eips eips-eip-3386 eips-eip-3386.html eips eips-eip-3403 eips-eip-3403.html eips eips-eip-3416 eips-eip-3416.html eips eips-eip-3436 eips-eip-3436.html eips eips-eip-3440 eips-eip-3440.html eips eips-eip-3450 eips-eip-3450.html eips eips-eip-3455 eips-eip-3455.html eips eips-eip-3508 eips-eip-3508.html eips eips-eip-3520 eips-eip-3520.html eips eips-eip-3521 eips-eip-3521.html eips eips-eip-3534 eips-eip-3534.html eips eips-eip-5143 eips-eip-5143.html eips eips-eip-2020 eips-eip-2020.html eips eips-eip-3569 eips-eip-3569.html eips eips-eip-3584 eips-eip-3584.html eips eips-eip-3589 eips-eip-3589.html eips eips-eip-3690 eips-eip-3690.html eips eips-eip-6170 eips-eip-6170.html eips eips-eip-3722 eips-eip-3722.html eips eips-eip-3754 eips-eip-3754.html eips eips-eip-3756 eips-eip-3756.html eips eips-eip-3770 eips-eip-3770.html eips eips-eip-3772 eips-eip-3772.html eips eips-eip-3788 eips-eip-3788.html eips eips-eip-3978 eips-eip-3978.html eips eips-eip-4341 eips-eip-4341.html eips eips-eip-4353 eips-eip-4353.html eips eips-eip-4393 eips-eip-4393.html eips eips-eip-4396 eips-eip-4396.html eips eips-eip-4430 eips-eip-4430.html eips eips-eip-4444 eips-eip-4444.html eips eips-eip-4488 eips-eip-4488.html eips eips-eip-4494 eips-eip-4494.html eips eips-eip-4520 eips-eip-4520.html eips eips-eip-4521 eips-eip-4521.html eips eips-eip-6 eips-eip-6.html eips eips-eip-4527 eips-eip-4527.html eips eips-eip-4546 eips-eip-4546.html eips eips-eip-4573 eips-eip-4573.html eips eips-eip-4671 eips-eip-4671.html eips eips-eip-4675 eips-eip-4675.html eips eips-eip-4747 eips-eip-4747.html eips eips-eip-2935 eips-eip-2935.html eips eips-eip-4760 eips-eip-4760.html eips eips-eip-4762 eips-eip-4762.html eips eips-eip-4799 eips-eip-4799.html eips eips-eip-4803 eips-eip-4803.html eips eips-eip-7503 eips-eip-7503.html eips eips-eip-4885 eips-eip-4885.html eips eips-eip-4886 eips-eip-4886.html eips eips-eip-4931 eips-eip-4931.html eips eips-eip-4944 eips-eip-4944.html eips eips-eip-4950 eips-eip-4950.html eips eips-eip-4974 eips-eip-4974.html eips eips-eip-4987 eips-eip-4987.html eips eips-eip-5000 eips-eip-5000.html eips eips-eip-5003 eips-eip-5003.html eips eips-eip-5005 eips-eip-5005.html eips eips-eip-5018 eips-eip-5018.html eips eips-eip-5022 eips-eip-5022.html eips eips-eip-5027 eips-eip-5027.html eips eips-eip-5050 eips-eip-5050.html eips eips-eip-5058 eips-eip-5058.html eips eips-eip-5065 eips-eip-5065.html eips eips-eip-5081 eips-eip-5081.html eips eips-eip-5094 eips-eip-5094.html eips eips-eip-5095 eips-eip-5095.html eips eips-eip-5131 eips-eip-5131.html eips eips-eip-5139 eips-eip-5139.html eips eips-eip-7519 eips-eip-7519.html eips eips-eip-5185 eips-eip-5185.html eips eips-eip-5187 eips-eip-5187.html eips eips-eip-5218 eips-eip-5218.html eips eips-eip-5252 eips-eip-5252.html eips eips-eip-5283 eips-eip-5283.html eips eips-eip-5298 eips-eip-5298.html eips eips-eip-5334 eips-eip-5334.html eips eips-eip-5345 eips-eip-5345.html eips eips-eip-5409 eips-eip-5409.html eips eips-eip-5437 eips-eip-5437.html eips eips-eip-5478 eips-eip-5478.html eips eips-eip-5485 eips-eip-5485.html eips eips-eip-5501 eips-eip-5501.html eips eips-eip-5505 eips-eip-5505.html eips eips-eip-2157 eips-eip-2157.html eips eips-eip-5539 eips-eip-5539.html eips eips-eip-5553 eips-eip-5553.html eips eips-eip-5554 eips-eip-5554.html eips eips-eip-5559 eips-eip-5559.html eips eips-eip-5560 eips-eip-5560.html eips eips-eip-5593 eips-eip-5593.html eips eips-eip-5625 eips-eip-5625.html eips eips-eip-5630 eips-eip-5630.html eips eips-eip-5633 eips-eip-5633.html eips eips-eip-1081 eips-eip-1081.html eips eips-eip-5643 eips-eip-5643.html eips eips-eip-5719 eips-eip-5719.html eips eips-eip-5744 eips-eip-5744.html eips eips-eip-5753 eips-eip-5753.html eips eips-eip-5792 eips-eip-5792.html eips eips-eip-5805 eips-eip-5805.html eips eips-eip-5827 eips-eip-5827.html eips eips-eip-5850 eips-eip-5850.html eips eips-eip-5851 eips-eip-5851.html eips eips-eip-5883 eips-eip-5883.html eips eips-eip-5902 eips-eip-5902.html eips eips-eip-5988 eips-eip-5988.html eips eips-eip-6047 eips-eip-6047.html eips eips-eip-1922 eips-eip-1922.html eips eips-eip-6190 eips-eip-6190.html eips eips-eip-6224 eips-eip-6224.html eips eips-eip-6268 eips-eip-6268.html eips eips-eip-6353 eips-eip-6353.html eips eips-eip-6384 eips-eip-6384.html eips eips-eip-6464 eips-eip-6464.html eips eips-eip-6506 eips-eip-6506.html eips eips-eip-6538 eips-eip-6538.html eips eips-eip-6789 eips-eip-6789.html eips eips-eip-6810 eips-eip-6810.html eips eips-eip-6811 eips-eip-6811.html eips eips-eip-6888 eips-eip-6888.html eips eips-eip-6913 eips-eip-6913.html eips eips-eip-5635 eips-eip-5635.html eips eips-eip-3 eips-eip-3.html eips eips-eip-67 eips-eip-67.html eips eips-eip-875 eips-eip-875.html eips eips-eip-908 eips-eip-908.html eips eips-eip-999 eips-eip-999.html eips eips-eip-1123 eips-eip-1123.html eips eips-eip-1154 eips-eip-1154.html eips eips-eip-1240 eips-eip-1240.html eips eips-eip-1355 eips-eip-1355.html eips eips-eip-5023 eips-eip-5023.html eips eips-eip-1682 eips-eip-1682.html eips eips-eip-1706 eips-eip-1706.html eips eips-eip-3337 eips-eip-3337.html eips eips-eip-2025 eips-eip-2025.html eips eips-eip-2315 eips-eip-2315.html eips eips-eip-2458 eips-eip-2458.html eips eips-eip-2677 eips-eip-2677.html eips eips-eip-2711 eips-eip-2711.html eips eips-eip-2733 eips-eip-2733.html eips eips-eip-2780 eips-eip-2780.html eips eips-eip-2786 eips-eip-2786.html eips eips-eip-4804 eips-eip-4804.html eips eips-eip-3332 eips-eip-3332.html eips eips-eip-160 eips-eip-160.html eips eips-eip-3382 eips-eip-3382.html eips eips-eip-3779 eips-eip-3779.html eips eips-eip-7199 eips-eip-7199.html eips eips-eip-7231 eips-eip-7231.html eips eips-eip-6120 eips-eip-6120.html eips eips-eip-1046 eips-eip-1046.html eips eips-eip-140 eips-eip-140.html eips eips-eip-7540 eips-eip-7540.html eips eips-eip-1418 eips-eip-1418.html eips eips-eip-3540 eips-eip-3540.html eips eips-eip-5516 eips-eip-5516.html eips eips-eip-4524 eips-eip-4524.html eips eips-eip-3374 eips-eip-3374.html eips eips-eip-3155 eips-eip-3155.html eips eips-eip-1271 eips-eip-1271.html eips eips-eip-191 eips-eip-191.html eips eips-eip-162 eips-eip-162.html eips eips-eip-3709 eips-eip-3709.html eips eips-eip-1923 eips-eip-1923.html eips eips-eip-2936 eips-eip-2936.html eips eips-eip-3224 eips-eip-3224.html eips eips-eip-2535 eips-eip-2535.html eips eips-eip-1538 eips-eip-1538.html eips eips-eip-2021 eips-eip-2021.html eips eips-eip-4863 eips-eip-4863.html eips eips-eip-3005 eips-eip-3005.html eips eips-eip-1620 eips-eip-1620.html eips eips-eip-1319 eips-eip-1319.html eips eips-eip-3322 eips-eip-3322.html eips eips-eip-2193 eips-eip-2193.html eips eips-eip-3338 eips-eip-3338.html eips eips-eip-2330 eips-eip-2330.html eips eips-eip-2565 eips-eip-2565.html eips eips-eip-155 eips-eip-155.html eips eips-eip-6051 eips-eip-6051.html eips eips-eip-1417 eips-eip-1417.html eips eips-eip-2718 eips-eip-2718.html eips eips-eip-7201 eips-eip-7201.html eips eips-eip-1890 eips-eip-1890.html eips eips-eip-4758 eips-eip-4758.html eips eips-eip-8 eips-eip-8.html eips eips-eip-1898 eips-eip-1898.html eips eips-eip-820 eips-eip-820.html eips eips-eip-161 eips-eip-161.html eips eips-eip-6988 eips-eip-6988.html eips eips-eip-1996 eips-eip-1996.html eips eips-eip-2972 eips-eip-2972.html eips eips-eip-6914 eips-eip-6914.html eips eips-eip-698 eips-eip-698.html eips eips-eip-7 eips-eip-7.html eips eips-eip-223 eips-eip-223.html eips eips-eip-190 eips-eip-190.html eips eips-eip-616 eips-eip-616.html blog blog-bootstrapping-a-decentralized-autonomous-corporation-part-3-identity-corp blog-bootstrapping-a-decentralized-autonomous-corporation-part-3-identity-corp.html blog blog-bootstrapping-an-autonomous-decentralized-corporation-part-2-interacting-with-the-world blog-bootstrapping-an-autonomous-decentralized-corporation-part-2-interacting-with-the-world.html blog blog-ethereum-now-going-public blog-ethereum-now-going-public.html blog blog-bootstrapping-a-decentralized-autonomous-corporation-part-i blog-bootstrapping-a-decentralized-autonomous-corporation-part-i.html blog blog-silos blog-silos.html blog blog-secret-sharing-daos-crypto-2-0 blog-secret-sharing-daos-crypto-2-0.html blog blog-call-bug-bounty-hunters blog-call-bug-bounty-hunters.html blog blog-ethereum-dev blog-ethereum-dev.html blog blog-gavs-ethereum-dev-update-iv blog-gavs-ethereum-dev-update-iv.html blog blog-devcon-0-recap blog-devcon-0-recap.html blog blog-inside-ethereum-devhub-berlin blog-inside-ethereum-devhub-berlin.html blog blog-proof-stake-learned-love-weak-subjectivity blog-proof-stake-learned-love-weak-subjectivity.html blog blog-bitcoin-maximalism-currency-platform-network-effects blog-bitcoin-maximalism-currency-platform-network-effects.html blog blog-gavs-dev-update-iii blog-gavs-dev-update-iii.html blog blog-scalability-part-3-metacoin-history-multichain blog-scalability-part-3-metacoin-history-multichain.html blog blog-search-stable-cryptocurrency blog-search-stable-cryptocurrency.html blog blog-stephans-ethereum-community-adoption-update-week-1 blog-stephans-ethereum-community-adoption-update-week-1.html blog blog-jeffs-ethereum-dev-update blog-jeffs-ethereum-dev-update.html blog blog-gavs-ethereum-dev-update-ii blog-gavs-ethereum-dev-update-ii.html blog blog-information-theoretic-account-secure-brainwallets blog-information-theoretic-account-secure-brainwallets.html blog blog-scalability-part-2-hypercubes blog-scalability-part-2-hypercubes.html blog blog-gavs-dev-update-ethereums blog-gavs-dev-update-ethereums.html blog blog-slasher-ghost-developments-proof-stake blog-slasher-ghost-developments-proof-stake.html blog blog-scalability-part-1-building-top blog-scalability-part-1-building-top.html blog blog-crypto-renaissance blog-crypto-renaissance.html blog blog-software-bounded-rationality blog-software-bounded-rationality.html blog blog-state-ethereum-august-edition blog-state-ethereum-august-edition.html blog blog-introduction-futarchy blog-introduction-futarchy.html blog blog-building-decentralized-web blog-building-decentralized-web.html blog blog-index blog-index.html blog blog-secret-sharing-erasure-coding-guide-aspiring-dropbox-decentralizer blog-secret-sharing-erasure-coding-guide-aspiring-dropbox-decentralizer.html blog blog-ether-sale-a-statistical-overview blog-ether-sale-a-statistical-overview.html blog blog-announcement-on-planned-exodus-withdrawal blog-announcement-on-planned-exodus-withdrawal.html blog blog-programming-society-with-asm-gavin-wood-at-assembly-2014 blog-programming-society-with-asm-gavin-wood-at-assembly-2014.html blog blog-ether-purchase-troubleshooting blog-ether-purchase-troubleshooting.html blog blog-launching-the-ether-sale blog-launching-the-ether-sale.html blog blog-ethereum-and-oracles blog-ethereum-and-oracles.html blog blog-the-ethereum-project blog-the-ethereum-project.html blog blog-toward-a-12-second-block-time blog-toward-a-12-second-block-time.html blog blog-how-to-make-a-purchase-in-the-ether-presale blog-how-to-make-a-purchase-in-the-ether-presale.html blog blog-stake blog-stake.html blog blog-advanced-contract-programming-example-schellingcoin blog-advanced-contract-programming-example-schellingcoin.html blog blog-mining blog-mining.html blog blog-ethereum-project-update blog-ethereum-project-update.html blog blog-what-if-ethereum-lived-on-a-treap-or-blockchains-charging-rent blog-what-if-ethereum-lived-on-a-treap-or-blockchains-charging-rent.html blog blog-on-long-term-cryptocurrency-distribution-models blog-on-long-term-cryptocurrency-distribution-models.html blog blog-long-range-attacks-the-serious-problem-with-adaptive-proof-of-work blog-long-range-attacks-the-serious-problem-with-adaptive-proof-of-work.html blog blog-the-xbox-and-ethereums-dual-mandate blog-the-xbox-and-ethereums-dual-mandate.html blog blog-what-is-ethereum-project-platform-fuel-stack blog-what-is-ethereum-project-platform-fuel-stack.html blog blog-daos-dacs-das-and-more-an-incomplete-terminology-guide blog-daos-dacs-das-and-more-an-incomplete-terminology-guide.html blog blog-serpent-upgrades-more-fun-stuff blog-serpent-upgrades-more-fun-stuff.html blog blog-decentralized-protocol-monetization-and-forks blog-decentralized-protocol-monetization-and-forks.html blog blog-pyethereum-and-serpent-programming-guide blog-pyethereum-and-serpent-programming-guide.html blog blog-the-issuance-model-in-ethereum blog-the-issuance-model-in-ethereum.html blog blog-schellingcoin-a-minimal-trust-universal-data-feed blog-schellingcoin-a-minimal-trust-universal-data-feed.html blog blog-the-latest-evm-ethereum-is-a-trust-free-closure-system blog-the-latest-evm-ethereum-is-a-trust-free-closure-system.html blog blog-the-question-of-mining blog-the-question-of-mining.html blog blog-daos-are-not-scary-part-2-reducing-barriers blog-daos-are-not-scary-part-2-reducing-barriers.html blog blog-daos-are-not-scary-part-1-self-enforcing-contracts-and-factum-law blog-daos-are-not-scary-part-1-self-enforcing-contracts-and-factum-law.html blog blog-ethereum-scalability-and-decentralization-updates blog-ethereum-scalability-and-decentralization-updates.html blog blog-important-statement-regarding-the-ether-pre-sale blog-important-statement-regarding-the-ether-pre-sale.html blog blog-why-not-just-use-x-an-instructive-example-from-bitcoin blog-why-not-just-use-x-an-instructive-example-from-bitcoin.html blog blog-cryptographic-code-obfuscation-decentralized-autonomous-organizations-are-about-to-take-a-huge-leap-forward blog-cryptographic-code-obfuscation-decentralized-autonomous-organizations-are-about-to-take-a-huge-leap-forward.html blog blog-more-thoughts-on-scripting-and-future-compatibility blog-more-thoughts-on-scripting-and-future-compatibility.html blog blog-introducing-ethereum-script-2-0 blog-introducing-ethereum-script-2-0.html blog blog-on-transaction-fees-and-the-fallacy-of-market-based-solutions blog-on-transaction-fees-and-the-fallacy-of-market-based-solutions.html blog blog-conference-alpha-testnet-and-ether-pre-sale-updates blog-conference-alpha-testnet-and-ether-pre-sale-updates.html blog blog-slasher-a-punitive-proof-of-stake-algorithm blog-slasher-a-punitive-proof-of-stake-algorithm.html blog blog-understanding-serenity-part-2-casper blog-understanding-serenity-part-2-casper.html blog blog-understanding-serenity-part-i-abstraction blog-understanding-serenity-part-i-abstraction.html blog blog-ethereum-in-practice-part-3-how-to-build-your-own-transparent-bank-on-the-blockchain blog-ethereum-in-practice-part-3-how-to-build-your-own-transparent-bank-on-the-blockchain.html blog blog-ethereum-in-practice-part-2-how-to-build-a-better-democracy-in-under-a-100-lines-of-code blog-ethereum-in-practice-part-2-how-to-build-a-better-democracy-in-under-a-100-lines-of-code.html blog blog-how-to-build-your-own-cryptocurrency blog-how-to-build-your-own-cryptocurrency.html blog blog-applications-of-security-deposits-and-prediction-markets-you-might-not-have-thought-about blog-applications-of-security-deposits-and-prediction-markets-you-might-not-have-thought-about.html blog blog-merkling-in-ethereum blog-merkling-in-ethereum.html blog blog-stateful-turing-complete-policies blog-stateful-turing-complete-policies.html blog blog-ethereum-dev-update-2015-week-44 blog-ethereum-dev-update-2015-week-44.html blog blog-microsoft-to-sponsor-ethereums-devcon1-2 blog-microsoft-to-sponsor-ethereums-devcon1-2.html blog blog-nick-szabo-confirmed-as-keynote-speaker-of-ethereums-devcon1 blog-nick-szabo-confirmed-as-keynote-speaker-of-ethereums-devcon1.html blog blog-security-alert-implementation-of-blockhash-instruction-in-c-and-go-clients-can-potentially-cause-consensus-issue-fixed-please-update blog-security-alert-implementation-of-blockhash-instruction-in-c-and-go-clients-can-potentially-cause-consensus-issue-fixed-please-update.html blog blog-vitaliks-research-and-ecosystem-update blog-vitaliks-research-and-ecosystem-update.html blog blog-ethereum-dev-update-2015-week-41 blog-ethereum-dev-update-2015-week-41.html blog blog-security-advisory-eth-cpp-ethereum-potentially-vulnerable-if-running-with-upnp-enabled blog-security-advisory-eth-cpp-ethereum-potentially-vulnerable-if-running-with-upnp-enabled.html blog blog-the-evolution-of-ethereum blog-the-evolution-of-ethereum.html blog blog-more-uncle-statistics blog-more-uncle-statistics.html blog blog-devcon-is-back blog-devcon-is-back.html blog blog-ethereum-comms-announcement blog-ethereum-comms-announcement.html blog blog-ethereum-wallet-developer-preview blog-ethereum-wallet-developer-preview.html blog blog-on-slow-and-fast-block-times blog-on-slow-and-fast-block-times.html blog blog-security-alert-previous-security-patch-can-lead-to-invalid-state-root-on-go-clients-with-a-specific-transaction-sequence-fixed-please-update blog-security-alert-previous-security-patch-can-lead-to-invalid-state-root-on-go-clients-with-a-specific-transaction-sequence-fixed-please-update.html blog blog-security-alert-implementation-bug-in-go-clients-causing-increase-in-difficulty-fixed-miners-check-and-update-go-clients-if-necessary blog-security-alert-implementation-bug-in-go-clients-causing-increase-in-difficulty-fixed-miners-check-and-update-go-clients-if-necessary.html blog blog-a-message-from-stephan-tual blog-a-message-from-stephan-tual.html blog blog-security-advisory-implementations-bugs-in-go-and-python-clients-can-cause-dos blog-security-advisory-implementations-bugs-in-go-and-python-clients-can-cause-dos.html blog blog-devcon-one-postponed-until-further-notice blog-devcon-one-postponed-until-further-notice.html blog blog-security-alert-insecurely-configured-geth-can-make-funds-remotely-accessible blog-security-alert-insecurely-configured-geth-can-make-funds-remotely-accessible.html blog blog-on-anti-pre-revelation-games blog-on-anti-pre-revelation-games.html blog blog-olympic-rewards-announced blog-olympic-rewards-announced.html blog blog-security-alert-consensus-issue blog-security-alert-consensus-issue.html blog blog-frontier-first-100k-blocks blog-frontier-first-100k-blocks.html blog blog-chain-reorganisation-depth-expectations blog-chain-reorganisation-depth-expectations.html blog blog-on-public-and-private-blockchains blog-on-public-and-private-blockchains.html blog blog-security-alert-1-windowsalethzero-2 blog-security-alert-1-windowsalethzero-2.html blog blog-the-thawing-frontier blog-the-thawing-frontier.html blog blog-ethereum-protocol-update-1 blog-ethereum-protocol-update-1.html blog blog-introducing-casper-friendly-ghost blog-introducing-casper-friendly-ghost.html blog blog-announcing-new-foundation-board-executive-director blog-announcing-new-foundation-board-executive-director.html blog blog-a-few-last-minute-notes blog-a-few-last-minute-notes.html blog blog-ethereum-launches blog-ethereum-launches.html blog blog-final-steps blog-final-steps.html blog blog-frontier-is-coming-what-to-expect-and-how-to-prepare blog-frontier-is-coming-what-to-expect-and-how-to-prepare.html blog blog-know-ethereum-secure blog-know-ethereum-secure.html blog blog-on-abstraction blog-on-abstraction.html blog blog-state-tree-pruning blog-state-tree-pruning.html blog blog-ethereum-messaging-masses-including-fathers-via-infographic blog-ethereum-messaging-masses-including-fathers-via-infographic.html blog blog-another-ethereum-dev-update blog-another-ethereum-dev-update.html blog blog-the-problem-of-censorship blog-the-problem-of-censorship.html blog blog-the-business-imperative-behind-the-ethereum-vision blog-the-business-imperative-behind-the-ethereum-vision.html blog blog-announcing-e�-ethereum-on-raspberry-pi-programme blog-announcing-e�-ethereum-on-raspberry-pi-programme.html blog blog-olympic-frontier-pre-release blog-olympic-frontier-pre-release.html blog blog-the-end-of-the-beginning blog-the-end-of-the-beginning.html blog blog-visions-part-2-the-problem-of-trust blog-visions-part-2-the-problem-of-trust.html blog blog-visions-part-1-the-value-of-blockchain-technology blog-visions-part-1-the-value-of-blockchain-technology.html blog blog-ethereum-foundation-open-call-re-board-selection blog-ethereum-foundation-open-call-re-board-selection.html blog blog-ethereum-foundation-is-hiring-an-executive-director blog-ethereum-foundation-is-hiring-an-executive-director.html blog blog-devgrants-help blog-devgrants-help.html blog blog-ethereum-builders-supercharging-github blog-ethereum-builders-supercharging-github.html blog blog-blockchain-scalability-chain-fibers-redux blog-blockchain-scalability-chain-fibers-redux.html blog blog-bazaar-services blog-bazaar-services.html blog blog-implementing-vitaliks-vision blog-implementing-vitaliks-vision.html blog blog-ethereums-unexpected-future-direction blog-ethereums-unexpected-future-direction.html blog blog-ethereum-builders-experiment blog-ethereum-builders-experiment.html blog blog-juttas-update-bug-bounty-program-security-audit blog-juttas-update-bug-bounty-program-security-audit.html blog blog-ethereum-the-first-year blog-ethereum-the-first-year.html blog blog-getting-to-the-frontier blog-getting-to-the-frontier.html blog blog-ethereum-development-process blog-ethereum-development-process.html blog blog-ethereum-launch-process blog-ethereum-launch-process.html blog blog-gavs-ethereum-dev-update-v blog-gavs-ethereum-dev-update-v.html blog blog-subjectivity-exploitability-tradeoff blog-subjectivity-exploitability-tradeoff.html blog blog-p-epsilon-attack blog-p-epsilon-attack.html blog blog-superrationality-daos blog-superrationality-daos.html blog blog-light-clients-proof-stake blog-light-clients-proof-stake.html blog blog-ethereum-community-survey blog-ethereum-community-survey.html blog blog-jeffs-ethereum-dev-update-2 blog-jeffs-ethereum-dev-update-2.html keywords: advisory; alert; blockchains; blog blog; bootstrapping; bug; cause; clients; code; consensus; corporation; cryptocurrency; daos; dev; eips eips; ethereummagicians; ethereums; ethresear; foundation; frontier; gavs; guide; implementation; increase; issue; part-2; practice; pre; problem; project; proof; sale; scalability; security; sharing; stake; swarmresear; transaction; trust; update; update.html blog; vitalik vitalik cache: x-metadata.csv plain text: x-metadata.txt