@kamil_nightly.near [Posted on DevHub](/devgovgigs.near/widget/Post?id=2554) ## Idea: Expand Nightly Connect on NEAR as an alternative for existing Wallet Selector and set of tools to kickstart growth of NEAR mobile apps. Hey, I'm Kamil from Nightly Wallet. We've been active in the NEAR ecosystem for over a year. During this time, we've identified a couple of wallet-related problems that are affecting the overall growth of the NEAR ecosystem. In this topic, I would like to bring your attention to these issues and the potential solutions we could offer and get your opinion about it. # The Vision Building dApps is complicated and time-consuming. Therefore, one of the missions of every blockchain should be to maximize the facilitation of this process, making it as fast and straightforward as possible, thereby effectively lowering the entry barrier for new applications. Otherwise many potential new applications will choose a different blockchain instead of NEAR. Also, developing current applications will be challenging and inefficient, which is a crucial factor in blockchain growth. Currently, those building on NEAR must create and maintain many repetitive but necessary functions themselves, wasting a tremendous amount of time. There are also processes that, due to their complexity, inadvertently slow down the development of applications. Therefore, we commit to delivering solutions that: * Save dApp builder time * Enable a step forward in the development of mobile applications * Facilitate the development of wallets We will achieve this by providing and subsequently maintaining tools that address the problems faced by all applications currently present on NEAR. These tools will additionally provide a foundation for building on it for mobile applications and automate tasks that have taken time. # Problems **The simple process of adding new wallets to the dApp generates too many problems and takes too much time.** This affects both wallet developers and dApp builders. Wallets lacking integrations with dApps struggle to grow. While the NEAR Wallet Selector was intended to solve this problem, it has proven ineffective. Consequently, for dApps, this theoretically quick process becomes problematic due to the need for each dApp to write its own implementation for every wallet, consuming their time and creating unnecessary conflicts between wallets. **NEAR is not ready for mobile adoption** Mobile is the future, and NEAR it's not ready for that future yet. Establishing a connection between mobile apps is challenging, even though it is one of the most basic operations. This is a key factor hindering the growth of mobile apps on NEAR— the absence of essential tools that projects could utilize instead of creating from scratch. Currently, most mobile applications on NEAR are wallets, and the impact of this issue is evident in them. For instance, HERE Wallet or Sweet Coin addressed it well but had to develop the solution from scratch and now must maintain it. Any potential new mobile app will face the same challenge, significantly raising the entry barrier. **Every change in the wallet requires action from the selector and the dApps to take effect.** Every, even the slightest change in any wallet, requires an update of that wallet in the selector and dApps to begin functioning. This involves additional individuals, often unnecessarily prolonging the process. It also frequently happens that some changes conflict with others, further extending or sometimes completely halting the process. **Maintenance of both, the Wallets and Wallet Selector is tough.** Maintaining the Wallet Selector is challenging, and it will only get more difficult. As mentioned above, it requires constant updates. Due to the lack of consistency in the library used across wallets, the Selector must support multiple versions of one library, creating numerous issues. The maintenance of wallets is also unnecessarily complicated by the need to maintain custom packages for the Wallet Selector. # Solutions The creation of a NEAR Wallet Standard and the expansion of Nightly Connect on NEAR will address each of these problems through the following solutions: **An automated and fully permissionless process for adding new wallets** An automated and fully permissionless process for adding new wallets, Nightly Connect aggregates every wallet that complies with the Wallet Standard in a fully automated and permissionless way, without any required action from the dApp's side. When the wallet updates to any new version, it will be fully automatically available in every dApp that has integrated Nightly Connect. And all of this without interaction with any dependencies. This will not only ensure a lack of conflicts between them but also significantly facilitate maintaining process. **NEAR Wallet Standard** The NEAR Wallet Standard will enhance the standardization and cohesion of wallet architectures. This will simplify and expedite the maintenance and further development for everyone in the NEAR ecosystem. **Ready-to-go tool to handle every way of connections** Nightly Connect will handle every form of connection, whether through deep links or QR codes, and then help you manage additional features like push notifications or enhanced sessions, thus improving the overall mobile user experience. This tool will be open and tailored for every kind of app or wallet, allowing mobile builders to focus on developing more critical aspects of their applications. # Nightly Connect Nightly Connect serves as an automated, fully permissionless Wallet Selector and a tool for handling a connection between desktop and mobile or mobile and mobile NEAR apps. While the default option aggregates every standard-compliant wallet, we also empower dApps to filter through the wallet list and only service the chosen ones. Nightly Connect also establishes a connection in two ways: by scanning a QR Code and through deep links. The architecture of Nightly Connect allows it to be used by any application after implementing a few lines of our code. In addition to servicing connections, Nightly Connect provides support for push notifications, persistent sessions, and allows dApps to edit parameters like the session duration. We also allow everyone to self-host of the whole service which makes it indepented from us. Moreover, applications can freely modify the Nightly Connect Model UI in a simple and fast manner using components prepared by us. Thanks to the NEAR Wallet Standard and the ability to inject wallets into Nightly Connect, this tool has no form of contact with wallet dependencies. This prevents any conflicts between them and makes maintenance a much more pleasant experience. Nightly Connect could also become a valuable component of the BOS, handling connections with Sui, Solana, or Polkadot wallets, as we already support these chains. You can test it using one of our demos on Sui, Solana or Aleph Zero that are available [here](https://example.connect.nightly.app/) Also [here](https://twitter.com/Nightly_app/status/1729891019133710478) you can check the demo videos. # Nightly Connect vs NEAR Wallet Selector The assumptions of the NEAR Wallet Selector were good, and indeed, it improved some issues. However, due to its architecture, it is no longer able to address certain troublesome issues. The major problems with the Wallet Selector that we mentioned above include: * The need to maintain packages for Wallet Selector by wallets * The requirement for an update of Wallet Selector after every minimal change in any wallet * Complex and overly large configuration causing conflicts * Unnecessary process of adding a new wallet to the Selector, requiring actions from those maintaining it, and often changes in the Selector itself. Nightly Connect resolves all of these issues. # Developer DAO In the NDC v1 Priorities document, there was a recommendation regarding Public Good Developers Initiatives. Our solutions perfectly fit this definition by providing fundamental infrastructure that every NEAR mobile app can incorporate into their projects. We strongly believe that by delivering this, we will help the entire NEAR Ecosystem take a step forward in mobile development. Due to the overall architecture of our solutions, they are not only flexible and permissionless but can also work totally independently from us. Nightly Connect Could be a great compontent of the BOS, that will handle a connection with Sui, Solana or Polkadot wallets as we're already supporting these chains # NEAR Wallet Standard Standards like this work well on Solana and Sui. Even Ethereum has something similar through [EIP-6963](https://eips.ethereum.org/EIPS/eip-6963). We will construct an interface and injection model. After its implementation, wallets will automatically inject themselves into Nightly Connect, granting them access to every app that has implemented Nightly Connect. Furthermore, this standard will promote more consistent code across wallets, reducing unnecessary code, setups, and conflicts. The API will be deterministic, and every contributor to the standard will be able to influence how it will look.