LiveDocs

livedocs

Identity as we know it – passports, email addresses, social handles – are controlled by centralized powers with the right to revoke it. Every government, platform or service has the concept of identity but, they’re all reinventing the wheel. Offline, your identity is the sum of your driving license, passport, and various membership cards. Online, your account, handle, and usernames you use for each SaaS product composes another identity. All of these identities are fragmented and must play by someone else’s “centralized” rules. To offer real choices and unify incompatible standards is to solve the problem – that’s why DIDs exist and why we’re excited to be building and improving on them with NameSpace IDs. Gmail Instagram DIDs, or decentralized identifiers, are a new type of ID that enables verifiable, self-sovereign digital identities. Unlike traditional identifiers, such as email addresses or usernames, which are issued by centralized entities (like email providers or social media platforms), DIDs are created, owned, and controlled by the subject of the digital identity without the need for a centralized authority or intermediary. They are seen as a solution to many of the challenges and vulnerabilities associated with centralized identity systems, such as data breaches, privacy concerns, and single points of failure. And, for application developers, DIDs can bypass the need to roll your own identity layer. However, even the next generation of identity, like names, are just leased and will return to the market if the owner doesn’t pay renewal fees. Let’s look at how is built to solve these problems for developers and end users. ENS namespace.gg The Namespace.gg Solution The namespace.gg framework enables anyone to spin up a custom name service for their , protocol, or community. It’s an abstraction of the tooling in production for ANS, complete with minting, admin dashboard, and marketplace UIs. DAO Namespace is built on and , meaning that addresses from any chain can be assigned identities and paid for in any token supported by everPay. MEM everPay That means sovereign identity for communities, transacted with your community’s token. Each namespace is indexed by a master resolver, solving the fragmentation issue, and even extensible via Ark Protocol. Ark with namespace.gg enables users to build full profiles, collating and binding all existing DIDs into one, . This is useful around social, reputation and identity verification. regardless of the chain All NameSpace IDs are stored permanently on Arweave and operate on a pay-once-own-forever model, so users don’t have to worry about losing the handle everyone knows them by. Need a custom identity layer for your dApp or community? Check the for a DIY approach or ways to let us help you get your own live! docs The Chain-Agnostic Architecture of NameSpace IDs is a web3 serverless functions platform on Arweave. It allows developers to build trustless and scalable chain-agnostic application backends. MEM is a real-time payment settlement layer that uses the storage-based computing paradigm (SCP), where all calculations are done off-chain, and the results are synchronized with Arweave. everPay is an L1 blockchain and the first truly permanent information storage network backed by a sustainable endowment. Arweave Namespaces in Production The first namespace to go live was . We built the infrastructure to work around the fact that Arweave smart contracts cannot natively custody the $AR token, so the solution involved going chain-agnostic and using a combination of MEM with everPay - an L2 payment processor for Arweave and the EVM. Arweave Name Service Since its launch in February 2023, over 1,500 ANS names have been minted and the protocol has been integrated widely into Arweave’s block explorer, wallets, and dApp ecosystem. We rebuilt the infrastructure for ANS to create an extensible generic MEM contract that can add any kind of wallet authentication or payment token via MEM’s . The rebuild spawned namespace.gg, which is now getting ready to launch DIDs for , and . molecules Hackernoon Raven Protocol AlphaKEK Let’s Explore Use Cases for NameSpace IDs : provide a custom TLD naming service for your DAO members with minting conditions based on factors such as governance participation. Make your DAO token the minting currency. DAO Identities : Establish a unified identity for users across multiple blockchains. With namespace.gg's chain-agnostic approach, users can have a consistent identity whether they're on EVM, Solana, Polkadot, or any other supported chain. Multi-Chain Identity : attach human-readable names to content txids. For example, the namespace.gg user of ANS set their Record to direct to a website on Arweave, which resolves via a custom namespace.gg gateway: shrine.arweave.gg. Decentralized Content Addressing shrine.ar A : As an alternative to centralized social media platforms or piggybacking on existing (expensive, limited) naming services, creators can develop a decentralized social ID layer where users mint their handles, ensuring true ownership of their digital identity and content. Decentralized Social Profiles (DeSoc) : create a custom TLD only mintable by holders of a particular NFT collection. Username layer for a protocol: spin up an identity system for your dApp users instead of building it from scratch. Integrate namespace.gg minting into your dApp UI. NFT Gated Identities : Companies can create a custom TLD specific to their brand, ensuring that all subdomains or identities under it are officially associated with the company. This can enhance brand trust and recognition. Branded Corporate Domains : Organizers of events, conferences, or festivals can offer custom domain names as tickets or passes, providing attendees with a unique digital identity associated with the event. Physical Events : Universities and schools can create a custom TLD for their students and faculty, ensuring a unified digital identity. This can be used for academic profiles, e-portfolios, or even course-specific sites. Educational Institutions Two Ways to Get Started While is in private beta, we are working closely with a handful of projects to onboard and build custom solutions. It is also possible to bootstrap your own implementations using our example contracts. namespace.gg Build a DIY implementation with as a starting point, or… this guide with the team to discuss custom requirements and implementation support. Get in touch Check the for more information, and don’t forget to for updates. namespace.gg docs follow @NameSpace_ID on X

