Reimagine fashion production supply chain for emerging brands

RE(SOURCE)

Cracking the Code of Organic Reach: A Startup's Guide to Sustainable Growth

Survey and Analysis of Smart Contract Quality Assurance: Conclusions, Acknowledgement and References

OpenCitations Meta: Methodology

OpenCitations Meta: পদ্ধতি

OpenCitations Meta: Methodik

Meta de OpenCitations: Metodología

Méta OpenCitations : Méthodologie

ओपनसाइटेशन्स मेटा: कार्यप्रणाली

OpenCitations メタ: 方法論

OpenCitations Meta: 방법론

OpenCitations Meta: Metodologia

Мета OpenCitations: методология

OpenCitations Metası: Metodoloji

OpenCites Meta: Phương pháp luận

OpenCitations Meta：方法论

This is about how a grocery store brand leverages the Cross-Cluster Replication (CCR) capability of Apache Doris to separate its data reading and writing workloads. In this case, where the freshness of data guarantees the freshness of groceries, Apache Doris uses Apache Doris as its data warehouse to monitor and analyze its procurement, sale, and stock in real-time for all its stores and supply chains. Why they need CCR A major part of the user's data warehouse (including the ODS, DWD, DWS, and ADS layers) is built within Apache Doris, which employs a micro-batch scheduling mechanism to coordinate data across the data warehouse layers. However, this is pressured by the burgeoning business of the grocery store brand. The data size they have to receive, store, and analyze is getting larger and larger. That means their data warehouse has to handle bigger data writing batches and more frequent data queries. However, task scheduling during query execution might lead to resource preemption, so any resource shortage can easily compromise performance or even cause task failure or system disruption. Naturally, the user thought of separating the reading and writing workloads. Specifically, they want to replicate data from the ADS layer (which is cleaned, transformed, aggregated, and ready to be queried) to a backup cluster dedicated to query services. This is implemented by the CCR in Apache Doris. It prevents abnormal queries from interrupting data writing and ensures cluster stability. Before CCR Before CCR was available, they innovatively adopted the Multi-Catalog feature of Doris for the same purpose. Multi-Catalog allows users to connect Doris to various data sources conveniently. It is actually designed for federated querying, but the user drew inspiration from it. They wrote a script and tried to pull incremental data via Catalog. Their data synchronization pipeline is as follows: They loaded data from the source cluster to the target cluster by regular scheduling tasks. To identify incremental data, they added a last_update_time field to the tables. There were two downsides to this. Firstly, the data freshness of the target cluster was reliant on and hindered by the scheduling tasks. Secondly, for incremental data ingestion, in order to identify incremental data, the import SQL statement for every table has to include the logic to check the last_update_time field; otherwise, the system just deletes and re-imports the entire table. Such requirements increase development complexity and data error rate. CCR in Apache Doris Just when they were looking for a better solution, Apache Doris released CCR in version 2.0. Compared to the alternatives they've tried, CCR in Apache Doris is: Lightweight in design: The data synchronization tasks consume very few machine resources. They run smoothly without reducing Apache Doris's overall performance.


Easy to use: It can be configured by one simple POST request.


Unlimited in migration: Users can raise the upper limit of the data migration capabilities in CCR by optimizing their cluster configuration.


Consistent in data: The DDL statements executed in the source cluster can be automatically synchronized into the target cluster, ensuring data consistency.


Flexible in synchronization: It is able to perform both full data synchronization and incremental data synchronization. To start CCR in Doris simply requires two steps. Step one is to enable binlogs in both the source cluster and the target cluster. Step two is to send the name of the database or table to be replicated. Then, the system will start synchronizing full or incremental data. The detailed workflow is as follows: In the grocery store brand's case, they need to synchronize a few tables from the source cluster to the target cluster, each table having an incremental data size of about 50 million rows. After a month's trial run, the Doris CCR mechanism is proven to be stable and performant: Higher stability and data accuracy: No replication failure has ever occurred during the trial period. Every data row is transferred and landed in the target cluster accurately.


Streamlined workflows:


Before CCR: The user had to write SQL for each table and write data via Catalog. For tables without a last_update_time field, incremental data synchronization can only be implemented by full-table deletion and re-import.


Insert into catalog1.db.destination_table_1 select * from catalog1.db.source_table1 where time > xxx
Insert into catalog1.db.destination_table_2 select * from catalog1.db.source_table2 where time > xxx
…
Insert into catalog1.db.destination_table_x select * from catalog1.db.source_table_x



After CCR: It only requires one POST request to synchronize an entire database.


curl -X POST -H "Content-Type: application/json" -d '{
    "name": "ccr_test",
    "src": {
    "host": "localhost",
    "port": "9030",
    "thrift_port": "9020",
    "user": "root",
    "password": "",
    "database": "demo",
    "table": ""
    },
    "dest": {
    "host": "localhost",
    "port": "9030",
    "thrift_port": "9020",
    "user": "root",
    "password": "",
    "database": "ccrt",
    "table": ""
    }
}' http://127.0.0.1:9190/create_ccr



