3 Burst results for "Ibc Channels"
The Crypto Basic
Terra Classic All Set To ReOpen IBC Channels Tomorrow
"7 a.m. Monday, December 5th, 2022. Terra classic all set to reopen IBC channels tomorrow. There are a few things to note as the Terra classic network is set to reopen IBC channels tomorrow. The Terra classic network is set to re-enable inter blockchain communication tomorrow, as confirmed by re XX terror rebels, AKA Rex, a member of the terror rebels, an independent Terra classic development group, in a tweet hours ago. According the post Terra classic all set to reopen IBC channels tomorrow first appeared on the crypto basic.
The Crypto Basic
Voting Is Live For Terra Classic Proposal To Re-open IBC Channels By December 5
"7 a.m. Thursday, November 24th, 2022. Voting is live for Tara classic proposal to reopen IBC channels by December 5th Edward Kim has initiated voting for the proposal to reopen IBC channels before the V 23 upgrade. Tara classic core developer Edward Kim has initiated voting for the proposal to reopen inter blockchain communication channels before the V 23 network upgrade per tweet from the developer today. If the proposal passes, the Terra classic chain will the post voting is left for Tara classic proposal to reopen IBC channels by December 5th first appeared on the crypto basic.
Epicenter
"ibc channels" Discussed on Epicenter
"Think it's obviously a little bit more complicated for sure than the V one. What mesh security really is is the V three design, but run bidirectionally. Instead of just one chain providing security to build security three in multiple directions. For my understanding, I believe the informal team had actually paused the development on V two and V three because they found what they thought there was issues with it. And so what we were able to do was help them explain like, oh, this is actually how you solve this issue and this issue of this issue. And now I think they are pretty on board again with moving towards this idea. So I was chatting with you on yesterday about like, I think they're also really excited about my security as well. And we're going to help build this. I know, I know that I know Jake from Juno is so excited. He's like ready to start hacking on it this weekend at hack awesome. And he's like, okay, we're going to start building a prototype right now. Him and Ethan fry and we're going to try to build some primitive pieces today. Obviously this algorithm. But this actually an interesting thing. It's like kind of like randomly independent. One thing I think I've realized by just talking to people at this conference and just seeing how the state of development is, I think that we have to start treating cosmos a more core piece of the cosmos stack where it just so much faster to do faster. They could prototyping in. The causes SDK is really supposed to be this kernel level code where you know, if you need to touch the deep stuff, like staking or how transaction fees were, that stuff should really be in SDK. But DeFi logic or new IBC protocols. That's up is way faster. And IBC. And I think cosmos. Yeah, yeah. In cosmos. And I think that all cosmos change actually going forward, or it causes SDK to change at least. Should implement some sort of permissioned cosmos. Similar to our osmosis does. And I think change that don't honestly are going to be kind of left behind. We've actually added, we have our first core module that we've written in cosmological now, which is IBC rate limiting. It's like a way of dealing with hacks and stuff where it's like, it says, hey, only 20% of IBC channel PBL or whatever can go every 6 hours or something. So basically all your IBC can L your IBC transfers are going through cosmos. They're not going through the internal level. Well, they go through the causes of because the IBC modulus and SDK. But then when it receives fun, IPC packet, it passes it to the cosmos on contract that does the rate limiting. And then the contract. The middleware stack is impossible. This is so interesting. Okay. So with regards to with regards to this permission permission, cosmos thing you just mentioned to you explain what do you mean by that? Why would it be permission? Why wouldn't it be permissionless? Because I don't think that you don't want a permissionless chain where anyone can start deploying whatever you want. It's just more of a way of oh, I see. So you're saying that change to deploy cosmos as a way to implement other sorts of functionality for their chain and at a minimum and then perhaps like some other exactly, yeah. So this IBC rate limiting contract we are going to add to our sources, but I'm sure other change will want to add it as well. So it's just a way of iterating quick more quickly on features. Yeah, okay. As opposed to say Ethereum route where they built all these core functions like into the EVM in cosmos, it would be better to build them as contracts and you have the core modules call them. Okay, very interesting. So one of the things that our team has been working on a lot over the last three or four months is deepening the relationship like the how easy it because right now you have a lot of teams who are very causal SDK focused, right? They don't use cosmos. And then you have a lot of teams that are very cosmos and focus, so confio team that build content was and they kind of really only think in terms of cosmos. Juno is very much like, you know, their core chain is very, very minimalistic and they have a lot of cool logic on the classroom was inside. But osmosis, we have a lot of stuff happening on the cost of SDKs and a lot of stuff happening on the cosmos on site. And so we've had to spend a lot of time making the interaction process between these two systems, like very seamless. And so yeah, so I think that tooling that we built is going to start to be able to be used by more change as well. What do you think in that context then around the prop 69 implemented cousin was in the cosmos hub, which failed. And now they're building neutron, which is a smart contract platform. So what are you thoughts on that for? Oh, I bought a guess on rob 69. So I think it was like a no brainer. Yeah. What do you think about it? Yeah, I mean, hearing you now, I think that perhaps it makes sense to implement it on the cosmos chain as the cosmos have changed. It's kind of a permission thing so that more functionality will come to it. Yeah, I also felt that having caused a Muslim on the cosmos hub was not, yeah, I think I voted no on that as well. And yeah, it's not the role of the cosmos. So I think especially after Adam two, prophecy 9 wasn't for permissionless cosmos. It was for permission to cause a loss. Like I said, I don't think it's the point of it is not to add more functionality to the hub necessarily, right? I think it was to