TRVL - Personalized AI Travel Assistant

AI Travel Assistant with memory retention to deliver tailored travel recommendations just for you.

Features

• Nextjs React framework

• Tailwind

• Shadcn Component Library

• Solana WalletAdapter

• Metaplex Umi

• Zustand

• Dark/Light Mode

• Umi Helpers

• OpenAI's o1-preview Model via OpenRouter: AI model for generating responses.

• Mem0: Memory management to retain user preferences and past interactions.

• Twitter API v2: For authentication and tweeting recommendations.

Change RPC

You are free to set up the RPC url into project as you wish either via

• .env
• constants.ts file
• hardcoded into umi directly

In this example the RPC url is hardcoded into the umiStore umi state under src/store/useUmiStore.ts at line 21.

const useUmiStore = create<UmiState>()((set) => ({
  // add your own RPC here
  umi: createUmi("http://api.devnet.solana.com").use(
    signerIdentity(
      createNoopSigner(publicKey("11111111111111111111111111111111"))
    )
  ),
  signer: undefined,
  updateSigner: (signer) => {
    console.log("updateSigner");
    set(() => ({ signer: createSignerFromWalletAdapter(signer) }));
  },
}));

Why Zustand?

Zustand is a global store that allows you to access the store state from both hooks and regular state fetching.

By storing the umiInstance in zustand we can access it in both ts and tsx files while also having the state update via other providers and hooks such as walletAdapter.

While it's normally easier to use the helper methods below to access umi you can also access the state methods manually by calling for the umiStore state yourself.

When fetching the umi state directly without a helper it will only pickup the umi instance and not the latest signer. By design when the walletAdapter changes state the state of the signer in the umiStore is updated but NOT applied to the umi state. So you will need to also pull the latest signer state and apply it to umi. This behaviour can be outlined in the umiProvider.tsx file. The helpers always pull a fresh instance of the signer state.

// umiProvider.tsx snippet
useEffect(() => {
  if (!wallet.publicKey) return;
  // When wallet.publicKey changes, update the signer in umiStore with the new wallet adapter.
  umiStore.updateSigner(wallet as unknown as WalletAdapter);
}, [wallet.publicKey]);

Access Umi in .tsx

// Pulls the umi state from the umiStore using hook.
const umi = useUmiStore().umi;
const signer = useUmiStore().signer;

umi.use(signerIdentity(signer));

Access Umi in .ts

// Pulls umi state from the umiStore.
const umi = useUmiStore.getState().umi;
const signer = useUmiStore.getState().signer;

umi.use(signerIdentity(signer));

Helpers

Stored in the /lib/umi folder there are some pre made helps you can use to make your development easier.

Umi is split up into several components which can be called in different scenarios.

sendAndConfirmWithWalletAdapter()

Passing a transaction into sendAndConfirmWithWalletAdapter() will send the transaction while pulling the latest walletAdapter state from the zustand umiStore and will return the signature as a string. This can be accessed in both .ts and .tsx files.

The function also provides and locks in the commitment level across blockhash, send, and confirm if provide. By default confirmed is used.

We also have a skipPreflight flag that can be enabled.

If using priority fees it would best to set them here so they can globally be used by the send function or to remove them entirely if you do not wish to use them.

import useUmiStore from "@/store/useUmiStore";
import { setComputeUnitPrice } from "@metaplex-foundation/mpl-toolbox";
import { TransactionBuilder, signerIdentity } from "@metaplex-foundation/umi";
import { base58 } from "@metaplex-foundation/umi/serializers";

const sendAndConfirmWalletAdapter = async (
  tx: TransactionBuilder,
  settings?: {
    commitment?: "processed" | "confirmed" | "finalized";
    skipPreflight?: boolean;
  }
) => {
  const umi = useUmiStore.getState().umi;
  const currentSigner = useUmiStore.getState().signer;
  console.log("currentSigner", currentSigner);
  umi.use(signerIdentity(currentSigner!));

  const blockhash = await umi.rpc.getLatestBlockhash({
    commitment: settings?.commitment || "confirmed",
  });

  const transactions = tx
    // Set the priority fee for your transaction. Can be removed if unneeded.
    .add(setComputeUnitPrice(umi, { microLamports: BigInt(100000) }))
    .setBlockhash(blockhash);

  const signedTx = await transactions.buildAndSign(umi);

  const signature = await umi.rpc
    .sendTransaction(signedTx, {
      preflightCommitment: settings?.commitment || "confirmed",
      commitment: settings?.commitment || "confirmed",
      skipPreflight: settings?.skipPreflight || false,
    })
    .catch((err) => {
      throw new Error(`Transaction failed: ${err}`);
    });

  const confirmation = await umi.rpc.confirmTransaction(signature, {
    strategy: { type: "blockhash", ...blockhash },
    commitment: settings?.commitment || "confirmed",
  });
  return {
    signature: base58.deserialize(signature),
    confirmation,
  };
};

