feat: Transactions package

[rafinskipg]

Adds a new transactions package to simplify transaction creation

🔧 Core Features

• ✅ Multi-chain transaction creation: Unified API for Solana, Ethereum/EVM, Bitcoin, and Sui
• ✅ RPC configuration system: Environment variable support and runtime configuration
• ✅ Blockchain-specific builders: Separate builders for each chain type
• ✅ Type safety: Full TypeScript support with comprehensive interfaces

⚡ Usage Examples

  import { createSendTokenTransaction } from "@phantom/transactions";
  import { useSignAndSendTransaction, NetworkId } from "@phantom/react-sdk";

  // Native token transfer
  const { transaction, error } = await createSendTokenTransaction({
    networkId: NetworkId.SOLANA_MAINNET,
    from: "sender-address",
    to: "recipient-address",
    amount: "1.5", // 1.5 SOL
  });

  // Token transfer  
  const { transaction, error } = await createSendTokenTransaction({
    networkId: NetworkId.ETHEREUM_MAINNET,
    from: "0x...",
    to: "0x...",
    amount: "100",
    token: "0x...", // USDC contract address
    decimals: 6,
  });

  // Use with Phantom SDK
  const signature = await signAndSendTransaction({
    transaction,
    networkId,
  });

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	bitcoinjs-lib@​6.1.7
	@​mysten/​sui.js@​0.54.1

View full report

[graphite-app]

The ERC-20 token transfer implementation has an issue with the transaction data encoding. The current approach using tokenContract.write.transfer.toString() won't produce valid transaction data that can be executed on-chain.

For proper ERC-20 transfers, the transaction data needs to be encoded with the function signature and properly formatted parameters. Consider using viem's encodeFunctionData method instead:

import { encodeFunctionData } from 'viem'

// ...

const data = encodeFunctionData({
  abi: ERC20_ABI,
  functionName: 'transfer',
  args: [params.to as `0x${string}`, value]
})

const transaction = {
  to: params.token as `0x${string}`,
  data
}

This will ensure the transaction contains properly encoded calldata that the EVM can interpret correctly when executing the token transfer.

Suggested change

	const transaction = {
	to: params.token as `0x${string}`,
	data: tokenContract.write.transfer.toString(), // This needs proper encoding
	// Note: This is a simplified version. In practice, you'd need to properly encode the function call
	const transaction = {
	to: params.token as `0x${string}`,
	data: encodeFunctionData({
	abi: ERC20_ABI,
	functionName: 'transfer',
	args: [params.to as `0x${string}`, value]
	})
	}

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

[alexz-phantom]

@rafinskipg

[graphite-app]

The conversion from bigint to Number in the SUI amount calculation risks precision loss for large values. This is particularly problematic for cryptocurrency transactions where exact amounts are critical. Consider preserving the full precision by using bigint arithmetic throughout:

const amount = typeof params.amount === 'string'
  ? BigInt(Math.floor(parseFloat(params.amount) * 1_000_000_000))
  : typeof params.amount === 'bigint'
  ? params.amount
  : BigInt(Math.floor(params.amount * 1_000_000_000));

This approach maintains precision for large transaction amounts while still handling all the input types correctly.

Suggested change

	const amount = typeof params.amount === 'string'
	? Math.floor(parseFloat(params.amount) * 1_000_000_000)
	: typeof params.amount === 'bigint'
	? Number(params.amount)
	: Math.floor(params.amount * 1_000_000_000);
	const amount = typeof params.amount === 'string'
	? BigInt(Math.floor(parseFloat(params.amount) * 1_000_000_000))
	: typeof params.amount === 'bigint'
	? params.amount
	: BigInt(Math.floor(params.amount * 1_000_000_000));

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

[alexz-phantom]

@rafinskipg BigInt is probably the best stable type to use everywhere if possible? Like, just get rid of the fractional part at step 1 and stay in BigInt through everything?

[graphite-app]

The syntax export type * from "./types"; is not valid TypeScript. TypeScript doesn't support exporting all types with the type keyword in this manner. To properly export all types and interfaces from the types file, change this to export * from "./types"; which will export both types and values.

Suggested change

	export type * from "./types";
	export * from "./types";

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

[alexz-phantom]

@rafinskipg

[alexz-phantom]

Do we strictly need to be turning off this rule globally?

[alexz-phantom]

@rafinskipg

[alexz-phantom]

@rafinskipg

[alexz-phantom]

could make these methods generic with some baseTokenToAmount or whatever if you set up a lookup of MIST_PER_SUI / LAMPORTS_PER_SOL etc

[alexz-phantom]

@rafinskipg BigInt is probably the best stable type to use everywhere if possible? Like, just get rid of the fractional part at step 1 and stay in BigInt through everything?