I'm Dilu and I'm planning to talk about why mobile developers should have a serious look at Flutter. Yeah, before start-up with things, anyone who has experience with Flutter? Okay. See, it's cool. It's great to see that all of you guys are new and because I can give you the actual thing behind that why, as mobile developers, why we should have at least look at Flutter. So this is basically about me. I'm currently studying at IIT and I'm part of GitHub Campus Expert Program also. I'm a training associate of engineer, so on 24-7, and we recently initiated Colombo Flutter Meetup at Sri Lanka. That's the first ever Meetup in Sri Lanka. So and this stuff, I'm kind of part of and I'm contributing to these organizations. So yeah, before moving to Flutter, you know, like nowadays we have this, we already had the mobile application development, right? So yeah, before I thought of like, before going jump into Flutter, if you can have a kind of a look at how mobile application development so far, then you can get the actual idea why I'm telling that you should have a serious look at Flutter. So yeah, when it comes to mobile application development, so we have these three platforms, right? So we have Android. They released the SDK back in 2009. So we have iOS. They released the FS SDK in back in 2008. And Windows. Do we have any Windows developers now? Okay, we have quite a very low number of developers for Windows. Okay, that's why I put the logo there. So I want to like, moving on, I'll only talk about these two because like, without comparing with Windows and stuff. So basically these are the major platforms that we are using today, right? The Android and the iOS. So like when it comes, even you are an Android or iOS developer, anyway you have to go through these layers because like that's the very high level layers that you have to go through in your application. So like, if you consider about the layers, like in the top part we have these widgets which renders your UI, whatever the thing that the users interact with. So that we, on your side we have the Cupercino widgets. In Android side we have material widgets with, they recently came up with these material principles and all the stuff that, to make sure that users are happy with the UI. So yeah, then the second layer we have the co-services and also in the Android side we have the application and the frameworks. So moving on, the third layer, that's kind of important because we have the co-OS in the iOS side. Comparing to iOS, the Android side we have the libraries and the runtime. And the bottom layer we have the kernel drivers in iOS as well as in Android side. We have Linux kernel and the device drivers. So this is a very, very high level thing. So like if you are just thinking about the native application development. Like in this part I'm talking about applications for single platform. Basically like, if you are developing application for iOS that means a single platform, right? So then again, if we consider a kind of high level architecture diagram. So here you have this application which was written in Java, Kotlin or Shift. Earlier days we used Objective C and in the other part we have the OEM widget box where you render the UI. So your application code directly communicates with the OEM widgets in order to render the UI. And also we have the Canvas and events in the same layer, in the same level. And whenever your application wants to use any of the location services or Bluetooth services or else assume that your project is using any other sensors, like any sensor, like you want to access any sensor, we call them through the services. So this is kind of a very high level thing about native application development or this application for single platforms. So whatever we do and whatever the platform we are talking about, everything has course and pros, right? So these are some of the pros that I noticed in single applications for single platform or the native applications. So like most of people telling that native applications are fast. So that's a key thing that hybrid applications are trying to achieve. So and it's also responsive. So also it has continuous support, yeah, because most of the native language native applications develop with big brands, right? Android said we have Google in the iOS side, we have the Apple. So and also the variety of features that we have, because we have already proven that Android applications or iOS applications, that's what today we are using, right? So it's already proven. And the community, that's the biggest part. So we have a lot of developers who has specialized in these areas, Android or either iOS. So moving on to the consite, the major thing that I see, as I assume you are a startup, you want to start a startup. You just want to make sure that you build mobile apps. So in your early stage or assume that you want to develop application for your freelance project or something like that. In that way that having two code bases, having two languages, it's the same case that every technology for multi-purpose, that's the selling point, right? That's how they promote it. So you have one code base for both applications. That's the anyway, I listed the same thing here. Also like maintaining two different projects and two different set of developers for both projects. It's again, it's a disadvantage. Assuming as a large scale company or a large product based company, so it's a disadvantage. So I don't know whether you guys have experienced that developing features in a synchronous way. It's somewhat hard when coming to native applications. So that part also I mentioned here. It's like if you are developing a feature in very synchronously, you have to put some effort there. So the next thing, like we had the applications for single platform. Then this one of the diagrams which shows the applications for multiple platforms. It has basically it's a kind of summary. So in this side we have basically two approaches, hybrid or the cross-platform approach. Maybe you guys are very familiar with these technologies. So one of these technologies. So if you are considering about hybrid approach, we have what do you call the application which was written in one of the markup languages like HTML, CSS to add styles, and we use JavaScript or a scripting language to add double logistics and stuff. So and also there are famous stuff like Kodowa, PhoneGap, and Ionic. Ionic is one of the very famous stuff for when it comes to hybrid approach. Then the other side is cross-platform approach. So in cross-platform approach we had maybe, have you ever noticed that we have two parts reactive and non-reactive? Okay. So moving on, these non-reactive stuff other than summary, I don't know whether anyone has used an accelerator? Anyone? Okay. So it's under the non-reactive part. So it's basically something similar to reactive, but it's more kind of, it's not developed in a very good way like reactive. So but the main reason reactive came up with they have then that reactive components. So in the other part, in the non-reactive side we have summary. Anyone have worked with summary? Okay. So summary is again, when you're developing large-scale, highly scalable mobile applications, we use summary which are written in C-sharp, and to the UI you can even use ASP.net as I guess. I would never work with summary, but I know the summary is there in the non-reactive side. So any react native developers? Okay. Cool. So react native is there, it's Google Flutter also there in the same area. So I'll talk about react native and Google how Flutter, how it differs in my next slides. So and we have the native JavaScript for write applications. So these are technologies that we are using to try to make sure that we can write applications for multi-platforms. So okay. So again, like before moving to in-detail stuff, this very high-level architecture about hybrid approach. Can you list what's the difference between the previous native architecture and this one? Anyone? Yeah, yeah. Bridge is there. Again, we have replaced the OEM widgets with something called WebView. So this is kind of a thing which runs on your browser. So it's basically we develop an application without thinking it as a web application. At the end of the day, it's a mobile application, but still we use a web view to render our things. So that way only we can communicate with the canvas or the events. And whenever the application, your hybrid approach application uses any of the sensors as in due to sensors or GPS or something. We have to go through this bridge because it can't directly communicate with the markup languages or the JavaScript languages. I'm not talking about the react native. This is something about the hybrid approach like Ionic or something like. We have this bridge in between these two steps. So moving to the pros and cons, in the pros side, we have a very good thing. We can do CI integrations, continuous integrations. So because we develop our application in the same way, we develop a web app. It's something similar to that. So even you can use your application as a web application. At the end of the day, if you have to change bit of UI and you have to make sure that some stuff are mapping your browser screen. So that way you can make sure that you can use the application as web application as well at the end of the day. So, and also we can use continuous integration. That's one of the key things, one of the key pros in hybrid approach. So moving on to the cons side, it's relatively slow because like OM widget, it renders the native components in cons side. But in this hybrid approach, what we have is a web view. So it has to make sure that the UI renders through a web view or inside the browser. So in that case, it causes some of the slowness in the application. Maybe you guys will experience lags, not for like smaller, small applications, but when it comes to large scale stuff, when we will experience those stuff. So it is one of the key points for use experience as I think. So moving on this cross-platform approach. This kind of a high level, very high level architecture for cross-platform approach. So we have the transfer native code in our left side, in my left side. So the framework libraries and SDK for non-reactive part, then this part is not basically a bridge, but we have something called JavaScript bridge. But in React Native, this is a very, React Native have very improvement way, improved way of communicating with the OEM widgets or the services. But still just to give you an idea about cross-platform approach, the entire technologies that we have in the cross-platform section. So it's something like this. So in cross-platform, did you notice that we have, again, we have the OEM widgets because the React kind of native, like when technologies like React Native, they can, now they can render native components as well. So then again that we, in this case, we have achieved that fast, the fast point, right? The native applications are fast, they are saying because they renders native components. So that thing we can achieve here as well, but not to that level. Like we experienced in native applications, but still we have the OEM widgets at the end of the reactive applications. So we also, in order to call with services, like we just have to go through it, RX bridge, the so-called JavaScript bridge, and the reactive part. So in that bridge, we have both non-reactive and reactive because in cross-platform approach, some of the stuff are non-reactive and some of the stuff are reactive. So this is the path for reactive stuff and that's the path for non-reactive stuff. So yeah, okay. I have the same thing, right? Not the same thing. It was a mistake. So I'll just keep it like that. So if I'm talking about the pros and cons in here, so I already mentioned that we have OEM widgets. So at the end of the day, we renders the same native components. So it's the look and feel somewhat similar to native components, the way it renders through the hardware. It's somewhat similar to native components. So even when you're accessing the services, it's way easier than the hybrid approach in these things. If you are considering about the cons in this approach still, that we can't achieve the frame rendering speeds, like assume like the native applications, we have 53 to 55 FPS. If you're trying to render something in that FPS count, we can render up to 55. But in this approach, I think in a cross-platform approach, we only can reach up to 51 or 50. So that was one of the major cons in hybrid approach. So if assume that you want to render kind of a very rich graphics application, so it's very hard to render stuff. We will realize the lags are there, the colors are coming, and it's still trying to render the colors. So those kind of stuff are there. So if I jump into Flutter, I'll talk about in a very brief way about the Flutter architecture, this is the exact very high-level architecture for Flutter. The Flutter has native ARM binary code. One you write with the dot language, so Flutter uses dot as the language, and they convert it to a native binary ARM code at the end of the day. And they have Flutter widgets. Flutter widget includes, maybe you guys have realized that in OEM widgets, we had Kupochino and Material both. So in same way, in Flutter, we have this Kupochino and Material widgets as an in-built thing in Flutter. So, and we have some thing called platform channels where they release all the plugins, libraries, to in order to achieve the services and all the stuff. So this doesn't work as a bridge because it doesn't convert anything. You can just import the plugin or the library, and you can directly call to the services. So yeah, Flutter runs on. So, as Google says, the Flutter runs on Jellybean and Android Jellybean up to, even it runs on ARM devices and up to 4.1. So, beginning from 4.1, the latest version to the latest version. So in iOS side, we have, we can Flutter supports iOS 8 or the newer versions. Also, the minimum hardware runs on iPhone 4s. So you can develop your application, you don't need to worry about the old phones or the old devices. So if we consider about the path, the Flutter came. So Google unveiled Flutter in 2015 during the Dart Summit, the Dart conference, or the Dart Dev Summit. So, and then they released their first alpha version in 2017, back in 2017. Then the 2018 was one of the most successful years for Google. The Flutter team announced the preview to the most stable version. We jumped into Flutter and tried some code and tried some application. So it was a very stable version where the developers started to, where the developers started to play with Flutter and what do you call, to make nice things in Flutter. So then they realized the current version is only have few fixes. So they released the version one back in 2018, December. So, and we are waiting for something called hummingbird. Without explaining about hummingbird, I'll keep that part for the last slides. So I'll jump into hummingbird in my last slides. So what is Flutter? So if I'm giving up just a short answer, it's the latest mobile SDK that was developed by Google Flutter team. And to develop high quality applications or high quality UIs, it can achieve very high quality stuff. Basically, I'll talk about the FPS rate that Flutter can achieve and all in later. So it supports both Android and iOS devices. And even in future, there's a project called Project Hummingbird, that's what I was showing in this diagram. So they are jumping to hummingbird in order to make sure that you only write once, you covered everything. So yeah, as I told, it's write once, run both. This is not a big thing, right? It's not magic. It's happening in every cross-platform or hybrid approach application. So it's one code base. So one code base to maintain. And also in Flutter, you have expressive, beautiful user interfaces. Some of the parts are very useful. I'll talk about those useful stuff. For now, it's very expressive and beautiful. So it has quick development. So the things come under quick development is like Flutter has something called hot reload and hot restart. Whenever you change application, assume you got into error and you fix that. I'll show you a kind of demo. So you fix that. You assume that you need to change the entire ABBA color in ABBA color, or a complete widget, or kind of thing, a complete part of your application. So it's just you change it. And one click on the hot reload button, it will appear. There's no delay between the rendering and the change. The moment you change the thing, you just press on the hot reload command R. It will build. It won't show you any progress lines or anything. It's that quick. So if you're looking to some kind of a demo project, once you've created the new Flutter project, Google giving this demo project which has the counter. You can press on a button and increase the number. So I have a pixel and the iPhone XR, which runs with iOS 12.1. This is the first time I'm running this application. So this project, so in the first time, it will take some time, as usual. But for further development, when you are working with the application, it won't take a lot of time. OK, so until it loads, you want to write one code base. And you need to deploy it through a mobile phone. And also then, as the extra. OK, that's why I told the hummingbird. There are a lot of surprises in hummingbird side. So just wait for hummingbird project slide. So now it's, I think, OK. This is the application which they give us as the demo application. So you can just press on a button and increase the number. That's the demo application. So you can see here the color is blue, right? The entire application or the app color is blue. So how do I show you the, OK. This way you can see how quick Flutter is. So assume you want to change this into red. Now it's made my change. Do you realize that? You may think the Android Studio also has the same button. But what it does is it renders the entire application again. So in Android, maybe you guys have experienced the same button is there, the kind of that button. So what Android does is they build the complete application again. But what Flutter does is it identifies the widget which changed, and it only renders that widget. So it maintains something called states. So it just refresh the state. That's it. Instead of building the entire application, it refreshes the state which helps to change the color from blue to red. So OK. I'll quickly go like since I have very limited time. So Flutter has something called, in Flutter, every UI a button, or whatever the thing we use, it's everything we call as a Flutter widget. So in Flutter, maybe a button or a menu, it's a widget. In a font color scheme or whatever, the padding stuff, aspect of layout, all those stuff are a widget. Even if you assume you want to capture a tap gesture, use a tap or something like, even it's a widget. So you can have a lot of widgets inside your widget folder. So you can reuse them. Assume you are creating a custom button, and you don't need to write it twice, so you just don't need to just import it everywhere. You just create a widget inside the widget folder. Just use it everywhere. So basically, what's a widget? If you're considering this part, the app buys a widget, and the hello world text, it's again another widget. So the scaffold, there's something called scaffold. When you're creating the scaffold, it's a widget. And the entire application is, again, a widget. So if you want to use this entire page, you just have to take the upper widget, and you can use it. So they maintain something, a widget tree. You can see, in this case, we have a card widget. And this is a widget tree, since I have only very short time, I'm moving on very fast. So you can just go through the Flutter widgets. You can just search for Flutter widgets. There are a lot of widgets. They have come up with everything, the shapes, and also everything is widgets. So they maintain the states, I told you guys, right? Instead of rebuilding the same application, the entire application, they only refresh the state, related to that part, or your change. So this is one of the key points that Flutter, it's capable of 60 FPS. And do you guys have here about racer phones, which you use to render games or graphics? It has 100 FPS capable screens. So even Flutter supports 120 FPS using the version one. So this high level architecture, this is there in documentation. We just have three main parts, the Dart framework, the Flutter engine, and the platform specific stuff. This is there in documentation, the entire diagram. So Flutter does not use OEM components. I was talking about this. So Flutter uses Dart, because if you are really comfortable with OOP related language, object oriented language, it's really the learning curve is very small. You can just learn Flutter within one week or two weeks, and just you can play. And you can develop beautiful apps. So it has fast allocation, and predictable high performance, the object orientation is there, and the developer productivity. So in Flutter, you can achieve the both native experience. In Android side, even you can write, if you want to see the native Android look and feel, instead of your custom feel, look and feel. So you can have that also in Flutter. It's built in. So it's free and open source. Even you can change the code and try out new things. So you can use these. These are the people who use Flutter. The Alibaba application, they entirely moved to Flutter because of the rendering time. Because of 120 FPS, Alibaba is using 120 FPS to render their mobile application. Google Ads now use Flutter. And these two, Hamilton. Maybe you guys have used Hamilton. So they are also using even the JD. So big brands are there, they are moving to Flutter. So one more thing, that's what I was talking about. So with the Hummingbird project, Flutter is capable of one code base, a Windows application for your desktop, a macOS application for your desktop, application for IoT devices, and also application for your mobile devices. So only one code base covering everywhere. So waiting for Hummingbird project, it's under development now. So next big thing in next December. So you can write one code base and have five or six apps for every platform. Isn't it cool? That's why I'm telling, start. Have a serious look at Flutter. Start learning Flutter, it's kind of an investment. You can just move to Flutter in next December. So this one of the applications which we do have, can you see the shape? How hard it is, how hard to achieve that shape in what you call in Android? You have to have import an asset. You have to design it using a designer, or you have to get help from a designer. So the thing is there, but still. So in Flutter, there's something called G Clipper. Just to import G Clipper, you can draw the shape. You give the points, 0, 0, that point and this. And you can just curve and adjust and all. It's simple. It's inbuilt. You don't have to import anything from outside. That's why it's fast. So I'll show you guys kind of a quick how fast, same application. I developed the same application using Android. And see the same shape and the same home screen. How fast Flutter is. See the shape is there. I'm importing the shape. I'm designing the shape. And I'm importing it to Flutter. The shape is already done. There you go. I was using the same laptop. I tried using the same internet connection, same. Everything same. Even the room temperature is same. Same place. It's done. 2,000 years later. So you can realize if you're working on a large scale project, how fast Flutter is. So yeah, that's the end of my last slide of my presentation. So yeah, the hummingbird. Just jump into Flutter and try out some stuff, because hummingbird is on the way. When you have a hummingbird, it's going to be a real cool thing. And it's from Google. Thank you very much.