Namespace.gg: A Solution To The (Centralized) Identity Crisis

The complete master-list based on and of the best Vue UI component libraries and frameworks lists for 2019. part 1 part 2 As the star-wars are raging, Vue.js recently passed in the number of GitHub stars. Although still behind React in the sheer number of downloads according to NPM, the popularity of Vue.js seems to be growing. React Like React, one of Vue’s best features is the ability to compose your UI using isolated and modular components. To help build your next application faster, here are some of the best UI component libraries out there in 2019. : Using you can turn any component into an API that you can use from other projects, and even install with NPM, with 0 refactoring. You can also collaborate and share collections with your team. Tip Bit’s component platform _Bit helps you share, discover and use code components between projects and applications to build new features and…_bitsrc.io Bit - Share and build with code components 1. Vuetify This 11K stars popular library provides over 80 Vue.js components implemented according to Google’s material design guidelines. Vuetify supports all modern browsers across platforms, including IE11 and Safari 9+ (using polyfills), and comes with 8 vue-cli templates out of the box. _vuetify - Material Component Framework for Vue.js 2_github.com vuetifyjs/vuetify 2. Quasar framework At over 6K stars, Quasar is a popular framework for building Vue.js powered responsive websites, PWAs, hybrid mobile Apps and Electron apps. Quasar also supports features such as HTML/CSS/JS minification, cache busting, tree shaking, sourcemapping, code-splitting & lazy loading, ES6 transpiling, linting andaccessibility out of the box. _quasar - Quasar Framework_github.com quasarframework/quasar 3. Element At nearly 28K stars, Element is a Vue.js 2.0 UI Toolkit for Web. With a strong community and 350 contributors, the library provides a rich selection of customizable components along with a full style-guide and more resources. _element — A Vue.js 2.0 UI Toolkit for Web_github.com ElemeFE/element 4. Vue material At 6K stars vue-material is a simple library implementing Googles material design. The library also provides a webpack boilerplate, SSR template for Nuxt.js and a single HTML file to start with the framework. Here are some to help you get started. CodeSandBox examples _vue-material - Material design for Vue.js_github.com vuematerial/vue-material 5. Keen-UI At nearly 3.5K stars, keen-ui is a collection of Vue components inspired by material design. Keen UI is not a CSS framework. As such, it doesn’t include a grid system, typography styles, etc. Instead, the focus is on interactive components that require . Javascript _Keen-UI - A lightweight collection of essential UI components written with Vue and inspired by Material Design_github.com JosephusPaye/Keen-UI 6. Buefy At 3k stars this library provides Lightweight UI components for Vue.js based on , which are the library’s only two internal dependancies. The library’s size is about 60KB min+gzip (with Bulma included). You can check out the and play with the code on Codepen. Bulma live docs site _buefy - Lightweight UI components for Vue.js based on Bulma_github.com buefy/buefy 7. Bootstrap Vue At over 5K stars, bootstrap-vue provides implementations of Bootstrap 4 components and grid system for Vue.js and with an automated WAI-ARIA accessibility markup. Here’s a quick link for in the docs. browsing components _bootstrap-vue - BootstrapVue provides one of the most comprehensive implementations of Bootstrap 4 components and grid…_github.com bootstrap-vue/bootstrap-vue 8. Muse-UI At over 6K stars, Muse is yet another MD library for Vue 2.0, providing over 40 UI components and customizable themes. The docs are mainly in Chinese, but most is self explanatory. The project is actively developed and maintained. _muse-ui — Material Design UI library for Vuejs 2.0_github.com museui/muse-ui 9. AT-UI At nearly 1.5K stars, AT-UI provides a modular front-end UI framework for developing fast web interfaces based on Vue.js, suited for desktop apps. With an NPM + Webpack + Babel Front-End development workflow and independent CSS styling, this library is worth checking out. _at-ui - A fresh and flat UI-Kit specially for desktop application, made with ♥ by Vue.js 2.0_github.com AT-UI/at-ui 10. Vux At over 13K stars, Vux is a popular community library is based on WeUI and Vue 2.0. The library also supports a webpack + vue-loader + vux workflow. The here are also in Chinese, and so is the live . docs community hub _vux - Mobile UI Components based on Vue & WeUI_github.com airyland/vux 11. iView At nearly 16K stars, iView provides dozens of UI components and widgets built with Vue.js and styled with a clean and elegant design. iView is widely adopted and , and comes with its own to help create projects in a visual way. This one is worth trying out. actively maintained CLI tool _iview - A high quality UI Toolkit built on Vue.js 2.0_github.com iview/iview 12. Uiv At “only” 550 stars, Uiv is a Bootstrap 3 component library for Vue 2. All component combined are ~20KB, and the only external dependencies are Vue and Bootstrap CSS. A Webpack-based workflow is supported. _uiv - Bootstrap 3 components implemented by Vue 2._github.com wxsms/uiv 13. Vuikit At 1K stars vuikit is a responsive Vue UI library for web site interfaces, with a clean and consistent design. The library is build as a “monorepo” managed by Yarn workspaces, when icons and themes are published as separate packages. _vuikit - A responsive Vue UI library for web site interfaces_github.com vuikit/vuikit 14. Onsen UI + Vue Based on the popular Onsen-UI frameworks, These Vue bindings for the provide components that wrap the core web Components and expose a Vue-like API. Onsen UI Components are also designed to act reactively to props. _Learn how to use Vue.js with Onsen UI._onsen.io Vue.js 2+ - Onsen UI 15. Semantic Ui + Vue This project is basically a Vue.js integration for the popular Semantic-UI framework. Still under development, the library provides an API similar to that of Semantic-UI as well as a set of customizable themes. See . example _Semantic UI Vue is the Vue integration for Semantic UI_semantic-ui-vue.github.io Semantic UI Vue 16. Fish-UI Although “only” at 500 stars and 3 contributors, fish-ui provides a Vue-based web toolkit with neat and clean looking components. The library supports a ES2015 + Webpack workflow. The documentation isn’t great, but the design is not to be overlooked. Your’e welcome to take a peek. _fish-ui - A Vue.js 2.0 UI Toolkit for Web_github.com myliang/fish-ui 17. Mint UI At over 11K stars, Mint-UI provides UI elements for Vue.js, with CSS and JS components for building mobile applications. When all imported, the compressed code takes only ~30kb (JS + CSS) gzip space. Import for individual components is supported. Here’s a . quick demo _mint-ui - Mobile UI elements for Vue.js_github.com ElemeFE/mint-ui 18. Framework 7 Vue This integration provides almost all of Framework7's elements and components with integration of Framework7 Router to render pages in a Vue completable way. The library is under and maintenance. active development _Bring components-syntax, structured data and data bindings to Framework7 with power and simplicity of Vue.js_framework7.io Framework7 Vue 19. Cube UI At over 3K stars cube-ui is a UI component library for Vue.js mobile apps. All components are unit-tested, and the library also supports and component import on demand. Cube-UI is still under active development. post-compile _cube-ui - 🔶 A fantastic mobile ui lib implement by Vue_github.com didi/cube-ui 20. Vueblu At 1.5K stars, vueblu is a UI component library based on Vue 2.0 and , made for building middle and back office products. It supports ES2015 and an NPM+Webpack+Babel workflow, and provides customizable themes. Bulma _vue-blu - UI Component Library Base on Vue.js(2.x) and Bulma_github.com chenz24/vue-blu 21. Ant design Vue At 1.5K stars, this Vue.js integration for is built for developing enterprise-level back-end products with dozens of components implementing Ant design, and supports a Webpack-based debug build solution that supports ES6. Note that it hasn’t been developed for a while. Ant design _vue-antd - Vue UI Component & Ant.Design_github.com okoala/vue-antd Honorable mentions ⭐️ , , , , , , , , … comment to add more! :) n3-components vuikit Kendu UI Vue Office Fabric-Vue vuestrap vueboot framevuerk Vue WeUI Vue-MDC Learn more _9 Useful tips for writing better code in React: Learn about Linting, propTypes, PureComponent and more._blog.bitsrc.io How To Write Better Code In React _5 tools to speed the development of your React application, focusing on components._blog.bitsrc.io 5 Tools For Faster Development In React _11 Useful Javascript utility libraries to speed your development._blog.bitsrc.io 11 Javascript Utility Libraries You Should Know In 2018

