Web, Mobile and Browser Extensions

Abstract

A system for transacting blockchain assets includes a blockchain engine having a cryptographic tool configured to generate a plurality of cryptographic hashes to create a sequence of encrypted data blocks storing a plurality of blockchain assets and their transactions for a plurality of users, a wallet tool for processing user requests for asset transactions between one or more users of one or more blockchains and facilitating wallet-to-wallet transactions, wallet-to-smart contract transactions, and record keeping, and a statistical tool for providing analytical information regarding the asset transactions. The system also includes a portfolio management engine having an aggregator tool for aggregating assets for each user and across one or more blockchains to provide to the statistical tool, and a smart contract tool for providing secure contracts to two or more parties involved in the asset transaction. A method for conducting asset transactions in a blockchain using the above system is also provided.

Description

[Technical field]

[0001] [CROSS REFERENCE TO RELATED APPLICATIONS] This disclosure is related to and claims priority under 35 U.S.C. § 119(e) to U.S. Provisional Patent Application No. 63 / 309,423, by Nicholas John Mussallem, et al., entitled WEB AND MOBILE BROWSER EXTENSION, filed on February 11, 2022, the contents of which are incorporated herein by reference in their entirety for all purposes. [Background technology]

[0002] (Field) The present disclosure relates generally to applications for handling transactions with blockchain assets. More specifically, the present disclosure is directed to a browser extension that enables a web browser to seamlessly and securely conduct transactions with assets on different blockchains.

[0003] (Related Technology) Blockchain networks are widely deployed and used to securely store assets and perform smart contract operations and other secure and tamper-proof transactions between parties. However, users often find complexity when trying to transfer assets between different blockchains or perform asset transactions. Current attempts to bridge the gap between different blockchains have encountered multiple hurdles in terms of compatibility and network architecture. There is a lack of a comprehensive platform that is compatible with multiple blockchain networks and flexible in terms of device access (mobile, browser, web app). Summary of the Invention

[0004] In a first embodiment, the system includes a blockchain engine having a cryptographic tool configured to generate a plurality of cryptographic hashes to create a sequence of encrypted data blocks that store a plurality of blockchain assets and transactions thereof for a plurality of users, a wallet tool configured to process user requests for asset transactions, including sending and receiving assets between two addresses on the blockchain, a statistics tool configured to provide analytical information regarding asset transactions, a swap tool configured to swap blockchain assets, a bridge tool for accessing two or more blockchains, and a purchase tool for purchasing blockchain assets using fiat currency. The system also includes a portfolio management engine having an aggregator tool configured to aggregate assets for each user and across two or more blockchains to provide to the statistics tool, and a smart contract tool configured to provide a secure contract to two or more parties involved in the asset transaction, and an account management engine including an address book tool and an account switching tool.

[0005] In a second embodiment, a computer-implemented method includes providing, via an application interface, a client device having a first user with a list of a plurality of assets in a first blockchain to which the first user subscribes; receiving, via the application interface, a request from the first user to conduct a transaction involving one or more of the assets in the first blockchain; determining a value of the transaction; and conducting the transaction when the first user accepts the value of the transaction.

[0006] In a third embodiment, a non-transitory computer readable medium storing instructions that, when executed by a processor, cause the computer to perform a method including providing, via an application interface, a client device having a first user, a list of a plurality of assets in a first blockchain to which the first user subscribes; receiving, via the application interface, a request from the first user to conduct a transaction involving one or more of the assets in the first blockchain; determining a value of the transaction; conducting the transaction when the first user accepts the value of the transaction; applying the value of the transaction to an account of the first user; and providing, via the application interface, a representation of the account to a wallet tool in an application running on the client device.

[0007] In another embodiment, a system includes first means for storing instructions and second means for executing the instructions to cause the system to perform a method. The method includes providing, via an application interface, a client device having a first user with a list of a plurality of assets in a first blockchain to which the first user subscribes, receiving, via the application interface, a request from the first user to conduct a transaction involving one or more of the assets of a second user subscribed to the first blockchain, determining a value of the transaction, and conducting the transaction when the first user and the second user accept the value of the transaction.

[0008] In some embodiments, the system supports subnets as independent blockchains that can be launched by third parties and have their own rules regarding membership and token economics. Thus, the system includes validators that validate the state of one or more blockchains in the network and achieve consensus, regardless of which network the user is connected to. In some embodiments, each blockchain is validated by one subnet, and one subnet may handle one or more blockchains. Additionally, one validator may service one or more subnets. In some embodiments, the system allows users to add new subnets, interact with them, hide them, and approve transactions between subnets.

[0009] These and other embodiments will become apparent to those of ordinary skill in the art in light of the following. [Brief description of the drawings]

[0010] [Figure 1] 1 illustrates a network architecture that supports applications for managing blockchain assets, according to some embodiments. [Diagram 2] A block diagram illustrating devices, components, engines, tools, and mobile applications used in the network architecture of FIG. 1 in accordance with some embodiments. [Figure 3A] FIG. 1 is a block diagram illustrating modules and components in an application for managing blockchain assets, according to some embodiments. [Figure 3B] FIG. 1 is a block diagram illustrating modules and components in an application for managing blockchain assets, according to some embodiments. [Figure 3C]FIG. 1 is a block diagram illustrating modules and components in an application for managing blockchain assets, according to some embodiments. [Figure 3D] FIG. 1 is a block diagram illustrating modules and components in an application for managing blockchain assets, according to some embodiments. [Figure 3E] FIG. 1 is a block diagram illustrating modules and components in an application for managing blockchain assets, according to some embodiments. [Figure 3F] FIG. 1 is a block diagram illustrating modules and components in an application for managing blockchain assets, according to some embodiments. [Figure 3G] FIG. 1 is a block diagram illustrating modules and components in an application for managing blockchain assets, according to some embodiments. [Figure 3H] FIG. 1 is a block diagram illustrating modules and components in an application for managing blockchain assets, according to some embodiments. [Figure 3I] FIG. 1 is a block diagram illustrating modules and components in an application for managing blockchain assets, according to some embodiments. [Figure 3J] FIG. 1 is a block diagram illustrating modules and components in an application for managing blockchain assets, according to some embodiments. [Figure 3K] FIG. 1 is a block diagram illustrating modules and components in an application for managing blockchain assets, according to some embodiments. [Figure 3L] FIG. 1 is a block diagram illustrating modules and components in an application for managing blockchain assets, according to some embodiments. [Figure 4A]FIG. 1 illustrates a screenshot of an application for managing blockchain assets, according to some embodiments. [Figure 4B] FIG. 1 illustrates a screenshot of an application for managing blockchain assets, according to some embodiments. [Figure 4C] FIG. 1 illustrates a screenshot of an application for managing blockchain assets, according to some embodiments. [Figure 4D] FIG. 1 illustrates a screenshot of an application for managing blockchain assets, according to some embodiments. [Figure 4E] FIG. 1 illustrates a screenshot of an application for managing blockchain assets, according to some embodiments. [Figure 5A] FIG. 13 illustrates a screenshot of an asset transaction between blockchains managed via an application, according to some embodiments. [Figure 5B] FIG. 13 illustrates a screenshot of an asset transaction between blockchains managed via an application, according to some embodiments. [Figure 5C] FIG. 13 illustrates a screenshot of an asset transaction between blockchains managed via an application, according to some embodiments. [Figure 5D] FIG. 13 illustrates a screenshot of an asset transaction between blockchains managed via an application, according to some embodiments. [Figure 6] 1 is a flowchart illustrating steps in a method for transacting blockchain assets, according to some embodiments. [Figure 7] FIG. 1 is a block diagram illustrating a computer system configured to host an application for managing blockchain assets, according to some embodiments.