Good morning and welcome. We're coming to you from day three of the Fiji Symposium in Bangalore, the platform for all dialogue on financial inclusion. And with me today is the Deputy Director for Financial Services for the Poor from the Bill and Melinda Gates Foundation, Mr. Daniel Radcliffe. Welcome Daniel and thank you for being part of the Fiji Symposium. Thanks Anush. It's great to be here. I appreciate the time to chat about it. That's great. This is the first ever Fiji Symposium. Your thoughts on this? Well, I think the timing is right for Fiji and the reason I say that is five, six years ago mobile money or DFS through telephones was a nascent domain. You just didn't have huge amounts of transaction volumes running through these platforms. Today we're starting to see big growth in mobile money deployments all around the world. That creates a whole new set of challenges and risks around cyber security, fraud, etc. These are things that the traditional financial inclusion community is just not exposed to. So in this new environment it's now critical time to bring in the standard setting bodies of banking, BIS, the standard setter around development policy, the World Bank, and then thirdly now the standard setter around telecoms which brings a much more sophisticated level of expertise around cyber security, fraud, using the telephone. So now is the time to actually bring in that level of technical expertise as mobile money platforms grow globally. Could you also tell us a little more about the potential of digital financial services to actually increase financial inclusion? Yeah, so first off one of the interesting questions we had five, six years ago was would mobile payment systems and DFS systems from these non-bank providers, would they cannibalize banks and their business? In fact, we're seeing the opposite. In the most advanced markets in terms of volumes, Kenya, Tanzania, we're seeing these mobile money platforms actually serve as a springboard for the core banking sector to expand its customer base, to expand its available credit, and that's a big deal. We didn't know that was going to be the case four or five years ago. And so now we're reaching this point where we can credibly go to banks and say, listen, do you stand to benefit from allowing these new players into the business because they allow you to identify customers remotely, they allow you to access customers remotely using telephone, and they will allow you to access a huge trove of data through the SIM card that can then be used to inform credit scores. And so it's now reaching this true win-win opportunity between banks and the non-bank payment providers, so that creates a massive opportunity not just to onboard poor people into a transaction account, but to connect them to a whole suite of services. The last point I'll say on this is that all those things I just described, access to a trove of data, being able to interconnect to the core banking system, that all requires a new set of technical standards that requires interoperability standards, not just between mobile money providers, but also between the mobile money systems and the core banking systems. It also requires data privacy standards that allow that trove of data to be shared in a safe, secure way and used soundly by the providers. And so for those reasons, to catalyze this expansion into real financial inclusion, it's now a time when we need a new set of standards, and that's why we're bringing together BIS, ITU and the World Bank. Now that we know the good points about digital financial services, what are the few factors that you think might be the deciding factors for people below poverty line to actually prefer digital financial services over the traditional methods of cash? Really good question. It's got to be extremely cheap. We can't have scenarios where people are having to pay fees every time they're doing transactions when cash is just a free service. It's an easy service. The second is convenience, particularly in terms of proximity, that the likelihood that a poor person will walk two, three kilometers to conduct transactions is minimal. That's in part why we're going to need regulators to figure out those distribution networks, allowing those companies that have the distribution networks into the space in a safe way. I think a third hook is going to be government transfers. You look at the poorest, most vulnerable households in the world, many of them don't have liquid cash or significant amounts of liquid cash to engage in DFS. Poor vulnerable households also should be very strong candidates for social welfare payments. Those social welfare payments can be a powerful onboarding trigger, but they can also be structured in a way that pulls people into financial behaviors. You get your monthly welfare payment into your account and press 1 if you want to divert 10% of that each month into a long-term savings account. Press 2 if you'd like future payments to be diverted into a school fee account, etc. These are some of the hooks that I think will be important. You have quite a few things that we can actually use to help them prefer digital financial services. When it comes down to the Bill and Melinda Gates Foundation, what exactly is your organization's role in increasing financial inclusion and how important is it for everyone to move towards this? Our role is really to try to place bets that we often think of as a three-legged stool. Government is, of course, absolutely essential, but taxpayer dollars are, by nature, risk averse. It's very hard for government bodies to take risks with taxpayer money. Secondly, you have the private sector, which, of course, is going to be an essential player, but the private sector, by its nature, is going to be focused on profit-maximizing in general. That creates the third leg of the stool, which is philanthropic money. We don't always succeed, but our goal should be to place risky bets like this one, bringing together behemoth standard-setting bodies, and take those risks that are needed to move the industry forward. Specifically, in terms of what we're working on, the first pillar that we work on is something that I focus on, which is our regulatory policy change. That we do at a global level through efforts like this, but also at a country level. We have program officers in eight focused countries. The second pillar that we focus on is the payment infrastructure that countries develop. I think when we look at payment systems around the world, they tend to be built on legacy technology. They're often built to favor incumbent players at the center. They have cost floors that are quite high and impede any incentive to expand out into poor and rural communities. We have a team of payment technologists that are working with the World Bank and BIS and others to establish an open-source code library that guides countries off the shelf. They can take this technology to build more inclusive, lower-cost payment technologies using the latest thinking in payment systems. The third piece of what we're working on is usage. How do we trigger excluded population segments? What are the ways to incorporate them into the system? There's no expectation that digital finance is going to be right for everybody at every scenario, but there are some low-hanging fruit opportunities to use government payment systems and credit systems to hook people into the DFS, those who could benefit from it. The last pillar is a research portfolio that is aiming to pressure test. Are these welfare linkages we have in our mind, are they true? When people have access to a payment system, does their household welfare increase? When a government goes from cash to digital, does household welfare increase? Do fiscal savings increase? Does corruption go down? This we really only can measure rigorously through randomized control trials, so a lot of that portfolio is trying to identify opportunities to randomize access to a savings account, access to payments, and then we use that data to pressure test our own strategy is what we're doing actually helping people, but secondly to inform advocacy, because if we find that the Indian government is saving a significant amount of money through direct benefit transfer, you want to have the data to be able to take that to the Nigerians and to the Mexicans and make a case with the central bank that this is worth testing. Those are the four pillars and I think that the key message across all of this is that everyone benefits from an economy that includes everyone, so that's where payments as a connective tissue to include everyone in an economy is at the core of what we work on. I think the Gates Foundation is doing an amazing job at this and thank you so much for being part of the Fiji Symposium. Great, thanks Anu. Thanks.


