internet-court/internet-court-skill / vendored/sendaifun/glam
glam
VerifiedSolana vault management via GLAM Protocol. Triggers: glam, glam-cli, glam-sdk, vault create/manage, tokenized vault, share class, DeFi vault, treasury, asset management, access control, delegate permissions, Jupiter swap, Kamino lending/borrow/vaults/farms, staking (Marinade/native/SPL/Sanctum/LST), cross-chain USDC (CCTP), timelock, subscription/redemption, NAV pricing, token transfer. Supports CLI and TypeScript SDK.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 11.1 KB |
| SKILL.md | skill md | 7.2 KB |
| docs/troubleshooting.md | markdown | 4.8 KB |
| evaluations.json | config | 10.7 KB |
| examples/EXAMPLES.md | markdown | 10.9 KB |
| resources/cli/advanced.md | markdown | 4.1 KB |
| resources/cli/alt.md | markdown | 1.6 KB |
| resources/cli/delegate.md | markdown | 3.6 KB |
| resources/cli/invest.md | markdown | 1.8 KB |
| resources/cli/jupiter.md | markdown | 2.8 KB |
| resources/cli/kamino-farms.md | markdown | 2.1 KB |
| resources/cli/kamino-lend.md | markdown | 3.4 KB |
| resources/cli/kamino-vaults.md | markdown | 2.3 KB |
| resources/cli/lst.md | markdown | 2.8 KB |
| resources/cli/manage.md | markdown | 2.9 KB |
| resources/cli/staking.md | markdown | 3.8 KB |
| resources/cli/transfer.md | markdown | 1.9 KB |
| resources/cli/vault.md | markdown | 8.0 KB |
| resources/concepts.md | markdown | 6.9 KB |
| resources/sdk/client.md | markdown | 10.3 KB |
| resources/sdk/integrations.md | markdown | 9.7 KB |
| resources/sdk/ix-mapper.md | markdown | 3.9 KB |
| resources/sdk/mint.md | markdown | 2.8 KB |
| resources/sdk/multisig.md | markdown | 3.3 KB |
resources/cli/advanced.md
View on GitHub# CLI: Advanced Commands
CCTP cross-chain bridging and timelock operations.
## CCTP Commands (Cross-Chain)
Bridge USDC between chains via Circle's Cross-Chain Transfer Protocol.
### `glam-cli cctp bridge-usdc`
Bridge USDC to another chain.
```bash
glam-cli cctp bridge-usdc <amount> <domain> <destination_address> [OPTIONS] [--yes]
```
**Arguments:**
| Argument | Description |
|----------|-------------|
| `amount` | USDC amount to bridge |
| `domain` | Target destination domain ID |
| `destination_address` | Destination address on target chain |
**Options:**
| Flag | Description |
|------|-------------|
| `--destination-caller <ADDRESS>` | Restrict who can receive on destination |
| `--max-fee-bps <BPS>` | Maximum fee in basis points (default: 1) |
| `--base58` | Use base58 encoding for address |
| `--fast` | Use fast bridging mode |
| `-y, --yes` | Skip confirmation prompt |
**Destination domains:**
| Domain | Chain |
|--------|-------|
| 0 | Ethereum |
| 1 | Avalanche |
| 2 | Optimism |
| 3 | Arbitrum |
| 6 | Base |
| 7 | Polygon |
**Example:**
```bash
# Bridge 1000 USDC to Ethereum
glam-cli cctp bridge-usdc 1000 0 0x742d35Cc6634C0532925a3b844Bc9e7595f00000
```
### `glam-cli cctp receive`
Receive bridged USDC (from another chain to Solana).
```bash
glam-cli cctp receive <source_domain> [OPTIONS]
```
**Options:**
| Flag | Description |
|------|-------------|
| `--txHash <HASH>` | Source chain transaction hash to receive |
| `--nonce <NONCE>` | CCTP message nonce to receive |
### `glam-cli cctp list`
List CCTP bridge transactions.
```bash
glam-cli cctp list [OPTIONS]
```
**Options:**
| Flag | Description |
|------|-------------|
| `--since-slot <SLOT>` | Only show events after this slot |
| `--batch-size <SIZE>` | Number of signatures to fetch per batch |
| `--commitment <LEVEL>` | Commitment level (`confirmed`, `finalized`) |
---
## CCTP Policy Commands
### `glam-cli cctp view-policy`
View CCTP policy settings for the vault.
```bash
glam-cli cctp view-policy
```
### `glam-cli cctp allowlist-destination`
Add a destination address/domain to the CCTP allowlist.
```bash
glam-cli cctp allowlist-destination <domain> <address> [--base58] [--yes]
```
### `glam-cli cctp remove-destination`
Remove a destination from the CCTP allowlist.
```bash
glam-cli cctp remove-destination <domain> <address> [--base58] [--yes]
```
---
## Timelock Commands
Protect vault with timelocked configuration changes.
### `glam-cli timelock view`
View current timelock status and pending changes.
```bash
glam-cli timelock view
```
**Output shows:**
- Current timelock duration and remaining time
- Pending state updates with detailed diffs:
- **integrationAcls**: Added/removed/modified integrations with protocol names
- **delegateAcls**: Added/removed/modified delegates with permission changes
- **assets / borrowable**: Added `[+]` and removed `[-]` token mints
- **timelockDuration**: Old → new duration
### `glam-cli timelock set`
Set timelock duration. Change takes effect after current delay period.
```bash
glam-cli timelock set <duration> [--yes]
```
**Common durations:**
| Seconds | Duration |
|---------|----------|
| 3600 | 1 hour |
| 86400 | 1 day |
| 259200 | 3 days |
| 604800 | 1 week |
**Example:**
```bash
# Set 24-hour timelock
glam-cli timelock set 86400
```
### `glam-cli timelock apply`
Apply pending timelock change after delay period.
```bash
glam-cli timelock apply [--yes]
```
### `glam-cli timelock cancel`
Cancel pending timelock change.
```bash
glam-cli timelock cancel [--yes]
```
---
## Timelock Workflow
```bash
# 1. View current status
glam-cli timelock view
# 2. Set new delay (e.g., 24 hours)
glam-cli timelock set 86400
# 3. Wait for current delay period to pass...
# 4. Apply the change
glam-cli timelock apply
# Or cancel if needed
glam-cli timelock cancel
```
---
## Security Best Practices
1. **Use timelocks for production vaults** - Gives time to react to unauthorized changes
2. **Start with shorter delays** - 1 hour during setup, increase for production
3. **Monitor pending changes** - Check `timelock view` regularly
4. **Cross-chain transfers** - Double-check destination addresses (irreversible)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |