Integration
Clawallex
By Clawallex provides the authorization engine, settlement layer, and protocol interfaces that enable OpenClaw and other AI systems to execute financial operations autonomously. Built on Solana with Model Context Protocol integration for natural language treasury management.
Install
npm install
#README
# Clawallex
> Payment infrastructure for autonomous AI agents. Protocol-native financial rails optimized for machine-to-machine transactions.
Clawallex provides the authorization engine, settlement layer, and protocol interfaces that enable OpenClaw and other AI systems to execute financial operations autonomously. Built on Solana with Model Context Protocol integration for natural language treasury management.
This repository contains the Clawallex web application, built with Next.js 15 and optimized for developer-first infrastructure positioning.
## Architecture Overview
Clawallex operates as a three-layer stack:
**Layer 1: On-Chain Settlement**
Solana smart contracts providing programmable treasury vaults with multi-signature authorization, time-locked transfers, and atomic swap primitives. Sub-400ms finality enables machine-speed financial operations.
**Layer 2: Authorization Engine**
Off-chain policy evaluation supporting merchant whitelisting, velocity controls, geographic restrictions, and multi-party approval workflows with configurable delegation hierarchies.
**Layer 3: AI Interface**
Model Context Protocol servers enabling natural language transaction requests, conversational balance queries, and policy configuration through structured prompts.
## Core Capabilities
### Protocol-Native Integration
Native MCP servers enable AI agents to execute financial operations through standardized protocol commands. Balance queries, transfer execution, policy configuration—infrastructure you can audit, running on Solana.
### Cryptographic Authorization
Threshold-based multi-party approval workflows with on-chain policy enforcement. Define spending policies, merchant whitelists, and approval requirements through declarative configuration validated cryptographically.
### Sub-Second Settlement
Sub-400ms finality from authorization to on-chain confirmation eliminates operational overhead of traditional payment rails. Zero internal transfer fees make micro-transactions economically viable.
### Programmable Treasury Vaults
Smart contract vaults with programmable authorization policies enforced on-chain. Multi-signature requirements, daily velocity limits, merchant restrictions, and time-locked transfers configured per agent deployment.
## Technology Stack
Infrastructure optimized for protocol operations and developer experience:
- **Framework**: [Next.js 15](https://nextjs.org) with App Router for static generation
- **Language**: [TypeScript](https://www.typescriptlang.org) with strict type checking
- **Blockchain**: Solana smart contracts for settlement layer
- **AI Interface**: [Model Context Protocol](https://modelcontextprotocol.io) for agent operations
- **Styling**: [Tailwind CSS 4](https://tailwindcss.com) with custom design system
- **Typography**: [Inter](https://fonts.google.com/specimen/Inter) (body) & [JetBrains Mono](https://www.jetbrains.com/lp/mono/) (code/metrics)
- **Deployment**: [Vercel](https://vercel.com) with edge functions
## Quick Start
### Prerequisites
Required dependencies:
- **Node.js** 18.17+ ([download](https://nodejs.org))
- **npm**, **yarn**, **pnpm**, or **bun**
- Code editor with TypeScript support
### Installation
```bash
# Clone repository
git clone https://github.com/clawallex-app/clawallex.git
cd clawallex
# Install dependencies
npm install
# Start development server
npm run dev
```
Open [http://localhost:3000](http://localhost:3000) to verify installation.
### MCP Server Configuration
Enable AI agent financial operations:
```bash
# Install Clawallex MCP server
npm install -g @clawallex/mcp-server
# Initialize configuration
npx clawallex-mcp init
# Start MCP server
npx clawallex-mcp serve
```
OpenClaw agents can now execute treasury operations through MCP protocol commands.
### Environment Configuration
Create `.env.local` for environment-specific settings:
```bash
# Solana RPC endpoint
NEXT_PUBLIC_SOLANA_RPC=https://api.mainnet-beta.solana.com
# Authorization engine endpoint
NEXT_PUBLIC_AUTH_ENGINE_URL=https://auth.clawallex.app
# Optional: Analytics
NEXT_PUBLIC_GA_ID=your_analytics_id
```
## Development
| Command | Description |
|---------|-------------|
| `npm run dev` | Start development server at [localhost:3000](http://localhost:3000) |
| `npm run build` | Build optimized production bundle |
| `npm run start` | Serve production build (requires build first) |
| `npm run lint` | Run ESLint for code quality checks |
| `npm run type-check` | Verify TypeScript type correctness |
### Development Workflow
```bash
# Development with hot reload
npm run dev
# Pre-commit verification
npm run lint
npm run type-check
# Production build testing
npm run build
npm run start
```
## Project Structure
```
clawallex/
├── app/
│ ├── components/ # React components
│ │ ├── Navbar.tsx # Navigation
│ │ └── Footer.tsx # Footer with protocol links
│ ├── demo/ # Demo dashboard
│ │ └── page.tsx # Vault/card interface
│ ├── status/ # System status monitoring
│ ├── layout.tsx # Root layout with metadata
│ ├── page.tsx # Landing page
│ └── globals.css # Design system styles
├── docs/ # Technical documentation
│ ├── getting-started/ # Integration guides
│ ├── operations/ # Vault operations, webhooks
│ ├── reference/ # API reference, SDK docs
│ └── technical-docs/ # Authorization engine architecture
├── public/ # Static assets
│ ├── logo.png
│ ├── logo_black.png
│ └── card.png
├── tailwind.config.ts # Design system configuration
├── tsconfig.json # TypeScript compiler settings
├── next.config.ts # Next.js configuration
└── package.json # Dependencies and scripts
```
### Key Directories
- [/app](app/) - Next.js App Router pages and components
- [/docs](docs/) - Protocol documentation and API reference
- [/public](public/) - Static assets served from root
- [/app/components](app/components/) - Shared UI components
## Design System
### Color Palette
Technical, data-driven color system:
```css
/* Primary */
--cyan: #00e5cc /* Actions, confirmations, on-chain states */
--crimson: #ff4d4d /* Attention, execution, agent activity */
/* Neutrals */
--off-white: #f0f4ff /* Primary text on dark backgrounds */
--slate: #8892b0 /* Secondary text, annotations */
--muted-slate: #5a6480 /* Tertiary text, metadata */
--dark-slate: #111827 /* Surface backgrounds */
--near-black: #050810 /* Base background */
/* Semantic */
--success: #00e5cc /* Confirmed transactions, active agents */
--warning: #fbbf24 /* Pending approvals, policy warnings */
--error: #ff4d4d /* Authorization denials, spending activity */
```
Update in [tailwind.config.ts](tailwind.config.ts):
```typescript
theme: {
extend: {
colors: {
cyan: '#00e5cc',
crimson: '#ff4d4d',
// ... additional palette
}
}
}
```
### Typography
Code-forward design system:
- **Display**: Clash Display (headings, hero text)
- **Body**: Inter (UI text, documentation)
- **Code**: JetBrains Mono (metrics, technical specifications, vault addresses)
Configure in [app/layout.tsx](app/layout.tsx):
```typescript
const inter = Inter({
subsets: ['latin'],
variable: '--font-inter',
weight: ['300', '400', '500'],
})
const jetbrainsMono = JetBrains_Mono({
subsets: ['latin'],
variable: '--font-jetbrains-mono',
weight: ['400', '500'],
})
```
### Component Patterns
Infrastructure-focused design:
- **Technical cards**: Monospace metrics, transaction visualizations
- **Protocol states**: Color-coded confirmation states
- **Data emphasis**: Transaction graphs, authorization flows, network activity
- **Minimal animations**: Performance-focused transitions
## Deployment
### Vercel (Recommended)
Zero-configuration deployment for Next.js:
[](https://vercel.com/new)
**Deployment Steps:**
1. Push repository to GitHub/GitLab/Bitbucket
2. Import in [Vercel](https://vercel.com)
3. Vercel detects Next.js configuration automatically
4. Deploy to `https://your-project.vercel.app`
5. Automatic deployments on git push
**Infrastructure Benefits:**
- Zero-configuration builds
- Automatic HTTPS and CDN
- Edge function support
- Preview deployments per PR
### Production Build Verification
```bash
# Create production build
npm run build
# Test locally
npm run start
```
### Alternative Platforms
Deployable to any Node.js hosting:
| Platform | Configuration Required |
|----------|----------------------|
| **Vercel** | Zero-config |
| **Netlify** | netlify.toml |
| **AWS Amplify** | GitHub connection |
| **DigitalOcean** | App Platform setup |
| **Railway** | Repository connection |
| **Self-hosted** | Node.js 18+ server |
### Container Deployment
```dockerfile
FROM node:18-alpine
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
RUN npm run build
EXPOSE 3000
CMD ["npm", "start"]
```
```bash
docker build -t clawallex .
docker run -p 3000:3000 clawallex
```
## Performance Metrics
Optimized for infrastructure operations:
- **Transaction Finality**: < 400ms from authorization to on-chain confirmation
- **Authorization Latency**: < 50ms for policy evaluation
- **First Contentful Paint**: < 1.2s
- **Time to Interactive**: < 2.5s
- **Bundle Size**: Optimized with automatic code splitting
## Browser Compatibility
Supports modern browsers:
- Chrome/Edge 90+
- Firefox 88+
- Safari 14+
- iOS Safari 14+
- Chrome Android 90+
## Contributing
Contributions accepted from the community. Follow standard workflow:
1. Fork the repository
2. Create feature branch: `git checkout -b feature/protocol-improvement`
3. Commit changes: `git commit -m 'Add authorization policy feature'`
4. Push branch: `git push origin feature/protocol-improvement`
5. Open Pull Request
###
... (truncated)
integration
Comments
Sign in to leave a comment