Welcome to JSA TV, the newsroom for tech and telecom professionals. I'm Jamie Scato-Cutaya here at ITW 2019 in Atlanta. Joining me today, my good friend, Mr. Philip Marangella, he's the CMO of EdgeConnex. Philip, welcome back to JSA TV. Thanks, Jamie. Nice to see you here in Atlanta this year at ITW. Yeah, it's a wonderful new facility for such an amazing global event. And it's kind of neat to try out new places, new locations, new restaurants nearby. So far, total success. And talking about location, location, location, your team's been globetrotting. You can, let's see, Memphis, let's start there. Sure. Tell us more. Yeah, so we just had an announcement last week where we've been in Memphis for a while now. But for us, you know, our primary focus is our customers, right? And working with Comcast and Megaport, it's all about working with them to help bring the cloud local to Memphis. So for many enterprises in Memphis, super excited, right? So you can have the best of breed, best of providers to give you direct, secure access to the cloud local in Memphis. In the past, they'd have to go to Ashburn or perhaps here to Atlanta to be able to connect to the cloud and bring an integrated solution to them local in Memphis is really appealing to the enterprise community there in Memphis. And even talking cloud, for sure, you have so many cloud providers and OTTs leveraging the Edge Connects network. How do you speak to that? I know they're building globally there. Yeah, so you know, it's interesting because we've helped build the Edge for sure. And so many people think of us as building smaller facilities and secondary markets. But the fact of the matter is, is because we focus on our customers and give them exactly what they want, where they want, when they want, we can go very large. The same concept applies. And so we can go to a tier one market like Amsterdam or Dublin or Chicago even and build very large facilities. And I think that's really what's unique about Edge Connects is our ability to support the customers throughout the entire spectrum of data center requirements, right? It can be a cable landing station always all the way up to a hyperscale facility. And that's what really sets us apart. Yes, it's that customer-centric infrastructure that you guys are offering, particularly as it relates to the Edge. Tell us a little bit more about that. Yeah, so it's really defined by our customers. But what they really like is that flexibility to give them a very precise location that suits their needs in a particular location. The ability to then scale that location with their ecosystem partners and their own requirements to meet their future needs. And then to have that ubiquity of to go to any market in the world, right? Whether it's Memphis, whether it's Buenos Aires in South America or Warsaw in Europe and further afield.  And you need that speed and flexibility. And so when you talk about future Edge data center needs and opportunities, what do you see coming down the pipeline? Yeah, that's, I mean, there's a ton of markets that we're looking at. We just went live two weeks ago in Buenos Aires. So it was unprecedented that we actually went live a week ahead of schedule, right? For a market like South America and Buenos Aires, yeah, that was huge, right? And so I think you'll see us to continue to grow and expand in many of our existing markets. And then extend into other markets throughout South America, throughout Europe. And everybody always asks about Asia, so stay tuned for that. Can't wait. EdgeConnect's on the move, taking over the world, literally, figuratively. And where can our viewers go who want to learn more? EdgeConnect.com. Spoken like a CMO. Thank you, Phillip. We love having you and thank you viewers for tuning in to JSA TV. Here at ITW 2019. Happy networking.


