Crewsphere successfully launched over 50 college hackathons simultaneously across the nation's premier IITs, NITs, and other leading engineering institutions.

Crewsphere Contributes To India’s Web3 Growth: $100K ICP Hackathon

As Hong Kong kicks off its annual FinTech Week conference, which marks one year since the city announced a policy shift with the intent of becoming a global cryptocurrency hub, big industry players have increasingly been focusing their messaging on a broader Web3 beyond just financialisation.

At Hong Kong Web3 events, industry players look past recent crypto scandals to promote blockchain for everything

Major Web3 events in Hong Kong have been focusing more on Web3 usability and use cases like identification, content ownership and video gaming The city faces challenges like recent crypto scandals and a talent shortage,

InvoiceMate is a blockchain & AI-powered invoicing platform that acts as a bridge between SMEs and financing institutions. InvoiceMate leads to easier financial inclusion by enabling SMEs access to various forms of credit like invoice discounting,

Invoicemate Partners With The DFINITY Foundation And Migrates From Hyperledger Fabric To The Internet Computer Blockchain

The DFINITY Foundation a major contributor to the Internet Computer blockchain (ICP), has announced that it has partnered with

Invoicemate Partners With The DFINITY Foundation And Migrates From Hyperledger

World’s first blockchain invoice platform InvoiceMate has jumped ship from Hyperledger Fabric to Internet Computer following a new partnership with DFINITY

World’s First Blockchain Invoicing Platform InvoiceMate Migrates to Internet Computer

World’s first blockchain invoice platform InvoiceMate has jumped ship from Hyperledger Fabric to Internet Computer following a new partnership with DFINITY Foundation, according to a recent announcement.

World’s First Blockchain Invoicing Platform InvoiceMate Migrates Internet Computer

Zurich, Switzerland & Dubai, UAE, October 20, 2023 (PlatoData via 500NewsWire) -- The DFINITY Foundation, a not-for-profit research and development organization based in Switzerland and a major contributor to the Internet Computer blockchain (ICP), has ...

InvoiceMate Partners with the DFINITY Foundation and Migrates from Hyperledger Fabric to The Internet Computer Blockchain

The DFINITY Foundation, a not-for-profit research and development organization based in Switzerland and a major

The DFINITY Foundation, a not-for-profit research and development organization based in Switzerland and a major contributor to the Internet Computer blockchain (ICP), has announced that it has partnered with InvoiceMate.

InvoiceMate partners with the DFINITY Foundation

Dfinity

dfinity

Omnity Eliminates the Chasm Between Bitcoin and Other Networks

Por qué Omnity Hub es la solución más segura y confiable para BTCFi

Pourquoi Omnity Hub est la solution la plus sûre et la plus fiable pour BTCFi

क्यों ओम्निटी हब BTCFi के लिए सबसे सुरक्षित और भरोसेमंद समाधान है

Omnity HubがBTCFiにとって最も安全で信頼できないソリューションである理由

ເປັນຫຍັງ Omnity Hub ເປັນການແກ້ໄຂທີ່ປອດໄພ ແລະບໍ່ມີຄວາມເຊື່ອໝັ້ນທີ່ສຸດສຳລັບ BTCFi

किन Omnity Hub BTCFi को लागि सबैभन्दा सुरक्षित र ट्रस्टलेस समाधान हो

ولې د Omnity Hub د BTCFi لپاره خورا خوندي او بې باوره حل دی

Imaraykutaq Omnity Hub Aswan Seguro & Mana Confiable Solución BTCFi kaqpaq

Почему Omnity Hub — самое безопасное и надежное решение для BTCFi

Impamvu Omnity Hub nigisubizo cyizewe cyane kandi kitizewe kuri BTCFi

Bakit Ang Omnity Hub ang Pinaka-Secure at Hindi Pinagkakatiwalaang Solusyon para sa BTCFi

Чому Omnity Hub є найбезпечнішим і надійним рішенням для BTCFi

