ArweaveKit Docs
  • ArweaveKit
    • Introduction
  • 🔐Wallets
    • Introduction to Wallets
    • Create Wallet
    • Get Wallet Address
    • Get Wallet Balance
    • Wallet Plugins
  • 💳ARWEAVE WALLET KIT
    • Introduction to Arweave Wallet Kit
    • Setup
    • Connect Button
    • Hooks
    • Customization
  • 🏦Transactions
    • Introduction to Transactions
    • Create Transaction
    • Sign Transaction
    • Post Transaction
    • Get Transaction Status
    • Get Transaction
    • Create and Post Transaction with Othent
    • Transaction Plugins
  • 📄SMART CONTRACTS
    • Introduction to Smart Contracts
    • Create Contract
    • Write Contract
    • Read Contract State
    • View Contract State
    • Write Contract with Othent
    • Read Contract with Othent
    • Smart Contract Plugins
  • ✅AUTH
    • Introduction to Auth
    • Connect
    • Disconnect
    • Get Active Address
    • Get Permissions
    • Get Wallet Names
    • Get All Addresses
    • Get Active Public Key
    • Is Installed
    • Log In with Othent
    • Log Out with Othent
    • Get User Details with Othent
    • Auth Plugins
  • 🔐Encryption
    • Introduction to Encryption
    • Encrypt Data with AES
    • Decrypt Data with AES
    • Encrypt AES Key with RSA
    • Decrypt AES Key with RSA
    • Encryption Plugins
  • 🌐GRAPHQL
    • Introduction to GraphQL
    • Query All Arweave Transactions
    • Query Arweave Data
    • Query Arweave Transactions
    • GraphQL Plugins
  • 🗺️RoadMap
    • Features
  • 📘REFERENCES
    • ArweaveKit in Browser Environments
  • 🛠️SUPPORTING TOOLS
    • Arweave StarterKit
Powered by GitBook
On this page
  • Authentication on Arweave
  • Authentication from a development perspective
  • Libraries used
  • Auth based functions

Was this helpful?

  1. AUTH

Introduction to Auth

Introduction to authentication on Arweave

PreviousSmart Contract PluginsNextConnect

Last updated 2 months ago

Was this helpful?

Authentication on Arweave

To interact with applications, a user must be authenticated and the application in-turn must have permissions from the user to interact with the network on the users behalf.

Additionally, every interaction (transaction) on the network has a unique signature. The signature is a hash of the various input parameters as well as the users key that helps authenticate the transaction and point it to a particular user.

Authentication from a development perspective

Developers need to create user friendly tools and interfaces that verify user wallet connection to applications, use wallet addressed and request permissions from users to perform actions on their behalf.

Libraries used

The functions associated with authentication leverage the following libraries:

Currently the library only supports the ArConnect extension for compatibility reasons. Support for additional browser based wallets will be added in the future.

Auth based functions

In this section, we will look at the following features:

  • connecting a web wallet

  • disconnecting a web wallet

  • getting address of connected web wallet

  • getting permissions from user to use connected web wallet

  • getting names associated with wallet addresses

  • getting all addresses from web wallet extension

  • getting a users active public key from web wallet

  • checking if web wallet is installed

  • connecting to applications using email ids

  • disconnecting email ids from applications

  • fetching user details of

✅
ArConnect
Othent