Files
logos-verified-proxy-module/metadata.json
T
Dario Gabriel LipicarandClaude Opus 5 e1550d61e1 chore: display as "Verified Proxy Module", to distinguish it from the UI
The module and its panel both showed as "Verified Proxy" in a package catalog,
distinguishable only by the `core` / `ui_qml` column beside them. The UI keeps
the plain name — it is what Basecamp puts in the sidebar, where "Verified Proxy
UI" would read as a component rather than an app — so the backend takes the
qualifier.

Version goes to 0.1.1 rather than reissuing 0.1.0: the release pipeline skips a
version that is already published, and the package contents do change, so a
reissue would be a lie about what 0.1.0 contained.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-27 00:24:58 -03:00

42 lines
859 B
JSON

{
"name": "verified_proxy_module",
"display_name": "Verified Proxy Module",
"version": "0.1.1",
"description": "Light-client-verified Ethereum JSON-RPC, wrapping nimbus libverifproxy",
"author": "Logos Core Team",
"type": "core",
"interface": "universal",
"concurrency": "multi",
"category": "wallet",
"main": "verified_proxy_module_plugin",
"codegen": {
"impl_header": "verified_proxy_impl.h",
"impl_class": "VerifiedProxyImpl"
},
"dependencies": [],
"include": [],
"capabilities": [],
"nix": {
"packages": {
"build": [
"pkg-config"
],
"runtime": [
"nlohmann_json",
"libmicrohttpd",
"curl"
]
},
"external_libraries": [
{
"name": "verifproxy"
}
],
"cmake": {
"extra_include_dirs": [
"lib"
]
}
}
}