Welcome to our "Innovators in Web3" series, where we delve into the minds shaping the future of blockchain technology. Today, we're honored to have Aisling Connolly, a prominent figure in cryptography and privacy research, discuss her pivotal role in integrating Internet Computer with Bitcoin. Aisling's deep expertise not only advances the field but also sets the stage for transformative changes across the Web3 landscape. Join us as we uncover how her groundbreaking work is driving innovation and securing a more interconnected digital world. Ishan Pandey: Hi Aisling. It's wonderful to have you here for our "Innovators in Web3" series. To start, could you share how your background in cryptography and privacy research has shaped the development strategies for Internet Computer's integration with Bitcoin? Aisling Connolly: My background and research interests have always been inspired by the cryptographers on the DFINITY team and generally, among such a group, the strategy is always to focus on strong cryptographic security and high-quality engineering. This can clearly be seen in our Bitcoin integration. Natively running Bitcoin adapters on ICP nodes removes some of the trust assumptions that come with traditional Bitcoin bridges. Our threshold signing capabilities also have stronger practical guarantees that are not always found in other implementations. Ishan Pandey: Internet Computer is being termed as a "Bitcoin layer-zero." Can you explain this concept for our audience and how it positions ICP in the broader blockchain ecosystem? Aisling Connolly: If you think about ICP from a high level, it consists of a network of nodes running in independent data centers which allow developers to build highly scalable applications. Moreover, ICP is built by one of the strongest cryptographic teams in the world, and hence has an unparalleled suite of cryptographic tools in addition to its web2 integrations. These features together serve as an ideal basis on which to build smart contracts and applications that interact with Bitcoin and Web3 more generally. Ishan Pandey: The introduction of Threshold-Schnorr signatures is a significant technical update. Could you discuss the advantages this brings to the Internet Computer Protocol, particularly in terms of security and efficiency compared to the existing ECDSA scheme? Aisling Connolly: Schnorr is a simpler scheme than ECDSA, so it’s easier to reason about its security. Hence, researchers and developers are less likely to make mistakes in implementations and analysis. The key benefits it brings, however, are in efficiency and the features it unlocks for bitcoin. Ishan Pandey: With the upcoming Bitcoin halving and the launch of the Runes protocol, how do you see the role of ICP evolving in the creation of Bitcoin-centric DeFi and NFT applications? Aisling Connolly: There are two key ways we see ICP being used in the creation of Bitcoin-centric DeFi and NFT. On the one hand, developers are using the ICP network as a basis to build DeFi and NFT applications without needing to build their own network from scratch and without the need for bridges or oracles. On the other hand, we’ve seen people using the ICP ecosystem to allow trading of assets (both in DeFi and NFT) with very fast finality and negligible fees. Ishan Pandey: Aisling, considering the broad scope of applications from DeFi to NFTs on the Bitcoin blockchain, what future developments can we expect from DFINITY to enhance these capabilities? Aisling Connolly: Right now, we are working on the threshold Schnorr integration which will allow smart contracts to interact with newer Defi and NFT aspects of Bitcoin directly. When complete, this will be the third pillar of our Bitcoin APIs (Bitcoin core functions, threshold-ECDSA signatures, and threshold-Schnorr signatures.) Beyond this, we’re looking closely at the developer tooling for Bitcoin devs and aim to create the best developer experience in the industry. Ishan Pandey: With ICP's 3rd anniversary approaching and the unveiling of the new "AI Roadmap" and "Chain Fusion Roadmap," can you share what these roadmaps mean for ICP's future? How will they shape the development and the overall impact of the Internet Computer Protocol in the coming years? Aisling Connolly: AI is becoming more integral to daily life, yet it faces a significant trust issue due to users' lack of insight into data usage and response generation. The opaque nature of AI models makes trust-building challenging. The AI Roadmap outlines a path that will bring trust and security to AI models. I am particularly interested in how AI can influence DeFI. Similar to traditional finance AI can be used AML services, fees or rates calculation, and market analysis in the DeFi space. Chain Fusion is a major priority for us this year. ICP enables direct interoperability with all major blockchains, including Bitcoin, Ethereum, other EVMs (and soon Solana), without relying on any trusted intermediary. Chain Fusion will open up a host of new use cases and access to liquidity for projects leveraging Chain Fusion. Ishan Pandey: Looking towards the future post-halving, how do you anticipate the Bitcoin ecosystem will change, and what role will the Internet Computer play in this new landscape? Aisling Connolly: From the conversations and discussions among some of the leading Bitcoin developers, there are a lot of super interesting projects set to launch in the coming months. Serious researchers are starting to enter the conversation, and we see the development of a host of new meta-protocols that take Bitcoin beyond the use cases of ordinals and runes. We’re seeing already that many developers are choosing the ICP network and suite of cryptographic tools to build their L2s, protocols, and other applications. This means they can get to market much faster as they don’t have to bootstrap a network from scratch, and they can inherit security and other advanced features of ICP. Don’t forget to like and share the story! Vested Interest Disclosure: This author is an independent contributor publishing via our business blogging program. HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR. Welcome to our "Innovators in Web3" series, where we delve into the minds shaping the future of blockchain technology. Today, we're honored to have Aisling Connolly, a prominent figure in cryptography and privacy research, discuss her pivotal role in integrating Internet Computer with Bitcoin. Aisling's deep expertise not only advances the field but also sets the stage for transformative changes across the Web3 landscape. Join us as we uncover how her groundbreaking work is driving innovation and securing a more interconnected digital world. Ishan Pandey: Hi Aisling. It's wonderful to have you here for our "Innovators in Web3" series. To start, could you share how your background in cryptography and privacy research has shaped the development strategies for Internet Computer's integration with Bitcoin? Ishan Pandey: Hi Aisling. It's wonderful to have you here for our "Innovators in Web3" series. To start, could you share how your background in cryptography and privacy research has shaped the development strategies for Internet Computer's integration with Bitcoin? Ishan Pandey: Hi Aisling. It's wonderful to have you here for our "Innovators in Web3" series. To start, could you share how your background in cryptography and privacy research has shaped the development strategies for Internet Computer's integration with Bitcoin? Aisling Connolly: My background and research interests have always been inspired by the cryptographers on the DFINITY team and generally, among such a group, the strategy is always to focus on strong cryptographic security and high-quality engineering. This can clearly be seen in our Bitcoin integration. Natively running Bitcoin adapters on ICP nodes removes some of the trust assumptions that come with traditional Bitcoin bridges. Our threshold signing capabilities also have stronger practical guarantees that are not always found in other implementations. Aisling Connolly: Ishan Pandey: Internet Computer is being termed as a "Bitcoin layer-zero." Can you explain this concept for our audience and how it positions ICP in the broader blockchain ecosystem? Ishan Pandey: Internet Computer is being termed as a "Bitcoin layer-zero." Can you explain this concept for our audience and how it positions ICP in the broader blockchain ecosystem? Ishan Pandey: Internet Computer is being termed as a "Bitcoin layer-zero." Can you explain this concept for our audience and how it positions ICP in the broader blockchain ecosystem? Aisling Connolly: If you think about ICP from a high level, it consists of a network of nodes running in independent data centers which allow developers to build highly scalable applications. Moreover, ICP is built by one of the strongest cryptographic teams in the world, and hence has an unparalleled suite of cryptographic tools in addition to its web2 integrations. These features together serve as an ideal basis on which to build smart contracts and applications that interact with Bitcoin and Web3 more generally. Aisling Connolly: Ishan Pandey: The introduction of Threshold-Schnorr signatures is a significant technical update. Could you discuss the advantages this brings to the Internet Computer Protocol, particularly in terms of security and efficiency compared to the existing ECDSA scheme? Ishan Pandey: The introduction of Threshold-Schnorr signatures is a significant technical update. Could you discuss the advantages this brings to the Internet Computer Protocol, particularly in terms of security and efficiency compared to the existing ECDSA scheme? Ishan Pandey: The introduction of Threshold-Schnorr signatures is a significant technical update. Could you discuss the advantages this brings to the Internet Computer Protocol, particularly in terms of security and efficiency compared to the existing ECDSA scheme? Aisling Connolly: Schnorr is a simpler scheme than ECDSA, so it’s easier to reason about its security. Hence, researchers and developers are less likely to make mistakes in implementations and analysis. The key benefits it brings, however, are in efficiency and the features it unlocks for bitcoin. Aisling Connolly: Ishan Pandey: With the upcoming Bitcoin halving and the launch of the Runes protocol, how do you see the role of ICP evolving in the creation of Bitcoin-centric DeFi and NFT applications? Ishan Pandey: With the upcoming Bitcoin halving and the launch of the Runes protocol, how do you see the role of ICP evolving in the creation of Bitcoin-centric DeFi and NFT applications? Ishan Pandey: With the upcoming Bitcoin halving and the launch of the Runes protocol, how do you see the role of ICP evolving in the creation of Bitcoin-centric DeFi and NFT applications? Aisling Connolly: There are two key ways we see ICP being used in the creation of Bitcoin-centric DeFi and NFT. Aisling Connolly: On the one hand, developers are using the ICP network as a basis to build DeFi and NFT applications without needing to build their own network from scratch and without the need for bridges or oracles. On the other hand, we’ve seen people using the ICP ecosystem to allow trading of assets (both in DeFi and NFT) with very fast finality and negligible fees. Ishan Pandey: Aisling, considering the broad scope of applications from DeFi to NFTs on the Bitcoin blockchain, what future developments can we expect from DFINITY to enhance these capabilities? Ishan Pandey: Aisling, considering the broad scope of applications from DeFi to NFTs on the Bitcoin blockchain, what future developments can we expect from DFINITY to enhance these capabilities? Ishan Pandey: Aisling, considering the broad scope of applications from DeFi to NFTs on the Bitcoin blockchain, what future developments can we expect from DFINITY to enhance these capabilities? Aisling Connolly: Right now, we are working on the threshold Schnorr integration which will allow smart contracts to interact with newer Defi and NFT aspects of Bitcoin directly. When complete, this will be the third pillar of our Bitcoin APIs (Bitcoin core functions, threshold-ECDSA signatures, and threshold-Schnorr signatures.) Beyond this, we’re looking closely at the developer tooling for Bitcoin devs and aim to create the best developer experience in the industry. Aisling Connolly: Ishan Pandey: With ICP's 3rd anniversary approaching and the unveiling of the new "AI Roadmap" and "Chain Fusion Roadmap," can you share what these roadmaps mean for ICP's future? How will they shape the development and the overall impact of the Internet Computer Protocol in the coming years? Ishan Pandey: With ICP's 3rd anniversary approaching and the unveiling of the new "AI Roadmap" and "Chain Fusion Roadmap," can you share what these roadmaps mean for ICP's future? How will they shape the development and the overall impact of the Internet Computer Protocol in the coming years? Ishan Pandey: With ICP's 3rd anniversary approaching and the unveiling of the new "AI Roadmap" and "Chain Fusion Roadmap," can you share what these roadmaps mean for ICP's future? How will they shape the development and the overall impact of the Internet Computer Protocol in the coming years? Aisling Connolly: AI is becoming more integral to daily life, yet it faces a significant trust issue due to users' lack of insight into data usage and response generation. The opaque nature of AI models makes trust-building challenging. The AI Roadmap outlines a path that will bring trust and security to AI models. I am particularly interested in how AI can influence DeFI. Similar to traditional finance AI can be used AML services, fees or rates calculation, and market analysis in the DeFi space. Aisling Connolly: Chain Fusion is a major priority for us this year. ICP enables direct interoperability with all major blockchains, including Bitcoin, Ethereum, other EVMs (and soon Solana), without relying on any trusted intermediary. Chain Fusion will open up a host of new use cases and access to liquidity for projects leveraging Chain Fusion. Ishan Pandey: Looking towards the future post-halving, how do you anticipate the Bitcoin ecosystem will change, and what role will the Internet Computer play in this new landscape? Ishan Pandey: Looking towards the future post-halving, how do you anticipate the Bitcoin ecosystem will change, and what role will the Internet Computer play in this new landscape? Looking towards the future post-halving, how do you anticipate the Bitcoin ecosystem will change, and what role will the Internet Computer play in this new landscape? Aisling Connolly: From the conversations and discussions among some of the leading Bitcoin developers, there are a lot of super interesting projects set to launch in the coming months. Serious researchers are starting to enter the conversation, and we see the development of a host of new meta-protocols that take Bitcoin beyond the use cases of ordinals and runes. Aisling Connolly: We’re seeing already that many developers are choosing the ICP network and suite of cryptographic tools to build their L2s, protocols, and other applications. This means they can get to market much faster as they don’t have to bootstrap a network from scratch, and they can inherit security and other advanced features of ICP. Don’t forget to like and share the story! Vested Interest Disclosure: This author is an independent contributor publishing via our business blogging program. HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR. Vested Interest Disclosure: This author is an independent contributor publishing via our business blogging program . HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR. Vested Interest Disclosure: business blogging program business blogging program

Why Internet Computer’s Approach to Bitcoin Integration Could Redefine Web3

কেন ইন্টারনেট কম্পিউটারের বিটকয়েন ইন্টিগ্রেশনের দৃষ্টিভঙ্গি Web3 পুনরায় সংজ্ঞায়িত করতে পারে

Warum der Ansatz von Internet Computer zur Bitcoin-Integration Web3 neu definieren könnte

Por qué el enfoque de Internet Computer para la integración de Bitcoin podría redefinir la Web3

Pourquoi l'approche d'Internet Computer en matière d'intégration Bitcoin pourrait redéfinir le Web3

बिटकॉइन एकीकरण के लिए इंटरनेट कंप्यूटर का दृष्टिकोण वेब3 को फिर से परिभाषित कर सकता है

インターネットコンピュータのビットコイン統合へのアプローチがWeb3を再定義する理由

비트코인 통합에 대한 인터넷 컴퓨터의 접근 방식이 Web3를 재정의할 수 있는 이유

Por que a abordagem do Internet Computer para a integração do Bitcoin pode redefinir a Web3

Почему подход Интернет-компьютера к интеграции биткойнов может переопределить Web3

İnternet Bilgisayarının Bitcoin Entegrasyonuna Yaklaşımı Neden Web3'ü Yeniden Tanımlayabilir?

Tại sao cách tiếp cận tích hợp Bitcoin của máy tính Internet có thể định nghĩa lại Web3

为什么互联网计算机对比特币的整合方式可以重新定义 Web3