Faster data loading: With CCR, it only takes 3~4 seconds to ingest a day's incremental data, as compared to more than 30 seconds with the Catalog method. As for real-time synchronization, CCR can finish data ingestion in 1 second without reliance on manual updates or regular scheduling. Conclusion Using CCR in Apache Doris, the grocery store brand separates reading and writing workloads into different clusters and thus improves overall system stability. This solution delivers a real-time data synchronization latency of about 1 second. To further ensure normal functioning, it has a real-time monitoring and alerting mechanism so any issue will be notified and attended to instantly, as well as a contingency plan to guarantee uninterrupted query services. It also supports partition-based data synchronization (e.g. ALTER TABLE tbl1 REPLACE PARTITION). With the demonstrated effectiveness of CCR, they are planning to replicate more of their data assets for efficient and secure data usage. CCR is also applicable when you need to build multiple data centers or derive a test dataset from your production environment. For further guidance on CCR, join the Apache Doris community. This is about how a grocery store brand leverages the Cross-Cluster Replication (CCR) capability of Apache Doris to separate its data reading and writing workloads. In this case, where the freshness of data guarantees the freshness of groceries, Apache Doris uses Apache Doris as its data warehouse to monitor and analyze its procurement, sale, and stock in real-time for all its stores and supply chains. Cross-Cluster Replication (CCR) Why they need CCR A major part of the user's data warehouse (including the ODS, DWD, DWS, and ADS layers) is built within Apache Doris, which employs a micro-batch scheduling mechanism to coordinate data across the data warehouse layers. However, this is pressured by the burgeoning business of the grocery store brand. The data size they have to receive, store, and analyze is getting larger and larger. That means their data warehouse has to handle bigger data writing batches and more frequent data queries. However, task scheduling during query execution might lead to resource preemption, so any resource shortage can easily compromise performance or even cause task failure or system disruption. Naturally, the user thought of separating the reading and writing workloads. Specifically, they want to replicate data from the ADS layer (which is cleaned, transformed, aggregated, and ready to be queried) to a backup cluster dedicated to query services. This is implemented by the CCR in Apache Doris. It prevents abnormal queries from interrupting data writing and ensures cluster stability. separating the reading and writing workloads. This is implemented by the CCR in Apache Doris. Before CCR Before CCR was available, they innovatively adopted the Multi-Catalog feature of Doris for the same purpose. Multi-Catalog allows users to connect Doris to various data sources conveniently. It is actually designed for federated querying, but the user drew inspiration from it. They wrote a script and tried to pull incremental data via Catalog. Their data synchronization pipeline is as follows: Multi-Catalog They loaded data from the source cluster to the target cluster by regular scheduling tasks. To identify incremental data, they added a last_update_time field to the tables. There were two downsides to this. Firstly, the data freshness of the target cluster was reliant on and hindered by the scheduling tasks. Secondly, for incremental data ingestion, in order to identify incremental data, the import SQL statement for every table has to include the logic to check the last_update_time field; otherwise, the system just deletes and re-imports the entire table. Such requirements increase development complexity and data error rate. last_update_time last_update_time CCR in Apache Doris Just when they were looking for a better solution, Apache Doris released CCR in version 2.0. Compared to the alternatives they've tried, CCR in Apache Doris is: Lightweight in design: The data synchronization tasks consume very few machine resources. They run smoothly without reducing Apache Doris's overall performance. Easy to use: It can be configured by one simple POST request. Unlimited in migration: Users can raise the upper limit of the data migration capabilities in CCR by optimizing their cluster configuration. Consistent in data: The DDL statements executed in the source cluster can be automatically synchronized into the target cluster, ensuring data consistency. Flexible in synchronization: It is able to perform both full data synchronization and incremental data synchronization. Lightweight in design: The data synchronization tasks consume very few machine resources. They run smoothly without reducing Apache Doris's overall performance. Lightweight in design : The data synchronization tasks consume very few machine resources. They run smoothly without reducing Apache Doris's overall performance. Lightweight in design Easy to use: It can be configured by one simple POST request. Easy to use : It can be configured by one simple POST request. Easy to use POST Unlimited in migration: Users can raise the upper limit of the data migration capabilities in CCR by optimizing their cluster configuration. Unlimited in migration : Users can raise the upper limit of the data migration capabilities in CCR by optimizing their cluster configuration. Unlimited in migration Consistent in data: The DDL statements executed in the source cluster can be automatically synchronized into the target cluster, ensuring data consistency. Consistent in data : The DDL statements executed in the source cluster can be automatically synchronized into the target cluster, ensuring data consistency. Consistent in data Flexible in synchronization: It is able to perform both full data synchronization and incremental data synchronization. Flexible in synchronization : It is able to perform both full data synchronization and incremental data synchronization. Flexible in synchronization To start CCR in Doris simply requires two steps. Step one is to enable binlogs in both the source cluster and the target cluster. Step two is to send the name of the database or table to be replicated. Then, the system will start synchronizing full or incremental data. The detailed workflow is as follows: In the grocery store brand's case, they need to synchronize a few tables from the source cluster to the target cluster, each table having an incremental data size of about 50 million rows. After a month's trial run, the Doris CCR mechanism is proven to be stable and performant: Higher stability and data accuracy: No replication failure has ever occurred during the trial period. Every data row is transferred and landed in the target cluster accurately. Streamlined workflows:


Before CCR: The user had to write SQL for each table and write data via Catalog. For tables without a last_update_time field, incremental data synchronization can only be implemented by full-table deletion and re-import.


Insert into catalog1.db.destination_table_1 select * from catalog1.db.source_table1 where time > xxx
Insert into catalog1.db.destination_table_2 select * from catalog1.db.source_table2 where time > xxx
…
Insert into catalog1.db.destination_table_x select * from catalog1.db.source_table_x



After CCR: It only requires one POST request to synchronize an entire database.


curl -X POST -H "Content-Type: application/json" -d '{
    "name": "ccr_test",
    "src": {
    "host": "localhost",
    "port": "9030",
    "thrift_port": "9020",
    "user": "root",
    "password": "",
    "database": "demo",
    "table": ""
    },
    "dest": {
    "host": "localhost",
    "port": "9030",
    "thrift_port": "9020",
    "user": "root",
    "password": "",
    "database": "ccrt",
    "table": ""
    }
}' http://127.0.0.1:9190/create_ccr Faster data loading: With CCR, it only takes 3~4 seconds to ingest a day's incremental data, as compared to more than 30 seconds with the Catalog method. As for real-time synchronization, CCR can finish data ingestion in 1 second without reliance on manual updates or regular scheduling. Higher stability and data accuracy: No replication failure has ever occurred during the trial period. Every data row is transferred and landed in the target cluster accurately. Higher stability and data accuracy : No replication failure has ever occurred during the trial period. Every data row is transferred and landed in the target cluster accurately. Higher stability and data accuracy Streamlined workflows: Before CCR: The user had to write SQL for each table and write data via Catalog. For tables without a last_update_time field, incremental data synchronization can only be implemented by full-table deletion and re-import. Insert into catalog1.db.destination_table_1 select * from catalog1.db.source_table1 where time > xxx
Insert into catalog1.db.destination_table_2 select * from catalog1.db.source_table2 where time > xxx
…
Insert into catalog1.db.destination_table_x select * from catalog1.db.source_table_x After CCR: It only requires one POST request to synchronize an entire database. curl -X POST -H "Content-Type: application/json" -d '{
    "name": "ccr_test",
    "src": {
    "host": "localhost",
    "port": "9030",
    "thrift_port": "9020",
    "user": "root",
    "password": "",
    "database": "demo",
    "table": ""
    },
    "dest": {
    "host": "localhost",
    "port": "9030",
    "thrift_port": "9020",
    "user": "root",
    "password": "",
    "database": "ccrt",
    "table": ""
    }
}' http://127.0.0.1:9190/create_ccr Streamlined workflows: Streamlined workflows: Before CCR: The user had to write SQL for each table and write data via Catalog. For tables without a last_update_time field, incremental data synchronization can only be implemented by full-table deletion and re-import. Before CCR: The user had to write SQL for each table and write data via Catalog. For tables without a last_update_time field, incremental data synchronization can only be implemented by full-table deletion and re-import. Before CCR : The user had to write SQL for each table and write data via Catalog. For tables without a last_update_time field, incremental data synchronization can only be implemented by full-table deletion and re-import. Before CCR last_update_time Insert into catalog1.db.destination_table_1 select * from catalog1.db.source_table1 where time > xxx
Insert into catalog1.db.destination_table_2 select * from catalog1.db.source_table2 where time > xxx
…
Insert into catalog1.db.destination_table_x select * from catalog1.db.source_table_x Insert into catalog1.db.destination_table_1 select * from catalog1.db.source_table1 where time > xxx
Insert into catalog1.db.destination_table_2 select * from catalog1.db.source_table2 where time > xxx
…
Insert into catalog1.db.destination_table_x select * from catalog1.db.source_table_x After CCR: It only requires one POST request to synchronize an entire database. After CCR: It only requires one POST request to synchronize an entire database. After CCR : It only requires one POST request to synchronize an entire database. After CCR POST curl -X POST -H "Content-Type: application/json" -d '{
    "name": "ccr_test",
    "src": {
    "host": "localhost",
    "port": "9030",
    "thrift_port": "9020",
    "user": "root",
    "password": "",
    "database": "demo",
    "table": ""
    },
    "dest": {
    "host": "localhost",
    "port": "9030",
    "thrift_port": "9020",
    "user": "root",
    "password": "",
    "database": "ccrt",
    "table": ""
    }
}' http://127.0.0.1:9190/create_ccr curl -X POST -H "Content-Type: application/json" -d '{
    "name": "ccr_test",
    "src": {
    "host": "localhost",
    "port": "9030",
    "thrift_port": "9020",
    "user": "root",
    "password": "",
    "database": "demo",
    "table": ""
    },
    "dest": {
    "host": "localhost",
    "port": "9030",
    "thrift_port": "9020",
    "user": "root",
    "password": "",
    "database": "ccrt",
    "table": ""
    }
}' http://127.0.0.1:9190/create_ccr Faster data loading: With CCR, it only takes 3~4 seconds to ingest a day's incremental data, as compared to more than 30 seconds with the Catalog method. As for real-time synchronization, CCR can finish data ingestion in 1 second without reliance on manual updates or regular scheduling. Faster data loading : With CCR, it only takes 3~4 seconds to ingest a day's incremental data, as compared to more than 30 seconds with the Catalog method. As for real-time synchronization, CCR can finish data ingestion in 1 second without reliance on manual updates or regular scheduling. Faster data loading 3~4 seconds Conclusion Using CCR in Apache Doris, the grocery store brand separates reading and writing workloads into different clusters and thus improves overall system stability. This solution delivers a real-time data synchronization latency of about 1 second. To further ensure normal functioning, it has a real-time monitoring and alerting mechanism so any issue will be notified and attended to instantly, as well as a contingency plan to guarantee uninterrupted query services. It also supports partition-based data synchronization (e.g. ALTER TABLE tbl1 REPLACE PARTITION ). With the demonstrated effectiveness of CCR, they are planning to replicate more of their data assets for efficient and secure data usage. ALTER TABLE tbl1 REPLACE PARTITION CCR is also applicable when you need to build multiple data centers or derive a test dataset from your production environment. For further guidance on CCR, join the Apache Doris community . Apache Doris community

Streamlining Data Operations: How a Grocery Chain Optimizes Workloads with Apache Doris

9 Common Technical SEO Issues and How to Fix Them - Beginners' Guide