[0011] In the figures, elements having the same or similar reference numbers are associated with the same or similar attributes, unless otherwise stated. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it will be apparent to those skilled in the art that embodiments of the present disclosure may be practiced without some of these specific details. In other instances, well-known structures and techniques are not shown in detail so as not to obscure the present disclosure.

[0013] (General Overview) Current blockchain networks are highly fragmented, forcing users to operate within each specific network with little overlap in resources and functionality. There is a lack of centralized workflows that provide a unified experience to take full advantage of features such as bridging assets, buying assets, lending assets, and exchanging assets across multiple blockchain networks (or subnets).

[0014] The embodiments disclosed herein solve the above-mentioned technical problems that arise in the realm of computer networks, and more specifically, blockchain networks, by creating functionality at the protocol level that allows users to leverage blockchain network assets (e.g., tokens, non-fungible tokens -NFTs- and fungible assets) as validators or delegate blockchain assets to third-party validators. Such functionality may be incorporated as a browser add-on, mobile application, or web-based application that users can operate from a desktop computer.

[0015] In some embodiments, a wallet tool is provided to allow users to interact with blockchain assets across platforms. The system provides users with full control of their assets and the ability to delegate some functions to selected third parties. Some functionality includes integration with third-party lending aggregators to provide a gateway for third-party services within the wallet tool. Some embodiments allow users to link with third-party lending protocols to sign and execute financial transactions involving one or more assets across a blockchain network. In this way, users participate in lending / borrowing activities using third-party lending protocols. Thus, the wallet tool disclosed herein provides users with an aggregated overview of borrowing and lending rates across multiple platforms. These lending and borrowing services may be integrated into the application by linking with third-party application programming interfaces (APIs), but users maintain the ability to link with liquidity providers or other financial institutions outside of the environment provided herein.

[0016] Some embodiments include monetization strategies such as collecting fees as a percentage of a given transaction amount or receiving commissions from third-party lending protocols. For example, some third-party payment applications may allow users to pay using their credit cards or blockchain asset transfers. These third-party applications may include "know your customer" (KYC) processes that collect data directly from users. Bridging applications disclosed herein may be configured to receive a flat fee or a percentage of the purchase amount, or commissions in fiat currency, according to an agreed-upon schedule.

[0017] The embodiments disclosed herein remove personally identifiable information (PII) by using anonymized IP addresses, hashed public wallet addresses, and device identifiers. In some embodiments, the application uses a third-party service to collect IP addresses and device identifiers from the user upon first use (e.g., when the user launches the product and creates a wallet). The third-party service provider anonymizes the IP address prior to sending it to the application for storage / use. The third-party service collects and pseudonymizes (e.g., via one-way hash) the public wallet address and device identifier, and sends them via an API call to the server hosting the application. The pseudonymized identifiers are securely stored in a database.

[0018] In some embodiments, users do not need to "sign up" to access the applications disclosed herein. Rather, users may download products and functionality directly through third-party services. For example, browser extensions may be downloaded through a third-party web store. Similarly, users may download mobile applications from a third-party app store.

[0019] Aspects of the disclosure include downloadable computer software for use as a cryptocurrency and digital asset wallet that enables the user to send, receive, sell, lend, borrow, and transfer crypto assets, read Quick Response (QR) codes, make purchases, manage contact information for other cryptocurrency and digital asset wallet users, manage user identities, verify user identities, transfer crypto assets between blockchains, and transfer crypto assets between accounts; and a hardware cryptocurrency wallet and cryptoasset transaction ledger that enables the user to manage private key management, sign transactions, staking tokens of value, create non-fungible tokens, view non-fungible tokens, interact with non-fungible tokens, exchange non-fungible tokens, and perform other functions. downloadable computer software for enabling transactions in a blockchain-based decentralized computing environment, including acquiring cryptocurrency wallets, transacting in non-fungible tokens, creating smart contracts, creating subnets, accessing other cryptocurrency wallets, digital asset custody, accessing a remittance and settlement platform controlled by others and for communicating with other cryptocurrency and digital asset wallet users; downloadable web browser software for accessing and navigating the blockchain-based network; downloadable web browser software for accessing and navigating the distributed computing platform; and downloadable software for an interface between the web browser software and the blockchain-based decentralized computing platform.

[0020] Aspects of the disclosure also relate to financial services, i.e., crypto-asset and related data transfer services featuring blockchain technology; crypto-asset and related data transfer services featuring blockchain technology, i.e., transfer of virtual currencies, virtual assets, digital currencies, digital assets, cryptocurrencies and crypto assets, and related data between blockchains; cross-blockchain and inter-blockchain transfer services involving virtual currencies, virtual assets, digital currencies, digital assets, cryptocurrencies and crypto assets, and related data; financial services, i.e., cross-blockchain and inter-blockchain transfer and communication services involving financial and related data; and financial information services provided online, i.e., providing information regarding financial transactions involving cryptocurrencies and crypto-assets; financial information services, i.e., providing a searchable online database of information regarding financial transactions involving cryptocurrencies and crypto-assets, including the status of transactions, the source and destination of the assets transacted, and the nature of the financial assets transacted.

