Migration playbook — off Futureverse-hosted infra

TL;DR. Futureverse is in winddown. The npm packages they published still work today, but the hosted services they call are at risk. Good news: gen3labs has re-hosted the FuturePass identity stack — the OIDC issuer, the signer service, and a "manage clients" console — under their own domains. The auth flow keeps working, you just point your client at futurepass.gen3labs.tech instead of auth.futureverse.app. This page maps every fv-hosted service to its post-winddown replacement.

What's actually at risk (and what's not)

Hosted service	Used by	Replacement
auth.futureverse.app (OIDC issuer)	@futureverse/auth*, @futureverse/wagmi-connectors	Re-hosted by gen3labs at https://futurepass.gen3labs.tech. Use @gen3labs/futurepass-auth and set authorizationURL: 'https://futurepass.gen3labs.tech' (it’s the package default).
login.passonline.cloud (Pass login UI)	@futureverse/auth*	Hosted alongside the gen3labs issuer.
pass-api.futureverse.app (Pass account API)	@futureverse/auth*	Same — folded into the gen3labs issuer service.
signer.futureverse.app (custodial signer)	@futureverse/signer, custodial flows	Re-hosted at https://fpsigner.gen3labs.tech. Set signerURL: 'https://fpsigner.gen3labs.tech'.
Manage Clients Console	App developers needing a client_id	https://futurepass.gen3labs.tech/manageclients — register OAuth2 clients here.
ar-api.futureverse.app/graphql (Asset Register)	@futureverse/asset-register*, @futureverse/swappable-viewer-react, @futureverse/artm	Not re-hosted as of capture. The schema + ARTM message format are open — anyone could host a replacement, but no community-run AR exists yet. On-chain ownership is still queryable directly via the nft pallet / ERC-721 precompile without AR.
seekers.sylo.io (Sylo node network)	@futureverse/sylo-*	Sylo nodes are a separate operator network; check Sylo's status independently of Futureverse.
TRN node RPC (root.rootnet.live, porcini.rootnet.app)	All of the above + @therootnetwork/api, @therootnetwork/evm	Operated by validator partners. Lowest-risk dependency — you can also run your own node.

After the gen3labs re-hosting:

• Pass auth (OAuth2 + custodial sign-in via Google/email/Facebook/X/TikTok) keeps working if you switch to the @gen3labs/* packages.
• Asset Register is the only piece that has no community replacement yet. Treat it as optional — fall back to on-chain ownership lookups for anything load-bearing.
• TRN itself is unaffected. RPC, pallets, precompiles, FuturePass on-chain accounts all keep running.

Direct replacement table

If you depend on	Replace with	Notes
@futureverse/auth	@gen3labs/futurepass-auth	Same surface. Routes through the gen3labs-hosted issuer (futurepass.gen3labs.tech) by default — Pass / Google / email / Facebook / X / TikTok sign-in all keep working.
@futureverse/auth-react	@gen3labs/futurepass-auth-react	Drop-in.
@futureverse/auth-ui	@gen3labs/futurepass-auth-ui	Drop-in.
@futureverse/auth-core	@gen3labs/futurepass-auth-core	Transitive.
@futureverse/wagmi-connectors	@gen3labs/futurepass-wagmi-connectors	Drop-in.
@futureverse/signer	@gen3labs/futurepass-signer	Drop-in.
@futureverse/signer-core	@gen3labs/futurepass-signer-core	Transitive.
@futureverse/transact	@gen3labs/futurepass-transact	Drop-in. Composes pallets directly — least exposed to fv shutdown.
@futureverse/auth-react-native	no fork	Stay on fv until a fork lands, or roll your own with @gen3labs/futurepass-auth + RN bindings.
@futureverse/next-auth	no fork	Pure Auth.js provider — easy to fork yourself (it's ~150 LOC).
@futureverse/transact-react	no fork	Thin wrapper — re-implement against @gen3labs/futurepass-transact.
@futureverse/oidc-client	@gen3labs/futurepass-auth	Already deprecated upstream.
@futureverse/wallet-signer-etherjs	viem + @therootnetwork/evm	Move off ethers v5.
@futureverse/evm	@therootnetwork/evm	Identical surface, different scope.
@futureverse/asset-register	no fork	If/when AR API goes down: query on-chain ownership via nft pallet / ERC-721 precompile; you lose link history.
@futureverse/asset-register-react	no fork	As above.
@futureverse/swappable-viewer-react	no fork	Visualisation only — replace with bespoke UI on top of nft pallet queries.
@futureverse/artm	no fork	Standalone codec — keep using until a self-hostable AR exists.
@futureverse/sylo-*	Track Sylo's own roadmap	Sylo Foundation operates separately.
@futureverse/mint-sdk(-react)	NFT precompile (ERC-721) directly	Most apps don't need a hosted minting service.
@futureverse/component-library	Replace with your design system	Empty README, no public docs.
@futureverse/react-unity-viewer	react-unity-webgl	Generic alternative.

Concrete migration: a wagmi + Pass app

- import { FutureverseAuthProvider } from '@futureverse/auth-react';
- import { futurepassConnector }    from '@futureverse/wagmi-connectors';
+ import { FutureverseAuthProvider } from '@gen3labs/futurepass-auth-react';
+ import { futurepassConnector }    from '@gen3labs/futurepass-wagmi-connectors';

Surface is identical — the gen3labs forks were published as v-for-v copies of the upstream releases. Your app code does not change beyond the imports.

If your auth client was previously pointing at the fv issuer explicitly, switch it to the gen3labs default (or set the URLs explicitly):

  const authClient = new FutureverseAuthClient({
    clientId: '<your-client-id>',
-   environment: 'production',          // routes at auth.futureverse.app
+   authorizationURL: 'https://futurepass.gen3labs.tech',
+   signerURL: 'https://fpsigner.gen3labs.tech',
    redirectUri: '<your-redirect-uri>',
  });

You'll need to register an OAuth2 client at https://futurepass.gen3labs.tech/manageclients and use that client_id. Existing fv-issued client IDs will not work against the gen3labs issuer — Pass user accounts are portable, but app credentials are per-issuer.

When to self-host vs. wait

• Building now, shipping in weeks → use the gen3labs forks. They're fresh (April 2026) and unblock you immediately.
• Long-lived enterprise integration → architect around the chain-direct path: identity = SIWE on a wallet you control; persistence = on-chain pallets; off-chain metadata = your own DB. Treat any Futureverse-hosted endpoint as optional enrichment, not a hard dependency.
• Mobile app → there is no React Native fork yet. Either (a) wait for one, (b) author one (the upstream is ~300 LOC of auth glue), or (c) skip Pass and use the user's wallet directly.

Open questions tracked

• Will the FuturePass OIDC issuer be re-hosted by gen3labs or a successor? Resolved (2026-05). gen3labs operates futurepass.gen3labs.tech (issuer) and fpsigner.gen3labs.tech (custodial signer). OAuth2 clients are registered at futurepass.gen3labs.tech/manageclients.
• Will the Asset Register become self-hostable from a public artifact? The data model is open, but no community-run instance exists today.
• Will Sylo nodes continue to run independently of Futureverse? Watch the Sylo Foundation channels.
• Will gen3labs publish forks of the React-Native auth provider, the Next-Auth provider, the transact-react wrapper, and the asset-register packages? As of capture they have not — eight @gen3labs/futurepass-* packages cover auth, wagmi connectors, signer, and transact only.

This page is rebuilt every site refresh — when these answers change, the table changes.