What Exactly is a Smart Contract? First introduced in the Ethereum blockchain, smart contracts are a fundamental building block of Web3 and a vital part of the blockchain’s advanced capabilities. They form the foundation for decentralized applications and automated business transactions by creating a level playing field of trust, authority, and authenticity that is already proving to be a paradigm shift in many industries today. Here, we take a look at what smart contracts are, how they work, and the opportunities they unlock for your business. We're going to analyze how they can be used to automate everything from internal business logic to programmable assets, transactions, and tokens. Most importantly, we're going to look at their benefits and limitations, how they're already being used today, and how they're going to evolve in the next few years. A is code hosted and executed on a blockchain network designed to execute a transaction when a set of predetermined conditions are met. Most often, it acts as an automated intermediary that will release funds, create tickets, or ship goods when all parties have met their obligations. In this use case, they answer the questions raised by eliminating third-party intermediaries from transactions and provide an accurate, fast, and tamper-proof way to exchange goods and funds. smart contract More broadly, smart contracts can be used to run any piece of code according to any external conditions at all. For example, they are becoming increasingly important in fields such as health care and logistics to maintain accurate records and updates with no possibility for tampering and fraud at their source. Smart contracts are a game-changing innovation in fields such as finance, health, and logistics because they have no central administrator or single attack vector for malicious parties to interfere with. There can be as many stipulations or requests baked into a smart contract as needed to meet everyone's demands before releasing funds, issuing tickets, or conducting a transaction. Whenever these conditions are met, a smart contract updates the blockchain with the finalized transaction, making the resulting ledger tamper-proof by design. When applied to multi-party digital agreements, smart contracts reduce the risks for all parties, increase efficiency, and provide a level of transparency that changes how we work with business transactions. Creating Smart Contracts As we've defined here, smart contracts are just pieces of code that happen to run on the blockchain. Like any other kind of code, there are about as many languages, conventions, and tools as there are developers available to write smart contracts. Etherium's is still the most popular by far, launching with the blockchain in 2015. However, there are many others worth mentioning for any new use cases you might have for your smart contracts. Solidity These include: . Another language for building Ethereum smart contracts. Vyper is designed to be more secure and easier to maintain than Solidity. In contrast, it has a smaller community and fewer resources to lean on. Vyper . Well-known and highly appreciated as a general-purpose language, Rust has exceptional resources and tooling for working in the blockchain space. Rust . The popularity and use of these languages within blockchain applications show blockchain as an evolution of tried and tested technologies rather than an intimidating shift to computing as we know it. C/C++ . Known for being simple, efficient, and in a league of its own when working with concurrency — Go is an excellent choice for building new kinds of applications using blockchain technologies. Go (GoLang) Any developer can create their smart contracts to deploy to a public blockchain using any language or tool they choose. Some of the most lucrative examples might include a personal yield aggregator that transfers funds to the highest-earning application to maximize returns. As with the rest of the blockchain, there's no authority or gatekeeper barring entry from the resource. A simple smart contract to manage product sales in Solidity might look something like this: pragma solidity 0.8.7;

