Skip to main content

Intent Solver

Overview​

Intent solver is Astromesh unique feature that builds on top of strategy module, designed to give retail users seamless access to Flux Astromesh's features with simple, human readable input

Problems​

Retail users face several challenges interacting with dApps:

  1. Steep learning curve: DApps knowledge takes time to absorb, which greatly consumes unwanted effort for retail users to get started.

  2. Complex navigation: Navigating through various dApps to execute a task is both challenging and time-consuming for users, especially new ones. Each dApp feature often requires multiple steps and inputs from frontends, leading to a tedious user experience and delays in creating transactions.

Solution​

The Cron Service was designed to address these issues with the following key features:

  • Composable FIS (Flux instruction set) instructions with given input and real-time queries.
  • Execute generated instructions on behalf of users
  • Abstract away advanced domain knowledges required to interact with dApps on different Planes

Keys benefits:

  1. Abstracting transaction complexity: Intent solvers simplifies the transaction process by allowing only necessary information from user in natural language. Powered by FIS, intent solvers will composes the transaction automatically, make complex transaction effortless for end users.

  2. Time saving: Without the need of navigating through many dApp pages, Intent solvers help reduce significantly the time required to complete transactions. Users now can accomplish their goal with single input quickly and conveniently.

  3. Enhance user experience: Retail users can enjoy a more intuitive experience. Intent solvers also minimize the learning curve and make advanced functionality accessible to everyone without any expertise

Components​

Since intent solver is a strategy, it inherits all components from strategy. See Strategy components

Workflow​

This flow shows how intent solver work on Flux Astromesh from user PoV:

Chart

See following sections for quickly try intent solver with scripts

Deploy your 1st Intent Solver​

Build example Intent Solver​

git clone https://github.com/FluxAstromeshLabs/nexus-bots
cd nexus-bots/examples/solver/plane-util
make build-release

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

Deploy Intent Solver​

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

# copy over the strategy binary
cp ../nexus-bots/examples/strategy/plane_util/target/wasm32-unknown-unknown/release/plane_util.wasm examples/chain/24_ConfigIntentSolver/intent_solver.wasm

# deploy
yes 12345678 | go run examples/chain/24_ConfigIntentSolver/example.go

Interact with the deployed Intent Solver​

# find intent (strategy) id from http://lcd.localhost/flux/strategy/v1beta1/strategies/lux1cml96vmptgw99syqrrz8az79xer2pcgp209sv4
# and paste in the ID field in MsgTriggerStrategies
yes 12345678 | go run examples/chain/24_TriggerIntentSolver/example.go

Build an Intent Solver​

See Build your first Intent Solver