<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Angelis Consulting Group | Kent | Activity</title>
	<link>https://angelisconsulting.com/members/creeknail49/activity/</link>
	<atom:link href="https://angelisconsulting.com/members/creeknail49/activity/feed/" rel="self" type="application/rss+xml" />
	<description>Activity feed for Kent.</description>
	<lastBuildDate>Thu, 27 Aug 2026 15:31:01 -0500</lastBuildDate>
	<generator>https://buddypress.org/?v=</generator>
	<language>en-US</language>
	<ttl>30</ttl>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>2</sy:updateFrequency>
	
						<item>
				<guid isPermaLink="false">fb4926161e2bcb4aca22c18972e8f203</guid>
				<title>Kent posted an update: The Future of Wagering: Navigating the Landscape of New [&#133;]</title>
				<link>https://angelisconsulting.com/activity/p/53294/</link>
				<pubDate>Tue, 18 Aug 2026 05:34:14 -0500</pubDate>

									<content:encoded><![CDATA[<p>The Future of Wagering: Navigating the Landscape of New Crypto Casinos</p>
<p>The digital gambling industry is undergoing a seismic shift. As blockchain technology grows, the traditional casino design&#8211; typically defined by sluggish banking processes, high transaction charges, and limited openness&#8211; is being challenged by a wave of new crypto gambling&hellip;<span class="activity-read-more" id="activity-read-more-53294"><a href="https://angelisconsulting.com/activity/p/53294/" rel="nofollow ugc">[Read more]</a></span></p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">e62545560b02fbb9bf4ac9f97750e623</guid>
				<title>Kent became a registered member</title>
				<link>https://angelisconsulting.com/activity/p/53273/</link>
				<pubDate>Tue, 18 Aug 2026 05:29:45 -0500</pubDate>

				
									<slash:comments>0</slash:comments>
				
							</item>
		
	</channel>
</rss>