contract SimpleSale {

    // Declare state variables
    address public owner;
    mapping (address => uint) public inventoryBalance;

    // When 'SimpleSale' contract is deployed:
    // 1. set the deploying address as the owner of the contract
    // 2. set the deployed smart contract's inventoryBalance to 100
    constructor() {
        owner = msg.sender;
        inventoryBalance[address(this)] = 100;
    }

    // Allow the owner to increase the smart contract's inventory
    function refillInventory(uint amount) public {
        require(msg.sender == owner, "Only the owner can refill.");
        inventoryBalance[address(this)] += amount;
    }

    // Allow anyone to purchase producrs
    function purchase(uint amount) public payable {
        require(msg.value >= amount * 1 ether, "You must pay at least 1 ETH per product");
        require(inventoryBalance[address(this)] >= amount, "Not enough inventory in stock");
        inventoryBalance[address(this)] -= amount;
        inventoryBalance[msg.sender] += amount;
    }

} As a trivial example, this smart contract demonstrates how the technology can be used to automate transactions and replace intermediaries in almost any industry. Many smart contracts involve multiple independent parties that have a very limited relationship and even less trust. The smart contract they use to interact will define exactly how, when, and where each party can interact with the transaction and what the results will be for any given input. This creates a multi-party digital agreement that executes automatically when everyone involved in the transaction has met the right conditions. Smart Contracts in Action Some key uses of smart contracts involve automating business processes and transactions between several entities. This means they can automate payments, process flow, and dispute resolutions to create highly efficient processes that minimize time, risk, and costs to every business. For example, a smart contract that governs global supply and trade might have just a couple of simple terms such as: If the product arrives on time, execute payment from retailer to supplier in the full amount. Condition 1: If the product arrives late, then execute partial payment from the retailer to the supplier for 95% of the full amount. Condition 2: Of course, this is a simplified trivial example but there are any number of supplier and customer relationships that can benefit from this technology without relying on intermediate payment processors. Another type of smart contract utilizes decentralized applications that provide interaction across the board without explicitly setting up permissions. Public distributed apps are typically open-source code that can be widely scrutinized to avoid any security concerns. One example of this type of application is a lending/borrowing market that works on the following terms: If a user deposits collateral into a specific smart contract, they will be issued a loan for some value of their posted collateral. Term 1: If the user’s collateralization ratio (collateral/outstanding loan value) drops below 200%, then the user’s collateral is automatically liquidated and transferred to the lender. Term 2: Lenders can deposit funds into a specific contract that other users can borrow from at predefined collateralization ratios, while the lender receives a claim to a portion of the interest rate payments. Term 3: Using these automated methods creates a fair and transparent method of lending that doesn't rely on a third party or central authority with a monopoly on terms and conditions. What this means in practice is that well-designed smart contracts can eliminate counterparty risk, and make it impossible for either party to renege on the terms of a deal, or fail to fulfill their contractual obligations. However, smart contracts are open instead to another kind of risk. Smart contract risk introduces the possibility that the code defining the contract has an inherent flaw or exploit that leads to undesirable outcomes. To guard against this, smart contracts have to be carefully looked over and well-understood by all parties before proceeding with the agreed-upon transaction. Benefits and Limitations to Smart Contracts Smart contracts offer a safer and more verifiable way of creating, maintaining, and upholding agreements in both B2B and B2C spaces. They offer data security and guarantees that can't be made any other way — creating something of a paradigm shift to come. However, the blockchain landscape is still relatively new for many, and smart contracts have yet to be proven at the kind of scale we're used to associating with high degrees of trust and authority. In short, we've still to get to know them fully to understand the risks and advantages they bring to a project. So let's take a look at what they can deliver into the project today and what we should currently guard against before we begin using them. Benefits of Smart Contracts When the conditions of a smart contract are met it is executed immediately without question. By shifting to an automated digital way of working there's no processing time (or fees), time spent checking, fixing, and re-issuing after errors, and nothing is ever lost or broken through manual processing. Speed, efficiency, and accuracy. Without the need to bring a third party into the transaction and an encrypted public record is shared — there's no question over whether documents have been altered or truncated at any stage in the process. Trust and Transparency. Blockchain records are public, shared, and immutable, meaning they can't be changed after the fact and have no single point of weakness. Each record in the chain is connected and verified by the last, making it impossible to change past transactions for malicious gain. Security. Smart contracts don't need intermediaries to execute so there are no fees or costs for handling or verification. As a result, smart contracts are the cheapest and fastest way to handle transactions. Cost-Effective. Limitations of Smart Contracts The strongest security feature of a smart contract is also one of its biggest limitations. By being immutable, any bugs or problems in the code can't be changed at any time after the contract has been issued. Any changes in external conditions or demands of the business can only ever be reflected in a new smart contract. Immutability. It's crucial that all parties involved in a smart contract understand its conditions and know how to scrutinize it. Bugs, whether introduced innocently or maliciously, can have severe consequences when executed. Every party on the contract needs to know how the code works and what it's going to do when executed. Complexity. Most smart contracts rely on external data for their preconditions. However, this data isn't accessible directly on the blockchain. Smart contracts have to rely on external services (oracles) to retrieve information outside the blockchain — introducing an element of third-party trust, reliability, and verification into some smart contracts. Oracle Dependency. Five Key Applications for Smart Contracts In truth, we're only just scratching the surface of what smart contracts can provide for organizations in the future. The creativity, innovation, and capabilities of developers can always be depended on to push the boundaries ever further to build ever more capable solutions to everyday business challenges. Five of the most innovative ways smart contracts are being used in organizations right now include: 1. Decentralised Finance (DeFi) Smart contracts enable decentralized lending, borrowing, and trading without the need for intermediaries within the transaction. There are already a host of DeFi platforms like and set up to allow decentralized transactions using smart contracts today. Compound aave 2. Insurance One of the largest and most profitable industries that smart contracts could revolutionize overnight is insurance. Smart contracts can automatically asses external conditions using known sources and trigger automated payouts or resolve accounts according to the terms of the agreement. The efficiency and guarantees smart contracts can provide for insurance products may well prove to overhaul the industry. 3. Supply Chain Management In contrast, smart contracts can make some of the biggest impacts in logistics. By enabling transparency and accurate accounting in supply chains, smart contracts can provide a level of oversight and tracking otherwise unheard of. Many logistics companies are already using them to track goods from production to distribution with a proven record of cutting down loss and fraud in real-world use. 4. Accurate Admin One of the largely unsung applications of smart contracts is their ability to securely store and manage data over the long term. Unlike traditional methods of increasing data security, smart contracts make data more accessible, easier to access, and more secure at the same time. In fields such as health tech, this has the power to be truly revolutionary by allowing patients both better access and security over highly confidential data. 5. Identity Management Smart contracts are ideal digital custodians to ensure the integrity of confidential information. This is critically important in maintaining and proving your identity, particularly on the web. Smart contract features such as selective disclosure, blockchain verification, and its in-built privacy by design are a paradigm shift in how we manage our online and in-person identities that will shift control of our identities from third-party organizations back to the individual. Learning Smart Contracts As one of the cornerstones of Web 3, smart contracts are set to revolutionize the way you conduct transactions and agreements in every context. The first step to reaching these capabilities is understanding exactly what they are, how to use them, and the way they work in business today. There's little doubt that they will continue to evolve and change over time as blockchain, web3, and future technologies become increasingly relevant within modern business. Understanding these technologies on the ground floor is a great first step towards innovating with them sooner, faster, and more effectively than the competition.

Smart Contracts: What They Are and How They Revolutionize Business

