Skip to main content

Real-time Strategy

Overview​

On-Chain Strategy is a category of Nexus Bot applications specifically designed for institutional users. These strategies leverage the unique capabilities of the Flux Instruction Set (FIS) to provide real-time data and execute transactions with minimal latency, addressing the critical needs of institutional users.

Problems​

Institutional users face several challenges:

  1. Time-Sensitive Decisions: Latency in data processing and decision-making can lead to significant risks and missed opportunities.
  2. Complex Infrastructure: Maintaining an up-to-date and responsive infrastructure requires substantial resources and expertise.
  3. Data Integrity and Reliability: Traditional data pipelines, involving event indexing, APIs, clients, and databases, can be manipulated or delayed, leading to potential inaccuracies in strategic decisions.

Solutions​

The On-Chain Strategy for institutional users offers several key advantages:

  1. Real-Time Data Access: By utilizing the Flux Instruction Set (FIS), on-chain strategies can access real-time data during the transaction execution phase. This eliminates the need for external data pipelines that are prone to delays and manipulation.
  2. Simplified Infrastructure: Institutional users can reduce their reliance on complex off-chain infrastructure. On-chain strategies handle the data processing and execution natively within the blockchain environment.
  3. Enhanced Reliability: Directly accessing on-chain data ensures the integrity and reliability of the information used for decision-making. This approach minimizes the risk of data manipulation and delays inherent in traditional data pipelines.

Strategy Components​

Strategy​

The strategy is a private, programmable, and configurable Nexus Bot tailored for each institutional user. Users first build and deploy their strategies with static FIS queries and permissions. These parameters can be configured later, allowing users to enable or disable the strategy, update strategy logic, and modify static FIS queries.

  • Static FIS Queries: These are common on-chain data points aggregated and made available at the beginning of each block for all strategies to utilize.
  • Dynamic FIS Queries: These are real-time on-chain data points accessed at the moment the trigger transaction occurs, providing up-to-the-minute information for strategy execution.

Trigger Client​

The trigger client is responsible for aggregating and processing data to generate actionable signals. During the transaction execution phase, the client packs these signals along with the necessary dynamic FIS queries into a trigger transaction. This trigger transaction is then sent to the strategy for execution. The strategy then converts trigger transaction signals along with FIS queries output into Nexus Transactions based on the programmed conditions of the strategy. These Nexus Transactions are forwarded to all Planes to fulfill the prompted actions.

Deploy your 1st Strategy​

Compile example Strategy​

git clone https://github.com/FluxAstromeshLabs/nexus-bots
cd nexus-bots/examples/strategy/bank-dummy
make build-release

# verify output binary exists
ls target/wasm32-unknown-unknown/release/bank_dummy.wasm

Deploy Strategy​

# clone sdk-go
git clone https://github.com/FluxAstromeshLabs/sdk-go
cd sdk-go

# copy over the strategy binary
cp ../nexus-bots/examples/strategy/bank-dummy/target/wasm32-unknown-unknown/release/bank_dummy.wasm examples/chain/21_MsgConfigStrategy/strategy.wasm

# tweak config in example.go

# deploy
yes 12345678 | go run examples/chain/21_MsgConfigStrategy/example.go

Trigger Strategy​


# find out your strategy id from http://lcd.localhost/flux/strategy/v1beta1/strategies/owner/lux1cml96vmptgw99syqrrz8az79xer2pcgp209sv4
yes 12345678 | go run examples/chain/21_MsgConfigStrategy/example.go

Build a Strategy​

See Build your first Strategy