Skip to content
Back to skills

Gdex Transfers

ASecurity

Native and ERC20/SPL token transfers via GDEX managed custody — send assets to any recipient on supported chains

  • 4 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 3, 2026
ai-agentstypescriptapibackend

Works with

  • api

Security analysis

A100/100

Scanned October 3, 2026

npx -y skills add GemachDAO/gdex-skill --skill gdex-transfers --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Gdex Transfers?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Gdex Transfers
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gemachdao-gdex-transfers/badge)](https://www.skillsdirectory.com/skills/gemachdao-gdex-transfers)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: gdex-transfers
description: Native and ERC20/SPL token transfers via GDEX managed custody — send assets to any recipient on supported chains
---

# GDEX: Transfers

Send native assets (ETH, SOL, SUI, BNB, …) or ERC20 / SPL tokens from a
managed-custody wallet to any recipient.

## When to Use

- Withdrawing native assets to an external wallet
- Sending ERC20 / SPL tokens to a recipient
- Paying out winnings, rewards, or peer-to-peer transfers

## Prerequisites

- `@gemachdao/gdex-skill` installed
- Authenticated via managed-custody sign-in — see **gdex-authentication**
- Session keypair (`sessionPrivateKey` + `sessionKey`) from sign-in
- Pre-built `computedData` payload (encrypted via the standard AES-256-CBC
  managed-custody contract). Caller is responsible for ABI-encoding the
  transfer parameters and signing with the session key — schema is
  documented in `src/api/services/ServiceMain.ts` of the backend.

## Backend Endpoints

| Method | Path | Purpose |
|--------|------|---------|
| `POST` | `/v1/transfer` | Native token transfer |
| `POST` | `/v1/transfer_token` | ERC20 / SPL token transfer |

Both endpoints accept:
```json
{ "computedData": "<hex>", "chainId": 8453 }
```

## SDK Usage

```typescript
import { GdexSkill } from '@gemachdao/gdex-skill';

const skill = new GdexSkill();
skill.loginWithApiKey(process.env.GDEX_API_KEY!);

// Native ETH transfer (caller pre-builds computedData)
const result = await skill.transferNative({
  computedData,           // hex-encoded encrypted payload
  chainId: 8453,
});

// ERC20 / SPL transfer
const result2 = await skill.transferToken({
  computedData,
  chainId: 622112261,     // Solana SPL
});
```

## Response

Typically:
```json
{ "requestId": "...", "status": "pending", "createdAt": 1717000000 }
```
Poll status via `GET /v1/trade-status/:requestId` (or `skill.getManagedTradeStatus(requestId)`).

## Notes

- Both endpoints follow the standard managed-custody encrypted-payload pattern.
- For Solana SPL transfers, the first transfer to a recipient may incur an
  Associated Token Account (ATA) creation fee (~0.002 SOL).
- Chain id semantics match the rest of the SDK — Solana uses `622112261`,
  Sui uses `1313131213`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.