21 Top Vue.js UI Libraries For Your App

How did games as service emerge, what are they used for, what are LiveOps in games, why does CS not change with years and stays popular, what else will be created in Fortnite and what is awesomeness inflation? There are so many questions that I decided to arrange them into a small FAQ. And this is because a whole chunk of games which aim at years of life are becoming games as a service (GaaS) and shifting towards the Metaverse. It became more evident when Fortnite began creating global in-game events, content for them and collaborations. This system is not suitable for everyone (and doesn’t appeal to everyone), but the trend is obvious. Even separate LiveOps for featuring modules have appeared in mobile stores. It means that stores themselves began giving developers marketing tools for events promotion inside games. And such games as CS don’t almost change and still stay popular. Does it mean that using LiveOps can spoil the game? It certainly can. FAQ LiveOps is a relatively new term. In Game Dev it refers to a number of in-game events, content, narrative and promotions. It is necessary for maintaining the project life when players have already mastered the core and meta — then they need events to refresh the experience, get new emotions not to turn the game into a routine. — What is LiveOps in gaming? At first developers created some content connected with holidays merely for a change. Even eight years ago my team was creating content for a mobile game which was connected with Halloween and other holidays. We added theme weapon and decorated the lobby — it was enough for that time. — How did it emerge? Seeing the interest of gamers and a burst of activity developers began to create more unique content for holidays — temporary locations, dungeons etc. It was almost always tied up to the world events and gradually, starting with separate items of content, it began to be packed into a narrative wrapper. It partially started with the Battle Pass. If you buy the Battle Pass, the longer you play the more prizes you get. It was a purely commercial idea but then it was tied up to a certain event. As a result commercially successful algorithm mixed with the effectiveness of the event season and it began to turn into carefully crafted game seasons. For example, there appeared a global enemy in a game universe as well as monthly quests, locations and content connected with it in particular. So, at some moment it became clear that it was possible to generate your own events without tying them up to the real world. Gamers inside the project have their own independent life — they relax, socialize, make friends, simulate situations and create their own content based on games. In most games, if there are no changes for a long time, gameplay turns into a routine and gamers start leaving the game in spite of the progress. These are objective metrics and that is why in Fortnite there appeared UFOs arriving for a month, the Cube Queen destroying the island piece by piece etc. — Why does it work? [ Here is a video about ] Fortnite’s storyline If you dig deeper, you can see that it is all about the human biology. Novelty and suspense reward brain. Just catching pokemons or shooting for a whole year is for the most part is boring. If in the game at some point everything becomes made of jelly and there is a giant ball gliding over the area and throwing bazookas — a gamer would want to see it with their own eyes and return to the game. Especially, if all other gamers in the game community start discussing it. Pokemon Go, for example, do all of it in reality. They rent the whole parks in different parts of the world and organize huge events. People come just because they can catch certain pokemons only in these locations. These are also LiveOps (and they happen to be literally Live). [ This is an example of quite a recent event: ] Pokemon GO Fest 2022 When Arcane was released, they made a collaboration with с PUBG — added a flying city, a new mode and a content pack, getting branded LiveOps. [ You can find this collaboration video ] there LiveOps model is not suitable for every project. CS:GO practically doesn’t change with years and still remains super popular. But even CS makes steps towards events, new modes and content. It just does it very carefully because the game core is strongly tied to sport. The main goal of CS is building personal skill to take part in ranked games. — And what about CS? I’ve been playing it for 20 years and still not bored! In CS or Dota 2 not much can be changed because players gain their skill, they spend a lot of hours on that to get into a rating system or a tournament. Аnd Fortnite is a fun service which provides the environment where players do simple things but at the same time their experience changes. If in CS Glocks are changed for water guns, a few people will be happy about it. If the game rules are changed, it is still worse. But it is possible to carefully introduce new modes without distracting from classical matches as Valve did. We can’t say that games as service are bad. Originally, those were gamers who got interested in this system. It isn’t just suitable for every project. For example, a part of players left mobile Lineage Revolution. I happened to enter this game a year later and saw Batman driving by on Vespa. It was not what I expected from an anime MMORPG. Although even in League of Legends there is a skin of a meta-courier from KFC. [ In some regions they made a promotion with ] local delivery services But if such content is supplied in big amounts, there will remain only a thin layer of players. Events themselves are necessary and important but you shouldn’t cross the line when the context of the project, its special features and the basis get changed. For example, in CS this is special forces against terrorists with real weapon. It is acceptable to change the colouring because it doesn’t break the specificity. But if you add inflatable guns, adult audience won’t accept it. In LiveOps you can easily be carried away. There are no problems if from the very beginning the game is designed taking this model into account. Fortnite’s metrics soared up when the game became a shooter with battle royale and the first event took place (a meteorite fell down). After that events became more epic, a special team was hired, they began connecting characters with each other, added branded things to the game, arranged music concerts etc. [ And in Pokemon GO there is a special , well, you get the idea ] collection of UNIQLO clothes In Fortnite they have already made a black hole sucking the world twice. When you start epically you cut off any opportunities for development. If you have marketed something that destroys reality, it will be more problematic to make something more awesome. But the problem of awesomeness inflation is quite common nowadays including the film industry. — What will happen when the ideas of events end up? Spider-man used to simply fly web but now he meets himself from different universes. «South Park» broke the fourth wall, in «Rick and Morty» Morty went beyond the reality established by his granddad. [ It becomes obvious that the spectator’s mind has already matured to consume more complicated concepts. ] It is now necessary to make things more and more sophisticated to spark interest. But at the same time it involves analyzing and planning further on to be able to slow down at any moment. If one creates a complicated event in the very beginning, they won’t be able to compete with themselves. After a season about traveling in space one can create an event about spies. Imaginary context can be changed into real — it is important to create contrast and it doesn’t have to be necessarily about the meaning, it has to provide a new experience. On the whole, it is a self-complicating process, and it seems to me that there will be a serious crisis in two years, it will become difficult to impress people. Developers will have to aim at the lowest biological levels. For example, the authors of Gravity Falls made Inside Job (drugs, sex, death). They did it for the sake of contrast and competition. The next who will use the same context will have to do it tougher. Or, on the contrary, everybody will get sick and tired of it. In design, for instance, everybody has got back to eco and minimalism again. [ In their turn, the authors of Rick and Morty released even tougher ] Solar Opposites. First, you need a preparatory part. You should announce, make teasers, spoilers — that is to prepare people. Then you should gradually develop (if gamers don’t get the idea, they won’t get interested), sustain and during a certain period of time give out the content in portions so that gamers couldn’t get it all quickly. That is why events connected with one storyline start off with pauses. The clearer a story is told, the more content will be consumed. — Are there any peculiarities of creating a big event? Then you should create as many points connected with each other as possible. For instance, we are creating an event with an alien in a shooter. In a free game mode, without any timing, when people just run around, we hang up plates which teleport people between maps. And in the main mode you create a reskin of the map for the context. It turns out that in all modes where monetization works gamers got a piece of a new content. At the same time the pack should relate to everything: the lobby, the screen, loading, all the modes, the content etc. Ideally, you should add unique mechanics for this season. It is very important so that all the groups of players felt the changes. There are also buffer events (or secondary) between main events in a big pack. They are inserted between main seasons. If there is an ancient event (the Vikings, Egypt), we carry out spin-off sales of the relevant content, and the event starts working more efficiently. If people run around an arena among gladiators, it becomes clearer to them why they need swords in a shooter. As people consume it in cycles, you should supply the content in turns. If you had a Sci-Fi season, next you should make a historical one, then in a cartoon style or a weird one (food, a virtual word). Then you make a real-life one. If there is a constantly playing core of people, you shouldn’t give them one and the same theme twice in a row. And on the contrary, if they’ve just had blasters and then they are given live guns with eyes, they will be more eager to get a new content. To metaverses. Facebook was renamed into Meta and is preparing a base for people to log in with a physical avatar wearing a helmet (yes, they are not very successful yet but we are speaking about the future). Some people are preparing a platform allowing to log in from one metaverse into another, but it is a different story. — Where is everything moving? [ And this is a teaser of the next article about what shouldn’t be called by name so far this year… ] In Fortnite there appeared Balenciaga clothes, Nike sneakers, Ferrari cars etc. Something similar once was in Second Life. Nowadays you won’t get far with a fancy shooter as the audience has become more demanding. Even Apple, when asking game developers about their plans for their stores, they ask particularly about LiveOps, moreover about plans for a whole quarter of a year. Studios plan events for upcoming months, membership, marketing. It means that all the major developers gradually start thinking about these categories. Useful links > > > > Liveops modules from stores: https://play.google.com/console/about/programs/liveopsbeta/ https://developer.apple.com/app-store/in-app-events/ Traffic sellers’ perspective: https://www.applovin.com/blog/what-are-live-ops-and-why-are-they-important Super useful tool for comparing trends and their impact: https://trends.google.com/trends/explore?date=today%205- y&amp;q=minecraft,fortnite,roblox,genshin%20impact,brawl%20stars P.S. If the article sparks heated debate, I will throw even more provocative material, so stay turned.

Why is Gaming Shifting to LiveOps, the Metaverse and Who Does Not Need It

Single-Threaded Node.js is a Myth  

Microarchitectural Security of AWS Firecracker VMM: Abstract & Intro

AWS ফায়ারক্র্যাকার VMM এর মাইক্রোআর্কিটেকচারাল নিরাপত্তা: বিমূর্ত এবং ভূমিকা

Mikroarchitektonische Sicherheit von AWS Firecracker VMM: Zusammenfassung und Einführung

Seguridad microarquitectónica de AWS Firecracker VMM: resumen e introducción

Sécurité microarchitecturale d'AWS Firecracker VMM : résumé et introduction

AWS फायरक्रैकर VMM की माइक्रोआर्किटेक्चरल सुरक्षा: सार और परिचय

AWS Firecracker VMM のマイクロアーキテクチャセキュリティ: 概要と概要

AWS Firecracker VMM의 마이크로아키텍처 보안: 개요 및 소개

Segurança microarquitetônica do AWS Firecracker VMM: resumo e introdução

Микроархитектурная безопасность AWS Firecracker VMM: Аннотация и введение

AWS Firecracker VMM'nin Mikro Mimari Güvenliği: Özet ve Giriş

Bảo mật vi kiến trúc của AWS Firecracker VMM: Tóm tắt & Giới thiệu

AWS Firecracker VMM 的微架构安全性：摘要和简介

**SHERMAN OAKS, United States, March 5th, 2024, GamingWire/--**Empowering Mobile Game Developers to Monetize Across Multiple Platforms Beyond Traditional App Stores. Xsolla, a global video game commerce company, has introduced Cross-Play and Cross-Pay, an innovative approach to mobile game monetization. In response to the evolving landscape, Xsolla’s suite of solutions enables mobile game developers to seamlessly transition their games from mobile to the web, desktop, and cloud while offering diverse monetization models out-of-the-box to power profitable direct-to-consumer sales for game developers. As the video game industry evolves, players anticipate engaging with their favorite titles seamlessly across all platforms, form factors, and control methods. This growing expectation places Cross-Play at the forefront of modern game development strategies. Mobile game developers can now effortlessly deploy their games across Mobile, PC, Console, Cloud, and Web with Xsolla Launcher and Xsolla Cloud Gaming. Xsolla Launcher makes it easier for developers to leverage the capabilities of desktop computing, including enhanced graphics, gameplay depth, and longer play sessions when porting mobile games to PC. Cloud Gaming for Mobile Games, in turn, is a strategic extension of the core Xsolla Cloud Gaming solution. It enables mobile video game developers to expand cross-platform by deploying game builds to cloud platforms directly from the developer's own branded landing page, allowing them to deliver flexible monetization mechanics for mobile users. Cross-Play experience ensures consistent and fair monetization strategy across all platforms for developers around the world. This approach ensures equal access to game content for players, thereby enhancing the overall playing experience while adhering to platform rules and guidelines. Xsolla Web Shop, a leading solution for web purchases, is a foundation for the Direct-to-Consumer strategy for mobile game developers. Web Shops are easily customizable branded online stores fully equipped to facilitate in-game web purchases. The next iteration of the Xsolla Web Shop Solution includes innovative updates drawing on Xsolla's expertise gained from launching over 210 Web Shops and 40 of the top 100 highest-grossing mobile games worldwide. Xsolla Web Shop introduces advanced LiveOps tools, additional personalization and engagement features, and an improved user flow for seamless purchases. Alongside these enhancements, Xsolla's experts are always available to offer guidance and support by providing best practices consultation in navigating the operation and management of web shops. "The advancements made with Cross-Play Cross-Pay have been a focus of our innovation over the past year after collaborating with numerous partners and launching over 200 web shops in 2023. This extensive real-world application with customer feedback has helped mobile game developers to efficiently market their games online by operating within the platform guidelines," said David Stelzer, President of Xsolla. "Cross-Play Cross-Pay is our strategic innovation to meet the continuously evolving demands of the ever-changing mobile game industry. By delivering a multi-platform solution for mobile game developers, we can help them to reach more players and to grow their business." This comprehensive suite of Cross-Play Cross-Pay solutions empowers mobile developers to ensure their games reach the widest possible audience by establishing deep and lasting connections with players around the globe. For more information about Xsolla Web Shop 2.0 and its features, please visit: For more information about Xsolla Cloud Gaming for mobile and its features, please visit: For more information about Xsolla Launcher, please visit: . xsolla.pro/web-shop2 . xsolla.pro/cloud-gaming xsolla.pro/xsolla-launcher About Xsolla Xsolla is a global video game commerce company with a robust and powerful set of tools and services designed specifically for the industry. Since its founding in 2005, Xsolla has helped thousands of game developers and publishers of all sizes fund, market, launch and monetize their games globally and across multiple platforms. As an innovative leader in game commerce, Xsolla’s mission is to solve the inherent complexities of global distribution, marketing, and monetization to help our partners reach more geographies, generate more revenue, and create relationships with gamers worldwide. Headquartered and incorporated in Los Angeles, California, with offices in London, Berlin, Seoul, Beijing, Kuala Lumpur, Raleigh, Tokyo, and cities around the world, Xsolla supports major gaming titles like Valve, Twitch, Roblox, Epic Games, Take-Two, KRAFTON, Nexters, NetEase, Playstudios, Playrix, miHoYo, and more. For additional information and to learn more, please visit: xsolla.com Contact Derrick Stembridge Xsolla d.stembridge@xsolla.com 9194800002 This story was distributed as a release by GamingWire under HackerNoon’s Business Blogging Program. Learn more about the program here.

