Skip to content

Retire rollup-http-server #101

@edubart

Description

@edubart

Context

The optimal solution for communicating with rollups is the libcmt library, which provides an easy-to-use C API that can be directly integrated into many programming languages through bindings.

The rollup-http-server is still provided for convenience, but it is no longer the recommended approach for rollup communication. Its use introduces overhead, and maintaining it adds burden to the machine unit. For these reasons, we plan to retire it.

Possible solutions

We should not remove rollup-http-server before we can see new Cartesi Rollups documentation have good approaches either using libcmt wrappers or simple HLF so dapp developers can start developing dapps with ease. We should also help https://github.com/cartesi/application-templates start using libcmt for its templates.

Once we can see the documentation and examples of dapps are not using it anymore, then we should remove all HTTP related code from the repository, this will also allow us to drop use of Rust in tools code base, allowing us to do the issue #89 (read it for why).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions