aioha

Aioha

![](https://files.peakd.com/file/peakd-hive/aioha/23tRvj6GYqyeZxdD8Tj7yi6tDm1SHnqxui4eicve3mEAwXeiroU5CJtXQsL5BWa6hi4mz.png)

We are pleased to announce that Aioha may now be used to sign transactions through [Wax Typescript](https://gitlab.syncad.com/hive/wax/-/tree/develop/ts?ref_type=heads) library.

[Wax](https://gitlab.syncad.com/hive/wax) is a next generation feature rich library for Hive. It provides a developer-friendly interface to low level hived C++ functions in Python and Typescript.

# Why Aioha and Wax?

By using Aioha as transaction signer, you can integrate 5 authentication providers (and more incoming) into your Wax-powered Hive app and leverage Aioha features such as:

* Common interface across authentication providers
* Lightweight (56 KiB uncompressed, 15 KiB gzipped main bundle)
* Built-in login persistence
* Account switcher
* Framework specific provider and UI

# Usage

```js
import { createHiveChain } from '@hiveio/wax'
import { initAioha, WaxAiohaSigner } from '@aioha/aioha'

const aioha = initAioha()
const chain = await createHiveChain()
const tx = await chain.createTransaction()

// push some operations here...

await tx.sign(WaxAiohaSigner.for(aioha, 'active'))
await chain.broadcast(tx)
```

# Caveats

As of writing this, most if not all providers produce signatures using the legacy serialization method, while Wax prefers the newer method supported as of HF26 which saves 4 bytes per asset/NAI value in the transaction.

In addition, Aioha primarily uses the legacy transaction JSON format (array tuple of `["operation_name", {...body}]`) while Wax primarily uses the newer JSON format of `{"type": "operation_name", value: {...body}}`.

We plan to address them in the next major breaking release of Aioha.

# Other changes in v1.7

* Plaintext key provider fixes:
  - User class variable not set upon login
  - dhive endpoint not changed upon calling `setApi()`
* Fix user specified API not passed in when constructing transaction header to sign
* Fix `signTx()` result typing
* Move mostly unused JSON-RPC extensions to extras as optional import to reduce main bundle size

# Bundle sizes

|Bundle Name|Uncompressed Size|gzipped|
|-|-|-|
|bundle.js|56 KiB|15 KiB|
|ledger.bundle.js|146 KiB|44 KiB|
|hiveauth-aes.bundle.js|11.5 KiB|4.5 KiB|
|**Total**|**214 KiB**|**64 KiB**|

# Links

Landing page and docs: https://aioha.dev
Github: https://github.com/aioha-hive
NPM: https://www.npmjs.com/package/@aioha/aioha
Sting: https://chat.peakd.com/t/hive-169420/0

HiveDevs

Aioha as transaction signer for Wax

<center>![](https://files.peakd.com/file/peakd-hive/aioha/23tkoyQ8PScnYXaWtoLnJQHAkosfsMrX7nTQ8n62x8JYJ7q8v5z83cuToJJErov651Jdx.png)</center>

<hr>

Today we are announcing the release of Aioha [v1.6](https://github.com/aioha-hive/aioha/releases) for our core, React provider and UI libraries. This is a major non-breaking update from [v1.5](https://github.com/aioha-hive/aioha/releases/tag/v1.5.6).

# What's new?

#### New wallet request events

Starting in v1.6, the following events will be emitted whenever a request has been sent to the wallet provider that may require user action:

- `login_request`
- `memo_request`
- `sign_msg_request`
- `sign_tx_request`
- `hiveauth_challenge_request`
- `hiveauth_sign_request`

Apps may listen to these events by registering the event listener using `aioha.on(eventName, callback)`. Refer to the [docs](https://aioha.dev/docs/core/jsonrpc#events) for more info.

#### Multi-user authentication

Aioha now supports multiple concurrent wallet connections to different accounts which may be using a variety of providers and switch between them.

Adding another user is as simple as calling `aioha.login()` again for the other user, as long as the same user is not already connected. Switching to an already connected user may be done using `aioha.switchUser('user2')`, and disconnecting a currently inactive account may be done using `aioha.removeOtherLogin('user2')`.

These additional connections persists in the browser (when applicable) besides the active connected account.

#### Account discovery

This searches the selected wallet provider for available accounts. It may be used to save an extra step of typing in the username, and instead a list of discovered accounts will be listed for the user to select.

Account discovery is currently available on Ledger provider only at this moment. More details on usage may be found [here](https://aioha.dev/docs/core/usage#discover-accounts).

#### Other features

* Updated VSC functions for mainnet with Keychain specific implementation ([Usage](https://aioha.dev/docs/core/usage#vsc-call))
* Method to sign and broadcast a [hive-uri](https://gitlab.syncad.com/hive/hive-uri) encoded transaction ([Usage](https://aioha.dev/docs/core/usage#sign-and-broadcast-hive-uri))

# React UI

The ready-made [UI library](https://aioha.dev/docs/react/ui) has been updated to handle the necessary frontend logic to implement the new features.

|![](https://files.peakd.com/file/peakd-hive/aioha/23t79CFT3cNagdjuYz2C9RkZwP9kuAh6ReW62z7tDZ9giiJm1oZDMBMUyrhtkevErkfAh.png)|![](https://files.peakd.com/file/peakd-hive/aioha/23tGXT1xTUqURdrfE2t311iS1enXK6jZwVDsc5QKPNbd1JfBGZSif2UauLCr47FCwMs3A.png)|
|-|-|
|<center>**Account Switcher**</center>|<center>**Discovered Accounts**</center>|

Additionally, a new grid provider selection layout has been added as a built-in option that apps may choose to use.

|![](https://files.peakd.com/file/peakd-hive/aioha/23tGbvpULM1LjzBwtoZuz5JBDx1turCrJRCyQesTaPJkmURiHJWD4qkHdaoJHxm1HV58n.png)|![](https://files.peakd.com/file/peakd-hive/aioha/Eo1wxQn1JFgKXFZt61tSMPVDSHJfo6Fcw8eKv2YV3BcCKWj8DmcXPHCV87ByeapVPT8.png)|
|-|-|
|<center>**List View**</center>|<center>**(New) Grid View**</center>|

## Links
Landing page and docs: https://aioha.dev
Github: https://github.com/aioha-hive
NPM: https://www.npmjs.com/package/@aioha/aioha
Sting: https://chat.peakd.com/t/hive-134220/1


Aioha v1.6: Multi-User Authentication, Account Discovery and more!


<center>[![](https://ipfs-3speak.b-cdn.net/ipfs/bafybeicgln4pyzbafndwrx2jbstlrvqlrpbsbfxxhdjdxhwwjwmkqai2xe)](https://3speak.tv/watch?v=aioha/tyaufvzvfg)</center>

@techcoderx presents Aioha and how it improves developer experience when working on Hive web apps on-stage in HiveFest 9 in Split, Croatia.

## Links
Landing page and docs: https://aioha.dev
Github: https://github.com/aioha-hive
NPM: https://www.npmjs.com/package/@aioha/aioha
Sting: https://chat.peakd.com/t/hive-134220/1

Improving Hive DX with Aioha @ HiveFest 9 in Split

![](https://files.peakd.com/file/peakd-hive/aioha/23tbMYL9QDacQXPZXhTXxeWusrB9Hb5jVfMPwa4UA6KdLFynnSHySNfYcxYUCDFwsrSxp.png)

The first framework-specific libraries for Aioha are here. We are releasing two new libraries that makes working with Hive logins easier on React.

# [React Provider](https://www.npmjs.com/package/@aioha/react-provider)

Built upon [Aioha core](https://www.npmjs.com/package/@aioha/aioha), the Aioha React Provider supplies the hooks that you need in order to work with Aioha in your React app. This is most suited for those who want to work with a fully-customised login UI.

To use the provider, initialize Aioha and setup at the root of the application:

```tsx
import { initAioha } from '@aioha/aioha'
import { AiohaProvider } from '@aioha/react-provider'

// See options: https://aioha.dev/docs/core/usage#instantiation
const aioha = initAioha()

const App = () => {
  return (
    <AiohaProvider aioha={aioha}>
      <TheRestOfYourApplication />
    </AiohaProvider>
  )
}
```

You may then use the `useAioha()` hook anywhere within `AiohaProvider` in order to access Aioha core methods as well as methods that are hook-specific which works with React state variables.

# [React UI](https://www.npmjs.com/package/@aioha/react-ui)

A ready-made modal UI that uses (and supplies) the React provider above, it allows developers to quickly bootstrap an Aioha-powered Hive logins including the UI logic required. This includes provider selection, username input and HiveAuth login request QR code view.

|![](https://files.peakd.com/file/peakd-hive/aioha/23tGc17fudcnHvi4YPnPxhn5W4V1jMaaPphoWdkJifmustpePcvADuu8fj2JYbYXUMS2j.png)|![](https://files.peakd.com/file/peakd-hive/aioha/23uQnHrXmpRkewY59vUTdMMyswgncDVqRzj8HMSz9hXxtQCsYfmFWVh51PeZK2e9iwDSY.png)|
|-|-|
|![](https://files.peakd.com/file/peakd-hive/aioha/23t79CFT2B8xTB6gVRXryWKMaqemydQRSwo384ZyJ8KdYJ27RkyQutz1BKcNmMewV1wqn.png)|![Screenshot 2024-07-01 at 4.40.33 PM.png](https://files.peakd.com/file/peakd-hive/aioha/23tGaDwX7DxPBNxX57FCKSrJ7gfnc8gDsgrSJswPyovQhg2NxWiLFrxtccYNm29NZdftD.png)|

To use the React modal UI, setup the React Provider (importing `@aioha/react-ui` instead of `@aioha/react-provider`) at the root of the application, then use the `AiohaModal` component anywhere within `AiohaProvider`.

```tsx
import { useState } from 'react'
import { useAioha, AiohaModal } from '@aioha/react-ui'
import { KeyTypes } from '@aioha/aioha'

export const AiohaPage = () => {
  const [aiohaModalDisplayed, setAiohaModalDisplayed] = useState(false)
  const { user } = useAioha()
  return (
    <>
      <button type="button" onClick={() => setAiohaModalDisplayed(true)}>
        {user ?? (
          <div className="inline-flex">
            Connect Wallet
          </div>
        )}
      </button>
      <AiohaModal
        displayed={aiohaModalDisplayed}
        loginOptions={{
          msg: 'Hello World',
          keyType: KeyTypes.Posting
        }}
        onClose={setAiohaModalDisplayed}
      />
    </>
  )
}
```

For more details and up-to-date info on these libraries, please refer to the [documentation](https://aioha.dev/docs/category/react).

# What's next?

Other than aforementioned in the [initial announcement post](/hive-139531/@aioha/aioha-all-in-one-hive-authentication), the following will be worked on based on collected feedback.

### JSON-RPC API

Alongside the existing Aioha core JavaScript class methods, a standardized JSON-RPC API will be defined and implemented on Aioha in a way that is similar to [EIP-1193](https://eips.ethereum.org/EIPS/eip-1193). This also includes returning an error code on results on top of error messages (if any).

### Custom Login Providers

The ability to register custom login providers that are not currently built into Aioha core. These providers must extend the provider base class as defined [here](https://github.com/aioha-hive/aioha/blob/main/src/providers/provider.ts). An example usecase for this would be a plaintext private key login provider for backend apps.

### DID Methods

This extends the JSON-RPC API above to include [EIP-2844](https://eips.ethereum.org/EIPS/eip-2844) style DID methods which will be used by VSC.

### Other Frameworks

Besides React, Aioha will be adapted to other frameworks such as Vue and Angular to provide a similar developer experience like the Aioha React libraries.

# Links

Landing page and docs: https://aioha.dev
Github: https://github.com/aioha-hive
NPM: https://www.npmjs.com/package/@aioha/aioha
Sting: https://chat.peakd.com/t/hive-134220/1

Aioha React Libraries

![](https://aioha.dev/img/aioha-social-card.png)

Introducing Aioha, an all-in-one Hive authentication API that provides a common interface across different Hive login providers.

Working with Hive authentication has never been easier than before. With Aioha, developers can integrate Hive logins and interact with the network on their applications without having to go through the implementation of each individual provider. This way they can focus on the main functionality of the application.

Aioha is designed for use in browser contexts.

# Aioha Core

The main library that contains the inner workings of Aioha, is now [ready to use](https://www.npmjs.com/package/@aioha/aioha) on web apps. As of now, it currently supports 5 login providers:

* [Keychain](https://hive-keychain.com)
* [HiveAuth](https://hiveauth.com)
* [HiveSigner](https://hivesigner.com)
* [Ledger](https://hiveledger.io)
* [Peak Vault](https://vault.peakd.com)

In addition to providing the common programmatic interface, it also handles storing and loading persistence logins (aka "remember me") in-browser using local storage. Below is a very brief preview of Aioha in action:

```
import { initAioha, Asset, KeyTypes, Providers } from '@aioha/aioha'

// Instantiation. See usage docs for optional configs.
const aioha = initAioha()

// Get registered providers
console.log(aioha.getProviders())

// Get current logged in user and provider name
if (aioha.isLoggedIn()) {
  console.log(aioha.getCurrentUser(), aioha.getCurrentProvider())
}

// Login with provider
const login = await aioha.login(Providers.Keychain, 'hiveusername', {
  msg: 'Hello World',
  keyType: KeyTypes.Posting,
  hiveauth: {
    cbWait: (payload, evt) => {
      // display HiveAuth QR code using `payload` as data
    }
  }
})

// Transfer 1 HIVE using logged in provider
const xfer = await aioha.transfer('recipient', 1, Asset.HIVE, 'Transferred using Aioha with memo')

// Vote comment with 100% weight
const vote = await aioha.vote('author', 'permlink', 10000)

// Claim rewards
const rewardClaim = await aioha.claimRewards()
```

Refer to the [usage docs](https://aioha.dev/docs/category/core-api) for more details.

# What's next?

The release of Aioha core is just the beginning. There are more to come in the next few weeks leading up to HiveFest 9 in order to make the developer and user experience even better.

We may conduct polls on the below matters on @aioha account to collect insights on how we can improve the implementation on Aioha.

### Multi-Account Login

From the initial feedback received, it will be possible to be logged in to multiple accounts simultaneously and have the ability to switch between them with a single-line Aioha core method call.

### Anonymous Login

There are certain applications (such as [this one](https://vote.hive.uno)) that may not want to formally authenticate users, but be able to perform on-chain actions within a click of a button.

Anonymous logins on Aioha will work in a way where the user will not enter their username on the application, but instead select an account to sign the transaction on the provider itself (i.e. choosing the transaction sender on the Keychain popup). Note that this may not work with all available providers on Aioha.

### Ready Made UI

Besides Aioha core, these are framework-specific libraries that implements all the UI logic required for an Aioha-powered Hive login modal.

It handles checks of whether the relevant extensions are installed in the browser, the login flow (i.e. getting username input, showing HiveAuth QR code etc), and finally display them in a ready-made modal. This should also make adding the HiveSigner callback page as simple as importing a component and using it as the page in a route (within one line of code of course).

### One-Click Login

Other than improving developer (and hence user) experience of Hive logins, we will also be looking into the signup experience.

Recently, we have observed that signup providers that provide a [one-click login](/hive-125125/@ecency/introducing-1-click-login) experience have helped [one of the top Hivemind communities](https://peakd.com/c/hive-140169/created) to onboard many of their users. Although Aioha does not intent to be a signup provider itself, we plan to replicate the one-click login functionality through HiveSigner provider using framework-specific libraries aforementioned above.

# Links

Landing page and docs: https://aioha.dev
Github: https://github.com/aioha-hive
NPM: https://www.npmjs.com/package/@aioha/aioha
Sting: https://chat.peakd.com/t/hive-134220/1

Aioha (61)

Aioha as transaction signer for Wax

Aioha v1.6: Multi-User Authentication, Account Discovery and more!

Improving Hive DX with Aioha @ HiveFest 9 in Split

Aioha React Libraries

Aioha: All-In-One Hive Authentication