Xsolla Unveils Cross-Play And Cross-Pay Strategy To Enhance Multi-Platform Monetization

This paper is under CC 4.0 license. available on arxiv Authors: (1) Tariq Bontekoe, University of Groningen; (2) Dimka Karastoyanova, University of Groningen; (3) Fatih Turkmen, University of Groningen. Table of Links Abstract & Introduction Preliminaries Zero-knowledge proofs and verifiable computing Privacy-preserving computations Requirements: an application’s perspective Verifiable, privacy-preserving computing Open challenges and future directions Conclusion & References 5. Requirements: an application’s perspective In this section, we discuss how verifiability is combined with privacy-preserving computing in practical settings that are frequently observed for verifiability and/or privacypreserving computations. We discuss two frequent scenarios: verifiable outsourcing and blockchain; and two use cases showing specific requirements: e-voting and genomics. These were the most frequently observed scenarios and use cases in existing literature. For each application we summarize the domain-specific requirements and efficiency trade-offs, that answer when combined. Each property has a specific mark X assigned, that will be used for reference in subsequent sections. RQ2 5.1. Verifiable outsourcing One of the first and most straightforward applications of verifiable PETs is that of verifiable outsourcing, where a (group of) data owner(s) outsource(s) a costly computation to a computing party with more resources. This computing party produces a computation result as well as a ZKP, trusted execution environment (TEE) attestation, or MAC to guarantee correctness. When the used verification method allows for verification that is more efficient than the original computation, the scheme is considered efficient. Pinocchio [21] was one of the first efficient ZKP schemes for general computations, making it practical for verifiable outsourcing. Since then, many new ZKPs schemes with better efficiency or security have been constructed, e.g., [22], [25], [49], [50]. However, when applying these schemes directly, they do not provide data privacy in most use cases, even though this is a necessity when computing over private data distributed over multiple parties. Since, in most cases, only the clients that outsource their computation need to be able to guarantee correctness, public verifiability is often not necessary. Most importantly, verifiable outsourcing is only beneficial when the verification (and/or preprocessing) time of the clients is significantly smaller than the time it would take to compute the outcome by themselves, i.e., the solution should be efficient. 5.2. Blockchain Blockchain was introduced as a platform to realize decentralized online currency, but has since become a much broader platform. The recent surge in blockchain and DLT applications, such as dApps, has also had significant impact on the development of new ZKP schemes, an important solution for verifiability. However, blockchain applications also frequently rely upon ZKPs to provide applications that guarantee correctness, whilst maintaining privacy. Examples of such applications range from private monetary transactions, e.g., Zerocash [7], Zether [26], and others [51], [52], to private smart contracts, e.g., Hawk [53], and decentralized private computation (DPC), e.g., ZEXE [54]. Due to the decentralized nature of blockchain, with a lack of central authority to guarantee correctness over private data, verifiable computing methods are a logical, and often unavoidable, solution. For most blockchain applications, regular verifiability will often not be sufficient. Since every (future) connected party must be able to verify any message posted to the blockchain, public verifiability is a necessary requirement. To prevent scaling issues in blockchain applications, developers attempt to keep verification times low, and onchain messages as small as possible. Therefore, solutions that sacrifice prover time for lower verification times and sublinear (or constant) sized verification messages are favorable. Finally, we note that interactive protocols are, generally speaking, not suitable for distributed ledgers as that would require direct communication, conflicting the principles of DLT. Since non-interactivity is a prerequisite for public verifiability, we do not include this requirement by itself. 5.3. Verifiable privacy-preserving genomics Usage of privacy-preserving computations in genomics has taken a big leap in the past decade [55], [56], [57] and even led to a yearly competition on human genome privacy [58], [59], [60], with specific tracks on the use of PETs and blockchain. The first application of verifiable computing in the genomic domain is discussed in [61], as far as we are aware. Specifically, the authors propose the use of HE and homomorphic MACs to outsource computation of the disease susceptibility (DS) score to a third party in a privacypreserving and verifiable manner. The increase in efficient methods for verifiable computing in recent years, has also led to the first solutions in this domain. A method to perform an elastic net regression among multiple parties in a privacy-preserving manner, by outsourcing the computation to a pair of non-colluding cloud providers, is proposed in [62]. Correctness of the result is guaranteed by verifying that the evaluation of the final gradient is close to zero. [63] presents a solution for evaluating secure count or top-k queries on multi-source genomic data. All data is encrypted using an additively homomorphic encryption scheme and shared with two non-colluding cloud providers. The cloud parties evaluate the query, with privacy of query, input data, and result, and use MACs to guarantee correctness. [64] presents a verifiable homomorphic secret sharing scheme for evaluating polynomials of low degree. Verifiable genomic analyses, and verifiable computations on outsourced data are mentioned as possible use cases. Lastly, [65] computes the minor allele frequency (MAF) score over multi-source data in a blockchain setting. The more expensive computations, those on additively HE ciphertexts, are performed off-chain, ZKPs are used to guarantee correctness thereof. It is clear that the use cases in genomics are very diverse and have different requirements regarding efficiency or which parties can verify. However, it is abundantly clear that genomic data requires strong privacy guarantees. Due to the long-livedness of genomic data, i.e., a person’s genome also reveals significant private information on their family and descendants, store-now-decrypt-later attacks form a serious risk, especially at the dawn of practical quantum computing [66]. The use of post-quantum secure solutions should therefore be seriously considered for any work in the genomic domain. 5.4. Verifiable e-voting An electronic voting system allows a population to cast their votes using electronic rather than physical means. The need for data privacy follows directly from the fact that, in general, elections and voting processes require voter privacy. Using verifiability techniques to make elections completely verifiable by the general public has been a topic of active research for many years, e.g., [67], [68]. The developments in blockchain and more efficient ZKPs have led to many new proposals for e-voting solutions. [69] discusses the use of NIZK proofs to make threshold homomorphic encryption-based voting secure. A novel SNARK-friendly, additively-homomorphic verifiable encryption scheme is proposed and applied to verify vote validity is presented in [9]. Recently, [70] proposes an end-to-end verifiable and secret election scheme, based on NIZKs and MPC. Blockchains and cloud servers can both be used to store the secure ballots. It is easy to see that public verifiability is a requirement in verifiable e-voting schemes. Next to this, trust is one of the most important factors to guarantee that e-voting schemes are to be adopted in practice [71]. It may therefore make sense, to only use solutions that are post-quantum secure and rely on standard assumptions to improve the level of trust, potentially at the cost of some efficiency.

