Okay, so today I will be, I'm from Sonomitsu, by the way, we're a Japanese fintech startup, Japanese in Swiss. I'm based in Berlin, Germany. We're distributed all around the world. And we designed a system called Bakong, which is a blockchain-based national payment infrastructure run by the National Bank of Cambodia. And it was actually the first blockchain-based national central bank operated payment system launched worldwide. It's been running with real money since 2019. And it has been running successfully with no crashes, no security issues. So we're quite pleased about that. And today I'll discuss, well, first I'll introduce Sonomitsu, then I'll discuss distributed ledger technology in the future of central bank money and then go into the system. So why Bakong in Cambodia and why hyper ledger of Iroha as a basis for Bakong? Then I'll talk quickly about incentivizing private sector cooperation within the Cambodian payments ecosystem and then give you a preview of some of the next steps that we hope to take as a company and also some of the National Bank of Cambodia's next steps. So Sonomitsu was founded in 2016. We currently have around 100 people who are growing every day and offices in five countries. We contributed hyper ledger Iroha along with a few other Japanese companies to the hyper ledger project in 2016. That was our first major project and we actively maintain Iroha. In fact, currently we are in the final process of refining and testing Iroha version two, 2.0 I know which our CEO Makoto Takamiya actually gave a talk about in yesterday's session. So maybe some of you caught that talk. If not, then the presentation should be available. I'd encourage you to take a look because it's a real step forward from Iroha V1. And I will talk about a few of the features of V2 at the end of today's talk, but there's a lot to learn. So our best known project is the payment system that I'll talk about today, which we implemented for the National Bank of Cambodia. We've also done work with the CSDs of Slovenia and Russia designing a tokenized CSD ledger. We run a crypto community, a crypto space called Sora. And we've also worked with a couple of different companies, private sector companies like the BCA group in Indonesia designing an identity management solution as well as a couple of Japanese firms like Hitachi and NTT, with whom we've done POCs and a university in Japan for whom we designed a private currency, a closed loop payment system. And then finally, we work with the Web3 Foundation a lot. We're creating the C++ implementation of the Polkadot runtime environment. And we've done a few other projects with Web3. So that's us. And we're turning five this year. And in five years, we've designed quite a few exciting technologies. And we closed 2020 actually by winning a FinTech and RegTech Global Award and Open 2020 with a Japan Financial Innovation Award. So we're quite happy about that. It sets a good tone going into 2021. And with the second version of Iroha coming up, we expect a really good year. So please stay in touch and join us in seeing what the next five years will bring. So Christine Lagarde says that public authorities must balance the benefits and risks of innovation in payments and be prepared to take a leading role in ensuring that payments remain efficient, safe, and inclusive in the digital age. And Fabio Panetta puts it a little more dramatically, saying that the impending revolution in payments requires us to stand ready to reinvent sovereign money. So what would drive these normally quite reserved and prudent central bankers to make such dramatic statements? Well, the payments ecosystem worldwide is changing. As we see payment, this is a McKinsey Global Payments Report from 2020, which indicates that payments companies outperform all other banking sectors in value creation. And the rate of which they do so has risen dramatically since around 2016 when we were founded actually. Fast payment systems are becoming more widespread worldwide. Currently, I think it's something like 50 jurisdictions have fast payment systems, fast retail payment systems in operation, and the number is increasing yearly, including in less developed countries where we would not previously have expected to find such systems in operation. And finally, central bank digital currency projects have really skyrocketed as well over the past four or five years, I believe, in 2017, something like 30 or 40 central banks were running experiments with CBDCs. Now it's up to something like 84% of central banks that responded to the BIS's most recent survey are doing some kind of work with central bank digital currencies. And a couple of jurisdictions have actually launched projects. The Bahamas is probably the best known jurisdiction. The central bank of the Eastern Caribbean currency union is launching a CBDC and the National Bank of Cambodia's Bakon system is not technically classified as a CBDC for legal and regulatory reasons which I will get into later. But on a technical level, it does many of the things that a CBDC will also do. So yeah, we can see that in 2017, around 66% of central banks were engaged in some kind of work with CBDC. Now the level is up past 85%. And also the proportion of central banks that are exploring general purpose as opposed to wholesale CBDCs has risen. So a general purpose CBDC is a retail digital currency that is available to everyday users, not just financial institutions. So why Bakon? The kingdom of Cambodia four years ago would not have come to mind if someone was discussing the jurisdictions with innovative financial infrastructure, forward thinking, financial monetary system planning. But lo and behold, they really kind of stole a move on the usual suspects and began a working group to explore CBDCs in 2016 which was quite early. And we should remember that prior to 2018, there wasn't even really a definition of what a CBDC was. So to begin thinking about this in 2016, they had quite a bit of foresight. They started conceptualizing use cases in 2017 and chose Hyperledger Iroha as a basis for a retail CBDC, which is again a digital currency that's available to everyday users, not just financial institutions. And we very quickly developed a minimum viable product and evaluated it. By 2019, we were ready to integrate the system and proceed with a soft launch with four participating financial institutions and their end customers using real fiat-backed digital Cambodian retail, which is the local currency and US dollars. In Q3 2019, we soft launched nationwide. In 2020 Q2, we published our white paper, which I'll provide a link to at the end of this presentation. And our nationwide launch went well. We received an average of four star app reviews for iOS and Android apps. And this led us to deciding in Q3 to launch nationwide formally. And we were literally three or four days behind the Bahamas sand dollar launch. So we didn't get as much press as we had hoped. But nevertheless, it was a successful launch. And the system has been running since then with 5.6 million indirect users who are users who use Bakong via member banks and 60,000 users who use the system via, sorry, via the Bakong wallet app that sort of means it developed. So there's also been a notable increase in cross-institutional transactions. And this was one of the major motivations for launching the system in the first place to make cross-institutional transactions easier. So the Bakong architecture is the burden is shared between the central bank and commercial financial institutions. The central bank runs the core ledger. It's responsible for creating money and it's responsible for creating domains and accounts whereas commercial financial institutions maintain Bakong settlement accounts that are backed by their central bank reserve accounts. They also run payment gateways which are mobile API servers. And they're responsible for onboarding end users conducting KYC, controlling end user personal identifiable information and integrating with the core banking system via ISO 2022. And I don't really have time unfortunately to go into the technical details of the architecture but a lot of this is available in our white papers and other literature which I would be happy to send you a link to. So why Project Bakong in the Kingdom of Cambodia? Well, the first motivation was that in 2017 Cambodia suffered from very low financial inclusion. Only 22% of adults had accounts at all. I believe only 15 or 16% of adults had financial institution accounts and only 16% had made digital payments. And this rate was even higher sorry even lower in rural areas among women, among the poor, among the young and the elderly and all of the other groups that normally suffer from poor financial inclusion. There's also a very large informal sector including many underbanked or unbanked MSMEs. And that's a problem both for MSMEs and for the Cambodian government. Obviously it's difficult to collect taxes but it's also difficult for these MSMEs to keep on top of trends in commerce. So for instance when tourists come to Phnom Penh and want to use a digital payment app with local merchants they can't so they turn to multinationals instead which cuts into the local business models. So offering these MSMEs and also everyday citizens some form of accessible digital payment the national bank decided would provide a public good. The payment infrastructure, the payment ecosystem in Cambodia was also quite fragmented. There was a good settlement infrastructure for banks. There's a fast retail payment system called FAST and also a CSD. But these were not accessible to payment service providers or microfinance providers. Because of regulatory issues a payment service provider that was not registered as a bank did not have access to the settlement infrastructure that banks had access to which led to a proliferation of isolated closed loop systems whose users could not interact with each other could not transact with each other unless the companies reached some kind of bilateral arrangement which was extraordinarily efficient for the companies themselves and also quite inconvenient for retail consumers, retail users. And there was also a lack of incentive for private sector innovation because it's a poor country and because banks did not see immediate potential for profit offering a wider range of financial instruments and services. There was not a lot of growth in the kind of services that financial institutions were offering or developing including online banking offers. The online banking offers that were on hand in 2017 in Cambodia were pretty rudimentary. Other contextual factors were dollarization and a high mobile broadband penetration but a low mobile money penetration in 2017. So the NBC saw this, they saw that a lot of Cambodians relatively had access to mobile broadband but that mobile money had not yet made a move into Cambodia to the same extent that it had in, for example, East Africa. And they saw this as a real opportunity to launch a system that could change Cambodian's lives for the better. So why Iroha? Number one, Iroha offers final irrevocable and secure transactions. It's a focused and circumscribed digital distributed ledger technology with Byzantine fault tolerant consensus. It doesn't try to be a database. It doesn't try to be enterprise management solution. It's a blockchain. Its logic is be a blockchain and that allows it to minimize attack factors to reduce the potential attack space which is important when you're talking about creating a new system critical infrastructure. Number two, it's modular. It's open source via the Hyperledger project. There are SDKs available in multiple languages. And the NBC, the National Bank of Cambodia decided that this would be a benefit for them because they wouldn't be locked in to working with a particular company necessarily. Although they have been working with us regularly and we have a good relationship. They didn't want to suffer from lock in on critical financial infrastructure. It's very user friendly. It has a simple command line interface which looks like this. And this is the basic version. Gives you a menu of transaction types that you can choose from. I encourage you to check out our GitHub and go through the quick guide and try setting up a Hyperledger at Ova node on your personal computer. It's very easy to do. It's also mobile first. It has a functional and customizable end user app that we developed for the National Bank of Cambodia. And here also you can test out the end user app. I was gonna do that, but I don't think I have time. So I'll just show you a picture instead, a mockup. It's very easy to use. I'm sure that you've used something similar. You can send money to a registered user via a QR code scan, via inputting their phone number or account number. You can also display a QR code that others can scan and send to. You can deposit money to existing bank accounts, either your own bank account or another person's bank account. And the QR functionality is particularly useful for micro, small and medium enterprises, medium-sized enterprises, because it doesn't require any special infrastructure. You don't need a card reader. You don't even need a landline. You can instantly accept and bank payments from any other back home user without investing, without sinking capital into these payment service provider-specific infrastructures that you may or may not actually end up using. So it's a very easy way to take a step into the world of digital payments for MSMEs that don't have a lot of capital. It's also fast. Iroha is quite computationally efficient. It's scalable. And it has a print transaction time of around 2.5 seconds and a throughput of around 2,000 transactions per second. And we're always working to improve those numbers. Although for Cambodia, this is sufficient to cover the transactional needs of the population, which is around 17 million people. We don't have 17 million users yet. We have around 5 million indirect users via our bank partners. But in theory, everybody in the country could use the system and it wouldn't endanger the functionality of the system. And finally, it's context-appropriate. It has a roles-based permission system, which is uniquely suited to a multi-stakeholder environment, which allows clear roles for the central bank and for commercial FIs. It also allows a segregation of data for a balance of compliance versus privacy. And I wanted to show you quickly the desktop interface. This is the interface that a financial institution would see. And as you see over here, there's a menu of different kinds of operations. Right now I'm logged in as an admin or a manager. I could also log in as a teller and then I would have a reduced menu of options. And this is easy to implement on the front end because on the back end, Iroha uses a roles-based permission system. You create a domain, within that domain you create a number of different roles and then you assign permissions to each role. So it's very well suited on a backend level on an architectural data structure level to this kind of use case. And I was mentioning KYC. And for instance, here you see the KYC status. Backong has a tiered KYC system. So you can open an account with a Cambodian cell phone number without going through any KYC, but it has a limit, a limited transaction of I believe 250 US dollars per day. I could be wrong, I'd have to go back and check that, but that's also available in our white papers, which was, which the limit was set in order to comply with local and international AMLCFT. In order to raise that limit, you have to undergo a KYC procedure. The first level would be a virtual KYC procedure where you take a selfie video and then you scan your government ID into your smartphone. It compares the two and then verifies you with your host bank. The second level you have to go into a bank physically and conduct KYC with a teller. And the benefit of this is that it allows banks to continue to use their normal KYC business processes that they use for core banking. And another benefit is that it allows the National Bank of Cambodia to maintain access to all transaction records without maintaining access to individual users personally identifiable information. So for instance, on a central bank level, you can check transactions by inputting a hash like this. And it'll tell you the transaction info. So here we have the transaction hash, the creator ID is the sender, admin at test, the creation time, the command and the assets transferred from the sender account, admin at test, the recipient account, which is in this case, test at test, the asset ID and the description and the amount. So this is what the central bank would see. And these IDs are pseudonymized. They don't have any intrinsic connection to the user's actual identity. What the commercial bank would see on the other hand is something like this. They would see the account ID, the pseudonymous account ID, which in this case is right here that would correspond to this. But they would also see that user's KYC identity documents that they provided for KYC. So the central bank has access to all transaction records, but no PII. The commercial bank has access to only the transaction records of their own user base, but they also have access to the PII. So there's a segregation of transaction data and personally identifiable information that allows for a balance between regulatory compliance on the one hand and privacy on the other. And using established legal channels, the central bank could quite easily subpoena the PII of any accounts that were found to be engaging in the legal activities. So it's a really elegant and efficient way of maintaining that balance. And wow, time flies. So we've gone through some of the benefits of EROHA. The last thing I wanna talk about then is where does Bakong fit exactly in the CBDC space? And in 2018 when Bakong was first developed, CBDC was still a, there was no agreed upon definition other than it was a new form of sovereign money, a new form of M zero. Since then, there's been a lot of research done and this comes from the Bank of International Settlements Quarterly Review March 2020. It distinguishes between indirect, direct and hybrid CBDCs based on the two criteria of the legal claim. Who is the currency a claim on? Is it a claim on the central bank or is it a claim on an intermediary? And are the payments netted and deferred or are they real time gross payments? And our and boom who created this typology define an indirect CBDC as one in which the legal claim is mediated by intermediaries and payments are deferred. They define a direct CBDC as one in which the legal claim is direct on the central bank and the payments are conducted in real time. And Bakong kind of crosses the boundaries of these because the legal claim is indirect. The legal claim is mediated by users commercial financial institutions. As I mentioned before, each financial institution maintains a Bakong settlement account which is linked to their central bank reserve account. So the claim is mediated by the commercial bank but the payments are written in real time on the distributed ledger maintained by the central bank. And the benefit of this is that you achieve the advantage of final and irrevocable transactions with legal finality without the drawback of disintermediation. Because the risk of disintermediation here we have some barriers for private sector participation. The risk of disintermediation has been widely discussed. If the central bank begins to take retail deposits then that will mean that the deposits on the commercial bank's balance sheets drop. So that would give commercial banks less money to work with which would then in turn, in principle at least reduce their profitability cut into their business model. Within Bakong, there are these clearly defined roles for the central bank as the operator of the ledger and commercial banks as the maintainers of accounts. And in this way deposits remain on the commercial bank's balance sheet while still maintaining the security of having a central bank backing in the end. The accounting model also minimizes the need for regulatory reform because KYC remains with the commercial banks. It has a very low cost to adopt for private sector players. The client module is plug and play. The business processes APIs and GUI are carried over from or integrated with the core banking system. And it has minimal hardware or personnel requirements and a clear explanation of how costs can be recouped. And actually prior to implementing we calculated the savings, potential savings for commercial banks and our modeling indicated a potential savings of around $240,000 US dollars per bank per year which is not a lot of money for a bank but nevertheless it helped to assuage the fears of banks that participating in the Bakong system would become a loss leader. So as of 2021, we are happy to say that we have the majority of Cambodian banks on board including some of the major mobile money operators like Wing. Wing is the big one. I think that they cover, I forget exactly 90% of mobile money transactions in Cambodia or something. They have a huge network of over-the-counter agents and Bakong allows users of commercial banks to take advantage of the PSP's huge networks of over-the-counter agents. So it has made life a lot more convenient for Cambodians and for Cambodian small businesses. And it has also incentivized PSPs to develop more bank-like services, a wider range of services. And it has incentivized banks to develop a wider range of PSP-like services. So it's enriching competition within the Cambodian payments ecosystem or co-optition to use a buzzword. The Director General of the Cambodian National Bank states that in terms of us destroying the payment service providers, I think by creating interoperability, it shouldn't destroy them, it should actually be strengthening them. They should take it as an advantage. Interoperability shouldn't kill competition. Competition should use that and make it more meaningful. So yeah, five minutes reminder. Okay, so if anybody has any questions, please put them in the chat really quickly and I'll try to get to them. And if not, then feel free to email me at edwardsatsonamitsu.co.jp and I would be happy to field any questions by email as well. The presentation will be accessible online, by the way, right after this talk. Okay, great. Well, unfortunately we're out of time. I didn't get through everything I wanted to, time flies. But hopefully it was informative. Hopefully it gave you a good sense of what the system is and what it can do. And hopefully it set you up to be able to ask some questions personally. As I said, feel free to email me anytime and talk to you soon, hopefully. Bye-bye.


Hi, I'm Preciosa Deni. Joining this bootcamp has really been a good journey. I've learnt lots of Microsoft Power Platforms, I also use Powerhouse, Power Automation, and Powerbian. Also learnt about Power Virtual Agent soon now. I can say thank you and I'm really glad I'm part of this bootcamp. Thank you.


read them online when you need books from our home page search your one search form that books electronic then apply but if you have a trouble can't find the book articles and database as well to look all you have to do is search by type and find a database you feel is hype now ha t trust worth your time think you're feeling that research huh like the 2c slide if you still need help please click right here we got librarians on the spot to get you now ha t trust worth your time think you're feeling that research huh like the 2c slide if you still need help please click right here we got librarians on the spot to get you there


afternoon. So my name is Jun and this is my colleague, Hugh. We're both from the eBay. The team is called New Data Team, which is a response for developing and maintaining the digital data infrastructure in eBay. So today we'd like to present to you the new graph, which is a GraphDB services step-up on Genesgrab and FoundationDB. We'll just give you a very brief introduction about the GraphDB. So a graph consists of vertices and edges. On the right-hand side, on the right-hand side diagram, you can see the airport is actually the vertex. Connected between these, the airport is actually called route, which is the edge. And then you have the property distance attached to the edge, like route, and also the property attached to the name, which is the belong to the vertex airport. So the graph traversal or graph query is actually just start with a set of vertices, and then you're following the incoming outgoing edge and move to the next set of the vertex, and then you start the examination again. So then we also have called one hop query, which is a start with the one vertex, and then move to the connected vertex, the next immediate neighbor. And so this one hop, and similarly, you can have a two hop, three hop, and hop query. So in eBay, we have many applications that like to have GraphDB. And these applications include fraud detection, knowledge graph, IT infrastructure management, and product recommendation. So these GraphDB is required a real-time query, near-real-time update, page update, and also had a bug loading at the initial time when the GraphDB is being constructed. So most of these applications excluding the first initial loading phase actually exhibit the traffic pattern that's really heavy. So for the rest of the presentation, we will go over this new graph architecture and then the detail with the important feature that we developed for the FoundationDB storage parking. And then we also try to identify some feature and improvement that we like to have from FoundationDB, and finally the conclusion. So this is a 3D architecture of a new graph. You start with the graph application on the left-hand side, and then the application live with our new graph current library, which is developed by our team. And then the request will roll through the GRPC and end up to the new graph service tier. And then the request actually will be landed at the particular node. And the inside this node, the request is a go to the Janus Graph. And then it goes down to this FoundationDB storage parking. And it's this storage parking that translates the graph query into the FoundationDB specific key value store-based query. And then query then reach this FoundationDB backend store. And this store is a store both the data table and the index table for the GraphDB. And separately, we also have the management plan to manage the cluster and manage the schema for both the service tier and the FoundationDB cluster tier. So Janus Graph, it's inherently to support the transaction. However, it's up to the storage plugin to decide whether they're going to implement the transaction logic or not. So today, all of the storage plugin download that you can get from the Janus Graph public release do not have a transaction, a distributed transaction. So Berkeley DB is the one that supports transaction, but it's not horizontally scalable. But distributed transaction is the one that provided by FoundationDB is key to adjust the data inconsistency that we encounter when we develop this GraphDB. So I'm going to spend the next three slides to identify the key data inconsistency that we encounter and to see that. And to show you that the digital transaction is the way to tackle all this issue in a very straightforward way. So the first one is you have two vertices. You add an edge. This is a very simple GraphDB operation. And because the Graph query usually requires a forward traversal from the V1 to V2 on this diagram, and also it supports the backward traversal from V2 to the V1. So as a result, the edge information had to store in two presses. The first row belong to the vertex one. The second row belong to the vertex two. But because these two vertices are actually scarred, it's actually shard in different shards, and therefore this edge information update becomes a distributed closure update. In the traditional eventual consistent system, it supports now the first row, update, succeed, but not the second one. So as a result, the forward traversal query come from the V1 to V2, we succeed. But the V1, backward traversal to V1, we fail. So if you had the digital transaction that both updates of the row update actually belong to the single transaction, then either all of these updates succeed, and therefore both queries succeed, or both will not fail, and will not become visible to external world, and therefore both queries will show nothing. So that is still consistent. So the second one is a theory with many of these operations related to this graph DB. We have real-time query, near-real-time update, batch update. So all these go to a single database. With the digital transaction, all these queries and simultaneous count, and they all get the consistent result. And this is very different from the traditional lambda architecture. So if you follow the lambda architecture, it proposes that you have temporary DB to host this recent update, and you also have master DB, and you merge the data periodically from the temporary DB back to the master DB. Well, that's introduced at least two challenges. The first one is that, well, the query has to spend across two databases. One is the temporary DB, one is the master DB, and you have the merged data by the application. Well, therefore the compass query is very challenging. The second one is actually introduce a back-end capacity in terms of data management. Because now you have the temporary DB, a back-end DB, both serving the online traffic. In particular, all of these two can serve in the right traffic, and now how are you going to merge these two in a consistent way? Well, that's very challenging as well. So this slide shows you the failure handling of JanusGraph. Suppose you have the node, you're going to update the node to JanusGraph. So update the node as you introduce is required. Just JanusGraph will give you the new vertex ID for each new node creation. So there's a set of mutations. Each mutation corresponds to a key value pair update. And those key is derived from this vertex ID. Suppose now in this eventual consistent system, some update of some mutation fails, some mutations succeed. The mutations succeed while we persist to the back-end. And then you also saw the exception because some of these mutations fail. So now when this client receives the exception and make a second retry, and then this retry will lead to the new vertex ID, and this will lead to the new mutation set. Suppose now these mutations have succeeded, and therefore you have this duplicative mutation, in this case, m1 and m2, and 1 prime and m2 prime in this back-end database. And therefore you get potentially duplicative vertices. So this inherently, the problem that you have in general scope, if you do not have a distributed transaction back-end, well, if you have distributed transaction back-end, this failure handle is very simple. You just have a low back. And this low back will take care of this parcel update failure for you. So FoundationDB will choose it as a new back-end because of this distributed cross-strat transaction. And in addition, it has horizontal scalability, cross-region, high variability, low latency, key value store access, and also has intelligent safe management. So this diagram just shows you that how we deploy our cluster in the Kubernetes environment. We have three cluster, DC1, DC2, forms the active region, and then DC3 from the standby region. So our FoundationDB storage plugin is based on one that provided by Ted Wimis, who presented the GenScrub FoundationDB plugin presentation last year in this FoundationDB summit as well. So we take these, what he has, and then fix the bugs. And then we also add the new features, including AC iterator, read-only new graph services, and read-only query optimization across the data center, and among others. So here, Ness is going to present to you this important feature that we developed in the FoundationDB storage plugin. Hello. Hello. Yes, good. Yeah, Drew, we just introduced to you the new graph architecture and that we use FoundationDB as our storage back-end. In the next slide, I will introduce some important features of the FoundationDB storage plugin of GenScrub. So first of all, it is query-reson fetching using iterator. So as you know, FoundationDB can query the data using two more, either blocking or non-blocking. With blocking, all the results can be returned in one blocking call or non-blocking. We can use an async iterator to fetch the result one by one on demand. So the high-level GenScrub query executor relies heavily on iterators to point the data on demand. So it is very in line with the non-blocking mode of FoundationDB. So that's why we use async iterator in our GenScrub storage plugin. So here, just to give you an example, we can have a queries, for example, g.v.iterator to get all the vertices in the graph. So the GenScrub executor would first get the iterator, and then from the iterator, it can loop through each in a while loop to get the result and then processing it. So with blocking, all the data will be fetched in the first call, so that this is not good for our lookup service because it increased the memory usage and also the CPU in case the GenScrub executor terminates the iterator as soon as it miscomes some condition. So with non-blocking, the first call is actually return only the async iterator of FoundationDB, and while it fetching through the iterator one by one, it can get the result as needed. So this is a very good solution. It keeps our service low memory and CPU consumption. The second feature is request contact propagation. So a request come from the client can have some request contact that carries metadata such as request ID, client address, and application ID. So the service upon receiving a request can get the contacts and attach it to the threadlocker, and the FoundationDB storage plugin can get the request contact from the threadlocker and then can enforcing some condition at that layer to handle the request differently. So note that by this way, we bypass the GenScrub, so there is no code change at the GenScrub layer, and we can get the request contact at the storage plugin. So how is the contact useful? So with that context, first we can enable the new app service to run in read-only mode. In this mode, basically every write request from the client will be directed. So you may think it is a simple solution just enable read-only mode at the FDB database level. Unfortunately, it is impossible because the GenScrub underneath it requires some administrative write operations to the database. And if we enable read-only mode at the FDB, then on the write from this write from GenScrub will be directed too. So the solution is that we check the FoundationDB storage plugin for the request contact. It exists, meaning that these requests come from the client so that we don't allow it to go to FoundationDB cluster. Otherwise, those requests are from GenScrub, and we allow them to go to the FoundationDB. The second use case of request context is that we enable prefetching the transaction version. So remember that every FoundationDB transaction need to get the transaction version at the primary DC. This is good. It provides strong consistency. However, it also costs the request to incur high latency because especially when the read comes from the secondary DC, since it has a cross DC drive trip just to get the transaction version. So we come up with an optimization that we can allow the client to optionally hint that the request is a type read. And then in this case, the client can prefer low latency rather than strong consistency. So the client can annotate the request with type read, and then the service will put this into the do-cast context. And at the FoundationDB storage plugin, it can get the annotation type reads. And then instead of going courtesy to get the transaction version, it gets the transaction version locally prefetched by a different background thread that are running the background. So with this solution, we can have a low latency and a higher throughput, especially in our use case, most of the workload are very read heavy. So with the example, we come up with a real wrap example and run some numbers. This is an account linking wrap in eBay, and we have multiple accounts that can be linked together with different linking strategies. So in this example, you can see that account one can be linked with account two, three, four via the linking strategy one, or account one can be linked to account seven via the linking strategy three. So there are two types of vertices here, account and linking strategy, and one type of edge which is linking. Note that after maybe multiple hope traversal, like a six or seven in this case, all the accounts are linked together. So in our deployment, as June said, we have a 3D C2 region deployment, and the total number of ports are nearly 290 ports, so this is very large. The database consists of 1.3 billion edge and 1.8 billion edges, and the triple mode is, we put the storage in triple mode, meaning that there are three copies of each data at each data center, and that results in 16.8 terabyte storage across on 3D C. So there are three types of query that we experiment, one hop, two hop, and three hops. The major query in our application is three hop traversal. Note that in this three hop, we limit the query to return only 50 reason to provide consistency, because there may be some super node that has a lot of vertices that satisfy the condition. So without the performance, from the primary DC and from both DC simultaneously. So here I only focus on the three hop traversal. So up to two DC, we can get to 15,000 query per second, and with that we can get to 95 latency of less than 15 milliseconds. So we are quite satisfied with this result. Note that we haven't put foundation to the limit in this case because we only have a 20 service node, and if we increase the number of threads, the service CPU would be exhausted. So next, we will continue to talk about some features that we want to have. So overall, the foundation is great to power our GraphDB backend, but we'd like to have some feature improvement or some features. So the first one is actually that five second transaction limit, right? So maybe it could be extended to 30 seconds or one minute. Well, the reason why is because some of the query, in particular the multi hop query, that also has a complex pattern matching, and also have the children node that can spend thousands of children nodes. So in that case, we're often that we get the transaction 2.0. So by having this longer transaction limit, then actually we can support a much more complex query. So the second one is actually we'd like to have a better storage management. So this happened, we found this problem when we do the one week long residency testing. We add in the storage node, we delete the storage node, and keep continuing doing that.  And some of them even go to 90% full. So this has introduced a storage imbalance as well. And then so we actually report into the forum. So this system that we have developed so far is actually OLTP oriented. So that's with two reasons, active and standby to support this OLTP transaction. But then we'd like if we want to have a graph analytics and there's a workload that requires the batch retrieval over the entire database sometimes, then that we need to have another third reason just to host this graph analytics workload. So finally I touch up this bug loading. So for the example data set that Hugh Mason actually took us more than two days to load that whole data set into our cluster. So now the question is that for this initial data loading, is that the way that we can bypass the normal transaction path? So as a conclusion, so we had to develop the graph DB service called new graph, which is based on the foundation DB and Janus graph. So foundation DB offered this distributed cost chart transaction. And this is a feature that key to adjust the data inconsistency issue that we encounter in graph DB. And also with this digital transaction, it greatly simplified the client-side application development. So with the last data set that we have, we found out we saw that foundation DB showed a high performance in terms of the high throughput and low latency. So with that, we conclude our presentation.