This paper is available on arxiv under CC 4.0 license. Authors: (1) Ayei E. Ibor, Trustworthy Digital Infrastructure for Identity Systems, The Alan Turing Institute, United Kingdom; (2) Mark Hooper, Trustworthy Digital Infrastructure for Identity Systems, The Alan Turing Institute, United Kingdom; (3) Carsten Maple, Trustworthy Digital Infrastructure for Identity Systems, The Alan Turing Institute, United Kingdom; (4) Gregory Epiphaniou, WMG, University of Warwick, United Kingdom. Table of Links Abstract & Introduction Background Review of Literature Methodology Discussion of Findings Conclusion and Future Work & References 5. Discussion of Findings The limitations of the current interoperability solutions, that is, eIDAS and X-Road show that there is a plethora of issues and complexities, which are yet to be addressed to achieve interoperability at the foundational level of identity management. Country-specific legislation and vendor-locked systems in developing countries add to these complexities. From the findings, the main limitations of the current interoperability solutions can be summarised as follows: i. Each registry implements its interfaces independently based on the use of a proprietary protocol equivalent to the technology in use. This results in the implementation of new interfaces, sometimes from scratch for new or evolving services. ii. There are different trust levels based on the implemented security architecture for verifying the integrity and authenticity of the data. iii. Incompatible certification authorities arise from different trust levels and legal systems of the trust service providers. iv. Interoperability is based on the signing of bilateral agreements, which are non-trivial and can result in several discrepancies in regulations and policies. v. There is no provision that the network must be accessible to private entities and as such may build inter-government competition on trust services e.g., eIDAS. vi. There is differentiation in notified eID schemes and authentication mechanisms leading to re-identification for public services, healthcare, or financial transactions e.g., eIDAS. These limitations imply that the interoperability of identity systems requires open standards with strong legal, regulatory, and governance structures. Also, there must be mechanisms to mitigate risks to the security and privacy of identification data including consent considerations for data use or sharing by the ID holder as outlined in Alamillo et al. (2023) and Srinivas, Das and Kumar (2019). From the findings, developing countries must also make provisions for a single, consolidated, and standardized view of civil registrations and identification data that constitute a single source of truth. This will enhance the onboarding of citizens and create a robust verification and validation process that does not require several levels of authentication that may increase the overhead of the identity system. Additionally, findings showed that the standardization of the structure and attributes of identity data such as name, date of birth, email, and several other relevant attributes to conform with the W3C recommendation should be a key consideration for interoperability. Enforcing the unicity and singularity of identification data will also ensure that ID holders do not have multiple identities that can hamper interoperability. Similarly, to enable the secure exchange of data or identity assertions, it was also found that developing countries must establish trust relationships through federation protocols that can foster interoperability. Interoperability portrays tremendous benefits to e-Government. We found that interoperability widens the dimensions of e-Government in cross-border identity management and data services. It also helps to provide open and accessible digital public services including systems and processes that allow people to move freely within the developing countries while also utilising public services outside their country of origin. Interoperability also helps to create sustainability, and economies of scale as demonstrated by X-Road and eIDAS (Hoffmann and Solarte-Vasquez, 2022; McBride et al., 2019; Schmidt and Krimmer, 2022). We found that while X-Road provides trustworthy data exchange using security servers that allow its members to communicate directly, it does not perform the verification and validation of the identification data that is part of the data exchange. There are also concerns about the limited amount of notified eID schemes under eIDAS, which builds on the limited scope of the eID schemes and the lack of relevant public services. These concerns underpin the need for the review of these interoperability solutions to underscore the notion of cross-border verification and validation of identification data for seamless data exchange. Building on the evidence from various sources as discussed in the Literature, an architecture for trustworthy cross-border interoperability is proposed in this work. This architecture is represented in Figure 4. From Figure 4, each citizen or prospective ID holder undergoes identity enrolment, which can include civil registration through online or offline capture procedures. The enrolment of the citizen is based on regulations and standards of the foundational identity system of the issuing country represented in Figure 4 as 𝑁𝐼𝐷𝑆௫. At the issuance of the ID credential, the citizen or ID holder presents such a document for establishing and proofing his/her identity to a requesting service provider, identity provider or relying party. Authentication and authorisation services are then used to complete the identity proofing process to allow an ID holder access to a service or resource at the point of access. In a cross-border use case, where a foundational identity system 𝑁𝐼𝐷𝑆௫ communicates with another system, say, in a federated identity ecosystem 𝐹𝑒𝑑ூ஽, or where an ID holder 𝑈ூ஽ requests for a service from the latter, then the processes of verifying and validating the identity of 𝑈ூ஽ should be an integral component of an interoperable identity system unlike in X-Road where such processes are the functions of the service provider/consumer. Verification and validation ensure that the claimed identity is true and belongs to the claimant at the time of the request and throughout service delivery. To achieve this, there is the need to have a trustworthy link that considers the representation of the data, semantics, binding, and the security and privacy of the identification data of 𝑈ூ஽. The relevance of the trust link at the interoperable layer is to ensure that the identity data as well as the requested resource or service maintains its integrity, security, privacy, and confidentiality throughout data exchange. We propose that the representation of the identification data must be data format agnostic as obtainable in X-Road using simple object access protocol (SOAP) and representational state transfer (REST) (Halili and Ramadani, 2018; Krimmer et al., 2021; Priisalu and Ottis, 2017). Also, the representation of credentials on the Web should be in a way that is machineverifiable, private, and cryptographically secure. The semantic interpretation of ID credentials must be unambiguous. That is, verifying credentials and presentations and cryptographically securing them both require predictable, bi-directional, and lossless processes. To be processed in an interoperable manner, any verification of a credential or presentation must be deterministic. The resulting credential or presentation must be semantically and syntactically equivalent to the original construct (Sedlmeir et al., 2021; W3C Recommendation, 2022). Likewise, each verified credential of 𝑈ூ஽ must be bound to its identity to a given level of assurance. This establishes an unbreakable link between the subject (𝑈ூ஽) and the credential to enforce identity disambiguation. Binding is relevant for the verification and validation of the claimed identity at cross-border entry/exit points. Finally, the security and privacy of the identification data are significant as it forms the integral component of the required trustworthiness for interoperability. There are several approaches for implementing the security and privacy of identification data such as the use of Transport Layer Security (TLS), Security Assertion Markup Language (SAML), authentication keys, etc. (for security), secure computation mechanisms, trusted third party, differential privacy, etc. (for privacy) (Grassi, Garcia and Fenton, 2017; Kaaniche, Laurent and Belguith, 2020). We posit that the use of secure computation mechanisms, data minimisation, and differential privacy in a cross-border context can fulfil the required privacy requirements due to the multifaceted risks associated with the exchange of data between interoperating entities. This paper is available on under CC 4.0 license. Arxiv

