In December 2018, Congress passed the Agricultural Improvement Act of 2018 (better known as the “Farm Bill”). Among other things, the passage of the bill removed industrial hemp from the federal Controlled Substances Act, allowing legal production of the crop. Despite this landmark legislation, pitfalls still lay on the path ahead. The legality of many industrial-hemp derived cannabidiol (“CBD”) products is in question now more than ever, with different states and federal agencies taking vastly different approaches on every facet of the hemp CBD industry.
Interest in hemp is at an all-time high, and with an industry that has a potential to be worth $20 billion by 2022, it is easy to see why. If you are a hemp CBD business, have interest in the industry or are interested in the state and future of hemp CBD legality, please join us on February 21, 2019 at noon (PST) for the latest installment in our lunchtime webinar series entitled “West Coast Hemp CBD After the Farm Bill.”
In this hour-long session, Harris Bricken lawyers Daniel Shortt (Seattle, Washington), Nathalie Bougenies (Portland, Oregon), and Griffen Thorne (Los Angeles, California) will provide an in-depth look at changes in federal law and policy post Farm bill, as well as its impact on each of the three west coast states (Washington, Oregon, and California). Throughout the presentation our team will also discuss the status of laws and regulations in each state. Some of the topics we will cover include:
- the future of hemp permitting;
- Farm Bill implications for Internal Revenue Code section 280E;
- banking for hemp CBD businesses;
- intellectual property for hemp CBD businesses;
- CBD in food, beverages, vape cartridges, oils, topicals, and other products; and
- the Food and Drug Administration’s role in hemp CBD.
With moderator Hilary Bricken, our panel of attorneys will address audience questions throughout the presentation. Please register for the event here! Should you have any further questions, please feel free to reach us at firstname.lastname@example.org.