♪ Don't ever leave me ♪ ♪ Don't wanna be all the life ♪ ♪ You can go on ♪ ♪ I'll be ♪ ♪ Don't ever leave me ♪
♪ Wanna be alright ♪ ♪ Right up this morning ♪ ♪ Just grab a little rest ♪ ♪ Free the shirt ♪ ♪ Come on, come on ♪
♪ This is a special year for you ♪ ♪ Take it all on ♪ ♪ By the way ♪
about a thing. Okay, baby, don't you worry. Everything is going to be all right. All right, thank you so much, Paloma. It's good to be with the pigeons again.
And good morning everybody. Today is Wednesday, August 24th. And this is the Paloma AMA where we share all that is happening on Paloma and we update the community. So if you are, you know,
We're going to say a special welcome to all the Paloma community members. And of course, those who are visiting from Twitter who may be asking what is up with this cryptocurrency. And we're like, that's the same question we're asking ourselves. And this is where this is the
track where we actually talk about what is happening. And also, so I want to say thank you to the Russian community, for Paloma, I want to say thank you to our Turkish community, come back, come on guys, don't be like that, we love you, Indonesia community, Vietnamese community,
community and of course our US based users and even some folks from Africa we have to meet African members that should be good. My name is Tarr Lewis and I am from volume and we're volume.finance where the company is hired by the Pulumma Foundation to bring
and Paloma will help deliver the software for Paloma. And today I have a guest with me, we're going to have Matia. Matia, are you here? Yeah, thank you. And so Matia is joining me, Matia is head of engineering at Paloma, and we're going to talk about
So, first of all, we want to give a shout out and thanks to all the non-incentivized valid errors on the testnet. This is public acknowledgement. We acknowledge that you are spending data center time, data center money, and now even a little bit of
to be testers on Paloma. And so you are not being forgotten. So that's why we always tell you, please do not lose the private key to your Ethereum wallet. And please do not lose the private key to your Ethereum wallet. I have no idea why that will be important in the future. But I think it should be important now because
you are proving that you're actually committed to this testnet by being on board. And the way we prove that is through your Valset updates and that Valset updates is how Paloma works. So before I talk about Russian and Paloma Valset updates, let me talk about the agenda for today. So with my thanks to the current testnet validators or testnest validators
We're going to talk about why those happened, why those calls happened, and that's going to be such a discussion with
the upgrades from Paloma 0.45 to 0.5 to 50 to 6.0 to 6.1 and now to 7.0. And then after we talk about what caused those changes and why Paloma 0.7 or exists, we're going to talk about what's coming in Paloma. What's going to be a new version of that?
That's a breaking change. That's a question. Yeah, that's a breaking change. I think the current one is 07. Oh, but that's like asking me what did you do? So if we're breaking change, right?
So next, so Paloma this Thursday, which is tomorrow. Okay, so everybody forgive me. I know I know I know everybody on this other call was like, dude, you need to give us more heads up. I'm like, yeah, it's like tomorrow.
So tomorrow, dear pigeons, we will have a new version of Paloma. We're going to talk a little bit of what's coming in the new version. So why don't we get started with the next few minutes talking about what happened, what upgrades we got in O50. Okay, so the reason why we had O50 upgrades
045 to 050 was we were upgrading our ability to verify and check the adding of chains. A lot has happened in Pulumma. Let me rewind. What the hell is Pulumma?
is the fastest message blockchain in the crypto ecosystem, the fastest, right? What does Paloma do? Paloma sends messages or allows any one to send messages to any blockchain from the Paloma chain.
And also to control smart contracts that are executing on any other chain. So imagine if you could have a way to control smart contracts that run on AppLedge, Solana, Ethereum Virtual Machines, Move,
suede, aptos, and any other cosmos IDC chain or even on any other proof of work chain, Bitcoin proof of work chain that is running a smart contract, you want to be able to send messages from one portal that will get to these chains, that's Paloma. And Paloma gets
So that's these messages from the portal, the Puluma portal, to these other chains via pigeons. Pigeons, yes, God damn pigeons. Pigeons exist everywhere. And what pigeons do in the old days, they would send messages. So like the old analog of message or pigeons, which is not really efficient way to send messages today.
But again, reflective of this is the early days, our pigeon sent messages to these other blockchains and the pigeons insert the message into blockchains. The pigeons spend gas to insert the message and then the pigeons get rewarded. The pigeons get rewarded with grains and they get rewarded with denominational cryptocurrents.
on the target change for sending the messages. Now, the reason why Pulum is the fastest is because these pigeons are constantly, constantly checking what's happening on the target blockchains and they're constantly looking for new messages to send because pigeons are very hungry for grain and they want to do a lot of work.
They don't want to do a little bit. They want to do a lot. So we have designed a plume as a cosmos SDK chain, which was meant to bring this new vision of having the validators act as relayers. So the difference between, you know, plume and some other cosmos IDC chains or cosmos base chains SDK chains is that
But usually the relayers are optional, right? So you have relayers in IDC and anybody can be a relayer. But in Paloma, only validators can be relayers and validators get slashed if they don't relay the messages. And validators get jailed if they're not monitoring and they're not essentially tracking the messages.
So the performance requirement for philoma pigeons is you must be talking to the other chains. You must be flying over there monitoring and you must be really decent messages as soon as they are ready to go. And our goal goal is that the validator flock as it continues to grow in size and grow and reach will be a good example.
will be essentially the fastest way you can send a message between chains in the current ecosystem. So that's the goal. So quick introduction to Paloma. All right. So next, let's come back to what we're trying to do with O50. So with O50 on version O50, we are all set. And so a lot of change.
One thing we wanted to do was deploy contracts from the pigeons to Ethereum. Now when we got the normal up and live and we were running it, we weren't talking to any of the blockchains. And we said, "Listen, instead of talking to a test net, why don't we just go talk straight to Ethereum?
because we're going to find out what it costs and we're going to find out how it works. And so the next phase of 050 was to allow us to create a proposal in governance to deploy a Compossibium, which is our "manager" contract. So at any time we launched a new
is a manager contract. And that compassivium contract is the contract that receives the validator set updates. OK, so I'm going to take a quick shot over to Mattia. Mattia, when we think about validator set updates, how would you describe validator set updates as an easy term to understand terms?
in easy terms. So basically we are bringing the validator information and they're taking power that external chain addresses to a target chain so that from the target chain point of view we can verify the incoming message.
So that's super simple explanation of what was supposed to be there. Basically they are using the target chain to verify that all validators from Paloma have actually signed the message. And this is a big key part of Paloma security because the Paloma security
model is a validator set security model, which means that we are saying that the validators who of course have stake at risk will send their signatures to the target chain currently Ethereum to say, "Hey, I'm a validator, Oklahoma. My signature is here. My signature is grouped
So what we wanted to do was to be able to send that message from Paloma via the Pitchense into the Ethereum mean. And so we created a proposal to upgrade our
order 5.0. And once we have a bridge, we had a small problem that we had a system halt. And if the system halt happened, because we were essentially, we could have a system halt. We deployed T theorem in that. But we found that we were not getting, we were having errors on
deployment that of course we're not detected. So the next version of the little one which was O.6 was meant to add more visibility around logging around the errors that happens because of course you're trying to deliver messages to a chain right and we can't see the chain and we don't know if the chain's working and the pigeons will know that.
So, you know, there's a lot of software layers at work here. And if every pigeon is running a remote procedure call, RPC network endpoint into Ethereum, we need to know if they see an error, then pull them in to see the error, or that error needs to be reported. If a transaction goes through, we need to know what success
If a transaction fails, we need to know that the transaction failure was also something that happened. So, 05-060 was to really add more intelligence to pigeons and Paloma's ability to digest that information and say, "Great, we get that." Also, what we wanted to do was we noticed that the network cannot
not come to consensus, right? If not enough pigeons were running their pigeon relair. Okay, so what that does that mean? So remember, think about it now, you're a validator in Pulumum, right? You have your Puluma D running, which is great. You have blocks validating, but you are in messenger as well because why are you in this business?
you don't want to be on any other boring blockchain address validates blocks. You want to make money, right? You want to generate cash, you want to be paid more money than it costs you to run your data center. So you need to be running your pigeon. But here's a problem is your pigeon running. Do you have the right configurations? You don't know. So somebody needs to tell you. So we needed to make sure
that Paloma would tell you because if you download a software and you're running Pigeon separately from Paloma, you don't have a way to verify that you are actually properly integrated or sending messages to Paloma so that those messages can then create a signature to get over
to eat theory. So in order to cross the Ethereum, we need to have your pitch in front. But you don't know that, right? Because you're like, do I have this pull in the software? It's running okay? And I just pitch in software. So we did something very ambitious, which is, you know, we're going to find out it works. We essentially started to couple, and we're going to talk about the
Let's talk about coupling first before we talk about marriage. We coupled Paloma and Pigeon more and more from 05 to 06. We wanted to make sure that Pigeon talked to Paloma to tell Paloma about its life. We wanted the Relayer software to tell Paloma
Hey, I'm alive. Hey, I'm working. Hey, I am monitoring the Ethereum mainnet. Hey, I am able to send messages from the Ethereum mainnet. Hey, I am able to read Ethereum mainnet. Hello, Paloma. Hello, Paloma. I am here. I am a pigeon. Cool. Cool. So,
versions from 05 to 06 were meant to do this because again we could not deploy a contract on governance if we did not have enough consensus or enough pigeons running the software right and even if pigeons were running the software and they don't know what's going wrong we need a way to signal to them so 06 so
sending pigeons, letting them know, hey, your diplomas are running. But even after 06-0 launch, we found that we had a problem. So the way we would send this message, that you're not running your pigeons, is that we would jail you. No, we eat diplomas. So the polymer network jails you at osix.o because you were not running your pigeon, this was a way that we could send them
to say, hey, your pigeon is not currently working really well, you're going to go to jail. You're not going to get slashed, you're not going to lose stake, but you're going to go to jail, so you're going to lose the ability to essentially sign transactions on the pool of a network, and eventually after certain times, you will be on bondage.
will be unbonded from the network. So you want to say an active value value intercept, you need to stay, keep your pitch in a live. Right. You need to feed that bird. So that was OSX release. Of course, we had a chain halt. Why? Because as soon as OSX released successfully, well, OSX release, then we had a chain halt.
So we did that patch, but after all six one, we still had a halt. We had our second chain halt. And thank you to all the pigeons that came online on O.61. You guys rock, you're awesome, but we had another chain halt. And that chain halt was because we had to do a lot of things.
were being jailed subsequently for validators for being jailed for running their pigeon and as more validators for jail, there was only one validator left and essentially the network halted. And so we had that problem. And what we found was that the Cosmos SDK was double jailing validators.
which was something new. So this was now a Cosmos SDK problem. Oh wow. Cosmos is double jailing. Yeah, like it runs, it doubles jails and then packs and then it panics the network calls. So we had to move to O.7. Oh. And while doing that O.7, we added more telemetry and ability for pigeon
to say to Paloma, "Hello, cool, cool, I'm alive." I know we say "chirp, chirp." I think we have to put "cool" in the chirp. Okay, but before I go forward, let me pause there. Mathia, did I get everything right? Did I miss anything in our progression from 056? Right. So, welcome everybody to Oda.
We have consensus and we have balsett updates. So 07, 0 was launched last Thursday, pigeons and pigeon validators upgraded their software. We found out some folks were having incorrect cause necessity case. So again, we encourage folks, please do not use
instructions that you get from random sites on the web. Pulloma instructions and pulloma downloads are available on our GitHub. If you want your pages working just use the standard pulloma configuration. It will spare you a lot of time and it will spare you jail time. So now that we have, I think as of yesterday, was it yesterday? Was it Tuesday? Yesterday, Tuesday,
Tuesday, we had ballot set updates and the city for Monday was our first day that Paloma had ballot updates. I think it was Sunday Monday with the first two days that we had sufficient pigeons to create consensus and that those pigeons were able to deliver a set updates. And with that, we suddenly had the point
want to eat that those pigeons have committed to spend to join the network, suddenly being consumed. And so we're going to say thank you to everybody who put up the 0.1 ETH. That was awesome. And then of course, now we have to refund you. So we've been refunding 0.1 ETH to all values who have been
essentially participating in the Val-Setup dates with their pigeons. And that's great news. So if you see it's 0.1 in your ETH wallet, you know, don't go spend it on your Lambo. Remember, Lambo's cost more than 0.1 ETH, and you're going to use it again. So that ETH is going to be
spent for Valse duptates. Now, the Valse duptates are poulting in this moment. The Valse duptates are poulting because some validators have been jailed and most likely because they didn't have the balance to be set the balance too strict. So we're going to be using the balance for Valse duptates.
And then what we're going to do is we're going to continue to replenish 0.1 eth to all validators for in the balset so that you are essentially always going to be at 0.15 eth and there will always be, you know, will never be jailed.
for Valsus not having enough ETH. So we're going to make that happen so that we can continue. We have about 200 messages, Valsus updates missing in the network that have not yet been posted because one of the validates went offline. So we have a new version of Paloma coming tomorrow, Matsya.
You want to share a little bit about the new version of Paloma and what we should expect? Yeah, so this version recall marriage. We're done. No, we're making it the faithful. I don't want any sex. No sex.
So basically this should be having as you said some ballers weren't running their pigeons, but with the marriage Paloma will depend on pigeon running on your
machine and vice versa. A pigeon will depend on Poloma running on your machine as well. Did I got that right? You got that right. So like marriage. Okay, okay. It's like marriage. You can't get away. Okay, no, I didn't. I didn't mean that. I didn't mean that. Marriage is wonderful. Yes, I
So what we want to say is that if your pigeon is not configured before you would be jailed and as a result, that's frustrating because you're like, "Well, I'm jailed, what's happening?" Palloma will not start. So pigeon is now what we call the same
same level of rights and power as Poulomadee because it's becoming more important to be a relayer. And this is the first time we're doing it in Cosmos. So, you know, this might be sacrilegious in some Cosmos instances, but if you are a validator on Poulomadee, your Poulomadee will not start unless your pigeon is configured properly and
And it's funded right like we would do require to be funded for the right because what's going to happen is that the job of the problem of allotator and the pigeon is to say no matter what blockchain Pigeon is sending messages I am here to send messages my wallets is funded my wallets are funded and I
I am ready to go. So the validator will, yes validator, you will be required to have funding. Now remember the governance will still decide whether or not a chain is deployed. And for now we are only deploying to Ethereum, but you should expect if you are in this chat or if you're reading this transcript or listening to the
this recording, we are going to be deploying to other chains. We got other chains lined. We want governance in testnest to go to other chains so we can see what Paloma looks like when it's talking to literally more, more chains. And that means you should think, wow, where is he going?
going. Well, you know, if you can think of an EVM chain that you like, Pulumma wants to be there. Pus Pulumma wants to deliver a net promise that any blockchain in the crypto ecosystem, it can send messages to any blockchain, any protocol, anyone. There is no, there will no blockchain will be left behind. So as a
So, the result pigeons are now first class citizens in the network as Paloma de Instances and your Paloma de Instance will not run. It will halt if it is unable to verify that the pigeons are working. What we will continue to do is add more visibility to limit tree UI errors messages
So folks can self heal or fix any of their pigeon issues. Right now we think those issues will be limited to one, making sure your RPC endpoints work. Two, making sure your wall is affunded. So far what we've seen in the test nest on telegram is that most of these errors
Again, if you're using the correct software and using the correct configuration, it will all come down to is your Ethereum wallet funded. And since volume will subsidize the pigeons for the test nest, no pigeon will ever spend eth without being refunded on the
network for BALSET updates. Now, you know, logic calls where, you know, we're going to be sending messages to, you know, augmenting NFTs and doing also so cool stuff will also require cost. We're working on that. We have new features coming off for that. So right now we just want to make sure that the BALSET updates
work and the security promise is delivered. Keep in mind, right? Like if you look at any other blockchain or any other protocol, you know, usually the validator set is highly controlled. We want this validator set to be permissionless. We want the validator set to be anyone can enter, anyone can join, become a Paloma.
that anyone can exit. However, the bar is raised. This is not going to be a network that I've made that, you know, it's like, oh yeah, you know, I can just fire up a node. You will be required to have balance on a private key on the
target chain. Right? So the target chain is, and that's any non-cosmos chain. If you're an IDC chain, I don't think we require it because the IDC security is a security layer we're doing, which is kind of like a different version of gravity, but what we'll be doing is IDC and IDC won't require those types of security.
But yes, if we're going to any non-cosmos chain, this is what's required. Of course, there are some Cosmos chains which do not have a IDC turned on, so they will be requiring Valsed updates via the client. This will be something we will be doing as well. Like, and we want to keep the promise, pigeons are everywhere, right? Pigeons are in New York.
Pigeons are in San Francisco, pigeons are in Paris, Barcelona, they're annoying, they're everywhere, they even should on you sometimes, but pigeons are everywhere. We want Paloma to be everywhere, a cryptocurrency transaction is happening. All right, so given that we have the marriage, I think all
Also, what we're going to be doing is looking at making sure that the VAL set updates are secure against what we see today. Currently, what you notice is that the VAL set updates have halted. If you're on our telegram, you'll see that we put the VAL set updates on the Ethereum blockchain. You'll notice that they haven't been updated.
24 hours, that is because one of our big validators is now offline, they're inactive. And so this new case, this new issue of, well, what happens if a major stakeholder goes offline for any reason, kind of the vial sets persist, and what we've seen is the vial sets have to pay it. So what we have to do is
This is a whole new problem that we did not expect to see. Again, if you're working in a relayer opt-in world where relayer is opt-in, you have to beg relayer. I got you. Can I relate to that next week?
outworld, what we're finding out where validists have to opt out of the real-layer network, then the real-layer network can halt. So suddenly now Valet's at updates are not being sent because we're missing the signature of this one big stakeholder. So we now have to go back in and figure out and design. And things are one of the things we're looking at in the future is how do we make sure
Or that even if the network sees the loss of a major signature that has a certain amount of power, how can we still preserve the Biles' updates to continue so that the remaining stake can come to consensus? And of course, since currently we still have consensus at, you know,
So we have to make sure that we again are able to come to consensus. We still have consensus at Paloma because blocks are being created. Right. We have blocks. So that means the network is coming to consensus. We need to make sure now that the pigeons come to come to consensus in the loss of validator that has significant stake on the network. So that's it. We have tons of other stuff coming
after O.0. I think we will create a new for speed tomorrow validators on this should expect that we will have a new chain ID that will be pull on a test net nine because we're at test net eight. So we will update our documentation. The release will happen tomorrow.
we will let you birds know. And we're super excited because now once we have consistent vowset updates, then the next exciting part is now sending arbitrary messages at will any time to any other chain. And then we have more chains coming. So super excited. Max, you have before we wrap anything else I'm missing.
Anything I forgot? Love, you mentioned everything. Yeah, I just want to say thanks to all the pigeons. You guys are doing great jobs, helping us in great amounts. Yeah, thanks. And keep your private keys. Before we jump, any questions from the group that is listening so far? Any questions from Telegram? Any questions from Discord?
All right, question going once, question going twice. All right, so lastly, please do not lose your private key for your test net on Paloma. That key is in
because that's key is proof of work. And if you're working for the vowsets, then we hope that you get paid. So keep your private keys, stay on the network, and thank you. We'll see you guys on the next one.
Next release. Cool, cool. What discord. Nice, nice. That's what I was saying, guys. We'll see you to see you on the telegram. Bye. Thanks. Bye-bye.
♪ Oh, I'm gonna be alright ♪ ♪ Oh, I'm gonna be alright ♪ ♪ Oh, I'm gonna be alright ♪
♪ I'm a boy, I'm a boy ♪ ♪ I'm a baby ♪ ♪ Never leave me ♪ ♪ I'm a girl, I'm a boy ♪ ♪ I'm a boy ♪