Conclave Cloud is here! Get started with confidential serverless computing architecture today.
Sustainability is on everyone’s minds these days. Take electric vehicles – nearly every auto manufacturer is producing one; many governments subsidize them; and the infrastructure for them is growing quickly. For the first time, cars are steadily becoming less polluting.
How do different blockchains compare? With headlines focusing on the sustainability problem of Bitcoin, you may be wondering what other options are out there, and whether they are really any better. The main contributing factor to energy consumption is the consensus process. But this can look very different depending on which blockchain you’re measuring. We decided to do some quick math to see if we could come up with a like-for-like ranking.
Bitcoin’s consensus problem
Both Bitcoin and large heavy cars have a reputation for being terrible for the environment. Every journey and transaction requires large amounts of energy. For that gas guzzler speeding down the highway, the engine is the problem; it uses fossil fuels which are non-renewable and pollute the environment.
For blockchain, the problematic feature is the consensus mechanism. Consensus is how a blockchain validates a transaction. While different blockchains use different consensus mechanisms, Bitcoin’s popularity and reach makes its mechanism – called Proof of Work (PoW) – the Hummer of blockchains.
In PoW, users compete to mine blocks of transactions. Mining is a competitive part of the validation process used to ensure that the input of a transaction is the same as its output. The process of finding an integer that results in the hash value of the block being under the current target difficulty requires many attempts, by many competing miners, which translates to a lot of computing power. Additionally, the market capitalization of a cryptocurrency strongly correlates with its energy demand, making any proof-of-work based cryptocurrency anti-efficient from an energy consumption perspective. This is particularly evident in popular cryptocurrencies like Bitcoin.
But wait! Every blockchain works a little differently
But not every blockchain is a Hummer. PoW is only one of several common consensus mechanisms. Others are Proof of Stake (PoS) and the low-energy alternatives of private blockchains.
In comparison to the energy-intensive mining free-for-all of PoW, PoS gives those with larger cryptocurrency holdings more power in transaction validation. Depending on the design of the PoS protocol, a validator may stake cryptocurrency in order to qualify as a validator. Should they abuse this position of power by acting dishonestly, the staked amounts may be “slashed”. This motivates good behavior, which obviates the need for computing puzzles in consensus, meaning that less energy is consumed than in PoW models.
Achieving finality in Corda is even more efficient
A broad approximation of the energy needed to achieve transaction finality can be made by taking into account the energy demand of servers responsible for transaction finalisation. In PoW dedicated mining hardware with a large energy footprint is required and, depending on the popularity of the blockchain, a large number of miners may participate. In PoS, commodity hardware is sufficient. Still, the number of participating validator machines can be high. In the Corda protocol, where notary nodes are responsible for transaction finalisation, networks can operate with a small number of validator nodes. In fact, most deployments, including the public Corda network, utilise just a single logical notary.
Table 1. Energy consumption of different blockchains
Blockchain | Transaction Finalisation | Energy consumed per transaction (Joules/Tx) |
---|---|---|
Bitcoin | Proof of work | 125,000,000 |
Ethereum | Proof of work | 17,222,222 |
Polkadot | Proof of stake | 1663 |
Corda | Corda Notary Service | 24.6 |
Note: data in this chart is based on publicly available data and may not reflect exact volumes.
Sources: Data for Bitcoin, Ethereum and Polkadot sourced from Powell, Hendon Mangle and Wimmer (2021). Data for Corda calculated from the Corda Network using the formula (205*6)/50.
For our purposes here – as a back of the envelope effort to compare magnitudes only – a single number “snapshot in time” approach was used. But as any holder of cryptocurrency knows, the number of validators and throughput changes frequently for public blockchains. Conceivably, the number of validators may even be correlated with the number of transactions on a blockchain. We believe that the table functions as a reasonable estimate of comparable magnitudes.
We have a couple of caveats to this table. In an ideal world, we would have high quality public data for each variable. In reality, the quality is uneven. We made our best efforts to use publicly available published data.
Second, we make some effort to overestimate Corda’s energy consumption. The estimates are driven down by either very high TPS or low numbers of servers. We use higher values when there is a range and the least efficient architecture where there is a selection. For example, the server energy consumption is at the high end of the spectrum, and the TPS we use takes the current average of 50 rather than the demonstrated potential for 6,300 TPS under a specialized configuration. This is intended to balance any perceived bias on the part of the authors.
But is this really comparing like-for-like?
We made our best effort to compare the same part of the consensus actions for all of the blockchains. Most existing work on energy usage measures public blockchains and the mining process. To extend this to Corda, which does not have mining, we needed to make some assumptions.
The biggest comparison hurdle was the definition of a transaction. In the case of public blockchains, this is clearly the achievement of global consensus about a particular set of UTXOs. This is a highly secure process in bitcoin. To extend this to Corda, which uses a notary service, we assume a simple payment transaction between two parties that processes a single state. Where a bitcoin transaction is always a payment, a Corda transaction can be anything from a smart contract execution to an asset transfer.
The calculation
There are differences in the calculations used for PoW, PoS and the Corda Notary service. The reason is that the protocols, number of validator nodes, recommended hardware, and need for throughput vary.
A very rough model we used to calculate energy use was this one:
Energy per transaction = (power per server x number of servers) / transactions per second
We adopted this admittedly highly simplified model from a peer-reviewed paper on the industry’s efforts to make blockchain greener. It assumes that a server consumes a certain amount of energy, that there are a known number of servers needed to operate a blockchain network, and that blockchain networks have a known volume of throughput.
For the public blockchains, their energy consumption figures were converted to watts per second, and then divisible by transactions per second (see figures for Bitcoin, Polkadot, Ethereum). This yielded numbers that are comparable to others published about these blockchains.
Power per server – The savvy reader will know that server consumption is a tricky variable. A recent paper on blockchain consensus mechanisms estimates that it can take a range of value from 5.5 to 328 watts depending on hardware type.
For Bitcoin and Ethereum, the Cambridge Bitcoin Electricity Consumption Index calculates a detailed number that takes into account the type of mining equipment. For the other blockchains, we need to make assumptions about the type of equipment used. Polkadot numbers assume a Dell R730 rack-mounted server which uses 168 watt hours as their figure. For Corda, we take a number at the higher end of the spectrum at 205.
Number of servers – Again, for public blockchains this can be estimated directly as the hash rate is known. Polkadot also publishes these numbers, which for them was 732 according to their public site at the time of access. For Corda, we estimated the number of servers by assuming every notary processes one state per transaction (this is a lower bound of efficiency as most nodes are probably processing multiple states) and uses all 3 of the notaries on the Corda Network plus each of their associated database nodes (for a total of 6 nodes per transaction).
An important caveat is that all blockchains use multiple phases for a transaction to validate and finalize. A recent paper breaks it down into five steps for public blockchains. Since we employ existing calculations, we follow the practice of only including transaction finality processes in our calculations and do not include the validation phase (signing and sending) for Corda or any of the other blockchains in Table 1..
Transactions per second – there are considerable differences in transactions per second (TPS) between different blockchains. TPS is defined by the way transaction finality occurs in each blockchain. In table 1 above PoW generally has lower TPS than PoS and finally Corda. We use average numbers for the network at the time of writing. But In all cases, protocol parameters can be adjusted to achieve higher TPS. For Corda, we estimate 50 TPS average per Corda node using data from existing traffic on the Corda Network.
Sustainability use cases are on the rise
Increasingly, the blockchain community is seeking ways to improve global sustainability. The technology facilitates use cases that prioritise climate resilience, including supply chain and energy provenance and green finance. And it consolidates processes of legacy systems, making them much more energy efficient. By storing information on a blockchain, it becomes immutable and viable, which ensures that parties are held accountable for their green pledges.
Private blockchains are the most energy efficient choice that you can make today. This has led the way in promoting change throughout the community, as, just as you can’t really justify driving a Hummer anymore, it is no longer possible to argue that high energy consumption is the only way to run a blockchain.
Relevant links
Authored by
– Alisa DiCaprio, R3, Head of Trade
– Maya Marie, R3 Summer Analyst, MA student at University of St Andrews
Share
Sign up for our flagship newsletter, The R3 Ledger, to receive the latest R3 news, updates and content. View all our newsletters here.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie | Duration | Description |
---|---|---|
__cfruid | session | This cookie is set by the provider Cloudflare. This cookie is used for load balancing and for identifying trusted web traffic. |
__cfruid | session | This cookie is set by the provider Cloudflare. This cookie is used for load balancing and for identifying trusted web traffic. |
__cfruid | session | This cookie is set by the provider Cloudflare. This cookie is used for load balancing and for identifying trusted web traffic. |
_biz_flagsA | 1 year | A Cloudflare cookie set to record users’ settings as well as for authentication and analytics. |
_biz_pendingA | 1 year | A Cloudflare cookie set to record users’ settings as well as for authentication and analytics. |
_biz_sid | 30 minutes | This cookie is set by Bizible, to store the user's session id. |
_ga | 2 years | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
_ga | 2 years | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
_ga | 2 years | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
_ga_1ECB5XX5W0 | 2 years | This cookie is installed by Google Analytics. |
_ga_1ECB5XX5W0 | 2 years | This cookie is installed by Google Analytics. |
_ga_1ECB5XX5W0 | 2 years | This cookie is installed by Google Analytics. |
_gat_UA-87760032-2 | 1 minute | This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites. |
_gat_UA-87760032-2 | 1 minute | This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites. |
_gat_UA-87760032-2 | 1 minute | This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites. |
_GRECAPTCHA | 5 months 27 days | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
ARRAffinity | This cookie is set by websites that run on Windows Azure cloud platform. The cookie is used to affinitize a client to an instance of an Azure Web App. | |
ARRAffinity | 1 year | This cookie is set by websites that run on Windows Azure cloud platform. The cookie is used to affinitize a client to an instance of an Azure Web App. |
ARRAffinity | 1 year | This cookie is set by websites that run on Windows Azure cloud platform. The cookie is used to affinitize a client to an instance of an Azure Web App. |
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
JSESSIONID | session | Used by sites written in JSP. General purpose platform session cookies that are used to maintain users' state across page requests. |
JSESSIONID | session | Used by sites written in JSP. General purpose platform session cookies that are used to maintain users' state across page requests. |
JSESSIONID | session | Used by sites written in JSP. General purpose platform session cookies that are used to maintain users' state across page requests. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
viewed_cookie_policy | 1 year | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
viewed_cookie_policy | 1 year | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
viewed_cookie_policy | 1 year | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
_biz_nA | 1 year | This cookie, set by Bizible, is a sequence number that Bizible includes for all requests, for internal diagnostics purposes. |
_biz_uid | 1 year | This cookie is set by Bizible, to store user id on the current domain. |
bcookie | 2 years | This cookie is set by linkedIn. The purpose of the cookie is to enable LinkedIn functionalities on the page. |
bcookie | 2 years | This cookie is set by linkedIn. The purpose of the cookie is to enable LinkedIn functionalities on the page. |
bcookie | 2 years | This cookie is set by linkedIn. The purpose of the cookie is to enable LinkedIn functionalities on the page. |
lang | session | This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website. |
lang | session | This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website. |
lang | session | This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website. |
language | This cookie is used to store the language preference of the user. | |
language | 1 year | This cookie is used to store the language preference of the user. |
language | 1 year | This cookie is used to store the language preference of the user. |
lidc | 1 day | This cookie is set by LinkedIn and used for routing. |
lidc | 1 day | This cookie is set by LinkedIn and used for routing. |
lidc | 1 day | This cookie is set by LinkedIn and used for routing. |
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie | Duration | Description |
---|---|---|
_BUID | 1 year | This cookie is used to store a universal user ID to identify the same user across multiple clients' domains. |
_BUID | 1 year | This cookie is used to store a universal user ID to identify the same user across multiple clients' domains. |
_BUID | 1 year | This cookie is used to store a universal user ID to identify the same user across multiple clients' domains. |
_gcl_au | 3 months | This cookie is used by Google Analytics to understand user interaction with the website. |
_gcl_au | 3 months | This cookie is used by Google Analytics to understand user interaction with the website. |
_gcl_au | 3 months | This cookie is used by Google Analytics to understand user interaction with the website. |
_gd_session | 4 hours | This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded. |
_gd_svisitor | 2 years | This cookie is set by the Google Analytics. This cookie is used for tracking the signup commissions via affiliate program. |
_gd_visitor | 2 years | This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads. |
_gid | 1 day | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form. |
_gid | 1 day | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form. |
_gid | 1 day | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form. |
_hjAbsoluteSessionInProgress | 30 minutes | No description available. |
_hjAbsoluteSessionInProgress | 30 minutes | No description available. |
_hjAbsoluteSessionInProgress | 30 minutes | No description available. |
_hjFirstSeen | 30 minutes | This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. |
_hjFirstSeen | 30 minutes | This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. |
_hjFirstSeen | 30 minutes | This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. |
_hjid | 1 year | This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
_hjid | 1 year | This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
_hjid | 1 year | This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
_hjIncludedInPageviewSample | 2 minutes | No description available. |
_hjIncludedInPageviewSample | 2 minutes | No description available. |
_hjIncludedInPageviewSample | 2 minutes | No description available. |
_hjIncludedInSessionSample | 2 minutes | No description available. |
_hjIncludedInSessionSample | 2 minutes | No description available. |
_hjIncludedInSessionSample | 2 minutes | No description available. |
_hjTLDTest | session | To determine the most generic cookie path that has to be used instead of the page hostname, Hotjar sets the _hjTLDTest cookie to store different URL substring alternatives until it fails. |
_uetsid | 1 day | This cookies are used to collect analytical information about how visitors use the website. This information is used to compile report and improve site. |
_uetsid | 1 day | This cookies are used to collect analytical information about how visitors use the website. This information is used to compile report and improve site. |
_uetsid | 1 day | This cookies are used to collect analytical information about how visitors use the website. This information is used to compile report and improve site. |
_ym_d | 1 year | This domain of this cookie is owned by Yandex.Matrica. This cookie is used to store the date of the users first site session. |
_ym_d | 1 year | This domain of this cookie is owned by Yandex.Matrica. This cookie is used to store the date of the users first site session. |
_ym_d | 1 year | This domain of this cookie is owned by Yandex.Matrica. This cookie is used to store the date of the users first site session. |
_ym_isad | 20 hours | This domain of this cookie is owned by Yandex.Matrica. This cookie is used to collect information about the user like his characteristics, behaviour on page and targeted actions. |
_ym_isad | 20 hours | This domain of this cookie is owned by Yandex.Matrica. This cookie is used to collect information about the user like his characteristics, behaviour on page and targeted actions. |
_ym_isad | 20 hours | This domain of this cookie is owned by Yandex.Matrica. This cookie is used to collect information about the user like his characteristics, behaviour on page and targeted actions. |
_ym_uid | 1 year | This cookie is by Yandex.Metrica. This cookie is used to set a unique ID to the visitor and to collect information about how visitor use the website. Thus it help to track the user and the collected informationn is used to improve the site. |
_ym_uid | 1 year | This cookie is by Yandex.Metrica. This cookie is used to set a unique ID to the visitor and to collect information about how visitor use the website. Thus it help to track the user and the collected informationn is used to improve the site. |
_ym_uid | 1 year | This cookie is by Yandex.Metrica. This cookie is used to set a unique ID to the visitor and to collect information about how visitor use the website. Thus it help to track the user and the collected informationn is used to improve the site. |
attribution_user_id | 1 year | This cookie is set by Typeform for usage statistics and is used in context with the website's pop-up questionnaires and messengering. |
browser_id | 5 years | This cookie is used for identifying the visitor browser on re-visit to the website. |
CONSENT | 16 years 5 months 12 days 10 hours | These cookies are set via embedded youtube-videos. They register anonymous statistical data on for example how many times the video is displayed and what settings are used for playback.No sensitive data is collected unless you log in to your google account, in that case your choices are linked with your account, for example if you click “like” on a video. |
CONSENT | 16 years 5 months 12 days 10 hours | These cookies are set via embedded youtube-videos. They register anonymous statistical data on for example how many times the video is displayed and what settings are used for playback.No sensitive data is collected unless you log in to your google account, in that case your choices are linked with your account, for example if you click “like” on a video. |
CONSENT | 16 years 5 months 12 days 10 hours | These cookies are set via embedded youtube-videos. They register anonymous statistical data on for example how many times the video is displayed and what settings are used for playback.No sensitive data is collected unless you log in to your google account, in that case your choices are linked with your account, for example if you click “like” on a video. |
pardot | past | The cookie is set when the visitor is logged in as a Pardot user. |
pardot | past | The cookie is set when the visitor is logged in as a Pardot user. |
pardot | past | The cookie is set when the visitor is logged in as a Pardot user. |
sid | 1 year | The sid cookie contains digitally signed and encrypted records of a user’s Google account ID and most recent sign-in time. |
uid | 1 year | This is a Google UserID cookie that tracks users across various website segments. |
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie | Duration | Description |
---|---|---|
_fbp | 3 months | This cookie is set by Facebook to deliver advertisement when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website. |
_fbp | 3 months | This cookie is set by Facebook to deliver advertisement when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website. |
_fbp | 3 months | This cookie is set by Facebook to deliver advertisement when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website. |
anj | 3 months | No description available. |
anj | 3 months | No description available. |
anj | 3 months | No description available. |
ANONCHK | 10 minutes | The ANONCHK cookie, set by Bing, is used to store a user's session ID and also verify the clicks from ads on the Bing search engine. The cookie helps in reporting and personalization as well. |
bscookie | 2 years | This cookie is a browser ID cookie set by Linked share Buttons and ad tags. |
bscookie | 2 years | This cookie is a browser ID cookie set by Linked share Buttons and ad tags. |
bscookie | 2 years | This cookie is a browser ID cookie set by Linked share Buttons and ad tags. |
fr | 3 months | The cookie is set by Facebook to show relevant advertisments to the users and measure and improve the advertisements. The cookie also tracks the behavior of the user across the web on sites that have Facebook pixel or Facebook social plugin. |
fr | 3 months | The cookie is set by Facebook to show relevant advertisments to the users and measure and improve the advertisements. The cookie also tracks the behavior of the user across the web on sites that have Facebook pixel or Facebook social plugin. |
fr | 3 months | The cookie is set by Facebook to show relevant advertisments to the users and measure and improve the advertisements. The cookie also tracks the behavior of the user across the web on sites that have Facebook pixel or Facebook social plugin. |
i | 10 years | The purpose of the cookie is not known yet. |
i | 10 years | The purpose of the cookie is not known yet. |
i | 10 years | The purpose of the cookie is not known yet. |
IDE | 1 year 24 days | Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile. |
IDE | 1 year 24 days | Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile. |
IDE | 1 year 24 days | Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile. |
MUID | 1 year 24 days | Used by Microsoft as a unique identifier. The cookie is set by embedded Microsoft scripts. The purpose of this cookie is to synchronize the ID across many different Microsoft domains to enable user tracking. |
MUID | 1 year 24 days | Used by Microsoft as a unique identifier. The cookie is set by embedded Microsoft scripts. The purpose of this cookie is to synchronize the ID across many different Microsoft domains to enable user tracking. |
MUID | 1 year 24 days | Used by Microsoft as a unique identifier. The cookie is set by embedded Microsoft scripts. The purpose of this cookie is to synchronize the ID across many different Microsoft domains to enable user tracking. |
NID | 6 months | This cookie is used to a profile based on user's interest and display personalized ads to the users. |
NID | 6 months | This cookie is used to a profile based on user's interest and display personalized ads to the users. |
NID | 6 months | This cookie is used to a profile based on user's interest and display personalized ads to the users. |
personalization_id | 2 years | This cookie is set by twitter.com. It is used integrate the sharing features of this social media. It also stores information about how the user uses the website for tracking and targeting. |
personalization_id | 2 years | This cookie is set by twitter.com. It is used integrate the sharing features of this social media. It also stores information about how the user uses the website for tracking and targeting. |
personalization_id | 2 years | This cookie is set by twitter.com. It is used integrate the sharing features of this social media. It also stores information about how the user uses the website for tracking and targeting. |
test_cookie | 15 minutes | This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies. |
test_cookie | 15 minutes | This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies. |
test_cookie | 15 minutes | This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies. |
uuid2 | 3 months | This cookies is set by AppNexus. The cookies stores information that helps in distinguishing between devices and browsers. This information us used to select advertisements served by the platform and assess the performance of the advertisement and attribute payment for those advertisements. |
uuid2 | 3 months | This cookies is set by AppNexus. The cookies stores information that helps in distinguishing between devices and browsers. This information us used to select advertisements served by the platform and assess the performance of the advertisement and attribute payment for those advertisements. |
uuid2 | 3 months | This cookies is set by AppNexus. The cookies stores information that helps in distinguishing between devices and browsers. This information us used to select advertisements served by the platform and assess the performance of the advertisement and attribute payment for those advertisements. |
VISITOR_INFO1_LIVE | 5 months 27 days | This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website. |
VISITOR_INFO1_LIVE | 5 months 27 days | This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website. |
VISITOR_INFO1_LIVE | 5 months 27 days | This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website. |
YSC | session | This cookies is set by Youtube and is used to track the views of embedded videos. |
YSC | session | This cookies is set by Youtube and is used to track the views of embedded videos. |
YSC | session | This cookies is set by Youtube and is used to track the views of embedded videos. |
yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
Cookie | Duration | Description |
---|---|---|
_an_uid | 7 days | No description available. |
_clck | 1 year | No description |
_clsk | 1 day | No description |
_hjSession_1646283 | 30 minutes | No description |
_hjSessionUser_1646283 | 1 year | No description |
_uetvid | 1 year 24 days | No description available. |
_uetvid | 1 year 24 days | No description available. |
_uetvid | 1 year 24 days | No description available. |
6suuid | 2 years | No description available. |
AnalyticsSyncHistory | 1 month | No description |
AnalyticsSyncHistory | 1 month | No description |
AnalyticsSyncHistory | 1 month | No description |
ARRAffinitySameSite | No description available. | |
ARRAffinitySameSite | 1 year | No description available. |
ARRAffinitySameSite | 1 year | No description available. |
bEkAYwpdRGcM | 1 day | No description |
bEkAYwpdRGcM | 1 day | No description |
bEkAYwpdRGcM | 1 day | No description |
BIGipServer~magenta~mag-c-http-http-xhttpd-http-xhttpd-http-80 | session | No description |
DCMpagecount | session | No description |
DCMpagecount | session | No description |
DCMpagecount | session | No description |
debug | never | No description available. |
gaCookie | 2 years | No description available. |
gaCookie_gid | 1 day | No description available. |
LEAfgqMGWpwUs | 1 day | No description |
LEAfgqMGWpwUs | 1 day | No description |
LEAfgqMGWpwUs | 1 day | No description |
li_gc | 2 years | No description |
li_gc | 2 years | No description |
li_gc | 2 years | No description |
lpv413292 | 30 minutes | No description |
lpv413292 | 30 minutes | No description |
lpv413292 | 30 minutes | No description |
m | 2 years | No description available. |
metrika_enabled | session | No description available. |
metrika_enabled | session | No description available. |
metrika_enabled | session | No description available. |
muc_ads | 2 years | No description |
SM | session | No description available. |
STYXKEY_formcomplete | 9 months 26 days | No description |
UserMatchHistory | 1 month | Linkedin - Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences. |
UserMatchHistory | 1 month | Linkedin - Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences. |
UserMatchHistory | 1 month | Linkedin - Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences. |
vary | 1 month | No description |
visitor_id413292 | 10 years | No description |
visitor_id413292 | 10 years | No description |
visitor_id413292 | 10 years | No description |
visitor_id413292-hash | 10 years | No description |
visitor_id413292-hash | 10 years | No description |
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Cookie | Duration | Description |
---|---|---|
SRM_B | 1 year 24 days | Used by Microsoft Advertising as a unique ID for visitors. |