Bonjour everyone. Welcome to Learning to Scale OpenStack. It's the Juneau update from the Rackspace public cloud specifically around the build release deploy systems. This is not my favorite microphone but this is one of my favorite quotes. In preparing for battle I have always found that plans are useless but planning is indispensable Dwight D. Eisenhower 34th president of the United States. I have a lot of letters that I can put after my name that certify I can plan projects and implement really good software development processes but I've been a developer long enough to know that all the process and planning in the world doesn't actually get you where you need to go you just need to code the stuff so but I have learned that the actual art of planning of talking of coming together of collaborating going through that conflict is really helpful and that's really what we do every six months when we come together at OpenStack is we we go through the planning which is indispensable this is what OpenStack is trying to do rainbows and unicorns all around the world space unicorn Google it hilarious earworm for the day there's a lot of optimism the keynotes after four years have been you know those are some of the best best yet as you're seeing the way that the software is changing how companies perform how their data centers work the reality of where we are right now is more like that this is the Miltonius blog unicorn of technical difficulties I don't know where it comes from but I saw it one day and just like yes that's what we are the unicorn is tangled up in the inner workings and so today I want to just walk you through what Rackspace has done for the last six months in the Juno cycle and give you a kind of a glimpse of where we're going as we look to kilo my name is Rainia Moser and I am a software development manager at Rackspace for the build release and deploy system that does all of the open stack public cloud control plane deployments so we are still I believe the largest public open stack deployment so when we're talking about scale it's this massive horizontal scale that the private cloud use cases aren't having to deal with just yet but I personally believe they will sooner rather than later because big clouds or little clouds grow up to be big clouds so let's define scale Rackspace's public cloud is in five time zones and four countries there are six production regions and we have over six and growing lower level environments so far CI continuous integration test pre-production stable environments those those are all they need to be deployed to there's over 20,000 hypervisors and growing over 20,000 computes and growing and over 2,000 control plane nodes and growing and we have to upgrade that code regularly in order to stay up to date with open stack provide new functionality to customers and most importantly provide the stability features and functionality that are coming out to open to open stack as that product platform matures so it's a lot yeah I actually got to deploy push the actual button to London that was really that was really cool that was really cool it's one thing to develop it and design it and another thing to actually deploy to a couple thousand things in another country so here is a super simple explanation of what the build release deploy system does in the public cloud a user comes in hits the API that's where the control plane is Nova Glantz neutron services live up in there open stack magic happens it comes down to the data plane which at Rackspace's Zen server and OBS for networking pops out a customer VM and that user can now access that instance for the build release and deploy system it is just going to upgrade disturb touch the open stack services and it's not going to come down into the data plane layer where that customer's instances so any impact that the customer feels is going to be on performing actions on their instance not on actually being able to access their instance so if they have a website that they're serving up to customers and we do a control plane upgrade that websites going to continue to function however they won't be able to maybe rebuild it or hit the API as the as the services upgrade so what have we done so far in 2014 to date we have upgraded the control plane at Rackspace 11 times it is the lowest number in the two and a half years that I have been here it's definitely getting more and more difficult to upgrade an open stack deployment at any scale and a lot of the talks and sessions design summits operator meetups that I've been through today have really it reiterated that that the deployment pain is now is now real and how do we how do we fix that so let's go into some details around the ones that we've done so our we we work in what we call iterations we started the year on iteration 8 which is representative of an upstream pull from trunk from open stack trunk pulled it down we did three deploys from that and the main thing we accomplished aside from just keep keeping up with open stack providing stability features as we were able to expose the public glance API which allows end users to go through public glance rather than having to go through Nova for all of that that took us through the end of March iteration 9 overlaps that's that's one of our goals is to try to keep it going continually we were only able to do two deploys because it was then migration to neutron and it was particularly challenging there was some really great sessions last summit in Atlanta if you want to go back and listen to the videos and find them it that that migration to neutron was much more painful than we thought it would be we learned a lot the community learned a lot now neutron is deployed and that is what we use we're we just wrapped up iteration 10 one of the the downsides of having waited so long in that iteration 9 with the neutron deployment is that there was a bunch of code that got stacked up upstream that we couldn't pull down and so then we had to take that gap and catch up restabilize make sure everything that was happening on upstream still worked with our internal billing system for example so we had a we had a gap there where we needed to reset refocus we did six deploys from this because there was a big push at rack space at the end you know towards the end of the year to launch some features boot from volume has been supported in open stock for a while not supported by all of the public clouds we really wanted to kind of put that out there let's get this let's get this working in usable in a production cloud new flavors were launched and just a bunch of new orchestration we change out the deployment orchestration which will talk a little bit about here so we did a lot in that iteration 10 so it was beneficial to us to extend it a little bit longer now we're starting up our iteration 11 we have three deploys planned through the end of the year and into early January and the main focus here is to actually expose that public neutron API point so that you can interact with your networks outside of Nova which will be very cool how do we do all of this it's a real simple system we have combination of open source software internal Python that has been written and put together to orchestrate interact with things a little bit of proprietary licensed software comes into play and it all works together somehow magic and really hard work to go to actually function so we're gonna go through each of these starting with open stock code we start everything from upstream and specifically when we're talking about the control plane and what what my team is really focused on we're really focused on Nova Glantz and neutrons of the compute and network portion and we we depend on upstream open stack and the CI gate and the open stack infrastructure team and all of the amazing work that they do to even start our process so for all the work and all of the detail that we're going through here there's a ton more of work that happens before it even gets to this point from the upstream open stack code even though open stack is great and the CI gate is amazing there is the need whether you are doing just configurations integrating with legacy systems need to make sure that it works with your billing internally there's a high probability that you're going to need a change that is not in upstream open stack master trunk and that's where the patch management comes into play this is a ply is what we use it was written by Rick Harris who is a rack space employee and a contributor to open stack and it's just it's github based ply management this allows us to put changes on top of open stack without rewriting history or risking a a overriding of changes from a get force from a force push which has happened and that's why we invented this so so that's how we do the patch management our configuration management we were transitioning from puppet to ansible on a project by project basis we have been previously on we've had a centralized puppet puppet master list is what we're using right now and as we explored more with ansible push the limits of its scale are seeing that for what we're doing at the scale that we're working at right now it works really really well a lot of projects like heat that are doing orchestration more at an application layer right now triple O is coming as it comes through and the fact of it is we have to be able to do this now and so ansible is working working really well for that use case issue tracking launch pad definitely we depend on launch pad and Garrett the review system which is the upstream issue tracking however we have internal project managers internal program managers that need to know what's going on and track towards improvements and functionality within the business and so we're right now we're using a mix of red mine and Jira red mine is open source Jira is licensed from is licensed and I think Jira is going to win in terms of standardizing so but but we're using a mix mix of all of that and we have our change gate that integrates with both red mine Jira and launch pad right now to help with the github pull requests run unit tests make sure there's an actual issue number in the commit message update the issue tracker with link backs update github with link backs and this just allows us to have some measure of sanity as changes are coming in internally it is nowhere near the scale or the coverage that the upstream gate provides but it does give us a little it gives us some measure of this isn't going to break everything before it gets packaged and we are looking internally at standing up our own Garrett which is how upstream open stack manages things but haven't gotten there yet so we do have an internal enterprise github that we use it's a secure place secure place for sensitive settings passwords SSH keys proprietary configurations that are unique to us and it's also a sandbox so that we can move our product development forward strategically when we need to deviate from the upstream what we can get into trunk almost there packaging it's actually a great talk later today around packaging from two of my co-workers if you'd like to go into more detail about how we do packaging from upstream at a high level the package artifact is a tarball of project code that's been put into a virtual environment bundled up with the configuration file either the ansible manifest the ansible playbook or the puppet manifest and then uploaded to a package service and distributed via torrent if you'd like to hear more about that and where we're going I strongly encourage you to attend that session and the time I have a slide with the time in the location for you and the last thing this is something I'm we're really actually extremely proud of as the deploy orchestration it's ansible playbooks triggered by Jenkins with some Python goodness underneath it to drive this all forward we upgrade the control plane first we'll do any database migrations if we need to change the database from an upstream patch set and then we upgrade the computes and then we're done when I first started when I first took over this team and really started exploring this space deploys would take six hours they were awful now we can actually do a deploy of our largest data centers in the US with over 6,000 computes in 30 minutes or less that doesn't include all of the process that goes around that and the communication and the validation and the tests running but the actual customer impacting period we've gotten it down to less than 30 minutes and if there's no database changes we've done it in less than 10 and it's just really we're really really proud of that accomplishment when we know we started at six hours so it's a good time so that is my system that is what we have created over the last year and it's really crystallized and matured in this Juno cycle to the point where previously my team was actually doing all of the deployments actually pressing the buttons and managing all of them and staying up and going through all of that operational things actually been able to turn it over to the individual product team so now compute runs their deployments and the network team runs their deployments and we can go on to the next the next level which for me was the ultimate measure of success was to be able to automate myself out of a job so I could go do something else I could go work on the next cool thing I've mentioned iterations a couple of times and I just want to give you some insight into how we're handling the crazy code of upstream plus internal plus configurations so like I said everything starts upstream with open-stack trunk we have a rack space master that we keep where we have our patches and our configurations we pull that down daily into rack space development using that ply process in the patch management system every day we're going to branch and tag inside of git inside a github the code for that day and create a package and deploy it to a continuous integration environment and run some validation on it so that's going to happen every day it's not always successful actually quite honestly it's usually not successful just because of the nature of some of the technical debt that we're carrying internally it causes a lot of conflicts and you have to stop and resolve and move on but on the days when it just goes all the way through the tests are green that's we actually do celebrate and we do celebrate and then periodically and there's not a set cadence it's really based on business need at this point there will be a periodic release branch selection for an iteration from one of those daily daily branches and tags that that went through and got a good a good green run and it's really up to the dev managers and the product managers of each of the products to determine when that's the right time to do it because deploys are impactful to the customer you do have to be a little bit selective on when you actually go alright so we've talked about the tech side what are the what's the software that we're using how are we putting it together not getting too deep into the weeds but just giving you an overview of what we've accomplished and how we're doing this this is the process that we're following and I can argue that it is more important in a lot of ways than the technology as great as it is to get down to 10 minutes to deploy a large data center knowing what we have to do to get there is really really important so the first half of this and I'm gonna go through it so you'll have larger and you can actually read it the first half is our iteration CI CD this is the daily the daily stuff that we can do for the continuous integration and delivery then the second half is going into a more traditional change and release management process where you stop you schedule you communicate you check and then you go and all together this is an iteration cycle and we may do this multiple times off of one major release branch so that we can not have to go through quite so much ramp up time so let's go through the first part which is the CI CD start so as I said we start with open stock continuous integration all the time always always always that's where we want to start then we're gonna merge in local patches and go through the packaging which includes the configs and then we're going to start into the continuous integration continuous delivery by deploying it to our CI environment it's a very small environment less like less than 20 hypervisors with a single with a control plane in a single cell this is really just telling us with automated testing does open stack work with what we have to put on top of it to make it work internally for the business once we have a good a good go there we promote it to actually selecting a release branch and we're deploying it to a test environment which is a little bit bigger has more comprehensive test coverage and is actually starting to do some integration testing it'll integrate with the storage so with cinder and so with cinder for the volumes it's going to hit more of on our identity side so we'll have a more in-depth validation there and from there once we're good there that's where a dev manager a product manager or the change and release manager can say okay it's time to actually cut a release branch and start working on a candidate an actual release candidate and that's this step here the release candidate process takes place in pre-prod which is a shared environment right now and so we do actually communicate out to the internal internal consumers quote-unquote of this environment to let them know hey it's going to be unstable because we're putting new code in there so we're going to take that package exactly from that previous test environment and deploy it to pre-prod run tests and see what doesn't work this is going to have even more integration this will be a full integration with the entire business all the notifications all the way to billing and we'll and we'll be able to see how it's how it's functioning if we find a issue most often it's a config setting wasn't quite right didn't get caught or just isn't tweaked correctly can do a pull request straight to the release branch go go back through the packaging process and then redeploy and you can repeat those steps over and over until you get that really solid release candidate that everybody's comfortable with this can take a week to three weeks depending on what's going on and how bad it is if there is a bug that made it through made it all the way down here and most importantly it's not for feature development this is just for stabilization this is just for tweaking things getting that last thing out so that you can actually deploy it to production and that's the last step schedule the maintenance take that package that you validated in pre-prod deploy it to production do some automated testing to make sure everything went okay and you're done and so that's that's the train that we're following release pipeline release train and it has worked fairly well overall takes a lot of people but in terms of dev managers change and release managers and is not the optimal we really do want to be with continuous all the way through and to automate this all the way through but right now open stack is not quite ready to support non disruptive deployments which is a requirement for that so what are the limitations of our release train we're not at a production scale in our lower level environments the largest environment is pre-prod with around 200 hypervisors none of the other none of the production regions are that small anymore the shared train right now is being shared between compute and network and it leads to blocking issues where network can block compute or vice versa and they can't ship their products ship their features multiple trains however will lead to coordination overhead between both automated systems and human beings individuals just being able to communicate what's going out when am I gonna overwrite you are you gonna clash with me and because we have to really stop everything and schedule a production deploy the flow through here is not is just not continuous at all production deploys are disruptive they have to be done after 10 o'clock local data center time so in the u.s. that's for those of us that are in the u.s. that staying up from 10 until 2 most often 10 until between 10 and 2 and then our international data centers those are during our daylight hours they can be 10 p.m. and that's one of the the major things that stops our flow there is a lot there's been so much great work done around that around how to make these deployments less impactful and one of my other colleagues will be giving a talk on Nova conductor and the road to less impactful deployments later today as well which I have a slide on here in a moment so what are we doing about this what can open stack do about this what is rock space pushing to do this is a quote by Martin Fowler talking about the microservice architecture some of you may recognize it as so a and so that's another another way of saying there's still lots of room to mess this up to but it's really about independently deployable services and open stack within the projects already have independent services each API registry worker is an independent separate entity that have common characteristics around their capabilities automated deployment intelligence in the endpoints and decentralized control of languages and data truly the microservices architecture it's a buzzword I like it better than so a just because it sounds new and cool but but really it's it's giving us the opportunity to empower the dev teams to do that if you build it you get to run it to avoid the monolithic nature that we have right now with our open stack deployments and really empower individuals to to be successful all the way through so what we're doing right now is neutron is ready and able to deploy independently or actually they will be into duration 11 that's the main thing as well with that neutron API and then up next is glance and stack tack because we use stack tack for our monitoring and notification things and then we're going to end up taking Nova out into its own packaging as we go we're converting from puppet manifests to the ansible playbooks for the configuration management and enabling each team within rock space to fully own their packaging their their software development their operational their packaging their deployment their testing it's a great great thing it's a great thing makes everybody have that ownership and we'll see how this comes about in the next couple of cycles as open stack itself realizes their growth challenges and that within each of the you know that each of the major projects there's only so many reviewers so many leaders how do you split up the work and they talk more and more about dividing on on sub on sub project lines so at the service level I mentioned there was a couple of talks today that were relevant up at 1150 in this room is the road to minimally impacting live updates of the rack space public cloud this is really going to go into some detail around how Nova conductor works as far as we can tell no one has used it yet at scale so this will be this is an experiment for us on how it will operate and function no one knows how many Nova conductors you need so we're gonna find out and let everybody know and then the second the second talk today is at 330 1530 building the rack stack and so it's packaging from upstream open stack and on that one they'll go into a lot more detail about how how the virtual environments are created how the packages are distributed and where we're going in the future that's an amphitheater blue which I saw in the science you should be able to find it if you'd like to go to that one but the thought I'd like to leave you all with is from the principles behind the agile manifesto today I've heard this week I've heard a lot of talk about how scrum doesn't work we open stack is an agile and scrum and agile are not synonymous scrum is a flavor of an agile framework and so our highest priority is to satisfy the customer through early and continuous delivery of valuable software and I think for all the developers I know all the operators I know they want that to be the case and so so for that I I look to the future as we continue to pursue the continuous delivery and deployment as we continue to pursue making this work making this easy at large scales at small scales for all use cases and I look forward to what we are able to accomplish in kilo and hope to be back to give you an update then so thank you very much and I'm happy to take questions hello can you could you please tell a little bit about testing tools that you are using for all all of the things so on the upstream on the upstream pieces we're using so I'll just go back to this one so upstream and continuous integration we're doing tempest we rely on tempest once we get downstream of of of the code on the testing here we're using a tool called a cloud cafe to validate that the instance goes all the way through not from API calls all the way through to pingable so it tests on the data plane also yes it tests that the instance is functional at the end and that is that is the requirement for all of these gates is that you have to be able to boot usable instances and usable includes network and thank you cloud cafe so CLO UD CAFE and it is I believe it is open-sourced on the rack space public GitHub and he's shaking his head yes so he's agreeing with me so yes plus one it was it was developed internally by by the by the rack space quality engineering organization so yes say that again the question was we're not using rally for the performance data I am not as familiar with how we do the performance testing so I am not certain what we are using for the performance testing data we may be I would imagine it's still cloud cafe though because that is pretty pretty well established in the QE organization looking to see if there's anybody here that would know but no yes sir on your early slide you mentioned that in your cloud and you have about the two thousand compute nodes so I'm just wondering and on average how many VMs one computer you host in your in your cloud it's going to depend on this on the flavor of it there's multiple there's different types of hardware in in each cloud in each data center and the type of hardware is going to determine the number of VMs and it's also going to depend on the size of the VM there are certain hypervisors in the standard kind of in the standard flavor line that can only hold 130 gigabyte you know 30 gigabyte instance there are and that same instance would be able to hold maybe five eight gigabyte instances for example so it's really it's a math equation of how many 512 slots do you have and then what size flavor are you doing okay so maybe yeah I know it depends on the software right on the hardware out of the servers and the configuration of the service up at the on a box numbers so like what the range we're talking about right like on the low end on the high end so what are numbers I am not able to just call up the data plane numbers from my head the VMs yeah I'm not I'm honestly not certain about those numbers I think it's just gonna vary it's it's too big of a range and I don't I don't have that number in my head I can help you find it out though okay okay sorry yeah that's fine my next question is so with all those 2,000 computer right so how many like the open-state controllers right you use too many are using the hierarchical models we use cells to manage the compute so how many control nodes you control nodes the control nodes there 2,000 control nodes and 20,000 compute yes sir hi firstly thank you for your talk I think what you presented was dynamite today thank you tell us how big is your team to achieve this right now there's four I can tell you it's not big enough at one point my team has gone through a crazy I could probably give a 40 minute talk just on that a crazy evolution we started as a team of three full-time employees with a team of four thought workers who's a really valued consulting partner spread out all over the country and all over the world we had India South Africa and all of the time zones in the United States and it was a nightmare and I don't know how we accomplished this but we did and so at its largest it was seven now we're down to four as people have moved on to other projects as we've accomplished what we set out to accomplish but yeah it's it's it's about five is where I would say we're at thank you sir thank you for your talk could you come back a few slides where you have the iterations and the deploys that one yeah what makes it within an in iteration what did what determines the number of deploy that you actually do you know at the beginning the number of deploy you're going to do or it's more like you have to adjust depending on if I had my way we would know and we wouldn't do any minor iterations and we would do one deploy for each major branch from upstream and that would be it and then we'd start over however there are business needs so the number of deploys from a major branch is going to be determined by business product needs so it's if we need to launch a feature or five features that sort of thing so the features are within a deploy and then iterations are more a way to group correct deploys into a consistent release cycle yeah if we could really if the ideal is to be able to pull from upstream the stated goal is to be able to pull from upstream every two weeks to play all the way through and then start over that's the state of goal it's it's still not there yet so so yes sir are there any performance metrics that you use as acceptance criteria or is it all functional verification right now it's primarily functional when there is a major change and we're talking like changing the way networking worked when we switched to neutron for example from quantum and melange there was extensive performance testing done by the quality engineering organization for the just the kind of the normal run of the mill every day let's pull down 10,000 lines of new code and see if it works we're focused more on on just the functional testing oh yes you said you reduced the deployment time from six hours to 30 minutes can you maybe explain more how you did that a lot of sleepless nights so when we first we first started part of what we did was in the very first iteration the distribution of the package artifact was part of the deployment and so as the environments grew that distribution took longer and longer so the first thing we did was to to pull the distribution out and be able to do that on its own so that we can do that out of band you know over the course of several hours if we need to in advance of the actual deployment window then we we made use of Ansible to have the series of plays to actually go in and and do in the way Ansible works is you can have a certain number of forks we run 500 at a time to go do SSH tasks in parallel and we have worked very closely with the Ansible community to help them get it working up at scale so that we can SSH through 6,000 nodes in a minute on a task so even if you're having to do 10 tasks in sequence you can actually accomplish that on 6,000 nodes pretty quickly so pulling out the pre-staging and making a making the package a pre-stage action rather than part of the deployment was the number one thing and then it was looking at how do we orchestrate and optimize the sequence of of events and using a responsive piece of software that worked that worked well at scale at our scale that answer it a little bit little bit any other questions all right thank you all for your attention you'll have a great rest of the day