[0021] Aspects of the disclosure also relate to communication services, i.e., inter-blockchain and cross-blockchain data communication; communication services, i.e., inter-blockchain and cross-blockchain communication of data representing virtual currencies, virtual assets, digital currencies, digital assets, cryptocurrencies, and cryptoassets; communication services, i.e., electronic transmission of data between blockchains and distributed ledgers; communication services, i.e., electronic transmission of data representing virtual currencies, virtual assets, digital currencies, digital assets, cryptocurrencies, and cryptoassets between blockchains and distributed ledgers. For example, some embodiments disclosed herein support the use of third-party hardware wallets to allow users to store / encrypt their private keys on the hardware wallet and sign transactions using the hardware wallet while using the system as an interface.

[0022] Aspects of the disclosure also include providing an internet-based service that enables inter-blockchain and cross-blockchain data communication; providing an internet-based service that enables the transfer of data from one blockchain or distributed ledger to another blockchain or distributed ledger; providing an internet-based service that enables inter-blockchain and cross-blockchain transfer of virtual currencies, virtual assets, digital currencies, digital assets, cryptocurrencies and crypto-assets; providing an internet-based service that enables the transfer of virtual currencies, virtual assets, digital currencies, digital assets, cryptocurrencies and crypto-assets from one blockchain or distributed ledger to another blockchain or distributed ledger; providing online, non-downloadable computer software for use as a cryptocurrency and digital asset wallet; providing online, non-downloadable computer software that enables users to send, receive, sell, lend, borrow and remit assets, read Quick Response (QR) codes, make purchases, manage contact information for other cryptocurrency and digital asset wallet users, manage user identities, authorize user identities, transfer crypto assets between blockchains and between accounts, private key management, signing transactions, staking tokens of value, creating non-fungible tokens, viewing non-fungible tokens, interacting with non-fungible tokens, acquiring non-fungible tokens, transacting with non-fungible tokens, creating smart contracts, creating subnets, accessing other cryptocurrency wallets, digital asset custody, accessing a remittance and settlement platform controlled by others and communicating with other cryptocurrency and digital asset wallet users;The present invention also relates to providing online, non-downloadable computer software for enabling transactions in a blockchain-based distributed computing environment, providing online, non-downloadable web browser software for accessing and navigating a blockchain-based network, providing online, non-downloadable web browser software for accessing and navigating a distributed computing platform, and providing online, non-downloadable software for interfacing between the web browser software and the blockchain-based distributed computing platform.

[0023] It will be appreciated that the above aspects are merely illustrative and that additional aspects may be included without departing from the scope of the disclosure.

[0024] According to aspects, the present disclosure may also be applied to subnets and support for subnets. Additional aspects include the ability to view, sign, and interact with the Bitcoin and Ethereum chains, among others.

[0025] (Example System Architecture) FIG. 1 illustrates a network architecture 100 supporting an application for managing blockchain assets, according to some embodiments. A server 130 and a database 152 are communicatively coupled to a client device 110 via a network 150. The server 130 may host an application running in the client device 110 for bridging assets and transactions across multiple blockchains. The client device 110 may be used by a user of the bridging application. The client device 110 may include a smartphone, a laptop, a mobile device, a palm device, and even a desktop. The network 150 may include, for example, any one or more of a local area network (LAN), a wide area network (WAN), the Internet, and the like. Furthermore, the network 150 may include any one or more of the following network topologies, including, but not limited to, a bus network, a star network, a ring network, a mesh network, a star-bus network, a tree or hierarchical network, and the like. Database 152 may store backup files containing tokens, cryptocurrencies, smart contracts, and financial data from blockchain asset transactions and smart contracts handled through the bridging application running in client device 110 and hosted by server 130. In addition, database 152 may contain encrypted keys that may be distributed to each, many, and all of the users of the bridging application.

[0026] FIG. 2 is a block diagram 200 illustrating the client device 210, the server 230, the components, engines, namely, blockchain engine 232 and portfolio management engine 234, and tools, namely, statistical tool 240, wallet tool 242, cryptographic tool 244, aggregator tool 246, and smart contract tool 248, used in the network architecture of FIG. 1, according to some embodiments. The client device 210 and the server 230 are communicatively coupled over a network 150 via respective communication modules 218-1 and 218-2 (hereinafter collectively referred to as "communication modules 218"). The communication module 218 is configured to interface with the network 150 to send and receive information, such as data, requests, responses, and commands, to other devices over the network 150. The communication module 218 can be, for example, a modem or an Ethernet card, and can include wireless hardware and software for wireless communication (e.g., via electromagnetic radiation, such as radio frequency - RF-, near field communication - NFC-, Wi-Fi, and Bluetooth wireless technologies). A user may interact with the client device 210 through input devices 214 and output devices 216. The input devices 214 may include a mouse, a keyboard, a pointer, a touch screen, a microphone, a joystick, a virtual joystick, etc. In some embodiments, the input devices 214 may include a camera, a microphone, and a sensor. The output devices 216 may be a screen display, a touch screen, a speaker, etc.

[0027] The client device 210 may include a memory 220-1 and a processor 212-1. The memory 220-1 may include an application 222 (e.g., a blockchain bridge application) configured to operate within the client device 210 and couple with the input device 214 and the output device 216. The application 222 may be downloaded by a user from a server 230 and may be hosted by the server 230. In some embodiments, the client device 210 is a desktop computer and the application 222 is a browser application with a blockchain bridge add-on as disclosed herein. In some embodiments, the client device 210 is a mobile phone and the application 222 is a mobile application. The execution of the application 222 may be controlled by the processor 212-1. In the application 222, the communication module 218-1 may transmit a user's dataset 225 to the server 230, which may return a dataset 227 to the client device 210. The data set 227 is transmitted from the server 230 to one or more users (e.g., different parties to a blockchain transaction or smart contract) via the communication module 218-2. Thus, the data sets 225 and 227 may include one or more cryptographic signatures that are verified by the client device 210 and the server 230.

[0028] In some embodiments, client device 210 is a desktop computer and application 222 is a browser installed in computer memory. In some embodiments, client device 210 is a mobile device (e.g., a mobile phone, a smart phone, etc.) and application 222 is a mobile application. In some embodiments, application 222 may be a web-based application that has been updated to incorporate most of the functionality of a browser extension or mobile application, along with new functionality not included in those products.

