WASM Vixen

[kespinola]

Goal

We have received many requests for interacting with vixen change event streams within nodejs environment.

What people are doing is migrating from ws to grpc.

Strategy

Expose the parsing logic of vixen through wasm lib. Clients subscribe to dragon's mouth in their code since wasm can't do I/O but once change event received can call the parse function exposed from the wasm lib to get the parsed change event. The caller is free to work in the language of their chose to be the handler for the vixen object.

fn parse(change_event:  ChangeEventUpdate): String {
vixen::wasm::builder()
        .account(Wasm::new(TokenExtensionProgramAccParser))
        .account(Wasm::new(TokenProgramAccParser))
        .account(Wasm::new(OrcaAccParser))
        .account(Wasm::new(RaydiumAccParser))
        .instruction(Wasm::new(TokenProgramIxParser))
        .instruction(Wasm::new(TokenExtensionProgramIxParser))
        .instruction(Wasm::new(OrcaIxParser))
        .instruction(Wasm::new(RaydiumIxParser))
        .build()
        .parse(change_event)
}

var { parse } = fs.readFileSync('vixen-parsers.wasm');

// construct dragon mouth subscription in nodejs
// run messages through the wasm parser
// handle the vixen object