That's it. You got it. Yeah, in your feet.
We spent a lot of time searching for love
And I got nowhere to come and phone And as soon as we get it, so come We seem to think that I work still Through the same thing I took to get not alone Probably not you'll have to do to keep us through
You gotta give a little take over. You gotta give a little take over. You gotta give a little take over. You gotta give a little take over. You gotta give a little take over. You gotta give a little take over. You gotta give a little take over. You gotta give a little take over. You gotta give a little take over. You gotta give a little take over. You gotta give a little take over. You gotta give a little take over.#
♪ And the baby's reading them the children ♪ ♪ But just to hold on ♪ ♪ Baby, the golden box ♪ ♪ The gold box is water to make ♪ ♪ And they're being homey ♪ ♪ That's too bad for me ♪ ♪ You stay like that ♪ ♪ I'll say that ♪
All right. Kill the music. All right, thank you. We got to keep the fire burning.
it feel hot right now. It feels very hot. Oh my god, somebody turned on the heat. I'll keep the fire burning. All right, definitely you got to keep the fire burning and welcome everyone to another Twitter spaces with volume and we are glad to have you here.
It is now June 14th, 2023 and it's 8am where I'm at. I hope it's a great deal where you guys are at. And with me here, Vera, are you here? There's Vera here. Hello. Hello. Hello. Hey, you're rocking a rollin. Grovin, so just want to thank everybody for jumping in and thank you Vera for coming on here. I have an awful
Of course, this is a volume, so we're volume.fans. And we are all about private key security and private key management. And our goal is how to get more use out of your private keys across multiple blockchains. And our goal is to enable more control of features for your private keys. We think there is a massive opportunity.
for distributing control of your private keys across the thousands of blockchains that are in the ecosystem. And of course, we at volume are the team that has been hired by the Paloma Foundation to build Paloma. And we really want to say thank you to the Paloma Foundation for allowing us to build
and continuing to work with many other teams and folks on extending the Paloma blockchain. So we work on top of the Paloma blockchain and of course many folks here who already in this chat, I see many of our rockstar validators that join us in keeping the network alive and keeping the network of the nest flapping. Good to see you guys.
And we would like to talk about the postmortem for this event. It's a postmortem on the Pulumma upgrade on the Pulumma testnet.
be a month, a month a year since Paloma's test nets launched. I think the first test met launched sometime in June of last year. And so we have the volume team have been constantly working to ship upgrades on the system. And we, it has been
Bruto, a year of continuous upgrades to get the Paloma network into a usable state. So we are, this, this, what we want to talk about is essentially the key highlights that came in the last upgrade that was for Paloma 1.2 and I think pigeon 1.2.
So the main big news is the VALSETs. We wanted to update VALSET performance. So as if you're in the Pulumma network, you'll notice that VALSETs essentially consume the minimum
that you must have .058.0.05BnB.05matic. These minimum coins you needed to make sure that you could support publishing essentially the powers of the validators at these checkpoints that are not available.
The network, the Pelloma network uses to verify that when messages are sent, they're being sent by the right group of validators. This is a security feature. So a big feature of gravity is essentially publishing a VALSA update from snapshots of the validator set. And these VALSA updates currently
on mainnet of being published like I think every 5, 10, 15 minutes. And of course those publishing activity consumes gas. So you know we at Voluntel, volunteers hey we've made an update to the network where you have to put this minimum of gas and then the gas goes and validers like hello where is my money.
And that's fair enough because the Puluma network is still not getting, you know, as much use as we want because it's still very new and validators are supporting the network as it comes online. So it's a very slow burn. And so this, these published checkpoints on the target chain published on ETH.
They cost gas and they cost a lot of money to the tune of current about one each a day and it's the funniest thing like you know I was telling somebody that you know you can tech you know do these tests on testnet and see how much we really eat your spending but it's only on mainnet that once you're running it you actually appreciate the the expense
that value just have to struggle under. So, our goal was to really aggressively go after the valve set updates and reduce them. And of course, when ETH is cheap, this is less of a problem. And so, since it hides itself when gas is cheap, but when gas is high, then the problem becomes
So better that we deal with it now than wait for it to even get worse. So bear markets actually good time to consolidate and to optimize and to lower costs. Right. So because we expect again continued slowness in getting message activity into the network.
expect that to continue to be a slow burn upwards, we want to make sure that validators aren't essentially getting poor or going poor supporting the network as it is on mainnet. So we had some improvements. What are those improvements? Well, the first improvement is we reduced the vowset updates for
quiet chains. So if a chain does not have activity for at least a week, is it a week or is it a week or is it just I think yeah, so it's like if sorry go ahead. No, I think we'll put it down to a week and I guess
We'll see how that works for us. We'll always fine tune it. Absolutely. The goal is we should have a minimum set of Valset updates. We don't need to. Hey, man, the chain is dead for a month. You don't even need a Valset in a month. We have this thing we call just in time Valset updates.
So instead of doing file set updates every time the powers have changed the powers could change for many different reasons powers couldn't change because hey You got more delegated stake as a validator powers can change because you spent stake or you claim rewards powers can change and we have it fine tune that it's very sensitive to power change so even for any small amounts of power
changes or small amounts of token holding changes, the snapshot changes and when the snapshot changes then the Valsa change. So we have essentially designed it now or maybe upgrade that is not running on TestNet and at the end of this event host and will be sort of a hosting a pre-code
before the next pip, pip 31 that we're working on. What will happen is that Valsa updates will only occur when messages are being relayed. So when messages are actually going through the network because somebody wants to send a call to Ethereum to control, say, they're spending of money or they're
position on a unisob v4 mm or v4 pool you want to then get the valset update. So the valset update will be checked and then published before that message is sent. So if no valsets update have been made and powers have changed and a message is sent
Then the Valset update will just come just in time, publish to the target chain, Ethereum, and then messages will relay and essentially use that Valset as a checkpoint. Now if powers change again and no Valsets are, and no messages are being sent, then they will not be a published Valset, right?
Imagine that one. Okay, we sent one message. Great. Everybody's great. I made a million bucks. I was a flash loan to some particular pool. That was the only message that went through on Pouloma. The Valsa update will cease after that message. If and then have been changes, then Valsa will cease. If another message comes in and they
And then there is a snapshot change, the vowsets will change. Therefore, another message comes in and the vowsets have not, the snapshot or the powers have not changed, then the vowsets will not be published. So what this means is that just in time vowsets also survive, you know, the
the current state of the powers. And so for every epoch in which powers have not changed, and assuming that epochs are variable in time, Balsett of days will not be published. But if Balsett updates will be published when in the epoch of time between snapshots, powers have changed, then they would
So of course this means as the network gets more messages and more activity then those vowsets will continue to be publishing more frequency and of course cost will go up but gay cost will only go up because revenues are not going up because people are paying for messages to be relayed. So this is a massive improvement. Huge.
as one of my former presidents was huge. I thought I was funny. So, Ver, did I get it right? Did I see it right? Was it okay or did I miss anything in terms of this new architecture design? No, I think you said it absolutely right.
Maybe we'll just talk a little bit about the fact that we right now chose a week. I think in the early days of the test net, we had a not very evenly distributed network, but now that the network is so distributed, we think that a week is good because whatever changes are happening within a week are usually not that
right. That's right. Like in relative terms, and like if we only have three validators and one leaves that the massive change to relative powers, but now that we have 50 plus validators, you know, and a lot of like a pretty even distribution at the top. Most of the changes that we do
see during the week or not that drastic so that we don't actually need to record every little change that we have done in the past. Yes, good, excellent, excellent, agreed. So right now on the Paloma test and on BNB chain, Valsas have been reduced. I think now I saw when I last checked there was
was at least 24 hours since the last I'll set update was showed that things are working. We're now also testing message relaying, which gets to our next topic, but we're really excited about it because not that the file set updates have been reduced, we can then upgrade this to main and want to get this out there quickly so that validators are
like, hey, this is not, they don't have to worry about holding EFO, worrying about EFO being consumed so quickly. So great. ETH through-- so here are the wins for the Pulumma Network of Validators, is particularly in ETH. E3 funds are greatly reduced because much less EFO will be spent. That's great.
We save on gas. Next up, publish Valsets on quiet chains will be weekly. So if we're on, you know, sameatic, which is a quiet chain for us but not for Mattic, or we're on a new chain, those, you know, those Valsets will not be weekly as we ramp
up communications on those pipelines or rails as it were. And also this means that we can deploy to more chains with less cost. Right. So and that's the goal. We want to get Paloma to less change because that's how we increase, uh, transit message relaying volume is we have to go to more chains quickly and we don't
want to go to more chain selling validators, oh my god, love, now you have to worry about even more money. So by putting this pressure on, we do get to do something now which we want to do aggressively and promiscuously which is deployed to more chains and we have more chains in mind. So that is what we're looking to do with that particular update. And we're on test
That's good news. It's working. I want to say thank you to all the testnet pigeons that made it happen. I think without the testnet pigeons, this would not be possible. So testnet pigeons are the heroes, the heroic birds that are keeping the main net going because again, we need to make sure that the testnet runs.
And that did is up and running and we know it's costing everybody. We know that these things aren't cheap, serve for time and serve for resources aren't cheap. So we would like to go really, really fast and continue to quickly stand up this network. So good news there. Next up, we're going to talk about security.
We had a new vision of pigeon that was currently available. I think that's the 1110 or the 1111 that folks are on and in testing this week we discovered that we'll talk about what that upgrade was supposed to be. So that upgraded that was
recently released and I think it's a 1.2, I think it's a 1.1. What version of Pigeon are we on? I need to just check it myself. Oh my goodness. Right exactly. It's the triple ones. 1.1. Okay, so that version
of Pigeon came with a new feature that we talked was the security added security so that it would send in this payload, in this message payload across the chain. It will also include the public key of the Paloma account can
the "Cosm wasm" address of the Paloma sending account so that these two pieces of information can be verified by the smart contract, by the receiving smart contract, the receiving account, that message is coming from an authorized sender in the Paloma network.
So the problem with Paloma today is that anybody can send any transaction to any address and we'd want to give away where developers are like, "Hey, I just want my accounts to be able to control my accounts." My accounts in Paloma to be able to control my accounts
any theorem, right? You want to limit that. So what we did was we upgraded the message relaying to add those accounts information to the payload, right? And so we've added it, we've installed it, but in testing, because remember we have now testing the balsad updates, right? So hey, how can we test just in time balsad updates? Let's testing
ability to send these secured messages or these sort of, uh, mess access control messages. Uh, and we were sending them and found out that, um, the access control wasn't working as designed. Um, the problem was that the, the, the, the actual payload did not include the address on the public
the key. So we're making a fix, right? And that fix will make, want to make that fix and really are testing it as of today, testing the ability to check if that fix is giving us the desired outcome on the smart contract
that we're trying to control. So the smart contracts we're trying to control are now checking to see, hey, did that message come from this account? And of course, we're depending upon the consensus on consensus on Paloma to prevent forgery of the payload of messages so that no pigeon will sort of, you know,
change the message in flight and whatever message information in flight is verified and validated by consensus. So once we're just about close to verified as working, I think we're going to have a new release of pigeon that will bring this fix and quite a few other fixes that will
we're looking to include. So let's talk about those other fixes now. But before I go forward, I get everything in that section when we're thinking about the forwarding keys and the forwarding costments addresses. Yeah. Absolutely. Oh, some miss. Okay. So then let's talk about the other performance improvements. But let's first talk about the bad news.
or the performance problems. All right. So the performance problem was that we noticed that the message architecture for pigeons ever since we did the upgrade to 1.0, that started testing. We were just a few weeks ago, if you were in the network, you notice a bunch of pigeons were losing ability to create blocks,
So basically, you know, even the one of the big validators were just knocked off. They were just like never gone. I'm gonna go on hers. And the reason why they were gone is that the message queue on the plumber was overloaded with thousands of messages. And why were thousands of messages in the queue? Well, thousands of messages in the queue because a number of messages
message had failed to be delivered on Ethereum. And because that message had failed to be delivered on Ethereum, it failed to deliver on Ethereum because it timed out. So the smart contract on Ethereum said, "Hey, your message came too late. Sorry. Bad news, bro. And why don't you have another pigeon?"
try. So because the message failed, other pigeons were trying to re-send the message with the same failure state. So you imagine you miss your bus to go to school and then you suddenly send your friends to come try to get the bus even though the bus has gone. It's very much a pointless exercise.
And pigeons are not the smartest. So they were very resilient, but not the smartest that kept retrying the messages. And because they were retrying the messages that every pigeon had to retry, you literally had thousands of messages sitting in a queue, which had to wait for every pigeon to touch it. That is bad. And so that was, you
essentially resulting in heavy load on the communications network between data centers and the nodes, and that was not good. So we wanted to fix that. And there are some other things like we were getting account sequence mismatches because
The validator key is also the pigeon signing key and it was working overtime, sending key polives, sending transactions, a lot, a lot of business happening. So improving pigeon performance and pigeon relay performance is now super critical. Before it was all about upgrading to Cosmos SDK for seven, that been
critical. Now before that, it was of course testing and I'm grading Paloma. Now we're doing a lot of work on improving pigeon. Pigeon needs to become even better performance. And pigeons fast, like the Paloma pigeons are very fast. Once there is not a lot of messages to be sent and once, you know, there is no message delay.
But if any issues happen, then things get clogged up. So we're making some changes. And those changes are going to be huge. One of the changes is now we're going to change how pigeons get messages. Pigeons usually get messages in a sort of round robin selection. And then each get
One message so that there is no competition for messages. This actually happened because last year pigeons were fighting each other for messages and again the network failed. Pigeons can be violent. So now we're going to change it so that all pigeons will get a selection of messages. So instead of pigeons either fighting for
one message all at the same time. Or pigeons grabbing one message and having that for a long period of time, we now let all pigeons grab a bunch of messages at once. And because all pigeons can get a bunch of messages at once, this means that many pigeons can essentially be pecking on many, many messages in parallel.
And that means more validators working on more messages, which means more speed. Also, we've changed failing functionality. When messages fail to be delivered, we don't make it at every other bird in the flock has to retry this message. If the message fail, one bird gets it, it's out. That is it.
It goes back, it is as if, hey, listen, the bird try, the bird couldn't deliver. Let's move on. I mean, there are other optimizations we can give to this, so we can get greater consensus reliability on pigeon failure. That will come later. But for now, what we're going to say is pigeons at most will send a message once. And if the message fails, no.
When we say failure to deliver, we're saying failure coming from the EVM site or any other target chain. Let's say we had a message going to Cardano, wink wink, and that message arrived at Cardano, but at Cardano Smart Contract we turned, "Hey, this message, this had an issue," then
we won't have every other bird tried and we will say that consensus comes from the failure on the error on the the error will come on the the target chain side because remember if there's an error on a contract execution guess what we will see the error on that target chain so therefore
For all pigeons can attest to failures that happen on the target chain. Very, very cool stuff. Again, simple fixes, big impact. And so now, Paloma is going to be a bird with a rocket, and that is our goal. So if we can get the bird to get a rocket, that means that the bird consent even more messages
across even more chains and take on more load. More load means more profits for the birds because then the birds can feed on more grains, right? And people will pay more grains to get more message delivery. So again, things we could not have foreseen a year ago because we didn't know what eventually this would
look like and things we could not for seen six months ago because even at that point we were just trying to get balsad updates working and consistent right we were just getting stable security messages now we're moving from stable security messages to stable relay messages communication messages we are in a new world
And that new world means that we have to optimize. So of course, speed is here. Yes, go ahead. We couldn't even foresee that in our internal testing. Right. You run everything private, very controlled test net and then also even in the public test net. Yes, right. We didn't see that.
see because it's just not the same as having all the valid is online. Correct. Set up in hardware. Correct. Yeah. They choose to run. Yeah. Having a three node private testnet is nothing compared to having a 45 node public mainnet. You just don't see the same
issues because you don't have that many computers having to communicate with each other. This is a coordination problem, right? And so all of blockchain is a coordination problem because we're coordinating between independent entities running their own software, their own data center, their own computers. And you know, it is making sure that there's no
way you can foresee. It's just unknown unknowns in the execution. So we want pigeons to improve their relay performance and parallelize them and then fail quickly and fail hard. Now try to keep going at it because that's costly, right? Like any pigeon that keeps
trying a failed message, it's costing the validator money, and because validator time is what we're trying to reward, right? So we're very excited to make a faster breed of pigeon, a more resilient and greedy pigeon that can consume. So,
All this and more is currently what has been the feedback and lessons from the last week. We're really excited to get an upgrade on Maynet again very, very quickly. Of course, we'll result in a chain halt and I think we'll look for that chain halt to occur on Monday. So we were looking to put up a proposal
to the community to vote for an upgrade on Maynet on Monday. And we'll see if we can get as many fixes in by that time. So that next week, we will be in yet a different world. And that world, most likely, will be the world of the robot pigeons. So look
looking forward to making that happen. Vera, did I miss anything? Anything else we need to cover before we wrap? >> No, that's all good to me. >> Awesome, rock and roll. Well, thank you, Vera. Thank you, community. Thank you, volume team. Thank you, Paloma Pigeons. Thank you every single validator, Paloma validator, pigeon on this network.
We are moving towards making this this really small network very versatile but very valuable and so Let's let's we're on our way to converting You know, if I'll set updates and to now essentially important mission critical messages that will be flying
across the crypto universe. Until then see you next week. Have a great June. Thanks so much from volume.finance. Music. Bye.