[0029] Thus, application 222 may include a browser extension that allows a user to bridge assets across one or more blockchains served by server 230. According to an aspect, any third-party browser application may be configured to include a browser extension as disclosed herein. Using the browser extension, a user can view their assets, send and receive assets, swap assets, and access decentralized applications "dApps" deployed on any one of several blockchain networks to which the user subscribes (e.g., buying, bridging, managing NFTs, and on-chain portfolio aggregation). The browser extension enhances these capabilities by allowing users to create and manage their personal information (through secret recovery phrases such as mnemonic phrases and seed phrases). When a decentralized application 222 wishes to conduct a transaction and write to the blockchain, the user gets a secure interface to double-check the transaction before approving or rejecting it. The application 222 browser extension works by injecting an object into the scripting context (e.g., JavaScript) of every website so that the decentralized application 222 can interact with wallet tools 242. This injected context acts as middleware between the wallet tool 242 and the application 222 .

[0030] The server 230 includes a memory 220-2, a processor 212-2, an API layer module 215, and a communication module 218-2. Hereinafter, the processors 212-1 and 212-2 and the memories 220-1 and 220-2 are collectively referred to as "processor 212" and "memory 220", respectively. The processor 212 is configured to execute instructions stored in the memory 220. In some embodiments, the memory 220-2 includes a blockchain engine 232 having a statistical tool 240, a wallet tool 242, and a cryptographic tool 244. The memory 220-2 may also include a portfolio management engine 234 having an aggregator tool 246 and a smart contract tool 248, and an account management engine 236 including an address book tool 249 and an account switching tool 250. The API layer module 215 handles the interface between the blockchain engine 232, the portfolio management engine 234, the account management engine 236, and the applications 222 in the client device 210. In some embodiments, the blockchain engine 232, the portfolio management engine 234, the tools included therein, and at least a portion of the training database 252 may be hosted on the server 230 or a different server accessible by the client device 210. A user of the client device 210 may access any of the assets included in one or more blockchain networks via the blockchain engine 232, the portfolio management engine 234, and the associated tools.

[0031] Statistical tools 240 perform statistical analysis and charts associated with blockchain transactions. In some embodiments, statistical tools 240 may determine a value associated with a given blockchain asset based on aggregated transactions on network 150.

[0032] Wallet tools 242 may enable fiat-to-crypto purchases and other paid transactions between blockchains. In some embodiments, wallet tools 242 integrate third-party payment applications to allow users to purchase blockchain assets with fiat, tokens, or cryptocurrencies within the same product experience. When a user activates a "Purchase" button, wallet tools 242 may be configured to launch the third-party application in a separate window hosted and controlled by a third-party server. The user can complete the transaction entirely within the third-party window. In some embodiments, wallet tools 242 may include tracking of anonymized usage of application features (user clicks, user actions, etc.). Data may be tracked through integration with third-party analytics platforms or statistics tools 240.

[0033] Cryptographic tools 244 provide hash and public key pairs to users and subscribers to access, modify, and conduct transactions with their assets in a blockchain network as disclosed herein. Transactions are signed using the hashes and encrypted keys in cryptographic tools 244.

[0034] The aggregator tool 246 is configured to aggregate historical data of a given user according to selected criteria (token value, contract terms and the like, locality, or demographics), over a period of time, across multiple blockchains, or across multiple users (anonymized) and multiple blockchains. The smart contract tool 248 is configured to handle smart contracts between multiple parties subscribed to the network or across different blockchains.

[0035] An address book tool 249 creates contacts to store frequently used addresses, and an account switching tool 250 creates and manages multiple addresses using the same recovery phrase.

[0036] 3A-3L are block diagrams illustrating modules 362, 364, 366, 368, 370, 372, 374, 376, 378, 380, and 382 in an application 300 (see application 222) for managing blockchain assets according to some embodiments.

[0037] The application 300 for bridging assets from multiple blockchain networks may be installed on a client device, a mobile device, or a server as disclosed herein. Thus, the bridge module 362 establishes a link between a user and two or more blockchains to which the user subscribes. The bridge module 362 allows the user to "transfer" his / her token from a first blockchain to a second blockchain. The transfer uses a smart contract on at least one blockchain. The user locks a first token in the first blockchain. The bridge module 362 then automatically mints a wrapped version of the same token on the second blockchain. The explorer module 364 allows search queries of items in one or more blockchains linked by the application 300. The wallet module 366 activates the wallet tools 242 (see FIG. 2). The browser extension module 368 provides the application 300 as an extension of a browser application already installed on the client device 210. The Defi module 370 allows users to interact with the decentralized finance protocol, such as swapping assets, lending or borrowing assets, or participating in other decentralized finance activities. The Portfolio module 372 allows users to review and manage a portfolio of assets across different blockchains. The Connectivity module 374 verifies security credentials and privileges to access the different blockchains to which a user subscribes. The Promotion / Event module 376 allows users to promote and generate events to sell, offer, and lend their assets across the network. The Profile module 378 stores, sets, and updates user preferences and other settings within the application 300.The developer center module 380 allows developers to provide tools and updates to all features of the application 300, the blockchain engine 232, and the portfolio management engine 234 (see FIG. 2), as well as the N-category vertical module 382, ​​which provides a secure sandbox environment to allow third parties to extend the functionality of the application while leveraging other internal application components.

[0038] Bridge module 362 establishes a link between two or more blockchains 363-1 (e.g., Ethereum) and 363-2 (e.g., Bitcoin), hereafter collectively referred to as "blockchain 363" in application 300. Bridge module 362 may charge a fee for transferring assets between blockchains 363. This fee is used to pay for access to blockchain 363. A user may use / interact with bridge module 362 in wallet module 366 (see wallet tools 242) to enable the user to effect such transfers.

[0039] The explorer function 364 includes a recent transaction block 365-1, which may include token transfers, token swaps, token staking or delegation, token lending or borrowing (including liquidity provisioning and yield farming), NFT minting, and validator node data bridging transactions and status. The explorer function 364 also includes a snowtrace block 365-2, a blockchain block 365-3, and an analysis block 365-4 (collectively referred to hereinafter as "explorer blocks 365").

