Sorry we're late. We were busy negotiating the purchase of a major crypto exchange and we were looking at their financials. So we're very sorry. Paloma, you know, being very aggressive as we are. We didn't want to let Binance take everything over. So we've been really working hard
on two dealages. So welcome everyone. Today's, today's a very cool day, right? Like really cool
Kuku as an crazy week. First of all, it's Wednesday, November 9th. Thanks to everybody in the full of community. Thanks to all the pigeons, the validators, the test mats, all the
devs everybody, the team, my goodness, the Paloma family is amazing and it is an uninsentivized family. Nobody is getting paid to pretend that they care about Paloma.
Because what we really want is we may be a slow growing community. We may not be, you know, overwhelmed with folks, but what we really want to be is genuine, sincere and genuine and authentic and true. And so welcome everyone. Hey, Vera. How's it going? Cool. Cool.
Oh, yeah, yeah, are you looking to buy an exchange? Are you in the market? You're here? You know, so so yes So where are we today is November 9th and this is the second week we're going on week
to after our upgrade from Dragonberry on Paloma to our latest version, O510. But before we go forward, just a little bit ahead, so if you're listening to the video or if you're reading the transcripts, hello, welcome back. We originally winding down the Paloma AMAs.
These are the AMAs we've had fun doing because we like to keep folks posted on the progress of the project. But due to the regulatory changes or the court case against library, LBRY, that token, we now are unable to run AMAs about the project.
So we are if we don't want the grains to be considered a latent security and that the owner reason why you're here is to put us to put the value of grains. We will have to end these AMAs and so the AMAs will come to an end.
At the end of this month, the month of November, starting December, we will not be doing the pull of my AMAs. Also, we will not be doing updates on engineering daily. We will not be posting daily updates on engineering. However, we will be posting releases. If there's a new release in the code, we will let folks know that
a new releases drop and we will end the new release put together a blog post or wings post outlining the features that have been added with the changes. This makes it more difficult to tell whether project is going because project awareness is what's really makes post not only in
and "Centivized" and "Cut and Cut" so contribute and help with the project but it also makes them incentivized to stay with the project. So we understand that it comes with a cost, however we don't want to be accused of trying to pump the price of grains by providing
software updates and weekly updates on how the software is going and happening. Now, we are still pre-mainnet. So for now, since grains are no value, it's not that bad because there's no such thing as grains that is investable. There are no investments
Okay, there is no main that main that is not coming we can't tell you but we're going to stop the AMAs at the end of November. So there you go. Cool. Cool. All right. So what deal we jump into? What is happening with Paloma? All right. Cool.
So where we are today with Paloma is that we are working on performance fixes. Last, so we have really some great help from Bez from Alexander Bezbichoff, who is one of the head devs over at Osmosis and one of the formerly dead
on 10 minutes. He is now part of our team. We brought him on to help us get Paloma ready for Maynet because we have no idea when Maynet is going to launch. So we did that. We instituted a number of grub grades. So Paloma was running fine. We were sending messages. Awesome, awesome.
a dragonberry which came out of the Binance hack, and I'm going to put $500 million of Binance lost due to the ICS hack which is the Interblockchain Protocol hack. That required a hot fix upgrade. So we upgraded Paloma based on the Cosmos SDK to that version.
And we upgraded that, then we redeployed a new testnet. So what we wanted to do, because again, we have no idea when mainnet is coming, what we wanted to do was test a new network and test full end-to-end deployment. So you can do integration testing on days and end, but then you want to really take your
pigeon out and really see if it could fly. And so we did that. And we could go, we did that. And we had partial success and a nonpartial complete surprise. The complete surprise was that our Ethereum contract did not deploy to, if you remain it. And our
Our Binance contract deployed to Mainnet was the most surreal thing. Why would one contract deploy and the other contract not deploy? So that was strange. Another issue was that the Valet set updates were not updating on the Binance Marching contract.
successful it was not. So we've sometime looking at logs and trying to debug errors. And long and short of it is that we're still debugging, we're still collecting logs. We've been going through log entries line by line and checking prior issues
issues and what we have found out is that our relayer module, Pigeon, most likely is our troublesome bird. And this troublesome bird is communicating with the Paloma Cosmos SDK and it's not communicating as well. The chirps are not coming through.
We are refactoring pigeon, but to refactor pigeon, what we want to do is take a full architecture review of pigeon, understand all our pieces because it should work. It was working before, and determine what may have changed in the Cosmos SDK to impact pigeon. This is a duty of the
You're depending upon a piece of software which has been developed by other devs and they're doing a great job. And when they make a change, if you're not careful or your modules that depend on the goal has a series of dependencies. So just so you know, when we compile, when you compile
When we compile, for example, you download that tar from our GitHub, that tar has been compiled based on real time retrieval of the code from the customer's estimate and GitHub project.
say, you know, go some, we'll say, hey, go pick, you know, Cosmos SDK, 05.10, please. Here's the GitHub URL. In theory, when it comes to goes, pulls that code in, I've come past, and every time this is a beauty of go. And that's why it's why I love it as a program is great. So that was another great feature of Rust and crates. So we#
Now, if the source code from the maintenance, the dependency code has changed and we are impacted by dependency, then our code breaks. So suddenly now what was working before is working. And then you're like, well, why did it break? Well, we don't know. We got to go in and check. Boom, boom, boom, okay.
So we now, birds, have to go back into pigeon, walk through our code and see where it breaks. And it's amazing. We have logs. One of the beautiful thing about Mattias' work on pigeon is that we log everything. I don't know if you've seen the relay or dot go file.
every line. We're log, log, log, log. But yeah, it's yeah, it's log, that's party, it's a lot of essential. We're logging everything. It's a cool, easy time to log. So we log it. But what those logs are telling us is that
I'll also talk about some of these errors right now. The first error that we see is that when, although the validators are being collected, so it collects the signatures, you know, pigeon collects the signatures, pigeon verifies everybody has Ethereum or BNB in their wallet.
I'm pigeon now has to sign a message and broadcast that message via Paloma. It's failing. It's completing. It's saying, "Hey, I tried to send that message, but I had a account sequence mismatch." An account sequence mismatch is that says that your node
is out of sync with the main node for that block or the proposing node. Imagine, by the way, I've become really good at accounts, equipment, mismatch problems, and defining them. Everybody in this team is getting really smart at Cosmos.
But we've seen accounts sequence mismatches before, usually when you have overloaded networks, right? Everything's going very fast. Because, you know, again, the software could only perform as fast as it can. But when our network's not overloaded, it's not a test net. But somehow the pigeon node is out of sync.
With the proposer notes and the node or the validated that's proposing a new box that's building a new block We're saying hey, we want to send a message into that block to broadcast our message to Ethereum or Binance or any smart chain and then the it's getting rejected because they'd be like bro
bro you want to go into block you know 27 but we're on block 28 bro bro where you've been bro like your late bro bro a consequence Mitch bash bro bro check yourself before you wreck yourself and so everyone who is doing this proposal so something is happening where
the pigeon is out of sync or the node, the pigeon is making a proposal for a node state that is no longer in sync with the proposal node. And so we're currently debugging why that is. Which means we're going top down into pigeon, which is in our case.
hub and we're documenting and saying, "Hey, here's where this is happening." So it's taking us some time because this is a bird and you know doing surgery on a bird requires very delicate form of cooling. No, it's just taking us some time because this is a new issue.
that we didn't have before. So we knew it's related to how cosmos upgrade and what we have is a typical dependency break. Now we have to find out why that dependency break is happening and how we can upgrade pigeon to address that dependency break. Now what's exciting about this is this means that we will now have a practice in the organized
that as Cosmos SDK continues to release new versions, Pigeon will be ready for changes and for possible breakage. So what we're doing here is we're hardening Pigeon and future versions of Pigeon against future versions of Cosmos SDK.
which will make Loma more competitive, right, against other chains in the similar space. And if we're able to accomplish that, you can realize that Loma and Pigeon can start using more advanced features of Cosmos SDK releases as they come on without fear of
breakage. We did consider downgrading to Cosmos SDKV459, but that has the exploit from the Binance hack. And although that we could patch it, we're like, listen, that's just a patch of a patch.
real problem is we need to build in a practice where pigeon releases are essentially tracking Cosmos SSTK releases and being hard against those Cosmos SSTK releases so that the entire community can take advantage of the best of the Cosmos SSTK without
fear that pigeon will break. Pigeon is our we are proud of pigeon. It's our most awesome software. And again, we, you know, we, we, this cross-chain communication marketplace is exploding. So we are saddened that we can't be deploying to more chains
and doing more exciting work because we have to take some time to fix this. And so it is slow going. But I think what we'd like to say is that this work will harden pigeon against future cross-nossesticate upgrade.
And so a hardening bird is a bird that is a rugged bird and then a bird that will keep on flying. No matter what new software, we want to do really aggressive things. Like we want to use the best. I mean, just to be clear, we should be on a Cosmos SDK 04610, but 0461, what was it? 0461?
I think it was 0.461. Yeah, we were going to be on 0.461 because that has transaction prioritization. And you may ask them, "Tar, why does Paloma need transaction prioritization? What does a bird need to be able to prioritize transactions in the pool?"
want to say, well, Paloma message is, remember we used to call it spedx shade, right? And we used to call it spedx shade for a reason. It means that messages get delivered on time. And with transaction prioritization in SDK for sex, what we get to do is to be able to say, hey, we can handle message
messages that have to go via RPC network to the target chains, those messages get transaction priority over a non-crushed message. So we continue to tune an optimized ploma to be the real cross-chain bird of choice. I'm not going to
tell you what target chain this would be useful for, but I hear something like the sun because we can't talk about what's coming on the moment because that would be regulatory bad in America. But we can say that in order to transaction partarize
for us to handle messages on faster, faster chains. And if Paloma is on a deployed chain that is doing thousands of transactions per second, or thousands of blocks or very, very fast, being able to take advantage of transaction prioritization in the SDK for six is something we need.
We can't afford to have pigeon to break when we go to four six. We must be hardening. So we're hardening the bird right now. And I think we're going to be proud. What we're going to do, I think what we would like to do is document how pigeon works and share that with the community. So folks can get an idea of how the module is built and when the future
are it's open source anybody can look at the software to date, but we're going to document it as part of this process because we as we continue to upgrade faster into higher versions of customer SSDK, we're going to be able to very, very quickly determine which pieces may have dependency issues when the upgrades occur.
There's lots of other things happening on Paloma. To be, we can't talk about that other stuff because it's not public, right? The stuff that begins with the W.
I'm sorry. Can we talk about the W thing? Is it public?
I guess it's public. It is public. Do you see it while I did I say what are you talking about? There's no such thing as a pillow mo
wallet or is there? Um, Vera, tell us more about this full of wallet. How can we get it? Is it like what do we have to buy it? Like, where is it?
And we don't find it's in the chrome store. It's in the chrome store. You mean there's a wallet in the chrome store for Pallola?
Oh my god, this is insane. This is ridiculous. How do we get to this wall? I don't even have this wallet. Where are the chrome store? Do I just go to chrome store and go proploma? I'm going there now. I'm going to the chrome store.
Yeah, you should be able to find it. Okay, hold on. Let's do this three times Chrome store. Let's go to the Chrome Web Store and let's search the Web Store for Paloma. Oh, yeah. Oh my god. Paloma, that's big. Ah, ah, ah, ah, ah, ah, ah, ah, ah, ah, ah, ah, ah, ah, ah, ah, ah, ah, ah,#
There is a Paloma Nest wallet in the Chrome store. So go to Chrome store.
And why don't you go get that get yourself one of them nice fine eggs? And that what look at that it's version 1.0. Oh that means it has buttons Yes, we actually working through
But this is amazing. It's very, very good. I'm going to add it to Chrome. It can read and change all your data on the website and replace the page. Oh my god, this is a vicious extension. It does evil. Okay, I'll add the
I'm turning on sync. Okay, I don't want to be out. No, thank you Google. So there it is. I have an egg pinned to my Google Chrome bar. It's a little pink egg that looks very cute. Oh, I get to create a new one. Oh, look at that.
Well, I get to select a nest while I call it blue nest, green nest, I'm going to go for yellow nest. Okay, and the password is cool. And my password is cool. All right. Okay, great. I got a monic. I hit submit.
Oh fuck, I didn't write down the demonic. Oh this is a wild. Okay hold on a second people. Oh yeah I can do that right. The fourth word is "whoa dude oh my goodness" "Semit"
I have a plenum wallet. It's taking up an entire page which is very funny which is very cute and I have no grades. But I have an address which I can copy. How do I copy my address? Oh just hit copy. It says copy. And now I go to the discord
And I'm going to go to the faucet. Let's go to the faucet. Yeah. Oh, hello. Okay. How do I do it? How do I string request? Paloma, my IPA address. Paloma testnet 13.
request. I got brains people. I just refresh it asked me to create a new wallet name. What happened to my old wallet? Oh fuck what's going on? My wallet. Wait, it's here. I have 10 brains.
I have 10 grades. Congratulations. Thank you so very much. It is good to-- you know, my precious grades. If I let you guys get your hands on my dot down grades, I can't feed my eggs. Anyway.
Congratulations to Vera and the UI team Joyce and to Jack. The nest is live and I have 10 grains. I was able to test it end to end.
and get my grades. And I was able to save my name in Monarch, which is great. So I can always come back and get going on my wallet. Can I send grades in this version or that's coming in the next version?
That's coming in next Thursday. Okay, so congratulations to Loma, you know, have a wallet and it's not because you're going mainnet. Mainnet is not coming and there's nothing we can say about Mainnet, but it is very good to say that we now have a wallet.
that anyone can use to hold their grains, and of course now have an address that they can use both on any test net and any main net. All right, that was just amazing. Thank you, Vera.
And they say, never join demo in real time, but we did the demo. And it worked real time and it's in production. So it's live. So get your nest set up. We have to tell everybody. Vera, am I missing anything else? Anything else we got to announce today?
No, I think we covered it. We think we covered it. All right, we did. Thank you, everyone, for this. We covered it well and we are super excited to stop making AMAs so that we won't go to jail. But we're also excited to progress
the project and also our continued excellence in the area of relay air software development in the cost of the ecosystem. Please continue to check us out on Discord, check us out on Twitter and please comment, tell us stuff, give us advice, thoughts, we welcome it, it's a community effort and we look forward to keeping your post
sorry we can't update you but when there's new updates on the code we will announce new releases. With that we cool the music and wish you best of luck in the coming crash and bear market on 2022.