diff --git a/blog/2019-05-28-first-blog-post.md b/blog/2019-05-28-first-blog-post.md deleted file mode 100644 index d3032efb..00000000 --- a/blog/2019-05-28-first-blog-post.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -slug: first-blog-post -title: First Blog Post -authors: [slorber, yangshun] -tags: [hola, docusaurus] ---- - -Lorem ipsum dolor sit amet... - - - -...consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet diff --git a/blog/2019-05-29-long-blog-post.md b/blog/2019-05-29-long-blog-post.md deleted file mode 100644 index eb4435de..00000000 --- a/blog/2019-05-29-long-blog-post.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -slug: long-blog-post -title: Long Blog Post -authors: yangshun -tags: [hello, docusaurus] ---- - -This is the summary of a very long blog post, - -Use a `` comment to limit blog post size in the list view. - - - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet diff --git a/blog/2019-08-01-mdx-blog-post.mdx b/blog/2019-08-01-mdx-blog-post.mdx deleted file mode 100644 index 0c4b4a48..00000000 --- a/blog/2019-08-01-mdx-blog-post.mdx +++ /dev/null @@ -1,24 +0,0 @@ ---- -slug: mdx-blog-post -title: MDX Blog Post -authors: [slorber] -tags: [docusaurus] ---- - -Blog posts support [Docusaurus Markdown features](https://docusaurus.io/docs/markdown-features), such as [MDX](https://mdxjs.com/). - -:::tip - -Use the power of React to create interactive blog posts. - -::: - -{/* truncate */} - -For example, use JSX to create an interactive button: - -```js - -``` - - diff --git a/blog/2020-08-10-the-league-of-entropy-launches-drand-v1-0-to-becom.md b/blog/2020-08-10-the-league-of-entropy-launches-drand-v1-0-to-becom.md index d51a6050..3fb1b46c 100644 --- a/blog/2020-08-10-the-league-of-entropy-launches-drand-v1-0-to-becom.md +++ b/blog/2020-08-10-the-league-of-entropy-launches-drand-v1-0-to-becom.md @@ -1,12 +1,15 @@ --- slug: "the-league-of-entropy-launches-drand" title: "The League of Entropy launches drand v1.0 to become the Internet’s first production-grade, publicly verifiable, randomness beacon!" -authors: [] +authors: [yolan] tags: [release, major, league-of-entropy] +date: 2020-08-10 --- Welcome to the brand-new website for the drand project! We are thrilled to announce that drand is now in production, offering publicly verifiable randomness as a foundational internet service. + + In this post, we'll introduce drand, highlight recent protocol upgrades, share details about the expansion of the League of Entropy's largest deployment, and provide a glimpse into the future of drand and the League of Entropy. ## New to drand? Here's a Primer diff --git a/blog/2020-08-10-the-league-of-entropy-launches-drand-v1-0.md b/blog/2020-08-10-the-league-of-entropy-launches-drand-v1-0.md index 33eb0e36..34428594 100644 --- a/blog/2020-08-10-the-league-of-entropy-launches-drand-v1-0.md +++ b/blog/2020-08-10-the-league-of-entropy-launches-drand-v1-0.md @@ -1,12 +1,15 @@ --- slug: "drand-v1.0-and-the-league-of-entropy-two-weeks-in" title: "drand v1.0 and the League of Entropy: Two Weeks In" -authors: [] +authors: [yolan] tags: [release, major, league-of-entropy] +date: 2020-08-24 --- Two weeks ago, we announced the launch of drand v1.0, the League of Entropy production-level service, and this very website. Here is a roundup of related blog posts and news items from around the web: + + - [The League of Entropy Launches Production Drand Network, Providing the First Publicly Verifiable Distributed Randomness Beacon](https://www.notion.so/League-of-Entropy-Launches-Production-drand-Network-dfc17d24f35d4558b6fd909276d573c1?pvs=21), League of Entropy press release, Aug 10 (picked up by [Yahoo! Finance](https://finance.yahoo.com/news/league-entropy-launches-production-drand-140000595.html) and others) - [The League of Entropy launches drand v1.0 to become the Internet’s first production-grade, publicly verifiable randomness beacon!](The%20League%20of%20Entropy%20launches%20drand%20v1%200%20to%20becom%202577496887ce4d88bf89358d0df69ac7.md), drand, Aug 10 - [How a Decentralized Randomness Beacon Could Boost Cryptographic Security](https://www.notion.so/How-a-Decentralized-Randomness-Beacon-Could-Boost-Cryptographic-Security-c880532146ff464eb953d388292b126e?pvs=21), CoinDesk, Aug 10 diff --git a/blog/2020-08-27-join-the-randomness-revolution-drand-is-hiring.mdx b/blog/2020-08-27-join-the-randomness-revolution-drand-is-hiring.mdx index db69ecd8..6603c899 100644 --- a/blog/2020-08-27-join-the-randomness-revolution-drand-is-hiring.mdx +++ b/blog/2020-08-27-join-the-randomness-revolution-drand-is-hiring.mdx @@ -1,12 +1,15 @@ --- slug: "join-th-randomness-revolution-drand-is-hiring" title: "Join the Randomness Revolution: Drand is hiring!" -authors: [] +authors: [yolan] tags: [league-of-entropy, news] +date: 2020-08-27 --- Are you passionate about randomness, dependable public services, and collaborative endeavors? Protocol Labs is on the lookout for talented individuals to join the drand team. If you thrive in innovative environments and want to shape the future of decentralized randomness, check out these exciting opportunities: +{/* truncate */} + - **Project Operator**: Drive the future growth and development of drand, working closely with the League of Entropy. This role is perfect for someone with a strategic mindset and a knack for fostering collaborative initiatives. - **Infrastructure Engineer**: Take charge of maintaining and deploying Protocol Labs' drand infrastructure. Provide support and guidance to other League of Entropy members, ensuring the robustness and reliability of our network. diff --git a/blog/2021-01-11-the-league-of-entropy-welcomes-quantum-resistant-ledger-qrl.mdx b/blog/2021-01-11-the-league-of-entropy-welcomes-quantum-resistant-ledger-qrl.mdx index 7653e0c6..90221d6b 100644 --- a/blog/2021-01-11-the-league-of-entropy-welcomes-quantum-resistant-ledger-qrl.mdx +++ b/blog/2021-01-11-the-league-of-entropy-welcomes-quantum-resistant-ledger-qrl.mdx @@ -1,12 +1,15 @@ --- slug: "the-league-of-entrophy-welcomes-quantum-resistant-ledger" title: "The League of Entrophy welcomes Quantum Resistant Ledger (QRL)" -authors: [] +authors: [yolan] tags: [league-of-entropy, new-members,news] +date: 2021-01-11 --- On Wednesday, December 16, 2020, The League of Entropy, running an [upgraded version of drand](https://github.com/drand/drand/releases/tag/v1.2.5), proudly welcomed The [Quantum Resistant Ledger](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Quantum%20Resistant%20Ledger%20b3e60c968098435790c3718f85ed3057.md) (QRL) to its list of esteemed members. QRL is an enterprise-grade blockchain platform that is secure from the quantum computing advances of tomorrow, as verified by external audits. The [QRL Foundation](https://qrl.foundation/), a not-for-profit organization, supports the research and development of open-source post-quantum blockchain solutions. +{/* truncate */} + The League of Entropy evaluates, votes on, and onboards new members quarterly. If you have experience running secure production services and are interested in operating a drand node, we’d love to hear from you. Contact us at [leagueofentropy@googlegroups.com](mailto:leagueofentropy@googlegroups.com). Join us and be a part of the randomness revolution! diff --git a/blog/2021-08-09-drand-celebrates-one-year-as-a-randomness-service.mdx b/blog/2021-08-09-drand-celebrates-one-year-as-a-randomness-service.mdx index bce76d30..14586ebe 100644 --- a/blog/2021-08-09-drand-celebrates-one-year-as-a-randomness-service.mdx +++ b/blog/2021-08-09-drand-celebrates-one-year-as-a-randomness-service.mdx @@ -1,12 +1,15 @@ --- slug: "drand-celebrates-one-year-as-a-randomness-service" title: "drand celebrates One Year as a Randomness Service!" -authors: [] +authors: [yolan] tags: [anniversary, jobs, updates] +date: 2021-08-09 --- drand, the distributed randomness beacon that aims to serve as a foundational randomness service for the Internet, surpassed 1M rounds on July 7, 2021! The drand mainnet was launched in July 2020 and received a significant update on August 10, 2020. This update included a number of key features, such as its 3-layer network architecture, client implementations in Go, and JavaScript, *round to timestamp* guarantees, deployment monitoring, and many other improvements. +{/* truncate */} + We have two reasons to celebrate today: - drand is celebrating its first anniversary since the launch of a significant upgrade to the mainnet on August 10, 2020, that enabled it to be used as a production-grade network! Drand has served as critical off-chain infrastructure for [Filecoin](https://filecoin.io/) (the world’s largest decentralized storage network) since its mainnet launch in Oct 2020 and several other projects in Web3 and beyond. @@ -23,7 +26,7 @@ There are also several reasons that *you* should be excited about the future o - Drand is hiring! The team is looking for top talent to join our efforts to establish drand as the default random value generator for the Internet. Open positions include Senior Software Engineer in Distributed Systems, and Infrastructure Engineer. [Take a look at our open roles](https://jobs.lever.co/protocol?team=Engineering). > *Filecoin is a decentralized storage network that relies on drand as an off-chain source of randomness, and has benefited greatly from having a reliable, performant, and trustworthy randomness service that itself is decentralized. Using drand has reduced the complexity involved in building, and operating large scale Layer 1 blockchain protocols such as Filecoin.* - Molly Mackinlay, Filecoin & IPFS Project Lead at Protocol Labs -> +> Stay tuned for more exciting updates! diff --git a/blog/2021-08-26-welcome/docusaurus-plushie-banner.jpeg b/blog/2021-08-26-welcome/docusaurus-plushie-banner.jpeg deleted file mode 100644 index 11bda092..00000000 Binary files a/blog/2021-08-26-welcome/docusaurus-plushie-banner.jpeg and /dev/null differ diff --git a/blog/2021-08-26-welcome/index.md b/blog/2021-08-26-welcome/index.md deleted file mode 100644 index 349ea075..00000000 --- a/blog/2021-08-26-welcome/index.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -slug: welcome -title: Welcome -authors: [slorber, yangshun] -tags: [facebook, hello, docusaurus] ---- - -[Docusaurus blogging features](https://docusaurus.io/docs/blog) are powered by the [blog plugin](https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog). - -Here are a few tips you might find useful. - - - -Simply add Markdown files (or folders) to the `blog` directory. - -Regular blog authors can be added to `authors.yml`. - -The blog post date can be extracted from filenames, such as: - -- `2019-05-30-welcome.md` -- `2019-05-30-welcome/index.md` - -A blog post folder can be convenient to co-locate blog post images: - -![Docusaurus Plushie](./docusaurus-plushie-banner.jpeg) - -The blog supports tags as well! - -**And if you don't want a blog**: just delete this directory, and use `blog: false` in your Docusaurus config. diff --git a/blog/2021-09-13-the-value-of-drand-part-1-of-2.md b/blog/2021-09-13-the-value-of-drand-part-1-of-2.md index 0cee2041..2e70f4aa 100644 --- a/blog/2021-09-13-the-value-of-drand-part-1-of-2.md +++ b/blog/2021-09-13-the-value-of-drand-part-1-of-2.md @@ -1,12 +1,15 @@ --- slug: "the-value-of-drand-part-1-of-2" title: "The Value of drand (Part 1 of 2)" -authors: [] +authors: [yolan] tags: [league-of-entropy] +date: 2021-09-13 --- *"We asked the League of Entropy members: “what’s the value of drand for you, and why do you support it?” Check out what they said!"* + + [The League of Entropy](https://www.notion.so/The-League-of-Entropy-1e76674b75e249699445799c5083fe78?pvs=21) (LoE) is a consortium of independent, and diverse organizations that partner together to operate a decentralized, bias-resistant, publicly verifiable, and reliable randomness beacon, called **drand**! The consortium was originally formed in 2019, and is currently supported by 16 member organizations that includes: [Cloudflare](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Cloudflare%2012bbcd90be5f4e42af18599f65019e7e.md), [EPFL Decentralized & Distributed Systems Lab (DeDiS)](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/EPFL%20Decentralized%20&%20Distributed%20Systems%20Lab%20(DeDi%20e855b8f643d4475aa89a47252e6623d9.md), [Universidad de Chile](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Universidad%20de%20Chile%2027708a6027104c3ba708e2d8d7508a66.md), [Kudelski Security](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Kudelski%20Security%20d800657770494c6cb39cffb5480407a4.md), [Protocol Labs](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Protocol%20Labs%209e18324379574803918146d996c24df5.md), [ChainSafe Systems](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/ChainSafe%20Systems%20480ac8864a33408dae64fad706c38a8e.md), [c**·**Labs](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/c%C2%B7Labs%208125559f2fb44804b9e6ca63da70f6b6.md), [EPFL Center for Digital Trust (C4DT)](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/EPFL%20Center%20for%20Digital%20Trust%20(C4DT)%20dc94bcdadab64950aa1e6bc96cb1e39a.md), [Emerald Onion](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Emerald%20Onion%20e22d8bdb07ef4198b283d0436bcc9cf4.md), [Ethereum Foundation](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Ethereum%20Foundation%20184fc01bc464488c9570eb543d6c386a.md), [PTisp](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/PTisp%20f8fa38c9c36d4b4bbbb40fe785e9ae12.md), [Tierion](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Tierion%205b38e1b289f44e9d87498eddb788d38f.md), [University College London](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/University%20College%20London%20af818bec61a542daa950596f01fddf09.md), and [Quantum Resistant Ledger](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Quantum%20Resistant%20Ledger%20b3e60c968098435790c3718f85ed3057.md). drand recently celebrated 1 year of undisrupted service, and completed 1M+ rounds of randomness (emitted at 30s intervals). You can read more about drand’s recent achievements in our recent [blog post](drand%20celebrates%20One%20Year%20as%20a%20Randomness%20Service!%20c66f0a909f034eae8f9bdc1b69d4014b.md). diff --git a/blog/2021-10-27-the-value-of-drand-part-2-of-2.md b/blog/2021-10-27-the-value-of-drand-part-2-of-2.md index a3f846de..0dbc46ce 100644 --- a/blog/2021-10-27-the-value-of-drand-part-2-of-2.md +++ b/blog/2021-10-27-the-value-of-drand-part-2-of-2.md @@ -1,11 +1,14 @@ --- slug: "the-value-of-drand-part-2-of-2" title: "The Value of drand (Part 2 of 2)" -authors: [] +authors: [yolan] tags: [league-of-entropy] +date: 2021-10-27 --- -*This blog post covers the second set of responses we received from League of Entropy members on our question: “What’s the value of drand for your organization and why do you support it”? We hope you enjoyed [**the first part**](The%20Value%20of%20drand%20(Part%201%20of%202)%200cc0bb5ecb6d471da62152370180701b.md) as much as we did.* +*This blog post covers the second set of responses we received from League of Entropy members on our question: “What’s the value of drand for your organization and why do you support it”? We hope you enjoyed [**the first part**](The%20Value%20of%20drand%20(Part%201%20of%202)%200cc0bb5ecb6d471da62152370180701b.md) as much as we did.* + + *As a reminder, [The League of Entropy](https://www.notion.so/The-League-of-Entropy-1e76674b75e249699445799c5083fe78?pvs=21) (LoE) is a consortium of independent, and diverse organizations that partner together to operate a publicly verifiable, decentralized, bias-resistant, and reliable randomness beacon, called **drand**! The consortium was originally formed in 2019, and is currently supported by 16 member organizations that include: [Cloudflare](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Cloudflare%2012bbcd90be5f4e42af18599f65019e7e.md), [EPFL Decentralized & Distributed Systems Lab (DeDiS)](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/EPFL%20Decentralized%20&%20Distributed%20Systems%20Lab%20(DeDi%20e855b8f643d4475aa89a47252e6623d9.md), [Universidad de Chile](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Universidad%20de%20Chile%2027708a6027104c3ba708e2d8d7508a66.md), [Kudelski Security](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Kudelski%20Security%20d800657770494c6cb39cffb5480407a4.md), [Protocol Labs](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Protocol%20Labs%209e18324379574803918146d996c24df5.md), [ChainSafe Systems](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/ChainSafe%20Systems%20480ac8864a33408dae64fad706c38a8e.md), [c**·**Labs](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/c%C2%B7Labs%208125559f2fb44804b9e6ca63da70f6b6.md), [EPFL Center for Digital Trust (C4DT)](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/EPFL%20Center%20for%20Digital%20Trust%20(C4DT)%20dc94bcdadab64950aa1e6bc96cb1e39a.md), [Emerald Onion](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Emerald%20Onion%20e22d8bdb07ef4198b283d0436bcc9cf4.md), [Ethereum Foundation](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Ethereum%20Foundation%20184fc01bc464488c9570eb543d6c386a.md), [PTisp](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/PTisp%20f8fa38c9c36d4b4bbbb40fe785e9ae12.md), [Tierion](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Tierion%205b38e1b289f44e9d87498eddb788d38f.md), [University College London](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/University%20College%20London%20af818bec61a542daa950596f01fddf09.md), and the [Quantum Resistant Ledger](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Quantum%20Resistant%20Ledger%20b3e60c968098435790c3718f85ed3057.md) Foundation.* diff --git a/blog/2022-02-20-multi-frequency-support-timelock-encryption.mdx b/blog/2022-02-20-multi-frequency-support-timelock-encryption.mdx index fbbd15ba..2b51f6d2 100644 --- a/blog/2022-02-20-multi-frequency-support-timelock-encryption.mdx +++ b/blog/2022-02-20-multi-frequency-support-timelock-encryption.mdx @@ -1,12 +1,15 @@ --- slug: "multi-frequency-support-&-timelock-encryption-are-coming-to-drand" title: "Multi-Frequency Support & Timelock Encryption are coming to drand!" -authors: [] +authors: [yolan] tags: [features] +date: 2022-02-20 --- The drand team has been hard at work the last couple of months to develop and integrate new and extremely valuable features into the drand codebase! We have worked together with [**Zondax**](https://zondax.ch/), a research and software development company, and we are extremely excited to announce the completion of a very important project for the future of drand. The project focused on two important features that have the potential to unlock new capabilities for the drand randomness service, enable new application scenarios and make drand able to support many more applications and platforms. +{/* truncate */} + In summary, the new features include: - **Unchained Randomness**: Each randomness beacon in drand has so far been linked to the previous one, forming a chain of beacons. With this update, each beacon is now independent of (all) the previous one(s). diff --git a/blog/2022-03-29-storswift-joins-the-league-of-entropy.md b/blog/2022-03-29-storswift-joins-the-league-of-entropy.md index 6d4dcaf6..3f3c3410 100644 --- a/blog/2022-03-29-storswift-joins-the-league-of-entropy.md +++ b/blog/2022-03-29-storswift-joins-the-league-of-entropy.md @@ -1,16 +1,16 @@ --- slug: "storswift-joins-the-league-of-entropy" title: "StorSwift joins the League of Entropy!" -authors: [] +authors: [yolan] tags: [league-of-entropy, new-members,news] +date: 2022-03-29 --- -Date Published: March 29, 2022 -Tags: League of Entropy, New Members, News - *"StorSwift becomes the newest member of the League of Entropy. We've asked them why they're motivated by drand and decided to contribute - check what they said!"* -![StorSwiftLogo.png](/img/StorSwiftLogo.png) + + +![StorSwiftLogo.png](https://images.spr.so/cdn-cgi/imagedelivery/j42No7y-dcokJuNgXeA0ig/5393c571-b63b-4062-bfa3-5778a04672cb/StorSwiftLogo/w=384,quality=90,fit=scale-down) We are excited to announce that [**StorSwift**](https://storswift.com/), a China-based cloud computing and storage services company, is joining forces with the [**League of Entropy**](https://leagueofentropy.com/) (LoE)! StorSwift is becoming the 15th member to join the LoE and the first partner joining from China - a significant milestone for the LoE! diff --git a/blog/2022-06-23-drand-at-northsec.mdx b/blog/2022-06-23-drand-at-northsec.mdx index ea16e1b9..b435132e 100644 --- a/blog/2022-06-23-drand-at-northsec.mdx +++ b/blog/2022-06-23-drand-at-northsec.mdx @@ -1,15 +1,18 @@ --- slug: "drand-at-northsec" title: "drand @ NorthSec" -authors: [] +authors: [yolan] tags: [conferences-and-events, news] +date: 2022-06-23 --- *Drand was recently presented at the North Sec conference! Here is a brief summary of the event and the drand talk, as well as the answers to a few of the interesting questions we received.* +{/* truncate */} + You can find the slides [**ready to be downloaded on IPFS](https://ipfs.io/ipfs/bafybeigenfo4az5j7abbjc3mbn7i4rl6qto7cca75kednwh73lopzq6foa/Public_verifiable_unbiasable_randomness_wassat-NSec2022-Yolan_Romailler.pdf):** -[CID: bafybeigenfo4az5j7abbjc3mbn7i4rl6qto7cca75kednwh73lopzq6foa] +[CID: bafybeigenfo4az5j7abbjc3mbn7i4rl6qto7cca75kednwh73lopzq6foa] A video of the talk is already [**available on Youtube**](https://youtu.be/I1iKtNGRv0s?t=17468). diff --git a/blog/2022-08-25-observing-randomness.mdx b/blog/2022-08-25-observing-randomness.mdx index a3563e30..ff50eed2 100644 --- a/blog/2022-08-25-observing-randomness.mdx +++ b/blog/2022-08-25-observing-randomness.mdx @@ -1,12 +1,15 @@ --- slug: "observing-randomness" title: "Observing Randomness" -authors: [] +authors: [yolan] tags: [features] +date: 2022-08-25 --- *Monitoring distributed systems is a challenge. While there are established patterns and solutions for monitoring the most common types of applications, there is usually no silver bullet. In this blog post, we outline the challenges that we faced when implementing monitoring for one such system, drand.* +{/* truncate */} + ### What is drand? **Drand** is a public, verifiable, unpredictable, and unbiased randomness beacon. It is based on the idea that to generate randomness in a reliable and trustworthy way, you cannot depend on a single entity to control the infrastructure where it runs. This led us to seek the collaboration of multiple organizations to run their own drand daemons, forming [The League of Entropy](https://www.notion.so/The-League-of-Entropy-1e76674b75e249699445799c5083fe78?pvs=21) (LoE)—a distributed organization where each participating partner runs a drand node. diff --git a/blog/2022-10-19-cryptosat-takes-drand-to-space.mdx b/blog/2022-10-19-cryptosat-takes-drand-to-space.mdx index 1d440a1d..82353244 100644 --- a/blog/2022-10-19-cryptosat-takes-drand-to-space.mdx +++ b/blog/2022-10-19-cryptosat-takes-drand-to-space.mdx @@ -1,8 +1,9 @@ --- slug: "cryptosat-takes-drand-to-space" title: "CryptoSat takes drand to Space!" -authors: [] +authors: [yolan] tags: [news] +date: 2022-10-19 --- ![https://drand.love/assets/img/cryptosat-blog-header3.84006631.png](/img/cryptosat-blog-header3.84006631.png) @@ -11,6 +12,8 @@ tags: [news] **drand is the next generation distributed randomness service.** It requires several independent organizations to run a node that contributes a part of the randomness to the network. So far, all of the nodes that participate in the [**League of Entropy’s**](https://blog.cloudflare.com/league-of-entropy/) drand network have been placed on Earth. But this has just changed! Temporarily for now, but hopefully more permanently in the near future. Read on to find out all the details. +{/* truncate */} + ### What is CryptoSat? [CryptoSat](http://cryptosat.io/) builds and launches satellites that power blockchain and cryptographic protocols. Satellites are physically inaccessible and can serve as the most secure root-of-trust that guarantees the confidentiality and integrity of sensitive computations and data. Such tamper-proof satellites can serve numerous use-cases including transaction signing, trusted setups for cryptographic schemes, a randomness oracle, a time-oracle (VDF), and more. diff --git a/blog/2023-01-22-drand-2022-year-in-review-our-2023-roadmap.mdx b/blog/2023-01-22-drand-2022-year-in-review-our-2023-roadmap.mdx index 5100c9d0..137fb165 100644 --- a/blog/2023-01-22-drand-2022-year-in-review-our-2023-roadmap.mdx +++ b/blog/2023-01-22-drand-2022-year-in-review-our-2023-roadmap.mdx @@ -1,12 +1,15 @@ --- slug: "drand-2022-year-in-review-&-our-2023-roadmap" title: "drand: 2022 Year in Review & our 2023 Roadmap" -authors: [] +authors: [yolan] tags: [news] +date: 2023-01-22 --- ## drand: 2022 Year in Review +{/* truncate */} + ### 🥳 Reflections on a Year of Achievements As 2022 wrapped up, the drand team took a moment to reflect on the incredible journey we’ve been on. The year was packed with milestones, innovations, and expansions that have set the stage for an exciting future. Here’s a look back at some of the standout moments from our year. @@ -36,7 +39,7 @@ Monitoring and maintaining a robust network is crucial. This year, we made signi - **Integrated Metrics:** We embedded metrics directly into our codebase, providing a clearer view of the network’s health. - **New Dashboard:** We built a comprehensive dashboard that gives us a holistic view of nodes before, during, and after resharing ceremonies. This tool has been instrumental in enabling async ceremonies, making the process more flexible for node operators. -*Curious about the technical details? Read more in [Observing Randomness](Observing%20Randomness%2080ade6b218314dde955b5692473d8c1c.md)* +*Curious about the technical details? Read more in [Observing Randomness](Observing%20Randomness%2080ade6b218314dde955b5692473d8c1c.md)* --- @@ -46,7 +49,7 @@ One of the most exciting developments of 2022 was our collaboration with CryptoS We’re not stopping there. Our goal is to have a permanent drand node operating from space, further enhancing the resilience of our network. -*Read all about this groundbreaking achievement in [CryptoSat takes drand to Space!](CryptoSat%20takes%20drand%20to%20Space!%200d0538c9c0df418a9aacf42859eb079f.md)* +*Read all about this groundbreaking achievement in [CryptoSat takes drand to Space!](CryptoSat%20takes%20drand%20to%20Space!%200d0538c9c0df418a9aacf42859eb079f.md)* --- @@ -57,7 +60,7 @@ We’re not stopping there. Our goal is to have a permanent drand node operating - **New Members:** We welcomed four new members to the League and have several more lined up for consideration in the coming months. - **Community Engagement:** We presented drand at several high-profile events, including NorthSec, MCH, and DEFCON. These presentations sparked new collaborations and expanded our community. -Interested in joining the League of Entropy? Learn more at [The League of Entropy](https://www.notion.so/The-League-of-Entropy-1e76674b75e249699445799c5083fe78?pvs=21) +Interested in joining the League of Entropy? Learn more at [The League of Entropy](https://www.notion.so/The-League-of-Entropy-1e76674b75e249699445799c5083fe78?pvs=21) --- diff --git a/blog/2023-01-26-ipfs-force-joins-the-league-of-entropy.mdx b/blog/2023-01-26-ipfs-force-joins-the-league-of-entropy.mdx index 1f445712..c1eac81f 100644 --- a/blog/2023-01-26-ipfs-force-joins-the-league-of-entropy.mdx +++ b/blog/2023-01-26-ipfs-force-joins-the-league-of-entropy.mdx @@ -1,14 +1,17 @@ --- slug: "ipfs-force-joins-the-league-of-entropy" title: "IPFS Force joins the League of Entropy!" -authors: [] +authors: [yolan] tags: [league-of-entropy, new-members, news] +date: 2023-01-26 --- ![https://drand.love/assets/img/ipfs-force-logo.18be5e96.png](/img/ipfs-force-logo.18be5e96.png) We are excited to announce that IPFSForce has joined the League of Entropy! +{/* truncate */} + IPFSForce has focused on technology research and development in blockchain since 2017. With the vision of being Web 3.0’s infrastructure service provider, IPFSForce is working to make storage more efficient, cost-effective, open, and safer. With "Co-built Value, Sharing Honour" as a guiding principle, IPFSForce leverages technologies to empower global communities with high-quality services. We've asked IPFSForce some key questions that we've previously asked other LoE members - see [**here**](The%20Value%20of%20drand%20(Part%201%20of%202)%200cc0bb5ecb6d471da62152370180701b.md) and [**here**](The%20Value%20of%20drand%20(Part%202%20of%202)%206d53b4cc6b5f4f31a8cab0b3fe2e94c3.md) - on the value of drand. Check out what they said. diff --git a/blog/2023-02-21-a-guide-on-how-to-use-drand.mdx b/blog/2023-02-21-a-guide-on-how-to-use-drand.mdx index f9c3f9e8..50b71ac1 100644 --- a/blog/2023-02-21-a-guide-on-how-to-use-drand.mdx +++ b/blog/2023-02-21-a-guide-on-how-to-use-drand.mdx @@ -1,14 +1,17 @@ --- slug: "a-guide-on-how-to-use-drand" title: "A Guide on how to use drand" -authors: [] +authors: [yolan] tags: [features, how-to] +date: 2023-02-21 --- # Using Public Randomness from drand In this blog post, we’ll dive into the fascinating world of public randomness and provide a step-by-step tutorial on how to consume randomness from drand and use it in your applications. Get ready for an exciting journey into the heart of randomness! +{/* truncate */} + --- ### Why Public Randomness? diff --git a/blog/2023-03-14-automata-network-joins-the-league-of-entropy.mdx b/blog/2023-03-14-automata-network-joins-the-league-of-entropy.mdx index 1d04b617..7525acfc 100644 --- a/blog/2023-03-14-automata-network-joins-the-league-of-entropy.mdx +++ b/blog/2023-03-14-automata-network-joins-the-league-of-entropy.mdx @@ -1,12 +1,15 @@ --- slug: "auttomata-network-joins-the-league-of-entropy" title: "Automata Network Joins the League of Entropy!" -authors: [] +authors: [yolan] tags: [league-of-entropy, new-members] +date: 2023-03-14 --- We are proud to announce that [Automata Network](https://www.ata.network/), a web3 middleware protocol focused on protecting fairness & privacy, is joining forces with the League of Entropy (LoE)! Automata is becoming the 17th member to join the LoE and the first partner joining from Singapore - a significant milestone for the LoE. +{/* truncate */} + We’ve asked Automata some key questions that we’ve regularly ask of new LoE members - see [**here**](The%20Value%20of%20drand%20(Part%201%20of%202)%200cc0bb5ecb6d471da62152370180701b.md), [**here**](The%20Value%20of%20drand%20(Part%202%20of%202)%206d53b4cc6b5f4f31a8cab0b3fe2e94c3.md) and [**here**](StorSwift%20joins%20the%20League%20of%20Entropy!%204cfa4cda241e4769a98f410428e93ebf.md) - on the value of drand. Here are the team's answers. --- diff --git a/blog/2023-03-15-drand-on-filecoin-virtual-machine-fvm-draffle.mdx b/blog/2023-03-15-drand-on-filecoin-virtual-machine-fvm-draffle.mdx index 9327deff..24a24912 100644 --- a/blog/2023-03-15-drand-on-filecoin-virtual-machine-fvm-draffle.mdx +++ b/blog/2023-03-15-drand-on-filecoin-virtual-machine-fvm-draffle.mdx @@ -1,12 +1,15 @@ --- slug: "drand-on-filecoin-virtual-machine-FVM-draffle" title: "drand on Filecoin Virtual Machine (FVM) - draffle" -authors: [] +authors: [yolan] tags: [FVM, features, how-to] +date: 2023-03-15 --- To mark the launch of user-programmable smart contracts on the Filecoin Virtual Machine (FVM), the drand team is excited to release a three-part blog series on using randomness on the FVM! In this first part, we dive into the prevrandao EVM opcode (the FVM fully supports EVM bytecode!), a sample Solidity contract using it, a UI to interact with it, and some other necessary plumbing to make it all work. +{/* truncate */} + If you want to skip all the wonderful learning, you can jump straight into the demo project we developed [**on GitHub**](https://github.com/drand/draffle) - the contract is deployed at address `0x9D38f3BB80D98cE09C3f0936Bea140181d4CCABA` on the Hyperspace testnet! A little familiarity with [**Solidity**](https://soliditylang.org/) will be helpful to follow along, but anyone familiar with a C-style language should be able to get the gist. ## 🎲 **Randomness on the Blockchain** ⛓️ diff --git a/blog/2023-03-27-timelock-encryption-is-now-supported-on-drand-mainnet.mdx b/blog/2023-03-27-timelock-encryption-is-now-supported-on-drand-mainnet.mdx index 963e744e..af74dc6e 100644 --- a/blog/2023-03-27-timelock-encryption-is-now-supported-on-drand-mainnet.mdx +++ b/blog/2023-03-27-timelock-encryption-is-now-supported-on-drand-mainnet.mdx @@ -3,13 +3,13 @@ slug: "timelock-encryption-is-now-supported-on-drand-mainnet" title: "Timelock Encryption is now supported on drand mainnet" authors: [] tags: [conferences-and-events, features, news] +date: 2023-03-27 --- -Date Published: March 27, 2023 -Tags: Conferences and Events, Features, News - The drand team has been busy during the past year working on delivering an exciting new feature: **Timelock Encryption**. Timelock encryption enables you to encrypt a message that cannot be decrypted by anyone until a specified time in the future. +{/* truncate */} + You might have heard about it from us already, since we were proud to present not just one, but *three* new open-source projects in August 2022, bringing a new very exciting feature called “timelock encryption” to our drand testnet! Well, wait no more: we have now finally reached “General Availability” and our *audited* Timelock Encryption scheme is **now compatible with the drand mainnet**, thanks to our newly launched `fastnet` network which we’ll discuss quickly in this post as well. @@ -87,7 +87,7 @@ In practice, we decided the easiest way to implement this was to rely on the exi We tried to stay pretty close to the age-plugin format in order to possibly adapt this new scheme into a plugin, perhaps sometime in the future. Here is our custom tlock stanza: ```jsx --> tlock {roundnumber} {chainhash} +-> tlock {roundnumber} {chainhash} {timelocked-fileKey-for-given-roundnumber-and-chainhash} ``` @@ -123,14 +123,14 @@ The best part about our timelock solution is that it is live on our mainnet! You This is possible because the League of Entropy actually launched a new drand mainnet network, on March 1st, 2023: the `fastnet` 🏎️ network! It is readily available through our mainnet endpoints: [**https://api.drand.sh/dbd506d6ef76e5f386f41c651dcb808c5bcbd75471cc4eafa3f4df7ad4e4c493/info**](https://api.drand.sh/dbd506d6ef76e5f386f41c651dcb808c5bcbd75471cc4eafa3f4df7ad4e4c493/info) ```jsx -{ -"public_key":"a0b862a7527fee3a731bcb59280ab6abd62d5c0b6ea03dc4ddf6612fdfc9d01f01c31542541771903475eb1ec6615f8d0df0b8b6dce385811d6dcf8cbefb8759e5e616a3dfd054c928940766d9a5b9db91e3b697e5d70a975181e007f87fca5e", -"period":3, -"genesis_time":1677685200, -"hash":"dbd506d6ef76e5f386f41c651dcb808c5bcbd75471cc4eafa3f4df7ad4e4c493", -"groupHash":"a81e9d63f614ccdb144b8ff79fbd4d5a2d22055c0bfe4ee9a8092003dab1c6c0", -"schemeID":"bls-unchained-on-g1", -"metadata":{"beaconID":"fastnet"} +{ +"public_key":"a0b862a7527fee3a731bcb59280ab6abd62d5c0b6ea03dc4ddf6612fdfc9d01f01c31542541771903475eb1ec6615f8d0df0b8b6dce385811d6dcf8cbefb8759e5e616a3dfd054c928940766d9a5b9db91e3b697e5d70a975181e007f87fca5e", +"period":3, +"genesis_time":1677685200, +"hash":"dbd506d6ef76e5f386f41c651dcb808c5bcbd75471cc4eafa3f4df7ad4e4c493", +"groupHash":"a81e9d63f614ccdb144b8ff79fbd4d5a2d22055c0bfe4ee9a8092003dab1c6c0", +"schemeID":"bls-unchained-on-g1", +"metadata":{"beaconID":"fastnet"} } ``` diff --git a/blog/2023-04-26-randomness-summit-tokyo-2023.mdx b/blog/2023-04-26-randomness-summit-tokyo-2023.mdx index 83c54100..789fe8b9 100644 --- a/blog/2023-04-26-randomness-summit-tokyo-2023.mdx +++ b/blog/2023-04-26-randomness-summit-tokyo-2023.mdx @@ -1,15 +1,15 @@ --- slug: "randomness-summit-tokyo-2023" title: "Randomness Summit Tokyo 2023" -authors: [] +authors: [yolan] tags: [conferences-and-events, news] +date: 2023-04-26 --- -Date Published: April 26, 2023 -Tags: Conferences and Events, News - On the 30th of March, the drand team hosted the second edition of the Randomness Summit alongside [**Real World Crypto**](https://rwc.iacr.org/) in Tokyo, the first having been [**online only in 2020**](https://randomness2020.com/) during the COVID pandemic. +{/* truncate */} + ### Overview The Randomness Summit was a one day conference consisting of talks from a range of speakers on topics such as verifiable randomness functions, verifiable delay functions, distributed key generation, cryptographic specifications, and more! diff --git a/blog/2023-05-25-security-assessment-of-tlock.mdx b/blog/2023-05-25-security-assessment-of-tlock.mdx index 3f20473a..751ce98d 100644 --- a/blog/2023-05-25-security-assessment-of-tlock.mdx +++ b/blog/2023-05-25-security-assessment-of-tlock.mdx @@ -1,15 +1,15 @@ --- slug: "security-assessment-of-tlock" title: "Security Assessment of tlock" -authors: [] +authors: [yolan] tags: [news, updates] +date: 2023-05-25 --- -Date Published: May 25, 2023 -Tags: News, Updates - We are happy to announce that our timed release encryption scheme "[**tlock**](https://eprint.iacr.org/2023/189)" and its implementations, which we introduced in our [**previous blog post**](Timelock%20Encryption%20is%20now%20supported%20on%20drand%20main%20327425b1e16d4c22aa0d785dbf1c5fbb.md), have recently undergone a comprehensive security assessment by [Kudelski Security](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Kudelski%20Security%20d800657770494c6cb39cffb5480407a4.md). This was a crucial step in ensuring the robustness and reliability of our encryption system in order to guarantee that timelocked content remains encrypted until the time has come for it to be decrypted and never before. +{/* truncate */} + ## **Overview** [Kudelski Security](../The%20League%20of%20Entropy%201e76674b75e249699445799c5083fe78/League%20Partners%2089fecb56737044e5bdfbbb3f6864a422/Kudelski%20Security%20d800657770494c6cb39cffb5480407a4.md), a renowned provider of cybersecurity solutions, was engaged to review the implementation of drand’s timelock encryption scheme and timelock responsible disclosure demo. The work covered: diff --git a/blog/2023-06-01-drand-explainer-for-beginners.mdx b/blog/2023-06-01-drand-explainer-for-beginners.mdx index d1c8371c..d0bf188e 100644 --- a/blog/2023-06-01-drand-explainer-for-beginners.mdx +++ b/blog/2023-06-01-drand-explainer-for-beginners.mdx @@ -1,17 +1,17 @@ --- slug: "drand-explainer-for-begginers" title: "drand Explainer for Beginners" -authors: [] +authors: [yolan] tags: [beginner, features, how-to] +date: 2023-06-01 --- -Date Published: June 1, 2023 -Tags: Beginner, Features, How-to - **drand is software for running a threshold network that generates publicly verifiable random numbers.** Boy, that's a mouthful. +{/* truncate */} + To the uninitiated, a bunch of questions spring to mind: What on earth is a threshold network? How can random numbers be verified?! Surely they're random? Why would I want my random numbers to be public? Well, this blog post is the right place to uncover all the mysteries of the above statement. Let's work backwards to build up a picture of what drand is and how it works. diff --git a/blog/2023-06-05-announcing-the-drand-code-walkthroughs.md b/blog/2023-06-05-announcing-the-drand-code-walkthroughs.md index 1639510a..d9d77612 100644 --- a/blog/2023-06-05-announcing-the-drand-code-walkthroughs.md +++ b/blog/2023-06-05-announcing-the-drand-code-walkthroughs.md @@ -1,23 +1,27 @@ --- -slug: "announcing-the-drand-code-walkthrough" +slug: "announcing-drand-code-walkthrough" title: "Announcing the drand Code Walkthroughs" -authors: [] +authors: [yolan] tags: [news, how-to, code-walkthrough] +date: 2023-06-05 --- -![https://drand.love/assets/img/drand-code-walkthroughs.5726ed76.png](/img/drand-code-walkthroughs.5726ed76.png) +test +![code-walkthroughs](https://images.spr.so/cdn-cgi/imagedelivery/j42No7y-dcokJuNgXeA0ig/843ad7ff-c63c-4c1d-86fe-8cb595395f15/drand-code-walkthroughs.5726ed76/w=1080,quality=90,fit=scale-down) ## **What, Where, & When** -The drand community and developer base is expanding rapidly. drand usage is gaining momentum with many applications using it to draw randomness for their systems. While our [**slack workspace](https://join.slack.com/t/drandworkspace/shared_invite/zt-19u4rf6if-bf7lxIvF2zYn4~TrBwfkiA)** is a great place to interact with other developers and the drand core maintainers, code walkthroughs are even better if one wants to gain a holistic view of the system, become familiar with nitty gritty details, and ask questions in real time. +The drand community and developer base is expanding rapidly. drand usage is gaining momentum with many applications using it to draw randomness for their systems. While our [**slack workspace](https://join.slack.com/t/drandworkspace/shared_invite/zt-19u4rf6if-bf7lxIvF2zYn4~TrBwfkiA)** is a great place to interact with other developers and the drand core maintainers, code walkthroughs are even better if one wants to gain a holistic view of the system, become familiar with nitty gritty details, and ask questions in real time. -With those benefits in mind, we have designed and will be running a series of virtual code walkthroughs on the drand codebase. The series consists of eight (8) sessions, taking place **every other Tuesday at 1430 UTC, starting on the 20th of June**. Each session is scheduled to last approximately 45mins with 30mins for Q&A and pair programming assistance. + + +With those benefits in mind, we have designed and will be running a series of virtual code walkthroughs on the drand codebase. The series consists of eight (8) sessions, taking place **every other Tuesday at 1430 UTC, starting on the 20th of June**. Each session is scheduled to last approximately 45mins with 30mins for Q&A and pair programming assistance. ## **Registration** Registrations are handled through Lu.ma. Any modifications or updates to the schedule or topics will be reflected on the Lu.ma event page, so the best way to be kept up-to-date is to register for the event series. -Lu.ma registration page: [**https://lu.ma/drand-code-walkthroughs**](https://lu.ma/drand-code-walkthroughs) +Lu.ma registration page: [**https://lu.ma/drand-code-walkthroughs**](https://lu.ma/drand-code-walkthroughs) ## **Sessions in a Nutshell** @@ -25,48 +29,48 @@ The topics and brief descriptions of the code walkthrough sessions are listed be ### **Session 1: “What is drand?: How to use its CLI and Clients”** -- **Dates:** Tuesday, **20th June 2023**, 1430 UTC -- **Description:** We will explain what the drand binary is, what it does and run through all of the CLI commands and related parameters to explain how to start a node as an operator and how to sync and follow other nodes. We will also run a Distributed Key Generation (DKG), perhaps the most central part of setting up a drand network. In this session we will not go through the DKG code, which is subject to another session. Finally we will do a walkthrough of the drand client libraries. There are currently two drand libraries (in Go and in JS), which we will use to consume drand randomness. +- **Dates:** Tuesday, **20th June 2023**, 1430 UTC +- **Description:** We will explain what the drand binary is, what it does and run through all of the CLI commands and related parameters to explain how to start a node as an operator and how to sync and follow other nodes. We will also run a Distributed Key Generation (DKG), perhaps the most central part of setting up a drand network. In this session we will not go through the DKG code, which is subject to another session. Finally we will do a walkthrough of the drand client libraries. There are currently two drand libraries (in Go and in JS), which we will use to consume drand randomness. ### **Session 2: “What is a drand beacon? How is it created?”** -- **Dates:** Tuesday, **4th July 2023**, 1430 UTC -- **Description:** This session will focus on the randomness beacons produced by the drand network. We will explain the different representations of a beacon, as well as the beacon model followed by the drand mainnet. We will also dive into the details of why drand randomness is “verifiable” and how to derive randomness from the signature. drand is based on “threshold cryptography”, which, in practice, means that every node is producing a “partial” of the final signature. In this session, we will explain how partials are aggregated to produce the final randomness beacon. +- **Dates:** Tuesday, **4th July 2023**, 1430 UTC +- **Description:** This session will focus on the randomness beacons produced by the drand network. We will explain the different representations of a beacon, as well as the beacon model followed by the drand mainnet. We will also dive into the details of why drand randomness is “verifiable” and how to derive randomness from the signature. drand is based on “threshold cryptography”, which, in practice, means that every node is producing a “partial” of the final signature. In this session, we will explain how partials are aggregated to produce the final randomness beacon. ### **Session 3: “drand Cryptographic Primitives”** -- **Dates:** Tuesday, **18th July 2023**, 1430 UTC -- **Description:** Cryptography is at the heart of drand. In this session, we will dive into the cryptographic primitives on which drand is based on. We will explain and showcase keypairs and distributed keys, the vault and the Kyber library. +- **Dates:** Tuesday, **18th July 2023**, 1430 UTC +- **Description:** Cryptography is at the heart of drand. In this session, we will dive into the cryptographic primitives on which drand is based on. We will explain and showcase keypairs and distributed keys, the vault and the Kyber library. ### **Session 4: “drand’s Distributed Key Generation (DKG)”** -- **Dates:** Tuesday, **1st August 2023**, 1430 UTC -- **Description:** Distributed Key Generation is the most central part of the drand network and threshold cryptography more in general. In this session, we will dive into the details of basic concepts, such as the Shamir secret sharing, Pedersen DKG, the “group file” and their implementation. We will also go through the lifecycle of a DKG event, relevant security considerations and the difference between “initial sharing” vs “resharing”. +- **Dates:** Tuesday, **1st August 2023**, 1430 UTC +- **Description:** Distributed Key Generation is the most central part of the drand network and threshold cryptography more in general. In this session, we will dive into the details of basic concepts, such as the Shamir secret sharing, Pedersen DKG, the “group file” and their implementation. We will also go through the lifecycle of a DKG event, relevant security considerations and the difference between “initial sharing” vs “resharing”. ### **Session 5: “The different layers of the drand system: from the daemon and the beacon process to storage/sync manager and the client”** -- **Dates:** Tuesday, **15th August 2023**, 1430 UTC -- **Description:** At a high level, drand comes as one coherent system. However, it is composed of several subcomponents that are distinct and play a particular role in the operation of the overall system. In this session, we’re going to put puzzle pieces from previous sessions together, define the taxonomy of the components, specify where does one stop and the other start and how they communicate and interoperate with one another. +- **Dates:** Tuesday, **15th August 2023**, 1430 UTC +- **Description:** At a high level, drand comes as one coherent system. However, it is composed of several subcomponents that are distinct and play a particular role in the operation of the overall system. In this session, we’re going to put puzzle pieces from previous sessions together, define the taxonomy of the components, specify where does one stop and the other start and how they communicate and interoperate with one another. ### **Session 6: “drand’s Networking Stack & Monitoring Infra”** -- **Dates:** Tuesday, **29th August 2023**, 1430 UTC -- **Description:** As a distributed, Internet-based system, drand has a number of networking components to distribute randomness beacons across the drand network nodes and make beacons available to its users. In this session we will go through the network-layer protocols used by drand and will also cover the monitoring tools, metrics and infrastructure that we have in place in order to guarantee smooth operation and identify concerning situations before they become serious incidents. +- **Dates:** Tuesday, **29th August 2023**, 1430 UTC +- **Description:** As a distributed, Internet-based system, drand has a number of networking components to distribute randomness beacons across the drand network nodes and make beacons available to its users. In this session we will go through the network-layer protocols used by drand and will also cover the monitoring tools, metrics and infrastructure that we have in place in order to guarantee smooth operation and identify concerning situations before they become serious incidents. ### **Session 7: “drand’s Storage & Sync Functionality”** -- **Dates:** Tuesday, **12th September 2023**, 1430 UTC -- **Description:** drand beacons are not only valuable at the time they’re produced, but also well after their generation for applications that want to use or verify past beacons. As such, storage of beacons is an important functionality that all nodes in the network should support. In this session, we’ll go through the different types of storage backends. We will also cover the “sync” functionality, i.e., the case when a new node (re-)joins the network and needs to sync the history of beacons. +- **Dates:** Tuesday, **12th September 2023**, 1430 UTC +- **Description:** drand beacons are not only valuable at the time they’re produced, but also well after their generation for applications that want to use or verify past beacons. As such, storage of beacons is an important functionality that all nodes in the network should support. In this session, we’ll go through the different types of storage backends. We will also cover the “sync” functionality, i.e., the case when a new node (re-)joins the network and needs to sync the history of beacons. ### **Session 8: “Client Libraries Deep Dive”** -- **Dates:** Tuesday, **26th September 2023**, 1430 UTC -- **Description:** In this final session, we will walk through the code of the client libraries in detail. We will also go through examples of using these libraries in practical use-cases to showcase their workflows. In addition, we will dive into the timelock encryption libraries and their code. +- **Dates:** Tuesday, **26th September 2023**, 1430 UTC +- **Description:** In this final session, we will walk through the code of the client libraries in detail. We will also go through examples of using these libraries in practical use-cases to showcase their workflows. In addition, we will dive into the timelock encryption libraries and their code. ## **Looking forward** -We’re looking forward to an enlightening series of sessions. Please share your thoughts and feedback by joining the drand slack workspace [**invitation link**](https://join.slack.com/t/drandworkspace/shared_invite/zt-19u4rf6if-bf7lxIvF2zYn4~TrBwfkiA)] and posting questions in the `#code-walkthroughs` channel. Requests for extra topics are more than welcome. The League of Entropy can also be reached through email at: `leagueofentropy [ at ] googlegroups.com`. +We’re looking forward to an enlightening series of sessions. Please share your thoughts and feedback by joining the drand slack workspace [**invitation link**](https://join.slack.com/t/drandworkspace/shared_invite/zt-19u4rf6if-bf7lxIvF2zYn4~TrBwfkiA)] and posting questions in the `#code-walkthroughs` channel. Requests for extra topics are more than welcome. The League of Entropy can also be reached through email at: `leagueofentropy [ at ] googlegroups.com`. -Finally, don't forget to **register for free** to our code walkthroughs on our [**registration page**](https://lu.ma/drand-code-walkthroughs), see you there! +Finally, don't forget to **register for free** to our code walkthroughs on our [**registration page**](https://lu.ma/drand-code-walkthroughs), see you there! --- diff --git a/blog/2023-07-02-fastnet-to-be-sunset-long-live-quicknet.md b/blog/2023-07-02-fastnet-to-be-sunset-long-live-quicknet.md index 3d197bbe..e483d422 100644 --- a/blog/2023-07-02-fastnet-to-be-sunset-long-live-quicknet.md +++ b/blog/2023-07-02-fastnet-to-be-sunset-long-live-quicknet.md @@ -1,13 +1,16 @@ --- slug: "fastnet-to-be-sunset" title: "fastnet to be sunset, long live quicknet" -authors: [] +authors: [yolan] tags: [news] +date: 2023-07-02 --- -Last month, we have identified [**a minor issue](https://github.com/drand/kyber-bls12381/issues/22)** in our implementation of the BLS signature on G1 used in the newly launched `fastnet` network. This is an RFC compliance issue which led us to plan the launch of a new compliant `quicknet` network and to spin down `fastnet`. +Last month, we have identified [**a minor issue](https://github.com/drand/kyber-bls12381/issues/22)** in our implementation of the BLS signature on G1 used in the newly launched `fastnet` network. This is an RFC compliance issue which led us to plan the launch of a new compliant `quicknet` network and to spin down `fastnet`. -## **The Issue** + + +## The Issue While not a *security issue* for drand, the problem is affecting our “hash to curve” function, used to map round numbers to a point on the elliptic curve that get signed using [**threshold BLS](https://en.wikipedia.org/wiki/BLS_digital_signature)** by the drand network. The issue relates to the upcoming Hash To Curve [**RFC 9380**](https://www.rfc-editor.org/auth48/rfc9380), which mandates specific “Domain Separation Tags“ (DST) for certain curves. In the BLS curve case, where we have two different groups (G1 and G2) that we can map to, the RFC recommends using different DST for both groups (it’s the point of having a DST!). Sadly, our implementation of BLS signatures was initially written to perform signatures on G2 and not on G1… (Stay tuned for an upcoming blog post about the choice of the group for BLS signatures!) The usage of a global variable in our codebase for the DST meant that both our G1 and G2 implementations were sharing the same DST. Since we don’t have “official test vectors” for BLS signatures on G1 and G2, this went unnoticed until [**someone tried](https://drandworkspace.slack.com/archives/C011JB8NU2E/p1683527867397549?thread_ts=1683197659.071499&cid=C011JB8NU2E)** to verify our signatures done on G1 with a C++ implementation and reported the issue in our Slack. @@ -19,7 +22,7 @@ For us, the main takeaways here are: - Generate more noise and community outreach around new network launches, including new testnets. - Expect early adopters to take at least 2-3 months to start testing their implementations building on top of your new features, and therefore plan your testnet and mainnet launches accordingly. -## **Next Steps** +## Next Steps This issue means that **all beacons** emitted for the new `fastnet` network that we launched on March 1st are featuring signatures that are non-compliant with the hash to curve spec, and so is the case for beacons from our testnet. @@ -40,13 +43,13 @@ Given the above, [The League of Entropy](https://www.notion.so/The-League-of-Ent We are currently planning to launch these new `quicknet` networks in July on both our Testnet and Mainnet. -## **Consequences** +## Consequences The biggest problem with shutting down our `fastnet` network, is that any usage of its public key to perform timelock encryption past the shutdown date will lead to ciphertexts that cannot be decrypted. This is because the required beacon’s signature won’t be emitted by the network. This means that whoever used our timelock system with our `fastnet` network (or our `testnet-g` one) and set a decryption date after their shutdown date won’t be able to decrypt their ciphertexts. For “classical” public randomness usage, switching to a new network does not affect the quality or verifiability of the randomness. -## **Recommendations** +## Recommendations For “public verifiable randomness usage”, we recommend always having a way to transition to a new “beacon chain” easily shall the need arise. This means being able to switch to a new public key and starting to monitor a new chainhash at a given time. diff --git a/blog/2023-10-03-Announcing-Randamu.md b/blog/2023-10-03-Announcing-Randamu.md index c0fd7576..25b70c4f 100644 --- a/blog/2023-10-03-Announcing-Randamu.md +++ b/blog/2023-10-03-Announcing-Randamu.md @@ -1,7 +1,8 @@ --- slug: "announcing-randamu" title: "Announcing Randamu!" -authors: [] +description: "Randamu is a spin off of the drand project with the original team members from Protocol Labs." +authors: [yolan, patrick, laith, erick] tags: [news, update, league-of-entropy] --- @@ -9,6 +10,8 @@ Dear Friends & Colleagues, TOPLINE: After four years of stewarding the [drand](https://github.com/drand) project on behalf of [LoE](https://leagueofentropy.com/), [Protocol Labs](https://protocol.ai/) has decided to spin off our drand team into its own private enterprise, now called [Randamu](https://randa.mu/). + + BACKGROUND: Protocol Labs is undergoing a slow and steady process of decentralization, expected to culminate by the end of this year. At its conclusion, Protocol Labs will no longer be one company but rather a network of companies known as the Protocol Labs Network (PLN). Today the PLN is already approaching 100 independent companies - each unique, but bound together in common cause to drive breakthroughs in computing that push humanity forward. For more details please visit the [Protocol Labs Blog](https://protocol.ai/blog/). What do these changes mean for you, the League of Entropy and the drand codebase? diff --git a/blog/2023-10-15-quicknet-is-live-on-League-of-Entropy-mainnet.md b/blog/2023-10-15-quicknet-is-live-on-League-of-Entropy-mainnet.md index 3b3d057f..5d9f27e7 100644 --- a/blog/2023-10-15-quicknet-is-live-on-League-of-Entropy-mainnet.md +++ b/blog/2023-10-15-quicknet-is-live-on-League-of-Entropy-mainnet.md @@ -1,15 +1,21 @@ --- -slug: "quicknet-is-live-on-league-of-entrophy-mainnet" -title: "quicknet is live on League of Entropy mainnet" -authors: [] +slug: "quicknet-live-on-loe-mainnet" +title: "quicknet is live!" +description: "quicknet is live on League of Entropy mainnet" +authors: [yolan] tags: [news] +date: 2023-10-15 --- +## quicknet is live on League of Entropy mainnet + We are thrilled to announce the General Availability (GA) of our brand new `quicknet` drand network running on the `mainnet` nodes. This significant upgrade harnesses the capabilities of the new unchained randomness mode, enables timelock encryption in production, and delivers outputs at a much faster frequency of **3 seconds**! The network has now been running without issues for a month and a half since its launch on August 23rd, and we’ve seen our first early adopters start transitioning to it successfully. -## **🌟 Key Features of `quicknet` drand Network** + + +## 🌟 Key Features of `quicknet` drand Network Keep reading to learn more details about the new features this network launch enables: @@ -18,7 +24,7 @@ Keep reading to learn more details about the new features this network launch en - **3-second frequency:** Quicker generation compared to the legacy frequency, enabling faster applications, better UX, and higher throughput. - **Shorter beacons:** Thanks to the G1-G2 swap that we’re detailing below, we’ve been able to cut our signatures’ size by 50%! -## **The `quicknet` Details** +## The `quicknet` Details We successfully launched the `quicknet-t` Testnet beacon chain on July 13th and more recently the `quicknet` one on our Mainnet on August 23rd. @@ -46,7 +52,7 @@ The same holds for our testnet relays, e.g. [https://pl-us.testnet.drand.sh/chai Check our [DevGuide: HTTP API](https://www.notion.so/3-4-DevGuide-HTTP-API-12e8a9712c5b4b77a52e2b42de1ac009?pvs=21) for more information about our public endpoints! -## **`quicknet-t`** +## `quicknet-t` You can always get more details about a given chain by querying its `{chainhash}/info` endpoint, e.g. [https://testnet-api.drand.cloudflare.com/cc9c398442737cbd141526600919edd69f1d6f9b4adb67e4d912fbc64341a9a5/info](https://testnet-api.drand.cloudflare.com/cc9c398442737cbd141526600919edd69f1d6f9b4adb67e4d912fbc64341a9a5/info) returns the `quicknet-t` details: @@ -63,7 +69,7 @@ You can always get more details about a given chain by querying its `{chainhash} ``` -## **`quicknet`** +## `quicknet` The same holds for our mainnet relays. Any given beacon chain information can be queried from our HTTP relays, e.g. [https://api.drand.sh/52db9ba70e0cc0f6eaf7803dd07447a1f5477735fd3f661792ba94600c84e971/info](https://api.drand.sh/52db9ba70e0cc0f6eaf7803dd07447a1f5477735fd3f661792ba94600c84e971/info) returns the `quicknet` details: @@ -80,7 +86,7 @@ The same holds for our mainnet relays. Any given beacon chain information can be ``` -## **Sun-setting of `fastnet`** +## Sun-setting of `fastnet` If you've been following our blog, you'll remember our previous post about [Timelock Encryption is now supported on drand mainnet](Timelock%20Encryption%20is%20now%20supported%20on%20drand%20main%20327425b1e16d4c22aa0d785dbf1c5fbb.md) where we announced the launch of our new `fastnet` network that supported our timelock scheme. The League of Entropy launched this new drand network on March 1st, 2023. However, we quickly identified an issue with our BLS signatures on G1 that made them non-compliant with the Hash To Curve [RFC 9380](https://www.ietf.org/rfc/rfc9380.html) specification, as well as most BLS signatures implementations on G1 apart from ours. Therefore, we had to double down and launch the `quicknet` network to fix this issue. @@ -91,19 +97,19 @@ us if this is a concern for you or your team. > ℹ️ NOTE: The default chained beacon network remains available with its legacy frequency of 30s for those who require it. We might consider deprecating it at some point in the next 18 months, but nothing is set in stone yet. > -## **Shoutout to the League of Entropy 🤝** +## Shoutout to the League of Entropy 🤝 Our decentralization journey wouldn't be possible without [The League of Entropy](https://www.notion.so/The-League-of-Entropy-1e76674b75e249699445799c5083fe78?pvs=21). We are delighted to share that all members in the League of Entropy are running the `quicknet` drand network alongside the `default` chained beacon network on the League’s network of 23 nodes. A big shoutout to the League of Entropy for their invaluable contributions, running drand nodes for free for anyone to use whenever one needs public, verifiable randomness. Together, we're pioneering a faster, more decentralized future for randomness generation, with this new unchained network enabling a host of new possibilities for our users! -## **Get Started 🚀** +## Get Started 🚀 For developers and users eager to dive into the new `quicknet` drand network, our [official documentation](https://drand.love/developer/) provides detailed resources about using drand relays and beacons. We also have a blog post about “[drand for beginners](https://drand.love/blog/2023/06/02/drand-explainer/)” that’s packed with useful information and another one about [using drand on-chain](https://drand.love/blog/2023/03/16/draffle/) with a demo lottery use-case running on the Filecoin Virtual Machine. -## **G1 - G2 Swap** +## G1 - G2 Swap Let us see what the G1-G2 swap really means! @@ -119,7 +125,7 @@ This is the reason why it makes more sense given the way drand beacons work to h This swap allowed us to **reduce the size of the drand beacons emitted by the new `quicknet` network by 50%**, as well as to **increase the performance and reduce the gas cost** of any on-chain operations pertaining to drand beacons produced by `quicknet`. -## **Unchained Mode** +## Unchained Mode We’ve introduced the notion of [unchained beacons](https://drand.love/blog/2022/02/21/multi-frequency-support-and-timelock-encryption-capabilities/#unchained-randomness-timed-encryption) last year on the blog already. But in essence, the new drand network brings a host of improvements aimed at enhancing the overall UX for drand users and developers. The 'unchained mode' means that new random beacons are entirely independent from previous ones, meaning that you can now perform stateless verification of a beacon, without having to keep a record of past beacons! @@ -127,7 +133,7 @@ These enhancements are designed to make the drand network more robust, efficient We’re looking forward to your projects and ideas, don’t hesitate to [join our Slack workspace](https://join.slack.com/t/drandworkspace/shared_invite/zt-19u4rf6if-bf7lxIvF2zYn4~TrBwfkiA) to discuss these. -## **Security Considerations** +## Security Considerations Finally, you might be wondering what these changes might mean from a **security** point of view. On that front, the guarantees of the League of Entropy (LoE) network remain the same: @@ -141,13 +147,13 @@ The fact that the drand beacons are now **unchained** might give the *false impr We’ve also made sure our new Timelock Encryption service relying on our new `quicknet` network was [properly audited](https://drand.love/blog/2023/05/26/tlock-security-assessment/). We’ve got you covered! -## **Extra Liveness!** +## Extra Liveness! From a **liveness** point of view, the way the drand nodes operate hasn’t changed and we are very happy to announce the availability of a new official HTTP relay run by [StorSwift](https://www.storswift.com/), a dear member of the League of Entropy. Their relay is reachable at [https://api.drand.secureweb3.com:6875](https://api.drand.secureweb3.com:6875/) and as you can see by querying [https://api.drand.secureweb3.com:6875/chains](https://api.drand.secureweb3.com:6875/chains), it provides access to both our mainnet `default` and mainnet `quicknet` beacons. It is also located in Asia. As you can see, the League of Entropy’s and drand’s security, liveness, and availability are not impacted in any way by these changes - on the contrary. -## **Onward!** +## Onward! That’s it, we’ve launched everything we need to allow you to start using Timelock Encryption or drand random beacons right now in your services! And actually, people do! diff --git a/blog/2024-02-22-Retro-on-the-drand-testnet-outage-offeb-21-2024.md b/blog/2024-02-22-Retro-on-the-drand-testnet-outage-offeb-21-2024.md index d170a712..6f3d2c49 100644 --- a/blog/2024-02-22-Retro-on-the-drand-testnet-outage-offeb-21-2024.md +++ b/blog/2024-02-22-Retro-on-the-drand-testnet-outage-offeb-21-2024.md @@ -1,8 +1,10 @@ --- -slug: "retro-on-the-drand-testnet" +slug: "retro-drand-testnet-outage-2024-02-21" title: "Retro on the drand testnet outage of Feb 21, 2024" -authors: [] +description: "Retro on the drand testnet outage of Feb 21, 2024" +authors: [yolan] tags: [news, postmortem, ceremony] +date: 2024-02-22 --- ## **TL;DR** @@ -13,6 +15,8 @@ tags: [news, postmortem, ceremony] - We will re-run the ceremony asynchronously. - Testnet has regained stability and is operating normally. + + ## Background On February 21, 2024, we had to abort our v2.0.2-testnet ceremony after encountering a series of bugs. The `default`, `testnet-g`, and `testnet-unchained-3s` networks were down for about 45 minutes, while `quicknet-t` remained relatively stable. diff --git a/blog/2024-07-26-creating-a-notion-widget-to-display-the-latest-pub.md b/blog/2024-07-26-creating-a-notion-widget-to-display-the-latest-pub.md index d10c6db0..4342fd20 100644 --- a/blog/2024-07-26-creating-a-notion-widget-to-display-the-latest-pub.md +++ b/blog/2024-07-26-creating-a-notion-widget-to-display-the-latest-pub.md @@ -1,12 +1,18 @@ --- slug: "create-a-notion-widget" -title: "Creating a Notion Widget to display the latest Public Randomness from drand!" -authors: [] -tags: [how-to, begginer, features] +title: "Notion Widget for drand Public Randomness!" +description: "Creating a Notion Widget to display the latest Public Randomness from drand!" +authors: [yolan] +tags: [how-to, beginner, features] +date: 2024-07-26 --- +## Creating a Notion Widget to display the latest Public Randomness from drand! + In this blog post, we’ll dive into creating a simple Notion widget that displays the latest public randomness from drand (for both the `default` and `quicknet` beacons from the League of Entropy network). + + ## An overview of drand Our earlier [blog](https://drand.love/blog/a-guide-on-how-to-use-drand) post titled "A Guide on How to Use drand", explains the importance of public randomness and how drand provides it using a threshold network. It offers a step-by-step tutorial on setting up and using drand's randomness in applications, including fetching randomness with JavaScript, verifying it, and using it in real-life scenarios like coin flips and random selection. The guide emphasizes fairness and verifiability in applications requiring random numbers. diff --git a/blog/2024-08-19-greetings.md b/blog/2024-08-19-greetings.md deleted file mode 100644 index 76b880b3..00000000 --- a/blog/2024-08-19-greetings.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -slug: drand-greetings -title: Greetings! -authors: [kentbull, dgrantham] -tags: [hello] ---- - -Congratulations, you have made your first post! - -Feel free to play around and edit this post as much as you like. - - - -We are building a replacement for the drand community docs. - -Once we are done then all of the docs will be done with docusaurus. - -How is line six? - -:::tip[Or eight?] - -Or eight lines? - -::: - -:::danger[Or ten?] - -Or even ten? Oh no! - -::: - -How about twenty? \ No newline at end of file diff --git a/blog/authors.yml b/blog/authors.yml index 32852128..727808f9 100644 --- a/blog/authors.yml +++ b/blog/authors.yml @@ -34,7 +34,7 @@ kentbull: dgrantham: name: Dave Grantham - title: drand Community Scout Master + title: drand Community Manager & Cryptographer url: https://cryptid.tech image_url: https://avatars.githubusercontent.com/u/5017470?v=4 page: @@ -42,3 +42,51 @@ dgrantham: permalink: '/all-dave-grantham-articles' socials: github: dhuseby + +yolan: + name: Yolan Romailler + title: Co-Founder & Cryptographer + description: | + Applied cryptographer with a leaning for broader security/vulnerability research. + + Worked on the Distributed Randomness project, drand, at Protocol Labs and also on CBDC and SSI at SICPA, as well as broader cryptographic engineering at Kudelski Security. I've also been a Security Engineer on the Diem security team for Novi (Facebook/Meta). + A subject matter expert in secure coding. As a consultant, I've supported customers by answering complex questions on security critical systems such as blockchain technologies, and by designing, evaluating and implementing complex cryptography such as key management systems or cryptographic primitives. + url: https://romailler.ch/ + image_url: https://media.licdn.com/dms/image/v2/C5603AQHKMl2eqMuNaw/profile-displayphoto-shrink_200_200/profile-displayphoto-shrink_200_200/0/1587563958538?e=1731542400&v=beta&t=P3xWRN9Vxshih2vPsvbdBKWmBo8mH5rTQGQljBlMEYg + page: true + socials: + linkedin: anomalroil + github: AnomalRoil + blog: https://romailler.ch/ + +patrick: + name: Patrick McClurg + title: Co-founder, CTO (Randamu) + description: | + Randamu, drand, threshold cryptography + Polyglot developer + image_url: https://media.licdn.com/dms/image/v2/D4E03AQHnR3WKvq1g2A/profile-displayphoto-shrink_200_200/profile-displayphoto-shrink_200_200/0/1709586991713?e=1731542400&v=beta&t=ea_E7RBxxyUtNewe_LAF9GvvFd3FzFiIufckhXM4Dps + page: true + socials: + linkedin: patrickmcclurg + +laith: + name: Laith Alissa + title: Fullstack & DevOps Engineer + description: | + I'm a full stack software engineer & devops who loves to build systems and pipelines meticulously. I care about attention to detail, correctness, and maintainability. + image_url: https://media.licdn.com/dms/image/v2/C4E03AQEgjfh_7ZwmSw/profile-displayphoto-shrink_200_200/profile-displayphoto-shrink_200_200/0/1516525202814?e=1731542400&v=beta&t=J4YvtoE2WK49MXtUylIv4xoUq9W9i3u07GkUq78yHwI + page: true + socials: + linkedin: laith-alissa-b2760874 + +erick: + name: Erick Watson + title: Co-Founder & CEO @ Randamu | Decentralized Ecosystem Builder + description: | + Erick Watson serves as the CEO of Randamu, a company that specializes in developing leading-edge cryptographic solutions. With over 15 years of experience in leading innovation projects, Erick has a proven track record of delivering value to customers and stakeholders. + image_url: https://media.licdn.com/dms/image/v2/D5603AQFDZrnupQzeLg/profile-displayphoto-shrink_200_200/profile-displayphoto-shrink_200_200/0/1718309668467?e=1731542400&v=beta&t=kgfROyBEDKJRwqnxhOYRKzOWMOlhNEz9lTeU-SGofJQ + socials: + linkedin: erick-watson + website: https://randa.mu + diff --git a/blog/tags.yml b/blog/tags.yml index faad7b47..83899bdf 100644 --- a/blog/tags.yml +++ b/blog/tags.yml @@ -1,32 +1,12 @@ -facebook: - label: Facebook - permalink: /facebook - description: Facebook tag description - -hello: - label: Hello - permalink: /hello - description: Hello tag description - -docusaurus: - label: Docusaurus - permalink: /docusaurus - description: Docusaurus tag description - -hola: - label: Hola - permalink: /hola - description: Hola tag description - how-to: label: How-to permalink: /how-to description: how to tag -begginer: - label: Begginer - permalink: /begginer - description: begginer tag +beginner: + label: Beginner + permalink: /beginner + description: beginner tag features: label: Features @@ -97,3 +77,8 @@ FVM: label: FVM permalink: /fvm description: fvm tag + +update: + label: update + permalink: /update + description: update tag diff --git a/docusaurus.config.ts b/docusaurus.config.ts index 133c2251..d2276bd3 100644 --- a/docusaurus.config.ts +++ b/docusaurus.config.ts @@ -7,23 +7,16 @@ const config: Config = { tagline: 'Distributed randomness beacon', favicon: 'img/favicon.ico', - // Set the production url of your site here url: 'https://docs.drand.love', - // Set the // pathname under which your site is served - // For GitHub pages deployment, it is often '//' baseUrl: '/', // GitHub pages deployment config. - // If you aren't using GitHub pages, you don't need these. - organizationName: 'drand', // Usually your GitHub org/user name. - projectName: 'drand-docs', // Usually your repo name. + organizationName: 'drand', // GitHub org/user name. + projectName: 'drand-docs', // GitHub repo name. onBrokenLinks: 'ignore', onBrokenMarkdownLinks: 'warn', - // Even if you don't use internationalization, you can use this field to set - // useful metadata like html lang. For example, if your site is Chinese, you - // may want to replace "en" with "zh-Hans". i18n: { defaultLocale: 'en', locales: ['en'], @@ -39,7 +32,13 @@ const config: Config = { 'https://github.com/drand/drand-docs/tree/master', }, blog: { + blogTitle: 'drand Blog', + blogDescription: 'The latest news from the drand project', + blogSidebarTitle: 'All posts', + blogSidebarCount: 'ALL', showReadingTime: true, + readingTime: ({content, frontMatter, defaultReadingTime}) => + defaultReadingTime({content, options: {wordsPerMinute: 300}}), feedOptions: { type: ['rss', 'atom'], xslt: true, @@ -50,6 +49,7 @@ const config: Config = { onInlineTags: 'warn', onInlineAuthors: 'warn', onUntruncatedBlogPosts: 'warn', + }, gtag: { trackingID: 'G-PH6HJ6ECV2'