[0040] The wallet module 366 includes a sending tool 367-1, a receiving tool 367-2, a transfer tool 367-3, a staking tool 367-4, an asset purchasing tool 367-5, and a hardware support tool 367-6. The wallet module 366 may include a fireblock / institutional custody tool 367-7 to enable third parties to implement "know your customer" (KYC) protocols on users, for example, for institutional use cases, and to facilitate multi-part computation or multi-signature configurations. Multi-signatures may involve a third-party wallet using "m of n" private keys (m≦n) to sign transactions (e.g., approve and send transactions). For example, if two of three keys need to be signed and each key is held by a different person, two of the three people need to approve the transaction. In some embodiments, the wallet module 366 is non-custodial and does not implement KYC protocols. In some embodiments, the wallet module 366 incorporates KYC for specific use cases such as institutional finance or regulated security offerings that require accredited investors. In some embodiments, the wallet module 366 enables crypto-to-crypto swaps integrated with third-party services to provide a gateway to those services. Some of these third-party services act as aggregators for decentralized exchanges. In some embodiments, the wallet 366 displays proposed swap rates (e.g., 100 PNG for 1 AVAX, to take an example of any two exemplary blockchain assets) that may be provided by the third-party service. The exchange rate may be updated at a preselected rate (e.g., every 45 seconds, etc.) based on market conditions (e.g., see bid / ask, liquidity, routing, statistics tools 240). In some embodiments, the third party may display multiple bids / offers. The application may receive a commission from the third-party service. The commission or fee may be a percentage of the transaction amount.In some embodiments, such details may be negotiated via a smart contract so that fees are automatically collected in real time. In some embodiments, the wallet function 366 allows a user to receive "airdrops" (e.g., deposits) from token issuers.

[0041] Browser extension 368 includes connection tool 369-1, transaction approval tool 369-2, and connection login tool 369-3 (collectively referred to herein as browser tools 369). When a user activates browser extension 368 from a browser (e.g., on a desktop device), the user can access any of the blockchains or subnets linked by the extension and interact with them and their assets via browser tools 369.

[0042] Defi module 370 handles games and similar applications. Tools and features include swap tool 371-1, borrow tool 371-2, lend tool 371-3, farm tool 371-4, staking tool 371-5, and watchlist tool 371-6 (collectively referred to as "tools 371" hereafter). By way of background, there are various types of blockchain games. Some represent certain game assets (e.g., swords) as NFTs. Others are "play-to-earn" games where users can earn tokens by taking certain actions in the game. Thus, game tokens typically take the form of either NFTs of game assets (e.g., swords that can be used in the game or sold to other users) or fungible tokens used in the game (e.g., resource tokens that allow users to take certain actions such as increasing the production of other assets or unlocking content in the game). Tools 371-1 through 371-4 may include an aggregator 346 that collects and aggregates anonymized data over selected time periods and selected groups of users. Staking tools 371-5 may include a validator 352 that validates stakes in the game.

[0043] The watchlist tool 371-6 may include features that support gaming tokens and related functionality, such as displaying an aggregated view of gaming token prices and performance 354 from the gaming token marketplace, allowing a user to browse an NFT library and potentially connect to the gaming token marketplace, selecting favorites 356, and displaying alerts 358 based on selected events.

[0044] The Defi module 370 may also display promotional and release information for new games and game tokens.

[0045] My Portfolio module 372 includes a portfolio aggregator 373-1 and a core culture 373-2. Portfolio aggregator 373-1 includes spot tools 390-1, leverage tools 390-2, pool tools 390-3, farm tools 390-4, borrow tools 390-5, and lend tools 390-6 (collectively referred to hereinafter as "tools 390"). Core culture 373-2 includes a gaming submodule 392 having social gaming tools 393-1, networked gaming tools 393-2, and play-and-earn tools 393-3. In addition, portfolio module 372 includes an NFT collectibles submodule 395, an aggregated marketplace submodule 397, and a fan tokens submodule 399. NFT collectibles submodule 395 allows a user to display their collectibles of NFTs in a wallet (see wallet module 366 and wallet tools 242). The aggregated marketplace submodule 397 performs aggregation of initial DEX offerings (IDOs) for game launches. In some embodiments, the submodule 397 displays an aggregated view of new IDOs by game protocols, such as sales of resource tokens that can be used in games. Using the portfolio module 372, users can send or receive NFTs, browse new game and game token launch announcements and IDO support, provide access to the aggregated NFT marketplace by integrating with the NFT marketplace, and provide access to the NFT marketplace.

[0046] The connectivity module 374 includes a browser extension tool 375-1, a MetaMask (MM) tool 375-2, a ledger tool 375-3, a wallet connection tool 375-4, and a coinbase tool 375-5 (collectively referred to herein as “connection tools 375”).

[0047] The promotion and event module 376 includes an IDO tool 377-1 (eg, future token activation), a directory tool 377-2, an activation tool 377-3, a promotion tool 377-4, a schedule tool 377-5, a media center tool 377-6, and a help tool 377-7 (collectively referred to hereinafter as "promotion tools 377").

[0048] The profile module 378 includes an authentication tool 379-1, a synchronization tool 379-2, a certificate tool (or store) 379-3, an NTT tool 379-4, a device tool 379-5, a key management tool 379-6, and an NFT tool 379-7 (collectively referred to below as "profile tools 379").

[0049] Developer center module 380 includes an IDE tool 381-1, a validator statistics tool 381-2, and an Open Zeppelin tool 381-3 for auditing smart contracts for security vulnerabilities (collectively referred to below as “developer tools 381”).

[0050] Vertical modules 382 include institutional finance tools 382-1, real estate tools 382-2, government tools 382-3, and gaming tools 382-4 (collectively referred to herein as "vertical tools 382"). Vertical modules 382 generally include functionality specific to different industry sectors.

[0051] Table 1 below illustrates several monetization schemes for each of the three application modalities (eg, web, mobile, and browser extension) disclosed herein. [Table 1]

[0052] 4A-4E illustrate screenshots 400A, 400B, 400C, 400D, and 400E (collectively referred to hereinafter as "screenshots 400") of a mobile application 422 for managing blockchain assets 412-1, 412-2, 412-3, 412-4, and 412-5 (collectively referred to hereinafter as "blockchain assets 412"), according to some embodiments. The application 422 can access assets 402 from different blockchains 414-1, 414-2, 414-3, 414-4, and 414-5 (collectively referred to hereinafter as "blockchains 414"). The application 422 may also include collectibles 416-1, 416-2, 416-3, and 416-4 (collectively referred to hereinafter as "collectibles 416"). Some screenshots 400 show an account balance 450.

[0053] Screenshot 400A illustrates a bridge module 466 for linking Bitcoin assets 412 with a blockchain 414-1.

[0054] Screenshot 400B illustrates a swap tool 471 that allows assets to be swapped between blockchains 414-1 and 414-2.

[0055] Screenshot 400C illustrates the use of a credit card or some other financial institution account and funds to effect a particular transaction via application 422. Portfolio management tools 434 include commands such as "send," "receive," "buy," "swap," and "bridge."

