Using Rental Code Metadata to Set Strategy Trading Limits
Summary
The document explains how strategy developers can attach metadata to rental registration codes and read it inside a strategy to set different usage limits for different customers. A strategy can map metadata values to operating tiers, then check account holdings before running its trading logic. The example applies this idea to a spot strategy: one tier has no position cap, other tiers impose coin limits, and an unset value uses a default cap. For futures, the document says that limits would need to account for position data and strategy specific behavior.
The example describes the workflow for assigning metadata, distributing the registration code, and changing the metadata later; the buyer may need to restart the bot for the changed tier to take effect. This is platform specific guidance, not a general trading method. The code is illustrative and the document explicitly cautions that real restrictions must be designed around the strategy. Metadata length is limited, and the example does not establish that its checks provide robust security or prevent all trading beyond the intended limits.
Key ideas
- Rental registration code metadata can assign different usage tiers to strategy customers.
- A strategy can read metadata and compare it with account holdings before executing its trading logic.
- The spot example maps tier labels to position limits and assigns a default when metadata is absent.
- Limits for futures strategies must be designed around the position information and logic used by those strategies.
- Changing a code's metadata may require the buyer to restart the bot before the new tier takes effect.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.