A Trustworthy Cross-Border Interoperable Identity System: What Our Findings Mean

Overview According to statistics, there were 34 funding rounds executed in the global blockchain market from February 19 to February 25, totaling 240.81 million dollars. The number of funding rounds increased by 13 and the amount of funds increased by 75.7%, compared with the previous week. The number of funding rounds in sectors of Infrastructure and DeFi is the highest, 11 of which are in the infrastructure and 7 in the DeFi area. The funds raised in the infrastructure sector are the highest, which is 170 million dollars. Funding in different sectors Infrastructure EigenLayer Round Series B Amount $100M Investors a16z, Polychain… Project Intro: EigenLayer is a protocol built on Ethereum that introduces restaking, a new primitive in cryptoeconomic security. This primitive enables the rehypothecation of ETH on the consensus layer. Users who stake ETH can opt-in to EigenLayer smart contracts to restake their ETH and extend cryptoeconomic security to additional applications on the network. Part of EigenLayer's potential lies in its ability to aggregate and extend cryptoeconomic security through restaking, and to validate new applications being built on top of Ethereum. AltLayer Round Strategic Amount $14.4M Investors Polychain, Hack VC… Project Intro: AltLayer is a system of highly scalable, application-dedicated execution layers that derive security from an underlying L1/L2. It is designed as a modular and pluggable framework for a multi-chain and multi-VM world. At its core, AltLayer consists of several optimistic rollup-like execution layers called flash layers, featuring a novel innovation that makes them disposable and thus highly resource-optimized. Flare Network Round / Amount $35M Investors DWF Labs Project Intro: Flare is a Layer-1 blockchain that enables secure, universal interoperability between chains, scaling blockchain use by allowing all digital assets and on-chain information to flow freely. Its consensus protocol for external data allows decentralized applications on Flare to safely and trustlessly acquire and use information from other blockchains and real-world data sources, solving the oracle problem and ushering in a new era of utility. Clave Round Pre-Seed Amount $1.6M Investors zkSync Labs Clave is an easy-to-use non-custodial smart wallet powered by Account Abstraction and the Hardware Elements (e.g Secure Enclave, Android Trustzone etc.), offering a unique onboarding process. Helius Round Series A Amount $9.5M Investors Foundation Capital, Reciprocal Ventures Helius aims to help creators overcome these obstacles by providing APIs (or application programming interfaces) to understand on-chain data and query transactions, as well as webhooks that enable automations and bots, plus RPC nodes that allow Solana apps to interact with the blockchain. All in all, they are designed to simplify complexity and facilitate application development. NodeShift Round Seed Amount $3.2M Investors Inovo VC NodeShift is a decentralized cloud service provider that provides a single API for accessing independent data center operators' redundant compute, storage and graphics accelerators and connecting to low-cost decentralized web services such as Akash and Filecoin. BEVM Round / Amount / Investors ViaBTC Capital BEVM is a decentralized EVM-compatible Bitcoin L2 that uses BTC as Gas. It allows all DApps which can run in the Ethereum ecosystem to operate on Bitcoin L2. Citrea Round Seed Amount $2.7M Investors Galaxy Citrea is a Bitcoin’s ZK rollup and an execution layer that settles on Bitcoin. Every transaction occurring on Citrea is fully secured by zero-knowledge proofs and verified by Bitcoin through BitVM. Inco Network Round Seed Amount $4.5M Investors 1kx, Circle Ventures Inco Network is an EVM Layer-1, utilizing fully homomorphic encryption (FHE) to enable composable and operable confidential states. Its fhEVM (FHE + EVM) makes it possible to write private smart contracts and perform computations on top of encrypted data without requiring its decryption. This innovation unlocks a wide range use cases with confidentiality components, such as card games, DID, private voting, dark pools, etc. - paving the way for a new era of possibilities. Nest Wallet Round Seed Amount $3.6M Investors Inception Capital, Orange DAO Nest Wallet is a multi-chain wallet built for traders. Powered by Safe, Nest Wallet adds a more friendly UI/UX for team to easily manage multiple Safe wallets and streamline the transaction signing process. DeFi ZeroLend Round Seed Amount $3M Investors Momentum 6 ZeroLend is a decentralized lending protocol on zkSync. Designed to provide individuals and businesses with a secure and transparent platform for borrowing and lending digital assets. The protocol operates in a peer-to-peer manner, eliminating the need for intermediaries such as banks or traditional financial institutions. After announcing the launch of their platform token $ZERO, ZeroLend has introduced a series of activities to encourage users to complete tasks and accumulate points. Recently, they have collaborated with the growth platform TaskOn to release a new set of activities. Shutter Round IDO Amount $8.31M Investors OKX Ventures Shutter Network is an open-source project that aims to prevent front running on Ethereum by using a threshold cryptography-based distributed key generation (DKG) protocol.Shutter allows users to send encrypted transactions in a way that protects them from front runners on their path through the dark forest (the metaphorical hunting ground of front runners that each transaction must cross). OX.FUN Round / Amount $4M Investors Gen Block Capital OX.FUN is a crypto derivatives trading platform. The core element of the gamified experience on OX.FUN revolves around the OX Farm. User can also expect to see leaderboards, competitions and copy trading vaults to help maximize the trading adventure. Renzo Round / Amount / Investors OKX Ventures, Binance Labs Renzo is a restaking protocol based on EigenLayer. Renzo abstracts the complex process of re-staking for end users, and stakers do not have to worry about the active selection and management of operators and reward strategies. ezETH is Renzo’s liquid, heavily-collateralized token that automatically captures rewards and ensures liquidity. ezETH allows users to participate in DeFi while retaining re-collateralization rewards. Singularity Round / Amount $2.2M Investors OKX Ventures, Binance Labs Singularity is a compliant institutional DeFi access layer that provides access to popular protocols for institutional on-chain participants with commercial confidentiality. Users will have their wallet addresses obfuscated whilst leveraging existing DeFi liquidity. Singularity uses the state-of-the-art UltraPLONK proof system with zero-knowledge circuits based on Noir. Honeypot Finance Round Pre-seed Amount / Investors AC Capital Honeypot Finance is whipping up a community-run DeFi Hub that have a honey-flavored flywheel model that churns out dual incentives. INIT Capital Round Seed Amount $3.1M Investors Robot Ventures, Mirana Ventures… INIT Capital is a Liquidity Hook Money Market: Lend, Borrow, and Access Yield Strategies with Liquidity Hook. Serving as the DeFi liquidity infrastructure for dApps to build on top, INIT facilitates diverse activities, including lending, borrowing, and yield strategies. INIT is where dApps and users meet, offering both permissionless access to a unified liquidity pool and efficient yield strategy management. GameFi Shuffle Round Seed Amount $2.5M Investors Karatage, Cypher Capital Shuffle is an all-new crypto casino that support numerous games and jackpots available for players. Matr1x Round Strategic Amount / Investors Animoca Brands, SevenX Ventures… Matr1x is the brand of Metaverse, planning to build the brand through high-quality games developed by themselves or in collaboration with third parties, game IP development and cooperation, and global Esports tournaments. Matr1x will express its game trilogy (Cyber Earth - Mars Immigration - Interstellar Exploration) through three large-scale games with a unified worldview: Matr1x FIRE (First-person shooter), Matr1x WAR (Shooting+MMORPG), and Matr1x EVOLUTION (SOC). Monkey Tilt Round Private Amount $21M Investors Polychain, Hack VC… Monkey Tilt is an online gambling platform focused on the convergence of cryptocurrencies and online gambling. Players can win real money by correctly predicting whether the player they choose will exceed or fall short of their statistical prediction. Crystal Fun Round Seed Amount $5M Investors Waterdrip Capital, Kucoin Ventures… Crystal Fun is a decentralized gaming mega-ecosystem and studio. It aims to seamlessly integrate high-quality games within sustainable economic systems, ushering in a groundbreaking gaming experience into Web3. Loong City Round / Amount $2M Investors MAZARINE SEA Loong City is the first original IP PFP metaverse project based on an improved ERC404 protocol. Autopunk and traditional China constitute the core elements of Dragon City. Each PFP is an entry ticket to this fictional world. NFT Prom Round / Amount / Investors DWF Labs Prom is the primary access point to the Web3 gaming ecosystem. With a robust marketplace at its core for trading and exchanging NFT assets, Prom offers an array of services including rental and mortgage solutions, comprehensive asset management tools, and an educational section with in-depth guides. Tools FortyTwo Round Strategic Amount / Investors LBankLong, Hash Ventures FortyTwo is a Cosmos Portfolio View Platform that allows users to clearly see the breakdown of their Cosmos holdings. Users can can connect one or a bundle of wallets. Tornado Blast Round Strategic Amount / Investors Atka Capital Tornado Blast is a Blast L2-native bot to trade and snipe tokens. User can earn $BLAST, $TRNDO & revenue share reward SocialFi Beoble Round Seed Amount $5M Investors Hashkey Capital, DWF Labs… Beoble is a communication infrastructure and ecosystem that allows users to chat between wallets. Its product includes a web-based chat app, as well as a toolkit that allows Dapps to integrate. Others HackQuest Round Pre-Seed Amount $1.1M Investors HashKey Capital HackQuest is the gateway to the Web3 development world, providing a comprehensive, one-stop educational infrastructure that minimizes friction and helps onboard developers and nondevelopers to the world of Web3. TruePNL Round M&A Amount / Investors Gate.io Labs, Magic Square.. TruePNL is a multi-chain launchpad that connects blockchain projects and crypto investors, providing a convenient, transparent, and secure mechanism for raising capital, investing, and distributing tokens. The platform enables cryptocurrency projects to raise funds by creating token exchange pools and launching public or private sale rounds using smart contracts on the Ethereum and Binance Smart Chain networks. Superfluid Round Strategic Amount $5.1M Investors Fabric Ventures, Multicoin Capital… Superfluid is a Web3 streaming payments protocol for handling subscriptions, salaries, rewards, or any other composable stream of value on a per-second basis. Its core feature is "streaming" payments, where money flows from one address to another in real-time, based on programmable logic and a single on-chain transaction. Silencio Round Pre-seed Amount $1M Investors Borderless Capital, Moonrock Capital Silencio is a global network that measure noise pollution. User will get rewarded for measuring noise pollution with phone. CeFi Januar Round Seed Plus Amount $12M Investors CMT Digital Januar is a European payment gate for crypto companies. Innovative EU crypto companies use Januar's payment account solutions to accept payments and send payouts while maintaining full compliance and stable business operations.

The Crypto Investment Weekly Recap for Feb 19 - Feb 25

RE(SOURCE)

resourcefashion.co

11-50 employees

Since 2021

COMPANY RANKING

RE(SOURCE)

EVERGREEN INDEX #8963

Representing this company? Click here to claim and customize this page!

RE(SOURCE) WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

RE(SOURCE)

resourcefashion.co

11-50 employees

Since 2021

COMPANY RANKING

RE(SOURCE)

EVERGREEN INDEX #8963

RELATED COMPANIESRANK

STORIES ABOUT RE(SOURCE)

Representing this company? Click here to claim and customize this page!

RE(SOURCE) WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!