[0056] Screenshot 400D illustrates a self-custody feature for users to control their assets in application 422.

[0057] Screenshot 400E illustrates asset management features in application 422, including Bitcoin, NFTs, etc. In some embodiments, collectibles 416 may include digital designs (photos, videos, audio files - music, etc. -, GIF files, JPEGs, etc.) or even digital representations of artwork and other collectibles that a user owns and may want to trade with other users. The application allows for sending and receiving non-fungible tokens (e.g., ERC-721). It also displays aggregated floor prices from various marketplaces to the user and allows for selling assets. In some cases, the ERC-721 is linked to a real-world asset and can signify ownership of a portion of that asset.

[0058] 5A-5D illustrate screenshots 500A, 500B, 500C, and 500D (collectively referred to herein as “screenshots 500”) of asset transactions or “bridging” between multiple blockchains 514-1 and 514-2 (collectively referred to herein as “blockchains 514”) managed via a mobile application 522, according to some embodiments. A bridge module 566 links assets 512-1, 512-2, 512-3, 512-4, 512-5, and 512-6 (collectively referred to herein as “assets 512”) between the blockchains 514.

[0059] 5A illustrates the transfer of an asset 512-1 between blockchains 514-2 and 514-6. An administration field 534a indicates the status 535 of the transfer.

[0060] FIG. 5B illustrates transaction details 534b, such as fees and time involved in the transaction.

[0061] FIG. 5C is a screenshot of a failed bridge attempt showing a list of different blockchain assets 512 available.

[0062] FG5D illustrates a display of a user's account in application 522, where bridge tool 566 has not yet finished updating all information on blockchain 514-2. Account balance 550 is also illustrated.

[0063] FIG. 6 is a flow chart illustrating steps in a method 600 for transacting blockchain assets, according to some embodiments. In some embodiments, at least one or more of the steps of the method 600 may be performed by a client device, a server, or a database (see client devices 110 and 210, servers 130 and 230, databases 152 and 252, communication module 218, and network 150) communicatively coupled to one another over a network via a communication module. In addition, some of the steps may be performed by a processor circuit (see processor circuit 212 and memory circuit 220) executing instructions stored in a memory circuit as disclosed herein. In some embodiments, the memory circuit may include an application installed on the client device interfaced with a blockchain engine, portfolio management engine, or account management engine in the server via an API layer module (see application 222, blockchain engine 232, portfolio management engine 234, account management engine 236, and API layer module 215). The blockchain engine may include instructions from a statistical tool, a wallet tool, and a cryptography tool, the portfolio management engine may include instructions from an aggregator tool and a smart contract tool, and the account management engine may include instructions in an address book tool and an account switching tool as disclosed herein (see statistical tool 240, wallet tool 242, cryptography tool 244, aggregator tool 246, smart contract tool 248, address book tool 249, and account switching tool 250). In some embodiments, a method consistent with the present disclosure may include only one or more of the steps of method 600, which may be performed in a different sequence or order, simultaneously, quasi-simultaneously, or overlapping in time.

[0064] Step 602 includes providing, via an application interface, to a client device having a first user, a list of a plurality of assets in a first blockchain to which the first user subscribes. In some embodiments, step 602 includes receiving a request to send, receive, buy, or swap one or more user assets in the first blockchain. In some embodiments, step 602 includes receiving a request from the client device to bridge the first blockchain with a second blockchain to which the first user subscribes. In some embodiments, step 602 includes receiving a request to send, receive, buy, or swap one or more user assets between the first user and the second user.

[0065] Step 604 includes receiving, via the application interface, a request from a first user to conduct a transaction involving one or more of the assets in the first blockchain.

[0066] Step 606 includes determining a value of the transaction. In some embodiments, step 606 includes applying the value of the transaction to an account of the first user and providing a representation of the account to a wallet tool of an application running on the client device via the application interface. In some embodiments, the application interface is configured to link with a gaming application in the client device, and step 606 includes associating user performance in the gaming application with token values ​​in the first blockchain. In some embodiments, step 606 includes valuing non-fungible tokens in the account of the first user for the transaction.

[0067] Step 608 includes conducting the transaction when the first user accepts the value of the transaction. In some embodiments, step 608 includes providing a digital signature of the smart contract to the first user prior to conducting the transaction.

[0068] (Hardware Overview) 7 is a block diagram illustrating an example computer system 700 configured to host an application for managing blockchain assets, according to some embodiments. In certain aspects, the computer system 700 may be implemented using hardware or a combination of software and hardware in a dedicated server or integrated with another entity or distributed across multiple entities. The computer system 700 may include a desktop computer, a laptop computer, a tablet, a phablet, a smartphone, a feature phone, a server computer, or otherwise. The server computer may be located remotely in a data center or stored locally.

[0069] Computer system 700 includes a bus 708 or other communication mechanism for communicating information, and a processor 702 (e.g., processor 212) coupled with bus 708 for processing information. By way of example, computer system 700 may be implemented with one or more processors 702. Processor 702 may be a general purpose microprocessor, a microcontroller, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a programmable logic device (PLD), a controller, a state machine, gated logic, a discrete hardware component, or any other suitable entity capable of performing calculations or other manipulations of information.

[0070] In addition to hardware, computer system 700 may include code that creates an execution environment for computer programs of interest, for example code constituting a processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of these, including memory 704 (such as memory 220), for example random access memory (RAM), flash memory, read only memory (ROM), programmable read only memory (PROM), erasable PROM (EPROM), registers, a hard disk, a removable disk, a CD-ROM, a DVD, or any other suitable storage device coupled to bus 708 for storing information and instructions executed by processor 702. Processor 702 and memory 704 may be supplemented by, or incorporated in, special purpose logic circuitry.

[0071] The instructions may be stored in memory 704 and implemented in one or more computer program products, e.g., in one or more modules of computer program instructions encoded on a computer-readable medium for execution by or to control the operation of computer system 700, and according to any manner known to those skilled in the art, including, but not limited to, computer languages ​​such as data-oriented languages ​​(e.g., SQL, dBase), system languages ​​(e.g., C, Objective-C, C++, Assembly), architecture languages ​​(e.g., Java, .NET), and application languages ​​(e.g., PHP, Ruby, Perl, Python). The instructions may also be implemented in a computer language such as an array language, an aspect-oriented language, an assembly language, an authoring language, a command line interface language, a compiled language, a concurrent language, a curly brace language, a data flow language, a data structure language, a declarative language, an esoteric language, an extensible language, a fourth generation language, a functional language, an interactive mode language, an interpreted language, an iterative language, a list-based language, a little language, a logic-based language, a machine language, a macro language, a metaprogramming language, a multi-paradigm language, numerical analysis, a non-English based language, an object-oriented class-based language, an object-oriented prototype-based language, an offside rule language, a procedural language, a reflection language, a rule-based language, a scripting language, a stack-based language, a synchronization language, a syntax processing language, a visual language, a worth language, and an xml-based language. The memory 704 may also be used for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor 702.

