Overview
Memo strings are included in transaction data to specify the intended operation and its parameters. The protocol parses these memos to execute the correct logic.Most users interact with Limora through the web interface, which automatically
constructs the correct memo strings. This documentation is primarily for
developers and advanced users building integrations.
Memo Format
All memo strings follow a structured format:- OPERATION: The action to perform
- PARAMS: Colon-separated parameters specific to the operation
Trade Operations
Open Long Position
Example:
Open Short Position
Example:
Close Position
Example:
Cancel Pending Trade
Example:
Matching Operations
Deposit to Match Pool
Example:
Match a Trade
Example:
Withdraw from Match Pool
Example:
Balance Operations
Deposit Collateral
Example:
Withdraw Collateral
Example:
Encoding Rules
Number Formatting
- Use decimal notation without thousands separators
- Maximum 18 decimal places for precision
- Use “0” for optional parameters that should be disabled
String Formatting
- Use uppercase for operation names
- Use uppercase for token symbols
- Trading pairs use hyphen separator (e.g., “BTC-USDC”)
Special Values
Error Handling
Invalid memo strings will cause transaction rejection. Common errors:Code Examples
JavaScript/TypeScript
Python
Versioning
The memo format may be updated as the protocol evolves. Current version: v1.0 Future versions will maintain backward compatibility where possible. Breaking changes will be announced in advance through official channels.API Reference
See the full API documentation for programmatic access.