And now for your strong Europe spotlight. The US Army Europe Engineer Division completed the first piece of the European reassurance initiative in Tapa Estonia. With the assistance of the Estonia Defense Ministry and US Army Corps of Engineers, they completed numerous projects in the area. This project that you see over my shoulder, the railhead here at the Tapa Contowment area represents one of our best examples of collaboration amongst all the stakeholders as part of this European reassurance initiative. So this marks a collaboration Estonian Defense Forces from the US Army Europe staff. This is one of 27 projects throughout Europe that will support US alliances in Europe. From Tapa Estonia for US Army Europe Public Affairs, I'm Army Sergeant Danny Debehetz.


Is your PlayStation 5 freezing while you're in the middle of a game? Today we're going to be talking about how to fix your PlayStation 5 when it's freezing. Let's get right into this. First, if your PlayStation 5 did freeze, you're going to want to completely shut it down. To do this, hold the power button on your console until you hear two beeps.  The next thing you're going to want to do is clean your PlayStation 5. Unplug the power and HDMI cables from your PS5. Take off both covers from your PlayStation 5. It's real easy to do and it does not affect warranty because you're not opening up your console.  Now over time, dirt and dust can accumulate on your PlayStation 5 causing it to overheat and freeze. Use a microfiber cloth to clean and remove any dust around the vents and inside the covers that you did remove. Also, you're going to want to inspect the fan. If you see any dirt or dust inside, use a soft brush to remove it. Now by only removing the covers, you can clean out most of the dust that does accumulate for your PlayStation 5. However, if you want to go more in depth, you can open up your PlayStation 5. Keep in mind that will alter the warranty for you, but you can do that as well. And also, if you find that there is a bigger issue with your PlayStation 5, you can also replace the thermal paste. Most people with the freezing issue is because there is a lot of dirt and dust in their PlayStation 5. So hopefully, if by just cleaning it out, that will fix the issue for you. Next, if that didn't work, you will want to adjust your settings on your PlayStation 5. One common cause for the PlayStation 5 freezing is having too many application opens or too many games running in the background, which is something that I experienced personally. I didn't realize with the PlayStation 5, if you do switch games, the other games still run in the background until you close them completely. So make sure that you close everything when you're done with it before you launch the next game. The next thing you don't want to check is to make sure that your PlayStation 5 is updated. Sony will periodically release new updates to fix bugs and improve performance. To make sure that you have the latest updates, you're going to want to go into settings and select System Software Updates. From there, you can tell to see if there is an update that is ready to go. Most of the time, you can set it to automatically update next time you turn your PlayStation 5 on. But sometimes, there is ones that just get stuck there and you don't know there is an update available. And this could cause other issues with your PlayStation 5 or other features of the PlayStation 5 not to work properly. Now, hopefully one of these fixes did work for you. Adjusting your settings, closing applications that you're not using, making sure your PlayStation 5 is updated, thoroughly cleaning out your PlayStation 5, making sure there's no dirt or dust inside. And if you have to, replacing the thermal paste. For most people, one of those fixes will fix the issue with the freezing of the PlayStation 5 and even overheating issues. But if it didn't, there might be a hardware issue with your PlayStation 5. Hopefully, your PlayStation 5 is under warranty. If it is or even if it isn't, then you can contact Sony directly to get the next steps rolling. But for most people, one of these fixes usually work for you. Hope you guys enjoyed this video and hopefully you can get back to gaming with your PlayStation 5 no longer freezing. I'll see you guys in the next video. Please take care. Peace.


