3.120 @gen3labs/futurepass-signer At a glance What it is Provides a signer interface with common methods for signing messages, transactions and extrinsics. Where it sits Part III — Reference · Chapter 3.120 Covers Technical notes · Upstream README Package @gen3labs/futurepass-signer
| At a glance | |
|---|---|
| What it is | Provides a signer interface with common methods for signing messages, transactions and extrinsics. |
| Where it sits | Part III — Reference · Chapter 3.120 |
| Covers | Technical notes · Upstream README |
| Package | @gen3labs/futurepass-signer |
Community fork of
@futureverse/signer.
Community fork of a Futureverse package
Published under @gen3labs by markibanez in April 2026 as a fork of the matching @futureverse/* package; the surface mirrors the upstream one-for-one. The sign-in forks default to the gen3labs-hosted issuer futurepass.gen3labs.tech and signer fpsigner.gen3labs.tech. Those did not answer, nor did the Futureverse services they re-host (checked 2026-10-10): signer.pass.online and signer.futureverse.app answer HTTP 402; login.futureverse.com, auth.futureverse.app and pass-api.futureverse.app do not resolve; futurepass.gen3labs.tech and fpsigner.gen3labs.tech refuse connections. FuturePass’s login pages answered on the same check. A sign-in through the forks’ default hosts cannot complete. New apps sign users in with their own wallet — any EIP-6963 wallet app, MetaMask preferred — and talk to the chain through @therootnetwork/api and @therootnetwork/evm. If you have a FuturePass, you can move what’s in it to your wallet at https://futurepass.trn.codeology.co.nz/wallet/futurepass.
- Version
1.8.0- Published
- 2026-04-28
- License
- n/a
- Status
fork-active- npm
- https://www.npmjs.com/package/@gen3labs/futurepass-signer
- Types
./index.d.ts- Maintainers
- markibanez
- Depends on
@polkadot/api·@polkadot/keyring·@polkadot/util·@polkadot/util-crypto·@polkadot/types·blakejs·ripple-binary-codec·ripple-keypairs·viem·xrpl·xumm·@gen3labs/futurepass-signer-core- Recent versions
1.8.0
3.120.1 Technical notes
3.120.1.1 Why use it
Existing code moved to the fork. Its custodial path goes through fpsigner.gen3labs.tech, which refuses connections (checked 2026-10-10).
3.120.1.2 When to skip it
Any new project: the user’s own wallet signs.
3.120.1.3 Pairs with
@gen3labs/futurepass-signer-core— shared interface
3.120.1.4 Alternatives
@futureverse/signer(fv-published) —
3.120.2 Upstream README
3.120.2.1 Futureverse Signer
Provides a signer interface with common methods for signing messages, transactions and extrinsics.
Installation
NPM:
bash
npm install @futureverse/signer --saveYarn:
bash
yarn add @futureverse/signerUsage
Wagmi useFutureverseSigner Hook
The example below shows how to create a hook (useFutureverseSigner) to get the signer interface from wagmi wallet client.
typescript
import { clientToSigner } from '@futureverse/signer';
import { useMemo } from 'react';
import { type Connector, useWalletClient } from 'wagmi';
/** Action to convert a Viem Client to a Futureverse Signer. */
export function useFutureverseSigner({ chainId, connector }: { chainId?: number; connector?: Connector } = {}) {
const { data: client } = useWalletClient({ chainId, connector });
return useMemo(() => (client ? clientToSigner(client) : undefined), [client]);
}Signing a message
typescript
import { useCallback } from 'react';
import { useFutureverseSigner } from './useFutureverseSigner';
function MessageSignerDemo() {
const { signer } = useFutureverseSigner();
const signExtrinsic = useCallback(async () => {
if (!signer) return;
const message = 'message to sign';
return await signer.signMessage(message);
}, [signer]);
// Your UI code to call signExtrinsic
return <></>;
}Signing a Root Network extrinsic
typescript
import { userSession } from '@futureverse/auth';
import { useTrnApi } from '@futureverse/transact-react';
import { useCallback } from 'react';
import { useFutureverseSigner } from './useFutureverseSigner';
function ExtrinsicSignerDemo() {
const { userSession } = useAuth();
const { trnApi } = useTrnApi();
const { signer } = useFutureverseSigner();
const signExtrinsic = useCallback(async () => {
if (!signer) return;
if (!trnApi) return;
if (!userSession?.eoa) return;
const collectionId = '<your collection id>';
const numberOfTokens = 1; // How many tokens to mint
const address = 'FuturePass or address to mint to';
const extrinsic = trnApi.tx.nft.mint(collectionId, numberOfTokens, address);
return await signer.signExtrinsic(trnApi, extrinsic, userSession.eoa);
}, [signer]);
// Your UI code to call signExtrinsic
return <></>;
}Source: https://www.npmjs.com/package/@gen3labs/futurepass-signer · captured 2026-10-10
Associated docs
Where else you might go from here. Following one is optional — this chapter stands without them.
- SDKs & Packages
Part of— Every public @therootnetwork/*, @futureverse/*, and @gen3labs/* npm package on TRN, with status, why-to-use, and full per-package technical notes.- @futureverse/signer
See also— Provides a signer interface with common methods for signing messages, transactions and extrinsics.- @gen3labs/futurepass-signer-core
See also— @gen3labs/futurepass-signer-core- @gen3labs/futurepass-transact
See also— An API to help facilitate transactions on The Root Network- @therootnetwork/api
See also— A utility package that complements the @polkadot/api to connect and interact with the Root Network node.- @therootnetwork/evm
See also— A utility package that simplifies EVM development on The Root Network.- Back matter — read in order
See also— The whole of Back matter as one continuous page, reprinted from its chapters without change.- Contents
See also— Every chapter in this book, each with the one line that tells you what you get by reading it.