export default sendAndConfirmWalletAdapter;

umiWithCurrentWalletAdapter()

This fetches the current umi state with the current walletAdapter state from the umiStore. This is used to create transactions or perform operations with umi that requires the current wallet adapter user.

Can be used in both .ts and .tsx files

import useUmiStore from "@/store/useUmiStore";
import { signerIdentity } from "@metaplex-foundation/umi";

const umiWithCurrentWalletAdapter = () => {
  // Because Zustand is used to store the Umi instance, the Umi instance can be accessed from the store
  // in both hook and non-hook format. This is an example of a non-hook format that can be used in a ts file
  // instead of a React component file.

  const umi = useUmiStore.getState().umi;
  const currentWallet = useUmiStore.getState().signer;
  if (!currentWallet) throw new Error("No wallet selected");
  return umi.use(signerIdentity(currentWallet));
};
export default umiWithCurrentWalletAdapter;

umiWithSigner()

umiWithSigner() allows you to pass in a signer element (generateSigner(), createNoopSigner()) and use it with the umi instance stored in the umiStore state.

import useUmiStore from "@/store/useUmiStore";
import { Signer, signerIdentity } from "@metaplex-foundation/umi";

const umiWithSigner = (signer: Signer) => {
  const umi = useUmiStore.getState().umi;
  if (!signer) throw new Error("No Signer selected");
  return umi.use(signerIdentity(signer));
};

export default umiWithSigner;

Example Transaction Using Helpers

Within the /lib folder you will find a transferSol example transaction that utilizes both the fetching of the umi state using umiWithCurrentWalletAdapter() and the sending of the generated transaction using sendAndConfirmWithWalletAdapter().

By pulling state from the umi store with umiWithCurrentWalletAdapter() if any of our transaction args require the signer type this will be automatically pulled from the umi instance which is generated with walletAdapter. In this case the from account is determined by the current signer connected to umi (walletAdapter) and auto inferred in the transaction for us.

By then sending transaction with sendAndConfirmWithWalletAdapter the signing process will use the walletAdapter and ask the current user to signer the transaction. The transaction will be sent to the chain.

// Example of a function that transfers SOL from one account to another pulling umi
// from the useUmiStore in a ts file which is not a React component.

import { transferSol } from "@metaplex-foundation/mpl-toolbox";
import umiWithCurrentWalletAdapter from "./umi/umiWithCurrentWalletAdapter";
import { publicKey, sol } from "@metaplex-foundation/umi";
import sendAndConfirmWalletAdapter from "./umi/sendAndConfirmWithWalletAdapter";

// This function transfers SOL from the current wallet to a destination account and is callable
// from any tsx/ts or component file in the project because of the zustand global store setup.

const transferSolToDestination = async ({
  destination,
  amount,
}: {
  destination: string;
  amount: number;
}) => {
  // Import Umi from `umiWithCurrentWalletAdapter`.
  const umi = umiWithCurrentWalletAdapter();

  // Create a transactionBuilder using the `transferSol` function from the mpl-toolbox.
  // Umi by default will use the current signer (walletAdapter) to also set the `from` account.
  const tx = transferSol(umi, {
    destination: publicKey(destination),
    amount: sol(amount),
  });

  // Use the sendAndConfirmWithWalletAdapter method to send the transaction.
  // We do not need to pass the umi stance or wallet adapter as an argument because a
  // fresh instance is fetched from the `umiStore` in the `sendAndConfirmWithWalletAdapter` function.
  const res = await sendAndConfirmWalletAdapter(tx);
};

export default transferSolToDestination;

Component Library

This template is setup to work with the Shadcn reusable components from https://ui.shadcn.com/.

Shadcn is preinstalled so you only need to install the required components you wish to use from the documentation https://ui.shadcn.com/docs/

Theming

Theming is handled by Shadcn and Tailwind using CSS Variables. Documentation regarding theming can be found here https://ui.shadcn.com/docs/theming and on Tailwinds websbite https://tailwindcss.com/docs/

Demo Blinks

https://www.dialect.to/

https://solana-actions.vercel.app/memo

Enable Solana Blinks on Twitter, with wallet support for Phantom, Backpack and Solflare.

Blinks transform the way you interact with the Solana ecosystem. This Chrome extension detects Action-compatible URLs and unfurls them into interactive buttons, allowing you to engage directly with the content.

Key Features:

• Seamless Integration: Automatically detects Action-compatible URLs and converts them into user-friendly, actionable Blinks on supported websites.
• Wallet Support: Compatible with Solana wallets including Phantom, Backpack, and Solflare, ensuring secure and streamlined transactions.
• Enhanced Interactivity: Blinks provide a standardized interface for executing actions on the blockchain, making it easier than ever to participate in the Solana ecosystem.

With Blinks, engaging and interacting with web3 is as simple as sharing a link

Add to Chrome: https://chromewebstore.google.com/detail/dialect-blinks/mhklkgpihchphohoiopkidjnbhdoilof