[0072] A computer program as discussed herein does not necessarily correspond to a file in a file system. A program can be stored as part of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., a file that stores one or more modules, subprograms, or portions of code). A computer program can be deployed to run on one computer or on multiple computers located at one site or distributed across multiple sites and interconnected by a communications network. The processes and logic flows described herein can be performed by one or more programmable processors executing one or more computer programs to perform functions by manipulating input data and generating output.

[0073] The computer system 700 further includes a data storage device 706, such as a magnetic or optical disk, coupled with the bus 708 for storing information and instructions. The computer system 700 can be coupled to various devices via an input / output module 710. The input / output module 710 can be any input / output module. An exemplary input / output module 710 includes a data port, such as a USB port. The input / output module 710 is configured to connect to a communication module 712. An exemplary communication module 712 includes a networking interface card, such as an Ethernet card and a modem. In certain aspects, the input / output module 710 is configured to connect to multiple devices, such as input devices 714 and / or output devices 716. An exemplary input device 714 includes a keyboard and a pointing device, such as a mouse or trackball, by which a consumer can provide input to the computer system 700. Other types of input devices 714, such as a tactile input device, a visual input device, an audio input device, or a brain-computer interface device, can also be used to provide interaction with a consumer. For example, feedback provided to the consumer can be any form of sensory feedback, e.g., visual, auditory, or tactile feedback, and input from the consumer can be received in any form, including acoustic, speech, tactile, or brainwave input. Exemplary output devices 716 include display devices, such as LCD (liquid crystal display) monitors for displaying information to the consumer.

[0074] According to one aspect of the disclosure, the headset and client device 110 may be implemented using computer system 700, at least in part, in response to processor 702 executing one or more sequences of one or more instructions contained in memory 704. Such instructions may be read into memory 704 from another machine-readable medium, such as data storage device 706. Execution of the sequences of instructions contained in main memory 704 causes processor 702 to perform the process steps described herein. One or more processors of a multi-processing arrangement may also be employed to execute the sequences of instructions contained in memory 704. In alternative aspects, hard-wired circuitry may be used in place of or in combination with software instructions to implement various aspects of the disclosure. Thus, aspects of the disclosure are not limited to any specific combination of hardware circuitry and software.

[0075] Various aspects of the subject matter described herein may be implemented in a computing system, or any combination of one or more such back-end, middleware, or front-end components, including a back-end component, e.g., a data server, including a middleware component, e.g., an application server, or a front-end component, e.g., a client computer having a graphical consumer interface or web browser through which a consumer can interact with an implementation of the subject matter described herein. The components of the system may be interconnected by any form or medium of digital data communication, e.g., a communication network. The communication network may include, for example, any one or more of a LAN, a WAN, the Internet, and the like. Furthermore, the communication network may include, for example, any one or more of the following network topologies, including, but not limited to, a bus network, a star network, a ring network, a mesh network, a star-bus network, a tree or hierarchical network, and the like. The communication module may be, for example, a modem or an Ethernet card.

[0076] Computer system 700 may include clients and servers. Clients and servers are generally remote from each other and typically interact through a communications network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. Computer system 700 may be, for example, but not limited to, a desktop computer, a laptop computer, or a tablet computer. Computer system 700 may also be embedded in another device, for example, but not limited to, a mobile phone, a PDA, a mobile audio player, a Global Positioning System (GPS) receiver, a video game console, and / or a television set-top box.

[0077] The terms "machine-readable storage medium" or "computer-readable medium" as used herein refer to any medium or media that participates in providing instructions to the processor 702 for execution. Such media may take many forms, including but not limited to non-volatile media, volatile media, and transmission media. Non-volatile media include, for example, optical or magnetic disks, such as the data storage device 706. Volatile media include dynamic memory, such as the memory 704. Transmission media include coaxial cables, copper wire, and fiber optics, including the wires that form the bus 708. Common forms of machine-readable media include, for example, floppy disks, flexible disks, hard disks, magnetic tape, any other magnetic media, CD-ROMs, DVDs, any other optical media, punch cards, paper tape, any other physical media with a pattern of holes, RAM, PROM, EPROM, FLASH EPROM, any other memory chip or cartridge, or any other medium from which a computer can read. The machine-readable storage medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter that affects a machine-readable propagated signal, or a combination of one or more of these.

[0078] To illustrate the interchangeability of hardware and software, the various illustrative blocks, modules, components, methods, operations, instructions, and algorithms have been described generally in terms of their functionality. Whether such functionality is implemented as hardware, software, or a combination of hardware and software depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in various ways for each particular application.

[0079] As used herein, the phrase "at least one of" preceding a series of items with the term "and" or "or" to separate any of the items modifies the list as a whole, not each member (i.e., each item) of the list. The phrase "at least one of" does not require the selection of at least one item, rather the phrase allows for a meaning including any one of the items, and / or at least one of any combination of the items, and / or at least one of each of the items. By way of example, the phrase "at least one of A, B, or C" or "at least one of A, B, or C" refers to A only, B only, or C only, any combination of A, B, and C, and / or at least one of each of A, B, and C, respectively.

[0080] To the extent that terms such as "include," "have," and the like are used in the description or claims, such terms are intended to be inclusive in the same manner as the term "include" is interpreted as "include" when used as a transitional term in a claim. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

[0081] Reference to an element in the singular is not intended to mean "one and only one" unless specifically noted otherwise, but rather "one or more." All structural and functional equivalents to the elements of the various configurations described throughout this disclosure that are known or later known to those of skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the subject art. Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is expressly set forth in the description above. No element of a claim is to be construed under the provisions of the sixth paragraph of 35 U.S.C. 112 unless the element is expressly recited using the phrase "means for" or, in the case of a method, unless the element is recited using the phrase "step for."