As the world of finance rapidly evolves, one trend that is capturing significant attention is the rise of decentralized finance (DeFi), which offers a revolutionary alternative to traditional banking systems and puts individuals in control of their financial futures. With decentralized networks like Bitcoin and Ethereum, people can access various financial services like lending, borrowing, trading, and asset management 24/7/365, without relying on intermediaries. DeFi democratizes finance by promoting accessibility, transparency, and security for the masses. It's an exciting time for the financial world as DeFi continues to change the game and bring more people into the world of decentralized finance. DeFi Evolution Timeline Let’s take a look at how it all started, how it evolved, and where do people make DeFi history these days: 🎂 2008 The pseudonymous Satoshi Nakamoto publishes the Bitcoin white paper, which outlines the design of a decentralized digital currency based on cryptography and a blockchain ledger. 🧑‍💻 2009 DeFi was born when the first Bitcoin block was mined, the first P2P digital asset built on top of the blockchain network. 🏪 2013 The first decentralized cryptocurrency exchange, CryptoNext, launched 🤖 2014 The first decentralized autonomous organization (DAO) is created on the Ethereum network. 🧐 2015 Ethereum launches its initial coin offering (ICO), raising $18 million in ether 📜 2016 The Ethereum network goes live, enabling the development of smart contracts and decentralized applications 💸 2018 The launch of the Compound and Uniswap protocol, which allows users to earn interest and trade cryptos, marks a new era of the DeFi movement. 📈 2019 DeFi sees rapid growth, with the launch of numerous decentralized exchanges, lending/borrowing platforms, and stablecoins such as MakerDao, Curve, dYdX, Aave, DAI, etc. ⛏️ 2020 DeFi Summer reaches mainstream awareness fueled by the liquidity mining program of COMP tokens launched by Compound in May 2020. ䷰ 2021 DeFi continues to evolve, with the launch of new protocols and financial instruments and an increase in regulatory attention. 🛸 2023 DFINITY Foundation launches ckBTC, a native BTC integration that replaces wrapped tokens and bridges with pure cryptography. #ckBTC is Every/Where/Thing A revolutionary solution by the Internet Computer allows network users to directly hold, receive, and seamlessly send Chain-Key Bitcoin (ckBTC) – cryptographically backed 1:1 with real bitcoin. The world’s most popular cryptocurrency can now be utilized for decentralized finance (DeFi) operations, such as yield farming, lending, and payments. Directly integrating with Bitcoin eliminates the need for bridged or wrapped Bitcoin, a common but unreliable method for connecting different blockchains and one susceptible to errors and hacking attempts. With ckBTC, transactions will be processed quickly and inexpensively on a local ledger and finalized on the Bitcoin network only when necessary. To better understand ckBTC, here is a comparison table of BTC, ckBTC, wBTC, tBTC: Feature BTC ckBTC wBTC tBTC Definition Bitcoin is a decentralized cryptocurrency and digital payment system ckBTC is a token backed 1:1 by Bitcoin and built on top of the Internet Computer wBTC is a token backed 1:1 by Bitcoin and built on the Ethereum network tBTC is a token backed 1:1 by Bitcoin and built on the Ethereum network Purpose To provide a decentralized, peer-to-peer digital currency and payment system To provide a fast and low-cost alternative for Bitcoin transactions and decentralized finance activities To bring Bitcoin's security to the Ethereum network for decentralized finance activities To bring Bitcoin's security to the Ethereum network for decentralized finance activities Issuance Created through a decentralized network of computers solving complex mathematical problems Issued and redeemed through canister smart contracts on the Internet Computer Issued through a centralized custodian and can be redeemed for Bitcoin Issued through a decentralized network of trusted participants and can be redeemed for Bitcoin Pros/Cons Secure, transparent, and resistant to manipulation. Transactions with ckBTC are processed quickly and inexpensively on a local ledger and only settled on the Bitcoin network when necessary. Less decentralized than Bitcoin or ckBTC. tBTC is issued and managed by a decentralized network of trusted participants, making it more decentralized than wBTC Is ckBTC for real, or is it just an alien tech? Indeed, #ckBTC is now live. The testnet has been active for an extended period, providing developers and builders ample opportunity to experiment with the technology. Here’s what that means for users: if you managed to get your hands on some $ckBTC, then you are good to swap it on ICP Decentralized Exchanges (DEXes). The talent and ambition of developers building on the Internet Computer blockchain is unlike any other ecosystem. Every project that takes part in this program has the ability to make a real impact in the blockchain industry. But what about the bigger picture? Some ICP Community projects are already developing solutions on top of this integration. DEXes such as Helix Markets and IC Lighthouse are leveraging the Bitcoin and Chain-Key signing features to offer bridgeless inter-chain token swaps. , a platform that allows cross-chain lending and borrowing against crypto without bridging, including Bitcoin, is using ckBTC too. – an NFT-based crowdfunding platform – is using ICP-BTC integration to accept funding for projects in BTC. Finterest Funded The DFINITY R&D team exceeded my expectations. They are excellent. I spoke with the engineers about the BTC and ETH integration. I was impressed! AstroX Co-Founder : Brutoshi It's amazing, isn't it? You can use BTC to crowdfund your digital project. Although this ignites my excitement, it appears there are no projects doing this…yet. Maybe it should be you who runs the first BTC fundraiser on Funded? Got a brilliant idea? Go check it out. It’s time to build! What is ICP Lab? ICP.Lab is a unique chance to meet other DeFi enthusiasts and professionals, share knowledge, and build the future of DeFi together. From what it seems, if you want to be at the of the DeFi revolution in 2023 - ICP.Lab is the place to go. According to the , you can witness it monthly at Dfinity HQ in Zurich. forefront source This DeFi meetup for the Internet Computer community marks the start of its third ICP.Lab initiative. This is an exceptional opportunity for DeFi enthusiasts and professionals to join the DeFi revolution and learn about the latest trends and developments in the space. Attendees of the program have the exclusive chance to be based at the Dfinity Foundation's headquarters in Zürich, Switzerland, the largest blockchain research and development center in the region. This is where participants get direct access to the wealth of knowledge and expertise from the experienced DFINITY team, including personalized coaching and workshops led by DFINITY's experts in R&D, Growth, Finance, Operations, and other key areas of the business. This week was very good and exceeded my expectations. I found the DFINITY team to be practical and helpful. So many developers with the same goal are gathered in the same room. It was a great opportunity to learn and get helpful feedback from the team Co-Founder of ICP League: Blockpunk People from the Foundation mentioned the plans to also open its extensive network of advisors and investors to the selected projects, which really excites me personally. As if that was not enough, ICP.Lab has partnered with some of the most active investors and participants in the Swiss blockchain space, including CV Labs, CV VC, INACTA, Crypto Valley, and Crypto Oasis, to bring more DeFi intel together and drive innovation forward. “The projects unlike any other projects” : Bringing true ownership and full transparency to DeFi trading Helix Markets : An automated market maker (AMM) that allows users to create, stake, and swap ETH & IC tokens Infinity Swap : A lending protocol that allows users to supply assets to the protocol and earn yield upon them Finterest : An Internet Computer community initiative with 40,000+ community members and 500+ community developers ICP League : Developers of the ME wallet - a multi-chain smart wallet that uses biometric technologies including fingerprints and facial recognition AstroX : A DEX built on the Internet Computer blockchain Orderswap : A leading-edge technology laboratory in the blockchain direction composed of top universities and community developers in Asia Mix Labs : DeFi development framework and Defi ecosystem on Internet Computer blockchain. IC Lighthouse : Building multi-chain products and tools for the next era of decentralized internet Rock Labs : Although there were 10 projects announced, I could only get my hands on 9 of them. If you are / you know that mysterious one - please ping me on . The first 10 people will get 1 ICP from me. ??? Twitter … at Google we're always thinking about 10x-ing things. I wanted to bring that same mentality to ICP.Lab... many VCs and investors were very impressed with what they saw… Tim Hermann, Senior Partner Manager at DFINITY Foundation: The Internet Computer Blockchain: The DFINITY Foundation has brought the dream of a decentralized Internet to life with its groundbreaking creation, the Internet Computer. Say goodbye to slow, centralized systems and hello to a world where end-to-end decentralized solutions are possible. Welcome to the future of the Internet, where a whole new world of web-speed services is now possible.\ The DFINITY Foundation: The DFINITY Foundation, headquartered in Zurich, is a not-for-profit organization focused on the advancement of the Internet Computer blockchain. Led by founder and Chief Scientist, Dominic Williams, the organization boasts a massive R&D team, with over 270 members spread across research centers in Zurich, Palo Alto, San Francisco, and Shanghai. With a track record of success, the team has published over 1564 articles, received 86,347 citations, and holds 191 patents. At the forefront of blockchain innovation, the DFINITY Foundation is dedicated to shaping the future of technology. What’s Next? 🧑‍💻 If you're a developer and would like to discuss #ckBTC with someone who can answer your questions, this is to talk to. the right person 🚀 For existing web3 startups interested in incorporating #ckBTC into their product for explosive growth, make sure to reach out to the people who live and breathe growth 🏦 And for those who are passionate about decentralized finance (DeFi) and would like to understand how #ckBTC can be used to their advantage, make sure you follow the legend Whether you're a developer, startup, or DeFi enthusiast, #ckBTC offers a variety of resources and support to help you get started with using this innovative token.

Is ckBTC for Real, or is it Just an Alien Tech?

¿Es ckBTC real o es solo una tecnología alienígena?

ckBTC est-il pour de vrai, ou est-ce juste une technologie extraterrestre ?

क्या ckBTC असली है, या यह सिर्फ एक एलियन टेक है?

ckBTC は本物なのか、それとも単なる Alien Tech なのか?

