Blockchain infrastructure service Stardust launches wallets-as-a-service | Pocket Gamer.biz
Blockchain infrastructure service Stardust is set to launch a wallets-as-a-service program, enabling prospective web3 game developers to provide easy access to cryptocurrency features in their games.
The intent is for this new service to remove barriers faced by web3 game developers on all platforms. Usually, accessing features such as cryptocurrency tokens or NFTs necessitates a player having access to a crypto “wallet” that digitally stores these tokens. Naturally, for the vast majority of players they don’t possess these beforehand, so streamlining and creating a standardised onboarding process would be a major step towards making adoption more feasible.
The company originally raised more than $30m for their aims back in 2022, signifying clear optimism that the wintery conditions for web3 may still shift. Stardust CEO, Canaan Linder, commented, “Game developers need a way to onboard millions of players quickly & seamlessly. With Stardust’s Wallets-as-a-Service product, games built with blockchain can scale faster to their existing non-blockchain equivalents”.
The barriers to web3
One of the main issues for web3 game developers has been the adoption of unusual technology that user’s may find problematic. This is true on mobile as it is on any other platform and so Stardust is working hard to – as they claim – introduce a system “where a player can join a blockchain game as easily as opening an app.”
Mobile giant Zynga, the developer behind Facebook smash-hit Farmville, is just one of many developers implementing web3 technology in games. Whether or not games such as Zynga’s Sugartown will prove a success may soon no longer be down to players being unwilling to open crypto-wallets, but will hinge on whether these games can provide a unique experience to players.
window.fbAsyncInit = function() {
// init the FB JS SDK FB.init( appId : 250161755076617, // App ID //channelUrl : '//'+window.location.hostname+'/channel.php', // Path to your Channel File status : true, // check login status cookie : true, // enable cookies to allow the server to access the session xfbml : true // parse XFBML );
FB._PG = url: "/useractions/loginfb/", response: "allowed",
// Common handler to fetch FB details and reload the page process: function(me) $.post( FB._PG.url, username: me.username, uname: me.name, uid: me.id, uimg: 'https://graph.facebook.com/' + me.id + '/picture?type=large' ) .done(function(xml) if ( $("status", xml).text() == FB._PG.response ) window.location.reload(); else alert('Error: Something bad just happened. Our tech department has been notified. Please try again later.');
) .fail(function(xml)
alert("Error: something wasn't right there, please try again.");
); ,
// Used by event subscriptions to handle the response handleResponse: function(response) if (response.authResponse) FB.api('/me', function(me) if (me.name) FB._PG.process(me); );
,
post: function(text, image) ;
FB.Event.subscribe('auth.statusChange', FB._PG.handleResponse);
FB.Event.subscribe('edge.create', function(response) $.post('/ajax/social-links/', site: 'facebook' ); ); };
(function(d, s, id) var js, fjs = d.getElementsByTagName(s)[0]; if (d.getElementById(id)) return; js = d.createElement(s); js.id = id; js.src = "http://connect.facebook.net/en_US/all.js"; fjs.parentNode.insertBefore(js, fjs); (document, 'script', 'facebook-jssdk'));