Developers shouldn\u2019t be working for the wallet; the wallet should be working for the developer. \u2013 Jack Liu at Coingeek London 2020. https:\/\/www.youtube.com\/watch?v3U4bxrNG1f8&t726 BSVABI is a specification proposal from Dean Little of Bitping that any existing or future wallet could implement in order to streamline access to Bitcoin applications. Identity A simple structure is proposed for IDs\u2014simply broadcast a transaction with an OP_RETURN output containing a JSON object of two public keys that act as owner and active keys. Inb4 \u2018Keys are not identity!\u2019\u2014this transaction only serves to establish an identity; since the ID is embedded in a Bitcoin transaction, it can be validated on-chain via an SPV proof. An interesting concept is the ability to apply Proof of Work to your identity. The transaction ID of possible owner\/active key permutations can be hashed repeatedly to achieve a certain number of leading zeroes, or a magic number prefix such as \u201821e8\u2019. Imagine a service provider who only allows users to access if they have at least six leading zeroes in their identity. This barrier to entry can be effective against fake accounts that infect most popular platforms we use today. https:\/\/twitter.com\/deanmlittle\/status\/1232446341206274050?s20 The active key\u2019s purpose is to link to wallets such that they can perform the following six standard functions on a user\u2019s behalf: -\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Sign -\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Login -\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Encrypt -\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Decrypt -\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Verify -\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Send (money) Almost all existing Bitcoin SV applications require implementations of these functions today. The segregation of owner and active keys intends to remove the need to trust a wallet or platform with ownership of their identity yet can prove they own the ID by signing with the owner key at any time. Bitcoin service providers can easily extend this open protocol to account for subsequent actions and supplemental information of Metalink IDs to further build reputation. As the Bitcoin whitepaper states, today\u2019s services must harass users for lots of sensitive information, partially due to the lack of a single source of truth representing their identity. With this solution where services begin to attest for users over time, a chain of digital trust can be formed and publicly verified. ABI implications for wallets The ABI spec is fairly technical and can be deeply explored here, but its goal is to streamline communication between applications and wallets by establishing a schema on-chain. The schema can then be imported by referencing its Transaction ID, allowing the wallet to perform any additional functions specified such as \u2018Like\u2019 or \u2018Post\u2019 in addition to the six standard functions referenced above can be leveraged. Currently, the existing wallets like Money Button, RelayX and DotWallet rely on legacy Internet protocols such as HTTPS, DNS and OAuth to validate user access to other Bitcoin platforms. Source: Twetch With this proposal, wallets would leverage the superior security model of Bitcoin, rather than these duct-taped, band-aid solutions created to address the poor security model of the Internet. In the timestamped link below, Andrew Desantis describes the fate for future platforms not on par with Bitcoin\u2019s security model: https:\/\/www.youtube.com\/watch?vGH6p3WE3v8Q&t5087 An added benefit of wallets adhering to something like Metalink is streamlined application development. If developers building apps can have these common, standard functions abstracted away for them, they can focus their time on the unique features of their platform, giving builders on Bitcoin SV a huge advantage in bringing a product to market. Discussion and recommendations to the proposal are encouraged, so please check out the proposal at BSVABI.org and submit feedback via a pull request on its GitHub.