O ckBTC é real ou é apenas uma tecnologia alienígena?

CKBTC có thật hay chỉ là một công nghệ ngoài hành tinh?

ckBTC 是真实的，还是只是一种外来技术？

This tutorial is dedicated to Internet Computer (Dfinity) platform. After completing it: You will know some advanced Internet Computer canister (smart-contract) development techniques on Rust. You will use library to execute background canisters tasks. IC-Cron You will use and Rust libraries to manage background task scheduling time. Chrono now This tutorial attempts to give all the information in a beginner-friendly manner, however it is intended for advanced blockchain-developers, who already understand all the basics about Rust canister development for the Internet Computer. Before we begin, it is recommended to go through these basics again. Here are some good starting points: , dedicated to canister development on the IC; , where you can find an answer to almost any question. official website developer forum Motivation It is a frequent software development task - to automatically execute some kind of task in a particular time of year, month, week or day. Some examples are: recurrent payments, which one needs to process, for example, each first day of each month at 12PM; database backup creation, which should be executed every each day at 9PM; email distribution, that should occur each week at some particular day and particular time; This tutorial tries to help developers, who want to implement the same kind of functionality on the IC. We are going to build a simple Rust canister, that should greet its users each week at any day of week the user defines. Complete tutorial code of this project can be found in this repository: https://github.com/seniorjoinu/ic-cron-time-alignment Project initialization To complete this tutorial we would need these tools: dfx 0.9.0 and toolchain rust 1.54+ wasm32-unknown-unknown ic-cdk-optimizer You can use any file system layout you want, but here’s mine: - src
  - actor.rs       // файл, опысывающий логику нашего канистера
  - common.rs      // вспомогательные функции
- build.sh         // скрипт билда канистера
- can.did          // candid интерфейс нашего канистера
- cargo.toml
- dfx.json First of all, let’s set up the build procedure for our project. Inside we need to declare all of the dependencies we would use: cargo.toml // cargo.toml

[package]
name = "ic-cron-time-alignment"
version = "0.1.0"
edition = "2018"

[lib]
crate-type = ["cdylib"]
path = "src/actor.rs"

[dependencies]
ic-cdk = "0.3"
ic-cdk-macros = "0.3"
serde = "1.0"
ic-cron = "0.5.1"
chrono = "0.4"
now = "0.1"
num-traits = "0.2" Then inside file we have to put this script - it will build and optimize a wasm-module for us: build.sh # build.sh

#!/usr/bin/env bash

cargo build --target wasm32-unknown-unknown --release --package ic-cron-time-alignment && \
 ic-cdk-optimizer ./target/wasm32-unknown-unknown/release/ic_cron_time_alignment.wasm -o ./target/wasm32-unknown-unknown/release/ic-cron-time-alignment-opt.wasm And also we need file, in which we would declare our canisters (we only have one) and what are they made of: dfx.json {
  "canisters": {
    "ic-cron-time-alignment": {
      "build": "./build.sh",
      "candid": "./can.did",
      "wasm": "./target/wasm32-unknown-unknown/release/ic-cron-time-alignment-opt.wasm",
      "type": "custom"
    }
  },
  "dfx": "0.9.0",
  "networks": {
    "local": {
      "bind": "127.0.0.1:8000",
      "type": "ephemeral"
    }
  },
  "version": 1
} Time management The function from ic-cron, which we’re going to use today for task scheduling has the following signature: cron_enqueue() pub fn cron_enqueue<Payload: CandidType>(
  payload: Payload,
  scheduling_interval: SchedulingInterval,
) -> TaskId; Let’s dive deep into it to better understand how exactly ic-cron will process our scheduled tasks. This function accepts these two arguments: , of any type that implements (it is a trait, that lets us efficiently serialize data in IC-compatible manner) - this argument allows a developer to attach any kind of data they would need at the moment of execution; payload CandidType , of type - this argument is used to set the correct task scheduling settings. scheduling_interval SchedulingInterval The first argument is not so interesting for us in this tutorial (because it is pretty simple - you just attach any data you want and that’s it), but the second one is very interesting. Let’s take a closer look at it. The type is defined this way: SchedulingInterval #[derive(Clone, Copy, CandidType, Deserialize)]
pub enum Iterations {
    Infinite,
    Exact(u64),
}

#[derive(Clone, Copy, CandidType, Deserialize)]
pub struct SchedulingInterval {
    pub delay_nano: u64,
    pub interval_nano: u64,
    pub iterations: Iterations,
} Notice how both of these types are annotated with and macros - this enables us to easily transmit them between canisters or even use them as a for task scheduling with ic-cron. CandidType Deserialize payload This type has three following fields: - an amount of nanoseconds the scheduler will wait until executing this task for a first time (if you pass here, the task will be executed at the next consensus round); delay_nano 0 - an amount of nanoseconds the scheduler will wait after each execution of the task to execute it again (if you pass here, the task will be executed at every consensus round); interval_nano 0 - enum type that has two values: iterations - this task should be executed infinite number of times, until it is manually descheduled (using function) Infinite cron_dequeue() - this task should be executed the exact amount of times. Exact(u64) It is important to remember that time flows differently on any blockchain platform - non-linearly and in spurts. During a single transaction execution time is not moving at all (if you execute function two times in a row they both return the same result). This happens because subnet nodes only synchronize their state (and time) with the consensus protocol which runs in rounds. time() Therefore any time-related operations on IC should be performed with that in mind and never rely on time intervals lesser than a single consensus round duration. In IC the consensus is pretty fast (relative to other blockchain platforms) - a single consensus round continues for about two seconds. You should always take it into account. For example, if you pass 10 seconds inside while scheduling a task, this task won’t necessarily be executed exactly after 10 seconds. More likely it will be executed in an interval between 10 and 12 seconds, despite the fact that ic-cron will do its best to compensate for that error. delay_nano So, if for example, you would create an object like: let nanos_in_sec = 1_000_000_000u64;

let scheduling_interval = SchedulingInterval {
	delay_nano: 10 * nanos_in_sec,
	interval_nano: 60 * nanos_in_sec,
	iterations: Iterations::Exact(10),
}; The task you would use this interval with will be processed like this: first, the scheduler will wait for at least 10 seconds to pass; then, the scheduler will execute the task for the first time; then, the scheduler will wait for at least a minute and execute it once again; the previous entry will repeat 9 times until the total count of executions reaches 10; after that, the scheduler will deschedule the task and remove it from its memory forever. So it looks like, in order to execute a task on some particular day of the week, a developer only needs to carefully calculate and parameters. should equal to an amount of nanoseconds from the moment of task creation to the defined weekday. should equal to constant - the amount of nanoseconds in a week. delay_nano interval_nano delay_nano interval_nano First of all, let’s define an enum that would hold weekdays for us: // common.rs

#[derive(CandidType, Deserialize)]
pub enum DayOfWeek {
    Mon,
    Tue,
    Wed,
    Thu,
    Fri,
    Sat,
    Sun,
}

impl DayOfWeek {
    pub fn to_weekday_num(&self) -> u32 {
        match self {
            DayOfWeek::Mon => 1,
            DayOfWeek::Tue => 2,
            DayOfWeek::Wed => 3,
            DayOfWeek::Thu => 4,
            DayOfWeek::Fri => 5,
            DayOfWeek::Sat => 6,
            DayOfWeek::Sun => 7,
        }
    }
} Yes, we could use the same exact type from library called , but then we would have to implement and traits for them by hand, which is not something we want to spend time for. chrono Weekday CandidType Deserialize This enum has nothing interesting at all. Only a little helper-function that returns the number of the weekday in that week. It would be very nice if we could work with timestamps (which are basically just ) in some semantically pleasant way, so let’s define a trait that we’ll use later to work with : u64 u64 // common.rs

pub trait TimeNanos {
    fn to_datetime(&self) -> DateTime<Utc>;
    fn nanos_till_next(&self, weekday: DayOfWeek) -> u64;
} This trait contains only two methods: - transforms a timestamp into type from library, that has rich functionality in terms of time manipulations; to_datetime() u64 DateTime chrono - calculates an amount of nanoseconds between a timestamp and the next day of week provided by user as an argument. nanos_till_next(DayOfWeek) u64 Let’s implement this trait for now, starting with function: u64 to_datetime() // common.rs

impl TimeNanos for u64 {
    fn to_datetime(&self) -> DateTime<Utc> {
        let system_time = UNIX_EPOCH + std::time::Duration::from_nanos(*self);

        DateTime::<Utc>::from(system_time)
    }

		...
} There is nothing interesting happens here. We just use Rust’s standard library to get UTC time from nanoseconds timestamp we have and then wrap this system time object into type. DateTime Now let’s move to the most interesting function here - : nanos_till_next() // common.rs

impl TimeNanos for u64 {
    fn nanos_till_next(&self, weekday: DayOfWeek) -> u64 {
        let current_datetime = self.to_datetime();

        let current_weekday_num = current_datetime
            .weekday()
            .number_from_monday()
            .to_i64()
            .unwrap();
        let target_weekday_num = weekday.to_weekday_num().to_i64().unwrap();

        let same_weekday_correction = if target_weekday_num == current_weekday_num {
            7
        } else {
            0
        };

        let days_till_target =
            (same_weekday_correction + target_weekday_num - current_weekday_num).abs();

				let duration_since_beginning_of_the_day =
            current_datetime - current_datetime.beginning_of_day();

        let duration_till_target =
            Duration::days(days_till_target) - duration_since_beginning_of_the_day;

        duration_till_target
            .num_nanoseconds()
            .unwrap()
            .to_u64()
            .unwrap()
    }