Harry asks, what are your thoughts on a Bitcoin proof-of-work change to combat mining centralization? Lately, we've had the anonymous owner of bitcoin.org, Cobra, come out in favor of a proof-of-work change. There have been voicing concerns about bitmain controlling ownership over three of the main mining pools. The quote here is, as of the last writing, at least 53% more likely of the hash rate is controlled by... and they mentioned three different pools. This is a dangerous level of centralization. Is this a real concern threat to Bitcoin, and does something like a proof-of-work change really address the core issue of mining centralization and control? Or would it only delay the inevitable? What other options would be available for Bitcoin to combat hidden pool ownership by large actors such as bitmain? If such ownership is in fact legitimate? There are good examples of other communities trying to combat ASICs in recent times. I would like to know why Bitcoin itself could not respond in a similar way. An example below. You can read the question yourselves, but it goes on to talk about a recent change in the way Monero does its proof-of-work algorithm in response to the release of ASICs. I disagree. I think a proof-of-work change doesn't combat mining centralization. In fact, it's likely to make it worse. The thing about proof-of-work at the moment is that the centralization is driven by economic factors... that have a lot to do with how quickly Bitcoin went from being CPU-mined to being GPU, FPGA, and finally ASIC-mined over a period of about nine years. This meant that the hardware was being obsolete very, very quickly, which gave enormous advantage to those who had close proximity to silicon-fabrication plants and cheap electricity. That 99% was concentrated in particular regions of China, but those incentives and that economic structure is pretty much over. The reason for that is that as ASICs achieved the highest level of silicon density, not about 16 nm, but now moving towards 12 nm of silicon fabrication, there is no more 1,000x performance improvement available in the next level of silicon-fabrication density. We've already hit the wall, Moore's Law applies, and now you can get maybe a 2x improvement in performance over the next 18 months. Even that's doubtful because at these levels of densities, we're reaching the end of Moore's Law in a traditional sense of chip density. What does that mean? That means that this silicon, these ASICs, this equipment, when manufactured now has a shelf-life that is more than two years, not just two months, and that means that it can be deployed in many other places where there are a set of favorable conditions, which includes both cheap electricity, low operating costs, but also several other considerations, such as political considerations. In fact, the concentration of mining in China is a disadvantage for Chinese miners, too, because having too much mining in one place makes you susceptible to political coercion and extortion. It also increases the risks from natural disasters, electricity shortages, a fire in one of the warehouses, or some other situation like that. I expect we will see that the centralization of mining is already reversing itself. It's going to take several years until that plays out, but we're beginning to see the emergence of other manufacturers making ASICs and other locations vying and competing for this. Let's play the other side of the game, which is what happens if you did a change in the proof-of-work. First of all, that would devastate the security of the Bitcoin network, and maybe you can do it on a smaller network like Monero. But quite honestly, Bitcoin security is the most robust level of security that exists at the moment, and a change in the proof-of-work would basically reset that, and all of the investment in ASICs would be wiped out. But that also means all of the existing security investment in Bitcoin would be wiped out. We're talking about several billion dollars of industrial-skill infrastructure that secures Bitcoin against various forms of attack. That's not a good thing, and it's a very, I think, cavalier suggestion to simply change proof-of-work. Also, I don't think it would be effective. I think an attempt to change Bitcoin's proof-of-work would be a contentious fork... that would not have majority consensus and, as a result, would result in a fork of Bitcoin, a contentious fork... that would split Bitcoin into Bitcoin SHA-256 and Bitcoin something else, and the Bitcoin something else would have a very hard time rebooting its security. Also, who do you think would reboot that security faster? So, let's say the proof-of-work algorithm is changed, maybe made a bit more ASIC-resistant. Well, theoretically, the very same players who have a couple billion dollars of liquid cash available to them, all of the operating expertise, manufacturing pipelines, relationships with silicon fabrication, and access to an expensive electricity, you think they might have an advantage in rebooting their entire operation... and investing in the new proof-of-work algorithm? Arguably, they would gain an even bigger share of the new proof-of-work algorithm mining and manufacturing facility... because it would set back everybody, only they would have the advantage of eight years of experience, two billion dollars, and existing relationships with manufacturers. So, I think it would actually undo the effects of competition that we're already seeing taking hold in this space. So, no to a proof-of-work algorithm change, no to shooting Bitcoin in the foot in order to really deal with a threat of centralization... that I think is already waning, and no to giving more power to developers or other parties who make unilateral decisions... about proof-of-work algorithm and split the consensus of the network. Is a hard fork still a valid option in case of emergency? In case it's needed to hard fork Bitcoin for any reason, is that still a valid option? Now that Bitcoin has started to have a lot of users, would that not be a big mess? And in your opinion, what threat or event could lead to a hard fork? Thanks. So, I think the question here really comes down to what we mean by a hard fork. A hard fork in itself is not necessarily a bad or disruptive thing. A hard fork, if properly planned and supported by a majority of the system, meaning the economic actors, the users, the merchants, the exchanges, the wallets, the miners, everybody is on board. Everybody agrees this needs to happen, or at least the vast majority of the participants in the system agree that a hard fork needs to happen. And it's planned, and people are willing to put in the effort to upgrade their software clients, so as to effectuate a fork. And it's properly executed and well-developed, and high-quality code is produced. Then a hard fork can be done, and it can be done effectively, and it can be done with a minimum amount of disruption. There are some cryptocurrencies and blockchains that regularly do hard forks, either to respond to problems. As we've seen with, for example, denial-of-service attacks in the Ethereum network that involved poorly chosen values for gas. And in that case, Tangerine, Whistle, and Spurious Dragon, which are some funny names for a couple of the hard forks that were introduced to solve those problems, were executed very effectively and on a fairly tight timeline. There are other blockchains that have regularly scheduled hard forks every six months in order to introduce new features that are backwards incompatible. That's generally not the development culture in Bitcoin. Bitcoin has a much more conservative approach to its software management, probably because there's a lot more at stake, and it's a much, much bigger economy and user community. But nevertheless, that doesn't mean that a hard fork can be pulled off. Contentious hard forks, where a small part of the network wants the hard fork and the majority doesn't. That was our very problematic, and these can lead to chain splits, as we've seen in the past. But let's say, for example, you asked me what threat or event could lead to a hard fork. Let's say, for example, that the fatal flaw was discovered in SHA-256 that would very quickly lead to a compromise of the proof-of-work algorithm and the weakening of the security of the chain. It's very likely that under those circumstances there would be a broad move to change the proof-of-work algorithm. That would be quite disruptive, and the reason for that being very disruptive is that there is a lot of deployed infrastructure in the form of A6 that would become obsolete with that hard fork. That would require a refresh of all of the mining hardware. Now, that's not entirely impossible. Keep in mind that up to very recently, as the pace of development in A6 was frenetic, many of the mining companies developed the skill of being able to completely refresh the majority of their A6 infrastructure every six months, because those A6 were basically becoming obsolete within three to six months of being deployed. So, it's not unthinkable that you might need to be able to execute a proof-of-work change algorithm. The mining companies, if it was in their interest, would not only go along, but would be able to quickly refresh probably within six months of their hardware infrastructure. Another possible event would be discovering a fatal flaw in ECDSA, or discovering some kind of weakness, or discovering a more widely available, powerful enough quantum computing system that could start negatively impacting the security of ECDSA. Now, in cryptography, these things generally don't happen overnight. Cryptographic algorithms that have had flaws like, for example, the data encryption standard, DES, or MD5, or SHA-1, these algorithms didn't just fall apart overnight, and they didn't go from completely robust to completely useless overnight. Instead, what happens is weaknesses were found that changed the effort required, and they changed the effort required so that it became feasible for very well-funded adversaries to start attacking these algorithms, but only over long periods of time. And still, there was plenty of time for organizations to retool those algorithms. So cryptography generally... there are exceptions to this rule, of course, but generally speaking, cryptography weaknesses do not fatally compromise an algorithm once and for all overnight, and in such a way that everyone can break it. Instead, they weaken it, and they weaken it such that we anticipate that, six months from now, you can do it for less than $10 million, and less than a warehouse full of equipment, so we'd better start changing things up now to protect against that eventuality. So in those cases, we might need to implement a hard fork. But then again, some of these problems, perhaps many of these problems, can be solved with a soft fork, too. It remains to be seen. I think it's still a viable option in an emergency.


