{
  "txid": "d9fddbe5850c6a2d8efaceb9bc1554d60dab341b415e4d21029d67ddb260cb3f",
  "block_height": 0,
  "time": null,
  "app": "treechat",
  "type": "reply",
  "map_content": "Uh, it is our custom that you introduce yourself and tell us who you are as if nobody knows who the hell you are. Go. >> Hi, I'm Greg Bailey. [clears throat] I work for Green Arrays, which was founded in 2009 on Friday the 13th of February by Chuck Moore and all of us who had been working with him for a fellow named Daniel E. Leone at a company called Intellysus. And when we were all laid off from there, we basically spun out with in fact no help at all from Intellysus in the process. I was going to make a couple of brief remarks uh before we run these videos. Uh first remarks are thanks for the opportunity to be here. Appreciate it. We've been here for a while obviously, but u this is a friendly environment. These are friendly folks here. Uh, I'd like to make a couple comments resonating first with what John Ryel reported about slurp. Uh, I also named my first fourth implementation flux f lux, which was an acronym for fourthlike language for unpretentious zero files. For the same [laughter] for the same reason that that John named his slurp, we were afraid. We were we didn't yet know that Elizabeth and Ned were human beings and so we were afraid of them. We're afraid of forth think. At any rate, that was misplaced fear. Chris Lzinski pointed out last year that some people had missed the fact that our computers do not have clocks as such. Chuck has the balls to design a computer with no clock. This is a thing that people generally are not ballsy enough to do. They were in the old days. In the 50s, there were clockless computers, but more recently, people put put clocks in their computers. And why are the clocks there? The function of a clock is to slow down the logic. If you actually look at the designs, you'll discover that is what they are for, is to slow down the logic. By having no clock, it's possible to let the logic run at full speed, which is a very advantageous thing to be able to do. Also, years ago, just to prove a point, I laid out a clock distribution network for a machine the size of one of our F-18s. Those are the computers, of which our chips have 144 of them, and measured its energy consumption using our simulator, which is fairly accurate in this regard. And much to my delight and amusement, it burned as much continuous power as does one of our computers running at 100% duty cycle flat out. So, for example, to have one of those clock distribution networks in our computer slowing it down, we would have on the order of twice the power being consumed. Not quite on the same order because of course the computer would have been slowed down by the clock circuit. And so many of those gates would not be flipping quite as fast as they could. Many of those capacitive loads would not be changing state. But at any rate, Chuck had the balls to do this. And we have in fact made them very, very reliable. They act just like computers. They will sit there and execute many billions of instructions correctly. And I haven't had one fall over without having a power glitch hit it. So there we go. Um, and we don't have clocks. Incidentally, even if you have a clock and shut it down occasionally to go into sleep mode, as it's often called, clocks don't stop instantaneously and they don't start instantaneously. And so there is a triangle of power consumption that you integrate under to determine how much power is squandered starting a clock and stopping a clock. And every start stop instance costs that on a conventional computer with a clock that has a sleep mode. Whereas our sleep mode is we get to a gate that says whether to execute the next instruction and the gate says no and we stop within 100 picos seconds. The power consumption is immeasurable and so that's quite [snorts] a different phenomenon. At any rate uh Chris had said that a lot of people didn't make that connection. and they didn't understand we didn't have a clock and that had something to do with our energy efficiency. It has a lot to do with our energy efficiency. Chris also at the same time suggested that crypto crypto mining was an obl an obvious application for us but actually it isn't because our hardware is not competitive in such mining. Um cryptocurrency mining is 100% duty cycle activity. It's best done by the best and most expensive technology you can get your hands on to at that moment. And you'd better use the hell out of it because the rate at which the difficulty of crypto mining at least for Bitcoin increases is such that at least at the time we were first looking at this [snorts] monthly the difficulty and therefore the amount of machine time you had to spend solving for a given hash was doubling. And so after 10 months, you now had lost a factor of a,024 out of the cash efficiency of your cryptomining hardware until you came up with millions of dollars to lay out the next chip and the next greatest current uh technology. So no, it's not the game for us. Um, usually when we excel at programming, we do it by simplifying the problem. And it's the nature of cryptocurrency mining that this is a cryptographic exercise. If I can find a way to simplify the performance of a cryptographic algorithm, I have most likely discovered a serious security flaw with that algorithm and most people will be real interested to hear about that so they can stop using it while they figure out the implications of that possible simplification. Excuse me. So, thank you for those observations, Chris. It is really great to see old friends here. I haven't commented on this before, but damn it. For example, we have in our midst still awake chuck our sefue uh which is a term that is used by some of us particularly that practice internal arts for an internal martial art instructor who is introducing us to not just a particular skill but also to a philosophy, a set of ethics, a craft, a tradition and Shrek has brought all those things to us by his insistence on flipping the bird to convention and asking why do I need all this? Why in the hell do I need all this stuff to solve a simple problem when actually the problem is much simpler than anybody thinks it is? Because they love making things sound complicated because it makes them seem important to their buddies. And that's anybody that hasn't participated in such a conversation in a school context I guess just wasn't there when I was there. But once upon a time it was regarded as being a real important indicator of how cool you were that you could make things complicated. And Chuck of course demonstrated with existence proofs that that's BS. Thank you Chuck. We have other collaborators here some missing. Leon is gone traveling. Sigh. I usually like to get to see him out there. John Ryel very longtime friend. And John, I trust you with my life too, buddy. And with my kids. And a lot of people have. By the way, John also teaches kids how to do basic things like throwing rocks, setting fires, using knives, all the things that [laughter] a lot a lot of folks are scared to let kids have anything to do with. And he teaches them how to use these things properly. And yay for him. And all the regulars that are here for SV Fig meetings. It's good to see you guys. I also would like to remember those who have followed at least in in our small group. We've in my actually our small group and my customer base. We've had Mike Lammana, we've had Min Moore, we've had Don Colurn, Jeff Fox, Ed Sizzler, Will Ben, Bill Mch, Glenn Sanderson, Chad Brown, Steve Meador, Skip Enskeep, Mike Benedict, and Howie Goodell. Just for just for starters, we've lost a lot of good friends during these last 50 years. And some of those we lost very early in that sequence. And we also have some new friends. Let's see. Right now it is about 2300 central European time. And I believe that's the clock that Kay Lac runs on. And if you're still awake, Kay, it's really nice to see you here. It's not often that we gain new friends in this community. sadly enough. And let's try and do something about that. We are going to try and do something about that. In fact, our status is that we're now headquartered in rural North Central Missouri. I'm learning personally a little something about subsistence farming, which is an interesting way to enhance your life. I recommended it to everybody. Uh we're very much still alive and very much resuming very energetic progress. We are introducing a new product called Volatco. V O L A TC O from an very interesting and excellent collaboration. Uh, Vlatco represents a major step into what we think is a better way to empower the creation of useful machine intelligence in contexts like industrial control and embedded robotics. algorithms first expressed by David Lheiserman from cybernetics's concepts of adaptation that has led to ideal currently being expressed by us in high level 4th augmented by parallel native F-18 code in our chips. You can find out more about this by going to the green arrays website. There is a section on the very first page that talks about latest developments and in that section we will mention what we're doing with Valatco and we will include a link on there. There is a link there now as at this moment um to an Indiegogo campaign that is almost ready to be turned into pre-release. As soon as that campaign is lit off, that link will work and you'll be able to find out continuous updates on what we're doing. I'm going to use the remainder of our time here, which by the way will leave the group done a half hour almost early, which is nice. So the closure of this today's session will be about 25 minutes 20 to 25 minutes early but we have started making a new series of videos. Um the videos originated because Kevin of SVF fig asked for some videos explaining how to install and turn on and do something with array 43. Now this isn't a trivial subject especially if people are not acquainted with polyforth which is something that we would like people to become acquainted with. And so for the next hour or so, we're going to run a series, the introd introductory series of these videos with pertains on a contextual formulation video and then some videos on installing array 43 and doing various simple things with it. This will be augmented very soon. We're going to continue making these uh with videos that explain how to make some F-18 code, how to execute it inside the chip, how to find out what it did, how to interact with the outside world, how to interact with yourself from the inside world, and all the wonderful things you can do with it. So, this will be an exposure on the new series of videos that will be a lot more complete in the next in the incoming weeks. That's really what the schedule is that we add to this immediately before the end of the year. So any feedback that you can give us on that will be greatly appreciated. My email address is greg greenarray chips all one of  glute native word . Com And if you have difficulty remembering that another one that works is gregit42  its 42  . Com  which should mean something if you know who Douglas Adams is. And so with that, [laughter] Brad, if you don't mind rolling it, I'm done until we find out whether we have any questions. >> I wish everybody well. >> Thank you. >> Greetings. I'm Greg Bailey from Green Arrays. We're engag\r\n\r\nhttps://youtube.com/watch?v=zPyRz63qax4&si=VeBjKMpoG-IKZ3MJ",
  "media_type": "text/markdown",
  "filename": "|",
  "author": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "display_name": "MarkKordusic",
  "channel": null,
  "parent_txid": "e9d8f0aed057456915042778dc369b90dd920eab0b14c429ac61f7b84fa1ab01",
  "ref_txid": null,
  "tags": null,
  "reply_count": 2,
  "like_count": 9,
  "timestamp": "2026-03-17T10:44:56.000Z",
  "media_url": null,
  "aip_verified": true,
  "has_access": true,
  "attachments": [],
  "ui_name": "MarkKordusic",
  "ui_display_name": "MarkKordusic",
  "ui_handle": "MarkKordusic",
  "ui_display_raw": "MarkKordusic",
  "ui_signer": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "ref_ui_name": "unknown",
  "ref_ui_signer": "unknown"
}