		...
} First of all, we get current from the function we just defined ourselves - . DateTime to_datetime() Then we get a weekday number of the current and also a weekday number of the day of week passed by the user as an argument. Then we calculate the amount of days between current weekday and the target weekday (taking into account the fact that they can be the same). DateTime After that we just wrap that amount of days into a object and subtract an amount of time that is already passed today since the start of the day (this will make our final result to match exactly time of our target weekday). The result we return as nanoseconds. Duration 00:00 Sanity check As you might notice, our functions don’t use any of Internet Computer system APIs. This is great, because it allows us to use standard Rust’s test engine in order to check if we did everything right: // common.rs

#[cfg(test)]
mod tests {
    use crate::common::NANOS_IN_DAY;
    use crate::{DayOfWeek, TimeNanos, NANOS_IN_WEEK};
    use chrono::{DateTime, NaiveDate, Utc};
    use num_traits::ToPrimitive;

    fn str_to_datetime(str: &str) -> DateTime<Utc> {
        DateTime::<Utc>::from_utc(
            NaiveDate::parse_from_str(str, "%d-%m-%Y")
                .unwrap()
                .and_hms(0, 0, 0),
            Utc,
        )
    }

    #[test]
    fn works_fine() {
        let mon = str_to_datetime("31-01-2022")
            .timestamp_nanos()
            .to_u64()
            .unwrap();
        let tue = str_to_datetime("08-02-2022")
            .timestamp_nanos()
            .to_u64()
            .unwrap();
        let wed = str_to_datetime("16-02-2022")
            .timestamp_nanos()
            .to_u64()
            .unwrap();
        let thu = str_to_datetime("24-02-2022")
            .timestamp_nanos()
            .to_u64()
            .unwrap();
        let fri = str_to_datetime("04-03-2022")
            .timestamp_nanos()
            .to_u64()
            .unwrap();
        let sat = str_to_datetime("12-03-2022")
            .timestamp_nanos()
            .to_u64()
            .unwrap();
        let sun = str_to_datetime("20-03-2022")
            .timestamp_nanos()
            .to_u64()
            .unwrap();

        // checking days consistency
        assert_eq!(
            mon.nanos_till_next(DayOfWeek::Mon),
            NANOS_IN_WEEK,
            "Invalid time dif mon"
        );
        assert_eq!(
            tue.nanos_till_next(DayOfWeek::Tue),
            NANOS_IN_WEEK,
            "Invalid time dif tue"
        );
        assert_eq!(
            wed.nanos_till_next(DayOfWeek::Wed),
            NANOS_IN_WEEK,
            "Invalid time dif wed"
        );
        assert_eq!(
            thu.nanos_till_next(DayOfWeek::Thu),
            NANOS_IN_WEEK,
            "Invalid time dif thu"
        );
        assert_eq!(
            fri.nanos_till_next(DayOfWeek::Fri),
            NANOS_IN_WEEK,
            "Invalid time dif fri"
        );
        assert_eq!(
            sat.nanos_till_next(DayOfWeek::Sat),
            NANOS_IN_WEEK,
            "Invalid time dif sat"
        );
        assert_eq!(
            sun.nanos_till_next(DayOfWeek::Sun),
            NANOS_IN_WEEK,
            "Invalid time dif sun"
        );

        // checking we can reach any day within the next week
        assert_eq!(
            mon.nanos_till_next(DayOfWeek::Tue),
            NANOS_IN_DAY,
            "Invalid time dif mon-tue"
        );
        assert_eq!(
            mon.nanos_till_next(DayOfWeek::Wed),
            NANOS_IN_DAY * 2,
            "Invalid time dif mon-wed"
        );
        assert_eq!(
            mon.nanos_till_next(DayOfWeek::Thu),
            NANOS_IN_DAY * 3,
            "Invalid time dif mon-thu"
        );
        assert_eq!(
            mon.nanos_till_next(DayOfWeek::Fri),
            NANOS_IN_DAY * 4,
            "Invalid time dif mon-fri"
        );
        assert_eq!(
            mon.nanos_till_next(DayOfWeek::Sat),
            NANOS_IN_DAY * 5,
            "Invalid time dif mon-sat"
        );
        assert_eq!(
            mon.nanos_till_next(DayOfWeek::Sun),
            NANOS_IN_DAY * 6,
            "Invalid time dif mon-sun"
        );
    }
} The test is very simple: take a bunch of known weekdays by their dates; make sure, that it is always an exact amount of nanoseconds between these weekdays; make sure, that it is always an exact amount of nanoseconds between Monday and other days. By the way, time constants are defined like this: // common.rs

pub const NANOS_IN_DAY: u64 = 1_000_000_000 * 60 * 60 * 24;
pub const NANOS_IN_WEEK: u64 = NANOS_IN_DAY * 7; Using ic-cron So now we need to define a function that a user will use in order to ask a canister to greet them every defined weekday: // actor.rs

implement_cron!();

#[update]
pub fn greet_each(weekday: DayOfWeek, name: String) -> TaskId {
    cron_enqueue(
        name,
        SchedulingInterval {
            delay_nano: time().nanos_till_next(weekday),
            interval_nano: NANOS_IN_WEEK,
            iterations: Iterations::Infinite,
        },
    )
    .expect("Unable to enqueue a new cron task")
} Notice that we use macro here. This macro initializes the state of ic-cron for our canister and also extends it with functions we use (like ). implement_cron!() cron_enqueue() Because we already did a good job understanding how works internally, we won’t stop at it again right now. We pass a users name as a here, in order to use it later while greeting. cron_enqueue() payload We almost did it. All we have left is to process all the scheduled tasks inside special system function that is annotated with macro. This function gets executed each consensus round automatically. #[heartbeat] // actor.rs

#[heartbeat]
pub fn tick() {
    for task in cron_ready_tasks() {
        let name: String = task.get_payload().expect("Unable to deserialize a name");

        print(format!("Hello, {}", name).as_str());
    }
} Inside it, we just get the name of the user and print “Hello, <username>” message to the console. This tutorial keeps it simple, but instead of printing to the console you can do any kind of stuff here: from writing something into the state to interacting with remote canisters. This is it! I hope the tutorial was helpful. Complete source code (with a couple of additional functions) is located in this repo: https://github.com/seniorjoinu/ic-cron-time-alignment

How to Execute Background Tasks on Particular Weekdays with IC-Cron and Chrono

Tutorial: Extending Sonic With Limit Orders Using ic-cron Library