Emerging SARS-CoV-2 amicron sublineages B.A.4 and B.A.5 rays concerns about potential immune evasion. Show that both B.A.4 and B.A.5 are able to escape immune response induced by prior B.A.1 infection, but that this effect is less pronounced in vaccinated individuals. This article was offered by Khadija Khan, Farina Karim, Yoshika Gonga, and others.


Welcome back to esoteric Atlanta. I am joined today by my friend, Jessica Jones, the cryptic huntress. How are you doing today, Jessica? Okay, Bryce, I'm doing excellent. How are you? Thanks for having me. So good, it's been a while. It's been so crazy. I'm so excited to have you back to talk about what we're gonna talk about today, you guys. Make sure, if you're not subscribed, make sure that you are subscribed to the cryptic huntress on YouTube. You're close to 10,000 subscribers, girl. And you guys, Jessica and I, we're just talking about this off camera. Make sure that you are still subscribed to our channels because we've both been dealing with the same issues on this platform that are out of our control. I will just leave it at that. So I will put all Jessica's links down in the description box below. And yeah, you guys, let me stop share quickly. Now I had Jessica, I love that I have a remote viewer friend where I could just text you and be like, I need you to look at something for me. Because I discovered this case when I was traveling, I heard it on a podcast. Whoops, let me actually hold on one second here. I'm gonna pull up the brief little video I did on it a few weeks ago because this case was so fascinating to me, so wild. I cannot believe I'd never heard of it before. And this was the Granger Taylor case. So it's this one right here. So I'll link that down in the description box below. If you guys missed that one are not familiar with the Granger Taylor case. And as this works, Jessica, you didn't know what you were remote viewing when I sent you the coordinates, did you? No, absolutely not. I got a set of coordinates. You sent me eight numbers and that's all I had because I do something called coordinate remote viewing where I'm given a set of coordinates, which are just some random numbers that are assigned to a target. So you had this, I guess the disappearance of Granger as the target in the circumstances surrounding it. So that's, but I didn't know that. I just had those numbers. And I got a lot of really cool data on this one. You sent me, as you often do, after she remote views it, she'll send me pictures of her notes. And she'll be like, does this make any sense to you? And I was like, girl, where do I start? So I'll send you a link to a podcast. So just briefly, guys, again, you can for details, you can go and watch the episode again. But just before we get into your data, Granger Taylor went missing on November 29th, 1980 from Vancouver Island up in the Pacific Northwest of Canada, very small town. He lived in called Duncan, which is a logging fishing city, very working class. As of 2021, the census was only about 5,000 people, so very small town. And he was kind of this like savant. He was very smart. He left school in the eighth grade, but he made kind of a name for himself of being this like genius mechanic where he could just like bring life back into old, you know, railroads. He got really obsessed with extraterrestrials. And around 1980, as she started to think that these extraterrestrials were telepathically talking to him and that he was gonna be picked up for a 42 month gal event around the galaxies, which is 150 years for us on Earth. And he did disappear on the day he told his friends they were picking him up. The police up in Canada believe they found his remains. We'll talk about it, but that's kind of the brief overview. So I'm gonna pass this over to you, Jessica, and let you kind of talk about your findings before you knew anything of what was going on with this case. Okay, so the first thing I asked you was, Bryce, was this a missing person? Because that was the entire session of my remote viewing, this session was obviously, to me, it looked as though there was a missing person. Okay, and okay, so let's just start with some of the sensory data. Okay, so what I do, I'll explain to your audience, who for anyone who's not familiar with remote viewing. Okay, so remote viewing is something that our governments use. The type of remote viewing that I do is called coordinate remote viewing. Now, remote viewing is a scientific way to psychically locate a target. Okay, or locate a target that's blind, you don't know what it is, using your psychic faculties, basically, after being given a set of numbers or coordinates. And like I said, the governments use them, our military was using remote viewing back during the Cold War, still using it today. I speak to soldiers occasionally who tell me they have a remote viewer assigned to their unit when they're overseas and stuff. So, especially the snipers, things like that. So we do use that. I think governments and militaries all over the world have used it. I'm trained in different modes of remote viewing, and it's something that I've been doing for a long time, and I love it, it's my favorite hobby. Okay, so I taught you, Bryce, how to task me with a target. And so you gave me the numbers. I got seven, eight, seven, eight, six, two, four, seven, I believe, for the numbers. And that's all I had.  And I draw out some charts, and I have stages, stage one, stage two, stage three, stage four, stage five. You can go to six, whatever, or seven. I mean, there's a lot of stages you can go to.  So I pick up on a lot of sensory data. That's what we're going for, sensory data. Anything that I taste, sense, see, touch, feel, whatever are here. And so some of my sensory data on this target was, okay, so I wrote rolling, waiting, or waiting, fast, flighty. I was picking up on something feminine, okay. So something feminine, broken, loving, wounded, and missing. I actually wrote down missing, okay. And so my analytic overlay, this is just some of the key things that I was seeing, but I was trying, I was like analyzing what my sensory data was basically is what this is, okay.  So I was definitely, there was definitely a vehicle involved. I wrote vessel, fast forward, fast movement, uprising, rebel soul in a rebel. I wrote down going with the flow. I picked up on a heartbreak. Somebody that was having a heartbreak, a heavy heart. And then I picked up on a feminine energy in the environment. I said feminine, and so I wrote down a young woman or a woman, but I kept hearing there's lots of love to give, lots of love to give. And then I wrote down missing person. Missing person, and for my stage three drawing, I wrote down a mile marker on a highway, okay. And it had a number nine in it. And I could not get it out of my head. There's number nine in this mile marker, 919, 908 or nine something. And I actually, yeah, I actually drew that for my stage three drawing right there, okay. But I also, yeah, I guess that's it. For the first three stages, I was very much picking up on like a rebel soul who had gone missing, okay. And, but there was kind of going with the flow. And I was picking up on something to do with a broken heart, or there was something to do with like a heavy heart in this person. So, yeah, do you wanna, do you wanna give me some feedback on that before we move on? Yes, let me switch it here. I was actually gonna suggest that cause there's a lot here. Cause I know some of the other stuff you got. So vehicle, we know that Granger Taylor was very kind of eccentric. I speculate that he might have had Asperger's or been on the spectrum because he was very much a savant. He was very highly intelligent. Like I said, he could bring anything mechanical back to life.  So I think sometimes it helps to have a face with a name. Granger Taylor, he was also known to always tell the truth. So this is Granger right here. And if we know anything about people on the spectrum, they always tell the truth, right? Even they don't know how to lie at all. So that was always the big thing. Now Granger, I think it was 32 when he went missing. He even built his own spaceship. And he was interested in how spaceships worked. That's why he built his own spaceship where he would spend a lot of time. This is when he believed the extraterrestrials were contacting him. Now with the vehicle, this guy, Robert, was a teenager who worked with Granger. And he helped Granger paint his truck like a Pepto-Bismol pink color is the description that Robert uses. And we do know that Granger Taylor drove away like the last anybody saw Granger drive away was 6 p.m. on November 28th, 1980 in his pink truck. Now that does come into, back into the story when the RCMP believe or are in, what is it, the Royal Mounted, what are they called? The RCMP, yeah, like the three letter agency of Canada, when they allegedly found remains of Granger's truck at a particular mountain in the area on Mount Prevo that's on Vancouver Island. Now there is speculation on whether that was actually Granger's truck or not. So the vehicle does make sense that he drove away in the vehicle, now heartbreak and feminine. So you see this dog, he's gotten his hands right here. This is his dog, Lady. And this breaks my heart. He loved that dog so much. Lady was his, the love of his life. As far as I know, nobody was dating Granger if you know anything about some forms of autism or Asperger's, that makes sense that there was not a whole, didn't seem to be a whole lot of romantic interest, but he loved Lady so much. And he actually left provisions for Lady. I mean, he was a very wealthy guy. He made a lot of money creating his machines. And so I can't, he knew he would never see Lady again because he was gonna be away for 150 years, Earth time, which is 42 months in the galactic time. So I got two hits when you said feminine heartbreak. Lady, the dog, which anybody who's a dog owner probably understands that.  Here's the letter that he left his parents on the night that he disappeared. Dear mother and father, I have gone away to walk abroad an alien spaceship. Sorry, let me get my glasses. I'm gonna show my age here in a minute. I can't see that, y'all, it's too small. Let me get my glasses here. All right, much better. I have gone to walk abroad an alien spaceship as reoccurring dreams assured a 42 month interstellar voyage to explore the vast universe then return. I am leaving behind all of my possessions to you as I will no longer, as I no longer will require the use of any, please use the instructions in my will as a guide to help love Granger. So this is the letter that he left on his parents door to their bedroom when he left. His mother, however, was away in Hawaii when he left. So she never had a chance to say goodbye to him.   So I took that to mean that Granger did not see himself as somebody that was going to get married, going to have children, but he saw this young boy had an opportunity at really living life here on earth. And he told Robert, when I come back, I will come and visit you. And Robert knew that meant he would come and visit his grave when he came back. And after 42 months had passed, people in the town did believe Granger was up on a spaceship because he never lied. He never had no reason to lie, you know? Robert was the one that was like, you guys know it's not 42 months earth time. It's 42 months galactic. We're not going to be here when he returns. So anyway, do you want to, does that make sense to you, Jessica? Totally. Yeah, it does. It's really, it's kind of sad. You know, we love our dogs. You know, I couldn't imagine leaving my dog or why I also have a kid too. Like I could, I couldn't do whatever he did. But yeah, that makes a lot of sense. It does. Now there's some more, okay. So in my stage four data, some things that you mentioned already, or in my data, and like, you said something about his truck being Pepto-Bismol pink, right? I picked up on a bright pink color in my data actually. So the first bit of information, the first bit of data I got for my stage four remote viewing part of the session, I was picking up on something that was very strict. Now to me, I was interpreting that what I was sensing as like a religion, but it was something very strict. Like he was very dedicated to whatever this was. So I wrote down religion. And in my, you know, with the AOL, I was right now like Mormon Catholic Baptist. Like I wrote down all of that because I was like, there's something, I couldn't put my finger on it, but there was something that was super, he was super, whatever I was remote viewing, it was very super strict in whatever this was, okay? And then I was picking up on some bright colors. And the first color I wrote down was bright pink. Okay, so, but I was writing down, I was sensing like, like the colors from like the 1980s and the 1990s. I actually wrote down, I actually wrote that down. And from like pink, green, blues and yellows, something super. And I actually wrote down in living color. That's a move like that show from the 1990s, you know, because there was so much color, a lot of brightness, a lot of bright colors were in here. I also wrote down acid washed, okay? So acid washes in my data. Okay, but then it started to get a little more ominous in the data because I wrote down, I was feeling tempted, like something was tempting. I wrote down tempted by fate. And then I was somewhere, okay, so I'd written down, like I felt like I was on a highway and I wrote down a mile marker. Well, I was, in this part of the data, I was sensing a fog and a mist. I wrote down nighttime in a car on the highway or an interstate is what I wrote down, okay? And then, then I actually was feeling, okay, so I wrote down hitchhiker. I actually wrote down hitchhiker and then my sensory data was lonely and alone. Okay, so somebody was lonely and alone and I actually wrote down the phrase solo dolo. Okay, so I was getting a whole lot of hitchhiker data. I wrote down truck stop. So I don't know if there's a truck stop that he may have passed or if that's even a part of it, but I was picking up on an actual truck and a vehicle. So I wrote down in my tangibles, which was like I was actually seeing it. I was sensing, I saw an actual truck. Then I heard last scene and then it got super ominous because I wrote down attempted kidnapping, attempted murder. I wrote down serial killer vibes, snuffed out, silenced. And then at the very last, the last bit of data I got was deafening silence. And then I ended the session because I didn't feel like there was anything else that I could possibly get at that point from this because I felt like someone had been unalived at the end of that target. So that gets kind of into the theories of what actually happened to Granger. So let me kind of, and I'd love to see your opinion based on what we know. So in March, so he went missing in 1980. And most of his family, so in his will, he changed the word deceased to departed. He asked for no funeral because he wasn't, he's no longer gonna be dead. When you say he was tempted by fate, I feel like Granger was so smart. He said that the aliens needed him. They needed his intelligence. And I feel like for him, this wasn't an egotistical thing. Like he saw other humans having relationships, having families, this was his fate. He wasn't gonna have the wife and the kids, but he was gonna go help the aliens, right? With their mechanics. So he goes missing. Now there's no evidence of him for six years. Then in March of 1986, news reports claim they found Granger's truck on Mount Prevo. As I had said, this is a mountain northwest Duncan at the top of the North Bluff is a war memorial.  So the blast site with pieces of truck and a crater workmen found it. They found a VIN number that was registered to Granger Taylor. Now the RCMP said that this truck was blue, not pink. I wrote down blue and pink in my data. That's so cool. This is interesting. And so a lot of people have pushed back but there was a journalist I listened to when I was researching and I thought he had a good point. Sometimes we have to look at the original color of the car because sometimes when the VIN number is registered, it's registered with its original color and not the color it is when it, and if it's a blast site, you might not be able to recognize color anyway. All right, so this, and this was, now there's a lot of weirdness around this. Like the RCMP has been a little sketchy with this. And this leads to some of the conspiracies around this. So the blast site was a 200 to 300 foot radius truck parts as far as 60 feet up. This is way too big for a normal blast site. Many experts that are very well versed in dynamite say that this is not, the math ain't mathin', right? Like this is not adding up. So now here's the thing about dynamite. So Granger did work with dynamite as part of his job, it makes sense. Like he was not a stranger to working. Now the thing about dynamite is that, I didn't know this, but when you purchase it, it's registered. They have to know who's purchasing it. And Robert, so basically the theory was that he went up on the mountain and he unalived himself by setting his car, right? A blaze. But Robert, the little kid, went back to his workshop and found all of his, his dynamite was all accounted for. And there was no records of anybody, Granger, anybody matching Granger's description buying anymore. And again, they have to log this every time somebody bought in Canada at least, at least in the 1980s. So they also found human remains. And they found clothing that the RCMP claimed a family member said was Granger's, but the family said they never asked them to ID the clothing. Oh my God, that's something that I, okay, I don't even think I said this. I think I skipped over it by accident, but I actually wrote in the tangibles, I wrote clothes. And that's where the bright colors came in too, was pink, green, blue, yellow, 1990s, 1980s colors, but it was clothes, so wow. Interesting. And Robert, the kid brings this, okay, so when we look at the human remains, they found two bone fragments and they were determined to be human, but they could not DNA test them back in 1980. They don't even know if the DNA at the bones, the DNA was male or female. Now, 2024, they could, but guess what, you guys? Uh-oh, oops. It's gone. Awesome. Are you kidding me? Oh, I mean, do people know where the site is? Could we, you go up there and kind of dig around for evidence today? Oh, the site is also known. This mountain is known for planes to crash and this mountain, they're never found again. So the fact that people even found this is a miracle in itself. Oh. And Robert was like, how the hell did a sweater, a wool sweater survive when the truck and the body didn't? I know. It's like never with passports. Like those passports at 9-11, right? Exactly, exactly. The family was never freaking comfortable. Suspicious. So again, the math ain't mathin' on this. Like, you're telling me that the biggest police force in Canada just, uh-oh, lost the bones of one of the most mysterious missing people cases in Canada? And they never talked to the family? They just told the family the case was closed? I think there's more to it. Because, I mean, especially with the data, saying that there was, I mean, this is just data. Okay, so data where I'm not solving any crimes here or whatever, but it is interesting when you look at the whole case and then I'm picking up on some kind of, like he potentially had someone with him at some point. I was picking up on, he got snuffed out. That's unalived. That's not like them doing it himself. That's somebody else doing it to him. That's another theory that the government took him out. Well, there was an attempted kidnapping, I do believe.  He didn't silence himself, he was silenced. And that was one of the theories. So, you know, of course the main theory is was he picked up by UFO and did they just discard the truck? Like that was my boyfriend's first who he listened to and he was like, did they pick him up? And then the craft was like that with the truck, like we don't need this, like threw out the car and zapped it, like, you know, but then there's also what we know about the government and their interference with thoughts.  I don't know. I don't know either. I didn't pick up on any kind of data like that though. I did pick up on, okay, so this, according to the data, that's all I've got right here. To me, it looked as though he made a pit stop and he picked somebody up. And that's, and maybe that, I mean, who knows who that person was? And something happened from there. That's what I picked up was that there was someone else involved and he was silenced. He was, he was unaligned by somebody else. But that would be interesting. I would like to know, because it's been 44 years, you guys. So if you're from the Canadian area and you're familiar with this case or this family, I would love to know, because that's not information anybody has ever shared before. Do you know if he was seen at a truck stop? Do you know he was a very kind guy and he called him a gentle giant. So if somebody needed a ride, I'm sure he would have accommodated.  I mean, this is a guy that people trusted. You know, and there was no reason for them not to. So your opinion, Jessica, is he's probably not in the galaxy. Not according to the data. According to the data, he has passed on to another realm. Okay, you know, when you were saying that, that he was saying that he wanted to, he had a job to do with the ETs or whatever was going on. I mean, I'm thinking on the terms of like inter-dimensionally and stuff and like maybe leaving this body behind and going into an inter-dimensional realm, you know, into the next two air trucks. Maybe he knew he was going to... That's the vibe of the thing is you were talking about that. Yeah, I mean, maybe it was just like, what is that cult? Okay, that they all wore the Nikes and they drank the cookies. Heaven's gates. Maybe it comes from the same time, right? Oh, could have been, could have been. So he was willing to lose his life and his body to go positive for the good of outer space for ETs. Yeah, I mean, that's wild. Yeah, I didn't even consider that. So that could have also explained like the heartache and the heartbreak that he was not only leaving his dog and his family and his friends behind, but he was also leaving this earth behind in general. His meat suit. Yeah, maybe. It's an, it's a, I'm throwing a wrench in the engine. Okay. But that may not be an impossibility. You know, that's, why not? Yeah. Do you think the person he picked up had anything to do with his departure? Like, was that an extraterrestrial he picked up who had incarnated shapeshifting into this existence? Oh my God. I don't know, that's going out on the limb. I mean, anything's possible, but I don't know. I think it was, to me, according to the data, it looked as though it was just a, somebody that had bad intentions is what it looked like for the data. But in my personal opinion, I don't know. I mean, that's, it's just a wild case. It's so, so freaking wild, man. I don't know. You know, I watched these like incisories and tech talks about like, you know how on Dateline and all these like true crime, they're like, she lit up a room when she walked into a door and people are like, if something happens to me, don't lie, just be like, she had two friends. She wasn't everyone's cup of tea, like, be honest. And I think that's what's so, so sensitive about Granger is Granger, like, literally everybody, no one had anything bad to say about him. He was such a kind person. You know, he literally was that Dateline.  And that could have been part of his demise, was just not having the common sense, you know, to, to stay. Did you pick up anything about the weather? Let's see. Yes, I wrote down foggy and mist. Because they called it, that night was the storm of the century. Okay, yeah, I picked up nighttime in a car. Yep. On a highway or an interstate. I couldn't figure out, I wrote down both, because I wasn't sure I was, I wrote down highway interstate and there was a foggy mist. I would love to know if there's anybody watching from Vancouver Island or who is familiar with Vancouver Island, because Jessica and I were two Southern girls. We're from the South. So we don't know much about the Pacific Northwest. So if you're familiar with Vancouver Island, can you kind of in the comments section or in the chat give us your impression of this and like the mile marker and what on Vancouver Island is it more of a highway or is it more of an interstate? Like what is that like on Vancouver Island?  But I don't miss Vancouver. Northwest, it's a very different story. So let us know, cause I think that's very interesting too to have someone's perspective who's from that area. Because I still feel like Jessica today, it seems like there's a mixed opinion over what, I think some people really do think he's coming back for their grandchildren's grandchildren or something. You know? Well, you know, I just, okay, so last night on space.radio, this over the weekend on space.radio, I have a show on Sunday nights here. And I had a guest from the Catskill Mountains over the weekend and his name is Charles Andrews. He's a big foot field researcher and he lives right across from me. You could see the mountain from his house. It's like a mountain. They just call Rip Mountain or something like that. But it's what the story of Rip Van Wekel was based off of. So this is so timely that we're talking about this right now because the story behind Rip Van Wekel goes, and that's in the Catskill Mountains in New York. Okay, this guy was irritated with his wife. Okay, she was nagging him all the time as to how the story goes. And so he took his dog. This is like a real life Rip Van Wekel almost because he took his dog up to the mountains to go get some fresh air. And he met a gentleman along the way who was carrying a keg of alcohol. Had some kind of substance in it. And but this difference is they were met. He was helping this guy carry this keg up the mountain and there were all these like gnomes. Okay, because the Catskills right there are known for their gnomes, their little people. And the guy, this is before the American Revolution happened, he took the keg up there. They drank that night. He drank a lot, I guess, and he passed out. And when he woke up the next day, he had a long beard down to his, down to the ground.  He stumbled into town. It was like, whoa, that was a weird night. It was 70 years later. And the whole town had changed. He was proclaiming, you know, his loyalty to the crown.  We're Americans now, you know? And so yeah, it's just a really interesting story but he wandered back down. He had been asleep on that mountain for 70 years or he just disappeared actually. Cause I think, I'm sure they went looking for him. Do you think that there is some folklore there that connects to the Granger store? Like maybe that was the Granger-Taylor story of that time. Maybe, could be. I mean, there's a reason that I talked about on my show this weekend. I did my research on Rip Van Winkle. I didn't even know who Rip Van Winkle was. I had heard his name, but yeah. Interesting. We are great. It's so fascinating. Like it is, some people are so torn on this. And so I think consensus is though he's probably not coming back. No, he might reincarnate. Yeah. Who knows? Yeah. Of being Granger. Cause he's never had a funeral. The state, I believe the state or the country has declared him legally dead. I think they have to do that in order to access his money for his provisions for his dog. But they've had no funeral because he didn't want a funeral cause he was gonna be sailing across the galaxy and helping the aliens with their stuff. So I'm gonna pose to our audience, Jessica. I love doing these missing person cases and these like unsolved, I will call them the unsolved mysteries cause some of them are paranormal. If you're down for a Jessica, if you have a case, an interesting weird case from wherever you are in the world that you want me to look into, email me, esotericatlanta.com and just put Jessica in the subject. I will research it and then I'll create coordinates for Jessica. Are you down for that, Jessica? I'm totally down. Yeah, that sounds fun. Try not to make it too gory if you can, y'all. Yeah. Okay. Well, I really do like the missing person's cases. That's why I do that. I love doing missing person's cases. Unfortunately, most of the missing persons are not alive that I end up looking for. But still, it gives some closure to people who don't have answers when their family members go missing and things like that. If anything I can do to help. I've been trained to do it. Why not? Yeah, and I think it's Occam's razor too. I think sometimes when people go missing, we have the humanity in us wants to create these stories that they're alive and they're doing well. But Occam's razor typically is the most likely outcome is probably the outcome of what happened to these people. But yeah, let's do it. Let some guys send me any cases because I really enjoyed this as well. It's, and I think that's humanity helping humanity. And do you think the government had anything to do with it, Jessica? I did not pick up on any government interaction with this. And trust me, most of my targets are government coverups. Okay. So, and I normally would pick up on something like that. I did not pick up on any kind of government interaction on this one. Do you think he was really hearing extra trust rules or do you think he was hearing his own voices? I don't know. I mean, coming from a girl who's had up close and personal contact with ETs, he may have been communicating with the ETs. They may have taken him. You know, they could have taken him. He's gone. But they, yeah, left his meat suit here, I think. Do you know it's interesting to cast opinions that we follow. They warn people not to get on spaceships for this very reason too. And they also say too that just because we think of things like shapeshifting with like reptilians or whatever. Remember, they don't just shapeshift into people or humanoids. They can shapeshift into objects as well. And they say that if you get on a spaceship, chances are you're not getting off. And that's just another good point. You know, we're here on Earth. We're here at Earthlings. This is our home for this life. So that's a cautionary tale. And I think sometimes though, Jessica, I wonder, the law of one talks about this concept of wishful thinking of being like a negative trait. And I think sometimes people confuse intuition with wishful thinking. But with Granger's situation, he seemed sad, you know. Even though this was a trip of a lifetime according to him and like maybe his destiny, he also there was heartbreak, wasn't there to leave. Oh yeah, definitely. I definitely picked up. I also picked up that he was very feeling ungrounded. OK, I don't know if I mentioned that earlier, but that was part of my data. Feeling very ungrounded, like a rebel, like he felt like he, like wild and free kind of, you know, like he was like a rebel soul ungrounded, but he was going with the flow. I had clearly heard that clear audience, go with the flow, is what I heard. So he was really discombobulated, but heard these voices. So he was going to go with the flow of what they were telling him to do. And maybe because he felt ungrounded, that's where he was seeking to be grounded again by following the advice of the voices he was hearing in his head. That's why it's important to ground yourself, guys. Get grounded, that's right. That's a hard lesson to learn. So, well, is there anything else about this case you want to say, Jessica? No, I think we covered all of the data here. And I think that, I think, I don't know. I mean, I hope that you got some answers, maybe, from some of this. And when you sent me the pictures of your remote viewing, I was like, shit, she got it. She nailed it. Because you're like, I remember you're like, is this a missing person? I looked at yourself, I was like, oh yeah, it is. And it looks like you kind of hit the nail in the head with this one. Yes, you do. Now what's going on on your channel? What's coming up this week for you, Jessica, on your channel? Oh, man. Well, I just have shows this week. I've got a show Wednesday at 1 PM live on my channel, The Cryptid Huntress on YouTube. And I got another show on Thursday. I don't even know what my topics are yet. I'm such a lass. I do so many shows and stuff. But it'll be a good one. And I'm at Spaced Out Radio this weekend on Sunday as well. So, but yeah, other than that, I'm going to be at the Georgia Bigfoot Conference. So I know people on your channel, so it's here at Atlanta here. So we got some 80 aliens watching us, including myself, OK. And so. Where's the Bigfoot Conference being held this year? It's going to be up near Clayton, Georgia. It's actually at the Dillard House in Dillard. I've been there. I've been there. I love that. OK, so we're going to be at Dillard. I believe it's March the 15th and through the 16th. It's a two-day event. One of the biggest names in Bigfooting, Ron Moorhead is going to be speaking to. So it's Ron Moorhead, Brooks Agnew. He's my friend. Met him at the Journey to Truth Conference. He is. He speaks on inner Earth and hollow Earth theory. So that he is. We've covered our channel. Yeah, that's I highly recommend. OK, you guys come into here. Ron Moorhead, Brooks Agnew, Matthew Delft, the badass monster hunter. He's going to be there. He's a good friend of mine and my research buddy and myself. So the Cryptid Huntress. We're all going to be up there along with some other people, some vendors, food. It's going to be awesome. So y'all can see what's going on that weekend. Because that sounds like a blast. I've been to the Dillard House. If you're in, if you're close, if you're in North Carolina, South Carolina, Tennessee, Georgia area, it's beautiful. That's where we go hiking all the time. I know that's where you do a lot of your research. Jessica, it's a beautiful. It's where they shot deliverance parts of deliverance. Oh, OK. The Banjo player was at the conference last year. Actually, I forgot his name. Yeah, the little kid, he's an older. He's a seasoned gentleman now. But he was there signing autographs last year. Yeah. So go figure. You know, we got everybody. It's so fun up there. And yeah, it's full of it's very squashy. Yeah, a lot of great restaurants. You're looking for a fun weekend. They've got downtown Clayton. They have like this great restaurant that they have a dog menu too.  So great antique shops. I think my friend Angie, she's up there a lot. She told me they have like a mystical shop up there now. Where you can get like carousels and your tarot cards and all sorts of fun stuff. So if you're close, I would highly recommend checking that out, you guys. Dillard House, it's right there. It's like right beside Clayton. But Clayton, Georgia, if you can't say the Dillard House because I know that might be quite pricey. There's other hotels up in the area. Cheap motels around there. Oh my God, we stayed in a cheap motel. Last time we were up there, we got a real cheap motel y'all and I was shocked. Like we pulled up to the outside and my boyfriend was like, this is kind of sketchy. But then we got into the room and I was like, this is kind of nice. Like it's not so bad for 60 bucks a night, you know? We're not going to be here. We're going to be out hiking. So, you know, I'm just a shower in a bed, right? Shower in a bed, that's all you need. And if you're from a city like I am, it's a dark night when you're up there, isn't it? I love it. That's why I'm a cryptid researcher. I'm a big foot researcher. I've been doing it for a long time. And so I've only stayed in a motel or hotel or whatever. I'm going to say that was a motel that I stayed in. But I've only stayed in one one time because I'm usually camping up there whenever we go. Or I'm at my, one of my best friends, they have a house at Lake Burton. So I've stayed there several times too, but. It's a real funny story before we head out. Do you remember, Jessica, when we had the blizzard of 1993? Oh, God, I was in high school. So I don't know. I think I do. Yeah, I'm sure. I remember it was up to my knee in 93. I was 11. And I remember, so you guys, the Yankees can laugh at us. Anytime it snows down here, the Piggly Wiggly sells out of red water and milk. Everyone thinks Jesus is coming back. Either a little bit of snow.  We lose power. We don't have the equipment to clear the roads. So in 1993, we got hit with a blizzard out of nowhere. I mean, I remember the week before my dad mentioning that it was supposed to snow, but we were like in shorts and a t-shirt. And we were like, yeah, not snow, you know, but it snowed. It knocked out our power. And where we lived, they couldn't get all the power lines were down. So we couldn't even as kids go outside and play because it was too dangerous to go outside and play. It was miserable. We had to pull a mattress into the living room to light a fire. We had to like bundle up. So we lived that way for a week. After a week, we still didn't have power. We lost water. So my parents had to figure out a way to get us into the town, to try to get a hotel room. They called around, all these hotel rooms were booked up because the hotel rooms already had power back. So they finally find a hotel, a motel at the Rome Motel. Oh God. You're Martha Berry Square Mall. Okay. And I'm 11 years old. So I know nothing about the ladies of the night at this point. We get there. It's, I remember thinking this is like a really like dirty, like I, but at least they had a TV and like a shower and like warmth. Pete. So my mother gets my sister and me into the bathroom. I'm sure we were getting put in the bath together at this time because we were probably so stinky and dirty. All of a sudden my mother screams and she goes, girls, get in the living room. So we run into the living room, get dressed, get in the car. We get dressed, we get in the car, we're in my dad's car.  Because it was one of those pay-by-the-hour hotels. Oh my God. So my parents, thank God, found a room at like the holiday in one room that my mom, my dad, my sister, me, my grandmother, my grandfather, all shared together. I didn't care because there was an inside pool we could go swimming. I just thought it was great, we had a pool. But I'll never forget that.  My mother was like yelling at my dad, like he basically brought us to a brothel to get a room at a motel.  But yeah, that's my motel experience from the Rome motel in 1993. Oh my gosh. Well, you have memories of a lifetime then for that, so. Freaking lifetime. I was so scandalous. I think my mother was probably mortified that her daughters, she just kept talking about that peephole, that peephole. Oh, I'd be furious. I would be so mad, because I have a kid. Oh no. And I think I'm like, what's a peephole? I just thought it was kind of dirty hotel. I didn't realize that it was a pay-by-the-hour hotel, you know, a family of four young children coming.  Don't touch anything, right? But I had so much fun once we got to the Holiday Inn, we stayed there for about a week until we got water and electricity back at our house. But I had so much fun, because of course school was canceled. And we, our grandparents were in the room too. And of course, when your grandparents are there, you get spoiled with everything. We could swim in the indoor pool and we got to have like pancakes for breakfast every morning at the buffet. I thought it was great as a kid, you know? Then I think about my mom having to stay in a small hotel room with her in-laws. I'm like, what's worse, the pay-by-the-hour hotel or staying in a hotel room with your in-laws for a week. So, the place I stayed up in Clayton is not, that's not. It was an actual hotel where you paid for the night on the hour. Not the hour, y'all. Not the same thing. Not the hour. The Romo dance. I've never stayed in my tent, man. I'll stay in my tent and swim in the, I'll wash off in the creek, okay? I'm a country girl, I can handle it. As long as it's not too cold. That sucks, we could even play outside in the snow and us Southerners don't get snow that often. So when we see it, we want to play in it. But the power lines were down, so we couldn't even go outside to play. We just had to, I mean, we read so many books by the fire, thank God we were the generation that didn't have internet because we didn't have, we didn't have such a withdrawal. All we were missing was the TV, you know? So we could read, we could play with our Barbies, all that kind of stuff.  I remember that, I'm traumatized by that. And so that's my story, you guys. But I'm actually gonna, once we hop off Jessica, I'm actually gonna talk to my boyfriend because I think it'd be so fun to go up there with the Bigfoot Conference. He's a lover of the, of the Cryptoids as well. So, you know. Y'all please come up there.  And they have the best vendors with Bigfoot merch and I got some jewelry, I sure I bought some Bigfoot earrings and stuff. So yeah, it's just gonna be a good time. I think some of my team's gonna be up there hanging out with us to get to hang out with some Bigfoot field researchers if you come up there. Yeah, let us know in the comments section if you're planning on coming or if you live close by. I'm actually really gonna look into it once we get off and talk. We've actually been talking, my boyfriend and I have been talking about planning a weekend to the mountains again. So we might just make a long weekend out of it and go hiking on the, what I'm assuming the 15th is a Saturday, the 16th is a Sunday. It must be the 14th, I think it's Friday and Saturday. So it'll be the Friday and Saturday of that weekend.  I don't even have a calendar right here. I do, actually I do, it's right here in front of me. I can tell you. I have my calendar. It's gonna be right now. Yeah, so the 15th is a Friday, the 16th is a Saturday, the 17th is St. Patrick's Day, Sunday. Okay, it's the 15th and 16th. The 15th, we're having a round table, I think, with the speakers and all the vendors will be there and stuff. And then the 16th is the big day for the full conference with all the presenters and stuff. We'll be on that Saturday. That's cool, I'm gonna definitely, because that's like in a couple of weeks actually, I'm gonna go talk to him and make sure and let's see. Cindy, if you're watching, I might need you to sub my class that Sunday. So yeah, so all right you guys, let me know if you guys are coming too. Let's see, maybe we can have like a little meetup. Oh, that'd be awesome. Get a beer together.  Oh yeah, beer is a big foot, so I can do that. I can totally deal with that. Just make sure you don't say it in a pay-by-the-hour hotel or motel. Yeah, watch some people.  No peoples. No peoples, we don't want peoples. Unless you're into that kind of thing and you're a consenting adult, otherwise no peoples. Don't tell us. We don't need to hear that. We don't need to know about it. All right you guys, well thank you so much for doing this Jessica. I can't wait to do the next one with you. I know I talked to Derek. We wanted to do an episode about the land between the lakes and was that Kentucky, Tennessee, area? Yes, Kentucky and Tennessee. Yeah, we'll post it on that. So thank you so much Jessica. Make sure you're subscribed to Jessica guys. All that stuff will be down in the description box below, so make sure you're subscribed. Do us a solid. If you enjoyed this video, please give us a like. Please share this video because Jessica and I deal with the same type of, they don't like us that much. The controllers don't like us that much. So help us out you guys. Thank you so much again, sitting through this video. We appreciate it. Cannot wait to hear all of your opinions and we will talk to you guys soon. Bye everybody. Bye.


Centera, we improve health every day, more simply, affordably, and personally. Why? It's what we were born to do. How? With high quality healthcare and exceptional health plans. All for the patients, members, and communities we serve. Centera, improving health every day.