What's going on everyone Sam here with late in sports cards ribbon 2022 tops triple threads baseball hobby nine-box case break number 15 random Team style there's a look again at your random results as always you can find these on the website under the results tab as well as the Lincoln Shatt Good luck everybody. Let's get going Thank you guys that's fantastic appreciate that that's gonna be a fun break Tiered is always such a good time, dude When we have a full nice full case. We're running with hey, what's up tic-tac? Let's do our first triple threads of the night. Good luck everybody 10-box Tuesday spots coming in whoa. Oh, that's what I like to see It is a good 10-box Tuesday lineup this week's we've got threads and Contenders and bass in basketball show hey to 199 go to the angels And Ted Williams on the onyx 38 out of 50 nice one there teddy ball games Bernie basically tiered random style is gonna be there's 15 like top tier teams and 15 Bottom tier teams so you get one team from each base and base We've got Cabrine ace gonna be the first hit of the break that is on card 95 out of 99 for the Pirates nice one there Pittsburgh And then we've got William Domis 46 out of 48 No 48 out of 48 going to the brewers nice one there was a little bit of pinch right on it as well There we go. Congrats a brew through George Brett to 298 to 59 on the green and Raphael Devers to 299 on the purple base base base nice one here go into the angels 7 of 9 Mike trout Congrats on that la that's Chris M Very cool 21 multi-homers The two is not cut out on The left side you could see it's still like the patches or the two is still in there Do you want to end the box or not for that nice one there? Congrats to the angels. We got Joe Musgrove. That's 16 out of 75 going to the Padres Okay Yeah Obviously box number two good luck here. It's going on tiktok. Yeah camo patch on the musgrove too, which is kind of cool like that Reggie Jackson 299 and Rookie Spencer trockelson 34 out of 150. There you go Tigers. That's when they're destroyed Jackie Corbin Jram there's a Colin Welker. That's numbered 5 of 50 on card rookie Jersey auto for the Rockies Yeah, I agree Gus triple threads is awesome and and John Carlos Stanton. That's gonna be numbered 15 out of 36 going to the Yankees Congrats on that New York Stantonian glass orange Austin Riley for the Braves to 199 and Vladdie jr. 61 out of 75 for the Blue Jays base base and base Nice one here. We've got Chris sale Rafael Davos Trevor story on the triple Triple triple It's numbered four out of 18. There you go Red Sox. That's Joseph s and Jose Berrios 44 out of 50 for the Blue Jays on the Jersey Congrats Toronto Got Hunter Green rookie to 299. They go Vaughn with the Reds Fernando Tauti's to 150 Padres base base and base Cool one here got going to the Phillies. That's gonna be Bryce Harper 36 of 36 power source Two-color patch on the bottom the you in the R and another Jose Berrios this time 58 out of 99 Jersey auto for the Blue Jays To Jose Berrios is now going for that rainbow Apparently so True Got a redemption coming up guys got CJ Abrams rookie to 199 and Vladdie jr. To 259 it all makes sense That's very true very true got mash Got redemption that's going to the Royals we've got Salvador Perez triple threads autographs rally card You go KC Ryan B with KC nice Salvi One of the best catchers in the game still and Justin Berlander game use memorabilia eight of nine for the Astros now. We met your strews Seven to go in the next triple threads with spots. Nice. Thank you guys down to seven down to seven We used to literally have to cover the computer in tapes Going God Say has a zoo get a 199 good lord for the Cubs and Luba up to 150 Nice one there for the white sauce I was gonna say because some of the people that started like before me obviously like what they would still top of the courtese Would cover the entire computer in it. Yeah, it's funny to look at That's why Bryce Harper because we used to literally have to otherwise we would fall behind There's a Ryan Mountcastle 18 out of 75 on the purple for the Orioles and Reese Hoskins 16 out of 48 for the Phillies. There you go, Philadelphia. Let's go Mookie bets to 99 Dodgers Green Joey Vado 259 Reds Wander rookie and Buster Posey Got a Cody Bellinger. That's gonna be October hero Six out of 27 for the Dodgers. There you go, Jonathan. There we go, Jonathan. Congrats, man Nice belly and Randy arosa rena Randy rakes 11 out of 75 for the rays. Congrats Tampa Tampa on the board now. It's one there. All right on to the next box. Good luck here Something wild make something wild in this box Lane Yeah, it's my guess my prediction. We got something wild See a nasty book Yeah, could be Could be Now Cal Ripken Jr to 199 Each year out of 259 the Manners Chopra Jones Each year and Peter Lonzo. I would say this is pretty crazy. We've got Josh Donaldson That's gonna be 17 out of 27 for the Yankees game use memorabilia. It's actually pretty cool It's kind of wild this next card We've got a Kyle Hendricks number seven of 10 and that's part of a patch. That's also signed That's kind of cool. Congrats Cubs Eric R Yes, O'Neill cruises in this Down to four left in number 17 I did not Shane actually that's pretty cool, man on his Wagner And a nice Cal Ripken color match to 199 the Orioles God CJ Abrams Ichiro Peter Lonzo Next up. We got a cool one here. That's gonna be the hawk five of nine going to the Cubs Andre Dawson Five free passes. That's gonna be game use jersey bat in jersey That's one there again a Chicago Eric R I don't believe so PW. There's no Jose Miranda. I don't think so And Alex Kerala that's uh six out of 18 on the orange jersey going to the twins Yeah, uh, these are so awesome. Such a great product Jonathan Yeah, there's that the Rangers are actually pretty loaded. You've got uh, Adrian Beltre Uh, Dolis Garcia, I believe will be in this. Pudger Rodriguez is in this too I guess not super loaded, but they've got guys in here Hunter Green to 199 Reds And Roberto Clemente on the uh onyx 41 out of 50. We've got that's kind of gross. Um, Spencer Trokelson Rookie Clayton Kershaw and Fernando Tatis Nice one here going to Jonathan. How about two of three Cody Bellinger? That's gonna be a patch then logo and then jersey. There we go Jonathan Nice bellinger game used You look at that tick tock with a patch on the middle of that thing That's so nasty So nasty there you go Jonathan nice hit man And a Brandon Lau 57 out of 75 That's going to the race Nolan Ryan for the Strohs to 75 And Don Matting late to 259. Is that the Vince Kelly cut? I don't think so. Is it an my I believe in there Yeah, it says my my Is it base base base this one's sick We've got going to Joseph S at the Red Sox. How about a triple? Raphael Devers, Xander Bogart, JD Martinez 20 out of 27 Nice hit there. Congrats Joseph. That's so sweet, man Oh, yeah, we'll mag that one up for you Nice one right there triple Red Sox, uh jersey auto to 27 And yoan moan kata That's going to number to 18. That does sting forest for the white socks How many guys will be left on the team when they tell us they haven't done zero I mean, they're gonna be only one somebody left after this year after this free agency. True Forest you picking a new team yet? Rangers are spending money. Yeah Red Sox will keep a player at some point. I heard they were gonna go into next season with no players Just minor leaguers CJ Abrams to 299 and Julio Rodriguez to 125 very nice Machado opt out next year and Devers to San Diego That'd be kind of funny That'd be kind of wild honestly if that happened Two to go two to go. Wow In number seven two to go and number 17 guys George Brett joey bottom lube up Y'all there is still 16 left in the first optic contenders break though So let's start taking some basketball spots. Oh, yeah Nolan Aronato 18 out of 36 for the Cardinals And we've got Nicoladolo 13 out of 75 nice rookie Otto for the Reds there you go Vaughan Rats on that buddy 15 to go now in 15 in basketball. Thank you guys getting that close The Red Sox have been called back down to the miners They've been relegated Elohim that has to 125 and orange Raphael Devers to 199 Of course I come back from eating to this convo Wow Dude this team had a break man Back to the Red Sox. We've got Wade Boggs, Jim Rice and Carlton Fisk On the triple one of nine forest stop watching honestly forest Vaughan stop watching We've got the uh, how about this take a look at this this sighting right here Two Red Sox triple autos unreal man There we go. Congrats on that Red Sox. That's Joseph S There you go, man This one there right there Fisk rice and Boggs Very cool very very cool card Then we've got any Machado Nine out of 48. I'm gonna go back Honestly, uh, uh, Gush here. That's old school and new school dinner number two coming I'll fight John Henry Vaughan That's funny man Yeah, it's uh, put them right next to each other. That's a family photo if I've ever seen one People are gonna go in and be like is that a booklet?  That would be a really cool book There we go right next to each other the Red Sox Got Shoei to 299 and Clayton Kershaw to 150. Yeah, now we gotta pull the Ted Williams cut out of this case Busser Posey, Trevor Story, Randy Johnson Yeah, another Buster Posey. That's gonna be, uh, nine out of 36 Stat, uh, Stat Buster And we've got Adola's Garcia going to the ranger 66 out of 99. Nice one there Congrats, Texas. I like Adola's Garcia He does. He kind of got uh He should have been in contention for that rookie of the year. I think he finished third. Did he finish third? Yeah Third or fourth? He was definitely talked about an update. Oh, yeah, Aaron Judge to uh, 259 and satchel page to 299 He was one of the voters like picks for the award. Really? One of the voting systems. I forget whether it was like a journal or something. I don't think I pulled a knob for us Mike Schmidt. This one's disgusting Going to the Braves. Look at the patch on this thing. Kyle Muller 11 out of 35 Four colors two shades of blue in there. Congrats Atlanta Of course, Sam's gonna let me rip one inner case and I'm gonna pull the knob. Stephen Al probably did And Austin Riley to 36 He hit a couple wood cards. Maybe that's what they meant. Yeah, I didn't pull a knob. I pulled uh I don't I don't think I pulled the wood yesterday. I think Forest pulled a bunch Yeah, Forest pulled a bunch that Muller was cool. Uh, Mookie Betts Nice one there, touch you uh, 259 and Mike Schmidt to 299 Tuba, Bregman, Maze We've got Walker Bueller 15 out of 27. Nice one there for the Dodgers Congrats LA and another John Carlos Stanton. That's gonna be 15 out of 27 for the inks All right last back of the break everybody. Good luck Let's see who could pull out of here redemption redemption on the back as well Boba Shep to 99 Peter Lanzo to 259 McGuire Salvi there's a wander rookie Pull you a hunter green wood card in the back 19 out of 36 that's Ozzy Albie. So be kind of sick I think it is We haven't seen one yet. Yeah Uh rookie autograph card amethyst parallel of 27 I think yeah Of hunter green. So we did pull Vaughn hunter green auto. There you go, buddy. Nice one there Hell yeah Vaughn We'll take that for sure. We'll take a hunter green. There you go tiktok nice hunter green right there amethyst That'll do it for the break guys do a quick recap here Sorry tiktoks shouldered you guys We really did honestly. We've got Ozzy Albie's braves That's uh, John Carlos Stanton Yanks, Austin Riley braves Buster Posey, Giants, Manny Machado Padres and uh, Nolan Aronato Cardinals Nasty Cody Bellinger for the Dodgers uh, Johan Moncada for the White Sox, Alex Kierlov Twins, Josh Donaldton Yankees, Cody Bellinger Dodgers, Rhys Hoskins, um, Phillies Justin Berlander Astros, Bryce Harper Phillies Triple Red Sox John Carlos Stanton for the Yankees Mike Trout Angels, Willi Adonis Brukruh Redemption Hunter Green for the Reds. That's Walker Bueller Dodgers Kyle Muller Braves, Aguilas Garcia Rangers Nicoladolo Reds Brandon Lau, uh, Raze That's Andre Dawson Cubs Kyle Hendricks Cubs, Randy Rosarana Raze, Brian Mowcastle Orioles, Salvador Perez Royals Jose Berrios Blue Jays, Jose Berrios Blue Jays, Colton Welker Rockies, Joe Musgrove Padres, Cabrine Hayes, Pirates And then we had, uh, how about two? Shriples Relic Autos, uh, for the Red Sox we have the left is going to be Wade Boggs, Jim Rice, Carlton Fisk, one of nine And the right is Raphael Devers, Zander Bogarts, JD Martinez numbered 20 of 27 That will do it for the break guys. Thanks again for the fill. Next up we got another triple Threads half case