The content covered in this article is based on the DFINITY Canister SDK, which differs from the NNS system in that they have a different account system. The Internet Computer blockchain enables multiple computers to operate as one very powerful virtual machine. The computers that make up a virtual machine are organized into subnetworks, each of which is a blockchain consisting of a certain number of independent machines (peer-connected computers called nodes) that run the software components of the Internet Computer protocol. The Internet computer software components running on each node are called replicas, and they replicate state and computation among all nodes in the subnetwork blockchain, and the core components of the replicas are organized into the following logical layers: A P2P network layer, which collects and publishes messages from users or other nodes in the current subnet or other subnets. The messages received by the network layer are replicated to all nodes in the current subnet. A consensus layer that creates input blocks by selecting and serializing messages received from users and different subnets, and notarizes and finalizes the blocks before they are passed to the message routing layer. A message routing layer for routing user- and system-generated block messages between subnets, managing the application's input and output queues and scheduling messages for execution. An execution environment for computing the deterministic calculations involved in executing the program and for processing messages received from the message routing layer. With Internet Computer, developers can focus on writing code using smart contracts without similar distractions associated with the environment, such as: Physical or virtual network configuration requirements Load balancing services Firewall, network topology or port management Database configuration and maintenance Storage volumes and devices Concept Actor: An actor is a special object in modern programming languages that handles messages in an isolated state, allowing them to be processed remotely and asynchronously. Usually, each canister contains the compiled code of an actor object. Each canister also contains some additional information, such as an interface description or front-end assets. It is possible to create projects containing multiple canisters, but each canister can only contain one Actor. A canister is an object with a common unique identifier similar to the concept of a smart contract that defines the owner of a specific application, service, or microsite. The canister encapsulates all programming logic, public entry methods, interface descriptions that provide message types, and state information for the application or service, or microservice. When calling functions by sending messages to the canister entry point, there are two types of calls: Query calls (non-committed query calls): allow calling functions that query the current state of the container or call functions that operate on the container state but do not change it. Has the following characteristics: Calls are synchronized and respond immediately. It can be made to any node that holds a canister and does not require consensus to verify the result. But there are security issues. Changes to the state of the canister are not allowed. The canister being called is not allowed to call functions of the inter-canister type of other canisters. Update calls (submit update calls): Allow calls to functions that change the state of a canister. Has the following characteristics. The call is asynchronous and responsive. Consensus must be passed to return the result. Changing the state of a container may take time because it requires two-thirds of the replicas in the subnet to agree on the result. The canister being called is allowed to call functions of the inter-canister type of other canisters. Controller is an identity with special privileges that are used to manage the canisters it controls. only the controller identity can be used to install, upgrade, or remove the canisters it controls. The controller identity can be specified using the principal identifier associated with the user or canister. The ledger Internet Computer records all transactions involving ICP tokens in an administrative canister called the ledger canister. ledger canister is a simplified parallel blockchain that runs in a subnet of Internet computers along with other network administrative canisters. The ledger canister implements a smart contract that holds accounts and balances and keeps a history of transactions that affect them. Recorded transactions are used to track specific events such as: Minting of ICP tokens. Transferring ICP tokens. Burning of ICP tokens. Principal: The first time you use the DFINITY Canister SDK, the dfx command line tool creates a default developer identity for you using the public/private key pair from the PEM file. The developer identity is represented by the derived principal data type and the text representing the principal, also known as the principal identifier. The developer identity can also be used to derive an account id (similar to a bitcoin or ethereum address) for holding ICP tokens in the ledger canister. Wallet: On Internet Computer, a wallet is an application dedicated to cycle. The wallet application is implemented as a canister and runs on an Internet computer. A wallet enables you to manage cycle balances, convert ICP tokens to cycles, and distribute cycles to your own or other users' canisters as a way to access or provide Internet services. When a canister needs to be created or manipulated, a wallet canister must be bound to the current subject identifier before the operation can take place. Smart contract: A smart contract is software that allows the execution of trusted transactions and agreements on a distributed, decentralized blockchain network without the need for any central authority or the legal system. With a smart contract, the terms of the transaction or agreement are written directly into lines of code that are executed on the blockchain network. The code controls execution and the transaction is tamper-proof, traceable, and irreversible. On Internet computers, smart contracts are deployed into canisters. WebAssembly WebAssembly (Wasm) is an underlying computer instruction format. Because WebAssembly defines a portable, open-standard binary format that can be clearly abstracted on most modern computer hardware, it is widely supported by programs running on the Internet. Programs written in Motoko are compiled into WebAssembly code for execution on a copy of an Internet computer. Replica: In the context of the Internet Computer Blockchain, replica refers to an Internet Computer process running on a physical computer node in the network. For the DFINITY Canister SDK, use the dfx start and dfx stop commands to start and stop replica processes locally, providing a local network for development. There are three accounts in IC as follows: identity: the identity account is the subject identifier, which can be mapped to the ICP account (account id) and the identity is the key to control the canister. ledger: The ledger account is the ICP account (account id), and all operations related to ICP are performed in the ledger. wallet: The wallet account is the canister where the cycle wallet program is deployed. identity must have the wallet set up to deploy the canister. Some of the account operations in the whole IC are as follows: DFX canister SDK is associated with a subject identity (principal identity) the first time it is used. The current principal identity can be obtained by using the command: dfx identity get-principal. Each principal identity derives an account id that is uniquely identified in the leger canister, similar to an address. use the command: dfx ledger account-id to obtain the current ICP address. The first canister is created using the leger canister and specifies the controller of the canister, into which the specified number of cycles will be deposited. use the command: dfx ledger --network ic create-canister tsqwz-udeik-5migd- ehrev-pvoqv-szx2g-akh5s-fkyqc-zy6q7-snav6-uqe --amount .25 creates a canister and specifies the controller body and the initialized cycles. The first created canister is empty and needs to be deployed to create a wallet canister. canister created. This canister is called the wallet canister. By default, after deploying a wallet, the wallet canister will be used as the current subject's cycle wallet. You can also set the current subject's cycle wallet with the following command: dfx identity --network ic set-wallet --force gastn-uqaaa-aaae-aaafq-cai After successful setting, the current identity uses the cycle wallet for canister operations. Once the current subject has a cycle wallet, it can use canister-related operations. For example, the command: dfx deploy --network ic deploys all canisters in the current project, and after the deployment is completed, the controller of these canisters is the current subject. Quick Start Local development Install nodejs and npm. Install dfx canister sdk. sh -ci "$(curl -fsSL )" https://sdk.dfinity.org/install.sh Create a new project. dfx new hello; cd hello; Start local network. dfx start Compile the project. npm install Deploy the canister. dfx deploy Network deployment Install nodejs and npm. Install dfx canister sdk. sh -ci "$(curl -fsSL )" https://sdk.dfinity.org/install.sh Create a new project. dfx new hello; cd hello; Start local network. dfx start Get the current subject identity. dfx identity get-principal Get the address of the current ICP account and transfer money to it. dfx ledger account-id Create a canister for the cycle wallet. dfx ledger --network ic create-canister <principal-identifier> --amount <icp-tokens> Deploy the cycle wallet application to the newly created canister. dfx identity --network ic deploy-wallet <canister-identifer> Compile the project. npm install Deploy the canister. dfx deploy Project structure# When the command dfx new hello is used, a directory with the following structure is created: hello/
├── README.md # default project documentation
├── dfx.json # project configuration file
├── node_modules # libraries for front-end development
├── package-lock.json
├── package.json
├── src # source files directory
│ ├── hello
│ │ └── main.mo
│ └── hello_assets
│ ├── assets
│ │ ├── logo.png
│ │ ├── main.css
│ │ └── sample-asset.txt
│ └── src
│ ├── index.html
│ └── index.js
└── webpack.config.js Among them: dfx.json is the configuration information for the whole project. package.json is the dependency and packaging information of the front-end project. The src directory holds the source files for the entire project. src/xxx/ holds the source files of the back-end project. The src/xxx_assets/ directory holds the source files of the front-end project. The appointment src/xxx_assets/assets/ holds the resource files of the front-end project. The appointment src/xxx_assets/src/index.html is the entry html file of the front-end project. The appointment src/xxx_assets/src/index.js is the JavaScript script that will be loaded automatically and uniquely for the front-end project. Dfx configuration file: When using the command dfx new hello, the dfx.json project configuration file with the following content will be created: {
    "canisters": {
        "hello": {
            "main": "src/hello/main.mo",
            "type": "motoko"
        },
        "hello_assets": {
            "dependencies": [
                "hello"
            ],
            "frontend": {
                "entrypoint": "src/hello_assets/src/index.html"
            },
            "source": [
                "src/hello_assets/assets",
                "dist/hello_assets/"
            ],
            "type": "assets"
        }
    },
    "defaults": {
        "build": {
            "packtool": ""
        }
    },
    "dfx": "0.7.2",
    "networks": {
        "local": {
            "bind": "127.0.0.1:8000",
            "type": "ephemeral"
        }
    },
    "version": 1
} Where: canisters specify the canisters that the project needs to deploy. assets are the canister for the front-end type, and Motoko is the canister for the back-end type. For backend types, the main specifies its compilation entry file. For front-end types, frontend.entrypoint specifies the compilation entry file. This file and its js file with the same name will be in the directory dist/<canister_name>/ after compilation. For frontend types, the source specifies all the files that need to be deployed after compilation. For front-end types, dependencies are specified if there are back-end dependencies. networks specify the network information for the connection. The default setting binds the local Internet computer network to the localhost address 127.0.0.1 and port 8000. defaults specify some settings when programming in non-Motoko languages. Author: Leo Figure from: Developer Experience (DX) and the Internet Computer Also published here.

Introducing the Internet Computer Learning Experience

Cryptocurrencies are under wide public for placing an undue burden on the environment. Concerns that cryptocurrency — the primary application of technology — will have broad implications for environmental sustainability are undoubtedly warranted. , for example, is responsible for the estimated annual energy consumption of over 41 terawatt hours, a figure on par with the . The sustainability problems associated with Bitcoin are predicated upon the Proof-of-Work protocol it employs in order to verify transactions on the network. scrutiny blockchain Bitcoin total energy use of New Zealand Proof-of-Work, the methodology used to ensure the validity of the ledger’s transactions, demands that complex cryptographic puzzles be solved in order to mint a new block of transactions recorded on the digital ledger. A new block on the chain is minted once a cryptographic puzzle is successfully solved by a miner. This block incorporates the transactions that have been made and propagates them through the network. The miner responsible for minting each block is awarded with a predefined number of coins, as well as the fees associated with the transactions in the block. In a race to mint the next block and reap mining incentives, miners expend a great deal of energy in order to stay competitive. Successful mining justifies the costs associated with mining operations because miners are able to exchange their coins for fiat currency. In countries like China and Mongolia, where electricity costs are amongst the lowest in the world, full-scale mining operations are powered primarily by coal. The use of cheap energy sources is a driving contributor to climate change and environmental degradation. Furthermore, the fact that Bitcoin miners rely on power from the grid is troublesome because power sources are ultimately at the hands of governmental bodies and regulatory agencies that can decide to restrict energy supplies or impose tariffs on mining operations. A crackdown on energy consumption in China, for example, could prove to be a major hit for the price of Bitcoin. China has already taken staunch action in the face of cryptocurrencies by banning initial coin offerings and shutting down online exchanges. In the coming weeks and months, Chinese officials . plan to take actions to shut down domestic mining operations Even without government interference, mining for Bitcoin on its existing Proof-of-Work platform may eventually be unprofitable. Every four years, the token incentives for miners are halved. Between 2021 and 2024, miners are expected to receive just over six Bitcoins per block. After 2024, that figure will again be cut in half. With fewer mining incentives, fewer miners on the network will potentially mean increased vulnerabilities in network security and profound ramifications for the price of Bitcoin. As blockchain technology continues to evolve, achieving decentralized distributed consensus in an immutable way will remain a primary goal of new projects. These projects seek to effectively establish a record that is agreed upon by everyone. Third generation blockchain networks like are employing Proof-of-Stake, an environmentally-conscious alternative to the Proof-of-Work methodology, both as a means of reducing the computing power required to effectively mine a block and as an answer to the security problems posed by Proof-of-Work. A Proof-of-Stake consensus algorithm provides for mining opportunities in proportion to the amount of tokens held by a user on the network. This means that an individual who has a 10% stake in the network (ownership of 10% of the coins) is able to validate transactions in proportion to his or her stake. This miner can theoretically mine one tenth of the total number of blocks. Stakeholders, also known as validators, participate in a voting round in order to validate the next block of transactions. The weight of his or her “vote” is a function of the proportion of tokens he or she owns. Proof-of-Stake ensures the security of the network because it is in the interest of the miners to maintain the integrity of the digital ledger. Furthermore, Proof-of-Stake imposes penalties against those who want to rig the system. If someone does not live up to his or her role of validating the next block, the penalties include network confiscation of the validator’s staking wallet. This is because a coin cannot be used for transactions and held in stake simultaneously. DFINITY While these types of networks have not yet been widely tested, the Proof-of-Stake model is attractive and promising. It is substantially less computationally expensive than its Proof-of-Work counterpart, and addresses the economic and ecological costs of mining. When DFINITY and other third generation blockchains relying on Proof-of-Stake are deployed, the early advantages will include enhanced network security and improved energy efficiency. Improvements in the speed of blockchain consensus algorithms will also have broad implications for the varieties of applications that can be run on top of the network.