Applications of Verifiable Privacy-Preserving Computing

141 Stories To Learn About Games

223 Stories To Learn About Game Development

Debugging: The Nature of Bugs, Their Evolution, and Tackling Them More Effectively

ডিবাগিং: বাগগুলির প্রকৃতি, তাদের বিবর্তন এবং তাদের আরও কার্যকরভাবে মোকাবেলা করা

Debuggen: Die Natur von Fehlern, ihre Entwicklung und eine effektivere Bekämpfung

Depuración: la naturaleza de los errores, su evolución y cómo abordarlos de forma más eficaz

Débogage : la nature des bogues, leur évolution et leur résolution plus efficace

डिबगिंग: कीड़ों की प्रकृति, उनका विकास, और उनसे अधिक प्रभावी ढंग से निपटना

デバッグ: バグの性質、その進化、およびより効果的に対処する

디버깅: 버그의 특성, 진화 및 보다 효과적인 해결 방법

Depuração: a natureza dos bugs, sua evolução e como lidar com eles de maneira mais eficaz

Отладка: природа ошибок, их эволюция и более эффективное их устранение

Hata Ayıklama: Hataların Doğası, Gelişimi ve Onlarla Daha Etkili Mücadele

Gỡ lỗi: Bản chất của lỗi, sự tiến hóa của chúng và cách xử lý chúng hiệu quả hơn

调试：错误的本质、它们的演变以及更有效地解决它们

Stories, News & Mentions about LIVEDOCS

Livedocs’s Stories on HackerNoon