Hi, I'm Aarushi. I'm going to talk about this joint work with Arka Rai Choudhary, Matthew Green, Abhishek Jain and Gabriel Kapturk on Secure Multi-Party Computation with Dynamic Participants. To begin with, MPC is an interactive protocol that allows a group of mutually distrusting parties to compute on their private inputs. And the security guaranteed by an MPC protocol is that an adversary who corrupts a subset of the parties should not be able to learn anything beyond just the output of the function that the parties were computing. MPC was introduced in the 80s and since then there has been extensive research in trying to bring MPC closer to practice. And as the efficiency of MPC increases, the hope is that it can be used to compute large complex functionalities such as training machine learning algorithms or simulating large RAM programs on massive distributed datasets. However, since these are massive functionalities, irrespective of how efficient the MPC protocol is, computing on them could take up to several hours or even days. The problem with most existing literature on MPC is that it considers static participants. And what that means is that the participating parties are fixed at the beginning of the protocol. In such protocols, if the computation is long drawn, some of the parties might leave or drop out in the middle of the computation. This could be because they have some other commitment or maybe because they ran out of resources. In such cases, the remaining parties usually have to simply abort the computation and all of the work done so far goes to waste. Indeed, requiring all of the parties to stay online throughout the entire computation is an unrealistic expectation. Therefore, the main question that we address in this work is whether the static nature of MPC protocols is really inherent or if there is a way to design protocols that allow dynamic participants. To elaborate on what I mean by dynamic participants, let's consider a group of parties that begin executing an MPC protocol. Now, after some time, let's say two parties need to leave, but at the same time, another party is willing to join the computation. What we want is that this should not disrupt the computation and instead this previous group of parties should be able to securely share the computation done by them with the new group such that they can use this group to continue the rest of the computation without having to redo the work done by the previous group. And the protocol can proceed in a similar way with parties leaving and joining Instavish without causing any disruptions. This approach will clearly reduce the burden of computation on individual parties. Parties that have low computational resources, for example the blue party here, can participate for a small amount of time and parties that have enough dedicated resources can continue to participate for a longer time, for example the yellow party here. Such a protocol would result in a weighted privacy preserving distributed computing system which can also be used as a paid MPC as a service framework where the clients can pay to delegate computational tasks and anyone irrespective of their time availability or computing resources can volunteer to participate and get paid accordingly. Notions related to dynamic participants have been considered in some prior works. For instance this notion of player replaceability where the parties are replaced after every round has been studied by Mikali and Chen in the context of Byzantine agreement. This notion of player replaceability was also used in the design of Algorand by Gillard et al. This idea in Algorand was used to keep the identity of the parties hidden until they speak and this notion of player replaceability helps prevent targeted attacks on chosen participants after their identity is revealed. While the idea of dynamic participants is relatively new, the notion of dynamism itself dates back to the 90s where Ostrovsky et al. introduced the notion of a mobile adversary that can keep changing its set of corrupted parties while the participants remain static. The main idea behind their modelling choice was to capture a slow moving adversary such as the spread of a computer virus. More recently Goyal et al and Benomoda et al have also studied secret sharing with dynamic participants. Their notion of dynamism is similar to ours but they only focus on secret sharing while we focus on a broader goal of designing MPC in this setting. Moving on to our contributions. Our contributions are twofold. Our first and main contribution is in formalising a model for MPC with dynamic participants. We refer to this model as fluid MPC and this name comes from the fact that it allows a smooth flow of information between the different groups of parties. We also design both semi-honest and maliciously secure protocols in this fluid MPC model. I will now talk about the fluid MPC model in more detail. So we model computation in the setting in the well-studied client-server model where the clients can delegate computational tasks to a set of volunteer servers and this computation proceeds in three main stages. The first stage is the input stage where the clients can give or share their inputs with the servers. Now given these inputs a set of dynamic servers participate in the execution stage where the main computation is done. And finally during the output stage the servers share the output of the computation with the clients who can then reconstruct and learn the output. Since we assume that the clients are static, dynamism only shows up in the execution stage therefore I am only going to focus on the execution stage now. So the execution stage can be viewed as proceeding in discrete steps called epochs where each epoch could potentially consist of many rounds. Each epoch is further divided into two main sub-phases called the computation phase and the handoff phase and each epoch has a designated set of parties which we refer to as the assigned committee for that epoch. While in the handoff phase the parties within the assigned committee of an epoch interact with each other in the computation phase and then in the handoff phase they interact with the parties in the next committee to share information about the computation done by them so far. And this is basically how the computation proceeds. For our protocols we consider an honest majority of clients and an honest majority of servers in each committee but of course one could consider a dishonest majority setting as well. So based on the discussion so far it's clear that there are two main components in a fluid MPC protocol. The first is deciding how the committees for each epoch will be selected and then given these committees how the protocol in particular the execution phase of the protocol will proceed. I will now elaborate on the different properties required from both these components. So the two main properties required from our protocol execution phase of our protocol are division of work and fluidity. Let me explain each of them in more detail. So the first main requirement that is division of work essentially means that each committee should only be required to compute a small part of the circuit. And ideally this computation should be independent of the depth of the circuit. Otherwise if the committee is required to do a lot of work then that would defeat the whole purpose of dynamism in some sense. Our second requirement is that the protocol should have a high churn rate. In other words the commitment that each party needs to make in order to participate should be relatively small. And we measure this commitment in the number of rounds in an epoch. In fact ideally what we want is that a protocol should have maximum fluidity meaning that each party should only be required to communicate in one round. This can be achieved only if the computation phase is completely silent and no messages are exchanged during this phase. While the handoff phase should consist of a single round of unidirectional messages from the old committee to the committee of the next epoch. Designing such protocols where each committee is only required to send a single message is in my opinion both theoretically and practically interesting. Looking ahead we design our protocols keeping these two properties in mind. So while we view committee selection as an external process and assume that its outcome is an input to our main protocol. Nevertheless the properties of the selection process actually dictates the design of the remaining protocol. Therefore the main properties of the committee selection process that we want to consider here are how and when the committees are formed and when the adversary gets to corrupt parties in these committees. I will discuss each of these in more detail now and on the way also mention how this committee selection process with the desired properties can be instantiated using prior works. Starting with when the committees are formed. So one could consider a weaker variant where the committees are decided at the beginning of the protocol but that is clearly too restrictive. Therefore we consider an on the fly committee formation model where the committees for each epoch are known at the start of the handoff phase of the previous epoch. So for instance in this example the committee for the first epoch is decided during the input stage. And similarly the committee for the second epoch is determined at the beginning of the handoff phase of the first epoch and so on. Now the next question to consider is how are these committees decided. So again one could consider a completely volunteer based system where anyone is allowed to sign up at any time and anyone who signs up is included in the computation. But clearly this kind of system is prone to similar tax in which a single party pretends to be many parties and enforcing a strict corruption threshold in each committee in the setting would be difficult. The other more realistic option is one that's based on an election mechanism. This is where every party who wants to participate can nominate itself and an election process decides which of these nominated parties actually get to participate. This is clearly a more realistic model and in fact these recent works by Benomoda et al and Goyal et al implement such an election process that enforces a corruption threshold in each committee using proof of stake blockchains. As I mentioned earlier one could choose which of these they want to consider depending on the need from the perspective of our main protocol. We came these choices separate from the main protocol and as long as the next committee is determined at the beginning of the handoff phase that's all we require. So the next question is about committee corruption. Here again one could consider static corruptions but we consider a stronger adaptive corruption model where the adversary is allowed to corrupt parties within a committee throughout its activity period. So for instance here it could corrupt a party in a given committee during the handoff phase or anytime during the computation phase or during the next handoff phase. We also need to account for the effect that corrupting a server has on the prior epochs where it participated. For instance here if the adversary corrupts this yellow party at some later epoch then it inevitably learns its private state in the previous epoch. Therefore if there is an overlap we assume that a server can only be corrupted if it doesn't violate the corruption threshold of the prior epochs. Now let me move on to the actual protocols that we design in this setting. So assuming that we have a committee selection process that satisfies all of the properties that I mentioned on the previous slides. We observe that an optimized version of the classical BGW protocol by Genero et al. can actually be naturally adapted to the fluid MPC setting. And in fact this protocol achieves maximal fluidity. I'm going to give a quick recap of this optimized semi-alist BGW protocol first. So this protocol evaluates the circuit in a gate by gate manual on secret shared inputs. In more detail the parties start by secret sharing their inputs using a threshold secret sharing scheme. Then for the addition gates the parties simply locally add their shares and for multiplication gates they first locally multiply their shares then reshare these locally evaluated shares using a lower degree polynomial. Exchange these shares of shares with all of the parties and finally reconstruct the relevant shares for the outgoing wire of this multiplication gate. For the final output gate the parties reveal their local shares for the output wires and then reconstruct the output. Our main observation here is that this protocol is quite amenable to the fluid MPC setting. In particular consider an input phase where the clients secret share their inputs with the first committee. Now the execution stage proceeds in different layers. In particular committee I is responsible for computing or evaluating layer I of the circuit. More specifically after the input phase the parties in the first committee locally compute on their respective shares depending on the gate in the layer. They then compute shares of these locally evaluated shares for both the addition gates and the multiplication gates. They then exchange these shares of shares in the handoff phase with the next committee. And now the next committee starts by first extracting the relevant shares from these shares of shares received from the previous committee in the handoff phase and then compute on them to evaluate the next layer and so on. Finally for the output phase the last committee simply sends the shares of the output wires to the clients who can then reconstruct the output. Note that here in the computation phase we do not require the parties to communicate at all. Moreover the handoff phase is also only one round long. Also the committee is here each committee here is only doing work proportional to the width of the circuit and is independent of the depth. Therefore it's easy to see that this protocol satisfies both division of work and maximal fluidity. Next for our maliciously secure protocol we present a compiler that transforms certain semi honest protocols including the fluid BGW protocol that I just mentioned into a maliciously secure protocol. And this resulting maliciously secure protocol achieves security with a part and has the same level of fluidity as the underlying semi honest protocol. We also provide an implementation of our maliciously secure protocol based on semi honest fluid BGW. I will now discuss this compiler in more. We start by examining the approach used in modern efficient NPC protocols and we notice that most of these protocols rely on an observation made by Genkin et al. who showed that most secret sharing based semi honest protocols are actually secure against malicious adversaries up to additive attacks. Meaning that the attack strategy of a malicious adversary in these protocols is restricted to just injecting arbitrary additive errors on intermediate wire values. And these additive errors are actually independent of the actual wire values. Most recent efficient NPC protocols exploit this idea by running two parallel executions of such semi honest protocols. One of the executions is on the actual inputs and the other one is on randomized inputs as shown on the slide. At the end of the protocol before the outputs are revealed to the parties, a correctness check is performed by comparing a random linear combination of the intermediate values in the two executions. What we now want to explore is whether we can use the similar strategy in the fluid NPC setting as well to get a maliciously secure protocol by transforming fluid BGW. And we observe that this paradigm does indeed extend in a natural way to the fluid NPC setting. And in fact, most secret sharing based semi honest fluid NPC protocols are likely to be secured against malicious adversaries up to additive attacks. Now let us try to see if known techniques in this paradigm can work in the fluid NPC setting as it is. So the first case that we consider is if the linear combination is computed at the very end. But in this case, all of the intermediate wire values will have to be passed along across all of the committees until the very end. And therefore we won't be able to get division of work. On the other hand, if we try to compute the linear combination in an incremental way, that is by combining all of the values of a given layer and only passing along this partially computed value, then we would have to find a way to generate these alpha values that are used in the linear combination on the fly. And generating these alpha values could take more than one rounds, which could hamper maximum fluidity. We resolve this problem using a simple idea. Let's say this is the circuit that we want to compute. Now at the time of secret sharing their inputs with the first committee, we require the clients to also secret share random values, beta and alpha one to alpha w where w is the width of the circuit. Now when the first committee computes the first layer in the dual executions, they also additionally multiply beta with itself and with each of the alpha values. Similarly, the next committee will additionally multiply beta with all of the previously computed random values. These values will then be used to compute the linear combination in an incremental manner. In particular, the first committee simply sets the partial linear combination to zero since no values have been computed so far. The next committee will compute this partial linear combination by multiplying alpha one beta with the first value, alpha two beta with the second value and so on and add these to the previously computed partial linear combination. And similarly, the parties will compute another linear combination using the same alpha beta values and the values induced on the circuit from the other parallel execution that is run on randomized inputs. Finally, the clients can compare the two linear combinations before reconstructing the actual R. Note that each of these additional computations are done in parallel with the dual executions and hence if the underlying semi honest MPC has maximum fluidity, so will the resulting maliciously secured protocol. Moreover, the parties in the solution still only do work that is proportional to the width of the circuit and doesn't depend on the depth and hence this protocol also supports division of work. Finally, to summarize, we present the first formal model for MPC with dynamic participants. We also present constructions for semi honest and maliciously secured protocols in this model and implement our maliciously secured protocol. However, these are only baseline solutions and there are many interesting open problems in this area. Thank you.