Why Proof-of-Stake is the Future of Blockchain Technology

The United Nations Development Programme (UNDP) has announced a partnership with the DFINITY Foundation. The collaboration, revealed on July 3rd, 2024, aims to leverage blockchain technology to implement the Universal Trusted Credentials (UTC) initiative. The UTC initiative, originally launched in cooperation with the Monetary Authority of Singapore (MAS), seeks to create a framework that will improve domestic financing access for Micro, Small, and Medium Enterprises (MSMEs). By implementing this system across multiple countries, the project aims to facilitate cross-border trade financing through enhanced trust in data provided by these businesses. UNDP's Marcos Neto, UN Assistant Secretary General and Director of the Bureau for Policy and Programme Support, emphasized the significance of this partnership. "This collaboration marks a crucial step in our efforts to advance digital inclusion and economic empowerment for MSMEs, starting in Cambodia," Neto stated. Blockchain Technology at the Core The DFINITY Foundation, known for developing the Internet Computer blockchain, will play a key role in this initiative. The foundation plans to utilize its decentralized compute platforms and digital identity solutions to develop and test a prototype for the UTC pilot in Cambodia. A central component of this effort will be the Internet Computer blockchain's decentralized identity solution, Internet Identity (II). This technology is expected to ensure secure storage and management of digital credentials, thereby enhancing the overall trust and reliability of the UTC system. While the initial pilot will focus on Cambodia, there are plans to expand the project to ten countries. This scaling could potentially have a significant impact on MSMEs worldwide, which often struggle to access traditional financial services. Dominic Williams, Chief Scientist and Founder of the DFINITY Foundation, highlighted the potential of this initiative. "MSMEs are the backbone of most economies. The UTC initiative represents a unique opportunity to bring transparency and increase inclusion within a financial system that often fails to cater to their needs," Williams noted. Analysis and Outlook This partnership between UNDP and the DFINITY Foundation represents a promising step towards addressing long-standing challenges faced by small businesses in accessing finance. By leveraging blockchain technology, the initiative has the potential to create a more transparent, secure, and accessible financial ecosystem for MSMEs. The use of decentralized identity solutions could prove particularly valuable in building trust across borders, potentially opening up new opportunities for international trade and expansion for small businesses. Moreover, the scalability of this project to multiple countries suggests that its impact could be far-reaching if successful. Overall, this collaboration exemplifies how international organizations and technology innovators can work together to address global development challenges. If successful, the UTC initiative could serve as a model for future projects aimed at leveraging advanced technologies to promote sustainable economic growth and financial inclusion. Don’t forget to like and share the story! Vested Interest Disclosure: This author is an independent contributor publishing via our business blogging program. HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR. The United Nations Development Programme (UNDP) has announced a partnership with the DFINITY Foundation . The collaboration, revealed on July 3rd, 2024, aims to leverage blockchain technology to implement the Universal Trusted Credentials (UTC) initiative. announced DFINITY Foundation The UTC initiative, originally launched in cooperation with the Monetary Authority of Singapore (MAS), seeks to create a framework that will improve domestic financing access for Micro, Small, and Medium Enterprises (MSMEs). By implementing this system across multiple countries, the project aims to facilitate cross-border trade financing through enhanced trust in data provided by these businesses. launched in cooperation UNDP's Marcos Neto, UN Assistant Secretary General and Director of the Bureau for Policy and Programme Support, emphasized the significance of this partnership. "This collaboration marks a crucial step in our efforts to advance digital inclusion and economic empowerment for MSMEs, starting in Cambodia," Neto stated. Blockchain Technology at the Core The DFINITY Foundation, known for developing the Internet Computer blockchain, will play a key role in this initiative. The foundation plans to utilize its decentralized compute platforms and digital identity solutions to develop and test a prototype for the UTC pilot in Cambodia. A central component of this effort will be the Internet Computer blockchain's decentralized identity solution, Internet Identity (II). This technology is expected to ensure secure storage and management of digital credentials, thereby enhancing the overall trust and reliability of the UTC system. While the initial pilot will focus on Cambodia, there are plans to expand the project to ten countries. This scaling could potentially have a significant impact on MSMEs worldwide, which often struggle to access traditional financial services. Dominic Williams, Chief Scientist and Founder of the DFINITY Foundation, highlighted the potential of this initiative. "MSMEs are the backbone of most economies. The UTC initiative represents a unique opportunity to bring transparency and increase inclusion within a financial system that often fails to cater to their needs," Williams noted. Analysis and Outlook This partnership between UNDP and the DFINITY Foundation represents a promising step towards addressing long-standing challenges faced by small businesses in accessing finance. By leveraging blockchain technology, the initiative has the potential to create a more transparent, secure, and accessible financial ecosystem for MSMEs. The use of decentralized identity solutions could prove particularly valuable in building trust across borders, potentially opening up new opportunities for international trade and expansion for small businesses. Moreover, the scalability of this project to multiple countries suggests that its impact could be far-reaching if successful. Overall, this collaboration exemplifies how international organizations and technology innovators can work together to address global development challenges. If successful, the UTC initiative could serve as a model for future projects aimed at leveraging advanced technologies to promote sustainable economic growth and financial inclusion. Don’t forget to like and share the story! Vested Interest Disclosure: This author is an independent contributor publishing via our business blogging program. HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR. Vested Interest Disclosure: This author is an independent contributor publishing via our business blogging program . HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR. Vested Interest Disclosure: business blogging program business blogging program

UNDP and DFINITY Test Blockchain Solution for MSME Financing

MSME অর্থায়নের জন্য UNDP এবং DFINITY টেস্ট ব্লকচেইন সলিউশন

UNDP und DFINITY testen Blockchain-Lösung zur Finanzierung von KMU

El PNUD y DFINITY prueban la solución Blockchain para el financiamiento de MIPYMES

Le PNUD et DFINITY testent la solution Blockchain pour le financement des MPME

यूएनडीपी और डीफिनिटी ने एमएसएमई वित्तपोषण के लिए ब्लॉकचेन समाधान का परीक्षण किया

UNDPとDFINITYが中小企業向け融資のためのブロックチェーンソリューションをテスト

MSME 금융을 위한 UNDP 및 DFINITY 테스트 블록체인 솔루션

PNUD e DFINITY testam solução Blockchain para financiamento de MPME

ПРООН и DFINITY тестируют блокчейн-решение для финансирования ММСП

UNDP ve DFINITY, MSME Finansmanı için Blockchain Çözümünü Test Ediyor

Giải pháp chuỗi khối thử nghiệm của UNDP và DFINITY dành cho tài chính của MSME

联合国开发计划署和 DFINITY 测试区块链解决方案以促进中小微企业融资

