BTF - Bitcoin Strategy ETF Learn More → | WGMI - Bitcoin Miners ETF Learn More → | Valkyrie's Opportunities Around GBTC Learn More →
Follow us:
Twitter: https://twitter.com/ValkyrieFunds
Instagram: https://instagram.com/valkyrie.invest
LinkedIn: https://www.linkedin.com/company/valkyrieinvestments/
Facebook: https://www.facebook.com/ValkyrieInvestments
Follow Sean Rooney: https://twitter.com/usaRooney
VP Trading and Research Sean Rooney breaks down the concept of Smart Contracts.
The concept of smart contracts was introduced in the 1990s. We've seen a progression of potential use cases as crypto continues to grow and innovate as an asset class.
With regards to crypto, we think of smart contracts as an application or program that runs on a blockchain. The Bitcoin protocol has been supporting smart contracts for many years, however, they were made more popular by Ethereum and now other Layer One Platform protocols such as Polkadot or Avalanche.
Smart Contracts facilitate three functions: To store rules of a contract, verify those rules, and self execute the agreement based on the rules.
The basic idea behind this technology is that two or more entities can make an agreement on the blockchain without the need for an intermediary, or the need to trust or know one another.
Perhaps, to some, the grand vision of smart contracts and their use in a decentralized finance (DeFi) would be to facilitate any number of financial services from borrowing and lending, real estate, or insurance.
One common example of using smart contracts for insurance relates to crop insurance. A farmer could purchase crop insurance to mitigate the risk of there not being enough rain. Based on the amount of rainfall that season, the contract would automatically pay out to the farmer based on the pre-arranged rules of the contract between the insurer and the insured.
Smart contracts become viable only when their conditions can be completely transcribed into the code.
Unfortunately, this is somewhat of a rare scenario as a significant portion of contracts are in fact filled with nuances. Back to the crop insurance example, who decides how much rainfall has actually occurred in a very particular geographical location that season? Already, we’re bringing in other parties. For that particular use case, smart contracts could be somewhat tricky.
A legitimately intelligent contract might take into account mitigating circumstances, think about the spirit of the contract, and then distribute funds in an even and fair manner, even in extreme gray areas or confusing circumstances.
Liquidity pools, DeFi, creating and utilizing new tokens on top of layer one protocols, and NFTs. All of these are made possible and powered by the use of smart contracts.
It will be interesting to see if smart contracts continue to develop and mature in order to fill some of the future use cases many people are looking for, such as protecting copyrights, digital identity storage, digital data recording, and much more.
Perhaps similar to NFTs, the fairly new technology exists in its current state, but perhaps we’re under estimating the deeper implications of smart contracts that are still to come.
The Lightbulb Series covers crypto topics in 5 minutes or less. If you have a question you want covered, reach out to us on social media or via email at [email protected]
DISCLOSURE: The opinions presented herein are solely of the individual and not necessarily representative of Valkyrie Investments Inc. and their affiliates. There is no guarantee that any specific outcome will be achieved. Investments may be speculative, illiquid and there is a risk of total loss of your investment. Past performance is not indicative of future results.
Cookie | Duration | Description |
---|---|---|
__hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
AWSELB | session | Associated with Amazon Web Services and created by Elastic Load Balancing, AWSELB cookie is used to manage sticky sessions across production servers. |
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-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-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
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-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-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". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
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. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
__hssc | 30 minutes | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
bcookie | 2 years | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
bscookie | 2 years | LinkedIn sets this cookie to store performed actions on the website. |
lang | session | LinkedIn sets this cookie to remember a user's language setting. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
Cookie | Duration | Description |
---|---|---|
AWSELBCORS | 5 minutes | This cookie is used by Elastic Load Balancing from Amazon Web Services to effectively balance load on the servers. |
Cookie | Duration | Description |
---|---|---|
__hstc | 5 months 27 days | This is the main cookie set by Hubspot, for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_ga_HB5P757H6F | 2 years | This cookie is installed by Google Analytics. |
_gat_gtag_UA_202302885_1 | 1 minute | Set by Google to distinguish users. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
at-rand | never | AddThis sets this cookie to track page visits, sources of traffic and share counts. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
hubspotutk | 5 months 27 days | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
undefined | never | Wistia sets this cookie to collect data on visitor interaction with the website's video-content, to make the website's video-content more relevant for the visitor. |
uvc | 1 year 1 month | Set by addthis.com to determine the usage of addthis.com service. |
Cookie | Duration | Description |
---|---|---|
_fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. |
loc | 1 year 1 month | AddThis sets this geolocation cookie to help understand the location of users who share the information. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
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. |
Cookie | Duration | Description |
---|---|---|
AnalyticsSyncHistory | 1 month | No description |
li_gc | 2 years | No description |
loglevel | never | No description available. |
pum-1717 | 1 month | No description |