okay guys so an object of size 7 cm is placed as 27 cm in front of a concave mirror of focal length 18 so focal length of a con the cave the mirror is negative clear shot shot the object is 7 cm in height and 27 cm is the distance we know that object distance is always taken as negative clear at what distance from the mirror should a screen be placed so that a sharp focused image can be obtained find the size and the nature of the image so


You need a financial advisor with the freedom to focus on your specific needs. Whatever your goals, Reid Potter can create a game plan tailored to you. Call Reid at 432-0777 at Pikeville, Kentucky to learn more. Trigger treaters will be filling the streets of Pikeville on Halloween night and Pikeville Police Department has some safety tips for both children and parents. Simple tips such as checking candy and driving slowly can make a big difference. Out in top news, spoke with Pikeville PD Captain Russell Blankenship for more details. First off, before you even leave, make sure the costumes fit right. They're not too long. Garments aren't maybe dragging under their feet so they don't trip and fall. If possible, try to use face paint instead of a mask. That way, you know, they can see better. If they are going to use a mask, if you need to, make sure the holes are big enough for their eyes to see. And parents, when you're out and about, make sure you're driving more cautiously that night. Slow down, turn your headlights on early, make sure you can see the kids. And if you want to on their costumes, you can put reflective tape or stickers and make sure they're visible. As always, inspect the candy when they get home.  Look for any sharp instruments like razor blades, maybe possibly a needle. Sometimes some of these new drugs can look like candies, so just try to inspect and make sure it's in the original wrapping. GED officers will also be on foot patrolling during trick-or-treat hours as an extra precautionary measure. If a child gets lost, an officer can assist them back to their parents. Before you go out, make sure you talk with your kids on how to dial 911 or also what to look for. We're going to have a lot of officers out there tonight. We're going to satrate the streets on foot patrol, extra vehicles driving around the area. So make sure they know to look for one of us. They can come to us and we'll make sure we find them, their parents. If their parents want to, they can put their name, phone number, maybe put it on a piece of paper and put it in their pocket. So if we find them, they can't find their parents. Maybe we can check there and we can try to call them. We always try to have extras out on patrol that night as many as possible because the streets get really busy. We even hand out candy here at the station, our clerk always takes care of that. But we've always got several on foot patrol in Cedar Creek, Bowls Edition, things like that. Reporting for Mountain Top News, I'm Nick Colum.


The Nasser al-State police command says it has arrested a suspected notorious kidnapper, Shraib al-Muhammad, also known as Chiyawa, who had been involved in several kidnapping cases in the state. The state's public police relations officer, DSP Rahman Nansal, made the disclosure at the command's headquarters in Lafayette, on Thursday, while parading 23 other suspects who were arrested for various crimes across the local government areas of the state. He commanded the police officers charged to the anti-kidnapping unit of the command, led by SP Lapshak Lenka, for walking tirelessly to arrest the suspected kidnapped kingpin. Yesterday, 19th of April, at about 17.07 hours, based on the tip of police operatives of the command's anti-kidnapping unit, arrested a kidnapped kingpin named Shraib al-Muhammad, also known as Chiyawa. Investigation has shown that Shraib al-Muhammad is the gun leader of a notorious kidnapping syndicate, terrorizing Deadly, Maraba al-Kunzalafia, and the suspect has been on the wanted list of the police command for various cases of kidnapping and has been invading arrests before Nemesis cut off with him.