Have you ever had actor nightmares? Like you forget your lines or something like that? Anything. Yeah. I had the most vivid, all night long actor nightmares that the show I'm in was time to do the show and everything was changed. It was now no longer a four-person show, it was a full ensemble cast. There were things that my main character was having to do like ride a bicycle and do a full face plant into grass and get hair in your head without me ever having rehearsed it. I got so freaked out, I pooped in a van on the way to the show and I woke up screaming. Actor nightmares. Wow. Did you poop in your bed?  I'm Rick and you can follow us on Instagram, Twitter, Facebook, juicy content. Thank you for your support. Patreon, follow us on Twitter, account and subscribe, like button. And today we're doing a movie review. No, in this is not an Indian movie, per se. Per se, it is about Indians. With Indians. Yes, in it. In it, but Hollywood movie. Correct. Need that to be very specified. But you'll know why we're doing this for a million reasons. But we are reviewing the new 2024 directorial debut of Dev Patel. Correct. Monkeyman. Monkeyman, monkeyman, look out here, he comes. Monkeyman, monkeyman, he has poseable thumbs. Monkeyman, monkeyman, he's gonna get you now. Monkeyman, monkeyman, monkeyman, monkeyman, monkeyman. And that's the theme song for it. That's actually straight out of the opening credits. Yeah, yeah, yeah, yeah. We sent that to Dev Patel and he was like, this is better than anything I could have ever come up with. Yes, and he's asked us to score every film he ever does from now on. My wife is here. Being her lovely self. Okay. Yes, so we are doing a movie review of Monkeyman and this will be primarily non-spoiler. Yeah, we'll let you know when the spoils are coming. Yeah, because obviously it's not even out yet. We got invited, graciously, by Universal Pictures, to go watch the premiere in Los Angeles. And if every Indian Instagram influencer. If you wanna see, on both of our Instagrams, there's a lot of different things on there from when we were at the event last night. And that's what we got these last night. Yeah, a little small, but we got to meet some cool people. You can go check out on Instagram. But yeah, so I believe it comes out this weekend. It does. For you in America. It does not come out this weekend for you in India. But hopefully at some point, it will be released for you guys. Anyways, so Rick, your initial non-spoiler thoughts of... The Monkeyman. Monkeyman, sorry, not the Monkeyman. Monkeyman. So, I would have written a paragraph, but this time didn't a lot for that late night, last night, early start, so I will try to off at the top of my head give you my paragraph. While I was sitting in the theater watching the film, there was a point during the film where I thought, holy crap, kids, Dev Patel has something to say. I've always enjoyed Dev as an actor. I've really enjoyed everything I've seen him done. This made it really clear to me that the man is an artist who is very passionate. This is... Did you see his film last year? Which one? The Green... No, I did not see that. I did not see that, was it? Yeah. He clearly, this is a passion project for him if you know anything about it and it's obvious from what you see on the screen. This is what I was hoping Animal was gonna be. In a world where the most recent incarnation of the action genre at its peak is John Wick, this holds its own as its own action film with really wonderful fight choreography that bespeaks the title with an animalism that is really off the charts. The cinematography is spectacular and ultimately for me the biggest take away from this was he has an amazing story to tell that is very personal, it's pretty profound and you probably won't see it in India. You won't see it the way he intended to.  And I wanted to tell him this last night but he was too busy and he left early. I know you need to make the money on the film and it's a huge market. At the same time, don't change your film. That's what I have to say. But you hated it. I loved it. Oh okay, sorry. I loved it, it met my expectations and my expectations were really high. Yeah, obviously we reacted to the trailer and we were really looking forward to it. And we saw in the trailer, but then we forgot because she showed up right in front of us that Sorbita was in along with many other. Yeah, we'll save that for the spoilers because there's some nifty little surprises. Some great surprises. That we'll talk about in the spoilers. That is absolutely wonderful. But yeah, the film was really, really nice. I really, really enjoyed it. And I think they, I don't know if it was an inspiration or after they made it, they're like, people are gonna make this comparison to John Wick. It's not a story like John Wick. Not in terms of like an assassin and stuff like that. Action style, it is. Much less headshots. Yeah, it's definitely, you have to compare it because right now John Wick is the bar of action standards in Hollywood. But in terms of the action that it brings and the style of it, it's that. And it's with up a notch because I think it's more brutal sometimes. It is more brutal. With some of that. Because it's more personal. Which is when Rick said that's what we wanted from Animal, we're talking about the violence of it. And the story. Seeing the animalistic, it's nothing like the story of Animal. Well, there is some aspects of it that I think are comparable. But you know what I'm saying? Yeah. Yeah, so the action of it and the violence were absolutely fantastic. Fantastic, so satisfying. I thought Dev did a very good job outside of, I think what he struggles with. And you saw it in Slumdog too. He struggles to hide his British accent sometimes. Oh, I didn't see that last night. Yeah, he did in Slumdog too. Well, that's understandable. That was really, really early in his career. I've seen that a lot with British people. Yeah. If they have to do like if. For Scottish, yeah. If they have to hide their accent with an accent that's not just plain American. Right. They do that very well. Yeah. But like if they have to like do a Southern accent or a Boston or Indian accent, I'm guessing he had more of a, they said that he grew up in Guadrata, but then he was in Mumbai. Mm-hmm. I spoke very good English for, but there was occasional times, the only gripe that I have with his performance is that same thing in Slumdog. I saw, I've heard his British accent. Interesting. Multiple times. Yeah, I never picked up on them. But that's not just strictly just of Patel. Other than that, this is actually, whatever the one that came out last year was called the Green Night, the Green Night. Yeah. Fantastic film. Well, watch it please. Awesome. One of my absolute favorites of last year, actually. Much different film. But this film was a lot of fun, man. Oh, it was. There were points in this film where the action sequences were so satisfying in their brutality that the audience applauded. Yes. I then laughed. One of the other, if I was to have another gripe is that it was fairly standard in its format of an action film in terms of, this is where it's going, training one, like, you know what I'm talking about. Just the plot. Correct. Plot points. Obviously it's done differently in India. I don't think I've ever seen an action film in Hollywood that has full Indian culture and actors in the center of it like that, here in America. No. Haven't seen that. But in terms of the format of the action film, yes, it is fairly formulaic, but the action scenes are the peak. They are. But for me, like I said before, we'll talk some of the technicalities. Yeah, a lot more to say. We'll talk about technicalities. But the other thing that I'm really excited about, and I'm rooting for him about, because he said something really revealing, which doesn't surprise me. I think this guy wears his heart on his sleeve. He does in his cinema. It seems like it. He said it before the movie started. He talked about how personal this was for him. And part of it was he's always struggled his whole life to question, am I British enough? Am I Indian enough? And the thing I love about this film, besides from the artistic excellence, is the fact that Dev really is positioned, and I'm rooting so hard for this to do well this weekend, to really continue to do films and open up doors for the people that we've come to appreciate and love in Indian cinema, who really want to work here as well and don't have open doors. Guys, you'd be surprised how many legends and potential future legends in Indian cinema have a hard time breaking through here because of just not being known. And so the more things that can platform the greatness of artists, which there's many in this thing, I'm hoping that's one of the things that comes out of this film too. Yeah, another, in terms of the performances, Dev obviously is the main lead in this, but there's a bunch of supporting actors, and I'm so happy that he reached into India to get a lot of his supporting actors. I didn't recognize all of them, so I don't know if they were all from India or if he kind of handpicked some from Hollywood, some from, there's three we know. Four we know for sure that are very much in the Indian industry. Yeah, but Sorbita, you saw them in the trailer. You saw her in the trailer. She was there. No spoilers yet. We'll give you some spoilers in a second. If they were in the trailer. We got to speak to her for a little bit. We did, and bless her heart. Not interview-wise. No, we just got to talk to her at the after party and oh my goodness, I could tell she was doing her utmost best. I could tell she was pretty tired. She had just arrived and she's turning right back around to go back to India, so bless her. She was doing her utmost. She did a fantastic job. She's supporting. Yes, and spends a lot of the time just emanating her presence. And obviously, you know from Indian cinema, she has a great screen presence. Beautiful presence on screen. From what we've seen, PS1, PS2, in made in heaven. And what was the last thing we saw? I forget. And really got the chance, that was something I was happy we got to tell her was, one, we've appreciated her work, that anytime we see her in something, we're excited for it and really hope this opens up doors for her. The doors are already open for her in India, but she deserves to work in where she wants to. You also had a more substantial cameo in Vipin Sharma, who we also got to talk to at the after party. Lovely guy. Had a really good performance as always as he does. And Sikinder Kerr is obviously in the trailer. He was there, we just didn't get a chance to talk to him because one of the reasons we didn't get to talk to him or really talk to Dev was because the bar took too long. Yeah, the bar. Note to self universal. But yeah, he was great. And also I love the fact that this movie showcased so much of Indian culture that, obviously we are well accustomed to now in the 400 plus films that we've seen. But for people that have never outside of maybe RRR now that they've seen, because a lot of Americans have seen RRR. Yeah. You know, this is not an Indian film, we know that. But they get to see a lot of Indian culture that they've not seen before. Correct. And a little shout out here, we got to talk to him as well, to Charl-Toe Copley, who's the white actor in this. And we were really happy that he was good. We told him too. Well yeah, he's a SAG actor. Yeah, he's a SAG actor here. He was unaware of, huh? Is he Australian or English? I believe he's Australian. Yeah, he may be Australian, but he's a SAG actor here. Yeah. Well, he actually could be South African. He said in the movie he was South African. Oh, that's true, he could be. I mean, North African. But he was unfamiliar. He's not familiar with Indian cinema. He was not aware of, he only learned about some of these people as he started doing the film. But we told him, he said, yeah, it was really nice to watch. Usually we only get Mark Bennington. But Mark could have done that role. Yeah, he absolutely could have done it. There's so many Indian actors that I could have placed in this and I don't know how many he reached out to, how many he said yes, how many he said no. But it's wonderful that he got some really nice Indian actors. And they all did a great job. They did a great job. Spoilers? No, no. The score also I thought was absolutely fantastic. It wasn't, they blended it a lot. There was a lot of hip hop, a lot of Western music, but they've also, no spoilers, but they blended it also very well with a lot of Indian culture, Indian classical music influences. Another Indian rapper as well, I believe. I don't know who it was. Another huge shout out that is equally as impressive as Dev's directing and the cinematography that was done by Charone Mayer. The whole editing team that worked with Dev. The editing team. Yeah, it was nice. Oh my stars. Because whatever Dev was visualizing on the day with the cinematographer, then the editing process, just this movie is so, the storytelling is so dependent on the cinematography and editing and it's really uniform and it's really interesting how much I felt that Dev with his cinematographer, Charone, really understood how the dynamics of the cinematography and the editing are gonna contribute to the pacing of the storytelling. Hugely important with pacing, which we could get to in spoilers. So all those, it was a really, really fun film. Got what I wanted from the trailer in the movie. And then some great action film that showcases all of Indian cinema, which is stuff that, you know, when we were looking at like animal, well, there's why we talked about animal, even though that's a different story, but we wanted to see the animalistic nature of it and we've seen that a few times. With reality. With reality, yes. I think there's a new film coming up. I think teaser drops tomorrow, but it's called Kill. I think, to be in Santa Monica, we missed it. Sucks. But it's supposed to be a really great action film produced by Kieran Johar. But that's what I was expecting. Yeah, and I want this to do so well that I've already reached out to Alexis and I'm gonna reach out to Micah. I wanna go this weekend and give it some money and be a part of the box office for the weekend for Dev and everybody. Because I think it's that good and I'm really rooting for it. Yeah, so if you haven't seen it, please go watch it. Hopefully, I don't know when and if it will ever release in India, but if it does, please go watch it. It's absolutely fantastic. And if you're in the United States or anywhere else, please go see it.  It's for two reasons. Yes, the violence is brutal and so the censor board will probably want that to be cut up. But there are very bold, direct parallels that will, the terminology that you've heard over and over again is it's going to hurt sensitivities. And I don't know how you could ever edit this thing or change it to make it any different because like I said at the outset, Dev has something to say. Yeah, he does. So yeah, if you haven't watched it, please go watch it and then come back. Spoiler time, yeah? Yeah, I guess. Yeah? Yeah. Okay. I debate on it because I don't want anybody to. I know. I don't want people to watch it and then no. Well, at least some of the surprises in the film. We won't give away. When Shahrukh Khan showed up? The story, but you remember, for those of you who've been around a while. Dev did mention Shahrukh Khan. He did mention Shahrukh Khan. And somebody he loved and looked up to at the beginning. But if you'll recall, our very first interview on this channel was with Astaji Zakir Hussain and we asked him if he's ever done any acting before. We'll leave it at that. Let's just say there's a training montage. Yeah, that's what you fancy. That's one of the best training montages you'll ever want to see. Yeah. It's, I would love to talk to Dev because I would love to know, obviously I'm sure he wanted, Oh, I guarantee. to Indian people from Indian culture and that kind of stuff. I'm sure even if he's a non, like he was born in Great Britain, right? Yeah, he was born in England. But I'm assuming he still knew who Astaji was? Well, I promise that's who he thought of when he was writing the script. Yeah, he was like, if we can get who Astaji. The table of players got to be Astaji Zakir Hussain. Or if somebody, I don't know. It had to be. I would love to talk to him about like, I know.  Yeah, if anybody with, I know Dev's schedule is going to be nuts right now. But even if we have to wait and do it later at some point, really would love to talk to Dev. So if anybody who's part of universal production or even anybody we talked to last night can wing that around at his leisure, we would be happy if we got the chance to talk. But yeah, having all the influx of different parts of Indian culture that he incorporated into the film, making it also accessible to the Western audiences. Right.  Because I'm assuming he didn't want the entire thing to be. No. And in subtitles. And the subtitles were right. If somebody said Marachoud, it was subtitled Motherfucker. Which was nice. It was very nice. That was really nice. I felt the symbolism throughout of the roots against cinematography and editing the constant throwback to the imagery of the storybook of Hanuman. Particularly in the climax, that wall. That wall was very nice. That was so great. Which is, I believe, a painting of the, what is it called? The Ramayana. Which Andrani had some points we were talking in the car afterwards that only an Indian would pick up. You and I would not. And she, Well, of course, but that's the point. You'd be far more likely to pick up on it than any American would. Read a Bible. But the whole relationship between Hanuman and Ram and all that symbolism. I knew it. Yeah. You need to watch that anime. It's really good. Yeah. There's some, I kind of- I didn't watch along with Steph like a year ago. I feel like a lot of folks are coming in here who won't have seen the film and I'm trying not to give too many spoilers away. Yeah. I really don't want to. Since it's so early. I really don't. I don't want to give a lot away. It's bad enough that we told you about the Stajia Zakir who's saying, because that was a, we all three of us went forward in our chairs. We saw him and we went, Huyah! Yup. And he got up during the credits when his name came up because he was given special credit that said and a Stajia Zakir who's saying and the audience was, they knew. Yeah. How do you get that guy? But yeah, the action was so good and so brutal. Because in the beginning, the guy introduced it. He was like, it's a beautiful film. It's a brutal film. And whenever somebody says that, I'm like, okay, you better- You better be. You better live up to you saying that because I'm expecting- So good. Brutal. And it's- So good. I don't squirm easily, but man, there was some stuff that I was like, oh! So good. There were at least five things that happened to different fight sequences that made everybody howl, laugh, go, oh my! Wow! I kept grabbing both of your hands. Oh yeah. Yeah. Because I was in the front. Yup. We're right on the front row and she'd reach out and she'd grab us. It was, I'm excited. I wanna see it again and listen to the audience react to those moments. Yeah. Yeah, I think it, I hope it'll do well. But my biggest, the thing I talked about with Andrani when we left was aside from all of those things, the really phenomenal performances of everybody, the direction, the cinematography, the editing, the score, you name it, right? The surprises. Yeah. Harry Belafonte, I quote him quite often because he has one of my favorite quotes when he spoke at the march on Washington with Martin Luther King. And he said that artists have a really incredible responsibility because artists reflect back to society who they are. Yeah. And that I would love to talk to Deb about because it's so very bold in his communicating and showing of stuff that he clearly has a strong feeling about regarding India. Yeah. And not just his own personal roots but about India as a whole. Yeah. Things he says that are directly related to politics, things that have happened in recent history of certain people groups being persecuted. Yeah. And I, that's one of the things, if we don't get to talk to him, I'm looking for interviews where I can hear what he's sharing about that because that was so, you can't get around that. That's why I'm wondering how the heck I don't know. You can't get around that. I have no idea.  I don't know. So it would be interesting to see what's gonna happen. I don't know if it'll ever get released in India. Me too. Or what version they will see. I think they'll see it on OTT, sadly. Hopefully.  Definitely be R. It's an R film. It's an R film for subject matter and violence and some nudity and it's an adult movie. But no government should tell an artist what they can or can't say. Yeah. Yeah. And so that's about it. I don't really want to get into it. Yeah, me too. I don't really want to get into a lot of spoilers because it's so early and a lot of people haven't seen it yet. Yeah. So I would love and who knows when it's gonna come out in India. Exactly.   You'll have a good time. Yeah, you'll have a great time.