[0082] Although the present specification contains many details, these should not be construed as limitations on the scope that may be claimed, but rather as descriptions of particular implementations of the subject matter. Certain features described herein in the context of separate embodiments may be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may be implemented separately in multiple embodiments or in any suitable subcombination. Furthermore, although features are described above as acting in a particular combination and are initially claimed as such, in some cases, one or more features from the claimed combination may be deleted from the combination, and the claimed combination may be subject to a subcombination or a variation of the subcombination.

[0083] Although the subject matter herein has been described in terms of certain aspects, other aspects may be implemented and are within the scope of the following claims. For example, although operations are depicted in the figures in a particular order, this should not be understood as requiring such operations to be performed in the particular order or sequence depicted, or that all illustrated operations must be performed to achieve desirable results. The acts described in the claims may be performed in a different order and still achieve desirable results. As an example, the processes depicted in the accompanying figures do not necessarily require the particular order or sequence depicted to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Furthermore, the separation of various system components in the aspects described above should not be understood as requiring such separation in all aspects, and it should be understood that the program components and systems described may generally be integrated in a single software product or packaged in multiple software products. Other variations are within the scope of the following claims.

[0084] The title, background, brief description of the drawings, abstract, and drawings of this disclosure are incorporated into this disclosure and are provided as illustrative examples of this disclosure, not as limiting descriptions. They are submitted with the understanding that they are not used to limit the claims or the spirit. In addition, in the detailed description, it is understood that the description provides illustrative examples, and that various features are grouped together in various implementations to streamline the disclosure. The method of disclosure should not be interpreted as reflecting an intention that the described subject matter requires more features than are expressly recited in each claim. Rather, as the claims reflect, the subject matter of the invention lies in less than all features of a single disclosed structure or operation. The claims are incorporated into the detailed description, with each claim standing on its own as a separate described subject matter.

[0085] The claims are not intended to be limited to the embodiments described herein, but are to be accorded full scope consistent with the language of the claims and encompass all legal equivalents. Nonetheless, none of the claims are intended to encompass subject matter that does not comply with the requirements of applicable patent law, and they should not be construed in such a manner.

Claims

1. 1. A system comprising: a cryptographic tool configured to generate a plurality of cryptographic hashes to create a sequence of encrypted data blocks storing a plurality of blockchain assets and transactions thereof for a plurality of users; a wallet tool configured to process user requests for asset transactions, including sending and receiving assets between two addresses on a blockchain; a statistical tool configured to provide analytical information regarding the asset transactions; a swap tool configured to swap blockchain assets; A bridge tool for accessing two or more blockchains; Purchasing tools to purchase blockchain assets using fiat currency; A blockchain engine including an aggregator tool configured to aggregate assets for each user and across one or more blockchains for provision to the statistical tool; a smart contract tool configured to provide a secure contract to two or more parties involved in the asset transaction; a portfolio management engine including: Address book tool, Account switching tool and an account management engine including:

2. 10. The system of claim 1, further comprising a database configured to store the blockchain assets, the asset transactions, and their associated smart contracts.

3. 2. The system of claim 1, wherein the blockchain assets include collectible items, at least one of the collectible items being a digital media file signed with a cryptographic hash.

4. 2. The system of claim 1, wherein the statistical tool is configured to generate a value for each blockchain asset based on aggregated transaction data on the blockchain asset.

5. 10. The system of claim 1, further comprising an application interface configured to link the blockchain engine and the portfolio management engine with a remote server hosting a web browser application.

6. 10. The system of claim 1, further comprising an application interface configured to link the blockchain engine and the portfolio management engine with an application installed on a mobile device to allow a user of the mobile device to conduct blockchain asset transactions.

7. 10. The system of claim 1, further comprising an application interface configured to link the blockchain engine and the portfolio management engine with a web application installed on a client device to allow a user of the client device to conduct blockchain asset transactions.

8. 10. The system of claim 1, further comprising an application interface configured to link the blockchain engine and the portfolio management engine with a gaming application installed on a client device to enable a user to play networked games and earn revenue.

9. 2. The system of claim 1, wherein the smart contract tool is configured to require each of the parties to digitally sign a smart contract and to store the executed contract in a database for public access.

10. 2. The system of claim 1 , wherein the portfolio management engine further comprises a developer module, the developer module configured to enable application developers to provide applications for performing operations on the blockchain assets.

11. 1. A computer-implemented method comprising: providing, via an application interface, to a client device having a first user, a list of a plurality of assets in a first blockchain to which the first user subscribes; receiving, via the application interface, a request from the first user to conduct a transaction involving one or more of the assets in the first blockchain; determining a value of the transaction; and performing the transaction when the first user and the second user accept the value of the transaction.

12. 12. The computer-implemented method of claim 11, further comprising receiving a request from the first user to bridge the first blockchain with a second blockchain to which the first user subscribes to an application interface.

13. 12. The computer-implemented method of claim 11, wherein receiving a request to conduct a transaction comprises receiving a request to send, receive, buy, or swap one or more user assets in the first blockchain with a second user.

14. 12. The computer-implemented method of claim 11, further comprising applying the value of the transaction to an account of the first user and providing, via the application interface, a representation of the account to a wallet tool within an application running on the client device.

15. 12. The computer-implemented method of claim 11, wherein the application interface is configured to link with a gaming application in the client device, and determining the transaction includes associating user performance in the gaming application with a token value in the first blockchain.

16. 12. The computer-implemented method of claim 11, wherein determining a value of the transaction includes valuing a non-fungible token in an account of the first user.

17. A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause a computer to perform a method, the method comprising: providing, via an application interface, to a client device having a first user, a list of a plurality of assets in a first blockchain to which the first user subscribes; receiving, via the application interface, a request from the first user to conduct a transaction involving one or more of the assets in the first blockchain; determining a value of the transaction; performing the transaction when the first user accepts the value of the transaction; applying the value of the transaction to an account of the first user and providing a representation of the account to a wallet tool within an application running on the client device via the application interface.

18. 20. The non-transitory computer-readable medium storing instructions of claim 17, wherein in the method, receiving a request to conduct a transaction comprises receiving a request to send, receive, buy, or swap one or more assets in the first blockchain.

19. 20. The non-transitory computer-readable medium storing instructions of claim 17, wherein the application interface is configured to link with a gaming application in the client device, and wherein the method, determining the transaction includes associating user performance in the gaming application with a token value in the first blockchain.

20. 20. The non-transitory computer-readable medium storing instructions of claim 17, the method further comprising providing a digital signature of a smart contract to the first user prior to conducting the transaction.

Images