@nadohq/mobile-client

HTTP client for the Nado mobile service API. Manages usernames, public profile lookups, the global trade feed, the follower/following graph, privacy settings, and push notification devices/preferences, using EIP-712 + msgpack signed authentication.

Full SDK Documentation

Usage

import { MobileClient, MOBILE_CLIENT_ENDPOINTS } from '@nadohq/mobile-client';
import { createWalletClient, http } from 'viem';
import { privateKeyToAccount } from 'viem/accounts';
import { ink } from 'viem/chains';

const walletClient = createWalletClient({
  account: privateKeyToAccount('0x...'),
  chain: ink,
  transport: http(),
});

const mobile = new MobileClient({
  url: MOBILE_CLIENT_ENDPOINTS.inkMainnet,
  walletClient,
});

// Unsigned public lookups
const availability = await mobile.getUsernameAvailability({ displayName: 'Alice.One' });
const [profile] = await mobile.getProfiles({
  subaccounts: [{ subaccountOwner: '0x...', subaccountName: 'default' }],
  include: { followCounts: true },
});

// Signed operations
await mobile.setUsername({
  subaccountOwner: walletClient.account.address,
  subaccountName: 'default',
  chainId: ink.id,
  verifyingAddr: '0x...',
  displayName: 'Alice.One',
});

API Surface

Public Queries

getUsernameAvailability, getProfiles, getFeed, getNotificationPreferences, getRegisteredWallet.

getProfiles is the only profile route: it batches up to 25 subaccounts, returns them in the requested order, and carries follower totals (include.followCounts) and a follow summary (include.followSummary.viewAs) as opt-in includes, so use it for a single subaccount too. Because it is unsigned, that viewAs is an unauthenticated claim. The backend still serves the older singular profile request for compatibility, but it returns base fields only and costs more weight than the batched equivalent, so the SDK does not expose it.

Public Executes

unregisterExpoToken, updateNotificationPreferences. These are authenticated by possession of an active Expo push token rather than a wallet signature, so they still work at logout when a signature may be unobtainable.

Signed Queries

getFollowers, getFollowing. Both follow list reads are signed because the rows carry an isFollowing relative to the signing Viewer, which has to be proven rather than claimed — including on each paginated request.

Signed Executes

setUsername, setPrivateMode, registerExpoToken, setFollow.

Linked Signers

The mobile client supports linked signers for delegated transaction signing:

mobile.setLinkedSigner(linkedSignerWalletClient);

License

ISC