What's up everybody, Jason here for JasperJasperCaseBricks.com. We're doing a quick one-packed solo break of 2019-20 Panini Optic Solo Basketball. It is a one-pack break, number 14 random teams. And again, this is a break to win spots in our last dance basketball mixer, where we're giving away a Michael Jordan autograph. And again, I'm just gonna show you guys the item description page. I know it says number 16. We're doing number 14 here in this video in a separate video to number 15, and then once number 16 sells out, which is down to 11 left, we'll break number 16, but this is number 14, guys, as you can see here, number 14. So again, randomized customer names and teams, open up the solo pack, distribute the hits, and then at the end of the break, get a new dice roller randomizer, get the original 30 customer names, and top four at the end of the randomizer win a spot each in the last dance basketball mixer. So good luck, let's roll it. We got a six and a three again. Rollin' nine today, guys, good luck. One, two, three, four, five, six, seven, eight, and nine. Nine times, Kessler, down to Peter, times Hawks Down to the Wizards. One, two, three, four, five, six, seven, eight, nine. Thunder, down to the Dallas Mavericks. All right, Thunder here, Kessler, Anthony with the Lakers, Kurt with the Rockets, Tyler with the Pacers, Peter with the Pelicans, James with the Horners, last one was with Chris with the Kings, Aaron with the Blazers, Ryan with the Celtics, Chad with the Warriors, Zach with the Pistons, Joe with the 76ers, Peter with the Hawks, Kurt with the Knicks, Spurs, Sean with the Wizards, Chris with the Jazz, Matthew with the Hunnets, Tyler with the Nuggets, James with the Raptors, Zach with the Clippers, Kevin with the Magic, Kurt with the Bulls, Tyler with the Heat, Ace with the Suzz, James with the Grizzlies, Marty with the Cavs, William with the Bugs, Dylan with the Tewos, Peter with the Dallas Mavericks. So let's alphabetize it, whoop, this way first. And quick 30 seconds, guys, no one really makes any trades, but I allow it. All right, guys, and then a separate Dice Rollin' Randomizer, we'll see who wins, spots, and the Last Down Spass will mix here. So we only had to do three guys, 14, which is here now, 15 and the 160 sells out. Number 14, quick Optic Sello, quick Optic Sello. Oh, look at that, right on the top of the pack, we got a Zon, Zon Williamson, Rader Rookie, Peter with the Pelicans, there you go. Tyler Hero, all right, it's the third pack and a half of the jaw, like it should, but it might not, you know. Cameron Johnson, my host DeMar DeRozan, Blue Velocities, Jim on Green, and wow, look at that, what a break for the heat. That's on Tyler, you got a Tyler Hero Velocity. Very nice, awesome O, not a bad one pack Sello. Tyler Hero, Tyler Hero, Zon, very nice. All right, now let's quickly switch scenes. And again, top four, you get a spot each in the mixer after one out of four or five times, good luck. One, two, three, four, and fifth and final time, guys, good luck. Five times, top four. Ryan, you're in, Kevin, you're in, Chad, M, you're in, and Kurt, you're in. Congratulations guys, one, two, three, four. You guys are now in the last dance basketball mixer, which will be coming up soon later on today, jaspyscasebricks.com, coming up next guys, Sello pack number 15 and go away for more spots. Appreciate it.