Decentralization is a dear topic to me. I believe decentralization is the future - a revolutionary technology that has the potential to change the way we use the Internet radically. This article compares two different approaches to decentralization; I call them 'flavors' - our implementation in the Decentralized web project and the one of the DFINITY project. Personally, I find the DFINITY approach pretty cumbersome. We, on the other hand, take a very minimalistic approach to decentralization. Besides comparing the technology, I did discover a 'little' secret of DFINITY, which I find troubling. At stake is democratizing of the Internet - either breaking up or extending current oligarchies in technology. The 'little' Secret On Friday, May 7th, 2021, the DFINITY project had a launch event live on YouTube. I find the presentation impressive, very professional, with many interviews and insights. However, it most likely cost tons of money to produce. A recording of the event is available on this link - One slide, on the mark of - 12:19 (12 mins 19 secs) is showing the partners of the DFINITY project. For copyright reasons, I do not want to include it as an image but just quote in text. The slide contains this statement - ...we have a team of engineers and researchers from world's leading technology organizations... and, the logos of 'who is who' of the world's tech oligarchs - Google, Facebook, Amazon, Apple, Microsoft, IBM, Intel, Samsung, oracle... Joining the tech oligarchs on the slide are Wall St. interests - namely Goldman Sachs. And, not to 'miss the boat' Uber hopped in that group too! So, that's the 'little' secret that slipped through the cracks - the oligarchs and monopolists of the current centralized internet together with Wall St. are trying to take over the upcoming decentralized internet as well. Fortunately, early or late, nature and society select the most efficient system. This is how the familiar to the Western world roman numeric system lost in dominance to the exotic but much more efficient Arabic numeric system. On the Identity Every decentralization implementation has to define the identity of the users. DFINITY project identifies new first-time users through submitting a fingerprint on a mobile phone or USB device which then assigns a number for the user. Although the name of the user is not typed the user surrenders their very sensitive personal information and potentially their privacy. Decentralized web project takes a different approach - minimalistic and privacy-preserving. It identifies new first-time users only by e-mail address and IP address. Comparing the Network Both decentralization projects aim to build a network of nodes. The vision of DFINITY is to have concentrated computing power centers in regions of the world. I was really curious about who is going to provide the computing centers. Having learned the 'little' secret of DFINITY, when having Amazon, Google, and Microsoft as partners, one does not need to possess psychic ability to guess who is going to provide it. For me it is a troubling aspect - partnering with the largest cloud computing providers and using their services is just going to be extending their dominance. Our vision of the building of a decentralized network of nodes is based on users running nonstop at home one of 2 choices of network devices. For more on our network of nodes please check . this article In the best-case scenario, the size of the DFINITY network of nodes will be several hundred, worldwide. In the best-case scenario, the size of the Decentralized web network of nodes will be in hundreds of millions, worldwide. On Network Applications Maybe it is a Swiss thing (having contributors from Switzerland) but naming a DFINITY network application a ' ' involves associations for me with chemical weapons. canister The word is probably ok to use in Switzerland but it may get the special attention of US government security agencies... Jokes aside, the approach of DFINITY is to require a developer who wants to deploy their decentralized app to convert from their preferred programming language to , which then is going to be deployed, converted to a binary, and then run in the 'canister'. Web-Assembly This approach is maybe ok for a simple program but may run into problems with a program using additional special libraries. All of these libraries have to be converted to web assembly as well. As mentioned above, one of the 2 choices in our project of decentralized bridge/node is raspberry pi, running at the home of a user of the decentralized web. Our current image of bridge/node includes natively - , , and pre-installed. A user who is also a developer can deploy a python, javascript, or a go program natively on their own bridge/node, or request deployment on other nodes/bridges. python node.js go-lang In addition, the bridge/node image includes a container program so that a developer can 'drop' a container with any other program on their own bridge/node, or request deployment on other nodes/bridges. docker Our approach to network apps avoids the issues of conversion in DFINITY, for example, converting a python program in web assembly and then from web assembly to binary, hoping the binary produced does not have issues while working. Comparing Communication One last, but probably the most important distinction - in the spirit of decentralization. The DFINITY project misses the fundamentals of enabling decentralization and relies on current centralized ways of communication. An example of a messaging network application deployed in a DFINITY 'canister' has all its users going through the same 'canister' to communicate with each other. Such a network app differs from the centralized facebook messenger app only in the lack of a domain name. Our decentralized web project favors direct user to user communication. One of the basics that users in our dWeb project need to understand is the outward and inward types of communication. Currently, the large majority of internet users communicate with outward only type of communication. But it is possible to break out of the confinement and enable outward + inward types of communication. Only through enabling 2 directional/outward + inward types of communication, we can achieve true decentralization. Conclusion Maybe I had to appeal to the sense of humor of the reader while reading - from the very beginning. The article is in no way disrespectful to another decentralization project, which like us is forging its unique path in technology development. As a developer myself in the Decentralized web project, I respect the efforts of the fellow developers of the DFINITY project. Finally, I did attempt to connect on LinkedIn with the chief scientist of the DFINITY project who appeared frequently in the launch event video. I hope he will be reading this article. Resources DINO (decentralized in name only) versus true decentralization You are welcome to connect with me on: - Discord https://discord.gg/Zwp3Vs65dk - LinkedIn https://www.linkedin.com/in/paul-arssov-arstech-com-biz-org

Decentralized Web vs DFINITY: Comparing 2 Decentralization Flavors 

Table of Links Abstract and 1. Introduction Abstract and 1. Introduction 2 Methodology 2 Methodology 3 Hardware 3 Hardware 4 Software 4 Software 5 Network 5 Network 6 Consensus 6 Consensus 7 Cryptocurrency Economics 7 Cryptocurrency Economics 8 Client API 8 Client API 9 Governance 9 Governance 10 Geography 10 Geography 11 Case Studies 11 Case Studies 12 Discussion and References 12 Discussion and References A. Decentralization and Policymaking A. Decentralization and Policymaking B. Software Testing B. Software Testing C. Brief Evaluations per Layer C. Brief Evaluations per Layer D. Measuring decentralization D. Measuring decentralization E. Fault Tolerance and Decentralization E. Fault Tolerance and Decentralization 3 Hardware The role of hardware in the potential decentralization of blockchain systems has been reported in various research works [187,43]. To be specific, by “hardware”, we refer to the machines that host and/or support the consensus software, which can be anything from personal computers to purpose-built devices. In many cases, the hardware is also provided as a service from cloud providers to consensus participants. To account for all possibilities, we segment this layer into two categories, namely “physical” and “virtual” hardware. Physical hardware. This category covers all hardware that is used directly by consensus participants. Bitcoin mining, and that of other Proof-of-Work (PoW) Physical hardware. Physical hardware. ledgers, started from regular CPUs, but quickly migrated to GPUs and, eventually, to dedicated devices (ASICs), which produce more hashes at a lower cost [163]. In the case of Proof-of-Stake (PoS) blockchains, participation is typically performed through generic hardware, although there are systems with particular requirements, which may restrict the compatible hardware options (an example such blockchain is The Internet Computer by Dfinity [56]). Some alternative schemes, such as certain forms of Proof-of-Useful-Work (PoUW) or Proof-of-Elapsed-Time (PoET) also make use of Trusted Execution Environments (TEEs) to guarantee higher security or efficiency levels [14]. When analyzing decentralization on this layer, the resource of interest is participating power (e.g., hashes per second or stake) and the relevant parties are the manufacturers of hardware products that are used for participating. That is, we consider a system to be decentralized in the hardware layer if the participating power is distributed across various pieces of equipment, manufactured by different entities. As demonstrated by the evolution of Bitcoin mining, one pathway to hardware centralization is the development and adoption of specialized machines that outperform generic equipment and provide an advantage to their operators. Nowadays, an overwhelming majority of block production in PoW blockchains comes from specialized hardware, despite the fact that PoW does not require specialized hardware in theory [163]. Notably, this trend has motivated significant research in “ASIC-resistance” and the development of PoW algorithms that attempt to facilitate better hardware diversity [19,64,149]. In other cases, strict or “non-typical” protocol requirements (e.g., the requirement for trusted hardware) reduce the pool of possible manufacturers that can support those systems, potentially leading to increased centralization. Concentration around few hardware manufacturers creates various hazards. Same-vendor products are more susceptible to collective faults, e.g., due to defective parts or hardware bugs. Such faults could result in sudden drops in the network’s power, lowering the threshold for gaining a computational majority (safety and liveness hazard) and slowing down block production, at least until the PoW parameters are recalculated (liveness hazard). Manufacturers could also introduce backdoors, threatening the ledger’s security and stability, albeit such hazards can possibly be mitigated via cryptographic techniques [7]. Virtual hardware. The emergence of mining data centers allowed for hashing power to be offered as a “cloud” service, effectively enabling miners to participate in block production without possessing their own hardware [121,165]. The advent of PoS protocols reinforced this trend towards “virtual” hardware, by decoupling Sybil resilience from physical requirements. In theory, this enables PoS nodes to run on generic hardware, e.g., even home equipment, but in practice, convenience often drives PoS users to employ cloud services, which offer uptime and connectivity guarantees that a DIY configuration cannot. This is exacerbated when PoS systems apply penalties to absent users and uptime guarantees become of utmost importance to guarantee profitability. Therefore, the resource of interest in this category is again participating power (either in the form of hashing power or stake) and the relevant parties are cloud providers. Virtual hardware. Virtual hardware. When nodes that control significant participating power are hosted by the same provider, significant hazards arise for all properties. First, the provider may have access to private keys and hence is able to create conflicting blocks (safety hazard) or deanonymize users (compromising privacy). Second, the provider controls the node’s network access, so it could prohibit communication (liveness hazard). Finally, it could also tamper with the system’s stability, e.g., increasing price volatility via targeted interference or even stealing user rewards. Authors:
(1) Christina Ovezik, University of Edinburgh (c.ovezik@ed.ac.uk);
(2) Dimitris Karakostas, University of Edinburgh (dkarakos@ed.ac.uk);
(3) Aggelos Kiayias, University of Edinburgh and IOG (akiayias@ed.ac.uk). Authors: Authors: (1) Christina Ovezik, University of Edinburgh (c.ovezik@ed.ac.uk); (2) Dimitris Karakostas, University of Edinburgh (dkarakos@ed.ac.uk); (3) Aggelos Kiayias, University of Edinburgh and IOG (akiayias@ed.ac.uk). This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv available on arxiv

Stories, News & Mentions about DFINITY

Categories

Trending Topics

Stories, News & Mentions about DFINITY

Dfinity’s Stories on HackerNoon

Dfinity's News & Mentions

Categories

Trending Topics